NetNumen T31 (V1 (1) .10R2) Network Element Management System Operation Manual (ASON NE Volume)

NetNumen T31
Network Element Management System

Operation Manual (ASON NE Volume)
Version 1.10R2
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 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 CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. 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 Data Revision Reason

R1.0 20091230 NetNumen T31(V1.10R2) first version issued
Serial Number: sjzl20099547

Table of Contents
Preface.............................................................. I
Configuring and Managing ASON Functions........1
Overview....................................................................... 1
Configuring ASON Node Property ...................................... 3
Configuring J0 Overhead ................................................. 5
Configuring DCC/ECC ...................................................... 6
Configuring Transfer Ports................................................ 8
Example of Configuring Transfer Ports ..........................11
Configuring Control Interfaces .........................................13
Configuring TE Link Property ...........................................16
Querying ControlPlane Run Topo ......................................18
Querying ControlPlane Timeslot Cross ..............................20
Resetting ASON Node.....................................................21
ASON Configuration Example ..........................................22
Networking Description ..............................................22
Configuration Flowchart..............................................22
Configuration Steps ...................................................23
Configuring Four-Fiber Link 1+1 MS
Protection .............................................23
Configuring Two-Fiber Bidirectional MS Shared
Protection Ring ......................................25
Configuring Necessary Overheads of Transfer
Ports ....................................................28
Configuring Transfer Ports ..................................29
Configuring and Managing ASON Services........ 33
Querying Calls...............................................................33
Creating Calls ...............................................................36
Setting Basic Properties..............................................37
Configuring A/Z End...................................................39
Setting Other Properties .............................................41
Configuring ASON Tunnel Services ...................................53
Confidential and Proprietary Information of ZTE CORPORATION I

NetNumen T31 Operation Manual (ASON NE Volume)
Configuring Control Plane 1:N Protection Groups................55

Configuring Associated Services ......................................59
Modifying Calls ..............................................................60
Setting Service Startup/Stop...........................................61
Setting Manual Reversion of Calls ....................................62
Activating/Deactivating Call Restoration............................63
Modifying Initial Connection ............................................64
Optimizing Calls ............................................................65
List of Figure ................................................... 71
List of Table .................................................... 73
II Confidential and Proprietary Information of ZTE CORPORATION

Preface
Purpose of This This manual is applicable to NetNumen T31 (V1.10R2) Network

Manual Element Management System (T31 in short hereinafter).
T31 is an NE-level Element Management System (EMS) applied to
the transport network. It has all of the NE-level functions and part
of the network-level functions.
The manual suite of T31 is as follows.
Manual Name Function
NetNumen T31 (V1.10R2) Describes the installation

Network Element Management procedure of T31.
System Installation Manual
NetNumen T31 (V1.10R2) Describes T31 basic knowledge,

Network Element Management common operations,
System Operation Manual equipment configuration,
service configuration, alarm
management, performance
management, routine
maintenance, troubleshooting,
etc., including the basic operation
volume and different volumes for
different types of NEs.
What is in This This manual is NetNumen T31 (V1.10R2) Network Element Man-
Manual agement System Operation Manual (ASON Volume), which is ori-
ented towards the EMS operations of ASON NEs. The manual con-
tents are introduced as below.
Chapter Content
Chapter 1 Configuring and Describes the configuration

Managing ASON Functions steps of ASON functions, which
includes configuring node
property, configuring J0 overhead,
configuring DCC/ECC, configuring
control interface, and configuring
TE link.
Chapter 2 Configuring and Describes the steps of configuring

Managing ASON Services ASON intelligent services.
Intended Readers This manual applies to the following engineers:

� Network supervision engineers
� Data configuration engineers
� EMS administrators
� Maintenance engineers
Conventions 1. Mouse Operation Conventions
Confidential and Proprietary Information of ZTE CORPORATION 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. Signs
This manual uses three prominent signs to indicate special
notes in operations.
� Caution: Reminds users to be cautious in an opera-

tion.
� Note: Provides additional information about a certain

topic.
� Tip: Indicates a suggestion or hint to make things

easier or more productive for the reader.
3. Manual Usage Convention
This manual takes the EMS client running on the Windows plat-
form as an example for illustration.
Revision History
Product Version Document Version Description
V1.10R2 20091115-R1.0 Applicable to

NetNumen T31
(V1.10R2) Network
Element Management
System
II Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Configuring and
Managing ASON
Functions
Table of Contents
Overview........................................................................... 1
Configuring ASON Node Property .......................................... 3
Configuring J0 Overhead ..................................................... 5
Configuring DCC/ECC .......................................................... 6
Configuring Transfer Ports.................................................... 8
Configuring Control Interfaces .............................................13
Configuring TE Link Property ...............................................16
Querying ControlPlane Run Topo ..........................................18
Querying ControlPlane Timeslot Cross ..................................20
Resetting ASON Node.........................................................21
ASON Configuration Example ..............................................22
Overview
In the NetNumen T31 operation window, double-click the ASON
View icon to enter the ASON View. In ASON View, the TE link
topology of ASON can be queried, as shown in Figure 1.
Confidential and Proprietary Information of ZTE CORPORATION 1

FIGURE 1 TE LINK TOPOLOGY OF ASON
Caution:
All configuration items described in this chapter are only applicable
to Online ASON NEs whose ASON functions have been enabled.
For detailed procedure of enabling ASON functions, refer to Uni-
trans ZXUCP A100 Unified Control Plane User Manual.
In the NetNumen T31 operation window, double-click the Topol-

ogy Management icon to enter the Topology Management
view. In the Topology Management view, select an ASON NE,
then click the menu item Device > ASON, and the submenu as
shown in Figure 2 pops up.
FIGURE 2 ASON MANAGEMENT MENU
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Configuring and Managing ASON Functions
Caution:
All the submenu items under Device > ASON can be displayed
only when users are operating an Online NE.
The meanings of the submenus shown in Figure 2 are as follows:

� Call Management: Views all the call information of the NE,
and performs such operations as call modification, reply, en-
abling, etc.
� SNC Management: Views the basic configuration, state in-
formation of the Sub-Network Connection (SNC).
� ASON Node: Configures the restoration time and time-out
time of deleting services for the SNC node.
� INNI Management: Configures the in-band IP Control Chan-
nel (IPCC), transfer port, out-of-band control interface and
out-of-band neighbor.
� TE Link: Views the TE link information, and sets TE link pa-
rameters such as weight, SRLG, etc.
� Resource Reservation: Views the consistency between the
resource reservation information and the transfer port infor-
mation of an ASON NE.
� ControlPlane Run Topo: Views the control link topology in-
formation of the whole ASON.
� Reset Ason Node: Resets an ASON node.
� ControlPlane Timeslot Cross: Views the timeslot cross-con-
nection information of the control plane.
Configuring ASON Node

Property
Prerequisites � The EMS user has the rights of "Operator Role" or above.
� The EMS can properly manage the equipment to be configured.
� The NE is not configured with intelligent services.
Context Use this procedure to configure or modify the parameters of an
ASON node, including the node ID, recovery time, time-out time
of deleting a service.
Caution:
When modifying the node parameter, if a node has been configured
with intelligent services, the service, connection, transfer port and
control interface of the intelligent NE should all be deleted.

Steps 1. In the T31 Topology Management view, select an ASON NE.

2. Select the menu item Device > ASON > ASON Node to pop
up the ASON Node dialog box, as shown in Figure 3.
FIGURE 3 ASON NODE DIALOG BOX
3. Double-click a property value to modify it. The property values

and recommended configurations are listed in the table below.
Caution:
The ASON Node (node ID) of an ASON NE is set according to
the node ID planning scheme. Once it is set successfully, do
not change it arbitrarily.
Property Description
Has the same format as the IP address

and is used to identify an ASON node.
Node ID
Configuring it as the IP address plus 1 is
recommended.
The recovery time of graceful restart (in

seconds, in the range of 60 to 1800, 200
by default). The recovery time should be
configured based on the traffic. When the
Recover Time traffic is large, the recovery time should
be set to a larger value. The reference
calculation way is T = 3 * number of
connections (T is the restoration time, and
60≤T≤1800.)
The waiting time from graceful deletion

to forced deletion (in seconds, in the
Time Out(s)
range of 10 to 180, 60 by default.) 60 is
recommended.
Tip:
For the meanings of graceful restart, graceful deletion and
forced deletion, refer to the "Technical Terms" section.
4. After configuration, click the Apply button.

5. Restart the NCP board.
Press the reset button on the NCP board to restart the NCP
board.
END OF STEPS

Result After setting the ASON node property, repeat steps 1 and 2 to
query the ASON node property. The displayed property value
should be the configured value.
Configuring J0 Overhead
� The physical fibers between the ports of the optical line board
to be configured have be properly connected.
Context Use this procedure to configure the J0 overhead for the port of the
optical line board to realize automatic discovery.
Steps 1. In the NetNumen T31 Topology Management view, select an
ASON NE.
2. Select the menu item Common Config > Overhead Manage-
ment > Overhead Config to pop up the Overhead Config
dialog box, as shown in Figure 4.
FIGURE 4 OVERHEAD CONFIGURATION
3. Click the Add button to add an overhead configuration item.

4. Refer to the following table to configure the property values.
Configuration Select the optical line board to be

Board configured.
Select the optical line board to be

configured. The options of the source
Source Board
board vary with the options of the
configuration board.
Select the physical port of the optical line

PTP
board to be configured.
Set the location of the overhead insertion.

Insert Num- The options vary with the model of the
ber/AUG Number configuration board. Select the default
value 1.
Section or Channel Set the section or channel type that the J0

Type overhead belongs to. Select RS.
After selecting the section or channel type,

CTP the options of CTP vary. Select the default
value.

