E-Fim OTNM2000 Element Management System Release Notes For Version V2.0R5 (Build04.20.05.50)

e-Fim OTNM2000
Element Management System
Release Notes for Version

V2.0R5 (Build04.20.05.50)
Version: A
Code: MN000002197
FiberHome Telecommunication Technologies Co., Ltd.
December 2014
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.
Fiberhome Telecommunication Technologies Co., Ltd.
Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +6 03 7960 0860/0884 (for Malaysia)
+91 98 9985 5448 (for South Asia)
+593 4 501 4529 (for South America)
Fax: +86 27 8717 8521
Website: http://www.fiberhomegroup.com
Legal Notice
are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.
All rights reserved
No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface
Terminology Conventions
Terminology Convention
FiberHome e-Fim OTNM2000 Element Management

OTNM2000
System
FiberHome e-Fim OTNM2100 Network Management

OTNM2100
System
I
Symbol Conventions
Symbol Convention Description
Important features or operation

Note
guide.
Possible injury to persons or

Caution systems, or cause traffic interruption
or loss.
Warning May cause severe bodily injuries.
Jump Jumps to another step.
Cascading menu Connects multi-level menu options.
Bidirectional service The service signal is bidirectional.
Unidirectional service The service signal is unidirectional.
II
Contents
Preface...................................................................................................................I
Terminology Conventions.................................................................................I
Symbol Conventions.......................................................................................II
1 New Features of This Version ......................................................................1-1
2 Overview of This Version .............................................................................2-1
2.1 Compatibility with Earlier Versions..................................................2-2
2.2 Northbound Interface Version.........................................................2-2
2.3 Device Version ..............................................................................2-3
3 Changes to Basic Functions.........................................................................3-1
3.1 Integrated Configuration Management ...........................................3-2
3.1.1 Modifying Project Attributes..............................................3-2

3.1.2 Managing Manager Services............................................3-3
3.1.3 Managing Network Blocks................................................3-8
3.1.4 Managing NEs ...............................................................3-12
3.1.5 Managing Cards ............................................................3-16
3.1.6 Managing Topology Fiber Connections...........................3-20
3.1.7 Configuring NE IP Remotely based on SN......................3-29
3.2 OTNM2000 GUI Optimization.......................................................3-36
3.3 Optimized Alarm Indicator Display................................................3-42
3.4 Layer-based Topology..................................................................3-44
3.4.1 Setting Topology Layers.................................................3-45

3.4.2 Modifying Topology Layers.............................................3-47
3.4.3 Viewing the Layer-based Topology.................................3-49
3.5 Authorization and Domain Division...............................................3-52
3.5.1 Basic Concepts..............................................................3-52

3.5.2 Scenarios for Authority and Domain Division ..................3-55
3.5.3 Authorization Planning ...................................................3-56
3.5.4 Managing Object Groups ...............................................3-58
3.5.5 Managing Operation Groups ..........................................3-60
3.5.6 Managing User Groups ..................................................3-64
3.5.7 Managing Users ............................................................3-67
3.5.8 Authorization and Domain Division Example ..................3-76
3.6 Network Management Tool...........................................................3-79
3.7 Configuration Management ..........................................................3-81
3.7.1 Batch Control Command................................................3-81

3.7.2 Automatic Updating Central Office Name with the NE Name
Change .........................................................................3-84
3.7.3 Added the Area Attribute for NE .....................................3-85
3.7.4 Added the NE Search Function in the NE IP Remote Config
Window .........................................................................3-86
3.8 Security Management ..................................................................3-87
3.8.1 Added the Scheduled Configuration Backup...................3-87
3.9 Alarm Management .....................................................................3-90
3.9.1 Optimized the Alarm Statistical Template........................3-90

3.9.2 Optimized the Alarm Filter ..............................................3-94
3.9.3 Added the Physical Address Column in the Alarm List
Tab ................................................................................3-95
3.9.4 Supporting Export of Alarm History Reports....................3-96
3.9.5 Supporting Backup of Current Alarm Remarks................3-97
3.10 Report Management ....................................................................3-97
3.10.1 Service Routing Information Statistics ............................3-97

3.10.2 Long-term Traffic Monitor ...............................................3-98
3.10.3 Device Version Statistics................................................3-99
4 Service Configuration and Management.......................................................4-1
4.1 Service Configuration and Management.........................................4-2
4.2 Service Query................................................................................4-2
4.2.1 Service Filter ...................................................................4-3

4.2.2 Association Location........................................................4-5
4.2.3 Signal Flow Direction Chart ..............................................4-6
4.3 Added the Comparison of Card Service Configuration ....................4-7
4.4 Optimized the Query Mode of Fiber Information in the Multi-service

Window .........................................................................................4-8
4.5 Cutover Management ....................................................................4-9

4.5.1 Function Description ........................................................4-9
4.5.2 Service Scenarios..........................................................4-11
4.6 Others .........................................................................................4-25
4.6.1 PTN / IPRAN Service Configuration ...............................4-25

4.6.2 OTN Service Configuration ............................................4-26
5 Precautions for Upgrade to a New Version ...................................................5-1

Figures
Figure 4-1 Service Migration Cutover Scenario Example ...............................4-10

Figure 4-2 Service Adjustment Cutover Scenario Example............................4-10
Figure 4-3 NNI Side Fiber Connection Adjustment (Working Path).................4-12
Figure 4-4 NNI Side Fiber ConnectionAdjustment (Protection Path) ...........4-13
Figure 4-5 Service Card Interface Adjustment (Same Card but Different
Slots)...........................................................................................4-14
Figure 4-6 Capacity Expansion .....................................................................4-15
Figure 4-7 Capacity Reduction 1...................................................................4-16
Figure 4-8 Deleting the Starting Node of the Branch Chain ............................4-17
Figure 4-9 Same-model Device Replacement (Station Changing) .................4-18
Figure 4-10 Replacing CiTRANS 660 with CiTRANS680V2 (CiTRANS 660 is
connected to CiTRANS680V2 through double fibers) ................4-19
Figure 4-11 Device Upgrade...........................................................................4-20
Figure 4-12 Replacing Immediate Nodes of MSPW.........................................4-21
Figure 4-13 PW Redundancy Protection .........................................................4-22
Figure 4-14 Changing Single-Connection to Double-Connection .....................4-23
Figure 4-15 Upgrading the Ring to Improve the Ring Rate ...............................4-24
Figure 4-16 Changing the Large Ring into Small Ring .....................................4-25
Tables
Table 2-1 List of Matching Cards ...................................................................2-3

Table 3-1 NE IP Address Settings................................................................3-33
Table 3-2 Alarm Color Description ...............................................................3-44
Table 3-3 Description of the Authority and Domain Division Scenario ...........3-56
Table 3-4 Authorization Planning Flow.........................................................3-57
Table 3-5 User Settings ...............................................................................3-70
Table 3-6 Creating User Groups ..................................................................3-77
Table 3-7 Creating Users.............................................................................3-78
Table 3-8 Description of DCG Backup Task Settings ....................................3-88
1 New Features of This Version
The release notes for version V2.0R5 (Build04.20.05.50) describe the updated
functions, including the changes to hardware features and software functions of the
OTNM2000 as well as the new features.
The main features of this version include:
u Implements the integrated configuration, completing the configuration in

seconds.
u Enlarges the OTNM2000 management capacity to 20 thousand physical NEs

and adopts separation of large amount of data. The performance management
capacity reaches 1.5 billion entries every day.
u Re-deploys the mode to store service configuration and the mode to download
service, improving the service storing efficiency by 10 times and service
download efficiency by 3 times on the premise that the service memory
resources are reduced.
u Further improves the management function of the OTNM2000, completing the

information reports of resource statistics. This makes the OTNM2000 more
user-friendly and easier to use during the maintenance.
The new features of this version are described as follows:
Configuration Management
The configuration management function manages the configuration information of

the NEs. This function is updated in the following aspects:
u Implements the integrated configuration function, which supports multiple users

configuring basic information of devices on the OTNM2000 main GUI, including
the manager services, projects, network blocks, NEs and cards.
u Synchronizes the configuration data to other clients in real-time with no

influence caused to users, replacing the offline configuration mode in Devcfg.
u Replaces the original mode of saving all data via Devcfg with the new mode of
saving incremental NE data into the database via the OTNM2000 main GUI, It
completes data saving in seconds.
Version: A 1-1
e-Fim OTNM2000 Element Management System Release Notes for Version V2.0R5 (Build04.20.05.50)
u Reserves the Devcfg, which is used only for data backup and restoring.
u Implements scheduled backup of device configuration data, enhancing data

security.
GUI Updates
The GUI has the following updates:
u Re-designs and beautifies the GUI layout and pattern as well as the icons.
u Sorts and adjusts the main menus to make the OTNM2000 GUI more user-
friendly and easier to user.
4 Re-sorts the menus by task type and their importance, and merges some
menus according to their attributes.
4 Unifies and standardizes the menu names and adds the Business
Configuration, Business Management and Statistics menus, making
the functions of menus more intuitive and clear.
4 Provides access keys for all the sub menus, improving access efficiency.
u Renames the tabs in unified and standard style, reflecting the contents in the
corresponding tabs directly.
Business Management
The business management function manages the service configuration and service
adjustment. This function is updated in the following aspects:
u Optimizes the data saving mode, the service memory usage reduced by 30%
and service data storing efficiency improved by 10 times or above.
u Implements multi-thread concurrent download of services, download efficiency

of PTN / IPRAN services improved by 3 times or above.
u Re-adjusts the service GUI to support configuring services on the OTNM2000

GUI, without the need to load circuit data. The original business management
(Subnet Cross-connect) module is no longer the menu to access service
configuration and is used only for querying, filtering and maintaining services.
u Re-defines the business management module and adds it with the service filter,
association and location, signal flow direction chart functions, convenient for
you to query and locate service data and improving maintenance efficiency.
1-2 Version: A
4 Service Filter: Enables you to set filter condition to view the matching
services.
4 Association Location: Enables you to view the associated path and

attribute information of the selected service and supports quick redirection
to the data view of the associated path.
4 Signal Flow Direction Chart: Displays the route graph of the multi-service
path, providing you with the service signal flow direction.
u Provides the service data query function, querying and gathering statistics of
device NE port, circuits between NEs and link results. This function helps you
understand the service data and distribution in the network, providing reference
for subsequent service adjustment or capacity expansion.
u Optimizes the circuit cutover management function, perfecting the online

service repairing scenarios and improving service cutover efficiency. For the
common project cutover scenario and detailed cutover method, see "e-Fim
OTNM2000 Circuit Cutover Operation Guide".
Topology Management
The topology management displays the managed NEs and the connection status
among them in a topological chart. You can get the networking and monitoring
status information in real time from the topological view. The topology management
function is updated in the following aspects:
u Re-adjusts the NE icons and supports up to 20 thousand nodes to be managed

in the topology.
u Implements quick layer-based topology via multiple ways and supports filtering
topological objects by object type, making NE search more faster and more
convenient.
u Supports graphical display of topological connections among NEs and NE

groups, displaying the paths among nodes and the information of NEs based
on layers. This helps locate and manage NEs, improving management
efficiency.
Version: A 1-3
Security Management
The security management conducts the control over the privileges of EMS users,
EMS user groups and NE users by authenticating, authorizing and encrypting to
ensure the security of the user accounts and the system running. The security
management function is updated in the following aspects:
u Optimizes the privilege management with detailed and classified operation

privileges for operation groups. This provides convenience for privilege
planning and management.
u Enhances control and monitoring on users' access, further improving the

security of the EMS system.
4 Supports restraints on login IP address, that is, allowing certain users to

login only from clients in the specified network segment.
4 Supports monitoring the activity information of a certain user.
u Adds password complexity check and lockup on failed password attempts,

offering more functions for you.
u Adds Web-based network management tool, which manages the network

management service processes, monitors system resources of network
management server and imports / exports configuration. This tool facilitates the
monitoring of health status of the EMS and analyzing of the EMS error
information.
Performance Management
The performance management gathers statistics of performance data of each NE

and directly displays the statistics, convenient for you to monitor the performance of
NEs. The performance management function is updated in the following aspects:
u Supports managing and processing large amount of data, improving the

stability of the performance service running.
u Optimizes the performance service. It separates the performance-related

functions, such as performance filter and current performance query, from
DtServer, and then forms a performance subsystem together with the global
performance service, performance history service and performance collection
service. This implements the separation of large amount of data with a large
daily performance management capacity of 1.5 billion.
1-4 Version: A
u Optimizes the traffic management to provide long-term traffic monitoring report

