EzView NMS User's Manual V3.10 PDF

1
EzView
2
EzView
NMS User’s Manual
Beijing Huahuan Electronics Co. Ltd

Nov.2018
3
Copyright Notice
The intellectual property rights of all parts of this product, including this manual
and accessories etc., are owned by Beijing Huahuan Electronics Co., Ltd. (Beijing
Huahuan for short). Without prior written consent of Beijing Huahuan, no part of this
document may be reproduced or transmitted in any form or by any means. The
information in this document, including product specifications and information, is
subject to change without notice. For information related, please consult Beijing
Huahuan.
Copyright © Beijing Huahuan Electronics Co., Ltd. 2014 All rights reserved
Product Name: EzView NMS
Manual Version: 3.10
Release Date: Nov. 2018
BEIJING HUAHUAN ELECTRONICS Co., LTD.
Address: No.26, Shangdi 6th Street, Haidian District, Beijing, 100085
P.R. China
Tel: +86-400-810-8580, +86-10-52046188
Fax: +86-10-52046288
Website: www.huahuan.com
E-mail: support@huahuan.com
i
User's Manual
EzView NMS Contents
Contents
Contents.....................................................................................................................i
List of Figures......................................................................................................... x
List of Tables......................................................................................................... xi
1 Software Overview............................................................................................. 1
1.1 EzView Network Element Management Software provides the following functions：... 1
1.2 EzView Specification......................................................................................................... 2
1.2.1 System Structure....................................................................................................... 3
1.2.2 Topology Management Function.............................................................................. 3
1.2.3 Fault Management Function..................................................................................... 4
1.2.4 Security Management Function................................................................................ 4
1.2.5 Trail Management..................................................................................................... 4
1.2.6 Multiple Report Management...................................................................................5
1.2.7 High Efficient, Low Demand....................................................................................5
1.3 EzView Architecture.......................................................................................................... 5
1.4 EzView Communication Protocol......................................................................................6
1.5 EzView Operation Environment........................................................................................ 6
2 Software Installation.......................................................................................... 7
2.1 Before installating EzView, please confirm the following items:......................................7
2.2 Installation of Software in One PC.................................................................................... 7
2.3 Installation of Independent Server Terminal......................................................................8
2.4 Installation of Independent Client Terminal.......................................................................8
3 Interface Description........................................................................................12
3.1 Home Page....................................................................................................................... 12
3.2 View................................................................................................................................. 12
Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. i

User's Manual
Contents EzView NMS ii
3.2.1 Topology View........................................................................................................ 13

3.2.2 NE Panel................................................................................................................. 14
3.2.3 NE Explorer............................................................................................................ 15
3.2.4 Trail View................................................................................................................15
3.2.5 Custom View...........................................................................................................16
3.3 Main Menu....................................................................................................................... 17
3.3.1 File.......................................................................................................................... 17
3.3.2 View........................................................................................................................ 18
3.3.3 Config..................................................................................................................... 20
3.3.4 System Management...............................................................................................21
3.3.5 Fault........................................................................................................................ 23
3.3.6 Performance............................................................................................................ 24
3.3.7 Trail.........................................................................................................................26
3.3.8 Diagnosis Task........................................................................................................ 30
3.3.9 Report......................................................................................................................31
3.3.10 Tools......................................................................................................................33
3.3.11 Help.......................................................................................................................34
3.4 Main Toolbar.................................................................................................................... 35
4 Operation Guide............................................................................................... 37
4.1 Start the System................................................................................................................37
4.1.1 Initialize or Recover Database................................................................................ 37
4.1.2 Start Server............................................................................................................. 39
4.1.3 Start Client.............................................................................................................. 41
4.2 Close System....................................................................................................................42
4.2.1 Close Client.............................................................................................................42
4.2.2 Close Server............................................................................................................42
4.3 Management of H0FL-1101S4A......................................................................................43
4.3.1 Add NE................................................................................................................... 43
4.3.2 Initialize NE............................................................................................................44
4.3.3 Configuring NE Communication Parameters......................................................... 46
4.3.4 Query or Configuration Data on NE.......................................................................47
4.3.5 Monitor NE Alarms................................................................................................ 49
5 Security Management...................................................................................... 51
5.1 Add NMS User.................................................................................................................51
ii Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

iii
User's Manual
EzView NMS Contents
5.2 Add NMS User Group......................................................................................................53

5.3 Add Operation Set............................................................................................................ 53
5.4 Add NE Set.......................................................................................................................54
5.5 Add Subnet Set.................................................................................................................54
5.6 E.g. Add User and Assign Permission..............................................................................55
5.7 Client Access Control.......................................................................................................62
5.8 Password Dictionary........................................................................................................ 62
5.9 Security Tactics................................................................................................................ 62
6 Topology Management.................................................................................... 63
6.1 EzView Topology.............................................................................................................63
6.2 Add NE.............................................................................................................................64
6.3 Config NE Data................................................................................................................64
6.4 Add Board........................................................................................................................ 65
6.5 Copy NE Configuration Data...........................................................................................65
6.6 Add Link...........................................................................................................................65
6.7 Add Topology Subnet.......................................................................................................65
6.7.1 Topology Discovery................................................................................................66
6.7.2 SNMP Topology Discovery.................................................................................... 68
6.7.3 DCN Topology Discovery...................................................................................... 69
6.8 Modify Network Topology...............................................................................................71
6.9 Example: Add NE and Configuration.............................................................................. 72
6.10 Example: Add Subnet.....................................................................................................75
7 System Management........................................................................................ 77
7.1 Browse Log...................................................................................................................... 77
7.2 Log Statistics....................................................................................................................77
7.3 DCN Management........................................................................................................... 78
7.3.1 Gateway NE............................................................................................................78
7.3.2 Network Element.................................................................................................... 78
7.3.3 SNMP......................................................................................................................79
7.3.4 Proxy Configuration............................................................................................... 79
7.3.5 Proxied NE..............................................................................................................80
7.3.6 Serial Interface Monitor Config of H5002............................................................. 80
7.3.7 Serial Monitor......................................................................................................... 80
7.3.8 NMNAT Configuration...........................................................................................80
Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. iii

User's Manual
Contents EzView NMS iv
7.3.9 NAT Mapping NE................................................................................................... 81

7.4 Adapter Management....................................................................................................... 81
7.5 Database Management..................................................................................................... 82
7.5.1 Data Dump.............................................................................................................. 82
7.5.2 Data Export............................................................................................................. 82
7.6 Schedule Task Management.............................................................................................83
7.7 System Parameter Configuration..................................................................................... 83
7.8 Naming Rules Configuration........................................................................................... 84
8 Performance Management.............................................................................. 85
8.1 SDH Performance Management...................................................................................... 85
8.1.1 Performance Monitoring Concepts.........................................................................85
8.1.2 Browse Performance...............................................................................................89
8.1.3 Customizing Performance Threshold Template......................................................92
8.1.4 Setting Performance Threshold of Specified Board............................................... 92
8.1.5 Enable/Disable Performance Monitoring............................................................... 93
8.1.6 Dumping Performance............................................................................................ 95
8.1.7 Resetting Performance Register..............................................................................97
8.2 MPLS Performance Statistics.......................................................................................... 97
8.2.1 Performance Monitor Manage................................................................................ 97
8.2.2 Check History Data...............................................................................................101
8.2.3 Current Performance.............................................................................................102
8.2.4 History Performance............................................................................................. 103
8.2.5 Performance Monitor Settings.............................................................................. 104
8.2.6 Performance Monitor Manage.............................................................................. 105
8.2.7 Performance Schedule Strategy Manage.............................................................. 106
8.2.8 Performance Template Manage............................................................................ 107
8.2.9 Browse MPLS History Performance.................................................................... 109
8.2.10 MPLS Flow Statistic........................................................................................... 110
8.3 RMON Flow Management............................................................................................. 111
8.3.1 Flow Monitor Task Management.......................................................................... 111
8.3.2 Browse Flow Record.............................................................................................112
8.3.3 Browse Over Threshold Record............................................................................113
9 Fault Management.......................................................................................... 115

9.1 Basic Concepts............................................................................................................... 115
iv Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

v
User's Manual
EzView NMS Contents
9.1.1Alarm Reporting Process....................................................................................... 115

9.2 Alarms Synchronization................................................................................................. 118
9.2.1 Synchronizing Specified NE Current Alarms....................................................... 118
9.2.2 Synchronizing NMS Current Alarms....................................................................118
9.3 Browse Alarms............................................................................................................... 118
9.3.1 Browse Alarms in Specified Time Period.............................................................118
9.3.2 Browse Current Alarms.........................................................................................118
9.3.3 Browse Current Alarms of Specified Level.......................................................... 119
9.3.4 Browse Current Alarms of Specified NE..............................................................119
9.3.5 Browse NMS Current Alarms...............................................................................119
9.3.6 Browse Current Alarms of SDH Trails................................................................. 119
9.3.7 Browse History Alarms.........................................................................................120
9.3.8 Browse Abnormal Events..................................................................................... 120
9.3.9 Browse Current Alarms Statistics......................................................................... 120
9.3.10 Browse History Alarms Statistics....................................................................... 121
9.4 Check Channel Alarms Suppression.............................................................................. 122
9.5 Customizing Alarms Attribute Template........................................................................122
9.6 Alarms Suppression........................................................................................................123
9.7 NM Alarms Attribute Configuration.............................................................................. 123
9.8 Alarm Level Adjustment................................................................................................ 124
9.9 Port QoS......................................................................................................................... 124
9.10 NE Alarms Storage Configuration............................................................................... 124
9.11 Dumping Alarms.......................................................................................................... 125
9.12 Alarms Function Switch...............................................................................................126
9.13 Alarm Poll Config........................................................................................................ 127
9.14 Remote Alarm Notification.......................................................................................... 129
9.14.1 Communication Parameter Config..................................................................... 130
9.14.2 Information Config............................................................................................. 133
9.14.3 Set Remote Notification Rules........................................................................... 134
10 Report Management..................................................................................... 140

10.1 Network Data Report................................................................................................... 140
10.2 Transmission Resource Statistics Report..................................................................... 141
10.3 Board Information Report............................................................................................ 141
10.4 Slot Information Report............................................................................................... 142
Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. v

User's Manual
Contents EzView NMS vi
10.5 Slot Count Report.........................................................................................................142

10.6 Board Count Report..................................................................................................... 143
10.7 Rack Information Report..............................................................................................143
10.8 Shelf Information Report............................................................................................. 144
10.9 Fiber/Cable Connection Report....................................................................................144
10.10 Lower Order Cross-connections Resource Report.....................................................144
10.11 Occupied Port Information Report............................................................................. 145
10.12 Optical Module Information Report...........................................................................145
10.13 VC12 Remote Connection Information Report......................................................... 146
10.14 Remote Equipment Information Reports................................................................... 147
10.15 Port Resource Report................................................................................................. 147
10.16 Port Resource Statistic Report................................................................................... 148
10.17 Ne Exchange Resource Report...................................................................................148
10.18 Link Bandwidth Report..............................................................................................149
10.19 Tunnel and PW Count Report.................................................................................... 149
10.20 Channel Resource Statistics....................................................................................... 150
11 SDH Trail Management...............................................................................152

11.1 Theory Description.......................................................................................................153
11.2 Principles of Creating Trail.......................................................................................... 154
11.3 Trail View Customization.............................................................................................154
11.4 SDH Trail Creation.......................................................................................................156
11.4.1 Non-SNCP Tail Creation.....................................................................................156
11.4.2 SNCP Trail Creation........................................................................................... 158
11.4.3 Bulk SDH Trail Creation.................................................................................... 161
11.5 SDH Trail Management............................................................................................... 163
11.5.1 Browse SDH Trail...............................................................................................163
11.5.2 Deactivate SDH Trail.......................................................................................... 164
11.5.3 Delete SDH Trail.................................................................................................165
11.5.4 Lock SDH Trail...................................................................................................166
11.6 Search SDH Trail......................................................................................................... 167
11.7 SDH Discrete Service Management.............................................................................168
11.8 64K Trail Creation........................................................................................................170
11.8.1 64K Tail Creation................................................................................................170
11.9 64K Trail Management.................................................................................................171
vi Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

vii
User's Manual
EzView NMS Contents
11.9.1 Browse 64K Trail................................................................................................171

11.9.2 Inactivate 64K Trail............................................................................................ 172
11.9.3 Delete 64K Trail..................................................................................................173
11.10 Search 64K Trail.........................................................................................................174
11.11 Customer Management...............................................................................................175
11.11.1 Create Customers.............................................................................................. 175
11.11.2 Configure Customer of Trails............................................................................176
12 Ethernet Trail Management........................................................................ 178

12.1 Theory Description.......................................................................................................179
12.2 Principles of Creating Trail.......................................................................................... 180
12.3 Service Management Process.......................................................................................180
12.4 Related Concepts..........................................................................................................182
12.4.1 Tunnel Introduction.............................................................................................182
12.4.2 Tunnel Protection Group Introduction................................................................184
12.4.3 PWE3 Introduction............................................................................................. 186
12.4.4 VPLS Introduction.............................................................................................. 187
12.5 Automatic Search IP Service........................................................................................188
12.6 Deploy Tunnel..............................................................................................................191
12.6.1 Create A Piece of Tunnel.................................................................................... 191
12.6.2 Create Tunnels in Bulk....................................................................................... 194
12.6.3 Modify Tunnel.................................................................................................... 196
12.6.4 Demolish Tunnel.................................................................................................198
12.6.5 Delete Tunnel......................................................................................................199
12.6.6 Create Tunnel Protection Group......................................................................... 200
12.6.7 Execute Tunnel Protection Group Switch...........................................................201
12.6.8 Demolish Tunnel Protection Group.................................................................... 202
12.6.9 Delete Tunnel Protection Group......................................................................... 203
12.7 Deploy PWE3 Service..................................................................................................205
12.7.1 Create A Piece of ETH Service...........................................................................205
12.7.2 Create ETH Service in Bulk............................................................................... 206
12.7.3 Create CES Service.............................................................................................208
12.7.4 Modify PWE3 Service........................................................................................ 212
12.7.5 Demolish PWE3 Service.................................................................................... 214
12.7.6 Delete PWE3 Service..........................................................................................215
Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. vii

User's Manual
Contents EzView NMS viii
12.8 Deploy VPLS Service.................................................................................................. 216

12.8.1 Create VPLS Service.......................................................................................... 216
12.8.2 Modify VPLS Service.........................................................................................221
12.8.3 Demolish VPLS Service..................................................................................... 227
12.8.4 Delete VPLS Service.......................................................................................... 228
12.9 Deploy Convergence Service....................................................................................... 229
12.9.1 Create A Piece of Etree Service.......................................................................... 229
12.9.2 Modify Etree Service.......................................................................................... 232
12.9.3 Demolish Etree Service...................................................................................... 235
12.9.4 Delete Etree Service............................................................................................235
13 Synchronization and Data Management..................................................237

13.1 Synchronize NE Time.................................................................................................. 237
13.2 Synchronize Current Alarm..........................................................................................239
13.2.1 Synchronize Alarms of the Whole Network....................................................... 239
13.2.2 Synchronize Alarm of a Specific NE..................................................................240
13.2.3 Manage NE Configuration Data......................................................................... 240
13.2.4 Upload and Download NE Configuration Data.................................................. 242
13.2.5 Copy NE Configuration Data............................................................................. 243
13.2.6 Initialize NMS-side Data.................................................................................... 244
14 Breakdown Maintenance.............................................................................246
14.1 Check Network Communication Status....................................................................... 246
14.2 Loopback......................................................................................................................247
14.2.1 SDH Interface Loopback.................................................................................... 247
14.2.2 PDH Interface Loopback.................................................................................... 248
14.3 Execute Protection Switching...................................................................................... 249
14.4 Configure Diagnosis Tasks...........................................................................................251
14.4.1 Configure Port Diagnosis Task........................................................................... 251
14.4.2 Configure SDH Trail Diagnosis Task................................................................. 256
14.4.3 Task Management............................................................................................... 260
14.4.4 Configure 64K Trail Diagnosis...........................................................................261
14.4.5 64K Diagnosis Task Management...................................................................... 263
15 Routine Maintenance................................................................................... 264

15.1 Schedule Backup..........................................................................................................264
viii Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

ix
User's Manual
EzView NMS Contents
15.1.1 Regular Database Backup................................................................................... 264

15.1.2 NE Schedule Backup.......................................................................................... 266
15.1.3 NTP Server Time Synchronization..................................................................... 268
15.2 (Optional) “Run” to start a task.Check Networkwide maintenance status.................. 270
15.2.1 Check loopback status........................................................................................ 270
15.2.2 Steps....................................................................................................................271
15.2.3 Check laser status of optical ports...................................................................... 271
15.2.4 Check alarm suppression status of channels.......................................................273
15.2.5 Check alarm reversion status of channels...........................................................274
15.3 Check NM Operation Log............................................................................................275
16 Software Management................................................................................. 276

16.1 Query Software Information........................................................................................ 276
16.2 Software Update...........................................................................................................277
16.2.1 Proprietary Protocol Update............................................................................... 277
16.2.2 FTP Update......................................................................................................... 278
16.2.3 TFTP Update.......................................................................................................280
16.3 Software Backup.......................................................................................................... 281
17 DHCP Zero Configurations........................................................................ 283

17.1 Brief Introduction of Zero Configurations...................................................................283
17.2 DHCP Auto Discovery of Remote NE.........................................................................284
17.2.1 Configure DHCP Server..................................................................................... 284
17.2.2 Configure Domain.............................................................................................. 285
17.2.3 Start DHCP Function of the Device....................................................................286
17.2.4 Automatically Add NE........................................................................................286
17.3 Modify IP Address of Remote NE............................................................................... 287
18 North Interface Configuration................................................................... 288

18.1 General Parameters Configuration...............................................................................288
18.2 Alarm Filter.................................................................................................................. 289
Appendix Terms and Abbreviations..............................................................292
Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. ix

User's Manual
Contents EzView NMS x
List of Figures
Figure 2-1 Client on-line installation Web login page............................................................ 9
Figure 2-2 Client on-line installation guide.......................................................................... 10
Figure 2-3 The client login page........................................................................................... 11
Figure 12-1 MPLS Tunnel in MPLS network..................................................................... 183
x Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

xi
User's Manual
EzView NMS Contents
List of Tables
Table 3-1 File menu...............................................................................................................17
Table 3-2 View menu............................................................................................................. 18
Table 3-3 Config menu.......................................................................................................... 20
Table 3-4 System Management menu....................................................................................21
Table 3-5 Fault menu............................................................................................................ 23
Table 3-6 Performance menu................................................................................................ 24
Table 3-7 Trail menu............................................................................................................. 26
Table 3-8 Diagnosis...............................................................................................................30
Table 3-9 Report menu.......................................................................................................... 31
Table 3-10 Tool menu............................................................................................................ 33
Table 3-11 Help menu............................................................................................................34
Table 3-12 Main toolbar........................................................................................................ 35
Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. xi

1
User's Manual
EzView NMS 0Contents
1 Software Overview
EzView Network Element Management Software is specially designed by

our company for management of various transmission equipment and
terminal equipment manufactured, including MSTP equipment, SDH
transmission equipment, PDH transmission equipment, and interface
converter etc.
It is based on C/S schema, and its GUI both in Chinese and English is
adopted which is easy to learn and operate, and has clear and straight
forward alarm indications. The software is an important tool for daily
maintenance and testing of network and equipment.
1.1 EzView Network Element Management

Software provides the following functions：
1. Topology Management ： Display network topology structure with
graphic mode. Organize and manage various network nodes and
connection between them.
2. Fault Management：Collect and manage alarm information reported by

all network equipment of Beijing Huahuan Electronics Co., Ltd. Also
provide functions like query, filter, count, transmitting and phonic
alarm.
Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. 1

User's Manual
0Contents EzView NMS 2
3. Performance Management ： Provide SDH performance management

function. Through EzView, the user may query all interior history
register value of the NE.
4. Security Management：Support multi administration accounts，provide

authorized divisional security management function. Detailed
system/equipment operation log is convenient to control operation
purview.
5. Log Management ： Completed log management includes system

operation log, equipment operation log, and system event
performance management function in order to track the status and
maintain system.
6. Trail management: Allow to create, search, and manage the end-to-end

trails in the way of graphical wizards. It is greatly simplifies the SDH
services configuration, to reduce the error probability of operation.
7. Report management: Supports multiple reports, which is convenient

for the user to inquire and save management information in time.
8. Software management: supports query of NE software version and

FPGA version, and NE software can be updated by various ways.
9. DHCP autodiscovery: through configuring DHCP server, NE will

automatically report the type and ip address of the device to the NMS,
and then after receiving the report, NMS will automatically add the
NE, realizing autodiscovery of NE.
Moreover, EzView Network Element Management Software provides

network configuration management and element configuration
management.
1.2 EzView Specification

At present, management capability of EzView covers a complete set of
equipment manufactured by our company, i.e. all our equipment can be
2 Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

3
User's Manual
managed in a centralized manner under the same environment, so as to

save user investment in manpower and material resources as well as
management costs.
EzView has the following main features：
1.2.1 System Structure

1. EzView Network Element Management Software adopts three layers
of distributed system structure “data base ---- server ---- client”.
According to your need, it can be deployed in different way. It much
better than traditional structure “database ---- application system”.
2. Supports SNMP.
3. Supports MySQL.
1.2.2 Topology Management Function

Monitored equipment constitute several ring network or chain network,
each of them called a subnet, and own an exact subnet address. Only one
node in each subnet connected to the console. The other subnets and
equipment can be monitored and managed through the transmission
channel across the network (domain).
The EzView supports:
1. Network Topology layout management, e.g. tree, ring, star topology.
2. Set up network topology view by operator. The user can establish

topology node and various connections between these nodes through
topology management.
3. Create a logical subnet manually, topological node can be classified

into subnets, convenient management. Support multiple subnet nested
created to meet the various needs.
4. Prompt search and orientation of managed node according to IP

address or the name of node.
5. Provide network topology tree view.

User's Manual
1.2.3 Fault Management Function

1. Support management of alarm information reported by all models
from Beijing Huahuan Electronics Co., Ltd.
2. Real time monitoring the status of every node and refurbish view.
3. Monitoring network occurred failure currently and real time renew

network node faulty status.
4. Reporting completed fault information and exact fault orientation.
5. Powerful alarm query function based on one condition like alarm level,
alarm time and alarm source or based on some of these conditions.
6. Different alarm is represented by different colors. EzView supports

user-defined color.
7. EzView has also provided the multimedia sound warning function.

When alarm occurs, users may hear different sounds that are
previously defined.
1.2.4 Security Management Function

1. Decentralized and regional security management can realize
authorization for different users to manage different equipment.
2. Monitoring and tracking operators’ work status through detailed user

operation logs and system operation logs.
1.2.5 Trail Management

1. The use of trail creation function can configure the VC12, VC3, VC4
level of SDH services quickly and easily just specify the source and
sink, EzView route calculation and configuration can be done
automatically on each NE, simplifying the SDH service configuration.
2. The trail search function that will search all the SDH service of
network elements which is on NMS. Trail service classified into trail

5
User's Manual
service management, other service classified into discrete service

management.
3. Trail service management allows you to activate, activate or delete

trails. Supports to query alarm information and trail customer
information.
4. Client Management supports to create a customer which is bind to a

trail. It is convenient in checking or managing the service of the
customer.
1.2.6 Multiple Report Management

1. Supports multiple reports, including entire network data report, cable
relational report, card information report, low-level cross resource
statistical reports etc.
2. Varieties of resource can be query intuitively, and supports batch

operation on the statistical resources.
1.2.7 High Efficient, Low Demand

Supports all Windows platform (Windows 7, Windows XP, Windows 2008
and etc.) and Linux platform.
1.3 EzView Architecture

EzView uses three-layer distributed structure “data base ----server ----
client”:
1. Database: It adopts MySQL data base management system and it is in

charge of memory administration information.
2. EzView Server: it performs various system services. Receiving the

event reporting, allocation command and data query request.
Accomplishing various transaction processing logics and providing
interface for other system.

User's Manual
3. Client（GUI），submitting service request and display information.
The three-layer distributed structure with distinct management level can

flexibly deploy according to practical application and network size, which
has incomparable advantages when compared to traditional “database
----application system” structure.
Two methods will be used to deploy in the actual working: distributed

deployment and standalone deployment. Through correct operation and
installation of the program, the above two methods can be installed and
deployed.
1.4 EzView Communication Protocol

EzView adopts two types monitoring method: network interface
monitoring and serial port monitoring.
Network interface monitoring adopts SNMP protocol or MSDH protocol,

while serial port monitoring adopts MSDH protocol or TABS protocol.
1.5 EzView Operation Environment

Hardware Environment:
Server: CPU Dual-core 4G or above; Memory: 8G or above.
Client: CPU Dual-core 1.5G or above; Memory: 2G or above.
Software Environment:
Sever: Windows server 2008R2 or above;
Client: Windows 7 or above

7
User's Manual
2 Software Installation
2.1 Before installing EzView, please confirm the

following items:
1. Before installing EzView, please confirm EzView has not been
installed before in your computer. If it has been installed already,
please uninstall in advance.
2. Before installation EzView, please confirm MySQL database has not

been installed before in your computer. If it has been installed already,
please uninstall in advance.
3. If your computer has installed network safety software, e.g. Norton

Internet Security, please break off the software during installation
process in order to install EzView properly. Please start network
security software again after installation.
2.2 Installation of Software in One PC

Under this mode, client terminal, server and database are deployed in the
same computer. This mode is good for small network and less network
nodes. Comparatively, this mode is the most economic method, but
requires higher of the configuration of the host system.

User's Manual
1. MySQL software should be installed before the installation of Server.

