System Description

1 Brief Introduction.......................................................................................... 1.1 Position in TMN Hierarchy ...................................................................... 1.2 Manageable Equipment ......................................................................... 2 Application .................................................................................................... 2.
1 Single-Layer Management Network ....................................................... 2.2 Hierarchical Management Network ........................................................ 3 Functional Characteristics........................................................................... 3.1 Main Functions ....................................................................................... 3.1.1 Alarm .............................................................................................. 3.1.2 Performance Monitoring ................................................................. 3.1.3 Configuration of NE Layer .............................................................. 3.1.4 Configuration of Network Layer ..................................................... 3.1.5 Security .......................................................................................... 3.1.6 Maintenance .................................................................................. 3.1.7 Report ............................................................................................ 3.1.8 Topology Management .................................................................. 3.1.9 Log Management ........................................................................... 3.2 Main Interfaces ....................................................................................... 3.3 New Characteristics ............................................................................... 4 System Architecture ..................................................................................... 4.1 Standard Client-Server Structure ........................................................... 4.1.1 Hardware Connection .................................................................... 4.1.2 Function Modules........................................................................... 4.1.3 Configuration Requirement ............................................................ 4.2 Extended Structure of Multiple Servers .................................................. 4.2.1 Hardware Connection .................................................................... 4.2.2 Software Structure ......................................................................... 4.3 About the HA System ............................................................................. 4.4 HA System (Sun Cluster) ....................................................................... 4.4.1 Hardware Connection .................................................................... 4.4.2 Software Structure ......................................................................... 4.4.3 Configuration Requirements .......................................................... 4.4.4 Principles of Switching ................................................................... 4.5 HA System (Veritas) ............................................................................... 4.5.1 Hardware Connection .................................................................... 4.5.2 Software Structure ......................................................................... 4.5.3 Configuration Requirements .......................................................... 4.5.4 Principles of Switching ...................................................................
1-1 1-1 1-3 2-1 2-1 2-3 3-1 3-1 3-1 3-3 3-4 3-8 3-10 3-11 3-12 3-13 3-13 3-13 3-14 4-1 4-1 4-1 4-3 4-4 4-6 4-6 4-6 4-7 4-8 4-8 4-9 4-9 4-10 4-11 4-11 4-12 4-12 4-13
4.6 HA System (Watchman) ......................................................................... 4.6.1 Hardware Connection .................................................................... 4.6.2 Software Structure ......................................................................... 4.6.3 Configuration Requirements .......................................................... 4.6.4 Principles of Switching ................................................................... 4.7 External Interfaces ................................................................................. 4.7.1 Qx .................................................................................................. 4.7.2 MML ............................................................................................... 4.7.3 CORBA .......................................................................................... 5 Reliability Design .......................................................................................... 5.1 HA System ............................................................................................. 5.2 DCN Protection ...................................................................................... 5.3 Disk Mirroring ......................................................................................... 5.4 Data Backup ........................................................................................... 6 Performance Indices .................................................................................... 6.1 Performance Indices .............................................................................. 6.1.1 Alarm Capacity ............................................................................... 6.1.2 Performance Capacity ................................................................... 6.1.3 Capacity of Other Logs .................................................................. 6.1.4 CPU Utilization Status .................................................................... 6.1.5 Response Speed of Alarm Handling .............................................. 6.1.6 Response Speed of Performance Handling ................................... 6.1.7 Time of Configuring a Circuit ......................................................... 6.1.8 Time of Searching a Circuit............................................................ 6.1.9 Number of Users, Subnets and Links Managed by the System .... 6.1.10 Time of Local Active/ Standby Server Switching ......................... 6.1.11 Time of Remote Active/Standby Server Switching ...................... 6.1.12 Time of DCN Protection Switching ............................................... 6.1.13 Mean Time Between Failures (MTBF) ......................................... 6.1.14 Mean Time to Repair (MTTR) ...................................................... 6.2 Management Capability Calculation ....................................................... A Standards Followed ..................................................................................... B Abbreviations ...............................................................................................
4-14 4-14 4-14 4-15 4-16 4-17 4-17 4-17 4-18 5-1 5-2 5-2 5-3 5-4 6-1 6-1 6-1 6-1 6-1 6-1 6-2 6-2 6-2 6-2 6-2 6-2 6-2 6-2 6-2 6-2 6-3 A-1 B-1
HUAWEI
OptiX iManager T2000 System Description

V100R008
Huawei Technologies Proprietary

Manual Version Product Version BOM T2-040294-20041027-C-1.82 V100R008 31026194
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd., Bantian, Longgang District, Shenzhen, P. R. China Postal Code: 518129 Website: http://www.huawei.com Email: support@huawei.com
Copyright 2004 Huawei Technologies Co., Ltd. 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
, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC, TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEIOptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this manual 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 all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Summary of Updates
This section provides the update history of this manual and introduces the contents of subsequent updates.
Update History
Release T2-040294-20040615-C-1.80 T2-040294-20040914-C-1.81 T2-040294-20041027-C-1.82 Release upgrade description Initial commercial release Second release. Third release.
Updates of Contents
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.
Updates in Manual Version 1.81

Modify the disk array delivery principle to optional in the Table 4-8. Add 6. ROME Text Export in the 3.3 New Characteristics.
Updates in Manual Version 1.82

Change Blade 2000 to Blade 2500 in the chapter 4 System Architecture.
Contents
Contents
1 Brief Introduction
1.1 Position in TMN Hierarchy 1.2 Manageable Equipment
1-1
1-1 1-3
2 Application
2.1 Single-Layer Management Network 2.2 Hierarchical Management Network
2-1
2-1 2-3
3 Functional Characteristics
3.1 Main Functions 3.1.1 Alarm 3.1.2 Performance Monitoring 3.1.3 Configuration of NE Layer 3.1.4 Configuration of Network Layer 3.1.5 Security 3.1.6 Maintenance 3.1.7 Report 3.1.8 Topology Management 3.1.9 Log Management 3.2 Main Interfaces 3.3 New Characteristics
3-1
3-1 3-1 3-3 3-4 3-8 3-10 3-11 3-12 3-13 3-13 3-13 3-14
4 System Architecture
4.1 Standard Client-Server Structure 4.1.1 Hardware Connection 4.1.2 Function Modules 4.1.3 Configuration Requirement 4.2 Extended Structure of Multiple Servers
4-1
4-1 4-1 4-3 4-4 4-6
Huawei Technologies Proprietary i
OptiX iManager T2000 System Description 4.2.1 Hardware Connection 4.2.2 Software Structure 4.3 About the HA System 4.4 HA System (Sun Cluster) 4.4.1 Hardware Connection 4.4.2 Software Structure 4.4.3 Configuration Requirements 4.4.4 Principles of Switching 4.5 HA System (Veritas) 4.5.1 Hardware Connection 4.5.2 Software Structure 4.5.3 Configuration Requirements 4.5.4 Principles of Switching 4.6 HA System (Watchman) 4.6.1 Hardware Connection 4.6.2 Software Structure 4.6.3 Configuration Requirements 4.6.4 Principles of Switching 4.7 External Interfaces 4.7.1 Qx 4.7.2 MML 4.7.3 CORBA
Contents 4-6 4-6 4-7 4-8 4-8 4-9 4-9 4-10 4-11 4-11 4-12 4-12 4-13 4-14 4-14 4-14 4-15 4-16 4-17 4-17 4-17 4-18
5 Reliability Design
5.1 HA System 5.2 DCN Protection 5.3 Disk Mirroring 5.4 Data Backup
5-1
5-2 5-2 5-3 5-4
6 Performance Indices
6.1 Performance Indices 6.1.1 Alarm Capacity 6.1.2 Performance Capacity 6.1.3 Capacity of Other Logs 6.1.4 CPU Utilization Status 6.1.5 Response Speed of Alarm Handling 6.1.6 Response Speed of Performance Handling 6.1.7 Time of Configuring a Circuit
6-1
6-1 6-1 6-1 6-1 6-1 6-2 6-2 6-2
Huawei Technologies Proprietary ii
OptiX iManager T2000 System Description 6.1.8 Time of Searching a Circuit 6.1.9 Number of Users, Subnets and Links Managed by the System 6.1.10 Time of Local Active/Standby Server Switching 6.1.11 Time of Remote Active/Standby Server Switching 6.1.12 Time of DCN Protection Switching 6.1.13 Mean Time Between Failures (MTBF) 6.1.14 Mean Time to Repair (MTTR) 6.2 Management Capability Calculation
Contents 6-2 6-2 6-2 6-2 6-2 6-2 6-2 6-3
A Standards Followed B Abbreviations
A-1 B-1
Huawei Technologies Proprietary iii
Figures
Figures
Figure 1-1 The position of the T2000 in TMN Figure 2-1 Networking of single-layer management network Figure 2-2 Hardware connection of remote maintenance scheme Figure 2-3 Networking of hierarchical management network Figure 2-4 Hierarchical networking structure realized through LAN Figure 2-5 Hierarchical networking structure realized through WAN Figure 4-1 Hardware connection-client-server structure Figure 4-2 T2000 functional modules Figure 4-3 Hardware connection-Scheme of extending multiple servers Figure 4-4 Hardware connection-HA system (Sun Cluster) Figure 4-5 Software structure-HA system (Sun Cluster) Figure 4-6 Hardware connection-HA system (Veritas) Figure 4-7 Software structure-HA system (Veritas) Figure 4-8 Hardware connection-HA system (Watchman) Figure 4-9 Software structure-HA system (Watchman) Figure 4-10 External communication interfaces of the T2000 Figure 5-1 Networking of DCN management network 1-2 2-2 2-2 2-3 2-4 2-4 4-1 4-3 4-6 4-8 4-9 4-11 4-12 4-14 4-14 4-17 5-2
Huawei Technologies Proprietary iv
Tables
Tables
Table 2-1 Difference in software used in two remote maintenance schemes Table 4-1 Description of the T2000 functional modules Table 4-2 Configuration requirement-OptiX iManager the T2000 server (Unix) Table 4-3 Configuration requirement-OptiX iManager T2000 server (Windows) Table 4-4 Configuration requirement- OptiX iManager T2000 client (UNIX) Table 4-5 Configuration requirement-OptiX iManager T2000 client (Windows) Table 4-6 Configuration requirement- HA system (Sun Cluster) Server Table 4-7 Configuration requirement- HA system (Sun Cluster) console Table 4-8 Configuration requirement-HA system (Veritas) Server Table 4-9 Configuration requirement-HA system (Watchman) server Table 4-10 Configuration requirement-HA system (Watchman) client Table 6-1 Equivalent relationship between various NEs and OptiX 155/622H Table 6-2 Management capability of different hardware platforms 2-2 4-3 4-4 4-4 4-5 4-5 4-9 4-10 4-12 4-15 4-15 6-4 6-5
Huawei Technologies Proprietary v
About This Manual
About This Manual

