eona

ZXUCP A200Unified Control Plane for WDM/OTN

User Manual

Version: V1.20

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright 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 ContentsPreface............................................................................................................. 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

I

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

V

PrefaceApplicable Product

This manual is applicable to Unitrans ZXUCP A200 (V1.20) Unified Control Plane forWDM/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/OTNUser Manual. The following table describes the chapters in this manual.

Chapter Content

Chapter 1 Fundamentals of

ASON

Describes the background, functions, architecture, protocols,

networking, protection and services of ASON.

Chapter 2 ZXUCP A200

(WASON) Functions and

Solutions

Describes the concepts and functions of WASON, functions of

ZTE ZXUCP A200 and ZXUCP A200 WASON solutions.


Initialization Configuration

Describes the initialization configuration of the ZXUCP A200

equipment.


Configuration Management

Describes the ZXUCP A200 product and WASON management.

Chapter 5 ZXUCP A200 Alarms

and Events

Describes the alarm handling and event handling related to

ZXUCP A200 WASON functions.


Routine Maintenance and

Troubleshooting

Describes the routine maintenance items and troubleshooting

methods of ZXUCP A200.

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 Planning engineersl Debugging engineersl Network supervision engineersl Maintenance engineers

Conventions

1. Mouse Operation Conventions

I

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

Danger

A serious accident, such as casualties or equipment damage may

occur if you ignore this safety warning.

Warning

A major accident, such as casualties or equipment damage may

occur if you ignore this safety warning.

Caution

Equipment damage, data loss, degradation of equipment perfor-

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

safety warning.

NoteProvides additional information about a topic.

Tip

Indicates a suggestion or hint to make things easier or more pro-

ductive.

3. Manual Usage Convention

This manual takes the ZXUCP A200 client running on the Windows platform as anexample for illustration.

II

Chapter 1Fundamentals of ASONTable of Contents

Background of ASON .................................................................................................1-1ASON Functions ........................................................................................................1-3ASON Architecture .....................................................................................................1-4ASON Protocols .......................................................................................................1-10Networking and Protection of ASON.........................................................................1-14ASON 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 anASON, service requests are initiated dynamically by a user end or a network managementsystem. NEs select routes automatically for these requests and apply the signalingcontrol to establish, modify, release, automatically protect, restore and discover serviceconnections. ASON is a new-generation optical network, which integrates the switch andtransport functions.

Generation of ASON

The concept of ASON was first put forward in 2000. Its basic idea is to introduce a controlplane into the traditional optical transport network, so as to allocate network resources inreal time according to the actual needs. In this way, the optical network can evolve to ahigh-capacity intelligent network, which is configurable and supports multiple channels. Asthe core technology for building a new-generation optical network, ASON is supported bythe compatible and extensible hardware system. It integrates advanced software systeminto the hardware platform to form an underlying platform with more elasticity, convertsthe optical layer from a static transmission media to a dynamic, intelligent optical networkhierarchy, and comprehensively promotes the transmission efficacy as well.

1.1.2 Problems in a Traditional Optical NetworkIn a traditional optical network, as the network scale and network capacity get increasinglylarger, 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 followingshortcomings:

l End-to-end services can only be configured segment by segment via a networkmanagement system. Therefore, it requires much time. Fast automatic setup andprotection of end-to-end services is unavailable in traditional optical networks.

l Network load cannot be balanced and optimized automatically.l Differentiated services are unavailable without diverse QoS.l Network topology changes cannot be displayed in real time in a network management

system, which makes real-time management difficult.l Traditional optical networks use network management systems with multiple

hierarchies, which manage a great diversity of equipment. Accordingly, it is difficult touse a unified network management system to manage all kinds of equipment, suchas DXC, ADM, and DWDM equipment.

l Different models of equipment are used on the backbone layer with lots of connectionsamong optical interfaces, which makes the network structure complex.

l Traditional optical networks generally use a ring networking mode. It results in theexistence of many cross-ring nodes, which become the bottleneck for the trafficscheduling.

l Service commissioning takes much time and increases the maintenance cost.

1.1.3 Demands Generated by ASONWith the rapid growth in IP services, the percentage of data services increases greatly innetworks. IP services feature the traffic burst and sudden changes of traffic directions.Thus, it requires new network technologies to guarantee the transmission QoS. Thecommercial use of large-capacity optical cross-connect components, adjustable lasercomponents, adjustable OTU devices and dynamic dispersion compensation devicescan solve the WDM dispersion restriction problem and provide technical support for thedynamic ASON network.

l With the growth of data services, the bursting bandwidth demands of data serviceswill become the mainstream service in future and challenge the semi-static mode oftransmission networks.

l High expansibility is required for transmission networks with the rapid growth of dataservices.

l Large capacity and bandwidth, high reliability, flexibility and fast commissioning ofoptical networks are needed.

l Diverse applications and services are required.l 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 ASONASON, as a new-generation optical network, not only satisfies the new demands of moderntelecommunication services, but also solves problems of traditional optical networks.