The username of MySQL system is root, the password is
Admin_123456 (mysql passward). Please choose “utf8” as language
choice and meanwhile create environment variables. See detailed
installation introductions in MySQL Server Installation
Instructions.doc.
2. During installation, you can choose “Complete”, and then continue to

the next step.
3. After installation, before running the EzView server, you must use the
database management tools to initialize MySQL database, or EzView
will not work.
2.3 Installation of Independent Server Terminal

1. MySQL software and Java runtime should be installed before
installation Server. The username of MySQL system is root; the
password is Admin_123456 as well. Please choose “utf8” as language
choice and meanwhile create environment variables. See detailed
installation introductions in MySQL Server Installation
Instructions.doc.
2. During Server installation, you can choose “Server”, and then

continue to the next step.
3. After installation, before running the EzView server, you must use the
database management tools to initialize MySQL database, or EzView
will not work.
2.4 Installation of Independent Client Terminal

1. To install Client, user does not need to install MySQL database
software.

9
User's Manual
2. During client installation, you can choose “Client”, and then continue
to the next step.
3. Client on-line installation
1) To enter the Client on-line installation page by logging in

http://Server IP:8070/cin. As shown in Figure 2-1.
Figure 2-1 Client on-line installation Web login page
2) To choose the client language according to the server; check

whether the JRE is installed to the computer, if not, please click
the “Install JRE” button to install the JRE according to the
wizard; If you have installed the JRE, please enter the
verification code, and then directly click “Set up” to start the
client installation guide. As shown in Figure 2-2.

User's Manual
Figure 2-2 Client on-line installation guide
3) To complete the client online installation according to the client

installation guide. When the client login page appears, you can
modify the server content and complete the client login. As
shown in Figure 2-3.

11
User's Manual
Figure 2-3 The client login page

User's Manual
3 Interface Description
3.1 Home Page

There are many function entrances in the Home page, through which you
can enter each function directly.
3.2 View
EzView NMS client adopts multi-tab view management, which supports to
open multiple different tabs simultaneously and switch between them.

13
User's Manual
View function is an important function and EzView network element

management software includes Topology View, NE panel view, NE
manager, path view and custom view.
3.2.1 Topology View

Topology view is the default interface appearing after logging in EzView
client, through which network topology management can be fulfilled,
including the creation of subnet, NE, link connection, topology
autodiscovery and etc.
Topology view adopts the form of left topology tree and right figure, and
brief functions of each region are as shown below.
 Menu bar：It is at the top of the main window and provides operation
by menu.
 Tool bar：It is at the bottom of the menu bar and provides operation by
button.

User's Manual
0List of Figures EzView NMS 14
 Tab bar: It is at the bottom of the toolbar, Shows all open windows,
and by clicking on the tab you can switch back and forth between
different windows.
 Status bar: It is at the bottom of the main window and provides
information containing the current subnet, the current user, server ip
address, the current time and etc.
 Topology tree view: It is at the most left of the main window in a tree
structure. Its root node is root. Click on the different subnet or NE, the
corresponding subnet or NE will be shown in the right topology view.
 Topology View: The main part of the client interface, displays all
subnets and network elements of the current subnet.
 Statistics Window: It is at the bottom of the topology tree view.
Display the type and number of all subnets and network elements that
belong to the current subnet.
3.2.2 NE Panel
NE panel shows boards and ports of NE. The status of alarm, LEDs and
loopback are displayed by various icons on the panel diagram.
Double-click NE icon in the topology view, NE panel diagram will be

displayed, which is as shown below.

15
User's Manual
EzView NMS 0List of Tables
3.2.3 NE Explorer
NE explorer is the main operation interface of EzView to devices, adopting
the form of “left topology tree and right table” and providing configuration,
management and maintenance functions of devices. Choose the
corresponding operation object and the corresponding functional node in
the function tree to open the configuration interface of this function.
Double-click the board or port on the NE panel diagram to enter NE

explorer, the interface of which is as shown below.
3.2.4 Trail View

Trail view provides searching, creating, configuring, managing and
maintaining of network path.
Select “Trail > Trail View” in the main menu to enter trail view interface,
as shown below.

User's Manual
1 Software Overview EzView NMS 16
3.2.5 Custom View

It introduces how to manage custom view, including creating, opening,
modifying and deleting custom view.
Custom view is a kind of topology view and is similar to the main view.
Generally, in EzView, different users have different range of network
management, and the user can customize a view for the network topology
and device under the jurisdiction of him as the working interface. In the
custom view window, the displayed network topology structure includes
link and subnet/NE.
Select “View > Custom View” in the main menu to open “View
Management” dialog, click a custom view and click Open button to enter it,
which is as shown below.

17
User's Manual
EzView NMS 1 Software Overview
3.3 Main Menu

Main menu of EzView includes file, view, config, system management,
fault, performance, trail, Diagnosis task, report, tool and help etc. The
following will introduce the menu one by one.
3.3.1 File
Use explaining of the every submenu in the File menu as shown in Table
3-1.
Table 3-1 File menu
Name of Menu Specification
New Topology Object Add a new NE or trail
Subnet Create a new subnet.
Custom Options Set system configuration. E.g. Sound,

Color, Delay Settings and Topology
Config.

User's Manual
System Parameter Configure Communications Config, NE

Configuration Poll Config, SSL Config and Other Config
Server Time Configuration Synchronize server time through

“Synchronize server time from NTP
server” and “Set server timezone”
Lock Client Lock the client.
Modify Password Modify password of current user.
Windows Show all TABs opened in the network

management interface, select to display
the content of the TAB
Log Out Logout current user, then back to the login

interface.
Exit Exit the NMS.
3.3.2 View
Use explaining of the every submenu in the View menu as shown in Table
3-2.
Table 3-2 View menu
Search NE Search the location of NE in topology view.
SNMP Topology Display “SNMP topology discovery” dialog,

Discovery automatically discovers SNMP devices
between the starting and ending IP.

19
User's Manual
DCN Topology Display “DCN Topology Discovery” dialog

Discovery box, you can configure “Original NE” and
click “Start” to discovery the device.
Topology Discovery Set topology discovery function. If you turn

on the topology discovery function of NE, it
will discovery other NE which supports
topology discovery function automatically.
Auto Layout Auto layout NE and subnet in topology view.
Go to Topmost Subnet Go to the topmost subnet. That is the root net.
Go to Parent Subnet Go to the parent subnet of current subnet.
Zone In Zoom in the topology view.
Zoom In Partially Zoom in the selected area of topology view.
Zoom Out Zoom out the topology view.
Restore Restore the topology view to its original size.
Move Permits you to "grab" the topology view and

move it
Unfold All Unfold all subnets, and display all NE in the

topology view.
Fold All If one NE is belong to the root net, it will be

displayed directly in the topology view. If not
so, only the icon of that subnet will be
displayed.
Custom View Create and manage custom view.
Topology Lock Lock the location of a topology object, or you

can click on it and drag it.

User's Manual
3.3.3 Config
Use explaining of the every submenu in the Config menu as shown in
Table 3-3.
Table 3-3 Config menu
NE Explorer Manage NE and configure board.
Configuration Data Shows configuration data status. Ensure the

Management configuration data is the same between NE
and NMS.
NE Time Synchronization Configure NE time, and stay

synchronization with the NMS server.
NE Data Save Save NE data in bulk.
Batch Clock Operation Batch query NE clock status.
Trap Batch Configuration Set the IP address of automatically report

and allows to batch query the
configuration.
Restore H5600/H5600.V2 to default

Restore To Default
configurations
Query in bulk and lead out voice channel

Chu Type Config
types and voice channel states
Car Create a Car strategy template for the NE
strategy QoS configuration
template
QoS
Flow Create a flow classification template for the
template
classificati NE QoS configuration
on
template

21
User's Manual
WRED Create a WRED strategy template for the

strategy NE QoS configuration
template
IPRAN DS Create an IPRAN DS strategy template for
domain the NE QoS configuration
template
3.3.4 System Management

Use explaining of the every submenu in the System Management menu as
shown in Table 3-4.
Table 3-4 System Management menu
Browse Log Show browse log view window. Allow

to set filter condition, and query all
behaviors of every logged-in client.
Log Statistics System log Use the statistical conditions to fulfill

statistics the log content statistics operated by
the system
Ne log Use the statistical conditions to fulfill

statistics the log content statistics operated by
Ne
Security NM User Set authorization for different user to

Management Management manage different equipment.
Client Access Set the client access control rules, only

Control on the specific host IP address to be
able to login corresponding NMS user.

User's Manual
0 EzView NMS 22
Password Password information in the Password

Dictionary Dictionary cannot be used as a new
user password or the original user's
modified password
Security Security Tactics includes “The

Tactics minimum password length”,
Config “Password of character”, “Password
survival time”, “Tip time”, “Password
reuse interval”, “Login failed times”,
“Unlock time”
Database Data Dump Set NMS data dump rule for daily log,
Management alarms log, abnormal events etc and
dumps data.
Data Export Set the Operation log and History

performance, Exporting condition and
Instance export
Schedule Task Management Set or revoke database backups

regularly, or run database backups
immediately, NE backups
immediately, NTP Server Time
Synchronization.
DCN Management Configuration of NE, proxied NE and

gateway, including gateway network
element, network element, SNMP
monitor, proxy configuration, proxied
NE, H200 serial monitor, serial
monitor, NMNAT configuration and
NAT mapped NE.

23
User's Manual
EzView NMS 2 Software Installation
Adapter Management Query status of adapter, and allows

deleting stopped adapter.
Settings Naming rules: topology connection

name and end to end tunnel name
support default name customization
3.3.5 Fault
Usage explanations of the every submenu in the Fault menu are as shown
in Table 3-5.
Table 3-5 Fault menu
Browse Current Alarms Shows current alarms of selected NE or

board.
Browse History Alarms Shows historical alarms of selected NE or

board.
Browse Abnormal Events Shows abnormal events of selected NE or

board.
Current Alarms Statistic Shows alarms statistic of selected NE or

board.
History Alarms Statistics Shows alarms statistics of selected NE.
Alarms Attribute Setting Allows setting alarms function switch,

alarms attribute and NMS alarms attribute.

User's Manual
2 Software Installation EzView NMS 24
Set Fault Diagnosis Rules Provide common fault diagnosis rules,

supports to define diagnosis rules, including
alarms cause, diagnosis method and
handling information.
Remote Notification Configure alarm remote notification

parameters to send notification of specified
alarm item under specified condition to
specified E-mail or cell phone users.
Alarm Poll Config Configure current and history alarm poll

