EONA

ZXUCP A200
Unified Control Plane for WDM/OTN

User Manual
Version: V1.20
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
2011-09-27
ZXUCP A200 (V1.20) First release
Serial Number: SJ-20110728142617-001

Publishing Date: 2011-09-27(R1.0)
Table of Contents
Preface............................................................................................................. I
Chapter 1 Fundamentals of ASON............................................................ 1-1
1.1 Background of ASON ......................................................................................... 1-1
1.1.1 Definition of ASON ................................................................................... 1-1
1.1.2 Problems in a Traditional Optical Network .................................................. 1-1
1.1.3 Demands Generated by ASON ................................................................. 1-2
1.1.4 Advantages of ASON ............................................................................... 1-2
1.2 ASON Functions ................................................................................................ 1-3
1.3 ASON Architecture ............................................................................................. 1-4
1.3.1 Three Functional Planes ........................................................................... 1-4
1.3.2 Three Connection Types........................................................................... 1-6
1.3.3 Two Relation Models ................................................................................ 1-8
1.4 ASON Protocols ............................................................................................... 1-10
1.4.1 Interface Protocols ................................................................................. 1-10
1.4.2 Control Protocols.....................................................................................1-11
1.5 Networking and Protection of ASON .................................................................. 1-14
1.5.1 Networking ............................................................................................ 1-14
1.5.2 Protection .............................................................................................. 1-16
1.5.3 Restoration ............................................................................................ 1-17
1.6 ASON Services ................................................................................................ 1-19
1.6.1 Introduction to ASON Services ................................................................ 1-19
1.6.2 ASON Service Models ............................................................................ 1-21
1.6.3 Management of ASON Services .............................................................. 1-23
Chapter 2 ZXUCP A200 (WASON) Function and Solution ..................... 2-1

2.1 WASON Concepts and Solved Problems ............................................................. 2-1
2.1.1 Concepts of WASON ................................................................................ 2-1
2.1.2 Problems Solved by WASON .................................................................... 2-1
2.2 ZXUCP A200 Functions...................................................................................... 2-2
2.3 ZXUCP A200 Solution ........................................................................................ 2-5
Chapter 3 ZXUCP A200 Debugging .......................................................... 3-1

3.1 Initialization Configuration Flow ........................................................................... 3-1
3.2 Initialization Configuration ................................................................................... 3-2
3.2.1 Preparation for Hardware.......................................................................... 3-2
3.2.2 Updating and Downloading Boot/Fpga Program ........................................ 3-3

3.2.3 Updating and Downloading App Application Program ................................. 3-3
3.2.4 Formatting SD Card ................................................................................. 3-4
Chapter 4 ZXUCP A200 Configuration Management............................... 4-1

4.1 Overview ........................................................................................................... 4-1
4.1.1 Network Topology..................................................................................... 4-1
4.1.2 Management Interface.............................................................................. 4-2
4.2 Enabling the Control Plane ................................................................................. 4-4
4.2.1 Operation Purpose ................................................................................... 4-4
4.2.2 Operation Description ............................................................................... 4-5
4.3 Node Management............................................................................................. 4-6
4.4 Configuring the Automatic Discovery ................................................................... 4-8
4.5 Configuring I-NNI Interface ................................................................................4-11
4.5.1 Operation Purpose ..................................................................................4-11
4.5.2 Operation Description ............................................................................. 4-12
4.6 Configuring TE Links ........................................................................................ 4-19
4.6.1 Operation Purpose ................................................................................. 4-19
4.7 Control Plane Running Topology ....................................................................... 4-22
4.8 Call Management ............................................................................................. 4-24
4.8.2 Configuring the Diamond Service ............................................................ 4-30
4.8.3 Configuring the Gold Service................................................................... 4-39
4.8.4 Configuring the Silver Service ................................................................. 4-43
4.8.5 Configuring the Copper Service............................................................... 4-46
4.8.6 Configuring the Iron Service.................................................................... 4-48
4.8.7 Querying, Modifying and Deleting a Call Service ...................................... 4-48
4.8.8 Manually Reverting to Services ............................................................... 4-55
4.8.9 Setting the Service Optimization.............................................................. 4-57
4.8.10 Presetting the Service Rerouting ........................................................... 4-59
4.9 Synchronizing SPC Services............................................................................. 4-60
II

4.10 SPC Service Maintenance .............................................................................. 4-61
4.10.1 Operation Purpose ............................................................................... 4-61
4.10.2 Operation Description ........................................................................... 4-62
4.11 Enabling the Autodiscovery (non-WASON)....................................................... 4-64
4.11.1 Operation Purpose................................................................................ 4-64
4.12 Bundled Links ................................................................................................ 4-65
4.13 Configuring Optical Impairment Parameters ..................................................... 4-67
4.14 Connection Crankback Policy.......................................................................... 4-72
4.15 Comparing Topology Links .............................................................................. 4-74
4.16 PCE Configuration.......................................................................................... 4-76
4.16.2 Configuring a PCE Shelf ....................................................................... 4-76
4.16.3 Configuring a PCE Node....................................................................... 4-80
4.16.4 Configuring a PCE Control Interface ...................................................... 4-81
4.16.5 Configuring the PCE Automatic Discovery.............................................. 4-83
Chapter 5 ZXUCP A200 Alarms and Events............................................. 5-1

5.1 Alarms on the Control Plane ............................................................................... 5-1
5.2 Events on the Control Plane................................................................................ 5-2
5.3 Alarm Handling .................................................................................................. 5-3
5.3.1 Connection Failure ................................................................................... 5-3
5.3.2 Connection Degradation ........................................................................... 5-4
5.3.3 RSVP Hello Failure .................................................................................. 5-5
5.3.4 LMP Hello Failure..................................................................................... 5-6
5.3.5 Node Parameters Not Configured.............................................................. 5-7
5.3.6 Service Failure ......................................................................................... 5-8
5.3.7 Transmit Interface Discovery Failure.......................................................... 5-9
III
5.3.8 Miswire ................................................................................................. 5-10

5.3.9 Neighbor Discovery Failure ......................................................................5-11
5.3.10 Transmit Interface Misconnection .......................................................... 5-12
5.3.11 Residual Timeslot Alarm........................................................................ 5-13
5.3.12 Inconsistency of Resource Management Rights ..................................... 5-14
5.4 Event Handling................................................................................................. 5-15
5.4.1 Connection Switching ............................................................................. 5-15
5.4.2 Service Restoration Starts ...................................................................... 5-15
5.4.3 Service Restoration Succeeds ................................................................ 5-15
5.4.4 Service Restoration Fails ........................................................................ 5-16
5.4.5 Service Reversion Starts ........................................................................ 5-16
5.4.6 Service Reversion Succeeds................................................................... 5-16
5.4.7 Service Reversion Fails .......................................................................... 5-17
5.4.8 Connection Resetup Attempt................................................................... 5-17
5.4.9 Connection Restart and Restoration ........................................................ 5-17
5.4.10 Fails to Set Cross-Connect on the Transport Plane................................. 5-17
5.4.11 Service Optimization Rerouting Starts .................................................... 5-18
5.4.12 Service Optimization Rerouting Succeeds.............................................. 5-18
5.4.13 Service Optimization Rerouting Fails ..................................................... 5-18
5.4.14 MCU Reset .......................................................................................... 5-19
Chapter 6 Network Maintenance of ZXUCP A200 ................................... 6-1

6.1 Network Routing Maintenance ............................................................................ 6-1
6.1.1 Maintenance Instructions .......................................................................... 6-1
6.1.2 List of Maintenance Items ......................................................................... 6-1
6.1.3 Maintenance Operations........................................................................... 6-2
6.2 Troubleshooting ................................................................................................. 6-5
6.2.1 Troubleshooting Principles ........................................................................ 6-5
6.2.2 Solution to Common Faults ....................................................................... 6-6
Appendix A Compliant Standards ........................................................... A-1

A.1 Compliant ITU-T Standards ................................................................................ A-1
A.1.1 Architecture and Requirements................................................................. A-1
A.1.2 Call and Connection Management ............................................................ A-1
A.1.3 Discovery and Link Management .............................................................. A-2
A.1.4 Other Related ITU-T Standards ................................................................ A-2
A.2 Compliant IETF Standards ................................................................................. A-3
A.3 Compliant OIF Standards ................................................................................... A-4
List of Figure................................................................................................... I
IV
List of Table....................................................................................................V
Glossary .......................................................................................................VII
VI
Preface
Applicable Product
This manual is applicable to Unitrans ZXUCP A200 (V1.20) Unified Control Plane for
WDM/OTN (ZXUCP A200 in short hereinafter).
What Is in This Manual

This manual is the Unitrans ZXUCP A200 (V1.20) Unified Control Plane for WDM/OTN
User Manual. The following table describes the chapters in this manual.
Chapter
Content
Chapter 1 Fundamentals of
Describes the background, functions, architecture, protocols,
ASON
networking, protection and services of ASON.
Chapter 2 ZXUCP A200
Describes the concepts and functions of WASON, functions of
(WASON) Functions and
ZTE ZXUCP A200 and ZXUCP A200 WASON solutions.
Solutions
Describes the initialization configuration of the ZXUCP A200
Initialization Configuration
equipment.
Describes the ZXUCP A200 product and WASON management.
Configuration Management
Chapter 5 ZXUCP A200 Alarms
Describes the alarm handling and event handling related to
and Events
ZXUCP A200 WASON functions.
Describes the routine maintenance items and troubleshooting
Routine Maintenance and
methods of ZXUCP A200.
Troubleshooting
Appendix A Compliant Standards
Lists the ITU-T, IETF and OIF standards related to WASON.
Intended Readers
This manual applies to the following engineers:
l
l
l
l
Planning engineers
Debugging engineers
Network supervision engineers
Maintenance engineers
Conventions
1. Mouse Operation Conventions
Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually the left mouse
button) once.
Double-click
Refers to quickly clicking the primary mouse button (usually the left
mouse button) twice.
Right-click
Refers to clicking the secondary mouse button (usually the right

mouse button) once.
Drag
Refers to pressing and holding a mouse button and moving the mouse.
2. Safety signs
The following safety signs may appear in this manual.
Safety Sign
Meaning
A serious accident, such as casualties or equipment damage may
Danger
occur if you ignore this safety warning.

A major accident, such as casualties or equipment damage may
Warning
occur if you ignore this safety warning.

Equipment damage, data loss, degradation of equipment perfor-
Caution
mance, or other unpredictable result may occur if you ignore this

safety warning.
Provides additional information about a topic.

Note
Indicates a suggestion or hint to make things easier or more proTip
ductive.
3. Manual Usage Convention

This manual takes the ZXUCP A200 client running on the Windows platform as an
example for illustration.
II
Chapter 1
Fundamentals of ASON
Table of Contents
Background of ASON .................................................................................................1-1
ASON Functions ........................................................................................................1-3
ASON Architecture .....................................................................................................1-4
ASON Protocols .......................................................................................................1-10
Networking and Protection of ASON.........................................................................1-14
ASON Services ........................................................................................................1-19
1.1 Background of ASON

1.1.1 Definition of ASON
Definition of ASON
Automatically Switched Optical Network (ASON) is an intelligent optical network. In an
ASON, service requests are initiated dynamically by a user end or a network management
system. NEs select routes automatically for these requests and apply the signaling
control to establish, modify, release, automatically protect, restore and discover service
connections. ASON is a new-generation optical network, which integrates the switch and
transport functions.
Generation of ASON
The concept of ASON was first put forward in 2000. Its basic idea is to introduce a control
plane into the traditional optical transport network, so as to allocate network resources in
real time according to the actual needs. In this way, the optical network can evolve to a
high-capacity intelligent network, which is configurable and supports multiple channels. As
the core technology for building a new-generation optical network, ASON is supported by
the compatible and extensible hardware system. It integrates advanced software system
into the hardware platform to form an underlying platform with more elasticity, converts
the optical layer from a static transmission media to a dynamic, intelligent optical network
hierarchy, and comprehensively promotes the transmission efficacy as well.
1.1.2 Problems in a Traditional Optical Network

In a traditional optical network, as the network scale and network capacity get increasingly
larger, the amount of service connections increases exponentially, which results in
1-1
SJ-20110728142617-001|2011-09-27(R1.0)
ZTE Proprietary and Confidential
ZXUCP A200 User Manual
higher requirements for equipment operation. The traditional network has the following
shortcomings:
l
l
l
l
l
l
l
End-to-end services can only be configured segment by segment via a network

management system. Therefore, it requires much time. Fast automatic setup and
protection of end-to-end services is unavailable in traditional optical networks.
Network load cannot be balanced and optimized automatically.
Differentiated services are unavailable without diverse QoS.
Network topology changes cannot be displayed in real time in a network management
system, which makes real-time management difficult.
Traditional optical networks use network management systems with multiple
hierarchies, which manage a great diversity of equipment. Accordingly, it is difficult to
use a unified network management system to manage all kinds of equipment, such
as DXC, ADM, and DWDM equipment.
Different models of equipment are used on the backbone layer with lots of connections
among optical interfaces, which makes the network structure complex.
Traditional optical networks generally use a ring networking mode. It results in the
existence of many cross-ring nodes, which become the bottleneck for the traffic
scheduling.
Service commissioning takes much time and increases the maintenance cost.
1.1.3 Demands Generated by ASON

With the rapid growth in IP services, the percentage of data services increases greatly in
networks. IP services feature the traffic burst and sudden changes of traffic directions.
Thus, it requires new network technologies to guarantee the transmission QoS. The
commercial use of large-capacity optical cross-connect components, adjustable laser
components, adjustable OTU devices and dynamic dispersion compensation devices
can solve the WDM dispersion restriction problem and provide technical support for the
dynamic ASON network.
l
l
l
l
l
With the growth of data services, the bursting bandwidth demands of data services
will become the mainstream service in future and challenge the semi-static mode of
transmission networks.
High expansibility is required for transmission networks with the rapid growth of data
services.
Large capacity and bandwidth, high reliability, flexibility and fast commissioning of
optical networks are needed.
Diverse applications and services are required.
With the rapid development of data services, traditional optical transmission networks,
originally designed for voice transmission, can no longer satisfy the service demands.
1.1.4 Advantages of ASON

ASON, as a new-generation optical network, not only satisfies the new demands of modern
telecommunication services, but also solves problems of traditional optical networks.
1-2
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 1 Fundamentals of ASON
ASON has the following advantages.

l
l
l
l
l
l
l
l
l
l
It supports the flexible traffic scheduling with high capacity and multiple granularities.
It has a small number of devices and a high utilization ratio, so that the network has
a clear structure.
It supports the flexible mesh networking mode, which has strong self-healing
capability, high scalability and high bandwidth utilization ratio.
It supports the automatic discovery of network topology.
It supports the automatic balancing, optimizing of link load as well as the dynamic
bandwidth allocation so as to improve the bandwidth utilization ratio.
It supports the fast and flexible service commissioning based on signaling requests.
It supports the end-to-end (cross-ring) traffic protection.
The network management is simplified. A unified NMS is implemented on different
networks. Therefore, different networks can be interconnected eventually.
It reduces the service setup time. The dynamic request and release of bandwidth is
supported.
IT provides Service Level Agreement (SLA). It provides new value-added services,
which include the bandwidth allocation on demand, bandwidth lease and wholesale,
and Optical Virtual Private Network (OVPN).
1.2 ASON Functions

The intelligent functions of ASON are mainly implemented by the control plane, which
provides basic functions and core functions. The basic functions of the ASON control
plane include routing, signaling, link management and unit interface technology. The core
functions of the ASON control plane include connection control, network survivability and
new services.
Basic Functions
Basic functions constitute the basic platform of the ASON control plane. It is the foundation
of the intelligence of ASON.
l
Routing function: includes the route calculation (service route and signaling route),
implementation of routing protocols, release and management of network topology,
and local resource information.
Signaling function: includes the setup, release and maintenance of the Label
Switching Path (LSP), processing LSP-related requests (including setup request of
SPC) that come from the management plane and maintaining signalling sessions.
Link management function: includes the discovery function (including the neighbor
discovery and the service discovery), data channel connectivity verification,
control channel maintenance, Traffic Engineering (TE) link management, and fault
information processing.
Core Functions
Core functions are the key for realizing the intelligence of ASON.
1-3
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
l
l
The connection control supports three types of ASON connection control and
management. Refer to the section of "Connection Types in ASON" for details.
Protection/restoration: guarantees the survivability of ASON, which includes the local
span protection, ring protection, section-to-section protection, permanent 1+1 protection based on the control plane and distributed restoration mechanism.
Service processing: supports the transport of new intelligent value-added services,
such as Bandwidth On Demand (BOD), Optical Virtual Private Network (OVPN).
Policy management: supports the processing of calls to ensure the intelligent use of
network resources.
1.3 ASON Architecture

1.3.1 Three Functional Planes
As shown in Figure 1-1, the functional architecture of ASON has three planes:
management plane, control plane and transport plane (also called service plane).
This figure also includes the Data Communication Network (DCN), which controls and
management communication.
Figure 1-1 ASON Architecture
Control Plane
The control plane comprises a group of control components providing specific functions as
routing and signaling, and it is supported by a signaling network. The information stream
needed by the communication between the components in the control plane is obtained
through interfaces.
l
Functions
1-4
SJ-20110728142617-001|2011-09-27(R1.0)
The main functions of control plane include: collecting and distributing network
topology information on the control plane in ASON and providing routes by means of
Shortest Path First algorithm. It mainly manages and controls the information stream.
It automatically discovers the adjacency relationship and link status (such as

available capacity and faults) and supports the connection setup, release and
restoration.
It supports to set up, release, maintain the end-to-end connections through

signaling.
It selects proper routes for connections through route selections.
It executes the protection and restoration when network faults occur.
It provides a proper naming and address mechanism.
Composition
The ASON control plane is composed of a group of communication entities that
provide the functions of call control, connection control. It mainly sets up, releases,
monitors and maintains the connection and restores the connection in case of failure.
It is supported by the signaling network.
The control plane mainly involves the following parts:
Signaling channels that allow the exchange of control information among nodes.
End-to-end connection that can be fast set up and released by nodes and
signaling protocols.
Topology database that can be modified and maintained in a distributed way.
Fast and flexible restoration mechanism.
Characteristics
It supports various transport infrastructures, such as the SDH transport network

defined in ITU-T G.803 and the Optical Transport Network (OTN) defined in ITU-T
G.872.
It supports various traffic control engineering, protection and restoration

mechanisms.
It supports various control protocols.
It is applicable regardless of the implementation of connection control, how the

control plane has been subdivided into domains and routing areas, and how the
transport resources have been partitioned into subnetworks.
It is applicable to client-layer services with the focus on real-time service

switching.
Transport Plane
l
The transport plane provides explicit routes and circuit service stream of the service
plane. The transport plane provides users with bidirectional or unidirectional
1-5
SJ-20110728142617-001|2011-09-27(R1.0)
information transmission from one end to another end and monitors the connection
status information (such as faults and signal quality) and then provides it to the
control plane.
It transfers detailed fault management and performance detection information. The
transport plane, layered as defined in ITU-T G.805, supports existing and future
transmission technologies. It provides the functions of optical signal transmission,
multiplexing, protection switching configuration, cross-connection and guarantees
the reliability of optical signals transmitted over it.
To realize various functions of ASON, the transport plane must have a strong detecting
function of signal quality and multiple-granularity cross-connection technology.
Management Plane
l
The management plane mainly implements such work as parameter configuration,

billing, maintenance, etc. The management plane provides the function of managing
the transport plane, control plane and DCN. The transport plane, control plane
and DCN report their management information (event, alarm, performance etc.) to
the management plane. According to the received management information, the
management plane coordinates the works on all planes.
In terms of logical function, the management plane can be divided into three
layers: NE layer, element management layer and network management layer. The
ASON network management system can be set based on traditional management
domain divisions, or based on the ASON control domains. Different ASON network
management systems can be set for different network carriers, that is, one network
management system manages the network of one carrier. When multiple control
domains exist in the network of a same carrier, different network management
systems can be set based on the division of control domains, or the same network
management system can manage multiple control domains.
1.3.2 Three Connection Types

ASON supports three types of connections: permanent connection, switched connection
and soft permanent connection. They are used under different application conditions.
Permanent Connection
Permanent connection is also called provisioned connection, which is implemented by the
network management system or manually.
Characteristics:
l
The management plane configures resources on the transport plane to set up

a permanent connection. It not only initiates but also configures the permanent
connection. Once being set up, a permanent connection will always exist until the
management plane commands to release it.
It follows the connection setup mode in the traditional networks, in which the EMS
calculates the route in advance.
1-6
SJ-20110728142617-001|2011-09-27(R1.0)
ASON can be better compatible with the traditional optical networks by issuing
commands to NEs for setting up cross-connections.
Switched Connection
Switched connection is also called signaling connection. Contrary to permanent
connection, the switched connection is established on request of the control plane, and
the configuration of transport plane resources is also completed by the control plane.
Characteristics:
l
l
l
l
End users originate request for setting up a new dynamic connection to the control
plane .
The control plane is responsible for completing the connection setup.
Automatic connection, the nodes are similar to that in intelligent switches.
To meet the fast, dynamic requirements and comply with the TE standard is the final
purpose of ASON.
Note:
The switched connection is the core of ASON. The optical network has intelligent functions
due to the introduction of switched connection, thus the needed optical channels can
be automatically provided according to user requirements. The switched connection is
realized under the control of the control plane.
Soft Permanent Connection

Soft permanent connection is also called hybrid connection.
Soft permanent connection is a combination of permanent connection and switched
connection. It is a user-to-user connection whereby the user-to-network portion of the
end-to-end connection is established by the network management system (management
plane) as a permanent connection. The network portion of the end-to-end connection
is established as a switched connection using the control plane. The release of the
connection is also completed under the command from the management plane.
Characteristics:
l
l
l
l
l
The management plane and control plane work together to implement the SPC.
The management plane configures the connections between users and network.
The management plane requests the control plane to configure the network.
Similar to a leased line, it is a interim form from PC to SC.
It is the best option for carriers at present.
1-7
SJ-20110728142617-001|2011-09-27(R1.0)
1.3.3 Two Relation Models

