Version: V12.16.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: 800@zte.com.cn
LEGAL INFORMATION
Copyright © 2016 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
II
Intended Audience
This manual is intended for:
l Planning engineers
l Monitoring personnel
l Maintenance engineers
Chapter 1, System Overview Describes the system overview, position, features, managed
NEs, management functions, interfaces, technical specifications,
and compliant standards of the U31 R22.
Chapter 2, New Features Describes the new functions and important changes of the U31
R22.
Chapter 3, System Architecture Describes the hardware architecture and software architecture
of the U31 R22.
Chapter 5, Network Designs and Describes the U31 R22 deployment plans, network designs, and
Applications requirements for network bandwidths.
Chapter 6, System Interfaces Describes the system interfaces of the U31 R22.
Chapter 9, Compliant Standards Describes the standards that the U31 R22 complies with.
Conventions
This manual uses the following conventions.
Italics Variables in commands. It may also refer to other related manuals and documents.
Constant
Text that you type, program codes, filenames, directory names, and function names.
width
[] Optional parameters.
{} Mandatory parameters.
II
1-1
1-2
1-3
1-4
reports can provide detailed information and defects about each equipment and
scores them.
l Provides network performance analysis through WEB
Together with external tools, the U31 R22 provides the network analysis and report
function through WEB.
Security
l Supports backup routes
When ECCs are broken, the U31 R22 information can be sent through the backup
DCN, so that the U31 R22 management will not be affected.
l International standards-compliant security mechanism
The U31 R22 supports three-level security mechanisms. They are located at the
clients, servers, and adapters. The client interfaces and server interfaces support
SSL, and TLS. The AAA, Radius authentication, PAP, CHAP, and LDAP are
supported.
l Supports data consistence protection
The U31 R22 uses database backup and database synchronization mechanism.
1-5
1-6
1-7
1-8
Function Description
Common Management scale Displays the NMS management scale, including NE names,
number of licenses, number of the current NEs, and the total
number of the current equivalent NEs.
PTN Unloaded tunnel The system detects and manages (queries or deletes)
unloaded non-terminating tunnels.
Migration into or out l You can check whether the service tunnel of the
of the shared ring protection sub-net at the section layer is bound to the
shared ring.
l You can check whether the service tunnel is bound to the
tunnel of the shared ring.
Resource Usage Displays the resource usages of the TMS and static tunnels,
including the CAC function, convergence ratio mode,
automatic adjustment or not, and bandwidth usage.
Batch adjustment of By adjusting the service bandwidth, the service CAC function
the service bandwidth can be enabled and the service bandwidth can also be
adjusted.
2-1
Function Description
PTN service recovery With this function, damaged tunnels and pseudo wire
services can be automatically recovered.
WDM/OTN ONT status The system can check the OTN protection status in the
maintenance and network and perform switchover.
management
Intelligent wave Supports adjusting the optical power threshold and gain after
spread tool wave spread, including the following:
l Automatically calculating the recommended optical
power threshold and delivering the threshold to
equipment after manual confirmation.
l Automatically calculating the recommended value for
automatically adjusting the VMUX attenuation or OA
gain and delivering the value to equipment after manual
confirmation.
2-2
Function Description
Tool for planning the The system can replan the protection relationship group ID
protection relationship and deliver this ID to equipment after manual confirmation.
group ID.
New Functions Provided by the U31 R22 V12.15.10P02 (Compared With V12.15.10)
For the new functions provided by the U31 R22 V12.15.10P02 (compared with V12.15.10),
refer to Table 2-2.
Table 2-2 New Functions Provided by the U31 R22 V12.15.10P02 (Compared With
V12.15.10)
Function Description
PTN Traffic statistics Adjusts traffic for PWs and tunnels in batches.
2-3
Function Description
New Functions Provided by the U31 R22 V12.15.10 (Compared With V12.14.10P02)
For the new functions provided by the U31 R22 V12.15.10 (compared with V12.14.10P02),
refer to Table 2-3.
Table 2-3 New Functions Provided by the U31 R22 V12.15.10 (Compared With
V12.14.10P02)
Function Description
Installation mode The U31 R22 client supports installation through Web.
2-4
Function Description
IT EMS The U31 R22 has the ITMP module and the U31 R22 can monitor and
manage server hardware, the operating system, and third-party software.
Resource search and The U31 R22 supports searching resources by an NE, board, port, or
location CTP. After your double-click the resource, the corresponding interface
is displayed.
Resource permission The U31 R22 supports management authority partition based on boards
management and ports.
POTN capacity expansion The ZXCTN 6500 (V2.0) supports capacity expansion and reduction of
and reduction the POTN.
Port convergence ratio The ZXCTN 6000 series and ZXCTN 9000 series support the
convergence ratio. The port convergence ratio can be set on the EMS.
Optical fiber cutover After optical fiber cutover, you can query optical power of the optical
management fibers, and compare the optical power after cutover with that before
the cutover.
Automatic generation of After optical fibers among WDM NEs are connected, the EMS
OTS and OMS paths automatically generates OTS and OMS paths.
Service interruption alarm The U31 R22 supports statistical analysis on service interruption alarms.
statistical analysis
PTN service cutover l Pre-configured services and normal services are involved in
function supporting CAC bandwidth sharing, release, and reuse.
l The TMS and tunnel resource usage interface shows the bandwidth
usages with pre-configured services and without pre-configured
services.
l The U31 R22 supports creating a redundancy protection scenario.
Tunnel migration function The tunnel NNI side can be migrated across NEs to meet the
requirements in the scenarios where nodes of a tunnel are added or
reduced, boards and nodes are migrated in an NE, and link capacity
is upgraded.
Same-route tunnel To release bandwidth and save the physical link bandwidth resources,
bandwidth compression the U31 R22 can set a tunnel sharing relationship for the tunnels that
tool share the same TMS.
New Functions Provided by the U31 R22 V12.14.10P02 (Compared With V12.14.10)
For the new functions provided by the U31 R22 V12.14.10P02 (compared with V12.14.10),
refer to Table 2-4.
2-5
Table 2-4 New Functions Provided by the U31 R22 V12.14.10P02 (Compared With
V12.14.10)
Function Description
Connection Admission The resource reservation switch is used to designate whether bandwidth
Control (CAC) parameters participate in the CAC calculation at the control layer.
Protocol template During protocol instance configuration, the preset protocol template
must be used.
Parameter template You can preset a parameter template based on the actual requirements,
and then directly import this parameter template during service
configuration. There is no need to set the parameters one by one.
Ethernet service Modification scenarios can be divided into incremental modification and
modification decremental modification, which are used to add or delete sites and
add or delete protection.
In these two scenarios, data is only sent to the affected sites.
QoS template During service parameter configuration, you can select the preset QoS
template.
Section layer OAM and You can query, set, and modify the section-layer OAM parameters of
SD CTN links.
Maintenance operations include Ping, LCK, LB, LM, and DM.
Fault information The CTN fault information collection tool can be used for remote fault
collection location and information collection (including computer configuration
information, EMS configuration files, and EMS log files).
Event compression The system discards the events that are repeatedly reported.
If the time interval between the next event and the previous event that
have the same source and the same alarm code is within a specified
range, this event is considered to be a repeatedly reported event.
New Functions Provided by the U31 R22 V12.14.10 (Compared With V12.13.10P02)
For the new functions provided by the U31 R22 V12.14.10 (compared with V12.13.10P02),
refer to Table 2-5.
Table 2-5 New Functions Provided by the U31 R22 V12.14.10 (Compared With
V12.13.10P02)
Function Description
NE-level resource The U31 R22 can implement region-based authentication and
authentication management in the network. The user with the resource management
authority in a region can only manage the NEs in this region rather than
query or operate the NEs in other regions.
CTN service automatic Cooperates with third-party companies to realize the CTN service
activation system automatic activation system.
2-6
Function Description
TMS fault response If a TMS fault occurs in the network and this fault affects its carried
services (such as TMS LOC), the tunnels, PWs, client-layer services
carried over the TMS report the service fault.
Service group navigation Supports creating, deleting, and modifies service groups and filtering
services by using service groups as filtering conditions.
OTN path management l Supports discovering OSC paths automatically and managing them.
l Supports the graphical routing display of OSC paths.
l Supports filtering OSC paths in the entire network and forming an
OSC path view.
Path management based Supports PID-based path management, including path discovery, path
on PID creation, path display, and path maintenance.
Batch migration Supports batch non-protection tunnel migration of CTN shared ring.
Service template Adds a damaged service template and an alarm service template to the
template list in the service view.
Ping and Trace l Supports the Ping and Trace functions of dynamic tunnels in the
IP private network.
l Supports the Ping and Trace functions of PWs.
Automatic discovery Supports the automatic TMS discovery of CTN pass-through WDM
and OTN and the automatic TMS discovery of aggregation microwave
interfaces.
Common routing analysis Supports the common routing analysis of CTN services.
New Functions Provided by the U31 R22 V12.13.10P02 (Compared With V12.13.10P01)
For the new functions provided by the U31 R22 V12.13.10P02 (compared with
V12.13.10P01), refer to Table 2-6.
Table 2-6 New Functions Provided by the U31 R22 V12.13.10P02 (Compared With
V12.13.10P01)
Function Description
IP conflict detection If the IP of a created NE conflicts with that of an existing NE, or the IP
of a port of a created NE conflicts with that of a port of an existing NE,
an alarm is reported.
2-7
Function Description
Capacity extension Supports extension and reduction of the shared ring, and service
and reduction, service migration.
migration
Ping and trace l Supports the Ping function of MS-PW, L2 services and L3 VPN.
l Supports the Trace function of MS-PW.
New Functions Provided by the U31 R22 V12.13.10P01 (Compared With V12.13.10)
For the new functions provided by the U31 R22 V12.13.10P01 (compared with V12.13.10),
refer to Table 2-7.
Table 2-7 New Functions Provided by the U31 R22 V12.13.10P01 (Compared With
V12.13.10)
Function Description
Copy and paste Copies and pastes IP addresses and subnet mask controls.
New Functions Provided by V12.13.10 (Compared With the U31 R22 V12.12.20P01)
For the new functions provided by the U31 R22 V12.13.10 (compared with V12.12.20P01),
refer to Table 2-8.
Table 2-8 New Functions Provided by V12.13.10 (Compared With the U31 R22
V12.12.20P01)
Function Description
2-8
Function Description
Protocol management Supports IPV6 protocol management channel; supports browsing the
IPV6 protocol.
Resource view Resource views support abnormal traffic monitoring and packet
performance reports
New Functions Provided by V12.12.20P01 (Compared With the U31 R22 V12.12.20)
For the new functions provided by the U31 R22 V12.12.20P01 (compared with V12.12.20),
refer to Table 2-9.
Function Description
Resource view The resource view supports topology monitoring over CPU and memory.
2-9
Table 2-10 Changed Items in the U31 R22 V12.16.10 (Compared With V12.15.10P02)
Function Description
Common Installation disk l The icons in the installation window are updated.
l Installation steps are simplified.
WDM/OTN Service view l Working routes and protective routes are displayed in
texts w and p on the link and are not hidden by default.
However, you can customize the routes as hidden or not.
l The texts are displayed on the link and are distinguished
in different colors (for example, p is displayed yellow and
w is displayed blue).
Service route When service creation fails due to a route computing failure,
computing failure the system provides the function of analyzing the route
analyzing tool computing failure causes.
2-10
Table 2-11 Changed Items in the U31 R22 V12.15.10P02 (Compared With V12.15.10)
Function Description
PTN Analysis for the NEs Based on the selected service, analyzes the actual
with the same routes operating status of the service and NEs with the same
routes.
Table 2-12 Changed Items in the U31 R22 V12.15.10 (Compared With V12.14.10P02)
Function Description
EMS frame The function accesses and names on the EMS interfaces are integrated
and optimized.
Alarm right-button function The suppression filtering rules can be configured with the time of taking
effect.
Clock/time view The node or link that does not lock the clock or time properly is strikingly
displayed.
Optical power With the optical power management function, you can export the
management network-wide main optical power status table by clicking one button.
2-11
Function Description
Optical power attenuation The optical fiber attenuation trend of an optical fiber over a period of
trend time is displayed graphically.
Ping The scenarios that are applicable to GNEs and the ZXMP M721 are
added.
Attenuation spectrum The default page for showing the attenuation spectrum is changed.
management
Optical per performance If optical power performance exceeds the performance threshold but it
belongs to the performance detection range, the detailed performance
value is displayed.
Service cutover The service cutover function supports automatically binding shared rings.
Table 2-13 Changed Items in the U31 R22 V12.14.10P02 (Compared With V12.14.10)
Function Description
Service query Modifies the fields of service query and optimizes query efficiency.
2-12
Function Description
Table 2-14 Changed Items in the U31 R22 V12.14.10 (Compared With V12.13.10P02)
Function Description
DBtool database tool Supports the database upgrade of data communication devices.
Time view/optical power Supports the unified management for CTN devices.
view This function can be configured even though the IPTN is not deployed.
Product operating -
efficiency optimization
2-13
Function Description
Table 2-15 Changed Items in the U31 R22 V12.13.10P02 (Compared With V12.13.10P01)
Function Description
Product operating -
efficiency optimization
2-14
Table 2-16 Changed Items in the U31 R22 V12.13.10P01 (Compared With V12.13.10)
Function Description
Changed Items in the V12.13.10 (Compared With the U31 R22 V12.12.20P01)
For the changed items of the U31 R22 V12.13.10 (compared with V12.12.20P01), refer to
Table 2-17.
Function Description
Protection function The MSTP EPS protection can be configured in the end-to-end mode.
ACL management Supports the ACL management for 8900 serials equipment.
2-15
Function Description
Changed Items in the V12.12.20P01 (Compared With the U31 R22 V12.12.20)
For the changed items of the U31 R22 V12.12.20P01 (compared with V12.12.20), refer to
Table 2-18.
Function Description
Software installation Simplifies the software installation disk and changes the installation
procedure.
Product operating -
efficiency optimization
Northbound interface TL1 and FTP northbound supports the 5900E series equipment.
NE management l Supports the ZXCTN 6130 and ZXR10 6800 series equipment.
l Supports daughter cards on the 2900E series equipment.
2-16
The U31 R22 hardware contains servers, clients, alarm boxes, network devices, and
optional devices, such as printers, sound boxes, and backup devices.
l Servers
The servers are the core devices of the U31 R22 system. The servers communicate
with NEs via southbound interfaces. After the data is processed on the servers, they
are sent to the corresponding clients. The servers communicate with the upper-level
network management systems via northbound interfaces.
The servers can be divided into application servers and database servers based
on their functions. In general, the application server and the database server are
configured in one computer. While, they can also be configured in different computers
for sharing the load.
You can configure one U31 R22 server or two servers (master/slave), which can create
an HA system, as required.
3-1
l Network devices
Network devices are used to connect U31 R22 and NEs or connect U31 R22 and the
upper-level network systems. The network devices contain switches and routers.
l Optional devices
Optional devices contain printers and sound boxes.
3-2
3-3
3-4
l Navigation
The navigation tree and topology view are consistent. The navigation tree provides
corresponding NE operations, including NE modification or alarm querying.
l Graphic Display
The topology map shows all NEs managed by the system as well as their relations in
the network. You can view NE statistics, such as NE quantity, link quantity or alarms.
4-1
à Synchronize the configuration information of NEs on the topology map from the
server and refresh the display on the client without changing the positions and
connection relations of those NEs.
à Select the layout mode of NE icons on the topology map, including hierarchical
layout, tree layout, radial tree layout, spring embedded layout, and uniform length
edges layout.
l Filtered Display
On the topology map, you can set filtering conditions to filter the NEs or links that
you do not concern from the topology map. The filter conditions can be NE name, IP
address, link name, NE type, link type, and/or group type.
l Authorization-Based Data Display
The system only provides topology management functions to authorized users.
l Alarm Display
On the topology map, an NE or link is highlighted in different colors when some
fault(s) occur in it according to the fault severity and the acknowledgement status of
corresponding alarm(s).
l Group-Based View
To manage NEs more effectively, you can group NEs based on NE types or NE
locations.
4-2
The system automatically clears an alarm from the active alarm list after the fault
causing this alarm is removed.
l Alarm Synchronization
Alarm synchronization includes the synchronization of alarm information between
the U31 R22 server and the managed NEs (that is, the alarm sources), and the
synchronization of alarm information between the U31 R22 client and the server.
The system initiates an alarm synchronization process in the following situations:
à The broken connection between the client and the server recovers.
à The broken connection between the server and a managed NE in the network
recovers.
à The server is restarted.
l Output of Alarm Data
All alarm information can be output to *.txt, *.xls, *.pdf, *.html, or *.csv files.
l Alarm Rule Management
A fault in an NE may cause several correlated alarms. By setting a correlation rule,
you can collapse a series of correlated alarms caused by the same fault and reduce
the count of alarms displayed on the client screen.
l Alarm Query and Statistic
The alarm query and statistic include history alarms, active alarms, notifications, and
alarm number.
In addition, the system can indicate the distribution of different alarms by displaying
the statistic information in various chart forms, such as PDF, HTML, or CSV.
l Data Query
You can query raw performance data stored in the database.
l Data Synchronization
The system can automatically synchronize performance data from the managed NEs
to the server, and synchronize performance data from the server to the client. You
can also initiate the synchronization of performance data through a client.
l Data Report
4-3
The system can generate a performance data statistic report to show current KPIs,
which can also be output as *.xls, *.pdf, *.html, and *.txt files.
A predefined template or user-defined template can be used to generate the report
you want.
The system can send the periodically-generated report to a user in the specified format
through E-mail as required.
A role specifies the management permission for a user group, including the operation
permission and manageable resources.
à The operation permission allows the user group to use specific functional modules
of the network management system. For example, if a role has the operation
permission of the log management module, the users acting as the role can
perform log management operations, such as querying logs and maintaining logs.
à The manageable resources refer to subnetworks and/or network elements that
can be managed by the role.
l Role Set
A role set is a set of roles. The management permission of a role set involves the
management permissions of all roles in the role set.
l Department
Departments are specified in the network management system to simulate the actual
administrative departments. In this way, the system administrator can conveniently
organize and manage users in the system.
l User
For the model of relations among user, role, role set, department, operation permission,
and manageable resources involved in the security management, see Figure 4-1.
4-4
The U31 R22 system provides the following security management functions.
l Security Event Recording
The system can record security events, for example, authentication failure, locking a
user, and disabling a user. The system administrator can know the situation of user
accounts in the system by observing the security event log.
l Reporting of Security-Related Alarms
The system can report alarms to the administrator when some important security
events occur, for example, a user account is locked.
l Setting of Login Time Period
By using the security management module, you can set a limit of the time period for
a user. The user is allowed to log in to the system only in this period.
l User Account Management
A user can query and change its password, policy, locking rule, and validity period.
For example, you can specify a rule like this: if a user enters the wrong password three
times, the user account will be locked for the purpose of preventing unauthorized login.
The super administrator of the system can remove a user from the system forcibly to
avoid unauthorized operations performed by this user and ensure the system security.
4-5
4-6
NE time configuration
Service telephone configuration
NE and board configuration
Configuration for equipment-layer protection
l Configuration for network-layer protection
Configuration for single NE service and end-to-end service
l Ethernet service configuration
l Configuration for CTN and SDH mixed networking service
l Clock view
l Network maintenance
l Optical power view
l Data synchronization
OTN NEs support the following configurations:
l Clock configuration
NE clock synchronization configuration
NE basic configuration
Protection configuration
Configuration for single NE service and end-to-end service
l APR-AOSD configuration
l Optical power configuration.
l Spectrum configuration
l Overhead configuration
l Service telephone configuration
The following hybrid networks are supported:
l Configuration for CTN and SDH mixed networking service
l Hybrid network composed of SDH and WDM/OTN NEs
l Hybrid network composed of CTN and router/switch NEs
IP NEs support the following configurations:
l Basic NE configuration
l Clock configuration
l Interface configuration
l L2 configuration
l L3 configuration
l Configuration for single NE service and end-to-end service
l Security configuration
l UAS configuration
l OAM configuration
l QoS configuration
l Alarm configuration
4-7
l Performance configuration
PCM NEs support the following configurations:
l Basic NE configuration
l NMS channel management
l Route management
l Alarm configuration
The log management module of the U31 R22 system provides the following log
management functions.
l Log Query
You can set filtering conditions to query specific logs in the system, and save or print
the query result.
l Log Backup
The system can back up the logs in the system as files according to the specified
number of days or storage capacity.
4-8
4-9
4-10
5-1
5-2
l When the master and slave servers are deployed at different locations, they use two
computers. The data of the two servers is synchronized automatically. When the
master server fails, the services processed by the master server will be switched to
the slave server.
For the remote hot standby redundancy, see Figure 5-3.
5-3
5-4
For the remote networking of the U31 R22 system based on E1 transmission, see
Figure 5-6.
5-5
5-6
Table 5-2 Bandwidth Requirement for the U31 R22 Network Architecture
Item Bandwidth
Bandwidth between the client and the server At least 2 Mbit/s is recommended.
Bandwidth between the primary server and the At least 10 Mbit/s is recommended.
standby server
5-7
5-8
Internal Interfaces
The internal interfaces of the U31 R22 system refers to the communication interfaces
between the server and the client. They adopt TCP/IP for communication. In the U31
R22 system, the server and the client communicate with each other through a Local Area
Network (LAN) or a Wide Area Network (WAN). The communication bandwidth is equal to
or greater than 2Mbps.
Southbound Interfaces
Southbound interfaces refer to the communication interfaces between U31 R22 and the
managed NEs.
The U31 R22 supports the SNMP, Syslog, Telnet/SSH, FTP/TFTP, and private interfaces.
Northbound Interfaces
The U31 R22 northbound interfaces locate between U31 R22 and the upper integrated
NMS/OSS (Operation Support System). The upper integrated NMS/OSS can manage the
northbound interfaces through U31 R22.
U31 R22 provides the following northbound interfaces of three types:
l BN-xTN northbound interface
à BN-xTN northbound CORBA interface
à BN-xTN northbound TMF CORBA (CTCC) interface
à BN-xTN northbound TMF CORBA (CTCC) dual-interface
à BN-xTN northbound SNMP interface
à BN-xTN northbound FTP (CSV) asset interface
à BN-xTN northbound FTP (CSV) performance interface
l Unified northbound interface
à Wireline northbound CORBA interface
à Wireline northbound XML(MTOS) interface
à Unified northbound SNMP interface
à Unified northbound MML interface
6-1
6-2
Item Specification
System response time l When the equipment operates properly, the response time for user
operations is less than 3 s.
l When the equipment operates abnormally (frequent alarms occur),
the response time for user operations is less than 30 s.
Mean response time for alarm display, which refers to the duration from
the time when NE generates an alarm to that when EMS displays the
alarm, is less than 10 s.
Mean system response time, which refers to the duration from the time
when an alarm is reported to that when the client displays the alarm, is
less than 3 s.
Master/slave network When the hot standby redundancy is used for the network management,
management system the time for switching the master and slave network management system
performance is less than 10 min.
Data storage capacity Alarm data storage time: It can be configured by users. The default value
is 6 months.
System log storage time: It can be configured by users. The default value
is 6 months.
7-1
Note:
When the system operates with full load, the system response time should not be larger
than 150% of the above specifications.
Item Specification
Note:
l Ordinary failures refer to the failures that only affect partial functions of the system.
When an ordinary failure occurs, the system can operate properly.
l Severe failures refer to the failures that affect the entire system. When a severe failure
occurs, the system cannot operate properly.
7-2
Temperature +5 ºC to +35 ºC
8-1
8-2
9-1
l ITU-T Q.821 Stage 2 and Stage 3 Description for the Q3 Interface - Alarm surveillance
l ITU-T Q.822 Stage 1, Stage 2 and Stage 3 Description for the Q3 Interface -
Performance Management
l ITU-T X.730 object management function
l ITU-T X.731 state management function
l ITU-T X.733 alarm reporting function
l ITU-T X.734 event report management function
l ITU-T X.735 log control function
9-2
9-3
9-4
CHAP
- Challenge Handshake Authentication Protocol
CORBA
- Common Object Request Broker Architecture
CTN
- Converged Transport Network
DCN
- Data Communications Network
DDN
- Digital Data Network
ECC
- Embedded Control Channel
EML
- Element Management Layer
EMS
- Element Management System
FE
- Fast Ethernet
FTP
- File Transfer Protocol
GE
- Gigabit Ethernet
HA
- High Availability
HCS
- Hierarchical Cell Structures
HDSL
- High-data-rate Digital Subscriber Line
IP
- Internet Protocol
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
KPI
- Key Performance Indicator
LAN
- Local Area Network
LCS
- LoCation Services
LCT
- Local Craft Terminal
LDAP
- Lightweight Directory Access Protocol
MODEM
- Modulator-Demodulator
MPLS
- Multiprotocol Label Switching
MPLS-TP
- Multi-Protocol Label Switching Transport Profile
MTBF
- Mean Time Between Failures
NBI
- Northbound Interface
NML
- Network Management Layer
NMS
- Network Management System
II
OAM
- Operation, Administration and Maintenance
OMG
- Open Mobile Gateway
OMS
- Optical Multiplex Section
OSI
- Open System Interconnection
OSPF
- Open Shortest Path First
OSS
- Operation Support System
OTN
- Optical Transport Network
PAP
- Password Authentication Protocol
QoS
- Quality of Service
RS
- Regenerator Section
SD
- Signal Degrade
SDH
- Synchronous Digital Hierarchy
SNMP
- Simple Network Management Protocol
SQA
- Service Quality Analyzer
SRLG
- Shared Risk Link Group
SSL
- Secure Sockets Layer
T-MPLS
- Transport Multi-Protocol Label Switching
TCP
- Transmission Control Protocol
TLS
- Transport Layer Security
III
TMN
- Telecommunications Management Network
TP
- Transport Protocol
UPS
- Uninterruptible Power Supply
UTC
- Universal Time Coordinated
WAN
- Wide Area Network
WDM
- Wavelength Division Multiplexing
WEB
- Web
XML
- Extensible Markup Language
IV