parameters and current and history alarm
poll NE.
User Defined Alarm Users can define the alarm name according
Name to their needs.
Operate the alarm reverse in bulk (reversion

Alarm Batch Reverse
mode and reversion status.
3.3.6 Performance
Use explaining of the every submenu in the Performance menu as shown
in Table 3-6.
Table 3-6 Performance menu
SDH Browse SDH Query performance data of SDH NE,

Performance Performance board and port, including current
Management data, historical data, UAT data and
performance threshold-crossing
TRAP data.

25
User's Manual
EzView NMS 2 Software Installation
Performance Set performance threshold template

Template which can be apply to NE.
Performance Turn ON/OFF NE performance

Monitor Time monitor and set its time range.
Performance Set and query current performance

Schedule schedule task, modify and delete
Task current performance schedule task
24-Hour SDH Configure the 24-hour SDH

Performance performance statistic, query or delete
Statistic 24-hour SDH performance statistic
MPLS Performance Configure NE performance monitor

Performance monitor manage, you can create, modify,
Management manage query, delete, suspend, resume the
performance monitoring instance,
and view the performance data
Performance Configure NE performance schedule

schedule strategy manage, you can create,
strategy modify, and delete performance
manage schedule strategy, use the created
performance schedule strategy in
creating performance monitor
instance
Performance Custom performance monitoring

template templates, which can be used in NE
manage
monitor instance
Browse Query history performance data in

MPLS history NE monitoring manage
performance

User's Manual
2 Software Installation EzView NMS 26
MPLS flow Query MPLS flow data

statistics
RMON Flow Flow monitor Create RMON flow monitor tasks for
Management task Ethernet ports (only supports
management H9MO-LME device Ethernet card
VCTRUNK port)
Browse flow View and store RMON flow data for

record Ethernet ports (only supports
H9MO-LME device Ethernet card
VCTRUNK port)
Browse over View and store RMON flow over

threshold threshold record for Ethernet ports
record (only supports H9MO-LME device
Ethernet card VCTRUNK port)
3.3.7 Trail
Use explaining of the every submenu in the Trail menu as shown in Table
3-7.
Table 3-7 Trail menu
Trail View Shows trail view window of current trail.
Trail View Customization Customize trail view, allows modifying

or deleting it.
SDH Trail Creation Allows creating SDH trail which is

based on the NE in current trail view.

27
User's Manual
EzView NMS 0
SDH Trail Search Search NE service information and

network layer service information on
NMS, then form trails and show them.
SDH Trail Management Query or manage SDH trail information

on NMS, allows activating, deactivating
or deleting trail and querying trail status.
SDH Discrete Service Query SDH discrete service information;

Management allow activating or deactivating the
selected service.
64K Trail Creation SDH trail has been created in Logic： 1

port
Displays the “64K trail creation”
window, you can modify the trail based
on SDH. The SDH trail has been created
in the VC4:2 or Logic: 1 port on the
aggregation card of the H5600 series
devices
Search 64K Trail Search the 64K cross-connection

information saved in the NE layer of
EzView NM side and the 64K cross
service information saved in the network
layer of EzView NM side, and form and
display 64K trail information
64K Trail Management Query or manage the 64K trail

information on NM side, set and view
the trail alarm, view the trail status and
information, modify the trail name, and
save the trail report to the file and print

User's Manual
3 Interface Description EzView NMS 28
Customer Management Create, modify and delete customer

information which is bound to the trails.
Automatic Search IP Search Ethernet service information in a

Service single network element side, form and
display corresponding end-to-end trail
information.
Tunnel Create Tunnel Create end-to-end Tunnel in the NE of

the current Trail view.
Tunnel Query or manage end-to-end Tunnel

Management information in NM side, deploy,
demolish or delete Tunnel, as well as
query Tunnel state information.
Discrete Query the discrete Tunnel information in

Tunnel Network, delete the selected discrete
Management Tunnel.
Create Create end-to-end Tunnel protection

Protection group on existed end-to-end Tunnel.
Group
Protection Query or manage Tunnel protection

Group group, deploy, demolish or delete
Management protection group, as well as query
protection group state information.
Automatic Search protection group information in a

Search single network element side, form and
Protection display end-to-end protection group.
Group
PW Service PW View the PW on all the services

statistics

29
User's Manual
EzView NMS 3 Interface Description
PWE3 Create PWE3 Create end-to-end PWE3 service in the

Service Service NE of the current Trail view.
PWE3 Query or manage end-to-end PWE3

Service service information in NM side, deploy,
Management demolish or delete PWE3 service, as
well as query service state information.
Discrete Query the discrete PWE3 service

PWE3 information in Network; delete the
Management selected discrete PWE3 service.
VPLS Create VPLS Create end-to-end VPLS service in the

service service NE of the current Trail view.
VPLS Service Query or manage end-to-end VPLS

Management service information in NM side, deploy,
demolish or delete VPLS service, as well
as query service state information
Discrete Query the discrete VPLS service

VPLS information in Network; delete the
Management selected discrete VPLS service.
Converge Create Etree Create end-to-end Etree service in the

nce Service NE of the current Trail view.
service
Etree Service Query or manage end-to-end Etree
Management service information in NM side, deploy,
demolish or delete Etree service, as well
as query service state information
Discrete Query the discrete Convergence service

Convergence information in Network; delete the
Management selected discrete Convergence service.

User's Manual
IP Create MPLS Create end-to-end MPLS protection ring

protection protection
subnet ring
Manage Query or manage end-to-end MPLS

MPLS protection ring on NM side, clear or
protection maintain MPLS protection ring
ring
Instrument RFC2544 test Check information about the RFC 2544

test instance on the NMS
free test
Y1564 test Check information about the Y1564 test

instance on the NMS
3.3.8 Diagnosis Task

Use the explaining of the every submenu in the Diagnosis Task menu as
shown in Table 3-8.
Table 3-8 Diagnosis
Name of menu Specification
Task Port/ Create port diagnosis task

Monitor Timeslot
Trail Create SDH trail diagnosis task
Task Management Uniformly manage the created port diagnosis

tasks and SDH trail
64K Trail Diagnosis Create 64K trail diagnosis task

31
User's Manual
Name of menu Specification
64K Diagnosis Task Manage 64K diagnosis task, start, stop, restart,
Management delete the 64K diagnosis task name, diagnosis
type, diagnosis object, creation time, start time,
end time, and running state
3.3.9 Report
Usage explanation of the every submenu in the Report menu is shown in
Table 3-9.
Table 3-9 Report menu
Network Data Report Provide the NE configuration information

of current management domain.
Provide the configuration information of

Transmission Resource
optical port transmission resource in the
Statistics Report
current management domain.
Fiber/Cable Connection Show fiber/cable Connection of selected

Report NE.
Board Information Report Show information of all board.
Slot Information Report Show slot information of all NE.
Board Count Report Count of different type board.
Slot Count Report Show occupied slot information of NE.
Rack Information Report Show information about the rack name,

version, vender, operation status, and etc.

User's Manual
Shelf Information Report Show information about the shelf name,

shelf type, vender, total slot number, serial,
and etc.
Low Order Provide statistic of Low Order

Cross-Connections Cross-Connections resource.
Resource Report
Optical module Display all the optical module information

information report of the device in the network
Occupied Port Show occupied port information of NE.

Information Report
VC12 Remote View HUEBE/HUBE+ remote connection

Connection Information information
Report
Remote Equipment Provide the Essenes equipment and remote

Information Report equipment information
Port Resource Report Show information about the port resource,

such as layer rate, MAC, work mode and
etc.
Port Resource Statistic Show information about the port resource,

Report such as port type, port count, settled port
and etc.
Ne Exchange Resource Show information about the Tunnel label

Report and PW label
Link Bandwidth Report Show information about the Ne link, you

can create, delete, modify and manage the
link

33
User's Manual
Tunnel and PW Count Show information about the Tunnel label,

Report usage rate=used Tunnel count /(settled
Tunnel count +remain Tunnel count)
*100%
Tunnel and PW Count Show information about the PW label,

Report usage rate=used PW count/(settled PW
count +remain PW count) *100%
Channel Resource Channel Resource Statistics interface only

Statistics exists in H9MO-LMDXC41 device. You
can query and edit channel resource. Such
as Digital Channel Code, TS Code, Start
Station, End Station and etc.
3.3.10 Tools
Use explaining of the every submenu in the Tools menu as shown in Table
3-10.
Table 3-10 Tool menu
Software Software Check device software information,

Management Management proprietary protocol update, FTP
update, TFTP update and realize
version upgrade function

User's Manual
Backup the device configuration files

or application program. This backup
function is only applied in the NE
Software which supports this backup function.
Backup Note that when using this function,
users must start TFTP tool and
correctly set the current catalogue
and server ip address
Upgrade Task Uniformly manage the created timed

Management NE upgrade tasks
CPU Packet Query and modify the CPU packet

Limit limit value
DHCP Config Configure related parameters of

DHCP server
North Interface Configuration Configure general parameters and

alarm filter of North Interface.
3.3.11 Help
Usage explanations of the every submenu in the Help menu are shown in
Table 3-11.
Table 3-11 Help menu
Data Move Move database from H7GMSW-CS to

EzView.
Help Topics View online help.

35
User's Manual
About Check the version of the NMS
3.4 Main Toolbar

Use explaining of the every icon in the main toolbar as shown in Table
3-12.
Table 3-12 Main toolbar
Icon Function Icon Function
Zoom In Custom View
Zoom Out Virtual Link
Zoom In Partially Browse Current Alarms
Restore Turn On/Off Alarms

Sound
Move Help Topic
Search NE Critical Alarms
Lock/Unlock Major Alarms

Topology
Topology Minor Alarms

Discovery
Auto Layout Warning Alarm
NE Explorer Abnormal Event
Add connection Network Maintenance

Status

User's Manual
Icon Function Icon Function
The rectangular The free marquee mode

marquee mode
The elliptical Grid Layout

marquee mode

37
User's Manual
4 Operation Guide
4.1 Start the System

4.1.1 Initialize or Recover Database
First time you start EzView, you need to create (initialize) database.
Double-click the EzView Database Management Tool icon on desktop or in

windows start menu. You will see the following management tool
interface.

User's Manual
0 EzView NMS 38
Click localhost in Database Server list on the left side, you will see the
following login interface.
Enter the default user name root and the password Admin_123456.Then
click OK, you will login the database successfully, and menu of each tool is
available.

39
User's Manual
In Database Initialize tab, click Initialize DataBase to initialize the

database.
Note: Initialize database will clear all data of the database. If you want to
remain old data, please make a backup before you initialize the database.
If there are some data need to be recovered, you should choose Recover
MO to recover database in the Database Back and Recover tab.
NMS can be start properly after database is initialized or recovered.
Note: if the NMS needs to be upgraded, you need to backup NM mo data

and then upgrade NMS. After upgrading succeeds, you must initialize
database, during which, you must ensure the current database version is
consistent with current NMS version, and then recover the backup mo data.
4.1.2 Start Server

Double-click EzView server icon on desktop or in windows start menu.
You will see the following System Monitor Client login interface.

User's Manual
The default user name is admin and the default password is Admin123.
Enter user name and password then click OK, you will see the following
System Monitor Client interface.
Note: User names and passwords are case sensitive.
In Process Info tab, select all service, right-click and chose start process.
When Process status is start, EzView service has started successfully.

41
User's Manual
EzView NMS 0
 Before start EzView server, the MySQL service must start already, or
EzView will not work.
 Do not start the same process again when one process already started.
4.1.3 Start Client

Double-click EzView Client icon on desktop or in windows start menu.
You will see the following System Monitor Client login interface.
The default user name is admin and the default password is Admin123.
Enter user name and password and chose server that you want to login,
then click Login, you will see the following EzView client main interface.
Note:
1. User names and passwords are case sensitive.
2. The default user name is admin and the default password is

Admin123. You can modify the password or add another user after
login.

User's Manual
3. If the server that you want to login do not landed in server drop-down
list, you can click the button on the right side then add an new one.
4. Only the server has started successfully, the client can log in.
4.2 Close System

4.2.1 Close Client
To close the client, you just need to execute the command in the File menu.
Use the command <File→Exit>. Before exit the client, you have to
confirm whether saving the topology view or not according to the prompts.
4.2.2 Close Server

To close the server, you just need to execute the command in the System
menu. Use the command <System→Stop NM Server>. When all statuses of

43
User's Manual
EzView NMS 0
processes are stop, server has been closed successfully. Then click close
button in the Menu to close the System Monitor client.
4.3 Management of H0FL-1101S4A

Use H0FL-1101S4A for example, to introduce the basic management
function of EzView.
4.3.1 Add NE
Prerequisites
NMS operators or users with higher permissions are required.
Steps
Step 1 Right-click on the topology view, executive the command <Add<Topology
Object. There will appear an Add Topology Object dialog box.
Step 2 Chose the NE type H0FL-1101S4A in the topology object tree.
Step 3 Enter the information of the NE, including name remarks etc.
Step 4 Chose the SNMP version of NE, the default version is SNMP V2, the
default SNMP port is 161, the read community is public, and the write
community is private.

User's Manual
0 EzView NMS 44
Step 5 Click OK, and then click at main topology view. NE icon will appear at
where you clicked.
4.3.2 Initialize NE
Prerequisites
 NMS maintainers or users with higher permissions are required.
 The NE you added must be an actual device and which is connected
properly.
Steps
Step 1 Double-click the icon of H0FL-1101S4A, there will appear a NE
Configuration Wizard dialog box.

45
User's Manual
EzView NMS 0
Step 2 Chose Upload and click Next, then there will appear a Confirm dialog box.
Step 3 Click Yes to start upload process. Wait for a few seconds until the process
finish. Configuration data of NE should be uploaded to NMS database
successfully.

User's Manual
4.3.3 Configuring NE Communication Parameters

Prerequisites
NMS maintainers or users with higher permissions are required.
Steps
Step 1 Execute the command in the Main menu. Use the command <System
Management →DCN Management >. Then chose the SNMP tab in the
opening interface.
Step 2 In this tab you can modify adapter, IP address, read community and write
community according to your need. Then click Apply.
Note：
 Modify the parameters of this interface may disrupt monitoring of NE, please
operation with caution.

47
User's Manual
 Modify the IP address, read and write community about the NE of this interface
just effect NMS database, and does not affect the data on the actual device.
4.3.4 Query or Configuration Data on NE

In the NE Explorer interface of NMS, allows querying or configuring all
parameters of NE.
NE Explorer is main operation interface of EzView, which adopts the left

tree right table layout, providing the equipment configuration, management
and maintenance functions. Users select the appropriate action object, and
then select the appropriate function node in the navigation tree, the feature
configuration interface will open in convenient.
Prerequisites
 The query operation requires NMS monitors or users with higher
permissions.
 The configure operation requires NMS operators or higher
permissions user.
Steps
Step 1 In the Main Topology view, select H0FL-1101S4A, and then select
<Configuration→NE Explorer> in the main menu to open the Network
Element Management tab.

User's Manual
0 EzView NMS 48
Step 2 Select a manipulate object in the upper-left corner, and then select the node
in the feature tree that you need to query or set in the lower-left corner. E.g.
Executive the command <Config→Port Config→Port Common Config>,
you will see the following interface. Query button is used to query
information of actual device. Click Apply button after parameters
modification, and the modified data will be sent to the device.

49
User's Manual
4.3.5 Monitor NE Alarms

Via EzView NMS, the alarm on the device can be monitored in real time.
Prerequisites
NMS monitors or users with higher permissions are required.
Steps
Step 1 In the Main Topology view, select H0FL-1101S4A, then right click and
select Synchronization Current Alarm to synchronize the alarms from NE
to NMS.
Step 2 Executive the command <Fault → Browse Current Alarm>. It will open the
Browse Current Alarm tab, then select device that you want to query and
click .
Step 3 It lists current alarms of all devices on the right side of the main interface.
You can synchronize, check or acknowledge the alarms through button in
the lower-right corner or Right-click menu.

User's Manual
Step 4 Through switching the tab on the top of interface, you can browse
historical alarm, abnormal event, alarms statistic information etc.

51
User's Manual
5 Security Management
Security management mainly refers to management of EzView users, i.e.

network administration personnel and network maintenance personnel, to
prevent unauthorized access to the system and serious accident caused
thereby. EzView has provided safety management mechanism that can
provide powerful security measures for network management. Security
management including NMS user management, NE customer management
and security log management. The NMS shall support the setting of
timeouts as required.
5.1 Add NMS User

In addition to the Admin user, all users who need operations network
management need to create an account for himself on NMS. It is also
called NMS user.
Add NMS User

According to network maintenance needs, you can create multiple network
users, and assign different permissions to each user to facilitate the
management.
Assign Permissions for Each NMS User

User permissions assignment rules:

User's Manual
0 EzView NMS 52
1. After you create a network management users, generally divide the

user to a user group, rather than assigning user permissions by
fine-tune;
2. If one user has divided to a default user group, but still not meet the
requirements of permission. You can create a new user group and
assign permission to it, then put the user into this group.
3. In practical application, not by creating a new user group, you can also
fine tune the user’s permissions, the properly way is:
− If you want to fine tune permission for a lot of NE, do not directly
choose one of these network elements, but add a new NE Set for
them, and then assign permissions to the NE Set.
− If you want to add lot permissions to one user, do not select all of
these permissions directly, but add a new Operation Set, and then
add this Operation Set to the user.
Client Access Control

In order to prevent unauthorized access, after you create a network
management user, we suggested that you specify the IP address range in
which the user can log on to the client. NMS user can only log on client of
NMS server through the IP address range. If you do not specify the range
of IP addresses, client of NMS server can log on through any IP address.
 Select use default client access control, it is available to all clients within a
defined IP range access.
 Admin user is not limited by the client access control.
Modify NMS User Password

In order to ensure network security, please change your password regularly
and keep it in a secure way. To avoid misuse or vandalism caused by
password leakage.

53
User's Manual
EzView NMS 4 Operation Guide
Delete NMS User

In order to ensure network security, No longer using account need to delete,
so as to avoid misuse or due to the unauthorized use of user vandalism.
5.2 Add NMS User Group

Generally a NMS will be used by multiple users, you can manage user by
group and control permissions for these users. Create custom permissions
groups can achieve this end.
Add New NMS User group

You can group users with similar characteristics into a group, which also
facilitates the users’ unified management.
Specify User Group Member

To classify users and then put them into the proper user group.
Permission and Operation Control

Assign each user group permissions corresponds to a device or a operation
set. Users within the user group have all permissions to the users group
them belong to.
5.3 Add Operation Set

When the default operation set cannot meet user needs, the NMS
administrator may add some customized operation set for assigning
permission to NMS users.
Operation Set Type

Operation set type decides the application scope of itself. There are two
types: management applications system and transport network

User's Manual
4 Operation Guide EzView NMS 54
management system. When specify users and user groups, you can assign
the permission according to the operation set type.
In NMS applications, NMS administrators own the highest permissions

operation sets and NMS monitor only own lowest permissions.
In transport network management system, Device Operation Set owns the

highest permission. Higher permission operation set contains lower
permission operation set by default.
Add Operation Set

Plan and create an operation set, a specific operation set authorized to
specific user groups, all users in this group have permission to perform the
operations in the operation set. This management model is conducive to
unified allocation and management permission of the NMS user.
5.4 Add NE Set

In this interface, users can modify the detailed descriptions and members
of NE set, as well as querying all users and user group in this group have
permission to operate the NE set.
Add NE Set
Plan and create a NE set, a specific device set authorized to specific user
groups, all users in this group have permission to perform the operations in
the operation set. This management model is conducive to unified
allocation and management permission of the NMS user. Users can delete
the unnecessary NE from subnet, making the user manage necessary NE.
After users logging, the deleted NE will not be shown in client.
5.5 Add Subnet Set

In this interface, users can modify the detailed descriptions and members
of subnet set, as well as querying all users and user group in this group
have permission to operate the subnet set.

55
User's Manual
Add Subnet Set

Plan and create a subnet set, combine the necessary subnets to the one and
allocate to specific users. Users can manage the necessary subnets
conveniently. After users logging, the subnet with allocated authority will
be shown. Users only can add the NE in the subnet, cannot create the new
NE under root state.
5.6 E.g. Add User and Assign Permission

Examples on how to create a NMS user, and assign permissions
Prerequisites
 Requires NMS administrator.
 NE Set：ES_NM_user1 has been created.
 Operation Set：OS_NM_user1 has been created.
Background information
NMS administrator A is responsible for network security management,
when installation and commissioning of NMS has been done, you need to
create a new network user called NM_user1, assigned to the NM
maintainer B. Specific requirements are:
 NMS user name：NM_user1

 Password：User123456
 NMS user NM_user1 belongs to NMS maintainer group
 Permission of OS_NM_user1 operation set should be assigned to
ES_NM_user1.
 Permission of OS_NM_user1 operation set should be assigned to
ZW_NM_user1 subnet set.
 IP address range that NMS user NM_user1 can log on the client is:
− Start IP address: 192.168.0.1
− End IP address: 192.168.0.168

User's Manual
− Subnet mask: 255.255.0.0
Steps
Step 1 Executive the command in main menu bar <System
Management→Security Management→NM User Management>.
Step 2 Add a new NMS user "NM_user1".
a Right-click on User and select New User.

b Enter following information in New User dialog box, and then click
OK.
Name：NM_user1
Password：User123456
Confirm Password：User123456

57
User's Manual
c Click "OK". NM_user1 you just added appears in the user list on the
right.
Step 3 To add NMS user "NM_user1" to "maintenance group".
a Select NMS user "NM_user1", and then click the "Subjected to" tab.
b Click the "add" pop-up "Add Group" dialog box.
c Select "Maintainer Group", and then click "Add".

User's Manual
d Click "OK". The user you just added appears in the list of maintainer
group. When adding a new NE, you can configure unnecessary NEs
in “Exclude Member”.

59
User's Manual
Step 4 Adjust the permissions of NMS user NM_user1, make it have the
permission of OS_NM_user1 NEset.
a Click the "Authority" tab, and then click "Add".

b In the "Add Authority" dialog box, set the following parameters:
Type：
“NM for Transmission Network”
“Operation Object”
：“ES_NM_user1”
“Operation Set Name”：“OS_NM_user1”

User's Manual
c Click "Add".
d And then click "OK".
The added authority will be appeared in the authority list.
Step 5 Adjust the authority of NMS user NM_user1, make it have the permission
of OS_NM_user1 (NE set: ZW_NM_user1).
a Click the “Authority” tab, and then click “Add”.

b In the "Add Authority" dialog box, set the following parameters:
Type: “NM for Transmission Network”
“Operation Object”: “OS_NM_user1”
“Operation Set Name”: “ZW_NM_user1”

61
User's Manual
Step 6 Setting IP address range that permit NMS user NM_user1 to log the client.
a Click the "User Access Control" tab, click "Set Client Access
Control".
b Click "add" in the "Client Access Control" dialogue box.
c Set the following parameters in the "Add client access control" dialog
box:
“Start IP Address”: 192.168.0.1
“End IP Address”: 192.168.0.168
“Subnet Mask”: 255.255.0.0

User's Manual
d Click "OK" and close the "Add client access control" dialog box.
e Click "Cancel" to close the "Client access control" dialog box.
f Uncheck "Default Range" check box, select the "Access Allow"
check box and then click "apply".
5.7 Client Access Control

You can set up the network segment where EzView client located. You can
add, modify, or delete the network segment. If you remove a network
segment, the segment of all EzView clients will ban the user login.
5.8 Password Dictionary

Password information in the Password Dictionary cannot be used as a new
user password or the original user's modified password.
5.9 Security Tactics

Security Tactics includes “The minimum password length”, “Password of
character”, “Password survival time”, “Tip time”, “Password reuse
interval”, “Login failed times”, “Unlock time”.

63
User's Manual
6 Topology Management
By creating NE and fiber/cable topology in the EzView, you can manage

them in an easy way.
6.1 EzView Topology

EzView topology refers to the objects created in EzView interface that
corresponding to the actual network device. If you want to manage a NE,
board or fiber cable, you must create a corresponding EzView topology
first.
EzView manage transmission of the actual network device by EzView

topology. At this point, the NE data is uploaded to the EzView, and the
corresponding EzView topology that has the same data as the actual
network device will be created. From then on, configuration of these NE
and board will be sent to them directly.
EzView can manage NE, boards, ports, channels, fiber, etc. EzView
topology can manage through NE, boards, ports, channels, fiber, etc.
Subnet is a logical concept of EzView topology, so EzView cannot manage
an actual device or object through it.

User's Manual
6.2 Add NE
Each actual equipment on the EzView is always established in the NE. You
must create a corresponding NE on the EzView before you manage it.
Gateway NE &Non-Gateway NE
In order to manage the actual network device, there must be information
transmission between NMS and NE through the network. This NE that
directly communicated with NMS through the network is the gateway
network element, short as gateway. While those NE that must connect
NMS through a gateway called non-gateway NE.
Virtual NE
Virtual NE is abstract of one NE that NMS cannot manage it directly. Its
purpose is to show topological relations between the devices that cannot be
directly managed and manageable devices of EzView on the topology. If
there are some devices that cannot be directly managed in the network, you
can build a trail in the NMS by creating a virtual NE.
Add NE
Only when the NE has been created can we manage it through NMS. One
NE can be added whether there is data on the NMS or not.
Add Virtual NE
In order to show the topological relations between the devices that cannot
be directly managed and manageable devices on EzView topology, virtual
NE is needed to achieve its unified management of NMS with actual NE.
6.3 Config NE Data

The NE is in an un-configured state after the success creation. Before
operating a NE, its NE data must be configured. There are 3 modes for

65
User's Manual
configuring management data of NE: manual configuration, copy NE data

and upload.
6.4 Add Board

Manually configure the network on the network element data required
adding a board. The board you add on the NE can be the actual physical
form of the reign plate or a logic board that does not exist on the NE.
6.5 Copy NE Configuration Data

When planning network, using virtual NE to simulate the entire network,
you need to configure the same data to a large number of NEs.
Configuration data replication function simplifies user operations and
improves work efficiency.
6.6 Add Link

In order to establish information communication between the NE and
EzView or between NE and NE and achieve management of NE by
EzView, you need to create a communication cable as its physical
connections. EzView supports to create optical link.
6.7 Add Topology Subnet

For easy management, those topology objects have the same or similar
properties could be put in one topology subnet. Subnet is a logical entity in
the delivery network, refers to a set of network management objects
collection.
It display devices in similar geographical region and close contact

(including NE, links and the underlying subnets) as an icon on the

User's Manual
0 EzView NMS 66
topology view, which contains network elements, link and the next level of
subnet. The system supports multiple subnets
Via subnets, you can organize network view in a better way. On the one
hand view space savings, on the other hand, make related applications,
maintainer dedicate on equipment within their jurisdiction.
6.7.1 Topology Discovery

In this interface, you can take a certain NE as the starting NE,
automatically discover other NEs and add NEs and wires to the NMS
according to the actual network topology.
Interface entry:
In the main menu, select “View > Topology Discovery”
Shortcut icon

67
User's Manual
EzView NMS 5 Security Management
Click Ok, and then click “Create Topology”.

User's Manual
5 Security Management EzView NMS 68
After adding the NE, the following prompt content appears, completing the
NE addition.
6.7.2 SNMP Topology Discovery

In this interface, you can use the IP address of a certain range as the first IP
and last IP. According to the topology of the actual network, network
elements within the IP range are automatically discovered and added to the
network management.
Interface entry:
In the main menu, select “View > SNMP Topology Discovery”

69
User's Manual
As shown in the figure above, input first IP and last IP, click “Start” to
search, and click “Create Topology” to complete the NE addition.
6.7.3 DCN Topology Discovery

In this interface, you can take a certain NE as the starting NE,
automatically discover other NEs and add NEs and wires to the NMS
according to the actual network topology.
Query the DCN domain information and DCN neighbor element of the
origanal NE, and then query each neighbor’s LLDP information to add
links, complete the discovery function.
Interface entry:
In the main menu, select “View > DCN Topology Discovery”

User's Manual
Select a NE and then click “Start”.

71
User's Manual
After the NE is discovered, click “Create Topology” to complete the NE

addition.
6.8 Modify Network Topology

Network Topology created on the EzView is not fixed and unchangeable,
you can modify existing settings. Such as modify a NE name, the
pre-configured NE status, or remove a board.
 Modify NE Name
Users may modify the NE names as you want, and it is not affecting the
operation of the NE.
 Modify Fiber Information
When create a fiber on EzView, the name, length, fiber type, fiber
attenuation and other information has been recorded. If the fiber has been
adjusted, you should change this information in a timely manner, so that
maintainers are able to learn the actual situation of fiber.
 Modify NMS Name
Users may modify the NMS names as you want at any time, and it is not
affecting the operation of the NMS.
 Batch Modify Pre-configuration NE State
Pre-configured data must be distributed to the NE side to take effect. After

the NE configuration is completed, the pre-configured data of NE should
download in a time.
 Delete Board
When you need to modify the configuration of a board on NE, you can
delete it from the NE.
 Delete Fiber
In network adjustment process, such as to delete a NE or change a link

between NE, the fiber connection between the NE must be deleted.

User's Manual
 Delete NE
When adjust the network topology or create an error NE, you can delete
NE on the EzView. Deleting NE will lose all information of the NE on
NMS, but this does not affect the operation of the device.
6.9 Example: Add NE and Configuration

Examples of how to create and configure the NE on the EzView.
Background Information
You should add a gateway NE before adding non-gateway NE.
Prerequisites
Requires NMS Operator or higher permissions user.
Steps
Step 1 Right-click on the topology view, executive the command
<Create→Topology Object >. There will appear an Add Topology Object
dialog box.
Step 2 Chose the NE type H0FL-1101S4A in the topology object tree.
Step 3 Enter the information of the NE, including name remarks etc.
Step 4 Chose the SNMP version of NE, the default version is SNMP V2, the
default SNMP port is 161, the read community is public, and the write
community is private.

73
User's Manual
Step 5 Click OK, and then click at main topology view. NE icon will appear at
where you clicked.
Step 6 If the NE you added must be a actual device and which is connected
properly. So that you can configure it by using up. Then double-click the
icon of H0FL-1101S4A in the main topology view, there will appear a NE
Configuration Wizard dialog box.

User's Manual
Step 7 Chose “Upload” and click “Next”, then there will appear a Confirm dialog
box.
Step 8 Click “Yes” to start upload process. Wait for a few seconds until the
process finishes. Three will appear “Process Result” dialog box then click
“Close”.

75
User's Manual
6.10 Example: Add Subnet

Prerequisites
NMS operators or users with higher permissions are required.
Topology subnet is created to simplify the interface, and has no effect on
NE running.
Steps
Step 1 Right-click on the topology view, executive the command
<Create→Subnet>. There will appear a “Create Subnet” dialog box.
Step 2 Select the “Attribute” tab, enter the basic parameters of subnet.
Step 3 Select the “Object” tab, chose the created NE in the Unified Select list tree,
then click to add it to Selected objects.

User's Manual
Step 4 Click “OK”, and then click at main topology view. Subnet icon will appear
at where you clicked. As shown below.

77
User's Manual
7 System Management
System management including browse log, DCN management, adapter

management, database dump and schedule task management.
7.1 Browse Log

All operation of NMS users on EzView system and the devices and their
operation results are recorded in the logs. EzView provides log browsing,
and you can filter based on different criteria. Log includes the operation
name, the operator, operation time, operation terminal, operation object,
operation result, and so on.
7.2 Log Statistics

Log is used to record all NMS users operating the EzView system and the
device, as well as the operation result. EzView provides system log
statistics and Ne log statistics, which can be filtered according to different
statistical line and statistical column conditions.

User's Manual
0 EzView NMS 78
7.3 DCN Management

7.3.1 Gateway NE
You can view and manage your gateway NE(GNE for short), including the
name, type, affiliated subnet, communication status, gateway type, adapter,
IP address, port, NE count, outband IP, monitor mode, standby IP and
network adapter, you can delete, connect, discon+-nect or refresh the
communication status of GNE manually, and so on.
Via keyboard shortcuts Ctrl+F, Search NE window can be opened, which

can query a specific NE in the current page.
7.3.2 Network Element

Describes how to configure the GNE of the NE, ensuring that DCN
working properly. Including the switching between the main gateways and
backup gateway, lock or unlock the gateway. The use of recovery mode is
when the main gateway has recovered after gateway switching, whether the
connection between EzView and NE has returned to the main gateway or
not.

79
User's Manual
EzView NMS 6 Topology Management

7.3.3 SNMP
Allows to view information of the SNMP NE, including NE name, NE type,
affiliated subnet, communication status, adapter, IP address, port (1-65535),
read community and write community information. You can configure
properties and respective adapter of SNMP NE.

7.3.4 Proxy Configuration

There are some NE need to configure the proxy monitoring, its proxy NE
related information including the proxy NE name, proxy channel, NE type,
first hop proxied NE and second hop proxied NE.

User's Manual
6 Topology Management EzView NMS 80
7.3.5 Proxied NE
The information of the proxied NE including NE name, NE type, affiliated
subnet, communication state, IP address, proxy NE name, proxy type and
proxy channel. Among them proxy type includes EoE monitor channel,
DCC monitor channel, and so on. It also allows you to switch a proxied NE
into a common NE, and synchronize NE communication state or locate the
NE.
7.3.6 Serial Interface Monitor Config of H5002

The information of the Serial Interface Monitor Config of H5002 includes
NE name, IP address, GW name, monitor channel and monitor TS. Start
serial port NM through this page; note that serial port NM (UsoSetup.exe)
must be installed to the NM installation content Client folder.
7.3.7 Serial Monitor

The information of the Serial Monitor includes NE name, NE type,
affiliated subnet, communication status, adapter, TABS link address (1-31),
TABS node address (0-254). You can configure serial port in this interface
to ensure TABS monitoring normally.
7.3.8 NMNAT Configuration

NAT mapping is a process in which the IP address of IP packet-head is
converted to another IP address. In this interface, you can view NAT
configuration information of multiple NMNAT devices, such as NE name,
IP address, Vlan ID, mapping IP, mapping Ne name, mapping Ne type, 161

81
User's Manual
port, 162 port, 21 port, 22port, 23 port, 2650 port, 3000 port, 12305 port,
16210 port, 16211 port, 23010 port and 23011 port.
7.3.9 NAT Mapping NE

In this interface, you can view all NEs configured with NAT mapping rules,
including the NEs mapping to NMNAT device and the third-party router.
NMNAT mapping must be configured through following rules:
1. Mapping Ne IP cannot be in the same network segment with

NMNAT IP;
2. Mapping port range is from 10000 to 65535;
3. When you add a new mapping, the NMS will automatically fill the
mapping port.
Rules:
When you add a new mapping, the NMS will choose unused
ports out of 10000-65535, from small to large, to fill the mapping
port.
4. Support user-defined port mapping. If the default port of NMNAT

cannot satisfy the needs, you can add the user-defined port
mapping manually.
7.4 Adapter Management

Adapter management interface shows adapter name, IP address of server it
belongs to, start time, running state, management NE count, maximum
capacity and so on that relates to adapter. Because EzView supports
multiple-adapter, there may be multiple adapters running in the interface.
You can refresh the adapters or delete the stopped adapter in this interface.

User's Manual
7.5 Database Management

7.5.1 Data Dump
EzView supports to dump the data automatically or manually. The
including alarms event, abnormal event, operation log, history performance,
performance report, UAT record, CSES record. History performance and
performance report support 15 mins and 24 hours performance data dump.
Three are 3 dump modes: Dumping condition, instant dump and instant
clear. Among them dumping condition includes dumping when overflow
and dumping in schedule. All dumping path has been set by default. The
NMS Server can accommodate at 6 months moving historical reports.
7.5.2 Data Export

EzView provides the Operation log and History performance, Exporting
condition and Instance export. Please see the details in the following two
Figures.

83
User's Manual
7.6 Schedule Task Management

Schedule task management is to manage the scheduled backup of database
or NENTP Server Time Synchronization. The schedule can be cancelled or
run immediately according to your need. And this operation is very flexible
as previously customized tasks can be conducted at any time under
emergency conditions.
7.7 System Parameter Configuration

In System Parameter Configuration, you can modify the communication,
NE poll, SSL and other parameters.
In Communication Configuration tab, you can modify Synch/Asynch

frame interval, gateway keep alive parameter, serial frame, frame timeout,
frame record and other parameters.
In NE Poll Configuration tab, you can modify NE poll switch, poll mode,
SDH poll parameter, SNMP poll parameter, serial poll parameter and other

User's Manual
parameters. It’s necessary to adjust poll interval in time according to

network capacity.
In SSL Configuration tab, you can configure whether to turn on SSL

switch.
In Other Configuration tab, you can set Trail search range, upgrade
timeslot occupancy state, cross connection timeout, Tpstate update,
synchronize NE time after NE configuration and Set trap address after NE
configuration.
7.8 Naming Rules Configuration

In the naming rules configuration, you can configure the naming rules of
network “Topology Connection” name and “Tunnel” name. The default
network “Topology Connection” name and “Tunnel” name are set by the
naming rules.
Topology connection: there are default rules which cannot be modified.

You can create new rules and set them as default rules or current usage
rules. Rules include the source network elements, connector, source port,
connector, destination network elements information. You can modify the
content length and type (dynamic type, connector type, digital type, and
fixed type), to realize the name of customization.
Tunnel: there are default rules which cannot be modified. You can create
new rules and set them as default rules or current usage rules. Rules
include the source network elements, connector, destination network
elements, connector, service label, destination slot, destination port,
destination in-label information. You can modify the content length and
type (dynamic type, connector type, digital type, and fixed type), to realize
the name of customization.

85
User's Manual
8 Performance Management
In order to ensure proper functioning of the network, network

administrators and maintainers should be regularly check and monitor the
network by performance management measures.
8.1 SDH Performance Management

8.1.1 Performance Monitoring Concepts
Through the performance management function, network risks can be
identified proactively, avoiding the risk of network failure. We should
know the basic concepts of performance monitoring before operating.
 Performance Event Type
In the operation of the optical transport network, due to internal and

external causes (such as various kinds of noise sources, dispersion, optical
fiber bends, etc), the transmission quality (including bit error, delay, jitter,
drift, etc) may be affected, that is transmission impairments. The reflection
of this damage on the EzView is various types of performance events.
Performance is different from the alarm, reporting performance event did

not break service, but the quality of the transmission has been deteriorated
compared to normal state. Because of the error-correction mechanism of
the optical transport network, the deterioration has been made up

User's Manual
temporarily. But as these factors gradually accumulated, it will eventually

lead to the performance threshold-crossings and so far as to alarm.
Through performance management, this deterioration trend can be found in

advance, and thus these vulnerabilities can be resolved before a failure
occurred.
 Performance Reporting Process
Performance reporting processes is a series of procedures including

detecting, transmission and informing user of the performance events.
Performance reporting includes performance monitoring, performance
reporting, performance threshold-crossings notification, etc. Performance
reporting process is shown in the following figure:

87
User's Manual
 RMON Performance
RMON is mainly used for monitoring and evaluating the quality of

communication on carrying data port, it is one of the widely used network
management standard. RMON includes statistics group, history group,
historical control group and the current control group.
 Performance Threshold
Setting performance thresholds can mask out performance events within

the normal range, making users to focus attention to the seriously
deteriorated performance events.
Threshold also known as tolerance, it means a value just right that make
transmission network to work properly. The use of performance thresholds
is to determine whether the device is working correctly. If one performance
indicator has exceeded its expected performance threshold, then the
performance degradation trend has reached levels that require user
attention and processing.
Usually, setting the performance threshold needs to remain some amount of

allowance, to ensure that you can identify problems in advance.
 Current Performance and Historical Performance
Performance data includes the current performance data and historical

performance data. Browsing the performance data helps maintainers to
understand whether the service is running properly in the past period of
time.
Current performance is the information that stored in the current

performance data register of NE. According to the different monitor
interval, current performance is divided into 15 minutes and 24 hours.
When browsing current performance, EzView will query performance data
directly from the current performance data register of NE. Historical
performance is the performance data that detected in the past period of
time. When querying historical data, you can choose to query the data that
stored on the NE or on the NMS.

User's Manual
When current performance event finished, it will be stored into the

historical data register. You can synchronize them between NE and NMS.
 Performance Monitoring Configuration
You can choose different monitoring policy to monitor performance of

network by performance monitoring configuration.
 Performance Browsing Operation
By browsing performance data you can master the operation quality of

network, and identify hidden risks in advance.
Performance browsing operation includes: viewing current performance

data, viewing historical performance data, viewing Automatic escalation
UAT, viewing UAT log, viewing performance threshold-crossing log,
viewing automatic escalation of the performance threshold-crossing,
resetting the NE performance register, browsing RMON of Ethernet ports,
such as performance data.
 Performance Dump
Performance dump feature makes historical performance data be dumped

in the form of files to a specified folder by the EzView, to improve
management performance.
When NE is running, it will create a lot of performance data. If this data is

all sent to the NMS, then it will be stored into database of EzView .When
the historical performance data that stored in EzView is more than a certain
limit, it will significantly affect the operation of NMS, and may even
breakdown the entire system. EzView can set up automatic or schedule
dump by setting dump parameters, EzView automatically dumps the data
of the history library to files, to relieve the EzView computer's load. Users
can manually back up or delete the dump file.
Usually, users do not need to set dump parameters manually. But under
some conditions of like the large-scale network or many performance
changes, the upper limit value can be raised and the dump period can be
reduced, but when doing this, you need to pay attention to whether there is

89
User's Manual
enough database and free disk space, moreover, if the filtration speed
degrades greatly after modification, a fine adjustment is still needed.
8.1.2 Browse Performance

 Browse Current Performance Data
Current performance data includes: current performance in past 24-hour

and in past 15 minute. Viewing the current performance data can help
maintainers to check the current running state of the network within 15
minutes and 24 hours.
 Browse History Performance Data
History performance data includes: history performance in past 24-hour

and in past 15 minute. Viewing the history performance data can help
maintainers to check the historical running state of the network in specified
time of past 24-hour or past 15 minutes.

User's Manual
 Browse UAT
Browse the NE unavailable time log, and learn about the device
performance. You can complete the following features: browsing finished
unavailable time events, browse unfinished unavailable time, setting
unavailable time new events to report timely tips, and querying unavailable
time events from NE and NM.
 Browse Performance Threshold-crossing Log
Performance threshold-crossings records include: 15 min

threshold-crossings records and 24 hour threshold-crossings records.
Browsing performance threshold-crossings helps maintainers to understand
what service exceptions are. Performance threshold-crossings should be
handled as soon as possible.

91
User's Manual
 Browse Ethernet Port History Group Performance
History group saves Ethernet performance data statistics within a certain

time in the past.
 Browse Ethernet Port Statistic Group Performance
Browsing statistics group performance helps maintainers to master state of

Ethernet port in real time.

User's Manual
8.1.3 Customizing Performance Threshold Template

EzView provides a quick way to set up multiple NE performance
thresholds -- customize performance threshold template. Customizing the
performance threshold template can quickly set performance thresholds for
several NE which save time and improve efficiency.
8.1.4 Setting Performance Threshold of Specified

Board
When the NE find that one performance value exceeds the specified
threshold value, then it will be reported as performance events. Setting
performance thresholds for different ports or channels of a board on

93
User's Manual
EzView NMS 7 System Management
demand can achieve the performance monitoring of NE. If performance

threshold template has been created, you can set up one or more
performance thresholds at a board, port or channel.
8.1.5 Enable/Disable Performance Monitoring

You can enable or disable performance monitoring on the specific NE or
board.
 Performance Monitoring Time
You can learn performance detail records of NE during its running when
the performance monitoring of the NE is enabled, which is convenient for
the maintainer to monitor and analysis its running state.

User's Manual
7 System Management EzView NMS 94
 Enabled/Disable Performance Monitoring of board
Describe how to set up the monitor status and automatic escalation status
of performance monitoring objects. EzView can monitor network
performance of all boards, but automatic escalation function is prohibited
by default, this property can be modified according to the actual need.
 Enable/Disable Performance Monitoring of Ethernet Port Statistics

Group
You can control performance monitoring of Ethernet port statistics group

by setting the parameter of Ethernet port current control group.

95
User's Manual
 Enable/Disable Performance Monitoring of Ethernet Port History

Group
You can control performance monitoring of Ethernet port history group by

setting the parameter of history control group.
8.1.6 Dumping Performance

To avoid overflow or damage of alarms data, the performance data should
be dumped timely. You can dump performance data manually. Or set up
some rules about dumping-condition, and then dump by EzView
automatically. There are two automatic dump methods: Overflow dump
and schedule dump.

User's Manual
 Manual Dump Performance
Manual dump performance data on NMS can save performance data to the
specified directory at any time, which is easy to view, and also reduces the
counts of records in the database, improving system speed.
 Auto Dump Performance
Auto dump performance data on NMS can save historical performance

data to the specified directory automatically, which is easy to view, and
also reduces the counts of records in the database, improving system speed.
There are two automatic dump methods: Overflow dump and schedule
dump.
In the dumping condition page, dumping file format can also be set.
Currently txt, xls, csv and html are supported; and at the same time the
dumping file can be backed up to the remote ftp server.

97
User's Manual
8.1.7 Resetting Performance Register

When turning into the normal operating stage after network test or recovery,
it needs to reset the NE performance registers in order to enter a new
period of performance monitoring.
8.2 MPLS Performance Statistics

8.2.1 Performance Monitor Manage
 Function entry: Menu Items-Performance-MPLS Performance
Management-Performance Monitor Manage
Configure NE performance monitor manage, you can create, modify, query,

delete, suspend and resume the performance monitor instance, as well as
viewing performance data. Please query before you create the monitor
instance.
Click the Query, you will see the prompt to select the network element.
After selecting the network element, you can check the relevant network
element performance monitoring instance.

User's Manual
Create Monitor Instance

1. Select monitor type, select the monitored NE and then refresh. Select
the monitor resources, click Next.

99
User's Manual
In this interface, you can select monitored NE and monitored cycle.

You can select more or choose only one.
2. Select data monitoring template and threshold monitoring template,

and then click Next.
In the interface, you can select the created data monitoring template
and threshold monitoring template, or create the new data monitoring
template and threshold monitoring template.
3. Select the start date, end date and schedule strategy, and then click
Next.

User's Manual
In the interface, you can set the start date and end date, you can
select the created schedule strategy, modify the unoccupied schedule
strategy, or create the new schedule strategy. You can also decide
whether to enable the created performance monitoring instance or
not.
4. The last interface during creating monitoring instance.

101
User's Manual
EzView NMS 8 Performance Management
You can view the created result in this interface.
Create End-to-end Monitoring Instance

1. Select the monitoring type and create the monitoring instance.
2. Select the monitoring NE and available resources.
3. The creating steps are the same with Create Monitor Instance.
Only in the end to end TUNNEL, can service be displayed in the available
resources. After selecting the monitoring item, you can set the performance
monitoring and view the monitored resources. The performance monitoring
resources of TUNNEL are one resource or multiple resources. The performance
monitoring resources of service are one or multiple PW, port, V-UNI or MEP. The
performance parameters showed in this interface (history performance) are the
same with data template.
8.2.2 Check History Data

1. Select the monitoring instance and right-click it to check history data.

User's Manual
8 Performance Management EzView NMS 102
2. Enter the historical data interface; you can check the history
performance data filtered according to the time range. The historical
data checked up from performance management- historical
performance also exists in this interface. You can check the table and
line chart. In this interface, you can also save the historical data in
files. The received the performance data trap and queried historical
performance data (discard duplicate data) will be saved to this
functional node.
 If there is some Node performance parameter existing in the data template,

there will be traffic and bandwidth utilization.
 The performance parameters showed in this interface (history performance)
are the same with data template.
8.2.3 Current Performance

1. Select the monitor instance, right-click it, select Performance
Manage-Current Performance.
2. Unicast tunnel management/PW management/port basic
configuration/E1 management/NE explorer selection/right-click the

103
User's Manual
card/performance management/current performance (laser, fault, MEP

does not have; V-UNI is in PW management interface).
3. You can query the current performance of the monitored instance.

When you query it, please select the monitoring period. If the selected
period does not match, you will see “Operation failed. Monitoring
instance does not exist! Error code: 60002”.
 Scalar performance parameters such as receive packet and transmit packet\

transceiver byte count in current performance interface are the accumulated
values.
 Vector performance parameters such as temperature, transceiver power in current
performance interface are real-time values. Start time is the first time you create
the monitor instance. Reset function is used to clear current performance
displayed in this interface.
8.2.4 History Performance

Manage-History Performance.

User's Manual
card/performance management/history performance (laser, fault, MEP

has no other entrance, V-UNI is in PW management interface).
3. You can query history performance data according to time range.

Since the device can at most save the latest 6 periods history
performance data, so this interface can display6 periods history
performance data at most. When you query history performance data,
you need to select monitor period and time range. The data in history
performance interface shows the statistic value in one period.
8.2.5 Performance Monitor Settings

Manage-Performance monitor settings.
card/performance management/Performance monitor settings (laser,
fault, MEP has no other entrance, V-UNI is in PW management
interface).

105
User's Manual
3. You can set whether to report history performance data actively in

this interface, only the created instance of the monitoring period
setting is valid.
8.2.6 Performance Monitor Manage

1. Select the monitor instance, right-click it, select Performance Monitor
Manage.
card/performance management/performance monitor manage (laser,
fault, MEP has no other entrance, V-UNI is in PW management
interface).

User's Manual
3. You can check the real-time performance data in this interface. NMS
can query current performance and calculate flow rate and bandwidth
utilization according to period frame-sending. As for the performance
of the scalar parameters, device response is the accumulated value.
When you do not select the accumulated value, the NMS will use the
value from the latest period to subtract the value from the former
period; this accumulated value will be displayed in this interface.
Device reports real-time values for vector values, such as temperature,
CPU utilization, packet loss rate, delay, delay variation, and
transceiver luminous power. No matter you select the accumulated
value or not, NMS will display the checked values directly.
8.2.7 Performance Schedule Strategy Manage

1. Menu items-Performance-MPLS Performance
Management-Performance Schedule Strategy Manage

107
User's Manual
2. Enter the Performance Schedule Strategy Manage interface, you can

create, modify, and delete performance schedule strategy in this
interface. Currently, it supports 5 kinds of cycles: 30 seconds, 5
minutes, 15 minutes, 1 hour and 24 hours. 30 seconds, 5 minutes and
1 hour belong to user-defined cycles. One monitor object supports 3
kinds of cycles at the same time; they are 15minutes, 24 hours and
any one other user-defined cycle. If the created schedule strategy has
being used in the monitoring instance, it will not be deleted or
modified.
8.2.8 Performance Template Manage

1. Menu items-Performance-MPLS Performance
Management-Performance Template Manage

User's Manual
2. Enter the Performance Template Manage interface, you can create or

delete performance template. The template includes data template and
threshold template. When the NE monitors some performance greater
than the threshold, it will report the event. You can set different
performance threshold to the card, port or channel, through which, the
performance of NE can be monitored in time.
 If the created template has already been used in the monitoring
instance, it cannot be deleted. If the template checked up by NMS
cannot match with existing templates, it must be automatically named
by NMS and saved in this interface.
 About threshold template: if the performance value is greater than
threshold trigger value, the alarm will be reported, if the performance
value is lower than threshold clear value, the alarm will be ended. So
the threshold trigger value should greater than threshold clear value.
Vector performance parameters such as temperature, transceiver
power in current performance interface are real-time values. Start time
is the first time you create the monitor instance. Reset function is used
to clear current performance displayed in this interface.

109
User's Manual
8.2.9 Browse MPLS History Performance

1. In the menu bar, select Performance>MPLS Performance
Management>Browse MPLS History Performance.
2. You will see the Query dialog box; the filter condition includes
resource name, physical topology, resource type and period.
3. Click Query, the monitor instance searched by filter condition will be
displayed in Available resources.
4. You can select one or more than one monitor instances, and then click
OK to enter Browse MPLS History Performance interface.

User's Manual
5. This is the MPLS performance report interface, you can check many
monitor instances from many devices according to tables and line
chart.
8.2.10 MPLS Flow Statistic

1. In the menu item, select Performance-MPLS Performance
Management>Browse MPLS Flow Statistic.
2. You will see Browse MPLS Flow Statistic diagram box.
3. Enter Browse MPLS Flow Statistic interface, you can check the
statistics of the performance data flow and bandwidth utilization of
many monitor instances from many devices according to tables and
line chart.

111
User's Manual
8.3 RMON Flow Management

8.3.1 Flow Monitor Task Management
1. Menu items-Performance-RMON Flow Management-Monitor Task
Management.
2. Select the network element that needs to be monitored in the left
topology tree.
3. Click “Create Task” to see the following dialog box.

User's Manual
4. Select the NE port information, enter the task name, start time, end
time, sampling interval, dump interval, over threshold count, over
threshold interval, threshold. And then click OK to complete the
RMON flow monitor task creation.
5. Select the task, and then you can pause, start, stop, and modify it. You
can only delete the RMON flow monitor tasks that are not in the
running state.
8.3.2 Browse Flow Record

1. Menu items-Performance-RMON Flow Management-Browse Flow
Record.
2. Select the RMON flow monitor task that needs to be checked in the
left topology tree.
3. You can view the flow data of the selected RMON flow monitor task
through the Table Perform/Linechart Perform.
4. You can select the flow data of the selected RMON flow monitoring
task based on the time range. After the time is changed, you need to
click the Query to update the data.
5. The data can be stored as a table by Save as.

113
User's Manual
6. In the linechart perform, you can select the Time granularity.

7. The linechart perform includes: Sent flow (Mbits/s), Sent Bandwidth
utilization (%), Receive Flow (Mbits/s), Receive Bandwidth
utilization (%), after you enter the contents, please click Refresh to
update the linechart.
8. After you enter the contents in Time granularity, Data Values, Date
Points, please click Refresh to update the linechart.
8.3.3 Browse Over Threshold Record

1. Menu items-Performance-RMON Flow Management-Browse Over
Threshold Record.

User's Manual
2. Select the over threshold record of RMON flow monitor task that
needs to be checked in the left topology tree.
3. You can select the over threshold record of the selected RMON flow
monitoring task based on the time range. The last over threshold
record will be used.
4. The over threshold record can be stored as data table contents.
 In the RMON flow monitor task, right-click it, you can enter the
Browse Flow Record and Browse Over Threshold Record.
 There are more 2 months of data in the database. The NMS
automatically dumps data once each month (1st every month), dumps
data two months ago, retains 2 months of historical data.

115
User's Manual
9 Fault Management
Fault management handles the alarm report of all managed devices, as well
as alarm information that are generated by NMS module during running
time, including alarm information and operation, information of real-time
monitoring, historical alarm information, operation information, etc.
Through the fault management function, users can query and handle all the
alarms that are collected by management monitoring system, and you can
query all alarms records of the system since its running. These records are
very valuable to the performance analyzing of networks and equipment.
9.1 Basic Concepts

9.1.1Alarm Reporting Process
Alarm reporting process is series of processes that how users to learn
alarms appearing on board by EzView. Understanding of alarm reporting
process is meaningful for users to handle alarms.
For different types of equipment, alarm escalation processes are not the
same, and mainly divided into two types.
The following figure describes Alarm reporting process of the LMXE

series equipment.

User's Manual
The following figure describes Alarm reporting process of the Non-LMXE

series equipment.

117
User's Manual
After receiving a new alarm notification, MPU will decide whether to

report the alarm to EzView according to the setting of the alarm TRAP.
If communication between the NMS and the NE breaks down, and NMS
re-login, it will take sync to MPU alarm libraries initiatively at once. This
ensures the synchronization refresh of alarm data.

User's Manual
9.2 Alarms Synchronization

Synchronizing alarm includes synchronizing current alarms on NE and
synchronizing current alarms on NMS. By synchronizing alarm, it will
achieve alarms synchronization between the NE and the NMS, also alarms
synchronization between current alarms and alarms libraries of the NMS.
9.2.1 Synchronizing Specified NE Current Alarms

Operation of synchronizing alarms will check alarm data between the NMS
and the specified NE, if there are inconsistencies, NE alarms will be
uploaded to NMS database and overwrite the original content. You should
synchronize NE alarms, when the service interruption has been restored, or
when some operations possibly causing alarms inconsistent between the
NE and the NMS have completed.
9.2.2 Synchronizing NMS Current Alarms

Synchronizing NMS alarms means refresh NMS alarm libraries, making
NMS alarm libraries consistent with the current alarms in the network.
Resubmit the unfinished alarms to alarm libraries, and finish the alarms
which are unfinished in the alarm libraries but have finished actually.
9.3 Browse Alarms

9.3.1 Browse Alarms in Specified Time Period
By browsing the alarms of single or multiple NE in specified time period,
you may master network status within this time period.
9.3.2 Browse Current Alarms

By browsing all current alarms of the whole network, you can learn the
current operating status of network, which is convenient to update alarms
information and handle them in time. When browsing all current alarms, it
allows you to send, sync, refresh, check, ack, filter the alarms, etc.

119
User's Manual
The same alarms on the same monitored object can be folded as one alarm.
9.3.3 Browse Current Alarms of Specified Level

By browsing all current alarms of the specified level, you can learn all the
current alarms of this level, which is convenient to locate the fault quickly.
Browsing all current alarms of the specified level allows you to send, sync,
refresh, check, ack, filter the alarms, etc.
9.3.4 Browse Current Alarms of Specified NE

By browsing all current alarms of the specified NE, you can learn the
operating status of this NE. When querying NE status or maintaining NE,
you need to browse current alarms of this NE. Browsing all current alarms
of the specified NE allows you to sync, refresh, check, ack, filter the
alarms, etc.
9.3.5 Browse NMS Current Alarms

By browsing all current alarms of the NMS, you can learn operating status
of the NMS and connection between the NE and the NMS. Browsing all
current alarms of the NMS allows you to sync, refresh, check, ack, filter
the alarms, etc.
9.3.6 Browse Current Alarms of SDH Trails

By browsing all current alarms of the SDH trails, you can learn the
operating status of the service that is carried by this trail, which is
convenient to update alarms information and handle them in time.
Browsing all current alarms of the SDH trails allows you to sync, refresh,
check, ack, filter the alarms, etc.

User's Manual
9.3.7 Browse History Alarms

By browsing all history alarms of the NMS, you can learn what faults have
occurred on the NE and NMS, which is convenient to analysis the fault.
When browsing all history alarms, it allows you to refresh, filter the alarms,
etc.
9.3.8 Browse Abnormal Events

When take regularly maintenance, you need to browse the abnormal events,
in order to check the operating status of the network.
9.3.9 Browse Current Alarms Statistics

By browsing current alarms statistics, you can learn the count that different
level alarms of each NE and NMS, which is convenient for network
maintenance.

121
User's Manual
9.3.10 Browse History Alarms Statistics

By browsing history alarms statistics, you can learn the number of different
level history alarms of each NE and NMS, which is convenient for network
maintenance.

User's Manual
9.4 Check Channel Alarms Suppression

Check all alarms that have been suppressed of entire network. You can
disable the suppression of alarms, to protect the alarms monitoring from
effect of mistaken setting.
9.5 Customizing Alarms Attribute Template

Check all the channels that have been set alarm reversion of the entire
network. You can modify alarm reverse rotation to avoid mistaken setting
that will affect the service.

123
User's Manual
9.6 Alarms Suppression

Alarms suppression means that do not monitor some alarm events had been
suppressed. The alarm event can from the entire network equipment,
specific NE, specific board, trails or even specific functional module of
specific board.
9.7 NM Alarms Attribute Configuration

If one alarm auto reporting is enabled on the NE, when this alarm occurs
on the device, it will report to NMS automatically. But sometime, there are
some alarms are not necessary, so that its auto reporting should be
shutdown (suppression) to reduce the effect of too much alarms on NMS
performance.

User's Manual
9.8 Alarm Level Adjustment

Alarm level of each alarm event of NMS, NE and board can be adjusted
according to the need for maintenance, which can facilitate management
and improve alarm monitoring efficiency.
9.9 Port QoS

For the port of a board, you can configure QoS according to count and
importance of its service to improve alarm management efficiency. QoS
can be set by setting port switching conditions.
9.10 NE Alarms Storage Configuration

By setting the mode of NE alarms storage, alarm information will be stored
into the corresponding registers, which make fault analysis easier.

125
User's Manual
9.11 Dumping Alarms

To avoid overflow or damaged of alarms data, the performance data should
be dumped timely. You can dump performance data manually. Or set up
some rules about dumping-condition, dump by EzView automatically.
dump.
Manual Dump Performance

Manual dump performance data on NMS can save performance data to the
specified directory at any time, which is easy to view, and also reduce the
counts of records in the database, improving system speed.
Auto Dump Performance

Auto dump performance data on NMS can save historical performance
data to the specified directory automatically, which is easy to view, and
also reduces the counts of records in the database, improving system speed.
dump.

User's Manual
In the dumping condition page, dumping file format can also be set.
Currently txt, xls, csv and html are supported; and at the same time the
dumping file can be backed up to the remote ftp
server.
9.12 Alarms Function Switch

Enable auto acknowledge, auto synchronization, dynamic correlation
analysis and auto change ended alarms into history alarms, helping
network maintainer dedicating to current alarms.

127
User's Manual
9.13 Alarm Poll Config

In alarm poll config page, you can configure and query the current alarm
poll parameters and history alarm poll parameters. After starting alarm poll
function, NMS will query NE alarms periodically to ensure the consistency
between NMS-side alarms and NE-side alarms.
In current alarm poll parameter configuration page, function switch can be

opened and function parameters can be configured. Serial and parallel
modes do not need the device response, but need to wait for a sending
frame interval. Parallel mode does not need to be processed by NMS. The
serial mode is that select one device in each gateway to send frames, and
then send a device of a gateway in each fixed timespan between cycles.
The parallel mode is that select one device in all gateways to send frames,
and then send frames to the second device of all gateways, and so on.
Current alarm poll start delay means how long it delays the start of alarm
poll after starting adapter process.

User's Manual
In Current Alarm Poll Ne Select page, and History Alarm Poll Ne Select
page, some important NE can be selected, NMS only polls the selected NE,
which will ensure the consistency of alarms and avoid the waste of system
resources by polling the unimportant NE.

129
User's Manual
In the History Alarm Poll Param page, you can turn on the poll switch and
configure the parameters. Only after the device response, can the history
alarm poll modes: serial and parallel send frames, parallel mode does not
need to be processed by NMS. The serial mode is that select one device in
each gateway to send frames, and then send a device of a gateway in each
fixed timespan between cycles. The parallel mode is that select one device
in all gateways to send frames, and then send frames to the second device
of all gateways, and so on.
History Alarm Poll Timespan Between Ne is the history alarm poll

command interval between NEs, which can be set to be 20s at least.
History Alarm Poll Plan can be set to every day, every hour and every
week.
9.14 Remote Alarm Notification

Through setting parameters like remote notification rules and format, NMS
will send the eligible alarm messages to maintainers by E-mails or SMS, to
make them informed about the alarms on NMS server so as to take
corresponding measures.

User's Manual
0 EzView NMS 130
9.14.1 Communication Parameter Config

Setting communication parameter of remote notification device can make
the remote notification device send E-mails or SMS to timely inform
maintainers to deal with alarms.
Prerequisites
“System operators” or users with high permissions are required.
 Sending devices include: “E-mail”, “GSM Modem”, “CDMA
Modem”, “direct connection to SMS center (SMS gateway)” and
“FTP”. Sending E-mails to inform users requires normal
communication of NMS server and mail server; “GSM Modem”,
“CDMA Modem” and “ direct connection to SMS center (SMS
gateway)” inform users by sending SMS; “FTP” saves messages as
into TXT files and upload to ftp server.
 The default port of is 25, please ensure SMTP port of mail server is
available.
Steps
Step 1 Select “Fault > Remote Notification” in the main menu.
Step 2 Click “Config” on the bottom left of remote notification window, and
select “Communication Parameter Config”.

131
User's Manual
EzView NMS 9 Fault Management
Create communication parameter
1. Click “Create” button.

2. Input the name of device and select the device in “Name” tab.

User's Manual
9 Fault Management EzView NMS 132
3. In “Communication Parameter” tab, after inputting correct server

information, click “Test on server” button to test whether the server is
available. After the server passes the test, check “Enable” box.
FTP method needs no server test. Different devices require setting different
communication parameters.
4. Click “OK” button.
Modify communication parameter config
1. Select a line in the list, and click “modify” button.

2. Modify the name and communication parameter of it in “Modify
communication parameter config” dialog.

133
User's Manual
3. Click “OK” button.
Delete communication parameter
1. Select a line in the list and click “Delete” button.
9.14.2 Information Config

Set the information of E-mails, SMS or file contents, including Subject,
Start, End, containing alarms/events fields and the display order of the
fields.
Prerequisites
“System operators” or users with higher permissions are required.
Steps
Step 2 Click “Config” on the bottom left of “Remote Notification” and select
“Information” config.

User's Manual
Step 3 Set Mail send content, SMS send content and Save file content in different
tabs of “Information config” window.
Step 4 Click “Mail content config”, select the information contained in the E-mail,
such as NE name and Object identity.
Step 5 Click “OK” button.
9.14.3 Set Remote Notification Rules

Prerequisites
“System operators” or users with higher permissions are required.
 Condition is used to set alarm name, alarm severity and etc;
Notification time is used to the time of sending remote notification;
Notification way is used to set input E-mails and input phone
numbers.

135
User's Manual
 The alarm occurrence time and cleared time in the E-mails or SMS
are the time of NMS server.
Steps
Step 2 Click “Create” in “Remote Notification” window, and select “Alarm

notification”.
Step 3 Set parameters including “Alarm name” and severity in “Base config” tab
in “New alarm rule property” dialog.
Step 4 Select “Alarm source” tab, select “Select all” button to select all the NE or
select “Custom selection” button to set alarm source according to NE and
NE type.

User's Manual
Step 5 Select “Notification time” tab to set the time of notification.

137
User's Manual
Step 6 Select “Notification way” tab, input emails and phone nums, and add
comment.
If this rule needs to be enabled immediately, please select “Enable” check box.
Afterwards check this option in “Remote notification” window, click “Property”
button and check “Enable” in “Notification way” tab.
 Click Contacts, you will see the following information.

User's Manual
 Click Manage Contacts, you will see the following information.
 Click Create, you will see the following information, fill in the blanks
and click OK.

139
User's Manual
Step 7 Click “OK” button.

User's Manual
10 Report Management
Reports provides a variety of network parameters and operating status,

including data report of entire network, a variety of information reports
about NE and board, provides powerful and useful data for engineering
maintenance.
EzView provides a variety of report, which make query and save

information timely.
EzView provides device configuration report. Device configuration report

mainly provides information about hardware configuration of device. It is
useful reference information for the engineers in the initial stage of
network construction.
When reports generated, you can browse, filter and print the reports, even
save the reports as text files. In the EzView interface, almost data that
displayed as a form can convert to report and then print.
10.1 Network Data Report

Network data report provides all devices configuration of NMS current
device management domain, including NE name, NE IP address, NE type,
affiliated subnet, software version, pre-configuration status, gateway type,
gateway attribute, start time, creation time, etc. This data report makes

141
User's Manual
query NE information of subnet easily, and also makes it easily to locate a

NE. After completion of the network, the network data report needs to
update and to prepare for the entire network maintenance.
10.2 Transmission Resource Statistics Report

Transmission resources statistics report provides all transmission resources
configuration from optical ports of NMS management domain, including
NE name, NE address, NE type, affiliated subnet, slot, board type, port,
time slot, remote NE name, remote NE address, remote NE, remote slot,
remote board type, remote port, related SDH service name, and related
SDH service remark. After configuring service to the optical ports, you
need to update transmission resources statistics report in time, to facilitate
the management of the transmission resources at optical ports.
10.3 Board Information Report

Board information report is information about attribute of the board,
including board type, NE side board status, software version, version of
FPGA A and FPGA B, slot information, etc. After configuration or

User's Manual
refreshment of board, board information report should update timely to

facilitate board management.
10.4 Slot Information Report

Slot information report is information about slot, including status of NE
side board and NM side board, as well as attribute of board slot Slot
information is on demand when configuring a new board, so Slot
information report should update if the slot of boards has been changed.
10.5 Slot Count Report

Slot count report is used to count the slot occupation information of each
NE. Such as showing total slot, used slot, untapped slot and usage rate (%)
of NE.

143
User's Manual
10.6 Board Count Report

The board count report provides information about board type and the
count of each type on every NE.
10.7 Rack Information Report

Show information about the rack name, version, vender, operation status,
and etc. This function is only supported by PTN series devices.

User's Manual
10.8 Shelf Information Report

Show information about the shelf name, shelf type, vender, total slot
number, serial, and etc. This function is only supported by PTN series
devices.
10.9 Fiber/Cable Connection Report

The fiber/cable connection report provides information about cable level,
source NE, source port, destination NE, destination port, rate, reality and
etc. You can create and modify the fiber direction in this page. After the
completion of fiber connection, fiber/cable connection report must be
updated for convenient fiber management.
10.10 Lower Order Cross-connections Resource

Report
Lower order cross-connections resource report provides the statistics about
usage of the lower order cross-connection resource, including NE name,

145
User's Manual
NE type, affiliated subnet, lower order cross-connection count, maximum

VC4 number, used VC4 number, remaining VC4 number, used VC3
number, remaining VC3 number, used VC12 number, remaining VC12
number, etc.
10.11 Occupied Port Information Report

This report is used to count port occupation information of each NE,
including NE name, NE type, port type, total port, settled port, untapped
port and usage rate (%).
If the port bears SDH service, it will be recognized as the occupied port.
10.12 Optical Module Information Report

You can query or print all the optical module information of the device in
the network through this report. When select Only Display The in-position
Optical Module button, you can only query the in-position optical module

User's Manual
information. If you do not select Only Display The in-position Optical

Module button, you can query the port information which supports optical
module.
You can get rid of powering down device, inserting and pulling out the
card and replacing the card through NMS. You can get rid of abnormal
situations through following methods.
a) When you refresh the interface, if the card is not in its position, the
Refresh button is marked in red.
b) When you refresh the interface, if the Refresh button is not marked in
red, you will see only the queried data.
10.13 VC12 Remote Connection Information