and export function, providing data support for service maintenance and device
maintenance.
Failure Management
The failure management manages the failure alarms and event alarms generated by
NEs, enabling you to locate and process network anomalies quickly and take
measures to restore the network to normal running timely. The failure management
function is updated in the following aspects:
u Provides alarm correlation analysis, alarm forwarding (to NE, port or service),
alarm filter, alarm suppression, maintenance expertise base, improving the
correctness and efficiency of alarm processing.
u Provides templates.
4 Sorts the commonly-concerned alarms according to the alarm level and

alarm filer rules, convenient for you to classify alarms flexibly and focus the
commonly-concerned alarms quickly.
4 Sets the commonly-used statistical conditions as an alarm statistical

template, providing convenience for querying and monitoring later.
u Optimizes the alarm indicator display: Changes the double-alarm indicator into
single-alarm indicator, and supports customized prompt icon for focused alarms,
displaying alarm indicators in a more concise and intuitive manner.
u Adds an independent column displaying the physical address (which can be

hidden or shown as needed), facilitating the failure isolation.
u Supports import and export of alarm remarks (relevant reference information for
alarm processing) through the Dtbackup tool. This can avoid loss of alarm
remark information caused by version upgrading and helping process alarms
quickly, improving the failure processing efficiency.
u Supports export of alarm history report at one time, providing efficient support
for exporting quarterly or yearly failure data analytical reports.
Version: A 1-5
Report Management
The report management provides reports specific to alarms, logs and resources.
You can view or print the reports or save them as an XLS, TXT, HTML or CSV file.
The report management function is updated in the following aspects:
u Gathers statistics of physical resource information in the network, including the

number of NEs, the number of devices of each type, the number of cards, slot
usage, NE fiber-connection information, management interface IP address,
logical interface IP address and device version. It supports sorting, filtering and
exporting query results. This helps analyze the resource usage and provides
reference data for network device construction.
u Gathers statistics of device maintenance information, including alarm filter

information, alarm history, NE CPU and memory usage, and supports sorting,
filtering and exporting querying results. This helps you comprehensively and
systematically understand the running status of the network devices and
provides reference data for device maintenance.
1-6 Version: A
2 Overview of This Version
The following introduces the related information of the OTNM2000 V2.0R5

(Build04.20.05.50) version.
Compatibility with Earlier Versions
Northbound Interface Version
Device Version
Version: A 2-1
2.1 Compatibility with Earlier Versions
The OTNM2000 V2.0R5 (Build04.20.05.50) version is compatible with the following

earlier versions:
Caution:
This version adjusts and optimizes the processing mode of underlying

data. The configuration data conversion is required upon EMS version
upgrading. In this case, contact the FiberHome engineers.
u V2.0T5(Build04.20.05.32SP7)
u V2.0T5(Build04.20.05.32SP7BD1)
u V2.0R5(Build04.20.05.32)BD series
u V2.0R5(Build04.20.05.36)
u V2.0R5(Build04.20.05.36SP2) and its project global and incremental patches
u V2.0R5(Build04.20.05.36SP2BD1) and its project global and incremental

patches

patches

patches

patches
2.2 Northbound Interface Version
The version of northbound interface applicable to the OTNM2000 V2.0R5

(Build04.20.05.50) version is V1.0R1(Build01.06.03.26)
2-2 Version: A
2 Overview of This Version
2.3 Device Version
The corresponding device version for the OTNM2000 V2.0R5 (Build04.20.05.50)

version is R800 V2R4. The changes to the matching card are shown in Table 2-1.
Table 2-1 List of Matching Cards
Card Name Hardware Version Software Version

ESJ3 WKE2.201.514R1A RP0300
QSO1 WKE2.200.892R2B RP0300
GSO1 WKE2.201.189R1A RP0300
GSO2 WKE2.200.848R1A RP0300
GSO3 WKE2.201.060R1C RP0300
GSO4 - RP0300
GSR1 WKE2.200.843R1A RP0300
GSR2 WKE2.201.433R1A RP0300
GSR3 WKE2.201.434R1A RP0300
XSR1 WKE2.200.844R1A RP0300
XSR2 WKE2.200.829R1A RP0300
XGO1 WKE2.200.677R1A RP0300
XGR1 WKE2.200.766R1A RP0300
XSO1 WKE2.201.019R1A RP0300
XSO3 WKE2.200.828R1A RP0300
XSO5 WKE2.201.137R1B RP0300
SCUR1 WKE2.200.741R1B1 RP0300
ESR1 WKE2.200.846R1B RP0300
Version: A 2-3
3 Changes to Basic Functions
The following introduces the changes to the basic functions of the OTNM2000.
Integrated Configuration Management
OTNM2000 GUI Optimization
Optimized Alarm Indicator Display
Layer-based Topology
Authorization and Domain Division
Network Management Tool
Configuration Management
Security Management
Alarm Management
Report Management
Version: A 3-1
3.1 Integrated Configuration Management
The following introduces the concept the integrated configuration and how to
manage the projects, network blocks, NEs, cards and manager services through the
integrated configuration in the OTNM2000.
Integrated Configuration
The integrated configuration implements the integration of the network data

configuration and management. It changes the configuration mode in which both the
Devcfg and the OTNM2000 are involved. The integrated configuration has the
following features:
u Supports direct management (adding, editing and deleting) of projects, network

blocks, NEs and cards in the OTNM2000, without the need to configure and
manage them in the Devcfg first. This saves the time spent in repeated
configuration.
u Allows multiple users to perform operations simultaneously in the OTNM2000

and synchronizes the data changes to other clients in real time, with no
influence caused to users. This improves the inconvenience that when multiple
users edit data simultaneously, the data changes saved at last will overwrite the
data changes of other users.
u After the integrated configuration function is provided, the Devcfg functions as a

storage, mainly backing up and restoring data, with no data configuration any
longer.
3.1.1 Modifying Project Attributes
The following introduces how to modify the attributes of the project in the
OTNM2000. After the project attributes are modified, the changes will be read from
the database in Devcfg, making sure the project information in Devcfg is consistent
with that in the OTNM2000.
Prerequisite
You have the privileges of Operator Group or higher privileges.
3-2 Version: A
Procedure
1. In the Logical Tree of the OTNM2000, right-click a project and select Project
Attribute from the shortcut menu to open the Project Attribute dialog box.
2. Modify the project name, structure configuration height and width parameters.
Click OK to complete modifying the project attributes.
3.1.2 Managing Manager Services
The NEs of different types communicate with the OTNM2000 using different
communication protocols. Before building network topologies of different types, it is
needed to understand the communication protocols used by NEs of different types
to communicate with the OTNM2000 so as to ensure normal communication
between the created NEs and the OTNM2000.
To ensure the communication between the EMS and the NE, it is necessary to
configure the manager services for managing NEs at the EMS side. The following
introduces how to add, edit and delete manager services in the OTNM2000.
3.1.2.1 Adding a Manager Service
To ensure the communication between the EMS and the NE, it is necessary to
configure the manger services for managing NEs at the EMS side. The following
introduces how to add manager services in the OTNM2000.
Version: A 3-3
Prerequisite
Procedure
1. Select ConfigurationManager Service Config from the main menu to open

the Manager Service Config tab.
2. Click Add to open the Add Manager Service dialog box and set the attributes.
The items with * are required, and others are optional.
Note:
u The IP address of a manager service must be unique in a project.

One manager service can manage multiple network blocks.
u Under the same communication protocol type, the listening IP

address and port of the communication network card must be unique
in a project.
3-4 Version: A
3. Click OK.
3.1.2.2 Modifying a Manager Service
When the existing manager services do not meet the requirements for NE
management, you can adjust the manager services for managing network blocks or
NEs by modifying or switching them.
The following introduces how to modify or switch manager services for managing
network blocks in the OTNM2000.
Prerequisite
Procedure (Modifying the Manager Service)

2. Modify the attributes of the manager service.
1) Select the desired manager service and click Modify.
Version: A 3-5
2) Modify the attributes in the displayed dialog box. The items with * are
required, and others are optional.
Note:
u The IP address of a manager service must be unique in a project.

One manager service can manage multiple network blocks.
u Under the same communication protocol type, the listening IP

address and port of the communication network card must be unique
in a project.
3-6 Version: A
3) Click OK.
Procedure (Switching Manager Services of Network Blocks)
1. Select the manager service.
2. Select the network block to be switched in the Part of configured this

manager service frame at the bottom (press Ctrl to select multiple ones
randomly; press Shift to select multiple ones successively).
3. Click Switch Network Block Manager Program.
4. Select the new manager service in the displayed Please Select Manager
Service dialog box.
5. Click OK.
6. Click OK in the displayed alert box.
3.1.2.3 Delete Manager Services
When a manager service is no longer used by NEs or network blocks, it can be

deleted to avoid redundant manager services and facilitate the maintenance. The
following introduces how to delete manager services in the OTNM2000.
Version: A 3-7
Caution:
The manager services in use cannot be deleted. To delete it, modify the
manager service managing the network block to another one. For
modifying the manager service, see the Procedure (Switching Manager
Services of Network Blocks) section in Modifying a Manager Service.
Prerequisite
Procedure

2. Select the desired manager service and click Delete.
3. Click OK in the displayed alert box.
4. Click OK in the displayed Integrated Config Operation Information dialog

box.
3.1.3 Managing Network Blocks
The following introduces how to add, edit and delete network blocks in the
OTNM2000.
3-8 Version: A
3.1.3.1 Adding a Network Block
The following introduces how to add a network block in the OTNM2000.
Prerequisite
The manager service is created.
Procedure
1. In the Logical Tree of the OTNM2000, right-click a project and select Add
Network Block from the shortcut menu to open the Add Network Block dialog
box.
2. Specify the network block number, name and manager service.
Note:
u The network block number must be unique, and a network block can
be managed only by one manager service.
u The network block name must be unique.
u The items with * are required, and others are optional.
3. Add the Ma NE for the network block.
Version: A 3-9
1) In the Add Network Block dialog box, click behind the Ma NE No. to
open the Add Ma NE dialog box.
2) Set the attributes of the Ma NE. The items with * are required, and others
are optional.
3) Click OK to complete adding the Ma NE.
4. Click OK to complete adding the network block.
3.1.3.2 Modifying Network Block Attributes
The following introduces how to modify the attributes of network blocks in the
OTNM2000.
Prerequisite
Procedure
1. In the Logical Tree of the OTNM2000, right-click a network block and select
Modify Network Block from the shortcut menu to open the Modify Network
Block dialog box.
3-10 Version: A
2. Modify the network block No., name, Ma NE No., manager service according to
the actual situation.
Note:
An Ma NE must exists under each network block.
3. Click OK to complete modifying the network block attributes.
3.1.3.3 Deleting a Network Block
The following introduces how to delete a network block in the OTNM2000.
Caution:
u When a network block is deleted, all the NEs under the network
block will be deleted simultaneously.
u Deleting a network block break the services carried by the NEs

under the network block.
Prerequisite
Version: A 3-11
Procedure
1. Right-click the network block in the Logical Tree pane and select Delete to
open the Delete Part dialog box.
2. Confirm the network block to be deleted and click Delete.
Caution:
When the Delete Part dialog box appears as shown in the following
figure, go to the Business Management menu to check and adjust the
service carried by the network block to another network block according
to the prompt in red. Otherwise, deleting the network block directly will
greatly influence the service.
3.1.4 Managing NEs
The following introduces how to add, edit and delete network NEs in the OTNM2000.
3.1.4.1 Adding an NE
The following introduces how to add NEs in the OTNM2000.
Prerequisite
u You have the privileges of Operator Group or higher privileges.
u The corresponding NE is created.
3-12 Version: A
Procedure
1. In the Logical Tree of the OTNM2000, right-click a project and select Add NE
from the shortcut menu to open the Add NE dialog box.
2. Specify the NE attributes and configuration. The items with * are required, and
others are optional.
Note:
u The names of NEs under a same network block cannot be repeated.
u The switch No. can be a decimal or hexadecimal number