Based on the differences of correlation between the lower-layer optical transport network
and the circuit switched device, two network models are defined in ASON, which are
overlay model and peer model.
Overlay Model
Overlay model is also called client-server model. In this model, the lower-layer optical
transport network plays the role of a server as an independent "intelligent" network layer.
While the circuit switched device is regarded as a client. The optical network layer and
the client layer are differentiated clearly. They are independent with each other, and select
different routes, signaling schemes and address spaces. The client layer and the optical
layer can only exchange limited controlling information through the UNI interface. Figure
1-2 shows the overlay model.
Figure 1-2 Overlay Model Diagram
The internal topology status information of the optical network is invisible to the client
layer. For the network service of higher layer, the lower-layer optical transport network
is like a black box with some interfaces (UNI interfaces). Through these interfaces,
multiple service access device (such as IP router, ATM exchange device, SDH digital
cross-connection device etc.) can apply for bandwidth resources from the optical
network dynamically.
In essence, the work that the client-server model does is to determine an interface
protocol between the optical network layer and the client layer, in order to provide
data transmission service for the multiple service access device. To set up a
client-server model, the User-to-Network Interface (UNI) needs to be separated
from the Network-to-Network Interface (NNI). Its typical optical channel bandwidth
can usually provide a transmission capacity over 2.5 Gb/s, which is adequate for
transmitting IP data on WDM.
1-8
SJ-20110728142617-001|2011-09-27(R1.0)
Peer Model
l
In the peer model, the circuit switched devices (such as IP, ATM, SDH etc.) and the
optical network devices have equal status. In this model, a unified control plane are
established for circuit switched devices and optical network devices. Figure 1-3 shows
the peer model.
Figure 1-3 Peer Model Diagram
Due to the introduction of the unified control plane which takes effect on circuit
switched devices and optical network devices at the same time, the circuit switched
device and the optical network device do not have an obvious boundary. Therefore,
the UNI in the overlay model is not needed.
In the peer model, the topology information of all devices in the entire network can
be clearly known through every circuit switched device (such as an IP router, an ATM
switched device and an SDH cross-connection device etc.) Through this mechanism,
a circuit switched device is allowed to calculate a complete end-to-end route that runs
through the whole network independently. By setting a unified control plane with
the peer model, each network carrier can use the base station devices from other
network carriers. Thus the complexity of managing an optical network that is not
unified because of using different methods can be avoided.
1-9
SJ-20110728142617-001|2011-09-27(R1.0)
1.4 ASON Protocols

1.4.1 Interface Protocols
Logically, the ASON has three kinds of standard signaling control interfaces: User Network
Interface (UNI), Internal Network to Network Interface (I-NNI), and External Network to
Network Interface (E-NNI), as shown in Figure 1-4.
Figure 1-4 Interface Protocols in ASON
UNI
l
It defines the interface protocol between users and the ASON equipment. UNI
is a bidirectional signaling interface between two control plane entities, one of
which requests service and the other provides service. Client layer network
can automatically request to set up a new connection, query or release existing
connection status via UNI. It supports the functions of call control, resource discovery,
connection control and connection selection. Please note that it does not have the
route selection function related to UNI.
In addition, it runs between the client and the optical network, and it supports call
security, authorization function, enhanced search function and enhanced number
service. Its main functions are: connection setup, connection release, connection
modification and status query.
The functions of UNI need to be supported by relevant signaling protocols. Two
optional solutions are: CR-LDP and RSVP-TE.
E-NNI
l
It defines the intercommunication protocol among the equipment from different

manufacturers at the optical network side. The GMPLS series protocols are the main
body of its signaling protocol.
1-10
SJ-20110728142617-001|2011-09-27(R1.0)
E-NNI is a bidirectional signaling interface between two control plane entities in

different control domains. E-NNI supports the functions of call control, resource
discovery, connection control, connection selection and connection route selection.
It defines the general interfaces between control planes, which are bidirectional
signaling interfaces. Its main function is exchanging reachability information among
different domains. The internal topology information of a network is masked.
I-NNI
l
I-NNI is a bidirectional signaling interface between two control plane entities in one or
more domains with dependent relationship. I-NNI supports the functions of resource
discovery, connection control, connection selection and connection route selection.
As a bidirectional signaling interface, it defines the interface between the units in a
control network. Therefore, it provides the internal topology information of a network.
I-NNI is an intra-domain interface and uses private protocols which can be self-defined by vendors, so the standardization is not required. However, for smooth transition to the final peer model, the standard signaling protocols such as GMPLS and
PNNI should be complied with for the convenience of upgrading and interconnection
in future.
1.4.2 Control Protocols

Control protocols are important components of the ASON control plane. They are also
important means for the implementation of control plane functions. The fastest way
to realizing it is adopting the current data network protocols. Now ITU-T and other
international standardization organizations are going to use GMPLS protocols as the
control protocols for ASON. The GMPLS is extended from the MPLS. There are many
choices, and ASON takes part of them for extension to adapt to ASON.
Figure 1-5 shows the composition of GMPLS protocols used for ASON.
Figure 1-5 GMPLS Protocols for ASON
1.4.2.1 Link Management Protocol (LMP)

LMP runs on the transport plane between adjacent nodes to provide links and manage
bidirectional control channels between them. It includes the following core functions:
1-11
SJ-20110728142617-001|2011-09-27(R1.0)
control channel management, link property correlation, link verification and link fault
management.
Control Channel Management

Control channel management serves to establish and maintain control channel
connectivity between adjacent nodes. It completes parameter negotiation and signaling
information transfer.
At least one bidirectional control channel should be available between adjacent nodes.
Multiple control channels are allowed as backups. The connectivity and interface identifiers
of local and remote nodes on transport plane should be known, which can be obtained
through the management plane or by means of automatic discovery mechanism. The
remote node supports the association between transport plane interface and trace object.
For SDH network, LMP uses SDH Trail Trace Identifier (TTI).
Link Property Correlation

l
Link property correlation serves to aggregate multiple data links into a single TE link
and to synchronize the link properties. This function greatly reduces the delivery of
Link State Advertisement (LSA) messages in networks.
Link property correlation allows the bundling, modification and correlation of links
as well as the exchange of their traffic engineering parameters so as to ensure the
consistency of the properties and capacity of TE links between adjacent nodes.
Link Verification
l
Link verification serves to verify the physical connectivity of the data links and verify
the mapping of the local ID to remote ID. After link verification, a local-to-remote ID
mapping table with definite link states can be obtained.
The LMP link verification procedure is initiated by the Begin Verify message on the
control channel. It is implemented with the coordination between control channel and
data channels. Link verification procedure is optional depending on the configuration
of verification flag during parameter negotiation.
Link Fault Management

Link fault management is initiated by a downstream node that detects data link fault. It
serves to exchange channel fault messages and response messages so as to detect link
state hop by hop along Label Switched Path (LSP) towards the upstream until the faulty
link is located. This procedure enables quick response to link faults and precise location
of faulty links.
1.4.2.2 Routing Protocols

At present, ITU-T has not specified routing protocols for ASON. The commonly used
intra-domain routing protocols include OSPF and IS-IS, while inter-domain routing
1-12
SJ-20110728142617-001|2011-09-27(R1.0)
protocols include BGP, OSPF, PNNI and DDRP. Now OSPF-TE is most widely-used by
different vendors.
l
OSPF is a dynamic routing protocol based on link state and SPF algorithm. OSPF
learns network topology (in the same area) by exchanging link state between
neighbors and calculates the routes to all destinations in the area with SPF algorithm.
The purpose of an OSPF router module is to collect the topology information of network, including topology information on control layer and traffic topology information
used for constrained route calculation, as well as the network protection information.
It calculates routes according to the topology information on control layer to establish
routing tables on the control layer.
After the collection of service plane topology in the whole area, OSPF calls
Constrained Shortest Path First (CSPF) algorithm to search traffic path. The following
constraints are involved when using CSPF algorithm: maximum link bandwidth,
available link bandwidth, shared link risk group, nodes to be involved (or nodes to be
avoided), Service Level Agreement (SLA) and optical distance etc.
CSPF calculates not only end-to-end working paths but also corresponding protection
paths. To ensure the protection takes effect, there should not be any crossed nodes
or links expect for the two endpoints of a protection path and a working path. After
a working path is calculated, an easy method to calculate a protection path is to cut
the nodes and links (excluding the source node and the destination node) covered by
the working path in the current network, and then find a path from the source to the
destination in the cut network again.
1.4.2.3 Signaling Protocols

The core of ASON is the introduction of control plane in optical transport network. With
the control plane and the switching capability of signaling control, the management for
connection configuration is implemented. Therefore, the signaling protocol of control
plane is specially important for ASON. ITU-T G.7713 specifies three signaling protocols
for ASON: PNNI, RSVP-TE and CR-LDP.
l
PNNI
PNNI originates from traditional telecommunication signaling protocols (Q.2931,
Q.931 and SS7). It is highly reliable but without enough flexibility. PNNI cannot
communicate with GMPLS. The PNNI specified by ITU-T G.7713.1 is only applicable
to soft permanent connections.
RSVP
RSVP originates from IPCoS technology. Compared with PNNI, RSVP can better
implement resource synchronization, error and fault processing such as power
failure. Moreover, it makes multicast easier. RSVP can fully separate the control
plane and the data plane with better flexibility.
It is used between I-NNI and E-NNI, from local domains to exterior domains or
all paths between service providers. It supports soft permanent connections and
intra-domain switched connections.
1-13
SJ-20110728142617-001|2011-09-27(R1.0)
CR-LDP
CR-LDP originates from IP MPLS technology. It is difficult to realize multicast, and
needs great extension and improvement. CR-LDP is applicable to UNI, E-NNI and
I-NNI, supporting some ASON-related automatic calling and connection operations.
RSVP is more mature than CR-LDP, so most vendors adopt it as their signaling protocol.
Compared with the original GMPLS protocol, the protocol suite used by ASON has the
following additional features:
l
l
l
l
l
l
l
Support different intra-domain and inter-domain protocols.

Support IPv4, IPv6 and Network Service Access Point (NSAP).
Support user-defined service specifications and service diversity with UNI and E-NNI
interfaces.
Support domains and hierarchical architecture, same for overlay and peer models.
Support call/connection separation.
Support soft permanent connection.
Support service signals of various formats and rate levels.
1.5 Networking and Protection of ASON

1.5.1 Networking
1.5.1.1 ASON Independent Networking
When a network only contains ASON equipment, the mesh networking mode is commonly
used, as shown in Figure 1-6.
Figure 1-6 Mesh Networking
1-14
SJ-20110728142617-001|2011-09-27(R1.0)
1.5.1.2 Hybrid Networking via UNI

ASON can be deployed with other traditional optical networks to form a hybrid network via
UNI interfaces, as shown in Figure 1-7. In the figure, AS1 and AS2 represent traditional
networks, and CMS is Connection Management System.
Figure 1-7 Hybrid Networking via UNI
In such hybrid network, traditional optical networks are accessed to ASON as clients. It
has the following features:
l
l
l
l
Existing network resources can be fully utilized.

UNI agents send connection requests from the network management system to
ASON, which completes the setup of connections. This networking mode is applicable
for the relation between existing metro area network and newly-constructed ASON
backbone network.
The current mode is traditional optical network unidirectional UNI-C, i.e. the traditional
optical network is the client of ASON.
UNI interfaces are used between ASON and traditional optical networks but not
directly used for end users. Therefore, the hybrid network does not directly support
switched connection services of clients.
The functions of UNI interfaces are actually provided by data equipment but not
transmission equipment in optical networks such as SDH equipment.
1.5.1.3 Hybrid Networking via NNI

An out-of-band ASON can be deployed with other traditional optical networks to form a
hybrid network via UNI interfaces, as shown in Figure 1-8.
1-15
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 1-8 Hybrid Networking via NNI
This networking mode has the following features:

l
l
l
l
l
The traditional optical network realizes the NNI function through an NNI agent. NNI
interfaces between ASON and traditional optical networks can provide more network
information, such as routing information and protection/restoration information.
The hybrid network using NNI interfaces is more like an ASON with more functions.
Each NNI agent can represent one or more node equipment.
NNI acts for a node or a network. It can provide switched connection services.
Those existing optical networks that cannot be upgraded or reconstructed can be
directly interconnected to an ASON on the transport layer.
The ASON and the existing network are managed and configured separately. This
interconnection mode is similar to that of networks provided by different vendors. It is
unable to realize unified management and scheduling in the whole network.
1.5.2 Protection
Protection is a procedure to replace a failure resource with a reserved standby resource,
which is generally completed in dozens of milliseconds.
Protection Mechanisms
ASON supports two protection mechanisms. One is based on the transport plane and the
other is based on the control plane.
l
l
Protection based on transport plane: The management plane implements the

protection configuration. The control plane is not involved in such protection.
Protection based on control plane: The control plane implements the protection
configuration, including setting up one or multiple protection connections and
providing connection configuration information for the purpose of protection. The
1-16
SJ-20110728142617-001|2011-09-27(R1.0)
protection based on control plane is carried out between the source node and sink
node of a protected link. Only the connection controllers of the source node and sink
node are involved in the protection regardless of those of intermediate nodes.
The control planes in optical-layer and electrical-layer switching equipment require that the
signaling, route and link management can support the fault restoration in data plane.
Label Switching Path (LSP) is applicable to the local (segment), segment and end-to-end
restoration.
l
l
l
Local segment protection refers to the link protection carried out between two adjacent
switches (all LSPs are labeled with "segment protection" and "link selection")
Segment protection refers to LSP segment restoration between two nodes (such as
SNC specified by ITU-T).
End-to-end protection refers to the LSP protection between the input port and the
output port.
Protection Types
l
1+1 protection:
Services are transported on both the working link and protection link. Those with
better quality are received at the receiving end.
1:1 protection:
Services are only transported on the working link. The protection link does not carry
services or only carries services with lower priority. When the working link fails, the
services carried by it are switched to the protection link; while the services with lower
priority carried by the protection link are discarded.
M:N protection (M N):

N working links share M protection links. M and N can be preset. The protection links
can carry extra services. No one-to-one relationship is set between working links and
protection links. When a working link fails, its services are switched to an available
protection link. If more than M working links fail at the same time, only M working links
with higher priority are protected.
The optical channel shared protection ring and the optical MS shared protection ring
need to use APS protocol.
1.5.3 Restoration
Restoration is a procedure to reroute for a new connection to replace a failed connection
with idle capacity in network. Restoration is generally completed in hundreds of
milliseconds to several seconds.
Classification by Control Methods

Restoration can be controlled in a centralized way or a distributed way.
1-17
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
l
Centralized control: Restoration is completed under the control of a network control

center.
Distributed control: Restoration is completed by distributed intelligent NEs in a
network.
The distributed control is commonly used for restoration in ASON.
Classification by Path Restoration Modes

Restoration can be divided into rerouting restoration and pre-planned LSP restoration.
l
Rerouting restoration
Pre-calculated routes
End-to-end restoration LSP is set up based on the pre-calculated path after the
fault occurs. Under this mechanism, one or multiple paths are calculated before
the fault occurs. If resources are not preset or chosen before the fault occurs, the
availability of restoration connection is not guaranteed.
No pre-calculated routes
End-to-end restoration LSP is set up after the fault occurs. One or multiple explicit
routes used for restoration are calculated dynamically, and one of them is chosen
after the fault occurs. This is called LSP rerouting mechanism. If resources
are not preset or chosen before the fault occurs, the availability of restoration
connection is not guaranteed.
Pre-planned LSP restoration
LSP restoration can complete the signaling exchange on demand or complete

it in advance. If the signaling exchange is completed on demand, the control
plane needs to deliver the restoration-related signals to each relevant node. If
the signaling exchange is completed in advance, pre-planned LSP restoration
will start directly.
Pre-planned LSP restoration (or pre-planned LSP rerouting) is carried out after
signaling exchange is completed. The restoration resources on the restoration
path are pre-planned.
Implementation Methods of Restoration

The implementation methods of restoration include pre-planned rerouting and dynamic
rerouting.
l
Pre-planned rerouting calculates restoration routes for working connections before a

fault occurs. When a working connection fails, the pre-planned connection is activated
to replace the failed one.
Dynamic rerouting calculates restoration route for working connection in real time
when a fault occurs, selects standby resources, and sets up new connections to
replace the failed one.
The dynamic rerouting is mostly used for restoration in ASON.
1-18
SJ-20110728142617-001|2011-09-27(R1.0)
1.6 ASON Services

1.6.1 Introduction to ASON Services
1.6.1.1 Service Types
ASON can provide transmission channels with fixed bandwidth between two client NEs.
The channel is defined between the input access point and the output access point of the
optical network. The ASON services include:
l
l
l
l
l
SDH service: SDH connections with granularity of VC-n and VC-n-Xv as specified in
ITU-T G.707
OTN service: OTN connections with granularity of ODUk and ODUk-n-Xv as specified
in ITU-T G.709
Transparent or non-transparent optical wavelength services
Ethernet services of 10 Mbit/s, 100 Mbit/s, 1 Gbit/s and 10 Gbit/s
Fiber Connection (FICON), Enterprise System Connection (ESCON), Fiber Channel
(FC) and Storage Area Network (SAN) services
1.6.1.2 Service Connection Topology Types

ASON supports the separation of call and connection control for the enhanced functions
such as bandwidth on demand, diversity of circuit assignment, and connection bundling,
etc. The separation of call and connection control reduces call control messages of
intermediate control nodes and thus lessen the workload of decoding and message
explanation. ASON supports the following topology types of service connections.
l
l
l
Bidirectional point-to-point connection

Unidirectional point-to-point connection
Unidirectional point-to-multipoint connection
Due to the separation of call and connection, a call can correspond to multiple connections.
At present, the bidirectional point-to-point connection is the most widely used connection
mode.
1.6.1.3 Service Connection Types

ASON supports three types of connections: Permanent Connection (PC), Switched
Connection (SC) and Soft Permanent Connection (SPC). Refer to the section of "Three
Connection Types" for details.
1.6.1.4 Service Levels

ASON supports the convenient division of services based on the priority to provide
transmission traffic complying with Service Level Agreement (SLA). Clients have different
requirements for connection availability. These requirements can be expressed in terms
of the "service level". In ASON, service level describes restoration/protection options and
1-19
SJ-20110728142617-001|2011-09-27(R1.0)
priority related connection characteristics, such as setup priority, holding priority (pre-idled
or not), or restoration priority.
l
l
Setup priority: It refers to connection setup time, which may be on day, hour or minute
level.
Holding priority (pre-idled or not): It determines whether a connection link without
protection can be pre-idled to carry more important service when some fault occurs
in system.
Restoration priority: It refers to restoration time in case of system failure and
restoration level such as percentage of restored services.
The control plane supports the priority setting of each connection, bandwidth reservation
with the purpose of restoration, as well as route unification after failure recovery. Generally,
ASON supports the following connection levels.
l
l
l
l
Private connection (1+1 and 1:1)

Shared protection (1:N, M:N and OCh-SPRING)
Non-protection (transport on active link)
Non-protection (transport on protection link)
1.6.1.5 Service Access Methods

In order to access services to an ASON, physical connections should be established
between clients and carrier networks on the transport plane. The following access
methods are optional, according to the locations of carrier networks and clients.
l
l
l
l
Intra-office access (when NEs in optical networks and client NEs are located at the
same place)
Direct remote access (for client devices with private link connections)
Remote access via access subnet
Dual homing access
ASON must support the dual homing access. Multiple addresses are not needed when a
client adopts the dual homing access. Dual homing access is a special case of the access
network. A client device may be dual homed to a carrier network through two different
paths. The purpose of dual homing is to enhance the network survivability. When one of
the access path fails, the client traffic will not be interrupted due to the existence of the
other access path.
From a security perspective, network resources should be protected from unauthorized
accesses and should not be used by unauthorized entities. Service access control is the
mechanism that limits and controls entities trying to access network resources, especially
via UNI and E-NNI. The Connection Admission Control (CAC) function should support the
following security features:
l
CAC is applicable to all entities accessed to network resources via UNI or E-NNI. An
authentication function of an entity should be included in order to prevent masquerade
(spoofing). Masquerade is fraudulent use of network resources by pretending to be
a different entity. An authenticated entity should be given a service access level in a
configurable policy basis.
1-20
SJ-20110728142617-001|2011-09-27(R1.0)
A corresponding mechanism should be set up at UNI and NNI to ensure the integrity
of client authentication and link information, such as link setup, release and signaling
information, in order to manage connections and guard against service intrusions.
CAC based billing information should be realized at UNI and E-NNI, in order to avoid
any fabrication of connection management information.
Each entity should be authorized to use network resources according to the
management policy of a carrier.
1.6.2 ASON Service Models

1.6.2.1 Enhanced Private Line Service
Enhanced private lines provide the enhanced leased service or private service, which are
assigned in real time or approximately real time by service Management Interfaces (MI) of
PC or SPC. They share the following features:
l
l
l
A connection should be requested via service management interface.

There is a relationship of client/server between a client device and optical network.
The optical network is invisible to clients. The setup of optical connections depends
on the intelligence of the network.
The management plane and control plane in ASON cooperates to realize an SPC, which
can provide services quickly. Clients just need to tell the carrier where and what kind of
service is needed. The carrier can set up satisfactory service connections almost in real
time through the management plane and control plane. In addition, the carrier can change
the service attributes fast in condition that lines between clients and carrier network can
meet the requirements.
1.6.2.2 BOD Service

BOD services are automatic connection services whose bandwidth is allocated on demand
via UNI signaling interfaces. Such connections, being switched connections, are set up in
real time. They share the following features:
l
l
l
A client device or its agent can initiate a connection request directly via UNI.
Optical network can be invisible or visible in a limited degree for clients according to
actual interconnection modes or network management policies.
A BOD service connection is based on the intelligence of either optical network or
client according to different interconnection models on the control plane.
When a connection is requested via UNI, optical transport network can set up/clear the
corresponding service connection as required. A client device must have the capability of
service discovery to get service information in the transport network via its UNI-N. During
setting up the connection, the service attributes must be found, including framing mode,
signal type, transparency and cascading mode.
Two request modes are optional when a client device requests a service connection via
UNI: direct request and indirect request. For direct request mode, UNI-C functions are
1-21
SJ-20110728142617-001|2011-09-27(R1.0)
implemented in a client device, which can directly request for services in a transport
network. For indirect request mode, UNI-C is independent of a client device. It performs
UNI functions on behalf of one or multiple client devices (as shown in Figure 1-9).
Figure 1-9 Direct and Indirect Request via UNI
1.6.2.3 OVPN
OVPN model provides the virtual private network service for a specific client group. It has
the following features:
l
l
l
l
l
Clients sign to use certain network resources, such as optical connection ports,
wavelengths, etc.
OVPN supports Closed User Group (CUG).
Optical connections for OVPN can be PC, SPC or SC, depending on different
assignment modes.
Any site in an OVPN can request to dynamically configure connections with other sites
in the same CUG.
A client has the visibility and control capability of network resources as its service
contract allows.
If the contract permits, the network resource can be visible and controlled by clients. An
optical transport network can be divided into multiple VPN. The network resources of each
part can only belong to one VPN. Authorized clients of an VPN can manage corresponding
resources of the network.
1-22
SJ-20110728142617-001|2011-09-27(R1.0)
1.6.3 Management of ASON Services

