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 10.0 User Manual

307 views

Published on

Spots 10.0 User Manual

Published in: Education
  • Be the first to comment

  • Be the first to like this

Spots 10.0 User Manual

  1. 1. SIEMENS S.A. SPOTS V10 Drop 4 User Manual November/2003 E200301-01-114-V10.0I-03
  2. 2.  SIEMENS S.A. OG IC, R&D WON NM CP2 R. Irmãos Siemens, nº 1 2720-093 Amadora 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 172 pages. The information contained in this document is subject to change.
  3. 3. User Manual (SPOTS V10 Drop 4) Siemens S.A. Table of Contents 1 INTRODUCING SPOTS .................................................................................................................. 5 1.1 Overview............................................................................................................................................5 1.2 Environment ......................................................................................................................................8 1.2.1 Single Server Installation ..........................................................................................................8 1.2.2 Distributed Environment............................................................................................................9 1.3 Domains ..........................................................................................................................................11 1.4 User Access Control ........................................................................................................................15 1.4.1 User assignment to a SPOTS domain ....................................................................................16 1.5 PM Entities Concept ........................................................................................................................17 1.5.1 Sets of Objects........................................................................................................................17 1.5.2 Sets of Counters .....................................................................................................................18 1.5.3 Virtual Counters ......................................................................................................................19 1.5.3.1 Pre-defined Virtual Counters ..........................................................................................20 1.6 Internal data organisation ................................................................................................................21 1.6.1 Aggregation of Detailed Data ..................................................................................................21 1.6.2 Historical Data.........................................................................................................................21 1.6.3 Rule for Computing Aggregated Values..................................................................................22 1.6.3.1 Aggregation with extrapolation of missing values...........................................................23 1.6.3.2 Aggregation without extrapolation of missing values......................................................23 1.6.4 Algorithm for computing Historical Data..................................................................................23 2 INITIAL CONFIGURATION TASKS.................................................................................................... 25 2.1 Licensing .........................................................................................................................................25 2.2 Creation of User Groups..................................................................................................................26 2.3 Assignment of Users to Domains.....................................................................................................27 2.4 Creation of Domains ........................................................................................................................28 2.5 Automatic Nodes Creation...............................................................................................................29 2.6 Data Collection and Loading............................................................................................................30 2.6.1 Overview.................................................................................................................................30 2.6.1.1 Special recommendations for RAN environments ..........................................................31 2.6.1.2 Symbolic name handling in RAN environments..............................................................33 2.6.2 Configuring the SPOTS data collection...................................................................................34 2.6.2.1 File collection with Collector (SC, AC, OMC-B, RC and IPM environments) ..................34 2.6.2.2 File collection with dc_transfer (OMC-S environment)....................................................35 2.6.3 Configuring the SPOTS data loading ......................................................................................36 2.6.4 Scheduling SPOTS data collection and loading......................................................................36 2.6.4.1 Scheduling data collection from OMC-S.........................................................................36 2.6.4.2 Scheduling data collection from OMC-B.........................................................................37 2.6.5 Objects naming restrictions.....................................................................................................37 3 USER INTERFACE........................................................................................................................ 38 3.1 User Login .......................................................................................................................................38 3.2 Main Window ...................................................................................................................................40 3.3 Interaction........................................................................................................................................42 3.4 Modes of Operation .........................................................................................................................43 3.5 Scheduling tasks..............................................................................................................................44 3.6 Messages ........................................................................................................................................45 3.7 Printing ............................................................................................................................................46 3.7.1 Setting Page Properties ..........................................................................................................47 3.7.2 Previewing the Printout ...........................................................................................................49 3.8 Getting Help.....................................................................................................................................50 3.8.1 Getting help while working ......................................................................................................50 3.8.2 User Documentation ...............................................................................................................50 3.9 Objects filtering................................................................................................................................51 3.10 User preferences ...........................................................................................................................55 4 USING SPOTS …....................................................................................................................... 56 4.1 Network Resources .........................................................................................................................56 4.1.1 Configuring Network Nodes ....................................................................................................56 4.1.2 Configuring Software Versions................................................................................................59 4.1.3 Removing Network Resources................................................................................................61 E200301-01-114-V10.0I-03 i
  4. 4. Siemens S.A. User Manual (SPOTS V10 Drop 4) 4.1.4 Configuring Domains Structure ...............................................................................................62 4.2 Data Administration .........................................................................................................................64 4.2.1 Data Loading...........................................................................................................................64 4.2.2 Data Deletion ..........................................................................................................................67 4.2.3 Make History ...........................................................................................................................69 4.2.4 Data Aggregation ....................................................................................................................71 4.3 PM Entities ......................................................................................................................................73 4.3.1 Virtual Counters ......................................................................................................................73 4.3.1.1 Virtual Counters Wizard..................................................................................................76 4.3.1.1.1 Virtual Counters Wizard – Define Properties .........................................................76 4.3.1.1.2 Virtual Counters Wizard – Selecting Counters.......................................................77 4.3.1.1.3 Virtual Counters Wizard – Define Expression ........................................................80 4.3.2 Sets of Counters .....................................................................................................................82 4.3.2.1 Set of Counters Wizard ..................................................................................................85 4.3.2.1.1 Set of Counters Wizard – Define Properties ..........................................................85 4.3.2.1.2 Set of Counters Wizard – Selecting Counters........................................................86 4.3.3 Sets of Objects........................................................................................................................89 4.3.3.1 Set of Objects Wizard.....................................................................................................93 4.3.3.1.1 Set of Objects Wizard – Define Properties.............................................................93 4.3.3.1.2 Set of Objects Wizard – Selecting Objects ............................................................94 4.4 Utilities .............................................................................................................................................97 4.4.1 Scheduler................................................................................................................................97 4.4.1.1 Task Administration......................................................................................................100 4.4.2 Scheduler Browser................................................................................................................102 4.4.3 Users Domain .......................................................................................................................103 4.5 User Defined Tasks .......................................................................................................................105 4.6 Reporting .......................................................................................................................................107 4.6.1 Report size issues.................................................................................................................108 Refresh Functionality .....................................................................................................................109 Date interval........................................................................................................................109 Data Source........................................................................................................................109 4.6.3 Ad-Hoc Reports.....................................................................................................................112 4.6.4 SIEMENS Reports ................................................................................................................119 4.6.5 Custom Reports ....................................................................................................................120 4.6.6 Report Definition Wizard .......................................................................................................121 4.6.6.1 Report Definition Wizard – Define Date Interval and Data Source ...............................121 4.6.6.2 Report Definition Wizard – Selecting Objects...............................................................122 4.6.6.3 Report Definition Wizard – Selecting Counters ............................................................127 4.6.6.4 Report Definition Wizard – Define Extra Parameters ...................................................130 4.6.6.5 Report Definition Wizard – Define Report Properties ...................................................131 4.6.7 Class Browser.......................................................................................................................135 4.6.7.1 Class Browser – Selecting Objects ..............................................................................135 4.6.7.2 Class Browser – Selecting Counters ............................................................................136 4.6.8 Defining Report Properties....................................................................................................137 4.7 Reports Editor................................................................................................................................138 5 ANNEXES.................................................................................................................................. 140 5.1 SPOTS Commands .......................................................................................................................140 5.1.1 PMS commands for SAS ......................................................................................................141 5.1.1.1 Collector .......................................................................................................................141 5.1.1.2 dc_transfer ...................................................................................................................145 5.1.1.3 loader ...........................................................................................................................146 5.1.1.4 dbLoader ......................................................................................................................149 5.1.1.5 dbAggregator................................................................................................................150 5.1.1.6 dbRemover...................................................................................................................151 5.1.1.7 mkHistory .....................................................................................................................152 5.1.1.8 reporter.........................................................................................................................154 5.1.1.9 spotsShutdown.............................................................................................................158 5.1.2 PMS commands for SDS ......................................................................................................159 5.1.2.1 dbArchive .....................................................................................................................159 5.1.2.2 dbCalcStat....................................................................................................................160 5.1.2.3 dbHistoryAdm...............................................................................................................161 5.1.2.4 dbInfo ...........................................................................................................................162 5.1.2.5 dbObjectsPurge............................................................................................................163 5.1.2.6 setdbpwd ......................................................................................................................164 5.1.2.7 startDB .........................................................................................................................165 5.1.2.8 stopDB..........................................................................................................................166 5.1.2.9 changeObjNames.........................................................................................................167 ii E200301-01-114-V10.0I-03
  5. 5. User Manual (SPOTS V10 Drop 4) Siemens S.A. 5.1.2.9.1 Retrieving BTS Symbolic Names from OTS Core Database ...............................170 5.1.3 Generic SPOTS commands (PMS and PMC) .......................................................................172 5.1.3.1 spotsPing......................................................................................................................172 5.2 SPOTS Data Model .......................................................................................................................173 6 REFERENCES............................................................................................................................ 174 7 GLOSSARY AND ABBREVIATIONS................................................................................................ 177 List of Tables Table 1 – Supported Network Nodes and Network Management Systems .................................. 7 Table 2 – PM Data Types ............................................................................................................ 21 Table 3 – Functionality allowed to Normal Users and Administrators......................................... 26 Table 4 – Configuration actions for Network Nodes and Network Management Systems ......... 31 Table 5 – File types retrieved by Collector ................................................................................ 143 Table 6 – Report File Names..................................................................................................... 155 E200301-01-114-V10.0I-03 iii
  6. 6. User Manual (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 mandatory application part, that is, the Long-Term part. The description of the SPOTS V10 Drop 4 Real-Time application is provided in [24]. Architecture The SPOTS system was design based on a three-tier scalable architecture, comprising the following functional components for the Long-Term part: SPOTS PMC • Client component, implementing the application graphical user interface. SPOTS PMS • Application Server, implementing all the application business logic. • Database Server, implementing the data repository. All SPOTS installable components are distributed via the SPOTS CD-ROM distribution media. E200301-01-114-V10.0I-03 5
  7. 7. Siemens S.A. User Manual (SPOTS V10 Drop 4) Software Functions The current version supports the following functions: • State of the art Java2 graphical user interface. • High-performance Oracle 8i database for storage of PM data. • Easy visualisation of PM data on table and chart formats. • PM data report output in Excel 2000. • Useful pre-defined PM reports. • Integration of user defined reports. • Export of PM data table reports to Excel, HTML and PDF formats. • Export of PM data chart reports to RTF, HTML and PDF formats. • Scheduling of tasks. • User access control. • Complex entities (Virtual Counters, Set of Counters, Set of Objects). • Management Domains. 6 E200301-01-114-V10.0I-03
  8. 8. User Manual (SPOTS V10 Drop 4) Siemens S.A. • Collection, loading and processing of detailed PM data (including generation of historical data) is supported for the Network Node versions indicated in the following table. (Note: These are the Network Node versions, also called Network Element versions, that are defined in SPOTS; for details on the correspondence between these versions and the Siemens Network Release designations, consult Section 2.2.1 SPOTS Node Version Designations in [22]). Technology Domain Supported Network Management Systems Supported Network Nodes Software Versions @Vantage Commander HLRi: HI11 OMC-S Classic nodes: SR80, SR90 Classic nodes: SR80, SR90, SR100 Core Circuit Switching Innovation nodes: CS10, CS20, CS21 Core Signalling (STP) Switch Commander STP nodes: V13, V15 PS10, PS20, PS21 GPRS nodes: GR11, GR20, GR31 Core Packet Switching P021C Core Value Added Services IP Manager MSP30 GERAN Radio Commander BR60 (covering BR6.01 and 6.02), BR70 Radio Access OMC-B BR50, BR55 UTRAN Radio Access Radio Commander UMR2x, UMR30, NB1P, NB2P (RNC, NodeB 1st and 2nd platforms) Table 1 – Supported Network Nodes and Network Management Systems • Processing of historical data is supported for all Network Node versions indicated in the above table, plus additionally SR60 and SR70 (support of SR6.0 and SR7.0 nodes applies only to data migrated from Databases of previous SPOTS versions). E200301-01-114-V10.0I-03 7
  9. 9. Siemens S.A. User Manual (SPOTS V10 Drop 4) 1.2 Environment SPOTS has been designed for high scalability: • all services are multi-threaded, providing an optimum scalability regarding the number of system processors; • the data storage can be distributed across several systems for better performance regarding the data access; • the application services can be distributed across several systems for better performance regarding the data processing. This provides a great breakthrough in ability for SPOTS to handle all network sizes. Currently two configuration types are available: the Single Server and Multiple Server configu-rations. These Server configuration types will now be described. Only the SPOTS Long-Term part components shall be considered - the choice of Real-Time part configurations (if real-time applies) is covered in Section 1.2 (Environment) in [24]. 1.2.1 Single Server Installa tion In a single server installation, all SPOTS PMS components are installed in the same target system. The SPOTS PMC can be installed in any workstation across the network, from where it accesses the server. Refer to the SPOTS Installation Guide ([21]) for information on the installation procedure. Note: It is possible to install the SPOTS PMC on the same system as the SPOTS PMS. However, due to performance reasons, intensive usage of the SPOTS PMC in this configuration (e.g. for frequent execution of performance reports) is not recommended. In a normal operation environment, this SPOTS PMC configuration is suitable only for sporadic actions (e.g. administrative actions). The picture below shows a SPOTS single server installation on a Switch Commander environment (this picture is provided only as an example - other NMSs are not considered): 8 E200301-01-114-V10.0I-03
  10. 10. User Manual (SPOTS V10 Drop 4) Siemens S.A. After installing the software, and before operating with SPOTS, the user must perform several configuration tasks (see Chapter 2). 1.2.2 Distributed Environment For big networks (with a significant number of nodes to manage), the amount of generated PM data to store and process is enormous; thus, the use of a single server installation has several limitations: • the required database performance is not acceptable for medium range servers; • the processing capabilities of the SPOTS Application Server (SAS) would not cope with the demands. To avoid these problems, it is necessary to configure a multiple server environment, where: • PM data is distributed through various SPOTS Database Servers (SDSs); • report processing load is distributed by several SASs. Based on this approach, it is suggested to distribute the whole network load through various management domains or regional centres and, for each centre, to distribute load through dedicated application and database server(s). A National Management Centre, from where all network information shall be available, may be created with the responsibility for the required network wide analysis. It is possible to create a hierarchy of regional management centres with the responsibility to collect PM data and perform analysis for the nodes within the scope of the region. The picture below shows a SPOTS distributed installation on a Switch Commander environment (this picture is provided only as an example - other NMSs are not considered): E200301-01-114-V10.0I-03 9
  11. 11. Siemens S.A. User Manual (SPOTS V10 Drop 4) In all management centres it is possible to install the complete set of SPOTS PMS components, in the same system or distributed across various servers, thus distributing system load. The exception is the SNS that shall be installed only once in the network. Refer to the SPOTS Installation Guide ([21]) for information on the installation procedure. 10 E200301-01-114-V10.0I-03
  12. 12. User Manual (SPOTS V10 Drop 4) Siemens S.A. 1.3 Domains A (network management) domain is a logical entity that denotes a group of Network Nodes. The concept of domain is useful for two complementary purposes: • providing the means to distribute the data and processing demands across multiple systems; • providing the means to restrict the network view for the users. The figure above shows a typical partitioning of a network in three domains: North, Middle and South. The Middle domain is itself partitioned in two sub-domains: MiddleE and MiddleW. The hierarchical organization of domains forms a network tree. The network tree is held in memory on a special PMS where the SNS component is installed. On multiple server installations the SPOTS administrator may assign different SDSs to different domains, the so-called Primary Domains. He can further partition the network by assigning groups of nodes to different Sub-domains. Primary Domains can be grouped in Network Domains, the highest hierarchy level in the domain’s structure, to which nodes can’t be directly assigned. A network tree configuration file describes the domain’s hierarchy, the assignment between Primary Domains and SDSs and the contained Sub-domains. A domain configuration file must be associated with each SAS. A Cluster is a SPOTS hardware and software complex containing: • one or more SPOTS Clients; • one SAS; • none, one or several SDSs. There is no hierarchical relation between Clusters. The way the Cluster’s components are inter-connected is described by the network tree configuration. Typically the SAS will be connected only to the Cluster's SDS(s). However, it is possible to set-up an SAS to access database servers from other Clusters. E200301-01-114-V10.0I-03 11
  13. 13. Siemens S.A. User Manual (SPOTS V10 Drop 4) The figure below exemplifies the relation between domains and Clusters. The overall network tree is only known by the SNS. The SPOTS location services of each Cluster (SAS) will use the SNS to gather information about the domain’s hierarchy that the SAS must manage. 12 E200301-01-114-V10.0I-03
  14. 14. User Manual (SPOTS V10 Drop 4) Siemens S.A. The next picture shows how the above management domain’s tree can be physically spread across several servers (in this example, each system represents a Cluster). The mapping between physical and logical distributions is specified in file domain.cfg of each SAS system, stored in the $SPOTS_DIR directory of the SAS (refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DIR and other SPOTS environment variables). The domain.cfg files map the Primary domains to the respective database servers (SDSs). The SDS IDs used in the files have to be the same as the names given to the property “ServerID” on the SDS configuration file “sds.cfg”. If no “ServerID” property is declared on a SDS, the used SDS ID shall be DS@SDS host, where SDS host is the own host name configured on the SDS system (either a simple UnixTM host name, e.g. machineA, or a fully qualified domain name, e.g. machineA.siemens.com). Examples: “domain.cfg” of Machine A domain Root { domain North DS@machineA.siemens.com }; E200301-01-114-V10.0I-03 13
  15. 15. Siemens S.A. User Manual (SPOTS V10 Drop 4) “domain.cfg” of Machine B domain Middle DS@MachineB.siemens.com { domain MiddleW; domain MiddleE; }; “domain.cfg” of Machine C domain South DS@MachineC.siemens.com 14 E200301-01-114-V10.0I-03
  16. 16. User Manual (SPOTS V10 Drop 4) Siemens S.A. 1.4 User Access Control In order to use SPOTS, any user must: 1. be defined as an Operating System user of (one of) the SAS system(s), 2. belong to a well defined Operating System user-group of that SAS system, and 3. be assigned to at least one of the existing SPOTS domains. The first two rules can be achieved using the UnixTM user administration facilities. The third rule can be achieved using the SPOTS Cluster configuration facilities. An Application Server can only accept sessions for SPOTS users registered according to the men-tioned rules. The user ID is considered to be unique for the complete SPOTS installation. Once a user gains access to an SAS, he only sees the network tree configuration of that server. Therefore, the SPOTS user privileges are defined according to: • user-group: the user must belong to one of the following UnixTM user groups: − pmuser (the SPOTS regular user); − pmadmin (the SPOTS administrator). • domain: the user must be registered at least in one of the existing SPOTS domains. The User Access Control configuration is specified in file users.cfg, stored in $SPOTS_DIR and maintained by each SAS (refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DIR and other SPOTS environment variables). This file contains the list of users that have access to the SAS Primary Domain or one of its contained Sub-domains. This information is provided to the SNS by each SAS, as part of the domain configuration. E200301-01-114-V10.0I-03 15
  17. 17. Siemens S.A. User Manual (SPOTS V10 Drop 4) 1.4.1 User assignment to a SPOTS domain An Operating System user, either assigned to the pmadmin or pmuser user groups, can’t use SPOTS GUI before being assigned to a certain SPOTS domain. The definition of the SPOTS domain tree and user assignment to a SPOTS domain is done within the SPOTS GUI, using the Domains Configurator (see Section 4.1.4) and the Users Domain (see Section 4.4.3) tasks respectively. The local spots user (or another SPOTS Administrator whose access has been granted before) must perform these tasks. As soon as the SPOTS domain’s structure is defined, the new users can be assigned to a domain. This assignment is registered, for the Cluster SAS, in the users.cfg file, stored in $SPOTS_DIR, like: John / Kevin /North Steven /Middle Karl /Middle/MiddleE Marie /Middle/MiddleW Julie /South For a better understanding of the concept behind, let us now closely follow the authentication steps: • User Steven logs on the SPOTS Client application (SCL) with user name and password; • SCL sends the login information to the SNS. • SNS returns the address of the SAS where the user was found. • SCL requests a session (with the returned SAS) using the login info. • SAS authenticates the user on the Operating System, determines the user privileges (based on the user-group), checks that the user belongs to an existing domain on its scope and returns the session identification. It is possible to administer the same user on distinct application servers. In this case the SNS will return multiple SAS addresses and it is up to the user to select the one where he/she wants to log in. 16 E200301-01-114-V10.0I-03
  18. 18. User Manual (SPOTS V10 Drop 4) Siemens S.A. 1.5 PM Entities Concept The processing of the Performance Management (PM) data is based on the concepts of PM counters and PM objects. Counters are variables provided by the telecommunications network to measure relevant aspects of the network behaviour, such as the occurrence and duration of specific events and activities, the usage of services and facilities, the occupation of resources and so on. Counters are logically grouped into SPOTS Measurements. The entities whose behaviour is being gauged by counters are the monitored PM Objects. These objects are instances of the object classes of the SPOTS object model. In a given SPOTS measurement, all counters refer to objects of the same object class i.e. one Measurement applies to a single Object Class. PM entities other than the PM objects and measurement counters can be used to extend the SPOTS reporting capabilities. The following entities are defined: Sets of Objects: user defined lists of objects from the same object class. A defined set of objects may be used as a macro to reference all the objects on the contained list or it may also be used to aggregate the contained objects into one virtual object. Sets of Counters: user defined lists of counters and/or Virtual Counters from the same object class. A defined set of counters may be used as a macro to reference all the counters and/or Virtual Counters on the contained list. Virtual Counters: arithmetical expressions used to combine counters and/or Virtual Counters into new PM indicators. The PM entities can be private or public: Private: can be used and managed only by the owner. Public: can be used by all users but managed only by users with administration privileges. PM Entities can be exported/imported to/from a file, thus enabling distribution of useful PM Entities within a SPOTS distributed environment. 1.5.1 Sets of Objects From the PM point of view, a network is a container of network resources. These resources have the ability to generate metrics at regular intervals that describe its characteristics in terms of traffic and performance. Within SPOTS the network resources are represented as objects. These objects may be grouped in Sets of Objects (SOO). Each SOO may be used to reference each single object within the scope of the defined set, or as a virtual object that represents all the objects within the scope of the set. From the user point of view, the SOO syntax is specified by the grammatical flow diagram below. E200301-01-114-V10.0I-03 17
  19. 19. Siemens S.A. User Manual (SPOTS V10 Drop 4) Instead of explicitly defining every object of the set, it is possible to use the following wildcards on the object names: • *: represents any sequence of alphanumeric characters. • ?: represents any alphanumeric character. Examples: MiddleETrunks = NE01:* MiddleWTrunks = NE07:* MiddleTrunks = SO!MiddleETrunks, SO!MiddleWTrunks Notice that: − MiddleETrunks is created in domain MiddleE; − MiddleWTrunks is created in domain MiddleW; − MiddleTrunks is created in domain Middle. 1.5.2 Sets of Counters Within SPOTS all metrics related with the network resources are represented as counters. These counters may represent raw measurements loaded from the Network Nodes or derived data calculated during the data load process. The counters can be grouped in Sets of Counters (SOC) that may be used to reference each single counter within the scope of the defined set. From the user point of view, the SOC syntax is specified by the grammatical flow diagram below. Example: TgrpCallMetrics = TGRP:CC_OO, TGRP:CC_IC, VC!TG_CC 18 E200301-01-114-V10.0I-03
  20. 20. User Manual (SPOTS V10 Drop 4) Siemens S.A. 1.5.3 Virtual Counters The counters may extend in runtime through the use of virtual counters (VC). Each VC represents an arithmetical formula that is computed in runtime. From the user point of view, the syntax of VC expressions is specified by the grammatical flow diagram below: where UnaryOp (Unary Operator): - ArithmOp (Arithmetical operators): +,-,*,/,^ BoolOp (Boolean operators): =,,,=,=,!= Function (available functions): MAX(expression, expression) MIN(expression, expression) IF(boolean_expression, expression1, expression2) Note: if the boolean_expression is 'true', then expression1 is returned; otherwise, expression2 is returned. GRANULARITY() Notes: • VCs can combine counters of different measurement types, as long as they belong to the same object class; • virtual counters apply to NEs whose release (version) supports the counters they use. This means that different NE instances, like for instance MSC, SGSN and HLRi instances, which are all modelled by object class EXCHOC (exchange) but belong to different NE versions, do not share the same virtual counters; however, when performing reports, the superset of all virtual counters for object class EXCHOC is available, and the user must select the ones that are appropriate to the NE in question. • Counters, for which there is no data, will be evaluated as “0” in additions and subtractions and as “1” in multiplications and divisions; however, when there is no data for all the counters, the expression yields “no data”. E200301-01-114-V10.0I-03 19
  21. 21. Siemens S.A. User Manual (SPOTS V10 Drop 4) Examples: VCname: TG_TV VCobject_class: XTPSG VCdescription:Traffic Volume of a Trunk Group VCexpression: TGRP:TV_OO+TGRP:TV_IC VCunit: ERL.S VCname: TG_CC VCobject_class: XTPSG VCdescription: Carried Calls of a Trunk Group VCexpression: TGRP:CC_OO+TGRP:CC_IC VCunit: NR VCname: TG_MHT VCobject_class: XTPSG VCdescription: Mean Holding Time of a Trunk Group VCexpression: TG_TV/TG_CC VCunit: SEC VCname: TG_TC VCobject_class: XTPSG VCdescription: Traffic Intensity of a Trunk Group VCexpression: TG_TV/GRANULARITY() VCunit: ERL 1.5.3.1 Pre-defined Virtual Counters A number of pre-defined virtual counters is supplied upon SPOTS installation in order to provide ready-to-use formulas for the computation of useful traffic indicators. The pre-defined virtual counters are visible to all users as public Virtual Counters in the SCL PM Entities → Virtual Counters task (see 4.3.1). For each virtual counter, its formula, unit, monitored object class and short description are provided. For further information consult Section 2.6 in [22]. 20 E200301-01-114-V10.0I-03
  22. 22. User Manual (SPOTS V10 Drop 4) Siemens S.A. 1.6 Internal data organisa tion The SPOTS data is organized in two logging tables: • Detailed Data; • Historical Data. The type of data stored in each of these logging tables and the methods used to load or generate it are described in the table below: Log Data description Data loading/generation method Detailed Data Raw PM data. The supported nodes generate PM data, typically with 15min granularity, which is loaded by executing the SAS loader command. It is also possible to generate Detailed Data, based on other imported or previously generated PM data, executing the SAS dbAggregator command or via the Data Aggregation task on the SCL. For more information see Section 1.6.1. Historical data Daily totals SPBH Daily Peaks All data contained in this log is generated either by the SAS mkHistory command or via the SCL task Make History, using as source for the calculations the PM data stored in the Detailed Data log. For more information see Section 1.6.2. Notice that both methods require at least 15min PM data to generate Historical data. When only 5min data is available, it is mandatory to execute the SAS dbAggregator command (or the SCL task Data Aggregation) prior to execute the mkHistory command (or the SCL task Make History). Table 2 – PM Data Types 1.6.1 Aggregation of Detailed Data Detailed Data, stored in the Detailed Data log, can be aggregated into a coarser granularity, thus improving the reports’ performance. The resulting Detailed Data is also stored in the Detailed Data log. Data aggregation is achieved by executing the SPOTS dbAggregator command or the Data Aggregation task (for details consult Section 5.1.1.5 or 4.2.4 respectively). For information on the algorithm used to compute the aggregated data values, consult Section 1.6.3. 1.6.2 Historical Data The analysis of evolution trends of the PM counters requires observation over long periods of time. The existence of detailed records (usually every 15 minutes) is not appropriate for this type of analysis. This would mean keeping in the Database an information volume of an unacceptable dimension, both due to the required amount of storage capacity and to the performance degradation in the access. E200301-01-114-V10.0I-03 21
  23. 23. Siemens S.A. User Manual (SPOTS V10 Drop 4) As an alternative, the significant indicators should be evaluated from the detailed data and only those (historical data) must be kept into the Database for long term. The resulting Historical Data is stored in the Historical Data log. The generation of historical data, based on the detailed data records, is achieved by executing the SPOTS mkHistory command or the Make History task (for details consult Section 5.1.1.7 or 4.2.3 respectively). For information on the algorithm used to compute the historical data values, consult Section 1.6.4. For pre-defined PM reports, if mkHistory is not executed prior to attempting execution either of Daily Totals or SPBH Peak reports, no data will be available for the corresponding date interval. Note: if desired, the generation of historical data may be disabled using SDS command dbHistoryAdm - see Section 5.1.2.3. 1.6.3 Rule for Computing Aggregated Values The computation of aggregated values of a counter may occur, in SPOTS, in the following situations (counter can be a raw counter or a pre-defined virtual counter, see Section 2.5.1.1 in [22]): • Aggregation of detailed data by the SPOTS dbAggregator command or the Data Aggregation task. In this case the detailed counter samples stored in the SPOTS Database are aggregated into a coarser granularity. The aggregation period is given by the output granularity parameter of the aggregation procedure. An example is the aggregation of data from 5 minutes granularity (input granularity) into 15 minutes granularity (output granularity). In this case, for every 15 minutes period the 5- minute samples are aggregated into a single 15-minute sample. • Generation of Historical Data (see Section 1.6.4) - Computation of the Daily Total value. In this case the detailed counter samples stored during a one day aggregation period are converted into a single value. • Generation of Historical Data (see Section 1.6.4) - Computation of the SPBH value. In this case the detailed counter samples stored for a variable during a one hour aggregation period (corresponding to the Peak Busy Hour) are converted into a single value. • Reporting - Computation of a report (of any kind, i.e. Ad-hoc, Siemens or Custom Report) whose output has a coarser time granularity than the input data stored in the SPOTS DB. In this case several data samples of a counter used in a report are aggregated into a single value, which is used in the computations (if any) needed to produce the report output. The aggregation period is given by the output granularity specified for the report (defined through the Data Source parameter in the Report Definition Wizard, see Section 4.6.6.1). The aggregated value of a counter is computed according to the counter's type (see Section 2.7 in [22]), by taking the sum, average or MAX/MIN of all the non-aggregated values within the aggregation period. Regarding the handling of possible missing data samples in the aggregation period, two variants of the aggregation algorithm may apply: Aggregation with extrapolation of missing values (Section 1.6.3.1); Aggregation without extrapolation of missing values (Section 1.6.3.2). The applicable variant is determined by the setting of the Extrapolation Flag for each measurement type and version, see [22], Section 2.4 Aggregation behaviour of Measurements. 22 E200301-01-114-V10.0I-03
  24. 24. User Manual (SPOTS V10 Drop 4) Siemens S.A. 1.6.3.1 Aggregation with extrapolation of missing values The computation of the aggregated value requires that valid data exist for a certain percentage of the total number of samples which fall into the aggregation period. This percentage is controlled by the value of the property “MinimumPercentageIntegrationData” defined in both the following configuration files: • SDS configuration file “sds.cfg” for data calculated by the SPOTS dbAggregator command (or the Data Aggregation task) and the generation of historical data (SPBH and Daily Total). • SAS configuration file “sas.cfg” for data computed for a report with a coarser output granularity period than the existing data in the SPOTS DB. In both cases the default value (if not defined in its specific configuration file) is 60%. If the percentage of existing and valid data is greater than or equal to the above defined percentage, but lower than 100% (i.e. some sample(s) is(are) missing), the missing values are handled as follows: • counters of type sum or average: missing values are taken to be the average of the values that exist within the aggregation period. In other words, the missing values are interpolated / extrapolated based on the existing values. • counters of type MAX or MIN: missing values are ignored (i.e. they are assumed not to affect the MAX or MIN of the values that exist within the aggregation period). Note that the existence of a minimum percentage of data is evaluated per counter. The traffic record samples for the measurement to which the counter belongs may exceed the minimum percentage, without implying that enough samples of the counter itself are available. This occurs because some traffic records may carry no data for some counters. Thus, for a given time period, object and measurement, aggregation may be possible for some counters and impossible for others. (Of course, if the percentage of traffic record samples for the measurement does not reach the minimum, then no counters can be aggregated at all.) 1.6.3.2 Aggregation without extrapolation of missing values In this case, the computation of the aggregated value requires only that one valid data sample exists in the aggregation period. The missing samples, if any, are considered to have a value of zero. 1.6.4 Algorithm for computing Historical Data The base period for historical data creation is the day. These are the significant indicators to be evaluated: Daily Total (also known as the daily Global Value) This is the aggregated value of a counter, for an aggregation period of a whole day (starting at midnight). The value is evaluated according to the general rule for computing aggregated values (see Section 1.6.3). If, in the aggregation period, the percentage of existing and valid counter data is below the minimum required by this rule, no Daily Total is registered. SPBH (Sample at Peak Busy Hour) This is the aggregated value of a counter for an aggregation period of one hour, corresponding to the PBH (Peak Busy Hour) of the Reference Variable. The value is evaluated according to the general rule for computing aggregated values (see Section 1.6.3). If, in the aggregation period, the percentage of existing and valid counter data is below the minimum required by this rule, no SPBH is registered. For each SPOTS Measurement, a Reference Variable is defined, which may be a raw counter or a pre-defined virtual counter (see Section 2.3 in [22] for a list of all Reference Variables). E200301-01-114-V10.0I-03 23
  25. 25. Siemens S.A. User Manual (SPOTS V10 Drop 4) The PBH of the reference variable is the end of the one-hour period for which the aggregated value of the reference variable (evaluated according to 1.6.3) reaches its maximum. The PBH is aligned to a multiple of the counter granularity in the SPOTS DB; for instance, if a counter is stored with 15 minute granularity, then its PBH on a given day may occur at 00:00, 00:15, 00:30, 00:45 etc. until 23:45 (note that the PBH 00:00 is considered to belong to the following day). The PBH evaluation considers a set of consecutive data samples ending on the PBH time, e.g. for PBH=12:15 the following samples are considered: 11:30, 11:45, 12:00 and 12:15. The evaluation of the PBH requires that, for the Reference Variable, enough data exist to compute an aggregated value for at least a single one-hour period within the day. If, for all one-hour aggregation periods in a day, the percentage of existing and valid counter data is always below the minimum required by 1.6.3, no PBH can be determined. In this case, no SPBH is registered for any of the counters associated with the Reference Variable in question. If the maximum aggregated value of the reference variable occurs in multiple one-hour periods within a day, then the first one-hour period will be considered the PBH. 24 E200301-01-114-V10.0I-03
  26. 26. User Manual (SPOTS V10 Drop 4) Siemens S.A. 2 Initial Configuration Tasks 2.1 Licensing Access to the following SPOTS functionality is controlled by licensing: • Global client functionality (i.e. login into SPOTS); • Reports edition. Therefore, specific licence strings must be provided for each of these items. Throughout this Manual, licensing support enabling the SPOTS full functionality will be assumed. Before using SPOTS, make sure that the necessary licence strings have been ordered and are installed - refer to the SPOTS Installation Guide ([21]), Section 7.6 (SPOTS Licensing Software), for information on the required procedure. E200301-01-114-V10.0I-03 25
  27. 27. Siemens S.A. User Manual (SPOTS V10 Drop 4) 2.2 Creation of User Groups There are two different categories of SPOTS users: regular users and administrators, which differ in the functionality they can perform: Functionality Normal User Administrator Perform Node Administration No Yes Import PM Data No Yes Explicitly Delete PM Data No Yes Run Reports Yes Yes Manage own Private Virtual Entities Yes Yes Manage others Private Virtual Entities No No Manage Public Virtual Entities No Yes Grant access of other system users to SPOTS No Yes Manage own Scheduled Tasks Yes Yes Manage others Scheduled Tasks No No Table 3 – Functionality allowed to Normal Users and Administrators All SPOTS users must be previously created as UnixTM users on one of the SAS systems of the SPOTS distributed environment, and assigned to one of the following UnixTM user groups of the SAS system: • pmadmin UnixTM user group (for a SPOTS administrator); • pmuser UnixTM user group (for a regular SPOTS users, without administration privileges). This task can be achieved using UnixTM user administration facilities. Once achieved, it is necessary to ensure the user has the proper UnixTM environment for SPOTS execution, and to associate him/her to the corresponding SPOTS domain (see Section 2.3). In order to provide the proper UnixTM environment for a user to execute SPOTS, proceed as follows: • edit the configuration file that contains the user-specific environment of the default user shell (for instance, home_directory/.profile for bourne shell or korn shell); • at the end of the file, add a line to execute the /etc/spotsenv file, which defines the UnixTM environment for SPOTS execution. In case of the above mentioned shells, this line would be: . /etc/spotsenv 26 E200301-01-114-V10.0I-03
  28. 28. User Manual (SPOTS V10 Drop 4) Siemens S.A. 2.3 Assignment of Users to Domains After installing the SAS for the first time, no SPOTS users are defined. In this case, only the local user spots is allowed to login to the SAS and set-up the SPOTS users. To set-up the SPOTS users, it is necessary to assign the previously created users (classified as pmadmin or pmuser) to the required domains (see Users Domain). For information on how to set-up the management domains, see Creation of Domains. All users logging into a certain SAS must be allowed to log into the UnixTM Operating System (on that SAS). E200301-01-114-V10.0I-03 27
  29. 29. Siemens S.A. User Manual (SPOTS V10 Drop 4) 2.4 Creation of Domains After installing the SPOTS, (by default) there will be no network domains. This means that all nodes will be contained under the default root domain (/). The network can be split in several domains. This task should be performed as soon as possible, be-fore the system becomes fully operational, to avoid necessary and significant configuration changes later. To set-up the required management domains, see Configuring Domains Structure. Please make sure to follow the domain's configuration rules: • Define a Primary Domain in association with a specific SDS. This means that all nodes under this Primary Domain will be stored on the respective database server. • For each SDS, only one Primary Domain can be associated. • Primary Domains can’t contain other Primary Domains. • Sub-domains under the Primary Domain may contain nodes and/or other Sub-domains. • Network Domains are (only) “containers” and can’t have directly assigned nodes. When the domains’ configuration is finished, the SAS will automatically restarted, in order to load the new configuration and update the SNS. 28 E200301-01-114-V10.0I-03
  30. 30. User Manual (SPOTS V10 Drop 4) Siemens S.A. 2.5 Automatic Nodes Creation In order to skip repetitive creation of nodes in the user interface (see Section 4.1.1), it is possible to activate their automatic creation triggered by first-time data import. A non-existing node is created automatically on data import. The corresponding version is defined in file nodes_creation.cfg, stored in $SPOTS_DIR (refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DIR and other SPOTS environment variables). When this file is empty or if no entry exists for the corresponding nxode type, the node must be created manually. In the following example, all nodes of type EXCHOC that have not yet been defined in SPOTS will be created upon data import with version CS10 starting at 2001/09/01. # # File: nodes_creation.cfg # Automatic Nodes Creation Configuration File # # Line Syntax: NodeType; VersionName; Date # # Example: EXCHOC;SR90;1999/01/01 EXCHOC;CS10;2001/09/01 To disable this facility it is only necessary to comment the definition line, i.e. insert a “#” in the beginning of the line, like: # # File: nodes_creation.cfg # Automatic Nodes Creation Configuration File # # Line Syntax: NodeType; VersionName; Date # # Example: EXCHOC;SR90;1999/01/01 #EXCHOC;CS10;2001/09/01 When the content of this configuration file changes, the corresponding SAS must be rebooted, thus all SPOTS GUI sessions connected to that server must also restart. To reboot a SPOTS Application Server, login as spots user and perform the command 'spotsShutdown -r' (see Section 5.1.1.9). E200301-01-114-V10.0I-03 29
  31. 31. Siemens S.A. User Manual (SPOTS V10 Drop 4) 2.6 Data Collection and Loading 2.6.1 Overview To be able to produce PM reports with the SPOTS tool, PM data must previously be loaded into the SPOTS database. This is achieved by the data collection and “data loading processes. The data collection consists of transferring the PM data (produced by the Network Nodes) from the Network Management System (NMS) platforms to the SAS. For the data collection to succeed, it must be ensured that all involved “partners” (Network Node(s), NMS(s) and SPOTS) are properly configured — see Table 4 for a high-level overview of the configuration actions to be performed on the Network Node and NMS and 2.6.2 - Configuring the SPOTS data collection for the actions to be performed on SPOTS. As a result of data collection, PM data become available on the SAS in the form of PM data files. The next step is the loading of these files into the SPOTS database (see 2.6.3 - Configuring the SPOTS data loading for details). After successful data loading, PM data can finally be used by the SPOTS tool as source for reports. Important Note: Special restrictions must be observed to allow processing of traffic data by the SPOTS Real-Time part, if that part is present. For information, see [24], Section 2.2 Data Collection and Processing. Technology Domain Network Node Versions NMS Types of Configuration Actions to be performed Ref. Docs. (Network Nodes) Ref. Docs. (NMS)s HLRi node: HI1.1 @Vantage Commander V7.8 Activate measurement jobs in the node. Perform any configuration actions required for HLRi PM Data Export Interface. [28] [27] OMC-S OSR9.0 Define data to be transferred in the OMC-S Upload Scheduler application. [03], [04], [33] Classic nodes: Activate REC [26] SR8.0, SR9.0, jobs in the SR10.0 node. Core - Circuit Switching Innovation nodes: CS1.0, CS2.0, CS2.1 Activate PM scanners and REC jobs in the node. [04], [07], [32] PS1.0, PS2.0, PS2.1 [08], [09], [31] Core - Packet Switching GPRS nodes: GR1.1, GR2.0, GR3.1 [05], [06], [30] Core - Signalling (STP) STP-V13 STP-V15 Switch Commander (SCR9.2.4 / PDC V2.2 and SCR10.1 / 10.2 PDC V2.3) Activate PDC scanners. Configure data upload to PDC and production of transmission files on PDC. [10], [11] – see SS7 and MP load measurements for SSNC. [19], [29],[34] 30 E200301-01-114-V10.0I-03
  32. 32. User Manual (SPOTS V10 Drop 4) Siemens S.A. Technology Domain Network Node Versions NMS Types of Configuration Actions to be performed Ref. Docs. (Network Nodes) Ref. Docs. (NMS)s Core - Packet Switching PO21C Core – Value Added Services MSP3.0 IP Manager 4.2 Activate IPM scanners. Configure data upload to IPM and production of transmission files on IPM. [38] [37] BR6.0, BR7.0 Radio Commander [14] [17], [35] GERAN Activate PM scanners. Setup the PM data upload from the Network Nodes to the Radio Commander. Observe the recommendations in section 2.6.1.1 at the end of this table. BR5.0, BR5.5 OMC-B [12], [13] [16] UTRAN UMR2.x, UMR3.0 (RNC, NodeB 1/2) Radio Commander [15] [18], [36] Table 4 – Configuration actions for Network Nodes and Network Management Systems 2.6.1.1 Special recommendations for RAN environments The following recommendations must be observed in order to allow correct processing of the GERAN and UTRAN traffic data in SPOTS: • For UTRAN, never set the granularity period to 6h nor 12h, as these values are not supported by SPOTS; • Additionally it is recommended not to set the granularity period to 24h, as this value is not supported by the SPOTS historical data generation procedure; • For both UTRAN and GERAN, the choice of granularity period should consider the effect on NMS system load - for example, and depending on the operating conditions, a granularity period of 5 minutes can generate an excessive load; • For GERAN, the traffic data originated by different RC / OMC-B scanners can in some cases be grouped by SPOTS into a single SPOTS measurement. Be sure never to use different granularity periods for scanners that are combined into the same SPOTS measurement. To know the mapping between scanners and SPOTS measurements, see Table 6 to Table 9 in Section 2.2 of [22] (the column Siemens measurement name(s) allows to identify the scanner(s) associated with each SPOTS measurement); • For GERAN and Radio Commander NMS, it is necessary to configure, on the RC, the generation of PM data files in the ASCII format - see Section Data conversion in ASCII format in [17]. During this configuration, when choosing the setMeasConvMode window parameters used to set the ASCII file options, please observe the following: set the parameters enabled to True and Duration to 0, in order for the RC to generate a single ASCII file for each uploaded BSC PM binary file; do NOT set the parameter format - preferredAlias to cellGlobalIdentity (1), as this would cause the Cell Global Identity value to be used as identification of cell objects (this is not currently supported by SPOTS). do NOT set the parameter format - cellIdFormat to symbolicName (0), as this would cause symbolic names to be used as identification of measurements (this is currently not supported by SPOTS). do NOT set the parameter format - cellNameFormat to newcellid (1), as this may E200301-01-114-V10.0I-03 31
  33. 33. Siemens S.A. User Manual (SPOTS V10 Drop 4) lead to failures in the loading of traffic files into SPOTS Database. • For GERAN, whenever a BSC managed via OMC-B is upgraded and becomes managed via RC, the managed objects of that BSC must be converted into symbolic names. To achieve this, it is necessary to execute the changeObjNames program according to 5.1.2.9. This must be done before initiating data collection via RC for the BSC in question. 32 E200301-01-114-V10.0I-03
  34. 34. User Manual (SPOTS V10 Drop 4) Siemens S.A. 2.6.1.2 Symbolic name handling in RAN environments When collecting GERAN and UTRAN traffic data via Radio Commander, SPOTS shall identify the managed network objects through their symbolic names, assigned on the Radio Commander. In order to achieve this, SPOTS automatically retrieves symbolic naming information from the Radio Commander. SPOTS maps the Full Distinguished Names of the objects (received in traffic files) to RC symbolic names. The SPOTS symbolic name handling has the following characteristics: • GERAN object classes that support symbolic names are: BSCOC, BTSMOC, BTSOC, ADJCOC; • UTRAN object classes that support symbolic names are: RNCOC, UCELLOC, NODEBOC; • If a managed object, belonging to an object class that supports symbolic names, has no symbolic name assigned on the Radio Commander, SPOTS shall use the last component of the object's Full Distinguished Name (FDN) as symbolic name. The FDN is a hierarchical concatenation of integer values, structured according to the RC object model containment tree. The last component (last value) identifies an object with respect to its parent object in the model. Example: Consider a BTS object without symbolic name, contained in a BTSM object also without symbolic name, which in turn is contained in a BSC with symbolic name myBSC. Assume the FDN of the BTS object is { 1 2 3 }. In this case 1 is the FDN component that identifies the BSC, 2 is the FDN component that identifies the BTSM and 3 is the FDN component that identifies the BTS. SPOTS will use symbolic name myBSC for the BSC, 2 for the BTSM and 3 for the BTS. The full identification of the BTS object in SPOTS will be myBSC:2:3. SPOTS ADJCOC (Cell Adjacency) objects are an exception to the previous point. ADJCOC objects are contained in BTSOC objects and represent cell adjacencies involved in call handovers. Each instance pair (BTSOC, ADJOC) represents a pair of adjacent cells, where the BTSOC instance is the observed cell and the ADJCOC instance allows to identify the neighbour cell (using the traffic measurements terminology). Cell adjacencies may be intra-BSC or inter-BSC according to the kind of handover performed: - For intra-BSC handovers, the ADJCOC object instance receives the RC symbolic name of the BTS corresponding to the neighbour cell. If that BTS has no symbolic name, then its full FDN is used, with the 3 integer values separated by _. Example for intra-BSC adjacency (neighbour cell has no symbolic name): ADJCOC symbolic name = 1_2_3; full identification of ADJCOC instance: someBSC:someBTSM:someBTS:1_2_3. - For inter-BSC handovers, the ADJCOC object instance receives the RC symbolic name of the RC tgtbts (target BTS) object corresponding to the inter-BSC adjacency. If that tgtbts has no symbolic name, then its full FDN is used, with the 2 integer values separated by _. Example for inter-BSC adjacency (target BTS object has no symbolic name): ADJCOC symbolic name = 4_5 full identification of ADJCOC instance: someBSC:someBTSM:someBTS:4_5. • A managed object is identified, from the SPOTS point of view, by its symbolic name - if this name changes, SPOTS assumes that a new object has been created. • When SPOTS loads traffic data in its Database, it associates traffic records with the respective managed objects, identified (where applicable) by their symbolic names. In this context, SPOTS always considers the latest symbolic names assigned by the RC. SPOTS will store the traffic records for an object in association with its latest available symbolic name, even if that symbolic name was assigned to the object after the time of traffic record generation. For details on Object Identifier syntaxes consult Section 2.1 (Object classes and identifiers) in [22]. E200301-01-114-V10.0I-03 33
  35. 35. Siemens S.A. User Manual (SPOTS V10 Drop 4) 2.6.2 Configuring the SPOTS data collection As a pre-condition for the data collection process, the user must configure the Network Node(s) and NMS(s) appropriately - see previous section. The data collection is achieved, depending on the NMS type, through the execution of the Collector program (in the Switch Commander, @VantageCommander, Radio Commander, OMC-B and IP Manager cases), or by dc_transfer daemon processes (in the OMC-S case) which are started automatically. These programs are prepared to carry out the data collection process for the environment of the NMSs (see Table 1). 2.6.2.1 File collection with Collector (SC, AC, OMC-B, RC and IPM environments) In a typical scenario, the UnixTM cron facility is used to schedule the periodic execution of one or more invocations of the Collector. The choice of the execution frequency should take into account the frequency with which traffic data are made available for retrieval on the NMS(s). The Collector invocations carry command-line parameters chosen according to the interfaced NMS(s), in order to specify the collection of all desired kinds of PM data (for a detailed description of the Collector interface, see Section 5.1.1.1). Previously to the first Collector invocation, specific configuration tasks must be performed to guarantee the interoperability between the SPOTS Server platform and the NMS — refer to the SPOTS Installation Guide ([21]), Section 7.5 (NMS Configuration). The main steps of the collection process are the following: Switch Commander (SC) Environment: PM data are produced by the nodes in the form of either Q3 scan reports, files written by REC jobs (cyclic or daily) or SNMP MIB variables (either polled via SNMP or, for SP:BSSGP MIBs, periodically dumped to file; the latter case applies to BVCI, NSEI and NSVCI specific counters). All these data are collected by the SC Upload Scheduler application and stored in so-called SPF (Siemens Performance Format) files, provided on the SC / PDC platform (as an exception, cyclic and daily files are not SPF; instead, they have the so-called tape format, usually designated in SPOTS be the adopted file extension: trf). The Collector program transfers the files from the PDC file store using the FTP protocol. @Vantage Commander (AC) Environment: PM data are produced by measurement jobs running in the HLRi nodes and transferred via a UDP-based protocol to the @Vantage Commander, where they are collected into files suitable for export to SPOTS via the HLRi PM Data Export Interface. OMC-B Environment: PM data are produced by the BSCs in the form of Q3 scan reports that are collected by the OMC-B and stored in the OMC-B database. The Collector program extracts the data to files (using the OMC-B MeasConv command) and transfer those files from the OMC-B using the UnixTM remote copy command. Radio Commander (RC) Environment: PM data are produced by nodes in the form of Q3 scan reports, for both GERAN and UTRAN. For GERAN, the RC collects these data in the form of binary format files and converts them into so-called PM ASCII files that are stored on the RC platform. For UTRAN, the RC collects these data in the form of ASN1/BER encoded binary files, also stored on the RC platform. In both GERAN and UTRAN, the Collector program transfers the files from the RC file store using a protocol proprietary variant of the FTP protocol (called OLTFTP). IP Manager (IPM) Environment: PM data are produced by the nodes in the form of SNMP MIB variables (polled via SNMP). All these data are collected by the IPM PDC application and stored in so-called SPF (Siemens Performance Format) files, provided on the IPM platform. The Collector program transfers the files from the IPM file store using the FTP protocol. 34 E200301-01-114-V10.0I-03
  36. 36. User Manual (SPOTS V10 Drop 4) Siemens S.A. 2.6.2.2 File collection with dc_t ransfer (OMC-S environment) PM data are produced by the nodes in the form of files written by REC jobs (cyclic or daily). These files are periodically transferred from Classic NEs by the OMC-S Upload Scheduler (see Section Upload Scheduler for SSS Measurement Data in [26]) and stored on the OMC-S platform. The data to be transferred from the NEs to the OMC-S, as well as the start time and the periodicity of this transfer mechanism, can be defined using the configuration capabilities of the Upload Scheduler (see Sub-section Editing the Configuration File in the above mentioned section of [26]). The SPOTS installation procedure automatically starts Unix daemon processes that transfer these files from the Upload Scheduler repository to the SPOTS Server platform. Configuration tasks must be performed, to guarantee the interoperability between the SPOTS Server platform and the OMC-S environment — refer to the SPOTS Installation Guide ([21]), Section 7.5.1 (NMS Configuration File). Transferred files are copied to the SPOTS Server platform, to the subdirectory traffic_data/daily or traffic_data/cyclic under the directory pointed by the Unix environment variable $SPOTS_DATA (Refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DATA and other SPOTS environment variables). The files are created on the SPOTS Server platform with the following naming convention: $SPOTS_DATA/traffic_data/cyclic or daily/NMS name.node name.text.trf where: NMS name is the name of the OMC-S platform from which data were collected, registered in $SPOTS_DIR/data/element_managers.cfg. node name is the Network Node name as it is registered in SPOTS i.e. it is the NE symbolic name administered on the NMS platform. text is a part of the name of the file such as it existed on the NMS. This part of the file name is not used by SPOTS (i.e. it is irrelevant from the point of view of the subsequent processing of the files). E200301-01-114-V10.0I-03 35
  37. 37. Siemens S.A. User Manual (SPOTS V10 Drop 4) 2.6.3 Configuring the SPOTS data loading The data loading is achieved through the execution of the loader program. This program is prepared to load into the SPOTS database the PM files already available on the SAS platform. The loader program copes with all types of traffic files that can be collected by SPOTS on all environments. Table 5 in Section 5.1.1.1 summarizes these file types. It encapsulates into a single command all the tasks necessary to process these different formats and insert the data into the Database. Additionally, it also ensures that the loaded data are passed to the SPOTS Real-Time applications in order to be processed for threshold analisys and alarm generation. Usually the files to be loaded are placed on the SAS by a previous Collector invocation or by a dc_transfer daemon. However, the files may be placed on the SAS by any means (e.g. restored from backup), as long as certain file path and name conventions are followed — see Section 5.1.1.3 for details on the loader interface specification. 2.6.4 Scheduling SPOTS data collection and loading In a typical scenario, the UnixTM cron facility is used to schedule the periodic execution of one or more invocations of the loader, coordinated with invocations of the Collector (for the OMC-S case, where data collection is not performed by the Collector, see next section), . One possibility is to create a script file with consecutive executions of Collector and loader and to schedule the periodic execution of this file. An example of such a script is presented below. Notice that previous to the execution of the commands, the environment is loaded (from files /home/username/.profile and /etc/spotsenv). Note also that the UnixTM cron facility emits a mail message with the output generated by every executed command. This may cause a large number of messages to become accumulated in the mailbox of the user who is executing the scheduled jobs. To prevent this, redirect the standard output and standard error to /dev/null (see example). Example: #!/usr/bin/ksh . /home/username/.profile /dev/null 21 . /etc/spotsenv /dev/null 21 $SPOTS_DIR/bin/Collector -e SC -n sc1 -t q3 /dev/null 21 $SPOTS_DIR/bin/loader -t q3dc /dev/null 21 Before loading data from a Network Node, it must be configured in the SPOTS database; this can be performed automatically (refer to Section 2.5) or manually (refer to Section 4.1.1). 2.6.4.1 Scheduling data collection from OMC-S Cyclic and daily files are uploaded with the naming convention and to the directories indicated in Table 5. Therefore any invocation of the loader program targeted on these types of files, will import in the database files collected from the OMC-S. As collection from the OMC-S is performed by daemon processes launched at boot time, the loader program may be scheduled to import files with the same time interval as dc_transfer. Further synchronization between both programs (a loader scheduled job and dc_transfer) , may only be achieved by stopping the dc_transfer daemon and restarting it prior to the moment the scheduled job (see Section 5.1.1.2) will be executed. Take into account the following issues concerning the periodicity of file collection from the OMC-S: − Daily files are transferred from the NE to the OMC-S gradually throughout the day (see [26]). − The Upload Scheduler must be restarted when jobs are restarted (see [26]). 36 E200301-01-114-V10.0I-03
  38. 38. User Manual (SPOTS V10 Drop 4) Siemens S.A. 2.6.4.2 Scheduling data collection from OMC-B For GERAN and the OMC-B NMS, when scheduling the file collection and loading, take the following into account: • The OMC-B and SPOTS SAS cannot have a time difference of more than 2 minutes (UCT time). • Data may take a while to be transferred from the BSC(s) to the OMC-B every hour. Therefore, to avoid loss of data by SPOTS when accessing the OMC-B, the start time collection process executed by SPOTS should be delayed by at least 5 minutes, from the instant where data is being transferred from the BSC(s) to the OMC-B. The upload of the BSC(s) to the OMC-B depends of the number of BSC(s), so the appropriate delay between the execution of the Collector (and loading) and this mechanism has to be adjusted. 2.6.5 Objects naming restr ictions There are restrictions when naming the objects in the Network Nodes. The names assigned to the objects or its descendants shall not contain the following characters: ' (quote) (double quote) % (percentage) ; (semi-colon) : (colon) @ (at) , (comma) . (dot) These characters are not supported in the SPOTS internal processing. E200301-01-114-V10.0I-03 37
  39. 39. Siemens S.A. User Manual (SPOTS V10 Drop 4) 3 User Interface 3.1 User Login When SCL is installed on a WindowsTM system, the user logs on the SCL via Start → Programs → SPOTS-PMC → - SPOTS Performance Management Client: The User Login window is presented over the SPOTS Client splash screen: This window allows the identification of the user that is starting a new session of the SCL. When SCL is installed on a UnixTM machine, the same window is invoked by calling the command spots located under directory $SPOTS_DIR/bin (refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DIR and other SPOTS environment variables). Window Attributes • The User Name field identifies the user. For a user name to be recognized as a SPOTS user, it is mandatory to create it as a UnixTM user on one of the SAS systems of the SPOTS distributed environment. Additionally, it is necessary to create the UnixTM user groups pmadmin and pmuser on the mentioned system, and assign the user in question to one of these two groups. Users assigned to the pmadmin group are considered as SPOTS administrators, whereas users assigned to the pmuser group are considered as regular SPOTS users, without administration privileges. The only exception is the server local spots user, whose access is granted (with adminis-tration privileges) independently of the user groups existence. • The Password field is the password associated to the specified user. Password is case sensitive. A user without password can’t use the SCL. • The Remember this user name and password check box allows to store the specified user 38 E200301-01-114-V10.0I-03
  40. 40. User Manual (SPOTS V10 Drop 4) Siemens S.A. name and password for a subsequent use. It means that next time the current system user logs into the SCL, the default presented user name/password are the inserted values. When this check box is selected, the remembered values depend on the Operating System user that has started the SCL session. This information is stored for each Operating System user (i.e. different values are presented for different Operating System users). Note: When the SCL runs for the first time, no user-domain associations have been yet specified. In these situations, the spots user shall be used; so, the spots user must exist. E200301-01-114-V10.0I-03 39
  41. 41. Siemens S.A. User Manual (SPOTS V10 Drop 4) 3.2 Main Window The SPOTS main window is an MDI (Multi-Document Interface) based graphical user interface, allowing the user to execute several task instances simultaneously. It comprises the following components: Titlebar 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. Menubar Application pull-down menus, containing all the available functions. Toolbar Shortcuts to the most used application functions. The toolbar display status can be toggled (hidden/visible), using the menu option View → Toolbar. Task Tree Window Application task tree. With this window, the user may select and open the required application tasks. The Task Tree window display status can be toggled (hidden/visible) by using the menu option View → Tree. Task Area Window Area where all the task windows are realized. 40 E200301-01-114-V10.0I-03
  42. 42. User Manual (SPOTS V10 Drop 4) Siemens S.A. History Log Window List of status information regarding the tasks started during the current session. The History Log window display status can be toggled (hidden/visible) by using the menu option View → History. Statusbar Text messages to assist the user during the normal operation. It also contains the Alarm Browser icon, which blinks upon the reception of QoS Alarms. Window Operations New chart Ad-hoc report. (Same as F2 function key) New table Ad-hoc report. (Same as F3 function key) Open selected task window. (Same as Ctrl + O) Hide/show the Task Tree window. Hide/show the History Log window. Select the active window. Context sensitive help (What's this?). Help window. E200301-01-114-V10.0I-03 41
  43. 43. Siemens S.A. User Manual (SPOTS V10 Drop 4) 3.3 Interaction The user interacts with the application using two possible devices: the keyboard and the pointer device. Keyboard The keyboard is divided into the following areas: Alphanumeric keys Contains letters, numbers, punctuation symbols, Space, Backspace, Enter, Insert and Delete keys. These keys are used to write the text to fill in the editable fields. Navigation keys Contains the cursor keys, Tab (for selection of the next object), the Home and End keys. These keys are used to navigate among objects or set the cursor within the text of an editable field. Function keys Include the keys F1 through F10. These keys are normally used as shortcuts to execute a pre-defined function (e.g. the key F1 executes the “Help - On Window “function). Extension keys Include the Shift, Alt and Ctrl keys. These keys are used together with another key(s), to enhance the keyboard functionality. Pointer device On the standard configuration, the pointer device will be a Mouse, allowing a quick interaction with the windows' components. The Mouse can be used to perform the following functions: Left Button • Click for selection/Operation execution • Double-click for default object execution Shift + Left Button • Selection of all entries between a previously selected pair Ctrl + Left Button • Appending a selected object to the current list of selected entries. Right Button • Contextual menu for the available operations Note: The application can be completely operated just with the keyboard. In this case, the following correspondence shall be used: Mouse Left click ↔ Cursor keys/Tab Mouse Left double-click ↔ Enter key Mouse Right click ↔ (Alt+Enter) keys 42 E200301-01-114-V10.0I-03
  44. 44. User Manual (SPOTS V10 Drop 4) Siemens S.A. 3.4 Modes of Operation Interactive Mode The SPOTS interactive operation is (preferably) performed via a GUI environment, based on Java technology. Most of the tasks that are accessible within the GUI environment (refer to Chapter 4) can also be executed from the (Operating System) command line. Besides them, other commands are available, addressing (mainly) SPOTS administration activities — all SPOTS commands are described in Chapter 5.1. Scheduled Mode The most relevant (repetitive) tasks — refer to Scheduling tasks — can be automatically executed, using a scheduling mechanism provided by SPOTS. Additionally, the Operating System scheduling facilities (e.g. UnixTM cron) will be used to support the automatic execution of the available SPOTS Commands. E200301-01-114-V10.0I-03 43
  45. 45. Siemens S.A. User Manual (SPOTS V10 Drop 4) 3.5 Scheduling tasks The most relevant (repetitive) tasks can be automatically executed, using the SPOTS Scheduler task. This includes: • Import of PM data files into SPOTS database, without real-time processing of the data (see Section 4.2.1); • Production of Historical Data (see Section 4.2.3); • Aggregate Detailed Data (see Section 4.2.4); • Reporting (see Section 4.6); • Deletion of Detailed and Historical Data (see Section 4.2.2). The status of the existing scheduled jobs (created by the SPOTS Scheduler) is presented by the Scheduler Browser. To guarantee an adequate SPOTS operation, the set of tasks to be automatically executed should be complemented with other SPOTS commands. It is suggested to include (at least) the following ones: • Collection of PM data files, using the Collector SPOTS command (see Section 5.1.1.1); • Import of PM data files into SPOTS database, including (if applicable) real-time processing of the data, using the loader SPOTS command (see Section 5.1.1.3); • Optimisation of database access, using the dbCalcStat SPOTS command (see Section 5.1.2.2). Execution of these tasks is supported by the Operating System scheduling facilities (e.g. UnixTM cron). 44 E200301-01-114-V10.0I-03
  46. 46. User Manual (SPOTS V10 Drop 4) Siemens S.A. 3.6 Messages During the execution of SPOTS, two basic types of messages are produced: Interactive and Logged messages. Interactive Messages They are produced in the interactive mode of operation, as result of an error, to confirm the requested action, or any other operation requiring immediate user attention. These messages are usually visualized through dialogue popup windows. Information message Warning message Error message Logged Messages They are produced to inform the user about the execution status of the requested tasks. These messages are usually visualized on the History Log window. Task Pending Task In progress Task Failed Task Stopped Task Executed E200301-01-114-V10.0I-03 45
  47. 47. Siemens S.A. User Manual (SPOTS V10 Drop 4) 3.7 Printing This option, available in almost every window, is accessible: • from the toolbar, selecting button • from the menu bar, selecting option Task → Print... • from the context sensitive menu, selecting Print ... The printing request is sent to the default printer, using the default settings. In addition, the menu option Spots → Print... can be used. The native Printer Setup dialogue box is presented to the user, to select the printer and set its properties. When SCL is installed on a WindowsTM system, this dialogue box looks like the following: When SCL is installed on a UnixTM system, this dialogue box looks like the following: 46 E200301-01-114-V10.0I-03
  48. 48. User Manual (SPOTS V10 Drop 4) Siemens S.A. 3.7.1 Setting Page Properties It is possible to customize the layout of the printout. This functionality is accessible: • from the toolbar, selecting button • from the menu bar, selecting option Task → Page Setup.... • from the context sensitive menu, selecting Page Setup... The Page Setup window contains two tabs and two buttons. Header/Footer tab This tab allows the customisation of the header and the footer of the printout. On the top, there are five buttons to customize and insert special functions in a selected text area on the bottom of the tab. Open the Font Setup window to customize some text selected in one of the three text boxes on the bottom of the tab; Insert the “page number” function in the selected text area; Insert the “total number of pages” function in the selected text area; Insert the “current date” function in the selected text area; Insert the “current time” function in the selected text area. On the bottom of the Header/Footer tab, three text boxes allow to insert text and the functions specified above. The characters’ font may be customized via the Font Setup button on the top. E200301-01-114-V10.0I-03 47
  49. 49. Siemens S.A. User Manual (SPOTS V10 Drop 4) Paper Settings tab The Paper Settings tab allows the customisation of the used paper. It is possible to: • select the paper orientation: Portrait and Landscape; • define the required margins (in centimetres): Left, Right, Top and Bottom; • choose the required paper size, using a drop-down list. Window Operations Confirm the inserted or modified data within the window and save the new settings. These settings are adopted as default for all subsequently generated printouts. Discard all the modifications. 48 E200301-01-114-V10.0I-03
  50. 50. User Manual (SPOTS V10 Drop 4) Siemens S.A. 3.7.2 Previewing the Printout To display the information as it will look when printed, the following alternatives are available: • from the menu bar, selecting option Task → Print Preview... • from the context sensitive menu, selecting Print Preview... • from the toolbar, selecting button The Print Preview window is presented: The Print Preview window contains the following buttons: Open the Print window; Preview one page at a time; Preview several pages at a time, up to a maximum of 2x3 pages; Use the full screen area; Close the window; Drop-down list to select the required zoom factor in this window. It doesn’t change the scale of the printout. E200301-01-114-V10.0I-03 49
  51. 51. Siemens S.A. User Manual (SPOTS V10 Drop 4) 3.8 Getting Help 3.8.1 Getting help while working The Help Window can be accessed using the Help button on the right side of the toolbar, or pressing the F1 function key. The purpose of the help system is to provide all relevant information regarding the product functionality and in particular concerning the interaction between the user and the application. The following help functions are available through the Help Menu: On Window Providing information about the current window. On Version Providing the identification of the installed version. On Help Providing information about the structure of the help system. 3.8.2 User Documentation The product documents are supplied with the application on the CD-ROM distribution media. The file readme.spots is provided, with notes about the distribution media contents, including the 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. 50 E200301-01-114-V10.0I-03
  52. 52. User Manual (SPOTS V10 Drop 4) Siemens S.A. 3.9 Objects filtering The selection of objects may be difficult to perform, due to the enormous quantity of object instances available within each object class. In order to avoid overloading the browser with all object instances, the user may define filters to reduce the scope of the object instances for selection, both when Removing Network Resources and in all reports which require the selection of one or more objects. The following example uses the Resources Deletion window, but a similar behaviour occurs within the reports, either in the wizard or in the Class Browser. It does not show lots of instances, in opposition to real situations, to be easier to understand. When the Resources Deletion window opens, the topmost domain level (whose access is granted to the current user) is considered. All the top object class instances are presented in the instance’s list, but none is selected. The object classes’ tree depends on the objects associated with the selected domain level. Only the classes supported by nodes of the selected domain are visible in the object classes tree. For instance, when the selected domain has no BSC nodes, the BSCOC object class (as well as the classes contained in it) is not visible. The first step it to select, from the top object class, one or more instances: The simplest filtering method is to click on the Set Filter button to immediately activate filtering for the selected objects. Now only the selected object instances are visible, even in lower level object classes: E200301-01-114-V10.0I-03 51
  53. 53. Siemens S.A. User Manual (SPOTS V10 Drop 4) The more accurate filtering method requires clicking on the Edit Filter button to open the Edit Filter window, considering the selected objects as the actual filter: Then the filter string is edited, to insert a more accurate filtering pattern: 52 E200301-01-114-V10.0I-03
  54. 54. User Manual (SPOTS V10 Drop 4) Siemens S.A. Valid filtering expressions: * any sequence of characters ? any character Multiple filters are supported. The filtering result is the union of the results of all defined filters. After clicking on the Apply or OK buttons, the instances list becomes empty, as the pattern specified does not match to any existing instance. However, when descending to a lower object class, for which the pattern makes sense, the number of presented instances has been reduced, when compared to those available without accurate filtering: E200301-01-114-V10.0I-03 53
  55. 55. Siemens S.A. User Manual (SPOTS V10 Drop 4) The filtering facility can be disabled in any moment, by clicking on the Reset Current Filter button . Now all instances of the current object class are again visible: 54 E200301-01-114-V10.0I-03
  56. 56. User Manual (SPOTS V10 Drop 4) Siemens S.A. 3.10 User preferences Each user can configure SPOTS according to his/her preferences, via the menu option Spots → Preferences... The user enables/disables several SPOTS features by checking/clearing the corresponding 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. These settings are stored per user in a specific file. Note: The wizard execute report automatically feature shall be disabled when the user just wants to create a User Defined Task and execute it later, either interactively or scheduled. E200301-01-114-V10.0I-03 55
  57. 57. Siemens S.A. User Manual (SPOTS V10 Drop 4) 4 Using SPOTS … 4.1 Network Resources 4.1.1 Configuring Network Nodes In order to collect and process the PM data produced by the Network Nodes, they must first be registered within the SPOTS application. There are two methods to register new nodes into the SPOTS application: • using the Automatic Nodes Creation facility, it is possible to automatically create a node when its PM data is being imported, assuming that some defaults have been previously defined and that they are compatible with the node under creation. • manually creating the nodes in the Node Configuration window. Once the nodes have been created, all the network resources belonging to the above mentioned nodes will be automatically recognized and configured during the data collection process. Start configuring the nodes, opening the Network Resources → Node Configuration task. Important Note: While the Network Resources → Node Configuration window is open, data loading should not be performed. Before editing the nodes configuration make sure than no loading tasks are running (loading may be triggered by executing the Data Administration → Data Loading task, loader command or dbLoader command - consult respectively Sections 4.2.1, 5.1.1.3, 5.1.1.4). 56 E200301-01-114-V10.0I-03
  58. 58. User Manual (SPOTS V10 Drop 4) Siemens S.A. Window Operations Most operations are only available to SPOTS administrators; a regular SPOTS user is only allowed to browse and print the Network Nodes he/she is allowed to view — see Creation of User Groups for more information about users' classification and Creation of Domains for the definition of the domains that a user can view. Select the domain, from a drop-down list of all domains that the current user can manage. In edit mode, when changes have occurred in current domain, a confirmation window is presented to validate the inserted information. The new domain is always presented in view mode. Undo last table change(s). Only available for SPOTS administrators. Redo last table change(s). Only available for SPOTS administrators. Select table edit mode for current domain, i.e. locks it to other users. Table changes (insert, update or remove network nodes) are allowed. Only available for SPOTS administrators. Select table view mode for current domain, i.e. unlocks it to other users. Table changes not allowed. Only available for SPOTS administrators. Save the changes to the network nodes table for the current domain. Only available for SPOTS administrators. Insert a new network node to current domain. Only available for SPOTS administrators. Remove selected network node from current domain. Only available for SPOTS administrators. Print list of network nodes from current domain. Print-preview of list of network nodes from current domain. Window Attributes Nodes: list of the configured Network Nodes for the selected domain. Name Name of the node. This attribute is case sensitive. Commentary (Optional) Description of the node. Version Name of the currently installed version. Date Installation date for the current version. E200301-01-114-V10.0I-03 57
  59. 59. Siemens S.A. User Manual (SPOTS V10 Drop 4) Notes: 1. If a node is removed, all contained resources and associated PM data are removed from the DB. 2. When in edit mode, a node can be reassigned to another sub-domain within the same DB. If a domain belonging to another DB is required, it is necessary to use the dbArchive SPOTS command (see Section 5.1.2.1) on both systems where the involved DBs are located. 58 E200301-01-114-V10.0I-03

×