1-2


Chapter 1 Fundamentals of ASON

ASON has the following advantages.

l It supports the flexible traffic scheduling with high capacity and multiple granularities.l It has a small number of devices and a high utilization ratio, so that the network has

a clear structure.l It supports the flexible mesh networking mode, which has strong self-healing

capability, high scalability and high bandwidth utilization ratio.l It supports the automatic discovery of network topology.l It supports the automatic balancing, optimizing of link load as well as the dynamic

bandwidth allocation so as to improve the bandwidth utilization ratio.l It supports the fast and flexible service commissioning based on signaling requests.l It supports the end-to-end (cross-ring) traffic protection.l The network management is simplified. A unified NMS is implemented on different

networks. Therefore, different networks can be interconnected eventually.l It reduces the service setup time. The dynamic request and release of bandwidth is

supported.l 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 FunctionsThe intelligent functions of ASON are mainly implemented by the control plane, whichprovides basic functions and core functions. The basic functions of the ASON controlplane include routing, signaling, link management and unit interface technology. The corefunctions of the ASON control plane include connection control, network survivability andnew services.

Basic Functions

Basic functions constitute the basic platform of the ASON control plane. It is the foundationof 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.

l Signaling function: includes the setup, release and maintenance of the LabelSwitching Path (LSP), processing LSP-related requests (including setup request ofSPC) that come from the management plane and maintaining signalling sessions.

l Link management function: includes the discovery function (including the neighbordiscovery and the service discovery), data channel connectivity verification,control channel maintenance, Traffic Engineering (TE) link management, and faultinformation processing.

Core Functions

Core functions are the key for realizing the intelligence of ASON.

1-3



l The connection control supports three types of ASON connection control andmanagement. Refer to the section of "Connection Types in ASON" for details.

l Protection/restoration: guarantees the survivability of ASON, which includes the localspan protection, ring protection, section-to-section protection, permanent 1+1 protec-tion based on the control plane and distributed restoration mechanism.

l Service processing: supports the transport of new intelligent value-added services,such as Bandwidth On Demand (BOD), Optical Virtual Private Network (OVPN).

l Policy management: supports the processing of calls to ensure the intelligent use ofnetwork resources.

1.3 ASON Architecture

1.3.1 Three Functional PlanesAs 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 andmanagement communication.

Figure 1-1 ASON Architecture

Control Plane

The control plane comprises a group of control components providing specific functions asrouting and signaling, and it is supported by a signaling network. The information streamneeded by the communication between the components in the control plane is obtainedthrough interfaces.

l Functions

1-4



The main functions of control plane include: collecting and distributing networktopology information on the control plane in ASON and providing routes by means ofShortest Path First algorithm. It mainly manages and controls the information stream.

It automatically discovers the adjacency relationship and link status (such asavailable capacity and faults) and supports the connection setup, release andrestoration.

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

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.

l Composition

The ASON control plane is composed of a group of communication entities thatprovide 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 andsignaling protocols.

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

Fast and flexible restoration mechanism.

l Characteristics

It supports various transport infrastructures, such as the SDH transport networkdefined in ITU-T G.803 and the Optical Transport Network (OTN) defined in ITU-TG.872.

It supports various traffic control engineering, protection and restorationmechanisms.

It supports various control protocols.

It is applicable regardless of the implementation of connection control, how thecontrol plane has been subdivided into domains and routing areas, and how thetransport resources have been partitioned into subnetworks.

It is applicable to client-layer services with the focus on real-time serviceswitching.

Transport Plane

l The transport plane provides explicit routes and circuit service stream of the serviceplane. The transport plane provides users with bidirectional or unidirectional

1-5



information transmission from one end to another end and monitors the connectionstatus information (such as faults and signal quality) and then provides it to thecontrol plane.

l It transfers detailed fault management and performance detection information. Thetransport plane, layered as defined in ITU-T G.805, supports existing and futuretransmission technologies. It provides the functions of optical signal transmission,multiplexing, protection switching configuration, cross-connection and guaranteesthe reliability of optical signals transmitted over it.

l To realize various functions of ASON, the transport planemust have a strong detectingfunction 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 managingthe transport plane, control plane and DCN. The transport plane, control planeand DCN report their management information (event, alarm, performance etc.) tothe management plane. According to the received management information, themanagement plane coordinates the works on all planes.

l In terms of logical function, the management plane can be divided into threelayers: NE layer, element management layer and network management layer. TheASON network management system can be set based on traditional managementdomain divisions, or based on the ASON control domains. Different ASON networkmanagement systems can be set for different network carriers, that is, one networkmanagement system manages the network of one carrier. When multiple controldomains exist in the network of a same carrier, different network managementsystems can be set based on the division of control domains, or the same networkmanagement system can manage multiple control domains.

1.3.2 Three Connection TypesASON supports three types of connections: permanent connection, switched connectionand soft permanent connection. They are used under different application conditions.

Permanent Connection