1.6.3.1 Service Policy on Management Plane
The management plane can assign the attributes of all kinds of connection services.
Normal connection management operations (such as connection release) will not lead
to protection and restoration. ASON supports the protection and restoration initiated by
the management plane for the convenience of maintenance, which forces traffic to be
switched to a protection circuit. The ASON management plane provides the following
service management functions:
l
l
l
l
l
End-to-end service assignment

Service setup and release
Service protection/restoration policy
Service attribute and service level agreement
OVPN management
ASON service management systems, supporting traditional service management

functions, are compatible with previous service management systems. The management
plane can customize service level protocols for different clients, providing them with
proper service policies to guarantee the service quality. The SLA-related services must
be flexible, easy and extensible.
1.6.3.2 OVPN Implementation and Management

OVPN has been applied on traditional transport network platform. A powerful management
plane is a prerequisite for the implementation of OVPN, which is established on the network
service layer management system. The management plane can identify multiple OVPNs
and set management areas. On the client service terminal, it can monitor alarm in the
management area, delete or set up a channel and query performance data. OVPN has a
firewall and other security measures to ensure the network security.
VPN is commonly applied on IP network. Its experience can be used on the distributed
ASON platform to develop and manage the OVPN service. Various OVPNs can be
divided based on internal addresses, assigned addresses, client addresses, service
types or areas. NEs in the same OVPN are visible to each other. It can provide the basic
functions of ASON such as protection/restoration, end-to-end service setup, etc. It can
also prevent illegal users from accessing to ensure the privacy of virtual network through
certain security measures.
1-23
SJ-20110728142617-001|2011-09-27(R1.0)
This page intentionally left blank.
1-24
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 2
ZXUCP A200 (WASON)

Function and Solution
Table of Contents
WASON Concepts and Solved Problems ...................................................................2-1
ZXUCP A200 Functions .............................................................................................2-2
ZXUCP A200 Solution ................................................................................................2-5
2.1 WASON Concepts and Solved Problems

2.1.1 Concepts of WASON
Wavelength Automatically Switched Optical Network (WASON) is an ASON based on the
WDM transport network, which is the standard of intelligent WDM recommended by IETF
standardization organization at present. In addition to the functions of traditional ASON,
WASON can solve such problems in the WDM network as fiber/wavelength automatic
discovery, online wavelength routing and routing based on damage model.
2.1.2 Problems Solved by WASON

ZXUCP A200 is a WASON control plane oriented for WDM/OTN devices, which is applied
in the mesh network with complex topology. The problems that can be solved by ZXUCP
A200 are as follows.
l
The traditional WDM network does not have a strong capability in the scheduling
of service wavelength and bandwidth. Most services can only support fixed
connection mode (PC), and the automatic optimized routing (SC and SPC) cannot
be implemented based on the use situation of network resources. Therefore, the
bandwidth request from clients cannot be responded quickly.
Generally, the traditional WDM network does not support the automatic discovery of
network links/wavelength resource status. Therefore, the status of network resources
cannot be updated automatically in real time. It can only be updated manually via the
network management system.
The survivability of traditional WDM network is solved through the ring networking
mode and the chain networking mode. In such modes, lots of bandwidths need to
be reserved for protection, and the capability of resisting multi-point faults is not
strong. The mesh networking cannot be provided with a good protection mode, and
2-1
SJ-20110728142617-001|2011-09-27(R1.0)
the protection by level is not supported for different service layers such as WDM
layer/SDH layer and WDM layer/IP layer.
In traditional WDM network, although interconnection and intercommunication
are supported at service interfaces for different vendors, the interconnection and
intercommunication cannot be realized for overall control of network.
The traditional WDM network does not support the network bandwidth request which
directly comes from end users, and cannot satisfy the demands for many new service
types such as Closed User Group (CUG), Optical Virtual Private Network (OVPN),
Bandwidth on Demand (BOD) and Provision Bandwidth Service (PBS).
Unlike SDH network application, to set up service connection in the networking with
WDM devices, the factors of physical optic characteristics (line attenuation, OSNR,
dispersion and channel power optimization) need to be fully taken into consideration.
That is, the effectiveness of connection set up by the WASON control plane protocol
based on the network topology information is largely depended on whether the
requirements of physical optic characteristics can be met for WDM network.
2.2 ZXUCP A200 Functions

Table 2-1 lists the product functions.
Table 2-1 ZXUCP A200 Product Functions
Function
Description
l
System management
l
l
Remark
System startup/reset, time

synchronization, IP address
Applied scenarios: protection
setting, online upgrade and
scenario and protection, control
active/standby status
plane scenario
management
Applied modes: manually
Queries the enabling/dis-
resetting the management plane
abling status.
and automatically resetting the
Uploads and downloads
control plane
the important data.

l
Sets and queries the

neighbor and link auto
discovery.
Creates and deletes

an controlled neighbor
Automatic discovery
automatically.
l
Automatically enables layer

adjacency discovery and
enables and disables the
transmission capability
discovery.
2-2
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 2 ZXUCP A200 (WASON) Function and Solution
Function
Description
l
Remark
Configures board
resources and fiber
connections in nodes
Transport resource
management
totally and partially.

l
Queries, modifies, reports

and refreshes information
of link interfaces.
Configures I-NNI nodes

for the first time and adds,
queries and modifies
parameters of the I-NNI
node.
Queries the I-NNI control

links in the whole network.
Control plane resource
management
Adds, queries and deletes

the I-NNI controlled
neighbors an transmission
interfaces.
l
Queries and modifies I-NNI

TE links and TE binding
links, querying the whole
network topology and
troubleshooting.
Creates/modifies and
deletes OCH service,
ODUk switching service
and ODUk mapping
service.
Modifies the grades of OCH

service, ODUk switching
Basic SPC service configuration
service and ODUk mapping
management
service (iron service,

copper service, silver
service, gold service and
diamond service).
l
Queries all SPC services

by service ID and service
creation time.
2-3
SJ-20110728142617-001|2011-09-27(R1.0)
Function
Description
l
Remark
Retries OCH service,

ODUk switching service
and ODUk mapping
service connection
;troubleshooting and
inspecting and clearing
Basic SPC service running and

maintenance
residual connection
l
Specifies original
connection, reroute
blocking, optimizing reroute
and support and supporting
external commands of SPC
service protection
Pre-calculates routes
before creating services
SPC service extension
Restoring routes by
manually pre-setting and

using the routes
l
Supports the routes

policies of minimum costs,
minimum hops of OCH
service, ODUk switching
service and ODUk mapping
service, load balance
and optical impairment
verification
Supports strict explicit

route/including, excluding
specific network
resources and protection
SPC service route calculation
independence policy
l
Supports reroute policies

of coinciding with original
routes as much as possible,
separating from original
routes as much as possible
and restoring the optimal
routes
Supports single layer

(optical layer, electrical
layer) and multiple layer
scenario; supporting
electrical layer link binding
2-4
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 2 ZXUCP A200 (WASON) Function and Solution
Function
Description
l
Remark
Supports the copper

service, gold service and
diamond service
Supports manual
pre-setting mode and
auto presetting mode
Supports optical link 1+1

protection, 1+1 OCH
protection, optical channel
shared protection ring and
1+1 protection networking
at client side
Supports low order ODUk

SNC1+1 protection, low
order ODUk shared ring
network, low order Pcycle
Transport plane protection
Mesh shared protection,
low order ODUk SNC1+1

protection and high order
ODUk shared ring network
l
Supports to freeze/reset
external commands,
protection group protocols
and to query protection
group status, switching
events and synchronization
switching action
Supports to query alarms,

report alarms, set and
Alarm, time and performance

management
query alarms screen

l
Supports to query control
system events, report the

events on control plane
2.3 ZXUCP A200 Solution

The ZXUCP A200 product of ZTE Corporation provides an integrated WASON solution.
l
l
Control plane software: ZXUCP A200

Transport plane devices
At the access and convergence network layers: compact ZXMP M720 series with
high integration and low power consumption.
2-5
SJ-20110728142617-001|2011-09-27(R1.0)
In the metro core network: ZXMP M820, ZXONE 8300 with high capacity and
electrical/optical cross-connect capability for multiple services.
In the backbone network: intelligent ZXWM M920 and ZXONE 8500 series that
support high capacity (3.2 TB) and ultra long haul (ultra long span).
Network management software: NetNumen U31 and the WASON control plane
together implement unified management for NEs.
Figure 2-1 illustrates the integrated WASON solution of ZTE.

Figure 2-1 Integrated WASON Solution of ZTE
2-6
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 3
ZXUCP A200 Debugging

Table of Contents
Initialization Configuration Flow ..................................................................................3-1
Initialization Configuration ..........................................................................................3-2
3.1 Initialization Configuration Flow

An NE needs to be initialized before providing WASON functions. The initialization
procedure, which also includes loading the application and logical programs, is
implemented before the debugging of the ZXUCP A200 product. Figure 3-1 shows the
initialization flow.
3-1
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 3-1 WASON Initialization Configuration Flow Chart
3.2 Initialization Configuration

3.2.1 Preparation for Hardware
The ZXUCP A200 hardware module consists of an AGENT module and a WASON module
on an SNP board. The AGENT module and WASON module use different SD cards and
ECM-A subcards.
3-2
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 3 ZXUCP A200 Debugging
3.2.2 Updating and Downloading Boot/Fpga Program

Boot and Fpga are integrated in one bin file. Firstly, check if the Boot/Fpga program is
available in the BootROM. If not, a programmer is needed; if yes, update the program
online using the telnet mode.
Programmer
This step varies with different programmers, which will not be described any further here.
The method of judging if Boot/Fpga is available in a chip is described as below:
1. Switch the DIP switch 4 of the ECM-A module to "on".
2. Power on the board and then observe the indicators (the middle two indicators on the
SNP board). If they flash quickly, it indicates that the programs are available in the
BootROM.
Telnet mode
To use this mode, the Boot/Fpga must have been written into the chip.
1. Switch the DIP switch 2 of the ECM-A module to "on".
Note:
The purpose of switching the DIP switch 2 to "on" is to make the forced IP
<192.192.192.12> of the module effective (merge the VLANs first before using the
forced IP ). If the WASON module can be pinged successfully with other IPs, the
switching is not a must.
2. Add an IP address of "192.192.192.xx" on the local computer. The subnet mask is

"255.255.255.0", and the range of "xx" is (0, 10)(13, 255).
3. Power on the board, and then open the CMD command line window on your computer.
4. Type telnet 192.192.192.12 9023 and then press Enter.
5. Set the Current Path of the tftp software interface as the path where the *.bin
Boot/Fpga program file is saved.
6. In the Server Interface of the tftp software interface, select the local IP address
"192.192.192.xx" that can be connected to the destination module (ECM-A).
7. Type tftp 192.192.192.xx -g *.bin and then press Enter.
8. Type q and then press Enter.
9. Type prg boot and then press Enter.
10. Type reset and then press Enter.
3.2.3 Updating and Downloading App Application Program

The download and update of WASON application program is almost the same as the Telnet
mode of Boot/Fpga except for changing prg boot to prg at step 9. Refer to the section of
3-3
SJ-20110728142617-001|2011-09-27(R1.0)
"Updating and Downloading Boot/Fpga Programs" for details. If the indicators flash slowly,
it indicates that the App application program is downloaded successfully.
Caution!
To download the App application program, the Boot/Fpga program must have been
downloaded and updated.
Downloading App is different from updating Boot/Fpga in the following items:
l
l
App can be downloaded through EMS.

The Telnet IP address for downloading App is different from that for updating
Boot/Fpga.
3.2.4 Formatting SD Card

Generally, an SD card needs to be formatted if it is used for the first time. Follow the
procedure below to judge if an SD card needs to be formatted and how to format it.
Caution!
To format the SD card, the App program must be available.
1. Connect the serial port line to the SNP board, so it can print out the starting information
of the WASON module. Be cautious of the difference of the serial port connectors
between the WASON module and the AGENT module.
2. Press the reset hole to restart the SNP board.
3. Watch the serial port for the print result. If mount sd failed appears, it indicates that the
mounting of SD card is not successful. In this case, the SD card needs to be formatted
provided that the card is not damaged. If mount sd successful appears, it indicates that
the SD card functions well and does not need to be formatted.
4. To format the SD card, type umount(), and then press Enter.
Caution!
When unmounting the SD card, ensure that the current file directory of WASON system
is not under /sd.
, and then press Enter.

5. After umount sd successful appears, type formatsd
6. Type reset, and then press Enter. Now the SD card can be used after restart.
3-4
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 4
ZXUCP A200 Configuration

Management
Table of Contents
Overview ....................................................................................................................4-1
Enabling the Control Plane ........................................................................................4-4
Node Management.....................................................................................................4-6
Configuring the Automatic Discovery ..........................................................................4-8
Configuring I-NNI Interface .......................................................................................4-11
Configuring TE Links ................................................................................................4-19
Control Plane Running Topology ..............................................................................4-22
Call Management .....................................................................................................4-24
Synchronizing SPC Services ....................................................................................4-60
SPC Service Maintenance........................................................................................4-61
Enabling the Autodiscovery (non-WASON)...............................................................4-64
Bundled Links...........................................................................................................4-65
Configuring Optical Impairment Parameters .............................................................4-67
Connection Crankback Policy...................................................................................4-72
Comparing Topology Links .......................................................................................4-74
PCE Configuration....................................................................................................4-76
4.1 Overview
4.1.1 Network Topology
This chapter takes the topology map shown in Figure 4-1 as an example to describe the
operations.
4-1
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-1 Network Topology Map
Note:
Only when NEs involved have been configuredyou can configure ZXUCP A200. Refer to
NetNumen U31 Operation Guide for the NE environmental configuration.
Only when the board has no SPC service, the WASON accepts board property changes
(except for the quantity and board port S.N.) in the network management system.
In this manual, all operations are performed through the NetNumen U31 network
management software, and the ZXMP M820 is taken as an example. The WASON
service configuration operations for other ZTE transmission equipment with the WASON
function are slightly different.
4.1.2 Management Interface

In the Main View window of the NetNumen U31 client, right-click a WASON NE and select
WASON Management. A window appears, as shown in Figure 4-2. The meanings of
these submenus are described in Table 4-1.
4-2
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 4 ZXUCP A200 Configuration Management
Figure 4-2 WASON Management Menu
Table 4-1 Meanings of WASON Management Submenus

Submenu
Meaning
Control Plane Enable
Enables or disables the control plane.
Node Parameters
Configures the parameters of a WASON NE, such as node ID.

Sets the global automatic discovery parameters. The management
Global Autodiscovery
plane can set the automatic discovery mode of the control plane, as
Parameters Config
well as the automatic activation mode of transmit interfaces on the

control plane.
I-NNI Interface Config
Configures the transmit interface, out-of-band control interface and

out-of-band neighbor of the current NE.
Queries the TE link information of the local NE and the global network,
TE Link Config
and sets the TE link parameters of the local node, such as weight and
SRLG.
Control Plane Running
Queries the running topology of the signaling network, that is, the
Topology
signaling network topology in the OSPF routing database.
4-3
SJ-20110728142617-001|2011-09-27(R1.0)
Submenu
Meaning
Enables the automatic discovery function. This item is used for the
Autodiscovery Enable
management plane to set the electric layer boards of the transport

plane, and is related to the automatic discovery function of the electric
layer.
Bundled Link
Bundles links. A bundled link is issued as a group of links to avoid

resource waste.
Optical Impairment
Configures optical impairment parameters, including OSNR, dispersion,
Parameters Config
and PMD.
Protocol Parameters Config
Connection Crankback
Policy
Queries and sets the parameters of the signaling protocols used on

the control plane.
Sets the connection crankback policy. If blocking occurs during service
connection setup or restoration, a crankback operation is performed
first according to the set parameters.
Manages the connectivity between internal interfaces so as to ensure
Link Interface Connectivity
that the internal interfaces are connected correctly in the abstract nodes
through configuring boards and fiber links.
Compares the fiber link configurations of the management plane
Topo Link Compare
with those of the control plane. The fiber link configurations of the
management plane will overwrite the control plane information if
differences exist.
Call Management
Adds, deletes, modifies, and queries SPC services.

Synchronizes SPC services, so that the SPC service information in the
SPC Synchronization
network management system is consistent with the actual SPC service

information on the control plane.
SPC Maintenance
Maintains SPC services, including modifying the service status,

modifying restoration activation, and modifying protection parameters.
Separates the resourcess on the management plane from those on
Link Resource Assignment
the control plane so as to solve the conflicts between the PC service

and SPC service resources.
4.2 Enabling the Control Plane

4.2.1 Operation Purpose
Use this procedure to enable or disable the control plane through the network management
system. You may manually enable or disable the control plane so as to load or download
the control plane.
4-4
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
You need to enable the control plane when you want to enable the WASON.
When you disable the control plane, the system only supports the protection function.
4.2.2 Operation Description

Context
l
l
You have the user permission to operate this function.

There are NEs supporting this function in the system.
Steps
1. In the Topology Management view, right-click a WASON NE and then select WASON
Management > Control Plane Enable. The Control Plane Enable dialog box opens,
as shown in Figure 4-3.
Figure 4-3 Enabling the Control Plane Window
2. Select the Enable check box to enable the WASON. Click Apply.
4-5
SJ-20110728142617-001|2011-09-27(R1.0)
Note:
The status of enabling the control plane will not be changed until the reset is completed.
Therefore, before the reset, the queried control plane enabling status is unchanged.
When the control plane is not enabled, service on it cannot be configured. You can
configure nodes on the control plane after enabling it.
End of Steps
Result
The control plane is enabled.
4.3 Node Management

Use this procedure to configure the identification parameters of a WASON node. A
WASON node cannot be managed in the network management system until its properties
are configured. The parameter configuration on nodes only affect the nodes but not other
functions.
After you configure the node parameters, you need to configure the SOSC static routes to
ensure that the WASON services are set up properly.

Prerequisites
l
l
You have the rights to operate this function.

You have created the WASON NE.
Context
l
l
l
l
A node ID can be set for an enabled WASON NE only.

By default, the node ID of an NE is the NE IP address(0.0.0.0) plus 1. Assume the
IP address of the NE is 192.90.1.4, then the node ID is 192.90.1.5 by default. You
should, however, manually change the node ID to another IP address that is not in
the same network segment as the IP address of the NE and not in the same network
segment as any internal IP address (192.168.x..x) of the NE.
When a WASON NE is started for the first time, the node parameters should be
configured first and the NE should be reset before other parameters are configured.
If SPC services are configured on a WASON NE, the node ID of the NE cannot be
modified.
4-6
SJ-20110728142617-001|2011-09-27(R1.0)
Steps
Management > Node Config. A dialog box pops up, as shown in Figure 4-4.
Figure 4-4 Node Configuration Window
2. The Node ID is a 4-byte integer and uses an IPv4 address as defined in the protocol.
The default value is the NE IP address plus 1. This parameter uniquely identifies a
WASON node on the control plane.
End of Steps
Result
The node properties are configured.
Follow-Up Action
After you configure the node parameters, you need to add SOSC static routes.
1. Right-click an NE, the card view appears.
Right click SOSC to select NE
Management. The NE management window appears.
2. In the Board Operation in the NE Management window, select Communication
Maintenance > Static Route Config, the static route configuration window appears.
4-7
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-5 Static Route Configuration Window
3. Click Add to add a static route. Set the Target IP Address to the node ID, set
the Target Subnet Mask to (255.255.255.255), and set Gateway IP Address to
the address of WASON address. Click Apply to complete the configuration. After
configuring the SOSC static route, you need to reset the SOSC board to enable it.
4.4 Configuring the Automatic Discovery

The management plane can set the automatic discovery mode of the control plane,
including the control channel, transmit interface, layer neighbor, and transmit capability
discovery. For example, the management plane can enable or disable the automatic
discovery function of the entire control plane. In addition, the management plane can
control the specific network layer (TDM/LSC) to which the automatic discovery function
applies.
The management plane can also set the automatic activation mode of transmit interfaces
on the control plane.
l
The increasingly larger-scale networks and more complicated topologies make

setting connections between NEs and tracing change very time consuming and
error prone. In such circumstances, the connections between NEs need to be
automatically checked and discovered, which is generally called automatic discovery
in this manual.
The management plane may set the automatic discovery mode on the control plane,
including the control channel, transport interface, layer adjacency, transport capacity
4-8
SJ-20110728142617-001|2011-09-27(R1.0)
discovery, for example, enabling or disabling the automatic discovery on the whole
control plane. Furthermore, the management plane can determine which layer the
automatic discovery is located on (TDM/LSC).
The automatic discovery on the control plane needs to meet the requirements of
ITU-T G.7714, mainly including automatic adjacent layer discovery, automatically
discovering and refreshing the topology and exchanging the discovery information
through the overhead bytes (the overhead bytes belongs to data and irrelative with
the signaling).
Neighbor auto discovery function: In the intelligent optical network, one network
control plane node can automatically discover adjacent control plane nodes and
establish the neighborhood through the standard protocol and notify other nodes on
the control plane via flooding. After new nodes are added on the network, the nodes
involved in the control plane can automatically discover the corresponding neighbor
changes and notify to other nodes. When a fiber between neighbors is broken, the
neighbor auto discovery failure alarm will be reported.
Link auto discovery: In WASON network, the control plane node can discover the
optical layer link information in threshold through standard protocols, including link
changes in status property (link port information, link capacity) and notify nodes on
the other control plane via flooding.
Fiber connection error detection: Automatically detects the remote error occurred
during the fiber re-connection caused by fiber faults or checks connection errors on
transport ports on OCh/ODUk layers.

Prerequisites
l
l

You have successfully queried the global automatic discovery configuration
information.
Context
Obey the following principles when setting the automatic activation mode of a transmit
interface.
When the control plane automatically discovers the transmit interface ID, layer adjacency,
and transmission capability of a link, it cannot determine whether the link meets the user's
requirements. Therefore, certain parameters need to be configured to determine whether
to use the discovered link. If the link is used and the layer adjacency changes, an alarm
will occur. If the link is used and the layer adjacency does not change, no alarms will
occur. The configuration operation described in this section is applicable to the following
scenarios:
l
During initial configuration, you can set Transmit Interface Automatic Activation
to "Manual Activation" to avoid incorrect layer adjacency caused by fiber connection
4-9
SJ-20110728142617-001|2011-09-27(R1.0)
errors (For example, port A should be connected to port B but is wrongly connected
to port C).
After the network configuration is finished, you can set Transmit Interface Automatic
Activation to "Automatic" after verifying the correctness of the layer adjacency. Then,
the control plane will automatically activate all the links not yet activated.
Steps
1. In the Topology Management view, right-click a WASON NE, and then select WASON
Management > Global Autdiscovery Parameters Config. A dialog box opens, as
shown in Figure 4-6.
Figure 4-6 Configuring Global Automatic Discovery Parameters Window
2. Table 4-2 describes the Global Parameters Automatic Discovery Config dialog box.
Table 4-2 Global Automatic Discovery Parameter Config Dialog Box
Item
Description
Control Interface Neighbor
The options include "Automatic Discovery" and "Manual" (default
Discovery Mode
value).
Layer Network Switching
The options include "TDM" and "LSC". TDM represents the ODUk
Capacity
layer, whereas LSC represents the OCh layer. When the transmit
interface is an interface on the OA board, this parameter is set
to "LCS". When the transmit interface is an interface on the LD
board, this parameter is set to "TDM".
4-10
SJ-20110728142617-001|2011-09-27(R1.0)
Item
Description
Layer Network Encode
Type
OCh layer: Sets the Layer Network Switching Capacity to be

