Product Description For SDH: Optix Imanager T2000 V200R007C03

OptiX iManager T2000
V200R007C03
Product Description for SDH
Issue 01
Date 2009-06-30
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: [email protected]
Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

Product Description for SDH Contents
Contents
About This Document.....................................................................................................................1

1 System Overview.......................................................................................................................1-1
1.1 Network Position.............................................................................................................................................1-2
1.2 Product Characteristics....................................................................................................................................1-3
1.3 Manageable Equipment...................................................................................................................................1-3
2 New Features...............................................................................................................................2-1
2.1 What's New in T2000 V200R007C03.............................................................................................................2-2
2.2 Updates in the T2000 V200R007C03 for SDH Equipment............................................................................2-3
3 Features and Functions..............................................................................................................3-1

3.1 Topology Management...................................................................................................................................3-3
3.2 Communication Management.........................................................................................................................3-3
3.3 Alarm Management.........................................................................................................................................3-5
3.4 Configuration Management.............................................................................................................................3-8
3.4.1 SDH NE Management............................................................................................................................3-9
3.4.2 Network Management..........................................................................................................................3-16
3.4.3 ASON Management.............................................................................................................................3-20
3.4.4 Configuration Data Management.........................................................................................................3-28
3.4.5 Time Localization Management...........................................................................................................3-28
3.5 Performance Management.............................................................................................................................3-28
3.6 Security Management....................................................................................................................................3-30
3.7 Log Management...........................................................................................................................................3-32
3.8 Database Management..................................................................................................................................3-33
3.9 System Monitoring........................................................................................................................................3-33
3.10 Report Management....................................................................................................................................3-34
3.11 License Management...................................................................................................................................3-35
4 Networking and Application...................................................................................................4-1

4.1 Single Layer Management Network...............................................................................................................4-2
4.2 Hierarchical Management Network................................................................................................................4-2
4.2.1 Connecting Upper Level NMS through a LAN.....................................................................................4-3
4.2.2 Connecting Upper Level NMS through a WAN....................................................................................4-4
4.3 Remote Maintenance.......................................................................................................................................4-5
Issue 01 (2009-06-30) Huawei Proprietary and Confidential i

Contents Product Description for SDH
5 System Architecture...................................................................................................................5-1
5.1 Standard Client/Server Structure.....................................................................................................................5-2
5.1.1 Hardware Connection.............................................................................................................................5-2
5.1.2 Software Structure..................................................................................................................................5-3
5.1.3 Configuration Requirement....................................................................................................................5-6
5.2 Extended Structure of Multiple Servers........................................................................................................5-10
5.2.1 Hardware Connection...........................................................................................................................5-10
5.2.2 Software Structure................................................................................................................................5-11
5.2.3 Configuration Requirement..................................................................................................................5-14
5.3 HA System (Veritas Hot Standby)................................................................................................................5-18
5.3.3 Configuration Requirements................................................................................................................5-20
5.3.4 Principles of Switching........................................................................................................................5-21
5.4 HA System (Veritas Warm Standby) ...........................................................................................................5-22
5.4.3 Configuration Requirements................................................................................................................5-23
5.5 HA System (Huawei 1:N Cold Standby)......................................................................................................5-24
5.5.3 Configuration Requirement..................................................................................................................5-26
5.6 External Interfaces.........................................................................................................................................5-28
6 Reliability....................................................................................................................................6-1
6.1 HA System......................................................................................................................................................6-3
6.2 Distributed System..........................................................................................................................................6-3
6.3 DCN Protection...............................................................................................................................................6-4
6.4 Disk Mirroring.................................................................................................................................................6-5
6.5 Data Backup....................................................................................................................................................6-5
7 Technical Specifications...........................................................................................................7-1
7.1 Performance Indexes.......................................................................................................................................7-2
7.2 Management Capability..................................................................................................................................7-3
A Standards Followed ................................................................................................................A-1

B Glossary......................................................................................................................................B-1
C Acronyms and Abbreviations................................................................................................C-1
ii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description for SDH Figures
Figures
Figure 1-1 The position of the T2000 in TMN....................................................................................................1-2

Figure 4-1 Networking of single layer management network..............................................................................4-2
Figure 4-2 Networking of hierarchical management network.............................................................................4-3
Figure 4-3 Hierarchical networking structure realized through a LAN...............................................................4-4
Figure 4-4 Hierarchical networking structure realized through a WAN..............................................................4-5
Figure 4-5 Remote maintenance...........................................................................................................................4-6
Figure 5-1 Hardware connection- standard client/server structure......................................................................5-3
Figure 5-2 T2000 software structure....................................................................................................................5-4
Figure 5-3 Hardware connection-Extending multiple servers............................................................................5-11
Figure 5-4 T2000 software structure..................................................................................................................5-12
Figure 5-5 Hardware connection-HA system (Veritas hot standby)..................................................................5-19
Figure 5-6 Software structure-HA system (Veritas hot standby).......................................................................5-19
Figure 5-7 Software structure-HA system (Veritas warm standby)...................................................................5-22
Figure 5-8 Hardware connection - HA system (Huawei 1:N cold standby)......................................................5-25
Figure 5-9 Software structure - HA system (Huawei 1:N cold standby)...........................................................5-26
Figure 5-10 External communication interfaces of the T2000...........................................................................5-28
Figure 6-1 Networking of DCN management network........................................................................................6-4
Issue 01 (2009-06-30) Huawei Proprietary and Confidential iii

Product Description for SDH Tables
Tables
Table 1-1 Manageable SDH series equipment.....................................................................................................1-3

Table 1-2 Manageable MSTP series equipment...................................................................................................1-4
Table 1-3 Manageable OSN series equipment.....................................................................................................1-5
Table 2-1 New boards...........................................................................................................................................2-4
Table 5-1 Software modules and functions..........................................................................................................5-4
Table 5-2 Recommended hardware configurations for the server on Solaris......................................................5-6
Table 5-3 Recommended hardware configurations for the server on SUSE Linux.............................................5-6
Table 5-4 Software configurations for the server on Solaris................................................................................5-7
Table 5-5 Software configurations for the server on SUSE Linux.......................................................................5-7
Table 5-6 Recommended hardware configurations for the server on Windows..................................................5-7
Table 5-7 Software configurations for the server on Windows............................................................................5-8
Table 5-8 Recommended hardware configuration for the T2000 client...............................................................5-8
Table 5-9 Software configurations for the client..................................................................................................5-8
Table 5-10 Solaris Platform..................................................................................................................................5-9
Table 5-11 Solaris Platform..................................................................................................................................5-9
Table 5-12 Windows Platform.............................................................................................................................5-9
Table 5-13 Software modules and functions......................................................................................................5-12
Table 5-14 Recommended hardware configurations for the server on Solaris..................................................5-14
Table 5-15 Recommended hardware configurations for the server on SUSE Linux.........................................5-14
Table 5-16 Software configurations for the server on Solaris............................................................................5-15
Table 5-17 Software configurations for the server on SUSE Linux...................................................................5-15
Table 5-18 Recommended hardware configurations for the server on Windows..............................................5-15
Table 5-19 Software configurations for the server on Windows........................................................................5-16
Table 5-20 Recommended hardware configuration for the T2000 client...........................................................5-16
Table 5-21 Software configurations for the client..............................................................................................5-16
Table 5-22 Solaris Platform................................................................................................................................5-17
Table 5-24 Windows Platform...........................................................................................................................5-17
Table 5-25 Recommended hardware configurations for the server....................................................................5-20
Table 5-26 Software configurations for the server.............................................................................................5-20
Table 5-29 Recommended hardware configurations for the server....................................................................5-23
Issue 01 (2009-06-30) Huawei Proprietary and Confidential v

Tables Product Description for SDH

Table 5-33 Recommended hardware configurations for the primary site..........................................................5-26
Table 5-34 Recommended hardware configurations for the secondary site.......................................................5-26
Table 6-1 Reliability design................................................................................................................................. 6-1
Table 6-2 Bandwidth requirement........................................................................................................................6-4
Table 6-3 Data backup..........................................................................................................................................6-5
Table 7-1 Performance indexes............................................................................................................................7-2
Table 7-2 Management capability of different hardware platforms.....................................................................7-4
Table 7-3 Equivalent coefficient of various NEs................................................................................................. 7-5
vi Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description for SDH About This Document
About This Document
Purpose
The OptiX iManager T2000 Product Description for SDH describes the position, functional
characteristics, system architecture and networking mode of the T2000, appended with standards
that the T2000 complies with, and performance indexes.
This document provides guides for getting the features and functionalities of the T2000.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX iManager T2000 V200R007C03
Intended Audience
The intended audiences of this document are:
l Network Planning Engineer

l Data Configuration Engineer
l System Maintenance Engineer
Organization
This document consists of following chapters and is organized as follows.
Chapter Description
Chapter 1 System Overview This chapter describes the position and characteristics
of T2000 and its manageable equipment.
Chapter 2 New Features This chapter describes new features of this version.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential 1

About This Document Product Description for SDH
Chapter Description
Chapter 3 Features and This chapter describes main functions of this version.
Functions
Chapter 4 Networking and This chapter describes the networking structure for
Application T2000 interconnection with transmission network
equipment and other transmission NMS.
Chapter 5 System Architecture This chapter describes hardware structure, external

interfaces and configuration requirements for the
T2000.
Chapter 6 Reliability This chapter describes the recommended reliability

design schemes provided by the T2000.
Chapter 7 Technical This chapter describes the performance indexes and the
Specifications methods to evaluate management capabilities.
Appendix A Standards Followed This part lists the standards that the T2000 complies
with.
Appendix B Glossary This part lists the glossary used in the document.
Appendix C Acronyms and This part lists the abbreviations, acronyms and terms
Abbreviations used in the document.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
time.
NOTE Provides additional information to emphasize or

supplement important points of the main text.
2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 01 (2009-06-30) Based on Product Version V200R007C03

The updated contents are as follows.
Chapter 2 New Features
Descriptions of new features are updated.
Chapter 3 Features and Functions
Descriptions of features and functions are updated.
Chapter 7 Technical Specifications
Descriptions of performance indexes and management capability are updated.


Chapter 1 System Overview
Descriptions of product characteristics are added, and descriptions of manageable equipment

are updated.
Descriptions of features and functions are updated.

Chapter 1 System Overview
Descriptions of product characteristics are added, and descriptions of manageable equipment

are updated.
Descriptions of log management, database management, system monitoring, NE software

management and License management are added.
Chapter 5 System Architecture
Descriptions of the 1:N cold standby system are added, and descriptions of the HA system (Sun
Cluster) are deleted.
Chapter 6 Reliability
Descriptions of the 1:N cold standby system are added, and descriptions of the HA system (Sun
Cluster) are deleted.

Descriptions of supported new boards, and new features are updated.


Descriptions of supported new boards, new equipment, and new features are updated.


Chapter 7 Management Capability
This chapter is added to describe the management capability. This chapter describes the method
of calculating management capability of the T2000.

Product Description for SDH 1 System Overview
1 System Overview
About This Chapter
This topic describes the position of the T2000 in the telecommunication management network
(TMN) hierarchy, the product characteristics, and the manageable equipment of the T2000
V200R007C03.
1.1 Network Position

The OptiX iManager T2000 SNMS for Transmission Network (Sub-network Level) is produced
by Huawei Technologies Co., Ltd. (hereinafter referred to as Huawei). It provides solutions for
the transport network management.
1.2 Product Characteristics
This topic describes the main characteristics of the T2000.
1.3 Manageable Equipment
The T2000 can uniformly manage OptiX series optical transmission equipment from Huawei,
such as SDH, WDM, RTN, PTN and submarine line equipment.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential 1-1

1 System Overview Product Description for SDH
1.1 Network Position

The OptiX iManager T2000 SNMS for Transmission Network (Sub-network Level) is produced
by Huawei Technologies Co., Ltd. (hereinafter referred to as Huawei). It provides solutions for
the transport network management.
The T2000 is a subnetwork management system (SNMS). In the TMN architecture, SNMS is
located between the NE layer and network layer. The T2000 supports all functions of the NE
layer and some of the network layer management functions. Figure 1-1 shows the position of
the T2000 in the TMN architecture.
Figure 1-1 The position of the T2000 in TMN
Business Management Layer BMS
Service Management Layer SMS
Network Management Layer NMS
Subnetwork Management Layer

(iManager T2000)
SNMS
Element Management Layer EMS EMS
Network Element Layer GNE GNE GNE
NE NE ... NE NE NE NE
NE NE NE
BMS: Business Management System
SMS: Service Management System
NMS: Network Management System
SNMS: Subnetwork Management System
EMS: Element Management System
GNE: Gateway Network Element
NE: Network Element
NOTE
The T2100 is a network management system (NMS), and manages the subnetwork management system
(SNMS).
1-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

1.2 Product Characteristics

This topic describes the main characteristics of the T2000.
l Uniformly manage multiple types of equipment and services, including SDH, WDM, PTN,
RTN, submarine cable system, Ethernet, ATM, ASON, and SAN.
l Provide the Network Management System Maintenance Suite to complete the T2000
deployment and expansion, fault data collection, and northbound interface configuration.
l Deploy the processes of the NE management service, network service, and NBI service
independently.
l As a subnetwork management system (SNMS), provide all element management functions
and some network management functions.
l Support end-to-end trail management.
l Support both Windows, Solaris and SUSE Linux platforms, on which the same operations
are provided.
l Support distributed deployment.
l Support several open external interfaces, such as CORBA, SNMP, and MML.
l Provide Java-based graphical user interface, in a structure of "tree on the left and table on
the right".
l Provide powerful equipment search function, with which the user can search for and then
create NEs and fibers in batches.
l Provide complete alarm, configuration, performance and security (FCPS) management
functions.
l Support the IP, OSI and ECC communication protocols.
l Provide three high availability solutions, including Veritas hot standby, Veritas warm
standby, and 1:N cold standby.
l Provide several tools and methods for data backup and restoration , to ensure network data
security.
l Provide various reports and drawings.
1.3 Manageable Equipment

The T2000 can uniformly manage OptiX series optical transmission equipment from Huawei,
such as SDH, WDM, RTN, PTN and submarine line equipment.
Table 1-1, Table 1-2 and Table 1-3 lists the SDH equipment that the T2000 V200R007C03
manages.
Table 1-1 Manageable SDH series equipment
Equipment Name in the T2000
OptiX 155C SDH transmission unit for the OptiX 155C

access network

1 System Overview Product Description for SDH
OptiX 155S simplified STM-1 optical OptiX 155S

transmission system
OptiX 155/622B STM-1/STM-4 compatible OptiX 155/622B_I

optical transmission system (19-inch rack) OptiX 155/622B_II
OptiX 2500 STM-4/STM-16 compatible OptiX 2500

optical transmission system
OptiX 2500 REG STM-16 regenerator OptiX 2500 REG
Table 1-2 Manageable MSTP series equipment

OptiX Metro 100 terminal STM-1 optical OptiX Metro 100

transmission system
OptiX Metro 200 ultra compact STM-1 OptiX Metro 200

optical transmission system
OptiX Metro 500 ultra compact STM-1 OptiX Metro 500

multi-service transmission system
OptiX 155/622H(Metro1000) STM-1/STM-4 OptiX 155/622H (Metro 1000)

MSTP optical transmission system
OptiX 155/622H(Metro1000) STM-1/STM-4 OptiX Metro 1000V3

MSTP optical transmission system V3 series
OptiX Metro 1050 compact STM-1/STM-4 OptiX Metro 1050

multi-service optical transmission system
OptiX Metro 1100 compact container OptiX Metro 1100

STM-16 multi-service transmission system
OptiX 155/622(Metro2050) STM-1/STM-4 OptiX 155/622 (Metro 2050)

compatible optical transmission system
OptiX 2500+(Metro3000) STM-16 MADM/ OptiX 2500+ (Metro 3000)

MSTP optical transmission system
OptiX Metro 3100 STM-16 multi-service OptiX Metro 3100

transmission system
OptiX 10G(Metro5000)STM-64 MADM optical OptiX 10G (Metro 5000)

transmission system

Table 1-3 Manageable OSN series equipment

OptiX OSN 500 STM-1/STM-4 multi- OptiX OSN 500

service CPE optical transmission system
OptiX OSN 1500 intelligent optical OptiX OSN 1500

transmission system
OptiX OSN 2000 enhanced STM-1/STM-4 OptiX OSN 2000

multi-service optical transmission system

transmission system
OptiX OSN 2500 REG STM-16 regenerator OptiX OSN 2500 REG

transmission system

switching system

switching system

Product Description for SDH 2 New Features
2 New Features
About This Chapter
This section describes new features supported by the T2000 V200R007C03.
2.1 What's New in T2000 V200R007C03

This topic describes the new features of the basic network management function in the T2000
V200R007C03.
2.2 Updates in the T2000 V200R007C03 for SDH Equipment
This topic describes the new features of the SDH equipment in the T2000 V200R007C03.

2 New Features Product Description for SDH
2.1 What's New in T2000 V200R007C03

This topic describes the new features of the basic network management function in the T2000
V200R007C03.
T2000 Deployment
l The T2000 server supports the SUSE Linux + Sybase platform.
l The T2000 server supports the distributed deployment on the Solaris and SUSE Linux.
Specifically, the functions includes deleting and migrating instances from a slave server,
monitoring the NMS status of a slave server, starting and stopping the T2000 on the master
server and slave servers simultaneously.
l The T2000 client supports the Windows Vista.
l The T2000 supports the blade server that can run on SUSE Linux and Windows.
l The T2000 supports the installation of single servers on Solaris and SUSE Linux in a
distributed manner.
l The T2000 supports the installation of the HA system (Veritas hot standby) in a distributed
manner.
l The MSuite supports the fault analysis tool for the T2000.
l The MSuite supports the functions of downloading the dump files and downloading files
from the server.
l The MSuite client can be automatically upgraded by using the CAU tool.
Optimized T2000 Alarm

l The T2000 supports the ability to report service alarms according to trails.
l In the setting of filter conditions for alarms to be browsed, you can filter alarms by board,
port, and functional block.
Optimized T2000 Topology

l For the NE nodes on the Main Topology, icons are added to display the ASON status of
the NEs.
l The equipment can be searched, created and uploaded in a whole process, which can
simplify the process of finding equipment.
Optimized Network Function

Support the ability to query the protection subnet related to a topology object or an optical
interface alarm.
Other Changes
l Based on the original upgrade scheme, the T2000 supports a new upgrade scheme, to
achieve a quick version upgrade.
NOTE
The new upgrade scheme is only applicable to an upgrade from T2000 V200R007C01, T2000
V200R007C02 to T2000 V200R007C03 by the database upgrade mode.

Product Description for SDH 2 New Features
l The T2000 V200R006C01 and V200R006C03 can be directly upgraded to V200R007C03

