SJ-20101008113605-008 - ZXUN XGW (V4.10.20) EXtendable GateWay PGW LMT Operation Guide

ZXUN xGW
eXtendable GateWay
PGW LMT Opteration Guide
Version: V4.10.20
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2010-12-03 First Edition
Serial Number: SJ-20101008113605-008
Publishing Date: 2010-12-03(R1.0)

Contents
About This Manual ......................................................................................... I
Chapter 1 LMT Operation Guide ............................................................... 1-1
1.1 Introduction to the OMM System ......................................................................... 1-1
1.2 Logging in to the LMT ......................................................................................... 1-3
1.3 Relevant Operations........................................................................................... 1-5
1.3.1 Setting the Network Environment .............................................................. 1-5
1.3.2 Querying the System Time........................................................................ 1-8
Chapter 2 DPI Rule Manager ..................................................................... 2-1

2.1 Logging in to the DPI Rule Manager .................................................................... 2-1
2.2 Loading the DPI Rule ......................................................................................... 2-2
Chapter 3 MML Terminal ............................................................................ 3-1

3.1 Logging in to the MML Terminal........................................................................... 3-1
3.2 Typing Commands ............................................................................................. 3-2
3.3 Viewing the Help ................................................................................................ 3-4
3.4 Viewing the Operation Log .................................................................................. 3-4
Chapter 4 Patrol Management................................................................... 4-1

4.1 Logging in to the Patrol Management .................................................................. 4-1
4.2 Setting the System Idle Time............................................................................... 4-2
4.3 Setting a Patrol Item ........................................................................................... 4-3
4.4 Executing a Patrol Item....................................................................................... 4-6
4.5 Query a Patrol Result ......................................................................................... 4-7
4.6 Querying All Patrol Results ................................................................................. 4-9
4.7 Export the Patrol Result .....................................................................................4-11
Chapter 5 Alarm Monitoring and Management........................................ 5-1

5.1 Logging in to the Alarm Management .................................................................. 5-1
5.2 Alarm Real-time Monitoring................................................................................. 5-3
5.2.1 Viewing the Current Alarm RealTime Monitor ............................................. 5-3
5.2.2 Viewing the History Alarm RealTime Monitor .............................................. 5-6
5.2.3 Viewing the Notify RealTime Monitor ......................................................... 5-7
5.3 Alarm Querying .................................................................................................. 5-9
5.3.1 Querying Current Alarms .......................................................................... 5-9
5.3.2 Querying History Alarms ......................................................................... 5-14
5.3.3 Query Notifications ................................................................................. 5-19
I
5.4 Real-time Monitoring on the CPU/MEM.............................................................. 5-24
5.5 Other Operations Related to Alarms .................................................................. 5-28
5.5.1 Exporting Alarms.................................................................................... 5-28
5.5.2 Filtering Alarms ...................................................................................... 5-29
5.5.3 Synchronizing Alarms ............................................................................. 5-31
Chapter 6 Performance Statistics and Management............................... 6-1

6.1 Basic Concepts .................................................................................................. 6-1
6.1.1 Counters.................................................................................................. 6-1
6.1.2 Collection Granularity ............................................................................... 6-2
6.2 Logging in to the Performance Management ........................................................ 6-2
6.3 Viewing Performance Statistics ........................................................................... 6-4
6.3.1 Viewing the Counter Information................................................................ 6-4
6.3.2 Viewing a Dynamic Measurement Object ................................................... 6-5
6.3.3 Querying the Performance Data ................................................................ 6-6
6.4 Exporting Performance Statistics......................................................................... 6-9
6.4.1 Exporting Counter Information................................................................... 6-9
6.4.2 Exporting a Dynamic Measurement Object................................................6-11
6.4.3 Exporting the Performance Data.............................................................. 6-12
Chapter 7 Trace Tools ................................................................................ 7-1

7.1 Description ........................................................................................................ 7-1
7.2 Logging in to the Trace Tools .............................................................................. 7-2
7.3 Creating a Subscriber Trace Task........................................................................ 7-4
7.4 Creating a Trace Task Instance ......................................................................... 7-10
Chapter 8 Rack Chart Management .......................................................... 8-1

8.1 Logging in to the Rack Chart ............................................................................... 8-1
8.2 Rack Related Operations .................................................................................... 8-3
8.2.1 Querying the Version Information .............................................................. 8-3
8.2.2 Reloading the System............................................................................... 8-5
8.3 Board Related Operations................................................................................... 8-6
8.3.1 Querying the Memory and CPU Running Status ......................................... 8-6
8.3.2 Querying the System Hardware Information ............................................... 8-9
8.3.3 Querying Version Information of the Software Set......................................8-11
8.3.4 Resetting a Board .................................................................................. 8-13
8.3.5 Switching Over the Active/Standby Boards .............................................. 8-14
Figures............................................................................................................. I
Tables .............................................................................................................V
II
Glossary .......................................................................................................VII
III
IV
About This Manual
Purpose
This manual provides procedures and guidelines for software installation related to ZXUN
PGW system.
Intended Audience
This manual is intended for engineers and technicians who are responsible for software
installation of ZXUN PGW.
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general understanding of wireless
telecommunications technology. Familiarity with the following is helpful:
l ZXUN PGW system structure and its various components.
l Operation knowledge of ZXUN PGW.
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
Chapter 1, LMT Introduces the basic concepts and operations of the operation and
Operation Guide maintenance system of the ZXUN PGW product.
Chapter 2, DPI Rule Introduces the basic operations of the DPI rule manager in the LMT.
Manager
Chapter 3, MML Terminal Introduces the basic operations of the MML terminal in the LMT.
Chapter 4, Patrol Introduces the basic operations of the patrol management in the LMT.
Management
Chapter 5, Alarm Introduces the basic operations of the daily alarm monitoring and alarm
Monitoring and information management in the LMT.
Management
Chapter 6, Performance Introduces the basic operations of the performance statistics and
Statistics and performance statistics task in the LMT.
Management
Chapter 7, Trace Tools Introduces the basic operations of the subscriber trace tasks in the LMT.
Chapter 8, Rack Chart Introduces the basic operations of the rack chart management in the LMT.
Management
Glossary Lists the glossary in this manual.
I
FCC Compliance Statement
This device complies with part 15 of the FCC Rules. Operation is subject to the following
two conditions.
1. This device may not cause harmful interference.
2. This device must accept any interference received, including interference that may
cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.
Conventions
ZTE documents employ the following typographical conventions.
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input fields, radio button names, check
boxes, drop-down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens and company name.
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be checked before

proceeding further.
Tip: Indicates a suggestion or hint to make things easier or more productive

for the reader.
II
Chapter 1
LMT Operation Guide
Table of Contents
Introduction to the OMM System ................................................................................1-1
Logging in to the LMT.................................................................................................1-3
Relevant Operations...................................................................................................1-5
1.1 Introduction to the OMM System

Basic Composition of the ZXUN PGW System
A complete ZXUN PGW system should be composed of a ZXUN xGW foreground, a Local
Maintenance Terminal (LMT), an MPU board debugging terminal, an local alarm box, and
an EMS OMM server; its networking is as shown in Figure 1-1.
Figure 1-1 Composition of ZXUN PGW
Description to the Operation & Maintenance System

According to the levels of the operation & maintenance system, the LMT, the MPU
debugging terminal, and the alarm box are called the local operation & maintenance
system; the EMS is called the professional operation & maintenance system; and the
1-1
SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

ZXUN xGW PGW LMT Opteration Guide
NMS is called the comprehensive operation & maintenance system. The schematic
diagram of the operation & maintenance system is as shown in Figure 1-2.
Figure 1-2 Schematic Diagram of the Operation & Maintenance System
Wherein:
l The MPU debugging terminal undertakes the initialization of the MPU board (including
setting the startup mode of the MPU board, setting the IP address, and loading the
version files), and it performs data configuration on the ZXUN xGW in the method of
command line.
l The LMT undertakes the function such as viewing daily alarms, managing
performance statistics tasks, tracing service signaling, and viewing board status.
l The alarm box is installed locally, prompts alarm information in audible and visible
ways.
l The EMS provides functions such as a centralized topology management, a
centralized log management, a centralized alarm management, a centralized
performance management, a centralized data configuration management, and a
centralized security management, and supports multiple interface protocols including
the CORBA, the FTP, the SNMP, and the TELNET.
l The NMS is higher than the EMS, which is a comprehensive operation & maintenance
system used for the operators to manage the inter-vendor, inter-product, and
inter-area telecom network.
Local Maintenance Terminal

The LMT software is installed on a common Personal Computer (PC), and communicates
to the ZXUN PGW foreground by the communication support program, as shown in Figure
1-3.
1-2

Chapter 1 LMT Operation Guide
Figure 1-3 Function of the LMT and Communication with the Foreground
The LMT has the following functions.

l DPI rule manager
l MML terminal
l Patrol management
l Alarm management
l Performance management
l Trace tool
l Rack chart
Note
If the EMS uses ZTE NetNumen M31 NE centralized management system, refer to
NetNumen M31 (V12.10.30) related documents for daily operations of the EMS.
1.2 Logging in to the LMT

Prerequisites
l The LMT is connected to the ZXUN PGW foreground properly.
l The ZXUN PGW foreground runs properly.
l The LMT software is installed successfully.
l The network environment addresses of the LMT are set.
Context
This topic describes how to log in to the LMT properly.
Steps
1. Open the Daily-Maintenance Login dialog box of the LMT using either of the following
methods, as shown in Figure 1-5.
1-3

l Run the program with the relative path as \ums-clnt\bin\run.exe.