Related Manuals
Manual OptiX iManager T2000 System Description Usage Introduces the position, functional characteristics, system architecture and networking mode of the T2000, appended with standards that the T2000 complies with, abbreviations and performance indices. Introduces configuration and maintenance operations of T2000. Introduces the installation procedure and FAQ of T2000 under the platforms of Windows 2000 Professional and Solaris 8. Contains all the above manuals in CD format.
OptiX iManager T2000 Operation Manual OptiX iManager T2000 Installation Manual OptiX iManager T2000 Electronic Documentation
Organization
Chapter Chapter 1 Brief Introduction Chapter 2 Application Description Introduces Huaweis solutions to the transmission NM as well as the position of T2000 and its manageable equipment. Introduces the networking structure when T2000 is interconnected with the transmission network equipment and other transmission NMs in the network. Introduces the main functions, main windows and new characteristics of this version. Introduces the hardware structure, external interfaces and configuration requirements of the T2000. Introduces the reliability design scheme provided by the T2000.
Chapter 3 Functional Characteristics Chapter 4 System Architecture Chapter 5 Reliability Design
Huawei Technologies Proprietary vi
OptiX iManager T2000 System Description Chapter Chapter 6 Performance Indices Appendix A Standards Followed Appendix B Abbreviations Description
About This Manual
Introduces the performance indices and calculating methods of management ability. Lists the standards that the T2000 complies with. Lists the abbreviations, acronyms and terms used in the manual.
Intended Audience
This manual is for the reader who wants to know the characteristics, application, structure and product specifications of the T2000 in general.
Conventions
The manual uses the following conventions.
Symbol Conventions
Symbol Warning Caution Important Note: Note: Description A warning notice with this symbol indicates a potentially hazardous situation in which there is a possibility of personal injury. A caution notice with this symbol indicates a risk to equipment damage or loss of data. An important note notice with this symbol helps you avoid an undesirable situation or indicates important supplementary information. A note notice with this symbol indicates additional, helpful, non-critical information.
GUI Conventions
Convention <> [] / Description Button name are inside angle brackets. For example, click the <OK> button Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window. Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].
Huawei Technologies Proprietary vii
About This Manual
Keyboard Operation
Format <Key> <Key1 + Key2> <Key1, Key2> Description Press the key with the key name inside angle brackets. For example, <Enter>, <Tab>, <Backspace>, or <A>. Press the keys concurrently. For example, <Ctrl + Alt + A> means the three keys should be pressed concurrently. Press the keys in turn. For example, <Alt, A> means the two keys should be pressed in turn.
Mouse Operation
Action Select Click Double-click Drag Description Press and hold the primary mouse button (left mouse button by default). Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Huawei Technologies Proprietary viii
1
1.1 Position in TMN Hierarchy

Brief Introduction
With integrated management application platform (iMap), iManager series NMs developed by Huawei aim at respective functional domains and customer groups of the telecommunication network. Huawei provides total solution for the network management of the transmission network, including: OptiX iManager T2000 (T2000 for short hereinafter) The integrated network management system for transmission network (sub-network level). OptiX iManager T2100 (T2100 for short hereinafter) The integrated network management system for transmission network (network level).
The T2000 is a subnetwork management system (SNMS). In the telecommunication management network (TMN) architecture, SNMS is located between the NE level and network level. So the T2000 supports all functions of NE-level and part of the network-level management functions.
Huawei Technologies Proprietary 1-1

Business management layer BMS
Service management layer
SMS
NMS Network-level management layer (iManager T2100)
Subnetwork-level management layer (iManager T2000)
SNMS
NE-level management layer EMS
EMS
GNE NE layer NE NE NE ... NE
GNE NE NE ... NE
GNE NE NE
Figure 1-1 The position of the T2000 in TMN
Note: T2100 belongs to network management system (NMS). It can manage SNMS or element management system (EMS).
1.2 Manageable Equipment

The T2000 can uniformly manage the Huawei-developed OptiX series optical transmission equipment in a multi-service transmission network. The OptiX series products include: Optical Switching Node (OSN), Synchronous Digital Hierarchy (SDH), Synchronous Optical Network (SONET) and Dense Wavelength Division Multiplexing (DWDM). Equipments specific to each category are listed below.
Category intelligent optical switching network (OSN) series Equipment OptiX OSN 9500 Intelligent optical switching system (called OptiX OSN9500 for short) OptiX OSN 3500 STM-16/STM-64 intelligent optical transmission system (called OptiX OSN 3500 for short) OptiX OSN 2500 STM-1/STM-4/STM-16 multi-service optical transmission system (called OptiX OSN 2500 for short) OptiX OSN 1500 compact STM-16/4 intelligent optical transmission system (called OptiX OSN 1500 for short) SDH series OptiX 155C SDH transmission unit for the access network (called OptiX 155C for short) OptiX 155S simplified STM-1 optical transmission system (called OptiX 155S for short) OptiX Metro 200 ultra compact STM-1 optical transmission system (called OptiX Metro 200 for short) OptiX Metro 500 ultra compact STM-1 multi-service transmission system (called OptiX Metro 500 for short) OptiX 155/622B STM-1/STM-4 compatible optical transmission system (19-inch rack) (called OptiX 155/622B for short) OptiX 155/622H integrated STM-1/STM-4 compatible optical transmission system (called OptiX 155/622H for short) OptiX 155/622H(Metro1000) STM-1/STM-4 MSTP optical transmission system (called OptiX Metro 1000 for short) OptiX Metro 1050 compact STM-1/STM-4 multi-service optical transmission system (called OptiX Metro 1050 for short) OptiX 155/622 STM-1/STM-4 compatible optical transmission system (called OptiX 155/622 for short) OptiX 155/622(Metro2050) STM-1/STM-4 compatible optical transmission system (called OptiX Metro2050 for short) OptiX 2500 STM-4/STM-16 compatible optical transmission system (called OptiX 2500 for short) OptiX 2500+(Metro3000) STM-16 MADM/MSTP optical transmission system (called OptiX Metro 3000 for short) OptiX 2500REG STM-16 regenerator (called OptiX 2500REG for short)
OptiX iManager T2000 System Description Category Equipment
OptiX Metro 1100 compact container STM-16 multi-service transmission system (called OptiX Metro 1100 for short) OptiX Metro 3100 STM-16 multi-service transmission system (called OptiX Metro 3100 for short) OptiX 10G STM-64 optical transmission system (called OptiX 10G for short) OptiX 10G(Metro5000) STM-64 MADM optical transmission system (called OptiX Metro 5000 for short) SONET series OptiX Metro 1600 compact container OC-48/OC-192 multi-service transmission system (called OptiX Metro 1600 for short) OptiX Metro 800 compact OC-3/OC-12/OC-48 multi-service transmission system (called OptiX Metro 800 for short) DWDM series OptiX Metro 6020 compact container WDM system (called OptiX Metro 6020 for short) OptiX Metro 6040 compact container DWDM system (called OptiX Metro 6040 for short) OptiX BWS 320G 16/32-channel DWDM optical transmission system (called OptiX BWS 320G for short) OptiX BWS 320GV3 16/32-channel backbone DWDM optical transmission system (called OptiX BWS 320G V3 for short) OptiX BWS 1600G 160-channel backbone DWDM optical transmission system (called OptiX BWS 1600G for short) OptiX Metro 6100 DWDM multi-service transmission system (called OptiX Metro 6100 for short)
2 Application
2
2.1 Single-Layer Management Network
Application
The T2000 provides the users with single-layer management network solutions to the small & medium-sized transmission networks. Meanwhile, it works in combination with the upper-level NM (the T2000 provides standard external interfaces for the upper-level NM) to compose a multi-layer management network, so as to assist network layer management system and service layer management system in managing large-scale transmission network.
Single-layer management network means that one transmission network is under the management of a single-layer NM. That is, the entire management network only includes the NEs and NE-level management systems (or subnet management systems). The networking mode is shown in Figure 2-1.
Note: Single-layer management network does not mean that there is only one NM in the entire network.
2 Application
T2000
... ...
T2000
OptiX network
OptiX network
Figure 2-1 Networking of single-layer management network
Note: Refer to Chapter 4 System Architecture for its internal networking mode.
T2000 provides two schemes of remote maintenance. The hardware connections are the same, as shown in Figure 2-2, while the software is different.
Table 2-1 Difference in software used in two remote maintenance schemes
Scheme 1 2
Software on the remote maintenance terminal The T2000 remote client Navigator
Software on the central NM The T2000 server RAS
Remote maintenance terminal
Serial port
Modem
PSTN Serial port
Modem
Central NM
Figure 2-2 Hardware connection of remote maintenance scheme
2 Application
2.2 Hierarchical Management Network