by using the upgrade wizard.
l In the Veritas hot standby and warm standby schemes, the version of the Veritas software
is changed from 4.1 to 5.0.
l In the case of the HA system (Veritas hot or warm standby), the T2000 supports a quick
installation of the Solaris operating system and its patch, and the HA software.
l In the Veritas hot standby scheme, the VCS no longer directly monitors the NMS processes.
The VCS monitors only the NMSServer and NMSAgent processes. With the NMSServer
process, you can start and stop the T2000, and monitor the status of the T2000 server. With
the NMSAgent process, you can ensure that the T2000 is shut down during the automatic
switching triggered by a T2000 failure. The service processes of the T2000 are monitored
on the System Monitor.
NOTE
With the preceding changes, the only difference between the operations on the T2000 for single server
and HA system schemes is in the operations to start and stop the T2000. The other operations to start
and stop the service processes of the T2000 between the two schemes are the same.
l In the function of backing up the NMS information (include the deployment information
about the T2000 and the database of the T2000). After the backup operation, the backup
data is saved simultaneously in the backup directory on the client of the NMS maintenance
suite.
l In the function of restoring the NMS information (include the deployment information
about the T2000 and the database of the T2000). In addition, cross-operating system, cross-
scheme (HA scheme or single server scheme) restoration is supported. In this case,
however, only the deployment information about the T2000 can be restored. The data of
the database cannot be restored.
l The T2000 supports the ability to import and export script files by subnet.
l The networkwide maintenance status indicator is optimized. When the maintenance status
indicator is on, no query is performed before a specific status category is specified for query.
l The T2000 supports the ability to manage DC user login.
l The T2000 supports the ability to modify the NE ID on the T2000.
l The T2000 supports the ability to configure the equipment to automatically enable LCT
access rights after the communication between the equipment and T2000 stops.
2.2 Updates in the T2000 V200R007C03 for SDH Equipment

This topic describes the new features of the SDH equipment in the T2000 V200R007C03.
New Equipment
The T2000 V200R007C03 supports no new equipment.
New Boards
Table 2-1 lists the new boards supported in the T2000 V200R007C03.

2 New Features Product Description for SDH
Table 2-1 New boards
Equipment Board
OptiX OSN 1500 V100R009C03 SSR1PEFS8, SSQ1PEGS2, SSR1PEGS1,

SSR1PCXL
OptiX OSN 3500 V100R009C03 SSN1PSXCS, SSN1PEX1, SSN1PETF8,

SSN1PEG16
New Features
The T2000 V200R007C03 supports the following new features:
l New Features for OSN 1500, OSN 3500

– Supports the features of L2VPN.
– Supports the management of multiprotocol label switching (MPLS) tunnels.
– Supports OAM management for MPLS tunnels, OAM management for Ethernet
services and OAM management for Ethernet port.
– Supports the following QoS features: configuring the differentiated service (DiffServ)
domains, port policy, CAR policy, Port WRED Policy, V-UNI ingress policy, V-UNI
egress policy, PW policy, weighted random early detection (WRED) congestion and
discarding policy of services, QinQ policy, weighted fair queuing (WFQ) schedule
policy, and mapping between the CoS priority and the scheduling queue.
– Supports the control plane for configuring the static routes and address resolution.
– Supports the management of the Ethernet multi-service transmission platform (MSTP)
protocol and the Internet group management protocol (IGMP) Snooping.
– Supports the management of the Ethernet interface.
– Supports the automatic protection switching (APS) of MPLS tunnels.
– Supports the packet Ethernet services including E-Line service, E-LAN service, E-
AGGR service and clock service.
– Supports the management of inband DCN.
l New Features of SDH Network
– Supports the ability to manage SDH platinum services.
– Supports the ability to manage fiber/cable pipes.
– Supports the service alarm analysis function.
l Optimize the SDH ASON Features
– Supports the SDH UNI service management.
– Supports the ability to create associated SDH services of the same source and query the
synchronization status of associated SDH services of different source nodes.
– Supports the in-service migration between a diamond SDH ASON trail and a gold SDH
ASON trail.
– Supports the ability to query the timeslot segmentation of links.

Product Description for SDH 3 Features and Functions
3 Features and Functions
About This Chapter
The T2000 provides all management functions at the NE layer, and some of the management
functions at the network layer.
3.1 Topology Management

The topology management function is used to construct and manage the topology structure of
the entire network. You can know and monitor the networkwide running status in real time, by
viewing the network topology view. The T2000 supports creating a network topology view in
two ways including topology search and manual creation. You can also manage topology
elements.
3.2 Communication Management
The communication management function provides a communication channel for operation,
administration and maintenance (OAM) of the transport network. You can configure a DCN
between the T2000 and gateway NE, and a communication protocol between NEs.
3.3 Alarm Management
The alarm management function monitors faults and abnormal events generated during running
of the equipment in real time, and also provides alarm details and analysis measures. This helps
you locate and clear faults in a fast manner. The T2000 provides a powerful alarm management
function. You can customize alarm monitoring policies as required, and analyze and process the
alarms.
3.4 Configuration Management
Configuration management is the most basic function of the T2000. You can use this function
to perform physical configuration, service configuration, management configuration, service
distribution, and maintenance on NEs and networks.
3.5 Performance Management
The performance management function collects performance data of the equipment, functions,
services, or other objects periodically or after being triggered, to record the operation status,
health status, and quality of service (QoS) of a network. The T2000 provides a powerful
performance management function. You can customize performance monitoring policies as
required, and analyze and process the collected performance data.
3.6 Security Management
The security management function includes authentication, authorization, and access control, to
ensure that users can perform operations according to their respective authorities. TheT2000

3 Features and Functions Product Description for SDH
adopts an authority-based and domain-based security management policy, and a security

mechanism including access control and encrypted text transmission. This ensures the security
of the T2000 system and the transport network data.
3.7 Log Management
Log management includes the management of T2000 security logs, T2000 operation logs, and
NE security logs. The T2000 allows you to query and save logs periodically, to detect illegal
login, and operations, and analyze faults in a timely manner.
3.8 Database Management
Database management includes the management of NE and T2000 databases. To ensure data
security, you need to back up the database periodically.
3.9 System Monitoring
The T2000 provides the System Monitor. You use this tool to monitor the T2000.
3.10 Report Management
The T2000 has comprehensive reporting capabilities. The T2000 user is able to print desired
data while viewing them. The report in table format supports filtering by equipment type and
can be saved in Excel format.
3.11 License Management
The T2000 provides the license management function to help query license details, such as
authorization and usage.

3.1 Topology Management

The topology management function is used to construct and manage the topology structure of
the entire network. You can know and monitor the networkwide running status in real time, by
viewing the network topology view. The T2000 supports creating a network topology view in
two ways including topology search and manual creation. You can also manage topology
elements.
By using the T2000, a user can perform the following operations:
l Customize the topology view.

l Create NEs, virtual NEs, fibers/cables, virtual fibers/cables, NMs and subnets.
l Automatically search for NEs.
l Automatically search for fibers/cables and create fibers/cables.
l Set the naming rules for fibers/cables and trails.
l Manage fibers or cables.
– Create and delete fibers or cables.
– Filter fiber or cable information.
– View and print fiber or cable information.
– Create the intermediate office.
l Save views.
l Perform operations in views, such as search, zoom in, zoom out, zoom in on a specific area,
restore, drag, set display options, and view legends and their description.
l Configure the networkwide maintenance status. By clicking the Networkwide Maintenance
Status icon, users can know if the loopback, laser shutdown, alarm suppression, alarm
insertion, alarm reversion, and DCC enabling functions are configured. Users can also
change this configuration.
l Support the deletion of NEs in batches.
l Support the statistics and display of the number of equivalent NEs.
l The equipment can be searched, created and uploaded in a whole process, which can
simplify the process of finding equipment.
l The script function supports the export of subnet topology. And you can import the NEs in
the subnets that are on the topology.
3.2 Communication Management

The communication management function provides a communication channel for operation,
administration and maintenance (OAM) of the transport network. You can configure a DCN
between the T2000 and gateway NE, and a communication protocol between NEs.
Connectivity Test Between the T2000 Server and the NE

Check the communication status between the T2000 and NEs by "Ping" function.

NE Communication Parameter Settings

l Set the following NE communication parameters:

– IP address
– Extended ID of NE
– Gateway IP address
– Subnet mask of GNE
– NSAP address
– Connection mode
l Set extension embedded control channel (ECC) parameters of the Ethernet interface and
serial port.
l Manage ECC link: Query ECC link related to the NE.
l Access control
– Enable the T2000 to access NEs by using communication ports, such as the OAM, COM,
Ethernet ports, and serial ports.
– Set the access rate for serial ports.
l Change DCC access rate by selecting the bytes used by DCC channel. Bytes used in DCC
communication can be set: three bytes (D1-D3), nine bytes (D4-D12) or twelve bytes (D1-
D12). The corresponding access rates are: 192 kbit/s, 576 kbit/s, and 768 kbit/s.
l Set transparent transmission of DCC: When networked with other vendor's equipment, the
OptiX series equipment can transparently transmit the D bytes of other vendor's equipment
through the D1-D3 bytes, and communicate with the OptiX equipment through the D4-D12
bytes.
l DCC resources allocation: Query and set how D bytes are allocated and used.
l Inband DCN management: You can configure inband DCN to manage the equipment in a
network that contains only Ethernet services.
l Open systems interconnection (OSI) management: Contains parameter configuration of the
network layout and the route table.
l OSI tunnel management: You can configure OSI tunnels for those NEs at the edge of a
non-OSI network by OSI tunnel. In this way, the NMS for an OSI network is able to pass
through a non-OSI network to manage OSI NEs.
l IP stack protocol: Includes IP route management, OSPF parameter settings and proxy ARP.
The IP route management provides a table that stores the IP route relations between the NE
and other NEs in the network. You can query all the IP route information in this table.
l Enable OSI link: Enable the OSI protocol at the Ethernet port of an NE so that the data in
accordance with the OSI protocol can pass through the NE. In this way an OSI link is
enabled.
l Set the second network interface: Support the setting of the second network interface mode
and the LAN_LOC alarm reversion at the network interface.
l Support setting the communication mode of Ethernet interfaces on the NE.
l Support DCC transparent transmission through external clock interfaces.

DCN Protection Configuration

By using the T2000, you can perform the following operations:
l Set active and standby gateway NEs (GNEs) for an NE.

NOTE
A maximum of 3 GNEs can be set for an NE.
l Set the revertive mode.
l Set the types and addresses of the GNEs on the T2000.
l Test the communication states of NEs.
l Query in DCN management the number of non-gateway NEs connected to each GNE.
3.3 Alarm Management

The alarm management function monitors faults and abnormal events generated during running
of the equipment in real time, and also provides alarm details and analysis measures. This helps
you locate and clear faults in a fast manner. The T2000 provides a powerful alarm management
function. You can customize alarm monitoring policies as required, and analyze and process the
alarms.
Alarm Monitoring Policy Settings

l Set several alarm functions.

– Automatically acknowledge alarms.
– Automatically synchronize alarms.
– Analyze alarm correlation.
l Set the alarm correlation rules (the T2000 also provides some default rules). By setting
alarm correlation rules, the user can suppress non-root alarms that are caused by root alarms,
or change the severities of root and non-root alarms. Using this setting, the user can quickly
locate root alarms.
l Perform the alarm correlation analysis. The T2000 is able to analyze alarms according to
the alarm correlation rules. The alarm correlation analysis is categorized into dynamic and
static correlation analysis.
NOTE
l Dynamic alarm correlation analysis: You can suppress non-root alarms and adjust their severities.
l Static alarm correlation analysis: You can filter non-root alarms only, but not suppress these alarms
and adjust their severities.
l Set the alarm notification. When the T2000 receives alarms, it sends alarm details to the
user by mobile phone short messages or email, according to the user settings.
NOTE
Currently, short messages can be sent in the following three ways:
l The T2000 sends short messages through the E-TEK TD-8011 GSM MODEM.
l Using the DKU-5 cable, the T2000 sends short messages through NOKIA 6610 mobile phones.
l Using infrared ray, the T2000 sends short messages through NOKIA 6610 mobile phones.

l Customize the alarm attribute templates. A maximum of 16 attribute templates can be set
in addition to the default template.
l Set the filtering status of alarms.
l Set NE alarm attributes in a quick manner by using an alarm attribute template.
l Set other attributes of NE alarms, including:
– Saving mode
– Reversion mode
– Correlative suppressing switch (NE layer)
– Delay switch
– Alarm occurring hold-off time
– Alarm ending hold-off time
l Set the attributes of T2000 alarms, including:
– Alarm severity
– Filter status
l Set alarm severity and automatic reporting.
l Set the alarm suppression.
l Set the alarm reversion.
l Set the ATM connection alarm suppression.
l Set the AIS insertion switch.
l Set the UNEQ insertion switch.
l Set the bit error alarm threshold.
l Edit alarm remarks.
l Save alarm data by printing a report or exporting a text file.
l Support the alarm sound indication in the case of the client disconnection.
l Support selecting the type of lower order alarm monitoring on a board.
l Support querying the root alarm suppression pairs of the NE.
l Support setting the insertion mode when the board is not configured with services.
l Support the correctness check of data in the T2000 database and the reporting of system
database data fragment clearing alarm of the T2000.
l Support backing up history alarms to a flash card.
l Support clearing the audible and visual alarm indication of an NE cabinet permanently.
Alarm Browsing
l View the current alarms on the T2000, including NE and NM alarms.
l View the history alarms on the T2000, including NE and NM alarms.
l View abnormal events.
l Query current alarms from NE.
l Query history alarms from NE.

l Acknowledge alarms manually or automatically.

l Check alarms.
l View the information of current alarms and abnormal events by using the tool bar.
l View the information of alarms on the Alarm Panel.
l View the information of alarms on the topology.
l View alarm remarks.
l View the correlative alarms.
NOTE
The alarm that directly caused by the abnormal events or faults in the network is root alarm. A root alarm
always generate some other alarms of lower severity level. This brings confusions when you need to locate
and handle alarms. These alarms are correlative alarms.
l Support the display of the name of the used alarm template.
l The T2000 supports the ability to report service alarms according to trails.
Alarm Deletion
By using the T2000, a user can delete current NE alarms.
Alarm Synchronization
The T2000 can manually or automatically synchronize alarms between NEs and the T2000. By
using the T2000, a user can perform the following operations:
l Manually synchronize alarm information networkwide.
l Manually synchronize alarm information of NE(s).
l Manually synchronize the NM alarms.
l Automatically synchronize networkwide alarms under different conditions, such as at
startup and when the T2000 LCT user exits the T2000 LCT.
Alarm Statistics
You can use the T2000 to collect statistics on the number of alarms, average alarm
acknowledgement time, and average alarm clearing time.
l The supported statistical items include alarm severity, alarm type and alarm status.
l The supported statistical conditions include alarm name, alarm severity, acknowledgement
status, clearing status, alarm type, rising time, cleared time, and other conditions.
Alarm Dumping
By using the T2000, a user can save the history alarm data to a file automatically or manually.
The following items should be set for a manual dump: Conditions for an immediate dump
The following items should be set for an automatic dump:
l Conditions for an overflow dump
l Conditions for a periodical dump
l Dump location

Fault Diagnosis
The T2000 guides the user to diagnose and analyze alarms according to the preset diagnosis
rules until the fault source is located.
Before diagnosis, the diagnosis rules, and the alarms allowed to be diagnosed should be set. The
T2000 has default fault diagnosis rules. Users may add, delete or modify these rules as required.
Alarm Insertion
By using the T2000, a user can manually insert an alarm into a service to help users locate the
fault point.
Alarm Box Settings

l Set communication parameters for the alarm box
l Enable the audible-visual control.
l Mute alarm sound on the alarm box.
3.4 Configuration Management

Configuration management is the most basic function of the T2000. You can use this function
to perform physical configuration, service configuration, management configuration, service
distribution, and maintenance on NEs and networks.
3.4.1 SDH NE Management

NE management includes the configurations on attributes, communications, services, protection,
and clock on an individual NE basis. The configuration data is saved at the NE layer on the
T2000 and in the database of the NE.
3.4.2 Network Management
Network management refers to end-to-end management for every network, including the
configuration of protection subnets, trails and others. The objects of such management are
individual networks. Its configuration data can be built through the NE layer data on the T2000,
or configured directly at the network layer on the T2000, then send configuration data to all
relevant NEs. Compared with the NE layer configuration for individual NEs, the network layer
configuration is easier and faster.
3.4.3 ASON Management
Automatically switched optical network (ASON) is a new generation of optical network that
integrates the exchange and transport. After the user initiates a service request, the ASON selects
a route automatically, establishes and removes connections through the signaling control, and
performs network connections automatically and dynamically. An ASON NE refers to the
equipment that is equipped with both SDH and ASON features. An automatically switched
optical network (ASON) is managed by the T2000 that combines ASON and SDH features.
3.4.4 Configuration Data Management
Besides basic NE configuration functions, configuration data management also includes the
backup and restoration of the NE configuration data. This ensures the data security and
reliability.
3.4.5 Time Localization Management

Time localization ensures that the time on the T2000 is correctly displayed when the T2000
crosses time zones and daylight saving time (DST).
3.4.1 SDH NE Management

NE management includes the configurations on attributes, communications, services, protection,
and clock on an individual NE basis. The configuration data is saved at the NE layer on the
T2000 and in the database of the NE.
Basic NE Configuration
l Modify NE attributes such as:
– NE name
– NE ID
– NE Extended ID
– Remarks
– NE pre-configuration
NOTE
In the case of the NE whose ID needs to be set through the DIP switch, you can modify the NE ID
on the T2000.
l Synchronize NE time: Align all NEs with the system time of the T2000 server. The user
can configure the T2000 to automatically synchronize the NE time by specifying the
automatic synchronization period.
l Query physical resources in the following lists:
– NE list
– Board manufacturer information
– Board list
– Cabinet list
– Subrack list
– Equipment room list
l Support the board plug and display feature: After a board is inserted to the slot, the NE
Panel automatically displays the board and board information.
l Replace a board. The user can replace a board with a board of another type on the T2000.
– The user can replace board A with board B whose rate is the same as the rate of board
A and where the number of ports is the same as the number of ports on board A.
– The user can also replace board A with board B whose rate is lower than the rate of
board B and where the number of ports is less than the number of ports on board A.
l Automatically disable the NE functions: You can set to periodically disable some NE
functions that may affect services, such as loopback and automatic laser shutdown (ALS).
When the time expires, these operations automatically stop.
l Environment monitoring information. You can set the following items:
– PMU interface
– EMU interface

– CAU interface
– NE fan speed
l Virtual NE management
– Create a virtual NE.
– Add a board.
– Create fibers between the virtual NE and other NEs.
– Create SDH services.
– Create protection subnets.
– Search for and create trails on the virtual NE.
l Support the replacement of the boards.
l Supports the management of inband DCN.
Orderwire Configuration
l Set and query the orderwire phone numbers, call waiting time and orderwire phone port
availability.
l Set and query the networkwide conference call number.
l Set and query the subnet No. length and the related subnet of the optical interface.
l Set and query the SDH NNI connection for orderwire.
l Set and query the F1 data port.
l Set and query the broadcast data port.
Board Protection Configuration