l Choose Start > All Programs > Local Maintenance Terminal > Local
Maintenance Terminal, as shown in Figure 1-4.
Figure 1-4 Choose Local Maintenance Terminal
The Daily-Maintenance Login dialog box appears as shown in Figure 1-5.
Figure 1-5 Login
2. Type User Name and Password in Figure 1-5, and click OK. After successful login,
the Daily Maintenance window as shown in Figure 1-6 appears.
1-4

Figure 1-6 LMT Main Window
– End of Steps –
1.3 Relevant Operations

1.3.1 Setting the Network Environment
Prerequisites
l The foreground runs properly.
l The LMT software is ready.
Context
Config the Environment provides the function of setting the LMT local IP, the local node,
the module number, and the opposite MPU board IP; set them according to the network
planning and the actual configuration data to log in to the LMT properly.
Steps
1. Open the Config the Environment of Software dialog box using either of the following
methods.
l Run the program with the relative path as \tools\config\run.bat.
l Choose Start > All Programs > Local Maintenance Terminal > Config the
Environment, as shown in Figure 1-7.
1-5

Figure 1-7 Choose Config the Environment
The Config the Environment of Software dialog box appears as shown in Figure
1-8.
Figure 1-8 Config the Environment of Software
Parameters in Figure 1-8 are described in Table 1-1.
1-6

Table 1-1 Description to Parameters in Config the Environment of Software
Parameter Meaning Example
Local IP IP address of the LMT connected to the ZXUN PGW

192.168.110.230
foreground
Remote IP IP address of the port Console on the Management

192.168.110.93
Process Unit (MPU) board
Local Node Node No. of the LMT, unrepeatable with other node No. It is 201 by default.
Module Module No. of the LMT, unrepeatable with other module

It is 250 by default.
Number No.
SNMP Config Select the corresponding SNMP version It is SNMPv2c by

default.
2. Type corresponding parameters in Figure 1-8 and click OK to complete configuring

the network environment.
Result
When the network environment is set, choose Start > All Programs > Local Maintenance
Terminal > Winnttcp, the ZTE Communication System window appears, as shown in
Figure 1-9.
Figure 1-9 Communication Status
1-7

Parameters in Figure 1-9 are described as follows:

l represents the LMT: 201 is the node number of the LMT, and 31 is the office number.
l represents the ZXUN PGW foreground: 1 is the foreground node number.
l the green link between them means that the communication between the LMT and
the ZXUN PGW foreground works properly
Follow-Up Action
If the link in Figure 1-9 is in red color, this means the link between the LMT and ZXUN
xGW foreground is broken, which requires to check the network environment configuration
(including IP address setting and whether the node numbers are conflict) and the physical
line connection.
1.3.2 Querying the System Time

Prerequisites
l You have logged in to the LMT properly.
Context
The LMT provides the function to query the time of the client and the server; use this
function to compare the current time of the server and the client to ensure the time
consistency.
Steps
1. On the Daily Maintenance window of the LMT, choose System > Query System
Time. A dialog box as shown in Figure 1-10 appears.
1-8

Figure 1-10 Querying System Time
On Figure 1-10, the detailed time zone and time information of Server Time and Client
Time are displayed. Wherein:
l Server Time identifies the time of the MPU board on the ZXUN PGW foreground.
l Client Time identifies the time of the LMT.
2. Click OK to complete querying the system time.
Follow-Up Action
l If the current time of the client and the server is inconsistent, generally adjust the client
time.
l If the server time is faulty, Telnet to the MPU board to adjust the server time.
1-9

This page intentionally left blank.
1-10

Chapter 2
DPI Rule Manager
Table of Contents
Logging in to the DPI Rule Manager ...........................................................................2-1
Loading the DPI Rule .................................................................................................2-2
2.1 Logging in to the DPI Rule Manager

Prerequisites
Context
The loading function of the Deep Packet Inspection (DPI) rule is deployed on the
foreground MPU in the form of the plug-in package, and users can load the DPI rule
information through the LMT.
Steps
• On the Daily Maintenance window, double-click DPI Rule Manager, and the DPI Rule
Manager window appears, as shown in Figure 2-1.
2-1

Figure 2-1 DPI Rule Manager
2.2 Loading the DPI Rule

Prerequisites
l You have logged in to the DPI Rule Manager properly.
Context
a user can execute the DPI rule loading function on the LMT. After the LMT uploads the DPI
rule to the MPU, inform the services to load the DPI rule file in the method of the internal
command interface.
Steps
1. On the DPI Rule Manager window, double-click . The Choose dialog box appears,
as shown in Figure 2-2.
2-2

Chapter 2 DPI Rule Manager
Figure 2-2 Choose
2. Choose the file to be loaded, and click Open to go to the window as shown in Figure
2-3.
Figure 2-3 DPI Rule Selected
2-3

3. On Ne Type, click Please select NE type. Choose PGW from the prompted shortcut
menu, as shown in Figure 2-4.
Figure 2-4 Choose Ne
4. After choosing the Ne Type, right-click this DPI rule, and select Load DPI Rule File
from the prompted shortcut menu, as shown in Figure 2-5. The DPI rule file is loaded,
and the progress for loading the DPI rule file is displayed.
2-4

Chapter 2 DPI Rule Manager
Figure 2-5 Load DPI Rule File
Note
The time for uploading the DPI rule file is related to the size of the DPI rule file, and
generally it is not more than 15 seconds.
2-5

2-6

Chapter 3
MML Terminal
Table of Contents
Logging in to the MML Terminal..................................................................................3-1
Typing Commands .....................................................................................................3-2
Viewing the Help ........................................................................................................3-4
Viewing the Operation Log .........................................................................................3-4
3.1 Logging in to the MML Terminal

Prerequisites
Context
The MML terminal tool provides the command tree navigation and the command
configuration functions through a unified window. Users can use this tool to perform
command fast searching, command full-view query, input instant prompt, and configuration
help
Steps
• On the Daily Maintenance window, double-click MML Terminal, the MML Terminal
window appears, as shown in Figure 3-1.
3-1

Figure 3-1 MML Terminal
l On the MML Terminal window, the left pane is the command tree. Users can
query the command help through clicking the command nodes in the command
tree. By the command searching function, users can find the specified commands
quickly.
l On the Input Information field, users can type configuration commands, and the
system automatically opens the corresponding help pages of the command typed.
Meanwhile, the floating prompt is also supported, and it automatically prompts the
subsequent parameters according to the user input and the syntax.
l Users type the configuration commands and press Enter, the command execution
window is displayed on the Output Information tab, which displays the command
execution information.
l On the Help tab, related command instructions are provided.
l On the Operation Log tab, the history records of the commands typed are
displayed.
3.2 Typing Commands

Prerequisites
3-2

Chapter 3 MML Terminal

l You have logged in to the MML Terminal properly.
Context
This topic describes how to type the configuration command information.
Steps
1. In the Input Information field on the MML Terminal window, type a configuration
command. The system automatically opens the corresponding help page of the
command typed, and the floating prompt is also supported. It automatically prompts
the subsequent parameters according to the user input and the syntax.
2. After typing the command, press Enter. The command information and command
execution result are displayed on the Output Information tab.
Example
For example, when typing a ? in Input Information, the result is as shown in Figure 3-2.
Figure 3-2 Result of the Command “?”
3-3

3.3 Viewing the Help

Prerequisites
Context
This topic describes how to view the command help, so as to know the function and the
used syntax of a command.
Steps
• On the Help tab of the MML Terminal window, query the command help information.
3.4 Viewing the Operation Log

Prerequisites
Context
This topic describes how to query the command operation log, so as to search the used
commands and corresponding output result information.
Steps
• On the Operation Log tab of the MML Terminal, query the command operation log
information.
3-4

Chapter 4
Patrol Management
Table of Contents
Logging in to the Patrol Management .........................................................................4-1
Setting the System Idle Time ......................................................................................4-2
Setting a Patrol Item...................................................................................................4-3
Executing a Patrol Item ..............................................................................................4-6
Query a Patrol Result .................................................................................................4-7
Querying All Patrol Results.........................................................................................4-9
Export the Patrol Result............................................................................................4-11
4.1 Logging in to the Patrol Management

Prerequisites
Context
The patrol management tool can automatically patrol the equipment systems, and provide
the patrol report and conclusions in a simple and direct way.
Steps
• On the Daily Management window, double-click Patrol Management. The Patrol
Management window appears, as shown in Figure 4-1.
4-1

Figure 4-1 Patrol Management
4.2 Setting the System Idle Time

Prerequisites
l You have logged in to the Patrol Management properly.
Context
Some patrol function requires a long time to carry out, so we want it to be carried out when
the server is idle. Users can manually set the system idle time, in this way, the patrol
function with the task type as will be executed at the specified idle time. The minimum
unit of the idle time is the hour.
Steps
1. On the Patrol Management window, click . The System idle time setting dialog
box appears, as shown in Figure 4-2.
4-2

Chapter 4 Patrol Management
Figure 4-2 System idle time setting
2. Select the system idle time from Figure 4-2.
Note
Time of one day is divided into 24 segments, and a user can select multiple system
idle time.
3. Click Confirm to complete setting the system idle time.

4.3 Setting a Patrol Item

Prerequisites
Context
This topic describes how to manually modify the period, task status (active or inactive),
and warning judgement condition of a patrol item.
Steps
1. On the Patrol Management window, right-click the patrol item to be modified. A
shortcut menu appears, as shown in Figure 4-3.
4-3

Figure 4-3 Right-click a Patrol Item
2. Select Setting, and the Patrol task setting dialog box appears, as shown in Figure
4-4.
4-4

