Spots V14 Um M

SPOTS V14 Mobile
User Manual (UMN)

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

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the “Legal, Safety
and Environmental Information” part of this document or documentation set.
The same text in German:
f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-
satzes.
2 Id:0900d8058018dbf6 E200613-01-114-V14.0I-23
User Manual (UMN)
Table of Contents
This document has 298 pages.
Reason for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1 Introducing SPOTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3 SPOTS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.4 Technology Plug-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.5 Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.6 User Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.7 PM Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.8 Database Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.9 Trend Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.9.1 Data Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.9.1.1 Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.9.1.2 Aggregation with Extrapolation of missing values . . . . . . . . . . . . . . . . . 29
1.9.1.3 Aggregation without Extrapolation of missing values. . . . . . . . . . . . . . . 30
1.9.2 Data Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.9.3 Trend Analysis Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.10 Online Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.10.1 Alarm Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.10.2 Online Monitoring Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.11 SNMP Alarm Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.12 Extended Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2 Initial Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.1 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.2 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.3 User-Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.4 User Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.5 Domain Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.6 Data Collection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.7 Automatic Node Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.8 Automatic Node Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.9 Online Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1 Interaction and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.1 User Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.1.1 Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.1.2 Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.2 Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.2.1 Interactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.2.2 Scheduled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.2 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.2.1 Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.2.2 SPOTS Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
E200613-01-114-V14.0I-23 Id:0900d8058018dbf6 3
User Manual (UMN)
3.2.2.1 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.2.2 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.2.2.3 Task Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.2.4 Taskbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.2.5 Task Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.2.6 History Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.2.2.7 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.2.3 Preferences window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.2.3.1 General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.2.3.2 Reports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.2.3.3 Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.2.3.4 Calendar Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.2.4 Object Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.3.1 Print window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.3.2 Print Preview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.3.3 Page Setup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.3.3.1 Margins Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.3.3.2 Header / Footer Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.3.3.3 Paper Setup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.1 SPOTS Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.1.1 SPOTS Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.1.2 User Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.1.3 Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.1.4 Technology Plug-Ins Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.1.5 Metadata Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.1.6 Reports Editor Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.2 Metadata Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4 Using Spots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.1 Network Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.1.1 Node Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.1.2 Software Version window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.1.3 Resources Deletion window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.1.4 Domains Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.1.5 User Domain window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.1.6 Extended Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.1.6.1 Creating a User Extended Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.1.6.2 Extended Fields Administration window . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.2 Data Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.2.1 Load Data window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.2.2 Delete Data window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.2.3 Data Aggregation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.2.4 Make History window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.3 PM Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.3.1 Sets of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.3.1.1 Sets of Objects window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4 Id:0900d8058018dbf6 E200613-01-114-V14.0I-23
User Manual (UMN)
4.3.1.2 Set of Objects syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.3.1.3 Sets of Objects Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.3.2 Sets of Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.3.2.1 Sets of Counters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.3.2.2 Set of Counters syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.3.2.3 Sets of Counters Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.3.3 Virtual Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.3.3.1 Virtual Counters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.3.3.2 Virtual Counters syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.3.3.3 Virtual Counters Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.3.4 Import PM Entities window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.3.5 Export PM Entities window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.4 Trend Analysis Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.4.1 Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.4.2 Scheduler Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.4.3 Task Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.4.4 My Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.5 Online Monitoring Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.5.1 Alarm Browser window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.5.2 Threshold Lifecycle window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.5.2.1 Create Monitored Metric window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.5.2.2 Create Threshold Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.5.2.3 Monitored Period Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.5.2.4 Period Definition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.5.2.5 Monitored Period Details window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4.5.2.6 Import and Export Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4.5.2.7 Delete Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.5.3 Threshold Classes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.5.3.1 Import and Export Thresholds Classes . . . . . . . . . . . . . . . . . . . . . . . . 117
4.5.3.2 Delete Threshold Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.5.4 Threshold Viewer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.5.5 PDC Types window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.5.6 PDC Platform window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4.6 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.6.1 Trend Analysis Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.6.1.1 Ad-Hoc Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.6.1.2 Ad-Hoc Comparison Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4.6.1.3 Nokia Siemens Networks Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
4.6.1.4 Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
4.6.1.5 Class Browser window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
4.6.1.6 Report Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
4.6.1.7 Report Filter Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
4.6.1.8 Report Output window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
4.6.2 Online Monitoring Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
4.6.2.1 Ad-Hoc Online Report window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
4.6.2.2 Online Monitor Preferences Editor window . . . . . . . . . . . . . . . . . . . . . 181
4.6.2.3 Report Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
E200613-01-114-V14.0I-23 Id:0900d8058018dbf6 5
User Manual (UMN)
4.6.2.4 Alarm Filter Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

4.6.3 My Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
4.7 SPOTS SlideShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
4.7.1 SlideShow window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
4.7.2 Preferences Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
4.7.3 Slide Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
4.7.4 Reports & Presentations Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
4.7.5 Presentation Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
4.7.6 Presentation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
4.8 SPOTS Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
4.8.1 Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
4.8.2 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
4.8.2.1 Visualization Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
4.8.2.2 Navigation Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
4.8.2.3 Main Processes Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
4.8.3 Feature Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
4.8.3.1 Live Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
4.8.3.2 Statistical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
4.8.3.3 Database Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
4.8.3.4 SPOTS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
4.8.4 Data Collection Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.8.5 Systems Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
4.9 Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
4.9.1 SPOTS Architecture and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
4.9.2 Saving SPOTS Server Resources (CPU, RAM …) . . . . . . . . . . . . . . . 246
4.9.2.1 Creating Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
4.9.2.2 Executing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
4.9.2.3 Saving Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
4.9.2.4 Virtual Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
4.9.3 Using PM Client Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
4.9.4 PM Client version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
4.9.5 Network elements load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
4.9.6 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
5.1 Appendix A - Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
5.1.1 Thresholds CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
5.1.2 Thresholds Classes CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
5.2 Appendix B - PMS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
5.2.1 adhoc2srl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
5.2.2 ChangeObjNames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
5.2.3 Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
5.2.4 dbaggregator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
5.2.5 dbarchive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
5.2.6 dbcalcstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
5.2.7 dbhistoryadm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
5.2.8 dbinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
5.2.9 dbloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
6 Id:0900d8058018dbf6 E200613-01-114-V14.0I-23
User Manual (UMN)
5.2.10 dbloadgaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

5.2.11 dbobjectpurge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
5.2.12 dbreadstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
5.2.13 dbremover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
5.2.14 deletealarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
5.2.15 extfieldinstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
5.2.16 initspots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
5.2.17 loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
5.2.18 mergeobjects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
5.2.19 metadump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
5.2.20 mkhistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
5.2.21 reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
5.2.22 setdbpwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
5.2.23 spotslicense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
5.2.24 spotsping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
5.2.25 spotsshutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
5.2.26 SQL Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
5.2.27 dbstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
5.2.28 dbshut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
5.3 Appendix C - PMC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
5.3.1 reportscompiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
5.3.2 spotsreportcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
5.4 Appendix D - Report Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
5.5 Appendix E - Refreshable Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
5.5.1 Restrictions to Refreshable Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 293
5.5.2 Refreshable Reports for Aggregated SoOs . . . . . . . . . . . . . . . . . . . . . 293
5.6 Appendix F- SPOTS Hardware dimensioning Assumptions . . . . . . . . 293
6 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
E200613-01-114-V14.0I-23 Id:0900d8058018dbf6 7
User Manual (UMN)
List of Figures
Figure 1 SPOTS Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 2 SPOTS Single Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 3 Network Partitioning Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 4 Relation between Network Domains and Clusters Diagram . . . . . . . . . . 25
Figure 5 Spreading of Management Domains Example . . . . . . . . . . . . . . . . . . . . 26
Figure 6 SPOTS SNMP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 7 Hierarchical Domain Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 8 User Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 9 SPOTS Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 10 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 11 Main Toobar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 12 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 13 Client Preferences Editor General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 14 Client Preferences Editor Reports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 15 Client Preferences Editor Alarms Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 16 Preferences Editor window - Calendar Tab . . . . . . . . . . . . . . . . . . . . . . 51
Figure 17 Report Wizard window - Set Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 18 Metadata Help window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 19 Node Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 20 Software Versions window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 21 Resources Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 22 Domains Configurator window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 23 Users Domain window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 24 Extended Fields Administration window . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 25 Load Data window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 26 Load Operation Results window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 27 Delete Data window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 28 Data Aggregation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 29 Make History window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 30 Set of Objects window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 31 SO Syntax Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 32 Extended Fields Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 33 Object Creation Wizard, Creating Virtual Identity window- Step1 . . . . . . 79
Figure 34 Object Creation Wizard, Creating Virtual Identity window - Step2 . . . . . 80
Figure 35 Set of Counters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 36 SC Syntax Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 37 Counter Creation Wizard, Creating Virtual Entity window- Step1 . . . . . . 86
Figure 38 Counter Creation Wizard, Creating Virtual Entity window - Step2 . . . . . 87
Figure 39 Virtual Counters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 40 VC Expressions Syntax Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 41 Virtual Counter Creation Wizard - Step1. . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 44 Scheduler window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 45 Scheduler Browser window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8 Id:0900d8058018dbf6 E200613-01-114-V14.0I-23
User Manual (UMN)
Figure 46 Task Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 47 My Tasks List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 48 New Public Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 49 New Private Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 50 Alarm Browser window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 51 Threshold Lifecycle window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 52 Create Monitored Metric window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 53 Create Threshold Value window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 54 Monitored Period Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 55 Period Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 56 Monitored Period Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 57 Threshold Classes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 58 Thresholds Viewer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 59 PDC Types window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 60 PDC Platform window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 61 Ad-Hoc Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 62 Ad-Hoc Report Creation Wizard - Step1 . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 66 Ad-Hoc Report Creation Wizard - Step5 (General tab) . . . . . . . . . . . . 132
Figure 67 Ad-Hoc Report Creation Wizard - Step5 (Output tab) . . . . . . . . . . . . . 133
Figure 68 Ad-Hoc Report Creation Wizard - Step5 (Options tab for table reports)134
Figure 69 Ad-Hoc Report Creation Wizard - Step5 (Appearance tab for table reports)
135
Figure 70 Ad-Hoc Report Creation Wizard - Step5 (Options tab for chart reports) . .
137
Figure 71 Ad-Hoc Report Creation Wizard - Step5 (Appearance tab for chart reports)
138
Figure 72 Ad-Hoc Comparison Report window . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 73 Ad-Hoc Report Creation Wizard - Step1. . . . . . . . . . . . . . . . . . . . . . . 142
Figure 75 Expression Editor Tab window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 77 Ad-Hoc Report Creation Wizard - Step4 (General tab) . . . . . . . . . . . . 148
Figure 78 Ad-Hoc Report Creation Wizard - Step4 (Output tab) . . . . . . . . . . . . . 149
Figure 79 Ad-Hoc Report Creation Wizard - Step4 (Options tab for table reports)150
151
Figure 81 Ad-Hoc Report Creation Wizard - Step4 (Options tab for chart reports) . .
152
153
Figure 83 Nokia Siemens Networks Report Preferences window . . . . . . . . . . . . 155
Figure 84 Siemens Report Creation Wizard - Step1 . . . . . . . . . . . . . . . . . . . . . . 157
Figure 85 Nokia Siemens Networks Report Creation Wizard - Step2 . . . . . . . . . 158
Figure 86 Nokia Siemens Networks Report Creation Wizard - Step3 (General tab) .
160
E200613-01-114-V14.0I-23 Id:0900d8058018dbf6 9
User Manual (UMN)
Figure 87 Nokia Siemens Networks Report Creation Wizard - Step3 (Output tab) . .
161
Figure 88 Nokia Siemens Networks Report Creation Wizard - Step3 (Options tab for
table reports). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 89 Nokia Siemens Networks Report Creation Wizard - Step3 (Appearance tab
for table reports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
chart reports). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
for chart reports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 92 Advanced Refresh Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 93 Custom Reports list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Figure 94 Report Properties window (General tab). . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 95 Report Properties window (Output tab). . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 96 Report Properties window (Options tab for table reports) . . . . . . . . . . . 171
Figure 97 Report Properties window (Appearance tab for table reports) . . . . . . . 172
Figure 98 Report Properties window (Options tab for chart reports). . . . . . . . . . . 173
Figure 99 Report Properties window (Appearance tab for chart reports) . . . . . . . 174
Figure 100 Filter Editor window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 101 Graph Output Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 102 Table Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 103 Ad-Hoc Online Report Alarms Browser tab . . . . . . . . . . . . . . . . . . . . . 180
Figure 104 Ad-Hoc Online Report Objects Browser tab . . . . . . . . . . . . . . . . . . . . . 181
Figure 105 Online Monitor Preferences Editor window . . . . . . . . . . . . . . . . . . . . . . 182
Figure 106 Report Properties Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 107 Alarm Filter Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 108 My Reports list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 109 SPOTS SlideShow Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Figure 110 Preferences Manager General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 111 Preferences Manager Presentation Tab . . . . . . . . . . . . . . . . . . . . . . . . 191
Figure 112 Slide Editor General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Figure 113 Slide Editor Layout Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Figure 114 Slide Editor Reports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 115 Reports and Presentation Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 116 Presentation Viewer Internalized Mode . . . . . . . . . . . . . . . . . . . . . . . . 197
Figure 117 Presentation Viewer Externalized Mode . . . . . . . . . . . . . . . . . . . . . . . . 198
Figure 118 Presentation control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 119 User Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 120 About the Administration Console window . . . . . . . . . . . . . . . . . . . . . . 201
Figure 121 Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 122 Preferences Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 123 Visualization Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 124 Welcome Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 125 Feature Access Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Figure 126 Open Tasks Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 127 The Main Processes Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 128 Main Processes Monitor Non-Critical Warning . . . . . . . . . . . . . . . . . . . 207
Figure 129 Main Processes Monitor Critical Error . . . . . . . . . . . . . . . . . . . . . . . . . 207
10 Id:0900d8058018dbf6 E200613-01-114-V14.0I-23
User Manual (UMN)
Figure 130 Main Processes Monitor Completely Operational . . . . . . . . . . . . . . . . 207

Figure 131 The Active Warnings Monitoring window . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 132 SPOTS Processes Monitor window . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 133 Scheduled Tasks Monitoring window. . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 134 Scheduled Tasks Information Pop-Up menu . . . . . . . . . . . . . . . . . . . . 215
Figure 135 System Logs Monitoring window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Figure 136 Application Server Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Figure 137 Database Server Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 138 Data Collection Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Figure 139 Data Conversion Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Figure 140 Data Loading Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 141 Database Views window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 142 Processes Configuration Edition window. . . . . . . . . . . . . . . . . . . . . . . 228
Figure 143 Scheduler Configuration Edition window . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 144 SPOTS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 145 SPOTS Welcome window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 146 SPOTS object tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 147 Set of Objects window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 148 List of objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Figure 149 Virtual object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Figure 150 Expression Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 151 Object aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Figure 152 Scheduler window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Figure 153 Virtual entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Figure 154 Thresholds CSV file opened with MS Excel. . . . . . . . . . . . . . . . . . . . . 253
Figure 155 Thresholds CSV file opened with MS Excel. . . . . . . . . . . . . . . . . . . . . 258
Figure 156 Mobile core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Figure 157 STP/number portability and transport . . . . . . . . . . . . . . . . . . . . . . . . . 295
Figure 158 Radio access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Figure 159 NGN and perfect voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
E200613-01-114-V14.0I-23 Id:0900d8058018dbf6 11
User Manual (UMN)
List of Tables
Table 1 Default port assignments for all main SPOTS components . . . . . . . . . . 22
Table 2 SPOTS Database Server data types . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 3 Online Monitoring Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 4 SPOTS user-group permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 5 Menu Bar Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 6 Main Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 7 Task execution icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 8 Status Bar Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 9 Print Preview Toolbar options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 10 Reports & Presentations Browser folders . . . . . . . . . . . . . . . . . . . . . . 195
Table 11 Reports & Presentations Browser actions . . . . . . . . . . . . . . . . . . . . . . 195
Table 12 Active warnings configuration paramaters . . . . . . . . . . . . . . . . . . . . . . 209
Table 13 Statistics service configuration parameters . . . . . . . . . . . . . . . . . . . . . 218
Table 14 AWs related to validation of PM file format . . . . . . . . . . . . . . . . . . . . . 230
Table 15 AWs related to validation of unknown data model . . . . . . . . . . . . . . . . 231
Table 16 AWs related to validation of the connection to EM . . . . . . . . . . . . . . . 231
Table 17 AWs related to validation of missing data for rolling counters . . . . . . . 232
Table 18 AWs related to DCM metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Table 19 dataCollectionDuration Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Table 20 dataCollectionEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Table 21 dataCollectionFiles Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Table 22 dataCollectionVolume Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Table 23 dataConnectionUnavailableEvents Metric . . . . . . . . . . . . . . . . . . . . . . 234
Table 24 dataConversionDuration Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Table 25 dataConversionErrors Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Table 26 dataConversionEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Table 27 dataConversionFiles Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Table 28 dataConversionVolume Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Table 29 dataLoadingDuration Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Table 30 dataLoadingErrors Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Table 31 dataLoadingEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Table 32 dataLoadingVolume Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Table 33 dbDetailedDataRecords Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Table 34 dbFreeSpace Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Table 35 dbHistoryDataRecords Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Table 36 dbNumberOfObjects Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Table 37 dbUsedSpace Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Table 38 emptyDataFiles Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Table 39 metadataLoadErrors Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Table 40 metadataLoadOperations Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Table 41 oraErrorEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Table 42 rejectedDataFiles Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Table 43 rtCrashEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Table 44 rtErrorEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Table 45 rtMemoryConsumption Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
12 Id:0900d8058018dbf6 E200613-01-114-V14.0I-23
User Manual (UMN)
Table 46 rtRestartEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Table 47 rtSystemConnectFailureEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . 241
Table 48 saaCrashEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Table 49 sasMemoryConsumption Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Table 50 sasRestartEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Table 51 sdsCrashEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Table 52 sdsMemoryConsumption Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Table 53 sdsRestartEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Table 54 Fields Description of the Thresholds CSV files . . . . . . . . . . . . . . . . . . 253
Table 55 Field Descriptions of the Thresholds Classes CSV files . . . . . . . . . . . 258
Table 56 SPOTS Reports commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Table 57 Report Output table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Table 58 Number of users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
E200613-01-114-V14.0I-23 Id:0900d8058018dbf6 13
User Manual (UMN)
14 Id:0900d8058018dbf6 E200613-01-114-V14.0I-23
User Manual (UMN) Reason for Update
Reason for Update

Summary:
SPOTS V14 Mobile User Manual has been updated according the following tables in
order to supply comprehensive and correct information to the user.
Details
Chapter/Section Reason for Update

5.2.10 dbloadgaps Updated information
4.8.3.1 Live Monitoring Updated information regarding Active Warnings
4.1.6.1 Creating a User Updated information
Extended Field Updated text formatting regarding Active Warnings
4.8.3.1 Live Monitoring Monitoring
4.3.1.4 Set of Objects Updated information.
4.6.1.1 Ad-Hoc Report Updated images regarding Statistical Reports
4.6.1.2 Ad-Hoc Comparison
Report
4.6.1.3 Siemens Reports
4.8.3.1 Live Monitoring
4.8.3.4 SPOTS Configuration
4.8.3.2 Statistical Reports
1.9.1.2 Aggregation with Updated information regarding Counters of type
Extrapolation of missing value MAX or MIN
4.4.1 Scheduler - Trend Analyi- Updated information regarding Execution Type with
sis Utilities a Minutely periodicity point
4.6.1.1 Ad-Hoc Report Updated information about the Expression Editor
4.8.3.1 Live Monitoring Tab.
Updated images regarding SPOTS Processes
4.8.3.1 Live Monitoring Monitor window
Updated the structure of the section regarding
SPOTS Processes Monitor window
5.2.20 mkhistory
Updated information
4.2.4 Make History window
Updated information
4.3.1.4 Set of Objects Wizard
Updated information about the Expression Editor
Tab.
1.1 Overview NSN Rebranding
4.1.6.2 Extended Fields Admin- NSN Rebranding
istration window
5.2.1 adhoc2srl Updated information regarding Public and Private
tasks.
5.2.20 mkhistory Updated information
E200613-01-114-V14.0I-23 Id:0900d80580165945 15
Reason for Update User Manual (UMN)

4.2.4 Make History Window Updated information
5.2.20 mkhistory Updated information
1.9.1.2 Aggregation with Updated information
Extrapolation of missing values
4.7.3 Slide Editor Updated information
4.1.1 Node Configuration NEs abbreviation fixed
window
4.6.1.3 Siemens Reports Updated information regarding DTEVL reports
5.2.1 adhoc2 NSN rebranding
5.2.29 userManagement New chapter
1.3 SPOTS Ports Updated information regarding SNS_PORT value
configuration
4.3.1.3 Creating a User Updated information

Extended Field
5.2.10 dbloadgaps Updated text formatting regarding dbloadgaps.cfg
content
4.1.1 Node Configuration Updated information
window
4.1.2 Software Version window Updated information regarding removing software
process
4.8.3.1 Live Monitoring Updated text formatting regarding
log4j_activewarningsproxy.properties file editing
4.8.3.2 Statistical Reports Updated information regarding Data Statistics
5.1.1 Threshold CSV Files Updated information regarding threshold import
process
5.2.21 reporter Updated information regarding -m parameter
5.2.29 userManagement Deleted chapter
2.9 Online Monitoring Updated information
4.8.3.1 Live Monitoring Updated information regarding Active Warnings for-
warding configuration
4.9.2 Considerations regarding New chapter
SPOTS services
4.5.5 PDC Types window Updated information regarding Upgrade Agents
5.1.1 Threshold CSV Files Updated information regarding possible filtering of
Threshold CSV Files
4.5.1 Alarm Browser window Updated information and note added regarding dif-
4.6.2.4 Alarm Filter Editor ferences between Alarm Browser and Alarm Filter
window Icon
Notes added regarding differences between Alarm
Filter Editor Icon and alarm Browser
16 Id:0900d80580165945 E200613-01-114-V14.0I-23
User Manual (UMN) Reason for Update

4.6.2.4 Alarm Filter Editor Note added regarding usage of Filter Condition field
window
4.6.1.1 Ad-Hoc Report Updated screenshots
4.8.1 Login Window Updated information in bullet “Remember me on this
computer”
3.2.1 Login window Added note at the end of the chapter
4.6.1.3 Siemens Reports Replaced all Siemens Reports references with

Nokia Siemens Networks Reports.
4.9 Best Practices Added chapter
3.2.4 Object Filtering Updated information under Set Filter.

4.5.2.2 Create Threshold Value Updated information under Cross Information.
4.5.2.1 Create Monitored Metric Added note in Select the Use Reference Counter
window bullet.
4.6.1.1 Ad-Hoc Report Updated information regarding Microsoft Excel
option in step 5 of the General tab.
Issue History
Issue Number Date of Issue Reason for Update

01 November/2007 First issue.
02 November/2007 Updated information in
chapters 4.8.3.1 and5.2.10
03 November/2007 Updated information in
chapters 4.1.6.1 and 4.8.3.1
04 December/2007 Updated information in
chapters 4.3.1.4, 4.6.1.1,
4.6.1.2, 4.6.1.3, 4.8.3.1, 4.8.3.4
and 4.8.3.2
05 January/2008 Updated information in 1.9.1.2,
4.4.1, 4.6.1.1, 4.3.1.4, 4.8.3.1,
5.2.20 and 4.2.4
06 Febuary/2008 NSN Rebranding in whole doc-
ument, made changes in 1.1,
4.1.6.2, 5.2.1, 5.2.20
07 Febuary/2008 Updated information in 4.2.4 &
5.2.20
08 March/2008 Updated information in 1.9.1.2
and 4.7.3
E200613-01-114-V14.0I-23 Id:0900d80580165945 17
Reason for Update User Manual (UMN)
Issue Number Date of Issue Reason for Update

09 May/2008 Updated information in 4.1.1,
4.6.1.3 and 5.2.1
10 June/2008 5.2.29
11 July/2008 Updated information in 1.3,
4.3.1.3 and 5.2.10
12 September/2008 5.2.29 deleted
Updated information in 4.1.1,
4.1.2, 4.8.3.1, 4.8.3.2, 5.1.1,
5.2.21
13 April/2009 Updated information in chapter
2.9
14 September/2009 Updated information in chapter
4.8.3.1
15 October/2009 Added chapter 4.9.2
16 December/2009 Updated information in chapter
4.5.5
17 February/2010 Updated information in chapter
5.1.1
18 March/2010 Updated information in 4.5.1
and 4.6.2.4
19 June/2010 Updated information in 4.6.2.4
20 September/2010 Updated information in 4.6.1.1
21 November/2010 Updated information in 4.8.1
22 February/2011 Updated information in 3.2.1,
4.6.1.3 and 4.9
23 March/2011 Updated information in 3.2.4
24 September/2011 Updated information in 4.5.2.2
25 October/2011 Updated information in chapter
4.5.2.1.
26 December/2011 Updated information in chapter
4.6.1.1
18 Id:0900d80580165945 E200613-01-114-V14.0I-23
User Manual (UMN) Introducing SPOTS
1 Introducing SPOTS
1.1 Overview
SPOTS: Support for Planning, Operation & Maintenance and Traffic Analysis
System
SPOTS is a network performance management solution by Nokia Siemens Networks.
The SPOTS performance management family is composed of the following elements.
Figure 1 SPOTS Elements

This User Manual provides information on the SPOTS Client (SCL) application, which
comprises the Trend Analysis and Online Monitoring functional components. The
Trend Analysis component comes as a standard functionality of the SPOTS perfor-
mance management solution. It provides all basic setup utilities and performance mon-
itoring capabilities. The Online Monitoring component is available as an optional
package. It provides more thorough real-time network performance monitoring.
1.2 Architecture
SPOTS is a three-tier scalable architecture, comprising the following main functional
components:
• SPOTS Performance Management Client (PMC)
The Performance Management Client implementing the Graphical User Interface.
SPOTS PMC is referred to throughout the customer documentation as SPOTS
Client.
• SPOTS Performance Management Server (PMS)
The Performance Management Server includes:
– SPOTS Application Server (SAS) implementing all application business logic.
– SPOTS Database Server (SDS) providing the traffic measurement data
storage.
Both the SPOTS Trend Analysis and Online Monitoring elements have specific func-
tional components, grouped into installable software packages:
• The default SPOTS Trend Analysis software package comprises the SPOTS PMS
and SPOTS PMC functional components.
• The optional SPOTS Online Monitoring software package comprises SPOTS
Threshold Administration Server (TAS), SPOTS Monitor Agency (MA), SPOTS
SNMP Alarm Agent (SAA) and SPOTS Client Online Monitoring functional compo-
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 19
Introducing SPOTS User Manual (UMN)
nents (the latter functionality is built-in to SPOTS PMC and enabled via Licensing
(see Licensing)).
Regardless of the chosen installation type, the SPOTS PMC (Trend Analysis and Online
Monitoring) and MA can be installed on any Solaris or Windows workstation across the
network, from where the server host is accessed.
Currently two configuration types are available, the Single Server and Multiple Server
configurations.
Single Server Installation

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,
remotely accessing the server.
SPOTS single server installation layout can be described by the diagram in Figure 2 (in
this example the displayed Network Management System is the SwitchCommander):
Figure 2 SPOTS Single Server Architecture

During installation, the various SPOTS PMS components are configured to register
themselves on the SPOTS Naming Server (SNS), using the default TCP/IP port
numbers.
The SPOTS PMC can be configured to connect to the SNS component by specifying:
• the FQN of SPOTS Server (for example "spotspms.nsn.de");
• the TCP/IP Port number of the SNS (for example "19980").
After installing SPOTS software, in order to enable its intended functionality, you must
perform several configuration tasks (please refer to Initial Configuration (see Initial Con-
figuration)).
Multiple Server Installation

A multiple server installation allows SPOTS to handle large sized networks. This can be
achieved by:
• distributing traffic data through various SPOTS Database Servers;
• distributing report processing load by several SPOTS Application Servers.
20 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
Based on this approach, it is suggested to distribute the whole network load through
various management domains or regional centers and, for each center to distribute load
through dedicated SASs and SDSs. For a typical layout of a multiple server installation,
please refer to the Domains (see Domains) chapter.
A national management center from where all network information is available may be
created, allowing network wide performance analysis. It is also possible to create a hier-
archy of regional management centers with the responsibility of collecting traffic data
and perform analysis for the nodes within the scope of the region. In all management
centers it is possible to install the complete set of SPOTS PMS components, in the same
system or distributed across various servers, thus distributing system load.
SPOTS Naming Server (SNS) registers all network components’ unique addresses,
allowing only one SNS component to exist in a multiple server configuration.
g For demo or field trial purposes it is possible to install SPOTS PMC on the same SPOTS
PMS system. However this configuration is not recommended for normal operation envi-
ronment due to bottlenecks in performance.
Online Monitoring Distributed Server Installation

SPOTS Online Monitoring system installation in a distributed environment needs to
follow these rules:
• For each SAS installation, there must be a TAS installed on the same machine. The
SAS/TAS machine carries all monitoring processing load, threshold analysis, alarm
triggering, among others, associated with the traffic data loaded by its SAS (that is
by loader command executions performed on the machine).
• For each TAS/SAS pair, the Online Monitoring PMC functionality uses a single SDS
to store the Online Monitoring specific configuration data. If more than one SDS is
being accessed by the SAS, the Online Monitoring PMC uses only one of them. The
SDS can be located on another machine.
• A global installation reachable by all Online Monitoring PMC needs to exist. The
PMC uses the SNS to establish connection to the selected SAS/TAS.
• On each TAS/SAS machine, the MA package must also be installed. You need to
use the Online Monitoring PMC to register Monitor Agencies (MA) and their Monitor
Agents responsible for handling the data for this SAS. Monitor Agents need to be
configured to send alarms to the correct primary domain.
After the TAS has been correctly installed the MA sends the alarms to the corresponding
SAS.
Users are able to login with a PMC to any TAS where they have permissions. These per-
missions are set in the SAS/TAS, so if a user has rights to login to a SAS they are also
capable of logging into its TAS counterpart.
Thresholds are configured for each TAS/SAS. This means that each RT Agent only gen-
erates alarms for thresholds defined in the TAS where it was registered.
g In Online Monitoring, alarms generated on a given cluster are visible only to users of that
cluster.
1.3 SPOTS Ports

Every SPOTS component must know in which port SPOTS Naming Server is listening
for new connections.
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 21
Since the SNS port is known by every SPOTS component, it can be used as reference
to a port interval that is known to all SPOTS components, and desirably complies with
the IANA Private Ports range which is from 49152 through 65535.
All SPOTS components then configure their initial ports within a well defined interval
relative to the SNS port.
A port span of 1024 for the entire universe of SPOTS components is sufficient. The
entire SPOTS port interval should be distributed according to the specific needs of
SPOTS components. Once this distribution is defined, it should be kept as stable as pos-
sible.
An administrator may modify certain system ports to better accommodate their setup,
and these are made using the local configuration files. Altering a specific system port is
accomplished by specifying a new absolute port for use, and this value overrides the
default (SNS_PORT + system_offset) value.
g You can modify the default value by using the following command:
$ export SNS_PORT=<value>
If the ports (or port range) assigned by the administrator fall outside the IANA authorized
range, then the corresponding system logs a warning stating that it is currently using a
non standard port. If the port specified is within authorized range but not the default port,
an information level message shall be logged instead. Default port and port ranges do
not issue any specific log message.
The following table describes default port assignments for all main SPOTS components.
Component Port Range

SNS 50000
SAS sns + 1
SDS sns + 2
RT APM sns + 5 ~ sns + 10
RT Manager sns + 11 ~ sns + 60
RT Monitor sns + 61 ~ sns + 70
RT Agency Launcher sns + 71 ~ sns + 80
RT Agency sns + 81 ~ sns + 100
SPOTS CLI Clients sns + 101 ~ sns + 300
SPOTS GUI Clients sns + 301 ~ sns + 600
SPOTS Active Warnings Proxy sns + 1000
SAS Events Gateway sns + 1024
SPOTS ORA Listener 1521
SAA - SNMP Requests 161
SAA - SNMP Traps 162
SPOTS Admin console 22; 80
Table 1 Default port assignments for all main SPOTS components
22 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
Component Port Range

Collectors 21; 22; 60000; 50600-50700
Table 1 Default port assignments for all main SPOTS components (Cont.)
1.4 Technology Plug-Ins

Due to the wide range of telecommunication protocols handled by SPOTS (for example
PSTN, PLMN / GSM, UMTS, ATM, IP, among others) the product is divided into two ele-
ments:
• The first element of the SPOTS performance management solution are the core
applications SPOTS PMS and PMC. They provide all executable and user interfaces
of the processing framework and are independent of any particular network technol-
ogy.
• The second element is the set of special libraries, Technology Plug-Ins (TP), that are
installed according to the exact network nodes being managed. TPs are specific to
each equipment version and provide the information of the associated Measurement
Types and Pre-Defined Reports.
TPs allow the SPOTS performance management solution to be tailored to the specific
network being managed. TPs can also be constantly updated to more recent versions
or, if required, completely removed from SPOTS.
TPs are available individually from Nokia Siemens Networks and each comprises the
following elements:
• Metadata
Provides the associated specification for Object Classes, Measurement Types,
Counters
• Data Loaders
Allow the transfer and conversion of the respective measurement files into Siemens
Performance File (SPF) format.
• Pre-Defined Nokia Siemens Networks Reports
Allows you to make ready-made statistical analysis reports on the specific network
node. For more information, please refer to Nokia Siemens Networks Reports (see
Nokia Siemens Networks Reports).
Detailed information on the measurements and counters supported can be found in the
Metadata Help (see Metadata Help).
g For more information on installing, upgrading or deleting a specific TP, please refer to
the corresponding Technology Plug-In Help
1.5 Domains
A network management domain is a logical entity that denotes a group of network ele-
ments. A domain can also group other network domains, called sub-domains
The concept of domain is useful for two complementary purposes:
• Allowing the distribution of measurement data and processing demands across
multiple systems.
• Restricting of the network view for the users.
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 23
Figure 3 Network Partitioning Example

Figure 3 shows a typical partitioning of a network in three network domains. The Middle
domain is itself partitioned in two sub-domains: MiddleE and MiddleW.
There are two different types of domains:
• Primary Domain
Primary domains are directly associated to a SPOTS Database Server (SDS). All
nodes associated to the primary domain or to any contained sub-domain, are regis-
tered in the primary domain's associated SDS. Each SDS can only have one asso-
ciated primary domain.
• Domain
A normal domain does not have an associated SDS. A domain can be created for
organizational purposes, in order to group nodes by type. However, the nodes and
their measurement data are registered in the primary domain that contains the asso-
ciated domain. A domain can also group primary domains, as seen in the above
diagram.
The hierarchical organization of domains forms a network tree. The network tree is kept
in a network domain configuration file in SPOTS Naming Server (SNS). The configura-
tion file is associated with each SAS.
A Cluster can comprise:
• A SPOTS Application Server
• At least one SPOTS Client
• And may contain a SPOTS Database Server
There is no hierarchical relation between clusters.
A cluster's SAS can have either a dedicated SDS, or it can connect remotely to another
cluster 's SDS.
24 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
Figure 4 illustrates the relation between network domains and clusters. Each cluster's
SPOTS Location Service (SLS) locates the network domain it is responsible for man-
aging, using the domain configuration file found in the SNS.
Figure 4 Relation between Network Domains and Clusters Diagram

Figure 5 shows how the above management domains tree can be physically spread
across several servers. In this example each system represents a cluster.
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 25
Figure 5 Spreading of Management Domains Example

The mapping between physical and logical distributions is specified in file domain.cfg of
each SAS system, stored in the $SPOTS_DIR directory of the SAS (please refer to
SPOTS Installation Guide, Annex 2 (Unix Environment Variables), for information on the
setting of $SPOTS_DIR and other SPOTS environment variables).
26 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
1.6 User Access Control

The access to the SPOTS Client application is conditional. Access and permissions
granted to SPOTS users are controlled by its Login window (see Login window). In
order to be granted access to the SPOTS Client application a user needs to satisfy the
following requirements.
• User registration with the SAS
You need to be registered as an operating system user (Unix) on the machine where
the SPOTS Application Server (SAS) is installed. The Unix administration facilities
should be used in order to performe tour registration. The network view provided to
you is the hierarchical network view from the corresponding SAS.
• Subscription to a user-group of the SAS
You need to be registered, according to the required permissions, to one of the fol-
lowing user-groups.
– pmadmin
You need to be registered with the "pmadmin" user-group in order to have
administration privileges.
– pmuser
You need to be registered with the "pmuser" user-group for normal user permis-
sions.
g The Unix administration facilities should be used in order to associate you to the
user-groups.
• Assigned to a Domain
You need to be assigned to a SPOTS domain. This can be achieved through the
User Domain (see User Domain window) task.
For more information about performing the above tasks, please refer to the Initial Con-
figuration (see Initial Configuration) topic.
1.7 PM Entities
From the performance management perspective, a network is a container of network
resources. These resources have the ability to generate metrics at regular intervals that
describe its characteristics in terms of traffic and performance. Performance Manage-
ment (PM) Entities can be used to extend the SPOTS reporting capabilities, by
grouping networking resources or their metrics.
The following PM Entities are available:
• Sets of Objects
Within SPOTS network resources are represented as objects. These objects can be
grouped into Sets of Objects (SOO) which are used as a macro to reference all the
objects on the contained list or to aggregate the contained objects into one virtual
entity.
• Sets of Counters
Within SPOTS all metrics related with the network resources are represented as
counters. The counters can be grouped into Sets of Counters (SOC), each being
used to reference all the counters and/or virtual counters on the contained list as one
single virtual entity.
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 27
• Virtual Counters
A Virtual Counter (VC) provides the means of establishing arithmetical relation-
ships between counters and representing them as a single entity.
The PM entities have two types of permission levels:
• Private
These entities can only be used and managed by their owners.
• Public
These entities can be used by all users but managed only by users with administra-
tion privileges.
PM Entities can be exported to or imported from a file, enabling the distribution of useful
PM Entities within a SPOTS distributed environment.
1.8 Database Organization

The SPOTS Database Server can hold the following types of data:
Log type Data description Data loading / generation method

Detailed Data Raw traffic mea- Network nodes generate traffic measurement
surement data data, typically with 15 minute sampling, which is
loaded periodically or using the Load Data (see
Load Data window) task.
It is also possible to generate Detailed Data,
based on other imported or previously gener-
ated measurement data, using the Data Aggre-
gation (see Data Aggregation window) task.
Historical Daily Totals Historical Data is generated by compressing
Data SPBH Maximum old Detailed Data to its most relevant informa-
Peaks tion (such as peaks). All data contained in this
log is generated using the Make History (see
SPBH Daily Peaks
Make History window).
Alarm Data Alarm description The performance alarms are generated by the
data SPOTS Online Monitoring functionality when
any threshold is exceeded.
Table 2 SPOTS Database Server data types
1.9 Trend Analysis
1.9.1 Data Generation

Traffic measurement data is generated by each network node installed. The traffic mea-
surement data is loaded into the SPOTS Database Server, either automatically or
manually using the Load Data (see Load Data window) task. The traffic measurement
data is then analyzed for trends in the network performance. Trend Analysis of the
traffic measurement data enables a more insightful knowledge of the network's perfor-
mance, achieving a more reliable prediction of its behavior.
28 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
1.9.1.1 Algorithms
Daily Total (DTOT)
The DTOT is the aggregated value of a counter, for an aggregation period of a whole
day (starting at midnight).
The value is evaluated according to the general rule for computing aggregated values
(The detailed counter samples, stored during a one-day aggregation period, are con-
verted into a single value). If, in the aggregation period, the percentage of existing and
valid counter data is below the minimum required by this rule, no Daily Total is regis-
tered.
SPBH (Sample at Peak Busy Hour)

The SPBH the aggregated value of a counter for an aggregation period of one hour, cor-
responding to the Peak Busy Hour (PBH) of the Reference Variable.
The value is evaluated according to the general rule for computing aggregated values
(The detailed counter samples, stored for a specified time-frame during a one-hour
aggregation period (corresponding to the Peak Busy Hour), are converted into a single
value). If, in the aggregation period, the percentage of existing and valid counter data is
below the minimum required by this rule no SPBH is registered.
For each SPOTS Measurement a Reference Variable is defined, which can be either a
raw counter or a pre-defined virtual counter.
The PBH of the reference variable is the end of the one-hour period for which the aggre-
gated value of the reference variable reaches its maximum. The PBH is aligned to a
multiple of the counter granularity in SPOTS DB; for instance, if a counter is stored with
15 minute granularity, then its PBH on a given day may occur at 00:00, 00:15, 00:30,
00:45, among others, until 23:45.
g The PBH "00:00" is considered to belong to the following day.
The PBH evaluation considers a set of consecutive data samples ending at the PBH
time, for example 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 exists
to compute 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 always below the minimum required by the above described aggregation
rules, no PBH can be determined. In this case, no SPBH is registered 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
periods within a day, then the first one-hour period is considered the PBH.
1.9.1.2 Aggregation with Extrapolation of missing values

The computation of the aggregated value, requires that valid data exists for a certain
percentage of the total number of samples that fall into the aggregation period.
This percentage is controlled by the value of the property MinimumPercentageIntegra-
tionData, defined in both the following configuration files:
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 29
• SDS configuration file sds.cfg for data calculated by SPOTS dbAggregator

command (see dbaggregator) (or the Data Aggregation task (see Data Manipula-
tion)) and the generation of historical data (SPBH and Daily Total).
• SAS configuration file sas.cfg for data computed for a report with a coarser output
granularity period than the existing data in 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 percentage
defined above, but lower than 100% (that is, some samples 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 values that exist within the aggrega-
tion 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 (that is, they are assumed not to affect 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 record samples, 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 some traffic records may carry "no data" for some coun-
ters.
Thus, for a given time period, object and measurement, aggregation may be possible
for some counters and impossible for others. (If the percentage of traffic record samples
for the measurement does not reach the minimum, then no counters can be aggregated
at all).
By default, SPOTS extrapolates missing data. The parameter that enables this extrap-
olation is present in $SPOTS_DIR/sds with the following flag:
"extrapolationDisabled= false"
To disable extrapolation, the flag should be: "extrapolationDisabled=true".If no
flag is included extrapolation is done by default.
When the extrapolationDisabled flag is altered in sds.cfg, mkhistory must be
run in order for the changes to take effect on historical results
g If the number of decimal places defined in sas.cfg Number type values assignations is
zero, then, there is a possibility of a discrepancy between the detailed 1 day and histor-
ical totals for some type of SOOs.This is due to the fact that all figures are rounded off
and, therefore, discrepancies may occur.
1.9.1.3 Aggregation without Extrapolation of missing values

In this case, the computation of the aggregated value requires only that one valid data
sample exists in the aggregation period.
The missing samples, if any, are considered to have a value of zero.
30 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
1.9.2 Data Manipulation

The traffic measurement data can be further manipulated in order to optimize the data
analysis.
Aggregation
The Data Aggregation task allows you to process the Trend Analysis detailed data into
higher granularity detailed data, modifying its sampling frequency. The Administrator
can delete the original data files after the measurement data has been processed into a
higher granularity.
The following data aggregation algorithms are available:
• Normal Measurements
Aggregates all ordinary Detailed data measurements.
• First & Interval
Aggregates all First and Interval alarm history data.
• Second Method after First Method
Aggregates all ordinary Detailed data measurements, followed by First and Interval
measurements.
Make History
The Make History task allows the Administrator to process the Trend Analysis detailed
data into a compressed log. The History log allows you to dispose of redundant mea-
surement data in the database. The sampling frequency of the History log is reduced
to one sample per 24 hours of detailed measurement data, being the selected value the
maximum recorded during the 24 hours. The Administrator can choose to delete the
original data files after the measurement data has been compressed.
1.9.3 Trend Analysis Reports

The SPOTS's performance capability is enabled by the Reporting functionality.
Reports allow the analysis of performance statistical data gathered on specific network
objects and counters. There are two main types of reporting; Trend Analysis Reports
analyze measurement data already present in the log, while the Online Monitoring
Reports provide a real-time measurement data analysis.
Trend Analysis Reports allow the analysis of previously gathered measurement data.
The measurement data is loaded using the Load Data (see Load Data window) task. A
Trend Analysis report can generate two types of on-screen output, further described
under the Report Output (see Report Output window) chapter. The following reports are
available:
Ad-Hoc Report
An Ad-Hoc Report is a basic analysis report of measurement data. The report provides
a direct reading from the measurement data database. You can create the report by
using the Ad-Hoc Report Wizard (see Ad-Hoc Report).
Ad-Hoc Comparison Report

An Ad-Hoc Comparison Report allows the direct comparison of the data from the
same measurement counter in two distinct periods of time. You can create the report by
using the Ad-Hoc Comparison Report Wizard (see Ad-Hoc Comparison Report).
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 31
Nokia Siemens Networks Reports

Nokia Siemens Networks Reports are predefined reports that allow you to make sta-
tistical analysis of specific counter measurements. They enable you to obtain industry-
standard statistical reports on every aspect of the network performance. You can create
the report by using the Nokia Siemens Networks Report Wizard (see Nokia Siemens
Networks Reports).
Custom Reports
Custom Reports are reports that are configured by you. You can manually build a
report using SPOTS Reporting Language (SRL). Similar to a typical programming lan-
guage, the report code is written and compiled using the Reports Editor. For more infor-
mation, please refer to the application's own user documentation.
1.10 Online Monitoring
1.10.1 Alarm Generation

The SPOTS Online Monitoring functionality provides the mechanisms to automatically
detect quality of service problems and alert the operator of performance degradations
within the network. This functionality significantly reduces the reaction time in the detec-
tion and solution of performance problems. SPOTS Online Monitoring complies with
Rec. ITU-T X.733 and X.739.
All performance data generated by the managed network nodes is collected via the sup-
ported NMS interfaces. Once the measurement data becomes available it is loaded into
the SPOTS Database Server and forwarded to SPOTS Monitor Agencies.
Monitor Agencies and Agents

For each PDC server supported, a SPOTS Monitor Agency is required to be in place.
These MAs are the support platforms used by the SPOTS Monitor Agents to perform
its tasks. The SPOTS Monitor Agencies and Monitor Agents are monitored and
managed through the SPOTS Client Online Monitoring functionality. SPOTS Monitor
Agencies can be created using the PDC Platform (see PDC Platform window) task.
The SPOTS Monitor Agents are software agents that are loaded into SPOTS Monitor
Agencies to monitor counters’ measurement data for alarm conditions. The Agents are
responsible for issuing an alarm when a threshold is crossed and for sending an alarm
clear notification when the threshold is crossed in the opposite direction. SPOTS
Monitor Agents can be created using the PDC Types (see PDC Types window) task.
Threshold Administration
Threshold Values with different severities are assigned to Monitored Metrics;
whenever the observed value of the Monitored Metric crosses one of its Threshold
Values, an alarm is generated. The threshold conditions and their properties can be
created using the Threshold Lifecycle (see Threshold Lifecycle window) task.
There may be more than one Threshold assigned to one counter at a time, each with a
different severity. There are four different threshold severities (WARNING, MINOR,
MAJOR and CRITICAL). Threshold Classes enable you to separate network objects
into different classes and to apply a different set of thresholds to each of those classes.
Threshold Classes can also restrict the monitoring of certain counters by adding them
32 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
to the default threshold class 'Black List'. Threshold Classes can be defined using the
Threshold Classes (see Threshold Classes window) task.
Monitored Periods can be associated with each Threshold Value, defining the period
of the day when the threshold condition is active.
Daily time intervals (Monitored Periods) are associated with each Threshold Value,
defining the period of the day when the alarm mechanism is active.
SPOTS Online Monitor provides support for the administration of Threshold and Filter
values. Each threshold is assigned to a measurement counter and contains at least one
of the following attributes:
• Threshold level
• Severity of the Threshold
• Threshold cross direction
• Threshold clear level
• Associated Object Class
• Associated Measurement Counter
• Associated Threshold Class
There may be more than one Threshold assigned to one counter at a time, each with a
different severity.
SPOTS Online Monitoring also supports one reference counter for each counter mon-
itored. This reference counter can be assigned to a minimum value that must be crossed
to enable the alarm analysis of the monitored counter.
Agents Alarm Processing

When a threshold condition violation occurs, its respective SPOTS Monitor Agent
issues a Quality of Service (QoS) alarm. The alarm generation is based on the com-
parison of the received traffic data to the user-defined threshold levels. Once the com-
parison no longer results in a threshold violation, then an alarm clear is issued.
SPOTS Monitor Agents are software agents that are loaded into SPOTS Monitor
Agencies (MA) on the Online Monitoring Server, to perform the necessary alarm moni-
toring tasks.
One SPOTS PMS, with SPOTS Online Monitoring add-on, can collect data from several
NMSs if required by the size of the network.
For each PDC server supported, there must be one SPOTS Monitor Agency in place.
These MAs are the support platforms for SPOTS Monitor Agents to perform their tasks.
These SPOTS Monitor Agencies and Monitor Agents are components that can be mon-
itored and managed through the Online Monitoring Client.
SPOTS Monitor Agents are responsible for issuing an alarm when a threshold is crossed
and for sending an alarm clear notification when the threshold is crossed in the opposite
direction.
Additionally they create a file containing all the issued user-defined QoS alarms. This
alarm log.SPF file can be loaded into SPOTS PMS database to prevent loss in alarm
on-line transmission.
The following table outlines the actions taken by SPOTS Online Monitoring Alarm Agent
based on the alarm state on the last and current monitoring periods for each threshold
and counter association.
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 33
Alarm state on Alarm state on the Action

the last period current period
normal procedure ON ON no action
normal procedure ON OFF sendClear
normal procedure OFF ON sendAlarm
normal procedure OFF OFF no action
exceptional procedure ON NO DATA (2) no action
exceptional procedure OFF NO DATA (2) no action
exceptional procedure ON NO THRESHOLD (3) sendClear
exceptional procedure OFF NO THRESHOLD (3) no action
exceptional procedure NO DATA (1) ON sendAlarm
exceptional procedure NO DATA (1) OFF no action
Table 3 Online Monitoring Actions
(1) When a counter is monitored for the first time (a new threshold is created) there is
no alarm state for that threshold and counter association on the last period.
(2) When performance data is no longer received for a monitored counter (for example,
an unplugged interface card) the Alarm Monitor Agent’s alarm state for that threshold
and counter association remains until data is received again. The alarm condition may
be manually cleared outside the Monitor Agents system, in SPOTS PMS Alarm
Browser.
(3) If a counter is no longer in the set of the monitored counters (a threshold was
deleted), and its alarm state was ON before, then an alarm Clear is issued.
1.10.2 Online Monitoring Reports

The SPOTS's performance management ability is achieved by its Reporting function-
ality. Reports allow the analysis of performance statistical data gathered on specific
network objects and counters. There are two main types of reporting; Trend Analysis
Reports analyze measurement data already present in the log, as Online Monitoring
Reports provide real-time measurement data analysis.
Online Monitoring Reports provide real-time measurement data analysis and alarming
functionality. The following report is available.
Ad-Hoc Online Reports

An Ad-Hoc Online Report constantly monitors specific enabled counters. The real time
monitoring is displayed in the Ad-Hoc Online Report window. The window also
provides a log displaying the alarm’s history.
1.11 SNMP Alarm Agent

SPOTS performance alarms can be forwarded via SNMP interface to fault management
or graphical information systems (for example HP´s OV TeMIP or Micromuse Netcool)
for integrated fault management.
34 Id:0900d805801b1cbf E200613-01-114-V14.0I-23
This allows a seamless integration in the fault management process. The performance
alarms are handled in the Fault Management application (for example notified via Map
topology or Alarm browser).
Figure 6 SPOTS SNMP Interface

Forwarding of alarms to external FM OS applications, as SNMP traps, includes:
• Flexible user-defined filtering criteria for selecting the alarms to be forwarded.
• Resynchronization of the pending performance alarms status.
• Manual deletion of pending performance alarms.
1.12 Extended Fields

The Extended Fields are configuration attributes, for instance, CellD, LACode,
MPType, among others, associated to counters and network resources.
These attributes are displayed for each instance (counters and resources) in the selec-
tion tables in additional columns other than Name and User Label columns. They can
also be accessed through the database views or via SRL reporting language (see Trend
Analysis Reports).
The Extended Fields provide important information regarding each instance which
grants you easy and quick selection of the required instances when creating sets of
counters, reports, among others.
For more information regarding the Creation of User Extended Fields, please see
Creating a User Extended Field.
g The Extended Fields' values coming from external data sources can be updated period-
ically via the SAS dbloader command (see dbloader).
E200613-01-114-V14.0I-23 Id:0900d805801b1cbf 35
Initial Configuration Tasks User Manual (UMN)
2 Initial Configuration Tasks
2.1 Initial Configuration

In order to enable the SPOTS Client functionality, the following elements need to be
configured:
Licensing
You need to provide the necessary licenses in order to enable each SPOTS Client func-
tionality. For more information, please refer to the Licensing (see Licensing) topic.
User-Group Creation
User-Groups need to be created within which users are grouped according to their per-
missions. For more information, please refer to the User-Group Creation (see User-
Group Creation) topic
User Creation
Individual users need to be allocated a unique username and password so SPOTS
Client can accuratly identify each person accessing the system. For more information,
please refer to the User Creation (see User Creation) topic.
Domain Creation
Each individual user needs to be associated to a domain. For more information, please
refer to the Domain Creation (see Domain Creation) topic.
Data Collection Configuration

The data collection and loading process defines how the performance data, generated
by the network elements, is transferred to the SPOTS server and loaded into the data-
base. Only then can any network performance report be created. For more information,
please refer to the Data Collection Configuration (see Data Collection Configuration)
topic.
Automatic Node Creation

Network Nodes are automatically recognized by SPOTS to allow a quick installation of
all Network Elements. For more information, please refer to the Automatic Node
Creation (see Automatic Node Creation) topic.
Automatic Node Migration

The Software Version of SPOTS Network Nodes can be automatically changed by
SPOTS, allowing a quick migration of all the equipment to new software versions. For
more information, please refer to the Automatic Node Migration (see Automatic Node
Migration) topic.
2.2 Licensing
Licensing enables users to obtain a network performance management solution that is
tailored to their exact needs, by enabling and disabling tasks. The Licence for each
chosen feature needs to be activated upon installation by entering a character string.
The access to the following tasks is controlled by licensing:
36 Id:0900d80580165949 E200613-01-114-V14.0I-23
User Manual (UMN) Initial Configuration Tasks
• SPOTS Client access

Providing the respective license, access to SPOTS Client and its basic tasks is
granted.
• Online Monitoring functionality
Providing the respective license, access to the real time SPOTS tasks is granted.
• SPOTS SNMP Alarm Agent functionality
Providing the respective license, access to the Alarm Agents is granted.
• Web Reports functionality
Providing the respective license, Web Reports are enabled.
• Backup and Restore (BAR) functionality
Providing the respective license, the Backup and Restore tasks are enabled.
• MultiVendor functionality
Providing the respective license, the MultiVendor compatibility is enabled.
• TP installation
Each TP and its related Nokia Siemens Networks Reports can be activated by
providing its respective license.
g Before attempting to run SPOTS Client, make sure that the necessary licence strings
have been ordered and are installed. Installation of licenses is a step of the normal
SPOTS installation procedure described in SPOTS Licensing Software section of
SPOTS Installation Guide. Throughout this Manual, licensing support enabling SPOTS
full functionality is assumed.
2.3 User-Group Creation

User-Groups allow the grouping of users according to their permissions. The two follow-
ing user-groups exist:
• pmadmin
You must be registered with the "pmadmin" user-group in order to have administra-
tion privileges.
• pmuser
You must be registered with the "pmuser" user-group for normal user permissions.
The specific permissions associated with each group are outlined in the following table:
Functionality Normal User Administrator

Perform Node Administration No Yes
Import Traffic Data No Yes
Delete Traffic 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
Table 4 SPOTS user-group permissions
E200613-01-114-V14.0I-23 Id:0900d80580165949 37
Functionality Normal User Administrator

Manage others Scheduled Tasks No No
Table 4 SPOTS user-group permissions (Cont.)
The Unix administration facilities must be used in order to associate you and all the
users to the user-groups.
2.4 User Creation

A user name must be allocated to each individual user so SPOTS Client can accuratly
identify each person accessing the application.
In order to login to SPOTS Client you must be also registered as an operating system
user (Unix) on the machine where the SPOTS Application Server (SAS) is installed.
After installing the SPOTS Client, no users are defined.
You must login for the first time with the administrator login of the Unix OS. The Unix
administration facility is used to register new users.
It is also necessary to assign each user to one particular domain. This can be performed
using the User Domain (see User Domain window) task.
g The user access control configuration is specified in the users.cfg file, stored in
$SPOTS_DIR and kept in each SAS (please refer to the Unix Environment Variables
section of SPOTS Installation Guide, Annex 2, 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 its contained Sub-
domains. This information is provided to the SNS by each SAS, as part of the domain
configuration.
2.5 Domain Creation

Domains allow sectioning of the network, ensuring minimal interdependency.
Every user must be associated to one network domain. After installing the SPOTS
Client, only the default Root domain exists. The hierarchical dependence of domains
can be illustrated by the following diagram:
Figure 7 Hierarchical Domain Diagram

There are two different types of domains:
• Primary Domain
Primary domains are directly associated to a SPOTS Database Server (SDS). All
nodes associated to the primary domain or to any contained sub-domain, are regis-
tered in the primary domain's associated SDS. Each SDS can only have one asso-
ciated primary domain.
38 Id:0900d80580165949 E200613-01-114-V14.0I-23
• Domain
A normal domain does not have an associated SDS. A domain can be created for
organizational purposes, in order to group nodes by type. However, the nodes and
their measurement data are registered in the primary domain that contains the asso-
ciated domain. A domain can also group primary domains, as seen in the above
diagram.
You can perform all domain configuration tasks using the Domains Configuration (see
Domains Configuration window) task.
It is also necessary to associate each user to one domain. This can be performed using
the User Domain (see User Domain window) task.
g In order to minimize the interdependency of the network resources, it is advisable to plan

the sectioning of the network resources into domains. The organization of the network
via domains does not imply that its sectioning should follow the physical network layout,
but in a way that you find coherent with its operation.
When the network domain’s configuration is complete, the SAS automatically restarts in
order to load the new configuration and update SPOTS Naming Server (SNS).
The SAS can be manually rebooted using the spotsshutdown -r command line.
2.6 Data Collection Configuration

In order to be able to create reports with SPOTS Client, the traffic measurement data
from each node must be loaded into the SDS. This is achieved by the "data collection"
and “data loading" automatic processes.
The data collection and loading processes are configured during the Technology Plug-
In (TPs) installation (please refer to each Technology Plug-In Help for a detailed
description of the configuration steps of the data collection and loading).
Traffic measurement data can also be manually loaded using the Load Data (see Load
Data window) task.
2.7 Automatic Node Creation

Automatic node creation enables SPOTS Client to automatically recognize the con-
nected network nodes. This allows you to skip the repetitive creation of nodes using
SPOTS Client. The automatic creation of a specific node is triggered by the first mea-
surement data upload from that specific node.
The node version information is available in the nodes_creation.cfg file, stored in
$SPOTS_DIR (please refer to the Unix Environment Variable section of SPOTS Instal-
lation Guide Annex 2, for information on the setting of $SPOTS_DIR and other SPOTS
environment variables).
When a required node does not have a corresponding list entry, it can be manually
created using SPOTS Client (Please refer to Network Administration). In the following
example, all nodes of type EXCHOC are created upon data upload from the version
CS10 and has an installation date of 2001/09/01.
# File: nodes_creation.cfg
# Automatic Nodes Creation Configuration File
#
# Line Syntax: NodeType;VersionName;Date
E200613-01-114-V14.0I-23 Id:0900d80580165949 39
#
EXCHOC;CS10;2001/09/01
To disable the particular node it is necessary to comment the definition line, inserting a
'#' in the beginning of the text line.
# Automatic Nodes Creation Configuration File
#
# Line Syntax: NodeType;VersionName;Date
# EXCHOC;CS10;2001/09/01
2.8 Automatic Node Migration

Automatic node migration enables SPOTS Client to automatically recognize changes on
the software version of network nodes. This allows you to skip the repetitive task of
changing the software version of specific nodes using SPOTS Client. The automatic
software version migration of a specific node is triggered by the first measurement data
upload from that node where the software version upgrade has occurred.
The node versions migration rules are available in the nodes_creation.cfg file, stored in
$SPOTS_DIR (please refer to the Unix Environment Variable section of SPOTS Instal-
lation Guide Annex 2, for information on the setting of $SPOTS_DIR and other SPOTS
environment variables).
When the required node does not have a corresponding list entry, its software version
can be manually changed using the SPOTS Client (Please refer to Network Administra-
tion).
The Line syntax for automatic node migration is the following:
NodeType;CurrentVersionMask;NewVersion
Where:
NodeType represents any of the installed SPOTS node types.
CurrentVersionMask represents the node's current software version. WildCards
such as '*' and '?' are accepted.
NewVersion represents the target software version.
In the following example, all nodes of type EXCHOC with version CS10, CS11, among
orhers, automatically migrates to version CS21 upon upload of data generated by the
CS21 software version. The node’s new software version installation date is set to the
first uploaded CS21 measurement’s date.
# Automatic Nodes Creation and Migration Configuration File
#
# Line Syntax for Nodes Creation: NodeType;VersionName;Date
# Line Syntax for Nodes Migration:
NodeType;CurrentVersionMask;NewVersion
#
EXCHOC;CS1*;CS21
40 Id:0900d80580165949 E200613-01-114-V14.0I-23
2.9 Online Monitoring

After enabling the SPOTS Online Monitoring functionality, the following configuration
steps must be performed:
Create SPOTS Monitor Agencies
You must create and register the SPOTS Monitor Agencies at the hosts where the
Monitor Agents collects the performance data. After successfully creating the agen-
cies, you must initialize them. SPOTS Monitor Agencies can be created using the PDC
Platform (see PDC Platform window) task.
Create SPOTS Monitor Agents
You must create SPOTS Monitor Agents that collects the data and assign them to the
respective network management domain. SPOTS Monitor Agents can be created using
the PDC Types task.
Create Thresholds
To receive user-defined QoS Alarm events you need to create the associated threshold
conditions. The threshold conditions and their properties can be created using the
Threshold Lifecycle (see Threshold Lifecycle window) task.
E200613-01-114-V14.0I-23 Id:0900d80580165949 41
User Interface User Manual (UMN)
3 User Interface
3.1 Interaction and Operation
3.1.1 User Interaction

You can interact with the Graphical User Interface in two distinct ways:
3.1.1.1 Mouse
The left and right mouse buttons are used to interact with the SPOTS GUI in the follow-
ing ways:
• Left mouse button
Click for item selection
Double-Click for task execution
• Shift + Left mouse button
Multiple item selection
• Ctrl + Left mouse button
Add item to selection list
• Rigth mouse button
Open context menu
The SPOTS general GUI layout is described in SPOTS Main Window (see SPOTS
Main Window) topic.
3.1.1.2 Keyboard
The keyboard allows you to type any text field name required, as well as providing short-
cuts to some of the most frequently used tasks:
• Press F1 to open the currently selected task's SPOTS Online Help related topic.
• Press F2 to open the Ad-Hoc Report window (see Ad-Hoc Report), pre-configured
to chart reports.
• Press F3 to open the Ad-Hoc Report window (see Ad-Hoc Report), pre-configured
to table reports.
3.1.2 Operation Modes

SPOTS tasks are performed in two distinct operation modes.
3.1.2.1 Interactive
You can interact with SPOTS by using its Java based Graphical User Interface. All
general tasks are available via the GUI, conferring SPOTS great ease of use. The
SPOTS general GUI layout is described under SPOTS Main Window (see SPOTS
Main Window) topic.
42 Id:0900d8058016594b E200613-01-114-V14.0I-23
User Manual (UMN) User Interface
3.1.2.2 Scheduled
You can schedule some of SPOTS most frequently used tasks, allowing a more efficient
and effortless operation. The following tasks can be scheduled using SPOTS Scheduler
task:
• Data loading, using the Load Data window (see Load Data window).
• Data deletion, using the Delete Data window (see Delete Data window).
• Aggregating data, using the Data Aggregation window (see Data Aggregation
window).
• Making a history log, using the Make History window (see Make History window).
• Running Trend Analysis data reports, using the Ad-Hoc Report window (see Ad-
Hoc Report).
3.2 Getting Started
3.2.1 Login window

The Login window can be accessed via:
> Start menu > Programs folder > SPOTS folder > SPOTS PMC menu item
The Login window allows the identification of each user, upon attempting to start a
SPOTS Client session.
Figure 8 User Login window

The window has the following fields:
• User Name
In this field your identification is entered.
For more information on the requirements of a valid SPOTS user, please refer to
User Access Control (see User Access Control) topic.
• Password
In this field you must enter the password associated to the username entered above.
The Password field is case sensitive.
• Remember this User Name and Password
Select the check box to activate the storage of username and password information,
enabling the automatic login the next time the SPOTS Client is opened.
The User Login window has the following buttons, located at the bottom of the window:
• Click OK to attempt to start a session in SPOTS Client with the entered user infor-
mation.
• Click Cancel to abort the user login and close the SPOTS Client application.
E200613-01-114-V14.0I-23 Id:0900d8058016594b 43
g When SPOTS Client is installed under the Unix OS, the login window can be opened by
running the spots command located under directory: </opt/spots-pmc>
g In order to overwrite the Use Stored Login option, without accessing SPOTS Prefer-
ences, you must execute SPOTS Client in the OS command prompt using the following
command: spots -l
g If the message "Application Server is still initializing" is shown it means that SPOTS
server is still initializing. You must wait for a while and retry the login.
3.2.2 SPOTS Main Window

The SPOTS main window is a Multi-Document Interface (MDI) based Graphical User
Interface (GUI), allowing you to perform several task instances simultaneously.
Figure 9 SPOTS Main Window
3.2.2.1 Menu Bar

Figure 10 shows SPOTS Main window Menu Bar with its menu items. When you click
one of these menu items, the pull-down menu specific to the menu item opens.
Figure 10 Menu Bar

Table 5 shows and briefly explains the available pull-down menus on SPOTS main
window.
44 Id:0900d8058016594b E200613-01-114-V14.0I-23
SPOTS
New Ad-Hoc Report Opens the Ad-Hoc Report window pre-configured to Chart or Table reports.
Open Launches the selected task.
Remove Removes the selected task-tree item.
Close Closes the currently active window.
Reports Editor ... Opens the Reports Editor window.
Clear History Clears the contents of the History Log field.
Preferences Opens the Preferences window for program and settings configuration.
Exit Closes SPOTS Client.
View
Toolbar Opens the Toolbar.
Tree Displays or hides the Task Tree.
History Displays or hides the History Log.
Window
Cascade Organizes windows in cascading order.
Title Horizontally Displays windows in a horizontally tiled order.
Title Vertically Displays windows in a vertically tiled order.
Help
Help Topics Opens SPOTS Online Help.
What’s This? Opens the selected window's relevant Online Help topic.
How To Use Help Opens the Online Help topic explaining how to use the in-system help
resource.
Metadata Help Opens the Metadata Help window, which provides an overview of the
installed network objects.
About Spots Provides information about SPOTS Client version.
Table 5 Menu Bar Entries
3.2.2.2 Toolbar
The Toolbar (see Main Toobar buttons) runs along the top edge of the main window
above the working area. Clicking on one of these buttons provides quick and easy
access to certain frequently used functions.
E200613-01-114-V14.0I-23 Id:0900d8058016594b 45
Figure 11 Main Toobar buttons

The functions of the main window toolbar buttons are briefly described in Table 6.
Icon Function Menu Entry Opens

Window
Open the Ad-Hoc Report pre- SPOTS menu > New Ad- Ad-Hoc
configured to chart reports. Hoc Report > Graph Report
entry
Open the Ad-Hoc Report pre- SPOTS menu > New Ad- Ad-Hoc
configured to table reports. Hoc Report > Table entry Report
Launch the selected task-tree SPOTS menu > Open 1.)
item. entry
Display or hide the Task Tree. View menu > Tree entry
Display or hide the History View menu > History

Log. entry
Open the PM Monitor Online Help menu > Help Topics Online Help
Help. entry
Open the selected window Help menu > What’s Online Help
relevant Online Help topic. This? entry
Table 6 Main Toolbar Icons
g 1.) Opens several windows depending on the selected task-tree item.
3.2.2.3 Task Tree

The Task Tree displays all available tasks. Task availability may vary depending on user
permissions and installed licenses. Please refer to Licensing (see Licensing) for more
information. The Task Tree can be displayed or hidden by clicking .
3.2.2.4 Taskbar
The Taskbar provides a summary of all currently open windows, providing shortcuts to
them by clicking their respective taskbar button. If the amount of taskbar buttons
exceeds the Task Area width, arrow buttons become active. You can scroll through the
taskbar buttons by clicking the arrows.
3.2.2.5 Task Area

The Tasks Area displays all task windows. Windows may be extracted to the Operating
System environment by clicking the Externalize toolbar button where available.
46 Id:0900d8058016594b E200613-01-114-V14.0I-23
3.2.2.6 History Log

The History Log displays all logged task activity. The History Log can be displayed or
hidden by clicking . The following messages (see Task execution icons) can be dis-
played in the History Log field.
Icon Task Execution

Pending
In Progress
Failed
Stopped
Successful
Table 7 Task execution icons
3.2.2.7 Status Bar

The status bar (see Status Bar) is located at the bottom of the main window. It gives
information on the operating states and displays important messages, such as alarms,
in short form.
Figure 12 Status Bar

Table 8 describes the PM Monitor status bar from left to right.
Notification Area A short help text for the currently selected window, menu
entry or toolbar button.
Alarm Notification Area
Provides the following options by right clicking on :
Apply Filter
Activate
Deactivate
Table 8 Status Bar Components
3.2.3 Preferences window

The Preferences window can be accessed via:
> SPOTS menu > Preferences menu item
The Preferences window allows you to configure SPOTS to best suit its specific oper-
ation. In the Preferences window you can activate and deactivate features in the
Reports (see Reports Tab), Login (see Login window) and Online Monitoring (see
Online Monitoring Reports) tasks.
E200613-01-114-V14.0I-23 Id:0900d8058016594b 47
The window has the following tabs:

• General Tab
• Reports Tab
• Alarms Tab
• Calendar Tab
3.2.3.1 General Tab

This tab allows you to activate and deactivate its preferences regarding the user Login.
Figure 13 Client Preferences Editor General Tab

Login
In this field you can activate or deactivate the Use Stored Login feature.
Select the Use Stored Login check box to associate the username and password
entered in the SPOTS login window to the current Windows user account. The next time
the SPOTS application starts using the same Windows user account, the associated
username and password are automatically entered, not requiring further user identifica-
tion.
Save
In this field you can activate or deactivate the Automatic Change to View Mode After
Save feature.
48 Id:0900d8058016594b E200613-01-114-V14.0I-23
Object Instances Identification

• User Defined Label
Select the User Defined Label check box to display the object instances with the
user’s label.
• Nokia Siemens Networks Defined Label
Select the Nokia Siemens Networks Defined Label check box to display the object
instances with the Siemens label.
• Display Both Labels
Select the Display Both Labels check box to display the object instances with the
user’s and Siemens’ labels. The labels are presented to you separated by a “#”.
3.2.3.2 Reports Tab

This tab allows you to activate and deactivate automation features in the Report Wizard.
Figure 14 Client Preferences Editor Reports Tab

The window has the following field:
Wizard
In this field you can activate or deactivate the following features:
• Start Automatically
Select the Start Automatically check box to activate the automatic start up of the
Report Wizard. If this option is selected, upon launch of the Ad-Hoc Report task, the
Report Wizard is automatically opened.
• Execute Automatically
Select the Execute Automatically check box to activate the automatic execution of
a report upon exiting the Report Wizard.
E200613-01-114-V14.0I-23 Id:0900d8058016594b 49
3.2.3.3 Alarms Tab

This tab allows you to activate and deactivate different alarm warnings.
Figure 15 Client Preferences Editor Alarms Tab

Alarm Icon
In this field you can activate or deactivate the following features:
• Active
Select the Active check box to activate the alarm icon warning in the status bar. The
Status Bar is further described under SPOTS Main Window (see SPOTS Main
Window) topic.
• Enable Audio Notification
Select the Enable Audio Notification check box to play an alarm sound when an
alarm has been triggered.
• Default Filter
Select the Default Filter check box to activate the browse option and select a default
filter to be associated with the alarm.
3.2.3.4 Calendar Tab

This tab allows you to set the working days of a week. By default weekends are not con-
sidered working days.
50 Id:0900d8058016594b E200613-01-114-V14.0I-23
Figure 16 Preferences Editor window - Calendar Tab

The window (see Preferences Editor window - Calendar Tab) has the Working Days
field.
In this field you can select the working days of a week by clicking on the respective check
box.
This window has the following buttons, located at the bottom of the window:
• Click OK to save preference settings.
• Click Cancel to leave the window without changing the preference settings.
g User preferences are always associated with the current Windows user account and
stored in a file named SPOTS-PREF.ini. When several PM Monitor users use the same
Windows user account, it is not possible to save the preferences for each PM Monitor
user.
3.2.4 Object Filtering

Filtering is used in order to avoid overloading the browser with all object instances. You
may define filters to reduce the scope of the object instances for selection. This function-
ality is active in any task that requires object selection, such as any Ad-Hoc Report
Wizard and Sets of Objects Wizard (see Sets of Objects Wizard).
Filtering can be performed by using the following set of context menu items:
• Set Filter
Activates filtering for the selected items in the Instances list. Default rule is “=” and
the default value is “INSTANCE_SELECTED*”. This allows you to retrieve all com-
posite instances based on the first selection. Filter selection is maintained across
objects classes. A common use case is when you select an instance called
“INSTANCE_SELECTED“ in a parent object class and can navigate to child object
E200613-01-114-V14.0I-23 Id:0900d8058016594b 51
classes to find filtered instance like “INSTANCE_SELECTED_001“,

“INSTANCE_SELECTED_002“, among others.
Figure 17 Report Wizard window - Set Filter
• Edit Filter
Allows you to extend the filter attributes, by specifying a sub-class of the object.
• Reset Filter
Deactivates the current object filtering.
3.3 Printing
3.3.1 Print window

The Print window can be accessed via:
> Print toolbar button

The Print window allows you to send a printing job to the local printer. The printer output
can be previewed in the Print Preview window and its settings can be adjusted in the
Page Setup window.
• Click OK to start the printing job.
• Click Cancel to leave the window without printing.
The Print window has the following fields:
• Printer
The Printer field allows you to select the printer to which the print job is sent. You
can select the printer from the drop-down menu and its network path is displayed.
The field also displays the Status, Type, location (Where) and any Comments
available.
You can view the selected printer properties by clicking the Properties button.
52 Id:0900d8058016594b E200613-01-114-V14.0I-23
• Print Range
The Print Range field allows you to specify which pages are to be printed. You can
select from the following options:
– All
Select the All radio button to print all pages available.
– Pages
Select the Pages radio button and specify the exact print range.
– Selection
Select the Selection radio button to print only the selected page.
• Copies
The Copies field allows you to specify the exact number of times the printing job is
repeated.
3.3.2 Print Preview window

The Print Preview window can be accessed via Print Preview toolbar button.
The Print Preview window allows you to preview the printer output on-screen, enabling
greater efficiency.
Table 9 explains the functions of the buttons located at the top of the window:
Icon Function
Opens the Print window (see Print window).
Previews one page at a time.
Previews more than one page at a time.
Zoom drop-down menu provides a selection of zoom to apply to the

Print Preview.
Provides a Full Screen of the Print Preview.
Table 9 Print Preview Toolbar options
This window has the Close button, located at the bottom of the window. Click to leave
the Print Preview window.
3.3.3 Page Setup window

The Page Setup window can be accessed via:
> Task menu > Page Setup menu item
The Page Setup window allows you to configure the page print output.
• Click OK to save preference settings.
The Page Setup window has the following tabs:
• Margins Tab
• Header / Footer Tab
E200613-01-114-V14.0I-23 Id:0900d8058016594b 53
• Paper Setup Tab
3.3.3.1 Margins Tab

This tab allows you to set the margin’s properties.
Margins
In this field you can set the space between the printed area and the paper margins. The
distance in centimeters can be specified for:
• Top margin
• Bottom margin
• Left margin
• Right margin
Orientation
This field provides two options for the printing orientation of the paper. The distance in
centimeters can be specified for:
• Portrait
Select the Portrait radio button to print the document in the upright position.
• Landscape
Select the Landscape radio button to print the document in the horizontal position.
3.3.3.2 Header / Footer Tab

This tab allows you to set the header and footer page properties.
• Header
This field allows you to type the text to be printed in the header of the page and set
its properties.
– Header from edge
This option sets the header location at the top of the page.
– Header Text
This option allows the insertion of the text to be displayed in the header.
– Header Font
This option sets the font and font size of the displayed text.
• Footer
This field allows you to type the text to be printed in the footer of the page and set
its properties.
– Footer from edge
This option sets the footer location at the bottom of the page.
– Footer Text
This option allows the insertion of the text to be displayed in the footer.
– Footer Font
This option sets the font and font size of the displayed text.
54 Id:0900d8058016594b E200613-01-114-V14.0I-23
3.3.3.3 Paper Setup Tab

This tab allows you to select the paper properties.
• Paper Size
In this field you can select the paper size using the respective drop-down menu.
Additionally the size can be set manually.
• Paper Source
In this field you can set the source to use for printing. Select the correct option from
the supplied list.
3.4 Getting Help
3.4.1 SPOTS Customer Documentation

The purpose of the Customer Documentation is to provide further information regard-
ing SPOTS functions and the user's interaction with the application optimizing the user's
experience.
3.4.1.1 SPOTS Online Help

You can obtain help while running the SPOTS Client by opening the SPOTS Online
Help, accessed by clicking Help. It can also be accessed at any time by pressing F1.
3.4.1.2 User Manual

A User Manual is available in electronic format (PDF) in the SPOTS installation media.
3.4.1.3 Installation Guide

An Installation Guide is provided to guide the Administrator step-by-step in the instal-
lation process.
3.4.1.4 Technology Plug-Ins Help

Each Technology Plug-In (TP) installed provides additional information in an Online
Help format. Each topic can be accessed by clicking What's this? and selecting the
required Nokia Siemens Networks Reports (see Nokia Siemens Networks Reports).
3.4.1.5 Metadata Help

Further information on the installed network objects can be obtained by opening the
Metadata Help window (see Metadata Help).
3.4.1.6 Reports Editor Help

The Reports Editor functionality provides additional information in an Online Help
format. It can be accessed by pressing F1 while in the Reports Editor window.
E200613-01-114-V14.0I-23 Id:0900d8058016594b 55
3.4.2 Metadata Help

The Metadata Help window can be accessed via:
> Help window > Metadata Help context menu item
The Metadata Help window provides you with more information about the installed NEs.
The window displays all measurement counters organized by object class.
Figure 18 Metadata Help window

Object Class Tree

The Object Class Tree contains all the available object classes. Select an object class
to view the associated measurements and counters.
Object Class Description

The Object Class Description displays further information on the selected object class.
It provides the name and further description.
Measurements Table
The Measurements Table displays all standard measurements supplied during instal-
lation of the selected object class. The associated counters can be viewed in the
Counters Table by selecting one of the measurement classes.
Counters Table
The Counters Table contains all the available counters for the selected measurement
and object class.
56 Id:0900d8058016594b E200613-01-114-V14.0I-23
User Manual (UMN) Using Spots
4 Using Spots
4.1 Network Administration
4.1.1 Node Configuration window

Creating, Editing and Viewing Network Nodes
The Node Configuration window can be accessed via:
> Network Administration task-tree folder > Node Configuration task-tree item
The Node Configuration window allows the Administrator to view, create and edit
Network Elements (NEs). It allows the Administrator to add Network Elements by pro-
viding their name, version and installation date. In order to add or edit existing network
nodes, the edit mode must be first activated by clicking the Edit Mode toolbar
button.
Figure 19 Node Configuration window

The Node Configuration window displays the Network Elements associated to the
selected domain. Information on each Network Element is displayed in table columns.
• Status
Displays the status icon of the network Node. The Node status icon is only shown
when a node has been created or removed.
• Name
Displays the name given to the network Node.
• Comment
Displays an optional description of network nodes.
• Version
Displays the Node hardware model. A new model can be added by installing its
respective Technology Plug-In (TPs). Version information can be seen in greater
detail in the Software Version window (see Software Version window).
• Date
Displays the Node installation date.
This window has specific toolbar buttons, located at the top of the SPOTS main window.
• Click Undo to remove the effect of the last performed operation.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 57
Using Spots User Manual (UMN)
• Click Redo to repeat the last performed operation.

• Click Print Preview to view a preview of the print output on the screen.
• Click Domain drop down menu to select the specific

domain responsible for the nodes that need to be configured.
Certain toolbar tasks are also available in a context menu by right clicking the table's
cells.
• Click Create Node to create a new Network Element.

• Click Remove Node to delete the selected Network Element.
• Click Edit Mode to allow the change of settings.
• Click View Mode to prevent changes to the Network Element’s settings.
• Click Save to save the changes made to the Network Element’s settings.
• Click Print to print the list of Network Elements.
Certain tasks are only available in a context menu by right clicking the table's cells.
• Click Versions... to open the Software Versions window.
g If performance data is available prior to the actual Node installation date, the date can
be set to any date to best suit you.
The changes made to settings are applied only upon saving or exiting the Configuration
window
f Removing network resources from the selection list automatically removes all associ-
ated performance data from the database. Reassigning an NE to another sub-domain,
if the network element is moved to a domain belonging to another database, is neces-
sary to export the respective data from the original database to the new database.
4.1.2 Software Version window

Viewing Software Versions
The Software Version window can be accessed via:
> Network Administration task-tree folder > Software Version task-tree item
The Software Version window allows the Administrator to view the Technology Plug-In
version for each installed NE. The window allows you to view both the Technology Plug
In details and installation date. In order to change a Software Version, the edit mode
must be first activated by clicking the Edit Mode toolbar button.
58 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Figure 20 Software Versions window

• Click Undo to remove the effect of the last operation performed.

• Click Redo to repeat the last operation performed.
• Click Domain drop down menu to select the specific

domain responsible for the nodes that need to be configured.
Certain toolbar tasks are also available in a context menu by right clicking the table
cell’s.

• Click View Mode to prevent changes to the software versions.
• Click Save to save the changes made to the software versions.
• Click Create Version to create a new software version.
• Click Delete Version to delete the selected software version.
• Click Print to print the software version list.
The Software Version window has the Node drop-down menu.
Click the Node drop-down menu to select a Network Element.
The window that displays the software version information is shown in table columns.
• Version
Displays the Technology Plug-In version.
• Date
Displays the software installation date.
f Removing a software version, automatically removes all associated performance data

from the database.
Before performing a BSC release upgrade (i.e from BR7.0 to BR8.0) it is necessary to
update the PM*, using the following procedure:
1. Select the Node Configuration Menu.
2. Select the option SW Version.
3. For the SW Version field enter the value of the new BSC version (for example
BR8.0) and for the field start date the relevant day.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 59
For example, for a BSC upgrade on the 8th of December, the following entries should
be made:
SW Version - BR8.0
Start date - 2006-12-08.
4.1.3 Resources Deletion window

Deleting Network Resources
The Resources Deletion window can be accessed via:
>Network Administration task-tree folder > Resources Deletion task-tree item
The Resources Deletion window allows the Administrator to remove any specific
Network Element (NE) from the network. You can selectively delete single NEs without
interfering with overall system performance. The Administrator can delete an NE by
selecting its object class and the specific instance.
Figure 21 Resources Deletion

• Click Delete to delete the selected Network Elements.
• Click Domain drop down menu to select the domain.

Class Tree
The Class Tree contains all the available object classes. Select an object class to view
the associated instances.
Instances Table
The Instances Table contains all the available instances of the selected object class.
Specific information on each available instance is given in two columns. More columns
are available for some NEs, with the information:
60 Id:0900d8058018db2b E200613-01-114-V14.0I-23
• Name
Displays the name of each instance for the selected object class.
• User Label
Displays the user’s label of the instance.
The selected instances can be added to the selection list by using the following buttons:
• Click Add to move all selected items from the Instances Table to the selection
list.
• Click Remove to remove all selected items from the Selection list to the
Instances Table.
The Instances Table contains a context menu by right clicking the table's cells.
• Hide
This option allows you to hide the selected table column.
• Columns
Allows you to select which columns are displayed in the Instances Tab and Sets
Tab.
• Show
This option allows you to choose and enable the column fields that were not selected
in the Columns option. If all columns are enabled this option is not available.
• Sorting...
The Sorting option opens a new window that provides a Sort by functionality. Select
the column that you wish to sort and the mode of sorting, that is, Ascending or
Descending. Additionally you can create new sorting or delete the existing ones by
using:
– Add
Adds a new sorting function
– Remove
Deletes the last sort created.
• Filters
Displays all the available filters and allows you to select which filter is active. When
one filter is active the following options are available:
– to open the editor filter window.
– to disable the active filter at the time.
• No Filter
This option deactivates any filter in use.
• Filter Editor
Runs the Filter Editor (see Report Filter Editor) configuration window.
• Export Data...
Saves the existing list of public or private sets of objects to a file.
• Refresh
Updates the Instances list.
The Instances Table contains a context menu by right clicking the selected item.
• Add Items
Adds all selected items from the Instances list to the Selection list.
• Select All
Selects all the items in the Instances list.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 61
g The Instances list allows you to sort by Name, by User Lable, or by both, in ascending
or descending order, by clicking on the corresponding list title.
Selection List
The Selection List contains all the selected instances. Double click an instance or set
to remove it from the selection list.
The Selection list contains a context menu by right clicking the list.
• Remove Items
Removes all selected items from the Selection list to the Instances lists.
• Select All
Selects all the items in the Selections list.
To delete the Network Elements in the Selection List click the Delete toolbar
button.
f If a network resource is removed from the selection list all associated performance data
is also removed from the database.
4.1.4 Domains Configuration window

Creating and Viewing Network Domains
The Domain Configuration window can be accessed via:
> Network Administration task-tree folder > Domain Configuration task-tree item
The Domain Configuration window allows the Administrator to view and create
network Domains. In order to create or edit network domains the edit mode must first be
activated by clicking the Edit Mode toolbar button.
Figure 22 Domains Configurator window


62 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Certain toolbar tasks are also available in a context menu by right clicking one of the
domains displayed in the hierarchical tree area.
• Click Create Domain to create a new network domain.

• Click Remove Domain to delete the selected network domain.
• Click View Mode to prevent changes to the network domain settings.
• Click Save to save the changes made to the network domain settings.
Certain tasks are only available in a context menu by right clicking the domain hierarchi-
cal tree area.
• Click Move Up to move the selected domain upwards.
• Click Move Down to move the selected domain downwards.
The Node Configuration window displays the network domains hierarchically in a tree.
Select a domain entry to view or edit its settings using the following fields:
• Name
In the Name text box you can type the name to be given to a new domain.
• Type
Click the Type drop down menu to select the type of domain. A domain can be either
a Primary Domain or a Sub-Domain. A Primary Domain contains all other sub-
domains in the network. A Primary Domain is always associated to a Database
Server.
• Database Server
In this text box you can type in the address of the Database Server to associate to
the Primary Domain.
g Network Elements are assigned either to a Primary Domain or to one of its sub-domains,
if they exist. When a sub-domain is removed, all network elements previously assigned
to that sub-domain become members of the Primary Domain above. In the domain's
structure, all domains defined above a Primary Domain only exist for visibility purposes,
as no network elements can be assigned to them.
4.1.5 User Domain window

Associating Users to Domains
The User Domain window can be accessed via:
> Network Administration task-tree folder > User Domain task-tree item
The User Domain window allows the Administrator to view and create network users.
Each user is associated to a particular domain. In order to create or edit users, the edit
mode must first be activated by clicking the Edit Mode toolbar button.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 63
Figure 23 Users Domain window

The window displays the properties of the users in table columns.
• Name
Displays the username.
• Domain
Displays the domain to which the user is associated. The network view of the user
extends only to its domain.

Certain toolbar tasks are also available in a context menu by right clicking the table’s
cells.
• Click Create Assignment to create a new network user.

• Click Remove Assignment to delete the selected network user.
• Click Edit Mode to allow the change of settings. This toolbar button must be
selected in order to create or edit a user.
• Click View Mode to prevent changes to the network user settings.
• Click Save to save the changes made to the user domain settings.
4.1.6 Extended Fields

Extended Fields (EF) are Properties (name-value pair) which can be associated to a
SPOTS Managed Object Instance. Each Managed Object Class contains at least one
pre-defined EF (UserLabel) but new ones can be created on user request. For a general
description regarding Extended Fields please refer to Chapter 1.12.
Uniqueness
Within each Object Class, the value of an Extended Field may or may not be repeated.
This is related to the Uniqueness parameter. If the parameter UNIQUE is used, the
extended field value can not be repeated. The parameter NOTUNIQUE states that the
value of the extended field can be repeated.
64 Id:0900d8058018db2b E200613-01-114-V14.0I-23
4.1.6.1 Creating a User Extended Field

To create a User Extended Field, the following steps must be performed:
Extract Extended Fields from DB

There are two possible ways to perform this operation:
• To return EF definitions for all the OCs available, the following command line must
be run:
extfieldinstall -a -x -f <filename>
• To return EF definitions for the object class specified while invoking use:
extfieldinstall -o <object class> -x -f <filename>
A file named <extended_field.txt> is generated at the location indicated, listing all
System and User EFs, which contents are similar to:
EXCHOC|1|User label|STRING|SYSTEM|NOTUNIQUE|EXCHOC|2|Test
Field|STRING|USER|NOTUNIQUE|CPOC|1|User label|STRING|
SYSTEM|NOTUNIQUE|LTGOC|1|User label|STRING|SYSTEM|
NOTUNIQUE|GPOC|1|User label|STRING|SYSTEM|NOTUNIQUE|
<OC_name>|<#>|<Extended_Field_Name>|<Data_Type>|<EF_Type>|
<Extended_Field_Value_UNIQUE/NOTUNIQUE>
Note that:
• In this structure, the second line refers to a user Extended Field (EF) while all the
other lines are from system Extended Fields
• The second parameter is a serial number, so if you intend to introduce a new EF, for
the same OC, the new line should be:
EXCHOC|3|New Test Field|STRING|USER|NOTUNIQUE|
• The parameter NOTUNIQUE means that the value of the extended field can be
repeated, although the name is identical.
Import Extended Fields into DB
The file exported in the first step can be edited in order to introduce or to remove some
Users EF lines, the import of the file results in the DB being updated.
extfieldinstall -i -f <path>/<extended_field.txt>
The file is imported and the new user’s EF can be seen in the Metadata Help window,
as well as in the Report Wizard’s second step.
Load Extended Fields values
Considering the following cm file structure, it is possible to generate values that are
going to be loaded for each Extended Field.
EXCHOC;NE_1_gr60;User label;Ext Field 1 for NE_1_gr60 of
gr60LOCAROC;NE_1_gr60.1;User label;Ext Field 2 for NE_1_gr60 of
gr60MPCLUSTEROC;NE_1_gr60.1;User label;Ext Field 3 for NE_1_gr60
of gr60ROUTINGAREAOC;NE_1_gr60.1.1;User label;Ext Field 4 for
NE_1_gr60 of gr60
<OC_name>,<Instance_Name>,<Extended_Field_Name>,<Extended_Field
_Value>
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 65
The file must have the extension .cm and must be placed in /var/opt/spots-
pms/cm_data/<Converter_Type>/
The following command line must be run:
dbloader -Xi -fi -d <domain> /var/opt/spots-
pms/cm_data/<Converter_Type>/<File_Name>.
The Extended Field values are then imported into the DB and it is possible to see the
values in the Report Wizard’s second step.
4.1.6.2 Extended Fields Administration window

The Extended Fields Administration window can be accessed via the Extended
Fields Administration task-tree item
Only user EFs are available to manage via the Extended Fields Administration window.
Since system EFs are distributed as part of the respective TP, their management cannot
be performed by users, only by Nokia Siemens Networks personnel.
Figure 24 Extended Fields Administration window

The Extended Fields Administration window is divided in two panes. The left pane
comprises the Object Classes into a tree form. The right pane displays the available
Extended Fields upon selection of an Object Class. This pane is composed of a table
with three columns:
The first column displays the actions which were executed on an EF:
New Extended Field
Edited Extended Field

Deleted Extended Field
The Extended Field Name column displays the name of the Extended Field.
The Source column identifies the EFs you are allowed to edit. Only Extended Fields with
Source equal to User can be edited. The System originated EFs are grayed out.
66 Id:0900d8058018db2b E200613-01-114-V14.0I-23
The options to create, edit and delete EFs are located on the application toolbar. Addi-
tionally it is also possible to right click the desired EF in order to perform theses opera-
tions via a context menu.
4.2 Data Administration
4.2.1 Load Data window

Loading Measurement Data
The Load Data window can be accessed via:
> Data Administration task-tree folder > Load Data task-tree item
The Load Data window allows the Administrator to load measurement data files for
Trend Analysis. You can selectively load Detailed measurements from single Network
Elements without interfering with the overall system database. The Administrator can
delete the data files after the measurement data has been imported into SPOTS.
Figure 25 Load Data window

Data Selection
The Data Selection field allows you to select the data to be loaded. You can filter the
data using the Apply Filter check box.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 67
Select the Apply Filter check box and type the name of the file to limit the files shown
in the File List.
The data location can be chosen by using one of the following radio buttons:
• Directory Selection
Select the Directory Selection radio button and click the ... button to browse
through the available directories. You can select a folder using the Directory
Chooser window.
• File Selection
Select the File Selection radio button and select the files to load using the Files and
Selection lists.
The Files List contains all the files in the default directory.
The selected files can be added to the Selection list by using the following buttons:
• Click Add button to move all selected items from the Files list to the Selection
list.
• Click Remove button to remove all selected files from the Selection list to the
Files list.
The Selection List contains all the selected measurement data files to be loaded.
Options
The Options field allows you to delete the original data using the following check box:
To load the measurement data files in the Selection List click the Execute toolbar
button, otherwise, in case of frequent use, click Schedule Task to automate the
measurement data loading. The Schedule Task menu has the following options:
• Delete Files After Load
Select the Delete Files After Load check box to erase the original measurement
data after successful loading.
• Show Load Operation Results
Select the Show Load Operation Results check box to display the final report.
68 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Figure 26 Load Operation Results window

This window has the following fields:
Load Operations Overview
The Load Operations Overview shows the number of files that were read, inserted,
updated and discarded in the Load Data Operation.
Load Operation Details
The Load Operation Details shows the filename and the respective operation that
occurred to that same file.
This window has the following buttons:
• Click OK to close the window.

• Click Cancel to cancel the visualization and close the window.
4.2.2 Delete Data window

Deleting Measurement Data
The Delete Data window can be accessed via:
> Data Administration task-tree folder > Delete Data task-tree item
The Delete Data window allows the Administrator to delete specific Trend Analysis
measurement data. You can selectively delete Detailed or Historical measurements
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 69
from single Network Elements without interfering with the overall system database. The
Administrator can delete the data from an NE by selecting its object class and the
specific instance.
Figure 27 Delete Data window

• Click Save Task to save the data deletion task to the My Tasks list.
• Click Schedule Task to postpone the execution of the data deletion to a later
specified date.
• Click Execute to delete the selected measurement data files.

Settings
The Settings field allows you to select the data type and time intervals to be deleted.
You can select the data type using the Logged Data drop-down menu.
Click the Logged Data drop-down menu to select the type of database to be deleted.
You can selectively delete several data types.
• Detailed
Log that stores the performance data (default data).
• First & Interval
Log that stores the performance data generated as result of the QoS Alarms (first
events).
70 Id:0900d8058018db2b E200613-01-114-V14.0I-23
• Historic
Log that stores the generated historic performance data.
The date interval can be chosen by using the following radio buttons:
• Preserve Last
Select the Preserve Last radio button, type in the number of days to delete all but
the last obtained measurements.
• Interval
Select the Interval radio button, select the dates using the From and To drop-down
menus, to delete only the data obtained in between the selected dates.
Data
The Data field allows you to select the measurement database to be erased by selecting
its object class and its specific measurements.
The Nodes Tree contains all the available object classes. Select an object class to view
the associated measurements. Double click a Network Element to select all measure-
ments into the selection list.
The Measurements List contains all the available measurements of the selected object
class. Double click a measurement to include it in the selection list.
The selected instances can be added to the selection list by using the following buttons:
• Click Add to move all selected items from the Measurements list to the Selection
list.
• Click Remove to remove all selected items from the Selection list to the Mea-
surements list.
The Selection List contains all the selected instances. Double click a measurement to
remove it from the selection list.
Both Measurements and Selection Lists contain a context menu by right clicking the
table’s cell.
• Add
Moves all selected items from the Measurements list to the selection list.
• Remove
Removes all selected items from the Selection list to the Sets or Instances lists.
• Select All
Selects all the items in the Measurements list.
To delete the measurement data in the Selection List click the Execute toolbar
measurement data deletion.
4.2.3 Data Aggregation window

Aggregating Measurement Data
The Data Aggregation window can be accessed via:
> Data Administration task-tree folder > Data Aggregation task-tree item
The Data Aggregation window allows you to process the Trend Analysis detailed data
into higher granularity detailed data, modifying its sampling frequency. The Administra-
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 71
tor can delete the original data files after the measurement data has been processed into
a higher granularity.
Figure 28 Data Aggregation window

This window has specific toolbar buttons located at the top of the SPOTS main window.
• Click Save Task to save the data aggregation task to the My Tasks list.
• Click Schedule Task to postpone the execution of the data aggregation to a
later specified date.
• Click Execute to aggregate the selected measurement data files.

The Data Aggregation window allows you to aggregate the data by using the following
drop-down menus:
• Time Scope
Click the Time Scope drop-down menu to select the time interval of the Detailed
data to be aggregated. The following preset date intervals are available.
– Yesterday
– Last Week
– All Existing
• Algorithm
Click the Algorithm drop-down menu to select the aggregation algorithm type. The
following preset algorithms are available.
– Normal Measurements
Aggregates all ordinary Detailed data measurements.
– First & Interval
Aggregates all First and Interval alarm history data
– Second Method after First Method
Aggregates all ordinary Detailed data measurements, followed by First and
Interval measurements.
• Input Granularity
Click the Input Granularity drop-down menu and select the measurement data's
original sampling frequency.
72 Id:0900d8058018db2b E200613-01-114-V14.0I-23
• Output Granularity
Click the File Selection drop-down menu and select the aggregated measurement
data's sampling frequency.
The window allows you to delete the original data using the Delete records after suc-
cessful aggregation check box.
Select the Delete records after successful aggregation check box to erase the
original measurement data after successful aggregation.
To aggregate the measurement data files click the Execute toolbar button, other-
wise, in case of frequent use, click Schedule Task to automate the measurement
data aggregation.
4.2.4 Make History window

Saving Measurement Data to the History Log
The Make History window can be accessed via:
> Data Administration task-tree folder > Make History task-tree item
The Make History window allows the Administrator to process the Trend Analysis
detailed data into a compressed log. The History log allows you to dispose of redundant
measurement data in the database. The sampling frequency of the History log is
reduced to one sample per 24 hours of detailed measurement data, being the maximum
recorded value within that 24 hour period. The Administrator can choose to delete the
original data files after the measurement data has been compressed.
Figure 29 Make History window

• Click Save Task to save the make history task to the My Tasks list.
• Click Schedule Task to postpone the execution of the make history task to a
later specified date.
• Click Execute to compress the selected measurement data files.

The date interval can be chosen by using the following radio buttons:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 73
• Begin and End dates

Select the radio button and select the dates using the Begin Date and End Date
drop-down menus, to delete only data obtained between the selected dates.
• Time Scope
Click the Time Scope drop-down menu to select the time interval of the detailed
data to be processed. The following preset date intervals are available.
– Yesterday
– Last Week
– All Existing
The Data Aggregation window allows you to aggregate the data by using the Input
Granularity drop-down menus.
Click the Input Granularity drop-down menu and select the measurement data's
original sampling frequency.
The window allows you to delete the original data using the Delete records after suc-
cessful aggregation check box.
Select the Delete records after successful aggregation check box to erase the
original measurement data after the successful processing of the history log.
To create a history log with the measurement data files click the Execute toolbar
process.
g The Make History tasks requires 15 minute granularity Detailed Data. If only 5 minute
granularity data is available, it is necessary to convert it to 15 minute granularity using
the Data Aggregation task
4.3 PM Entities
4.3.1 Sets of Objects
4.3.1.1 Sets of Objects window

The Sets of Objects window can be accessed via:
> PM Entities task-tree folder > Set of Objects task-tree item
The Sets of Objects window allows you to view, create and edit Sets of Objects
(SOOs). A Set of Objects provides the means of representing a group of network
objects as a single entity. Sets of Objects can also be created and edited using the Sets
of Objects Wizard (see Sets of Objects Wizard). In order to create or edit Sets of
Objects, the edit mode must be first activated by clicking the Edit Mode toolbar
button.
74 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Figure 30 Set of Objects window

The window displays the properties of the Sets of Objects in table columns.
• Name
Displays the names of the public or private sets of objects.
• Expression
Provides a list of the objects (or sets) included in a set.
• Comment
Displays an optional description for the private/public set of objects. It is displayed
in the Reports Wizard and Class Browser (see Class Browser window) objects
window.
• Class
Displays the measurement class associated to the public or private set of objects.
Public Tab
The Public tab allows you to view, create and edit public Sets of Objects. Public Sets of
Objects can be viewed by all SPOTS users.
Private Tab
The Private tab allows you to view, create and edit private Sets of Objects. Private Sets
of Objects can be viewed by it's (SPOTS user) author only.
The tabs above only differ on the permissions of the contained Sets of Objects, both
having the same tasks available.
The Sets of Objects window has specific toolbar buttons, located at the top of the
SPOTS main window.

cells.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 75
• Click Wizard... context menu.

• Click Create Set to create a new Set of Objects using the Sets of Objects
Wizard.
• Click Edit Set to modify the selected Set of Objects using the Sets of Objects
Wizard.
• Click Create Set to create a new Set of Objects.
• Click Remove Set to delete the selected Set of Objects.
• Click Edit Mode to allow the change of settings for selected Sets of Objects.
• Click View Mode to prevent changes to Sets of Objects settings.
• Click Save to save a Set of Objects settings.
• Click Print to print the Sets of Objects list.
Certain tasks are only available in a context menu by right clicking the table’s cells.
• Click Transfer To Private to move the selected sets to the private list. Both Private
and Public lists must be in Edit Mode in order to transfer a set.
• Click Transfer To Public to move the selected sets to the public list. Both Private
• Click Import... to overwrite the existing list of public or private sets of objects using
the information contained in a file. This operation is done using the Import window.
• Click Export... to save the existing list of public or private sets of objects to a file,
using the Export window.
• Click Page Setup... to configure the page display properties using the Page Setup
window.
4.3.1.2 Set of Objects syntax

Within SPOTS, the network resources are represented as objects. These objects may
be grouped into sets of objects (SO). Each SO may be used to reference each single
object within the scope of the defined set, or as a whole, as a virtual object, representing
all the objects within the scope of the set.
From the user point of view, the SO syntax is specified by the grammatical flow diagram
below.
Figure 31 SO Syntax Flow Diagram
76 Id:0900d8058018db2b E200613-01-114-V14.0I-23
The Set of Objects with Conditions functionality can be used when creating a new Set
of Objects using the New Set option to filter unnecessary objects. In the Expression
column the list of objects to include can be set using the following operators along with
the objects properties:
• “!“ : NOT
• “&” or “&&” : AND
• “|” or “||” : OR
• “=” or “==” : EQUAL
• “!=” : NOT EQUAL
• “<“ : LESS
• “>” : GREATER
g To use all or none of the objects in the set, type “=1” or “=0” respectively.
The following example gives an overview of the functionality:

= User Label == “T58”
= (User Label == “T58”) || (Region<“PORTO”)
g If an expression starts with the character “=”, it cannot contain wildcards.
The following wildcards can be used on the object names instead of explicitly defining
every object of the set:
• "*" - represents any sequence of alphanumeric characters
• "?" - represents any alphanumeric character
The following image demonstrates several examples of filters that can be applied.
Figure 32 Extended Fields Filters
• Using “*” it is possible to create an expression like:

NE*
• Using “*” and “,” it is possible to create an expression like:
V5:1,NE_1_hiS700V5b:*,NE_1_his700V5a:1 Please note that after the use of the
“,” symbol there can be no blank spaces.
• Using “*” and “?” it is possible to create an expression like:
NE_1_hiS700V4*,NE_1_hiS700V5?
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 77
It is possible to create an expression using several “*” however, this expression will not
accept the “?” symbol to substitute other symbols. Therefore in the instances filters it is
not possible to implement an expression to filter instances with the “|” symbol as the
fourth symbol.
It is possible to perform several operations in order to filter the unnecessary data. When
doing so it is necessary to use “( )” in each filtering operation.
g The names used in the table fields are recognized as variables and are case sensitive.
The operations with boolean and logical operators are case insensitive.
Using wildcards is advantageous because you do not need to specify all NEs to be fil-
tered. It is, however less efective in performance since all NEs are checked to match the
filter. Not using wildcards is advantageous when it concerns performance, but you must
know and specify all intended NEs.
4.3.1.3 Sets of Objects Wizard

The Sets of Objects wizard can be accessed via:
> PM Entities task-tree folder > Set of Objects task-tree item > Create Set toolbar button
The Sets of Objects wizard allows you to group several network objects in a Set of
Objects. The wizard is available when the Set of Objects window is opened.
This window has a navigation toolbar, located at the bottom of the window:
• Click Finish to create a Set of Objects with the chosen settings.
This button is enabled in the last step.
• Click Cancel to leave the window without changing the settings.
• Click Previous to go to the previous step of the window.
• Click Next to go to the next step of the window.
This button is enabled in the first step.
The Contents field provides an overview of the different wizard steps. The wizard has
the following steps:
Step 1: Set of Objects Properties

This step allows you to set the general properties of the Set of Objects.
78 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Figure 33 Object Creation Wizard, Creating Virtual Identity window- Step1

• Entity Visibility
Displays the permissions associated to the Set of Objects being created. You can
select a different permission level by selecting its respective tab in the Set of
Objects window (see Sets of Objects window).
• Name
Type in the name to be given to the Set of Objects.
• Comment
Type in any relevant note (warning, additional information, among others) to be
associated to the Set of Objects.
Step 2: Select Instances

This step allows you to select the objects to be included in the Set of Objects.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 79
Figure 34 Object Creation Wizard, Creating Virtual Identity window - Step2

Class Tree
the associated instances or sets of objects.
Instances and Sets Lists

Click the Instances Tab to select any instance available for the previously selected
object class. Double click an instance to add it to the selection list.
Specific information on each available instance is given in two columns.
• Name
• User label
Click the Sets Tab to select any set of objects available for the previously selected
object class. Double click a set of objects to add it to the selection list.
The selected instances or sets can also be added to the selection list by using the fol-
lowing buttons:
• Click Add Items to move all selected items from the Instances list to the selection
list.
• Click Remove Items to remove all selected items from the Selection list to the
Sets or Instances lists.
Click the Expression Editor Tab to use conditions and select objects based on the
information contained in their Extended Fields.
• Click New to add a new expression.
80 Id:0900d8058018db2b E200613-01-114-V14.0I-23
• Click Open to open a existing expression.

• Click Save the created expressions, in public or private form.
• Click Cut to cut the expression.
• Click Copy to copy the expression.
• Click Paste to paste the expression.
• Click the Execute Report to return the results of the current expression. This
button is only visible if the expression created is valid. This is noted by the Success-
ful and Failed icons in the lower right corner of the expression editor.
• Click Import Instance to browse active filters.
• Click Add Items to move all selected items to the selection list.
• Click Remove Items to remove all selected items from the Selection list.
The Sets Tab and Instances Tab lists contain a context menu by right clicking the
mouse.
• Add Items
Moves all selected items from the Sets or Instances lists to the selection list.
• Select All
Selects all the items in the Sets or Instances lists.
The Sets Tab and Instances Tab lists also provide a drop down menu above the scroll
bar which contains the following tasks in a context menu.
• Hide
• Columns
Tab.
• Show
• Sorting...
the column to sort and the mode of sorting, Ascending or Descending. Additionally
you can create new sorting or delete the existing ones by using:
– Add
– Remove
Deletes the last sorting option created.
• Filters
Displays all the available filters and allows you to select which filter will be active.
When one filter is active the following options are available:
• No Filter
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 81
• Filter Editor
• Export Data...
• Refresh
g Both lists allow you to make an ascendent or descendent sort by Name, by User Label,
or both, by clicking on the corresponding list title.
Selection List
The Selection List contains all the selected instances and sets of objects. Double click
an instance or set to remove it from the selection list.
The Selection list contains a context menu by right clicking the mouse.
• Remove Items
• Select All
4.3.2 Sets of Counters
4.3.2.1 Sets of Counters window

The Sets of Counters window can be accessed via:
> PM Entities task-tree folder > Set of Counters task-tree item
The Sets of Counters window allows you to view, create and edit Sets of Counters
(SOCs). A Set of Counters provides the means by which a group of measurement
counters can be represented as a single entity. Sets of Counters can also be created
and edited using the Sets of Counters Wizard. In order to create or edit Sets of Counters,
the edit mode must be first activated by clicking the Edit Mode toolbar button.
82 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Figure 35 Set of Counters window

The window displays the properties of the Sets of Counters in table columns.
• Name
Displays the names of the public or private sets of counters.
• Expression
Provides a list of the counters (or sets) included in a set.
• Comment
Displays an optional description for the private/public set of counters. It is displayed
in the Reports Wizard and Class Browser objects window.
• Class
Displays the object class associated to the public or private set of counters.
Public Tab
The Public tab allows you to view, create and edit public Sets of Counters. Public Sets
of Counters can be viewed by all SPOTS users.
Private Tab
The Private tab allows you to view, create and edit private Sets of Counters. Private
Sets of Counters can be viewed only by their SPOTS User owners.
The tabs above only differ on the permissions of the contained Sets of Counters, both
The Sets of Counters window has specific toolbar buttons, located at the top of the
SPOTS main window.

cells.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 83
• Click Wizard ... context menu.

• Click Create Set to create a new Set of Counters using the Sets of Counters
Wizard.
• Click Edit Counter to modify the selected Set of Counters using the Sets of
Counters Wizard.
• Click Create Set to create a new Set of Counters.
• Click Remove Set to delete the selected Set of Counters.
• Click Edit Mode to allow the change of settings for selected Sets of Counters.
• Click View Mode to prevent changes to the Sets of Counters settings.
• Click Save to save the Set of Counters settings.
• Click Print to print the Sets of Counters list.
• Click Copy To Private to move the selected sets to the private list. Both Private and
Public lists must be in Edit Mode in order to transfer a set.
• Click Copy To Public to move the selected sets to the public list. Both Private and
Public lists must be in Edit Mode in order to transfer a set.
• Click Import... to overwrite the existing list of public or private sets of counters using
• Click Export... to save the existing list of public or private sets of counters to a file,
window.
4.3.2.2 Set of Counters syntax

Within SPOTS all metrics related with the network resources are represented as coun-
ters. These counters may represent raw measurements loaded from the network
resources or derived data calculated during the data load process.
The counters may be grouped into sets of counters (SOC). Each SOC may be used to
reference each single counter within the scope of the defined set.
From the user point of view, the SOC syntax is specified by the grammatical flow
diagram below.
84 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Figure 36 SC Syntax Flow Diagram

Example:
TgrpCallMetrics = TGRP:CC_OO, TGRP:CC_IC, VC!TG_CC
4.3.2.3 Sets of Counters Wizard

The Sets of Counters wizard can be accessed via:
> PM Entities task-tree folder > Set of Counters task-tree item > Create Set button
The Set of Counters wizard allows you to select the object class and respective counters
to create a Set of Counters. The wizard is available when the Set of Counters window
is opened.
• Click Finish to create a Set of Counters with the chosen settings.
Step 1: Set of Counters Properties

This step allows you to set the general properties of the Set of Counters (see Sets of
Counters window). The name and class of object to be grouped can be set.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 85
Figure 37 Counter Creation Wizard, Creating Virtual Entity window- Step1

Displays the permissions associated to the Set of Counters being created. You can
select a different permission level by selecting its respective tab in the Set of
Counters window.
• Name
Type in the name to be given to the Set of Counters.
• Comment
Type in any relevant note (warning, additional information, among others) to asso-
ciate to the Set of Counters.
The object class can be selected using the Object Class drop down list.
Select the Object Class of the Set Counters from the drop down list.
Step 2: Select Counters

This step allows you to select the counters to be included in the set of counters.
86 Id:0900d8058018db2b E200613-01-114-V14.0I-23
Figure 38 Counter Creation Wizard, Creating Virtual Entity window - Step2

Measurements and Sets Lists

Click the Measurements Tab to select a measurement class. The associated counters
can be viewed in the Counters Table by selecting one of the available classes:
• The first list entries (SEMSU, SYSLMP, among others) represent all standard mea-
surements supplied during installation of the selected object class.
• The Sets of Counters displays all available public and private Sets of Counters for
the selected object class.
• The Virtual Counters displays all available public and private virtual counters for
the selected object class.
Click the Sets Tab to select a set of counters. The counters displayed in the Counters
Table are restricted to those defined in private and public Sets of Counters. This method
differs from the Sets of Counters measurement class in the Measurements Tab as it
allows the selection of individual counters contained in each Set of Counters.
Counters Table
The Counters Table contains all the available counters for the selected object class.
Specific information on each available counter is given in two columns.
• Name
Displays the names of the available counters for the selected object class.
• Description
Provides a brief description of each counter properties.
The selected counters or sets can be added to the selection list by using the following
buttons:
• Click Add Items to move all selected items from the Counters Table to the selec-
tion list.
Counters Table.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 87
The Counters Table list contains a context menu by right clicking the mouse.
• Add Items
Moves all selected items from the Counters list to the selection list.
• Select All
Selects all the items in the Counters list.
The Counters Table list also provides a drop down menu above the scroll bar which
contains the following tasks in a context menu.
• Hide
• Columns
Allows you to select which columns are displayed in the Measurements Tab and
Sets Tab.
• Show
• Sorting...
– Add
– Remove
Deletes the last sorting created.
• Filters
• No Filter
• Filter Editor
• Export Data...
• Refresh
g Both lists allow you to make an ascending or descending sort by Name, by Description,
or both, by clicking on the correspondent list title.
Selection List
The Selection List contains all the selected counters and sets of counters. The items
in the selection list correspond to either the number of data series in graph reports or to
the number of data columns in table reports. Double click a counter or set to remove it
from the selection list.
The Selection List contains a context menu by right clicking the mouse.
88 Id:0900d8058018db2b E200613-01-114-V14.0I-23
• Remove Items
Removes all selected items from the Selection list to the Counters lists.
• Select All
4.3.3 Virtual Counters
4.3.3.1 Virtual Counters window

The Virtual Counters window can be accessed via:
> PM Entities task-tree folder > Virtual Counters task-tree item
The Virtual Counters (VC) window allows you to view, create and edit Virtual Counters.
A Virtual Counter provides the means of establishing arithmetical relations between
measurement counters and of representing them as a single entity. Virtual Counters can
also be created and edited using the Virtual Counters Wizard (see Virtual Counters
Wizard). In order to create or edit Virtual Counters, the edit mode must first be activated
by clicking the Edit Mode toolbar button.
Several VCs can be created and edited in the GUI, but when you save the newly created
VCs, the GUI sends the VCs one by one to the SAS. The SAS then validates each VC
and saves it in the virtual_entities.dat file. This approach guarantees that the saved
virtual counters are correct.
When several VCs are created and you click "Save", only the correct VCs are saved and
an error message is issued for each one of the remaining faulty VCs. You may correct
the faulty VCs and may try to save them again. The VCs will only be saved when they
are correct.
For example: User creates two VCs, vc1 and vc2, and vc1 refers vc2.
VC1=SOMEMEASURE:SOMECOUNTER + .... .+ VC!VC2VC2=SOMEMEA-
SURE:SOMECOUNTER + .......
When you click SAVE, the following will occur:
– The SAS will receive firstly the VC1 for validation and saving.
– The SAS will not be able to save VC1 because at the time it is validating VC1, VC2
does not exist, and there is no guaranty whatsoever that it will ever exist.
– The SAS receives the VC2. VC2 is correct and will be saved.
– If you click save again, at this point, then SAS can now save the VC1 because VC2
exists.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 89
Figure 39 Virtual Counters window

The Virtual Counters window displays the properties of the Virtual Counters in table
columns.
• Name
Displays the names of the public or private virtual counters.
• Expression
Displays the mathematical expression that weighs and relates all counters and sets
evaluated into a virtual counter.
• Comment
Displays an optional description for the private/public virtual counters. It is displayed
in the Reports Wizard and Class Browser objects window.
• Unit
Displays the unit type of public or private virtual counter.
• Class
Displays the object class associated to the public or private virtual counters.
The Virtual Counters window has the following tabs:
Public Tab
The Public tab allows you to view, create and edit public Virtual Counters. Public Virtual
Counters can be viewed by all SPOTS users.
Private Tab
The Private tab allows you to view, create and edit private Virtual Counters. Private
Virtual Counters can be viewed only by their SPOTS user owners.
The tabs above only differ on the permissions of the contained Sets of Counters, both
The Sets of Counters window has specific toolbar buttons, located at the top of the
SPOTS main window.
90 Id:0900d8058018db2b E200613-01-114-V14.0I-23

cells.
• Wizard ... context menu.

• Click Create Counter to create a new Virtual Counter using the Virtual Counters
Wizard (see Virtual Counters Wizard).
• Click Edit Set to modify the selected Virtual Counter using the Virtual Counters
Wizard (see Virtual Counters Wizard).
• Click Create Counter to create a new Virtual Counter.
• Click Remove Counter to delete the selected Virtual Counter.
• Click Edit Mode to allow the change of settings for the selected Virtual Counter.
• Click View Mode to prevent changes to Virtual Counters settings.
• Click Save to save a Virtual Counter settings.
• Click Print to print the Virtual Counters list.
• Click Transfer To Private to move the selected sets to the private list. Both Private
• Click Transfer To Public to move the selected sets to the public list. Both Private
• Click Import... to overwrite the existing list of public or private Virtual Counters using
• Click Export... to save the existing list of public or private Virtual Counters to a file,
window.
4.3.3.2 Virtual Counters syntax

Within SPOTS, all metrics related with the network resources are represented as coun-
ters. These counters may represent raw measurements loaded from the network
resources or derived data calculated during the data load process (base calculated vari-
ables).
The counters may be extended in runtime through the use of virtual counters (VC). Each
VC represents an arithmetical formula that is computed in runtime.
From the user point of view, the syntax of VC expressions is specified by the grammat-
ical flow diagram below.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 91
Figure 40 VC Expressions Syntax Flow Diagram

Available operations:
• Unary operator: -
• Arithmetical operators: +,-,*,/,^
• Boolean operators: =,<,>,>=,<=,!=
Available functions:
• MAX( <expression>, <expression> )
• MIN( <expression>, <expression> )
• IF( <boolean_expression>, <expression1>, <expression2> )
Note: when the boolean_expression is 'true' then expression1 is returned else
expression2 is returned.
• GRANULARITY ()
Note that:
• Virtual Counters can combine counters of different measurement types as long as
they belong to the same object class.
• Counters, for which there is no data, will be evaluated as 0 in additions and subtrac-
tions and as 1 in multiplications and divisions. However, when there is no data for
all the counters then the expression yields no data.
Examples:
VCname: TG_TV
VCobject_class: XTPSG
VCdescription:Traffic Volume of a Trunk Group
VCexpression: TGRP:TV_OO+TGRP:TV_IC
VCunit: ERL.SVCname: TG_CC
92 Id:0900d8058018db2b E200613-01-114-V14.0I-23
VCdescription: Carried Calls of a Trunk Group

VCexpression: TGRP:CC_OO+TGRP:CC_IC
VCunit: NRVCname: TG_MHT
VCdescription: Mean Holding Time of a Trunk Group
VCexpression: TG_TV/TG_CC
VCunit: SECVCname: TG_TC
VCdescription: Traffic Intensity of a Trunk Group
VCexpression: TG_TV/GRANULARITY()
VCunit: ERL
Editing\Saving behavior
Several VCs may be created and edited in the GUI. However, when you save the newly
created VC, the GUI sends one VC at a time to the SAS. Then the SAS validates each
VC and saves them in the virtual_entities.dat file. This procedure guarantees that the
saved VCs are correct. When several VCs are created and you click the Save button,
only the correct VCs are saved and an error message is issued for each remaining faulty
VC. You may correct the faulty VC and can try to save them again. They will only be
saved when they are completly correct.
Example:
You create two Virtual Counters, VC1 and VC2 where VC1 refers VC2.
VC1=SOMEMEASURE:SOMECOUNTER + ... + VC!VC2VC2=SOMEMEA-
SURE:SOMECOUNTER + ...
When you click the Save button:
1. The SAS receives the VC1 for validation and saving.
2. The SAS is not able to save VC1 because at its validation time, VC2 does not exist,
and there is no guaranty that it will ever exist.
3. The SAS receives the VC2. VC2 is correct, so it will be saved.
When you click the Save button again, the SAS can now save VC1 because VC2
already exists.
4.3.3.3 Virtual Counters Wizard

The Virtual Counters wizard can be accessed via:
> PM Entities task-tree folder > Virtual Counters task-tree item > Create Counter button
The Virtual Counters wizard allows you to select the object class, respective counters
and arithmetical expression to create a Virtual Counter. The wizard is available when
the Virtual Counters window is opened.
• Click Finish to create a Virtual Counter with the chosen settings.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 93
Step 1: Virtual Counter Properties

This step allows you to set the general properties of the Virtual Counter.
Figure 41 Virtual Counter Creation Wizard - Step1

Displays the permissions associated to the Virtual Counter being created. You can
select a different permission level by selecting its respective tab in the Virtual
Counters window.
• Name
Type in the name to be given to the Virtual Counter.
• Comment
Type in any relevant note (warning, additional information, among others) to be
associated to the Virtual Counter.
• Object Class
Select the Object Class of the Virtual Counter from the drop down list.
• Unit
Select the Unit to use from the drop down list.
Step 2: Select Counters

This step allows you to select the counters to be included in the Virtual Counter.
94 Id:0900d8058018db2b E200613-01-114-V14.0I-23


surements supplied during installation of the selected object class
• Sets of Counters displays all available public and private Sets of Counters for the
selected object class
• Virtual Counters displays all available public and private virtual counters for the
selected object class
Counters Table
• Name
• Description
Provides a brief description of each counter properties.
buttons:
tion list.
Counters Table.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 95
• Add Items
• Select All
• Hide
• Columns
Sets Tab.
• Show
• Sorting...
The Sorting option opens a new window that provides a Sort-by functionality. Select
you can create new sorts or delete the existing ones by using:
– Add
– Remove
• Filters
• No Filter
• Filter Editor
• Export Data...
• Refresh
g Both lists allow you to make an ascending or decscending sort by Name, by Description,
or both, by clicking on the corresponding list title.
Selection List
96 Id:0900d8058018db2b E200613-01-114-V14.0I-23
• Remove Items
• Select All
Step 3: Build Expression

This step allows you to establish an arithmetical relation between the selected counters.

Expression
The Expression text box displays the arithmetical relationship between the selected
counters. The formula relating the counters can be set either by using the Numerical
Keypad with the mouse or by using the keyboard.
Counters
The Counters list contains all the previously selected counters for the selected object
class. A counter or set can be added to the Expression text box by double clicking it.
Macros
The Macros list contains a series of predefined functions. These functions can be used
to perform statistical analysis to the counter measurements. Double click a macro to
apply it to the Expression text box.
Numerical Keypad
The Numerical Keypad field contains an on-screen keypad that allows you to set the
arithmetical formula to be used in the Expression text box. The formula is used to math-
ematically quantize each counter with respect to the other selected counters. The
formula can be set by using the mouse.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 97
4.3.4 Import PM Entities window

Importing Sets of Counters, Sets of Objects or Virtual Counters
The Import window can be accessed via:
Sets of Counters, Sets of Objects or Virtual Counters window > Import... context menu
item
The Import window allows you to create a list or lists of public or private SOCs, SOOs
or VCs using a file external to the SPOTS PMC. Therefore allowing lists of SOCs, SOOs
or VCs to be used across several SPOTS PMCs by exporting and importing the lists.
g The file to import can contain more than one list depending on how you performed the
export procedure.
A browser is supplied to help you to navigate through the system folders. If you know
the whole file path and the filename of the file to import you can input them manually into
the File Name text box.
The Import window has two buttons, located at the bottom of the window:
• Click Open to start the file import.
• Click Cancel to leave the window without importing a file.
g In order to import a file, the list of SOCs, SOOs or VCs must be in Edit Mode.
4.3.5 Export PM Entities window

Exporting Sets of Counters, Sets of Objects or Virtual Counters
The Sets of Counters, Sets of Objects or Virtual Counters windows’ > Export... context
menu item
The Export window allows you to save public or private SOCs, SOOs or VCs to a file
external to the SPOTS PMC. This therefore allows the same SOCs, SOOs or VCs to be
used across several SPOTS PMCs, by exporting and importing.
g If none of the lists are selected when the export procedure is executed, all the current
lists of the table are exported. To export a specific list you must select it from the table.
The supplied browser helps you to navigate through the system folders. You must select
the path and input the filename in the File Name text box.
The Export PM Entities window has two buttons, located at the bottom of the window:
• Click Save to start the file export.
• Click Cancel to leave the window without exporting a file.
g In order to export a file, the list of SOCs, SOOs or VCs must be in Edit Mode.
98 Id:0900d8058018db2b E200613-01-114-V14.0I-23
4.4 Trend Analysis Utilities
4.4.1 Scheduler
Scheduling Tasks
The Scheduler window can be accessed via:
> Utils task-tree folder > Scheduler task-tree item
The Scheduler window allows the Administrator to create, edit or remove scheduled
jobs. A scheduled job contains one or more tasks to be performed at a specified time or
with a specific frequency. The following tasks, such as Load Data (see 4.2.1), Delete
Data (see 4.2.2), Data Aggregation (see 4.2.3), Make History (see 4.2.4) and Reports
can be scheduled in a job. In order to create or edit scheduled jobs, the edit mode must
first be activated by clicking the Edit Mode toolbar button.
Figure 44 Scheduler window


• Click View Mode to prevent changes to the scheduled job settings.
• Click Save to save the changes made to the scheduled jobs settings.
• Click Create Job to create a new scheduled job.
• Click Remove Job to delete the selected scheduled job.
Jobs List
The Jobs List allows you to create, edit or remove jobs.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 99
The toolbar buttons above are also available in a context menu that contains the
Rename Job additional feature by right clicking the list. This feature allows you to to
type a new name for the scheduled job.
Tasks List
The Tasks List displays all the tasks included in the job selected in the Jobs List. Jobs
can be added by using the Task Administration window (see 4.4.3). All available tasks
can also be viewed in the My Tasks (see 4.4.4) and My Reports (see 4.6.3) task-tree
folders.
The task execution order can be changed by using the following buttons:
• Click Move Down to move the selected task one position down. The tasks are
performed in top to bottom order.
• Click Move Up to move the selected task one position up. The tasks are per-
formed in top to bottom order.
The buttons above are also available in a context menu. It contains the following addi-
tional feature by right clicking the list.
Task Administration
Click the Task Administration context menu item to choose the tasks to be included in
a job using the Task Administration window.
Execution Settings
The Execution Settings field allows you to select the data type and time intervals to be
deleted. You can select the data type using the following drop-down menu.
Click the Execution Type drop-down menu to select the scheduled job periodicity. You
can select from several execution types.
• Once
Execute the job on a specific date.
• Minutely
Repeat the job execution with a minutely periodicity.
• Hourly
Repeat the job execution with an hourly periodicity.
• Daily
Repeat the job execution with a daily periodicity
• Weekly
Repeat the job execution with a weekly periodicity.
• Monthly
Repeat the job execution with a monthly periodicity.
The job execution time can be specified by using the Start at field. It allows you to set
the execution time using the adjacent buttons.
If execution fails, a scheduled job can be retried a given number of times by selecting
the Retry on Error check box and using the following fields:
• Max Retry
Enter the maximum number of retries using the adjacent arrow buttons.
• Delay
Enter the wait time between retries using the adjacent arrow buttons.
100 Id:0900d8058018db2b E200613-01-114-V14.0I-23

4.4.2 Scheduler Browser

Viewing the status of each Scheduled Task
The Scheduler window can be accessed via:
> Utils task-tree folder > Scheduler Browser task-tree item
The Scheduler Browser window allows the Administrator to view the status of each
scheduled job. You can view the tasks associated to the selected job and its results can
be reproduced.
Figure 45 Scheduler Browser window

• Click Refresh to update the Details Table.

• Click Get Result to obtain the results produced by a specific selected task.
Jobs Table
The Jobs Table allows you to view the status of each executed job. The field displays
the general job properties in table columns.
• Status
Displays an icon representing the job status.
• Name
Displays the job name.
• Start
Displays the date and time at which the job execution attempt started.
• End
Displays the date and time at which the job execution ended.
• Message
Displays the status of the job execution in greater detail.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 101

Details Table
The Details Table allows you to view the status of every task included in the job
selected in the Jobs Table. The table can be hidden or expanded by clicking the Details
expandable box. The field displays each task’s properties in table columns.
• Status
Displays an icon representing the specific task status.
• Name
Displays the task name.
• Start
Displays the date and time at which each specific task execution attempt started.
• End
Displays the date and time at which each specific task execution ended.
• Message
Displays the status of each task execution in greater detail.
The toolbar buttons above are also available in a context menu by right clicking the
Details Table.
4.4.3 Task Administration window

Viewing the status of each Scheduled Task
The Task Administration window can be accessed via:
> Scheduler window > Tasks List context menu item
The Task Administration window allows the Administrator to select the tasks to be
executed in a specific job. Jobs can be created using the Scheduler window (see 4.4.1).
102 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 46 Task Administration window

Tasks List
The Tasks List displays the tasks available from the My Tasks and My Reports lists.
Tasks can be selected to be included in a report by using the following buttons:
• Click Add Items to move all selected tasks from the Tasks list to the Selection
list.
• Click Remove Items to remove all selected tasks to the Tasks list.
Selection List
The Selection List displays the tasks selected from the Tasks List.
The selection can be confirmed using the following buttons, located at the bottom of the
window:
• Click OK to confirm the task selection.
• Click Cancel to leave the window without changing the settings of the task selection.
4.4.4 My Tasks
The My Tasks list can be viewed by expanding the:
> My Tasks task-tree folder
The My Tasks task-tree folder displays all saved Data Administration tasks. Both
saved and scheduled tasks can be viewed in the My Tasks expandable list. Tasks can
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 103

be added to the My Tasks list by using the following toolbar buttons available in the
Load Data (see 4.2.1), Delete Data (see 4.2.2), Data Aggregation (see 4.2.3), and Make
History (see 4.2.4) windows:
• Click Save Task to save any Data Administration task to the My Tasks list.
• Click Schedule Task to schedule the execution of any Data Administration
task using the Scheduler window (see 4.4.1). The scheduled task is also added to
the My Tasks list.
Figure 47 My Tasks List

The task-tree contains the following context menu.
• Click Open to open the selected task window.

• Click Remove to delete the selected task from the list.
• Click Rename to rename the selected task.
• Click Expand to show all tasks contained in the selected task-tree folder.
• Click Collapse to hide all tasks contained in the selected task-tree folder.
Public Tasks
Any user belonging to the Administrators User Group can select any given task's avail-
ability to the public or private user domain. In New Public Task figure, the task is listed
under the Public Tasks feature. InNew Private Task figure, the task is only visible to the
user that created it, listed under the feature "My Tasks". An option is available in the
Save Task dialog box that supports the choice of the created task's visibility. Select one
option to determine if the task is available publicly or privately.
104 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 48 New Public Task
Figure 49 New Private Task

When you are not an administrator and do not have enough privileges to save a public
task, the options are inactive, with the Private option selected, in order to give a clear
indication that the operation is not permitted.
4.5 Online Monitoring Utilities
4.5.1 Alarm Browser window

The Alarm Browser can be accessed via:
> Real Time Utils task-tree folder > Alarm Browser task-tree item
The Alarm Browser window displays all the generated alarms in a table. In this table
you can view important information regarding each alarm. The table filters in Alarm
Browser offer several filtering options. You can define conditional filters (>, <, >=, <=)
instead of just equality and/or inequality. There is also the option of defining filters for
fields not available on the Alarm Icon filter, such as, Instance, Domain, Clear Time, Time
and Counter.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 105

Figure 50 Alarm Browser window
Alarms Browser
The Alarms Browser tab displays all the alarms’ information in table columns:
• Severity
Displays the severity level associated to the alarm.
• Clear Time
Displays the time in which the alarm was cleared. A checked box corresponds to a
cleared alarm.
• Time
Displays the time at which the alarm was issued.
• Counter
Displays the name of the counter associated to the alarm.
• Instance
Displays the name of the instance associated to the alarm.
• Domain
Displays the domain in which the alarm was issued.
Objects Browser
The Objects Browser tab allows you to view the current measurement of each network
object.
g There is a functional similarity between Alarm Browser's filters and Alarm Filter Editor
(see 4.6.2.4), but the scope is different. The Alarm Browser's filter has a limited scope
inside that particular feature, by impacting on the alarms that reach the table, though it
is very configurable and powerful. On the other hand, when defining a filter in the Alarm
Icon feature, we are controlling which alarms should fire alerts (either by visual or sonic
means). This last feature is available throughout the whole framework, despite being
less customizable.
106 Id:0900d8058018db2b E200613-01-114-V14.0I-23

4.5.2 Threshold Lifecycle window

The Threshold Lifecycle can be accessed via:
> Real Time Utils task-tree folder > Threshold Lifecycle task-tree item
The Threshold Lifecycle window allows you to manage monitored metric counters for
SPOTS Online Monitoring. Enable the real-time counter monitoring by creating an
associated monitored metric. A monitored metric counter allows you to define threshold
conditions and severity level warnings, providing you a real-time overview of abnormal
operating conditions.
Figure 51 Threshold Lifecycle window

Class Tree
In this field you can view and select the available counters by browsing through their
object classes. A monitored metric can be associated to a counter by using the following
context menu:
• Click Create Monitored Metric to enable the real-time counter monitoring using the
Create Monitored Metric window (see 4.5.2.1).
• Click Update Monitored Metric to edit a monitored metric counter.
• Click Delete Monitored Metric to disable the real-time counter monitoring.
Reference Counter Information

The parameters defined in this field can be activated by selecting the following check
box. Select the Use Reference Counter check box to enable monitoring a counter
against another reference counter. In this field you can specify the reference counter
parameters.
• Reference Counter Name
Select the reference counter from the drop-down list.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 107

• Reference Value
Specify the reference value at which an alarm is triggered.
• Cross Direction
Specify at which cross direction an alarm is triggered.
Threshold Information
This field allows you to create, edit and delete thresholds. You can specify the threshold
class by using the Threshold Class drop-down menu. Select a threshold class from the
drop-down menu. Threshold classes can be created, edited or deleted using the
Threshold Classes window (see 4.5.3).
You can activate and deactivate all thresholds simultaneously by using the following
buttons.
• Click Activate All to activate all thresholds in the threshold table below.
• Click Deactivate All to deactivate all thresholds in the threshold table below.
This field displays all threshold information in table columns.
• Name
Displays the name of the monitored metric counter.
• Value
Displays the threshold value.
• Severity
Displays each individually associated severity level.
• Clear Percentage
Displays the alarm reset condition.
• Cross Direction
Displays the alarm triggering cross direction.
• Activation State
Displays whether each specific threshold is activated or deactivated.
• Monitored Period
The Monitored Period table column allows you to edit each threshold monitored
period using the Monitored Period Editor window (see 4.5.2.3).
• Default
Indicates the default threshold by its check box selected state.
You can create, edit or delete thresholds by using the following buttons:
• Click Create to create a new threshold associated to the selected monitored metric
counter using the Create Threshold Value window (see 4.5.2.2).
• Click Update to edit the selected threshold.
• Click Delete to delete the selected threshold.
4.5.2.1 Create Monitored Metric window

The Create Monitored Metric can be accessed via:
> Threshold Lifecycle window > Create Monitored Metric context menu item
The Create Monitored Metric window allows you to enable real time monitoring of
specific counters. The monitored counter can be evaluated in different ways, against
predefined threshold values or against other monitored reference counters. The Create
Monitored Metric window allows you to set the parameters of the reference counter
evaluation.
108 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 52 Create Monitored Metric window

Reference Counter Information

The parameters defined in this field can be activated by selecting the Select the Use
Reference Counter check box to enable monitoring a counter against another refer-
ence counter. In this field you can specify the reference counter parameters.
g If a Reference Counter is used, the alarm will be raised only if both Reference Counter-
value and Threshold value are crossed, and will be cleared only if it fulfills the Clear
Value for the threshold.
• Reference Counter Name

Select the reference counter from the drop-down list.
• Reference Value
Specify the reference value at which an alarm is triggered.
• Cross Direction
Specify at which cross direction an alarm is triggered.
The window has two buttons located at the bottom of the window:
• Click Create to leave the window and save the changes or enable a real time mon-
itoring counter.
4.5.2.2 Create Threshold Value

The Create Threshold Value can be accessed via:
> Threshold Lifecycle window > Create button
The Create Threshold Value window allows you to define a threshold value to the mon-
itored counter. You can set threshold information, such as severity levels and cross
information as well as threshold values. A time period can also be defined during which
the threshold condition is active.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 109

Figure 53 Create Threshold Value window

Threshold Information
In this field you can specify the threshold’s main information:
• Threshold Name
Specify the name to be given to the threshold value.
• Severity
Select the severity level to be associated with the threshold value from the drop-
down menu.
• Activation State
Select the activation state from the drop-down menu to be associated with the
threshold value.
Cross Information
In this field you can set the counter measurement value at which the alarm is triggered.
The Value specifies the exact counter measurement reading at which the alarm is trig-
gered.
The condition, at which the alarm state is reset, is done by selecting one of the following
radio buttons:
110 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Select Clear Percentage to reset the alarm state once the current counter measure-
ment reaches a specific percentage of the threshold value, depending on the
selected type of Cross Direction. The alarm reset threshold percentage value can
be entered in the Clear Percentage text box.
Note:
If the input is Clear Percentage, the threshold's Clear Value is calculated as follows:
– For Cross Direction UP: Clear Value = Threshold Value - (Clear Percent-
age/100)* Threshold Value
– For Cross Direction DOWN: Clear Value = Threshold Value + (Clear Percent-
age/100)* Threshold Value
• Select Clear Value to reset the alarm state once the current counter measurement
reaches the specific counter measurement value. The alarm reset counter measure-
ment value can be entered in the Clear Value text box.
In this field you can specify the alarm trigger action using the Cross Direction drop-
down menu. It allows you to select whether the alarm is triggered as the counter mea-
surement rises or falls from the threshold value.
Additional Information
In this field you can supply relevant information such as links to help pages, procedures
to overcome the alarm event, among others. This information is displayed when an
alarm is generated.
The window has three buttons, located at the bottom of the window:
• Click Monitored Period to edit the time period during which the threshold con-
dition is active, using the Monitored Period Editor window (see 4.5.2.3).
• Click Create to save the threshold settings and leave the window.
• Click Cancel to exit the window without saving the threshold settings.
4.5.2.3 Monitored Period Editor window

The Monitored Period Editor can be accessed via:
> Create Threshold Value window > Monitored Period button
The Monitored Period Editor window displays all the time periods during which the
threshold condition is active. On each day of the week several time periods can be set,
enabling the threshold condition to be active at specific times only, such as peak times.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 111

Figure 54 Monitored Period Editor

Monitored Period Editor

In this field you can View, Edit or Add a period.
To View a complete list of the defined periods for a specific day click Details button
to access the Monitored Period Details window (see 4.5.2.5)
To Edit a previously defined monitoring period double-click the intended period to
access the Period Definition window (see 4.5.2.4).
To Add a new monitoring Period click the Add Period button to access the Period Def-
inition window (see 4.5.2.4)
You can exit the window by using the following buttons:
• Click Ok to save the monitoring time period and leave the window.
• Click Cancel to exit the window without saving the monitoring time period settings.
4.5.2.4 Period Definition window

The Period Definition can be accessed via:
> Create Threshold Value window > Monitored Period button > Add Period button
The Period Definition window allows you to define a new monitoring period.
112 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 55 Period Definition

Days
This field allows you to select one of four possible configurations:
• All
The defined monitoring period is valid for all days.
• Working Days
The defined monitoring period is valid for specified working days defined by you.
• Non Working Days
The defined monitoring period is valid for weekends only.
• Custom Selection
The defined monitoring period is only valid on the days selected by you. To select a
day click the corresponding check box.
Period
In this field you can set the active period of the threshold’s time condition by using the
24 hour time bars. Drag each slider pair to the start and end time positions required. The
corresponding start and end times are displayed adjacently to the time bar. The blue
time bar section represents the time during which the threshold is active.
You can exit the window by using the following buttons:
• Click OK to save the monitoring time period and leave the window.
• Click Cancel to exit the window without saving the monitoring time period settings.
4.5.2.5 Monitored Period Details window

The Monitored Period Details can be accessed via:
> Create Threshold Value window > button

The Monitored Period Details window gives a complete list of the defined periods for
a specific day.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 113

Figure 56 Monitored Period Details

The window displays the period properties in table columns.
• Start
Displays the starting time of the monitored periods.
• End
Displays the ending time of the monitored periods.
The task has two buttons, located on the left side of the window:
• Click Edit to leave the window and edit the selected period on the Period Defi-
nition window (see 4.5.2.4).
• Click Erase to delete the selected period.
The window has Close button, located at the bottom of the window. Click to exit the
window.
4.5.2.6 Import and Export Thresholds

The Import and Export tasks are accessed via:
Thresholds menu > Import Thresholds and Export Thresholds menu items
The Import and Export tasks allow you to import and export all the Thresholds, from
and into, CSV files. CSV files have a pre-defined format (see 5.1.1) and can be opened
using MS Excel.
Importing
The Importing window has a File text box in which you can input the filename and the
path of the file to be imported. The filename and path can also be specified by using the
Select button. Click the Select button to select the file by browsing the system folders.
Selecting a file automatically specifies its filename and path in the File text box.
The window has two check boxes to enable the following options:
• Overwrite definitions
If checked, the file imported substitutes all existing thresholds with the ones con-
tained in the file being imported.
• Simulate definitions
If checked, the file imported simulates the loading of the input file, but no changes
are made. This option is useful to check if the input file is correct and to check how
many thresholds are loaded and deleted.
This window has two buttons, located at the bottom of the window:
• Click OK to start the task.
• Click Cancel to leave the window without completing the task.
114 Id:0900d8058018db2b E200613-01-114-V14.0I-23

g A Log is presented after the task is completed with information regarding the import
operation.
Exporting
The Exporting window has a File text box in which you can input the filename. To select
the folder in which the file is stored you can use the available browser.
g Default Values are set by SPOTS when exporting Thresholds to CSV.
4.5.2.7 Delete Thresholds

The Delete Thresholds task is accessed via:
Thresholds menu > Delete Thresholds menu item
The Delete Thresholds task allows you to delete all the thresholds available in the
system. If no thresholds are defined this option is not available.
4.5.3 Threshold Classes window

The Threshold Classes can be accessed via:
> Real Time Utils task-tree folder > Threshold Classes task-tree item
The Threshold Classes window allows you to manage Threshold Classes for SPOTS
Online Monitoring. You can create, edit or delete Threshold Classes by associating
them to the available network objects.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 115

Figure 57 Threshold Classes window

Class Tree
The Class Tree contains all the available object classes. Select the object class to be
associated to the threshold.
Threshold Classes
In the Threshold Classes field you can create edit or delete threshold classes. The User
Defined Threshold Classes list displays all the threshold classes created by you. You
can configure the threshold classes by using the following buttons:
• Click New to create a new threshold class. The new threshold class can include
copies of network objects selections from existing threshold classes by using the
Copy Thresholds From drop-down menu.
• Click Rename to edit the name given to the threshold class.
• Click Delete to remove the selected threshold class.
Threshold Class Object Selection

In the Threshold Class Object Selection you can add and remove network objects
from each threshold class. The field contains two Network Objects lists. The network
objects contained in the Network Objects lists correspond to the threshold class
selected in each drop-down. The menu is located above each list. The drop-down
menus contain two predefined threshold classes:
116 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Unclassified
Contains all network objects that do not belong to a user created threshold class or
to the Black List.
• Black List
Contains all objects that are not monitored.
The network objects can be added to the different threshold classes by using the follow-
ing buttons:
• Click Add to move all selected network objects between threshold classes.
• Click Remove to remove all selected network objects from the selected thresh-
old class.
In this field you can specify the date interval type by selecting one of the following radio
buttons:
• Click Save to save the threshold class changes and close the window.
g A network object can only be included in one threshold class. The use of Black List fil-
tering is highly recommended as it improves the overall performance and reduces object
search time. Wildcard filtering allows all hierarchically dependent objects to also be
included by a particular filter.
4.5.3.1 Import and Export Thresholds Classes

The Import and Export tasks are accessed via:
Thresholds Classes menu > Import Thresholds Classes and Export Thresholds
Classes menu items
The Import and Export tasks allow you to import and export all the Thresholds
Classes, from and into, CSV files. CSV files have a pre-defined format (see 5.1.2) and
can be opened using MS Excel.
Importing
The Importing window has a File text box in which you can input the filename and the
path of the file to be imported. The filename and path can also be specified by using the
Select button. Click the Select button to select the file by browsing the system folders.
Selecting a file automatically specifies its filename and path into the File text box.
The window has two check boxes to enable the following options:
• Overwrite definitions
If checked, the file imported substitutes all existing thresholds with the ones con-
tained in the file being imported.
• Simulate definitions
If checked, the file imported simulates the loading of the input file, but no changes
are made. This option is useful to check if the input file is correct and to check how
many thresholds are loaded and deleted.
g A log is presented after the task is completed with information regarding the import oper-
ation.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 117

Exporting
The Exporting window has a File text box in which you can input the filename. To select
the folder in which the file is stored, you can use the available browser.
g Default Values are set by SPOTS when exporting the Thresholds Classes to CSV.
4.5.3.2 Delete Threshold Classes

The Delete Threshold Classes task is accessed via:
Threshold Classes menu > Delete Threshold Classes menu item
The Delete Threshold Classes task allows you to delete all the threshold classes avail-
able in the system. If no threshold classes are defined this option is not available.
4.5.4 Threshold Viewer window

The Threshold Viewer can be accessed via:
> Real Time Utils task-tree folder > Threshold Viewer task-tree item
The Threshold Viewer window displays all the created thresholds in a table. In this
table you can view important information regarding each threshold.
Figure 58 Thresholds Viewer window

The window displays all the threshold’s information in table columns.
• Severity
Displays each individually associated severity level.
• Name
Displays the name of the threshold.
• Counter
Displays the name of the monitored metric counter.
• Direction
Displays the alarm triggering cross direction.
118 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Value
Displays the threshold value.
The Thresholds Viewer window also provides a drop down menu above the scroll bar
which contains the following tasks in a context menu:
• Hide
• Columns
Tab.
• Show
• Sorting...
– Add
– Remove
• Filters
• No Filter
• Filter Editor
Runs the Filter Editor (see 4.6.1.7) configuration window.
• Export Data...
• Refresh
Makes an update to the Instances list.
g All columns allow you to make an ascending or descending sort by clicking on the cor-
responding list title.
4.5.5 PDC Types window

The PDC Types can be accessed via:
> Real Time Utils task-tree folder > PDC Types task-tree item
The PDC Types window allows you to register Performance Data Collection Monitor
Agents, enabling SPOTS real time monitoring. All agent types supported by SPOTS are
displayed, allowing Monitor Agents to be registered according to their type.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 119

Figure 59 PDC Types window

Agent Type Tree

In this field you can view all types of agents supported by SPOTS. Agent types are asso-
ciated to the installed TPs. Agents are organized in the Agent Type Tree according to
their type.
A context menu can be found by right clicking the agent name.
• Click Register Agent to create a new Performance Data Collection agent, asso-
ciated to an agent type.
• Click Unregister Agent to remove an agent from the Agent Type Tree.
• Click Start Agent to activate the selected agent's real time performance data mon-
itoring. In order to start an agent, its associated agency must be activated.
• Click Stop Agent to deactivate the selected agent's real time performance data
monitoring.
• Click Change Primary Domain to view another domain's Agent Type Tree.
To upgrade an Agent Type, right-click the type you want to upgrade and then click
Upgrade Agents of this Type:
Agent Properties
In this field you can view the specific properties of the agent selected in the Agent Type
Tree. The following properties can be viewed in the Agent Properties field:
• Agency Name
Displays the agent name.
120 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Agency
Displays the associated agency.
• Agency Type
Displays the agent type.
• Agent State
Displays the current agent activation state.
• Agent Automatic Start
Displays the state of the automatic agent start up.
• Agent Primary Domain
Displays the associated primary domain.
4.5.6 PDC Platform window

The PDC Platform can be accessed via:
> Real Time Utils task-tree folder > PDC Platform task-tree item
The PDC Platform window allows you to register Performance Data Collection (PDC)
agencies, enabling SPOTS real time monitoring. Agents are also displayed associated
to their respective agencies. Each PDC server supported must have an associated
Monitor Agency (MA). The MAs provide the platform on which the Monitor software
Agents perform the monitoring tasks.
g In order to register a new agency, the "agencylauncher" service is must be run on the
machine where the agency is to be created.
Figure 60 PDC Platform window

Agencies Tree
In this field you can view all agencies and respective agents. You can create or delete
agencies and activate or deactivate their agents.
A context menu can be found by right clicking the agency name.
• Click Register Agency to create a new MA.
• Click Unregister Agency to remove the selected MA.
• Click Start Agency to activate the selected Monitor Agency.
• Click Stop Agency to deactivate the selected Monitor Agency.
• Click Start Agents of this Agency to activate all the agents contained in the
selected agency. In order to start an agent, its associated agency must be activated.
• Click Stop Agents of this Agency to deactivate all the agents contained in the
selected agency.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 121

Agency Properties
In this field you can view the specific properties of both agencies and agents selected in
the Agencies Tree. The following properties can be viewed in the Agency Properties
field:
• Agency Name
Displays the agent name.
• Agency Host
Displays the associated PDC server host IP address.
• Agent State
Displays the current agent activation state.
• Agent Automatic Start
Displays the state of the automatic agent start up.
4.6 Reports
4.6.1 Trend Analysis Reports
4.6.1.1 Ad-Hoc Report

Ad-Hoc Report window
The Ad-Hoc Report can be accessed via:
> Reports task-tree folder > Ad-Hoc Report task-tree item
The Ad-Hoc Report window provides you an overview of the previously set parameters
required to execute a report in SPOTS. The Ad-Hoc Report window allows you to
analyze Trend Analysis measurement data in graph or table formats. By default, the
Ad-Hoc Report Wizard is opened automatically upon selection of the Ad-Hoc Report
task-tree item, however, it can be configured in the Preferences window (see Prefer-
ences window).
122 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 61 Ad-Hoc Report window

This window has specific toolbar buttons, located at the top of the SPOTS main window:
• Click Wizard to set the report parameters using the Report Wizard.
• Click Open Class Browser to select or modify the previously selected object
instances and counters using the Class Browser window (see Class Browser
window).
• Click Report Properties to view previously set parameters and set report output
options using the Report Properties window (see Report Properties window).
• Click Execute Report to execute the Report with the currently set parameters.
• Click Stop Report to halt the execution of the Report.
• Click Schedule Report to postpone the execution of a report to a specified date
and time.
• Click Save Report to save the report parameters, enabling a latter execution.
Date Interval
buttons:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 123


Using the drop-down menu you can select the time span to be analyzed in the report
by specifying the start and finish dates.
• Keyword
Using the drop-down menu you can select a relative time span to be analyzed in the
report. Ultimately, the time span considered in the report is relative to the present
date and time. This option enables the report refresh functionality, allowing the
report to be updated periodically at a specific rate.
Refresh
In this field you can enable the periodic update of the report by selecting the Use
Refresh check box. The graph or table report is then automatically updated as soon as
new measurement data is loaded into the database.
Data Source
In this field you can select the Trend Analysis data type and its granularity. The left
drop-down menu enables you to select the type of data to use in the report. The right
drop-down menu enables you to select the data sample rate to use in the report.
Objects
This field contains a list displaying the selected object instances to be evaluated in the
report. The contents of the list can be hidden or expanded by clicking the Objects
expandable box.
The list is a table with two column fields:
• Name
This field displays the name of the object.
• Aggregate
This field allows you to select a Set of Objects as distinct or aggregate by clicking
the correspondent check box. When unchecked the correspondent objects of the set
are used by the system as distinct objects.
Counters
This field contains a list displaying the selected measurements, virtual and sets of
counters to be evaluated in the report. The items in the selection list correspond to either
the number of data series in graph reports or data columns in table reports. The contents
of the list can be hidden or expanded by clicking the Counters expandable box.
Results
In this field you are given an overview of the generated reports. The results overview is
shown by clicking the Execute Report toolbar button. The field has the Show only
one window check box. Select the Show only one window check box to display only
one report at a given time.
A description of each result produced, comprised of its object’s and counter’s names, is
provided, followed by the 1, 2, 3... (numbered buttons) button. An array of sequentially
numbered buttons identify each result produced. Click a numbered button to generate
the related Report Output in a separate window.
Ad-Hoc Report Wizard

The Report Wizard can be accessed via:
124 Id:0900d8058018db2b E200613-01-114-V14.0I-23

> Reports task-tree folder > Ad-Hoc Report task-tree item > Report Wizard toolbar
button
The Report Wizard window allows you to set the parameters required to execute a report
in SPOTS. The Ad-Hoc Report window allows you to analyze Trend Analysis mea-
surement data in graph or table formats. By default, the wizard is opened automatically
upon selection of the Ad-Hoc Report (see Ad-Hoc Report) task-tree item, however, it can
be configured in the Preferences window (see Preferences window).
• Click Previous to go to the previous step of the wizard.
This button is disabled both in the first and last steps of the wizard.
• Click Next to go to the next step of the wizard.
This button is disabled in the last two steps of the wizard.
• Click Finish to validate the settings and execute a Report.
This button is enabled in the last two steps of the wizard.
• Click Cancel to leave the wizard without changing the settings.
This button changes to Close in the last step of the wizard.
The Contents field provides an overview of the different steps of the wizard. The wizard
has the following steps:
Step 1: Date Interval and Data Type Selection

This step allows you to set the data type and respective collection dates for the report.
Figure 62 Ad-Hoc Report Creation Wizard - Step1

E200613-01-114-V14.0I-23 Id:0900d8058018db2b 125

Date Interval
buttons:
• Keyword
Data Source
Refresh
Step 2: Objects Instances Selection

This step allows you to select the network objects to be evaluated in the report.

Class Tree
126 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Instances, Sets and Expression Editor Lists

• Name
• User label
Displays the user label of the instance.
lowing buttons:
list.
information contained in their Extended Fields. This tab has the following icons:
• Click New to add a new expression.

• Click Open to open a existing expression.
• Click Save the created expressions, in public or private form.
• Click Cut to cut the expression.
• Click Copy to copy the expression.
• Click Paste to paste the expression.
• Click the Execute Report to return the results of the current expression. This
button is only visible if the expression created is valid. This is noted by the Success-
ful and Failed icons in the lower right corner of the expression editor.
• Click Import Instance to browse active filters.
The Sets Tab and Instances Tab lists contains a context menu by right clicking the
mouse.
• Add Items
• Select All
bar which contains the following tasks in a context menu:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 127

• Hide
• Columns
Tab.
• Show
• Sorting...
you can create new sort or delete the existing ones by using:
– Add
Adds a new sorting function.
– Remove
• Filters
• No Filter
• Filter Editor
• Export Data...
• Refresh
g Both lists allow you to make a sort in ascending or descending order by Name and/or
User Label by clicking on the corresponding list title.
Selection List
• Remove Items
• Select All
Step 3: Counters Selection

This step allows you to select the measurement counters, virtual counters and set of
counters to be evaluated in the report.
128 Id:0900d8058018db2b E200613-01-114-V14.0I-23



selected object class.
differs from the Sets of Counters measurement class in the Measurements Tab. It
Counters Table
• Name
• Description
Provides a brief description of each counter’s properties.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 129

buttons:
tion list.
Counters Table.
• Add Items
• Select All
• Hide
• Columns
Sets Tab.
• Show
• Sorting...
the column to sort and the mode of sorting (Ascending or Descending). Addition-
ally you can create new sort or delete the existing ones by using:
– Add
– Remove
• Filters
• No Filter
• Filter Editor
• Export Data...
• Refresh
g Both lists allow you to make a sort in ascending or descending order by Name or
Description, or both, by clicking on the correspondent list title.
130 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Selection List
• Remove Items
• Select All
Step 4: Extended Fields

This step allows you to select the extended fields to be included in the report output.
Step 5: Report Properties

This step allows you to set additional report output options.
General Tab
The General tab allows you to set the report’s main properties.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 131

Figure 66 Ad-Hoc Report Creation Wizard - Step5 (General tab)

Type
In this field you are able to select the type of report to be created. The following report
types are available:
• Table
The report measurements are displayed in a table.
• Graph
The report measurements are plotted in a graph.
• Excel
The report measurements are exported to a CSV file that can be opened with MS
Excel. If MS Excel is not installed, the option is greyed out and a tooltip stating this
is displayed on mouse hover.
Group By
In this field you can group performance indicators by selecting the Grouping check box.
The performance indicators can be grouped by objects or variables by selecting the
respective check boxes.
Title
In this field you can type in the name to be given to the report.
g The Refresh option is available when a relative date interval has been previously
selected in the Report Wizard - Date Interval and Data Source step.
Output Tab
The Output tab allows you to set the report output type.
132 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 67 Ad-Hoc Report Creation Wizard - Step5 (Output tab)

Output Type When Scheduled

In this field you are able to select the type of report output. The following types are avail-
able by selecting the respective radio buttons:
• Screen
Select the Screen radio button to display the report in the computer monitor. This
option is selected by default.
• File
Select the File radio button, type the name and select the type of file to be created.
The file is created in the associated SPOTS Application Server. Additionally you can
add the date and time of the system when the file was saved, by typing %D%T after
the filename. Example: Testfile%D%T
• Printer
Select the Printer radio button and type the path and name of the printer to print the
report. The file is sent to the printers associated with the SPOTS Application Server.
g This option is available when the report is scheduled. A Report can be printed locally on
a printer associated with the SPOTS Client by selecting the Screen radio button, and
selecting Print when the report has been generated.
Options Tab (for table reports)

The Options tab allows you to set report display options.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 133

Figure 68 Ad-Hoc Report Creation Wizard - Step5 (Options tab for table reports)
In the window you can set the following parameters:
• Show Only Last Interval
Select the Show Only Last Interval check box to display the data corresponding to
the last interval of time.
• Remove lines without data
Select the Remove lines without data check box to remove, from the displayed
table, the rows without data.
• Header Rotation Degrees
The header rotation angle can be set by using the drop down menu.
• Header Font
Select the font format for the table header.
• Cells Font
Select the font format for the table cells.
Appearance Tab (for table reports)

The Appearance tab allows you to set the table color patterns.
134 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Header
In this field you are able to set the Header Background color.
Date/Time Cells
In this field you are able to set the Cell’s Background color.
Objects Cells
In this field you are able to set the Odd and Even Cell’s Background colors.
Counters Cells
All chosen color patterns can be applied to the table report by selecting the Apply Color
Patterns check box.
Options Tab (for chart reports)

E200613-01-114-V14.0I-23 Id:0900d8058018db2b 135

136 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 70 Ad-Hoc Report Creation Wizard - Step5 (Options tab for chart reports)
Chart Properties
In this field you are able to set the following parameters:
• Chart Type
The Chart Type is set by selecting the type of chart display (Line, Area, Bar, among
others) from the drop down menu.
• Border
The Border is set by selecting the type of border to apply to the chart (None, Etched,
Black Line, among others) from the drop down menu.
• Show Grid
Select the check box to enable a grid in the displayed chart.
• Grid Spacing
The Grid Spacing allows you to set the spacing between grids.
• Unit
The Unit is set by selecting the unit in which the data is presented in the chart (%,
Erl, Kbps, among others) from the drop down menu.
• 3D Effect
The 3D Effect is only available for Bar and Stacked Bar chart types. Select the
check box to enable a 3D effect to the chart.
Axis Definitions
In this field you are able to define the minimum and maximum values of the axis and
define threshold lines to be displayed in the chart. The following buttons are provided:
• Add
Click Add to limit the axis by setting a minimum, maximum or a threshold to a unit.
• Remove
Click Remove to remove the selected Axis Definition.
• Edit
Click Edit to change the properties of the selected Axis Definition.
All set axis definitions are displayed in table columns.
Legend
In this field you are able to add a legend to the chart and set its position.
• Show Legend
Select the check box to enable a legend to be displayed.
• Location
Select the location of the legend from the drop down menu.
Appearance Tab (for chart reports)

The Appearance tab allows you to set the chart color patterns.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 137

Backgrounds
In this field you are able to set the Chart Background Color.
Series Colors
In this field you are able to set the color for each individual series by using a table.
4.6.1.2 Ad-Hoc Comparison Report

Ad-Hoc Comparison Report window
The Ad-Hoc Comparison Report can be accessed via:
> Reports task-tree folder > Ad-Hoc Comparison Report task-tree item
The Ad-Hoc Comparison Report window provides you an overview of the previously set
parameters required to execute a comparison report in SPOTS. The comparison report
allows you to view normal Trend Analysis measurement data shown against data from
a different time period, allowing a direct comparison to be made. The Trend Analysis
measurement data for both Date and Comparison Intervals is obtained from the same
Object Class and Counter. By default, the Ad-Hoc Comparison Report Wizard is
opened automatically upon selection of the Ad-Hoc Comparison Report task-tree
item, but it can be configured in the Preferences window (see Preferences window).
138 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 72 Ad-Hoc Comparison Report window

window).
and time.
• Click Save Report to save the report parameters, enabling a later execution.
Date Interval
In this field you can specify the original date interval type of the measurements to be
compared, by selecting one of the following radio buttons:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 139


• Keyword
Comparison Interval
In this field you can specify the comparison date interval of the measurements to be
compared in the report, by selecting one of the following radio buttons:
Using the drop-down menu you can select the time span to be compared in the
report by specifying the start and finish dates.
• Average Days
Using the drop-down menu you can select an average day measurements to be
compared with the original data in the report.
• Average Weeks
Using the drop-down menu you can select an average week’s measurements to be
Refresh
Data Source
Objects
report. The same objects instances are evaluated for both original and comparison inter-
vals. The contents of the list can be hidden or expanded by clicking the Objects expand-
able box.
• Name
• Aggregate
Counters
This field contains a list displaying the selected measurements, virtual and sets of
counters to be evaluated in the report. The items in the selection list correspond to either
the number of data series in graph reports or data columns in table reports. The contents
of the list can be hidden or expanded by clicking the Counters expandable box.
140 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Results
In this field you are given an overview of the generated comparison reports. The results
overview is shown by clicking the Execute Report toolbar button. The field has the
Show only one window check box. Select the Show only one window check box to
display only one report at a given time.
A description of each result produced, comprised of its object’s and counter’s names, is
the related Report Output (see Report Output window) in a separate window.
Ad-Hoc Comparison Report Wizard

The Comparison Report Wizard can be accessed via:
> Reports task-tree folder > Ad-Hoc Comparison Report task-tree item > Report Wizard
toolbar button
The Ad-Hoc Comparison Report wizard allows you to set the parameters required to
execute a report in SPOTS. The comparison report allows you to view normal Trend
Analysis measurement data shown against data from a different time period, allowing
a direct comparison to be made. The Trend Analysis measurement data for both Date
and Comparison Intervals is obtained from the same Object Class and Counter. By
default, the wizard is opened automatically upon selection of the Ad-Hoc Comparison
Report (see Ad-Hoc Comparison Report) task-tree item, but it can be configured in the
Preferences window (see Preferences window).
• Click Back to go to the previous step of the wizard.

E200613-01-114-V14.0I-23 Id:0900d8058018db2b 141


Date Interval
In this field you can specify the original date interval type of the measurements to be
compared, by selecting one of the following radio buttons:
• Keyword
Comparison Interval
In this field you can specify the comparison date interval of the measurements to be
compared in the report, by selecting one of the following radio buttons:
Using the drop-down menu you can select the time span to be compared in the
report by specifying the start and finish dates.
• Average Days
Using the drop-down menu you can select an average day measurements to be
• Average Weeks
Using the drop-down menu you can select an average week’s measurements to be
Data Source
142 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Refresh

This step allows you to select the network objects to be evaluated in the report.

Class Tree

• Name
• User label
lowing buttons:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 143

list.
information contained in their Extended Fields, using the RNCOC class and the EF
"RNC Name". See picture below.
Figure 75 Expression Editor Tab window
Click the Execute Report toolbar button to return the results of the current expres-
sion.This button is only visible if the expression created is valid. This is noted by the Suc-
cessful and Failed icons in the lower right corner of the expression editor.
• Click The expression is valid.

• Click There is an error (the error can then be determined by hovering the
mouse cursor over the icon).
• Click Save the created Expressions, in public or private form.
mouse.
• Add Items
• Select All
bar which contains the following tasks in a context menu.
144 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Hide
• Columns
Tab.
• Show
• Sorting...
– Add
– Remove
• Filters
• No Filter
• Filter Editor
• Export Data...
• Refresh
g Both lists allow you to make a sort in ascending or descending order by Name or User
Label, or both, by clicking on the corresponding list title.
Selection List
• Remove Items
• Select All
Selects all the items in the Selection’s list.
Step 3: Counters Selection

This step allows you to select the measurement counters, virtual counters and sets of
counters to be evaluated in the report.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 145



Counters Table
• Counters
• Description
Provides a brief description of each counter’s properties.
buttons:
tion list.
146 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Counters Table.
• Add Items
• Select All
The Counters Table list also provide a drop down menu above the scroll bar which
• Hide
• Columns
Sets Tab.
• Show
• Sorting...
you can create a new sort or delete the existing ones by using:
– Add
Adds a new sort function.
– Remove
• Filters
• No Filter
• Filter Editor
• Export Data...
• Refresh
g Both lists allow you to make a sort in ascending or descending order by Name or
Description, or both, by clicking on the corresponding list title.
Selection List
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 147

• Remove Items
• Select All

General Tab
Figure 77 Ad-Hoc Report Creation Wizard - Step4 (General tab)

Type
• Table
• Graph
The report measurements are plotted into a graph.
• Excel
The report measurements are exported to an excel sheet.
148 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Group By
Title
Type in the name to be given to the report.
Output Tab
Figure 78 Ad-Hoc Report Creation Wizard - Step4 (Output tab)


• Screen
• File
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 149

• Printer
a printer associated with the SPOTS Client by selecting Screen radio button, and select-
ing Print when the report has been generated.

Figure 79 Ad-Hoc Report Creation Wizard - Step4 (Options tab for table reports)
• Header Font
• Cells Font
Select the font format for the table’s cells.

150 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Header
Date/Time Cells
Objects Cells
Counters Cells
Patterns check box.

E200613-01-114-V14.0I-23 Id:0900d8058018db2b 151

Figure 81 Ad-Hoc Report Creation Wizard - Step4 (Options tab for chart reports)
Chart Properties
• Chart Type
• Border
• Show Grid
• Grid Spacing
• Unit
• 3D Effect
Axis Definitions
• Add
152 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Remove
• Edit
Legend
• Show Legend
• Location

Backgrounds
Series Colors
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 153

4.6.1.3 Nokia Siemens Networks Reports

Nokia Siemens Networks Report window
The Nokia Siemens Networks Report can be accessed via:
> Reports task-tree folder > Nokia Siemens Networks task-tree item
The Nokia Siemens Networks Report window provides you an overview of the previ-
ously set parameters required to execute a Nokia Siemens Networks preset report in
SPOTS. Nokia Siemens Networks Reports are predefined reports that allow the
running of reports to make statistical analysis of specific counter measurements. These
reports are associated to the installed TPs, becoming available with each specific
hardware installed. Nokia Siemens Networks Reports enable you to easily obtain
industry-standard statistical reports on every aspect of the network performance. The
Nokia Siemens Networks pre-configured reports can perform the following statistical
analysis:
• SPBH Max Peak
Displays the maximum peak hour for the specified date interval. Report uses mea-
surement data from the History log.
• SPBH Daily Peak
Displays the daily peak hour. Report uses measurement data from the History log.
• DTOT
Displays the daily total for each measurement counter. Report uses measurement
data from the History log.
• TEVL
Displays the detailed time evolution based on 15 minute samples. Report uses mea-
surement data from the Detailed log.
• TCBH
Displays the daily average. Report uses measurement data from the Detailed log.
By default, the Nokia Siemens Networks Report Wizard is opened automatically upon
selecting of any Nokia Siemens Networks Reports. It can be configured in the Prefer-
ences window (see Preferences window).
154 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 83 Nokia Siemens Networks Report Preferences window

window).
and time.
• Click Save Report to save the report parameters, enabling a latter execution.
Date Interval
buttons:
• Keyword
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 155

Refresh
Refresh check box. The graph or table report is then automatically updated as defined
in the Advanced Refresh Option window, by clicking the Advanced button.
g In reports DTEVL do not use daily aggregation (today) because not enough data is avail-
able. DTEVL is meaningful to be executed over several days.
Objects
report. The contents of the list can be hidden or expanded by clicking the Objects
expandable box.
• Name
• Aggregate
Results
In this field you are given an overview of the generated reports. The results overview is
shown by clicking the Execute Report toolbar button. The field has the Show only
one window check box. Select the Show only one window check box to display only
one report at a given time.
A description of each result produced, comprised of its objects and counters names, is
the related Report Output (see Report Output window) in a separate window.
Nokia Siemens Networks Report Wizard

The Nokia Siemens Networks Report Wizard can be accessed via:
> Nokia Siemens Networks Report window > Report Wizard toolbar button
The Nokia Siemens Networks Report Wizard window allows you to set the parameters
required to execute a report in SPOTS. Nokia Siemens Networks Reports are pre-
defined reports that allow you to perform statistical analysis of specific counter measure-
ments. These reports are associated to the installed TPs, becoming available with each
specific hardware installed. Nokia Siemens Networks Reports enable you to easily
obtain industry-standard statistical reports on every aspect of the network performance.
By default, the wizard is opened automatically upon selection of any Nokia Siemens
Networks Reports (see Nokia Siemens Networks Reports) task-tree item. It can be con-
figured in the Preferences window (see Preferences window).
• Click Back to go to the previous step of the wizard.
156 Id:0900d8058018db2b E200613-01-114-V14.0I-23



Figure 84 Siemens Report Creation Wizard - Step1

Date Interval
buttons:
• Keyword
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 157

Refresh
The Advanced button opens the Advanced Refresh Option window.

This step allows you to select the network objects to be evaluated in the report. No mea-
surement counter selection is required as it is predefined by each Nokia Siemens
Networks Report.
Figure 85 Nokia Siemens Networks Report Creation Wizard - Step2

Class Tree

• Name
• User label
158 Id:0900d8058018db2b E200613-01-114-V14.0I-23

lowing buttons:
list.
mouse.
• Add Items
• Select All
bar which contains the following tasks in a context menu:
• Hide
• Columns
Tab.
• Show
• Sorting...
you can create a new sort or delete the existing ones by using:
– Add
Adds a new sort function.
– Remove
• Filters
• No Filter
• Filter Editor
• Export Data...
• Refresh
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 159

g Both lists allow you to make a sort in ascending or descending order by Name or User
Label, or both, by clicking on the corresponding list title.
Selection List
• Remove Items
• Select All

General Tab
Figure 86 Nokia Siemens Networks Report Creation Wizard - Step3 (General tab)
Type
• Table
160 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Graph
Group By
Title
Output Tab
Figure 87 Nokia Siemens Networks Report Creation Wizard - Step3 (Output tab)

• Screen
• File
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 161

• Printer
a printer associated with the SPOTS Client by selecting Screen radio button, and select-
ing Print when the report has been generated.

table reports)
• Header Font
• Cells Font
Select the font format for the table cell’s.
162 Id:0900d8058018db2b E200613-01-114-V14.0I-23


for table reports)
Header
Date/Time Cells
Objects Cells
Counters Cells
Patterns check box.

E200613-01-114-V14.0I-23 Id:0900d8058018db2b 163

chart reports)
Chart Properties
• Chart Type
• Border
• Show Grid
• Grid Spacing
• Unit
• 3D Effect
Axis Definitions
164 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Add
• Remove
• Edit
Legend
• Show Legend
• Location

for chart reports)
Backgrounds
Series Colors
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 165

Advanced Refresh Option window

The Advanced Refresh Options window can be accessed via:
> Nokia Siemens Networks Report window > Advanced button
The Advanced Refresh Options window allows you to configure Nokia Siemens
Networks Reports refresh options.
Figure 92 Advanced Refresh Options window

• Start Delay
Set the report update delay in respect to the measurement data load time.
• Refresh Interval
Click the Refresh Interval drop-down menu and select the required report update
frequency.
4.6.1.4 Custom Reports

Custom Reports, when available, can be accessed via:
> Reports task-tree folder > Custom Reports task-tree folder
Custom Reports are reports that are configured by you. You can manually build the
report using SPOTS Reporting Language (SRL). Similar to a typical programming lan-
guage, the report code is written and compiled using the Reports Editor. The report can
be set to select specific objects or counters by default. It can also determine the exact
statistical analysis to be performed. The following statistical analysis types are available:
• SPBH Max Peak
Displays the maximum peak hour for the specified date interval. Report uses mea-
surement data from the History log.
• SPBH Daily Peak
Displays the daily peak hour. Report uses measurement data from the History log.
• DTOT
Displays the daily total for each measurement counter. Report uses measurement
data from the History log.
• TEVL
Displays the detailed time evolution based on 15 minute samples. Report uses mea-
surement data from the Detailed log.
• TCBH
Displays the daily average. Report uses measurement data from the Detailed log.
There are two main types of Custom Reports depending on their user permissions.
Private Custom Reports are only accessible to the user that has created the report.
Public Custom Reports are accessible by all SPOTS users.
166 Id:0900d8058018db2b E200613-01-114-V14.0I-23

The Custom Reports give you the ability to customize both the report window and
wizard. A general description of both is given below:
Custom Reports window

The report window can be opened by double-clicking a report item in the Custom
Reports task-tree folder.
Figure 93 Custom Reports list

Custom Reports, in order to perform statistical analysis, have a predefined selection of
measurement counters. Due to its similarity, a general description of a typical report
window can then be given by the topic Nokia Siemens Networks Report window (see
Nokia Siemens Networks Reports).
Custom Reports Wizard

By default, the relevant wizard is opened automatically upon selecting a Custom
Report, but it can be configured in the Preferences window (see Preferences window).
As for the report window, the wizard does not require a measurement counter selection
step. Due to its similarity, a general description of a typical report wizard can then be
given under the topic Nokia Siemens Networks Report Wizard.
However, if the specific report requires, an additional step is available. The following
field describes the wizard’s additional step:
Additional Step: Extra Parameters

This step allows you to set the report's specific extra parameters.
Parameters Table
In the Parameters Table you can fill in the required extra parameters of the custom built
report. The extra parameters may also include symbols and special characters.
g Due to their customizable nature, no specific description of Custom Reports can be

given. Further predefined selections can be set, such as Date Interval, Data Source,
Objects, among others. To learn more on creating your own custom built reports, please
refer to the Reports Editor's own user documentation.
Reports Editor
The Reports Editor window can be accessed via:
SPOTS menu > Reports Editor... menu item
The Report Editor window allows you to manually configure a Custom Report (see
Custom Reports) using SPOTS Reporting Language (SRL). Similar to a typical pro-
gramming language, the report code is written and compiled using the editor, which
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 167

consists of an independent application to the SPOTS Client. The application and its pro-
gramming language (SRL) are further described in their own customer documentation,
found with the SPOTS installation media.
4.6.1.5 Class Browser window

The Class Browser window can be accessed via:
Ad-Hoc Report, Ad-Hoc Comparison Report and Nokia Siemens Networks Reports
window > Class Browser toolbar button
The Class Browser window allows you to select or modify the previously selected object
instances and counters by launching the Report Wizard. The wizard is launched in Step
2, where you can resume the report setup process. The Class Browser toolbar button
is available when any of the Ad-Hoc Report window, Ad-Hoc Comparison Report
window or Nokia Siemens Networks Report window windows are opened.
The Class Browser window can be accessed from the following report windows:
Ad-Hoc Report
Accessing the Class Browser window from the Ad-Hoc Report window opens the Ad-
Hoc Report Wizard. The wizard is automatically launched in Step 2: Object Instances
Selection. Please refer to the second and third steps of the Ad-Hoc Report Wizard.
Ad-Hoc Comparison Report

Accessing the Class Browser window from the Ad-Hoc Comparison Report window
opens the Ad-Hoc Comparison Report Wizard. The wizard is automatically launched
in Step 2: Object Instances Selection. Please refer to the second and third steps of
the Ad-Hoc Comparison Report Wizard.
Nokia Siemens Networks Reports

Accessing the Class Browser window from any Nokia Siemens Networks Report
window opens the Nokia Siemens Networks Report Wizard. The wizard is automati-
cally launched in Step 2: Object Instances Selection. Please refer to the second step
of the Nokia Siemens Networks Report Wizard.
4.6.1.6 Report Properties window

The Report Properties window can be accessed via:
Reports task-tree folder > Ad-Hoc Report task-tree item > Report Properties toolbar
button
The Report Properties window allows you to set additional report output options. In order
to modify object instances and counter selection the Class Browser window (see Class
Browser window) is available.
General Tab
168 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 94 Report Properties window (General tab)

Type
• Table
• Graph
Group By
Title
Output Tab
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 169

Figure 95 Report Properties window (Output tab)

Output Type Only When Scheduled

• Screen
• File
• Printer
a printer associated with the SPOTS Client by selecting the Screen radio button, and
selecting Print when the report has been generated.

170 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 96 Report Properties window (Options tab for table reports)

• Header Font
• Cells Font
Select the font format for the table’s cells.

E200613-01-114-V14.0I-23 Id:0900d8058018db2b 171

Figure 97 Report Properties window (Appearance tab for table reports)

Header
Date/Time Cells
Objects Cells
Counters Cells
Patterns check box.

172 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 98 Report Properties window (Options tab for chart reports)

Chart Properties
• Chart Type
• Border
• Show Grid
• Grid Spacing
• Unit
• 3D Effect
Axis Definitions
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 173

• Add
• Remove
• Edit
Legend
• Show Legend
• Location

Figure 99 Report Properties window (Appearance tab for chart reports)

Backgrounds
Series Colors
This window has a toolbar, located at the bottom of the window:
174 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Click OK to save the preference settings.

• Click Apply to validate the settings.
4.6.1.7 Report Filter Editor

The Report Filter Editor window is accessed via:
> Reports task-tree folder > Ad-Hoc Report, Ad-Hoc Comparison Report and Nokia
Siemens Networks Report wizard > Objects and /or Counters selection drop down
menu
The Report Filter Editor allows you to filter the displayed items in the selection lists.
Figure 100 Filter Editor window

Filters
In this field you can add or remove a filter by using the following buttons:
• Add to add a filter to the available filter list.
• Remove to remove a filter from the available filter list.
Filter Editor
This field allows you to name the filter and add or remove boolean operators between
filters by using the following buttons:
• Add Boolean Op. to perform a boolean operation between filters.
• Remove Op. to remove a boolean operation between filters.
Filter Node Editor

In this field you can configure the following filter options:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 175

• Column
You can select to which field column the filter is assigned to.
• Rule
Provides a rule (>, <, =, =>, =<, <>) selection to apply to the filter. This rule compares
the object and the value introduced by you.
• Value
This value interacts with the Rule previously selected, and perform the filter opera-
tion.
4.6.1.8 Report Output window

You can view the results generated by a report by:
> SPOTS menu > Preferences menu item
The Report Output window allows you to view the graphical or numerical results gen-
erated by a Trend Analysis report. You can execute a report by running any Trend
Analysis report wizard, further described under the Reports Introduction (see 4.6.1)
topic.
The following types of reports can be generated:
Graph Report
A graph report displays all measurements in a line plotted graph.
Figure 101 Graph Output Report window

176 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Title
This field summarizes the report details, displaying the report type and data collection
dates. You can also activate or deactivate the following features:
• View
Click the View drop down menu to select the time range of the graphical report.
• Vertical Zoom
Click the Vertical Zoom drop down menu to select the range of the vertical axis dis-
played in the graphical report.
Graph
In this field you can view the plotted measurements in a graph. You can zoom in to a
specific area of the graph by clicking and dragging the mouse, selecting an area. The
selected area is then shown in greater detail.
The Graph field contains a context menu by right clicking the graph area.
• Click UnZoom to reset the zoom applied to the graphical report and display it in its
original settings.
• Click Save to save the obtained graph to a file.
• Click Print to print the graphical report.
Legend
This field contains a legend displaying a list of the counters displayed in the graph. A
table displays generic statistical data in columns.
• Legend Item
Displays the object class and counter name.
• Value At
Displays the counter value at a specific date and time.
• Maximum
Displays the maximum value measured for the counter and its occurrence date and
time.
• Minimum
Displays the minimum value measured for the counter and its occurrence date and
time.
Table Report
A table report displays all obtained measurements as numerical values in a table.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 177

Figure 102 Table Report window

Title
This field summarizes the report details, displaying the report type and data collection
dates.
Table
The table displays all obtained measurements in columns.
• Date
Displays the data collection data.
• Time
Displays the data collection time.
• Object
Displays the object instance class.
• Counters (name of each counter)
Displays all obtained measurements as numerical values for each counter at the
respective date and time.
4.6.2 Online Monitoring Reports
4.6.2.1 Ad-Hoc Online Report window

The Ad-Hoc Online Report can be accessed via:
> Reports task-tree folder > Ad-Hoc Online Report task-tree folder
The Ad-Hoc Online Report window provides you a near real-time display of the counter
measurements. The window allows you to monitor the current activity of the enabled
178 Id:0900d8058018db2b E200613-01-114-V14.0I-23

network objects as well as monitor all triggered alarm situations. The online report's
display properties can be set in the Online Monitor Preferences window (see 4.6.2.2).
Click Externalize to view the online report in a window independent to the SPOTS main
window.
Certain toolbar tasks are also available in a context menu by right clicking the window.
• Click Add Counter to add a new monitored metric counter.

• Click Remove Counter to delete the selected monitored metric counter.
• Click Execute Report to run the report.
• Click Execute Report... to run a custom report. A list of available reports of the
respective object class is displayed.
• Click Save Task to save the report settings to the My Reports (see 4.6.3) list.
• Click Save Custom Report to save the report as a custom report.
• Click Print to print the online report.
Certain tasks are only available in a context menu by right clicking the window.
• Click Set as Default to set the current view as default.
• Click Report Properties to set the report properties in the Report Properties
window.
g Administrators can set a report as default for all users (public) or for their own use only
(private). Other users can only set a report as private.
Alarms Browser Tab

The Alarms Browser tab allows you to view the current state of all triggered alarms.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 179

Figure 103 Ad-Hoc Online Report Alarms Browser tab

Alarm List
In this field you are able to select the network object associated to a triggered alarm.
Upon selection of the adjacent check-box, the network object's counter measurements
are displayed in the Report field. The field displays the alarm information in columns.
The field provides the:
• Time
Displays the time each alarm was triggered.
• Counter
Displays the counter responsible for the alarm triggering situation.
• Instance
Displays the exact instance responsible for the alarm triggering situation.
Alarm Properties
Chart Report
This field provides a graphical representation of the counter measurements. The
counter instance measurements are plotted against the horizontal threshold lines. Adja-
cently to the graph the most recent measurement of each counter instance is displayed.
Table Report
This field displays the counter instances measurements in table format.
Objects Browser Tab

The Objects Browser tab allows you to view the current measurement of each network
object.
180 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 104 Ad-Hoc Online Report Objects Browser tab

Class Tree
In this field you can view and select the available counters by browsing through their
object classes. For each object class its enabled monitored metric counters are dis-
played. Selecting a monitored metric enabled counter displays its measurement
behavior in real-time.
Chart Report
This field provides a graphical representation of the counter measurements. The
counter instance measurements are plotted against the horizontal threshold lines. Adja-
cently to the graph the most recent measurement of each counter instance is displayed.
Table Report
This field displays the counter instance measurements in table format.
4.6.2.2 Online Monitor Preferences Editor window

The Online Monitor Preferences Editor window can be accessed via:
> Task menu > Online Monitor Preferences menu item
The Online Monitor Preferences Editor window allows you to configure SPOTS
Online Monitor to best suit its operation. You can customize the Ad-Hoc Online Report
window (see Ad-Hoc Online Report window).
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 181

Figure 105 Online Monitor Preferences Editor window

General
The General tab allows you to activate and deactivate its preferences regarding the user
Login.
Select the Use Stored Login check box to associate the username and password
entered in the SPOTS login window to the current Windows user account. The next time
the SPOTS application starts using the same Windows user account, the associated
username and password are automatically entered, not requiring further user identifica-
tion.
Display
The Display tab allows you to select the label to display in the object’s instances. You
can select one of the following Object Instances Identification options:
• User Defined Label
Select the User Defined Label check box to display the object instances with the
user’s label.
• Nokia Siemens Networks Defined Label
Select the Nokia Siemens Networks Defined Label check box to display the object
instances with the Siemens label.
• Display Both Labels
Select the Display Both Labels check box to display the object instances with the
user’s and Nokia Siemens Networks labels. The labels are presented to you sepa-
rated by a “#”.
182 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Additionally you can enable the Report Last Value Panel option. Select the Show
Counter Names check box to display the counter’s name in the report.
Chart
The Chart tab allows you to set the Ad-Hoc Online Report chart display properties.
You can select one of the following chart properties:
• Background
Set the report background color by selecting one of the following radio buttons:
– Use Color From Report Template
Select the Use Color From Report Template radio button to apply the Trend
Analysis reports color scheme, defined in the Report Properties window (see
Report Properties window).
– Use Custom Color
Select the Use Custom Color radio button and pick a background color using
the ... button.
• Series
Set the report series colors by selecting one of the following radio buttons:
– Use Colors From Report Template
Select the Use Colors From Report Template radio button and to apply the
Trend Analysis reports color scheme defined in the Report Properties window
(see Report Properties window).
– Use Custom Colors
Select the Use Custom Colors radio button and set the series colors by config-
uring the adjacent table.
Table
The Table tab allows you to set the Ad-Hoc Online Report table display properties. You
can select one of the following Date Format options:
• Use Date Format From Report Template
Select the Use Date Format From Report Template radio button to apply the
Trend Analysis reports date format, defined in the Report Properties window (see
Report Properties window).
• Use Custom Format
Select the Use Custom Format radio button and select the table format from the
options in the adjacent drop-down menu.
Alarms
The Alarms tab allows you to set the Ad-Hoc Online Report threshold display proper-
ties and define the maximum number of alarms.
• Alarm Browser
Allows you to define the number of alarms to be displayed in the Alarm Browser.
– Use Default Alarm Limit
Select the Use Default Alarm Limit check box to set the number of displayed
alarms to its default value (200).
– Maximum Number of Alarms
If the previous option is not selected you can set the maximum number of alarms
by dragging the slider bar.
• Threshold Lines
You can choose one of the following Threshold Lines options:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 183

– Show
Select the Show radio button to display the threshold horizontal lines in the Ad-
Hoc Online Report.
– Hide
Select the Hide radio button to disable the display of threshold lines in the Ad-
Hoc Online Report.
– As Defined in the Report Template
Select the As Defined in the Report Template radio button to apply the thresh-
old horizontal lines defined in the Report Properties window (see Report Prop-
erties window).
• Click OK to save the preference settings.
4.6.2.3 Report Properties window

The Report Properties window can be accessed via:
> Ad-Hoc Online Report window > Report Properties context menu item
The Report Properties window allows you to configure the currently displayed Online
Report. You can customize the specific report displayed in the Ad-Hoc Online Report
window (see Ad-Hoc Online Report window).
Figure 106 Report Properties Editor window

Chart
The Chart field allows you to set the counter table display properties. The following
options can be set:
184 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Background
Set the counter table background color by clicking the adjacent button.
• Counters
Set the colors to represent each counter by clicking the table and selecting its
Table
The Table field allows you to set the counter table date format. Select the Date Format
to apply from the drop-down menu.
Threshold
The Threshold field allows you to set the Ad-Hoc Online Report threshold display
properties. You can choose one of the following threshold Lines options:
• Show
Select the Show Lines radio button to display the threshold horizontal lines in the
Ad-Hoc Online Report.
• Hide
Select the Hide Lines radio button to disable the threshold lines’ display in the Ad-
Hoc Online Report.
• Click OK to save the properties settings.
• Click Cancel to leave the window without changing the properties settings.
4.6.2.4 Alarm Filter Editor window

The Alarm Filter Editor window can be accessed via:
Status Bar Main Window field > Alarm icon context menu
The Alarm Filter Editor window allows you to filter the which alarms should fire alerts.
Figure 107 Alarm Filter Editor window

Filter Name
The field allows you to type in the name of the filter in the text box.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 185

Filter Conditions
The field displays all filter conditions that can be edited using the following buttons:
• Set Filter
Creates a new filter condition.
• Edit Filter
Edits the selected filter condition.
• Reset Filter
Deletes the selected filter condition.
g The OK button is only available when the correct syntax is entered in this field. For
example: if the condition is related to numeric values, this button is available if the text
entered is related with the same criteria. The same happens when logical periods are
applied.
Logical Operator
The Logical Operator field allows you to set the logical operation to be performed
between the above filter conditions. You can choose one of the following logical opera-
tions options:
• AND
• OR
• Click New to create a new alarm filter.
• Click Save to save the current alarm filter settings.
• Click Load to load an alarm filter.
• Click Delete to delete the currently selected alarm filter.
• Click OK to apply the alarm filter settings.
• Click Cancel to leave the window without changing the alarm filter settings.
g There is no relationship between Alarm Filter Editor and Alarm Browser (see 4.5.1).
Please note that when defining a filter on the Alarm Icon, we are controling which alarms
should fire alerts. While on the other hand, when defining a filter on the Alarm Browser
we are configuring which information is presented to you on the table.
g The Default Filter, as defined on the Preferences window, is only applied to the Alarm
Icon. Also, the Alarm Icon can be accessed at anytime in SPOTS interface, while the
Alarm Browser must be accessed through the Real Time Utils task-tree folder.
4.6.3 My Reports
The My Reports list can be viewed by expanding the:
> My Reports task-tree folder
The My Reports task-tree folder displays all saved Report tasks. Both saved and
scheduled reports can be viewed in the My Reports expandable list. Tasks can be
added to the My Reports list by using the following toolbar buttons available in the Ad-
Hoc Report window, Ad-Hoc Comparison Report window and Nokia Siemens
Networks Report window windows:
• Click Save Report to save any Report task to the My Reports list.
186 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Click Schedule Report to schedule the execution of any Reports task using the
Scheduler window (see 4.4.1). The scheduled report task is also added to the My
Reports list.
Figure 108 My Reports list

The task-tree contains the following context menu:
• Click Open to open the selected report window.

• Click Remove to delete the selected report task from the list.
• Click Rename to rename the selected report task.
• Click Expand to show all tasks contained in the selected task-tree folder.
• Click Collapse to hide all tasks contained in the selected task-tree folder.
4.7 SPOTS SlideShow
4.7.1 SlideShow window

The SPOTS SlideShow external application allows you to view a set of SPOTS based
reports as a slide presentation. This functionality can be very useful when presenting the
network behavior in a meeting on a video wall system.
The SPOTS SlideShow application runs externally to the SPOTS Client and uses the
reports stored on the SPOTS Database Server. Reports can be produced using the Ad-
Hoc Report window or the Report Wizard.
The SPOTS SlideShow can be accessed via:
> Start menu > Programs folder > SPOTS folder > SlideShow menu item
Main Window
The following image presents the SPOTS SlideShow Main window.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 187

Figure 109 SPOTS SlideShow Main Window

The SPOTS SlideShow Main window is divided into four main areas that are the appli-
cation toolbar, the Reports & Presentations Browser (see chapter Reports & Presenta-
tions Browser), the Presentation Viewer (see chapter Presentation Viewer) and the
Presentation Control (see chapter Presentation Control).
The application toolbar has the following items:
File
The File menu item has the following actions available:
• Preferences
Opens the Preferences window. It is also available with the shortcut keys
CTRL+SHIFT+P. For more information regarding the Preferences Manager (see
chapter Preferences Manager)
• Exit
Exits the application.It is also available with the shortcut keys CTRL+SHIFT+X
View
The View menu item has the following actions available:
• Toolbar Visible
Display or hide the toolbar.
• Statusbar Visible
Display or hide the Status Bar.
188 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Viewer Externalized
Externalize the Presentation Viewer. It is also available with the shortcut keys
CTRL+SHIFT+E
• Refresh
Refreshes the Slideshow information. It is also available with the shortcut keys
CTRL+SHIFT+H
Presentation
The Presentation menu item has the following actions available:
• New
Creates a new Presentation. It is also available with the shortcut keys CTRL+N
• Open
Opens an existing Presentation. It is also available with the shortcut keys CTRL+O
• Save
Saves the currently open Presentation. It is also available with the shortcut keys
CTRL+S
• Delete
Deletes the currently open Presentation It is also available with the shortcut keys
CTRL+SHIFT+D
• Play
Plays the currently selected Presentation.It is also available with the shortcut keys
CTRL+P
• Pause
Pauses the currently selected Presentation.
• Stop
Stops the currently selected Presentation
• Previous Slide
Moves back to the previous slide.
• Next Slide
Moves forward to the next slide.
Slide
The Slide menu item has the following actions available:
• Add Slide
Adds a new slide to the Presentation. It is also available with the shortcut keys
CTRL+A
• Remove Slide
Removes the selected slide from the Presentation. It is also available with the
shortcut keys CTRL+R
• Edit Slide
Edits the selected slide. It is also available with the shortcut keys CTRL+SHIFT+E
• Add Report
Adds a report to the current slide. It is also available with the shortcut keys
CTRL+SHIFT+A
• Remove Report
Removes the selected report. It is also available with the shortcut keys
CTRL+SHIFT+R
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 189

• Move Slide Up
Moves the slide up in the current Presentation. It is also available with the shortcut
keys CTRL+SHIFT+U
• Move Slide Down
Moves the slide up in the current Presentation. It is also available with the shortcut
keys CTRL+SHIFT+D
Help
Opens the Help file.
4.7.2 Preferences Manager

The Preferences Manager window allows you to configure certain parameters. It is
divided into two tabs: the General Tab and the Presentation Tab.
The General tab allows you to use the Store Login Information. This option is enabled
by clicking the available checkbox.
Figure 110 Preferences Manager General Tab

The Presentation Tab allows you to configure certain parameters regarding the Pre-
sentation timing. It is possible to define the slide’s minimum and maximum delay in the
respective text boxes as well as the actual delay for each slide. A scroll bar is also avail-
able to determine the actual slide delay time.
190 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 111 Preferences Manager Presentation Tab
4.7.3 Slide Editor

The Slide Editor’s (SE) purpose is to allow you to create and setup presentation slides.
The slide setup procedure includes the definition of the slide layout and the reports that
are associated with the chosen slide layout.
The SE is tab based and it contains three main tabs: General tab, Layout tab and
Reports tab. The General tab allows you to enter general slide information, such as the
slide title and its description. The Layout tab allows you to setup the slide layout. The
Reports tab allows you to add or remove reports to or from the slide. It also assigns
each added report to a particular location in the defined layout.
It is important to mention that each slide has a grid of its own which allows you to define
different layouts for different slides. To further enhance and customize slide layout, as
well as allow you to define different areas for the reports, it is possible to merge grid cells
across multiple columns and rows. Cell merging operations are always performed to the
right when merging columns and to the bottom when merging rows
As mentioned the slide editor also allows you to add or remove reports to and from the
slide and to customize where they should appear in the defined layout. The Editor
Reports tab provides you a tree with the available public and private reports from which
they can choose the reports to add to the slide. After adding the reports to the slide, it is
possible to assign a layout cell to each of them.
The SE focus error detection on the layout grid and the association between the reports
and the underlying slide grid cells. The SE analyzes invalid cell merges according to the
principles defined for cell merging and, when an invalid merge situation is detected an
error message is presented to you.
The error detection mechanism associated to the SE also verifies if the underlying slide
grid is suitable for the number of associated reports. When you change the grid or adds
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 191

reports to a given slide, the editor verifies if all the reports associated with the slide are
assigned to a grid cell and if they are not, an error message is presented. This procedure
guarantees that all the added reports are visible within the slide.
General Tab
Through this tab you are able to specify the slide title and description using the appro-
priate text fields. In order to successfully create the slide you must enter a slide title, this
field is mandatory for the slide creation.
Figure 112 Slide Editor General Tab

Layout Tab
Through this tab you are able to define the number of columns and rows that constitute
the slide layout grid and setup the cell merges.
This tab presents an interactive preview of the grid that identifies each cell using an
alphabet letter. Through the preview grid you are able to select layout cells and define
the column and row spans using the corresponding fields. The column and row span
fields are available according to the selected cell and the already defined merging prin-
ciples. The selected cell background is painted with a different color to emphasize the
cell being edited.
192 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 113 Slide Editor Layout Tab

Reports Tab
Through this tab you are able to add and remove reports to and from the slide, as well
as define the layout cell that contains each added report.
In this tab there are three main components: the available reports tree, the slide reports
table and the slide layout preview.
The available reports tree contains the available public and private reports (excluding
the ones already present in the slide). It is through this tree that you are able to add
reports to the slide. It is also possible to refresh the tree contents using the refresh
button.
Ad-Hoc Reports are marked with a blue symbol whereas Predefined Reports are
marked with a yellow symbol. Ad-Hoc comparison Reports are marked with a green
symbol and Online Reports are marked with a red symbol.
The slide reports table contains an entry for each of the slide associated reports. The
first column identifies the report visibility. The second column identifies the report type
The third column contains the report title, and finally the fourth column identifies the cell
that contains the report display.
The slide layout preview contains a preview of the slide layout; layout cells that are
already associated with a report are painted in red and the layout cells that are empty
are painted in green.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 193

Figure 114 Slide Editor Reports Tab

To add a new report to the slide you must select the desired report from the reports tree
and then click the add button. After clicking the add button, a new entry appears in the
slide reports table. The entry that identifies the added report is removed from the avail-
able reports tree. After adding the report to the table you have to specify the layout cell
that contains the report display. To do this the combo box, associated with the table 'Cell'
column, is used. This combo box presents the available cells in the slide layout (the cells
painted in green in the slide layout preview).
To remove a report from the slide you should select the report to remove in the reports
table and then click the remove button. After clicking the remove button the entry asso-
ciated with the selected report is removed from the table and the report is available again
from the reports tree. Additionally the background of the layout cell that was previously
being occupied by the report becomes green in the slide layout preview.
When you click the OK button all the changes should be applied to the presentation slide
and the SE is closed. If the Cancel button is pressed all the changes made are ignored
and nothing changes in the presentation slide.
4.7.4 Reports & Presentations Browser

The Reports & Presentations Browser’s (RPB) purpose is to allow you to navigate
through the available reports and presentations.
194 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 115 Reports and Presentation Browser

The browser is tree based and contains four main folders as described in the following
table:
Folder Description
My Reports Folder that contains the user private reports
Public Reports Folder that contains all the available public reports
My Presentations Folder that contains the user private presentations
Public Presentations Folder that contains all the available public presenta-
tions
Table 10 Reports & Presentations Browser folders
In addition to the navigation, the RPB also allows you to perform some relevant actions
on the reports and presentations. For this purpose a toolbar is embedded in the browser
and a pop-up menu is available when interacting with its contents. The following table
presents the actions that are available through the browser:
Action Description
Refresh This action updates the browser contents. By executing
this action, the application refreshes the browser accord-
ing to the server’s existing contents.
Close This action closes the browser. This allows you to
maximize the visualization area.
Table 11 Reports & Presentations Browser actions
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 195

Action Description
Open This action is only available when a presentation object
is selected and the purpose of the Open action is to open
the selected presentation.If there is an unsaved presen-
tation open, you are asked if you want to save the active
presentation before opening the selected one.
Delete This action allows you to delete a specific presentation.
Add To New Slide Adds the currently selected report to a new presentation
slide. This action opens the slide editor in order to allow
you to setup the new slide and configure the location and
the space that is occupied by the report that is being
added.This action is only available for report nodes.
When a presentation or folder node is selected the action
is disabled.
Add To Slide Adds the currently selected report into an existing pre-
sentation slide. This action presents a small list that
allows them to select the target slide. After the slide is
chosen, the slide editor is opened in order to configure
the location and space that is occupied by the report that
is being added.This action is only available for report
nodes. When a presentation or folder node is selected
the action is disabled.
Expand Opens the currently selected tree (folder) node. This
action is only available for folder nodes. When a tree leaf
node is selected the actions is disabled.
Collapse Closes the currently selected tree (folder) node. This
action is only available for folder nodes. When a tree leaf
node is selected the action is disabled.
Table 11 Reports & Presentations Browser actions (Cont.)
There are some errors that can occur while working with the RPB.
When you are trying to open a previously saved presentation there are two error situa-
tions that can occur:
• The presentation file is invalid. This error can occur if the presentation file struc-
ture is not, according to the presentation, a defined XML structure for persistency.
• The presentation includes reports that could not be found. This error can occur,
for instance, if the presentation is associated with report description files that were
deleted.
When the presentation file is invalid an error message is presented and the open oper-
ation is aborted. When the presentation includes reports that could not be found, a
message is presented identifying the reports that were discarded.
When you are trying to delete an existing presentation an I/O exception can occur which
invalidates the process so an error message is presented. The message identifies the
error cause and clearly state that the operation could not completed successfully.
196 Id:0900d8058018db2b E200613-01-114-V14.0I-23

When refreshing the tree contents errors can occur while retrieving the new information
from the server. When this happens the application presents an error message and the
RPB existing contents remain unchanged.
4.7.5 Presentation Viewer

This section describes the UI for each of the PV available modes: internalized and exter-
nalized.
Internalized mode
When the viewer is in this mode it is a simple visualization box embedded within the
application framework and it does not contain any toolbar or menu associated to it. All
the actions are performed using the other application components.
Figure 116 Presentation Viewer Internalized Mode

Externalized Mode
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 197

Figure 117 Presentation Viewer Externalized Mode

This mode provides a small embedded toolbar that allows you to perform some basic
operations associated with the presentation visualization: switch to full-screen, switch to
internalized mode, play, stop, jump to next slide, jump to previous slide and change the
slides rotation delay. When in this mode the viewer ispresented in a new and indepen-
dent window that coexists with the application main window in the desktop.
4.7.6 Presentation Control

The Presentation Control is based on a tree table component. This allows the display of
the reports contained in the presentation to be grouped by slides. This means the slides
and reports structure are presented without loosing the notion of which reports are asso-
ciated with each slide. The following image displays the mentioned Presentation Control
tree table.
198 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 118 Presentation control

The Presentation Control table has five columns:
• Name
This column contains the name of the associated object. When associated with a
report, it contains the report name. When associated with a slide it contains the slide
name.
• Last Event
This column contains a timestamp that represents the last event of the associated
object. If the associated object is a report, the field contains the timestamp that rep-
resents the last instant in which new report data was received. If the associated
object is a slide, the field contains the most recent event that occurred within the
slide, that is, it contains the timestamp of the most recently updated report.
• Object Class
This column is only available for the report objects and it contains the object class
that is associated with the report. When associated to a slide object the field
contains the undefined symbol "-".
• Data Type
This column is only available for the report objects and it contains the report data
type identifier. When associated to a slide object the field contains the undefined
symbol "-".
• Status
This column contains the status of the associated object. When associated with a
report object, the column reflects the report execution status. When associated with
a slide object the column reflects the slide reports overall execution status.
The Presentation Control toolbar includes four direct access actions: create slide, play
presentation, stop presentation and close the presentation control area. It also includes
a pull-down menu to access other PC related actions. To have a better understanding
regarding what each of the mentioned actions does, see the Slide menu options in
chapter SlideShow window.
4.8 SPOTS Administration Console

The SPOTS Administration Console is a web based tool that allows the SPOTS admin-
istrator to perform regular operation and configuration tasks throughout the SPOTS
system.
The SPOTS Administration Console can be accessed via an internet browser. The
address has the following format:
http://<hostname|ip address>:<8080|port>/console
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 199

4.8.1 Login Window

The Login window (see Figure 119) is available in the SPOTS Administration Console
home window. The Login Window allows the identification of each user, upon attempt-
ing to start a SPOTS Administration Console session.
Figure 119 User Login window

The Login Window has the following fields:
• User
In this field, you can enter the identification.
For more information on the requirements of a valid SPOTS user, please refer to
User Access Control topic (see Chp.1.6).
• Password
In this field, you can enter the password associated to the username entered in the
User field. The Password field is case sensitive.
• Remember me on this computer
In this field, you can select the check box to activate the storage of use and
password information. This storing enables the automatic login the next time the
SPOTS Administration Console is opened.
The automatic login expires after 14 days. After that period, you need to re-enter the
username and password.
g To run this feature, you must not use the Logout button. The Remember me feature
works only if the browser application or browser tab is closed, and the last login was
done in the past 14 days.
The Login Window has the Sign In button. Click Sign In after having entered
a valid username and password to access the application.
Logout
In order to logout, you need to click the Logout button located in the top right corner
of the Administration Console’s window (see Figure 121). The Logout button is available
in any window after you have successfully initiated an Administration Console session.
Additionally you can also logout by using the File menu located at the top left corner
clicking the logout menu entry.
About the Administration Console
This window provides an overview and generic information about the Administration
Console (see Figure 120). The window is available simultaneously with the Login
Window.
200 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 120 About the Administration Console window
4.8.2 Main Window

The Administration Console Main window is displayed after you have logged in (see
Figure 121). The Administration Console Main window provides an overview of the
features available in the Administration Console and the access to each Feature
Group. The main page has a layout in which it is possible to differentiate three distinct
areas as follows:
• Visualization Area
• Navigation Area
• Main Processes Monitor
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 201

Figure 121 Main window

The Main window has the following buttons located in the task bar:
• Click Welcome Window to show the Welcome Window.

• Click Toggle Feature Access Area to hide or show the Feature Access Area.
• Click Toggle Open Tasks Area to hide or show the Open Tasks Area.
• Click Logout to logout.
The Main Window has the following menus:
• File - allows you to Logout using the logout menu item.
• Help - allows you to open the Help Contents File by clicking the Help Contents
menu item. It is also possible to view information regarding the version of the Admin-
istration Console by clicking the About SPOTS Administration Console menu
item.
• Preferences - allows you to configure visual settings regarding the Administration
Console (Figure 122).
Figure 122 Preferences Window

This window has the following tabs:
202 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Themes - you can configure the icons format by clicking the Select the icon theme
combo box. Additionaly you can configure the color pattern of the Administration
Console by clicking the Select the color theme combo box.
• Active Warnings - you can configure the number of Active Warnings to be dis-
played. This is achieved by means of a box menu or by inserting the desired number
manually in the text field available.
• Scheduled Tasks - you can configure the number of Scheduled Tasks to be dis-
played. This is achieved by means of a box menu or by inserting the desired number
manually in the text field available.
• Logs - you can configure the number of Logs to be displayed. This is achieved by
means of a box menu or by inserting the desired number manually in the text field
available.
4.8.2.1 Visualization Area

Whenever you select a feature, the feature is displayed in the Visualization Area (see
Figure 123). The Visualization Area is window based.
Figure 123 Visualization Area

Welcome Window
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 203

The Welcome Window is the first window presented to users in the Visualization Area
after having successfully logged in (see Figure 124). It is automatically loaded when the
administration console main window is presented. This window is a quick access area.
It displays the features available as well as a small description of each feature’s func-
tionality.
By clicking in the Feature Group button, the Welcome Window displays the features
available in that Feature Group. By clicking on a feature button, you access the selected
feature.
Figure 124 Welcome Window

The Welcome Window has the following buttons located on the left of the window:
• Click Live Monitoring to view a description of this Feature Group and

access each feature this Feature Group contains. This Feature Group has the fol-
lowing features available:
– Click System Logs Monitoring to access this feature.
– Click Scheduled Tasks Monitoring to access this feature.
– Click SPOTS Processes Monitoring to access this feature.
– Click Active Warnings Monitoring to access this feature.
• Click Reporting to view a description of this Feature Group and access

each feature this Feature Group contains. This Feature Group has the following
features available:
– Click Data Loading Statistics to access this feature.
– Click Data Conversion Statistics to access this feature.
204 Id:0900d8058018db2b E200613-01-114-V14.0I-23

– Click Data Collection Statistics to access this feature.

– Click Database Server Statistics to access this feature.
– Click Application Server Statistics to access this feature.
• Click Database Queries to view a description of this Feature Group

and access each feature this Feature Group contains. This Feature Group has the
following features available:
– Click Database Views to access this feature.
• Click SPOTS Configuration to view a description of this Feature

Group and access each feature this Feature Group contains. This Feature Group
has the following features available:
– Click Scheduler to access this feature.
– Click SPOTS Processes to access this feature.
4.8.2.2 Navigation Area

The Navigation Area contains the Feature Access Area and Open Tasks Area. In the
Navigation Area you have access to all available features. In the Open Tasks Area you
have access to the tasks that are currently open.
Feature Access Area
The Feature Access Area is the main navigation component. In this area users have full
access to all available features. The Administration Console Feature Access Area (see
Figure 125) is available in the Administration Console on the Navigation Area. It offers
a navigation in the form of a hierarchical tree that allows access to the information in a
structured fashion, in this particular case, grouping the available features. The top levels
display the Feature Groups and by clicking on each feature group the tree extends to
display all the features available.
Figure 125 Feature Access Area

Open Tasks Area
The purpose of the Open Tasks Area is to display a list of currently open features pro-
viding shortcuts to them. By clicking on one of the presented links (see Figure 126), the
selected task is shown in the Visualization Area.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 205

Figure 126 Open Tasks Area
4.8.2.3 Main Processes Monitor

The Main Processes Monitor runs along the bottom of the Main Window (see Figure
127). It monitors the main processes of the system:
• Application Server
• Naming Server
• Database Server
• Real Time Server
Each of these processes has a pop-up menu that allows the stop, start or restart of the
process. Additionally the Main Processes Monitor itself has a pop-up menu that allows
the stop, start or restart of the entire system. By clicking on the round status button of
each process, you have access to the pop-up menus.
Figure 127 The Main Processes Monitor

By providing visual indications, the Main Processes Monitor allows users to have an
intuitive perception of the processes’ behavior. In addition, the Main Processes Monitor
also provides visual indication of the monitored SPOTS Server instance global state. If
a given process changes state, the background of the component is changed accord-
ingly. This state change is done according to the state transition that occurred, and the
process priority in the managed SPOTS instance. For example, if the Real Time Server
stops, the background color must change to reflect this state change. As Real Time
Server is not a key process of SPOTS, the background color changes to dark yellow
(see Figure 128) to signal that something happened, but it was not a critical situation.
On the other hand, if the Application Server stops, the background changes to red (see
Figure 129) to inform that a vital process has crashed. The example of the Real Time
Server stoppage only considered the fact of single process failure, but if multiple pro-
cesses failed the background color changes according to priority levels. For example, if
both Real Time and Application servers stop the background color changes to red as
206 Id:0900d8058018db2b E200613-01-114-V14.0I-23

SAS has a higher priority. If all processes are running the background is green (see
Figure 130).
Figure 128 Main Processes Monitor Non-Critical Warning
Figure 129 Main Processes Monitor Critical Error
Figure 130 Main Processes Monitor Completely Operational

The pop-up menu buttons that are available for both the entire system and each of the
processes are the following:
• Click Start to Start the System or process.

• Click Stop to Stop the System or process.
• Click Restart to Restart the System or process.
4.8.3 Feature Groups

The Feature Groups are an intermediary stage that groups features according to their
context.
The feature’s groups are divided in the following groups:
• Live Monitoring
• Statistical Reports
• Database Queries
• SPOTS Configuration
If you access the console running from the machine that contains the SDS and SNS,
the active warnings monitoring are not available, neither the application server, real
time server, data loading, data collection and data conversion statistics. With this
console you are not able to access the SAS and RT logs as well as the correspond-
ing processes states and configuration files. If you access the console running from
the machine that contains the SAS and RT, the database querying feature is not
available, neither the database server statistics. With this console you are not able
to access the SDS and SNS logs as well as the corresponding processes states and
configuration files.
4.8.3.1 Live Monitoring

The Live Monitoring Feature Group allows you to access several Online Monitoring Fea-
tures. The Online Monitoring features grant you a complete online analysis of several
aspects of the functioning of SPOTS.
The Live Monitoring Feature Group is divided in the following features:
• Active Warnings Monitoring
• SPOTS Processes Monitoring
• Scheduled Tasks Monitoring
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 207

• System Logs Monitoring

Active Warnings Monitoring
Active Warnings (AWs) are alarms that reflect the functional status of the SPOTS appli-
cation. The alarms include errors occurring in the system, for example communication
breakdowns, loader failures or missing NEs, as well as warnings like memory occupa-
tion, partition capacity or CPU load.
There is a centralized Active Warnings configuration file that allows the configuration of
the several active warnings processed by the monitor application and all other executa-
bles/subsystems of the SPOTS application. The configuration file defines, for each
active warning, its activation state and its severity as defined in the severity field of the
alarm structure, in addition to the other required active warning fields. The Active
Warning configuration file is $SPOTS_DIR/activewarnings.cfg. This file is a
comma-separated-value file.
The Active Warnings are similar to normal events and are triggered when a special con-
dition is detected in one of the monitored subsystems. When generated, the warnings
are launched into the system, but no post-processing or state maintenance is performed
on them. An event is launched every time an error is detected and the notion of pending
and clear is not applied to these events. The Active Warnings are able to work along side
of SPOTS while still being able to notify the client applications when the system recovers
from the error. The Administration Console is able to show the active warnings at all
times, being independent of the state of the SPOTS system.
The Active Warnings Monitoring is displayed in the form of a table through which you
can view the warnings active at that moment (see Figure 131). This feature provides the
following information which is detailed in several aspects:
• Time
This tab displays the date and time when the Warning started.
• Source System
This tab displays the subsystem where the Warning originated.
• Severity
This tab shows the gravity of the warning (Critical / Major / Warning).
• Probable Cause
This tab displays the cause that generated the alarm.
• Additional Info
This tab displays a message that either comments about the warning or provides
information regarding actions to be taken.
It is possible to sort the warnings by any of the mentioned categories present in the
Active Warnings Monitoring table by clicking in the respective category. As new active
warnings are processed, the table automatically reflects this by loading the newly
arrived values. These new warnings are added into their correct position so that any
applied sort can be valid.
It is possible to forward active warnings to an external tool via snmp. In order to config-
ure the forwarding, you are required to edit the log4j_activewarningsproxy.properties file
and set some parameters:
#SPOTS logger configuration
log4j.loggerFactory=com.siemens.spots.utils.logging.SPOTSLogger
Factory
208 Id:0900d8058018db2b E200613-01-114-V14.0I-23

log4j.logger.SPOTSActiveWarningProxyLogger=debug,rolling,trapse
nder
(“trapsender" must be added to this line to activate the SNMP trap forwarding.)
log4j.appender.trapsender=com.siemens.spots.utils.logging.SPOTS
SNMPTrapAppender
log4j.appender.trapsender.Threshold=DEBUG
log4j.appender.trapsender.ImplementationClassName=com.siemens.s
pots.utils.logging.SPOTSJoeSNMPTrapSender
log4j.appender.trapsender.layout=com.siemens.spots.utils.loggin
g.SPOTSSnmpConversionPatternLayout
#ManagementHost can be one or more separated by ',' or ';'
log4j.appender.trapsender.ManagementHost= address of the machines that
receive the Active Warnings (works with IP addresses), separated by ‘,’ or ‘;’
#ManagementHostTrapListenPort is 162 by default, but there may be conflicts with
other SNMP agents
log4j.appender.trapsender.ManagementHostTrapListenPort=162 (this is
the port ManagementHostuses to listen for AWs. By default 162 is in use. In case 162
is not being used, it must be configured)
log4j.appender.trapsender.LocalIPAddress=127.0.0.1
#LocalTrapSendPort is 161 by default, but there may be conflicts with other SNMP
agents
log4j.appender.trapsender.LocalTrapSendPort=1061 (this is the trap
sending port)
log4j.appender.trapsender.EnterpriseOID=1.3.6.1.4.1.5308.1.1.2
log4j.appender.trapsender.GenericTrapType=6
log4j.appender.trapsender.SpecificTrapType=2
log4j.appender.trapsender.CommunityString=Public
log4j.appender.trapsender.ForwardStackTraceWithTrap=true
The following table provides a description of all the available configuration parameters-
for the Active Warnings Monitor service.
Identifier Type Default Description

aw.service.pool- Long 15000 the service pooling interval; this con-
ing.interval figuration parameter specifies the
periodicity is used by the service to
query the active warnings source (in
this case the active warnings proxy
log file); the parameter defaults to 15
seconds; the value is expressed in
mili-seconds;
Table 12 Active warnings configuration paramaters
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 209


aw.service.min.pool- Long 5000 the service minimum acceptable
ing.interval pooling interval; this value is used
(when the pooling interval validation
feature is active) to guarantee that
the service is not configured with a
pooling interval lower than this
value; this prevents performance
degradation; defaults to 5 seconds;
the value is expressed in mili-
seconds;
aw.service.pool- Boolean True this configuration parameter enables
ing.interval.verifica- or disables the pooling interval verifi-
tion.enabled cation; defaults to ‘true’ meaning that
the verification is enabled;
aw.service.pro- Boolean False this configuration parameter enables
file.enabled or disables the service profiling;
when the service profiling is enabled
the elapsed time of the operations
performed by the service is logged to
the application log files;
aw.ser- Boolean True this configuration parameter enables
vice.cache.enabled or disables the service cache; when
the service cache is enabled the
read active warnings are stored by
the service and the requests made
are supported by the cache data;
defaults to ‘true’ meaning that the
service cache is enabled;
aw.ser- Integer 10000 this configuration parameter
vice.cache.size contains the service cache size;
defaults to 10000 and it is expressed
in number of active warnings stored;
aw.ser- String ${SPOTS_D this configuration parameter
vice.source.files.dire IR}/logs contains the pathname that identifies
ctory the directory that contains the active
warnings source files; this pathname
is used by the service to resolve the
files that are used as active warn-
ings’ sources; the pathname
supports properties that is resolved
by using the application environment
or the system environment (if neces-
sary);
Table 12 Active warnings configuration paramaters (Cont.)
210 Id:0900d8058018db2b E200613-01-114-V14.0I-23


aw.ser- String activewarn- this configuration parameter
vice.source.file- ing- contains the pattern used to identify
name.pattern sproxy{0}.lo the active warnings’ source files; this
g pattern is used by the service along
with the source files directory
pathname to resolve the available
active warnings source files;
aw.service.file.com- String # this configuration parameter
ment.identifier contains the comments identifier
used in the active warnings’ source
files; this identifier is used by the
service to ignore any eventual irrele-
vant information that can exist in the
active warnings’ files during the
parse phase;
aw.ser- String ; this configuration parameter
vice.file.field.separa- contains the identifier of the separa-
tor.identifier tor that is used in the active warn-
ings’ source files to separate each of
the active warning fields; this param-
eter is used by the service parser to
create the active warnings’ objects;
aw.ser- String yyyy-MM-dd this configuration parameter
vice.file.date.format HH:mm:ss, contains the date format that are
SSS used by the service to parse the
active warnings occurrence time-
stamps; this format pattern is used to
interpret the date fields contained in
the active warnings source files;
Table 12 Active warnings configuration paramaters (Cont.)
The Active Warnings Monitoring is displayed in the form of a table through which you
can view the warnings active at that moment.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 211

Figure 131 The Active Warnings Monitoring window

Active Warnings
This field has the following tabs:
• Time
This tab displays the date and time the warning started.
• Source System
This tab displays the subsystem where the warning was originated.
• Severity
This tab shows the gravity of the warning (Critical / Major / Warning).
• Probable Cause
• Additional Info
This tab displays a message that either comments the warning or provides informa-
tion regarding actions to be taken.
It is possible to sort the warnings by any of the mentioned categories present in the
Active Warnings Monitoring table by clicking in the respective category. As new active
warnings are processed, the table automatically reflects this by loading the newly
arrived values. These new warnings are added into their correct position so that any
applied sort continues valid.
SPOTS Processes Monitoring
This feature displays the status of each of the subsystems of SPOTS and allows you to
start, stop or restart each subsystem individually or the entire system as a whole (see
Figure 132). On each of the four subsystems (Application Server, Naming Server,
Database Server, and, Real Time Server) there are individual controls in the form of
buttons to perform the start, stop or restart functions. Additionally there are three control
commands at the top of the window to control the system as a whole. The Feature has
a color scheme identical to the Processes Monitoring Area. The background color of the
component is changed accordingly with the given state of the process changes. This
state change is done according to the state transition that occurred, as well as the
process priority in the managed SPOTS instance. For example, if the Real Time Server
stops, the background color must change to reflect this state change. As Real Time
Server is not a key process of SPOTS, the background color changes to a dark yellow
212 Id:0900d8058018db2b E200613-01-114-V14.0I-23

color to signal that something happened, but it was not a critical situation. On the other
hand, if the Application Server stopped, the background changes to red to inform that a
vital process has crashed. The Real Time Server stoppage example only considered the
fact of single process failure, but if multiple processes failed the background color
changes according to priority levels. For example, if both Real Time and Application
servers stop the background color changes to red, as SAS has a higher priority. If all
processes are running the background is green.
Figure 132 SPOTS Processes Monitor window

The pop-up menu buttons that are available for both the entire System and each of the
processes are the following:
• Click Start to start the system or process.

• Click Stop to stop the system or process.
• Click Restart to restart the system or process.
Scheduled Tasks Monitoring
The Scheduled Tasks Monitoring is responsible for displaying the scheduled tasks of
operating system. In this feature, users obtain a listing of the currently scheduled tasks
along with the state of its last execution, execution time and task result in this case.
In order to correctly define a job in the Crontab to be monitored by the Symon, it is nec-
essary to use the script SPOTSTASK.sh.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 213

It is not possible to monitor tasks that include shell special characters, such as < > | & ;
( ) ! * ? [ ] { } ~ $ and \, because these are interpreted by the shell before the actual
command execution. By default, the SPOTSTASK.sh script suppresses the standard
output and standard error of the task commands (both sent to /dev/null). In case you
does not want to suppress the output of the command task, the "-v" argument must be
used in the SPOTSTASK.sh script call. Example: 5,20,35,50 * * * *
SPOTSTASK.sh -v make_history.
This feature uses a table that displays the task command itself, the date of its execution
and its state (see Figure 133). Through this table you can verify if the scheduled task
was executed successfully or if it failed. This information can be obtained through the
Status tab of the table. It is possible to sort the tasks by any of the mentioned categories
present in the Scheduled Tasks Monitoring table by clicking in the respective category.
Additionally there is an information button placed on the bottom of the window that, when
clicked, displays a pop-up menu (see Figure 134) with more detailed information about
that specific task. This pop-up menu allows you to obtain additional information regard-
ing the Scheduled Task, for example whether it was a background task and if it created
a log file. In case there was a log file created, the pop-up menu displays the log file des-
tination in a text box.
Figure 133 Scheduled Tasks Monitoring window

The Scheduled Tasks Monitoring is displayed in the form of a table through which you
can view the tasks scheduled at that moment. The window has the following field:
Scheduled Tasks
• Task Command
This tab displays the command that originated the task.
• Last Execution
This tab displays the time when the task was executed.
214 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Status
This tab shows the result of the task execution.
It is possible to sort the tasks by any of the mentioned categories present in the Sched-
uled Tasks Monitoring table by clicking in the respective category.
This window has the following button:
• Click Info to open the information pop-up menu.
Figure 134 Scheduled Tasks Information Pop-Up menu
g For more information regarding the SPOTSTASK.sh please refer to Scheduler Config-
uration Edition in Chapter 4.8.3.4 SPOTS Configuration
System Logs Monitoring

The System Logs Monitoring feature allows users to read the most recent log entry
records of each of SPOTS subsystems available. The number of maximum records dis-
played is configured for each user by accessing the Preferences link on the top-right
corner in the Main Window. The system logs are monitored through a text area in which
you are able to receive the log records (see Figure 135). The System Log Analysis Tool
processes the existing SPOTS logs and output a set of statistics and values that are pre-
sented to you of the Administration Console. You are able to start the reception of these
logs records and stop them at any time by clicking the Play/Stop buttons displayed
above the text area. Additionally, it is possible to choose the subsystem which you want
to monitor. Above the text area you have four tabs to select the different subsystems
(Application Server, Naming Server, Database Server and Real Time Server). By
default, the text area displays the entries from the log when you clicked on this feature,
without further updating the displayed text. This behavior can be changed if users click
the Play button located above the text area. When the Play button is clicked the text area
gets updated as new entries are added to the log file being monitored. The default
behavior is resumed again by pressing the Stop button located above the text area.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 215

Figure 135 System Logs Monitoring window

This window has the following field:
System Logs Monitoring
This tab displays the system logs regarding the Application Server.
• Naming Server
This tab displays the system logs regarding the Naming Server.
• Database Server
This tab displays the system logs regarding the Database Server.
Each tab has the following buttons:
• Click Play to start the reception of new log records.

• Click Stop to stop the reception of new log records.
4.8.3.2 Statistical Reports

The Statistical Reports provide graphical information regarding several subsystems.
The subsystems can be selected at the Feature Group window.You can select several
subsystems to monitor and for each of these subsystem there are various statistical
reports available. After having accessed the Feature Group window, you can select the
statistical report to run. This selection is made through box menus available at the top
of the window. Additionally you can export the statistical report once it is finished by
selecting the Save button located above the graphic result. The export can create a file
in either *.pdf or *.xls format. There are five types of subsystems available to analyze
which are the following:
• Application Server Statistics.
216 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Database Server Statistics.

• Data Collection Statistics.
• Data Conversion Statistics.
• Data Loading Statistics.
g The Data Collection, Conversion and Loading Statistics are only applicable for
GERAN and UTRAN. Core is not covered by these statistics.
You can configure new statistical reports or add and edit the metrics of the already
created statistical reports. Each metric has an associated set of log codes. These log
codes define the log entries that are considered when trying to resolve the metric value.
When executing a statistic, the service determines which logs are considered by
inspecting the metrics involved. While analyzing the logs that are considered, the
service also groups the metrics by log in order to make it possible to collect all the infor-
mation required from the log with a single parse operation.
After grouping the metrics by log, the service parses each log file individually. To resolve
the entries that are considered from each log file the service uses the log codes associ-
ated with each of the metrics involved in the parse operation. In order to optimize the
parsing, the service builds a regular expression for each metric, based on the associated
log codes, and it uses it to parse the file. As a result of the parse operation, the service
receives a collection of log entries grouped by metric. These metrics consist only in the
metrics which matched the supplied regular expressions.
At this point the service has the log entries required to process the metrics values so it
resolves, for each metric, all the entries individually and extract the value according to
the metric associated aggregation function (EMetricAggregationFunction).
If the metric aggregation function is COUNT the service simply counts the number of
retrieved log entries and it creates a single metric result data instance (StatisticMetric-
Data) with the count result. The metric data object has an undefined timestamp associ-
ated considering that the metric result is a single value.
If the metric aggregation function is SUM the service extracts the value for the metric
from the log message field of each of the resolved log entries and add them according
to the metric data type (EMetricValueType). A single metric result data (StatisticMetric-
Data) is created with the sum operation result; this metric data object has an undefined
timestamp associated considering that the metric result is a single value
If the metric aggregation function is NONE the service extracts the value for the metric
from the log message field of each of the resolved log entries and create a metric result
data object (StatisticMetricData) for each entry. Each resulting metric data object is
associated with the timestamp of the corresponding log entry.
The service extracts the metric value from the log entry message field using the SPOTS
Log Message Format. The service assumes that the message field for the log entries
that are associated with metrics that require this field parsing have values structured like
the following example:
<key> = <value>{separator}<key> = <value>{separator} … <key> = <value>
The <key> represents the metric identifier, or the metric identifier alias if defined. The
<value> represents the metric value. The {separator} represents the token that is used
to separate different metrics in the same log entry; the default separator is the comma
(,).
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 217

When the service boots it collects the configuration information from a property based
configuration file (named statistics_service.properties) that is placed in a configuration
folder under the application home directory. If any of the configuration properties are not
defined in the mentioned file, the service assumes the default values defined in the
internal configuration.
The following table presents a description of all the available configuration parameters
for the Statistics service:

stat.service.statis- String ${SPOTS_ADM_DIR}/w This configuration param-
tic.descrip- ebapps/console/con- eter contains the
tions.file.pathname fig/statistics_service_co pathname to the statistics
nfiguration.xml catalog; this file defines
the statistical reports that
is available through the
service.
stat.service.met- String ${SPOTS_ADM_DIR}/w This configuration param-
rics.catalog.file.path- ebapps/console/con- eter contains the
name fig/statistics_metrics_cat pathname to the metrics
alog.xml catalog; this file describes
the available pre-defined
metrics.
stat.service.pro- Boolea False This configuration param-
file.enabled n eter enables or disables
the service profiling; when
the service profiling is
enabled the elapsed time
of the operations per-
formed by the service is
logged to the application
log files.
stat.ser- String ${SPOTS_DIR}/log4j_sp This configuration param-
vice.log4j.con- ots.properties eter contains the
fig.file.pathname pathname to the file that
contains the server
logging configuration
properties.
stat.ser- String log4j.SPOTSLogger.Off- This configuration param-
vice.log.msg.codes. setMessageCode eter contains the name of
offset.property the property defined in the
'stat.service.log4j.con-
fig.file.pathname' file. This
property depicts the value
that offsets log message
codes with associated
metrics.
Table 13 Statistics service configuration parameters
218 Id:0900d8058018db2b E200613-01-114-V14.0I-23


stat.ser- String = This configuration param-
vice.log4j.con- eter contains the token
fig.property.key.valu used as the key value sep-
e.separator arator in the log4j configu-
ration file (defined in the
parameter 'stat.ser-
vice.log4j.config.file.path-
name').
Table 13 Statistics service configuration parameters (Cont.)
Application Server Statistics

The Application Server Statistics (Figure 136) provide statistical information regarding
the application server behavior that includes: application server restarts and crashes,
memory usage, running reports or logged users. Additionally you can export the statis-
tical report once it is finished by selecting the Externalize check box located above the
graphic result. The export can create a file in either *htm, *.pdf or *.xls format.
Figure 136 Application Server Statistics

Statistic Report
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 219

This field has the following areas:

• Available Reports
In this area you choose the statistical report which is to be performed.
• Select Output
In this area you can choose the type of file in which you want to export the report
and perform that operation.
• Click Combo box to choose the type of file in which the report is
to be exported.
• Click View to view the Statistical Report in the Window.
• Click Details to view the details of the Statistical report.
Database Server Statistics
The Database Server Statistics (see Figure 137) provide statistical information regard-
ing the database server behavior that includes for example: database server restarts
and crashes, database internal errors, database occupancy, loaded metadata, make
history, among others. Additionally you can export the statistical report once it is finished
by selecting the Externalize check box located above the graphic result. The export can
create a file in either *htm, *.pdf or *.xls format.
Figure 137 Database Server Statistics
220 Id:0900d8058018db2b E200613-01-114-V14.0I-23


Statistic Report
• Select Output
In this area you can choose the type of file in which they want to export the report
to be exported.
Data Collection Statistics

The Data Collection Statistics (see Figure 138) provide statistical information regarding
the data collection history. A statistical report is generated with the data collection
pattern that includes information regarding the type and amount of files collected,
among others. Additionally you can export the statistical report by selecting the Exter-
nalize check box located above the graphic result. The export can create a file in either
*htm, *.pdf or *.xls format.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 221

Figure 138 Data Collection Statistics

Statistic Report
• Select Output
to be exported.

Data Conversion Statistics
The Data Conversion Statistics (Figure 139) provide statistical information regarding the
222 Id:0900d8058018db2b E200613-01-114-V14.0I-23

data conversion history. A statistical report is generated with the data conversion pattern
that includes information regarding the type and amount of files being converted, and
the number of conversion errors. Additionally you can export the statistical report by
selecting the Externalize check box located above the graphic result. The export can
create a file in either *htm, *.pdf or *.xls format.
Figure 139 Data Conversion Statistics

Statistic Report
• Select Output
to be exported.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 223


Data Loading Statistics
The Data Loading Statistics (Figure 140) provide statistical information regarding the
data loading history. A statistical report is generated with the data loading pattern that
includes information regarding the type and amount of files (and records) being loaded,
among others. Additionally you can export the statistical report by selecting the Exter-
nalize check box located above the graphic result.The export can create a file in either
*.htm, *.pdf or *.xls format.
Figure 140 Data Loading Statistics

Statistic Report
224 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Select Output
to be exported.
4.8.3.3 Database Queries

The Database Queries Feature Group provides a set of predefined queries that allow
you to retrieve specific information from the database. This feature is very similar to the
Statistical Reports feature. The only difference is that you now access results from
database queries.
After having accessed the Feature Group window you can select what query to run in
the Database Views Feature (see Figure 141). This selection is made through box
menus available at the top of the window. There is also an information button available
on each of the queries reports’ selection box to provide detailed information on that
report’s purpose. Additionally you can export the statistical report by selecting the Exter-
nalize check box located above the graphic result. The export can create a file in either
*.pdf or *.xls format.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 225

Figure 141 Database Views window

View Report
• Date
This tab displays the date and time the warning started.
• System
This tab displays the subsystem where the warning was originated.
• Severity
This tab shows the gravity of the warning (Critical/Major/Warning).
• Probable Cause
• Message
This tab displays a message that either comments the warning or provides informa-
tion regarding actions to be taken.
The View Report field has the following areas:
226 Id:0900d8058018db2b E200613-01-114-V14.0I-23

• Select Output
In this area you can choose the type of file in which you want to export the report
to be exported.
4.8.3.4 SPOTS Configuration

The Spots Configuration Group Feature allows you to edit and configure several system
processes configuration parameters. These configurations can be accessed in the
Feature Group window. The configuration parameters available are:
• Processes Configuration Edition
• Scheduler Configuration Edition
Processes Configuration Edition
The Processes Configuration files edition (see Figure 142) is performed using two
distinct mechanisms, one for property based configuration files and another for complex
file types. The property based configuration files are edited using an appropriate form
based editor and the other configuration files are edited using a free text editor.
Through this feature you can select which subsystem to configure by means of tabs
located on the top of the window. The report is selected through a drop down menu.
According to the selected configuration file the Administration Console opens the form
editor or the free text editor. To begin editing the file you need to activate the by clicking
the Edit button. After editing the configuration file, you can save the changes by clicking
the Save button. The configuration parameters are displayed in the form of a textbox
which has an information button available. By clicking this button a pop-up with the
description of the configuration parameter appears with its usage details.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 227

Figure 142 Processes Configuration Edition window

SPOTS Configuration
• Collectors
To configure the Collectors.
• Database Server
To configure the Database Server.
To configure the Application Server.
• Naming Server
To configure the Naming Server.
The Processes Configuration window has the following buttons:
• Click Select a file drop down menu to choose the file to edit.
• Click Edit button to begin editing the file and click again to exit the edit mode.
• Click Save button to save the changes made in the file.
Scheduler Configuration Edition
Through the Scheduler Configuration Edition window (see Figure 143) you are able to
change the scheduler configuration. To begin editing the file you need to activate the edit
mode by clicking the Edit button. After editing the configuration file, you can save the
changes by clicking the Save button. Considering the differences between the Windows
scheduler and the Unix scheduler (Crontab), the Scheduler Configuration Edition
feature may require two distinct interfaces in order to offer all the corresponding sched-
uler features. The solution for the Unix scheduler (Crontab) is presented.
228 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 143 Scheduler Configuration Edition window

Scheduler Configuration
This field allows you to edit the scheduler configuration when the edit mode is activated.
The Processes Configuration window has the following buttons:
• Click Edit button to begin editing the file and click again to exit the edit mode.
• Click Save button to save the changes made in the file.
g For you to configure a Scheduled Task it is necessary to insert SPOTSTASK.sh before

the desired task. For example, for the task 5,20,35,50 * * * * make_history, it is neces-
sary to type 5,20,35,50 * * * * SPOTSTASK.sh make_history.
4.8.4 Data Collection Monitoring

Data Collection Monitoring monitors data collection and issues an alarm if any problems
are detected. These problems can range from the collection itself to metadata validation
problems. If a measurement does not contain all its counter values or if it is associated
to a wrong or unknown version, the measurement is not loaded and an error is logged.
In this case an Active Warning (AW) event with MAJOR severity is issued. In order to
prevent a possible AW flood, only one single AW per measurement and per day is gen-
erated.
The SPOTS Data Collection subsystem comprises a set of functional modules respon-
sible for the collection, conversion and forwarding of PM/CM data to other SPOTS sub-
systems. It is composed of:
• Collectors, which collect PM data files from different Commanders and PDCs.
• Converters, which convert PM data from different types and formats into SPOTS
internal format, and forward it to the SPOTS Server and TES. Based on different
types of inputs, for example symbolic names files, converters can also generate CM
data files to be loaded into SPOTS Extended Fields.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 229

• Collector command, which enables the synchronized launching of all Collectors.

• Loader command, which enables the synchronized launching of all Converters.
The SPOTS Database Server is responsible for data storage, providing the interface
between the SAS and the SPOTS Database.
For all of the DCM functionalites the kind of action to be taken upon validation failure is
common to all components which is to issue a log entry or generate an AW.
Validation of PM file format
Each core network converter validates if the PM file format is according to what is
expected.
The AWs related to such validation are presented in the following table and are gener-
ated, when appropriate.
Message Active Source Name Severity Probable

code Warning Flag system cause
name
6043 TRUE DataCon- Input file MAJOR Input file
verters opening opening
error error
6048 TRUE DataCon- Parsing MAJOR Parsing
verters Error Error
6054 TRUE DataCon- Filename MAJOR Filename
verters not sup- not sup-
ported ported
6055 TRUE DataCon- File con- MAJOR File con-
verters verted but verted but
some line(s) some line(s)
could not be could not be
parsed parsed
Table 14 AWs related to validation of PM file format
Only one AW event is generated for this kind of problem, in each reporting period. In the
subsequent periods, if the problem persists, an AW event is also generated.
Validation of unknown data model
Each core network converter validates if the PM file content is aligned with the converter
internal metadata. This allows the detection of unknown or wrong counter names, mea-
surement versions, among others. The AWs related to such validations are presented
in the following table and is generated, when appropriate.
230 Id:0900d8058018db2b E200613-01-114-V14.0I-23


code Warning flag system cause
name
6032 TRUE DataCon- Converter MAJOR Converter
verters metadata metadata
missing missing
6058 TRUE DataCon- Mapping MAJOR Mapping
verters info not info not
found for found for
measure- measure-
ment/ver- ment/ver-
sion sion
6076 TRUE DataCon- Mapping MAJOR Counter not
verters info not supported or
found for not in
counter mapping
files
Table 15 AWs related to validation of unknown data model
Only one AW event is generated for this kind of problem, in each reporting period. In the
subsequent periods, if the problem persists, an AW event is also generated.
Validation of the connection to EM
All core network collector components detect and log the error caused by a network
failure.
In this case, the following AW event must be generated in each reporting period:

name
5003 TRUE DataCollec- EM con- CRITICAL No LAN con-
tors nection nection or
broken Com-
mander is
down
Table 16 AWs related to validation of the connection to EM
In the subsequent periods, if the problem persists, an AW event is also generated.

Validation of missing data for rolling counters
The implemented algorithm always stores the current counter values for a specified
measurement/object pair in a file. These values are used in the next granularity period
to compute the difference relative to the new values for the same measurement/object
pair.
If the previous counter values are missing from the file, the AW event present in the fol-
lowing table is generated.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 231


name
6075 TRUE DataCon- Missing MAJOR Problems in
verters information the collec-
for rolling tion/conver-
counters sion
Table 17 AWs related to validation of missing data for rolling counters
Only one AW event per reporting period is generated. In the subsequent periods, if the
problem persists, an AW event is also generated.
Validation of empty PM files
This validation is common to all core network converters. During the conversion cycle
each component gathers information about empty files detected, as well as other infor-
mation associated to the files being converted. After the conversion cycle it issues log
entry 6003, present in Table 18, if applicable.
DCM metrics
Each DC component gathers several statistics relative to the collection and conversion
process.
The following log messages apply:
Code Message Level Active

Warning
flag
5000 dataCollection- SPOTS_INFO FALSE
Files={nr};EMName{EM_name}
5001 dataCollectionDura- SPOTS_INFO FALSE
tion={time_seconds};EMName{EM_na
me}
5002 dataCollectionVol- SPOTS_INFO FALSE
ume={size_bytes};EMName{EM_nam
e}
6000 dataConversionFiles={nr} SPOTS_INFO FALSE
6001 dataConversionDura- SPOTS_INFO FALSE
tion={time_seconds}
6002 dataConversionVolume={size_bytes} SPOTS_INFO FALSE
6003 emptyDataFiles={nr} SPOTS_INFO FALSE
6004 rejectedDataFiles={nr} SPOTS_INFO FALSE
Table 18 AWs related to DCM metrics
4.8.5 Systems Monitoring

Systems Monitoring
232 Id:0900d8058018db2b E200613-01-114-V14.0I-23

The System Monitor (System Monitor Sysmon) interfaces with the Active Warnings for
dispatching the active warnings into the system. This type of operation allows a
complete separation of this application from the rest of the SPOTS subsystems resulting
in a complete decoupled solution. There is a configuration file that allows the configura-
tion of the activation state on the several active warnings processed by the monitor
application. The configuration file defines for each active warning its activation state,
with two possible values: on and off, and, its severity as defined in the severity field of
the alarm structure. The Sysmon runs continuously in order to collect periodical metrics.
These metrics are used by the appplication to detect operating system (OS) problems
that happen in the SPOTS System. The Sysmon runs cyclically with a period that is con-
figurable. It is possible to configure the size of the log. This imposes a limit on the data
that needs to be inspected by the system when looking for problems.When a problem is
detected, the Sysmon launches an event to the Active Warnings. There is no notion of
state maintenance and control in active warnings managed by the Sysmon. Every time
the monitor cycle runs, if a problem is detected, a warning is generated without knowing
whether the warning was already reported in one of the previous cycles.There is a con-
figuration file that allows activation state configuration on the several active warnings
processed by the monitor application.This configuration file has the name
$SPOTS_DIR/sysmon.cfg and contains all the essential parameters for the SYSmon
basic functionality plus the specific entries for each execution module. The configuration
file defines for each active warning its activation state (two possible values exist: on and
off) and its severity as defined in the severity field of the alarm structure.
The funcitonalities of the System Monitoring can be divided into high level groups of
functionality that serve different purposes:
• OS Monitoring: collects information about processes, cpu, disks and partitions,
memory, swap, network.
• Scheduled Tasks Monitoring: collects information about scheduled tasks executed
time, last scheduler error, among others.
• Log Files Inspection: inspects the log files to find errors that must be reported by
active warnings.
• Database Monitoring: collects information about the database instance, database
listener, the storage capacity, among others.
The Systems Monitoring is executed in a periodic basis. Different periodicities must
be defined. This means that the Systems Monitoring executes different processes,
with each one executed within a different time interval. Default periodicities are 2
minutes,1 hour and 24 hours.
A description of the necessary metrics analysed by Sysmon and the log file entries for
each metric is given in the next tables:
Metric dataCollectionDuration
Description Search the logs to determine how much time was necessary to
collect the available NE's files into SPOTS System.
Log File GetDataFromXXX<n>.log
Log Message
Format
Table 19 dataCollectionDuration Metric
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 233

Metric dataCollectionEvents
Description Provides the history for Data Collection. A report is generated with
the Data Collection pattern. The information available is the amount
of files being collected.
Log Message
Format
Table 20 dataCollectionEvents Metric
Metric dataCollectionFiles
Description Search the logs to find the number of collected files during the col-
lection phase of the ETL process.
Log Message
Format
Table 21 dataCollectionFiles Metric
Metric dataCollectionVolume
Description Search the logs to determine the amount of data (in bytes) collected
from the NE's in the phase of data collection.
Log Message
Format
Table 22 dataCollectionVolume Metric
Metric dataConnectionUnavailableEvents
Description Search the logs to count the number of detected problems in the
connectivity to the NE's.
Log File Converter Log files
Log Message
Format
Table 23 dataConnectionUnavailableEvents Metric
Metric dataConversionDuration
Table 24 dataConversionDuration Metric
234 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Description Search the logs to determine out how much time was necessary to
convert files previously collected into SPOTS System.
Log File
Log Message
Format
Table 24 dataConversionDuration Metric (Cont.)
Metric dataConversionErrors
Description Search the logs to find the number of conversion errors detected
while parsing the EM files.
Log Message
Format
Table 25 dataConversionErrors Metric
Metric dataConversionEvents
Description A report is generated with the Data Conversion pattern. The infor-
mation available has the type and amount of files being converted,
and the number of conversion errors.
Log File Converter log files
Log Message
Format
Table 26 dataConversionEvents Metric
Metric dataConversionFiles
Description Search the logs to find the number of converted files during the con-
version phase of the ETL process.
Log File Converter log files
Log Message
Format
Table 27 dataConversionFiles Metric
Metric dataConversionVolume
Description Search the logs to determine the amount of data (in bytes) con-
verted from the NE’s file format to the SPOTS format in the data
conversion phase of the ETL process.
Table 28 dataConversionVolume Metric
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 235

Log File Converter Log files

Log Message
Format
Table 28 dataConversionVolume Metric (Cont.)
Metric dataLoadingDuration
Description Search the logs to determine the time taken to import files into
SPOTS database.
Log File sas<n>.log
Log Message
Format
Table 29 dataLoadingDuration Metric
Metric dataLoadingErrors
Description Search the logs to find the number of errors detected during the load
of the data from the NEs into SPOTS System.
Log File dbloader<n>.log
Log Message
Format
Table 30 dataLoadingErrors Metric
Metric dataLoadingEvents
Description A report is generated with the Data Loading pattern. The information
available has the amount of files and records being loaded.
Log File sas<n>.log
Log Message
Format
Table 31 dataLoadingEvents Metric
Metric dataLoadingVolume
Description Search the logs to determine the amount of data (in bytes) imported
into SPOTS database.
Log File sas<n>.log
Log Message
Format
Table 32 dataLoadingVolume Metric
236 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Metric dbDetailedDataRecords
Description Count the number of detailed data records existent in the DB.
Log File SYSmon<n>.log
Log Message message_code=7002+BASE_CODE message_text=<Total
Format Detail Record:nnn>
Table 33 dbDetailedDataRecords Metric
Metric dbFreeSpace
Description Request the amount of free space present in a database
tablespace.
Log Message message_code=7005+BASE_CODE message_body=<Total
Format Free Space: nnnn>
Table 34 dbFreeSpace Metric
Metric dbHistoryDataRecords
Description Count the number of historical data records existent in the DB.
Format History Records:nnnn>
Table 35 dbHistoryDataRecords Metric
Metric dbNumberOfObjects
Description Count the number of objects that currently exist in SPOTS data-
base.
Log Message message_code=7001+BASE_CODE message_text=<Total
Format Detail Record:nnn>
Table 36 dbNumberOfObjects Metric
Metric dbUsedSpace
Description Request the amount of used space present in a database
tablespace.
Table 37 dbUsedSpace Metric
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 237


Format Used Space: nnnn>
Table 37 dbUsedSpace Metric (Cont.)
Metric emptyDataFiles
Description Search the logs to detect the number of processed NE files that
have 0 bytes in length.
Log File
Log Message
Format
Table 38 emptyDataFiles Metric
Metric metadataLoadErrors
Description Search the logs to find errors occurred during the installation of the
metadata into SDS.
Log File sds<n>.log
Log Message
Format
Table 39 metadataLoadErrors Metric
Metric metadataLoadOperations
Description Search the logs to read the entries related to the import of metadata
into SDS.
Log File sds<n>.log
Log Message
Format
Table 40 metadataLoadOperations Metric
Metric oraErrorEvents
Description Search the logs to find for errors related to Oracle. Oracle errors are
reported in the logs as ORA XXX.
Log File sds<n>.log
Table 41 oraErrorEvents Metric
238 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Log Message Code=8001+BASE_CODE Body=ORA-14400: inserted

Format partition key does not map to any
partitionCode=8002+BASE_CODE Body= ORA-00257:
archiver error. Connect internal only, until
freedCode=8003+BASE_CODE Body=ORA-00001: unique
constraint (key) violatedCode=8004+BASE_CODE
Body=ORA-00018: maximum number of sessions
exceededCode=8005+BASE_CODE Body=ORA-00028: your
session has been killedCode=8006+BASE_CODE
Body=ORA-00054: resource busy and acquire with
NOWAIT specifiedCode=8007+BASE_CODE Body=ORA-
00069: cannot acquire lock -- table locks disabled
for nameCode=8008+BASE_CODE Body=ORA-00057:
maximum number of temporary table locks
exceededCode=8009+BASE_CODE Body=ORA-01041:
HOSTDEF extension does not
existsCode=8010+BASE_CODE Body=ORA-03113: end-of-
file on comunication channelCode=8011+BASE_CODE
Body=ORA-03114: not connected to
ORACLECode=8012+BASE_CODE Body=ORA-12154: TNS:
could not resolve service nameCode=8013+BASE_CODE
Body=ORA-12203: TNS: unable to connect to
destinationCode=8014+BASE_CODE Body=ORA-12224:
TNS: no listenerCode=8015+BASE_CODE Body=ORA-
12571: TNS:packet writer
failureCode=8016+BASE_CODE Body="ORACLE EXCEPTION
..."
Table 41 oraErrorEvents Metric (Cont.)
Metric rejectedDataFiles
Description Search the logs to find the number of PM data files that were
rejected during an import operation.
Log File
Log Message
Format
Table 42 rejectedDataFiles Metric
Metric rtCrashEvents
Description Search the logs to find the number of RT crashes present in the
logs.
Table 43 rtCrashEvents Metric
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 239

Log File monitor<n>.log

manager<n>.log
apm<n>.log
agencylauncher<n>.log
agency_<agency name>_<n>.log
agent_<agency_name>_<agent type>_<n>.log
Log Message message_code=1002+BASE_CODE message_text=Monitor
Format Crashed
message_code=2002+BASE_CODE message_text=APM
Crashed
message_code=3002+BASE_CODE message_text=Manager
Crashedmessage_code=4002+BASE_CODE
message_text=Agency
message_text=Agent
message_text=Agencylauncher Crashed
Table 43 rtCrashEvents Metric (Cont.)
Metric rtErrorEvents
Description Search the logs to find the number of RT errors present in the logs.
manager<n>.logapm<n>.logagencylauncher<n>.logagen
cy_<agency
name>_<n>.logagent_<agency_name>_<agent
type>_<n>.log
Log Message message_code=1003+BASE_CODE message_text= Error!
Format <Error Description>message_code=2003+BASE_CODE
message_text= Error! <Error
Description>message_code=3003+BASE_CODE
message_text= Error! <Error Description>
Table 44 rtErrorEvents Metric
Metric rtMemoryConsumption
Description To find out how the amount of memory is used by the RT server
search the logs.
Table 45 rtMemoryConsumption Metric
240 Id:0900d8058018db2b E200613-01-114-V14.0I-23


Log Message message_code=1005+BASE_CODE message_text=Memory
Format Used-<Value in Mbytes>
message_code=2005+BASE_CODE message_text=Memory
Used-<Value in Mbytes>message_code=3005+BASE_CODE
message_text=Memory Used-<Value in
Mbytes>message_code=4005+BASE_CODE
message_text=Memory Used-<Value in Mbytes>
Table 45 rtMemoryConsumption Metric (Cont.)
Metric rtRestartEvents
Description Search the logs to find the number of RT restarts present in the logs.
cy_<agency
type>_<n>.log
Log Message message_code=1001+BASE_CODE message_text=Monitor
Format Started
message_code=2001+BASE_CODE message_text=APM
Startedmessage_code=3001+BASE_CODE
message_text=Manager
message_text=Agency
message_text=Agent
message_text=Agencylauncher Started
Table 46 rtRestartEvents Metric
Metric rtSystemConnectFailureEvents
Description Search the logs to detect the number of processed NE files that
have 0 bytes in length.
Table 47 rtSystemConnectFailureEvents Metric
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 241


cy_<agency
type>_<n>.log
Log Message message_code=1004+BASE_CODE
Format message_text=Connection Error! <Error Description
message_code=2004+BASE_CODE
message_text=Connection Error! <Error
Description>
Table 47 rtSystemConnectFailureEvents Metric (Cont.)
Metric saaCrashEvents
Description Search the logs to find the number of SAA crashes present in the
logs.
Log File sas<n>.log
Log Message
Format
Table 48 saaCrashEvents Metric
Metric sasMemoryConsumption
Description To find out how the amount of memory currently used by the SAS
search the logs.
Log File sas<n>.log
Log Message
Format
Table 49 sasMemoryConsumption Metric
Metric sasRestartEvents
Description To find the number of SAS restarts present in the logs search the
logs.
Table 50 sasRestartEvents Metric
242 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Log File sas<n>.log

Log Message
Format
Table 50 sasRestartEvents Metric (Cont.)
Metric sdsCrashEvents
Description Search the logs to find the number of SDS crashes.
Log File sds<n>.log
Log Message
Format
Table 51 sdsCrashEvents Metric
Metric sdsMemoryConsumption
Description Search the logs to find out what amount of the memory is currently
being used by the SDS.
Log File sds<n>.log
Log Message
Format
Table 52 sdsMemoryConsumption Metric
Metric sdsRestartEvents
Description Search the logs to find the number of SDS restarts.
Log File sds<n>.log
Log Message
Format
Table 53 sdsRestartEvents Metric
4.9 Best Practices

This chapter provides guidelines to SPOTS users and administrators in order to improve
SPOTS performance and stability.
For best practices regarding Real Time functionality see Annex 4 in Installation Guide.
4.9.1 SPOTS Architecture and Services

SPOTS product, to be functional, requires the following services active and properly
configured.
SPOTS Server Services:
• SPOTS Application Server (SAS)
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 243

• SPOTS Database Server (SDS)

• SPOTS Naming Server (SNS)
PM Client Services:
• Java based client (PMC)
Overview
Figure 144 SPOTS services

Nokia Siemens Networks assumes that the required DCN and Connection between
SPOTS and OSS equipment is available and working for on-line data collection accord-
ing to OSS/Network Element performance guidelines in terms of Granularity Period con-
figuration (for example fetch new PM data hourly based).
It is also assumed that PM Client connection is never interrupted during an active PM
client session. Close PM client before unplugging the network cable, undocking the
laptop, shutting down the machine, among others.
g Any connection failure between the SPOTS Client and the SPOTS Server, while the
SPOTS Client is opened, may cause instability problems in the SPOTS Server.
All services should be up and running (green status in SPOTS System bar) to ensure
that SPOTS is functional.
244 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 145 SPOTS Welcome window

If you do not have access to SPOTS Administration Console feature and PM client does
not seem to start or hang, please get in contact with your administrator to check if the
services are running (services restart action can be executed with small downtime).
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 245

4.9.2 Saving SPOTS Server Resources (CPU, RAM …)
4.9.2.1 Creating Reports

Ad-Hoc Reports best practices
Figure 146 SPOTS object tree

When tens of objects, or more, are going to be used in a report, Set of Objects (SoO)
feature should be used as a first step. Later, this SoO can be used as a report parame-
ter. The above figure shows the correct steps to be performed in case a higher number
of objects is going to be used.
1. Set of Objects - use of wildcards in reports
Figure 147 Set of Objects window

It is important that wildcards are used in reports to reduce system resources consump-
tion during reports execution. Performance is improved by having reduced database
queries on object level (less information flow between client-server connection and
object control check).
In report creation instead of the following list, only one virtual object is selected (number
2 in SPOTS object tree figure)
246 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 148 List of objects
Figure 149 Virtual object

It is also easy to create a Dynamic SoO using a Rich Expression Editor. Sets of objects
created using Rich Expression Editor are evaluated during execution time. They are a
very flexible and powerful option.
Context help is available as a regular Integrated Development Environment (IDE) by
pressing Ctrl+Space, and expression validation is always being performed in back-
ground (note the “OK” and “Error” icons in the bottom right of the Expression Editor), so
you can be aware of possible errors.
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 247

Figure 150 Expression Editor

In case of network expansions, SPOTS not only automatically detects new NEs (inde-
pendently of the use of wildcards), but also provides update of new NEs contained in
reports automatically. Reports are always up-to-date with less manual intervention from
reports’ author.
g SoO is commonly used for object aggregation, for example to aggregate all BTS KPI into
BSC level.
248 Id:0900d8058018db2b E200613-01-114-V14.0I-23

Figure 151 Object aggregation
Data granularity
The granularity used defines the sampling interval to be used in reports. The higher
(coarser) the granularity, the lower the number of samples in a report. In this case, the
resource consumption (CPU, memory, among others) to execute a report is higher and
the execution time is longer.
To minimize system resources consumption, prefer the original granularity available in
SPOTS database. When executing an Ad-Hoc Report with a granularity that is different
from the inherent data granularity, there is always an overhead associated to aggrega-
tion or disaggregation operations.
Whenever possible, prefer Historical Data values (Daily Totals and SPBH) to Detailed
Data (DAILY, HOUR_QUARTERLY, among other raw data). Historical Data values are
pre-calculated and stored in the database for further usage avoiding the computational
effort associated to the aggregation algorithms, improving processing time. This gain in
processing time may be irrelevant for just a few objects, but not when executed for the
entire network.
Choosing higher (coarser) granularities also improves Trend Analysis, because longer
time spans are used.
User Interface
The report output should be adequate to the amount of data expected. SPOTS GUI
Client is limited in system resources and it can get clogged when displaying a large
report, due to network connectivity, memory or processor issues. As a general rule,
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 249

output to file if a massive volume of data is expected; output to chart if a small volume
of data is expected and output to table as a general rule.
Whenever possible use the wizard features presented in SPOTS GUI Client as it allows
users to easily perform frequent operations with step-by-step assistance while maintain-
ing flexibility. Using this method also offers the benefit of reducing the occurrence of user
mistakes.
4.9.2.2 Executing Reports

Scheduler feature is very useful whenever you are aware that a report execution is going
to take a long time or consume a large amount of system resources. By scheduling the
report execution time, user is able to avoid overloading the system during working hours,
contributing to a more balanced resource usage. This is particularly useful when period-
ically executing large reports that can be executed during the off-peak hours.
SPOTS provides “scheduler task” and “scheduler Job” options. In case several tasks
have the same frequency they should be within the same job (for example daily reports).
Figure 152 Scheduler window
g Try to always consolidate all the scheduled reports within the same Job. Scheduler Job
feature activation reserves some memory which can be saved by reducing the number
of Jobs.
g Request support to administrator Make History ending time (SPOTS system aggrega-
tions for the Sample Peak Busy Hour and Daily Total calculations). Avoid scheduling any
reports that are doing on-the-fly-aggregations to run during the Make History execution
period. Avoid running reports that make aggregations on-the-fly. Waiting for the end of
the Make History processing allows the use of the pre-aggregated values that were
created by Make History, improving considerably the reports' performance as well as
general system performance.
250 Id:0900d8058018db2b E200613-01-114-V14.0I-23

g Avoid overlapping scheduled Jobs by trying to distribute scheduled Jobs during low uti-
lization period. Avoid overlapping scheduled jobs in time. A good way to do this is by
running reports in a same job, which runs them in sequence.
4.9.2.3 Saving Reports

Reports that are going to be edited or reused at a later time should be saved to minimize
duplicated effort. User has the choice of saving the report as a public or a private task.
Changing the visibility of the task to Public allows different audiences to reuse it.
4.9.2.4 Virtual Entities

SPOTS stores almost all information in databases, but Virtual Entities (VC, SoO, SoC)
are exceptions.
Figure 153 Virtual entities

In this case, the information is stored in several types of files within SAS. These files can
become so large that SAS can spend a lot of time parsing and processing data, slowing
down the response time in SPOTS Client, such as:
• For a given object class, each time you ask for a list of instances and simultaneously
asks for a list of Set of Objects.
• Each time you ask for a list of measurements, counters, and simultaneously asks for
a list of Virtual Counters and Set of Counters available from the selected instances.
• Whenever you open the Scheduler for creating or editing jobs.
• Whenever you open the Scheduler Browser.
• When you open the SPOTS CL, it is necessary to load the files associated to the
Tasks created by you in previous sessions, from SAS to SPOTS SCL.
4.9.3 Using PM Client Resources

SPOTS PM client is a Java based application that requires user equipment resources
when running.
By having memory resources allocated to SPOTS from client machine (for example user
laptop), several client-server information flow can be reduced since it can be kept on
client machine side (that is network elements object tree, online help, among others).
PM client application memory limits are configurable and can be changed by you to
higher values if the machine has the available resources - Physical RAM.
To change memory parameter, perform the following steps:
E200613-01-114-V14.0I-23 Id:0900d8058018db2b 251

1 Go to SPOTS PM Client folder, default is C:\NSN\SPOTS-PMC

2 Edit spots.bat file with, for example, Windows Notepad
3 Replace memory limit value in Start /D"C:\NSN\SPOTS-PMC" %SPOTS_JRE%\
bin\javaw.exe –Xmx512m -jar .\lib\spots-client.jar -s
10.46.19.164 -p 50000 %1 to higher, for example, 1024.
g SPOTS minimum is 512m.

Half of physical memory is recommended, for example, with 3GB of RAM 1.5 can be
allocated to SPOTS PM Client.
4.9.4 PM Client version

SPOTS PM client must have the exact same version of Application Server. If you are
the system administrator, ensure that all the client PCs have the latest patch set version
of the software that is aligned with the server. Any client that is accessing SPOTS Appli-
cation Server in a different situation probably affects SPOTS system stability.
4.9.5 Network elements load

One of the parameters for SPOTS system dimensioning is the expected load in terms
of raw data that needs to be handled per 15 minutes, hour or day.
Nokia Siemens Networks recommendations are used for standard definition in terms of
system CPU, RAM and disks configuration.
Check also within OSS or network element customer documentation the recommended:
• PM measurements that should be active
• PM data collection granularity (see Appendix F- SPOTS Hardware dimensioning
Assumptions)
Contact Nokia Siemens Networks support for a different Network Element configuration.
SPOTS provides system check mechanisms (for example spotscheck script) that can
be used as an indicator of the available system capacity.
4.9.6 User Management

SPOTS system should not hang due to the number of concurrent sessions active in the
Application Server. It is very important to ensure that this situation is not reached and,
in order to control and improve the system’s behavior, simpler user actions can be done
to prevent it, such as:
• Always log out from SPOTS application in case you are not going to use the session.
This ensures that server user sessions and resources are released.
• Always try to use your own user when accessing to PM client.
Although SPOTS Application allows more than one user session with the same user
in parallel (for example one user name and password for the “planning” department),
in case of performance decreased, due to the amount of logged users, the adminis-
trator cannot identify the user that is creating the load.
252 Id:0900d8058018db2b E200613-01-114-V14.0I-23

User Manual (UMN) References
5 References
5.1 Appendix A - Thresholds
5.1.1 Thresholds CSV Files

The Import/Export of Threshold Configuration Data is done using CSV files. This means
that a CSV file with a pre-defined format is used to store all the relevant information nec-
essary to define Thresholds.
g During the threshold import process the Agencies are stopped. In order to restart the
agencies, the user should restart manually their execution.
For more information on how to start agencies manually, please refer to PDC Types
window (see 4.5.6).
The following figure is an example of a table of thresholds, exported to a CSV file:
Figure 154 Thresholds CSV file opened with MS Excel

Where:
Column Column Name Observations Default Values

Number
1 Exist Status for this Threshold on the SPOTS RT Automatically defined by
Database. SPOTS when exporting CSV.
Allowable Values: YES – This threshold is
present on the SPOTS Database
NO – This threshold is not present on the
SPOTS Database.
In order to improve the performance of this
action, the user can filter the result of this
column by the value "YES" and then create
a new CSV file where only the filtered
results appear. This improves future import
processes of Threshold Configuration Data.
2 Object Class Name of the Object Class. Must be a valid Automatically defined by
SPOTS Object Class. SPOTS when exporting CSV.
Allowable Values: Alphanumeric Characters
(0..1,a..z,A..Z,-,_)
Maximum character count = 255 characters.
Table 54 Fields Description of the Thresholds CSV files
E200613-01-114-V14.0I-23 Id:0900d80580165955 253

References User Manual (UMN)

Number
3 Measurement Name of the measurement. If Virtual Automatically defined by
Counter, place an ‘-‘ character. Must be a SPOTS when exporting CSV.
valid Measurement for the Object Class
specified in column 3. Only the Measure-
ment name used in the GUI is relevant, the
versions are not important for the RT db.
(0..1,a..z,A..Z,-,_)
4 Counter Name of the Counter. If Virtual Counter, Automatically defined by
place an ‘-‘ character. Must be a valid SPOTS when exporting CSV.
counter for the Measurement specified in
column 3.
(0..1,a..z,A..Z,-,_)
5 Virtual Counter Name of the Virtual Counter. If it’s not a Automatically defined by
virtual counter, place an ‘-‘ character. Must SPOTS when exporting CSV.
be an existing virtual counter for the Object
Class specified in column 2.
(0..1,a..z,A..Z,-,_)
6 Threshold Class Name of the Threshold class that this Automatically defined by
Threshold is related. The Threshold class SPOTS when exporting CSV.
must already exist prior to the import opera-
tion.
(0..1,a..z,A..Z,-,_)
7 Threshold Name Threshold Name. Automatically defined by
Allowable Values: Alphanumeric Characters SPOTS when exporting CSV.
(0..1,a..z,A..Z,-,_)
8 Severity Severity Value. “MINOR”
Allowable Values: “WARNING”
“MINOR”
“MAJOR”
“CRITICAL”
Table 54 Fields Description of the Thresholds CSV files (Cont.)
254 Id:0900d80580165955 E200613-01-114-V14.0I-23


Number
9 Activation State Activation State of the Threshold. “OFF”
Allowable Values: “ON”
“OFF”
10 Value Threshold activation value. –9999999,99
Allowable Values: Double (from –
9999999,99 to 9999999,99).
11 Clear Percentage Threshold clear percentage value. 0
Allowable Values: Positive double (from 0 to
100).
12 Cross Direction Threshold trigger cross direction. “DOWN”
Allowable Values: “UP”
“DOWN”
E200613-01-114-V14.0I-23 Id:0900d80580165955 255


Number
13 Monitoring Period List Threshold Monitoring Period List. “start=00:00.end=24:00.week-
Format of the list: start=<start days=ALL“
time>.end=<end time>.weekdays=<week
days>| start=<start time>.end=<end
time>.weekdays=<week days>| …|
start=<start time>.end=<end time>.week-
days=<week days>
A Monitoring period entry is defined by three
values, the start time, end time and week
days. The times are filled in the <start time>
and <end time> string sections. The format
of the time is <hh>:<mm>.The week days
are filed in the <week days> string sections.
The format of the week days is
<ALL>,<WD>,<NWD> or <MO-TU-WE-TH-
FR-SA-SU>.
Each Monitoring period must have a start
and an end time. The start time must be less
than the end time. Both the start and end
times are relevant only for the same day,
that is, no time overlaps between consecu-
tive days are allowed. Consecutive monitor-
ing periods can be added to the list by using
the character ‘|’ as list separator. If no Mon-
itoring periods are defined, then the charac-
ter “-“ should be placed. Allowable Values:
• The <hh> field is a two digit integer with
range from 00 to 23. The <mm> field is
an two digit integer with range from 00 to
59.
• The <ALL> week days specify all the
week days. example-
start=00:00.end=12:00.weekdays=ALL
• The <WD> specify all Working Days
defined in the SCL preferences.exam-
ple- start=00:00.end=12:00.week-
days=WD
• The <NWD> specify all the Non Working
Days, which are the remaining days of
the week that are not Working
Days.example-
start=00:00.end=12:00.week-
days=NWD
• The <MO-TU-WE-TH-FR-SA-SU>
specifiy individual week days. At least
one week day must be specified in the
list. If more than one day is specified,
then the separator '-' must be used
between different days.example 1-
256 Id:0900d80580165955
start=00:00.end=12:00.weekdays=MO- E200613-01-114-V14.0I-23
TU-WEexample 2-
start=00:00.end=12:00.weekdays=SA

Number
14 Reference Counter Reference Counter for the current thresh- “-“
old. If no Reference Counter is to be defined
for this Threshold, then the character ‘-‘
should be present in this column. If the
Threshold is related to a Counter, then only
the name of a Counter of the same Mea-
surement can be specified. If the Threshold
is related to a Virtual Counter, then the Ref-
erence Counter String must be in the format
<Measurement>:<Counter Name> where
<Measurement> is the designation of any
Measurement from the current Threshold
Object Class, and <Counter Name> is a
designation of a Counter belonging to that
Measurement.
(0..1,a..z,A..Z,-,_)
15 RC Compare Value Reference Counter Compare Value for the –9999999,99
current threshold. If no Reference Counter
is to be defined for this Threshold, then the
value –9999999,99 should be present in this
column.
Allowable Values: Double (from –
9999999,99 to 9999999,99).
16 RC Cross Direction Reference Counter Cross Direction. If no “DOWN”
Reference Counter is to be defined for this
Threshold, then the value “DOWN” should
be present in this column.
Allowable Values: “UP”
“DOWN”
5.1.2 Thresholds Classes CSV Files

The Import/Export of Threshold Configuration Data is done using CSV files. This means
that a CSV file with a pre-defined format is used to store all the relevant information nec-
essary to define Thresholds.
The following figure is an example of a table of thresholds classes, exported to a CSV
file:
E200613-01-114-V14.0I-23 Id:0900d80580165955 257

Figure 155 Thresholds CSV file opened with MS Excel

Where:

Number
1 Object Class Name Name of the Object Class. Automatically defined by
SPOTS when exporting
CSV.
2 Threshold Class Name Name of the Threshold Class. Automatically defined by
Allowable Values: Alphanumeric Characters SPOTS when exporting
(0..1,a..z,A..Z,-,_) CSV.

3 Network Object Name of the Network Object that belongs Automatically defined by
within the Threshold Class. Must be a valid SPOTS when exporting
SPOTS Network Object name. CSV.
(0..1,a..z,A..Z,-,_)
Table 55 Field Descriptions of the Thresholds Classes CSV files
5.2 Appendix B - PMS Commands
5.2.1 adhoc2srl
Description
258 Id:0900d80580165955 E200613-01-114-V14.0I-23

This command enables you to generate SRL reports from existing AdHoc reports.
These SRL reports can then be customized to extend the basic functionality provided by
the AdHoc Reporting mechanism.
The output SRL report is stored directly in the user area inside the SPOTS File System.
Under the {spots_user_private_directory}/reports/source folder.
The command line tool has the ability to establish a session with the SPOTS Application
Server in order to perform essential operations needed for the conversion. In short,
these operations should include:
• Validate the SPOTS user.
• Obtain information about SPOTS counters in the metadata.
• Obtain information about virtual counters in the Virtual Entities database.
• Store the output SRL file directly in the user area, so you can see it next time it opens
the SRL Report Editor in the SPOTS GUI client.
g Adhoc2srl validates the user session and must use Private tasks. In the case that a
Public task is selected then an error occurs.
Syntax
adhoc2srl [-h]
or
adhoc2srl -fFilename
or
adhoc2srl -pOutPath -uUser -wPassword taskfilename.udr
where:
-uUser SPOTS User Name

-wPassword SPOTS User Password
-p Outpath Output path (see Information Note).
g •
•
The reportFile is always the last argument.
If the -f argument is declared the remaining arguments are ignored.
• The maximum length of a line in the input arguments file is 1024.
• The drive of the file path is the Spots Application Server's path.
• Example of one day interval (1/01/2000): 20000101000001 - 20000102000000.
• Predefined Time Periods are TODAY, YESTERDAY, LAST_WEEK or
LAST_MONTH
• By default, the output path is the Spots user's directory. If this parameter is specified,
it is concatenated to Spots user's directory.
• Variables types are: boolean, long, real, string, time.
• Report Origin can be: 'Siemens' for public reports provided by Nokia Siemens Net-
works, 'Custom' for public customized reports or 'Private' for user-defined reports.
5.2.2 ChangeObjNames
Description
Renames managed objects in SPOTS database. This command allows two different
kinds of renaming operations:
E200613-01-114-V14.0I-23 Id:0900d80580165955 259

• Change NE names for any type of NE.

• Rename GERAN managed objects that have no symbolic names, assigning them
symbolic names.
The renaming of GERAN managed objects into symbolic names is mandatory when a
BSC, previously managed via OMC-BBSSOMC-B, is upgraded and becomes managed
by RC.
g This command must be executed offline, that is, with SPOTS and all its services and
jobs stopped.
It is not possible to rename two different managed objects into a new single name, that
is, merging data from two different objects into a single new one.
Syntax
changeObjNames
Usage
1. Login as root user.
2. Stop all SPOTS services (SAS, SDS, SNS)
Verify that $SPOTS_DIR environment variable is correctly set.
3. Execute the command: 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 the corresponding number option.
The steps described below apply only if the SPOTS Database contains objects of
the selected "type”.
g If the selected option was to rename Mobile-Core or UTRAN object names, then
execute the next 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 Editor that is set in the environment variable EDITOR.
In the displayed Text Editor window, a line per NE with the following syntax is pre-
sented: <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’.
Example of the contents, displayed in the Text Editor window:
omc1@lisbon1 omc1@lisbon1
lisbon2 lisbon2
Rename the desired NE names editing the field ‘new_NE_name’, replacing it by the
“new” NE name. Note that all NE names must be unique network wide. Example of
the contents after modification:
omc1@lisbon1 lisbon1
lisbon2 lisbon2
260 Id:0900d80580165955 E200613-01-114-V14.0I-23

g Enter ‘return’ in the last line of the file. Otherwise, that line is not considered and
an error is 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 is displayed again. Select a
new option to rename objects or quit procedure.
g If the selected option was to rename GERAN object names, then execute the next
step.
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
therefore are 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
Editor that is set in the environment variable EDITOR.
In the displayed Text Editor window, a line per NE with the following syntax is pre-
sented: <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 be
replaced with the BSC Symbolic Name as configured in the RC.
omcb01_BLC01D omcb01_BLC01D
omcb01_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. Example of the contents after modification:
omcb01_BLC01D Lisbon_1
omcb01_BLC02D Lisbon_2
names are renamed in the SPOTS Database and the menu is displayed again.
Select a new option to rename objects or quit procedure.
9. Modify the SPOTS Ids for BTSMs, assigning symbolic Ids to the desired BTSMs. All
BTSMs contained in BSCs which received Symbolic names in the previous step
should now be given Symbolic Ids.
A list of BTSM object names existing in SPOTS database is displayed in a window,
using the Text 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 is presented: <current_BSC_name> <current_BTSM_id> <BTSM_symb_id>
where:
<current_BSC_name>: is the name of the BSC that contains the BTSM (BSC name
in use and saved in SPOTS database).
<current_BTSM_id>: is the BTSM identification in use and saved in SPOTS data-
base.
<BTSM_symb_id>: this field is initially set with ‘current_BTSM_id’ and must be
replaced with the BTSM Symbolic Id as configured in the RC.
E200613-01-114-V14.0I-23 Id:0900d80580165955 261

omcb01_BLC01D 20 20
omcb01_BLC02D 21 21
For each BTSM whose identification has to be changed, edit the field
‘BTSM_symb_id’ field, replacing it by the new symbolic identification. Example of the
contents after modification:
omcb01_BLC01D 20 Lapa
omcb01_BLC02D 21 Benfica
names are renamed in the SPOTS Database and the menu is displayed again.
Select a new option to rename objects or quit procedure.
10. Modify the SPOTS Ids for BTSs, assigning Symbolic Ids to the desired BTSs. All
BTSs contained in BSCs which received symbolic names in the previous step
should now be given Symbolic Ids.
A list of BTSM object names existing in SPOTS database is displayed in a window,
using the Text 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 is presented: <current_BSC_name> <current_BTSM_id> <current_BTS_id>
<BTS_symb_id> where:
<current_BSC_name>: is the name of the BSC that contains the BTSM (BSC name
in use and saved in SPOTS database).
<current_BTSM_id>: is the BTSM identification in use and saved in SPOTS data-
base.
<current_BTS_id>: is the BTS identification in use and saved in SPOTS database.
<BTS_symb_id>: this field is initially set with 'current_BTS_id' and must be replaced
with 'BTS_symb_id.
omcb01_BLC01D 20 0 0
For each BTS whose identification has to be changed, edit the field ‘BTS_symb_id’
field, replacing it by the new symbolic identification. Example of the contents after
modification:
5.2.3 Collector
For a detailed description of this command please refer to the TPs Customer Documen-
tation.
262 Id:0900d80580165955 E200613-01-114-V14.0I-23

5.2.4 dbaggregator
Description
Aggregates measurement records to a higher granularity.
Syntax
dbaggregator -h
or
dbaggregator [-s] [-d domain_id] [-g granularity_in] [-f
granularity_out] [-l {d | w | a} ] [-m {1 | 2 | 3} ] [-r]
where:
-h Provides detailed help

-s Silent mode
-d <domain_id> Specifies that data to aggregate refers to objects from domain
domain_id
This parameter is optional for single domain configurations.
When the -h parameter is used, depending on the detected
domain configuration, some extra information is presented
concerning the values to use in domain_id. An example is:
The available domains are:
/
/Transit (*)
/North (*)
/North/NorthWest
/North/NorthEast
(*) Domains directly associated with a database server

(primary domains).
The domain_id parameter identifies a network domain or a

primary domain.
The domain_id parameter cannot be a sub-domain.
When domain_id is a network domain, it is expanded to all
associated primary domains and the command is executed
for each existing database within the network.
See domains concept for details concerning the domains
classification.
-g <granularity_in> Specifies the granularity of the input records in seconds.
The possible values for granularity_in are 300, 900, 1800 and
3600, with 300 as default.
The granularity_in value must be smaller than granularity_out.
E200613-01-114-V14.0I-23 Id:0900d80580165955 263

-f <granularity_out> Specifies the granularity of the output records in seconds.

The possible values for granularity_out are 900, 1800, 3600
and 86400, with 900 as default.
The granularity_out value must be bigger than granularity_in.
-l Aggregates existing records for:
d: yesterday.
w: the last week.
a: all existing records, until and including yesterday (default).
-m Aggregates according to the following algorithm:
1: normal measurements.
2: 1st & Interval measurements.
3: method (2) after method (1) (default).
-r Deletes the input records after successful aggregation.
5.2.5 dbarchive
Description
Exports or imports data from/to SPOTS database.
Syntax
dbarchive -h
or
dbarchive -x [-a archive_dir] [-l [1 | 2]] [-o ne_type... [-n
ne_name...]] [-f gran] [-g] [-r] {-b ndays} | {begin_date
end_date}
or
dbarchive -i [-a archive_dir] [-d domain] [-u] [-c] [-o ne_type...
[-n ne_name...]] [begin_date end_date]
where

-x Exports data from the database
-a <archive_dir> Specifies that archive_dir is the directory to use to
read/write the archive files.
The default directory is $TMP/SdsExportFiles.
-l Only valid during export. Specifies which logs are archived:
1 - normal log
2 - history log
3- only network objects
Both logs are processed by default.
264 Id:0900d80580165955 E200613-01-114-V14.0I-23

-o <ne-type> Specifies a network element type.

Multiple NE types are specified using multiple '-o ne-type’
parameters.
-n <ne-name> Specifies a network element name.
Multiple NE's are specified using multiple ‘n ne-name’ param-
eters.
-f <gran> Only valid during export. Specifies the granularity of the normal
log data to be exported.
When omitted, all granularities are exported.
-g Only valid during export. Group the export files by network ele-
ments.
-r only valid during export. Removes all exported data.
-b <ndays> Only valid during export. Exports all available data until n days
days from today.
<begin_date> First day of log data to be imported/exported, in format
YYYY/MM/DD
<end_date> Last day of log data to be imported/exported, in format
YYYY/MM/DD
-i Imports data into the database
-d <domain_id> Only valid during import. Specifies that data to import refers to
objects from domain_id domain.
-u Only valid during import. If data to import already exists, it is
updated.
When this option is not used, data that already exists in the
database is discarded.
-c Creates all the managed objects from the import files, even
without attached log data
g The command must be run with the user SPOTS.
5.2.6 dbcalcstat
Description
Optimizes database access after importing traffic data.
Syntax
dbcalcstat -h
or
dbcalcstat { { -o | -d | -c } ... }
where:

-o Calculates statistics for the Managed Objects tables
E200613-01-114-V14.0I-23 Id:0900d80580165955 265

-d Calculates statistics for the Detailed Log tables

-c Calculates statistics for the Compressed Log table
5.2.7 dbhistoryadm
Description
Changes the aggregation flag of a measurement version. Setting or unsetting the aggre-
gation flag determines if history data is generated for the measurement.
Syntax
dbhistoryadm -h
or
dbhistoryadm -a | { { -s | -u | -d | -e | -n } meas_version } ... }
where:
-h Provides detailed help.

-a Displays the aggregation flag for all measurement versions.
-s meas_version Sets the aggregation flag for the measurement version speci-
fied by meas_version.
Multiple sets are specified using multiple '-s meas_version’
options.
-u meas_version Un-sets the aggregation flag for the measurement version
specified by meas_version.
Multiple sets are specified using multiple '-u meas_version’
options.
-d meas_version Displays the aggregation flag for the measurement version
specified by meas_version.
Multiple sets are specified using multiple '-d meas_version’
options.
-e meas_version Sets the extrapolation method flag of the following measure-
ment version.
Multiple sets are specified using multiple '-e meas_version'
options.
-n meas_version Unsets the extrapolation method flag of the following measure-
ment version.
Multiple commands are specified using multiple '-n
meas_version' options.
266 Id:0900d80580165955 E200613-01-114-V14.0I-23

5.2.8 dbinfo
Description
Calculates the amount of disk space occupied by the database.
Syntax
dbinfo -h
or
dbinfo -f filename
where:

-f <filename> Name of the output file.
The default file name is $TMP/DatabaseDiskInfo.txt
5.2.9 dbloader
Description
Loads SPF traffic data and configuration management data files into the SPOTS data-
base.
Syntax
dbloader -h
or
dbloader [-s] [-f { i | d }] [-e { i | d }] [-r] [-d domain_id]
SPF_filename(s)
where:

-s Silent mode
-f { i | d } Specifies the behavior with duplicated measurement records:
i - insert duplicated records;
d - discard duplicated records.
-e { i | d } Specifies the behavior with suspect measurement records:
i - insert suspect records;
d - discard suspect records.
-x { i | e} import/export Configuration Management Data.
i - import configuration management data from file.
e - export configuration management data to file.
-r Forces file deletion after successful import, if the file read only
flag is not set.
E200613-01-114-V14.0I-23 Id:0900d80580165955 267

-d <domain_id> Specifies that data to import refers to objects from domain

domain_id.
domain configuration extra information is presented concern-
ing the values to use in domain_id. An example is:
/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, the
newly created nodes are assigned to domain_id.
See domains concept for details concerning the domains clas-
sification.
SPF_filename(s) List of SPF traffic files, separated by spaces, each file identified
by its full pathname or remote share name using Universal
Naming Convention (UNC). The remote share security
checking must be disabled. The use of wilcards is possible.
g There are restrictions when naming the objects. See TPs Customer Documentation for
details.
5.2.10 dbloadgaps
Description
Finds gaps in the load process of normal traffic data.
Syntax
dbloadgaps -h
or
dbloadgaps [-f configuration_file]
where:

-f <configuration_file> Specifies the fully qualified file name of the configuration
file to use.
The default value is $SPOTS_DIR/dbloadgaps.cfg, where
$SPOTS_DIR is the target directory where SPOTS-PMS
was installed.
The supplied dbloadgaps.cfg has the following contents:
268 Id:0900d80580165955 E200613-01-114-V14.0I-23

# DbLoadGaps Configuration File

#
# Description:
#
# measurementName_=NAME the name of a measurement to look for
loading gaps.
# measurementGranularity_=X the granularity of the data.
# Default value is 900 (X=900).
# collectionPeriod_=Y the number of seconds, counting
from current time, to inspect.
# Default value is measurementGranularity_ (Y=X).
#
# Multiple combinations of the previous three parameters can co-
exist, distinguishable via the 
# variable, starting at 1, with increments of 1 till the number
of measurements to inspect.
# When the variable is set to 0, the value assigned to that
parameter will overlap all subsequent
# definitions of similar parameters.
# When none of the above parameters is specified, the inspection
is performed for all existing
# measurements, assuming the default values for
measurementGranularity and collectionPeriod.
#
# dataWindow=N specifies the number of minutes (N) to inspect,
starting from execution
# moment (date&time) and moving backwards.
# Default value is 1 day (N=1440 minutes).
# outputDirectory=C: specified an existing directory where the
result file shall be created.
# Default value is the temporary directory (C:\TEMP for Windows
# and /tmp for Solaris)
# outputFileName=dataload the name of the output file.
# The execution date&time stamp is appended to the specified file
name,
# together with the extension ".txt".
# Default value is "dbloadgaps".
# historic Specifies if the inspection should be performed on the
detailed or historical records.
# Default value is false.
# verbose Specifies if a detailed or compact output should be
provided.
# Default value is both.
#
# Example:
#
# measurementName_1=TGRP
# measurementGranularity_1=900
# collectionPeriod_1=3600
# measurementName_2=CP
# collectionPeriod_2=3600
E200613-01-114-V14.0I-23 Id:0900d80580165955 269

# DataWindow=1440
# OutputDirectory=C:
# OutputFileName=LoadGaps
# historic=true
# verbose=both
g For a given data window, dbloadgaps only provides a correct output whenever the
data of the measurements belongs to the same version of the desired NE. If different or
upgraded versions of the NE are used, the output is not correct.
5.2.11 dbobjectpurge
Description
Removes unlogged managed objects from SPOTS database. The removed object keys
are written in the SDS log.
Syntax
dbobjectpurge -h
or
dbobjectpurge { -a | { { -o oc_name } ... } } [-s]
where:

-a Looks for all object classes.
-o <oc_name> Specifies a object class name.
Multiple object classes are specified using multiple '-n
oc_name’ options.
-s Simulates the operation. Only a check is performed without
object removal.
5.2.12 dbreadstat
Description
Reads the values of dynamic statistics from ORACLE.
Syntax
dbreadstat -h
or
dbreadstat [-d start_date] [-t start_time] [-l duration] [-f
conf_file]
where:
-h provides detailed help
270 Id:0900d80580165955 E200613-01-114-V14.0I-23

-d <start_date> Specifies the date to start the statistics monitor.

The start_date format is YYYY/MM/DD
The default value is today's date.
-t <start_time> Specifies the time to start the statistics monitor.
The start_time format is HH24:MI:SS
The default value is current time.
-l <duration> Specifies the duration of the process in seconds.
The default value is 3600,that is, one hour.
-f <conf_file> Specifies the name of the configuration file conf_file.
The default filename is $SPOTS-DIR/DatabaseStatistics.cfg,
where $SPOTS_DIR is the target directory where SPOTS-
PMS was installed.
5.2.13 dbremover
Description
Removes logged data from the SPOTS database.
Syntax
dbremover -h
or
dbremover [-d domain_id] [-l { 1 | 2 | 3 | 4 | 5 } ] [ {-o
ne_type}... [ {-n ne_name}...][ {-m measurement}...]] days |
{begin_date end_date}
where:
E200613-01-114-V14.0I-23 Id:0900d80580165955 271

-d <domain_id> Specifies that the logged data to remove refers to objects from
domain domain_id.
If network elements are specified, using -o and -n parameters
described below, the specified domain must be directly associ-
ated with a database server.
ing the values to use in domain_id. An example is:
/
/Transit (*)
/North (*)
/North/NorthWest
/North/NorthEast

(primary domains).
primary domain.
The domain_id cannot be a sub-domain.
associated primary domains and the command is executed for
each existing database within the network.
sification.
-l Specifies the logs to use:
1: use the normal log (default)
2: use the 1st and interval log
3: use the normal log and then the 1st and interval log
4: use the alarm log
5: use history log.
-o <ne-type> Specifies a network element type.
Multiple NE types are specified using multiple '-o ne-type’
parameters.
-n <ne-name> Specifies a network element name.
Multiple NEs are specified using multiple ‘n ne-name’ param-
eters.
-m <measurement> Specifies a measurement.
Multiple measurements are specified using multiple ‘-m
measurement’ parameters.
272 Id:0900d80580165955 E200613-01-114-V14.0I-23

<days> Number of days of log data to preserve, starting on current date

and counting 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
5.2.14 deletealarms
Description
Purges alarms from the known alarms storage subsystems.
Syntax
deletealarms -h
or
deletealarms [-s ] [-c "command"]
where:

-s Silent mode
E200613-01-114-V14.0I-23 Id:0900d80580165955 273

-c <commands> Specifies an expression to be used in the selection of alarms

to delete.
The deletealarms expressions EBNF grammatic is:
<expression> ::= <operand> <other_operands>
<other_operands> ::= + <operand>
<other_operands>
| - <operand> <other_operands>
| * <operand> <other_operands>
| / <operand> <other_operands>
| < <operand> <other_operands>
| > <operand> <other_operands>
| <= <operand> <other_operands>
| >= <operand> <other_operands>
| != <operand> <other_operands>
| AND <operand> <other_operands>
| OR <operand> <other_operands>
| <void>
<operand> ::= <expression>
| <field_name>
| <constant>
| <string>
| <function>
<field_name> ::= IsPending
| EventType
| ObjectClass
| ObjectInstance
| EventTime
| PerceivedSeverity
| CrossDirection
| ProbableCause
| SpecificProblems
| TriggeredThreshold
| ThresholdValue
| ThresholdName
| ThresholdExpression
| ThresholdGranularity
| ClearValue
| AdditionalInformation
| ReportLink
| ObservedValue
| ClearTime
| AlarmType
| ClearObservedValue
| LoggingTime
274 Id:0900d80580165955 E200613-01-114-V14.0I-23

-c <command> <constant> ::= -5 | ... | -5.7 | ... | 4 | ...

| 78.98 | ... | +127.01 | ... | +76 | ...
<string> ::= 'String content'
<function> ::= DateTime(<year>, <month>,
<day>, <hours>, <minutes>, <seconds>)
| NOT(<operand>)
<year> ::= 1970 | ... | 2003 | ...
<month> ::= 1 | ... | 12
<day> ::= 1 | ... | 31
<hours> ::= 0 | ... | 23
<minutes> ::= 0 | ... | 59
<seconds> ::= 0 | ... | 59
<void> ::=
5.2.15 extfieldinstall
Description
Allows the creation or listing of the Extended Fields by Object Class.
Syntax
extfieldinstall -h
or
extfieldinstall -x [-f filename] [-a | -o oc_name ...] [-r]
or
extfieldinstall -i [-f filename] [-u]
where:

-x Exports data from the database.
-f The configuration file to be used with its full path name.
-a Looks for all object classes.
-o <oc_name> Specifies a object class name. Multiple object classes are
specified using multiple '-o oc_name' options.
-r Removes User exported data. The System Extended Fields
can not be removed with this command.
-i Imports data to the database.
-u Updates database if the data to import already exists.
E200613-01-114-V14.0I-23 Id:0900d80580165955 275

5.2.16 initspots
Description
Starts/Stops the SPOTS processes.
Syntax
Three types of commands are available:
/etc/init.d/initSpotsPMS start|stop
/etc/init.d/initSpotsLT start|stop
/etc/init.d/initSpotsRT start|stop
initSpotsPMS Starts/Stops SPOTS Online Monitoring + Trend Analysis pro-

cesses
initSpotsLT Starts/Stops SPOTS Trend Analysis processes (SAS, SDS,
SNS)
initSpotsRT Starts/Stops SPOTS Online Monitoring processes
5.2.17 loader
For a detailed description of this command please refer to the TPs Customer Documen-
tation.
5.2.18 mergeobjects
Description
Copies SPOTS data, belonging to an object and its descendents, and imports its perfor-
mance data to the database using a different key. Allows adding SPOTS data from one
object to another, or to add a new SPOTS object whose data is a copy of an existing one.
The MergeObjects command is divided in three steps:
1. Export the data to be merged from SPOTS database using the dbarchive
command. Only the selected data is exported.
2. Create new dbarchive files with the lines to be merged, according to the Object
Map File. The new dbarchive files contains only the necessary lines to perform the
merge.
3. Import the new dbarchive files into the database using dbarchive.
The complete process executes all three steps. It is possible to run each step at a time,
by using the appropriate parameter.
Syntax
The MergeObjects is implemented in perl. To execute it, use the perl compiler as
follows:
perl mergeObjects.pl -h
or
perl mergeObjects.pl -o <filename> -d <dir_name> [-u] [-p
X[M[I]]]
where:
276 Id:0900d80580165955 E200613-01-114-V14.0I-23


-o <file_name> Name of the file containing the map of the objects to merge.
You must indicate the objects to merge and how, by providing
an object map file. The file must contain one or more lines,
where each line represents an object to merge. Each line
contains three mandatory fields, separated by the character “|”.
Example:
< object class>|<source object key>|<target object key>
The default file name is objKeyMap.dat. The file must be

located on the current directory.
-d <dir_name> Directory where to export archive logs. The amount of data to
export depends on the objects to merge. It can occur that all of
the database must be exported, so it is important to redirect the
exported data to a directory with enough space. The default
directory is called <archiveData> with location on the current
directory.
-u Indicates whether to update (if the –u option is not set) or not
(if the option –u is set) the data on the database with the new
data when importing.
-p XMI Steps to be executed (all by default)
X: export the log data
M: filter/process the log data for the merge
I: import the merged log data
Use the combination of the above letters to indicate which step
should be executed during the MergeObjects command.
g Each step must be executed together with the previous ones at least once, using the
same values for the –o and –d parameters. The merge configuration lines on the Object
Map file are all executed on the same source data. One line can not assume as input
the result of a merge from a previous line.
5.2.19 metadump
Description
Displays the local SPOTS Application Server metadata.
Syntax
metadump -h
or
metadump {[-a] | [-p] | [-c [class]] | [-t] | [-m [measurement]]}
[package]
where:
E200613-01-114-V14.0I-23 Id:0900d80580165955 277


-a Dumps everything: packages, classes, containment tree, mea-
surements and counters.
-p Dumps all the packages descriptions
-c <class> Dumps all the object class descriptions, or only the specified
ones.
The 'class' can contain wildcards or can be "all".
-t Dumps the containment tree.
-m <measurement> Dumps all the measurement's descriptions, or only the speci-
fied ones.
The 'measurement' can contain wildcards or can be "all".
A measurement description contains all the counter's descrip-
tions.
<package> Dumps only the metadata entities associated with the specified
packages.
The 'package' can contain wildcards.
All packages are selected if 'package' is not specified.
5.2.20 mkhistory
Description
Aggregates measurement records into the history log.
Syntax
mkhistory -h
or
mkhistory [-d domain_id] [-g granularity] [-r] [-l { d | w | a }
] | {begin_date end_date}
where:
278 Id:0900d80580165955 E200613-01-114-V14.0I-23

-d <domain_id> Specifies that data to aggregate refers to objects from domain.

ing the values to use in domain_id.
/
/Transit (*)
/North (*)
/North/NorthWest
/North/NorthEast

(primary domains).
primary domain.
The domain_id cannot be a sub-domain.
associated primary domains and the command is executed for
each existing database within the network.
sification.
-g <granularity> Specifies the granularity of the input records in seconds.
The possible values are 900, 1800, 3600 and 86400 with 900
as default.
-r Removes input records after successful aggregation.
-l Aggregate data for:
d - yesterday
w - the last week
a - all existing data, until and including yesterday (default)
The use of this option is mutually exclusive with begin_date
and end_date.
<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 parame-
ter.
<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 param-
eter.
E200613-01-114-V14.0I-23 Id:0900d80580165955 279

g The date interval can be defined by the -l parameter or with specification of a

begin_date and an end_date. The -I a parameter behavior on the very first execution
of the mkhistory command is slightly different than specified. It creates a time stamp
on the database, corresponding to its first execution. In this case, all traffic data imported
into the database since 0:00 of the previous day are aggregated. If the existing data was
imported two or more days ago, the used parameter should not be '-I' but rather a date
interval.
5.2.21 reporter
Description
It is SPOTS Client reporting facility, which can be invoked either by you on the server
system or by a scheduled task.
Syntax
reporter [-h]
or
reporter -fFilename
or
reporter -oObjects -tbBeginDate -teEndDate -tpPeriod -
aOutputFileFormat -dlines -dobjects -pOutPath -uUser -wPassword
-rReportOrigin -vVariables reportFile
For example:
reporter -u username -w xxxxx -d byyyymmddhhmmss -d
eyyyymmddhhmmss -o /@NE -r Siemens
/reports/bin/BssOverviewReport_tevl.si
For example:
# IN example
file[Username]bruno[Password]siemens[PeriodBegin]20061021000000
[PeriodEnd]20061022000000[Objects]/@NE_4_br80
[OutputFileFormat]CSV[ReportOrigin]Siemens
[ReportFileName]/reports/bin/BssOverviewReport_tevl.si #End In
file
g The -u <username> and -w <password> parameters are mandatory for the exe-
cution of the reporter command.
Where:

-u <username> Specifies the spots user name.
-w <password> Specifies the password for the user.
-r <ReportOrigin> Origin of the report (see Notes).
-f <Filename> Reads the arguments from a file.
280 Id:0900d80580165955 E200613-01-114-V14.0I-23

-o <Objects> Objects to apply to the report. This argument (-o) also accepts
the options:SOD!<name> for a Distinct Set of Objects and
SOA!<name> for an Aggregated Set of Objects. Note that
<name> stands for the name of the Set of Objects.
-t b<BeginDate> Begin time of the report (YYYYMMDDHHMMSS format).
-t e<EndDate> End time of the report (YYYYMMDDHHMMSS format).
-t Report predefined period (see Notes).
p<PredefinedPeriod>
-a CSV for a CSV file, HTML for a HTML file. Default is HTML.
<OutputFileForma
t>
-d <lines> While outputting to a CSV file do not write lines with all
counters equal to NO_DATA.
-d <objects> While outputting to a CSV file do not write objects with all
counters in all time intervals equal to NO_DATA.
-p <OutPath> output path (see Notes).
-v $Variable definition.
$VAR=<value,type
>
-m The object output format can be changed in three different
<ObjectLabelForm ways:
at>
• Using the -m 0/1/2 parameter in the reporter command
line to change object label format to MOI (2), User Label (1)
or both (0) (for example: reporter -m 1 -f ./public/
web/BssCallSetup_daily.par -a CSV instructs the
reporter to display just the user label as object label format)
• Adding the line ObjectLabelFormat=0/1/2 in sas.cfg,
where 0/1/2 has the same meaning as in the last para-
graph
• Adding the line [ObjectLabelFormat] 0/1/2 in the
".par" file, where 0/1/2 has the same meaning as in the
last paragraph
File of Arguments Description:
The arguments input file is a set of sections (arguments) and its values. The format is
similar to an 'ini' file and the possible sections are:
[Username] Spots Username
[Password] Password for user
[ReportOrigin] Origin of the report (see Notes).
[Objects] Each line has one object or many separated by ';'
[OutputFileFormat] Type of the output file. Can be CSV or HTML. Default is HTML
[BehaviourWithNoData] Behavior with NO_DATA lines/objects. Can be RemoveNo-
DataLines or RemoveNoDataObjects. By default empty lines and empty objects is
written:
[OutputPath] output path (see Notes).
E200613-01-114-V14.0I-23 Id:0900d80580165955 281

[PeriodBegin] Time in the following format: 'YYYYMMDDHHMMSS'

[PeriodEnd] Time in the following format: 'YYYYMMDDHHMMSS'
[Period] Report predefined period (see Notes)
[ReportFileName] Source of the report to execute (full path)
[Variables] Variables, each line: $VARNAME=value,type.
Lines that begin with '#' are considered comments.
-SOD!<name> -Set of Objects Distinct
-SOA!<name> -Set of Objects Aggregate
g The reportFile is always the last argument (if -f is not defined). If the -f argument is
declared the remaining arguments are ignored. The maximum length of a line in the
input arguments file is 1024. The drive of the file path is the Spots Application Server's
path. Example of one day interval (1/01/2000): 20000101000001 - 20000102000000.
Predefined Time Periods are TODAY, YESTERDAY, LAST_WEEK or LAST_MONTH.
By default, the output path is the Spots user's directory. If this parameter is specified, it
is concatenated to Spots user's directory. Variables types are: boolean, long, real,
string, time. Report Origin can be: 'Siemens' for public reports provided by Nokia
Siemens Networks, 'Custom' for public customized reports or 'Private' for user-defined
reports.
5.2.22 setdbpwd
Description
This command updates the Oracle user and password for all SPOTS Database Ser-
vices' connections.
To successfully update the Oracle password the following rules must be taken in con-
sideration:
• The first character must be a letter.
• Only letters, numbers and the symbols _ , $ and # are allowed.
• Oracle passwords are not case sensitive.
Syntax
setdbpwd -h
or
setdbpwd -u user_name [-c]
where:

-u user_name Oracle user name
-c Change Oracle user's password on the database
282 Id:0900d80580165955 E200613-01-114-V14.0I-23

5.2.23 spotslicense
Description
Provides information concerning current SPOTS license. Optionally removes the
existing SPOTS license from the system.
Syntax
spotslicense [ -H ]
or
spotslicense [-h] [-g] [-l | -i | -r | -w] [-f licenses_file |
{LICENSE, ...}]
where:
-h provides detailed help.

-g dumps reference code.
-l dumps the installed licenses.
-i installs new license(s).
-r removes installed license(s).
-w dumps warning(s).
-f specifies the file that contains the license keys to install, if used
with option -i, or the license identifiers if used with option -r.
LICENSE specifies a license key, if used with option -i, or a license iden-
tifier if used with option -r.
5.2.24 spotsping
Description
Informs if the specified SPOTS Server component is running on a certain system.
Optionally the TCP/IP port number may be specified.
Syntax
spotsping -h
or
spotsping server_type server_address [ port ] [loop]
where:

<server_type> Specifies the SPOTS Server component to check. The
possible values are:
AS - for the SPOTS Application Server component
DS - for the SPOTS Database Server component;
NS - for the SPOTS Naming Server component.
E200613-01-114-V14.0I-23 Id:0900d80580165955 283

<server_address> Identifies the system where the SPOTS Server component is

installed.
Two methods are possible:
- TCP/IP address, like 191.231.79.52
- Fully qualified domain name, like spots.nsn.com.
<port> The TCP/IP port number assigned to the SPOTS Server com-
ponent.
When this parameter is not specified, the default value is con-
sidered.
The default values are:
19980 - for SPOTS Naming Server component
19981 - for SPOTS Application Server component
19982 - for SPOTS Database Server component
loop pings the server in 500ms intervals until the command is
stopped by typing ^C.
5.2.25 spotsshutdown
Description
Issues a shutdown request to the local SPOTS Application Services.
Optionally a shutdown is also requested to all SPOTS Database Servers of that cluster.
Syntax
spotsshutdown -h
or
spotsshutdown [-s] [-d]|[-r]|[-p]
where:
-h Displays detailed help.

-s Silent mode.
-d Specifies that a shutdown request is also issued to all con-
nected database servers that belong to this cluster.
-r Reboots the application server.
The server is unavailable for 15 seconds.
-p Specifies that a reboot request is also issued to all connected
database servers that belong to this cluster.
The servers are unavailable for 15 seconds.
5.2.26 SQL Interface

In SPOTS the description of the SQL-based external interface is obtained by running a
SPOTS command (CLI) which provides a description, in HTM format, of the columns
included in the views provided for an external access to the database.
284 Id:0900d80580165955 E200613-01-114-V14.0I-23

Description
This command generates the description of the available Database views. Every time a
new TP is installed or updated in the system in terms of metadata (SDS_TPinstaller),
the command must be run to update the views description so that it becomes consistent
with the newly updated views.
Syntax
Runvg
or
Runvg -h
where:
-h Prints the help of View Generator.
5.2.27 dbstart
Description
Starts 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).
Syntax
dbstart
5.2.28 dbshut
Description
Stops 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).
Syntax
dbshut
5.3 Appendix C - PMC Commands
5.3.1 reportscompiler
Description
The ReportsCompiler tool compiles a SPOTS Report Processing language source file
and generates a file of intermediate code for the Spots Report Processing Interpreter
Syntax
ReportsCompiler [-help]
or
E200613-01-114-V14.0I-23 Id:0900d80580165955 285

ReportsCompiler [-hH_FileName] [-tT_FileName] [-oO_FileName] [-

w{yes|no}] [-v{yes|no}] input_file
where:
-help Provides detailed help.

-hH_<FileName> Forces creation of a header file from a library source file whose
name follows the -h characters.
The library source file should have extension .sh.
-tT_<FileName> Forces creation of a trace information file whose name follows
the -t characters.
-oO_<FileName> Characters following -o specify the output file (in executable
directory by default).
-w{yes|no} Enables/disables warnings presentation. The selected option
can be yes or no and follows characters -w.The default value
is yes.
-v{yes|no} Enables/disables generation of a $variable file. The selected
option can be yes or no and follows characters -v.The default
value is no.
<input_file> Name of the input file, with extension .sc.
g The option's filenames do not have extensions, except the 'header' file
5.3.2 spotsreportcommand
Description
Executes a report outside SPOTS client.
Syntax
Several syntax are possible, depending on the report to execute and also on the method
used to pass the required parameters.The date interval and the objects to consider are
mandatory, together with the Application Server (TCP/IP address and port) who should
process the report and the username/password of the person responsible for the exe-
cution.The specification of objects can be made via the sets of objects concept, which
avoids having to specify object by object. For ad-hoc reports, it is also necessary to
specify the counters to present, with/without virtual counters, either individually or using
the sets of counters concept. All other parameters have default values.To execute a
Nokia Siemens Networks report or a custom report, only the report name is required
beyond the mandatory parameters, except for private custom reports, where the i
parameter should be set to false. All other parameters assume default values.The
SpotsReportCommand command has a configuration file, named configuration.proper-
ties and located in %SPOTS_CL_DIR%, where several parameters may be modified by
the end-user. All directories are specified relative to the %SPOTS_CL_DIR% directory,
so, for instance, when .\\Examples\\ is specified, it refers to %SPOTS_CL_DIR%\Exam-
ples. Do not remove ".\\" from the beginning of the directory name and "\\" from its end,
as these strings are used to obtain the full pathname to the files.
The various methods to specify the required report parameters are:
Via an UDR file (XML parameters file generated by SPOTS client)
286 Id:0900d80580165955 E200613-01-114-V14.0I-23

SpotsReportCommand -fx XMLParamFile [{ - <parameter>

<parameter_value>} ... ]
Specifying each required or optional parameter individually
SpotsReportCommand [ { - <parameter> <parameter_value>} ... ]
All parameters are separated through spaces.
where:
Command line XML/Properties Description

parameter file parameter
For a single command line parameter, with all other parameters specified in a UDR file except TCP/IP address,
TCP/IP port, user, password.
fx Not applicable Identifies the XML file name. You can use only the file name, as the
directory where the file is located can be defined in file configura-
tion.properties, in the XML_DIRECTORY parameter, where the entire
path can be specified; or the WORKING_DIRECTORY parameter.
s Not available TCP/IP address or fully qualified domain name of the SPOTS Naming
Server that processes the report.
p Not available TCP/IP port number of the SPOTS Naming Server that processes the
report.
u User User who executes the report.
Corresponds to the user who logs into SPOTS Client.
k Password Password of the user who executes the report.
Corresponds to the password used when you logged into SPOTS
Client.
usl Use Stored Login Stores in system preferences the last user and password. The avail-
able values are true or false, not case sensitive. Default value is true.
For Ad-Hoc Reports
t ReportType Type of report. It can be chart or table. It is not case sensitive. The
default is table.
s Not available TCP/IP address or fully qualified domain name of the SPOTS Applica-
tion Server that processes the report.
p Not available TCP/IP port number of the SPOTS Application Server that processes
the report.
u User User who executes the report.
Corresponds to the user who logs into SPOTS Client.
k Password Password of the user who executes the report.
Corresponds to the password used when you logged into SPOTS
Client.
ra ReportTitle Report title/window report name. The default value is the default report
name (see fon command line parameter).
Table 56 SPOTS Reports commands
E200613-01-114-V14.0I-23 Id:0900d80580165955 287


d DataType Identifies the type of the Data Source: Detailed, historical or SPBH. The
available values are DETAILED, TOTALS and SPBH. It is not case
sensitive. The default value is DETAILED.
pe Period Specifies the date or date&time interval to consider in the report. When
specifying the date interval, it is possible to use keywords. The date
interval format is date_begin:date_end.
Ex: 20011201:20011207.
The date&time format is date&time_begin:date&time_end.
Ex: 20011201000001:20011207235959.
The available keywords are Today, Yesterday and LastWeek, not case
sensitive.
o ManagedObjectID List of object instances to include in the report. The syntax is:
domain1#obj1,obj2,obj3;domain2#obj4,obj5.
so SetOfObjects Alternate method to specify the objects to include in the report (see o
command line parameter)
c Counters List of counters to include in the report, separated by commas (","). The
syntax is:
Meas01:Counter1,Counter2;Meas02:Counter3
vc VirtualCounters Alternate method to specify the counters to include in the report (see c
sc SetOfCounters Alternate method to specify the counters to include in the report (see c
g Grouping Specifies whether grouping is required in the report presentation. The
available values are none, object and variable, and are case sensitive.
If available value is object or variable, the maximum of objects per
window and precedence can be configured. The syntax is:
grouping_value;objects#max,pred;variables#maxmax,pred
The default value is none.
granularity Granularity Required input granularity. The available values are DAILY,
HOUR_QUARTERLY and IMPLICIT_GRANULARITY, not case sensi-
tive. The default value is HOUR_QUARTERLY.
ot OutputType Type of output produced. The available values are s for screen, f for file
and p for printer or combinations of these three values, like sf for screen
and file. It is case sensitive. OutputType is set to screen by default.
fon FileOutputName File output name. The default name is RP#begin_date#end_date, like
RP#20011201#20011207.
Table 56 SPOTS Reports commands (Cont.)
288 Id:0900d80580165955 E200613-01-114-V14.0I-23


fop FileOutputPath Full path name of the directory where the output file should be placed.
The default path is specified by the FILE_OUTPUT_PATH parameter in
configuration.properties file.
If the FILE_OUTPUT_PATH parameter in configuration.properties does
not exists the default is the working directory
fot FileOutputType Specifies the format of the output file. The available values are xml,
html and pdf, not case sensitive.
The default output type is specified by the FILE_OUTPUT_TYPE
parameter in configuration.properties file.
If the FILE_OUTPUT_TYPE parameter in configuration.properties does
not exist the default is html.
printer Printer Printer address.
The default value is specified in configuration.properties file, by the
PRINTER parameter.
If the value is not specified in configuration.properties file, the default
value is the default local printer.
r Refresh Specifies if the report is refreshable. The available values are true or
false, not case sensitive.
idt InstanceDisplay- Specifies the instance display identification type. The available values
Type are USER_LABEL, SIEMENS_LABEL, BOTH_LABELS. It is not case
sensitive. Default value is SIEMENS_LABEL.
For all pre-defined reports (Nokia Siemens Networks and Custom public/private)
t ReportType Type of report. It can be chart or table. It is not case sensitive. The
default is table.
s Not available TCP/IP address or fully qualified domain name of the SPOTS Applica-
tion Server that processes the report.
p Not available TCP/IP port number of the SPOTS Application Server that processes
the report.
u User User who executes the report. Corresponds to the user who logs into
SPOTS Client.
k Password Password of the user who executes the report. Corresponds to the
password used when you logged into SPOTS Client.
rp PredefReport- Pre-defined report name.
Name
ra ReportTitle Report title/window report name. The default value is the default report
name (see fon command line parameter).
E200613-01-114-V14.0I-23 Id:0900d80580165955 289


i IsPublic Specifies if the report is a Public Custom report. The available values
are true and false, not case sensitive. The default value is true.
pe Period Specifies the date or date&time interval to consider in the report. When
specifying the date interval, it is possible to use keywords. The date
interval format is date_begin:date_end.
Ex: 20011201:20011207.
The available keywords are Today, Yesterday and LastWeek, not case
sensitive. The date&time format is date&time_begin:date&time_end.
Ex: 20011201000001:20011207235959.
o ManagedObjectID List of object instances to include in the report. The syntax is:
domain1#obj1,obj2,obj3;domain2#obj4,obj5.
so SetOfObjects Alternate method to specify the objects to include in the report (see o
command line parameter).
ep ExtraParameters Assign the values to the extra parameters of the selected report. If two
parameters corresponding to two counters, and corresponding values,
have to be passed then we should have:
"-ep Counter1,Value1;Counter2,Value2".
g Grouping Specifies whether grouping is required in the report presentation. The
available values are none, object and variable, and are case sensitive.
The default value is none.
ot OutputType Type of output produced. The available values are s for screen, f for file
and p for printer or combinations of these three values, like sf for screen
and file. It is case sensitive. OutputType is set to screen by default.
fon FileOutputName File output name. The default name is RP#begin_date#end_date, like
RP#20011201#20011207.
fop FileOutputPath Full path name of the directory where the output file is placed.
The default path is specified by the FILE_OUTPUT_PATH parameter in
configuration.properties file.
If the FILE_OUTPUT_PATH parameter in configuration.properties file
does not exist, the default is the working directory.
fot FileOutputType Specifies the format of the output file. The available values are xml,
html and pdf, not case sensitive.
The default output type is specified by the FILE_OUTPUT_TYPE
parameter in configuration.properties file.
If the FILE_OUTPUT_TYPE parameter in configuration.properties does
not exist the default is html.
290 Id:0900d80580165955 E200613-01-114-V14.0I-23


printer Printer Printer address.
The default value is specified in the configuration.properties file, by the
PRINTER parameter.
If the value is not specified in the configuration.properties file, the
default value is the default local printer.
r Refresh Refresh configuration. Specifies if the report is refreshable. The syntax
is:
enable;interval;startDelay
"enable" is true or false, "interval" is a keyword and "startDelay" is a
number. The keywords available are:REFRESH_IMPLICIT,
REFRESH_1_MIN, REFRESH_5_MIN, REFRESH_15_MIN,
REFRESH_30_MIN, not case sensitive.
idt InstanceDisplay- Specifies the instance display identification type. The available values
Type are USER_LABEL, SIEMENS_LABEL, BOTH_LABELS. It is not case
sensitive. Default value is SIEMENS_LABEL.
Command Line Examples

Ad-Hoc Reports examples:
-s 141.29.135.22 -p 19980 -u __root__ -k qwerty -pe
20050601:20050720 -o /#T58 -g variable -c
SEMSU:MSUTRO;SEMSU:MSUORO;SEMSU:NEISLDUR -granularity
FIVE_MINUTES -d DETAILED -r false -ot f -t table -ra "report
title é este" -fon nomeFile
(Item Refresh)
20050725:20050725 -o /#T58:31; T69:31 -c
ATMIFTR:CERX;ATMIFTR:CETX;ATMIFTR:LOAD;ATMIFTR:LOADRX;ATMIFTR:L
OADTX;ATMIFTR:PCR -r true
20050725:20050725 -o /#T58:31;T69:31 -c
OADTX;ATMIFTR:PCR -r false -ot sf
(No data)
20050725:20050725 -o /#T58 -c SCCPQOSNET:CRMSGRCV
-s 141.29.135.22 -p 19980 -u __root__ -k qwerty -pe lastmonth -
o /#T58:31;T69:31 -c
OADTX;ATMIFTR:PCR -g variable;objects#1,true;variables#2,false
E200613-01-114-V14.0I-23 Id:0900d80580165955 291


20050725:20050725 -o /#T58:31;T69:31 -c
OADTX;ATMIFTR:PCR -fon outputName%d-hora-%t -ot fs -g object
-s 141.29.135.28 -p 19980 -pe 20061101:20061106 -o NE_1_po50
-u __root__ -k qwerty -c SYSLMP:CALLPLOAD -idt user_label
-s 141.29.135.28 -p 19980 -pe 20061101:20061106 -o NE_1_po50
-u __root__ -k qwerty -c SYSLMP:CALLPLOAD -idt siemens_label
-s 141.29.135.28 -p 19980 -pe 20061101:20061106 -o NE_1_po50
-u __root__ -k qwerty -c SYSLMP:CALLPLOAD -idt both_labels
Pre-defined Report examples:
-s 141.29.135.22 -p 19980 -u __root__ -k qwerty -rp "ATM
Interface Load - Top 10 SPBH" -pe 20040707:20050722 -o /#T58;T69
XML file example:
-s 141.29.135.22 -p 19980 -u __root__ -k qwerty -fx
new_adhoc_test.udr
5.4 Appendix D - Report Outputs

The following table displays the different outputs that are available for each type of
report run:
GUI spotsreportcommand reporter Scheduler SPOTS Online

Output Type
Printer Y Y N Y N
Screen desktop window Y Y N N Y
File Y Y Y Y N
Excel with templates Y N N N N
Excel without templates Y N N Y N
PDF Y Y N Y N
XML Y Y Y Y N
HMTL Y Y Y Y N
CSV Y N Y Y N
Report Types
Ad-hoc Y Y N Y N
Predefined reports Y Y Y Y N
Ad-Hoc Online Reports Y N N N Y
Table 57 Report Output table
292 Id:0900d80580165955 E200613-01-114-V14.0I-23

5.5 Appendix E - Refreshable Reports
5.5.1 Restrictions to Refreshable Reports

Due to performance and consistency issues, there are two main restrictions applicable
to Refreshable ADHOC Reports.
• Past intervals relative to the last refreshed interval are not processed.
• The first refreshable interval must be within 6 time periods after the execution of the
report.
By default, the number of acceptable back periods relative to the report execution time
is 6. This means that report for 15 minutes detailed data, that starts executing at 10:00h
(Server Time), accepts the first refresh interval if the data timestamp is not inferior to
8:30h.
This timeframe can be configured in the sas.cfg using the parameter
PdgEventAcceptedGranularityDelay = x (default 6 periods)
Reports executing in refresh mode only show the data available at a given moment.
5.5.2 Refreshable Reports for Aggregated SoOs

Refreshing Aggregated SoOs reliably and consistently can only be done if an important
precondition is met: Data Collection must be working smoothly and timely.
The AppServer cannot wait forever for all data associated to a given SoO to be avail-
able. Due to many reasons, that might not always be possible. For instance:
• Data collection for some NEs of the SoO may be disabled.
• Data for a given timestamp may be dispersed by many collection periods.
Therefore, a timeframe for accepting data at a given interval must be defined. This time-
frame is dimensioned as 20% of the data granularity.
The data required to present complete results for a given SoO at a given interval must
be collected and delivered to the AppServer within the defined timeframe. This time-
frame for data acceptance can be configured in the sas.cfg with the parameter.
PdgEventTimeout = x (default is 20)
For a granularity of 15 minutes, all data associated with a given SoO must arrive to the
system within 3 minutes (20%) counting after the arriving of the first record.
g These kinds of restrictions also apply to the refreshing of Virtual Counters.
There is a small probability of gap occurrences on the first refresh after the reports
finishe the execution. This may occur if the report is still executing while data for the first
refresh is already being processed by the SPOTS AppServer but it is not yet stored in
the DataBase.
5.6 Appendix F- SPOTS Hardware dimensioning Assumptions

SPOTS hardware configuration rules are based on mean values from typical customer
usage and typical Network Element load.
Different configurations are possible, but may decrease performance. Contact region
Sales for a different configuration.
E200613-01-114-V14.0I-23 Id:0900d80580165955 293

The following assumptions are considered in standard dimensioning:

1. Number of concurrent users
2. Network element load
• Standard data retention time is 2 weeks of detailed data and 1 year of historical
data.
• Standard Nokia Siemens Networks recommendations in terms of data collec-
tion.
1. ) The performance of SPOTS system can only be met if the number of concurrent
users (users executing a report simultaneously) or logged users do not exceed the
limits given as follows:
Number of Users
Small SPOTS system
- 10 logged users
- 2 concurrent users executing reports
Medium or Low-End SPOTS system
- 15 logged users
Large or High-End SPOTS system
- 25 logged users
Table 58 Number of users
For higher number of users the performance of the system may decrease, but it
remains operational up to the double of concurrent users. For simplification, the
number of simultaneously logged users may be taken. There is the assumption that
20% of the logged users execute reports simultaneously.
These limits are only applicable to SPOTS users of Java Client (LT+RT). In case of
WebPortal, above table limits does not affect Web client.
2. SPOTS hardware dimensioning
294 Id:0900d80580165955 E200613-01-114-V14.0I-23

Figure 156 Mobile core
Figure 157 STP/number portability and transport
E200613-01-114-V14.0I-23 Id:0900d80580165955 295

Figure 158 Radio access
Figure 159 NGN and perfect voice
296 Id:0900d80580165955 E200613-01-114-V14.0I-23

User Manual (UMN) Abbreviations
6 Abbreviations
ATM Asynchronous Transfer Mode
BAR Backup and Restore
BSC Base Station Controller
BSS Base Station System (now known as GERAN)
BTS Base Transceiver Station
DTOT Daily Total
FQN Fully Qualified Name
GERAN GSM and EDGE Radio Access Network(formerly known as BSS)
GSM Global System for Mobile Communications
MA Monitor Agencies/Agents
OMC-B Operations and Maintenance Centre forBSS
PBH Peak Busy Hour
PDC Performance Data Collector
PLMN Public Land Mobile Network
PMC Public Switching Telephony Network
PMS Performance Management Server
PSTN Public Switching Telephony Network
QoS Quality of Service
RC Radio Commander
SAS SPOTS Application Server
SCL SPOTS Client
SDS SPOTS Database Server
SNS SPOTS Naming Server
SOC Set of Counters
SOO Set of Objects
SPBH Sample at Peak Busy Hour
SPF Siemens Performance File Format
SPOTS Support of Planning, Operation & Maintenance and Traffic Analysis System
SRL SPOTS Reporting Language
Sysmon System Monitor
E200613-01-114-V14.0I-23 Id:0900d80580165958 297

Abbreviations User Manual (UMN)
TAS Online Monitoring Threshold AdministrationServer
TCP/IP Transmission. Control Protocol/Internet Protocol
TP Technology Plug-In
UMTS Universal Mobile Telecommunications System
UNC Universal Naming Convention
UTRAN UMTS Terrestrial Radio Access Network
VC Virtual Counter
298 Id:0900d80580165958 E200613-01-114-V14.0I-23

Spots V14 Um M

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Spots V14 Um M

Hochgeladen von

Copyright:

Verfügbare Formate

SPOTS V14 Mobile

User Manual (UMN)

f Important Notice on Product Safety

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

Reason for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Initial Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2.2.1 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.3.1.2 Set of Objects syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.6.2.4 Alarm Filter Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

5.2.10 dbloadgaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Figure 46 Task Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 130 Main Processes Monitor Completely Operational . . . . . . . . . . . . . . . . 207

Table 46 rtRestartEvents Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Reason for Update

Chapter/Section Reason for Update

Chapter/Section Reason for Update

4.3.1.3 Creating a User Updated information

Chapter/Section Reason for Update

4.6.1.3 Siemens Reports Replaced all Siemens Reports references with

4.9 Best Practices Added chapter

3.2.4 Object Filtering Updated information under Set Filter.

Issue Number Date of Issue Reason for Update

Issue Number Date of Issue Reason for Update

Figure 1 SPOTS Elements

Single Server Installation

Figure 2 SPOTS Single Server Architecture

Multiple Server Installation

Online Monitoring Distributed Server Installation

1.3 SPOTS Ports

Component Port Range

Table 1 Default port assignments for all main SPOTS components

Component Port Range

1.4 Technology Plug-Ins

Figure 3 Network Partitioning Example

Figure 4 Relation between Network Domains and Clusters Diagram

Figure 5 Spreading of Management Domains Example

1.6 User Access Control

1.8 Database Organization

Log type Data description Data loading / generation method

Table 2 SPOTS Database Server data types

1.9 Trend Analysis

1.9.1 Data Generation

SPBH (Sample at Peak Busy Hour)

g The PBH "00:00" is considered to belong to the following day.

1.9.1.2 Aggregation with Extrapolation of missing values

• SDS configuration file sds.cfg for data calculated by SPOTS dbAggregator

Counters of type sum or average

Counters of type MAX or MIN

1.9.1.3 Aggregation without Extrapolation of missing values

1.9.2 Data Manipulation

1.9.3 Trend Analysis Reports

Ad-Hoc Comparison Report

Nokia Siemens Networks Reports

1.10 Online Monitoring

1.10.1 Alarm Generation

Monitor Agencies and Agents

Agents Alarm Processing

Alarm state on Alarm state on the Action

Table 3 Online Monitoring Actions

1.10.2 Online Monitoring Reports

Ad-Hoc Online Reports

1.11 SNMP Alarm Agent