(automatically converted), which must be globally unique.
u The IP address must be unique.
3. Click OK to complete adding the NE.
Note:
After an NE is added, the system automatically adds the main switch card
(in the default slot) for the NE.
3.1.4.2 Modifying the NE Attributes
The following introduces how to modify the attributes of the NE in the OTNM2000.
Version: A 3-13
Prerequisite
Procedure
1. Right-click the NE in the Logical Tree pane and select Property to open the
Property dialog box.
2. In the Property dialog box, modify the NE attribute and click OK to save your
changes.
3.1.4.3 Deleting an NE
The following introduces how to delete an NE in the OTNM2000.
3-14 Version: A
Caution:
u When an NE is deleted, the icon, card and topological connection of

the NE will be deleted simultaneously. Meanwhile, the services
carried by the NE will be broken.
u When only the MA NE exists under a network block, deleting the MA

NE will also delete the network block to which it belongs. However,
when there are multiple NEs under a network block, the MA NE
cannot be deleted.
Prerequisite
Procedure
1. Right-click the NE in the Logical Tree pane and select Delete NE to open the
Delete NE dialog box.
2. Confirm the NE to be deleted and click Delete.
Version: A 3-15
Caution:
When the Delete NE dialog box appears as shown in the following figure,
go to the Business Management menu to check and adjust the service
carried by the NE to another NE according to the prompt in red.
Otherwise, deleting the NE directly will greatly influence the service.
3.1.5 Managing Cards
The following introduces how to add, replace, edit and delete cards in the
OTNM2000.
3.1.5.1 Adding a Card
The following introduces how to add a card in the OTNM2000.
Note:
After an NE is added, the system will automatically add the core switch
card (in the default slot for the core switch card).
Prerequisite
3-16 Version: A
u The corresponding NE has been created.
Procedure
1. Right-click the null slot in the NE shelf view (using CiTRANS 620 as an example)
and select the desired card from the shortcut menu.
3.1.5.2 Replacing a Card
The following introduces how to replace a card in the OTNM2000.
Prerequisite
Procedure
1. Right-click the card in the NE shelf view (using CiTRANS 620 as an example),
select Replace the Card from the shortcut menu and select the new card.
Version: A 3-17
2. Confirm the target card and click Replace.
Caution:
When the Delete Board dialog box appears as shown in the following
service carried by the card to another card according to the prompt in red.
Otherwise, replacing the card may influence the service.
3.1.5.3 Editing a Card
The following introduces how to set the attributes of cards in the OTNM2000,
convenient for querying and maintaining the cards of the project.
Prerequisite
Procedure
1. Right-click the card in the NE shelf view and select Property from the shortcut
menu to open the Property dialog box.
3-18 Version: A
2. Specify the attributes related to the card and click OK.
3.1.5.4 Deleting a Card
The following introduces how to delete a card in the OTNM2000.
Caution:
When a card is deleted, the topological connection of the card will be also
deleted. Meanwhile, the services carried by the card will be broken.
Prerequisite
Version: A 3-19
Procedure
1. Right-click the card in the NE shelf view and select Delete the card from the
shortcut menu to open the Delete Board dialog box.
2. Confirm the card to be deleted and click Delete.
Caution:
When the Delete Board dialog box appears as shown in the following
service carried by the card to another card according to the prompt in red.
Otherwise, deleting the card directly will greatly influence the service.
3.1.6 Managing Topology Fiber Connections
The OTNM2000 provides the function of managing topology fiber connections. The
following introduces how to add, edit and delete the connection lines.
3.1.6.1 Adding a Fiber Connection
The following introduces how to add fiber connections in the OTNM2000.
Prerequisite
3-20 Version: A
u Before adding the connection, you need to select the desired NE from the
Logical Tree and drag it to the main topology.
Procedure
1. Right-click an NE (the source NE) in the topology and select Add Link from the
shortcut menu.
2. Click the other NE (the sink NE), and the Add Link... dialog box appears.
Version: A 3-21
3. Set the card name, port information and other parameters of the source and
sink NEs, and then click Add. The new connection appears in the topology.
3.1.6.2 Editing a Fiber Connection
The following introduces how to modify the connection lines between the stations in
the OTNM2000 topology, including the connection annotation, connection No.,
connected port, connection line color as well as the line curvature.
Prerequisite
Procedure (Modifying Connection Attributes)
1. Right-click a connection in the topology.
3-22 Version: A
2. Select Link Property to open the Link Property dialog box. Modify the
attributes and click Modify.
Version: A 3-23
Procedure (Setting the Line Color)
1. Right-click a connection in the topology,
2. and select Modify the selected lines colorsCustomized Color from the
shortcut menu to open the Color dialog box. Select the new color and click OK.
Procedure (Modifying the line curvature)
1. In the main topology, click the button.
2. Double-click the connection between two NEs and select Convert Anchor
from the shortcut menu to set the line curvature.
3. After setting is completed, click Finish. The connection line after the
modification is as shown in the figure below.
3-24 Version: A
3.1.6.3 Deleting a Fiber Connection
The following introduces how to delete fiber connections in the OTNM2000.
Caution:
When a fiber connection is deleted, the services carried by it will be

damaged.
Prerequisite
Procedure
1. Right-click a connection in the topology (the selected connection line turns to

yellow) and select Delete from the shortcut menu to open the Delete Fiber
Connection dialog box.
Version: A 3-25
2. Confirm the connection and click Delete to delete the connection line.
Caution:
When the Delete Fiber Connection dialog box appears as shown in the
following figure, go to the Business Management to check and move the
services carried by the link to other card according to the prompt in red.
Otherwise, deleting the fiber connection will influence the services.
3.1.6.4 Optimized the Topology Connection Adding Function
This version optimizes the topological connection between NEs and implements
setting the sink NE manually. This solves the inconvenience of the previous version,
3-26 Version: A
in which the sink NE needs to be searched among a large number of NEs, greatly
improving the topological connection adding efficiency.
Prerequisite
u Before adding the connection, you need to select the desired NE from the
Logical Tree and drag it to the main topology.
Procedure
1. Right-click an NE (the source NE) in the topology and select Add Link from the
shortcut menu.
2. Click the other NE (the sink NE), and the Add Link... dialog box appears.
Version: A 3-27
3. In the Dest port info combo box, set the network block No., NE No., card name
and port information of the sink NE, click ApplyAdd to add a connection from
the source NE to the desired sink NE.
3.1.6.5 Optimized Topology Connection Display
There are commonly multiple topological links between two NEs, presenting too
many links in the main topology which are inconvenient inconvenient for displaying
and viewing. For better display and viewing, this version implements link
aggregation in case of multiple links between two NEs to simplify the complicated
topological chart.
Prerequisite
3-28 Version: A
Procedure
1. In the Current View of the main topology, confirms that the button pops
up.
2. Double-click one of the multiple links between the NEs to implement the link
aggregation, as shown in the figure.
Note:
The +(*) appears on the link after the aggregation. The asterisk *
indicates the number of links aggregated.
Other Operations
Double-click the link after the aggregation to expand the links.
3.1.7 Configuring NE IP Remotely based on SN
The SN refers to the 12-digit serial number of the device NMU card, similar to the
MAC address of the computer. This SN must be unique in the entire network. The
SN has already been downloaded to the device NMU card upon delivery. Commonly,
the SN of each NMU card will be labeled on the card panel.
The OTNM2000 configures and downloads the IP address locally and remotely
based on SN to complete configuring IP addresses of the NEs in the entire network.
This version adds the EMS Device SN, indicating the device SN stored in the EMS-
side database. This provides convenience for you to compare the SN written into
the device with that labeled on the device (EMU Device SN), ensuring the
uniqueness of the SN in the entire network.
Version: A 3-29
1. Configure the IP address of the local NE (local download).
Connect the network management computer directly with the local NE and the
OTNM2000 will obtain the SN of the NMU card of the local NE and configure
the IP address and switch. Then it downloads the mapping relationship
between SN and IP address to the local NE.
Note:
Local NE: Indicates the NE directly connected to the network

management computer through a network cable.
2. Configure the IP address of the neighboring NE (remote download).
1) After the IP address of the local NE is configured, the OTNM2000 will

obtain the SN of the NMU card of the neighboring NE based on the SN of
the NMU card of the local NE, and configure the IP address and switch of
the neighboring NE. Then it downloads the mapping relationship between
SN and IP address to the neighboring NE.
2) The OTNM2000 obtains the SN of the NMU card of the neighboring NE

based on the NE whose IP address has already been configured. In this
way, it finally finds all NEs and completes configuring the IP addresses of
the NEs in the entire network.
3-30 Version: A
Note:
u Neighboring NE: Indicates the NE directly connected to the source

NE through an optical path or network cable without no NEs between
them.
u Only when the neighboring NE communicates with the source NE

smoothly through the MCC channel can the neighboring NE be
detected by the source NE.
u If multiple neighboring NEs are found simultaneously, you can refer

to the corresponding project design document (listing the SNs of the
NMU cards corresponding to the NE) for the specific NE.
3.1.7.1 Configuring the IP Address of the Local NE
The following introduces how to set the mapping between the IP address and SN of
the local NE.
Prerequisite
u The project network planning, NE IP address and domain planning is prepared.
u The card of the local NE are configured.
u The physical connection between the network management computer and the
local NE is completed.
Procedure
1. Select ConfigurationNE IP Remote Config.
Version: A 3-31
Note:
The NE IP Remote Config window lists the NEs whose basic

configuration has been completed.
2. Set the local NE: Select a local NE entry in the NE IP Remote Config window,
and then select SettingsSet as Local NE.
3. Query the SN of the local NE: In the NE IP Remote Config window, select
QueryRead Local NE SN.
3-32 Version: A
Note:
If there are multiple local NEs as the network management server is

connected through Hub, the SN will be randomly obtained. You need to
confirm the SN corresponding to the equipment according to the SN label
on the NMU card panel of the device.
4. Set the IP address and switch-related parameters of the local NE: Click each
parameter field to set according to Table 3-1.
Table 3-1 NE IP Address Settings
Item Description
SN Default setting, which does not need to be modified.
u For the local NE, this item displays the network block / NE number
stored in the database.
Object u For the remote NE, this item automatically displays the network block /
NE number according to the neighboring SN detection sequence.
u NE number in descending order
EMU SN SN of the NMU card.

It displays the IP address of the NE that detects the neighboring NE for the
neighboring NE.
Source NE IP For example, suppose NE 1 is the local NE with the IP address 11.18.1.1,
and NE 2 is the neighboring NE of NE 1, the Source NE Address of NE2 is
11.18.1.1.
The switch 1 and switch 2 are the NE IDs and the combination of switch 1
Switch 1/2
and switch 2 must be unique in the entire network.
IP address of the NE, which must be unique in the entire network.

As the local NE is connected with the network management server through
IP address network cables, the IP address of the NE must be in the same subnet as the
IP address of the network card on the network management server;
otherwise, detecting the SN of the neighboring NE may be influenced.
IP Mask 255.255.255.0
IP Gateway No need to set.
Note 1: Adopt the default settings for the parameters not listed above.
5. Download the IP configuration of the local NE: In the NE IP Remote Config

window, click SettingsWrite Local NE IP.
Version: A 3-33
6. Save the IP address of the local NE and the switch-related parameter settings:
In the NE IP Remote Config window, select SystemSave Configuration.
Note:
After saving the settings, you can go to the NE Property Config to query
the IP address and switch information of the NE.
3.1.7.2 Configuring the IP Address of the Neighboring NE
The following introduces how to set the mapping between the IP address and SN of
the neighboring NE.
Prerequisite
u The project networking planning, NE IP address and domain planning is

prepared.
u The IP address of the local NE is configured.
u The attributes and card of the neighboring NE are configured.
u The neighboring NE communicates with the source NE smoothly through the

MCC channel.
Procedure
1. In the NE IP Remote Config window, refer to the related project design

document and IP planning, and double-click the parameter bar to configure the
SN, IP address, switch and other information of other NEs.
2. Click to save the settings.
3. Obtain the SN of the neighboring NE: Select a local NE entry in the NE IP

Remote Config window, and then select QueryFind Near NE by SN.
3-34 Version: A
4. Compare the SN of the NE automatically detected and the SN of the created

NE. Download the IP address If they are consistent. When the IP address is
downloaded, the NMU card is reset.
1) For the NE whose SN is consistent with that of the NE automatically

detected, set the Source NE IP, which should be consistent with that of the
NE automatically detected.
2) Select the NE entry whose IP address is to be downloaded in the NE IP

Remote Config window, select SettingsWrite Remote NE IP.
Caution:
u Downloading the IP address of the NE means downloading the

mapping between the SN and the IP address. The SN deleted is
used to compare with the SN labeled on the NMU card and check
whether the SN manually configured is correct. If there are
inconsistent, the SN automatically detected should be taken as the
standard one. Do not download IP address to the NE automatically
detected and generated before the comparison.
u The number of NEs to which the IP addresses are downloaded