l Configure board 1+1 protection.
l Configure 1:N tributary protection switching (TPS) protection on the tributary board.
l Configure board level protection.
l Configure port protection.
SDH Interface Configuration

l Interface board management: Query and set the SDH interface boards installed on NEs.
l Set the parameters of SDH interfaces.
l Set the parameters of PDH interfaces.
l Modify the optical/electrical attributes of the board port.
l Set overhead interfaces, including:
– Orderwire
– Hotline number
– Special line number
– Conference call number

– Subnet number length

– F1 data port
– Broadcast data port
– Communication port
– Data port
– Out-ring route
l Set the optical amplifier board interface.
l Manage the optical power of a board.
l Set tone and data access (TDA) interfaces, including:
– TDA clock source.
– TDA power feeding.
l Query and set the overhead including:
– Regenerator section overhead (J0).
– Lower order path overhead (V5, J2)
– VC4 higher order path overhead (J1, C2) and its pass-through or termination.
– VC3 higher order path overhead (J1, C2).
l Support PRBS.
l Support pre-alerts for the port optical power.
l Support setting and querying the TUG structure in the transmit and receive directions for
a board.
l Support lower order loopbacks for a board.
l Support querying the in service (IS) port status and the out of service (OOS) port status of
a line board or a data board.
l Support managing the power consumption.
l Support setting and querying the optical power threshold of a line board.
l Support the TCM function.
l Support the configuration of enabling the AIS insertion of the J0MM alarm.
Configuration for SDH Services and Protection

l Configure VC12, VC3, or VC4 services and select protection groups for them.
l Manage Transmux services, including M13/E13 Transmux and M13/E13 Transmux Server
services.
l Configure VC4-4C, VC4-8C, VC4-16C, or VC4-64C concatenated service; bind or unbind
services, and select protection groups for them.
l Configure other services: ESCON service, 64 kbit/s service (including TDA board service,
N x 64 kbit/s service) and DSL service.
l Manage SNCMP services.
l Activate or deactivate services.
l Support SNCP service management.

l Support SNCTP service management.

l Convert an SNCP service to a normal service or change a normal service to an SNCP
service.
l Support multiple MSPs configured at a single optical port. You can configure multiple MSP
rings by VC4 at an optical port to increase the utilization of the network resources.
l Configure REG. After the line board is set as REG on the T2000, each pair of optical
interfaces of the line board provides a special receive or transmit function. Through the
internal switch, the SDH signals from the receiving optical interface are sent out directly
to the corresponding transmitting optical interface after passing through the regenerator
section layer and being amplified. The REG function is completely realized by the board
without the need of system control and communication unit and cross-connect unit.
l Query the capacity of higher and lower order cross-connections on an NE.
l Support the ability to manage multiprotocol label switching (MPLS) for multi-service
transmission platform (MSTP) equipment. The MSTP equipment builds an label switched
path (LSP) with a PE router, identifies LSP labels and service priorities, and encapsulates
LSPs into virtual concatenation groups (VCGs) for transmission.
l The linear MSP supports the reconstruction protocol. The appointed MSP group can be set
as the reconstruction protocol.
l Support the ability to configure two 40G lower order cross-connect protection groups at
the same. You can adjust concatenated timeslots and optimize higher order pass-trough.
Configuration for ATM Interfaces, Services, and Protection

l Interface board management: Query and configure the ATM interface board on an NE.
l ATM bandwidth management: Query the bandwidth of ATM board.
l Set ATM interface parameters.
l Configure ATM traffic.
l Configure ATM cross-connection services.
– Create network to network interface (NNI) on the ATM processing board.
– Configure ATM cross-connections.
– Configure ATM protection groups.
– Configure ATM protection pairs.
– Configure ATM services from ATM board to SDH line.
– Activate or deactivate ATM cross-connection.
l Configure ATM binding path.
l Operate and maintain ATM (OAM).
– Set or query the section-end attribute of the connection point.
– Set or query the continuity check (CC) activation state of the connection point.
– Perform remote loopback test.
– Set or query the NE loopback location identifier (LLID).
– Upload, download, duplicate the OAM data of the NE or perform the related consistency
check.

l Configure the ATM IMA group.

l Supports the automatic protection switching (APS) of MPLS tunnels.
Configuration for Ethernet Interfaces and Services

l Interface board management: Query and configure the Ethernet interface board on an NE.
l Configure fast Ethernet transparent transmission board.
l Configure Ethernet internal interfaces, including:
– Basic attributes
– TAG attributes
– Network attributes
– Encapsulation/mapping
– Link capacity adjustment scheme (LCAS)
– Bound path
– Advanced attributes.
l Configure external ports of Ethernet interface, including:
– Basic attributes
– Flow control
– TAG attributes
– Network attributes
– Advanced attributes.
l Configure point-to-point LPT and point-to-multipoint LPT.
l Configure private line services, including Ethernet private line (EPL) and Ethernet virtual
private line (EVPL). You can create a new service and configure a bound path.
l Configure Ethernet private LAN (EPLAN) services. You can create a new virtual bridge
(VB) and configure the following: service mount, VLAN filtering, VLAN unicast, disable
MAC address, bound path, self-learning MAC address, VB port MAC address table
capacity, and VLAN MAC address table capacity.
l Configure Ethernet Layer-2 switching, including:
– Aging time
– Spanning tree
– IGMP snooping protocol.
l Configure QinQ service: QinQ is an embedded technology in VLAN, and tags users with
multi-layer VLAN ID, so that VLAN can be extended. You can perform operations such
as adding, stripping and exchanging of tags in different scenarios.
l Configure Ethernet link aggregation group (LAG), which contains intra-board LAG and
inter-board LAG.
– Create or delete an LAG.
– Add or delete LAG ports.
– Query LAG ports and aggregation state.
l Configure quality of service (QoS), including:

– Flow configuration
– CAR configuration
– CoS configuration
– Flow shaping management
– Port shaping management
– Configuring the differentiated service (DiffServ) domains
– Port policy
– CAR policy
– Port WRED Policy
– V-UNI ingress policy
– V-UNI egress policy
– PW policy
– Weighted random early detection (WRED) congestion and discarding policy of services
– QinQ policy
– Weighted fair queuing (WFQ) schedule policy
l Test frame receiving and transmitting on Ethernet boards, including the EGT, EFT, EGS,
EFS and EMS boards.
l Support the ability to query the opposite NE of the data services on these boards for the
Metro 1000V3.
l Configure OAM for Ethernet services.
l Configure OAM for Ethernet ports.
l Configure the LCAS attributes such as hold-off time, WTR time and protocol mode.
l Use QoS template to simplify the QoS configuration for Ethernet services.
l Support the automatic reporting of RMON performance of Ethernet boards.
l Support the dumping of history RMON performance of Ethernet boards.
l Support the automatic creation of OAM for Ethernet trails.
l Support the protocol diagnosis function.
l Support the configuration of IGMP static multicast table items.
l Support the standard LPT bearer mode.
l Support the setting of the LCAS alarm threshold.
l Support the alarm function in the case of no traffic at Ethernet ports.
l Support the Ethernet port mirroring.
l Support the unidirectional LPT function.
l Support setting and querying the MAC address of a data board.
l Support the LPT and port traffic statistics functions for a board.
l Support creating flows in batches for a board.
l Support the setting of the LPT restoration time and the point to multi-point LPT
management in the three scenarios of IP->VCTrunk(s), VCTrunk->IP(s), and VCTrunk(s)-
>VCTrunk(s) for a board.

l Support the ability to manage multiprotocol label switching (MPLS) for multi-service
transmission platform (MSTP) equipment. The MSTP equipment builds an label switched
path (LSP) with a PE router, identifies LSP labels and service priorities, and encapsulates
LSPs into virtual concatenation groups (VCGs) for transmission.
l Supports the management of the virtual Ethernet interface
l Supports the control plane for configuring the static routes and address resolution.
l Supports the packet Ethernet services including E-Line service, E-LAN service, E-AGGR
service and clock service.
RPR Management
l Modify resilient packet ring (RPR) node information.
l Set and query the node information of an NE in the RPR.
l Set the RPR link information of an NE.
l Query the topology of the RPR that the NE belongs to.
l Query the protection status, switching status and switching position of the RPR that an NE
belongs to.
l Set forced switch, manual switch or clear switch in the RPR that an NE belongs to.
Clock Configuration
l Query the clock synchronization status.
l Set clock source priority tables, including:
– System clock source priority list
– Priority table for phase-locked sources of 1st external clock output
– Priority table for phase-locked sources of 2nd external clock output
l Set clock source switching, including:
– Clock source restoration parameters
– Clock source switching condition
– Clock source switching
l Configure clock subnets, including:
– Clock subnet
– Clock quality
– Synchronization status message (SSM) output control
– Clock ID status
l Set phase-locked sources output by external clock, including:
– External clock output phase-locked source
– 2 Mbit/s phase-locked source external clock attributes
l Support the IEEE 1588 clock management. Configure the network that is based on
IEEE1588 protocol for the high precision time transmission.

l Support the reporting of the DST events of NEs.
Ethernet OAM Management

By using the T2000, a user can configure the 802.1 ag Ethernet OAM as follows:
l Create and configure maintenance nodes.
l Perform CC check.
l Perform LB check.
l Perform LT check.
l Perform Ping test.
l Perform Performance detect.
By using the T2000, a user can configure the 802.3 ah Ethernet OAM as follows:
l Query remote OAM parameters.
l Set link monitoring parameters. This function can help you to detect the events of frame
error, frame error period, and frame error seconds.
l Perform remote loopback.
Support reporting Ethernet OAM loopback events.

Supports OAM management for MPLS tunnels.
3.4.2 Network Management

Network management refers to end-to-end management for every network, including the
configuration of protection subnets, trails and others. The objects of such management are
individual networks. Its configuration data can be built through the NE layer data on the T2000,
or configured directly at the network layer on the T2000, then send configuration data to all
relevant NEs. Compared with the NE layer configuration for individual NEs, the network layer
configuration is easier and faster.
The license for the protection subnet and trail management function must be provided.
Protection Subnet Management

l Create protection subnets of different types.
– Linear multiplex section (MS) protection: 1+1 and M:N.
– Multiples section protection (MSP) ring: two-fiber bidirectional MS shared protection
ring, two-fiber unidirectional MS dedicated protection ring, and four-fiber bidirectional
MS shared protection ring.
– Path protection (PP) ring: two-fiber unidirectional PP ring and two-fiber bidirectional
PP ring.
– DNI protection.
– Non-protection (NP) ring and NP chain.
l Search for a protection subnet according to the information of NEs and fibers or cables in
the T2000, to form a complete protection subnet.
l Migrate an NP chain to a 1+1 linear MSP without interrupting services.

l Start or stop the MSP protocol of the MSP subnet, including enable or disable the MSP
protocols networkwide or the MSP protocol for a single node.
l For 1+1 MSP, the T2000 automatically generates the service of the protection channel
according to the service of the working channel.
l Adjust the bandwidth dynamically. You can dynamically adjust the MSP bandwidth
according to the service demands and how the network bandwidth is used currently to
improve the utilization of network bandwidth. For example, for an STM-16 MSP of an 8
x VC4 bandwidth, if the 6 x VC4 bandwidth is enough, then you can change the protection
bandwidth from 8 x VC4 to 6 x VC4 bandwidth and save 4 x VC4 for the use of non-MSP-
protected services.
l Expand the capacity of an MSP ring and a linear MSP chain. Expand the link capacity by
replacing the line boards on both sides of the link without interrupting active services. For
example, upgrade an STM-16 MSP ring to STM-64 smoothly.
l Modify the reversion mode, single-ended or dual-ended mode of linear MSP protection
without restarting the protocol.
l Expand and add nodes to multiple types of protection subnets, including MSP, SNCP, PP,
NP ring, NP chain and their combinations.
l Query the name, type and status of all protection subnets.
l Query and set the switching status, wait-to-restore (WTR) time and the trigger condition
of the protection subnet.
l Query all the isolated nodes and delete useless nodes.
l Set and view SDH NNIs.
l Query the relevant trail by protection subnet.
l Manage the entire RPR ring network. An RPR ring can be created, deleted, and searched.
RPR ring protection parameters and link parameters can also be managed. RPR ring
topology can be displayed through a view.
l Support the ability to count protection subnets, and display the rate levels of the protection
subnets.
l The two-fiber bidirectional MS SPRing and four-fiber bidirectional MS SPRing support
the transoceanic protocol.
l Support the ability to query the protection subnet related to a topology object or an optical
interface alarm.
Trail Management
l Create and maintain an SDH trail.
– Create an SDH trail, designate a timeslot, and select the protection priority strategy and
the resource usage strategy. The service level includes VC12, VC3, VC4, VC4 server
trail, VC4-4C, VC4-8C, VC4-16C and VC4-64C.
– Activate or deactivate, lock or unlock an SDH trail.
– Join or split, enable or disable VC4 server trails.
– During search of SDH trails, the T2000 retains the attributes of the existing ones as they
are.
– Upgrade an SDH trail to an ASON trail.
– Query the service status station by station according to SDH trails.

– Manage Optical power: Query input power, output power, and power thresholds for
SDH boards.
– Set and query the overhead bytes of all NEs on the trail, such as the trace byte.
– Prompt users to configure trace bytes when timeslot out-of-sequence occurs to the MS.
– Query the status of the low-order service.
– Set overhead pass-through or termination of all NEs on the trail.
– Insert alarms into the trails of MS and VC4 levels, such as AIS and RDI.
– Set loopback on any nodes of the trail, including VC4 loopback, tributary loopback,
optical interface loopback and cross-connection loopback.
– Perform pseudo-random binary sequence (PRBS) test on the trail.
– Modify the add/drop ports of the trail and the timeslot occupied by the trail in-service.
– Partially adjust the original route by changing the NE, board or timeslot the trail passes.
– Modify the route for concatenated services in-service.
– Set SNCP switching on the trail.
– Automatically generate dual-fed SDH services for 1+1 linear MSP.
– Copy an SDH trail for creating trails in batch.
– Manage discrete SDH services. Including query or analyze discrete services.
– Support the ability to analyze connectivity of an SDH trail.
– Support the ability to adjust the capacity of a link from STM-16 to STM-64 by using
the expansion wizard.
– Support ATM trails for the MSTP equipment.
– Support the ability to manage SDH platinum services.
– Support the ability to manage fiber/cable pipes.
– Support the ability to automatically refresh valid routes.
l Manage the alarms and performance events related to an SDH trail.
– Set alarm suppression or alarm reversion for a trail.
– Query current alarms, history alarms, current performance data, history performance
data, UAT and performance threshold-crossing records of an SDH trail.
– Set performance parameters of an SDH trail.
– Query the SDH trails and customer information affected by the alarm.
– Display the R_LOS alarms in the Transmission Media Layer Route view.
– Support the service alarm analysis function.
– Support the ability to set, on a per-trail basis, the alarm thresholds of the source or sink
end of the trail.
– Support the ability to set, on a per-trail basis, performance monitoring status and
automatic reporting of the source or sink end of the trail.
– Support the ability to query, on a per-trail basis, the performance events of the source
or sink end of the trail.
l Create and maintain an Ethernet trail.
– Create trunk links at VC12, VC3, VC4, VC4-4C, VC4-8C and VC4-16C levels.
– Create an unterminated trunk link.

– Create an Ethernet trail. The service includes EPL, EVPL, unterminated EPL, EPLAN,
EVPL based on QinQ, EVPL based on RPR and EVPLAN based on RPR.
NOTE
For release 4.0 NEs, the SDH NNI needs to be created on Ethernet line boards.
– Activate or deactivate an Ethernet trail.
– During search of Ethernet trails, the T2000 retains the attributes of the existing ones as
they are.
– Manage discrete Ethernet services. Including query or analyze discrete services.
l Manage the alarms and performance events related to an Ethernet trail.
– Query the Ethernet trails and customer information affected by the alarm.
– Query current alarms, history alarms of an Ethernet trail.
– Support the function of alarm affected ETH trails.
– Support the service alarm analysis function.
l Search for trails. According to the NE configuration data, at the NE layer, or the fiber
connection data, protection subnet information at the network layer, the T2000 generates
the network layer information about end-to-end trails, including SDH trails and Ethernet
trails.
l Automatically name trails.
l Filter trails in three ways.
– Filter all: filter all trails and only display the qualified trails in a network.
– Secondary filter: filter those trails that have been displayed in the interface according
to the filter conditions. This is secondary filter.
– Incremental filter: filter the newly added trails and display the new qualified trails
together with the currently displayed ones. This is incremental filter.
Networkwide Clock Management

l Configure the clock subnet.
l Provide the clock subnet view.
l Query the networkwide clock synchronization status.
l Search for the clock trace status.
l Output the clock tracing diagram.
l Enable or disable clock status change prompting.
Expansion Wizard
l Change board.
l Add extended subracks.
l Add nodes to a protection subnet.
l Delete a node for expansion.
l Upgrade link capacity.

3.4.3 ASON Management

Automatically switched optical network (ASON) is a new generation of optical network that
integrates the exchange and transport. After the user initiates a service request, the ASON selects
a route automatically, establishes and removes connections through the signaling control, and
performs network connections automatically and dynamically. An ASON NE refers to the
equipment that is equipped with both SDH and ASON features. An automatically switched
optical network (ASON) is managed by the T2000 that combines ASON and SDH features.
Topology Management
l Automatically discover ASON topologies and resources.
l Synchronize NEs in a domain: the T2000 can obtain the topology of the network through
the active NE.
l Automatically upload the configurations of NEs that have been created.
l Set the active and standby NEs.
l Synchronize cross-connections for NEs.
l Manage domains as follows:
– Create domains.
– Delete domains.
– Change the domain name.
l Query the enable status of the ASON NE software.
l Query the ASON NE software version.
l Search for ASON discrete signaling.
l Enable or disable the ASON feature of an ASON NE.
l Support SDH ASON clocks.
l Support managing node IDs on an ASON NE.
l Support managing the running status of the ASON software.
l The windows of SDH TE Link Management, Control Link Management, and ASON
Trail Management are changed to be selected from a drop-down list box that is located
in the Resource panel.
l Enable or disable the OVPN status of the NE.
TE Link Management
l Synchronize networkwide links by domain.
l Filter links by domain, source/sink information or OVPN customer.
l View TE links.
l Create virtual TE links.
l Delete virtual TE links.
l Create fibers.

l Set the distance for a TE link.

l Set the shared risk link group (SRLG) number.
l Create a link resource report.
l View bandwidth usage.
l View the alarm information about a link.
l View the alarm suppression information for a control plane alarm.
l Set alarm suppression for a control plane alarm.
l Partition resource of the selected TE link.
Component Link Management

l Synchronize networkwide component links.

