Mentor Server Admin v9.1 User Guide

Mentor Server
Admin
User Guide
For Version 9.1
Confidentiality, Copyright Notice & Disclaimer
Due to a policy of continuous product development and refinement, TEOCO Ltd. (and its
affiliates, together “TEOCO”) reserves the right to alter the specifications, representation,
descriptions and all other matters outlined in this publication without prior notice. No part of
this document, taken as a whole or separately, shall be deemed to be part of any contract for
a product or commitment of any kind. Furthermore, this document is provided “As Is” and
without any warranty.
This document is the property of TEOCO, which owns the sole and full rights including
copyright. TEOCO retains the sole property rights to all information contained in this
document, and without the written consent of TEOCO given by contract or otherwise in
writing, the document must not be copied, reprinted or reproduced in any manner or form, nor
transmitted in any form or by any means: electronic, mechanical, magnetic or otherwise,
either wholly or in part.
The information herein is designated highly confidential and is subject to all restrictions in any
law regarding such matters and the relevant confidentiality and non-disclosure clauses or
agreements issued with TEOCO prior to or after the disclosure. All the information in this
document is to be safeguarded and all steps must be taken to prevent it from being disclosed
to any person or entity other than the direct entity that received it directly from TEOCO.
®
TEOCO and Netrac are trademarks of TEOCO.
All other company, brand or product names are trademarks or service marks of their
respective holders.
This is a legal notice and may not be removed or altered in any way.
COPYRIGHT © 2014 TEOCO LTD.
ALL RIGHTS RESERVED.
Your feedback is important to us: The TEOCO Documentation team takes many measures
in order to ensure that our work is of the highest quality.
If you found errors or feel that information is missing, please send your Documentation-
related feedback to [email protected]
Thank you,
The TEOCO Documentation team

Table of Contents
Table of Contents
Introduction..................................................................................................................... 1
System Description .................................................................................................................... 2
Front-End Clustering .................................................................................................................. 3
Viewing the Map Topology ......................................................................................................... 4
Administrator View of the Mentor Server Admin Application ..................................................... 6
Engineer View of the Server Admin Application ........................................................................ 7
Getting Started................................................................................................................ 8
Logging On to the Mentor Server ............................................................................................... 8
Upgrading the Mentor Server Admin ....................................................................................... 13
Viewing and Editing Your User Properties ............................................................................... 15
Changing Passwords ............................................................................................................... 16
Changing Passwords that are About to Expire ................................................................... 17
Changing Expired Passwords ............................................................................................. 18
Changing Existing Passwords............................................................................................. 19
Setting Preferences - Administrators ....................................................................................... 20
Setting Preferences - Engineers .............................................................................................. 21
Logging Off from the Mentor Server ........................................................................................ 23
User Interface................................................................................................................ 25
Menus....................................................................................................................................... 25
File Menu............................................................................................................................. 26
View Menu........................................................................................................................... 28
Action Menu ........................................................................................................................ 29
Help Menu ........................................................................................................................... 30
Keyboard Shortcuts .................................................................................................................. 30
Toolbar ..................................................................................................................................... 31
Navigation Pane ....................................................................................................................... 32
View/Edit Pane ......................................................................................................................... 33
Status Bar ................................................................................................................................ 33
Displaying Table Columns ....................................................................................................... 36
Searching for Server Items ...................................................................................................... 38
Managing Servers ......................................................................................................... 39
Adding Servers ......................................................................................................................... 40
Defining Server Properties ....................................................................................................... 40
General Properties .............................................................................................................. 42
Connection Properties ......................................................................................................... 43
Excluded Dates ................................................................................................................... 44
Backup Properties ............................................................................................................... 45
Dashboard Properties ......................................................................................................... 47
Locked Sectors ................................................................................................................... 52
Advanced Properties ........................................................................................................... 54
Defining Multi-selection Server Properties ............................................................................... 71
Server Maintenance ................................................................................................................. 73
Testing Server Connectivity ................................................................................................ 73
Exporting a Stack Trace ...................................................................................................... 73
Updating the Network Element Environment ......................................................................74
Deleting Old Files ................................................................................................................ 74
Backing Up the Server ........................................................................................................ 74
Restoring the Server Data................................................................................................... 75
Importing Advanced Server Properties .................................................................................... 75
Exporting Advanced Server Properties .................................................................................... 76
Importing Terrain Files ............................................................................................................. 77
iii
Mentor Server Admin 9.1 User Guide
Managing Agents .......................................................................................................... 79
Adding Agents .......................................................................................................................... 81
Viewing Agent Properties ......................................................................................................... 81
Agent General Properties.................................................................................................... 83
Agent Advanced Properties ................................................................................................ 84
Assigning Agents ..................................................................................................................... 90
Viewing Agent Statistics ........................................................................................................... 93
Viewing the Agent Storage Folder ........................................................................................... 95
Managing Online Collectors ........................................................................................ 96
Adding Online Collectors.......................................................................................................... 97
Viewing Online Collector Properties ...................................................................................... 101
General Online Collector Properties ................................................................................. 102
Advanced Online Collector Properties .............................................................................. 103
Importing Online Collectors .................................................................................................... 104
Exporting Online Collectors ................................................................................................... 105
Managing Data Devices .............................................................................................. 106
Viewing Data Device Properties ............................................................................................ 107
Managing Channels .................................................................................................... 109
Editing Channel Properties .................................................................................................... 110
Managing Network Elements ..................................................................................... 111
Adding Network Elements ...................................................................................................... 112
Defining General Network Element Properties ................................................................. 113
Defining Data Device Properties ....................................................................................... 115
Editing Data Device Properties ......................................................................................... 122
Defining Collection Tasks.................................................................................................. 124
Duplicating Network Elements ............................................................................................... 136
Viewing Network Element Properties ..................................................................................... 137
Exporting Network Properties ................................................................................................ 142
Importing Network Properties ................................................................................................ 143
Renaming Network Elements ................................................................................................ 143
Editing the Network Element Management System BSCs/RNCs..........................................145
Changing the Network Element Time Zone ........................................................................... 147
Viewing the Network Element History .................................................................................... 148
Deactivating Network Elements ............................................................................................. 150
Adding Data Devices.............................................................................................................. 151
Viewing Last Task Failure Details .......................................................................................... 153
Editing the Model Data ........................................................................................................... 154
Calculating the Collected Data Period ................................................................................... 156
Uploading Extracted Raw Data to the FTP Server ................................................................ 157
Defining Task Recurrences .................................................................................................... 159
Exporting Network Elements .................................................................................................. 161
Importing Network Elements .................................................................................................. 162
Deleting Network Elements .................................................................................................... 163
Completing the Physical Data - GSM Network Elements ......................................................166
Completing the Physical Data ................................................................................................ 167
Mass Data Completion ...................................................................................................... 168
Data Completion ............................................................................................................... 169
iv
Table of Contents
Creating Administration Reports ............................................................................................ 173
Agents Tab ........................................................................................................................ 174
Call DB Tab ....................................................................................................................... 176
Collections Tab ................................................................................................................. 176
Collection Statistics Tab .................................................................................................... 177
Log Processing Tab .......................................................................................................... 178
Log Processing Statistics Tab ........................................................................................... 178
Mobile Tracking Audit Tab ................................................................................................ 179
Models Tab........................................................................................................................ 179
Model Data Tab ................................................................................................................. 180
Model Statistics Tab .......................................................................................................... 180
Raw Data Tab ................................................................................................................... 181
Users Tab .......................................................................................................................... 181
Managing Notifications .............................................................................................. 182
Working with Notifications ...................................................................................................... 183
Filtering Notifications .............................................................................................................. 184
Data Collection ........................................................................................................... 186
Managing Collection Tasks .................................................................................................... 186
Working with Collection Tasks .......................................................................................... 188
Filtering Collection Tasks .................................................................................................. 191
Viewing Collection Task Properties .................................................................................. 193
Defining Task Recurrences ............................................................................................... 204
Importing Data Collection Task Properties ....................................................................... 207
Exporting Data Collection Task Properties ....................................................................... 208
Managing Physical Data Collection Tasks ............................................................................. 209
Adding Physical Data Collection Tasks ............................................................................ 211
Processing the Collected Physical Data ........................................................................... 216
Viewing Physical Data Collection Task Properties ...........................................................217
Physical Data Collection Task Notifications ...................................................................... 221
Editing Advanced Physical Data Collection Task Properties ............................................221
Importing Physical Data Collection Tasks......................................................................... 227
Exporting Physical Data Collection Tasks ........................................................................ 228
Managing Online Collection Tasks ........................................................................................ 229
Viewing Online Collection Task Properties ....................................................................... 231
Data Processing ......................................................................................................... 234
Managing Call Database Monitoring ...................................................................................... 234
Defining Call Database Properties .................................................................................... 236
Starting and Stopping the Call Database Loading Process ..............................................240
Viewing Network Element Call Database Monitoring Properties ......................................241
Managing Log Processing Tasks ........................................................................................... 244
Defining Log Processing Task Properties ......................................................................... 246
Defining Multi-selection Log Processing Task Properties .................................................257
Defining New GSM Log Processing Tasks ....................................................................... 261
Activating Log Processing Tasks ...................................................................................... 265
v
Managing Model Tasks .......................................................................................................... 266
Adding Modeling Periods .................................................................................................. 268
Viewing Model Task Properties ........................................................................................ 273
Viewing Modeling Period Properties ................................................................................. 275
Selecting Model Task Clusters ......................................................................................... 277
Viewing the Model Task Schedule .................................................................................... 278
Viewing Modeling Task Time Filter Properties.................................................................. 279
Viewing the Model Task Agents ........................................................................................ 280
Viewing Model Task History .............................................................................................. 281
Viewing Advanced Model Task Properties ....................................................................... 284
Viewing the Model Task Reports ...................................................................................... 286
Working with Model Tasks ................................................................................................ 288
Deleting Model Tasks........................................................................................................ 291
Managing Engineering Task Occurrences ................................................................ 293
Managing Optimization Tasks ................................................................................................ 293
Adding Optimization Tasks ............................................................................................... 295
Editing Optimization Task Properties ................................................................................ 303
Editing the Optimization Task Agent Properties ............................................................... 304
Viewing the Optimization Task History ............................................................................. 305
Viewing the Optimization Task Reports ............................................................................ 307
Managing Analysis Tasks ...................................................................................................... 308
Adding Analysis Tasks ...................................................................................................... 310
Editing Analysis Task Properties ...................................................................................... 319
Editing the Analysis Task Agent Properties ...................................................................... 320
Viewing Analysis Task History .......................................................................................... 321
Viewing the Analysis Task Reports ................................................................................... 323
Managing Provisioning Tasks ................................................................................................ 324
Adding Provisioning Tasks ................................................................................................ 326
Editing Advanced Provisioning Task Properties ............................................................... 334
Editing Provisioning Task Properties ................................................................................ 337
Viewing the Provisioning Task History .............................................................................. 338
Running Provisioning Tasks.............................................................................................. 340
Managing Regions ...................................................................................................... 341
Adding Regions ...................................................................................................................... 342
Assigning Clusters to Regions ............................................................................................... 343
Assigning Network Elements to Regions ............................................................................... 345
Assigning Users to Regions ................................................................................................... 347
Viewing Region Properties ..................................................................................................... 349
Deleting Regions .................................................................................................................... 350
Managing Clusters...................................................................................................... 351
Adding Clusters ...................................................................................................................... 352
Assigning Network Elements to Clusters ............................................................................... 354
Assigning Users to Clusters ................................................................................................... 356
Assigning Regions to Clusters ............................................................................................... 357
Editing Cluster Properties ...................................................................................................... 358
Exporting Clusters .................................................................................................................. 359
Importing Clusters .................................................................................................................. 360
Deleting Clusters .................................................................................................................... 362
vi
Table of Contents
Managing Users .......................................................................................................... 363
Adding Users .......................................................................................................................... 364
Assigning Regions to Users ................................................................................................... 367
Assigning Clusters to Users ................................................................................................... 368
Editing User Properties .......................................................................................................... 370
Exporting Users ...................................................................................................................... 372
Importing Users ...................................................................................................................... 373
Deactivating Users ................................................................................................................. 374
Deleting Users ........................................................................................................................ 374
Viewing Statistics ....................................................................................................... 375
Viewing Task Statistics .......................................................................................................... 375
Viewing Agent Statistics ......................................................................................................... 376
Managing Antenna Models ........................................................................................ 379
Viewing Antenna Model Properties ........................................................................................ 381
Viewing General Antenna Model Properties ..................................................................... 382
Viewing Antenna Model Profile Properties ........................................................................ 383
Importing Antenna Models ..................................................................................................... 386
Exporting Antenna Models ..................................................................................................... 388
Merging Antenna Models ....................................................................................................... 388
vii
Introduction
Introduction
The Mentor Server automates routine tasks, relieving the RF engineer of laborious manual
tasks such as collecting network data, importing statistics and network configuration,
performing preparation tasks such as modeling the network and running analyses and
optimizations, and finally implementing the recommended optimization changes. By
automating these processes, the client significantly reduces the process effort, eliminates
human errors, and shortens the optimization cycles, ensuring that the network is always
optimal, leaving the RF engineer with more time for creative tasks such as analysis and
decision making.
The enterprise configuration allows the Mentor Server to manage medium and larger
networks under a single centralized system. This provides access to market or nation-wide
data, while keeping all capabilities that are available when using a single server. Another
advantage is the enhanced load-balancing capability that allows efficient usage of system
machines, and redundancy in case of component failure.
The Mentor, Mentor Sparks, and Forte clients use the information collected and prepared by
the server to run optimizations and to schedule recurring optimizations on the server. After a
successful optimization plan has been generated, the user can send the tilt changes to the
server for implementation on the network. The rest of the changes can be saved to vendor-
specific provisioning scripts for easy implementation.
The Mentor Server Admin application enables an administrator to log on to multiple servers
and define network elements and their modeling periods, users and their assigned clusters,
and to schedule collection, optimization, and provisioning tasks. If there are any problems
executing these tasks, the server will notify the administrator.
1
System Description
The following is a description of the different levels in the Network Management System
hierarchy, of which the Mentor Server is in the Network Manager group.
Network Elements: The network elements are the lowest level in the network system
hierarchy. They are the physical elements in the network, the hardware on which the work is
done, for example, the antennas.
Element Managers: The element managers, which may be vendor-specific, work with
individual network elements, for example, configuring them, receiving notifications and so on.
However, because they can deal with only individual elements below them, they do not know
how changing one element may affect other elements in the network. The element managers
require the network managers in order to see the relationship between the elements.
Network Managers: The network managers see all the elements in the network together,
and know how elements affect each other. However, due to the network management
hierarchy, network managers deal only with element managers, and only the element
managers deal with the elements themselves. The network managers communicate with the
different element managers, for example, the BSCm which is the Motorola element manager,
the MTX which is the element manager that collects the statistics, and the EMS, which works
with Powerwave devices.
The Mentor Server is part of the network managers group in the network management
hierarchy. It can see all the elements in the network, and knows how they affect each other.
For example, it understands how changing the neighbor list in one area will affect another
area, or how changing the tilt in one area affects the antennas in a different area.
2
Introduction
Front-End Clustering
The Mentor Server supports front-end clustering functionality, where the system allocates a
serving host from its group of existing front-end servers, provides load balancing and
resilience in the system. It also provides high-availability, using one of the following methods:
 Active/Active: All nodes in the server group can perform the same task concurrently.
 Active/Passive: Only one node can perform a task. If it fails, another node takes
over the task execution.
User Requests (Active/Active):
User requests are handled as follows:
 All front-end servers handle user requests concurrently.
 Every time a user logs in, the system allocates a serving host for the entire session.
In the first login, the user must define a new server and specify one of the existing
hosts in the cluster. The serving host is then automatically allocated from the existing
front-end servers in the cluster using a round-robin allocation method.
 If a specific host fails, the user must manually log in to the system again.
Agent Management (Active/Passive):
 One of the front-end servers acts as the "master", and is in charge of scheduling, task
load balancing, and automatic upgrades.
 If there is a problem on this host, for example, the service is down, network
disconnection, or machine shutdown, another host in the front-end cluster becomes
the Master and takes over these responsibilities.
Note: If a front-end server leaves the cluster due to disconnection, it may have to be
manually restarted.
 Collection, model, and calculation tasks running on the agents are not affected by a
master failover.
You can view the status of the connected servers in the Servers pane.
3
Viewing the Map Topology

You can view a graphic display of the system to help understand the network physical and
logical connectivity and hierarchy.
To display the topology map:

1. On the View menu, click Topology Map.
-OR-
On the toolbar, click .
A topology map is displayed, showing the connected servers and their hierarchy.
4
Introduction
2. To view the topology legend, on the Topology Map toolbar, click .
5
Administrator View of the Mentor Server Admin Application

Super administrator users have full access to all the functionality of the Mentor Server Admin
application. They can see all the activities in all regions in the network and configure the
properties for all users in the network.
Regional administrator users have full access to all the functionality of the of the Mentor
Server Admin application for all regions assigned to them. They can see all the activities in all
their regions and configure the properties for all users in these regions.
When an administrator user logs on to the server, the following items are displayed in the
navigation pane on the left of the main window:
 Entity Configuration
o Servers
o Agents
o Online Collectors
o Data Devices
o Channels
o Network Elements
6
Introduction
 Process Monitoring
o Notifications
o Data Collection
 Collection Tasks
 Physical Data Collection Tasks
 Online Collection Tasks
o Data Processing
 Call Database Monitoring
 Log Processing Tasks
 Model Tasks
o Engineering Tasks
 Optimization
 Analysis
 Provisioning
 Security
 Regions
 Clusters
 Users
 Antenna Models
Engineer View of the Server Admin Application

Engineer users are responsible for scheduling and monitoring optimization, analysis, and
provisioning tasks in the clusters to which they are assigned.
When an engineer user logs on to the server, the following items are displayed in the
navigation pane on the left of the main window:
 Process Monitoring
o Notifications
o Engineering Tasks
 Optimization
 Analysis
 Provisioning
 Antenna Models
7
Getting Started
This section describes how to start working with the Mentor Server Admin application.
It contains the following sections:
 Logging On to the Mentor Server
 Upgrading the Mentor Server Admin Application
 Viewing and Editing User Properties
 Changing Passwords
 Setting Preferences - Administrators
 Setting Preferences - Engineers
 Logging Off from the Mentor Server
Logging On to the Mentor Server

In order to manage your networks and tasks in the Mentor Server Admin application, you
must first log on to a Mentor Server. The first time you log on to the server, you will be
prompted to specify a host server, and then you will be prompted to reset your password.
Note: The Mentor Server and the Mentor Server Admin application versions must be
compatible. If not, when logging on you will receive a notification enabling you to upgrade to
the compatible version.
To log on to the Mentor Server:
1. Double-click the Server Admin shortcut on your desktop, or click the

icon on the Quick Launch bar.
-OR-
From the Start menu, click Programs > TEOCO System > Server Admin.
The splash screen is displayed while the application is loading.
Note: If this is the first time you are logging on to the server, the New Server dialog
box is displayed.
o In the Server name field, enter a nickname or alias to provide a logical name for
the system. The default name is Mentor Server.
o In the Host field, specify the name of an existing server. If you have a front-end
cluster, enter the name of one of the relevant hosts.
8
Getting Started
o Click OK.
The Log On to Mentor Server dialog box is displayed.
2. In the User name field, enter your user name, as defined by the system
administrator.
3. In the Password field, enter your password, as defined by the system administrator.
4. Depending on whether you have a single server or a front-end clustering server, in
the Server name drop-down list, select the server/server front-end clustering name to
which you want to connect.
Note: The server name represents all the hosts in this cluster, and you will
automatically be connected to any one of them.
5. Click the Advanced button if you want to add a new server group, remove a server
group, or edit the hosts within a server group. The window changes as follows:
9
6. To add a new server group, which can contain multiple servers, click New. The
following dialog box is displayed:
o Enter the name of the new server group in the Server name field.
o For each host you want to add to the group, enter the name of the host in the
Host name field.
o Click Add. The host is added to the list in the Host name area, as shown below:
10
Getting Started
o Click OK. The server group is displayed in the Server area.
o Click OK to save your settings and exit the window.

7. To remove a server group, select the server group and then click Delete.
8. To add or remove the hosts in a server group, click Edit. The Server Properties
window is displayed.
o To add a host to the server group, enter the name of the host to add to the group
in the Host name field and then click Add. The server is added to the list in the
Host name area.
o To remove a host from a server group, select the host and then click Remove.
The host is removed from the server group.
o Click OK to save your settings and exit the window.
11
9. Click OK to log in. The Change Password dialog box is displayed prompting you to
change your password.
o In the Old Password field, enter the password supplied by the administrator.
o In the New password field, enter a new password.
Note: The password must contain at least 8 characters, including an upper-case

letter, a lower-case letter, and a digit. Special characters such as <, >, ., and ? are
not allowed.
o In the Confirm password field, re-enter the new password to confirm it is correct.
o Click OK.
The Mentor Server Admin application opens, showing either the Administrator
Entity Configuration pane or the Engineer Process Monitoring pane, according to
your user type.
12
Getting Started
10. If you are an Administrator user, you can log on to additional servers by selecting the
Log On option on the File menu, or if you have logged on to these servers in
previous sessions, you can right-click them in the Servers pane, and then select Log
On. If the servers have the same user name and password, you can log on to
multiple servers simultaneously. The status of all servers to which you have logged
on is displayed as Connected in the Servers pane.
Upgrading the Mentor Server Admin

In order for the Mentor Server Admin client and the Mentor Server to be compatible and work
together, they have to be from the same version and build. A typical upgrade is initiated when
the Server Admin client tries to establish a connection with a Mentor Server that has been
upgraded, making the versions incompatible.
There are 2 methods by which the Server Admin client can be upgraded:
 Full Installation: The old build is uninstalled during the installation process, and the
new build or version is automatically installed in the same location as the previous
version.
 Quick Upgrade: Involves a much shorter file transfer and installation mechanism,
thereby reducing the time required to upgrade the product.
By default, the full installation is required for a new version release, while a quick upgrade is
run when a new build for the same version becomes available. However, this may change
depending on the nature of the changes within the different product builds, as decided by the
network administrator and defined in the Upgrade Parameters in the advanced server
properties.
To upgrade the Server Admin client while connecting to the Mentor Server:
1. On the Server menu, or in any dialog box prompting you to log on to the server, click
Log On.
If your current version of the Server Admin client is not compatible with the server
version, and only a quick upgrade is required, the Server Connection Failed dialog
box is displayed.
13
o Click Yes to upgrade the Server Admin client. You will be prompted to save any
unsaved networks. The Server Admin will close, a command prompt window with
a script execution will appear for a few seconds, and then the Admin client will
reopen with the same build as the server and a message notifying you of the
successful upgrade.
o If a full installation is required, the following dialog box is displayed, enabling you
to download a compatible version of the client.
o Click Yes to download the compatible version. A security warning is displayed.

2. Click Run and then Run again, and follow the wizard's instructions to perform a full
installation.
14
Getting Started
Viewing and Editing Your User Properties

You can view and edit your own user properties. Note that you cannot change your user type,
or the clusters to which you are assigned.
Administrator users: You can also view and edit properties of other users.
To view your user properties:

1. On the File menu, select User Properties. The User Properties dialog box is
displayed.
15
2. To change your password, click Change. The Change Password dialog box is
displayed.
o In the New password field, enter a new password.
Notes:
 The password must not have been used in the last 6 passwords.
 The password must contain at least 8 characters, including an upper-case
letter, a lower-case letter, and a digit.
 Special characters such as <, >, ., and ? are not allowed.
o In the Confirm password field, re-enter the new password to confirm that it is
correct.
o Click OK.
3. Modify your mobile and e-mail details as required.
4. In the E-mail Notifications field, select whether to enable or disable notifications
about server-related information, or select High only to receive only e-mails with high
priority.
5. Click OK to close the User Properties dialog box and save your changes.
Changing Passwords
By default, passwords are valid for only 60 days. A few days before your password expires, a
message will be displayed when you log in, notifying you to change your password. You can
also change your password at any time before or after it has expired.
 Changing passwords that are about to expire
 Changing expired passwords
 Changing existing passwords
16
Getting Started
Changing Passwords that are About to Expire

A few days before your password is about to expire, the Password Expired dialog box is
displayed after you log in to the server, notifying you that your password is about to expire,
and enabling you to change your password.
To change a password that is about to expire:

1. In the Password Expired dialog box, click OK to choose a new password. The
Change Password dialog box is displayed.
2. In the Old password field, enter your current password.

3. In the New password field, enter a new password.
Notes:
4. In the Confirm password field, re-enter the new password to confirm it is correct.
5. Click OK to save your new password and log on to the Mentor Server. The Mentor
Server Admin application opens, showing the entity configuration according to your
user type.
17
Changing Expired Passwords

If you try logging on to the server after your password has expired, the Change Password
dialog box is displayed, and you will have to enter a new password before you can access the
server.
To log on to the Mentor Server if your password has expired:

1. In the Old password field, enter your current password that has now expired.
Notes:
3. In the Confirm password field, re-enter your new password to confirm that it is
correct.
4. Click OK to save your new password and log on to the Mentor Server. Click OK. The
Mentor Server Admin application opens, according to your user type.
18
Getting Started
Changing Existing Passwords

You can change your existing password at any time. Administrator users can change the
existing password of engineer users at any time.
To change an existing password:

1. Engineer users: On the File menu, click User Properties.
Administrator users: In the Users pane, right-click the user whose password you
want to change, then select Properties.
The User Properties dialog box is displayed.
2. In the Password field, click Change. The Change Password dialog box is displayed.
19
Notes:
4. In the Confirm password field, re-enter the new password to confirm that it is
correct.
5. Click OK to save the changes.
6. Click OK to close the User Properties dialog box.
Setting Preferences - Administrators

Administrator users can set the preferences that apply to units in which measurements are
displayed, as well as to the status bar at the bottom of the Mentor Server Admin window of all
servers to which they are connected. They can also set system-level properties that apply to
the servers in the network.
To set the status-bar preferences:

1. On the File menu, select Preferences. The Preferences dialog box is displayed.
2. In the Length units field, select the units in which measurements should be
displayed.
20
Getting Started
3. In the Status Bar area, select the check box next to the fields you want to display in
the status bar.
o Server connection: Displays whether the Mentor Server Admin is connected to
one or more servers, and if so, the number of servers.
o New notifications: Displays the number of new notifications.
o Running/Failed collection tasks: Displays the number of running and failed
collection tasks.
o Running/Failed model tasks: Displays the number of running and failed model
tasks.
o Running/Failed optimization tasks: Displays the number of running and failed
optimization tasks.
o Running/Failed analysis tasks: Displays the number of running and failed
analysis tasks.
o Running/Failed provisioning tasks: Displays the number of running and failed
provisioning tasks.
4. Click OK to close the Preferences dialog box, and apply your changes.
Setting Preferences - Engineers

You can define general preferences, for example, the fields that are displayed in the status
bar at the bottom of the Mentor Server Admin window. You can also view the system-level
parameters that were set by the administrator.
To set the preferences:

1. On the File menu, select Preferences.
21
The Preferences dialog box is displayed, showing the General tab.
The details of the host to which you are currently connected are displayed in the
Hosts area.
2. In the Status Bar area, select the check boxes next to the fields you want to display
in the status bar:
o Server connection: Displays whether the Mentor Server Admin is connected to
the server, and if so, the name of the server host.
o New notifications: Displays the number of new notifications on the status bar.
o Running/Failed collection tasks: Displays the number of running and failed
collection tasks on the status bar.
o Running/Failed model tasks: Displays the number of running and failed model
tasks on the status bar.
o Running/Failed optimization tasks: Displays the number of running and failed
optimization tasks on the status bar.
22
Getting Started
o Running/Failed analysis tasks: Displays the number of running and failed

analysis tasks on the status bar.
o Running/Failed provisioning tasks: Displays the number of running and failed
provisioning tasks on the status bar.
3. Select the Connections, Excluded Dates, Locked Sectors, or Advanced tabs to
view the system-level parameters that were set by the administrator.
o Connections: Enables you to view the account for the server notifications.
o Excluded Dates: Enables you to view the period that should be excluded from the
optimization and analysis processes.
o Locked Sectors: Enables you to view and define the sectors that will not
automatically be updated following a physical data collection run.
o Advanced: Enables you to view the system-level parameters that are taken into
account when using the Mentor Server.
4. Click OK to close the Preferences dialog box, and apply your changes.
Logging Off from the Mentor Server

You can log off from the Mentor Server at any time. As soon as you log off, you disconnect
from the server, and the application window is shown as empty.
If you are an Administrator user, you can log off from a selected server or from all connected
servers at the same time.
Engineer users:
To log off from the Mentor Server:

1. On the File menu, select Log Off. A confirmation message is displayed.
2. Click Yes. The connection to the server is disconnected, and the Log On to Mentor
Server dialog box is displayed, showing the user name and server used in the
previous session.
23
Administrator users
To log off from the Mentor Server:

1. In the Servers pane, right-click the server from which you want to log off, and select
Log Off. A confirmation message is displayed.
-OR-
If you want to log off from all connected servers, on the File menu select Log Off All.
A confirmation message is displayed.
2. Click Yes. If you have logged off from a selected server, the connection to the server
is disconnected, and the status of the server is displayed as Disconnected in the
Servers pane. If you have logged off from all the connected servers, you exit the
application and the Log On to Mentor Server dialog box is displayed, showing the
last user name and server used in the previous session.
24
User Interface
User Interface
The following shows the Mentor Server Admin user interface for administrator users. For
engineer users, fewer items are displayed in the navigation pane, on the left.
The Mentor Server Admin window is made up of the following window elements:
 Menu Bar
 Toolbar
 Navigation Pane
 View/Edit Area
 Status Bar
Menus
The menu bar contains the following menus, which enable you to perform various tasks in the
Server Admin application, according to whether you are an Administrator or Engineer user.
 File Menu
 View Menu
 Action Menu
 Help Menu
Note: Most menu options are also available in the right-click shortcut menus.
25
File Menu
The File menu contains the following menu options:
Menu Description
Option
New Displays a sub-menu, with the following options:

 Server: Enables you to define a new server.
 Agent: Enables you to define a new agent that can be used for
modeling, collection, and engineering tasks.
 Online Collector: Enables you to define a new online collector that can
be used for monitoring the NSN online collection.
 Data Device: Enables you to define a new data device that can be used
for retrieving the network data.
 Network Element: Enables you to define a new BSC or RNC.
 Physical Data Collection Task: Enables you to define a new physical
data collection task.
 GSM Logs Processing: Enables you to define a new log processing
task for GSM networks.
 Modeling Period: Enables you to define a new modeling period.
 Region: Enables you to define a new region.
 Cluster: Enables you to define a new cluster.
 User: Enables you to define a new user.
 Optimization Task: Enables you to define a new optimization task.
 Analysis Task: Enables you to define a new analysis task.
 Provisioning Task: Enables you to define a new provisioning task.
26
User Interface
Menu Description
Option
Import Displays a sub-menu with the following options:

 Network Elements: Enables you to import one or more previously-
exported network elements that do not exist in a selected server.
 Clusters: Enables you to import one or more previously exported
clusters that do not exist in the current network.
 Users: Enables you to import users from other networks or servers, so
that they can be used in the current or selected server.
 Online Collectors: Enables you to import online collectors from other
servers, so that they can be used in the current or selected server.
 Physical Data Collection Tasks: Enables you to import one or more
previously exported physical data collection tasks, so that they can be
used in the current or selected server.
 Antenna Models: Enables you to import previously exported antenna
models into the antenna model database.
 Terrain: Enables you to import a terrain map.
 Network Properties: Enables you to import previously exported
advanced network properties.
 Data Collection Task Properties: Enables you to import previously
exported advanced data collection task properties.
 Advanced Server Properties: Enables you to import previously
exported advanced server properties.
Export Displays a sub-menu with the following options:

 Network Elements: Enables you to export one or more selected
network elements so that they can be used by other users in additional
servers and networks.
 Clusters: Enables you to export one or more selected clusters so that
they can be used by other users in additional servers and networks.
 Users: Enables you to export one or more selected users so that they
can be used in additional servers and networks.
 Online Collectors: Enables you to export one or more selected online
collectors so that they can be used in additional servers and networks.
 Physical Data Collection Tasks: Enables you to export one or more
selected physical data collection tasks so that they can be used by other
users in additional servers and networks.
 Antenna Models: Enables you to export antenna models from the
antenna model database so that they can be imported into the Mentor
client, to other servers, or for any other use.
 Network Properties: Enables you to export the advanced properties of
one or more selected network elements or clusters.
 Data Collection Task Properties: Enables you to export the advanced
properties of selected data collection tasks so that they can be saved as
a backup, or imported to other tasks.
 Advanced Server Properties: Enables you to export the advanced
server properties so that they can be saved as a backup, or imported to
other networks.
27
Menu Description
Option
Restore Enables you to restore your server database with a previously backed up
version.
Run Backup Enables you to back up your server database at any time, without waiting for
Task a scheduled backup task. You can also schedule a task to back up the
server.
Stop Backup Enables you to stop a running backup task.

Task
Print Enables you to print selected notifications.
Preferences Engineer Users: Enables you to define general network preferences, as

well as view the system-level parameters that were set by the administrator.
Administrator Users: Enables you to set preferences that apply to the
status bar at the bottom of the main Mentor Server Admin window of all
servers to which you are connected.
User Enables you to view and edit your user properties.

Properties
Delete Deletes the selected entity.
Log On Enables you to log on to the Mentor Server.
Log Off Enables you to log off from the Mentor Server.
Log Off All Enables you to log off from all connected servers.
Exit Exits the Mentor Server Admin application.
View Menu
The View menu contains the following menu options:
Menu Description
Option
History Enables you to view the history of a selected network element.
Last Failure Enables you to view details about the last failed task.
Details
Filter Enables you to filter the notifications as well as the collection and
engineering tasks according to date or status.
Clear Filter Clears the previously selected filter.
28
User Interface
Menu Description
Option
Topology Enables you to display a graphic display of the network in order to

Map understand its physical and logical connectivity and hierarchy.
Find Enables you to search for selected items.
Properties Enables you to view and possibly edit the properties a selected item.
Refresh Refreshes the data in the Agents pane.
Action Menu
The Action menu contains the following menu options:
Menu Description
Option
Test Enables you to test the connection between the server and the channel.
Export Stack Enables you to export the stack trace, if required for internal
Trace troubleshooting by TEOCO.
Invoke Agent Enables you to manually update the environment for each network
Update element, so that it is available immediately.
Run Enables you to run a selected task immediately, without having to wait for
its scheduled time.
Stop Enables you to stop a running task.
Recurrence Enables you to define the recurrence of a selected task.
Deactivate Enables you to deactivate the selected network elements or tasks.
Activate Enables you to activate selected previously-deactivated network elements

or tasks.
Physical Enables you to complete the physical data for a selected network element.
Data
Completion
Disable Disables notifications for a selected item in the navigation pane.

Notifications
Enable Enables notifications for a selected item in the navigation pane.

Notifications
Reports Enables you to display reports for a selected task.
29
Menu Description
Option
Create Enables you to create reports that show the status of the collection for
Admin selected network elements in the server.
Reports
Assign Agents Enables you to assign a selected collection, modeling or engineering task
to an agent or agent group.
Assign Region Enables you to assign a region to a selected network element, cluster, or
user.
Merge Enables you to merge identical antenna models so that each model will
Antenna have more than one available profile.
Models
Create REST Enables you to manually run the REST API creation task.
Cache
Help Menu
The Help menu contains the following menu options:
Menu Description
Option
Help Contents Displays this Help file.
TEOCO on Opens the TEOCO Web site.