LSC, and sets the Layer Network Code Type to be G.709
Optiacl Channel
ODUk layer: set the Layer Network Switching Capacity to be

TDM, and sets the Layer Network Code Type to be G.709
ODUk
Layer Adjacency Discovery
Mode
value). This parameter can be set to "Automatic Discovery" only

when Local Transmit Interface Discoverable Mode is set to
"Automatic Discovery".
Interface Capacity
Discovery Mode
value). This parameter can be set to "Automatic Discovery" only

when layer Adjacency Discovery Mode is set to "Automatic
Discovery".
Note:
For the automatic discovery of ODUk links, you also need to configure the automatic
discovery function of ports on service boards. For details, refer to the section of 4.14
Enabling Autodiscovery (Non-WASON).
End of Steps
Result
The global automatic discovery parameters are configured.
4.5 Configuring I-NNI Interface

The I-NNI interface configuration includes the configurations for the transmit interface,
out-of-band control interface and out-of-band neighbor. In a WASON device, resources
need to be allocated. The resources allocated for the control plane are used and
scheduled by WASON, while the resources allocated for the management plane are used
and scheduled by the network management system. At present, the resource allocation
granularity of the optical-layer transmit interface is at the wavelength level, and the
resource allocation granularity of the electrical-layer transmit interface is at the ODU level.
4-11
SJ-20110728142617-001|2011-09-27(R1.0)
Transmit interface configuration: transmit interfaces represent some basic attributes

of data transmission links and operations independent from TE links under some
constrains conditions are allowed. The nodes in domain is called I-NNI transmit port.
Out-of-band control interface configuration: out-of-band control interfaces are mainly
used for controlling the communication between plane nodes/external PCE nodes and
other nodes in the same control domain. To guarantee the communication, one ASON
and external PCE node can support more than one I-NNI control interfaces.
Out-of-band neighbor configuration: To control an out-of-band neighbor ASON node is
to create an control channel of bearer signaling between nodes. I-NNI control neighbor
management and maintenance is to manage and maintain I-NNI control channels
between ASON nodes.

Prerequisites
l
l

You have installed certain boards supporting this function in the network management
system.
Context
l
Automatic discovery parameters of transmit interfaces

The management plane can control the automatic discovery mode of each transmit
interface, including the layer adjacency and transmit capability of each transmit
interface. However, the layer adjacency and transmit capability of a transmit
interface can also be controlled through global automatic discovery parameters.
When the Layer Adjacency Discovery Mode is "Automatic Discovery" or "Manual",
the automatic discovery mode of the transmit interface is irrelevant with the global
automatic discovery mode. When it is "Same as Global Setting", the global automatic
discovery mode is used for the transmit interface.
The following conditions need to be met so as to modify the layer adjacency

information of a transmit interface:
You can freely modify the layer adjacency information of a transmit interface when
the discovery mode of the transmit interface is "Manual" and the status of the
transmit interface is "Initial".
You cannot modify the layer adjacency information of a transmit interface when
the discovery mode of the transmit interface is "Manual" but the status of the
transmit interface is "Enable" or "Disable".
You cannot modify the layer adjacency information of a transmit interface when
the discovery mode of the transmit interface is "Automatic Discovery".
The following conditions need to be met so as to modify the transmit capability

information of a transmit interface:
4-12
SJ-20110728142617-001|2011-09-27(R1.0)
You can freely modify the transmit capability information of a transmit interface
when the discovery mode of the transmit interface is "Manual" and the status of
the transmit interface is "Initial".
You cannot modify the wavelength or timeslots occupied by the service when the
status of the transmit interface is "Enable" or "Disable".
Layer adjacency information refers to parameters of Remote Node, Remote Transmit

Interface, and Remote TE Link. None of the three parameters can be set to 0.
Transmit capability information refers to parameters Switching Capability, Encoding,
Wavelength Count, and Wavelength Information. None of these parameters can be set
to an invalid value.
Steps
Management > I-NNI Interface Config. Click the Transmit Interface tab to open the
Transmit Interface tab, as shown in Figure 4-7.
Figure 4-7 I-NNI Interface Config - NET-E Window
2. Click Add in the bottom right corner of the dialog box. The I-NNI Transmit Interface
Property dialog box opens, as shown in Figure 4-8. Table 4-3 describes the
parameters in the I-NNI Transmit Interface Property dialog box.
4-13
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-8 I-NNI Transmit Interface Property Dialog Box
Table 4-3 Description of the I-NNI Transmit Interface Property Dialog Box
Item
Description
Switching Capability
This parameter is set to "LSC" (indicating the OCh layer) if the transmit
interface is an interface on the OA board, or "TDM" (indicating the
ODUk layer) if the transmit interface is an interface on the LD board
or other boards of the same type.
LMP Transmit
CLMP data link verification mode, the default value is Link Outband
Mechanism
Verifying.
Transmit Interface
Uniquely identifies a transmit interface. It can be an OTS inbound

port on the OPA, OLA, HOPA, HOLA, EOPA, EONA, EOLA, SEOPA,
SEOLA, SDM, or SSDM board, or an OCH inbound port on the LS3/LD2
board or other boards of the same type. The value of this parameter
cannot be modified once successfully configured.
4-14
SJ-20110728142617-001|2011-09-27(R1.0)
Item
Description
Send Interface
Indicates the physical transmit interface in the outbound direction, which

can be an OTS outbound port on the OBA, OLA, HOBA, HOLA, EOBA,
EONA, EOLA, SEOBA, SEOLA, SDM, or SSDM board of the local
node, or an OCH outbound port on the LS3/LD2 board or other boards
of the same type. The value of this parameter cannot be modified once
successfully configured.
TE Link
Indicates the local TE link ID of the transmit interface, which is

automatically generated by the control plane. Currently, the value of
this parameter is the same as the local ID of the transmit interface.
Type "0" during the configuration. The management plane can query
or automatically discover and report the configured value after this
parameter is successfully configured.
Remote Transmit
Indicates an OTS inbound port on a board, such as OPA, OLA, HOPA,
Interface
HOLA, EOPA, EONA, EOLA, SEOPA, SEOLA, SDM, and SSDM, or an

OCH inbound port on the LS3/LD2 board or other boards of the same
type. The value of this parameter can be modified.
Remote TE Link
Indicates the TE link ID of the remote transmit interface.
If Virtual Interface
Automatically generates control planes.
Resource Partition
Sets the wavelength rate and central frequency of the configured

wavelength.
3. Click Add in the bottom right corner in the I-NNI Transmit Interface Property dialog
box. The I-NNI Interface Wavelength Property dialog box opens, as shown in Figure
4-9.
4-15
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-9 I-NNI Transmit Interface Wavelength Property Dialog Box
The wavelength properties of an I-NNI transmit interface can be modified after you
successfully configure the transmit interface.
4. Click the Out-of-band Control Interface tab in the I-NNI Interface Config window.
The Out-of-band Control Interface page is displayed, as shown in Figure 4-10. Table
4-4 describes the Out-of-band Control Interface page.
4-16
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-10 I-NNI Interface Config Window (Out-of-band Control Interface)
Table 4-4 Description of the Out-of-band Control Interface Page

Item
Port
Description
Indicates the Ethernet port number. An OSC board has four Ethernet
ports. Currently, at most 16 Ethernet ports can be configured.
IP Address
Indicates the local IP address of the control interface. It is a 4-byte

IP address and must be different from the node ID. Currently, only
one IP address can be configured for an Ethernet interface.
Mask
OSPF Protocol
Indicates the subnet mask of the control interface IP address.

Indicates the OSPF switch of the interface to which the control
channel belongs. This parameter can be set to "Enable" or
"Disable".
5. Click the Out-of-band Neighbor tab in the I-NNI Interface Config window. The
Out-of-band Neighbor page is displayed, as shown in Figure 4-11. Table 4-5
describes the Out-of-Band Neighbor page.
4-17
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-11 I-NNI Interface Configuration Window (Out-of-band Neighbor)
Table 4-5 Description of the Out-of-band Neighbor Page

Item
Description
Z End Node
The node ID of the neighbor node
Z End IP
Indicates the IP address of the control port on the remote neighbor

node.
Next Hop IP
Indicates the next-hop IP address in the format of an IPv4 address.

The default value is all 0-s.
Work Mode
Indicates the work mode of the out-of-band neighbor. The options

include "NM Config" and "Automatic Discovery". The value of this
parameter cannot be modified once successfully configured.
End of Steps
Result
The I-NNI interface configuration is finished.
4-18
SJ-20110728142617-001|2011-09-27(R1.0)
4.6 Configuring TE Links

After I-NNI transmit interface information is configured, the control plane can automatically
generate TE links based on the allocated resources. You can query the TE links that use
the transmit interface on an WASON node as the source, check the running status of TE
links on the network topology, and modify certain attributes of TE links so as to guarantee
the optimal path.
Note:
When this function is enabled, users can select various overhead modes. Only when the
overhead modes if all the nodes in the network are consistent, the automatic discovery
function can implemented.

Prerequisites
l
l
l

You have the right to manage WASON devices.
You have configured the I-NNI transmit interface information.
Context
After confirming the failure of control communication between two neighboring nodes, the
control plane will actively report the corresponding TE link information and an "LMP Hello
Fault" alarm. Upon receipt of the TE link information, the management plane needs to
update relevant attributes, such as TE link weight and link status.
When detecting the restoration of control communication between the two neighboring
nodes, the control plane will actively report the corresponding TE link information and
an "LMP Hello Fault" recovery message. Upon receipt of the TE link information, the
management plane needs to update relevant attributes, such as TE link weight and link
status.
Steps
Management > TE Link Config. The Local Config dialog box opens, as shown in
Figure 4-12.
4-19
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-12 TE Link Config (Local Config) Window
Click Refresh in the bottom right corner of the page to show the TE link configuration
information of the node. Modify certain parameters, such as weight, when necessary.
Table 4-6 describes the Local Config page.
Table 4-6 Description of the Local Configuration
Item
Description
User Label
System generates NE ID automatically.
Source Port
Indicates the source port of the TE link.
Sink Port
Indicates the destination port of the TE link.
Weight
Indicates the weight of the TE link. The value range is [1,(2^24)-1],

and the default value is 50.
SRLG
Indicates the SRLG. The same SRLG settings apply to TE links in the
same interface (shared protection or logical subnet protection group
interface). In other words, when you modify the SRLG settings of one
TE link, the SRLG settings of the other TE links in the interface are
also modified. The network management system, however, should
ensure that the SRLG values do not repeat. The default value is 0,
and the maximum value is 5. The value range is 0-65535. The SRLG
values cannot repeat.
Protection Type
Indicates the protection type of the TE link. Currently, the links

carrying extra services will not be flooded. This parameter can
be set to "Extra Traffic", "Unprotected", "Shared", "Dedicated 1:1",
"Dedicated 1+1", or "Enhanced".
4-20
SJ-20110728142617-001|2011-09-27(R1.0)
Item
Description
Link State
Indicates the current status of the TE link. The link status can be
"Normal", "Alarm", or "Degrade".
Bundled Link
Indicates whether the link is a bundled link.
FA Generation
Indicates the link generated by optical layer.
Component Link
Indicates the number of member links.
Number
Total Bandwidth
Indicates the total TE link bandwidth, including the idle bandwidth

and the allocated bandwidth. This parameter is in the unit of TSs for
ODUk links, and in the unit of wavelengths for OCh links.
Available Bandwidth 1
This parameter is in the unit of ODU1 for ODUk links, and in the unit
of OCh at 2.5 G for OCh links.
of OCh at 10 G for OCh links.
of OCh at 40 G for OCh links.
of OCh at 10G for OCh links.
This parameter is in the unit of ODU0 for ODUk links, and is invalid
for OCh links.
This parameter is in the unit of ODU2e for ODUk links, and is invalid
for OCh links.
This parameter is in the unit of ODUflex for ODUk links, and is invalid
for OCh links.
2. In the TE Link Config dialog box, click the Whole Network Query tab. The TE Link
Config window is shown in Figure 4-13.
4-21
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-13 TE Link Config (Whole Network Query) Window
Click Refresh in the bottom right corner of the dialog box to show the TE link
configuration information of all NEs.
End of Steps
Result
The TE link configuration is finished, and the TE link configuration information of all NEs
can be queried.
4.7 Control Plane Running Topology

The control plane running topology refers to the data communication network topology
used for OSPF flooding and Resource Reservation Protocol (RSVP) signaling.
Use this procedure to query the running topology of the signaling network, that is, the
signaling network topology in the OSPF routing database.

Prerequisites
l

4-22
SJ-20110728142617-001|2011-09-27(R1.0)
You have created WASON devices.
Steps
Management > ControlPlane Run Topo. A dialog box opens, as shown in Figure
4-14.
Figure 4-14 Control Plane Running Topology Dialog Box
2. Click Refresh in the bottom right corner of the dialog box to refresh the control plane
running topology.
End of Steps
Result
The control plane running topology is displayed.
4-23
SJ-20110728142617-001|2011-09-27(R1.0)
4.8 Call Management

The call management function of ZXUCP A200 supports to create, modify and delete
diamond, gold, silver, copper, and iron services and services related to SPC.
l
The services include optical-layer services and electrical-layer services. Prerequisites

for setting up these services are described as follows:
Item
Prerequisites
Electrical-layer services
Configures the board mapping on boards at

the electrical-layer client side.
There are corresponding optical-layer TE

links or electric layer TE links.
Optical-layer services
There are corresponding optical-layer TE

links.
For OCh service, you must configure the electrical-layer line side mapping.
Before setting up services with protection and services without protection. Note the
following precautions.
Item
Precaution
Service with protection
If the optical-layer service to create is transmitted between the line side of an opticallayer service board and an optical-layer transmitting port through an OP board, the service
must have the protection.
When creating an electrical-layer service, because the electrical cross-connection board

has the protection, the boards at the electrical-layer client side may create services with
protection or without protection.
Service without protection
When creating an optical-layer service, if no

OP board is configured, only service without
protection can be created.
When creating an electrical-layer service, because the electrical cross-connection board

has the protection, the boards at the electrical-layer client side may create services with
protection or without protection.
4-24
SJ-20110728142617-001|2011-09-27(R1.0)
Services include services with electrical-layer cross-connection and services without

electrical-layer cross-connection.
l
l
l
MAP combination mode-OAC port establishment: creating electrical-layer services

without the electrical cross.
SWITCH combination mode-OAC port establishment: creating electrical-layer
services with the electrical cross.
SWITCH combination mode-OCH port establishment: creating optical-layer services
with the electrical cross.
Attributes of the MAP combination mode-OAC port service establishment are shown in
Table 4-7.
Table 4-7 MAP Combination Mode-OAC Port Service Establishment Grade
Grade
OAC
OCh
OM(
T)S
Dia-
PP
RR
ODUk
OCh
Protec-
Restor-
Service
Pro-
Protec-
Restor-
Ser-
Pro-
tion
ation
Resto-
tection
tion
ation
vice
tection
ration
Switch-
Resto-
Swit-
Rever-
ing Re-
ration
ching
sion
version
Rever-
Rever-
sion
sion
Dy-
Non-re-
Perma-
Link dy-
Non-
Non-re-
mond
nent
namic
reve-
version
namic
version
service
1+1
rerout-
sion
Autom-
rerout-
Manual
protec-
ing
Autom-
atic re-
ing
rever-
atic re-
version
tion
-
PP+
RR
Gold
TP
RR
service
TP+
version
Link
atic re-
Non-re-
nent
1+1
tion
protec-
atic re-
tion
version
1+1
Link dy-
Non-re-
Non-re-
OCH
namic
version
version
protec-
rerout-
Manual
Autom-
tion
ing
rever-
atic re-
sion
version
1+1
tion
RR
Autom-
Perma-
protec-
protec-
sion
1+1
Link
RR
TP
version
version
Autom-
Non-re-
version
Manual
1+1
Dy-
rever-
Non-re-
OCH
namic
sion
version
protec-
rerout-
Autom-
Autom-
tion
ing
atic re-
atic re-
version
version
Link
Manual
rever-
1+1
rever-
sion
protec-
sion
Autom-
tion
Autom-
Automatic reversion
Manual
4-25
SJ-20110728142617-001|2011-09-27(R1.0)
Grade
OAC
OCh
OM(
T)S
Silver
TP
service
TP
ODUk
OCh
Protec-
Restor-
Service
Pro-
Protec-
Restor-
Ser-
Pro-
tion
ation
Resto-
tection
tion
ation
vice
tection
ration
Switch-
Resto-
Swit-
Rever-
ing Re-
ration
ching
sion
version
Rever-
Rever-
sion
sion
1+1
atic re-
atic re-
version
version
Non-re-
OCH
version
protec-
Autom-
tion
atic reversion
Link
1+1
Non-re-
1+1
OCH
version
protec-
protec-
Autom-
tion
tion
atic reversion
TP
Link
1+1
protection
Cop-
RR
Link dy-
Non-re-
per
namic
service
rerouting
Dy-
Non-re-
version
namic
version
Manual
rerout-
Manual
rever-
ing
rever-
sion
Iron
sion
Autom-
Autom-
atic re-
atic re-
version
version
service
Attributes of the SWITCH combination mode-OAC port service establishment are shown
in Table 4-8.
4-26
SJ-20110728142617-001|2011-09-27(R1.0)
Table 4-8 SWITCH Combination Mode-OAC Port Service Establishment Grade

Grade
LO
HO
ODU
ODU
Dia-
PP+
mond
RR
OCh
OM(T)
S
ODUk
OCh
Pro-
Res-
Ser-
Pro-
Pro-
Res-
Ser-
Pro-
tec-
tora-
vice
tec-
tec-
tora-
vice
tec-
tion
tion
Res-
tion
tion
tion
Res-
tion
tora-
Swit-
tora-
Swit-
tion
ching
tion
ching
Re-
Re-
Re-
Re-
ver-
ver-
ver-
ver-
sion
sion
sion
sion
Per-
Dy-
Non-
Non-
ma-
namic
rever-
rever-
ser-
nent
rerou-
sion
sion
vice
1+1
ting
Man-
Auto-
pro-
ual re-
matic
tec-
ver-
rever-
tion
sion
sion
Dy-
Automatic
reversion
PP+
RR
RR
Per-
Dy-
Non-
Non-
ma-
namic
rever-
rever-
namic
nent
rer-
sion
sion
rerou-
1+1
out-
pro-
ing+L-
tec-
ink dy-
tion
namic
ting
rerouting
Gold
TP+
ser-
RR
vice
1+1
Dy-
Non-
Non-
OCH
namic
rever-
rever-
pro-
rerou-
sion
sion
tec-
ting
Man-
Auto-
ual re-
matic
ver-
rever-
sion
sion
tion
Automatic
reversion
-
RR
Dynamic
Dynamic
4-27
SJ-20110728142617-001|2011-09-27(R1.0)
Grade
LO
HO
ODU
ODU
OCh
OM(T)
S
ODUk
OCh
Pro-
Res-
Ser-
Pro-
Pro-
Res-
Ser-
Pro-
tec-
tora-
vice
tec-
tec-
tora-
vice
tec-
tion
tion
Res-
tion
tion
tion
Res-
tion
tora-
Swit-
tora-
Swit-
tion
ching
tion
ching
Re-
Re-
Re-
Re-
ver-
ver-
ver-
ver-
sion
sion
sion
sion
rer-
rerou-
out-
ting
ing+Link dynamic
rerouting
RR
TP
Link
Dy-
Man-
1+1
namic
ual re-
1+1
pro-
rerou-
ver-
pro-
tec-
ting
sion
tec-
Auto-
tion
tion
Link
matic
reversion
Silver
TP
1+1
Non-
ser-
OCH
rever-
vice
pro-
sion
tec-
Auto-
tion
matic
rever-
Link
sion
1+1
-
TP
pro-
Link
tec-
1+1
tion
protection
4-28
SJ-20110728142617-001|2011-09-27(R1.0)
Grade
Cop-
LO
HO
ODU
ODU
RR
OCh
OM(T)
S
ODUk
OCh
Pro-
Res-
Ser-
Pro-
Pro-
Res-
Ser-
Pro-
tec-
tora-
vice
tec-
tec-
tora-
vice
tec-
tion
tion
Res-
tion
tion
tion
Res-
tion
tora-
Swit-
tora-
Swit-
tion
ching
tion
ching
Re-
Re-
Re-
Re-
ver-
ver-
ver-
ver-
sion
sion
sion
sion
Dy-
Dy-
Non-
per
namic
rever-
ser-
rerou-
sion
vice
ting
Manual reversion
Automatic
reversion
RR
RR
Dy-
namic
namic
rer-
rerou-
out-
ting
ing+Link dynamic
rerouting
Iron
service
Attributes of the SWITCH combination mode-OCH port service establishment are shown
in Table 4-9.
4-29
SJ-20110728142617-001|2011-09-27(R1.0)
Table 4-9 SWITCH Combination Mode-OCH Port Service Establishment Grade

Grade
OCh
OM(T)S
OCh Service
Protection
Restora-
Service
Protection
tion
Restora-
Switching
tion Rever-
Reversion
sion
Silver
RR
Dynamic
Non-
rerouting
reversion
service
Copper
service
Manual
reversion
Automatic
reversion
Iron service
TP
Link 1+1
protection
l
l
l
l
l
Caution!
TP: Traditional protections that includes the 1+1 (SNCP), M:N(1:1 and 1:N), ring
protection and PCYCLE.
PP: Permanent protection
RR: Rerouting
LO ODU: Lower-order ODU
HO ODU: Higer-order ODU
4.8.2 Configuring the Diamond Service

Prerequisites
l
l
You have the operation right for this function.

WDM NEs with WASON exist in the system.
Context
l
l
l
The network has the working path and protection path in the system initialization.
The working path failure will trigger the protection switching (within 50 ms), and then
rerouting is performed to establish a new protection path.
The protection path failure will trigger the 1+1 protection switching, and then rerouting
is performed to establish a new protection path.
4-30
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
Note:
The SPC service cannot be established on the service board where the PC service is
locked.
The request for creating a call cannot be originated between different boards or
different service ports. Thus, there are limitations on the board type and port type
(including service rate) of the boards installed on the first and the last port. The
boards on the first port and last port must be of the same type. The client-side type
and access rate must be identical.
The grades of all tributary services belonging to the same aggregate board must be
identical. Before creating a call in EMS, query whether the aggregate board has
created a call. If yes, set the service grade of the call being created to be the existed
service grade. However, the user can modify the service grade.
Steps
1. Create the non-revertive diamond service between Node_A and Node_C in the
topology diagram, as shown in Figure 4-15. The working path passes by Node_B
and the protection path passes by Node_D.
Figure 4-15 NE Topology
1. To create other call