Hierarchical management network means that the transmission network is managed via the NM with two or more layers. That is, the entire management network includes three or more layers, such as NE-level management systems (or subnetwork management systems) and network-level management systems. The typical networking mode is shown in Figure 2-3.
T2100
DCN
T2000
T2000
The T2000 and T2100 can be connected through LAN or WAN. The T2000 is interconnected to T2100 through MML interface. Figure 2-3 Networking of hierarchical management network
The hierarchical management network has such advantages:

Improved management capability The capacity of network management is improved through hierarchical management. Unified NM Separating NE management and network management functions Meeting requirements for operation & maintenance mechanism of operators

2. Connecting upper-level NM through LAN
The nearby T2000 server and NMS server can be directly connected through LAN, as shown in Figure 2-4.
2 Application
T2000 client1
T2000 clientN
......
NMS
T2000 server
Figure 2-4 Hierarchical networking structure realized through LAN
3. Connecting upper-level NM through WAN
The distant T2000 server and NMS server can be directly connected through WAN, such as digital data network (DDN), 2M private line, integrated services digital network (ISDN) and public switched telephone network (PSTN), as shown in Figure 2-5.
T2000 client1
T2000 clientN
......
NMS
DDN, 2M, ISDN, PSTN T2000 server
Figure 2-5 Hierarchical networking structure realized through WAN
3
3.1 Main Functions

Functional Characteristics
The T2000 not only supports all management functions of NE layer (fault management, performance management, configuration management, security management, communication management, topology management and system management), but also supports part of management functions of network layer, as shown below: End-to-end trail management End-to-end service maintenance Unified network resource management through protection subnet Network-wide data communication network (DCN) management
Users can get part of the network-level management functions only with an investment in element-level NM, thus achieving a higher cost-effectiveness.
3.1.1 Alarm
1. Browse alarms

View, filter, print current and history alarms, and delete current alarms. Query the history alarms from the NEs. Acknowledge (manually or automatically) and verify the current alarm. View the information of alarms at all levels through the toolbar. Display the alarm information on the topology. View and filter abnormal event. Browse alarms generated in protection channel. Save alarm filtering conditions. Set NE alarm attributes. NE alarm recording mode, inversion mode, correlative suppressing switch (NE layer), delay switch, and alarm delay time. Set alarm correlation analysis switch (network layer). Set the analysis rules of alarm correlation. Huawei Technologies Proprietary 3-1
Before browsing an alarm, the following need to be set:

The default rule is provided by the T2000.

Set alarm. Include alarm severity, suppression status, automatic report status, filtering status, port alarm inversion status and asynchronous transfer mode (ATM) connection alarm suppression status. Customize NE attribute templates (up to 16). Set the switch of automatically acknowledged alarms.

2. Synchronize alarms
The T2000 can manually or automatically synchronize the alarm data between NEs and the T2000.
3. Get alarm statistics
Get the statistics of alarms at all levels and the un-ended alarms.
4. Dump alarms
Save the alarm data as file automatically or manually. For automatic dumping, conditions for the alarm overflow dump, periodical dump, and position for saving the dump file should be set in advance.
5. Clear alarms
Clear the NE alarms. Clear the current NE alarm data saved on the NE and the T2000. Clear the alarm indications on the rack of NE.
6. Send the alarm messages out of the T2000
After receiving alarms, the T2000 can automatically send maintenance engineers a certain telephone number by pager; or the statistics of all level alarms by short message of mobile phone (up to now, only Nokia mobile phones are supported ); or the details of a critical alarm and the statistics of all level alarms by email. Users can choose a suitable mode to send alarms out of the T2000. The following should be set in advance:

The user names of maintenance engineers (up to 15 maintenance engineers ) The pager numbers, mobile phone numbers, or email addresses of maintenance engineers The alarm filtering conditions Include alarm severity, alarm type, and related equipment. The number of serial port connected to Modem and the mail servers address Nokia connection manager

This function can help the maintenance personnel learn the equipment fault information as soon as possible.
7. Fault diagnosis
With the wizard, 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 following should be preset: diagnosis rules and the alarms allowed to be diagnosed. The T2000 has default fault diagnosis rules. Users may add, delete or modify these rules by experience. Huawei Technologies Proprietary 3-2
OptiX iManager T2000 System Description 8. Insert alarms
Manually insert an alarm into a service to help users locate the fault point.
3.1.2 Performance Monitoring

1. Customize performance threshold template
The T2000 provides default performance threshold templates. Users can customize new threshold templates (up to 16 threshold templates can be supported).
2. SDH/DWDM performance monitoring

Reset the NE performance register. Preset the following before performance monitoring starts. Include performance event threshold, performance monitoring object, start & stop time for performance monitoring, timely UAT prompt, and timely threshold crossing event prompt. Browse performance event. Include current performance data, history performance data, UAT, and threshold crossing event. Analyze history performance data. Medium & long-term forecasts on performance. Work out the empirical formula according to history performance data of the optical transceiver. If performance data is given, the formula can be used to calculate the time (with deviation range) for generating this performance; if time is given, the performance data at that time(with deviation range) can be calculated. Dump performance data. Save the performance data as file automatically or manually. Before automatic dumping, conditions for the overflow dump, periodical dump and immediate dump, and the position for saving the dump file should be set in advance. Reset ATM performance register. Set ATM performance monitoring parameters. Include performance monitoring period, and start & stop time for performance monitoring. Monitor ATM port performance. Include monitor the ATM port performance in real time, and browse the ATM port history performance data. Dump performance data. Reset Ethernet performance register. Set Ethernet performance monitoring parameters. Include monitoring status, monitoring period, and start & stop time for performance monitoring. Monitor Ethernet port performance. Include monitor Ethernet port performance in real time, and browse Ethernet port history performance. Support two browse modes. Huawei Technologies Proprietary 3-3

3. ATM performance monitoring

4. Ethernet performance monitoring

Graph and list.

Monitor Ethernet RMON performance. Dump performance data. Reset the NE performance register. Preset the following before performance monitoring. Include performance event threshold, performance monitoring object, and timely threshold crossing event prompt. Browse performance event. Include current performance data, history performance data, UAT, threshold crossing event. Analyze history performance data. Dump performance data. Save the performance data as file automatically or manually. Before automatic dumping, conditions for the overflow dump, periodical dump and immediate dump, and the position for saving the dump file should be set in advance.
5. SONET performance management

3.1.3 Configuration of NE Layer

The configuration management of the T2000 includes the configuration of NE layer and that of network layer. The configuration of NE layer includes:
1. Common configuration
NE attribute Query NE attribute, modify NE name or remarks. NE time synchronization Send the computers system time of the T2000 server to all the NEs for synchronization. Automatic synchronization of NE time can also be set. NE hardware information View information such as NE resource, board resource, subrack resource, board resource statistics, and so on. NE board information View the logical and physical boards in each slot of the NE. Board version information View the BIOS version and NE software version of the actual boards in the slots on the NE. Physical location information Enter and view information about the equipment room, cabinet and subrack where the NE is. Environment monitor information Set PMU interface, EMU interface, CAU interface, and fan speed of NE Virtual NE management Create virtual NE, add board to virtual NE, create fiber connecting virtual NE and other NEs, create SDH service in virtual NE, create protection subnet as well as search and create trails.
OptiX iManager T2000 System Description 2. SDH configuration

Set SDH interface board. Query and set the SDH interface boards installed on NEs. Set the parameters of SDH interfaces. Set the parameters of plesiochronous digital hierarchy (PDH) interfaces. Set overhead interfaces. Include order wire, hotline number, special line number, conference call number, subnet number length, F1 data port, broadcast data port, communication port, data port and out-ring route, and so on. Set optical amplifier board interface. Set tone & data access (TDA) interfaces. Include TDA clock source and TDA power feeding. Configure clock. Query clock synchronization status, set clock source priority table, set clock source recovery parameters, set clock source switching conditions, query clock source switching status, set external clock output phase-locked source, configure clock subnet, and provide clock subnet view Configure Board protection. Set board 1+1 hot backup, set tributary protection switching (TPS) protection (1:N), and manage TPS protection groups. Configure VC12, VC3 (Used for interconnection with SONET service, transparently transmiting SONET STS-3 service via SDH), or VC4 services. Configure AU-4c, AU-8c, AU-16c, or AU-64c cascaded service. Configure and control sub-network connection (SNC) service. Configure and control sub-network connection multi-trail protection (SNCMP) service. Activate or deactivate service. Set service loading status. Manage overhead byte. Query and set overheads, such as: regenerator section overhead (J0), lower order overhead (V5, J2), VC4 higher order overhead (J1, C2) and its pass-through or termination, VC3 higher order overhead (J1, C2), the trace bytes (J0, J1 and J2), the label byte C2, low-order channel trace byte V5 and VC4 overhead byte pass-through or termination. Interchange between common service and SNC service. Configure REG. After the line board is set as REG hardware on the T2000, every pair of optical interfaces of the line board provide special receive/transmit function. Via 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 & communication unit and cross-connect unit. Configure the board. Huawei Technologies Proprietary 3-5