cannot exceed 20. Once the limited is exceeded, the OTNM2000 will
gives the corresponding prompt. In this situation, you can download
them gradually.
5. Detect other neighboring NEs based on the neighboring NE whose IP address

is configured. Repeat Step 4 to complete configuring the IP addresses of the
neighboring NEs.
Version: A 3-35
6. Repeat Step 5 to compete configuring the IP addresses of the NEs in the entire
network and then close NE IP Remote Config window.
3.2 OTNM2000 GUI Optimization
The OTNM2000 adopts an entirely new user graphic interface (GUI), on which the
functional menus are sorted and adjusted for you to conveniently monitor and
manage the network, improving the user-friendliness of the OTNM2000 GUI.
u Sorts out and adjusts the menus of the OTNM2000.
u Re-designs and beautifies the GUI layout and pattern as well as the icons.
u Unified the names of the tabs.
Main GUI
The OTNM2000 adopts a completely new GUI, including an overall improvement on

main menus, tool bar, status bar as well as beautification on subject style and icons.
3-36 Version: A
Main Menu
u System
u View
u Business Management
Version: A 3-37
u Service Configuration
3-38 Version: A
u Configuration
u Alarm
Version: A 3-39
u Performance
u Statistics
3-40 Version: A
u Security
u Help
Version: A 3-41
Directly displayed tabs
The names of the tabs in the main GUI directly express the contents of the
respective tabs. For example, User Management.
3.3 Optimized Alarm Indicator Display
The optimized OTNM2000 alarm indicator display changes the double-alarm

indicator into single-alarm indicator, making the alarm indicator display more
concise and intuitive.
Context
The alarm indicator directly displays the alarm information of the equipment in
different colors according to different alarm levels, helping you quickly locate the
related alarm monitoring point.
3-42 Version: A
The current OTNM2000 double-alarm indicator mechanism reflects the alarm

information in a complex way, which may influence the alarm processing efficiency.
The optimized OTNM2000 alarm indicator display changes the double-alarm
indicator into single-alarm indicator, and supports customized prompt icon for
focused alarms, making the alarm indicator display more concise and intuitive.
Alarm Indicator
The alarm indicator is composed of the main indicator, frame and prompt icon. The
main indicator of the main topology and logical tree differs from the main indicator of
the subrack and card in that the former displays object types using different icons.
Position Alarm Indicator Example
Main Topology
Logical Tree
Subrack
Vertically plugged card
Horizontally plugged card
u Main indicator: The color of the main indicator depends on the color of the
highest priority level of the unended alarms (excluding interruption alarms).
u Frame: The color of the frame depends on the color of the highest priority level
of the unconfirmed alarms.
u Prompt icon: Prompts the focused alarm and interruption alarm information. In
case of coexisting of focused alarms and interruption alarm, the defined icon for
focused alarms will be displayed preferentially. If there are no customized
alarms or interruption alarms, the prompt icon will be not displayed.
Version: A 3-43
Note:
The icon for focused alarm is set in the Alarm Report Settings dialog
box.
Alarm Color Description
The relationship between the default alarm colors and alarm levels are shown in
Table 3-2.
Table 3-2 Alarm Color Description
Alarm Priority Alarm Color Alarm Level
Red Critical alarm

Orange Major alarm
Yellow Minor alarm

Blue Prompt alarm
Green Normal
3.4 Layer-based Topology
The OTNM2000 manages the network topology through the main topology. You can
understand the networking status information and monitor the running status in real
time in the topological view.
The OTNM2000 of the R0550 version implements the layer-based topology display,
which graphically displays topological connections among NEs and NE groups,
including the paths among nodes and the information of NEs based on layers. This
helps locate and manage NEs, improving management efficiency.
u Manages the topology based on layers and changes the topological view in the
previous version, in which too much NEs are displayed with no layer-based
display function, inconvenient for locating commonly concerned objects.
3-44 Version: A
u Reasonably places the stations in an area at a same layer, convenient for you
to quickly select the source / sink stations and set the routes in the topology,
without the need to drag over the topology. This greatly improves the service
configuration efficiency.
3.4.1 Setting Topology Layers
The topology displays the tree on the left and the graph on the right. On the left is
the navigation tree displaying the topological objects and the layer relationship
among them; on the right is the topological chart displaying all the topological
objects in the current physical topology view and their location relationship. For
convenient management, the topological objects in the same area or of the similar
attributes can be placed and displayed at a same topological layer.
Context
According to the actual network, the layer-based topology of the R0550 version
supports classifying objects into different layers by device type or NE type, meeting
different management requirements.
u It supports quick display of layer-based topology through multiple ways,

including system-defined layers and layers classified according to device type.
u The Default Layer is a system-defined layer. All the uncategorized NEs will be
added to this layer.
u Each NE can be added into only one layer.
u This version supports up to nine topological layers.
u Even when an NE is deleted from the customized view, it exists in the

corresponding physical view.
Procedure
1. Select ViewTopo Layer Management to open the Topo Layer

Management tab.
2. Click to open the "Add Topology Layer" dialog box. Then select Basic
Property tab to set the name and remark information of the topological layer.
Version: A 3-45
3. Select the Member tab, select the desired NE in the NE to be Selected box
and click or to add it into the Selected NE box.
Note:
u : Indicates adding the selected objects in the left box into the
right box.
u : Indicates adding all the objects in the left box into the right
box.
u The object selection supports fuzzy query. Click to filter the

objects by NE name or NE type.
4. Click to save the topology layer settings.
3-46 Version: A
Other Operations
The other shortcut icons on the toolbar of the Topo Layer Management tab are
described in the following figure:
Icon Description
Deletes the selected layer.
Modifies the selected layer.
Moves up the selected layer.
Moves down the selected layer.
Categorizes all NEs into Core Layer, Convergence Layer and

Access Layer according to their device type.
Note: When this button is clicked, the customized layers
will be deleted and all the NEs will be re-categorized
according to their device types.
3.4.2 Modifying Topology Layers
After setting the topology layers, you can modify their basic attributes and members
as needed.
Procedure
1. Select ViewTopo Layer Management to open the Topo Layer

Management tab.
2. Modify basic attributes of the topology layer.
1) Select the desired layer and click to modify the layer name and remark
information.
Version: A 3-47
2) Click OK.
3. Adjust the members at the layer.
4 Method 1
a) Select the desired layer and click to open the Modify Property of
Layer dialog box.
b) Select the Member tab and click or to adjust the

members.
c) Click OK.
4 Method 2
a) Double-click the desired layer, or select the desired layer and click the
Detail button at the lower left corner of the Topo Layer Management
window to open the Detail pane.
b) Expand the members at the selected layer.
3-48 Version: A
c) Right-click the member to be adjusted and select Delete or Move to

to delete the member or move it to another layer.
4. Click to save the topology layer settings.
5. In the displayed dialog box that prompts successful saving, click OK.
3.4.3 Viewing the Layer-based Topology
The following introduces how to view the topology based on layers to understand
the structural information of the topology.
Context
The layer-based topology adopts the display mode similar to the way how the map
is browsed (a city includes the information of all its urban areas and streets). The
layer-based topology display adopts this browsing mode. When you select the layer
at the top of the Current View drop-down list, all the NEs at the selected layer as
well as those at the layers under the selected one will be displayed in the main
topology. The layer-based topological view has the following functions:
u It supports layer-based navigation, which means scrolling up / down the mouse

to zoom in / out the topology will switch the topology among different layers.
u When the current view is locked, zooming in / out the topology will not switch
the current view.
u A network block can be taken as an independent layer to view the NEs under it.
u The NEs uncategorized into layers will be displayed in Default Layer.
Version: A 3-49
Procedure
1. View the topology information in the Main Topology tab.
2. Click to the right of Current View to select the desired layer from the drop-
down list.
Note:
The topological chart will display the NEs at the selected layer and those
at the layers under the selected one. For example, if you select Core
Layer, the topological chart displays the members at the access layer,
convergence layer and core layer.
3-50 Version: A
Shortcut Icon Description
The shortcut icons on the toolbar at the top of the topological chart are described in
the following figure.
Icon Description
Locks / unlocks the current view. When the current view is

locked, zooming in / out the topology will not switch the
current view.
Switches to the selected mode, in which you can select the
topology objects.
Switches to the drag mode, in which you can move the

topology view.
Opens / closes the thumbnail view.
Opens / closes the editing mode, in which you can drag the
NE.
Opens the Chart pane to view the object type and status
information corresponding to each icon in the topology view.
Zoom in the topology.
Zoom out the topology.
Restore the topology to the original size.
Select the display size of the topology.
Other Operations
u If the current view is not locked, scrolling the mouse wheel or zooming in / out
the topology will switch the topology among different layers according to the
scaling.
u If the current view is locked, scrolling the mouse wheel or zooming in / out the
topology will scale the current view to reach the best display.
u Select a network block in Logical Tree, and then select ViewTopo Display
Show NE in the network block only in the main menu to only display the
NEs under a specific network block.
Version: A 3-51
3.5 Authorization and Domain Division
The OTNM2000 implements the authorization and domain division function by

dividing the operation groups and object groups. With the authorization division
(operation groups) management function, you can divide the EMS authorities into
different functional domains, and with the domain division (object groups)
management function, you can divide equipment units into different network
domains. For the OTNM2000 users, you can grant them with authority combinations
consisting of different functional domains and network domains so as to conduct
effective control over user management authorities.
3.5.1 Basic Concepts
The administrative objects of authorization and domain division include user groups,
operation groups, object groups and users. Understanding the concepts related to
the authorization and domain division helps plan and allocate user authorities.
User Group
A user group is a set of OTNM2000 users with the same management authorities.
For the users to be granted with the same authorities, you can add them into a same
user group and authorize the user group to make every user in the user group have
the same authorities, quickly allocating the authorities to users.
The OTNM2000 provides the following default user groups, among which
Administrators, Security Administrator Group, Devcfg, Eot Group and NMS Group
cannot be deleted and modified.
u Administrators: This user group has the management domain over assembly of
objects and operation authorities over assembly of application operations.
Note:
The Assembly of Application Operations does not include the operation

authorities related to the security management.
3-52 Version: A
u Security Administrator Group: This user group has the operation authorities
related to the security management, including user management and online
user management.
u Operator Group: This user group has the management domain over assembly
of objects and operation authorities over assembly of application operators by
default.
u Maintainer Group: This user group has the management domain over assembly
of objects and operation authorities over assembly of application maintainers
by default.
u Inspector Group: This user group has the management domain over assembly
of objects and operation authorities over assembly of application inspectors by
default.
u Devcfg: This user group has the operation authorities of the Devcfg.
u Eot Group: This user group has the operation authority of the Eot group.
u NMS Group: This user group has the operation authority of the OTNMApi.
When the upper-level NMS system connects to the OTNM2000 through the
northbound interface, you need to create a user for the NMS on the
OTNM20000 and add the user into the NMS group. The NMS group is for
managing the access authorities of the NMSs.
If the default user groups do not meet the requirements, you can create user groups
of the two types: Domain Security Admin Group and Common User Group.
Security administrators (users in the Security Admin Group user group) can create
sub domain security administrator groups and common user groups, while the sub
domain administrator can only create common user groups. Creating a sub domain
administrator group equals creating a sub domain. The users belonging to the sub
domain administrator group have the operation authorities within the sub domain
range, that is, the object sets, operation sets, user groups and users created by a
sub domain administrator are only visible to the sub domain administrators in the
same group. When creating a common user group, the operation authority cannot
be set as the security management authorities.
Version: A 3-53
Operation Group
An operation group is a set of operation authorities provided by the OTNM2000.

When a user or user group is bound with an operation group, this user or user group
has all the operation authorities of the operation group. By creating an operation
group and adding the required operation authorities into the operation group, you
can allocate the authorities to relevant users or user groups, implementing quick
allocation of user authorities.
The OTNM2000 EMS provides the following default operation groups:
u Assembly of Application Operations: Includes the operation authorities of all NE

applications except the security management.
u Assembly of Application Operators: Includes the operation authorities of

creating NEs, modifying NEs and deleting NEs of integrated configurations.
u Assembly of Application Maintainers: Includes the authorities of alarm

confirmation.
u Assembly of Application Inspectors: Includes the authorities of viewing alarms

and performance.
Object Group
An object group is a set of manageable objects provided by the OTNM2000. When