Report
This report is used to count the remote connection information of
HUBE/HUBE+ device monitoring router, including NE name, NE type,
HUBE/HUBE+ device VC12 remote information No, monitoring NE IP
address, type, monitor channel, monitor NE name, monitor NE type.

147
User's Manual
10.14 Remote Equipment Information Reports

Remote equipment information report introduces the information of ASV1
series, ASV2 series equipment and remote equipment, including NE name,
NE type, port NE address, shelf Num, slot, board type and remote
equipment type.
10.15 Port Resource Report

Port Resource Report shows information about NE name, NE type, slot,
port number, port name, port type, direction, layer rate, MAC address, and
transceiver module status.

User's Manual
10.16 Port Resource Statistic Report

Port Resource Statistic Report shows information about NE name, NE type,
port type, port type index, port count, protected port, unused port, and
usage rate.
10.17 Ne Exchange Resource Report

Ne Exchange Resource Report shows occupation information about Tunnel
label and PW label, such as label count, remain inlabel count, used outlabel
count, remain outlabel count. This function is only supported by PTN
series devices.

149
User's Manual
10.18 Link Bandwidth Report

Link Bandwidth Report shows the selected NE port resource information.
Create Tunnel through the end-to-end network elements, you can view the
usage information of the Tunnel link bandwidth; create the link
information by selecting the NE object, configuring the source NE,
destination NE, port information, you can check the Link Bandwidth
Report information, such as modify, delete, refresh the remaining
Bandwidth, print, save as file. This function is only supported by PTN
series devices.
10.19 Tunnel and PW Count Report