3. SONET configuration
Install board, query the installed board, reset board, save or clear the configuration of board.

Set optical amplifier automatic level shutdown. Set the parameters of line unit. Include optical amplifier on/off switch, in service or out of service for optical port, loopback mode of optical port, cross-connect loopback, whether the path is used, output gain of path, signal code type, signal frame type, (query) the V5 byte received, and enable/disable to send overhead byte. Configure the cross-connection. Configure the clock. Configure unidirectional protection switched ring (UPSR). Include UPSR protection group, hierarchy of switching, interchange between normal service and special service, V5 byte to be received, and V5 byte received. Configure 1+1 linear automatic protection switching (APS). Create or delete linear APS protection pair, set linear APS wait-to-restore (WTR) time, start/stop linear APS protocol, query switching status. Configure bidirectional line switched ring (BLSR) protection. Create and delete BLSR protection pairs, query and initialize the Ring Map, set the WTR time, set the switching mode, query the switching status, perform the external switching operation, query or initialize the squelch table. Set the 1+1 protection of cross-connection board. Set TPS of tributary board. Interchange between common service and UPSR service. Configure DWDM board interface. Configure DWDM overhead interface. Include order wire telephone, F1 data port, conference call, broadcast data port, subnet number length, and outgoing subnet connection. Set board clock source. Configure clock transparent transmission and protection. Set optical line protection (OLP) protection. Set optical path protection (optical wavelength protection). Manage the optical power. Support coarse wavelength division multiplexing (CWDM). Query wavelength division types of boards, query and display CWDM wavelength, and wavelength of CMR1 and CMR2 added/dropped. Install ATM interface board. Set ATM interface parameters. Set management of ATM traffic. Configure ATM services. Create network-network interface (NNI) on the ATM processing board, configure ATM cross-connect, configure ATM protection group, configure ATM protection Huawei Technologies Proprietary 3-6

4. DWDM configuration

5. ATM configuration

pair, configure ATM service from ATM board to SDH line, activate or deactivate ATM cross-connect.
6. Ethernet configuration

Install and set Ethernet interface board. Configure Ethernet service transparent transmission. Configure fast Ethernet transparent transmission board and Ethernet service transparent transmission priority. Configure Ethernet transparent transmission service. Configure Ethernet layer-2 switching services. Include virtual local area network (VLAN) filtering table, media access control (MAC) address-port forwarding table, service type, and message priority classification mode. Configure private line services. Include Ethernet private line (EPL) and Ethernet virtual private line (EVPL). Configure LAN services. Include Ethernet private LAN (EPLn) and Ethernet virtual private LAN (EVPLn). Configure other features of Ethernet. Include CAR function, IGMP Snooping management, VPLS, LSP and attachment management, flow classification management, link-state pass through (LPT) management, QoS management. Test frame receiving and transmitting on Ethernet transparent transmission board (EGT), 2-port Ethernet electrical interface board (VC-3) (ET3D), 1-port Gigabit Ethernet optical interface board (VC-4) (GF4S), and 2-port gigabit Ethernet optical interface board (VC-4) GF4D, and so on. Manage Ethernet users. Configure ESCON service. Configure 64K services. Include TDA board service, N 64K service. Configure DSL service. Initialize the configuration data. Upload or download the NE configuration data. Check configuration data consistency. Copy NE configuration data. Import or export script file of configuration data. Backup NE database. Backup board data. Configuration data upgrade wizard. Set NE communication parameters. Include ID of NE, IP address, extended ID, gateway NE IP address, and subnet Huawei Technologies Proprietary 3-7

7. Configuration of other services

8. Management of configuration data

9. Configure NE communication parameters

mask.

Set extended embedded control channel (ECC) parameters. Manage ECC link. Set data communications channel (DCC) access control. Set the method the T2000 (or the T2000-LCT) accesses NE. Include by Ethernet port or by COM port. Set DCC access. New features of D overhead bytes. D1~D12 bytes can all be used in DCC communication, providing the DCC rate of 192kbit/s~768kbit/s. The following D bytes used by DCC channel can be set: three bytes (D1~D3 or D7~D9), nine bytes (D4~D12) or twelve bytes (D1~D12). 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. The overhead information of other vendor's equipment can also be transparently transmitted by configuring overhead bytes cross-connection, without being processed by the NE software.

3.1.4 Configuration of Network Layer

The configuration management of the T2000 includes the configuration of NE layer and that of network layer. The configuration of network layer includes:
1. Protection subnet management
Create protection subnet. Include two-fiber bidirectional Multiplex Section (MS) shared protection ring, two-fiber unidirectional MS dedicated protection ring, four-fiber bidirectional MS shared protection ring, two-fiber unidirectional PP ring, two-fiber bidirectional PP ring, dual node interconnection (DNI), linear MSP (1+1, or M:N), unprotected ring, unprotected chain. Search protection subnet. Search for the information of NEs and cables in the data of the T2000 NE layer to get the complete information of the protection subnet. View all the isolated nodes. View the description for the protection subnet resource. View and set the switching status of the protection subnet. Set the wait-to-restore time(WTR) and the trigger condition. Start or stop the MS protection protocol of the protection subnet. Starting and stopping network-wide MS protection protocols at the same time. Set and browse NNI. Set NE as gateway network element (GNE) or non-GNE. Set restore mode. Test NEs. Provide 1:N (N 3) protection to GNE. IP over DCC. Huawei Technologies Proprietary 3-8

2. DCN protection

The IP protocol is used for the communications between the T2000 and all NEs and the communications among all NEs. The T2000 has TCP connections with all NEs, which are all GNEs. The original DCC mode coexists.
3. Trail management
Fast create trail. Create the SDH trail in one page. The service level includes: E1, E3, E4, T1, T3, STM-1, VC4, VC4-4c, VC4-8c, VC4-16c, and VC4-64c. Create trail step by step. Guided by the wizard, the user can create the trail automatically or semi-automatically step by step. The service level includes: E1, E3, E4, T1, T3, STM-1, VC4, VC4-4c, VC4-8c, VC4-16c, and VC4-64c.
Note: The semi-automatic creation means that user can specify the timeslots along the route as required during route creation. While, the full-automatic creation means that the system automatically selects one best route during the creation.
Create trail in batches. If Copy after creation is selected in the configuration wizard for trail creation or wizard for fast trail creation, it will automatically switch to the Copy trail dialog box after the creation. Thus fulfill the batch creation through trail copy. Create Ethernet trail. Create Ethernet trail in the wizard mode, including Ethernet transparent transmission service, Ethernet leased line service (EPL, EVPL) and Ethernet VLAN service (EPLn, but not the EVPLn service for the time being). Before creating an Ethernet service, you need to create Trunk Link. Search for trail. On the basis of the NE configuration data, fiber connection information saved in the NE-layer data of the T2000, or even the protection subnet information in the network-layer data, the T2000 can generate the information about end-to-end trails, including SDH trails, wavelength trails, and Ethernet trails. Manage end-to-end wavelength trail. Filter the trail (including SDH trail, Ethernet trail and wavelength trail) list. There are three modes for filtering: full filter (i.e., filter and display all the trail data according to the set conditions), secondary filter (i.e., filter and display the currently displayed result according to the conditions) and incremental filter (i.e., filter all the trail data according to the filtering condition, and then display them together with the currently preserved result as a union). Customize the trail view. The user can filter the trail view according to NE and saves it as a customized trail view. By calling different customized trail views, the user can search the concerned contents rapidly among multiple NEs and trails. The customized view created by one user can be used by all users. This function is suitable for managing large-scale networks with multiple NEs and trails. Copy, delete, activate and deactivate the SDH trails in the list. Huawei Technologies Proprietary 3-9


Delete, permanently delete, activate and deactivate the Ethernet trails in the list. View the related current or history alarms on the specific SDH trails. Provide alarm shielding and alarm reverse for the specific SDH trails. Set and view performance parameters of the SDH trail and wavelength trail. View the current and history performance data and unavailable time of the trails. Insert alarms into trails of MS and VC4 levels, such as AIS and RDI. Set loopback on any nodes on the SDH trail and Ethernet trail, including VC4 loopback, tributary loopback and optical interface Loopback. Perform pseudo-random binary sequence (PRBS) test on the trail. Set overhead pass-through or termination on the trail. Set and query the overhead bytes on the trail uniformly, including the trace byte and signal label byte C2.Prompt users to configure trace bytes when timeslot out-of-sequence occurs to the MS. Modify the trail in-service. When a fault occurs to the equipment, modifications shall be made to the trails in-service to avoid the faulty point and keep the traffic unblocked. Such modifications include modifying the upper and lower ports of the trail, adjusting the original route partially, changing the NEs or boards the trail passes and modifying the timeslot occupied by the trail. Currently, these modifications are supported for trails at E1, E3 and E4 levels only. View the detailed information of the trail. Include the attributes, channel allocation, and so on. Query relevant trails of the current trail. Include the SDH trail, Ethernet trail and wavelength trail. Statistics of trail resources. Provide the statistics of trails between NEs, statistics of tributary port resources, statistics of timeslot resources of protection subnet, and statistics of wavelength resources. Manage trail users. Create and maintain user information. Query and view the network-wide clock synchronization status. Clock trace search. Output clock trace chart. Enable or disable clock status change prompting.

4. Network-wide Clock Management

3.1.5 Security
The security management of the T2000 includes the NM security management and the NE security management.
1. NM security management
Management of NM users The system administrator can create other users, specify the user name and password, allocate the user group to which it is subordinate, and slightly adjust the users rights. It involves equipment set management, operation set management, Huawei Technologies Proprietary 3-10
user group management, and user management.