l View component link information.
l Create component links.
l Delete component links.
l Set resources reservation.
l Query VC4 timeslot occupation status.
l Query Link Timeslot Segmentation.
ASON Trail Management

l Filter relevant ASON services by domain, name, original route, shared MESH restoration
trail, created time, planned time, OVPN customer, type, activation status, managed
identifier, class or whether original route is active.
l Synchronize networkwide ASON trails by domain or attributes.
l View ASON trails.
l Create an ASON server trail of the diamond, gold, silver, or copper class.
l Create an ASON trail of the diamond, gold, silver, copper or iron class.
l Create an ASON association trail of the silver or copper class.
l Query the synchronization status of associated services of different source nodes.
l Manage SDH UNI services.
l Set OVPN customer of an ASON trail.
l Duplicate ASON trails.
l Activate or deactivate ASON trails.
l Apply planning data to an ASON trail.
l Delete an ASON trail.
l Delete an ASON trail from NM.
l Synchronize ASON trails.

l Set routing attributes.

l Set revertive mode of the ASON trails.
l Set WTR time for rerouting ASON trails.
l Set scheduled revertive time of an ASON trail.
l Set the reversion lockout status of the ASON trails.
l Set the rerouting lockout status of the ASON trails.
l Enable or disable rerouting triggered by B3 bit error.
l Set priorities for rerouting ASON trails.
l Set the trigger condition for rerouting ASON trails.
l Set the crankback for the ASON trails.
l Set the policy for rerouting ASON trails.
l Set the rerouting hold-off time for the ASON trails.
l Set association source for ASON trails.
l Set association for ASON trails.
l Remove association for ASON trails.
l Downgrade an ASON trail to an SDH trail.
l Query related SDH trails for ASON trails.
l Migrate a ASON trail in-service.
l View details of an ASON trail.
l Set names for ASON trails in batches according to the naming rules.
l Revert an ASON trail to the original route.
l Optimize ASON trails.
l Switch the working or protection trail of a diamond trail manually.
l Revert ASON trails manually.
l Refresh the actual route of an ASON trail.
l Refresh the original route of an ASON trail.
l Set an actual route as an original route.
l Refresh the preset restoration trail for an ASON trail.
l Set the preset restoration trail for an ASON trail.
l Delete the preset restoration trail for an ASON trail.
l Refresh the shared MESH restoration trail for an ASON trail.
l Set the shared MESH restoration trail for an ASON trail.
l Delete the shared MESH restoration trail for an ASON trail.
l View the SNCP access service for an ASON trail.
l Query switching status of the SNCP access service.
l Switch between the access points of SNCP access service.
l Pre-calculate and adjust service trails.
l Query the rerouting reversion status of a revertive ASON trail.

l View the actual route of an ASON trail.

l View the original route of an ASON trail.
l View the associated route of an ASON trail.
l Refresh the associated route of an ASON trail.
l View the preset restoration trail or shared for an ASON trail.
l View the shared MESH restoration trail for ASON trails.
l View the alarms of an ASON trail.
l View the alarm suppression information for the selected ASON trail.
l Set alarm suppression for the selected ASON trail.
l View the performance events of the ASON trails.
l View the control plane performance of the ASON trails.
l View the control plane performance parameters of the ASON trails.
l Create the ASON trail report.
l Recover to original route in batch.
l Query the SLA conformity of ASON trails.
l Support the display of valid routes for gold services after the MSP switching.
l View the alarm suppression information for the selected ASON trail.
l Set alarm suppression for the selected ASON trail.
One-End Terminated ASON Server Trail Management

l Create and delete a one-end terminated ASON server trail.

l Activate and deactivate a one-end terminated ASON server trail.
l Associate one-end terminated ASON server trails.
l Create and delete the ASON-SDH trail that contains one-end terminated ASON server trail.
l Activate and deactivate the ASON-SDH trail that contains one-end terminated ASON
server trail.
l Search for the ASON-SDH trail that contains one-end terminated ASON server trail.
l Set association relations between the ASON trails that have different sources and sinks.
ASON Control Link Management

l Synchronize control links networkwide.

l Filter control links by domain, source/sink information.
l View control links.
l Customize whether to display the color of alarms in the Control Link Management
window.
l View the alarm information of the selected control link.

l View the alarm suppression information for the selected control link.
l Set the alarm suppression for the selected WDM ASON trail.
ASON Reserved Resource Management

l Query or set reserved resources station by station.

l Reserve resources for both ends of a component link.
VC4 Timeslot Occupation Status Management

l Query VC4 timeslot occupation status station by station.

l Query VC4 timeslot occupation status for both ends of a component link.
ASON Feature Management

l Enable and disable the ASON features of an NE.

l Query the ASON software running status.
l Query and set node IDs of NEs.
l Enable and disable the ASON features of a board.
Control Plane Parameters

l Set route computation strategy.

l Query route computation strategy parameters.
l Query route computation strategy parameters.
l Support the setting of rerouting delay time.
Link Management Protocol

l Query LMP control channels.

l Create LMP control channels.
l Delete LMP control channels.
l Query component links.
l Query LMP TE links.
l Query the LMP auto discovery types.
l Set the LMP auto discovery types.

Fiber Resource Threshold Management

l Query threshold for fiber resource.
l Set threshold for fiber resource.
OSPF Protocol Management

l Query open shortest path first (OSPF) control channels.
l Query whether OSPF is enabled.
l Query OSPF TE links.
l Query OSPF component links.
l Query OSPF IP addresses.
l Set OSPF IP addresses.
l Query the flood threshold for TE links.
l Set the flood threshold for TE links.
l Query OSPF protocol authentication.
l Set OSPF protocol authentication.
RSVP Protocol Management

l Query resource reservation protocol (RSVP) protocol authentication.
l Set RSVP protocol authentication.
l Delete RSVP protocol authentication.
Querying the ASON Trail Information on a Per-NE Basis

l Query ASON trails.
l Print ASON trail information.
ASON Trail Group Management

l Query an ASON trail group.
l Add an ASON trail group.
l Delete an ASON trail group.
l Query the members in an ASON trail group.
l Add a member to an ASON trail group.
l Delete a member to an ASON trail group.

ASON Control Plane Advanced Maintenance

l Maintain ASON signaling.

l Maintain the ASON switch controller.
l Maintain ASON protocol management.
l Maintain the ASON shared MESH switch controller.
l Manage inactive PPPoE out-band control link.
ASON Control Plane Alarm Suppression

l Query and set alarm suppression for an NE.

l Query and set alarm suppression for an ASON trail.
l Query and set alarm suppression for a TE link.
l Query and set alarm suppression for a control link.
l Query and set alarm suppression for a control channel.
ASON Control Plane Performance

l Query and set performance thresholds.

l Query and set the performance monitoring status.
l Query and set the automatic reporting status.
l Query and set the current performance events.
l Query and set the history performance events.
UNI Management
l Enable and disable the UNI feature.

l Manage an UNI interface.
l Manage the UNI access policy.
l Manage a GMPLS UNI link.
l Manage a transport network address (TNA).
Integration of SDH and ASON Trails

l Specify the included route for ASON services when creating an ASON-SDH trail. That is,
an ASON-SDH trail includes an SDH trail and an ASON trail.
l View SDH and ASON trails at the same time in SDH trail management.

l Manage overhead bytes, alarms and performance of a joint trail in a unified manner.
l Query related ASON trails from an SDH trail.
l Query related SDH trails from an ASON trail.
l Degrade an ASON trail to an SDH trail.
l Upgrade SDH services to ASON services.
l Set the revertive attributes when an SDH trail is being migrated to an ASON trail.
l Create dual fed and selectively received VC4 ASON server trails.
l Create lower order diamond trails.
l Calculate working and protection routes using the SPC First policy.
l The alarm in the ASON section of an ASON-SDH trail supports the alarm statistics
function.
l Support an SNCP access scheme.
– Set the SNCP access attributes of an ASON trail.
– Query the SNCP protection switching status of the ASON trail.
– Switch the SNCP access point of the ASON trail.
File Export or Import for Simulated Network Planning Information

l Export the TE link information.

l Export the associated ASON service information.
l Export the route calculation policy for ASON trails.
l Export the component link information.
l Export the ASON resource reservation information.
l Export the WTR time information for ASON trails.
l Export the preset restoration trails.
l Export route calculation policy for nodes.
l Export a networkwide configuration file.
l Export an NE configuration file.
l Export a network layer information file.
l Export an ASON information file.
l Import file scripts of the simulated planning information.
OVPN Management
l Divide resources based on VC4 granularity.

l Isolate static services from ASON services.
l Manage resources based on authority and domain.

ASON NE Catastrophe Restoration

The T2000 supports an ASON NE catastrophe restoration scheme.
PPPoE
The T2000 supports PPPoE out-band control link scheme.
3.4.4 Configuration Data Management

Besides basic NE configuration functions, configuration data management also includes the
backup and restoration of the NE configuration data. This ensures the data security and
reliability.
l Upload the configuration data of NE.

l Download the configuration data of NE.
l Copy configuration data of an NE to others.
l Automatically check the synchronization status between the T2000 and NEs.
l Check whether the configuration data in T2000 is consistent with that in NE.
l View the unsynchronized NE information.
l Synchronize NE data manually. In this way, the data in the T2000 is consistent with that
in the NE.
l Initialize configuration data in the T2000. The NE-layer data at the NM side is cleared and
the NE becomes unconfigured after the initialization.
l Back up NE data to the FDB0 and FDB1 databases in the SCC board.
l Back up the NE database manually or automatically to the CF card.
l Restore the NE database form the SCC board or the CF card.
3.4.5 Time Localization Management

Time localization ensures that the time on the T2000 is correctly displayed when the T2000
crosses time zones and daylight saving time (DST).
By using the T2000, a user can perform the following operations.
l Customize the display mode of the T2000 time.

l Set and query NE time zones.
l Enable or disable the daylight saving time for the NE.
3.5 Performance Management

The performance management function collects performance data of the equipment, functions,
services, or other objects periodically or after being triggered, to record the operation status,
health status, and quality of service (QoS) of a network. The T2000 provides a powerful
performance management function. You can customize performance monitoring policies as
required, and analyze and process the collected performance data.

Performance Monitoring Policy Settings

l Customize performance threshold template: You can customize a maximum of 16 threshold

templates in addition to the default template.
l Select the threshold template for NE and set the performance threshold.
l Set the performance threshold for a specified board.
l Set the start and stop time for NE performance monitoring.
l Set whether to prompt unavailable time (UAT) and threshold crossing events in a timely
manner.
l Set the start and stop time for Ethernet performance monitoring.
l Set Ethernet performance event monitoring status.
l Set the ATM performance monitoring time.
l Set the ATM performance monitoring period.
l Set the ATM performance event monitoring status.
l Set the ATM performance real-time monitoring.
l Support the setting of performance threshold based on ports or channels.
Performance Monitoring
l View the SDH current performance data, history performance data, UAT and threshold
crossing events.
l Monitor the ATM port performance in real time, and view ATM port history performance
data.
l Monitor the ATM VP and VC performance in real time, and view ATM VP and VC history
performance data.
l Monitor Ethernet port performance in real time, and view the Ethernet port history
performance data.
l View the Ethernet performance data in the form of a graph or a table.
l Monitor the Ethernet RMON performance.
l Support lower order performance management in the case of a board.
Performance Data Dumping

By using the T2000, you can save the performance data to a file automatically or manually.
The following item should be set for a manual dump: Conditions for an immediate dump
The following items should be set for an automatic dump:
l Conditions for an overflow dump

l Conditions for a periodical dump
l Dump location

Performance Data Analysis

l Analyze history performance data.
l Forecast long-term performances and medium-term performances. According to the history
performance data of the optical transceiver, create the empirical formula.
– If the performance data is available, the time (with deviation range) for generating this
performance can be calculated.
– If the time is available, the performance data at that time (with deviation range) can be
calculated.
Performance Register Resetting

l Reset the performance register on the board.
l Reset the performance register on the ATM board.
l Reset the performance register on the Ethernet board.
3.6 Security Management

The security management function includes authentication, authorization, and access control, to
ensure that users can perform operations according to their respective authorities. TheT2000
adopts an authority-based and domain-based security management policy, and a security
mechanism including access control and encrypted text transmission. This ensures the security
of the T2000 system and the transport network data.
Authentication Management
NM user authentication
l Log in to the T2000 with a legal user name and password.
l Enable the Access Control List (ACL) function by setting client access control conditions.
l Switch the login user.
l Switch between the single-user mode and the multi-user mode.
l Force a user to log out.
l Lock the terminal.
l Manage the remote maintenance user.
NE security management
l Manage NE users.
l Manage NE login.
l Manage DC users login.
l Lock NE login.
l Lock NE configuration.
l Set the LCT access control to determine whether the LCT is allowed to access an NE.

l Manage NE user groups.

l Query logged-in NE users.
l Force a certain NE user to log out.
l Set security parameters for NEs.
l Manage NE security log that contains the operation records of logging in to the NE, deleting
an NE user and forcing a user to exit.
NOTE
The NE Explorer supports all the security functions of a single NE. Users can perform operations
related to a single NE using the NE Explorer. The Main Menu in the Main Topology, however, allows
users to perform operations on multiple NEs.
The detailed functions of NE security management in the NE Explorer depend on the type of NEs.
l Manage the LCD password. If you forget the LCD password, you can change it using the
T2000.
NOTE
OptiX Metro 100 equipment supports the LCD control panel. You can use the control panel to set and
query parameters. Log in to the LCD control panel as an Admin or a Guest. Enter the password as Admin.
You can use the T2000 to set and change this password.
l Query all users of an NE.
l Configure the NE Syslog protocol.
l Perform NE security log auditing.
l Support NE basic ACL rule and advanced ACL rule.
l Support the encryption function of user name and password when the T2000 logs in to an
NE.
l Support the Warning Screen function of displaying messages during NE login.
l Support the change of NE user passwords in batches.
Authority Management
l Create operation sets to realize user authority grouping management.
l Create equipment sets to realize management object grouping management.
l Create user groups, and assign operation set and equipment set authorities to user groups.
l Create users and assign them to user groups. Set the access control switch for NM users,
and fine-tune NM user authorities.
l Query the operation authorities for the remote maintenance user.
l Configure the operation authorities for the remote maintenance user.
l Set the validity period for the remote maintenance user.
Network Security Management

l The security socket layer (SSL) protocol is supported in the communication between the
following:
– The T2000 and NMS/OSS connected by the CORBA interface.
– The T2000 client and server.
– The T2000 and NEs.

l Support encrypting the user name and password that are used to log in to an NE.
System Security Management

l Support the timeout mechanism for a user login session.
l Set the timeout value.
l Customize the password policy and account policy of the T2000 users.
l Monitor the operations performed by T2000 users.
l Send a text message to the logged-in T2000 users.
l After a user is logged in, the system locks out the client screen if the user does not perform
any operations in a specified duration.
l The system locks out a user if the user fails the login for three consecutive times.
l If a user is locked out, the user can be automatically unlocked, or manually unlocked by
the administrator.
l Sensitive information such as the password cannot be displayed in plain text, stored, or
transferred in plain text.
l Display a legal statement during the user login process.
l Support the lockout function for the system monitoring client.
3.7 Log Management

Log management includes the management of T2000 security logs, T2000 operation logs, and
NE security logs. The T2000 allows you to query and save logs periodically, to detect illegal
login, and operations, and analyze faults in a timely manner.
T2000 Security Log

l View T2000 security logs.
l Dump T2000 security logs.
– Dump T2000 security logs manually.
– Set log dumping when overflow or scheduled dumping.
l Forward T2000 security logs to the Syslog server.
T2000 Operation Log

l View T2000 Operation logs.
l Dump T2000 operation logs.
– Dump T2000 operation logs manually.
– Set log dumping when overflow or scheduled dumping.
l Forward T2000 operation logs to the Syslog server.
NE Security Log
l View NE security logs.
l Forward NE security logs to the Syslog server.

3.8 Database Management

Database management includes the management of NE and T2000 databases. To ensure data
security, you need to back up the database periodically.
NE Database Management
l Back up NE database to the SCC board.
l Back up the NE database manually or automatically to the CF card.
l Restore the NE database form the SCC board or the CF card.
l Back up NE database to a local server or a remote server.
– Start manually backup.
– Set periodical backup task.
l Restore NE database from a local server or a remote server.
T2000 Database Management

l Back up the T2000 database to a local server or a remote server.
– Start immediate backup.
– Set periodical backup task.
l Restore T2000 database from a local server or a remote server.
l Dump data in the T2000 database, including operation log, security log, alarm data, event
data, and various performance event.
– Start manually dump.
– Set overflow dump or periodical dump.
l Import or export script files: Export the configuration data in the T2000 to script files, or
import the configuration data to the T2000 from script files.
l Initialize the T2000 database.
l Configuration upgrade wizard: On the upgraded T2000 software, previous data can be
recovered with the help of the upgrade wizard.
l Customize scheduled tasks: Provide flexible customization of scheduled tasks to reduce
operation and maintenance costs. The scheduled tasks that the T2000 supports are backing
up the database, exporting the script files, collecting the performance data, loading software
package, and refreshing the ASON information.
l The T2000 information can be exported to an .XML or TXT file for the MDS 6600 to use.
l The T2000 can import the XML or TXT file that records the MDS 6600 data.
3.9 System Monitoring

The T2000 provides the System Monitor. You use this tool to monitor the T2000.
The T2000 provides the following functions.
l Monitor the process status on the T2000 server.

– Start and stop processes.

– Set start mode for the processes.
– View detailed information of the processes.
l Monitor the database status on the T2000 server.
l Monitor the system resource status on the T2000 server.
l Monitor the disk status on the T2000 server.
l View the installed component information.
l View operation logs on the System Monitor.
l Set the refreshing interval for the system monitoring information.
l Set the monitoring thresholds. When the CPU usage, memory usage, hard disk usage, or
database usage of the T2000 exceeds the alarm threshold, the System Monitor Server sends
an alarm to the T2000.
l Set sampling to collect the information on processes, databases, and system resources of
the T2000.
– Manual sampling.
– Set automatic sampling.
3.10 Report Management

The T2000 has comprehensive reporting capabilities. The T2000 user is able to print desired
data while viewing them. The report in table format supports filtering by equipment type and
can be saved in Excel format.
The T2000 provides the following reports:
l Clock tracing diagram

l Networking diagram
l Timeslot assignment diagram
l NE information report
l Physical location information report
l Equivalent NE statistics report
l Port resource report
l Board information report
l Board manufacturer information report
l Lower order cross-connection statistics report
l Fiber Cable Occupancy Resources
l SDH Trail Statistics Between NEs
l TU Port Resource Statistics
l Port Resource Statistics EPL
l Ethernet Inter-NE Service Resource Statistics
l SDH trail report, including single specifics, identical route combination, and end-to-end
combination.

3.11 License Management