Tunnel Count Report shows Tunnel information, such as settled Tunnel
count, used Tunnel count, remain Tunnel count and usage rate. This
function is only supported by PTN series devices.

User's Manual
PW Count Report shows PW information, such as settled PW count, used

PW count, remain PW count and usage rate. This function is only
supported by PTN series devices.
10.20 Channel Resource Statistics

Channel Resource Statistics interface only exists in H9MO-LMDXC41
device. You can query the service which is created by “schedule” or
“Service Config” functions in H9MO-LMDXC41 device. Such as Digital
Channel Code, TS Code, Start Station, End Station and etc. You can
modify channel resource by double-click or right-click the menu. You can
see what channel resource you want by Filter function.

151
User's Manual

User's Manual
11 SDH Trail Management
Through network-level functions of EzView, SDH trail and service can be

created and managed rapidly from end to end. Compared with single
station configuration, end-to-end method is more rapidly and conveniently.
SDH end-to-end management is to realize end-to-end management of SDH

service through network-level management function of EzView. Through
SDH end-to-end management function, the user can do the following:
 Configure end-to-end service.

 View graphic interfaces and virtual routers of trails.
 Query detailed trail information.
 Rapidly filter, search and locate trails.
 Centrally manage and maintain trails.
 Manage alarms through trail.
 Print trail report.
Operations and displays of SDH end-to-end management are fulfilled

under graphic wizard, which make operation process more intuitive. SDH
trail supports semi-automatic, automatic and manual creation.
 Under automatic method, it only needs to specify the source and

destination nodes of trail and port.
 Under semi-automatic method, the user can specify the router and
timeslot that the trail will pass through.

153
User's Manual
 Manual method means the routers and timeslots that the trail passes
through are all specified by the user.
End-to-end management is the core function of EzView network-level

functions. Using trail management method to configure services greatly
simplifies service configuration operations and reduces operation error
probability.
If there is no end-to-end management function, the process of configuring

a trail is a completely manual process, for example, if configure a circuit of
a 2M circuit from one NE land from the Nth NE after passing through N
NEs, it needs to configure timeslot cross-connection on these N＋1 NEs.
If there is end-to-end management function, configure a circuit like that

can be as simple as ignoring the N － 1 nodes in-between and just
specifying the source and destination ports of the circuit, and then EzView
can generate a circuit automatically.
Trail function’s impact on system performance: under the condition of

satisfying the requirements of EzView capability (specifically shown by
model, NE managed by EzView, the number of trails and etc.), SDH
end-to-end management does not have a significant impact on system
performance. Trail function’s impact on other features: SDH end-to-end
trail management relies on fiber configuration.
11.1 Theory Description

A brief introduction of SDH end-to-end trail automatic creation theory:
 Select the level and source and destination of the wanted trail on
EzView interface.
 EzView automatically calculates the routing of the trail and display it
on the interface.
 After check the routing of the trail, confirm to create the trail.

User's Manual
 EzView creates the trail according to its source and destination and
routing, and also calculates the corresponding cross connections to
send down to NE to create.
Thus, an end-to-end SDH trail will be created out on EzView, and at the
same time services are automatically sent down to NE to be created.
11.2 Principles of Creating Trail

As creating network-wide service by single station configuration is very
cumbersome and easy to make mistakes, so creating service by trail
function of EzView is recommended.
Principles of creating SDH trail service:
 The source and destination ends of trail service cannot choose the
same network element.
 The failed trail service for some reason can only be activated and
recreated after being deleted, and cannot be activated.
 When there are resources with same low-order idle timeslots, the
number of the same time slots is preferable, while the smallest
number is the next choice (which can be modified manually).
11.3 Trail View Customization

Customizing trail view is convenient for users to view the topology of
creating a trail.
Prerequisites
System operators or users with higher permissions are required to log in
NE management system.
Steps
Step 1 Select “Trail > Trail View Customization” in the main menu, then “View
Customization” dialog will pop up.

155
User's Manual
Step 2 Input “View Name” and select NE.
Step 3 Click “OK”, thus the creation of trail view is succeeded.
Step 4 (Optional) click “Delete” to delete the trail view.
The view being used cannot be deleted.

User's Manual
10 Report Management EzView NMS 156
11.4 SDH Trail Creation

11.4.1 Non-SNCP Tail Creation
When SDH service without SNCP needs to be created, end-to-end method
of creating trails can complete service configuration quickly. In each trail
view, non-SNCP trail can be created in the same way.
Prerequisites
 System operators or users with higher permissions are required to log
in NE management system
 There are spare timeslots on source and destination NEs.
Steps
Step 1 Select “Trail > SDH Trail Creation” in the main menu.
Step 2 Select the direction of the service and set the level of it.
 The direction of service could be unidirectional or bidirectional.
 The level of service could be “VC12”, “VC3” or “VC4”.
Step 3 Configure “Strategy”, set “Type” as “Common Trail”.
 Strategy is the principle for NMS to search available routes, which includes
“Shortest Route First” and “Smallest Load First”. “Shortest Route First”
means the number of passed NEs calculated from the source to the
destination of the trail is the fewest; “Smallest Load First” means the
resources of available timeslots calculated from the source to the destination
of the trail is the largest.
 Trail type is classified to “common trail” and “protection trail”. “Common

trail” is an unprotected trail; “protection trail” is a SNCP-protected trail.
Step 4 Double click the source and the sink NEs in turn. Select boards, ports and
timeslots in the “Select source”, “Select target” dialogs that pops up, and

157
User's Manual
EzView NMS 10 Report Management
then click “OK”. The trail automatically chosen by the system will display
between the source and the sink NEs.
Step 5 (Optional) right click NE icon, and in the right-click menu that pops up,
the NE can be set to be a necessary node or a prohibited node of the trail.
Clicking “Set prohibited node” can specify the service trail not to pass the
NE, above which a red “X” will show. Clicking “Set prohibited node” can
specify the service trail to pass the NE, above which a green check mark
will show.
For the NE that has been set to be a necessary node or a prohibited node, it can be
cancelled by clicking “Cancel Necessary Node” or “Cancel Prohibited Node” in
the right-click menu.
Step 6 (Optional) double clicking the source and the sink of the trail can cancel
the selected source or sink and reselect.
Step 7 (Optional) if the level of the trail is VC12, then different encoding methods
can be selected, including “TS”, “Tributary” or “Moto”; under different
encoding methods, the number of VC12 is different.
Step 8 (Optional) click “Set Route Timeslot”. “Set Route Timeslot” dialog will
pop up. Select timeslot and click “OK”.

User's Manual
Step 9 Set general attributes of the trail, like name, remarks and etc.
Step 10 (Optional) set activation status of the trail, select “Active”.
 Activate the trail, service configuration data will be sent down to NE side.
 Deactivate the trail, service configuration data can only be saved at NMS
side.
Step 11 (Optional) if several trails of the same routing need to be created, select
“Copy After Creation” check box.
Step 12 Click “Apply”, a successful prompt will be shown, click “Close”.
11.4.2 SNCP Trail Creation

Prerequisites
in NE management system.
 There are spare timeslots on source and sink NEs.

159
User's Manual
Steps
Step 1 Select “Trail > SDH Trail Creation” in the main menu.
Step 2 Select the direction of the service and set the level of it.
 The direction of service could be unidirectional or bidirectional.
 The level of service could be “VC12”, “VC3” or “VC4”.
Step 3 Configure “Strategy”, set “Type” as “Common Trail”.
 Strategy is the principle for NMS to search available routes, which includes
“Shortest Route First” and “Smallest Load First”. “Shortest Route First”
means the number of passed NEs calculated from the source to the sink of
the trail is the fewest; “Smallest Load First” means the resources of available
timeslots calculated from the source to the sink of the trail is the largest.
 Trail type is classified to “Common Trail” and “Protection Trail”. “Common

Trail” is an unprotected trail; “Protection Trail” is a SNCP-protected trail.
Step 4 Double click the source and the sink NEs in turn. Select boards, ports and
timeslots in the “Select source”, “Select target” dialogs that pops up, and
then click “OK”. The trail automatically chosen by the system will display
between the source and the destination NEs, and the primary route is
marked with green and blue while the protection route is marked with
purple and yellow.
Step 5 (Optional) right click NE icon, and in the right-click menu that pops up,
the NE can be set to be a necessary node or a prohibited node of the trail.
Clicking “Set unnecessary node” can specify the service trail not to pass
the NE, above which a red “X” will show. Clicking “Set prohibited node”
can specify the service trail to pass the NE, above which a green check
mark will show. Click “Set protection node” can specify the protected trail
to pass the NE, above which a brown check mark will show.

User's Manual
For the NE that has been set to be a necessary node or a prohibited node, it can be
cancelled by clicking “Cancel main route necessary node”, “Cancel protection
node” or “Cancel Prohibited Node” in the right-click menu.
Step 6 (Optional) double clicking the source and the sink of the trail can cancel
the selected source or sink and reselect.
Step 7 (Optional) if the level of the trail is VC12, then different encoding methods
can be selected, including “TS”, “Tributary” or “Moto”; under different
encoding methods, the number of VC12 is different.
Step 8 (Optional) click “Set Route Timeslot”. “Set Route Timeslot” dialog will
pop up. Select timeslot and click “OK”.

161
User's Manual
Step 9 Set general attributes of the trail, like name, remarks and etc.
Step 10 (Optional) set activation status of the trail, select “Active”.
 Activate the trail, service configuration data will be sent down to NE side.
 Deactivate the trail, service configuration data can only be saved at NMS
side.
Step 11 (Optional) if several trails of the same routing need to be created, select
“Copy After Creation” check box.
Step 12 Click “Apply”, a successful prompt will be shown, click “Close”.
11.4.3 Bulk SDH Trail Creation

Prerequisites
 SDH trail has been created.

User's Manual
Steps
Step 1 Select “Trail > SDH Trail Management”. “Set Trail Browse Filter
Conditions” dialog will pop up.
Step 2 Set filter conditions in “Set Trail Browse Filter Conditions”, then click
“Filter”, trails will be shown in a list.
Step 3 Select a trail, right-click and select “Copy”, “Copy” dialog will pop up.
Step 4 In “Selected Source And Sink” pane, select source and sink boards after
trail copy.
Step 5 In “Available Timeslot/Port” pane, select source and sink timeslot after
trail copy. Click “Add”, in “Selected TimeSlot/Port” pane, the selected
timeslots and ports will be displayed.

163
User's Manual
 In “Available TimeSlot/Port” pane, multiple items can be selected.
 Only when the numbers of the selected source and sink timeslots are the
same can “Add” button become enabled from grayed state.
Step 6 In “Selected TimeSlot/Port” pane, selecting an item and clicking “Set

Route Timeslot” can modify the routing timeslot of the trail; clicking
“Delete” button can delete the selected trail.
Step 7 Select “Activated” check box, and click “OK”, a successful prompt will be
shown.
Step 8 Click “Close”.
11.5 SDH Trail Management

11.5.1 Browse SDH Trail
Prerequisites
 System monitors or users with higher permissions are required to log
 SDH trail has been created.
Steps
Step 1 Select “Trail > SDH Trail Management” in the trail view, “Set Trail
Browse Filter Conditions” dialog will pop up.

User's Manual
Step 2 Set filter conditions.
Step 3 Click “Filter”, the filtered trail information will be displayed in a list.
Step 4 Select a trail, and then the detailed information of it will be shown below.
Step 5 (Optional) click “Alarm” to view alarm information of the trail.
11.5.2 Deactivate SDH Trail

Prerequisites

165
User's Manual
Steps
Step 1 Select “Trail > SDH Trail Management” in the main menu.
Step 2 Select filter conditions in filter dialog, and click “Filter”.
Step 3 Select the SDH trail to be deactivated, right-click and select “deactivate” in
the shortcut menu. And click “OK” in the pop-up confirmation dialog.
Step 4 An “operation result” prompt box will pop up to indicate successful

operation.
Deactivating SDH trail will lead to service interruption, please be careful.
 If the deactivated SDH trail is reactivated, the attributes of the service

carried by the trail are the same as the ones before deactivating.
 If there is diagnosis task in the selected trail to be deactivated, then

deactivation is not allowed.
11.5.3 Delete SDH Trail

Prerequisites
 The SDH trail to be deleted is under unactivated state.
 The SDH trail to be deleted is under unlocked state.
Steps

User's Manual
Step 2 Select the SDH trail to be deleted, right click and select “Delete”. A
confirmation dialog will pop up.
 There are two ways to delete trail, as shown below:
− “Delete”: delete trail information in the network layer of NMS and

service information at NE side.
− “Network layer delete”: delete trail information in the network
layer of NMS. This command will not be sent down to NE and
affect service. After deleting the trail in the network layer, search
trail command can be executed, and then EzView will search out
trails again according to the service information in the NE layer.
 If there is diagnosis task in the selected trail to be deactivated, then
deactivation is not allowed.
Step 3 Click “OK” and send down delete trail command.
11.5.4 Lock SDH Trail

Prerequisites
Steps
Step 2 Select the SDH trail to be locked, right click and select “Lock”.
Step 3 Click “OK” in the pop-up confirmation window.
 A trail or several trails can be locked at one time.

167
User's Manual
EzView NMS 0
 After being locked, under single-station configuration, the cross connection

used by the trail cannot be activated, deactivated, deleted and modified. In
trail management page, select a trail and right click, menu items including
delete, activate, deactivate and network layer delete will become gray.
Step 4 (Optional) select the SDH trail to be unlocked, right click and select
“Unlock”.
Step 5 Click “OK” button in the pop-up confirmation window.
Step 6 Click “Close” in the pop-up “operation result” window.
11.6 Search SDH Trail

Prerequisites
 System maintainers or users with higher permissions are required to
log in NE management system.
 NE data has been uploaded to EzView.
 Fiber connection between NEs has been properly established.
The whole search process will not affect running service and configuration
data of NE, it only update the trail information of network layer on
EzView.
Steps
Step 1 Select “Trail > Search SDH Trail” in the main menu, “SDH Trail Search”
wizard will pop up.
Step 2 Click “Next” to start to search trail.
Step 3 The search process will continue for a period of time (The specific time
relates to the number of services). Please wait until the progress bar is

User's Manual
11 SDH Trail Management EzView NMS 168
updated, then click “Next” and now you can browse the trail information
that has been searched out. And you can sort the results as well.
Step 4 Select Management Symbol check box, management symbol can be set to
it.
The function of management symbol is to specify whether to include a trail to the

trail management of the network layer and manage it by default. If excluding to
the trail management of the network layer is selected, the cross connection of a
single NE can also be managed in single-station service configuration.
Step 5 Click “Next”. The trail without set management symbol searched out from
the network layer will be deleted by NMS (without affecting services at
NE side and data on NMS), at this time all the discrete services in the
network can be viewed (cross connection of trails cannot be formed).
Step 6 The search is completed, click “Finish”.
11.7 SDH Discrete Service Management

Prerequisites
System monitors or users with higher permissions are required to log in NE
management system.
Steps
Step 1 Select “Trail > SDH Discrete Service Management” in the main menu.
Step 2 A prompt dialog will pop up.

169
User's Manual
EzView NMS 11 SDH Trail Management
Step 3 Click “OK”, “Set Discrete Service Filter Conditions” dialog will pop up.
Step 4 Select filter conditions and click “Filter”.
Step 5 Detailed information of discrete services could be viewed in the window.

User's Manual
11.8 64K Trail Creation

11.8.1 64K Tail Creation
Create the 64K trail service by end to end, and realize the quick completion
of cross-service configuration.
Prerequisites
in NE management system
 There are spare 64K timeslots on the voice card of source and sink
NEs.
 The SDH trail has been created in the VC4:2 or Logic: 1 port on the
aggregation card of the H5600 series devices.
Steps
Step 1 Select “Trail > 64K Trail Creation” in the main menu.
Step 2 Service type: 64K and service direction: Bidirectional.
Step 3 Double click the source NE and the sink NE in turn. Select card (voice
card), ports and timeslots in the “Select Source”, “Select Sink” dialogs that
pops up, and then click “OK”. The trail automatically chosen by the system
will display between the source and the sink NEs.
Step 4 (Optional) you can cancel the selected source or sink and reselect them by
double-clicking the source and the sink of the trail.

171
User's Manual
Step 5 (Optional) The SDH Trail shows the SDH trail associated with the 64K
trail, which can be changed by clicking the “modify” button.
 If you activate the trail, the service configuration data will be sent to
the network element side.
 If you do not activate the trail, the service configuration data will be
only saved to the network management side.
11.9 64K Trail Management

11.9.1 Browse 64K Trail
Prerequisites
 System monitors or users with higher permissions are required to log
 64K trail has been created.
Steps
Step 1 Select “Trail >64K Trail Management” in the trail view, “Filter” dialog
will pop up.

User's Manual
Step 2 Set filter conditions.
Step 3 Click “Filter”, the filtered 64K trail information will be displayed in a list.
Step 4 Select a 64K trail, and then the detailed topology and service parameters of
it will be shown below.
11.9.2 Inactivate 64K Trail

Prerequisites
Steps
Step 1 Select “Trail > 64K Trail Management” in the main menu.
Step 2 Select filter conditions in filter dialog, and click “Filter”.
Step 3 Select the 64K trail to be inactivated, right-click and select “inactivate” in
the shortcut menu. And click “OK” in the pop-up confirmation dialog.

173
User's Manual
Step 4 “Succeeded” indicates successful operation.
Inactivating 64K trail will lead to service interruption, please be careful.
 If the inactivated 64K trail is reactivated, the attributes of the service carried
by the trail are the same as the ones before inactivating.
 If there is 64K diagnosis task in the selected 64K trail to be inactivated, you
cannot inactivate 64K trail.
11.9.3 Delete 64K Trail

Prerequisites
 The 64K trail to be deleted is under unactivated state.
Steps
Step 1 Select “Trail > 64K Trail Management” in the main menu.
Step 2 Select the 64K trail to be deleted, right click and select “Delete”. A
confirmation dialog will pop up.
 There are two ways to delete 64K trail, as shown below:
− “Delete”: delete 64K trail information in the network layer of

NMS and service information at NE side.
− “Network layer delete”: delete 64K trail information in the
network layer of NMS. This command will not be sent down to
NE and affect service. After deleting the 64K trail in the network

User's Manual
layer, search 64K trail command can be executed, and then

EzView will search out 64K trails again according to the service
information in the NE layer.
 If there is 64K diagnosis task in the selected 64K trail to be deleted, it cannot
be deleted.
Step 3 Click “OK” and send down delete trail command.
11.10 Search 64K Trail

Prerequisites
 System maintainers or users with higher permissions are required to
 NE data has been uploaded to EzView.
 Connection between NEs has been properly established.
The whole search process will not affect running service and configuration
data of NE, it only update the 64K trail information of network layer on
EzView.
Steps
Step 1 Select “Trail > 64K Trail Search” in the main menu, “64K Trail Search”
wizard will pop up.
Step 2 Click “Next” to start to search trail.
Step 3 The search process will continue for a period of time (The specific time
relates to the number of services). Please wait until the progress bar is
updated, then click “Next” and now you can browse the 64K trail
information that has been searched out. And you can sort the results as
well.
Step 4 Select Is Managed check box, management symbol can be set to it.

175
User's Manual
The function of management symbol is to specify whether to include a trail to the

trail management of the network layer and manage it by default. If excluding to
the trail management of the network layer is selected, the cross connection of a
single NE can also be managed in single-station service configuration.
Step 5 The search is completed, click “Finish”.
11.11 Customer Management

11.11.1 Create Customers
Prerequisites
Steps
Step 1 Select “Trail > Customer Management” in the main menu to enter
“Customer Management” window.
Step 2 Click “Create”, then a new customer information bar will appear in the
customer list.
Step 3 Fill in the new customer information according to the actual need,
including “Customer Name”, “Legal Representative”, “Phone” and etc.,
then click “Apply”.
When “Customer Name” is repeated, a prompt will pop up.
Step 4 (Optional) right click on the title bar of the list, select “Customer Extend
Information Setting” to add and extend the list.

User's Manual
Step 5 Click “Close” in the pop-up “Operation Result” dialog.
11.11.2 Configure Customer of Trails

Prerequisites
 Trails have been created.
 Customers have been created.