Permanent connection is also called provisioned connection, which is implemented by thenetwork management system or manually.

Characteristics:

l The management plane configures resources on the transport plane to set upa permanent connection. It not only initiates but also configures the permanentconnection. Once being set up, a permanent connection will always exist until themanagement plane commands to release it.

l It follows the connection setup mode in the traditional networks, in which the EMScalculates the route in advance.

1-6



l ASON can be better compatible with the traditional optical networks by issuingcommands to NEs for setting up cross-connections.

Switched Connection

Switched connection is also called signaling connection. Contrary to permanentconnection, the switched connection is established on request of the control plane, andthe configuration of transport plane resources is also completed by the control plane.

Characteristics:

l End users originate request for setting up a new dynamic connection to the controlplane .

l The control plane is responsible for completing the connection setup.l Automatic connection, the nodes are similar to that in intelligent switches.l 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 functionsdue to the introduction of switched connection, thus the needed optical channels canbe automatically provided according to user requirements. The switched connection isrealized 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 switchedconnection. It is a user-to-user connection whereby the user-to-network portion of theend-to-end connection is established by the network management system (managementplane) as a permanent connection. The network portion of the end-to-end connectionis established as a switched connection using the control plane. The release of theconnection is also completed under the command from the management plane.

Characteristics:

l The management plane and control plane work together to implement the SPC.l The management plane configures the connections between users and network.l The management plane requests the control plane to configure the network.l Similar to a leased line, it is a interim form from PC to SC.l It is the best option for carriers at present.

1-7



1.3.3 Two Relation ModelsBased on the differences of correlation between the lower-layer optical transport networkand the circuit switched device, two network models are defined in ASON, which areoverlay model and peer model.

Overlay Model

Overlay model is also called client-server model. In this model, the lower-layer opticaltransport 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 andthe client layer are differentiated clearly. They are independent with each other, and selectdifferent routes, signaling schemes and address spaces. The client layer and the opticallayer can only exchange limited controlling information through the UNI interface. Figure1-2 shows the overlay model.

Figure 1-2 Overlay Model Diagram

l The internal topology status information of the optical network is invisible to the clientlayer. For the network service of higher layer, the lower-layer optical transport networkis like a black box with some interfaces (UNI interfaces). Through these interfaces,multiple service access device (such as IP router, ATM exchange device, SDH digitalcross-connection device etc.) can apply for bandwidth resources from the opticalnetwork dynamically.

l In essence, the work that the client-server model does is to determine an interfaceprotocol between the optical network layer and the client layer, in order to providedata transmission service for the multiple service access device. To set up aclient-server model, the User-to-Network Interface (UNI) needs to be separatedfrom the Network-to-Network Interface (NNI). Its typical optical channel bandwidthcan usually provide a transmission capacity over 2.5 Gb/s, which is adequate fortransmitting IP data on WDM.

1-8



Peer Model

l In the peer model, the circuit switched devices (such as IP, ATM, SDH etc.) and theoptical network devices have equal status. In this model, a unified control plane areestablished for circuit switched devices and optical network devices. Figure 1-3 showsthe peer model.

Figure 1-3 Peer Model Diagram

l Due to the introduction of the unified control plane which takes effect on circuitswitched devices and optical network devices at the same time, the circuit switcheddevice and the optical network device do not have an obvious boundary. Therefore,the UNI in the overlay model is not needed.