Figure 4-4 Patrol task setting
Parameters in Figure 4-4 are described in Table 4-1.
Table 4-1 Description of Patrol Task Setting
Parameter Meaning Example
Name of the selected patrol item,

Patrol item name -
unchangeable
Task state Includes Active and Inactive. Active
Time of this patrol function automatically

Scheme policy executing, includes: By hour, By day, By week, By day
and By month. By default, it is By day.
Sets the fixed time range. When this parameter

Select time
is selected, the Start date and End date -
range
should be set.
Select all time Sets all time ranges. Selected
Note
Double-clicking a patrol item can also enter the Patrol task setting dialog box.
3. Set parameters in Figure 4-4.
4. Click the Confirm button to complete the Patrol task setting.

4-5

Result
After setting the patrol item, the system automatically executes the patrol function
according to the set patrol period and time.
4.4 Executing a Patrol Item

Prerequisites
Context
A patrol item is executed in the following ways:
l System automatically executes a patrol item
After setting a patrol item information, the system automatically executes the patrol
item according to the set patrol item period and time. When multiple patrol tasks are
executed serially, wait till a patrol task is executed and the patrol data are saved into
a file, the next patrol task is executed.
l Manually executes a patrol item
When a user manually executes a patrol task, the foreground equipment immediately
executes the patrol task. The patrol result is saved as the data file, and the patrol client
downloads the data file through the FTP to analyze and display the patrol result.
This topic describes how to manually execute a patrol item.
Steps
1. On the Patrol Management window, right-click the patrol item to be executed. Select
Execute immediate from the prompted shortcut menu, and the Attention dialog box
appears, as shown in Figure 4-5.
Figure 4-5 Attention
2. Click OK to start executing the patrol item.

4-6

Result
After the execution, the result of executing a patrol item is displayed in the Result of
executing immediately field, as shown in Figure 4-6.
Figure 4-6 Result of executing immediately
4.5 Query a Patrol Result

Prerequisites
Context
This topic describes how to query the execution result of a patrol item.
4-7

Steps
1. On the Patrol Management window, right-click the patrol item to be queried, and
select Query timing patrol results from the prompted shortcut menu. The Patrol
result dialog box appears, as shown in Figure 4-7.
Figure 4-7 Patrol result
2. View the patrol result in Figure 4-7, and click Confirm to compete the query.
Follow-Up Action
Set the query method of the patrol in Figure 4-7 using the following way.
1. In Figure 4-7, click . The Query condition setting dialog box appears, as shown
in Figure 4-8.
4-8

Figure 4-8 Query condition setting
2. Select the patrol item to be queried and the time range, and click Confirm.
4.6 Querying All Patrol Results

Prerequisites
Context
This topic describes how to query the execution results of all patrol items.
Steps
1. On the Patrol Management window, click . The Patrol result dialog box appears,
4-9

2. View the patrol result in Figure 4-9, and click Confirm to complete the query.
Follow-Up Action
Set the query method of the patrol in Figure 4-9 using the following way.
1. In Figure 4-9, click . The Query condition setting dialog box appears, as shown
in Figure 4-10.
4-10

Figure 4-10 Query condition setting
2. Select the patrol item to be queried and the time range, and click Confirm.
4.7 Export the Patrol Result

Prerequisites
Context
This topic describes how to locally save the patrol result by exporting the patrol result. Two
ways are available for exporting the patrol result.
l After manually executing a patrol task, export the patrol result in Result of executing
immediately. For the method of manually executing a patrol task, refer to 4.4
Executing a Patrol Item.
l Export the patrol result on the Patrol result dialog box. For the method of logging in
to the Patrol result dialog box, refer to 4.5 Query a Patrol Result or 4.6 Querying All
Patrol Results.
Steps
• After manually executing a patrol result, export the patrol result in the Result of
executing immediately field.
1. In the Result of executing immediately field as shown in Figure 4-11, click .
4-11

Figure 4-11 Result of executing immediately
The Export file dialog box appears, as shown in Figure 4-12.
4-12

Figure 4-12 Export file
2. Set the location and file name to be saved, and click Save to complete exporting
the patrol result.
• Export the patrol result on the Patrol result dialog box.
1. On the Patrol result dialog box as shown in Figure 4-13, click . The Export file
dialog box appears, as shown in Figure 4-12.
4-13

2. Set the location and file name to be saved, and click Save to complete exporting
the patrol result.
4-14

Chapter 5
Alarm Monitoring and
Management
Table of Contents
Logging in to the Alarm Management .........................................................................5-1
Alarm Real-time Monitoring ........................................................................................5-3
Alarm Querying ..........................................................................................................5-9
Real-time Monitoring on the CPU/MEM ....................................................................5-24
Other Operations Related to Alarms .........................................................................5-28
5.1 Logging in to the Alarm Management

Prerequisites
Context
The alarm management function can integrally monitor and manage the faults and alarms
occurred on ZXUN PGW, and can directly display them to the maintenance personnel in
audible and visible ways through the alarm box. Users can perform a real-time monitoring
on the alarms, including viewing, acknowledging, and querying.
l According to alarm severity, the alarm information can be classified as: critical, major,
minor, and warning.
l According to the fault types, the alarm information can be classified as:
communication alarms, Quality of Service (QoS) alarms, equipment alarms,
processing error alarms, and environment alarms.
Steps
• On the Daily Maintenance window, double-click the Alarm Management node, the
Alarm Management window appears as shown in Figure 5-1.
5-1

Figure 5-1 Alarm Management
In Figure 5-1, the Alarm Manager management tree is on the left pane, which lists the
basic functions of the alarm management, including the monitoring and querying; the
detailed alarms are displayed on the right pane, and it is the Current Alarm RealTime
Monitor view by default.
Follow-Up Action
Double-click any alarm information on the right pane in Figure 5-1, the details are displayed
5-2

Chapter 5 Alarm Monitoring and Management
Figure 5-2 Alarm Details
In Figure 5-2, the Information tab shows the basic information of the alarm, and the
Description tab shows the reason analysis and default handling suggestions for this alarm.
5.2 Alarm Real-time Monitoring

5.2.1 Viewing the Current Alarm RealTime Monitor
Prerequisites
l You have logged in to the Alarm Management properly.
Context
The current alarm real-time monitoring function supports to monitor the alarm status of the
current system, so as to enable users to know the network running state; and the faults
can be quickly solved once the system is faulty. The real-time monitoring of the current
alarms reflects the unsolved alarms in the system in real-time.
5-3

Steps
1. On the Alarm Management window, double-click the Alarm Manager > Alarm
RealTime Monitor > Current Alarm RealTime Monitor node to go to the window
as shown inFigure 5-3.
Figure 5-3 Current Alarm RealTime Monitor
On the right pane in Figure 5-3, the real-time alarm information is displayed as
described in Table 5-1.
Table 5-1 Alarm Details
Alarm Meaning
Information
Alarm ID Sequence No. of the alarms occurred
Severity Alarm levels. Classified as: Severity, Important, Common, and Light.
Alarm Code Code of the alarm information in the alarm database, and it is the unique ID of
the alarm information.
Alarm A simple description to the alarm information, describes the alarm error type.
Description
Happen Location where the alarm is generated, corresponded to the rack, shelf, slot,
Position and CPU ID
5-4

Alarm Meaning
Information
Occurrence Time when the alarm is generated

Time
Alarm Info Other information of the alarm, including the module generating the alarm
Alarm Type Alarm type. Classified as: Communication alarm, Quality of Service (QoS)
alarm, equipment alarm, processing error alarm, and environment alarm.
Information Detailed reasons why an alarm is generated
Comment Default handling suggestions for an alarm
2. Query the current alarm real-time monitoring information in Figure 5-3.

Double-click any alarm information on the right pane in Figure 5-3, the details are
displayed, as shown in Figure 5-4.
Figure 5-4 Alarm Details
Follow-Up Action
In the alarm real-time monitoring, two more functions are provided.
5-5

l Alarm Export
Click in Figure 5-3 to export the alarm information in xls format and save it on the
local server.
l Alarm Filter
Input keywords in the input box after the Filter Condition in Figure 5-3, alarm
information satisfying the keywords will be displayed.
5.2.2 Viewing the History Alarm RealTime Monitor

Prerequisites
l You have logged into the Alarm Management properly.
Context
The history alarm real-time monitoring supports to monitor the history alarm status of the
current system, so as to enable users to know the previous running state of the network.
The history alarm real-time monitoring reflects the alarms occurred and handled in the
system in real-time, but the history alarms before opening the View are not displayed.
Steps
RealTime Monitor > History Alarm RealTime Monitor node to go to the window as
shown in Figure 5-5.
5-6

Figure 5-5 History Alarm RealTime Monitor
2. Double-click any alarm information on the right-pane in Figure 5-5, and the alarm
details are displayed.
Follow-Up Action
In the history alarm real-time monitoring, two more functions are provided.
l Alarm Export
Click in Figure 5-5 to export the alarm information in xls format and save it on the
local server.
l Alarm Filter
Input keywords in the input box after the Filter Condition in Figure 5-5, and the alarm
5.2.3 Viewing the Notify RealTime Monitor

Prerequisites
l The LMT is connected to ZXUN PGW foreground properly.
5-7

Context
The notification is a kind of special alarms, it reflects the system daily running status,
reminds the maintenance personnel of the system running state and displays it through
the LMT.
The notification real-time monitoring reflects the matters to be handled during equipment
running in the system in real-time, but the notifications reported before opening the View
are not displayed.
Steps
RealTime Monitor > Notify RealTime Monitor node to go to the window as shown
in Figure 5-6.
Figure 5-6 Notify RealTime Monitor
2. Click any notification in Figure 5-6 the notification details are displayed.
Follow-Up Action
In the notification real-time monitoring, two more functions are provided.
l Notification Export
5-8