Row No. and Select the configured overhead. Select

Column No. R1C7(J0).
It indicates the automatic discovery value

expected to receive. The minimum length
Expect Value
is 0 and the maximum length is 54. It is
blank by default.
Configure the send value of the J0

overhead, which must be unique in
the network. It is used to differentiate
the physical ports in the network. The
Send Value maximum length is 15 bytes.
The default value is: node no.-shelf
no.+slot no.+port no., such as 8-010706.
It is recommended to keep the default
value.
It is used to obtain the peer port connected

with the local port.
Click to obtain it. If the automatic
discovery is successful, the send value
Receive Value of the peer end which is automatically
discovered will be returned; If the
automatic discovery fails (or the fiber
connection breaks), an error value will be
returned.
Note:
To obtain the Receive Value successfully at the local port, the
overhead configuration of the peer port connected with the port
must be completed already.

END OF STEPS
Result After configuring the J0 overheads of the ports on the optical line
boards at both ends, click the corresponding Receive Value but-
ton of the port, the receive value should be able to be
obtained properly.
Configuring DCC/ECC
Context Use this procedure to set the Data Communications Channel (DCC)
/ Embedded Control Channel (ECC) usage mode of the port on
optical line board.


ASON NE.
2. Select the menu item Operation > Topology Operation >
Device Manager, and the Device Manager dialog box pops
up.
3. Click the icon before the NE to expand the board list of the
NE.
4. Click the optical line board to be configured, and the Board
Operation tree menu will be displayed on the bottom left.
5. In the Board Operation menu, select the menu item Com-
munication Maintenance > DCC/ECC Usage Mode Config
to enter the DCC/ECC Usage Mode Config dialog box.
6. Configure the DCC/ECC usage mode of the current board and

port according to the table below.
Attribute Description
It identifies the port of the optical line board. It

Port
is no need to be configured.
Configure the DCC/ECC usage mode at the

DCC receiving receiving direction. The options include
direction DCCr, DCCm, DCCr+DCCm and Do not use DCC.
DCCr+DCCm usage mode is recommended.
Configure the DCC/ECC usage mode at the

DCC sending sending direction. DCCm, DCCr+DCCm and
direction Do not use DCC. DCCr+DCCm usage mode is
recommended.
END OF STEPS
Result Repeat steps 1~5 to query the DCC/ECC mode of the port on the
optical line board. The mode should be the configured mode.

Configuring Transfer Ports

� The fibers between the ports of the NEs to be configured have
been properly connected.
� If the transfer port configuration enables auto discovery, the J0
overhead of the corresponding port should be configured first
before configuring the transfer port.
� If an MSP exists in the network, the MSP must be configured
first before configuring the transfer port.
Context Use this procedure to configure the transfer port. The TE link is
automatically discovered by ASON.
ASON NE.
2. Select the menu item Device > ASON > INNI Management
to pop up the INNI Management dialog box.
FIGURE 5 INNI MANAGEMENT DIALOG BOX
3. Click the Add button to add a transfer port configuration item.

4. Refer to the following table to set the property values.
Caution:
Input the resource partition of transfer port based on the actual
situation:
After the two-fiber MS protection is configured, half of the fiber
resource is used for protection. For example, input 8 in the
resource partition for the STM-16 optical port.
If the whole fiber resource is used for protection (in the cases
of 1+1 protection and four-fiber MS protection ring), then the
ASON transfer port cannot be configured at the two corre-
sponding ports of the fiber.
PTP Select the optical port to be configured.
The logical port ID of the local TE link. It is

Local TE Link ID automatically generated after configuration
and no need to input.
The logical port ID of the local transfer

TC ID port. It is automatically generated after
configuration and no need to input.

Select this option to enable automatic

discovery, or deselect it to disable
Autodiscovery automatic discovery. It is selected by
default, that is, automatic discovery is
enabled.
The node ID of the opposite end. No need

to input when auto discovery is enabled.
Remote Node ID
Input the node ID of the opposite end when
auto discovery is not enabled.
The logical port ID of the transfer port at

the opposite end. No need to input when
Remote auto discovery is enabled. Input the port
TransferPort ID ID of the opposite end when auto discovery
is not enabled. Refer to the detailed
description as below for the input method.
The logical port ID of the remote TE

Remote TE Link ID link. It is automatically generated after
configuration and no need to input.
The resource allocated to the transfer port.

Resource Partition
The unit is the number of AU-4.
Note:
The transfer port ID is generated in hexadecimal, and it is
eventually converted into decimal.
i. The first three digits are 0x084;
ii. The 4th and 5th digits are the corresponding slot number of
the port times 4, and then it is converted into hexadecimal;
iii. The 6th and 7th digits are 0x10;
iv. The 8th digit is the port number;
v. Convert the 8–digit hexadecimal transfer port ID into dec-
imal, and then input it in the dialog box.
For example, the transfer port ID is "number 2 optical port of
the optical line board at slot 10": the 4th and 5th digits are
10×4=40, which is 0x28 in hexadecimal. The 8th digit is 0x2.
The corresponding transfer port ID is 0x08428102, which is
138576130 in decimal.
Table 1 lists the simple correspondences of the transfer port

ID. The common configurations can be checked in the table.
TABLE 1 CORRESPONDENCE TABLE OF TRANSFER PORTS
Slot.P- Applicable
Hexadecimal Decimal
ort Device
1.1 08404101 138428673 S385/5800
2.1 08408101 138445057 S385/5800

Slot.P- Applicable
Hexadecimal Decimal
ort Device
3.1 0840c101 138461441 S385/5800
4.1 08410101 138477825 S385/5800
5.1 08414101 138494209 S385/5800
6.1 08418101 138510593 S385/5800
7.1 0841c101 138526977 S385/5800
8.1 08420101 138543361 5800
10.1 08428101 138576129 S385
11.1 0842c101 138592513 S385/5800
12.1 08430101 138608897 S385/5800
13.1 08434101 138625281 S385/5800
14.1 08438101 138641665 S385/5800
15.1 0843c101 138658049 S385/5800
16.1 08440101 138674433 S385/5800
17.1 08444101 138690817 5800
18.1 08448101 138707201 5800
19.1 0844c101 138723585 5800
21.1 08454101 138756353 5800
22.1 08458101 138772737 5800
23.1 0845c101 138789121 5800
24.1 08460101 138805505 5800
32.1 08480101 138936577 5800
33.1 08484101 138952961 5800
34.1 08488101 138969345 5800
39.1 0849c101 139051265 5800
40.1 084a0101 139067649 5800
41.1 084a4101 139084033 5800
42.1 084a8101 139100417 5800
43.1 084ac101 139116801 5800
44.1 084b0101 139133185 5800
45.1 084b4101 139149569 5800

Slot.P- Applicable
Hexadecimal Decimal
ort Device
46.1 084b8101 139165953 5800
47.1 084bc101 139182337 5800
48.1 084c0101 139198721 5800
49.1 084c4101 139215105 5800
50.1 084c8101 139231489 5800
51.1 084cc101 139247873 5800
52.1 084d0101 139264257 5800
53.1 084d4101 139280641 5800
54.1 084d8101 139297025 5800

END OF STEPS
Result After configuring the transfer ports between nodes, the ASON can
automatically discover TE links. Refer to the "Example of Config-
uring Transfer Ports" section for details.
Example of Configuring Transfer

Ports
Prerequisites � Two ASON NEs have been configured: NE20 and NE125.
� The 1# optical port of slot 6 under NE20 and the 1# optical
port of slot 6 under NE125 have been connected with physical
fibers.
� Enter the Topology Management view to query the transfer
port configured on NE125. The transfer port adjacent to NE20
has not been configured.
� Enter Ason view to view the network topology. No fiber con-
nection is available between NE125 and NE 20, as shown in
Figure 6.

FIGURE 6 NO OPTICAL CONNECTION BETWEEN NE125 AND NE20
Tip:
In Figure 6, the number in the parentheses indicates the EMS
ID, which is automatically added when creating an NE. Users
do not need to pay special attention to it.
Context Use this procedure to configure the specified ports of the two ASON
nodes respectively, so that the ASON can automatically discover
the TE links between the specified ports.
Steps 1. As shown in Figure 7, configure the 1# optical port of slot 6
under NE20. Configure the local transfer port, and use auto
discovery mode for the remote transfer port. For detailed con-
figuration steps, refer to the "Configuring Transfer Ports" sec-
tion.
FIGURE 7 CONFIGURING REMOTE NE125 OF NE20 WITH AUTO DISCOVERY MODE
2. As shown in Figure 8, configure the 1# optical port of slot 6

under NE125. Configure the local transfer port, and use auto
discovery mode for the remote transfer port. For detailed con-
figuration steps, refer to the "Configuring Transfer Ports" sec-
tion.
FIGURE 8 CONFIGURING REMOTE NE20 OF NE125 WITH AUTO DISCOVERY MODE
END OF STEPS
Result � After configuring the transfer ports at both ends, enter the
Topology Management view to view the TE link. Two TE
links have seen automatically discovered between NE125 and
NE20, as shown in Figure 9.

FIGURE 9 QUERYING TE LINK OF NE125
� Enter Ason view to view the network topology. Optical con-

nection is available between NE125 and NE20, as shown in
Figure 10.
FIGURE 10 QUERYING NETWORK TOPOLOGY
Configuring Control
Interfaces
� The fibers between the ports of the NEs to be configured have
Context Use this procedure to configure the control interface between NEs,
in order to provide the control channel for ASON to transfer the
control information.
Note:
� Generally, ASON uses in-band control channel to transfer con-
trol information. Only the iNNI Ctrl needs to be configured at
this time.
� When the out-of-band control channel is used to transfer con-
trol information, NNI Ctrl and Out Band Neighbor need to be
configured. At this time, the supporting DCN or SDH network
should be available to provide the out-of-band control channel.