l In the peer model, the topology information of all devices in the entire network canbe clearly known through every circuit switched device (such as an IP router, an ATMswitched 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 runsthrough the whole network independently. By setting a unified control plane withthe peer model, each network carrier can use the base station devices from othernetwork carriers. Thus the complexity of managing an optical network that is notunified because of using different methods can be avoided.

1-9



1.4 ASON Protocols

1.4.1 Interface ProtocolsLogically, the ASON has three kinds of standard signaling control interfaces: User NetworkInterface (UNI), Internal Network to Network Interface (I-NNI), and External Network toNetwork 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. UNIis a bidirectional signaling interface between two control plane entities, one ofwhich requests service and the other provides service. Client layer networkcan automatically request to set up a new connection, query or release existingconnection status via UNI. It supports the functions of call control, resource discovery,connection control and connection selection. Please note that it does not have theroute selection function related to UNI.

l In addition, it runs between the client and the optical network, and it supports callsecurity, authorization function, enhanced search function and enhanced numberservice. Its main functions are: connection setup, connection release, connectionmodification and status query.

l The functions of UNI need to be supported by relevant signaling protocols. Twooptional solutions are: CR-LDP and RSVP-TE.

E-NNI

l It defines the intercommunication protocol among the equipment from differentmanufacturers at the optical network side. The GMPLS series protocols are the mainbody of its signaling protocol.

1-10



l E-NNI is a bidirectional signaling interface between two control plane entities indifferent control domains. E-NNI supports the functions of call control, resourcediscovery, connection control, connection selection and connection route selection.

l It defines the general interfaces between control planes, which are bidirectionalsignaling interfaces. Its main function is exchanging reachability information amongdifferent 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 ormore domains with dependent relationship. I-NNI supports the functions of resourcediscovery, connection control, connection selection and connection route selection.

l As a bidirectional signaling interface, it defines the interface between the units in acontrol 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-de-fined by vendors, so the standardization is not required. However, for smooth tran-sition to the final peer model, the standard signaling protocols such as GMPLS andPNNI should be complied with for the convenience of upgrading and interconnectionin future.

1.4.2 Control ProtocolsControl protocols are important components of the ASON control plane. They are alsoimportant means for the implementation of control plane functions. The fastest wayto realizing it is adopting the current data network protocols. Now ITU-T and otherinternational standardization organizations are going to use GMPLS protocols as thecontrol protocols for ASON. The GMPLS is extended from the MPLS. There are manychoices, 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 managebidirectional control channels between them. It includes the following core functions:

1-11



control channel management, link property correlation, link verification and link faultmanagement.

Control Channel Management

Control channel management serves to establish and maintain control channelconnectivity between adjacent nodes. It completes parameter negotiation and signalinginformation transfer.

At least one bidirectional control channel should be available between adjacent nodes.Multiple control channels are allowed as backups. The connectivity and interface identifiersof local and remote nodes on transport plane should be known, which can be obtainedthrough the management plane or by means of automatic discovery mechanism. Theremote 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 linkand to synchronize the link properties. This function greatly reduces the delivery ofLink State Advertisement (LSA) messages in networks.

l Link property correlation allows the bundling, modification and correlation of linksas well as the exchange of their traffic engineering parameters so as to ensure theconsistency 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 verifythe mapping of the local ID to remote ID. After link verification, a local-to-remote IDmapping table with definite link states can be obtained.

l The LMP link verification procedure is initiated by the Begin Verify message on thecontrol channel. It is implemented with the coordination between control channel anddata channels. Link verification procedure is optional depending on the configurationof verification flag during parameter negotiation.

Link Fault Management

Link fault management is initiated by a downstream node that detects data link fault. Itserves to exchange channel fault messages and response messages so as to detect linkstate hop by hop along Label Switched Path (LSP) towards the upstream until the faultylink is located. This procedure enables quick response to link faults and precise locationof faulty links.

1.4.2.2 Routing Protocols

At present, ITU-T has not specified routing protocols for ASON. The commonly usedintra-domain routing protocols include OSPF and IS-IS, while inter-domain routing

1-12



protocols include BGP, OSPF, PNNI and DDRP. Now OSPF-TE is most widely-used bydifferent vendors.

l OSPF is a dynamic routing protocol based on link state and SPF algorithm. OSPFlearns network topology (in the same area) by exchanging link state betweenneighbors and calculates the routes to all destinations in the area with SPF algorithm.

l The purpose of an OSPF router module is to collect the topology information of net-work, including topology information on control layer and traffic topology informationused for constrained route calculation, as well as the network protection information.It calculates routes according to the topology information on control layer to establishrouting tables on the control layer.

l After the collection of service plane topology in the whole area, OSPF callsConstrained Shortest Path First (CSPF) algorithm to search traffic path. The followingconstraints are involved when using CSPF algorithm: maximum link bandwidth,available link bandwidth, shared link risk group, nodes to be involved (or nodes to beavoided), Service Level Agreement (SLA) and optical distance etc.

l CSPF calculates not only end-to-end working paths but also corresponding protectionpaths. To ensure the protection takes effect, there should not be any crossed nodesor links expect for the two endpoints of a protection path and a working path. Aftera working path is calculated, an easy method to calculate a protection path is to cutthe nodes and links (excluding the source node and the destination node) covered bythe working path in the current network, and then find a path from the source to thedestination 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. Withthe control plane and the switching capability of signaling control, the management forconnection configuration is implemented. Therefore, the signaling protocol of controlplane is specially important for ASON. ITU-T G.7713 specifies three signaling protocolsfor 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 cannotcommunicate with GMPLS. The PNNI specified by ITU-T G.7713.1 is only applicableto soft permanent connections.

l RSVP

RSVP originates from IPCoS technology. Compared with PNNI, RSVP can betterimplement resource synchronization, error and fault processing such as powerfailure. Moreover, it makes multicast easier. RSVP can fully separate the controlplane and the data plane with better flexibility.

It is used between I-NNI and E-NNI, from local domains to exterior domains orall paths between service providers. It supports soft permanent connections andintra-domain switched connections.

1-13



l CR-LDP

CR-LDP originates from IP MPLS technology. It is difficult to realize multicast, andneeds great extension and improvement. CR-LDP is applicable to UNI, E-NNI andI-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 thefollowing additional features:

l Support different intra-domain and inter-domain protocols.l Support IPv4, IPv6 and Network Service Access Point (NSAP).l Support user-defined service specifications and service diversity with UNI and E-NNI

interfaces.l Support domains and hierarchical architecture, same for overlay and peer models.l Support call/connection separation.l Support soft permanent connection.l 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 commonlyused, as shown in Figure 1-6.

Figure 1-6 Mesh Networking

1-14



1.5.1.2 Hybrid Networking via UNI

ASON can be deployed with other traditional optical networks to form a hybrid network viaUNI interfaces, as shown in Figure 1-7. In the figure, AS1 and AS2 represent traditionalnetworks, 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. Ithas the following features:

l Existing network resources can be fully utilized.l UNI agents send connection requests from the network management system to

ASON, which completes the setup of connections. This networkingmode is applicablefor the relation between existing metro area network and newly-constructed ASONbackbone network.

l The current mode is traditional optical network unidirectional UNI-C, i.e. the traditionaloptical network is the client of ASON.

l UNI interfaces are used between ASON and traditional optical networks but notdirectly used for end users. Therefore, the hybrid network does not directly supportswitched connection services of clients.

l The functions of UNI interfaces are actually provided by data equipment but nottransmission 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 ahybrid network via UNI interfaces, as shown in Figure 1-8.

1-15



Figure 1-8 Hybrid Networking via NNI

This networking mode has the following features:

l The traditional optical network realizes the NNI function through an NNI agent. NNIinterfaces between ASON and traditional optical networks can provide more networkinformation, such as routing information and protection/restoration information.

l The hybrid network using NNI interfaces is more like an ASON with more functions.Each NNI agent can represent one or more node equipment.

l NNI acts for a node or a network. It can provide switched connection services.l Those existing optical networks that cannot be upgraded or reconstructed can be

directly interconnected to an ASON on the transport layer.l 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 isunable to realize unified management and scheduling in the whole network.

1.5.2 ProtectionProtection 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 theother is based on the control plane.

l Protection based on transport plane: The management plane implements theprotection configuration. The control plane is not involved in such protection.

l Protection based on control plane: The control plane implements the protectionconfiguration, including setting up one or multiple protection connections andproviding connection configuration information for the purpose of protection. The

1-16



protection based on control plane is carried out between the source node and sinknode of a protected link. Only the connection controllers of the source node and sinknode are involved in the protection regardless of those of intermediate nodes.

The control planes in optical-layer and electrical-layer switching equipment require that thesignaling, 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-endrestoration.

l Local segment protection refers to the link protection carried out between two adjacentswitches (all LSPs are labeled with "segment protection" and "link selection")

l Segment protection refers to LSP segment restoration between two nodes (such asSNC specified by ITU-T).

l End-to-end protection refers to the LSP protection between the input port and theoutput port.

Protection Types

l 1+1 protection:

Services are transported on both the working link and protection link. Those withbetter quality are received at the receiving end.

l 1:1 protection:

Services are only transported on the working link. The protection link does not carryservices or only carries services with lower priority. When the working link fails, theservices carried by it are switched to the protection link; while the services with lowerpriority carried by the protection link are discarded.

l M:N protection (MN):

N working links share M protection links. M and N can be preset. The protection linkscan carry extra services. No one-to-one relationship is set between working links andprotection links. When a working link fails, its services are switched to an availableprotection link. If more than M working links fail at the same time, only M working linkswith higher priority are protected.

l The optical channel shared protection ring and the optical MS shared protection ringneed to use APS protocol.

1.5.3 RestorationRestoration is a procedure to reroute for a new connection to replace a failed connectionwith idle capacity in network. Restoration is generally completed in hundreds ofmilliseconds to several seconds.

Classification by Control Methods

Restoration can be controlled in a centralized way or a distributed way.

1-17



l Centralized control: Restoration is completed under the control of a network controlcenter.

l Distributed control: Restoration is completed by distributed intelligent NEs in anetwork.

l 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 thefault occurs. Under this mechanism, one or multiple paths are calculated beforethe fault occurs. If resources are not preset or chosen before the fault occurs, theavailability 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 explicitroutes used for restoration are calculated dynamically, and one of them is chosenafter the fault occurs. This is called LSP rerouting mechanism. If resourcesare not preset or chosen before the fault occurs, the availability of restorationconnection is not guaranteed.

l Pre-planned LSP restoration

LSP restoration can complete the signaling exchange on demand or completeit in advance. If the signaling exchange is completed on demand, the controlplane needs to deliver the restoration-related signals to each relevant node. Ifthe signaling exchange is completed in advance, pre-planned LSP restorationwill start directly.

Pre-planned LSP restoration (or pre-planned LSP rerouting) is carried out aftersignaling exchange is completed. The restoration resources on the restorationpath are pre-planned.

Implementation Methods of Restoration

The implementation methods of restoration include pre-planned rerouting and dynamicrerouting.

l Pre-planned rerouting calculates restoration routes for working connections before afault occurs. When a working connection fails, the pre-planned connection is activatedto replace the failed one.

l Dynamic rerouting calculates restoration route for working connection in real timewhen a fault occurs, selects standby resources, and sets up new connections toreplace the failed one.

l The dynamic rerouting is mostly used for restoration in ASON.

1-18



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 theoptical network. The ASON services include:

l SDH service: SDH connections with granularity of VC-n and VC-n-Xv as specified inITU-T G.707

l OTN service: OTN connections with granularity of ODUk and ODUk-n-Xv as specifiedin ITU-T G.709

l Transparent or non-transparent optical wavelength servicesl Ethernet services of 10 Mbit/s, 100 Mbit/s, 1 Gbit/s and 10 Gbit/sl 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 functionssuch as bandwidth on demand, diversity of circuit assignment, and connection bundling,etc. The separation of call and connection control reduces call control messages ofintermediate control nodes and thus lessen the workload of decoding and messageexplanation. ASON supports the following topology types of service connections.

l Bidirectional point-to-point connectionl Unidirectional point-to-point connectionl 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 connectionmode.

1.6.1.3 Service Connection Types

ASON supports three types of connections: Permanent Connection (PC), SwitchedConnection (SC) and Soft Permanent Connection (SPC). Refer to the section of "ThreeConnection Types" for details.

1.6.1.4 Service Levels

ASON supports the convenient division of services based on the priority to providetransmission traffic complying with Service Level Agreement (SLA). Clients have differentrequirements for connection availability. These requirements can be expressed in termsof the "service level". In ASON, service level describes restoration/protection options and

1-19



priority related connection characteristics, such as setup priority, holding priority (pre-idledor not), or restoration priority.

l Setup priority: It refers to connection setup time, which may be on day, hour or minutelevel.

l Holding priority (pre-idled or not): It determines whether a connection link withoutprotection can be pre-idled to carry more important service when some fault occursin system.

l Restoration priority: It refers to restoration time in case of system failure andrestoration level such as percentage of restored services.

The control plane supports the priority setting of each connection, bandwidth reservationwith the purpose of restoration, as well as route unification after failure recovery. Generally,ASON supports the following connection levels.

l Private connection (1+1 and 1:1)l Shared protection (1:N, M:N and OCh-SPRING)l Non-protection (transport on active link)l 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 establishedbetween clients and carrier networks on the transport plane. The following accessmethods are optional, according to the locations of carrier networks and clients.

l Intra-office access (when NEs in optical networks and client NEs are located at thesame place)

l Direct remote access (for client devices with private link connections)l Remote access via access subnetl Dual homing access

ASON must support the dual homing access. Multiple addresses are not needed when aclient adopts the dual homing access. Dual homing access is a special case of the accessnetwork. A client device may be dual homed to a carrier network through two differentpaths. The purpose of dual homing is to enhance the network survivability. When one ofthe access path fails, the client traffic will not be interrupted due to the existence of theother access path.

From a security perspective, network resources should be protected from unauthorizedaccesses and should not be used by unauthorized entities. Service access control is themechanism that limits and controls entities trying to access network resources, especiallyvia UNI and E-NNI. The Connection Admission Control (CAC) function should support thefollowing security features:

l CAC is applicable to all entities accessed to network resources via UNI or E-NNI. Anauthentication function of an entity should be included in order to prevent masquerade(spoofing). Masquerade is fraudulent use of network resources by pretending to bea different entity. An authenticated entity should be given a service access level in aconfigurable policy basis.

1-20



l A corresponding mechanism should be set up at UNI and NNI to ensure the integrityof client authentication and link information, such as link setup, release and signalinginformation, 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 avoidany fabrication of connection management information.

l Each entity should be authorized to use network resources according to themanagement 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 areassigned in real time or approximately real time by service Management Interfaces (MI) ofPC or SPC. They share the following features:

l A connection should be requested via service management interface.l There is a relationship of client/server between a client device and optical network.l 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, whichcan provide services quickly. Clients just need to tell the carrier where and what kind ofservice is needed. The carrier can set up satisfactory service connections almost in realtime through the management plane and control plane. In addition, the carrier can changethe service attributes fast in condition that lines between clients and carrier network canmeet the requirements.

1.6.2.2 BOD Service

BOD services are automatic connection services whose bandwidth is allocated on demandvia UNI signaling interfaces. Such connections, being switched connections, are set up inreal time. They share the following features:

l A client device or its agent can initiate a connection request directly via UNI.l Optical network can be invisible or visible in a limited degree for clients according to

actual interconnection modes or network management policies.l 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 thecorresponding service connection as required. A client device must have the capability ofservice discovery to get service information in the transport network via its UNI-N. Duringsetting 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 viaUNI: direct request and indirect request. For direct request mode, UNI-C functions are

1-21



implemented in a client device, which can directly request for services in a transportnetwork. For indirect request mode, UNI-C is independent of a client device. It performsUNI 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 hasthe following features:

l Clients sign to use certain network resources, such as optical connection ports,wavelengths, etc.

l OVPN supports Closed User Group (CUG).l Optical connections for OVPN can be PC, SPC or SC, depending on different

assignment modes.l Any site in an OVPN can request to dynamically configure connections with other sites

in the same CUG.l 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. Anoptical transport network can be divided into multiple VPN. The network resources of eachpart can only belong to one VPN. Authorized clients of an VPN can manage correspondingresources of the network.

1-22



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 leadto protection and restoration. ASON supports the protection and restoration initiated bythe management plane for the convenience of maintenance, which forces traffic to beswitched to a protection circuit. The ASON management plane provides the followingservice management functions:

l End-to-end service assignmentl Service setup and releasel Service protection/restoration policyl Service attribute and service level agreementl OVPN management

ASON service management systems, supporting traditional service managementfunctions, are compatible with previous service management systems. The managementplane can customize service level protocols for different clients, providing them withproper service policies to guarantee the service quality. The SLA-related services mustbe flexible, easy and extensible.

1.6.3.2 OVPN Implementation and Management

OVPN has been applied on traditional transport network platform. A powerful managementplane is a prerequisite for the implementation of OVPN, which is established on the networkservice layer management system. The management plane can identify multiple OVPNsand set management areas. On the client service terminal, it can monitor alarm in themanagement area, delete or set up a channel and query performance data. OVPN has afirewall and other security measures to ensure the network security.

VPN is commonly applied on IP network. Its experience can be used on the distributedASON platform to develop and manage the OVPN service. Various OVPNs can bedivided based on internal addresses, assigned addresses, client addresses, servicetypes or areas. NEs in the same OVPN are visible to each other. It can provide the basicfunctions of ASON such as protection/restoration, end-to-end service setup, etc. It canalso prevent illegal users from accessing to ensure the privacy of virtual network throughcertain security measures.

1-23



This page intentionally left blank.

1-24


Chapter 2ZXUCP A200 (WASON)Function and SolutionTable of Contents

WASON Concepts and Solved Problems ...................................................................2-1ZXUCP A200 Functions .............................................................................................2-2ZXUCP A200 Solution................................................................................................2-5

2.1 WASON Concepts and Solved Problems

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

2.1.2 Problems Solved by WASONZXUCP A200 is a WASON control plane oriented for WDM/OTN devices, which is appliedin the mesh network with complex topology. The problems that can be solved by ZXUCPA200 are as follows.

l The traditional WDM network does not have a strong capability in the schedulingof service wavelength and bandwidth. Most services can only support fixedconnection mode (PC), and the automatic optimized routing (SC and SPC) cannotbe implemented based on the use situation of network resources. Therefore, thebandwidth request from clients cannot be responded quickly.

l Generally, the traditional WDM network does not support the automatic discovery ofnetwork links/wavelength resource status. Therefore, the status of network resourcescannot be updated automatically in real time. It can only be updated manually via thenetwork management system.

l The survivability of traditional WDM network is solved through the ring networkingmode and the chain networking mode. In such modes, lots of bandwidths need tobe reserved for protection, and the capability of resisting multi-point faults is notstrong. The mesh networking cannot be provided with a good protection mode, and

2-1



the protection by level is not supported for different service layers such as WDMlayer/SDH layer and WDM layer/IP layer.

l In traditional WDM network, although interconnection and intercommunicationare supported at service interfaces for different vendors, the interconnection andintercommunication cannot be realized for overall control of network.

l The traditional WDM network does not support the network bandwidth request whichdirectly comes from end users, and cannot satisfy the demands for many new servicetypes such as Closed User Group (CUG), Optical Virtual Private Network (OVPN),Bandwidth on Demand (BOD) and Provision Bandwidth Service (PBS).

l Unlike SDH network application, to set up service connection in the networking withWDM 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 protocolbased on the network topology information is largely depended on whether therequirements of physical optic characteristics can be met for WDM network.

2.2 ZXUCP A200 FunctionsTable 2-1 lists the product functions.

Table 2-1 ZXUCP A200 Product Functions

Function Description Remark

System management

l System startup/reset, time

synchronization, IP address

setting, online upgrade and

active/standby status

management

l Queries the enabling/dis-

abling status.

l Uploads and downloads

the important data.

Applied scenarios: protection

scenario and protection, control

plane scenario

Applied modes: manually

resetting the management plane

and automatically resetting the

control plane

Automatic discovery

l Sets and queries the

neighbor and link auto

discovery.

l Creates and deletes

an controlled neighbor

automatically.

l Automatically enables layer

adjacency discovery and

enables and disables the

transmission capability

discovery.

-

2-2


Chapter 2 ZXUCP A200 (WASON) Function and Solution


Transport resource

management

l Configures board

resources and fiber

connections in nodes

totally and partially.

l Queries, modifies, reports

and refreshes information

of link interfaces.

-

Control plane resource

management

l Configures I-NNI nodes

for the first time and adds,

queries and modifies

parameters of the I-NNI

node.

l Queries the I-NNI control

links in the whole network.

l 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.

-

Basic SPC service configuration

management

l Creates/modifies and

deletes OCH service,

ODUk switching service

and ODUk mapping

service.

l Modifies the grades of OCH

service, ODUk switching

service and ODUk mapping

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




Basic SPC service running and

maintenance

l Retries OCH service,

ODUk switching service

and ODUk mapping

service connection

;troubleshooting and

inspecting and clearing

residual connection

l Specifies original

connection, reroute

blocking, optimizing reroute

and support and supporting

external commands of SPC

service protection

-

SPC service extension

l Pre-calculates routes

before creating services

l Restoring routes by

manually pre-setting and

using the routes

-

SPC service route calculation

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

l Supports strict explicit

route/including, excluding

specific network

resources and protection

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

l Supports single layer

(optical layer, electrical

layer) and multiple layer

scenario; supporting

electrical layer link binding

-

2-4


Chapter 2 ZXUCP A200 (WASON) Function and Solution


l Supports the copper

service, gold service and

diamond service

l Supports manual

pre-setting mode and

auto presetting mode

Transport plane protection

l Supports optical link 1+1

protection, 1+1 OCH

protection, optical channel

shared protection ring and

1+1 protection networking

at client side

l Supports low order ODUk

SNC1+1 protection, low

order ODUk shared ring

network, low order Pcycle

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

-

Alarm, time and performance

management

l Supports to query alarms,

report alarms, set and

query alarms screen

l Supports to query control

system events, report the

events on control plane

-

2.3 ZXUCP A200 SolutionThe ZXUCP A200 product of ZTE Corporation provides an integrated WASON solution.

l Control plane software: ZXUCP A200l Transport plane devices

At the access and convergence network layers: compact ZXMPM720 series withhigh integration and low power consumption.

2-5



In the metro core network: ZXMP M820, ZXONE 8300 with high capacity andelectrical/optical cross-connect capability for multiple services.

In the backbone network: intelligent ZXWM M920 and ZXONE 8500 series thatsupport high capacity (3.2 TB) and ultra long haul (ultra long span).

l Network management software: NetNumen U31 and the WASON control planetogether 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


Chapter 3ZXUCP A200 DebuggingTable of Contents

Initialization Configuration Flow ..................................................................................3-1Initialization Configuration ..........................................................................................3-2

3.1 Initialization Configuration FlowAn NE needs to be initialized before providing WASON functions. The initializationprocedure, which also includes loading the application and logical programs, isimplemented before the debugging of the ZXUCP A200 product. Figure 3-1 shows theinitialization flow.

3-1



Figure 3-1 WASON Initialization Configuration Flow Chart

3.2 Initialization Configuration

3.2.1 Preparation for HardwareThe ZXUCP A200 hardware module consists of an AGENTmodule and aWASONmoduleon an SNP board. The AGENT module and WASON module use different SD cards andECM-A subcards.

3-2


Chapter 3 ZXUCP A200 Debugging

3.2.2 Updating and Downloading Boot/Fpga ProgramBoot and Fpga are integrated in one bin file. Firstly, check if the Boot/Fpga program isavailable in the BootROM. If not, a programmer is needed; if yes, update the programonline 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 theBootROM.

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 of the module effective (merge the VLANs first before using theforced IP ). If the WASON module can be pinged successfully with other IPs, theswitching 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 ProgramThe download and update of WASON application program is almost the same as the Telnetmode of Boot/Fpga except for changing prg boot to prg at step 9. Refer to the section of

3-3



"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 beendownloaded and updated.

Downloading App is different from updating Boot/Fpga in the following items:

l App can be downloaded through EMS.l The Telnet IP address for downloading App is different from that for updating

Boot/Fpga.

3.2.4 Formatting SD CardGenerally, an SD card needs to be formatted if it is used for the first time. Follow theprocedure 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 informationof the WASON module. Be cautious of the difference of the serial port connectorsbetween 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. Ifmount sd failed appears, it indicates that the

mounting of SD card is not successful. In this case, the SD card needs to be formattedprovided that the card is not damaged. If mount sd successful appears, it indicates thatthe 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 ofWASON systemis not under /sd.

5. After umount sd successful appears, type formatsd, and then press Enter.6. Type reset, and then press Enter. Now the SD card can be used after restart.

3-4


Chapter 4ZXUCP A200 ConfigurationManagementTable of Contents

Overview....................................................................................................................4-1Enabling the Control Plane ........................................................................................4-4Node Management.....................................................................................................4-6Configuring the Automatic Discovery ..........................................................................4-8Configuring I-NNI Interface.......................................................................................4-11Configuring TE Links ................................................................................................4-19Control Plane Running Topology ..............................................................................4-22Call Management .....................................................................................................4-24Synchronizing SPC Services ....................................................................................4-60SPC Service Maintenance........................................................................................4-61Enabling the Autodiscovery (non-WASON)...............................................................4-64Bundled Links............

eona

Documents

fundamentals of ason

background of ason

definition of ason

advantages of ason

ason functions

ason architecture

zte corporationno

revision historyrevision