Management of remote maintenance user Set the levels of remote maintenance users (including configuration and view authorities) and whether the access is allowed or not. Other control modes Change user, switch between the single-user mode and multi-user mode, lock the screen, and force the user to quit. Management of NE users Management of NE logon Lock of NE logon Lock of NE configuration Control on local craft terminal (LCT) access
2. NE security management

3.1.6 Maintenance
The Maintenance Status icon on the toolbar To display whether such operations have been done on the equipment: loop back (only supports SDH loopback status display at present), laser shutdown, path loading, alarm shielding, alarm insertion, alarm inversion, and so on. Loopback Include tributary loopback, VC4 loopback, optical/electrical interface loopback, ATM interface loopback, Ethernet interface loopback and ESCON interface loopback. Laser maintenance Include On/off status of SDH laser, Automatic Laser Shutdown, laser performance threshold, on/off status of DWDM laser, laser performance analysis and on/off status of Ethernet laser. Software and hardware reset of the board Board 1+1 active/standby switching Tributary Protection Switching Query current temperature of the board Query and set the upper and lower limits of the temperature value for the board. Upgrade the cross-connect board Change and upgrade the active and standby cross-connect board types in the wizard mode. 2M PRBS test Insert PRBS at the 2M port and test the bit error rate of the signal at the transmitting end after it is looped back from the peer end. If there is no BER tester, short-term and in-service test can be performed on 2M tributary board. This operation will interrupt services. Tandem connection measurement (TCM) In some cases, an operator needs to rent other operators network for service transmission (for example, when there is no self-owned optical cable available in a specific region), then the TCM can be used to correctly test the performance of the leased line. TCM is conducted on the NEs interconnected with leased network. Huawei Technologies Proprietary 3-11


Test receiving and sending of frames on Ethernet boards SNC control SNC service control and SNCMP service control. Set intelligent power adjustment (IPA) Set the automatic level control (ALC) Support wave-number detection (MCA needed) and power control (MCA not needed). Set the automatic power pre-equilibrium (APE) Support optical fiber (cable) line automatic monitoring system (OAMS) Through the OAMS function, the tests can be performed for the optical fibers (being used or reserved) of WDM equipment in multiple modes. It provides optical fiber aging alarm, preliminary location of link optical fiber faults and link fault alarm functions. This function can improve the alarm function of the transmission equipment and maintainability of the transmission network. Automatic disabling of NE function Set automatic canceling of operations like loopback, laser shutdown, and alarm insertion, and select the time for automatic canceling. This function can prevent the service from being affected in case those operations are not canceled in time. Collect equipment data The T2000 can remotely collect the NE data under failure in order to diagnose the fault. Expansion wizard In several cases during the network expansion, the T2000 will provide a wizard to guide users through the process of smooth expansion or reconstruction. If more extended subracks are needed to expand the add/drop capability of the tributary, the boards on the main subrack can be moved to the extension subrack. The T2000 will guide users to re-calculate, adjust and send related services. If it is necessary to move the board, related services will be automatically adjusted and sent through the wizard of the T2000.If a node is to be added into the multiplex section protection (MSP) subnet, for smooth upgrade of the newly added MS node, the T2000 will do the following: automatically calculate the logic system configuration and service configuration of the new node; implement forced switching to the subnet (to protect the service from being interrupted during the expansion); send the configuration data; modify the MS node information, and start the MS protocol. This function only supports the operation of a single user. Configure data upgrade wizard After the T2000 software is upgraded, the user can restore the original data on the new T2000 under the guide of the wizard.

3.1.7 Report
The T2000 supports reports as follows:

Table of network-wide data Slot configuration and version Fiber & cable connection table Wavelength resource distribution report Equipment information report SDH timeslot assignment diagram Huawei Technologies Proprietary 3-12

NE timeslot configuration report SDH trail configuration report Wavelength trial configuration report Ethernet trail report Ethernet trail configuration report Network chart Clock trace chart
3.1.8 Topology Management

Topology management includes: creation of the topology objects, subnet management, fiber & cable management, search for the network equipment, etc.
3.1.9 Log Management

Log management of the T2000 includes log browse and log dump.
3.2 Main Interfaces

The T2000 mainly supports the following interfaces:

Main topology view Equipment maintenance console Protection view Trail view Clock view DCN view
3.3 New Characteristics

1. Support new equipments

OptiX OSN 1500 OptiX Metro 800 EFT board of OptiX Metro 500 Supporting the transparent transmission of 10M/100M Ethernet service. GE06 board of OptiX OSN 9500 Supporting transparent transmission of 1000M Ethernet service, LPT and frame test.
2. Ethernet end-to-end trail function
The function supports end-to-end creation and management of the Ethernet service, including Ethernet transparent transmission service, Ethernet dedicated line service (EPL and EVPL services), Ethernet LAN service (Supports the EPLn service, but not the EVPLn service for the time being). Before creating an Ethernet service, you need to create the Trunk Link. This function supports end-to-end alarm management, performance management. At present, this function does not support QoS management for the Ethernet service.
3. The BLSR function of the SONET equipment
The BLSR characteristics supported by this version are listed below.

In case of a single-point failure, it recovers all the services. In case of a multi-point failure, it recovers some of the services. Through the squelch table, it guarantees that no misconnection of services will occur during protection switching. It supports the protection switching initialization standard defined in the ITU-T recommendation. It supports extra services.
BLSR supported by this version of the T2000 has the following operations: Create or delete BLSR protection pairs, query or initialize the Ring Map, set the WTR time, set the switching mode, query the switching status, perform the external switching operation, query or initialize the squelch table.
4. ALC
Besides the original ALC characteristics, the T2000 supports new ALC solutions: Supports automatic regulation without MCA, with the original ALC solution compatible. The new ALC solution has two working modes: wave number detection and power control, of which wave number detection is the original mode needing MCA.
5. IP over DCC
The IP protocol is used for the communications between the T2000 and all NEs and the communications among all NEs. The T2000 has TCP connections with all NEs, which are all GNEs. The original DCC mode coexists.
6. ROME Text Export
The T2000 NE data are exported in ROME text files and stored in the specified Huawei Technologies Proprietary 3-14
directory on the T2000 server. The T2000 can export the ROME text files at a scheduled time, that is, it automatically exports data at a specific time without personal intervention. Export NE data in the T2000 only NE data need to be managed through ROME database.
4

System Architecture
The T2000 provides multiple schemes as required: Standard client-server architecture Extended Structure of Multiple Servers High-availability (HA) system structures
4.1 Standard Client-Server Structure

4.1.1 Hardware Connection
The T2000 client and server can run on different computers in client-server structure, as shown in Figure 4-1, or run on the same computer, with each server able to access multiple clients. The server and client computers can be PCs or Sun workstations, and the display of T2000 screen on different operating systems is exactly the same.
......
T2000 client1
T2000 clientN
T2000 server
Figure 4-1 Hardware connection-client-server structure
Up to eight clients can be accessed to one server and operated 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. The maximum number of clients Huawei Technologies Proprietary 4-1
connected to different servers is shown in Table 6-2 Management capability of different hardware platforms.
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 network-wide. The client of the T2000 implements workstation function (WSF) of TMN for users to operate and manage the transmission network. The server of the T2000 implements operating system function (OSF) of TMN, saving network data and providing various management functions for the transmission network. [WSF and OSF] WorkStation function (WSF) is a concept relating to the TMN architecture: providing the conversion between the information of TMN and the information that can be understood by users. Operations system function (OSF) is a concept relating to the TMN architecture: processing the information about the telecommunication management, so as to monitor and control the telecommunication functions (including the management function).
4.1.2 Function Modules
GUI Application modules Database Adaptation layer iMap platform GUI
Interfaces Server Client
Figure 4-2 T2000 functional modules
Table 4-1 Description of the T2000 functional modules
Module name Graphic User Interface iMAP platform Application modules
Function description Serving as the client Including graphical user interface (GUI) frame and common modules Including fault management module, performance management module, configuration management module, and security management module. All modules are constructed on the basis of iMAP platform. Accomplishing database management. Adapting to different NE protocols, shielding host version and function difference, providing unified and consistent interface for upper-layer application, and expanding external interfaces (such as MML) and access. The interface between NM and gateway NE.
Database Adaptation layer
Interface
4.1.3 Configuration Requirement
Note: The software and hardware running environment required by the T2000 undergoes strict type selection and test. Please configure the T2000 computer according to the following requirements.
1. Server
Table 4-2 Configuration requirement-OptiX iManager the T2000 server (Unix)
Description Blade 2500-2x1.28GHz-2G-2x73G-DVD-18 Inch LCD-English Document-Configuration Sheet SUN Fire V880-4x1.2GHz-8GB-6x73G-Network adapter-20G 4mm tape driver-17-inch display - No OS-No service-English document-USB keyboard/USB mouse-A configuration table Operation system - Sun Solaris 8 - English -English Document Database- Sybase Adaptive Server-12.0-For Sun Solaris 2.x-English-English documentation Software package-OptiX iManager T2000- UNIX network management system software package iManager T2000 Server adapter component
Quantity 1 1
Remarks Required. Select one from the two schemes. Required Required Required Required
1 1 1 1
Table 4-3 Configuration requirement-OptiX iManager T2000 server (Windows)
Description Desktop-P4 2.4G or above-512M-40G-Floopy disk- DVD- Integrated network adapter- Sound box-19-Inch Pure Flat Display- English-Windows 2000 Pro.-V92 Inside Modem PC Server-P4 PE6600-4xXeon 1.9GHz or above-4x1G-3x36G -FDD-DVD-PERC3/DC-DDS4 internal tape drive-19-inch pure flat display/Vertical /Windows 2000 Server (5 users)-3-year 5x8 service-Documentation-3x600W-External Modem-Keyboard and mouse HP Workstation-xw6000-2xP4 Xeon 2.4GHz or above-1GB-2x36GB-DVD-Quadro4 380XGL Video adapter-21-inch pure flat monitor- Windows 2000 Professional- Audio adapter- Speaker Database-MS SQL Server 7.0 Software package-OptiX iManager T2000-Windows network management system software package iManager T2000 Server license component
Quantity 1
Remarks Required. Select one from the three schemes.
1 1 1
Required Required Required
OptiX iManager T2000 System Description 2. Client