Click in Figure 5-6 to export the notification information as xls file and save it on
the local server.
l Notification Filter
Input keywords in the input box after the Filter Condition in Figure 5-6, notification
5.3 Alarm Querying

5.3.1 Querying Current Alarms
Prerequisites
Context
Querying current alarms supports that users query current alarms according to certain
conditions. Users can set specified conditions such as alarm code, location, time, severity,
and alarm type to query current alarms.
Steps
1. On the Alarm Management, double click the Alarm Manager > Alarm Query >
Current Alarm Query node to go to the Current Alarm Query dialog box, as shown
in Figure 5-7.
5-9

Figure 5-7 Current Alarm Query (Alarm Code)
2. Set querying by alarm codes.

On the Alarm Code tab, select the alarm codes to be queried in the Available Items
area, and assign the selected alarm codes to the Selected Items area by clicking
or . Alarm codes in Selected Items are those to be queried. If no alarm code is
selected in the Alarm Code tab, this means to select all alarm codes.
3. Set querying by the alarm time, the type, and the level.
a. Click the Time/Type/Level tab, as shown in Figure 5-8.
5-10

Figure 5-8 Querying Current Alarms (Time/Type/Level)
b. Select the alarm time to be queried in the Happen Time.

c. Select the alarm type to be queried in the Alarm Type; if not alarm type is selected,
this means to select all types.
d. Select the alarm level to be queried in the Severity; if no alarm level is selected,
this means to select all alarm levels.
4. Set querying by the alarm position.

a. Click the Alarm Position tab, as shown in Figure 5-9.
5-11

Figure 5-9 Querying Current Alarms (Alarm Position)
b. Select the position of the alarm to be queried; if no position is selected, this means
to select all positions.
5. Set fuzzy query by the alarm information.
a. Click the Fuzzy Query tab, as shown in Figure 5-10.
5-12

Figure 5-10 Querying Current Alarms (Fuzzy Query)
b. Type the alarm condition information in Alarm Information Fuzzy Query

Condition; if no information is typed, this means no fuzzy query condition setting.
6. After setting the alarm condition, click OK. The query result prompts, as shown in
Figure 5-11.
5-13

Figure 5-11 Querying Current Alarms (Query Result)
5.3.2 Querying History Alarms

Prerequisites
Context
Querying history alarms supports that users query the history alarms according to certain
condition. Users can set specified query conditions such as alarm code, position, time,
severity, and alarm type to query the history alarms.
Steps
1. On the Alarm Management window, double-click the Alarm Manager > Alarm Query
> History Alarm Query node to go to the History Alarm Query window, as shown in
Figure 5-12.
5-14

Figure 5-12 History Alarm Query (Alarm Code)

On the Alarm Code tab, select alarm codes to be queried in the Available Items area,
and assign the selected alarm codes to Selected Items by clicking or . The alarm
codes in the Selected Items are those to be queried. If no alarm code is selected in
the Alarm Code tab, this means to select all alarm codes.
3. Set querying by the alarm time, type, and severity.
5-15

Figure 5-13 History Alarm Query (Alarm Time/Type)
b. Select the alarm time to be queried in the Happen Time.

c. Select the alarm type to be queried in the Alarm Type; if no alarm type is selected,
d. Select the alarm severity to be queried in the Severity, if no severity is selected,

this means to select all severities.
4. Set the alarm position.

5-16

Figure 5-14 History Alarm Query (Alarm Position)
b. Select the alarm position to be queried; if no position is selected, this means to

select all positions.
5. Set the fuzzy query.
5-17

Figure 5-15 History Alarm (Fuzzy Query)
b. Type the alarm condition information to be queried in the Alarm Information

Fuzzy Query Condition; if no information is typed, this means no fuzzy query
condition setting.
6. After setting the alarm condition, click OK. The alarm query result prompts, as shown
in Figure 5-16.
5-18

Figure 5-16 History Alarm Query (Query Result)
5.3.3 Query Notifications

Prerequisites
l You have logged in to the Alarm Management.
Context
The notification query function supports that users query notifications according to certain
conditions. Users can set specified conditions such as alarm codes, position, time, and
alarm types to query the notification data.
Steps
1. On the Alarm Management window, double-click the Alarm Manager > Alarm Query
> Notify Query node to go to the Notify Query dialog box, as shown in Figure 5-17.
5-19

Figure 5-17 Notify Query (Alarm Code)

In the Alarm Code tab, select the alarm codes to be queried in the Available Items
area, assign the selected alarm codes to Selected Items by clicking or , and
the alarm codes in the Selected Items are those to be queried. If no alarm code is
selected in the Alarm Code tab, this means to select all alarm codes.
3. Set querying by the alarm time, type, and severity.
5-20

Figure 5-18 Notify Query (Time/Type/Level)
b. Select the notification time to be queried in the Happen Time.

c. Select the alarm type to be queried in the Alarm Type; if no alarm type is selected,
d. Select the alarm severity to be queried in the Severity. If no alarm severity is

selected, this means to selected all severities.
4. Set the alarm position.

5-21

Figure 5-19 Notify Query (Alarm Position)
b. Select the notification position to be queried; if no position is selected, this means

to select all positions.
5. Set the fuzzy query.
5-22

Figure 5-20 Notify Query (Fuzzy Query)
b. Type the notification information to be queried in the Alarm Information Fuzzy

Query Condition; if no information is typed, this means no fuzzy query condition
setting.
6. After the notification condition is set, click OK. The notification query result prompts,
5-23

Figure 5-21 Notify Query (Query Result)
5.4 Real-time Monitoring on the CPU/MEM

Prerequisites
Context
The LMT supports that users monitor the resource utilization of CPUs of the boards,
including the CPU and memory utilization ratio, enabling users to know the CPU utilization
in real-time.
Steps
1. On the Alarm Management window, right-click the Alarm Manager > CPU/MEM
RealTime Monitor node, and a shortcut menu prompts. Select New RealTime
Monitor to go to the RealTime Monitor dialog box, as shown in Figure 5-22.
5-24

Figure 5-22 RealTime Monitor
2. Type the name to be monitored in the RealTime Monitor Name. Click OK to go to the
dialog box as shown in Figure 5-23.
5-25

Figure 5-23 Select CPU
Figure 5-23 shows the shelf, slot and ID of the CPU which are configured in the rack.
3. Select the CPU ID to be monitored in Figure 5-23 and click OK to go to the window as
shown in Figure 5-24.
5-26

Figure 5-24 RealTime Monitor Result
In Figure 5-24, the CPU and memory utilization is identified by a red line and a blue
line by default.
l CPU Utilization Monitor
Dynamically displays the CPU utilization in real-time, and the data are refreshed
every 5 seconds. Wherein, the horizontal axis represents the time, while the
vertical axis represents the utilization.
l Memory Utilization Monitor
Dynamically displays the memory utilization in real-time, and the data are
refreshed every 5 seconds. Wherein, the horizontal axis represents the time,
while the vertical axis represents the utilization.
l Monitor Objects
Lies beneath the diagram; displays the information of the currently monitored
objects, and indicates the rack, shelf, slot, and ID of the monitored CPU.
4. View the CPU and memory utilization in Figure 5-24.
The CPU and memory utilization can be used to determine whether the boards are at
overload status. For the proper operation range of the CPU utilization and the memory
utilization, refer to Table 5-2.
5-27

Table 5-2 CPU Utilization and Memory Utilization of the Boards
Board Average Value Range of CPU Average Value Range of Memory

Utilization Utilization
MPU board 10% ~ 85% Lower than 80%
GSU board Lower than 40% Lower than 75%
PFU board Lower than 15% Lower than 50%
Follow-Up Action
When the data traffic is heavy, the CPU and memory utilization may be high.
5.5 Other Operations Related to Alarms

5.5.1 Exporting Alarms
Prerequisites
Context
Exporting alarms means to export the alarms and save the alarm information locally.
Note
Current Alarm RealTime Monitor, History Alarm RealTime Monitor, Notify RealTime
Monitor, and Alarm Query all support exporting alarms, and the procedures are also
similar. Here we use exporting alarms in Current Alarm RealTime Monitor as an
example.
Steps
1. On the Current Alarm RealTime Monitor view of the Alarm Management window,
click , the Save dialog box appears, as shown in Figure 5-25.
5-28

Figure 5-25 Save
Currently ZXUN PGW supports to save the files in .xls and .txt formats.
2. In Figure 5-25, set the position where the alarms are saved and type a file name. Click
Save to complete exporting alarms.
Follow-Up Action
After exporting the alarms, view the alarm information by opening the .xls or the .txt files
on the local computer.
5.5.2 Filtering Alarms

Prerequisites
l The LMT is connected to the ZXUN xGW foreground properly.
Context
In the alarm (or notification) real-time monitoring, the alarm information can be selected
to display according to the filtering condition. When the filtering condition is set, only the
alarms (or notifications) satisfying the filtering condition are displayed.
5-29

Note
Current Alarm RealTime Monitor, History Alarm RealTime Monitor, Notify RealTime
Monitor all support to display the alarm information according to the filtering condition.
Steps
1. On the Current Alarm RealTime Monitor view of the Alarm Management window,
click the input box after Filter Condition, as shown in Figure 5-26.
Figure 5-26 Filter Condition
2. Set the keywords of the filtering condition in the input box as shown in Figure 5-26,
and the alarm information is displayed according to the filtering condition.
For example: Type Severity in the input box as shown in Figure 5-26, the alarm
information is displayed as shown in Figure 5-27.
5-30

