10 FNG31 Performance Management

Performance Management
1 Flexi NG Performance Management ©2013 Nokia Solutions and Networks. All rights reserved.
PDF created with pdfFactory Pro trial version www.pdffactory.com

Performance management
Module objectives:
• Learn to use PM management tools
• Be able to create PM measurement jobs

The need for Performance Management
• Enables the operator to monitor key resources in the Network element. This
can be used to (for example):
– Maximize available services to users
– Optimize the usage of the resources
– Locate possible configuration errors before they affect service
– Locate potential HW defects (for example network interface errors that
may indicate a failing interface card)
• Performance management can also be used to collect data over a longer

term for trend analysis or analysis of element load under certain well known
scenarios (for example, a past ”free call weekend”)

The FlexiPlatform Performance Management System
• The main tasks of the FlexiPlatform Performance Management System

(SS_PM9) are:
– To manage Measurement Jobs
– To manage Object Lists
– To manage Threshold Jobs
– To schedule Measurement Jobs
– To collect measurement result files
– To raise or clear appropriate alarms based on set thresholds and monitored
attributes
– To format the measurement result files according to the OMeS 2.0 format

Performance Management Process
• The process for performing Performance Management can be summarized in the following
three steps:
1. The data to be collected must be defined by creating a measurement job.

• Periodic or continuous collection?
• What is our measurement type? (i.e., which attributes or counters are to be monitored?)
• Single object or multiple objects to gather the measurements from?
(Nodes, Services, etc.)
2. The PM9 collects, processes and stores the data in the Network Element (in file system
and/or database)
3. The data is analyzed in the NE or in OSS
• The definition and scheduling of the performance measurement jobs are done with the SCLI

Managing the PM System
• The PM System can be managed from

– SCLI
– NE3S Interface
• SCLI is the recommended tool for PM related tasks
• NE3S provides limited support
Shell:
Shell: WebUI
WebUI OSS
SCLI
SCLI //
fspm9cli
fspm9cli
ssh HTTPS SNMP
J2SE/
J2SE/ NE3S
NE3S
Directory
Directory Servlet
Servlet Engine
Engine Adapter
Adapter
PM
PM Server
Server
NE

Retrieving and Analysing Collected Data
Is
Is used
used to:
to: CLI
-- Delete
Delete old
old result
result files
files Tool Retrieval
Retrieval of
of
-- Export result files
Export result files result
result files
files
OSS
Directory
Directory FTP-server
FTP-server
/var/opt/nokiasiemens/SS_PM9/
storage/results
-- Schedules
Schedules measurements
measurements
PM
PM Server
Server -- Gathers
Gathers data
data
-- Transfers
Transfers data
data to
to the
the PM
PM Server
Server
Data
Data Provider
Provider
NE

Flexi NG performance management
• Provides measurement information of Flexi NG performance

• Measurements can be created with SCLI (fsclish)
• Examples of Flexi NG traffic and service performance data:
– the number of PDP context / EPC session activations
– the number of Radius authentication queries
– the number of failed sessions
– traffic volumes
• Examples of resource performance data:
– CPU average
– minimum and maximum usage
– received and transmitted Ethernet packets and errors

Defining measurement jobs
• Objects of the measurements

– From which objects is the PM data collected
– Object list
• Measurement types
– What performance indicators are collected
• Schedule
– Timeframe for the collection of PM data
– Continuous or periodical
– A continuous measurement has only one recording interval.
– A periodical measurement may contain several recording intervals, and for each, you can
define a specific granularity period.

Object lists
•Object lists consist of:

– Object list name
– Measurement Type (for example “NG Load”)
– Actual list of objects to be monitored (for example, all the AS)
•The predefined measurement type defines:
• What type of objects are monitored (Nodes, processes, databases etc.)
• What Performance Indicators (PIs) within these objects are measured (free RAM, number of threads,
number of database tables etc.)
• The measurement types and OMES codes are listed in the configuration files located in
/var/opt/nokiasiemens/SS_PM9/plans
NG20_cdr.xml NG20_ip.xml NG20_up.xml

NG20_diameter.xml NG20_ippools.xml PMFlexiCpuPlan.xml
NG20_gre_tunnel.xml NG20_pmip.xml PMFlexiMeasPlan.xml
NG20_gtpc.xml NG20_qos_dl_drop.xml PMFlexiNetQosPlan.xml
NG20_gtpcv2.xml NG20_radius.xml PMFlexiNetstatPlan.xml
NG20_gtpp.xml NG20_session_cdr.xml PMFlexiRUCpuMemPlan.xml
NG20_gtpu.xml NG20_session_profiles.xml PMFlexiStoragePlan.xml