The T2000 provides the license management function to help query license details, such as
authorization and usage.
l Perform a license validity check during T2000 user login. Prompt the T2000 users to use
a valid license the license is invalid or expired.
l View the authorization and utilization of a license, including the number of equipment and
clients, value-added functions, validity, and other information.
l Change a license by using the T2000 client without interrupting services.
l Support license management capability threshold-crossing alarms.

Product Description for SDH 4 Networking and Application
4 Networking and Application
About This Chapter
The T2000 provides users with single layer management network solutions for small and
medium transmission networks. Together with the upper level network management system
(through the standard external interfaces), the T2000 can assist the network layer management
system and the service layer management system in managing large transmission networks.
4.1 Single Layer Management Network

Single layer management network means that a transmission network is under the management
of a single layer network management system. That is, the entire management network only
includes NEs and EMSs (or SNMSs).
4.2 Hierarchical Management Network
Hierarchical management network means that the transmission network is managed through the
network management system with two or more layers. That is, the entire management network
contains three or more layers, such as NEs, EMSs (or SNMSs) and NMSs.
4.3 Remote Maintenance
Huawei provides the service of the IPSec VPN remote access. Thus, the network of the customer
can be accessed at any time and any place. This helps to provide powerful remote technical
supports.

4 Networking and Application Product Description for SDH
4.1 Single Layer Management Network

Single layer management network means that a transmission network is under the management
of a single layer network management system. That is, the entire management network only
includes NEs and EMSs (or SNMSs).
Figure 4-1 shows the networking mode.
NOTE
Single layer management network does not mean that there is only one network management system in
the entire network.
Figure 4-1 Networking of single layer management network
......
T2000 T2000
NOTE
For the internal networking mode of T2000, refer to 5 System Architecture.
4.2 Hierarchical Management Network

Hierarchical management network means that the transmission network is managed through the
network management system with two or more layers. That is, the entire management network
contains three or more layers, such as NEs, EMSs (or SNMSs) and NMSs.
The hierarchical management network has the following advantages:
l Increase of the network management capacity, and solution to the management problems
of large-scale networks
l Display of the status of the entire network through the integrated T2000
l Separated NE and network management functions, well suited to the operation and
maintenance mechanism of operators
Figure 4-2 shows the typical networking mode.

Figure 4-2 Networking of hierarchical management network
NMS/OSS
DCN
T2000 T2000
OSS: Operation Support System
DCN: Data Communication Network
4.2.1 Connecting Upper Level NMS through a LAN

If the T2000 server is near a network management system (NMS) server, the two servers can be
directly connected through a LAN.
4.2.2 Connecting Upper Level NMS through a WAN
The remote T2000 server can be directly connected to the NMS server through a WAN.
4.2.1 Connecting Upper Level NMS through a LAN

If the T2000 server is near a network management system (NMS) server, the two servers can be
directly connected through a LAN.
See Figure 4-3. The TCP/IP protocol must be used between the T2000 client and server and
between the T2000 server and the NMS server.

Figure 4-3 Hierarchical networking structure realized through a LAN
T2000 Client 1 T2000 Client N
...... NMS
T2000 Server
NOTE
When NMSs from many vendors access an upper level NMS at the same time, use a separate switch or
LAN at the T2000 client or server end, to avoid information interference of the NMSs from different
vendors.
4.2.2 Connecting Upper Level NMS through a WAN

The remote T2000 server can be directly connected to the NMS server through a WAN.
See Figure 4-4. The WAN can be any of the following:
l Digital data network (DDN)
l 2 Mbit/s private line
l Integrated services digital network (ISDN)
l Public switched telephone network (PSTN)
The TCP/IP protocol is recommended.

Figure 4-4 Hierarchical networking structure realized through a WAN
T2000 Client 1 T2000 Client N
......
NMS
DDN, 2M,
ISDN, PSTN
T2000 Server
NOTE
A minimum of 2 Mbit/s bandwidth must be available for the communication between the T2000 server
and the NMS server.
4.3 Remote Maintenance

Huawei provides the service of the IPSec VPN remote access. Thus, the network of the customer
can be accessed at any time and any place. This helps to provide powerful remote technical
supports.
After the VPN broadband connection is established between the network of Huawei and the
network of the customer, customer support engineers can log in to the T2000 server of the
customer by using the T2000 client in Huawei intranet and then maintain the equipment of the
customer remotely. Figure 4-5 shows the networking of the remote maintenance.

Figure 4-5 Remote maintenance
Remote maintenance terminal
Huawei
Intranet
Customer
Customer
T2000 server
Intranet
IPSec VPN connection
Transport
network

Product Description for SDH 5 System Architecture
5 System Architecture
About This Chapter
The T2000 provides multiple schemes according to user requirements.

l Standard client/server architecture
l Extended architecture of multiple servers
l High availability (HA) system architectures
5.1 Standard Client/Server Structure

The standard client/server structure is a standard system structure of the T2000. It refers to the
structure in which a T2000 server is accessed by multiple T2000 clients. This section describes
the software and hardware structure and configuration requirements of the standard client/server
structure.
5.2 Extended Structure of Multiple Servers
This section describes the software and hardware structure and configuration requirements of a
system with multiple servers.
5.3 HA System (Veritas Hot Standby)
The T2000 HA system (Veritas hot standby), a type of HA system provided by the T2000, applies
to the hot standby of a remote HA system.
5.4 HA System (Veritas Warm Standby)
The T2000 HA system (Veritas warm standby), a type of HA system provided by the T2000,
applies to the warm standby of a remote HA system.
5.5 HA System (Huawei 1:N Cold Standby)
The T2000 HA system (huawei 1:N cold standby) is a type of HA system that the T2000 provides
to realize HA system cold standby.
5.6 External Interfaces
This section describes interfaces for the communication between the T2000 and external
systems.

5 System Architecture Product Description for SDH
5.1 Standard Client/Server Structure

The standard client/server structure is a standard system structure of the T2000. It refers to the
structure in which a T2000 server is accessed by multiple T2000 clients. This section describes
the software and hardware structure and configuration requirements of the standard client/server
structure.
5.1.1 Hardware Connection
This section describes the hardware connection when the T2000 is installed in the standard client/
server mode.
5.1.2 Software Structure
The T2000 adopts an open software architecture and a modular structure.
5.1.3 Configuration Requirement
The software and hardware running environment required by the T2000 undergoes strict type
selection and test. Configure the T2000 computer according to the following requirements.

This section describes the hardware connection when the T2000 is installed in the standard client/
server mode.
The T2000 client and server can run on different computers in client/server structure. See Figure
5-1. The T2000 client and server can also run on the same computer, with each server capable
of accessing multiple clients. The server and client computers can be PCs or workstations. The
display of the T2000 screen on different operating systems is exactly the same.
NOTE
Client/server structure
The client/server structure refers to a structure where multiple terminals are connected with the server through
LAN or WAN. Users can operate on the clients, while a set of data saved on the server is shared networkwide.
The client of the T2000 implements the workstation function (WSF) of TMN for users to operate and manage
the transmission network.
The server of the T2000 implements the operating system function (OSF) of TMN, saving network data and
providing various management functions for the transmission network.
WSF and OSF
WSF is a concept related to the TMN architecture and enables conversion of the TMN information so that it can
be understood by users.
OSF is a concept related to the TMN architecture and enables the processing of telecom management
information, to monitor and control telecom functions (including the management function).

Figure 5-1 Hardware connection- standard client/server structure
T2000 Client 1
...... T2000 Client N
T2000 Server
A maximum of 100 clients can access one server and be operated on at the same time. The
number of clients accessed to one server is related to not only the authority assigned by license
but also the hardware of the server. For the maximum number of clients connected to different
servers, refer to Table 7-2.
NOTE
The recommended number of clients for configuration should not be more than five, and other clients
should be mainly used for monitoring, to lower the probability of operation conflict among multiple clients.
l For operations on a per-NE basis, when different clients operate on different NEs, the number of clients
that can operate at the same time depends on the number of clients defined in the license only. For
operations of monitoring and querying, such as alarm monitoring, the number of clients that can operate
at the same time depends on the number of clients defined in the license only, and the maximum possible
number is 100.
l For operations at the network level, such as trail searching, trail creation, configuration data uploading,
consistency check of configuration data, and networkwide alarm synchronization, when one client
operates, the operated network resource is locked and other clients cannot perform the same operation
at the same time. In this way, data consistency is ensured.

Figure 5-2 shows the architecture of the main modules. Table 5-1 briefly describes the name
and function of each main module.

Figure 5-2 T2000 software structure

T2000 Client
Sysmonitor Client
End-to-End Trail
Fault
Configuration
Performance
Security
Common
Servers
NMS/Other
MDP NBI Servers
Systems
Web Server
Sysmonitor Server
NEMgr Servers Domain NM ASON Servers

Servers
SDH NEMgr
NML ETH
RTN NEMgr SDH ASON
WDM NEMgr NML SDH Database
NGWDM NEMgr
NML OTN
Marine NEMgr
Ext NEMgr NML PTN WDM ASON
PTN NEMgr NML Common
T2000 Server
Transport Network
Table 5-1 Software modules and functions

Module Function
T2000 Client Client A Java-based graphical application that can run on

different platforms. Through the client, the user can
interact with the T2000 system to perform relevant
T2000 functions.

Module Function
T2000 MDP The message distribution process. Distributes all

Server messages between the T2000 server processes, as well
as between the T2000 server and client.
NEMgr Servers The NE management server that manages NEs in

different product scopes.
l SDH NEMgr manages all equipment in the SDH
product scope.
l RTN NEMgr manages the RTN series equipment.
l WDM NEMgr manages the Metro WDM and LH
WDM series equipment.
l NGWDM NEMgr manages the NG WDM series
equipment.
l PTN NEMgr manages the PTN series equipment.
l Marine NEMgr manages the submarine line
monitoring equipment.
l Ext NEMgr manages the OSN 900A and
OTU40000.
Domain NM The network management server that provides end-to-

Servers end management of different product scopes.
l NML Common provides the end-to-end common
management function.
l NML SDH provides the end-to-end SDH
l NML OTN provides the end-to-end OTN
l NML PTN provides the end-to-end PTN
l NML ETH provides the end-to-end Ethernet
ASON Servers The ASON feature server that provides the

management of SDH ASON and WDM ASON
features.
Common Servers The common server that provides common services to

non-specific product scope. The common server
programs include fault, performance, security,
topology, scheduled task, and so on.
Web Server Provides Web services, and works with the NE

management server to manage the NG WDM, RTN,
PTN and submarine line monitoring equipment.
NBI Servers The northbound interface server that provides the

interface management service between the T2000 and
an upper-layer NMS.

Module Function
System Sysmonitor Server Manages and monitors all T2000 server processes
Monitor except MDP.
Sysmonitor Client A simple GUI monitoring terminal based on Java.
NOTE
Deploy the NEMgr servers, domain NM servers, ASON servers, and NBI servers as required.T2000
provides the network management system maintenance suite to deploy network management systems.
The Database refers to the database management software adopted for the T2000. On Windows,
the database software is SQL Server. In SUSE Linux and Solaris, the database software is Sybase.
The T2000 manages transport network equipment through the Qx interface, and communicates
with the upper layer NMS through the MML, SNMP or CORBA interface. For the details about
external interfaces, refer to 5.6 External Interfaces.

Server
Table 5-2 Recommended hardware configurations for the server on Solaris
Reference Model Quantity
Sun Netra 240 1
Sun Fire V890 1
Sun SPARC Enterprise T5220 1
Sun SPARC Enterprise M4000 1
Sun Fire E4900 1
NOTE
In the preceding table, Quantity refers to the quantity of the required hardware when the T2000 adopts
the corresponding Reference Model.
Table 5-3 Recommended hardware configurations for the server on SUSE Linux
CPU Speed Memory Hard disk
2*Xeon quad 2.13G or above 16G or above 2*146G

Table 5-4 Software configurations for the server on Solaris

Description Quantity Remarks
SUN Solaris 10 (08/07), 1 Required

Multilingual Version
Database-Sybase Adaptive 1 Required

Server-12.5
Software package-OptiX 1 Required

iManager T2000-Solaris
network management system
software package
OptiX iManager T2000 1 Required

Server license component
Table 5-5 Software configurations for the server on SUSE Linux

SUSE Linux10 Enterprise 1 Required

Server 10 SP1

Server-12.5

iManager T2000-SUSE
Linux network management
system software package

NOTE
If the count of NEs managed by the T2000 is not less than 6,000 equivalent nodes, the OceanStor S3100
disk array should be configured for the primary and secondary nodes to enhance the management capability,
and also the installation disk of the OceanStor Manager Suite should be prepared for both nodes.
Table 5-6 Recommended hardware configurations for the server on Windows

IBM X3200M2 1
IBM X3500 1
IBM X3650 1
IBM X3850M2 1

Table 5-7 Software configurations for the server on Windows

Operation system-Windows 1 Required

Server 2003 R2 Standard
Edition
Database-MS SQL Server 1 Required

2000- Standard Edition

iManager T2000-Windows
software package

Client
Table 5-8 Recommended hardware configuration for the T2000 client

Platform Reference Model Quantity
Solaris Sun Ultra 45 1
Windows Dell Precision T7400 1
Desktop E2140 2G 80G or 1

Above
Table 5-9 Software configurations for the client

Platform Description Quantity Remarks
Solaris SUN Solaris 10 1 Required

(08/07), Multilingual
Version
OptiX iManager 1 Required

T2000-Solaris client
software
Windows Operation system- 1 Required. Choose

Windows XP (SP2/ either of the two
SP3) operating systems.
Operation system- 1
Windows Vista
Business (SP1)


T2000-Windows
client software
Compatibility
Table 5-10 Solaris Platform
Operation System Database Installation Upgrade

Software
Solaris 10 Sybase 12.5 Supported Supported
Operation Database Installation Upgrade Remarks

System Software
SUSE Linux Sybase 12.5 Supported Not supported Only the T2000
Enterprise server can run
Server 10 SP1 on this platform.
Table 5-12 Windows Platform

System Software
Windows SQL Server Supported Supported A maximum of

Server 2003 R2 2000 Standard 4 GB physical
Standard memory is
Edition SP2 supported.
Windows SQL Server Supported Supported The physical

Server 2003 R2 2000 Standard memory of more
Enterprise than 4 GB is
Windows SQL Server Not supported Supported A maximum of

Server 2003 2000 Standard 4 GB physical
Standard memory is
Windows SQL Server Not supported Supported The physical

Server 2003 2000 Standard memory of more


System Software
Windows XP SQL Server Supported Supported -

Professional 2000 Personal
SP2/SP3
Windows 2000 SQL Server 7.0 Not supported Supported -

Professional
SP4

Server SP4
Windows XP SQL Server 7.0 Not supported Supported -

Professional
SP2/SP3
Windows Vista - Not supported Not supported Only the T2000

Business SP1 client and
T2000 Web
LCT can run on
this platform.
5.2 Extended Structure of Multiple Servers

This section describes the software and hardware structure and configuration requirements of a
system with multiple servers.
This section describes the hardware connection when multiple T2000 servers are installed.

This section describes the hardware connection when multiple T2000 servers are installed.
When there are too many NEs to be managed by the standard client/server structure of the T2000,
more T2000 servers can be added for the management. See Figure 5-3.

Figure 5-3 Hardware connection-Extending multiple servers
......
T2000 Client 1 T2000 Client 2 T2000 Client N
T2000 Server 1 T2000 Server 2
The user can choose any client to log in to any server. The user can also query, configure, and
maintain the subnets managed by the server. By selecting the server to log in, the user has a
broad range in which to view and manage networks.
It should be noted that by using this method (logging in by using a single client), the user cannot
simultaneously log in to two or more servers to query or manage subnets managed by the servers.
Therefore, if the user needs to manage a network with a broad range, hierarchical network
management scheme should be used.

Figure 5-4 shows the architecture of the main modules. Table 5-13 briefly describes the name
and function of each main module.

Figure 5-4 T2000 software structure

T2000 Client
Sysmonitor Client
End-to-End Trail
Fault
Configuration
Performance
Security
Common
Servers
NMS/Other
MDP NBI Servers
Systems
Web Server
Sysmonitor Server
NEMgr Servers Domain NM ASON Servers

Servers
SDH NEMgr
NML ETH
RTN NEMgr SDH ASON
WDM NEMgr NML SDH Database
NGWDM NEMgr
NML OTN
Marine NEMgr
Ext NEMgr NML PTN WDM ASON
PTN NEMgr NML Common
T2000 Server
Transport Network
Table 5-13 Software modules and functions

Module Function
T2000 Client Client A Java-based graphical application that can run on

different platforms. Through the client, the user can
interact with the T2000 system to perform relevant
T2000 functions.

Module Function
T2000 MDP The message distribution process. Distributes all

Server messages between the T2000 server processes, as well
as between the T2000 server and client.
NEMgr Servers The NE management server that manages NEs in

different product scopes.
l SDH NEMgr manages all equipment in the SDH
product scope.
l RTN NEMgr manages the RTN series equipment.
l WDM NEMgr manages the Metro WDM and LH
WDM series equipment.
l NGWDM NEMgr manages the NG WDM series
equipment.
l PTN NEMgr manages the PTN series equipment.
l Marine NEMgr manages the submarine line
monitoring equipment.
l Ext NEMgr manages the OSN 900A and
OTU40000.
Domain NM The network management server that provides end-to-

Servers end management of different product scopes.
l NML Common provides the end-to-end common
l NML SDH provides the end-to-end SDH
l NML OTN provides the end-to-end OTN
l NML PTN provides the end-to-end PTN
l NML ETH provides the end-to-end Ethernet
ASON Servers The ASON feature server that provides the

management of SDH ASON and WDM ASON
features.
Common Servers The common server that provides common services to

non-specific product scope. The common server
programs include fault, performance, security,
topology, scheduled task, and so on.
Web Server Provides Web services, and works with the NE

management server to manage the NG WDM, RTN,
PTN and submarine line monitoring equipment.
NBI Servers The northbound interface server that provides the

interface management service between the T2000 and
an upper-layer NMS.

Module Function
System Sysmonitor Server Manages and monitors all T2000 server processes
Monitor except MDP.
Sysmonitor Client A simple GUI monitoring terminal based on Java.
NOTE
Deploy the NEMgr servers, domain NM servers, ASON servers, and NBI servers as required.T2000
provides the network management system maintenance suite to deploy network management systems.
The Database refers to the database management software adopted for the T2000. On Windows,
the database software is SQL Server. In SUSE Linux and Solaris, the database software is Sybase.
The T2000 manages transport network equipment through the Qx interface, and communicates
with the upper layer NMS through the MML, SNMP or CORBA interface. For the details about
external interfaces, refer to 5.6 External Interfaces.

Server
Table 5-14 Recommended hardware configurations for the server on Solaris
Sun Netra 240 1
Sun Fire V890 1
Sun Fire E4900 1
NOTE
In the preceding table, Quantity refers to the quantity of the required hardware when the T2000 adopts
the corresponding Reference Model.
Table 5-15 Recommended hardware configurations for the server on SUSE Linux
CPU Speed Memory Hard disk
2*Xeon quad 2.13G or above 16G or above 2*146G