Figure 5-27 Display by Filtering Condition-Example 1
Note
Currently, the LMT supports filtering by keywords.
5.5.3 Synchronizing Alarms

Prerequisites
5-31

Context
The synchronization function provides users with the capability of synchronizing NE
information. When users find that the alarm data on the LMT may be inconsistent with
that on the ZXUN PGW foreground, use this function to forcibly synchronize the alarm
data with that on the foreground equipment.
Steps
1. On the Alarm Management window, choose Operation > Synchronize Alarm, a
dialog box as shown in Figure 5-28 appears.
Figure 5-28 Synchronization Success
2. Click OK as shown in Figure 5-28 to complete synchronizing alarms.

5-32

Chapter 6
Performance Statistics and
Management
Table of Contents
Basic Concepts ..........................................................................................................6-1
Logging in to the Performance Management ..............................................................6-2
Viewing Performance Statistics ..................................................................................6-4
Exporting Performance Statistics................................................................................6-9
6.1 Basic Concepts

6.1.1 Counters
Definition
A counter, which is also called a statistical item, is a variable that calculates the number
of times that a particular service occurs or the number of a particular resource. The
value of the statistical item is related with the measurement object and time quantum.
Without the restriction of measurement objects or time quantum, the statistical item value
is meaningless.
Collection Methods
The performance statistics function is to collect the values of counters on the measurement
objects within a period of time.
There are four collection methods available, listed as follows.
l Cumulative Counter (CC) Collection
A running counter is saved in the tested NE, and it is used to perform cumulative
counting on a kind of events. When each collection cycle starts, the counter will be
reset to a predefined value (generally 0). When the collection cycle ends, the value
of the counter is the valid collection result.
l GAUGE Collection
Measures the dynamic variables that change bidirectionally (increase or decrease),
and these variables should be integers or real numbers. The variable value read when
the collection cycle ends is the valid collection result.
l Discrete Event Registration (DER) Collection
6-1

DER collection is a measurement method for a group of events related with the
measured attribute. Here, the Nth times of occurrence of one or some specified
events in this group of events will be regarded as the trigger point to drive the
measurement process, and furthermore to form measurement values. The value of
N depends on the occurrence frequency of the specified event(s). The measurement
value of discrete event registration will be reset when each collection cycle starts.
When the collection cycle ends, a valid collection result is given according to the
corresponding measurement value.
l Status Inspection (SI) Collection
Some internal counters for resource management purpose are saved in the tested
NE, and they are constantly read at the preset sampling frequency. The measurement
value of status inspection will be reset when each collection cycle starts. When
the collection cycle ends, a valid collection result is calculated according to all the
sampling values in this cycle.
6.1.2 Collection Granularity

The collection granularity refers to the cycle that the operation & maintenance system
collects data from the ZXUN PGW foreground.
l The collection granularity that can be set on the LMT is 15 minutes.
l The collection granularity that can be set on EMS is generally 5 minutes, 15 minutes,
and 1 hour.
6.2 Logging in to the Performance Management

Prerequisites
Context
Performance management collects the daily running performance indices of the ZXUN
xGW system by creating measurement tasks, and provides query and operation functions,
too.
l Query includes querying the counter information, querying dynamic measurement
objects, and querying the performance data sub-function; it provides users with
information of corresponding measurement types, counters, and measurement
objects, and provides a report about the running status of the whole network for
users.
l Operation includes two functions: synchronizing and exporting.
à Synchronizing means to execute the synchronization between the LMT and the
ZXUN PGWforeground, ensuring the data accuracy.
6-2

Chapter 6 Performance Statistics and Management
à Exporting means to export the query result as Excel files, which is used for users
to analyze the data.
Steps
• On the Daily Maintenance window, double-click the Performance Management
node to go to the Performance Data View window, as shown in Figure 6-1.
Figure 6-1 Performance Data View
As shown in Figure 6-1, the Manage Tree is on the left pane, which is a relation tree of
the NE location and the measurement object types. It is composed of 4-layer nodes.
l The 1-layer node is the performance management root node, displayed as
Performance Management by default.
l The 2-layer node is the NE type node, which records the NE types managed by
the LMT, displayed as PGW and COMM by default. If the PGW and the SGW are
integrally installed, the SGW still displays.
à PGW
PGW provides the performance measurement types related to PS system.
à COMM
COMM provides the performance measurement types of the CPU/MEM and
ports based on the general equipment.
6-3

l The 3-layer node is the measurement type information integrated node, records
the measurement types with similar functions.
l The 4-layer node is the measurement type node, records all measurement type
information.
6.3 Viewing Performance Statistics

6.3.1 Viewing the Counter Information
Prerequisites
l You have logged in to the Performance Management properly.
Context
The counter is a data representation of the running status of an aspect of the network or
the NE.
Steps
• On the Performance Management window, right-click any measurement type node
on the left pane and select View Counter Information from the prompted shortcut
menu, the corresponding counters are displayed on the right pane.
Example
On the PM Data View LMT window, right-click PGW > General Measurement > RADIUS
Signal Measurement, and select View Counter Information from the prompted shortcut
menu. The counter information as shown in Figure 6-2 appears on the right pane.
6-4

Figure 6-2 Counters in RAUIUS Signal Measurement
In the right pane as shown in Figure 6-2, the counter information included in the RADIUS
Signal Measurement is displayed in a list, including Index, Name, and Measurement
Type, as shown in Table 6-1.
Table 6-1 Counter Info View
Parameter Description
Index Index of a counter. It is the unique ID of a counter.
Name Description of a counter. It describes the specific information of a counter.
Measurement type of a counter. It includes measurement type name and

Measurement Type
measurement type index.
6.3.2 Viewing a Dynamic Measurement Object

Prerequisites
l You have logged in to the Performance Management properl.
6-5

Context
An measurement object is a list of exact objects to be measured, and the performance
measurement gathers and displays the data according to the measurement objects.
If the measurement type reports data according to the modules and units, there is no
measurement object.
Steps
• On the Performance Management window, right-click any measurement type node
from the Manage Tree on the left pane, and select Dynamic Measurement Object
from the prompted shortcut menu. Corresponding counters are listed on the right pane.
6.3.3 Querying the Performance Data

Prerequisites
l You have logged in to the Performance Management properly.
Context
Display the performance data on the LMT interface for users to make analysis by selecting
counters, measurement objects, and query time quantum.
Steps
1. On the Performance data query dialog box, right-click the measurement type node to
be queried on the Management Tree on the left pane, and select View Performance
Data from the prompted shortcut menu. The query set dialog box appears, as shown
in Figure 6-3.
6-6

Figure 6-3 Performance data query-query set
In Figure 6-3, the default page is Measurement Information, which is composed of

5 areas, as shown in Figure 6-4.
Figure 6-4 Performance data query-Area Explanation
In Figure 6-4, function of each area is described in Table 6-2.
6-7

Table 6-2 Performance data query-Area Explanation
Area No. Area Name Function Description
If there are many counter items, input a keyword in this area, and then the
Counter keyword
1 counter only with the keyword is displayed. Click to clear the input
filtering setting area
keyword.
2 Counter display area Displays the counter types included in this measurement type in a list.
If the measurement type includes the object, THE object list is displayed; if
3 Object display area
the object is not included, the No Object is displayed.
If there are many object items, input a keyword in this area, and then the
Object keyword
4 object type only with the keyword is displayed. Click to clear the typed
filtering setting area
keyword.
Query granularity
5 Currently only the query granularity of 15 minutes is supported.
setting area
2. Click the Time Information tab to go to the time setting dialog box, as shown in Figure
6-5.
Figure 6-5 Performance data query-Time information
3. In Figure 6-5, set the begin time and the end time of a performance measurement task.
Click OK to display the performance measurement data, as shown in Figure 6-6.
6-8

Figure 6-6 Performance Measurement Data
6.4 Exporting Performance Statistics

6.4.1 Exporting Counter Information
Prerequisites
The counter information is queried.
Context
This topic describes how to locally save the counter information.
Steps
1. In the Counter Info View window as shown in Figure 6-7, click . A Save dialog box
6-9

Figure 6-7 Counter Info View
6-10

Figure 6-8 Save
2. In Figure 6-8, set the location and file name to be saved, and click Save to complete
exporting counter information.
6.4.2 Exporting a Dynamic Measurement Object

Prerequisites
The dynamic measurement object is queried.
Context
This topic describes how to locally save the dynamic measurement objection information.
Steps
1. On the Dynamic Measurement Object window, click . A Save dialog box appears,
6-11

Figure 6-9 Save
exporting the dynamic measurement object information.
6.4.3 Exporting the Performance Data

Prerequisites
The performance data are queried.
Context
This topic describes how to locally save the performance data.
Steps
1. In the performance data query result dialog box as shown in Figure 6-10, click . A
Save dialog box appears, as shown in Figure 6-11.
6-12

Figure 6-10 Measurement Information
6-13

Figure 6-11 Save
exporting the performance data.
6-14