Table 4-4 Configuration requirement- OptiX iManager T2000 client (UNIX)
Description Workstation- Blade 2500-1.28GHz-1G-73G-DVD-18 Inch LCD-English Document-Configuration Sheet Operation system-Sun Solaris 8-English-English documentation Software cost-iManager T2000-UNIX client software
Quantity 1 1 1
Remark Required Required Required
Table 4-5 Configuration requirement-OptiX iManager T2000 client (Windows)
Description Desktop PC-P4 2.4GHz or above-512M-40G-FDD-DVD-Video adapter-Integrated network adapter- 10&100M network adapter- Audio adapter-Sound box-19-inch flat display-Vertical -English Windows 2000 Professional-110V,220V automatic switching HP Workstation-xw6000-2xP4 Xeon 2.4GHz or Above-1GB-2x36GB-DVD-Quadro4 380XGL Video Adapter-21-inch pure Flat Display- Windows 2000 Professional- Audio Adapter- Speaker Software cost- iManager T2000-Windows client software
Quantity 1
Remarks Required. Select one from the two schemes.
Required
4.2 Extended Structure of Multiple Servers

The management capability of the T2000 meets most demands. 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, as shown in Figure 4-3.
T2000 client1 T2000 client2
......
T2000 clientN
T2000 server1
T2000 server2
Figure 4-3 Hardware connection-Scheme of extending multiple servers
Through any client, the user can select to log in to any server to view, configure, and maintain the subnets managed by the server. By selecting the server to log in, the user can view and manage networks in a broader range. It should be noted that, by using this method, through single one client, the user cannot simultaneously view or manage subnets connected by two (or more) server. Therefore, if the user needs to manage a network with a broad range, hierarchical NM scheme shall be employed.
4.2.2 Software Structure

It is the same as the standard client-server software structure.
4.3 About the HA System

For better stability and risk resistance capability, the server adopts 1+1 or 1:N backup method with the clients connected with both the active and standby servers. Such a T2000 structure is called an HA system. The T2000-provided HA system includes the following solutions:

HA system (Sun Cluster), for local hot backup. HA system (Veritas), for remote hot backup. HA system (Watchman), for remote hot backup. Timely synchronization between the databases of the active and standby servers. Automatic switching of the application software on the active and standby servers.
The protection mechanism of an HA system lies in two aspects:

If the above two aspects can be realized, it is called hot backup.
4.4 HA System (Sun Cluster)

Cluster console Active server Ethernet1 SCSI port1 SCSI port2 Ethernet2 Sieral port Ethernet3 Disk array Sieral port SCSI port1 SCSI port2 Standy server Ethernet1 Ethernet2 Ethernet4 Terminal connector HUB DCN T2000 client2 T2000 client1
SCSI Cable Serial Cable Network sable
Figure 4-4 Hardware connection-HA system (Sun Cluster)

Active server T2000 server Sybase database Sun custer VxVM Solaris Standby server T2000 server Sybase database Sun cluster VxVM Solaris
T2000 client Java VM Solaris/Windows T2000 client Solaris Console
T2000 client Java VM Solaris/Windows T2000 client
Figure 4-5 Software structure-HA system (Sun Cluster)
4.4.3 Configuration Requirements
Note: HA System (Sun Cluster)s software/hardware running environment is strictly selected and tested. Please follow the requirements below.
1. Server
Table 4-6 Configuration requirement- HA system (Sun Cluster) Server
Description Netra20 dual-system-2x1.2GHz-2G-2x73G hard disk-2xdual-network-interface network adapter-Terminal with a Hub-dual StorEdge3310 (5x36G) arrays-DDS4 4mm tape drive-No monitoring terminal-No HA software-No service-English documentation-a configuration table Software package-OptiX iManager T2000- UNIX network management system software package Operation System - Sun Solaris8 - English -English Documentation Database- Sybase Adaptive Server-12.0-For Sun Solaris 2.x-English-English Documentation Application software-Sun Cluster-3.1-for SUN Solaris 8-English-with Volume Manager 3.5-English documentation-for Netra20 iManager T2000 Server license component
Quantity 2
Remarks Required
2 2 2 1 2
Required Required Required Required Required
OptiX iManager T2000 System Description 2. HA system Console

Table 4-7 Configuration requirement- HA system (Sun Cluster) console
Description Workstation-Blade 150-650MHz-1G-2x40G-CDROM-21-inch display-No operating system-English documentation-A configuration table Operation System-Sun Solaris8-English-English Documentation
Quantity 1 1
Remarks Required Required
3. T2000 Client
Please refer to the Table 4-4 and Table 4-5 in 4.1.3 Configuration Requirement.
4.4.4 Principles of Switching

Normally, the active and standby servers share the database data which are stored in the shared disk array. Within the system, all devices work in the active/standby mode. The terminal connector provides a logical IP address as the IP address of the T2000 server. When the active server fails, through the coordination of the Sun Cluster software, the standby server takes over all the tasks to keep the application program running efficiently.
4.5 HA System (Veritas)

Primary Secondary
Ethernet port 1
Ethernet port 2 2M line HUB Router
Ethernet port 1
Ethernet port 2
Router
HUB
DCN
GNE T2000 client SCSI cable Network cable
Figure 4-6 Hardware connection-HA system (Veritas)
Note: Here, the number of the Ethernet port is variable. V880 needs to configure two network cards and Blade 2500 needs to configure one network card only.

Primary T2000 server Sybase database GCO VCS VVR Solaris Secondary T2000 server Sybase database GCM GCO VCS VVR VVR, VxVM Solaris
T2000 client Java virtual machine Solaris/Windows T2000 client 1
... ...
T2000 client Java virtual machine Solaris/Windows T2000 client n
GCO VVR VCS
Global Cluster Option Veritas Volume Replicator Veritas Cluster Server
Figure 4-7 Software structure-HA system (Veritas)
Note: HA System (Veritas)s software/hardware running environment is strictly selected and tested. Please follow the requirements below.
1. Server
Table 4-8 Configuration requirement-HA system (Veritas) Server
Description Mini computer- SUN Fire V880-4x1.2GHz-8GB-6x73G-Network adapter-20G 4mm tape drive-17-inch display-No operating system-No service-English documentation-USB keyboard-USB mouse-A configuration table Blade 2500-2x1.28GHz-2G-2x73G-DVD-18 Inch LCD-English Document-Configuration Sheet Operation System-Sun Solaris8 - English -English documentation
Quantity 2
Remarks Required. Select one from the two schemes.
2 2 Required
OptiX iManager T2000 System Description Description Database- Sybase Adaptive Server-12.0-For Sun Solaris 2.x-English-English documentation Software package-OptiX iManager T2000-UNIX network management system software package iManager T2000 Server license component Tool software -Veritas remote backup software-(including VVR,VCS,GCO)-English documentation-A configuration table Quantity 2 2 2 2
4 System Architecture Remarks Required Required Required Required
2. T2000 Client

Normally, only the Sybase database application and T2000 application of the active workstation are started, while those on the standby T2000 server are not. Through the VVR software, bi-directional 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 or standby server will be copied to the other server in real time. When the active server fails, the system automatically starts the sybase database application and T2000 application of the standby server, switching the active server to the standby one.
4.6 HA System (Watchman)

Primary site Secondary site
Netw ork port 1
Netw ork port 2 2M dedicated line
Netw ork port 1 Lansw itch Router
Netw ork port 2
Lansw itch
Router
DCN Wathman client Wathman client
T2000 client
Figure 4-8 Hardware connection-HA system (Watchman)

Server (primary site) Watchman server application T2000 server Sybase database VxVM,VVR Solaris Server (secondary site) Watchman server application T2000 server Sybase database VxVM,VVR Solaris
Watchman client Java virtual machine Solaris/Windows Watchman client A
Watchman client Java virtual machine Solaris/Windows Watchman client B
T2000 client Java virtual machine Solaris/Windows T2000 client
T2000 client
... Java virtual machine

Solaris/Windows T2000 client
VVR VxVM
Veritas Volume Replicator Veritas Volume Manager
Figure 4-9 Software structure-HA system (Watchman)
Note: HA System (Watchman)s software/hardware running environment is strictly selected and tested. Please follow the requirements below.
1. Server
Table 4-9 Configuration requirement-HA system (Watchman) server
Description Blade 2500-2x1.28GHz-2G-2x73G-DVD-18 Inch LCD-English Document-Configuration Sheet SUN Fire V880-4x1.2GHz-8GB-6x73G-Network adapter-20G 4mm tape drive-17-inch display-No operating system-No service-English documentation-USB keyboard-USB mouse-A configuration table Operation system-Sun Solaris 8-English-English documentation Database- Sybase Adaptive Server-12.0-For Sun Solaris 2.x-English-English documentation Software package-OptiX iManager T2000- UNIX network management system software package iManager T2000 Server license component Physical software of the terminal -iMAP-Watchman software Tool software-VERITAS remote backup software-(with VVM,VVR,VCS)-English documentation-A configuration table
Quantity 2 2
Remarks Required. Select one from the two schemes. Required Required Required Required Required Required
2 2 2 2 2 2
2. HA System (Watchman) Client