ASON NE.
3. Configure iNNI Ctrl.
i. Select the iNNI Ctrl tab to enter the in-band control inter-
face configuration page, as shown in Figure 11.

FIGURE 11 IN-BAND CONTROL INTERFACE CONFIGURATION
ii. Click the Add button to add an in-band control interface

configuration item.
iii. Refer to the following table to configure the property val-
ues.
Select the optical port of the control

PTP
interface.
The name state of the control interface

address.
Name State Make selection based on the NE model:
– S385: Select named
– 5800: Select unnamed
The local IP address of the control interface.

Local IP It is generated automatically and no need
to input.
The subnet mask of the local IP address.

Local Address It is generated automatically and no need
to input.
The logical ID of the control interface. It

CC ID is generated automatically and no need to
input.
The corresponding IP address of the far-end

Z Node NE node. It is generated automatically and
no need to input.
The corresponding far-end optical port

Z Index of the control interface. It is generated
automatically and no need to input.
Whether the LMP protocol is enabled on the

LMP control interface or not. The default setting
is "In Use".
Whether the OSPF HELLO message function

OSPF is enabled on the control interface or not.
The default setting is "In Use".
The current status of the control channel.

No need to input. The status of the control
IPCC Status
channel will be displayed in this field after
successful configuration.
iv. After configuration, click the Apply button.

4. Configure NNI Ctrl.

i. Select the NNI Ctrl tab to enter the out-of-band control

interface configuration page, as shown in Figure 12.
FIGURE 12 OUT-OF-BAND CONTROL INTERFACE CONFIGURATION
ii. Click the Add button to add an out-of-band control inter-

face configuration item.
ues.
The Ethernet interface of the out-of-band

Port
control interface. The default setting is 1.
The IP address of the out-of-band control

IP Address
interface. Input the NE address.
The IP address mask of the out-of-band

Mask control interface. Input the NE address
mask.
Whether the OSPF HELLO message function

OSPF Protocol is enabled on the control interface or not.
The default setting is "In Use".

5. Configure NNI IPCC.
i. Select the NNI IPCC tab to enter the out-of-band neighbor
configuration page, as shown in Figure 13.
FIGURE 13 OUT-OF-BAND NEIGHBOR CONFIGURATION
ii. Click the Add button to add an out-of-band neighbor con-

figuration item.
ues.

Caution:
– In configuration, the port of the out-of-band control in-
terface and the Ethernet ID of the out-of-band neighbor
have the same value. The default value is 1.
– The configuration of the out-of-band neighbor only con-
figures the out-of-band control channel neighbor of the
LMP protocol. The LMP protocol will maintain the con-
trol channel on the out-of-band interface.
– If the LMP is selected as Not In Use, the LMP protocol
will not maintain the out-of-band control channel.
The Ethernet interface of the out-of-band

Eth ID
control interface. The default setting is 1.
The node ID of the opposite end connected

Z End Node ID with the control interface. Input the ASON
node ID of the opposite end.
The IP address of the opposite end control

interface connected with this control
Z End IP
interface. Input the IP address of the NE
at the opposite end.
The next hop IP address of the opposite

Next Hop end control interface. The default setting is
0 and no need to input.
Whether the LMP protocol is enabled on the

LMP control interface or not. The default setting
is "In Use".
The current status of the control channel.

No need to input. The status of the control
IPCC Status
channel will be displayed in this field after
successful configuration.

END OF STEPS
Result After configuring the control interface, the control channel is set
up between ASON NEs to provide routes for transferring message
packets on the control plane.
Configuring TE Link Property

� The fibers between the ports of the NEs to be managed have

� The TE link to be set is usable.

Context Users can set the TE link parameters: weight and SRLG.
� Weight indicates the use cost. The smaller the weight is, the
link has a higher priority of being chosen when the route se-
lection policy is based on the lowest link cost.
� SRLG is Shared Risk Link Group. In practical application, some
links are under the same physical risk. For example, these links
are fibers in the same cable. When the cable is broken, all the
links will be broken. Therefore, these links can be included in a
same SRLG, that is, the SRLG values of these links can be set
to the same value. When the intelligent service is rerouting,
the links with the same SRLG value will be avoided.
ASON NE.
2. Select the menu item Device > ASON > TE Link to pop up
the TE Link dialog box.
3. All the TE links with the selected NE as one end are listed in
the dialog box. Select a TE link to be configured.
Caution:
Due to the features of optical network, the TE information of
the link is maintained in the receiving direction. The two direc-
tions of a link are maintained by the NEs at two ends respec-
tively. Therefore, an NE can only operate the TE attributes at
the receiving end of its link, that is, the link when the current
NE is Remote NE. Meanwhile, users must login to the NE at
the other end, and find the corresponding TE link of the oppo-
site direction for synchronous modification.
4. Double-click the Weight property to configure it. The valid

range is 1–4294967295.
FIGURE 14 WEIGHT CONFIGURATION OF TE LINK
Note:
When a fiber cut or an MS alarm occurs, the weight of the TE
link will be identified as the maximum value automatically and
no need to be modified.
5. Double-click the SRLG property to configure it. One TE link

has five SRLG values at most, and each value is separated by
a comma.

FIGURE 15 SRLG CONFIGURATION OF TE LINK
Note:
If the control plane of a node fails, its related TE link will be
unusable. The neighbor node needs about 30 minutes for route
aging failure, so as to delete such TE link information.
END OF STEPS
Result Repeat steps 1~3 to query the configured TE link information. The
weight or the SRLG value should be the configured value.
Querying ControlPlane Run

Topo
� The ASON NE control channel has been configured.
Context Use this procedure to view the control channel topology informa-
tion of the whole ASON network.
ASON NE.
2. Select the menu item Device > ASON > ControlPlane Run
Topo to pop up the ControlPlane Run Topo dialog box as
shown in Figure 16.

FIGURE 16 CONTROLPLANE RUN TOPO DIALOG BOX
3. View the control channel topology information of the network.

� In the ControlPlane Run Topo dialog box, the upper part
of the window lists the detailed information of control chan-
nel. The meanings of the fields are described in the table
below.
Port Id Type Port ID of the control channel
A End Source end of the control channel
Z End Destination end of the control channel
Link Weight Weight of the control channel
� In the ControlPlane Run Topo dialog box, the lower part

of the window displays the running topology of the control
plane. The line between NEs indicates the existence of the
control channel.
END OF STEPS

Querying ControlPlane
Timeslot Cross
Context Use this procedure to view the timeslot cross-connection informa-
tion of the control plane.
ASON NE.
2. Select the menu item Device > ASON > ControlPlane
Timeslot Cross, and the ControlPlane Timeslot Cross
dialog box pops up, as shown in Figure 17.
FIGURE 17 CONTROLPLANE TIMESLOT CROSS DIALOG BOX
3. View the timeslot cross-connection information in the control

plane of the current ASON NE.
The meanings of the fields are described in the table below.
Rate The rate level of the timeslot cross
A End The source end of the timeslot cross
Z End The destination end of the timeslot cross

The protection end to which service

Protection End signals are sent concurrently when a
protection connection is available
The service that the timeslot cross belongs

Trail User Label
to
Direction The direction of the timeslot cross
END OF STEPS
Resetting ASON Node

� The EMS can properly manage the node to be reset.
Context Use this procedure to reset an ASON node.
Caution:
Resetting an ASON node will interrupt all services on the node.
If some services are running on an ASON node, users should be
cautious in performing this operation.

ASON NE.
2. Select the menu item Device > ASON > Reset Ason Node,
and the Reset Ason Node dialog box pops up.
3. In Reset Delay Time (ms), input the delay time before re-
setting, in ms. The default value is 1000, indicating the ASON
node will be reset in 1000ms.
4. Click the Apply button.
END OF STEPS
Result The ASON node will be automatically reset after the configured
Reset Delay Time (ms).

ASON Configuration
Example
Networking Description
Figure 18 illustrates a networking example of four ASON NEs. This
network contains an MS link and an MS ring. All these four nodes
use in-band signaling mode and enable the automatic discovery
function.
FIGURE 18 NETWORK WITH AN MS LINK AND AN MS RING
The IDs of these four nodes are as follows:
NE Node ID
NE1 180.180.180.125
NE2 180.180.180.22
NE3 180.180.180.19
NE4 180.180.180.18
Configuration Flowchart
The configuration flowchart is as shown in Figure 19.

FIGURE 19 CONFIGURATION FLOWCHART
Configuration Steps
Configuring Four-Fiber Link 1+1 MS Protection

ASON NE.
2. Select the menu item CommonConfig > Protection Man-
agement > MS Protection to pop up MS Protection dialog
box.
3. Click the button to pop up the Create Protection Group

FIGURE 20 CREATE PROTECTION GROUP DIALOG BOX (1)

ProtectionGroup ID Keep the default value.
Userlabel Keep the default value.
ProtectionGroup type Select SDH Four-fiber Link 1+1 MS

Protection (MSP 1+1)
Description Input information as needed.
5. After configuration, click the Next button to enter the Protec-

tion Parameter configuration interface.
Return mode Select Revertive.
Extra service It can not be modified. No need

to be configured.
Wait to Restore Time The unit is minute. Set as

(minutes) required. The default value is
recommended.
Pmc Set as required. The default

setting is recommended.
Alarm Clear Affirm Time The unit is second. Set as

(seconds) required. The default value is
recommended.
Protection levels Set as required. The default

level is recommended.
7. Click the Next button to enter the Protection Relation con-

figuration interface.

8. Configure the protection relation of the port, that is, select

