Performance measurement reports

Performance measurement reports
		GO

Purpose

This topic describes the characteristics of performance reports.

Report creation and storage

Reports are created according to the defined reporting schedule. Reports are stored for 30 days. After 30 days the oldest report is overwritten.

To ensure that performance data is not lost, export or print reports before the reports are overwritten.

Report validity

Events can occur that affect the validity of a report. If such an event occurs, the event is reported in the report.

The following events are reported for all Lucent CM nodes:

Actions that affect a Lucent CM process. Examples of such actions are shutdowns and restarts.

Loss of a Lucent CM node

Change in the measurement interval

Change in the reporting interval, when the change results in incomplete data for the reporting interval

The following events are reported for Lucent CM U-nodes and A-nodes:

Loss of a connection to an external server

Inability to connect to an external server

Overload condition

The following servers are considered external servers:

FS 3000 (for provisioning interface (OCI-P or OSS) and call control interface (OCI-C or CAP) connection)

FS 5000 (for both WPIF and DB connection)

OMC-P

AnyPath^® Messaging System

LDAP

Lucent Presence Solution

MiLife^® Intelligent Services Gateway

Report outline

Each report includes the following items:

Time and date

Lucent CM node name for node-related data

Lucent CM node name for data segment-related data

labeled measurements

Events that affect validity

Example of a measurement report

An example of a measurement report (Total Report):

Record Begin:200701181700  Record End:200701181713

It's an incomplete period data
RTU counts:50  RTU used(%):20

Node Name:node1
Node Type:Unit Node
General Exception:
App Exception:

General Data
------------------------------------------------------------
Cpu Usage(%):4   Cpu Peak Usage(%):5
JBoss Cpu Usage(%):4  JBoss Cpu Peak Usage(%):4
LVS Cpu Usage(%):0  LVS Cpu Peak Usage(%):0
MySQL Cpu Usage(%):0  MySQL Cpu Peak Usage(%):0
Mem Free(%):79   Mem Peak Free(%):79
Mem Swapping(%):93  Mem Peak Swapping(%):93
JBoss Mem Usage(%):53  JBoss Mem Peak Usage(%):53
LVS Mem Usage(%):1  LVS Mem Peak Usage(%):1
MySQL Mem Usage(%):15  MySQL Mem Peak Usage(%):15
Disk Usage(%):25
Net Internal In(Byte):23808 Net Internal In Loss(Byte):0
Net Internal Out(Byte):128  Net Internal Out Loss(Byte):0
Net External In(Byte):340864 Net External In Loss(Byte):0
Net External Out(Byte):165200 Net External Out Loss(Byte):0
Net Internal In(Pkgs):366  Net Internal Out(Pkgs):1
Net External In(Pkgs):4516  Net External Out(Pkgs):366
DB Read Request:428  DB Write Request:0
A/U Node Data
------------------------------------------------------------
Admin Client API:0  API to admin indicate error :0
User Client API:29  API to user indicate error:0
API FROM FS:1   API to FS indicate error:1
Request to FS interface:1  Request to FS DB interface:4
API from other nodes:0  API to other nodes:0
FS DB reply error:0  Event deliver to client:0
FS Call Intf busy reply:0  Seconds FS Call Intf busy:0
FS Call Intf busy rejections:0
FS user count:6   Unique user session:1
Request to PS SIP interface:0   Request from PS SIP interface:0
Error responses from PS SIP interface:0  Request to PS XCAP interface:0
Error responses from PS XCAP interface:0  User counts with both FS5000 and PS services:0
------------------------------------------------------------
Segment Exception

Call log stored:35  Call log quota used(%):2
Users on the segment:10  FS5000 and PS users on the segment:0
FS5000 and PS PAB entries on the segment:0  Nodes: node1; 
============================================================

		GO
© Lucent Technologies