Table 4-10 Configuration requirement-HA system (Watchman) client
Description Workstation-Blade 150-650MHz-512MB-1x40GB-DVD-1xnetwork adapter -Sound adapter Operation system - Sun Solaris 8 - English -English documentation Physical software of the terminal -iMAP-Watchman software
Quantity 1 1 1
Remarks Optional Optional Optional
3. T2000 Client

Normally, the application program runs on the active server, the VVR software copies the updated data of the active server to the standby server in real time, and the Watchman software monitors the data replication status. When the active server fails, the Watchman automatically starts the T2000 server software on the standby server.
4.7 External Interfaces

The communication interfaces between the T2000 and the external system are shown in Figure 4-10.
Other Vendor's NMS
T2100 MML CORBA T2000 Qx
Figure 4-10 External communication interfaces of the T2000
4.7.1 Qx
Qx interface is used between the T2000 and OptiX NEs.
4.7.2 MML
MML interface, one of the interfaces for NE-level NM and network-level NM, provides such functions 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 interface format of Huawei. With least overhead, MML interface is easy to use, but the disadvantage is that it is a specific standard of the suppliers instead of a standard of the industry. The T2000 with the standard configuration provides MML interface for information report, query and management of various operations.
4.7.3 CORBA
The CORBA interface is one of the universal standard interfaces in the telecommunication field. Through it, 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 CORBA interface provided by the T2000 is in compliance with recommendations TMF513, TMF608, and TMF814.
5
Risk Hardware failure Power failure of the T2000 computer Communication failure with gateway NE (fiber and cable fault, and gateway NE network interface fault) Computer hard disk or CPU fault at the server Software failure Database crash and network data loss
Reliability Design
The purpose of reliability design is to take some measures to reduce risk and enhance the running ability of products. The T2000 may encounter some risks when applied in the network. Although the probability is very low, measures should still be taken for the sake of safe running of the system.
Solution of the T2000 Use UPS power supply Start DCN protection first
Disk mirroring or HA system Timely backup database, dump database, copy database (one type of two-node cluster backup), or export configuration data to script HA system
The T2000 application software failure
5.1 HA System
Please refer to 4.3 About the HA System.
5.2 DCN Protection

The communication between NE (except GNE) and the T2000 is transferred by GNE. Active and standby GNEs can be preset for every NE on the T2000. When the communication between the active GNE and the T2000 fails, the T2000 will switch to the standby GNE automatically to ensure that the communication between the NE and the T2000 will not be interrupted. When the communication recovers, whether the active GNE is used again will be decided according to the restoration mode preset. The networking of DCN protection is shown in Figure 5-1:
T2000 client1 T2000 client2
HUB
T2000 server
DCN Router Router
Figure 5-1 Networking of DCN management network
The communication between the T2000 and the standby gateway can be accomplished via internal communication of transmission network, or via other DCN, for example, 2M private line, digital data network (DDN) private line, integrated services digital network (ISDN), public switched telephone network (PSTN), or Ethernet.
Note: Each gateway NE can support up to 50 non-gateway NEs (including using the extended ECC). Once the limit is exceeded, the number of gateway NEs should be increased. Each T2000 can support up to 62 gateway NEs. Once the limit is exceeded, extended ECC is recommended for combining some gateway NEs.
5.3 Disk Mirroring

If the server adopts Sun workstation and has more than two hard disks, disk mirroring can be installed together with the T2000. The T2000 employs Solatice DiskSuite software of Sun to provide disk mirroring scheme. Any change in data can be updated to two disks simultaneously. DiskSuite automatically monitors the running status of the disks. In case the working disk fails, the T2000 will be switched to the protection disk for data storage by command. Then replace the faulty working disk, and DiskSuite will automatically perform the re-mirroring of the working disk.
5.4 Data Backup

The security of network data is users concern. The T2000 provides the following solutions:
Data to be backed up Alarm log, abnormal event log, performance log, operation log and security log Configuration data Solution of the T2000 Dump database Operation description Operate on the T2000 client. See T2000 online help for details. Operate on the T2000 client. See T2000 online help for details.
Export them to scripts, adopting MML command format. The scripts can neglect the structural differences among databases of all the T2000 versions, suitable for data backup in the case of version upgrade. The scripts supported by the T2000 include network-wide configuration files, NE configuration files, NE port naming files, NE list files, NM computer information files and service implementation configuration files.
Database
Backing up database is to save managed object (MO) data to hard disk in the form of file. Backing up board data to flash database of the board. Backing up NE database is to back up NE data to the static databases of FDB0 and FDB1.
Operate on the T2000 client. See T2000 online help for details. Operate on the T2000 client. See T2000 online help for details. Operate on the T2000 client. See T2000 online help for details.
Board database
NE database
Note: For more detailed operations, please refer to the T2000 online help or Operation Manual.
6
6.1 Performance Indices
6.1.1 Alarm Capacity 6.1.2 Performance Capacity 6.1.3 Capacity of Other Logs
Performance Indices
It can manage 300,000 pieces of current alarms and 3,000,000 pieces of history alarms.
It can manage 3,000,000 pieces of history performance and the current performance is saved in the T2000 database.
For other logs that can be stored (including the operation log and system log), it can manage 300,000 pieces of logs.
6.1.4 CPU Utilization Status

Normally, no more than 10% of the CPU is used.
6.1.5 Response Speed of Alarm Handling

Normally, the time interval from the generation of an alarm on the equipment to its display on the T2000 is no more than 10 seconds.
6.1.6 Response Speed of Performance Handling

Normally, for 1,000 pieces of performance data, the time interval from report to being stored in the T2000 is about 10 seconds.
6.1.7 Time of Configuring a Circuit

Generally, it takes no more than 20 seconds to configure or delete a circuit.
6.1.8 Time of Searching a Circuit

Generally, it takes no more than 20 seconds to search a route.
6.1.9 Number of Users, Subnets and Links Managed by the System

The system supports the management of 255 users, 255 user groups, 255 equipment sets, and 255 function sets.
6.1.10 Time of Local Active/Standby Server Switching

It takes no more than 15 minutes to execute the switching of local active/standby server switching.
6.1.11 Time of Remote Active/Standby Server Switching

It takes no more than 15 minutes to execute the switching of remote active/standby switching.
6.1.12 Time of DCN Protection Switching

The time interval from judging the active gateway is unavailable to finishing the DCN protection switching is no more than 10 seconds.
6.1.13 Mean Time Between Failures (MTBF)

The MTBF is more than 6 months (The failure is defined as the crash of the database).
6.1.14 Mean Time to Repair (MTTR)

The MTTR is no more than 15 minutes (The failure is defined as the crash of the database)
6.2 Management Capability Calculation

The management capability of the T2000, on the basis of satisfying the prescribed performance indices, can be measured by the maximum number of NEs it manages. Currently, a set of the T2000 can manage up to 1000 155/622H NEs. This conclusion is drawn after the test under a certain environment and it reflects the management capability of the T2000 objectively. 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 shall take the following aspects into account.
The equivalence relationship between other types of NEs and 155/622H. Here, we shall consider the effect on the NM performance caused by the difference in the size of databases due to the difference in fiber quantity and service quantity of various NEs, as shown in Table 6-1. Different hardware platforms will affect the management capability of the T2000 inevitably. Generally, both the T2000 server and the T2000 client will be affected, as shown in Table 6-2. If the client runs at the server at the same time, its management capability will be reduced by 50%. Therefore, it is recommended that the client and the server be run separately. In this case, it is unnecessary to consider the effect on the management capability of the server caused by the client.

