04-Mentor Server Process Monitoring

Server Process MonitoringLesson Objectives 2 By the end of this lesson you will be able to monitor the automated network data collection and processing By the end of this lesson you w

Privileged and confidential. The information contained in this material is privileged and confidential, and is intended only for the use of the individual to whom it is addressed and others who have been specifically authorized to receive it

If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this material is strictly prohibited If you have received this material in error, please destroy it immediately.Mentor Server

Server Process Monitoring

Server Process Monitoring

Lesson Objectives

2

By the end of this lesson you will be able

to monitor the automated network

data collection and processing

By the end of this lesson you will be able

to monitor the automated network

data collection and processing

Server Process Monitoring

Main Topics

3

Server Process Monitoring 4

Data Processing Workflow

Log & KPI Collection

Log & KPI Collection

Physical Collection

Physical Collection

Log Processing

Log

Engineering Tasks

Engineering Tasks

Call DB

Server Process Monitoring 5

Data Collection

• The server performs automatic collection tasks from several sources, according to the schedule set when defining the NEs

• For every raw data type, there is a recurring task that is connected

to a data device using a channel

• If you have an Ericsson network, you can define a partial collection to

collect only the changes in the switch.

• It can also automatically import the physical configuration data for

its configured NEs from the antennas.txt file or from the planning tools

It then correlates this with the network switch dump data

Server Process Monitoring 6

Data Collection – Scripts

• In some cases, a script is required for the data collection:

(FTP GET, FS copy), built into the server code

executable from the command line (if channel type is SQL, the

script should contain SQL queries)

• Each script is executed by the server with a single argument, which is the file that contains all the parameters configured for this task

Server Process Monitoring 7

set in the advanced parameters

(MAX_TASK_EXECUTION_TIME).

• Failed tasks are highlighted using the ! column.

Server Process Monitoring 8

Collection Task Properties

• General – task details, resources and schedule.

• History – status of all the occurrences of this collection task

• Agents – assigned agents to perform the task

• Advanced – task parameter

settings

The Collection Task Properties includes the following tabs:

Server Process Monitoring 9

Physical Data Collection Task Properties

• General – task details and resources.

• Network Elements – NEs from which to collect the data.

• Schedule – task scheduling.

• History – details or reports of each task occurrence.

• Agents – assigned agents.

• Advanced – task parameter

settings

The Physical Data Collection Task Properties includes the

following tabs:

Server Process Monitoring 10

Tasks Management – Main Operations

• Run a task immediately.

• Deactivate / Activate.

• Edit the task recurrence.

• Enable / Disable notifications.

• View last task failure details.

• View last occurrence details.

• View task properties.

• View statistics (explained next).

• Export / Import task properties.

Following are the common operations relevant to data collection

and data processing tasks:

Server Process Monitoring 11

Task Statistics

You can view the duration of a selected task as well as the

amount of time the selected task spent in the queue

Server Process Monitoring 12

Log Processing Tasks

• 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

• Log processing tasks are created automatically when creating new

network elements

• By default, the log processing tasks are disabled, and they must

be activated in order to parse the log data

The log parsing tasks create positioned calls in Mentor Format

for the model task and for the call database

Server Process Monitoring 13

Log Processing Task Properties

• General – activate the task, as well as schedule the task recurrence.

• History – view the task history.

• Agents – select the agents that will be used.

• Call Filters – define which calls will be added to the call database,

and which call details will be saved

• Advanced – set the system-level parameters.

You can view and edit the properties of a selected log

processing task any time after it has been created:

Server Process Monitoring 14

Model Tasks

• The modeling process takes the relevant data from the collected raw

data, and builds a calculated representation

• A cluster model is a merged model of its NEs over a specific period

• It is created when the user imports the model to the client or when running scheduled analysis and optimization tasks

• By default, the Busy Hours modeling period is created when

defining the network elements, but additional modeling periods for

other times can be created later

A model task defines each modeling period that should

be used for modeling network elements

Server Process Monitoring 15

Model Period Properties

• General – network elements and clusters used for modeling

• Modeling Period – modeling period properties and special

event periods

Server Process Monitoring 16

Model Task Properties

• General – general properties of the modeling task.

• Clusters – clusters whose sector carriers will be included in the

calculation set

• Schedule – time or days the modeling task should be processed.

• Time Filter – filter the hours used in the modeling period.

• Agents – assigned agents.

• History – details of each task occurrence.

• Advanced – parameter settings

for the model task

Server Process Monitoring 17

Call Database Monitoring

• It displays a row for each network element relevant to the call database

The Call Database Monitoring pane enables you to verify whether

the call data was correctly inserted into the call database

Server Process Monitoring 18

Call Database Monitoring (cont.)

• Click Install Call DB.

To install the call database:

To upgrade the call database to the latest Mentor version:

• Prepare an upgrade package containing the scripts required for a

manual upgrade to the latest Mentor version

or

• Automatically upgrade the call database

to the latest Mentor version

If required, you can stop and start

the loading to the database

Server Process Monitoring 19

Call Database Properties

• General – general settings for the call database

• Advanced – parameters for configuring the call database

You can view and edit the call database properties:

Server Process Monitoring 20

NE Call DB Monitoring Properties

• General – general call DB loading properties of the selected NE.

• Files – details of each of the files that are created for uploading the

data into the call database

You can view the properties of the call database loading for all

network elements involved:

Server Process Monitoring 21

Engineering Tasks

• After an analysis, APD, or optimization (scrambling code, neighbor

list, e-tilt and overshooting, antenna sectors) has been run in the client,

it can be scheduled to run as a recurring task in the server

• Each successful task occurrence contains the full environment and

results which later can be imported into the Mentor client

Server Process Monitoring 22

Engineering Tasks – Life Cycle

• Scheduler (or user manually) triggers the task

• Build environment of the cluster, with last X days (configurable) of

model

• Wait for available resources

• Run the optimization / analysis process

• Save the results

• Send notification

Following is the life cycle of recurring calculation tasks:

Server Process Monitoring 23

Notifications

• Notification Examples – login errors, model completion, optimizations

that need to be approved, engineering tasks that completed

successfully, etc

• Notifications are also sent to your own email address, as entered by

the administrator when defining your user properties

• The number of days the notifications are saved and displayed is

defined in the server properties

(MAX_DAYS_OF_NOTIFICATIONS_TO_SAVE)

Using the Notifications pane, you can view all the notification

messages you have received for the servers to which you are

currently connected

Server Process Monitoring 24

Notifications (cont.)

• ! – indicates notifications concerning errors or failed tasks

• Double-click to open and view the notification message

• Notifications about optimization and analysis tasks may include

links to reports and other activities in Mentor

Server Process Monitoring

Lesson Summary – Q&A