the Type of the port as work or protection. For example, the
working port of node NE2 is 6.5, and the protection port is 6.8.
9. After configuration, click the Next button to enter the APS
Setting configuration interface.
Caution:
The Automatic Protection Switching (APS) protocol must be en-
abled. Otherwise, the four-fiber link 1+1 MS protection cannot
take effect.
10. Select the check box in the APS Protocol row to enable the
APS protocol.
11. Click the Finish button.
If a success message box pops up, it indicates that the MS
protection group is successfully created.
12. Click the OK button to close the message box and return to
the MS Protection dialog box.
END OF STEPS
Result The MS Protection dialog box will display the newly-created pro-
tection group.
Configuring Two-Fiber Bidirectional MS Shared

Protection Ring
Context The APS IDs of the nodes in the two-fiber bidirectional MS shared
protection ring are shown in Figure 24

FIGURE 24 APS IDS OF NODES IN TWO-FIBER BIDIRECTIONAL MS SHARED

PROTECTION RING

ASON NE.
2. Select the menu item CommonConfig > Protection Man-
agement > MS Protection to pop up MS Protection dialog
box.
3. Click the button to pop up the Create Protection Group

FIGURE 25 CREATE PROTECTION GROUP DIALOG BOX 1 (FOR MS SHARED PROTECTION

RING CONFIGURATION)
ProtectionGroup ID Keep the default value.
Userlabel Keep the default value.
ProtectionGroup type Select SDH Two-fiber Bidirectional MS

Shared Protection Ring (with Extra Service)
Description Input information as needed.
5. After configuration, click the Next button to enter the Protec-

tion Parameter configuration interface, as shown in Figure
26.

FIGURE 26 CREATE PROTECTION GROUP DIALOG BOX 2 (FOR MS SHARED PROTECTION

RING CONFIGURATION)
6. Configure the Protection Parameter. Refer to "Configuring

Four-Fiber Link 1+1 MS Protection".
7. Click the Next button to enter the Protection Relation con-
figuration interface.
Set the protection relation between related ports. For example,
two ports, 6.4 and 6.6, of the node NE2 should be configured,
as shown in Figure 27.
FIGURE 27 CREATE PROTECTION GROUP DIALOG BOX 3 (FOR MS SHARED PROTECTION RING
CONFIGURATION)
8. After configuration, click the Next button to enter the APS

Setting configuration interface, as shown in Figure 28.
FIGURE 28 CREATE PROTECTION GROUP DIALOG BOX 4 (FOR MS SHARED PROTECTION RING
CONFIGURATION)

Caution:
The APS protocol must be enabled. Otherwise, the two-fiber
bidirectional MS shared protection ring cannot take effect.
9. Configure the property values in APS Setting.

In this configuration example, the APS IDs of three nodes on
the ring are respectively set as 1, 2 and 3, as illustrated in
Figure 24. Taking NE2 as an example, refer to the following
table to configure the properties.
LocalNode APS Id Input "3".
NeighborNode APS Input "1". It is the opposite node

ID-Direction 1–work of port 6.4, that is, node NE3.
port
NeighborNode APS Input "2". It is the opposite node

ID-Direction 2–work of port 6.6, that is, node NE4.
port
APS Protocol Select the check box to enable the

APS protocol.
10. After configuration, click Finish.

If a success message box pops up, it indicates that the MS
protection group is successfully created.
11. Click the OK button to close the message box and return to
the MS Protection dialog box.
END OF STEPS
Result The MS Protection dialog box will display the newly-created pro-
tection group.
Configuring Necessary Overheads of Transfer

Ports
ASON NE.
2. Select the menu item CommonConfig > Overhead Manage-
ment > Overhead Config to pop up the Overhead Config
FIGURE 29 OVERHEAD CONFIG DIALOG BOX

3. Click the Add button to add an overhead configuration item.

4. Configure the new overhead item according to the table below.
Configuration Select the optical board where the optical

Board port to be configured is located.
PTP Select the port number.
Row No. and

Select R1C7[J0].
Column No.
Input the send value of the port to be

configured. Keep the default value.
The form of the send value is N-AABBCC,
where N is the node number, AA is the
Send Value frame number, BB is the slot number and
CC is the port number.
For example, the node number of NE2 is 2,
then the send value of the first port at slot
6 of node NE2 is 2–010601.
Note:
In this example, only the four items in the above table need to
be configured.
END OF STEPS
Result After configuring the J0 overheads of the ports on the optical line
boards at both ends, click the corresponding Receive Value but-
ton of the port, the receive value should be able to be
obtained properly.
Configuring Transfer Ports

ASON NE.
Note:
In this example, only NNI Trans (transfer port) and iNNI Ctrl
(in-band control interface) need to be configured.
3. Configure the NNI Trans tab.

i. Click the NNI Trans tab to enter the transfer port config-
uration interface.

ii. Click the Add button to add a transfer port configuration

item.
iii. Configure the new transfer port according to the table be-
low.
PTP Select the port to be configured.
For an unprotected port, all

resources are used by default. For
Resource Partition a port configured as two-fiber MS
protection ring, half of the resources
are used.
Select the check box to enable the

Autodiscovery
automatic discovery function.
Note:
In this example, only the three items in the above table
need to be configured.

Taking NE2 as an example, configure the transfer port
needed by NE2, as shown in Figure 30.
FIGURE 30 INNI MANAGEMENT DIALOG BOX - NNI TRANS
4. Configure the iNNI Ctrl tab.

i. Click the iNNI Ctrl tab to enter the in-band control inter-
face configuration interface.
ii. Click the Add button to add an in-band control interface
configuration item.
iii. Configure the new in-band control interface according to
the table below.
PTP Select the port to be configured.
Name Status Select unnamed.

Note:
In this example, only the two items in the above table need
to be configured.

The configuration of the in-band control interface is shown
in Figure 31.
FIGURE 31 INNI MANAGEMENT DIALOG BOX - INNI CTRL
END OF STEPS
Result After configuring all the transfer ports between nodes, the ASON
can automatically discover TE links.
After completing all the configurations described in the "Configura-
tion Steps" section, the network as shown in "Network with an MS
Link and an MS Ring" is capable of commissioning ASON services.

This page is intentionally blank.

Chapter 2
Configuring and
Managing ASON
Services
Table of Contents
Querying Calls ..................................................................33
Creating Calls ...................................................................36
Configuring ASON Tunnel Services .......................................53
Configuring Control Plane 1:N Protection Groups....................55
Configuring Associated Services ..........................................59
Modifying Calls ..................................................................60
Setting Service Startup/Stop...............................................61
Setting Manual Reversion of Calls ........................................62
Activating/Deactivating Call Restoration................................63
Modifying Initial Connection ................................................64
Optimizing Calls ................................................................65
Querying Calls
Prerequisites � The EMS user has the rights of "Supervisor Role" or above.
Context Use this procedure to query the call information, detailed routes
of SNC, etc.
ASON NE.
2. Select the menu item Device > ASON > Call Management.
The Call Management dialog box pops up, as shown in Figure
32.

FIGURE 32 CALL MANAGEMENT
3. Set query conditions.

In the Call Management dialog box, filter the current calls ac-
cording to the filter conditions such as User Label, Call Sta-
tus, A End, Z End, Setup Time, Close Time, etc.
Tip:
A End is selected as the default query condition. Users can set
other query conditions as needed.
4. Click the Search button to query calls according the configured

conditions.
The queried call information includes the following items.
User Label Identifies the user information.
Call ID Identifies a specific call.
Identifies the local end of a tunnel call. If

Local Tunnel ID the call information is not a tunnel call, the
value is 0.

Chapter 2 Configuring and Managing ASON Services
Identifies the remote end of a tunnel call.

Remote Tunnel ID If the call information is not a tunnel call,
the value is 0.
A End The source end of a call.
Z End The destination end of a call.
If the status is Success, it indicates the

Call Status call is normal. Other statuses indicate the
call is abnormal.
Call RPT Reason Displays the call report reason.
5. Query the detailed routes and timeslot information of a call.

i. In the queried call list, select a call to query its SNC infor-
mation.
ii. Right-click on any field of the call, and then select SNC
Management from the shortcut menu. The SNC Man-
agement dialog box displays the SNC information of the
call, as shown in Figure 33.
FIGURE 33 SNC INFORMATION
Figure 33 displays the detailed SNC information of Call ID

1.
As we can see in the figure, the call with the Call ID of 1
contains one connection, and its corresponding SNC ID is
1.
iii. Select this connection, and then select the Cross Connec-
tion tab to view the detailed routing information of this
connection.
As shown in Figure 33, the SNC ID 1 of the Call ID 1 passes
two NEs: NE 125 and NE 22. As shown in order in the
figure, the forward connection passes through the A and
Z timeslots of NE125, and the forward connection passes
through the A and Z timeslots of NE22.

Note:
The definition of forward and backward: If we set up a call
from A to Z, the direction from A to Z is defined as forward,
and the direction from Z to A is backward.
END OF STEPS
Creating Calls
Prerequisites � The EMS users has the rights of "Operator Role" or above.
� ASON functions properly.
Context Use this procedure to create a call connection based on the con-
figured call attributes, such as protection type, restoration type,
route policy, etc.
Tip:
In ZXUCP A100, creating a call means creating an ASON service.

ASON NE.
2. Select the menu item Device > ASON > Call Management
to pop-up the Call Management dialog box.
3. Click the New button, and the Create Call dialog box pops up,

FIGURE 34 CREATING A CALL
4. Set basic properties. Refer to the "Setting Basic Properties"

section.
5. Set other properties. Refer to the "Setting Other Properties"
section.
END OF STEPS
Result � If the call status changes to Success, it indicates that the call
setup is successful.
� If the call status is Failure, it indicates that the call setup fails.
Setting Basic Properties