Table 5-16 Software configurations for the server on Solaris

SUN Solaris 10 (08/07), 1 Required

Multilingual Version

Server-12.5

iManager T2000-Solaris
software package

Table 5-17 Software configurations for the server on SUSE Linux

SUSE Linux10 Enterprise 1 Required

Server 10 SP1

Server-12.5

iManager T2000-SUSE
Linux network management
system software package

NOTE
If the count of NEs managed by the T2000 is not less than 6,000 equivalent nodes, the OceanStor S3100
disk array should be configured for the primary and secondary nodes to enhance the management capability,
and also the installation disk of the OceanStor Manager Suite should be prepared for both nodes.
Table 5-18 Recommended hardware configurations for the server on Windows

IBM X3200M2 1
IBM X3500 1
IBM X3650 1
IBM X3850M2 1

Table 5-19 Software configurations for the server on Windows

Operation system-Windows 1 Required

Server 2003 R2 Standard
Edition
Database-MS SQL Server 1 Required

2000- Standard Edition

iManager T2000-Windows
software package

Client
Table 5-20 Recommended hardware configuration for the T2000 client

Platform Reference Model Quantity
Solaris Sun Ultra 45 1
Windows Dell Precision T7400 1
Desktop E2140 2G 80G or 1

Above
Table 5-21 Software configurations for the client

Solaris SUN Solaris 10 1 Required

(08/07), Multilingual
Version

T2000-Solaris client
software
Windows Operation system- 1 Required. Choose

Windows XP (SP2/ either of the two
SP3) operating systems.
Operation system- 1
Windows Vista
Business (SP1)


T2000-Windows
client software
Compatibility

Software

System Software
Table 5-24 Windows Platform

System Software
Windows SQL Server Supported Supported A maximum of

Server 2003 R2 2000 Standard 4 GB physical
Standard memory is
Windows SQL Server Supported Supported The physical

Server 2003 R2 2000 Standard memory of more
Windows SQL Server Not supported Supported A maximum of

Server 2003 2000 Standard 4 GB physical
Standard memory is
Windows SQL Server Not supported Supported The physical

Server 2003 2000 Standard memory of more


System Software
Windows XP SQL Server Supported Supported -

Professional 2000 Personal
SP2/SP3

Professional
SP4

Server SP4
Windows XP SQL Server 7.0 Not supported Supported -

Professional
SP2/SP3
Windows Vista - Not supported Not supported Only the T2000

Business SP1 client and
T2000 Web
LCT can run on
this platform.
5.3 HA System (Veritas Hot Standby)

The T2000 HA system (Veritas hot standby), a type of HA system provided by the T2000, applies
to the hot standby of a remote HA system.
This section describes the hardware connection of the T2000 HA system (Veritas hot standby).
This section describes the software structure of the T2000 HA system (Veritas hot standby).
5.3.3 Configuration Requirements
The software or hardware running environment of the HA system (Veritas hot standby) should
be strictly selected and tested. The following requirements must be met.
5.3.4 Principles of Switching
This section describes the principles of switching the T2000 HA system (Veritas hot standby).

This section describes the hardware connection of the T2000 HA system (Veritas hot standby).

Figure 5-5 Hardware connection-HA system (Veritas hot standby)

Primary Site Secondary Site
Ethernet Port Ethernet Port
Switch Router Router Switch
DCN
GNE
T2000 Client

This section describes the software structure of the T2000 HA system (Veritas hot standby).
The software architecture of the T2000 HA system (Veritas Hot Standby) is shown in Figure
5-6.
Figure 5-6 Software structure-HA system (Veritas hot standby)

Active Site Standby Site
T2000 Server T2000 Server
Sybase database Sybase database
GCO GCO
VCS VCS
VVR,VxVM VVR,VxVM
Solaris Solaris
T2000 Client T2000 Client
Java virtual machine ... ... Java virtual machine
Solaris/Windows Solaris/Windows
T2000 Client 1 T2000 Client n

GCO: Stands for VERITAS Global Cluster Option that is used for in-service monitoring of
system and application services. When the T2000 server program in the active node is
unavailable, the T2000 server program in the standby node is started immediately.
VVR: Stands for VERITAS Volume Replicator that is used to copy the T2000 data of the active
node to the standby node to synchronize data between the two nodes.
VCS: Stands for VERITAS Cluster Server that is used to monitor system and application services
in real time. When the hardware or software fails, the VCS restarts or closes the application
service.
VxVM: Stands for VERITAS Volume Manager that is used to manage the disk and the data
volume.

The software or hardware running environment of the HA system (Veritas hot standby) should
Server
Table 5-25 Recommended hardware configurations for the server
Sun Netra 240 2
Sun Fire V890 2
Table 5-26 Software configurations for the server
SUN Solaris 10 (08/07), Multilingual 2 Required

Version
Database-Sybase Adaptive Server-12.5 2 Required
Software package-OptiX iManager T2000- 2 Required

UNIX network management system software
package
iManager T2000 Server license component 2 Required
Tool software-Veritas-5.0 remote standby 2 Required

software (including VVR, VCS, GCO,
VxVM)

NOTE
If the count of NEs managed by the T2000 HA system (Veritas hot standby) is not less than 6,000 equivalent
nodes, the OceanStor S3100 disk array should be configured for the primary and secondary nodes to
enhance the management capability, and also the installation disk of the OceanStor Manager Suite should
be prepared for both nodes.
Client
Refer to the Table 5-20 and Table 5-21 in section "5.2.3 Configuration Requirement".
Compatibility

Software

System Software

This section describes the principles of switching the T2000 HA system (Veritas hot standby).
Normally, only the Sybase database application and T2000 application of the active workstation
are started, while those on the standby T2000 server are not. By using the VVR software,
unidirectional and real-time data replication at the memory device layer is realized between the
databases of the active and standby servers. That is, any data variation in the database of the
active server will be copied to the standby server in real time.
When the active server fails, VCS and GCO automatically start the Sybase database application
and the T2000 application on the standby server, and switch the active server to the standby one.
When the active server is restored to normal, VCS and GCO do not automatically start the Sybase
database application and the T2000 application on the active server. If you want to switch back
to the active server after the active server is restored to normal, you need to manually switch the
Sybase database application and the T2000 application from the standby server back to the active
server.

5.4 HA System (Veritas Warm Standby)

The T2000 HA system (Veritas warm standby), a type of HA system provided by the T2000,
applies to the warm standby of a remote HA system.
This section describes the software structure of the T2000 HA system (Veritas warm standby).
The software or hardware running environment of the HA system (Veritas warm standby) should
This section describes the principles of switching the T2000 HA system (Veritas warm standby).
It is the same as the hardware connection of the HA system (Veritas hot standby) .

This section describes the software structure of the T2000 HA system (Veritas warm standby).
The software architecture of the T2000 HA system (Veritas Warm Standby) is shown in Figure
5-7.
Figure 5-7 Software structure-HA system (Veritas warm standby)

VVR,VxVM VVR,VxVM
Solaris Solaris
Java virtual machine ... ... Java virtual machine
Solaris/Windows Solaris/Windows
T2000 Client 1 T2000 Client n
VVR: Stands for VERITAS Volume Replicator that is used to copy the T2000 data of the active
node to the standby node to synchronize data between the two nodes.


The software or hardware running environment of the HA system (Veritas warm standby) should
Server
Table 5-29 Recommended hardware configurations for the server

Sun Netra 240 2
Sun Fire V890 2

SUN Solaris 10 (08/07), Multilingual 2 Required

Version
Database- Sybase Adaptive Server-12.5 2 Required
Software package-OptiX iManager T2000- 2 Required

Solaris network management system
software package
iManager T2000 Server license component 2 Required
Tool software-Veritas-5.0 remote standby 2 Required

software (including VVR, VxVM)
NOTE
If the count of NEs managed by the T2000 HA system (Veritas warm standby) is not less than 6,000
equivalent nodes, the OceanStor S3100 disk array should be configured for the primary and secondary
nodes to enhance the management capability, and also the installation disk of the OceanStor Manager Suite
should be prepared for both nodes.
Client
Refer to the Table 5-20 and Table 5-21 in section "5.2.3 Configuration Requirement".

Compatibility

Software

System Software

This section describes the principles of switching the T2000 HA system (Veritas warm standby).
Normally, only the Sybase database application and T2000 application of the active workstation
are started, while those on the standby T2000 server are not. By using the VVR software,
unidirectional and real-time data replication at the memory device layer is realized between the
databases of the active and standby servers. That is, any data variation in the database of the
active server will be copied to the standby server in real time.
When the active server fails, the switch to the standby server has to be manually performed.
5.5 HA System (Huawei 1:N Cold Standby)

The T2000 HA system (huawei 1:N cold standby) is a type of HA system that the T2000 provides
to realize HA system cold standby.

This topic describes the hardware connection structure of the T2000 HA system (Huawei 1:N
cold standby).
This topic describes the software structure of the T2000 HA system (Huawei 1:N cold standby).
The software and hardware running environment required by the T2000 HA system (Huawei
1:N cold standby) undergoes strict type selection and test. Configure the T2000 HA system
according to the following requirements.
This topic describes the protection switching principles of the T2000 HA system (Huawei 1:N
cold standby).


This topic describes the hardware connection structure of the T2000 HA system (Huawei 1:N
cold standby).
Figure 5-8 Hardware connection - HA system (Huawei 1:N cold standby)
T2000 client
DCN
Gateway NE
Primary node1
T2000 client
T2000 server
DCN DCN Secondary node
Gateway NE
Primary node2
Disk Array
……
T2000 client
DCN
Gateway NE
Primary nodeN

This topic describes the software structure of the T2000 HA system (Huawei 1:N cold standby).
Figure 5-9 shows the software structure of the T2000 HA system (Huawei 1:N cold standby).

Figure 5-9 Software structure - HA system (Huawei 1:N cold standby)

Msuite Msuite
Scheduled backup Scheduled backup
Solaris Solaris

Msuite Client ... ... Java virtual machine
Java virtual machine Solaris/Windows
Solaris/Windows
T2000 Client n
T2000 Client 1

The software and hardware running environment required by the T2000 HA system (Huawei
1:N cold standby) undergoes strict type selection and test. Configure the T2000 HA system
according to the following requirements.
Server
Table 5-33 Recommended hardware configurations for the primary site
Sun SPARC Enterprise T5220 N
Sun SPARC Enterprise M4000 N
Table 5-34 Recommended hardware configurations for the secondary site

NOTE
The secondary site of Sun SPARC Enterprise T5220 or M4000 requires one OceanStor S3100 disak array.

SUN Solaris 10 (08/07), Multilingual N+1 Required

Version
Database-Sybase Adaptive Server-12.5 2N Required
Software package-iManager T2000-Solaris 2N Required

network management system software
package
Component-iManager T2000-server license 2N Required

component
T2000 Client
Refer to Table 5-20 and Table 5-21 in 5.2.3 Configuration Requirement.
Compatibility

Software

System Software

This topic describes the protection switching principles of the T2000 HA system (Huawei 1:N
cold standby).
Huawei 1:N cold standby logically divides a secondary site to N virtual computers to create
redundancy for multiple primary sites, by using the remote data backup function of the T2000
database management tool and the remote file synchronization function of the network

management system maintenance suite, in combination with the Zones function provided by the
Solaris 10 operating system. In this way, the standby function of Huawei 1:N cold standby is
achieved. On normal conditions, a primary site backs up the database to the secondary site by
using the T2000 management tool at the scheduled time. When you perform deployment
operations on the primary site, the network management system maintenance suite automatically
synchronizes files to the secondary site.
In the HA system (Huawei 1:N cold standby), data is not backed up in real time and switching
is also performed manually. When a fault occurs on a primary site, you need to manually switch
the primary site to the secondary site. On the secondary site, by using the T2000 database
management tool, you can restore database backup files to the databases of the secondary site
and start the T2000 of the secondary site. The HA system (Huawei 1:N cold standby) is in the
switching state at this time. In this case, other primary sites still allow backup of data and files,
but do not allow switching. When the faulty primary site restores, you need to immediately
switch the application back to the primary site. Hence, the secondary site provides the
redundancy service for the primary site normally.
If faults occur in two or more primary sites, you need to specify the primary site to switch
according to the priorities of services.
5.6 External Interfaces

This section describes interfaces for the communication between the T2000 and external
systems.
Figure 5-10 shows the communication interfaces between the T2000 and the external system.
Figure 5-10 External communication interfaces of the T2000
T2100
Other vendor's
MML NMS
CORBA/SNMP
T2000
Qx
Qx
The Qx interface uses the internal OptiX private management protocol of Huawei. It enables the
T2000 to connect the OptiX series equipment.

MML
The MML interface, one of the interfaces for NE-level NM and network-level NM, provides
functions such as information report, query and management of various operations. Based on
TCP/IP, MML interface takes the binary byte stream as the carrier, and the syntax format is the
unified command line format of Huawei. The MML interface provided by the T2000 is used to
connect with the T2100.
With least overhead, the MML interface is easy to use, but the disadvantage is that it is a supplier-
specific standard and not an industry standard.
The T2000 with a standard configuration provides MML interface for information report, query
and management of various operations.
CORBA
The CORBA interface is one of the universal standard interfaces in the telecommunication field.
Through the CORBA interface, the EMS and NMS of different manufacturers can be
interconnected to implement the management function.
TMF multi-technology network management (MTNM) defines the CORBA based interface
between NMS and EMS, and has been recognized by more and more equipment vendors.
The northbound CORBA interface provided by the T2000 is in compliance with the TMF513,
TMF608, and TMF814 recommendations.
SNMP
The simple network management protocol (SNMP) is one of the standard interfaces used in the
industry. Through the SNMP interface, the iManager T2000 can connect to the upper level
management system of the carrier or another vendor. The T2000 provides the alarm reporting
function.
The SNMP interface provided by the T2000 is compliant with the SNMP V1, V2 and V3
standards.

Product Description for SDH 6 Reliability
6 Reliability
About This Chapter
In reliability design, measures are taken to reduce potential risks, so that the product can operate
in a safer manner.
The T2000 may encounter some risks when applied in the network. Although the probability of
risks is very low, the following measures listed in Table 6-1 should be taken to ensure that the
system runs safely.
Table 6-1 Reliability design

Risk Solution of the T2000
Hardware Power failure of the T2000 Use UPS power supply.

failure computer
Communication failure with GNE Start DCN protection first.

(fiber and cable fault, and GNE
network interface fault)
Computer hard disk or CPU fault at Disk mirroring or HA system

the server
Software Database crash and network data Restore the T2000 data from the
failure loss backed up database.
The T2000 application software HA system

failure
6.1 HA System
The high availability (HA) system helps you improve the running reliability of the T2000 server.
6.2 Distributed System
A distributed system consists of the master server and slave servers, which compose a site to
implement the functions of the T2000 server.
6.3 DCN Protection

6 Reliability Product Description for SDH
You can use a DCN to connect the T2000 to a standby GNE. This improves the reliability of the
communication connection between the T2000 and equipment.
6.4 Disk Mirroring
The disk mirroring function helps you improve the reliability of disk data on the T2000 server.
6.5 Data Backup
The data backup function helps you improve the reliability of important T2000 data.

6.1 HA System
The high availability (HA) system helps you improve the running reliability of the T2000 server.
For better stability and risk resistance capability, the server uses a 1+1 or 1:N standby scheme.
If the active server fails, the T2000 can be switched to the standby server so that the T2000
application is not interrupted. Such a T2000 structure is called an HA system.
The protection mechanism of an HA system has two aspects:
l Database synchronization and backup between the active and standby servers
l Switching the application software between the active and standby servers
The HA system for the T2000 consists of the following schemes:
l HA system (Veritas hot standby): for remote hot standby, featuring automatic switching.
l HA system (Veritas warm standby): for remote warm standby, featuring manual switching.
l HA system (Huawei 1:N cold standby): for HA system cold standby, featuring manual
switching.
6.2 Distributed System

A distributed system consists of the master server and slave servers, which compose a site to
implement the functions of the T2000 server.
To lower the CPU usage and memory occupancy of the master server, the T2000 server can
adopt the distributed system structure. The master server is the core of a distributed system,
because the database server and the core subsystems of the T2000 are running on the master
server. The non-core subsystems of the T2000 are running on the slave server. In this way, the
CPU usage and the memory occupancy on the master server are lowered and the load is balanced
between the master server and slave servers.
The distributed system helps to improve the management capability of the T2000 server and is
mainly used in the following two scenarios.
l You can dynamically add blade servers to improve the management capability of the
T2000 server.
l By using the existing computers with lower configuration, you can create a distributed
system to manage a large-scale network.
The T2000 provides the following distributed system schemes:

l Distributed system (Solaris single server system): It is used for the distributed deployment
of the single server system that is installed on Solaris.
l Distributed system (SUSE Linux single server system): It is used for the distributed
deployment of the single server system that is installed on SUSE Linux and the blade server
is used.
l Distributed system (Veritas hot standby system): It is used for the distributed deployment
of the remote HA system (Veritas hot standby).

6.3 DCN Protection

You can use a DCN to connect the T2000 to a standby GNE. This improves the reliability of the
communication connection between the T2000 and equipment.
NEs communicate with the T2000 through the GNE. Active and standby GNEs can be preset
for every NE on the T2000. When communication between the active GNE and the T2000 fails,
the T2000 automatically switches to communicate with the standby GNE to ensure that the
communication between the NE and the T2000 is not interrupted. When communication is
restored, whether the active GNE is used again is determined according to the restoration mode
preset.
Figure 6-1 shows the networking of DCN protection.
Figure 6-1 Networking of DCN management network

T2000
Primary GNE Standby GNE
DCN
The T2000 communicates with the standby GNE through internal communication in the
transmission network, or through other DCNs. For example, 2 Mbit/s private line, digital data
network (DDN) private line, ISDN, PSTN, or Ethernet.
NOTE
l The recommended number of non-gateway NEs (including non-gateway NEs that connects to the GNE
by using the extended ECC) that connect to each GNE is fewer than 50. Once the limit is exceeded,
the number of GNEs should be increased.
l Each T2000 supports a maximum of 2000 GNEs. Once the limit is exceeded, the number of GNEs
should be decreased.
Table 6-2 describes the bandwidth required for the T2000 system and equipment management.
Table 6-2 Bandwidth requirement
Item Bandwidth Requirement
Bandwidth required for the communication 2 Mbit/s

between the T2000 client and server

Item Bandwidth Requirement
Bandwidth required for the communication 2 Mbit/s

between a GNE and the T2000 server NOTE
In a certain networking, the 2 Mbit/s bandwidth
may not satisfy the actual bandwidth requirement.
In this case, determine the required bandwidth
using the formula "N x 192 kbit/s + 192 kbit/s x
120%", in which the letter N refers to the number
of NEs that are directly connected to the GNE
through fibers.
Bandwidth required for data synchronization A minimum of 2 Mbit/s is required.