service, refer to this
topology diagram.
2. Right-click Node_A, and then select WASON Management > Call Management. The
Call Management window opens, as shown in Figure 4-16.
4-31
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-16 Call Management Window
3. Click New in the Call Management window. The Create Call dialog box opens. Select
end A and end Z as shown in Figure 4-17 and Figure 4-18.
Figure 4-17 Selecting End A Dialog Box
4-32
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-18 Selecting End Z Dialog Box
Receive port: includes the client-side receive port and line-side send port. The
optional ports include: OAC input ports of a service board on the WASON node, OCH
output ports of the service boards, TIN port of OP boards, T1_IN and T2_IN ports of
DOP boards, AIN and BIN port of SOPCS boards.
Send port: includes the client-side send port, line-side receive port. The optional
ports include: OAC output ports of a service board, OCH input ports of service boards,
ROUT port of OP boards, R1_OUT and R2_OUT ports of SOP and DOP boards, AOUT
and BOUT ports of SOPCS boards. This parameter is valid only when Connection
Direction is set to "Bidirection".
4. Configure the other basic properties of the call, as shown in Figure 4-19.
4-33
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-19 Dialog Box of Configuring the Common Properties of a New Call
Table 4-10 lists the basic properties of the call.

Table 4-10 Basic Properties of the Call
Item
User Label
Service Grade
Description
Indicates the friendly name of the service. It is a string of 32-byte
characters.
This parameter restricts the value range of Protection Type,
Restoration Type, and Service Restoration Reversion Type.
Indicates the mode to create links after the service creation is
successful. This parameter can be set to one of the following three
options. The default value is Not As Link.
Create Link Mode
Not As Link: No link is automatically generated after a pure

optical layer service or an optical layer service is created. If links
need to be used, you can manually configure links later.
TE Link: Links are automatically generated by the control plane,

and flooded through OSPF.
Service Status
Indicates the service status.

The options include "Unidirection" and "Bidirection". The default value
Connection Direction
is "Bidirection". Currently, this parameter can be set to "Bidirection"

only and cannot be modified.
4-34
SJ-20110728142617-001|2011-09-27(R1.0)
Item
Description
The value of this parameter can be "None", standard concatenation,
Concatenation Type
or any continuous concatenation. The default value is "None".

Currently, this parameter can be set to "None" only and cannot be
modified.
The value of this parameter can be 0, 4, 16, 64, or 256. The
Concatenation Count
default value is 0. When Concatenation Type is set to "None",

this parameter must be set to 0. Otherwise, this parameter can be
set to 4, 16, 64, or 256.
Min Time Interval

between Connection
Indicates the maximum time interval between connection creation
Creation Retries (100
retries. It is an integer between 0 and 655350.
ms)
The Minimum Try
Interval of Creating
Connection (100 ms)
Indicates the minimum time interval between connection creation

retries. It is an integer between 0 and 655350.
Creation Count
Connection of Initial
An integer between 0 and 10.
Route
Creation Count
Connection of Rerouting

Indicates the creation priority of working connections/protection
Create Priority
connections/optimization rerouting connections. Options: high,

middle and low.
Restore Priority
Indicates the connection restoration priority. The value range is 1-8.

Options: high, middle and low.
5. After setting the basic properties, respectively click Protection Setting, Restoration
Setting, and Route Strategy to set protection, restoration/reversion, routing policy,
and route constraint parameters, as shown in Figure 4-20, Figure 4-21 and Figure
4-22.
4-35
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-20 Protection Setting Window
Table 4-11 describes the Protection Setting window.

Table 4-11 Description of the Protection Setting Window
Item
Description
Protection Type
These options are related to Service Grade.
Protection Switching WTR
This is a parameter used for transport plane protection. It is not
Time (s)
related to WASON and thus need not be set.
Protection Switching Delay

Time (100 ms)
Protection Switching
Reversion Type
The options are related to Service Grade.
Figure 4-21 Restoration Setting Window
4-36
SJ-20110728142617-001|2011-09-27(R1.0)
Table 4-12 describes the Restoration Setting window.

Table 4-12 Description of the Restoration Setting Window
Item
Description
Global Dynamic Re-routing: Local layer has the restoration
Global Dynamic Re-routing,
attribute.
Link Dynamic Re-routing,
Link Dynamic Re-routing: Service-layer services have the
Automatic Preset Re-routing
restoration attribute.
Automatic Preset Re-routing: the default value.
Service Restoration
Reversion Type
The options are related to Restoration Type.

This parameter is not configurable when Restoration Type is set
Restoration Waiting Time
to "None". If you select the check box Determined by Control
(100ms)
Plane, you cannot set the time through the network management
system. Otherwise, you can type an integer between 0 and 100.
This parameter is configurable only when Restoration Type is
Reversion Waiting Time (s)
set to "Dynamic Rerouting" and Service Restoration Reversion

Type is set to "Automatic Reversion". It can be set to an integer
between 60 and 720.
Restoration Connection
Creation Count of Initial
Route
This parameter should be set to an integer between 0 and 10. It is

not configurable when Restoration Type is set to "None".
Restoration Connection
This parameter should be set to an integer between 0 and 10. It is
Creation Count of Rerouting
not configurable when Restoration Type is set to "None".
4-37
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-22 Route Strategy Setting Window
1. The window lists all

created and connected
calls in the topology
network by default.
Users can set from
which connections the
current service needs

to be isolated.
4-11 describes the Route Strategy window.

Table 4-13 Description of the Route Strategy Window
Item
Description
Min Cost Algorithm
The algorithms for calculating the minimus

cost: two algorithms are optional.
Isolated with Other Nodes in Service
Are excluded from other nodes.
Isolated with Other Links in Service
Are excluded from other links.
Isolated with Other SRLG in Service
Irrelative to SRLG connecting to other nodes.
Load Balancing
Services are allocated to all paths evenly.
Optimization Restore
Selects the optimal path during the restoration.
Optical Impairment Verify
Verifies one performance.
Isolated Services Selection
Selects the connection to be isolated or

excluded.
Isolated with Other Nodes between Services
Excluded from a specified node.
Isolated with Other Links in Service
Excluded from a specified link.
Isolated with Other SRLG in Service
Excluded from a specified SRLG.
4-38
SJ-20110728142617-001|2011-09-27(R1.0)
Item
Description
Re-route Policy
6. Click Route Constraint View/Adjust in the Create Call window. The Route
Constraint View/Adjust dialog box opens. Configure the route constraints as shown
in Figure 4-23.
Figure 4-23 Configuring Route Constraints Dialog Box
1. Set the Constraint

Degree to Loose.
End of Steps
4.8.3 Configuring the Gold Service

Prerequisites
l
l

WASON WDM NEs exist in the system.
Context
l
l
l
If the working path fails, the services are switched to the protection path.
The protection path failure will trigger the reroute and establish a new protection path.
Steps
1. Create the auto-revertive OCH 1+1 gold service between Node_A and Node_C. The
working path passes by Node_B and the protection service passes by Node_D.
4-39
SJ-20110728142617-001|2011-09-27(R1.0)
Call Management window opens.
3. Set Node A and Node Z in the same way as the diamond service.
4. Configure the basic properties of the call, as shown in Figure 4-24.
Figure 4-24 Dialog Box of Configuring the Basic Properties of a Call
5. Figure 4-25 shows the protection setting tab, Figure 4-26 shows the restoration
property setting tab, and Figure 4-27 shows the route policy setting tab.
4-40
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-25 Setting Protection Window
Figure 4-26 Setting Restoration Window
4-41
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-27 Setting Route Strategy Window
in Figure 4-28.
End of Steps
4-42
SJ-20110728142617-001|2011-09-27(R1.0)
4.8.4 Configuring the Silver Service

Prerequisites
l
l

Context
l
l
l
The protection path failure will cause the service interruption.
Steps
1. Create the silver service between Node_A and Node_C. The working path passes by
Node_B and the protection service passes by Node_D.
2. Righ-click an Node_A, and then select WASON Management > Call Management.
The Call Management window opens.
3. Set Node A and Node Z in the same way as in the diamond service.
5. Figure 4-30 shows the protection setting tab. Figure 4-31 shows the restoration
property setting tab and Figure 4-32 shows the route policy setting tab.
4-43
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-30 Setting the Protection Window
Figure 4-31 Setting the Restoration Window
4-44
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-32 Setting the Route Strategy Window
in Figure 4-33.
Figure 4-33 Dialog Box of Configuring the Route Constraints
End of Steps
4-45
SJ-20110728142617-001|2011-09-27(R1.0)
4.8.5 Configuring the Copper Service

Prerequisites
l
l

WASON WDM NEs exist in the system.
Context
l
l
l
The protection path failure will trigger the reroute and establish a new protection path.
Steps
1. Create the copper service between Node_A and Node_C. The working path passes
by Node_B and the protection service passes by Node_D.
Call Management window opens.
3. Set Node A and Node Z in the same way as the diamond service.
5. Figure 4-35 shows the protection setting tab, Figure 4-36 shows the restoration
property setting tab and Figure 4-37 shows the route policy setting tab.
4-46
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-35 Setting Protection Window
Figure 4-36 Setting Restoration Window
Figure 4-37 Setting Route Strategy Window
4-47
SJ-20110728142617-001|2011-09-27(R1.0)
in Figure 4-38.
End of Steps
4.8.6 Configuring the Iron Service

To configure the iron service, refer to the configuration for other services. The configuration
details are not described again in this section.
4.8.7 Querying, Modifying and Deleting a Call Service

Prerequisites
l
l
l

You have opened the Call Management window.
Querying Call Service

1. In the Call Management window, select the newly created call. The detailed
information about the call is displayed, including basic properties, protection,
restoration/reversion, route strategy, isolated connections, route constraints, and
created connections. The information is consistent with the data configured during
the call creation.
2. Figure 4-39 and Figure 4-40 show the basic properties of the service after the service
is successfully created.
4-48
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-39 Call Query Results Dialog Box 1
Figure 4-40 Call Query Results Dialog Box 2
Modifying Call Service

1. Select the call to be modified in the Call Management window, as shown in Figure
4-41. Right-click the call and then select Modify Call, or click Modify in the bottom
right corner of the window. The Modify Call dialog box opens. Modify the call as
needed.
4-49
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-41 Call Management Dialog Box (Call Modification)
2. As shown in Figure 4-42 through Figure 4-46, click tabs Call Setting, Protection
Setting, Restoration Setting, Route Strategy and Isolated Service Selection
respectively to modify the corresponding parameters. You can also modify parameters
in windows Isolated Services Selection and Route Constraint. After modifying
relevant parameters, click Apply in the bottom right corner in the Modify Call dialog
box.
4-50
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-42 Call Modification Dialog Box (Common Properties)
4-51
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-43 Call Modification Dialog Box (Protection Setting)
4-52
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-44 Call Modification Dialog Box (Restoration Setting)
4-53
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-45 Call Modification Dialog Box (Route Strategy)
4-54
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-46 Call Modification Dialog Box (Route Constraint Selection)
3. Right-click an NE in the Modify Call window. An window opens, as shown in Figure

4-47. You can set the NE properties, such as Work, Protection, etc.
Figure 4-47 Modifying NE Properties Menu
Deleting Call Service

Select the call to be deleted in the Call Management window, or click Delete in the bottom
right corner of the window, to confirm the deletion.
4.8.8 Manually Reverting to Services

Short Description
You may manually revert to the SPC services which support the restoration function.
After the services are restored, if the Revert mode of service restoration is set to
Manual Reversion, the original working connections will be reserved. If the original
4-55
SJ-20110728142617-001|2011-09-27(R1.0)
working connection failure disappears, you may revert the service to the original working
connection status through setting the Manual Revert.
Prerequisites
l
l
There are SPC services and the SPC services can be restored.
Set the Revert mode of service restoration to Non-reversion.
Context
You can only manually revert to services which support the restoration and the Revert
Mode of restoration mode is set to Manual Reversion.
Steps
1. Right-click and NE and select WASON Management > Call Management. The Call
Management dialog box appears, as shown in Figure 4-48.
Figure 4-48 Call Management Dialog Box
2. Right-click a service and select Manual Revert.

End of Steps
4-56
SJ-20110728142617-001|2011-09-27(R1.0)
4.8.9 Setting the Service Optimization

Short Description
Before optimizing service connections, you may calculate the corresponding paths based
on the route constraints in order to make sure that the calculated paths meet requirements
and do not pre-occupy resources. When the calculated paths meet the requirements, you
may optimize services by using the constraint.
Prerequisites
Services have been created.
Context
None.
Steps
1. In the topology window, select Service > Service View. The Service View window
appears, as shown in Figure 4-49.
Figure 4-49 Service View Window
2. Select Filter All in the bottom-left corner in the window, all the service connections are
displayed. Select a service path line between two NEs. All services between the two
NEs will be displayed in the lower part of the window.
3. Right-click a service, select Operation > ASON > SPC Optimize Rerouting, The
Connection Selector dialog box appears, as shown in Figure 4-50 and Figure 4-51.
4-57
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-50 SPC Optimize Rerouting Menu
Figure 4-51 Connection Selector Dialog Box
4. Select a connection to optimize, and click Add to add it to the list. Click OK. The
optimization window appears.
5. Select a path to optimize and right-click it. Select Detail Route Constraint. The
Optional Detail Route Constraint dialog box appears, as shown in Figure 4-52.
4-58
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-52 Optional Detail Route Constraint Dialog Box
6. View the detailed constraint conditions. After you ensure that all information is correct,
click OK to optimize the services.
End of Steps
4.8.10 Presetting the Service Rerouting

Short Description
When services support the restoration, you may preset conditions and calculate the
required rerouting paths in order to reduce the time required for restoring connections
during the rerouting or you may restore the customized connections.
Prerequisites
None.
Context
None.
Steps
1. In the Service View window, select a path connection line between two NEs. All
services between the two NEs will be displayed in the lower part of the window.
Right-click a service to preset, select Operation > ASON > SPC Preset Rerouting .
The Connection Selector dialog box appears, as shown in Figure 4-53.
4-59
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-53 SPC Preset Rerouting Menu
2. Similar to setting the service optimization function, select a path to preset. Right-click
the path to preset, and select Optional Detail Route Constraint. In the Optional
Detail Route Constraint dialog box, select the path to preset and click OK.
End of Steps
4.9 Synchronizing SPC Services

Use this procedure to synchronize SPC services, so that the SPC service information in
the network management system is consistent with the actual SPC service information on
the control plane.

Prerequisites
l
l

WASON devices exist in the system.
Steps
Management > SPC Synchronization. The SPC Synchronization dialog box opens,
4-60
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-54 SPC Synchronization Window
2. Select Time Period, set Start Time and End Time, and then click Synchronize in
the bottom right corner in the dialog box to synchronize the SPC services excluding
abnormal SPC services on the source node in the specified time period.
3. Select Services, specify the services to be synchronized and then click Synchronize
in the bottom right corner the dialog box to synchronize the specified SPC services
excluding abnormal SPC services.
4. Select Synchronize All and then click Synchronize in the bottom right corner of the
dialog box to synchronize all the SPC services including abnormal SPC services on
the source node.
End of Steps
4.10 SPC Service Maintenance

Use this procedure to maintain SPC services, including:
l
Modifying the status of SPC services. You can modify the service status of SPC
services created on the control plane (whether a service is operating or not). If a
service is not operating, the fault of the service path will not be monitored.
Modifying the restoration of SPC service startup activation. You may modify the
restoration of the SPC service startup activation that is created on the control plane
and support the restoration. If the service does not allow the startup activation
4-61
SJ-20110728142617-001|2011-09-27(R1.0)
restoration (for example, there is fault on the path), the service will not activate the
restoration.
Modifying the protection parameters of SCP services. You can modify the attributes
of 1+1 protection services created on the control plane, such as protection switching
WTR time, protection switching delay, and protection switching restoration type.
Converting SPC to PC, or PC to SPC. This function serves to manage all services
in a network environment which has been loaded with ASON.

Maintaining SPC Services
Prerequisite
l
l
l

Normal SPC services exist in the system.
SPC services with channel 1+1 protection exist if service protection parameters are
to be modified.
Steps
1. In the Topology Management window, right-click a WASON NE, and then select
WASON Management > SPC Maintenance. The SPC Maintenance dialog box
opens. The Service Status tab is shown in Figure 4-55.
Figure 4-55 SPC Maintenance Window
2. Respectively click Restoration Activation, Protection Parameters and Switch

Routing to maintain the current service, as shown in Figure 4-56 through Figure 4-58.
4-62
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-56 Restoration Activation Window
1. Automatically restore
the automatic lock
after the service has
been restored for 6

times.
Figure 4-57 Protection Parameters Window
4-63
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-58 Switch Routing Window
Partitioning Link Resources

l
l
l
Link resource partition is to separate resources between the management platform

and control platform, which is mainly to handle the conflicts of wavelengths and
timeslots between PC services and SPC services.
After the equipment is enabled, WASON will divide the resources after reporting the
division interfaces.
WASON Management > Link Resource Assignment.
4.11 Enabling the Autodiscovery (non-WASON)

Use this procedure to set the automatic discovery function of the electrical layer. This
configuration is applied by the management plane to set the electric-layer boards of the
transport plane. The transport plane can cooperate with the WASON system to implement
the automatic discovery function of the electrical layer only when the automatic discovery
function is enabled.

Prerequisites
4-64
SJ-20110728142617-001|2011-09-27(R1.0)
Steps
Management > Autodiscovery Enable. The Auto Discovery Enable dialog box
opens, as shown in Figure 4-59.
Figure 4-59 Auto Discovery Enable Window
2. Select a card, select Enable Status and then click Apply.

End of Steps
4.12 Bundled Links

Bundling links enables all or multiple parallel links with the same characteristics between
two neighboring WASON nodes to be merged into one logical link. The group of links
can be issued as a single link during link maintenance and advertisement, so as to avoid
resource waste.
The merged logical link is called a bundled link, whereas the physical links composing the
bundled link are called member links.

Prerequisites
4-65
SJ-20110728142617-001|2011-09-27(R1.0)
Context
All member links of a bundled link must start from and terminate at the same pair of nodes,
and must have the same link characteristics. The following requirements must be met
during link bundling:
l
l
l
A bundled link can comprise one or multiple member links, but a member link can
belong to a bundled link only. Currently, recursive link bundling (that is, a bundled link
is a member link of another bundled link) is not considered.
The member links must exist. For a member link, the remote link information exists
and the remote link must be in an enabled or disabled status. Therefore, the status of
the transmit interface of a member link cannot be changed to "Initial" and the transmit
interface cannot be deleted.
Currently, only ODUk links can be bundled. OCH links cannot be bundled.
ODUk links can be bundled only when the interfaces at the two ends use the same
electrical cross-connect board, signal type, TS bandwidth, protection properties, link
cost, and SRLG.
Deleting a bundled link: The members of a bundled link become non-member links after
the bundled link is deleted.
Modifying a bundled link: You can add or delete member links to or from a bundled link.
You cannot delete all the member links and need to keep at least one member link for a
bundled link.
Steps
Management > Bundled Link. The Bundled Link dialog box opens, as shown in
Figure 4-60.
Figure 4-60 Bundled Link Window
2. Table 4-14 describes the Bundled Link dialog box.

4-66
SJ-20110728142617-001|2011-09-27(R1.0)
Table 4-14 Description of the Bundled Link Dialog Box

Item
Local Node
Local Interface ID
Remote Node
Remote Interface ID
Description
Indicates the local node ID of the bundled link. It is the same as the
local node ID of the member links.
Indicates the local interface ID of the bundled link. It is allocated by
the network management system.
Indicates the remote node ID of the bundled link. It is the same as the
remote node ID of the member links.
Indicates the remote interface ID of the bundled link. It is allocated by
the network management system.
Component Link
Indicates the number of member links of the bundled link. It is an
Number
integer equal to or greater than 1.
End of Steps
4.13 Configuring Optical Impairment Parameters

Optical impairment parameters are used to describe the characteristics of an optical
device, including the attenuation, dispersion, and non-linear effect. The linear effects
such as attenuation and dispersion can be compensated, but the non-linear effect is an
issue more difficult to solve. Because there is no proper solution to the non-linear effect,
the setting of non-linear effect parameters is not considered for the time being.
Currently, the optical impairment parameters to be verified include the Optical
Signal-to-Noise Ratio (OSNR), dispersion, and Polarization Mode Dispersion (PMD).

Prerequisites
Context
Parameters related to optical impairment parameters:
l
l
l
OSNR: Amplifier output power, amplifier gain, and amplifier noise figure
Dispersion: Dispersion coefficient, fiber length, and dispersion compensation distance
PMD: Device quantity and device PMD value
Device-related optical impairment parameters:

l
Line-side fiber: Dispersion coefficient, length, and PMD value

4-67
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
l
OA: Gain, output power, and noise figure

WSU, OMU, and ODU: PMD value
DCM: Compensation distance
Steps
1. In the Topology Management view, click a WASON NE and then select WASON
Management > Optical Impairment Parameters Config. The Optical Impairment
Parameters Config dialog box opens, as shown in Figure 4-61.
Figure 4-61 Dialog Box of Configuring Optical Impairment Parameters
You can set three types of parameters: Optical impairment parameters of line cards,
optical impairment parameters of amplifiers, and optical impairment parameters of
links.
2. In the Optical Impairment Parameters Config dialog box, click the Line Card Optical
Impairment Parameters tab, and then click Add at the bottom right of the dialog box
to set the optical impairment parameters of line cards, as shown in Figure 4-62.
4-68
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-62 Line Card Optical Impairment Parameters Dialog Box
Table 4-15 describes the Line Card Optical Impairment Parameters dialog box.
Table 4-15 Description of the Line Card Optical Impairment Parameters
Item
Description
Card Port
Card port ID
FEC Type
Non-FEC Mode by default
Modulation Type
NRZ by default
3. In the Optical Impairment Parameters Config dialog box, click the Amplifier Optical
to set the optical impairment parameters of amplifiers, as shown in Figure 4-63.
4-69
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-63 Dialog Box of Amplifier Optical Impairment Parameters
Table 4-16 describes the Amplifier Optical Impairment Parameters dialog box.
Table 4-16 Description of the Amplifier Optical Impairment Parameters
Item
Description
Card
Indicates the amplifier card related to optical impairment.
Gain
Indicates the gain of the card in the unit of dB.
Transmit Power
Noise Figure
Indicates the transmit power in the unit of dBm. The value range is
[-100,100]. The default value is 0.
Indicates the noise figure in the unit of dB. The value range is [0,6]. The
default value is 0.
4. In the Optical Impairment Parameters Config dialog box, click the Link Optical
to set the optical impairment parameters of links, as shown in Figure 4-64.
4-70
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-64 Dialog Box of Link Optical Impairment Parameters
Table 4-17 describes the Link Optical Impairment Parameters page.