a user or user group is bound with an object group, this user or user group has the
authorities to manage all the objects in the object group. By creating an object group
and adding the objects to be managed into the object group, you can specify a user
or user group to manage all the objects in the object group, lowering the
management cost. You can create object groups based on geographical regions,
network layers or equipment type.
The object group provided by the OTNM2000 by default is Assembly of Objects,

which cannot be deleted or modified. The objects include subnets, network blocks
and NEs, with the NE as the smallest granularity.
User
For the OTNM2000 client users, their usernames and passwords uniquely
determine their respective operation and management authorities on the
OTNM2000.
3-54 Version: A
There are two default built-in users: admin and root. The "admin" user is a system
administrator, which cannot be deleted or modified.
Authority Allocation
Binding a user with an operation group, object group and user group implements the
authorization and domain division function. After a user logs in, the OTNM2000 only
displays the sets of equipment applicable to the user group that the user belongs to
and the user can only perform the operations defined in the bound operation group
on the equipment; The path list of the domain user are the paths among the NE
nodes managed by the user. The cross-domain paths will only appears in the global
user's path list, which means it will not appear in the domain user's path list.
Authorities can be assigned to a user through the following ways:
u Adding a user into a specific user group so that the user has the authorities
assigned to the user group.
u Binding a user with a specific object group and operation group.
Note:
u One user can be added into multiple user groups simultaneously,

and therefore the final authorities of the user are the user's original
authorities coupled with the authorities of the user groups to which
the user belongs.
u It is recommended to bind a user with a or more user groups to

authorize the user instead of directly authorizing the user (by binding
the user with operation groups and object groups) or adjusting the
default user group for user authorization.
3.5.2 Scenarios for Authority and Domain Division
There are two scenarios applicable for authorization and domain division: initial
authorization and authority adjustment. See Table 3-3 for operations according to
your situation.
Version: A 3-55
Table 3-3 Description of the Authority and Domain Division Scenario
Scenario Description Sub Scenario
1. Make an authorization plan.

Make a plan before the authorization to reduce
After installing the OTNM2000, you
unnecessary authorization and maintenance
Initial need configure and authorize the
workload.
Authorization administrator for managing sets of
2. Authorize the users.
equipment.
Authorize the users according to the authorization
plan.
u Adjust authorities in case of adding or removing of

equipment sets.
After new sets of equipment (NE or the entire
subnet) is deployed, you need to authorize the
When the initial authorization is corresponding user group to manage the
completed, the authority maintenance equipment. After any sets of equipment is
Authority begins. When any sets of equipment is removed, the authorities for managing the
Adjustment added or removed, or user authorities equipment will be automatically removed from the
are changed, you need to adjust users' corresponding user or user group.
authorities. u Adjust authorities in case of authority change.
You need to adjust users' authorities when their
authorities are required to change due to
administrative NE scope change, operation
authority change or role change.
3.5.3 Authorization Planning
Make a plan before the authorization to reduce unnecessary authorization and

maintenance workload. The authorization plan flow is as shown in Table 3-4.
3-56 Version: A
Table 3-4 Authorization Planning Flow
Planning Flow Content Principle
You can sort out the equipment

management division table as the original
data of authority management according
to your organization structure and
equipment networking.
Analyze the original data for subsequent
planning based on the following
Collect original data of requirements:
-
authority management. u Sort out the users managing the
same devices, that is, the users
belong to the same object group.
u Sort out the users with the same
responsibilities, including not only
the same administrative equipment
but also the same operation
authorities.
Add the users with the same authorities
Classify users according their into a same user group. For users with
Configure user groups
responsibilities. different authorities, plan different user
groups.
For the users with the same

Plan how to group the administrative administrative scope, plan their object
Configure operation groups objects to fulfill efficient authorization, group together. For users with different
convenient for subsequent maintenance. administrative scope, plan different object
groups for them.
For user groups requiring the same

Analyze the authorities required for users
operation authorities, define the same
to fulfill the corresponding management
Configure operation groups operation set for them. Otherwise, define
and define these operation authorities
operation sets respectively for each user
into operation set.
group.
Sort and output the complete

authorization planning, providing
reference for authorization and
Output authorization subsequent authority maintenance.
-
planning summary listing The authorization planning summary
listing should include user group name,
user group members, management
domain and operation authorities.
Version: A 3-57
3.5.4 Managing Object Groups
An object group is a set of manageable objects. Managing object groups help you
centrally manage the equipment objects.
u The default object group of the OTNM2000 is Assembly of Objects, which

including all manageable objects.
u When a user or user group is bound with an object group, this user or user
group has the authorities to manage all the objects in the object group.
u Only the users in "Security Admin Group" and "Domain Security Admin Group"
can manage object groups.
u The default object group cannot be deleted and only its description information
can be modified.
3.5.4.1 Viewing Object Groups
You can view the objects included in an object group to check whether the objects
meet the requirements.
Prerequisite
You have logged into the OTNM2000 as a user belonging to Security Admin
Group or Domain Security Admin Group.
Procedure
1. Select SecurityUser Management from the main menu to open the User
Management window.
2. Expand the Object Group node in the left pane to view the existing object
groups.
3. Select the desired object group, click the Member tab on the right to view the
specific objects included in the object group.
3-58 Version: A
Other Operations
u Delete an object group.
Right-click the object group, select Del from the short menu and click Yes in the
displayed alert box.
u Modify a object group.
Select the desired object group in the left pane, modify the corresponding
information in the right pane as needed and click Apply.
Note:
For the "Assembly of Objects", only the description information can be

modified.
3.5.4.2 Creating Object Groups
You can create user groups according to your needs.
Prerequisite
Procedure
Management window.
Version: A 3-59
2. Select one of the following access methods to open the Add Object Group
dialog box.
Function- Access Method

al Item
Right-click Object Group in the left pane and select Add Object Group from the
Creating shortcut menu.
an Object Click Object Group in the left pane and then click the Add Object Group button
Group in the right pane.
Click Object Group in the left pane, right-click in a blank area in the right pane
and select Add Object Group from the shortcut menu.
3. Set the object group name and description information in the Basic Info tab
according to the planning.
4. In the Member tab, expand the Device node under Object For Select on the
left, select the members and click to add them into the Object
Selected on the right.
5. After completing the settings, click OK in the Add Object Group dialog box.
3.5.5 Managing Operation Groups
An operation group is a set of operations. By managing operation groups, you can

allocate and manage the operations to be performed on the equipment.
3-60 Version: A
u The default operation groups of the OTNM2000 include Assembly of

Application Operations, Assembly of Application Operators, Assembly of
Application Maintainers and Assembly of Application Inspectors.
u When a user or user group is bound with an operation group, this user or user
group has all the operation authorities assigned to the operation group.
can manage operation groups.
u The default operation groups cannot be deleted and only their description
information can be modified.
3.5.5.1 Viewing Operation Groups
You can view the operation objects included in an operation group to check whether
the authorities in the operation group meet the requirements.
Prerequisite
Procedure
Management window.
2. Expand the Operation Group node in the left pane to view the existing
operation groups.
3. Select the desired operation group, click the Member tab on the right to view
the specific operation objects included in the operation group.
Version: A 3-61
Other Operations
u Delete an operation group.
Right-click the operation group, select Del from the short menu and click Yes in
the displayed alert box.
u Modify an operation group.
Select the desired operation group in the left pane, modify the corresponding
information in the right pane as needed and click Apply.
Note:
The default operation groups cannot be deleted and only their description
information can be modified.
3.5.5.2 Creating Operation Groups
You can create operation groups when the existing operation groups do not meet
your requirements.
Prerequisite
3-62 Version: A
Procedure
Management window.
2. Select one of the following access methods to open the Add Operation Group
dialog box.
Functional Access Method

Item
Right-click Operation Group in the left pane and select Add Operation Group
Creating an from the shortcut menu.
Operation Click Operation Group in the left pane and then click the Add Operation
Group Group button in the right pane.
Click Operation Group in the left pane, right-click in a blank area in the right
pane and select Add Operation Group from the shortcut menu.
3. Set the operation group name and description information in the Basic Info tab
4. In the Member tab, select the members under Operation For Select on the left
and click to add them into the Operation Selected on the right.
5. After completing the settings, click OK in the Add Operation Group dialog
box.
Version: A 3-63
3.5.6 Managing User Groups
A user group is a set of OTNM2000 users with the same management authorities.
For the users to be granted with the same authorities, you can add them into a same
user group and authorize the user group to make every user in the user group have
the same authorities, quickly allocating the authorities to users.
u The OTNM2000 built-in default user groups include Administrators, Security

Administrator Group, Operator Group, Maintainer Group, Inspector Group,
Devcfg, Eot Group, and NMS Group.
u When a user is bound with a user group, this user owns the authorities
assigned to the user group.
can manage user groups.
u The default user groups "Administrators", "Security Administrator Group",

"Devcfg", "Eot Group" and "NMS Group" cannot be deleted and only their
description information can be modified.
3.5.6.1 View User Groups
You can view the objects and operations corresponding to a user group so as to
check whether the authorities assigned to the user group meet the requirements.
Prerequisite
You have logged into the OTNM2000 as a user in Security Admin Group or
Domain Security Admin Group.
Procedure
Management window.
2. Expand the User Group node in the left pane to view the existing user groups.
3. Select the desired user group in the left pane, and view the related information
of the user group in the right pane.
3-64 Version: A
Other Operations
u Delete a user group.
Right-click the user group, select Del from the shortcut menu and click Yes in
the displayed alert box.
u Modify a user group.
Select the user group in the left pane, modify the corresponding information in
the right pane as needed, and then click Apply.
3.5.6.2 Creating a User Group
You can create user groups according to your needs to centrally assign authorities
to users.
Prerequisite
Procedure
Management window.
2. Select one of the following access methods to open the Add User Group
dialog box.
Version: A 3-65
Function- Access Method

al Item
Right-click User Group in the left pane and select Add User Group from the
Creating a shortcut menu.
User Click User Group in the left pane and then click the Add User Group button in
Group the right pane.
Click User Group in the left pane, right-click in a blank area in the right pane and
select Add User Group from the shortcut menu.
3. Set the relevant parameter of the user group in the Add User Group dialog box
Note:
There are two types of user group: Domain Security Admin Group and
Common User Group.
u Domain Security Admin Group: The Domain Security Admin Group,
with its management domain assigned by the security administrator,
only has the Security Management authorities, which cannot be
modified.
In case the network managed by the OTNM2000 is large with a

relatively high quantity of network objects, the security administrator
can divide the entire network into several domains and specify a
domain security administrator for each domain. The domain security
administrator responsible for a domain can create users for this
domain and assign authorities to users.
u Common User Group: The management domain and operation

authorities of a common user group are assigned by the security
administrator or domain security administrator.
4. After completing the settings, click OK in the Add User Group dialog box.
3-66 Version: A
3.5.7 Managing Users
The security administrator reasonably authorizes the EMS users to ensure the
users have necessary authorities to perform operations and meanwhile avoid
authority-exceeding operations.
Planning users should combine with the requirement of maintenance and

management, authorizing users with appropriate privileges and restraining them to
use the management and maintenance functions in corresponding situations. The
OTNM2000 V2.0R5 (Build04.20.05.50) uniquely identifies the user logged in and its
operation privileges by the username and password.
After the OTNM2000 V2.0R5 (Build04.20.05.50) is installed, it only provides the

default user: admin (username and password are admin) and the users (1, 2, 3, 4)
will be no longer used.
The admin user is the super user, who has all the operation and management
privileges. Other users will be directly or indirectly created by the admin user.
3.5.7.1 Viewing Users
You can view the related information of users, conveniently managing them.
Prerequisite
Procedure
Management window.
2. Expand the User node in the left pane to view the existing users.
Version: A 3-67
3. Select the desired user in the left pane, and view the related information of the
user in the right pane.
Other Operations
u Delete a user.
Right-click the user, select Del from the shortcut menu and click Yes in the
u Modify a user.
Select the user in the left pane, modify the corresponding information in the
right pane as needed, and then click Apply.
3-68 Version: A
3.5.7.2 Creating a User
You can create OTNM2000 user accounts, assign them with corresponding
authorities, and then allocate the accounts to users with different responsibilities.
Note:
After creating users, you can add them into corresponding user groups
and authorize the user groups to avoid cross-over authorization. It is not
recommended to set management domain and operation authorities for
users respectively.
Prerequisite
Procedure
1. Select SecurityUser Management to open the User Management tab.
2. Select one of the following paths to open the Add User dialog box.
Functional Item Path