Context Use this procedure to set the basic properties of a call, such as
type, rate, etc.
Steps 1. In the Create Call dialog box, set the basic properties, as
shown in Figure 35.

FIGURE 35 SETTING BASIC PROPERTY
2. Refer to the following table to set the properties.
Type Not supported at the moment, no need to set.
Options: unidirectional and bidirectional. Select

Direction
bidirectional.
Supports Service VC4, VC4, VC4-4c, VC4-16c and

VC4-64c. Among them, Service VC4 is tunnel
Rate call, while others are non-tunnel call. VC4-4c,
VC4-16c and VC4-64c are concatenation services
of non-tunnel call.
Service Degree Identifies the service level information of a call.
Batch Number Creates calls in batches. The default value is 1.
Identifies the source node, input port and input

A End timeslot of the call. Refer to the "Configuring
the A/Z End" section for configuration steps.
Identifies the destination node, output port

and output timeslot of the call. Refer to
Z End
the "Configuring the A/Z End" section for
configuration steps.
User Label Identifies the name of a call.
Customer Info Identifies the customer name.
Sets whether to activate all created calls

Active immediately. This property is not used at the
moment.

The service state of a call. Select this item to

set instant use of the call. If it is not selected,
Instant use the actions such as restoration and reversion
are not allowed, but the call can be optimized.
It is selected by default.
Description Inputs remarks.
User Define 1~
For customized use as needed.
User Define 3
END OF STEPS
Configuring A/Z End

Context Use this procedure to set the A end and Z end information of a call.
Steps 1. In the Create Call dialog box, click the button after A
End, and the Explorer dialog box pops up, as shown in Figure
36.
FIGURE 36 CREATING A CALL: SELECTING A END NE

2. If the Rate of the call to be created is a Service VC4 (tunnel

service), then perform this step. Otherwise, skip this step.
i. Select the NE name, and then click the Add button.
The selected NE will appear in Selection Result.
ii. Click the OK button.
Now the configuration of service location at A End is com-
pleted.
3. If the Rate of the call to be created is not VC4 of the service
layer, select any field of the NE in Figure 36 and double-click
it, and the resource information of the service board pops up,
FIGURE 37 CREATING A CALL: ADDING A END BOARD
4. Select the slot of the source node correctly according to the

actual networking requirements, and double-click the slot. The
Explorer dialog box pops up and lists all the port information
of the selected service board, as shown in Figure 38.
FIGURE 38 CREATING A CALL: ADDING A END PORT
5. Select the port of the source node according to the actual

networking requirements, and double-click the port. The Ex-
plorer dialog box pops up and lists all the timeslot information
of the selected port, as shown in Figure 39.

FIGURE 39 CREATING A CALL: ADDING A END TIMESLOT
6. Select the timeslot of the source node according to the actual

networking requirements, and then click the Add button.
The selected timeslot will appear in Selection Result.
7. Click the OK button after confirming the above operations are
correct.
Now the configuration of service location at A End is com-
pleted.
END OF STEPS
Result After configuration, the A end (or timeslot) information will appear
in the A End property column in the Create Call dialog box.
Postrequisite Refer to the above steps to configure the Z End.
Setting Other Properties

Context Use this procedure to set the call properties, such as protection
type, restoration type, route strategy, etc. Configure services of
different levels through different combinations of call protection
and restoration property.
Steps 1. Set parameters in the Call tab.
i. In the Create Call dialog box, click the Call tab, as shown
in Figure 40.

FIGURE 40 CALL SETUP: CALL
ii. Refer to the following table to set the properties in the Call
tab.
The try times when the normal call

NormalConnectRe-
connection fails. The recommended
tryCount
value is 3.
The try times when the restoration

RevertConnectRetry-
connection fails. The recommended
Count
value is 3.
The maximum interval of tries when

CallRetryMaxIn-
the connection fails. The unit is 100
terval(100ms)
ms, and the default value is 100.
The minimum interval of tries when

CallRetryMinIn-
the connection fails. The unit is 100
terval(100ms)
ms, and the default value is 1.
Not in use currently. Use the default

Create Priority
value 1.
Not in use currently. Use the default

Revert Priority
value 1.
Supports No Protection, 1+1 SNCP

Protection, MS Protection and SNC
Associated.
– No Protection call only contains
one connection.
– 1+1 SNCP Protection call contains
Protection type two connections: one working
connection and one protection
connection, which form a
"concurrently transmitting and
preferably receiving" relation.
– MS Protection call also contains
one connection only, and the

connection route must be an MS
link.
– SNCP Associated call requires
the connection to form a
cross-domain 1+1 SNCP relation
with another no protection
call. It is used to configure the
service association. For detailed
configuration steps, refer to the
"Configuring ASON Associated
Services" section.
The combination of Protection
type and Reroute in the Reverse
tab decides the service level of a
call. Refer to the following text for
detailed settings.
2. Set parameters in the Reverse tab.

i. Click the Reverse tab, as shown in Figure 41.
FIGURE 41 CALL SETUP: REVERSE
ii. Refer to the following table to set the properties in the Re-
verse tab.
Whether to enable restoration or not.

Select this item to enable restoration.
Reroute The combination of Reroute and
Protection type in the Call tab decides
the service level of a call. Refer to the
following text for detailed settings.
Applicable to the call with restoration

property. This item is configurable only
Reroute after Reroute is selected.
Reversion Mode
Options: Non-revertive, Auto Revertive and
Manual Revertive.

– Non-revertive: After the service

is switched to the restoration
connection, the system deletes the
original working connection first,
and then changes the restoration
connection to working connection.
– Auto Revertive: After the service
connection, the system keeps the
original working connection. When
the fault of the original working
connection is removed, the service
will automatically reverse to the
original working connection, and
then the restoration connection will
be deleted.
– Manual Revertive: After the service
connection, the system keeps the
original working connection. But
when the fault of the working
connection is removed, the service
will not automatically reverse to
the original working connection,
and manual reversion needs to be
initiated through the EMS. Refer to
the "Setting Manual Reversion of
Calls" section for the operation steps
of manual reversion.
The Auto Revertive mode is recommended.
The delay time before the restoration is

initiated when the service gets faulty.
The unit is 100 ms, and the range is
0~100. That is, the range of reroute delay
time is 0 to 10 s.
When Auto is selected, the reroute delay
time will be decided by the control plane,
Reroute Delay and the Reroute Delay Time(100ms)
Time(100ms) cannot be set manually in this case.
It is recommended to set to Auto.
When the Reroute Delay
Time(100ms) is set to Auto, the
control plane automatically sets the
reroute delay time of the MS call to 100
ms, and automatically sets the reroute
delay time of other calls to 0 ms.
The waiting time before the reversion

Reroute WTR is initiated. The unit is second and the
Time(s) range is 60~720. It is recommended to
set the reroute WTR time to 60.

Note:
In T31, service levels are implemented by configuring ser-
vices as different protection types and restoration types.
The detailed configuration is as follows:
– Service level 1: Protection type is configured as 1+1
SNCP Protection; Reroute is selected.
– Service level 2: Protection type is configured as MS
Protection; Reroute is selected.
– Service level 3: Protection type is configured as 1+1
SNCP Protection; Reroute is not selected.
– Service level 4: Protection type is configured as MS
Protection; Reroute is not selected.
– Service level 5: refer to the "Configuring Control Plane
1:N Protection Groups" section for the configuration.
– Service level 6: Protection type is configured as No
Protection; Reroute is selected.
– Service level 7: Protection type is configured as No
Protection; Reroute is not selected.
After configuring Protection type and Reroute of a call,
users should continue to configure other properties based
on the requirements and characteristics of service levels.
3. Set parameters in the Protection tab.
Note:
� The parameters in the Protection tab are configurable only
when the Protection type in the Call tab is set as 1+1 SNCP
Protection or SNCP Associated.
� SPC Name and SPC Property are configurable only when
the Protection type in the Call tab is set as SNCP Associated.
i. Click the Protection tab, as shown in Figure 42.

FIGURE 42 CALL SETUP: PROTECTION
ii. Refer to the following table to set the properties in the Pro-
tection tab.
The delay time of SNCP switching. The unit

SNCP de-
is 100 ms and the range is 0~100. That is,
lay time(100
the delay time range is 0~10 s. The default
ms)
value is 0.
The SNCP waiting reversion time. After

SNCP switching, the waiting time before
the protection connection reversing to the
SNCP Wrt
working connection from the moment that the
Time(min)
fault of the working connection disappears.
The unit is min and the range is 1~12. The
default value is 5.
Supports Non-revertive and Revertive.

– Non-revertive: After the alarm of the
SNCP working connection disappears,
the service is still transferred on the
protection connection without being
Reversion reversed.
Mode
– Revertive: After the alarm of the
SNCP working connection disappears,
the service reverses to the original
working connection from the protection
connection.

Identifies the unprotected call connection

associated with the current call connection.
These two connections form a 1+1 SNCP
SPC Name
relation that crosses the control domain, that
is, concurrently transmitting and preferably
receiving.
Identifies whether the current call connection

is the working connection or protection
connection in the 1+1 SNCP relation.
SPC Property
If the current call connection is the protection
connection, then its associated call connection
is the working connection, or vice versa.
4. Set parameters in the Route Strategy tab.

i. Click the Route Strategy tab, as shown in Figure 43.
FIGURE 43 CALL SETUP: ROUTE STRATEGY
ii. Set the parameters of Basic route strategy in the Route

Strategy tab.
Note:
– In Basic route strategy, the independence strategy
(InServiceNodeDiversityLevelOfEffort, InSer-
viceLinkDiversityLevelOfEffort and InServiceSRL-
GDiversityLevelOfEffort) is configurable only when
the Protection type in the Call tab is set as 1+1 SNCP
Protection or SNCP Associated.
– When the basic route strategy is applied in the SNCP
associated protection call, its meaning is the same as
applying in the 1+1 SNCP call. The difference is that,
the two associated connections in the SNCP associated
protection call belong to two different unprotected calls.