between active and standby Veritas sites
Bandwidth required for data synchronization A minimum of 512 kbit/s is required.

between primary and secondary 1:N sites
6.4 Disk Mirroring

The disk mirroring function helps you improve the reliability of disk data on the T2000 server.
If the server is a Sun workstation with more than two hard disks, disk mirroring can be installed
together with the T2000. The T2000 uses Sun's Solaris Volume Manager software to provide
the disk mirroring scheme. Any change in data can be updated to two disks simultaneously.
Solaris Volume Manager automatically monitors the running status of the disks. If the working
disk fails, the T2000 is switched to the protection disk using a command, to ensure data storage.
Then, replace the faulty working disk, and perform the re-mirroring of the working disk.
6.5 Data Backup

The data backup function helps you improve the reliability of important T2000 data.
The security of network data is a concern for users. The T2000 provides the following solutions
shown in Table 6-3.
Table 6-3 Data backup

Data to be backed Solution of the T2000 Operation
up description
Alarm log, abnormal Dump logs. Operate on the

event log, performance T2000 client. For
log, operation log more detailed
operations, please
refer to the T2000
online help.

Data to be backed Solution of the T2000 Operation

up description
Configuration data Export them to scripts, adopting the MML

command format. The scripts can neglect the
structural differences among databases of all
the T2000 versions, and are suitable for data
backup in the case of version upgrade. The
scripts supported by the T2000 consist of
networkwide configuration files, NE port
naming files, NE configuration file, NE list
files, NM computer information files, service
actualization scripts, network layer
information files and network modeling and
design information files.
Database Back up all data in T2000 database or back

up the T2000 MO data.
NE database To back up the NE database, back up NE data

to the FDB0 and FDB1 databases.

Product Description for SDH 7 Technical Specifications
7 Technical Specifications
About This Chapter
This section describes the technical specifications of the T2000, including performance indexes
and management capability.
7.1 Performance Indexes

This section describes the performance indexes of the T2000.
7.2 Management Capability
The management capability of the T2000, on the basis of satisfying the prescribed performance
indexes, can be measured by the maximum number of NEs it manages.

7 Technical Specifications Product Description for SDH
7.1 Performance Indexes

This section describes the performance indexes of the T2000.
Table 7-1 Performance indexes

Item Sub-item Index
Storage Current alarms capacity Maximum: 50,000 pieces

capacity
History alarms capacity Maximum: 2,000,000 pieces
Event capacity Maximum: 120,000 pieces
Performance event capacity Maximum: 300,000 pieces
Operation log capacity Maximum: 300,000 pieces
Security log capacity Maximum: 300,000 pieces
Resources CPU used rate Normally, not more than 10% of the CPU is
occupied used.
Processing Response speed of alarm Normally, the time interval from the
capacity handling generation of an alarm on the equipment until
it is displayed on the T2000 is not more than
10 seconds.
Response speed of Normally, for 1,000 pieces of performance

performance handling data, the time interval from being reported
until the time it is stored in the T2000 is about
10 seconds.
Alarm handing capacity Normally, 100 (not more than 400 at most)
pieces of alarms can be handled per second.
Time taken to configure a Generally, it takes not more than 20 seconds

trail to configure or delete a trail.
Time taken to search for a Generally, it takes not more than 20 seconds
trail to search for a trail.
Manageable Users Maximum: 2000

T2000 users
User groups Maximum: 255
Equipment sets Maximum: 255
Operation sets Maximum: 255
Switch time Time of local active or <15min

standby server switching
Time of remote active or <15min

standby server switching

Item Sub-item Index
Time of DCN protection When an error of the NE communication

switching occurs, it takes three minutes for the T2000
to detect that the NE is unreachable. When the
T2000 detect that the active gateway NE is
unreachable, it takes no more than ten
seconds to complete the DCN protection
switching.
Stability MTBF The MTBF is more than 6 months. (Failure is

when the database crashes.)
MTTR The MTTR is not more than 15 minutes.

(Failure is when the database crashes.)
OSI over Number of manageable L1 Maximum: 32

DCC domains
networking
capability Number of manageable NEs Maximum: 64
in a L1 domain
Number of manageable NEs Maximum: 64

in a L2 domain
HWECC/IP Number of manageable Not more than 2000

over DCC GNEs
networking
capacity Number of manageable NEs Not more than 60
for a GNE
7.2 Management Capability

The management capability of the T2000, on the basis of satisfying the prescribed performance
indexes, can be measured by the maximum number of NEs it manages.
Currently, a set of the T2000 can manage a maximum of 15000 Equivalent NEs. This conclusion
is drawn after the test under a certain environment and reflects the actual ability of the T2000.
For the network construction of various NEs, the management capability of the T2000 has a
certain conversion relationship with the data mentioned above. Specifically, the conversion
considers the following aspects into account.
l The size of databases depends on the number of fibers of various NEs, and the volume of
service on the fibers.
l Different hardware platforms inevitably affect the management capability of the T2000.
Generally, both the T2000 server and the T2000 client are affected.
l If the T2000 server and the client run at the same computer, the T2000 management
capability is reduced by 50%. Therefore, it is recommended to run the client and the server
separately. In this case, it is unnecessary to consider the effect of the client on the
management capability of the server.
Considering the factors stated above, the formulas for the management capability of the T2000
are as follows:

Maximum number of managed NEs = 1000 * A / B
A: Management capability coefficient of hardware platform. See Table 7-2.
B: Equivalent coefficient to Equivalent NE. See Table 7-3.
Table 7-2 Management capability of different hardware platforms
Hardware platform Management Maximum Maximum

capability number of Number of
coefficient concurrently Managed Trails
accessed clients
Sun SPARC Enterprise 15 100 SDH: 300000

M4000 (4CPU)a WDM: 50000
Sun SPARC Enterprise 6 64 Trunk Link: 5000
M4000 (2CPU) Ethernet: 10000
ATM: 10000
Sun SPARC Enterprise 6 64
T5220 (8Core) Tunnel: 35000
PTN: 40000
Sun SPARC Enterprise 2 32
T5220 (4Core)
Sun Fire E4900 6 64
Sun Fire V890 (4CPU) 3 48
Sun Fire V890 (2CPU) 1.5 32
Sun Netra 240 0.6 16
Sun Fire V490 (2CPU) 0.8 24
Sun Blade 2500 0.6 16
Fujitsu PW 650 (4CPU) 2 48
Fujitsu PW 650 (2CPU) 1.5 32
IBM X3850 10 100
IBM X3650 6 100
IBM X3500 2 64
IBM X3200 0.6 24
HP DL 580 10 100
HP DL 380 6 100
HP ML 350 2 64
HP ML 110 0.6 24
HP 570 2 48
DELL PE 6800 2 48

Hardware platform Management Maximum Maximum

capability number of Number of
coefficient concurrently Managed Trails
accessed clients
DELL PE 2900 1.5 32
DELL PE 840 0.6 24
DELL 6850 2 48
DELL 6600 0.8 24
DELL 2800 1 24
NOTE
a: If the count of NEs managed by the T2000 is not less than 6000 equivalent nodes, the disk array should
be configured.
Table 7-3 Equivalent coefficient of various NEs

NE Equivalent coefficient
OSN series OptiX OSN 500 1
OptiX OSN 1500 3.5 (With ASON)/2.5 (Without

ASON)
OptiX OSN 2000 2

ASON)

ASON)
OptiX OSN 7500 10 (With ASON)/6.5 (Without

ASON)
OptiX OSN 9500 15 (With ASON)/10 (Without

ASON)
MSTP series OptiX Metro 100 0.5
OptiX Metro 200 0.5
OptiX Metro 500 1
OptiX 155/622H(Metro 1000) 1
OptiX Metro 1000V3 1
OptiX Metro 1050 1.5

OptiX 155/622(Metro 2050) 2
OptiX 2500+(Metro 3000) 3
OptiX Metro 3100 3
OptiX 10G(Metro 5000) 4
SDH series OptiX 155C 1
OptiX 155S 1
OptiX 155/622B 2
OptiX 2500 3
OptiX 2500 REG 1.5
Metro WDM OptiX Metro 6020 1

series
OptiX Metro 6040 1
OptiX Metro 6040 V2 1
OptiX Metro 6100V1 1.5
OptiX Metro 6100V1E 1.5
OptiX OSN 900A 1
LH WDM series OptiX BWS OAS, OptiX BWS 1.5

OCS, OptiX BWS OIS
OptiX BWS 320GV3 1.5
OptiX BWS 1600G, OptiX BWS 1.5 x (N + 1)

1600G OLA NOTE
N refers to the number of slave
subracks on WDM equipment.
OptiX OTU40000 1
Submarine OptiX BWS 1600S 1.5

series
OptiX SLM 1630 1
NG WDM OptiX OSN 1800 1

series
ASON)
OptiX OSN 6800 4 x (N + 1) (With ASON)

2 x (N + 1) (Without ASON)
NOTE

OptiX OSN 8800 I 10 x (N + 1) (With ASON)

6 x (N + 1) (Without ASON)
NOTE
RTN series OptiX RTN 605 0.4
OptiX RTN 610 0.4
OptiX RTN 620 0.5
OptiX RTN 910 0.5
OptiX RTN 950 1
PTN series OptiX PTN 1900 2.5
OptiX PTN 3900 4.5
OptiX PTN 912 0.5
OptiX PTN 910 0.5
OptiX PTN 950 1

Product Description for SDH A Standards Followed
A Standards Followed
Standard Description
ITU-T G.707 Network node interface for the synchronous digital hierarchy (SDH)
ITU-T G.773 Protocol suites for Q-interfaces for management of transmission

systems
ITU-T G.774 (01, 02, Synchronous Digital Hierarchy (SDH) management information
03, 04) model for the NE view
ITU-T G.783 Features of SDH functional blocks
ITU-T G.784 Synchronous digital hierarchy (SDH) management
ITU-T G.803 Architecture of transport networks based on the synchronous digital

hierarchy (SDH)
ITU-T G.831 Management capabilities of transport networks based on the

synchronous digital hierarchy (SDH)
ITU-T G.851.1 Management of the transport network - Application of the RM-ODP

framework
ITU-T G.852.1 Management of the transport network - Enterprise viewpoint for

simple sub-network connection management
ITU-T G.852.2 Enterprise viewpoint description of transport network resource model
ITU-T G.852.3 Enterprise viewpoint for topology management
ITU-T G.852.6 Enterprise viewpoint for route management
ITU-T G.853.1 Common elements of the information viewpoint for the management
of a transport network
ITU-T G.853.2 Sub-network connection management information viewpoint
ITU-T G.853.3 Information viewpoint for topology management
ITU-T G.853.6 Information viewpoint for trail management
Issue 01 (2009-06-30) Huawei Proprietary and Confidential A-1

A Standards Followed Product Description for SDH
Standard Description
ITU-T G.854.1 Computational interfaces for basic transport network model
ITU-T G.854.3 Computational viewpoint for topology management
ITU-T G.854.6 Computational viewpoint for trail management
ITU-T M.20 Maintenance philosophy for telecommunications networks
ITU-T M.3000 Overview of TMN recommendations
ITU-T M.3010 Principles for a telecommunications management network
ITU-T M.3013 Considerations for a telecommunications management network
ITU-T M.3017 Framework for the integrated management of hybrid circuit/packet

networks
ITU-T M.3020 TMN interface specification methodology
ITU-T M.3100 Generic network information model
ITU-T M.3101 Managed Object Conformance statements for the generic network
information model
ITU-T M.3180 Catalogue of TMN management information
ITU-T M.3200 TMN management services and telecommunications managed areas:

overview
ITU-T M.3300 TMN F interface requirements
ITU-T M.3400 TMN management functions
ITU-T X.720 Management information model
ITU-T X.721 Definition of management information
ITU-T X.722 Guidelines for the definition of managed objects
ITU-T X.733 Information technology - Open Systems Interconnection - Systems

Management: alarm reporting function
ITU-T X.903 Information technology - Open distributed processing - Reference

Model: architecture
Sif99025 EML-NML interface models
TMF 509 NML-EML Interface Business Agreement For Management of

SONET/SDH Transport Networks
TMF513 V2.0 Multi-Technology Network Management Business Agreement

NML-EML Interface Version 2.0
TMF608 V2.0 Multi-Technology Network Management Information Agreement

NML-EML Interface Version 2.0
TMF814 V2.0 Multi Technology Network Management Solution Set Conformance

Document Version 2.0
A-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description for SDH B Glossary
B Glossary
AIS insertion If there are excessive errors in a channel, AIS can be inserted in this
channel to indicate it is unavailable. For a line board, you can set
whether to insert AIS when there are excessive errors in the B1, B2
and B3 bytes. For a tributary board at the E1 or T1 level, you can set
whether to insert AIS when there are excessive errors in BIP-2. For a
tributary board at the E3 level or higher, you can set whether to insert
AIS when there are excessive errors in the B3 byte.
AIS Alarm Indication Signal. A signal sent downstream in a digital

network if an upstream failure has been detected and persists for a
certain time.
Alarm correlation In the case alarm2 is raised within five seconds after alarm1 is raised,
analysis and alarm2 complies with the conditions defined in the alarm
correlation analysis rule, you can either suppress the alarm2 or raise
its severity level according to the behavior defined in the alarm
correlation rule. Such a process is called alarm correlation analysis.
Alarm reversion For the port that has already been configured but not actually loaded
with services, this function can be used to avoid generating relevant
alarm information, thus preventing alarm interference.
Alarm severity According to ITU-T recommendations, the alarm is classified into

four severities: Critical, Major, Minor, and Warning.
Alarm suppression The suppressed alarm of a specific object is not reported. The object
here may be the networkwide equipment, a specific NE, a specific
board and even a specific function module of a specific board.
Alarm A visible or an audible indication to notify the person concerned that

a failure or an emergency has occurred. See also Event.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential B-1