Right-click User in the left pane and select Add User from the
shortcut menu.
Creating a User Click User in the left pane and then click the Add User button in the
right pane.
Click User Group in the left pane, right-click in a blank area in the right
pane and select Add User Group from the shortcut menu.
Version: A 3-69
3. See Table 3-5 to set the relevant parameter of the user in the Add User dialog
box according to the planning.
Table 3-5 User Settings
Parameter Description
Name of the user. It is required and should contain at least 6

User name
characters.
Description Description information of the user, for distinguishing users.
Name of the user. It should contain at least 8 characters. If the

password complexity check is enabled, the password should
Password
contain three types of characters among upper-case letters,
Basic
lower-case letters, numbers and other characters.
Information
Confirm
Type the password again.
password
Number of days in which the password is valid.

Password u If you check Unlimit, the password will never expire.
Valid Days u If you do not check Unlimit, set the specific number in the
text box. Value range: 1 to 180 days.
3-70 Version: A
Table 3-5 User Settings (Continued)
Parameter Description
Maximum number of users allowed to use this account to log

into the OTNM2000.
Max Online u If you check Unlimit, it has no limit on number of users
No. using this account to log into the OTNM2000.
u If you uncheck Unlimit, set the specified number in the text
box. Value range: 1 to 32.
Disable This If you check Disable This User, this user account cannot be
User used.
Sets the user group to which this user belongs. One user can
User Group Belong To be added into the user group of a same administrator type
(Security Administrator or Domain Security Administrator).
Object Group Belong To Sets the object group to which this user belongs.
Operation Group Belong TO Sets the operation group to which this user belongs.
Sets the allowed IP range for login, allowing the users to login
Access Control List
from the client in the specified IP range.
4. After completing the settings, click OK in the Add User dialog box.
3.5.7.3 Unlocking Users
After being unlocked, the users can log into the OTNM2000 again.
Context
u When a user's login attempts reach three times, the user will be locked. Only
the users in "Security Admin Group" and "Domain Security Admin Group" can
unlock users.
u The OTNM2000 supports manual unlocking and automatic unlocking of the

locked user.
Prerequisite
Version: A 3-71
Procedure
u Manual Unlocking
1) Select SecurityUser Management from the main menu to open the

User Management window.
2) Expand the User node in the left pane.
3) Right-click the locked user, and select Unlock User from the shortcut
menu.
u Automatic Unlocking
A locked user cannot log into the OTNM2000 until it is automatically unlocked
after specified time period.
Note:
The system automatically unlocks the locked user accounts in the

following ways:
u Unlock user accounts 30 minutes later since the lockup.
u Unlock user accounts at midnight.
3.5.7.4 Resetting the User Password
The following introduces how to reset the user password. In case a user forgets the
password, the password expires or the user login is denied, you need to reset the
password for the user.
Context
u A user in Security Admin Group can reset the passwords for all the users
except admin and himself / herself.
u A user in Domain Security Admin Group can reset the passwords for its
created users.
u The password of Admin cannot be reset.
3-72 Version: A
Prerequisite
Procedure
Management window.
2. Expand the User node in the left pane.
3. Right-click the corresponding user account, select Reset Password from the
shortcut menu.
4. In the Reset Password dialog box, set the New Password and Confirm New,
and then click OK.
3.5.7.5 Setting the User Login Detection
An IP address, after being specified in the login detection settings, can log into only
one client at a time.
Prerequisite
Group.
Procedure
1. Select SecurityUser Management to open the User Management tab.
Version: A 3-73
2. Click the User node, and click the Login Check Setup button in the right pane
or right-click in the right pane to select Login Check Setup.
3. Click Add in the User Login Check Setup dialog box.
4. Type the desired IP address in the IP Address text box, and click OK.
5. After completing the settings, click OK in the User Login Check Setup dialog
box.
3.5.7.6 Querying User Authorities
The following introduces how to view the user authorities.
3-74 Version: A
Prerequisite
You have logged into the OTNM2000 as a user belonging to "Security Management
Group".
Context
A user's original authorities coupled with the authorities of the user groups to which
the user belongs amount to the total authorities of the user. For example,
As shown in the above figure, the user "test" owns the following authorities:
u For the objects in the Object Group A, the user has the operation authorities
defined in Operation Group A.
u For the objects in the Object Group B, the user has the operation authorities
defined in Operation Group B.
However, the user "test" cannot perform the operations defined in Operation Group
B on the objects defined in Object Group A, and similarly the user cannot perform
the operations defined in Operation Group A on the object defined in Object Group
B.
Procedure
Management window.
2. Expand the User node in the left pane, and select the desired user.
Version: A 3-75
4 View the user groups to which the user belongs. In the right pane, click
User Group Belong To to view the user groups to which the user is
added.
4 View the object groups to which the user belongs. In the right pane, click
Object Group Belong To to view the object groups to which the user is
added.
4 View the operation groups to which the user belongs. In the right pane,
click Operation Group Belong To to view the operation groups to which
the user is added.
3. Expand User Group in the left pane to view the object groups and operation
groups associated with the user groups that the user belongs to.
4. Confirm the user's authorities through the query result of step 2 to 3.
3.5.8 Authorization and Domain Division Example
The following uses an example to introduce the operations related to the

authorization and domain division.
3.5.8.1 Authorizing a New User
The following takes assigning authorities for users in two regions as an example to
introduce how to create user accounts and assign authorities.
Scenario Description
There are region A and region B. The equipment in the two regions are centrally
monitored managed and maintained through the OTNM2000. To have the
equipment in region A monitored, managed and maintained by the staff in region A
and the equipment in region B by the staff in region B, you need to create user
accounts and allocate authorities for the staff in region A and region B respectively.
Procedure
1. Create object groups.
3-76 Version: A
Create object group A and object Group B according to the region, and add the
equipment sets in region A into object group A and the equipment sets in region
B into object group B.
For creating object sets, see Creating Object Groups.
2. Create operation groups.
Adopt the default operation sets according to the users' responsibilities.
4 The user responsible for monitoring the equipment corresponds to the

operation group Assembly of Application Inspectors.
4 The user responsible for operating the equipment corresponds to the

operation group Assembly of Application Operators.
4 The user responsible for maintaining the equipment corresponds to the

operation group Assembly of Application Maintainers.
For details of creating operation groups, see Creating Operation Groups.
3. Create user groups.
According to the users' responsibilities, it is required to create six user groups,

as shown in Table 3-6.
Table 3-6 Creating User Groups
User Group Type Management Authorities

Name Domain
Inspector Group Common User
Object Set A Assembly of Application Inspectors
A Group
Operator Group Common User

Object Set A Assembly of Application Operators
A Group
Maintainer Common User Assembly of Application

Object Set A
Group A Group Maintainers
Inspector Group Common User

Object Set B Assembly of Application Inspectors
B Group
Operator Group Common User

Object Set B Assembly of Application Operators
B Group
Maintainer Common User Assembly of Application

Object Set B
Group B Group Maintainers
For details of creating user groups, see Creating a User Group.
4. Create users.
Version: A 3-77
4 Create user basic information, such as user name and password.
4 Set the user groups to which the users belong respectively. Suppose six
users A, B, C, D, E and F are created. You can add the users into the
respective user groups, as shown in Table 3-7. After being added into the
corresponding user groups, the users own the management domain and
operation authorities of their corresponding user groups.
Table 3-7 Creating Users
User User Group
A Inspector Group A
B Operator Group A
C Maintainer Group A
D Inspector Group B
E Operator Group B
F Maintainer Group B
4 Set the access control list to restrict users' login IP address to the specified
ones.
For details of creating user groups, see Creating a User.
After completing the above configurations, provide the user accounts for the
corresponding staff.
3.5.8.2 Adjusting Users' Authorities
The following takes deleting specific authorities of an existing EMS user as example
to introduce how to adjust the authorities of existing users.
Description
Delete the Modify NE authority of the EMS user B.
3-78 Version: A
Adjustment Analysis
User's Original Authorities Analysis Description
The authority adjustment

Operator Group A requirement in this example does
includes the non-default not involve any changes of the
In this example, you need to
object group Object Set management domain, and
unbind the user group Operator
A. therefore no adjustment to the
Group A with the operation group
The EMS user object group is needed.
Assembly of Application
B belongs to As the authority adjustment
Operators and then bind it with a
the non- requirement in this example
new operation group.
default user involves changes of operation
If there are other users who
group Operator Group A authorities and modifying the
require the Modify NE authority in
Operator includes the default default operation group is not
the user group, you need to
Group A. operation group recommended, you need to create
remove the user B from Operator
Assembly of an operation group that includes
Group A and then re-assign
Application Operators. all the operation authorities in
authorities to the user.
Assembly of Application
Operators except the Modify NE
authority.
Procedure
1. Create an operation group.
Create the operation group and select all the authorities in "Assembly of
Application Operators" with Modify NE removed.
For details of creating operation groups, see Creating Operation Groups.
2. Modify the user group Operator Group A.
Modify the user group Operator Group A, unbind it with the operation group
Assembly of Application Operators and then bind it with the new operation
group.
For details of modifying user groups, see View User Groups.
3.6 Network Management Tool
The Web-based network management tool is added to manage the network

management service processes, monitor system resources of network management
server and import / export configuration.
Version: A 3-79
Prerequisite
The EMS_unmcmagent and EMS_unmcmservice services are started up at the

server end.
Procedure
1. Type "http://IP:52308/nmtool" (IP indicates the IP address of the computer

running the OTNM2000 server end) in the address bar of the browser to open
the login GUI.
2. Type the username and password, and click Login.
Note:
There are two default system users:

u Both the username and password of the "admin" user are Admin.
u Both the username and password of the ordinary user are Query.
This user can only view and export data.
3. You can perform the following operations through the network management
tool (Admin is used as an example here)
Item Description
The Process window lists the information of services monitored. You

Process can start, stop or restart one or more services. You can also start, stop
or restart the EMS.
The Resource window enables you to view related information of
Resource
operation system, network management system and database.
The History Data window directly displays the resource usage of

History Data operation system, network management system and database in
graphs.
The Logs window enables you to view the operation records to know
Logs the operation-related information, including operation name, time,
terminal and result.
3-80 Version: A
Item Description
The Settings window allows you to set history data reserve time and
Settings
log data reserve time.
The Import/Export window enables you to import or export the EMS

configuration data.
u It supports setting the backup server. You can select to backup to
local computer or the FTP server and set related parameters of the
Import/Export
backup server, including local backup folder, FTP server IP
address, port, etc.
u It supports setting the timer to automatically export the EMS
configuration data.
3.7 Configuration Management
The following introduces the changes to the configuration management function.
3.7.1 Batch Control Command
This version supports issuing control commands in a batch manner, greatly

improving maintenance efficiency.
Prerequisite
Procedure
1. The batch control command function is enabled.
1) Open the otnm.ini file in the d:\OTNM\ui\ini\ directory.
2) Set BATCH_CONTROL_CMD to 1. Then save and close the otnm.ini file.
Version: A 3-81
2. In the Operational Tree, select Management ToolBatch Control

Command to open the Batch Control Command tab.
3. Select the operation type from the Batch operation drop-down list, and the
corresponding object and parameter settings are displayed in the pane below.
In this example, MSK1/GSK2A/XSK2 Board Laser Switch is selected and the

corresponding information is displayed in the pane as shown below:
3-82 Version: A
4. Select the object of the same operation type. Right-click an operation object
and select the corresponding menu as needed.
In this example, right-click the MSK1 card and select Select all MSK1 board of
this part from the shortcut menu. Then right-click the GSK2A card and select
Select all GSK2A board of this part from the shortcut menu.
5. Right-click in a blank area of the tab, and select Batch set select param from
the shortcut menu to open the Batch Set dialog box.
6. Set the parameters of the selected objects according to the batch rule and then
click OK.
Version: A 3-83
7. Click Exit to close the Batch Set dialog box.
8. In the Batch Control Command tab, click Run at the lower-right corner, and
you can view the command execution result in the Command Result column.
3.7.2 Automatic Updating Central Office Name with the NE

Name Change
When the name of an NE is modified, the name of the corresponding central office
will be updated automatically and simultaneously to make sure the NE name and
the central office name are consistent.
Prerequisite
3-84 Version: A
Procedure
1. In the Logical Tree, right-click an NE and select Modify NE from the shortcut
menu to open the Modify NE dialog box.
2. Modify the NE Name and check Automatically Synchronize Bureau Name.
3. Click OK to complete modifying the NE name, and the name of the