the Web
TEOCO Enables you to log in to the TEOCO Support Center in the TEOCO web
Support site.
About Server Displays information about the currently installed version, and the license
Admin agreement.
Keyboard Shortcuts
The following keyboard shortcuts are available in the Mentor Server Admin application:
Ctrl+P — Print (File menu)
Delete — Delete (File menu)
Ctrl+Q — Exit (File menu)
Ctrl+H — History (View menu)
Ctrl+F — Find (View menu)
F4 — Properties (View menu)
F1 — Help Contents (Help menu)
30
User Interface
Toolbar
The toolbar, which is displayed below the menu bar, displays buttons for the most common
menu commands.
The toolbar contains the following buttons:
Button Name Description
New Displays a sub-menu that enables you to define new:

 Servers
 Agents
 Data devices
 Network elements
 Physical data collection tasks
 Modeling periods
 Regions
 Clusters
 Users
 Optimization tasks
 Analysis tasks
 Provisioning tasks
Find Enables you to search for selected items.
Properties Enables you to view and edit the properties of selected

items.
Delete Enables you to delete selected items.
Filter Enables you to filter the tasks by various criteria.
Statistics Enables you to display statistics of selected tasks

(modeling, collection, and engineering) as well as the
statistics of one or more connected agents.
Topology Enables you to display a graphical multi-level

Map representation of the server resources.
Note: Most toolbar options are also available in the right-click shortcut menus.
31
Navigation Pane
The navigation pane is displayed on the left side of the main Mentor Server Admin window.
When you select an item in the navigation pane, you can view or edit the item in the pane on
the right.
When you log on to the Mentor Server Admin application, the navigation pane displayed
according to your user type, and the name of the application is displayed in the right pane.
or
32
User Interface
View/Edit Pane
The view/edit pane is displayed on the right of the Mentor Server Admin window. When you
log on to the Mentor Server, the name of the application is displayed in the view/edit pane.
When you select an item in the navigation pane on the left, it displays the details of the
selected item. For example, you can select Model Tasks in the navigation pane on the left to
display all the model task occurrences in the view/edit pane on the right.
The pane is automatically refreshed as soon as there are any changes, for example if a new
task was performed, or if it failed. You can sort the items displayed in the view/edit pane
according to descending or ascending order by clicking any of the column headers. If
required, you can filter the display to show only items that match your filter criteria.
Status Bar
The status bar is displayed at the bottom of the Mentor Server Admin window.
By default, the status bar displays the status of the server connection, the number of new
notifications, and the number of running and failed collection tasks. If required, you can
change the fields that are displayed.
33
Engineer Users
To define the fields in the status bar:

1. On the File menu, select Preferences. The Preferences dialog box is displayed,
showing the General tab.
34
User Interface
2. In the Status Bar area in the lower section of the dialog box, select the fields to be
displayed in the status bar in the Visible status bar fields.
Field Description
Server Whether the Mentor Server Admin is connected to the server, and
connection if so, the name of the server host.
New The number of new notifications that have arrived, and have not
notifications been read.
Running/Failed The number of collection tasks that are currently running, and the
collection number that have failed.
tasks
Running/Failed The number of optimization tasks that are currently running, and
optimization the number that have failed.
tasks
Running/Failed The number of analysis tasks that are currently running, and the
analysis tasks number that have failed.
Running/Failed The number of provisioning tasks that are currently running, and
provisioning the number that have failed.
tasks
3. Click OK to apply your changes and close the Preferences dialog box.
Administrator Users
To define the fields in the status bar:

1. On the File menu, select Preferences. The Preferences dialog box is displayed.
35
2. In the Status Bar area, select the fields to be displayed in the status bar.
Field Description
Server connection Whether the Mentor Server Admin is connected to one or

more servers, and if so, the number of servers.
New notifications The number of new notifications that have arrived, and
have not been read.
Running/Failed The number of collection tasks that are currently running,

collection tasks and the number that have failed.
Running/Failed model The number of modeling tasks that are currently running,
tasks and the number that have failed.
Running/Failed The number of optimization tasks that are currently

optimization tasks running, and the number that have failed.
Running/Failed analysis The number of analysis tasks that are currently running,
tasks and the number that have failed.
Running/Failed The number of provisioning tasks that are currently

provisioning tasks running, and the number that have failed.
3. Click OK to apply your changes and close the Preferences dialog box.
Displaying Table Columns

You can select the table columns to be displayed in all relevant panes and dialog boxes.
Depending on the number of columns in each table, you can right-click the table header and
then do the following:
 Up to 4 columns: Select or clear the check boxes next to the names of the columns
to be displayed.
 4–8 columns: Select or clear the check boxes next to the names of the columns to
be displayed, or hide a specific column, or customize the display by showing or hiding
multiple columns.
 Over 8 columns: Hide the selected column, or customize the display by showing or
hiding multiple columns.
36
User Interface
To hide a column:
1. In the relevant table, right-click a column in the column header. Depending on the
number of columns in the table, a menu is displayed:
2. Click Remove this Column, or clear the check boxes next to the columns to be
hidden. The selected columns are hidden.
To show or hide multiple columns:

1. In the relevant table, right-click the column header and then click Customize. The
Customize Columns dialog box is displayed:
2. Using the arrows, move the columns to be displayed to the Show these columns
pane, and the columns to be hidden to the Available columns pane.
3. Click OK to save your changes and close the Customize Columns dialog box.
37
Searching for Server Items

You can search for any selected server items, according to the item name, or part thereof.
The Server Admin application displays the number of items that match your search criteria,
and enables you to navigate through the matching items.
To search for selected server items:

1. In the navigation pane, select the item type for which you are searching. For example,
Users.
2. On the toolbar, click . The Find <item> dialog box is displayed.
3. In the Find field, enter your search criteria. You can enter the whole name, or part
thereof, of the item for which you are searching.
4. Select the Exact match check box if you know the exact name of the item for which
you are searching.
5. Click Next. The number of items that match your search criteria is displayed in the
title of the dialog box, and the first item is highlighted.
6. Click Next until you find the item for which you are searching.
7. Click Close to close the Find dialog box.
38
Managing Servers
Managing Servers
The Server Admin enables you to log on to multiple servers to view the activities in each one.
The Servers pane displays the details for the servers to which you are currently connected,
or to which you were connected in the past.
If you try making changes to any of the Server Admin features while you are connected to
more than one server, you will be prompted for the server to which to make the changes. If
you are creating a new engineering task, you can create it for one or more selected servers
simultaneously.
The Servers pane is automatically refreshed as soon as there are any changes, for example if
a new server was added, or if a server was disconnected.
The Servers pane contains the following fields:
Field Description
Server The name of the server.
User Name The name of the last user to connect to the server.
Status Whether the Server Admin is currently connected to or disconnected from
the server.
Active Hosts The number of servers currently active in the cluster.
Connected The number of users that are currently connected to the server.
Users
Last Backup The current status of the backup task.
Status
Latest The date and time of the latest successful backup.
Succeeded
Last The date and time the last backup task was performed.
Performed
Recurrence The frequency of the backup task occurrence.
Size The size of the backup file.
Note: By default, some fields are hidden.
You can filter the displayed fields by adding or removing columns.

39
Adding Servers
You can add a new server when logging on to the Mentor Server Admin, or any time
afterwards. After a server has been added, it is displayed in the Servers pane.
To add a server:
1. In the navigation pane, right-click Servers and then select New Server. The New
Server dialog box is displayed.
2. In the Server name field, enter a new name for the server, if required.
3. In the Host field, enter the name of the computer on which the server resides.
4. Click OK. The new server is displayed in the Servers pane, with the rest of the
servers to which you are currently connected, or to which you connected in the past.
Defining Server Properties

Administrator users can set system-level parameters that apply to the network as well as
user-level parameters that apply to all the users in the network. These parameters can be set
for each server, or for multiple connected servers, simultaneously.
To define the server properties:

1. In the Servers pane, right-click the server whose properties you want to define, and
then click Properties.
40
Managing Servers
The Server Properties dialog box is displayed.
The Server Properties dialog box contains the following tabs:

o General, which enables you to rename the front-end cluster and view the details
of all the hosts contained in this cluster.
o Connections, which enables you to define the account for the server notifications.
o Excluded Dates, which enables you to define the periods that should be excluded
from the engineering tasks.
o Backup, which enables you to implement the server backup as a scheduled task,
and define the recurrence of the task.
o Dashboard, which enables you to define the settings for creating the data that is
used for the Insight dashboard.
o Locked Sectors, which enables you to define the sectors that will not automatically
be updated following a physical data collection run.
o Advanced, which enables you to set the system-level parameters that are taken
into account when using the Mentor Server.
2. Edit the fields as required in each of the tabs.
3. Click OK to close the Server Properties dialog box, and apply your changes to the
selected server. A confirmation message is displayed to indicate whether your
changes were applied successfully.
4. Click OK.
41
General Properties
The General tab enables you to rename the front-end cluster, and view the details of all the
hosts in the front-end cluster.
You can view the following information in the General tab:

 Server name: The name of the group of servers making up the front-end cluster. If
required, you can rename the front-end cluster.
 Serving host: The name of the host that is currently serving as the Master.
 Host Name: The name of the host included in the front-end cluster.
 Version: The version of the Mentor Server being used.
 Status: The current status of the server (Active or Not Active)
 Agent Management: The current agent management status of the server (Active or
Passive). Only one host in the front-end cluster can have an Active status at any
given time. The host with the Active status is currently the Master, and is in charge of
task management and scheduling for the cluster. When the Master fails, another host
takes over and becomes the Master. Collection, modeling, and calculation tasks
running on the agents are not affected by a Master failover. If a host leaves the
cluster due to disconnection, that host may need to be manually restarted.
 Connected Users: The number of users that are currently connected to the server.
 Licensed: Whether the server has a valid license.
42
Managing Servers
To rename the front-end cluster:

1. In the Server name field, enter a new name for the front-end cluster.
2. Click OK to apply your changes and close the Server Properties dialog box.
Connection Properties
The Connections tab enables you to define the account settings for server notifications.
To define the connection properties:

1. In the SMTP server field, enter the address of the outgoing mail server.
2. In the SMTP port field, enter the port of the outgoing mail server.
3. In the Account field, enter the e-mail account from which the data is sent.
4. In the User name field, enter the name of the mail server.
5. In the Password field, enter the password for the mail server.
6. Click OK to apply your changes and close the Server Properties dialog box. A
confirmation message is displayed notifying whether your changes were applied
successfully.
7. Click OK.
43
Excluded Dates
The Excluded Dates tab enables you to define the periods that should be excluded from the
optimization and analysis processes. For example, you can exclude periods where there was
not enough data available due to a technical problem, or if the modeling data was inaccurate
due to some major event. If required, you can also edit or remove a previously defined period.
To define the excluded dates:

1. Select the dates to be excluded from the engineering processes from the From date
and To date drop-down calendars.
2. If required, add a reason for the exclusion in the Reason field.
3. Click Add. The excluded dates and the reason for the exclusion are displayed in the
excluded dates area.
4. If required, you can cancel an exclusion period by selecting it in the excluded dates
area, and then clicking Remove. This period will now be included in all future
optimization processes.
successfully.
6. Click OK.
44
Managing Servers
Backup Properties
The Backup tab enables you to implement the server backup as a scheduled task that can be
executed while the server is running, without service interruption or degradation. All the data,
besides notifications and raw information (logs, counters, etc.) is backed up during the backup
process.
If required you can define the backup and restore parameters in the advanced server
properties.
You can also manually back up the server at any time without waiting for its scheduled time
by clicking Run Backup Task on the File menu.
Note: Only the latest version of the backup file is saved. Each occurrence of the backup
overwrites the previous occurrence.
To activate and schedule the backup task:

1. In the Servers pane, right-click the server to be backed up, and then click
Properties. The Server Properties dialog box is displayed.
2. Click the Backup tab.
3. Select the Activate Backup Task check box to activate implementing the server
backup as a scheduled task.
45
4. If required, in the Location field, select or enter the location to which to the data is
backed up on the server.
5. Click Test to verify that the location exists. A confirmation message is displayed if the
location is valid. Click OK.
6. By default, the server will be backed up once a day, at midnight. To change the time
or the frequency, click Recurrence and then define the task recurrence.
7. To view the details of a specific backup occurrence, select the occurrence in the
Latest Occurrences area and then click Details.
o To save the details for future reference, click Save or click Close to close the
Details dialog box.
8. Click OK to save your changes and close the Server Properties dialog box.
46
Managing Servers
Dashboard Properties
The Dashboard tab enables you to define the system level parameters that will be taken into
account when creating dashboard data for the Insight application.
Note: These parameters should be changed by advanced users only.
By default, the parameters are displayed according to parameter group, but you can display
them alphabetically, if required.
 Click to display the parameters alphabetically. Click the column header to sort
the parameters according to parameter name, or value.
 Click to display the parameters according to groups.
47
The following groups of parameters and their default values are displayed:
Configuration Dashboard
Parameter Description
CONFIGURATION_ANALYSIS_JVM_ Advanced parameters for the configuration

ADDITIONAL_PARAMS analysis process, for example, memory
(Default = -Xmx1024M) allocation and so on.
CONFIGURATION_DASHBOARD_ENABLED Whether the Insight application should

(Default = No) include a configuration dashboard.
MAX_AUDIT_DASHBOARD_DAYS_TO_SAV The maximum number of days of server

E usage, for example, number of connected
(Default = 365) users, to save.
MAX_CHANGES_DASHBOARD_DAYS_TO_ The maximum number of days of

SAVE dashboard changes to save.
(Default = 60)
Dashboard Database
DASHBOARD_DATABASE_HOST The name of the host that is running the

dashboard program.
DASHBOARD_DATABASE_ORACLE_ The user name and password used to

PASSWORD access the Oracle database, which
contains the handset statistics and
DASHBOARD_DATABASE_ORACLE_USER neighbor list dashboard.
DASHBOARD_DATABASE_PASSWORD The password used to access the

database.
DASHBOARD_DATABASE_PORT The port used to access the database.

(Default = 1521)
DASHBOARD_DATABASE_SID The type of database. For example, XE

(Express Edition) or SE (Standard Edition)
for Oracle databases.
DASHBOARD_DATABASE_USER The user name used by the database for

the dashboard.
DASHBOARD_DATABASE_USE_TNS Whether to use TNS in the database.

(Default = No)
48
Managing Servers
Dashboard Files Storage
DASHBOARD_STORAGE_DIR The parameters to use when uploading

configuration and KPI dashboard data.
DASHBOARD_STORAGE_FTP_PASSWORD
DASHBOARD_STORAGE_FTP_PORT
(Default = 21)
DASHBOARD_STORAGE_FTP_USER
DASHBOARD_STORAGE_HOST
DASHBOARD_STORAGE_UPLOAD_METHO
D
(Default = FILE_SYSTEM)
Dashboard General
DASHBOARD_DEBUG_DIRECTORY The directory to which the server writes.

This directory is typically for internal use
for troubleshooting and monitoring of a
remote server. It is usually part of the
server's data folder.
Dashboard Task
DASHBOARD_DB_MAX_PARALLEL_ The maximum number of parallel

UPDATE_PROCESSES processes that can be used to update the
(Default = 50) database.
MAX_DASHBOARD_TASK_HISTORY_ The maximum number of days of task

TO_SAVE history to save.
(Default = 365)
49
Equipment Type Dashboard
MAX_HS_DASHBOARD_DAYS_TO_SAVE_ The maximum number of days of handset

DATA statistical data to save.
(Default = 15)
MAX_HS_DASHBOARD_DAYS_TO_SAVE_ The maximum number of days of hourly

HOURS_DATA handset statistical data to save.
(Default = 15)
MAX_HS_DASHBOARD_MONTHS_TO_ The maximum number of months of

SAVE_DATA handset statistical data to save.
(Default = 15)
MAX_HS_DASHBOARD_WEEKS_TO_SAVE The maximum number of weeks of

_DATA handset statistical data to save.
(Default = 15)
MAX_HS_DASHBOARD_YEARS_TO_SAVE_ The maximum number of years of handset

DATA statistical data to save.
(Default = 15)
KPIs Dashboard
KPIS_DASHBOARD_ENABLED Whether the Insight application should

(Default = No) include a KPI dashboard.
MAX_KPIS_DASHBOARD_DAYS_TO_SAVE The maximum number of days of daily KPI

_DAILY_DATA dashboard data to save.
(Default = 60)
MAX_KPIS_DASHBOARD_DAYS_TO_SAVE The maximum number of days of hourly

_HOURLY_DATA KPI dashboard data to save.
(Default = 7)
50
Managing Servers
Neighbor List Dashboard
FIRST_DAY_OF_WEEK The first day of the week, after the

(Default = Monday) weekend.
MAX_INTER_LM_NL_DASHBOARD_DAYS_ The maximum number of days of layer

TO_SAVE_DATA management neighbor list dashboard data
(Default = 2) to save.
Note: TEOCO recommends using not
more than 2 to 3 days of data, as this is a
very heavily processed part of the
dashboard.
MAX_NL_DASHBOARD_DAYS_TO_SAVE_ The maximum number of days of neighbor

DATA list dashboard data to save.
(Default = 31)
Usage Audit Dashboard
MAX_USAGE_DAYS_TO_SAVE The maximum number of days of Mentor

(Default = 60) usage-detail logs to save.
To set the advanced system-level parameters:

1. Click the button next to the parameter group you want to edit. The group is
expanded.
2. Double-click in the Value field next to the parameters you want to change, and enter
or select the new values.
successfully.
4. Click OK.
51
Locked Sectors
The Locked Sectors tab enables you to define the sectors that will not be automatically
updated following a physical data collection run. For example, you can prevent sectors that
were manually corrected from being changed back to their incomplete state if the antennas.txt
file has not yet been updated, or you can protect sectors on which you are working from being
updated.
When you select the Locked Sectors tab, a progress bar is displayed while any previously
selected locked sectors are loaded and displayed in the sectors area.
To define the sectors to be excluded from automatic updates:

1. In the Sector name field, enter the name of each sector that you want to exclude
from the automatic updates and click Add. The sectors are displayed in the sector
area.
2. To exclude a previously-defined sector selection, click Load and then browse to the
selection.
3. To remove previously added sectors, select the sectors and the click Remove. The
sectors are removed from the sectors area, and will be included in the automatic
updates, if relevant.
4. To save the current selection, click Save and then browse to the location in which to
save the selection.
5. Click OK to save your changes and close the Server Properties dialog box.
52
Managing Servers
To save a sector selection:

1. In the Sector name field, enter the name of each sector that you want to exclude
from the automatic updates and click Add. The sectors are displayed in the sector
area.
2. Click Save and then browse to the location in which to save the selection.
To exclude a previously-saved list of sectors:

 Click Load and then browse to the file containing the list of sectors.
To find a previously locked sector:

1. Click Find. The Find dialog box is displayed.
2. Enter the name of the sector, or part thereof, and then click Next. If you know the
exact name of the sector, select the Exact match check box. The number of items
that match your search criteria is displayed in the title of the dialog box, and the first
sector is highlighted in the list of locked sectors.
3. Click Next until you find the sector for which you are searching.
4. Click Close to close the Find dialog box.
53
Advanced Properties
The Advanced tab shows the system-level parameters such as collection, optimizations, and
provisioning that are taken into account when configuring the Mentor Server.
54
Managing Servers
 Agent
 Analysis
 Archive
 Authentication
 Backup/Restore
 Calculations
 Call DB
 Call DB Server
 Call Details
 Collection
 Configuration
 Data Transfer
 Display
 EMS
 Env Model Cache
 Export/Import
 General
 Log Processing
 Model
 Optimizations
 Provisioning
 Tasks
 Upgrade
 Web Map Licenses

expanded.
successfully.
4. Click OK.
55
Agent Parameters
AGENTS_REFRESH_INTERVAL The maximum time after which to refresh the

(Default = 90,000) status of the agents.
HOURS_TO_KEEP_REPOSITORY_AFTER The number of hours to keep folders in the

_NE_DELETE repository after the network element has
(Default = 24) been deleted.
MAINTENANCE_ENV_IMPORT_TIMEOUT The number of minutes the environment-

_MINUTES import task will wait before it times out.
(Default = 120)
MAINTENANCE_INVOCATION_TIMEOUT_ The number of minutes the agent-update

MINUTES task will wait before it times out.
(Default = 300)
VALIDATE_DEVICES_VERSION Whether to prevent agents from previous

(Default = Yes) builds from working with the current front-
end build.
Analysis Parameters
ANALYSIS_JVM_ADDITIONAL_PARAMS Advanced parameters in the analysis

(Default = -Xmx1024M) process, for example, memory allocation.
MAX_ANALYSIS_TASK_HISTORY_TO_ The number of occurrences of the same

SAVE analysis task to save.
(Default = 10)
NUM_MODEL_DAYS_PERF The number of model days to count in the

(Default = 7) analysis.
Archive Parameters
ARCHIVE_INTERVAL The number of hours between each

(Default = 8.0) archiving event.
EXP_DAYS_ARCHIVE_PERSISTENT_ The number of days until persistent data

DATA expires and is archived.
(Default = 14)
56
Managing Servers
Authentication Parameters
DAYS_UNTIL_PASSWORD_EXPIRES The number of days a password is valid,

(Default = 60) before it needs to be renewed.
DAYS_UNTIL_PASS_EXPIRES_WARN The number of days before password

expiration to display a warning of such.
(Default = 5)
DomainDNSName The domain DNS name, for LDAP

authentication.
LDAP_AUTHENTICATION_ENABLED Whether to enable LDAP authentication.

(Default = No)
LDAP_HOST The host for LDAP authentication.
LDAP_PORT The port for LDAP authentication.

(Default = 389)
MAX_DAYS_BETWEEN_LOGINS The number of days after which an unused

account will be revoked.
(Default = 3650)
Note: This is not relevant for system and
integration users.
MAX_LOGIN_FAILURES The number of unsuccessful login attempts

after which the user account will be locked.
(Default = 999)
MIN_ADMIN_PASSWORD_LENGTH The minimum length for administrator-user

(Default = 8) passwords.
MIN_ENGINEER_PASSWORD_LENGTH The minimum length for engineer-user

(Default = 8) passwords.
PASSWORD_STRENGTH Whether the password should be protected.

(Default = Yes) If yes, the password must contain at least
one upper-case letter, one lower-case letter,
and a digit.
57
Backup/Restore Parameters
BACKUP_RESTOR_DB_ONLY Whether to back up only the Oracle

(Default = No) database. If No, all system components will
be backed up.
BACK_UP_SCRIPTS Whether to back up the current scripts, so

(Default = Yes) that they can be restored if required.
COMPRESS_BACKED_UP_DATA Whether to compress the backed up data.

(Default = Yes)
MAX_BACKUP_TASK_HISTORY_TO_ The number of backup occurrences to save.

SAVE
(Default = 5)
NUM_ANTENNAS_PER_BACKUP_FILE The number of antennas to back up, per file.

(Default =100)
NUM_CALC_OCCURRENCES_TO_BACK_ The number of each calculation occurrence

UP that should be backed up.
(Default = 5)
NUM_CONFIG_UPDATES_TO_BACK_UP The number of configuration updates to back

(Default = 1) up.
NUM_MODEL_DAYS_TO_BACK_UP The number of latest model days to back up.

(Default = 14)
NUM_PHYSICAL_DATA_TO_BACK_UP The number of physical data updates to

(Default = 1) back up.
USE_EXISTING_SCRIPTS_WHEN_ Whether to search for scripts in the existing

RESTORE scripts folder rather than copying the ones in
(Default = No) the network element file.
Calculation Parameters
COPY_CALCULATION_REPORTS_ROOT The location in which to save the calculation

(Default = N/A) reports. If N/A, they will not be saved.
Note: Ensure that the server has read/write
access to this folder.
CREATE_DROP_REPORTS_IN_TEXT_ Whether to save the Drop reports in text

FORMAT format.
(Default = No)
58
Managing Servers
Call DB Parameters
Note: TEOCO highly recommends coordinating this feature with your account manager when
installing or operating the call database for the first time.
CALLS_DATA_PULL_DELAY_SECONDS How long a file should be kept in the agent

(Default = 10) before being taken to the call database, in
order to ensure that the file is not currently
being changed.
CALLS_MONITORING_RECURRENCE How often the database will check if there is

(Default = 0 0/10 * * * ?) new data in the server that can be uploaded
to the call database.
CALL_DB_CONCURRENT_UPDATES The maximum number of database-loading

(Default = 5) processes that can work in parallel.
CALL_DB_HOST The call database host.
CALL_DB_PASSWORD The call database password.
CALL_DB_PORT The port used for the call database.

(Default = 1521)
CALL_DB_REPOSITORY_PATH The path for the call database repository.

(Default = N/A) Note: The repository must be saved on the
central system LAN.
CALL_ DB_RETRY_NUM The number of times to retry after a failed

(Default = 3) database query.
CALL_DB_RETRY_WAIT_MILLIS The time to wait before retrying after a failed

(Default = 10,000) database query.
CALL_DB_SID The call database SID.

(Default = DBIIG)
CALL_DB_UPDATE_RECURRENCE How often to upload the available data from

(Default = 0 0/15 * * * ?) the server.
CALL_DB_USER The call database user.

(Default = calls_db_test)
CALL_DB_USE_TNS Whether to use TNS in the call database.

(Default = No)
These parameters can also be viewed and defined in the Advanced Call Database properties.
59
Call DB Server Parameters
CALL_DB_LOCAL_PATH_ON_SERVER The location in the call database machine in

(Default = /u01/oracle_loader) which server data is temporarily stored by
the server.
CALL_DB_SERVER_PASSWORD The password of the call database

(Default = support) administrator user.
CALL_DB_SERVER_USER The user name of the call database

(Default = oracle) administrator user.
These parameters can also be viewed and edited in the Advanced Call Database properties.
Call Detail Parameters
ENABLE_EVENT_VIEWER_CLIENT Whether to enable the client to retrieve

(Default = Yes) event flow viewer data.
Collection Parameters
MAX_COLL_TASK_HISTORY_TO_SAVE The number of occurrences of the same

(Default = 5) collection task to save.
Note: This parameter works in parallel with
the Collected-data limit field, which is set in
the Collected Data tab in the Network
Element Properties dialog box.
MAX_DAYS_OF_GSM_COUNTERS_TO_ The number of days to store the GSM

SAVE counters.
(Default = 10)
MAX_DAYS_OF_PHYSICAL_RAW_DATA_ The number of days of collected physical

TO_SAVE raw data to store.
(Default = 5)
MAX_PHYSICAL_COLL_TASK_HISTORY_ The number of occurrences of the same

TO_SAVE physical data collection task to save.
(Default = 5)
RESET_LAST_COLLECTED_WHEN_IMPO Whether to reset the collection time when

RT importing network elements using the
(Default = No) <internal operation> scripts.
SCRIPT_TASK_PRIORITY The priority of the collection tasks that are

(Default = NORMAL) run using scripts.
60
Managing Servers
TELNET_DATA_DEVICE_PROMPT The list of most probable prompt signs. If

(Default = >, %, $) you are using a different prompt sign, add it
to this list.
USE_SCRIPT_FILE_FILTER Whether to filter the list of scripts shown

(Default = Yes) when adding new collection tasks.
Configuration Parameters
DAYS_OF_DATA_COMPLETION_ The number of days of data completion

REPORTS_TO_SAVE reports to save. These reports are attached
(Default = 5) to the notifications that are sent after the
data has been completed.
DAYS_OF_PHYSICAL_COLLECTION_REP The number of days of physical data

ORTS_TO_SAVE collection reports to save. These reports are
(Default = 5) attached to the notifications that are sent
after the physical data collection tasks are
completed.
DAYS_OF_SUBMIT_REPORTS_TO_SAVE The number of days of submitted data

(Default = 5) reports to save. These reports are attached
to the notifications that are sent after the
changes are submitted.
FORCE_IMPORT_TERRAIN Whether to enable users to overwrite the

(Default = No) terrain map in the Mentor, Mentor Sparks, or
Forte clients when importing a network from
the server.
FORCE_SUBMIT_TERRAIN Whether to enable Server Admin users to

(Default = No) overwrite the terrain map on the server when
submitting changes.
MAX_DAYS_OF_CONFIG_DATA_TO_ The maximum number of days of

SAVE configuration data to save.
(Default = 60)
MAX_DAYS_OF_SWITCH_DUMP_TO_ The maximum number of days of switch

SAVE dump data to save.
(Default = 10)
SYNC_ENABLED_BY_DEFAULT Whether to automatically search for updates

(Default = Yes) on the client. When set to No, automatic
updates on the client are disabled. When set
to Yes, automatic updates are enabled,
which means that the client automatically
searches for updates that have already been
downloaded from the server.
61
TERRAIN_BIN_SIZE The default bin size of terrain maps in the

(Default = 100) server.
WB_SECTOR_CARRIER_LIMIT The maximum allowed number of sector

(Default = 11,000) carriers per cluster, in order to prevent
service degradation and out of memory
issues.
Data Transfer Parameters - Server
AGENTS_FTP_DOWNLOAD_RETRIES The number of times the agent will

(Default = 20) attempt downloading from the FTP.
AGENTS_FTP_DOWNLOAD_RETRY_INTERVAL The number of seconds the agent will

(Default = 60) wait between each attempt to
download from the FTP.
AGENTS_FTP_DOWNLOAD_TIMEOUT The number of milliseconds before the

(Default = 0) agent's download from the FTP times
out.
BUILDS_DOWNLOAD_METHOD The method to be used for

(Default = FTP) downloading builds from the server.
DATA_DOWNLOAD_METHOD The method to be used for

(Default = FTP) downloading data from the server.
DATA_UPLOAD_METHOD The method to be used for uploading

(Default = FTP) data to the server.
ENABLE_FTP_DATE_FIX Whether to enable fixing FTP time

(Default = No) zone errors.
FTP_SESSION_COUNT The number of parallel FTP sessions

(Default = 1) when downloading data from the
server.
HTTP_SESSION_COUNT The number of parallel HTTP sessions

(Default = 1) when downloading data from the
server.
LOCAL_FTP_PORT The port to use for the FTP server.

(Default = 10021)
PASSIVE_FTP_PORTS The passive ports used for the FTP.

(Default = 10022–10122)
62
Managing Servers
Display Parameters
MIN_TASK_DETAILS_LEVEL The minimum severity level to display for

(Default = DEBUG) task details.
 DEBUG: Only debug-level details are
displayed.
 INFO: Debug and info-level details are
displayed.
 WARN: Debug, info, and warning-level
details are displayed.
 ERROR: Debug, info, warning, and
error-level details are displayed.
EMS Parameters
EMS_CONNECTION_TIMEOUT The amount of time the server will wait for a

(Default = 60) response from the EMS client before the
action fails.
JMS_IP_ADDRESS The JMS IP address, used for automatic

provisioning.
QUE_CREATION_TIMEOUT The amount of time the server will wait for a

(Default = 60,000) response from the EMS client before the
action fails.
Env Model Cache Parameters

CLEAN_CACHE_ON_STARTUP Whether to clean the cache on startup.

(Default = No)
ENV_MODEL_CACHE_SIZE_MB The size of the environment model and

(Default = 3,000) cache in the SF-cache folder.
USE_LOGS_ON_MDL_MERGE_FOR_CALC Whether to use a "quick model" based on

(Default = No) performance counters only. (Can be used
analysis and neighbor list calculations only).
Export/Import Parameters
COMPRESS_EXPORTED_DATA Whether to compress the exported data.

(Default = Yes)
63
EXPORT_SCRIPTS Whether to export scripts when exporting

(Default = No) the network element.
NUM_CALC_OCCURRENCES_TO_EXPORT The number of each calculation occurrence

(Default = 1) that should be exported.
NUM_CONFIG_UPDATES_TO_EXPORT The number of days for which to export the

(Default = 1) switch data.
NUM_MODEL_DAYS_TO_EXPORT The number of latest model days to export.

(Default = 14)
NUM_PHYSICAL_DATA_TO_EXPORT The number of days for which to export the

(Default = 1) physical data.
USE_EXISTING_SCRIPTS_WHEN_IMPORT Whether to search for scripts in the existing

(Default = No) scripts folder rather than copying the ones
in the network element file.
General Parameters
COLLECTOR_SERVICE_REFRESH_ The number of milliseconds after no new

INTERVAL data is received before the collector service
(Default = 90,000) is refreshed.
FILE_STORAGE_TYPE For future use.

(Default = DAS)
DAS: Direct-attached storage
NAS: Network-attached storage
SAN: Storage area network
LENGTH_UNITS The length unit to in server reports.

(Default = Km)
LOCAL_DIR_FOR_MERGE The directory in which to perform the

intensive i/o of the front end server. If this
field is left empty, the shared storage (NAS)
will be used.
MAX_DAYS_OF_NOTIFICATIONS_TO_ The number of days for which to save

SAVE notifications and display them in the
(Default = 60) application.
MAX_PARALLEL_ENV_MERGE_ The maximum number of parallel

PROCESSES environment merge processes on the front
(Default = 10) end.
64
Managing Servers
NOTIFICATION_DATE_TIME_FORMAT The format in which the date and time are

(Default = MM/dd/yy hh:mm:ss) displayed in notifications.
USE_NOTIFICATIONS Whether to enable notifications receiving

(Default = Yes) notifications.
WEEKEND The weekend days.

(Default = Saturday, Sunday)
Log Processing Parameters
ENABLE_GSM_CALL_TRACE Defines whether GSM call traces have

(Default = No) been enabled for virtual drive test maps.
MAX_LOGS_PROCESSING_HISTORY_ Defines the maximum number of days of

TO_SAVE task history to save.
(Default = 12)
Model Parameters
DISPATCHER_REQUEST_TIMEOUT The number of minutes within which the

(Default = 3) dispatcher must respond to a request
before it times out.
MAX_DAYS_BACK_FOR_CALIBRATION The maximum number of days to store

(Default = 7) processed artifacts used for data
calibration.
MAX_DAYS_OF_MODELING_DATA_TO_ The maximum number of days for which

SAVE the modeling data should be saved. This
(Default = 30) number should be at least the number of
days required to run an optimization task.
MAX_DAYS_OF_MODEL_REPORTS_TO_ The number of days to save model reports.

SAVE
(Default = 5)
MAX_HHO_SAMPLES The maximum number of hard handoffs in

(Default = 1,000,000) the model.
MAX_MODEL_TASK_HISTORY_TO_SAVE The number of occurrences of the same

(Default = 20) modeling task to save.
65
MAX_NEIGHBOR_NES_DISTANCE The distance within which a network

(Meters/Feet) element must be situated in order to be
(Default = 10,000/32,810) considered a neighbor.
MAX_UE_TX_POWER_SAMPLES The maximum number of UE Tx power

(Default = 2,000,000) records in the model.
MODEL_ENABLED Whether the model will run.

(Default = Yes)
NEIGHBOR_NE_MATCHING The method used for determining the

(Default = DISTANCE) neighboring network elements, which will
be affected by the modeling:
 DISTANCE: Network elements within a
specified distance of the network
element being modeled, based on the
MAX_NEIGHBOR_NES_DISTANCE
parameter, are considered neighbors.
 NONE: Only the network element being
modeled is taken into consideration.
 JOINEDCLUSTER: Enables you to