Defining object lists
• To create a new object list with the SCLI

add stats obj-list name CPUList omes 3004 object NODE-AS7-0//GTPC-
ALL/CREATE_SESSION_RESPONSE_ALL NODE-AS7-1//GTPC-
ALL/CREATE_SESSION_RESPONSE_ALL
• To view existing object lists
show stats obj-list all

Measurement jobs
• Measurement jobs define which KPIs on what object lists should be monitored,
as well as how and when should this occur
• A measurement job consists of
– Job name
– Measurement type
– Status
– Schedule
– Object list
• To create a measurement job, the object list that defines what objects are
being measured during this job must exist (unless “all objects” is selected)

Scheduling principles for measurement jobs

Defining measurement jobs
• To define a new measurement job with the SCLI, for example

add stats m-job name GTPC-Report omes 3004 start 2009.05.01-00:00:00
stop 2009.05.30-23:59:59 granularity 3600
• The full syntax is
add stats m-job name <name> omes <omesid> granularity
<GranularityPeriod> start <startTime> [stop <stopTime>] [continuous|
[object-listid <ObjectListID>]
–For granularity the possible values are 300, 900, 1800 and 3600 seconds
–A new job ID is automatically allocated
• To start the measurement job
set stats m-job id <jobID> enabled

Querying measurement jobs
• To check the current measurement jobs with the SCLI

show stats m-job id <jobID>
id Name OmesID JobState ObjectListID StartTime StopTime GranPeriod Cont Deact Periods
-- ---- ------ -------- ------------ --------- -------- ---------- ----
11 CPUJob2 2002 activated [ALL] 2009.11.14 13:55:00 Non-stop 300 yes 0 0

Threshold jobs
• Threshold management will allow the users of performance management (PM)

to place boundary values on each and/or every performance indicator (PI) in
such a way that if the boundaries are reached, an alarm can be raised to
indicate it
• The difference to standard measurement jobs is that each PI can be set with
threshold values to define when an alarm or log event should be created

Threshold values (1/2)
• PI name
– The name of the PI (performance indicator) measurement attribute. PIs are specific to the
measurement type.
• Min
– Minimum threshold value. If the value of a PI consecutively reaches the minimum value as many
times as defined in the column Occurrences, an alarm is raised.
• Clearing min
– Clearing value for a minimum threshold value. If the value of a PI consecutively reaches this value as
many times as defined in the column Occurrences, an alarm is cleared.
• Max
– Maximum threshold value. If the value of a PI consecutively reaches the maximum value as many
times as defined in the column Occurrences, an alarm is raised.
• Clearing max
– Clearing value for a maximum threshold value. If the value of a PI consecutively reaches this value
as many times as defined in the column Occurrences, an alarm is cleared.

Threshold values (2/2)
• Occurrences
– The number of occurrences of an event that effects the raising or clearing of an alarm.
These events can also occur at the end of a sampling period defined in the measurement
job.
– An example of this event is when CPU consumption exceeds the maximum threshold
value set. In this case, an alarm would be raised if the set maximum threshold value is
reached consecutively for Occurrence number of samples.
• Running average
– Instead of the plain measured values, the running average of them can also be used for
raising and clearing an alarm. With the running average, reaching the alarm thresholds is
based on the average of the last n samples. The number of samples used for calculating
the running average can be defined by the user.
• Severity
– The severity level of alarm that is sent to log files or alarm system. The severity level can
be warning,minor, major, or critical.

The threshold attributes
CPU usage % Alarm is

raised
Max Threshold Value 90
Max Clearing Value 80
70
60
50
Alarm is
40
cleared
Alarm is
raised
Min Clearing Value 30
Min Threshold Value 20
10
0 Time
9:00 9:05 9:10 9:15 9:20 9:25 9:30 9:35 9:40 9:45 9:50 9:55
Note! Occurrence has been set

to 3 in this example Granularity
period

Threshold alarms
• When the maximum threshold value is exceeded, the system raises the alarm
70074 MAXIMUM THRESHOLD HAS BEEN CROSSED.
• When the minimum threshold is exceeded, the alarm 70197 MINIMUM
THRESHOLD HAS BEEN CROSSED is raised.

Creating threshold jobs
• To create a new threshold job with the SCLI, for example

add stats t-job name NetTJob omes 2004 start 2009.12.01-00:00:00 stop
2009.12.30-23:59:59 samples 5
–Running average is defined with the ”samples” attribute
• To add the threshold values to an existing job
add stats t-values id 100000001 attid 0003 severity major occ 3 min
20 min-clearing 30 max 100 max-clearing 90
• To start the threshold job
set stats t-job id <jobID> enabled
• To check the existing threshold jobs
show stats t-job all

Result files
• Each measurement job running on a network element (NE) produces

scheduled measurement reports at the end of each granularity period
• The information in the reports is defined by the system operator, and it
consists of:
– an identification of the involved measurement type and the measured network resource(s)
or observed objects, for example, AS7-0
– a time stamp, referring to the start of the granularity period
– interval, referring to the length of the granularity period
– for each measurement type, the result value(s)

Open Measurement Standard
• The performance measurement data is in Open Measurement Standard

(OMeS) file format. The OMeS files can be used, for example, for passing data
between the NEs and the operations support system (OSS).
– Based on XML schema
• NetAct fetches the measurement data from the NE using sFTP
• The measurement result file is stored locally in the network element, and the
performance management notifies the OSS of the new file
• After OSS has fetched the file, it deletes the result file

PM9 measurement results
• By default, the result files are stored to:

– /var/opt/nokiasiemens/SS_PM9/storage/results
• The recent results be accessed by using the PM (pseudo) file system
• By default, the mount point for pmfs is /cdafs/pmfs
• The list of the collected result files can be found by using the SCLI command
- root@CLA-0 [FP] > show stats data results
- [MX] id - Measurement job ID
- [MX] start - The start time of the desired period
- [MX] stop - The stop time of the desired period

Result file example
• Example:
A20050407.1030+0000-20090407.1035+0000_XYZ_NSN_1.0.xml
• The name of the measurement result file indicates that
– it contains the results of one NE
– the granularity period started on April 7, 2009, at 10:30 local time
– the granularity period ended at 10:35 local time, with a time diff of 0 to the UTC
– the file is produced by the NE with the baseId XYZ_NSN_1.0.

OMeS 2.0 result file format
• Result files are XML formatted:

<?xml version="1.0"?>
<OMeS>
<PMSetup startTime="2008-11-14T13:55:00.000+02:00" interval="5">
<PMMOResult>
<MO>
<DN>NODE-CLA-0//CPU-0</DN>
</MO>
<PMTarget measurementType="CpuUsage">
<m02002c0003>0</m02002c0003>
<m02002c0004>0.566667</m02002c0004>
<m02002c0005>0.239326</m02002c0005>
</PMTarget>
</PMMOResult>
</PMSetup>
</OMeS>

Checking the result snapshot file
• In the specific pmfs file system there is a snapshot file that contains the current
counter value for any specified measurement
• For example,
– cd /cdafs/pmfs/3004_GTP_C_v1_create_response_sent/NODE-AS7-1/GTPC-
SUM/CREATE_RESPONSES_SENT-SUM]
– more snapshot.txt
Number of sent Create PDP Context responses by cause
code(m3004c0001) : 19

