Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SPOTS V10 Drop 4, User Manual - Real Time

327 views

Published on

SPOTS V10 Drop 4, User Manual - Real Time

Published in: Education
  • Be the first to comment

  • Be the first to like this

SPOTS V10 Drop 4, User Manual - Real Time

  1. 1. SIEMENS S.A. SPOTS V10 Drop 4 User Manual - Real Time July/2003 E200301-01-514-V10.0I-02
  2. 2.  SIEMENS S.A. OG IC R&D WON NM CP2 Estrada Nacional 107, 3570 4456-901 Perafita Portugal All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the written permission of Siemens S.A. This document consists of a total of 92 pages. The information contained in this document is subject to change.
  3. 3. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. Table of Contents 1 INTRODUCING SPOTS....................................................................................................................... 5 1.1 Overview ...................................................................................................................................... 5 1.2 Environment ................................................................................................................................. 7 1.2.1 Single Server Installation...................................................................................................... 7 1.2.2 Distributed Environment ....................................................................................................... 8 1.2.3 RT Distributed Server ......................................................................................................... 10 1.2.4 RT Distributed Agencies..................................................................................................... 10 1.3 User Documentation................................................................................................................... 10 2 INITIAL CONFIGURATION TASKS ................................................................................................... 11 2.1 Licensing .................................................................................................................................... 11 2.2 Data Collection and Processing ................................................................................................. 11 2.2.1 Processing of traffic data by Real-Time.............................................................................. 11 2.2.1.1 Agents Overview ............................................................................................................ 12 2.3 QoS Alarms ................................................................................................................................ 13 2.3.1 User-defined QoS Alarms overview.................................................................................... 13 2.4 Alarms Configuration.................................................................................................................. 14 3 SPOTS REAL-TIME........................................................................................................................... 15 3.1 Overview .................................................................................................................................... 15 3.2 Description ................................................................................................................................. 15 3.3 SPOTS RT Threshold Administration......................................................................................... 16 3.3.1 Centralised Administration of Thresholds........................................................................... 16 3.4 SPOTS RT Architecture ............................................................................................................. 17 3.4.1 SPOTS RT Monitoring Agents............................................................................................ 17 3.4.2 SPOTS RT Server module ................................................................................................. 17 3.4.3 Client Terminals ................................................................................................................. 17 3.5 SPOTS RT Agents Alarm Processing ........................................................................................ 18 3.6 SPOTS Real-Time User Interface .............................................................................................. 19 3.6.1 Starting in Windows environment ....................................................................................... 19 3.6.2 Starting in Solaris environment........................................................................................... 19 3.6.3 Login................................................................................................................................... 19 3.6.4 Main Window...................................................................................................................... 21 3.6.5 Threshold Lifecycle Tab ..................................................................................................... 22 3.6.5.1 Monitor Information......................................................................................................... 22 3.6.5.2 Threshold Values............................................................................................................ 26 3.6.5.3 Threshold Values for Virtual Counters............................................................................ 30 3.6.5.4 Threshold Actions........................................................................................................... 31 3.6.5.4.1 Print Threshold Values ............................................................................................. 31 3.6.5.4.2 Export Threshold Values .......................................................................................... 32 3.6.5.4.3 Import Threshold Values .......................................................................................... 37 3.6.5.4.4 Delete All Threshold Values ..................................................................................... 40 3.6.6 Agency Management Tab .................................................................................................. 40 3.6.7 Agent Type Management Tab ............................................................................................ 47 3.6.8 History Log Panel ............................................................................................................... 49 3.6.9 RT Log Viewer in Windows environment............................................................................ 50 3.6.10 RT Log Viewer in Solaris environment ............................................................................... 51 3.7 SPOTS LT User Interface – Utils............................................................................................... 52 3.7.1 Alarm Notification ............................................................................................................... 52 3.7.2 Alarm Browser.................................................................................................................... 53 3.7.2.1 Alarm Browser options ................................................................................................... 54 3.7.2.2 Alarms Filter ................................................................................................................... 54 3.7.2.3 PM Reports driven by Alarm........................................................................................... 56 3.7.2.3.1 TEVL Chart Report................................................................................................... 57 3.7.2.3.2 RT Bar Chart Report................................................................................................. 58 3.7.3 RT Monitoring Panels ......................................................................................................... 60 3.7.4 Refresh Functionality.......................................................................................................... 62 Date interval 62 Data Source 62 3.8 SPOTS SNMP Alarm Agent (SAA)............................................................................................. 65 3.8.1 Overview ............................................................................................................................ 65 E200301-01-514-V10.0I-02 3
  4. 4. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.8.2 Forwarding of SPOTS QoS alarms..................................................................................... 66 3.8.3 Filtering of alarms............................................................................................................... 67 3.8.3.1 Global filtering................................................................................................................. 67 3.8.3.2 Additional filtering ........................................................................................................... 68 3.8.4 Resynchronisation of pending performance alarms ........................................................... 68 3.8.5 Manual alarm deletion ........................................................................................................ 69 3.8.6 SAA Administration Interface.............................................................................................. 69 3.8.6.1 Configure alarm trap destinations and SNMP protocol version ...................................... 70 3.8.6.2 Count all pending alarms................................................................................................ 71 3.8.6.3 Visualise all pending alarms........................................................................................... 71 3.8.6.4 Visualise pending alarms with class …........................................................................... 71 3.8.6.5 Visualise pending alarms with instance … ..................................................................... 71 3.8.6.6 Visualise pending alarms with triggered threshold …..................................................... 71 3.8.6.7 Visualise pending alarms with event time … .................................................................. 72 3.8.6.8 Clear all pending alarms................................................................................................. 72 3.8.6.9 Clear pending alarms with class … ................................................................................ 72 3.8.6.10 Clear pending alarms with instance … ....................................................................... 72 3.8.6.11 Clear pending alarms with triggered threshold …....................................................... 72 3.8.6.12 Clear pending alarms with event time ….................................................................... 72 3.8.6.13 SAA Processes Administration................................................................................... 73 3.8.6.14 SAA Filtering Administration....................................................................................... 74 4 REFERENCE FOR SPOTS REAL-TIME COMMANDS ..................................................................... 80 4.1 SPOTS Real-Time Server Commands....................................................................................... 80 4.1.1 Stopping SPOTS RT .......................................................................................................... 80 4.1.2 Starting SPOTS RT ............................................................................................................ 80 5 ANNEXES .......................................................................................................................................... 81 5.1 Log Files..................................................................................................................................... 81 5.1.1 RT Agent Log Files............................................................................................................. 81 5.1.2 RT Server Log Files............................................................................................................ 81 5.2 SNMP Alarm Agent MIB Definition ............................................................................................. 83 6 REFERENCES................................................................................................................................... 89 7 GLOSSARY AND ABBREVIATIONS ................................................................................................. 90 4 E200301-01-514-V10.0I-02
  5. 5. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 1 Introducing SPOTS 1.1 Overview Motivation Due to the immense growth and harsh competition that characterizes today's telecommunication business, the operators need to take full advantage of their installed equipment. Only effective management of the network performance can achieve the balance between optimised usage of the network resources and a good quality of service. The Network Nodes have the ability to generate extensive data for performance analysis. As these data can easily add up to several gigabytes, a powerful analysis tool is required to collect, process and analyse the huge volume of information. The SPOTS tool allows the operator to easily implement the required performance analysis tasks and generate all the necessary information for taking the right decisions. Scope The SPOTS V10 Drop 4 application software includes a mandatory Long-Term part and an optional, additional Real-Time part. The SPOTS V10 Drop 4 Long Term provides performance management analysis capabilities, allowing to produce pre-defined and user-defined reports with Performance Management indicators based on data periodically collected from the network. The SPOTS V10 Drop 4 Real Time part provides near real-time updates of the network Performance Management information, allowing to define threshold values for Performance Management indicators that result in alarms when they are violated. The optional module "SNMP Alarm Agent" allows these alarms to be forwarded via SNMP to an external application. This document describes the SPOTS V10 Drop 4 Real-Time application part. The description of the SPOTS V10 Drop 4 mandatory application part, that is, the Long-Term part, is provided in [1]. Architecture The SPOTS system was design based on a three-tier scalable architecture, comprising the following functional components: SPOTS PMC Client component, implementing the application graphical user interface. SPOTS PMS Application server, implementing all the application business logic. Database server, implementing the data repository. SPOTS RTS Real-Time Application server, implementing the RT application business logic. Real-Time Database server module, implementing the RT data repository. SPOTS RTA Real-Time Application agents, implementing the first level of traffic data processing. E200301-01-514-V10.0I-02 5
  6. 6. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) SPOTS RTC Real-Time Client component, implementing the Real-Time application graphical user interface. SPOTS SAA SNMP Alarm Agent, implementing the forwarding of alarms to external FM OS applications. All SPOTS installable components are distributed via the SPOTS CD-ROM distribution media. Real-Time Performance Monitoring SPOTS-RT supports in-depth investigations of the network status through graphical reports of current and historical traffic attributes. SPOTS-RT features: Traffic data analysis using multiple thresholds, for all NE types and versions supported by the SPOTS Long-Term traffic data collection and processing (consult [1], Table 1 Supported Network Nodes and Network Management Systems). Comprehensive and flexible reporting features to facilitate quick and easy investigations of network traffic problems Correlation with historical traffic values such as daily, weekly, monthly statistics Distributed platform Threshold definition for user-defined metrics (Virtual Counters) ‘Mass’ threshold administration Forwarding of alarms to external FM OS applications, as SNMP traps, including: Flexible user-defined filtering criteria for selecting the alarms to be forwarded Resynchronisation of the pending performance alarms status Manual deletion of pending performance alarms Software Functions The current version supports the following functions: • State of the art Java2 graphical user interface • High-performance Oracle 8i database for storage of PM data. • Easy visualisation of performance data on table and chart formats • Useful SIEMENS Real-Time pre-defined reports • User access control • Complex entities (Virtual Counters, Set of Counters, Set of Objects) • Management Domains • Real-Time Monitoring Panels for UTRAN (Cell and the RNC Processor Load), CS (MSC), PS (BIAS Load), and GERAN (Cell, BSC Processor Load, BSC PCU Load, BTSM Processor Load and TRx Availability). • Auto-refreshed on-line reports 6 E200301-01-514-V10.0I-02
  7. 7. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 1.2 Environment SPOTS has been designed for high scalability: • all services are multi-threaded thus providing an optimum scalability regarding the number of system processors; • the data storage can be distributed across several systems for better performance regarding the data access; • the application services can be distributed across several systems for better performance regarding the data processing. This provides a great breakthrough in ability for SPOTS to handle all network sizes. Both the SPOTS Long-Term and Real-Time parts comprise several functional components, grouped into installable SW packages according to a Client/Server approach. The SPOTS Long-Term part comprises the SPOTS Performance Management Server (PMS) and SPOTS Performance Management Client (PMC) functional components - refer to [1], Section Overview. The SPOTS Real Time (RT) application for Performance Alarm Monitoring comprises the following functional components: • SPOTS Real Time Server (RTS): responsible for all Real-Time-specific application processing and related storage (with exception of alarms, which are stored on the PMS). Available on Solaris. Comprises the following packages: - SPOTS Real Time Server (RTS) - SPOTS Real Time Agency (RTA) (also available on Windows 2000) - SPOTS SNMP Alarm Agent (SAA) (optional package) • SPOTS Real Time Client (RTC): graphical user interface for Real-Time application administration. Available on Solaris and on Windows NT/2000. Comprises a single RTC package. Currently two SPOTS installation types are available, the Single Server and Multiple Server installations. In a single server installation, all SPOTS PMS and RTS components are installed on a single Solaris host machine, whereas in a multiple server installation, they are deployed across multiple hosts. Regardless of the chosen installation type, the SPOTS PMC, RTC and RTA can be installed on any Solaris or Windows workstation across the network, from where they access the server host(s). 1.2.1 Single Server Installation In a single server installation, all SPOTS PMS and RTS components are installed in the same target system. Refer to [4] and [5] for information on the installation procedure for Long-Term and Real- Time respectively. The picture below shows a SPOTS single server installation on a Switch Commander environment (this picture is provided only as an example - other NMSs are not considered): E200301-01-514-V10.0I-02 7
  8. 8. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) GMC – Global Management Center CS Ethernet PMS + RTS + RTA PDC PMC + RTC PMC + RTC NE PMS – SPOTS Performance Management Server PMC – SPOTS Performance Management Client CS – SC Communications Server PDC – SC Performance Data Collector RTS – S POTS Real-Time Server RTC – SPOTS Real-Time Client RTA – SPOTS Real-Time Agents After installing the SPOTS software and before executing the available performance reports, the user must perform several configuration tasks (see Chapter 2 Initial Configuration Tasks). 1.2.2 Distributed Environment For big networks, which have a significant number of nodes to manage, the amount of generated traffic data to store and process is enormous; thus, the use of a single server installation may pose performance and capacity limitations. These problems can be overcome through the use of a multiple server installation, where PMS and RTS packages are deployed across multiple Solaris host machines. 8 E200301-01-514-V10.0I-02
  9. 9. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The picture below shows a SPOTS distributed installation with 3 sites, on a Switch Commander environment (this picture is provided only as an example - other NMSs are not considered): RMC2 – Regional Management Center 2 CS Ethernet PDC PMS + RTS + RTA PMC + RTC PMC + RTC (NE) NMC – National Management Center CS Ethernet PMS + RTS + RTA PDC PMC + RTC PMC + RTC RMC1 – Regional Management Center 1 CS Ethernet PDC PMS + RTS + RTA PMC + RTC PMC + RTC NE (NE) PMS – SPOTS Performance Management Server PMC – SPOTS Performance Management Client CS – SC Communications Server PDC – SC Performance Data Collector RTS – SPOTS Real-Time Server RTC – SPOTS Real-Time Client RTA – SPOTS Real-Time Agents The existing possibilities for distributing RTS packages depend on the multiple server distribution chosen for the Long-Term (PMS) packages, namely, the distribution of the SAS, SNS and SDS packages. Refer to [1], Section Distributed Environment for aspects regarding the PMS multiple server installation. The current document deals only with distribution of RTS packages. The rules for distribution of RTS packages are put forward in the next section. E200301-01-514-V10.0I-02 9
  10. 10. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 1.2.3 RT Distributed Server The SPOTS RT system installation in a distributed environment must follow some simple rules: • For each SAS installation, there must be a RTS installed on the same machine. The SAS/RTS machine carries all Real-Time processing load (threshold analysis, alarm triggering etc.) associated with the traffic data loaded by its SAS (i.e. by loader command executions performed on the machine). • For each RTS/SAS pair, the RTS will use a single SDS to store the RT-specific configuration data. If more than one SDS is being accessed by the SAS, the RTS will use only one of them. The SDS can be located on another machine. • There must exist a global SNS reachable by all RTC. The RTC will use this SNS to establish connection to the selected SAS/RTS pair. • On each RTS/SAS machine, the RTA package must also be installed. The user must then use the RTC to register the RT Agencies and their RT Agents responsible for handling the data for this SAS. RT Agents must be configured to send alarms to the correct primary domain. After the RTS has been correctly installed the RTA will send the alarms to the correspondent SAS. Users will be able to login with a RTC to any RTS where they have permissions. These permissions will be set in the pair SAS/RTS, so if a user has rights to login to a SAS he will also be capable of logging in its counterpart RTS. Thresholds will be configured for each RTS/SAS. This means that each RT Agent will only generate alarms for thresholds defined in the RTS where it was registered. 1.2.4 RT Distributed Agencies The SPOTS RT Agencies may be installed on the same machine as the SPOTS RT Server or/and on a dedicated Windows 2000 machine to allow the SPOTS load distribution. The SPOTS RT Agency is the platform where several RT Agents can run. The SPOTS user/administrator can register RT Agencies and RT Agents via the SPOTS RT Client on any machine where the SPOTS RTA service/daemon was installed. It is advisable to have all RT Agents running on the same machine, although it is possible to have some data being processed in RT Agents running in the server machine (in Solaris) and other data types being processed in other RT Agents in a Windows dedicated machine. The details on these configurations (RTA in Solaris and Windows) are described in [5]. 1.3 User Documentation The product documents are supplied with the application on the CD-ROM distribution media. The file readme.spots is provided, with notes about the distribution media contents, including the list and location of the supplied documents. Additionally, the Customer Release Notes (containing important information about configuration, installation and known problems) are provided on paper. 10 E200301-01-514-V10.0I-02
  11. 11. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 2 Initial Configuration Tasks 2.1 Licensing Access to the following SPOTS Real-Time functionality is controlled by licensing: • Global real-time functionality; • SPOTS SNMP Alarm Agent. Therefore, specific license strings must be provided for each of these items. Throughout this Manual, licensing support enabling the SPOTS Real-Time full functionality will be assumed. Before using SPOTS Real-Time, make sure that the necessary license strings have been ordered and are installed - refer to [4], Section Configuring SPOTS licenses, for information on the required procedure. 2.2 Data Collection and Processing The SPOTS Real-Time reuses the Data Collection and Processing mechanisms provided by the SPOTS Long-Term part. Upon execution of the SAS loader command (see [1], Section PMS Commands for SAS), the data are automatically forwarded to the Real-Time applications (in addition to being loaded into SPOTS Long-Term Database). This section will not cover in detail the configuration of Data Collection and Loading, since this belongs to the Long-Term part - for details see [1], Section Data Collection and Loading. Only Real-Time specific issues which affect the configuration of Data Collection and Loading will be covered here - see following section. 2.2.1 Processing of traffic data by Real-Time The following restrictions must be taken into account when configuring the Data Collection and Processing mechanisms provided by the SPOTS Long-Term part (refer to [1], Section Data Collection and Loading). These restrictions must be observed in order to allow processing of traffic data by the SPOTS Real-Time part. Data Granularity restrictions: The traffic data Granularity Period (GP) must match the GP of the Real-Time agent type in charge of processing that data. Only traffic data with the correct GP duration shall be processed by Real-Time. This must be taken into account, in particular, for UTRAN and GERAN Network Elements, which produce traffic data with a configurable GP. If Real-Time data processing is desired, the Network Elements configuration must take into account the appropriate Real-Time agent type's GP. For information on the supported agent types and their GP's see Section 2.2.1.1 below. Data Upload periodicity restrictions: For data handled by a single agent type (e.g. Core Q3 scanner data), the configured upload periodicity from the NMS (Network Management System) to SPOTS must be uniform across all Network Nodes and measurements handled by the agent type. For example, if part of the Core-Q3 data are uploaded from PDC to SPOTS at 15- minute intervals and the remainder at 30-minute intervals, errors may occur in the Real- Time processing (even if all the data were generated with a common 15-minute GP). This implies that Transmission File generation frequency on the PDC (see [6], [7]) must be uniform - preferably with a single GP per transmission file for all kinds of data. E200301-01-514-V10.0I-02 11
  12. 12. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) For specific Real-Time configuration issues please refer to [5], Sections Configuration Issues. 2.2.1.1 Agents Overview There are multiple RT Agents to cover the supported traffic data file types, according to the following table. For more information on the supported file types see [1], Table 5 File types retrieved by Collector. Data type Files GP (min) Files dir. NEs Agent types CS REC (*.trf) 15 /cyclic SR80, SR90, CS10, CS20, CS21 CS REC 15 /sctc SR80, SR90, CS10, CS20, CS21 ST REC (*.trf) 15 /hlri HI11 HI SSNC Q3 (*.spf) 15 CS10, CS20, CS21, GR11, GR20, GR31, PO10, PO20, PO21, V13, V15 PS Q3 (*.spf) 15 /q3dc GR11, GR20, GR31, PO10, PO20, PO21 Q3 PS SNMP / FTP (*.spr) 15 /spr GR20, GR31, PO10, PO20, PO21 SNMP UTRAN ASN.1 (*.upf) 60 /upf UMR2X, UMR3.0 NB1P NB2P UTRAN GERAN *.exp 60 /exp BR5.0 BR_OMCB BR5.5 *.ASCII 60 /ascii BR6.0, BR7.0 BR_RC CiscoGGSN *.spf 15 /ggsn PO21C GGSN MSP *.spf 15 /msp MSP30 MSP Table 1 - RT Agent types, file types and supported NE versions As can be seen above, the core NE versions (except HI11) are shared between several agents (Q3, CS, SNMP and ST). For each measurement, depending on the source of data, one and only one agent applies. All the performance data is collected from its several sources by the SPOTS Long-Term mechanisms described in [1], Section Data Collection and Loading. The data may come from any of the Network Management Systems (Element Managers) supported by SPOTS Long-Term in the current SPOTS version. The default installation procedure installs agents prepared for 15 minutes granularity (core) and 60 minutes granularity (radio). There is a procedure described in the RT Installation Guide [5], Section 4.4.4 (Modifying the RT Agents default granularity) in order to allow the user, if desired, to operate an agent type at a different granularity (e.g. change the UTRAN agent type to 15 minutes granularity). However, one agent type shall always operate at one single fixed granularity (the user cannot analyse thresholds at one granularity for some measurements and another granularity for other measurements, within the same agent type). 12 E200301-01-514-V10.0I-02
  13. 13. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 2.3 QoS Alarms 2.3.1 User-defined QoS Alarms overview The SPOTS Real-Time add-on application provides support to user-defined QoS Alarms based on the traffic data produced by the managed network nodes. These alarms correspond to threshold violation alarms generated by the SPOTS Real-Time Alarm Monitor Agents. The SPOTS RT Agents receive as input for the QoS alarm monitoring the same traffic data files which are processed by the SAS loader command (see [1], Section PMS Commands for SAS) in order to load data into the SPOTS Long-Term Database. This alarm generation is based on the comparison of the received traffic data against the SPOTS RT user-defined threshold levels. Alarms generation is performed in near-real-time, meaning that it can only occur when the loader processes the relevant traffic files i.e. after the traffic data have already been collected onto the SPOTS file system from the respective NMS. The timestamp of the issued alarms is always the time of the end of the granularity period of the data, just like the timestamp of the corresponding traffic data records. Once the comparison results no longer in a threshold violation, then an alarm clear notification is generated. SPOTS PMS is able to receive these QoS alarms and send them through a specific SPOTS Event Gateway to the SPOTS PMC Alarm Browser, where they can be visualized. Alarms are also stored on a dedicated log in the PMS Database. E200301-01-514-V10.0I-02 13
  14. 14. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 2.4 Alarms Configuration After installing the SPOTS RT add-on a few tasks need to be completed before starting to use the RT system. The first two tasks are to be performed in the SPOTS LT system and might already have been performed when this RT system was installed: Create SPOTS DB Domains Using the PMC, the user must create the SPOTS Domains to which the traffic data and alarms coming from the RT Agents should be sent. See SPOTS Long-Term User Manual for more information about SPOTS Domains. Create SPOTS Users Using the PMC, the user must create the SPOTS Users that will use the RTC, with respective privileges. After performing these two tasks on the SPOTS LT Client the user still needs to configure the SPOTS RT system: Create SPOTS RT Agencies Using the RTC, the user must create and register the SPOTS RT Agencies at the hosts where the RT Agents will collect the performance data, and start them up. Create SPOTS RT Agents Using the RTC, the user must create the SPOTS RT Agents that will collect the data and assign them the correct SPOTS Domain. Create Thresholds To receive user-defined Q0S Alarm events the user also needs to create Thresholds, using the RTC. Configure SPOTS Event Gateway Please refer to the RT Installation Manual[5]. Note that after altering the egw.cfg file it is necessary to stop and start the SAS and the RTS. This can be done following the steps described in the relevant sections of the LT and RT Installation Guides [4] and [5]. 14 E200301-01-514-V10.0I-02
  15. 15. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3 SPOTS Real-Time 3.1 Overview The SPOTS Real-Time component is an optional add-on to the SPOTS Long-Term functionality, providing near real-time updates of the network performance management information. This module also provides the possibility of defining threshold values for PM indicators that result in alarms when they are violated. 3.2 Description All performance data produced by the managed network nodes is collected via the supported NMS interfaces by the Collector program. Once this data becomes available on the SPOTS platform it is loaded into Database using the loader command. This command also forwards the traffic data onto the SPOTS RT components. SPOTS RT monitors the violation of SPOTS’ user-configured Threshold Values for selected counters and forwards these violations in the form of alarms to the SPOTS PMS Event Gateway. These alarms can be seen using the Alarm Browser window from the SPOTS LT Client. The SPOTS RT add-on offers the user the possibility to: • Administer the PM monitoring threshold values and filters and associate them with network object classes and PM indicators. • Administer the SPOTS RT platform. SPOTS LT Client SPOTS LT Server SPOTS RT Client SPOTS RT Agents SPOTS RT Server The SPOTS RT Client (SPOTS RTC) allows the operator to interact with the SPOTS RT Server (SPOTS RTS) add-on component in order to administrate the threshold and filter values, as well as to manage the several SPOTS RT Agents and Agencies (SPOTS RTA). This component also interacts with the SPOTS PMS Database Server in order to obtain the SPOTS measurements’ metadata and object model. SPOTS RTC interacts with the SPOTS RT Agents Platform Manager to continuously get updated log messages about the behaviour of the SPOTS RT Agents Platform and about the behaviour of the SPOTS RT overall application logic. SPOTS RT server runs independently of SPOTS RTC. It may not be running or even installed for SPOTS RT server to run. E200301-01-514-V10.0I-02 15
  16. 16. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.3 SPOTS RT Threshold Administration The SPOTS RT components for Performance Alarm Monitoring provide the mechanisms to automatically detect quality of service problems and alert the operator about performance degradations of the network. It reduces significantly the reaction times to fix performance problems. Spots Alarming complies with Rec. ITU-T X.733 and X.739. Performance Management Alarms are based on the Monitored Metric concept: the Performance Management indicator (Raw or Calculated Counter) and the corresponding network Object(s). Threshold Values with different severity are assigned to Monitored Metrics; whenever the observed value of the Monitored Metric crosses one of its Threshold Values, an Alarm is generated. Daily time intervals (Monitored Periods) are associated with each Threshold Value, defining the period of the day when the alarm mechanism is active. SPOTS RT provides support for the administration of Threshold and Filter values. Each threshold is associated to a measurement counter and contains at least the following attributes: • Threshold level; • Severity of the Threshold; • Threshold cross direction; • Threshold clear level; • Associated Object Class; • Associated measurement Counter; There may be more than one Threshold associated to one counter at a time, each with a different severity. It is possible to associate filters to object instances in order to limit the range of monitored object. For this the concept of a “Black List” of monitored objects is implemented. All the Thresholds defined in SPOTS RT component are associated to counters known in SPOTS LT Metadata. These can be raw counters or calculated counters. These last counters are complex counters built from arithmetic formulas based on the raw counters of one specific SPOTS Measurement. These formulas are stored in SPOTS Metadata and their values are calculated when the performance management data is loaded in SPOTS database. The values of these complex counters are also stored in the SPOTS database. In SPOTS RT there is also support for the definition of one reference counter per each counter monitored. This reference counter can be associated a minimum value that must be crossed to enable the alarm analysis of the monitored counter. For example, an alarm for one Trunk Group is only triggered for “ASR 80 %” if “Calls Carried 1000”, or an alarm for one Destination is only triggered for “MHT 10 seconds” if “Calls Carried 50”. 3.3.1 Centralised Administration of Thresholds The administration maintenance tasks will be very simple to handle. The user has facilities to manage the threshold from the entire range of RT Agents from one single point. 16 E200301-01-514-V10.0I-02
  17. 17. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.4 SPOTS RT Architecture The architecture of SPOTS RT is very scalable. It is distributed, allowing a very effective use of the communication infrastructure, and at the same time providing the critical information in a short period for further analysis. This architecture can grow with the network allowing the operator to start with a very small configuration. The following components are available: • SPOTS RT Agents • SPOTS RT Server, responsible for the core processing • Client terminal working positions 3.4.1 SPOTS RT Monitoring Agents All configuration of filtering is done at the central server. This RT Server will automatically download to the RT Agents any necessary update to the monitoring parameters. The administration of these machines can be done at the local console or via remote access. These RT Agents are responsible for the collection of real-time data. 3.4.2 SPOTS RT Server module The SPOTS RT Server module is a software upgrade installed at the SPOTS Long-Term server. This package will enable the real-time functionality and remote monitoring in the same system as the one used for long term. This makes it possible to make a real traffic analysis short or long term based using the same tooling. 3.4.3 Client Terminals These are the working positions used by the operators, corresponding to workstations where PMC and RTC are installed. From these clients it is possible to run daily routine tasks as well as administrating the servers. These will depend on the privileges assigned to the client. As a security measure, the administration of thresholds is restricted to one client only. E200301-01-514-V10.0I-02 17
  18. 18. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.5 SPOTS RT Agents Alarm Processing The SPOTS RT Agents are software agents that are loaded into the SPOTS Real-Time Agencies (RTA) on the RT Server, to perform the necessary alarm monitoring tasks. One SPOTS PMS with the SPOTS RT add-on can collect data from several NMSs if the size of the networks requires. For each PDC server supported, there must be one SPOTS RT Agency in place. These RTAs are the support platforms for the SPOTS RT Agents to perform its tasks. These SPOTS RT Agencies and RT Agents are components that can be monitored and managed through the RT Client. The SPOTS RT Agents are responsible for issuing an alarm when a threshold is crossed and for sending an alarm clear notification when the threshold is crossed on 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 resumes the actions taken by the SPOTS RT Alarm Monitor Agent based on the alarm state on the last and current monitoring periods for each association of threshold and counter. Alarm state on the last period Alarm state on the current period Action ON no action ON OFF sendClear ON sendAlarm normal procedure OFF OFF no action ON no action NO DATA (2) OFF no action ON sendClear NO THRESHOLD (3) OFF no action ON sendAlarm exceptional procedure NO DATA (1) OFF no action Table 2: Alarm Processing (1) When a counter starts being monitored for the first time (a new threshold is created) there is no alarm state for that association of threshold and counter on the last period. (2) When performance data is no longer received for a monitored counter (imagine that an interface card has been unplugged) the Alarm Monitor Agent’s alarm state for that association of threshold and counter shall remain until data is received again. The alarm condition may be manually cleared outside the RT Agents system, in the SPOTS PMS Alarm Browser. (3) If a counter is no longer on the set of the monitored counters (a threshold was deleted), then, if its alarm state was ON before then an alarm Clear shall be issued. 18 E200301-01-514-V10.0I-02
  19. 19. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.6 SPOTS Real-Time User Interface 3.6.1 Starting in Windows environment To start the RT Client or the RT Log Viewer, select the correct icon from the start menu. The RT Client will provide the user with an interface to all RT administration tasks. Only one of these clients can be opened at the same time, so a Log Viewer is also available for users who just want to check Agencies and Agents events. 3.6.2 Starting in Solaris environment To start the RT Client perform the following commands: - go to the RTA installation directory. In case in the RTA installation the default path was accepted this installation directory is /opt/spots/rt. Otherwise it is the installation path selected by the user. cd /opt/spots/rt - execute the command monitor 3.6.3 Login Immediately after starting the RT Client, the user is presented with a Login Dialog asking the user to enter his username and password. In the username field, the user should enter his complete username, including the machine or NT domain (e.g. northjohn). In the password field the user should enter the password for the username entered before. By pressing the “Cancel” button the user cancels the login and the RTC exits. After pressing the “Ok” button, the following scenarios might happen: The RTC could retrieve the list of SAS available for the corresponding user, thus presenting a window asking the user to select the desired SAS. E200301-01-514-V10.0I-02 19
  20. 20. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) The RTC couldn’t get the list of SAS, either because it couldn’t contact the SNS (‘Logon Failed’) or the user didn’t have permission on any of the available SAS (‘No SAS found’). There’s also the possibility that another user is already using the RTC and only one can administrate the RT system at a time. If that’s the case the user cannot login and will be presented with the following Dialog. In the select SAS dialog the user can still cancel the login by pressing the “Cancel” button, returning to the initial Login dialog. He can also pick the desired SAS and press “Ok”. This can lead to two situations: The username/password pair was accepted, leading to the main RTC window The username/password pair was not recognized originating a “Logon Failed” window. If SPOTS or the RT system are not licensed the following window will appear: Please follow those instructions to find out how to get a license for your RT system. 20 E200301-01-514-V10.0I-02
  21. 21. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.6.4 Main Window If the login procedure is successful, the user will be presented with the SPOTS RT Client main window. This window will be composed of six distinct areas: Title bar - Consists of the application icon plus the name of the application or application task on the left side and the standard minimize, maximize and close buttons on the right side. Toolbar - The application pull down menus, containing all the available functions. Action Pane Selector - Provides a way to the user of selecting the desired Action Panel. Selection Tree – Provides a way to the user of selecting the object to modify (a Counter Monitor Information, an Agency or an Agent). Action Panel – In this panel the user will be able to modify the attributes of the object selected in the Selection Tree. Log History Panel – Here, the user can see the last actions performed by the agents. After startup the last logs are automatically loaded. E200301-01-514-V10.0I-02 21
  22. 22. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) At any time the user can choose to leave the application by Selecting the Exit action from the Client menu. 3.6.5 Threshold Lifecycle Tab The Threshold Lifecycle Tab allows the user to administrate the Threshold Values associated to the monitored SPOTS Measurements’ Counters. 3.6.5.1 Monitor Information For the user to be able to create Threshold Values associated to one specific SPOTS Counter he must start monitoring the Counter. To do this the user selects the SPOTS Object Class. This can be done using the SPOTS Real- Time Object Browser on the left side window. The icon represents the SPOTS Object Classes. The user must then select the SPOTS Measurement and the Counter to be monitored. The icon represents the SPOTS Measurements of the Object Class parent, and the icon represents the Counters of its parent Measurement. 22 E200301-01-514-V10.0I-02
  23. 23. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The creation of the Monitor Information can be done using the right-side mouse button to select the Monitor This Counter option over the chosen Counter. This Monitor Information will be common to all the Threshold Values created for that monitored SPOTS Counter. The icon represents the Monitored Counters in the SPOTS Object Browser. E200301-01-514-V10.0I-02 23
  24. 24. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) After a Counter is being monitored it is possible to Update Reference Counter or to Delete Monitor Information. These options can be selected using the right-side mouse button. 24 E200301-01-514-V10.0I-02
  25. 25. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The Update Reference Counter window allows the user to define a Reference Counter. If the Use Reference Counter option is selected then the alarm analysis of the monitored Counter for all the defined Threshold Values will be dependent on the violation of the Reference Counter’s Reference Value. If this option is selected the Reference Counter Information must be provided: Reference Counter Name: Any Counter that belongs to the selected SPOTS Measurement. Except the own Counter being monitored. Reference Value: Only when the observed Reference Counter crosses this value, the Threshold Values can be evaluated. Cross Direction: The comparison of the crossing of the Reference Value can either be done when the observed value is increasing or decreasing. The Update button saves the new Reference Counter Information in SPOTS Real-Time database. The Cancel button discards all the modifications. When the user selects the Delete Monitor Information option and confirms that he really wants to delete the selected Monitored Information then this information will be deleted from the SPOTS real-time database. Important note: By deleting a Monitor Information, all the Threshold Values created under it will also be deleted from the database. E200301-01-514-V10.0I-02 25
  26. 26. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.6.5.2 Threshold Values An Alarm is generated when the observed value of the Counter’s Monitor Information crosses one Threshold Value. For each Counter being monitored, up to four Thresholds can be defined – one for each Alarm Severity (from “Warning” to “Critical). Each Threshold Value will be categorised according to the crossing direction: “Up” (Alarm triggered when the Monitor Information value is increasing) or “Down” (Alarm triggered when the Monitor Information value is decreasing). In order to avoid a meaningless sequence of Set/Clear Alarm when the Monitor Information values are close to the Threshold Values, a value is defined (based on a percentage of the Threshold’s Value) for Alarm clearance. After selecting a Counter being monitored, the right side window of the Threshold Lifecycle tab will present the Reference Counter information as well as the Thresholds Information table. The three buttons on the bottom of the Threshold Information window are used to administrate the Threshold Values. The Create button allows the user to create a new Threshold Value for that Counter being monitored by opening a Create Threshold Value window. The Update button allows the user to update a selected Threshold Value from that Counter’s Threshold list by opening an Update Threshold Value window. The Delete button allows the user to delete one Threshold Value from the SPOTS RT database. When a user selects the Create or Update button a window containing the properties of the Threshold Value appears. 26 E200301-01-514-V10.0I-02
  27. 27. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. In this window it is possible to change the attributes of the Threshold being updated or created. When updating a Threshold it is not possible to change the Threshold’s name and severity. The attributes are depicted in the following table: Thresholds Value Attributes Name: Identification of the Threshold Value. Severity: Alarm severity: “Warning” (the default value), “Minor”, “Major’” or “Critical” (ordered by increasing severity). Activation State: The threshold alarm monitoring status. If “OFF” (the default value), the Threshold Value is not evaluated; therefore, no PM Alarm (for this Threshold Value) is generated. Value: When the observed Counter crosses this value, an Alarm is generated (set). Clear Percentage: According to the “Crossing Direction”, a pending Alarm is cleared if the observed value is: • Less than Threshold Value - Threshold Value x Clear Percentage (“Up”) • Greater than Threshold Value + Threshold Value x Clear Percentage (“Down”) Clear Value Clear Value is the value the threshold must pass to clear a Pending Alarm: • Clear Value = Threshold Value - Threshold Value x Clear Percentage (“Up”) • Clear Value = Threshold Value + Threshold Value x Clear Percentage (“Down”) Cross Direction: Depending on the evolution of the Threshold Value (increasing or decreasing), two different Alarms can be produced when a certain value is crossed. Therefore, the crossing direction must be specified when defining a Threshold: • Up: an Alarm is set if the Threshold is crossed when the observed value was increasing. • Down (default value): an Alarm is set if the Threshold is crossed when the observed value was decreasing. E200301-01-514-V10.0I-02 27
  28. 28. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) As one can see, the Clear Value, Clear Percentage, Cross Direction and Value attributes are dependent on each other. Because of this, the user has the choice to change the Threshold Values based on Clear Percentage or Clear Value. To perform this choice the user has to select the Radio Button next to the Attribute he wishes to work with. After performing this choice the attribute not selected becomes disabled and any changes in the other attributes cause this attribute to update accordingly. The Threshold Information table presents some extra information about each Threshold Value: Monitored Period: Link to the Monitored Period window. Monitored Periods are used to specify, for each Threshold Value, the daily time interval for which the alarm mechanism is active (i.e., Threshold Values are observed and the corresponding Alarms are set / cleared). Object Black List: Link to the Object Black List window. It is possible to filter object instances in order to limit the range of monitored objects. For this the concept of a “Black List” of monitored objects is implemented by allowing the user to select the Object Instances to which he/she does not want to associate this Threshold Value. Default: Since one monitored Counter may have more than one Threshold Value defined, this Default option allows the user to select one of the Threshold Values to be the default one. From that moment on, when the user creates a new Threshold Value all its attributes will be similar to the ones of the default Threshold. In the Threshold Information Window the user can see some information regarding Monitored Periods and Object Black List. For each threshold value, the percentage of time of the day the threshold is to be active is presented near the Monitored Period icon. The size of the Object Black List is also presented near its icon. The user can see more detailed information about each one of these parameters by clicking in the desired icon. By choosing the Monitored Period icon a window showing which periods of the day are being monitored by the selected Threshold is presented: 28 E200301-01-514-V10.0I-02
  29. 29. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. By choosing the Object Black List’s icon the user can browse the chosen list for the selected threshold value: To change a given Threshold Value’s Monitored Period or Black List the user should use the Update button below the Threshold Value Information Table. After being presented with the Update window the user should select what information he/she desires to change by pressing one of the two buttons presented in the bottom of the window. By selecting the Change Monitored Period Window a new window, identical to the Monitored Period Viewer, is presented. The main differences will be that this window has an Add Period button, the Sliders in each Monitored Period are enabled. And each Monitored Period has a Delete button next to it: E200301-01-514-V10.0I-02 29
  30. 30. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) Using this window users can add new Monitored Periods, using the Add Period button, modify existing ones, using the sliders provided, and delete Monitored Periods by pressing the associated Delete button. If the user selects the Change Object Black List button, a window with two lists is presented. The left-sided list contains all the Monitorable Objects not in the Black List, while the right-sided list contains the Objects in the Black List. Users can change objects to and from the Black List using the arrow buttons provided. If for any reason the user is not satisfied with the changes performed he/she can use the Cancel Button to undo any changes. 3.6.5.3 Threshold Values for Virtual Counters As for Counters, alarms are generated when the observed value of a Virtual Counter (VC) Monitor Information crosses one Threshold Value. The Monitor Information concept and the management of thresholds for VCs is done like for the Counters as explained in sections 3.6.5.1 and 3.6.5.2. In the left side tree in the Threshold Lifecycle tab the VCs for a specific OC appear under a Measurement node called OCName_VC. 30 E200301-01-514-V10.0I-02
  31. 31. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.6.5.4 Threshold Actions 3.6.5.4.1 Print Threshold Values To print or view a complete list of all the defined Threshold Values the user can select the Print Thresholds option under the Thresholds menu. E200301-01-514-V10.0I-02 31
  32. 32. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) This action will bring up a new window containing a list of all the Thresholds. The user can then use the printer icon ( ) to print the list. 3.6.5.4.2 Export Threshold Values To export all the defined Threshold Values the user can select the Export Thresholds option under the Thresholds menu. The main purpose of this functionality is to give to the user an alternative way to create, modify or delete thresholds. Instead of using the RTC user interface, a text editor or the Excel application in case of the Windows environment can be used. This could be very useful if for example the operator wants to make considerable modifications. Additionally this functionality can be used to perform backups of the Threshold Configuration 32 E200301-01-514-V10.0I-02
  33. 33. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. data present in SPOTS RT. The typical use case of this feature consists in: 1. Export the existing thresholds. In this operation a CSV file is created. Please take note that in the CSV file there is a line for all the possible thresholds that can exist. The thresholds that are present in the SPOTS RT database, at the time of the export, are written in the CSV file with the Flag Exist set to “YES”. All the other possible thresholds that can be created in the SPOTS database are written in the CSV file with the Flag Exist set to “NO”. 2. Modify the CSV file (adding new thresholds, etc) and save it. 3. Import the CSV file in the RTC causing the new changes to occur in the SPOTS RT DB. After selecting the Export Thresholds option the following window is displayed. Select a path (the default one is the RTC installation directory) and the filename for the CSV file that will contain the thresholds configuration information. Press Ok to Export. Press Cancel if you want to cancel the Export action. When the Export finishes the following message is displayed. Opening the exported CSV file, for example, with the Excel application, the threshold configuration data is displayed and can then be modified. E200301-01-514-V10.0I-02 33
  34. 34. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) The format of the CSV file used in the Import/Export of the threshold configuration data is described in the following table. Column Number Column Name Description Default Value 1 Exist Status of the Threshold in the SPOTS RT Database. Allowable Values: YES – This threshold is present in the SPOTS Database NO – This threshold is not present in the SPOTS Database. NO 2 Object Name of the Object Class. Must be a valid SPOTS Object Class. Allowable Values: Alphanumeric Characters (0…1, a….z ,A…Z,-,_) Maximum character count = 255 characters. Automatically defined by SPOTS when exporting CSV. 3 Measurement Name of the measurement. If Virtual Counter, place an ‘-‘ character. Must be a valid Measurement for the Object Class specified in column 2. Only the Measurement name used in the GUI is relevant, the versions are not important for the RT database. Allowable Values: Alphanumeric Characters (0…1, a….z, A…Z,-,_) Maximum character count = 255 characters. Automatically defined by SPOTS when exporting CSV. 4 Counter Name of the Counter. If Virtual Counter, place an ‘-‘ character. Must be a valid counter for the Measurement specified in Automatically defined by SPOTS when exporting 34 E200301-01-514-V10.0I-02
  35. 35. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. column 3. Allowable Values: Alphanumeric Characters (0…1, a….z, A…Z,-,_) Maximum character count = 255 characters. CSV. 5 VirtualCounter Name of the Virtual Counter. If it’s not a virtual counter, place the ‘-‘ character. Must be an existing virtual counter for the Object Class specified in column 2. Allowable Values: Alphanumeric Characters (0…1, a….z, A…Z,-,_) Maximum character count = 255 characters. Automatically defined by SPOTS when exporting CSV. 6 Threshold Name Threshold Name. Allowable Values: Alphanumeric Characters (0…1,a….z, A…Z,-,_) Maximum character count = 255 characters. Automatically defined by SPOTS when exporting CSV. 7 Severity Severity Value. Allowable Values: “WARNING”, “MINOR”, “MAJOR”, “CRITICAL” “MINOR” 8 Activation State Activation State of the Threshold. Allowable Values: “ON”, “OFF” “OFF” 9 Value Threshold activation value. Allowable Values: Double (from –9999999,99 to 9999999,99). –9999999,99 10 Clear Percentage Threshold clear percentage value. Allowable Values: 0 to 100. 0 11 Cross Direction Threshold trigger cross direction. Allowable Values: “UP”, “DOWN” “DOWN” 12 Monitoring Period List Threshold Monitoring Period List. Format of the list: start=start time.end=end time| start=start time.end=end time|…| start=start time.end=end time A Monitoring period entry is defined by two values, the start and end times. The times are filled in the start time and end time string sections. The format of the time is hh:mm. 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, i.e., no time overlaps between consecutive days are allowed. Consecutive monitoring periods can be added to the list by using the character ‘|’ as list separator. If no Monitoring periods are defined, then the character “-“ should be placed. Allowable Values: The hh field is a two-digit integer with range from 00 to 23. The mm field is a two-digit integer with range from 00 to 59. “-“ E200301-01-514-V10.0I-02 35
  36. 36. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 13 Object Black List Threshold Object Black List. Format of the list: /Domain@MOI|/Domain@MOI|…|/Domain@ MOI An Object that is part of the Black List is defined by the Domain of the object and by its MOI designation (Managed Object Instance. Each Object that is part of the Black List must have a Domain and a MOI. Consecutive Black List Objects can be added to the list by using the character ‘|’ as list separator. If no Objects are to be declared, place the “-“ character. Allowable Values: Each Domain and MOI field can be composed of Alphanumeric Characters (0…1, a….z, A…Z,-) Maximum character count = 255 characters. “-“ 14 Reference Counter Reference Counter for the current threshold. 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 Measurement can be specified. If the Threshold is related to a Virtual Counter, then the Reference 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. Allowable Values: Alphanumeric Characters (0…1, a….z, A…Z,-,_) Maximum character count = 255 characters. “-“ 15 RC Compare Value Reference Counter Compare Value for the 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: from –9999999,99 to 9999999,99. –9999999,99 16 RC Cross Direction Reference Counter Cross Direction. If no Reference Counter is to be defined for this Threshold, then the value “DOWN” should be present in this column. Allowable Values: “UP”, “DOWN” “DOWN” Note: Default values are set by SPOTS when exporting thresholds to CSV in case the Threshold does not exist on the SPOTS RT Database. Tips to modify the CSV file contents: - The export action uses the ';' as default separator (',' is already used in numbers). If when opening the CSV file with Excel the different columns appear all in the same column go to the Control Panel and change in the Regional Settings/Number the List Separator to ‘;’. - Do not modify the first line in the file. - Exist flag values need to be inserted in capital letters. 36 E200301-01-514-V10.0I-02
  37. 37. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.6.5.4.3 Import Threshold Values To import Threshold Values from an external CSV file the user can select the Import Thresholds option under the Thresholds menu. After selecting this option the following window is displayed. Pressing the Browse button select the CSV filename file to import. Select options Overwrite and/or Simulate and/or Verbose using the check boxes and according to the following: Option Description with Overwrite - new Thresholds in CSV (Flag Exist set to “YES”) are created in the DB - deleted Thresholds in CSV (Flag Exist set to “NO”) are deleted in the DB - modified Thresholds in CSV are modified in the DB without Overwrite - new Thresholds in CSV (Flag Exist set to “YES”) are created in the DB - deleted Thresholds in CSV (Flag Exist set to “NO”) are NOT deleted in the DB - modified Thresholds in CSV are NOT modified in the DB E200301-01-514-V10.0I-02 37
  38. 38. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) Simulate Quicker way to see the impact of the CSV file import in the DB without changing it. This action proceeds with the CSV loading process without effectively updating the SPOTS DB Verbose Prints all the CSV lines modified Press the Import button to go on with the Import action. Press Cancel to abort the action. During the Import action an ‘Operation in Progress’ window is displayed showing the phase in which the action is. In the end of the Import action the following window is showed. In this case the import was successful, no errors occurred during the operation. If there are errors in the CSV file the import action will discard the lines (thresholds) where the syntax is not correct. Please also note that the lines in the CSV file are treated one by one and in the sequence in which they are in the file. This means that a subsequent line (threshold) in the file can replace a previous threshold in case the ‘Overwrite’ option is selected. 38 E200301-01-514-V10.0I-02
  39. 39. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The following window illustrates a situation where there were errors during the Import: - A line was not parsed due to syntax errors (invalid Exist flag). - Two thresholds for the same measurement and counter pair were defined with the same severity (CRITICAL) in the CSV file. The consequence is that only the last threshold was added to the SPOTS database. The SUMMARY area: Lines read from CSV file: all the lines in the CSV file Parsed Thresholds: all the lines in the CSV file except the Header and all the discarded lines due to syntax errors Created Thresholds: number of thresholds created in the database Overwritten Thresholds: number of thresholds overwritten in the database Thresholds not updated: number of thresholds that exist in the database but were not overwritten Thresholds Deleted: number of thresholds deleted in the database E200301-01-514-V10.0I-02 39
  40. 40. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) Regarding the descriptions that appear in the LOG area of the previous figures, some types of errors can be considered: - Modification of not allowed fields (e.g. ‘Counter’) - Addition of objects to the ‘Object Black List’ using a wrong separator - Missing column values - Modification of the field ‘Reference Counter’ to use as Reference Counter Name the own ‘Meas:Counter’ name - Modification of the ‘Severity’ in a Counter to a new severity already existing - Addition of two thresholds in the same Counter but in these thresholds there are two different ‘Reference Counter’ names - Usage of an invalid ‘Exist’ flag (e.g. ‘yes’ – without capital letters) 3.6.5.4.4 Delete All Threshold Values To delete all the Threshold Values in the SPOTS database the user can select the Delete All Thresholds option under the Thresholds menu. 3.6.6 Agency Management Tab The SPOTS RT Agents are software agents that are loaded into the SPOTS RT Agencies (RTA) to perform the necessary alarm monitoring tasks in an efficient, distributed and scalable way. The SPOTS Real-Time system can collect data from several NEs. For each data type supported, there is one Agent Type. We suggest running different agent types in different SPOTS RT Agencies (but this is not a limitation, different types of agents can run in the same agency). These RTAs are the support platforms for the SPOTS RT Agents to perform its tasks. The relation between the number of agencies running and the number of agents running on these agencies should be based in the required performance for the data processing. A particular restriction is that only one agent of the same type can run in the same agency. Please note that for each agency running the memory size is limited. And all the agents running there share this memory size. In the following we are assuming that one agency per data type is registered, meaning that only one agent is running in one agency, according to: Agent types Agency name CS CS_Agency ST ST_Agency HI HI_Agency Q3 Q3_Agency SNMP SNMP_Agency UTRAN UTRAN_Agency BR_OMCB BR5_Agency BR_RC BR6_Agency 40 E200301-01-514-V10.0I-02
  41. 41. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. GGSN C_GGSN_Agency MSP MSP_Agency The Agency Management Tab provides the means to administer the SPOTS RT Agencies and Agents. In order to have the SPOTS RT functionality working properly, the user must first configure the several RT Agencies and RT Agents on the system. Before going any further, the user must assure that the Agency to register was properly installed following the SPOTS RTA Installation Guide. To register an Agency in the SPOTS RT system the user must select the Register Agency function from the Agency pull-down Menu. E200301-01-514-V10.0I-02 41
  42. 42. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) The user must then provide the required information to the Register Agency window. Name: Identification of the Agency in the SPOTS RT database. Host: SPOTS RT Agency host name or IP address. The Register button saves the new Agency object in SPOTS RT database. If the host is unknown this action is discarded. When a new Agency is registered the system tries to start it automatically. The Cancel button discards all the modifications. The left-side window of the Agency Management Tab presents the list of all the registered Agencies under the Agencies Root icon. The icon represents each Agency registered on the database. The right-side window of the Agency Management Tab presents the detailed information about the Agency selected on the left-side Agencies list. 42 E200301-01-514-V10.0I-02
  43. 43. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. Beside the Agency’s Name and Host information, this window presents the Agency State and Agency Automatic Start. An Agency may be in one of three states, as seen from the server: Agency State Description ON An Agency is ON when the Agency process is running on the SPOTS RTA host and the server can monitor its behaviour. OFF An Agency is OFF when the Agency process is not running on the SPOTS RTA host and the server can monitor its behaviour. DOUBT An Agency is in DOUBT when the server cannot monitor its behaviour, because the Agency host is not accessible in the network. The Agency Automatic Start field shows if the RT Server should automatically start the selected Agency. The RT Server will try to start agencies that the user has asked to start but, by some reason, are currently stopped. To manage a selected Agency registered in the system, the user may use several functions provided in the Agency pull-down Menu. All these functions, except the Register Agency one, are also available by using the right-side mouse button while selecting an Agency from the list. Agency Management functions: Register Agency Register a new Agency on the database. Unregister Agency Unregister a selected Agency from the database. This means deleting all references of this Agency from the database. Start Agency Start the selected Agency process on the Agency host. Besides starting the Agency, this function also stores in the database the information that this Agency must be automatically started the next time the SPOTS RT Server is restarted. This function is only available if the Agency is in the OFF state. Stop Agency Stop the selected Agency process on the Agency host. Besides stopping the Agency, this function also stores in the database the information that this Agency must not be automatically started the next time the SPOTS RT Server is restarted. This function is only available if the Agency is in the ON state. Start Agents of this Agency Start all Agents registered on the selected Agency. This function is only available if the Agency is in the ON state. Stop Agents of this Agency Stop all Agents registered on the selected Agency. This function is only available if the Agency is in the ON state. E200301-01-514-V10.0I-02 43
  44. 44. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) Important Note All the previous functions need the particular SPOTS RT Agency host to be accessible in the network and also need a specific SPOTS RTA daemon to be running on the Agency host machine. For more information about the Agency host configuration please refer to the SPOTS RTA section in [5]. Also note that the agencies registered in the RTC to be properly used must be configured in a configuration file described in the ‘Configuring real_time.cfg files’ section in [5]. Agent Management The last step in the SPOTS RT Agency configuration procedure is the registration and start of the actual SPOTS RT Agents. To register an Agent in the SPOTS RT system the user must select the Register Agent function from the Agent pull-down Menu. The user must then provide the required information to the Register Agent window. Name: Identification of the Agent in the SPOTS RT database. Agent Type: Type of the Agent. For this SPOTS RT version the CS, ST, HI, Q3, SNMP, UTRAN, BR_OMCB, BR_RC GGSN and, MSP types are supported. Agency: Identification of the Agency platform on which the Agent shall be registered. Primary Domain: The Primary Domain this Agent will monitor. The Register button saves the new Agent object in SPOTS RT database. The Cancel button discards all the modifications. The left-side window of the Agency Management Tab presents the list of all the registered Agents under their Agencies. 44 E200301-01-514-V10.0I-02
  45. 45. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The icon represents each Agent registered on the database. The right-side window of the Agency Management Tab presents the detailed information about an Agent when it is selected on the left-side Agents list. Beside the Agent’s Name, Type, Agency and Domain information, this window presents the Agent State and Agent Automatic Start. An Agent may be in one of three states, as seen from the server: Agent State Agent Icon Description Running An Agent is Running when the Agent process is running on the SPOTS RT Agency host and the server can monitor its behaviour. Off An Agent is OFF when the Agent process is not running on the SPOTS RT Agency host and the server can monitor its behaviour. Doubt An Agent is in DOUBT when the server cannot monitor its behaviour, because the Agency host is not accessible in the network. E200301-01-514-V10.0I-02 45
  46. 46. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) Users can quickly find out the state of all defined agents by looking to the agent icons. A green circle over the agent icon means the agent is running, a yellow circle means the agent is in doubt and a red circle means the agent is stopped. The Agent Automatic Start field shows if the RT Server should automatically start the selected Agent. The RT Server will try to start agents that the user has asked to start but, by some reason, are currently stopped. To manage a selected Agent registered in the system, the user may use several functions provided in the Agent pull-down Menu. All these functions, except the Register Agent one, are also available by using the right-side mouse button while selecting an Agent from the list. Agent Management functions Register Agent: Register a new Agent on the database. Unregister Agent: Unregister a selected Agent from the database. This means deleting all references of this Agent from the database. Start Agent: Start the selected Agent process on its Agency. Besides starting the Agent, this function also stores in the database the information that this Agent must be automatically started the next time the SPOTS RT Server is restarted. This function is only available if the Agent is in the OFF state and its Agency is ON. 46 E200301-01-514-V10.0I-02
  47. 47. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. Stop Agent: Stop the selected Agent process on its Agency. Besides stopping the Agent, this function also stores in the database the information that this Agent must not be automatically started the next time the SPOTS RT Server is restarted. This function is only available if the Agent is in the ON state. Change Primary Domain: Change the domain assigned to this Agent. This function is only available if the Agent is in the OFF state. 3.6.7 Agent Type Management Tab The SPOTS Real-Time platform is prepared to support different types of Agents, performing different tasks on different types of PM collected data. The left-side window of the Agent Type Management Tab presents the list of all the supported Agent Types. The icon represents each Agent Type supported. For this SPOTS RT version, CS, ST, HI, Q3, SNMP, UTRAN, BR_OMCB, BR_RC, GGSN and MSP are the Agent Types supported. To manage a selected Agent Type, the user may use several functions provided in the Agent Type pull-down Menu. All these functions are also available by using the right-side mouse button while selecting an Agent Type from the list. E200301-01-514-V10.0I-02 47
  48. 48. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) Agent Type Management functions Start Agents of this Type: Start all Agents registered in the system of the selected Agent Type. Besides starting each Agent, this function also stores in the database the information that the Agent must be automatically started the next time the SPOTS RT Server is restarted. This function only affects the Agents that are in the OFF state and its Agency is ON. Stop Agents of this Type: Stop all Agents registered in the system of the selected Agent Type. Besides stopping each Agent, this function also stores in the database the information that the Agent must not be automatically started the next time the SPOTS RT Server is restarted. This function only affects the Agents that are in the ON state. Upgrade Agents of this Type: If there is the need for upgrading the functionality of the Agents of one type (CS, ST, HI, Q3, SNMP, UTRAN, BR_OMCB BR_RC, GGSN or MSP) this function allows the administration user to perform this task in an easy way. When this function is used, the system will stop all Agents of the selected type and perform the upgrade. To start the upgraded Agents again, the user may use the “Start Agents of this Type” function. If the SPOTS RT server is restarted right after the upgrade, all the Agents that were running before the upgrade will be restarted automatically. For details about the Agents Upgrade procedure please see the SPOTS RT Server section in the RT Installation Guide. The left-side window of the Agent Type Management Tab presents the list of all the registered Agents of each Agent Type. The right-side window of this Tab presents the detailed information about an Agent when it is selected on the left-side Agents list. 48 E200301-01-514-V10.0I-02
  49. 49. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.6.8 History Log Panel The lower part of the application window is reserved to the History Log Panel. In this panel the user can see messages sent by agencies and agents. Messages in the History Log Panel are always sorted by date, with the most recent messages being on top. This provides the user a way of always having the most recent messages present. The following data fields compose the Log: • Log Type – Informs the user if an agency or an agent has generated this log message. • An agency icon will represent a log message generated by an agency ( ). • Log messages generated by Agent will be represented by the agent icon ( ). E200301-01-514-V10.0I-02 49
  50. 50. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) • Type – 4 types of messages can be generated: • Positive Reactive ( ) – Messages indicating that an action triggered by the user was successfully executed. • Negative Reactive ( ) – Messages indicating that an action triggered by the user failed. • Positive Warning ( ) – Messages triggered by a warning event which were successful. • Negative Warning ( )– Messages triggered by a warning event which failed. • Date – The date and time the message was generated. • Agency – The agency that issued the message. • Agent Type – The type of the agent that generated the message. Empty if the message was generated by an Agency. • Description – A short description of the event being reported. The user can choose to clear the log, to recall some older messages or to filter the logs of a specific agency, using a popup menu that appears when clicking with the right button on the Log Panel. 3.6.9 RT Log Viewer in Windows environment As only one can user can use the RT Client at the same time, the Log Viewer Panel can be used as a separate application, without any restrictions on the number of simultaneous users. This will enable a larger set of users to monitor the behaviour of the RT system. The Log Viewer can be started just like the RT Client but the user must press the Spots Real Time Log Viewer option instead of the Real Time Client one. 50 E200301-01-514-V10.0I-02
  51. 51. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.6.10 RT Log Viewer in Solaris environment To start the RT Log Viewer perform the following commands: - go to the RTA installation directory. In case in the RTA installation the default path was accepted this installation directory is /opt/spots/rt. Otherwise it is the installation path selected by the user. cd /opt/spots/rt - execute the command logmonitor E200301-01-514-V10.0I-02 51
  52. 52. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.7 SPOTS LT User Interface – Utils 3.7.1 Alarm Notification SPOTS RT Performance Alarming automatically detects quality of service problems and alerts the operator about performance degradations of the network. It reduces significantly the reaction times to fix performance problems. If an alarm is received during a user's normal work, a flashing icon (and sound) on the status bar (bottom of the SPOTS PMC window) will alert the user to the incoming alarm. By moving the mousse above the alarm-flashing icon, the number of new incoming alarms is showed. If the user clicks on this icon, the Alarm Browser pops up with detailed information on the alarm so that the user can immediately start to search for the problem. Each user can configure the SPOTS Alarm Notification according to his/her preferences, via the menu option Spots - Preferences.... The user enables/disables several SPOTS features by checking/clearing the corresponding check boxes. The following SPOTS reports features can be enabled/disabled: Automatic start of the report wizard upon creation of a new report; Automatic execution of a report upon exiting the report wizard. The following SPOTS Alarm features can be enabled/disabled: Automatic notification of user upon reception of an alarm. This notification is done by blinking the alarm icon; Automatic notification of alarm reception by the emission of a sound. 52 E200301-01-514-V10.0I-02
  53. 53. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The SPOTS Alarm Notification can be also configured via the pop-up menu that appears when right clicking on the alarm icon. These features (flashing icon, sound notification) can be enabled/disabled by checking/clearing the corresponding check boxes. 3.7.2 Alarm Browser It is possible to read all existing Alarms either by: Using the Alarm button on the lower right corner of SPOTS client main window; Selecting SPOTS - Utils - Alarm Browser from the task tree. The Alarm Browser window is displayed, containing all existing alarms: The details of the selected alarm are displayed in the lower part of the Alarm Browser window. The status of each alarm is cleared when the corresponding details are read. E200301-01-514-V10.0I-02 53
  54. 54. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) When an alarm is received for a non-existing object, it is automatically displayed but it is not stored in the SPOTS database. These alarms are discarded every time a refresh occurs, thus cleared from the browser. Window Operations Refresh the window, removing all alarms associated with non-existing objects. Invokes the Alarms Filter window. Resets the filter on the list of alarms. Print a report of all existing alarms. Print-preview of the report of all existing alarms. Create a TEVL Chart Report with the selected alarm. Create a RT Bar Chart Report with the selected alarm. 3.7.2.1 Alarm Browser options At any time, the user can refresh the Alarm Browser contents, thus the Alarms table is updated with all alarms stored in the database. The alarms information and quantity presented is configurable via the Task - Options menu option, available when the Alarm Browser window is presented. By default all alarms information is presented, thus all table columns are checked. The number of alarms visible is set to All by default. The maximum number of alarms stored in the SPOTS Database is 1000. 3.7.2.2 Alarms Filter In order to avoid overloading the Alarm Browser with all existing alarms, the user may define filters to reduce its scope. The toolbar set filter button invokes the Alarms Filter window: 54 E200301-01-514-V10.0I-02
  55. 55. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. You may filter the alarms by: Time – allows the selection of the beginning and end date and time; Type or Object Class - allows the selection of either the measurement type or the object class; Severity – allows the selection of several severity levels; Object – allows editing the object name, using wild cards or the selection from a list of Instances. Window Operations Applies the defined filter on the Alarm Browser and closes window. Closes window without applying the filter settings since last use of the Apply button. Applies the specified report properties without closing the window. This button is enable some changes occurred. Window Attributes Time Specification of the date time interval. Type Measurement type of the alarm that shall be presented Object Object class of the alarm that shall be presented Class Severity Degree of severity to consider Object Network resource to inspect E200301-01-514-V10.0I-02 55
  56. 56. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) When you choose to filter the alarms by object and click on the Browse... button a ‘Select Objects’ window like the following will appear: You may choose the domain and the associated instances. You can select one or more filtering conditions and set them with the Apply button. Now only the alarms that accomplish the selected conditions are visible on the Alarm Browser. You may reset the filter through the Reset Filter button on the toolbar. 3.7.2.3 PM Reports driven by Alarm The main idea of the PM Reports driven by alarm is to provide very specialised reports for rapid detection of network problems. These new reports are seen as part of a decision oriented workflow, providing a global view of the behaviour of a specific class of network resource. The reports called from the Alarm Browser present correlated metrics information in an intuitive graphical form and based on the values of performance data for the last time period for some specific counters. 56 E200301-01-514-V10.0I-02
  57. 57. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.7.2.3.1 TEVL Chart Report Within the Alarm Browser it is possible, for the selected alarm, to generate a time evolution report for the respective variable and object. The correlation between an alarm and the item on the time evolution is the following: where T1= T0 + 2 hours. The Alarm driven TEVL Chart Report is available by: clicking on the toolbar Launch Time Evolution Chart Report button; selecting Task - TEVL Chart Report from the client main menu; selecting TEVL Chart Report from the Alarm Browser pop-up menu. A TEVL Chart report appears presenting the evolution of the counter’s value for the time interval starting 2 hours prior to the alarm date and ending at the time the alarm was issued. The report is continuously updated with new incoming values each time interval, these new values are added to the report but the report start time is maintained. E200301-01-514-V10.0I-02 57
  58. 58. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.7.2.3.2 RT Bar Chart Report Within the Alarm Browser it is also possible to call a RT Bar-Chart report. This report provides an intuitive way of presenting the evolution of an indicator during some time periods (by default 4), as well as allowing the user to check for the behaviour of correlated metrics. The Alarm driven RT Bar Chart Report is available by: Clicking on the toolbar Launch RT Bar Chart Report button; Selecting Task - RT Bar Chart Report from the client main menu; Selecting RT Bar Chart Report from the Alarm Browser pop-up menu. A RT Bar Chart report appears presenting the value of the affected counter as well as some pre-defined correlated counters during the last 4 time intervals; the last interval presented corresponds to the time the alarm was issued: Note: The Bar Chart reports are available for a subset of all the counters provided by SPOTS. Consult [2] for a listing of all the Bar Chart reports available in the current SPOTS version and the respective sets of correlated counters. Attempting to invoke a Bar Chart report on a non-supported counter will yield an error message. 58 E200301-01-514-V10.0I-02
  59. 59. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The RT Bar Chart report displays information like the Maximum and Minimum values for each indicator displayed as well as the Threshold value for the affected counter. The report is continuously updated with new incoming values each time interval. These new values are added to the report but the only 4 time periods are presented, the older period of the report disappears. Note: The report’s refresh functionality can not be disabled for the reports called from the Alarm Browser. For specific details regarding each of the available RT Bar Chart Reports, please consult [2]. E200301-01-514-V10.0I-02 59
  60. 60. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.7.3 RT Monitoring Panels The “Monitoring Panel” is a very special report, dedicated to graphically monitor specific network objects (e.g., Nodes) that have critical conditions. These reports have 3 rows: “Nr. Affected Nodes”: the first row displays the number of Nodes that match the defined critical condition; “Aggr. Value (Affected)”: the second row displays the aggregated value (total or average) of the observed variable for all Node’s that match the defined critical condition and for the observation period. “Aggr. Value (Total)”: the third row displays the aggregated value of the observed variable, but for all Nodes on the network. Note: The scope of the Nodes seen in each Monitoring Panel is related to the user’s profile in terms of Domains. This report displays the values of a predefined set of indicators for two time intervals: • The Current value column (“C”): the time interval when PM data was last collected from the network; • The Maximum value column (“M”): the time interval when the performance indicator reaches its maximum/minimum value. The observation period is equal to 60 minutes and the Panel Reports are auto-refreshed. These Panels can be externalized. Figure 1 – Monitoring Panel The user can click on the mouse right-button to access the Report launching facility that calls a pre-defined report with the same performance indicators and assuming the parameters: • Requested objects: all exchanges that match the defined critical condition; • Time period: time where reference variable value is maximum/minimum. 60 E200301-01-514-V10.0I-02
  61. 61. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. The pre-defined reports associated with the Monitoring Panel are not accessible from the SPOTS LT - Reports Task tree. For specific details regarding each of the available Monitoring panels, please consult [2]. E200301-01-514-V10.0I-02 61
  62. 62. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 3.7.4 Refresh Functionality The current SPOTS version allows the refresh of Ad-hoc and pre-defined reports. Either via the “Report Wizard – Report Properties” or directly via the “Report Properties” windows the Refresh functionality can be configured. The refresh area is only enabled for reports if the following conditions are verified: Date interval Keyword “TODAY” is selected or - The end date is equal to the current day or - “Now” is selected Data Source - “Detailed” is selected. Example: It is possible to customize the start time delay and the refresh frequency. The start time delay is a relative value referenced to the full hour (e.g. 00:00). This parameter is important because it allows the minimization of the delay between the collection of new traffic data and its visualization. If new traffic data is loaded in a scheduled way every 5 minutes two minutes after the full hour, then the report start delay parameter should have the value 3. Behavior of the report’s Refresh functionality: 1- when the refresh option is selected then the report is executed normally with the refresh properties activated; 2- after the execution of the report, the STOP button stays active so that the report can be stopped; 2.1- If the STOP button is pressed, if the user wants to have the refresh feature active again on the stopped report then he must change the report’s properties and execute it again. 2.2- Otherwise, the STOP button stays active; 3- If any report’s refresh-related property is changed after the report has been executed once, then the report must be executed again, and the EXECUTE button is therefore enabled. 62 E200301-01-514-V10.0I-02
  63. 63. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. Important Notes: 1- For a better system performance it is advisable to select a refresh granularity equal or multiple of the data input granularity. For example, in reports with Q3 data, which has 15 minutes granularity, the refresh granularity should be set to 15 minutes, 30 minutes, 45 minutes, etc. Not less than that. 2- Using the same argument, in case of multiple reports in refresh, the “start time after full hour” value in each one, should be set to distinct values. 3- Whatever the refresh options are, if the report is refreshed more than 150 times and the result is always NO_DATA_AVAILABLE, then the refresh stops and an exception message is presented to the user. Report Wizard – Report Properties Report Properties E200301-01-514-V10.0I-02 63
  64. 64. Siemens S.A. User Manual - Real Time (SPOTS V10 Drop 4) 64 E200301-01-514-V10.0I-02
  65. 65. User Manual - Real Time (SPOTS V10 Drop 4) Siemens, S. A. 3.8 SPOTS SNMP Alarm Agent (SAA) 3.8.1 Overview The SPOTS SNMP Alarm Agent (SAA) component is an optional add-on to the SPOTS Real- Time functionality, allowing the forwarding of QoS alarms, generated by the SPOTS Real-Time application (see Section 2.3) to an external Fault Management application via SNMP. In generic terms, the SAA interface covers the following functionality: Forwarding of SPOTS alarms (based on ITU-T X.733) via SNMP traps (see Section 3.8.2); Filtering of alarms (see Section 3.8.3); Resynchronisation of pending performance alarms (see Section 3.8.4); Manual deletion of pending performance alarms (see Section 3.8.5). Additionally, an administration interface to control the various aspects of SAA functionality is provided (see Section 3.8.6). For the SPOTS SAA MIB definitions consult Annex 5.2. It is possible to establish a direct relationship between the basic interface functionality and SNMP operations, as represented at Figure 2 below: Alarm Notification SNMP TRAP Alarm Filtering SNMP SET Resynchronisation SNMP GET Table (list of all pending active alarms) Alarm Deletion SNMP SET (Note: the Alarm Filtering mentioned above refers to Global filtering policies, see Section 3.8.3.1; Additional filtering capabilities can be configured via SAA administration interface, see Section 3.8.3.2). Alarm notification (SNMP TRAP) Alarm Trap filter (SNMP SET) SPOTS FM Delete perf. alarm (SNMP SET) Alarm synchronisation (SNMP GET) Figure 2 - SAA interfaces to external FM Application The SPOTS SNMP Agent assumes: The SNMP manager knows the semantics of the traps parameters which are defined in the MIB (consult Annex Error! Reference source not found.). E200301-01-514-V10.0I-02 65

×