Table 4-17 Description of the Link Optical Impairment Parameters
Item
Transmit Interface ID
Description
Indicates the transmit interface ID. This parameter should be set to the
name of a local transmit interface with switching capability "TDM".
Indicates the PMD coefficient. This parameter should be set in the
PMD Coefficient
unit of ps/km1/2 if there is no measured PMD value. The value range

is [0,100]. The default value is 0.
PMD Measured Value
Indicates the measured value of PMD in the unit of ps. The value range
is [0,0xFFFFFFFF]. The default value is 0.
Dispersion (10G 1530
Indicates the dispersion of the specified wavelength in the unit of
nm)
ps/nm. The value range is [0,100]. The default value is 0.
Optical Type
Indicates the compensation fiber type.
Optical Fiber Length
Indicates the optical fiber length in the unit of km.
Gain
Indicates the gain of the card in the unit of dB.
Transmit Power
Noise Figure
Indicates the transmit power in the unit of dBm. This parameter should
be set according to the actual device.
Indicates the noise figure in the unit of dB.
4-71
SJ-20110728142617-001|2011-09-27(R1.0)
Item
Compensation Mode
Description
Indicates the compensation mode. The default value is
"Precompensation".
Compensation Optical
Indicates the compensation fiber type. This parameter can be set to
Fiber Type
"G.652" or "G.655 (LEAF)".
Compensation
Indicates the compensation distance in the unit of km.
Distance
End of Steps
4.14 Connection Crankback Policy

If crankback parameters are not set for SPC connections or it is inconvenient to set
parameters for SPC connections, you can set relevant policy parameters for network
nodes. If crankback parameters have been configured for connections or service layer
connections, a crankback operation will be performed according to the configured
crankback policy and method when certain connections are blocked. The same policy is
selected and configured for all nodes in a network, so as to avoid rerouting chaos caused
by inconsistent operations during system running.
While sending an SPC service request to the control plane, the management plane
specifies the crankback parameters for the specific service connection. If blocking occurs
during service connection setup or restoration, a crankback operation is performed first
according to the settings.

Prerequisites
l
l

WASON devices exist in the system.
Context
After the crankback policy or parameters are set successfully, if intermediate node resource
conflicts occur or resources are unavailable during connection setup or connection trail
optimization, the system will crank back and set up new connections according to the
settings.
4-72
SJ-20110728142617-001|2011-09-27(R1.0)
Steps
Management > Connection Crankback Policy. The Connection Crankback Policy
dialog box opens, as shown in Figure 4-65.
Figure 4-65 Dialog Box of Connection Crankback Policy
2. Set the connection crankback policy parameters as described in Table 4-18.

Table 4-18 Description of Connection Crankback Policy Parameters
Item
Description
NE
Indicates the WASON node related to crankback computation.

Indicates the crankback node type. The options include "Not
Crankback Node Type
Crankback", "End-to-end Re-routing", "Boundary Re-routing", and

"Segment-based Re-routing".
Indicates the maximum number of connection retries initiated
The Try Times of
through route recomputation in the event of connection crankback.
Creating Rerouting Initial
Initial connections refer to the other service connections (such as
Connections
working connection and protection connection) except restoration

connections. The value range is 0-10. The default value is 3.
The Try Times of Creating
Indicates the maximum number of connection retries initiated
Rerouting Restore
through route recomputation in the event of restoration connection
Connections
crankback. The value range is 0-10. The default value is 3.
The Maximum Try Interval

of Creating Connections
Indicates the maximum interval between connection setup

attempts. The value range is 0-65535, the step length is 100 ms,
and the default value is 100.
4-73
SJ-20110728142617-001|2011-09-27(R1.0)
Item
The Minimum Try Interval
of Creating Connections
Description
Indicates the minimum interval between connection setup attempts.
The value range is 0-65535, the step length is 100 ms, and the
default value is 100.
End of Steps
4.15 Comparing Topology Links

The management plane can query the fiber link configurations of the control plane,
compare the configuration information with its own fiber link configuration information,
and thus generate comparison results. If the comparison results indicate inconsistency,
the management plane can re-synchronize its own fiber link information to the WASON
control plane. The fiber link information from the management plane will overwrite the
fiber link information on the control plane.

Prerequisites
l
l

You have created WASON devices.
Steps
Management > Topo Link Compare. The Topo Link Compare dialog box opens,
4-74
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-66 Fiber Link Data Comparison Window
2. Table 4-19 describes the Topo Link Compare dialog box.

Table 4-19 Description of Parameters in the Topo Link Compare Window
Item
Description
Topo Link Property
This parameter indicates the fiber link property to be compared. The

options include "Topo Link ID", "Source Port", and "Sink Port".
The value of this parameter is the fiber link data obtained from the
NM
NM database. If there is no data, the value is displayed as a null

character string.
The value of this parameter is the fiber link data obtained from the
WASON
control plane. If there is no data, the value is displayed as a null

character string.
Note:
To re-configure the optical fiber connection, make sure that there are no SPC services
at the current node, otherwise the configuration will fail.
End of Steps
4-75
SJ-20110728142617-001|2011-09-27(R1.0)
4.16 PCE Configuration

1. PCE supports the Multiple-layer Traffic Engineering (M-TE) and can automatically
configure services, calculate the restoration path, and optimize the available
resources. PCE has the advantages on improving the calculation efficiency and
reducing the resource conflicts.
2. The control plane sends a request for optimization calculation by connection resource
to PCE (the operation objects are link table and signaling granularity). PCE outputs
an optimized connection table and expected data on links and global fragment rate.
You may select the connections to be optimized (more than one connection can be
selected. All connections are selected by default) and confirm it. The management
plane sends a request for optimization calculation by connection resource to PCE (the
operation objects are connection table).
3. PCE performs the optimization calculation on the connections allocated by users. After
that the management plane update the data of expected fragment rate and global
fragment rate and compare the data before and after the optimization.
PCE supports the following functions:
l
l
l
l
l
l
l
GMPLS link constraints

Two-direction path calculation
Isolation policy
Load-balance policy
Synchronization path calculation
Distinguishing priorities
Calculating path in batches
4.16.2 Configuring a PCE Shelf

Context
The EMS displays individual PCE shelf and users may operate the PCE shelf in the EMS.
Each NE only contains one PCE shelf at most, and the shelf only contains one slot. The
shelf identifier is always 127. Once the shelf with ID 127 (PCE shelf or other shelf) is
configured in the NE, no PCE shelf can be added. If the shelf 127 is not a PCE shelf, the
PCE shelf cannot be configured until the shelf 127 is deleted.
Note:
There are two kinds of PCE modules: the external PCE and built-in PCE. The built-in PCE
has been configured before delivery from the factory, and is not described here.
4-76
SJ-20110728142617-001|2011-09-27(R1.0)
Steps
1. In the Topology Management view, right-click a WASON NE and then select NE
Management > NE Property > Rack/Shelf Configto open the Rack/Shelf Config
window, as shown in Figure 4-67.
Figure 4-67 Rack/Shelf Configuration Window
2. Right-click Main Rack, and then select Add PCE Shelf from the shortcut menu to
configure the related parameters. The PCE shelf property configuration window is
Figure 4-68 PCE Shelf Configuration Dialog Box
Table 4-20 describes the PCE Shelf Configuration window.
4-77
SJ-20110728142617-001|2011-09-27(R1.0)
Table 4-20 Description of the PCE Shelf Configuration

Item
Shelf ID
Shelf Label
Position ID
Shelf Type
Description
The unique ID of the shelf, which is exclusive and cannot be
modified
The NE name defined by users, which can be modified and
cannot be unique. The default shelf label is PCE.
Describes the current position of shelf. The position ID changes
with the shelf moving up and down
The shelf type 127 or adding PCE shelf menu. The PCE shelf is
set by default.
The slave rack must have a master shelf to bind to. Only the
Binding Main Rack
slave shelf has the property. The PCE shelf must be bound to
the R0 main shelf (Note: displays the label of R0 main shelf).
Description
Users may type shelf description information.
3. After setting the PCE properties, click OK. Right-click the NE and select Card
Management to view the PCE shelf view, as shown in Figure 4-69.
Figure 4-69 PCE Shelf Dialog Box
End of Steps
Example
l
Creating a PCE Device
In the Topology Management view, right-click an NE configured with PCE shelf,

and then select PCE Management > Create PCE device, Figure 4-70 dialog box
opens.
4-78
SJ-20110728142617-001|2011-09-27(R1.0)
Figure 4-70 Dialog Box of Creating a PCE Device
The PCE shelf is shown in Figure 4-71.

Figure 4-71 PCE Shelf Dialog Box
Note:
Only when the PCE device is configured successfully, the PCE management will
display other menus related to PCE for further management.
When PCE device is created successfully, the system will originate request for
establishing connections to PCE device.
Deleting a PCE Device

In the Topology Management view, right-click an NE configured with PCE shelf, and
then select PCE management > Delete PCE device, a dialog box opens, as shown
in Figure 4-72. Click OK.
Figure 4-72 Dialog Box of Deleting a PCE Device
4-79
SJ-20110728142617-001|2011-09-27(R1.0)
Note:
After deleting the PCE device successfully, the PCE management will only display
Create PCE Device, other menus will not be displayed.
4.16.3 Configuring a PCE Node

Prerequisites
After a PCE device is created successfully, it needs to be configured with a PCE node ID
so that the device can be managed properly by the NMS.
Steps
1. In the Topology Management window, right-click an NE configured with PCE shelf
and then select PCE Management > Node ID Config. A dialog box opens, as shown
in Figure 4-73.
Figure 4-73 Node ID Configuration Dialog Box
4-80
SJ-20110728142617-001|2011-09-27(R1.0)
Note:
Node ID: a unique ID of a PCE device. It is a 4byte integer. It is identified as an IPv4
address in the protocol, and it can be modified. The NMS verifies its uniqueness in
the entire network.
End of Steps
4.16.4 Configuring a PCE Control Interface

Context
The NMS issues the configuration of the new physical out-band control interface to the
PCE. The PCE searches for correlation between the physical interface index and the
address according to the out-band control interface address, and then configures the
out-band control interface into the system protocol module.
Steps
1. In the Topology Management view, click an NE configured with PCE shelf, and then
select PCE Management > Control Interface Management. A dialog box opens, as
Figure 4-74 Control Interface Management Dialog Box
The control interface management properties are described in .
4-81
SJ-20110728142617-001|2011-09-27(R1.0)
Item
Description
Ethernet port used to build a out-band control channel. When
configuration is issued to PCE, it needs to be converted to
Port
the interface ID.

One OSC contains four-direction ports, up to now, 16 ports
can be configured at most.
Local IP address of control interface. It must be different
IP address
from the node ID. Up to now one Ethernet port only can be
configured with one IP address.
Mask
OSPF Protocol
The subnet mask of the control interface IP address:

255.255.0.0 by default
The OSPF switch of the control channel's interface. Options:
In use or forbidden. In use by default.
When PCE device is accessed to a domain in the network, it needs to know all
control plane neighbors in the domain, so the control plane neighborhood needs to be
configured. The PCE control interface neighborhood is used to configure the mapping
relation between the PCE control interface and ASON control interface. However,
the control interface neighborhood cannot be configured between two PCE control
interfaces. Control plane neighbor relation is maintained by the control interface. PCE
control neighbors need to configure Z end IP address (IP of ASON control interface).
a. In the Topology Management view, click an NE configured with PCE shelf, and
then select PCE Management > Control Interface Management > Control
Interface Neighbor, a dialog box opens, as shown in Figure 4-75.
Figure 4-75 Control Interface Neighbor Dialog Box
4-82
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
Note:
Z end node ID: refers to the neighbor node ID that serves to configure the
IPCC of LMP. IPv4 address is composed of all 0s by default.
Z end IP: refers to the neighbor interface address that serves to configure the
OSPF neighbor and Z end IPCC address of LMP.
End of Steps
4.16.5 Configuring the PCE Automatic Discovery

The PCE automatic discovery can enable the PCC to automatically detect the PCE
existence, capacity, and service ranges, so as to use the calculation capability of PCE.
In the Topology Management window, click an NE configured with PCE shelf, and then
select PCE Management > Auto Discovery Property Config. A dialog box opens, as
Figure 4-76 Auto Discovery Property Window
4-83
SJ-20110728142617-001|2011-09-27(R1.0)
4-84
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 5
ZXUCP A200 Alarms and

Events
Table of Contents
Alarms on the Control Plane.......................................................................................5-1
Events on the Control Plane .......................................................................................5-2
Alarm Handling...........................................................................................................5-3
Event Handling.........................................................................................................5-15
5.1 Alarms on the Control Plane

You may query the alarms related to WASON control plane as follows:
Right-click an NE, and then select Fault Management > Synchronize Active Alarm >
Custom Query. In the Custom Query window, set the ASON value in Alarm Code in the
New Active Alarm Query window and execute the filter and query.
Table 5-1 lists the alarms that can be detected by the WASON control plane.
Table 5-1 Alarms on the Control Plane
Alarm Name
Alarm No.
Connection failure
07D0H
Connection degradation
07D1H
Signals on a connection degrade.
Major
RSVP Hello failure
07D2H
RSVP Hello failure
Minor
LMP Hello failure
07D3H
LMP Hello failure
Minor
07D8H
Node parameters are not configured.
Major
Node parameters not configured

Service failure
Transmit interface discovery
failure
Transmit interface misconnection
Description
Severity
A connection fails because of some

severe fault.
All support connections of a service
07E1H
are faulty.
The automatic discovery of transmit
07E9H
interfaces fails.
Critical
Critical
Major
The automatic discovery result is in07EAH
consistent with the configured con-
Critical
nection relationship.
5-1
SJ-20110728142617-001|2011-09-27(R1.0)
Alarm Name
Alarm No.
Description
Severity
The inconsistent connection relaMiswire
tion of transport interfaces between
07EAH
neighbor nodes can be discovered
Critical
automatically.
Resource of transport mismatch
The fact that NMS deletes boards or

07EEH
divide link interface resources affect
Critical
the existent
After the neighbors have been dis-
Neighbor Discovery Failure
07D4H
covered successfully, some causes
Minor
lead to the neighbor discovery failure.

Residual timeslot alarm
The timeslot occupation at two ends
07EDH
of a link is inconsistent.
Major
5.2 Events on the Control Plane

When the control plane works normally, it reports some normal or abnormal running states
to the management plane in the form of events. Table 5-2 lists the events related to the
WASON function.
Table 5-2 List of Events
Detection Point
Service
(OTN SPC, SC, etc.)
Event No.
Description
0x4202
Service restoration starts
0x4203
Service restoration succeeds
0x4204
Service restoration fails
0x4205
Service reversion starts
0x4206
Service reversion succeeds
0x4207
Service reversion fails
0x4213
Service optimization rerouting starts
0x4214
Service optimization rerouting fails
0x4215
Service optimization rerouting succeeds
0x420B
Connection
0x420C
Tries to set up a connection or reestablish a connection (the

application range of this event has been expanded)
Connection restart and restoration
Fails to set cross-connections on the transport plane: The
Transport plane
0x420F
transport plane may return multiple failure messages about

cross-connection configuration. Therefore, this event is not
associated with specific connections.
5-2
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 5 ZXUCP A200 Alarms and Events
Detection Point
Event No.
Description
0x2900
MCU Raset
5.3 Alarm Handling

5.3.1 Connection Failure
Description
A severe fault occurs on the Label Switched Path (LSP) maintained by the control plane
and results in connection failure.
Alarm Explanation
The transport resource used by the connection generates a Signal Failure (SF) alarm,
which results in connection failure of the control plane.
Alarm Properties
The properties of the connection failure alarm are described in Table 5-3.
Table 5-3 Properties of the Connection Failure Alarm
Alarm No.
Alarm Severity
07D0H
Critical
Alarm Parameters
The parameters of the connection failure alarm are described in Table 5-4.
Table 5-4 Parameters of the Connection Failure Alarm
Parameter
Source node ID/source TNA
address
Destination node ID/destination
TNA address
Description
Source node ID or source TNA address
Destination node ID or destination TNA address
Service ID
The service ID assigned between the source and destination
Connection ID
The connection ID in the service
Influence on System
A severe fault occurs on an existing LSP may lead to one of the following results according
to the actual network configuration.
5-3
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
If the services on the LSP are configured with 1+1 or channel shared ring protection,
they will be switched to an alternate path and therefore the service quality is
guaranteed.
If the services on the LSP support dynamic restoration, transient service interruption
will occur before successful connection restoration.
If the services on the LSP have neither dynamic restoration capability nor protection
configuration, they will be interrupted.
Possible Cause
The transport resources corresponding to the LSP of the connection report severe alarms,
such as LOS, OTUk LOF, or OTUk-AIS.
Solution
Check for alarms reported by transport resources, which may result in signal failure, on
the nodes by which the LSP passes.
5.3.2 Connection Degradation

Description
A fault occurs on the Label Switched Path (LSP) of a connection maintained by the control
plane because of signal degradation.
Alarm Explanation
The transport resource used by the connection generates a Signal Degrade (SD) alarm,
which results in the connection degradation.
Alarm Properties
The properties of the connection degradation alarm are described in Table 5-5.
Table 5-5 Properties of the Connection Degradation Alarm
Alarm No.
Alarm Severity
07D1H
Major
Alarm Parameters
The parameters of the connection degradation alarm are described in Table 5-6.
Table 5-6 Parameters of the Connection Degradation Alarm
Parameter
address
Description
5-4
SJ-20110728142617-001|2011-09-27(R1.0)
Parameter
TNA address
Description
Service ID
Connection ID
The connection ID in the service
Influence on System
The signal degradation on an existing LSP may lead to one of the following results
according to the actual network configuration. Currently the handling principles for the
connection degradation alarm are the same as those for the connection failure alarm.
l
l
l
If the services on the LSP are configured with 1+1 or channel shared ring protection,
they will be switched to an alternate path and therefore the service quality is
guaranteed.
If the services on the LSP support dynamic restoration, transient service interruption
will occur before successful connection restoration.
If the services on the LSP have neither dynamic restoration capability nor any
protection configuration, they will be interrupted.
Possible Cause
The transport resources corresponding to the LSP of the connection report SD alarms,
such as SM-DEG.
Solution
Check for alarms reported by transport resources, which may result in signal degradation,
on the nodes by which the LSP passes.
5.3.3 RSVP Hello Failure

Description
RSVP neighborhood is established or lost.
Alarm Explanation
RSVP exchanges Hello messages to check whether the neighbor relation is established
or lost. If the Hello message exchange fails between neighbors, an RSVP Hello failure
alarm is generated. If the exchange of Hello message recovers, the system will report that
the RSVP Hello failure alarm disappears.
Alarm Properties
The properties of the RSVP HELLO failure alarm are described in Table 5-7.
5-5
SJ-20110728142617-001|2011-09-27(R1.0)
Table 5-7 Properties of the RSVP Hello Failure Alarm

Alarm No.
Alarm Severity
07D2H
Minor
Alarm Parameters
The parameters of the RSVP HELLO failure alarm are described in Table 5-8.
Table 5-8 Parameters of the RSVP Hello Failure Alarm
Parameter
Description
Neighbor node ID
The node ID of the neighbor node
Influence on System
When an RSVP Hello failure alarm occurs, the signaling messages cannot reach related
neighbor nodes.
Possible Cause
The SOSC is blocked, or related neighbor nodes are restarted.
Solution
Check whether the related neighbor nodes are restarted. If not, check whether the SOSC
is normal.
5.3.4 LMP Hello Failure

Description
The LMP control channel is established or lost.
Alarm Explanation
The LMP maintains neighbor relation by exchanging Hello messages on the control
channel. If the Hello message exchange fails, an LMP Hello failure alarm is generated.
If the Hello message exchange on the control channel recovers, the system will report
that the LMP Hello failure alarm disappears.
Alarm Properties
The properties of the LMP HELLO failure alarm are described in Table 5-9.
Table 5-9 Properties of the LMP Hello Failure Alarm
Alarm No.
Alarm Severity
07D3H
Minor
5-6
SJ-20110728142617-001|2011-09-27(R1.0)
Alarm Parameters
The parameters of the LMP HELLO failure alarm are described in Table 5-10.
Table 5-10 Parameters of the LMP Hello Failure Alarm
Parameter
Description
Interface index
The ID of the control channel
Influence on System
The failure of all LMP control channels to a neighbor node causes the failure of both
residual connection detection and automatic TE link discovery.
Possible Cause
The SOSC is blocked, or related neighbor nodes are restarted.
Solution
Check whether the SOSC is normal and whether the related neighbor nodes are restarted.
5.3.5 Node Parameters Not Configured

Description
The relevant parameters of the WASON node are not configured.
Alarm Explanation
The relevant parameters of the WASON node are not configured, such as node ID, RSVP,
and LMP.
Alarm Properties
The properties of the node parameters not configured alarm are described in Table 5-11.
Table 5-11 Properties of the Node Parameters Not Configured Alarm
Alarm No.
Alarm Severity
07D8H
Major
Alarm Parameters
Not applicable
Influence on System
The WASON node can not be normally started if its parameters are not configured.
5-7
SJ-20110728142617-001|2011-09-27(R1.0)
Possible Cause
Specific parameters have not been configured.
Solution
Follow relevant steps to configure node parameters.
5.3.6 Service Failure

Description
All connections that carry services fail.
Alarm Explanation
When all connections that carry services fail, a service failure alarm is generated. If at
least one of the connections is restored, the system will report that the service failure alarm
disappears.
Alarm Properties
The properties of the service failure alarm are described in Table 5-12.
Table 5-12 Properties of the Service Failure Alarm
Alarm No.
Alarm Severity
07E1H
Critical
Alarm Parameters
The parameters of the service failure alarm are described in Table 5-13.
Table 5-13 Parameters of the Service Failure Alarm
Parameter
address
TNA address
Service ID
Description

Influence on System
If these connections are used to carry some services, the generation of the service failure
alarm means that the transport of these services over the network fails. When the alarm
disappears, it indicates that the network connection restores the transport capability.
5-8
SJ-20110728142617-001|2011-09-27(R1.0)
Possible Cause
Link fault on the transport plane, or node fault (such as broken fiber, board failure, or node
powered down.)
Solution
Check whether the status of resources on the transport plane is normal (such as broken
fibers, the board failure, or whether the node is powered down.)
5.3.7 Transmit Interface Discovery Failure