Table 6-1 Equivalent relationship between various NEs and OptiX 155/622H
NE OSN series OptiX OSN 9500 OptiX OSN 3500 OptiX OSN 2500 OptiX OSN 1500 SDH series OptiX 155C OptiX 155S OptiX Metro 200 OptiX Metro 500 OptiX 155/622B OptiX 155/622H OptiX Metro 1000 OptiX Metro 1050 OptiX 155/622 OptiX Metro 2150 OptiX 2500 OptiX Metro 3000 OptiX 2500REG OptiX Metro 1100 OptiX Metro 3100 OptiX 10G OptiX Metro 5000 SONET series DWDM series OptiX Metro 1600 OptiX Metro 800 OptiX Metro 6020 OptiX Metro 6040 OptiX BWS 320G OptiX BWS 320G V3 OptiX BWS 1600G OptiX Metro 6100
Equivalent coefficient to OptiX 155/622H 20 4.5 3.5 2.5 1 1 0.5 1 2 1 1 1.5 2 3.5 3 3 1.5 1.5 3 4 4 3 1.5 1 1 1.5 1.5 1.5 1.5
Table 6-2 Management capability of different hardware platforms
Hardware platform
Management capability coefficient 0.6 0.8
Maximum number of accessed clients 4 6
Blade 2500-2x1.28GHz-2G-2x73G-DVD-18 Inch LCD-English Document-Configuration Sheet SUN Fire V880-4x1.2GHz-8GB-6x73G-Network adapter-20G 4mm tape drive-17-inch display-No operating system-No service-English documentation-USB keyboard-USB mouse-A configuration table Netra20 dual-system-2x1.2GHz-2G-2x73G hard disk-2xdual-network-interface network adapter-Terminal with a Hub-dual StorEdge3310 (5x36G) arrays-DDS4 4mm tape drive-No monitoring terminal-No HA software-No service-English documentation-a configuration table PC server-PE6600-4xXeon 1.9GHz or above-4x1G-3x36G-FDD-DVD-PERC3-DC-DDS 4 internal tape drive-19-inch pure flat display-Vertical-Windows 2000 Server (5 users)-3-year 5x8 service-Documentation-3x600W-External Modem-keyboard and mouse HP Workstation- xw6000,2xP4 Xeon 2.4GHz or Above,1GB,2x36GB,DVD,Quadro4 380XGL Video Adapter,21-inch pure Flat Display, Windows 2000 Professional, Audio Adapter, Speaker Desktop PC-P4 2.4GHz or above-512M-40G-FDD-DVD-10&100M network adapter-Integrated audio adapter-Loudspeaker box-19-inch pure flat Trinitron display- Windows 2000 Professional-V90 internal Modem
0.5
0.6
0.2
Considering the factors stated above, the formulas for the management capability of the T2000 are as follows: Formula 1: Maximum number of managed 155/622H NEs = 1000 % management capability coefficient of hardware platform Formula 2: Maximum number of managed NEs = Maximum number of managed 155/622H NEs Equivalent coefficient to 155/622H
A Standards Followed
A
A.
Standards Followed
ITU-T G.707 ITU-T G.773 ITU-T G.774 (01, 02, 03, 04) ITU-T G.783 ITU-T G.784 ITU-T G.803 ITU-T G.831 ITU-T G0.851.1 ITU-T G.852.1 ITU-T G.852.2 ITU-T G.852.3 ITU-T G.852.6 ITU-T G.853.1 ITU-T G.853.2 ITU-T G.853.3 ITU-T G.853.6 ITU-T G.854.1 ITU-T G.854.3 ITU-T G.854.6
Network node interface for the synchronous digital hierarchy (SDH) Protocol suites for Q-interfaces for management of transmission systems Synchronous Digital Hierarchy (SDH) management information model for the NE view Features of SDH functional blocks Synchronous digital hierarchy (SDH) management Architecture of transport networks based on the synchronous digital hierarchy (SDH) Management capabilities of transport networks based on the synchronous digital hierarchy (SDH) Management of the transport network - Application of the RM-ODP framework Management of the transport network - Enterprise viewpoint for simple sub-network connection management Enterprise viewpoint description of transport network resource model Enterprise viewpoint for topology management Enterprise viewpoint for route management Common elements of the information viewpoint for the management of a transport network Sub-network connection management information viewpoint Information viewpoint for topology management Information viewpoint for trail management Computational interfaces for basic transport network model Computational viewpoint for topology management Computational viewpoint for trail management
Huawei Technologies Proprietary A-1
OptiX iManager T2000 System Description ITU-T M.3010 ITU-T M.3100 ITU-T M.3400 ITU-T X.720 ITU-T X.721 ITU-T X.722 ITU-T X.733 ITU-T X.903 Rational Unified Process 5.5 Sif99025 TMF513 TMF608 TMF814
A Standards Followed Principles for a telecommunications management network Generic network information model TMN management functions Management information model Definition of management information Guidelines for the definition of managed objects Information technology - Open Systems Interconnection - Systems Management: alarm reporting function Information technology - Open distributed processing - Reference Model: architecture Rational Unified Process EML-NML interface models Multi Technology Network Management Information Agreement Multi Technology Network Management Business Agreement Multi Technology Network Management Solution Set Conformance Document
Huawei Technologies Proprietary A-2
OptiX iManager T2000 Operation Manual
B FAQ
B
B.
Abbreviations
Abbreviation ACE ALC APE ASN.1 ATM BLSR BML CORBA CWDM DCC DCN DDN DWDM ECC EGT EML EMS EPL EPLn EVPL EVPLn FCAPS GCO
Explanation Adaptive Communication Environment Automatic Level Control Automatic Power Pre-equilibrium Abstract Syntax Notation One Asynchronous Transfer Mode Bidirectional Line Switched Ring Business Management Layer Common Object Request Broker Architecture Coarse Wavelength Division Multiplexing Data Communications Channel Data Communication Network Digital Data Network Dense Wavelength Division Multiplexing Embedded Control Channel Gigabit Ethernet Transparent Transmission Board Element Management Layer Element Management System Ethernet Private Line Ethernet Private LAN Ethernet Virtual Private Line Ethernet Virtual LAN Fault Management, Configuration Management, Accounting Management, Performance Management, Security Management Global Cluster Option
Huawei Technologies Proprietary B-1
OptiX iManager T2000 Operation Manual Abbreviation GNE GUI HA HTTP iMAP IP IPA ISDN ITU-T LCS LCT LPT MAC MCA MDI MDP Mgr MIB MIT MML MO MS NE NEL NML NMS OADM OAMS OCH Explanation Gate Network Element Graphical User Interface High-Availability Hyper-Text Transmission Protocol Integrated Management Application Platform Internet Protocol Intelligent Power Adjustment Integrated Services Digital Network International Telecommunication Union- Telecommunication Standardization Sector Leased Circuit Service Local Craft Terminal Link-state Pass Through Media Access Control Multi-channel Spectrum Analyzer Unit Multi-Document Interface Message Dispatch Process Manager Management Information Base Managed Object Instance Tree Man Machine Language Managed Object Multiplex Section Network Element Network Element Level Network Management Layer Network Management System Optical Add/Drop Multiplexer Optical fiber (cable) line Automatic Monitoring System Optical Channel
B FAQ
OptiX iManager T2000 Operation Manual Abbreviation OIF OSF OSI OSN OSNR PC PDH PSTN RAS RDBMS RS RUP SDH SIF SML SMS SNCMP SNCP SNML SNMS SONET TCM TCP/IP TDA TMF TMN TPS UML UPSR VLAN Explanation Optical Internetworking Forum Operation System Function Open Systems Interconnection Optical Switch Network Optical Signal-to-Noise Ratio Personal Computer Plesiochronous Digital Hierarchy Public Switched Telephone Network Reliability, Availability, Survivability Relational Database Management System Regenerator Section Rational Unified Process Synchronous Digital Hierarchy SONET Interoperability Forum Service Management Layer Service Management System Sub-Network Connection Multiple Protection Sub-Network Connection Protection Sub-Network Management Layer Sub-network Management System Synchronous Optical Network Tandem Connection Measurement Transmission Control Protocol/ Internet Protocol Tone & Data Access Unit Telecommunication Management Forum Telecommunication Management Network Tributary Protection Switching Unified Modeling Language Unidirectional Path Switched Ring Virtual Local Area Network
B FAQ
OptiX iManager T2000 Operation Manual Abbreviation UPSR VCS VPN VVR WSF Explanation Unidirectional Path Switched Ring Veritas Cluster Server Virtual Private Network Veritas Volume Replication Workstation Function
B FAQ

System Description

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

System Description

Transféré par

Droits d'auteur :

Formats disponibles

OptiX iManager T2000 System Description

Huawei Technologies Proprietary

OptiX iManager T2000 System Description

Huawei Technologies Co., Ltd.

Huawei Technologies Proprietary

Copyright 2004 Huawei Technologies Co., Ltd. All Rights Reserved

Huawei Technologies Proprietary

Updates in Manual Version 1.81

Updates in Manual Version 1.82

Huawei Technologies Proprietary

OptiX iManager T2000 System Description

Huawei Technologies Proprietary i

Huawei Technologies Proprietary ii

Contents 6-2 6-2 6-2 6-2 6-2 6-2 6-2 6-3

A Standards Followed B Abbreviations

Huawei Technologies Proprietary iii

OptiX iManager T2000 System Description

Huawei Technologies Proprietary iv

OptiX iManager T2000 System Description

Huawei Technologies Proprietary v

OptiX iManager T2000 System Description

About This Manual

About This Manual

Chapter 3 Functional Characteristics Chapter 4 System Architecture Chapter 5 Reliability Design

Huawei Technologies Proprietary vi

About This Manual

Huawei Technologies Proprietary vii

OptiX iManager T2000 System Description

About This Manual

Huawei Technologies Proprietary viii

OptiX iManager T2000 System Description

Huawei Technologies Proprietary 1-1

OptiX iManager T2000 System Description

Service management layer

NMS Network-level management layer (iManager T2100)

Subnetwork-level management layer (iManager T2000)

NE-level management layer EMS

GNE NE layer NE NE NE ... NE

Figure 1-1 The position of the T2000 in TMN

Huawei Technologies Proprietary 1-2

OptiX iManager T2000 System Description

1.2 Manageable Equipment

Huawei Technologies Proprietary 1-3

OptiX iManager T2000 System Description Category Equipment

Huawei Technologies Proprietary 1-4

OptiX iManager T2000 System Description

Huawei Technologies Proprietary 2-1

OptiX iManager T2000 System Description

Figure 2-1 Networking of single-layer management network

Software on the central NM The T2000 server RAS

Remote maintenance terminal

PSTN Serial port

Figure 2-2 Hardware connection of remote maintenance scheme

Huawei Technologies Proprietary 2-2

OptiX iManager T2000 System Description

2.2 Hierarchical Management Network

The hierarchical management network has such advantages:

2. Connecting upper-level NM through LAN

Huawei Technologies Proprietary 2-3

OptiX iManager T2000 System Description

Figure 2-4 Hierarchical networking structure realized through LAN

3. Connecting upper-level NM through WAN

DDN, 2M, ISDN, PSTN T2000 server