10 FNG31 Performance Management

Uploaded by

Document Information

Original Title

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

10 FNG31 Performance Management

Uploaded by

Copyright:

Available Formats

Performance Management

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

• Performance management can also be used to collect data over a longer

PDF created with pdfFactory Pro trial version www.pdffactory.com

• The main tasks of the FlexiPlatform Performance Management System

PDF created with pdfFactory Pro trial version www.pdffactory.com

1. The data to be collected must be defined by creating a measurement job.

PDF created with pdfFactory Pro trial version www.pdffactory.com

• The PM System can be managed from

ssh HTTPS SNMP

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

• Provides measurement information of Flexi NG performance

PDF created with pdfFactory Pro trial version www.pdffactory.com

• Objects of the measurements

PDF created with pdfFactory Pro trial version www.pdffactory.com

•Object lists consist of:

NG20_cdr.xml NG20_ip.xml NG20_up.xml

PDF created with pdfFactory Pro trial version www.pdffactory.com

• To create a new object list with the SCLI

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

• To define a new measurement job with the SCLI, for example

PDF created with pdfFactory Pro trial version www.pdffactory.com

• To check the current measurement jobs with the SCLI

PDF created with pdfFactory Pro trial version www.pdffactory.com

• Threshold management will allow the users of performance management (PM)

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

CPU usage % Alarm is

Max Threshold Value 90

Max Clearing Value 80

Min Threshold Value 20

Note! Occurrence has been set

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

• To create a new threshold job with the SCLI, for example

PDF created with pdfFactory Pro trial version www.pdffactory.com

• Each measurement job running on a network element (NE) produces

PDF created with pdfFactory Pro trial version www.pdffactory.com

• The performance measurement data is in Open Measurement Standard

PDF created with pdfFactory Pro trial version www.pdffactory.com

• By default, the result files are stored to:

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

• Result files are XML formatted:

PDF created with pdfFactory Pro trial version www.pdffactory.com

PDF created with pdfFactory Pro trial version www.pdffactory.com

You might also like