Description
This alarm indicates that the discovery process of a transmit interface cannot be completed
properly.
Alarm Explanation
A neighbor node fails to find ports when the operation of automatic transmit interface
discovery is performed. The alarm disappears if ports are discovered successfully.
Alarm Properties
The properties of the transmit interface discovery failure alarm are described in Table 5-14.
Table 5-14 Properties of the Transmit Interface Discovery Failure Alarm
Alarm No.
Alarm Severity
07E9H
Major
Alarm Parameters
The parameters of the transmit interface discovery failure alarm are described in Table
5-15.
Table 5-15 Parameters of the Transmit Interface Discovery Failure Alarm
Parameter
Transmit interface
ID
Description
Remark
4-byte transmit interface ID
This ID can be mapped to a specific

device port number.
Influence on System
When discovery failure occurs, transport resources between nodes can not be
automatically reflected on the control plane. In other words, these transport resources
are invisible and thus unavailable on the control plane.
Possible Cause
l
The optical port is not connected with an optical cable.

5-9
SJ-20110728142617-001|2011-09-27(R1.0)
The optical cable is broken.
Solution
1. Check related optical connections and make sure that all related optical interfaces are
connected properly.
2. Replace the broken optical cable.
5.3.8 Miswire
Description
This alarm indicates that lines at receiving and transmitting directions of the transiting
interface are not connected to one remote port.
Alarm Explanation
The connections relations between transmitting interfaces of a transmitting interface
adjacent neighbors can be discovered automatically. If the transmitted data are
inconsistent and the transmission port has generated the corresponding TE link, the
alarm will be generated. The alarm disappears if the transmitted data become consistent
with each other.
Alarm Properties
The properties of the miswire alarm are described in Table 5-16.
Table 5-16 Properties of the Miswire Alarm
Alarm No.
Alarm Severity
07EAH
Critical
Alarm Parameters
The parameters of the miswire alarm are described in Table 5-17.
Table 5-17 Parameters of the Miswire Alarm
Parameter
Local transmit
interface ID
Description
Interface ID of the miswire
Influence on System
If this alarm is not removed, the services using these resources may be affected.
Possible Cause
l
The fibers on transmission plane are connected incorrectly.

5-10
SJ-20110728142617-001|2011-09-27(R1.0)
Solution
1. Connect the fibers on transmission plane properly.
5.3.9 Neighbor Discovery Failure

Description
After the neighbors have been discovered successfully, some causes lead to the neighbor
discovery failure.
Alarm Explanation
When a node is added in the network, the nodes concerned on the control platform can
discover the new neighbor and notify the change to other nodes. When the fibers between
neighbors are broken, the neighbor discovery failure is notified.
Alarm Properties
The properties of the neighbor discovery failure alarm are described in Table 5-18.
Table 5-18 Properties of the neighbor discovery failure alarm
Alarm No.
Alarm Severity
07D4H
Critical
Alarm Parameters
None
Influence on System
When discovery failure occurs, the local TE link may have flooding.
Possible Cause
l
l
All fibers connecting two nodes are broken or the laser shuts down.
The remote end disable the neighbor discovery, while the local end does not.
Solution
1.
2.
3.
4.
Check related optical connections.

Check the laser configuration.
Disable the neighbor discovery at local end.
Delete the neighborhood manually.
5-11
SJ-20110728142617-001|2011-09-27(R1.0)
5.3.10 Transmit Interface Misconnection

Description
The automatic discovery result is inconsistent with the connection relation configured by
the management plane.
Alarm Explanation
The connection relation of transmit interfaces between neighbor nodes can be discovered
automatically. If the discovery result is inconsistent with the interface relation configured
by the management plane, this alarm is generated. After the discovery result is consistent
with the interface relation configured by the management plane, this alarm disappears.
Alarm Properties
The properties of the transmit interface misconnection alarm are described in Table 5-19.
Table 5-19 Properties of the Transmit Interface Misconnection Alarm
Alarm No
Alarm Severity
07EAH
Critical
Alarm Parameters
The parameters of the transmit interface misconnection alarm are described in Table 5-20.
Table 5-20 Parameters of the Transmit Interface Misconnection Alarm
Parameter
Transmit interface
ID
Description
Remark
4-byte transmit interface ID
This ID can be mapped to a specific

device port number.
Influence on System
If the alarm is not handled, the services that use this resource later may be affected.
Possible Cause
The connection relation configured by the management plane is inconsistent with the
discovery result.
Solution
Check the connection relation configured by the management plane and the automatic
discovery result.
5-12
SJ-20110728142617-001|2011-09-27(R1.0)
5.3.11 Residual Timeslot Alarm

Description
The use status of timeslots at two ends of the TE link is inconsistent.
Alarm Explanation
When the use status of a wavelength or sub-wavelength at two ends of the TE link is
inconsistent, the residual timeslot alarm is generated.
Alarm Properties
The properties of the residual timeslot alarm are described in Table 5-21.
Table 5-21 Properties of the Residual Timeslot Alarm
Alarm No.
Alarm Severity
07EDH
Major
Alarm Parameters
The parameters of the residual timeslot alarm are described in Table 5-22.
Table 5-22 Parameters of the Residual Timeslot Alarm
Parameter
Transmit interface ID
Description
Indicates the ID of the transmit interface, which can correspond
to a specific port.
Label type
Indicates SDH label or WDM label.
Label value
For WDM label, it indicates wavelength and sub-wavelength.
Segment type
InSegment or OutSegment
Concatenation count
The number of concatenations
Influence on System
This alarm is on TE link and does not affect services. If the resource status is inconsistent,
this TE link can not be used during the selection of resources.
Possible Cause
Service transfer is not complete.
Solution
1. Check whether the reserved channel resources at both ends of the link are consistent.
If not, reserve the channel resources at the idle end, or cancel the reservation of
channel resources at the reserved end.
5-13
SJ-20110728142617-001|2011-09-27(R1.0)
2. Check the occupation status of both ends of the link. If one end is idle while the
other is occupied, delete the cross-connection at the occupied end, or configure
cross-connection at the idle end.
5.3.12 Inconsistency of Resource Management Rights

Description
The resources at two ends of the TE link is inconsistent.
Alarm Explanation
The resources allocated at the link interface and the reported resources are inconsistent.
Alarm Properties
The properties of the inconsistent resource management rights alarm are described in
Table 5-23.
Table 5-23 Properties of the Inconsistent Resource Management Rights Alarm
Alarm No.
Alarm Severity
07EEH
Major
Alarm Parameters
The parameters of the alarm about inconsistency of resource management rights are
described in Table 5-24.
Table 5-24 Parameters of the Alarm About Inconsistency of Resource Management
Rights
Parameter
Transmit interface ID
Description
Indicates the ID of the transmit interface, which can correspond
to a specific port.
Label type
Indicates SDH label or WDM label.
Label value
For WDM label, it indicates wavelength or sub-wavelength.
Segment type
InSegment or OutSegment
Concatenation count
Concatenation count
Influence on System
This alarm is on TE link and does not affect services. If the resource status is inconsistent,
this TE link can not be used during the selection of resources.
Possible Cause
Service transfer is not complete.
5-14
SJ-20110728142617-001|2011-09-27(R1.0)
Solution
Check whether the use status at two ends of the link is consistent. If one end belongs to
the management plane while the other end belongs to the control plane, hand over the
end managed by the control plane to the management plane.
5.4 Event Handling

5.4.1 Connection Switching
Detection Point
APS
Event No.
0x4201
Solution
Check the cause of the connection switching.
5.4.2 Service Restoration Starts

Detection Point
CC
Event No.
0x4202
Solution
Check the cause of the service restoration.
5.4.3 Service Restoration Succeeds

Detection Point
CC
Event No.
0x4203
5-15
SJ-20110728142617-001|2011-09-27(R1.0)
Solution
Check the cause of the service restoration, as well as the service attributes after the service
restoration succeeds.
5.4.4 Service Restoration Fails

Detection Point
CC
Event No.
0x4204
Solution
Check the cause of the service restoration failure.
5.4.5 Service Reversion Starts

Detection Point
CC
Event No.
0x4205
Solution
Check the cause of the service reversion.
5.4.6 Service Reversion Succeeds

Detection Point
CC
Event No.
0x4206
Solution
Check the cause of the service reversion, as well as the service attributes after the service
reversion succeeds.
5-16
SJ-20110728142617-001|2011-09-27(R1.0)
5.4.7 Service Reversion Fails

Detection Point
CC
Event No.
0x4207
Solution
Check the cause of the service reversion failure.
5.4.8 Connection Resetup Attempt

Detection Point
CC
Event No.
0x420B
Solution
Check the cause of the connection setup failure, as well as the number of connection
resetup attempts.
5.4.9 Connection Restart and Restoration

Detection Point
CC
Event No.
0x420C
Solution
Check the connection properties after the connection restart and restoration.
5.4.10 Fails to Set Cross-Connect on the Transport Plane

Detection Point
TAP
5-17
SJ-20110728142617-001|2011-09-27(R1.0)
Event No.
0x420F
Solution
Check the cause of the failure to set cross-connect on the transport plane.
5.4.11 Service Optimization Rerouting Starts

Detection Point
CC
Event No.
0x4213
Solution
Check the cause of the service optimization rerouting.
5.4.12 Service Optimization Rerouting Succeeds

Detection Point
CC
Event No.
0x4215
Solution
Check the cause of the service optimization rerouting, as well as the service properties
after the service optimization rerouting succeeds.
5.4.13 Service Optimization Rerouting Fails

Detection Point
CC
Event No.
0x4214
Solution
Check the cause of the service optimization rerouting failure.
5-18
SJ-20110728142617-001|2011-09-27(R1.0)
5.4.14 MCU Reset

Detection Point
None
Event No.
0x2900
Solution
The system may be reset successfully. When this alarm occurs, you need to check whether
the system runs properly based on the reported alarms and system running indicators etc.
5-19
SJ-20110728142617-001|2011-09-27(R1.0)
5-20
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 6
Network Maintenance of
ZXUCP A200
Table of Contents
Network Routing Maintenance....................................................................................6-1
Troubleshooting..........................................................................................................6-5
6.1 Network Routing Maintenance

6.1.1 Maintenance Instructions
l
l
l
Do not exit the network management system when the system is running normally.
Otherwise, the network management system will stop monitoring the equipment,
although the services of the equipment will not be interrupted.
Assign different NMS login accounts with different operation rights to different users,
and periodically modify user passwords to guarantee security.
Do not deploy services with the network management system at the peak service time,
because a great impact will be caused if errors occur. Instead, deploy services when
the traffic amount is minimum.
Note:
It is recommended that you select a time between 2:00 AM and 6:00 AM (GMT) to
deploy services. Perform relevant settings according to actual conditions to minimize
operation risks.
l
l
Back up data in time after service deployment to facilitate fast service restoration once
faults occur.
Do not play games on NMS computers, or copy irrelevant files or software to the NMS
computers. Periodically use the antivirus software to scan the NMS computers for
viruses, so as to prevent virus infection.
6.1.2 List of Maintenance Items

The maintenance items are listed as follows:
6-1
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
l
l
Checking SPC services

Checking TE links
Checking the alarms and events on the control plane
Maintenance-related configuration
6.1.3 Maintenance Operations

6.1.3.1 Checking SPC Services
Purpose
The integrity and normal attribute changes of SPC services should be guaranteed during
routine maintenance. In the NetNumen U31 network management system, you can check
details about each SPC service.
Prerequisite
You have the operation rights for this function.
Maintenance Period
Every day
Tools and Materials

NetNumen U31
Steps
1. In the SPC Synchronization window, select all WASON nodes, select the
Synchronize All check box, and then click Synchronize.
2. Operation success information is returned after the synchronization is completed.
3. In the Call Management window, query all the current services.
4. Check the number of services and the running status of each service. For details about
the check items and criteria, refer to Table 6-1.
Table 6-1 Criteria for Checking the Status of SPC Services
Check Item
Remarks
The number of
Check whether the number of services is consistent with the plan.
services
Service trail
Check whether the service trail properties have changed. Ensure that the
actual routes and original routes are consistent with the plan.
Service attributes
Check the service attributes, including the service activation status, protection
level, used wavelength, and restoration/reversion settings. In addition, check
whether the rerouting settings are consistent with the plan.
6-2
SJ-20110728142617-001|2011-09-27(R1.0)
Chapter 6 Network Maintenance of ZXUCP A200
Check Item
Remarks
Service status
Check whether the service status is normal. Locate and remove the fault if
the service status is abnormal.
6.1.3.2 Checking TE Links

Purpose
Always focus on the usage of TE links during routine maintenance. In the NetNumen U31
network management system, you can check TE links.
Prerequisite
Maintenance Period
Every day
Tools and Materials

NetNumen U31
Steps
1. In the TE Link Config window, click Whole Network Query to query the TE links of
the whole network.
2. Check the usage of each TE link. For details about the check items and criteria, refer
to Table 6-2.
Table 6-2 Criteria for TE Link Check
Check Item
Remarks
The number of TE links
First check whether the total number of TE links of the whole network
is correct. The number of TE links should be consistent with the actual
number of TE links.
TE link parameters
There must be bidirectional TE links between two WASON NEs connected by fibers, and no alarms should be reported.
The number of wave-
The number of available wavelengths should be consistent at the two
lengths and the number
ends of an optical layer WASONTE link, and the number of available
of channels at the two
channels at the two ends of an electrical layer WASON TE link should
ends of a TE link
be consistent. Otherwise, residual information may exist.
TE link status
The TE link status should be normal. Locate and remove the fault if the
TE link status is abnormal.
6-3
SJ-20110728142617-001|2011-09-27(R1.0)
6.1.3.3 Checking the Alarms and Events on the Control Plane

Purpose
Focus on the alarms and abmornal events occurring on the control plane during routine
maintenance, including current alarms and history alarms, so as to timely locate and
remove the faults occurring on the control plane.
Prerequisite
Maintenance Period
Every day
Tools and Materials

NetNumen U31
Steps
1. Select all the WASON nodes in the whole network. Select Fault Management >
Synchronize Active Alarms > Custom Query.
2. In the Custom Query > New Active Alarm Query > Alarm Code window, enter the
ASON value and then click Filter.
3. The current alarms and events occurring on the control plane are displayed in the
current alarm list.
4. Select all WASON nodes in the whole network. In the Fault Management >
Synchronize Active Alarms window, repeat steps 1 through 3 to query the history
alarms and events occurring on the control plane.
6.1.3.4 Maintenance-Related Configuration

Configuring Node Parameters
The node ID of an intelligent NE should be unique in a network. The node ID of an NE must
be decided during network planning. The node ID cannot be the same as the IP address
of the NE.
To modify a node ID, first check whether the node has any intelligent services (including
abnormal services). If yes, delete the intelligent services. After the node ID is modified,
the intelligent NE will restarts automatically to validate the modification. Check the
configuration of the neighbor NE and re-configure the SOSC static route.
6-4
SJ-20110728142617-001|2011-09-27(R1.0)
l
l
Note:
Before modifying the node parameters, it is necessary to delete the transmission
interfaces of the intelligent NEs.
Node ID is the only identifier of WASON in the whole network, do not modify it
frequently.
Configuring the I-NNI

Follow the correct configuration order when configuring the I-NNI. The out-band neighbor
cannot be configured until the out-band control interface is configured. To delete the
out-band control interface, ensure that no related out-band neighbor exists.
Deleting Services
To delete an intelligent service, ensure that all nodes by which the intelligent service passes
are online, and there are no restarted or offline nodes.
6.2 Troubleshooting
6.2.1 Troubleshooting Principles
Obey the following principles during troubleshooting: Check, inquiry, thinking, and action.
Check
After you arrive at the site, the first thing is to carefully check the fault symptom, including
the fault location, alarm cause, severity, and harm. You can accurately locate the fault
cause only after thoroughly analyzing the fault symptom.
To query the NMS alarms, select Alarm > Alarm Monitoring.
Inquiry
After checking the fault symptom, inquire onsite operators to obtain information about the
fault cause, for example, whether data has been modified, files have been deleted, circuit
boards have been replaced, a power failure has occurred, or lighting stroke has occurred.
Thinking
Analyze the fault based on the fault symptom and inquiry results, and locate the fault point
and fault cause.
Action
After locating the fault cause, take proper actions such as configuration data modification
or board replacement to remove the fault.
6-5
SJ-20110728142617-001|2011-09-27(R1.0)
6.2.2 Solution to Common Faults

Deleting Boards Failure
l
Fault Phenomenon
The NMS indicates that the SPC services on the board are deleted.
Causes
There are SPC services on the board.
Solutions
You need to view the corresponding alarms. If the board must be deleted, you need
to delete services and fiber connections related to the board.
Modifying Board Attributes Failure

l
Fault Phenomenon
The NMS indicates that the modified attributes affect the SPC service.
Causes
There are SPC services on the board.
Solutions
You need to view the corresponding alarms. If the board attributes must be modified,
you need to delete services and fiber connections related to the board.
Deleting Fiber Connection Failure

l
Fault Phenomenon
The NMS indicates that the deleted fiber connections have SPC service.
Causes
There are SPC services on the fiber connections.
Solutions
You need to view the corresponding alarms. If the fiber connection must be deleted,
you need to delete services related to fiber connections.
Adding Transmitting Interface Failure

l
Fault Phenomenon
The management plane displays the response to adding transmitting interface failure.
Causes
1. Illegal parameters
2. Transmitting ports exist.
3. Physical port verification failure
Solutions
6-6
SJ-20110728142617-001|2011-09-27(R1.0)
1. You need to view the corresponding alarms to determine which parameters are
illegal and reset the parameters after modifying he parameters.
2. You need to view the corresponding alarms to determine the caused of verification
failure and then re-configure the parameters after modifying the related physical
resource information (board or fiber)
3. The wavelength/sub-wavelength may not support the physical verification and
cause the physical verification failure, so you need to view the label resources
supported by current transmitting interface by viewing the TAP command line.
Modifying Transmitting Interface Failure

l
Fault Phenomenon
The management plane displays the response to modifying transmitting interface
failure .
Causes
2. Transmitting ports exist.
3. Transmitting ports bear services.
4. Configuring the transmitting capacity of transmitting ports incorrectly.
Solutions
1. You need to view the corresponding alarms to determine which parameter is illegal
and modify it. After that, configure the transmitting interface again.
2. If all labels allocated to the management plane bear the SPC service, you
cannot modify the transmitting port. Otherwise, the transmitting capacity of the
transmitting port is configured incorrectly will be prompted.
3. You are not allowed to modify the transmitting port in the following scenario,
otherwise Transmitting capacity of the transmitting port is configured incorrectly
will be prompted.
If the new wavelength added to the OCh transmitting port is not supported
by the port, obtain the wavelength that is not supported and then use TAP
command line to view the current wavelength and configure it after the
modification.
Deleting Transmitting Interface Failure

l
Fault Phenomenon
The management plane displays the response to deleting transmitting interface
failure.
Causes
2. Transmitting ports do not exist.
3. The operation is not supported.
4. Transmitting port bear services.
Solutions
6-7
SJ-20110728142617-001|2011-09-27(R1.0)
1. You need to view the corresponding alarms to determine which parameter is

illegal, and modify it. After that, configure the transmitting interface again.
2. You are not allowed to delete the transmitting port in the following scenario, otherwise The operation is not supported will be prompted.
The transmitting interface corresponds to the member link of bundling link.
The transmitting port is a virtual interface.
3. You are not allowed to delete the transmitting port in the following scenario,
otherwise The transmitting port bears services will be prompted.
The transmitting port bears services.
Modifying TE Links Failure

l
Fault Phenomenon
The management plane displays the response to modifying TE link failure.
Causes
2. TE links do not exist.
3. The operation is not supported.
Solutions
1. You need to view the corresponding alarms to determine which parameter is
illegal, and modify it. After that, configure the transmitting interface again.
2. You are not allowed to modify the TE link in the following scenario, otherwise The
operation is not supported will be prompted.
a. You cannot modify a TE link, when it bears services.
b. You cannot modify a TE link, if it created by FA_LSP.
Creating Service Failure-Parameter Errors

l
Fault Phenomenon
After the request for creating services is issued through NMS, the NMS displays that
the services are created unsuccessfully and prompts that parameters are incorrect.
Causes
Illegal parameters
Solutions
You need to view the corresponding alarms to determine which parameter is illegal.
Creating Service Failure-Creation Failure

l
Fault Phenomenon
After the request for creating services is issued through NMS, the control plane has
accepted the command and processed the command and reports that the service is
created unsuccessfully.
6-8
SJ-20110728142617-001|2011-09-27(R1.0)
Causes
The control plane reports that the service is created unsuccessfully.
Solutions
You need to view the corresponding alarms to determine the causes leading to service
creating failure.
Creating Service Failure-No Response

l
Fault Phenomenon
After the request for creating services is issued through NMS, the control plane has
accepted the command and processed the command and then returns no response.
Causes
Internal program faults
Solutions
You need to view the current service state to analyze in which state the service is.
Handling Link Fault

Related Information
l I-NNI TE links are generated automatically and maintained by the control plane. Users
cannot create or delete the TE link.
l The control plane needs to check whether the data transmission links are
connected correctly according to the configured protocol information. When the data
transmission link is invalid, if there is bearer service, both the service alarm and
transmitting port alarm information will be reported. If there is no bearer service,
transmitting port alarm information alone will be reported.
l There are two ways for checking the data transmission link connectivity:
When the control plane is running, check the connectivity periodically,
After the control plane restarts, check the connectivity.
Fault Phenomenon
The TE link state is Down (There is an alarm and the link weight is infinite.)
Influence on System
If there are TE link faults, the services on the TE link are broken and the link cannot
be used again.
Causes
There are alarms on transmitting interface.
Physical fiber connection error
Board errors (optical layer amplification board, electrical line-side board)
Invalid control channel between the node and neighbor node

6-9
SJ-20110728142617-001|2011-09-27(R1.0)
Solutions
1. Check whether there are alarms related to transmitting interfaces. If yes, please
handle alarms according to actual conditions.
2. Check whether there is physical fiber connection error, if yes, connect the fiber
again.
3. Check whether there are abnormal alarm to be reported.
4. Check whether the signaling communication between nodes by using PING. If
PING fails, check whether the node label is correct, if yes, check whether the
SOSC static route is configured correctly.
Handling Service Interruption

Related Information
When services are running properly, the optical physical failure or link resources being
taken lead to service interruption.
l
Fault Phenomenon
Services are broken, meters does not function and the service-related alarms are
reported.
Influence on System
Services are affected or services are broken permanently. Or, the dynamic reroutes
are enabled and other network resources are taken so that other services are affected.
Causes
Faults of optical channel where the service path is located
Network resources are taken.
Solutions
1. Check whether the service board client side and line side report the related alarms
(no optical input power, high optical input power). If yes, check whether the
physical optical fibers where the service path is located are connected. If not,
check the optical power and adjust it.
2. Check the how the resources are used in the whole network and whether there i
conflict, if yes, plan the network resource again.
6-10
SJ-20110728142617-001|2011-09-27(R1.0)
Appendix A
Compliant Standards
Table of Contents
Compliant ITU-T Standards .................................................................................... A-1
Compliant IETF Standards...................................................................................... A-3
Compliant OIF Standards ....................................................................................... A-4
A.1 Compliant ITU-T Standards