Chapter 7
Trace Tools
Table of Contents
Description .................................................................................................................7-1
Logging in to the Trace Tools......................................................................................7-2
Creating a Subscriber Trace Task...............................................................................7-4
Creating a Trace Task Instance ................................................................................7-10
7.1 Description
Terminologies
l Trace Entity
A trace entity refers to the signaling trace objects, including various users, protocols,
services, and interfaces.
l Trace Task
A trace task means the signaling trace originated to the traced entities. The trace task
can be classified as the system task and the client task; the ZXUN PGW system uses
only the client task.
à System task: a task originated by the system itself.
à Client task: a task originated by the signaling trace client (such as the LMT), it
has the same lifetime with the client. When the client exits, the client task ends
and the trace result is reported to the client which originates this trace.
Basic Functions
Currently in the ZXUN PGW product, the LMT provides signaling trace to the data users.
The signaling trace tasks are created according to the International Mobile Subscriber
Identity (IMSI), Mobile Station International Subscriber Directory Number (MSISDN),
Network Access Identifier (NAI), and LNS IP/LAC IP/VRFID of the common users.
Diameter Link Signaling Trace

Currently in the ZXUN PGW product, the LMT provides signaling trace to the Diameter link,
and the signaling trace is created according to the signaling messages of the Diameter
protocol stack.
7-1

7.2 Logging in to the Trace Tools

Prerequisites
Context
The trace tool is a tool for system debugging, maintenance, and observation, which
provides maintenance personnel with accurate and reliable maintenance methods. It is
easy to operate, and provides accurate, reliable and abundant information.
Steps
• On the Daily Maintenance window, double-click the Trace Tools node, the Trace
Tool window appears, as shown inFigure 7-1.
Figure 7-1 Trace Tool
In Figure 7-1, the main window is divided into two parts: the left pane is the function
topology tree, while the right pane is the data display area.
l The root node of the function topology tree is the module name (Trace Tool by
default), the level-2 node is the product alias (XGW by default), the level-3 node
is the sub-NE (it is PGW by default in the ZXUN xGW system), and the level-4
node is the trace entity node.
7-2

Chapter 7 Trace Tools
l Data display area shows the general information of the data reported by the
trace entities in the form of table, and the detailed field information is different for
different entities.
• After creating a signaling trace task, the main window of the signaling trace is as shown
in Figure 7-2.
Figure 7-2 Trace Tool Result Window
In Figure 7-2, the lower area shows the Hint Message and Error Message when
performing the trace task.
Follow-Up Action
On the tool bar, the function of the operation buttons is as described in Table 7-1.
Table 7-1 Introduction to the Tool Bar
Tool Function Description Remarks
Open a history data file Corresponding to the menu Operation >

Open Data File
Cancel all trace tasks Corresponding to the menu Operation >

Stop All Task
Set local client parameters, and set the Corresponding to the menu Operation >
maximum records in the data display Set Client Parameter
area
7-3

Tool Function Description Remarks
Create a signaling trace result -
Save all data in the table to a new file -
Save the selected data to a new file -
Search data in the table according to

-
the keyword
Display the data satisfying the filtering

-
condition in a new window
Set or query the trace condition of a

task -
Start a trace task

-
Stop the current trace task -
Pause or restore the data refreshment

-
in the current table
Show the data table in a full screen -
Query the original code stream of the

-
selected data lines
Query the detailed decoding of the

-
selected data lines
Clear the data in the data table -
Pause or restore the data rolling in the

-
current table
The data table in the data display area can support the following operations.
l Double-click any title bar on the table to re-order the data.
l Right-click any title bar on the table, the prompted menu can define the column to be
displayed.
l Select any line in the table, right-click it, a functional menu prompts.
l Double-click any line of data to open the detailed decoding panel.
l On the decoding panel, use the up & down arrow buttons to switch current data line,
meanwhile, the decoding result is displayed on the decoding panel.
7.3 Creating a Subscriber Trace Task

Prerequisites
7-4


l You have logged in to the Trace Tool properly.
Context
The complete flow for creating the task includes selecting the trace entity node on the
topology tree, creating a signaling trace task by the tool bar or the menu, setting trace
conditions in the Subscriber Trace Trace Tool Task Settings dialog box, and starting the
trace task.
The subscriber trace is to trace all signaling and failure messages occurred during the
subscriber activities.
Steps
1. Create a signaling trace task, using either of the following ways to go to the Subscriber
Trace Trace Tool Task Settings window, as shown in Figure 7-3.
l Double-click Trace Tool > XGW > PGW > Subscriber Trace on the Trace Tool
window.
l Click Trace Tool > XGW > PGW > Subscriber Trace on the Trace Tool window,
and then click the icon on the tool bar.
l Right-click Trace Tool > XGW > PGW > Subscriber Trace on the Trace Tool
window and select Create Task from the prompted shortcut menu.
7-5

Figure 7-3 Subscriber Trace Trace Tool Task Settings (Primary)
In Figure 7-3, the default tab is the Primary tab, and the parameters are described in
Table 7-2.
Table 7-2 Subscriber Trace Trace Tool Task Settings (Primary)
Parameter Description Remarks
Trace Mode objects of the signaling trace, it is Single User Currently the signaling trace is provided
by default. for a single user or multiple users.
Num Type User number type, including IMSI, MSISDN Operations are different when choosing
and LNS IP/LAC IP/VRFID; the default value different number types.
is IMSI. l If choosing IMSI, type the
corresponding IMSI number in
the User Num.
l If choosing MSISDN , type the
corresponding MSISDN number in
the User Num.
l If choosing LNS IP/LAC IP/VRF ID,
type the corresponding IP address
information.
7-6

User Num IMSI numbers corresponded to the traced Click Add to add the IMSI number to the
users Setting Result list; repeat this step to
add more IMSI numbers.
Signaling Trace > Services, protocols, or interface types of the Check or uncheck the checkboxes to
Service Type signaling trace, including all protocols and select or cancel the service type
interface types involved in the whole PS
system.
Fail Observer > Services, protocols, or interface types of the fail Check or uncheck the checkboxes to
Service Type observer, including all protocols and interface select or cancel the service type
types involved in the whole PS system.
Position Setting Means the group and the CPU in the group to Here, the CPU module information is the
be traced CPU ID on the GSU board.
Trace Level Levels of the fail observer, divided as System Select one from the two options: System
Fail and User Fail. Fail and User Fail.
l System Fail means the failure reason
caused by xGW system setting or fault
l User Fail means the failure reason caused
by the users
2. Click the Advance tab, as shown in Figure 7-4.
7-7

Figure 7-4 Subscriber Trace Trace Tool Task Settings (Advance)
In Figure 7-4, parameters are described in Table 7-3.
Table 7-3 Subscriber Trace Trace Tool Task Settings (Advance)
Timing set Sets the start time and end time of a trace task: Selecting Continued means to execute the
l Continued means the valid time of the task is trace from the task is created till the task is
from creating the task to terminating the task terminated. When a user exits the LMT, the
l Timing: if it is selected, set the Starting time running trace tasks created by this user are
and The End of time, and the trace task is valid automatically terminated.
only within this time period.
Saving set Saving methods of the trace task result: Only when Automatic saving is selected,
l Automatic saving means that the system the saving directory can be set by the Saving
saves the result automatically to the specified directory button.
directory and the specified file. If Automatic saving and Save by time
l Save by time interval means the system can interval are all selected, this means to save
save the task result at the interval of 5 minutes, the task result automatically to the specified
15 minutes, and 30 minutes. directory according to the configured time
interval.
7-8

3. After setting the trace conditionclick OK to complete setting the parameters of a trace
task and start the trace task.
When a trace task starts, the Signaling Trace main window becomes as shown in
Figure 7-5. The progress of the trace task is displayed on the Hint Message field.
Figure 7-5 Running a Trace Task
Result
When a trace task is complete, the trace result is displayed in the form of a table at the
data display area.
The meaning of the fields in the data display area is described in Table 7-4.
Table 7-4 Fields in Data Display Area
Field Description
NO Automatically increments according to the sequence that the

background receives the message.
Trace Type Message reporting type: Fail Observer or Signaling Trace
NE Type NE type for the message reporting, PGW by default
Trace Level Level of the fail observer message
Service Type Service type of the reported message
Event Description Event description of the reported message
7-9

Field Description
ID user identification of the reported message
Source IP Source IP address of the reported message
Dest IP Destination IP address of the reported message
Source Job Source JOB identification of the reported message
Dest Job Destination JOB identification of the reported message
Time Time for message reporting, and the unit is 10 millisecond
CPU Number CPU number of the reported message
7.4 Creating a Trace Task Instance

Prerequisites
l You have logged in to the Trace Tool properly.
Context
This topic describes how to create a Diameter link signaling trace task, and perform
signaling trace according to the Diameter link information and the CPU group number of
the PGW.
Steps
1. To create a signaling trace task, use one of the following methods to go to the Diameter
Link Signaling Trace Trace Tool Task Settings dialog box, as shown in Figure 7-6.
l Under Trace Tool > XGW > PGW, double-click Diameter Link Signaling Trace.
l Under Trace Tool > XGW > PGW, select Diameter Link Signaling Trace, and
click the button on the tool bar.
l Under Trace Tool > XGW > PGW, right-click Diameter Link Signaling Trace,
and select Creating task from the prompted shortcut menu.
7-10

Figure 7-6 Trace Tool Task Settings (Primary)
2. In Figure 7-6, select the information of the Diameter link to be traced and its CPU
number.
3. Click the Advance tab, as shown in Figure 7-7.
7-11

Figure 7-7 Diameter Link Signaling Trace Trace Tool Task Settings (Advance)
4. Set the trace time and saving mode in Figure 7-7.

5. Click OK to complete setting the Diameter link signaling trace to go to the trace result
window.
Result
When a trace task is complete, the trace result is displayed in the form of table at the data
display area.
7-12

Chapter 8
Rack Chart Management
Table of Contents
Logging in to the Rack Chart ......................................................................................8-1
Rack Related Operations ...........................................................................................8-3
Board Related Operations ..........................................................................................8-6
8.1 Logging in to the Rack Chart