select the clusters whose sector carriers
will be included in the modeling
calculation set. By default, all clusters to
which the network element belongs are
included.
OPERATOR_IMSI_PREFIXES The MCC and MNC of the network

operator, written as <MCC>:<MNC>. These
parameters should be configured before
working on the server.
POSITIONING_ENABLED Whether the model will be positioned.

(Default = Yes)
Optimization Parameters
CREATE_SCRIPTS_FOR_ANTENNA_ Whether export scripts will be created after

OPTIMIZATION_PROVISIONING the antenna sectors plan optimization in
(Default = No) the server has ended.
CREATE_SCRIPTS_FOR_NL_PLAN_ Whether export scripts will be created after

PROVISIONING the neighbor list plan optimization in the
(Default = No) server has ended.
CREATE_SCRIPTS_FOR_SC_ Whether export scripts will be created after

OPTIMIZATION_PROVISIONING the SC optimization in the server has
(Default = No) ended.
66
Managing Servers
HOURS_TO_KEEP_ON_THE_FLY_TASKS The number of hours after which to refresh

(Default = 24) "on-the-fly" optimization tasks.
MAX_DAYS_OF_IMPL_PLAN_TO_SAVE The maximum number of implementation

(Default = 5) days to save.
MAX_EVALUATIONS The total maximum number of evaluations

(Default = 100) to execute in the optimization before
stopping the calculation run.
Note: If this number is too large the
optimization will fail, and if it is not large
enough, the results will not be accurate.
The optimization will be terminated as
soon as one of the following parameters is
reached:
 MAX_EVALUATIONS
 MAX_OPT_EXE_TIME_MIN
MAX_OPT_EXE_TIME_MIN The maximum optimization time, in

(Default = 10) minutes, after which the calculation run is
stopped.
The optimization will be terminated as
soon as one of the following parameters is
reached:
 MAX_EVALUATIONS
 MAX_OPT_EXE_TIME_MIN
MAX_OPT_TASK_HISTORY_TO_SAVE The number of occurrences of the same

optimization task to save.
(Default = 10)
NBRGSM_JVM_ADDITIONAL_PARAMS Advanced parameters for the Forte

(Default = -Xmx1024M) neighbor list optimization process, for
example memory allocation, and so on.
NL_JVM_ADDITIONAL_PARAMS Advanced parameters for the Mentor

(Default = -Xmx1024M) neighbor list optimization process, for
example, memory allocation, and so on.
NUM_MODEL_DAYS_NBRGSM_OPT The number of modeling days that will be

(Default = 5) counted for Forte neighbor list
optimizations.
NUM_MODEL_DAYS_NL_OPT The number of modeling days that will be

(Default = 5) counted for Mentor neighbor list
optimizations.
NUM_MODEL_DAYS_OFP_OPT The number of modeling days that will be

(Default = 5) counted for Forte frequency plan
optimizations.
67
NUM_MODEL_DAYS_OSP_OPT The number of modeling days that will be

(Default = 5) counted for Forte load balancing
optimizations.
NUM_MODEL_DAYS_OVERSHOOT_OPT The number of modeling days that will be

counted for Mentor e-tilt and overshooting
(Default = 5)
optimizations.
NUM_MODEL_DAYS_QE_EVAL The number of modeling days that will be

(Default = 5) counted for Forte quality evaluation runs.
NUM_MODEL_DAYS_SC_OPT The number of modeling days that will be

(Default = 5) counted for Mentor scrambling code
optimizations.
NUM_MODEL_DAYS_SECTOR_PLAN_OPT The number of modeling days that will be

(Default = 5) counted for Mentor power and tilt
optimizations.
Provisioning Parameters
COPY_IMPLEMENTATION_PLAN_ROOT The folder to which to copy scripts

(Default = N/A) generated by the optimization.
FTP_IMPLEMENTATION_PLAN_ROOT The folder to which to upload scripts

(Default = ftp://[user ID]:[password]@[host generated by the optimization.
name]:[port]/[path name])
MAX_PROVISION_TASK_HISTORY_TO_ The number of occurrences of the same

SAVE provisioning task to save.
(Default = 20)
Task Parameters
DEVICES_RECOVERY_MINUTES The number of minutes to wait for

(Default = 10) communication recovery before declaring a
failed task.
MAX_DAYS_OF_TASK_LOGS_TO_SAVE The number of days of task logs to save.

(Default = 14)
MAX_TASKS_STATISTICS The number of task statistics to save.

(Default = 25)
68
Managing Servers
MIN_TASK_LOG_LEVEL The minimum log level to display for tasks.

(Default = INFO)
TASKS_QUEUE_TIMEOUT_MINUTES The number of minutes the task can wait in

(Default = 360) the queue before being canceled.
TASK_RERUNS_DUE_TO_ The number of attempts to rerun a task that

DISCONNECTION failed due to agent disconnection.
(Default = 3)
Upgrade Parameters
CLIENT_RAM_THRESHOLD The physical RAM (GBs) required for a 64-

(Default = 6) bit client to trigger a 64-bit download.
CLIENT_VERSION_MISMATCH_POLICY Defines what should be done if there is a

(Default = BUILD_OR_PATCH) mismatch between the client and Server
Admin versions:
 IGNORE: The mismatch will be ignored.
Note: This should be used only for
internal testing or troubleshooting.
 BUILD: A full installation will be
required.
 BUILD_OR_PATCH: A new build or a
quick patch will be required, depending
on the version and build defined in the
VERSIONS_FORCE_BUILD
parameter.
 FAIL: The login will fail.
Note: This should be used only for
internal testing or troubleshooting.
OFFER_64_BIT_CLIENTS Whether to enable 64-bit downloads when

(Default = Yes) updating the client.
If set to No, only 32-bit applications will be
available when downloading updates.
VERSIONS_FORCE_BUILD The version number that requires a full

upgrade if there is a mismatch between the
client and the Server Admin versions.
69
Web Map Licenses
GOOGLE_MAPS_CHANNEL Free text field that can be used to

distinguish Mentor usage in your Google
account.
GOOGLE_MAPS_CLIENT_NAME The user's client ID for Google maps.

If the user has a Google maps account,
Google maps will be displayed in the
background.
GOOGLE_MAPS_SIGNATURE The user's password for Google maps.

If the user has a Google maps account,
Google maps will be displayed in the
background.
PROXY_PASSWORD The password for connecting to the proxy

server.
PROXY_PORT The port used for the proxy server.

(Default = 80)
PROXY_SERVER_NAME The name of the proxy server.
PROXY_USER_NAME The user name for connecting to the proxy

server
70
Managing Servers
Defining Multi-selection Server Properties

Administrator users can set system-level parameters for multiple connected Mentor Servers,
simultaneously. These parameters will be taken into consideration when configuring the
selected servers.
Note: The parameters should be changed by advanced users only.
To define multi-selection server properties:

1. In the Servers pane, right-click the servers whose properties you want to define. The
Server Properties (Multi-selection) dialog box is displayed.
By default, the parameters are displayed according to parameter group, but you can
display them alphabetically, if required.
o Click to display the parameters alphabetically. Click the column header to

sort the parameters according to parameter name, or value.
o Click to display the parameters according to groups.
71
The following groups of parameters, and their default values, are displayed:
o Agent
o Analysis
o Archive
o Authentication
o Backup/Restore
o Calculation
o Call DB
o Call DB Server
o Call Detail
o Collection
o Configuration
o Data Transfer
o Display
o EMS
o Env Model Cache
o Export/Import
o General
o Log Processing
o Model
o Optimization
o Provisioning
o REST API
o Task
o Upgrade
expanded.
3. Double click in the Value field next to the parameters you want to change, and enter
Note: If the current value is the same in all selected servers, it is displayed. If the
value is different, an empty field is displayed.
4. Click OK to apply your changes and close the Server Properties (Multi-selection)
dialog box. A confirmation message is displayed notifying whether your changes were
applied successfully. If the changes were not applied successfully to one or more of
the servers, click Details to view the names of the servers to which the changes were
not applied.
5. Click OK.
72
Managing Servers
Server Maintenance
 Testing Server Connectivity
 Exporting a Stack Trace
 Invoke Agent Update
 Deleting Old Files
 Backing Up the Server
 Restoring the Server Data
Testing Server Connectivity

The Server Admin enables you to test the connectivity of a specific server.
To test server connectivity:

1. In the Servers pane, right-click the server whose connection you want to check and
select Test. A progress bar is displayed while the connectivity is being tested, and
then a confirmation message is displayed, showing the status of the connection.
2. If the connection failed, click Details to view the details of the connectivity failure.
Exporting a Stack Trace

The Export Stack Trace command provides a trace dump about an event as that event
occurs, in order to provide a snapshot of a current problem. It is typically used for debugging,
and can be sent to support personnel for further analysis.
To export a stack trace:

1. In the Servers pane, right-click the server for the stack trace operation and select
Export Stack Trace. The Select Folder dialog box is displayed.
2. Select a folder to which to export the stack trace.
Note: This folder must be accessible to all server devices.
3. Click Save. A message is displayed notifying that the stack trace has been exported.
4. Click OK.
73
Updating the Network Element Environment

The log processing task runs on the latest network-element environment, which is
automatically downloaded to a specific repository folder. If required, you can manually update
the environment for each network element, so that it is available immediately.
To manually update the agent:

1. In the Servers pane, right-click the servers whose network-element environments
you want to update, and then click Invoke Agent Update. A dialog box is displayed
notifying that the update process has started.
2. Click OK.
Deleting Old Files

You can remove temporary files used for performing tasks in order to free up disk space. Any
obsolete files older than two days will be deleted.
To delete old files:

1. In the Servers pane, right-click the server from which to delete the files, and then
click Clean Old Files. A dialog box is displayed notifying that the operation is in
progress.
2. Click OK to close the dialog box.
Backing Up the Server

The server can be backed up, as follows:
 Manually by clicking File and then Run Backup
 Automatically as a scheduled task
After the server has been backed up, you can restore the data at any time.
74
Managing Servers
Restoring the Server Data

You can at any stage replace the current Mentor Server database with a previously backed
up version of the database.
Note: Restoring the data will overwrite the existing data.
To restore the server data:

1. In the Servers pane, right-click the server whose data you want to restore, and then
click Restore. A confirmation message is displayed, notifying you that the existing
data will be overwritten.
2. Click OK to continue.
Importing Advanced Server Properties

You can import previously-exported advanced server parameters from the current server or a
different server, so that they can be used in the current server.
To import the advanced server properties:

1. On the File menu, click Import and then Advanced Server Properties. The Import
dialog box is displayed.
2. Browse to the required .properties file, and then click Open. A progress bar is
displayed while the server properties are being imported, and then the Import
Completed dialog box is displayed, notifying whether the file was successfully
imported.
75
Exporting Advanced Server Properties

You can export the advanced server parameters so that they can be restored in the future, or
imported to a different server.
To export the advanced server properties:

1. In the Servers pane, select the server whose advanced properties you want to
export.
2. On the File menu, click Export and then Advanced Server Properties. The Export
3. Browse to the location to which to export the advanced parameters, enter a name for
the properties file, and then click Save. A progress bar is displayed while the
properties are being exported, and then the Export Completed dialog box is
displayed, notifying whether the file was successfully exported.
76
Managing Servers
Importing Terrain Files

You can import a terrain file for a selected server.
To import a terrain file:

1. In the Servers pane, right-click the server to which to import the terrain file.
-OR-
Select the server, and on the File menu, click Import and then Terrain.
A standard Windows dialog box is displayed enabling you to browse to the required
terrain file.
Note: Currently only .tif and .tiff files can be imported.
2. Select the required terrain file, and click Open.

If the selected terrain does not use a standard projection, a dialog box is displayed,
enabling you to select its projection.
o Select the projection from the drop-down list, and then click OK.
77
A progress bar is displayed while the terrain file is being imported, and then a dialog
box is displayed notifying you whether the import completed successfully.
3. Click Close.
78
Managing Agents
Managing Agents
Agents are used for modeling, collection, and engineering tasks.
The Mentor Server distinguishes between two types of agents—Local belonging to the
Central System, and Remote belonging to remote sites:
 Local: Local agents are part of the Central System agent group. These agents
share the same raw data storage as the front end.
 Remote: Remote agents belong to a Remote Site agent group. These agents
reference different raw data storage than the front end. Multiple agents can comprise
a remote agent group, which means that all of the agents in a group share the same
raw data storage.
Each agent has a storage ID that is automatically generated during installation. If an agent is
not part of an agent group, then its storage ID is unique. Agents that are part of an agent
group share the same raw data storage and have the same storage ID.
For example, in the figure above, the Central System agent group consists of three agents,
each of which shares the same data storage as the front end. There are also two discrete
Remote Site agent groups, with each group containing three agents. Each Remote Site agent
group shares the same raw data storage among its group of agents.
The use of agent groups improves load balancing and resilience in the system. If a task is
assigned to an agent that is part of an agent group, and that agent cannot for some reason
execute the task, then another agent from that group can take over when necessary to
execute the task.
79
The Agents pane displays the details for each of the agents belonging to the servers to which
you are currently connected.
The Agents pane contains the following fields:
Field Description
Error Displays if there is a connectivity issue.
Agent The name of the agent.
Server The name of the server to which the agent belongs.
Status The status of the agent—Connected or Disconnected.
Disconnection The reason the agent was disconnected, or cannot connect.

Reason
Running Tasks The number of tasks belonging to the agent that are currently running.
No. of CPUs The number of CPUs in the agent.
RAM (GB) The amount of RAM in the agent.
Free Disk The amount of free space in the agent.

Space
Storage ID The storage ID assigned to the agent during installation. Agents that are
part of an agent group share the same raw data storage and have the
same storage ID.
Version The server version being used.
Local Temp The path of the temporary location to which to run the model on the agent.
Folder
80
Managing Agents
Adding Agents
Agents are used for running modeling, collection, and engineering tasks. By default, all
agents belong to the Central group.
To add an agent:
1. In the navigation pane, right-click Agents and then select New Agent. If you are
currently connected to more than one server, you will be prompted to select the
server to which to add the agent.
o Select the server from the drop-down list and click OK.
The New Agent dialog box is displayed.
2. Enter the name of the computer to be used as the agent.

3. Click OK. The new agent is displayed in the Agents pane, with the rest of the agents
belonging to the servers to which you are currently connected.
Viewing Agent Properties

You can view and edit the properties of a selected agent while creating a new network
element, or at any time afterwards.
You can also change the computer that is used as the agent.
To view the agent properties:

1. In the Agents pane, right-click the agent whose properties you want to view or edit,
and the select Properties.
81
The Agent Properties dialog box is displayed, showing the General tab.
The Agent Properties dialog box contains the following tabs:
o General, which displays general properties of the computer that is used as the
agent, such as the number of running tasks, and the amount of disk space or
RAM.
o Advanced, which displays the advanced agent parameters that are taken into
account for modeling and engineering tasks.
82
Managing Agents
3. To change the computer used as the agent, click Change. The Change Computer
o Enter the name of the new computer, and click OK.

4. Click OK to close the Agent Properties dialog box and apply your changes to the
selected agent. A confirmation message is displayed, notifying whether your changes
were applied successfully.
5. Click OK.
Agent General Properties

The General tab displays the general properties of the computer that is used as the agent, for
example the number of running tasks, and the disk space and the amount of RAM.
83
To set the general agent properties:

1. In the Computer area, click Change if you want to change the computer that is used
as the agent. The Change Computer dialog box is displayed.
o In the New computer field, enter the name of the computer to be used as the
agent.
o Click OK.
2. Select the Active check box to activate the agent.
3. Click OK to apply you changes and close the Agent Properties dialog box. A
successfully.
4. Click OK.
Agent Advanced Properties

The Advanced tab shows the parameters that are taken into account for the agents.
84
Managing Agents

 Data Transfer Parameters
 General Parameters
 Insight Agent Parameters
 Insight Agent Setting Parameters
 KPI Aggregator Parameters
 Retention Parameters
 Service Parameters
To set the advanced agent parameters:

expanded.
3. Click OK to apply your changes and close the Agent Properties dialog box. A
successfully.
4. Click OK.
Data Transfer Parameters - Agent

DATA_DOWNLOAD_METHOD The method used for downloading data from the

(Default = FTP) server.
DATA_UPLOAD_METHOD The method used for uploading data to the server.

(Default = FTP)
DOWNLOAD_TO_TEMP Whether to make the agent fetch every file to the

(Default = No) temp folder before copying it to the raw data folder,
when using the FTP file system. This method
should be used when working with NAS, since
fetching directly to NAS is reportedly much slower.
FTP_SESSION_COUNT The number of parallel FTP sessions when

(Default = 1) downloading data from the server.
HTTP_SESSION COUNT The number of parallel HTTP sessions when

(Default = 1) downloading data from the server.
85
LOCAL_FTP_PORT The port to use for the FTP server.

(Default = 10021)
PASSIVE_FTP_PORTS The passive ports used for the FTP.

(Default = 10022-10122)
General Parameters - Agent
ENV_DIR The directory in which the agent stores the network

that will be saved for log processing.
LOCAL_TEMP_DIR The directory in which to save the archived data.
Insight Agent Parameters
DATA_ROOT The root folder for Insight data.

(Default = c:\KPIs\Data)
GUI_LOAD_SCRIPT The script for reloading the QlikView GUI.

(Default = Update_GUI_File.bat)
IS_INSIGHT_AGENT Whether the agent is an Insight agent.

(Default = No)
MODEL_NAME The name of the Insight model.

(Default = Schema Dashboard)
QV_INSTALLATION_ROOT The root folder for the QlikView installation.

(Default = C:\Program Files\QlikView)
QV_ROOT The root folder for QlikView.

(Default = C:\qv)
QV_STORAGE_ROOT The root folder for the QlikView storage.

(Default = C:\Storage)
SPARKS_MODEL_NAME The name of the Mentor Sparks model.
86
Managing Agents
Insight Agent Setting Parameters
CustomerName The customer name to be used in the Excel

(Default = Generic) selection.
CustomerTechnology The technology to be displayed in the Neighbor List

(Default = UMTS) dashboard.
DefaultAuditDailyDaysToKeep The number of audit days to save in the storage.

(Default = 365)
DefaultChangesDailyDaysToKeep The number of change days to save in the storage.

(Default = 60)
DefaultDropsDailyDaysToKeep The number of drop days to save in the storage.

(Default = 60)
Environment Whether the environment is for development (D) or

(Default = P) production (P).
IsIncrementalLoading Whether there is an incremental reload for

(Default = 1) configuration. (0=False, 1=True)
IsMultiVendor Whether Insight should support more than one

(Default = 0) vendor. (0=False, 1=True)
KpisDailyDaysToKeep The number of KPI days to save in daily resolution

(Default = 14) in the storage.
KpisHourlyDaysToKeep The number of KPI days to save in hourly resolution

(Default = 14) in the storage.
RNC_label The way the RNC name will be displayed.

(Default = RNC)
vMarketsplitflag Whether the final GUI model should be split into

(Default = 0) smaller models. (0=False, 1=True)
vQtyDropsCondition The maximum number of call faults that can be

(Default = 3000) displayed in the call fault maps.
vQtyRncCondition The maximum number of RNCs that can be

(Default = 4) included in the model.
87
KPI Aggregator Parameters
AGGREGATOR_LOGS_FOLDER The root folder for the KPI aggregator logs.

(Default = c:\KPIs\Logs)
AGGREGATOR_ROOTS_FOLDER The root folder for the KPI aggregator installation

(Default = c:\KPIAggregator) files.
DAILY_DEVICES_DAYS_TO_KEEP The number of days of daily aggregation data of the

(Default = 15) devices to keep.
DAILY_MOBILITY_DAYS_TO_KEEP The number of days of daily aggregation of the

(Default = 15) mobility data to keep.
FIRST_DAY_OF_THE_WEEK The first day of the week.

(Default = Monday)
KPIS_AGG_WINDOW The time window in which the KPI aggregator

(Default = [07:00-13:00], should run.
[13:00-15:00])
MONTHLY_DEVICES_MONTHS_TO The number of months of monthly aggregation data

_KEEP of the devices to keep.
(Default = 15)
VERBOSE Whether the KPI aggregator should generate logs.

(Default = Yes)
WEEKLY_DEVICES_WEEKS_TO_ The number of weeks of weekly aggregation data of

KEEP the devices to keep.
(Default = 15)
Retention Parameters
CONFIGURATIONS_RETENTION_ The size of the configuration cache in MB, per

SIZE_MB_PER_NE network element.
CONFIGURATION_MAX_DAYS_TO The number of days of configuration data to save.

_SAVE
(Default = 5)
DELETE_METHOD The method by which the data is selected for

(Default = BY_LAST_MODIFIED) deletion from the agent.
 BY_CONTENT: According to the date of the
content.
 BY_LAST_MODIFIED: According to the
modification date.
88
Managing Agents
INTERNAL_ARTIFACTS_MAX_ The number of days of internal artifacts to save.

DAYS_TO_SAVE
(Default = 5)
INTERNAL_ARTIFACTS_ The size of the internal artifact cache in MB, per

RETENTION_SIZE_MB_PER_NE network element.
KPS_RETENTION_SIZE_MB_PER_ The size of the KPI cache in MB, per network

NE element.
KPIS_MAX_DAYS_TO_SAVE The number of days of collected KPI data to store.

(Default = 5)
LOGS_MAX_DAYS_TO_SAVE The number of days of collected raw log data to

(Default = 5) save.
LOGS_RETENTION_SIZE_MB_PER The size of the log cache in MB, per network

_NE element.
PROCESSED_LOGS_MAX_DAYS_ The maximum number of days of log processing

TO_SAVE artifacts to save.
(Default = 5)
PROCESSED_LOGS_RETENTION_ The size of the processed log cache in MB, per

SIZE_MB_PER_NE network element.
Service Parameters - Agent

ANALYSIS Whether the service is supported by the server.

(Default = Yes)
COLLECTION
(Default = Yes)
LOGSPROCESSING
(Default = Yes)
MODEL
(Default = Yes)
MULTICALCULATION
(Default = Yes)
NBRGSM
(Default = Yes)
89
NL
(Default = Yes)
OFP
(Default = Yes)
OSP
(Default = Yes)
PROVISIONING
(Default =Yes)
QE
(Default = Yes)
SC
(Default = Yes)
SECTOR_PLAN
(Default = Yes)
Assigning Agents
You can assign a collection, physical data collection, modeling, or engineering task to an
agent or agent group. When a task is assigned to a specific agent, only that agent can
execute the task. When a task is assigned to an agent group, any agent within that group can
execute the task. By default, tasks are assigned to the Central System agent group.
To assign agents to a task:

1. In the navigation pane, right-click the tasks to which to assign an agent, and then
click Assign Agents.
90
Managing Agents
The Assign Agents dialog box is displayed.
Note: You can also right-click a single task, click Properties and then the Agents
tab.
91
By default, the Filter agents by storage ID check box is selected, and only the
agents in the Central system agent group are displayed. You can clear the check box
to display all agents, and not only those in the Central System agent group.
The Computer column specifies the name of the computer on which the agent
resides.
The Storage ID column identifies the storage ID for the agent, and also shows the
name of the agent group to which agent group belongs, in parentheses.
2. Select the agent group from which to select the agents for the task. If you have
selected the Filter agents by storage ID check box, only the agents in the selected
group are displayed.
3. Select the check boxes next to the agents to assign to the task.
4. Click OK to save your changes and close the Assign Agents dialog box.
92
Managing Agents
Viewing Agent Statistics

You can view the statistics of one or more connected agents, for all agent tasks, or only
selected tasks. Agent statistics represent the utilization of the agent, and enable you to
determine why a task failed.
To view the agent statistics:

 In the navigation pane, right-click the required agent and then click Statistics.
-OR-
Select the agent in the navigation pane and then click in the toolbar.
The Agent statistics dialog box is displayed.
Use the drop-down list at the top-left of the window to select the type of graph to
display. You can select from the following options:
o Utilization Statistics: Displays utilization statistics for the selected agent.
o Utilization Per Agent: Displays utilization statistics for multiple agents. This
option enables you to compare between agents.
93
o Agent Tasks: Displays a Gantt chart for the selected agent. This option is only
available when selecting a single agent.
Note that a separate graph is shown for each agent selected for the comparison.
The Model, Analysis, Neighbor List Optimization, and Antenna Sectors

Optimization check boxes each correspond to a task type. Select the relevant check
boxe(s) to display data for that type of task in the graph.
94
Managing Agents
The pane on the bottom left displays the list of agents. Select the check box(es)
corresponding to the agent(s) whose data you want to display.
Note: Multiple agents are only displayed in this list when you select more than one
agent in the navigation pane, whose statistics you wish to view.
By default, the statistics are displayed for all tasks, for all connected agents. If
required, filter the display by selecting or clearing the check boxes in the left column.
Viewing the Agent Storage Folder

You can open the storage folder of a selected agent to view the raw RNC data.
To view the agent storage folder:

 In the Agents pane, right click the agent whose storage you want to view, and then
click Open Storage. The storage folder opens, displaying the raw RNC data.
95
Managing Online Collectors

The Online Collectors pane enables you to monitor the online collection. It enables you to
see the current status of the data collection, including the date of the latest data.
Note: Currently, online collection is supported for NSN only. The Mentor Server sends a
command to the NSN collector (Emil client) to check the collector status and the amount of
data that was received from the collector.
The Online Collectors pane contains the following fields:
Field Description
Server The name of the server to which the online collector belongs.
Online The location of the online collector.

Collector
Network The network elements for which the online collector is collecting data.
Elements
Status The status of the online collection service.
Last Data The time of the latest received logs.

Received
Time
Last Failure The latest reason the service failed.

Reason
Agents The name of the agents.
96
Adding Online Collectors

When adding a new online collector, you can manually define the stream providers or you can
load a predefined file that contains all the required data except for the required network
elements. If required, you can also add additional stream providers when viewing the collector
properties.
To manually define a new online collector:

1. In the navigation pane, right-click Online Collectors, and then click New Online
Collector. If you are currently connected to more than one server, you will be
prompted to select the server to which to add the online collector.
o Select the server from the drop-down list, and click OK.
The New Online Collector dialog box is displayed.
2. In the Computer field, enter the name of the server on which the online collector is
installed.
97
3. Click Add. The Add Stream Provider dialog box is displayed.
4. In the Host name field, enter the location of the NSN Emil server.
5. In the Port field, enter 12345. This is the port used by the NSN collector to connect to
the Emil.
6. In the Output location field, select or browse to the location of the data. This location
should include the server name and be accessible to all computers, for example,
\\<server name>\<file name>.
7. In the Network element field, select the network element for which the data is being
collected.
8. Click OK. The stream provider details are displayed in the Stream Providers area of
the New Online Collector dialog box.
9. Repeat steps 3 to 8 for each stream provider you want to add to the online collector.
10. Click OK. The new online collector is displayed in the Online Collectors pane, and
each of its stream providers are displayed in the Online Collection Tasks pane.
To define a new online collector using a predefined properties file:

1. In the navigation pane, right-click Online Collectors, and then click New Online
Collector. If you are currently connected to more than one server, you will be
prompted to select the server to which to add the online collector.
98
The New Online Collector dialog box is displayed.
2. In the Computer field, enter the name of the server on which the online collector is
installed.
3. Click Load. The Load Properties File dialog box is displayed.
4. Select or browse to the file containing the collector service properties. For more
details about this file, contact your account manager.
99
5. Click OK. The stream provider details are displayed in the Stream Providers area,
with a red frame as the required network elements are missing.
6. Double-click each stream provider. The Stream Provider Properties dialog box is
displayed, enabling you to add the required network element.
7. Enter or browse to the required network element and then click OK.
8. Click OK. The new online collector is displayed in the Online Collectors pane, and
each of its stream providers are displayed in the Online Collection Tasks pane.
100
Viewing Online Collector Properties

You can view and edit the properties of a selected online collector any time after it has been
created. You can add additional stream providers or remove existing stream providers. You
can also define the advanced properties that are taken into account when collecting data.
To view the online collector properties:

1. In the Online Collectors pane, right-click the online collector whose properties you
want to view or edit, and then click Properties. The Online Collector Properties
dialog box is displayed, showing the General tab.
The Online Collector Properties dialog box contains the following tabs:
o General, which displays general properties of the online collector, including details
of its stream providers. It also enables you to add or remove stream providers.
o Advanced, which displays the advanced properties that are taken into account for
the online collection.
3. Click OK to close the Online Collector Properties dialog box and apply your changes.
101
General Online Collector Properties

The General tab of the Online Collector Properties dialog box enables you to view the
general properties of the online collector, including details of its stream providers. It also
enables you to add or remove stream providers.
To define the general properties:

1. If required, enter a new name for the collector server.
2. Click Add to add an additional stream provider.
3. Click Remove to remove a selected stream provider.
4. Click Load to add a stream provider from a predefined file.
5. Click OK to save your changes.
102
Advanced Online Collector Properties

The Advanced tab of the Online Collector Properties dialog box enables you to view and edit
the advanced properties that are taken into account for the online collection.
To set the advanced online collector parameters:

expanded showing all the available parameters:
ADMIN_PORT The connection port that the NSN collector listens
Default = 23456 to in the Admin client.
LOG_DIRECTORY The location of the log file for the NSN collector.
TIME_TO_WAIT_AFTER_INIT_IN_ The number of minutes to wait after initiation before
MIN starting to monitor the NSN collector.
Default = 2
TIME_TO_WAIT_BEFORE_RESTAR The number of hours the agent should wait after the
T_IN_HOURS last file was created before restarting the NSN
Default = 1 collector.
3. Click OK to apply your changes and close the Online Collector Properties dialog box.
103
Importing Online Collectors

You can import previously-exported online collectors from other servers.
To import online collectors:

1. On the File menu, click Import and then Online Collectors. The Import Online
Collector Service dialog box is displayed.
2. In the Location field, select or browse to the location of the exported online collector.
All existing stream collector services will be displayed.
3. Select the check box next to any service that does not yet exist in the current server.
4. Click OK.
A progress bar is displayed while the selected stream collector services are being
imported, and then a dialog box is displayed notifying you whether the import
completed successfully. The new online collector is displayed in the Online Collectors
pane, and each of its stream providers are displayed in the Online Collection Tasks
pane.
104
Exporting Online Collectors

You can export one or more online collectors so that they can be imported into other servers.
To export the online collectors:

1. In the Online Collectors pane, right-click the online collectors you would like to
export and then click Export Online Collectors. An Export dialog box is displayed.
2. Browse to the folder to which to export the online collectors, and then click Save. A
progress bar is displayed while the online collectors are being exported, and then a
dialog box is displayed notifying you whether the export process completed
successfully.
105
Managing Data Devices

Data devices are used to retrieve the network data from the network elements. The Data
Devices pane displays the details for each of the data devices belonging to the servers to
which you are currently connected.
The Data Devices pane contains the following fields:
Field Description
Data Device The name of the data device.
Server The name of the server to which the data device belongs.
Network The network element from which the data device retrieves the data.
Element
Type The type of data device.
Protocols The protocol used for collecting the data from the network element.
106
Managing Data Devices
Viewing Data Device Properties

You can view and edit the properties of a selected data device while creating a new network
element, or at any time afterwards.
To view the data device properties:

1. In the Data Devices pane, right-click the data device whose properties you want to
view or edit, and then select Properties. The Data Device Properties dialog box is
displayed.
2. Click Add to add an additional channel. The New Channel dialog box is displayed,
enabling you to enter a name and select the protocol for the new channel.
107
3. Click Edit to edit the channel properties. The Channel Properties dialog box is
displayed, enabling you to edit the channel name, user name and password of the
channel.
4. Click Remove to remove a selected channel from the data device.

5. Click Test to test the connection between a selected channel and the server. A
confirmation message is displayed notifying about the status of the connection.
6. Click OK to close the Data Device Properties dialog box and save your changes.
108
Managing Channels
Managing Channels
Channels are the connection properties for data communication. The Channels pane
displays the details for each of the channels for the network elements belonging to the
servers to which you are currently connected.
The Channels pane contains the following fields:
Field Description
Channel The name of the channel, which includes the name of the data device used
Name for collection and the protocol used for extracting the data.
Server The name of the server to which the channel belongs.
Data Device The name of the data device used for retrieving the network data.
Network The name of the network elements.

Elements
Protocol The protocol used for collecting the data.
Host Name The name of the database host.
User Name The user name of the database host.
109
Editing Channel Properties

You can view and edit the properties of a channel any time after it has been created.
To edit the channel properties:

1. In the Channels pane, right-click the channel whose properties you want to edit and
then click Properties. The Channel Properties dialog box is displayed.
2. If required, enter a new name for the channel.

3. Click Test to test the connection between the server and the database.
4. Click OK to save your changes and close the Channel Properties dialog box. The
edited channel properties are displayed in the Channels pane.
110
Managing Network Elements

The network elements are used to collect the configuration, log, KPI, and performance data.
The Network Elements pane displays the details for each of the network elements belonging
to the servers to which you are currently connected.
The Network Elements pane contains the following fields:
Field Description
Network The name of the BSC, RNC, or CBSC.
Element
Server The name of the server to which the network element belongs.
Region The regions to which the network element is assigned.
Last Task The data type, and the date and time, of the last collection task started.
Performed
Failed Tasks The number of collection tasks that have failed out of the total number of
all the collection tasks for the specific network element.
Active Whether the network element is active.
If a network element is deactivated, all its collection tasks stop, and no
collection tasks are performed from that moment on. The network element
appears dimmed in the user interface. Note that the clusters are still active,
and the optimization and provisioning tasks continue working as usual.
You will be notified of any tasks assigned to a network element that has
been deactivated.
Note: Only licensed network elements can be active. If a network element
is not licensed, it appears dimmed in the user interface, and Unlicensed is
displayed.
Assigned The number of clusters that are assigned to the network element.
Clusters
Vendor The hardware vendor.
Technology The vendor technology.
111
Field Description
Completion The status of the sectors belonging to the network element following the
Required physical data collection run.
 number: The number of sectors still requiring data completion after
being automatically updated.
 None: The sector data was completely updated.
 N/A: Data completion is not relevant, for example, if you have not yet
run a physical data collection task for these network elements.
Last Agent The date and time the network element environment was last updated.
Update
Last Update The last environment-update error.
Error
Adding Network Elements

When defining a new network element, you can duplicate an existing network element, or
define one from scratch by defining the data device to be used for collecting each of these
data types, as well as the protocol used. If you are currently connected to more than one
server, you will be prompted to select the server to which to add the network element.
To add a new network element:

 In the navigation pane, right-click Network Elements and then select New Network
Element. If you are currently connected to more than one server, you will be
prompted to select the server to which to add the network element.
The General page of the New Network Element wizard is displayed.
The New Network Element wizard contains three steps:
 Step 1 - General, enables you to define the general properties for the network
element. For example, its name and time zone, and the agent to which it is assigned.
 Step 2 - Data Device, enables you to define the properties of the data devices used to
perform the collection tasks.
 Step 3 - Collection Tasks, enables you to edit the collection tasks defined in step 2,
as well as to define any collection tasks that were not defined in step 2.
112
Defining General Network Element Properties

The General page of the New Network Element wizard enables you to define the vendor and
technology of the network element, to set the time zone, and to select the agent to which it is
assigned.
Depending on the vendor and technology used, you may have to define additional fields for
adding BSCs/RNCs to the relevant management system. For example, if you have an IRAT
environment, you must also define the BSCs for the OMC when creating the GSM network
elements, or if you are using a Motorola network, you must also define the CBSCs or RNCs
for the OMCR, and so on.
To define the general network element properties:

1. In the Network element name field, select the name of the network element from a
list of licensed network elements. If you have an unlimited license, you can enter the
name of new network element. The network element name is mapped to either the
RNC or the BSC of the client site, depending on the vendor-type and technology.
Notes:
 You can rename a network element at any time, as long as the network-element
data has not yet been submitted from the client to the server.
 Ensure that the name matches the name in the license, otherwise you will not be
able to use this network element in the model. Also, you will not be able to import
data from this network element if it is not recognized.
2. In the Vendor field, select the hardware vendor.

3. In the Technology field, select the vendor technology.
4. In the Time zone field, select the time zone of the network element.
113
5. In the Region field, select the region to which to assign the network element. You can
click the browse button to view the properties of the selected region.
You can also assign the network element to a region at any time in the future, as well
as change the region to which the network element is assigned.
Note: The Region field is displayed only if regions are defined.
6. Depending on your network vendor and technology, you may have to add the
required BSCs/RNCs for the relevant management system. If required, you can edit
these fields in the future.
o GSM users: In the BSC name field, select the BSCs for the OMC from a list of
licensed BSCs, and click Add. If you have an unlimited license, you can enter the
name of the BSCs. (If required, click Remove to remove any selected BSCs.)
o UMTS IRAT users: If you selected to define a network element with GSM
technology, in the BSC name field, enter the name of each BSC for the OMC and
click Add. (If required, click Remove to remove any selected BSCs/RNCs.)
o Huawei CDMA/EVDO users: In the CBSC/BSC name field, select the
CBSCs/BSCs for the CBSC/BSC from a list of licensed CBSCs/BSCs, and click
Add. If you have an unlimited license, you can enter the name of the
CBSCs/BSCs. (If required, click Remove to remove any selected CBSCs/BSCs.)
o Lucent CDMA/EVDO users: In the BSC/RNC name field, select the BSC/RNCs
for the OMP from a list of licensed BSC/RNCs, and click Add. If you have an
unlimited license, you can enter the name of the RNC/BSCs. (If required, click
Remove to remove any selected BSCs/RNCs.)
o Motorola CDMA/EVDO users: In the CBSC/RNC name field, select the
CBSC/RNCs for the OMCR from a list of licensed CBSC/RNCs, and click Add. If
you have an unlimited license, you can enter the name of the CBSC/RNCs. (If
required, click Remove to remove any selected CBSC/RNCs.)
o Nortel EVDO users: In the RNC name field, select the RNCs for the cluster from
a list of licensed RNCs, and click Add. If you have an unlimited license, you can
enter the name of the RNCs. (If required, click Remove to remove any selected
RNCs.)
7. Click Next to proceed to the Data Device page.
114
Defining Data Device Properties

The Data Device page enables you to define the data devices used to retrieve the network
data. You can use existing data devices, or define new ones. After you have defined a data
device, you can edit or delete it. You can also add data devices any time after the network
element has been created.
Note: If you do not define all the tasks for the required data devices in this step, you can add
them in the next step, but you cannot complete the wizard unless all the required data devices
and tasks have been defined.
115
To use existing collection data devices:

1. If data devices exist for your server, click Add. The Add Data Device dialog box is
displayed.
2. Select a data device and then click OK. The selected data device details are
displayed in the Data Device page.
3. Repeat this procedure for each data device you want to add.
4. Click Next to proceed to the Collection Tasks page.
116
To define the data collection devices:

1. If no data devices are defined for the server or if you would like to define a new data
device, click the New button to define a new data device for the network element. The
New Data Device dialog box is displayed.
2. In the Name field, enter a name for the data device.
Note: You can rename a data device at any time.
3. In the Host field, enter the IP address or name of the computer on which the server is
installed.
117
4. In the Type field, select the type of data device you want to add, depending on the
hardware technology selected in step 1. The following data-device types are
available:
Technology Vendor Data-device Description

Type
CDMA Huawei AIRBRIDGE Collects the configuration data.
BAM Collects the log events.
PMDB Collects the KPI counters.
Other All other types of data devices, for

example, FTP, Telnet, SQL-Sybase, SQL-
Oracle, File System.
Lucent OMP Collects PCMD logs, SMs, and

DBSurveys.

Motorola OMCR Collects the CLI scripts, CDL logs, and PM

reports.

Nortel BSM Collects the configuration data.

CDMA
MTX Collects the performance data.

118
Technology Vendor Data-device Description

Type
EVDO Lucent OMP Collects PCMD logs, SMs, and

DBSurveys.

Motorola OMCR Collects the CLI scripts, CDL logs, and PM

reports.

Nortel EMS Collects the alarm and configuration data

for the tilt.

GSM All Other All types of data devices, for example,

vendors FTP, Telnet, SQL-Sybase, SQL-Oracle,
File System.
UMTS Ericsson OSS Collects the GPEH, statistics, and

topology data.

Huawei M200 Collects the counters, logs, and

configuration data.
RNC Collects the counters, logs, and

configuration data.
NSN Other All types of data devices, for example,

FTP, Telnet, SQL-Sybase, SQL-Oracle,
File System.
119
5. Click Add to add at least one channel to the data device. The New Channel dialog
box is displayed, enabling you to define the details of the protocol to be used for
collecting the data.
6. In the Protocol field, select the method to be used for retrieving the data. The
following methods are supported: FTP, Telnet, SQL-Sybase, SQL-Oracle, and File
System. The selected protocol is displayed next to the name of the data device in the
Channel name field.
7. In the User name field, enter the user name for connecting to the database.
8. In the Password field, enter the password for connecting to the database.
9. The status of the connection is displayed in the Status field. At first, the status is Not
tested. Click Test to test whether the server can connect to the database. If it
connects, the status changes to OK, and the date and time the test was performed
are also displayed.
Note: If any changes are made to the channel or its data device, the connection
status returns to Not tested, and must be retested.
120
10. Click OK to save the channel, and close the New Channel dialog box. The channel is
displayed in the Channels area of the New Data Device dialog box.
You can add new channels, or remove or edit the existing channels, as required.
11. Click OK. The New Data Device dialog box closes, and the new data device details
are displayed in the Data Device page. You can view the details of a selected data
device in the Data Device area at the bottom of the page.
121
12. To add additional data devices, repeat steps 1-4 for each data device you want to
add, and then add the required methods, as described in steps 5-11.
If required, you can edit or delete selected data devices.
13. Click Next to proceed to the Collection Tasks page.
Editing Data Device Properties

You can edit the data device properties while adding the network element, or you can edit the
network element's properties any time after it has been created.
To edit the data device properties:

1. In the Data Device page of the New Network Element wizard, select the data device
whose properties you want to edit, and click Edit. The Data Device Properties dialog
box is displayed, showing the channels belonging to the selected data device.
2. If required, in the Name field, enter a new name for the data device.
3. If required, in the Host field, enter a new IP address or name of the computer on
which the database is installed.
122
4. Click Add to add additional channels. The New Channel dialog box is displayed,
enabling you to select the protocol, user name, and password for an additional
channel.
o Click Test to test the connectivity between the channel and the server. If there is a
connection, the status changes to OK, and the date and time of the test is
displayed. If there is no connection, the status changes to Error, and the date
and time of the test is displayed.
o Click OK to save the new channel and close the New Channel dialog box.
5. Click Remove to remove a selected channel. Note that the channel will be removed
without any confirmation message.
6. Click Edit to test the connectivity of the channel. The Channel Properties dialog box
is displayed.
o Click Test to test the connectivity between the channel and the server. If there is a
connection, the status changes to OK, and the date and time of the test is
displayed. If there is no connection, the status changes to Error, and the date
and time of the test is displayed.
o Click OK to save the new channel and close the Channel Properties dialog box.
7. Click OK to save your changes and close the Data Device Properties dialog box.
123
Defining Collection Tasks

The Collection Tasks page enables you to view the collection tasks that have already been
defined, as well as any other tasks required for the network element, according to its specific
vendor. You can also define the scripts required for the data collection.
Note: The collection tasks must be coordinated with the model process to ensure that the
model is built using the latest network data.
To define the collection tasks:

1. Select an existing task, and click Edit to select the script that should be used for the
collection.
2. Click Add to add any collection tasks still required.
3. Click Finish. The new network element is displayed in the Network Elements pane.
124
Editing Collection Task Properties

You can change the protocol used for data collection, edit the task schedule, select the script
that is used for the data collection, as well as edit the advanced parameters for each
collection task.
To edit the collection task properties:

1. In the Collection Tasks page of the New Network Element wizard, select the data
type you want to edit, and click Edit. The Collection Task Properties dialog box is
displayed.
2. If required, select the data device and channel to be used for collecting the data.
3. If required, click Recurrence to define how often the selected task should run. By
default, collection tasks are scheduled daily at midnight.
4. If required, in the Script field, select the script that is used for the collection. For more
information on scripts, refer to the Scripting section in the Mentor Server Installation
Guide.
125
5. If required, edit the script fields in the Advanced tab.
Note: You can edit the script parameters only if you select a script other than the
default <Internal Operations>.
6. Tip: In order to prevent a collection task from carrying on endlessly, in the Advanced
tab, set a timeout period by entering the maximum number of minutes a task should
run before being terminated in the MAX_TASK_EXECUTION_TIME field. After this
time, the task status will be displayed as Canceled, and a notification will be
displayed.
7. Click OK. The edited task is displayed in the Collection Tasks window.
126
Adding Collection Tasks

When you define a new network element, you have to define each of the collection tasks
required for the network element. If you did not define them all when defining the data
devices, you can add them manually in the Collection Tasks page.
To add a collection task:

1. In the Collection Tasks page of the New Network Element wizard, click Add. The
Collection Task Properties dialog box is displayed, showing the properties of one of
the data types that have to be added manually.
2. If required, edit the collection task properties:

o In the Data type field, select the type of data for which to schedule collection. The
fields displayed in the dialog box change accordingly.
o In the Data device field, select the data device from which to retrieve the data. By
default, the required device is displayed in the field.
o In the Channel field, select the protocol to be used for collecting the data.
o Click Recurrence to define how often the selected task should run. By default,
collection tasks are scheduled daily at midnight.
Note: Ensure that the collection is completed before the modeling task begins.
127
o In the Script field, select the script that is to be used for the collection and then
edit the script parameters as required in the Advanced tab. For more information
on scripts, refer to the Scripting section in the Mentor Server Installation Guide.
Note: You can edit the script parameters only if you select a script other than the
default <Internal Operations>.
o Tip: In order to prevent a collection task from running endlessly, in the Advanced
tab, set a timeout period by entering the maximum number of minutes a task
should run before being terminated in the MAX_TASK_EXECUTION_TIME field.
After this time, the task status will be displayed as Canceled, and a notification
will be displayed.
3. Click OK. The task is displayed in the Collection Tasks window.
4. Repeat this procedure for each collection task you have to add manually.
5. Click Finish to save your changes and add the new network element to the list of
network elements defined in the Server Admin.
128
Editing Advanced Collection Task Properties

The Advanced tab shows the advanced parameters that are taken into account for the
selected collection task.
If required, you can also view and edit the advanced parameters for multiple selected
collection tasks by right-clicking the required tasks and then clicking Properties.
Note: Script group parameters are displayed only if you select to use your own scripts, and
not the default <Internal Operations> script.
129

expanded, as follows:
Dashboard group
CONFIGURATION_DASHBOARD_ Whether to create configuration data for the Insight

ENABLED application during the collection.
(Default = Yes)
KPIS_DASHBOARD_ENABLED Whether to create KPI data for the Insight

application during the collection.
(Default = Yes)
File Transfer group
ANTENNAS_SOURCE The path of the profiles to be collected.

(Default = \profiles)
ANTENNAS_SOURCE_TYPE The type of profile data to collect.

(Default = NONE)
CELL_OWNERS_LOOKUP The name of the file to use when matching site

names from Mentum Planet. If this field is empty,
the cellownerslookup.txt file is used.
COORDINATES_TYPE The format of the coordinates in the planning tool.

(Default = AUTO)  DEGREES: Will be parsed as lat/lon in Mentor.
 UTM: Will be parsed as x/y in Mentor.
 AUTO: Will be parsed as lat/lon in Mentor, if
possible. If outside the projection, will be parsed
as x/y.
DAYS_FROM_TODAY The number of days counted from today.

(Default = 14)
DELETE_REMOTE_FILE Whether data that was downloaded should be

deleted from the remote machine after finishing the
(Default = No)
collection.
FILES_TIMESTAMP_REWIND_IN_ The amount of time before the last collection from

HOURS which to start collecting new files.
(Default = 0)
FILE_LOCATION_PATTERN The pattern used to filter the file location.

(Default = .*)
130
FILE_PATTERN The pattern used to filter the file name.

(Default = .*)
FTP_TIMEOUT_SECONDS The number of seconds before the download from

the FTP times out.
(Default = 0)
INDEX_FILE The index file from the planning tool, relevant for
the physical data collection.
MINUTES_NOT_MODIFIED_FILTER The number of minutes after which unmodified files

should be collected.
(Default = 1)
NUM_PARALLEL_CHANNEL The number of parallel FTP/File System channels

that should be opened.
(Default = 1)
PROFILES_TRANSLATOR Converts the profile names used by the planning

tools to the names in the existing profiles.
(Default = \profilestranslator.txt)
RECURSIVE_DOWNLOAD Whether to keep the current hierarchical structure

when downloading the data.
(Default = Yes)
Forwarding group
FTP_FORWARD_HOST The parameters to be used when sending data

automatically.
(Default = N/A)
FTP_FORWARD_PASSWORD
(Default = N/A)
FTP_FORWARD_PORT
(Default = 21)
FTP_FORWARD_ROOT
(Default = N/A)
FTP_FORWARD_USER
(Default = N/A)
FTP_RESULT Whether to forward the collected data to the FTP.

(Default = No)
131
General group
ALLOWED_PERCENTAGE_OF_ The percentage of sectors that can be missing, in

MISSING_ELEMENTS order to avoid large deletions of the network.
(Default = 20)
ANALYZE_CONFIGURATION Whether to create a new Mentor, Mentor Sparks, or

Forte environment that contains data merged from the
(Default = Yes)
switch dump and the current environment.
 Yes: The client creates a new environment using
data from the switch dump and the current
environment. Data from the switch dump and the
environment are merged and resolved to create a
new Schema Format, which creates a set of lighter
files that are easier and faster to import to the
client.
This is the recommended option.
 No: Data is not merged to create a new
environment, and the switch dump data itself is
imported directly to the client. This method takes
considerably longer, as the switch dump files are
very heavy.
CALCULATE_PERIODS Whether to calculate the file periods directly after the

collection.
(Default = Yes)
EVDO_CDMA_CONFIGURATION_ Defines which CDMA network elements will be

MATCHING included in the EVDO switch resolving.
(Default = JOINEDCLUSTER)
FAIL_IF_RESOLVING_FAILED Whether to fail the entire switch dump collection task

if the file itself could not be parsed.
(Default = Yes)
FORCE_SET_WORKING_DIR This controls the current working directory of the

script.
(Default = BY_PATHNAME)
 YES: The working directory is the script's folder.
 NO: The working directory is determined by the