Steps
Step 2 Set filter conditions and get the needed trails in the trail list.
Step 3 Select trails in the trail list, right click and select “Details”.
Step 4 Select appropriate customers in the dropdown “Customer” box in “Details”

dialog.

177
User's Manual
Step 5 Click “OK”.

User's Manual
12 Ethernet Trail Management
Through network-level functions of EzView, Ethernet trail and service can

be created and managed rapidly from end to end. Compared with single
station configuration, end-to-end method is more rapid and convenient.
Ethernet end-to-end management uses network-level management function

of EzView to realize end-to-end management of Ethernet service. Through
Ethernet end-to-end management function, the user can do the following
operations:
 Configure end-to-end service.

 View graphic interfaces and virtual routers of trails.
 Query detailed trail information.
 Rapidly filter, search and locate trails.
 Centrally manage and maintain trails.
 Manage alarms through trail.
 Print trail report.
Operations and displays of Ethernet end-to-end management are fulfilled

under graphic wizard, which make operation process more intuitive.
Ethernet trail supports semi-automatic, automatic and manual creation.
 Under automatic method, it only needs to specify the source and

destination nodes of trail and port.
 Under semi-automatic method, the user can specify the router and
label that the trail will pass through.

179
User's Manual
 Manual method means the routers and labels that the trail passes
through are all specified by the user.
End-to-end management is the core function of EzView network-level

functions. Using trail management method to configure services greatly
simplifies service configuration operations and reduces operation error
probability.
If there is no end-to-end management function, the process of configuring

a trail is a completely manual process, for example, if configure a circuit of
a 2M circuit from one NE land from the Nth NE after passing through N
NEs, it needs to configure Tunnel cross-connection on these N＋1 NEs.
If there is end-to-end management function, configure a circuit like that

can be as simple as ignoring the N － 1 nodes in-between and just
specifying the source and destination ports of the circuit, and then EzView
can generate a circuit automatically.
Trail function’s impact on system performance: under the condition of

satisfying the requirements of EzView capability (specifically shown by
model, NE managed by EzView, the number of trails and etc.), Ethernet
end-to-end management does not have a significant impact on system
performance. If EzView is at full strength, system performance must be
affected. Trail function’s impact on other features: SDH end-to-end trail
management relies on fiber configuration.
12.1 Theory Description

A brief introduction of Ethernet end-to-end trail automatic creation theory:
 Select the source and sink of the trail on EzView interface.

 EzView automatically calculates the routing of the trail and display it
on the interface.
 After checking the routing of the trail, confirm to create the trail.

User's Manual
 EzView creates the trail according to its source/sink and routing,

calculates the corresponding NE and port, and then send to NE to
create a trail.
Thus, an end-to-end Ethernet trail will be created out on EzView, and at the
same time services are automatically sent to NE to be created.
12.2 Principles of Creating Trail

Creating Ethernet service by single station configuration is very
cumbersome and easy to make mistakes, so creating service by trail
function of EzView is recommended.
Principles of creating Ethernet trail service:
 The source and sink ends of trail service cannot choose the same
network element.
 The failed trail service can be activated and recreated after being
deleted, and can be activated once more.
 In the single station, you must configure layer-3 port, layer-3 port
address and LSR ID.
12.3 Service Management Process

This section introduces how to use the end-to-end way to manage IP
service, and the relationship between each operation task. Meanwhile, it
provides the operation task’s corresponding chapter and interface entrance.
IP service is adapted to H20PN series NE. For different types of network

elements, the IP service management processes are slightly different
(Prerequisites in different NEs are not the same, some IP service function
are only supported by some NEs). In the following part, we will introduce
preparations, service deployment, service monitoring and maintenance
flow chart of each NE. At the same time, we provide tables to explain the
tasks in the process chart.

181
User's Manual
Flow Chart of IP Service Management

User's Manual
12.4 Related Concepts

12.4.1 Tunnel Introduction
Ezview supports MPLS Tunnel based on MPLS protocol encapsulation.
MPLS Tunnel
MPLS (Multi-Protocol Label Switching) is a transmission technology,
which can realize transparent transmission of data service packet between
users. MPLS Tunnel is the Tunnel defined by MPLS protocol. MPLS

183
User's Manual
Tunnel is independent from service, which can realize end-to-end

transmission and provide channels for PW.
MPLS Tunnel is used as service transmission channel in network, as shown

in Figure 12-1.
Figure 12-1 MPLS Tunnel in MPLS network
MPLS Tunnel has nothing to do with the service encapsulated in PW, it

provides only one channel from local to the remote site. After the data
service packets are encapsulated into PW (Pseudo Wire), they will be
added MPLS tag and sent to MPLS Tunnel for transmission, in sink end,
data service packets are recovered and keep the original features. MPLS
Tunnel has Ingress node and Egress node on both ends and Transit node in
the middle node.
According to signaling types, MPLS Tunnel can be divided into 4 types of

Tunnel: static, static CR, RSVP TE (Resource Reservation Protocol-Traffic
Engineering) and LDP (Label Distribution Protocol). Differences among
those 4 types Tunnel are as follows:
 Static: The tag in static Tunnel is assigned by hand, without using the
signaling protocol, no need to mutual controlled packet.
 Static CR: Static CR Tunnel is created on the basis of certain
constraints, the mechanism of creation and management is called CR

User's Manual
(Constraint-based Routing), is constraint-based route. Different from

static Tunnel, static Tunnel CR is not only dependent on routing
information, but also satisfying other conditions, such as the specified
bandwidth, selected trail or QoS parameters.
 LDP: Only specify the source/sink nodes, LDP protocol automatically
calculates Tunnel routing, Tunnel LDP can run in any network
supporting MPLS domain, more flexible.
 RSVP TE: Only specify the source/sink nodes, MPLS protocol
automatically calculates the Tunnel route, you can also use the
specified constraints node to plan specific route which Tunnel passes
through. RSVP TE Tunnel can configure FRR protection and QoS
function, safer and more flexible than LDP.
At present, device only supports static Tunnel.
12.4.2 Tunnel Protection Group Introduction

MPLS Tunnel APS (Automatic Protection Switching) is a kind of network
protection mechanism, which protects service transmitted by working
MPLS Tunnel through protection MPLS Tunnel. When a working MPLS
Tunnel fails, service will be switched to the protection MPLS Tunnel, so as
to protect the service in working Tunnel. PTN device supports 1+1 and 1:1
MPLS Tunnel APS.
Basic Concepts
APS
APS protocol is used to coordinate the operation between the source and
sink during bidirectional protection switching, making the source and sink
work together to realize protection switching, switching delay and waiting
for recovery functions.
APS protocol is fixed to be sent in protection channel, thus the devices on

both sides know the channel which receives APS protocol packet is the
protection channel of each other’s, so as to judge whether the working
channel and the protection channel on both sides are configured
consistently.

185
User's Manual
Switching mode
MPLS Tunnel APS has two switching modes; they are single-end
switching and dual-end switching. Only dual-end switching is supported by
our device at present.
Single-end switching: when a working channel to a certain direction fails,

only the service to that direction will be switched to a protection channel.
Dual-end switching: when a working channel to a certain direction fails,

according to APS protocol, the service on dual directions of working
channel will be switched to a protection channel.
Recovery mode
The protection recovery of MPLS Tunnel APS has two modes: recovery
and non-recovery.
Under non-recovery mode, the service will not be switched from protection
channel to working channel even if the working channel recovers normally.
Under recovery mode, the service will be switched from protection channel
to its original working channel after the working channel recovering time
reaches wait to restore time.
WTR (Wait to restore) time
After the working channel is repaired, the protection channel needs to be

switched to working channel, the time for finishing which is called wait to
restore time.
In some certain scenarios, working Tunnel is not steady; in this case,

setting WTR time can avoid switching service from working Tunnel to
protection Tunnel frequently.
WTR time is 5 minutes by default.
Delay time
The time from detecting fault to switching is called delay time.

User's Manual
When the device configures MPLS APS and other protections, setting
delay time can ensure other protection switchings are performed firstly.
The delay time is 0s by default.
1+1 protection
In 1+1 protection group, service is dual-sent by source end, but selected to

be received by sink end. When the working channel fails, service
receiving-end uses protection channel to receive service, so as to realize
service switching.
1:1 protection
In 1:1 protection group, service is transmitted through working channel,

when the working channel fails, it will be switched to protection channel.
Service is single-sent and single-received.
Tunnel protection group application
According to the protected Tunnel type, Tunnel protection group creates

the Tunnel in the same type to conduct protection in 1+1 or 1:1 way. When
the working Tunnel fails, Tunnel protection group ensures service transmits
normally.
Through NMS, user can configure 1+1 and 1:1 protections to Tunnel which
bears important service.
12.4.3 PWE3 Introduction

PWE3 belongs to edge to edge layer-2 VPN (Virtual Private Network)
technology. PWE3 (Pseudo-Wire Emulation Edge to Edge) stipulates the
multi-hop negotiation method, making the networking mode is more
flexible.
Definition
PWE3 is a kind of layer-2 service bearing technology which used in PSN

(Packet Switched Network). It imitates the basic behaviors and
characteristics of the ATM, frame relay, Ethernet, low-speed CES circuit

187
User's Manual
and SONET (Synchronous Optical Network)/SDH (Synchronous Digital

Hierarchy).
Purpose
With the development of IP data network, the IP network has strong

abilities in expansion, upgrade and compatibility. The traditional
communication network is relatively poorer in expansion, upgrade and
compatibility. Limited by the transmission mode and service type, as well
as newly-built network is poor in sharing; traditional communication
network is not suitable for interoperability management. Therefore, in the
process of upgrading and developing the traditional communication
network, we should consider whether to establish the duplicate network or
make full use of the existing or public network resources. PWE3 is one of
the solutions provided by combining the traditional communication
networks and the existing packet networks.
When the PWE3 protocol is not steady in network, we can reduce the
number of packet interaction to avoid building or deleting PW repeatedly.
PWE3 technology has some inherent advantages of MPLS L2VPN;

besides, we can use PWE3 technology to interconnect traditional network
and packet switching network, so as to realize the resource sharing and
network expansion.
12.4.4 VPLS Introduction

VPLS is a layer-2 VPN technology based on MPLS and Ethernet
technology. VPLS can realize multipoint to multipoint VPN networking. It
provides a more complete solution for operators who use point-to-point
L2VPN service before, it can also avoid managing user internal routing
information like L3VPN.
Purpose
VPLS, also known as TLS (Transparent LAN service) or Virtual Private

Switched Network Service is a layer-2 VPN technology based on MPLS
and Ethernet technology.

User's Manual
Purpose
The main purpose of VPLS is to connect multiple Ethernet LANs through

PSN (packet switching network), making them work like one LAN. VPLS
can achieve multi-point to multi-point VPN networking. Through VPLS
technology, service providers can provide users with Ethernet-based
multi-point service through MPLS backbone network. Using MPLS virtual
link as Ethernet bridge link can provide transparent transmission LAN
service through MPLS network.
12.5 Automatic Search IP Service

After a new network is built or using single station in network element to
configure service, we can perform automatic search IP service operation,
add single point information to the network management service interface,
so as to do end to end management towards these single point services.
Prerequisites
 Service information does not exist in NM service management, but
exists on NE.
 NE has been added to NMS, and network data is synchronized.
Steps
Step 1 Select “Trail>Automatic Search IP Service” in the main menu, “Automatic
Search IP Service” wizard will pop up.

189
User's Manual
Step 2 Set search strategy.
In the Search Strategy tab, specify the setting range, service type, customer
strategy and service search strategy for the IP service.
Main parameters Configuration method
Search in the whole Search all the NEs managed by EzView in the
network whole network
Select NE Perform automatic search operation of

combination service to the specified NE

User's Manual
Main parameters Configuration method
Customer strategy Customer is one of the properties of the IP

service, which is used to identify the customer of
the service. If we do not set customer,
automatically-searched services will not be
related to any customer. If we set customer, all
the automatically-searched
services will be related to this customer
Step 3 Perform automatic search operation.
After finishing the configurations above, click “Start” to perform automatic

search IP service operation.
Step 4 View search result.
In “Search Result” tab, we can view automatically-searched IP service.

191
User's Manual
12.6 Deploy Tunnel

12.6.1 Create A Piece of Tunnel
We can create a piece of reverse Tunnel when creating the Tunnel.
Prerequisites
 LSR ID of NE has been configured.
 Layer-3 port information of NE has been configured.
Steps
Step 1 Select “Trail>Tunnel>Create Tunnel” in the main menu.
Step 2 Configure protocol type, signaling type and protection type of Tunnel.
Step 3 Click the “Select Source and Sink” button, in the pop-out dialog box, select
source and sink NEs, click the arrow to the right, and then click “OK”.

User's Manual
The selected NEs display in the right topology diagram. In “Node Role”,
set the NE location in Tunnel.
Step 4 Selectable: the route constraints of Tunnel.
When creating a Tunnel, if the data layout specifies the necessary node or
prohibited node of Tunnel, we need to configure route constraints of Tunnel. If not,
we just need to select source and sink NE of Tunnel, no route constraints setting.
Click “Route Constraints” button, we can click “Add” button to add

necessary node and interface. After setting, click “OK” button.

193
User's Manual
EzView NMS 0
Step 5 Selectable: click “Detailed” to configure the detailed information for

Tunnel, such as tag, QoS and etc.
Step 6 Selectable: click “Configure OAM” to configure the OAM detailed

information for Tunnel. Currently, only the OAM information on source
and sink NEs can be configured.

User's Manual
12 Ethernet Trail Management EzView NMS 194
Step 7 Click OK. After creating successfully, we can view result in “Tunnel
Management”.
12.6.2 Create Tunnels in Bulk

This section introduces how to create Tunnels in bulk. When creating
Tunnels towards multiple network elements, we need to create Tunnels in
bulk.
Prerequisites

195
User's Manual
EzView NMS 12 Ethernet Trail Management
Steps
Step 1 Select “Trail>Tunnel>Create Tunnel” in the main menu.
Step 2 Refer to Step 2~Step 6 of “Create a Tunnel”; select source and sink NEs
and then configure each parameter.
Step 3 Check “Copy After Creation” on the bottom left of the interface.
Step 5 After creating the first Tunnel, NMS will automatically pop out the Tunnel
copy window.
Step 6 Click “OK”, when the state list shows Success, close the window, Tunnels
are created in bulk.

User's Manual
12.6.3 Modify Tunnel

After creating Tunnel, we can modify configuration parameters in Tunnel
Management, including QoS, OAM and etc.
Prerequisites
End-to-end Tunnel is created successfully.
Steps
Step 1 Select “Trail>Tunnel>Tunnel Management” in the main menu.
Step 2 In the pop-out “Filter” window, click “Filter”.

197
User's Manual
Step 3 Modify QoS of end-to-end Tunnel.
a) Select a piece of Tunnel in Tunnel list, and then select “QoS Info” tab.
b) After modifying QoS parameters, click “Apply”.
Step 4 Modify OAM of end-to-end Tunnel.
a) Select a piece of Tunnel in Tunnel list, and then select “Configure

OAM” in right-key menu.
b) After modifying OAM parameters, click “OK”.

User's Manual
12.6.4 Demolish Tunnel

When we convert end-to-end Tunnel from deployed to undeployed state,
we need to demolish Tunnel.
Prerequisites
 Tunnel which will be demolished has no service in deployed state.
 Tunnel which will be demolished does not belong to APS protection
group in arbitrary deployment.

199
User's Manual
Steps
Step 3 In the Tunnel list, right-click Tunnel to select “Demolition”, and then click
“OK” in the pop-out window.
Step 4 In the “Operation Result” dialog box, click “Close”.
12.6.5 Delete Tunnel

Delete unnecessary Tunnel to release network resources.
Prerequisites
 Tunnel which will be deleted is under “Demolition” state.
 There is no service exists on Tunnel which will be deleted.
 Tunnel which will be deleted does not belong to APS protection group
in arbitrary deployment.
Steps
Step 3 In the Tunnel list, right-click Tunnel to select “Delete”, and then click
“OK” in the pop-out window.
 There are two ways to delete Tunnel:
1) “Delete”: Delete the information from the NM network layer and NE side.
Deleting the trail will interrupt the service, please caution on using it.

User's Manual
2) “Delete from Network Layer”: Delete the information from the NM network
layer. This command will not be sent to NE, so it won’t affect service. When
deleting this Tunnel in network layer, we can use automatic search IP service,
and EzView will search out the Tunnel according to information in NE
layer.
 If the Tunnel which will be deleted is in activation state, we need to

demolish it before deleting. If we delete from network layer, no need to do
this operation.
12.6.6 Create Tunnel Protection Group

Create Tunnel protection group. When master Tunnel fails, protection
group will switch the service in master Tunnel to protection Tunnel, so as
to guarantee service reliability.
Prerequisites
Ensure that the working Tunnel and protection Tunnel used in protection
has been created successfully, and the OAM parameters in Tunnel are
configured correctly.
Steps
Step 1 Select “Trail>Tunnel>Create Protection Group” in the main menu.

201
User's Manual
Step 2 Configure “Protection Type” and “Reverse Mode”.
Step 3 Click “Add”, and then select working Tunnel and protection Tunnel.
Step 4 In Tunnel table, select “Positive Working” and “Positive Protection” in

drop-down list of “Tunnel Type”.
Step 5 (Selectable) configure the attribute of Tunnel protection group, such as

“Revertive” mode, “WTR Time (s)” and etc.
Step 6 Click “Apply” to finish configuring Tunnel protection group.
12.6.7 Execute Tunnel Protection Group Switch

In Tunnel Protection Group Management page, we can view the working
state of protection group and configure protection group switch according
to actual needs, so as to guarantee normal transmission for data service.
Prerequisites
 End-to-end Tunnel protection group has been created successfully.
 Protection group is in Deployed state.
Steps
Step 1 Select “Trail>Tunnel>Protection Group Management” in the main menu.
Step 3 Select protection group and right click it, select “Switch>Force Switch” in
right-click menu. Protection group will execute the corresponding switch
action.

User's Manual
12.6.8 Demolish Tunnel Protection Group

When we convert end-to-end Tunnel protection group from deployed to
undeployed state, we need to demolish Tunnel protection group.
Prerequisites
Tunnel protection group which will be demolished has no service.
Steps
Step 1 Select “Trail>Tunnel>Protection Group Management” in the main menu.

203
User's Manual
Step 3 In the Tunnel protection group list, right-click Tunnel protection group to
select “Demolition”, and then click “OK” in the pop-out window.
12.6.9 Delete Tunnel Protection Group

Before deleting Tunnel, we must delete the protection group on the tunnel.
We can release network resources by deleting unnecessary Tunnel
protection group.
Prerequisites
 Tunnel protection group which will be deleted is under “Demolition”
state.
 There is no service exists on Tunnel protection group which will be
deleted.
Steps
Step 1 Select “Trail>Tunnel> Protection Group Management” in the main menu.

User's Manual
Step 3 In the Tunnel protection group list, right-click Tunnel protection group to
select “Delete”, and then click “OK” in the pop-out window.
 There are two ways to delete Tunnel protection group:
deleting this Tunnel protection group in network layer, we can use automatic
search IP service, and EzView will search out the Tunnel protection group
according to information in NE layer.
 If the Tunnel protection group which will be deleted is in activation state, we

need to demolish it before deleting. If we delete from network layer, no need
to do this operation.

205
User's Manual
12.7 Deploy PWE3 Service

12.7.1 Create A Piece of ETH Service
This section introduces how to create a piece of Ethernet service on PTN
device.
Prerequisites
 Tunnel service has been configured on device.
Steps
Step 1 Select “Trail>PWE3 Service>Create PWE3 Service” in the main menu.
Step 2 Configure protection type, description, customer and comment of ETH

private service.
source and sink NEs, click the arrow to the right, select the port used in
connections in source and sink NEs, and then click “Add Node” in
“Service Interface Configuration”, at last, click “OK”.

User's Manual
Step 4 The selected NEs display in the right topology diagram. In “Node Role”,
set the locations of source and sink NEs in “Location”.
Step 5 Select the basic information of created service in WP, and then right click
Positive Tunnel/Negative Tunnel, we can modify Tunnel which is related
to Positive/Negative Tunnel.
Step 6 Selectable: click “Detailed” button to configure the detailed information of

PWE3, such as PW QoS service parameters.
Step 7 Click “OK” to finish configuration, we can view the result in “PWE3
Service Management” page.
12.7.2 Create ETH Service in Bulk

This section introduces how to create ETH service in bulk. When creating
multiple dynamic PWE3 towards the same network elements, we need to
create PWE3 service in bulk.
Prerequisites

207
User's Manual

Steps
Step 1 Select “Trail>PWE3 Service>Create PWE3 Service” in the main menu.
Step 2 Refer to Step 2~Step 6 of “Create a piece of ETH service”; select source
and sink NEs and then configure each parameter.
Step 5 After creating the first PWE3 service, NMS will automatically pop out the
PWE3 copy window. After entering the copy numbers of PWE3, select
“Tunnel Select Strategy”, click “Apply”.
Step 6 Click “OK”, when the state list shows Success, close the window, PWE3
services are created in bulk.

User's Manual
12.7.3 Create CES Service

12.7.3.1 Create A Piece of CES Service
This section introduces how to create a piece of CES service on PTN
device.
Prerequisites
Steps
Step 1 Select “Trail>PWE3 Service>Create PWE3 Service” in the main menu,
select CES for service type.

209
User's Manual
Step 2 Click Yes!
Step 3 Configure protection type, description, customer, comment of CES service.
source and sink NEs, click the arrow to the right, select the port used in
connections in source and sink NEs, and then click “Add Node” in
“Service Interface Configuration”, at last, click “OK”.

User's Manual
Step 5 The selected NEs display in the right topology diagram. In “Node Role”,
set the locations of source and sink NEs in “Location”.

211
User's Manual
Step 6 Selectable: click “Detailed” button to configure the detailed information of

CES, such as CE QoS service parameters.
Step 7 Click “OK” to finish configuration, we can view the result in “PWE3
Service Management” page.
12.7.3.2 Create CES Service in Bulk

This section introduces how to create CES service in bulk. When creating
multiple CES to the same network elements, we need to create CES service
in bulk.
Prerequisites
Steps
Step 1 Select “Trail>PWE3 Service>Create PWE3 Service” in the main menu,
select CES for service type.
Step 2 Refer to Step 2~Step 6 of “Create a piece of CES service”; select source
and sink NEs and then configure each parameter.
Step 5 After creating the first CES service, NMS will automatically pop out the
CES copy window. After entering the copy numbers of CES, click “OK”.

User's Manual
Step 6 Click “OK”, when the state list shows Success, close the window, CES
services are created in bulk.
12.7.4 Modify PWE3 Service

After creating PWE3 service, we can modify PWE3 configuration
parameters in PWE3 Service Management, such as QoS, OAM and etc.
Prerequisites
 End-to-end Tunnel is created successfully.
 End-to-end PWE3 (ETH/CES) service is created successfully.

213
User's Manual
Steps
Step 1 Select “Trail>PWE3 Service>PWE3 Service Management” in the main
menu.
Step 2 Modify end-to-end PWE3 QoS.
a) Select a piece of PWE3 service in PWE3 list, and then select

“PW>QoS Info”.
Step 3 Modify end-to-end PWE3 OAM.
a) Select a piece of PWE3 service in PWE3 list, and then select

“PW>Base Property”.

User's Manual
b) Select one property, and then click Configure OAM. Modify the OAM
parameters and click OK.
12.7.5 Demolish PWE3 Service

When we convert end-to-end PWE3 service from deployed to undeployed
state, we need to demolish PWE3 service.
Prerequisites
 End-to-end Tunnel is created successfully.
 In end-to-end PWE3 service management interface, there exists
PWE3 service.

215
User's Manual
Steps
menu.
Step 3 In the PWE3 service list, right-click PWE3 service to select “Demolition”,
and then click “OK” in the pop-out window.
12.7.6 Delete PWE3 Service

Delete unnecessary PWE3 service to release network resources.
Prerequisites
PWE3 service which will be deleted is under “Demolition” state.
Steps
menu.
Step 3 In the PWE3 service list, right-click PWE3 service to select “Delete”, and
then click “OK” in the pop-out window.
 There are two ways to delete PWE3:
deleting this PWE3 in network layer, we can use automatic search IP service,
and EzView will search out the PWE3 according to information in NE layer.

User's Manual
 If the PWE3 which will be deleted is in activation state, we need to demolish

it before deleting. If we delete from network layer, no need to do this
operation.
12.8 Deploy VPLS Service

12.8.1 Create VPLS Service
12.8.1.1 Create A Piece of VPLS Service
This section introduces how to create a piece of VPLS service on PTN
device.
Prerequisites
Steps
Step 1 Select “Trail>VPLS Service>Create VPLS Service” in the main menu.

217
User's Manual
Step 2 Select the signaling type, network type and service type of VPLS service.
Step 3 Click the Add button and select NPE, in the pop-out dialog box, select
NPE NE (H-VPLS), and then click the right arrow, at last, click OK.
Step 4 Click the Add button and select UPE, in the pop-out dialog box, select
UPE NE, and then click the right arrow, at last, click OK.

User's Manual
Step 5 Select an NE in the node list, click Detailed button, open Service Interface
Configuration page, click Create button, and then type in the vlan
information and click OK button.

219
User's Manual
Step 6 Use the same way to add the service interface to each NE.

User's Manual
Step 7 Optional: in PW Configuration page, right-click Positive Tunnel/Negative

