00438451-Configuration Guide (V100R003 - 02) Jipe

OptiX OSN 2000 Enhanced STM-1/STM-4/STM-16 Multi-Service
Optical Transmission System

V100R003
Configuration Guide
Issue 02
Date 2008-10-15
Part Number 00438451
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

OptiX OSN 2000 Enhanced STM-1/STM-4/STM-16 Multi-
Service Optical Transmission System
Configuration Guide Contents
Contents
About This Document.....................................................................................................................1

1 Starting the T2000.......................................................................................................................1-1
1.1 Starting or Shutting Down the T2000.............................................................................................................1-2
1.1.1 Starting the Computer............................................................................................................................1-3
1.1.2 Starting the T2000 Server......................................................................................................................1-3
1.1.3 Viewing the T2000 Process Status.........................................................................................................1-4
1.1.4 Logging in to the T2000 Client..............................................................................................................1-4
1.1.5 Exiting a T2000 Client...........................................................................................................................1-5
1.1.6 Shutting Down the T2000 Server...........................................................................................................1-6
1.1.7 Shutting Down the Computer.................................................................................................................1-6
1.2 Entering the T2000 Common Views...............................................................................................................1-7
1.2.1 Opening the Main Topology..................................................................................................................1-8
1.2.2 Opening the NE Explorer.......................................................................................................................1-8
1.2.3 Opening the Clock View........................................................................................................................1-8
2 Configuring SDH/PDH Services.............................................................................................2-1

2.1 Engineering Requirements..............................................................................................................................2-4
2.2 Engineering Planning......................................................................................................................................2-5
2.2.1 Networking Diagram..............................................................................................................................2-5
2.2.2 IP Address Allocation Diagram.............................................................................................................2-6
2.2.3 Board Information of Each NE..............................................................................................................2-7
2.2.4 Fiber/Cable Connection Table...............................................................................................................2-9
2.2.5 Timeslot Allocation Diagram.................................................................................................................2-9
2.2.6 Board Level Protection.........................................................................................................................2-10
2.2.7 Clock Tracing Diagram........................................................................................................................2-11
2.2.8 Orderwire Diagram..............................................................................................................................2-12
2.3 Engineering Preparation................................................................................................................................2-12
2.3.1 NE Side................................................................................................................................................2-12
2.3.2 T2000 Side...........................................................................................................................................2-13
2.3.3 Document.............................................................................................................................................2-13
2.4 Configuration Process...................................................................................................................................2-13
2.5 Logging In to the T2000................................................................................................................................2-14
2.6 Creating a Topology......................................................................................................................................2-15
Issue 02 (2008-10-15) Huawei Proprietary and Confidential i

Contents Configuration Guide
2.6.1 Creating a Gateway NE: NE1..............................................................................................................2-16

2.6.2 Creating Non-Gateway NEs: NE2–NE5..............................................................................................2-16
2.7 Configuring Communication.........................................................................................................................2-17
2.8 Creating an NE User.....................................................................................................................................2-18
2.9 Logging In to an NE......................................................................................................................................2-20
2.10 Creating a Board..........................................................................................................................................2-21
2.10.1 Adding a Board in the Configuration Wizard....................................................................................2-22
2.10.2 Adding a Board in the NE panel Manually........................................................................................2-23
2.11 Creating Fibers............................................................................................................................................2-24
2.11.1 Creating Fibers Manually...................................................................................................................2-24
2.11.2 Creating Fibers Automatically...........................................................................................................2-25
2.12 Creating a Topology Subnet........................................................................................................................2-26
2.13 Configuring Protection................................................................................................................................2-26
2.13.1 Creating a Two-Fiber Bidirectional MSP Ring..................................................................................2-27
2.13.2 Creating a 1+1 Linear MSP Chain.....................................................................................................2-27
2.13.3 Configuring TPS Protection...............................................................................................................2-28
2.14 Configuring the Clock.................................................................................................................................2-29
2.14.1 Configuring the Clock Source Priority Table....................................................................................2-30
2.14.2 Configuring a Clock Subnet...............................................................................................................2-31
2.15 Configuring SDH/PDH Services by Using the Trail Function...................................................................2-32
2.15.1 Creating a VC-4 Server Trail.............................................................................................................2-33
2.15.2 Creating a VC-12 Trail.......................................................................................................................2-34
2.16 Configuring SDH/PDH Services by Using the Per-NE Configuration Function........................................2-36
2.16.1 Creating Services on NE1..................................................................................................................2-37
2.17 Configuring Parameters of SDH/PDH Boards............................................................................................2-44
2.18 Configuring Overhead Bytes.......................................................................................................................2-45
2.18.1 Configuring the RS Overhead J0.......................................................................................................2-45
2.18.2 Configuring the Tracing Byte J1........................................................................................................2-46
2.18.3 Configuring the Signal Flag Byte C2.................................................................................................2-47
2.19 Configuring the Orderwire..........................................................................................................................2-48
2.19.1 Configuring the Orderwire of NE1–NE3...........................................................................................2-48
2.19.2 Configuring the Orderwire of NE4....................................................................................................2-49
2.19.3 Configuring the Orderwire of NE5....................................................................................................2-50
2.20 Enabling/Disabling Performance Monitoring.............................................................................................2-50
2.21 Setting Alarm Parameters............................................................................................................................2-52
2.22 Configuring Automatic Laser Shutdown....................................................................................................2-53
2.23 Backing Up the NE Configuration Data.....................................................................................................2-54
2.24 Backing Up the T2000 Configuration Data................................................................................................2-55
ii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

2.24.1 Immediate Backup..............................................................................................................................2-55

2.24.2 Periodic Backup.................................................................................................................................2-56
3 Configuring Services in Different Protection Schemes.....................................................3-1

3.1 Networking Diagram.......................................................................................................................................3-2
3.2 Information of Boards on Each NE.................................................................................................................3-2
3.3 SNCP Ring with Non-Protection Chains........................................................................................................3-4
3.3.1 Configuring a Non-Protection Chain.....................................................................................................3-4
3.3.2 Configuring SNCP Services...................................................................................................................3-5
3.4 SNCP Ring with 1:1 Linear MSP Chains.......................................................................................................3-9
3.4.1 Configuring a 1:1 Linear MSP Subnet...................................................................................................3-9
3.4.2 Configuring SNCP Services.................................................................................................................3-10
4 Configuring Ethernet Services................................................................................................4-1

4.1 Configuring Transparent Transmission EPL Services by Using the Per-NE Configuration Function ..........4-4
4.1.1 Engineering Requirements.....................................................................................................................4-4
4.1.2 Engineering Planning.............................................................................................................................4-5
4.1.3 Configuration Process............................................................................................................................4-8
4.1.4 Creating a Board.....................................................................................................................................4-8
4.1.5 Configuring the Data of NE1.................................................................................................................4-9
4.1.6 Configuring the Data of NE2...............................................................................................................4-14
4.2 Configuring Transparent Transmission EPL Services by Using the Trail Function.....................................4-17
4.2.1 Engineering Requirements...................................................................................................................4-18
4.2.2 Engineering Planning...........................................................................................................................4-18
4.2.3 Configuration Process..........................................................................................................................4-21
4.2.4 Creating a Trunk Link..........................................................................................................................4-22
4.2.5 Creating an EPL Trail..........................................................................................................................4-24
4.3 Configuring PORT-Shared EVPL Services by Using the Per-NE Configuration Function.........................4-26
4.4 Configuring PORT-Shared EVPL Services by Using the Trail Function.....................................................4-41
4.5 Configuring VCTRUNK-Shared EVPL Services by Using the Per-NE Configuration Function................4-48
Issue 02 (2008-10-15) Huawei Proprietary and Confidential iii


4.6 Configuring VCTRUNK-Shared EVPL Services by Using the Trail Function............................................4-59
4.7 Configuring the Ingress/Egress EVPL Services by Using the Per-NE Configuration Function...................4-65
4.8 Configuring the Transit EVPL Service by Using the Per-NE Configuration Function................................4-74
4.9 Configuring the 802.1d Bridge-Based EPLAN Service by Using the Per-NE Configuration Function.......4-86
4.10 Configuring the 802.1q Bridge-Based EVPLAN Service by Using the Per-NE Configuration Function
.............................................................................................................................................................................4-98
4.10.1 Engineering Requirements.................................................................................................................4-98
4.10.2 Engineering Planning.........................................................................................................................4-98
4.10.3 Configuration Process......................................................................................................................4-103
4.10.4 Configuring the Data of NE3...........................................................................................................4-104
4.11 Configuring the 802.1q Bridge-Based EVPLAN Service by Using the Trail Function...........................4-109
4.11.1 Engineering Requirements...............................................................................................................4-109
4.11.2 Engineering Planning.......................................................................................................................4-110
4.11.4 Creating a Trunk Link......................................................................................................................4-115
iv Huawei Proprietary and Confidential Issue 02 (2008-10-15)

4.11.5 Creating an EVPLAN Trail..............................................................................................................4-116

4.12 Configuring the MPLS-Based EVPLAN Service by Using the Per-NE Configuration Function............4-117
4.12.1 Engineering Requirements...............................................................................................................4-118
4.12.2 Engineering Planning.......................................................................................................................4-118
5 Configuring Auxiliary Services...............................................................................................5-1

5.1 Configuring Broadcast Services......................................................................................................................5-2
5.2 Configuring F1 Data Services.........................................................................................................................5-4
6 Configuring the DCN................................................................................................................6-1

6.1 Overview.........................................................................................................................................................6-3
6.1.1 Background for the Generation of the DCN..........................................................................................6-3
6.1.2 DCN Solutions.......................................................................................................................................6-4
6.2 HWECC Communication................................................................................................................................6-4
6.2.1 Functions and Features...........................................................................................................................6-4
6.2.2 Application.............................................................................................................................................6-5
6.3 Configuring HWECC Communication...........................................................................................................6-6
6.3.1 Creating a Gateway NE..........................................................................................................................6-7
6.3.2 Creating a Non-Gateway NE..................................................................................................................6-7
6.3.3 Setting the NE ID...................................................................................................................................6-7
6.3.4 Configuring the Extended ECC..............................................................................................................6-8
6.3.5 Querying the ECC Route......................................................................................................................6-10
6.3.6 Configuring the DCC Rate...................................................................................................................6-10
6.3.7 Configuring DCC Transparent Transmission......................................................................................6-12
6.4 IP over DCC..................................................................................................................................................6-14
6.4.1 Basic Concepts.....................................................................................................................................6-14
6.4.2 Functions and Features.........................................................................................................................6-15
6.4.3 Application...........................................................................................................................................6-15
6.4.4 Configuration Requirements................................................................................................................6-18
6.5 Configuring IP over DCC Communication...................................................................................................6-19
6.5.1 Creating a Gateway NE........................................................................................................................6-19
6.5.2 Setting NE Communication Parameters...............................................................................................6-19
6.5.3 Configuring Static Routes....................................................................................................................6-20
Issue 02 (2008-10-15) Huawei Proprietary and Confidential v

6.5.4 Allocating DCC Resources..................................................................................................................6-21

6.5.5 Querying Communication Status.........................................................................................................6-22
6.5.6 Querying the OSPF Protocol Status.....................................................................................................6-22
6.6 OSI over DCC...............................................................................................................................................6-22
6.6.1 Basic Concepts.....................................................................................................................................6-23
6.6.2 Functions and Features.........................................................................................................................6-24
6.6.3 Application...........................................................................................................................................6-24
6.7 Configuring the OSI over DCC Communication..........................................................................................6-26
6.7.1 Creating a Gateway NE........................................................................................................................6-27
6.7.2 Setting the NE ID.................................................................................................................................6-27
6.7.3 Setting NE Communication Parameter................................................................................................6-27
6.7.4 Setting the NSAP Address for an NE...................................................................................................6-28
6.7.5 Configuring the Node Type for an NE.................................................................................................6-30
6.7.6 Configuring Optical Port Protocol Stake and LAPD Role...................................................................6-31
6.7.7 Querying Route Information................................................................................................................6-33
6.7.8 Creating an OSI GNE...........................................................................................................................6-33
7 Configuring the STP or RSTP..................................................................................................7-1

7.1 Overview.........................................................................................................................................................7-2
7.1.1 Background for the Generation of the STP or RSTP.............................................................................7-2
7.1.2 Basic Knowledge about the STP or RSTP ............................................................................................7-2
7.1.3 STP/RSTP Port State Transition............................................................................................................7-3
7.3 Engineering Planning......................................................................................................................................7-4
7.3.1 Networking Diagram..............................................................................................................................7-4
7.3.2 Board Information of Each NE.............................................................................................................. 7-5
7.3.3 Service Configuration Diagram of Each NE..........................................................................................7-5
7.4 Configuration Process.....................................................................................................................................7-8
7.4.1 Creating a Board.....................................................................................................................................7-9
7.4.2 Configuring the Ethernet Ports of NE1................................................................................................7-10
7.4.3 Configuring the Bound Paths of NE1..................................................................................................7-12
7.4.4 Creating the Ethernet LAN Service of NE1.........................................................................................7-12
7.4.5 Configuring the VLAN Forwarding Filtering Table............................................................................7-13
7.4.6 Configuring Cross-Connections from Ethernet boards to SDH Line Boards on NE1.........................7-14
7.4.7 Configuring the Data of NE2 and NE3................................................................................................7-15
7.4.8 Configuring the STP/RSTP..................................................................................................................7-15
7.4.9 Querying STP/RSTP Running Information.........................................................................................7-18
8 Configuring ETH-OAM............................................................................................................8-1
8.1 Overview.........................................................................................................................................................8-3
8.3 Configuration Process.....................................................................................................................................8-5
8.4 Creating MPs...................................................................................................................................................8-5
8.5 Activating the CC............................................................................................................................................8-6
vi Huawei Proprietary and Confidential Issue 02 (2008-10-15)

8.6 Enabling the LB..............................................................................................................................................8-7

8.7 Starting the LT................................................................................................................................................8-8
9 Configuring the LPT..................................................................................................................9-1

9.1 Overview.........................................................................................................................................................9-2
9.2 Application......................................................................................................................................................9-2
9.2.1 Application of the P2P LPT...................................................................................................................9-2
9.2.2 Application of the P2MP LPT................................................................................................................9-4
9.3 Configuring the Point-to-Point LPT Function................................................................................................9-8
9.4 Configuring the P2MP LPT Function...........................................................................................................9-10
10 Configuring the PRBS...........................................................................................................10-1

10.1 Overview.....................................................................................................................................................10-2
10.1.1 PRBS Function...................................................................................................................................10-2
10.1.2 Boards with the PRBS Function.........................................................................................................10-2
10.2 Application..................................................................................................................................................10-2
10.3 Lower Order PRBS Function......................................................................................................................10-3
11 Configuring the Ethernet Test Frame.................................................................................11-1

11.1 Overview.....................................................................................................................................................11-2
11.2 Application..................................................................................................................................................11-2
11.3 Configuring the Ethernet Test Frame..........................................................................................................11-3
12 Configuring the LCAS..........................................................................................................12-1

12.1 Overview.....................................................................................................................................................12-2
12.2 Application..................................................................................................................................................12-2
12.3 Configuring the LCAS................................................................................................................................12-4
13 Configuring Transmux..........................................................................................................13-1
13.1 Overview.....................................................................................................................................................13-2
13.2 Functions and Features................................................................................................................................13-2
13.3 Application..................................................................................................................................................13-3
13.4 Configuring the Working Mode of a Board................................................................................................13-5
13.5 Configuring the Transmux Mode................................................................................................................13-6
13.6 Configuring the Transmux Server Mode ...................................................................................................13-8
A Glossary.....................................................................................................................................A-1
B Acronyms and Abbreviations.................................................................................................B-1
Index.................................................................................................................................................i-1
Issue 02 (2008-10-15) Huawei Proprietary and Confidential vii

Configuration Guide Figures
Figures
Figure 2-1 Geographic position of each node and available optical fiber cables.................................................2-4
Figure 2-2 Networking diagram...........................................................................................................................2-6
Figure 2-3 IP address allocation diagram.............................................................................................................2-7
Figure 2-4 Board layout of NE1...........................................................................................................................2-7
Figure 2-5 Board layout of NE2 and NE3............................................................................................................2-8
Figure 2-8 Timeslot allocation diagram.............................................................................................................2-10
Figure 2-9 Clock tracing diagram......................................................................................................................2-11
Figure 2-10 Orderwire diagram..........................................................................................................................2-12
Figure 3-2 Timeslot allocation diagram...............................................................................................................3-2
Figure 3-4 Board layout of NE2 and NE3............................................................................................................3-3
Figure 4-1 Ethernet service networking and port allocation................................................................................4-5
Figure 4-4 Service configuration diagram............................................................................................................4-6
Figure 4-5 SDH timeslot allocation for Ethernet services ...................................................................................4-7
Figure 4-6 Ethernet service networking and port allocation..............................................................................4-19
Figure 4-7 Board layout of NE1.........................................................................................................................4-19
Figure 4-8 Board layout of NE3.........................................................................................................................4-20
Figure 4-9 Service configuration diagram..........................................................................................................4-20
Figure 4-10 SDH timeslot allocation for Ethernet services ...............................................................................4-21
Figure 4-11 Ethernet service networking and port allocation............................................................................4-28
Figure 4-12 Board layout of NE1.......................................................................................................................4-28
Figure 4-14 Service configuration diagram........................................................................................................4-29
Figure 4-15 SDH timeslot allocation diagram...................................................................................................4-30
Issue 02 (2008-10-15) Huawei Proprietary and Confidential ix

Figures Configuration Guide

Figure 4-20 SDH timeslot allocation diagram...................................................................................................4-45
Figure 4-25 SDH timeslot allocation for Ethernet services................................................................................4-52
Figure 4-38 Board layout of NE2 and NE3........................................................................................................4-77
Figure 4-42 Board layout of NE2 and NE3........................................................................................................4-88
Figure 4-47 Board layout of NE 2 and NE3.......................................................................................................4-99
Figure 4-48 Board layout of NE4.....................................................................................................................4-100
Figure 4-49 Service configuration diagram......................................................................................................4-100
Figure 4-50 SDH timeslot allocation for Ethernet services..............................................................................4-103
Figure 4-51 Ethernet service networking and port allocation..........................................................................4-110
Figure 4-52 Board layout of NE 2 and NE3.....................................................................................................4-111
Figure 4-54 Service configuration diagram......................................................................................................4-112
Figure 4-56 Ethernet service networking and port allocation..........................................................................4-118
Figure 4-58 Board layout of NE2 and NE3......................................................................................................4-119
Figure 4-59 Service configuration ...................................................................................................................4-120
x Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Configuration Guide Figures
Figure 4-60 NE Service Configuration Diagram..............................................................................................4-120

Figure 6-1 Positions of the D bytes in the SDH overhead................................................................................... 6-3
Figure 6-2 Networking that involves only Huawei equipment............................................................................6-5
Figure 6-3 Networking that involves Huawei equipment and third-party equipment..........................................6-6
Figure 6-4 Application Ι.....................................................................................................................................6-16
Figure 6-5 Application II....................................................................................................................................6-16
Figure 6-6 Application III..................................................................................................................................6-17
Figure 6-7 Application IV..................................................................................................................................6-18
Figure 6-8 Format of a simple NSAP address....................................................................................................6-23
Figure 6-9 Format of a complicated NSAP address...........................................................................................6-23
Figure 6-10 Huawei equipment at the edge of the network...............................................................................6-25
Figure 6-11 Huawei equipment at the core of the network................................................................................6-26
Figure 7-1 STP port state transition..................................................................................................................... 7-3
Figure 7-2 Ethernet service networking and port allocation................................................................................7-5
Figure 7-3 Board layout of NE1, NE2, and NE3................................................................................................. 7-5
Figure 7-4 Service configuration diagram............................................................................................................7-6
Figure 8-1 Application example of the maintenance point..................................................................................8-3
Figure 10-1 Signal flow for the lower order PRBS test.....................................................................................10-3
Figure 10-2 Lower order PRBS test in the tributary direction...........................................................................10-3
Figure 11-1 Application of the test frame..........................................................................................................11-3
Figure 12-1 Dynamic bandwidth adjustment by using the LCAS.....................................................................12-3
Figure 12-2 Virtual concatenation group protection realized by using the LCAS.............................................12-3
Figure 13-1 E1 Transmux...................................................................................................................................13-4
Figure 13-2 E1 Transmux Server.......................................................................................................................13-4
Figure 13-3 Networking diagram in the Transmux Server mode.......................................................................13-9
Issue 02 (2008-10-15) Huawei Proprietary and Confidential xi

Configuration Guide Tables
Tables
Table 2-1 Service requirements among the nodes................................................................................................2-4

Table 2-2 Mapping relation between the place codes and the NEs......................................................................2-6
Table 2-3 Fiber/Cable connection between the NEs............................................................................................2-9
Table 2-4 Board level protection information....................................................................................................2-11
Table 2-5 Procedures for configuring SDH/PDH services.................................................................................2-13
Table 2-6 NE user level and authority description.............................................................................................2-18
Table 2-7 NE user flag........................................................................................................................................2-19
Table 2-8 Parameters for configuring the ALS..................................................................................................2-54
Table 3-1 Fiber/Cable connection between NE4 and NE5...................................................................................3-9
Table 4-1 Mapping relation between Ethernet boards and Ethernet services......................................................4-1
Table 4-2 Ethernet service connection.................................................................................................................4-7
Table 4-3 Process of point-to-point transparent transmission EPL service configuration...................................4-8
Table 4-4 Parameters of basic attributes.............................................................................................................4-12
Table 4-5 Parameters for configuring the bound paths......................................................................................4-13
Table 4-6 Ethernet service connection...............................................................................................................4-20
Table 4-7 Process of configuring point-to-point transparent transmission EPL services (by trail)...................4-22
Table 4-8 Parameters for creating a trunk link...................................................................................................4-24
Table 4-9 Parameters for creating an EPL trail..................................................................................................4-26
Table 4-10 Ethernet service connection.............................................................................................................4-29
Table 4-11 Process of configuring the PORT-shared EPL service....................................................................4-31
Table 4-12 Parameters for tag attributes.............................................................................................................4-36
Table 4-13 Parameters for configuring the EPL service (by station).................................................................4-37
Table 4-15 Process of configuring the PORT-shared EVPL services by using the trail function......................4-46
Table 4-17 Flow for configuring the VCTRUNK-shared EVPL service...........................................................4-53
Table 4-18 CAR parameters...............................................................................................................................4-58
Table 4-19 Flow configuration parameters........................................................................................................4-58
Table 4-21 Flow of configuring the VCTRUNK-shared EVPL service (by trail).............................................4-63
Table 4-23 Process of configuring the ingress/egress service............................................................................4-70
Issue 02 (2008-10-15) Huawei Proprietary and Confidential xiii

Tables Configuration Guide
Table 4-25 Process of configuring the transit EVPL service.............................................................................4-79

Table 4-26 Ethernet service connection............................................................................................................. 4-89
Table 4-27 Process of configuring the EPLAN service..................................................................................... 4-90
Table 4-28 Parameters for configuring the Ethernet LAN service.....................................................................4-93
Table 4-29 Connection relation of the Ethernet service of company F............................................................4-101
Table 4-30 Connection relation of the Ethernet service of company G...........................................................4-101
Table 4-31 VLAN filtering table......................................................................................................................4-102
Table 4-32 Process of configuring the EVPLAN service.................................................................................4-104
Table 4-33 Parameters for configuring the VLAN filtering table....................................................................4-108
Table 4-34 Connection relation of the Ethernet service of company F............................................................4-112
Table 4-35 Connection relation of the Ethernet service of company G...........................................................4-113
Table 4-37 Process of configuring the EPLAN service by using the trail function.........................................4-115
Table 4-38 Ethernet service connection...........................................................................................................4-121
Table 4-40 Process of configuring the EVPLAN service.................................................................................4-123
Table 5-1 NE parameters......................................................................................................................................5-3
Table 5-2 NE parameters......................................................................................................................................5-5
Table 6-1 NE attributes.........................................................................................................................................6-8
Table 6-2 Parameters for configuring the extended ECC.....................................................................................6-9
Table 6-3 DCC channel modes of the OptiX OSN 2000................................................................................... 6-11
Table 6-4 Parameters for configuring the DCC rate...........................................................................................6-12
Table 6-5 Parameters for configuring the DCC transparent transmission..........................................................6-13
Table 6-6 Communication parameters............................................................................................................... 6-20
Table 6-7 Parameters for configuring the GNE attributes..................................................................................6-29
Table 6-8 Network-layer parameters..................................................................................................................6-31
Table 6-9 Parameters for setting the optical port protocol and LAPD role........................................................6-32
Table 7-1 Ethernet service connection table 1......................................................................................................7-6
Table 7-2 Ethernet service connection table 2......................................................................................................7-7
Table 7-3 Forwarding filtering table....................................................................................................................7-8
Table 7-4 Bridge priority table.............................................................................................................................7-8
Table 7-5 Process of configuring the STP/RSTP.................................................................................................7-8
Table 7-6 Parameters for setting the basic attributes of Ethernet ports..............................................................7-11
Table 7-7 Point-to-point attributes..................................................................................................................... 7-11
Table 7-8 Parameters for configuring the Ethernet LAN service.......................................................................7-13
Table 7-9 Bridge parameters.............................................................................................................................. 7-17
Table 7-10 Parameter description.......................................................................................................................7-17
Table 7-11 Status of the internal ports ...............................................................................................................7-19
Table 8-1 Fiber/Cable connection table................................................................................................................8-4
Table 8-2 Process of configuring the ETH-OAM................................................................................................8-5
Table 8-3 Recommended average CC period.......................................................................................................8-7
Table 9-1 Parameters for the P2P LPT.................................................................................................................9-9
xiv Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Configuration Guide Tables
Table 9-2 Parameters for the P2MP LPT........................................................................................................... 9-11

Table 10-1 Parameters of lower order PRBS configuration...............................................................................10-5
Table 11-1 Parameters of the test frame.............................................................................................................11-4
Table 12-1 LCAS parameters.............................................................................................................................12-5
Table 13-1 Working mode of the PLM..............................................................................................................13-2
Table 13-2 Parameters for configuring the service mode...................................................................................13-6
Table 13-3 PLM in the MUX mode...................................................................................................................13-7
Table 13-4 Service requirements in the MUX mode..........................................................................................13-7
Table 13-5 PLM in the Transmux Server mode.................................................................................................13-8
Table 13-6 Service requirements in the Transmux Server mode.......................................................................13-9
Table 13-7 Services configured in the Transmux Server mode.........................................................................13-9
Issue 02 (2008-10-15) Huawei Proprietary and Confidential xv

Configuration Guide About This Document
About This Document
Purpose
This document provides an overview of the configuration, describes the engineering
requirements, engineering planning, and configuration process.
This document describes how to configure services, such as SDH services and Ethernet services
on the T2000.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 2000 V100R003
OptiX iManager T2000 V200R007C01
Intended Audience
This document is intended for the following audience:
l Data configuration engineers

l System maintenance engineers
l Installation and commissioning engineers
Organization
The following table lists the contents of this document.
Chapter Description
1 Starting the T2000 Describes the basic operations to the quick start of the
T2000.
Issue 02 (2008-10-15) Huawei Proprietary and Confidential 1

About This Document Configuration Guide
Chapter Description
2 Configuring SDH/PDH Describes how to configure NEs, boards, cables/fibers,

Services protection subnet, SDH services, clock, and orderwire on
the T2000.
3 Configuring Services in Describes the service configuration methods in various

Different Protection Schemes protection schemes.
4 Configuring Ethernet Describes how to configure EPL, EVPL, EPLAN, and

Services EVPLAN services by using the per-NE configuration
function or the trail function on the T2000.
5 Configuring Auxiliary Describes how to configure broadcast data services and F1

Services interface services on the T2000.
6 Configuring the DCN Describes how to configure the data communication

network (DCN) on the T2000.
7 Configuring the STP or Describes how to configure the spanning tree protocol
RSTP (STP) and rapid spanning tree protocol (RSPT) on the
T2000.
8 Configuring ETH-OAM Describes how to configure the operation, administration,

and management (OAM) feature on the T2000.
9 Configuring the LPT Describes how to configure the LPT feature on the T2000.
10 Configuring the PRBS Describes how to configure the pseudorandom binary

sequence (PRBS) function on the T2000.
11 Configuring the Ethernet Describes how to configure the Ethernet test frames on the
Test Frame T2000.
12 Configuring the LCAS Describes how to configure the link capacity adjustment
scheme (LCAS) feature on the T2000.
13 Configuring Transmux Describes how to configure the Transmux feature on the

T2000.
A Glossary Lists the terms used in this document.
B Acronyms and Lists the acronyms and abbreviations used in this document.
Abbreviations
Conventions
Symbol Conventions
The following table describes the symbols that are used in this document.
2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Symbol Description
Indicates a hazard with a high level of risk, which if not

prevented, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk, which

if not prevented, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation, which if not

prevented, could result in damage to the equipment, data loss,
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
time.
NOTE Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

About This Document Configuration Guide
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
4 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Action Description
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 02 (2008-10-15)

The updated contents are as follows.
This version fixes some known defects.
Updates in Issue 01 (2008-08-30)

Initial field trial release.

Configuration Guide 1 Starting the T2000
1 Starting the T2000
About This Chapter
The following section describes certain preparation operations that ensure a smooth and trouble-
free launch of the T2000.
1.1 Starting or Shutting Down the T2000

The T2000 uses the standard client/server architecture and multiple-user mode. Therefore, it is
recommended that you comply with the following procedures when starting or shutting down
the T2000 so that other users who are operating on the T2000 are not affected.
1.2 Entering the T2000 Common Views
The T2000 common views include Main Topology, Trail View, Clock View, and NE Explorer.
You can use these views to manage the topology, equipment, trail, and clock.
Issue 02 (2008-10-15) Huawei Proprietary and Confidential 1-1

1 Starting the T2000 Configuration Guide
1.1 Starting or Shutting Down the T2000

The T2000 uses the standard client/server architecture and multiple-user mode. Therefore, it is
recommended that you comply with the following procedures when starting or shutting down
the T2000 so that other users who are operating on the T2000 are not affected.
Context
l To start the computer and the T2000 application, do as follows:
1. Start the computer.
2. Start the T2000 server.
3. Start the T2000 client.
l To shut down the T2000 application and the computer, do as follows:
1. Exit the T2000 client.
2. Stop the T2000 server.
3. Shut down the computer.
1.1.1 Starting the Computer
To prevent damage to the computer or data loss, refer to the procedure provided to start the
computer. The startup procedures of the workstation are different from the startup procedures
of a normal PC. Follow the procedure correctly to perform the required operations.
1.1.2 Starting the T2000 Server
After starting the computer, you need to start the T2000 server. Then, you can log in to the
T2000 to manage the network.
1.1.3 Viewing the T2000 Process Status
When you fail to log in to the T2000 client or abnormally exit the T2000 client, you can use the
System Monitor to view the T2000 process status to determine whether the server is faulty.
1.1.4 Logging in to the T2000 Client
You can manage the network in the graphic user interface (GUI) only after logging in to the
T2000 client.
1.1.5 Exiting a T2000 Client
Before restarting the T2000 client or shutting down the T2000 server, you must exit the
T2000 client.
1.1.6 Shutting Down the T2000 Server
When the T2000 server is managing the system normally, do not perform this operation. In
special situations, for example, when modifying the system time of the computer where the
T2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the T2000 server.
1.1.7 Shutting Down the Computer
Generally, the computer is not shut down. In special situations, for example, if the computer
becomes faulty, shut down the computer by following the correct sequence. The shutdown
procedures of the workstation are different from the shutdown procedures of a normal PC. Follow
the procedure correctly to perform the required operations.
1-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

1.1.1 Starting the Computer

To prevent damage to the computer or data loss, refer to the procedure provided to start the
computer. The startup procedures of the workstation are different from the startup procedures
of a normal PC. Follow the procedure correctly to perform the required operations.
Prerequisite
l The T2000 must be installed correctly.
l The power cable of the workstation or of the computer, the power cable of the monitor, the
data line, and the Ethernet line must be connected correctly.
l If there is a printer, modem, or other peripherals, their power line and data line must be
connected correctly.
Background Information
The T2000 can run on the UNIX or Windows operating system. The functions are the same on
each operating system. For more information about the recommended hardware configuration,
see the OptiX iManager T2000 Product Description.
Procedure
l On UNIX
1. Power on the printer, modem, and other peripherals.
2. Power on the workstation. The Solaris starts automatically and the Prompt dialog box
is displayed.
3. Enter the Username and Password in the Login dialog box. For example, User:
t2000 (by default); Password: t2000 (by default).
4. Click OK to open the Common Desktop Environment (CDE) window.
l On Windows
1. Power on the printer, modem, and other peripherals.
2. Power on the computer. The Windows starts automatically.
3. Enter the Username and Password in the Login dialog box. For example, User:
t2000 (by default); Password: t2000 (by default).
4. Click OK to open the Windows user interface.
----End
1.1.2 Starting the T2000 Server

After starting the computer, you need to start the T2000 server. Then, you can log in to the
T2000 to manage the network.
Prerequisite
l The computer where the T2000 is installed must be started correctly.
l The operating system of the T2000 server must be running correctly.
l The T2000 license must be in the server directory.
l The SQL server must be started and must work normally.

Procedure
Step 1 Double-click the T2000Server icon on the desktop of the T2000 server.
Step 2 In the Login dialog box, enter User Name, Password and Server. For example, User Name:
admin, Password: T2000 (T2000 is the default password of the admin user.), and Server:
Local.
NOTE
Periodically change the password and keep it safely.
Step 3 Click Login to display the System Monitor window. Wait until the core processes (including
Ems Server, Schedulesrv Server, Security Server, Syslog Agent, Topo Server, WebLCT
Server, Tomcat Service, Client Upgrader, and Toolkit Server) and Database Server
Process are in the Running state. Now the T2000 server is started successfully.
Step 4 Optional: When required, you can also start the Northbound Interface processes (including
Northbound Interface Module(iPASSAgent) Process, Northbound Interface Module
(SNMP) Process, Naming Service, Notify Service, and itnotify) manually.
Step 5 Optional: If the System Monitor is started, you need to use it to restart the T2000 server when
required. Choose System > Start Server from the Main Menu of the System Monitor. When
the core processes and Database Server Process processes are in the Running state, the T2000
server is started properly.
----End
1.1.3 Viewing the T2000 Process Status

When you fail to log in to the T2000 client or abnormally exit the T2000 client, you can use the
System Monitor to view the T2000 process status to determine whether the server is faulty.
To view the status of the T2000 processes by using UNIX command line, run the following
command:
# /T2000/server/bin/showt2000server
If each process that is entered has a corresponding process ID and the specific ID does not change,
the T2000 processes are normal.
Procedure
In the System Monitor, click the Process tab. View the status of the T2000 core processes
(including Ems Server, Schedulesrv Server, Security Server, Syslog Agent, Topo Server,
WebLCT Server, Tomcat Service, Client Upgrader, and Toolkit Server), Database Server
Process, and Northbound Interface processes (including Northbound Interface Module
(iPASSAgent) Process, Northbound Interface Module(SNMP) Process, Naming Service,
Notify Service, and itnotify). If all the processes are in the Running state, the T2000 process
is normal.
----End
1.1.4 Logging in to the T2000 Client

You can manage the network in the graphic user interface (GUI) only after logging in to the
T2000 client.

Prerequisite
The T2000 server must be started correctly.
Procedure
Step 1 On the computer of the T2000 client, double-click the T2000 Client icon on the desktop.
Step 2 Enter the User Name and Password of the T2000 client. For example, User Name: admin;
Password: T2000.
NOTE
l By default, the initial user name is admin, and the password is T2000. To protect the T2000 from
unauthorized logins, you need to immediately change this password.
l The administrator needs to create new T2000 users and assign them to certain authority groups.
Step 3 Optional: Set the server parameters.
1. Click to display the Setting dialog box.

2. Click New to display another Setting dialog box.
3. In the Setting dialog box, specify the IP Address, Mode, and Server Name.
NOTE
l The IP address is the IP address used by the T2000 server.

l The Mode has two options including Common and Security (SSL). When you select the
Security (SSL) mode, the communication between the client and the server is encrypted.
l The communication mode of the client must be consistent with the communication mode of the
server. Otherwise, the client cannot log in to the server. To view the communication mode of the
server, choose System > Communication Security Setting from the Main Menu of the System
Monitor client.
l You need not enter the Port number. After the Mode is specified, the system selects a Port
number automatically.
4. Click OK to complete the process of adding a server.
5. Click OK to complete the server settings.
Step 4 Select a server and click Login to access the T2000.
----End
1.1.5 Exiting a T2000 Client

Before restarting the T2000 client or shutting down the T2000 server, you must exit the
T2000 client.
Prerequisite
The T2000 client must be started normally.
Procedure
Step 1 Choose File > Exit from the Main Menu.
Step 2 Click OK in the confirmation dialog box.

NOTE
If the layout of the view is changed and not saved, a Confirm dialog box is displayed, prompting you to
save the changes. After you click OK in the dialog box, you can automatically exit the client.
----End
1.1.6 Shutting Down the T2000 Server

When the T2000 server is managing the system normally, do not perform this operation. In
special situations, for example, when modifying the system time of the computer where the
T2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the T2000 server.
Prerequisite
All the T2000 clients connected to the T2000 server must be shut down.
Context
When performing the operations related to the database (such as initializing the T2000
database, restoring T2000 databases, and restoring T2000 MO data) or when performing the
operations related to the T2000 (such as the upgrade, installing patches, and re-installing the
T2000), you need to shut down the T2000 server first. It is recommended that you shut down
the T2000 server in the same way as you shut down the T2000 server and the System Monitor
Client.
Procedure
l Shut down the T2000 server and the System Monitor.
NOTE
After shutting down the T2000 server and the System Monitor, you can perform the operations related
to the database (such as initializing the T2000 database, restoring T2000 databases, and restoring
T2000 MO data) or can perform the operations related to the T2000 (such as the upgrade, installing
patches, and re-installing the T2000).
1. In the System Monitor, choose System > Shutdown System from the Main Menu.
l Shut down the T2000 server only.
NOTE
After shutdown, you cannot perform the operations related to the database (such as initializing the
T2000 database, restoring T2000 databases, and restoring T2000 MO data) or you cannot perform
the operations related to the T2000 (such as the upgrade, installing patches, and re-installing the
T2000).
1. In the System Monitor, choose System > Stop Server from the Main Menu.
2. Click OK in the confirmation dialog box. When all the processes are in the
Stopped status, the T2000 server is stopped normally.
----End
1.1.7 Shutting Down the Computer

Generally, the computer is not shut down. In special situations, for example, if the computer
becomes faulty, shut down the computer by following the correct sequence. The shutdown
procedures of the workstation are different from the shutdown procedures of a normal PC. Follow
the procedure correctly to perform the required operations.

Prerequisite
The T2000 server and client applications must be stopped.
Precaution
CAUTION
To prevent damage to the equipment or data loss, perform the following steps one by one to shut
down the workstation.
Procedure
l On UNIX platform
1. Enter the following commands in the terminal window, and the UNIX workstation
shuts down automatically:
% su root
Password: rootkit
# sync;sync;sync;sync;sync
# shutdown -y -g0 -i5
NOTE
l rootkit is the default password of super user root. If the password is changed, enter the
new password.
l To restart the Sun workstation, the last command should be # shutdown -y -g0 -i6.
2. Switch off the monitor and the peripheral equipment.
l On Windows platform
1. Choose Start > Shut down from the Windows desktop.
2. Choose Shut down and click OK in the dialog box. The computer shuts down
automatically.
3. Switch off the monitor and the peripheral equipment.
----End
1.2 Entering the T2000 Common Views

The T2000 common views include Main Topology, Trail View, Clock View, and NE Explorer.
You can use these views to manage the topology, equipment, trail, and clock.
1.2.1 Opening the Main Topology

After opening the Main Topology, you can manage the network topology. For example, you can
create a topology object and a subnet, and lock the position of an NE icon on the topology.
1.2.2 Opening the NE Explorer
The NE Explorer is the key interface for the T2000 to configure a single station. After opening
the NE Explorer, you can configure, manage, and maintain each NE, board, or port in a
hierarchical manner.
1.2.3 Opening the Clock View

After opening the Clock View, you can set an NE clock, query a network clock synchronization
status, or trace a clock.
1.2.1 Opening the Main Topology

After opening the Main Topology, you can manage the network topology. For example, you can
create a topology object and a subnet, and lock the position of an NE icon on the topology.
Prerequisite
You must be an NM user with "NE and network monitor" authority or higher.
Procedure
l To open the Main Topology, log in to the T2000.
l Choose Window > Main Topology from the Main Menu.
----End
1.2.2 Opening the NE Explorer

The NE Explorer is the key interface for the T2000 to configure a single station. After opening
the NE Explorer, you can configure, manage, and maintain each NE, board, or port in a
hierarchical manner.
Prerequisite
You can open a maximum of five NE Explorer windows at the same time.
Procedure
Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
----End
1.2.3 Opening the Clock View

After opening the Clock View, you can set an NE clock, query a network clock synchronization
status, or trace a clock.
Prerequisite
Procedure
Choose Configuration > Clock View from the Main Menu.
----End

Configuration Guide 2 Configuring SDH/PDH Services
2 Configuring SDH/PDH Services
About This Chapter
This topic uses an example to describe how to configure the SDH/PDH services on the T2000.
It also describes the related engineering requirements and engineering information. You can
learn how to configure SDH/PDH services and other similar services through this example.
NOTE
The screen shots contained in this manual vary with the T2000 version and NE software version. If the
versions mismatch, the screen shots may be different from the actual version.
The OptiX iManager T2000 version is V200R007C01.
The OptiX iManager T2000 is referred to as T2000 hereinafter.
2.1 Engineering Requirements

In a city, new communication lines need to be constructed among nodes A, B, C, D, and E to
form a local network.
2.2 Engineering Planning
Based on the requirements, the engineering design department conducts planning and outputs
the detailed engineering information.
2.3 Engineering Preparation
Check the following items before configuring services on the T2000.
2.4 Configuration Process
This topic describes how to configure SDH/PDH services.
2.5 Logging In to the T2000
The T2000 provides all the NE-layer management functions, including the fault management,
performance management, configuration management, security management, communication
management, topology management, and system management. In addition, the T2000 provides
certain network-layer management functions. This topic describes how to log in to the T2000.
2.6 Creating a Topology
This topic describes how to create, display, and manage an NE on the T2000.
2.7 Configuring Communication
This topic describes how to set the Ethernet access function of an NE on the T2000. By default,
an NE supports access of the T2000 through Ethernet.

2 Configuring SDH/PDH Services Configuration Guide
2.8 Creating an NE User

This topic describes how to create an NE user on the T2000. The NE user can specify the authority
of the NE operator, thus facilitating the control of the NE access and configuration.
2.9 Logging In to an NE
This topic describes how to switch the NE users on the T2000. Different clients cannot use the
same NE user ID to log in to or manage an NE. Otherwise, the client automatically logs out of
the NE when another client logs in to the NE.
2.10 Creating a Board
This topic describes how to create a board in the configuration wizard or the NE panel diagram.
Before you configure services on an NE and to manage an NE, create the boards.
2.11 Creating Fibers
This topic describes how to create fibers on the T2000. After fibers are created, they are displayed
on the T2000.
2.12 Creating a Topology Subnet
This topic describes how to create a topology subnet on the T2000 and how to include the created
NEs into the topology subnet. A topology subnet is created to simplify the GUI and has no impact
on the running NEs. To facilitate management, the topology objects in the same network area
or with similar attributes are displayed in one subnet.
2.13 Configuring Protection
This topic describes how to create a protection subnet and TPS protection group, for example,
a two-fiber bidirectional MSP ring with a 1+1 protection chain. The protection subnet provides
a network level protection for the services of each NE on the protection subnet. The TPS
protection provides the board level protection for the services.
2.14 Configuring the Clock
This topic describes how to configure a clock on the T2000. After you set the clock source and
specify the clock priority level, You need to enable the SSM or extended SSM protocol to prevent
the NE from tracing the incorrect clock source, thus providing protection. For the clock.
2.15 Configuring SDH/PDH Services by Using the Trail Function
This topic describes how to configure SDH/PDH services and the server layer trail by using the
trail function on the T2000. The trail function provides end-to-end service configuration between
NEs.
2.16 Configuring SDH/PDH Services by Using the Per-NE Configuration Function
This topic describes how to configure SDH/PDH services by using the per-NE configuration
function.
2.17 Configuring Parameters of SDH/PDH Boards
Common SDH board parameters include Laser Switch, Optical Interface Loopback, and
VC-4 Loopback. Common PDH board parameters include Service Load Indication and
Tributary Loopback.
2.18 Configuring Overhead Bytes
This topic describes how to configure overhead bytes on the T2000. You can set the overhead
bytes for maintaining or monitoring trails.
2.19 Configuring the Orderwire
This topic describes how to configure the orderwire on the T2000. If the NE is provisioned with
an orderwire, the network maintenance personnel can use the orderwire as a private
communication channel during emergencies.
2.20 Enabling/Disabling Performance Monitoring

This topic describes how to enable or disable the performance monitoring function on the T2000.
The performance parameters are used to monitor the equipment and analyze the network. This
topic describes how to enable or disable the performance monitoring function on the T2000.
2.21 Setting Alarm Parameters
This topic describes how to set the alarm parameters on the T2000. To prevent the alarm data
from overflowing or to prevent damage to the alarm data, you need to dump the alarm data in
time.
2.22 Configuring Automatic Laser Shutdown
The automatic laser shutdown (ALS) is performed before the output power of the laser
transmitter and the optical amplifier reaches a dangerous level. This topic considers the XCS4A
as an example to describe how to configure the ALS.
2.23 Backing Up the NE Configuration Data
This topic describes how to back up the NE configuration data on the T2000. To prevent data
loss, back up the NE configuration data after the configuration is complete.
2.24 Backing Up the T2000 Configuration Data
To prevent data loss, back up the T2000 configuration data after the configuration is complete.
This topic describes the immediate data backup and the periodic data backup on the T2000.


In a city, new communication lines need to be constructed among nodes A, B, C, D, and E to
form a local network.
Table 2-1 lists the requirements for the services among the nodes.
Table 2-1 Service requirements among the nodes
Node A B C D E
A - 32xE1 20xE1 32xE1 -
B 32xE1 - - - -
C 20xE1 - - - 12xE1
D 32xE1 - - 10xE1
E - - 12xE1 10xE1 -
Figure 2-1 shows the geographic position of each node and the available optical fiber cables.
Figure 2-1 Geographic position of each node and available optical fiber cables
Node A
(central equipment room)
25 km
2-core
Node B 40 km
2-core
2-core Node E
Node D 80 km
35 km
2-core 4-core
30 km
Node C
Optical fiber
Node
cable
The basic engineering plan is as follows:
l The central equipment room and the network management system (NMS) are set up at node
A.
l Nodes A, B, C, and D are connected by 2-core fibers. Nodes D and E are connected by 4-
core fibers.
l Line fibers are compliant with ITU-T G.652.
l The tributary E1 cables are 75-ohm coaxial cables.

l Nodes A, B, C, and D need to converge and groom services from different places. These
nodes bear large service capacities.
l The network level protection is required for the services between these nodes. The
equipment level protection is also required for the boards at node A.
Based on the routing of the fibers that are newly configured, the current service capacities, and
the forecast future service capacities, the optical ports used on the backbone lines at nodes A,
B, C, D, and E are 622 Mbit/s ports and the optical ports between the nodes D and E are 155
Mbit/s ports.

the detailed engineering information.
2.2.1 Networking Diagram

The networking diagram illustrates the architecture of the network.
2.2.2 IP Address Allocation Diagram
IP addresses need to be properly allocated to the NEs on a network according to the networking
diagram and specified service requirements.
2.2.3 Board Information of Each NE
This topic lists the boards that need to be configured on each NE according to the actual
networking and service requirements.
2.2.4 Fiber/Cable Connection Table
The fiber/cable connection is formed based on the networking architecture. The connection table
helps to connect the NEs properly and quickly.
2.2.5 Timeslot Allocation Diagram
The timeslot allocation diagram helps users learn the correct traffic direction and as a result the
service requirements for different NEs are properly fulfilled.
2.2.6 Board Level Protection
The OptiX OSN 2000 provides the board level protection schemes such as TPS and backup for
the SCC board, cross-connect and timing board, and PIU board. The protection schemes are
used to prevent service interruption from occurring in the case of a fault in the corresponding
boards.
2.2.7 Clock Tracing Diagram
The clock diagram helps to configure the correct clock tracing relations between NEs.
2.2.8 Orderwire Diagram
The orderwire diagram helps to configure the correct orderwire communication information for
different NEs.

The networking diagram illustrates the architecture of the network.
Based on the engineering situation and requirements, a MAN is constructed with the OptiX OSN
2000. See Figure 2-2. Table 2-2 lists the mapping relation between the place codes and NE
names. The line fibers are compliant with ITU-T G.652. The fiber attenuation coefficient is 0.275
dB/km (includes the attenuation of all the spliced joints and jumper connectors).

Table 2-2 Mapping relation between the place codes and the NEs
Place Code NE Name
A NE1
B NE2
C NE3
D NE4
E NE5
Figure 2-2 Networking diagram
NE1 (A)
T2000
40 km
25 km
NE4 (D) NE5 (E)
NE2 (B)
STM-4 two-fiber bidirectional 80 km
MSP ring
STM-1 linear MSP

NE3 (C) chain
35 km 30 km
2.2.2 IP Address Allocation Diagram

IP addresses need to be properly allocated to the NEs on a network according to the networking
diagram and specified service requirements.
Figure 2-3 shows the IP address allocation diagram.

Figure 2-3 IP address allocation diagram

NM ID T2000
IP address 129.9.0.254
Subnet mask 255.255.0.0
NE1
9-1
129.9.0.1
OSN 2000
NE2 129.9.0.1 NE4 NE5
9-2 9-4 9-5
129.9.0.2 STM-4 two-fiber bidirectional 129.9.0.4 129.9.0.5

MSP ring
OSN 2000 OSN 2000 OSN 2000
129.9.0.1 129.9.0.1 STM-1 linear MSP 129.9.0.1

chain
9-3
129.9.0.3
Extended ID–NE ID
IP address OSN 2000
Equipment type 129.9.0.1

Gateway NE3

This topic lists the boards that need to be configured on each NE according to the actual
networking and service requirements.
Figure 2-4 shows the board layout of NE1. Figure 2-5 shows the board layout of NE2 and NE3.
Figure 2-6 shows the board layout of NE4. Figure 2-7 shows the board layout of NE5.
Figure 2-4 Board layout of NE1

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
(IU1) (IU2) (IU3) (SU1) (SU2) (SU3) (XCS) (XCS) (SU4) (SU5) (SU6) (SCC) (PIU) (IU4) (IU5) (AUX)
S P
C I
X X
T T P P P C U A
C C
7 7 T T T U
S S
5 5 1 1 1 X
S P
4 4 P
S S
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

Figure 2-5 Board layout of NE2 and NE3

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S P
C I
X X
T P C U A
C C
A T U
S S
1 1 X
S P
4 4
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S P
C I
X X S S
T P C U A
C C L L
A T U
S S 1 1
1 1 X
S P
4 4 A A
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S P
C I
X X
T P C U A
C C
A T U
S S
1 1 X
S P
1 1
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

2.2.4 Fiber/Cable Connection Table

The fiber/cable connection is formed based on the networking architecture. The connection table
helps to connect the NEs properly and quickly.
Table 2-3 provides the fiber/cable connection between the NEs.
Table 2-3 Fiber/Cable connection between the NEs

Local End Remote End
NE Slot Board Port NE Slot Board Port

Name Name Number Name Name Numb
er
NE1 Slot 28 OSB4A TX NE2 Slot 27 OSB4A RX
NE1 Slot 28 OSB4A RX NE2 Slot 27 OSB4A TX
NE5 Slot 28 OSB1A TX NE4 Slot 11 SL1A RX
NE5 Slot 28 OSB1A RX NE4 Slot 11 SL1A TX
NE4 Slot 10 SL1A RX NE5 Slot 27 OSB1A TX
NE4 Slot 10 SL1A TX NE5 Slot 27 OSB1A RX
NOTE
The OSB1A/OSB4A in slot 27 is the line subboard integrated on the XCS1A/XCS4A board in slot 7. The
OSB1A/OSB4A in slot 28 is the line subboard integrated on the XCS1A/XCS4A board in slot 8.
2.2.5 Timeslot Allocation Diagram

The timeslot allocation diagram helps users learn the correct traffic direction and as a result the
service requirements for different NEs are properly fulfilled.
Figure 2-8 shows the timeslot allocation between the nodes.

Figure 2-8 Timeslot allocation diagram

Ring
Station
NE1 NE2 NE3 NE4 NE1
Timeslot 28-OSB4A-1 27-OSB4A-1 28-OSB4A-1 27-OSB4A-1 28-OSB4A-1 27-OSB4A-1 28-OSB4A-1 27-OSB4A-1
VC12:1-32 VC12:1-12
t4:1-32 t4:1-32 t4:1-12
1#VC4 VC12:33-52
t4:33-42,t5:33-42 t4:13-32
VC12:1-32
2#VC4
t4:1-32 t5:1-32
Line
Station NE4 NE5

Timeslot 10-SL1A-1 27-OSB1A-1
VC12:1-12
t4:1-12
1#VC4 VC12:13-22
t4:33-42 t4:13-22
Forward
Add/Drop
`
The t4 and t5 indicate the E1 tributary board in slots 4 and 5 respectively. The number that
follows the tributary board indicates the number of E1 path. For example, "t4:1-32" indicates
the first to the thirty-second E1 paths of the tributary board in slot 4. The numbers that are above
the horizontal lines indicate the timeslot number of the VC-4 that is occupied.
Consider NE4 as an example. The service shown in the diagram is as follows:
l The 12xE1 services from NE3 to NE5 pass through NE4 and occupy the timeslots 1 to 12
of the first VC-4.
l The E1 paths 33 to 42 of the tributary board in slot 4 of NE4 exchange services with the
E1 paths 13 to 22 of the tributary board in slot 4 of NE5. The timeslots 13 to 22 in the first
VC-4 carry the services.
l The E1 paths 1 to 32 of the tributary board in slot 4 of NE4 exchange services with the E1
paths 1 to 32 of the tributary board in slot 5 of NE1. The timeslots 1 to 32 in the second
VC-4 carry the services.
2.2.6 Board Level Protection

The OptiX OSN 2000 provides the board level protection schemes such as TPS and backup for
the SCC board, cross-connect and timing board, and PIU board. The protection schemes are
used to prevent service interruption from occurring in the case of a fault in the corresponding
boards.
Table 2-4 provides the information of the board level protection schemes.

Table 2-4 Board level protection information
NE TPS Backup for Backup for the PIU Backup

Protection SCC Cross-
Connect and
Timing Board
NE1 √ √ √ √
NE2 × √ √ √
NE3 × √ √ √
NE4 × √ √ √
NE5 × √ √ √
2.2.7 Clock Tracing Diagram

The clock diagram helps to configure the correct clock tracing relations between NEs.
Figure 2-9 shows the clock tracing diagram of the network.
Figure 2-9 Clock tracing diagram
BITS
NE1
BITS/intr
NE4 NE5
NE2
S27/S28 S27/S28
S27/S28 /intr /intr
/intr
NE3
S27/S28
/intr
NE name Sn: slot where the line

intr: internal clock source Clock tracing
Clock source priority clock source exists direction
1/priority 2/priority 3
To prevent mutual tracing of clocks in this example, do as follows: enable the extended SSM,
set the clock ID of the external clock source 1 (BITS) on NE1 to 1, and set the clock ID of the
internal clock source to 2.
Connect the BITS to the external clock source 1 of NE1 and adopt SA4 as the synchronization
status byte.

2.2.8 Orderwire Diagram

The orderwire diagram helps to configure the correct orderwire communication information for
different NEs.
Figure 2-10 shows the orderwire diagram.
Figure 2-10 Orderwire diagram

Extended ID-NE ID
NE name
Equipment type
9-1 Orderwire
NE1 phone/Conference call
OSN 2000
25 km
1001/9999 40 km
9-2 STM-4 linear

9-4 9-5
MSP chain
NE2 STM-4 two-fiber bidirectional NE4 NE5
OSN 2000 MSP ring OSN 2000 OSN 2000
1002/9999 80 km
1004/9999 1005/9999
9-3
NE3
OSN 2000 30 km
35 km
1003/9999
2.3 Engineering Preparation

Check the following items before configuring services on the T2000.
2.3.1 NE Side
Check the following items and make sure that the equipment functions properly.
2.3.2 T2000 Side
Check the following items and make sure that the equipment can be normally managed by the
T2000.
2.3.3 Document
Make sure that the relevant documents are available so that the correct configuration information
can be easily accessed in the networking process.
2.3.1 NE Side
Check the following items and make sure that the equipment functions properly.
l The OptiX OSN 2000 must be installed.

l The single-station commissioning must be complete.
l The fibers between stations must be connected correctly.
l The NE IDs, extended IDs, and the IP address of the gateway NE (GNE) must be set as
shown in Figure 2-3.

2.3.2 T2000 Side

Check the following items and make sure that the equipment can be normally managed by the
T2000.
l The T2000 software and hardware must be installed correctly.

l The T2000 server must run normally.
l The communication between the T2000 and GNE must be established and must be normal.
2.3.3 Document
Make sure that the relevant documents are available so that the correct configuration information
can be easily accessed in the networking process.
l The engineering planning information must be available.

l After logging in to the T2000 client, the user must be able to use the key F1 to view the
online Help.
l The manuals for the OptiX OSN 2000 and the OptiX iManager T2000 must be available.

This topic describes how to configure SDH/PDH services.
NOTE
This section describes the procedures and precautions for configuring services in an SDH network on the
T2000. For details, see the OptiX iManager T2000 Operation Guide for SDH.
Procedures for configuring SDH services on the T2000 are listed as follows.
Table 2-5 Procedures for configuring SDH/PDH services
Procedure Operation
1 2.5 Logging In to the T2000
2 2.6 Creating a Topology
3 2.7 Configuring Communication
4 2.8 Creating an NE User
5 2.9 Logging In to an NE
6 2.10 Creating a Board
7 2.11 Creating Fibers
8 2.12 Creating a Topology Subnet
9 2.13 Configuring Protection
10 2.14 Configuring the Clock
11 2.15 Configuring SDH/PDH Services by Using the Trail Function

Procedure Operation
12 2.16 Configuring SDH/PDH Services by Using the Per-NE

Configuration Function
13 2.17 Configuring Parameters of SDH/PDH Boards
14 2.18 Configuring Overhead Bytes
15 2.19 Configuring the Orderwire
16 2.20 Enabling/Disabling Performance Monitoring
17 2.21 Setting Alarm Parameters
18 2.22 Configuring Automatic Laser Shutdown
19 2.23 Backing Up the NE Configuration Data
20 2.24 Backing Up the T2000 Configuration Data
2.5 Logging In to the T2000

The T2000 provides all the NE-layer management functions, including the fault management,
performance management, configuration management, security management, communication
management, topology management, and system management. In addition, the T2000 provides
certain network-layer management functions. This topic describes how to log in to the T2000.
Prerequisite
l The T2000 server and client must be started and the server must operate normally.
l The user must know the user name and password.
Precautions
CAUTION
l If the T2000 server and T2000 client are installed on one computer, set the IP address and
port number of the T2000 server to 127.0.0.1 and 9800 respectively, to log in to the T2000.
l If the T2000 server and T2000 client are on different computers, enter the actual IP address
for the IP address of the T2000 server and 9800 for the port number, to log in to the T2000.
l By default, the server is in the common mode. The server mode can also be switched to the
security (SSL) mode. You need not enter the port number manually. After the mode is
selected, the system automatically selects the corresponding port number. If the server and
the client are installed on different computers, the modes must be the same. Otherwise, the
client fails to log in to the server.

Procedure
Step 1 Double-click the T2000Client icon on the desktop to enter the Login interface.
Step 2 Enter the following user information in the Login interface:
l User Name: admin
l Password: T2000
Step 3 Click , and Click Add Server in the Server Setting dialog box that is displayed.
Step 4 Enter the following T2000 server information in the dialog box:
l IP Address: 129.9.0.254
l Port: 9800
l Mode: Common
l Server Name: T2000
Step 5 Click OK. Select the corresponding server, and then click OK.
CAUTION
By default, the initial user name of the T2000 is admin, and the password is T2000. To ensure
security, change this password immediately after you log in to the system. The IP address
provided in this example may not be the IP address of the server. Hence, you need to set the IP
address according to the actual situation.
Step 6 Click Login. After the data is loaded, the Main Topology is displayed on the T2000.
----End
2.6 Creating a Topology

This topic describes how to create, display, and manage an NE on the T2000.
2.6.1 Creating a Gateway NE: NE1

This topic uses an example to describe how to configure a gateway NE (NE1).
2.6.2 Creating Non-Gateway NEs: NE2–NE5

This topic uses an example to describe how to configure non-gateway NEs (NE2–NE5).
2.6.1 Creating a Gateway NE: NE1

This topic uses an example to describe how to configure a gateway NE (NE1).
Prerequisite
l You must log in to the T2000, and the T2000 must be connected to the equipment correctly.
l You must be a T2000 user with "NE and network operator" authority or higher.
Procedure
Step 1 Right-click on the Main Topology and choose New > Device. Then, select the NE type: OSN
Series > OptiX OSN 2000.
Step 2 Enter the NE attributes into the dialog box according to the IP address allocation diagram as
l ID: 1
l Extended ID: 9
l Name: NE1
l Gateway Type: Gateway
l Protocol: IP
l IP Address: 129.9.0.1
l Connection Mode: Common
l Port: 1400
l NE User: root
l Password: password
l Clear the NE Preconfiguration check box.
Step 3 Click OK.
Step 4 Click on the Main Topology, and the icon of NE1 is displayed. There are and above the
NE1 icon. indicates the gateway and indicates that the NE is not configured.
----End
2.6.2 Creating Non-Gateway NEs: NE2–NE5

This topic uses an example to describe how to configure non-gateway NEs (NE2–NE5).
Prerequisite

Procedure
Step 1 Right-click on the Main Topology and choose New > Device . Then, select the NE type: OSN
Series > OptiX OSN 2000 .
Step 2 Enter the NE attributes into the dialog box according to the IP address allocation diagram as
l ID: 2
l Extended ID: 9
l Name: NE2
l Gateway Type: Non-Gateway
l Affiliated Gateway: NE1
l Affiliated Gateway Protocol: IP
l NE User: root
Step 3 Click OK.
Step 4 Click on the Main Topology, and the icon of NE2 is displayed. There is a above the icon to
indicate that the NE is not configured.
Step 5 Refer to Steps 1–4 to create the NE icons for NE3, NE4, and NE5 respectively.
----End
2.7 Configuring Communication

This topic describes how to set the Ethernet access function of an NE on the T2000. By default,
an NE supports access of the T2000 through Ethernet.
Prerequisite
l You must be an NM user with "network maintainer" authority or higher.
Precautions
CAUTION
When the Ethernet access control is enabled, the NE communication is reset.
Procedure
Step 1 Select the NE1 icon on the Main Topology. Right-click and choose NE Explorer from the
shortcut menu.

Step 2 Select NE1 from the Object Tree and choose Communication > Access Control from the
Function Tree.
Step 3 Set The First Network Port to Enabled in the Ethernet Access Control window.
Step 4 Click Apply.
----End
2.8 Creating an NE User

This topic describes how to create an NE user on the T2000. The NE user can specify the authority
of the NE operator, thus facilitating the control of the NE access and configuration.
Prerequisite
l You must an NM user with "NE and network administrator" authority or higher.
There are five levels of user authority, and they are monitor, operation, maintenance, system,
and debug in an ascending order of priority. A higher level user has the authority of the lower
level. For example, an operation level user has the authority of the monitor level, and the highest
level user has all the authority. Table 2-6 provides the authority pertaining to each level.
Table 2-6 NE user level and authority description
NE User Level Authority
Monitor level All query commands, login and logout, and modification to its own
password
Operation level All settings for fault and performance, certain security settings, and
certain configurations
Maintenance level Certain security settings, certain configurations, communication

settings, and log management
System level All security settings and all configurations
Debug level All security settings, all configurations, and all debugging
commands

Different NE users are used to log in to different T2000 systems. Table 2-7 lists the NE user
flags.
Table 2-7 NE user flag

NE User Flag Description
LCT NE user An NE user who manages NEs on the local craft terminal (LCT)
EMS NE user An NE user who manages NEs on the element management system
(EMS), that is, on the T2000
CMD NE user An NE user who manages NEs by using commands
Universal NE user An NE user who does not belong to any particular T2000 category
Procedure
Step 1 Choose System > NE Security Management > NE User Management from the Main Menu.
Step 2 Select NE1–NE5 from the navigation tree and click .

Step 3 Select NE1–NE5 and click Add.
Step 4 Enter the attributes of the added NE user: user name, user level, user flag, password, and a
detailed description of the new NE user. For example, create a unified NE user T2000 for NE1–
NE5, as shown in the following figure. The user name contains 4 to 16 characters. The password
contains 6 to 16 characters, including at least one letter and one numeral. For description on the
user level and priority, refer to Table 2-6. For description of the user flag, refer to Table 2-7.

Step 5 Click OK. A dialog box is displayed indicating that the operation is successful. Click Close.
----End
2.9 Logging In to an NE
This topic describes how to switch the NE users on the T2000. Different clients cannot use the
same NE user ID to log in to or manage an NE. Otherwise, the client automatically logs out of
the NE when another client logs in to the NE.
Prerequisite
l The NE user to log in to the NE must be created.
l You must be an NM user with "NE and network administrator" authority or higher.
Procedure
Step 1 Choose System > NE Security Management > NE Login Management from the Main Menu.

Step 2 Select NE1–NE5 from the navigation tree and click .

Step 3 Select NE1–NE5, and then click Switch NE User.
Step 4 Enter the user name and password of the NE user to switch to. For example, switch the NE users
of NE1–NE5 to the T2000 user.
Step 5 Click OK. A dialog box is displayed indicating that the operation is successful. Click Close.
----End
2.10 Creating a Board

This topic describes how to create a board in the configuration wizard or the NE panel diagram.
Before you configure services on an NE and to manage an NE, create the boards.
You can create a board by using either of the following methods:
l Add a board in the configuration wizard. This applies to NEs that are not configured.
l Add a board on the NE panel manually. This is applicable to NEs that are configured.
NOTE
l The AUX board integrates the STI board. Hence, create the AUX and STI boards when creating the
AUX on the T2000.
l The AUX1 board integrates the ST1 and LA1 boards. Hence, create the AUX, ST1, and the LA1 boards
when creating the AUX1 on the T2000.
l The XCS1A/XCS4A/XCS16 board integrates the XCS and OSB1A/OSB4A/OSB16 boards. Hence,
create the XCS and OSB1A/OSB4A/OSB16 boards when creating the XCS1A/XCS4A/XCS16 on the
T2000.
2.10.1 Adding a Board in the Configuration Wizard

This topic describes how to configure a board by using the configuration wizard. This method
applies to the NE that is not configured.
2.10.2 Adding a Board in the NE panel Manually
This topic describes how to configure a board in the NE panel. This method applies to the NE
that is configured.
2.10.1 Adding a Board in the Configuration Wizard

This topic describes how to configure a board by using the configuration wizard. This method
applies to the NE that is not configured.
Prerequisite
l The board to be created must be installed and it must work normally.
Procedure
Step 1 Double-click the NE1 icon on the Main Topology. Then, the NE Configuration Wizard is
displayed.
Step 2 Select Manual Configuration and click Next.
Step 3 Confirm the NE attributes and click Next.
Step 4 Then, the NE panel diagram is displayed. Click Query Physical Slot(s), and the board that is
already installed on the NE side is displayed. Then, click Next.

Step 5 Select Verify and Run, and click Finish. The configuration data is delivered to the NE side.
Step 6 Refer to Steps 1–5 to configure NE2, NE3, NE4, and NE5. Figure 2-4 shows the board layout
of NE1. Figure 2-5 shows the board layout of NE2 and NE3. Figure 2-6 shows the board layout
of NE4. Figure 2-7 shows the board layout of NE5.
----End
2.10.2 Adding a Board in the NE panel Manually

This topic describes how to configure a board in the NE panel. This method applies to the NE
that is configured.
Prerequisite
l The board to be created must be installed and it must work normally.
l The NE must be configured.
Procedure
Step 1 Double-click the NE1 icon on the Main Topology. Then, the NE panel diagram is displayed.

Step 2 See Figure 2-4 and right-click the slot to be added with a board, and select the corresponding
board.
Step 3 Click to exit the NE panel diagram.
Step 4 Refer to Steps 1–3 to configure NE2, NE3, NE4, and NE5. Figure 2-5 shows the board layout
of NEs 2 and 3. Figure 2-6 shows the board layout of NE4. Figure 2-7 shows the board layout
of NE5.
----End
2.11 Creating Fibers

This topic describes how to create fibers on the T2000. After fibers are created, they are displayed
on the T2000.
Create fibers in either of the following methods:
l Manually creating fibers: This method is applicable to scenarios where few fibers are to be
created.
l Automatically searching for and then creating fibers: This method is applicable to scenarios
where many fibers are to be created.
2.11.1 Creating Fibers Manually
This topic describes how to create fibers manually. This method is applicable to creating a small
number of fibers one after another.
2.11.2 Creating Fibers Automatically
This topic describes how to search and create fibers automatically. This method is applicable
when fibers are created in batches.
2.11.1 Creating Fibers Manually

This topic describes how to create fibers manually. This method is applicable to creating a small
number of fibers one after another.
Prerequisite
l The fibers between the equipment must be correctly connected. The boards that are
connected to the fibers must be created.
l You must be an NM user with "NE and network administrator authority or higher.
Procedure
Step 1 Select from the shortcut icons of the Main Topology. Then, the mouse pointer changes to
.
Step 2 Click on the Main Topology to select the fiber source NE NE1, and select the source board 28-
OSB4A, and the source port 1.
Step 3 Click on the Main Topology to select the fiber source NE NE2, and select the source board 27-
OSB4A, and the source port 1.
Step 4 Set the fiber attributes from the Create Fiber/Cable dialog box and click OK.

TIP
If you click Apply in the Create Fiber/Cable dialog box, you can continue to create other fibers without
repeating Step 1.
Step 5 Refer to Steps 1–4 to create a fiber connection between NEs so that the five NEs form a ring
with a chain. Table 2-3 provides the connection relation between the fibers and cables.
----End
2.11.2 Creating Fibers Automatically

This topic describes how to search and create fibers automatically. This method is applicable
when fibers are created in batches.
Prerequisite
l The fibers between the equipment must be correctly connected. The boards that are
connected to the fibers must be created.
Procedure
Step 1 Choose File > Search for Fiber/Cable from the Main Menu.

Step 2 Select NE1–NE5 from the Navigation Tree on the left and click Search. A progress bar is
displayed indicating the progress of the operation.
Step 3 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 4 Select one or several fibers from Newly Searched Fiber and click Create Fiber/Cable.
----End
2.12 Creating a Topology Subnet

This topic describes how to create a topology subnet on the T2000 and how to include the created
NEs into the topology subnet. A topology subnet is created to simplify the GUI and has no impact
on the running NEs. To facilitate management, the topology objects in the same network area
or with similar attributes are displayed in one subnet.
Prerequisite
l The NEs must be created on the T2000 correctly.
NOTE
The subnet that is created in this example is only a topology concept. You can place the topology objects
in a network into a subnet for display.
Procedure
Step 1 Right-click on the Main Topology and choose New > Subnet to enter the Add Object dialog
box.
Step 2 Click the Properties tab, and enter the subnet name OptiX OSN 2000.
Step 3 Click the Select Object tab and select NE1–NE5 from Available Objects. Click to add
the NEs to Selected Objects.
Step 4 Click OK.
Step 5 After the subnet is created successfully, the icon is displayed on the Main Topology.
Step 6 Double-click or right-click the icon of this subnet, and then choose Enter. You can only enter
the topology view that contains this topology only. Right-click on this topology to choose Up
and you can enter the Main Topology that contains all the topology objects.
----End
2.13 Configuring Protection

This topic describes how to create a protection subnet and TPS protection group, for example,
a two-fiber bidirectional MSP ring with a 1+1 protection chain. The protection subnet provides
a network level protection for the services of each NE on the protection subnet. The TPS
protection provides the board level protection for the services.

2.13.1 Creating a Two-Fiber Bidirectional MSP Ring

NE1, NE2, NE3, and NE4 form a two-fiber bidirectional MSP ring. Before the service
configuration, you need to create a protection subnet.
2.13.2 Creating a 1+1 Linear MSP Chain
NE4 and NE5 form a 1+1 protection chain.
2.13.3 Configuring TPS Protection
This topic describes how to configure TPS protection on the T2000.
2.13.1 Creating a Two-Fiber Bidirectional MSP Ring

NE1, NE2, NE3, and NE4 form a two-fiber bidirectional MSP ring. Before the service
configuration, you need to create a protection subnet.
Prerequisite
l The created protection subnet must be consistent with the actual topology.
l The NEs, boards, and fibers must be created on the T2000.
Procedure
Step 1 Choose Protection Subnet > Create SDH Protection Subnet > 2f_MS_SPRing from the Main
Menu. Then, the Wizard for Creating Two-Fiber Bidirectional MS Shared Protection
Ring is displayed.
Step 2 Set the following parameters in the Wizard for Creating Two-Fiber Bidirectional MS Shared
Protection Ring dialog box:
l Name: 2f_MS_SPRing_1
l Level: STM-4
Step 3 Double-click the icons of NE1 to NE4 in the topology view on the right in turn to add them into
the protection subnet. The Node Attributes parameter uses the default value MSP Node. Then,
click Next.
Step 4 Confirm Physical Link Information and click Finish.
Step 5 A dialog box is displayed indicating that the protection subnet is successfully created.
----End
2.13.2 Creating a 1+1 Linear MSP Chain

NE4 and NE5 form a 1+1 protection chain.

Prerequisite
l You must be an NM user with "NE and network operator" authority or higher.
Procedure
Step 1 Choose Protection Subnet > Create SDH Protection Subnet > 1+1 linear MSP from the
Main Menu. Then, the Wizard for Creating 1+1 Linear MSP Chain dialog box is displayed.
Step 2 Set the following parameters in the Wizard for Creating 1+1 Linear MSP Chain dialog box:
l Name: 1+1_MSP_1
l Level: STM-1
l Revertive Mode: Non-Revertive
l Switching Mode: Single-Ended Switching
Step 3 Double-click the NE4 and NE5 icons in turn in the topology view on the right to add them to
the protection subnet. Then, Click Next.
Step 5 A dialog box is displayed indicating that the protection subnet is successfully created.
----End
2.13.3 Configuring TPS Protection

This topic describes how to configure TPS protection on the T2000.
Prerequisite

NOTE
The T2000 automatically creates the 1+1 protection for the SCC unit, clock unit, and cross-connect unit
according to the board configurations. Thus, you need not configure the 1+1 protection manually.
Procedure
Step 1 Right-click the NE icon in the Main Topology, and choose NE Explorer from the shortcut
menu.
Step 2 Select NE1 in the upper left pane and choose Configuration > TPS Protection from the
Function Tree.
Step 3 Click Create and set the following parameters in the Create SDH TPS Protection Group dialog
box:
l Protection Board: 11-PT1P
l Working Board: 4-PT1, 5-PT1
l WTR Time(s): 600
l Priority: Priority-1 for the 4-PT1, Priority-2 for the 5-PT1
Step 4 Click OK.

----End
2.14 Configuring the Clock

This topic describes how to configure a clock on the T2000. After you set the clock source and
specify the clock priority level, You need to enable the SSM or extended SSM protocol to prevent
the NE from tracing the incorrect clock source, thus providing protection. For the clock.

CAUTION
l The NE can trace the external clock, the building integrated timing supply (BITS), line clock,
tributary clock, and internal clock. To realize clock protection, you need to set a minimum
of two clock tracing sources. Normally, the tributary clock is not used as the reference clock
of the clock subnet.
l When the extended SSM protocol is disabled, do not set the clock into a loop or trace the
loopback clock source to prevent clock interlock.
l When the extended SSM protocol is enabled, the clock can be set to a loop.
2.14.1 Configuring the Clock Source Priority Table

This topic describes how to configure the clock source priority table.
2.14.2 Configuring a Clock Subnet
This topic describes how to configure a clock subnet, including the procedures and parameter
settings.
2.14.1 Configuring the Clock Source Priority Table

This topic describes how to configure the clock source priority table.
Prerequisite
l To realize clock protection, a minimum of two clock tracing sources must be configured.
Procedure
Step 1 Right-click the NE icon on the Main Topology, and choose NE Explorer from the shortcut
menu.
Step 2 Select NE1 in the upper left pane and choose Configuration > Clock > Clock Source
Priority from the Function Tree.
Step 3 Click the System Clock Source Priority List tab.
Step 4 Click Create. Select External Clock Source 1.
Step 5 Click OK.
Step 6 Select External Clock Source 1. Set the default value for External Clock Source Mode and
Synchronous Status Byte.
NOTE
In this example, set External Clock Source Mode and Synchronous Status Byte for NE1 only.
Step 7 Set External Clock Source 1 to the highest priority and click Apply. Select External Clock
Source 1. You can click to lower its priority or to increase its priority.
The priority of the internal clock source should be the lowest.
Step 8 Click Apply.

Step 9 See Figure 2-9 and refer to Steps 1–7 to set clock tracing source and clock priority table of NE2,
NE3, NE4, and NE5.
----End
2.14.2 Configuring a Clock Subnet

This topic describes how to configure a clock subnet, including the procedures and parameter
settings.
Prerequisite
l To realize clock protection, a minimum of two clock tracing sources must be configured.
NOTE
In this example, all NEs belong to the same clock subnet and use the extended SSM protocol. Hence, the
two parameters Line Ports of SSM Output Control and Line Ports of Clock ID Status are set to
Enabled.
Procedure
Step 1 Right-click the NE1 icon on the Main Topology, and choose NE Explorer from the shortcut
menu.
Step 2 Select NE1 in the upper left pane and choose Configuration > Clock > Clock Subnet
Configuration from the Function Tree.
Step 3 Click the Clock Subnet tab and set the following parameters:
l Affiliated Subnet: 0
l Protection Status: Start Extended SSM Protocol
l Clock Source ID of External Clock Source 1: 1
l Clock Source ID of Internal Clock Source: 2
Step 4 Click Apply.

NOTE
In this example, only NE1 requires the setting of the clock source ID.
Step 5 Click the Clock Quality tab and then click the Clock Source Quality tab. Set Configuration
Quality as follows:
l External Clock Source 1: Automatic Extraction
l Internal Clock Source: Automatic Extraction
Step 6 Click Apply.
Step 7 Click the SSM Output Control tab. Set Control Status of line ports 27-OSB4A (SDH-1) and
28-OSB4A (SDH-1) to Enabled.
Step 8 Click Apply.
Step 9 Select Clock ID Status. Set the enable status of line ports 27-OSB4A (SDH-1) and 28-OSB4A
(SDH-1) to Enabled.
Step 10 Click Apply.
Step 11 Refer to Steps 1–10 to set the clock subnet parameters of NE2, NE3, NE4, and NE5.
----End
2.15 Configuring SDH/PDH Services by Using the Trail

Function
This topic describes how to configure SDH/PDH services and the server layer trail by using the
trail function on the T2000. The trail function provides end-to-end service configuration between
NEs.
On the T2000, SDH and PDH services can be configured by using either of the following
methods:
l Using the trail function

l Using the single station configuration, that is, perform the configuration on the per-NE
basis: The service must be capable of being added to/dropped from the NEs at two ends
and passed through the intermediate NEs.

NOTE
l You need to obtain the license for the trail function. Otherwise, you can only use the station
configuration function.
l Before you configure the services, query the remaining available resources by choosing Report > TU
Port Resource Statistics.
2.15.1 Creating a VC-4 Server Trail

The VC-4 server layer trail is used to carry VC-12/VC-3 services between NEs. Before
configuring the VC-12/VC-3 services, create the VC-4 server layer trail. You need not create a
VC-4 server layer trail for VC-4 services.
2.15.2 Creating a VC-12 Trail
This topic describes how to create a VC-12 trail, including the operations and parameter settings.
2.15.1 Creating a VC-4 Server Trail

The VC-4 server layer trail is used to carry VC-12/VC-3 services between NEs. Before
configuring the VC-12/VC-3 services, create the VC-4 server layer trail. You need not create a
VC-4 server layer trail for VC-4 services.
Prerequisite
l The preceding operations must be complete.
l The license for using the trail function must be available.
Procedure
Step 1 Choose Trail > SDH Trail Creation from the Main Menu.
Step 2 Set the following parameters in the SDH Trail Creation window:
l Direction: Bidirectional
l Level: VC4 Server Trail
l Resource Usage Strategy: Protected Resource
l Protection Priority Strategy: Trail Protection First
Step 3 Select the source NE and sink NE. Double-click the NE in the topology view on the right, and
select the source NE NE1 and sink NE NE2. If you double-click the NE again, the selection is
cancelled. Alternatively, click Browse to select an NE. The selected source NE is marked as
, and the selected sink NE is marked as .
Step 4 Click Set Route Timeslot. Set Timeslot to 1 and click OK. Select Auto-Calculation. The trail
marked with an arrow is displayed between the source NE and the sink NE in the topology view
on the right.
Step 5 Set the trail parameters as follows:

l Name: NE1-NE2-VC4 Server Trail-0001
l Order No.: 1
Step 6 Select the Activate the trail and Copy after Creation check boxes.

Step 7 Click Apply. A dialog box is displayed indicating that the trail is created successfully. Click
Close.
Step 8 In the displayed Copy dialog box, set the following parameters and then click Add:
l Source: NE1-28-OSB4A-1(SDH-1)-VC4:2
l Sink: NE2-27-OSBA4-1(SDH-1)-VC4:2
Step 9 Select the Specify the start timeslot check box and set the parameter to 2. Set The start value
of the trail name suffix to 2.
Step 10 Select Activate. Click OK to create a VC-4 server layer trail.
Step 11 Refer to Steps 1–10 to create the VC-4 service trails for paths 1–2 between adjacent NEs: NE2
and NE3, NE3 and NE4, and NE4 and NE1. Refer to Steps 1–7 to create the VC-4 service trail
for path 1 between NE4 and NE5.
----End
2.15.2 Creating a VC-12 Trail

This topic describes how to create a VC-12 trail, including the operations and parameter settings.
Prerequisite
l The license for using the trail function must be available.
Procedure
Step 1 Choose Trail > SDH Trail Creation from the Main Menu.
l Level: VC12
l Resource Usage Strategy: Protected Resource
l Protection Priority Strategy: Trail Protection First

Step 3 Select the source and the sink. See Figure 2-8 and create the service of each NE. Double-click
the icon of NE1 in the topology view on the right. In the Select Board Port-Source-NE1 dialog
box, click the PT1 board in slot 4 on the NE panel diagram. Select 1 for Tributary Port.
Step 4 Click OK.
Step 5 Double-click the icon of NE2 in the topology view on the right. In the Select Board Port-Sink-
NE2 dialog box, click the PT1 board in slot 4 on the NE panel diagram. Select 1 for Tributary
Port.
Step 6 Click OK.
Step 7 Optional: Double-click the icon of NE4 in the topology view on the right to specify the backup
route provided by the system that does not pass through NE4. is displayed above NE4. You
can specify the route that should not be used to pass through a certain NE with this method. This
ensures that the routing direction conforms to the requirement. Normally, it is not selected.
Step 8 Click Set Route Timeslot. When the Set Route Timeslot dialog box is displayed, click the
choice box under Timeslot to select timeslot 1[1-1-1] for the service on the VC-4.
Step 9 Click OK.
l Name: NE1-NE2-VC12-0001
l Order No.: 1
Step 11 Select the Activate the trail and Copy after Creation check boxes to allow the duplication of
other 31 E1 services from NE1 to NE2 after the creation of this E1 timeslot.
Step 12 Click Apply.
Step 13 In the displayed Copy dialog box, set the following parameters and then click Add:
l Source: NE1-4-PT1-2(SDH_TU-2)–NE1-4-PT1-32(SDH_TU-32)
l Sink: NE2-4-PT1-2(SDH_TU-2)–NE2-4-PT1-32(SDH_TU-32)
Step 14 Select the Select Timeslots/Port check box. Set the Specify the start timeslot of the 31 E1s on
the VC-4 to 2: 2-1-1. Set The start value of the trail name suffix to 2. Select Activated.

Step 15 Click OK.

Step 16 Refer to Steps 1–15 to create the E1 service from NE1 to NE3 and NE1 to NE4, and then the
E1 service between NE3, NE4, and NE5.
----End
2.16 Configuring SDH/PDH Services by Using the Per-NE

This topic describes how to configure SDH/PDH services by using the per-NE configuration
function.
NOTE
When using the per-NE configuration function to configure services, you need not configure the VC-4
server layer trail. Instead, configure cross-connections of services on NE1 to NE5 in turn. This topic can
be skipped if the SDH/PDH service has been configured by using the trail function.
NOTE
Before you configure the services, query the remaining available resources by choosing Report > TU Port
Resource Statistics.

NOTE
l Before configuring add/drop services, configure bidirectional services from line boards to tributary
boards.
l Before configuring pass-through services, configure bidirectional services between line boards.
2.16.1 Creating Services on NE1

This topic uses an example to describe how to configure the data of NE1.
This topic describes how to configure the data of NE2 through an example.

Prerequisite
Procedure
menu.
Step 2 Select NE1 in the upper left pane and choose Configuration > SDH Service Configuration
from the Function Tree. Click .
Step 3 According to Figure 2-8, create the E1 service from NE1 to NE2: from ports 1–32 of the 4-PT1
tributary board to timeslots 1–32 of the first VC-4 on the 28-OSB4A optical interface board.
Click Create. Set the following parameters in the Create SDH Service dialog box:
l Level: VC12
l Source Slot: 4-PT1
l Source Timeslot Range (e.g. 1, 3-6): 1–32
l Sink Slot: 28-OSB4A-1(SDH-1)
l Sink VC4: VC4-1
l Sink Timeslot Range (e.g. 1, 3-6): 1–32
l Activate Immediately: Yes

Step 4 Click OK.
Step 5 According to Figure 2-8, create the E1 services from NE1 to NE3: from ports 33–42 of the 4-
PT1 tributary board to timeslots 33–42 of the first VC-4 on the 28-OSB4A optical interface
board and from ports 33–42 of the 5-PT1 tributary board to timeslots 43–52 of the first VC-4
on the 28-OSB4A optical interface board. Click Create. Set the following parameters in the
Create SDH Service dialog box:
1. Set the service from the 4-PT1 board to the 28-OSB4A board as follows:
l Level: VC12
l Sink VC4: VC4-1
2. Set the service from the 5-PT1 board to the 28-OSB4A board as follows:
l Level: VC12

l Sink VC4: VC4-1
Step 6 Click OK.
tributary board to timeslots 1–32 of the second VC-4 on the 27-OSB4A optical interface board.
l Level: VC12
l Sink VC4: VC4-2
Step 8 Click OK.
----End

This topic describes how to configure the data of NE2 through an example.
Prerequisite
Procedure
Step 1 Click in NE Explorer and select the NE2 icon from the Object Tree. Then, click OK.
tributary board to timeslots 1–32 of the first VC-4 on the 27-OSB4A optical interface board.
l Level: VC12


l Sink VC4: VC4-1
Step 4 Click OK.
Step 5 According to Figure 2-8, configure the service from NE1 to NE3 that passes through NE2: from
timeslots 33–52 of the first VC-4 on the 27-OSB4A optical interface board to timeslots 33-52
of the first VC-4 on the 28-OSB4A optical interface board. Click Create. Set the following
parameters in the Create SDH Service dialog box:
l Level: VC12
l Source Slot: 27-OSB4A-1(SDH-1)
l Source VC4: VC4-1
l Sink VC4: VC4-1
Step 6 Click OK.
----End

Prerequisite
Procedure
board. Click Create. Set the following parameters in the Create SDH Service dialog box:
l Level: VC12

l Sink VC4: VC4-1
Step 4 Click OK.
PT1 tributary board to timeslots 1–12 of the first VC-4 on the 28-OSB4A optical interface board.
l Level: VC12
l Sink VC4: VC4-1
Step 6 Click OK.
----End

Prerequisite
Procedure
tributary board to timeslots 1–32 of the second VC-4 on the 28-OSB4A optical interface board.
l Level: VC12


l Sink VC4: VC4-2
Step 4 Click OK.

Step 5 According to Figure 2-8, configure the E1 service from NE3 to NE5 that passes through NE4:
from timeslots 1–12 of the first VC-4 on the 27-OSB4A optical interface board to timeslots 1-12
of the first VC-4 on the 110-SL1A optical interface board. Click Create. Set the following
parameters in the Create SDH Service dialog box:
l Level: VC12
l Source VC4: VC4-1
l Sink Slot: 10-SL1A-1(SDH-1)
l Sink VC4: VC4-1

Step 6 Click OK.

PT1 tributary board to timeslots 13–22 of the first VC-4 on the 10-SL1A optical interface board.
l Level: VC12
l Sink Slot: 10-SL1A-1(SDH-1)
l Sink VC4: VC4-1
Step 8 Click OK.
----End


Prerequisite
Procedure
PT1 tributary board to timeslots 1–12 of the first VC-4 on the 27-OSB4A optical interface board.
l Level: VC12
l Sink VC4: VC4-1
Step 4 Click OK.

board. Click Create. Set the following parameters in the Create SDH Service dialog box:
l Level: VC12
l Sink VC4: VC4-1
Step 6 Click OK.
----End
2.17 Configuring Parameters of SDH/PDH Boards

Common SDH board parameters include Laser Switch, Optical Interface Loopback, and
VC-4 Loopback. Common PDH board parameters include Service Load Indication and
Tributary Loopback.

Prerequisite
l Trails must be created and activated.
NOTE
For settings of the board parameters, see the OptiX iManager T2000 Help.
Procedure
Step 1 Set the parameters of SDH boards on each NE according to the requirements.
Step 2 Set the parameters of PDH boards on each NE according to the requirements.
----End
2.18 Configuring Overhead Bytes

This topic describes how to configure overhead bytes on the T2000. You can set the overhead
bytes for maintaining or monitoring trails.
2.18.1 Configuring the RS Overhead J0
J0 is an RS trace byte. It is used to verify that a section receiver is connected to the intended
transmitter. This topic describes how to configure the J0 byte on the T2000. This topic describes
how to configure the regenerator section (RS) overhead byte J0 on the T2000.
2.18.2 Configuring the Tracing Byte J1
The J1 byte allows a receiving terminal to verify its continued connection to the intended
transmitting terminal. This topic describes how to configure the J1 byte on the T2000. The tracing
byte can be set as any same characters at both ends if the interconnection involves only the
equipment from the same vendor. If the interconnection involves equipment from different
vendors, the tracing bytes should be set to defined characters. Otherwise, the interconnection
fails.
2.18.3 Configuring the Signal Flag Byte C2
The C2 byte specifies the multiplex structure and the service type such as PDH services. This
topic describes how to configure the C2 byte on the T2000.
2.18.1 Configuring the RS Overhead J0

J0 is an RS trace byte. It is used to verify that a section receiver is connected to the intended
transmitter. This topic describes how to configure the J0 byte on the T2000. This topic describes
how to configure the regenerator section (RS) overhead byte J0 on the T2000.
Prerequisite

Procedure
menu.
Step 2 Select 27-OSB4A from the Object Tree and choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
Step 3 Double-click J0 to be Sent([Mode]Content). Set Input in Text Format, Byte Mode, and
Input Mode for overhead bytes.
Step 4 Click OK.
Step 5 Double-click J0 to be Received([Mode]Content). Set Input in Text Format, Byte Mode, and
Step 6 Click OK.
Step 7 Click Query to query J0 Received([Mode]Content).
----End
2.18.2 Configuring the Tracing Byte J1

The J1 byte allows a receiving terminal to verify its continued connection to the intended
transmitting terminal. This topic describes how to configure the J1 byte on the T2000. The tracing
byte can be set as any same characters at both ends if the interconnection involves only the
equipment from the same vendor. If the interconnection involves equipment from different
vendors, the tracing bytes should be set to defined characters. Otherwise, the interconnection
fails.
Prerequisite
NOTE
The VC-12/VC-3/VC-4 tracing byte J1 can be queried or set only after the VC-12/VC-3/VC-4 cross-
connection is created.
Procedure
menu.
Step 2 Select 27-OSB4A from the Object Tree and choose Configuration > Overhead
Management > VC4 Path Overhead from the Function Tree.
Step 3 Click the Tracing byte J1 tab. Double-click J1 to be Sent([Mode]Content). Set Input in Text
Format, Byte Mode, and Input Mode for overhead bytes.
Step 4 Click OK.

Step 5 Double-click J1 to be Received([Mode]Content). Set Input in Text Format, Byte Mode, and
Step 6 Click OK.
Step 7 Click Query to query J1 Received([Mode]Content).
----End
2.18.3 Configuring the Signal Flag Byte C2

The C2 byte specifies the multiplex structure and the service type such as PDH services. This
topic describes how to configure the C2 byte on the T2000.
Prerequisite
NOTE
The C2 byte of this VC-3/VC-4 can be set or queried only when cross-connections at the VC-3/VC-4 level
are created.
The T2000 processes the write/read attributes of overhead bytes in the extended mode or general mode. In
the extended mode, the T2000 has more capacities to process the write/read attributes of overhead bytes.
Set the C2 byte only after the mode is set to the extended mode.
Procedure
Step 1 Right-click the NE icon on the Main Topology, and choose NE Explorer from the shortcut
menu.
Step 2 Select 27-OSB4A from the Object Tree. Choose Configuration > Overhead Management >
VC4 Path Overhead from the Function Tree.
Step 3 Click the Signal Flag C2 tab and click Options. Set the mode to Extended Mode in the dialog
box that is displayed. Click OK.
Step 4 Click Query to query C2 to be Received.
Step 5 Set C2 to be Sent and C2 to be Received. Click OK in the dialog box that is displayed.
Step 6 Click Apply.
----End

2.19 Configuring the Orderwire

This topic describes how to configure the orderwire on the T2000. If the NE is provisioned with
an orderwire, the network maintenance personnel can use the orderwire as a private
communication channel during emergencies.
2.19.1 Configuring the Orderwire of NE1–NE3
This topic describes how to configure the orderwire of NE1–NE3.
2.19.2 Configuring the Orderwire of NE4
This topic describes how to configure the orderwire of NE4.
This topic describes how to configure the orderwire of NE5 on the T2000.
2.19.1 Configuring the Orderwire of NE1–NE3

This topic describes how to configure the orderwire of NE1–NE3.
Prerequisite
l The NEs and boards must be created on the T2000.
l The orderwire board must be installed correctly.
Precautions
CAUTION
Make sure that the call waiting time of each node is the same. When 30 or less nodes exist, set
the call waiting time to 5s. When more than 30 nodes exist, set the call waiting time to 9s.
Procedure
menu.
Step 2 Select NE1 in the upper left pane and choose Configuration > Orderwire from the Function
Tree.
Step 3 Click the General tab and see Figure 2-10 to set the following parameters:
l Call Waiting Time(s): 5
l Conference Call: 9999
l Phone 1: 1001
l Available Orderwire Port: 27-OSB4A-1, 28-OSB4A-1

Step 4 Click Apply.

Step 5 Click the Conference Call tab. Select 27-OSB4A-1 and 28-OSB4A-1 into Selected Conference
Call Port.
Step 6 Click Apply.
Step 7 Refer to Steps 1–5 to set the orderwire of NE2 and NE3. For the orderwire phone numbers of
NE2 and NE3, see Figure 2-10.
----End

This topic describes how to configure the orderwire of NE4.
Prerequisite
Procedure
menu.
Tree.
l Call Waiting Time: 5
l Phone 1: 1004

l Available Orderwire Port: 27-OSB4A-1, 10-SL1A-1
Step 4 Click Apply.
Step 5 Click the Conference Call tab. Select 27-OSB4A-1 and 10-SL1A-1 into Selected Conference
Call Port.
Step 6 Click Apply.
----End

This topic describes how to configure the orderwire of NE5 on the T2000.
Prerequisite
Procedure
menu.
Tree.
l Call Waiting Time: 5
l Phone 1: 1005
l Available Orderwire Port: 27-OSB4A-1
Step 4 Click Apply.
Step 5 Click the Conference Call tab. Select 27-OSB4A-1 into Selected Conference Call Port.
Step 6 Click Apply.
----End
2.20 Enabling/Disabling Performance Monitoring

This topic describes how to enable or disable the performance monitoring function on the T2000.
The performance parameters are used to monitor the equipment and analyze the network. This
topic describes how to enable or disable the performance monitoring function on the T2000.
Prerequisite
You must be an NM user with "NE and network administrator" authority or higher.

NOTE
Normally, all performance parameters are set to the default values. Hence, you only need to start the
performance monitoring. You can also set the performance parameters according to the requirements.
Procedure
Step 1 Choose Configuration > NE Time Synchronization from the Main Menu.
Step 2 Select NE1 to NE5 from the Object Tree and click .
Step 3 Set Synchronous Mode of each NE to NM.
Step 4 Click Apply.
Step 5 Select NE1 to NE5 and right-click to select Synchronize with NM Time. Click Yes in the dialog
box that is displayed.
Step 6 A dialog box is displayed, indicating that the operation is successful. Click Close.
Step 7 Choose Performance > NE Performance Monitoring Time from the Main Menu.
Step 8 Select NE1 and click . Set the parameters as follows:

l Set 15-Minute Monitoring: Enabled
l Set 24-Hour Monitoring: Enabled
l From: Set the parameters according to the requirements and make sure that the time is later
than the current time of the NM and NE.
Step 9 Click Apply.

Step 10 Refer to Steps 7–9 to set the performance parameters for NE2 and NE3.
----End
2.21 Setting Alarm Parameters

This topic describes how to set the alarm parameters on the T2000. To prevent the alarm data
from overflowing or to prevent damage to the alarm data, you need to dump the alarm data in
time.
Prerequisite
NOTE
Normally, all alarm parameters except Dumping Condition are set to the default values. You can also set
alarm parameters depending on the actual situations. For details, see the alarm setting part in the OptiX
iManager T2OOO Help.
NOTE
It is recommended that you set all the alarm and performance parameters to the default values.
Procedure
Step 1 Choose System > Database > Dump Settings from the Main Menu.
Step 2 Select Alarm Data in the Dump Settings dialog box. If the record needs to be dumped
periodically, set Yes for Periodic dump. The default value is commonly used and can also be
set based on the actual conditions.

Step 3 Click OK.
----End
2.22 Configuring Automatic Laser Shutdown

The automatic laser shutdown (ALS) is performed before the output power of the laser
transmitter and the optical amplifier reaches a dangerous level. This topic considers the XCS4A
as an example to describe how to configure the ALS.
Prerequisite
Procedure
Step 1 Right-click the NE1 icon in the Main Topology, and choose NE Explorer.
Step 2 Select 27-OSB4A from the Object Tree and choose Configuration > Automatic Laser
Shutdown from the Function Tree. For a detailed description of the parameters for configuring
the ALS, refer to Table 2-8.
Step 3 Set the Automatic Shutdown parameter to Enabled. Set the other parameters to the default
values.

Step 4 Click Apply.
----End
Parameters
For a detailed description of the parameters for configuring the ALS, refer to Table 2-8.
Table 2-8 Parameters for configuring the ALS
Parameter Value Range Default Value Description
Automatic Enabled, Disabled Specifies whether to automatically

Shutdown Disabled shut down the laser. You can set
start time, shutdown time, and
constantly-on period only when
auto shutdown is set as Enabled.
On Period (ms) 0–655350 2000 Indicates the time to start the laser
automatically to test whether the
fiber is normal after the laser is shut
down.
Off Period (ms) 0–655350 60000 Indicates the time for auto laser
shutdown.
Continuously 0–655350 90000 Indicates the time to start the laser

On-Test Period manually to test whether the fiber is
(ms) normal after the laser is shut down.
2.23 Backing Up the NE Configuration Data

This topic describes how to back up the NE configuration data on the T2000. To prevent data
loss, back up the NE configuration data after the configuration is complete.
Prerequisite
Precautions
NOTE
Ensure that no abnormal alarm or performance event exists before backing up the NE database.
Procedure
Step 1 Choose Configuration > Configuration Data Management from the Main Menu.

Step 2 Select NE1 to NE5 from the Object Tree on the left and click .
Step 3 Select the records of NE1–NE5 and choose Back Up NE Database > Back Up to SCC. Click
OK in the dialog box that is displayed.
Step 4 A dialog box is displayed, indicating that the backup is successful. Click Close.
----End
2.24 Backing Up the T2000 Configuration Data

To prevent data loss, back up the T2000 configuration data after the configuration is complete.
This topic describes the immediate data backup and the periodic data backup on the T2000.
2.24.1 Immediate Backup
This topic describes how to back up the T2000 configuration data immediately on the T2000.
2.24.2 Periodic Backup
This topic describes how to back up the T2000 configuration data periodically on the T2000.
2.24.1 Immediate Backup

This topic describes how to back up the T2000 configuration data immediately on the T2000.
Prerequisite
l After configuration, check whether there are any alarms or performance events before
performing the following operations.
NOTE
The default password of the T2000 superuser admin is T2000. The superuser should be modified after the
T2000 system is installed.
Procedure
Step 1 Optional: Choose File > Log Out from the Main Menu. In the dialog box that is displayed,
click OK.
Step 2 Optional: Enter the user information in the Login interface.

l User Name: admin
l Password: T2000
NOTE
Steps 1 and 2 are optional. If the login user is already admin, start with Step 3.
Step 3 Choose System > NMS Security Settings > Single User Mode from the Main Menu. In the
dialog box that is displayed, click OK.

CAUTION
When Single User Mode is chosen, the users other than admin are forcibly logged out.
Step 4 Choose System > Database > Database Backup from the Main Menu. Click Backup and the
system backs up the NM database to the appointed directory immediately.
----End
2.24.2 Periodic Backup

This topic describes how to back up the T2000 configuration data periodically on the T2000.
Prerequisite
l After the configuration, check whether any abnormal alarms or performance events are
generated before performing the following operations.
NOTE
The default password of the T2000 superuser admin is T2000. The password of the superuser should be
modified after the T2000 system is installed.
Procedure
Step 1 Optional: Choose File > Log Out from the Main Menu. In the dialog box displayed, click
OK.
Step 2 Optional: Enter the following user information in the Login interface:
l User Name: admin
l Password: T2000
NOTE
Steps 1 and 2 are optional. If the login user is already admin, start with Step 3.
Step 3 Choose System > NE Security Management > NE User Management from the Main Menu.
In the dialog box that is displayed, click OK.

CAUTION
When Single User Mode is chosen, the users other than admin are forcibly logged out.
Step 4 Choose System > Schedule Task Management from the Main Menu. In the dialog box that is
displayed, click OK.
Step 5 Click New. Choose Task Type and set Task Name to Backup periodically in the Task
Creation Wizard dialog box.
Step 6 Click Next and confirm the backup directory on the server side. Then, click Next.
Step 7 Set running period to Weekly and click Next.
Step 8 Click Finish. Then, the system backs up the T2000 database to the appointed directory
periodically according to the backup period.
----End

Configuration Guide 3 Configuring Services in Different Protection Schemes
3 Configuring Services in Different Protection

Schemes
About This Chapter
This topic describes the service configuration methods in different protection schemes. It also
describes the service configuration of an SNCP ring with non-protection chains and the service
configuration of an SNCP ring with 1:1 linear MSP chains. After you are familiar with the
concepts, you can create a protection subnet quickly and correctly.
NOTE
For the configuration of an MSP ring and 1+1 linear MSP chain, see 2.13 Configuring Protection.
3.1 Networking Diagram

This topic describes the network architecture and the timeslot allocation.
3.2 Information of Boards on Each NE
This topic describes the information of boards on each NE.
3.3 SNCP Ring with Non-Protection Chains
This topic describes how to configure a protection subnet, which is an SNCP ring with non-
protection chains.
3.4 SNCP Ring with 1:1 Linear MSP Chains
A 1:1 linear MSP chain is different from a non-protection chain, and requires that two fibers are
created on the T2000.

3 Configuring Services in Different Protection Schemes Configuration Guide
3.1 Networking Diagram

This topic describes the network architecture and the timeslot allocation.
Figure 3-1 shows the networking diagram.
NE1 (A)
T2000
NE2 (B) NE4 (D) STM-1 chain NE5 (E)

STM-4 two-fiber
directional ring
NE3 (C)
Figure 3-2 shows the timeslot allocation between NEs.
Figure 3-2 Timeslot allocation diagram

Ring
Station
NE1 NE2 NE3 NE4 NE1
VC12:1-12
1#VC4 t4:1-12
Line
Station NE4 NE5

Timeslot 10-SL1A-1 27-OSB1A-1
VC12:1-12
t4:1-12
1#VC4
Forward
Add/Drop
3.2 Information of Boards on Each NE

This topic describes the information of boards on each NE.

Figure 3-3 shows the board layout of NE1. Figure 3-4 shows the board layout of NE2 and NE3.
Figure 3-5 shows the board layout of NE4. Figure 3-6 shows the board layout of NE5.

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S P
C I
X X
T T P P P C U A
C C
7 7 T T T U
S S
5 5 1 1 1 X
S P
4 4 P
S S
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S P
C I
X X
T P C U A
C C
A T U
S S
1 1 X
S P
4 4
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S P
C I
X X S S
T P C U A
C C L L
A T U
S S 1 1
1 1 X
S P
4 4 A A
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S P
C I
X X
T P C U A
C C
A T U
S S
1 1 X
S P
1 1
C I
A A
C U
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18
3.3 SNCP Ring with Non-Protection Chains

This topic describes how to configure a protection subnet, which is an SNCP ring with non-
protection chains.
If NE1, NE2, NE3, and NE4 described in 2 Configuring SDH/PDH Services form an SNCP
ring, you need not configure the protection subnet for the ring before you configure the SDH
services.
3.3.1 Configuring a Non-Protection Chain
This topic describes how to configure a non-protection chain.
3.3.2 Configuring SNCP Services
This topic describes how to configure the SNCP services.
3.3.1 Configuring a Non-Protection Chain

This topic describes how to configure a non-protection chain.
Prerequisite
Procedure
Step 1 Choose Protection Subnet > Create SDH Protection Subnet > NP Chain from the Main
Menu. Then, Wizard for Creating Chain Without Protection is displayed.
Step 2 Set the following parameters in the Wizard for Creating Chain Without Protection dialog
box:
l Name: NP_Chain_1
l Level: STM-1

Step 3 Double-click the icons of NE4 and NE5. Then, the NEs are added into the protection subnet.
Then, click Next.
Step 5 A dialog box is displayed indicating that the protection subnet is successfully created. Click
Close.
----End

This topic describes how to configure the SNCP services.
Prerequisite
Procedure
Step 1 To configure the services on NE3, do as follows:
1. Right-click the NE3 icon on the Main Topology, and choose NE Explorer from the
shortcut menu.
2. Select NE3 in the upper left pane and choose Configuration > SDH Service
Configuration from the Function Tree. Click .
3. See Figure 3-2 and configure the SNCP services from NE3 to NE5 to be dually fed from
NE3. Click Create SNCP Service. Set the following parameters in the Create SNCP
Service dialog box:
l Service Type: SNCP
l Level: VC12
l Source Slot (for the working service): 28-OSB4A-1 (SDH-1)
l Source Timeslot Range (for the working service): 1–12
l Source Slot (for the protection service): 27-OSB4A-1 (SDH-1)
l Source Timeslot Range (for the protection service): 1–12
l Sink Slot: 4-PT1
l Set the other parameters to the default values.
4. Select the Activate Immediately check box and click OK.


shortcut menu.
3. According to Figure 3-2, configure the E1 service from NE3 to NE5 that passes through
NE2: from timeslots 1–12 of the first VC-4 on the 27-OSB4A optical interface board to
timeslots 1-12 of the first VC-4 on the 28-OSB4A optical interface board. Click Create.
Set the following parameters in the Create SDH Service dialog box:
l Level: VC12
l Source VC4: VC4-1
l Sink Slot: 28-OSB4A -1(SDH-1)
l Sink VC4: VC4-1
4. Click OK.


NOTE
Service configuration on NE1 is the same as the service configuration on NE2. You can refer to
"Configuring Services on NE2" in this topic.

shortcut menu.
3. See Figure 3-2 and configure the SNCP services from NE3 to NE5 to be selectively
received at NE4. Click Create SNCP Service. Set the following parameters in the Create
SNCP Service dialog box:
l Level: VC12
l Source Slot (for the working service): 27-OSB4A-1 (SDH-1)
l Source Timeslot Range (for the working service): 1–12
l Source Slot (for the protection service): 28-OSB4A-1 (SDH-1)
l Source Timeslot Range (for the protection service): 1–12
l Sink Slot: 10-SL1A(SDH-1)
4. Select the Activate Immediately check box and click OK.


shortcut menu.
3. According to Figure 3-2, create the E1 services from NE3 to NE5: from timeslots 1–12 in
the first VC-4 of the 27-OSB1A optical interface board to timeslots 1–12 of the first VC-4
on the 4-PT1 board. Click Create. Set the following parameters in the Create SDH
Service dialog box:
l Level: VC12
l Source VC4: VC4-1
l Sink Slot: 4-PT1
4. Click OK.
----End

3.4 SNCP Ring with 1:1 Linear MSP Chains

A 1:1 linear MSP chain is different from a non-protection chain, and requires that two fibers are
created on the T2000.
This topic describes the differences in terms of service configuration between an SNCP ring
with 1:1 linear MSP chains and an SNCP ring with non-protection chains (described in 3.3 SNCP
Ring with Non-Protection Chains).
Table 3-1 provides the fiber/cable connection relations between NE4 and NE5.
Table 3-1 Fiber/Cable connection between NE4 and NE5
Fiber/ NE-Slot-Board NE-Slot-Board

Cable
1 NE4-10-SL1A NE5-27-OSB1A
2 NE4-11-SL1A NE5-28-OSB1A
3.4.1 Configuring a 1:1 Linear MSP Subnet

This topic describes how to create 1:1 linear MSP.
This topic describes how to configure SNCP services.
3.4.1 Configuring a 1:1 Linear MSP Subnet

This topic describes how to create 1:1 linear MSP.
Prerequisite
Procedure
Step 1 Choose Protection Subnet > Create SDH Protection Subnet > M:N linear MSP from the
Main Menu. Then, the Wizard for Creating M:N Linear MSP Chain dialog box is displayed.
Step 2 Set the following parameters in the Wizard for Creating M:N Linear MSP Chain dialog box:
l Name: 1:N_MSP_1
l Level: STM-1
Step 3 Double-click the icons of NE4 and NE5. Then, the NEs are added into the protection subnet.
Then, click Next.

Step 5 A dialog box is displayed indicating that the protection subnet is successfully created. Click
Close.
----End

This topic describes how to configure SNCP services.
The SNCP service configuration is the same as the service configuration described in 3.3.2
Configuring SNCP Services.

Configuration Guide 4 Configuring Ethernet Services
4 Configuring Ethernet Services
About This Chapter
This topic describes how to configure Ethernet private line (EPL), Ethernet private local area
network (EPLAN), Ethernet virtual private line (EVPL), and Ethernet virtual private local area
network (EVPLAN) services on the T2000. This topic also describes the related engineering
requirements and engineering information.
Table 4-1 lists the Ethernet services that are supported by Ethernet boards of the OptiX OSN
2000.
Table 4-1 Mapping relation between Ethernet boards and Ethernet services
Item EPL EVPL EPLAN EVPLAN
EFT0 Supported Not supported Not supported Not supported
EFT8A Supported Not supported Not supported Not supported
EFT8B Supported Not supported Not supported Not supported
EMS1 Supported Supported Supported Supported
4.1 Configuring Transparent Transmission EPL Services by Using the Per-NE Configuration
Function
The transparent transmission EPL services execute point-to-point interconnected services that
cannot share the SDH bandwidth. You can configure the transparent transmission EPL services
on the T2000 by using the trail function or by using the per-NE configuration function. This
topic describes how to configure the point-to-point EPL services by using the per-NE
4.2 Configuring Transparent Transmission EPL Services by Using the Trail Function
The point-to-point EPL services execute point-to-point interconnected services that cannot share
the SDH bandwidth. You can configure the transparent transmission EPL services on the T2000
by using the trail function or by using the per-NE configuration function. This topic describes
how to configure the transparent transmission EPL services by using the trail function. The trail
function cannot be used to configure end-to-end services.

4 Configuring Ethernet Services Configuration Guide
4.3 Configuring PORT-Shared EVPL Services by Using the Per-NE Configuration Function
The PORT-shared EVPL services execute point-to-point interconnected services that cannot
share the SDH bandwidth. You can configure the PORT-shared EVPL services on the T2000
how to configure the PORT-shared EVPL services by using the per-NE configuration function.
4.4 Configuring PORT-Shared EVPL Services by Using the Trail Function
by using the trail function or by using the per-NE configuration function. This topicdescribes
how to configure the PORT-shared EVPL services by using the trail function. The trail function
cannot be used to configure end-to-end services.
4.5 Configuring VCTRUNK-Shared EVPL Services by Using the Per-NE Configuration
Function
The VCTRUNK-shared EVPL services execute point-to-point interconnected services that share
the SDH bandwidth. You can configure the VCTRUNK-shared EVPL services on the T2000
how to configure the VCTRUNK-shared EVPL services by using the per-NE configuration
function.
4.6 Configuring VCTRUNK-Shared EVPL Services by Using the Trail Function
how to configure the VCTRUNK-shared EVPL services by using the trail function.
4.7 Configuring the Ingress/Egress EVPL Services by Using the Per-NE Configuration Function
When the data of multiple users is transmitted on the same VCTRUNK, the ingress/egress EVPL
service is used to isolate the data by using the VLAN ID and MPLS labels. You can configure
the ingress/egress EVPL service on the T2000 by using the per-NE configuration function.
4.8 Configuring the Transit EVPL Service by Using the Per-NE Configuration Function
The EVPL services of different users can share the same VCTRUNK, where switching of the
MPLS labels ensures the interworking between the MPLS networks. You can configure the
transit EVPL service on the T2000 by using the per-NE configuration function.
4.9 Configuring the 802.1d Bridge-Based EPLAN Service by Using the Per-NE Configuration
Function
The EPLAN service implements the dynamic sharing of the Ethernet service bandwidth between
multiple points, thus meeting the requirements of the dynamic features of the data services and
saving the bandwidth resources. You can configure the 802.1d bridge-based EPLAN service on
the T2000 by using the trail function or by using the per-NE configuration function. This topic
describes how to configure the 802.1d bridge-based EPLAN service by using the single station
function.
4.10 Configuring the 802.1q Bridge-Based EVPLAN Service by Using the Per-NE
The EVPLAN service implements the dynamic sharing of the Ethernet service bandwidth
between multiple points, thus meeting the requirements of the dynamic features of the data
services and saving the bandwidth resources. You can configure the 802.1q bridge-based
EVPLAN service on the T2000 by using the trail function or by using the per-NE configuration
function. This topic describes how to configure the 802.1q bridge-based EVPLAN service by
using the per-NE configuration function.
4.11 Configuring the 802.1q Bridge-Based EVPLAN Service by Using the Trail Function

function. This topicdescribes how to configure the 802.1q bridge-based EVPLAN service by
using the trail function.
4.12 Configuring the MPLS-Based EVPLAN Service by Using the Per-NE Configuration
Function
The EVPLAN service uses the MPLS technology. The transmission efficiency is lower than the
transmission efficiency of the EPLAN service and the configuration is more complex. Therefore,
the EPLAN is recommended unless EVPLAN needs to be used to meet certain special
requirements. You can configure the MPLS-based EVPLAN service on the T2000 by using the
per-NE configuration function.

4.1 Configuring Transparent Transmission EPL Services by

Using the Per-NE Configuration Function
The transparent transmission EPL services execute point-to-point interconnected services that
cannot share the SDH bandwidth. You can configure the transparent transmission EPL services
on the T2000 by using the trail function or by using the per-NE configuration function. This
topic describes how to configure the point-to-point EPL services by using the per-NE
4.1.1 Engineering Requirements
The completely isolated data services of two companies at a station must be transported to
another station through the multi-service transport platform (MSTP) equipment.
4.1.2 Engineering Planning
The engineering design department conducts planning based on the preceding requirements and
the engineering information described in Chapter 1, and outputs the engineering information
mentioned in This topic.
4.1.3 Configuration Process
This topic describes how to configure transparent transmission EPL services on the T2000, by
4.1.4 Creating a Board
Ethernet boards need to be added to the NE based on the type and volume of the service. This
topic describes how to create a board.
4.1.5 Configuring the Data of NE1

In the example provided in Chapter 2, Ethernet services need to be added. The requirements for
the Ethernet services are listed in this topic.
l The two companies A and B at NE1 must transmit data services to NE3 through the MSTP
equipment.
l The services of companies A and B must be isolated completely.
l Company A requires a 10 Mbit/s bandwidth, and company B requires a 20 Mbit/s
bandwidth.
l The equipment of companies A and B provides the 10M/100M autosensing Ethernet
electrical ports for the interconnection with the MSTP.


l Networking diagram
l Board layout of each NE
l Service configuration diagram of each NE
l Timeslot allocation diagram
Networking Diagram
Figure 4-1 shows the Ethernet service networking and port allocation.
Figure 4-1 Ethernet service networking and port allocation

A B
PORT1 PORT2
T2000
NE1
STM-1 linear MSP
chain
NE2 STM-4 two-fiber
NE4
bidirectional MSP ring
NE3
PORT1 PORT2 VCTRUNK
A B
Board Information of Each NE

The Ethernet boards should be added to the NEs according to the service type and traffic volume
of the new service. NE1 and NE3 need to be added with one EFT0 and one ETFS8. Figure
4-2 shows the board layout of NE1. Figure 4-3 shows the board layout of NE3.


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C F T U
F
5 5 1 1 S S T 1 S X
4 4 S
S S 0 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C F T U
1 1 S S T F X
4 4 S
0 PIU
A A
8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18
Service Configuration Diagram of Each NE

Figure 4-4 shows the service configuration diagram of NE1 and NE3.
Figure 4-4 Service configuration diagram
PORT VCTRUNK VCTRUNK PORT
PORT1 PORT1
A A
10 Mbit/s VCTRUNK1 SDH VCTRUNK1 10 Mbit/s
VC4-2: VC12-1 to VC4-2: VC12-1 to
PORT2 VC12-5 VC12-5 PORT2
B VCTRUNK2 VCTRUNK2 B
20 Mbit/s 20 Mbit/s
VC4-2: VC12-6 to VC4-2: VC12-6 to
VC12-15 VC12-15
NE1
NE3

NOTE
l On the EFT0, only VC4-2 can bind VC-12 paths and VC4-1 to VC4-2 can bind VC-3 paths.
l One VC-4 can be used to bind paths of only the VC-12 or VC-3 level.
Table 4-2 lists the mapping relation of Ethernet service connection.
Table 4-2 Ethernet service connection
Item A B
NE NE1
Slot-board-port 9-EFT0-1 9-EFT0-2
Timeslot VC4-2: VC12-1–VC12-5 VC4-2: VC12-6–VC12-15
VCTRUNK VCTRUNK1 VCTRUNK2
Bound bandwidth 5xVC-12 10xVC-12
Working mode of PORT Auto-negotiation Auto-negotiation
NE NE3
Timeslot Allocation Diagram

Figure 4-5 shows the SDH timeslot allocation.
Figure 4-5 SDH timeslot allocation for Ethernet services

Ring
Station NE1 NE2 NE3 NE4 NE1
1#VC4
VC12:1-15
2#VC4
9-EFT0:VC4-2: 9-EFT0:VC4-2:
VC12:1-15 VC12:1-15
Add/Drop


This topic describes how to configure transparent transmission EPL services on the T2000, by
NOTE
This topic describes the procedures and precautions for configuring Ethernet services on the T2000. For
details, see the OptiX iManager T2000 Operation Guide for SDH.
Table 4-3 lists the procedures for configuring the point-to-point transparent transmission EPL
service for the EFT0 board on the T2000.
Table 4-3 Process of point-to-point transparent transmission EPL service configuration

Procedur Operation Remarks
e
1 Creating a board Required
2 Configuring port attributes of the Ethernet board and Required

bound paths
3 Configuring the transparent transmission EPL In the case of the

service Ethernet transparent
transmission board
EFT0/EFT8A/EFT8B,
the T2000 automatically
creates the EPL service.
In the case of the
Ethernet switching
board EMS1 board, you
need to create the EPL
service manually.
4 Creating a cross-connection between the Ethernet Required

board and the line board

Ethernet boards need to be added to the NE based on the type and volume of the service. This
topic describes how to create a board.
Prerequisite
l The Ethernet boards must support the EPL function and must be inserted in the correct
slots.
l The fibers and the protection subnet must be created.

Precautions
NOTE
You can also configure the EMS1 boards on the NE to transparently transmit EPL services. Note the
following items when configuring transparent transmission EPL services:
l PORT1 is the GE port on the EMS1 board. PORT2 to PORT7 are the FE ports on the Ethernet interface
board.
l VCTRUNK1 to VCTRUNK12 can be bound with VC4-1 only. VCTRUNK13 to VCTRUNK24 can
be bound with VC4-2 only.
l Paths of VC-3 or VC-12 level can be bound in VC4-1 or VC4-2. But paths at only one of the two levels
can be bound in a VC-4.
l Set Entry Detection of the internal port and external port to Disabled.
l Configure EPL services manually to create the mapping relation between PORTs and VCTRUNKs.
Procedure
Step 1 In the Main Topology, double-click the NE1 icon. Then, the NE panel is displayed.
Step 2 Right-click slot 09 according to the board layout shown in Figure 4-2 and select EFT0 from
the shortcut menu. Right-click slot 16 and select ETFS8 from the shortcut menu.
Step 3 Make sure that the EFT0 board is configured in slot 9 and the EFT8 board is configured in slot
16. Click to exit the NE panel diagram.
Step 4 Refer to Steps 1–3 to create the Ethernet board of NE3. Figure 4-3 shows the board layout of
NE3.
----End

Prerequisite
slots.
Precautions
NOTE
On the EFT0 board, only PORT5 to PORT8 support Jumbo frames whose maximum frame length is 9600
bytes. PORT1 to PORT4 support only frames whose maximum frame length is 6154 bytes.
NOTE
The EFT0 supports three mapping protocols: GFP, LAPD and HDLC. The EMS1 supports only one
mapping protocol: GFP. Currently, the GFP is the mainstream mapping mode. Hence, set the mapping
protocol to GFP unless another protocol is specified. The mapping protocol at the local NE must be the
same as the mapping protocol at the opposite NE.

Procedure
Step 1 Configure Ethernet external ports as follows:
1. Right-click the NE1 icon in the Main Topology, and choose NE Explorer.
2. Select 9-EFT0 from the Object Tree and choose Configuration > Ethernet Interface
Management > Ethernet Interface . Click .
3. Choose External Port > Basic Attributes and set the parameters of PORT1 and PORT2
as follows:
l Enabled/Disabled: Enabled
l Working Mode: Auto-Negotiation
l Maximum Frame Length: Set it according to the connected Ethernet equipment, and
adopt the default value of 1522 in normal cases.
l For other parameters, adopt the default values.
4. Click Apply.
Step 2 Configure Ethernet internal ports as follows:

1. Choose Internal Port > Encapsulation/Mapping and set the parameters as follows:
l Mapping Protocol: GFP (recommended)
2. Click Apply.
3. Click the LCAS tab and set the attributes of VCTRUNK1 and VCTRUNK2:
l Enabling LCAS: Enabled
NOTE
To use the LCAS function, you must set the equipment at both ends to the same LCAS mode.
l If Huawei equipment is used at the local and the opposite stations, select Huawei Mode.
l If Huawei equipment interconnects with the equipment from other vendors, select Standard
Mode for the equipment at the local and opposite ends.
l If the equipment from other vendors does not support Standard Mode, select Huawei Mode.
4. Click Apply.
Step 3 Configure bound paths as follows:

1. In the Internal Port page, click the Bound Path tab.
2. Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
3. To set bound paths for VCTRUNK1, set the following parameters in the dialog box:
l Level: VC12-xv

l Service Direction: Bidirectional

l Available Resources: VC4-2
l Select VC12-1–VC12-5 in Available Timeslots. Click .

4. To set a bound path for VCTRUNK2, set the following parameters in the dialog box:
l Level: VC12-xv

5. Click OK.
Step 4 Configure the cross-connections from the Ethernet boards to the SDH line boards.
1. Select NE1 from the Object Tree.
2. Choose Configuration > SDH Service Configuration from the Function Tree.
3. Click Create, and the Create SDH Service dialog box is displayed.
4. See Figure 4-5 and set the following parameters in the dialog box:
l Level: VC12
l Source Slot: 9-EFT0-1(SDH-1)
l Source VC4: VC4-2
l Source Timeslot Range (e.g. 1, 3–6): 1–15
l Sink VC4: VC4-2

l Sink Timeslot Range (e.g. 1, 3–6): 1–15

5. Click OK.
----End
Parameters
Table 4-4 Parameters of basic attributes

Enabled/ Enabled, Disabled Specifies the enabled or disabled

Disabled Disabled state of the port. "Enabled" means
that this port is allowed to access the
services. "Disabled" means that this
port is not allowed to access the
services.

Working Mode Auto- Auto- The auto-negotiation mode is

Negotiation, Negotiation recommended, because it can
10M Half- automatically detect the best
Duplex, 10M working mode to combine a port
Full-Duplex, and its interconnected port. Hence it
100M Full- facilitates maintenance.
Duplex, 100M During the configuration, make
Half-Duplex, sure that the working modes of the
1000M Half- connected ports are the same. If the
Duplex, 1000M working modes are different, the
Full-Duplex services are unavailable.
Maximum l 1518–1535 1522 l This parameter should be larger

Frame Length (EFT0/ than the maximum frame length
EFT8A/ of the data frame to be
EFT8B) transmitted.
l 1518–9600 l In the case of the EFT0/EFT8A/
(EMS1) EFT8B board, this parameter is
invalid. For JUMBO frames. In
the case of the EMS1 board, this
parameter has a restriction on
JUMBO frames.
l If JUMBO frames need not be
considered, it is recommended
that you adopt the default value
for this parameter when the
accessed services are the
Ethernet frames that have the
layer 1 VLAN labels or do not
have the VLAN label.
MAC Loopback Non-Loopback, Non-Loopback Specifies the loopback state at the

Inloop MAC layer.
PHY Loopback Non-Loopback, Non-Loopback Specifies the loopback state at the

Inloop PHY layer.
Table 4-5 Parameters for configuring the bound paths

Configurable VCTRUNKn VCTRUNK1 You need to select the value

Ports according to the actual service
requirement.
Level VC3-xv, VC4- - Indicates the level of VCTRUNK-

xv, VC12-xv bound path.

Direction Bidirectional, Bidirectional Indicates the direction of the

Uplink, service.
Downlink
Available - - Indicates the available paths.

Resources
Available - - Indicates the available timeslots.

Timeslots

Prerequisite
l The Ethernet boards must support the EPL function. In addition, they must be inserted in
the correct slots.
Procedure
Step 2 Choose Configuration > SDH Service Configuration from the Function Tree.
Step 3 According to Figure 4-5, configure the service from NE1 to NE3 that passes through NE2: from
timeslots 1–52 of the first VC-4 on the 27-OSB4A optical interface board to timeslots 1-52 of
the first VC-4 on the 28-OSB4A optical interface board.
Step 4 Click Create. Set the following parameters in the Create SDH Service dialog box:
l Level: VC12
l Source VC4: VC4-2
l Source Timeslot Range (e.g. 1, 3–6): 1-15
l Sink VC4: VC4-2
l Sink Timeslot Range (e.g. 1, 3–6): 1-15

Step 5 Click OK.
----End

Prerequisite
slots.
Procedure
Step 1 Configure the Ethernet ports as follows:

2. Select 9-EFT0 from the Object Tree and choose Configuration > Ethernet Interface
as follows:
4. Click Apply.
5. Choose Internal Port > Encapsulation/Mapping and set the attributes of VCTRUNK1
and VCTRUNK2 as follows:
l Mapping Protocol: GFP (recommended)
6. Click Apply.
7. Click the LCAS tab and set the parameters as follows:
8. Click Apply.

1. In the Internal Port page, select the Bound Path tab.
2. Click Configure, and the bound path configuration dialog box is displayed.
3. To configure bound paths of VCTRUNK1, set the parameters In the dialog box as follows:
l Configurable Ports: VCTRUNK1
l Level: VC12-xv

l Level: VC12-xv

5. Click OK.

l Level: VC12
l Source Slot: 9-EFT0-1(SDH-1)
l Source VC4: VC4-2
l Sink VC4: VC4-2
5. Click OK.
----End
4.2 Configuring Transparent Transmission EPL Services by

Using the Trail Function
The point-to-point EPL services execute point-to-point interconnected services that cannot share
the SDH bandwidth. You can configure the transparent transmission EPL services on the T2000
how to configure the transparent transmission EPL services by using the trail function. The trail
function cannot be used to configure end-to-end services.
NOTE
l This topic describes the procedures and precautions for configuring Ethernet services on the T2000.
For details, see the OptiX iManager T2000 Operation Guide for SDH.

This topic describes how to configure the transparent transmission EPL services by using the
trail function on the T2000.
4.2.4 Creating a Trunk Link
This topic describes how to create a trunk link when a point-to-point EPL service is configured
by using the trail function, including the configuration steps and the parameter setting.
4.2.5 Creating an EPL Trail
This topic describes how to create an EPL trail when a point-to-point EPL service is configured


l The two companies A and B at NE1 must transmit data services to NE3 through the MSTP
equipment.
l The services of companies A and B must be isolated completely.
l Company A requires a 10 Mbit/s bandwidth, and company B requires a 20 Mbit/s
bandwidth.
l The equipment of companies A and B provides the 10M/100M autosensing Ethernet
electrical ports for the interconnection with the MSTP.

Networking Diagram


A B
PORT1 PORT2
T2000
NE1
STM-1 linear MSP
chain
NE2 STM-4 two-fiber
NE4
bidirectional MSP ring
NE3
PORT1 PORT2 VCTRUNK
A B

The Ethernet boards should be added to the NEs according to the service type and traffic volume
of the new service. NE1 and NE3 need to be added with one EFT0 and one ETFS8. Figure
4-7 shows the board layout of NE1. Figure 4-8 shows the board layout of NE3.

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C F T U
F
5 5 1 1 S S T 1 S X
4 4 S
S S 0 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C F T U
1 1 S S T F X
4 4 S
0 PIU
A A
8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

PORT1 PORT1
A A
10 Mbit/s VCTRUNK1 SDH VCTRUNK1 10 Mbit/s
VC4-2: VC12-1 to VC4-2: VC12-1 to
PORT2 VC12-5 VC12-5 PORT2
B VCTRUNK2 VCTRUNK2 B
20 Mbit/s 20 Mbit/s
VC4-2: VC12-6 to VC4-2: VC12-6 to
VC12-15 VC12-15
NE1
NE3
NOTE
l On the EFT0, only VC4-2 can bind VC-12 paths and VC4-1 to VC4-2 can bind VC-3 paths.
l One VC-4 can be used to bind paths of only the VC-12 or VC-3 level.
Item A B
NE NE1

Item A B
NE NE3


Ring
1#VC4
VC12:1-15
2#VC4
9-EFT0:VC4-2: 9-EFT0:VC4-2:
VC12:1-15 VC12:1-15
Add/Drop

This topic describes how to configure the transparent transmission EPL services by using the
trail function on the T2000.
NOTE
Ethernet service can be created by using the trail function or by using the per-NE configuration function.
If you purchase the license with trail function, you can create Ethernet service by using the trail function.
Otherwise, you can create Ethernet service only by using the per-NE configuration function.
Table 4-7 provides the process of creating the point-to-point transparent transmission EPL
service by using the trail function on the T2000.

Table 4-7 Process of configuring point-to-point transparent transmission EPL services (by trail)
Proce Operation Remarks
dure
1 Creating a server trail See 2.15.1 Creating a VC-4 Server Trail.
2 Creating a trunk link -
3 Creating an EPL trail -

This topic describes how to create a trunk link when a point-to-point EPL service is configured
Prerequisite
slots.
l The license that supports the trial function must be available.
Procedure
Step 1 Choose Trail > Trunk Link Creation from the Main Menu.
Step 2 Set Bandwidth to 5xVC12 in the Trunk Link Creation interface.
Step 3 Click Browse. Select the source NE (NE1). Select the EFT8 board, then select 1 for VCTRUNK
Port, and then select VC4:2-VC12(1)–VC4:2-VC12(5) for Available Timeslot. Click OK.
Step 4 Click Browse. Select the source NE (NE3). Select the EFT8 board, then select 1 for VCTRUNK
Step 5 Select the Activate the trail check box, and adopt default settings for other parameters.
Step 6 Click Apply to create the trunk link from NE1 to NE3 of user A.

Step 7 Refer to Steps 2–6 to create the trunk link from NE1 to NE3 of user B.
----End

Parameters
Table 4-8 Parameters for creating a trunk link
Bandwidth l EFT0/EFT8A/ 1xVC-12 Determines the

EFT8B: nxVC-12 bandwidth of the
(n: 1–63), nxVC-3 trunk link. Note that
(n: 1–6), nxVC-4 the bandwidth should
(n:1, 2) be consistent with the
l EMS1: nxVC-12 bandwidth of the
(n: 1–126), selected server trail
nxVC-3 (n: 1–6), or the bound
nxVC-4 (n:1, 2) timeslot.
Source NE-slot-board- - Indicates the source

VCTRUNKn port, where "n" is the
port number.
Bound timeslot Port-VC4-n-VC12/ - Indicates the timeslot

VC3-m that is bound with the
source/sink
VCTRUNK port,
where "n" is the
VC-4 path number
and "m" is the
VC-12/VC-3 path
number. Note that the
bandwidth of the
timeslot bound with
the source port,
bandwidth of the
timeslot bound with
the sink port, and the
bandwidth must be
consistent.
Sink NE-slot-board- - Indicates the sink

VCTRUNKn port, where "n" is the
port number.

This topic describes how to create an EPL trail when a point-to-point EPL service is configured
Prerequisite
slots.


l The trunk link must be created on the T2000.
Procedure
Step 1 Choose Trail > Ethernet Trail Creation > EPL Creation from the Main Menu.
Step 2 Set the following parameters regarding the service source in the window that is displayed:
l Port Usage Strategy: Port
l Click Browse. Select NE1 and select a proper source line port PORT1.
Step 3 Set parameters regarding the sink as follows:

l Port Usage Strategy: Port
Step 4 Select Use Existing Trunk Links in Trunk Link Route Strategy. Select Trunk_Link-0001
with a bandwidth of 5xVC-12.
Step 5 Click Next. Set the port attributes of NE1 and NE3 in the window that is displayed:
l Port Enabled for PORT1: Enabled
l Enabling LCAS for VCTRUNK1: Enabled
Step 6 Click Finish.
Step 7 Refer to Steps 2–6 to create the EPL service from NE1 to NE3 of user B.
----End

Parameters
Table 4-9 Parameters for creating an EPL trail

Parameter Value Default Description
Range Value
Port Usage Port, Port - Indicates the usage strategy of the source/sink
Strategy +VLAN port. When This parameter is set to Port, it
indicates that the source/sink is identified
only by the external physical port number and
is used for transparent transmission. When
this parameter is set to Port+VLAN, it
indicates that the source/sink is identified
only by the external physical port number +
VLAN and is used for convergent
transmission.
Trunk Link Use Existing Use Existing It is recommended that you adopt the
Route Trunk Link, Trunk Link following procedures to create the EPL
Strategy Manually service by using the trail function: creating
Create Trunk the server trail→creating the trunk link trail
Link, →creating the EPL trail. In this case, select
Automaticall Use Existing Trunk Link.
y Create Alternatively, you can create the trunk Link
Trunk Link trail when creating the EPL trail. In this case,
you should select Manually Create Trunk
Link or Automatically Create Trunk
Link.
4.3 Configuring PORT-Shared EVPL Services by Using the

Per-NE Configuration Function
how to configure the PORT-shared EVPL services by using the per-NE configuration function.
The engineering design department conducts planning based on the requirements and the
engineering information described in Chapter 1, and outputs the following engineering
information.
This topic describes how to configure the PORT-shared EVPL service by using the per-NE
configuration function on the T2000.


l The headquarters of company C located at NE1 must transmit data services to the two
branches (C1 and C2) located at NE3 through the MSTP equipment.
l The services of the two branches must be isolated completely.
l Branch C1 requires a 10 Mbit/s bandwidth, and branch C2 requires a 20 Mbit/s bandwidth.
l The Ethernet switch of company C must provide the 10M/100M autosensing Ethernet
electrical ports that support VLAN.

information.
Networking Diagram


Headquarters of A
PORT2
T2000
NE1
STM-1 linear MSP
chain
STM-4 two-fiber
NE2 bidirectional MSP ring NE4
NE3
PORT2 PORT3 VCTRUNK
C1 C2

Based on the service type and the traffic volume, one EMS1 and one ETFS8 board are added to
NE1 and NE3. Other NEs require no new boards. Figure 4-12 shows the board information of
NE1. Figure 4-13 shows the board information of NE3.

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

PORT2
VCTRUNK1 VCTRUNK1 C1
C
PORT2
VC4-1: VC12-1 to
SDH VC4-1: VC12-1 to
10 Mbit/s
VC12-5 VC12-5 PORT3
C2
VCTRUNK2 VCTRUNK2 20 Mbit/s
VC4-1: VC12-6 to VC4-1: VC12-6 to
VC12-15 VC12-15
NE1
NE3
Item C1 C2
NE NE1
Slot-board-port 9-EMS1-2
Working mode of PORT Auto-negotiation
Tag flag of the source port Tag aware

Item C1 C2
Source VLAN ID 100 200
NE NE3
Slot-board-port 9-EMS1-2 9-EMS1-3
Tag flag of the sink port Access Access
VLAN ID 100 200

The SDH timeslot allocation for Ethernet services is as shown in Figure 4-15.
Figure 4-15 SDH timeslot allocation diagram

Ring
1#VC4
VC12:1-15
2#VC4 9-EMS1:VC4-1: 9-EMS1:VC4-1:
VC12:1-15 VC12:1-15
Add/Drop
NOTE
l PORT1 is the GE port on the EMS1 board. PORT2 to PORT7 are the FE ports on the ETFS8 board.
l On the EMS1, VCTRUNK1 to VCTRUNK12 can be bound with VC4-1 only and VCTRUNK13 to
VCTRUNK24 can be bound with VC4-2 only.
l On the EMS1, paths of VC-3 or VC-12 level can be bound in VC4-1 or VC4-2, but paths at only one
of the two levels can be bound in a VC-4.

This topic describes how to configure the PORT-shared EVPL service by using the per-NE
configuration function on the T2000.
Table 4-11 lists the process of configuring the PORT-shared Ethernet EPL service on the T2000.

Table 4-11 Process of configuring the PORT-shared EPL service

dure
1 Creating a board For details, see 4.1.4

Creating a Board.
2 Configuring port attributes of the Ethernet board and -

bound paths
3 Creating a cross-connection between the Ethernet -

4 Creating EPL services -

Prerequisite
l The Ethernet boards must support the EVPL function and must be inserted in the correct
slots.
Precautions
NOTE
l See the T2000 online Help for the meaning of each parameter.
l To use the LCAS function, you must set the equipment at both ends to the same LCAS mode.
l If Huawei equipment is used at the local and the opposite stations, select Huawei Mode.
l If Huawei equipment interconnects with the equipment from other vendors, select Standard
Mode for the equipment at the local and opposite ends.
l If the equipment from other vendors does not support Standard Mode, select Huawei Mode.
Procedure
2. Select 9-EMS1 from the Object Tree and choose Configuration > Ethernet Interface
3. Choose External Port > Basic Attributes and set the parameters of PORT2 as follows:

l Maximum Frame Length: Set this parameter according to the connected Ethernet
equipment, and adopt the default value 1522 in normal cases.
4. Click Apply.
5. Click the TAG Attributes tab and set the attributes of PORT2 as follows:
l TAG: Tag Aware
l Entry Detection: Enabled
6. Click Apply.
2. Click Apply.
3. Click the LCAS tab and set the attributes of VCTRUNK1 and VCTRUNK2:
l TAG: Tag Aware
4. Click Apply.
1. In the Internal Port page, select the Bound Path tab.
2. Click Configure. Then, the Bound Path dialog box is displayed.
l Level: VC12-xv

l Level: VC12-xv
l Available timeslots: VC12-6 to VC12-7. Then click .

5. Click OK.
3. Click Create. Then, the Create SDH Service dialog box is displayed.
l Level: VC12
l Source Slot: 9-EMS1-1(SDH-1)
l Source VC4: VC4-1
l Sink VC4: VC4-2

5. Click OK.
Step 5 Create the PORT-shared EPL service as follows:
1. Select 9-EMS1 from the Object Tree.
2. Choose Configuration > Ethernet Service > Ethernet Line Service from the Function
Tree.
3. Click New and the Create Ethernet Line Service dialog box is displayed.
4. See Figure 4-14, and set the following parameters in the dialog box to create services from
C to C1:
l Service Type: EPL
l Source port: PORT2
l Source VLAN(e.g.1, 3-6): 100
l Sink Port: VCTRUNK1
l Sink VLAN(e.g.1, 3-6): 100

5. Click Apply.
6. See Figure 4-14, and repeat Step 4 to create the service from C to C2. Set the following
parameters in the dialog box:
l Service Type: EPL
l Sink VLAN(e.g.1, 3-6): 200
7. Click OK.
----End

Parameters
Table 4-12 Parameters for tag attributes

Range Value
TAG Tag Aware, Tag Aware The tag flag is used to set the type of data
Access, packets to be processed.
Hybrid l Tag Aware: The port of this attribute
transmits and receives the packets that
carry the VLAN tag. During the receiving
process, the port discards the packets that
do not carry the VLAN tag, but transmits
the packets that carry the VLAN tag. The
packets to be received and transmitted may
belong to different VLANs.
l Access: The port of this attribute transmits
and receives the packets that do not carry
the VLAN tag.
– It receives only the packets that do not
carry the VLAN tag, and adds Port
VLAN ID (PVID, which can be set) to
these packets.
– At the egress port, the VLAN tag is
stripped from the packets.
l Hybrid: The port of this attribute transmits
and receives the packets regardless of
whether the VLAN tag is carried.
– It transparently transmits the packets
that carry the VLAN tags. After
receiving the packets that do not carry
the VLAN tag, it adds Port VLAN ID
(PVID, which can be set) to these
packets.
– At the egress port, if the VLAN ID
carried in the packets is the same as the
PVID of the port, the VLAN Tag is
stripped. Otherwise, the packets are
transmitted transparently.
Entry Enabled, Enabled Indicates whether to identify the tag flags in

Detection Disabled the data packets. If Disabledis selected, the
tag flag is invalid. In this case, the port
transparently transmits the received data
packets.
Default 1–4095 1 Specifies the default VLAN ID of the port

VLAN ID when Access or Hybrid is selected for
TAG.


Range Value
VLAN 0–7 0 Indicates the service quality level. For

Priority example, when the network is busy, the data
packets with higher VLAN priority are
transmitted first, and the data packets with
lower VLAN priority may be discarded. The
value 0 indicates the highest priority, and the
value 7 indicates the lowest priority.
Table 4-13 Parameters for configuring the EPL service (by station)
Range Value
Board - - Indicates the board that needs to be

configured with the Ethernet service.
Service Type EPL EPL Indicates the type of the Ethernet service.
Transit
(MPLS)
EVPL
(MPLS)
Service Bidirectional Bidirectional Indicates the direction of the Ethernet service.

Direction ,
Unidirection
al
Source Port - PORT1 Indicates the source port of the Ethernet

service.
Source 1–4095 - Indicates the source VLAN ID of the Ethernet

VLAN service.
Sink Port - VCTRUNK Indicates the sink port of the Ethernet service.
1
Sink VLAN 1–4095 - Indicates the sink VLAN ID of the Ethernet

service.
Port Type PE, P PE On the boards that support the MPLS

function, the ports types may be PE and P.
The default value of this parameter is PE.
Encapsulatio MartinioE MartinioE When the port type is set to "P", this
n Format parameter can be set.
The MartinioE encapsulation uses two layers
of labels (Tunnel label and VC label) to
interconnect to other MPLS equipment.


Range Value
Enabled/ Enabled, Enabled Specifies the enabled or disabled state of the

Disabled Disabled port. "Enabled" means that this port is
allowed to access the services. "Disabled"
means that this port is not allowed to access
the services.

Prerequisite
slots.
Procedure
Step 2 According to Figure 4-15, configure the service from NE1 to NE3 that passes through NE2:
from timeslots 1–15 of the second VC-4 on the 27-OSB4A optical interface board to timeslots
1-15 of the second VC-4 on the 28-OSB4A optical interface board.
l Level: VC12
l Source VC4: VC4-2
l Sink VC4: VC4-2
Step 4 Click OK.
----End


Prerequisite
slots.
Procedure
as follows:
4. Click Apply.
5. Click the TAG tab and set the attributes of PORT2 and PORT3 as follows:
l TAG: Access
l Default VLAN ID for PORT2: 100
6. Click Apply.
8. Click Apply.

9. Click the LCAS tab and set the attributes of VCTRUNK1 and VCTRUNK2 as follows:
l TAG: Tag Aware
10. Click Apply.

3. To configure bound paths of VCTRUNK1, set the parameters in the dialog box as follows:
l Level: VC12-xv

4. To configure bound paths of VCTRUNK2, set the parameters as follows in the dialog box.
l Level: VC12-xv

5. Click OK.
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
5. Click OK.
Step 4 Create the PORT-shared EPL service as follows:


Tree.
4. See Figure 4-14, and set the following parameters in the dialog box to create services from
C to C1:
l Service Type: EPL
l Sink VLAN(e.g.1, 3-6): 100
l TAG for VCTRUNK1: Access
5. Click Apply.
6. See Figure 4-14, and repeat Step 4 to create the service from C to C2. Set the following
parameters in the dialog box:
l Service Type: EPL
l Sink VLAN(e.g.1, 3-6): 200
l TAG for VCTRUNK2: Access
7. Click OK.
----End
4.4 Configuring PORT-Shared EVPL Services by Using the

Trail Function
how to configure the PORT-shared EVPL services by using the trail function. The trail function
cannot be used to configure end-to-end services.
information.

This topic describes how to configure the PORT-shared EVPL services by using the trail function
on the T2000.
This topic describes how to create a trunk link when a PORT-shared EPL service is configured
This topic describes how to create an EPL trail when a PORT-shared EPL service is configured

branches (C1 and C2) located at NE3 through the MSTP equipment.
l Branch C1 requires a 10 Mbit/s bandwidth, and branch C2 requires a 20 Mbit/s bandwidth.
l The Ethernet switch of company C must provide the 10M/100M autosensing Ethernet
electrical ports that support VLAN.

information.
Networking Diagram


Headquarters of A
PORT2
T2000
NE1
STM-1 linear MSP
chain
STM-4 two-fiber
NE2 bidirectional MSP ring NE4
NE3
PORT2 PORT3 VCTRUNK
C1 C2


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

PORT2
VCTRUNK1 VCTRUNK1 C1
C
PORT2
VC4-1: VC12-1 to
SDH VC4-1: VC12-1 to
10 Mbit/s
VC12-5 VC12-5 PORT3
C2
VCTRUNK2 VCTRUNK2 20 Mbit/s
VC4-1: VC12-6 to VC4-1: VC12-6 to
VC12-15 VC12-15
NE1
NE3
Item C1 C2
NE NE1
Tag flag of the source port Tag aware

Item C1 C2
Source VLAN ID 100 200
NE NE3
Tag flag of the sink port Access Access
VLAN ID 100 200

The SDH timeslot allocation for Ethernet services is as shown in Figure 4-20.
Figure 4-20 SDH timeslot allocation diagram

Ring
1#VC4
VC12:1-15
2#VC4 9-EMS1:VC4-1: 9-EMS1:VC4-1:
VC12:1-15 VC12:1-15
Add/Drop
NOTE

This topic describes how to configure the PORT-shared EVPL services by using the trail function
on the T2000.

NOTE
Ethernet service can be created by using the trail function or by using the per-NE configuration function.
Otherwise, you can create Ethernet service only by using the per-NE configuration function.
Table 4-15 provides the process of creating the PORT-shared EVPL service by using the trail
function on the T2000.
Table 4-15 Process of configuring the PORT-shared EVPL services by using the trail function

dure

This topic describes how to create a trunk link when a PORT-shared EPL service is configured
Prerequisite
slots.
Procedure
Step 2 In the window that is displayed, set the bandwidth as 5xVC-12.
Step 3 Click Browse. Select the source NE (NE1). Select the EMS1 board, then select 1 for VCTRUNK
Port, and then select VC4:-1-VC12(1)–VC4-1:VC12(5) for Available Timeslot. Click OK.
Step 4 Click Browse. Select the source NE (NE3). Select the EMS1 board, then select 1 for VCTRUNK
Step 6 Click Apply to create the trunk link from NE1 to NE3 (from user C to user C1).
Step 7 Refer to Table 4-14 and refer to Steps 2–6 to create the trunk link from NE1 to NE3 (from user
C to user C2).
----End


This topic describes how to create an EPL trail when a PORT-shared EPL service is configured
Prerequisite
slots.
Procedure
Step 2 Set the following parameters regarding the source in the window that is displayed:
l Port Usage Strategy: PORT+VLAN
l Click Browse. Select NE1 and select the EMS1 board. Select PORT2 as the source port.
l VLAN ID: 100
Step 3 Set parameters regarding the sink as follows:

l Click Browse. Select NE3 and select the EMS1 board. Select PORT2 as the sink port.
l VLAN ID: 100
Step 4 Select Use Existing Trunk Links for Trunk Link Route Strategy.
l Set the Bandwidth as 5xVC12 and Name to Trunk_Link-0003.
l Click Next.

Step 5 In the window that is displayed, set the port attributes as follows:
l Set the attributes of PORT2 on NE1 as follows:
– TAG: Tag Aware
– Enabled/Disabled: Enabled
l NE1-9-EMS1-VCTRUNK1: Enabled (Enabling LCAS)
l Set the attributes of PORT2 on NE3 as follows:
– TAG: Access
– Enabled/Disabled: Enabled
l NE1-9-EMS1-VCTRUNK2: Enabled (Enabling LCAS)
l Select the Activate check box.
Step 6 Click Finish.

Step 7 Refer to Table 4-14 and refer to Steps 1–6 to create the EPL trail from user C at NE1 to user
C2 at NE5.
----End
4.5 Configuring VCTRUNK-Shared EVPL Services by

how to configure the VCTRUNK-shared EVPL services by using the per-NE configuration
function.
In the example provided in Chapter 2, Ethernet services need to be added.


information.
This topic describes how to configure the VCTRUNK-shared EVPL service on the T2000.
The method of configuring the data of NE3 is the same as the method of configuring the data of
NE2.

The requirements for the Ethernet services are listed in this topic.
l Department A at NE2 must transmit data services to department A' at NE3 through the
MSTP equipment.
l Department B at NE2 must transmit data services to department B' at NE3 through the
MSTP equipment.
l Services of the two departments can share a 45 Mbit/s bandwidth.
l Ethernet equipment of users can provide 10M/100M autosensing Ethernet ports that support
VLAN.

information.
l Board Information of Each NE
Networking Diagram

NE1
T200
0
PORT1
A
NE2 NE4
STM-4
NE5
B PORT2
NE3
PORT1 PORT2
VCTRUNK
A' B'


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


SDH
A PORT2 PORT2
A'
PORT3 VCTRUNK1 VCTRUNK1 PORT3

B VC4-1: VC3-1 VC4-1: VC3-1 B'
NE2
NE3
NOTE
Item A B
NE NE2
Timeslot VC4-1:VC3-1

Item A B
VCTRUNK VCTRUNK1
Bound bandwidth 1xVC-3
Tag flag of PORT Access Access
PORT VLAN ID 100 200
NE NE3
VCTRUNK VCTRUNK1


Ring
1#VC4
VC3:1
2#VC4 9-EMS1:VC4- 9-EMS1:VC4-
1:VC3:1 1:VC3:1
Add/Drop

This topic describes how to configure the VCTRUNK-shared EVPL service on the T2000.
Table 4-17 provides the process of configuring the VCTRUNK-shared EVPL service on the
T2000.

NOTE
Table 4-17 Flow for configuring the VCTRUNK-shared EVPL service

Proced Operation Remarks
ure
1 Creating a board For details, see 4.1.4

Creating a Board.
2 Configuring port attributes of the Ethernet board and -

bound paths
3 Creating a cross-connection between the Ethernet -

4 Creating an EPL Trail -
5 Configuring the CAR parameters (optional) -

Prerequisite
slots.
NOTE
See the OptiX iManager T2000 Help for the meaning of each parameter.
Procedure
Management > Ethernet Interface. Click .
as follows:


4. Click Apply.
5. Click the TAG tab and set the attributes of PORT2 and PORT3 as follows:
l TAG: Access
6. Click Apply.

1. Choose Internal Port > LCAS and set the attributes of VCTRUNK1 as follows:
2. Click Apply.
3. Click the TAG Attributes tab and set the attributes of VCTRUNK1 as follows:
l TAG: Tag Aware
4. Click Apply.

l Level: VC3-xv
l Available Timeslots: VC3-1
Then, click .
4. Click OK.
4. Set the following parameters in the dialog box:
l Level: VC3
l Source VC4: VC4-1

l Source Timeslot Range(e.g.1, 3-6): 1

l Sink VC4: VC4-1
l Sink Timeslot Range(e.g.1, 3-6): 1
5. Click OK.
Step 5 Create the VCTRUNK-shared EVPL service as follows:
Tree.
4. Refer to Table 4-16, and set the following parameters in the dialog box to create the EPL
service from A to A':
l Service Type: EPL
l Source Port: PORT2
l Sink VLAN(e.g.1, 3-6): 100
5. Click Apply.

6. Repeat Step 3 to create the EPL service from B to B'. Set the following parameters in the
dialog box:
l Service Type: EPL
l Sink VLAN(e.g.1, 3-6): 200
7. Click OK.
Step 6 Optional: Configure the CAR parameters as follows:

2. Choose Configuration > QoS Management > Flow Management from the Function
Tree. Click the CAR Configuration tab.
3. Click Create, and the Create CAR dialog box is displayed.
4. Set the following parameters in the dialog box:
l CAR ID: 1
l Committed Information Rate(kbit/s): 20480
l Committed Burst Size(kbyte): 0
l Peak Information Rate(kbit/s): 40960
l Maximum Burst Size(kbyte): 0
5. Click Apply.
6. Set the following parameters according to the method in substep 5.
l CAR ID: 2
l Committed Information Rate(kbit/s): 20480
l Committed Burst Size(kbyte): 0
l Peak Information Rate(kbit/s): 40960
l Maximum Burst Size(kbyte): 0
7. Click OK.
8. Click the Flow Configuration tab and set the parameters as follows:
l Bound CAR for PORT2 and for VCTRUNK1 with the VLAN ID being 100: 1
l Bound CAR for PORT3 and for VCTRUNK1 with the VLAN ID being 200: 2

9. Click Apply.
----End
Parameters
Table 4-18 CAR parameters
CAR ID 1–2048 1 Indicates the CAR number.
Enabled/ Enabled, Disabled Indicates whether the CAR function

Disabled Disabled is enabled.
Committed You can enter 0 Defines a minimum committed

Information an integer bandwidth for an Ethernet service.
Rate (bit/s) ranging from 0 Its value represents an average rate.
to 1048576 in
steps of 64.
Alternately, you
can select from
the following
values: 512
kbit/s, 1 Mbit/s,
2 Mbit/s, 3
Mbit/s, 4 Mbit/
s, 5 Mbit/s, 6
Mbit/s, 7 Mbit/
s, 8 Mbit/s, 9
Mbit/s, 10 Mbit/
s, 20 Mbit/s, 30
Mbit/s, 40 Mbit/
s, 50 Mbit/s,
100 Mbit/s, and
1000 Mbit/s.
Committed 0 0 Defines the maximum guaranteed

Burst Size data amount that an Ethernet service
(kbyte) can transmit within a time interval.
Table 4-19 Flow configuration parameters
Bound CAR - - Displays or sets the CAR ID bound

with the flow.
Bound CoS - - Displays or sets the CoS ID bound

with the flow.


The method of configuring the data of NE3 is the same as the method of configuring the data of
NE2.
See Figure 4-24 and 4.5.4 Configuring the Data of NE2.
4.6 Configuring VCTRUNK-Shared EVPL Services by

Using the Trail Function
how to configure the VCTRUNK-shared EVPL services by using the trail function.
information.
This topic describes how to configure the VCTRUNK-shared EVPL service by using the trail
This topic describes how to create a trunk link when a VCTRUNK-shared EPL service is
configured by using the trail function, including the configuration steps and the parameter
setting.
This topic describes how to create an EPL trail when a VCTRUNK-shared EVPL service is
setting.

MSTP equipment.
MSTP equipment.
l Services of the two departments can share a 45 Mbit/s bandwidth.
l Ethernet equipment of users can provide 10M/100M autosensing Ethernet ports that support
VLAN.


information.
l Board Information of Each NE
Networking Diagram
NE1
T200
0
PORT1
A
NE2 NE4
STM-4
NE5
B PORT2
NE3
PORT1 PORT2
VCTRUNK
A' B'



01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


SDH
A PORT2 PORT2
A'
PORT3 VCTRUNK1 VCTRUNK1 PORT3

B VC4-1: VC3-1 VC4-1: VC3-1 B'
NE2
NE3

NOTE

Item A B
NE NE2
VCTRUNK VCTRUNK1
NE NE3
VCTRUNK VCTRUNK1



Ring
1#VC4
VC3:1
2#VC4 9-EMS1:VC4- 9-EMS1:VC4-
1:VC3:1 1:VC3:1
Add/Drop

This topic describes how to configure the VCTRUNK-shared EVPL service by using the trail
Table 4-21 lists the flow for configuring the VCTRUNK-shared EVPL service.
NOTE
Ethernet services can be created by using the trail function or by using the per-NE configuration function.
Otherwise, you can only create Ethernet services by using the per-NE configuration function.
Table 4-21 Flow of configuring the VCTRUNK-shared EVPL service (by trail)

dure
4 Configuring the CAR See Step 6 in 4.5.4 Configuring the Data of NE2.
parameters (optional)

This topic describes how to create a trunk link when a VCTRUNK-shared EPL service is
setting.
Prerequisite
slots.


Procedure
Step 2 In the window that is displayed, set the bandwidth to 1xVC-3.
Step 3 Click Browse. Select NE2 as the source NE. Select the EMS1 board, then select 1 for
VCTRUNK Port. Select 1 for the higher order timeslot. Select VC4:1-VC3:1 for the lower
order timeslot. Click OK.
Step 4 Click Browse. Select NE3 as the sink NE. Select the EMS1 board, then select 1 for VCTRUNK
Port. Select 1 for the higher order timeslot. Select VC4:1-VC3:1 for the lower order timeslot.
Click OK.
Step 6 Click Apply to create the trunk link from NE2 to NE3 that is shared by users A, A', B, and B'.
----End

This topic describes how to create an EPL trail when a VCTRUNK-shared EVPL service is
setting.
Prerequisite
slots.
l The trunk link must be created.
Procedure
Step 2 Set the following parameters regarding the source in the window that is displayed:
1. Set the parameters regarding the source as follows:
l VLAN ID: 100
2. Set the parameters regarding the sink as follows:

l Click Browse. Select NE3 and select a proper sink line port PORT2.
l VLAN ID: 100
3. Select Use Existing Trunk Links for Trunk Link Route Strategy.
l Select a Trunk_Link with a bandwidth of 1xVC-3.
l Click Next.
Step 3 In the window that is displayed, set the port attributes as follows:
1. Set the attributes of PORT2 on NE2 as follows:
l TAG: Access
2. NE2-9-EMS1-VCTRUNK1: Enabled (Enabling LCAS)
3. Set attributes of PORT1 as follows for NE3:
l TAG: Access
4. NE3-9-EMS1-VCTRUNK1: Enabled (LCAS Enabled)
5. Select the Activate check box.
Step 4 Click Finish to complete the configuration of the EPL trail from user A at NE2 to user A' at
NE3.
Step 5 Refer to Steps 1–5 to create the EPL trail from user B at NE2 to user B' at NE3.
----End
4.7 Configuring the Ingress/Egress EVPL Services by Using

the Per-NE Configuration Function
When the data of multiple users is transmitted on the same VCTRUNK, the ingress/egress EVPL
service is used to isolate the data by using the VLAN ID and MPLS labels. You can configure
the ingress/egress EVPL service on the T2000 by using the per-NE configuration function.
The engineering design department conducts planning based on the requirements.
The EVPL services of different clients can share the same bandwidth. This topic describes how
to configure the ingress/egress EVPL service on the T2000.


MSTP equipment.
MSTP equipment.
l Services of the two departments can share a 45 Mbit/s bandwidth. The Ethernet equipment
of users provides 10M/100M autosensing Ethernet electrical ports and adopts the same
VLAN.

The engineering design department outputs the following engineering information based on the
engineering information described in Chapter 1:
Networking Diagram


Department A Department B
NE1
NE2 STM-4
NE4
NE5
NE3 Company A Company B
Department A’ Department B’


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


SDH
Tunnel: 20
Tunnel: 20
A PORT2 VC: 30 PORT2
VC: 30
A'
VCTRUNK1 VCTRUNK1
PORT3 PORT3
B VC4-1: VC3-1 VC4-1: VC3-1 B'
Tunnel: 20 Tunnel: 20
VC: 35 VC: 35
NE1
NE3
NOTE
Item A B
NE NE1
Timeslot VC4-1:VC3-1 VC4-1:VC3-1

Item A B
VCTRUNK VCTRUNK1
Sink tunnel 20 20
Sink VC 30 35
Working mode Auto-negotiation Auto-negotiation
TAG Tag aware Tag aware
NE NE3
Timeslot VC4-1:VC3-1 VC4-1:VC3-1
VCTRUNK VCTRUNK1
Sink tunnel 20 20
Sink VC 30 35
Tag flag of PORT Tag aware Tag aware


Ring
1#VC4
VC3:1
2#VC4 9-EMS1:VC4-1:VC3:1 9-EMS1:VC4-1:VC3:1
Add/Drop


The EVPL services of different clients can share the same bandwidth. This topic describes how
to configure the ingress/egress EVPL service on the T2000.
NOTE
Table 4-23 lists the flow for configuring the EVPLAN service.
Table 4-23 Process of configuring the ingress/egress service

dure
1 Creating a board For details, see 4.1.4 Creating a

Board.
2 Configuring port attributes of the Ethernet -

board and bound paths
3 Creating a cross-connection between the -

Ethernet board and the line board
4 Creating EPL services -
5 Configuring the QoS parameters of the This operation is optional. See 4.5.4
service (if required) Configuring the Data of NE2.

Prerequisite
slots.
NOTE
Procedure

as follows:
4. Click Apply.
5. Click the TAG Attributes tab and set the attributes of PORT2 and PORT3 as follows:
l TAG: Tag Aware
6. Click Apply.
7. Click the Network Attributes tab and set Port Type of PORT2 and PORT3 to PE.
8. Click Apply.
2. Click Apply.
l TAG: Tag Aware
4. Click Apply.
5. Click the Network Attributes tab and set the attributes of VCTRUNK1 as follows:
l Port Type: P
l Encapsulation Format of P Port: MartinioE
6. Click Apply.
l Level: VC3-xv

l Select VC3-1 from Available Resources and click .

4. Click OK.
4. Set the parameters as follows in the dialog box.
l Level: VC-3
l Source VC4: VC4-1
l Sink VC4: VC4-2
5. Click OK.
Step 5 Create an EVPL service as follows.
1. Select 9-EMS1 from the Object Tree and choose Configuration > Ethernet Service >
Ethernet Line Service from the Function Tree. Select the Display MPLS Shared
Service check box.
3. See Figure 4-34, and set the following parameters in the dialog box to create the EVPL
service from A to A':
l Service Type: EVPL (MPLS)
l Sink Tunnel: 20
l Sink VC: 30
4. Click Apply.

5. Repeat Step 3 to create the EVPL service from B to B'. Set the following parameters in the
dialog box:
l Service Type: EVPL (MPLS)
l Sink Tunnel: 20
l Sink VC: 35
6. Click OK.
----End


Prerequisite
slots.
Procedure
Step 2 See Figure 4-35 and configure the SNCP services from NE1 to NE3 so that the services are
passed through NE2. Click Create. Set the following parameters in the Create SDH Service
dialog box:
l Level: VC-3
l Source VC4: VC4-2
l Sink VC4: VC4-2
Step 3 Click OK.
----End

NOTE
The method of configuring the data of NE3 is the same as the method of configuring the data of NE1. See
4.7.4 Configuring the Data of NE1.
4.8 Configuring the Transit EVPL Service by Using the Per-

NE Configuration Function
The EVPL services of different users can share the same VCTRUNK, where switching of the
MPLS labels ensures the interworking between the MPLS networks. You can configure the
transit EVPL service on the T2000 by using the per-NE configuration function.


The transit service is a type of EVPL service. This topic describes how to configure the transit
EVPL service on the T2000.

branches (C1 and C2) located at NE2 and NE3 through the MSTP equipment.
l Each of branch C1 and branch C2 must occupy a 10 Mbit/s bandwidth.
l The MPLS router of company C provides 10M/100M autosensing Ethernet electrical ports
but transmits only MPLS data packets.

Networking Diagram


Headquarters of C
PORT2
NE1
NE2
PORT2
C1
STM-4
tunnel=70
NE4 NE5
NE3
PORT2
Tunnel = 80
C2

NE1, NE2, and NE3. Other NEs require no new boards. Figure 4-37 shows the board layout of
NE1. Figure 4-38 shows the board layout of NE2 and NE3.

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

Figure 4-39 shows the service configuration diagram of NE1, NE2, and NE3.

VCTRUNK PORT
Tunnel: Tunnel:
30 70 PORT2
C1
PORT VCTRUNK VCTRUNK1
VC4-1: VC12-1 to VC12-5
MPLS
Tunnel: Tunnel:
switch
70 30
PORT2 VCTRUNK1 NE2
C VC4-1: VC12-1 to VC12-5
Tunnel:
80 MPLS 20
Tunnel: VCTRUNK2 VCTRUNK PORT
VC4-1: VC12 to 6~VC12-10
switch
Tunnel: Tunnel:
NE1 20 80 PORT2
C2
VCTRUNK1
VC4-1: VC12-1 to VC12-5
SDH MPLS
switch
NE3
NOTE
Item C←→C1 C←→C2
NE NE1

Item C←→C1 C←→C2
Source tunnel 70 80
Sink tunnel 30 20
Tag flag of PORT Tag aware
NE NE2 NE3
Source tunnel 70 80
Sink tunnel 30 20



Ring
1#VC4
VC12:1-5
2#VC4
9E:VC4-1: 9E:VC4-1:
VC12:1-5 VC12:1-5
VC12:1-5
9E:VC4-1: 9E:VC4-1:
VC12:6-10 VC12:6-10
Add/Drop
9E: 9-EMS1

The transit service is a type of EVPL service. This topic describes how to configure the transit
EVPL service on the T2000.
NOTE
Table 4-25 provides the process of configuring the transit EVPL service on the T2000.
Table 4-25 Process of configuring the transit EVPL service

dure

Board.


4 Creating an EVPL service -


Prerequisite
slots.
NOTE
Procedure
4. Click Apply.
l TAG: Tag Aware
6. Click Apply.
7. Click the Network Attributes tab and set the attributes of PORT2 as follows:
l Port Type: P
8. Click Apply.
Step 2 Configure the Ethernet internal ports as follows:
1. Choose Internal Port > LCAS and set the attributes of VCTRUNK1 and VCTRUNK2 as
follows:
2. Click Apply.
3. Click the TAG Attributes tab and set the attributes of VCTRUNK1 and VCTRUNK2 as
follows:
l TAG: Tag Aware

4. Click Apply.
5. Click the Network Attributes tab and set the attributes of VCTRUNK1 and VCTRUNK2
as follows:
l Port Type: P
6. Click Apply.
l Level: VC12-xv

4. Click Apply.
l To configure bound paths of VCTRUNK2, set the parameters as follows in the dialog
box.
l Level: VC12-xv

6. Click OK.
4. Set the following parameters in the dialog box to create the SDH service from C1 to C1:
l Level: VC12

l Source VC4: VC4-1

l Sink VC4: VC4-2
5. Click OK.
6. Set the following parameters in the dialog box to create the SDH service from C to C2:
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
7. Click OK.
Step 5 Create the EVPL service as follows:
Service check box.
service from C to C1:
l Service Type: Transit (MPLS)
l Source Tunnel: 70
l Sink Tunnel: 30

4. Click Apply.
5. Repeat Step 3 to create the EVPL service from C to C2. Set the following parameters in
the dialog box:
l Source Tunnel: 80
l Sink Tunnel: 20
6. Click OK.
----End


Prerequisite
slots.
NOTE
Procedure
4. Click Apply.
l TAG: Tag Aware
6. Click Apply.
7. Click the Network Attributes tab and set the attributes of PORT2 as follows:
l Port Type: P
8. Click Apply.
10. Click Apply.
l TAG: Tag Aware


12. Click Apply.
13. Click the Network Attributes tab and set the attributes of VCTRUNK1 as follows:
l Port Type: P

l Level: VC12-xv

4. Click OK.
Step 3 Configure cross-connect from the Ethernet board to the SDH line board.
4. Set the following parameters in the dialog box to create the SDH service from C1 to C:
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
5. Click OK.
Step 4 Create the EVPL service as follows:
Service check box.
service from C1 to C:


l Source Tunnel: 70
l Sink Tunnel: 30
4. Click OK.
----End

NOTE
The method of configuring the data of NE3 is the same as the method of configuring the data of NE2. See
4.8.5 Configuring the Data of NE2.
4.9 Configuring the 802.1d Bridge-Based EPLAN Service by

The EPLAN service implements the dynamic sharing of the Ethernet service bandwidth between
multiple points, thus meeting the requirements of the dynamic features of the data services and
saving the bandwidth resources. You can configure the 802.1d bridge-based EPLAN service on
the T2000 by using the trail function or by using the per-NE configuration function. This topic
describes how to configure the 802.1d bridge-based EPLAN service by using the single station
function.
This topic describes how to configure the EPLAN service by using the per-NE configuration

l Three branches (F2, F1, and F3) of company F are located at NE2, NE3, and NE4. F2 needs
to communicate with F1 and F3. F1 and F3 need not communicate with each other.

l The three branches must share a 10 Mbit/s bandwidth.

l The Ethernet equipment of company F provides the 10M/100M autosensing Ethernet ports
that support VLAN.

Networking Diagram
NE1
T2000
VCTRUNK1 VB
PORT2
VB VCTRUNK1
NE2
PORT2 STM-4 two-fiber
bidirectional MSP ring NE4
PORT2 PORT2
NE3 NE5
F3
F1
PORT2
VCTRUNK1 VB VCTRUNK2 VCTRUNK

PORT2
F2

NE2 and NE3. Figure 4-43 shows the board layout of NE4.


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


VCTRUNK PORT
LP2 LP1 PORT2

F1
PORT VCTRUNK VCTRUNK1
VC4-1: VC12-1 to VC12-5
VB1
LP2
PORT2 LP1 VCTRUNK1 NE2
F2 VC4-1: VC12-1 to VC12-5
LP3
VCTRUNK2
VB1 VC4-1: VC12-6 to VC12-10 VCTRUNK PORT
NE3 LP2 LP1 PORT2

F3
VCTRUNK1
VC4-1: VC12-1 to VC12-5
SDH
VB1
NE4

NOTE
The 802.1q VB is used to implement EPLAN services of which the user VLAN is not defined.
Table 4-26 shows the Ethernet service connection relations.
Item F
NE NE3
Slot-port working mode Auto-negotiation
Mapping protocol GFP
Enabling LCAS Enabled
Entry detection Disabled
VB VB1
Bridge type 802.1d
Bridge switch mode SVL/Ingress filter disable
VB mount port PORT2, VCTRUNK1, VCTRUNK2
NE NE2 NE4
Mapping protocol GFP
Enabling LCAS Enabled
Entry detection Disabled
VB VB1

Item F
Bridge type 802.1d
Bridge switch mode SVL/Ingress filter disable
Mounted port PORT2, VCTRUNK1 PORT2, VCTRUNK1


Ring
Timeslot 28-OSB4A-1 27-OSB4A-128-OSB4A-1 27-OSB4A-1 28-OSB4A-1 27-OSB4A-1 27-OSB4A-1 28-OSB4A-1
1#VC4
VC12:1-5 VC12:1-5
2#VC4 9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1:
VC12:1-5 VC12:1-5 VC12:6-10 VC12:1-5
Forward
Add/Drop
9E: 9-EMS1

This topic describes how to configure the EPLAN service by using the per-NE configuration
NOTE
Table 4-27 provides the process of configuring the EPLAN service on the T2000.
Table 4-27 Process of configuring the EPLAN service
Proc Operation Remarks

edur
e

Board.



edur
e

4 Creating EPLAN services -
6 Enabling the STP (if the service is This operation is optional. See 7
configured in a ring) Configuring the STP or RSTP.

Prerequisite
l The Ethernet boards must support the EPLAN function and must be inserted in the correct
slots.
NOTE
Refer to the T2000 Help for the meaning of each parameter when you configure a service.
Procedure
4. Click Apply.
5. Click the TAG Attributes tab. Set Entry Detection of PORT2 to Disabled.
6. Click Apply.


1. Select Internal Port. Click the TAG Attributes tab. Set Entry Detection of VCTRUNK1
and VCTRUNK2 to Disabled.
2. Click Apply.
3. Click the Encapsulation/Mapping tab and set the attributes of VCTRUNK1 and
VCTRUNK2 as follows:
l Mapping Protocol: GFP
4. Click Apply.
5. Click the LCAS tab and set the attributes of VCTRUNK1 and VCTRUNK2 as follows:
6. Click Apply.

l Level: VC12-xv

4. Click Apply.
l Level: VC12-xv

6. Click OK.
4. Set the following parameters in the dialog box to create the service from F2 to F1:
l Level: VC12

l Source VC4: VC4-1

l Sink VC4: VC4-2
5. Click Apply.
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
7. Click OK.
Step 5 To create the EPLAN services, do as follows:

1. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function
Tree.
2. Click New and the Create Ethernet LAN Service dialog box is displayed.
3. Set VB Name to VB1.
4. Set VB Type to 802.1d.
5. Click Configure Mounted Port and the VB Mount Port Configuration dialog box is
displayed.
6. Set VB Mount Port to PORT2, VCTRUNK1, and VCTRUNK2. Then, click .

7. Click OK.
8. Click OK in the Create Ethernet LAN Service dialog box.
----End
Parameters
Table 4-28 Parameters for configuring the Ethernet LAN service
Board - - Indicates the board that needs to be

configured with the Ethernet
service.

VB name A maximum of - Indicates the VB name. The concept

16 English of virtual bridge or various bridge
characters (VB) is originally developed by
Huawei. In the case of the Ethernet
data boards that have the Layer 2
switching capability, the switching
domain can be divided into multiple
separate sub-switching domains. As
a result, if no services are
interconnected, different VBs
cannot access each other. Each VB
has an independent configuration
mode and uses an independent
VLAN. Different VBs can use the
same VLAN.
Bridge type 802.1d 802.1q l 802.1d: shared learning bridge

802.1q that supports only the MAC
address forwarding-based Layer
2 switching
l 802.1q: VLAN-based
independent learning bridge that
supports isolation by using one
layer of VLAN tags
Bridge switch IVL/Ingress IVL/Ingress l In the case of the 802.1q bridge,

mode filtering enabled filter enable the bridge switching mode is
SVL/Ingress SVL/ingress filter enabled.
filtering l In the case of the 802.1d bridge,
disabled the bridge switching mode is
SVL/ingress filter disabled.
Bridge learning SVL IVL To forward a Layer-2 switching

mode IVL service, a network bridge must learn
the MAC address. A bridge learns
the MAC address in one of the
following two ways:
l Shared VLAN learning (SVL):
forwarding and learning based
on the MAC address only
l Independent VLAN learning:
forwarding and learning based
on the MAC address and VLAN

Ingress filtering Enable, Disable Enabled In the case of the data packets that
access the bridge, you need to
determine whether to check the
validity of the VLAN ID based on
the bridge.
l Ingress filter disabled: The
validity of the VLAN ID is not
checked. That is, all the packets
to enter the bridge are valid.
l Ingress filter enabled: The
validity of the VLAN ID is
checked. If a packet received at
the port does not belong to the
VLAN of the bridge port, the
packet is discarded.
Mounted port - - Indicates the mounted ports, which

may be PORT or VCTRUNK.
Port type P, PE PE l Indicates Provider Edge (PE),

which refers to the edge port of
the service provider. A PE port
(the default MPLS encapsulation
type is invalid) can transmit or
receive standard Ethernet
packets.
l Indicates Provider (P), which
refers to the port in the core
network of the service provider.
A P port can transmit or receive
the data packets with the MPLS
labels (the default TAG attribute
is invalid).
Enabled/ Enabled, Enabled Specifies to enable or disable the

Disabled Disabled. port.
l Enabled: means that the port can
access services.
l Disabled: means that the port
cannot access services.


Prerequisite
slots.
NOTE
Procedure
Management > Ethernet Interface from the Function Tree. Click .
4. Click Apply.
5. Click the TAG Attributes tab. Set Entry Detection of PORT2 to Disabled.
6. Click Apply.
1. Select Internal Port. Click the TAG Attributes tab. Set Entry Detection of VCTRUNK1
to Disabled.
2. Click Apply.
3. Click the Encapsulation/Mapping tab and set the attributes of VCTRUNK1 as follows:
l Mapping Protocol: GFP
4. Click Apply.
5. Click the LCAS tab and set the attributes of VCTRUNK1 as follows
6. Click Apply.


l Level: VC12-xv

4. Click OK.
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
5. Click OK.
Step 5 To create the EPLAN services, do as follows:

Tree.
4. Set VB Type to 802.1d.
displayed.
6. Set VB Mount Port to PORT2 and VCTRUNK1. Then, click .

7. Click OK.
----End


NOTE
The method of configuring the data of NE4 is the same as the method of configuring the data of NE2,
except that the parameter settings are different. For the parameter settings, see 4.9.2 Engineering
Planning. For the procedures, see 4.9.5 Configuring the Data of NE2.
4.10 Configuring the 802.1q Bridge-Based EVPLAN Service

by Using the Per-NE Configuration Function
function. This topic describes how to configure the 802.1q bridge-based EVPLAN service by
This topic describes how to configure the EVPLAN service by using the per-NE configuration

l The three branches of user F are located at NE2, NE3, and NE4. The three branches must
form a LAN and share a 10 Mbit/s bandwidth.
l The three branches of user G are located at NE2, NE3, and NE4. The three branches must
l The service of user F must be isolated from the service of user G.
l The Ethernet equipment of user F and user G provide 10M/100M autosensing Ethernet
ports of which the working mode is auto-negotiation.


Networking Diagram
NE1
T2000
G3
PORT3
NE2
PORT3
STM-4 two-fiber
G1 bidirectional MSP ring
PORT2
PORT2
NE4 NE5
F3
F1
NE3
PORT3 PORT2
VCTRUNK
G2 F2

Figure 4-47 Board layout of NE 2 and NE3

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

VCTRUNK PORT
PORT VCTRUNK
VB1 PORT2
F1
VCTRUNK1
VC4-1: VC12-1 to VC12-5
PORT2 VCTRUNK1
F2 PORT3
VC4-1: VC12-1 to VC12-5 G1
VCTRUNK2 VB2
VC4-1: VC12-6 to VC12-10
VCTRUNK2
VB1 VC4-1: VC12-6 to VC12-10
NE2
PORT VCTRUNK
VCTRUNK PORT
VB1 PORT2
PORT3
G2 VCTRUNK3
VCTRUNK1
F3
VC4-1: VC12-11 to VC12-15
VC4-1: VC12-1 tp VC12-5
VCTRUNK4 PORT3
VB2 VC4-1: VC12-16 to VC12-20
VCTRUNK2 G3
VC4-1: VC12-6 to VC12-10
VB2
SDH
NE3
NE4
NOTE
Table 4-29 shows the connection relation of the Ethernet service of company F. Table 4-30
shows the connection relation of the Ethernet service of company G.

Table 4-29 Connection relation of the Ethernet service of company F
Item F
NE NE3
Tag flag of PORT Access
PORT VLAN ID 100 (set according to the requirement of the client)
VB name VB1
Bridge type 802.1q
Bridge switch mode IVL/Ingress filter enable
NE NE2 NE4
VB name VB1 VB1
Bridge switch mode 802.1q 802.1q
VB mount port IVL/Ingress filter enable IVL/Ingress filter enable
Mount port PORT2, VCTRUNK1 PORT2, VCTRUNK1
Table 4-30 Connection relation of the Ethernet service of company G
Item G
NE NE3

Item G
VB name VB2
Bridge type 802.1q
NE NE2 NE4
VB name VB2 VB2
Table 4-31 is the forwarding filtering table of NE2, NE3 and NE4.
Table 4-31 VLAN filtering table
Company NE VB VLAN ID Forwarding Port
F NE2 VB1 100 PORT2, VCTRUNK1
NE3 VB1 100 PORT2, VCTRUNK1,

VCTRUNK2
NE4 VB1 100 PORT2, VCTRUNK1

G NE2 VB2 200 PORT3, VCTRUNK2

VCTRUNK4


Ring
1#VC4
VC12:1-5 VC12:1-5
9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1:
2#VC4
VC12:1-5 VC12:1-5 VC12:6-10 VC12:1-5
VC12:6-10 VC12:6-10
9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1:
VC12:6-10 VC12:11-15 VC12:16-20 VC12:6-10
Forward
Add/Drop
9E: 9-EMS1

This topic describes how to configure the EVPLAN service by using the per-NE configuration
services and saving the bandwidth resources.
NOTE
This topic describes the procedures and precautions. For configuring Ethernet services on the T2000. For
Table 4-32 provides the process of configuring the EVPLAN service on the T2000.

Table 4-32 Process of configuring the EVPLAN service

edur
e

Board.


4 Creating the EVPLAN service -
5 Creating the VLAN filtering table -
6 Enabling the STP (if the service is This operation is optional. See 7
configured in a ring) Configuring the STP or RSTP.

Prerequisite
l The Ethernet boards must support the EVPLAN function and must be inserted in the correct
slots.
NOTE
except that the parameter settings are different.
Procedure
as follows:

4. Click Apply.
l TAG: Access
6. Click Apply.
7. Choose Internal Port > LCAS and set the attributes of VCTRUNK1–VCTRUNK4 as
follows:
8. Click Apply.
9. Click the TAG Attributes tab and set the attributes of VCTRUNK1–VCTRUNK4 as
follows:
l TAG: Tag Aware

3. To configure bound paths of VCTRUNK1–VCTRUNK4, set the parameters in the dialog
box as follows:
l Level: VC12-xv

l Level: VC12-xv

l Level: VC12-xv


l Level: VC12-xv

4. Click OK.
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
5. Click Apply.
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
7. Click OK.
8. Refer to Steps 3–7 and see Figure 4-50 to create the service between the branches of
company G.
Step 4 Create the EVPLAN service as follows:

Tree.
4. Set VB Type to 802.1q.
displayed.

7. Click Apply in the Create Ethernet LAN Service dialog box.

9. Set VB Type to 802.1q.
displayed.
Step 5 Create a VLAN forwarding filtering table as follows:

Tree. Click the VLAN Filtering tab.
NOTE
If there are multiple VBs, select the target VB for which the VLAN filtering table needs to be created.
Then, click the VLAN Filtering tab.
2. Configure the VLAN filtering table of company F. Select VB1. Click New and the Create
VLAN dialog box is displayed.
3. Set the following parameters in the Create VLAN dialog box:

l VLAN ID: 100

l Selected forwarding ports: PORT1, VCTRUNK1, and VCTRUNK2
4. Click OK.
5. Configure the VLAN filtering table of company G. Select VB2. Click New and the Create
VLAN dialog box is displayed.
l VLAN ID: 200
l Selected forwarding ports: PORT3, VCTRUNK3, and VCTRUNK4
7. Click OK.
----End
For the parameters to be set for configuring Ethernet LAN services, refer to Table 4-28
Table 4-33 Parameters for configuring the VLAN filtering table
VLAN ID 1–4095 - Specifies the VLAN ID of the

forwarding filtering table.
Forwarding Port - - Specifies the physical port for

forwarding the data.


NOTE

NOTE
4.11 Configuring the 802.1q Bridge-Based EVPLAN Service

by Using the Trail Function
function. This topicdescribes how to configure the 802.1q bridge-based EVPLAN service by
using the trail function.
This topic describes how to configure the EPLAN service by using the trail function on the
T2000.
This topic describes how to create a trunk link when an EVPLAN service is configured by using
the trail function, including the configuration steps and the parameter setting.
4.11.5 Creating an EVPLAN Trail
This topic describes how to create an EPLAN trail when an EPLAN service is configured by
using the trail function, including the configuration steps and the parameter setting.

l The three branches of user F are located at NE2, NE3, and NE4. The three branches must

l The three branches of user G are located at NE2, NE3, and NE4. The three branches must
l The service of user F must be isolated from the service of user G.
l The Ethernet equipment of user F and user G provide 10M/100M autosensing Ethernet
ports of which the working mode is auto-negotiation.

Networking Diagram
NE1
T2000
G3
PORT3
NE2
PORT3
STM-4 two-fiber
G1 bidirectional MSP ring
PORT2
PORT2
NE4 NE5
F3
F1
NE3
PORT3 PORT2
VCTRUNK
G2 F2


Figure 4-52 Board layout of NE 2 and NE3

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


VCTRUNK PORT
PORT VCTRUNK
VB1 PORT2
F1
VCTRUNK1
VC4-1: VC12-1 to VC12-5
PORT2 VCTRUNK1
F2 PORT3
VC4-1: VC12-1 to VC12-5 G1
VCTRUNK2 VB2
VC4-1: VC12-6 to VC12-10
VCTRUNK2
VB1 VC4-1: VC12-6 to VC12-10
NE2
PORT VCTRUNK
VCTRUNK PORT
VB1 PORT2
PORT3
G2 VCTRUNK3
VCTRUNK1
F3
VC4-1: VC12-11 to VC12-15
VC4-1: VC12-1 tp VC12-5
VCTRUNK4 PORT3
VB2 VC4-1: VC12-16 to VC12-20
VCTRUNK2 G3
VC4-1: VC12-6 to VC12-10
VB2
SDH
NE3
NE4
NOTE
Table 4-34 shows the connection relation of the Ethernet service of company F. Table 4-35
shows the connection relation of the Ethernet service of company G.
Table 4-34 Connection relation of the Ethernet service of company F

Item F
NE NE3
VB name VB1
Bridge type 802.1q

Item F
NE NE2 NE4
VB name VB1 VB1
Table 4-35 Connection relation of the Ethernet service of company G

Item G
NE NE3
VB name VB2
Bridge type 802.1q
NE NE2 NE4

Item G
VB name VB2 VB2
Table 4-36 is the forwarding filtering table of NE2, NE3 and NE4.

F NE2 VB1 100 PORT2, VCTRUNK1

VCTRUNK2
G NE2 VB2 200 PORT3, VCTRUNK2

VCTRUNK4



Ring
1#VC4
VC12:1-5 VC12:1-5
9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1:
2#VC4
VC12:1-5 VC12:1-5 VC12:6-10 VC12:1-5
VC12:6-10 VC12:6-10
9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1:
VC12:6-10 VC12:11-15 VC12:16-20 VC12:6-10
Forward
Add/Drop
9E: 9-EMS1

This topic describes how to configure the EPLAN service by using the trail function on the
T2000.
NOTE
Ethernet services can be created by using the trail function or by using the per-NE configuration function.
Otherwise, you can only create Ethernet services by using the per-NE configuration function.
Table 4-37 Process of configuring the EPLAN service by using the trail function
Procedu Operation Remarks

re
3 Creating an EVPLAN -
service trail
4 Configuring the QoS This operation is optional. See 4.5.4 Configuring

parameters of the service (if the Data of NE2.
required)

This topic describes how to create a trunk link when an EVPLAN service is configured by using
the trail function, including the configuration steps and the parameter setting.

Prerequisite
slots.
Procedure
Step 2 See Figure 4-54 to create the trunk link from F2 to F1. Set Bandwidth to 5xVC12 in the
displayed interface.
Step 3 Click Browse. Select the source NE (NE3). Select the EMS1 board. Select 1 for VCTRUNK
Port, and then select VC4:1-VC12:1–VC4:1-VC12:5 for Available Timeslot.
Step 4 Click OK.
Step 5 Click Browse. Select the sink NE (NE2). Select the EMS1 board. Select 1 for VCTRUNK
Port, and then select VC4:1-VC12:1–VC4:1-VC12:5 for Available Timeslot.
Step 7 Click Apply to create the trunk link from NE3 to NE2.
Step 8 Create the trunk links from F2 to F3, from G2 to G1, and from G2 to G3 in the same manner.
----End
4.11.5 Creating an EVPLAN Trail

This topic describes how to create an EPLAN trail when an EPLAN service is configured by
using the trail function, including the configuration steps and the parameter setting.
Prerequisite
l The Ethernet boards must support the EPLAN function and must be inserted in the correct
slots.
l The trunk link must be created.
Procedure
Step 1 Choose Trail > Ethernet Trail Creation > EPLAN Creation from the Main Menu.
Step 2 Set the parameters regarding the source in the displayed Create EPLAN window. To create the
Ethernet LAN service of company F, double-click the nodes to be added into the EPLAN. In
the window that is displayed, select PORT2 and click . Then, click OK.

Step 3 Select the trunk link created previously from Trunk Link Route Strategy. Click Next. Set the
parameters of PORT2 on NE2, NE3, and NE4 in the Port Attribute Setting window:
l TAG: Access
Step 4 Click Add in the VLAN configuration window, and set the following parameter in the VLAN
Configuration for Ethernet Trail window:
l VLAN ID: 100
l Select the mounted port and click .
Step 5 Click OK.
Step 6 After the setting, click Next.
Step 7 Set the EPLAN name. Select the Activate the trail check box. Click Finish.
Step 8 Refer to Steps 1–7 to create the EPLAN service of company G.
----End
4.12 Configuring the MPLS-Based EVPLAN Service by

The EVPLAN service uses the MPLS technology. The transmission efficiency is lower than the
transmission efficiency of the EPLAN service and the configuration is more complex. Therefore,
the EPLAN is recommended unless EVPLAN needs to be used to meet certain special
requirements. You can configure the MPLS-based EVPLAN service on the T2000 by using the
per-NE configuration function.
This topic describes how to configure the EVPLAN service on the T2000.



l Company A has three branches that are located at NE1, NE2 and NE3. Data must be shared
among the branches.
l Company B has three branches that are located at NE1, NE2 and NE3. Data must be shared
among the branches.
l Companies A and B must share a bandwidth of 10 Mbit/s.
l The Ethernet equipment of companies A and B provides 10M/100M autosensing electrical
ports and adopts the same VLAN.

Networking Diagram
PORT2 PORT3
NE1
PORT2
STM-4 two-fiber NE4
NE2 bidirectional MSP ring
PORT3
NE3
PORT2 PORT3
Company Company
A B


NE1. Figure 4-58 shows the board layout of NE2 and NE3.

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU E
T T P P X X E P C A
T
7 7 T T C C M T U
F
5 5 1 1 S S S 1 S X
4 4 S
S S 1 P C PIU
A A 8
C
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18

01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
S
4 4 S
1 C PIU
A A
C 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18


Figure 4-59 Service configuration

NE1
Port2 Port3
VB1 VB2
LP
VCTRUNK
VCTRUNK
Tu
e l
nn
nn
e
Tu
l
VB1 VB1
NE2 NE3
Port2 Port2
Port3 Tunnel Port3
VB2 LP VB2
LP
VCTRUNK
Figure 4-60 NE Service Configuration Diagram
PORT VB logical port VB logical port VCTRUNK
lp2 LSP1 VCTRUNK1
VLAN 11 2 lp1
Party A VB 1
VCTRUNK2
lp3 LSP2
P3
LS
VLAN 11 3 lp1 lp2

Party B SP4
VB 2 L
lp3
LSP1: tunnel: 20 VC: 30 LSP3: tunnel: 20 VC: 32

LSP2: tunnel: 21 VC: 31 LSP4: tunnel: 21 VC: 33
LSP: link swich path

NOTE
Item A B
NE NE1
VCTRUNK (bound VCTRUNK1 (VC4-1:VC12-1– VCTRUNK1 (VC4-1:VC12-1–

timeslot) VC12-5), VCTRUNK2 VC12-5), VCTRUNK2
(VC4-1:VC12-6–VC12-10) (VC4-1:VC12-6–VC12-10)
Working mode of Auto-negotiation Auto-negotiation

PORT
PORT VLAN ID 11 11
VB name VB1 VB2
Bridge type 802.1q 802.1q
Bridge switch mode IVL/Ingress filter enable IVL/Ingress filter enable
VB mount porta PORT2, VCTRUNK1 ({20, PORT3, VCTRUNK1 ({20, 32},

31}, {20, 31}), VCTRUNK2 {20, 32}), VCTRUNK2 ({21,
({21, 31}, {21, 31}) 33}, {21, 33})
NE NE2

(VC4-1:VC12-6–VC12-10) (VC4-1:VC12-6–VC12-10)

PORT
PORT VLAN ID 11 11
VB name VB1 VB2

Item A B

30}, {20, 30}), VCTRUNK2 {20, 32}), VCTRUNK2 ({22,
({22, 31}, {22, 31}) 33}, {22, 33})
NE NE3

(VC4-1:VC12-6–VC12-10) (VC4-1:VC12-6–VC12-10)

PORT
PORT VLAN ID 11 11
VB name VB1 VB2

30}, {22, 30}), VCTRUNK2 {20, 32}), VCTRUNK2 ({21,
({21, 31}, {21, 31}) 33}, {21, 33})
"VCTRUNK1 ({21, 31}, {21, 31})" represents the following:
The logical port of VCTRUNK1 is the mounted port.
Both the uplink and downlink logical ports of VCTRUNK1 bear the service flow in Tunnel 21
and VC 31.
Table 4-39 is the VLAN filtering table of NE1, NE2, and NE3.
NE VB VLAN ID Forwarding Port
NE1 VB1 11 PORT2, VCTRUNK1, VCTRUNK2
VB2 11 PORT3, VCTRUNK1, VCTRUNK2



Ring
Station
NE1 NE2 NE3 NE4 NE1
1#VC4
VC12:1-5 VC12:1-5 VC12:1-5

2#VC4
9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1: 9E:VC4-1:
VC12:1-5 VC12:1-5 VC12:6-10 VC12:1-5 VC12:6-10 VC12:6-10
Forward
Add/Drop
9E: 9-EMS1

This topic describes how to configure the EVPLAN service on the T2000.
NOTE
Table 4-40 Process of configuring the EVPLAN service

dure

Board.

3 Creating the Cross-Connect Between an -

Ethernet Board and a Line Board
4 Creating an EVPLAN Trail -
5 Creating the VLAN filtering table -
6 Configuring the QoS parameters of the service This operation is optional. See
(if required) 4.5.4 Configuring the Data of
NE2.


Prerequisite
slots.
NOTE
Procedure
as follows:
4. Click Apply.
l TAG: Tag Aware
6. Click Apply.
7. Click the Network Attributes tab and set Port Type of PORT2 and PORT3 to PE.
8. Click Apply.
1. Choose Internal Port > LCAS and set the attributes of VCTRUNK1 and VCTRUNK2
as follows:
2. Click Apply.
3. Click the TAG Attributes tab and set the attributes of VCTRUNK1 and VCTRUNK2 as
follows:

l TAG: Tag Aware

4. Click Apply.
5. Click the Network Attributes tab and set the attributes of VCTRUNK1 and VCTRUNK2
as follows:
l Port Type: P
6. Click Apply.
l Level: VC12-xv

4. Click Apply.
l Level: VC12-xv

6. Click OK.
4. Set the following parameters in the dialog box to create the SDH service from NE1 to NE2:
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2


5. Click OK.
6. Set the following parameters in the dialog box to create the SDH service from NE1 to NE3:
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
7. Click OK.
Step 5 Create the EVPLAN service as follows:
Ethernet LAN Service.
2. Click New and the Create Ethernet LAN Service dialog box is displayed. Create the
EVPLAN service of company A on NE1 as follows.
displayed.
5. According to the NE service configuration diagram, select PORT2, VCTRUNK1, and
VCTRUNK2 for Available Mounted Ports. Click .
6. Click OK.
7. In the Create Ethernet LAN Service dialog box, set the parameters of the VB mounted
port:
l Uplink Tunnel: 20 (VCTRUNK1), 21 (VCTRUNK2)
l Downlink Tunnel: 20 (VCTRUNK1), 21 (VCTRUNK2)
l Uplink VC: 30 (VCTRUNK1), 31 (VCTRUNK2)
l Downlink VC: 30 (VCTRUNK1), 31 (VCTRUNK2
8. Click OK.
9. Click New and the Create Ethernet LAN Service dialog box is displayed. Create the
EVPLAN service of company A on NE1 as follows:
displayed.
12. According to the NE service configuration diagram, select PORT3, VCTRUNK1. and
VCTRUNK2 for Available Mounted Ports. Click .
13. Click OK.
14. In the Create Ethernet LAN Service dialog box, set the parameters of the VB mounted
port:

l Uplink Tunnel: 20 (VCTRUNK1), 21 (VCTRUNK2)

l Downlink Tunnel: 20 (VCTRUNK1), 21 (VCTRUNK2)
l Uplink VC: 32 (VCTRUNK1), 33 (VCTRUNK2)
l Downlink VC: 32 (VCTRUNK1), 33 (VCTRUNK2)
15. Click OK.
Step 6 Create a VLAN forwarding filtering table as follows:

Tree. Click the VLAN tab.
2. If there are multiple VBs, select the target VB for which the VLAN filtering table needs to
be created. Then, click the VLAN tab.
3. Click Create and the Create VLAN dialog box is displayed.
l VB: 1-VB1
l VLAN ID: 11
l Selected Forwarding Ports: PORT3, VCTRUNK1, and VCTRUNK2
5. Click OK.
----End

NOTE

NOTE

Prerequisite
slots.

Procedure
Step 2 According to Figure 4-61, configure the service from NE1 to NE3 that passes through NE4:
from timeslots 1–5 of the second VC-4 on the 27-OSB4A optical interface board to timeslots
1-5 of the second VC-4 on the 28-OSB4A optical interface board.
l Level: VC12
l Source VC4: VC4-2
l Sink VC4: VC4-2
Step 4 Click OK.
----End

Configuration Guide 5 Configuring Auxiliary Services
5 Configuring Auxiliary Services
About This Chapter
This topic describes how to configure the broadcast data service and the F1 data service on the
T2000. It also describes the related engineering requirements and engineering information.
5.1 Configuring Broadcast Services

The OptiX OSN 2000 uses the RS232 or RS422 port to achieve the universal asynchronous
receiver/transmitter (UART) full-duplex communication. The data is transmitted transparently.
Hence, the port rate or the transmission control protocols need not be configured. The highest
bit rate can be 19.2 kbit/s. The communication mode can be configured to either point-to-point
or point-to-multipoint. The OptiX OSN 2000 uses overhead bytes (Serial1–Serial4) as the
broadcast data communication channel to broadcast the data that is received from the data port
to other NEs over the fiber.
5.2 Configuring F1 Data Services
The AUX board of the OptiX OSN 2000 provides a 64 kbit/s synchronous data port (F1 port).
The F1 port provides a 64 kbit/s channel for transparent data transmission by using the F1 byte.
The F1 port can be used for point-to-point transmission of 64 kbit/s data.

5 Configuring Auxiliary Services Configuration Guide
5.1 Configuring Broadcast Services

The OptiX OSN 2000 uses the RS232 or RS422 port to achieve the universal asynchronous
receiver/transmitter (UART) full-duplex communication. The data is transmitted transparently.
Hence, the port rate or the transmission control protocols need not be configured. The highest
bit rate can be 19.2 kbit/s. The communication mode can be configured to either point-to-point
or point-to-multipoint. The OptiX OSN 2000 uses overhead bytes (Serial1–Serial4) as the
broadcast data communication channel to broadcast the data that is received from the data port
to other NEs over the fiber.
CAUTION
In the point-to-multipoint mode, only one slave station can transmit data to the master station at
a time.

As described in Chapter 2, broadcast data services need to be added.
The overhead bytes, broadcast data source, and broadcast data sink should be determined
according to the service requirements.
The broadcast data ports are used to access the collected monitoring data and report it to the NE
software. This topic describes how to configure broadcast data services on the T2000.

As described in Chapter 2, broadcast data services need to be added.
The requirements for broadcast data services are listed in this topic.
l NE1 is connected to the monitor server through the S1 port.
l NE2, NE3, and NE4 are connected to the environment monitor through the S1 ports.
l The monitor server broadcasts commands to the environment monitors of NE2–NE4. They
serve as slave stations and report the data collected locally to the monitor server.
The environment monitor must meet the following requirements:
l The port must be of the RS-232 level, where logic 1 ranges from –5 V to –15 V and logic
0 ranges from +5 V to +15 V.
l The port must be of the RS-232 high level (about –9 V) when the data is not transmitted.
l Only one slave station transmits the data to the master station at a time.

The overhead bytes, broadcast data source, and broadcast data sink should be determined
according to the service requirements.
Table 5-1 provides the engineering planning information.

Table 5-1 NE parameters
NE Overhead Broadcast Data Source Broadcast Data Sink

Byte
NE1 SERIAL1 SERIAL1 27-OSB4A-1, 28-OSB4A-1
NE2 SERIAL1 27-OSB4A-1 28-OSB4A-1, S1
NE3 SERIAL1 27-OSB4A-1 S1
NE4 SERIAL1 28-OSB4A-1 S1

The broadcast data ports are used to access the collected monitoring data and report it to the NE
software. This topic describes how to configure broadcast data services on the T2000.
Prerequisite
l The engineering planning operations must be complete.
Precautions
CAUTION
The broadcast data ports should not form a loop. Certain optical ports are not configured into
the broadcast data ports.
Procedure
Step 2 Select NE1 from the Object Tree and choose Configuration > Orderwire from the Function
Tree.
Step 3 Set the following parameters in the Broadcast Data Port tab:
l Overhead Byte: SERIAL1
l Working Mode: RS232
l Broadcast Data Source: SERIAL1
l Broadcast Data Sink: 27-OSB4A-1, 28-OSB4A-1
NOTE
"SERIAL1" stands for serial port S1. "SERIAL2" stands for serial port S2.

Step 4 Click Apply.

Step 5 Refer to Table 5-1 and configure the broadcast data services of NE2, NE3, and NE4 in the same
manner.
----End
5.2 Configuring F1 Data Services

The AUX board of the OptiX OSN 2000 provides a 64 kbit/s synchronous data port (F1 port).
The F1 port provides a 64 kbit/s channel for transparent data transmission by using the F1 byte.
The F1 port can be used for point-to-point transmission of 64 kbit/s data.
As described in Chapter 2, F1 data services need to be added.
The data channels to be cross-connected on each NE need to be determined according to the
service requirements.
This topic describes how to configure F1 data services on the T2000.

As described in Chapter 2, F1 data services need to be added.
The requirements for the F1 data services are listed in this topic.
l NE1 is connected to one set of communication equipment through the F1 port. The port of
the communication equipment must comply with the features of the E0 port defined in ITU-
T G.703.
l NE3 is connected to another set of communication equipment through the F1 port. The port
of the communication equipment must comply with the features of the E0 port defined in
ITU-T G.703.

l Point-to-point communication is required between the two sets of communication

equipment.

The data channels to be cross-connected on each NE need to be determined according to the
service requirements.
Table 5-2 provides the engineering planning information.
Table 5-2 NE parameters
NE Number Data Channel 1 Data Channel 2
NE1 1 F1 28-OSB4A-1
NE2 1 27-OSB4A-1 28-OSB4A-1
NE3 1 F1 27-OSB4A-1

This topic describes how to configure F1 data services on the T2000.
Prerequisite
l The engineering planning operations must be complete.
Procedure
Step 2 Select NE1 from the Object Tree and choose Configuration > Orderwire from the Function
Tree.
Step 3 Set the following parameters in the F1 Data Port tab:

l Data Channel 1: F1
l Data Channel 2: 28-OSB4AA-1
NOTE
In Available Data Channel, select Data Channel 1 and then select Data Channel 2.

Step 4 Refer to Table 5-2 and configure the F1 data services of NE2 and NE3 in the same manner.
----End

Configuration Guide 6 Configuring the DCN
6 Configuring the DCN
About This Chapter
This topic uses an example to describe how to configure the data communication network (DCN)
on the T2000.
6.1 Overview
The SDH NMS communicates with the SDH NEs through the DCN. The SDH NMS can then
manage and maintain these SDH NEs.
6.2 HWECC Communication
The embedded control channel (ECC) uses the D bytes to transmit the OAM data. Thus, the
T2000 can manage NEs in an SDH network.
6.3 Configuring HWECC Communication
By default, the Huawei equipment supports the HWECC protocol and considers bytes D1 to D3
as the physical channels. If the node ID is set, the ECC communication can be performed without
any configuration when the fiber is inserted correctly. If required, modify the ECC
communication parameters at the local station. Do not modify the parameters at the remote
station. Otherwise, the ECC communication cannot be restored after it is interrupted. If you have
to modify the parameters at the remote station, start from the remote station and then to the
nearest station.
6.4 IP over DCC
The IP over DCC protocol follows the TCP/IP protocol and is applied to control remote NEs
through the Internet.
6.5 Configuring IP over DCC Communication
This topic describes how to configure the IP over DCC communication on the T2000.
6.6 OSI over DCC
The OSI over DCC protocol is used for communication in case of hybrid networking of the
Huawei equipment and the third-party equipment that support the OSI over DCC
communication.
6.7 Configuring the OSI over DCC Communication
The OSI protocol is a communication protocol. It is widely used in the SDH management
network. The OSI over DCC protocol is applied to eliminate the limit of the hybrid networking.

6 Configuring the DCN Configuration Guide
The NM data can then be transparently transmitted at the network layer. Hence, the Huawei
equipment can interconnect with the third-party equipment that supports the OSI protocol.

6.1 Overview
The SDH NMS communicates with the SDH NEs through the DCN. The SDH NMS can then
manage and maintain these SDH NEs.
In the DCN, the NMS and NEs are considered as nodes for the DCN management network.
These nodes are connected to each other through Ethernet or DCC physical channels.
In actual network applications, the NMS and NEs may be located at different floors in the same
building, at different buildings,or even in different cities. As a result, the NMS should connect
to the NEs through the external DCN, which consists of equipment such as Lanswitch and router.
Thus, the DCN among NEs is called an internal DCN.
6.1.1 Background for the Generation of the DCN
With the scaled development of the network, the operation, administration, maintenance, and
provision (OAM&P) becomes more difficult. The DCN then requires great attention from
operators. A stable and robust DCN helps lower the operation expenditure (OPEX) for vendors.
6.1.2 DCN Solutions
Huawei equipment supports the DCN networking by using three communication protocols.
6.1.1 Background for the Generation of the DCN

With the scaled development of the network, the operation, administration, maintenance, and
provision (OAM&P) becomes more difficult. The DCN then requires great attention from
operators. A stable and robust DCN helps lower the operation expenditure (OPEX) for vendors.
In the SDH frame, D bytes are considered as the physical channels for the creation of DCN. In
this case, no specific DCN channels are required. Hence, the OPEX is minimized for the client.
If bytes D1 to D3 of the RSOH in the SDH overhead are used, a 192 kbit/s bandwidth is available
in the DCN. If bytes D4 to D12 of the MSOH in the SDH overhead are used, a 576 kbit/s
bandwidth is available in the DCN. If bytes D1 to D12 in the SDH overhead are used, a 768
kbit/s bandwidth is available in the DCN.
Figure 6-1 Positions of the D bytes in the SDH overhead
* *
A1 A1 A1 A2 A2 A2 J0
B1 E1 F1 RSOH
D1 D2 D3
AU PTR
B2 B2 B2 K1 K2
D4 D5 D6
D7 D8 D9 MSOH
D10 D11 D12
S1 M1 E2

DCC Resource Management

The optical ports of the SDH equipment support the communication through channels D1 to D3
or D4 to D12. In the actual application, configure the DCC resources at each station according
to the DCC bytes that are used.
Count the number of 3-byte and 9-byte channels according to the DCC channels that are enabled
at each optical port of each station. Bytes D1 to D3 are 3-byte channels. Bytes D4 to D12 are 9-
byte channels. If the DCC communication configuration already exceeds the restriction, close
or adjust the DCCs of certain ports, depending on the actual situation.
6.1.2 DCN Solutions

Huawei equipment supports the DCN networking by using three communication protocols.
The three communication protocols are listed in this topic.
l HWECC
l IP over DCC
l OSI over DCC
The HWECC protocol is a proprietory protocol, which is developed by Huawei for the DCN
networking. This protocol features simple configuration and convenient application. As a
proprietory protocol, the HWECC protocol does not meet the management requirements when
the third-party equipment is involved.
The IP over DCC and the OSI over DCC protocols are standard communication protocols, which
are used widely. To solve the management problem when the third-party equipment is involved,
Huawei OptiX equipment can use either of the protocols. Either protocol can be selected for the
networking that involves only Huawei equipment.
If the third-party equipment that does not support either the IP over DCC or OSI over DCC
protocol is involved, the Huawei equipment can transparently transmit the OAM data of the
third-party equipment.
6.2 HWECC Communication

The embedded control channel (ECC) uses the D bytes to transmit the OAM data. Thus, the
T2000 can manage NEs in an SDH network.
6.2.1 Functions and Features

The HWECC protocol is mainly adopted to transmit the OAM data between Huawei optical
equipment.
6.2.2 Application
There are two typical applications of the HWECC protocol for the networking schemes.

The HWECC protocol is mainly adopted to transmit the OAM data between Huawei optical
equipment.
This protocol stake does not recognize the OAM data of the third-party equipment. When the
third-party equipment is involved, the OAM data cannot be interconnected. The Huawei optical

equipment, however, can transparently transmit the OAM data of the third-party equipment.
Hence, the client can use the current DCC resources to manage all the equipment.
6.2.2 Application
There are two typical applications of the HWECC protocol for the networking schemes.
Application I Networking That Involves Only Huawei Equipment

Figure 6-2 shows the networking mode that involves only the Huawei equipment.
Figure 6-2 Networking that involves only Huawei equipment
HUB1 GNE1 NE6

NE6 HUB2 NE7 NE12
T2000
NE2 NE5 NE8 NE11
Network
cable NE3 NE4 NE9 NE10
Fiber Subnet 1 Subnet 2
This networking mode requires that one gateway NE (GNE) is used for the communication
between other NEs and the T2000 through the Ethernet port. The NEs communicate with each
other through fibers or Ethernet ports. The network shown in Figure 6-2 consists of two subnets.
The two subnets conduct the extended ECC communication through Ethernet ports, such as
between NE6 and NE7.
Application II Networking That Involves Huawei Equipment and Third-Party

Equipment
Figure 6-3 shows the networking mode that involves the Huawei equipment and the third-party
equipment.

Figure 6-3 Networking that involves Huawei equipment and third-party equipment
HUB NE NE NE
NM of third-party
equipment
NE NE
Third-party equipment
NE
NE NE
NE
Huawei equipment
NE
In this networking mode, the OAM data of the third-party equipment should travel through the
Huawei equipment. The Huawei equipment transparently transmits the DCC. During the
transmission, Huawei equipment does not analyze the data. In the case of DCC transparent
transmission, perform the corresponding configuration at each NE along the data transmitting
trail.
6.3 Configuring HWECC Communication

By default, the Huawei equipment supports the HWECC protocol and considers bytes D1 to D3
as the physical channels. If the node ID is set, the ECC communication can be performed without
any configuration when the fiber is inserted correctly. If required, modify the ECC
communication parameters at the local station. Do not modify the parameters at the remote
station. Otherwise, the ECC communication cannot be restored after it is interrupted. If you have
to modify the parameters at the remote station, start from the remote station and then to the
nearest station.
NOTE
The parameters described in the following parts are examples. In actual applications, set the parameters
according to the network planning.
6.3.1 Creating a Gateway NE

This topic describes how to create a gateway NE on the T2000.
6.3.2 Creating a Non-Gateway NE
This topic describes how to create a non-gateway NE on the T2000.
6.3.3 Setting the NE ID
This topic describes how to set the NE ID.
6.3.4 Configuring the Extended ECC
If there are two subnets which are not connected to each other by fibers, Ethernet lines can be
adopted to establish the extended ECC communication. In this way, the T2000 can manage the
equipment in a centralized manner.
6.3.5 Querying the ECC Route

You can check whether the ECC route is correct. If the ECC route is incorrect, you need to re-
configure it.
6.3.6 Configuring the DCC Rate
The DCC communication can be performed among NEs. D1–D3, D4–D12, or D1–D12 can be
set for the DCC communication at different rates. Thus, the NM requirements in the case of
complex networking can be met. When configuring DCC, you need to set DCC rate and allocate
DCC resources according to DCC channel types.
6.3.7 Configuring DCC Transparent Transmission
When the networking involves Huawei equipment and the third-party equipment, the Huawei
equipment can transparently transmit the DCC bytes of the third-party equipment. Huawei
equipment also supports the adjustment of its DCC bytes and transparent transmission over the
idle DCC bytes of the third-party equipment.

See 2.6.1 Creating a Gateway NE: NE1.
6.3.2 Creating a Non-Gateway NE

This topic describes how to create a non-gateway NE on the T2000.
See 2.6.2 Creating Non-Gateway NEs: NE2–NE5.

Prerequisite
Precautions
CAUTION
Modifying the NE ID may interrupt the communication.
Procedure
Step 1 Select the NE icon on the Main Topology, right-click, and select Attribute from the shortcut
menu.
Step 2 In the NE Attribute dialog box, click Modify NE ID. For the NE attributes, refer to Table
6-1.
Step 3 In the Modify NE ID dialog box, set New ID and New Extension ID according to the actual
engineering requirements.

Step 4 Click OK. In the dialog box that is displayed, click OK.
----End
Parameters
Table 6-1 NE attributes
Param Value Defaul Description

eter Range t Value
ID 1–49151 - Indicates the ID of the created NE.
Extende 1–255 - Indicates the extended ID of the created NE.

d ID
Name - - Indicates the name of the created NE. The default value is
"NE + ID". The ECC protocol takes the NE ID as the
unique identification for an NE. In the T2000 interface and
databases, the NE ID is also taken as the key word for
searching. In the network planning, allocate the NE ID to
each NE. The conflict of NE IDs causes the conflict of ECC
routing. As a result, certain NEs cannot be managed.
NE Pre- Checked, Unchec If Checked is selected, the configuration data is stored

configu Unchecke ked only on the T2000 and not delivered to the NE. If
ration d Unchecked is selected, the configuration data is delivered
to the NE.
6.3.4 Configuring the Extended ECC

If there are two subnets which are not connected to each other by fibers, Ethernet lines can be
adopted to establish the extended ECC communication. In this way, the T2000 can manage the
equipment in a centralized manner.
Prerequisite
Precautions
CAUTION
This operation causes resetting of the NE and affects services.

Procedure
Step 1 Right-click the NE icon in the Main Topology, and choose NE Explorer.
Step 2 Choose Communication > ECC Management from the Function Tree.
Step 3 Select ECC Extended Mode according to the actual engineering requirements. Refer to Table
6-2 for the extended ECC parameters.
NOTE
l If Specified mode is selected, set IP and Port for the server, Opposite IP and Port for the client.
l If Auto mode is selected, all parameters are set automatically.
Step 4 Click Apply.

Step 5 In the Warning dialog box that is displayed, click OK. In the Operation Result dialog box
displayed, click Close.
----End
Parameters
Table 6-2 Parameters for configuring the extended ECC

Range Value
ECC Auto mode, Specified If Auto mode is selected, the extended ECC
Extended Specified mode connection is automatically established. This
Mode mode mode is convenient. Extra connections,
however, are still to be established and the
resource availability is low. Hence, it is
recommended that you select Auto mode
only in the case of not more than four NEs. In
addition, two NEs can automatically establish
extended ECC communication only after the
ECC Extended Mode parameters of the two
NEs are set to Auto mode.
If Specified mode is selected, the extended
ECC is to be established between the server
and the client. The connection is highly
reliable. The bandwidth availability is high.
This mode is used to establish an extended
ECC connection in normal cases.


Range Value
Specified Set Server, Set Server If Set Server is selected for the specified
mode Set Client mode, set the parameters as follows:
l "IP" indicates the IP address of the
extended ECC server NE. Click Refresh
after setting the IP address and then 0.0.0.0
should be returned.
l "Port" indicates the number of the NE port
used for the extended ECC. The number
can be any integer from 1601 to 1699.
After this parameter is set, set the opposite
NE as the client. The actual port number
should be the same as this port number.
If Set Client is selected for the specified
mode, set the parameters as follows:
l "Opposite IP" indicates the IP address of
the current extended ECC server NE.
l "Port" indicates the number of the port,
which is used for extended ECC, of the
extended ECC server NE.
6.3.5 Querying the ECC Route

You can check whether the ECC route is correct. If the ECC route is incorrect, you need to re-
configure it.
Prerequisite
Procedure
Step 2 Choose Communication > NE ECC Link Management from the Function Tree.
Step 3 Click Refresh. The ECC routes of the NE are displayed in the NE ECC Link Management
List.
----End
6.3.6 Configuring the DCC Rate

The DCC communication can be performed among NEs. D1–D3, D4–D12, or D1–D12 can be
set for the DCC communication at different rates. Thus, the NM requirements in the case of

complex networking can be met. When configuring DCC, you need to set DCC rate and allocate
DCC resources according to DCC channel types.
Prerequisite
The OptiX OSN 2000 supports the following three modes.
Table 6-3 DCC channel modes of the OptiX OSN 2000
Running Mode DCC Allocation
Mode 1 (default) 22 D1–D3 channels, four D4–D12 channels, two D1–D12

channels
Mode 2 22 D1–D3 channels, six D4–D12 channels
Mode 3 22 D1–D3 channels, five D1–D12 channels
Precautions
CAUTION
If the query result shows that the DCC resources are in "using" mode when the DCC allocating
mode is modified, delete the channel in DCC Rate Configuration.
Procedure
Step 2 Choose Communication > DCC Management from the Function Tree.
Step 3 Click the DCC Rate Configuration tab. Click Channel Type to set the DCC rate according to
the actual requirements. Refer to Table 6-4 for the description of the DCC rates.
Step 4 Click Apply.
Step 5 Click Close in the dialog box that is displayed.
Step 6 Click the DCC Resource Allocation tab and double-click Number for Allocation to set the
number of DCC channels according to actual requirements. For the DCC channel modes, refer
to Table 6-3.
Step 7 Click Apply and then click OK in the dialog boxes that are displayed.
----End

Parameters
Table 6-4 Parameters for configuring the DCC rate
Paramete Value Range Default Description

r Value
Enabled/ Enabled, Disabled Enabled Specifies whether to enable the DCC

Disabled communication.
Channel D1–D3, D4–D12, D1–D3 Specifies the DCC bytes, that is, the
Type D1–D12 channel rate.
DCC Obtained Already, - Indicates the DCC resource acquisition of

Resources Obtaining Failed a specified optical port at the NE side. This
parameter can be queried only.
Communic Normal, Receiving - Indicates the communication status of a

ation Failed, Transmitting specified optical port. This parameter can
Status Failed, Transmitting/ be queried only.
Receiving Failed
Protocol IP, OSI, HWECC, - Specifies the type of DCC communication.

Type Auto
6.3.7 Configuring DCC Transparent Transmission

When the networking involves Huawei equipment and the third-party equipment, the Huawei
equipment can transparently transmit the DCC bytes of the third-party equipment. Huawei
equipment also supports the adjustment of its DCC bytes and transparent transmission over the
idle DCC bytes of the third-party equipment.
Prerequisite
The transparent transmission of DCC has the following three scenarios:
l The Huawei equipment is located in the center of the network and third-party equipment
as the two ends of the network. The Huawei equipment and the third-party equipment are
managed by separate NM systems basedon bytes D1 to D3. In this case, the Huawei
equipment supports adjusting of the bytes D1 to D3 of the third-party equipment to any
three successive bytes of bytes D4 to D12. The Huawei equipment then transparently
transmits the DCC bytes of third-party equipment.
l The Huawei equipment is located at the two ends of the network and third-party equipment
at the center of the network. The Huawei equipment and the third-party equipment are
managed by separate NM systems basedon bytes D1 to D3. In this case, the Huawei
equipment supports adjusting of its own bytes D1 to D3 to any three successive bytes of

bytes D4 to D12. The OAM data of the Huawei equipment is transparently transmitted by
the third-party equipment.
l Other overhead bytes are transparently transmitted throughspare D bytes. The overhead
bytes include E2, F1, and X1-X4.
Procedure
Step 2 Choose Communication > DCC Management from the Function Tree. Click the DCC
Transparent Transmission Management tab.
Step 3 Click New and the Create DCC Transparent Transmission Byte dialog box is displayed.
Select the source and sink timeslots, port, and overhead bytes to be transparently transmitted.
For the parameters for configuring the DCC transparent transmission, refer to Table 6-5.
Step 4 Click OK. In the dialog box that is displayed, click Close.
----End
Parameters
Table 6-5 Parameters for configuring the DCC transparent transmission

Parameter Value Range Defaul Description
t Value
Source - - Specifies the source port where the

Timeslot/Port transparent transmission byte is to be set.


t Value
Transparent D1–D12, E2, F1, D1 Specifies the byte to be transmitted

Transmission X1–X4 transparently through the source port.
of Overhead
Byte at Source
Port
Sink Timeslot/ - - Specifies the sink port where the

Port transparent transmission byte is to be set.
Transparent D1–D12, E2, F1, D1 Specifies the byte to be transmitted

Transmission X1–X4 transparently through the sink port.
of Overhead
Byte at Sink
Port
6.4 IP over DCC

The IP over DCC protocol follows the TCP/IP protocol and is applied to control remote NEs
through the Internet.
6.4.1 Basic Concepts

This topic describes the basic concepts of IP over DCC.
The DCC is used to transmit the OAM data between the SDH equipment. The protocol stacks
used by different vendors are not compatible with each other. Thus, extra overhead bytes or
service resources need to be allocated to transmit DCC data transparently in a network that is
composed of multi-vendor products.
6.4.3 Application
The OptiX OSN 2000 can be connected in various ways in an IP network. Communicating based
on IP, the T2000 accesses NEs through Ethernet. The NEs connect to each other through fibers
or Ethernet ports and can form any type of the networking topologies, such as ring, chain, or
star.
6.4.4 Configuration Requirements
This topic describes the configuration requirements for IP over DCC.

This topic describes the basic concepts of IP over DCC.
IP over DCC
The OptiX OSN products support remote operation and maintenance by applying the IP over
DCC protocol. The IP over DCC protocol follows the TCP/IP protocol and is applied to control
remote NEs through the Internet. In the IP over DCC protocol, the D bytes (D1–D3 by default)
of the overhead are used for communication. The OptiX OSN 2000 supports the dynamic and
static routing.

OSPF
The open shortest path first (OSPF) protocol is a dynamic routing protocol based on the link
state. The SDH products update the route table of each NE dynamically by using the OSPF
protocol. The OSPF protocol divides an autonomous domain into different areas so that routes
are updated within an area or between areas. In normal cases, the GNE and all the non-gateway
NEs (non-GNEs) managed by it must be within the same OSPF area.
Remote Access
Gateway NE mode: The ECC protocol is used. For a remote access, log in to the GNE that is
connected to the computer. Then other NEs can be accessed through the NE ID. After the IP
over DCC feature is added, This mode can still be used to access remote NEs.
Direct connection mode: The IP over DCC feature is used, and the remote NE can be connected
directly through the IP address. You only need to enter the destination IP address in the login
interface. For this mode, however, you need to add in advance the static route or default gateway
in the NMS and the NE that needs to be accessed directly.

The DCC is used to transmit the OAM data between the SDH equipment. The protocol stacks
used by different vendors are not compatible with each other. Thus, extra overhead bytes or
service resources need to be allocated to transmit DCC data transparently in a network that is
composed of multi-vendor products.
IP over DCC meets most of the interworking requirements in the existing network without using
extra overhead or service resources. In this way, the networking structure is simplified, network
resources are saved and other networking requirements can be quickly satisfied.
IP over DCC has the following characteristics:
l Adopts the standard TCP/IP protocol. This makes the OptiX OSN 2000 compatible with
the equipment of other vendors and simplifies the network management.
l Adopts the forwarding function of the third layer in the protocol stack. This requires extra
overhead bytes or service paths.
l Implements flexible networking models.
l Achieves simple upgrade modes and great compatibility. It is easy for IP over DCC to work
with new forwarding or multi-protocol features on the application layer.
6.4.3 Application
The OptiX OSN 2000 can be connected in various ways in an IP network. Communicating based
on IP, the T2000 accesses NEs through Ethernet. The NEs connect to each other through fibers
or Ethernet ports and can form any type of the networking topologies, such as ring, chain, or
star.
Application I GNE Mode

If the T2000 and the GNE connect to the same Ethernet (the T2000 and the GNE need to be in
the same subnet), and other NEs are accessed in the gateway NE mode, you need not add any
static routes.
As shown in Figure 6-4, the T2000 with the IP address of 129.9.0.100 uses NE1 as the GNE to
access other NEs. In This case, you need not add static routes on the T2000 or NEs.

Figure 6-4 Application Ι
NM T2000
NE4
Subnet mask 255.255.255.0 133.168.0.3
255.255.255.0
NE1 NE3
T2000 129.9.0.1 133.168.0.2
255.255.255.0 255.255.255.0
NE2
NE name
133.168.0.1
IP address
255.255.255.0
Subnet mask
Application II Gateway NE Mode (Default Gateway)

If the T2000 connects to the GNE through a router and other NEs are accessed in the gateway
NE mode, add a default gateway on the T2000 and on the GNE.
As shown in Figure 6-5, the T2000 with the IP address of 10.100.11.12 connects to the GNE
(NE1) through a router and accesses other NEs in the gateway NE mode. In this case, set a default
gateway on both the T2000 and NE1. Set the default gateway on the T2000 to 10.100.11.1, and
that on NE1 to 129.9.0.254.
Figure 6-5 Application II

NM T2000 NE4
IP address 10.100.11.12 133.168.0.3
Subnet mask 255.255.255.0 255.255.255.0
Default gateway 10.100.11.1
10.100.11.1 129.9.0.254 NE1 NE3

255.255.255.0 Router 255.255.255.0 129.9.0.1 133.168.0.2
255.255.255.0 255.255.255.0
129.9.0.254
NE2
133.168.0.1
255.255.255.0
NE name
IP address
Subnet mask
Default gateway
Application III Direct Connection Mode (by Static Routes)

If the T2000 and the GNE connect to the same Ethernet and other NEs are accessed in the direct
connection mode, set the default gateway to the IP address of the NE that is connected to the
T2000 directly. Otherwise, add the static route to the non-GNEs, with the forwarding address
as the IP address of the GNE.
As shown in Figure 6-6, if the T2000 with the IP address of 129.9.0.100 needs to access NE3
directly, add the static route to 133.168.0.0/24 on the T2000.

Figure 6-6 Application III
NM T2000
Default gateway 129.9.0.1
Destination:
133.168.0.0
Static routes
Mask:
255.255.255.0 NE4
133.168.0.3
255.255.255.0
T2000 NE1 NE3

129.9.0.1 133.168.0.2
255.255.255.0 255.255.255.0
NE name
IP address NE2
255.255.255.0
Default gateway
Static routes
Application IV Direct Connection Mode Through a Router (by Static Routes)

The T2000 connects to the Ethernet port of a certain NE through a router and accesses other
NEs in the direct connection mode. Do as follows:
l On the T2000, set the static route to the GNE and non-GNEs.
l On the GNE, set the default route to the T2000.
l Add static routes to the T2000 on the destination station and the intermediate station.
As shown in Figure 6-7, the T2000 with the IP address of 10.100.11.12 connects to NE1 through
a router and accesses NE3 in the direct connection mode. Suppose the IP address of the T2000
is 10.100.11.0 (subnet mask 255.255.255.0). Do as follows:
l Add the static route on the T2000 to the gateway 129.9.0.1.
l Set the default gateway on NE1 to 129.9.0.254.
l Add the static route on NE2 to 10.100.11.0, with the next hop address as 129.9.0.1.
l Add the static route on NE3 to 10.100.11.0, with the next hop address as 133.168.0.1.

Figure 6-7 Application IV
NE4
133.168.0.3
255.255.255.0
10.100.11.1 129.9.0.254 NE1 NE3

255.255.255.0Router 255.255.255.0
129.9.0.1 133.168.0.2
255.255.255.0 255.255.255.0
129.9.0.254 Static routes
NM Destination:10.100.11.0
T2000
IP address NE2 Mask: 255.255.255.0
10.100.11.12
133.168.0.1 Next hop:133.168.0.1
Default gateway 10.100.11.1 NE name 255.255.255.0
IP address Static routes
Static routes Subnet mask Destination:10.100.11.0
Destination:129.9.0.1
Default gateway Mask: 255.255.255.0
Mask:255.255.255.0
Next hop:129.9.0.1
Destination:133.168.0.0 Static routes
Mask:255.255.255.0
6.4.4 Configuration Requirements

This topic describes the configuration requirements for IP over DCC.
Network Scale
If NEs communicate with each other through IP over DCC, note the following rules for setting
the network scale:
l To prevent data loss, limit the number of NE nodes in the same OSPF area to 60.
l When using the T2000 to monitor NEs, limit the number of non-GNEs monitored by one
GNE to 60.
IP Address Planning
If NEs communicate with each other through IP over DCC, note the following rules for setting
the IP address:
l If SDH products communicate through IP addresses on the network layer, each NE must
have a unique IP address to prevent routing error due to conflict.
l NEs support standard A, B, C types of IP addresses, that is, the IP address that ranges from
1.0.0.1 to 223.255.255.254. The 127.x.x.x, a loopback address, cannot be used.
l The IP address must be used with the subnet mask. The subnet mask must support
consecutive masks in addition to natural masks, for example, 255.255.224.0.
l When the IP over DCC communication is used between a GNE and a non-GNE, the IP
addresses can be of different network sections.
l The NEs that belong to the same OSPF domain can be in different IP subnets.
l Do not configure one GNE and one non-GNE in the same IP subnet.
l The Ethernets in the network must belong to different subnets. Otherwise, a routing error
occurs in the whole network. This is not allowed.
l The subnet masks of the NEs must be the same.
l The priority of static routes is higher than that of dynamic routes. If there is a conflict, static
routes take priority.

6.5 Configuring IP over DCC Communication

This topic describes how to configure the IP over DCC communication on the T2000.
NOTE
The following parameters are considered as examples. In actual application, configure the parameters

6.5.2 Setting NE Communication Parameters
This topic describes how to set the NE communication parameters.
6.5.3 Configuring Static Routes
This topic describes how to set the static routes.
6.5.4 Allocating DCC Resources
This topic describes how to allocate the DCC resources.
6.5.5 Querying Communication Status
This topic describes how to query the communication status.
6.5.6 Querying the OSPF Protocol Status
This topic describes how to query the OSPF protocol status.

6.5.2 Setting NE Communication Parameters

Prerequisite
Procedure
Step 2 Select the NE icon and choose Communication > Communication Parameters from the
Function Tree.
Step 3 Set NE communication parameters such as the IP address, extended ID, and subnet mask,
according to the actual plan. Refer to Table 6-6 for the communication parameters.
Step 4 Click Apply.
----End

Parameters
Table 6-6 Communication parameters

Range Value
IP - - Indicates the IP address of an NE. After the

IP address is set manually, any ID address
change does not affect the IP address.
Extended ID 1–254 9 Indicates the higher order 8 bits of a 24-bit

NE ID, also called the subnet number, used to
identify different subnets.
Gateway IP - 0.0.0.0 In the case of the NE that applies the ECC

protocol for communication, the gateway IP
is the IP address of the route that is connected
to the NE. In the case of the NE that applies
the IP over DCC protocol for communication,
the gateway IP is the IP address of the NE that
has the routing function. In the case of the NE
that applies the OSI over DCC protocol for
communication, the gateway IP is similar to
that for the IP over DCC.
Subnet Mask - 255.255.0.0 The network mask code of the subnet where
an NE resides, is used to identify the network
segment where an NE resides.
NSAP 26 4700040006 The NSAP address consists of the domain

Address hexadecimal 0001 address and NE SYSID. The domain address
numbers is editable, which can be 26 hexadecimal
digits at most.
6.5.3 Configuring Static Routes

This topic describes how to set the static routes.
Prerequisite
Procedure
Step 2 Select the NE icon and choose Communication > IP Stack Protocol Management from the
Function Tree.
Step 3 Click the IP Route Management tab.

Step 4 Click New. Then, the Create an IP Route dialog box is displayed. Set the following parameters
in the interface:
l Destination Address: 192.168.0.0
l Gateway IP: 10.100.11.0
l Subnet Mask: 255.255.255.0
Step 5 Click OK.
----End
6.5.4 Allocating DCC Resources

This topic describes how to allocate the DCC resources.
Prerequisite
Precautions
CAUTION
If the query result shows that the DCC resources are in use when the DCC allocating mode is
changed, delete the channel from DCC Rate Configuration.
Procedure
Step 2 Select the NE icon and choose Communication > DCC Management from the Function Tree.
Step 3 Click the DCC Resource Allocation tab and double-click Number for Allocation to set the
number of DCC channels according to actual requirements. For the DCC channel modes, refer
to Table 6-3.
Step 4 Click Apply.
----End

6.5.5 Querying Communication Status

This topic describes how to query the communication status.
Prerequisite
Procedure
Step 2 Select the NE icon and choose Communication > DCC Management from the Function Tree.
Step 3 Click the DCC Rate Configuration tab.
Step 4 Click Query. Then, the communication status is displayed.
----End
6.5.6 Querying the OSPF Protocol Status

This topic describes how to query the OSPF protocol status.
Prerequisite
Procedure
Step 2 Select the NE icon and choose Communication > IP Stack Protocol Management from the
Function Tree.
Step 3 Click the OSPF Parameter Setting tab.
Step 4 Click Query. Check whether the OSPF protocol is normal.
----End
6.6 OSI over DCC

The OSI over DCC protocol is used for communication in case of hybrid networking of the
Huawei equipment and the third-party equipment that support the OSI over DCC
communication.

This topic describes the basic concepts related to OSI over DCC.
When products of different vendors are used to create a transmission network, the OSI over DCC
protocol is used for communication. It can eliminate the limits for such hybrid networking. The

management information is transparently transmitted at the network layer. Thus, the networking
becomes more flexible.
6.6.3 Application
According to different network situations, OSI over DCC has two major applications.

This topic describes the basic concepts related to OSI over DCC.
NSAP
The OSI protocol takes the NSAP address as the protocol identification for nodes. The NSAP
address is of the format as shown in the following figure.
Figure 6-8 Format of a simple NSAP address
AREA ID SYS ID NSEL
One to 13 bytes Six bytes One byte
AREA ID: The length is adjustable from 1 to 13 bytes. The AREA ID is used for L2 routing
addressing within a domain. The values must be the same in the L1 route domain and be different
in the L2 route domain.
SYS ID: The length is fixed to six bytes. The SYS ID is used for route addressing within a
domain. For Huawei SDH optical equipment, the former three bytes are fixed to 0x08003E and
the latter three bytes are the same with the NE ID.
NSEL: The NSNL value is fixed to 0x1D.
The AREA ID of Huawei optical equipment is 47000400060001.
The ISO8348/AD2 defines a complicated format of the NSAP address. This manual does not
cover the naming details and functions of each character in the NSAP address format. In the
case of the OSI protocol, only the simple NSAP address format needs to be noticed.
Figure 6-9 Format of a complicated NSAP address
IDP DSP
High order DSP
AFI IDI+pad DFI ORG RES RD Area
Area address System ID NSEL
1 1 1 1 1 1 1 1 1 1 2
1 2 3 4 5 6 7 8 9
0 1 2 3 4 5 6 7 8 9 0
The Huawei equipment uses the simple NSAP address format. This does not affect the
interconnection between Huawei equipment and third-party equipment. The configuration of
the NSAP address requires that the AREA IDs in the same domain should be the same. The
NSAP address of the third-party equipment is configured as follows:
l AFI: 47

l IDI: 0005
l DFI: 80
l ORG: 000000
l RES: 0000
l RD: 0001
l AREA: 0001
l SYS ID: 00206005FA68
l NSEL: 1D
When a networking involves Huawei equipment and the third-party equipment within the same
domain, set the AREA ID to 4700058000000000000001 0001.
TP4
The TP4 protocol exists at the transport layer of the OSI protocol stake. The TP4 protocol is
applied to create a reliable communication connection. The TP4 protocol can handle the
problems such as data packet loss, repetition and falsification, which are caused by network
faults.

When products of different vendors are used to create a transmission network, the OSI over DCC
protocol is used for communication. It can eliminate the limits for such hybrid networking. The
management information is transparently transmitted at the network layer. Thus, the networking
becomes more flexible.
The client need not create extra DCN channels. The current DCC resources then can be used to
realize central management over equipment from several vendors.
The OSI protocol supports three types of network nodes: end system (ES), level 1 intermediate
systems (L1-IS), and level 2 intermediate systems (L2-IS).
6.6.3 Application
According to different network situations, OSI over DCC has two major applications.
Application Ι Third-Party Equipment Forwarding OAM Data of Huawei

Equipment
In this networking mode, the Huawei equipment is located at the edge of the network and the
third-party equipment is located at the core. The third-party equipment forwards the NM data
between Huawei equipment and the T2000. In this case, at least one GNE must be configured
in the subnet of the Huawei equipment.

Figure 6-10 Huawei equipment at the edge of the network

EMS of third-party
Huawei T2000 equipment
ES
OSI LAN
OSI DCN
Layer 2 routing
area
GNE
Legacy network
GNE
New network Third-party equipment
Huawei equipment
Application II Huawei Equipment Forwarding OAM data of Third-Party

Equipment
In this networking mode, the Huawei equipment is located at the core of the network while the
third-party equipment at the edge. The Huawei equipment forwards the NM data between the
NMS and third-party equipment.

Figure 6-11 Huawei equipment at the core of the network

EMS of third-party
Huawei T2000 equipment
ES
OSI LAN
OSI DCN
Layer 2 routing
area
GNE
New network
GNE
Legacy network
Third-party equipment
Huawei equipment
6.7 Configuring the OSI over DCC Communication

The OSI protocol is a communication protocol. It is widely used in the SDH management
network. The OSI over DCC protocol is applied to eliminate the limit of the hybrid networking.
The NM data can then be transparently transmitted at the network layer. Hence, the Huawei
equipment can interconnect with the third-party equipment that supports the OSI protocol.
CAUTION
Regardless of the operating system, Window or Solaris, the PC does not support the OSI protocol.
If the NMS installed at the PC side needs to use the OSI protocol to manage NEs, install the
corresponding protocol software at the PC side.

NOTE
The following parameters are provided as examples only. In actual application, configure the parameters

6.7.3 Setting NE Communication Parameter
6.7.4 Setting the NSAP Address for an NE
This topic describes how to set the NSAP address of a GNE. Do as follows to modify the NSAP
address of a GNE.
6.7.5 Configuring the Node Type for an NE
You can set the node type to ES, L1, or L2 for an NE according to the network plan. To facilitate
the network expansion, do not set the NE to the ES type.
6.7.6 Configuring Optical Port Protocol Stake and LAPD Role
The default protocol stake that is started at the optical port varies with products. If the current
protocol stake started at the optical port does not match with that in the network planning, do as
follows to set the protocol stake on the T2000: Select the optical port, delete the current
configuration, and then add the required protocol stake.
6.7.7 Querying Route Information
After the previous configuration is complete, connect the fibers correctly. Use the NMS to query
if the route information of each node is normal. If yes, the nodes can communicate with each
other. If not, perform careful check to ensure the configuration is correct.
6.7.8 Creating an OSI GNE
After the configuration of the NSAP address is complete, use the TP4 connection scheme to
create an OSI GNE.


See 6.3.3 Setting the NE ID.
6.7.3 Setting NE Communication Parameter

Prerequisite

Procedure
Step 2 Select the NE icon and choose Communication > Communication Parameters from the
Function Tree.
Step 3 Set the NSAP address for the NE according to the actual application. The following figure is for
reference only.
Step 4 Click Apply.
----End
6.7.4 Setting the NSAP Address for an NE

This topic describes how to set the NSAP address of a GNE. Do as follows to modify the NSAP
address of a GNE.
Prerequisite
Procedure
Step 1 Choose System > DCN Management from the Main Menu. Click the GNE tab.
Step 2 Right-click the Gateway NE icon and then select Modify GNE.

Step 3 In the displayed Modify GNE dialog box, set the NSAP address according to actual application.
The following NSAP address is provided as an example. Refer to Table 6-7 for the parameters
for GNE attributes.
l Gateway Type: OSI Gateway
l NSAP Address: 4700040006000108003E09004B1D
----End
Parameters
Table 6-7 Parameters for configuring the GNE attributes

Range Value
GNE Name - GNE name Indicates the GNE Name.
Gateway IP IP indicates the type of the GNE.

Type Gateway, Gateway
OSI
Gateway
NSAP - - An NSAP address with the maximum length is

Address 20-byte hexadecimal numbers. The format of the
NSAP address is "domain address + 08003e + NE
ID + NSEL". The maximum length of the domain
address is 13 bytes, which is entered by the user.
NSEL is the port number for the network-layer
protocol. The NSEL is fixed to 1d, which is of
one byte.
TSAP 8888 8888 Indicates the port number of the OSI protocol,
which cannot be modified.

6.7.5 Configuring the Node Type for an NE

You can set the node type to ES, L1, or L2 for an NE according to the network plan. To facilitate
the network expansion, do not set the NE to the ES type.
Prerequisite
Precautions
CAUTION
The configuration of the NE type takes effect only after the NE is reset. Resetting the NE may
interrupt the services.
Procedure
Step 2 Choose Communication > OSI Management from the Function Tree. Click the Network
Layer Parameters tab. Refer to Table 6-8 for the parameters at the network layer.
Step 3 Double-click Configuration Role and select a node type from the drop-down list.
Step 4 Click Apply.

Step 5 Click OK in the displayed Confirm dialog box. In the Operation Result dialog box displayed,
click Close.
----End

Parameters
Table 6-8 Network-layer parameters

Configuration ES, L1, L2 L1 Specifies the role of an NE in OSI

Role communications. ES indicates "do
not handle the IS protocol". L1
indicates "send route information in
the area". L2 indicates "send route
information between areas".
Current Role ES, L1, L2 L1 Specifies the current role of an NE

in OSI communications.
6.7.6 Configuring Optical Port Protocol Stake and LAPD Role

The default protocol stake that is started at the optical port varies with products. If the current
protocol stake started at the optical port does not match with that in the network planning, do as
follows to set the protocol stake on the T2000: Select the optical port, delete the current
configuration, and then add the required protocol stake.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explore. Choose Communication > DCC
Management from the Function Tree. Click the DCC Rate Configuration tab.
Step 2 Click Query. In the Operation Result dialog box that is displayed, click Close.
Step 3 Select the optical port that needs to be configured with the protocol stake. Click Delete to delete
the current configuration. The Prompt dialog box is displayed. Click Yes. Click Close in the
dialog box that is displayed.
Step 4 Click New and then the Create dialog box is displayed. Set each parameter in the dialog box
according to actual planning. Refer to Table 6-9 for the parameters for the configuration of the
protocol stake and LAPD role of optical ports.

----End
Parameters
When operating the OSI protocol stack at the port, the LAPD role of the NEs at all ports is
network by default. You need to set the LAPD role at each port according to the networking
plan.
Table 6-9 Parameters for setting the optical port protocol and LAPD role
Channel Type D1–D3, D4– D1–D3 Specifies the channel-occupied

D12, D1–D12 bytes, that is, the channel rate.
Protocol Type IP, OSI, IP Specifies the protocol type of DCC

HWECC, Auto communication.
LAPD Role User, Network Network The LAPD may be either User or
Network. In the case of two optical
ports that are connected by a fiber,
the LAPD roles must be different.
Follow this rule in the case of
networking exclusively of Huawei
equipment and hybrid networking
of Huawei equipment and third-
party equipment.

6.7.7 Querying Route Information

After the previous configuration is complete, connect the fibers correctly. Use the NMS to query
if the route information of each node is normal. If yes, the nodes can communicate with each
other. If not, perform careful check to ensure the configuration is correct.
Prerequisite
l After the previous configurations are complete, connect the fibers according to the actual
situation.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explore. Choose Communication > OSI
Management from the Function Tree. Click the Routing Table tab. Click Refresh.
Step 2 Check if the information in Link Adjacency Table is correct.
Step 3 Click the L1 Routing tab and the L2 Routing tab respectively to check if the route information
is correct.
----End
6.7.8 Creating an OSI GNE

After the configuration of the NSAP address is complete, use the TP4 connection scheme to
create an OSI GNE.
Prerequisite
l After the previous configurations are complete, connect the fibers according to the actual
situation.
Procedure
Step 1 Right-click on the Main Topology and choose New > Device. Set the NE type to OSN Series
> OptiX OSN 2000.
Step 2 Enter the NE attributes according to the IP address allocation diagram:
l ID: 24
l Extended ID: 9
l Name: NE1
l Gateway Type: Gateway
l Protocol: OSI
l NASP Address: 47000400060001 08003e0900181d
l NE User: root (default)

NOTE
An NSAP address with the maximum length is 20-byte hexadecimal numbers. The format of the NSAP
address is "domain address + 08003e + NE ID + NSEL". The maximum length of the domain address is
13 bytes, which is entered by the user. NSEL is the port number for the network-layer protocol. The NSEL
is fixed to 1d, which is of one byte.
Step 3 Click OK.
Step 4 Click on the Main Topology, and the icon of NE1 is displayed. There are and above the
NE1 icon, indicates gateway and indicates that the NE is not configured.
NOTE
The NE user root is the default NE user set for the NMS. The default password is password.
----End

Configuration Guide 7 Configuring the STP or RSTP
7 Configuring the STP or RSTP
About This Chapter
This topic uses an example to describe how to configure the STP or RSTP on the T2000.
7.1 Overview
This topic describes the background for the generation of the STP or RSTP, basic knowledge
about the STP or RSTP, and STP/RSTP port state transition.
Company F has three branches located in NE1, NE2, and NE3. The data must be shared between
the branches. Any two branches must be able to visit each other. The three branches must share
a 10 Mbit/s bandwidth dynamically. The Ethernet equipment of company F provides 100 Mbit/
s Ethernet ports. The RSTP must be enabled.
the engineering information.
This topic describes how to configure the RSTP/STP services on the T2000. The spanning tree
blocks certain ports to prevent the loop and thus to solve loop problems.

7 Configuring the STP or RSTP Configuration Guide
7.1 Overview
This topic describes the background for the generation of the STP or RSTP, basic knowledge
about the STP or RSTP, and STP/RSTP port state transition.
7.1.1 Background for the Generation of the STP or RSTP
Normally, the topology for the Layer 2 switching network involves a loop. The loop may cause
the broadcast storm and MAC address table flapping.
7.1.2 Basic Knowledge about the STP or RSTP
The spanning tree protocol (STP) blocks certain ports to prevent a loop. The rapid spanning tree
protocol (RSTP) realizes all the functions of the STP. The RSTP is modified and developed
based on the STP. In the case of the RSTP, the convergence speed in the network is faster. When
a link fails, the congested ports can be enabled quickly to restore the services.
7.1.3 STP/RSTP Port State Transition
An STP port may be in the enabled or disabled state. The enabled status is further classified into
the following states: blocking, listening, learning, and forwarding.
7.1.1 Background for the Generation of the STP or RSTP

Normally, the topology for the Layer 2 switching network involves a loop. The loop may cause
the broadcast storm and MAC address table flapping.
The problems are described as follows:
l Broadcast storm: The broadcast packets are duplicated and forwarded cyclically on the loop
until all the network bandwidth is exhausted. As a result, normal services and
communication equipment are heavily impacted. Even in the case of unicast packets, before
the equipment learns the destination MAC addresses, the unicast packets are broadcast, and
as a result, a broadcast storm may be caused.
l MAC address table flapping: In the case of a broadcast storm, a large number of packets
with the same source MAC address are broadcast to the loop, and then reach different ports
of the equipment on the opposite side. These ports then learn and replace the source MAC
address repeatedly. This is called MAC address table flapping. As many equipment
resources are used for the address learning, more load is placed on the equipment.
7.1.2 Basic Knowledge about the STP or RSTP

The spanning tree protocol (STP) blocks certain ports to prevent a loop. The rapid spanning tree
protocol (RSTP) realizes all the functions of the STP. The RSTP is modified and developed
based on the STP. In the case of the RSTP, the convergence speed in the network is faster. When
a link fails, the congested ports can be enabled quickly to restore the services.
The basic principle of the STP is as follows: Bridge protocol data units (BPDUs) are transmitted
between bridges to determine the topological structure of the network.
l Configuration BPDU (CBPDU)
l Topology change notification (TCN) BPDU
The RSTP specifications are described in IEEE 802.1W and IEEE 802.1D (2003). The RSTP is
developed based on the STP. Detailed modifications and supplements are made on the STP. The
RSTP shortens the time delay between congestion and forwarding at the ports, restores the
network connectivity rapidly, and provides better services if a temporary loop is not caused.

This is different from the STP. The protocol packets transmitted between the bridges that start
the RSTP are the RSTP data unit, namely, RST PDU.
The RSTP is compatible with the STP. When the RSTP is mixed with the STP, advantages of
the RSTP such as rapid convergence are unavailable.
The EMS1 board of the OptiX OSN 2000 supports both the STP and the RSTP. By default, the
RSTP is supported.
7.1.3 STP/RSTP Port State Transition

An STP port may be in the enabled or disabled state. The enabled status is further classified into
the following states: blocking, listening, learning, and forwarding.
Figure 7-1 shows the state transition of the STP port.
Figure 7-1 STP port state transition

Disabled
Listening
Disabled Blocking Learning Disabled
Forwarding
Enabled
Disabled
l Disabled: The port that is in the disabled state is not involved in the topology and does not
forward any packets. Any of the enabled states can change to this state. The disabled state
must change to the Blocking state to enter the Enabled state. The spanning tree cannot
control the disabled state because the port in the disabled state is not involved in the
topology. The disabled state can only be controlled by the management function.
l Blocking: The port in the Blocking state is involved in the topology but does not forward
any packets.
l Listening: The port in the listening state is involved in the topology, and can forward the
BPDU and discard packets. The Listening state is a temporary state in the process of
topology generation or change.
l Learning: The port in the learning state is involved in the topology and can forward the
BPDU and discard packets. The Learning state is a temporary state in the process of
topology generation or change.
l Forwarding: The port in the forwarding state is involved in the topology and can forward
packets and the BPDU.
Control the port state to make certain ports finally change into the forwarding or blocking state.
Disconnect at least one port from a loop to prevent the loop. This is the ultimate goal of the STP
algorithm.

In the case of the STP, the convergence time is relatively long and the ports play unclear roles.
In this case, the RSTP is widely used. In addition, the RSTP is compatible with the STP. In
comparison with the STP, the RSTP has the following improvements:
l Ports play clear roles through configuration.
l A more active handshake mechanism is applied to decrease the port status to three types:
– Forwarding
– Learning
– Discarding
l The Discarding state in the RSTP corresponds to the Listening and Blocking states in the
STP.
l Rapid convergence

Company F has three branches located in NE1, NE2, and NE3. The data must be shared between
the branches. Any two branches must be able to visit each other. The three branches must share
a 10 Mbit/s bandwidth dynamically. The Ethernet equipment of company F provides 100 Mbit/
s Ethernet ports. The RSTP must be enabled.

the engineering information.

Determine the networking diagram according to the engineering requirements.
Ethernet boards need to be added to the NE based on the type and volume of the service.
7.3.3 Service Configuration Diagram of Each NE
This topic describes the service configuration of each NE based on the engineering plan.

Determine the networking diagram according to the engineering requirements.

VCTRUNK1 VB VCTRUNK2
PORT2
NE1
T2000
B
PORT2 NE3 PORT2
PORT2
F1 NE2
F3
PORT2 VCTRUNK
F2
PORT2

Ethernet boards need to be added to the NE based on the type and volume of the service.
One EMS1 board is added to NE1, NE2, and NE3. Figure 7-3 shows the board information of
NE1, NE2, and NE3.
Figure 7-3 Board layout of NE1, NE2, and NE3
01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
4 4 1 PIU S
A A 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18
7.3.3 Service Configuration Diagram of Each NE

This topic describes the service configuration of each NE based on the engineering plan.

F1
10 Mbit/s
NE1
PORT2
PORT
LP1
VB1
VCTRUNK
LP2
LP3
VC4-1: VC12-6 to VC12-10

VC4-1: VC12-1 to VC12-5
VCTRUNK2
VCTRUNK1
VCTRUNK PORT
PORT VCTRUNK
LP2
LP2 F3
VCTRUNK1 LP1 PORT2
PORT2 LP1
VCTRUNK1
F2 VC4-1: VC12-1 to VC12-5
VC4-1: VC12-1 to VC12-5
LP3
LP3
10 Mbit/s 10 Mbit/s
VCTRUNK2 VCTRUNK2
VB1 VC4-1: VC12-6 to VC12-10 VC4-1: VC12-6 to VC12-10
VB1
NE3
NE2
Table 7-1 provides the information of the Ethernet service connection between NE2 and NE1/
NE3. Table 7-2 provides the information of the Ethernet service connection between NE1 and
NE3.
Table 7-1 Ethernet service connection table 1

Item F
NE NE2
VCTRUNK port type PE PE
VB VB1
Mounted port PORT2, VCTRUNK1, VCTRUNK2
NE NE1 NE3

Item F
VCTRUNCK port type PE PE
PORT VLAN ID 11 11
VB VB1 VB1
Mounted port PORT2, VCTRUNK1 PORT2, VCTRUNK2
Table 7-2 Ethernet service connection table 2
Item F
NE NE3
Timeslot VC4-1: VC12-1–VC12-5
VCTRUNK VCTRUNK1
VCTRUNCK port type PE
VB VB1
Mounted port PORT2, VCTRUNK1
NE NE1
Timeslot VC4-1: VC12-6–VC12-10
VCTRUNK VCTRUNK2
VCTRUNCK port type PE
PORT VLAN ID 11
VB VB1
Mounted port PORT2, VCTRUNK2

Table 7-3 is the forwarding filtering table of NE1, NE2, and NE3.
Table 7-3 Forwarding filtering table
NE VB VLAN ID Forwarding Port
In this example, the bridge of NE1 is assumed as the root bridge. Table 7-4 lists the bridge
priority of NE1, NE2, and NE3.
Table 7-4 Bridge priority table
Bridge Priority
NE1-VB1 4096
NE2-VB1 8192
NE3-VB1 12288

This topic describes how to configure the RSTP/STP services on the T2000. The spanning tree
blocks certain ports to prevent the loop and thus to solve loop problems.
Table 7-5 provides the process of configuring the STP/RSTP service on the T2000.
Table 7-5 Process of configuring the STP/RSTP

edur
e
1 Creating a board Required
2 Configuring Ethernet ports Required
3 Configuring bound paths Required
4 Creating the Ethernet LAN service Required
5 Configuring a forwarding filtering Required

table
6 Configuring the CAR This operation is optional. See 4.5.4

Configuring the Data of NE2.


edur
e
7 Configuring a cross-connection This operation is required. See 4.5.4

from the Ethernet board to the Configuring the Data of NE2.
SDH line board
8 Configuring the STP/RSTP Required
NOTE

This topic describes how to create the Ethernet boards on the T2000.
7.4.2 Configuring the Ethernet Ports of NE1
This topic uses an example to describe how to configure the Ethernet ports of NE1.
7.4.3 Configuring the Bound Paths of NE1
This topic uses an example to describe how to configure the bound paths of NE1.
7.4.4 Creating the Ethernet LAN Service of NE1
This topic uses an example to describe how to configure the Ethernet LAN service of NE1.
7.4.5 Configuring the VLAN Forwarding Filtering Table
This topic uses an example to describe how to configure the VLAN forwarding filtering table
of NE1.
7.4.6 Configuring Cross-Connections from Ethernet boards to SDH Line Boards on NE1
This topic uses an example to describe how to configure the cross-connections from the Ethernet
boards to the SDH line boards on NE1.
7.4.7 Configuring the Data of NE2 and NE3
This topic uses an example to describe how to configure the data of NE2 and NE3.
7.4.8 Configuring the STP/RSTP
This topic uses an example to describe how to enable the STP/RSTP.
7.4.9 Querying STP/RSTP Running Information
This topic uses an example to describe how to query the running information of the STP/RSTP.

This topic describes how to create the Ethernet boards on the T2000.
Prerequisite
l The Ethernet board must be installed on the equipment.

Procedure
Step 1 In the Main Topology, double-click the NE1 icon. Then, the NE panel is displayed.
Step 2 Right-click slot 9 according to the board layout shown in Figure 7-3, and select EMS1 from the
displayed boards.
Step 3 Make sure that the EMS1 board is configured in slot 9 and that the ETFS8 board is configured
in slot 16. Click to exit the NE panel diagram.
Step 4 Refer to Steps 1–3 to create the Ethernet boards of NE2 and NE3. Figure 7-3 shows the board
layout of NE2 and NE3.
----End
7.4.2 Configuring the Ethernet Ports of NE1

This topic uses an example to describe how to configure the Ethernet ports of NE1.
Prerequisite
Precautions
CAUTION
This configuration is invalid for internal ports (VCTRUNK ports). Hence, retain the default
configuration (auto-negotiation) for VCTRUNK ports.
Configure external ports according to the actual port status.
Procedure
Step 2 Select 9-EMS1 from the Object Tree and choose Configuration > Ethernet Interface
Step 3 Select External Port and perform the following settings:

1. Click the Basic Attributes tab. Set Enabled/Disabled of PORT2 to Enabled.
2. Click Apply.
3. Click the TAG Attributes tab. Set TAG of PORT2 to Access and Default VALN ID of
PORT2 to 11. For other parameters, the default values are used.
4. Click Apply.
Step 4 Select Internal Port, and click the Advanced Attributes tab. Set Point to Point Attributes of
VCTRUNK1 and VCTRUNK2 to Adaptive connection.

Step 5 Click Apply.
----End
Parameters
Table 7-6, Table 4-12, and Table 7-7 list the configuration parameters for Ethernet ports.
Table 7-6 Parameters for setting the basic attributes of Ethernet ports

t Value
Enabled/ Enabled, Disabled Disable Specifies the enabled or disabled state of

Disabled d the port. "Enabled" means that this port is
allowed to access the services. "Disabled"
means that this port is not allowed to access
the services.
Working Auto-Negotiation, Auto- The auto-negotiation mode is

Mode 10M Half-Duplex, Negotia recommended, because it can
10M Full-Duplex, tion automatically detect the best working
100M Half-Duplex, mode to combine a port and its
100M Full-Duplex, interconnected port. Hence it facilitates
1000M Half- maintenance. During configuration, make
Duplex, 1000M sure that the working modes of the
Full-Duplex connected ports are the same. If the
working modes are different, the services
are unavailable.
Maximum 1518–65535 1522 It is also called the maximum transmitted

Frame unit (MTU).
Length
MAC Non-Loopback, Non- Specifies the loopback state at the MAC

Loopback Inloop, Outloop Loopba layer.
ck
PHY Non-Loopback, Non- Specifies the loopback state at the PHY

Loopback Inloop, Outloop Loopba layer.
ck
Table 7-7 Point-to-point attributes
Point-to-Point Application Port Attribute

Attribute
Link connection The port is forced to be a point- Full duplex

to-point link connection.
Shared media The port is forced to connect to Half duplex

the shared media.

Point-to-Point Application Port Attribute

Attribute
Adaptive connection The connection is adaptive by Auto-negotiation

default.
7.4.3 Configuring the Bound Paths of NE1

This topic uses an example to describe how to configure the bound paths of NE1.
Prerequisite
Procedure
Step 1 In the Internal Port page, click the Bound Path tab.
Step 2 Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
Step 3 To configure the bound paths of VCTRUNK1, set the parameters in the dialog box as follows:
l Level: VC12-xv
l Available Timeslots: VC12-1 to VC12-5. Click .
Step 4 To configure the bound paths of VCTRUNK2, set the parameters in the dialog box as follows:
l Level: VC12-xv
l Available Timeslots: VC12-6 to VC12-10. Click .
Step 5 Click OK.
----End
7.4.4 Creating the Ethernet LAN Service of NE1

This topic uses an example to describe how to configure the Ethernet LAN service of NE1.
Prerequisite

Procedure
Step 1 Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New and the Create Ethernet LAN Service dialog box is displayed.
Step 3 Set VB Name to VB1.
Step 4 Click Configure Mounted Port and the VB Mount Port Configuration dialog box is
displayed.
Step 5 Set as follows in the dialog box according to the service configuration diagram of NE1:
l Set VB Mount Port to PORT2, VCTRUNK1, and VCTRUNK2. Then, click .

l Click OK.
Step 6 For other parameters, the default values are used. Click OK in the Create Ethernet LAN
Service dialog box.
----End
Parameters
Table 7-8 lists the configuration parameters for the EPLAN service.
Table 7-8 Parameters for configuring the Ethernet LAN service
Parameter Value Range Defau Description

lt
Value
VB Name A maximum of sixteen - Specifies the VB name.

English characters
Mounted Port - - The mount port may be the MAC port

or the VCTRUNK port.
VLAN ID 1–4095 - Specifies the VLAN ID. Configures

the forwarding filtering table
Selected - - Specifies the physical port for

Forwarding forwarding the data.
Port
7.4.5 Configuring the VLAN Forwarding Filtering Table

This topic uses an example to describe how to configure the VLAN forwarding filtering table
of NE1.
Prerequisite

Procedure
Step 1 Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Click the VLAN tab.
Step 2 Click Create and the Create VLAN dialog box is displayed.
Step 3 Set the following parameters in the Create VLAN dialog box:
l VB: 1-VB1
l VLAN ID: 11
l Selected forwarding ports: PORT2, VCTRUNK1, VCTRUNK2
Step 4 Click OK.
----End
7.4.6 Configuring Cross-Connections from Ethernet boards to SDH

Line Boards on NE1
This topic uses an example to describe how to configure the cross-connections from the Ethernet
boards to the SDH line boards on NE1.
Prerequisite

Procedure
Step 1 Select NE1 from the Object Tree.
Step 2 Choose Configuration > SDH Service Configuration from the Function Tree.
Step 3 Click Create, and the Create SDH Service dialog box is displayed.
Step 4 Set the following parameters in the dialog box:

l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2
Step 5 Click OK.
Step 6 Refer to Step 4 and set the following parameters in the dialog box:
l Level: VC12
l Source VC4: VC4-1
l Sink VC4: VC4-2.
Step 7 Click OK.
----End
7.4.7 Configuring the Data of NE2 and NE3

This topic uses an example to describe how to configure the data of NE2 and NE3.
NOTE
The method of configuring the data of NE2 and NE3 is the same as the method of configuring the data of
NE1, except that the parameter settings are different. For the configuration process, see 7.4.6 Configuring
Cross-Connections from Ethernet boards to SDH Line Boards on NE1.
7.4.8 Configuring the STP/RSTP

This topic uses an example to describe how to enable the STP/RSTP.

Prerequisite
l The Ethernet Layer 2 switching services must be created before you enable the RSTP
protocol.
Precautions
CAUTION
The RSTP identifies a bridge by the bridge priority. The smaller the priority value is, the higher
the priority is.
In the case of the bridges with the same priority, the smaller the priority value of the port, the
higher the priority.
Procedure
Step 2 Select 9-EMS1 from the Object Tree and choose Configuration > Layer-2 Switching
Management > Spanning Tree from the Function Tree. Click .
Step 3 Click the Bridge Parameter tab. Click Query to query the bridge parameters. According to
Table 7-4, set Priority to 4096. For other parameters, use the default values.
Step 4 Click Apply.
Step 5 Click the Port Parameter tab. Click Query to query the port parameters. Set Priority according
to the actual requirements. For other parameters, use the default values.
Step 6 Click Apply.
Step 7 Click the Protocol Enable tab. Set the parameters as follows:
l Protocol Enabled: Enabled
l Protocol Type: RSTP
Step 8 Click Apply.
Step 9 A dialog box is displayed indicating that this operation may cause service interruption. Click
OK.

Step 10 A dialog box is displayed indicating that the operation is successful.

Step 11 Refer to Table 7-4 and refer to Steps 1–10 to start the RSTP for NE2 and NE3.
----End
Parameters
Table 7-9 lists the bridge parameters. Table 7-10 lists the port parameters.
Table 7-9 Bridge parameters

t
Value
Priority 0, 4096, 8192, 32768 Indicates the priority of the bridge. The step is
12288, ……, 4096. The bridge priority increases when the
61140 value decreases.
Max Age(s) 6–40 20 Specifies the maximum age of the message.

The larger the value is, the more stable the
topology is, but the slower the fault locating is.
Hello Time(s) 1–10 2 Specifies the interval at which packets are sent.
The larger the value is, the fewer network
resources the spanning tree occupies, but the
less stable the topology is.
Forward 4–30 15 Indicates the state transition time delay of the

Delay(s) port. The larger the value is, the more stable the
topology is, but the longer it takes to build up
the topology.
Table 7-10 Parameter description

Parameter Value Range Default Description
Value
Priority 0–255 128 Indicates the priority of the port. The

step is 16. The bridge priority increases
when the value decreases.

Parameter Value Range Default Description

Value
The bridge 1–65535 - The path value is used to measure how

priority many overheads are needed to transport
increases when the messages through the network
the value bridge port. The larger the port rate is,
decreases. the smaller the path value is. The default
value for the VCTRUNK port is 2, the
default value for the GE port is 4, and the
default value for the FE port is 19.
Status Blocking, - Indicates the status of the port. This

Listening, parameter can be queried only.
Learning,
Forwarding,
Discarding
Admin Edge Enabled, Disabled Disabled Indicates whether to enable the edge
Attribute port.
Protocol Enabled, Disabled Enabled Indicates whether to enable the port.

Enabled
7.4.9 Querying STP/RSTP Running Information

This topic uses an example to describe how to query the running information of the STP/RSTP.
Prerequisite
l The STP/RSTP must be enabled.
NOTE
l The priority to query the bridge running information is determined by both the bridge ID and the bridge
priority.
l In the spanning tree, the bridge ID represents the priority. The smaller the VB ID, the higher the priority.
CAUTION
After the RSTP is in effect, the root port and the specified ports (for the root port) are in the
forwarding state. Other ports are in the discarding state.

Procedure
Step 2 Select 9-EMS1 from the Object Tree and choose Configuration > Layer-2 Switching
Management > Spanning Tree from the Function Tree. Click .
Step 3 Click the Bridge Running Information tab. Click Query to query the running information of
the bridge.
Step 4 Click the Port Running Information tab. Click Query to query the running information of the
port.
Table 7-11 lists the port states that are applicable for the previous example.
Table 7-11 Status of the internal ports

Port Mounted Port Status
NE1-9-EMS1-VB1-2 VCTRUNK1 Forwarding
NE3-9-EMS1-VB1-3 VCTRUNK2 Discarding
----End

Configuration Guide 8 Configuring ETH-OAM
8 Configuring ETH-OAM
About This Chapter
As Ethernet services develop, the operators give more and more attention to the maintainability
of the equipment. When the Ethernet services expands to MANs and WANs, Ethernet operation,
administration and maintenance (ETH-OAM) of the transmission network needs to be
implemented in a timely manner. The Ethernet Layer 2 maintenance capability, however, is
rather limited. Thus, the ETH-OAM is generated.
8.1 Overview
The ETH-OAM can be realized by the following means: continuity check (CC), loopback (LB),
link trace (LT).
The EPL services are configured between two NEs. Continuity, loopback and link trace tests
are required for the two NEs.
This topic describes how to configure the ETH-OAM on the T2000.
8.4 Creating MPs
The MP refers to the function entity of ETH-OAM, including the MEP and MIP. This topic
describes how to create an MP.
8.5 Activating the CC
In a unidirectional continuity check, a message is sent over the network to check if any fault
exists in continuity. The MEP at the source end constructs the frames of the continuity check
message (CCM), and sends the CCM frames in a periodic manner. After receiving the CCM
from the source, the MEP at the sink end starts the CC function. If the MEP at the sink end does
not receive the CCM during a certain period of time, a CC-LOS alarm is automatically reported.
This topic describes how to activate the CC.
8.6 Enabling the LB
During the LB check, the source MEP constructs and transmits the loopback message (LBM)
frames and starts the timer for timing. After receiving the LBM, the MP at the sink end constructs
and sends the frame of a loopback return (LBR) back to the MEP at the source end. This indicates
the loopback is successful. If the timer at the MEP times out, the loopback fails. This topic
describes how to enable the LB.
8.7 Starting the LT

8 Configuring ETH-OAM Configuration Guide
During the LT check, the source MEP constructs and transmits LTM frames and starts the timer
for timing. All the MPs that receive the LTM frames send the LTR frame response. According
to the LTR frame response, you can verify all the MIPs that pass from the source MEP to the
sink MEP. This topic describes how to start the LT.

8.1 Overview
The ETH-OAM can be realized by the following means: continuity check (CC), loopback (LB),
link trace (LT).
The process of the ETH-OAM is as follows: The maintenance point initiates the fault detection.
When a fault is detected at the maintenance point, related alarms are reported. Meanwhile, these
alarms can be synchronized onto the Ethernet path related to the maintenance point.
The object of the ETH-OAM function is the maintenance point (MP). The maintenance points
consist of the maintenance end point (MEP) and maintenance intermediate point (MIP).
Figure 8-1 Application example of the maintenance point
MEP1 MEP2
NE1 NE2
MEP1 MIP1 MIP2 MEP2
VCTRUNK
PORT
The maintenance point is created based on the traffic flow. All the maintenance points at the
same level on the same traffic flow form the maintenance domain, thus implementing the
maintenance of the traffic flow. When the maintenance point is created, the maintenance domain
where this maintenance point is located is determined.
l The IDs of the maintenance points must be different from each other in the same network.
l The levels and VLAN IDs of different MPs in the same maintenance domain must be the
same.
– To ensure that MPs belong to the same maintenance domain, set the level of the MPs
to the same.
– To ensure the maintenance of the same traffic flow, set the VLAN IDs to the same.
l Only the MEP is directional. Set the direction from the external physical port to the
VCTRUNK port on the system side to the SDH direction. The MIP can be set only to be
bidirectional.
NOTE
Create the Ethernet service before you create the MPs.

The EPL services are configured between two NEs. Continuity, loopback and link trace tests
are required for the two NEs.
Networking Diagram

T2000
NE1 NE2
PORT1 PORT1

Configure the EMS1 board on NE1 and NE2 based on the service type and service volume.
Figure 8-3 shows the board information of NE1 and NE2.
01 02 03 04 05 06 07 08 09 10 11 12 14 16 17 18
S
C PIU
T P X X E C E A
A T C C M T U
1 1 S S S F X
4 4 1 PIU S
A A 8
01 02 03 04 05 06 07 08 09 10 11 13 15 16 17 18
Fiber/Cable Connection
Table 8-1 shows the fiber and cable connection.
Table 8-1 Fiber/Cable connection table
Local NE Opposite NE
NE Name Slot Board Optical NE Slot Board Port

Name port Name Numb
number er
NE1 27 OSB4A 1IN NE2 27 OSB4A 1OUT
NE1 27 OSB4A 1OUT NE2 27 OSB4A 1IN


This topic describes how to configure the ETH-OAM on the T2000.
Table 8-2 lists the configuration process.
Table 8-2 Process of configuring the ETH-OAM
Proced Operation Remarks

ure
1 Creating a board See 2.10 Creating a Board.
2 Creating fibers See 2.11 Creating Fibers.
3 Configuring Ethernet Services See 4 Configuring Ethernet Services.
4 Creating MPs -
5 Activating the CC -
6 Enabling the LB -
7 Starting the LT -
8.4 Creating MPs

The MP refers to the function entity of ETH-OAM, including the MEP and MIP. This topic
describes how to create an MP.
Prerequisite
Context
CAUTION
In the OAM test, all the MPs of a traffic flow must be within the same maintenance domain. If
an MP of the same level or of a higher level is created in the existing maintenance domain of a
traffic flow, the maintenance domain is damaged and as a result, the OAM test fails.
Procedure

Step 2 Select the 9-EMS1 board from the Object Tree and choose Configuration > Ethernet
Maintenance > Ethernet OAM from the Function Tree. Click .
Step 3 Create the MP of NE1 as follows:
1. Click Create, and the Create MP dialog box is displayed. Set the following parameters:
l Node: NE1-9-EMS1-PORT1
l MP ID: 00-00-0001
l Type: MEP
l Direction: SDH Direction
2. Click Advanced to display the Advanced Configuration dialog box. Set the parameters.
Step 4 Create the MIP of NE1. Click New, and the Create MP dialog box is displayed. Set the following
parameters:
l Node: NE1-9-EMS1-VCTRUNK1
l MP ID: 00-00-0002
l Type: MIP
l Use the default values for other parameters. Then, click OK.
Step 5 Click . Click NE2 and click OK.

Step 6 Repeat Step 3 to create the MEP of NE2. Click Create, and the Create MP dialog box is
displayed. Set the following parameters:
l Node: NE2-9-EMS1-PORT1
l MP ID: 00-00-0003
l Type: MEP
l Direction: SDH Direction
Step 7 Repeat Step 4 to create the MIP of NE2. Click New, and the Create MP dialog box is displayed.
Set the following parameters:
l Node: NE2-9-EMS1-VCTRUNK1
l MP ID: 00-00-0004
l Type: MIP
----End
8.5 Activating the CC

In a unidirectional continuity check, a message is sent over the network to check if any fault
exists in continuity. The MEP at the source end constructs the frames of the continuity check
message (CCM), and sends the CCM frames in a periodic manner. After receiving the CCM
from the source, the MEP at the sink end starts the CC function. If the MEP at the sink end does

not receive the CCM during a certain period of time, a CC-LOS alarm is automatically reported.
This topic describes how to activate the CC.
Prerequisite
l The MPs must be created.
To ensure that the ETH-OAM and other functions can work normally in different conditions,
set the average CC period according to Table 8-3 when you activate the CC.
Table 8-3 Recommended average CC period
Number of MPs (N) Recommended Average CC Period
Nx32 1000 ms
32 < Nx48 4000 ms
48 < Nx64 8000 ms
64 < Nx96 16000 ms
96 < Nx128 20000 ms
In addition, the CC message can be transmitted at a lower rate to minimize the impact on the
utilization of the network bandwidth.
Procedure
Step 2 Select 9-EMS1 from the Object Tree and choose Configuration > Ethernet Maintenance >
Ethernet Service OAM from the Function Tree. Click .
Step 3 Select the created MEP and choose Activate CC from the shortcut menu.
----End
8.6 Enabling the LB

During the LB check, the source MEP constructs and transmits the loopback message (LBM)
frames and starts the timer for timing. After receiving the LBM, the MP at the sink end constructs
and sends the frame of a loopback return (LBR) back to the MEP at the source end. This indicates
the loopback is successful. If the timer at the MEP times out, the loopback fails. This topic
describes how to enable the LB.

Prerequisite
Only MEPs can initiate the LB test, but both the MEP and MIP can work as the receive end in
the test.
Procedure
Step 3 Select the created MEP and choose Start LB from the shortcut menu.
Step 4 In the LB Test dialog box, set the IDs of the source and sink MPs for the LB test.
----End
Result
l If the LB test is successful, the following feedback is received.
– The Operation Result dialog box is displayed, indicating that the LB test is successful.
– The Test Result displays relevant information to indicate that the LB test is successful.
l If the LB test fails, the following feedback is received.
– The Operation Result dialog box is displayed, indicating that the LB test times out.
– The Test Result displays relevant information to indicate that the LB test fails.
8.7 Starting the LT

During the LT check, the source MEP constructs and transmits LTM frames and starts the timer
for timing. All the MPs that receive the LTM frames send the LTR frame response. According
to the LTR frame response, you can verify all the MIPs that pass from the source MEP to the
sink MEP. This topic describes how to start the LT.
Prerequisite
Only MEPs can initiate the LT test and work as the termination point in the test.

Procedure
Step 3 Select the created MEP and choose Start LT from the shortcut menu.
Step 4 In the LT Sink MP ID dialog box, set LT sink MP ID to 00-00-0003. Click OK.
Step 5 A dialog box is displayed indicating that the operation is successful.
----End

Configuration Guide 9 Configuring the LPT
9 Configuring the LPT
About This Chapter
LPT stands for link state pass through, and it is a link-based protection scheme. If the LPT
function is enabled at a port, the service of the port is automatically switched to the protection
link when the working link becomes faulty. This topic describes how to configure the LPT.
9.1 Overview
This topic describes the basic concepts related to LPT.
9.2 Application
LPT is a link-based protection mode. The LPT information is provided for data communication
equipment such as routers that are interconnected with the transmission equipment.
9.3 Configuring the Point-to-Point LPT Function
The point-to-point (P2P) LPT function is applicable to the P2P services. When the access link
or the transmission network is faulty, the P2P LPT function ensures that the equipment at both
ends starts the backup network in time to ensure normal communication.
9.4 Configuring the P2MP LPT Function
The point-to-multipoint (P2MP) LPT function is applicable to the P2MP services. If the
convergence point is faulty, the P2MP LPT function is enabled to notify all the access points of
quickly switching to the backup network.

9 Configuring the LPT Configuration Guide
9.1 Overview
This topic describes the basic concepts related to LPT.
Primitive
In the No. 7 signaling structure, when a higher layer requests service from a lower layer or when
a lower layer provides service to a higher layer, the service user needs to communicate with the
service provider. The signaling data communicated between two adjacent layers is known as the
primitive.
Pass-Through
"Pass-through" refers to the action of receiving the information that is transmitted as it is, in the
specific transmission direction.
Bearer Mode
"Bearer mode" refers to the trail on which the LPT protocol packets are transmitted. Different
bearer modes are used for transmitting different LPT protocol packets. If the bearer mode of the
received LPT protocol packets is inconsistent with the bearer mode at the receive end of the
equipment, the LPT protocol packets will be discarded.
9.2 Application
LPT is a link-based protection mode. The LPT information is provided for data communication
equipment such as routers that are interconnected with the transmission equipment.
OptiX All the Ethernet service boards of the OptiX OSN 2000 support point-to-point LPT and
the EMS1 board supports point-to-multipoint (P2MP) LPT.
9.2.1 Application of the P2P LPT
9.2.2 Application of the P2MP LPT
The point-to-multipoint LPT function is used to detect faults on the access node link or in the
service network for point-to-multipoint LPT services.
9.2.1 Application of the P2P LPT

Fault in the Link at the Access Point

l Locating the fault

Disconnect the link

Report the link Service and report the
fault alarm network LPT_RFI alarm
Access Service Broken Service Access

node 1 equipment A equipment B node 2
1. After the service equipment A detects any fault in the access link, it reports the alarm to
inform that the local access point is faulty and sends the Broken control frame to the service
equipment B.
2. After the service equipment B receives the Broken control frame, it deactivates the local
link and reports the LPT_RFI alarm.
l Restoring the service network
Service
Clear the link network Restore the
fault alarm link
Non_Broken
Access Service Service Access
node 1 equipment A equipment B node 2
1. After the service equipment A detects that the fault in the access link disappears, it sends
the Non_Broken control frame to the service equipment B.
2. After the service equipment B receives the Non_Broken control frame, it activates the local
link again.
Fault in the Service Network

Broken Broken
Access Service Service Service Access
node 1 equipment network equipment node 2
A B
The service equipment A and B can detect whether the service network is available. If the service
network is unavailable, the service equipment A and B sends the Broken primitive to each other
and disconnects the connection from the local users,
NOTE
The method of troubleshooting a unidirectional or bidirectional P2MP LPT fault in the service network is
the same.
l If a bidirectional fault occurs in the service network, the service equipment A and B can detect the
fault, and thus determines to disconnect the connection between the local end and the users and then
sends the Broken primitive to the opposite end.
l If a unidirectional fault occurs in the service network, for example, if the fault occurs in the B–>A
direction, only the service equipment A can detects the fault. In this case, the service equipment A
disconnects the connection between the local end and the access node 1, and uses the service network
in the A–>B direction where no fault occurs to send the Broken primitive to the service equipment B.
After the service equipment B receives the Broken primitive, it disconnects the connection between
the local end and the access node 2, thus to complete the fault locating process.

l Restoring the service network

Non_Broken Non_Broken
A B
After detecting that the service network is restored, the service equipment A and B sends the
Non-Broken primitive to each other to inform the opposite end that the link is restored, and
restores the connection between the local end and the local users immediately.

A B
If the service equipment A and B receives the Non_Broken primitive from each other of if the
waiting time before the Broken frame is received times out, the service equipment A and B
determines that the entire link is normal and thus restores the local link of the service equipment.
9.2.2 Application of the P2MP LPT

The point-to-multipoint LPT function is used to detect faults on the access node link or in the
service network for point-to-multipoint LPT services.
NOTE
The point-to-multipoint LPT function processes faults in the unidirectional service network and
bidirectional service network by using the same means.
Detecting the Faults in the Link of the Access Point on the Convergence Node Side
Disconnect the
link and report the
LPT_RFI alarm
Service Access
Report the link Broken equipment B node 1
fault alarm
Convergence Service Disconnect the
node equipment A link and report the
LPT_RFI alarm
Broken Service Access
equipment C node 2
Service Equipment A that connects to the convergence node detects that the link at the access
node is faulty, and then reports the alarm of the fault that occurs at the local end. At the same
time, service equipment A transmits Broken packets to service equipment B and C. After
receiving the packets, equipment B and C disconnect the local end. In this case, equipment B
and C report the LPT_RFI alarms.
l Restoring the link

Restore the
Service link Access
Non_Broken
equipment B node 1
Clear the link
fault alarm
Convergence Service
node equipment A
Restore the
Service link Access
Non_Broken
equipment C node 2
Service Equipment A that connects to the convergence node detects the link restoration at the
access nod, and then reports the clearance of the local fault alarm. At the same time, service
equipment A transmits Non-Broken packets to service equipment B and C. After receiving the
packets, equipment B and C recover the connections to the local end. In this case, equipment B
and C report the clearance of LPT_RFI alarms.
Access Node Link Fault on the Access Node Side

l Scenario 1
– Locating the fault
Report the link
Disconnect the fault alarm
link and report the Service Access
Broken
LPT_RFI alarm equipment B node 1
Convergence Service
node equipment A Report the link
fault alarm
Service Access
Broken
equipment C node 2
1. Service equipment B that connects to access node 1 detects that the link at the access
node is faulty, and then reports the alarm of the local access node fault. At the same
time, equipment B transmits the Broken packets to service equipment A.
2. After receiving the packets, equipment A reports the LPT_RFI alarm and transmits
the Broken packets to equipment C at the same time.
3. In this case, service equipment C disconnects the local end and reports the LPT_RFI
alarm.
– Restoring the link
Clear the link
Service fault alarm Access
Non_Broken equipment B node 1
Recover
the link
Convergence Service
node equipment A
Restore the
Service link Access
Non_Broken
equipment C node 2
1. Service equipment B that connects to access node 1 detects that the link at the access
node is restored, and then reports the clearance of the local fault alarm. At the same
time, equipment B transmits the Non-Broken packets to service equipment A.

2. After receiving the packets, equipment A recovers the connection to the local end and
then reports the clearance of the LPT_RFI alarm. At the same time, equipment A
transmits the Broken packets to equipment C.
3. In this case, service equipment C recovers the connection to the local end and then
reports the clearance of the LPT_RFI alarm.
l Scenario 2
– Locating the fault
Disconnect the link
and report the Service Access
Convergence Service
Report the link
node equipment A
fault alarm Access
node 2
Service
Broken
equipment C
Access
node 3
Service equipment C that connects to access node 2 detects that the link at the access node
is faulty, and then reports the alarm of the fault that occurs at the local end. At the same
time, equipment C transmits the Broken packets to service equipment A. In this case, service
equipment A disconnects the local end and reports the LPT_RFI alarm.
Disconnect the link
and report the
LPT_RFI alarm
Service Access
Broken equipment B node 1
Convergence Service
node equipment A
Access
node 2
Broken_Ack Service
equipment C
Access
Disconnect the node 3
link and report the
LPT_RFI alarm
After receiving the Broken packets where the response confirmation frame is contained,
service equipment A transmits the Broken packets to service equipment B. After receiving
the Broken_Ack packets, service equipment C disconnects the access node 3 and reports
the LPT_RFI alarm. After receiving the Broken packets from equipment A, service
equipment B recovers the link of the local end and reports the LPT_RFI alarm.
– Restoring the link

Recover the link

and clear the Service Access
Convergence Service
node equipment A Restore the
Access
link
node 2
Service
Non_Broken equipment C
Access
node 3
Service Equipment C that connects to the access node 2 detects the link at the access node
is restored, and then reports the clearance of the fault alarm at the local end. At the same
time, service equipment C transmits Non-Broken packets to service equipment A. After
receiving the packets, equipment A recovers the local connection and reports the clearance
of the LPT_RFI alarm.
Recover the link
and clear the
LPT_RFI alarm
Non_Broken Service Access

equipment B node 1
Convergence Service
node equipment A
Access
node 2
Non_Broken_Ack Service
equipment C
Access
Recover the link
node 3
and clear the
LPT_RFI alarm
After receiving the Non_Broken packets where the response confirmation frame is
contained, service equipment A transmits the Non_Broken packets to service equipment
B. After receiving the Non_Broken_Ack packets, service equipment C recovers the
connection to access node 3 and reports the clearance of the LPT_RFI alarm. After
recovering the Non_Broken packets from equipment A, service equipment B disconnects
the local end and reports the clearance of the LPT_RFI alarm.
Fault in the Service Network

Disconnect the
link and report the
LPT_RFI alarm
Disconnect the link
and report the Broken Service Access
Convergence Service Disconnect the

node equipment A link and report the
LPT_RFI alarm
Broken Service Access
equipment C node 2

The bidirectional fault occurs in the service network between service equipment A and B. In
this case, equipment A and B cut the local connections respectively and report the LPT_RFI
alarms. At the same time, equipment A transmits the Broken packets to equipment C. In this
case, service equipment C cuts the local connection and reports the LPT_RFI alarm.
l Restoring the link

Recover the link
and clear the
Recover the link LPT_RFI alarm
and clear the Non_Broken Service Access
Convergence Service Recover the link

node equipment A and clear the
LPT_RFI alarm
Service Access
Non_Broken
equipment C node 2
The bidirectional fault is cleared in the service network between service equipment A and B. In
this case, equipment A and B recovers the local connections respectively and report the clearance
of the LPT_RFI alarms. At the same time, equipment A transmits the Non-Broken packets to
equipment C. In this case, service equipment C recovers the connection to the local end and then
reports the clearance of the LPT_RFI alarm.
9.3 Configuring the Point-to-Point LPT Function

Prerequisite
l The Ethernet data boards support the P2P LPT function.
l The specified port must be configured with the P2P EPL services.
Precautions
NOTE
The P2P LPT conflicts with the P2MP LPT. Hence, you can select only one configuration mode to
implement the LPT function on the same Ethernet service processing board.
Procedure
Step 2 Select the relevant Ethernet data board, and then choose Configuration > Ethernet Interface
Management > LPT Management from the Function Tree. Then, click .
Step 3 Click Query. A dialog box is displayed indicating that the operation is successful. Click
Close.

Step 4 Select PORT1 and VCTRUNK port, and then set LPT to Yes. For the parameters of the P2P
LPT, refer to Table 9-1.
Step 5 Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
Step 6 Refer to Steps 1–5 to set LPT to Yes for the opposite NE in the network.
----End
Parameter
Table 9-1 Parameters for the P2P LPT
VCTRUNCK - - Indicates the VCTRUNK port that

Port can be used. For configuring the
LPT.
Direction Forward - Indicates the direction of the EPL

direction, transparent transmission service
reverse over the port. The direction is
direction forward when the source port is
PORT and the sink port is
VCTRUNK.
The direction is reverse when the
source port is VCTRUNK and the
sink port is PORT.
LPT Yes, No - Specifies whether to use the LPT.
Bearer Mode GFP GFP Bearer Mode needs to be set only

(HUAWEI), (HUAWEI) for the VCTRUNK ports.
Ethernet, GFP
(CSF)
Port-Type Port An integer in the - To set this parameter, set LPT to

Hold-Off Time range from 0 to Yes.
(ms) 10000, with a To prevent the impact caused by
step of 500 random poor quality (jitter) of the
link, and to prevent frequently
switching the link, you need to set
the port hold-off time.
VCTRUNK An integer in the - To set this parameter, set LPT to

Port Hold-Off range from 0 to Yes.
Time (ms) 10000, with a To prevent the impact caused by
step of 500 random poor quality (jitter) of the
link, and to prevent frequently
switching the link, you need to set
the port hold-off time.

9.4 Configuring the P2MP LPT Function

The point-to-multipoint (P2MP) LPT function is applicable to the P2MP services. If the
convergence point is faulty, the P2MP LPT function is enabled to notify all the access points of
quickly switching to the backup network.
Prerequisite
l The Ethernet data boards support the P2MP LPT function.
l The specified port must be configured with the P2P EPL services.
Precautions
NOTE
The P2P LPT conflicts with the P2MP LPT. Hence, you can select only one configuration mode to
implement the LPT function on the same Ethernet service processing board.
Currently, only the EMS1 board supports the P2MP LPT.
Procedure
Management > LPT Management from the Function Tree. Then, click .
Step 3 Click Advanced Configuration. Then, the LPT Management dialog box is displayed. An
important message is displayed in the left lower corner of the dialog box.
Step 4 Click Create and the Create LPT dialog box is displayed.
Step 5 In the Convergence Point and Access Point group boxes, set the P2MP LPT parameters
according to the actual requirements. For the parameters of the P2MP LPT, refer to Table 9-2.
Step 6 Click OK. A dialog box is displayed, indicating that the operation is successful.
Step 7 Refer to Steps 1–6 to set the P2MP LPT of the opposite NE.
----End
Parameters
For the P2MP LPT parameters, refer to Table 9-2.

Table 9-2 Parameters for the P2MP LPT

Parameter Value Range Default Value
Converge Port For example, Indicates the port where the

nce Point PORT1 convergence point resides.
Bearer Mode GFP(HUAWEI), Indicates the bearer mode of the

Ethernet, GFP convergence port.
(CSF) This parameter can be set only when it
is supported by a board.
Hold Off Time 0–10000 If LPT switching is enabled, the port

(ms) notifies the opposite end after the hold-
off time.
Access Port For example, Indicates the port where the access
Point VCTRUNK1 point resides.
Bearer Mode GFP(HUAWEI), Indicates the bearer mode of the access

Ethernet, GFP port.
(CSF) This parameter can be set only when it
is supported by a board.

Configuration Guide 10 Configuring the PRBS
10 Configuring the PRBS
About This Chapter
This topic describes how to configure the pseudo-random binary sequence (PRBS) test on the
T2000.
10.1 Overview
Certain boards of the OptiX OSN 2000 provide the PRBS functional module, which is used for
network self-test and maintenance. Depending on whether bit errors are detected in a PRBS test,
you can determine whether the tributary port and the working path in the cross-connect direction
work normally.
10.2 Application
The OptiX OSN 2000 supports the lower order PRBS test in the tributary direction.
10.3 Lower Order PRBS Function
This topic describes how to configure the PRBS test in the tributary direction on the T2000,
which is triggered by the tributary board. Hardware loopback related to the electrical ports of
the tributary board is considered as an example.

10 Configuring the PRBS Configuration Guide
10.1 Overview
Certain boards of the OptiX OSN 2000 provide the PRBS functional module, which is used for
network self-test and maintenance. Depending on whether bit errors are detected in a PRBS test,
you can determine whether the tributary port and the working path in the cross-connect direction
work normally.
10.1.1 PRBS Function
An NE that provides the PRBS function can be used as a simple tester. According to the bit
errors detected by this tester, you can determine whether the service path is faulty, and locate
the faults to a fiber or the relevant board between NEs. By using the PRBS function, you can
analyze the local NE and the entire network. Therefore, to carry out deployment or locate
problems, you can perform a test without using a real tester.
10.1.2 Boards with the PRBS Function
The PL1, PT1, PLM, PQ1, PL3, and PD3 boards on the OptiX OSN 2000 support the PRBS test
function.
10.1.1 PRBS Function

An NE that provides the PRBS function can be used as a simple tester. According to the bit
errors detected by this tester, you can determine whether the service path is faulty, and locate
the faults to a fiber or the relevant board between NEs. By using the PRBS function, you can
analyze the local NE and the entire network. Therefore, to carry out deployment or locate
problems, you can perform a test without using a real tester.
The PRBS functional module is equivalent to a simple meter that by itself transmits and receives
unframed services.
l In the case of the E1, T1, and T3 services, the PRBS15 is transmitted.
l In the case of the E3 services, the PRBS23 is transmitted.
10.1.2 Boards with the PRBS Function

The PL1, PT1, PLM, PQ1, PL3, and PD3 boards on the OptiX OSN 2000 support the PRBS test
function.
10.2 Application
The OptiX OSN 2000 supports the lower order PRBS test in the tributary direction.
Figure 10-1 shows the signal flow for the lower order PRBS test.

Figure 10-1 Signal flow for the lower order PRBS test
RX TX
(1) PRBS (2) (2)

module
TX RX
Tributary board Cross-connect Line board

board
(1) PRBS test loop in the tributary direction
(2) PRBS test loop in the cross-connect direction
The lower order PRBS test in the tributary direction is used to check whether the tested tributary
port works properly. In the transmit port (Tx) direction of this tributary, the board transmits fixed
PRBS. In the receive port (Rx) direction of this tributary, the board receives the PRBS. See
Figure 10-2. When you perform a PRBS test in the tributary direction, note the following:
l You must use a cable to loopback the tested tributary port.
l When you perform a PRBS test for the PDH boards in the tributary direction, you need to
configure the VC-12/VC-3 cross-connection for the tested tributary port.
Figure 10-2 Lower order PRBS test in the tributary direction
TX
PRBS generator
Cable
RX
PRBS receiver
Tributary
board
10.3 Lower Order PRBS Function

This topic describes how to configure the PRBS test in the tributary direction on the T2000,
which is triggered by the tributary board. Hardware loopback related to the electrical ports of
the tributary board is considered as an example.
Prerequisite
l The E1 cable must be used to perform loopback at the first port on the T76S board in slot
1.

10 Configuring the PRBS Configuration Guide
Precautions
CAUTION
When you set a loopback, make sure that no active service is running on the optical port or path
to be loopbacked. Otherwise, the service is interrupted.
Procedure
Step 1 Create and activate a VC-12 service from tributary port 1 of the 4-PT1 to timeslot 1 in the first
VC-4 path of optical port 1 on the 27-OSB4A. For details, see 2 Configuring SDH/PDH
Services.
Step 2 In the Object Tree, select the 4-PT1 board, and then choose Configuration > PRBS Test from
the Function Tree.
Step 3 Select the SDH_TU-1 port, and then set the following parameters in the Set Test Parameters
area. Refer to Table 10-1 for the parameter description of the PRBS test configuration.
l Direction: Tributary
l Duration: 10
l Measured in Time: s
Step 4 Click Start to Test. In the confirmation dialog box, click OK.
Step 5 When the Progress field is displayed as 100%, check the value in the Total PRBS field.
l If the value is 0, it indicates that no bit errors are detected in the test. The tested loop is normal.
l If the value is not 0, the value indicates the number of bit errors detected in the test. In this
case, you need to analyze the causes of bit errors and perform the troubleshooting.
NOTE
If the cable is not loopbacked during the tributary test, the board reports a number of 0xFFFFFFFF bit
errors.
----End

Parameters
Table 10-1 Parameters of lower order PRBS configuration

Port - - Indicates the port where the PRBS

test is performed.
Direction Cross, Tributary Cross l Cross: The PRBS is inserted into

the cross-connect side.
l Tributary: The PRBS is inserted
into the tributary side.
Duration 1–255 1 Specifies the test duration.
Measured in s, 10m, h s Specifies the measurement unit of

Time the test duration.
Total PRBS - 0 Indicates the total number of

PRBSs.

Configuration Guide 11 Configuring the Ethernet Test Frame
11 Configuring the Ethernet Test Frame
About This Chapter
The test frames are data packets used to test the continuity of the SDH-side network that carries
Ethernet services. The test frames are mainly used for commissioning Ethernet services in the
case of deployment or for locating faults in the Ethernet services. The test frame function is
compliant with the Huawei internal protocol standard, and can be transmitted and received only
between VCTRUNK ports.
11.1 Overview
This topic describes the basic concepts related to the test frame.
11.2 Application
When you commission the Ethernet service during the deployment or locate a fault in the
Ethernet service, you can send test frames to test the connectivity of the SDH link in the service
network.
11.3 Configuring the Ethernet Test Frame
You can configure the parameters (such as send mode and send direction of VCTRUNK1 port)
that are used to initiate the Ethernet test. According to the test result, you know whether the
Ethernet services run normally.

11 Configuring the Ethernet Test Frame Configuration Guide
11.1 Overview
This topic describes the basic concepts related to the test frame.
The bearer mode indicates the encapsulation format of the test frame. Different bearer modes
correspond to different test frames. If the encapsulation format of the received test frame is
inconsistent with the bearer mode of the receive end, the test frame is discarded without being
processed. The Ethernet boards support two bearer modes: Ethernet and GFP.
l The packet in the Ethernet bearer mode is of Ethernet packet format. The packet that is
constructed by the CPU is issued to the same path as the normal Ethernet packet.
l The packet in the GFP bearer mode is of GFP management frame format. The packet is
issued to the same path as the GFP management frame.
If the bearing mode of a VCTRUNK port is the Ethernet bearer mode but the received test frame
is of GFP format, the test frame is not processed.
11.2 Application
When you commission the Ethernet service during the deployment or locate a fault in the
Ethernet service, you can send test frames to test the connectivity of the SDH link in the service
network.
The bandwidth used for transmitting the test frames is little and thus can be ignored. The
transmission mode and quantity of the test frames to be transmitted can be set.
As shown in Figure 11-1, when the Ethernet service between Router 1 and Router 2 is
unavailable, you can locate a fault in the Ethernet service by sending test frames between
neighboring nodes. The process of the test frame transmission is as follows:
1. The VCTRUNK port on the data board of NE1 sends the test frame to the VCTRUNK port
on the data board of NE2.
2. NE2 sends the response packet to NE1, after receiving the test frame.
3. NE1 calculates the received and transmitted test frame packets. The client determines
whether the service network is normal according to the number of the transmitted and
received packets.
l In the case of a bidirectional service, the service network is considered normal if the
transmit end of the test frame received the response packet.
l In the case of a unidirectional service, the service network is considered normal if the
receive end of the test frame received the test frame.

Configuration Guide 11 Configuring the Ethernet Test Frame
Figure 11-1 Application of the test frame
Access network Service network Access network
Test frame
NE1 Response frame

NE2
MAC VCTRUNK VCTRUNK MAC
Router 1 Board Board Router 2
OptiX NE
Router
11.3 Configuring the Ethernet Test Frame

You can configure the parameters (such as send mode and send direction of VCTRUNK1 port)
that are used to initiate the Ethernet test. According to the test result, you know whether the
Ethernet services run normally.
Prerequisite
l The Ethernet data board supports the test frame function.
l The Ethernet services must be successfully created.
There are three transmitting modes: Continue, Burst, and Disabled.
l In the Continue mode, the test frames are transmitted continuously. One test frame is
transmitted at intervals of about one second.
l In the Burst mode, the frames to send can be set. The transmission is at intervals of about
one second.
l In the Disabled mode, transmission of test frames is stopped.
The two interconnected ends support the same bearing mode.
Procedure

11 Configuring the Ethernet Test Frame Configuration Guide
Step 2 Select the relevant Ethernet data board, and then choose Configuration > Ethernet
Maintenance > Ethernet Test from the Function Tree.
Step 3 Configure the VCTRUNK port that initiates the Ethernet test. For the parameters of the test
frame, see Table 11-1.
l Send Mode: Burst
l Send Direction: SDH Direction
l Frames to Send: 20
Step 4 Click Apply. A dialog box is displayed indicating that the operation is successful.
Step 5
----End
Parameters
Table 11-1 Parameters of the test frame

Send Mode Continue, Burst, Disabled l In the Continue mode, the test
Disabled frames are transmitted
continuously. One test frame is
transmitted at intervals of about
one second.
l In the Burst mode, the frames to
send can be set. The transmission
is at intervals of about one
second.
l In the Disabled mode,
transmission of test frames is
stopped.
Send Direction SDH Direction SDH Direction Indicates the direction for sending
the frames.
Frames to Send 1–255 / To set this parameter, set Send

Mode to Burst Mode.
Specifies the frames to send for test.

Configuration Guide 12 Configuring the LCAS
12 Configuring the LCAS
About This Chapter
The link capacity adjustment scheme (LCAS) is a technology that is applied to virtual
concatenation and enhances the performance of virtual concatenation. It can dynamically adjust
the number of virtual containers that map the required services to meet the requirements of
various service bandwidths. As a result, the bandwidth utilization is elevated, and the Ethernet
services are protected.
12.1 Overview
The LCAS is supplementary to the virtual concatenation technology. The LCAS dynamically
adjusts the number of virtual containers required for service mapping to meet the requirements
of various service bandwidths. This elevates the bandwidth utilization and enhances the
robustness of virtual concatenation.
12.2 Application
The LCAS function can be used to dynamically adjust the bandwidth and protect virtual
concatenated services, thus improving the robustness and flexibility of the network.
12.3 Configuring the LCAS
By referring to this configuration process, you can configure the LCAS function and its relevant
parameters on the T2000.

12 Configuring the LCAS Configuration Guide
12.1 Overview
The LCAS is supplementary to the virtual concatenation technology. The LCAS dynamically
adjusts the number of virtual containers required for service mapping to meet the requirements
of various service bandwidths. This elevates the bandwidth utilization and enhances the
robustness of virtual concatenation.
The LCAS applies to only the virtually concatenated paths.
When the LCAS function is used in the network, the following advantages are available:
l The availability of the original services is not affected when the service bandwidth is
dynamically adjusted (added or deleted).
l If failed physical paths exist in the virtual concatenation, the LCAS function can suppress
the failed paths. In this case, the other paths can still transmit the services normally, thus
preventing service interruption due to failure of certain physical paths. After the failed
physical paths are restored, they can be used to transport services again.
The the LCAS complies with ITUT G.806 and ITUT G.7042/Y.1305(2005).
12.2 Application
The LCAS function can be used to dynamically adjust the bandwidth and protect virtual
concatenated services, thus improving the robustness and flexibility of the network.
Dynamic Bandwidth Adjustment

If the bandwidth of a certain VCTRUNK is improper, the bandwidth needs to be increased or
decreased. During bandwidth adjustment in the traditional mode, services are interrupted. During
bandwidth adjustment by using the LCAS function, only the number of VCTRUNK members
needs to be increased or decreased, thus to smoothly switch the bandwidth without interrupting
the services.
As shown in Figure 12-1, the LCAS can add members to increase the bandwidth dynamically,
without interrupting the services. The LCAS can also delete members to dynamically decrease
the bandwidth.

Figure 12-1 Dynamic bandwidth adjustment by using the LCAS

MSTP network
Member
Member Headquarters
Branch
Add a 10 Mbit/s bandwidth
Member
Member
Branch Headquarters
New 10 Mbit/s member
Original New
OptiX NE
member member
Protection of Virtual Concatenated Services

As shown in Figure 12-2, the LCAS can be used to protect Ethernet services. When certain
members fail, the LCAS automatically suppress them; the other members still normally transport
data. This prevents the entire virtual concatenation group from becoming unavailable. When the
failed members become available again, they are automatically restored, and the data is reloaded
to them.
Figure 12-2 Virtual concatenation group protection realized by using the LCAS
MSTP network
Member
Member Headquarters
Branch
Failed member
Member
Member Headquarters
Branch Delete the failed memeber
Original Failed
OptiX NE
member member

As shown in the preceding figure, assume that in the normal state, a VCTRUNK maps three
VC-12 virtual concatenations and the bandwidth of the services is 6 Mbit/s. When one channel
in VC12-3v fails, the LCAS suppresses this failed member and adjusts the capacity of the
VCTRUNK. In this case, the bit rate of the services decreases and the system reports an alarm
to inform the loss of partial bandwidth. The services of the entire VCTRUNK, however, are not
interrupted.
After the failed member is restored, the LCAS reuses the restored member to transport data and
the bandwidth of the services is restored to 6 Mbit/s.
12.3 Configuring the LCAS

By referring to this configuration process, you can configure the LCAS function and its relevant
parameters on the T2000.
Prerequisite
l The Ethernet data boards must support the LCAS function.
l The Ethernet services must be successfully created.
l You must be a T2000 user with "NE or network operator" authority or higher.
l The configuration that complies with the LCAS protocol should meet the following two
requirements:
– The configured services should be bidirectional services that adopt virtual
concatenation.
– The networking topology should be of the point-to-point mode.
l When configuring the LCAS function, you must set the same LCAS parameters to the same
values for the equipment at both ends.
– The LCAS enable/disable attribute of the equipment at both ends must be the same.
– The equipment at both ends must be set to the same LCAS mode.
Procedure
Management > Ethernet Interface from the Function Tree.
Step 3 Select Internal Port. Set the parameters of VCTRUNK ports in the LCAS tab. For the LCAS
parameters, refer to Table 12-1.

NOTE
The screen shot is. For reference only. In the case of different boards, the parameters are different, and the
information displayed on the T2000 may also be different.
Step 4 Click Apply. A dialog box is displayed, indicating that the operation is successful.
----End
Parameters
Table 12-1 LCAS parameters

Port VCTRUNKn - Indicates the VCTRUNK port.

Letter "n" indicates the number of
the VCTRUNK port.
Enabling LCAS Enabled, Disabled Specifies whether to enable the

Disabled LCAS function.
LCAS Mode Huawei Mode, Huawei Mode To use the LCAS function, you
Standard Mode must set the equipment at both ends
to the same LCAS mode.
l If the equipment at both ends is
Huawei equipment, set LCAS
Mode. For the equipment at both
ends to Huawei Mode.
l If Huawei equipment is
interconnected with the third-
party equipment, set LCAS
Mode for the equipment at both
ends to Standard Mode.
l If Huawei equipment is
interconnected with the third-
party equipment that does not
support the standard mode, set
LCAS Mode for the equipment
at both ends to Huawei Mode.
HO Time (ms) 0 or an integer in 2000 If the timeslot is unavailable,

the range from suppress the timeslot after the hold
2000 to 10000, off time expires. If the timeslot is
with a step of available again within the hold off
100 time, LCAS does not suppress the
timeslot that is unavailable.
You need to set the hold off time to
the default value, unless otherwise
specified. The parameters must be
set to the same values. For the
equipment at both ends.

WTR Time(s) 0–720 300 The WTR time refers to the time for
the timeslot to wait. For being added
to the virtual concatenation group
after the timeslot suppressed by the
LCAS is restored to normal.
You need to set the WTR time to the
default value, unless otherwise
specified. The parameters must be
set to the same values for the
equipment at both ends.
TSD Enabled, Disabled Specifies whether to use the trail

Disabled signal degrade (TSD) as the
condition for LCAS switching.
The TSD trigger condition is
BIP_SD for VC-12 paths, and is
B3_SD for VC-3/VC-4 paths.

Configuration Guide 13 Configuring Transmux
13 Configuring Transmux
About This Chapter
This topic uses an example to describe how to configure the Transmux feature on the T2000.
13.1 Overview
Currently, the E13/M13 functions are the core of the Transmux/Transmux Server feature that
the OptiX OSN 2000 supports.
13.2 Functions and Features
This topic describes the functions and features of the Transmux and Transmux Server.
13.3 Application
This topic considers the E1 signal as an example to describe the scenario where the Transmux
feature is used.
13.4 Configuring the Working Mode of a Board
This topic uses an example to describe how to configure the working mode of a board.
13.5 Configuring the Transmux Mode
This topic considers the E1 service as an example to describe how to configure the Transmux
mode.
13.6 Configuring the Transmux Server Mode
Server mode.

13 Configuring Transmux Configuration Guide
13.1 Overview
Currently, the E13/M13 functions are the core of the Transmux/Transmux Server feature that
the OptiX OSN 2000 supports.
The PLM board on the OptiX OSN 2000 supports the E13/M13 function. The E13/M13 functions
are performed inside the SDH equipment. The E13/M13 functions are as follows:
l Multiplexing 16xE1 signals to 1xE3 signals or demultiplexing 1xE3 signals to 16xE1
signals
l Multiplexing 16xT1 signals to 1xT3 signals or demultiplexing 1xT3 signals to 16xT1
signals
13.2 Functions and Features

This topic describes the functions and features of the Transmux and Transmux Server.
There are two application modes for the E13/M13 function: Transmux and Transmux Server.
l Transmux
– The NE first aggregates the accessed E1/T1 signals and then multiplexes the E1/T1
signals to form E3/T3 signals by using the E13/M13 function.
– The NE interconnects the E3/T3 services with other transmission equipment by using
the SDH line.
l Transmux Server
– The remote NE transmits the E1/T1 services at the VC-12 granularity to the central NE
over the SDH line.
– The central NE demaps the E1/T1 services from the VC-12s. Then, it aggregates the
E1/T1 signals and multiplexes the E1/T1 signals to form E3/T3 signals by using the
E13/M13 function.
– The central NE interconnects the E3/T3 services with other transmission equipment by
using the SDH line.
The PLM board can work in the following three modes: normal mode, Transmux mode, and
Transmux Server mode. Refer to Table 13-1.
Table 13-1 Working mode of the PLM

Working Board External E1 First VC-4 of Second VC-4
Mode Function Electrical Port the Internal of the Internal
Port Port
Normal mode The E13/M13 Timeslots 1–16 Unavailable Unavailable

function is are unavailable.
unavailable.

Working Board External E1 First VC-4 of Second VC-4

Mode Function Electrical Port the Internal of the Internal
Port Port
Transmux mode Converges the Timeslots 1–16 Unavailable Timeslot 1 is

accessed E1/T1 are unavailable. available and
services on the can be
external configured with
electrical port E3/T3 services
into the E3/T3 at the VC-3
services on the granularity.
internal port and
deconverges the
E3/T3 services
on the internal
port into the E1/
T1 services on
the external
electrical port.
Transmux Converges the Unavailable Timeslots 1–16 Timeslot 1 is

Server mode accessed E1/T1 are available and available and
services on the can be can be
internal port into configured with configured with
the E3/T3 E1/T1 services E3/T3 services
services on the at the VC-12 at the VC-3
internal port and granularity. granularity.
deconverges the
E3/T3 services
on the internal
port into the E1/
T1 services on
the internal port.
CAUTION
This topic introduces only The general approach of configuring the Transmux feature on a single
NE. The configuration method used on site must be based on the actual application scenario.
Many configuration activities are involved in a successful service configuration. For details, see
2 Configuring SDH/PDH Services.
13.3 Application
This topic considers the E1 signal as an example to describe the scenario where the Transmux
feature is used.

E1 Transmux
The user equipment transmits the E1 services at the VC-12 granularity to the central NE over
the PDH line. The central NE multiplexes the E1 signals into E3 signals. The E3 signals are
transmitted to the local NE. The local NE transmits the E3 signals to the local user equipment
through the electrical ports.
Figure 13-1 shows the E1 Transmux mode.
Figure 13-1 E1 Transmux

User equipment 1
E3 service
E1 service
E3
service E1 service
User
E1 service equipment 2
Local user Local NE Central NE
equipment
User equipment 3
E1 Transmux Server
The remote NE transmits the E1 services at the VC-12 granularity to the central NE over the
SDH line. The central NE multiplexes the E1 signals into E3 signals. The E3 signals are output
to other transmission equipment over the SDH line.
Figure 13-2 shows the E1 Transmux Server mode.
Figure 13-2 E1 Transmux Server

Remote NE1
E3 service
E1 service
E1 service
E1 service
Central NE Remote NE2
Other transmission
equipment
Remote NE3

13.4 Configuring the Working Mode of a Board

This topic uses an example to describe how to configure the working mode of a board.
Prerequisite
l The board must be configured.
l You must be an NM user with "NE or network operator" authority or higher.
Precautions
NOTE
The following parameters are provided as examples only. In actual application, configure the parameters
Procedure
Step 1 Right-click the NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Select the PLM from the Object Tree and choose Configuration > PDH Interface from the
Function Tree.
Step 3 Click By Board/Port(Path) and choose Board from the drop-down list.
Step 4 Select the required mode from the Service Mode drop-down list according to the actual situation.
Table 13-2 lists the parameters required for configuring the service mode.
----End

Parameters
Table 13-2 Parameters for configuring the service mode

Service Mode Normal Mode - l Normal mode: The board

MUX Mode supports the configuration of
PDH ports, but does not provide
Server Mode the Transmux function.
l MUX mode: The board supports
the configuration of SDH and
PDH ports, and thus converges
the accessed E1/T1 services on
the external electrical port into
the E3/T3 services on the internal
port and deconverges the E3/T3
services on the internal port into
the E1/T1 services on the
external electrical port.
l Server mode: The board supports
the configuration of SDH ports,
and thus converges the accessed
E1/T1 services on the internal
port into the E3/T3 services on
the internal port and deconverges
the E3/T3 services on the internal
port into the E1/T1 services on
the internal port.
13.5 Configuring the Transmux Mode

mode.
Prerequisite
When the PLM works in the MUX mode, external electrical ports 1–16 are available. The PLM
board also supports an internal port numbered 17. In this case, however, only the second VC-4
of internal port 17 is available. The PLM board implements the convergence from the E1 service
into the E3 service and deconvergence from the E3 service into the E1 service. For the MUX
working mode, refer to Table 13-3.

Table 13-3 PLM in the MUX mode
E1 Service E3 Service
Port Number VC-4 Number Timeslot
External electrical 17 (internal port) 2 1

ports 1–16
In the Transmux mode, the PLM automatically implements the convergence from the E1/T1
service accessed from the external electrical port into the E3/T3 service on the internal port and
deconvergence from the E3/T3 service on the internal port into the E1/T1 service on the external
electrical port. Hence, the corresponding action need not be configured. The services from the
internal port of the PLM board to a line board or an E3/T3 tributary board need to be configured.
For example, when NE1 needs to be configured with the services as required in Table 13-4, you
can use the MUX mode of the board to implement the service requirement.
Table 13-4 Service requirements in the MUX mode
Serial Service Service Level Remarks

Number Access Access
Slot Timeslot/
Path
1 9-PLM 1–16 VC-12 Indicates the E1 services that are

accessed at the local end. The actual
services are accessed through the
interface board.
2 10-SL4 VC4:1:1 VC-3 Indicates the E3 services from NE2.
Procedure
Step 2 Select NE1 and choose Configuration > SDH Service Configuration from the Function Tree.
Click .
Step 3 Create the VC-3 services from the internal port of the PLM board to a line board: from the first
VC-3 of the second VC-4 of the PLM board in slot 9 to the first VC-3 of the first VC-4 of the
SL4 in slot 10. Click Create. Set the following parameters in the Create SDH Service dialog
box:
l Level: VC-3
l Source Slot: 9-PLM-17
l Source VC4: VC4-2
l Sink Slot: 10-SL4-1

l Sink VC4: VC4-1.

Step 4 Click OK.
----End
13.6 Configuring the Transmux Server Mode

Server mode.
Prerequisite
When the PLM works in the Transmux Server mode, all the external electrical ports are
unavailable. In this case, the PLM supports internal port 17. The first and second VC-4s of
internal port 17 are available. The first VC-4 can be configured with 16xVC-12 services and the
second VC-4 can be configured with 1xVC-3 services. The PLM implements the convergence
from the E1 service into the E3 service and deconvergence from the E3 service into the E1
service. For the Transmux Server mode, refer to Table 13-5.
Table 13-5 PLM in the Transmux Server mode

E1 Service E3 Service
Port VC-4 Timeslot Port VC-4 Timeslot

Number Number Number Number
17 (internal 1 1–16 17 (internal 2 1

port) port)
In the Transmux Server mode, the PLM board automatically implements the convergence from
the VC-12s in the first VC-4 of the internal port into the VC-3s in the second VC-4 of the internal
port and the deconvergence from the VC-3s in the second VC-4 of the internal port into the
VC-12s in the first VC-4 of the internal port. Hence, the corresponding action need not be
configured. The services that need to be configured are as follows:
l E1 services from the VC-12s of the first VC-4 of the internal port to a line board or a
tributary board
l E3 services from the VC-12s of the second VC-4 of the internal port to a line board or a
tributary board
For example, when an NE needs to be configured with the services as required in Table 13-6,
you can use the Transmux Server mode of the board to implement the service requirement.

Figure 13-3 Networking diagram in the Transmux Server mode

NE2
28-OSB4A
E3 service
E1 service
9-PLM
10-SL4
NE1 E1 service
NE4
27-OSB4A
NE3
Table 13-6 Service requirements in the Transmux Server mode

Serial Service Service Level Remarks
Number Access Access
Slot Timeslot/
Path
1 28- VC4:1:1-8 VC-12 Indicates the E1 services from NE2.

OSB4A
2 27- VC4:1:9-1 VC-12 Indicates the E1 services from NE3.

OSB4A 6
3 10-SL4 VC4:1:1 VC-3 Indicates the E3 services from NE4.
To meet the previous requirements, three services must be configured, as listed in Table 13-7.
Table 13-7 Services configured in the Transmux Server mode

Serial Level Source Sink
Numbe
r Port VC-4 Timesl Port VC-4 Timesl
Numbe Numbe ot Numbe Numbe ot
r r r r
1 VC-12 28- 1 1-8 9- 1 1-8

OSB4A- PLM-17
1
2 VC-12 27- 1 9-16 9- 1 9-16

OSB4A- PLM-17
1
3 VC-3 10- 1 1 9- 2 1
SL4-1 PLM-17

Procedure
Step 2 Select NE1 and choose Configuration > SDH Service Configuration from the Function Tree.
Click .
Step 3 Create service 1 according to Table 13-7. Click Create and set the following parameters in the
l Level: VC12
l Source Slot: 28-OSB4A-1
l Source VC4: VC4-1
l Sink VC4: VC4-1
l Level: VC12
l Source Slot: 27-OSB4A-1
l Source VC4: VC4-1
l Sink VC4: VC4-1
l Level: VC-3
l Source VC4: VC4-2
l Sink Slot: 10-SL4-1
l Sink VC4: VC4-1.
----End

Configuration Guide A Glossary
A Glossary
Numerics
1+1 A 1+1 protection architecture has one normal traffic signal, one working SNC/
protection trail, one protection SNC/trail and a permanent bridge.
A
ADM Add/Drop Multiplexing. Network elements that provide access to all or certain
subset of the constituent signals contained within an STM-N signal. The
constituent signals are added to (inserted), and/or dropped from (extracted) the
STM-N signal as it passed through the ADM.
ALS Automatic Laser Shutdown. A technique (procedure) to automatically
shutdown the output power of laser transmitters and optical amplifier to avoid
exposure to hazardous levels.
Auto- The rate/work mode of the communication party set as self-negotiation is
negotiation specified through negotiation according to the transmission rate of the opposite
party.
B
Back up Copy the important data into a backing storage in case that the original is
damaged or corrupted.
BITS Building Integrated Timing Supply. A building timing supply that minimizes
the number of synchronization links entering an office. Sometimes referred to
as a synchronization supply unit.
Bound The VC Trunk refers to the 2 Mbps paths which are bound together to transmit
path Ethernet data. The VC Trunk is an entity between the Ethernet port and the 2
Mbps path.
Issue 02 (2008-10-15) Huawei Proprietary and Confidential A-1

A Glossary Configuration Guide
ECC Embedded Control Channel. An ECC provides a logical operations channel

between SDH NEs, utilizing a data communications channel (DCC) as its
physical layer.
EPL Ethernet Private LiNE. An EPL service is a point-to-point interconnection
between two UNIs without SDH bandwidth sharing. Transport bandwidth is
never shared between different customers.
EPLAN Ethernet Private LAN. An EPLAN service is both a LAN service and a private
service. Transport bandwidth is never shared between different customers.
EVPL Ethernet Virtual Private Line. An EVPL service is a service that is both a line
service and a virtual private service.
EVPLAN Ethernet Virtual Private Local Area Network. An EVPLAN service is a service
that is both a LAN service and a virtual private service.
Ethernet A data link level protocol comprising the OSI model's bottom two layers. It is
a broadcast networking technology that can use several different physical
media, including twisted pair cable and coaxial cable. Ethernet usually uses
CSMA/CD. TCP/IP is commonly used with Ethernet networks.
F
FEC Forward error correction, It is a kind of technology for enhancing the reliability
of digital transmission. It can increase transmission distance and improve
network performance.
G
Gateway IP address is used for TCP/IP communication between an NE and the T2000,
IP which is effective only when it is used for TCP/IP communication. That is, only
the gateway NE needs the IP address. IP address cannot be used to identify an
NE uniquely. NEs in different TCP/IP networks may have the same IP address.
And one NE may have several IP addresses (for example: an IP address of a
dial-up network, an IP address of the Ethernet port and so on).
L
LCAS Link Capacity Adjustment Scheme. A solution features flexible bandwidth and
dynamic adjustment. In addition, it provides a failure tolerance mechanism,
which enhances the viability of virtual concatenations and enables the dynamic
adjustment to bandwidth (non-service affecting).
Loopback The fault of each path on the optical fiber can be located by setting loopback
for each path of the line. There are three kinds of loopback modes: No loopback,
Outloop, Inloop.
A-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

MPLS Multiprotocol Label Switching. Multi-protocol label switching. It is a standard

routing and switching technology platform, capable of supporting various high
level protocols and services. The data transmission over an MPLS network is
independent of route calculating. MPLS, as a connection-oriented transmission
technology, guarantees QoS effectively, supports various network level
technologies, and is independent of the link layer.
MSTP Multi-service transmission platform. It is based on the SDH platform, capable
of accessing, processing and transmitting TDM services, ATM services, and
Ethernet services, and providing unified management of these services.
O
Orderwire It establishes the voice communication among the operators and maintenance
engineers work in each working station.
P
PDH Plesiochronous Digital Hierarchy. PDH is the digital networking hierarchy that
is used before the advent of SONET/SDH.
R
REG A device that performs regeneration.
RS232 In the asynchronous transfer mode and there is no hand-shaking signal. It can
communicate with RS232 and RS422 of other stations in point-to-point mode
and the transmission is transparent. Its highest speed is 19. 2kbit/s.
RS422 The interface can change to RS232 through the hardware jumper and others are
the same as RS232.
RSTP The Rapid Spanning Tree Protocol is an evolution of the Spanning Tree
Protocol, providing for faster spanning tree convergence after a topology
change.
S
SDH Synchronous Digital Hierarchy. A hierarchical set of digital transport
structures, standardized for the transport of suitably adapted payloads over
physical transmission networks.
SNCP SubNetwork Connection Protection. A working subnetwork connection is
replaced by a protection subnetwork connection if the working subnetwork
connection fails, or if its performance falls below a required level.

A Glossary Configuration Guide
SSM Synchronization Status Message. ITU-T defines S1 byte to transmit the

network synchronization status information. It uses the lower four bits of the
multiplex section overhead S1 byte to indicate 16 types of synchronization
quality grades.
STP STP is a protocol that provides a loop free topology for any bridged LAN and
is used in switched networks to prevent loops.
Subnet Also referred to as the network mask off code, it is used to define network
mask segments, so that only the computers in the same network segment can
communicate with one another, thus suppressing broadcast storm between
different network segments.
Subnet Sub-network is the logical entity in the transmission network and comprises a
group of network management objects. A sub-network can contain NEs and
other sub-networks. A sub-network planning can better the organization of a
network view.
Switching There may be the case that several protected boards need to be switched; thus
priority the tributary board switching priority should be set. If the switching priority of
each board is set the same, the tributary board that fails later cannot be switched.
The board with higher priority can preempt the switching of that with lower
priority.
T
TCP/IP Transmission Control Protocol/Internet Protocol. Common name for the suite
of protocols developed to support the construction of worldwide internet
networks.
TCM Tandem Connection Monitoring. In the SDH transport hierarchy, the TCM is
located between the AU/TU management layer and the HP/LP layer. The TCM
uses the N1/N2 byte of the lower order path (LP) overhead to monitor the
quality of the transport channels at a transmission section – TCM section.
Timeslot Single timeslot on an E1 digital interface—that is, a 64-kbps, synchronous, full-
duplex data channel, typically used. For a single voice connection.
TPS Tributary Protection Switching. A function provided by the equipment, is
intended to protect N tributary processing boards through a standby tributary
processing board.
Trail A network level management functions of the T2000. Through trail
manageme management, you can configure end-to-end services, view graphic interface
nt function and visual routes of a trail, query detailed information of a trail, filter, search
and locate a trail quickly, manage and maintain trails in a centralized manner,
manage alarms and performance data by trail, and print a trail report.
V
VLAN ID Namely, it is the virtual LAN identifier. One Ethernet port can support 4K
VLAN routes, and one NE can support up to 8K VLAN routes.
A-4 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

VLAN Virtual local area network. A subset of the active topology of a Bridged Local
Area Network. Associated with each VLAN is a VLAN Identifier (VID).
W
WTR time A period of time that must elapse before a – from a fault recovered – trail/
connection can be used again to transport the normal traffic signal and/or to
select the normal traffic signal from.
WTR Wait to Restore. This command is issued when working channels meet the
restoral threshold after an SD or SF condition. It is used to maintain the state
during the WTR period unless it is pre-empted by a higher priority bridge
request.

Configuration Guide B Acronyms and Abbreviations
B Acronyms and Abbreviations
A
ADM Add/Drop Multiplexer
APS Automatic Protection Switch
B
BITS Building Integrated Timing Supply
D
DCC Data Communication Channel
E
ECC Embedded Control Channel
EPL Ethernet Private Line
EPLAN Ethernet Private LAN
ETS European Telecommunication Standards
ETSI European Telecommunications Standards Institute
EVPL Ethernet Virtual Private Line
EVPLAN Ethernet Virtual Private LAN
G
GE Gigabit Ethernet
GFP Generic Framing Procedure
Issue 02 (2008-10-15) Huawei Proprietary and Confidential B-1

B Acronyms and Abbreviations Configuration Guide
H
HDLC High level Data Link Control;
IEEE Institute of Electrical and Electronics Engineers
I
ITU-T International Telecommunication Union -
Telecommunication Standardization Sector
L
LAPS Link Access Procedure-SDH
LCAS Link Capacity Adjustment Scheme
LCT Local Craft Terminal
M
MPLS Multi-Protocol Label Switch
MSP Multiplex Section Protection
N
NM Network Management
O
OAM Operation Administration and Maintenance
P
PDH Plesiochronous Digital Hierarchy
R
RSTP Rapid Spanning Tree Protocol
S
SNCP Sub-Network Connection Protection
SSM Synchronization Status Marker
STP Spanning Tree Protocol
B-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Configuration Guide B Acronyms and Abbreviations
T
TPS Tributary Protection Switching
V
VLAN Virtual Local Area Network
VPN Virtual Private Network
Issue 02 (2008-10-15) Huawei Proprietary and Confidential B-3

Configuration Guide Index
Index
Symbols/Numerics configuring the RS overhead J0, 2-45

configuring the signal flag byte C2, 2-47
1+1 linear MSP chain, 2-27 configuring the STP or RSTP, 7-1
802.1d bridge-based EPLAN service configuring the tracing byte J1, 2-46
configuration process(by station), 4-90 configuring transmux, 13-1
802.1q bridge-based EVPLAN service creating fiber, 2-24
configuration process(by station), 4-103 automatically, 2-25
configuration process(by trail), 4-115 manually, 2-24
A
alarm parameters setting, 2-52 D
DCN
B overview, 6-3
back up
NE configuration data, 2-54 E
T2000 configuration data, 2-55 EPL service
board creation transparent transmission configuration (by trail),
adding in the configuration wizard, 2-22 4-17
adding on the NE panel, 2-23 transparent transmission configuration(by station),
board,creating, 2-21 4-4
broadcast data service EPLAN service
configuration process, 5-3 802.1d bridge-based configuration(by station),
4-86
C ETH-OAM
activating the CC, 8-7
configuring broadcast data service, 5-2 configuration process, 8-5
configuring clock, 2-30 enabling the LB, 8-7
clock source priority, 2-30 overview, 8-3
subnet, 2-31 starting the LT, 8-8
configuring ETH-OAM, 8-1 Ethernet test frame
configuring F1 data service, 5-4 overview, 11-2
configuring HWECC communication, 6-6 EVPL service
configuring IP over DCC communication, 6-19 ingress/egress configuration(by station), 4-65
configuring STP or RSTP, 7-15 PORT shared configuration(by station), 4-26
configuring the DCN, 6-1 PORT shared configuration(by trail), 4-41
configuring the Ethernet test frame, 11-3 transit configuration(by station), 4-74
configuring the LCAS, 12-4 VCTRUNK-shared configuration(by station), 4-48
configuring the LPT, 9-1 VCTRUNK-shared configuration(by trail), 4-59
configuring the orderwire, 2-48 EVPLAN service
configuring the OSI over DCC communication, 6-26 802.1q bridge-based configuration(by station),
configuring the P2MP LPT function, 9-10 4-98
configuring the point-to-point LPT function, 9-8 802.1q bridge-based configuration(by trail), 4-109
configuring the PRBS, 10-1 MPLS-based configuration(by station), 4-117
Issue 02 (2008-10-15) Huawei Proprietary and Confidential i-1

Index Configuration Guide
F Q
F1 data service querying STP/RSTP running information, 7-18
configuration process, 5-5
S
I
SDH/PDH
Immediate Backup, 2-55 backing up NE data, 2-54
ingress/egress EVPL service backing up T2000 data, 2-55
configuration process(by station), 4-70 configuration process, 2-13
configuring alarm parameters, 2-52
L configuring orderwire, 2-48
configuring overhead byte, 2-45
LCAS configuring parameter, 2-45
overview, 12-2 configuring pass-through service, 2-39
logging in to an NE, 2-20 configuring performance event monitoring, 2-50
logging in to the T2000, 2-14 configuring VC-12 trail, 2-34
Lower Order PRBS Function, 10-3 configuring VC-4 server trail, 2-33
LPT SDH/PDH service configuration
overview, 9-2 per-NE configuration function, 2-36
trail management function, 2-32
M shutting down T2000
shutting down T2000 client, 1-5
MPLS-based EVPLAN service shutting down T2000 server, 1-6
configuration process, 4-123 starting T2000
MSP ring configuration, 2-27 logging in to T2000 client, 1-4
starting T2000 server, 1-3
N startingT2000
startingT2000computer, 1-3
NE creation STP or RSTP
gateway NE, 2-16 configuration process, 7-8
non-gateway NE, 2-16 overview, 7-2
NE user,creating, 2-18 system monitor, 1-4
O T
overhead byte configuration, 2-45 T2000 client
exiting, 1-5
P login, 1-4
T2000 main topology
performance monitoring setting, 2-50 main topology, 1-8
Periodic Backup, 2-56 T2000 main window
PORT shared EVPL service clock view, 1-8
configuration process(by station), 4-30 NE Explorer, 1-8
configuration process(by trail), 4-45 T2000 server
PRBS running status, 1-4
overview, 10-2 shutdown, 1-6
protection configuration starting, 1-3
1+1 linear MSP chain, 2-27 topology subnet, creating, 2-26
SNCP ring with 1 TPS protection, 2-28
1 linear MSP chains, 3-9 transit EVPL service
SNCP ring with non-protection chains, 3-4 configuration process(by station), 4-79
TPS protection, 2-28 transmux
two-fiber bidirectional MSP ring, 2-27 configuring board working mode, 13-5
protection,creating, 2-27 configuring the transmux mode, 13-6
configuring the transmux server mode, 13-8
overview, 13-2
i-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Configuration Guide Index
transparent transmission EPL service

configuration process(by station), 4-8
configuration process(by trail), 4-21
V
VCTRUNK-shared EVPL service
configuration process(by station), 4-52
configuration process(by trail), 4-63
Issue 02 (2008-10-15) Huawei Proprietary and Confidential i-3


00438451-Configuration Guide (V100R003 - 02) Jipe

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

00438451-Configuration Guide (V100R003 - 02) Jipe

Caricato da

Copyright:

Formati disponibili

OptiX OSN 2000 Enhanced STM-1/STM-4/STM-16 Multi-Service

Optical Transmission System

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

2 Configuring SDH/PDH Services.............................................................................................2-1

Issue 02 (2008-10-15) Huawei Proprietary and Confidential i

2.6.1 Creating a Gateway NE: NE1..............................................................................................................2-16

ii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

2.24.1 Immediate Backup..............................................................................................................................2-55

3 Configuring Services in Different Protection Schemes.....................................................3-1

4 Configuring Ethernet Services................................................................................................4-1

Issue 02 (2008-10-15) Huawei Proprietary and Confidential iii

4.5.3 Configuration Process..........................................................................................................................4-52

iv Huawei Proprietary and Confidential Issue 02 (2008-10-15)

4.11.5 Creating an EVPLAN Trail..............................................................................................................4-116

5 Configuring Auxiliary Services...............................................................................................5-1

6 Configuring the DCN................................................................................................................6-1

Issue 02 (2008-10-15) Huawei Proprietary and Confidential v

6.5.4 Allocating DCC Resources..................................................................................................................6-21

7 Configuring the STP or RSTP..................................................................................................7-1

vi Huawei Proprietary and Confidential Issue 02 (2008-10-15)

8.6 Enabling the LB..............................................................................................................................................8-7

9 Configuring the LPT..................................................................................................................9-1

10 Configuring the PRBS...........................................................................................................10-1

11 Configuring the Ethernet Test Frame.................................................................................11-1

12 Configuring the LCAS..........................................................................................................12-1

Issue 02 (2008-10-15) Huawei Proprietary and Confidential vii

Issue 02 (2008-10-15) Huawei Proprietary and Confidential ix

Figure 4-18 Board layout of NE3.......................................................................................................................4-44

x Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Figure 4-60 NE Service Configuration Diagram..............................................................................................4-120

Issue 02 (2008-10-15) Huawei Proprietary and Confidential xi

Table 2-1 Service requirements among the nodes................................................................................................2-4

Issue 02 (2008-10-15) Huawei Proprietary and Confidential xiii

Table 4-25 Process of configuring the transit EVPL service.............................................................................4-79

xiv Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Table 9-2 Parameters for the P2MP LPT........................................................................................................... 9-11

Issue 02 (2008-10-15) Huawei Proprietary and Confidential xv

About This Document

Product Name Version

OptiX OSN 2000 V100R003

OptiX iManager T2000 V200R007C01

l Data configuration engineers

Issue 02 (2008-10-15) Huawei Proprietary and Confidential 1

2 Configuring SDH/PDH Describes how to configure NEs, boards, cables/fibers,

3 Configuring Services in Describes the service configuration methods in various

4 Configuring Ethernet Describes how to configure EPL, EVPL, EPLAN, and

5 Configuring Auxiliary Describes how to configure broadcast data services and F1

6 Configuring the DCN Describes how to configure the data communication

8 Configuring ETH-OAM Describes how to configure the operation, administration,

10 Configuring the PRBS Describes how to configure the pseudorandom binary

13 Configuring Transmux Describes how to configure the Transmux feature on the

A Glossary Lists the terms used in this document.

2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

NOTE Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.