The basic route independence strategy (InServiceNode-

DiversityLevelOfEffort, InServiceLinkDiversityLevel-
OfEffort and InServiceSRLGDiversityLevelOfEffort) is
used in the following two situations:
– When creating a 1+1 SNCP call or an SNCP associated
call, the working connection and protection connection
must satisfy the configured route independence strat-
egy.
– If one of the connections (for example, the working con-
nection) of the 1+1 SNCP call or the SNCP associated
call fails, the restoration connection and the protection
connection must satisfy the configured independence
strategy in the basic route strategy.
Caution:
When the resource is not sufficient, the creation of a call
must still satisfy the configured independence strategy. In
this case, a call that satisfies the independence strategy
may not be created successfully, which results in service
interruption.
Refer to the following table to set the parameters of Basic

route strategy in the Route Strategy tab.
Options: Min links weight and Min nodes

weight.
– Min links weight: the minimum
links by which the call connection
passes under the condition that the
independence strategy is satisfied.
Min Weight Type Refer to the "Configuring TE Link
Property" section to set the value
of link weight.
– Min nodes weight: the minimum
nodes by which the call connection
passes under the condition that the
independence strategy is satisfied.
Two connections cannot pass the same

node except for the first node and the
last node.
No need to set this item for the one
hop service, because it is definitely
InServiceNodeDi- satisfied.
versityLevelOfEf- For the detached connection or
fort associated call connection, when the
created connection has a different
last node, the created connection
should exclude the last node of the
detached connection or associated call
connection.

InServiceLinkDi-
Two connections cannot pass the same
versityLevelOfEf-
link.
fort
The created connection must exclude

all the links under the SRLG which the
specified link belongs to.
InServiceSRLGDi- To exclude a link in the SRLG when
versityLevelOfEf- creating a call, specify InServi-
fort ceSRLGDiversityLevelOfEffort. Thus
all the links under the SRLG which this
link belongs to will be excluded when
the control plane is calculating routes.
iii. Set the parameters of Additional route strategy in the

Route Strategy tab.
Additional route strategy is used to specify the detached
connection of the current connection, and it specifies the
independence strategy of the two connections.
The independence strategy includes InServiceNodeDi-
versityLevelOfEffort, InServiceLinkDiversityLevelOf-
Effort and InServiceSRLGDiversityLevelOfEffort
Additional route strategy applies to the creation of any
type of call.
For example, when creating a call, users set Additional
route strategy, that is, specify Detach and the indepen-
dence strategy, then the "call connection" and the "spec-
ified detached connection" created by the control plane
must satisfy the configured independence strategy in Ad-
ditional route strategy.
Specify the name of the

detached connection, and then
configure the independence
Detach strategy that the detached
connection and current
connection must satisfy in the
subsequent parameters.
The current call connection

and the detached connection
InServiceNodeDiversityLe-
cannot pass the same node
velOfEffort
except for the first node and
the last node.

InServiceLinkDiversityLe-
velOfEffort
cannot pass the same link.

InServiceSRLGDiversityLe-
must exclude all the links
velOfEffort
under the SRLG which the
specified link belongs to.

Note:
When the independence strategy is not specified, the con-
trol plane will try its best to satisfy the node independence,
link independence and SRLG independence.
5. Set included links and excluded links.

i. In the main interface of the Create Call dialog box, click
a link to set included links and excluded links. The Limit
Setting column will display the corresponding configura-
tion item.
FIGURE 44 CALL SETUP: LIMIT INFORMATION

Tip:
More than one links may exist between the neighboring
NEs. Check the property value of Resource in the Limit
Setting column to ensure the correct link is selected. The
assistant tools on the top of the interface can be used for
selection if necessary.
ii. Refer to the following table to set the parameters of in-

cluded links and excluded links.
Lists the currently selected link information, so

Resource that users can confirm whether the selected
link is correct or not. No need to be configured.
Not used currently and no need to be

Channel
configured.
Identifies the limit type to be configured. The

options are None, Through, Protect and Forbidden.
None: No limit.
Through: The working connection must pass
through this link.
Limit Type Protect: The protection connection must pass
through this link.
Forbidden: The working connection and the
protection connection must exclude this link.
Refer to configuration example in the following
text for the detailed description of Limit Type.
Differentiates strict route limit and loose route

limit. It is only applicable to the Through or
Protect link limit, and not applicable to the
Forbidden limit. The options are Strict and Loose.
If the included link limit is set as strict, this link
limit has one hop interval at most compared
with the previous included (link or node) limit.
There is no such a requirement if the limit
degree is loose.
Limit
Degree Strict: This link limit has one hop interval at
most compared with the previous included
(link or node) limit.
Loose: This link limit has no interval restriction
compared with the previous included (link or
node) limit.
text for the detailed description of Limit
Degree.

Identifies the direction of the limit route.

The rules on the direction of included and
excluded links must be strictly followed.
Direction
Otherwise, the route search will fail.
text for the detailed description of Direction.
It is configurable only when the Limit Type is

Exclude
Forbidden. Users can select whether to exclude
SRLG
SRLG or not.
Caution:
To set multiple limit messages, click the corresponding link
again, and they can only be validated after all fields are set.
– A configuration example of Limit Type and Limit De-

gree parameters:
In the example shown in Figure 45, create a call from NE
A to NE E. Suppose two included messages are set, the
first included message is the included link limit A→B;
If the second included link limit is D→E, and the limit
degree is strict, when the route module is calculating
the connection path, there should be no more than one
hop from the first link A→B to the second included link
D→E. Obviously a route that can meet such a condition
is not available, so the failure of route calculation will
be returned. It is acceptable if the second included link
message is B→C or C→D.
FIGURE 45 CALL SETUP: INCLUDED AND EXCLUDED LIMITS
– A configuration example of the Direction parameter:

For example, in Limit Setting in Figure 46,
NE125/NE22 is displayed in the resource field. As
shown in the left pane of the window, NE125 is A End,
and NE22 is Z End. In this case, the direction of route
limit should be set as A-Z. If the direction is selected
as Z-A wrongly, it will result in failure of route search.

FIGURE 46 CALL SETUP: ROUTE LIMIT DIRECTION CONFIGURATION
END OF STEPS
Configuring ASON Tunnel

Services
Context Use this procedure to create a tunnel and configure low rate ser-
vices on the tunnel.
Note:
Refer to the "Tunnel Services" section for details.
Steps 1. Create a tunnel.

i. In the NetNumen T31 Topology Management view, se-
lect an ASON NE.

ii. Select the menu item Device > ASON > Call Manage-
ment, and the Call Management dialog box pops up.
iii. Click the New button to enter the Create Call dialog box.
iv. Configure the call property: Select Service VC4 for the speed.
Note:
For the configuration of other call properties and the call
setup steps, refer to the "Creating Calls" section.
v. After configuration, click the Apply button.

2. Configure cross-connection and create low rate tunnel ser-
vices.
Note:
To add services on the tunnel, the corresponding cross-con-
nection needs to be configured on the EMS after the tunnel is
created.
i. In the NetNumen T31 Topology Management view, se-

lect the first node NE.
ii. Select the menu item Operation > Topology Operation
> Cross Connection to enter the Cross Connection di-
alog box.
iii. Click the Graphics Mode tab.
iv. Select Edit and Double in Operation.
FIGURE 47 TIMESLOT CONFIGURATION OF SERVICE ON TUNNEL
v. Connect the timeslots under the tunnel ID of the corre-

sponding tunnel service based on service requirements.
vi. Click the Apply button.
END OF STEPS
Result The finished interface after tunnel creation is shown in Figure 48.

FIGURE 48 FINISHED INTERFACE OF TUNNEL CREATION
The EMS has allocated a Local Tunnel ID and a Remote Tunnel

ID for the created tunnel.
After configuring the low rate tunnel service, the configured ser-
vice can be queried by querying calls.
Configuring Control Plane

1:N Protection Groups
� The call to be added to the 1:N protection group has been
created. The call must be non-tunnel call, and the call property
must be no protection and no restoration.
Context This section describes the steps of configuring ASON control plane
1:N protection groups.
Note:
Steps of establishing a Level 5 service:
1. Create a call with no protection and no restoration as per user
requirements.
2. Configure a 1:N protection group, and add the created call to
the 1:N protection group as a working service.
Steps 1. In the NetNumen T31 Service View view, select an ASON NE.
2. Select the menu item Configuration > 1:N Protection
Group Management, and the 1:N Protection Group Man-
agement dialog box pops up, as shown in Figure 49.
FIGURE 49 1:N PROTECTION GROUP MANAGEMENT INTERFACE

3. Click the Add… button to pop up the Create 1:N Protection

Group dialog box.
4. Configure Protection Group Info.
i. In the Create 1:N Protection Group dialog box, click the
Protection Group Info tab.
FIGURE 50 CREATE 1:N PROTECTION GROUP
ii. Refer to the following table to configure the properties.
User Label Identifies the protection group, such as PG1.
Select the service direction according to the

Service configuration of the protection group. If it is
Direction a unidirectional service, select Unidirection. If
it is a bidirectional service, select Bidirection.
Configure the source NE of the service in

NE A the protection group. Click the Select…
button to configure it.
Configure the destination NE of the service

NE Z in the protection group. Click the Select…
button to configure it.
Whether to enable the protection switch

Enable function of the protection group. Select the
Protection check box to enable the switch function;
Switch Deselect the check box to disable the switch
function.
The waiting time before the service is

Waiting
switched from the protection connection to
Time for
the working connection. The unit is min and
Revert(min)
the range is 1~12. The default value is 1.
The finished configuration figure of the Protection Group

