Académique Documents
Professionnel Documents
Culture Documents
Operation Guide
Issue 03 (2008-04-10)
9-1
System Structure
The performance management system of the GGSN9811 consists of:
l
Figure 9-1 shows the structure of performance management system of the GGSN9811.
Figure 9-1 Structure of the performance management system of the GGSN9811
LAN
Local LMT
M2000
Server
M2000
Client
Modem
GGSN/BAM
PSTN
Modem
Remote LMT
9-2
Issue 03 (2008-04-10)
GGSN9811/BAM
The GGSN9811 is a functional entity in the general packet radio service (GPRS)/Universal
mobile telecommunications system (UMTS) network. The BAM is the module of the operation
and maintenance (O&M) system of the GGSN9811. The BAM reports the performance
measurement statistics of the GGSN9811 to the M2000.
LMT
The LMT is connected to the GGSN9811 through the intranet, Internet, or modem. You can
locally or remotely operate and maintain the GGSN9811 through the LMT.
M2000
The M2000 is connected to the GGSN9811 through the BAM. The M2000 is an integrated O&M
system developed for the UMTS by Huawei. The NEs including the GGSN9811 in the UMTS
can be managed through the M2000.
The M2000 provides the following performance management functions through the graphic user
interface (GUI):
l
9-3
The M2000 then FTP obtains the notice. At the same time, the M2000 analyzes the result. If a
performance specification exceeds the threshold, the system generates a performance threshold
alarm.
Figure 9-2 shows the performance measurement function of the GGSN9811/M2000.
Figure 9-2 Performance measurement function
Activate a default performance
measurement task
M2000
Query performance
measurement result
M2000
Threshold alarm/Result
subscription
M2000
Report performance
measurement result
GGSN9811
Save performance
measurement result
M2000
Analyzing performance
measurement result
M2000
Subscribe notice to
GGSN9811
M2000
Obtain measurement
result by the FTP
M200
M2000
0
Measurement Objects
A measurement object defines what is measured. The object is a physical or logic entity, or a
combination of entities.
Table 9-1 lists the measurement objects of the GGSN9811. These are the level-1 nodes in the
structure of performance measurement system.
The attribute of the measurement object defines what to be measured. The measurement object
may be physical items such as boards, or logic items. The measurement objects and measurement
items are related.
A measurement object defines a type. The object may involve many instances. In a specific
measurement task, the attribute of the object is the specific instance. If the average CPU usage
of boards is measured, the object is the boards. The boards of the GGSN9811 are an instance of
the measurement object. When the measurement task is created, the boards must be specified.
9-4
Issue 03 (2008-04-10)
The default measurement objects are boards and subracks of the GGSN9811.
Table 9-1 Possible measurement objects in the GGSN9811 system
M2000 Object ID
BAM Object ID
Object Name
134218178
CG IP
134218179
IMSI
134218180
APN
134218181
Board
134218182
GGSN function
134218183
HPLMN
134218184
SGSN IP
Measurement Sets
The measurement set is the category of the measurement units.
The measurement set is a level-2 node in the structure of the performance measurement system
of the GGSN9811.
There is a one-to-many relation between measurement sets and measurement units. A
measurement set contains multiple measurement units. A measurement unit can belong to only
one measurement set.
Measurement Units
The measurement unit is the category of the measurement items.
The measurement unit is a level-3 node in the structure of the performance measurement system
of the GGSN9811.
There is a one-to-many relation between measurement units and measurement items. A
measurement unit contains multiple measurement items. A measurement item can belong to only
one measurement unit.
Measurement Items
The basic unit of performance measurement is called measurement item, such as the average
number of activated PDP contexts, peak throughput of the Gn interface, average CPU usage,
and number of successfully-created call detail records (CDRs).
The measurement item is a level-4 node in the structure of the performance measurement system
of the GGSN9811.
Measurement Thresholds
When the value of a measurement item is higher or lower than the critical value, the system
generates alarms. The critical value here is the measurement threshold. You can set the threshold.
Issue 03 (2008-04-10)
9-5
Measurement Results
When a measurement period is over, the GGSN9811 generates a result file for each default task.
If the file generation succeeds, the GGSN9811 sends a notice indicating that the measurement
result file is ready to the M2000 that subscribes to the notice. If the generation of the file fails,
the GGSN9811 sends a notice indicating that the measurement result file fails to the M2000.
After receiving the notice indicating the measurement result file is ready, the M2000 sends an
order to upload measurement result file to the GGSN9811. The GGSN9811 FTP uploads the
file to the directory specified by the M2000.
When the upload of the result file is complete, the GGSN9811 sends a notice indicating that the
file transfer is over to the M2000. If the upload fails, the GGSN9811 sends a notice indicating
the file transfer fails to the M2000.
Level 1: measurement set, containing several measurement units related to certain functions
of the system
Level 3: measurement item, existing in the tree structure system of "measurement object
class->measurement set->measurement unit->measurement item"
Table 9-2 lists the relations among measurement sets, measurement units, and measurement
items.
9-6
Issue 03 (2008-04-10)
Table 9-2 Relations among measurement sets, measurement units, and measurement items
Measurement Set
Measurement Unit
Measurement Item
A measurement set contains one or multiple measurement units. A measurement unit contains
one or multiple measurement items.
For details on measurement sets, measurement units, and measurement items of the
GGSN9811, see the appendix of this document.
9-7
This part describes the measurement set and the measurement unit of the Layer 2 Tunneling
Protocol (L2TP) control plane performance measurement.
9.2.9 Forwarding Performance Measurement (Specified APN)
This part describes the measurement set and the measurement unit of the forwarding performance
measurement (specified APN).
9.2.10 DHCP Performance Measurement
This part describes the measurement set and the measurement unit of the Dynamic Host
Configuration Protocol (DHCP) performance measurement.
9.2.11 System Resource Measurement
This part describes the measurement set and the measurement unit of the system resource
measurement.
9.2.12 MIP FA Performance Measurement
This part describes the measurement set and the measurement unit of the Mobile Internet
Protocol (MIP) foreign agent (FA) performance measurement.
9.2.13 Signaling Message Error Cause Measurement
This part describes the measurement set and measurement unit of the signaling message error
cause measurement.
9.2.14 Traffic-Class-Based Basic Session Measurement
This part describes the measurement set and the measurement unit of the traffic-class-based
basic session measurement.
9.2.15 Traffic-Class-Based Forwarding Performance Measurement
This part describes the measurement set and the measurement unit of the traffic-class-based
forwarding performance measurement.
9.2.16 User Number Measurement
This part describes the measurement set and the measurement unit of the user number
measurement.
9.2.17 Traffic-Class-Based APN Session Performance Measurement
This part describes the measurement set and the measurement unit of the traffic-class-based
access point name (APN) session performance measurement.
9.2.18 IMS Basic Session Service Measurement
This part describes the measurement set and the measurement unit of the IP multimedia
subsystem (IMS) basic session service measurement.
9.2.19 IMS Session Performance Measurement
This part describes the measurement set and the measurement unit of the IP multimedia
subsystem (IMS) session performance measurement.
9.2.20 Layer 7 Parse Performance Measurement
This part describes the measurement set and the measurement unit of the layer 7 parse
performance measurement.
9.2.21 Gy Interface Performance Measurement
This part describes the measurement set and the measurement unit of the Gy interface
performance measurement.
9.2.22 Prepaid Service Measurement
This part describes the measurement set and the measurement unit of the prepaid service
measurement.
9-8
Issue 03 (2008-04-10)
9.2.1 Overview
This part describes the concepts of the measurement set and measurement unit.
Table 9-3 lists 29 measurement sets and 31 measurement units of the GGSN9811.
Table 9-3 Measurement sets and measurement units
Measurement Set
Measurement Unit
G-CDR measurement
G-CDR measurement
Issue 03 (2008-04-10)
9-9
Measurement Set
Measurement Unit
NOTE
The following sections are categorized in terms of functions. Thus, one section may contain different
measurement sets. The measurement sets are divided in terms of functions and objects.
Different software versions may provide different measurement sets and measurement units.
Session activation
Session deactivation
Session modification
Number of requests
Number of successes
Number of users
Table 9-4 lists the measurement units relating to the session management.
9-10
Issue 03 (2008-04-10)
Measurement Unit
Description
Providing session
performance measurement
relating to a specified 3G
APN
Providing session
performance measurement
relating to a specified 2G
APN
Providing status
measurement relating to a
specified APN
Providing session
measurement relating to a
specified HPLMN
Providing session
measurement relating to a
specified GGSN
Table 9-5 lists the measurement unit relating to the forwarding performance management.
Issue 03 (2008-04-10)
9-11
Measurement Unit
Description
Forwarding performance
measurement
Forwarding performance
measurement
Number of forwarding
packets, throughput,
forwarding success rate of
the Gn and Gi interfaces
Measurement Unit
Description
G-CDR measurement
G-CDR measurement
Ga interface performance
measurement
Ga interface performance
measurement
Ga interface performance
measurement (specified CG)
9-12
Ga interface performance
measurement (specified CG)
Number of connection
interruptions between the
GGSN and the CG
CG redirections
Based on different IP
addresses of the CGs,
counting:
l
Number of connection
interruptions between the
GGSN and the CG
CG redirections
Issue 03 (2008-04-10)
Measurement Set
Measurement Unit
Description
G-CDR measurement
(specified IMSI)
Measurement Unit
Description
AAA performance
measurement
AAA performance
measurement
AAA performance
measurement (specified
APN)
AAA performance
measurement (specified
APN)
Number of authentication
request successes
Number of charging
request successes
Number of authentication
request attempts
Number of charging
request attempts
Number of authentication
request successes
Number of charging
request successes
Number of authentication
request attempts
Number of charging
request attempts
9-13
Table 9-8 lists the measurement unit relating to the intelligent service performance
measurement.
Table 9-8 Measurement unit relating to the intelligent service performance measurement
Measurement Set
Measurement Unit
Description
Intelligent service
performance measurement
Intelligent service
performance measurement
Table 9-9 lists the measurement unit relating to the PPP control plane performance.
Table 9-9 Measurement unit relating to the PPP control plane performance
9-14
Measurement Set
Measurement Unit
Description
IPCP negotiation
successes
Issue 03 (2008-04-10)
Measurement Unit
Description
Number of established
L2TP tunnels
Number of established
L2TP sessions
Issue 03 (2008-04-10)
Measurement Set
Measurement Unit
Description
Forwarding performance
measurement (specified
APN)
Forwarding performance
measurement (specified
APN)
9-15
Measurement Unit
Description
DHCP performance
measurement
DHCP performance
measurement
Number of received
DHCP address allocation
requests
Measurement Unit
Description
System resource
measurement
System resource
measurement
9-16
Issue 03 (2008-04-10)
Measurement Unit
Description
MIP FA performance
measurement
MIP FA performance
measurement
Measurement Unit
Description
Issue 03 (2008-04-10)
Measurement Set
Measurement Unit
Description
Traffic-class-based basic
session measurement
Traffic-class-based basic
session measurement
9-17
Measurement Unit
Description
Traffic-class-based
forwarding performance
measurement
Traffic-class-based
forwarding performance
measurement
Measurement Unit
Description
9-18
Issue 03 (2008-04-10)
Table 9-19 Measurement unit relating to the traffic-class-based APN session performance
measurement
Measurement Set
Measurement Unit
Description
Traffic-class-based APN
session performance
measurement
Traffic-class-based APN
session performance
measurement
Measurement Unit
Description
Issue 03 (2008-04-10)
Measurement Set
Measurement Unit
Description
9-19
Measurement Unit
Description
Layer 7 resolution
performance measurement
Layer 7 resolution
performance measurement
Packet throughput
Measurement Unit
Description
Gy interface performance
measurement
Gy interface performance
measurement
9-20
Issue 03 (2008-04-10)
Measurement Unit
Description
Measurement Unit
Description
9-21
Context
ADD MEASOBJ is used to add a measurement object. The measurement object is a certain
physical or logic resource entity in performance management. The objects added on other
management terminals such as the local maintenance terminal (LMT) or network elements (NEs)
are not displayed on the interface of the M2000. The objects added on the M2000 are suitable
only for the measurement objects of which the period is longer than 30 minutes.
If you add an existing object, a success message is returned.
Procedure
l
Context
RMV MEASOBJ is used to remove a measurement object. The objects measured by the M2000
must be removed from the interface of the M2000.
l
If the value of the object class is not specified, all measured object class instances that can
be configured are removed.
If the value of the object instance is not specified, all objects of this class are removed.
Example
Remove a measurement object. The object class is APN. The object instance is ISP.com.
RMV MEASOBJ: MOC = "APN", MOI = "ISP.com";
l
9-22
Issue 03 (2008-04-10)
Context
LST MEASOBJ is used to query a measurement object.
In an object class, the object instances that are collecting data is listed.
Example
Query a measurement object. The object class is APN.
LST MEASOBJ: MOC=APN;
The results are as follows:
+++
GGSN HUAWEI
2006-08-31 16:14:23 O&M
% RETCODE = 0 Execution succeeded
MOI
END
9-23
Context
VRF DEFMEAS is used to check whether the items and objects in the measurement task file
are valid and whether the active task file and the standby task file are consistent.
The file status in the measurement result is as follows:
l
OK
The file is normal.
CORRUPT
The file is abnormal.
NONEXIST
The file does not exist.
The active task file is the file that is activated. When the standby task file is activated, it becomes
the active task file.
Example
Verify the task file.
VRF DEFMEAS:; +++
GGSN HUAWEI
2006-08-24 01:02:40 O&M
DEFMEAS:;%% RETCODE = 0 Execution succeeded
#19 %%VRF
OK
OK The standby file
TRUE (Number of results = 3)
---END
Context
ACT SDEFMEAS is used to activate the standby task file.
The validity of the task file is checked when the standby task file is activated.
The standby task file becomes the active task file after activation. The original active task file
becomes the standby task file.
When the activation succeeds, the new task file takes effect immediately. The result file of the
current period is generated based on the new task file.
Example
Activate the standby task file.
ACT SDEFMEAS:;
Issue 03 (2008-04-10)
Context
DLD DEFMEAS is used to download the task file from the File Transfer Protocol (FTP) server
to the GGSN.
The active task file and standby task file are saved on the GGSN. The active task file is used
currently. The downloaded task file replaces the standby task file.
After the task file is downloaded to the master main control board, the file on the slave main
control board is synchronized automatically.
The downloaded task file replaces the standby task file.
Example
Download the task file.
l
Postrequisite
Uploading Task Files
This part describes how to uploading task files.
Context
ULD DEFMEAS is used to upload the task file from the GGSN to the File Transfer Protocol
(FTP) server.
Before you run this command, you must check whether there is a file with the same name as the
file to be uploaded to the FTP server.
Example
Upload the task file.
l
9-25
Context
LST DEFMEAS is used to check whether the active and standby task files exist on the
GGSN and to query the time when the files are created.
Example
Query the task file.
LST DEFMEAS: ; +++
GGSN HUAWEI
2006-08-24 23:59:59 O&M
DEFMEAS: ";%% RETCODE = 0 Execution succeeded
#1000 %% LST
20060526.2230
20060526.2230 (Number
----END
Context
LST MEASRST is used to upload the measurement result file.
When a measurement period is over, the GGSN generates a measurement result file for each
default measurement task.
You can query the generated result file with LST MEASRST.
Example
Upload the measurement result file.
9-26
Issue 03 (2008-04-10)
Context
RMV MEASRST is used to remove the specified or all measurement result files from the
GGSN.
l
You can query the generated result file with LST MEASRST.
If the file name is not specified, all result files are removed.
Example
Remove a measurement result file. The file name is A20050526.2200+0800-2230+0800_EMSNORMAL.mrf.
RMV MEASRST: FN = "A20050526.2200+0800-2230+0800_EMSNORMAL.mrf";
Remove all the measurement result files.
RMV MEASRST:;
Context
LST MEASRST is used to query the measurement result file.
The information of the measurement result file includes the time when the measurement result
is generated.
Example
Query the measurement result file.
LST MEASRST:; +++
GGSN HUAWEI
2006-08-24 19:18:12 O&M
MEASRST: ;%% RETCODE = 0 Execution succeeded
#1000 %% LST
Issue 03 (2008-04-10)
9-27
Generated Time
A20060824.1030+0800-1100+0800_EMS-NORMAL.mrf
A20060824.1130+0800-1200+0800_EMS-NORMAL.mrf
of results = 2)
---
20060824.1106
20060824.1206 (Number
END
9.4.1 Overview
This part describes the functions and the usage of the performance browser tool.
With the performance browser tool, you can browse the performance measurement results that
are saved in the network element (NE).
The performance browser tool provides the File Transfer Protocol (FTP) download function.
The local maintenance terminal (LMT) can be connected to the FTP server for transmitting the
performance data and files.
Issue 03 (2008-04-10)
When the performance browse tool is started, you must configure the parameters relating to the
File Transfer Protocol (FTP) server of the NE. Then, you can download, query, or browse the
measurement results.
Choose System > Net Configure in the menu, and Net Configure dialog box is displayed. You
can set the FTP download parameters. Refer to Figure 9-3.
Figure 9-3 Net Configure dialog box
Table 9-26 lists the fields and description in the Net Configure dialog box.
Table 9-26 Fields and description in the Net Configure dialog box
Issue 03 (2008-04-10)
Field
Description
NE name
FTP config
IP address
User
9-29
Field
Description
Password
Local result
Server path
Target file
9-30
Address list
Add
Modify
Delete
Issue 03 (2008-04-10)
When the network element (NE) configuration is complete, choose System > Download
Measurement Results . The Download Measurement Results dialog box is displayed. Refer
to Figure 9-4.
Figure 9-4 Download Measurement Results dialog box
The FTP server in the address list in the Net Configure window is displayed. Double-click the
FTP server name to connect to the server. When the connection is complete, in FTP Server
Directory in Download Measurement Results, all measurement result files with the extension
name as mrf are listed. The local files are listed in Local Directory.
Select all measurement result files. You can choose multiple files by pressing Shift. Then, click
Download. The progress bar is displayed. The downloading process may last two to five minutes
when multiple files are downloaded.
When the process is complete, open the directory tree data\176\60 in Local Directory.
Directories are generated based on dates. For example, the measurement result files with
measurement period of 60 minutes on October 18, 2006 are saved in data\176\60\20061018.
9-31
9-32
Issue 03 (2008-04-10)
Table 9-27 Fields and description in the Query Performance Results window
Tab
Field
Description
Counters information
Measurement sets
Measurement units
Available counters
Selected counters
Time information
Query mode
Date/time
When the counters and time are selected, click Query, and then the progress bar is displayed.
When the progress bar is complete, the data of the specified counters in the specified time is
displayed in time sequence.
Measurement item
Issue 03 (2008-04-10)
9-33
The performance browser tool uses this file to explain the measurement result file.
You can know about the measurement items and objects provided by the NE through the
measurement description file.
Choose System > Browse Description File. The Browse Description File dialog box is
displayed. Refer to Figure 9-7.
Figure 9-7 Browse Description File dialog box
9-34
Issue 03 (2008-04-10)
Context
To create a customized template, perform the following steps:
Procedure
Step 1 In the Browse Description File window of the navigation tree, you can open the Add dialog
box in two ways:
l
Step 2 Click the measurement objects, sets, units, or items in Available Counters in the Add dialog
box displayed. Then, add them to Selected Counters by clicking
Step 3 Click Save Template. The Information dialog box is displayed. Type the template name.
Step 4 Click OK.
----End
Context
To modify a customized template, perform the following steps:
Procedure
Step 1 In the Browse Description File window of the navigation tree, you can open the Modify dialog
box in two ways:
l
Right-click the customized template to be modified. Choose Modify in the shortcut menu.
Step 2 Choose the measurement sets, units, or items of the same measurement object in the Modify
dialog box displayed. Click Save Template.
Step 3 Click OK in the Confirm dialog box displayed.
----End
Postrequisite
NOTE
You cannot modify the measurement object when modifying the customized template.
Issue 03 (2008-04-10)
9-35
Context
To delete a template, perform the following steps:
Procedure
Step 1 In the Browse Description File window of the navigation tree, you can open the Delete dialog
box in two ways:
l
Context
To query the created templates, perform the following steps:
Procedure
Step 1 In the Browse Description File window of the navigation tree, you can open the Query
Performance Results dialog box in two ways:
l
Press Enter.
Step 2 Set Query Mode and Date/Time in the Query Performance Results dialog box displayed.
Step 3 Click Query to query the items in the template.
----End
Issue 03 (2008-04-10)
Comparative analysis on the data in the same period of measurement items of multiple
measurement units
This analysis can be used to locate the fault in a complex process.
For example, by comparing the measurement item of the authentication and activation
process errors, you can locate the fault of activation failures due to authentication failures.
Issue 03 (2008-04-10)
GGSN Item
SGSN Item
Analytic Description
9-37
GGSN Item
SGSN Item
Analytic Description
9-38
GGSN Item
SGSN Item
Analytic Description
2G MS activate session
requests + 2G network
activate session requests +
3G MS activate session
requests + 3G network
activate session requests
Issue 03 (2008-04-10)
Issue 03 (2008-04-10)
GGSN Item
SGSN Item
Analytic Description
2G MS activate session
succeed + 2G network
activate session succeed + 3G
MS activate session succeed
+ 3G network activate
session succeed
Average 3G activation
session users + Average 2G
activation session users
Maximum simultaneously
activated PDP contexts
Maximum 3G activation
session users + Maximum 2G
activation session users
2G MS deactivate session
request + 2G SGSN
deactivate session requests +
3G MS deactivate session
requests + 3G SGSN
deactivate session requests
2G MS deactivate session
successes + 2G SGSN
deactivate session successes
+ 3G MS deactivate session
successes + 3G SGSN
deactivate session successes
9-39
Fault description
After the measurement task is created, the measurement result file of a certain period is not
generated, while the measurement result files of other periods are normal.
Cause analysis
The log files show that the system time is changed in the period when the measurement
result file is not generated. The measurement result file of corresponding measurement
period may be lost if the system time is changed manually or by the Network Time Protocol
(NTP) server.
Conclusion
The system time cannot be change at random.
Comment
The measurement result file of corresponding measurement period cannot be generated if
the system time is changed. If the system time is changed to earlier time, the previous
measurement result files are overwritten. This operation must be avoided.
Fault description
Observe the performance measurement data, and you can find that the number of
deactivation successes is larger than that of deactivation requests in a record. Refer to the
following:
9-40
Issue 03 (2008-04-10)
Cause analysis
The performance measurement data is reported based on the periods. By analyzing the
context data during the performance test process, you can find that the number of
deactivation successes is not recorded in the previous measurement data.
The deactivation is being performed when the data is reported in the previous period. Thus
the measurement of the deactivation successes does not start and the success times are
counted into the measurement data of the next period. Therefore, the number of deactivation
successes is larger than that of deactivation requests in the next data.
Conclusion
If the measurement data is reported when the process is not complete, the success times are
counted into the measurement data of the next period. Therefore, the number of deactivation
successes is larger than that of deactivation requests.
Comment
The performance measurement data must be analyzed in association with the context data
in the related periods. Otherwise, you may misunderstand the measurement data.
Fault description
The measurement data of one access point name (APN) is normal all the time; however,
no measurement result is reported since 16: 00.
Cause analysis
Query the measurement task status, and you can find that the task is normal. Check the
signaling link, and you can find that the APN is deleted.
Conclusion
The measurement object is deleted. Therefore, the measurement task must be deleted.
Comment
Any modification to the configuration data relating to the measurement object may lead to
measurement abnormality of the object.
Issue 03 (2008-04-10)
9-41