Prerequisites
Context
The LMT has the rack chart management function. The rack chart provides the query
function to the racks, shelves, and boards in the graphical user interface method, executes
a real-time refreshment, and integrates the function such as operations on boards. The
rack chart identifies the boards in different status using different color blocks, and it can
show alarm information in different levels on the board diagram.
Steps
• On the Daily Maintenance window, double-click the Rack Chart node, the Rack
Chart window appears, as shown in Figure 8-1.
8-1

Figure 8-1 Rack Chart
In Figure 8-1, from left to right, the rack chart management window consists of three
parts:
l Rack ID
Rack ID area shows the rack ID of the ZXUN PGW, starting from rack 0 by default.
l Board Diagram
Board diagram area shows the distribution and slot number of the logical boards
on a ZXUN PGW shelf, wherein, different color blocks indicate the boards at
different status; the number identifies the slot No. of the boards.
l Legend
Legend area shows the correspondence of the color and the alarm level, and the
correspondence of the color and the board operation status.
Warning
When the critical alarms in red color and the faulty boards in red color happen in
the rack chart, handle this as soon as possible, otherwise, the overall service will be
seriously affected.
8-2

Chapter 8 Rack Chart Management
8.2 Rack Related Operations

8.2.1 Querying the Version Information
Prerequisites
l You have logged in to the Rack Chart properly.
Context
Querying the version information provides the users the function to query the version
information of the rack in the rack chart.
Note
When the boards on the ZXUN PGW foreground are upgraded or replaced, use the Query
Version Information function to verify the boards.
Steps
1. Right-click the slot No. area on the Rack Chart window, the shortcut menu as shown
in Figure 8-2 appears.
Figure 8-2 Querying Version Information
2. Select Show Version Info from the prompted shortcut menu, the Show Version Info
dialog box appears, as shown in Figure 8-3.
8-3

Figure 8-3 Query Version Information Result
Figure 8-3 shows the software and hardware information of the ZXUN PGW rack,
including:
l Product name
l Hardware and software version
l System uptime
l BOOTROMM version
l System Memory
l System Flash
l CPU Uptime
l CPU uptime
3. Click Close to complete querying the version information.

8-4

8.2.2 Reloading the System

Prerequisites
Context
Resetting the system provides users the function to reset the whole system.
Warning
System resetting will cause the restart of whole ZXUN PGW shelf and interrupt all data
services. If this operation must be done, we recommend you to do it at the time with
lightest traffic.
Steps
1. Right-click the slot number area on the Rack Chart window, a shortcut menu as shown
in Figure 8-4.
Figure 8-4 System Reloading Command
2. Select Reload System from the prompted shortcut menu, the Reload System dialog
box appears. Select Force to reload system, as shown in Figure 8-5.
8-5

Figure 8-5 Force to reload system
3. Click OK, a confirmation dialog box appears, as shown in Figure 8-6. If it is confirmed
to reset the system, click OK, the system starts to reboot.
Figure 8-6 System Reloading Confirmation
Follow-Up Action
After the system is reset, perform the basic service function test and hardware information
check, so as to prevent service or hardware abnormality.
8.3 Board Related Operations

8.3.1 Querying the Memory and CPU Running Status
Prerequisites
Context
The rack chart management facilitates users to query the running status information of the
CPU and the memory on the board, including the current temperature, the CPU usage,
and the memory usage.
8-6

Steps
1. Right-click the boards to be queried on the Rack Chart window, a shortcut menu
prompts, as shown in Figure 8-7.
Figure 8-7 Right-click Menu
2. Select Show CPU from the prompted shortcut menu, and a Show CPU dialog box
Figure 8-8 Show CPU
3. Select Show Processor Info from the prompted shortcut menu, and the Show
Processor Info dialog box appears, as shown in Figure 8-9.
8-7

Figure 8-9 Show Processor Info
In Figure 8-9, the CPU (corresponding rack, slot number, and CPU number)
temperature, CPU usage, physical memory size, memory free size, and memory
usage are displayed. Wherein, the CPU usage and memory usage can be used to
determine whether the board is overload. For the proper range of the CPU usage and
memory usage, refer to Table 8-1.
Table 8-1 Board CPU Usage and Memory Usage
Board Type CPU Usage Range Memory Usage Range
MPU 10% – 85% Lower than 80%
GSU Lower than 40% Lower than 75%
PFU Lower than 15% Lower than 50%
NoteWhen the board CPU usage or memory usage exceeds a proper operation
range, the ZXUN PGW foreground will report corresponding alarms, such as CPU
overload, high memory usage, and CPU overload.
4. Click Close to complete querying the memory and CPU running status.
8-8

Follow-Up Action
If the ZXUN PGW foreground reports the alarm information such as CPU overload and
memory usage, handle the alarms by referring to the ZXUN xGW eXtendable GateWay
PGW Alarm and Notification Message Reference.
8.3.2 Querying the System Hardware Information

Prerequisites
Context
The rack chart management view provides users with the function to query the basic
hardware information of the board in the rack chart.
Steps
1. On the Rack Chart window, right-click the board to be queried, and select Show
Hardware Info from the prompted shortcut menu. The Show Hardware Info dialog
8-9

Figure 8-10 Show Hardware Info
In Figure 8-10, the hardware information includes the information such as board type,
slot number, CPU number, BOOTROOM version, board physical memory size, FLASH
memory size, board type, EPLD version, and hardware version.
Note
Hardware information of different boards is different.
2. Click Close to complete querying the hardware information.
8-10

8.3.3 Querying Version Information of the Software Set

Prerequisites
Context
The rack chart management view provides users the function to query the software set
version information of the board in the rack chart.
Steps
1. On the Rack Chart window, right-click the board to be queried, and select Show
Software Info from the prompted shortcut menu. The Show Software Info dialog
8-11

Figure 8-11 Show Software Info
In Figure 8-11, the software set information includes the product name, board image
file size, board operation time, board image file loading method, board type, slot No.,
operation system version, and ROSNG version.
Note
Software set information of different boards is different.
2. Click Close to complete querying the software set version information.
8-12

8.3.4 Resetting a Board

Prerequisites
Context
The rack chart management view provides users the function to reset the board (also called
warm start).
Warning
Resetting a board is a dangerous operation, which may interrupt all running services on
the board. If this operation must be done, we recommend you to do it at the time with
minimum services.
Steps
1. On the Rack Chart window, right-click the board to be reset, and select Reload Slot
from the prompted shortcut menu. A dialog box asking whether the reset appears.
2. Click OK to complete resetting the board.
Follow-Up Action
After the board is reset, confirm that the board is properly started using the measures such
as checking the indicators on the front panel, checking the memory, and checking the CPU
running status. When the board is working properly, the indicators are described in Table
8-2.
Table 8-2 Description to Indicators on the Board Panel
Indicator Color Function
Board running indicator; it flashes during proper operation, and the

RUN Green
flashing frequency is 1Hz.
Board alarm indicator; it is on when a fault occurs, and it is off during

ALM Red
proper operation.
Board active indicator; being on means active, while being off means
ACT Green
standby.
Scanning indicator, being on means that the board is at SJTAG

SCAN Green
scanning status.
8-13

Note
To know the detailed function of all indicators on the board, refer to the ZXUN xGW
eXtendable GateWay PGW Hardware Decription.
8.3.5 Switching Over the Active/Standby Boards

Prerequisites
Context
The rack chart management view provides users the function to switch over the
active/standby boards on those 1+1 backup redundancy mode is set. Currently only the
MPU board supports the active/standby switchover.
Caution
Before switching over the active/standby MPU boards, check the operation status of the
active/standby boards, and make sure that the standby board is at proper running status.
Perform this operation at the time with lightest traffic.
Steps
1. On the Rack Chart window, right-click the board to be switched over, and select
Redundancy Switch from the prompted shortcut menu. A dialog box as shown in
Figure 8-12 appears.
Figure 8-12 Force to redundancy switch
8-14

2. If the active/standby boards must be switched, select the Force to redundancy

switch option in Figure 8-12 and click OK.
3. A confirmation dialog box prompts. Click OK to start the switchover.
Follow-Up Action
After the boards are properly switched over, confirm the active board is properly started by
measures such as checking the indicators on the front panel, and querying the memory
and CPU running status.
8-15

8-16

Figures
Figure 1-1 Composition of ZXUN PGW ..................................................................... 1-1
Figure 1-2 Schematic Diagram of the Operation & Maintenance System .................. 1-2
Figure 1-3 Function of the LMT and Communication with the Foreground................. 1-3
Figure 1-4 Choose Local Maintenance Terminal ....................................................... 1-4
Figure 1-5 Login ....................................................................................................... 1-4
Figure 1-6 LMT Main Window ................................................................................... 1-5
Figure 1-7 Choose Config the Environment .............................................................. 1-6
Figure 1-8 Config the Environment of Software......................................................... 1-6
Figure 1-9 Communication Status............................................................................. 1-7
Figure 1-10 Querying System Time........................................................................... 1-9
Figure 2-1 DPI Rule Manager ................................................................................... 2-2
Figure 2-2 Choose .................................................................................................... 2-3
Figure 2-3 DPI Rule Selected ................................................................................... 2-3
Figure 2-4 Choose Ne............................................................................................... 2-4
Figure 2-5 Load DPI Rule File................................................................................... 2-5
Figure 3-1 MML Terminal .......................................................................................... 3-2
Figure 3-2 Result of the Command “?” ...................................................................... 3-3
Figure 4-1 Patrol Management.................................................................................. 4-2
Figure 4-2 System idle time setting ........................................................................... 4-3
Figure 4-3 Right-click a Patrol Item ........................................................................... 4-4
Figure 4-4 Patrol task setting .................................................................................... 4-5
Figure 4-5 Attention .................................................................................................. 4-6
Figure 4-6 Result of executing immediately............................................................... 4-7
Figure 4-7 Patrol result ............................................................................................. 4-8
Figure 4-8 Query condition setting ............................................................................ 4-9
Figure 4-9 Patrol result ........................................................................................... 4-10
Figure 4-10 Query condition setting ........................................................................ 4-11
Figure 4-11 Result of executing immediately ........................................................... 4-12
Figure 4-12 Export file............................................................................................. 4-13
Figure 4-13 Patrol result ......................................................................................... 4-13
Figure 5-1 Alarm Management.................................................................................. 5-2
Figure 5-2 Alarm Details ........................................................................................... 5-3
I
Figure 5-3 Current Alarm RealTime Monitor.............................................................. 5-4