Tunnel, you can modify the related positive Tunnel and negative Tunnel.
Double-click Positive Label/Negative Label, you can modify the service
label. Optional: in PW QoS page, you can configure PW QoS information.
Step 8 Optional: in VSI configuration page, select MAC address learn configure
button, you can configure MAC address learn parameters.
Step 9 Optional: you can modify service name, customer and comment according
to your needs.
Step 10 At last, click OK button, you can view the configuration result in VPLS
Service Management page.
12.8.1.2 Create VPLS Service in Bulk

This section introduces how to create VPLS service in bulk, which is used
when you need to create many dynamic VPLS service in the same NE.
Prerequisites
Steps
Step 1 Select “Trail>VPLS Service>Create VPLS Service” in the main menu.
Step 2 Refer to 12.8.1.1 Create A Piece of VPLS Service Step 2~Step 10, and
then select NE port and configure each parameter.
Step 3 Select the “Copy after creation” check box.
Step 4 Click OK.
Step 5 After creating the first VPLS service, the NMS will pop up VPLS copy
window. After typing in copy numbers of VPLS, click Apply. Select VPLS
service, and edit service parameter information in Details.

221
User's Manual
Step 6 Click OK button. After you see Success in all State lists; please close the
window.
12.8.2 Modify VPLS Service

After configuring VPLS service, you can modify VPLS parameters, QoS,
interface, MAC address learn parameters in VPLS Service Management
page.
Prerequisites
 End-to-end VPLS service is created successfully.

User's Manual
Steps
Step 1 Select “Trail>VPLS Service>VPLS Service Management” in the main
menu, and then click Filter button.
Step 2 Modify QoS of end-to-end VPLS.
a) Select a piece of VPLS service in VPLS list, and then select

“PW>QoS”.
Step 3 Modify service interface of end-to-end VPLS.
a) Select a piece of VPLS service in VPLS list, and then select “Service
Interface >Base Property”.
b) If you do not need some interface, you can select it and click Delete
button to delete it.

223
User's Manual
c) Click Create button to create a new service interface, and then click
OK button.

User's Manual
Step 4 Modify VSI of end-to-end VPLS.
a) Select a piece of VPLS service in VPLS list, and then select

“VSI>VSI Base Property”.
b) If you do not need some VSI node, you can select it and click Delete
button to delete it.
c) Click Create button to create a new VSI, select the NE and click the
right arrow, and then modify the node role according to your need, at
last, click OK button.

225
User's Manual
Click Create button in the Service Parameter page.
After selecting the NE, click OK button.

User's Manual
Select the card, port and type in vlan parameters, and then click OK button.

227
User's Manual
Click OK button to finish adding VSI.
Step 5 Modify MAC address learn parameters of end-to-end VPLS service.
a) Select a piece of VPLS service in VPLS list, and then select “VSI>
MAC address learn configure”.
b) After modifying the MAC address learn parameters, click Apply

button.
12.8.3 Demolish VPLS Service

When we convert end-to-end VPLS service from deployed to undeployed
state, we need to demolish VPLS service.

User's Manual
Prerequisites
 In end-to-end VPLS service management interface, there exists VPLS
service.
Steps
menu.
Step 3 In the VPLS service list, right-click VPLS service to select “Demolition”,
12.8.4 Delete VPLS Service

Delete unnecessary VPLS service to release network resources.
Prerequisites
VPLS service which will be deleted is under “Demolition” state.
Steps
menu.
Step 3 In the VPLS service list, right-click VPLS service to select “Delete”, and
 There are two ways to delete VPLS:

229
User's Manual
deleting this VPLS in network layer, we can use automatic search IP service,
and EzView will search out the VPLS according to information in NE layer.
 If the VPLS which will be deleted is in activation state, we need to demolish

it before deleting. If we delete from network layer, no need to do this
operation.
12.9 Deploy Convergence Service

12.9.1 Create A Piece of Etree Service
This section introduces how to create a piece of Etree service on PTN
device.
Prerequisites
Steps
Step 1 Select “Trail>Convergence Service>Create Etree Service” in the main
menu.

User's Manual
Step 2 Click the Add button and select Source, in the pop-out dialog box, select
NE, and then select service interface and type in vlan parameter, at last,
click OK.
Step 3 Use the same way to add the service interface of multiple source NE.
Step 4 Click the Add button and select Sink, in the pop-out dialog box, select NE,
and then select service interface and type in vlan parameter, at last, click
OK.

231
User's Manual
Step 5 NMS will automatically calculate the service trail.
Step 6 Optional: in PW Configuration page, right-click Positive Tunnel/Negative

Tunnel, you can modify the related positive Tunnel and negative Tunnel.
Double-click Positive Label/Negative Label, you can modify the service
label.

User's Manual
Step 7 Optional: in PW QoS page, you can configure PW QoS information.
Step 8 Optional: select MAC address learn configure page, you can configure
MAC address learn parameters.
Step 9 Optional: you can modify service name, customer and comment according
to your needs.
Step 10 At last, click OK button, you can view the configuration result in ETREE
Service Management page.
12.9.2 Modify Etree Service

After configuring Etree service, you can modify Etree parameters, QoS,
interface, MAC address learn parameters in Etree Service Management
page.
Prerequisites
 End-to-end Etree service is created successfully.
Steps
Step 1 Select “Trail>Convergence Service>ETREE Service Management” in the
main menu, and then click Filter button.
Step 2 Modify QoS of end-to-end Etree service.

233
User's Manual
a) Select a piece of Etree service in Etree list, and then select

“PW>QoS”.
Step 3 Modify service interface of end-to-end Etree service.
a) Select a piece of Etree service in Etree list, and then select “Service
Interface >Base Property”.
b) If you do not need some interface, you can select it and click Delete
button to delete it. Note that you can only delete source NE interface.
c) Click Create button and select Source, in the pop-out page, select NE,
interface and type in vlan parameters, and then click OK button.

User's Manual
In the pop-out page, you can modify PW parameters, after that, click OK
button.
Step 4 Modify MAC address learn parameters of end-to-end Etree service.
a) Select a piece of Etree service in Etree list, and then select “MAC
address learn configure”.
b) After modifying the MAC address learn parameters, click Apply

button.

235
User's Manual
12.9.3 Demolish Etree Service

When we convert end-to-end Etree service from deployed to undeployed
state, we need to demolish Etree service.
Prerequisites
 In end-to-end Etree service management interface, there exists Etree
service.
Steps
main menu.
Step 3 In the Etree service list, right-click Etree service to select “Demolition”,
12.9.4 Delete Etree Service

Delete unnecessary Etree service to release network resources.
Prerequisites
Etree service which will be deleted is under “Demolition” state.
Steps
main menu.
Step 3 In the Etree service list, right-click Etree service to select “Delete”, and

User's Manual
 There are two ways to delete Etree service:
deleting this Etree in network layer, we can use automatic search IP service,
and EzView will search out the Etree according to information in NE layer.
 If the Etree service which will be deleted is in activation state, we need to

demolish it before deleting. If we delete from network layer, no need to do
this operation.

237
User's Manual
13 Synchronization and Data

Management
This chapter will introduce corresponding operations of synchronizing NE

time, current alarm, configuration data and data management.
13.1 Synchronize NE Time

It introduces how to synchronize times of H9MO-LMESE device and
NMS.
Prerequisites
Before set NE time synchronization, please make sure that the machine time of the
server is accurate, and if it needs to be modified, please log out NMS first and
reset the machine time, and then restart NMS.
The occurring times of alarms and performance events mean a great deal to
maintenance and troubleshooting. If the times of NE and NMS are
different, it will lead to untimely handling of problems and then cause
financial losses. Therefore, NE time and NMS time should keep consistent.

User's Manual
Steps
Method 1
Step 1 Select “Config> NE Time Synchronization” in the main menu.
Step 2 Select the NE that needs to be set in the left object tree and click .
Step 3 Click “Query” to query NE time in the list.
Step 4 Either of the following two ways can complete the synchronization of NE
time and NMS time:
 Select one or several NEs, right click and select “NE Time
Synchronization”.
 Select the NE that needs to be synchronized, select the execution time
of automatic synchronization in “Synchronization Starting Time” and
select the execution period of automatic synchronization in
“Synchronization Period (days)”, then click “Apply”.
Step 5 “Operation result” dialog will pop up, and the setup is completed.
After selecting the NE that has enabled auto synchronization function, “cancel
auto synchronization” button becomes available from grayed state, by clicking
which, the auto synchronization function of NE time can be cancelled.

239
User's Manual
Method 2
Step 1 Select NE in NE manager and “Config> NE time synchronization” in the

function tree.
Step 2 Click “Query” to query the time of NE.
Step 3 Either of the following two ways can complete the synchronization of NE
time and NMS time:
 Select NE, right click and select “NE Time Synchronization”.

 Select the execution time of automatic synchronization in
“Synchronization Starting Time” and select the execution cycle of
auto synchronous in “Synchronization Period (days)”, then click
“Apply”.
Step 4 “Operation result” dialog will pop up, and the setup is completed.
After selecting the NE that has enabled auto synchronization function, “Cancel
Auto Sync” button becomes available from grayed state, by clicking which, the
auto synchronization function of NE time can be cancelled.
13.2 Synchronize Current Alarm

It introduces how to synchronize alarms of the whole network or a specific
NE to NMS.
The operation of synchronizing alarms first needs to check the alarms of

NMS and NE, and if there are any inconsistencies, upload NE alarms to
NMS database to replace the existing content.
13.2.1 Synchronize Alarms of the Whole Network

Synchronize alarms of all the devices in the whole network to NMS.

User's Manual
Steps
Step 1 Select “Fault > Browse Current Alarms” in the main menu.
Step 2 Select “root” and click the right arrow.
Step 3 Click “Sync”, and the synchronization result can be observed in the
process dialog.
Step 4 Click “OK” and log out synchronize alarm.
13.2.2 Synchronize Alarm of a Specific NE

Synchronize alarm of a specific NE to NMS.
Steps
Step 1 Right click H9MO-LMESE device in the topology tree or the topology
view, select “Synchronization Current Alarm” item.
Step 2 A prompt box will pop up to indicate successful operation, and the
synchronization is finished.
13.2.3 Manage NE Configuration Data

It introduces how to manage NE Configuration Data, including NE
synchronization and NE data recovery.

241
User's Manual
NE synchronization
It introduces how to synchronize NE.
Prerequisites
When the data at NE side has been configured and NE is operating
normally, synchronously upload the data at NE side to NMS side to keep
the data at NMS side and the data at NE side consistent.
Steps
Step 1 Select “Config > Configuration Data Management” in the main menu.
Step 2 Select NE in the left object tree and click .
Step 3 Select one or several NEs in the configuration data management list.
Step 4 Click “Synchronize” or select “Synchronize” in the right-click menu.
Step 5 In the pop-up prompt window, click “Yes” to start to check, the progress
will be shown in the pop-up progress bar.

User's Manual
Step 6 After the synchronization is completed, “Synchronize” dialog will pop up.
Step 7 Select the data type in the left list and inconsistent items of NE side data
and NM side data will be listed in the right list. Select the item that you
want to set, and then click “Use NE Side Data” or “Use NM Side Data”.
Step 8 “Operation Result” dialog will pop up, and the setup is completed.
13.2.4 Upload and Download NE Configuration Data

Introduces how to upload or download NE data during configuration or
maintenance.

243
User's Manual
Prerequisites
EzView-side NE configuration data may be different from NE-side. If it
requires NE to operate according to EzView-side configuration data,
download the data to NE side. If the network is running normally and
NE-side data is correct, NE-side data can be uploaded to EzView.
Steps
Step 2 Select NE in the left the resource tree and click .
Step 3 Select one or several NEs in the configuration data management list, click
“Upload” or “Download”, or select “Upload” or “Download” in the
right-click menu.
Downloading NE configuration data may interrupt service, please be careful.
Step 4 Select “Yes” in the confirmation dialog.
Step 5 When the progress reaches 100% in the progress bar, the upload or
download is completed.
13.2.5 Copy NE Configuration Data

Prerequisites

User's Manual
Configure NE in bulk by the method of copying NE data. When configure
several NEs with the same configuration, this method is simple and
effective.
Steps
Step 2 Select NE that requires to be copied and the copied NE and click .
Step 3 Select NE that has been set in the configuration data management list and
select “Copy” in the right-click menu.
Step 4 Right click the NE that needs to be configured with data and select “Paste”.
Step 5 Click “Yes” in the confirmation dialog.
Step 6 When the progress reaches 100% in the progress bar, the copy is
completed.
The copied source NE and the destination NE should be of the same type.
The destination NE can be set, but there can be no link on the board.
13.2.6 Initialize NMS-side Data

Prerequisites
If it needs to reconfigure NE data, NMS-side NE configuration data can be
initialized first.

245
User's Manual
Steps
Step 2 Select NE in the left resource tree and click .
Step 3 Select one or several NEs in the configuration data management list, click
“Initializing NM Side Data” or select “Initializing NM Side Data” in the
right-click menu.
Step 4 Click “Yes” in the confirmation dialog.
Step 5 When the progress reaches 100% in the progress bar, the initialization is
completed. The device state of the initialized NE displays as
“Unconfigured”.
Delete links first when initialize NE.

User's Manual
14 Breakdown Maintenance
It introduces basic operations during breakdown maintenance.
14.1 Check Network Communication Status

During the operation of network, sometimes NMS cannot manage some
NE. through checking network communication status can learn the
communication state of NMS and NE.
Prerequisites
System maintainer or users with higher permissions are required to log in
Steps
Step 1 Select “System Management > DCN Management” in the main menu.
Step 2 Select “NE” tab and click “Refresh” to view communication state of all the
NEs.
Select “GNE” tab to view state of gateway network element.

247
User's Manual
14.2 Loopback
14.2.1 SDH Interface Loopback
Loop backing SDH interface is a common way of fault location to test and
maintain SDH board. Loop backing SDH interface can judge whether SDH
interface and the cable connecting SDH boards are normal; whether service
process module of SDH board and cross boards are normal.
Prerequisites
SDH interface loopback modes include inloop and outloop.
 Outloop means that SDH service received by NE is returned at SDH

interface, the loop backed signal will go out of the SDH network
element. It can be used to judge whether SDH interface and the cable
connecting SDH boards are normal.
 Inloop means SDH service sent by NE is returned to the cross board
at SDH interface; the loop backed signal will go into the SDH
network element. It can be used to judge whether service process
module of SDH board and cross boards are normal.
SDH interface loopback will interrupt service of the interface, the

loopback operation can only be used to fault location, and after
troubleshooting, loopback setting of the interface should be cleared.

User's Manual
Steps
Step 1 Select the corresponding board in NE manager and “Configuration > SDH
Interface” in the function tree.
Step 2 Select “By Function”, select “Optical (Electrical) Interface Loopback”.
Step 3 Select a SDH interface in the list and click “Optical (Electrical) Interface
Loopback” to select loopback mode.
Step 4 Click “Apply”.
14.2.2 PDH Interface Loopback

Loop backing PDH interface is a common way of fault location to test and
maintain PDH board. Loop backing PDH interface can judge whether PDH
interface and the cable connecting PDH boards are normal; whether service
process module of PDH board and cross boards are normal.
Prerequisites
PDH interface loopback modes include inloop and outloop.
 Outloop means that PDH service received by NE is returned at PDH

interface. It can be used to judge whether PDH interface and the cable
connecting PDH boards are normal.
 Inloop means PDH service sent by NE is returned to the cross board
at PDH interface. It can be used to judge whether service process
module of PDH board and cross boards are normal.

249
User's Manual
PDH interface loopback will interrupt service of the interface, the

loopback operation can only be used to fault location, and after
troubleshooting, loopback setting of the interface should be cleared.
Steps
Step 1 Select the corresponding board in NE manager and “Configuration > PDH
Interface” in the function tree.
Step 2 Select “By function”, select “Port Loopback”.
Step 3 Select a PDH interface in the list and click “Tributary Loopback” to select
loopback mode.
Step 4 Click “Apply”.
14.3 Execute Protection Switching

SNCP service can execute protection switching when the main service
channel fails, i.e. switch the service to the protection channel to ensure no
service interruption.
Prerequisites
 System maintainer or users with higher permissions are required to
 SNCP service has been configured.
Switching operations that can be executed on SNCP service include: forced
switch (forced switch to work/forced switch to protection) and manual
switch (manual switch to work/manual switch to protection).

User's Manual
Priority of forced switch is higher than SF, SD alarm of the protection

channel. That is to say, no matter what status of the working channel and
the protection channel, the switch will be executed.
Priority of manual switch is lower than SF, SD alarm of the protection

channel. Only when there are no cases like signal failure or signal
degradation in the protection channel can manual switch command take
effect.
Forced switch may interrupt service.
Steps
Step 1 Click NE in NE manager and select “Configuration > SNCP Service
Control” in the function tree.
Step 2 Select the service that needs to be switched, click “Function” button and
select to switch or lock in the pop-up menu.
Only under the condition that the service is not locked can switch be executed.

251
User's Manual
Step 3 Click “Query” to query switching status.
Step 4 (Optional) click “WTR Time” to set wait-to-restore time.
“WTR Time” refers to the time from normal working service is detected to
switching to working service, which can only be edited when “Revertive Mode” is
“Revertive”.
14.4 Configure Diagnosis Tasks

Diagnosis tasks include port diagnosis task and trail diagnosis task.
14.4.1 Configure Port Diagnosis Task

Create port diagnosis task, including the test of E1 tester, port loopback
(local loopback, remote loopback) and timeslot loopback.
Prerequisites
Steps
 Diagnosis Task Tested by E1 Tester
Step 1 Select “Diagnosis Task > Task Monitor > Port/Timeslot” in the main
menu.

User's Manual
0 EzView NMS 252
Step 2 Select NE in the upper-left NE tree and port in the lower-left board tree,
right click and select “New”, NE icon will be displayed in the upper-right
area.
Step 3 Right click at NE icon , select “Set Test Point” in the right-click menu,
then the corresponding port will be shown at the bottom “Test Point”.
Diagnosis port cannot be both test point and loopback point, i.e. the diagnosis port
can have one and only one loopback point and test point.
Step 4 Input the name of the diagnosis task in “Task name” box.
The name of diagnosis tasks should not be repeated.
Step 5 Select “Start Time” check box.
Step 6 Click in “Start Time” input box, “Set start time” dialog will pop up.

253
User's Manual
EzView NMS 13 Synchronization and Data Management
Step 7 After setting the time, click “OK”.
Start time must be later than the current time.
Step 8 Click in “Test Time” input box, “Set Test Time” dialog will pop up.
 The range of the test time is: more than 10 seconds and less than or equal to
7 days.
 Input hours, minutes or seconds, it will automatically convert to the

corresponding unit of time.
 Executing 5~7 can set the start time of diagnosis task, if it does not need to
do so, directly execute 8.

13 User's Manual
Synchronization and Data Management EzView NMS 254
Step 10 Click “New”, diagnosis tasks will be displayed in the bottom middle list.
“New” button reads “Save” now.
Step 11 Select a task and click “Start” to execute diagnosis task, “Start” button
reads “Suspend”. “Run Status” of tasks in the list reads “Running”, after a
period of time, data will be displayed periodically in the bottom-right list.
If the timeslot that newly creates a test task of E1 tester has created SDH service,
when the diagnosis task is running, the original service of the timeslot will be
interrupted and a test task of E1 tester will be allocated, after the test is ended, the
original service will be restored automatically.
Step 12 (Optional) select a task and click “Suspend” to suspend the running
diagnosis task.
Step 13 (Optional) select a task and click “Restart” or “Suspend” to restart or

suspend the diagnosis task.
The record in the bottom-right list will be updated every 10s, the test time shows
accumulative value, when the test time is equal to the test time set when creating
the new task, the task is completed. “Running status” in the middle list reads
“Completed”. “Start”, “Restart” and “Suspend” buttons become grayed.
Step 14 Tasks can be managed in “Diagnosis Task > Task Management” interface.
Please see detailed operation steps in 14.4.3 Task Management
Diagnosis Task of Port/Timeslot Loopback

Step 1 Select “Diagnosis Task > Task Monitor >Port/Timeslot” in the main menu.
Step 2 Select NE in the upper-left NE tree and port in the lower-left board tree,
right click and select “New”, NE icon will be displayed in the upper-right
area.
Step 3 Right click at NE icon , select “NoLoopback” or “Timeslot Loopback”

in the right-click menu, and then the corresponding port will be shown at
the bottom “Loopback Point”.

255
User's Manual
Diagnosis port cannot be both test point and loopback point, i.e. the diagnosis port
can have one and only one loopback point and test point.
Step 4 Input the name of the diagnosis task in “Task Name” box.
Step 6 Click in “Start Time” input box, “Set Start Time” dialog will pop up.
 The range of test duration is: more than 10 seconds and less than or equal to
7 days.

 Executing step 5~7 can set the start time of diagnosis task, if it does not need
to do so, directly execute 8.
reads “Suspend”. “Run Status” of tasks in the list reads “Running”.

13 User's Manual
 Local loopback, remote loopback: the port is set to loopback after the start of
the diagnosis task, after the test time of the diagnosis task is ended, the port
will automatically restore to non-loopback state.
 Timeslot loopback: if the timeslot that creates timeslot loopback has created
SDH service, when the diagnosis task is running, the original service of the
timeslot will be interrupted and a test task of E1 tester will be allocated, after
the test is ended, the original service will be restored automatically.
diagnosis task.

Step 14 Tasks can be managed in “Diagnosis task > Task Management” interface.
14.4.2 Configure SDH Trail Diagnosis Task

Create trail diagnosis task including the test of E1 tester and timeslot
loopback.
Prerequisites
 Trail service has been created; please see the detailed creation method
in 11.4 SDH Trail Creation.
Steps
Test Task of E1 Tester

Step 1 Select “Diagnosis Task > Task Monitor > Trail” in the main menu

257
User's Manual
Step 2 Select trail in the upper-left trail tree and execute “New” in the right-click
menu. NE icon will be displayed in the upper-right area.
Step 3 Right click at NE icon , select “Set Test Point” in the right-click menu,
then the corresponding trail will be shown at the bottom “Test Point”.
Trail diagnosis has at least one loopback point and test point.

13 User's Manual
 The range of test time is: more than 10 seconds and less than or equal to 7
days.

reads “Suspend”. “Run Status” of tasks in the list reads “Running”. After a
period of time, data will be displayed periodically in the bottom-right list.
When the diagnosis task of E1 tester is running, the original service of the timeslot
will be interrupted and a test task of E1 tester will be allocated, after the test is
ended, the original service will be restored automatically.
Executing 5~7 can set the start time of diagnosis task, if it does not need to do so,
directly execute 8.
diagnosis task.

The record in the bottom-right list will be updated every 10s, the test time shows
accumulative value, when the test time is equal to the test time set when creating
the new task, the task is completed. “Run Status” in the middle list reads
“Completed”. “Start”, “Restart” and “Suspend” buttons become grayed.
Step 14 Tasks can be managed in “Diagnosis task > Task Management” interface.
Diagnosis Task of Timeslot Loopback

Step 1 Select “Diagnosis task > Task Monitor > Trail” in the main menu

259
User's Manual
Step 2 Select trail in the upper-left trail tree and execute “New” in the right-click
menu. NE icon will be displayed in the upper-right area.
Step 3 Right click at NE icon , select “Timeslot Loopback” in the right-click

menu, and then the corresponding trail will be shown at the bottom
“loopback point”.
Trail diagnosis has at least one loopback point and test point.
 The range of test duration is: more than 10 seconds and less than or equal to
7 days.

reads “Suspend”. “Run Status” of tasks in the list reads “Running”.

13 User's Manual
 Timeslot loopback: when the diagnosis task is running, the original service
of the timeslot will be interrupted and a timeslot self-loop service will be
allocated, after the test is ended, the original service will be restored
automatically.
 Executing 5~7 can set the start time of diagnosis task, if it does not need to
do so, directly execute 8.
diagnosis task.

Step 14 Tasks can be managed in “Diagnosis Task > Task Management” interface.
14.4.3 Task Management

The created port diagnosis tasks and trail diagnosis tasks can be centrally
managed, and execute: start, pause, restart, stop, delete, view report and
details to tasks.
Prerequisites
 Port diagnosis tasks and trail diagnosis tasks have been created.
Steps
Step 1 Select “Diagnosis Task > Task Management” in the main menu.
Step 2 (Optional) select the tasks whose “Run Status” is “Ready” or “Suspend”,
right click and select “Start” in the right-click menu, the selected tasks will
be started.
Step 3 (Optional) select the tasks whose “Run Status” is “Running”, right click to
suspend the selected diagnosis tasks.

261
User's Manual
EzView NMS 0
Step 4 (Optional) select the tasks whose “Run Status” is “Running”, right click
and select “Stop” in the right-click menu to stop the selected diagnosis
tasks.
Step 5 (Optional) select the tasks whose “Run Status” is “Running” or “Suspend”,
right click and select “Restart” in the right-click menu to restart the
selected diagnosis tasks.
Step 6 (Optional) select the tasks whose “Run Status” is “Ready” or “Completed”,
right click and select “Delete” in the right-click menu to delete the selected
diagnosis tasks.
Step 7 Select a diagnosis task in the list, right click and select “Report” in the
right-click menu to view the diagnosis report of the diagnosis task.
Step 8 Select a diagnosis task in the list, right click and select “Detail” in the
right-click menu to open port diagnosis and trail diagnosis interfaces to
view the detailed information of diagnosis task.
14.4.4 Configure 64K Trail Diagnosis

Create 64K trail diagnosis task supporting the loopback diagnosis.
Prerequisites
 Trail service has been created; please see the detailed creation method
in 11.8 64K Trail Creation.
Steps
Loopback Diagnosis Task

Step 1 Select “Diagnosis Task>64K Trail Diagnosis” in the main menu.
Step 2 Select trail in the upper-left trail tree. NE icon will be displayed in the
upper-right area.