Info is shown in Figure 51.

FIGURE 51 PROTECTION GROUP INFO TAB
5. Configure Working Service Info.
Caution:
The service added to the protection group must be no protec-
tion and no restoration.

Working Service Info tab to enter the Working Service
Info configuration interface.
ii. Click the Add… button to pop up the Explorer dialog box.
iii. In the Explorer dialog box, select the filter conditions as
needed, and then click the Filter button to query the ser-
vices with the same source/destination ends as the protec-
tion group.
Note:
If no filter condition is set, then all the services with the
same source/destination ends as the protection group will
be queried.
iv. Select the service to be added to the protection group from

the filtered result, and then click the Add button to add the
selected service to the working service information. The
number of selectable services is 1~15.
v. Click the OK button after selection. Return to the Create
1:N Protection Group dialog box.
The figure after adding working services is shown in Figure
52.

FIGURE 52 FINISHED CONFIGURATION FIGURE OF WORKING

SERVICE INFO
vi. Configure other properties of the working service.
Identifies the service added to the

Service Label protection group. No need to be
configured.
The range is 1~4. It is not used at

Priority
present. Keep the default value.
The waiting time before the

occurrence or cancellation of the
switching when an alarm occurs
Waiting Time for or disappears. The unit is 100 ms
Switch(100ms) and the range is 0~100, that is, the
range is 0~10 s. The default value
is 0, that is, the service is switched
as soon as an alarm occurs.
6. Configure Protection Service Info.
Caution:
� The service added to the protection group must be no pro-
tection and no restoration.
� Only one protection service can be added to one 1:N pro-
tection group at present.

Protection Service Info tab to enter the Protection Ser-
vice Info configuration interface.
ii. Click the Add… button to enter the Explorer interface.
iii. Add a protection service. The selected service will be the
protection service in the work group. Refer to the configu-
ration steps of Working Service Info for detailed steps.
iv. Click the OK button.
The finished configuration figure of Protection Service Info
is shown in Figure 53.
FIGURE 53 FINISHED CONFIGURATION FIGURE OF PROTECTION SERVICE

INFO

7. After the parameters of 1:N protection group are configured,

click the OK button.
END OF STEPS
Result The finished configuration figure of 1:N protection group is shown

in Figure 49.
Configuring Associated
Services
Context � The two associated calls must be no protection calls rather than
calls of other types.
� The associated service is used to form a 1+1 SNCP relation
between two calls that cross control domains. In the local con-
trol domain, the two calls that form a 1+1 SNCP relation start
from the same first node but end at different destination nodes.
That is, the two calls have different routes in the local control
domain, and the add/drop service timeslots are the same at
their source nodes.
Steps 1. Set up the first call.
Configure the properties of the first call: the service Protec-
tion type must be configured as No Protection.
Note:
The configuration of other call properties is the same as an
unprotected service. Refer to the "Creating Calls" section for
details.
2. Set up the second call.

Refer to the following table to configure the properties for the
second call:
Protection type Set to SNCP Associated.
Reroute
Set to Non-revertive.
Reversion Mode

Select the first call created in the previous

SPC Name step. Now the association between the two
connections is established.
If Work is selected, this call connection is the

working connection in the 1+1 protection
SPC Property relation, while the first call connection is the
protection connection in the 1+1 protection
relation, and vice versa.
Note:
The configuration of other call properties is the same as a 1+1
SNCP service. Refer to the "Creating Calls" section for details.
END OF STEPS
Result The two configured unprotected services are associated and form
1+1 protection relation.
Modifying Calls
� A call has been created and the call status is normal.
Caution:
A call is not allowed to be modified in the following cases:
� The call is not in the normal status.
� The call has been added to a 1:N protection group.
� The call has been restored and the protection connection ex-
ists.
� The No Protection call configured with SNCP associated protection
cannot be modified to a 1+1 SNCP Protection call.
� The reversion modes of the SNCP Associated call and the 1+1 SNCP
Protection call must be Non-revertive and cannot be modified to
Auto Revertive or Manual Revertive.
� The reversion mode of the MSP call cannot be modified as non-
revertive.
Context Use this procedure to modify the basic parameters of a call con-
nection, including protection property, restoration property, route
strategy, etc.


ASON NE.
2. Select the menu item Device > ASON > Call Management,
and the Call Management dialog box pops up.
3. In the Call Management dialog box, select a call to be modi-
fied.
4. Click the Modify button, and the Modify Call dialog box pops
up.
5. Modify the call information.
The call modification is described as follows:
� The call parameters that can be modified include: User La-
bel, Instant Use, NormalConnectRetryCount, Revert-
ConnectRetryCount, CallRetryMaxInterval(100ms),
CallRetryMinInterval(100ms), Create Priority, Pro-
tection Type, Reroute, Reroute Reversion Mode,
Reroute Delay Time, Reroute WTR Time, Basic route
strategy and Additional route strategy. The meanings
of above fields are described in the "Creating Calls" section.
� To modify a No Protection call to a 1+1 SNCP Protection call, a
protection connection needs to be added. To modify a 1+1
SNCP Protection call to a No Protection call, a connection in
the 1+1 SNCP needs to be deleted. The connection to be
deleted is decided by the control plane strategy, and a rule
should be followed: the faulty connection is deleted first.
� The modification between a No Protection call and an MS Pro-
tection call is supported. There are two steps to modify the
No Protection call to the MS Protection call:
a) Modify the protection type.
b) Perform a call optimization on the modified call.
6. Click the Apply button after modification.
END OF STEPS
Result After modifying a call, query the call information again. The call
properties should be the modified properties.
Setting Service Startup/Stop

� A call has been created.
Context Use this procedure to set the startup or stop of the service.
ASON NE.
3. In the Call Management dialog box, select a call to be modi-
fied.

4. Click the Modify button, and the Modify Call dialog box pops
up.
5. Set service startup/stop.
� Select Instant Use to start up the service.
� Deselect Instant Use to stop the service.
FIGURE 54 SERVICE STARTUP/STOP

END OF STEPS
Result � After selecting the Instant Use check box, the service starts
up.
� After deselecting the Instant Use check box, the service
stops.
Setting Manual Reversion of

Calls
� A call has been created. The Reroute Reversion Mode of the
call is Manual Revertive, and the service has been switched from
the working connection to the restoration connection.
Context When the fault of the working connection disappears, the rever-
sion needs to be triggered manually to switch the service from the
restoration connection to the working connection.
ASON NE.
3. In the Call Management dialog box, query the calls to be
handled.

Note:
Refer to the "Querying Calls" section for the query method.
4. Right-click a call to be handled, and then select Manual Re-

cover in the pop-up shortcut menu, as shown in Figure 55.
FIGURE 55 MANUAL CALL REVERSION
END OF STEPS
Result The service is switched from the restoration connection to the

working connection.
Activating/Deactivating Call
Restoration
� A call has been created.
Context � The Revert Active of a call is used to activate the restoration,
which is applied in two situations as follows:
� If the original Reroute property of a call is not enabled,
the restoration will not be activated even the call connec-
tion fails. The control plane will trigger a call restoration
automatically if the Revert Active operation is performed
once.
� If the original Reroute property of a call is enabled, when
the working connection fails, the restoration is triggered.
However, due to insufficient resource in the network or
other reasons, the restoration fails after maximum times
have been tried. Thus, even all of the resources needed by
the restoration are satisfied afterwards, the control plane
will not activate restoration automatically. In this case, the
Revert Active command needs to be issued by the EMS
manually to trigger an activation.

� The Revert Deactive of a call is used to deactivate the restora-

tion function.
ASON NE.
handled.
Note:
4. Right-click a call to be handled, and then select Revert Active

or Revert Deactive in the pop-up menu, as shown in Figure
56.
FIGURE 56 RESTORING CALL ACTIVATION/DEACTIVATION
END OF STEPS
Result � After performing the Revert Active operation, the call auto-
matically initiates a restoration.
� After performing the Revert Deactive operation, if the call is
waiting for restoration, then the restoration is stopped; If a
restoration is progressing (the restoration connection is being
created), the restoration will continue. But the subsequent
restoration will not be implemented.
Modifying Initial Connection

� A call has been created, and the call has the reversion property.
That is, the working connection and the restoration connection
exist. Meanwhile, the call restoration has been completed.

Context For a service with reversion property and the restoration is

completed, the management plane can request the control plane
to modify the restoration connection to working connection and
delete the original working connection. In this case, the initial
connection needs to be modified.
ASON NE.
handled.
Note:
4. Right-click a call to be handled, and then select Modify Init

Link to Work in the pop-up menu, as shown in Figure 57.
FIGURE 57 MODIFY INIT LINK TO WORK
Note:
T31 V1.10 version supports Modify Init Link to Work, and
the subsequent version will support Modify Init Link to Pro-
tect.
END OF STEPS
Result The restoration connection of the call is modified to working con-

nection.
Optimizing Calls

� A call has been created, and the call is in normal status.

Context Due to the reasons such as EMS, traffic engineering, etc., some
connections in a call need to be optimized.
For example, the independence principles with other connections
are added, the node independence, link independence, SRLG in-
dependence, etc. of the call connection are added.
Caution:
The call optimization is not allowed in the following situations:
� Optimization on the call in a 1:N protection group.
� Restoration connection exists in a call when optimizing.
� Optimization on two SNCP associated calls at the same time.
� Optimization on the working connection and protection con-
nection in the 1+1 SNCP call at the same time.
Steps 1. In the NetNumen T31 Service View, select the link to be op-
timized for call connection.
The EMS will display all the call connections passing the link.
2. Right-click the call connection to be optimized, and then select
the menu item SPC Optimize Rerouting to enter the SPC
Optimize Rerouting interface.
3. Configure Route Constraint.
i. To add the Route Constraint condition, click the Route
Constraint tab to enter the configuration interface of route
constraint.
ii. Add link constraint conditions. To add link constraint con-