Figure 5-4 Alarm Details ........................................................................................... 5-5
Figure 5-5 History Alarm RealTime Monitor............................................................... 5-7
Figure 5-6 Notify RealTime Monitor........................................................................... 5-8
Figure 5-7 Current Alarm Query (Alarm Code) ........................................................ 5-10
Figure 5-8 Querying Current Alarms (Time/Type/Level) .......................................... 5-11
Figure 5-9 Querying Current Alarms (Alarm Position) ............................................. 5-12
Figure 5-10 Querying Current Alarms (Fuzzy Query) .............................................. 5-13
Figure 5-11 Querying Current Alarms (Query Result) .............................................. 5-14
Figure 5-12 History Alarm Query (Alarm Code)....................................................... 5-15
Figure 5-13 History Alarm Query (Alarm Time/Type) ............................................... 5-16
Figure 5-14 History Alarm Query (Alarm Position)................................................... 5-17
Figure 5-15 History Alarm (Fuzzy Query) ................................................................ 5-18
Figure 5-16 History Alarm Query (Query Result) ..................................................... 5-19
Figure 5-17 Notify Query (Alarm Code) ................................................................... 5-20
Figure 5-18 Notify Query (Time/Type/Level)............................................................ 5-21
Figure 5-19 Notify Query (Alarm Position)............................................................... 5-22
Figure 5-20 Notify Query (Fuzzy Query).................................................................. 5-23
Figure 5-21 Notify Query (Query Result) ................................................................. 5-24
Figure 5-22 RealTime Monitor................................................................................. 5-25
Figure 5-23 Select CPU .......................................................................................... 5-26
Figure 5-24 RealTime Monitor Result...................................................................... 5-27
Figure 5-25 Save .................................................................................................... 5-29
Figure 5-26 Filter Condition..................................................................................... 5-30
Figure 5-27 Display by Filtering Condition-Example 1 ............................................. 5-31
Figure 5-28 Synchronization Success ..................................................................... 5-32
Figure 6-1 Performance Data View ........................................................................... 6-3
Figure 6-2 Counters in RAUIUS Signal Measurement ............................................... 6-5
Figure 6-3 Performance data query-query set ........................................................... 6-7
Figure 6-4 Performance data query-Area Explanation............................................... 6-7
Figure 6-5 Performance data query-Time information ............................................... 6-8
Figure 6-6 Performance Measurement Data ............................................................. 6-9
Figure 6-7 Counter Info View .................................................................................. 6-10
Figure 6-8 Save ...................................................................................................... 6-11
Figure 6-9 Save ...................................................................................................... 6-12
II
Figures
Figure 6-10 Measurement Information .................................................................... 6-13

Figure 6-11 Save .................................................................................................... 6-14
Figure 7-1 Trace Tool................................................................................................ 7-2
Figure 7-2 Trace Tool Result Window........................................................................ 7-3
Figure 7-3 Subscriber Trace Trace Tool Task Settings (Primary) ............................... 7-6
Figure 7-4 Subscriber Trace Trace Tool Task Settings (Advance).............................. 7-8
Figure 7-5 Running a Trace Task .............................................................................. 7-9
Figure 7-6 Trace Tool Task Settings (Primary)......................................................... 7-11
Figure 7-7 Diameter Link Signaling Trace Trace Tool Task Settings
(Advance) ............................................................................................ 7-12
Figure 8-1 Rack Chart............................................................................................... 8-2
Figure 8-2 Querying Version Information................................................................... 8-3
Figure 8-3 Query Version Information Result ............................................................ 8-4
Figure 8-4 System Reloading Command................................................................... 8-5
Figure 8-5 Force to reload system ............................................................................ 8-6
Figure 8-6 System Reloading Confirmation............................................................... 8-6
Figure 8-7 Right-click Menu ...................................................................................... 8-7
Figure 8-8 Show CPU ............................................................................................... 8-7
Figure 8-9 Show Processor Info................................................................................ 8-8
Figure 8-10 Show Hardware Info ............................................................................ 8-10
Figure 8-11 Show Software Info .............................................................................. 8-12
Figure 8-12 Force to redundancy switch ................................................................. 8-14
III
Figures

Tables
Table 1-1 Description to Parameters in Config the Environment of Software ............. 1-7
Table 4-1 Description of Patrol Task Setting .............................................................. 4-5
Table 5-1 Alarm Details............................................................................................. 5-4
Table 5-2 CPU Utilization and Memory Utilization of the Boards.............................. 5-28
Table 6-1 Counter Info View...................................................................................... 6-5
Table 6-2 Performance data query-Area Explanation ................................................ 6-8
Table 7-1 Introduction to the Tool Bar........................................................................ 7-3
Table 7-2 Subscriber Trace Trace Tool Task Settings (Primary)................................. 7-6
Table 7-3 Subscriber Trace Trace Tool Task Settings (Advance) ............................... 7-8
Table 7-4 Fields in Data Display Area ....................................................................... 7-9
Table 8-1 Board CPU Usage and Memory Usage ..................................................... 8-8
Table 8-2 Description to Indicators on the Board Panel ........................................... 8-13
V
Tables

Glossary
CC
- Cumulative Counter
CORBA
- Common Object Request Broker Architecture
DER
- Discrete Event Registration
DPI
- Deep Packet Inspection
EMS
- Network Element Management System
EPLD
- Erasable Programmable Logic Device
FTP
- File Transfer Protocol
IMSI
- International Mobile Subscriber Identity
LAC
- Location Area Code
LMT
- Local Maintenance Terminal
LNS
- L2TP Network Server
MPU
- Management Process Unit
MSISDN
- Mobile Station International Subscriber Directory Number
NAI
- Network Access Identifier
NMS
- Network Management System
PC
- Personal Computer
QoS
- Quality of Service
VII
SI
- Status Inspection
SJTAG
- System Joint Test Action Group
SNMP
- Simple Network Management Protocol
TELNET
- Telecommunication Network Protocol
VIII

SJ-20101008113605-008 - ZXUN XGW (V4.10.20) EXtendable GateWay PGW LMT Operation Guide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SJ-20101008113605-008 - ZXUN XGW (V4.10.20) EXtendable GateWay PGW LMT Operation Guide

Hochgeladen von

Copyright:

Verfügbare Formate

ZXUN xGW

Revision No. Revision Date Revision Reason

R1.0 2010-12-03 First Edition

Serial Number: SJ-20101008113605-008

Publishing Date: 2010-12-03(R1.0)

Chapter 2 DPI Rule Manager ..................................................................... 2-1

Chapter 3 MML Terminal ............................................................................ 3-1

Chapter 4 Patrol Management................................................................... 4-1

Chapter 5 Alarm Monitoring and Management........................................ 5-1

Chapter 6 Performance Statistics and Management............................... 6-1

Chapter 7 Trace Tools ................................................................................ 7-1

Chapter 8 Rack Chart Management .......................................................... 8-1

Prerequisite Skill and Knowledge

What Is in This Manual

Glossary Lists the glossary in this manual.

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before

Tip: Indicates a suggestion or hint to make things easier or more productive

1.1 Introduction to the OMM System

Figure 1-1 Composition of ZXUN PGW

Description to the Operation & Maintenance System

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

Figure 1-2 Schematic Diagram of the Operation & Maintenance System

Local Maintenance Terminal

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

The LMT has the following functions.

1.2 Logging in to the LMT

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

l Run the program with the relative path as \ums-clnt\bin\run.exe.

Figure 1-4 Choose Local Maintenance Terminal

The Daily-Maintenance Login dialog box appears as shown in Figure 1-5.

Figure 1-5 Login

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

Figure 1-6 LMT Main Window

1.3 Relevant Operations

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

Figure 1-7 Choose Config the Environment

Figure 1-8 Config the Environment of Software

Parameters in Figure 1-8 are described in Table 1-1.

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

Table 1-1 Description to Parameters in Config the Environment of Software

Parameter Meaning Example

Local IP IP address of the LMT connected to the ZXUN PGW

Remote IP IP address of the port Console on the Management

Module Module No. of the LMT, unrepeatable with other module

SNMP Config Select the corresponding SNMP version It is SNMPv2c by

2. Type corresponding parameters in Figure 1-8 and click OK to complete configuring

Figure 1-9 Communication Status

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

Parameters in Figure 1-9 are described as follows:

1.3.2 Querying the System Time

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

Figure 1-10 Querying System Time

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

2.1 Logging in to the DPI Rule Manager

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential

Figure 2-1 DPI Rule Manager

2.2 Loading the DPI Rule

SJ-20101008113605-008|2010-12-03(R1.0) ZTE Proprietary and Confidential