corresponding central office will be automatically synchronized.
3.7.3 Added the Area Attribute for NE
The Area parameter is added in the NE properties. This parameter facilitates the
statistics gathering of stations and types of devices in each administrative central
office or specified physical address range during the coordination.
Prerequisite
Procedure
1. In the Logical Tree, right-click an NE and select Properties from the shortcut
menu to open the Properties dialog box.
Version: A 3-85
2. Type the central office to which the NE belongs in the Area textbox.
3. Click OK to complete the settings.
3.7.4 Added the NE Search Function in the NE IP Remote

Config Window
The NE search function is added in the NE Remote IP Configuration window, which

is convenient in the search for added NE stations in large-scale network.
Procedure
1. On the OTNM2000 main GUI, select ConfigurationNE IP Remote Config to

open the NE IP Remote Config window.
2. Select SystemText Filter to open the Text Filter dialog box.
3. Type the name of the NE to be searched. The NE IP Remote Config window

only displays the information of the matching NE, as shown below:
3-86 Version: A
4. With the buttons on the toolbar, you can complete the Set NE Remote IP,
Query Remote NE SN, Set Remote NE SN and Find Near NE by SN
operations.
3.8 Security Management
The following introduces the changes to the security management function.
3.8.1 Added the Scheduled Configuration Backup
You can set scheduled tasks of configuration data backup to guarantee the data
security in the OTNM2000.
Prerequisite
Procedure
1. Select ConfigurationBackup DCG File.
2. Add the task of backing up the DCG file.
1) In the Backup DCG File tab, click Add to open the Add dialog box.
Version: A 3-87
2) SeeTable 3-8 for setting related parameters of the DCG backup task and
then click Run.
Table 3-8 Description of DCG Backup Task Settings
Item Description
Task Name Indicates the name of the DCG backup task.
Task Enable Indicates the status of the task. The default status is Enable.
Indicates the type of the task, including Timing Run and Manual
Run. The default type is Time Run.
u Timing Run: Indicates the system will automatically run the
Task Type
task at the specified time.
Basic
u Manual Run: Indicates they system will immediately run the
Setting
task after its settings are completed.
The time settings are available only when Task Type is set to
Timing Run.
Task Time
Begin Time and End Time are optional, specifying the execution
Setting
time range of the task. Running Time is required, specifying the
running time of the task.
3-88 Version: A
Table 3-8 Description of DCG Backup Task Settings (Continued)
Item Description
The task period settings are available only when Task Type is set
to Timing Run.
Sets the task execution period, Day and Week.
Task Period u If Day is selected, specify the execution interval in the
Interval(Day) textbox.
u If Week is selected, specify the number in the EveryWeek
textbox.
3. In the Backup DCG File tab, view the added DCG file backup task.
4. Select the task already executed and click Task Result Files to open the File
Result List. Select the desired file, click Save As and specify the saving
directory. You can go to the saving directory to view the DCG file.
5. Select the corresponding task and click View Log to view the task logs.
Version: A 3-89
Other Operations
u Select the corresponding task, click Modify and modify the parameters in the
displayed dialog box according to Table 3-8. Then click Run.
u Select the corresponding task and click Delete. You can select to only delete
the task or delete both the task and the task execution result file.
3.9 Alarm Management
The following introduces the changes to the alarm management function.
3.9.1 Optimized the Alarm Statistical Template
After setting the alarm statistical templates as needed, you can view the template
settings and modify them according to the actual situation.
Procedure
1. Select AlarmAlarm Statistical Template from the main menu or select

Management ToolAlarm ManagementAlarm Statistical Template in the
Operational Tree to open the Alarm Statistical Template tab.
3-90 Version: A
Note:
The shortcut menu of the Alarm Statistical Template tab includes all the
functions of the following buttons.
2. Set an alarm template.
1) Select the corresponding network block, NE or subnet under the

Operational Tree.
2) Click Add to open the Add Custom Alarm Statistical Template dialog
box.
3) Set the related information and click OK.
Version: A 3-91
4) Click OK in the displayed alert box.
3. View or modify a template.
Note:
The templates in the Alarm Panel For Template status cannot be

modified.
1) Select the desired template and click Modify.
2) View or modify the template settings in the displayed Modify Custom

Alarm Statistical Template dialog box.
3) Click OK.
4) Click OK in the displayed alert box.
4. Delete a template.
3-92 Version: A
Note:
The templates in the Alarm Panel For Template status cannot be

modified.
1) Click Delete All and click OK in the displayed alert box.
2) Select the desired template, click Delete Select Row and click OK in the
5. Switch the statistical objects displayed on the alarm panel.
1) Click Alarm Panel For Project. The current alarm panel on the toolbar
displays all the alarms in the entire network.
2) Select the desired template and click Alarm Panel For Template. The
current alarm panel on the toolbar displays alarms according to the
template settings.
Other Operations
u Export custom alarm statistical templates.
Select the desired templates, right-click in any area of the Custom Alarm
Statistical Template tab and select Export File from the shortcut menu to
export the templates as a XML file to the specified directory.
u Import custom alarm statistical templates.
Right-click in any area of the Custom Alarm Statistical Template tab and
select Import from File from the shortcut menu to import the alarm statistical
templates previously backed up.
u Refresh custom alarm statistical templates.
Right-click in any area of the Custom Alarm Statistical Template tab and
select Refresh from the shortcut menu. The system reads the alarm statistical
templates from the database and displays them in the tab.
Version: A 3-93
3.9.2 Optimized the Alarm Filter
The optimized alarm filter function supports quick filter of the current alarm and
management of alarm filter rules.
Prerequisite
Procedure
1. Right-click an alarm entry in the Current Alarm tab and select Filter Alarm.
2. Select the filter range in the Current Alarm Quick Filtering and click OK.
3-94 Version: A
3. Select AlarmAlarm Filtering Rule Management to manage the alarm filter

rules.
3.9.3 Added the Physical Address Column in the Alarm List

Tab
The alarm list tab is added with an independent Physical Address Column,
displaying the physical area of the alarmed device. This helps locate the alarmed
device quickly in case that too many NEs and network blocks exists, improving
maintenance efficiency.
Note:
You can select to show or hide this column.
Procedure
1. In the Logical Tree, right-click an alarmed network block or NE and select

Current Alarm.
2. In the Current Alarm tab, right-click the column head and select Physical
Address from the shortcut menu to show the column, as shown below.
Version: A 3-95
3.9.4 Supporting Export of Alarm History Reports
This version supports one-off export of alarm history reports, convenient for
gathering statistics of and analyzing alarms during the device running so as to
understand the device running status and frequently occurred alarms.
Prerequisite
Procedure
1. Right-click an alarm entry in the Alarm History tab, select ExportAll to

export all alarm history. You can view the exported alarm history report in D:
\OTNM\md\task_result.
3-96 Version: A
3.9.5 Supporting Backup of Current Alarm Remarks
This version supports importing or exporting the remark information of current

alarms through the Dtbackup tool. This function facilitates the updating of remark
information of alarms, providing suggestions for failure processing.
3.10 Report Management
The following introduces the changes to the report management function.
3.10.1 Service Routing Information Statistics
This version supports gathering statistics of service routing information and

exporting the report as an XLS file. You can view the A / Z port, label, VLAN /
timeslot through the L2VPN service routing information report.
Version: A 3-97
Procedure
1. Select Business ManagementL2VPN Service. In the L2VPN dialog box,

set the filter condition and click Filter.
2. Right-click the L2VPN Service tab and select Service Routing Info Report to
save the current L2VPN service information as an XLS file.
3. Open the L2VPN service routing information report saved, and you can view
the A / Z port, label, VLAN / timeslot information of the circuit.
3.10.2 Long-term Traffic Monitor
The added long-term traffic monitoring function supports exporting long-term traffic
monitoring data into a report or image.
Prerequisite
Procedure
1. Set the long-term traffic monitoring task. Select PerformanceLong-term

traffic monitoring settings to open the Long-term traffic monitoring
settings tab. Then set the monitoring conditions, including monitored objects,
saving time period of monitored data and saving path of the long-term traffic
data.
3-98 Version: A
Note:
u After the above settings are completed, the system will obtain the
performance history data of the previous day from the database at 4
o'clock every morning according to the specified monitoring
conditions. Then it computes the daily, weekly and monthly data and
then saves the data into files.
u The file saving path cannot be modified once set. As modifying the
file saving path will cause loss of previous data, the Saving path
drop-down list will be greyed out after it is set.
2. View long-term traffic and export it into a report / image.
1) In the Card Description tab, right-click a port in the Port List textbox and
select View Long-term Receive Flow or View Long-term Send Flow.
2) View the long-term traffic monitoring data in the displayed window,

including 15-minute, daily, weekly and monthly traffic.
3) Export the traffic data as a report or image.
3.10.3 Device Version Statistics
You can gather statistics of the hardware version and software version of the device,
providing data support for project upgrading and maintenance.
Prerequisite
Procedure
1. Select ViewOperational Tree from the OTNM2000 main menu to open the
Operational Tree.
2. Select StatisticsNE Version View, select the desired device in the lower
pane and then click the button.
3. View the software version and NE type of the device in the right pane.
Version: A 3-99
Other Operations
You can sort, filter or export the version information in the result pane.
3-100 Version: A
4 Service Configuration and
Management
The following introduces the changes to the service configuration and management
functions.
Service Configuration and Management
Service Query
Added the Comparison of Card Service Configuration
Optimized the Query Mode of Fiber Information in the Multi-service Window
Cutover Management
Others
Version: A 4-1
4.1 Service Configuration and Management
The OTNM2000 has redefined the service configuration and management functions
and separated the service configuration from the maintenance function, greatly
improving configuration efficiency.
u The access method of service configuration and management is adjusted and

the function related to service configuration and management are displayed as
main menus.
4 Business Management: Views, maintains and backs up various services.
4 Service Configuration: Configures the services of various devices.
4 System: Configures system-related information, including the "Connect to

MSMP Service" function.
4 Statistics: Indicates the statistics and export functions of various service

data.
4 Log: Includes viewing service logs.
u The service data statistical icons are added in the toolbar, including:
4 Normal service object statistics
4 To-be-activated service object statistics
4 To-be-deleted service object statistics
4 Broken service object statistics
4.2 Service Query
The OTNM2000 separates the service query function from the service configuration.
You can view the service information through the service query window, modify the
services and monitor the alarm / performance.
Access Method
The service query menus are under the Business Management main menu.
4-2 Version: A
4 Service Configuration and Management
Service Query GUI
The OTNM2000 provides the service query GUI in unified style. For Tunnels, the
query GUI is as shown below:
1 Filter Condition Sets the filter condition to query services.

Area
2 Query Result Displays the results matching the condition. You can right-click a
Area service in the list and select corresponding menus from the shortcut
menu to perform related operations.
3 Service Details By selecting a service in the query result, you can view the detailed
Area information of the service and modify some service parameters. The
service details tab varies with different services.
4.2.1 Service Filter
The following takes the L2VPN service as an example to introduce how to filter
services. The procedure of filtering other services are similar and based on the
actual GUI.
Procedure
1. Select Business ManagementL2VPN Service in the main menu.
2. In the L2VPN Service Filter dialog box, set the filter condition and click Filter.
Version: A 4-3
3. View the tunnel list matching the filter condition.
Note:
The drop-down list in filter condition area displays the current filter
condition.
4-4 Version: A
Other Operations
You can perform the following operations through related tools in the filter condition
area.
Item Description
The drop-down list displays the current filter condition by default. Select
Filter Condition
the filter conditions from the drop-down list to quickly view the default
Drop-down List
circuit, the circuits created in last 7 days or 30 days.
Resets the filter conditions, setting the filter list or canceling the filter.
Refreshes the query result.
Sets the sorting condition to sort the query result.
Selects the column items to be listed in the query result.
Exports the query result into a TXT, HTML or XLS file.
Supports fuzzy query, that is, typing a keyword to query the contents.
4.2.2 Association Location
The association location function enables you to view the associated path and
attribute information of the selected service and supports quick redirection to the
data view of the associated path.
Procedure
1. In the service query result area, select the corresponding service and click
Relations/Properties tab in the service details area.
2. View the associated path and its attribute information of the selected service in
the Relations/Properties tab.
Version: A 4-5
3. Right-click the path associated with the selected service and select Open data
grid view.
4. View the information of the associated path in the displayed Business View
tab.
4.2.3 Signal Flow Direction Chart
The OTNM2000 graphically displays the specific routes of circuits and provides the
access methods of querying related NEs, channel alarms, performance and traffic in
the service topology GUI.
Procedure
1. In the service query result area, select the corresponding service and click
Service Topo tab in the service details area.
4-6 Version: A
2. View the service signal flow chart of the selected service in the Service Topo
tab.
4 In the signal flow direction chart, you can right-click an NE to navigate to