B Glossary Product Description for SDH
ATM protection An ATM protection group refers to the logically bound ATM VP
group network or subnetwork connections that share the same physical
transmission channel. In the VP group (VPG), a pair of VP
connections (working connection and its protection connection) is
used for monitoring the automatic protection switching, called
monitoring connections (APS VPCs). If the monitoring connections
switch over, the whole VPG will switch over to quicken the ATM
protection switching (as quick as the protection switching of the SDH
layer.
ALS Automatic Laser Shutdown. ALS is turned on when the optical

interface board does not carry services or the optical fibre is faulty.
Its service life can be prolonged by decreasing the duration during
which laser is on.
Attribute Property of an object.
Automatic switching When the active board or path fails, the standby one can automatically
take over the job of the active one.
Binding In virtual concatenated payload configuration, designating one

binding number to identify the VC4s of the same virtual concatenated
payload is called "bind". If a fault occurs to one of the bound services,
all bound services will switch as a whole.
Bit error alarm When the bit error reaches a specific limit, the equipment will report
threshold an alarm. This limit is the bit error alarm threshold. The threshold can
be divided into crossing threshold and defect threshold.
Check alarms The check feature compares one (or more) uncleared alarm on the
T2000 with that on the NE. If an alarm is included in the current alarms
on the NE, it is kept on the T2000. If not, it will be removed from the
T2000.
Client A kind of terminal (PC or workstation) connected to a network that

can send instructions to a server and get results through a user
interface. See also server.
Clock View The Clock View provides a visible platform to enable:1. NE clock
settings2. Networkwide clock synchronisation status query3. Clock
tracing and search functions
Configuration data The data that configures the NE hardware for coordination between
this NE and other NEs in the entire network and operation of specified
services. Configuration data is the instruction file of NEs, and it is the
key for efficient network running. The typical configuration data
includes board configuration, clock configuration and protection
relationship.
B-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Configuration Configuration management enables inventory query of network

management configuration resources, including relevant configuration of NMS or
SNMS, NE, subnet, links, SNC, route, TP, edge point, equipment, and
so on. Real-time inventory change report can also be provided through
this resource, it will be timely reported to the upper NMS to notify
the carrier of the current network operation status and ensure data
consistency of the upper NMS or SNMS.
Configure To set the basic parameters of an operation object.
Connection point A reference point where the output of a trail termination source or a
connection is bound to the input of another connection, or where the
output of a connection is bound to the input of a trail termination sink
or another connection. The connection point is characterized by the
information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
Connection A "transport entity" which consists of an associated pair of

"unidirectional connections" capable of simultaneously transferring
information in opposite directions between their respective inputs and
outputs.
Current alarms Alarms that do not clear, or has cleared but is not acknowledged.
Current performance The performance data stored in the current register is called current
data performance data. The current 15-minute or 24-hour register (only
one for each) is applied to collect the performance data in the current
monitoring period. It changed within the monitor period.
DCC Within an STM-N signal there are two DCC channels, one is the 192
kbit/s DCC-R channel composed of bytes D1-D3, and the other is the
576 kbit/s DCC- channel composed of bytes D4-D12. All NEs can
communicate with one another through the DCC-R. The DCC-M is
not the regenerator section overhead and does not support
communications among regenerators, and it is used to support
communication channels of more universal purpose. For example, it
supports TMN as a physical channel of ECC.
DNI Dual Node Interconnection. The protection mode defined in G. 842

Recommendation for the inter-ring service . By using the
recommended protection modes, the protection of the interconnecting
service between two ring networks composed of the devices from
different manufacturers and in different protection modes can be
realised. Moreover, in case of fibre failure or node failure, services
can also be protected.
Domain The domain of the T2000 specifies the scope of address or functions
which are available to a certain user.

ECC Embedded Control Channel. An ECC provides a logical operations

channel between SDH NEs, utilising a data communications channel
(DCC) as its physical layer.
EMU Environment Monitoring Unit. As one type of power and environment

monitoring unit, EMU is installed on the top of the OptiX 155/622H
equipment cabinet to monitor the environment variables, such as the
power supply and temperature. With external signal input through the
relay, fire alarm, smoke alarm, burglary alarm, and so on can be
monitored as well. Displayed on the T2000, the change of
environment can be monitored timely and accurately.
Equipment set An aggregate of multiple managed equipment. Equipment set

facilitates the user authority management on equipment in the
management domain of the T2000. If some operation authorities over
one equipment set are assigned to a user (user group), these operation
authorities over all equipment of the equipment set are assigned to the
user (user group).
Failure The fault cause persisted long enough to consider the ability of an
item to perform a required function to be terminated. The item may
be considered as failed; a fault has now been detected.
Fault A fault is the inability of a function to perform a required action. This

does not include an inability due to preventive maintenance, lack of
external resources, or planned actions.
Forced switch This command performs the ring switch from working channels to the
protection channels. This switch occurs regardless of the state of the
protection channels, unless the protection channels are satisfying a
higher priority bridge request.
History alarms Alarms that have cleared and been acknowledged.
History performance The performance data stored in the history register and the auto-report
data performance data stored on the T2000 are called history performance
data in a unified way.

Intermediate office It refers to the equipment used for optical fibre management and
dispatch in the metropolitan area. It has multiple pairs of interfaces
for the optical fibre connection. Every two interfaces in a pair are
connected with each other to form a longer physical optical fibre path.
The physical optical fibre path connecting the transmission equipment
can comprise two or more sections of optical fibre cascaded via the
intermediate office. There is an intermediate office information list
for some fibre & cable connections, which shows the section
information about the fibre & cable.
IP address In the TCP/IP protocol, it is used to uniquely identify the address of

the communication port, which consists of four bytes in decimal
digits, for example, 129.9.161.55.
Label A mark on a cable, a subrack, or a cabinet for identification.
Layer A concept used to allow the transport network functionality to be

described hierarchically as successive levels; each layer being solely
concerned with the generation and transfer of its characteristic
information.
LCT Local Craft Terminal. The LCT provides the user with single-layer
management network solutions to the transmission network of up to
five NEs to realise integrated management of multi-service
transmission network. Usually it uses the cross-over cable or serial
port cable to connect one NE, so as to configure and maintain a single
NE. See also T2000 LCT.
Licence A permission provided by a vendor to authorise the use of specific

functions of a product. Usually the licence consists of encrypted
codes, and the operation authority varies with different level of
licence.
Lock NE login This function prohibits the users at lower levels from logging in NE
and forces logged NE users with lower level to log out.
Main Topology The default T2000 client interface and all topology management
functions are accessed here.
Management The signal passing across an access point.

information
Manual switch When the protection channel is efficient and there is no higher-level
switching request, this mode switches the service from the working
channel to the protection channel, thus testing whether network still
has the protection capability.
MO Managed Object. The management view of a resource within the

telecommunication environment that may be managed via the agent.
Examples of SDH managed objects are: equipment, receive port,
transmit port, power supply, plug-in card, virtual container, multiplex
section, and regenerator section.

MS Multiplex Section. A multiplex section is the trail between and

including two multiplex section trail termination functions.
MSP Multiplex section protection. The nodes online achieve protection

switching through the K1 and K2 bytes in the multiplex section,
including linear 1+1 MS protection switching link, linear 1:n MS
protection switching link, dedicated MS protection ring and shared
MS protection ring.
NE database There are three types of database on NE SCC board as following: (1)
DRDB: a dynamic database in a dynamic RAM, powered by battery;
(2) SDB: a static database in a power-down RAM; (3) FDB0, FDB0:
permanently saved databases in a Flash ROM. In efficient operation,
the NE configuration data is saved in DRDB and SDB at the same
time. Backing up an NE database means backing up the NE
configuration data from SDB to FDB0 and FDB1.
NE Explorer NE Explorer is the main operation interface of the T2000. For easy
navigation, the NE Explorer window presents an expandable
directory tree (Function Tree) in the lower left pane. The
configuration, management and maintenance of the equipment are
accessed here.
NE Network Element. NE includes the hardware unit and the software

running on it. Usually, one NE has at least an SCC (system control
and communication) board which responsible for the management
and monitoring of the NE. The NE software runs on the SCC board.
NM Network Management. In the telecommunication management

network structure, the T2000 is located between the NE level and
network level, which can supports all functions at NE level and part
of the network level management functions. See also T2000.
NNI Network Node Interface. NNI identifies the interface between the
ATM network nodes. See also SDH NNI.
Online help An indexed collection of information on all aspects of the T2000.

They can be accessed at any time from the Help menu or by pressing
the F1 key.
Path protection The working principle of path protection: When the system works in
path protection mode, the PDH path uses the dual-fed and signal
selection mode. Through the tributary unit and cross-connect unit, the
tributary signal is sent simultaneously to the east and west lines.
Meanwhile, the cross-connect matrix sends the signal dually sent from
the opposite end to the tributary board through the active and standby
buses, and the hardware of the tributary board will selectively receive
the signal from the two groups of buses automatically according to
the AIS number of the lower order path.

Path A trail in a path layer.
Performance register Performance register is the memory space for performance event
counts, including 15-min current performance register, 24-hour
current performance register, 15-min history performance register,
24-hour history performance register, UAT register and CSES
register.
Performance Performance events usually have upper and lower thresholds. When
threshold the performance event count value exceeds the upper threshold, a
performance threshold-crossing event is generated; when the
performance event count value is below the upper threshold for a
period of time, the performance threshold-crossing event is ended. In
this way, performance jitter caused by some sudden events can be
shielded.
PMU One type of power and environment monitoring unit.
Private line Both communication parties are connected permanently.
Procedure A generic term for an action.
Process A generic term for a collection of actions.
Protection path A specific path that is part of a protection group and is labeled
protection.
Protection strategy In case the service route provides multiple service protections,
different protection strategies can be selected as required. Protection
strategy refers to the protection mode given the priority in use for the
trail: protection, no protection, and extra traffic. Of the above, the
protection preference is divided into trail protection and sub-network
connection protection.
Protection subnet The resources that form a protection subnetwork include NEs and
fiber cables. The creation of the protection subnetwork actually means
that corresponding logical system is configured for each NE by means
of creating the protection subnetwork, the optical interfaces (or VC4)
of each board are mapped into the logical system, and then these
independent logical systems are connected with one another to form
a complete network structure.

Route The IP route selection is in table driving mode. In each host and each
router of the Internet, there is a routing table that contains information
about how the service is transmitted from the source to the sink,
providing a basis for route selection. Ethernet static routing in ET1
refers to the mapping relationship between the Ethernet port and the
bound path. Its routing type includes port routing and VLAN routing.
Port routing: It means configuring a route between the Ethernet port
and the bound path port, which is usually used for point-to-point
networking communication; VLAN routing: It means configuring a
route between the Ethernet port and the bound path port based on the
VLAN service. It can be used flexibly in point-to-point, point-to-
multipoint or multipoint-to-multipoint communication. The
implementation is to divide and converge the data stream according
to the VLAN flag of the packet. As a VLAN flag can be added to the
Ethernet port, the equipment can be applied more flexibly.
Script file It is the text file describing the physical information and configuration
information of the entire network, including the NE configuration file,
port naming file, end-to-end configuration file, NE physical view
script file, NM information file and service implementation data script
file.
Script A list of instructions for performing a specific task or action, written

in a scripting language.
SDH NNI SDH Network Node Interface. It is applied to build communications

connection with the equipment beyond the T2000 management area.
Usually, the NM creates an SDH NNI by creating a logical system on
the port of an idle line board, and the NE must be a TM without
protection and fibre connection.
Section A trail in a section layer.
Settings Parameters of an operation that can be selected by the user.
Severity See Alarm Severity.
Subnet mask Also referred to as the network mask off code, it is used to define
network segments, so that only the computers in the same network
segment can communicate with one another, thus suppressing
broadcast storm between different network segments.
Subnet number Subnetwork number is used to differentiate the different network

sections in the sub-network conference. Actually it is the first several
digits (one or two) of the user phone number. An orderwire phone
number is composed of the sub-network number and the user number.
Subnet Sub-network is the logical entity in the transmission network and

comprises a group of network management objects. A sub-network
can contain NEs and other sub-networks. A sub-network planning can
better the organisation of a network view.

Support The frame on the bottom of a cabinet, when installing the cabinet on
the antistatic floor.
Synchronise NE time Send the system time of the T2000 server to NEs so as to synchronise
all NEs with the server.
T2000 The T2000 is a subnetwork management system (SNMS). In the TMN

architecture, the T2000 is located between the NE level and network
level, which can supports all function of NE-level and part of the
network-level management functions. See also NM.
T2100 The T2100 is a network level management system for the optical
transmission network, and is located in the network management layer
(NML) in the telecommunication management network (TMN)
architecture.
TDA clock source TDA is short for Tone Data Access. For the 2500+ NE equipment, it
can be installed with the external TDA board for which the clock
source must be set so that the TDA board can switch according to the
set clock source sequence when clock source switching occurs.
TMN Telecommunications Management Network. The entity which

provides the means used to transport and process information related
to management functions for the telecommunications network.
Topology The T2000 topology is a basic component of the man-machine

interactive interface. The topology clearly shows the structure of the
network, the alarms of different NEs, sub-networks in the network,
the communication status as well as the basic network operation
status.
Trail management A network level management function of the T2000. Through trail
function management, you can configure end-to-end services, view graphic
interface and visual routes of a trail, query detailed information of a
trail, filter, search and locate a trail quickly, manage and maintain
trails in a centralised manner, manage alarms and performance data
by trail, and print a trail report.
Trail A trail is a kind of transport entity, mainly engaged in transferring

signal from the input of the trail source to the output of the trail sink,
and monitoring the integrality of the transferred signal. According to
the different levels of the trail, the trail includes various types (OTS,
OCH, OMS, SPI, RS, MS, VC4 server trail, VC4, VC3 and VC12).
Among them, OTS, OCH and OMS represent the trails in a DWDM
layer network. For the ADM and TM equipment in the SDH network,
each optical fibre connection corresponds to an SPI, RS or MS trail,
and a trail is the general name for service carriers, including SDH and
PDH services.
Tributary loopback A fault can be located for each service path by performing loopback
to each path of the tributary board. There are three kinds of loopback
modes: No loopback, Outloop and Inloop.

UAT Unavailable Time. A UAT event is reported when the monitored

object generates 10 consecutive severely errored seconds (SES) and
the SESs begin to be included in the unavailable time. The event will
end when the bit error ratio per second is better than 10-3 within 10
consecutive seconds.
UNI UNI is the abbreviation for User Network Interface. It identifies the
interface between the user and the ATM network node.
Unprotected Services transmitted through an ordinary way, once a failure or

interruption occurs, the data cannot be restored for lack of protection
mechanism.
Upload Report all or part of the configuration data of the NE to the NM and
overwrite the configuration data saved in the NE layer on the NM
side.
User group User set refers to the set of NMS users with the same management
authorities. The default user group includes: system administrator,
system maintainer, system operator and system supervisor. The
attributes of user set include name and detailed description.
User The user of the T2000 client, and the user and his/her password define
the corresponding authority of operation and management of the
T2000.
VC4 loopback The fault of each VC4 path on the optical fibre can be located by
setting loopback for each VC4 path of the line. There are three kinds
of loopback modes: No loopback, Outloop, Inloop.
VC4 server trail The path rate of the VC4 server trail is 150.336Mbit/s. The VC4 server
trail provides transparent channels (that is, circuit group) for circuit-
layer network nodes (for example, a switch) in a path-layer network,
and acts as the basic unit of inter-office communication path. When
the VC4 server trail is configured, only the higher order cross-
connection of VC4 is generated in the intermediate NE, but no cross-
connection is generated at the two ends, that is, no service is added/
dropped. Therefore, the VC4 server trail is not a traditional service.
It is only the basis for VC3 and VC12 trail creation.
VCI The VCI, shorted for Virtual Channel Identifier, occupies 16 bits in
both NNI cell or UNI cell. It indicates the virtual channel in the path.
The VPI and VCI together indicate a virtual connection.

Virtual fibre A virtual fibre is created between SDH equipment that has WDM
equipment in between. From SDH equipment perspective, creation of
virtual fibres disassociates its fibre connection with WDM equipment
and prevents impact on the auto fibre search function, ensuring
independence of SDH trail management.From WDM equipment
perspective, its service bearer layer is a virtual fibre instead of a true
one after the virtual fibre is created. Deletion of the true fibre does
not affect trail management.
Virtual NE Like a common NE, a virtual NE is also displayed with an icon on a

view, but it is only an NE simulated according to the practical
situation, which does not represents an actual NE. Therefore, the
actual status of this NE cannot be queried and its alarm status cannot
be displayed with colours. Usually, when the trail management
function is used for the NEs or sub-networks the T2000 cannot
manage, or the equipment is interconnected with other vendors’ NEs
for service configuration, the end-to-end service configuration
method and the trail management capability are provided.
VLAN ID Namely, it is the virtual LAN identifier. One Ethernet port can support
4K VLAN routes, and one NE can support up to 8K VLAN routes.
VPI The VPI, shorted for Virtual Path Identifier, occupies 12 bits in the
NNI cell, and 8 bits in the UNI cell.
Web LCT In the TMN architecture, the Web LCT is located in the NE
management level, which can manage the RTN series and NG WDM
series equipment.
Working path A specific path that is part of a protection group and is labelled
working.
WTR time A period of time that must elapse before a - from a fault recovered -
trail/connection can be used again to transport the normal traffic
signal and/or to select the normal traffic signal from.
WTR Wait to Restore. This command is issued when working channels

meet the restoral threshold after an SD or SF condition. It is used to
maintain the state during the WTR period unless it is pre-empted by
a higher priority bridge request.

Product Description for SDH C Acronyms and Abbreviations
C Acronyms and Abbreviations
ACE Adaptive Communication Environment
ACL Access Control List
AIS Alarm Indication Signal
ASN.1 Abstract Syntax Notation One
ASON Automatically Switched Optical Network
ATM Asynchronous Transfer Mode
BML Business Management Layer
CAR Committed Access Rate
CC Continuity Check
CORBA Common Object Request Broker Architecture
CoS Class of Service
CPU Central Processing Unit
DCC Data Communications Channel
DCN Data Communication Network
DDN Digital Data Network
DNI Dual Node Interconnection
ECC Embedded Control Channel
EML Element management Layer
EMS Element Management System
EPL Ethernet Private Line
EPLAN Ethernet Private LAN
ESCON Enterprise System Connection
Issue 01 (2009-06-30) Huawei Proprietary and Confidential C-1

C Acronyms and Abbreviations Product Description for SDH
EVPL Ethernet Virtual Private Line
FCAPS Fault Management, Configuration Management, Accounting

Management, Performance Management, Security Management
GNE Gate Network Element
GUI Graphical User Interface
HA High-Availability
HTTP Hyper-Text Transmission Protocol
ID IDentification
IGMP Internet Group Management Protocol
IMA Inverse Multiplexing for ATM
iMAP Integrated Management Application Platform
ION Intelligent Optical Network
IP Internet Protocol
ISDN Integrated Services Digital Network
ITU-T International Telecommunication Union- Telecommunication

Standardization Sector
LAN Local Area Network
LB Loopback
LCAS Link Capacity Adjustment Scheme
LCD Liquid Crystal Display
LCT Local Craft Terminal
LLID Locate Loopback ID
LPT Link-state Pass Through
LT Link Trace
MAC Media Access Control
MDI Multi-Document Interface
MDP Message Dispatch Process
Mgr Manager
MIB Management Information Base
MIT Managed Object Instance Tree
MML Man Machine Language
MO Managed Object
C-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description for SDH C Acronyms and Abbreviations
MPLS Multiprotocol Label Switching
MS Multiplex Section
MSP Multiplex Section Protection
MSTP Multi-Service Transmission Platform
MTBF Mean Time Between Failures
MTTR Mean Time to Repair
NE Network Element
NEL Network Element Level
NML Network Management Layer
NMS Network Management System
NSAP Network Service Access Point
OAM Operation Administration and Maintenance
OIF Optical Internetworking Forum
OSF Operation System Function
OSI Open Systems Interconnection
OSN Optical Switch Network
OSNR Optical Signal-to-Noise Ratio
OSPF Open Shortest Path First
PC Personal Computer
PDH Plesiochronous Digital Hierarchy
PP Path Protection
PRBS Pseudo-Random Binary Sequence
PRC Primary Reference Clock
PSTN Public Switched Telephone Network
QoS Quality of Service
RAS Reliability, Availability, Survivability
RSVP Resource Reservation Protocol
RDBMS Relational Database Management System
RPR Resilient Packet Ring
RMON Remote Monitoring
RS Regenerator Section
Issue 01 (2009-06-30) Huawei Proprietary and Confidential C-3

C Acronyms and Abbreviations Product Description for SDH
RTN Radio Transmission Node
RUP Rational Unified Process
SDH Synchronous Digital Hierarchy
SML Service Management Layer
SMS Service Management System
SNCMP Sub-Network Connection Multiple Protection
SNCP Sub-Network Connection Protection
SNCTP Sub-Network Connection Tunnel Protection
SNML Sub-Network Management Layer
SNMS Subnetwork Management System
SONET Synchronous Optical Network
TCM Tandem Connection Measurement
TCP/IP Transmission Control Protocol/Internet Protocol
TDA Tone & Data Access Unit
TM Terminal Multiplexer
TMF TeleManagement Forum
TMN Telecommunication Management Network
TPS Tributary Protection Switching
UML Unified Modeling Language
UPS Uninterrupted Power Supply
VB Virtual Bridge
VCS Veritas Cluster Server
VCI Virtual Channel Identifier
VPI Virtual Path Identifier
VLAN Virtual Local Area Network
VPN Virtual Private Network
VVR Veritas Volume Replicator
VxVM Veritas Volume Manager
WDM Wavelength Division Multiplexing
WSF Work Station Function
WTR Wait-to-Restore
C-4 Huawei Proprietary and Confidential Issue 01 (2009-06-30)


Product Description For SDH: Optix Imanager T2000 V200R007C03

Uploaded by

Copyright:

Available Formats

Product Description For SDH: Optix Imanager T2000 V200R007C03

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Product Description For SDH: Optix Imanager T2000 V200R007C03

Uploaded by

Copyright:

Available Formats

What is the product being described?

What is the product being described?

What are some of the key features discussed?

What are some of the key features discussed?

OptiX iManager T2000

Product Description for SDH

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

3 Features and Functions..............................................................................................................3-1

4 Networking and Application...................................................................................................4-1

Issue 01 (2009-06-30) Huawei Proprietary and Confidential i

A Standards Followed ................................................................................................................A-1

ii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Figure 1-1 The position of the T2000 in TMN....................................................................................................1-2

Issue 01 (2009-06-30) Huawei Proprietary and Confidential iii

Table 1-1 Manageable SDH series equipment.....................................................................................................1-3

Issue 01 (2009-06-30) Huawei Proprietary and Confidential v

Table 5-30 Software configurations for the server.............................................................................................5-23

vi Huawei Proprietary and Confidential Issue 01 (2009-06-30)

About This Document

Product Name Version

OptiX iManager T2000 V200R007C03

l Network Planning Engineer

Issue 01 (2009-06-30) Huawei Proprietary and Confidential 1

Chapter 5 System Architecture This chapter describes hardware structure, external

Chapter 6 Reliability This chapter describes the recommended reliability

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

NOTE Provides additional information to emphasize or

2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Issue 01 (2009-06-30) Huawei Proprietary and Confidential 3

Double-click Press the primary mouse button twice continuously and

Updates in Issue 01 (2009-06-30) Based on Product Version V200R007C03

Chapter 2 New Features

Descriptions of new features are updated.

Chapter 3 Features and Functions

Descriptions of features and functions are updated.

Chapter 7 Technical Specifications

Descriptions of performance indexes and management capability are updated.

4 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Updates in Issue 01 (2009-03-30) Based on Product Version V200R007C02

Chapter 1 System Overview