A.1.1 Architecture and Requirements
The standards related to architecture and requirements are listed in Table A-1.
Table A-1 List of Standards (Architecture and Requirements)
Standard No.
G.8080/Y.1304
G.807/Y.1302
G.8081/Y.1353
Standard Name
Architecture for the automatically switched optical network (WASON)
Requirements for automatic switched transport networks (ASTN), Distributed call
and connection management (DCM)
Terms and definitions for Automatically Switched Optical Networks (WASON)
(06/2004)
G.7718/Y.1709
Framework for WASON management (02/2005)
G.7715.1/Y.1706.1
WASON routing architecture and requirements for link state protocols (02/2004)
A.1.2 Call and Connection Management

The relevant call and connection management standards are listed shown in Table A-2.
Table A-2 List of Standards (Call and Connection Management)
Standard No.
Standard Name
G.7713.1/Y.1704.1
DCM signalling mechanism using PNNI/Q.2931
G.7713.2/Y.1704.2
DCM signalling mechanism using GMPLS RSVP-TE
G.7713.3/Y.1704.3
DCM signalling mechanism using GMPLS CR-LDP
A-1
SJ-20110728142617-001|2011-09-27(R1.0)
A.1.3 Discovery and Link Management

The relevant discovery and link management standards are listed in Table A-3.
Table A-3 List of Standards (Discovery and Link Management)
Standard No.
Standard Name
G.7714/Y.1705
Generalized automatic discovery techniques
G.7714.1/Y.1705.1
Usage of the different discovery mechanisms
G.7715/Y.1706
G.7716/Y.1707
G.7717/Y.1708
Architecture and requirements of routing for automatic switched transport network

Architecture and requirements of link resource management for automatically
switched transport networks
ASTN connection admission control
A.1.4 Other Related ITU-T Standards

Other related protocols and standards are listed in Table A-4.
Table A-4 List of Other Related Protocols and Standards
Standard No.
Standard Name
G.872
Architecture of optical transport networks
G.709/Y.1331
Interface for the optical transport network (OTN)
G.959.1
Optical transport network physical layer interfaces
G.874
Management aspects of the optical transport network element
G.874.1
G.875
Optical transport network (OTN) protocol neutral management information

model for the network element view
Optical transport network (OTN) management information model for the network element view
G.7041/Y.1303
Generic framing procedure (GFP)
G.7042/Y.1305
Link capacity adjustment scheme (LCAS) for virtual concatenated signals
G.65x
series on optical fibre cables and test methods
G.693
Optical interfaces for intra-office systems
G.7710/Y.1701
Common equipment management function requirements
G.7712/Y.1703
Architecture and specification of data communication network
G.806
Characteristics of transport equipment-Description methodology and generic

functionality
A-2
SJ-20110728142617-001|2011-09-27(R1.0)
Appendix A Compliant Standards
A.2 Compliant IETF Standards

The compliant IETF standards are listed in Table A-5.
Table A-5 List of Compliant IETF Standards
Standard Name
Standard No.
Link Management Protocol
draft-ietf-ccamp-lmp
SONET/SDH Encoding for LMP Test messages
draft-ietf-ccamp-lmp-test-sonet-sdh
OSPF Extensions in Support of Generalized Multi-Protocol La-
draft-ietf-ccamp-ospf-gmpls-exten-
bel Switching
sions
Resource ReSerVation Protocol (RSVP) -Version 1 Functional

Specification
RFC 2205
OSPF Version 2
RFC 2328
The OSPF Opaque LSA Option
RFC 2370
RSVP Refresh Overhead Reduction Extensions
RFC 2961
Extensions to RSVP for LSP Tunnels
RFC 3209
GMPLS Signaling Functional Description
RFC 3471
CR-LDP Extensions
RFC 3472
GMPLS Signaling - RSVP-TE Extensions
RFC 3473
Traffic Engineering (TE) Extensions to OSPF Version 2
RFC 3630
GMPLS Architecture
RFC 3945
GMPLS Extensions for SONET/SDH Control
RFC 3946
GMPLS Signaling Extensions for WASON
RFC 4139
Link Bundling in MPLS Traffic Engineering (TE)
RFC 4201
Routing Extensions in Support of GMPLS
RFC 4202
OSPF Extensions in Support of Generalized Multi-Protocol Label Switching

Link Management Protocol
RFC 4203
RFC 4204
Label Switched Paths (LSP) Hierarchy with GMPLS Traffic Engineering (TE)
RFC 4206
SONET/SDH Encoding for Link Management Protocol (LMP)
RFC 4207
DWDM LMP
RFC 4209
GMPLS Routing for WASON
RFC 4258
GMPLS Recovery Functional Specification
RFC 4426
Analysis of GMPLS Recovery Mechanism
RFC 4428
A-3
SJ-20110728142617-001|2011-09-27(R1.0)
A.3 Compliant OIF Standards

The compliant OIF standards are listed in Table A-6.
Table A-6 List of Compliant OIF Standards
Standard Name
Standard No.
User Network Interface (UNI) 1.0 Signaling Specification, Release 2:

Common Part
RSVP Extensions for User Network Interfaces (UNI) 1.0 Signaling,
Release 2
User Network Interface (UNI) 1.0 Signaling Specification, Common
Part
OIF-UNI-01.0-R2-Common
OIF-UNI-01.0-R2-RSVP
OIF-UNI-02.0-Common
RSVP Extensions for User Network Interfaces (UNI) 1.0 Signaling
OIF-UNI-02.0-RSVP
Intra-Carrier E-NNI Signaling Specification
OIF-E-NNI-Sig-01.0
External Network-Network Interface (E-NNI) OSPF-based Routing 1.0 (Intra-Carrier) Implementation Agreement
Intra-Carrier E-NNI Signaling Specification
OIF-E-NNI-OSPF-01.0
OIF-E-NNI-Sig-02.0
External Network-Network Interface (E-NNI) OSPF-based Routing 2.0 (Intra-Carrier) Implementation Agreement
OIF-E-NNI-OSPF-02.0
Security Extension for UNI and NNI
OIF-SEP-01.0
Addendum to the Security Extension for UNI and NNI
OIF-SEP-02.1
Security for Management Interfaces to Network Elements
OIF-SMI-01.0
Addendum to the Security for Management Interfaces to Network Elements
OIF-SMI-02.1
Call Detail Records for OIF UNI 1.0 Billing.
OIF-CDR-01.0
OIF Control Plane Logging and Auditing with Syslog
OIF2003.119.06
A-4
SJ-20110728142617-001|2011-09-27(R1.0)
List of Figure
Figure 1-1 ASON Architecture .................................................................................. 1-4
Figure 1-2 Overlay Model Diagram ........................................................................... 1-8
Figure 1-3 Peer Model Diagram ................................................................................ 1-9
Figure 1-4 Interface Protocols in ASON .................................................................. 1-10
Figure 1-5 GMPLS Protocols for ASON .................................................................. 1-11
Figure 1-6 Mesh Networking ................................................................................... 1-14
Figure 1-7 Hybrid Networking via UNI ..................................................................... 1-15
Figure 1-8 Hybrid Networking via NNI ..................................................................... 1-16
Figure 1-9 Direct and Indirect Request via UNI ....................................................... 1-22
Figure 2-1 Integrated WASON Solution of ZTE ......................................................... 2-6
Figure 3-1 WASON Initialization Configuration Flow Chart ........................................ 3-2
Figure 4-1 Network Topology Map ............................................................................ 4-2
Figure 4-2 WASON Management Menu.................................................................... 4-3
Figure 4-3 Enabling the Control Plane Window ......................................................... 4-5
Figure 4-4 Node Configuration Window .................................................................... 4-7
Figure 4-5 Static Route Configuration Window.......................................................... 4-8
Figure 4-6 Configuring Global Automatic Discovery Parameters Window................ 4-10
Figure 4-7 I-NNI Interface Config - NET-E Window ................................................. 4-13
Figure 4-8 I-NNI Transmit Interface Property Dialog Box......................................... 4-14
Figure 4-9 I-NNI Transmit Interface Wavelength Property Dialog Box ..................... 4-16
Figure 4-10 I-NNI Interface Config Window (Out-of-band Control Interface) ............ 4-17
Figure 4-11 I-NNI Interface Configuration Window (Out-of-band Neighbor) ............. 4-18
Figure 4-12 TE Link Config (Local Config) Window ................................................. 4-20
Figure 4-13 TE Link Config (Whole Network Query) Window .................................. 4-22
Figure 4-14 Control Plane Running Topology Dialog Box ........................................ 4-23
Figure 4-15 NE Topology ........................................................................................ 4-31
Figure 4-16 Call Management Window ................................................................... 4-32
Figure 4-17 Selecting End A Dialog Box ................................................................. 4-32
Figure 4-18 Selecting End Z Dialog Box.................................................................. 4-33
Figure 4-19 Dialog Box of Configuring the Common Properties of a New
Call ....................................................................................................... 4-34
Figure 4-20 Protection Setting Window ................................................................... 4-36
Figure 4-21 Restoration Setting Window ................................................................. 4-36

Figure 4-22 Route Strategy Setting Window ........................................................... 4-38
Figure 4-23 Configuring Route Constraints Dialog Box ........................................... 4-39
Figure 4-24 Dialog Box of Configuring the Basic Properties of a Call ...................... 4-40
Figure 4-25 Setting Protection Window ................................................................... 4-41
Figure 4-26 Setting Restoration Window ................................................................. 4-41
Figure 4-27 Setting Route Strategy Window ........................................................... 4-42
Figure 4-30 Setting the Protection Window ............................................................. 4-44
Figure 4-31 Setting the Restoration Window ........................................................... 4-44
Figure 4-32 Setting the Route Strategy Window...................................................... 4-45
Figure 4-33 Dialog Box of Configuring the Route Constraints.................................. 4-45
Figure 4-35 Setting Protection Window ................................................................... 4-47
Figure 4-36 Setting Restoration Window ................................................................. 4-47
Figure 4-37 Setting Route Strategy Window ........................................................... 4-47
Figure 4-39 Call Query Results Dialog Box 1 .......................................................... 4-49
Figure 4-40 Call Query Results Dialog Box 2 .......................................................... 4-49
Figure 4-41 Call Management Dialog Box (Call Modification).................................. 4-50
Figure 4-42 Call Modification Dialog Box (Common Properties) .............................. 4-51
Figure 4-43 Call Modification Dialog Box (Protection Setting).................................. 4-52
Figure 4-44 Call Modification Dialog Box (Restoration Setting) ............................... 4-53
Figure 4-45 Call Modification Dialog Box (Route Strategy) ...................................... 4-54
Figure 4-46 Call Modification Dialog Box (Route Constraint Selection).................... 4-55
Figure 4-47 Modifying NE Properties Menu............................................................. 4-55
Figure 4-48 Call Management Dialog Box............................................................... 4-56
Figure 4-49 Service View Window........................................................................... 4-57
Figure 4-50 SPC Optimize Rerouting Menu ............................................................ 4-58
Figure 4-51 Connection Selector Dialog Box........................................................... 4-58
Figure 4-52 Optional Detail Route Constraint Dialog Box ........................................ 4-59
Figure 4-53 SPC Preset Rerouting Menu ................................................................ 4-60
Figure 4-54 SPC Synchronization Window.............................................................. 4-61
Figure 4-55 SPC Maintenance Window .................................................................. 4-62
II
List of Figure
Figure 4-56 Restoration Activation Window............................................................. 4-63

Figure 4-57 Protection Parameters Window ............................................................ 4-63
Figure 4-58 Switch Routing Window ....................................................................... 4-64
Figure 4-59 Auto Discovery Enable Window ........................................................... 4-65
Figure 4-60 Bundled Link Window .......................................................................... 4-66
Figure 4-61 Dialog Box of Configuring Optical Impairment Parameters .................. 4-68
Figure 4-62 Line Card Optical Impairment Parameters Dialog Box.......................... 4-69
Figure 4-63 Dialog Box of Amplifier Optical Impairment Parameters ...................... 4-70
Figure 4-64 Dialog Box of Link Optical Impairment Parameters .............................. 4-71
Figure 4-65 Dialog Box of Connection Crankback Policy......................................... 4-73
Figure 4-66 Fiber Link Data Comparison Window ................................................... 4-75
Figure 4-67 Rack/Shelf Configuration Window ........................................................ 4-77
Figure 4-68 PCE Shelf Configuration Dialog Box .................................................... 4-77
Figure 4-69 PCE Shelf Dialog Box .......................................................................... 4-78
Figure 4-70 Dialog Box of Creating a PCE Device ................................................. 4-79
Figure 4-71 PCE Shelf Dialog Box .......................................................................... 4-79
Figure 4-72 Dialog Box of Deleting a PCE Device .................................................. 4-79
Figure 4-73 Node ID Configuration Dialog Box........................................................ 4-80
Figure 4-74 Control Interface Management Dialog Box ........................................... 4-81
Figure 4-75 Control Interface Neighbor Dialog Box ................................................. 4-82
Figure 4-76 Auto Discovery Property Window ......................................................... 4-83
III
List of Figure
List of Table
Table 2-1 ZXUCP A200 Product Functions ............................................................... 2-2
Table 4-1 Meanings of WASON Management Submenus ......................................... 4-3
Table 4-2 Global Automatic Discovery Parameter Config Dialog Box ...................... 4-10
Table 4-3 Description of the I-NNI Transmit Interface Property Dialog Box .............. 4-14
Table 4-4 Description of the Out-of-band Control Interface Page............................. 4-17
Table 4-5 Description of the Out-of-band Neighbor Page ........................................ 4-18
Table 4-6 Description of the Local Configuration ..................................................... 4-20
Table 4-7 MAP Combination Mode-OAC Port Service Establishment Grade ........... 4-25
Table 4-8 SWITCH Combination Mode-OAC Port Service Establishment
Grade..................................................................................................... 4-27
Table 4-9 SWITCH Combination Mode-OCH Port Service Establishment
Grade..................................................................................................... 4-30
Table 4-10 Basic Properties of the Call ................................................................... 4-34
Table 4-11 Description of the Protection Setting Window......................................... 4-36
Table 4-12 Description of the Restoration Setting Window ...................................... 4-37
Table 4-13 Description of the Route Strategy Window............................................. 4-38
Table 4-14 Description of the Bundled Link Dialog Box ........................................... 4-67
Table 4-15 Description of the Line Card Optical Impairment Parameters ................ 4-69
Table 4-16 Description of the Amplifier Optical Impairment Parameters ................. 4-70
Table 4-17 Description of the Link Optical Impairment Parameters ......................... 4-71
Table 4-18 Description of Connection Crankback Policy Parameters....................... 4-73
Table 4-19 Description of Parameters in the Topo Link Compare Window ............... 4-75
Table 4-20 Description of the PCE Shelf Configuration............................................ 4-78
Table 5-1 Alarms on the Control Plane...................................................................... 5-1
Table 5-2 List of Events............................................................................................. 5-2
Table 5-3 Properties of the Connection Failure Alarm ............................................... 5-3
Table 5-4 Parameters of the Connection Failure Alarm ............................................. 5-3
Table 5-5 Properties of the Connection Degradation Alarm ....................................... 5-4
Table 5-6 Parameters of the Connection Degradation Alarm ..................................... 5-4
Table 5-7 Properties of the RSVP Hello Failure Alarm............................................... 5-6
Table 5-8 Parameters of the RSVP Hello Failure Alarm............................................. 5-6
Table 5-9 Properties of the LMP Hello Failure Alarm ................................................. 5-6
Table 5-10 Parameters of the LMP Hello Failure Alarm ............................................. 5-7
Table 5-11 Properties of the Node Parameters Not Configured Alarm ....................... 5-7
Table 5-12 Properties of the Service Failure Alarm.................................................... 5-8
Table 5-13 Parameters of the Service Failure Alarm ................................................. 5-8
Table 5-14 Properties of the Transmit Interface Discovery Failure Alarm................... 5-9
Table 5-15 Parameters of the Transmit Interface Discovery Failure Alarm................. 5-9
Table 5-16 Properties of the Miswire Alarm ............................................................. 5-10
Table 5-17 Parameters of the Miswire Alarm ........................................................... 5-10
Table 5-18 Properties of the neighbor discovery failure alarm ................................. 5-11
Table 5-19 Properties of the Transmit Interface Misconnection Alarm ..................... 5-12
Table 5-20 Parameters of the Transmit Interface Misconnection Alarm ................... 5-12
Table 5-21 Properties of the Residual Timeslot Alarm ............................................. 5-13
Table 5-22 Parameters of the Residual Timeslot Alarm ........................................... 5-13
Table 5-23 Properties of the Inconsistent Resource Management Rights
Alarm ..................................................................................................... 5-14
Table 5-24 Parameters of the Alarm About Inconsistency of Resource Management
Rights .................................................................................................... 5-14
Table 6-1 Criteria for Checking the Status of SPC Services....................................... 6-2
Table 6-2 Criteria for TE Link Check.......................................................................... 6-3
Table A-1 List of Standards (Architecture and Requirements) ...................................A-1
Table A-2 List of Standards (Call and Connection Management)...............................A-1
Table A-3 List of Standards (Discovery and Link Management).................................A-2
Table A-4 List of Other Related Protocols and Standards..........................................A-2
Table A-5 List of Compliant IETF Standards..............................................................A-3
Table A-6 List of Compliant OIF Standards ...............................................................A-4
VI
Glossary
ADM
- Add/Drop Multiplexer
APS
- Automatic Protection Switching
ATM
- Asynchronous Transfer Mode
BGP
- Border Gateway Protocol
BOD
- Bandwidth On Demand
CAC
- Call Admission Control
CR-LDP
- Constrained Route - Label Distribution Protocol
CSPF
- Constrained Shortest Path First
CUG
- Closed User Group
DCN
- Data Communications Network
DDRP
- Domain to Domain Routing Protocol
DWDM
- Dense Wavelength Division Multiplexing
DXC
- Digital Cross Connect
E-NNI
- External Network-Network Interface
ESCON
- Enterprise System Connection
FC
- Fiber Channel
FEC
- Forward Error Correction
VII
FICON
- Fiber Connection
GMPLS
- Generalized Multi-Protocol Label Switching
I-NNI
- Internal Network-Network Interface
IETF
- Internet Engineering Task Force
IP
- Internet Protocol
IS-IS
- Intermediate System-to-Intermediate System
LMP
- Link Management Protocol
LSP
- Label Switched Path
MPLS
- Multi Protocol Label Switching
NNI
- Network Node Interface
NRZ
- Non-Return to Zero
NSAP
- Network Service Access Point
ODU
- Optical Channel Data Unit
OIF
- Optical Internetworking Forum
OSC
- Optical Supervision Channel
OSNR
- Optical Signal-Noise Ratio
OSPF
- Open Shortest Path First
OSPF-TE
- Open Shortest Path FirstTraffic Engineering
OTN
- Optical Transport Network
VIII
Glossary
OVPN
- Optical Virtual Private Network
PMD
- Polarization Mode Dispersion
PNNI
- Private or Public Network-to-Network Interface
RSVP
- Resource ReSerVation Protocol
RSVP-TE
- Resource ReSerVation Protocol - Traffic Engineering
SAN
- Storage Area Network
SLA
- Service Level Agreement
SPC
- Soft Permanent Connection
SPF
- Shortest Path First
SRLG
- Shared Risk Link Group
TE
- Traffic Engineering
TTI
- Trail Trace Identifier
UNI
- User Network Interface
UNI-C
- UNI Signaling Agent - Client
UNI-N
- UNI Signaling Agent - Network
VC-n
- Virtual Container, level n
VPN
- Virtual Private Network
WDM
- Wavelength Division Multiplexing
IX

EONA

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

EONA

Caricato da

Copyright:

Formati disponibili

ZXUCP A200

Unified Control Plane for WDM/OTN

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

ZXUCP A200 (V1.20) First release

Serial Number: SJ-20110728142617-001

Chapter 2 ZXUCP A200 (WASON) Function and Solution ..................... 2-1

Chapter 3 ZXUCP A200 Debugging .......................................................... 3-1

3.2.2 Updating and Downloading Boot/Fpga Program ........................................ 3-3

Chapter 4 ZXUCP A200 Configuration Management............................... 4-1

4.9.1 Operation Purpose ................................................................................. 4-60

Chapter 5 ZXUCP A200 Alarms and Events............................................. 5-1

5.3.8 Miswire ................................................................................................. 5-10

Chapter 6 Network Maintenance of ZXUCP A200 ................................... 6-1

Appendix A Compliant Standards ........................................................... A-1

What Is in This Manual

Describes the background, functions, architecture, protocols,

networking, protection and services of ASON.

Chapter 2 ZXUCP A200

Describes the concepts and functions of WASON, functions of

(WASON) Functions and

ZTE ZXUCP A200 and ZXUCP A200 WASON solutions.

Describes the initialization configuration of the ZXUCP A200

Chapter 4 ZXUCP A200

Describes the ZXUCP A200 product and WASON management.

Describes the alarm handling and event handling related to

ZXUCP A200 WASON functions.

Chapter 6 ZXUCP A200

Describes the routine maintenance items and troubleshooting

Routine Maintenance and

methods of ZXUCP A200.

Lists the ITU-T, IETF and OIF standards related to WASON.

Refers to clicking the secondary mouse button (usually the right

occur if you ignore this safety warning.

occur if you ignore this safety warning.

mance, or other unpredictable result may occur if you ignore this

Provides additional information about a topic.

3. Manual Usage Convention

1.1 Background of ASON

1.1.2 Problems in a Traditional Optical Network

ZTE Proprietary and Confidential

ZXUCP A200 User Manual

End-to-end services can only be configured segment by segment via a network

1.1.3 Demands Generated by ASON

1.1.4 Advantages of ASON

ZTE Proprietary and Confidential

Chapter 1 Fundamentals of ASON

ASON has the following advantages.

1.2 ASON Functions

ZTE Proprietary and Confidential

ZXUCP A200 User Manual

1.3 ASON Architecture

ZTE Proprietary and Confidential

Chapter 1 Fundamentals of ASON

It automatically discovers the adjacency relationship and link status (such as

It supports to set up, release, maintain the end-to-end connections through

It selects proper routes for connections through route selections.

It executes the protection and restoration when network faults occur.

It provides a proper naming and address mechanism.

Topology database that can be modified and maintained in a distributed way.

Fast and flexible restoration mechanism.

It supports various transport infrastructures, such as the SDH transport network

It supports various traffic control engineering, protection and restoration

It supports various control protocols.