Logical Tree and query alarm and performance as well as configure the
NE.
4 By right-clicking a fiber connection in the signal flow direction chart, you

can query alarms / performance and monitor traffic.
4 The color of the NE icon displayed in the signal flow direction chart is
consistent with that in the main topology.
4 The fiber connection with the LOS alarm will turns red in the signal flow
direction chart, which is consistent with the main topology.
4.3 Added the Comparison of Card Service

Configuration
This version adds the function of comparing card service configuration, that is,
comparing the card configuration in the database and that generated by the current
NE before downloading the NE configuration.
Procedure
1. Right-click the corresponding circuit and select Download NE Cross-connect.
2. In the Download NE Cross-connect dialog box, click Compare Card Config.
Version: A 4-7
3. View the comparison result in the Compare Card Config column

corresponding to the NE.
4.4 Optimized the Query Mode of Fiber

Information in the Multi-service Window
The following introduces how to query the fiber information.
Note:
In the previous EMS versions, the system responds slowly when

querying the fiber-connection information in the topology and the result
displayed may cause incomplete display of the topology. In this version,
the mode for querying the fiber-connection information is optimized.
Procedure
1. Click the corresponding NE in the main topology or the multi-service topology

and press the Tab key to open the Link Information List dialog box, displaying
the fiber-connection information of the selected NE.
4-8 Version: A
2. Click OK to close the Link Information List dialog box.
4.5 Cutover Management
With the ever increasing expansion of the network, operators may frequently
confront the requirements for circuit cutover during project provisioning and network
maintaining. Therefore, the multi-service management platform introduced the
cutover management function, which provides systematical and general circuit
cutover solutions for service cutover scenarios commonly used for projects.
4.5.1 Function Description
The cutover management function provided by the multi-service management

platform includes cutover service management and broken service management.
Cutover Service Management
It supports replacing the port and specifying the policy for a single entry or multiple
entries of data. The cutover management can be divided into service migration and
service adjustment based on whether the start point and end point of the service
route change.
u Service Migration: In case of a source or sink NE change, you need to migrate

the services to other NEs.
Version: A 4-9
Figure 4-1 Service Migration Cutover Scenario Example
u Service Adjustment: modifying intermediate working / protection routing, adding

/ deleting protection and replacing UNI ports when the source or sink NE has
no changes.
Figure 4-2 Service Adjustment Cutover Scenario Example
4-10 Version: A
Broken Service Management
It repairs the broken services. During repairing a single or multiple services, it only
enumerates the broken ports of the selected objects, supports replacing of non-
broken ports and specifies the routing policy between specified NEs. The broken
service management can be divided into the following nine independent
management modules:
u Broken tunnel
u Broken PW
u Broken service data
u Broken MPLS ring
u Broken protection pair
u Broken OTN circuit
u Broken OTN ring
u Broken SDH/MSTP circuit
u Broken SDH/MSTP ring
4.5.2 Service Scenarios
In this release notes, only the various scenario models for cutover are introduced.
For detailed device application, card usage and operation procedures, see "e-Fim
OTNM2000 Element Management System Circuit Cutover Operation Guide".
4.5.2.1 Path Adjustment
Along with the development of service requirements, changes may be required to

the working or protection path and therefore you need to adjust the services or
protection paths. The scenarios for path adjustment are as follows:
Version: A 4-11
Scenario 1 Model
Figure 4-3 NNI Side Fiber Connection Adjustment (Working Path)
4-12 Version: A
Scenario 2 Model
Figure 4-4 NNI Side Fiber ConnectionAdjustment (Protection Path)
Version: A 4-13
Scenario 3 Model
Figure 4-5 Service Card Interface Adjustment (Same Card but Different Slots)
4-14 Version: A
4.5.2.2 Capacity Expansion
The capacity expansion function is used to add stations between existing links
according to the project requirement to expand the capacity of the network. The
scenario model for capacity expansion is as follows:
Figure 4-6 Capacity Expansion
4.5.2.3 Capacity Reduction
The capacity reduction function is used to remove the devices between two fibers
and merge the two fibers into one according to the project requirement to adjust and
optimize the network. The scenario model for capacity reduction is as follows:
Version: A 4-15
Figure 4-7 Capacity Reduction 1
4-16 Version: A
Figure 4-8 Deleting the Starting Node of the Branch Chain
4.5.2.4 Device Replacement
The device replacement function is used to update or upgrade the existing out-of-
date devices according to the project requirements to enlarge the service capability
of the devices so as to meet the ever increasing service requirements. The scenario
model for device replacement is as follows:
Version: A 4-17
Figure 4-9 Same-model Device Replacement (Station Changing)
4-18 Version: A
Figure 4-10 Replacing CiTRANS 660 with CiTRANS680V2 (CiTRANS 660 is connected to
CiTRANS680V2 through double fibers)
Version: A 4-19
Figure 4-11 Device Upgrade
4-20 Version: A
Figure 4-12 Replacing Immediate Nodes of MSPW
Version: A 4-21
Figure 4-13 PW Redundancy Protection
4.5.2.5 Network Adjustment
The network adjustment is used to restructure the links and ring networks according
the service development requirements to optimize the network capacity and network
mode. The scenario model for network adjustment is as follows:
4-22 Version: A
Figure 4-14 Changing Single-Connection to Double-Connection
Version: A 4-23
Figure 4-15 Upgrading the Ring to Improve the Ring Rate
4-24 Version: A
Figure 4-16 Changing the Large Ring into Small Ring
4.6 Others
The following introduces the changes to other functions of service configuration and
management.
4.6.1 PTN / IPRAN Service Configuration
The following introduces the feature changes to the PTN / IPRAN service
configuration functions.
u Supports multi-service operations by at least eight users.
Version: A 4-25
u Supports point-to-point service and reverse automatic creation of E1 CES

service.
u Supports service configuration status rollback, which makes it possible to roll

back the status of activated or partially activated paths after being deleted by
mistake, avoiding re-configuration.
u The subnet gives a prompt when the CIR exceeds the loopback line bandwidth.
u Supports manually adding entries in the NE configuration tab.
u Adjusts some routes to support manual selection of fiber connection.
u Simplifies the modifying procedure of the Wrapping_V3 ring network label.
u Adds the path increment import and export functions, which can be used to
configure paths in a batch manner, greatly improving the configuration
efficiency.
4.6.2 OTN Service Configuration
The following introduces the feature changes to the OTN service configuration
function.
4.6.2.1 OCH Configuration Optimization
The OCH configuration optimization includes the following:
u The default port rate is 10G, with the 1.25G disabled.
u Independent specifying of reverse routing.
u Adjusted layout of user attribute / path code and path name.
u Supports directly clicking "Finish" with the detailed routing information skipped
during the configuration.
u Optimized display of detailed routing information.
u Supports automatic creation of OCH in the entire network, improving creation

efficiency.
u Directly displays the wavelength in path parameters.
4-26 Version: A
4.6.2.2 ODUK Configuration Optimization
The ODUK configuration has the following optimization:
u The path attributes will be skipped by default and automatically completed.
u The service layer display is optimized when the ODUK is automatically created.
u In case of path pass-through, adding service layer OCH manually is not needed
for the source / sink station.
4.6.2.3 CLIENT Creation Optimization
The CLIENT creation has the following optimization:
u The service-layer circuits can be selected in a batch manner when selecting

service-layer circuits or creating multiple services.
u After selecting the service layer, you can complete it directly without viewing the
route information.
Version: A 4-27
5 Precautions for Upgrade to a New
Version
The following introduces the precautions for upgrade to a new version.
The OTNM2000 V2.0R5 (Build04.20.05.50) version is compatible with the earlier

versions. For upgrade to this version, see the release notes of the earlier version.
Version: A 5-1
Product Documentation Customer Satisfaction Survery
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.
Name
Phone Number
Email Address
Company
To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.
Documentation Name
Code and Version
Usage of the product documentation:

1. How often do you use the documentation?
Frequently Rarely Never Other (please specify)
2. When do you use the documentation?
in starting up a project in installing the product in daily maintenance in trouble
shooting Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
100% 80% 50% 0% Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
Satisfied Unsatisfied (your advice)
5. Which documentation form do you prefer?
Print edition Electronic edition Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
Very Somewhat Not at all (your advice)
2. How do you like the language style of the documentation?
Good Normal Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
Yes
No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
Yes
No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
Yes (Please give an example)
No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?
8. Which parts of the documentation are you unsatisfied with?Why?
9. What is your opinion on the Figures in the documentation?
Beautiful Unbeautiful (your advice)
Practical Unpractical (your advice)
10. What is your opinion on the layout of the documentation?

Beautiful Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:
Satisfied (please specify)
Unsatisfied (please specify)
12. Additional comments about our documentation or suggestions on how we can improve:
Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
edit@fiberhome.com

E-Fim OTNM2000 Element Management System Release Notes For Version V2.0R5 (Build04.20.05.50)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

E-Fim OTNM2000 Element Management System Release Notes For Version V2.0R5 (Build04.20.05.50)

Загружено:

Авторское право:

Доступные форматы

e-Fim OTNM2000

Element Management System

Release Notes for Version

FiberHome Telecommunication Technologies Co., Ltd.

We appreciate your business. Your satisfaction is our goal.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

All rights reserved

No part of this document (including the electronic version) may be

FiberHome e-Fim OTNM2000 Element Management

FiberHome e-Fim OTNM2100 Network Management

Important features or operation

Possible injury to persons or

Warning May cause severe bodily injuries.

Jump Jumps to another step.

Cascading menu Connects multi-level menu options.

Bidirectional service The service signal is bidirectional.

Unidirectional service The service signal is unidirectional.

1 New Features of This Version ......................................................................1-1

2 Overview of This Version .............................................................................2-1

2.1 Compatibility with Earlier Versions..................................................2-2

2.2 Northbound Interface Version.........................................................2-2

2.3 Device Version ..............................................................................2-3

3 Changes to Basic Functions.........................................................................3-1

3.1 Integrated Configuration Management ...........................................3-2

3.1.1 Modifying Project Attributes..............................................3-2

3.2 OTNM2000 GUI Optimization.......................................................3-36

3.3 Optimized Alarm Indicator Display................................................3-42

3.4 Layer-based Topology..................................................................3-44

3.4.1 Setting Topology Layers.................................................3-45

3.5 Authorization and Domain Division...............................................3-52

3.5.1 Basic Concepts..............................................................3-52

3.6 Network Management Tool...........................................................3-79

3.7 Configuration Management ..........................................................3-81

3.7.1 Batch Control Command................................................3-81

3.8 Security Management ..................................................................3-87

3.8.1 Added the Scheduled Configuration Backup...................3-87

3.9 Alarm Management .....................................................................3-90

3.9.1 Optimized the Alarm Statistical Template........................3-90

3.10 Report Management ....................................................................3-97

3.10.1 Service Routing Information Statistics ............................3-97

4 Service Configuration and Management.......................................................4-1

4.1 Service Configuration and Management.........................................4-2

4.2 Service Query................................................................................4-2

4.2.1 Service Filter ...................................................................4-3

4.3 Added the Comparison of Card Service Configuration ....................4-7

4.4 Optimized the Query Mode of Fiber Information in the Multi-service

4.5 Cutover Management ....................................................................4-9

4.6 Others .........................................................................................4-25

4.6.1 PTN / IPRAN Service Configuration ...............................4-25

5 Precautions for Upgrade to a New Version ...................................................5-1

Figure 4-1 Service Migration Cutover Scenario Example ...............................4-10

Table 2-1 List of Matching Cards ...................................................................2-3

The main features of this version include:

u Implements the integrated configuration, completing the configuration in

u Enlarges the OTNM2000 management capacity to 20 thousand physical NEs

u Further improves the management function of the OTNM2000, completing the

The new features of this version are described as follows:

The configuration management function manages the configuration information of

u Implements the integrated configuration function, which supports multiple users

u Synchronizes the configuration data to other clients in real-time with no

u Implements scheduled backup of device configuration data, enhancing data