User's Manual
14 Breakdown Maintenance EzView NMS 262
Step 3 Right click at NE icon , select “Loopback” in the right-click menu, then
the corresponding trail will be shown at the bottom “Loopback Point”.
The 64K trail with multiple time-slots, when creating a diagnostic task, you need
to select a specific time slot to loop back.
 The range of test time is: more than 10 seconds and less than or equal to 7
days.

Step 8 Select a task and click “Start” to execute diagnosis task. “Run Status” of
tasks in the list reads “Running”.
Loopback: when the diagnosis task is running, the original service of the timeslot
will be interrupted and a self-loop task will be allocated, after the test is ended, the
original service will be restored automatically.

Step 10 Tasks can be managed in “Diagnosis Task > 64K Diagnosis Task
Management” interface.

263
User's Manual
EzView NMS 14 Breakdown Maintenance
14.4.5 64K Diagnosis Task Management

The created 64K trail diagnosis tasks can be centrally managed, and you
can execute: start, restart, stop, delete and detail commands.
Prerequisites
 64K trail diagnosis tasks have been created.
Steps
Step 1 Select “Diagnosis Task > 64K Diagnosis Task Management” in the main
menu.
Step 2 (Optional) select the tasks whose “Run Status” is “Ready” or “Suspend”,
right click and select “Start” in the right-click menu, the selected 64K
diagnosis task will be started.
and select “Stop” in the right-click menu to stop the selected 64K diagnosis
tasks.
and select “Restart” in the right-click menu to restart the selected 64K
diagnosis tasks.
Step 5 (Optional) select the tasks whose “Run Status” is “Ready” or “Completed”,
right click and select “Delete” in the right-click menu to delete the selected
64K diagnosis tasks.
Step 6 Select a diagnosis task in the list, right click and select “Detail” in the
right-click menu to open 64K trail diagnosis interfaces to view the detailed
information of diagnosis task.

User's Manual
15 Routine Maintenance
To ensure the normal running of the network, network management and

maintenance personnel should regularly use EzView to check and monitor
the network.
15.1 Schedule Backup

EzView can timely and automatically execute some tasks without manual
intervention. EzView provides scheduled tasks including database, NE
backup and can also set and modify them as needed.
15.1.1 Regular Database Backup

Steps
Step 1 Select “System Management > Schedule Task Management” in the main
menu.
Step 2 (Optional) create schedule task.
1. Click “New”, “Task Creation Wizard” dialog will pop up.

2. Select the type of the schedule task and input its name, click “Next”.

265
User's Manual
3. Set parameters of the schedule task according to the wizard, and click
“Next” in turn until the appearance of “Complete” button.
4. Click “Complete” to finish the creation.

− (Optional) select a schedule task and click “Modify” to modify
parameters of it.
− (Optional) click “Disable” or “Enable” to disable or enable the
task.
− (Optional) click “Run” to execute the schedule task.

User's Manual
“Run” means to execute the task no matter whether the scheduled time is reached;
“Enable” means to start the schedule task and when the scheduled time is reached,
the task will be executed.
15.1.2 NE Schedule Backup

Steps
Step 1 Select “System Management > Schedule Task Management” in the main
menu.
Step 2 (Optional) create schedule task.
1. Click “New”, “Task Creation Wizard” dialog will pop up.

2. Select the type of the schedule task and input its name, click “Next”.
3. Select the NE according to the wizard, and click “Next”.

267
User's Manual
4. Set parameters of the schedule task according to the wizard, and click
“Next” in turn until the appearance of “Complete” button.
5. Click “Complete” to finish the creation.

− (Optional) select a schedule task and click “Modify” to modify
parameters of it.

User's Manual
− (Optional) click “Disable” or “Enable” to disable or enable the

task.
− (Optional) click “Run” to execute the schedule task.
“Run” means to execute the task no matter whether the scheduled time is reached;
“Enable” means to start the schedule task and when the scheduled time is reached,
the task will be executed.
15.1.3 NTP Server Time Synchronization

Steps
Step 1 In the main menu, select “System Management>Schedule Task
Management”.
Step 2 (Optional) create a new schedule task.
1. Click “New”, you will see “Task Creation Wizard”.
2. Select task type and enter task name, and then click “Next”.
Step 3 According to the Task Creation Wizard, enter the NTP server address.

269
User's Manual
Step 4 Select the running period and click the Next.
Step 5 Set each parameter according to Task Creation Wizard, and click Next
until you see “Complete”.

User's Manual
Step 6 Click “”Complete” and finish the task.

− (Optional) Select a task and click “Modify”, and then you can
modify the parameters.
− (Optional) Click Disable or Run to disable or enable the task.
15.2 (Optional) “Run” to start a task.Check

Networkwide maintenance status
Through checking network wide maintenance status, network maintainers
can get the operation state of the network timely to avoid affecting services
by wrong setting.
15.2.1 Check loopback status

Check all the optical/electrical ports that have been set to loopback. Here
loopback can be cancelled to avoid affecting services by wrong loopback.

271
User's Manual
Prerequisites
15.2.2 Steps
Step 1 Click netowkwide maintenance status shortcut icon on the toolbar,
“Networkwide Maintenance Status” dialog will pop up.
Step 2 Check loopback status of channels.
Step 3 (Optional) select proper loopback state and click “Apply”, a prompt will
pop up to indicate success, click “Close”.
Setting loopback will interrupt service, please be careful.
15.2.3 Check laser status of optical ports

Check all the lasers that have been set to close in the network. Here laser
state can be modified to avoid affecting service by wrong setting.

User's Manual
Prerequisites
Steps
Step 1 Click networkwide maintenance status shortcut icon on the toolbar,

Step 2 Click “Laser Status” tab to view laser state of optical ports.
Step 3 (Optional) set on-state of lasers and click “Apply”, a prompt will pop up to
indicate success and click “Close”.
Closing laser will interrupt service, please be careful.

273
User's Manual
15.2.4 Check alarm suppression status of channels

Check all the alarm events that have been set to alarm suppression. Here
the default suppression status can be restored to avoid affecting alarm
monitoring of services by wrong setting.
Prerequisites
Steps

Step 2 Click “Alarm Suppression” tab to view alarm suppression state of

channels.
Step 3 (Optional) right click to select “Default”, alarm suppression state will
restore to the default state. Click “Apply”, a prompt will pop up to indicate
success and click “Close”.

User's Manual
15.2.5 Check alarm reversion status of channels

Check all the channels that have been set to alarm reversion in the entire
network. Here alarm reversion state can be modified to avoid affecting
service by wrong setting.
Prerequisites
Steps

Step 2 Click “Alarm Reversion” tab to view alarm reversion state of channels.
Step 3 (Optional) click “Reversion Status” to modify alarm reversion state. Click
“Apply”, a prompt will pop up to indicate success and click “Close”.
The alarm state of the port that has been set to alarm reversion is contrary to the
actual situation (i.e. even there is alarm, it still appears as normal state). Thus the
alarms that do not need to pay attention to will be filtered out. But when LOS
alarm of ports is set to alarm shielding, alarm reversion cannot be set.

275
User's Manual
15.3 Check NM Operation Log

All the NM users’ operations to EzView system and devices and their
operation results will be recorded in the logs. EzView provides log
browsing function and can filter the logs according to different conditions.
System operation log: logs record operations to NM.
Device operation log: logs record operations to NE.
Prerequisites
It requires NM administrators or NM users with higher permissions.
Steps
Step 1 Select “System Management > Browse Log” in the main menu.
Step 2 Set filter conditions of log browsing.
Step 3 Click “Query” to view logs.

User's Manual
16 Software Management
Use software management function of NMS to query software versions and

FPGA versions of NE, and the update and backup of NE software and
configuration files and so on can be realized by various ways.
16.1 Query Software Information

In software information page, software versions and FPGA versions of NE
can be viewed in bulk and their update time can also be viewed.
Steps
Step 1 Select “Tool > Software Management > Software Management” in the
main menu, select “Software Information” tab.
Step 2 Select NE that needs to be updated in the left NE list, and click the right
“Inquery Database” arrow.
Step 3 In the right list, software information of NE can be queried.

277
User's Manual
16.2 Software Update

16.2.1 Proprietary Protocol Update
The update adopts our company’s proprietary protocol, both gateway NE
and non-gateway NE support this kind of update.
Prerequisites
Steps
main menu，select “Proprietary Protocol Update” tab.
Step 2 Select NE that needs to be upgraded in the left NE list and click the right
Step 3 Select the file, file type, frag length and resend times that need to be
updated.

User's Manual
NE of different types and different file types correspond to different files to

be updated, if choose wrong, it will lead to a failed upgrade.
Step 4 Click “Upload” button.
Step 5 Wait for some time, and when “Download Progress” reaches 100%, click
“Install” button.
Step 6 Optional: during the update, click “Stop” to stop upgrading.
Step 7 Wait for some time, the update will be completed after the device finishes
processing.
16.2.2 FTP Update

The upgrade adopts FTP protocol, only gateway NE supports this kind of
upgrade.
Prerequisites

279
User's Manual
EzView NMS 0
Steps
main menu，select “FTP Update” tab.
Step 2 Select NE that needs to be upgraded in the left NE list and click the right
Step 3 Select the file and file type that need to be updated.

be updated, if choose wrong, it will lead to a failed upgrade.
Step 4 Click “Upload” button.
Step 5 Wait for some time, and when “Download Progress” reaches 100%, means
download successfully.
Step 6 Wait for some time, and when “Progress” reaches 100%, means install
successfully.

User's Manual
15 Routine Maintenance EzView NMS 280
16.2.3 TFTP Update

The update adopts TFTP protocol; part of NE supports this kind of update.
This needs the help of external TFTP tool, when use this function, TFTP
tool must be started, and the current directory and the server's IP address
are correctly set.
Prerequisites
Steps
Step 1 Start TFTP tool, set the current directory and the server’s IP address.
main menu, select “TFTP Update” tab.
Step 3 Select NE that needs to be updated in the left NE list and click the right
Step 4 Double click “Server Address” column and input TFTP server address in
the pop-up window, double click “File Name” column and input the name
of the uploaded file.

281
User's Manual
EzView NMS 15 Routine Maintenance

be upgraded, if choose wrong, it will lead to a failed upgrade.
Step 5 Click “Start” button.
Step 6 Wait for some time, and click “Install” button.
Step 7 Wait for some time, the update will be completed after the device finishes
processing.
16.3 Software Backup

Through software backup function, the configuration files and application
programs on the device can be backed up locally.
This needs the help of external TFTP tool, when use this function, TFTP
tool must be started, and the current directory and the server's IP address
are correctly set.

User's Manual
Steps
Step 1 Start TFTP tool, set the current directory and the server’s IP address.
Step 2 Select “Tool > Software Management > Software Backup” in the main
menu.
Step 3 Select NE that needs to be updated in the left NE list and click the right
Step 4 Select NE in the right list and click “Backup” button.

283
User's Manual
17 DHCP Zero Configurations
17.1 Brief Introduction of Zero Configurations

Zero Configurations of remote devices means that remote devices can
realize Plug and Manage, and do not need to configure management
VLAN, management IP and default route, as long as the NMS service path
of the upper-layer PTN network is unblocked, the correct configuration
needed by management can be generated automatically and the
communication with NMS server will be established. Zero Configurations
of remote devices realize zero configurations of NMS channel; the
configuration relating to specific customer services still needs manual
configuration. Zero Configuration function mainly adopts the method of
detecting NMS channel and DHCP address distribution to realize Plug and
Manage.
The full name of DHCP is Dynamic Host Configuration Protocol, whose

predecessor is BOOTP. DHCP works in the application layer of OSI, which
is a Bootstrap protocol which get configuration information from specific
DHCP servers. DHCP adopts client/server model, the device requesting
configuration information calls DHCP client, while the device providing
information calls DHCP server. DHCP client can get IP address from the
server dynamically and other configuration information like subnet mask,
FTP server address.
Presently, EzView has built-in DHCP server, when start DHCP service in
the NMS server, it can automatically find the remote NE, allocate ip
address and add this remote NE in the NMS.

User's Manual
17.2 DHCP Auto Discovery of Remote NE

17.2.1 Configure DHCP Server
Prerequisites
NMS administrators or NMS users with higher permissions are required.
Start “dhcpserver” in system monitoring client.
Steps
Step 1 Select “Tool >DHCP Config” in the main menu.
Step 2 Select “DHCP server” in the left function tree.
Step 3 Modify configuration information related to DHCP server in the right list.

285
User's Manual
 If it is auto discovery in the two layer network, DHCP server and

NMS must be in the same subnet with the two layer scope.
 The default auto report port is 162.
Step 4 Click “Apply” button.
17.2.2 Configure Domain

Prerequisites
NMS administrators or NMS users with higher permissions are required.
Start “dhcpserver” in system monitoring client.
If NE that needs to be added is in the third layer network, the domain does
not need to be configured, after receiving the DHCP configuration
information sent by the device, DHCP server will automatically create the
third layer domain and add the device to it.
Steps
Step 1 Select “Tool>DHCP Config” in the main menu.
Step 2 Select the default two layer scope under “DHCP Server” in the left
function tree.
Step 3 Modify related configuration of the two layer domain in the right list.

User's Manual
If it is auto discovery in the two layer network, DHCP server and NMS
must be in the same subnet with the two layer domain.
17.2.3 Start DHCP Function of the Device

Connect the remote device to the network and start DHCP function.
Different devices may have different start methods, please see details in
each device’s user’s manual.
17.2.4 Automatically Add NE

After the success of the negotiation between NM and the device, a remote
NE will be added automatically in the NM topology, whose IP address is
the one allocated by DHCP server, at the same time the information of this
NE will be displayed in “DHCP Domain Address Pool”.

287
User's Manual
17.3 Modify IP Address of Remote NE

Prerequisites
 NMS administrators or NM users with higher permissions are
required.
 Start “dhcpserver” in system monitoring client.
 The remote NE has been added automatically in NM.
Steps
Step 1 Select “Tool>DHCP Config” in the main menu.
Step 2 Select “DHCP Server” in the left function tree, and select the domian of
NE that needs to modify IP.
Step 3 Double click IP address list in the right “DHCP Domain Address Pool” to
modify IP address of NE.
Step 5 Restart DHCP function of the device.
Step 6 A remote NE with modified IP address will be re-added in NM.

User's Manual
18 North Interface
Configuration
North interface configuration has two configuration interfaces, they are

general parameters and alarm filter configuration. We can modify general
parameters in general parameters interface, so as to realize docking needs;
alarm filter function realizes reporting of the specified element specified
alarm type by configuring the alarm rules. Function entrance
“ToolsNorth Interface Configuration”.
18.1 General Parameters Configuration

Configure each related item in General Parameters interface. Each
parameter configuration will be valid after starting North Interface. After
modifying parameters, we must reboot North Interface to make the process
valid.
Start SSL function of system parameters, and then we can enable SSL.

289
User's Manual
18.2 Alarm Filter

Alarm filter function is the user customized function, which can report the
specified alarm type within the specified time in the specified NE
according to user’s needs. After starting alarm filter function, we can
configure the NE and alarm rules, so as to achieve selective alarm
reporting.
Prerequisites
In general parameter, "alarm filter switch" is the open state, or the relevant
setting will be invalid.
Steps
Step 1 Add alarm rules, select “Rule” in “Alarm Filter” interface, we will see
“Alarm Rule” dialog box.

User's Manual
Step 2 Select “Add” to add a new rule; select “Modify” to modify the existed
alarm rule; select “Delete” to delete the selected rule, select “Apply” to
finish the alarm rule setting. We must click “Apply” to make
“add/modify/delete” the alarm rules valid; or those settings will be invalid.
Step 3 Click “Add” to see Alarm Rule Config dialog box, in which we can set
alarm reporting time and type:

291
User's Manual
EzView NMS 0
After confirming adding alarm rules, we need to click “Apply” button in

“Alarm Rule” frame, or adding alarm rules will not succeed; modifying
and deleting also need to click “Apply” to be valid.
Step 4 The function tree on the left side of “Alarm Filter” shows the total NEs in
the whole network, we can select the NE which needs to be filtered and
then select to start alarm filter. We can configure different alarm

rules for NE, card or port. After selecting NE and rules, click “Apply” to
finish configuration.
 Start alarm filter function, select specified NE, the alarm reporting
state is “not report” by default;
 When selecting rules “report” and “not configure”, all alarms of the
selected NE will be reported;
 When selecting “report” and another alarm rule, the alarm made by
selected NE’s rules will be reported;
 When selecting “not report”, no matter configuring rules or not, no
alarm will be reported.

User's Manual
Software Management EzView NMS 292
Appendix Terms and Abbreviations
This chapter introduces terms and abbreviations involved in this user’s

manual.
 Terms
 Abbreviations
Terms
A
ACL (Access ACL is a series of sequential rules composed by

Control List) permit | deny statements. Based on these rules, the
device determines which data packets can be
received and which must be denied
APS (Automatic Automatic protection switched technology can

Protection conduct real-time monitoring towards transmission
Switched) path and automatic analysis of alarm information,
to timely detect the fault and hidden dangers. In
the event of a serious fault, it can automatically
switch the working channel to the spare channel,
so as to recover the communication in time and
complete the rapid response to failure and recovery
mechanism
Auto-Negotiation Two interconnected Ethernet interfaces

automatically select interface rate and duplex
mode according to negotiation result

293
User's Manual
EzView NMS Software Management
DHCP (Dynamic DHCP is a technology which can assign IP address

Host dynamically in the network. It can automatically
Configuration assign IP address for all clients in the network to
Protocol) reduce the workload of the administrator, realizing
the centralized management of IP address
EFM (Ethernet in EFM that complies with IEEE 802.3ah is a

the First Mile) link-level Ethernet OAM technology. It focuses on
link between two directly connected devices and
provides link connectivity check, link fault
monitoring, remote fault notification, and other
functions. EFM is mainly applied in Ethernet link
of user access network edge
ERPS (Ethernet ERPS is an ITU-T G.8032 based APS protocol

Ring Protection used in Ethernet ring. Normally, it can prevent
Switching) broadcast storm caused by data loop in Ethernet
ring. When the fault occurs to the link or
equipment in Ethernet ring, it can rapidly switch to
the backup link to ensure rapid service recovery
Full-duplex In a communication link, both parties can receive

and send data concurrently
Half-duplex In a communication link, only one party can send

data at a time. One party is receiving information,
while the other party is sending information

User's Manual
IEEE (Institute of IEEE is an international electronic technology and

Electrical and information science and engineer association,
Electronics which is also one of the world's largest
Engineers) professional technical organizations
LACP (Link LACP is a protocol used to implement the link

Aggregation dynamic aggregation. LACP uses LACPDU (Link
Control Protocol) Aggregation Control Protocol Data Unit) to
exchange information with remote side
Link Aggregation One logical aggregation group is formed through

aggregating multiple physical Ethernet interfaces
and the physical links in the same aggregation
group is seen as one logical link, so as to
implement link protection and load sharing
between devices, greatly enhance reliability of
service between devices, and enhance the
bandwidth without upgrading the hardware
Multi-mode Fiber Multi-mode can be transmitted in one fiber
NTP (Network NTP is a time synchronization protocol defined by

Time Protocol) RFC1305, which is used for the time
synchronization between distributed time server
and client. The purpose of using NTP is to conduct
fast clock synchronization to all devices which
have clocks in the network, so that the device can
provide different application based on the unified
time. At the same time, NTP can guarantee high
accuracy (error is about 10ms)

295
User's Manual
Protection Ground Protection ground wire is used to connect device

Wire with the protection ground. Usually, it is a
yellow-green coaxial wire
QoS (Quality of QoS is a network security mechanism used to

Service) solve the network delay and congestion problems.
It can ensure the timeliness and integrity of
important service during network overload or
congestion and the highly efficient running of the
entire network
QinQ (Stacked QinQ is extended from 802.1Q, defined by IEEE

VLAN or Double 802.1ad recommendation. In carrier backbone
VLAN) network (public network), the packets take double
VLAN Tag passing through trunk network (public
network): public network VLAN Tag and private
network VLAN Tag. In public network, the private
VLAN Tag is transmitted as data in packets. QinQ
supports basic QinQ and flexible QinQ
RSTP (Rapid RSTP is developed to make up slow convergence

Spanning Tree for the STP (Spanning Tree Protocol). Based on
Protocol) STP, RSTP is improved a lot, which implements
fast convergence for network topology
Single Mode Fiber In this fiber, single-mode optical signals are

transmitted
SNTP (Simple SNTP is mainly used in the device time of

Network Time synchronization network.
Protocol)

User's Manual
STP (Spanning STP can remove loopback in a LAN and backup

Tree Protocol) data links. Thus it can logically block loopback
and avoid the generation of broadcast storm. When
the unblocked link fails, the blocked link will be
activated and serve as a backup line
VLAN (Virtual VLAN is a protocol proposed to solve broadcast

Local Area and security issues for Ethernet. It divides devices
Network) in a LAN into different segment logically rather
than physically, thus implementing virtual work
groups which are based on Layer 2 isolation and
do not affect each other
Abbreviations
A
AC Alternating Current
ACL Access Control List
APS Automatic Protection Switching
ARP Address Resolution Protocol
BPDU Bridge Protocol Data Unit
BTS Base Transceiver Station
CE Customer Edge

297
User's Manual
CIR Committed Information Rate
CoS Class of Service
CRC Cyclic Redundancy Check
DC Direct Current
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Service
EFM Ethernet in the First Mile
ERPS Ethernet Ring Protection Switching
FE Fast Ethernet
FTP File Transfer Protocol
GE Gigabit Ethernet
IEEE Institute of Electrical and Electronics Engineers
IP Internet Protocol

User's Manual
EzView NMS 298
ITU-T International Telecommunications Union -

Telecommunication Standardization Sector
LACP Link Aggregation Control Protocol
LACPDU Link Aggregation Control Protocol Data Unit
LAN Local Area Network
LLDP Link Layer Discovery Protocol
LLDPDU Link Layer Discovery Protocol Data Unit
MAC Medium Access Control
MTU Maximum Transmission Unit
NTP Network Time Protocol
OAM Operation，Administration and Management
PDU Protocol Data Unit
PE Provider Edge

299
User's Manual
EzView NMS DHCP Zero Configurations
Ping Packet Internet Grope
QoS Quality of Service
RMON Remote Network Monitoring
RSTP Rapid Spanning Tree Protocol
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SP Strict-Priority
SSHv2 Secure Shell v2
STP Spanning Tree Protocol
TPID Tag Protocol Identifier
UNI User Network Interface

User's Manual
DHCP Zero Configurations EzView NMS 300
VLAN Virtual Local Area Network
WAN Wide Area Network
WRR Weight Round Robin

EzView NMS User's Manual V3.10 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EzView NMS User's Manual V3.10 PDF

Uploaded by

Copyright:

Available Formats

1

NMS User’s Manual

Beijing Huahuan Electronics Co. Ltd

Product Name: EzView NMS

Manual Version: 3.10

Release Date: Nov. 2018

BEIJING HUAHUAN ELECTRONICS Co., LTD.

Address: No.26, Shangdi 6th Street, Haidian District, Beijing, 100085

Tel: +86-400-810-8580, +86-10-52046188

Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. i

3.2.1 Topology View........................................................................................................ 13

ii Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

5.2 Add NMS User Group......................................................................................................53

Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. iii

7.3.9 NAT Mapping NE................................................................................................... 81

9 Fault Management.......................................................................................... 115

iv Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

9.1.1Alarm Reporting Process....................................................................................... 115

10 Report Management..................................................................................... 140

Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. v

10.5 Slot Count Report.........................................................................................................142

11 SDH Trail Management...............................................................................152

vi Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

11.9.1 Browse 64K Trail................................................................................................171

12 Ethernet Trail Management........................................................................ 178

Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. vii

12.8 Deploy VPLS Service.................................................................................................. 216

13 Synchronization and Data Management..................................................237

15 Routine Maintenance................................................................................... 264

viii Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

15.1.1 Regular Database Backup................................................................................... 264

16 Software Management................................................................................. 276

17 DHCP Zero Configurations........................................................................ 283

18 North Interface Configuration................................................................... 288

Appendix Terms and Abbreviations..............................................................292

Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. ix

Figure 2-1 Client on-line installation Web login page............................................................ 9

Figure 2-2 Client on-line installation guide.......................................................................... 10

Figure 2-3 The client login page........................................................................................... 11

Figure 12-1 MPLS Tunnel in MPLS network..................................................................... 183

x Beijing Huahuan Electronics Co., Ltd. Version3.10 (Nov.2018)

Table 3-1 File menu...............................................................................................................17

Table 3-2 View menu............................................................................................................. 18

Table 3-3 Config menu.......................................................................................................... 20

Table 3-4 System Management menu....................................................................................21

Table 3-5 Fault menu............................................................................................................ 23

Table 3-6 Performance menu................................................................................................ 24

Table 3-7 Trail menu............................................................................................................. 26

Table 3-8 Diagnosis...............................................................................................................30

Table 3-9 Report menu.......................................................................................................... 31

Table 3-10 Tool menu............................................................................................................ 33

Table 3-11 Help menu............................................................................................................34

Table 3-12 Main toolbar........................................................................................................ 35

Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. xi

EzView Network Element Management Software is specially designed by

1.1 EzView Network Element Management

2. Fault Management：Collect and manage alarm information reported by

Version3.10 (Nov.2018) Beijing Huahuan Electronics Co.,Ltd. 1

3. Performance Management ： Provide SDH performance management

4. Security Management：Support multi administration accounts，provide

5. Log Management ： Completed log management includes system

6. Trail management: Allow to create, search, and manage the end-to-end

7. Report management: Supports multiple reports, which is convenient