server (and is probably not the script's folder)
 BY_PATHNAME: If the script location is a shared
folder (begins with "\\") then working directory is
not set (same as "NO"). Otherwise, working
directory is the scripts location.
As a rule of thumb, if the script uses other scripts, this
parameter should be set to YES. Otherwise, leave the
default.
132
MAX_TASK_EXECUTION_TIME The number of minutes the collection task should run

before it is automatically terminated. After this amount
of time, the task status is displayed as Canceled, and
a notification is displayed.
RETRY_ATTEMPTS_INTERVAL_ The number of seconds between each collection task

SECONDS attempt.
(Default = 60)
RETRY_ATTEMPTS_NUMBER The number of times to attempt performing a failed

collection task.
(Default = 0)
SCRIPT_PARAMS_OUTPUT_ROOT The path of the folder to which to copy the .properties

_PATH file of the collection task.
SUB_FOLDER The name of the sub-folder that is used, if a specific

folder structure is required in the collected log folder.
ZIP_RESULT Whether the incoming files should be zipped.

(Default = No)
ZIP_RESULT_BY_PERIOD Whether to zip the files after the range calculation. If

set to Yes, this parameter overrides the
(Default = No)
ZIP_RESULT_ONE_BY_ONE parameter, and files
will first transfer to the cache folder under the hours
folder, and will then be zipped, taking into
consideration the ZIP_RESULT_MAX_GROUP_SIZE
parameter.
Note: This parameter is relevant only if the
ZIP_RESULT parameter is set to Yes.
ZIP_RESULT_MAX_GROUP_SIZE The maximum number of files that can be zipped

together. This parameter affects all zip parameters.
(Default = 262,144)
ZIP_RESULT_METHOD Whether to zip the incoming files in GZ or ZIP format.

(Default = GZ)
ZIP_RESULT_ONE_BY_ONE Whether to zip each collection file separately.

(Default = Yes)
the new values.
3. Click OK to apply your changes and close the Collection Task Properties dialog box.
133
Required Collection Data

The following data types must be collected for each network element, according to vendor. A
directory will be created for each type.
If any of these data types are missing, you must add them manually.
Technology Vendo Data Types Description and Default Times

r
CDMA Huawei Configuration Airbridge LST dump file is collected once a

day, at 06:00, using FTP.
Log CHR logs are collected once a day, at

06:00, using FTP.
PMs PM reports are collected once a day, at

06:00, using SYBASE SQL queries.
Lucent SMs SMs are collected twice daily, 00:00 and

(OMP) 01:00, using Telnet.
Log PCMD logs are collected every 4 hours,

using FTP.
Configuration DBSurveys are collected once a day, at

02:00, using Telnet.
Motorola Log CDL logs are collected once a day, at

(OMCR) 02:00, using FTP.

04:00, using FTP.
CLI CLI scripts are collected once a day, at

Nortel Performance Performance tasks are defined

(BSC) automatically for MTX data devices. Every
30 minutes, the MTX reports the network
performance for the previous 30 minutes.
This information is deleted after half an
hour.
Configuration Configuration data is collected from the

switch dumps once a day, at 02:00, using
BSMCI. This data defines the antennas,
neighbor lists, sector carriers and so on.
Log Logs are made up of the mobile

measurements recorded during each call,
including drop calls. BSC logs are
collected twice a day, at 14:00 and 19:00,
using FTP.
134

r
OMs OMs report the KPI data for traffic and

power.
EVDO Lucent SMs SMs are collected twice daily, 00:00 and
(OMP) 01:00, using Telnet.
Log PCMD logs are collected every 4 hours,

using FTP.
Configuration DBSurveys are collected once a day, at

Motorola Log CDL logs are collected once a day, at

(OMCR) 02:00, using FTP.

04:00, using FTP.
CLI CLI scripts are collected once a day, at

Nortel Performance OMs are collected daily at 04:00, using

(RNC) Telnet.
Configuration System Audit is collected daily at 11:00,

using FTP.
Log RNC logs are collected daily at 11:00,

using FTP.
GSM Alcatel, Counters Load-balancing KPIs, Traffic, and HO

Ericsson, statistics are collected once a day, at
Huawei, 06:00.
Motorola,
Nokia, Configuration Configuration data is collected from the
Nortel, switch dumps once a day, at 06:00.
Siemens
Mobile Statistics Mobile statistics are collected once a day,
at 06:00.
UMTS Ericsson Counters Statistics are collected once a day, at

(RNC) 02:00, using FTP.
GPEH GPEH is collected once a day, at 03:00,

using FTP.
Configuration Topology is collected once a day, at 06:00,

using FTP.
135

r
Huawei CM Topology is collected once a day, at 06:00,

using FTP.
Log Logs are collected once a day, at 03:00,

using FTP.
Counters Statistics are collected once a day, at

02:00, using FTP.
Duplicating Network Elements

When defining a new network element, you can either duplicate an existing network element,
or define one from scratch. The duplicated network element will contain the same collection
tasks and parameters as the original network element, but you can edit the fields as required.
To duplicate a network element:

1. In the Network Elements pane, right-click the network element you would like to
duplicate, and then click Duplicate. If you are currently connected to more than one
server, you will be prompted to select the server to which to add the network element.
The New Network Element wizard is displayed.
2. Enter a name for the new network element.

3. Edit the fields in the wizard, as required.
136
Viewing Network Element Properties

You can view and edit the properties of a selected network element any time after it has been
created. You can also edit the data device properties and the collection tasks while the
network element is being created.
To view the network element properties:

1. In the Network Elements pane, right-click the network element whose properties you
want to view or edit, and then click Properties. The Network Element Properties
o Click Rename to rename the network element.
Note: This can be done only if changes from the client have not yet been
submitted.
o Click Change to change the time zone.
Note: This can be done only if the changes have not yet been submitted to the
server.
137
o Click Edit to add or remove BSCs/RNCs to or from the list of BSCs/RNCs for the
OMCR, OMP, or OMC.
Note: BSCs/RNCs can be removed only if changes have not yet been submitted
to the server.
This option is available only for CDMA, EVDO, and GSM network elements.
o Clear the Active check box to deactivate the network element. Select the Active
check box to activate the network element.
o Click History to view a history of the selected network element. Each row
represents a task type.
2. Click the Data Device tab to view the data device properties.
o Click Add to add an existing collection device

o Click New to define a new collection data device.
o Click Edit to edit a selected data device.
o Click Delete to remove a selected data device. Note that if you delete a data
device, you also delete its respective channels and collection tasks.
138
3. Click the Collection Tasks tab to view the collection tasks.
o Click Add to add a new collection task.

o Click Edit to edit a selected collection task.
o Click Remove to remove a selected collection task.
139
4. Click the Model Content tab to view the current modeling times and busy hours, as
well as the modeling tasks and the dates for which there is a model.
o Edit the model data, as required, or run or stop specific modeling periods, as well
as delete specific dates from the model.
140
5. Click the Collected Data tab to view the amount of collected data, and the data-
collection limit, if any. This tab enables you to estimate for which days there will be a
model.
o Enter a collected-data limit in the Collected data limit field. The collection data is
saved until it reaches this limit or the limit set by the
MAX_COLL_TASK_HISTORY_TO_SAVE parameter.
o Click Put on FTP Server to upload the selected collected data to the FTP server.
o Click Calculate Periods to use the collected log and KPI data and estimate the
time and date for the folders, including the unknown data. This option is generally
used for troubleshooting.
6. Click OK to save your changes and close the Network Element Properties dialog box.
141
Exporting Network Properties

You can export the network properties file containing all the visible and hidden parameters as
well as the filters used in a selected cluster or network element, so that they can be imported
and used in other servers, clusters, or network elements.
To export the network properties:

1. In the Network Elements pane or the Clusters pane, right-click the network element
or cluster whose network properties you want to export, and then click Export
Network Properties. The Export Network Properties dialog box is displayed.
2. Browse to the location to which to export the selected network properties, enter a
name for the file, and click Export. A progress bar is displayed while the network
properties are exported, and then a dialog box is displayed notifying whether the
export process completed successfully.
142
Importing Network Properties

You can import previously exported network properties from other network elements or
servers, so that they can be used in the currently selected network elements or clusters.
To import the network properties:

1. In the Network Elements or Clusters pane, right-click the network elements or
clusters to which to import the network properties and then click Import Network
Properties. The Import Network Properties dialog box is displayed.
2. Browse to the required file and then click Open. A progress bar is displayed while the
network properties are being imported, and then a message is displayed notifying
whether they were successfully imported.
Renaming Network Elements

You can rename a network element at any time, as long as changes have not yet been
submitted from the client to the server. If changes have been submitted, a dialog box is
displayed.
143
To rename a network element:

1. In the Network Elements pane, right-click the network element you want to rename,
and click Properties. The Network Element Properties dialog box is displayed,
2. Click Rename. The Rename Network Element dialog box is displayed.
3. Enter a new name for the network element.

4. Click OK to save the network element with the new name.
5. Click OK to close the Network Element Properties dialog box.
144
Editing the Network Element Management System BSCs/RNCs

Depending on the vendor and technology used, you can add or remove BSCs/RNCs to/from
the relevant management system of a selected network element.
Note: The BSCs/RNCs can be removed only if changes have not yet been submitted to the
server.
To edit the management system BSCs/RNCs:

1. In the Network Elements pane, right-click the network element whose management
system BSCs/RNCs you would like to edit. The Network Element Properties dialog
box is displayed.
145
2. Click Edit. The relevant dialog box is displayed, showing the current BSCs/RNCs
assigned to the network element management system.
3. To add a BSC/RNC, enter the name of the BSC/RNC and click Add.
4. To remove a BSC/RNC, select the BSC/RNC in the list and then click Remove.
Note: You can remove a BSC/RNC only if it has not yet been submitted to the
server.
5. If required, click Save to save the currently selected BSCs/RNCs, for example, so
that they can be used as a reference or updated, and loaded in the future.
6. If required, click Load to load a group of previously selected BSCs/RNCs for
updating, using as a reference, and so on.
7. Click OK to save your changes and close the dialog box.
146
Changing the Network Element Time Zone

You can change the time zone of a network element at any time, as long as changes have not
been submitted from the client to the server. If changes have been submitted, you are notified
of such.
To change the network element time zone:

1. In the Network Elements pane, right-click the network element whose time zone you
want to change, and click Properties. The Network Element Properties dialog box
is displayed, showing the General tab.
2. Click Change. The Change Time Zone dialog box is displayed.
3. Select a new time zone for the network element.

4. Click OK to save the new time zone.
5. Click OK to close the Network Element Properties dialog box.
147
Viewing the Network Element History

The Mentor Server saves a history of all the collection tasks performed by the network
elements, according to the settings in the Server Properties dialog box.
You can view the history of all the collection tasks for a selected network element, as well as
the details of the operations performed in a selected data type. Tasks are listed in
chronological order.
To view the network element history:

1. In Network Elements pane, right-click the network element whose history you want
to view, and then select History.
-Or-
In the General tab of the Network Element Properties dialog box, click History.
The History for Network Element <name> dialog box is displayed, showing the
history of the collection tasks in the selected network element.
148
The History for Network Element <name> dialog box contains the following fields:
Field Description
Data Type The type of collection task.
Data Device The data device running the collection task.

Note: This field is not applicable for EMS devices.
Agent The agent responsible for executing the tasks associated with this network
element.
Occurrence The status of the collection task:

Status
 Succeeded: The task has run, and has succeeded.
 Failed: The task has run, and has failed.
 Running: The task is currently running. After completion, the status of
the occurrence will change to Succeeded or Failed.
Recurrence How often the task is scheduled to run.
Date The date and time the task started.
2. Select the collection task whose details you want to view, and then click Details. The
Details dialog box is displayed, showing each operation that took place during the
data collection.
149
The Details dialog box enables you to view the following information for each of the
operations in the selected collection task:
Field Description
Information
Warning
Error
Date and The date and time the operation was executed.
Time
Type The type of operation, for example, model, collection, antenna sector plan
optimization, importing environment and model, sanity check, provisioning,
download started, and so on.
Event Whether the operation started, stopped, or was in process.
Source The name of the network element, optimization, model and so on.
Results The outcome of the operation:

 Succeeded: The operation completed successfully.
 Failed: The operation failed, and therefore the task has failed.
Details A description of the operation.
Deactivating Network Elements

When you deactivate a network element, no collection tasks are performed from that moment
on, and the network element appears dimmed in the Network Elements pane. Note that the
clusters are still active, and the optimization and provisioning tasks continue working as usual.
You will be notified of any active tasks assigned to the network element, if necessary.
Note: You cannot deactivate a network element while there are collection tasks in progress.
You will be notified that you have to first cancel the task.
To deactivate a network element:

 In the Network Elements pane, right-click the network element you want to
deactivate, and from the menu select Deactivate. The network element is
deactivated, and No is displayed in the Active column.
To reactivate a network element:

 In the Network Elements pane, right-click the network element you want to activate,
and from the menu select Activate. The network element is Activated, and Yes is
displayed in the Active column.
150
Adding Data Devices

Data devices are used to retrieve the network data from the network elements. You can
define data devices while creating a new network element or anytime afterwards, as required.
This is very useful when you have to create multiple data devices with FTP/Telnet
connections.
To define a new device:

1. In the navigation pane, right-click Data Devices and then select New Data Device. If
you are currently connected to more than one server, you will be prompted to select
the server to which to add the data device.
o Select the server from the drop-down list and click OK.
The New Data Device dialog box is displayed.
2. In the Name field, enter a name for the data device.

3. In the Host field, enter an IP address or the name of the computer on which the
server is installed.
4. In the Type drop-down list, select the type of data device you want to add. The
options available here depend on the hardware technology specified in step 1 of the
New Network Element page. If you have not yet defined the vendor and hardware
technology for the device, all options are available and displayed in the list.
151
5. Click Add to add channels. The New Channel dialog box is displayed, enabling you
to enter a name and select the protocol for the additional channel.
6. Click Test to test the connectivity between the channel and the server. If there is a
connection, the status changes to OK, and the date and time of the test is displayed.
If there is no connection, the status changes to Error, and the date and time of the
test is displayed.
7. Click OK to save the new channel and close the New Channel dialog box.
8. Click Remove to remove a selected channel. Note that the channel is removed
without any confirmation message.
9. Click Edit to test the connectivity of the channel. The Channel Properties dialog box
is displayed.
10. Click Test to test the connectivity between the channel and the server. If there is a
connection, the status changes to OK, and the date and time of the test is displayed.
If there is no connection, the status changes to Error, and the date and time of the
test is displayed.
11. Click OK to save the new channel and close the Channel Properties dialog box.
12. Click OK to save your changes and close the New Data Device dialog box. The new
data device is displayed in the Data Device tab of the Network Element Properties
dialog box.
152
Viewing Last Task Failure Details

By default, the reason a task failed is displayed in the Last Failure Details column of the
Collection Tasks, Physical Data Collection Tasks, and Model Tasks panes. If required, you
can view the full details of a failed task or a failed network element from the time it started,
until it failed.
To view the details of the last task failure:

1. In the relevant pane, right-click the network element or task whose failure details you
want to view, and then select Last Failure Details. The Details dialog box is
displayed, showing the operations in the failed task occurrence.
operations in the failed task:
Field Description
Information
Warning
Error
Time

153
Editing the Model Data

You can specify the data that is included in the models of each network element by defining
the times each modeling period starts and ends, and the time that is used as the busy hour.
These times will be used when creating new modeling tasks. You can also view the status of
each modeling period, and the dates for which there is a model for each selected modeling
period.
To edit the model data:

1. In the Network Elements pane, right-click the network element whose modeling
periods you want to edit, and then select Properties. The Network Element
Properties dialog box is displayed, showing the General tab.
2. Click the Model Content tab. The times for the morning and evening models, and the
busy hours are displayed, as well as the details of each modeling period. In the
calendar at the bottom of the dialog box, dates for which a model exists are displayed
in bold.
3. In the Mornings (from/to) fields, select the times the morning modeling period starts
and ends. These times will be used when creating a morning modeling period.
4. In the Evenings (from/to) fields, select the times the evening modeling period starts
and ends. These times will be used when creating an evening modeling period.
5. In the Defined busy hours field, select the time that should be used as the busy
hour.
154
6. To run a model for a selected modeling period, click Options and then select Run.
7. To stop a selected running model, click Options and then select Stop.
8. To delete specific dates from a selected modeling period, click Options and then
select Delete Dates. The Delete Dates - <modeling period> dialog box is displayed.
o Select the period to delete, and click Delete.

o Click OK to close the Delete Dates - <modeling period> dialog box.
9. To view the days for which there is a model for the selected modeling period, select
the required month and year from the drop-down lists. The days with a model for the
selected modeling period are displayed in the calendar in bold.
10. Click OK to save your changes and close the Network Element Properties dialog box.
155
Calculating the Collected Data Period

The Mentor Server can take the raw data logs and KPIs that have already been collected, and
if necessary, recalculate the time range for this data.
Note: This is a timely process that can take up to a few days.
To calculate the data period:

1. In the Network Elements pane, right-click the network element for which to calculate
the data period and then select Properties. The Network Element Properties dialog
box is displayed, showing the General tab.
2. Click the Collected Data tab. A progress bar is displayed while the content of the
collected data is retrieved. The amount of collected data is displayed, as well as a list
of all the collected data, per day.
3. Select the check boxes next to the raw data whose time range you want to
recalculate and click Calculate Periods. A progress bar while the collected data
content is retrieved and the data period is calculated. A confirmation message is
displayed.
4. Click Close to close the Calculate Periods dialog box.
156
Uploading Extracted Raw Data to the FTP Server

You can extract raw data for one or more specific days, and upload this data to the FTP
server. If required, you can also calculate the period of this data.
To upload extracted raw data to the FTP server:

1. In the Network Elements pane, right-click the network element from which you want
to extract the raw data, and then select Properties. The Network Element
Click the Collected Data tab. The amount of collected data is displayed, as well as a
list of all the collected data, per day.
157
2. Select the check box next to the raw data you want to upload to the FTP server, and
click Put on FTP server. The Put <network element> collected data on FTP
server dialog box is displayed.
3. In the Host field, enter the name of the FTP server.

4. In the User field, enter the user name for the FTP server.
5. In the Password field, enter the password for the FTP server.
6. In the Port field, enter a new port for the FTP server, if required.
7. In the Remote Dir field, enter the path to the directory to which to upload the
collected data.
8. Click OK. A progress bar is displayed while the data is being forwarded, and then a
dialog box is displayed, confirming whether the data transfer was successful.
9. Click Close to close the Collected Data dialog box.
158
Defining Task Recurrences

When creating the network elements, or scheduling optimization, provisioning, and analysis
tasks, you can define the frequency at which the tasks are performed. You can also edit
future task occurrences at any time after the network elements and tasks have been defined.
To define a task recurrence:

1. In the relevant dialog box, click Recurrence.
-OR-
In the Action menu, click Recurrence.
The Task Recurrence dialog box is displayed.

2. Specify the time the recurrence should take place. Tasks can be performed daily,
weekly, or monthly.
3. Click OK to close the dialog box and apply your changes.
To set daily task recurrences:

1. In the Recurrence area, select the Daily option. The Task Recurrence (Daily)
2. In the Process At area, select the time at which the selected recurrence takes place.
3. In the Pattern area, select one of the following options:
o Recur every, and then select the frequency of the recurrence. If required, you
can exclude one or more times by selecting them, and then clicking Delete.
o Once a day
The occurrence times are displayed in the Pattern area, starting at the time selected
in the Process At field.
4. Select the Ignore weekends check box if you do not want the task to be executed
over weekends.
5. Click OK to close the Task Recurrence dialog box and apply the changes.
159
To set weekly task recurrences:

1. In the Recurrence area, select the Weekly option. The Task Recurrence (Weekly)
2. In the Process At field, select or enter the time the recurrence(s) should take place.
3. In the Pattern area, select the day(s) of the week the recurrence should take place.
4. Click OK to close the Task Recurrence dialog, and apply the changes.
To set monthly task recurrences:

1. In the Recurrence area, select the Monthly option. The Task Recurrence (Monthly)
160
2. In the Process At field, select or enter the time the recurrence should take place.
o The date of the month, and the monthly frequency. For example you can define
tasks to run on the first day of every month, or the 10th day of every 3rd month,
and so on.
o The day of the month, and the monthly frequency. For example, you can define
tasks to run on the first Sunday of every month, or the third Monday of every
second month.
Exporting Network Elements

You can export one or more selected network elements so that their data can be imported
and used in other servers.
To export a network element:

1. In the Network Elements pane, right-click the network elements you want to export,
and then select Export Network Elements. The Export dialog box is displayed.
2. Browse to the folder to which to export the data. The path is displayed in the Folder
name field.
3. Click Save. A progress bar is displayed while the selected network elements are
being exported. You can minimize the progress bar to continue working during the
import process. Once the network elements have been exported, the Export
Completed dialog box is displayed notifying whether the process was successful.
4. Click Close to close the Export Network Element dialog box. The network elements
and there data can now be imported into other servers.
161
Importing Network Elements

You can import one or more previously exported network elements from other networks or
servers, so that they can be used in the current or selected server.
To import a network element:

1. On the File menu, select Import and then Network Elements. If you are connected
to more than one server, you will be prompted for the server to which to add the
imported network elements.
2. Select the server, and click OK. The Import Network Elements dialog box is
displayed.
3. If required, browse to the location of the previously exported network elements, and
then click Open to display a list of available network elements.
4. Select the check boxes next to the network elements you want to import. A progress
bar is displayed while the selected network elements are being imported. You can
minimize the progress bar and continue working while the network elements are
being imported.
162
Once the networks elements have been imported, the Import Completed dialog box
is displayed, notifying whether the network element data was successfully imported.
5. Click Close. The imported network elements are displayed in the Network Elements
pane.
Note: Only network elements that do not already exist in the server can be imported.
6. Click OK.
Deleting Network Elements

You can delete network elements at any time. Before deleting network elements, you must
first unassign all clusters assigned to them and stop all running modeling tasks.
Note: If the network element being deleted is the only network element that contains a
specific modeling period, the modeling period will be deleted as well.
To delete a network element:

1. In the Network Elements pane, right-click the network element you want to delete,
and click Delete. A confirmation window is displayed, warning that all the collection
tasks, data devices, and channels associated to the network element will also be
deleted.
2. Click Yes. The selected network element and its respective collection tasks, data
devices, and channels are deleted.
163
If you have not yet unassigned the clusters assigned to the network element, an error
message is displayed notifying that there are still clusters assigned to it.
o Click Details to view a list of the assigned clusters.
o Click Close, unassign the clusters, and then try again.

3. If the network element is currently running a model task, a notification is displayed
asking whether to stop the model.
164
4. Click Yes. If the network element is the last network element containing specific
modeling periods, a message is displayed notifying that the modeling periods will also
be deleted if the network element is deleted.
5. Click Details to see a list of the modeling periods that will be deleted.
6. Click Yes to delete the network element and any listed modeling periods.
165
Completing the Physical Data - GSM Network Elements

After you have run a physical data collection task, the sector data for each network element is
automatically updated, and if there is data missing after the physical data import, or if there is
a discrepancy with the data from the switch dump, the number of sectors requiring data
completion is displayed in the Completion Required column of the Network Elements pane.
When completing the physical data, a file will be generated containing a list of all unidentified
antennas. After you have edited the list, you must run a new Physical Data Collection task
using the edited list.
To complete the physical data:

1. In the Network Elements pane, right-click the GSM network elements whose
physical data you want to complete and then select Physical Data Completion. A
progress bar is displayed while a file containing all unidentified antennas is created,
and then a standard Save dialog box is displayed.
2. Enter a name for the file, browse to the location in which to save the file, and then
click Save.
3. In the saved file, enter tab-delimited values for longitude, latitude, and azimuth for all
unidentified antennas.
4. Delete all antennas without completed data.
5. Run a new Physical Data Collection task, using the edited file as the remote directory.
166
Completing the Physical Data

After you have run a physical data collection task, the sector data for each network element is
automatically updated, and if there is data missing after the physical data import, or if there is
a discrepancy with the data from the switch dump, the number of sectors requiring data
completion is displayed in the Completion Required column of the Network Elements pane.
To complete the physical data:

 In the Network Elements pane, right-click the network elements whose physical data
you want to complete and then select Physical Data Completion. A progress bar is
displayed and then the first page of the Data Completion wizard is displayed.
Note for GSM network elements: An antenna file is created containing all the
invalid sectors in the network. This file must be saved and edited, and then used as
the remote directory when running a new Physical Data Collection task.
167
The Data Completion wizard contains two steps:

 Step 1 - Mass Data Completion, enables you to complete the missing data in the
Schema Format and reimport the data.
 Step 2 - Data Completion, enables you to complete the data or make configuration
changes directly in the GUI.
Mass Data Completion

The Mass Data Completion page enables you to view the total number sectors that are
missing physical data, as well as the number of sectors that are missing each type of data.
You can either export the current data to the Schema Format, update the relevant files using
an external text editor, and then reload the associated .opr file to continue the import process,
or you can proceed directly to the Data Completion page and update specific sectors directly
in the GUI.
To complete the missing data in the GUI:

 Click Next to proceed to the Data Completion page.
To complete all the data in the Schema Format:

1. In the first section of the Mass Data Completion page, check which data should be
updated.
2. In the second section, click Save to browse to the folder in which to save the current
network, in the Schema Format.
3. Open the folder in which the network files were saved, and then correct the files
according to the list of required updates in the first section of the page.
4. After you have updated all the required files, click Load. The Select Mentor Project
File Location dialog box is displayed, enabling you to browse to the folder containing
the updated .opr or .mpr file.
168
5. Double-click the .opr or .mpr file. A progress bar is displayed while the updated
network is being imported.
6. Click Next to proceed to the Data Completion page.
Data Completion
After you have entered the path of the project file or the network data, and there are no more
sectors with missing data, you can finish the data completion.
If you selected to skip the mass data completion option, you can manually complete the data
of selected sectors directly in the GUI.
To finish the data completion after updating the Schema Format:

1. In the Data Completion page, click Finish. A progress bar is displayed while the
data is imported, and then a confirmation message is displayed.
2. If required, click Details to view the details of the data completion process.
3. If required, click Reports to view the Accepted Changes report, which lists the
network elements whose data was completed, as well as the values of the fields that
were changed, before and after the update.
169
To complete the missing data directly in the GUI:

1. In the Data Completion page, sectors that are identified in the network switch dump,
but which will not be updated as they are missing physical data after the automatic
physical data collection task, are displayed in red in the Excluded sectors pane, on
the left. The number of sectors with missing data is displayed at the top of the pane.
2. Select the sectors you would like to include in the import process and click the right
arrow button , or right-click the sectors and then click Move. The selected sectors
move to the Excluded sectors to be edited and imported pane, on the right. The
number of sectors with missing data to be completed and imported is displayed at the
top of the pane.
170
3. In the right pane, select a sector whose data you want to complete, and click Edit.
The <sector name> Properties dialog box is displayed, enabling you to enter the
missing data. Fields with missing information are highlighted in red.
4. Enter the required data. After you have completed the data, the sectors are displayed
in black.
171
5. Click Finish. A progress bar is displayed while the data is imported, and then a
confirmation message is displayed.
6. If required, click Details to view the details of the data completion process.
7. If required, click Reports to view the Accepted Changes report, which lists the
network elements that were updated, as well as the values of the fields that were
changed, before and after the update.
Note: If this is the first time you are viewing reports, a dialog box will be displayed
enabling you to browse to the Microsoft Excel executable file.
172
Creating Administration Reports

You can create CLI reports directly through the Server Admin. These reports display the
status of the collection runs for one or more selected network elements.
To create an administration report:

1. In the Network Elements pane, right-click the network elements for which to create a
report, and then click Create Admin Reports. The Create Admin Report dialog box
is displayed.
2. By default, all report types are displayed, but you can select a specific report type
from the Report type drop-down list.
If required, you can select multiple report types by clicking the browse button , and
then selecting the required report types in the Add Report Types dialog box.
The selected report types will be saved in the Report type list for future use.
173
Currently, the following report types are supported:

o Agents
o Calls DB
o Collections
o Collection Statistics
o Log Processing
o Log Processing Statistics
o Mobile Tracking Audit
o Models
o Model Data
o Model Statistics
o Raw Data
o Users
3. In the Target Directory field, select or browse to the location in which to save the
reports.
4. In the Days area, select whether to display the reports for all days, or for the latest
number of days.
5. Click OK. A progress bar is displayed while the selected report types are being
generated.
Agents Tab
The Agents tab enables you to view the properties of the agent. It displays the following
fields:
Field Description
Object ID For internal use only.
Agent The name of the agent.
Version The server version being used.
Server The name of the server to which the agent belongs.
Active Whether the agent is active.
Status The status of the agent—Connected or Disconnected.
Disconnection The reason the agent was disconnected.

Reason
Running Tasks The number of tasks belonging to the agent that are currently
running.
Front End Whether the agent is running on a front-end machine.
Storage ID The storage ID assigned to the agent during installation.
174
Field Description
Data Folder The folder in which the agent's storage is located.
Local Temp Folder The path of the temporary location to which to run the model on the
agent.
Total Disk Space The total amount of disk space on the agent.
Free Disk Space The amount of free disk space on the agent.
Memory The amount of memory in the agent.
Processors The number of processors in the agent.
SECTOR_PLAN Whether the service is supported by the server.
MODEL Whether the service is supported by the server.
NL
ANALYSIS
COLLECTION
OSP
SC
NBRGSM
PROVISIONING
QE
OFP
MULTICALCULATION
LOGSPROCESSING
RULE_BASED
DELETE_METHOD The way the agent data is selected for deletion.

Note: This field is displayed only if the DELETE_METHOD
parameter is set to BY_CONTENT.
175
Call DB Tab
The Call DB tab enables you to verify whether the call data was correctly inserted into the call
database. It displays the following fields:
Field Description
Network Element The name of the network element.
Latest File The status of the latest file-processing task. If the status is Partial, it
Processing Status means that one call was rejected. You can view the details of the
rejected calls in the log.
Latest Data Date The date of the latest data.
Failed Files - Last 12 The number of files that failed in the last 12 hours.
Hours
Failed Files - Last 24 The number of files that failed in the last 24 hours.
Hours
Pending Files The number of files waiting to be processed.
Pending in Agent The number of files that have been processed, but have not yet
been moved from the agent to the call database.
Collections Tab
The Collections tab displays general details of all the collection runs in the selected network
elements. It displays the following fields:
Field Description
Data Type The type of data collected, for example, counters, log, configuration.
Data Device Name The name of the data device used to retrieve the data.
Data Device Host The IP address or name of the computer on which the server is
installed.
Status The status of the collection.
Details The reason the collection failed, if any.
Start Time The date and time the collection started.
Run Time The amount of time the task ran.
Recurrence The frequency of the task occurrence.
176
Field Description
Process At The time at which the recurrence took place.
Pattern The recurrence pattern, for example, once a day.
Agent The agent used for the task.
Notifications The notification status for this task. If enabled, notifications will be
sent.
Script The script used to collect the data.
Zip The zip method used. This field is displayed only if the default
method was not used.
Note: Advanced parameters may be displayed at the end of the report, depending on the
script and parameter definitions of the selected network element. If N/A is displayed in one of
these fields, it means that the default value of the parameter was used.
Collection Statistics Tab

The Collection Statistics tab displays data for all collection runs, including the number of
files collected and parsed, as well as the number of files per day. It contains the following
fields:
Field Description
Data Type The type of data collected, for example, configuration, counters,
logs.
Data Device The device used to retrieve the data.
Remote Directory The name of the remote directory from which the data was
Name downloaded.
Script Name The script that was used for the collection.
Status The status of the collection task—Succeeded or Failed.
End Time The time the collection finished.
Error Message The reason the task failed.
Collected The number of files that were collected.
Parsed The number of files that were parsed.
177
Log Processing Tab

The Log Processing tab displays details of all the log processing tasks for the selected
network elements. It contains the following fields:
Field Description
Status The status of the task—Succeeded or Failed.
Start Time The date and time the task started.
Run Time The number of minutes the task ran.
sent.
Log Processing Statistics Tab

The Log Processing Statistics tab displays details of the log processing tasks for the
selected network elements. It contains the following fields:
Field Description
Triggered Time The time the task should have started.
Wait Time The amount of time the task had to wait until it was run, for
example, waiting for an available device to run the task.
Start Time The date and time the task actually started.
End Time The date and time the task ended.
Error Message The reason the task failed. For example, missing raw data.
Date The date of the processed data.
178
Field Description
Hours The time of the processed data.
Number of Files The number of processed files.
Filtered Calls The number of calls that passed the filter criteria, and were loaded
into the call database.
All Calls The total number of calls that were processed.
Mobile Tracking Audit Tab

The Mobile Tracking Audit tab displays details of calls where the user filtered the IMSIs or
IMEIs. It contains the following fields:
Field Description
Action The action performed by the user, for example, Virtual Drive Test,
Traffic Map, and so on.
User The name of the user.
Host The host to which the user is connected.
Filtered Subscriber The IMSIs that were selected by the user.

ID
Filtered Hardware ID The IMEIs that were selected by the user.
Models Tab
The Models tab displays details of all the model tasks for the selected network elements. It
contains the following fields:
Field Description
Start Time The date and time the task started.
Last Model Date The date of the latest model logs.
179
Field Description
sent.
Note: Advanced parameters may be displayed at the end of the report, depending on the
script and parameter definitions of the selected network element. If N/A is displayed in one of
these fields, it means that the default value of the parameter was used.
Model Data Tab

The Model Data tab displays details of all existing models for the selected network elements.
It contains the following fields:
Field Description
Date The date of the model.
Creation Time The date and time the model ran.
Busy Hour The busy hour.
Busy Hour Traffic The busy hour traffic.
Model Statistics Tab

The Model Statistics tab displays details of all the model runs, including the model data (if a
model exists) and the running statistics, for example the start and end time. It contains the
following fields:
Field Description
Triggered Time The time the task should have started.
Wait Time The amount of time the task had to wait until it was run, for
example, waiting for an available device to run the task.
End Time The date and time the task ended.
180
Field Description
Date The date of the model.
Busy Hour The busy-hour of the model.
Busy Hour Traffic The busy hour traffic.
Error Message The reason the model task failed. For example, missing raw data.
Raw Data Tab

The Raw Data tab displays details of the existing raw data folders, including the data type,
number of files, and the size of the files, for the selected network elements. It contains the
following fields:
Field Description
Type The type of data collected, for example, KPIs, processed logs, logs,
OMs, and so on.
Date The date of the collection.
Number of Files The number of files for each type of data.
Size on Disk (KB) The size of the data.
Users Tab
The Users tab displays details about the user permissions for the selected network elements.
It contains the following fields:
Field Description
User Name The name of the user.
Type The type of user—Super Administrator or Engineer.
Region The regions to which the user is assigned.
Serving Host The host of the server to which the user is connected.
Cluster The clusters to which the user is assigned.
Permission The engineer user's read/write permissions. This is not applicable

for administrator users.
181
Managing Notifications
Notifications are messages that are sent to users informing them of activities in the server.
The Notifications pane displays the details for all the notifications you have received for the
servers to which you are currently connected. If required, you can filter the display to show
only those notifications that meet your criteria. The number of days the notifications are saved
and displayed is defined in the server properties.
For example, notifications are sent to inform you of the following: Login errors, model
completion, failure to send mail to user and alerting you to correct the user details,
optimizations that need to be approved (this is sent after a recurrence of a task has
completed, showing the suggested changes to the network), and so on.
Notifications are also sent to your own email address, as entered by the administrator when
defining your user properties. If required, you can disable all notifications in the server
properties.
The Notifications pane contains the following fields:
Field Description
Severity The importance of the notification.

- Error or failed task
Read The read status of the notification.

- Read
- Unread
Server The server to which the notification refers.
Type The item for which the notification was sent, for example, Analysis Task,
Model Task, Cluster, and so on.
Subject A brief description of the contents of the notification.
Received The date and time the notification was received.
Region The region to which the notification refers.
Object The cluster or network element to which the notification refers.
182
Working with Notifications

After you have received a notification, you can open it, copy parts of it to the clipboard, print it,
delete it, or mark it as read or unread. If the notification is for a provisioning task, you can
approve the provisioning. If the notification is about an optimization, you can click the links to
view the optimization or the reports in the relevant Mentor, Mentor Sparks, or Forte client.
If required, you can disable receiving notifications by setting the USE_NOTIFICATIONS
parameter to No.
To open notifications:
1. In the Notifications pane, double-click the notification you want to open. The
notification-status icon changes from to , and the body of the notification is
displayed so that you can read it.
2. If the email contains links, click the link to view the details in the relevant Mentor,
Mentor Sparks, or Forte client.
For example, if the report is about an engineering task, you can click the links to view
the reports or layers. You can also export the plan for manual provisioning.
183
To change the status of notifications:

 In the Notifications pane, right-click the notifications whose status you want to
change from read to unread or vice versa, and then select Mark as Unread/Read.
The notification-status icon changes accordingly, from to .
To print notifications:
1. In the Notifications pane, right-click the notifications you want to print, and click
Print.
-OR-
In an open notification, click .

A standard windows Print dialog box is displayed.
2. Set your print preferences, and click OK.
To delete notifications:
1. In the Notifications pane, right-click the notification(s) you want to delete, and click
Delete. A confirmation message is displayed.
2. Click Yes. The notifications are deleted from the Notifications pane.
Filtering Notifications
If you have multiple notifications, you can filter the list of notifications to display only
notifications that meet certain criteria. For example, you can filter the list to display only
notifications about modeling tasks that succeeded.
To filter the list of notifications:

1. Open the Notifications pane.
2. On the toolbar, click the Filter button . The Table Filter dialog box is displayed.
184
3. In the Column drop-down list, select the column that you want to filter.
4. In the Condition drop-down list, specify the condition operation to use when filtering,
such as contains, is, is not, and so on.
5. Specify the value to use for filtering, and then click Add. The filter criteria you
specified are displayed in the bottom pane, as shown below:
6. [Optional] Repeat steps 3 through 5 to add additional filter criteria, as required. When
multiple filter criteria are defined, an AND relationship exists between them.
7. Click OK. Only notifications that meet the filter criteria will be displayed in the
Notifications pane, and the number of tasks that comply with the filter criteria is
displayed at the top of the pane.
To remove the task filter:

1. Open the Notifications pane.
2. On the toolbar, click . The Table Filter window is displayed.

3. Select the filter criteria, and click Remove.
4. Click OK. The filter is cleared, and all the notifications are displayed in the
Notifications pane.
185
Data Collection
The Mentor Server performs automatic collection tasks from several sources, according to
the schedule set when defining the network elements.
The Mentor Server can also automatically import the physical configuration data for its
configured network elements from the antennas.txt file in the Schema Format or from the
planning tools (if relevant), and then correlates it with the network switch dump data that is
already available in the client, updating the switch dump data if necessary.
 Collection Tasks
 Physical Data Collection Tasks
 Online Collection Tasks
Managing Collection Tasks

The Mentor Server performs automatic collection tasks from several sources, according to the
schedule set when defining the network elements.
The Collection Tasks pane displays the details of each of the data types to be collected from
the network elements belonging to the servers to which you are currently connected.
The Collection Tasks pane contains the following fields:
Field Description
Displays if the collection task failed.
Data Type The type of data being collected, for example, Mobile Statistics,
Configuration, Logs, SMs, OMs, PMs, Performance, Counters, GPEH, and
so on, according to the vendor.
Server The name of the server to which the collection task belongs.
Network The name of the network element from which the data will be collected.
Element
186
Data Collection
Field Description
Status The status of the latest task occurrence:

 Failed: The task has run, and has failed. An icon is displayed next to
the name of the failed task occurrence.
 Canceled: The task was canceled because the running time exceeded
the maximum allowed time set in the advanced parameters when
defining or editing the collection task properties.
Details Displays additional information about the status of the executed task, for
example, Queued.
Started The actual date and time the task started.
Duration The number of minutes the task ran.
Last Failure The reason the collection task failed, for example, the file was not fetched.
Details
Recurrence How often the task will be performed.
Process At The date and time the occurrence is set to take place.
Pattern The frequency of the task recurrence.
Data Device The name of the data device used to collect the data.
Agents The names of the potential agents assigned to execute the task. The name
of the agent that actually executed the task is displayed in the Details
dialog box of the relevant analysis or optimization task occurrence.
Notifications The status of the notification feature for this task.
Next The timestamp of the last collected file, and the date and time from which
Collection data should be collected for the next collection run.
From
Note: This feature works only when using the default "Internal operations"
script.
Description Displays a description or comment entered by the administrator.
187
Working with Collection Tasks

After you have defined the network elements, you can perform the collection tasks
immediately, without waiting for their scheduled time. If the task has already run, and failed,
you can view the failure details of the last task, as well as the view the task properties.
If you want to temporarily disable a single collection task and not the entire collection process,
for example, if there is a switch problem or if you want to perform tests, you can deactivate a
specific collection task.
Tip: To ensure that the collection task does not run endlessly, when creating the collection
task or any time afterwards, you can define a timeout period after which the collection task will
be canceled automatically.
By default, data is collected from the time of the last collection. If required, you can reset the
time so that data is collected from all dates.
To perform a collection task immediately:

 In the Collection Tasks pane, right-click the collection task you want to run, and then
click Run. The status of the task changes to Running, and the current date and time
are displayed in the Started column.
To stop a running collection task:

 In the Collection Tasks pane, right-click the running collection task you want to stop,
and then select Stop. The status of the task changes to Canceled, and the current
date and time are displayed in the Last Performed column.
To deactivate a specific collection task:

 In the Collection Tasks pane, right-click the collection task you want to disable, and
then select Deactivate. The task appears dimmed in the Collection Tasks pane.
 To reactivate the collection task, right-click it and then select Activate.
To collect data from all dates:

 In the Collection Tasks pane, right-click the collection task for which you want to
make a collection for all dates, and then click Reset Next Collection to From All
Dates.
188
Data Collection
To define a timeout period for the collection task:

1. In the Collection Tasks pane, right-click the collection task for which to add a
timeout period and click Properties. The Collection Task Properties dialog box is
displayed.
189
2. Click the Advanced tab.
3. In the General group, enter the maximum number of minutes a task should run
before being terminated in the MAX_TASK_EXECUTION_TIME field. After this
amount of time, the task status will be displayed as Canceled, and a notification will
be displayed.
4. Click OK.
190
Data Collection
Filtering Collection Tasks

If you have multiple collection tasks, you can easily filter them to display only the tasks that
suit your filter criteria in the Collection Tasks pane. For example, you can filter the pane to
display only failed tasks for on a specific network element.
To filter the collection tasks:

1. Open the Collection Tasks pane.
2. On the toolbar, click . The Table Filter dialog box is displayed.
3. In the Column drop-down list, select the column that you want to filter.
4. In the Condition drop-down list, specify the condition operation to use when filtering,
such as contains, is, is not, and so on.
5. Specify the value to use for filtering, and then click Add. The filter criteria you
specified are displayed in the bottom pane, as shown below:
191
6. [Optional] Repeat steps 3 through 5 to add additional filter criteria, as required. When
multiple filter criteria are defined, an AND relationship exists between them.
7. Click OK. Only the tasks that comply with your filter criteria are displayed in the
Collection Tasks pane, and the number of tasks that comply with the filter criteria is
displayed at the top of the pane.
To remove the task filter:

1. Open the Collection Tasks pane.
2. On the toolbar, click . The Table Filter window is displayed.

3. Select the filter criteria, and click Remove.
4. Click OK. The filter is cleared, and all the collection tasks are displayed in the
Collection Tasks pane.
192
Data Collection
Viewing Collection Task Properties

You can view and edit the properties of a selected collection task, as well as view its history
and the details of a selected task occurrence. If required, you can also view and edit the
advanced properties of multiple selected tasks.
To view the collection task properties:

1. In the Collection Tasks pane, right-click the collection task whose properties you
want to view or edit, and then click Properties. The General tab of the Collection
Task Properties dialog box is displayed.
2. Edit the general task properties, as required:

o General
o History
o Agents
o Advanced
3. Click OK to close the Collection Task Properties dialog box and save your changes.
193
Defining General Collection Task Properties

The General tab enables you to view and edit general properties of the data collection task.
To view the collection task properties:

want to view or edit, and then click Properties. The General tab of the Collection
Task Properties dialog box is displayed.

o Enter a description for the collection task in the Description field. This description
can be viewed in the Collection Task pane.
o By default, data is collected from the time of the last collection. Click Reset to
collect data from all dates.
o Clear the Active check box to deactivate the collection task.
194
Data Collection
o In the Data device list, select the data device that will be used to retrieve the data
from the drop-down list, or click the browse button to open the Add Data
Device dialog box, select a data device and then click OK.
o Select the channel for the selected data device.

o Select a new script from the Script drop-down list.
o In the Remote directory field, enter or select the directory from which to
download the data, and then click Test to test the connection to the remote
directory.
o In the Schedule area, click Recurrence to define how often the selected task
should run. By default, collection tasks are scheduled daily 06:00.
195
Viewing the Collection Task History

The History tab enables you to view the status of all the occurrences of the task. You can
also view the details of a specific task occurrence.
To view the collection task history:

1. Click the History tab to view the status of all the occurrences of this collection task.
2. To view more information about a specific task occurrence, select the task
occurrence and then click the Details button. The Details dialog box is displayed.
196
Data Collection
operations in the selected collection task:
Field Description
Information
Warning
Error
Date and Time The date and time the operation was executed.
optimization, importing environment and model, sanity check,
provisioning, download started, and so on.

197
Viewing the Collection Task Agents

The Agents tab enables you to view or assign the agents that will be used for the collection
tasks.
By default, the Filter agents by storage ID check box is selected, and only agents in the
Central system agent group are displayed. You can clear the check box to display all agents,
and not only those in the Central system agent group.
The Computer column specifies the name of the computer on which the agent resides.
The Storage ID column identifies the storage ID for the agent, and also shows the name of
the agent group to which agent group belongs, in parentheses.
To select the agents to be included in the model selection set:

2. Select the check boxes next to the agents to be included in the collection task.
3. Click OK to save your changes and close the Collection Task Properties dialog box.
198
Data Collection
Editing Advanced Collection Task Properties

The Advanced tab shows the advanced parameters that are taken into account for the
selected collection task.
If required, you can also view and edit the advanced parameters for multiple selected
collection tasks by right-clicking the required tasks and then clicking Properties.
199
The following groups of parameters, and their default values, are displayed:
Note: Script group parameters are displayed only if you select to use your own scripts, and
not the default <Internal Operations> script.

Dashboard group

(Default = Yes)

(Default = Yes)
200
Data Collection
File Transfer group


(Default = NONE)


as x/y.

(Default = 14)

(Default = No)
collection.
FILES_TIMESTAMP_REWIND_IN_H The amount of time before the last collection from

OURS which to start collecting new files.
(Default = 0)

(Default = .*)
INDEX The index file from the planning tool, relevant for
the physical data collection.
PROFILES_TRANSLATOR Converts the profile names used by the planning

tools to the names in the existing profiles.

(Default = Yes)
201
Forwarding group

automatically.
(Default = N/A)
(Default = N/A)
FTP_FORWARD_PORT
(Default = 21)
FTP_FORWARD_ROOT
(Default = N/A)
FTP_FORWARD_USER
(Default = N/A)

(Default = No)
General group

(Default = 20)

(Default = Yes)
client.
very heavy.
202
Data Collection

collection.
(Default = Yes)

FAIL_IF_RESOLVING_FAILED Whether to fail the entire switch dump collection task if

the file itself could not be parsed.
(Default = Yes)

script.
default.


SECONDS attempt.
(Default = 60)

collection task.
(Default = 0)


(Default = No)
203

(Default = No)
parameter.

(Default = 262,144)

(Default = GZ)

(Default = Yes)
the new values.
Defining Task Recurrences

When creating the network elements, or scheduling optimization, provisioning, and analysis
tasks, you can define the frequency at which the tasks are performed. You can also edit
future task occurrences at any time after the network elements and tasks have been defined.
To define a task recurrence:

1. In the relevant dialog box, click Recurrence.
-OR-
In the Action menu, click Recurrence.
The Task Recurrence dialog box is displayed.

2. Specify the time the recurrence should take place. Tasks can be performed daily,
weekly, or monthly.
3. Click OK to close the dialog box and apply your changes.
204
Data Collection
To set daily task recurrences:

1. In the Recurrence area, select the Daily option. The Task Recurrence (Daily)
2. In the Process At area, select the time at which the selected recurrence takes place.
o Recur every, and then select the frequency of the recurrence. If required, you
can exclude one or more times by selecting them, and then clicking Delete.
o Once a day
The occurrence times are displayed in the Pattern area, starting at the time selected
in the Process At field.
4. Select the Ignore weekends check box if you do not want the task to be executed
over weekends.
5. Click OK to close the Task Recurrence dialog box and apply the changes.
205
To set weekly task recurrences:

1. In the Recurrence area, select the Weekly option. The Task Recurrence (Weekly)
2. In the Process At field, select or enter the time the recurrence(s) should take place.
3. In the Pattern area, select the day(s) of the week the recurrence should take place.
To set monthly task recurrences:

1. In the Recurrence area, select the Monthly option. The Task Recurrence (Monthly)
2. In the Process At field, select or enter the time the recurrence should take place.
206
Data Collection

o The date of the month, and the monthly frequency. For example you can define
tasks to run on the first day of every month, or the 10th day of every 3rd month,
and so on.
o The day of the month, and the monthly frequency. For example, you can define
tasks to run on the first Sunday of every month, or the third Monday of every
second month.
Importing Data Collection Task Properties

You can import a previously exported file containing all the visible and hidden data collection
task properties used in other collection tasks, so that they can be used in the one or more
selected collection tasks.
To import the data collection task properties:

1. In the Collection Tasks pane, right-click the collection tasks to which to import the
collection task properties, and then click Import Data Collection Task Properties.
The Import Data Collection Task Properties dialog box is displayed.
2. Browse to the required file and then click Open. A progress bar is displayed while the
task properties are being imported, and then a message is displayed notifying
whether the file was successfully imported.
207
Exporting Data Collection Task Properties

You can export the collection task properties file containing all the visible and hidden
parameters as well as the filters used in a selected collection task, so that they can be
imported and used and used in other servers or collection tasks.
To export the data collection task properties:

want to export, and then click Export Data Collection Task Properties. The Export
Data Collection Task Properties dialog box is displayed.
2. Browse to the location to which to export the task properties, enter a name for the file,
and click Export. A progress bar is displayed while the task properties are exported,
and then a dialog box is displayed notifying whether the export process completed
successfully.
208
Data Collection
Managing Physical Data Collection Tasks

The Mentor Server can automatically import the physical configuration data for its configured
network elements from the antennas.txt file in the Schema Format or from the planning tools
(if relevant), and then correlates it with the network switch dump data that is already available
in the client, updating the switch dump data if necessary.
Notes:
 Sectors that are locked for physical data collection updates will not be affected.
 Existing data in the server will not be overwritten by missing, invalid, or partial data
from the physical data collection.
The Physical Data Collection Tasks pane displays the details of each of the physical data
collection tasks belonging to the servers to which you are currently connected.
The Physical Data Collection Tasks pane contains the following fields:
Field Description
Displays if the physical data collection task failed.
Name The name of the physical data collection task.
Data Source The source of the physical data—TEOCO, Asset, Atoll, PlantEV, or S-Info.
Network The name of the network elements for which the physical data was
Elements collected.
Server The name of the server to which the physical data collection task belongs.
209
Field Description
Status The status of the latest task occurrence:

 Canceled: The task was canceled because the running time exceeded
the maximum allowed time set in the advanced parameters when
defining or editing the task properties.
Details Displays additional information about the status of the executed task, for
example, Queued.
Last Failure The reason the collection task failed, for example, the file was not fetched.
Details
Recurrence How often the task will be performed.
Agents The names of the potential agents assigned to execute the task.
The name of the agent that actually executed the task is displayed in the
History tab of the task
210
Data Collection
Adding Physical Data Collection Tasks

The physical data collection task automatically collects new and updated physical data for the
network elements belonging to the servers to which you are connected.
Before you run a new physical data collection task:
 Ensure that you have a scheduled network physical configuration data dump, and
note the period of the dump creation (per day, per week).
 Check whether all the network BSCs/RNCs are exported to one file or to several files,
and the location and format of these files.
 Check whether there are any cells that do not need to be part of the automatic
physical network configuration data import, and if necessary, lock these cells out of
the automatic import mechanism.
Note: If there are multiple physical network configuration data export files, one for each group
or per individual BSC/RNC, a physical collection task should be defined separately for each
group. Each individual task will then process the relevant physical export file.
To add a new physical data collection task:

 In the navigation pane, right-click Physical Data Collection Tasks and then select
New Physical Data Collection Task. If you are currently connected to more than
one server, you will be prompted to select the server that will run the new physical
data collection task.
The General page of the New Physical Data Collection Task wizard is displayed.
The New Physical Data Collection Task wizard contains three steps:
 Step 1 - General, enables you define the general properties of the task, for example,
the device used to retrieve the data and the remote directory from which to retrieve
the data.
 Step 2 - Network Elements, enables you to define the network elements for which the
data is collected.
 Step 3 - Schedule, enables you to schedule the time and days recurring physical
collection tasks should be processed.
211
Defining General Physical Data Collection Task Properties

The General page of the New Physical Data Collection Task wizard enables you to define the
general properties of the task, for example, the name of the task, the device used to retrieve
the data, the remote directory from which to retrieve the data, and so on.
To define the general physical data collection properties:

1. In the Task Name field, enter a new name for the task, if required.
2. In the Data source field, select the source of the data.
3. In the Data device field, select or browse to the data device used to retrieve the
network data.
4. In the Channel field, select the channel from the selected data device.
5. In the Script field, select the script that is used for the collection. For more
information on scripts, refer to the Scripting section in the Mentor Server Installation
Guide.
6. In the Remote directory field, enter or select the directory from which to download
the data, and then click Test to test the connection to the remote directory.
Note: If you are running a physical data collection task for GSM network elements
after completing the physical data, browse to the edited antenna file.
212
Data Collection
7. If required, click Advanced to view and edit the parameters that are taken into
consideration during the physical data collection.
8. Click Next to proceed to the Network Elements page.
213
Defining Physical Collection Task Network Elements

The Network Elements page enables you to define the network elements for which the data
will be collected, based on how the physical data export is created. For example, if a single
export file is created for the entire network, the task will include all the network elements.
To define the physical data collection task network elements:

1. To add a network element, click Add. The Add Network Elements dialog box is
displayed, showing a list of available network elements, and if relevant, the regions to
which they are currently assigned, their time zones, and the number of sectors or
sector carriers.
214
Data Collection
2. Select the required network elements and click OK.
Note: The selected network elements must all be from the same time zone and use
the same technology.
3. To remove a selected network element, select the network element and then click
Remove.
4. To view the properties of a selected network element, select the network element and
then click Properties. The Network Element Properties dialog box is displayed, in
read-only mode.
5. Click Next to proceed to the Schedule page.
215
Scheduling Physical Data Collection Tasks

In the Schedule page, you can define the recurrence of the task, coordinated with the
scheduled creation of the physical dump.
To define the task schedule:

1. By default, physical data collection tasks are scheduled to run daily at 02:00. If
required, click Recurrence and then define the task recurrence.
2. Click Finish. A progress bar is displayed while the task is submitted to the server,
and then the new task is displayed in the Physical Data Collection Tasks pane, per
server.
Note: If you have created the task for multiple servers, a progress bar is displayed
for each cluster and server to which the task is submitted, and then the task is
displayed in the Physical Data Collection Tasks pane, per server.
Processing the Collected Physical Data

The Mentor Server will collect the physical data dump according to the schedule defined for
the tasks, and parse it. The server will then try and to match each cell in the processed file to
an existing cell in the Mentor, Mentor Sparks, or Forte client internal network configuration
retrieved from the network switch dump.
The automatic matching process will target new cells retrieved from the switch dump that do
not yet have any physical data, for example, location data, antenna profiles, etc. The
matching process will then automatically complete the missing data for these cells.
216
Data Collection
In addition, for existing cells that do have physical data, the client will update the information
to reflect the processed data from the physical data dump:
 If a new cell is identified from the physical data dump, but no network switch dump
configuration is available (e.g. planned cells), the cell will be ignored until it becomes
available in the network switch dump.
 If a new cell is identified in the network switch dump, but no physical data is available
from the automatic physical network configuration task import, the new cell will be
created in the client configuration and will be indicated as having missing data in the
Network Elements pane, and will require running the Physical Data Completion
wizard.
Viewing Physical Data Collection Task Properties

You can view and edit the properties of a selected physical data collection task, as well as
view its history and the details of a selected task occurrence.
To view the physical data collection task properties:

1. In the Physical Data Collection Tasks pane, right-click the physical data collection
task whose properties you want to view or edit, and then click Properties. The
General tab of the Physical Data Collection Task Properties dialog box is
displayed.
217

o In the Task name field, enter a new name for the task.
o In the Next collection from field, click Reset if you would like to collect all files,
and not only the files since the last collection.
o Clear the Active check box to deactivate the physical data collection task.
o In the Data source field, select the source of the data.
o In the Data device field, select or browse to the data device used to retrieve the
network data.
o In the Channel field, select the channel from the selected data device.
o In the Script field, select the script that is used for the collection.
For more information on scripts, refer to the Scripting section in the Mentor
Server Installation Guide.
o In the Remote directory field, enter or select the directory from which to
download the data, and then click Test to test the connection to the remote
directory.
3. Click the Network Elements tab to add, remove, or view the properties of a selected
network element.
218
Data Collection
4. Click the Schedule tab to edit the task recurrence.
5. Click the History tab to view details or reports of each task occurrence.
219
6. Click the Agents tab to assign additional agents to the task.
7. Click the Advanced tab to edit the parameters that are taken into consideration when
collecting the physical data.
220
Data Collection
Physical Data Collection Task Notifications

By default, notifications are sent concerning the physical data collection tasks. If required, you
can disable receiving notifications for one or more specific tasks.
To disable physical data collection task notifications:

 In the Physical Data Collection Tasks pane, right-click the tasks for which to disable
notifications, and then click Disable Notifications. No notifications will be sent for the
selected tasks, and Disabled will be displayed in the Notifications column.
To enable the disabled physical data collection task notifications:

 In the Physical Data Collection Tasks pane, right-click the tasks for which to enable
notifications, and then click Enable Notifications. Notifications will be sent for the
selected tasks, and Enabled will be displayed in the Notifications column.
Editing Advanced Physical Data Collection Task Properties

If required, you can edit the advanced physical data collection task properties that are taken
into account during the physical data collection when creating the task, or anytime afterwards.
To edit the advanced physical data collection task properties:

1. In the Physical Data Collection Tasks pane, right-click the task whose properties
you want to edit, and then click Properties. The General tab of the Physical Data
Collection Task Properties dialog box is displayed.
221
Note: Script group parameters are displayed only if you select to use your own
scripts, and not the default <Internal Operations> script.
By default, the parameters are displayed according to parameter group, but you
can display them alphabetically, if required.

222
Data Collection
Dashboard group

(Default = Yes)

(Default = Yes)
File Transfer group


(Default = NONE)


as x/y.

(Default = 14)

(Default = No)
collection.
FILES_TIMESTAMP_REWIND_IN_ The amount of time before the last collection from

HOURS which to start collecting new files.
(Default = 0)

(Default = .*)
223
INDEX_FILE The index file from the planning tool, relevant for
the physical data collection from the planning tool.
(Default = \antennas.csv)
PROFILES_TRANSLATOR The file used for translating planning tool profiles to

those in the Mentor profile repository.

(Default = Yes)
Forwarding group

automatically.
(Default = N/A)
(Default = N/A)
FTP_FORWARD_PORT
(Default = 21)
FTP_FORWARD_ROOT
(Default = N/A)
FTP_FORWARD_USER
(Default = N/A)

(Default = No)
224
Data Collection
General group

(Default = 20)

(Default = Yes)
client.
very heavy.

collection.
(Default = Yes)

FAIL_IF_RESOLVING_FAILED Whether to fail the entire switch dump collection task if

the file itself could not be parsed.
(Default = Yes)

script.
default.
225


SECONDS attempt.
(Default = 60)

collection task.
(Default = 0)


(Default = No)

(Default = No)
parameter.

(Default = 262,144)

(Default = GZ)

(Default = Yes)
the new values.
226
Data Collection
Importing Physical Data Collection Tasks

You can import one or more previously exported physical data collection tasks from other
networks or servers, so that they can be used in the current or selected server.
To import a physical data collection task:

1. On the File menu, select Import and then Physical Data Collection Tasks. If you
are connected to more than one server, you will be prompted for the server to which
to add the imported tasks. Select the server, and click OK. The Import Physical
Data Collection Tasks dialog box is displayed.
2. Browse to or select the folder containing the physical data collection tasks you would
like to import, and click Open. All the physical data collection tasks in the folder are
displayed in the Physical Data Collection Tasks area, and any that already exist in
the server are marked as such.
227
3. Select the check boxes next to the tasks you would like to import, and then click OK.
Note: Only data collection tasks that do not already exist in the server can be
imported.
4. A progress bar is displayed while the selected tasks are being imported. You can also
view the progress of the import process on the left of the status bar.
After the data collection tasks have been imported, a message is displayed notifying
whether the task data was successfully imported.
5. Click Close. The imported tasks are displayed in the Physical Data Collection
Tasks pane.
Exporting Physical Data Collection Tasks

You can export one or more physical data collection tasks so that they can be imported and
used in other servers or networks.
To export a physical data collection task:

1. In the Physical Data Collection Tasks pane, right-click the physical data collection
tasks you want to export, and then click Export Physical Data Collection Tasks.
The Export dialog box is displayed.
228
Data Collection
2. Browse to the location to which to export the selected tasks, and click Save. A
notification is displayed warning that this could overwrite existing files.
3. Click Yes to continue. A progress bar is displayed while the tasks are being exported.
If required, click Minimize to hide the progress bar. You can also view the progress of
the export process on the left of the status bar.
4. As soon as the export process is complete, a dialog box is displayed. Click Close to
close the dialog box.
Managing Online Collection Tasks

The Online Collection Task pane displays the stream providers of each of the online
collectors. It displays the connections between the online connectors and the NSN Emil.
The Online Collection Task pane contains the following fields:
Field Description
Server The name of the server to which the online collection task belongs.
Network Element The name of the network element for which the Emil is collecting the
data.
Reported RNC The RNC from which the information is gathered.
Online Collector The location of the Emil client collector service.
Host The streamer host — the computer with which the Emil
communicates.
229
Field Description
Port The port used by the Emil.
Status The status of the NSN collector service.
Run Duration The amount of time the task ran.
Last Failure Reason The latest reason the task failed.
Throughput The speed of the data.
Average Payload The average amount of data received for the task time.
You can filter the displayed fields by adding or removing columns:

 To remove a column, right-click the column you want to remove and then click
Remove this Column. The selected column will be hidden.
 To display or hide multiple columns, right-click the column header and then click
Customize. The Customize Columns dialog box is displayed, enabling you to select
the columns to be displayed or hidden.
230
Data Collection
Viewing Online Collection Task Properties

You can view and edit the properties of a selected stream provider any time after the online
collection task has been created.
To view the online collection task properties:

1. In the Online Collection Tasks pane, right-click the stream provider whose
properties you want to view or edit, and then click Properties. The Online Collection
Task Properties dialog box is displayed, showing the General tab.
The Online Collection Task Properties dialog box contains the following tabs:
o General, which displays general properties of the stream provider.
o Advanced, which displays the advanced properties that are taken into account for
the online collection.
3. Click OK to close the Online Collection Task Properties dialog box and apply your
changes.
231
General Online Collection Task Properties

The General tab of the Online Collection Task Properties dialog box enables you to view and
edit the general properties of the selected stream providers.
To define the general properties:

1. In the Host name field, enter a new name for the computer with which the Emil client
communicates.
2. In the Port field, enter the port number used by the Emil.
3. In the Output location field, enter or browse to the path of the data. This location
should include the server name and be accessible to all computers, for example,
\\<server name>\<file name>.
4. In the Network element field, click the browse button and then select the
required network element.
5. Click OK to save your changes and close the dialog box.
232
Data Collection
Advanced Online Collection Task Properties

The Advanced tab of the Online Collection Task Properties dialog box enables you to view
and edit the advanced properties that are taken into account for the online collection tasks.
To set the advanced online collection task parameters:

expanded showing all the available parameters:
FILE_LENGTH_MIN The number of minutes of data that exist in the log

data file.
Default = 15
NUM_OF_GROUPS The number of files with the specified number of

minutes of data based on the FILE_LENGTH_MIN
Default = 10
parameter, that will be created.
RECONNECT_ON_CONNECTION_ The number of seconds the NSN collector will wait

ERROR_TIMEOUT_SEC before trying to reconnect to the Emil.
Default = 60
3. Click OK to apply your changes and close the Online Collection Task Properties
dialog box.
233
Data Processing
The Data Processing branch in the navigation pane contains the following items:
 Call Database Monitoring
 Log Processing Tasks
 Model Tasks
Managing Call Database Monitoring

The Call Database Monitoring pane enables you to verify whether the call data was
correctly inserted into the call database. It displays a row for each network element relevant to
the call database. You can view the call database properties of each of these network
elements, as well as the properties of each call database monitoring task.
By default, all calls are saved in the call database, but if required, you can filter the calls to be
saved.
The Call Database Monitoring pane contains the following fields:
Field Description
Latest File The status of the latest file-processing task. If the status is Partial, it
Processing Status means that at least one call was rejected. You can view the details of
the rejected calls in the Log.
Latest Data Date The date of the latest data.
Failed Files - Last The number of files that failed in the last 12 hours.
12 Hours
Failed Files - Last The number of files that failed in the last 24 hours.
24 Hours
Pending Files The number of files waiting to be processed.
Pending in Agent The number of files that have been processed, but have not yet been
moved from the agent to the call database.
234
Data Processing
By default some fields are hidden. You can customize the displayed fields by adding
or removing columns:
o To remove a column, right click the header of the column you want to remove and
then click Remove this Column. The selected column will be hidden.
o To display or hide multiple columns, right-click the column header and then click
Customize. The Customize Columns dialog box is displayed, enabling you to
select the columns to be displayed or hidden.
235
Defining Call Database Properties

You can view and edit the call database properties, such as the number of days to save calls,
as well as the advance parameters that are taken into account when configuring the call
database.
To view the call database properties:

1. In the Navigation pane, right-click Call Database Monitoring and then click
Properties. The Call DB Properties dialog box is displayed.
The Call DB Properties dialog box contains the following tabs:
o General, which enables you to view and edit the general settings for the call
database.
o Advanced, which enables you to view and edit the system-level parameters for
configuring the call database.
236
Data Processing
Defining General Call Database Properties

The General tab enables you to define the general settings for the call database. It also
enables you to validate the advanced parameter settings.
You can view and edit the following properties in the General tab:
 No. of days to save calls in database: The number of days to save calls in the call
database.
 No. of days to save call files: The number of days to save call files. These files are
artifacts that are created by the server during the log processing task run, and then
transferred to the call database machine. They contain material for the call database
before the call data is entered.
 No. of days to save call uploading logs: The number of days to save the logs
about the call data being uploaded to the call database.
 No. of parallel loaders: The number of services that load data into the call database
at the same time.
 Validate: Click this to check the values of the parameters in the Advanced tab.
237
Defining Advanced Call Database Properties

The Advanced tab shows the system-level parameters for configuring the call database.
These parameters can also be viewed and edited in the Call DB Parameters and Call DB
Server Parameters.
Call DB Parameters:
CALLS_DATA_PULL_DELAY_ Defines how long a file should be kept in the agent

SECONDS before being taken to the call database, in order to
(Default = 10) ensure that the file is not currently being changed.
CALLS_MONITORING_ Defines how often the database will check if there is

RECURRENCE new data in the server that can be uploaded to the
(Default = 0 0/10 * * * ?) call database.
238
Data Processing
CALL_DB_CONCURRENT_ Defines the maximum number of database-loading

UPDATES processes that can work in parallel.
(Default = 5)
CALL_DB_HOST Defines the call database host.
CALL_DB_PASSWORD Defines the call database password.
CALL_DB_PORT Defines the port used for the call database.

(Default = 1521)
CALL_DB_REPOSITORY_PATH Defines the path for the call database repository.

(Default = N/A) Note: The repository must be saved on the central
system LAN.
CALL_DB_SID Defines the call database SID.
CALL_DB_UPDATE_RECURRENCE Defines how often to upload the available data from

(Default = 0 0/15 * * * ?) the server.
CALL_DB_USER Defines the call database user.
CALL_DB_USE_TNS Whether to use TNS in the call database.

(Default = No)
Call DB Server Parameters:
CALL_DB_LOCAL_PATH_ON_ Defines the location in the call database machine in

SERVER which server data is temporarily stored by the
(Default = N/A) server.
CALL_DB_SERVER_PASSWORD Defines the password of the call database

(Default = N/A) administrator user.
CALL_DB_SERVER_USER Defines the user name of the call database

(Default = N/A) administrator user.
239
Starting and Stopping the Call Database Loading Process

The start/stop call database feature controls the call loading mechanism. The first time you
start the call database, an internal database is set up and tables and so on are defined. When
you stop the call database, the loaders are brought down, and the loading mechanism
becomes inoperable.
To start the call database:

1. In the navigation pane, right-click Call Database Monitoring and then click Start
Call DB. A progress bar is displayed while the call database is started. If there are
any problems, a dialog box is displayed.
2. Click Details to view the reasons why the call database cannot be started.
To stop the call database
3. In the navigation pane, right-click Call Database Monitoring and then click Stop Call
DB. A progress bar is displayed while the call database is stopped. If there are any
problems stopping the call database, a dialog box is displayed.
4. Click Details to view the reasons the call database cannot be stopped.
240
Data Processing
Viewing Network Element Call Database Monitoring Properties

You can view the properties of the call database loading for all network elements involved.
To view the call database properties for a network element:

1. In the Call Database Monitoring pane, right-click a selected network element and
then click Open. The Network Element Call Database Monitoring dialog box is
displayed, open to the Files tab.
The Network Element Call Database Monitoring dialog box contains the following tabs:
o General, which enables you to view general call database loading properties of
the selected network element.
o Files, which enables you to view the details of each of the files that are created for
uploading the data into the call database.
241
Viewing the Network Element Call Database Monitoring File Properties

The Files tab displays each of the files that are created for uploading data into the call
database, for the selected network element. Each file can contain thousands of calls.
You can view the following information in the Files tab:

 File Name: The name of the file used for uploading data into the call database.
 Size: The size of the file.
 Data Loading Time: The time the data was uploaded into database.
 Data Content Time: The date of the data.
 Status: The status of the file used for uploading data into the database. A status of
Partial means that at least one call in the file was rejected.
To view the log details of a selected file:

 In the Files tab, select a file and then click Details. The log of the selected file is
displayed in your default text editor.
242
Data Processing
Viewing the Network Element Call Database Monitoring General Properties

The General tab displays properties such as the name of the network element, and the
number of files that were not uploaded.

 Network element: The name of the network element.
 Latest file processing status: The status of the latest file that was used for
uploading data into the database. A status of Partial means that at least one call in
the file was rejected.
 Latest data date: The date of the latest data.
 Failed files last 12 hours: The number of files that failed in the last 12 hours.
 Failed files last 24 hours: The number of files that failed in the last 24 hours.
 Pending files: The number of files waiting to be processed.
243
Managing Log Processing Tasks

The log parsing tasks create positioned calls in Schema Format for the model task and for the
call database. These tasks dramatically reduce the modeling time by parsing logs throughout
the day, and not only right before the modeling task run. By default, the log processing tasks
deliver the data to the call database every 30 minutes, based on a user-defined recurrence.
3G log processing tasks are created automatically when creating new network elements.
GSM log processing tasks must be created manually.
Notes:
 Log processing tasks are disabled when created, and must be activated before they
can be used. TEOCO recommends activating the log processing tasks even if you do
not have a license for the call database, in order to expedite the modeling process. If
you do not activate the log processing task, the logs will be parsed at the beginning
of the modeling task run.
 If a filter is defined, it is relevant only for the data delivered to the call database, and
not for the model.
 Log processing tasks for GSM network element tasks only can be deleted.
The Log Processing Tasks pane displays the details of each of the log processing tasks of
the network elements belonging to the servers to which you are currently connected.
The Log Processing Tasks pane contains the following fields:
Field Description
Error Displays if the log processing task failed.
Server The name of the server to which the task belongs.
Network The name of the network element for which the task is to be run.
Element
Technology The technology used in the model.
244
Data Processing
Field Description
Status The status of each occurrence of the task:

 Succeeded: The task has run, and as succeeded. The system sends
you a notification with a link that opens the task in the relevant Mentor,
Note: Regular scheduled tasks will show the current percentage of the
task run in parentheses. If the percentage is not displayed, it is an
ongoing task.
 Cancelled: The task was cancelled by the user.
Details Additional information about the status of the task, for example, Queued.
Started The actual time the task started.
Duration The amount of time the task ran.
Last Failure The reason the log processing task failed, for example, the GPEH group is
Details not defined properly.
Pattern The recurrence pattern, for example, once a day, every 23 hours etc.
Agents The agent used for the task. This is the same agent that is used for the
modeling task.
Details The type of call details that will be saved in the database, based on the
Collection options selected in the log-processing task Call Filters.
Calls The type of calls that will be saved in the database, based on the option
Collection selected in the log-processing task Call Filters.
Note: By default some fields are hidden.
You can customize the displayed fields by adding or removing columns:

 To remove a column, right click the header of the column you want to remove and
245
Defining Log Processing Task Properties

Log processing tasks are created automatically when new network elements are defined. You
can view and edit the properties of a selected log processing task any time after it has been
created.
To view the log processing task properties:

1. In the Log Processing Tasks pane, right-click the log processing task whose
properties you want to view or edit, and then click Properties. The Log Processing
Task Properties dialog box is displayed, showing the General tab.
The Log Processing Task Properties dialog contains the following tabs:
o General, which enables you to activate the task, as well as schedule the task
recurrence.
o History, which enables you to view the task history.
o Agents, which enables you to select the agents that will be used in the log
processing task.
o Call Filters, which enables you to define which calls and call details will be saved
in the call database.
into account for each task.
246
Data Processing

3. Click OK to close the Log Processing Task Properties dialog box, and apply your
changes to the selected task. A confirmation message is displayed to indicate
whether you changes were applied successfully.
4. Click OK.
Defining General Log Processing Properties

The General tab enables you to activate the task and edit the scheduled task recurrence.

 Network element: The name of the network element for which the task was created.
 Last status: The last status of the network element.
 Active check box: Select this to activate the log processing task. TEOCO
recommends activating the log processing task even if you do not have a license for
the call database, in order to expedite the model creation.
 Schedule: The recurrence, time, and pattern in which the task is run. By default, the
task is run every 30 minutes, but you can edit the task recurrence if required. The log
processing task should be triggered to run according to the required call database
update time (i.e. every 15 minutes.) The model should still run once a day.
Note: For ongoing log processing tasks, set the task recurrence pattern to Once a
day.
247
To activate the log processing task:

1. Select the Active check box.
2. Click OK.
Viewing the Log Processing Task History

The History tab enables you to view the date, time, and status of each log processing task
occurrence, as well as the details of each operation in a selected occurrence.
To view the log processing task history:

1. In the Logs Processing Tasks pane, right click the task whose history you want to
view, and then click Properties. The Log Processing Task Properties dialog box is
displayed.
2. Click the History tab. The date, time, and status of each occurrence of the task are
displayed.
248
Data Processing
3. To view the details of a selected occurrence, click Details. The Details dialog box is
displayed, showing each operation that took place during the task occurrence.
The Details dialog box enables you to view the following information for each
operation in the selection log processing task:
Field Description
Information
Warning
Error
Time

249
Viewing the Log Processing Task Agents

The Agents tab enables you to view and select the agents that will be included in the log
processing task.
Note: These agents should be the same agents that are used for the modeling task.
To select the agents to be included in the log processing task:

2. Select the check boxes next to the agents to be included in the task.
3. Click OK to save your changes and close the Log Processing Task Properties dialog
box.
250
Data Processing
Defining Log Processing Task Call Filters

The Call Filters tab enables you to select whether calls and/or call details should be saved in
the call database. If required, you can create a filter to save only specific calls or call details.
By default, neither calls nor call details are saved in the call database.
Notes:
 You can save calls to the call database only if your license supports it. If you have
the relevant license, any filters you select for the call database will affect the call
details as well.
 If you do not have a license for the call database, you can define which call details
should be saved and displayed in the Ultima Mentor Event Viewer.
When you select the Call Filters tab, a progress bar is displayed while the task details are
downloaded from the server.
251
If required, you can:

 Save all calls or call details
 Filter the calls to be saved
 Filter the call details to be saved
 Remove filters
 Edit existing filters
 Save the current filters
 Load previously defined filters
To add all calls and/or call details to the database:

1. In the relevant areas of the dialog box, select one or both of the following options:
o Add all calls to the database
o Save details for all calls
2. Click OK. All calls and/or call details will be saved in the call database.
To filter the calls to be added to the call database:

1. In the upper area of the dialog box, select Add to database only the following
calls.
2. If you want to define more than one filter, select the operator to be used between the
filters.
3. Click Add. The Edit Filter dialog box is displayed.
4. In the Field drop-down list, select the option by which to filter the calls.
5. In the Condition drop-down list, select the filter condition for the value of the selected
field. For example, is in, contains, does not contain.
6. In the Values field, enter the value by which to filter the selected field. Depending on
the Field selection, you can also click the browse button and then select the
values from a list, calendar, and so on.
7. Click OK to save the filter. The new filter will be added to the filter area in the upper
area of the dialog box.
8. Repeat steps 3 to 7 for each new filter you would like to add.
9. Click OK to apply the new filters and close the Call Filters tab. Only calls that meet
your filter criteria will be saved in the call database.
252
Data Processing
To filter the call details to be saved in the call database:

1. In the lower area of the dialog box, select Save call details only for the following
calls.
2. If you want to define more than one filter, select the operator to be used between the
filters.
3. Click Add. The Edit Filter dialog box is displayed.
4. In the Field drop-down list, select the option by which to filter the call details.
5. In the Condition drop-down list, select the filter condition for the value of the selected
field. For example, is in, contains, does not contain.
6. In the Values field, enter the value by which to filter the selected field. Depending on
the Field selection, you can also click the browse button and then select the
values from a list, calendar, and so on.
7. Click OK to save the filter. The new filter will be added to the filter area in the lower
area of the dialog box.
8. Repeat steps 3 to 7 for each new filter you would like to add.
9. Click OK to apply the new filters and close the Call Filters tab. Only call details that
meet your filter criteria will be displayed in the Ultima Mentor Event Viewer.
To remove a filter:
1. In the filter area, select the filter you would like to remove, and click Remove.
2. Click OK to apply your changes and close the Log Processing Task Properties dialog
box.
253
To edit an existing filter:

1. In the relevant filter area, select the filter you would like to edit, and then click Edit.
The Edit Filter dialog box is displayed.
2. Edit the Condition or Values fields as required.

3. Click OK to create the new filter and close the Edit Filter dialog box.
4. Click OK to apply the new filter and close the Log Processing Task Properties tab.
To save the current filters:

1. In the relevant filter area, click Save. A standard Windows Save dialog box is
displayed, enabling you to browse to the location in which to save the filters.
2. Enter the name of the file in the File name field.
3. Click Save. The filters are saved as a .zip file in the specified location.
To load previously saved filters:

1. In the relevant filter area, click Load. A standard Windows Open dialog box is
displayed, enabling you to browse to the file containing the required filters.
2. Select the file and click Open. The loaded filters are displayed in the filter area.
3. Click OK to apply the filters and close the Log Processing Task Properties tab.
254
Data Processing
Defining Advanced Log Processing Task Properties

The Advanced tab shows the system-level parameters that are taken into account when
configuring the selected log processing task and/or call database.
255
GPEH Parameters:
GPEH_GROUP_SIZE The number of files in a GPEH group. When

(Default = 16) collecting GPEHs, it is important to know whether
the entire group has arrived, and when it can be
parsed.
Note: If a group is larger than expected, the server
will assume that there is an error in the
configuration, and fail the task. A message will be
displayed informing you to change the value of this
preference.
PARTIAL_GPEH_GROUPS_DELAY The number of minutes to delay the GPEH log

_MINUTES processing run if the group is not yet "full".
(Default = 0)
General Parameters:
JVM_ADDITIONAL_PARAMS Additional JVM parameters, mainly for debug

purposes.
ONGOING_TASK Whether the task is ongoing.

(Default = No)  Yes: The task will run continuously.
Notes:
o Ensure that the task recurrence pattern is
set at Once a day before running the task.
o CPU utilization will be very high, as ongoing
tasks run in the background all the time.
 No: The task will run according to its scheduled
time.
PROCESSING_DELAY_MINUTES The number of minutes the log files have to wait in

(Default = 0) the agent's storage before they are processed.
Parallel Processing Parameters:
NUMBER_OF_PARALLEL_ The number of threads that can be used in parallel

THREADS to process the log files.
(Default = 1)
256
Data Processing
Retention Parameters:
DELETE_LOGS_AFTER_PROCESS Whether to delete the logs after the processing

ING completed successfully.
(Default = No)
Defining Multi-selection Log Processing Task Properties

Administrator users can view and edit the properties of multiple log processing tasks
simultaneously, any time after they have been created.
To view the log processing task properties:

1. In the Log Processing Tasks pane, right click the tasks whose properties you want
to view or edit, and then click Properties. The Log Processing Task Properties
(Multi-selection) dialog box is displayed.
The Log Processing Task Properties (Multi-selection) dialog box contains the
following tabs:
into consideration for all tasks.
257
o Call Filters, which enables you to define which calls will be added to the call
database.
Defining Advanced Log Processing Properties (Multi-selection)

The Advanced tab shows the system-level parameters that are taken into account when
configuring the selected log processing tasks and/or call database.
258
Data Processing
GPEH Parameters:
GPEH_GROUP_SIZE The number of files in a GPEH group. When

(Default = 16) collecting GPEHs, it is important to know whether
the entire group has arrived, and when it can be
parsed.
Note: If a group is larger than expected, the server
will assume that there is an error in the
configuration, and fail the task. A message will be
displayed informing you to change the value of this
preference.
PARTIAL_GPEH_GROUPS_DELAY The number of minutes to delay the GPEH log

_MINUTES processing run if the group is not yet "full".
(Default = 0)
General Parameters:
JVM_ADDITIONAL_PARAMS Additional JVM parameters, mainly for debug

purposes.
PROCESSING_DELAY_MINUTES The number of minutes the log files have to wait in

(Default = 0) the agent's storage before they are processed.
Parallel Processing Parameters:
NUMBER_OF_PARALLEL_ The number of threads that can be used in parallel

THREADS to process the log files.
(Default = 1)
Retention Parameters:
DELETE_LOGS_AFTER_PROCESS Whether to delete the logs after the processing

ING completed successfully.
(Default = No)
259
Defining Log Processing Task Call Filters (Multi-selection)

By default, all calls are added to the call database. In the Call Filters tab, you can choose
whether to add only specific calls to the database, or leave the filter properties as-is in each of
the selected log processing tasks.
You can add new filters, remove or edit existing filters, as well as save the current filters or
load previously-defined filters.
To filter the calls for the call database for all selected tasks:
1. Select whether to leave the filter properties as defined in each log processing task,
add all calls to the database, or create a filter to add only specific calls to the
database.
2. If you selected Add specific calls to the database option, select the required filter
criteria for all selected tasks:
o In the Field field, select the field by which to filter the calls.
o In the Condition list, select the operator. For example, is in, is not in, and so on.
o In the Values field, enter the value by which to filter the selected field. Depending
on the Field selection, you can also click the browse button and then select
the values from a list.
3. Click Add. The selected filter is displayed in the filter area.
4. Repeat steps 2 and 3 for each filter condition you want to apply.
5. Click OK to filter the calls according to the filter. Only calls that meet your filter criteria
will be saved in the call database.
260
Data Processing
Defining New GSM Log Processing Tasks

Log processing tasks for GSM need to be created manually, but once they have been
created, they run automatically according to schedule.
To add a new GSM log processing task:

 In the navigation pane, right-click Logs Processing Tasks and then select New
GSM Logs Processing Task. If you are currently connected to more than one
server, you will be prompted to select the server that will run the new physical data
collection task.
The General page of the New GSM Logs Processing Task wizard is displayed.
The New GSM Logs Processing Task wizard contains two steps:
 Step 1 - General, enables you define the general properties of the task, for example,
the network elements to collect the data and the clusters that will be included in the
model calculation set.
 Step 2 - Schedule, enables you to schedule the time and days recurring GSM log
processing tasks should be processed.
261
Defining General GSM Log Processing Task Properties

The General page enables you to define the network elements that will be used to collect the
processed logs.
To define the GSM log processing task network elements:

1. To add a network element, click Add. The Add Network Elements dialog box is
displayed.
262
Data Processing
2. Select the network elements that will be used to collect the processed logs, and click
OK. The selected network elements are displayed in the Network Element area.
3. By default, all the clusters to which the selected network element belongs are
included in the calculation set. If you selected the JOINEDCLUSTER option in the
NEIGHBOR_NE_MATCHING advanced server parameter, you can include only
selected clusters to be included in the model calculation set.
Select the required network element, and then click Clusters. The Clusters
<network element> dialog box is displayed.
4. Select the check boxes next to the clusters whose sectors should be included in the
model calculation set, and then click OK.
263
Scheduling GSM Log Processing Task Properties

In the Schedule page, you can define the time and days the GSM log processing task should
be run.
To define the log processing schedule:

1. By default, GSM log processing tasks are scheduled to run daily at 01:00. If required,
select a new time from the Process at drop-down list.
2. By default, GSM log processing tasks are scheduled to run every day. If required,
clear the check boxes next to the days the task should not run.
3. Click Finish to save your changes and add the task to the list of tasks in the Logs
Processing Tasks pane.
264
Data Processing
Activating Log Processing Tasks

Log processing tasks are created automatically when creating network elements. By default,
the log processing tasks are disabled, and they must be activated in order to parse the log
data throughout the day, and not only right before the modeling task run.
TEOCO recommends activating the log processing tasks even if you do not have a license for
the call database, in order to expedite the modeling process.
To activate a log processing task:

 In the Log Processing Tasks pane, right-click the log processing task you would like
to activate and then click Activate.
-OR-
In the General tab of the Log Processing Task Properties dialog box, select the
Activate check box, and then click OK.
265
Managing Model Tasks

A model task defines each modeling period that should be used for modeling network
elements. The Model Tasks pane displays the details for each of the modeling tasks for the
network elements belonging to the servers to which you are currently connected.
By default, the Busy Hours modeling period is created when defining the network elements,
but you can create additional modeling periods for mornings, evenings, and special
occasions. You can also schedule recurring model tasks when defining a new modeling
period or anytime afterwards.
The Model Tasks pane contains the following fields:
Field Description
Displays if the model task failed.
Model Task The modeling period to be run.
Server The name of the server to which the model belongs.

Note: By default, this column is hidden. To display the column, right-click
in the column header and then select Server from the shortcut menu.
Network The name of the network element for which the model is to be run.
Element
Technology The technology used in the model: CDMA, EVDO, UMTS, GSM.

 Succeeded: The task has run, and as succeeded. The system sends
you a notification with a link that opens the task in the relevant Mentor,
266
Data Processing
Field Description
Started The actual time the task started.
Duration The amount of time the task ran.
Last Failure The reason the model task failed, for example, missing raw data.
Details
Latest Model The date of the latest model logs.

Date
Pattern The recurrence pattern, for example, once a day, every 23 hours etc.
Agents The agent used for the task.

 To remove a column, right-click the column you want to remove and then click
Remove this Column. The selected column will be hidden.
267
Adding Modeling Periods

The modeling process takes the relevant data from the collected raw data, for example
dropped calls, positioning, and so on, and builds a calculated representation. It is very
important that the modeling process and the collection tasks are coordinated, so that the
model will be based on the latest collection data.
By default, the busy-hour modeling period is created when defining the network element, but
you can add morning, evening, and additional modeling periods for special events. When
defining a new modeling period, you select all the model tasks for that period. You can also
define a schedule for recurring modeling periods.
To add a new modeling period:

 In the navigation pane, right-click Model Tasks and then select New Modeling
Period. If you are currently connected to more than one server, you will be prompted
to select the server to which to add the modeling period.
The General page of the New Modeling Period wizard is displayed.
The New Modeling Period wizard contains three steps:

 Step 1 - General, enables you to name the modeling period, and select the network
elements for which to create the modeling period.
 Step 2 - Modeling Period, enables you to define the time for the modeling period.
 Step 3 - Schedule, enables you to schedule the time and days recurring modeling
tasks should be processed.
268
Data Processing
Defining General Modeling Period Properties

The General page of the New Modeling Period wizard enables you to define the network
elements that are included in the new period. Each selected network element will be listed as
a separate task in the Model Tasks pane.
To define the general modeling period properties:

1. In the Modeling period name field, enter a name for the new modeling period, if
required.
2. Click Add to select the network elements to be included in the new modeling period.
The Add Network Elements dialog box is displayed.
269
3. Using standard Windows functionality, select the network elements to be included in

the new modeling period.
4. Click OK. The selected network elements are displayed in the Network Elements
area of the General page. A new modeling task will be created for each network
element selected, which will be displayed in the Modeling Tasks pane.
5. By default, all the clusters to which the selected network element belongs are
included in the calculation set. If you selected the JOINEDCLUSTER option in the
NEIGHBOR_NE_MATCHING advanced server parameter, you can include only
selected clusters to be included in the model calculation set.
Select the required network element, and then click Clusters. The Clusters
<network element> dialog box is displayed.
6. Select the check boxes next to the clusters whose sectors should be included in the
model calculation set, and then click OK. The selected clusters are displayed next to
the network elements in the Network Elements area of the General page.
7. Click Next to proceed to the Modeling Period page.
270
Data Processing
Defining the Modeling Period

The Modeling Period page enables you to define the new modeling period. The times for the
morning and evening modeling periods are defined by default when creating each network
element, but you can edit these times if required. If required, you can also add modeling
periods for one or more user-defined special events.
To define the modeling period:

1. Select one of the following options for the modeling period:
o Mornings: The model will be created for the morning hours, as defined in the
Model Content tab in the Network Element Properties dialog box.
o Evenings: The model will be created for the evening hours, as defined in the
o Special event: The model will be created according to your selection in the Dates
and Time area.
2. If you are creating a model for a special event:
o Select the date and time to start and stop the model task from the relevant drop-
down lists.
o By default, weekends are excluded, but you can change this by selecting whether
to exclude the weekend from the Exclude weekends drop-down list.
o Click Add to add the new special-event period. It is displayed in the Dates and
Time area.
o Repeat this procedure for each special-event period you want to create.
271
Scheduling Modeling Periods

In the Schedule page, you can define the time and the days the modeling task should be
processed.
To define the modeling schedule:

1. By default, modeling tasks are scheduled to run daily at 01:00. If required, select a
new time from the Process at drop-down list.
2. By default, modeling tasks are scheduled to run every day. If required, clear the
check boxes next to the days the model should not run.
3. Click Finish to save your changes and add the tasks in the new modeling period to
the list of model tasks in the Model Tasks pane.
272
Data Processing
Viewing Model Task Properties

You can view the properties of a selected modeling task or edit its schedule or modeling
period, any time after the modeling period has been defined. Any changes to the task and
modeling period affect all future occurrences of the modeling task.
To view the model task properties:

1. In the Model Tasks pane, right-click the model task whose properties you want to
view, and from the menu select Properties. The Open Model Task dialog box is
displayed.
2. To view the task properties, select Open the task. The Model Task Properties
dialog box is displayed, showing the General tab:
273
The Model Task Properties dialog can contain the following tabs:
o General: Enables you to view the general properties of the modeling task, for
example, its modeling period, the network element on which it was run, the last
task occurrence status and date, and so on. You can also view the days for which
there is a model. These dates are displayed in bold in the calendar area on the
right side of the General tab.
o Clusters: Enables you to select the clusters whose sector carriers will be included
in the calculation set.
Note: This tab is displayed only if you select JOINEDCLUSTER in the

NEIGHBOR_NE_MATCHING advanced server parameter.
o Schedule: Enables you to view or edit the time or days the modeling task should
be processed.
Select the time of day to process the modeling task from the Process at drop-down list.
Select the check boxes next to the days for which to process the recurring modeling task.
o Time Filter: Enables you to filter the hours used in the modeling period.
o Agents: Enables you to view or assign the agents for performing this task
o History: Enables you to view the date, time, and status of each occurrence of the
task, as well as the details of a selected task occurrence.
o Advanced: Enables you to view and edit the advanced properties that are taken
into account during the modeling phase.
o Click OK to close the Model Task Properties dialog box. Any changes made will
affect all future occurrences of the model task.
274
Data Processing
Viewing Modeling Period Properties

You can view and edit the properties of a selected modeling period, or edit its schedule or any
of the modeling task properties, any time after the modeling period has been defined. Any
changes to the task and modeling period affect all future occurrences of the modeling task.
Note: You cannot change Busy Hour modeling periods.
To view the modeling period properties:

1. In the Model Tasks pane, right-click the model task whose modeling period you want
to view, and from the menu select Properties. The Open Model Task dialog box is
displayed.
2. To view them modeling period, select Open the modeling period. The Modeling
Period Properties dialog box is displayed showing the General tab, displaying the
name of the modeling period, and all the network elements that are included in the
task.
Note: Clusters are displayed only if you select JOINEDCLUSTER in the

NEIGHBOR_NE_MATCHING advanced server parameter.
275
3. In the General tab, you can add or remove network elements, view the network
element properties, or select which of the network element clusters should be used:
o To add or remove a network element, select the network element and then click
Add or Remove.
o To view the properties of a selected network element, click Properties.
o To view or edit the clusters used, click Clusters.
o Click OK to save your changes and close the Modeling Period Properties dialog
box, or click the Modeling Period tab.
4. CDMA, EVDO, and UMTS networks: In the Modeling Period tab, you can view the
modeling period properties, or add or remove special-event periods.
o To add a special event, select the date and time to start and stop the special
event from the relevant drop-down lists and then click Add.
o To remove an existing special event, select the special event and then click
Remove.
Note: Each special-event modeling period must include at least one special
event. To remove all the special events, you have to delete the modeling period.
276
Data Processing
5. GSM networks: In the Modeling Period tab for GSM networks, you can select
whether to use the default filter, or to load a filter template for the model.
6. Click OK to save your changes and close the Modeling Period Properties dialog box.
Selecting Model Task Clusters

The Clusters tab enables you to select the clusters whose sectors will be included in the
model calculation set.
By default, all clusters are included in the calculation set.
277
To select the clusters to be included in the calculation set:

1. Select the check box next to the clusters you want to include in the calculation set.
2. Click OK.
Viewing the Model Task Schedule

The Schedule tab enables you to schedule the time and day the model task should run.
By default, model tasks are scheduled to run daily at 01:00.
To schedule the model task:

1. In the Process at field, select a new time to start running the model task.
2. Select the check boxes next to the days the task should run.
3. Click OK.
278
Data Processing
Viewing Modeling Task Time Filter Properties

By default, the modeling task includes all hours, but you can filter the period to include only
specific hours to include in the model.
To filter the modeling task period:

1. Select the Model specific hours option.
2. Select the hours from which and until which to include in the model task.
3. Click Add. The selected time range is displayed in the specific hours area.
4. If required, repeat steps 2 and 3 for any additional times to include in the model.
5. Click OK. The model will run the task for the selected hours only.
279
Viewing the Model Task Agents

The Agents tab enables you to select the agents that will be included in the model selection
set.
To select the agents to be included in the model selection set:

2. Select the check boxes next to the agents to be included in the model selection set.
3. Click OK to save your changes and close the Model Task Properties dialog box.
280
Data Processing
Viewing Model Task History

You can view the date, time, and status of each modeling task occurrence. You can also view
and save the details of each operation in a selected occurrence, as well view the reports for
the occurrence.
To view the model task history:

1. In the Model Tasks pane, right-click the model task whose history you want to view,
and then click Properties. The Open Model Task dialog box is displayed, enabling
you to view the properties of the current task or of its modeling period.
2. Select Open the task, and click OK. The Model Task Properties dialog box is
displayed, showing the General tab.
281
3. Click the History tab. The starting date and time, status, and model date of each
occurrence of the task are displayed.
4. To view the details of a selected occurrence, click Details. The Details dialog box is
displayed, showing each operation that took place during the task occurrence.
282
Data Processing
operation in the selected modeling task:
Field Description
Information
Warning
Error
Time

5. If required, click Save to save the model task details.

6. To view the model reports for a selected occurrence, click Reports. A progress bar is
displayed while the reports are loaded, and then the Reports dialog box is displayed
showing the reports that are relevant to the selected task occurrence.
7. Select the report you want to view and then click Open. The selected report is
displayed in Microsoft Excel format.
283
Viewing Advanced Model Task Properties

If required, you can edit the advanced model task properties that are taken into account
during the modeling phase.
To edit the advanced model task properties:

1. In the Model Tasks pane, right-click the model task whose properties you want to
view, and from the menu select Properties. The Open Model Task dialog box is
displayed.
2. To view the task properties, select Open the task. The Model Task Properties
284
Data Processing


Call Details group
SAVE_VENDOR_INTERNAL_DETAILS Whether to collect 3GPP details for the event flow

viewer.
(Default = No)
General group
ALLOW_MODELING_WHEN_COLLECTING_DATA Whether to start modeling

tasks while collection tasks are
(Default = Yes)
running.
DASHBOARD_ACCESS_FAILURE_REPORT_ENABLED Whether to create an access

failure report for the dashboard.
(Default = No)
285
DASHBOARD_BLOCK_REPORT_ENABLED Whether to create a block

report for the dashboard.
(Default = No)
DASHBOARD_DROP_REPORT_ENABLED Whether to create a drop report

for the dashboard.
(Default = No)
DASHBOARD_HANDSET_STATISTICS_ENABLED Whether to enable collection of

handset statistics.
(Default = No)
MODEL_ENABLED_CURRENT_DAY Whether to run the model for

the current day.
(Default = Yes)
the new values.
6. Click OK to apply your changes and close the Model Task Properties dialog box.
Viewing the Model Task Reports

The model task reports enable you to view reports relevant to the selected task occurrence.
To view the model task reports:

1. In the Model Tasks pane, right-click the model task whose reports you want to view,
and then click Properties or double click the task row. The Open Model Task dialog
box is displayed, enabling you to view the properties of the current task or of its
modeling period.
286
Data Processing
2. Select Open the task, and click OK. The Model Task Properties dialog box is
3. Click the History tab. The starting date and time, status, and model date of each
occurrence of the task are displayed.
287
4. To view the model reports for a selected occurrence, select the occurrence and then
click Reports. A progress bar is displayed while the reports are loaded, and then the
Reports dialog box is displayed showing the reports that are relevant to the selected
task occurrence.
5. Select the report you want to view and then click Open. The selected report is
displayed in Microsoft Excel format.
Working with Model Tasks

After you have created a modeling period, you can:
 Delete one or more selected tasks, or the entire modeling period
Note: The Busy Hours model task cannot be deleted.
 Deactivate the entire modeling task
Note: The Busy Hours model task cannot be deactivated.
 Run a modeling task
Note: You can manually run a modeling task only if there are days that have not yet
been modeled, and they contain raw data.
 View the task properties

 Edit the model task schedule
 View the task history
288
Data Processing
To delete a model task:

1. In the Model Tasks pane, right-click the model task you want to delete, and select
Delete. The Delete Model Task dialog box is displayed, enabling you to select
whether to delete the selected model task, or the entire modeling period.
o Select Delete the task to delete only the selected task.

o Select Delete the modeling period to delete all the model tasks in the modeling
period to which the selected task belongs.
2. Click OK to close the Delete Model Task dialog box. The model task or modeling
period is deleted, and will not be used in the future.
To deactivate a model task:

1. In the Model Tasks pane, right-click the model task you want to deactivate, and
select Deactivate. A confirmation message is displayed, warning that deactivating
the modeling period will deactivate all the model tasks in the modeling period.
2. Click OK to deactivate all the tasks in the modeling period. The tasks are displayed
dimmed in the Model Tasks pane.
To run a model task:

1. In the Model Tasks pane, right-click the model task you want to run manually, and
select Run. A confirmation message is displayed, warning that running the task will
use extensive system resources.
289
2. If required, click Advanced to define the dates of the raw data to be included in the
task occurrence.
o Click the browse button next to the data type for which to display the dates.
The relevant Date dialog box is displayed.
o Select the required dates, and click OK.

3. In the Model Run Configurations dialog box, click Yes to run the model period. A
message is displayed to confirm that the model task has started.
4. Click OK. The model task status changes to Running, and the current progress is
shown in parentheses.
290
Data Processing
Deleting Model Tasks

If required, you can delete one or more model tasks or their modeling periods.
Notes:
 The Busy Hour modeling period cannot be deleted.

 If the model task being deleted is the only one that contains the specific modeling
period, the modeling period will be deleted as well.
 If the model task contains a model, you must first delete the model days using the
To delete a model task:

1. In the Model Tasks pane, right-click the model task you want to delete, and click
Delete. The Delete Model Task dialog box is displayed.
2. Select Delete the task if you want to remove the task. If the modeling period contains
only the task to be deleted, a confirmation message is displayed notifying that the
entire modeling period will also be deleted.
291
o Click Details to view details of the optimizations and dates that will be deleted.
o Click OK to continue. The model task is deleted from the Model Tasks pane, and
will not be run by the server.
3. Select Delete the modeling period if you want to remove the entire modeling period.
A confirmation message is displayed.
 Click Details to view details of the optimizations to be deleted.
 Click OK to delete the modeling period.

292
Managing Engineering Task Occurrences

Tasks are routine actions that the system should perform on a selected cluster. Some tasks
are performed once only, while other tasks are recurrent.
After an analysis or optimization has been run in the client, it can be scheduled to run as an
analysis, optimization, or provisioning task in the server. Tasks are executed automatically
according to the scheduling information. Multiple engineering tasks can run simultaneously,
and each task can include multiple templates.
Managing optimization tasks
Managing analysis tasks
Managing provisioning tasks
Note: You can provision analysis and optimization tasks only if your license supports
provisioning.
Managing Optimization Tasks

Optimization tasks can be scheduled directly from the client or from the Server Admin, using
the optimization template. The Optimization pane displays the details for each of the
optimization tasks belonging to the servers to which you are currently connected.
If you are an administrator user, you can view and edit the tasks of all the users in the
network. If you are an engineer user, you can view and use the tasks in the clusters assigned
to you, and edit only the tasks that were created or submitted by you.
Note: Assign an optimization task to an agent, as described in Assigning Agents.
293
The Optimization pane contains the following fields:
Field Description
Displays if the task failed.
Name The name of the recurring task.
Cluster The group of network elements being analyzed or optimized.
Model Period The modeling period used in the analysis or optimization.

 Succeeded: The task has run, and has succeeded. The system sends
you a notification with a link that opens the calculation in the client.
Created By The user that created the task.
History tab of the task.
Note: By default, some fields are hidden. To display these fields, right click the column
header and then select the field from the shortcut menu.
294
Adding Optimization Tasks

After you have run an optimization task in the client, you can use the same template to
schedule additional optimization tasks in the server. When adding an optimization task, you
have to select the cluster and sectors to be optimized, the model period to be included, as
well as the template to be used. If required, you can add multiple templates per task.
Note for administrator users: If you are currently connected to more than one server, you
will be prompted for the servers to which to add the optimization task. You can run the
optimization tasks on multiple servers for multiple clusters simultaneously, using the same
templates.
To add an optimization task:

 Expand the Task Occurrences item in the navigation pane, right-click Optimization
and then click New Optimization Task.
Note for administrator users: If you are currently logged in to more than one
server, the Select Server dialog box is displayed, displaying the servers to which you
are currently connected, and to which you can add the new optimization task.
o Select the servers to which to add the optimization task and click OK.
A status bar is displayed while connecting to the servers, and then the General page
of the New Optimization Task wizard is displayed.
The New Optimization Task wizard contains three steps:

 Step 1 - General, enables you to define the general properties for the new
optimization task, for example, the name of the optimization, and the optimization
templates to be used.
 Step 2 - Modeling Data, enables you to define the modeling data that should be used.
 Step 3 - Schedule, enables you to define when the task will run.
295
Defining General Optimization Task Properties

Single Server
The General page enables you to define the general properties for the task, for example, the
name of the task, the cluster and sectors to be optimized, and the optimization template to be
used. If required, you can add multiple templates in the same task, including analysis
templates, as long as there is at least one optimization template. You can also edit the name
of the calculation for a specific template, as well as change the order in which each task will
run.
To define the general task optimization properties:

1. In the Task name field, enter a new name for the task, if required. If you do not enter
a new name, the default name will be used.
2. In the Cluster field, select the cluster to be optimized.
3. Select the sectors to be optimized:
o All sectors in the cluster: Select this option to optimize all the sectors in the
cluster
o Selection: Select this option to load a previously saved sector selection, and then
click the browse button to select the file with the sector selection.
296
4. In the Calculations area, click Add to select an optimization template to use. The
Template dialog box is displayed.
5. Browse to the required template and then click Open. The optimization template is
displayed in the Calculations area.
6. If required, repeat steps 4 and 5 for each additional template you want to add.
7. If required, you can add or remove templates, edit the name of the calculation for a
specific template, as well as change the order in which each task will run.
8. Click Next to proceed to the Modeling Data page.
297
Multiple Servers - Administrator users only

The General page enables you to define the general properties for the task for all selected
servers, for example, the name of the task, and the optimization template to be used. If
required, you can add multiple templates in the same task, including analysis templates, as
long as there is at least one optimization template. You can also edit the name of the
calculation for a specific template, as well as change the order in which each task will run.
To define the general task optimization properties:

298
2. In the Calculations area, click Add to select an optimization template to use. The
3. Browse to the required template and then click Open. The selected template is
displayed in the Calculations area.
5. If required, you can add or remove templates, edit the name of the calculation for a
specific template, as well as change the order in which each task will run.
299
Defining Modeling Data for an Optimization Task

Single Server
The Modeling Data page enables you to define the modeling period for the task, and the
modeling days that will be included in the task.
To define the modeling data for the task:

1. In the Period field, select the modeling period to include in the optimization. By
default, the daily busy hours are used, but you can select to use a different modeling
period, if one has been defined.
2. In the Number of Modeling Days field, specify or select the number of model days to
use in the optimization.
3. In the Week days area, select one or both of the following check boxes, if required:
o Excluded days: Select this check box to ignore the days that were defined for
exclusion from engineering tasks, such as special days or holidays. This data will
not be included in the task.
o Ignore weekends: Select this check box to ignore weekends from the
optimization. This data will not be included in the task.
300

The Modeling Data page enables you to define the clusters and modeling periods for the
task, as well as the modeling days that will be included in the task.

1. In the Cluster field, select a cluster to be optimized.
2. In the Modeling period field, select the modeling period for the cluster. By default,
the daily busy hours are used, but you can select to use a different modeling period if
one has been defined.
3. Click Add. The selected cluster and its modeling period are displayed in the dialog
box.
4. Repeat steps 1 to 3 for each cluster and modeling period to be optimized.
5. In the Number of Modeling Days field, specify the number of model days to use in
the optimization.
o Ignore weekends: Select this check box to ignore weekends from the
optimization. This data will not be included in the task.
301
Scheduling Optimization Tasks

In the Schedule page, you can define the recurrence of the task. If you are scheduling a
neighbor list task, you can also define whether the task data should be collected and written
to the dashboard.
To define the optimization schedule:

1. By default, optimization tasks are scheduled to run daily at 08.30. If required, click
Recurrence and then define the task recurrence.
2. If you are scheduling a neighbor list optimization, you can select the Set as
dashboard for analysis check box for relevant data about this task to be written to
the dashboard database whenever the task is executed.
3. In the Dashboard Market Name field, specify the name of the task, as defined on the
dashboard.
4. Click Finish. A progress bar is displayed while the optimization task is submitted to
the server, and then the new task is displayed in the Optimization pane.
Note for administrator users: If you have created a task for multiple servers, a
progress bar is displayed for each cluster and server to which the task is submitted,
and then the task is displayed in the Optimization pane, per server.
302
Editing Optimization Task Properties

You can view the properties of a selected optimization task any time after it has been defined.
If required, you can edit the properties of any of the recurring tasks that you submitted. For
example, you can deactivate the task, or change the sectors to be optimized. The changes
will affect all future occurrences of the task.
To edit the optimization task properties:

1. In the Optimization pane, right-click the optimization task whose properties you want
to edit, and then click Properties. A progress bar is displayed while the task details
are downloaded, and then the Optimization Task Properties dialog box is
Note: The History tab is displayed only when viewing the properties of the task
series, and not for a specific occurrence.
2. Edit the fields in the General, Modeling Data, Schedule, and Agents tabs, as
required.
3. Click OK to save your changes and close the Optimization Task Properties dialog
box. A progress bar is displayed while the changes are submitted to the server. The
updated properties are displayed in the Optimization pane, and will be used for all
future task occurrences.
303
Editing the Optimization Task Agent Properties

When a task is assigned to a specific agent, only that agent can execute the task. When a
task is assigned to an agent group, any agent within that group can execute the task. By
default, tasks are assigned to the Central System agent group.
The Agents tab enables you to view and edit the agents that are currently assigned to the
optimization task.
 The Computer column specifies the name of the computer on which the agent
resides.
 The Storage ID column identifies the storage ID for the agent. This column also
shows the name of the agent to which the agent belongs, in parentheses.
To edit the agents assigned to an optimization task:

1. If required, select the Storage check box and then select an agent group by which to
filter the list of available agents. If you do not select the Storage check box, all the
available agents from all groups are displayed.
2. In the list of agents, select the check boxes for the agents to assign to the
optimization task, or clear the check boxes to remove the agents from the task.
3. Click OK to save your changes and close the Optimization Task Properties dialog
box.
304
Viewing the Optimization Task History

You can view the date, time, and status of each optimization task occurrence, as well as the
details of each operation in a selected occurrence.
To view the optimization task history:

1. In the Optimization pane, right-click the optimization task whose history you want to
view, and then click Properties. A progress bar is displayed while the task details are
downloaded, and then the Optimization Task Properties dialog box is displayed,
2. Click the History tab. The date and time each occurrence of the task started, as well
as the status of each occurrence of the task are displayed.
305
3. Select the occurrence whose details you want to view, and click Details. The Details
dialog box is displayed, showing each operation that took place during the task
occurrence.
operation in the selected optimization task:
Field Description
Information
Warning
Error
Time

306
4. Click Reports to display the Reports dialog box showing the reports for the task.
Viewing the Optimization Task Reports

The optimization task reports enable you to view reports relevant to the task, including reports
relating to the network import and the model.
To view the optimization task reports:

1. In the Optimization pane, right-click the optimization task whose reports you want to
view, and then click Properties or double-click the task row. A progress bar is
displayed while the task details are downloaded, and then the Optimization Task
displayed.
307
3. Select the occurrence whose details you want to view, and click Reports. A progress
bar is displayed while the reports are being loaded, and then the Reports dialog box
is displayed, showing all the reports that are relevant to the selected task occurrence,
including import and model reports.
4. Select the report you want to view and click Open. The selected report is displayed in
Microsoft Excel format.
Managing Analysis Tasks

Analysis tasks can be scheduled directly from the client or from the Server Admin, using the
analysis template. The Analysis pane displays the details for each of the analysis tasks
belonging to the servers to which you are currently connected.
308
Field Description
Displays if the task failed.
Name The name of the recurring task.
Model Period The modeling period used in the analysis or optimization.

 Succeeded: The task has run, and has succeeded. The system sends
you a notification with a link that opens the calculation in the client.
History tab of the task.
309
Adding Analysis Tasks

After you have scheduled an analysis task using the client, you can use the same template to
schedule additional analysis tasks. When adding an analysis task, you have to select the
cluster and sectors to be analyzed, the model period to be included, as well as the template to
be used. If required, you can add multiple templates per task.
Note for administrator users: If you are currently connected to more than one server, you
will be prompted for the servers to which to add the analysis task. You can run the analysis on
multiple servers for multiple clusters simultaneously, using the same templates.
To add an analysis task:

 Expand the Engineering Tasks item in the navigation pane, right-click Analysis and
then click New Analysis Task. A status bar is displayed while connecting to the
server, and then the General page of the New Analysis Task wizard is displayed.
310
Note for administrator users: If you are currently logged in to more than one
server, the Select Server dialog box is displayed, displaying the servers to which you
are currently connected, and to which you can add the new analysis task.
o Select the servers to which to add the analysis task and click OK. A status bar is
displayed while connecting to the servers, and then the General page of the New
Analysis Task wizard is displayed.
The New Analysis Task wizard contains three steps:

 Step 1 - General, enables you to define the general properties for the new analysis
task, for example, the cluster to be analyzed and the analysis templates to be used.
 Step 2 - Modeling Data, enables you to define the modeling data that should be used.
 Step 3 - Schedule, enables you to define when the task will run.
311
Defining General Analysis Task Properties

The General page enables you to define the general properties for the analysis task,
according to whether you are creating a task for one server or multiple servers.
Single Server
name of the task, the cluster and sectors to be analyzed, and the template to be used. If
required, you can add multiple QE or analysis templates in the same task, remove tasks, edit
task information, and change the order in which the tasks will be run.
To define the general analysis task properties:

2. In the Cluster field, select the cluster to be analyzed.
3. Select the sectors to be analyzed:
o All sectors in the cluster: Select this option to analyze all the sectors in the
cluster.
o Selection: Select this to load a previously saved sector selection, and then click
the browse button to select the file with the sector selection.
312
4. In the Analysis area, click Add to select an analysis or QE template to use. The
5. Browse to the required template and then click Open. The template is displayed in
the Analysis area.
7. If required, you can repeat steps 2 and 3 for each cluster to be analyzed.
313

The General page enables you to define the general properties of the analysis task for all
selected servers. For example, the name of the task, and the template to be used. If required,
you can add multiple QE or analysis templates in the same task, remove tasks, edit task
information, and change the order in which the tasks will be run.
To define the general analysis task properties:

314
2. In the Analysis area, click Add to select an analysis or QE template to use. The
3. Select the template to use, and click Open. The template is displayed in the Analysis
area.
4. If required, repeat steps 2 and 3 for each additional template you would like to add.
315
Defining Modeling Data for an Analysis Task

Single Server
The Modeling Data page enables you to define the modeling period for the task, and the
modeling days that will be included in the analysis task.

1. In the Period field, select the modeling period to include in the analysis. By default,
the daily busy hours are used, but you can select to use a different modeling period, if
2. In the Number of Modeling Days field, specify or select the number of model days to
use in the analysis.
o Ignore weekends: Select this check box to ignore weekends from the analysis.
This data will not be included in the task.
316

The Modeling Data page enables you to define the clusters and modeling periods for the
task, as well as the modeling days that will be included in the task.

1. In the Cluster field, select a cluster to be analyzed.
2. In the Modeling Period field, select the modeling period for the cluster. By default,
the daily busy hours are used, but you can select to use a different modeling period if
3. Click Add. The selected cluster and its modeling period are displayed in the dialog
box.
4. Repeat steps 1 to 3 for each cluster and modeling period to be analyzed.
5. In the Number of Modeling Days field, specify the number of model days to use in
the analysis.
o Ignore weekends: Select this check box to ignore weekends from the analysis.
This data will not be included in the task.
317
Scheduling Analysis Tasks

In the Schedule page, you can define the recurrence of the task.
To define the analysis schedule:

1. By default, analyses are scheduled to run daily at 08.30. If required, click Recurrence
and then define the task recurrence.
2. Click Finish. A progress bar is displayed while the analysis task is submitted to the
server, and then the new task is displayed in the Analysis pane.
Note for administrator users: If you have created a task for multiple servers, a
progress bar is displayed for each cluster and server to which the task is submitted,
and then the task is displayed in the Analysis pane, per server.
318
Editing Analysis Task Properties

You can view the properties of a selected analysis task any time after it has been defined. If
required, you can edit the properties of any of the recurring tasks that you submitted. For
example, you can deactivate the task, or change the sectors to be analyzed. The changes will
affect all future occurrences of the task.
To edit the analysis task properties:

1. In the Analysis pane, right-click the analysis task whose properties you want to edit,
and then click Properties or double-click the task row. A progress bar is displayed
while the task details are downloaded, and then the Analysis Task Properties dialog
Note: The History tab is displayed only when viewing the properties of the task
series, and not for a specific task occurrence.
2. Edit the fields in the General, Modeling Data, Schedule and Agents tabs, as
required.
3. Click OK to save your changes and close the Analysis Task Properties dialog box. A
progress bar is displayed while the changes are submitted to the server. The updated
properties are displayed in the Analysis pane, and will be used for all future task
occurrences.
319
Editing the Analysis Task Agent Properties

When a task is assigned to a specific agent, only that agent can execute the task. When a
task is assigned to an agent group, any agent within that group can execute the task. By
default, tasks are assigned to the Central System agent group.
The analysis task Agents tab enables you to view and edit the agents that are currently
assigned to the analysis task.
 The Computer column specifies the name of the computer on which the agent
resides.
 The Storage ID column identifies the storage ID for the agent. This column also
shows the name of the agent to which the agent belongs, in parentheses.
To edit the agents assigned to an analysis task:

1. If required, select the Storage check box and then select an agent group by which to
filter the list of available agents. If you do not select the Storage check box, all the
available agents from all groups are displayed.
2. In the list of agents, select the check boxes for the agents to assign to the analysis
task, or clear the check boxes to remove the agents from the task.
3. Click OK to save your changes and close the Analysis Task Properties dialog box.
320
Viewing Analysis Task History

You can view the date, time, and status of each task occurrence, as well as the agent that
executed the occurrence. You can also view the details of each operation in a selected
occurrence, as well as the reports for the occurrence.
To view the analysis task history:

1. In the Analysis pane, right-click the analysis task whose history you want to view,
2. Click the History tab. The date and time each occurrence of the task started, as well
as the status of each occurrence of the task are displayed.
occurrence.
321
operation in the selected analysis task:
Field Description
Information
Warning
Error
Time

4. Click Reports to display the Reports dialog box showing the reports for the task.
322
Viewing the Analysis Task Reports

The analysis task reports enable you to view reports relevant to the task, including reports
relating to the network import and the model.
To view the analysis task reports:

1. In the Analysis pane, right-click the analysis task whose reports you want to view,
displayed.
323
3. Select the occurrence whose details you want to view, and click Reports. A progress
bar is displayed while the reports are being loaded, and then the Reports dialog box
is displayed, showing all the reports that are relevant to the selected task occurrence,
including import and model reports.
4. Select the report you want to view and click Open. The selected report is displayed in
Microsoft Excel format.
Managing Provisioning Tasks
provisioning.
Provisioning tasks implement the recommended changes in the network, according to the
selected neighbor list, power, and load balancing optimizations. Provisioning tasks can be
scheduled directly from the client after an optimization has been run, or from the Server
Admin once the optimizations have been submitted to the server.
The Provisioning pane displays the details for each of the provisioning tasks belonging to
the servers to which you are currently connected.
324
The Provisioning pane contains the following fields:
Field Description
Displays if the provisioning task failed.
Name The name of the task and its recurrence status:

 denotes a recurring task
 denotes a one-time task run at a specific time
Server The server to which the task belongs.
Optimization The optimization tasks that are included in the provisioning run.
Tasks
Status The status of each occurrence of the task.

 Creation Running: The creation task is currently running. After
completion, the status of the task will change to Creation Succeeded,
Creation Partially Succeeded, or Creation Failed.
 Creation Succeeded – implementation will be run automatically:
The creation phase of the task succeeded, and the implementation
phase will be run automatically according to its schedule.
 Creation Partially Succeeded – implementation should be run
manually: Only part of the creation phase succeeded. To run the
implementation phase, right-click the task and then click Run.
 Creation Failed: The creation task has run, and has failed. An icon is
displayed next to the name of the failed task occurrence.
 Implementation Running: The implementation task is currently
running. After completion, the status of the occurrence will change to
Implementation Succeeded or Implementation Failed.
 Implementation Succeeded: The implementation task has run, and
has succeeded.
 Implementation Failed: The implementation task has run, and has
failed. An icon is displayed next to the name of the failed task
occurrence.
 N/A: The task has not been run yet.
Details Displays additional information about the status of the task, for example,
Queued.
Last Failure The reason the provisioning task failed, for example, if the cluster was
Details inactive or if there are no output scripts.
Recurrence How often the task will be performed, for example, daily, weekly, or
specific date.
325
Field Description
Pattern The frequency of the task occurrence, for example, once a day, Sundays
etc.
Agents The names of the potential agents assigned to execute the task. The name
of the agent that actually executed the task is displayed in the Details
dialog box of the relevant task occurrence.
Notifications Whether notifications should be sent for the task.
Current Plan The name of the provisioning plan that was created and executed in the
Name OSS.
Current Plan The date that the provisioning plan was created in the OSS.
Creation Date
Adding Provisioning Tasks
provisioning.
After you have run an optimization task, you can schedule the task to be provisioned by the
server. You can schedule the provisioning task to be run once only, at a specific time, or you
can schedule it as a recurring task.
If you are an administrator user who is currently connected to more than one server, you will
be prompted for the server to which to add the provisioning task.
326
To add a provisioning task:

 Expand the Engineering Tasks item in the navigation pane, right-click Provisioning
and then click New Provisioning Task. If you are currently logged in to more than
one server, the Select Server dialog box is displayed, enabling you to select the
server to which to add the new provisioning task.
o Select the server to which to add the provisioning task from the drop-down list,
and click OK.
A progress bar is displayed while connecting to the server, and then the General
page of the New Provisioning Task wizard is displayed.
The New Provisioning Task wizard contains three steps:

 Step 1 - General, enables you to define the general properties for the new
provisioning task, for example, the data device to be used, as well as define
advanced parameters that are taken into account during the provisioning.
 Step 2 - Optimization Tasks, enables you to select the optimization tasks that should
be provisioned.
 Step 3 - Schedule, enables you to define when the plan creation and/or
implementation provisioning task will run.
327
Defining General Provisioning Task Properties

name of the task, and the data device to which to copy the scripts. You can also define the
advanced properties that are taken into account during the provisioning.
To define the general provisioning properties:

2. In the Data device field, enter or select or click the browse button to browse to
the host to which to copy or FTP the scripts. You can also click the browse button
to display the Add Data Device dialog box.
328
If required:
o Click to define a new data device.

o Click to view the properties of the selected data device.
o Click to search for a specific data device or property.
Select a data device and then click OK.
3. In the Upload channel field, select the method for uploading the data to the OSS.
4. In the Execute channel field, select the interface to run OSS commands.
5. In the Script field, select the script that is used for the provisioning. For more
information on scripts, refer to the scripting section in the Mentor Server Installation
Guide.
6. Click Test to test the connection to the data device. A progress bar is displayed while
the path of the remote directory is being tested.
7. If required, click Advanced to edit the file transfer and general provisioning
parameters. The Advanced dialog box is displayed.
8. Click Next to proceed to the Optimization Tasks page.
329
Defining Optimization Tasks

The Optimization Tasks page enables you to select the optimization tasks to be provisioned.
To select the optimization tasks to be provisioned:

1. In the Optimization Tasks page, click Add. The Add dialog box is displayed,
showing a list of all available optimizations.
330
2. Select the required optimization tasks to be provisioned using standard Windows

functionality.
3. Click OK. The selected tasks are displayed in the Optimization Tasks area.
4. To add an additional optimization task, click Add to display the Add dialog box, and
then select the required task.
5. To remove a task, select the task and then click Remove.
331
6. To view the properties of a selected task, click Properties. A progress bar is

displayed while the task details are downloaded, and then the Optimization Task
Properties dialog box is displayed, enabling you to edit the task as required.
7. Click Next to proceed to the Scheduling page.
332
Scheduling Provisioning Tasks

Scheduling the provisioning task is made up of two phases—during the plan creation phase,
the .xml file that was generated by the optimization is imported and uploaded to the OSS, and
during the plan implementation phase, the new plan is implemented.
You can specify whether the provisioning tasks should be run manually as required, schedule
the tasks to run as a single provisioning task on a specific date, or schedule recurring tasks.
By default, provisioning tasks recur daily at 1.00.
To schedule the provisioning tasks:

1. To run the plan creation or implementation manually, select Manual only in the
relevant pane.
2. To select a one-time occurrence, select Provision at in the relevant pane, and then
select the date and time the task should be executed from the drop-down lists.
3. To select a recurring occurrence, select Recurring task in the relevant pane, and
then click Recurrence to schedule a recurring provisioning task.
4. To run the plan implementation immediately after the plan creation, in the Plan
implementation pane, select Implement immediately after plan creation.
5. Click Finish. A progress bar is displayed while the task is created, and then the
provisioning task is displayed in the Provisioning pane with a status of Pending.
333
Editing Advanced Provisioning Task Properties

If required, you can edit the advanced provisioning task properties that are taken into account
during the provisioning when creating the task, or anytime afterwards.
To edit the advanced provisioning task properties:

1. In the Provisioning pane, right-click the task whose properties you want to edit, and
then click Properties. The General tab of the Provisioning Task Properties dialog
box is displayed.
334


File Transfer group
FILE_LOCATION_PATTERN The pattern used to filter the file location.

(Default = .*)

(Default = .*)
335
General group

script.
 BY_PATHNAME: If the script location is a
shared folder (begins with "\\") then working
directory is not set (same as "NO"). Otherwise,
working directory is the scripts location.
As a rule of thumb, if the script uses other scripts,
this parameter should be set to YES. Otherwise,
leave the default.
LOG_ALL_OUTPUT Whether to log all provisioning output. This is useful

for troubleshooting purposes.
(Default = No)
MAX_TASK_EXECUTION_TIME The number of minutes the provisioning task should

run before it is automatically terminated. After this
amount of time, the task status is displayed as
Canceled, and a notification is displayed.
Provisioning group
ALLOWED_TIME_BETWEEN_ The maximum number of hours between the end of

CALCULATION_AND_ the optimization task and the beginning of the
PROVISIONING_IN_HOURS provisioning task, in order for the script to remain
valid.
(Default = 24)
ALLOWED_TIME_BETWEEN_PLAN The maximum number of hours between the end of

_CREATION_AND_IMPLEMENTATI the provisioning task (plan creation) and the
ON_IN_HOURS beginning of the implementation task, in order for
the script to remain valid.
(Default = 24)
the new values.
5. Click OK to apply your changes and close the Provisioning Task Properties dialog
box.
336
Editing Provisioning Task Properties

You can view the properties of a selected provisioning task any time after it has been defined.
If required, you can edit the properties of any pending or recurring tasks that were submitted
by you. The changes will affect all future occurrences of the task.
To edit the provisioning task properties:

1. In the Provisioning pane, right-click the provisioning task whose properties you want
to edit, and then click Properties. A progress bar is displayed while the task details
are downloaded, and then the Provisioning Task Properties dialog box is
2. Edit the fields in the relevant tabs, as required.

3. Click OK to save your changes and close the Provisioning Task Properties dialog
box. A progress bar is displayed while the changes are submitted to the server. The
updated properties are displayed in the Provisioning pane, and will be used for all
future task occurrences.
337
Viewing the Provisioning Task History

You can view the date, time, and status of each provisioning task occurrence, as well as the
details of each operation in a selected occurrence.
To view the provisioning task history:

1. In the Provisioning pane, right-click the provisioning task whose history you want to
view, and then click Properties. A progress bar is displayed while the task details are
downloaded, and then the Provisioning Task Properties dialog box is displayed,
2. Click the History tab. The date, time, and status of each occurrence of the task is
displayed, as well as the task phase—creation or implementation.
338
occurrence.
operation in the selected provisioning task:
Field Description
Information
Warning
Error
Time

339
Running Provisioning Tasks

You can run one or more provisioning tasks at any time, without waiting for the scheduled
time. Depending on the status of the task, you can run the plan creation phase, plan
implementation phase, or both the plan creation and implementation phases.
To run a provisioning task:

1. In the Provisioning pane, right-click the provisioning task you want to run and then
select Run. The Run Provisioning Task dialog box is displayed.
2. Select one of the following options:

o Run the plan creation phase: Runs the plan creation phase of the task.
o Run implementation for: Runs the plan implementation phase of the task. This
option is available only after the plan creation has succeeded. (Displayed when
only one task is selected.)
o Run the implementation phase for all selected plans: Runs the plan
implementation phase of the task for all selected plans. This option is available
only after the plan creation of the selected tasks has succeeded. (Displayed when
more than one task is selected.)
o Run plan creation and implementation: Runs both the plan creation and plan
implementation phases of the task.
3. Click OK to close the Run Provisioning Task dialog box and run the task.
340
Managing Regions
Managing Regions
Large networks can be split into different logical regions in the server for administrative and
financial reasons. Each region is a separate entity, with its own users, clusters, network
elements, tasks, and so on.
A region can have a regional administrator, who defines and/or manages all the objects
(users, clusters, network elements) in his region. Each new object that the regional
administrator defines is automatically assigned to his region. Regional administrators can
view only objects that are relevant to their regions, and are unaware of other objects.
The super administrator is not connected to a region, and can define and manage all objects.
Each new object that the super administrator defines is not assigned to any region and will
not be viewed by the regional administrators unless specifically assigned to their region by the
super administrator.
The super administrator can reassign objects (clusters, network elements, users) to a
different region, if required.
The Regions pane displays the details for each of the regions to which you are assigned.
The Regions pane contains the following fields:
Field Description
Region Name The name of the region.
Server The name of the server to which the region belongs.
Regional The name of the administrator assigned to the region.

Administrators
Network The network elements that are used in the region.

Elements
Clusters The clusters that are defined in the region.
341
Adding Regions
The super administrator can define new regions, and the regional administrators responsible
for these regions.
To add a region:
1. In the navigation pane, right-click Regions, then click New Region. If you are
server to which to add the region.
The New Region dialog box is displayed.
2. Enter a name for the region, if required. If you do not enter a name, the default name,
Region<#>, will be used.
3. Click OK. The new region is added to the list of regions in the Regions pane.
342
Managing Regions
Assigning Clusters to Regions

You can assign clusters to regions while defining the new clusters, or at any time afterwards.
All network elements included in the cluster will be assigned to the region.
Note: If the cluster is currently assigned to a different region, the cluster and its network
elements and users will be unassigned from their current region before being assigned to the
new region.
To assign regions to clusters:

1. In the Regions pane, right-click the region to which to assign the cluster, and click
Properties. The Region Properties dialog box is displayed, showing the name of the
region, and any clusters assigned to it.
343
2. To add a cluster, click Add. The Select Clusters dialog box is displayed, enabling to
select the clusters to be included in the region.
3. Select the required clusters and click OK. The selected clusters are displayed in the
Clusters area.
344
Managing Regions
Notes:
 If a cluster contains network elements that are currently also assigned to other
clusters in the current region, the cluster will not be moved to the new region, and a
message will be displayed. Click OK to continue.
 If a cluster contains users that are assigned to the current region, they will be
unassigned from the cluster before it is moved to the new region. A message will be
displayed. Click Details to view the name of the users, or Yes to continue.
4. Click OK to save your changes and close the Region Properties dialog box.
Assigning Network Elements to Regions

A network element can be assigned to multiple clusters but only to one region. You can
assign the network element to a region when defining the network element, or any time
afterwards.
Note: If the network element is already assigned to a region, it will be unassigned from the
currently-assigned region before being assigned to the new region. The network element
cannot be unassigned if it is also assigned to other clusters in the current region.
To assign a network element to a region:

1. In the Regions pane, right-click the region to which to assign the network element,
and click Properties. The Region Properties dialog box is displayed.
2. Click the Network Elements tab. A list of all network elements currently assigned to
the clusters in the region is displayed.
345
3. Click Add. The Add Network Elements dialog box is displayed, showing the list of
available network elements, the regions to which they are currently assigned, if
relevant, and their time zone.
4. Select the required network elements and click OK. The network elements are
assigned to the selected region, and are displayed in the Network Elements tab.
Note: If a network element is currently also assigned to a cluster in a different region,

it cannot be added, and a message is displayed. Click OK.
346
Managing Regions
Assigning Users to Regions

You can assign users to regions while defining the new users, or at any time afterwards.
Note: If a user is assigned to clusters in his current region, he will be removed from those
clusters before being moved to the new region.
To assign users to regions:

1. In the Regions pane, right-click the region to which to assign the user, and click
Properties. The Region Properties dialog box is displayed.
2. Click the Users tab. A list of the users currently assigned to the region, and their user
type is displayed.
347
3. To add a user, click Add. The Select User dialog box is displayed, enabling to select
the users to be assigned to the region.
4. Select the required users using standard Windows functionality, and click OK. The
selected users are added to the Users tab.
Note: If a user is assigned to clusters in his currently-assigned region, you will

receive a message. Click Details to view the list of clusters to which the user is
assigned, or click Yes to remove him from the currently-assigned clusters.
5. To add an additional user, click Add.

6. To remove a user, select the user and click Remove.
7. To view the properties of a selected user, click Properties. A read-only User
Properties dialog box is displayed.
348
Managing Regions
Viewing Region Properties

You can view the clusters, network elements, and users assigned to a selected region any
time after it has been defined. If required, you can also add or remove these items, as well as
view their properties.
To view the region properties:

1. In the Regions pane, right-click the region whose properties you want to view or edit,
and then click Properties. The Region Properties dialog box is displayed.
349
2. To add clusters, network elements, or users, select the relevant tab and then click
Add. The relevant dialog box is displayed, showing all the available items. Select the
required items and click OK.
3. To remove clusters, network elements, or users, select the items to be removed, and
then click Remove.
4. To view the properties of the clusters, network elements, or users, select the item and
then click Properties. The relevant dialog box is displayed.
Deleting Regions
You can delete regions at any time after they have been created. Any users, clusters, or
network elements assigned to the deleted region will be unassigned.
To delete a region:
1. In the Regions pane, right-click the regions you want to delete, and click Delete. A
confirmation message is displayed.
2. Click Yes to delete the selected regions. The regions are deleted from the Regions
pane, and all users that were assigned to the deleted regions are now assigned to all
regions, and the network elements and clusters are now assigned to no regions.
350
Managing Clusters
Managing Clusters
Large networks are divided into areas, called clusters, each with their own management, for
administrative and financial reasons. The division is usually geographic, for example, the
cluster is divided into in areas such as north, south, central, and so on.
The Clusters pane displays the details for each of the clusters belonging to the servers to
which you are currently connected, as well as their network elements, and authorized users.
The Clusters pane contains the following fields:
Field Description
Cluster Name The name of the cluster.
Server The name of the server to which the cluster belongs.
Region The region to which the cluster belongs.
Network The network elements that are used in the cluster.

Elements
Authorized The users that are authorized to use the cluster.

Users Note: The super-administrator user is authorized for all the clusters.
351
Adding Clusters
After you have defined the network elements for collecting the data, you can define the
clusters in which they will be used. If you have multi-vendor network, you can define which
network-element vendor will be the market vendor, and be used in the model. After the
network elements have been assigned to a cluster, the name of the cluster is displayed in the
General tab of the Network Element Properties dialog box.
To add a cluster:
1. In the navigation pane, right-click Clusters, then click New Cluster. If you are
server to which to add the cluster.
The New Cluster dialog box is displayed.
2. In the Cluster name field, enter a name for the new cluster. If you do not enter a
name, the default name, Cluster<#>, will be used.
352
Managing Clusters
3. In the Market Projection field, select the projection for the new cluster, if required. By
default, the cluster identifies the projection of the network elements that are added,
and this is displayed in the Market Projection field. If the network elements do not
already contain a projection, you will have to select one from the list.
Note: If you manually select a market projection, only network elements with the
same projection can be selected.
4. To add network elements to the cluster, click Add. The Add Network Elements
dialog box is displayed, showing a list of the available network elements that can be
assigned to the cluster.
5. Select the network elements to be used in the new cluster, using standard Windows
functionality, and then click OK. The selected network elements are displayed in the
Network Elements area.
6. By default, all network element model data is automatically included for data
collection, but if you have a multi-vendor network, only one vendor can be used for
the model.
To exclude model data for all other vendors, select the network elements belonging to
the vendors that should not be included in the model, and then click the Do not
Include button. The Include Model column now displays No for these network
elements.
Note: For very large clusters containing many sector carriers, you may need to
exclude model data for some network elements in the cluster.
353
Each network element has a defined number of sector carriers, which is specified by
the WB_SECTOR_CARRIER_LIMIT parameter in the Configuration properties. The
sum of the WB_SECTOR_CARRIER_LIMIT values for all network elements in the
cluster defines the maximum number of sector carriers for the cluster. This threshold
cannot be exceeded. If you attempt to exceed this threshold (default = 11,000), then
you must exclude model data from some network elements in the cluster.
o To exclude model data for a network element, select that network element in the
list and then click the Do not Include button. The Include Model column now
displays No for this network element.
o To include model data for a given network element that was previously marked for
exclusion, select the network element and then click the Include model button.
7. Click OK. The details of the new cluster are displayed in the Clusters pane, and the
name of the cluster is displayed in the properties dialog box of each network element
assigned to it.
8. Click OK to save your changes and close the New Cluster dialog box.
Assigning Network Elements to Clusters

You can assign network elements to clusters while defining the new cluster, or any time
afterwards.
To assign network elements to clusters:

1. In the Clusters pane, right-click the cluster to which to assign the network elements,
and then click Properties. The Cluster Properties dialog box is displayed, showing
the General tab, and any network elements currently assigned to the cluster.
354
Managing Clusters
2. Click Add. The Add Network Elements dialog box is displayed, showing the list of
available network elements, and if relevant, the regions to which they are currently
assigned, their time zones, and the number of sector carriers.
3. Select the required network elements and click OK.
4. Click OK to save your changes and close the Cluster Properties dialog box.
355
Assigning Users to Clusters

You can assign users to clusters while defining the new users, or new clusters, or at any time
afterwards. In order to assign a user to a cluster, both the user and the cluster must be from
the same region, or not be assigned to any regions.
To assign users to clusters:

1. In the Clusters pane, right-click the cluster to which you want to add users, and then
click Properties. The Cluster Properties dialog box is displayed.
2. Click the Users tab. A list of the users currently assigned to the selected cluster is
displayed.
3. In the User name field, select the user to add.

Tip: If there are many users, click the browse button to view a list of available
users. Select the required user and click OK.
4. In the Permission field, select the permissions for the user—Read/Write or Read-
only.
5. Click Add. The selected user is displayed in the user area.
6. Repeat steps 2 – 4 for each user you want to add.
7. Click OK to save your changes and close the Cluster Properties dialog box. The
selected users are displayed in the Authorized Users field, in the Clusters pane.
356
Managing Clusters
Assigning Regions to Clusters

You can assign a region to a cluster when defining the cluster or anytime afterwards.
Notes:
 Clusters can be assigned to different regions only if they do not contain network
elements that are also assigned to different clusters in the current region.
 If users in the cluster are assigned to the current region, they will have to be
unassigned from the cluster before it can be moved to the new region.
To assign a region to a cluster:

1. In the Clusters pane, right-click the clusters you want to assign to a region, and then
click Assign Region. The Assign Region dialog box is displayed.
2. You can assign clusters to different regions only if they do not contain network
elements that are also assigned to different clusters in the current region. Select the
Remove cluster's network elements from their current regions check box to
remove the cluster's network elements from their current regions.
3. Select the region to which to assign the selected clusters and click OK. The clusters
are assigned to the selected region.
357
Editing Cluster Properties

You can enter a new name for a selected cluster, change the region to which it is assigned,
add or remove network elements, and add or remove users.
To edit the cluster properties:

1. In the Clusters pane, right-click the cluster you want to edit, and click Properties.
The Cluster Properties dialog box is displayed, showing the General tab with the
name of the cluster, the region to which it is currently assigned, and the network
elements assigned to it.
2. If required, enter a new name in the Cluster name field.

3. In the Region field, select the region to which to assign the cluster.
Note: If there are any network elements that are currently also assigned to other
clusters in the original region, select the Remove cluster's network elements from
their current regions check box to enable moving them to the new region. If you do
not select the check box, you will get a warning notifying that the cluster cannot be
assigned to the new region, with the name of the network elements, the clusters to
which they are currently assigned, and their region.
358
Managing Clusters
4. If required, click Add to add additional network elements, or select a network element
and click Remove to unassign the network element from the cluster.
5. By default, all model data for a network element is automatically included for data
collection. For very large clusters containing many sector carriers, you may need to
exclude model data for some network elements in the cluster.
To exclude model data for a network element, select that network element in the list
and then click the Do not include button. Alternatively, you can right-click a network
element in the list and then select the Do not include model option. The Include
Model column now displays No for this network element.
6. Click the Users tab to assign users to clusters.
7. Click OK to save your changes and close the Cluster Properties dialog box. The
edited properties are displayed in the Clusters pane, and affect all future task
occurrences.
Exporting Clusters
You can export one or more clusters so that they can be imported and used in other servers
or networks.
To export a cluster:
1. In the Clusters pane, right-click the clusters you want to export and then click Export
Cluster. The Export dialog box is displayed.
2. Browse to the location to which to export the selected clusters, and click Save. A
notification is displayed warning that this could overwrite existing files.
359
3. Click Yes to continue. A progress bar is displayed while the clusters are being
exported. If required, click Minimize to hide the progress bar. You can also view the
progress of the export process on the left of the status bar.
4. As soon as the export process is complete, a dialog box is displayed notifying

whether the process was successful. Click Close to close the dialog box.
Importing Clusters
You can import previously exported clusters from other networks or servers that do not exist
in the current network, so that they can be used in the current or selected server.
To import clusters:
1. On the File menu, click Import and then Clusters. If you are connected to more than
one server, you will be prompted for the server to which to add the imported clusters.
The Import Clusters dialog box is displayed.
360
Managing Clusters
2. Browse to or select the folder containing the clusters you would like to import, and
then click Open. All the clusters in the folder are displayed in the Clusters area, and
any that already exist in the server are marked as such.
3. Select the check boxes next to the clusters you want to import, and then click OK.
Note: Only clusters that do not already exist in the server can be imported.
A progress bar is displayed while the selected clusters are being imported. You can
also view the import progress on the left of the status bar.
After the clusters have been imported, a message is displayed notifying whether the
cluster data was successfully imported.
4. Click Close. The imported clusters are displayed in the Clusters pane.
361
Deleting Clusters
You can delete clusters at any time. If the clusters have tasks associated to them, these tasks
must first be deleted before the cluster can be deleted.
To delete a cluster:
1. In the Clusters pane, right-click the clusters you want to delete, and then select
Delete. A confirmation message is displayed.
Note: If there are tasks currently assigned to the cluster, a dialog box is displayed
notifying that the cluster cannot be deleted.
o Click Details to view the assigned tasks that must be deleted before the cluster
can be deleted.
o Click Close to close the dialog box.

2. Click Yes. The clusters are deleted, and removed from the Clusters pane. A
notification is sent to the users assigned to the clusters, informing them of the cluster
deletion.
362
Managing Users
Managing Users
The Users pane displays the details for each of the users belonging to the servers to which
you are currently connected and the regions to which you are assigned.
The Users pane contains the following fields:
Field Description
User Name The name of the user.
Server The name of the server to which the user belongs.
Type The type of user.

Currently three types of users are supported:
 Super Administrator: Super Administrators do the initial
configuration of the system, and then divide the network into regions,
name the regions, create clusters, and create new users, which they
then assign to these clusters. The administrators are usually
responsible for the back-end tasks, such as connecting the server to
the network managers, maintaining the server, and checking that the
scheduled tasks, for example, collection and optimization, are
configured correctly. They can see the whole network, and can perform
all actions in all the clusters.
 Regional Administrator: Regional Administrators can perform all
actions on the clusters and users in the regions to which they are
assigned.
Note: Regional Administrators can be defined only if one or more
regions have already been defined.
 Engineer: Engineers are assigned to regions and clusters, and can
only perform actions in the regions and clusters to which they are
assigned. The engineers take the ready-processed data from the
Mentor Server, analyze it, optimize it, and then return it to the server to
implement the resultant changes in the network.
Region The region to which the user is assigned.

Note: By default, users are assigned to all regions, meaning they can view
all the clusters in the network.
363
Field Description
Clusters The clusters to which the user is assigned, and in which the user can
perform actions.
Serving Host The server to which the user is currently connected.
Adding Users
You can add new users to a connected server at any time. You can assign the region and
clusters to which the user is assigned while defining the user, or when defining the region and
cluster properties. If you are currently connected to more than one server, you will be
prompted for the server to which to add the new user.
To add a new user:

1. In the navigation pane, right-click Users, then click New User. If you are currently
logged in to more than one server, you will be prompted to select the server to which
to add the new user.
o Select the server to which to add the user from the drop-down list, and click OK.
364
Managing Users
The New User dialog box is displayed, enabling you to add the new user's details.
2. In the User name field, enter a name for the new user.
3. In the Type field, select whether the user will have Super Administrator, Regional
Administrator, or Engineer permissions.
Note: Regional Administrators can be defined only if one or more regions have been
defined.
4. In the Password field, enter a password for the user.
Notes:

letter, a lower-case letter, and a digit. These limitations can be changed in
the Authentication settings.
365
5. In the Confirm password field, retype the password to confirm that it is correct.
6. In the Mobile field, enter the user's mobile phone number.
7. In the E-mail field, enter the user's e-mail address to enable receiving notifications via
E-mail. When relevant, the user will receive reports as attachments, and relevant
links to the reports or layers in the relevant Mentor, Mentor Sparks, or Forte clients, or
for manually exporting the plan for provisioning.
8. In the E-mail notifications field, select whether to send the user all notifications
about server related information, or only notifications with high priority, for example,
tasks that failed, or to disable receiving notifications.
9. By default, all new users are activated. To deactivate the user, clear the Active check
box.
Note: The user will not be able to perform any functions until activated.
10. In the Region field, select the region to which the user is assigned. If you do not
assign a region, the user is assigned to all regions.
Note: This field is displayed only if one or more regions have been defined.
11. In the Assigned Clusters area, select or browse to each cluster to which to assign to
the user, select the user permissions, and then click Add. (Read/Write permissions
are required for submitting networks and tasks.) This area is enabled only when
adding Engineer users.
Note: You can add only clusters that belong to the currently selected region. If
clusters have not yet been defined, you can assign the users when defining the
relevant cluster.
12. Click OK. The new user is displayed in the Users pane.
366
Managing Users
Assigning Regions to Users

You can assign a specific region to which the user is assigned when defining the new user, or
anytime afterwards. Note that by default users are assigned to all regions, and can therefore
view all the clusters in the network.
Note: If the user is currently assigned to clusters in a different region, you will be notified of
such. If you choose to continue, the user will be removed from his previously-assigned
clusters and moved to the new region.
To assign regions to a user:

1. In the Users pane, right-click the user to which to assign a region, and click Assign
Region. The Assign Region dialog box is displayed.
2. Select the region to which to assign the user from the drop-down list, and then click
OK. The region to which the user is assigned is displayed in the Region field in the
Users pane.
367
Assigning Clusters to Users

You can assign one or more clusters to a user while creating the new user, or any time
afterwards. When assigning clusters to a user, you can also specify the user permissions on
each cluster.
To assign clusters to a user:

1. In the Users pane, right-click the user to whom you would like to add a cluster, and
then click Properties. The User Properties dialog box is displayed.
2. In the Cluster name field, select the cluster to assign to the user from the drop-down
list.
3. In the Permission field, select the user permissions for this cluster from the drop-
down list. In order for the user to submit networks and tasks, Read/Write permissions
are required.
4. Click Add. The cluster and its user permissions are displayed in the Assigned
Clusters area.
368
Managing Users
5. If required, click Properties to view the properties of a selected cluster.
6. Repeat steps 1-3 for each cluster required.

7. Click OK to save your changes and close the User Properties dialog box.
369
Editing User Properties

Administrator users can modify the properties of other users, for example the clusters to
which users are assigned, and their passwords. Engineer users can view their own
properties, and edit some of them.
To edit the user properties:

1. In the Users pane, right-click the user whose properties you want to edit, and then
click Properties. The User Properties dialog box is displayed.
2. Modify the User name, Type, Password, Mobile, E-mail, and E-mail notification
fields, as required.
370
Managing Users
3. To change the user's password, click Change. The Change Password dialog box is
displayed.
o In the New password field, enter a new password for the user.
Notes:
o In the Confirm password field, re-enter the new password to confirm that it is
correct.
o Click OK.
4. To activate or deactivate a user, select or clear the Active check box, respectively.
5. To assign an additional cluster to the user, select the cluster and the read/write
permissions and click Add.
6. To remove a cluster from the user, select the cluster and click Remove.
7. Click OK to close the User Properties dialog box and save the changes.
371
Exporting Users
You can export one or more selected users so that they can be imported and used in other
networks and servers.
To export a user:
1. In the Users pane, right-click the user you want to export, and then select Export
User. The Export dialog box is displayed.
2. Select the location to which to export the users, and click Save. A notification is
displayed warning that this could overwrite existing files.
3. Click Yes to continue. A progress bar is displayed while the selected users are
exported. If required, click Minimize to hide the progress bar. You can also view the
progress of the export process on the left of the status bar.
4. As soon as the export process is complete, a dialog box is displayed. Click Close to
close the dialog box.
372
Managing Users
Importing Users
You can import one or more previously exported users from other networks or servers, so that
they can be used in the current or selected server.
To import a user:
1. On the File menu, select Import and then Users. If you are connected to more than
one server, you will be prompted for the server to which to add the imported users.
Select the server, and click OK. The Import Users dialog box is displayed.
2. Browse to or select the folder containing the users you would like to import, and click
Open. All the users in the folder are displayed in the Users area, and any that
already exist in the server are marked as such.
373
3. Select the check boxes next to the users you would like to import, and then click OK.
Note: Only users that do not already exist in the server can be imported.
A progress bar is displayed while the selected users are being imported. You can
also view the progress of the import process on the left of the status bar.
After the users have been imported, a message is displayed notifying whether the
user data was successfully imported.
4. Click Close. The imported users are displayed in the Users pane.
Deactivating Users
You can deactivate users at any time. For example, you may want to deactivate users when
testing new features so that they do not affect the overall performance, and so on.
Deactivated users cannot log on to the Server Admin.
Note: The admin user is predefined in the system, and cannot be deactivated.
To deactivate a user:
1. In the Users pane, right-click the users you want to deactivate, and then click
Deactivate. If the users are currently connected, a dialog box is displayed notifying
that the users' sessions will be terminated.
2. Click Yes to deactivate the selected users. The users appear dimmed in the Users
pane.
To reactivate users:
1. In the Users pane, right-click the users you want to reactivate, and then click
Activate.
You can also deactivate and reactivate users in the User Properties dialog box.
Deleting Users
Administrator users can delete other users at any time, only if they do not have any scheduled
optimization, analysis, or provisioning tasks.
Note: The admin user is predefined in the system, and cannot be deleted.
To delete a user:
 In the Users pane, right-click the user you want to delete, and then select Delete. A
confirmation message is displayed. If the user is the last user in the cluster, it will be
specified in the message. Click Yes to continue. The user is removed from the list of
users in the Users pane.
374
Viewing Statistics
Viewing Statistics
You can view the statistics of selected modeling, collection, and engineering tasks, as well as
the statistics of one or more connected agents.
 Viewing Task Statistics
 Viewing Agent Statistics
Viewing Task Statistics

You can view the duration of a selected task (collection, modeling, engineering) as well as the
amount of the selected task spent in the queue.
To view the task statistics:

1. In the navigation pane, right-click the required task and then click Statistics. The
relevant task statistics window is displayed.
2. By default, the statistics are displayed for each status, for all agents that took part in
executing the tasks. If required, filter the display by selecting or clearing the check
boxes in the left column.
375
Viewing Agent Statistics

You can view the statistics of one or more connected agents, for all agent tasks, or only
selected tasks. Agent statistics represent the utilization of the agent, and enable you to
determine why a task failed.
To view the agent statistics:

 In the navigation pane, right-click the required agent and then click Statistics.
-OR-
Select the agent in the navigation pane and then click in the toolbar.
The Agent statistics dialog box is displayed.
Use the drop-down list at the top-left of the window to select the type of graph to
display. You can select from the following options:
o Utilization Statistics: Displays utilization statistics for the selected agent.
o Utilization Per Agent: Displays utilization statistics for multiple agents. This
option enables you to compare between agents.
376
Viewing Statistics
o Agent Tasks: Displays a Gantt chart for the selected agent. This option is only
available when selecting a single agent.
Note that a separate graph is shown for each agent selected for the comparison.
377
The Model, Analysis, Neighbor List Optimization, and Antenna Sectors

Optimization check boxes each correspond to a task type. Select the relevant check
boxe(s) to display data for that type of task in the graph.
The pane on the bottom left displays the list of agents. Select the check box(es)
corresponding to the agent(s) whose data you want to display.
Note: Multiple agents are only displayed in this list when you select more than one
agent in the navigation pane, whose statistics you wish to view.
By default, the statistics are displayed for all tasks, for all connected agents. If
required, filter the display by selecting or clearing the check boxes in the left column.
378
Managing Antenna Models

The antenna model database contains ready-mode profiles and radiation patterns for
hundreds of commonly used antenna models. This enables you to access a large resource of
profiles in one location within the server, rather than have to collect the profiles you use and
then import them.
The Antenna Models pane displays the details for each of the antenna models included in
the antenna model database, including their tilt and beamwidth.
The Antenna Models pane contains the following fields:
Field Description
Name The name of the antenna model.
Manufacturer The antenna model manufacturer.

Min. Electrical Tilt The minimum electrical tilt of the antenna model.
(deg)
Max. Electrical Tilt The maximum electrical tilt of the antenna model.
(deg)
Nominal Gain (dBi) The average gain of the antenna profiles.
Nominal V The average vertical beamwidth of the antenna profiles.

Beamwidth (deg)
Nominal H The average horizontal beamwidth of the antenna profiles.

Beamwidth (deg)
Support E Tilt Whether the antenna model supports electrical tilt.
Support E Whether the antenna model supports electrical beamwidth.

Beamwidth
379

 To remove a column, right-click the header of the column you want to remove and
380
Viewing Antenna Model Properties

You can view the general properties of antenna model, as well as the RF properties of each
of the antenna profiles associated with the antenna model.
To view the antenna model properties:

1. In the Antenna Models pane, right click the antenna model whose properties you
want to view, and then click Properties. The Antenna Model Properties dialog box
is displayed.
The Antenna Model Properties dialog box contains the following tabs:
o General, which enables you to view general properties of the antenna model,
such as the manufacturer and the tilt range.
o Profiles, which enables you to view the properties of each profile associated with
the antenna model.
2. Click Close to close the Antenna Model Properties dialog box.
381
Viewing General Antenna Model Properties

The General tab enables you to view general properties of the antenna model. For example,
the manufacturer and the tilt range.
The General tab displays the following properties:
Field Description

Tilt range (deg) The tilt range supported by the antenna profiles.
Electrical tilt support Whether the antenna model supports electrical tilt.
Electrical beamwidth support Whether the antenna model supports electrical beamwidth.
Nominal V beamwidth (deg) The average vertical beamwidth of the antenna profiles.
Nominal H beamwidth (deg) The average horizontal beamwidth of the antenna profiles.
Nominal gain (dBi) The average gain of the antenna profiles.

Comments Any textual comments about the antenna, for example, any
updates.
382
Viewing Antenna Model Profile Properties

The Profiles tab enables you to view the properties of each profile associated with the
antenna model. If required, you can also view the horizontal and vertical patterns of a
selected profile.
The Profiles tab displays the following details per selected profile:
Field Description

Tilt range (deg) The tilt range supported by the antenna profiles.
Electrical tilt support Whether the antenna model supports electrical tilt.
Electrical beamwidth support Whether the antenna model supports electrical beamwidth.
Nominal V beamwidth (deg) The average vertical beamwidth of the antenna profiles.
Nominal H beamwidth (deg) The average horizontal beamwidth of the antenna profiles.
Nominal gain (dBi) The average gain of the antenna profiles.

Comments Any textual comments about the antenna, for example, any
updates.
383
To view the horizontal and vertical patterns of a selected profile:

1. Select the profile whose patterns you want to view, and then click Properties.
-OR-
Double-click the profile whose patterns you want to view.
The Antenna Profile dialog box is displayed, showing the horizontal patterns.
2. Click in the pattern area on the left to view the angle and attenuation in the Co-polar
Section area on the right.
384
3. Click the Vertical Pattern tab to display the vertical pattern of the profile.
4. Click Close to close the Antenna Profile dialog box.
385
Importing Antenna Models

You can import previously exported antenna models into the antenna model database. You
can import single files or entire folders. If one or more of the antenna models already exist in
the server, you can select whether to import the new models only, merge the new and
existing model profiles, or import all the models and overwrite the existing models.
To import an antenna model:

1. On the File menu, click Import and then Antenna Models. The Import Antenna
Models dialog box is displayed.
2. Browse to the antenna models you want to import, and then click Open. A progress
bar is displayed while the selected antenna models are being imported.
3. If there are no conflicts, a message is displayed notifying whether the antenna
models were successfully imported.
Click OK.
386
4. If one or more of the antenna models or profiles already exist in the server, a dialog
box is displayed with the following options:
o Import new only: Only the new models will be imported, and all others will be
ignored.
o Merge new and existing: The new models will be added, as well as new profiles
to the existing models.
o Import all and overwrite existing: All existing models will be deleted and
replaced with the new models.
Select the required options, and click OK. A progress bar is displayed while the
requested antenna models are imported, and then a dialog box is displayed notifying
whether the antenna models were successfully imported. The antenna database is
updated with the new antenna models and profiles.
5. Click Reports to display the differences between the existing models and the
imported models.
6. If the selected antenna models already exist in the database, a message is displayed
notifying that no changes were detected. Click OK.
387
Exporting Antenna Models

You can export antenna models from the database so that they can be imported into the
Mentor client, to other servers, or for any other use.
To export the antenna models:

1. In the Antenna Models pane, right-click the antenna models you would like to export.
The Export Antenna Models dialog box is displayed.
2. Browse to the location to which to export the antenna models, and then click Save. A
dialog box is displayed notifying whether the models were successfully exported.
Merging Antenna Models

Administrator users can merge identical antenna models so that each antenna model has
more than one profile, and can use any profile.
To merge antenna models:

1. In the Antenna Models pane, select the antenna models you would like to merge,
and then on the Action menu, click Merge Antenna Models. A confirmation
message is displayed.
2. Click Yes to merge the models.
388

Mentor Server Admin v9.1 User Guide

Uploaded by

Copyright:

Available Formats

Mentor Server Admin v9.1 User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mentor Server Admin v9.1 User Guide

Uploaded by

Copyright:

Available Formats

Mentor Server

The TEOCO Documentation team

Viewing the Map Topology

To display the topology map:

2. To view the topology legend, on the Topology Map toolbar, click .

Administrator View of the Mentor Server Admin Application

Engineer View of the Server Admin Application

Logging On to the Mentor Server

To log on to the Mentor Server:

1. Double-click the Server Admin shortcut on your desktop, or click the

o Click OK. The server group is displayed in the Server area.

o Click OK to save your settings and exit the window.

Note: The password must contain at least 8 characters, including an upper-case

Upgrading the Mentor Server Admin

o Click Yes to download the compatible version. A security warning is displayed.

Viewing and Editing Your User Properties

To view your user properties:

o In the New password field, enter a new password.

Changing Passwords that are About to Expire

To change a password that is about to expire:

2. In the Old password field, enter your current password.

Changing Expired Passwords

To log on to the Mentor Server if your password has expired:

Changing Existing Passwords

To change an existing password:

The User Properties dialog box is displayed.

3. In the New password field, enter a new password.

Setting Preferences - Administrators

To set the status-bar preferences:

Setting Preferences - Engineers

To set the preferences:

The Preferences dialog box is displayed, showing the General tab.

o Running/Failed analysis tasks: Displays the number of running and failed

Logging Off from the Mentor Server

To log off from the Mentor Server:

To log off from the Mentor Server:

New Displays a sub-menu, with the following options:

Import Displays a sub-menu with the following options:

Export Displays a sub-menu with the following options:

Stop Backup Enables you to stop a running backup task.

Print Enables you to print selected notifications.

Preferences Engineer Users: Enables you to define general network preferences, as

User Enables you to view and edit your user properties.

Delete Deletes the selected entity.

Log On Enables you to log on to the Mentor Server.

Exit Exits the Mentor Server Admin application.

History Enables you to view the history of a selected network element.

Clear Filter Clears the previously selected filter.

Topology Enables you to display a graphic display of the network in order to

Find Enables you to search for selected items.

Refresh Refreshes the data in the Agents pane.

Stop Enables you to stop a running task.

Recurrence Enables you to define the recurrence of a selected task.

Deactivate Enables you to deactivate the selected network elements or tasks.

Activate Enables you to activate selected previously-deactivated network elements

Disable Disables notifications for a selected item in the navigation pane.

Enable Enables notifications for a selected item in the navigation pane.

Reports Enables you to display reports for a selected task.

Help Contents Displays this Help file.

TEOCO on Opens the TEOCO Web site.