Professional Documents
Culture Documents
This slide is based on the application style of the client, you can also switch to the
traditional style on preference menu.
Performance function is mainly about two parts, measurement management and result
management, the previous one is how to set all kinds of counters to measure and how to
check the measurement status and so on, the latter is how to get the results and manage
them.
And additional, some performance monitor functions also provided.
To facilitate management, measurement counters are classified into function sets and
function subsets.
Level 1: function set
A function set contains several function subsets that are related to a group
of system functions. Function set is also called measurement set.
Level 2: function subset
A function subset contains a few measurement counters that are related to
a system function. Function subset is also called measurement unit.
Level 3: measurement counter
Only after you set the measurement counters, measured objects, and measurement period
for an NE on M2000, can the NE reports the results, that is, the performance data, to
M2000 when the measurement period comes.
Switch to the status index, if the light is green and the description is active, then the
measure is normal, if not, please check the reason of the fault.
User-defined counters refer to the counters that are defined by adding, subtracting,
multiplying, and dividing system counters. The sources of user-defined counters are as
follows:
Defining the counters on M2000 client.
Defining the counters in the files before importing the counters into M2000.
User-defined counters can be nested to create other user-defined counters. You can add,
modify, and delete user-defined counters when M2000 is running.
Double-click a counter in Available Counter List, or manually enter a counter to edit the
formula. The format of a manually entered counter is as follows:
(Counter 1 + Counter 2) x {100}/(Counter 3 + Counter 4 + Counter 6)
Double-click a counter in Available Counter List, or manually enter a counter to edit the
formula. The format of a manually entered counter is as follows:
(Counter 1 + Counter 2) x {100}/(Counter 3 + Counter 4 + Counter 6)
You can group objects of the same type into an object group. In this way, you can perform
the same operation on all the objects in this object group. M2000 allows you to create,
view, and modify the information about a user-defined object group. This function is used
only for commissioning cells.
You can group objects of the same type into an object group. In this way, you can perform
the same operation on all the objects in this object group. M2000 allows you to create,
view, and modify the information about a user-defined object group. This function is used
only for commissioning cells.
The data of a performance object on M2000 may be different from that on a specific NE. If you find
that some objects are missing, the Diagnose Missing Object function can diagnose missing object
and provide the cause and troubleshooting suggestions to help find missing objects.
Object missing involves the following scenarios: Objects are actually missing.
Data of a specific object fails to be correctly synchronized to M2000 system because the
link between M2000 and the desired NE is faulty.
Synchronization is performed by schedule and time difference exists between two
synchronization tasks. In this case, the information of a specific object may be not
synchronized in time.
The performance object information is converted from configuration object information. If
the information of some configuration objects is incomplete, the data of the specific
performance objects may be missing.
Objects are actually not missing but are regarded as being lost.
If information of an NE's objects are not configured, M2000 displays that no object
information is present.
The performance object information is converted from configuration object information.
The conversion rules are complex, and users may mistakenly take the configuration objects
as the performance objects and think that the performance objects are missing.
Type 3 objects need to be imported manually. If users fail to import the objects, the system
thinks that the objects are missing.
Through M2000 client, you can query the performance data of the OSS server and
subscribe to and query the performance measurement results of the NEs that are set for
measurement on M2000. M2000 allows you to check the integrity and reliability of the
performance measurement results reported by NEs. You can also check whether missing
performance measurement results exist by specifying query conditions.
The number of function subsets can not exceed 10 for one query. In the displayed Result
Query dialog box, the query results are displayed in a table. You can choose to display
them in a line chart or a bar chart.
Before returning the results, M2000 estimates the number of results for this query. If the
estimated number is greater than 500,000, M2000 displays a message asking you to
export the results to your local PC.
Busy Time: Some counters can be queried by using this option. This option becomes
available after some Function subset is selected in the Organization Style area.
Busy hour query supports 60-minute period only.
Buy hour query is not supported in certain time systems.
Busy hour query can be executed only when a busy-hour counter is set to be measured.
Busy hour counters are defined by specific NEs.
The performance query result in line charts or bar charts can be saved as a JPG file.
You can choose to print it as well.
One or multiple rows of data may be lost and not be displayed on GUIs when you perform
result query. In this case, you can use the result loss diagnosis tool to make a diagnosis.
Prerequisites
M2000 service is running properly.
The period for result loss diagnosis is not a summary period.
The period for result loss diagnosis is not a history period.
The objects for result loss diagnosis are not neighboring cells.
The time segment for result loss diagnosis is continuous.
The counters for result loss diagnosis are not busy-hour counters.
The objects for result loss diagnosis are not historical cells.
The result loss diagnosis for the process of reporting 5-minute results is not
supported.
The result loss diagnosis for the process of reporting cBSC results is not supported.
You can also query results and then click Diagnose Result Loss for the queried result.
A large deal of traffic statistics on neighboring cells will be generated and if all this data
get into the database, the database IO may break down and the database space may be
insufficient, so the traffic statistics of neighboring cells are not imported into the database
by default but saved as files. If you want to query the data, import the files into the
database.
The intermediate file storing the performance measurement data of neighboring cells can
be stored for a maximum of 15 days on M2000 server. The performance measurement
data of neighboring cells imported from the performance database can be stored for a
maximum of 3 days.
A maximum of five import tasks can be performed at a time on M2000 server.
Only the data that is collected for a maximum of three days can be imported. Otherwise,
an error message is displayed on the GUI.
The imported files are saved in /export/home/omc/var/pm/NeighborCellPMData.
The Neighboring Cell Data Import window displays all the running neighboring cell
import tasks. Tasks that are newly created are automatically displayed. Tasks that have
been completed are not automatically deleted. When you open the Neighboring Cell
Import Task window again, the Neighboring Cell Data Import window displays only
the running neighboring cell import tasks but does not display the complete tasks.
Performance result can be exported to files which are stored on the PC and then the result
will be deleted from the database to ensure the later result can enter the database
normally.
This is a system task and can not be deleted but suspended.
After the storage period reach the value that are set on the Extend parameters, the
corresponding performance result will be deleted from the database.
You can query the system performance counters preset by M2000 or the existing custom
performance monitoring counters to learn about the monitored objects and the formula of
the counters. If the counters meet the monitoring requirements, you can directly select the
corresponding counters when creating monitoring tasks. Otherwise, you must customize
monitoring counters.
M2000 provides the function of performance counter threshold alarms so that one or
more counters of a measurement object can be monitored during periodical measurements.
When the performance results of NEs meet the triggering conditions, the corresponding
threshold alarms are generated. Performance counter thresholds are categorized into
simple thresholds and combined thresholds.
The principles for generating the corresponding threshold alarms are as follows:
When a counter value of an NE meets the preset alarm severity conditions, the
M2000 generates only the threshold alarms corresponding to the measurement
period and alarm severity. It cannot generate threshold alarms of other periods.
If a threshold alarm of another severity is generated for a counter in the system,
the M2000 clears this alarm and then generates a threshold alarm of the
corresponding severity.
Only when the alarm generation conditions are met for a simple threshold, the
alarm of the current severity is generated, the history alarms are cleared, and
repeated alarms are not sent.
An alarm is generated or cleared for a combined threshold only when the preset
times for triggering or clearing alarms are reached.
If a threshold alarm of the same severity is generated for a counter in the system,
the threshold alarm of this severity is not generated repeatedly.
If no result generated within the period corresponding to the threshold conditions
is reported, no threshold alarm is generated.
A simple threshold of performance counter refers to a threshold set for a single counter.
After a threshold is correlated to a threshold alarm name, a threshold alarm corresponding
to the alarm name is generated when the measurement result of a counter goes beyond
the preset threshold range.
You can set a simple threshold for all objects of one type or some objects of a specific NE.
You are not allowed, however, to set a simple threshold for objects of different object
types. You can set simple thresholds of four alarm severities in one simple threshold task.
If a counter threshold is not correlated to a threshold alarm name, this threshold is
automatically correlated to the default threshold alarm name. The default threshold alarm
name is Performance Threshold Default Alarm, and the default alarm ID is 40925
You can create a new threshold by copy an old one and modify some parameters of it, the
modifications do not affect the old threshold alarms.
A combined counter threshold refers to the threshold defined for the value obtained
through logical or arithmetic operations of multiple counter values. After correlating a
preset threshold to a threshold name, the threshold alarm is generated when the
measurement results of a counter meet the alarm triggering conditions for successive
periods. When the measurement results of a counter meet the alarm clearance conditions
for successive periods, the threshold alarm is automatically cleared.
You can set a combined threshold for all objects of one object type or some objects of a
specific NE. You are not allowed, however, to set a combined threshold for objects of
different types.
If a counter threshold is not correlated to a threshold alarm name, this threshold is
automatically correlated to the default threshold alarm name. The default threshold alarm
name is Performance Threshold Default Alarm, and the default alarm ID is 40925.
This function is to set the time segment for suspending the counter thresholds of each NE.
Thus, the activated counter thresholds are automatically suspended during the specified
time segment. After the counter thresholds of an NE are suspended, the system no longer
performs threshold check on the counter values of this NE.
When the time segment set for suspending the counter thresholds of an NE conflicts with
the time segment set for activating the counter thresholds, the suspending operation takes
priority.
You can set only one time segment for suspending counter thresholds of one NE. If a
suspending time segment is preset for the NE, a new time segment replaces the preset one.
You can manually activate the counter thresholds that are within the suspending time
segment. After a counter threshold is activated, it will not be suspended at the specified
suspending time segment. To suspend this counter threshold again, you must suspend it
manually.
Default status: Specifies the default status so that the default status and the function
subsets in the default state are displayed in the measurement status table.
Default style: Specifies the default status of the measurement status table: expanded or
collapsed.
You can save the settings of some parameter-based system functions by using the
preferences settings.
When you log in to M2000 client next time, M2000 client will be automatically adjusted to
the settings of the last login.
Specific Query: The default interval of querying result.
Synchronize Result: The default interval of synchronization of result.
Result Segment: The default interval of querying result in section time.