ditions, perform this step, otherwise skip this step.
a) In the configuration interface of route constraint, right-
click the connection line between the nodes to be added
with constraint conditions, and then select Constraint
Detail from the pop-up menu. The Optional Route
Constraints dialog box pops up, as shown in Figure
58.

FIGURE 58 OPTIONAL ROUTE CONSTRAINTS DIALOG BOX
b) The Optional Route Constraints dialog box lists all

the links on the selected connection line. Click an un-
wanted link, and then click the Delete button. Only
keep the link to be configured with constraint, as shown
in Figure 59.
FIGURE 59 ADD LINK CONSTRAINT CONDITIONS
Caution:
The link has strict requirement on direction, so be care-
ful to select the link with correct direction when setting
the link constraint.
c) Refer to the following table to set the properties.
Identifies the selected NE. The setting

Resource
of route policy is applicable to this NE.
Set the restraint policy for the selected

Restraint Type NE. The options include Working Pass,
Protection Pass and Forbidden.
Restraint Select the restraint degree. The options

Degree include Restricted and Loose.
Exclude SRLG Not applicable at present.
Select this item. Otherwise, the

Is Selected constraint conditions of the link cannot
take effect.

d) Click the OK button.

iii. Add node constraint conditions. To add node constraint
conditions, perform this step, otherwise skip this step.
a) In the configuration interface of route constraint, right-
click the node icon to be added with constraint con-
ditions, and then select Constraint Detail from the
pop-up menu. The Optional Route Constraints di-
alog box pops up, as shown in Figure 60.
FIGURE 60 ADD NODE CONSTRAINT CONDITIONS
b) For the detailed configuration, refer to the "Add link

constraint conditions" step.
c) Click the OK button.
4. Configure Route Policy.
i. To add the route policy, click the Route Policy tab to enter
the configuration interface.

ii. Create Priority: Set the priority of optimizing route policy.

The options are 1~8.
iii. For the detailed configuration of other parameters, refer
to the configuration steps of "Additional Route Strategy" in
the "Creating Calls" section.
Note:
To optimize a connection in a 1+1 SNCP call, the connection
to be optimized and its peer connection (for example, the peer
connection of the working connection is the protection con-
nection) must satisfy the independence principles in the basic
route policy; The connection to be optimized and the detached
connection must satisfy the independence principles in the ad-
ditional route policy.
When the corresponding independence policy is not specified,
the control plane will try its best to satisfy the independence
principles if the network resource is sufficient.
END OF STEPS
Result The control plane automatically creates call routes again according
to the configured route optimization policy.

This page is intentionally blank.

List of Figure
Figure 1 TE Link Topology of ASON ....................................... 2

Figure 2 ASON Management Menu ........................................ 2
Figure 3 ASON Node Dialog Box ........................................... 4
Figure 4 Overhead Configuration .......................................... 5
Figure 5 INNI Management Dialog Box .................................. 8
Figure 6 No Optical Connection between NE125 and NE20 ......12
Figure 7 Configuring Remote NE125 of NE20 with Auto
Discovery Mode .................................................12
Figure 8 Configuring Remote NE20 of NE125 with Auto
Discovery Mode .................................................12
Figure 9 Querying TE link of NE125 ......................................13
Figure 10 Querying Network Topology ..................................13
Figure 11 In-Band Control Interface Configuration .................14
Figure 12 Out-of-Band Control Interface Configuration ...........15
Figure 13 Out-of-Band Neighbor Configuration ......................15
Figure 14 Weight Configuration of TE Link .............................17
Figure 15 SRLG Configuration of TE Link ...............................18
Figure 16 ControlPlane Run Topo dialog box ..........................19
Figure 17 ControlPlane Timeslot Cross Dialog Box ..................20
Figure 18 Network with an MS Link and an MS Ring ...............22
Figure 19 Configuration Flowchart........................................23
Figure 20 Create Protection Group Dialog Box (1) ..................23
Figure 24 APS IDs of Nodes in Two-Fiber Bidirectional MS
Shared Protection Ring .......................................26
Figure 25 CREATE PROTECTION GROUP DIALOG BOX
1 (FOR MS SHARED PROTECTION RING
CONFIGURATION)..............................................26
Figure 26 CREATE PROTECTION GROUP DIALOG BOX
2 (FOR MS SHARED PROTECTION RING
CONFIGURATION)..............................................27

Figure 27 Create Protection Group Dialog Box 3 (for MS

Shared Protection Ring Configuration) ..................27
Figure 28 Create Protection Group Dialog Box 4 (for MS
Shared Protection Ring Configuration) ..................27
Figure 29 Overhead Config Dialog Box..................................28
Figure 30 INNI Management Dialog Box - NNI Trans...............30
Figure 31 INNI Management Dialog Box - iNNI Ctrl ................31
Figure 32 Call Management.................................................34
Figure 33 SNC Information .................................................35
Figure 34 Creating a Call ....................................................37
Figure 35 Setting Basic property..........................................38
Figure 36 Creating a Call: Selecting A End NE .......................39
Figure 37 Creating a Call: Adding A End Board ......................40
Figure 38 Creating a Call: Adding A End Port.........................40
Figure 39 Creating a Call: Adding A End Timeslot ..................41
Figure 40 Call Setup: Call ..................................................42
Figure 41 Call Setup: Reverse .............................................43
Figure 42 Call Setup: Protection ..........................................46
Figure 43 Call Setup: Route Strategy ...................................47
Figure 44 Call Setup: Limit Information ................................50
Figure 45 Call Setup: Included and Excluded Limits ..............52
Figure 46 Call Setup: Route Limit Direction Configuration .......53
Figure 47 Timeslot Configuration of Service on Tunnel ............54
Figure 48 Finished Interface of Tunnel Creation......................55
Figure 49 1:N Protection Group Management Interface ...........55
Figure 50 Create 1:N Protection Group .................................56
Figure 51 Protection Group Info Tab .....................................57
Figure 52 Finished Configuration Figure of Working Service
Info ................................................................58
Figure 53 Finished Configuration Figure of Protection Service
Info ................................................................58
Figure 54 Service Startup/Stop ...........................................62
Figure 55 Manual Call Reversion ..........................................63
Figure 56 Restoring Call Activation/Deactivation ....................64
Figure 57 Modify Init Link to Work .......................................65
Figure 58 Optional Route Constraints Dialog Box....................67
Figure 59 Add Link Constraint Conditions ..............................67
Figure 60 Add Node Constraint Conditions.............................68

List of Table
Table 1 Correspondence Table of Transfer Ports ...................... 9

NetNumen T31 (V1 (1) .10R2) Network Element Management System Operation Manual (ASON NE Volume)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetNumen T31 (V1 (1) .10R2) Network Element Management System Operation Manual (ASON NE Volume)

Uploaded by

Copyright:

Available Formats

NetNumen T31

Network Element Management System

Copyright © 2006 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision No. Revision Data Revision Reason

Serial Number: sjzl20099547

Confidential and Proprietary Information of ZTE CORPORATION I

Configuring Control Plane 1:N Protection Groups................55

II Confidential and Proprietary Information of ZTE CORPORATION

Purpose of This This manual is applicable to NetNumen T31 (V1.10R2) Network

Manual Name Function

NetNumen T31 (V1.10R2) Describes the installation

NetNumen T31 (V1.10R2) Describes T31 basic knowledge,

Chapter 1 Configuring and Describes the configuration

Chapter 2 Configuring and Describes the steps of configuring

Intended Readers This manual applies to the following engineers:

Confidential and Proprietary Information of ZTE CORPORATION I

Click Refers to clicking the primary

Double-click Refers to quickly clicking the

Right-click Refers to clicking the secondary

Drag Refers to pressing and holding a

� Caution: Reminds users to be cautious in an opera-

� Note: Provides additional information about a certain

� Tip: Indicates a suggestion or hint to make things

V1.10R2 20091115-R1.0 Applicable to

II Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 1

FIGURE 1 TE LINK TOPOLOGY OF ASON

In the NetNumen T31 operation window, double-click the Topol-

FIGURE 2 ASON MANAGEMENT MENU

2 Confidential and Proprietary Information of ZTE CORPORATION

The meanings of the submenus shown in Figure 2 are as follows:

Configuring ASON Node

Confidential and Proprietary Information of ZTE CORPORATION 3

Steps 1. In the T31 Topology Management view, select an ASON NE.

FIGURE 3 ASON NODE DIALOG BOX

3. Double-click a property value to modify it. The property values

Has the same format as the IP address

The recovery time of graceful restart (in

The waiting time from graceful deletion

4. After configuration, click the Apply button.

4 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 4 OVERHEAD CONFIGURATION

3. Click the Add button to add an overhead configuration item.

Configuration Select the optical line board to be

Select the optical line board to be

Select the physical port of the optical line

Set the location of the overhead insertion.

Section or Channel Set the section or channel type that the J0

After selecting the section or channel type,

Confidential and Proprietary Information of ZTE CORPORATION 5

Row No. and Select the configured overhead. Select

It indicates the automatic discovery value

Configure the send value of the J0

It is used to obtain the peer port connected

5. After configuration, click the Apply button.

6 Confidential and Proprietary Information of ZTE CORPORATION

Steps 1. In the NetNumen T31 Topology Management view, select an

6. Configure the DCC/ECC usage mode of the current board and

It identifies the port of the optical line board. It

Configure the DCC/ECC usage mode at the

Configure the DCC/ECC usage mode at the

Confidential and Proprietary Information of ZTE CORPORATION 7