Toaz - Info Optix Osn 550 Configuration Guide v100r003 PR

OptiX OSN 550 Multi-Service CPE Optical
Transmission System
V100R003C00
Configuration Guide
Issue 02
Date 2011-06-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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 trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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 all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
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
Issue 02 (2011-06-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
OptiX OSN 550 Multi-Service CPE Optical Transmission
System
Configuration Guide About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 550 V100R003C00
iManager U2000 V100R005C00
Intended Audience
This document describes procedures for service configurations on the OptiX OSN 550, including
basic concepts, networking diagrams, signal flow and timeslot allocation of services.
This document is intended for:
l Data configuration engineer

l Installation and commissioning engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

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

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

avoided, could result in equipment damage, data loss,
CAUTION
performance degradation, or unexpected results.
Issue 02 (2011-06-30) Huawei Proprietary and Confidential iii

System
About This Document Configuration Guide
Symbol Description
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.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
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.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 02 (2011-06-30) Based on Product Version V100R003C00

This document is the second issue for product version V100R003C00. The updates in this issue
are described as follows:
l Related contents are updated based on the mapping NMS GUIs.
Changes in Issue 01 (2011-04-30) Based on Product Version V100R003C00

This document is the first issue for product version V100R003C00.
iv Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
Configuration Guide Contents
Contents
About This Document...................................................................................................................iii

1 Getting Started............................................................................................................................1-1
1.1 Starting or Shutting Down the U2000.............................................................................................................1-2
1.1.1 Starting the U2000 Server......................................................................................................................1-2
1.1.2 Logging In to the U2000 Client.............................................................................................................1-3
1.1.3 Exiting a U2000 Client...........................................................................................................................1-3
1.1.4 Shutting Down the U2000 Server..........................................................................................................1-3
1.2 Main Windows and Common Operations of the U2000.................................................................................1-4
1.2.1 Components of the Client GUI...............................................................................................................1-4
1.2.2 Key GUI Components............................................................................................................................1-6
1.2.3 Frequently Used Buttons........................................................................................................................1-7
1.2.4 Shortcut Icon..........................................................................................................................................1-9
1.2.5 Common Shortcut Keys.......................................................................................................................1-13
1.2.6 Main Windows.....................................................................................................................................1-14
1.2.6.1 Workbench........................................................................................................................................1-15
1.2.6.2 Main Topology..................................................................................................................................1-15
1.2.6.3 NE Explorer.......................................................................................................................................1-17
1.2.6.4 Clock View........................................................................................................................................1-18
1.2.6.5 NE Panel............................................................................................................................................1-19
1.2.6.6 Browse Alarm...................................................................................................................................1-19
1.2.6.7 Browse Event....................................................................................................................................1-19
1.2.6.8 Browse Performance Window..........................................................................................................1-20
2 Creating the Network................................................................................................................2-1

2.1 Creating NEs...................................................................................................................................................2-3
2.1.1 Creating a Single NE..............................................................................................................................2-3
2.1.2 Creating NEs in Batches........................................................................................................................2-5
2.2 Configuring the NE Data.................................................................................................................................2-6
2.2.1 Configuring the NE Data Manually.......................................................................................................2-6
2.2.2 Replicating the NE Data.........................................................................................................................2-8
2.2.3 Uploading the NE Data..........................................................................................................................2-8
2.3 Checking Board Parameters............................................................................................................................2-9
2.4 Creating Fibers..............................................................................................................................................2-11
Issue 02 (2011-06-30) Huawei Proprietary and Confidential v

System
Contents Configuration Guide
2.4.1 Creating Fibers Automatically.............................................................................................................2-11

2.4.2 Creating Fibers Manually.....................................................................................................................2-12
2.4.3 Creating Virtual Fibers.........................................................................................................................2-13
2.4.4 Creating DCN Communication Cable..................................................................................................2-13
2.5 Creating a Topology Subnet..........................................................................................................................2-14
2.6 Configuring the Protection Subnet................................................................................................................2-14
2.6.1 Configuring a Non-Protection Chain...................................................................................................2-15
2.6.2 Configuring a Non-Protection Ring.....................................................................................................2-16
2.6.3 Creating an MS Ring Protection Subnet..............................................................................................2-16
2.6.4 Creating a Linear MS Protection Subnet..............................................................................................2-19
2.7 Configuring Clocks.......................................................................................................................................2-21
2.7.1 Configuring the NE Clock Source.......................................................................................................2-21
2.7.2 Configuring the Clock Source Protection............................................................................................2-22
2.8 Clock Configuration Parameters...................................................................................................................2-23
2.8.1 Managing External Clock Sources.......................................................................................................2-23
2.8.2 Configuring Clock Protection and Restoration....................................................................................2-27
2.8.3 Clock Quality and Status Management................................................................................................2-30
2.8.4 Retiming Management.........................................................................................................................2-32
2.9 Configuring the Orderwire Phone.................................................................................................................2-33
2.9.1 Configuring the Orderwire...................................................................................................................2-33
2.9.2 Configuring the Conference Calls........................................................................................................2-34
2.10 Configuring the Broadcast Data Service.....................................................................................................2-36
2.11 Configuring the F1 Data Service.................................................................................................................2-37
2.12 Orderwire Configuration Parameters..........................................................................................................2-37
2.12.1 Configuring Orderwire Phones..........................................................................................................2-37
2.12.2 Configuring F1 Data Interfaces..........................................................................................................2-39
2.12.3 Configuring Broadcast Data Interfaces..............................................................................................2-40
3 Configuring SDH Services.......................................................................................................3-1

3.1 Basic Concepts................................................................................................................................................3-3
3.2 Configuring Services on the Non-Protection Chain........................................................................................3-4
3.2.1 Networking Diagram..............................................................................................................................3-4
3.2.2 Signal Flow and Timeslot Allocation.....................................................................................................3-5
3.2.3 Per-NE Configuration Procedure...........................................................................................................3-5
3.2.4 End-to-End Configuration Process.........................................................................................................3-7
3.3 Configuring Services on the Non-Protection Ring......................................................................................... 3-9
3.3.1 Networking Diagram..............................................................................................................................3-9
3.3.2 Signal Flow and Timeslot Allocation...................................................................................................3-10
3.3.3 Per-NE Configuration Process.............................................................................................................3-10
3.3.4 End-to-End Configuration Process.......................................................................................................3-13
3.4 Configuring 1+1 Linear MSP Services.........................................................................................................3-15
3.4.1 Networking Diagram............................................................................................................................3-15
vi Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System

3.5 Configuring 1:1 Linear MSP Services..........................................................................................................3-21
3.6 Configuring Two-Fiber Unidirectional MSP Services..................................................................................3-26
3.7 Configuring the Two-Fiber Bidirectional MSP Services..............................................................................3-37
3.8 Configuring Services on the SNCP Ring......................................................................................................3-44
3.9 Configuring Services on the SNCP Ring with a Non-Protection Chain.......................................................3-51
3.10 Configuring Service on the MSP Ring with a Non-Protection Chain.........................................................3-61
3.10.1 Networking Diagram..........................................................................................................................3-62
3.10.2 Signal Flow and Timeslot Allocation.................................................................................................3-63
3.10.3 Per-NE Configuration Process...........................................................................................................3-63
3.10.4 End-to-End Configuration Process.....................................................................................................3-66
3.11 Protection Configuration Parameters..........................................................................................................3-68
3.11.1 SNCP Configuration..........................................................................................................................3-68
3.11.2 Configuring the Multiplex Section Protection...................................................................................3-69
4 Configuring Ethernet Services................................................................................................4-1

4.1 Service Types..................................................................................................................................................4-3
4.2 Basic Concepts................................................................................................................................................4-7
4.2.1 Formats of Ethernet Frames...................................................................................................................4-8
4.2.2 Internal Ports and External Ports..........................................................................................................4-11
4.2.3 Auto-Negotiation..................................................................................................................................4-11
4.2.4 Flow Control........................................................................................................................................4-13
Issue 02 (2011-06-30) Huawei Proprietary and Confidential vii

System
4.2.5 Encapsulation and Mapping Protocol..................................................................................................4-14

4.2.6 Virtual Concatenation..........................................................................................................................4-15
4.2.7 Tag Attribute........................................................................................................................................4-17
4.2.8 Bridge...................................................................................................................................................4-19
4.3 Flow of Configuring Ethernet Services.........................................................................................................4-22
4.3.1 Flow of Configuring EPL Services......................................................................................................4-23
4.3.2 Flow of Configuring EVPL Services...................................................................................................4-25
4.3.3 Flow of Configuring EPLAN Services................................................................................................4-27
4.3.4 Flow of Configuring EVPLAN Services.............................................................................................4-30
4.4 Configuring EPL Services on an Ethernet Transparent Transmission Board...............................................4-33
4.4.3 Configuration Process..........................................................................................................................4-36
4.5 Configuring EPL Services on an Ethernet Switching Board........................................................................4-43
4.5.4 Configuration Process (End-to-End Mode)..........................................................................................4-56
4.6 Configuring PORT-Shared EVPL (VLAN) Services...................................................................................4-59
4.7 Configuring VCTRUNK-Shared EVPL (VLAN) Services..........................................................................4-72
4.8 Configuring EPLAN Services (IEEE 802.1d Bridge)...................................................................................4-83
4.9 Configuring EVPLAN Services (IEEE 802.1q Bridge)................................................................................4-96
4.9.3 Configuration Process........................................................................................................................4-101
4.10 Configuring EVPLAN Services (IEEE 802.1ad Bridge)..........................................................................4-115
4.10.1 Networking Diagram........................................................................................................................4-115
4.10.2 Signal Flow and Timeslot Allocation...............................................................................................4-117
4.10.3 Configuration Process......................................................................................................................4-119
4.11 Ethernet Port Configuration Parameters...................................................................................................4-130
4.11.1 Basic Attributes................................................................................................................................4-131
4.11.2 Flow Control....................................................................................................................................4-132
4.11.3 Network Attributes...........................................................................................................................4-133
viii Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
4.11.4 Advanced Attributes.........................................................................................................................4-134

4.11.5 TAG Attributes.................................................................................................................................4-137
4.11.6 Encapsulation/Mapping....................................................................................................................4-138
4.11.7 Bound Path.......................................................................................................................................4-139
4.12 Ethernet Service Configuration Parameters..............................................................................................4-140
4.12.1 Configuring Ethernet Private Line Services.....................................................................................4-140
4.12.2 Configuring Ethernet Private Network Services..............................................................................4-150
5 Modifying the Configuration Data.........................................................................................5-1

5.1 Changing the Values of NE Attributes............................................................................................................5-2
5.1.1 Changing the NE ID...............................................................................................................................5-2
5.1.2 Changing the NE Name..........................................................................................................................5-3
5.1.3 Deleting an NE.......................................................................................................................................5-3
5.1.4 Changing the Parameter Values of the Gateway NE............................................................................. 5-4
5.1.5 Changing the Gateway NE of a Non-Gateway NE................................................................................5-5
5.2 Modifying the Board Configuration Data.......................................................................................................5-6
5.2.1 Adding Boards........................................................................................................................................5-6
5.2.2 Deleting Boards......................................................................................................................................5-7
5.2.3 Modifying Board Configuration Parameters..........................................................................................5-7
5.3 Modifying the Fiber Configuration Data........................................................................................................ 5-8
5.3.1 Deleting Fibers.......................................................................................................................................5-8
5.3.2 Changing Fiber/Cable Information........................................................................................................ 5-8
5.3.3 Deleting DCN Communication Cables..................................................................................................5-9
5.4 Modifying the Service Configuration Data.....................................................................................................5-9
5.4.1 Modifying SDH Services.......................................................................................................................5-9
5.4.2 Deleting SDH Services.........................................................................................................................5-11
5.4.3 Deleting Ethernet Private Line Services..............................................................................................5-11
5.4.4 Deleting EPLAN Services....................................................................................................................5-12
5.4.5 Deleting EVPLAN Services.................................................................................................................5-13
5.5 Modifying the Protection Subnet..................................................................................................................5-13
5.5.1 Deleting Protection Subnets.................................................................................................................5-14
5.5.2 Changing the Values of Protection Subnet Parameters........................................................................5-14
6 Equipment Information............................................................................................................6-1
6.1 Service Support Capability of Ethernet Boards.............................................................................................. 6-2
6.2 Requirements for Binding Paths with VCTRUNKs on Ethernet Boards........................................................6-2
6.3 Ethernet Service Bandwidths Carried by VCTRUNKs of Ethernet Boards...................................................6-3
7 List of Parameters.......................................................................................................................7-1
7.1 Port Attributes (Ethernet Port)........................................................................................................................ 7-6
7.2 Maximum Frame Length (Ethernet Port Attribute)........................................................................................ 7-7
7.3 Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute)..............................................................7-8
7.4 Autonegotiation Flow Control Mode (Ethernet Port Attribute)......................................................................7-9
7.5 MAC Loopback (Ethernet Port Attribute)....................................................................................................7-10
Issue 02 (2011-06-30) Huawei Proprietary and Confidential ix

System
7.6 PHY Loopback (Ethernet Port Attribute)......................................................................................................7-10

7.7 QinQ Type Area............................................................................................................................................7-11
7.8 Loop Detection (Ethernet Port Attribute)......................................................................................................7-12
7.9 Loop Port Shutdown (Ethernet Port Attribute).............................................................................................7-13
7.10 Traffic Threshold(Mbit/s)(External Ethernet Port Attribute)......................................................................7-13
7.11 Broadcast Packet Suppression Threshold (Ethernet Interface Attributes)..................................................7-14
7.12 Broadcast Packet Suppression (Ethernet Interface Attributes)...................................................................7-15
7.13 Zero-Flow Monitor (Ethernet Interface Attributes)....................................................................................7-15
7.14 Port Traffic Threshold Time Window(Min)...............................................................................................7-16
7.15 Jumbo Frame Type......................................................................................................................................7-17
7.16 Default VLAN ID (Ethernet Port Attribute)...............................................................................................7-17
7.17 VLAN Priority (Ethernet Port Attribute)....................................................................................................7-18
7.18 Entry Detection (Ethernet Port Attribute)...................................................................................................7-19
7.19 TAG.............................................................................................................................................................7-19
7.20 Mapping Protocol........................................................................................................................................7-21
7.21 Scramble......................................................................................................................................................7-22
7.22 Set Inverse Value for CRC..........................................................................................................................7-23
7.23 Check Field Length.....................................................................................................................................7-24
7.24 FCS Calculated Bit Sequence.....................................................................................................................7-25
7.25 Operation Type (EPL Service)....................................................................................................................7-26
7.26 Service Type (EPL Service)........................................................................................................................7-28
7.27 Encapsulation Format of P Port (Network Attributes)................................................................................7-28
7.28 C-VLAN and S-VLAN...............................................................................................................................7-30
7.29 VLAN ID (For Creation of Ethernet Virtual Private Lines).......................................................................7-31
7.30 Bridge Learning Mode (Ethernet LAN Service).........................................................................................7-31
7.31 MEP ID (Ethernet OAM)............................................................................................................................7-32
7.32 Maintenance Point Type (Ethernet OAM)..................................................................................................7-33
7.33 CC Status (Ethernet OAM).........................................................................................................................7-34
7.34 Test Result (LB and LT Test).....................................................................................................................7-34
7.35 Responding MP Type (Ethernet LT Test)...................................................................................................7-35
7.36 Hop Count (Ethernet LT Test)....................................................................................................................7-35
7.37 Packet Length (Ping Test)...........................................................................................................................7-36
7.38 Timeout (Ping Test)....................................................................................................................................7-37
7.39 Detect Attempts...........................................................................................................................................7-37
7.40 Send Direction (Ethernet Test)....................................................................................................................7-38
7.41 Error Frame Monitor Window (ms)............................................................................................................7-39
7.42 Error Frame Monitor Threshold(Entries)....................................................................................................7-39
7.43 Error Frame Period Window(Frames).........................................................................................................7-40
7.44 Error Frame Monitor Threshold(Frames)...................................................................................................7-41
7.45 Error Frame Second Window (s)................................................................................................................7-42
7.46 Error Frame Second Threshold(s)...............................................................................................................7-42
7.47 Enable OAM Protocol.................................................................................................................................7-43
x Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
7.48 OAM Working Mode..................................................................................................................................7-43

7.49 Remote Alarm Support for Link Event.......................................................................................................7-44
7.50 Unidirectional Operation.............................................................................................................................7-45
7.51 Loopback Status (OAM Parameter)............................................................................................................7-46
7.52 Flow Type (Flow Configuration)................................................................................................................7-46
7.53 Bound CAR (Flow Configuration)..............................................................................................................7-47
7.54 Bound CoS (Flow Configuration)...............................................................................................................7-48
7.55 CAR ID (CAR Configuration)....................................................................................................................7-49
7.56 Enabled/Disabled (CAR Configuration).....................................................................................................7-49
7.57 Committed Information Rate (kbit/s) (CAR Configuration).......................................................................7-50
7.58 Committed Burst Size (kbyte) (CAR Configuration).................................................................................7-51
7.59 Peak Information Rate (kbit/s) (CAR Configuration).................................................................................7-51
7.60 Maximum Burst Size (kbyte) (CAR Configuration)...................................................................................7-52
7.61 CoS ID (CoS Configuration).......................................................................................................................7-53
7.62 CoS Type (CoS Configuration)...................................................................................................................7-53
7.63 CoS Priority (CoS Configuration)...............................................................................................................7-54
7.64 Port Priority (Link Aggregation).................................................................................................................7-56
7.65 System Priority (Link Aggregation)............................................................................................................7-56
7.66 Status (Link Aggregation)...........................................................................................................................7-57
7.67 Load Sharing(Ethernet Link Aggregation)..................................................................................................7-58
7.68 Protocol Enabled (Spanning Tree)..............................................................................................................7-59
7.69 Protocol Type (Spanning Tree Protocol)....................................................................................................7-59
7.70 Priority (Bridge Parameters).......................................................................................................................7-60
7.71 Max Age(s)..................................................................................................................................................7-61
7.72 Hello Time(s) (Spanning Tree)...................................................................................................................7-61
7.73 Forward Delay(s) (Spanning Tree).............................................................................................................7-62
7.74 TxHoldCount(per second) (Spanning Tree)................................................................................................7-63
7.75 Root Path Cost.............................................................................................................................................7-63
7.76 Hold Count (Spanning Tree).......................................................................................................................7-64
7.77 Port ID.........................................................................................................................................................7-64
7.78 Designated Path Cost..................................................................................................................................7-65
7.79 Designated Root Bridge Priority.................................................................................................................7-66
7.80 Designated Bridge Priority(Spanning Tree)................................................................................................7-67
7.81 Designated Bridge MAC Address (Spanning Tree)....................................................................................7-67
7.82 Edge Port Status (Spanning Tree)...............................................................................................................7-68
7.83 Point to Point Attributes(External Ethernet Port Attributes)......................................................................7-69
7.84 Enabling LCAS...........................................................................................................................................7-70
7.85 LCAS Mode................................................................................................................................................7-70
7.86 Hold-Off Time (ms) (LCAS)......................................................................................................................7-71
7.87 WTR Time (s) (LCAS)...............................................................................................................................7-72
7.88 TSD (LCAS)...............................................................................................................................................7-72
7.89 Min Members - Transmit Direction............................................................................................................7-73
Issue 02 (2011-06-30) Huawei Proprietary and Confidential xi

System
7.90 LPT..............................................................................................................................................................7-74
7.91 Bearer Mode................................................................................................................................................7-74
7.92 Port-Type Port Hold-Off Time (ms)...........................................................................................................7-75
7.93 VCTRUNK Port Hold-off Time (ms).........................................................................................................7-76
7.94 Protocol Enable (IGMP Snooping Protocol)...............................................................................................7-76
7.95 Multicast Aging Time(Min)........................................................................................................................7-77
7.96 Frames to Send............................................................................................................................................7-78
7.97 Status...........................................................................................................................................................7-78
7.98 Set Frame Count..........................................................................................................................................7-79
7.99 Received Response Test Frame Count........................................................................................................7-80
7.100 Test Frames to Receive.............................................................................................................................7-80
7.101 Send Mode (Ethernet Test).......................................................................................................................7-81
7.102 Call Waiting Time(s).................................................................................................................................7-82
7.103 Conference Call.........................................................................................................................................7-82
7.104 Phone.........................................................................................................................................................7-83
7.105 Available Orderwire Port..........................................................................................................................7-84
7.106 No.(F1 Data Port)......................................................................................................................................7-85
7.107 Data Channel (F1 Data Port).....................................................................................................................7-85
7.108 Overhead Byte (Broadcast Data Port).......................................................................................................7-86
7.109 Working Mode (Broadcast Data Port)......................................................................................................7-87
7.110 Broadcast Data Source (Broadcast Data Port)..........................................................................................7-88
7.111 Broadcast Data Sink (Broadcast Data Port)..............................................................................................7-88
7.112 External Clock Output Mode When 2M Output Synchronous Source Is Invalid.....................................7-89
7.113 External Clock Output Mode....................................................................................................................7-90
7.114 External Clock Output Timeslot...............................................................................................................7-91
7.115 External Source Output Threshold............................................................................................................7-92
7.116 2M Phase-Locked Source Fail Condition.................................................................................................7-94
7.117 2M Phase-Locked Source Fail Action......................................................................................................7-95
7.118 Clock Source Threshold............................................................................................................................7-96
7.119 AIS Alarm Generated................................................................................................................................7-97
7.120 B1 BER Threshold-Crossing Generated...................................................................................................7-98
7.121 B2-EXC Alarm Generated........................................................................................................................7-99
7.122 Higher Priority Clock Source Reversion Mode......................................................................................7-100
7.123 Clock Source WTR Time........................................................................................................................7-101
7.124 Lock Status..............................................................................................................................................7-101
7.125 Synchronous Source................................................................................................................................7-102
7.126 S1 Byte Synchronization Quality Information........................................................................................7-103
7.127 NE Clock Working Mode.......................................................................................................................7-104
7.128 Data Output Method in Holdover Mode.................................................................................................7-105
7.129 Retiming Mode........................................................................................................................................7-106
7.130 Switching Mode (MSP)...........................................................................................................................7-107
A Glossary and Acronyms..........................................................................................................A-1
xii Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
A.1 Numerics........................................................................................................................................................A-3
A.2 A....................................................................................................................................................................A-3
A.3 B....................................................................................................................................................................A-5
A.4 C....................................................................................................................................................................A-7
A.5 D....................................................................................................................................................................A-9
A.6 E...................................................................................................................................................................A-10
A.7 F...................................................................................................................................................................A-12
A.8 G..................................................................................................................................................................A-14
A.9 H..................................................................................................................................................................A-15
A.10 I..................................................................................................................................................................A-15
A.11 J..................................................................................................................................................................A-17
A.12 L.................................................................................................................................................................A-17
A.13 M................................................................................................................................................................A-18
A.14 N................................................................................................................................................................A-20
A.15 O................................................................................................................................................................A-21
A.16 P.................................................................................................................................................................A-22
A.17 Q................................................................................................................................................................A-24
A.18 R................................................................................................................................................................A-24
A.19 S.................................................................................................................................................................A-26
A.20 T.................................................................................................................................................................A-29
A.21 U................................................................................................................................................................A-30
A.22 V................................................................................................................................................................A-31
A.23 W...............................................................................................................................................................A-31
Issue 02 (2011-06-30) Huawei Proprietary and Confidential xiii

System
Configuration Guide Figures
Figures
Figure 1-1 Client GUI..........................................................................................................................................1-5

Figure 1-2 Main Topology.................................................................................................................................1-16
Figure 3-1 Networking diagram of the non-protection chain...............................................................................3-4
Figure 3-2 Signal flow and timeslot allocation of the services on the non-protection chain...............................3-5
Figure 3-3 Networking diagram of the non-protection ring.................................................................................3-9
Figure 3-4 Signal flow and timeslot allocation of the services on the non-protection ring...............................3-10
Figure 3-5 Networking diagram of the 1+1 linear MSP services.......................................................................3-15
Figure 3-6 Signal flow and timeslot allocation of the 1+1 linear MSP services ...............................................3-16
Figure 3-7 Networking diagram of the 1:1 linear MSP services........................................................................3-21
Figure 3-8 Signal flow and timeslot allocation of the 1:1 linear MSP services.................................................3-22
Figure 3-9 Networking diagram of the services on the two-fiber unidirectional MSP ring ..............................3-27
Figure 3-10 Signal flow and timeslot allocation of the two-fiber unidirectional MSP services .......................3-29
Figure 3-11 Networking diagram of the services on the two-fiber bidirectional MSP ring...............................3-38
Figure 3-12 Signal flow and timeslot allocation................................................................................................3-39
Figure 3-13 Networking diagram of the services on the SNCP ring .................................................................3-45
Figure 3-14 Signal flow and timeslot allocation ...............................................................................................3-46
Figure 3-15 Networking diagram of the services on the SNCP ring with a non-protection chain ....................3-53
Figure 3-17 Networking diagram of the services on the two-fiber bidirectional MSP ring with a non-protection
chain ...................................................................................................................................................................3-62
Figure 3-18 Signal flow and timeslot allocation ...............................................................................................3-63
Figure 4-1 EPL services.......................................................................................................................................4-3
Figure 4-2 PORT-shared EVPL services ............................................................................................................4-4
Figure 4-3 VCTRUNK-shared EVPL services ...................................................................................................4-4
Figure 4-4 EPLAN services (IEEE 802.1d bridge) .............................................................................................4-5
Figure 4-5 EVPLAN services (IEEE 802.1q bridge) ..........................................................................................4-6
Figure 4-6 EVPLAN services (IEEE 802.1ad bridge).........................................................................................4-7
Figure 4-7 Formats of Ethernet frames................................................................................................................4-9
Figure 4-8 Positions of the TPID and TCI in the frame structure .......................................................................4-9
Figure 4-9 TCI structure of the C-TAG ............................................................................................................4-10
Figure 4-10 TCI structure of the S-TAG ...........................................................................................................4-10
Figure 4-11 External ports and internal ports on Ethernet boards .....................................................................4-11
Figure 4-12 Waveform of a single FLP .............................................................................................................4-12
Figure 4-13 Consecutive FLP and NLP bursts ..................................................................................................4-12
Issue 02 (2011-06-30) Huawei Proprietary and Confidential xv

System
Figures Configuration Guide
Figure 4-14 Structure of the PAUSE frame....................................................................................................... 4-14

Figure 4-15 VC-3-Xv/VC4-Xv multiframe and sequence indicator .................................................................4-17
Figure 4-16 Relations between VBs, LPs, PORTs, and VCTRUNKs...............................................................4-19
Figure 4-17 Transparent bridge and virtual bridge.............................................................................................4-20
Figure 4-18 Flow of configuring EPL services .................................................................................................4-24
Figure 4-19 Flow of configuring EVPL services ..............................................................................................4-26
Figure 4-20 Flow of configuring EPLAN services............................................................................................4-28
Figure 4-21 Flow of configuring EVPLAN services ........................................................................................ 4-31
Figure 4-22 Networking diagram of the EPL services.......................................................................................4-34
Figure 4-23 Signal flow and timeslot allocation (Ethernet transparent transmission board).............................4-35
Figure 4-24 Networking diagram of the EPL services.......................................................................................4-44
Figure 4-25 Signal flow and timeslot allocation (Ethernet switching board) ................................................... 4-45
Figure 4-26 Networking diagram for configuring PORT-shared EVPL (VLAN) services ..............................4-60
Figure 4-28 Networking diagram for configuring VCTRUNK-shared EVPL (VLAN) services .....................4-73
Figure 4-30 Networking diagram for configuring EPLAN services (IEEE 802.1d bridge) ............................. 4-84
Figure 4-31 Signal flow of and timeslot allocation ...........................................................................................4-84
Figure 4-32 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge) ...........................4-97
Figure 4-33 Signal flow of and timeslot allocation to EVPLAN services (IEEE 802.1q bridge)......................4-98
Figure 4-34 Networking diagram for configuring EVPLAN services (IEEE 802.1ad bridge) .......................4-116
Figure 4-35 Signal flow of and timeslot allocation to EVPLAN services (IEEE 802.1ad bridge)..................4-117
Figure 7-1 Encapsulation format of MartinioE..................................................................................................7-29
Figure 7-2 Encapsulation format of Stack VLAN..............................................................................................7-30
Figure 7-3 An example of number of hops........................................................................................................ 7-36
xvi Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
Configuration Guide Tables
Tables
Table 2-1 SDH board parameters.........................................................................................................................2-9

Table 2-2 PDH board parameters.......................................................................................................................2-10
Table 2-3 Parameters for configuring the output phase-locked source table of an external clock.....................2-24
Table 2-4 Parameters for configuring the 2M phase-locked source attributes of an external clock..................2-25
Table 2-5 Parameters used for configuring clock protection and restoration.....................................................2-27
Table 2-6 Parameter description: clock synchronization status.........................................................................2-30
Table 2-7 Parameters used for retiming.............................................................................................................2-32
Table 2-8 Parameters for configuring orderwire phones....................................................................................2-38
Table 2-9 Parameters for configuring F1 data interfaces...................................................................................2-39
Table 2-10 Parameters for configuring broadcast data interfaces......................................................................2-40
Table 3-1 Parameters for configuring the SNCP................................................................................................3-68
Table 3-2 Parameters for configuring the MSP..................................................................................................3-70
Table 4-1 Corresponding relations between the external ports and the VCTRUNKs (EPL services).................4-3
Table 4-2 Corresponding relations between the PORTs and the VCTRUNKs (PORT-shared EVPL services)
...............................................................................................................................................................................4-4
Table 4-3 Corresponding relations between the PORTs and the VCTRUNKs (VCTRUNK-shared EVPL services)
...............................................................................................................................................................................4-5
Table 4-4 Tag types defined by using the TPID...................................................................................................4-9
Table 4-5 Processing mode of data frames on ports with different tags............................................................4-18
Table 4-6 Transparent Bridge and Virtual Bridge..............................................................................................4-20
Table 4-7 Types of bridges supported by the Ethernet boards...........................................................................4-21
Table 4-8 Flow of configuring EPL services .....................................................................................................4-24
Table 4-9 Flow of configuring EVPL services ..................................................................................................4-26
Table 4-10 Flow of configuring EPLAN services..............................................................................................4-28
Table 4-11 Flow of configuring EVPLAN services ..........................................................................................4-32
Table 4-12 Parameters of external ports on the Ethernet boards........................................................................4-35
Table 4-13 Parameters of internal ports on the Ethernet boards........................................................................4-36
Table 4-16 Parameters of the EPL services........................................................................................................4-46
Table 4-17 Parameters of the VC-4 server trail between user A1 and user A2..................................................4-57
Table 4-18 Parameters of the VC-4 server trail route between user A1 and user A2........................................4-57
Table 4-19 Parameters of the EPL services between user A1 and user A2........................................................4-58
Table 4-20 Parameters of port attributes for user A1 and user A2.....................................................................4-59
Issue 02 (2011-06-30) Huawei Proprietary and Confidential xvii

System
Tables Configuration Guide

Table 4-23 Parameters of the PORT-shared EVPL (VLAN) services...............................................................4-62
Table 4-26 Parameters of the VCTRUNK-shared EVPL (VLAN) services......................................................4-75
Table 4-29 Parameters of Ethernet LAN services (IEEE 802.1d bridge)...........................................................4-86
Table 4-32 Parameters of Ethernet LAN services (IEEE 802.1q bridge).........................................................4-100
Table 4-33 Parameters of external ports on the Ethernet boards......................................................................4-118
Table 4-34 Parameters of internal ports on the Ethernet boards......................................................................4-118
Table 4-35 Parameters of Ethernet LAN services (IEEE 802.1ad bridge).......................................................4-119
Table 4-36 Parameters for configuring the basic attributes of an Ethernet port...............................................4-131
Table 4-37 Parameters for configuring flow control of an Ethernet port.........................................................4-133
Table 4-38 Parameters for configuring network attributes of an Ethernet port................................................4-134
Table 4-39 Parameters for configuring the advanced attributes of an Ethernet port........................................4-134
Table 4-40 Parameters for configuring the tag attributes of an Ethernet port..................................................4-137
Table 4-41 Parameters for configuring the encapsulation and mapping of an Ethernet port...........................4-138
Table 4-42 Parameters for bound path.............................................................................................................4-139
Table 4-43 Parameters for configuring Ethernet private line services.............................................................4-141
Table 4-44 Parameters for configuring Ethernet private network services......................................................4-150
Table 4-45 Parameters for configuring service mount.....................................................................................4-151
Table 4-46 Parameters for configuring VLAN filtering...................................................................................4-153
Table 4-47 Parameters for configuring VLAN unicast....................................................................................4-153
Table 4-48 Parameters for configuring disable MAC address.........................................................................4-154
Table 4-49 Parameters for bound path.............................................................................................................4-154
Table 6-1 Service support capability of Ethernet boards......................................................................................6-2
Table 6-2 Requirements for binding paths with VCTRUNKs on Ethernet boards..............................................6-2
Table 7-1 The mapping protocol supported by each type of board....................................................................7-22
Table 7-2 Scramble supported by each type of board........................................................................................7-23
Table 7-3 The length of the CRC field supported by each type of board...........................................................7-24
Table 7-4 FCS calculated bit sequence supported by each type of boards.........................................................7-25
Table 7-5 CoS priority of the simple type..........................................................................................................7-54
Table 7-6 CoS priority of the VLAN Priority type............................................................................................7-55
Table 7-7 CoS priority of the DSCP type...........................................................................................................7-55
Table 7-8 CoS priority of the IPTOS type..........................................................................................................7-55
Table 7-9 Recommended values of the port path cost........................................................................................7-65
xviii Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
Configuration Guide 1 Getting Started
1 Getting Started
About This Chapter
The following topices introduce some preparation operations that will ensure a smooth, trouble-
free launch of the U2000.
1.1 Starting or Shutting Down the U2000

The U2000 uses the standard client/server architecture and multiple-user mode. So, you are
recommended to start or shut down the U2000 by strictly observing the following procedure, in
order not to affect other users that are operating the U2000.
1.2 Main Windows and Common Operations of the U2000
This topic describes the main windows of the U2000 client. Learning the main windows helps
you to locate the entrances to operations quickly, which increased your operation efficiency.
Issue 02 (2011-06-30) Huawei Proprietary and Confidential 1-1

System
1 Getting Started Configuration Guide
1.1 Starting or Shutting Down the U2000

The U2000 uses the standard client/server architecture and multiple-user mode. So, you are
recommended to start or shut down the U2000 by strictly observing the following procedure, in
order not to affect other users that are operating the U2000.
Context
l You are recommended to start the computer and theU2000 application in the following
sequence: Start the computer, start theU2000 server, and then start theU2000 client.
l You are recommended to shut down theU2000 application and the computer in the
following sequence: Exit theU2000 client, stop theU2000 server, and then shut down the
computer.
1.1.1 Starting the U2000 Server
For network management first start theU2000 server, and then start theU2000 application.
1.1.2 Logging In to the U2000 Client
To manage networks through the U2000 client graphical user interface, you need to use
theU2000 client to log in to the U2000 server.
1.1.3 Exiting a U2000 Client
Before shutting down the U2000 server, you must exit the U2000 client.
1.1.4 Shutting Down the U2000 Server
When the U2000 server is managing the system normally, do not perform this operation. In
special circumstances, for example, when modifying the system time of the computer where the
U2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the U2000 server.
1.1.1 Starting the U2000 Server

For network management first start theU2000 server, and then start theU2000 application.
Prerequisite
l The computer time must be set correctly.
l The computer where theU2000 is installed must be started correctly.
l The operating system of theU2000 server must be running correctly and the database must
be started normally.
l TheU2000 license must be in the server directory.
l The instance must be deployed.
Procedure
Step 1 Double-click the shortcut icon to start U2000 Server.

Step 2 In the Login dialog box, enter the user name and password. The user name is admin and the
password is null by default. Change the password of the default user at the first login. Then,
click Login to display the System Monitor window.
1-2 Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
NOTE
Periodically change the password and memorize it.

You can login to theU2000 client, checking whether the status of each process is Running.
----End
1.1.2 Logging In to the U2000 Client

To manage networks through the U2000 client graphical user interface, you need to use
theU2000 client to log in to the U2000 server.
Prerequisite
The U2000 server must be started correctly.
Procedure
Step 1 Double-click the U2000 Client shortcut icon.
Step 2 In the Login dialog box, enter the user name and password. The user name is admin and the
password is null by default. Change the password of the default user at the first login. Then,
click Login.
Step 3 Optional: For the first login, you need to configure the access control list of the system.
----End
1.1.3 Exiting a U2000 Client

Before shutting down the U2000 server, you must exit the U2000 client.
Prerequisite
The U2000 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, the Confirm dialog box appears asking you whether to
save the changes. After you confirm the dialog box, automatically exit the client.
----End
1.1.4 Shutting Down the U2000 Server

When the U2000 server is managing the system normally, do not perform this operation. In
special circumstances, for example, when modifying the system time of the computer where the
U2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the U2000 server.

System
Prerequisite
All the U2000 clients connected to the U2000 server must be shut down.
Procedure
Step 1 From the Main Menu of System Monitor Client, choose System > Stop All NMS Services to
close all processes of the U2000 server.
Step 2 Click OK in the confirmation dialog box. Wait until the U2000 core process, and the processes
that are optional according to the actual situation are in the Stopped state. Now the U2000 server
is shut down successfully.
Now you cannot shut down the MDP process or initialize the database.
Step 3 Click OK in the confirmation dialog box. Wait until the U2000 processes are all in Stopped
status. Now the server is shut down successfully.
Now you cannot shut down the MDP process or initialize the database.
----End
1.2 Main Windows and Common Operations of the U2000

This topic describes the main windows of the U2000 client. Learning the main windows helps
you to locate the entrances to operations quickly, which increased your operation efficiency.
1.2.1 Components of the Client GUI

This topic describes the components of the client GUI.
1.2.2 Key GUI Components
The key U2000 GUI components are as follows:
1.2.3 Frequently Used Buttons
The frequently used buttons on the U2000 GUI are as follows:
1.2.4 Shortcut Icon
This topic describes the shortcut icons on the Main Topology.
1.2.5 Common Shortcut Keys
This topic describes the common shortcut keys. Using shortcut keys, you can increase the
operation efficiency. The shortcut keys include Enter, Ctrl, Esc, and Tab.
1.2.6 Main Windows
This topic describes the main windows of the U2000 client. And tells you what you can do in
the windows.
1.2.1 Components of the Client GUI

This topic describes the components of the client GUI.
Figure 1-1 shows the client GUI.

System
Figure 1-1 Client GUI
3
6
1: Menu bar 2: Toolbar 3: Workbench list
4: Output pane 5: Status bar 6: Workbench
Menu Bar
The menu bar provides the entries to all the functions of the U2000 client. It consists of the
following menus: File, Fault, Performance,Configuration, Service, Inventory,
Administration, Window, and Help. In the topology window, the menu bar also provides the
Edit and View menu items.
Toolbar
The toolbar provides the shortcut icons for major operation tasks. The shortcut icons are as
follows:
l : Accesses the favorites folder.
l : Deregister your account.
l : Displays in full screen.
l : Browse Current Alarm.
l : Log Out.

System
l : Locks the U2000 client.
l : Creates fiber.
l : NE Explorer.
l : Main Topology.
l : Views the SDH performance.
l : Views the WDM performance.
l : Maintains the SDH protection subnet.
l : Manages WDM trails.
l : Creates SDH trails.
l : Manages SDH trails.
Workbench list
You can create or modify a workbench through the shortcut icons.
Output Pane
The output pane displays the returned information and other relevant information.
Status Bar
The status bar displays the information such as the system status, the login users, and the IP
address of the connected server. The information displayed from left to right is as follows:
l Coordinate information: Displays the current position of the cursor.
l Connection information: Displays the name and IP address of the server.
l Login user: Displays the name of the login user.
l Connection duration: Displays the duration of the connection between the client and the
server.
l Login mode: Displays the login mode. It can be single-user mode and multi-user mode.
l Operation prompt: Displays the result of the operation.
l Logo: Displays the logo of Huawei Technologies Co., Ltd.
Workbench
The shortcut icons on the workbench help you perform operations.
1.2.2 Key GUI Components

The key U2000 GUI components are as follows:

System
Component Example
Button
Shortcut icon
Radio button
Check box
Tab
Field
Drop-down
menu
Menu
Function Tree
Dialog box
1.2.3 Frequently Used Buttons

The frequently used buttons on the U2000 GUI are as follows:

System
Button Functionality
Selects the objects.
Expands all available options.
Collapses all available options.
Displays or hides a dialog box.
Selects the objects.
Selects the objects as a batch.
Increases the priority of the selected object.
Decreases the priority of the selected object.
Displays a dialog box.
Queries results from the NE.
Imposes the current settings.
Displays the latest result(s).
Exports the selected scheduled tasks to the

browser of the operating system for printing.
Saves selected data to the specified file.
Makes the current setting effective and closes

the dialog box.
Cancels the current setting and closes the

dialog box.

System
Button Functionality
Allows the user to view and select the board

ports.
Deletes the selected data or icon.
Closes the operation wizard.
Creates a new service, protection or physical

inventory information etc.
Proceeds to the next step.
Returns to the previous step.
Closes the dialog box.
Expands the Object Tree.
Collapses the Object Tree.
Makes the current setting effective and closes

the dialog box.
Cancels the current setting and closes the

dialog box.
Search the correlative information.
Sets the correlative condition.
1.2.4 Shortcut Icon

This topic describes the shortcut icons on the Main Topology.
You can customize the toolbar so that only the frequently-used buttons are displayed on the
toolbar. To customize the toolbar, right-click the toolbar and choose a menu item from the
shortcut menu.
Button Name Description
Favorites Folder Adds the commonly used functions to

the favorites folder.
Exit Exits from the client.

System
Lock Terminal Locks the current client.
Main Topology Switches to the Main Topology.
Log Out Logs out of the current session.
Views the topology Views the current window in full

in full screen. screen.
Browse Current Displays the Current Alarms

Alarm window.
SDH Protection Accesses the SDH Protection Subnet

Subnet Common Attributes window.
Maintenance
SDH Trail Accesses the SDH Trail

Management Management window.
SDH Trail Creation Accesses the SDH Trail Creation

window.
WDM Trail Accesses the WDM Trail

Management Management window.
Verify Policy Verifies the validity of a configuration

policy before the policy is deployed on
devices.
Deploy Policy Deploys a policy to the selected

devices or device groups.
Undeploy Policy Undeploys all the policies in the

current policy package from the
selected devices and clear the related
commands deployed on these devices.
Discover Policy Policy auditing is to audit the policy

configuration differences between the
NMS and device, so as to determine
whether the policy needs to be
deployed or discovered.
Audit Policy Policy discovery is to recover the data

synchronized to the database to the
NMS for management.
Save Saves a policy package.

System
View History Queries the history record of policy

Record deployment or undeployment
according to the device name, device
IP address, status, and operator.
NE Explorer Accesses the NE Explorer window of

the selected NE.
Create Link Creates fiber and radio links.
Browse SDH Accesses the Browse SDH

Performance Performance window.
Browse WDM Accesses the Browse WDM

Performance Performance window.
Lay Out Lays out the NEs in the topology.
Print and Preview Prints and previews the current

topology view.
New Selects Custom View, NESubnet, or

Link from the drop-down list box.
Creat Link Creates a link in the Main Topology.
Print Prints the current Main Topology.
Up Returns to the previous level.
Zoom out Zooms out the Main Topology.
Zoom in Zooms in the Main Topology.
Zoom in Partially Zooms in an area selected in the Main

Topology.
View Move Moves the Main Topology. When you

click this icon, the Main Topology can
be moved. When you click the icon
again, the Main Topology cannot be
moved.
Alarm List Area Views the alarm list area in the lower
part of the Main Topology.
Search NE Searches for an NE in the view.
Select Selects the NE in the Main Topology.

System
Topology Views the navigation tree in the

Navigator Topology.
View Navigator Views the view navigation tree in the

Topology.
Legend&Filter&At Opens the setting area of the view to

tribute display the attribute, filter plane and
legends.
NE Statistics Views the quantity of the NE on the

network.
Save the Location Saves the location of the current

of the Current submap icons.
Submap Icons
Refresh View Refreshes the current view.
Lock View Locks out the position of an NE icon in

the active view.
Unlock View Unlocks the position of an NE icon in

the active view.
NE Time Synchronizes the NE time and NMS

Sychronization time.
Synchronize Synchronizes the current alarms of an

Current Alarms NE.
Browse Current Browses the current alarms of an NE.

ALarms
Clear ALarm Clears the current alarm indications of

Indication an NE.
Refresh NE Panel Refreshes the NE panel status to make

Status the NE panel display the latest data.
Verify Verifies the configuration data. During

Configuration the verification, two risky operation
prompts are displayed.
Back Up NE Backs up the NE data to the SCC.

Database To SCC
Display/Hide Displays or hides the extended slot on

Extended Slot the Extended Slot tab page.
Legend Displays a legend and its description.
Shrink all Shrinks Alarm/Event Name.

System
Classify by group id Classifies alarms by group ID.
Classify by severity Classifies alarms by severity.
Classify by type Classifies alarms by type.
Classify by Classifies alarms by category.

category
1.2.5 Common Shortcut Keys

This topic describes the common shortcut keys. Using shortcut keys, you can increase the
operation efficiency. The shortcut keys include Enter, Ctrl, Esc, and Tab.
Shortcut Key Description
F1 Opens the Help.
Enter Confirms the operation or moves downward to the next line. If the
cursor is on a button, pressing Enter means to confirm the operation.
If the cursor is in the list box, press Enter once and the cursor then
moves downward to the next line.
Esc Closes a dialog box.
Tab Switches between buttons if the cursor is on a button. Switch between

text boxes if the cursor is in the list box.
Ctrl+F Searches resources such as the NEs, subnets, cards, frames, interfaces,
and VLANs in basic and rapid modes by pressing Ctrl+F in all views.
Ctrl+A Selects all NEs or selects all contents in the list. If the cursor is in the
view, press Ctrl+A to select all NEs. If the cursor is in the list box,
press Ctrl+A to select all contents in the list.
Ctrl+C Quickly copies the table texts.
Ctrl+V Pastes the copied data to another text area.
Alt+F Opens the File menu from the Main Menu.
Alt+E Opens the Edit menu from the Main Menu.
Alt+V Opens the View menu from the Main Menu.
Alt+U Opens the Fault menu from the Main Menu.
Alt+P Opens the Performance menu from the Main Menu.
Alt+C Opens the Configuration menu from the Main Menu.
Alt+R Opens the Service menu from the Main Menu.

System
Shortcut Key Description
Alt+I Opens the Inventory menu from the Main Menu.
Alt+S Opens the Administration menu from the Main Menu.
Alt+W Opens the Window menu from the Main Menu.
Alt+H Opens the Help menu from the Main Menu.
1.2.6 Main Windows

This topic describes the main windows of the U2000 client. And tells you what you can do in
the windows.
1.2.6.1 Workbench
This topic describes the workbench. After a client is started, the system automatically accesses
the default workbench. The default shortcut icons are displayed on the workbench.
1.2.6.2 Main Topology
This topic describes the items in the Main Topology. All topology management functions can
be accessed through the Main Topology in . These functions include creating topological objects,
subnets, searching for the existing equipment in the network. You can search, view, create, set,
and manage subnets; and search, create, configure, and maintain management functions on trails.
1.2.6.3 NE Explorer
The NE Explorer is the main user interface used to manage equipment. In the NE Explorer, a
user can configure, manage and maintain the NE, boards, and ports on a per-NE basis. The NE
Explorer is the main user interface for commissioning and configuration on a per-NE basis. The
NE Explorer contains a Function Tree that makes the operations easy. To display the
configuration window for an object, the user can just select the object and then choose a desired
function in the Function Tree.
1.2.6.4 Clock View
The Clock View provides a visible platform to enable NE clock settings, networkwide clock
synchronization status query, and clock tracing and search functions, supports the synchronous
Ethernet clock, SDH clock, TOP clock, ACR clock, TDM clock, PON clock, and E1 clock, and
applies to the MSTP, RTN ,PTN and router NE40E V3R7 equipment.
1.2.6.5 NE Panel
The NE Panel displays boards and ports in different colors depending on their current status. In
the U2000, most operations such as equipment configuration, monitoring, and maintenance are
performed in the NE Panel window.
1.2.6.6 Browse Alarm
This topic describes the user interface for viewing the current and history alarms, Alarm Logs.
In this user interface, buttons are provided, such as Filter, Synchronize, Refresh, and
Acknowledge, to help you quickly locate the alarm cause.
1.2.6.7 Browse Event
In the Browse Event window, you can view events at different levels. This window provides
buttons, such as Filter by Template, Filter and Refresh, to help you to quickly locate the alarm
cause.
1.2.6.8 Browse Performance Window

System
You can view the current and history performance data, UAT events and performance threshold
crossings.
1.2.6.1 Workbench
This topic describes the workbench. After a client is started, the system automatically accesses
the default workbench. The default shortcut icons are displayed on the workbench.
l In the main windows of the U2000, click the to access the workbench.
l You can do as follows to modify a workbench: Right-click the icon of the workbench and
choose Modify Workbench from the shortcut menu to modify the name or description of
a workbench.
l You can expand and order workbenches to separate the customized workbenches from the
default workbench.
l You can view the description about the function of the workbench in the background picture
of the workbench and press F1 to view the Help.
1.2.6.2 Main Topology

This topic describes the items in the Main Topology. All topology management functions can
be accessed through the Main Topology in . These functions include creating topological objects,
subnets, searching for the existing equipment in the network. You can search, view, create, set,
and manage subnets; and search, create, configure, and maintain management functions on trails.
GUI
To open the Main Topology, log in to the U2000. If the preceding operation closes the Main
Topology, you can choose View > Main Topology from the main menu to open the Main
Topology. Figure 1-2 shows the Main Topology of the U2000.

System
Figure 1-2 Main Topology
1 2 3 4 5
6 7 8 9 10 11 12
1: Network management 2: Menu bar 3: Shortcut button

system name You can operate the NM and Click the button, you can
the NE with submenu bar, perform a simple task
include configure tasks, quickly. For example: exit
manage tasks and so on. NM, lock terminal, log out,
NMS user management, stop
the current alarm sound,
browse alarm, NE explorer,
creating connections,,
browse performance
window.

System
4: Shortcut button 5: Alarm button bar 6: NMS status bar

Click the button, you can The Alarm buttons for Views the running
perform a simple task quickly alarms at different severity information of the NMS. For
on the Main Topology. For levels are in different colors. example, NMS login, and
example: zoom in or zoom You can click the button to loading of each module.
out or refresh or save the view the number of the
view, show or hide the alarms generated on the
navigators, search objects, current U2000. You can click
see object attributes, lock or the button to view current
unlock the view. alarms. For example:
browsing the alarm list, show
alarm panel.
When the U2000 has
abnormal events, the
Abnormal event indicator
turn to red from green. You
can click the indicator to
view current abnormal
events.
7: Views the current location 8: Physical Map 9: Views the name which is
of the cursor in the Main Views the managed set by the current U2000
Topology. equipment. client, and views the IP
address of the current
On the Physics Map, you can U2000 server.
perform operations, such as
creating NEs, deleting
topology objects, NE
explorer, creating
connections, browsing
fibers/cables, configuring the
NE data, browse
performance window, and so
on.
10: Views user name of the 11: Filter Tree and Legend 12: Total elapsed time after
logged-in U2000 user In this area, you can set the the current user is logged in
currently. display types of the objects in to the U2000.
a view, and view the
descriptions of legends in the
view. To locate an operation
object quickly.
1.2.6.3 NE Explorer
The NE Explorer is the main user interface used to manage equipment. In the NE Explorer, a
user can configure, manage and maintain the NE, boards, and ports on a per-NE basis. The NE
Explorer is the main user interface for commissioning and configuration on a per-NE basis. The
NE Explorer contains a Function Tree that makes the operations easy. To display the
configuration window for an object, the user can just select the object and then choose a desired
function in the Function Tree.

System
NOTE
You can open a maximum of five NE Explorer windows at the same time.
GUI
l Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
l In the left-hand pane of the Main Topology, right-click an NE and choose NE Explorer
from the shortcut menu.
Correlation operation
l Click the in NE Explorer window, display the 1.2.6.5 NE Panel.
l Click the in NE Explorer window, switch to other NE.
1.2.6.4 Clock View

The Clock View provides a visible platform to enable NE clock settings, networkwide clock
synchronization status query, and clock tracing and search functions, supports the synchronous
Ethernet clock, SDH clock, TOP clock, ACR clock, TDM clock, PON clock, and E1 clock, and
applies to the MSTP, RTN ,PTN and router NE40E V3R7 equipment.
GUI
Access the clock view. In the Main Topology window, select Clock View from the Current
View drop-down list. Select the NE to be queried or configured from the object tree.
Legends
l The Clock View uses continuous lines to represent the trace relations between NEs. Smaller
number indicates higher priority. The number displayed on the continuous line indicates
the priority of the traceable clock. The Clock View displays the line clock source numbers
only. Internal and tributary clock sources are also numbered, but they are not displayed in
the Clock View.
l The arrow direction in the Clock View indicates the clock tracing direction. For example,
if NE2 points to NE3, it indicates that NE3 traces the clock information transmitted from
NE2, and that NE3 traces the primary PRC NE1-External 1.
l The arrow direction in the Clock View indicates the clock tracing direction.
l An internal clock source is the clock provided by an NE, and has no trace relations with
other NEs. Therefore, internal clock sources are not displayed on the Clock View.
l Tributary clock sources have no relation with the clock sources that are not provided by
the U2000. Therefore, the clock trace relations are not displayed on the Clock View.
l On the U2000, the four clock trace relations of free-run, tracing, holdover, and invalid are
respectively identified in blue, green, yellow, and red.
l In the Clock View, you can select multiple NEs, right-click, and query the clock
synchronization status or search for clock trace relations.

System
NOTE
The rule of verifying an invalid clock tracing relation is as follows: First, verify whether a clock source is in the
SSM protocol mode. In the non-SSM protocol mode, verify the status of a clock source. The status directly
determines whether a clock tracing relation is invalid. In the SSM protocol mode, verify the status of a clock
source. If the status is unavailable, it indicates that the clock tracing relation is invalid. If the status is available,
you also need to verify the S1 byte (clock quality). When you manually cancel settings of the quality of the S1
byte and the quality of the S1 byte is unknown, the clock tracing relation is invalid.
1.2.6.5 NE Panel
The NE Panel displays boards and ports in different colors depending on their current status. In
the U2000, most operations such as equipment configuration, monitoring, and maintenance are
performed in the NE Panel window.
GUI
Double-click an NE on the Main Topology to display the NE Panel.
To add a new board, right-click an idle slot and choose a board type.
NOTE
l Choose the Always On Top for the Slot Layout window to always remain on top.
l When a board occupies multiple slots, the slot ID of the main slot is displayed in boldface, and the slot
ID of the slave slot is grayed out.
l In the NE panel, when you click the processing board that is accompanied by an interface board, the
slot ID of this interface board is displayed in orange.
Click the icon on the toolbar, to view the legends of the boards and ports on the right of the
Slot Layout.
To select an operation related to an installed board, right-click the installed board and choose it
from the shortcut menu. For example, right-click an AUX board and choose Path View to display
the detailed path information.
1.2.6.6 Browse Alarm

This topic describes the user interface for viewing the current and history alarms, Alarm Logs.
In this user interface, buttons are provided, such as Filter, Synchronize, Refresh, and
Acknowledge, to help you quickly locate the alarm cause.
GUI
l Choose Fault > Browse Current Alarm from the main menu.
l Choose Fault > Browse History Alarm from the main menu.
l Choose Fault > Browse Alarm Logs from the main menu.
1.2.6.7 Browse Event

In the Browse Event window, you can view events at different levels. This window provides
buttons, such as Filter by Template, Filter and Refresh, to help you to quickly locate the alarm
cause.

System
GUI
Choose Fault > Browse Event Logs from the main menu.
1.2.6.8 Browse Performance Window

You can view the current and history performance data, UAT events and performance threshold
crossings.
GUI
Choose Performance > Browse SDH Performance from the main menu.

System
Configuration Guide 2 Creating the Network
2 Creating the Network
About This Chapter
NEs and fibers or cables can be managed on the U2000 only after their topologies are created.
2.1 Creating NEs

Each piece of equipment is represented as an NE on the U2000. Before the U2000 manages the
actual equipment, you need to create the corresponding NEs on the U2000. There are two NE
creation methods, namely, creating a single NE and creating NEs in batches. When you need to
create a large number of NEs, for example, during the deployment, it is recommended that you
use the method of creating NEs in batches. When you need to create only a few NEs, it is
recommended that you use the method of creating a single NE.
2.2 Configuring the NE Data
After an NE is created, you need to configure the data of the NE on the U2000. Otherwise, the
U2000 still cannot manage the NE.
2.3 Checking Board Parameters
To learn about board parameter status, you can check board parameters. Before configuring the
boards in actual networking, you need to check board parameters and ensure that the board
parameters meet the requirements of actual networking.
2.4 Creating Fibers
You can create fibers, serial port cables, extended ECC, and virtual fibers by using the U2000.
2.5 Creating a Topology Subnet
To facilitate network management, you can assign the topology objects in the same network area
or with similar attributes into the same topology subnet.
2.6 Configuring the Protection Subnet
The OptiX OSN equipment supports various network level protection schemes, including the
linear MSP.
2.7 Configuring Clocks
A clock is the basis for the normal operation of an NE. You need to configure the clocks for all
the NEs before configuring services. In addition, you need to configure the clock protection in
the case of a complicated network.
2.8 Clock Configuration Parameters

System
2 Creating the Network Configuration Guide
A clock is one of the basic configuration items of an NE. When configuring a clock, you need
to set the parameters in terms of clock source, clock protection, clock quality, and retiming
management.
2.9 Configuring the Orderwire Phone
The orderwire phone provides an important communication tool for maintenance personnel.
2.10 Configuring the Broadcast Data Service
To meet the requirements for the broadcast data services between the monitoring host and the
environment monitors, you need to configure the broadcast data services of NE1-NE4.
2.11 Configuring the F1 Data Service
The F1 data service is transparently transmitted in the point-to-point mode by using the F1 byte.
2.12 Orderwire Configuration Parameters
The equipment supports various orderwire management, which involves orderwire phones and
F1 data interfaces.

System
2.1 Creating NEs

Each piece of equipment is represented as an NE on the U2000. Before the U2000 manages the
actual equipment, you need to create the corresponding NEs on the U2000. There are two NE
creation methods, namely, creating a single NE and creating NEs in batches. When you need to
create a large number of NEs, for example, during the deployment, it is recommended that you
use the method of creating NEs in batches. When you need to create only a few NEs, it is
recommended that you use the method of creating a single NE.
2.1.1 Creating a Single NE

After an NE is created, you can use the U2000 to manage the NE. Creating a single NE is not
as quick and accurate as creating NEs in batches. But you can create a single NE regardless of
whether the data is configured on the NE side.
2.1.2 Creating NEs in Batches
When the U2000 communicates with the gateway NE normally, you can create NEs in batches
by searching for all the NEs that communicate with the gateway NE according to the IP address
of the gateway NE, the network segment to which the IP address of the gateway NE belongs, or
the NSAP addresses of the NEs. This method is quicker and more accurate than manual creation.
2.1.1 Creating a Single NE

After an NE is created, you can use the U2000 to manage the NE. Creating a single NE is not
as quick and accurate as creating NEs in batches. But you can create a single NE regardless of
whether the data is configured on the NE side.
Prerequisite
l You must be an NM user with "NM operator" authority or higher.
l The NE Explorer instance of the NEs must be created.
Background Information
First create a gateway NE, and then create a non-gateway NE.
Procedure
Step 1 Right-click in the blank area of the Main Topology and choose New > NE from the shortcut
menu. Then, the Create NE dialog box is displayed.
Step 2 Select the NE type from the Object Type drop-down list.
Step 3 Set ID, Extended ID, Name, and Remarks

System
Step 4 To create a gateway NE, proceed to Step 5. To create a non-gateway NE, go to Step 6.
Step 5 Choose Gateway Type and Protocol, and set the IP address.
1. Select Gateway from the Gateway Type drop-down list.
2. Select the Protocol type.
If ... Then ...
The U2000 communicates Select IP from the Protocol drop-down list. Set IP
with NEs through the IP Address of the gateway NE and use the default value of the
protocol Port number.
The U2000 communicates Select OSI from the Protocol drop-down list. Set NSAP
with NEs through the OSI Address of the gateway NE.
protocol
Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the gateway NE to which
the NE belongs from the Affiliated Gateway drop-down list.
Step 7 Set NE User and Password.

NOTE
The default NE user is root, and the default password is password.
Step 8 Optional: If you need not deliver the NE configuration data from the U2000 to the NE, select
the NE Preconfiguration check box and set NE Software Version.
NOTE
Do not deliver the NE preconfiguration data from the U2000 to the NE if the freconfiguration data is
inconsistent with the actual configurations on the NE. Otherwise, the services on the NE are affected.
Step 9 Click OK. Click in the blank area of the Main Topology. Then, the NE icon is displayed at the
position where you clicked.
NOTE
If the NE creation is incorrect or if the communication between the NE and the U2000 is abnormal, the
NE is displayed in grey.
----End

System
Result
After an NE is successfully created, the system automatically saves the information, such as the
IP address, NSAP address, subnet mask, and NE ID to the U2000 database.
Follow-up Procedure
if you fail to log in to the created NE, the possible causes are listed as follows:
l The communication between the U2000 and the NE is abnormal. In this case, check the
settings of communication parameters, such as the IP address and ID of the NE.
l The NE user is invalid. Change to use a valid NE user.
2.1.2 Creating NEs in Batches

When the U2000 communicates with the gateway NE normally, you can create NEs in batches
by searching for all the NEs that communicate with the gateway NE according to the IP address
of the gateway NE, the network segment to which the IP address of the gateway NE belongs, or
the NSAP addresses of the NEs. This method is quicker and more accurate than manual creation.
Prerequisite
l You must be an NM user with "NE administrator" authority or higher.
l The U2000 must communicate with the gateway NE normally.
l The NE Explorer instance of the NEs must be created.
Procedure
Step 1 Choose File > Discovery > NE from the Main Menu. Then, the NE Discovery window is
displayed.
Step 2 Choose Transport NE Search tab, Click Add. Then, the Input Search Domain dialog box is
displayed.
Step 3 Set Address Type to IP Address Range of GNE, IP Address of GNE, or NSAP Address.
Enter Search Address. Then, Click OK.

System
NOTE
You can repeat Steps 2 and 3 to add more search domains. You can also delete the system default search
domain.
l If you search for the NEs according to the IP address of the gateway NE and if the IP address of the
U2000 computer and the IP address of the gateway NE are within the same network segment, you can
set Address Type to IP Address Range of GNE or IP Address of GNE.
l If the IP addresses of the gateway NE and the U2000 computer are in two different network segments,
you can set Address Type to IP Address of GNE only.
l If you search the NEs according to the NSAP addresses of the NEs, you can set Address Type to
NSAP address only.
Step 4 In the NE Discovery window, ClickNext.
Step 5 After the search is complete, select the uncreated NEs from the Result list and then click
Create. The Create dialog box is displayed.
Step 6 Enter the NE user name and password.

NOTE
l The default NE user is root.

l The default password is password.
Step 7 Click OK.
----End
Follow-up Procedure
If you fail to log in to the created NE, the possible causes are listed as follows:
l The password for the NE user is incorrect. In this case, enter the correct password for the
NE user.
l The NE user is invalid. Change to use a valid NE user.
2.2 Configuring the NE Data

After an NE is created, you need to configure the data of the NE on the U2000. Otherwise, the
U2000 still cannot manage the NE.
2.2.1 Configuring the NE Data Manually

By configuring NE data manually, you can configure the slot layout information of an NE.
2.2.2 Replicating the NE Data
You can directly replicate the data of an NE that is of the same NE type and NE version to the
newly created NE.
2.2.3 Uploading the NE Data
By uploading the NE data, you can synchronize the current NE configuration data to the
U2000 directly.
2.2.1 Configuring the NE Data Manually

By configuring NE data manually, you can configure the slot layout information of an NE.

System
Prerequisite
l The NE must be created successfully.
l You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Double-click the unconfigured NE on the Main Topology. Then, the NE Configuration
Wizard dialog box is displayed.
Step 2 Select Manual Configuration and click Next. Then, the Confirm dialog box is displayed,
indicating that manual configuration clears the data on the NE.
Step 3 Click OK. Then, the Confirm dialog box is displayed, indicating that manual configuration
interrupts the service on the NE.
Step 4 Click OK. Then, the Set NE Attribute dialog box is displayed.
Step 5 Set NE Name, Equipment Type, NE Remarks, and Shelf Type and then click Next. The NE
slot layout window is displayed.
Step 6 Optional: Click Query Logical Information to query the logical boards of the NE.
Step 7 Optional: Click Query Physical Information to query the physical boards of the NE.
NOTE
The Query Logical Information and Query Physical Information operations cannot be performed for
a preconfigured NE.
Step 8 Right-click the slot to which you need to add a board. Click Next. Then, the Send
Configuration window is displayed.
Step 9 Select Verify and Run according to the requirements and click Finish.
NOTE
Verification is to run the verification command. Click Finish to deliver the configuration data to the NE,
thus completing the basic configuration of the NEs. After the successful verification, the NEs start to work
normally.
----End

System
2.2.2 Replicating the NE Data

You can directly replicate the data of an NE that is of the same NE type and NE version to the
newly created NE.
Prerequisite
l The NE type and NE version of the source NE must be the same as the NE type and NE
version of the newly created NE.
Procedure
Step 2 Select Copy NE Data and click Next. Then, the NE Replication dialog box is displayed.
Step 3 Select the NE from the drop-down list and click Start. Then, the Confirm dialog box is
displayed, indicating that the replication operation copies all the data of the source NE.
NOTE
After the NE data is replicated, only the data on the U2000 is changed, but the data on the equipment is
not changed.
Step 4 Click OK. Then, the Confirm dialog box is displayed, indicating that the replication operation
results in the loss of the original data of the NE to which the data is replicated.
Step 5 Click OK to start the replication.
Step 6 Wait for several seconds. Then, in the Result dialog box indicating that the operation succeeded,
click Close.
----End
2.2.3 Uploading the NE Data

By uploading the NE data, you can synchronize the current NE configuration data to the
U2000 directly.

System
Prerequisite
Procedure
Step 2 Select Upload and click Next. Then, the Confirm dialog box is displayed.
Step 3 Click OK to start the upload. When the uploading is completed, the Operation Result dialog
box is displayed, indicating that the operation succeeded.
Step 4 Click Close.
----End
2.3 Checking Board Parameters

To learn about board parameter status, you can check board parameters. Before configuring the
boards in actual networking, you need to check board parameters and ensure that the board
parameters meet the requirements of actual networking.
Procedure
Step 1 Select the corresponding navigation path and check the related board parameters.
1. Check the SDH board parameters. For the SDH board parameters, see Table 2-1.
Table 2-1 SDH board parameters
Boar
Paramet Navigation
d Application Scenario
er Path
Type
Laser a. In the NE When configuring MSP shared services on an

Switch Explorer, optical interface of a board, enable this
select a board. parameter.
b. Choose
When configuring services on an optical
Configuratio
interface of a board, enable this parameter.
n > SDH
Interface
SDH from the
Function
Tree.
c. Click By
Board/Port
(channel)
and select
Port from the

System
Boar
Paramet Navigation
er Path
Type
Optical drop-down l Non-loopback: It is the normal state. When

(Electrical list. the equipment runs normally, set this
)Interface parameter to non-loopback.
Loopback l Inloop: The loop is performed toward the
local NE.
l Outloop: The loop is performed toward the
opposite NE. Inloop and outloop of an
optical interface affect services. They are
used to locate faults.
2. Check the PDH board parameters. For the PDH board parameters, see Table 2-2.
Table 2-2 PDH board parameters
Boar
Paramet Navigation
er Path
Type
Tributary l Non-loopback: It is the normal state. When

Loopback the equipment runs normally, set this
a. In the NE parameter to non-loopback.
Explorer, l Inloop: When input service signals reach
select a board. the tributary board of the target NE, the
b. Choose signals revert to the original trail. This
Configuratio function is used to locate faults of each
n > PDH service path.
Interface l Outloop: When input service signals reach
from the the tributary board through the input port
PDH Function of the local NE, the signals are looped back
Tree. directly to the service output end.
c. Click By
Service Board/Port l Non-loaded: The service path does not
Load (channel) process the services that are carried, to
Indication and select suppress alarms in non-loaded service
Port from the paths.
drop-down l Load: The service path processes the
list. services that are carried. In the case of a
tributary board that has services, set this
parameter to Load.
Step 2 Change the values of the board parameters according to service planning and actual board
configurations. For details, see 5.2.3 Modifying Board Configuration Parameters.
----End

System
2.4 Creating Fibers

You can create fibers, serial port cables, extended ECC, and virtual fibers by using the U2000.
2.4.1 Creating Fibers Automatically

By using the fiber search feature, you can check whether a specified optical interface is connected
to a fiber. Then, you can quickly create a fiber for this optical interface on the U2000. In the
case of a newly created network, after configuring the boards on the U2000, you can search for
all the optical interfaces and then create the fibers on the entire network. In this way, you can
monitor the actual working status of each fiber.
2.4.2 Creating Fibers Manually
Before you configure services, you need to create the required fibers. You can create a small
number of fibers manually one after another.
2.4.3 Creating Virtual Fibers
When the U2000 manages the SDH, PTN, and WDM equipment at the same time, you can create
virtual fibers between the SDH or PTN equipment (with the WDM equipment in between), to
facilitate network management.
2.4.4 Creating DCN Communication Cable
The U2000 can communicate with NEs through the Ethernet port or serial port. The NEs can
also communicate with each other through the extended ECC. Depending on the communication
mode, different types of communication cables can be created on the U2000.
2.4.1 Creating Fibers Automatically

By using the fiber search feature, you can check whether a specified optical interface is connected
to a fiber. Then, you can quickly create a fiber for this optical interface on the U2000. In the
case of a newly created network, after configuring the boards on the U2000, you can search for
all the optical interfaces and then create the fibers on the entire network. In this way, you can
monitor the actual working status of each fiber.
Prerequisite
l Fibers must be connected to the optical interfaces of each NE.
l The boards of each NE must be created on the U2000.
l You must be an NM user with "NE maintainer" authority or higher.
Precautions
CAUTION
l If conflicting fibers are detected during the creation, delete the conflicting fibers on the
U2000 before you start creating new fibers.

System
Procedure
Step 1 Choose File > Discovery > Fiber from the Main Menu.
Step 2 In the pane on the left, select one or more ports of the NE and click Search. Then, the progress
bar is displayed, indicating the progress of the search.
NOTE
l If you select the Do not search the ports with Fibers/Cable created on NMS check box, the system
only searches for the ports that do not have fibers.
l To check whether the created fibers are consistent with the actual fiber connection, deselect the Do not
search the ports with Fibers/Cable created on NMS check box.
l If you select the Do not search the ports with Fibers/Cable created on NMS check box and if the
fibers are created for all the selected ports, a dialog box is displayed indicating that the search domain
is null.
Step 3 A dialog box is displayed, indicating that the operation is successful. Click Close.
Step 4 Select one or more fibers from the Physical Fibers/Cable Link List list and click Create Fiber/
Cable.
NOTE
l When one or more fibers are selected from the Physical Fibers/Cable Link List list, the fibers that
conflict with the selected fibers are automatically displayed in the Logical Fibers/Cable Link List
list. If there is any conflicting fiber, refer to Step 5 and delete the conflicting fiber before creating fibers.
l During the fiber creation, if all the selected fibers are in Already created state, the system displays
the message No fiber to create.
Step 5 Select one or more conflicting fibers (namely, the fibers of which the Conflict with logical link
(Y/N) parameter is set to Yes in the Misconnected Fibers/Cable list) from the Logical Fibers/
Cable Link List list. Click Delete Fiber/Cable.
----End
2.4.2 Creating Fibers Manually

Before you configure services, you need to create the required fibers. You can create a small
number of fibers manually one after another.
Prerequisite
l The required boards must be created on each NE.
Procedure
Step 1 Right-click in the Main Topology and choose New > Link from the shortcut menu. Then, the
Create Link dialog box is displayed.
Step 2 Choose Fiber/Cable > Fiber from the left pane.
Step 3 The parameter Create Ways can be set to Common Ways or Batch Ways. The default value
is Common Ways.
Step 4 Click the button in Source NE. Select the source board and source port in the Select Fiber/
Cable Source dialog box that is displayed.

System
Step 5 Click OK.
Step 6 Click the button in Sink NE. Select the sink board and sink port in the Select Fiber/Cable
Sink dialog box that is displayed.
Step 7 Click OK. Then, the created fiber is displayed between the source NE and the sink NE in the
Main Topology.
Step 8 Right-click the created fiber and choose Detect Link from the shortcut menu. The Operation
Result dialog box is displayed, indicating the information on the fiber connections.
----End
2.4.3 Creating Virtual Fibers

When the U2000 manages the SDH, PTN, and WDM equipment at the same time, you can create
virtual fibers between the SDH or PTN equipment (with the WDM equipment in between), to
facilitate network management.
Prerequisite
l You must create fiber connections according to the true fibers that connect the SDH and
WDM or PTN equipment.
l In the case of SDH equipment, the virtual fibers ensure the automatic fiber search and SDH
trail management functions are independent of each other.
l The source and sink ports of the virtual fibers must be SDH ports. On the source and sink
ports, there must be two physical fibers that are connected to the WDM or PTN equipment.
l The virtual fibers do not support the expansion function.
Procedure
Step 1 Right-click in the blank area of the Main Topology, and choose New > Link from the shortcut
menu.
Step 2 In the Create Link dialog box, choose Fiber/Cable > Virtual Fiber.
Step 3 Set the fiber/cable attributes in the attribute list on the right.
Step 4 Click OK.
----End
2.4.4 Creating DCN Communication Cable

The U2000 can communicate with NEs through the Ethernet port or serial port. The NEs can
also communicate with each other through the extended ECC. Depending on the communication
mode, different types of communication cables can be created on the U2000.
Prerequisite
You must be an NM user with "NE operator" authority or higher.

System
Procedure
Step 1 Right-click in the blank area of the Main Topology and choose New > Link from the shortcut
menu. Then, the Create Link dialog box is displayed.
Step 2 Choose Fiber/Cable > Cable from the left pane.
Step 3 Enter the cable attributes in the panel on the right.
Step 4 Click OK. The cable that is already created between the U2000 and the gateway NE is displayed
on the Main Topology.
----End
2.5 Creating a Topology Subnet

To facilitate network management, you can assign the topology objects in the same network area
or with similar attributes into the same topology subnet.
Prerequisite
You must be an NM user with "NM operator" authority or higher.
A topology subnet is created only to simplify the user interface and does not affect the operation
of the NEs.
Procedure
Step 1 Right-click in the blank area of the Main Topology and choose New > Subnet from the shortcut
menu.
Step 2 Click the Property tab in the Create Physical Subnet dialog box. Set the attributes of the subnet.
Step 3 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects
column. Click to add the selected objects to the Selected Objects column.
NOTE
The information about the signs in a similar dialog box for selecting objects is
provided as follows:
l indicates adding the selected objects from the left column to the right column.
l indicates adding all the objects from the left column to the right column.
Step 4 Click OK.
----End
2.6 Configuring the Protection Subnet

The OptiX OSN equipment supports various network level protection schemes, including the
linear MSP.

System
2.6.1 Configuring a Non-Protection Chain

If the services on a chain do not need to be protected, you can configure the chain as a non-
protection chain. In this case, all the timeslots on the chain can be used to transmit the services.
2.6.2 Configuring a Non-Protection Ring
When services on a ring need not be protected, you can configure a non-protection (NP) ring.
All timeslots on the ring can be used to transmit services.
2.6.3 Creating an MS Ring Protection Subnet
Generally, the MS ring protection is configured on the public ring network whose protection
paths are used to transmit extra services. By running the APS protocol, it achieves the MS level
protection.
2.6.4 Creating a Linear MS Protection Subnet
In a chain network, an NE can protect the services in different fiber sections after a linear MS
protection subnet is created.
2.6.1 Configuring a Non-Protection Chain

If the services on a chain do not need to be protected, you can configure the chain as a non-
protection chain. In this case, all the timeslots on the chain can be used to transmit the services.
Prerequisite
l The data of each NE must be configured and the fibers must be created on the U2000.
l You must be an NM user with "network maintainer" authority or higher.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create Unprotected Chain from the Main Menu.
Then, the Create Protection Subnet dialog box is displayed.
Step 2 Enter the name of the protection subnet.

Generally, enter the default name, for example, NP_Chain_1.
Step 3 Select the capacity level of the protection subnet,

for example, STM-4.
Step 4 Optional: Select Resource Sharing and Assigned by VC4 as needed.

NOTE
l If multiple protection subnets uses one port of a board, you need to check the Resource Sharing check
box. If different protection subnets use different ports of a board, do not check this check box.
l Select the Assigned by VC4 option when there are different VC4s belonging to different protection
subnets to achieve virtual optical path protection.
Step 5 Select the NEs where you need to create the non-protection chain. Double-click the NEs in the
Main Topology and add them to the NE list on the left. At the same time, is displayed above
the NE icons. You can cancel the selection by double-clicking the NE icons again to cancel the
selection.
Step 6 Click Next. Set the parameters such as Physical Link Information.

System
Step 7 Click Finish to deliver the configuration data. Click Close in the Operation Result dialog box
indicating that the operation succeeded.
----End
2.6.2 Configuring a Non-Protection Ring

When services on a ring need not be protected, you can configure a non-protection (NP) ring.
All timeslots on the ring can be used to transmit services.
Prerequisite
l The NE data must be configured, and fibers must be created properly.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create Unprotected Ring from the Main Menu.
Then, the Create Protection Subnet dialog box is displayed.

Generally, the default name is used, for example, NP_Ring_1.
Step 3 Select the capacity level of the protection subnet,

for example, STM-4.
Step 4 Select Resource Sharing and Assigned by VC4 according to the requirement.
NOTE
l If multiple protection subnets uses one port of a board, you need to check the Resource Sharing check
box. If different protection subnets use different ports of a board, do not check this check box.
l Select the Assigned by VC4 option when there are different VC4s belonging to different protection
subnets to achieve virtual optical path protection.
Step 5 Select the nodes that belong to the protection subnet that needs to be created. Double-click the
selected NE in the Main Topology to add the NE to the NE list on the left. In addition, is
displayed on the NE icon. If you need to cancel the selection, double-click the NE again.
Step 6 Click Next. Set the parameters such as Physical Link Information in the window.
Step 7 Click Finish to deliver the configuration data. Then, click Close in the Operation Result dialog
box indicating that the operation succeeded.
----End
2.6.3 Creating an MS Ring Protection Subnet

Generally, the MS ring protection is configured on the public ring network whose protection
paths are used to transmit extra services. By running the APS protocol, it achieves the MS level
protection.
Prerequisite
l The NE data must be configured and fibers must be created properly.

System
Precautions
CAUTION
l The number of nodes in an MSP ring should not exceed 16.
l Starting the protocol controller may interrupt the services.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 2f_MS_SPRing from the Main Menu.
Click OK in the dialog box that is displayed. Then, the Create Protection Subnet window is
displayed.
NOTE
l To create a four-fiber bidirectional MS shared protection ring, choose Service > SDH Protection
Subnet > Create 4f_MS_SPRing from the Main Menu.
l To create a two-fiber bidirectional MS shared protection ring, choose Service > SDH Protection
Subnet > Create 2f_MS_DPRing from the Main Menu.
l The following part provides an example of configuring a common two-fiber bidirectional MS shared
protection ring.
Step 2 Enter the name of the protection subnet. Generally, the default name is used, for example,
2f_MS_SPRing_1.
Step 3 Select the capacity level of the protection subnet, for example, STM-4.
NOTE
Create a two-fiber bidirectional MSP ring. The capacity of the ring can be set to STM-4, STM-16.
Step 4 Choose Resource Sharing and Assigned by VC4 according to the requirement.

System
NOTE
l Resource Sharing indicates that a port is mapped into multiple protection subnets. When multiple
protection subnets occupy the same port of a board, Resource Sharing must be selected. When different
protection subnets occupy different ports of a board, Resource Sharing is not required. If multiple
protection subnets use one port of a board, you need to select the Resource Sharing check box. If
MSP Sharing is enabled, you can select the Resource Sharing check box to map a port of the board
to multiple MSP subnets.
l Assigned by VC4 indicates that different VC-4s belong to different protection subnets, therefore
achieving virtual optical path protection. For example, in the case of an STM-4 fiber, the first and
second VC-4s are allocated for the STM-4 MS shared protection, and the third and fourth VC-4s are
allocated for the non-protection.
NOTE
To facilitate maintenance, it is recommended that you add the nodes anticlockwise to the protection subnet.
Step 6 Set the attribute of each node to MSP Node.
Step 7 Click Next. Set the parameters such as Physical Link Information in the window.
NOTE
l If there are multiple fibers between two NEs, select the required links from the Physical Link
Information drop-down list.
l If Assigned by VC4 is selected, you can Select the working and protection VC-4 timeslots according
to the requirement.
Step 8 Click Finish to deliver the configuration data. Then, the Operation Result dialog box is
displayed. Click Close.
Step 9 Choose Service > SDH Protection Subnet > Search for SDH Protection Subnet from the
Main Menu. Select the created protection subnet, right-click and choose Protection Subnet
Attributes from the shortcut menu.
Step 10 Click the Protection Subnet Maintenance tab to check whether the protocol controller is
started. If the protocol controller is not started, select all the nodes of the protection subnet.
Right-click and choose Start/Stop Protocol > Start from the shortcut menu. Click Yes in the
dialog box that is displayed twice. Ensure that the status of all the values in the Protocol
Controller column is Protocol Started.
Step 11 Click the Protection Subnet Parameters tab. Set WTR time and SD Condition according to
the requirement. Click Apply to deliver the configuration data. The WTR time of all NEs in
the same protection subnet should be the same.
NOTE
The default value is 600s.
----End

System
2.6.4 Creating a Linear MS Protection Subnet

In a chain network, an NE can protect the services in different fiber sections after a linear MS
protection subnet is created.
Prerequisite
l The NE data must be configured and fibers must be created properly.
Precautions
CAUTION
l Starting the protocol controller may interrupt the services.
l Fibers that are used for the linear MSP cannot be used by other protection subnets. That is,
a linear MS protection subnet and other subnets cannot be used together to form virtual fibers.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 1+1 linear MSP from the Main Menu.
Then, the Create Protection Subnet window is displayed.
NOTE
To create the M:N linear MS protection, choose Service > SDH Protection Subnet > Create M:N Linear
MSP from the Main Menu. Then, the corresponding window is displayed.
In the case of the M:N linear MS protection scheme, set the number of working links to N. M indicates the
number of protection links and cannot be set manually. Currently, the value of M can be 1 only.

Generally, the default name is used, for example, 1+1_MSP_1.
Step 3 Select the capacity level of the protection subnet, for example, STM-4.

System
Step 4 Set Revertive Mode and Switching Mode according to the protection type and related
requirements.
NOTE
When setting the parameters, note the following points:

l Revertive Mode indicates the handling strategy that is used after the faulty line is recovered. Non-
Revertive: The service is not automatically reverted to the working channel after the faulty line is
recovered. Revertive: The service is automatically reverted to the working channel after the faulty line
is recovered.
l Switching Mode indicates the switching strategy that is used after a fault occurs in the line. Single-
ended switching: To protect services, a switching occurs at the receive end when the receive end is
faulty and a switching occurs at the transmit end when the transmit end is faulty. Dual-ended
switching: To protect services, a switching occurs at the receive and transmit ends when the receive
end or transmit end is faulty.
Step 6 Click Next. Set Physical Link Information of Working Link and Protection Link.
Step 7 Click Finish to deliver the configuration data. Then, click Close in the Operation Result dialog
Step 8 Choose Service > SDH Protection Subnet > Search for SDH Protection Subnet from the
Main Menu. Select the created protection subnet, right-click and choose Protection Subnet
Attributes from the shortcut menu.
Step 9 Click the Protection Subnet Maintenance tab to check whether the protocol controller is
started.

System
NOTE
If the protocol controller is not started, select all the NEs of the protection subnet. Right-click and choose
Start/Stop Protocol > Start from the shortcut menu. Click Yes in the dialog box that is displayed twice.
Ensure that the status of all the values in the Protocol Controller column is Protocol Started.
Step 10 Click the Protection Subnet Parameters tab. Set WTR time and SD Condition according to
the requirement. Click Apply to deliver the configuration data.
NOTE
The WTR time of all NEs in the same protection subnet should be the same.
----End
2.7 Configuring Clocks

A clock is the basis for the normal operation of an NE. You need to configure the clocks for all
the NEs before configuring services. In addition, you need to configure the clock protection in
the case of a complicated network.
2.7.1 Configuring the NE Clock Source
Before configuring services, you must configure the NE clock source and specify the priority
level to ensure that correct clock trace relations are created for all the NEs on the network.
2.7.2 Configuring the Clock Source Protection
On a complicated clock network, you need to configure the clock protection for all the NEs.
After you set the clock source and specify the clock priority level for the NEs, you can enable
the standard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clock
source.
2.7.1 Configuring the NE Clock Source

Before configuring services, you must configure the NE clock source and specify the priority
level to ensure that correct clock trace relations are created for all the NEs on the network.
Prerequisite
To implement clock protection, you must configure at least two traceable clock sources for the
equipment. Generally, the tributary clock is not used as the clock source for the equipment.
After you set the clock sources for all the NEs, query the networkwide clock trace status again.
For details, see Querying the Clock Trace Status.

System
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Layer
Clock > Clock Source Priority from the Function Tree.
Step 2 Click Query to query the existing clock source.
Step 3 Click Create. In the Add Clock Source dialog box, select a new clock source and click OK.
Step 4 Optional: If an external clock source is selected, select External Clock Source Mode according
to the type of external clock signals. In the case of the 2 Mbit/s clock, specify the Synchronous
Status Byte to deliver the SSM message.
Step 5 Select a clock source and click or to adjust its priority level. The clock
sources are arranged in the descending order. The clock source at top is the preferred clock
source for the NE.
NOTE
Internal clock sources have the lowest priority because of their low precision.
Step 6 Click Apply. Then, click Close in the Operation Result dialog box indicating that the operation
succeeded.
NOTE
If the clock trace relation changes according to the change of the clock source, the Prompt dialog box is
displayed, asking you whether to refresh the clock trace relation. Click OK. If Disable Prompting Next
Time is selected, the Prompt dialog box is not displayed even if the clock trace relation changes.
----End
2.7.2 Configuring the Clock Source Protection

On a complicated clock network, you need to configure the clock protection for all the NEs.
After you set the clock source and specify the clock priority level for the NEs, you can enable
the standard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clock
source.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Layer
Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the Clock Subnet tab. Click Query to query the existing parameter settings.
Step 3 Select Start Standard SSM Protocol or Start Extended SSM Protocol.
NOTE
The same SSM protection protocol must be used for the NEs within the same clock protection subnet.
Step 4 Set the subnet number of the clock subnet to which the NE is associated.

System
NOTE
Allocate the same subnet number to the NEs that trace the same clock source.
Step 5 Optional: If the extended SSM protocol is enabled, set the clock ID of the clock source.
Step 6 Click Apply. Click Close in the Operation Result dialog box indicating that the operation
succeeded.
Step 7 Optional: If the clock ID is specified for the line clock of an NE, click the Clock ID Status tab,
and set Enabled Status to Enabled. Click Apply. Click Close in the Operation Result dialog
----End
2.8 Clock Configuration Parameters

A clock is one of the basic configuration items of an NE. When configuring a clock, you need
to set the parameters in terms of clock source, clock protection, clock quality, and retiming
management.
2.8.1 Managing External Clock Sources

To use an external clock as the clock source, you need to set the relevant parameters such as the
output mode, output timeslot, and output threshold of the external clock source.
2.8.2 Configuring Clock Protection and Restoration
You need to configure necessary protection for the clock so that the NE can be synchronized
normally.
2.8.3 Clock Quality and Status Management
You can manage the quality and status of a clock to ensure the stability and precision of the
clock source that is currently traced.
2.8.4 Retiming Management
This topic describes the parameters that are used for setting the retiming clock source and the
retiming mode.
2.8.1 Managing External Clock Sources

To use an external clock as the clock source, you need to set the relevant parameters such as the
output mode, output timeslot, and output threshold of the external clock source.
Table 2-3 lists the parameters that are used for configuring the output phase-locked source table
of an external clock.

System
Table 2-3 Parameters for configuring the output phase-locked source table of an external clock
Field Value Range Description
NE Name For example: NE(9-1001) Displays the name of the NE.
External Clock Output Mode Synchronization Quality The External Clock Output
When 2M Output Unavailable, Output AIS, Mode When 2M Output
Synchronous Source Is Shut off Synchronous Source Is
Invalid Default value: Shut off Invalidparameter is used to
specify an action to control
the output mode of external
clock source when all the
clock sources in the 2M
phase-locked source priority
table become invalid or when
the clock quality of the
selected source is inferior to
the output quality threshold
of external clock source.
You can click 7.112
External Clock Output
Mode When 2M Output
Synchronous Source Is
Invalid to display the
detailed information.
Output Impedance of For example: 120 ohms The NE can provide two
External Clock Source 1 clocks for external outputs.
You need to specify the
output impedance of external
clock 1.
Output Impedance of For example: 120 ohms The NE can provide two
External Clock Source 2 clocks for external outputs.
output impedance of external
clock 2.
Output Mode of External 2 Mbit/s, 2 MHz The NE can provide two

Clock Source 1 Default value: 2 Mbit/s clocks for external outputs.
output mode of external
clock 1.
Output Mode of External 2 Mbit/s, 2 MHz The NE can provide two

Clock Source 2 Default value: 2 Mbit/s clocks for external outputs.
output mode of external
clock 2.

System
Clock Source Threshold No Threshold Value, G.813 The Clock Source

SETS Signal, G.812 Lock Threshold parameter
Clock Signal, G.812 Transit indicates the lower quality
Clock Signal, G.811 Clock threshold of 2M external
Signal clock source. When the clock
Default value: No Threshold quality level of the external
Value clock source that is selected
from the 2M phase-locked
source priority table is
inferior to the threshold, the
2M phase-locked source
becomes invalid, and the
action specified for 2M
phase-locked source failure
is invoked to control the
external clock source output.
You can click 7.118 Clock
Source Threshold to display
the detailed information.
Table 2-4 lists the parameters that are used for configuring the 2M phase-locked source attributes
of an external clock.
Table 2-4 Parameters for configuring the 2M phase-locked source attributes of an external clock
2M Phase-Locked Source For example: NE Displays the number of the

Number (9-5595)-2M phase-locked external clock source output
source 1 of the NE.
External Clock Output Open, Close Specifies the output switch of

Switch the external clock source.
External Clock Output Mode 2 MHz, 2 Mbit/s The External Clock Output
Default value: 2 Mbit/s Mode parameter is used to
set the output mode of the
external clock source to 2
Mbit/s or 2 MHz.
You can click 7.113
Mode to display the detailed
information.

System
External Clock Output SA4, SA5, SA6, SA7, SA8, The External Clock Output
Timeslot All versions Timeslot parameter is used
Default value: All versions to set the output timeslot for
the S1 byte of the external
clock source. The external
clock source transmits the S1
overhead byte through
certain timeslots. After
starting the SSM protocol,
make sure that the timeslot
for receiving the S1 byte is
consistent with the timeslot
for transmitting the S1 byte
so that the S1 byte can be
received correctly.
You can click 7.114
Timeslot to display the
External Source Output Threshold Disabled, Not The External Source

Threshold Inferior to G.813 SETS Output Threshold
Signal, Not Inferior to G.812 parameter is used to set the
Local Clock Signal, Not output quality threshold of
Inferior to G.812 Transit the external clock source.
Clock Signal, Not Inferior to When the output quality of
G.811 Clock Signal the external clock source is
Default value: Threshold inferior to the threshold, the
Disabled action specified for 2M
phase-locked source failure
You can click 7.115
External Source Output
Threshold to display the
2M Phase-Locked Source No Failure Condition, AIS, The 2M Phase-Locked

Fail Condition LOF, AIS OR LOF Source Fail Condition
Default value: No Failure parameter is used to set the
Condition failure condition of the 2M
phase-locked source.
You can click 7.116 2M
Phase-Locked Source Fail
Condition to display the

System
2M Phase-Locked Source Shut Down Output, Send The 2M Phase-Locked

Fail Action AIS, 2M Output S1 Byte Source Fail Action
Unavailable parameter is used to specify
Default value: Shut Down the action to be invoked in the
Output case of 2M phase-locked
source failure. When the
reference clock signal for
locking external clock output
is invalid or inferior to the
threshold, the specific action
external clock output by
either shutting down the
output or inserting an AIS
alarm.
You can click 7.117 2M
Phase-Locked Source Fail
Action to display the detailed
information.
2.8.2 Configuring Clock Protection and Restoration

You need to configure necessary protection for the clock so that the NE can be synchronized
normally.
Table 2-5 lists the parameters that are used for configuring clock protection and restoration.
Table 2-5 Parameters used for configuring clock protection and restoration
Higher Priority Clock Source Non-Revertive, Auto- The Higher Priority Clock
Reversion Mode Revertive Source Reversion Mode
Default value: Auto- parameter specifies whether
Revertive to switch from the lower-
priority clock source back to
the higher-priority clock
source after the higher-
priority clock source is
restored to normal.
You can click 7.122 Higher
Priority Clock Source
Reversion Mode to display

System
Clock Source WTR Time 0-12 The Clock Source WTR

Default value: 5 Time parameter is used to
specify the wait-to-restore
(WTR) time when the
Higher Priority Clock
Source Reversion Mode
parameter is set to Auto-
Revertive. When a clock
source is restored to its valid
status, the system does not
regard it as a valid source
immediately but verifies the
validity of the clock source in
a specific period of time. The
system regards the clock
source as a valid source only
if the clock source remains
valid during the specific
period of time. This specific
period of time is called the
WTR time of the clock
source.
You can click 7.123 Clock
Source WTR Time to
display the detailed
information.
Clock Source For example: Internal Clock Displays the name of the
Source clock source.
AIS Alarm Generated Yes, No The AIS Alarm Generated

Default value: No parameter is used to specify
whether an AIS alarm is a
condition for triggering the
switching of clock sources.
You can click 7.119 AIS
Alarm Generated to display

System
B1 BER Threshold-Crossing Yes, No The B1 BER Threshold-

Generated Default value: No Crossing Generated
parameter is used to specify
whether a B1 BER threshold-
crossing alarm is a condition
for triggering clock source
switching. B1 BER
Threshold-Crossing alarm is
an index for measuring the
performance of clock source
signals.
You can click 7.120 B1 BER
Threshold-Crossing
Generated to display the
RLOS, RLOF and OOF Yes Displays whether the

Alarms Generated switching condition is
enabled. If the R_LOS,
R_LOF, or OOF alarm is
reported, the NE considers
that the corresponding clock
source is faulty.
By default, this parameter is
set to yes and cannot be
changed.
CV Threshold-Crossing Yes, No Sets the switching condition

Generated enable status. When CV
threshold-crossing occurs in
the NE, the NE thinks that the
corresponding clock source
fails.
CV Threshold - Displays the CV threshold.
B2-EXC Alarm Generated Yes, No The B2-EXC Alarm

Default value: No Generated parameter is used
to specify whether a B2-EXC
alarm is a condition for
triggering clock source
switching. B2-EXC alarm is
an index for measuring the
performance of clock source
signals.
You can click 7.121 B2-EXC
Alarm Generated to display

System
Effective Status Valid, Invalid Specifies whether the clock

source is valid. This
parameter is used for query
only.
Lock Status Lock, Unlock The Lock Status parameter

Default value: Unlock indicates the lock status of a
clock source in the priority
table.
You can click 7.124 Lock
Status to display the detailed
information.
Switching Source For example: 1-SL1D-1 Displays the clock source to

(SDH-1) be traced by the NE after the
switching.
Switching Status Forced Switching, Manual Displays the switching status

Switching, Normal of the current clock source.
2.8.3 Clock Quality and Status Management

You can manage the quality and status of a clock to ensure the stability and precision of the
clock source that is currently traced.
Table 2-6 lists the parameters that are used for managing the quality and status of a clock.
Table 2-6 Parameter description: clock synchronization status

NE Clock Working Mode Normal Mode, Holdover The NE Clock Working

Mode, Free-Run Mode Mode parameter is used to
Default value: - set the current working mode
of the system clock to the
normal, holdover or free-run
mode.
You can click 7.127 NE
Clock Working Mode to
information.

System
S1 Byte Synchronization Synchronous Source The S1 Byte

Quality Information Unavailable, Quality Synchronization Quality
Unknown, G.811 Reference Information parameter
Clock, G.812 Transit Clock, indicates the synchronization
G.812 Local Clock, SDH quality information in the S1
equipment timing source byte that is output by the
(SETS) signal current traced synchronous
Default value: - source. The S1 byte defined
by the ITUT is used to
transmit the quality
information about the clock
sources. It indicates the
quality information of 16
types of synchronous sources
with bits 5-8 of the S1 byte in
the section overhead. With
this quality information and
certain switching protocols,
the automatic protection
switching of the
synchronization clock can be
realized in the synchronous
network.
You can click 7.126 S1 Byte
Synchronization Quality
Information to display the
S1 Byte Clock Synchronous For example: Internal Clock Displays the clock source
Source Source that is traced by the clock of
the current NE. This
parameter is used for query
only.
The relevant information can
be displayed only when the
S1 byte is used. That is, the
clock protection function is
enabled. Similarly, the
relevant information can be
displayed only when you
click Query. Otherwise, only
NA is displayed.

System
Synchronous Source For example: External Clock The Synchronous Source

Source1 parameter indicates the
Clock Source in System synchronous clock source
Clock Priority Table that is being traced. The
synchronous clock source
Default value: None here refers to a certain clock
source contained in the
system clock priority table.
You can click 7.125
Synchronous Source to
information.
Data Output Method in Normal Data Output Mode, The Data Output Method in
Holdover Mode Keep the Latest Data Holdover Mode parameter is
Default value: Normal Data used to specify whether the
Output Mode data is output normally or the
latest data is kept when the
NE clock is in the holdover
mode.
You can click 7.128 Data
Output Method in
Holdover Mode to display
2.8.4 Retiming Management

This topic describes the parameters that are used for setting the retiming clock source and the
retiming mode.
Table 2-7 lists the parameters that are used for retiming.
Table 2-7 Parameters used for retiming

Retiming Mode Normal, Retiming Mode of The Retiming Mode

Tributary Clock, Retiming parameter specifies whether
Mode of Cross-Connect the retiming clock, tributary
Clock clock, or cross-connect
Default value: Normal (external) clock is used.
NOTE You can click 7.129
For the OptiX OSN equipment, Retiming Mode to display
this parameter can be set to only
Retiming Mode of Tributary
Clock.

System
2.9 Configuring the Orderwire Phone

The orderwire phone provides an important communication tool for maintenance personnel.
2.9.1 Configuring the Orderwire
The orderwire provides a dedicated communication channel that the network maintenance
personnel can use in the case of emergencies. You can configure the orderwire after configuring
the NEs and boards on the U2000.
2.9.2 Configuring the Conference Calls
The conference calls ensure one or more dedicated communication channels that the network
maintenance personnel can use in the case of emergencies.
2.9.1 Configuring the Orderwire

The orderwire provides a dedicated communication channel that the network maintenance
personnel can use in the case of emergencies. You can configure the orderwire after configuring
the NEs and boards on the U2000.
Prerequisite
You must be an NM user with "network operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE, and then choose Configuration > Orderwire from the
Function Tree. Click the General tab.

System
Step 2 Click Query to query the related NE-side information.

Step 3 Set Call Waiting Time(s), Telephone No. and the orderwire ports.
NOTE
l Call Waiting Time should be set to the same value for all NEs that are involved in the orderwire
communication. When the number of NEs is less than 30, set Call Waiting Time to 5s. Otherwise, set
Call Waiting Time to 9s.
l The orderwire phone numbers must be unique to each other in the same orderwire subnet.
l Set the length of the telephone number according to the actual requirements. The maximum length is
eight digits and the minimum length is three digits. In the same orderwire subnet, the number lengths
of the orderwire phone numbers must be the same.
l The length of the telephone number must be the same as the length of the conference call number.
l If the length of the subnet number is 1, the first digits of the two orderwire numbers must be the same.
If the length of the subnet number is 2, the first two digits of the two orderwire numbers must be the
same.
Step 4 Click Apply. A dialog box is displayed, indicating that the operation is successful.
Step 5 Click Close.
----End
2.9.2 Configuring the Conference Calls

The conference calls ensure one or more dedicated communication channels that the network
maintenance personnel can use in the case of emergencies.
Prerequisite
You must be an NM user with "network operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select the NE, and then choose Configuration > Orderwire from the
Function Tree. Click the Conference Call tab.
Step 2 Click Query to query the conference call configuration of the NE.
Step 3 Set Conference Call Authorities to Able to Listen and Speak or Able to Listen but not
Speak.

System
Step 4 In the Available Conference Call Port pane, select the port where you need to configure a
conference call, and click .
NOTE
If the optical interfaces that support conference calls form a loop, howler tone is generated. Hence,
"releasing loop" is required, that is, only one optical port can be set for the conference calls on a certain
node.
Step 5 Click Apply. A dialog box is displayed, indicating that the operation is successful.
Step 6 Click Close.
Step 7 Click the General tab. Set the Conference Call number.
NOTE
The conference call numbers for all the NEs must be the same, and must have the same length as the
corresponding orderwire phone numbers. If the orderwire phone number has four digits, it is recommended
that you set the conference call number to 9999.
Step 8 Click Apply.
----End
Example
You can follow the sample configuration to prevent a conference call loop.

System
NM ID U2000
NM name NM
IP address 192.9.0.54
2-SL4D-1 2-SL4D-2
9-1
NE1
1001/9999
2-SL4D-2 2-SL4D-1
9-2 9-4 1-SL1D-1 1-SL1D-1 9-5
NE2 Two-fiber bidirectional
NE4 NE5
1002/9999
MSP ring
1004/9999 1005/9999
2-SL4D-1 Two-fiber
2-SL4D-2 bidirectional
9-3
NE3
1003/9999
NE ID
NE name
2-SL4D-2 2-SL4D-1
Telephone No./
Conference Call No.
As shown in the preceding figure, if conference calls are configured for all optical interfaces,
howler tone is generated. You can configure a conference call for the optical interface NE3-2-
SL4D-2 only, instead of the optical interface NE3-2-SL4D-1.
2.10 Configuring the Broadcast Data Service

To meet the requirements for the broadcast data services between the monitoring host and the
environment monitors, you need to configure the broadcast data services of NE1-NE4.
Prerequisite
l The 2 Creating the Network task must be completed.

l Understand the signal flow and timeslot allocation.
Precautions
CAUTION
When you configure the broadcast data ports, ensure that the broadcast data ports do not form
a loop. Certain optical ports cannot be configured as the broadcast data ports.
Procedure
Step 1 Select NE in the NE Explorer, and then choose Configuration > Orderwire from the Function
Tree.
Step 2 Click the Broadcast Data Port tab and set the parameters as listed in the following table. Then,
click Apply. For the values of specified parameters, see 2.12.3 Configuring Broadcast Data
Interfaces.

System
Step 3 See Setting Network-Wide Performance Monitoring and enable the performance monitoring
function of the NEs.
Step 4 Back up the configuration data of the NEs. For details, see Backing Up the NE Data to the System
Control Board.
----End
2.11 Configuring the F1 Data Service

The F1 data service is transparently transmitted in the point-to-point mode by using the F1 byte.
Prerequisite
l The 2 Creating the Network is completed.
l Understand the signal flow and timeslot allocation.
Procedure
Step 1 In the NE Explorer, select NE1 and choose Configuration > Orderwire from the Function Tree.
Step 2 Click the F1 Data Port tab. After setting the parameters, click Apply. For the principles of
setting the parameters, see 2.12.2 Configuring F1 Data Interfaces.
Step 3 Enable the performance monitoring function of the NEs. For details, see Setting Performance
Monitoring Parameters of an NE.
Step 4 Back up the configuration data of the NEs. For details, see Backing Up the NE Database to the
SCB Board.
----End
2.12 Orderwire Configuration Parameters

The equipment supports various orderwire management, which involves orderwire phones and
F1 data interfaces.
2.12.1 Configuring Orderwire Phones

This topic describes the parameters that are used for configuring orderwire phones.
2.12.2 Configuring F1 Data Interfaces
This topic describes the parameters that are used for configuring F1 data interfaces.
2.12.3 Configuring Broadcast Data Interfaces
This topic describes the parameters that are used for configuring broadcast data interfaces.
2.12.1 Configuring Orderwire Phones

This topic describes the parameters that are used for configuring orderwire phones.
Table 2-8 lists the parameters that are used for configuring orderwire phones.

System
Table 2-8 Parameters for configuring orderwire phones

Call Waiting Time(s) 1-9 The Call Waiting Time(s)

Default value: 9 parameter specifies the
timeout period of searching
an orderwire route. If the
period of searching an
orderwire route exceeds the
specified value, the
orderwire phone changes to
the busy tone status.
You can click 7.102 Call
Waiting Time(s) to display
Dialing Mode Pulse, Dual-Tone Frequency Displays the dialing mode of

Default: Dual-Tone the orderwire phone.
Frequency
Conference Call 100-99999999 The Conference Call

Default value: 999 parameter specifies the
phone numbers of
networkwide orderwire calls.
You can click 7.103
Conference Call to display
Phone 1, Phone 2, Phone 3 100-99999999 The Phone parameter

NOTE specifies the phone numbers
OptiX OSN 550 equipment of orderwire addressing calls.
only supports Phone 1. An addressing call refers to a
point-to-point call.
Specifies the phone numbers
of up to three orderwire
phones supported by the
overheads. Certain
equipment supports one
orderwire phone only. In this
case, phones 2 and 3 are not
required. If the value is null,
the delivered configuration
does not indicate that the
corresponding data on the NE
side needs to be cleared, but
indicates that the
corresponding data on the NE
side is not changed.
You can click 7.104 Phone to
information.

System
Selected Orderwire Port Slot ID-Board Name-Port Specifies the port on the line
No.(Port Name) board for orderwire phone
transmission.
Available Orderwire Port Available Orderwire Port The Available Orderwire

Default value: Bid-BidType- Port parameter specifies
PortID whether the optical interface
is used to make orderwire
calls.
You can click 7.105
Available Orderwire Port
to display the detailed
information.
2.12.2 Configuring F1 Data Interfaces

This topic describes the parameters that are used for configuring F1 data interfaces.
Table 2-9 list the parameters that are used for configuring F1 data interfaces.
Table 2-9 Parameters for configuring F1 data interfaces

No. 1-88 The No. (F1 Data Port)

parameter specifies the
numbers of the F1 data ports
that have the same direction.
You can click 7.106 No.(F1
Data Port) to display the
Data Channel 1 - The Data Channel (F1 Data

Port) parameter specifies the
uplink and downlink ports
that pass through the F1
data. displays pass-through
channel 1, namely, the source
port of the data services at the
local station.
Channel (F1 Data Port) to
information.

System
Data Channel 2 - The Data Channel (F1 Data

Port) parameter specifies the
uplink and downlink ports
that pass through the F1
data. displays pass-through
channel 2, namely, the sink
port of the data services at the
local station.
Channel (F1 Data Port) to
information.
Available Data Channel - Displays all the available

data interfaces or optical
interfaces.
2.12.3 Configuring Broadcast Data Interfaces

This topic describes the parameters that are used for configuring broadcast data interfaces.
Table 2-10 list the parameters that are used for configuring broadcast data interfaces.
Table 2-10 Parameters for configuring broadcast data interfaces

Overhead Byte SERIAL1, SERIAL2, The Overhead Byte

SERIAL3, SERIAL4 (Broadcast Data Port)
Default value: SERIAL1 parameter specifies the
number of the overhead
bytes, which are used to
transmit orderwire broadcast
data services, in the SDH
frame header.
You can click 7.108
Overhead Byte (Broadcast

System
Working Mode RS232 The Working Mode

Default value: RS232 (Broadcast Data Port)
working mode of the local
interface at which broadcast
data services are added or
dropped.
You can click 7.109
Working Mode (Broadcast
Broadcast Data Source No Data, SERIALx, Bid- The Broadcast Data Source
BidType-PortID (Broadcast Data Port)
Default value: - parameter specifies the
source of the orderwire
broadcast data service.
You can click 7.110
Broadcast Data Source
(Broadcast Data Port) to
information.
Broadcast Data Sink SERIALx, Bid-BidType- The Broadcast Data Sink

PortID (Broadcast Data Port)
Default value: - parameter specifies the sink
of the orderwire broadcast
data service.
You can click 7.111
Broadcast Data Sink
(Broadcast Data Port) to
information.

System
Configuration Guide 3 Configuring SDH Services
3 Configuring SDH Services
About This Chapter
This topic uses an example to describe how to configure SDH services on the U2000.
3.1 Basic Concepts

The following basic concepts help you understand and configure the relevant SDH services
correctly.
3.2 Configuring Services on the Non-Protection Chain
Configure the protection subnet and the services on the non-protection chain separately. It is
recommended that you configure the protection subnet before configuring the services on the
non-protection chain.
3.3 Configuring Services on the Non-Protection Ring
Configure the protection subnet and the services on the non-protection ring separately. It is
recommended that you configure the protection subnet before configuring services on the non-
protection ring.
3.4 Configuring 1+1 Linear MSP Services
In the case of the 1+1 linear multiplex section protection (MSP), services are transmitted on the
working path and protection path at the same time. The sink NE selects the services from the
working path in normal cases, and selects services from the protection path when the working
path becomes faulty.
3.5 Configuring 1:1 Linear MSP Services
In the case of the 1:1 linear MSP, services are transmitted on the working path and the sink NE
receives the services from the working path in normal cases. When the working path becomes
faulty, the services are switched to the protection path for transmission and the sink NE receives
the services from the protection path.
3.6 Configuring Two-Fiber Unidirectional MSP Services
The two-fiber unidirectional MSP services can provide network level protection for the services
on NEs on the MSP ring. On the U2000, you can add all the NEs on the MSP ring into the
protection subnet to create a two-fiber unidirectional MSP ring.
3.7 Configuring the Two-Fiber Bidirectional MSP Services
To configure the two-fiber bidirectional MSP services, you need to create the MSP subnet
protection and MSP services separately. There is no requirement for the configuration sequence.

System
3 Configuring SDH Services Configuration Guide
3.8 Configuring Services on the SNCP Ring

Compared with the services on an MSP ring, the services on an SNCP ring have dedicated
physical paths as the protection paths. In addition, the services on an SNCP ring are dually fed
and selectively received. When you configure services on an SNCP ring, you need not configure
the protection subnet and the services separately. When you configure services on an SNCP ring,
however, you need to configure the working services and protection services separately.
3.9 Configuring Services on the SNCP Ring with a Non-Protection Chain
To configure the services on the SNCP ring, you can directly configure the working service and
protection service, without first configuring the protection subnet. To configure the services on
the non-protection chain, you can configure the services only after the protection subnet is
created.
3.10 Configuring Service on the MSP Ring with a Non-Protection Chain
Configure the protection subnet for the MSP, Protection Subnet for the non-protection chain,
and services on the MSP ring with a non-protection chain separately. It is recommended that
you configure the protection subnets before configuring the services on the MSP ring with a
non-protection ring chain.
3.11 Protection Configuration Parameters
You need to set the necessary parameters when configuring the protection such as MSP, SNCP
for an NE.

System
3.1 Basic Concepts

The following basic concepts help you understand and configure the relevant SDH services
correctly.
Unidirectional Service
The unidirectional service indicates the service that is received and transmitted on different
paths. A unidirectional service created between NE A and NE B can only be transmitted from
NE A (source) to NE B (sink) or only be transmitted from NE B (sink) to NE A (source).
Bidirectional Service
The bidirectional service indicates the service that is received and transmitted on the same path.
A bidirectional service created between NE A and NE B can be transmitted and received from
NE A to NE B or from NE B to NE A.
MSP
The multiplex section protection (MSP) provides a function that switches the signals from the
working section to the protection section.
Shared MSP Ring

As an SDH ring structure, the shared MSP protection ring provides the working and protection
paths for each node in the ring network. When the service in the working path is abnormal or
interrupted, the service is automatically switched to the protection path for further transmission.
In this case, the service loss can be avoided.
Two-Fiber Shared MSP Ring

To form a two-fiber shared MSP ring, you need to use two fibers. In each fiber, one half of
channels are used as working timeslots, and the other half of channels are used as protection
timeslots. For example, in the case of an STM-4 service, VC-4s numbered 1 to 2 are used as
working timeslots and VC-4s numbered 3 to 4 are used as protection timeslots. When VC-4s
numbered 1 to 2 is abnormal or faulty, the service is switched to the corresponding protection
timeslots 3 to 4 for further transmission.
SNCP Principle
The sub-network connection protection (SNCP) is defined by the ITU-T Recommendations.
With 1+1 single-ended switching function, the SNCP is used for protecting services that travel
across different subnets. The SNCP is characterized by the dual-fed and selective-receiving
mode.
Principles for Generating SNCP Services

The SNCP is characterized by the dual-fed and selective receiving mode. Thus, to configure the
SNCP service, you should configure the dual-fed service and the selective receiving service. On
the U2000, the service can be automatically created. When the selective receiving service is
configured on the U2000, the dual-fed service of the NE can be automatically created. Thus,

System
you only need to configure the selective receiving service in actual service configuration. That
is, if the SNCP service pair is configured, the service configuration of the SNCP is complete.
3.2 Configuring Services on the Non-Protection Chain

Configure the protection subnet and the services on the non-protection chain separately. It is
recommended that you configure the protection subnet before configuring the services on the
non-protection chain.
3.2.1 Networking Diagram

You can configure a non-protection chain if the services on the chain need not be protected. In
this case, all the timeslots on the chain can carry services.
3.2.2 Signal Flow and Timeslot Allocation
To configure services on the non-protection chain, you need to plan the traffic direction and
timeslot allocation for the services on the non-protection chain.
3.2.3 Per-NE Configuration Procedure
The configuration of services on the non-protection chain is not related to the configuration of
the protection subnet. To configure the services on the non-protection chain, configure the SDH
services from the tributary board to the line board on the source and sink NEs if the protection
subnet is already created.
3.2.4 End-to-End Configuration Process
The configuration of services on a non-protection chain is independent of the creation of the
protection subnet. To configure the services on the non-protection chain, configure the SDH

You can configure a non-protection chain if the services on the chain need not be protected. In
this case, all the timeslots on the chain can carry services.
Figure 3-1 shows a point-to-point non-protection chain. In this example, the SP3D boards are
configured on the source NE (NE1) and the sink NE (NE2) as tributary boards to add and drop
services, and the SL1D boards are used as line boards to transmit SDH services.
Figure 3-1 Networking diagram of the non-protection chain

1-SL1D-1 1-SL1D-1
NE 1 NE 2
Tributary board Line board Line board Tributary board
3-SP3D 1-SL1D 1-SL1D 3-SP3D

System

To configure services on the non-protection chain, you need to plan the traffic direction and
timeslot allocation for the services on the non-protection chain.
Figure 3-2 shows the signal flow and timeslot allocation. In this example, five E1 services are
added to or dropped from NE1 and NE2.
Figure 3-2 Signal flow and timeslot allocation of the services on the non-protection chain
3-SP3D 1-SL1D-1 1-SL1D-1 3-SP3D
线路
5×E1 板 5×E1
VC4-1:1-
NE1 5(VC12) NE2
Tributary board Line board Line board Tributary board

3-SP3D 1-SL1D 1-SL1D 3-SP3D
Line Board
Tributary Board
Traffic direction of the non-protection chain
3.2.3 Per-NE Configuration Procedure

The configuration of services on the non-protection chain is not related to the configuration of
the protection subnet. To configure the services on the non-protection chain, configure the SDH
Prerequisite
l The physical topology of the network must be created.
l The NEs, boards, and fibers must be created on the U2000.
l The created protection subnet must be consistent with the actual network topology. For
details about how to create the protection subnet, see 2.6.1 Configuring a Non-Protection
Chain.
l You must be familiar with the information about 3.2.2 Signal Flow and Timeslot
Allocation.
Procedure
Step 1 Configure SDH services on the source NE (NE1).
1. Select NE1 in the NE Explorer, and then choose Configuration > SDH Service
Configuration from the Function Tree.
2. Click Create on the lower-right pane to display the Create SDH Service dialog box. Set
the parameters that are required, and then click OK,

System
Parameter Value in Description

This
Example
Level VC12 In this example, E1 services are configured. Hence,

Level of the E1 services is set to VC12.
Direction Bidirectiona In this example, the services are transmitted and

l received over the same path. That is, the services are
Bidirectional services.
Source Slot 3-SP3D In this example, the SP3D board in slot 3 of NE1 is
configured as the source tributary board. See Figure
3-2.
Source VC4 - -
Source 1-5 In this example, five E1 services are configured

Timeslot Range between NE1 and NE2. Hence, the service source
(e.g.1,3-6) occupies VC-12s 1-5.
Sink Slot 1-SL1D-1 In this example, the SL1D board in slot 1 of NE1 is
(SDH-1) configured as the sink line board. See Figure 3-2.
Sink VC4 VC4-1 The service sink uses the timeslots of VC4-1.
Sink Timeslot 1-5 In this example, five E1 services are configured

Range(e.g. between NE 1 and NE2. Hence, the service sink
1,3-6) occupies VC-12s 1-5.
Activate Yes -
Immediately
Step 2 Refer to Step 1 and configure SDH services on the sink NE (NE2). Set the parameters as follows.
This
Example

Direction Bidirectional In this example, the services are transmitted and received
over the same path. That is, the services are
3-2.
Source VC4 - -
Source Timeslot 1-5 In this example, five E1 services are configured between
Range(e.g.1,3-6) NE1 and NE2. Hence, the service source occupies
VC-12s 1-5.

System

This
Example
Sink Timeslot 1-5 In this example, five E1 services are configured between
Range(e.g.1,3-6) NE1 and NE2. Hence, the service sink occupies VC-12s
1-5.
Activate Yes -
Immediately
Step 3 Check whether the services are configured correctly. For details, see Verifying the Correctness
of the SDH Service Configuration.
SCB Board.
----End
Relevant Task
If the services are configured incorrectly and need to be deleted, see Deleting SDH Services.

The configuration of services on a non-protection chain is independent of the creation of the
protection subnet. To configure the services on the non-protection chain, configure the SDH
Prerequisite
l The physical network topology must be set up.
l The NEs, boards, and fibers must be successfully created on the U2000.
l The protection subnet must be created and must be the same as the actual topology. For
Chain.
l The operator must understand the information provided in 3.2.2 Signal Flow and Timeslot
Allocation.
Procedure
Step 1 Choose Service > SDH Trail > Create SDH Trail from the Main Menu.
Step 2 Create the VC-4 service-layer trail.

System
1. Configure the parameters as follows. Set Level to VC4 Server Trail. The other parameters
take default values.
2. Double-click the source NE (NE1) and sink NE (NE2) on the right of the main topology
and click Apply. Then, click Close in the Operation Result dialog box indicating that the
operation succeeded.
3. Optional: In the Operation Result dialog box indicating that the operation succeeded,
click Browse Trail to query the created VC4 service-layer trail.
Step 3 Create VC12 services.

1. In Create SDH Tail, configure the parameters as follows. Set Level to VC12. The other
parameters take default values.
2. Double-click the source NE on the right of the main topology. The Select Board Port-
Source dialog box is displayed. Select the required PDH board and Tributary Port. Click
OK.
3. Double-click the sink NE (NE2) on the right of the main topology. Configure NE2 in the
same manner.
4. Select Copy after Creation and click Apply. Click Close in the Operation Result dialog
box indicating that the operation succeeded. Then, the Copy dialog box is displayed.
5. In Available Timeslots/Port, select the ports from NE1-Slot3-SP3D-2(SDH_TU-2) to
NE2-Slot3-SP3D-5(SDH_TU-5), and click Add.
6. In the Operation Result dialog box indicating that the operation succeeded, click Close.
click Browse Trail to query the created VC12 services.
Step 4 Check whether the service configuration is correct. For details, see Verifying the Correctness
SCB Board.
----End

System
Relevant Task
If the services are configured incorrectly and thus need to be deleted, see Deleting SDH Services.
3.3 Configuring Services on the Non-Protection Ring

Configure the protection subnet and the services on the non-protection ring separately. It is
recommended that you configure the protection subnet before configuring services on the non-
protection ring.

You can configure a non-protection ring if the services on the ring need not be protected. In this
case, all the timeslots on the ring can carry services.
To configure services on the non-protection ring, you need to plan the traffic direction and
timeslot allocation for the services on the non-protection ring.
3.3.3 Per-NE Configuration Process
The configuration of the services on the non-protection ring is not related to the configuration
of the protection subnet. To configure the services on the non-protection ring, configure the SDH
services from the tributary board to the line board on the source and sink NEs and the pass-
through services on the intermediate NEs if the protection subnet is already created.

You can configure a non-protection ring if the services on the ring need not be protected. In this
case, all the timeslots on the ring can carry services.
Figure 3-3 shows a non-protection ring consisting of four pieces of equipment. In this example,
the SP3D boards are used on the source NE (NE1) and the sink NE (NE3) as tributary boards
to add and drop services, and the SL1D boards are used as line boards to transmit SDH services.
Figure 3-3 Networking diagram of the non-protection ring

NE1:
3-SP3D
Tributary board Line board
1-SL1D-1 3-SP3D 1-SL1D-1
NE1
1-SL1D-2
Two-fiber bidirectional
NE2 NE4
non-protection ring
NE2: 1-SL1D-1
NE3
Line board Line board
1-SL1D-2 1-SL1D-1
NE3:
1-SL1D-2
3-SP3D 3-SP3D 1-SL1D-2

System

To configure services on the non-protection ring, you need to plan the traffic direction and
timeslot allocation for the services on the non-protection ring.
Figure 3-4 shows the signal flow and timeslot allocation. In this example, five E1 services are
added to or dropped from NE1 and NE3, and they pass through NE2.
Figure 3-4 Signal flow and timeslot allocation of the services on the non-protection ring
5×E1
VC4-1:1-5(VC12) 3-SP3D NE1:
3-SP3D 1-SL1D-1
1-SL1D-1
NE1
1-SL1D-2
VC4-1:1-5(VC12)
Two-fiber bidirectional 线路板
Pass-through service NE2 NE4
non-protection ring
1-SL1D-1
NE2:
1-SL1D-2 1-SL1D-1 NE3
NE3:
1-SL1D-2
VC4-1:1-5(VC12) 3-SP3D 3-SP3D 1-SL1D-2
Traffic 5×E1
Line board
direction
Tributary board

Prerequisite
Ring.
Allocation.

System
Procedure
Step 1 Configure SDH services of the source NE (NE1).
the parameters that are required, and then click OK.
This
Example

Direction Bidirectiona In this example, the services are transmitted and received
l over the same path. That is, the services are
3-4.
Source VC4 - -
Source 1-5 In this example, five E1 services are configured between

Timeslot NE1 and NE3. Hence, the service source occupies
Range(e.g. VC-12s 1-5.
1,3-6)
Sink VC4 VC4-1 The timeslots where the service sink is located belong
to the first VC-4 (VC4-1).
Sink 1-5 In this example, five E1 services are configured between

Timeslot NE1 and NE2. Hence, the service sink occupies VC-12s
Range(e.g. 1-5.
1,3-6)
Activate Yes -
Immediately
Step 2 Configure SDH services on the sink NE (NE3). Refer to Step 1. Set the parameters as follows.
This
Example
Level VC12 In this example, E1 services are configured. Hence, Level

of the E1 services is set to VC12.

System

This
Example
over the same path. That is, the services are Bidirectional
services.
configured as the source tributary board. See Figure 3-4.
Source VC4 - -

Timeslot NE1 and NE3. Hence, the service source occupies VC-12s
Range(e.g. 1-5.
1,3-6)
Range(e.g. NE1 and NE3. Hence, the service sink occupies VC-12s
1,3-6) 1-5.
Activate Yes -
Immediately
Step 3 Configure pass-through services on NE2.

This
Example

l over the same path. That is, the services are
Source Slot 1-SL1D-2 In this example, the SL1D board in slot 1 of NE2 is
(SDH-2) configured as the source line board. See Figure 3-4.
Source VC4 VC4-1 The timeslots where the service source is located belong
to the first VC-4 (VC4-1).

System

This
Example

1,3-6)

1,3-6)
Activate Yes -
Immediately
SCB Board.
----End
Relevant Task

Prerequisite
Ring.
Allocation.

System
Procedure

and click Apply. In the Operation Result dialog box that is displayed, click Close.
3. Optional: In the Operation Result dialog box that is displayed, you can also click Browse
Trail to query the created VC4 service-layer trail.

1. In Create SDH Tail, configure the parameters as follows. Set Level to VC12 and set
Direction to Bidirectional. The other parameters take default values.
OK.
same manner.
4. Select Copy after Creation and click Apply. In the Operation Result dialog box that is
displayed, click Close. Then, the Copy dialog box is displayed.
6. In the Operation Result dialog box that is displayed, click Close.
Trail to query the created VC12 services.

System
SCB Board.
----End
Relevant Task
3.4 Configuring 1+1 Linear MSP Services

In the case of the 1+1 linear multiplex section protection (MSP), services are transmitted on the
working path and protection path at the same time. The sink NE selects the services from the
working path in normal cases, and selects services from the protection path when the working
path becomes faulty.

The networking diagram of the point-to-point 1+1 linear MSP services is simple. Two NEs are
connected with two pairs of optical fibers.
To configure the 1+1 linear MSP services, you can configure the services that need to be added
to the source NE and dropped from the sink NE if the 1+1 linear MSP is already created.
This topic describes how to configure the 1+1 linear MSP services.

The networking diagram of the point-to-point 1+1 linear MSP services is simple. Two NEs are
As shown in Figure 3-5, the SP3D boards are used on NE1 and NE2 as tributary boards to add
and drop services, and the SL1D boards are used as line boards to transmit SDH services.
Figure 3-5 Networking diagram of the 1+1 linear MSP services

1-SL1D-1 1-SL1D-1
1-SL1D-2 1-SL1D-2
NE2 NE1
Tributary board Line board Line board Line board Line board Tributary board
3-SP3D 1-SL1D-1 1-SL1D-2 1-SL1D-2 1-SL1D-1 3-SP3D

To configure the 1+1 linear MSP services, you can configure the services that need to be added
to the source NE and dropped from the sink NE if the 1+1 linear MSP is already created.

System
As shown in Figure 3-6, the signal flow and timeslot allocation are as follows:
l Traffic direction from NE1 to NE2: NE1→NE2
Services are added to the source NE (NE1) and are transmitted to the working path and
protection path at the same time. Then, the services are dropped from the sink NE (NE2),
which selects the services from the working path.
Services are added to the source NE (NE2) and are transmitted on the working path and
l The services between NE 1 and NE2 occupy VC-12s 1-5 of VC4-1 (VC4-1:VC-12:1-5) on
the SDH link between NE1 and NE2. The capacity of the services is 5xE1.
When the working path from NE1 to NE2 becomes faulty, in the case of single-ended switching,
the signal flow is as follows:
which selects the services from the protection path.
l The services from NE2 to NE1 are not affected, and the traffic direction is NE2→NE1.
When the working path from NE1 to NE2 becomes faulty, in the case of dual-ended switching,
the signal flow is as follows:
Figure 3-6 Signal flow and timeslot allocation of the 1+1 linear MSP services
1-SL1D-1 1-SL1D-1
VC4-1:1-5(VC12) VC4-1:1-5(VC12)
5xE1 services are 5xE1 services are

added/dropped added/dropped
3-SP3D 3-SP3D
NE2 1-SL1D-2 1-SL1D-2 NE1

Traffic direction of
the working path Line board
the protection path Tributary board

System

Prerequisite
details about how to create the protection subnet, see 2.6.4 Creating a Linear MS
Protection Subnet.
Allocation.
Procedure
1. In the NE Explorer, select NE1 and then choose Configuration > SDH Service
This
Example

Direction Bidirectiona In this example, services are transmitted and received

l over the same path. That is, the services are bidirectional
services. Hence, Direction of the services is set to
Bidirectional.
Source Slot 3-SP3D In this example, the SP3D board in slot 3 is configured
as the source tributary board for the bidirectional
services from NE1 to NE2. See Figure 3-6.
Source VC4 - -
Source 1-5 The total capacity of the service is 5xE1 according to the
Timeslot plan. Hence, Source Timeslot Range(e.g.1,3-6) is set
Range(e.g. to 1-5.
1,3-6)
Sink Slot 1-SL1D-1 In this example, the SL1D board in slot 1 is configured
(SDH-1) as the sink line board. See Figure 3-6.
Sink VC4 VC4-1 In this example, the services require five VC-12s. Sink
VC4 is set to VC4-1, because a VC-4 contains 63
VC-12s.

System

This
Example
Sink 1-5 The total capacity of the services is 5xE1 according to

Timeslot the plan. Hence, Sink Timeslot Range(e.g.1,3-6) is set
Range(e.g. to 1-5.
1,3-6)
Activate Yes -
Immediately
Step 2 Configure SDH services on the sink NE (NE2).
Click , and select NE2 from the displayed NE Navigator. Configure NE2 in the same way
that NE1 is configured. Then, click OK.

This
Example

over the same path. That is, the services are bidirectional
Bidirectional.
Source Slot 1-SL1D-1 In this example, the SL1D board in slot 1 is configured as
(SDH-1) the source line board. See Figure 3-6.
Source VC4 VC4-1 In this example, the service requires five VC-12s. Source
VC4 is set to VC4-1, because a VC-4 contains 63 VC-12s.
Source 1-5 The total capacity of the services is 5xE1 according to the
Timeslot plan. Hence, Source Timeslot Range(e.g.1,3-6) is set to
Range(e.g. 1-5.
1,3-6)
Sink Slot 3-SP3D In this example, the SP3D board in slot 3 is configured as
the sink tributary board for the bidirectional services from
NE1 to NE2. See Figure 3-6.
Sink VC4 - -
Sink Timeslot 1-5 The total capacity of the services is 5xE1 according to the
Range(e.g. plan. Hence, Sink Timeslot Range(e.g.1,3-6) is set to 1-5.
1,3-6)
Activate Yes -
Immediately

System
SCB Board.
----End
Relevant Task

Prerequisite
Protection Subnet.
Allocation.
Procedure
and click Apply. In the Operation Result dialog box indicating that the operation
succeeded, click Close.
1. In Create SDH Trail, configure the parameters as follows. Set Level to VC12. The other

System
2. Double-click the source NE (NE1) on the right of the main topology. The Select Board
Port-Source dialog box is displayed. Select the required SP3D board and Tributary
Port. Click OK.
same manner.
4. Select Copy after Creation and click Apply. In the Operation Result dialog box
indicating that the operation succeeded, click Close. Then, the Copy dialog box is
displayed.
Step 4 Optional: Modify the parameters SD Condition, Revertive Mode, and Switching Mode for
the linear MSP.
NOTE
l The parameter settings of the sink NE must be the same as those of the source NE.
l When modifying Switching Mode,
l Ensure that the protection group is in a proper state.
l Ensure that the protection protocol is disabled.
1. Choose Service > SDH Protection Subnet > Maintenance SDH Protection Subnet from
the Main Menu to display the SDH Protection Subnet Common Attributes window.
2. Select the created linear MSP group. In the Protection Subnet Maintenance tab, select
all nodes, right-click and choose Start/Stop Protocol > Stop from the shortcut menu.
3. Click the Protection Subnet Parameters tab and modify the parameters SD Condition,
Revertive Mode, and Switching Mode.
4. Click Apply. Then, click Close in the Operation Result dialog box indicating that the
5. After the parameters are modified, restart the protection protocol according to Step 4.2.
SCB Board.
----End

System
Relevant Task
3.5 Configuring 1:1 Linear MSP Services

In the case of the 1:1 linear MSP, services are transmitted on the working path and the sink NE
receives the services from the working path in normal cases. When the working path becomes
faulty, the services are switched to the protection path for transmission and the sink NE receives
the services from the protection path.

The networking diagram of the point-to-point 1:1 linear LSP services is simple. Two NEs are
To configure the 1:1 linear MSP service, you can configure the services that need to be added
to the source NE and dropped from the sink NE if the 1:1 linear MSP is already created.
This topic describes how to configure the 1:1 linear MSP services.
This topic describes how to configure 1:1 linear MSP services in an end-to-end manner.

The networking diagram of the point-to-point 1:1 linear LSP services is simple. Two NEs are
and drop services, and the SL1D boards are used on NE1 and NE2 as line boards to transmit
SDH services.
Figure 3-7 Networking diagram of the 1:1 linear MSP services

1-SL1D-1 1-SL1D-1
1-SL1D-2 1-SL1D-2
NE2 NE1

To configure the 1:1 linear MSP service, you can configure the services that need to be added
to the source NE and dropped from the sink NE if the 1:1 linear MSP is already created.

System
Services are added to the source NE (NE1) and then are dropped from the sink NE (NE2).
The services are transmitted on the working path.
The services are transmitted on the working path.
l The services between NE1 and NE2 occupy VC-12s 1-5 of VC4-1 (VC4-1:VC-12:1-5) on
the SDH link between NE1 and NE2. The capacity of the services is 5xE1.
When the working path between NE1 and NE2 becomes faulty, the signal flow is as follows:
The services are transmitted on the protection path.
The services are transmitted on the protection path.
The difference between the 1:1 linear MSP service and the 1+1 linear MSP service is as follows:
l In the case of the 1+1 linear MSP service, services are transmitted on the working path and
protection path at the same time. The sink NE selects the services from the working path.
l In the case of the 1:1 linear MSP service, services are transmitted only on the working path.
Services are switched to the protection path for transmission only when the working path
becomes faulty.
Figure 3-8 Signal flow and timeslot allocation of the 1:1 linear MSP services
1-SL1D-1 1-SL1D-1
VC4-1:1-5(VC12) VC4-1:1-5(VC12)
5xE1 services are 5xE1 services are

added/dropped added/dropped
3-SP3D 3-SP3D
1-SL1D-2 1-SL1D-2
NE2 NE1
Line board
the working path

This topic describes how to configure the 1:1 linear MSP services.
Prerequisite

System
Protection Subnet.
Allocation.
Procedure

This
Example

Direction Bidirectiona In this example, services are transmitted and received on

l the same path. That is, the services are bidirectional
Bidirectional.
as the source tributary board for the bidirectional
Source VC4 - -
Source 1-5 The total capacity of the service is 5xE1 according to the
Timeslot plan. Hence, Source Timeslot Range(e.g.1,3-6) is set
Range(e.g. to 1-5.
1,3-6)
VC-12s.

Range(e.g. to 1-5.
1,3-6)
Activate Yes -
Immediately
Step 2 Configure SDH services on the sink NE (NE2).

System
Click , and select NE2 from the displayed NE Navigator. Click OK.

This
Example

on the same path. That is, the services are bidirectional
Bidirectional.
(SDH-1) the source line board. See Figure 3-8.
Source VC4 VC4-1 In this example, the service requires five VC-12s. Source
Source 1-5 The total capacity of the services is 5xE1 according to the
Timeslot plan. Hence, Source Timeslot Range(e.g.1,3-6) is set to
Range(e.g. 1-5.
1,3-6)
the sink tributary board for the bidirectional services from
NE1 to NE2. See Figure 3-8.
Sink VC4 - -
Sink Timeslot 1-5 The total capacity of the services is 5xE1 according to the
Range(e.g. plan. Hence, Sink Timeslot Range(e.g.1,3-6) is set to 1-5.
1,3-6)
Activate Yes -
Immediately
SCB Board.
----End
Relevant Task

System

This topic describes how to configure 1:1 linear MSP services in an end-to-end manner.
Prerequisite
l NEs, boards, and fibers must be successfully created on the U2000.
l A linear MSP subnet must be created and must be the same as the actual topology. For
details about how to create a protection subnet, see 2.6.4 Creating a Linear MS Protection
Subnet.
Allocation.
Procedure

and click Apply. In the Operation Result dialog box indicating that the operation

1. In Create SDH Trail, configure the parameters as follows. Set Level to VC12. The other
2. Double-click the source NE (NE1) on the right of the main topology. The Select Board
Port. Click OK.
same manner.

System
displayed.
Step 4 Optional: Modify the parameters SD Condition, Revertive Mode, and Switching Mode for
the linear MSP.
NOTE
l The parameter settings of the sink NE must be the same as those of the source NE.
l When modifying Switching Mode,
l Ensure that the protection group is in a proper state.
l Ensure that the protection protocol is disabled.
2. Select the created linear MSP group. In the Protection Subnet Maintenance tab, select
all nodes, right-click and choose Start/Stop Protocol > Stop from the shortcut menu.
3. Click the Protection Subnet Parameters tab and modify the parameters SD Condition,
Revertive Mode, and Switching Mode.
5. After the parameters are modified, restart the protection protocol according to Step 4.2.
SCB Board.
----End
Relevant Task
3.6 Configuring Two-Fiber Unidirectional MSP Services

The two-fiber unidirectional MSP services can provide network level protection for the services
on NEs on the MSP ring. On the U2000, you can add all the NEs on the MSP ring into the
protection subnet to create a two-fiber unidirectional MSP ring.

The networking diagram of a single two-fiber unidirectional MSP ring is simple. When you
construct the network, follow a certain order to create and name these NEs and ensure that the

System
traffic flows in a proper direction. This helps when you plan the traffic direction planning and
service configuration in future.
To configure the two-fiber unidirectional MSP service, you can configure the services that need
to be added to the ring network on the source NE, to pass through the intermediate nodes, and
to be dropped from the sink NE if the MSP protection subnet is already created.
This topic describes how to configure the two-fiber unidirectional MSP service.
This topic describes how to configure two-fiber unidirectional MSP services.

The networking diagram of a single two-fiber unidirectional MSP ring is simple. When you
construct the network, follow a certain order to create and name these NEs and ensure that the
traffic flows in a proper direction. This helps when you plan the traffic direction planning and
service configuration in future.
and drop services, and the SL1D boards are used as line boards to transmit SDH services.
Figure 3-9 Networking diagram of the services on the two-fiber unidirectional MSP ring
NE1:
Tributary board Line board Line board
3-SP3D 1-SL1D-1 1-SL1D-2
1-SL1D-1 1-SL1D-2
NE1
1-SL1D-2 1-SL1D-1
Two-fiber unidirectional
NE2 MSP ring NE4
1-SL1D-1
NE2: 1-SL1D-2
NE3 NE4:
1-SL1D-2 1-SL1D-1 Line board Line board
1-SL1D-1 1-SL1D-2
1-SL1D-2 1-SL1D-1
NE3:
3-SP3D 1-SL1D-1 1-SL1D-2

To configure the two-fiber unidirectional MSP service, you can configure the services that need
to be added to the ring network on the source NE, to pass through the intermediate nodes, and
to be dropped from the sink NE if the MSP protection subnet is already created.
l Traffic direction from NE1 to NE3: NE1→NE2→NE3

System
Services are added to the ring on the source NE (NE1), pass through NE2, and finally are
dropped from the sink NE (NE3). The capacity of the services is 5xE1.
l Traffic direction from NE3 to NE1: NE3→NE4→NE1
Services are added to the ring on the source NE (NE3), pass through NE4, and finally are
dropped from the sink NE (NE1). The capacity of the services is 5xE1.
l VC-12s 1-5 of VC4-1 carry the five E1 services for transmission.
When the transmission path between NE1 and NE2 becomes faulty, the signal flow and timeslot
allocation are as follows:
l Traffic direction from NE1 to NE3: NE1→NE4→NE3→NE2→NE3
Services are added to the ring on the source NE (NE1) and switched from the original
working path to the protection path. Then, the services pass through NE4 and NE3. After
that, the services are switched from the protection path to the working path on NE2. Finally,
the services are dropped from NE3.
l The services from NE3 to NE1 are not affected, and the traffic direction is NE3→NE4→
NE1.
The difference between the two-fiber unidirectional MSP service and the two-fiber bidirectional
MSP service is as follows:
l The two-fiber unidirectional MSP service uses the diverse routes, whereas the two-fiber
bidirectional MSP service uses the uniform route.
l In the case of the two-fiber unidirectional MSP service, different optical fibers are used for
the working timeslot and protection timeslot. That is, one optical fiber is used for carrying
the working service, and the other optical fiber is used for protection. In the case of the
two-fiber bidirectional MSP service, the same optical fiber is used for the working timeslot
and protection timeslot. That is, a certain capacity of the optical fiber is used for carrying
the working service, and a certain capacity of the optical fiber is used for protection.

System
Figure 3-10 Signal flow and timeslot allocation of the two-fiber unidirectional MSP services
5xE1services are
added/dropped
VC4-1:1-5(VC12) 3-SP3D NE1:
1-SL1D-1 1-SL1D-2 3-SP3D 1-SL1D-1 1-SL1D-2
NE1
1-SL1D-2 1-SL1D-1
VC4-1:1-5(VC12) VC4-1:1-5(VC12)
Pass-through service Two-fiber unidirectional 线路
Pass-through service
NE2 NE4 板
MSP ring
1-SL1D-1 1-SL1D-2
NE2: NE4:
Line board Line board Line board Line board
NE3
1-SL1D-2 1-SL1D-1 1-SL1D-1 1-SL1D-2
1-SL1D-2 1-SL1D-1
NE3:
VC4-1:1-5(VC12) 3-SP3D
5xE1services are
added/dropped 3-SP3D 1-SL1D-1 1-SL1D-2
the working path Line board
Traffic direction of the

Tributary board
protection path

This topic describes how to configure the two-fiber unidirectional MSP service.
Prerequisite
details about how to create the protection subnet, see 2.6.3 Creating an MS Ring
Protection Subnet.
Allocation.
Procedure
Step 1 Configure unidirectional services from NE1 to NE3.
1. Configure SDH services on the source NE (NE1).
l In the NE Explorer, select NE1 and then choose Configuration > SDH Service
l Click Create on the lower-right pane to display the Create SDH Service dialog box.
Set the parameters that are required, and then click OK.

System

This
Example

Direction Unidirectio In this example, the services are transmitted and

nal received on different paths. That is, the services are
unidirectional services. Hence, Direction of the
services is set to Unidirectional.
as the source tributary board for the unidirectional
Source VC4 - -
Source 1-5 The total capacity of the services is 5xE1 according to

Timeslot the plan. Hence, Source Timeslot Range(e.g.1,3-6)
Range(e.g. is set to 1-5.
1,3-6)
Sink VC4 VC4-1 In this example, the services require five VC-12s.
Sink VC4 is set to VC4-1, because a VC-4 contains
63 VC-12s.

Timeslot the plan. Hence, Sink Timeslot Range(e.g.1,3-6) is
Range(e.g. set to 1-5.
1,3-6)
Activate Yes -
Immediately
2. Configure unidirectional pass-through services on NE2.

This
Example

Direction Unidirection In this example, the services are transmitted and received
al on different paths. That is, the services are unidirectional
Unidirectional.

System

This
Example
Source Slot 1-SL1D-2 In this example, the SL1D board in slot 1 is configured
(SDH-2) as the source line board. See Figure 3-10. You can select
different source boards depending on the actual
situation.
Source VC4 VC4-1 In this example, the services require five VC-12s.
Source VC4 is set to VC4-1, because a VC-4 contains
63 VC-12s.

Timeslot the plan. Hence, Source Timeslot Range(e.g.1,3-6) is
1,3-6)
VC-12s.

Range(e.g. to 1-5.
1,3-6)
Activate Yes -
Immediately
3. Configure SDH services on the sink NE (NE3).

This
Example

Unidirectional.
(SDH-2) as the source line board. See Figure 3-10.

System

This
Example
63 VC-12s.

1,3-6)
Sink Slot 3-SP3D In this example, the SP3D board in slot 3 is configured
as the sink tributary board for the unidirectional services
from NE1 to NE3. See Figure 3-10.
Sink VC4 - -

Timeslot the planning. Hence, Sink Timeslot Range(e.g.1,3-6) is
1,3-6)
Activate Yes -
Immediately
Step 2 Configure unidirectional services from NE3 to NE1.

To configure unidirectional services from NE3 to NE1, refer to Step 1.
1. Configure SDH services on the source NE (NE3).
This
Example

Unidirectional.
as the source tributary board for the unidirectional

1,3-6)

System

This
Example
VC-12s.

Range(e.g. to 1-5.
1,3-6)
Activate Yes -
Immediately
2. Configure unidirectional pass-through services on NE4.

This
Example

Unidirectional.
63 VC-12s.

Range(e.g. set to1-5.
1,3-6)
VC-12s.

System

This
Example

Range(e.g. to 1-5.
1,3-6)
Activate Yes -
Immediately
3. Configure SDH services on the sink NE (NE1).

This
Example

al on the same path. That is, the services are bidirectional
Bidirectional.
Source VC4 VC4-1 In this example, the service requires five VC-12s.
63 VC-12s.

1,3-6)
Sink VC4 3-SP3D In this example, the SP3D board in slot 3 is configured
as the sink tributary board for the unidirectional services
from NE3 to NE1. See Figure 3-10.

Range(e.g. to 1-5.
1,3-6)
Activate Yes -
Immediately

System
SCB Board.
----End
Relevant Task

This topic describes how to configure two-fiber unidirectional MSP services.
Prerequisite
l A linear MSP subnet must be created and must be the same as the actual topology. For
details about how to create a protection subnet, see 2.6.3 Creating an MS Ring Protection
Subnet.
Allocation.
In end-to-end mode, configuration of two-fiber unidirectional MSP services is similar to
configuration of two-fiber bidirectional MSP services. The only difference is that you set
Direction to Unidirectional for two-fiber unidirectional MSP services and set Direction to
Bidirectional for two-fiber bidirectional MSP services.
Procedure
Step 2 Create a VC4 server trail.

1. Set associated parameters as follows. Set Direction to Unidirectional and Level to VC4
Server Trail, and take default values for other parameters.
2. Double-click the source NE (NE1) and sink NE (NE3) on the right of the Main Topology
and click Apply. Then, click Close in the Operation Result dialog box that is displayed,
if the operation is successful. A unidirectional VC4 server trail is set up from NE1 to NE3.

System
3. Double-click the source NE (NE3) and sink NE (NE1) on the right of the Main Topology,
and set up a unidirectional VC4 server trail from NE3 to NE1 using the same method.
4. Optional: If the Operation Result dialog box indicates that the operation is successful,
you can also click Browse Trail to query the created VC4 server trail.
Step 3 Create VC12 services after setting up VC4 server trails.

1. In Create SDH Trail, configure associated parameters as follows. Set Level to VC12, set
Direction to Bidirectional, and take default values for other parameters.
2. Double-click the source NE (NE1) on the right of the Main Topology. The Select Board
Port, and then click OK.
3. Double-click the sink NE (NE3) on the right of the Main Topology, and configure NE3
using the same method.
4. Select Copy after Creation and click Apply. If the Operation Result dialog box is
displayed to indicate that the operation is successful, click Close. Then, the Copy dialog
box is displayed.
5. In Available Timeslots/Port, select the ports from SP3D-2(SDH_TU-2) to SP3D-5
(SDH_TU-5), and click Add.
6. If the Operation Result dialog box is displayed to indicate that the operation is successful,
click Close.
7. Optional: If the Operation Result dialog box is displayed to indicate that the operation is
successful, you can also click Browse Trail to query the created VC12 services.
Step 4 Optional: Change WTR Time and SD Condition.

NOTE
Parameter settings of the sink NE must be the same as those of the source NE.
2. Click the Protection Subnet Parameters tab and change parameters such as WTR
Time and SD Condition.
3. Click Apply. If the Operation Result dialog box is displayed to indicate that the operation
is successful, click Close.
Step 6 Enable the performance monitoring function for NEs. For details, see Setting Performance
SCB Board.
----End

System
Relevant Task
3.7 Configuring the Two-Fiber Bidirectional MSP Services

To configure the two-fiber bidirectional MSP services, you need to create the MSP subnet
protection and MSP services separately. There is no requirement for the configuration sequence.
The networking diagram of a single two-fiber bidirectional MSP ring is simple. When you
construct the network, follow a certain order to create and name the NEs and ensure that the
traffic flows in a proper direction. This helps when you plan the traffic directions and configure
services in future.
To configure the two-fiber bidirectional MSP service on a ring network, configure the services
that need to be added to the ring network on the source NE, to pass through the intermediate
nodes, and to be dropped from the sink NE, if the MSP protection subnet is already created. In
the case of the ring network, more than one route is available from the source NE to the sink
NE. In actual application scenarios, not all the routes need to be configured. Hence, you need
to properly plan and configure the service directions and timeslots before the configuration.
The configuration of the two-fiber bidirectional MSP services is independent of the configuration
of the protection subnet. To configure the two-fiber bidirectional MSP service, if the protection
subnet is configured, configure the SDH services from the tributary board to the line board on
the source and sink NEs and configure the pass-through services on the intermediate NEs.
The configuration of two-fiber bidirectional MSP services is independent of the configuration
of a protection subnet. To configure two-fiber bidirectional MSP services, configure SDH
services from the tributary board to the line board on the source and sink NEs and configure
pass-through services on the intermediate NEs if a protection subnet has already been configured.
The following part describes how to configure two-fiber bidirectional MSP services in end-to-
end mode.

The networking diagram of a single two-fiber bidirectional MSP ring is simple. When you
construct the network, follow a certain order to create and name the NEs and ensure that the
traffic flows in a proper direction. This helps when you plan the traffic directions and configure
services in future.
Figure 3-11 shows the networking of the two-fiber bidirectional MSP ring that comprises four
pieces of OptiX OSN equipment. In this example, the SP3D boards are configured on the source
NE (NE1) and the sink NE (NE3) as tributary boards to add and drop services, and the SL4D
boards are used as line boards to transmit SDH services.

System
Figure 3-11 Networking diagram of the services on the two-fiber bidirectional MSP ring
NE1:
3-SP3D 1-SL4D-1 1-SL4D-2
1-SL4D-1 1-SL4D-2
NE1
1-SL4D-2 1-SL4D-1
NE2 Two-fiber bidirectional NE4

MSP ring
1-SL4D-1
1-SL4D-2
NE2: NE3
Line board Line board NE4:
1-SL4D-2 1-SL4D-1 1-SL4D-1 1-SL4D-2
NE3:
3-SP3D 1-SL4D-1 1-SL4D-2

To configure the two-fiber bidirectional MSP service on a ring network, configure the services
that need to be added to the ring network on the source NE, to pass through the intermediate
nodes, and to be dropped from the sink NE, if the MSP protection subnet is already created. In
the case of the ring network, more than one route is available from the source NE to the sink
NE. In actual application scenarios, not all the routes need to be configured. Hence, you need
to properly plan and configure the service directions and timeslots before the configuration.
Figure 3-12 shows the service signal flow and timeslot allocation. In this example, five E1
services are configured so that the services enter the ring network from NE1, pass through NE2,
and then are dropped on the sink NE (NE3).

System
Figure 3-12 Signal flow and timeslot allocation

5xE1 services are
added/dropped
VC4-1:1-5(VC12)
NE1:
3-SP3D 1-SL4D-1 1-SL4D-2
NE1
VC4-1:1-5(VC12) 线路
Pass-through service NE2 MSP ring NE4 板
NE2:
1-SL4D-2 1-SL4D-1 NE3
NE3:
3-SP3D 1-SL4D-1 1-SL4D-2
VC4-1:1-5(VC12)
5xE1 services are
service Line board added/dropped
route
Tributary board

The configuration of the two-fiber bidirectional MSP services is independent of the configuration
of the protection subnet. To configure the two-fiber bidirectional MSP service, if the protection
subnet is configured, configure the SDH services from the tributary board to the line board on
the source and sink NEs and configure the pass-through services on the intermediate NEs.
Prerequisite
details about how to create the protection subnet, see 2.6.3 Creating an MS Ring
Protection Subnet.
l You must be familiar with 3.7.2 Signal Flow and Timeslot Allocation.
Procedure
Step 1 Configure the SDH services of the source NE (NE1).
1. In the NE Explorer, select NE1, and then choose Configuration > SDH Service

System

This
Example

l on the same path. That is, the services are bidirectional
Bidirectional.
as the source tributary board. See Figure 3-12. You can
select different source boards depending on the actual
situation.
Source VC4 - -
Source 1-5 In this example, the total capacity of the services is 5xE1
Timeslot according to the plan. The service level is VC12. Hence,
Range(e.g. Source Timeslot Range(e.g.1,3-6) is set to 1-5. See
1,3-6) Figure 3-12.
(SDH-1) as the sink line board. See Figure 3-12. You can select
different sink boards depending on the actual situation.
VC-12s.
Sink 1-5 In this example, the total capacity of the services is 5xE1
Range(e.g. Sink Timeslot Range(e.g.1,3-6) is set to 1-5. See
1,3-6) Figure 3-12.
Activate Yes -
Immediately
Step 2 Configure the SDH services of the sink NE (NE3). Refer to Step 1 and configure the SDH
services of NE3. Set the parameters as follows.
This
Example

on the same path. That is, the services are bidirectional
Bidirectional.

System

This
Example
(SDH-2) the source line board. See Figure 3-12. You can select
different source boards depending on the actual situation.
Range(e.g. Source Timeslot Range(e.g.1,3-6) is set to 1-5. See Figure
1,3-6) 3-12.
the sink tributary board. See Figure 3-12. You can select
Sink VC4 - -
Sink Timeslot 1-5 In this example, the total capacity of the services is 5xE1
Range(e.g. according to the plan. The service level is VC12. Hence,
1,3-6) Sink Timeslot Range(e.g.1,3-6) is set to 1-5. See Figure
3-12.
Activate Yes -
Immediately
Step 3 Configure the pass-through services of NE2.

1. In the NE Explorer, select NE2 and then choose Communication > SDH Service
This
Example

Bidirectional.
situation.

System

This
Example
63 VC-12s.
1,3-6) Figure 3-12.
VC-12s.
1,3-6) Figure 3-12.
Activate Yes -
Immediately
SCB Board.
----End
Relevant Task

The configuration of two-fiber bidirectional MSP services is independent of the configuration
of a protection subnet. To configure two-fiber bidirectional MSP services, configure SDH
services from the tributary board to the line board on the source and sink NEs and configure
pass-through services on the intermediate NEs if a protection subnet has already been configured.
The following part describes how to configure two-fiber bidirectional MSP services in end-to-
end mode.

System
Prerequisite
l An MSP subnet must be created and must be the same as the actual topology. For details
about how to create a protection subnet, see 2.6.4 Creating a Linear MS Protection
Subnet.
Allocation.
In end-to-end mode, configuration of two-fiber unidirectional MSP services is similar to
configuration of two-fiber bidirectional MSP services. The only difference is that you set
Direction to Unidirectional for two-fiber unidirectional MSP services and set Direction to
Bidirectional for two-fiber bidirectional MSP services.
Procedure

and click Apply. In the Operation Result dialog box that is displayed, click Close.
Trail to query the created VC4 service-layer trail.

1. In Create SDH Tail, configure the parameters as follows. Set Level to VC12 and set
Direction to Bidirectional. The other parameters take default values.
OK.

System
same manner.
SCB Board.
----End
Relevant Task
3.8 Configuring Services on the SNCP Ring

Compared with the services on an MSP ring, the services on an SNCP ring have dedicated
physical paths as the protection paths. In addition, the services on an SNCP ring are dually fed
and selectively received. When you configure services on an SNCP ring, you need not configure
the protection subnet and the services separately. When you configure services on an SNCP ring,
however, you need to configure the working services and protection services separately.
The creation of an SNCP ring network is similar to the creation of an MSP ring network. For
example, the MSP and SNCP rings are constructed based on two fibers and their services must
pass through the intermediate nodes for transmission from the source NE to the sink NE. The
difference is that the SNCP protection and SNCP services can be created on the U2000 at a time.
Similar to the service configuration of an MSP ring, you need to plan proper traffic directions
before configuring the services on an SNCP ring, if multiple service routes are available from
the source end to the sink end. In the case of the services on the SNCP ring, allocate timeslots
for the source slot of the working service and timeslots for the source slot of the protection
service, when allocating timeslots for source slots.
The SNCP protection and the services on the SNCP ring are configured on the U2000 at a time.
To configure the SNCP services on the source and sink NEs, you need to determine the source
boards and timeslots for the working service and protection service. In addition, you need to
configure the pass-through service on the intermediate nodes.
SNCP protection and services on an SNCP ring are configured on the U2000 at the same time.
To configure SNCP services on the source and sink NEs, determine the source boards and

System
timeslots for the working service and protection service, and configure pass-through services on
the intermediate nodes. The following part describes how to configure services on an SNCP ring
in an end-to-end manner.

The creation of an SNCP ring network is similar to the creation of an MSP ring network. For
example, the MSP and SNCP rings are constructed based on two fibers and their services must
pass through the intermediate nodes for transmission from the source NE to the sink NE. The
difference is that the SNCP protection and SNCP services can be created on the U2000 at a time.
Figure 3-13 shows an SNCP ring that comprises four pieces of MSTP equipment. In this
example, the SP3D boards are configured on the source NE (NE1) and the sink NE (NE3) as
tributary boards to add and drop services, and the SL1D boards are used as line boards to transmit
SDH services.
Figure 3-13 Networking diagram of the services on the SNCP ring

NE1:
3-SP3D 1-SL1D-1 1-SL1D-2
3-SP3D
1-SL1D-1 1-SL1D-2
NE1
1-SL1D-2 1-SL1D-1
NE2 SNCP ring NE4
1-SL1D-1
NE2: 1-SL1D-2
NE3
1-SL1D-2 1-SL1D-1 1-SL1D-1 1-SL1D-2
NE3: 3-SP3D
3-SP3D 1-SL1D-1 1-SL1D-2

Similar to the service configuration of an MSP ring, you need to plan proper traffic directions
before configuring the services on an SNCP ring, if multiple service routes are available from
the source end to the sink end. In the case of the services on the SNCP ring, allocate timeslots
for the source slot of the working service and timeslots for the source slot of the protection
service, when allocating timeslots for source slots.
Figure 3-14 shows the signal flow of the services on the SNCP ring and the timeslot allocation
to the services on the SNCP ring. In the actual configuration, you can plan other proper working
paths and protection paths according to the requirement. In this example, the working service
route is NE1-NE2-NE3 and the protection service route is NE1-NE4-NE3. There are five E1
services.

System

NE1:
Protection
SNCP protection Service service Service
5xE1 services are group source
source sink
added/dropped
Group 1 1-SL1D-1 1-SL1D-2 3-SP3D
VC4-1:1-5(VC12) VC4-1:1-5(VC12)
1-SL1D-1 1-SL1D-2
NE2 and NE4:

SDH Service Service
service source sink
NE1
VC12 1-SL1D-2 1-SL1D-1
1-SL1D-2
1-SL1D-1
VC4-1:1-5(VC12)
线路
VC4-1:1-5(VC12)
Pass-through service NE2 SNCP ring NE4 板 Pass-through service
1-SL1D-1 1-SL1D-2
NE3
1-SL1D-2 1-SL1D-1
VC4-1:1-5(VC12) VC4-1:1-5(VC12)
NE3:
5xE1 services are
added/dropped Protection
Traffic direction of SNCP protection Service service Service
Line board
the working path group source source sink
Traffic direction of Group 1 1-SL1D-2 3-SP3D
1-SL1D-1

The SNCP protection and the services on the SNCP ring are configured on the U2000 at a time.
To configure the SNCP services on the source and sink NEs, you need to determine the source
boards and timeslots for the working service and protection service. In addition, you need to
configure the pass-through service on the intermediate nodes.
Prerequisite
Procedure
2. Click Create SNCP Service on the lower-right pane to display the Create SNCP
Service dialog box. Set the parameters that are required, and then click OK.

System

This
Example
Service Type SNCP In this example, Service Type adopts the

default value, namely, SNCP.
Level VC12 In this example, E1 services are configured on

the ring. Hence, Level of the E1 services is set
to VC12.
Direction Bidirectio In this example, the services are transmitted

nal and received on the same path. That is, the
services are bidirectional services. Hence,
Direction of the services is set to
Bidirectional.
Revertive Mode Revertive This parameter indicates whether the services

are switched back after the faulty line is
recovered, that is, whether the switching is
revertive or non-revertive. In this example,
Revertive Mode is set to Revertive.
Hold-Off Time (100ms) 0 It is recommended that this parameter adopts

the default value.
WTR Time (s) 600 After the working path is recovered to normal
and the normal state lasts for 600s, the
switching restoration occurs. This parameter is
valid only when the Revertive Mode
parameter is set to Revertive.
Working Source 1-SL1D-1 In this example, the SL1D board in slot 1 is

Service Slot (SDH-1) configured as the source line board of the
working service. See Figure 3-14. You can
select different source boards depending on the
actual situation.
Source VC4-1 In this example, the working service source

VC4 uses the timeslots of VC4-1.
Source 1-5 In this example, the total capacity of the

Timeslot services is 5xE1 according to the plan. The
Range(e.g. service level is VC12. Hence, Source Timeslot
1,3-6) Range of the Working Service is set to 1-5.
See Figure 3-14.
Sink Slot 3-SP3D In this example, the SP3D board in slot 3 is

configured as the sink tributary board. See
Figure 3-14. You can select different sink
boards depending on the actual situation.
Sink VC4 - -

System

This
Example
Sink 1-5 In this example, the total capacity of the

1,3-6) Range of the Working Service is set to 1-5.
See Figure 3-14
Protection Source 1-SL1D-2 In this example, the SL1D board in slot 1 is

Service Slot (SDH-2) configured as the source board of the protection
service. See Figure 3-14. You can select
situation.
Source VC4-1 In this example, the protection service source

VC4 uses the timeslots of VC4-1.
Source 1-5 In this example, the total capacity of the

1,3-6) Range of the Protection Service is set to 1-5.
See Figure 3-14.
Step 2 Configure the SDH services of the sink NE (NE3). Refer to Step 1 and configure the SDH
services of NE3. The method and parameters for configuring the SDH services of NE3 are the
same as the method and parameters for configuring the SDH services of NE1.
This
Example
Level VC12 In this example, E1 services are configured on the ring.

Hence, Level of the E1 services is set to VC12.
services. Hence, Direction of the E1 services is set to
Bidirectional.
situation.

System

This
Example
63 VC-12s.
1,3-6) Figure 3-14.
VC-12s.
1,3-6) Figure 3-14.
Activate Yes -
Immediately
Step 4 Configure the pass-through services of NE4. Refer to Step 3 and configure the pass-through
services of NE4. The method and parameters for configuring the pass-through services of NE4
are the same as the method and parameters for configuring the pass-through services of NE2.
SCB Board.
----End
Relevant Task

SNCP protection and services on an SNCP ring are configured on the U2000 at the same time.
To configure SNCP services on the source and sink NEs, determine the source boards and
timeslots for the working service and protection service, and configure pass-through services on
the intermediate nodes. The following part describes how to configure services on an SNCP ring
in an end-to-end manner.

System
Prerequisite
Allocation.
Procedure
Step 2 Create a VC4 server trail.

1. Set associated parameters as follows. Set Level to VC4 Server Trail, and take default
values for other parameters.
2. Double-click the source NE (NE1) and sink NE (NE3) on the right of the Main Topology,
and set up a VC4 server trail from NE1 to NE3 via NE2.
a. On the Route Constraint tab, right-click Explicit Node, and then choose Add.
b. In the Add Explicit Node dialog box that is displayed, set Type and What for
configuring the pass-through node NE2.
c. Click OK. The VC4 server trail is sure to stretch from NE1 to NE3 via NE2
click Browse Trail to query the created VC4 server trail.
Step 3 Set up a protection VC4 server trail using the same method as setting up a VC4 server trail.
During the setup of a protection VC4 server trail, ensure that the originated node is NE1, the
terminated node is NE3, and the pass-through node is NE4.

1. In Create SDH Trail, set associated parameters as follows. Set Level to VC12, and take
default values for other parameters.
2. Double-click the source NE (NE1) on the right of the Main Topology. The Select Board
Port, and then click OK.

System
3. Double-click the sink NE (NE3) on the right of the Main Topology, and use the same
method to Tributary Port of NE3.
4. In Create SDH Trail, click the SNCP Setting tab, right-click in the blank pane, and choose
Add from the shortcut menu. In the Add the dual-fed and selective receiving node dialog
box that is displayed, select NE1 as the dual-fed node and NE3 as the selective receiving
node, and then click OK. In the Operation Result dialog box indicating that the operation
5. Optional: In the Create SDH Trail window, select Set Route Timeslot. In the dialog box
that is displayed, you can modify the working server trail of VC12 services.
displayed.
8. Click OK. In the Operation Result dialog box indicating that the operation succeeded,
click Close.
9. Optional: In the Operation Result dialog box indicating that the operation succeeded, you
can also click Browse Trail to query the created VC12 services.
Step 5 Optional: After configuring SNCP services in an end-to-end manner, you can browse the created
VC4 server trails and VC12 services by choosing Service > SDH Trail > Manage SDH
Trail from the Main Menu and specifying the filter conditions.
SCB Board.
----End
Relevant Task
To delete any service that is incorrectly configured, see Deleting SDH Services.
3.9 Configuring Services on the SNCP Ring with a Non-

Protection Chain
To configure the services on the SNCP ring, you can directly configure the working service and
protection service, without first configuring the protection subnet. To configure the services on
the non-protection chain, you can configure the services only after the protection subnet is
created.

System
The networking of the SNCP ring in the case of configuring the services on the SNCP ring with
a non-protection chain is similar to the networking in the case of configuring the services on the
SNCP ring. The services from the SNCP ring to the non-protection chain pass through the
intersecting node and are added to or dropped from the NE on the non-protection chain.
To configure services on the SNCP ring with a non-protection chain, you need to plan proper
traffic directions for the services on the SNCP ring and the services on the non-protection chain.
In the case of the services on the SNCP ring, allocate timeslots for the source slot of the working
service and timeslots for the source slot of the protection service, when allocating timeslots for
source slots.
Before you configure the services on the SNCP ring with a non-protection chain, familiarize
yourself with the information about the source slot, sink slot, and their corresponding timeslots
of the working service and protection service on the source and sink NEs on the SNCP ring. You
need to configure the pass-through services on the intersecting NE.
Before configuring services on an SNCP ring with a non-protection chain, familiarize yourself
with the information about the source slot, sink slot, and their corresponding timeslots of the
working service and protection service on the source and sink NEs on the SNCP ring. You also
need to configure pass-through services on the intersecting NE. The following part describes
how to configure services on an SNCP ring with a non-protection chain in an end-to-end manner.

The networking of the SNCP ring in the case of configuring the services on the SNCP ring with
a non-protection chain is similar to the networking in the case of configuring the services on the
SNCP ring. The services from the SNCP ring to the non-protection chain pass through the
intersecting node and are added to or dropped from the NE on the non-protection chain.
Figure 3-15 shows the networking diagram of the SNCP ring with a non-protection chain. The
SNCP ring comprises five pieces of equipment.
In this example, 5xE1 services are configured between NE3 and NE5. The SP3D boards are
configured on the source NE (NE3) and the sink NE (NE5) as tributary boards to add and drop
services. The SL4D and SL1D boards are used as the line boards for transmitting SDH services.

System
Figure 3-15 Networking diagram of the services on the SNCP ring with a non-protection chain
NE1:
1-SL4D-1 1-SL4D-2
1-SL4D-1 1-SL4D-2 NE5:

3-SP3D 2-SL1D-1
NE1
1-SL4D-2 1-SL4D-1
3-SP3D
2-SL1D-1 2-SL1D-1
NE2 SNCP ring NE4
1-SL4D-1 Non-protection
1-SL4D-2 chain NE5
NE2: NE3
1-SL4D-2 1-SL4D-1 Line board Line board Line board
1-SL4D-1 1-SL4D-2 2-SL1D-1
1-SL4D-2 1-SL4D-1
3-SP3D
NE3:
3-SP3D 1-SL4D-1 1-SL4D-2

To configure services on the SNCP ring with a non-protection chain, you need to plan proper
traffic directions for the services on the SNCP ring and the services on the non-protection chain.
In the case of the services on the SNCP ring, allocate timeslots for the source slot of the working
service and timeslots for the source slot of the protection service, when allocating timeslots for
source slots.
Figure 3-16 shows the signal flow of the services on the SNCP ring with a non-protection chain
and the timeslot allocation to the services on the SNCP ring with a non-protection chain . In this
example, five E1 services are configured between NE3 and NE5.
In this example, the traffic direction of the services on the SNCP ring, is configured as follows:
l Traffic direction of the working service between NE3 and NE4: NE3-NE4
l Traffic direction of the protection service between NE3 and NE4: NE3-NE2-NE1-NE4
In the actual configuration, you can plan other proper working paths and protection paths
according to the requirement.

System

NE1:VC4-1:1-5(VC12) Service pass through
SDH Service Service
service source sink
VC12 1-SL4D-2 1-SL4D-1
1-SL4D-1 1-SL4D-2 NE4:

Protection
NE2: VC4-1:1-5(VC12) Service pass through SNCP protection Service service Service
NE1 group source source sink
SDH Service Service
service source sink Group 1 1-SL4D-2 1-SL4D-1 2-SL1D-1
VC12 1-SL4D-2 1-SL4D-1
1-SL4D-2 1-SL4D-1 VC4-1:1-5(VC12)
2-SL1D-1 2-SL1D-1 3-SP3D
线路
线路
NE2 SNCP ring NE 板
板 5×E1
4
Non-protection
1-SL4D-1 1-SL4D-2
chain NE5
VC4-1:1-5(VC12) NE5:
SDH Service Service
service source sink
NE3
VC12 2-SL1D-1 3-SP3D
1-SL4D-2 1-SL4D-1
VC4-1:1-5(VC12) VC4-1:1-5(VC12)
3-
SP3D NE3:
Traffic direction of Protection
Line board 5×E1 SNCP protection
the working path Service service Service
Traffic direction of group source source sink
the protection path Tributary board Group 1 1-SL4D-1 1-SL4D-2 3-SP3D
Traffic direction of services
on the non-protection chain

Before you configure the services on the SNCP ring with a non-protection chain, familiarize
yourself with the information about the source slot, sink slot, and their corresponding timeslots
of the working service and protection service on the source and sink NEs on the SNCP ring. You
need to configure the pass-through services on the intersecting NE.
Prerequisite
Chain.
Procedure

System

This
Example
Service Type SNCP In this example, Service Type is set to SNCP.
Level VC12 In this example, E1 services are configured.

Revertive Mode Revertive When an NE is in the switching state, the NE is

restored from the switching state to the normal
state some time after the working path is recovered
to normal.
Direction Bidirection In this example, the cross-connections are

al configured in the SNCP receive direction and in
the SNCP transmit direction.
Hold-Off Time 0 It is recommended that this parameter adopts the

(100ms) default value.
WTR Time (s) 600 After the working path is recovered to normal and
the normal state lasts for 600s, the switching
restoration occurs. This parameter is valid only
when the Revertive Mode parameter is set to
Revertive.
Wor Source Slot 1-SL4D-1 In this example, the SL4D board in slot 1 of NE3
king (SDH-1) is configured as the source line board of the
Ser working service. See Figure 3-16.
vice
Source VC4 VC4-1 In this example, the working service source uses
the timeslots of VC4-1.

Timeslot between NE3 and NE5. Hence, the working
Range(e.g. service source occupies VC-12s 1-5.
1,3-6)
Sink Slot 3-SP3D In this example, the SP3D board in slot 3 of NE3
is configured as the sink line board of the working
service. See Figure 3-16.
Sink VC4 - -

Range(e.g. between NE3 and NE5. Hence, the working
1,3-6) service source occupies VC-12s 1-5.
Prot Source Slot 1-SL4D-2 In this example, the SL4D board in slot 1 of NE3
ecti (SDH-2) is configured as the source line board of the
on protection service. See Figure 3-16.
Ser
vice Source VC4 VC4-1 In this example, the protection service source uses

System

This
Example

Timeslot between NE3 and NE5. Hence, the protection
1,3-6)
Step 2 Configure the SDH services of the sink NE (NE4).
1. In the NE Explorer, click , and then select NE4. Click OK.

2. Choose Configuration > SDH Service Configuration from the Function Tree.
This
Example
Service Type SNCP In this example, Service Type is set to SNCP.
Level VC12 In this example, E1 services are configured.

Revertive Mode Revertive When an NE is in the switching state, the NE is

restored from the switching state to the normal
state some time after the working path is recovered
to normal.
Direction Bidirection In this example, the cross-connections are

al configured in the SNCP receive direction and in
the SNCP transmit direction.
Hold-Off Time 0 It is recommended that this parameter adopts the

(100ms) default value.
WTR Time (s) 600 After the working path is recovered to normal and
the normal state lasts for 600s, the switching
restoration occurs. This parameter is valid only
when the Revertive Mode parameter is set to
Revertive.
Wor Source Slot 1-SL4D-2 In this example, the SL4D board in slot 1 of NE4
king (SDH-2) is configured as the source line board of the
Ser working service. See Figure 3-16.
vice
Source VC4 VC4-1 In this example, the working service source uses

System

This
Example

Timeslot between NE3 and NE5. Hence, the working
1,3-6)
Sink Slot 2-SL1D-1 In this example, the SL1D board in slot 2 of NE4
(SDH-1) is configured as the sink line board of the working
service. See Figure 3-16.
Sink VC4 VC4-1 In this example, the working service sink uses the
timeslots of VC4-1.

Range(e.g. between NE3 and NE5. Hence, the working
1,3-6) service sink occupies VC-12s 1-5.
Prot Source Slot 1-SL4D-1 In this example, the SL4D board in slot 1 of NE3
ecti (SDH-1) is configured as the source line board of the
on protection service. See Figure 3-16.
Ser
vice Source VC4 VC4-1 In this example, the protection service source uses

Timeslot between NE3 and NE5. Hence, the protection
1,3-6)


This
Example

Direction Bidirectiona In this example, Direction of the service is set to

l Bidirectional.
Source VC4 VC4-1 In this example, the working service source uses the
timeslots of VC4-1.

System

This
Example

Timeslot NE3 and NE5. Hence, the working service source
Range(e.g. occupies VC-12s 1-5.
1,3-6)
Sink VC4 VC4-1 In this example, the service sink uses the timeslots of
VC4-1.

Range(e.g. 1-5.
1,3-6)
Activate Yes -
Immediately
Step 4 Configure the pass-through services of NE1. Refer to Step 3 and configure the SDH services of
NE1. The method and parameters for configuring the pass-through services of NE1 are the same
as the method and parameters for configuring the pass-through services of NE2.
Step 5 Configure the services on the non-protection chain at NE5.

3. Click Create on the lower-right pane to display the Create SDHP Service dialog box. Set

This
Example

Direction Bidirectiona In this example, Direction of the E1 services is set to

l Bidirectional.
3-16.
Source VC4 - -

Timeslot NE3 and NE5. Hence, the working service source
Range(e.g. occupies VC-12s 1-5.
1,3-6)

System

This
Example
VC4-1.

Range(e.g. 1-5.
1,3-6)
Activate Yes -
Immediately
SCB Board.
----End
Relevant Task

Before configuring services on an SNCP ring with a non-protection chain, familiarize yourself
with the information about the source slot, sink slot, and their corresponding timeslots of the
working service and protection service on the source and sink NEs on the SNCP ring. You also
need to configure pass-through services on the intersecting NE. The following part describes
how to configure services on an SNCP ring with a non-protection chain in an end-to-end manner.
Prerequisite
l A protection subnet must be created and must be the same as the actual topology. For details
about how to create a protection subnet, see 2.6.1 Configuring a Non-Protection Chain.
Allocation.
Procedure
Step 1 Create a working VC-4 server trail.

System
1. Choose Service > SDH Trail > Create SDH Trail from the Main Menu.
3. Double-click NE3 and NE4 on the right of the Main Topology, select the trail from NE3
to NE4 as the working, VC-4 server trail, and click Close. In the Operation Result dialog
box indicating that the operation succeeded, click Close.
Step 2 Create a protection VC-4 server trail, using the method described in Step 1.
NOTE
When creating a protection VC-4 server trail, double-click NE3 and NE4 on the right of the Main Topology,
and ensure that the traffic direction is NE3-NE2-NE1-NE4.
On the Route Constraint tab, click the Explicit Node tab, right-click in the blank area, and then choose
Add from the shortcut menu. In the Add Explicit Node dialog box that is displayed, set Type and What
for configuring the pass-through node NE2, and then click OK.
Step 3 Create a VC-4 server trail without a protection chain.

1. In Create SDH Tail, configure the parameters as follows. Set Level to VC4 Server
Trail, and take default values for other parameters.
2. Double-click NE4 and NE5 on the right of the Main Topology, and click Apply. Then,
click Close in the Operation Result dialog box indicating that the operation succeeded.
Step 4 Create VC12 services after setting up a VC-4 server trail.

1. In Create SDH Tail, configure associated parameters as follows. Set Level to VC12, and
take default values for other parameters.

System
2. Double-click the NE3 on the right of the Main Topology. The Select Board Port-
Source dialog box is displayed. Select the SP3D board to be configured and choose 1 on
Tributary Port, and then click OK.
3. Configure NE5 using the method described in Step 4.2.
4. In Create SDH Trail, click the SNCP Setting tab, right-click in the blank area, and choose
Add from the shortcut menu. In the Add the dual-fed and selective-receiving node dialog
box that is displayed, select NE3 as the dual-fed node and NE4 as the selective receiving
node, and then click OK. In the Operation Result dialog box indicating that the operation
displayed.
8. Optional: In the Operation Result dialog box indicating that the operation succeeded, you
can also click Browse Trail to query the created VC12 services.
SCB Board.
----End
Relevant Task
3.10 Configuring Service on the MSP Ring with a Non-

Protection Chain
Configure the protection subnet for the MSP, Protection Subnet for the non-protection chain,
and services on the MSP ring with a non-protection chain separately. It is recommended that
you configure the protection subnets before configuring the services on the MSP ring with a
non-protection ring chain.

In the case of the MSP ring with a non-protection chain, the networking diagram of the MSP
ring is similar to the networking diagram of the single two-fiber bidirectional MSP ring. The
only difference is that one line board needs to be configured on the intersecting NE when the
non-protection chain is added. This can realize the pass-through of the services when the services
are required to be transmitted out of the MSP ring.
To configure the service on the MSP ring with a non-protection chain, you should plan a proper
traffic direction and a timeslot allocation scheme for the services on the SNCP ring and the
services on the non-protection chain.

System

The configuration of the services on the two-fiber bidirectional MSP ring with a non-protection
chain is independent of the creation of the protection subnets for the MSP and for the non-
protection chain. To configure the services on the two-fiber bidirectional MSP ring with a non-
protection chain, configure the SDH services from the tributary board to the line board on the
source and sink NEs and configure pass-through services on the intermediate NEs, if the
protection subnet is already created.
The configuration of services on a two-fiber bidirectional MSP ring with a non-protection chain
is independent of the creation of protection subnets for the MSP and for the non-protection chain.
To configure services on a two-fiber bidirectional MSP ring with a non-protection chain,
configure SDH services from the tributary board to the line board on the source and sink NEs
and configure pass-through services on the intermediate NEs, if the protection subnet has already
been created. The following part describes how to configure services on an MSP ring with a
non-protection chain in an end-to-end manner.

In the case of the MSP ring with a non-protection chain, the networking diagram of the MSP
ring is similar to the networking diagram of the single two-fiber bidirectional MSP ring. The
only difference is that one line board needs to be configured on the intersecting NE when the
non-protection chain is added. This can realize the pass-through of the services when the services
are required to be transmitted out of the MSP ring.
Figure 3-17 shows the networking diagram of the MSP ring with a non-protection chain. The
MSP ring comprises five pieces of equipment. In this example, the SP3D boards are configured
on the source NE (NE3) and sink NE (NE5) as tributary boards to add and drop services, and
the SL4D and SL1D boards are used as line boards to transmit SDH services.
Figure 3-17 Networking diagram of the services on the two-fiber bidirectional MSP ring with
a non-protection chain
NE1:
1-SL4D-1 1-SL4D-2
1-SL4D-1 1-SL4D-2
NE5:
3-SP3D 2-SL1D-1
NE1
1-SL4D-2 1-SL4D-1
2-SL1D-1 2-SL1D-1
Two-fiber bidirectional
NE2 NE4
MSP ring
Non-protection
1-SL4D-1 1-SL4D-2 chain NE5
NE2: NE3
1-SL4D-2 1-SL4D-1 Line board Line board Line board
1-SL4D-1 1-SL4D-2 2-SL1D-1
1-SL4D-2 1-SL4D-1
NE3:
3-SP3D 1-SL4D-2 1-SL4D-1

System

To configure the service on the MSP ring with a non-protection chain, you should plan a proper
traffic direction and a timeslot allocation scheme for the services on the SNCP ring and the
services on the non-protection chain.
Figure 3-18 shows the signal flow of the services on the MSP ring with a non-protection chain
and the timeslot allocation to the services on the MSP ring with a non-protection chain. In this
example, five E1 services are added to or dropped from NE3 and NE5, and these services pass
through NE4.
On the MSP ring, the services from NE3 to NE4 in this example are transmitted on the short
path. In the actual configuration, you can plan other service paths according to the requirement.
NOTE
On a ring network, the long path and short path do not actually refer to the geographical distance. They are
determined by the number of intermediate NEs. As shown in Figure 3-18, when the service is transmitted
from NE3 to NE4, NE3→NE4 is the short path, and NE3→NE2→NE1→NE4 is the long path.
1-SL4D-1 1-SL4D-2
NE4:
NE1
Line board Line board Line board
1-SL4D-1 1-SL4D-2 2-SL1D-1
1-SL4D-2 1-SL4D-1
2-SL1D-1 2-SL1D-1 3-SP3D
MSP ring 线路板

NE2 NE4 5×E1
Non-protection
1-SL4D-1 1-SL4D-2 chain NE5
VC4-1:1-5(VC12) Line board Tributary board
2-SL1D-1 3-SP3D
NE3
1-SL4D-2 1-SL4D-1
VC4-1:1-5(VC12)
Line board
NE3:
5×E1
Tributary board Line board Tributary board
1-SL4D-1 3-SP3D
Traffic direction of the MSP ring
Traffic direction of the non-protection chain

The configuration of the services on the two-fiber bidirectional MSP ring with a non-protection
chain is independent of the creation of the protection subnets for the MSP and for the non-
protection chain. To configure the services on the two-fiber bidirectional MSP ring with a non-
protection chain, configure the SDH services from the tributary board to the line board on the
source and sink NEs and configure pass-through services on the intermediate NEs, if the
protection subnet is already created.

System
Prerequisite
details about how to create the protection subnet, see2.6.1 Configuring a Non-Protection
Chain and 2.6.3 Creating an MS Ring Protection Subnet.
Procedure
2. Click Create on the lower-right pane to display the Create SNCP Service dialog box. Set

This
Example


l received on the same path. That is, the services are
3-18.
Source VC4 - -

Timeslot Range between NE3 and NE5. Hence, the service source
VC4-1.

Range(e.g. between NE3 and NE5. Hence, the service sink
Activate Yes -
Immediately
Step 2 Refer to Step 1 and configure the SDH services of NE5. Set the parameters as follows.

System

This
Example

on the same path. That is, the services are Bidirectional
services.
3-18.
Source VC4 - -
Source Timeslot 1-5 In this example, five E1 services are configured between
Range(e.g.1,3-6) NE3 and NE5. Hence, the service source occupies
VC-12s 1-5.
VC4-1.
Range(e.g.1,3-6) NE3 and NE5. Hence, the service sink occupies VC-12s
1-5.
Activate Yes -
Immediately

This
Example


l received on the same path. That is, the services are

System

This
Example
Source VC4 VC4-1 In this example, the service source uses the timeslots
of VC4-1.

Timeslot Range between NE3 and NE5. Hence, the service sink
VC4-1.

Range(e.g. between NE3 and NE5. Hence, the service sink
Activate Yes -
Immediately
SCB Board.
----End
Relevant Task

The configuration of services on a two-fiber bidirectional MSP ring with a non-protection chain
is independent of the creation of protection subnets for the MSP and for the non-protection chain.
To configure services on a two-fiber bidirectional MSP ring with a non-protection chain,
configure SDH services from the tributary board to the line board on the source and sink NEs
and configure pass-through services on the intermediate NEs, if the protection subnet has already
been created. The following part describes how to configure services on an MSP ring with a
non-protection chain in an end-to-end manner.
Prerequisite

System
l A protection subnet must be created and must be the same as the actual topology. For details
about how to create a protection subnet, see 2.6.1 Configuring a Non-Protection Chain
and 2.6.4 Creating a Linear MS Protection Subnet.
l The operator must understand the information provided in 3.10.2 Signal Flow and
Timeslot Allocation.
Procedure
Step 1 Create a VC-4 server trail.
1. Choose Service > SDH Trail > Create SDH Trail from the Main Menu.
3. Double-click NE3 and NE5 on the right of the Main Topology, and click Apply. Then,
click Close in the Operation Result dialog box that is displayed.
Trail to query the created VC4 server trail.

1. In Create SDH Tail, configure associated parameters as follows. Set Level to VC12, and
take default values for other parameters.
2. Double-click the NE3 on the right of the Main Topology. The Select Board Port-
Source dialog box is displayed. Select the required PDH board and Tributary Port, and
then click OK.
3. Configure NE5 using the method described in Step 2.2.
5. In Available Timeslots/Port, select the timeslots or ports to be duplicated, and click
Add.

System
SCB Board.
----End
Relevant Task
3.11 Protection Configuration Parameters

You need to set the necessary parameters when configuring the protection such as MSP, SNCP
for an NE.
3.11.1 SNCP Configuration

You need to set the necessary parameters when configuring the SNCP for an NE.
3.11.2 Configuring the Multiplex Section Protection
You need to set the necessary parameters when configuring the multiplex section protection
(MSP).
3.11.1 SNCP Configuration

You need to set the necessary parameters when configuring the SNCP for an NE.
Table 3-1 lists the parameters for configuring the SNCP.
Table 3-1 Parameters for configuring the SNCP
Field Value Description
Service Type SNCP Specifies the type of the new

SNCP service.
Revertive Mode Non-Revertive, Revertive Specifies whether the services

Default: Non-revertive can be switched from the
protection channel to the
working channel after the
working channel is restored.
If you set this field to
Revertive, the services can be
switched from the protection
channel to the working
channel. If you set this
parameter to Non-Revertive,
the services cannot be
switched from the protection
channel to the working
channel.

System
WTR Time (s) Example: 600 Specifies the wait-to-restore

(WTR) time of the NE.
When the time after the
former working channel is
restored to normal reaches the
set WTR time, a revertive
switching occurs. This field is
available only when
Revertive Mode is set to
Revertive.
Hold-Off Time (100 ms) 0 to 100 Specifies the hold-off time of

Default: 0 the NE.
If Hold-Off Time (100 ms) is
set to 0, you do not need to set
a specific hold-off time.
Source Board Example: 1-SL1D-1 Displays the slot ID, board

(SDH-1) name, port number, and port
name at the source end.
Sink Board Example: 3-SP3D Displays the slot ID, board

name, port number, and port
name at the sink end.
Source VC4 Example: VC4-1 Specifies the VC-4 timeslot at

the source end.
One VC-4 timeslot can
contain a maximum of 63
VC-12 timeslots.
Sink VC4 - Specifies the VC-4 timeslot at

the sink end.
Source Timeslot Range(eg.1, Example: 1-5 Specifies the timeslot range at

3-6) the source end.
3.11.2 Configuring the Multiplex Section Protection

You need to set the necessary parameters when configuring the multiplex section protection
(MSP).
Table 3-2 lists the parameters for configuring the MSP.

System
Table 3-2 Parameters for configuring the MSP

Name For Example: two-fiber Indicates the name of the

bidirectional multiplex protection subnetwork. Th
section shared protection name of a new protection
ring_1 subnetwork is automatically
generated. You can rename
the protection subnetwork
according to the
requirements.
Level If Assigned by VC4 is not Indicates the new capacity

selected, the values are level of a protection
STM-1, STM-4, STM-16, subnetwork. The new
STM-64, and STM-256. capacity level of a protection
If Assigned by VC4 is subnetwork must be the same
selected, the values are as the transmission rate of the
STM-2, STM-4, STM-6, ..., line boards that form the
STM-254, and STM-256. protection subnetwork.
NOTE CAUTION
When selecting an incorrect
l The OptiX OSN 550 capacity level, you fail to create
supports only STM-1, a protection subnetwork.
STM-4 and STM-16
levels.
l For LMSP, Assigned by
VC4 is not supported.
Resource Sharing - Resource sharing indicates

that two protection
subnetworks can share one
physical resource. If multiple
protection subnetworks are
created on a fiber, the second
and later protection
subnetworks share the
resources on the fiber.
NOTE
The OptiX OSN 550 does not
support this parameter.

System
Assigned by VC4 Selected, Deselected Indicates that different VC-4s

correspond to different
protection subnetworks. You
can group VC-4s in the
optical fiber into different
protection subnets to protect
virtual optical channels. This
means that certain VC-4s in
the fiber can be allocated to a
protection subnetwork. For
example, in the case of an
STM-16 fiber, the former four
VC-4s can be allocated for an
STM-4 MSP, and the
following four VC-4s can be
allocated for channel
protection.
NOTE
For LMSP, Assigned by VC4 is
not supported.
Node For example: NE70 Displays the selected NE.
Link For example: NE140-NE141 Displays the fiber link of the

Ring 1 protection subnetwork.
Physical Information For example: 1-SL1Q-1 Displays the line board

(SDH-1)-1-SL1Q-2(SDH-1) resource used by the fiber
link.
VC4 For example: 1 to 4 If Assigned by VC4 is

selected in Step 1, you can
specify the VC-4 resource
used by the protection
subnetwork in Step 2.
Subnet Name For example: Two-fiber Displays the name of the

bidirectional multiplex protection subnetwork.
section shared protection
ring_1
Subnet Type 2f_MS SPRing, 2f_MS Displays the type of the

DPRing, 1+1 Linear MSP, protection subnetwork.
M:N Linear MSP,
Unprotected Ring,
Unprotected Chain
WTR Time (s) For example: 600 Displays the switching WTR
time of the protection
subnetwork.
Revertive Mode Non-Revertive, Revertive Displays the revertive mode

of the protection subnetwork.

System
Switching Mode Single-Ended Switching, The Switching Mode

Dual-Ended Switching parameter specifies the
Default: Single-Ended switching mode of the linear
Switching MSP.
You can click 7.130
Switching Mode (MSP) to
information.

System
Configuration Guide 4 Configuring Ethernet Services
4 Configuring Ethernet Services
About This Chapter
In compliance with ITU-T G.8011x/Y.1307x, Huawei MSTP equipment supports Ethernet

private line (EPL), Ethernet virtual private line (EVPL), Ethernet private local area network
(EPLAN), and Ethernet virtual private local area network (EVPLAN) services.
4.1 Service Types

4.2 Basic Concepts
Before you configure Ethernet boards with services, you need to learn the basic concepts
including external port, internal port, logical port, and bridge so that you can understand the
service configuration process and the signal flow when the boards process the services.
4.3 Flow of Configuring Ethernet Services
This topic describes the configuration processes related to Ethernet services. Before you
configure Ethernet services according to the flow, you need to complete the basic configurations
of the NEs according to the flow of creating a network.
4.4 Configuring EPL Services on an Ethernet Transparent Transmission Board
EPL services provide the point-to-point Ethernet transparent transmission solution with the
bandwidth exclusively occupied. EPL services are applicable when the communication
equipment that is used to access the client-side data in the transmission network does not support
VLANs or when the VLAN planning must be kept secret to the network operator.
4.5 Configuring EPL Services on an Ethernet Switching Board
4.6 Configuring PORT-Shared EVPL (VLAN) Services
The PORT-shared EVPL (VLAN) service is applicable when the services of multiple users
received from the same external port on the Ethernet board at a station are transmitted on different
VCTRUNKs to another station or to another external port of the station.

System
4 Configuring Ethernet Services Configuration Guide
4.7 Configuring VCTRUNK-Shared EVPL (VLAN) Services

When the data of multiple users without VLAN tags sent to a transmission network is transmitted
on the same VCTRUNK, the VCTRUNK-shared EVPL (VLAN) service is used to isolate the
data by adding VLAN tags. In this way, the bandwidth is shared on the SDH side.
4.8 Configuring EPLAN Services (IEEE 802.1d Bridge)
The EPLAN service (IEEE 802.1d bridge) provides a LAN solution for multipoint-to-multipoint
convergence. This service applies where the user-side data communication equipment connected
to the transmission network does not support VLANs or where the VLAN planning is kept secret
from the network operator.
4.9 Configuring EVPLAN Services (IEEE 802.1q Bridge)
The EVPLAN service (IEEE 802.1q bridge) provides an LAN solution for multipoint-to-
multipoint convergence. This service applies in cases where user-side data communication
equipment connected to the transmission network does not support VLANs or where the VLAN
planning is open to the network operator.
4.10 Configuring EVPLAN Services (IEEE 802.1ad Bridge)
The QinQ technology provides a cheap and easy solution for Layer 2 virtual private networks
(VPNs). The IEEE 802.1ad bridge uses the QinQ technology to provide the VPN solution, thus
facilitating the identifying, differentiating and grooming EVPLAN services.
4.11 Ethernet Port Configuration Parameters
Before configuring an Ethernet service, you need to configure the corresponding Ethernet ports.
4.12 Ethernet Service Configuration Parameters
Ethernet services can be classified into Ethernet private line services and Ethernet private
network services. Ethernet private line services include EPL services and EVPL services.
Ethernet private network services include EPLAN services and EVPLAN services.

System
4.1 Service Types

EPL Services
Two nodes are used to access EPL services and implement transparent transmission of the
Ethernet services of the users. The service of one user occupies one VCTRUNK and need not
share the bandwidth with the services of the other users. Hence, in the case of EPL services, a
bandwidth is exclusively occupied by the service of a user and the services of different users are
isolated. In addition, the extra QoS scheme and security scheme are not required.
Figure 4-1 EPL services

User A1 User A2
NE 1 NE2
Port1 VCTRUNK1 Port1
Port2 Port2
VCTRUNK2
User B1 User B2
The corresponding relations between the PORTs (namely, external ports) and the VCTRUNKs
are listed in Table 4-1.
Table 4-1 Corresponding relations between the external ports and the VCTRUNKs (EPL
services)
NE1 NE2
User A1 PORT1←→VCTRUNK1 VCTRUNK1←→PORT1 User A2
User B1 PORT2←→VCTRUNK2 VCTRUNK2←→PORT2 User B2
EVPL Services
In the case of EVPL services, services of different users share the bandwidth. Hence, the VLAN/
QinQ scheme needs to be used for differentiating the services of different users. If the services
of different users need to be configured with different quality levels, you need to adopt the
corresponding QoS scheme. EVPL services are classified into two types, depending on whether
the PORT or VCTRUNK is shared.

System
l PORT-shared EVPL services

As shown in Figure 4-2, the services of different users are accessed through a PORT at a station,
and are then isolated from each other by using the VLAN IDs. Services are transmitted to other
PORTs at this station through different VCTRUNKs.
Figure 4-2 PORT-shared EVPL services

User C2
User C1 NE 1 NE2
Port1
VLAN 100 VCTRUNK1 Port1
VLAN 200 VCTRUNK2 Port2
User C3
The corresponding relations between the PORTs and the VCTRUNKs are provided in Table
4-2.
Table 4-2 Corresponding relations between the PORTs and the VCTRUNKs (PORT-shared
EVPL services)
NE1 NE2
User C1 PORT1←→VCTRUNK1 VCTRUNK1←→PORT1 User C2
PORT1←→VCTRUNK2 VCTRUNK2←→PORT2 User C3
l VCTRUNK-shared EVPL services Ethernet boards support the convergence and

distribution of EVPL services by using the following modes:
– VLAN tag-based convergence and distribution of EVPL services
– QinQ technology-based convergence and distribution of EVPL services
As shown in Figure 4-3, the services of different users are isolated by using the VLAN/QinQ
scheme. Hence, the services of different users can be transmitted in the same VCTRUNK.
Figure 4-3 VCTRUNK-shared EVPL services

User D1 User D2
NE 1 NE2
Port1 Port1
VCTRUNK1
Port2 Port2
User E1 User E2

System
The corresponding relations between the PORTs and the VCTRUNKs are provided in Table
4-3.
Table 4-3 Corresponding relations between the PORTs and the VCTRUNKs (VCTRUNK-
shared EVPL services)
NE1 NE2
User D1 PORT1←→VCTRUNK1 VCTRUNK1←→PORT1 User D2
User E1 PORT2←→VCTRUNK1 VCTRUNK1←→PORT2 User E2
EPLAN Services
The EPLAN services can be accessed from a minimum of two nodes. Hence, the services of
different users need not share the bandwidth. That is, in the case of EPLAN services, a bandwidth
is exclusively occupied by the service of a user and the services of different users are isolated.
In addition, the extra QoS scheme and security scheme are not required. The EPLAN services
have more than one node. Hence, the nodes need to learn the MAC addresses and forward data
according to MAC addresses. Therefore, Layer 2 switching is realized.
As shown in Figure 4-4, three branches of user F need to communicate with each other. On
NE1, the IEEE 802.1d bridge is established to achieve EPLAN services. The IEEE 802.1d bridge
can create the MAC address-based forwarding table, which is periodically updated by using the
self-learning function of the system. The accessed data can be forwarded or broadcast within
the domain of the IEEE 802.1d bridge according to the destination MAC addresses.
Figure 4-4 EPLAN services (IEEE 802.1d bridge)
NE3
U2000
NE2 NE4
PORT1 NE1 PORT1
F2 F3
PORT5
IEEE 802.1d bridge
VCTRUNK
VCTRUNK1 VCTRUNK2
F1
PORT5

System
EVPLAN Services
EVPLAN services of different users need to share the bandwidth. Hence, the VLAN/QinQ
scheme needs to be used for differentiating the data of different users. If the services of different
users need to be configured with different quality levels, you need to adopt the corresponding
QoS scheme.
As shown in Figure 4-5, three branches of user G need to communicate with each other. Services
of user G need to be isolated from the services of user H. Hence, the IEEE 802.1q bridge needs
to be established on NE1 to achieve EVPLAN services.
IEEE 802.1q bridge: IEEE 802.1q bridge supports isolation by using one layer of VLAN tags.
This bridge checks the contents of the VLAN tags that are in the data frames and performs Layer
2 switching according to the destination MAC addresses and VLAN IDs.
Figure 4-5 EVPLAN services (IEEE 802.1q bridge)
NE3
NM
PORT2 PORT2
H2 NE2 NE4
H3
PORT1 NE1 PORT1
G2 G3
H1 G1
PORT6 PORT5
VCTRUNK
IEEE 802.1q bridge IEEE 802.1q bridge

VLAN 200 VLAN 100
VCTRUNK1 VCTRUNK2 VCTRUNK1 VCTRUNK2
PORT6 PORT5
As shown in Figure 4-6, the VoIP services from user M and the HSI services from user N need
to respectively access the VoIP server and the HSI server. In this case, the operator needs to
separately groom the VoIP services and HSI services, and isolate the data on the transmission
network side. On NE1, the IEEE 802.1ad bridge must be established to support the EVPLAN
services.
IEEE 802.1ad bridge: The IEEE 802.1ad bridge supports data frames with two layers of VLAN
tags. This bridge adopts the outer S-VLAN tags to isolate different VLANs and supports only
the mounted ports whose attributes are C-Aware or S-Aware. This bridge supports the following
switching modes:
l This bridge does not check the contents of the VLAN tags that are in the packets and
performs Layer 2 switching according to the destination MAC addresses of the packets.

System
l This bridge checks the contents of the VLAN tags that are in the packets and performs
Layer 2 switching according to the destination MAC addresses and the S-VLAN IDs of the
packets.
Figure 4-6 EVPLAN services (IEEE 802.1ad bridge)
NE3
NM
Service C-VLAN Service C-VLAN
VoIP 10 VoIP 10
HSI 20 HSI 20
PORT1 PORT1
User M NE2 NE4 User N
8 NE1 11
VoIP 11 8
HSI
PORT5 PORT6
VCTRUNK
IEEE 802.1ad bridge IEEE 802.1ad bridge

S-VLAN 100 S-VLAN 200
PORT5 PORT6
4.2 Basic Concepts

Before you configure Ethernet boards with services, you need to learn the basic concepts
including external port, internal port, logical port, and bridge so that you can understand the
service configuration process and the signal flow when the boards process the services.
4.2.1 Formats of Ethernet Frames

To implement the VLAN and QinQ functions, the IEEE 802.1q and IEEE 802.1ad protocols
define different formats of the Ethernet frames, which contain different VLAN information.
4.2.2 Internal Ports and External Ports
External ports on Ethernet boards are used to access the services on the user side. Internal ports
on Ethernet boards are used to encapsulate and map the services to the transmission network for
transparent transmission.
4.2.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
4.2.4 Flow Control
When the data processing/transferring capability of the equipment fails to handle the flow
received at the port, congestion occurs on the line. To reduce the number of discarded packets
due to buffer overflowing, proper flow control measures must be taken.

System
4.2.5 Encapsulation and Mapping Protocol

To ensure that Ethernet frames can be transparently transmitted over the optical transmission
network, the Ethernet frames need to be encapsulated and mapped into VC containers at the
access point. The encapsulation and mapping protocols used by the Ethernet service board
include the high-level data link control (HDLC), link access procedure - SDH (LAPS), and
generic framing procedure (GFP).
4.2.6 Virtual Concatenation
The rate of the Ethernet service does not adapt to the rate of the standard VC container. Hence,
if you directly map the Ethernet service data into a standard VC container, there is a great waste
of the transmission bandwidth. To solve the problem, use the virtual concatenation technology
to concatenate many standard VC containers to a large VC container that adapts to the rate of
the Ethernet service.
4.2.7 Tag Attribute
When data frames are received on or transmitted from a port on an Ethernet board, the processing
mode of the data frames is determined by the tag attributes of the port.
4.2.8 Bridge
A bridge is a functional unit that is used to implement the interconnection between two or more
LANs.
4.2.1 Formats of Ethernet Frames

To implement the VLAN and QinQ functions, the IEEE 802.1q and IEEE 802.1ad protocols
define different formats of the Ethernet frames, which contain different VLAN information.
To implement the VLAN function, the IEEE 802.1q protocol defines the Ethernet frame format
that contains the VLAN information. Compared with the ordinary Ethernet frame, the frame
with the format defined by the IEEE 802.1q protocol is added with a four-byte header.
To implement VLAN mesting (QinQ), the IEEE 802.1ad protocol defines two VLAN tag types.
See Figure 4-7. The VLAN tag types are defined to differentiate the services on the client side
and the services on the supplier service side.
l The VLAN tag used on the client side is represented as C-VLAN, of which the frame format
is the same as the frame format defined by the IEEE 802.1q protocol.
l The VLAN tag used on the supplier service side is represented as S-VLAN.

System
Figure 4-7 Formats of Ethernet frames

802.1q frame format
Destination Source MAC FCS Check

Address VLAN Length/Type Data
MAC Address Character
Variable
6 bytes 6 bytes 4 bytes 2 bytes 4 bytes
length
Format of the frame with

one C-VLAN tag
Destination Source MAC FCS Check

Address C-VLAN Length/Type Data
MAC Address Character
6 bytes 6 bytes 4 bytes 2 bytes Variable 4 bytes

length
Format of the frame with
one S-VLAN tag nested
with one C-VLAN tag
Destination Source MAC S-VLAN C-VLAN Data FCS Check

Length/Type
MAC Address Address Character
Variable
6 bytes 6 bytes 4 bytes 4 bytes 2 bytes 4 bytes
length
The length of the data field is variable. maximum length of the data field depends on the
maximum frame length that the ports of the equipment support.
The four-byte S-VLAN or C-VLAN field is divided into two sub-fields: the tag protocol ID
(TPID) and the tag control Information (TCI).
Both the TPID and TCI consist of two bytes. See Figure 4-8.
Figure 4-8 Positions of the TPID and TCI in the frame structure
S-VLAN C-VLAN
Destination Source MAC TPID TCI TPID TCI Length/Type Data FCS Check
MAC Address Address Character
Variable
6 bytes 6 bytes 2 2 bytes 2 bytes 2 bytes 2bytes 2 bytes 4 bytes
length
l TPID structure
The TPID consists of two bytes and indicates the VLAN tag type. TPID of the C-VLAN is
always 0x8100 whereas the TPID of the S-VLAN can be customized. Refer to Table 4-4.
Table 4-4 Tag types defined by using the TPID

Tag Type Name Value
C-VLAN Tag 802.1q Tag Protocol Type 0x8100

System
Tag Type Name Value
S-VLAN Tag 802.1q Service Tag Type Customizable
NOTE
The IEEE 802.1ad specifies the TPID of the S-VLAN to 0x88a8. In actual application, the setting of TPID
for the S-VLAN tag varies according to the equipment manufacturer. To ensure compatibility between
interconnected equipment, it is recommended that you set the TPIDs of the S-VLAN tags of the
interconnected equipment to the same value within 0X600-FFFF.
l TCI structure
The TCI structure of the S-TAG is basically the same as the TCI structure of the C-TAG. VLAN
ID (VID) field consists of 12 bits and ranges from 0 to 4095. The difference is that the TCI of
the S-TAG contains the drop eligible (DE) indication and works with the priority code point
(PCP) to indicate the priority of the S-TAG frame.
The TCI structures of the C-TAG and S-TAG are shown in Figure 4-9 and Figure 4-10.
Figure 4-9 TCI structure of the C-TAG
Octets: 1 2
PCP CFI VID VID
Bits: 8 6 5 4 1 8 1
The TCI field of the C-TAG consists of the following bytes:
l PCP: three bits

l CFI: one bit
Figure 4-10 TCI structure of the S-TAG
Octets: 1 2
PCP DE VID VID
Bits: 8 6 5 4 1 8 1
The TCI field of the S-TAG consists of the following bytes:
l PCP: three bits

l DE: one bit
l VID: 12 bits

System
4.2.2 Internal Ports and External Ports

External ports on Ethernet boards are used to access the services on the user side. Internal ports
on Ethernet boards are used to encapsulate and map the services to the transmission network for
transparent transmission.
External ports on Ethernet boards (that is, external physical ports) are also referred to as client-
side ports or user-side ports, which are used to access the Ethernet services on the user side.
Internal ports on Ethernet boards (that is, internal VCTRUNKs) are also referred to as system-
side ports or backplane-side ports in certain cases, which are used to encapsulate and map the
services to the SDH side.
VCTRUNKs are VC-based transmission paths, which can be implemented by using the adjacent
concatenation or virtual concatenation technology. On the U2000 window, paths are bound to
specify the bandwidth of different granularities for a VCTRUNK port.
Figure 4-11 External ports and internal ports on Ethernet boards

External port VCTRUNK port
Backplane
Cross-
Interface Service Encapsulation/ Interface connect unit
module processing Mapping conversion
module module module Cross-
connect unit
Ethernet board
4.2.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
The working modes of the interconnected ports on the equipment at both ends must be the same.
Otherwise, the services are affected.
If the working mode of the port on the opposite equipment is full duplex and if the working
mode of the port on the local equipment is auto-negotiation, the local equipment works in the
half-duplex mode. That is, the working modes of the interconnected ports at both ends are
different, and thus packets may be lost. Hence, when the working mode of the port on the opposite
equipment is full duplex, you need to set working mode of the port on the local equipment to
full duplex.
NOTE
When the interconnected ports at both sides work in the auto-negotiation mode, the equipment at both sides
can negotiate the flow control through the auto-negotiation function.
The auto-negotiation function uses fast link pulses (FLPs) and normal link pulses (NLPs) to
transfer information of the working mode so that no packet or upper layer protocol overhead
needs to be added.

System
NOTE
This topic considers FE electrical interfaces as an example to describe how to implement the auto-negotiation
function.
The FLP is called the 100BASE-T link integrity test pulse sequence. Each set of equipment on
the network must be capable of issuing FLP bursts in the case of power-on, issuing of
management commands, or user interaction. The FLP burst consists of a series of link integrity
test pulses that form an alternating clock/data sequence. Extraction of the data bits from the FLP
burst yields a link code word that identifies the working modes supported by the remote
equipment and certain information used for the negotiation and handshake mechanism.
To maintain interoperability with the existing 100BASE-T equipment, the auto-negotiation
function also supports the reception of 100BASE-T compliant link integrity test pulses. The
10BASE-T link pulse activity is referred to as the NLP sequence. equipment that fails to respond
to the FLP burst sequence by returning only the NLP sequence is treated as the 100BASE-T
compatible equipment.
The first pulse in an FLP burst is defined as a clock pulse. Clock pulses within an FLP burst
occur at intervals of 125 us. Data pulses occur in the middle of two adjacent clock pulses. The
positive pulse represents logic "1" and the absence of a pulse represents logic "0". An FLP burst
consists of 17 clock pulses and 16 data pulses (if all data bits are 1). The NLP waveform is
simpler than the FLP waveform. NLP sends a positive pulse every 16 ms when no data frame
needs to be transmitted.
Figure 4-12 Waveform of a single FLP
T3 T1
Clock pulses
T2
First bit on wire
Data 1 1 0 1 …
Encoding D D D D
0 1 2 3 …
T1: 100 ns T2: 62.5 us T3: 125 us
Figure 4-13 Consecutive FLP and NLP bursts

T5
T4
FLP bursts
NLPs
T4: 2 ms T5: 16 ms

System
4.2.4 Flow Control

When the data processing/transferring capability of the equipment fails to handle the flow
received at the port, congestion occurs on the line. To reduce the number of discarded packets
due to buffer overflowing, proper flow control measures must be taken.
The half-duplex Ethernet port applies the back-pressure mechanism to control the flow. The full-
duplex Ethernet port applies PAUSE frames to control the flow. Currently, the half-duplex
Ethernet function is not widely applied. Hence, the flow control function realized by Ethernet
service boards is used for the full-duplex Ethernet ports.
The flow control function realized by Ethernet service boards is classified into two types: auto-
negotiation flow control and non-auto-negotiation flow control.
Auto-Negotiation Flow Control

When the Ethernet port works in the auto-negotiation mode, you can adopt the auto-negotiation
flow control function. The auto-negotiation flow control modes include the following:
l Enable dissymmetric flow control
The port can transmit PAUSE frames in the case of congestion but cannot process the
received PAUSE frames.
l Enable symmetric flow control
The port can transmit PAUSE frames and process the received PAUSE frames.
l Enable symmetric/dissymmetric flow control
The port has the following abilities:
– Transmits and processes PAUSE frames.
– Transmits PAUSE frames but cannot process the received PAUSE frames.
– Processes the received PAUSE frames but cannot transmit PAUSE frames.
l Disable
Disables the auto-negotiation flow control function.
Non-Auto-Negotiation Flow Control

When the Ethernet port works in a fixed working mode, you can adopt the non-auto-negotiation
flow control function. The non-auto-negotiation flow control modes include the following:
l Send only
The port can transmit PAUSE frames in the case of congestion but cannot process the
received PAUSE frames.
l Receive only
The port can process the received PAUSE frames but cannot transmit PAUSE frames in
the case of congestion.
l Send and receive
The port can transmit PAUSE frames and process the received PAUSE frames.
l Disable
The port does not support the auto-negotiation flow control function.

System
Realization Principle
The realization principle of the flow control function is described as follows:
1. When congestion occurs in the receive queue of an Ethernet port (the data in the receive
buffer exceeding a certain threshold) and the port is capable of sending PAUSE frames,
the port sends a PAUSE frame to the opposite end. pause-time value in the frame is N
(0<N≤65535).
2. If the Ethernet port at the opposite end is capable of processing PAUSE frames, this Ethernet
port stops sending data within a specified period of time N (the unit is the time needed for
sending 521 bits) after receiving the PAUSE frame.
3. If the congestion at the receive port is cleared (the data in the receive buffer is below a
certain threshold) but the pause-time does not end, the port sends a PAUSE frame whose
pause-time is 0 to notify the opposite end to send data.
IEEE 802.3 defines the format of the PAUSE frame as follows:
l Destination address: 01-80-C2-00-00-01 (multicast address)

l Source address: MAC address of the source port
l Type/Length: 88-08 (MAC control frame)
l MAC control code: 00-01 (PAUSE frame)
l MAC control parameter: pause-time (two bytes)
Figure 4-14 Structure of the PAUSE frame
Destination address 01-80-C2-00-00-01 6 octets
Source address XX-XX-XX-XX-XX-XX 6 octets
Type/Length 88-08 2 octets
MAC control opcode 00-01 2 octets
MAC control parameter

XX-XX 2 octets
(pause-time)
Reserved
4.2.5 Encapsulation and Mapping Protocol

To ensure that Ethernet frames can be transparently transmitted over the optical transmission
network, the Ethernet frames need to be encapsulated and mapped into VC containers at the
access point. The encapsulation and mapping protocols used by the Ethernet service board
include the high-level data link control (HDLC), link access procedure - SDH (LAPS), and
generic framing procedure (GFP).

System
HDLC
The HDLC is a general data link control procedure. When using the HDLC protocol, the system
encapsulates data services into HDLC-like frames as information bits and maps the frames into
SDH VC containers.
LAPS
The LAPS is also a data link control procedure. It is optimized based on the HDLC. The LAPS
complies with ITU-T X.86.
GFP
The GFP is the most widely applied general encapsulation and mapping protocol. It provides a
general mechanism to adapt higher-layer client signal flows into the transport network and can
map the variable-length payload into the byte-synchronized transport path. The client signals
can be protocol data units (PDU-oriented, such as IP/PPP and Ethernet), block code data (block-
code oriented, such as Fiber Channel and ESCON), or common bit data streams. The GFP
protocol complies with ITU-T G.7041.
The GFP defines the following modes to adapt client signals:
l Frame-mapped GFP (GFP-F)
The GFP-F is a PDU-oriented processing mode. It encapsulates the entire PDU into the
GFP payload area and makes no modification on the encapsulated data. It determines
whether to add a detection area for the payload area, depending on requirements.
l Transparent GFP (GFG-T)
The GFP-T is a block-code (8B/10B code block) oriented processing mode. It extracts a
single character from the received data block and maps the character into the fixed-length
GFP frame.
4.2.6 Virtual Concatenation

The rate of the Ethernet service does not adapt to the rate of the standard VC container. Hence,
if you directly map the Ethernet service data into a standard VC container, there is a great waste
of the transmission bandwidth. To solve the problem, use the virtual concatenation technology
to concatenate many standard VC containers to a large VC container that adapts to the rate of
the Ethernet service.
The concatenation is defined in ITU-T G.707 and contains contiguous concatenation and virtual
concatenation. Both concatenation methods provide concatenated bandwidth of X times
Container-N at the path termination.
Contiguous concatenation concatenates the contiguous VC-4s in the same STM-N into an entire
structure to transport. It maintains the contiguous bandwidth throughout the whole transport.
Virtual concatenation concatenates many individual VC containers (VC-12 containers, VC-3
containers, or VC-4 containers) into a bit virtual structure to transport. The virtual concatenation
breaks the contiguous bandwidth into individual VCs, transports the individual VCs, and
recombines these VCs to a contiguous bandwidth at the transmission termination point.
In the case of virtual concatenation, transport of each VC container may occupy different paths
and there may be a transport delay difference between VC containers. Hence, there are
difficulties to restore the client signal. Virtual concatenation requires concatenation functionality
only at the path termination equipment and it can flexibly allocate bandwidth. Hence, the virtual
concatenation technology is widely used.

System
Virtual concatenation is available in two types: virtual concatenation in a higher order path and
virtual concatenation in a lower order path. A higher order virtual concatenation VC4-Xv
provides a payload of X Container-4s (VC-4s). The payload is mapped individually into X
independent VC-4s. Each VC-4 has its own POH. A lower order virtual concatenation VC-12-
Xv provides a payload of X Container-12s (VC-12s). The payload is mapped individually into
X independent VC-12s. Each VC-12 has its own POH. It is the same case with the virtual
concatenation of VC-3s.
VC4-Xv and VC-3-Xv

The virtual container that is formed by a VC4-Xv/VC-3-Xv can be mapped into X individual
VC-4/VC-3s that form the VC4-Xv/VC-3-Xv. Each VC-4/VC-3 has its own POH. POH has the
same specifications as the ordinary VC-4 POH. The H4 byte in the POH is used for the virtual
concatenation-specific multiframe indicator (MFI) and sequence indicator (SQ).
MFI indicates the position of a frame in the multiframe. Each frame sent by the source carries
the MFI information. The sink end combines the frames with the same MFI into the C-n-Xv.
MFI includes MFI-1 and MFI-2. MFI-1 is transmitted by bits 5-8 of the H4 byte and ranges from
0 to 15. MFI-2 is transmitted by the two frames of which the MFI-1 is "0" and "1" in the
multiframe. Bits 1-4 of the H4 bytes of the two frames indicate the higher four bits and lower
four bits of the MFI-2 respectively. Hence, the MFI-2 ranges from 0 to 255. That is, a multiframe
consists of 4096 frames and the period is 512 ms.
SQ indicates the position of a frame in the C-n-Xv. The source end inserts the SQ information
into the frame according to the payload allocation sequence. The sink end determines the
sequence to extract the payload from the frames that form C-n-Xv according to the SQ. SQ is
transmitted by the two frames of which the MFI-1 is "14" and "15" in the multiframe. Bits 1-4
of the H4 bytes of the two frames indicate the higher four bits and lower four bits of the SQ
respectively.

System
Figure 4-15 VC-3-Xv/VC4-Xv multiframe and sequence indicator

C-3-X/C-4-X C-3-Xv/C-4-Xv
SQ = X-1
H
1 X SQ = 0 =0
POH
MFI-1 = 0 =0
MFI-2 = 0 X-1
SQ = 0 =1
POH
MFI-1 = 1 =0
MFI-2 = 0
Multiframe (MF)
SQ = X-1
H
SQ = 0 = 15
POH
MFI-1 = 15 = 0
MFI-2 = 0 X-1
SQ = 0 =0
POH MFI-1 = 0 = 15
MFI-2 = 1
H SQ = X-1
SQ = 0 = 15
POH
MFI-1 = 15 = 255
MFI-2 = 255 X-1
SQ = 0 =0
POH
MFI-1 = 0 =0
MFI-2 = 0
With the MFI and SQ, the sink end can correctly restore the position of each frame in the C-n-
Xv to prevent the frame alignment problem due to the different propagation delays of the frames.
VC-12-Xv
The virtual container that is formed by a VC-12-Xv can be mapped into X individual VC-12s
which form the VC-12-Xv. Each VC-12 has its own POH. POH has the same specifications as
the ordinary VC-12 POH. Bit 2 of the K4 byte in the POH is used for the virtual concatenation-
specific frame count and sequence indicator.
Bit2s of the K4 bytes in every 32 multiframes (one multiframe comprising four VC-12s) are
extracted to form a 32-bit character string to express the frame count and sequence indicator.
Bits 1-5 of the string express the frame count, whose value range is between 0 and 31. structure
formed by 32 multiframes has 128 frames. Hence, the resulting overall multiframe is 4096 frames
with the period of 512 ms. Bits 6-11 of the string express the sequence indicator. The frame
count/sequence indicator in the VC-12-Xv has the same usage as the multiframe indicator/
sequence indicator in the VC4-Xv/VC-3-Xv.
4.2.7 Tag Attribute

When data frames are received on or transmitted from a port on an Ethernet board, the processing
mode of the data frames is determined by the tag attributes of the port.
The tags for the port on an Ethernet board are available in three types: tag aware, access, and
hybrid.

System
Table 4-5 Processing mode of data frames on ports with different tags
Direction Data Frame Type Processing Mode
Tag aware Access Hybrid
Ingress port Data frames with The data frames are The data frames are The data frames are
VLAN tags transparently discarded. transparently
transmitted. transmitted.
Data frames without The data frames are The VLAN tags that contain Default VLAN
VLAN tags discarded. ID and VLAN Priority are added to the data
frames, and then the data frames are
transparently transmitted.
Egress port Data frames with The data frames are After the VLAN l If the VLAN IDs
VLAN tags transparently tags are stripped contained in the
transmitted. from the data data frames are
frames, the data Default VLAN
frames are ID, the VLAN
transparently tags are stripped
transmitted. from the data
frames, and then
the data frames
are transparently
transmitted.
l If the VLAN IDs
contained in the
data frames are
not Default
VLAN ID, the
data frames are
transparently
transmitted.
NOTE
The tag setting is valid only when the following conditions are met:
l Port Type of the port is set to PE or UNI.
l The entry detection function is enabled. When the Ethernet switching board works in the Ethernet
transparent transmission state and when the entry detection function is disabled, the port transparently
transmits the received data frames regardless of whether the data frames carry VLAN tags.
Based on the features of tag aware, access, and hybrid, adhere to the following principles when
setting the tag for a port:
l If the data packets transmitted from the interconnected equipment carry VLAN tags, set
TAG to Tag Aware.
l If the data packets transmitted from the interconnected equipment do not carry VLAN tags,
set TAG to Access.
l If the data packets transmitted from the interconnected equipment may carry VLAN tags,
set TAG to Hybrid.

System
4.2.8 Bridge
A bridge is a functional unit that is used to implement the interconnection between two or more
LANs.
VB and LP
The switching domain of an Ethernet board that has the Layer 2 switching capability can be
divided into multiple sub-switching domains. As a result, if no services are interconnected,
different various bridges (VBs) cannot access each other. Each VB has an independent
configuration mode and uses an independent VLAN. Different VBs can use the same VLAN.
A VB can contain a number of logical ports (LPs). By configuring the mounting relation, you
can mount multiple PORTs and VCTRUNKs to the same VB.
Figure 4-16 shows the relations between VBs, LPs, PORTs, and VCTRUNKs.
Figure 4-16 Relations between VBs, LPs, PORTs, and VCTRUNKs
Ethernet Switching Board
VB1
LP1 LP4 VCTRUNK1

PORT1
LP2 LP5 VCTRUNK2

PORT2
LP3 LP6 VCTRUNK3

PORT3
VB2
LP1 LP4 VCTRUNK4

PORT4
PORT5 LP2 LP5 VCTRUNK5
LP3 LP6 VCTRUNK6

PORT6
Transparent Bridge and Virtual Bridge

l The services of different transparent bridges are isolated , but the services in the same
transparent bridge are not isolated. The entire transparent bridge is a switching domain.

System
l The services of different virtual bridges are isolated and the services with different VLAN
IDs in the same virtual bridge are also isolated. The switching domain of the entire virtual
bridge is divided into multiple sub-switching domains according to the VLAN IDs.
NOTE
As shown in Figure 4-17, the same logical port may belong to one or more sub-switching domains with
different VLAN IDs. On the U2000, the same logical port can belong to multiple filtering tables with
different VLAN IDs.
Figure 4-17 Transparent bridge and virtual bridge
VCTRUNK1 VCTRUNK1
PORT1 PORT1 VLAN1
VCTRUNK2 VCTRUNK2
VLAN1
VCTRUNK3 VLAN2 VCTRUNK3
PORT2 VLAN2 PORT2
VCTRUNK4 VCTRUNK4
VLAN3
... VCTRUNK5 VCTRUNK5
PORT3 VCTRUNK6 PORT3 VLAN3
VCTRUNK6
Pure bridge Virtual bridge
Logical port
Table 4-6 Transparent Bridge and Virtual Bridge

Item Transparent Bridge Virtual Bridge
VLAN filtering table It is not configured. It must be configured.
Ingress filter Does not check the validity of Check the validity of VLAN
VLAN tags. All data frames tags. If the VLAN ID is not
that enter the bridge are valid. the same as the VLAN ID
defined in the VLAN
filtering table, discard the
data frame.
MAC address learning mode SVL IVL
Data frame forwarding mode Query the MAC address table Query the MAC address table
to obtain the forwarding port to obtain the forwarding port
of the data frame according to of the data frame according to
the destination MAC address the destination MAC address
of the data frame. and VLAN ID of the data
frame.
Broadcast range Forward broadcast data Forward the broadcast data

frames on all ports of a frames on the forwarding
bridge. ports defined in the VLAN
filtering table.

System
NOTE
To forward a Layer 2 switching service, a bridge must learn the MAC address. A bridge learns the MAC
address through one of the following methods: shared VLAN learning (SVL) and independent VLAN
learning (IVL).
l When the bridge adopts the SVL learning mode, the entry in the MAC address table is created according
to the source MAC address and source port of the data frame. The entry is valid for all VLANs.
l When the bridge adopts the IVL learning mode, the entry in the MAC address table is created according
to the source MAC address, VLAN ID, and source port of the data frame. The entry is valid for only
the VLAN.
Bridge Type
As listed in Table 4-7, the Ethernet boards support three types of bridges.
Table 4-7 Types of bridges supported by the Ethernet boards
Bridge Type Bridge Switch Mode Bridge Learning Ingress

Mode Filter
IEEE 802.1d MAC bridge SVL/Ingress Filter SVL Disabled

Disable
IEEE 802.1q Virtual Bridge IVL/Ingress Filter IVL Enabled

Enable
IEEE 802.1ad 1 SVL/Ingress Filter SVL Disabled

Provider Bridge Disable
2 IVL/Ingress Filter IVL Enabled
Enable
l IEEE 802.1d MAC bridge: The IEEE 802.1d MAC bridge does not check the contents of
the VLAN tags that are in the data frames, but performs Layer 2 switching according to
the destination MAC addresses of the data frames.
l IEEE 802.1q bridge: The IEEE 802.1q bridge supports data isolation by using one layer of
VLAN tags. This bridge checks the contents of the VLAN tags that are in the data frames
and performs Layer 2 switching according to the destination MAC addresses and VLAN
IDs.
l The IEEE 802.1ad bridge: The IEEE 802.1ad bridge supports data frames with two layers
of VLAN tags. This bridge adopts the outer S-VLAN tags to isolate different VLANs and
supports only the mounted ports whose attributes are C-Aware or S-Aware. This bridge
supports the following switching modes:
1. This bridge does not check the contents of the VLAN tags that are in the data frames,
but performs Layer 2 switching according to the destination MAC addresses of the
data frames.
2. This bridge checks the contents of the VLAN tags that are in the data frames and
performs Layer 2 switching according to the destination MAC addresses and the S-
VLAN IDs of the data frames.

System
MAC Address Table

The entries in the MAC address table reflect the corresponding relations between MAC addresses
and ports. The MAC address table contains the following entries:
l Dynamic entry
Indicates the entry that the bridge obtains by adopting the SVL/IVL learning mode. The
dynamic entry ages and is even lost after the Ethernet switching board is reset.
l Static entry
Indicates the entry corresponding to the MAC address and the port that the network
administrator manually adds in the MAC address table on the U2000. A static entry is a
unicast entry. The static entry does not age and is not lost after the Ethernet switching board
is reset.
l Blackhole entry
Indicates the entry used to discard the data frame that contains the specified destination
MAC address, and is also referred to as the MAC address disable entry. The blackhole entry
is configured by the network administrator. This entry does not age and is not lost after the
Ethernet switching board is reset.
NOTE
l If a routing entry is not updated within a specific period of time, that is, if the MAC address fails to be learnt
because the new data frame from the MAC address is not received, this routing entry is deleted automatically.
This mechanism is considered as aging, and this period of time is considered as the aging time. The aging
time of the MAC address table is five minutes by default and can be set by using the U2000.
l A limited number of MAC addresses can be learnt at a time.
Hub/Spoke
Generally, the central station and non-central stations can access each other, but the non-central
stations cannot access each other in the case of convergence services. Therefore, the ports
mounted to the bridge need to be defined as Hub or Spoke ports.
l Hub port
Hub ports can access each other. Hub ports and Spoke ports can also access each other.
l Spoke port
Spoke ports cannot access each other. Hub ports and Spoke ports can access each other.
The mounted ports are Hub ports by default.
4.3 Flow of Configuring Ethernet Services

This topic describes the configuration processes related to Ethernet services. Before you
configure Ethernet services according to the flow, you need to complete the basic configurations
of the NEs according to the flow of creating a network.
4.3.1 Flow of Configuring EPL Services
The EPL services feature simplicity, transparent transmission, and dedicated bandwidth. The
configuration flow differs depending on whether Ethernet transparent transmission boards or
Ethernet switching boards are configured.
4.3.2 Flow of Configuring EVPL Services
In the case of EVPL services, services of different users share the bandwidth. Hence, the VLAN
ID or other schemes need to be used for differentiating the services of different users. If the

System
services of different users need to be configured with different quality levels, you need to adopt
the corresponding QoS scheme.
4.3.3 Flow of Configuring EPLAN Services
EPLAN services provide the customers with Layer 2 switching-based multipoint-connected
LAN services.
4.3.4 Flow of Configuring EVPLAN Services
EVPLAN services of different users need to share the bandwidth. Hence, the VLAN ID or other
schemes need to be used for differentiating the services of different users. If the services of
different users need to be configured with different quality levels, you need to adopt the
corresponding QoS scheme.
4.3.1 Flow of Configuring EPL Services

The EPL services feature simplicity, transparent transmission, and dedicated bandwidth. The
configuration flow differs depending on whether Ethernet transparent transmission boards or
Ethernet switching boards are configured.
Ethernet transparent transmission boards or Ethernet switching boards can be used to configure
EPL services. The Ethernet transparent transmission boards and Ethernet switching boards are
provided in Table 6-1.

System
Figure 4-18 Flow of configuring EPL services
Required Start
Optional
Ethernet transparent Ethernet switching
transmission board board
1 1
Configure Ethernet Configure Ethernet
external ports external ports
2 2
Configure Ethernet Configure Ethernet
internal ports internal ports
3
Create EPL services
4
Create cross-
connections
5
Check service
continuity
6 Enable NE
performance
monitoring
7
Back up NE
configuration data
End
Table 4-8 Flow of configuring EPL services
Step Operation Remarks
1 Configuring External Ports on Ethernet Required

Boards When an NE accesses Ethernet services through the external
ports on the Ethernet board, you need to configure the
attributes of the external ports so that the external ports can
work with the data communication equipment on the client
side, thus ensuring the normal accessing of the Ethernet
services.

System
2 Configuring Internal Ports on Ethernet Required

Boards When an NE transmits Ethernet services through the internal
ports (that is, VCTRUNK ports) on the Ethernet board to the
SDH side, you need to configure the attributes of the
VCTRUNK ports so that the VCTRUNK ports can work
with the Ethernet board on the opposite equipment. This
ensures that the transmission of the Ethernet services in the
SDH network is normal.
3 Creating EPL Services l If Ethernet transparent transmission boards are used,

skip to Step 4. On Ethernet transparent transmission
boards, the EPL service connections from the PORTs to
the VCTRUNKs are considered to be created by default.
l If Ethernet switching boards are used, the EPL service
connections between the PORTs and the VCTRUNKs
must be created.
4 Creating SDH Services Required

This topic describes how to create the timeslot connections
between the bound paths and the line board, thus ensuring
that the Ethernet services are transmitted in specified
timeslots over the transmission line.
5 Testing Ethernet Service Channels Required

After the Ethernet services are created, test the service
continuity.
6 Setting Performance Monitoring Required

Parameters of an NE Enable the performance monitoring function for a specific
NE. Then, you can obtain detailed performance records
during the operation process of this NE. These records can
be used for monitoring and analyzing the running status of
this NE.
7 Backing Up the NE Database to the SCB Required

Board Back up the NE database to ensure that the NE can be
automatically recovered to normal operation after the SCC
data is lost or after the equipment is powered off.
4.3.2 Flow of Configuring EVPL Services

In the case of EVPL services, services of different users share the bandwidth. Hence, the VLAN
ID or other schemes need to be used for differentiating the services of different users. If the
services of different users need to be configured with different quality levels, you need to adopt
the corresponding QoS scheme.
The Ethernet switching boards are required for configuring EVPL services. The Ethernet
switching boards that support EVPL services are provided in Table 6-1.

System
Figure 4-19 Flow of configuring EVPL services
Required Start
Optional 1
Configure Ethernet
external ports
2
Configure Ethernet
internal ports
3
Create EPL services
4
Create cross-
connections
5
Configure the QoS
6
Check service
continuity
7 Enable NE
performance
monitoring
8
Back up NE
configuration data
End
Table 4-9 Flow of configuring EVPL services

1 Configuring External Ports on Required

Ethernet Boards When an NE accesses Ethernet services through the external
services.

System

VCTRUNK ports so that the VCTRUNK ports can work with
the Ethernet board on the opposite equipment. This ensures
that the transmission of the Ethernet services in the SDH
network is normal.
3 Creating EPL Services Required

When an Ethernet switching board carries private line
services, the relevant information of the private line services,
such as the service source and service sink, must be specified.

between the bound paths and the line board, thus ensuring that
the Ethernet services are transmitted in specified timeslots
over the transmission line.
5 Configuring QoS Optional

The services of different users need to share the bandwidth. If
the services of different users need to be configured with
different quality levels, you need to adopt the corresponding
QoS scheme.

continuity.

Parameters of an NE Enable the performance monitoring function for a specific NE.
Then, you can obtain detailed performance records during the
operation process of this NE. These records can be used for
monitoring and analyzing the running status of this NE.
8 Backing Up the NE Database to the Required

SCB Board Back up the NE database to ensure that the NE can be
4.3.3 Flow of Configuring EPLAN Services

EPLAN services provide the customers with Layer 2 switching-based multipoint-connected
LAN services.
The Ethernet switching boards are required for configuring EPLAN services. The Ethernet
switching boards that support EPLAN services are provided in Table 6-1.

System
Figure 4-20 Flow of configuring EPLAN services
Required Start
Optional 1
Configure Ethernet
external ports
2
Configure Ethernet
internal ports
3
Create Ethernet LAN
services
4 Modify Hub/Spoke
attribute of mounted
ports
5
Create cross-
connections
6
Configure the Layer
2 switching feature
7
Check service
continuity
8 Enable NE
performance
monitoring
9
Back up NE
configuration data
End
Table 4-10 Flow of configuring EPLAN services

1 Configuring External Ports on Ethernet Required

Boards When an NE accesses Ethernet services through the external
services.

System

VCTRUNK ports so that the VCTRUNK ports can work with
the Ethernet board on the opposite equipment. This ensures
that the transmission of the Ethernet services in the SDH
network is normal.
3 Creating Ethernet LAN Services Required

When an Ethernet switching board carries LAN services, you
need to create the bridge and set the attributes of the bridge
and the port mounted to the bridge.
4 Modify Hub/Spoke attribute of Optional

mounted ports In the case of Ethernet LAN services, you can modify the Hub/
Spoke attribute between access nodes from the default value
of Hub to Spoke, thus disabling the communication between
the access nodes; however, the communication between the
access nodes and the convergence node is not disabled.

the Ethernet services are transmitted in specified timeslots
over the transmission line.
6 Configuring the Layer 2 switching Optional

feature l You can manually specify the port for forwarding the
l Creating MAC Address Entries MAC frames to create the VLAN unicast entries and you
l Modifying Aging Time of MAC can suppress the forwarding of certain MAC frames to
Addresses create the MAC address disabled entries. The manually
created MAC entries are not affected by the aging time.
l Configuring the Spanning Tree
l The aging time of the dynamic MAC address entries of an
Ethernet switching board is five minutes by default. You
can modify the aging time according to the actual
requirements.
l There may be loops in the network topology of Ethernet
services. Hence, the STP/RSTP protocol is enabled to
prevent packets from being proliferated and endlessly
cycled in the loop network.

continuity.

System

Parameters of an NE Enable the performance monitoring function for a specific
NE. Then, you can obtain detailed performance records
during the operation process of this NE. These records can be
used for monitoring and analyzing the running status of this
NE.

4.3.4 Flow of Configuring EVPLAN Services

EVPLAN services of different users need to share the bandwidth. Hence, the VLAN ID or other
schemes need to be used for differentiating the services of different users. If the services of
different users need to be configured with different quality levels, you need to adopt the
corresponding QoS scheme.
The Ethernet switching boards are required for configuring EVPLAN services. The Ethernet
switching boards that support EVPLAN services are provided in Table 6-1.

System
Figure 4-21 Flow of configuring EVPLAN services
Required Start
Optional 1
Configure Ethernet
external ports
2
Configure Ethernet
internal ports
3
Create Ethernet
LAN services
4
Create the VLAN
filtering table
5 Modify the Hub/Spoke

attribute of mounted
ports
6
Create cross-
connections
7
Configure the Layer
2 switching feature
8
Configure the QoS
9
Check service
continuity
10 Enable NE
performance
monitoring
11
Back up NE
configuration data
End

System
Table 4-11 Flow of configuring EVPLAN services

1 Configuring External Ports on Required

Ethernet Boards When an NE accesses Ethernet services through the external ports
on the Ethernet board, you need to configure the attributes of the
external ports so that the external ports can work with the data
communication equipment on the client side, thus ensuring the
normal accessing of the Ethernet services.
2 Configuring Internal Ports on Required

Ethernet Boards When an NE transmits Ethernet services through the internal
ports (that is, VCTRUNK ports) on the Ethernet board to the SDH
side, you need to configure the attributes of the VCTRUNK ports
so that the VCTRUNK ports can work with the Ethernet board
on the opposite equipment. This ensures that the transmission of
the Ethernet services in the SDH network is normal.
3 Creating Ethernet LAN Services Required

When an Ethernet switching board carries LAN services, you
need to create the bridge and set the attributes of the bridge and
the port mounted to the bridge.
4 Creating VLANs Filtering Required

In the case of Ethernet LAN services, when the type of the bridge
is IEEE 802.1q or IEEE 802.1ad, the VLAN filtering table needs
to be created for the bridge if VLANs are used to isolate the data
of different users.
5 Modify Hub/Spoke attribute of Optional

mounted ports In the case of Ethernet LAN services, you can modify the Hub/
Spoke attribute between access nodes from the default value of
Hub to Spoke, thus disabling the communication between the
access nodes; however, the communication between the access
nodes and the convergence node is not disabled.

the Ethernet services are transmitted in specified timeslots over
the transmission line.

System
7 Configuring the Layer 2 switching Optional

feature l You can manually specify the port for forwarding the MAC
l Creating MAC Address Entries frames to create the VLAN unicast entries and you can
l Modifying Aging Time of MAC suppress the forwarding of certain MAC frames to create the
Addresses MAC address disabled entries. The manually created MAC
entries are not affected by the aging time.
l Configuring the Spanning Tree
l The aging time of the dynamic MAC address entries of an
Ethernet switching board is five minutes by default. You can
modify the aging time according to the actual requirements.
l There may be loops in the network topology of Ethernet
services. Hence, the STP/RSTP protocol is enabled to prevent
packets from being proliferated and endlessly cycled in the
loop network.
l When a multicast router is located on the network, the IEEE
802.1q or IEEE 802.1ad bridge can enable the IGMP
Snooping protocol to work with the router, thus implementing
the multicast function.
8 Configuring QoS Optional

The services of different users need to share the bandwidth. If the
services of different users need to be configured with different
quality levels, you need to adopt the corresponding QoS scheme.

After the Ethernet services are created, test the service continuity.

Parameters of an NE Enable the performance monitoring function for a specific NE.
Then, you can obtain detailed performance records during the
operation process of this NE. These records can be used for
monitoring and analyzing the running status of this NE.

automatically recovered to normal operation after the SCC data
is lost or after the equipment is powered off.
4.4 Configuring EPL Services on an Ethernet Transparent

Transmission Board

System
The completely isolated data services of two users at a station must be transported to another
station.
Ethernet services are received from an external port, encapsulated through an internal port, and
mapped to the SDH network for transparent transmission. In this way, the node communicates
with a remote node.
4.4.3 Configuration Process
The Ethernet transparent transmission boards support only EPL services. The EPL are already
created by default and hence you need not configure the Ethernet transparent transmission boards
on the U2000.

station.
Service Requirement
In the network as shown in Figure 4-22, the service requirements are as follows:
l The two branches of user A that are located at NE1 and NE3 need to communicate with
each other over Ethernet. A 10 Mbit/s bandwidth is required.
l The two branches of user B that are located at NE1 and NE3 need to communicate with
l The services of user A must be isolated from the services of user B.
l The Ethernet equipment of user A and user B provides 100 Mbit/s Ethernet ports of which
the working mode is auto-negotiation, and does not support VLANs.
Figure 4-22 Networking diagram of the EPL services

User A2 User B2
PORT1 PORT1 NE3:

Ethernet board Ethernet board Line board
NM 3-EGT1 4-EGT1 5-SL4D-1
5-SL4D-2 NE3
5
5-SL4D-1
NE2 NE4
5-SL4D-2
NE2:
5-SL4D-2
5-SL4D-1 NE1
5-SL4D-1
NE1:
Ethernet board Ethernet board Line board
PORT1 PORT1 3-EGT1 4-EGT1 5-SL4D-2
VCTRUNK
User A1 User B1

System
Board Configuration Information

Ethernet transparent transmission boards or Ethernet switching boards can be used for
configuring EPL services. In this example, NE1 and NE3 are configured with two EGT1 boards
respectively, which occupy logical slots 3 and 4.

with a remote node.
Figure 4-23 shows the signal flow and timeslot allocation of the EPL services.
For the method of calculating the bandwidth of the Ethernet services carried by a VCTRUNK,
see 6.3 Ethernet Service Bandwidths Carried by VCTRUNKs of Ethernet Boards.
Figure 4-23 Signal flow and timeslot allocation (Ethernet transparent transmission board)
NOTE
The EGT1 board supports transparent transmission of Ethernet services, the link capacity adjustment
scheme (LCAS), test frames, and other functions.
NE1 NE2 NE3

3-EGT1 3-EGT1
PORT1 PORT1
VCTRUNK1 VCTRUNK1
User A1 User A2
VC4-4:VC12:1-5 VC4-1:VC12:1-5 VC4-4:VC12:1-5
PORT1 4-EGT1 4-EGT1
VCTRUNK1 VCTRUNK1 PORT1
User B1 User B2
VC4-4:VC12:1-10 VC4-4:VC12:1-10
VC4-1:VC12:6-15
SDH
l The EPL services of user A:

– Occupy the first to fifth VC-12 timeslots of the first VC-4 (VC4-1:VC12:1-5) on the
SDH link between NE1 and NE3 and pass through NE2.
– Are added and dropped by using the first to fifth VC-12 timeslots of the fourth VC-4
(VC4-4:VC12:1-5) on the 3-EGT1 board of NE1 and the first to fifth VC-12 timeslots
of the fourth VC-4 (VC4-4:VC12:1-5) on the 3-EGT1 board of NE3.
l The EPL services of user B:
– Occupy the sixth to fifteenth VC-12 timeslots of the first VC-4 (VC4-1:VC12:6-15) on
the SDH link between NE1 and NE3 and pass through NE2.
– Are added and dropped by using the first to tenth VC-12 timeslots of the fourth VC-4
(VC4-4:VC12:1-10) on the 4-EGT1 board of NE1 and the first to tenth VC-12 timeslots
Table 4-12 Parameters of external ports on the Ethernet boards
Parameter NE1 NE3
Board 3-EGT1 4-EGT1 3-EGT1 4-EGT1

System
Parameter NE1 NE3
Port PORT1 PORT1 PORT1 PORT1
Enabled/ Enabled Enabled Enabled Enabled

Disabled
Working Mode Auto- Auto- Auto- Auto-

Negotiation Negotiation Negotiation Negotiation
Maximum 1522 1522 1522 1522

Frame Length
Table 4-13 Parameters of internal ports on the Ethernet boards
Parameter NE1 NE3
Board 3-EGT1 4-EGT1 3-EGT1 4-EGT1
Internal Port VCTRUNK1 VCTRUNK1 VCTRUNK1 VCTRUNK1
Mapping GFP GFP GFP GFP

Protocol
Bound Path VC4-4:VC12-1 VC4-4:VC12-1 VC4-4:VC12-1 VC4-4:VC12-1

-VC12-5 -VC12-10 -VC12-5 -VC12-10

The Ethernet transparent transmission boards support only EPL services. The EPL are already
created by default and hence you need not configure the Ethernet transparent transmission boards
on the U2000.
Prerequisite
You must be familiar with 4.3.1 Flow of Configuring EPL Services.
By default, EPL service connections from external ports to internal ports are already created for
Ethernet transparent transmission boards. The EPL service connections can be queried on the
U2000, but cannot be created, modified, or deleted on the U2000.
If the Ethernet transparent transmission boards in the actual application scenarios are different
from the boards in this example, you need to learn about the requirements for configuring specific
boards.
l For the EPL services supported by Ethernet transparent transmission boards, see 6.1
Service Support Capability of Ethernet Boards.
l For the VCTRUNK binding requirements of Ethernet transparent transmission boards, see
6.2 Requirements for Binding Paths with VCTRUNKs on Ethernet Boards.

System
Procedure
Step 1 Configure the EPL services of user A1 and user B1 on NE1.
1. Set the attributes of the external ports (PORT1 of 3-EGT1 board and PORT1 of the 4-EGT1
board) used by the services of user A1 and user B1.
l In the NE Explorer, select the EGT1 and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
l Select External Port.
l Click the Basic Attributes tab. After setting the parameters, click Apply.
Parame Value in This Example Description

ter
Enabled PORT1: Enabled PORT1 is used by the service of user A1.

/ PORT2 is used by the service of user B1. In
Disable this example, Enabled/Disabled is set to
d Enabled for PORT1 and PORT2.
Workin PORT1: Auto- In this example, the Ethernet service access

g Mode Negotiation equipment of user A1 and user B1 supports
the auto-negotiation mode. Hence, Working
Mode is set to Auto-Negotiation for PORT1
and PORT2.
Maximu PORT1: 1522 Generally, this parameter adopts the default

m value 1522.
Frame
Length
MAC PORT1: Non-Loopback The MAC loopback setting is used for fault
Loopba diagnosis. In this example, MAC
ck Loopback is set to Non-Loopback.
PHY PORT1: Non-Loopback The PHY loopback setting is used for fault
Loopba diagnosis. In this example, PHY Loopback
ck is set to Non-Loopback.
2. Set the attributes of the internal ports (VCTRUNK1 of 3-EGT1 board and VCTRUNK1 of
the 4-EGT1 board) used by the services of user A1 and user B1.
l Select Internal Port.
l Click the Encapsulation/Mapping tab. After setting the parameters, click Apply.

ter
Mappin VCTRUNK1: GFP In this example, the EFS8 board is used. This
g parameter adopts the default value GFP.
Protocol Mapping Protocol of the VCTRUNKs on
the Ethernet boards of the interconnected
equipment at both ends must be set to the
same value.

System

ter
Scrambl VCTRUNK1: In this example, this parameter adopts the

e Scrambling mode [X43 default value Scrambling mode [X43+1].
+1] Scramble of the VCTRUNKs on the
Ethernet boards of the interconnected
same value.
Check VCTRUNK1: FCS32 In this example, this parameter adopts the

Field default value FCS32. Check Field Length
Length of the VCTRUNKs on the Ethernet boards of
the interconnected equipment at both ends
must be set to the same value.
FCS VCTRUNK1: Big endian When Mapping Protocol is set to GFP, FCS
Calculat Calculated Bit Sequence is set to Big
ed Bit endian. FCS Calculated Bit Sequence of
Sequenc the VCTRUNKs on the Ethernet boards of
e the interconnected equipment at both ends
Set VCTRUNK1: - When Mapping Protocol is set to GFP, this

Inverse parameter is valid and adopts the default
Value value -. Set Inverse Value for CRC of the
for CRC VCTRUNKs on the Ethernet boards of the
interconnected equipment at both ends must
be set to the same value.
l Click the Bound Path tab. Click the Configuration button. Set the following
parameters in the Bound Path Configuration dialog box that is displayed. Then, click
Apply.
User Parameter Value in Description
This
Example
User Configurab VCTRUN As shown in Figure 4-23, VCTRUNK1 of the

A1← le Ports K1 (3- 3-EGT1 board is used by the service between
→user EGT1) user A1 and user A2.
A2
Avai Lev VC12-xv The service between user A1 and user A2 uses
lable el a 10 Mbit/s bandwidth. Hence, five VC-12s
Bou need to be bound.
nd For the method of computing the bound
Path timeslots based on the service bandwidth, see
s 6.3 Ethernet Service Bandwidths Carried
by VCTRUNKs of Ethernet Boards.

System

This
Example
Ser Bidirection The service between user A1 and user A2 is a

vice al bidirectional service.
Dir
ecti
on
Av VC4-4 For the resources used by the specific boards,

aila see 6.2 Requirements for Binding Paths
ble with VCTRUNKs on Ethernet Boards.
Res
our
ces
Av VC12-1 to Five VC-12s need to be bound for the service

aila VC12-5 from user A1 to user A2. In this example, the
ble first to the fifth VC-12 need to be selected in
Ti sequence.
mes
lots
User Configurab VCTRUN As shown in Figure 4-23, VCTRUNK1 of the

B1← le Ports K1 (4- 4-EGT1 board is used by the service between
→user EGT1) user B1 and user B2.
B2
Avai Lev VC12-xv The service between user B1 and user B2 uses
lable el a 20 Mbit/s bandwidth. Hence, 10 VC-12s
Bou need to be bound.
Ser Bidirection The service between user B1 and user B2 is a

vice al bidirectional service.
Dir
ecti
on
Av VC4-4 For the resources used by the specific boards,

aila see 6.2 Requirements for Binding Paths
ble with VCTRUNKs on Ethernet Boards.
Res
our
ces

System

This
Example
Av VC12-1 to Ten VC-12s need to be bound for the service

aila VC12-10 from user B1 to user B2. In this example, the
ble first to the tenth VC-12 need to be selected in
Ti sequence.
mes
lots
3. Configure the cross-connections from the Ethernet services to the SDH links for user A1
and user B1.
Set the parameters as follows.
User Paramete Value in Description

r This
Example
User A1 Level VC12 The timeslot bound with the service of user
A1 is at the VC-12 level. The service level
must be consistent with the level of the path
bound with the VCTRUNK.
Service Bidirectiona The service of user A1 is a bidirectional

Direction l service.
Source Slot 3-EGT1-1 When you create a bidirectional SDH

(SDH-1) service from an Ethernet board to a line
board, it is recommended that you set the
slot of the Ethernet board as the source slot.
Source VC4-4 The value range of Source VC4 is

VC4 consistent with the value range of
Available Resources, which is set for the
paths bound with VCTRUNK1. In the case
of VCTRUNK1, the value of Available
Resources is VC4-4.
Source 1-5 The value range of the source timeslot is

Timeslot consistent with the value range of
Range(e.g. Available Timeslots, which is set for the
1,3-6) paths bound with VCTRUNK1. In this
example, the value range of Available
Timeslots is from VC12-1 to VC12-5.
Sink Slot 5-SL4D-1 When you create a bidirectional SDH

slot of the line board as the sink slot.

System

r This
Example
Sink VC4 VC4-1 In this example, VC4-1 is specified as the

VC-4 timeslot of the Ethernet service on the
line board.
Sink 1-5 The value range of the sink timeslot can be

Timeslot the same as or different from the value
Range(e.g. range of the source timeslot. The number of
1,3-6) source timeslots must be, however, the
same as the number of sink timeslots. For
example, if the source timeslots are five
VC-12s, the sink timeslots must be five
VC-12s.
Activate Yes -
Immediatel
y
User B1 Level VC12 The timeslot bound with the service of user
B1 is at the VC-12 level. The service level
Service Bidirectiona The service of user B1 is a bidirectional

Source Slot 4-EGT1-1 When you create a bidirectional SDH


Resources is VC4-4.
Source 1-10 The value range of the source timeslot is



System

r This
Example

line board.
Sink 6-15 The value range of the sink timeslot can be

Range(e.g. range of the source timeslot. The number of
1,3-6) source timeslots must be, however, the
example, if the source timeslots are 10
VC-12s, the sink timeslots must be 10
VC-12s.
Activate Yes -
Immediatel
y
Step 2 Configure the pass-through services of user A1 and user B1 on NE2.
1. Click . Select NE2 in the Navigation Tree that is displayed. Then, click OK.
2. In the NE Explorer, select NE2 and then choose Configuration > SDH Service
the parameters as follows.
This
Example
Level VC12 The SDH service of NE1, which passes through NE2, is
at the VC-12 level.
Service Bidirectional As shown in Figure 4-23, the SDH service from NE1 to
Direction NE2 is a bidirectional service.
Source Slot 5-SL4D-1 As shown in Figure 4-23, the service signals are
(SDH-1) transmitted from 5-SL4D-1(SDH-1) to 5-SL4D-2
(SDH-2). In this example, Source Slot is set to 5-SL4D-1
(SDH-1).
Source VC4-1 VC4-1 is allocated to the service from NE1 to NE2.

VC4
Source 1-15 The service between user A1 and user B1 uses timeslots
Timeslot 1-15.
Range(e.g.
1,3-6)

System

This
Example
Sink Slot 5-SL4D-2 As shown in Figure 4-23, the service signals are
(SDH-1). In this example, Sink Slot is set to 5-SL4D-2
(SDH-2).
Sink VC4 VC4-1 It is recommended that you set Sink Slot to be the same
as Source Slot.
Sink 1-15 The service between user A1 and user B1 uses timeslots
Timeslot 1-15.
Range(e.g.
1,3-6)
Activate Yes -
Immediatel
y
Step 3 Configure the EPL services of user A2 and user B2 on NE3.

Refer to Step 1 and configure the EPL services for users A2 and B2.
Step 4 Check whether the service between user A1 and user A2 and the service between user B1 and
user B2 are correct. For the operation procedure, see Testing Ethernet Service Channels.
SCB Board.
----End
Relevant Task
If the services are configured incorrectly and thus need to be deleted, see 5.4.3 Deleting Ethernet
Private Line Services.
4.5 Configuring EPL Services on an Ethernet Switching

Board
station.

System
with a remote node.
This topic describes the process of configuring Ethernet private line services for Ethernet
switching boards.
4.5.4 Configuration Process (End-to-End Mode)
During the configuration of EPL services on Ethernet switching boards, you need to configure
Ethernet private line services. This topic describes the process of configuring EPL services for
Ethernet switching boards in end-to-end mode.

station.
Service Requirement
l The two branches of user A that are located at NE1 and NE3 need to communicate with
l The two branches of user B that are located at NE1 and NE3 need to communicate with
l The services of user A must be isolated from the services of user B.
l The Ethernet equipment of user A and user B provides 100 Mbit/s Ethernet ports of which
the working mode is auto-negotiation, and does not support VLANs.
Figure 4-24 Networking diagram of the EPL services

User A2 User B2
PORT1 PORT2
NE3:
NM Ethernet board Line board

4-EFS8 6-SL4D-1
6-SL4D-2 NE3
6-SL4D-1
NE2 NE4
6-SL4D-2
NE2:
Line board Line board 6-SL4D-1 NE1
6-SL4D-1 6-SL4D-2
NE1:
Ethernet board Line board
PORT1 PORT2 4-EFS8 6-SL4D-2
VCTRUNK
User A1 User B1

System

Ethernet transparent transmission boards or Ethernet switching boards can be used to configure
EPL services. The Ethernet switching processing board is displayed as the EFS8 on the
U2000, which occupies logical slot 4.
In this example, NE1 and NE3 each are configured with one EFS8 board, which is an Ethernet
switching board.

with a remote node.
Figure 4-25 shows the signal flow and timeslot allocation of the EPL services.
Figure 4-25 Signal flow and timeslot allocation (Ethernet switching board)
NE1:EFS8 NE2 NE3 :EFS8
PORT1 PORT1
VCTRUNK1 VCTRUNK1
User A1 User A2
VC4-4:VC12:1-5 VC4-1:VC12:1-5 VC4-4:VC12:1-5
PORT2
VCTRUNK2 VCTRUNK2 PORT2
User B1 User B2
VC4-4:VC12:6-15 VC4-4:VC12:6-15
VC4-1:VC12:6-15
SDH
l The EPL services of user A:

SDH link between NE1 and NE3 and pass through NE2.
(VC4-4:VC12:1-5) on the EFS8 board of NE1 and the first to fifth VC-12 timeslots of
the fourth VC-4 (VC4-4:VC12:1-5) on the EFS8 board of NE3.
l The EPL services of user B:
– Occupy the sixth to fifteenth VC-12 timeslots of the first VC-4 (VC4-1:VC12:6-15) on
the SDH link between NE1 and NE3 and pass through NE2.
– Are added and dropped by using the sixth to fifteenth VC-12 timeslots of the fourth
VC-4 (VC4-4:VC12:6-15) on the EFS8 board of NE1 and the sixth to fifteenth VC-12
timeslots of the fourth VC-4 (VC4-4:VC12:6-15) on the EFS8 board of NE3.
Parameter NE1 NE3
Board EFS8 EFS8

System
Parameter NE1 NE3

Disabled

Maximum 1522 1522 1522 1522

Frame Length
Parameter NE1 NE3
Board EFS8 EFS8
Internal Port VCTRUNK1 VCTRUNK2 VCTRUNK1 VCTRUNK2

Protocol

-VC12-5 -VC12-15 -VC12-5 -VC12-15
Entry Detection Disabled Disabled Disabled Disabled
Port Type UNI UNI UNI UNI
Table 4-16 Parameters of the EPL services
Parameter EPL Services of User A EPL Services of User B
Board EFS8
Service Type EPL
Service Direction Bidirectional
Source Port PORT1 PORT2
Source C-VLAN (e.g. 1,3-6) Null Null
Sink Port VCTRUNK1 VCTRUNK2
Sink C-VLAN (e.g. 1,3-6) Null Null

This topic describes the process of configuring Ethernet private line services for Ethernet
switching boards.

System
Prerequisite
If the Ethernet switching boards in the actual application scenarios are different from the boards
in this example, you need to learn about the requirements for configuring specific boards.
l For the EPL services supported by Ethernet switching boards, see 6.1 Service Support
Capability of Ethernet Boards.
l For the VCTRUNK binding requirements of Ethernet switching boards, see 6.2
Requirements for Binding Paths with VCTRUNKs on Ethernet Boards.
Procedure
Step 1 Configure the EPL services for users A1 and B1 on NE1.
1. Set the attributes of the external ports (PORT1 and PORT2 on the EFS8 board) used by the
services of users A1 and B1.
l In the NE Explorer, select the EFS8 and then choose Configuration > Ethernet

ter
Enabled PORT1: Enabled PORT1 is used by the service of user A1.

/ PORT2: Enabled PORT2 is used by the service of user B1. In
d Enabled for PORT1 and PORT2.

g Mode Negotiation equipment of user A1 and user B1 supports
PORT2: Auto- the auto-negotiation mode. Hence, Working
Negotiation Mode is set to Auto-Negotiation for PORT1
and PORT2.

m PORT2: 1522 value 1522.
Frame
Length
Loopba PORT2: Non-Loopback diagnosis. In this example, MAC
Loopba PORT2: Non-Loopback diagnosis. In this example, PHY Loopback

System
l Click the Flow Control tab. The parameters in the Flow Control tab page adopt the
default values.
l Click the TAG Attributes tab. After setting the parameters, click Apply.
ter
TAG PORT1: Access The access equipment of user A1 and user B1

PORT2: Access does not support the VLAN. Hence, the
access equipment transmits only the packet
without the VLAN tag. In this example, it is
recommended that you set the TAG flags at
PORT1 and PORT2 to Access.
Default PORT1: 1 The services of user A1 and user B1

VLAN PORT2: 1 exclusively occupy the PORTs and
ID VCTRUNKs. Hence, the VLAN ID is not
required for isolating the services. In this
example, Default VLAN ID adopts the
default value.
VLAN PORT1: 0 Both the VLAN ID and VLAN priority are

Priority PORT2: 0 unnecessary for users A1 and B1. In this
example, VLAN Priority adopts the default
value.
Entry PORT1: Disabled The services of user A1 and user B1 are EPL
Detectio PORT2: Disabled transparent transmission services. Hence,
n you need not enable the entry detection
function to check the VLAN tags of the
packets. In this example, Entry Detection
need to be set to Disabled. When Entry
Detection is set to Disabled, the parameters
of TAG, Default VLAN ID, and VLAN
Priority are invalid.
l Click the Advanced Attributes tab. The parameters in the Advanced Attributes tab
page adopt the default values.
2. Set the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 of the EFS8 board)
used by the services of user A1 and user B1.

System

ter
Entry VCTRUNK1: Disabled The services of user A1 and user B1 are EPL
Detectio VCTRUNK2: Disabled transparent transmission services. Hence,
n you need not enable the entry detection
function to check the VLAN tags of the
packets. In this example, Entry Detection
need to be set to Disabled. When Entry
Detection is set to Disabled, the parameters
of TAG, Default VLAN ID, and VLAN
Priority are invalid.
l Click the Network Attributes tab. After setting the parameters, click Apply.

ter
Port VCTRUNK1: UNI UNI indicates the user-network interface,

Attribut VCTRUNK1: UNI namely, the interface of the service provider
es located near the user side. The UNI interface
processes the tag attribute of IEEE 802.1Q-
compliant packets. That is, the UNI interface
processes and identifies the VLAN
information of the accessed user packets,
according to the supported tag flag, namely,
Tag Aware, Access, and Hybrid.

ter
g VCTRUNK2: GFP parameter adopts the default value GFP.
same value.

VCTRUNK2: Ethernet boards of the interconnected
Scrambling mode [X43 equipment at both ends must be set to the
+1] same value.

Field VCTRUNK2: FCS32 default value FCS32. Check Field Length

System

ter
Calculat VCTRUNK2: Big endian Calculated Bit Sequence is set to Big

Inverse VCTRUNK2: - parameter is valid and adopts the default
l Click the Bound Path tab. Click the Configuration button. Set the following in the
Bound Path Configuration dialog box that is displayed. Then, click Apply.
r This
Example
User Configura VCTRUN As shown in Figure 4-25, VCTRUNK1 is used

A1← ble Ports K1 by the service between user A1 and user A2.
→user
A2 Ava Lev VC12-xv The service between user A1 and user A2 uses
ilab el a 10 Mbit/s bandwidth. Hence, five VC-12s
le need to be bound.
Bou For the method of computing the bound
nd timeslots based on the service bandwidth, see
Pat 6.3 Ethernet Service Bandwidths Carried by
hs VCTRUNKs of Ethernet Boards.
Ser Bidirectio The service between user A1 and user A2 is a

vic nal bidirectional service.
e
Dir
ecti
on
Av VC4-4 The fourth VC-4 of the EFS8 board can be

aila bound with VC-12s. In this example, Available
ble Resources is set to VC4-4.
Res For the resources used by other boards, see 6.2
our Requirements for Binding Paths with
ces VCTRUNKs on Ethernet Boards.

System

r This
Example

aila VC12-5 from user A1 to user A2. In this example, the
ble first to the fifth VC-12s need to be selected in
Ti sequence.
me
slot
s
User Configura VCTRUN As shown in Figure 4-25, VCTRUNK2 is used

B1← ble Ports K2 by the service between user B1 and user B2.
→user
B2 Ava Lev VC12-xv The service between user B1 and user B2 uses
ilab el a 20 Mbit/s bandwidth. Hence, 10 VC-12s need
le to be bound.
Ser Bidirectio The service between user B1 and user B2 is a

vic nal bidirectional service.
e
Dir
ecti
on
Av VC4-4 The fourth VC-4 of the EFS8 board can be

aila bound with VC-12s. In this example, Available
ble Resources is set to VC4-4.
Res For the resources used by other boards, see 6.2
our Requirements for Binding Paths with
ces VCTRUNKs on Ethernet Boards.
Av VC12-6 to Ten VC-12s need to be bound for the service

aila VC12-15 from user B1 to user B2. In this example, the
ble sixth to the fifteenth VC-12s need to be selected
Ti in sequence.
me
slot
s
3. Configure the Ethernet private line services for user A1 and user B1.
l In the NE Explorer, select the EFS8 board, and then choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
l Click New on the lower-right pane to display the Create Ethernet Line Service dialog
box. Set the following parameters, and then click OK. The Operation Result dialog
box is displayed, indicating that the operation is successful. Click Close.

System

This
Example
User A1 Service EPL The service of user A1 is an EPL service.

Type
Service Bidirection The service of user A1 is a bidirectional

Direction al service.
Source Port PORT1 When creating the bidirectional Ethernet

service from a PORT to a VCTRUNK, it is
recommended that you use a specific PORT as
the source port. In this example, the service of
user A1 occupies PORT1.
Source C- Blank In this example, the EPL service does not carry
VLAN (e.g. the VLAN tag.
1, 3-6)
Sink Port VCTRUN When creating the bidirectional Ethernet

K1 service from a PORT to a VCTRUNK, it is
recommended that you use a specific
VCTRUNK as the sink port. In this example,
the service of user A1 occupies VCTRUNK1.
Sink C- Blank In this example, the EPL service does not carry
1, 3-6)
User B1 Service EPL The service of user B1 is an EPL service.

Type
Service Bidirection The service of user B1 is a bidirectional

Direction al service.

the source port. In this example, the service of
user B1 occupies PORT2.
Source C- Blank In this example, the EPL service does not carry
1, 3-6)

the service of user B1 occupies VCTRUNK2.
Sink C- Blank In this example, the EPL service does not carry
1, 3-6)

System
4. Configure the cross-connections from the Ethernet services to the SDH links for user A1
and user B1.
r This
Example
User A1 Level VC12 The timeslot bound with the service of user
A1 is at the VC-12 level. The service level
Service Bidirectiona The service of user A1 is a bidirectional

Source Slot 4-EFS8-1 When you create a bidirectional SDH


Resources is VC4-4.
Source 1-5 The value range of the source timeslots is



line board.

System

r This
Example
Sink 1-5 The value range of the sink timeslots can be

Range(e.g. range of the source timeslots. The number
1,3-6) of source timeslots must be, however, the
VC-12s.
Activate Yes -
Immediatel
y
User B1 Level VC12 The timeslot bound with the service of user
B1 is at the VC-12 level. The service level
Service Bidirectiona The service of user B1 is a bidirectional



Resources is VC4-4.



line board.

System

r This
Example

VC-12s.
Activate Yes -
Immediatel
y
1. Click . Select NE2 in the Navigation Tree that is displayed. Then, click OK.
the parameters as follows.
This
Example
Level VC12 The SDH service of NE1, which passes through NE2, is
at the VC-12 level.
Service Bidirectional As shown in Figure 4-25, the SDH service from NE1 to
Direction NE2 is a bidirectional service.
Source Slot 6-SL4D-1 As shown in Figure 4-25, the service signals are
(SDH-2). In this example, Source Slot is set to 6-SL4D-1
(SDH-1).
Source VC4-1 VC4-1 is allocated to the service from NE1 to NE2.

VC4
Source 1-15 The service between user A1 and user B1 uses timeslots
Timeslot 1-15.
Range(e.g.
1,3-6)
Sink Slot 6-SL4D-2 As shown in Figure 4-25, the service signals are
(SDH-2). In this example, Sink Slot is set to 6-SL4D-2
(SDH-2).

System

This
Example
Sink VC4 VC4-1 It is recommended that you set Sink Slot to be the same
as Source Slot.
Sink 1-15 The service between user A1 and user B1 uses timeslots
Timeslot 1-15.
Range(e.g.
1,3-6)
Activate Yes -
Immediatel
y
Refer to Step 1 and configure the EPL services for users A2 and B2. The parameter values of
user A2 and user B2 must be consistent with the parameter values of user A1 and user B1.
Step 4 Check whether the service between user A1 and user A2 and the service between user B1 and
user B2 are correct. For the operation procedure, see Testing Ethernet Service Channels.
SCB Board.
----End
Relevant Task
4.5.4 Configuration Process (End-to-End Mode)

During the configuration of EPL services on Ethernet switching boards, you need to configure
Ethernet private line services. This topic describes the process of configuring EPL services for
Ethernet switching boards in end-to-end mode.
Prerequisite
You must understand the information provided in 4.5.2 Signal Flow and Timeslot
Allocation.
If in the actual application you use an Ethernet switching board different from the one described
in this example, learn about the requirements for configuring that specific as follows:

System
l For the EPL services supported by Ethernet switching boards, see 6.1 Service Support
l For the VCTRUNK binding requirements of the Ethernet switching boards, see 6.2
Procedure
Step 1 Configure the EPL services between user A1 and user A2 in end-to-end mode.
1. Create a VC-4 server trail.
l Choose Service > SDH Trail > Create SDH Trail from the Main Menu and set
parameters for the VC-4 server trail.
Table 4-17 Parameters of the VC-4 server trail between user A1 and user A2
Parameter Value in This Example
Direction Bidirectional
Level VC4 Server Trail
Service Domain SDH&RTN
Resource Usage Strategy Protected Resource
Protection Priority Strategy Trail Protection First
l Double-click NE1 (source) and NE3 (sink) on the main topology to configure the source
and sink of the VC-4 server trail.
l In the Trail Settings tab, configure Explicit Node and Set Route Timeslot.
Table 4-18 Parameters of the VC-4 server trail route between user A1 and user A2
Explicit Node NE NE2

NOTE
Right-click and choose
Add from the shortcut
menu. In the Add Explicit
Node dialog box that is
displayed, select NE2.
Set Route Timeslot Timeslot 1

NOTE
Click Set Route Timeslot.
In the Set Route Timeslot
dialog box that is displayed,
set the VC-4 server trail
from NE1 to NE3 to VC4-1.
Other parameters Default values

System
l Click Apply. The Operation Result dialog box is displayed indicating that the
operation is successful. Click Close or Browse Trail to query the created VC-4 server
trail.
2. Create a trunk link.
l Choose Service > MSTP Trail > Create Trunk Link from the Main Menu.
l Set Bandwidth to 5 X: VC12. Select Auto Create Server Trails.
NOTE
If you do not select Auto Create Server Trails, refer to Step 1.1 to create cross-connections of
Ethernet services between NE1 and NE3 to SDH links. Set Level to VC12. Set Server Layer
Trail to the created link when creating trunk links.
l Configure bound timeslots for the source NE. Click Browse. In the dialog box that is
displayed, select NE1 and set NE Panel to EFS8, VCTRUNK Port to 1, and Lower
Order to VC4:4-VC12:1 to VC4:4-VC12:5. Click OK.
l Configure bound timeslots for the sink NE. Click Browse and select NE3. Set NE
Panel to EFS8, VCTRUNK Port to 1, and Lower Order to VC4:4-VC12:1 to VC4:4-
VC12:5. Click OK.
l Select Activate the trail and click Apply.
3. Create EPL services.
l Choose Service > MSTP Trail > Create EPL from the Main Menu.
l Double-click NE1 (source) and NE3 (sink) on the main topology to configure the source
and sink of the EPL services.
Table 4-19 Parameters of the EPL services between user A1 and user A2
Source Port Usage Strategy Port
Port NE1-4-EFS8-PORT1
Sink Port Usage Strategy Port
Port NE3-4-EFS8-PORT1
l Set trunk link routing policies using the existing trunk link. Select the trunk link created
in step 1 b. Click Next.
NOTE
l To create EPL services in end-to-end mode, complete the following recommended steps: first
create a server trail, then create a trunk link, and finally create EPL services. When creating
EPL services, select Use Existing Trunk Link.
l Alternatively, create the trunk link when creating the EPL services. In this case, select Create
Trunk Link Manually or Create Trunk Link Automatically.
l In the Port Attribute Setting dialog box, set port attributes.

System
Table 4-20 Parameters of port attributes for user A1 and user A2
Parameter Value in This

Example
Source NE PORT1 Entry Detection Disabled
VCTRUNK1 Entry Detection Disabled
Sink NE PORT1 Entry detection Disabled
VCTRUNK1 Entry Detection Disabled
Other parameters Default values
l Select Activate the trail and click Finish.
Step 2 Repeat Step 1.2 to Step 1.3 configure EPL services between user B1 and user B2 according to
service planning.
Step 3 Check whether the services between user A1 and user A2 and the services between user B1 and
user B2 are proper. For details, see Testing Ethernet Service Channels.
SCB Board.
----End
Related Task
If the services are configured incorrectly, see 5.4.3 Deleting Ethernet Private Line Services
for the deletion method.
4.6 Configuring PORT-Shared EVPL (VLAN) Services

The PORT-shared EVPL (VLAN) service is applicable when the services of multiple users
received from the same external port on the Ethernet board at a station are transmitted on different
VCTRUNKs to another station or to another external port of the station.

The services of multiple users received from the same external port on an Ethernet board of a
station are transmitted to different stations on different VCTRUNKs.
Ethernet services wherein different VLAN IDs are used to isolate the data of different users are
received from the same external port of NE1, encapsulated through an internal port, and
transparently transmitted on the SDH network. In this way, the node communicates with a remote
node.
Ethernet switching boards are required for creating EVPL services of different VLAN IDs on
NE1. In this way, the data of different users received from the same external port can be

System
differentiated. Ethernet transparent transmission boards are required for creating EPL
transparent transmission services on NE2 and NE4.

The services of multiple users received from the same external port on an Ethernet board of a
station are transmitted to different stations on different VCTRUNKs.
Service Requirement
l The headquarters C1 of user C is located at NE1. Two branches (C2 and C3) of user C are
located at NE2 and NE4. The services between C1 and C2 are transmitted in the VLAN of
which the VLAN ID is 100. The services between C1 and C3 are transmitted in the VLAN
of which the VLAN ID is 200.
l The services of C2 are isolated from the services of C3. The services of C2 and C3 require
a 20 Mbit/s bandwidth respectively.
l The Ethernet equipment of C1, C2, and C3 provides 100 Mbit/s Ethernet electrical
interfaces that work in auto-negotiation mode. The Ethernet equipment of C1 supports
VLANs, but the Ethernet equipment of C2 and C3 does not support VLANs.
– The VLAN ID used by the Ethernet services between C1 and C2 is 100.
– The VLAN ID used by the Ethernet services between C1 and C3 is 200.
Figure 4-26 Networking diagram for configuring PORT-shared EVPL (VLAN) services
NM
NE2: NE4:
Ethernet board Line board Line board Ethernet board
NE3
4-EGT1 6-SL4D-2 6-SL4D-1 4-EGT1
NE2 NE4
PORT1 PORT1
User C3
User C2 6-SL4D-2 6-SL4D-1
NE1
6-SL4D-1 6-SL4D-2
VLAN 100
PORT1 NE1:
VCTRUNK
VLAN 200
Ethernet board Line board Line board
4-EFS8 6-SL4D-1 6-SL4D-2
User C1

In this example, NE1 is configured with an EFS8 board. VLAN IDs are used to isolate the data
of different users received from the same port. NE2 and NE4 are each configured with an EGT1

System
board. The EPL services are configured to implement service transparent transmission from NE2
and NE4 to NE1.
In this example, NE1 is configured with an EFS8 board. NE2 and NE4 are each configured with
an EGT1 board.

Ethernet services wherein different VLAN IDs are used to isolate the data of different users are
received from the same external port of NE1, encapsulated through an internal port, and
transparently transmitted on the SDH network. In this way, the node communicates with a remote
node.
Figure 4-27 shows the signal flow of the PORT-shared EVPL (VLAN) services and the timeslot
allocation to the PORT-shared EVPL (VLAN) services .

NE2:EGT1
0 VCTRUNK1 EPL PORT1

NE1:EFS8 :1-1 User C2
C1 2 VC4-4:VC12:1-10
-1:V
VC4
VCTRUNK1
EVPL1
PORT1 VC4-4:VC12:1-10
User C1
VCTRUNK2 VC
EVPL2 4-1
VC4-4:VC12:11-20 : VC NE4:EGT1
12
:1-
1 0
VCTRUNK1 EPL PORT1
User C3
VC4-4:VC12:1-10
SDH
l The EVPL service from C1 to C2:

– Occupies the first to tenth VC-12 timeslots of the first VC-4 (VC4-1:VC12:1-10) on
the SDH link from NE1 to NE2.
– Is added and dropped by using the first to tenth VC-12 timeslots of the fourth VC-4
(VC4-4:VC12:1-10) on the EFS8 board of NE1 and the first to tenth VC-12 timeslots
of the fourth VC-4 (VC4-4:VC12:1-10) on the EGT1 board of NE2.
l The EVPL service from C1 to C3:
– Occupies the first to tenth VC-12 timeslots of the first VC-4 (VC4-1:VC12:1-10) on
– Is added and dropped by the using the eleventh to twentieth VC-12 timeslots of the
fourth VC-4 (VC4-4:VC12:11-20) on the EFS8 board of NE1 and the first to tenth
VC-12 timeslots of the fourth VC-4 (VC4-4:VC12:1-10) on the EGT1 board of NE4.

System

Parameter NE1 NE2 NE4
Board EFS8 EGT1 EGT1
Port PORT1 PORT1 PORT1
Enabled/Disabled Enabled Enabled Enabled
Working Mode Auto-Negotiation Auto-Negotiation Auto-Negotiation
Maximum Frame 1522 1522 1522

Length
TAG Tag Aware - -

Port VCTRUNK1 VCTRUNK2 VCTRUNK1 VCTRUNK1

Protocol
TAG Access Access - -
Entry Detection Enabled Enabled - -
Default VLAN 100 200 - -

ID
VLAN Priority 0 0 - -

to VC12-10 1 to VC12-20 to VC12-10 to VC12-10
Port Type UNI UNI - -
Table 4-23 Parameters of the PORT-shared EVPL (VLAN) services

Parameter NE1
EVPL1 EVPL2
(PORT1←→ (PORT1←→VCTRUNK2)
VCTRUNK1)
Board EFS8
Service Type EVPL

System
Parameter NE1
EVPL1 EVPL2
(PORT1←→ (PORT1←→VCTRUNK2)
VCTRUNK1)
Service Direction Bidirectional
Source Port PORT1 PORT1
Source C-VLAN (e.g. 1,3-6) 100 200
Sink Port VCTRUNK1 VCTRUNK2
Sink C-VLAN (e.g. 1,3-6) 100 200

Ethernet switching boards are required for creating EVPL services of different VLAN IDs on
NE1. In this way, the data of different users received from the same external port can be
differentiated. Ethernet transparent transmission boards are required for creating EPL
transparent transmission services on NE2 and NE4.
Prerequisite
You must be familiar with 4.3.2 Flow of Configuring EVPL Services.
If the Ethernet boards in the actual application scenarios are different from the boards in this
example, you need to learn about the requirements for configuring specific boards.
l For the EVPL services supported by Ethernet switching boards, see 6.1 Service Support
Procedure
Step 1 Configure the EVPL services for user C1 on NE1.
1. Set the attributes of the external port (PORT1 of the EFS8 board) used by the service of
user C1.

System

ter
Enabled PORT1: Enabled The service of user C1 occupies PORT1. In

/ this example, Enabled/Disabled is set to
Disable Enable.
d
Workin PORT1: Auto- The Ethernet service access equipment of

g Mode Negotiation user C1 supports the auto-negotiation mode.
In this example, Working Mode is set to
Auto-Negotiation.

m value 1522.
Frame
Length
default values.
ter
TAG PORT1: Tag Aware When the port is set to Tag Aware, all data
frames transmitted and received at the port
must have VLAN tags. In this example,
TAG is set to Tag Aware.
Default - When TAG is set to Tag Aware, you need

VLAN not set Default VLAN ID.
ID
VLAN - When TAG is set to Tag Aware, you need

Priority not set VLAN Priority.
Entry PORT1: Enabled The equipment of user C1 supports VLANs.

Detectio Hence, the entry detection function must be
n enabled to check the VLAN tag. In this way,
the user data frames with different VLAN
tags can be distinguished at one port. In this
example, Entry Detection of PORT1 is set
to Enabled.

System
used by the services between user C1 and user C2 and between user C1 and user C3.
ter
TAG VCTRUNK1: Access This parameter is set to Access if the Ethernet

VCTRUNK2: Access equipment of users C2 and C3 does not
support VLANs and if the transmitted
packets do not carry VLAN tags.
Default VCTRUNK1: 100 According to the plan, the VLAN ID is set to

VLAN VCTRUNK2: 200 100 on the transmission network side for
ID Ethernet services between user C1 and user
C2.
The VLAN ID is set to 200 on the
transmission network side for Ethernet
services between user C1 and user C3.
VLAN VCTRUNK1: 0 In this example, this parameter adopts the

Priority VCTRUNK2: 0 default value.
Entry VCTRUNK1: Enabled VCTRUNK1 is used by the service between

Detectio VCTRUNK2: Enabled user C1 and user C2. VCTRUNK2 is used by
n the service between user C1 and user C3.
Then, you need to enable the entry detection
function to detect the VLAN tags of the
received packets.
ter


System

ter
Mappin VCTRUNK1: GFP Mapping Protocol of the VCTRUNKs on

g VCTRUNK2: GFP the Ethernet boards of the interconnected
Protocol equipment at both ends must be set to the
same value.

+1]
VCTRUNK2:
Scrambling mode [X43
+1]

Set VCTRUNK1: No When Mapping Protocol is set to GFP, this

Inverse VCTRUNK2: No parameter is valid and adopts the default
Apply.
r This
Example
User C1 Configurab VCTRUN As shown in Figure 4-27, VCTRUNK1 is

←→ le Ports K1 used by the service between user C1 and user
user C2 C2.

System

r This
Example
Avai Lev VC12-xv The service between user C1 and user C2

lable el uses a 20 Mbit/s bandwidth. Hence, 10
Bou VC-12s need to be bound.
Ser Bidirectio The service between user C1 and user C2 is

vic nal a bidirectional service.
e
Dir
ecti
on
Av VC4-4 Select VC4-4.

aila
ble For the resources used by other boards, see
Res 6.2 Requirements for Binding Paths with
our VCTRUNKs on Ethernet Boards.
ces
Av VC12-1 to Ten VC-12s need to be bound. In this

aila VC12-10 example, the first to the tenth VC-12s need
ble to be selected in sequence.
Ti
me
slot
s
User C1 Configurab VCTRUN As shown in Figure 4-27, VCTRUNK2 is

←→ le Ports K2 used by the service between user C1 and user
user C3 C3.
Avai Lev VC12-xv The service between user C1 and user C3

lable el uses a 20 Mbit/s bandwidth. Hence, 10
Bou VC-12s need to be bound.
Ser Bidirectio The service between user C1 and user C3 is

vic nal a bidirectional service.
e
Dir
ecti
on

System

r This
Example
Av VC4-4 Select VC4-4.

aila
ble For the resources used by other boards, see
Res 6.2 Requirements for Binding Paths with
our VCTRUNKs on Ethernet Boards.
ces
Av VC12-11 Ten VC-12s need to be bound. In this

aila to example, the eleventh to the twentieth
ble VC12-20 VC-12s need to be selected in sequence.
Ti
me
slot
s
3. Configure the Ethernet private line services between user C1 and user C2 and between user
C1 and user C3.
l In the NE Explorer, select the EFS8 board and then choose Configuration > Ethernet
l Click New on the lower-right pane to display the Create Ethernet Line Service
window. Set the following parameters and then click OK. The Operation Result dialog
This
Example
User C1 Service EPL The service between user C1 and C2 is a point-

←→user Type to-point Ethernet private line service.
C2
Service Bidirection The service between user C1 and user C2 is a
Direction al bidirectional service.

the source port. PORT1 is the external port
used by the service between user C1 and user
C2.
Source C- 100 According to the plan, the VLAN ID is set to

VLAN (e.g. 100 for the Ethernet service between user C1
1, 3-6) and user C2.

System

This
Example

VCTRUNK as the sink port. VCTRUNK1 is
the internal port used by the service between
user C1 and user C2.
Sink C- 100 According to the plan, the VLAN ID is set to

User C1 Service EPL The service between user C1 and C3 is a point-

C3
Service Bidirection The service between user C1 and user C3 is a

the source port. PORT1 is the external port used
by the service between user C1 and user C3.


VCTRUNK as the sink port. VCTRUNK2 is
the internal port used by the service between
user C1 and user C2.

4. Configure the cross-connections from the Ethernet service between user C1 and user C2
to the SDH link and the Ethernet service between user C1 and user C3 to the SDH link.

System

r This
Example
User C1 Level VC12 The timeslots bound with the service

←→ between user C1 and user C2 is at the VC-12
user C2 level. The service level must be consistent
with the level of the paths bound with the
VCTRUNK.
Service Bidirectiona The service between user C1 and user C2 is

Direction l a bidirectional service.


paths bound with VCTRUNK1. In this
example, Source VC4 is set to VC4-4.



line board.

example, if the source timeslots are ten
VC-12s, the sink timeslots must be ten
VC-12s.
Activate Yes -
Immediatel
y

System

r This
Example
User C1 Level VC12 The timeslots bound with the service

←→ between user C1 and user C3 is at the VC-12
user C3 level. The service level must be consistent
VCTRUNK.
Service Bidirectiona The service between user C1 and user C3 is

Direction l a bidirectional service.





line board.

example, if the source timeslots are ten
VC-12s, the sink timeslots must be ten
VC-12s.
Activate Yes -
Immediatel
y
Step 2 Configure the EPL services on NE2 and NE4.

System
NOTE
The Ethernet services of NE2 and NE4 are point-to-point transparent transmission services. See 4.4
Configuring EPL Services on an Ethernet Transparent Transmission Board to set the parameters.
Step 3 Check whether the services are configured correctly. For the operation procedures, see Testing
Ethernet Service Channels.
l Before testing the service connectivity between headquarters C1 and branch C2, set TAG of
PORT1 on the EFS8 board to Access and Default VLAN ID to 100.
l Before testing the service connectivity between headquarters C1 and branch C3, set TAG of
PORT1 on the EFS8 board to Access and Default VLAN ID to 200.
NOTE
After the test, change the modified parameter values to the values specified in the service configuration.
SCB Board.
----End
Relevant Task
4.7 Configuring VCTRUNK-Shared EVPL (VLAN) Services

When the data of multiple users without VLAN tags sent to a transmission network is transmitted
on the same VCTRUNK, the VCTRUNK-shared EVPL (VLAN) service is used to isolate the
data by adding VLAN tags. In this way, the bandwidth is shared on the SDH side.

The data of multiple Ethernet users received from the same station is transmitted on the same
VCTRUNK and isolated by using different VLAN IDs. In this way, the bandwidth is shared on
the SDH side.
The services of multiple users that are received from different external ports on an Ethernet
board are tagged with different VLAN IDs and then transmitted on the same VCTRUNK. In
this way, the data of different users is isolated. After the data arrives at the sink node, the VLAN
tags are stripped.
Ethernet switching boards are required on both the source and sink nodes for creating EVPL
services of different VLAN IDs. In this way, the packets received from different external ports
are added with different VLAN tags. As a result, the packets are isolated when they are
transmitted on the same VCTRUNK.

System

The data of multiple Ethernet users received from the same station is transmitted on the same
VCTRUNK and isolated by using different VLAN IDs. In this way, the bandwidth is shared on
the SDH side.
Service Requirement
l Two branches of user D are located at NE1 and NE2, and need to communicate with each
other.
l Two branches of user E are located at NE1 and NE2, and need to communicate with each
other.
l The services of user D need to be isolated from the services of user E. The traffic of user
D and user E, however, are complementary in terms of time and can share a 20 Mbit/s
bandwidth.
l The Ethernet equipment of user D and user E provides 100 Mbit/s Ethernet ports of which
the working mode is auto-negotiation, and does not support VLAN tags.
Figure 4-28 Networking diagram for configuring VCTRUNK-shared EVPL (VLAN) services
NM
NE2:
Ethernet Board Line Board NE3
4-EFS8 6-SL4D
PORT1
NE2 NE4
User D2 PORT2 6
NE1
6
PORT1 PORT2 User E1
User E2
NE1:
Ethernet Board Line Board
VCTRUNK 4-EFS8 6-SL4D
User D1

The Ethernet switching boards that support EVPL services are provided in Table 6-1.
In this example, NE1 and NE2 each are configured with an EFS8 board. Different VLAN IDs
are used to isolate the data of different users transmitted on the same VCTRUNK.
l When the data of user D arrives at the transmission network, the VLAN ID of 100 is added
to the data. When the data leaves the transmission network, the VLAN tag is stripped.
l When the data of user E arrives at the transmission network, the VLAN ID of 200 is added
to the data. When the data leaves the transmission network, the VLAN tag is stripped.

System

The services of multiple users that are received from different external ports on an Ethernet
board are tagged with different VLAN IDs and then transmitted on the same VCTRUNK. In
this way, the data of different users is isolated. After the data arrives at the sink node, the VLAN
tags are stripped.
Figure 4-29 shows the signal flow of the VCTRUNK-shared EVPL (VLAN) services and the
timeslot allocation to the VCTRUNK-shared EVPL (VLAN) services.
NE1:EFS8 NE2:EFS8
PORT1 PORT1
User D1 EVPL1 EVPL1 User D2
VCTRUNK1 VCTRUNK1
PORT2 VC4-4:VC12:1-10 VC4-4:VC12:1-10 PORT2
VC4-1:VC12:1-10
User E1 EVPL2 EVPL2 User E2
SDH
l The EVPL services of user D and user E that share VCTRUNK1 occupy the first to tenth
VC-12 timeslots of the first VC-4 (VC4-1:VC12:1-10) on the SDH link from NE1 to NE2.
l The services are added and dropped by using the first to tenth VC-12 timeslots of the fourth
VC-4 (VC4-1:VC12:1-10) on the EFS8 board of NE1 and the first to tenth VC-12 timeslots
of the fourth VC-4 (VC4-1:VC12:1-10) on the EFS8 board of NE2.
Parameter NE1 NE2
Board EFS8 EFS8

Disabled

Maximum 1522 1522 1522 1522

Frame Length
TAG Access Access Access Access
Entry Detection Enabled Enabled Enabled Enabled
Default VLAN 100 200 100 200

ID

System
Parameter NE1 NE2
VLAN Priority 0 0 0 0

Parameter NE1 NE2
Board EFS8 EFS8
Port VCTRUNK1 VCTRUNK1
Mapping Protocol GFP GFP
TAG Tag Aware Tag Aware
Entry Detection Enabled Enabled
Bound Path VC4-4:VC12-1-VC12-10 VC4-4:VC12-1-VC12-10
Port Type UNI UNI
Table 4-26 Parameters of the VCTRUNK-shared EVPL (VLAN) services

Parameter NE1 NE2
EVPL1 EVPL2 EVPL1 EVPL2

PORT1←→ PORT2←→ PORT1←→ PORT2←→
Board EFS8 EFS8
Service Type EVPL EVPL
Service Bidirectional Bidirectional

Direction
Source Port PORT1 PORT2 PORT1 PORT2
Source C- 100 200 100 200

VLAN (e.g.
1,3-6)
Sink Port VCTRUNK1 VCTRUNK1 VCTRUNK1 VCTRUNK1
Sink C-VLAN 100 200 100 200

(e.g. 1,3-6)

Ethernet switching boards are required on both the source and sink nodes for creating EVPL
services of different VLAN IDs. In this way, the packets received from different external ports

System
are added with different VLAN tags. As a result, the packets are isolated when they are
transmitted on the same VCTRUNK.
Prerequisite
You must be familiar with 4.3.2 Flow of Configuring EVPL Services.
l The Ethernet switching boards that support EVPL services are provided in 6.1 Service
Support Capability of Ethernet Boards.
Procedure
Step 1 Configure the EVPL services for users D1 and E1 on NE1.
1. Set the attributes of the external ports (PORT1 and PORT2 of the EFS8 board) used by the
service of user D1 and user E1.

ter
Enabled PORT1: Enabled The service of user D1 occupies PORT1 and

/ PORT2: Enabled the service of user E1 occupies PORT2. In
d Enabled.
Workin PORT1: Auto- The Ethernet access equipment of user D1

g Mode Negotiation and user E1 supports the auto-negotiation
PORT2: Auto- mode. Working Mode of PORT1 and
Negotiation PORT2 is set to Auto-Negotiation.

Frame
Length

System
default values.
ter
TAG PORT1: Access This parameter is set to Access if the Ethernet

PORT2: Access equipment of user D1 and user E1 does not
packets do not carry VLAN tags.
Default PORT1: 100 According to the plan, the VLAN ID is set to

VLAN PORT2: 200 100 on the transmission network side for
ID Ethernet services between user D1 and user
D2.
The VLAN ID is set to 200 on the
transmission network side for Ethernet
services between user E1 and user E2.
VLAN PORT1: 0 In this example, this parameter adopts the

Priority PORT2: 0 default value.
Entry PORT1: Enabled If the equipment of users D1 and E1 does not

Detectio PORT2: Enabled support VLANs, you need to enable the entry
n detection function to detect wether the
received packets contain VLAN tags. In this
case, Entry Detection is set to Enabled.
2. Set the attributes of the internal port (VCTRUNK1 on the EFS8 board) used by the services
between user D1 and user D2 and between E1 and user E2.
ter
TAG VCTRUNK1: Tag Aware When the port is set to Tag Aware, all data
frames transmitted and received at the port
must have VLAN tags. In this example,
TAG is set to Tag Aware.

ID


System

ter
Entry VCTRUNK1: Enabled VCTRUNK1 is used by the service between

Detectio user D1 and user D2 and the service between
n user E1 and user E2. Then, you need to enable
the entry detection function to detect the
VLAN tags of the received packets.

ter

Attribut namely, the interface of the service provider

ter
Mappin VCTRUNK1: GFP Mapping Protocol of the VCTRUNKs on

g the Ethernet boards of the interconnected
Protocol equipment at both ends must be set to the
same value.

Ethernet boards of the interconnected
same value.

Field default value FCS32. Check Field Length
Calculat Calculated Bit Sequence is set to Big

System

ter

Inverse parameter is valid and adopts the default
Apply.
User Parameter Value Description
in This
Examp
le
User D1 Configurab VCTR As shown in Figure 4-29, VCTRUNK1 is

←→user le Ports UNK1 used by the service between user D1 and user
D2 D2 and the service between user E1 and user
User E1 E2.
←→user
Av Leve VC12- The service between user D1 and user D2 and
E2
aila l xv the service between user E1 and user E2 share
ble a 20 Mbit/s bandwidth. Ten VC-12s need to be
Bo bound.
und For the method of computing the bound
Pat timeslots based on the service bandwidth, see
hs 6.3 Ethernet Service Bandwidths Carried
Serv Bidirect The service between user D1 and user D2 and

ice ional the service between user E1 and user E2 are
Dire bidirectional services.
ction
Avai VC4-4 Select VC4-4.

lable
Reso For the resources used by other boards, see 6.2
urce Requirements for Binding Paths with
s VCTRUNKs on Ethernet Boards.
Avai VC12-1 Ten VC-12s need to be bound. In this example,

lable to the first to the tenth VC-12s need to be selected
Tim VC12-1 in sequence.
eslot 0
s
3. Configure the Ethernet private line services between user D1 and user D2 and between user
E1 and user E2.

System
l Click New on the lower-right pane to display the Create Ethernet Line Service
window. Set the following parameters and then click OK. The Operation Result dialog
This
Example
User D1 Service EPL The service between user D1 and user D2 is a

←→user Type point-to-point EVPL service.
D2
Service Bidirection The service between user D1 and user D2 is a

the source port. In this example, PORT1 is the
external port used by the service between user
D1 and user D2.

VLAN (e.g. 100 on the transmission network side for
1, 3-6) Ethernet service between user D1 and user D2.

VCTRUNK1 is the internal port used by the
service between user D1 and user D2.

1, 3-6) Ethernet services between user D1 and user D2.
User E1 Service EPL The service between user E1 and E2 is a point-

E2
Service Bidirection The service between user E1 and user E2 is a

the source port. In this example, PORT2 is the
external port used by the service between user
E1 and user E2.

1, 3-6) Ethernet service between user E1 and user E2.

System

This
Example

VCTRUNK1 is the internal port used by the
service between user E1 and user E2.

1, 3-6) Ethernet service between user E1 and user E2.
4. Configure the cross-connections from the Ethernet services to the SDH links for user D1
and user E1.
r This
Example
User D1 Level VC12 The timeslots bound with the service

←→ between user D1 and user D2 and the
user D2 service between user E1 and user E2 are at
user E1 the VC-12 level. The service level must be
←→ consistent with the level of the paths bound
user E2 with the VCTRUNK.
Service Bidirectiona The service between user D1 and user D2

Direction l and the service between user E1 and user
E2 are bidirectional services.



System

r This
Example



line board.

1,3-6) of sink timeslots must be, however,
consistent with the number of sink
timeslots.
Activate Yes -
Immediatel
y
Step 2 Configure the EVPL service on NE2.
Refer to Step 1 and configure the EVPL service of NE2.
l Test the service connectivity between user D1 and user D2.
l Test the service connectivity between user E1 and user E2.
SCB Board.
----End
Relevant Task

System
4.8 Configuring EPLAN Services (IEEE 802.1d Bridge)

The EPLAN service (IEEE 802.1d bridge) provides a LAN solution for multipoint-to-multipoint
convergence. This service applies where the user-side data communication equipment connected
to the transmission network does not support VLANs or where the VLAN planning is kept secret
from the network operator.
The convergence node needs to exchange Ethernet services with two access nodes at Layer 2.
The two access nodes need not communicate with each other.
The Ethernet services of the convergence node are received from an external port, forwarded to
an internal port through Layer 2 switching, encapsulated, and transparently transmitted on the
SDH network. In this way, the node communicates with a remote node.
At the convergence node NE1, you need to create an EPLAN service (IEEE 802.1d bridge). At
the access nodes NE2 and NE4, you need to configure only transparent transmission EPL
services.

The two access nodes need not communicate with each other.
Service Requirement
l Three branches (F1, F2, and F3) of user F are located at NE1, NE2, and NE4. F1 needs to
communicate with F2 and F3, and requires a 10 Mbit/s bandwidth for communication with
each branch.
l The Ethernet equipment of user F provides 100 Mbit/s Ethernet electrical interfaces that
work in auto-negotiation mode and support VLANs. The VLAN IDs and the number of
VLANs, however, are unknown and may change.
NOTE
The application scenarios where one branch needs to communicate with other branches are as follows:
l Branches F2 and F3 need to communicate with each other.
l Branches F2 and F3 need not communicate with each other.
If branches F2 and F3 need to communicate with each other, skip Step 1.4 in which you change the Hub/
Spoke attributes of ports connected to the bridge.

System
Figure 4-30 Networking diagram for configuring EPLAN services (IEEE 802.1d bridge)
NE3
NM NE4:
NE2:
4-EGT1 6-SL4D-2 6-SL4D-1 4-EGT1
PORT1
NE2 NE4
NE1 PORT1
6-SL4D-2 6-SL4D-1
F2
6-SL4D-1 6-SL4D-2 F3
PORT1 NE1:
VB
VCTRUNK1 VCTRUNK2
4-EFS8 6-SL4D-1 6-SL4D-2
PORT1
F1 VCTRUNK

For the EPLAN (IEEE 802.1d bridge) services supported by Ethernet switching boards, refer to
Table 6-1.
In this example, the convergence node NE1 is configured with an EFS8 board that supports the
IEEE 802.1d bridge to implement EPLAN services wherein user VLANs are not limited.
The access nodes NE2 and NE4 each are configured with an EGT1 board. The EPL services are
configured to be transparently transmitted from NE2 and NE4 to NE1.

The Ethernet services of the convergence node are received from an external port, forwarded to
an internal port through Layer 2 switching, encapsulated, and transparently transmitted on the
SDH network. In this way, the node communicates with a remote node.
Figure 4-31 shows the signal flow of the EPLAN services (IEEE 802.1d bridge) and the timeslot
allocation to the EPLAN services (IEEE 802.1d bridge).
Figure 4-31 Signal flow of and timeslot allocation

NE2:EGT1
VCTRUNK1 PORT1
NE1:EFS8 User F2
VC4-4:VC12:1-5
5
: 1-
12
VC
VCTRUNK1 4 -1 :
PORT1 VC
VC4-4:VC12:1-5
User F1
VCTRUNK2
VC4
VC4-4:VC12:6-10 -1:V NE4:EGT1
C12
:1 -5
VB1
VCTRUNK1 PORT1
User F3
VC4-4:VC12:1-5
SDH

System
l The Ethernet LAN service of user F occupies the first to fifth VC-12 timeslots of the first
VC-4 (VC4-1:VC12:1-5) on the SDH link from NE1 to NE2 and the first to fifth VC-12
timeslots of the first VC-4 (VC4-1:VC12:1-5) on the SDH link from NE1 to NE4.
l The Ethernet LAN service from NE1 to NE2 is added and dropped by using the first to fifth
VC-12 timeslots of the fourth VC-4 (VC4-4:VC12:1-5) on the EFS8 board of NE1 and the
first to fifth VC-12 timeslots of the fourth VC-4 (VC4-4:VC12:1-5) on the EGT1 board of
NE2.
l The Ethernet LAN service from NE1 to NE4 is added and dropped by using the sixth to
tenth VC-12 timeslots of the fourth VC-4 (VC4-4:VC12:6-10) on the EFS8 board of NE1
and the first to fifth VC-12 timeslots of the fourth VC-4 (VC4-4:VC12:1-5) on the EGT1
board of NE4.

Port PORT1 PORT1 PORT1
Enabled/Disabled Enabled Enabled Enabled
Working Mode Auto-Negotiation Auto-Negotiation Auto-Negotiation
Maximum Frame 1522 1522 1522

Length
Entry Detection Enabled - -
TAG Tag Aware - -


Protocol
Entry Detection Enabled Enabled - -
TAG Tag Aware Tag Aware - -

-VC12-5 -VC12-10 -VC12-5 -VC12-5
Port Type UNI UNI - -

System
Table 4-29 Parameters of Ethernet LAN services (IEEE 802.1d bridge)
Parameter Ethernet LAN Service of NE1
Board EFS8
VB Name VB1
Bridge Type IEEE 802.1d
Bridge Switch Mode SVL/Ingress Filter Disable
Bridge Learning Mode SVL
Ingress Filter Disabled
VB Mount Port PORT1, VCTRUNK1, VCTRUNK2
Hub/Spoke PORT1 Hub
VCTRUNK1 Spoke
VCTRUNK2 Spoke

At the convergence node NE1, you need to create an EPLAN service (IEEE 802.1d bridge). At
the access nodes NE2 and NE4, you need to configure only transparent transmission EPL
services.
Prerequisite
You must be familiar with 4.3.3 Flow of Configuring EPLAN Services.
l For the EPLAN services supported by Ethernet switching boards, see 6.1 Service Support
Procedure
Step 1 Configure the EPLAN services for users F1, F2, and F3 on NE1.
1. Set the attributes of the external port (PORT1 of the EFS8 board) used by the service of
user F1.

System
ter
Enabled PORT1: Enabled In this example, PORT1 carries the services

/ and is set to Enabled.
Disable
d
Workin PORT1: Auto- The Ethernet service access equipment of

g Mode Negotiation user F1 supports the auto-negotiation mode.
In this example, Working Mode is set to
Auto-Negotiation.

m value 1522.
Frame
Length
default values.
ter
Entry PORT1: Enabled If the packets of user F1 carry VLAN tags,

Detectio you need to enable the entry detection
n function to detect the VLAN tags of packets.
In this example, Entry Detection is set to
Enabled.
TAG PORT1: Tag Aware The service access equipment of user F1

supports VLANs and the transmitted data
frames carry VLAN tags. In this example,
Tag is set to Tag Aware for PORT1.

ID


System
used by the services of user F2 and user F3 on NE1.
ter
Entry VCTRUNK1: Enabled If the packets of user F2 and user F3 carry

Detectio VCTRUNK2: Enabled VLAN tags, you need to enable the entry
n detection function to detect the VLAN tags
of the packets. In this example, Entry
Detection is set to Enabled.
TAG VCTRUNK1: Tag Aware The service access equipment of user F2 and
VCTRUNK2: Tag Aware user F3 supports VLANs and the transmitted
data frames carry VLAN tags. In this
example, Tag is set to Tag Aware for
VCTRUNK1 and VCTRUNK2.

ID

ter

according to the supported tag flags, namely

System

ter
same value.

+1] same value.


l This operation is optional. Click the LCAS tab. After setting the parameters, click
Apply.
ter
Enablin VCTRUNK1: Enabled In this example, the LCAS function is

g LCAS VCTRUNK2: Enabled enabled.
LCAS VCTRUNK1: Huawei In this example, this parameter adopts the

Mode Mode default value Huawei Mode. When Huawei
VCTRUNK2: Huawei equipment is used at both ends, LCAS
Mode Mode of the equipment at both ends is set to
Huawei Mode.

System

ter
Hold- VCTRUNK1: 2000 In this example, this parameter adopts the

off Time VCTRUNK2: 2000 default value 2000. This parameter can also
(ms) be set according to the requirement of the
user.
WTR VCTRUNK1: 300 In this example, this parameter adopts the

Time(s) VCTRUNK2: 300 default value 300. This parameter can also be
set according to the requirement of the user.
TSD VCTRUNK1: Disabled In this example, the TSD function is disabled.

VCTRUNK2: Disabled The LCAS does not check the B3 bit error or
BIP status of the VCTRUNK members.
Min. VCTRUNK1: 256 Sets the min. members - transmit direction.

Member VCTRUNK2: 256 When the LCAS is enabled and the number
s- of available members is smaller than this
Transmi value, an alarm is reported.
t
Directio
n
Min. VCTRUNK1: 256 Sets the min. members - receive direction.

Receive value, an alarm is reported.
Directio
n
Apply.
r This
Example
User Configura VCTRUN As shown in Figure 4-31, VCTRUNK1 of the

F1← ble Ports K1 EFS8 board is used by the service between user
→user F1 and user F2.
F2
Ava Lev VC12-xv The service between user F1 and user F2 uses

System

r This
Example
Ser Bidirection The service between user F1 and user F2 is a

vic al bidirectional service.
e
Dir
ecti
on
Av VC4-4 For the resources used by other boards, see 6.2

aila Requirements for Binding Paths with
ble VCTRUNKs on Ethernet Boards.
Res
our
ces

aila VC12-5 between user F1 and user F2. In this example,
ble the first to the fifth VC-12s need to be selected
Ti in sequence.
me
slot
s

F1← ble Ports K2 EFS8 board is used by the service between user
→user F1 and user F3.
F3
Ava Lev VC12-xv The service between user F1 and user F3 uses
Ser Bidirection The service between user F1 and user F3 is a

vic al bidirectional service.
e
Dir
ecti
on

Res
our
ces

System

r This
Example

aila VC12-10 between user F1 and user F3. In this example,
ble the sixth to the tenth VC-12s need to be selected
Ti in sequence.
me
slot
s
3. Create a bridge for the EFS8 board on NE1.
Service > Ethernet LAN Service from the Function Tree.
l Click New.
l Set the parameters in the Create Ethernet LAN Service dialog box that is displayed.
This
Example
VB Name VB1 This parameter is a character string used to describe

the bridge. It is recommended that you set this
parameter to a character string that contains the
information about the detailed application of the
bridge.
VB Type 802.1d The IEEE 802.1d MAC bridge learns and forwards
the packets according to the MAC addresses of the
user packets. The information in the VLAN tags of
the user packets, however, is not considered in the
learning and forwarding process. The IEEE 802.1d
MAC bridge is used when the entire information of
the VLANs used by the client cannot be learned or
when the data between the VLANs of the client need
not be isolated.
Bridge SVL/Ingress When the bridge adopts the SVL learning mode, all
Switch Mode Filter the VLANs share the same MAC address table. That
Disable is, the bridge learns and forwards the packets
according to the MAC addresses of the user packets
only. The information in the VLAN tags of the user
packets, however, is not considered in the learning
and forwarding process.
Bridge SVL -
Learning
Mode

System

This
Example
Ingress Filter Disabled The IEEE 802.1d MAC bridge does not detect the
VLAN tags of the received packets.
l Click Configure Mount.

l In the Available Mounted Ports window, select PORT1, VCTRUNK1, and
VCTRUNK2. Then, click .
l Click OK.
l In the Create Ethernet LAN Service dialog box, click OK.
4. Change the Hub/Spoke attribute of the port that is mounted to the bridge.
NOTE
If normal communication is required between user F2 and user F3, go to Step 1.5.
l Select the created bridge and click the Service Mount tab.
l Change the Hub/Spoke attribute of the port that is mounted to the bridge. After setting
the parameters, click Apply.
This
Example
Hub/Spoke PORT1: Hub If user F1 needs to communicate with user F2 and

VCTRUNK user F3, PORT1 that accesses the services of user F1
1: Spoke is set to Hub. A port of the Hub attribute can
communicate with a port of the Spoke or Hub
VCTRUNK attribute.
2: Spoke
If user F2 need not communicate with user F3, set
the two VCTRUNKs that receive the services of
users F2 and F3 to Spoke. Ports of the Spoke
attribute cannot communicate with each other.
5. Configure the cross-connections from Ethernet services (between user F1 to user F2 and
between user F1 to user F3) to the SDH links.

System

r This
Example
User F1 Level VC12 The timeslot bound with the service

←→ between user F1 and user F2 is at the VC-12
user F2 level. The service level must be consistent
VCTRUNK.
Direction Bidirectiona The service between user F1 and user F2 is

l a bidirectional service.


Resources is VC4-4.



line board.

VC-12s.
Activate Yes -
Immediatel
y

System

r This
Example
User F1 Level VC12 The timeslot bound with the service

←→ between user F1 and user F3 is at the VC-12
user F3 level. The service level must be consistent
VCTRUNK.
Direction Bidirectiona The service between user F1 and user F3 is

l a bidirectional service.


Resources is VC4-4.



line board.

VC-12s.
Activate Yes -
Immediatel
y

System

NOTE
The Ethernet services of NE2 and NE4 are point-to-point transparent transmission EPL services. See 4.4
l Before testing the service connectivity between F1 and F2, set TAG to Access and set Default
VLAN ID to 1 for PORT1 and VCTRUNK1, which receive the services of F1 and F2
respectively, on the EFS8 board.
l Before testing the service connectivity between F1 and F3, set TAG to Access and Default
VLAN ID to 1 for PORT1 and VCTRUNK2, which receive the services of F1 and F3
respectively, on the EFS8 board.
NOTE
After the test, change the modified parameter values to the values specified in the service configuration.
SCB Board.
----End
Relevant Task
If the services are configured incorrectly and thus need to be deleted, see 5.4.4 Deleting EPLAN
Services.
4.9 Configuring EVPLAN Services (IEEE 802.1q Bridge)

The EVPLAN service (IEEE 802.1q bridge) provides an LAN solution for multipoint-to-
multipoint convergence. This service applies in cases where user-side data communication
equipment connected to the transmission network does not support VLANs or where the VLAN
planning is open to the network operator.
LAN services of the two users (H and G) need to be isolated.
The Ethernet services of the convergence node are received from an external port and tagged
with the corresponding VLAN IDs. After the services are forwarded to an internal port through
Layer 2 switching, the VLAN IDs are stripped and then the services are transparently transmitted
in the SDH network. In this way, the node communicates with a remote node.
At the convergence node NE1, you need to create An EVPLAN service (IEEE 802.1q bridge)
and a VLAN filtering table need to be created for the convergence node NE1. The access nodes
NE2 and NE4 need to be configured with EPL transparent transmission services only.

System

LAN services of the two users (H and G) need to be isolated.
Service Requirement
In the network shown in Figure 4-32, the service requirements are as follows:
l Three branches (G1, G2, and G3) of user G are located at NE1, NE2, and NE4 respectively.
The branches need to form a LAN and share a 10 Mbit/s bandwidth. G2 and G3 do not
need to communicate with each other.
l Three branches (H1, H2, and H3) of user H are located at NE1, NE2, and NE4 respectively.
The branches need form a LAN and share a 20 Mbit/s bandwidth. H2 and H3 need to
communicate with each other.
l The service of user G needs to be isolated from the service of user H.
l The Ethernet equipment of user G and user H provides 100 Mbit/s Ethernet electrical
interfaces that work in auto-negotiation mode and do not support VLANs.
Figure 4-32 Networking diagram for configuring EVPLAN services (IEEE 802.1q bridge)
NE2:
Line board Ethernet board Ethernet board
6-SL4D-2 4-EGT1 3-EGT1
NE4:
NE3 Line board Ethernet board Ethernet board

NM 6-SL4D-1 4-EGT1 3-EGT1
3-EGT1-PORT1 3-EGT1-PORT1
H2 H3
NE2 NE4
4-EGT1-PORT1 4-EGT1-PORT1
NE1 G3
6-SL4D-2 6-SL4D-1
G2
6-SL4D-1 6-SL4D-2
H1 PORT2 PORT1
G1
VCTRUNK NE1:
4-EFS8 6-SL4D-1 6-SL4D-2
VB1 VLAN 200 VB1 VLAN 100

PORT2 PORT1

For the EVPLAN (IEEE 802.1q bridge) services supported by Ethernet switching boards, refer
to Table 6-1.

System
IEEE 802.1q bridge to implement EVPLAN services in which user data is isolated.
The access nodes NE2 and NE4 each are configured with two Ethernet transparent transmission
boards respectively, which occupy logical slots 3 and 4. The EPL services are configured to
implement transparent transmission from NE2 and NE4 to NE1.

The Ethernet services of the convergence node are received from an external port and tagged
with the corresponding VLAN IDs. After the services are forwarded to an internal port through
Layer 2 switching, the VLAN IDs are stripped and then the services are transparently transmitted
in the SDH network. In this way, the node communicates with a remote node.
Figure 4-33 shows the signal flow of the EVPLAN services (IEEE 802.1q bridge) and the
timeslot allocation to the EVPLAN services (IEEE 802.1q bridge).
Figure 4-33 Signal flow of and timeslot allocation to EVPLAN services (IEEE 802.1q bridge)
NE2
3-EGT1
VCTRUNK1 PORT1
- 5 User G2
NE1:EFS8 1 2:1 VC4-4:VC12:1-5
VC
4 -1 : PORT1
VC VCTRUNK1
VLAN 100 User H2
VCTRUNK1 10 VC4-4:VC12:1-10
1-
PORT1 VC4-4:VC12:1-5 1 2: 4-EGT1
User G1 VC
1:
VCTRUNK2
C 4-
VC4-4:VC12:6-10 V V
C4
VLAN 200 VCTRUNK3 -1
:V NE4
PORT2 C1
VC4-4:VC12:11-20 2:
User H1 1- 3-EGT1
VC 5
VCTRUNK4 4-1 VCTRUNK1 PORT1
: VC User G3
VC4-4:VC12:21-30 12 VC4-4:VC12:1-5
:1-
1 0
VB1 VCTRUNK1 PORT1
User H3
VC4-4:VC12:1-10
4-EGT1
SDH
PORT VCTRUNK
Strip VLAN Label Add VLAN Label Strip VLAN Label
Data(User G) VLAN(100) Data(User G) Data(User G)
Data(User H) VLAN(200) Data(User H) Data(User H)
l The Ethernet LAN services of user G:

SDH link from NE1 to NE2 and the first to fifth VC-12 timeslots of the first VC-4
(VC4-1:VC12:1-5) on the SDH link from NE1 to NE4.
(VC4-4:VC12:1-5) on the EFS8 board of NE1 and the first to fifth VC-12 timeslots of
the fourth VC-4 (VC4-4:VC12:1-5) on the 3-EGT1 board of NE2.
– Are added and dropped by using the sixth to tenth VC-12 timeslots of the fourth VC-4
(VC4-4:VC12:6-10) on the EFS8 board of NE1 and the first to fifth VC-12 timeslots

System
l The Ethernet LAN services of user H:

– Occupy the first to tenth VC-12 timeslots of the first VC-4 (VC4-1:VC12:1-10) on the
SDH link from NE1 to NE2 and the first to tenth VC-12 timeslots of the first VC-4
(VC4-1:VC12:1-10) on the SDH link from NE1 to NE4.
– Are added and dropped by using the eleventh to twentieth VC-12 timeslots of the fourth
VC-4 (VC4-4:VC12:11-20) on the EFS8 board of NE1 and the first to tenth VC-12
timeslots of the fourth VC-4 (VC4-4:VC12:1-10) on the 4-EGT1 board of NE2.
– Are added and dropped by using the twenty-first to thirtieth VC-12 timeslots of the
fourth VC-4 (VC4-4:VC12:21-20) on the EFS8 board of NE1 and the first to tenth
VC-12 timeslots of the fourth VC-4 (VC4-4:VC12:6-15) on the 4-EGT1 board of NE3.

Paramete NE1 NE2 NE4
r
Board EFS8 3-EGT1 4-EGT1 3-EGT1 4-EGT1
Port PORT1 PORT2 PORT1 PORT1 PORT1 PORT1
Enabled/ Enabled Enabled Enabled Enabled Enabled Enabled

Disabled
Working Auto- Auto- Auto- Auto- Auto- Auto-

Mode Negotiatio Negotiatio Negotiatio Negotiatio Negotiatio Negotiatio
n n n n n n
Maximum 1522 1522 1522 1522 1522 1522

Frame
Length
TAG Access Access - - - -
Entry Enabled Enabled - - - -

Detection
Default 100 200 - - - -

VLAN ID
VLAN 0 0 - - - -
Priority

Param NE1 NE2 NE3
eter
Board EFS8 3- 4- 3- 4-
EGT1 EGT1 EGT1 EGT1
Port VCTR VCTR VCTR VCTR VCTR VCTR VCTR VCTR

UNK1 UNK2 UNK3 UNK4 UNK1 UNK1 UNK1 UNK1

System
Param NE1 NE2 NE3

eter
Mappin GFP GFP GFP GFP GFP GFP GFP GFP

g
Protoco
l
TAG Access Access Access Access - - - -
Entry Enable Enable Enable Enable - - - -

Detecti d d d d
on
Default 100 100 200 200 - - - -

VLAN
ID
VLAN 0 0 0 0 - - - -
Priority
Bound VC4-4: VC4-4: VC4-4: VC4-4: VC4-4: VC4-4: VC4-4: VC4-4:

Path VC12- VC12- VC12- VC12- VC12- VC12- VC12- VC12-
1- 6- 11- 21- 1- 1- 1- 1-
VC12- VC12- VC12- VC12- VC12- VC12- VC12- VC12-
5 10 20 30 5 10 5 10
Port UNI UNI UNI UNI - - - -

Type
Table 4-32 Parameters of Ethernet LAN services (IEEE 802.1q bridge)

Board EFS8
VB Name VB1
Bridge Type IEEE 802.1q
Bridge Switch Mode IVL/Ingress Filter Enable
Bridge Learning Mode IVL
Ingress Filter Enabled
VB Mount Port PORT1, PORT2, VCTRUNK1, VCTRUNK2, VCTRUNK3,

VCTRUNK4
VLAN VLAN VLAN filter table 1 VLAN filter table 2

Filtering Filtering
VLAN ID 100 200

System
Forwarding PORT1, VCTRUNK1, PORT2, VCTRUNK3,

Physical Port VCTRUNK2 VCTRUNK4
Hub/Spoke PORT1 Hub
PORT2 Hub
VCTRUNK Spoke
1
VCTRUNK Spoke
2
VCTRUNK Hub
3
VCTRUNK Hub
4

At the convergence node NE1, you need to create An EVPLAN service (IEEE 802.1q bridge)
and a VLAN filtering table need to be created for the convergence node NE1. The access nodes
NE2 and NE4 need to be configured with EPL transparent transmission services only.
Prerequisite
You must be familiar with 4.3.4 Flow of Configuring EVPLAN Services.
l For the EVPLAN services supported by Ethernet switching boards, see 6.1 Service
Procedure
Step 1 Configure the EVPLAN services for user G1 and user H1 on NE1.
services of user G1 and user H1.
l In the NE Explorer, select the EFS8, and then choose Configuration > Ethernet

System

ter
Enabled PORT1: Enabled In this example, PORT1 and PORT2 carry

/ PORT2: Enabled the services and are set to Enabled.
Disable
d

g Mode Negotiation equipment of user G1 and user H1 supports
PORT2: Auto- the auto-negotiation mode. Hence, Working
Negotiation Mode is set to Auto-Negotiation for PORT1
and PORT2.

Frame
Length
default values.
ter
Entry PORT1: Enabled The packets of user G1 and user H1 do not

Detectio PORT2: Enabled carry VLAN tags. You need to enable the
n entry detection function to detect whether the
packets carry VLAN tags. In this example,
Entry Detection is set to Enabled.
TAG PORT1: Access If the service access equipment of user G1

PORT2: Access and user H1 does not support VLANs and if
the transmitted packets do not carry VLAN
tags, TAG is set to Access for PORT1 and
PORT2.
Default PORT1: 100 According to the plan, the VLAN ID is set to

VLAN PORT2: 200 100 on the transmission network side for
ID EVPLAN services between user G1, user G2,
and user G3. The VLAN ID is set to 200 on
the transmission network side for EVPLAN
services between user H1, user H2, and user
H3. In this case, the service data is isolated.

System

ter
VLAN 0 This parameter adopts the default value.

Priority
2. Set the attributes of the internal ports (VCTRUNK1, VCTRUNK2, VCTRUNK3, and
VCTRUNK4 on the EFS8 board) used by the service between user G1 and user G2, the
service between user G1 and user G3, the service between user H1 and user H2, and the
service between user H1 and user H3.
ter
Entry VCTRUNK1: Enabled The packets of user G2, user G3, user H2, and
Detectio VCTRUNK2: Enabled user H3 do not carry VLAN tags. You need
n to enable the entry detection function to
VCTRUNK3: Enabled detect the VLAN tags of the packets. In this
VCTRUNK4: Enabled example, Entry Detection is set to
Enabled.
TAG VCTRUNK1: Access If the service access equipment of user G2,

VCTRUNK2: Access user G3, user H2, and user H3 does not
VCTRUNK3: Access packets do not carry VLAN tags, TAG is set
VCTRUNK4: Access to Access for the four VCTRUNKs.
Default VCTRUNK1: 100 According to the plan, the VLAN ID is set to

VLAN VCTRUNK2: 100 100 on the transmission network side for
ID EVPLAN services between user G1, user G2,
VCTRUNK3: 200 and user G3. The VLAN ID is set to 200 on
VCTRUNK4: 200 the transmission network side for EVPLAN
services between user H1, user H2, and user
H3. In this case, the service data is isolated.
VLAN VCTRUNK1: 0 This parameter adopts the default value.

Priority VCTRUNK2: 0
VCTRUNK3: 0
VCTRUNK4: 0

System
Parameter Value in This Description

Example

Attributes VCTRUNK2: UNI namely, the interface of the service
provider located near the user side. The
VCTRUNK3: UNI UNI interface processes the tag attribute of
VCTRUNK4: UNI IEEE 802.1Q-compliant packets. That is,
the UNI interface processes and identifies
the VLAN information of the accessed user
packets, according to the supported tag
flag, namely, Tag Aware, Access, and
Hybrid.
ter
VCTRUNK3: GFP the Ethernet boards of the interconnected
VCTRUNK4: GFP equipment at both ends must be set to the
same value.

+1] same value.
VCTRUNK3:
+1]
VCTRUNK4:
+1]

VCTRUNK3: FCS32 the interconnected equipment at both ends
VCTRUNK4: FCS32 must be set to the same value.
Sequenc VCTRUNK3: Big endian the VCTRUNKs on the Ethernet boards of
e VCTRUNK4: Big endian the interconnected equipment at both ends

System

ter

for CRC VCTRUNK3: - VCTRUNKs on the Ethernet boards of the
VCTRUNK4: - interconnected equipment at both ends must
Apply.
ter
Enablin VCTRUNK1: Enabled In this example, Enabling LCAS is set to

g LCAS VCTRUNK2: Enabled Enabled.

Mode Mode default value Huawei Mode. If the
VCTRUNK2: Huawei interconnected equipment at both ends is
Mode Huawei equipment, LCAS Mode is set to
Huawei Mode for the interconnected
equipment.

off Time VCTRUNK2: 2000 default value 2000. You can set this
(ms) parameter according to the expected hold off
time of LCAS switching.

Time(s) VCTRUNK2: 300 default value 300. You can set this parameter
according to the expected WTR duration of
LCAS recovery.
TSD VCTRUNK1: Disabled In this example, TSD is set to Disabled. In

VCTRUNK2: Disabled this case, the LCAS protocol does not
monitor the status of the B3 or BIP bit errors
of a VCTRUNK member.

t
Directio
n

System

ter

Directio
n
r This
Example

G1←→ ble Ports K1 EFS8 board is used by the service between
user G2 user G1 and user G2.
Av Leve VC12-xv The service between user G1 and user G2 uses

aila l a 10 Mbit/s bandwidth. Hence, five VC-12s
ble need to be bound.
Bo For the method of computing the bound
un timeslots based on the service bandwidth, see
d 6.3 Ethernet Service Bandwidths Carried
Pat by VCTRUNKs of Ethernet Boards.
hs
Serv Bidirectio The service between user G1 and user G2 is a
ice nal Bidirectional service.
Dire
ction
Avai VC4-4 For the resources used by other boards, see 6.2
lable Requirements for Binding Paths with
Reso VCTRUNKs on Ethernet Boards.
urce
s
Avai VC12-1 to Five VC-12s need to be bound for user G2. In

lable VC12-5 this example, the first to the fifth VC-12s need
Tim to be selected in sequence.
eslot
s
user G1 Configura VCTRUN As shown in Figure 4-33, VCTRUNK2 of the

←→ ble Ports K2 EFS8 board is used by the service between
user G3 user G1 and user G3.

System

r This
Example
Av Leve VC12-xv The service between user G1 and user G3 uses

aila l a 10 Mbit/s bandwidth. Hence, five VC-12s
hs
Serv Bidirectio The service between user G1 and user G3 is a
Dire
ction
urce
s
Avai VC12-6 to Five VC-12s need to be bound for the service

lable VC12-10 between user G1 and user G3. In this example,
Tim the sixth to the tenth VC-12s need to be
eslot selected in sequence.
s

H1←→ ble Ports K3 EFS8 board is used by the service between
user H2 user H1 and user H2.
Av Leve VC12-xv The service between user H1 and user H2 uses

aila l a 20 Mbit/s bandwidth. Hence, 10 VC-12s
hs
Serv Bidirectio The service between user H1 and user H2 is a
Dire
ction
urce
s

System

r This
Example
Avai VC12-11 Ten VC-12s need to be bound for the service

lable to between user H1 and user H2. In this example,
Tim VC12-20 the eleventh to the twentieth VC-12s need to
eslot be selected in sequence.
s

H1←→ ble Ports K4 EFS8 board is used by the service between
user H3 user H1 and user H3.
Av Leve VC12-xv The service between user H1 and user H3 uses

aila l a 20 Mbit/s bandwidth. Hence, 10 VC-12s
hs
Serv Bidirectio The service between user H1 and user H3 is a
Dire
ction
urce
s
Avai VC12-21 Ten VC-12s need to be bound for the service

lable to between user H1 and user H3. In this example,
Tim VC12-30 the twenty-first to the thirtieth VC-12s need to
eslot be selected in sequence.
s
l Click New.
l Set the required parameters in the Create Ethernet LAN Service dialog box that is
displayed.

System

This
Example
Board NE1-4-EFS8 -

bridge.
VB Type 802.1q IEEE 802.1q bridge supports isolation by using one

layer of VLAN tags. This bridge checks the contents
of the VLAN tags that are in the packets and
performs Layer 2 switching according to the
destination MAC addresses and the VLAN IDs of
the packets.
Bridge IVL/Ingress When the bridge adopts the IVL learning mode, the
Switch Mode Filter Enable entry in the MAC address table is created according
to the source MAC address, VLAN ID, and source
port of the data frame. The entry is not valid for all
the VLANs..
Bridge IVL -
Learning
Mode
Ingress Filter Enabled This parameter checks the validity of VLAN tags. If
the VLAN ID is not the same as the VLAN ID
defined in the VLAN filtering table, the data frame
is discarded.
MAC Enabled -
Address Self-
Learning

l In Available Mounted Ports, select PORT1, PORT2, VCTRUNK1, VCTRUNK2,
VCTRUNK3, and VCTRUNK4. Then, click .
l OK.
4. Create a VLAN filtering table.
l Select the created bridge and click the VLAN Filtering tab.
l Click New.
l Create the VLAN filtering table for user G1, user G2, and user G3.

System

This
Example
VLAN ID 100 According to the plan, the VLAN ID is set to 100 on

(e.g.1,3-6) the transmission network side for EVPLAN services
between user G1, user G2, and user G3.
l In Available Forwarding Ports, select PORT1, VCTRUNK1, and VCTRUNK2. Click

. Then, click Apply.
l Create the VLAN filtering table for user H1, user H2, and user H3.
This
Example
VLAN ID 200 According to the plan, the VLAN ID is set to 200 on

(e.g.1,3-6) the transmission network side for EVPLAN services
between user H1, user H2, and user H3.

. Then, click OK.
5. Change the Hub/Spoke attribute of the ports mounted to the bridge.
l Change the Hub/Spoke attribute of the port mounted to the bridge. After setting the
parameters, click Apply.
Example
Hub/Spoke PORT1: Hub If user G2 need not communicate with user G3,
VCTRUNK1: set VCTRUNK1 and VCTRUNK2 ports that
Spoke receive the services of user G2 and user G3 to
Spoke. Ports of the Spoke attribute cannot
VCTRUNK2: communicate with each other. A port of the Hub
Spoke attribute can communicate with a port of the
PORT2: Hub Spoke or Hub attribute.
VCTRUNK3:
Hub
VCTRUNK4:
Hub
6. Configure the cross-connections from the Ethernet service to the SDH link for user G2,
user G3, user H2, and user H3.
l In the NE Explorer, select NE1, and then choose Configuration > SDH Service

System

r This
Example
User G1 Level VC12 The timeslot bound with the service

←→ between user G1 and user G2 is at the
user G2 VC-12 level. The service level must be
consistent with the level of the path bound
with the VCTRUNK.
Direction Bidirectiona The service between user G1 and user G2

l is a Bidirectional service.


of VCTRUNK1, Available Resources is
set to VC4-4.

Range(e.g. Available Timeslot, which is set for the
1,3-6) paths bound with VCTRUNK1. In the case
Timeslot is from VC12-1 to VC12-5.


line board.

VC-12s.
Activate Yes -
Immediatel
y

System

r This
Example
User G1 Level VC12 The timeslot bound with the service

←→ between user G1 and user G3 is at the
user G3 VC-12 level. The service level must be
with the VCTRUNK.
Direction Bidirectiona The service between user G1 and user G3

l is a bidirectional service.


set to VC4-4.



line board.

VC-12s.
Activate Yes -
Immediatel
y

System

r This
Example
User H1 Level VC12 The timeslot bound with the service

←→ between user H1 and user H2 is at the
user H2 VC-12 level. The service level must be
with the VCTRUNK.
Direction Bidirectiona The service between user H1 and user H2



set to VC4-4.



line board.

VC-12s.
Activate Yes -
Immediatel
y

System

r This
Example
User H1 Level VC12 The timeslot bound with the service

←→ between user H1 and user H3 is at the
user H3 VC-12 level. The service level must be
with the VCTRUNK.
Direction Bidirectiona The service between user H1 and user H3



set to VC4-4.



line board.

VC-12s.
Activate Yes -
Immediatel
y

System

NOTE
SCB Board.
----End
Relevant Task
4.10 Configuring EVPLAN Services (IEEE 802.1ad Bridge)

The QinQ technology provides a cheap and easy solution for Layer 2 virtual private networks
(VPNs). The IEEE 802.1ad bridge uses the QinQ technology to provide the VPN solution, thus
facilitating the identifying, differentiating and grooming EVPLAN services.
A network operator requires that the voice over IP (VoIP) and high speed Internet (HSI) services
sent to the transmission network be uniformly labeled and groomed at the convergence node.
The services of user M and user N are transmitted from the access nodes NE2 and NE4
respectively to the convergence node NE1 through the Ethernet transparent transmission boards.
VoIP and HSI services carrying different C-VLAN IDs are tagged with different S-VLAN IDs.
The service data is isolated and exchanged at Layer 2 through S-VLAN filtering.
An EVPLAN service (IEEE 802.1ad bridge) and the corresponding S-VLAN filtering table need
to be created for the convergence node NE1. The access nodes NE2 and NE4 need to be
configured with EPL transparent transmission services only.

A network operator requires that the voice over IP (VoIP) and high speed Internet (HSI) services
sent to the transmission network be uniformly labeled and groomed at the convergence node.
Service Requirement
As shown in Figure 4-34, the transmission network is required to carry the VoIP and HSI
services.
User requirements:

System
l The VoIP services of user M and user N are sent to the transmission network at NE2 and
NE4 respectively and to the VoIP server at the convergence node NE1. The services share
a 20 Mbit/s bandwidth.
l The HSI services of user M and user N are sent to the transmission network at NE2 and
NE4 respectively and to the HSI server at the convergence node NE1. The services share
a 40 Mbit/s bandwidth.
l The VoIP services need to be isolated from the HSI services.
l The data communication equipment of user M and user N provides 100 Mbit/s Ethernet
electrical interfaces of which the working mode is auto-negotiation, and does not support
VLAN.
– C-VLAN ID of the VoIP services: 10
– C-VLAN ID of the HSI services: 20
NOTE
The application scenarios where one branch needs to communicate with other branches are as follows:
l User M needs to communicate with user N.
l User M need not communicate with user N.
If user M and user N need to communicate with each other, skip Step 1.5 in which you change the Hub/
Spoke attributes of ports connected to the bridge.
Requirement of the operator: The operator requires that all services received from the user side
should be uniformly labeled and groomed through planned S-VLANs.
l S-VLAN ID of the VoIP services: 100

l S-VLAN ID of the HSI services: 200
Figure 4-34 Networking diagram for configuring EVPLAN services (IEEE 802.1ad bridge)
NE2: NE4:
4-EGT1 6-SL4D-2 6-SL4D-1 4-EGT1
NE3
NM
Service C-VLAN Service C-VLAN
VoIP 10 VoIP 10
HSI 20 HSI 20
PORT1 PORT1
NE2 NE4
User M NE1 User N
VoIP server
PORT1 PORT2 HSI server
VCTRUNK NE1:
4-EFS8 6-SL4D-1 6-SL4D-2
VB1 S-VLAN 100 VB1 S-VLAN 200
PORT1 PORT2

System

For the EVPLAN (IEEE 802.1ad bridge) services supported by Ethernet switching boards, refer
to Table 6-1.
IEEE 802.1ad bridge to implement EVPLAN services in which VoIP data is isolated from HSI
data.
l The VoIP services tagged with C-VLAN ID 10 from NE2 and NE4 are further tagged with
S-VLAN ID 100 when they arrive at the IEEE 802.1ad bridge of NE1. Then, the services
are forwarded to the VoIP server through Layer 2 switching.
l The HSI services tagged with C-VLAN ID 20 from NE2 and NE4 are further tagged with
S-VLAN ID 200 when they arrive at the IEEE 802.1ad bridge of NE1. Then, the services
are forwarded to the HSI server through Layer 2 switching.
The access nodes NE2 and NE4 each are configured with an EGT1 board. The EPL services are
configured to implement transparent transmission from NE2 and NE4 to NE1.

The services of user M and user N are transmitted from the access nodes NE2 and NE4
respectively to the convergence node NE1 through the Ethernet transparent transmission boards.
VoIP and HSI services carrying different C-VLAN IDs are tagged with different S-VLAN IDs.
The service data is isolated and exchanged at Layer 2 through S-VLAN filtering.
Figure 4-35 shows the signal flow of the EVPLAN services (IEEE 802.1ad bridge) and the
timeslot allocation to the EVPLAN services (IEEE 802.1ad bridge).
Figure 4-35 Signal flow of and timeslot allocation to EVPLAN services (IEEE 802.1ad bridge)
NE1:EFS8 NE2:EGT1
-30 VCTRUNK1 PORT1

SVLAN 100 12:1 User M
-1:VC
VC4 VC4-4:VC12:1-30
PORT1
VoIP VCTRUNK1
Server
VC4-4:VC12:1-30
SVLAN 200 NE4:EGT1

VCTRUNK2 VC 4
PORT2 -1:VC
HSI 12:1
VC4-4:VC12:31-60 -30
Server PORT1
VCTRUNK1
User N
VC4-4:VC12:1-30
VB1 SDH
PORT VCTRUNK
Strip S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
C-VLAN(10) Data(VoIP) S-VLAN(100) C-VLAN(10) Data(VoIP) C-VLAN(10) Data(VoIP)
C-VLAN(20) Data(HSI) S-VLAN(200) C-VLAN(20) Data(HSI) C-VLAN(20) Data(HSI)
l The services of user M:

System
– Occupy the first to thirtieth VC-12 timeslots of the first VC-4 (VC4-1:VC12:1-30) on
– Are added and dropped by using the first to thirtieth VC-12 timeslots of the fourth VC-4
(VC4-4:VC12:1-30) on the EFS8 board of NE1 and the first to thirtieth VC-12 timeslots
of the fourth VC-4 (VC4-4:VC12:1-30) on the EGT1 board of NE2.
l The services of user N:
– Occupy the first to thirtieth VC-12 timeslots of the first VC-4 (VC4-1:VC12:1-30) on
– Are added and dropped by the using the thirty-first to sixtieth VC-12 timeslots of the
fourth VC-4 (VC4-4:VC12:31-60) on the EFS8 board of NE1 and the first to thirtieth
VC-12 timeslots of the fourth VC-4 (VC4-4:VC12:1-30) on the EGT1 board of NE4.


Disabled

Maximum 1522 1522 1522 1522

Frame Length
Port Type C-Aware C-Aware C-Aware C-Aware


Protocol
Port Type C-Aware C-Aware - -

-VC12-30 1-VC12-60 -VC12-30 -VC12-30

System
Table 4-35 Parameters of Ethernet LAN services (IEEE 802.1ad bridge)

Board EFS8
VB Name VB1
Bridge Type IEEE 802.1ad
Bridge Switch Mode IVL/Ingress Filter Enable
Bridge Learning Mode IVL
Ingress Filter Enabled
Operation Type Add S-VLAN base for Port and C-VLAN
VB Port 1 2 3 4
Mount Port PORT1 PORT2 VCTRUNK1 VCTRUNK2
C-VLAN 10 20 10 20 10 20
S-VLAN 100 200 100 200 100 200
VLAN VLAN VLAN filter table 1 VLAN filter table 2

Filterin Filtering
g
VLAN ID 100 200
Forwarding PORT1, VCTRUNK1, PORT2, VCTRUNK1,

Physical Port VCTRUNK2 VCTRUNK2
Hub/ PORT1 Hub

Spoke
PORT2 Hub
VCTRUNK Spoke
1
VCTRUNK Spoke
2

An EVPLAN service (IEEE 802.1ad bridge) and the corresponding S-VLAN filtering table need
to be created for the convergence node NE1. The access nodes NE2 and NE4 need to be
configured with EPL transparent transmission services only.
Prerequisite

System
l For the EVPLAN services supported by Ethernet switching boards, see 6.1 Service
l For the VCTRUNK binding requirements of Ethernet transparent transmission boards, see
6.2 Requirements for Binding Paths with VCTRUNKs on Ethernet Boards.
The IEEE 802.1ad provider bridge supports ports with the C-Aware and S-Aware attributes only.
The C-Aware ports are used to add and strip the S-VLAN tags. The S-Aware ports are used to
transparently transmit the S-VLAN tag.
The IEEE 802.1ad provider bridge supports the following operation types:
l Adding the S-VLAN tag based on the port

l Adding the S-VLAN tag based on the port and C-VLAN
l Performing port mounting based on the port
l Performing port mounting based on the port and the S-VLAN
This topic describes the four operation types when Bridge Switch Mode of the IEEE 802.1ad
provider bridge is set to IVL/Ingress Filter Enabled.
l Adding the S-VLAN based on the port: The packets that enter the C-Aware port are added
with the preset S-VLAN tag, and are forwarded in the bridge according to the S-VLAN
filtering table. Before the packets leave the C-Aware port, the S-VLAN tag is stripped.
l Adding the S-VLAN tag based on the port and C-VLAN: The entry detection is performed
for the packets that enter the C-Aware port. Then, the corresponding S-VLAN tags are
added to the packets according to the mapping relation between the C-VLAN tags and the
S-VLAN tags of the packets. If the mapping relation does not exist, the packets are
discarded. After the S-VLAN tags are added, the packets enter the bridge, where the packets
are forwarded according to the S-VLAN filtering table. Before the packets leave the C-
Aware port, the S-VLAN tag is stripped.
NOTE
l The same C-Aware port supports different C-VLAN tags being mapped to different S-VLAN
tags, but does not support the same C-VLAN tag being mapping to multiple S-VLAN tags.
l Performing port mounting based on the port: The packets that enter the S-Aware port are
not filtered. Instead, the S-VLAN switch is performed directly. The packets must have the
S-VLAN tags. Otherwise, the packets are discarded. When the packets leave the S-Aware
port, the packets are transparently transmitted.
l Performing port mounting based on the port and the S-VLAN: The entry filtering is
performed according to the preset S-VLAN tag. The packets that do not belong to the S-
VLAN are discarded. Then, the packets are forwarded according to the S-VLAN filtering
table. When the packets leave the S-Aware port, the packets are transparently transmitted.
In the case of the four operation types, the following conditions must be met before the packets
leave a port:
l The port is contained in the S-VLAN filtering table that is created by the user.
l The S-VLAN ID corresponding to the port must be specified when the user manually
mounts the port to the bridge.

System
– In the case of a C-Aware port, the S-VLAN ID corresponding to the port is the S-VLAN
ID that is added when the packets enter the port.
– In the case of an S-Aware port, the S-VLAN ID corresponding to the port is the S-VLAN
ID that is set when the user mounts the port to the bridge. If the S-Aware port is mounted
based on the port, the S-VLAN ID is considered to contain all the legal S-VLAN IDs.
Procedure
Step 1 Configure the EVPLAN services on NE1.
VoIP server and HSI server.
Example
Enabled/ PORT1: Enabled In this example, PORT1 and PORT2 carry

Disabled PORT2: Enabled the services and Enabled/Disabled is set
to Enabled for PORT1 and PORT2.
Working PORT1: Auto- In this example, the VoIP server and HSI
Mode Negotiation server support the auto-negotiation mode.
PORT2: Auto- Hence, Working Mode is set to Auto-
Negotiation Negotiation for PORT1 and PORT2.
Maximum PORT1: 1522 Generally, this parameter adopts the

Frame PORT2: 1522 default value 1522.
Length
Loopback PORT2: Non-Loopback diagnosis. In this example, MAC
Loopback is set to Non-Loopback.
Loopback PORT2: Non-Loopback diagnosis. In this example, PHY
Loopback is set to Non-Loopback.
default values.

System
Parameter Value in This Example Description
Port PORT1: C-Aware The C-Aware or S-Aware attribute

Attributes PORT2: C-Aware must be selected for the port when you
configure the IEEE 802.1ad bridge.
The C-Aware port connects to the port
in the client network, identifies and
processes the packets that contain C-
VLAN tags (namely, client tags). The
S-Aware port connects to the port on
the network side, identifies and
processes the packets that contain S-
VLAN tags (namely, service tags of
the network operator).
l It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is
set to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless.
2. Set the attributes of the internal ports (VCTRUNK1 and VCTRUNK2 on the EFS8 board)
used by the services of user M and N.
Paramet Value in This Description
er Example
Port VCTRUNK1: C-Aware The C-Aware or S-Aware attribute must be

Attributes VCTRUNK2: C-Aware selected for the port when you configure the
IEEE 802.1ad bridge. The C-Aware port
connects to the port in the client network,
identifies and processes the packets that
contain C-VLAN tags (namely, client tags).
The S-Aware port connects to the port on the
network side, identifies and processes the
packets that contain S-VLAN tags (namely,
service tags of the network operator).
l It is unnecessary to set the parameters on the TAG Attributes tab. If the port type is
set to C-Aware or S-Aware, the parameters on the TAG Attributes are meaningless.

System

ter
same value.

+1] same value.


Apply.
ter
Enablin VCTRUNK1: Enabled In this example, Enabling LCAS is set to

g LCAS VCTRUNK2: Enabled Enabled.

Mode Mode default value Huawei Mode. If the
VCTRUNK2: Huawei interconnected equipment at both ends is
Mode Huawei equipment, LCAS Mode is set to
Huawei Mode for the interconnected
equipment.

System

ter

off Time VCTRUNK2: 2000 default value 2000. You can set this
(ms) parameter according to the expected hold off
time of LCAS switching.

Time(s) VCTRUNK2: 300 default value 300. You can set this parameter
according to the expected WTR duration of
LCAS recovery.
TSD VCTRUNK1: Disabled In this example, TSD is set to Disabled. In

VCTRUNK2: Disabled this case, the LCAS protocol does not
monitor the status of the B3 or BIP bit errors
of a VCTRUNK member.

t
Directio
n

Directio
n
User Paramet Value in Description
er This
Example

M ble Ports K1 EFS8 board is used by the service of user M.
Av Lev VC12-xv The service of user M uses a 60 Mbit/s

aila el bandwidth. Hence, 30 VC-12s need to be
ble bound.
und timeslots based on the service bandwidth, see

System

er This
Example
Ser Bidirection The service of user M is a bidirectional service.

vic al
e
Dir
ecti
on

Res
our
ces
Av VC12-1 to Thirty VC-12s need to be bound for user M. In

aila VC12-30 this example, the first to the thirtieth VC-12s
ble need to be selected in sequence.
Ti
me
slot
s
User N Configura VCTRUN As shown in Figure 4-35, VCTRUNK2 of the

ble Ports K2 EFS8 board is used by the service of user N.
Av Lev VC12-xv The service of user N uses a 60 Mbit/s

aila el bandwidth. Hence, 30 VC-12s need to be
ble bound.
und timeslots based on the service bandwidth, see
Ser Bidirection The service of user N is a bidirectional service.

vic al
e
Dir
ecti
on

Res
our
ces

System

er This
Example
Av VC12-31 Thirty VC-12s need to be bound for user N. In

aila to this example, the thirty-first to the sixtieth
ble VC12-60 VC-12s need to be selected in sequence.
Ti
me
slot
s
l Click New.
l Set the required parameters in the Create Ethernet LAN Service dialog box that is
displayed.

This
Example
Board NE1-4-EFS8 -

bridge.
VB Type 802.1ad The IEEE 802.1ad bridge supports data frames with
two layers of VLAN tags. This bridge adopts the
outer S-VLAN tags to isolate different VLANs and
supports only the mounted ports whose attributes are
C-Aware or S-Aware.
Bridge IVL/Ingress This bridge checks the contents of the VLAN tags
Switch Mode Filter Enable that are in the packets and performs Layer 2
switching according to the destination MAC
addresses and the S-VLAN IDs of the packets.
Bridge IVL -
Learning
Mode
Ingress Filter Enabled -
MAC Enabled -
Address Self-
Learning

System

l Set the parameters for service mounting in the Service Mount Configuration dialog
box that is displayed.
Attribute Attribute Value
Operation Adding S-VLAN tags based on Port and C-VLAN

Type
VB Port 1 2 3 4
Mount Port PORT1 PORT2 VCTRUNK1 VCTRUNK2
C-VLAN 10 20 10 20 10 20
S-VLAN 100 200 100 200 100 200
l Click OK.
4. Create a VLAN filtering table.
l Select the created bridge and click the VLAN Filtering tab.
l Click New.
l Create the VLAN filtering table of the VoIP service.

This
Example
VLAN ID 100 According to the plan, the S-VLAN ID is 100 for the
(e.g.1,3-6) VoIP service.

. Then, click Apply.
l Create the VLAN filtering table of the HSI service.

This
Example
VLAN ID 200 According to the plan, the S-VLAN ID is 200 for the
(e.g.1,3-6) HSI service.

. Then, click OK.
5. Change the Hub/Spoke attribute of the ports mounted to the bridge.
NOTE
If user M and user N need to communicate with each other, proceed to Step 1.6.

System
l Change the Hub/Spoke attribute of the port mounted to the bridge.
Example
Hub/Spoke PORT1: Hub User M and user N need not communicate with
PORT2: Hub each other. In this case, set VCTRUNK1 and
VCTRUNK2 that access the services of user M
VCTRUNK1: and user N to the Spoke attribute. Ports of the
Spoke Spoke attribute cannot communicate with each
VCTRUNK2: other.
Spoke A port of the Hub attribute can communicate
with a port of the Spoke or Hub attribute.
6. Configure the cross-connections from the Ethernet service to the SDH link for user M and
user N.
l In the NE Explorer, select NE1, and then choose Configuration > SDH Service
r This
Example
User M Level VC12 The timeslot bound with the service of user
M is at the VC-12 level. The service level
Direction Bidirectiona The service of user M is a bidirectional

l service.


set to VC4-4.


System

r This
Example


line board.

1,3-6) of sink timeslots must be, however,
consistent with the number of sink
timeslots.
Activate Yes -
Immediatel
y
User N Level VC12 The timeslot bound with the service of user
N is at the VC-12 level. The service level
Direction Bidirectiona The service of user N is a bidirectional

l service.


set to VC4-4.



System

r This
Example

line board.

same as the number of sink timeslots.
Activate Yes -
Immediatel
y

NOTE
SCB Board.
----End
Relevant Task
4.11 Ethernet Port Configuration Parameters

Before configuring an Ethernet service, you need to configure the corresponding Ethernet ports.
4.11.1 Basic Attributes

This topic describes the parameters, such as the port attribute, port enabling status, and maximum
frame length, that are used for configuring the basic attributes of an Ethernet port.
4.11.2 Flow Control
This topic describes the parameters, such as autonegotiation and non-autonegotiation, which are
used for configuring flow control function of an Ethernet port.
4.11.3 Network Attributes
This topic describes the parameters, such as port attribute and P port encapsulation format, which
are used for configuring network attributes of an Ethernet port.
4.11.4 Advanced Attributes
This topic describes the parameters, such as the loop detection, loop port shutdown, and traffic
threshold (Mbit/s), which are used for configuring the advanced attributes of an Ethernet port.

System
4.11.5 TAG Attributes

Tag attributes are important attributes that are used for configuring Ethernet services, including
the parameters such as the default VLAN ID, VLAN priority, ingress detection setting, and tag
ID.
4.11.6 Encapsulation/Mapping
The equipment supports the setting of encapsulation and mapping protocols for Ethernet packets,
including the parameters such as mapping protocol, scrambling code, and CRC or not.
4.11.7 Bound Path
This topic describes the parameters, such as available resources, available timeslots, and service
direction, which are used for binding a path with an Ethernet port.
4.11.1 Basic Attributes

This topic describes the parameters, such as the port attribute, port enabling status, and maximum
frame length, that are used for configuring the basic attributes of an Ethernet port.
Table 4-36 lists the parameters that are used for configuring the basic attributes of an Ethernet
port.
Table 4-36 Parameters for configuring the basic attributes of an Ethernet port
Port PORTn Displays all the available ports

on an Ethernet port. The letter
n indicates the number of the
PORT port.
Name For example: PORT-1 Specifies the name of a PORT

port. The name can contain up
to 32 characters in English or
16 characters in Chinese.
Enabled/Disabled Disabled, Enabled Enabled indicates that this

Default value: Disabled port is used and services are
available. Disabled indicates
that the services on this port are
not processed. Hence, when
configuring a service, you need
to enable the port to be used.
Working Mode Auto-Negotiation, 100M Full- Specifies the working mode of

Duplex, 1000M Full-Duplex the Ethernet port on a board.
Default value: Auto- This parameter determines the
Negotiation maximum transmission rate
and communication mode of
NOTE
the Ethernet port.
l The EGT1 board supports
only Auto-Negotiation, and When setting this parameter,
1000M Full-Duplex. you must ensure the working
l The EFS8 board supports modes of the interconnected
Auto-Negotiation, and 100M ports are the same. Otherwise,
Full-Duplex. the services are not available.

System
Maximum Frame Length 1518-9600 The Maximum Frame

Default value: 1522 Length (Ethernet Port
Attribute) parameter specifies
the maximum frame length
that is supported at an Ethernet
port.
You can click 7.2 Maximum
Frame Length (Ethernet
Port Attribute) to display the
Port Physical Parameters Displays the value that is Displays the actual working
queried. status of the port.
MAC Loopback Non-Loopback, Inloop The MAC Loopback

Default value: Non-Loopback (Ethernet Port Attribute)
parameter specifies the MAC
loopback state at an Ethernet
port. Port loopback setting is
applied to locating faults only.
You can click 7.5 MAC
Loopback (Ethernet Port
Attribute) to display the
PHY Loopback Non-Loopback, Inloop The PHY Loopback

Default value: Default Value (Ethernet Port Attribute)
parameter specifies the PHY
loopback state at an Ethernet
port. Port loopback setting is
applied to locating faults only.
You can click 7.6 PHY
Loopback (Ethernet Port
4.11.2 Flow Control

This topic describes the parameters, such as autonegotiation and non-autonegotiation, which are
used for configuring flow control function of an Ethernet port.
Table 4-37 lists the parameters that are used for configuring flow control of an Ethernet port.

System
Table 4-37 Parameters for configuring flow control of an Ethernet port

Port PORTn Displays all the available

MAC ports on an Ethernet
board.
Specifies the PORT port. The
letter n indicates the number of
the PORT port.
Non-Autonegotiation Disabled, Enable Symmetric The Non-Autonegotiation

Flow Control Mode Flow Control, Send Only, Flow Control Mode
Receive Only (Ethernet Port Attribute)
Default value: Disable specifies the flow control
mode adopted when an
Ethernet port works in non-
auto-negotiation mode.
You can click 7.3 Non-
Autonegotiation Flow
Control Mode (Ethernet
Autonegotiation Flow Disabled, Enable The Autonegotiation Flow

Control Mode Dissymmetric Flow Control, Control Mode (Ethernet
Enable Symmetric Flow Port Attribute) specifies the
Control, Enable Symmetric/ flow control mode adopted
Dissymmetric Flow Control when an Ethernet port works in
Default value: Disabled auto-negotiation mode.
You can click 7.4
Autonegotiation Flow
Control Mode (Ethernet
4.11.3 Network Attributes

This topic describes the parameters, such as port attribute and P port encapsulation format, which
are used for configuring network attributes of an Ethernet port.
Table 4-38 lists the parameters that are used for configuring network attributes of an Ethernet
port.

System
Table 4-38 Parameters for configuring network attributes of an Ethernet port

Port PORTn or VCTRUNKn Specifies the PORT or

VCTRUNK port. The letter n
indicates the number of the
port.
Port Attributes The value ranges of the The Port Attributes

parameters are different from (Ethernet Port) parameter
each other for different boards specifies the position of a port
and products. You can click in the network. Different port
the hyperlink in the attributes support different
description to display the packets.
specific information. You can click 7.1 Port
Attributes (Ethernet Port) to
information.
4.11.4 Advanced Attributes

This topic describes the parameters, such as the loop detection, loop port shutdown, and traffic
threshold (Mbit/s), which are used for configuring the advanced attributes of an Ethernet port.
Table 4-39 lists the parameters that are used for configuring the advanced attributes of an
Ethernet port.
Table 4-39 Parameters for configuring the advanced attributes of an Ethernet port
Port PORTn Indicates the PORT. The

letter n indicates the
number of the PORT port.
Transmitting Rate (kbit/s) For example: 0 Indicates the Transmitting

Rate.
Receiving Rate (kbit/s) For example: 0 Indicates the Receiving

Rate.

System
Broadcast Packet Suppression Enabled, Disabled The Broadcast Packet

Default value: Disabled Suppression (Ethernet
Interface Attributes)
parameter specifies
whether to enable the
function for a port to
suppress the broadcast
packets and to control the
traffic of the broadcast data
packets that enter the port.
If the broadcast packet
suppression function is
enabled, and if the
broadcast traffic exceeds
the specified threshold
value, the broadcast
packets that enter the port
are discarded.
You can click 7.12
Broadcast Packet
Suppression (Ethernet
Interface Attributes) to
information.
Broadcast Packet Suppression 10%-100% The Broadcast Packet

Threshold Default value: 30% Suppression Threshold
(Ethernet Interface
Attributes) parameter
allocates the specified
bandwidth to the broadcast
packets. The bandwidth is
allocated on the basis of the
traffic proportion at the
port. If the bandwidth
allocated to the broadcast
packets reaches the
specified threshold, the port
discards the broadcast data
packets that are received.
You can click 7.11
Broadcast Packet
Suppression Threshold
(Ethernet Interface
Attributes) to display the

System
Traffic Threshold(Mbit/s) 0-100 (FE), 0-1000 (GE), in The Traffic Threshold

step length of 1 (Mbit/s) (External
Default value: 100 (FE), Ethernet Port Attribute)
1000 (GE) parameter specifies the data
flow threshold at external
physical ports.
You can click 7.10 Traffic
Threshold(Mbit/s)
(External Ethernet Port
Port Traffic Threshold Time 0-30 The Port Traffic

Window(Min) Default value: 0 Threshold Time Window
(Min) parameter specifies
the duration for a
VCTRUNK or a IP port to
monitor the traffic after the
zero traffic monitoring
function of the port is
enabled.
You can click 7.14 Port
Traffic Threshold Time
Window(Min) to display
Loop Detection Enabled, Disabled The Loop Detection

Default value: Disabled (Ethernet Port Attribute)
function of reporting the
self-loop alarms after one
of the following loopback
cases is detected.
You can click 7.8 Loop
Detection (Ethernet Port
Loop Port Shutdown Enabled, Disabled The Traffic Threshold

Default value: Enabled (Mbit/s) (External
Ethernet Port Attribute)
parameter specifies the data
flow threshold at external
physical ports.
You can click 7.9 Loop
Port Shutdown (Ethernet
Port Attribute) to display

System
4.11.5 TAG Attributes

Tag attributes are important attributes that are used for configuring Ethernet services, including
the parameters such as the default VLAN ID, VLAN priority, ingress detection setting, and tag
ID.
Table 4-40 lists the parameters that are used for configuring the tag attributes of an Ethernet
port.
Table 4-40 Parameters for configuring the tag attributes of an Ethernet port
Port PORTn Specifies the PORT. The letter n

indicates the number of the port.
TAG Access, Tag Aware, Hybrid The Tag Identifier parameter

Default value: Tag Aware indicates that the Ethernet port
supports IEEE 802.1Q Ethernet
packets that contain VLAN tags.
You can set three attributes to
differentiate the packets from each
other so that these packets can be
transmitted efficiently.
You can click 7.19 TAG to display
Default VLAN ID 1-4095 The Default VLAN ID (Ethernet

Default value: 1 Port Attribute) parameter
specifies the default VLAN ID of
a port.
You can click 7.16 Default VLAN
ID (Ethernet Port Attribute) to
display the detailed information.
VLAN Priority 0-7 The VLAN Priority (Ethernet

Default value: 0 Port Attribute) parameter
specifies the priority of the default
VLAN ID of a port. It indicates the
priority of the service quality.
You can click 7.17 VLAN
Priority (Ethernet Port
Attribute) to display the detailed
information.
Entry Detection Enabled, Disabled The Entry Detection (Ethernet

Default value: Enabled Port Attribute) parameter
specifies whether to identify the
tag labels in the data packets.
You can click 7.18 Entry
Detection (Ethernet Port
Attribute) to display the detailed
information.

System
4.11.6 Encapsulation/Mapping
The equipment supports the setting of encapsulation and mapping protocols for Ethernet packets,
including the parameters such as mapping protocol, scrambling code, and CRC or not.
Table 4-41 lists the parameters that are used for configuring the encapsulation and mapping of
an Ethernet port.
Table 4-41 Parameters for configuring the encapsulation and mapping of an Ethernet port
Port VCTRUNKn Indicates the VCTRUNK

port. The letter n indicates the
number of the VCTRUNK
port.
Mapping Protocol GFP, LAPS, HDLC The Mapping Protocol

Default value: GFP parameter specifies the
mapping protocol of the
VCTRUNK port.
You can click 7.20 Mapping
Protocol to display the
Scramble Unscrambled, Scrambling The Scramble parameter

mode[X43+1], Scrambling specifies whether to scramble
mode[X48+1] the payload area of the
Default value: Scrambling encapsulation protocol and
mode[X43+1] the scramble mode.
You can set this parameter
NOTE
The OptiX OSN 550 does not
only when the mapping
support Scramble mode[X48 protocol is GFP, HDLC, or
+1]. LAPS.
You can click 7.21
Scramble to display the
Set Inverse Value for CRC Yes, No The Set Inverse Value for
Default value: Yes CRC parameter specifies
whether to set an inverse
value for the CRC field of the
HDLC or LAPS protocol.
You can set this parameter
only when the mapping
protocol is HDLC or LAPS.
You can click 7.22 Set
Inverse Value for CRC to
information.

System
Check Field Length The value ranges of the The Check Field Length
parameters are different from parameter specifies the length
each other for different of the CRC field of the
boards and products. You can mapping protocol.
click the hyperlink in the You can set this parameter
description to display the only when the mapping
specific information. protocol is GFP, HDLC, or
LAPS.
You can click 7.23 Check
Field Length to display the
FCS Calculated Bit The value ranges of the The FCS Calculated Bit
Sequence parameters are different from Sequence parameter
each other for different specifies the sequence of
boards and products. You can storing the bits in the CRC
click the hyperlink in the field of the mapping protocol.
description to display the You can set this parameter
specific information. only when the mapping
protocol is GFP, HDLC, or
LAPS.
You can click 7.24 FCS
Calculated Bit Sequence to
information.
4.11.7 Bound Path

This topic describes the parameters, such as available resources, available timeslots, and service
direction, which are used for binding a path with an Ethernet port.
Table 4-42 lists the parameters that are used for binding a path.
Table 4-42 Parameters for bound path
Configurable Ports For example: VCTRUNKn Displays all the available

VCTRUNK ports on the
board.
Available Resources For example: VC4-1 Displays all the available

VC-4s.
Available Timeslots For example: VC12-1 Displays all the available

timeslots.
VCTRUNK Port VCTRUNKn Displays the number (n) of

the VCTRUNK port.

System
Level For example: VC12-xv Specifies the level of a path

that is bound with the
VCTRUNK.
Service Direction Bidirectional, Uplink, Specifies the direction of the

Downlink Ethernet service.
Default value: Bidirectional
Bound Path For example: VC4-1-VC12 Specifies the number of the

(1-3) path to be bound.
Bound Path Count For example: 3 Displays the number of

VCTRUNKs to be bound.
Used Channel For example: Uplink:VC4-3- Displays the actually used

VC3(1-3):3 channel.
Downlink:VC4-3-VC3(1-3):
3
Activation Status Active, Deactive Displays whether the path is

active.
Display in Combination - If you select Display in

Combination, the bound
paths are displayed in a
centralized manner.
Otherwise, the bound paths
are displayed in a distributed
manner.
4.12 Ethernet Service Configuration Parameters

Ethernet services can be classified into Ethernet private line services and Ethernet private
network services. Ethernet private line services include EPL services and EVPL services.
Ethernet private network services include EPLAN services and EVPLAN services.
4.12.1 Configuring Ethernet Private Line Services

This topic describes the parameters, such as operation type, service type, and encapsulation
format of the P port, that are used for configuring Ethernet private line services.
4.12.2 Configuring Ethernet Private Network Services
This section describes the parameters for configuring Ethernet private network services.
4.12.1 Configuring Ethernet Private Line Services

This topic describes the parameters, such as operation type, service type, and encapsulation
format of the P port, that are used for configuring Ethernet private line services.
Table 4-43 lists the parameters that are used for configuring Ethernet private line services.

System
Table 4-43 Parameters for configuring Ethernet private line services

Board For example: NE501-5-EFS8 Displays the name

of the board.
Service Type The value ranges of the parameters are The Service Type
different from each other for different (EPL Service)
boards and products. You can click the parameter specifies
hyperlink in the description to display the Ethernet private
the specific information. line service type.
You can click 7.26
Service Type (EPL
Service) to display
the detailed
information.
Service Direction Bidirectional, Unidirectional Specifies the

Default value: Bidirectional transmission
direction of the
service.
A bidirectional
service refers to the
two services that are
transmitted from
the source port to
the sink port and
from the sink port to
the source port. A
unidirectional
service refers to the
service that is
transmitted from
the source port to
the sink port.
Source Port PORTn, RPRn Specifies the name

For example: PORT3 of the source port.

System
Source C-VLAN Empty, 1-4095 The C-VLAN and

Default value: Empty S-VLAN parameter
specifies the two
types of VLAN tags
defined in the QinQ
service and IEEE
802.1ad. C-VLAN
is taken as the client
VLAN tag. S-
VLAN is taken as
the service VLAN
tag. C-VLAN Tag
(C-TAG) indicates
the VLAN tag on
the client side, and
S-VLAN Tag (S-
TAG) indicates the
VLAN tag at the
service layer of the
carrier.
This parameter is
applicable to the
QinQ services.
You can click 7.28
C-VLAN and S-
VLAN to display
the detailed
information.

System
Source S-VLAN Empty, 1-4095 The C-VLAN and

specifies the two
types of VLAN tags
defined in the QinQ
service and IEEE
802.1ad. C-VLAN
VLAN tag. S-
VLAN is taken as
the service VLAN
tag. C-VLAN Tag
(C-TAG) indicates
the VLAN tag on
S-VLAN Tag (S-
TAG) indicates the
VLAN tag at the
carrier.
This parameter is
applicable to the
QinQ services.
You can click 7.28
C-VLAN and S-
VLAN to display
the detailed
information.
Sink Port PORTn, RPRn Specifies the name

For example: PORT3 of the sink port.

System
Sink C-VLAN Empty, 1-4095 The C-VLAN and

specifies the two
types of VLAN tags
defined in the QinQ
service and IEEE
802.1ad. C-VLAN
VLAN tag. S-
VLAN is taken as
the service VLAN
tag. C-VLAN Tag
(C-TAG) indicates
the VLAN tag on
S-VLAN Tag (S-
TAG) indicates the
VLAN tag at the
carrier.
This parameter is
applicable to the
QinQ services.
You can click 7.28
C-VLAN and S-
VLAN to display
the detailed
information.

System
Sink S-VLAN Empty, 1-4095 The C-VLAN and

specifies the two
types of VLAN tags
defined in the QinQ
service and IEEE
802.1ad. C-VLAN
VLAN tag. S-
VLAN is taken as
the service VLAN
tag. C-VLAN Tag
(C-TAG) indicates
the VLAN tag on
S-VLAN Tag (S-
TAG) indicates the
VLAN tag at the
carrier.
This parameter is
applicable to the
QinQ services.
You can click 7.28
C-VLAN and S-
VLAN to display
the detailed
information.
Activation Status Active, Inactive Displays the service

status.
Operation Type The value ranges of the parameters are The Operation
different from each other for different Type (EPL
boards and products. You can click the Service) parameter
hyperlink in the description to display specifies whether to
the specific information. add, strip, translate
or transparently
transmit VLAN
labels for service
packets at a port
when Service
Type is set to
EVPL(QinQ).
You can click 7.25
Operation Type
(EPL Service) to
information.

System
Port For example: PORT3, VCTRUNK1 Displays the port

name.

System
Port Type l If a board supports the MPLS Specifies the

function, its port type can be set to network attribute of
PE or P. Default value: PE. a port.
l If a board supports the QinQ A provider edge
function, its port type can be set to (PE) port refers to
UNI, C-Aware, or S-Aware. the edge port that is
Default value: UNI. provided by the
service provider. A
PE port can transmit
and receive
standard Ethernet
frames, because its
default MPLS
encapsulation type
is invalid.
A provider (P) port
refers to the port on
the core network of
the service
provider. A P port
can transmit and
receive the packets
that contain MPLS
labels, because its
default tag attribute
is invalid.
If a port is in UNI
mode and processes
802.1Q tag
attribute, this port
has the Tag Aware,
Access, and Hybrid
attributes.
If a port is in C-
Aware mode, this
port does not
process the packets
with 802.1Q tag
attributes. In this
case, this port
considers that the
accessed packets
contain C-VLAN
tags rather than S-
VLAN tags.
If a port is in S-
Aware mode, this
port does not

System
process the packets

with 802.1Q tag
attributes. In this
case, this port
considers that the
accessed packets
contain S-VLAN
tags rather than C-
VLAN tags.
Port Enabled Enabled, Disabled Indicates whether a

Default value: Disabled port is enabled.
Enabled: The port
can access services.
Disabled: The port
cannot access
services.

System
TAG Tag Aware, Access, Hybrid Specifies the type of

Default value: Tag Aware a packet to be
processed. If you set
this parameter to be
a Tag Aware port,
the port processes
only the packets
that contain tags
and discards the
packets that do not
contain tags. If you
set this parameter to
be an Access port,
the port processes
only the packets
that do not contain
tags and discards
the packets that
contain tags. If you
set this parameter to
be a Hybrid port, the
port processes all
the packets
regardless of tags
and adds tags to the
received packets
that do not contain
tags according to
the VLAN ID of the
local port.
You can click 7.19
TAG to display the
detailed
information.
VCTRUNK Port For example: VCTRUNK1 Displays the name

of the VCTRUNK.
Level VC12-xv, VC3-xv Specifies the level

of a path that is
bound with the
VCTRUNK.
Service Direction Bidirectional, Uplink, Downlink Indicates the

Default value: Bidirectional direction of the
Ethernet service.

System
Bound Path For example: VC4-4-VC12(1-2,4) Specifies the

number of a path to
be bound, including
the numbers of the
VC-4, VC-12 or
VC-3, and GE
paths.
Bound Path Count For example: 3 Displays the

number of bound
paths.
4.12.2 Configuring Ethernet Private Network Services

This section describes the parameters for configuring Ethernet private network services.
Table 4-44 lists the parameters that are used for configuring Ethernet private network services.
Table 4-44 Parameters for configuring Ethernet private network services

Board NE Name-Slot ID-Board Displays the name of the board.

Name
For example: NE(9-1)-4-
EFS8
VB ID For example: 1 The VB ID is allocated automatically

when you create a LAN service.
VB Name Contains up to 16 Specifies the name of the VB.

characters or numerals in
English or eight
characters in Chinese.
For example: VB1
Bridge Type 802.1q, 802.1d, 802.1ad Specifies the type of the VB.
Default value: 802.1q
Bridge Switch Mode IVL/Ingress Filter Specifies the switching mode of the VB.
Enable, SVL/Ingress
Filter Disable
Default value: IVL/
Ingress Filter Enable

System
Bridge Learning IVL, SVL Bridge Learning Mode (Ethernet LAN

Mode Default value: IVL (The Service) indicates how the bridge learns
bridge type is compliant the MAC address. Bridge Learning
with IEEE 802.1q or Mode is classified into the shared VLAN
IEEE 802.1ad), SVL learning and independent VLAN
(The bridge type is learning modes. The shared VLAN
compliant with learning mode indicates learning and
IEEE802.1d or IEEE forwarding based on the MAC address.
802.1ad) The independent VLAN learning mode
indicates learning and forwarding based
on the VLAN and MAC address.
You can click 7.30 Bridge Learning
Mode (Ethernet LAN Service) to
Displays the detailed information.
Ingress Filter Enabled Displays the status of the ingress filter

Default value: Enabled function.
Enabled: The ingress port checks the
validity of VLAN IDs based on the VB.
If the packets received on the ingress port
do not belong to the VLAN of the VB
port, these packets are discarded.
MAC Address Self- Enabled Indicates whether the MAC address

Larning Default value: Disabled learning function is enabled.
Enabled: MAC addresses can be learnt.
Active Active Displays the activation status of the VB.
Table 4-45 Parameters for configuring service mount

VB Port For example: 1 Displays the VB port.

Allocated automatically when the VB
mount port is configured.
Mount Port For example: PORT1 Displays the mount port. The mount
port may be the PORT port or VC
trunk port.
Port Type For example: UNI Displays the network attributes for a
port.
Value Range: UNI, C-Aware, S-
Aware. Default value: UNI

System
Encapsulation MartinioE, stack VLAN Displays the encapsulation format for

Format a port of the P type.
NOTE
The OptiX OSN 550 does not support this
parameter.
Port Enabled Enabled, Disabled Enables or disables a port.

l Enabled: This port can access
services.
l Disabled: This port cannot access
services.
Hub/Spoke Hub, Spoke Hub/Spoke (Ethernet LAN Service)

Default value: Hub is used to separate packets between
the logical ports in the network
bridge.
In the same VB VLAN filter or plain
bridge:
l Communication is available
between ports configured with
Hub.
l Communication is available
between a port configured with
Spoke and a port configured with
Hub.
l Communication is unavailable
between ports both configured
with Spoke.
Set this parameter according to the
isolation domain range of the user.
TAG Access, Tag Aware, Hybrid Displays the tag attribute of the VB.
Default VLAN ID For example: 1 Displays the VLAN ID.
Working Mode Auto-Negotiation, 10M Displays the working modes of the

Half-Duplex, 10M Full- Ethernet port. Auto-Negotiation can
Duplex, 100M Half-Duplex, automatically determine the
100M Full-Duplex, 1000M optimized working modes of the
Half-Duplex, 1000M Full- connected ports. This mode is easy to
Duplex, 10G Full-Duplex maintain and is recommended.
LAN, 10G Full-Duplex During configuration, make sure that
WAN working modes of the connected ports
NOTE are consistent. If the working modes
l The EFS8 board supports are different, the services are down.
Auto-Negotiation, and
100M Full-Duplex.
Active For example: Active Displays the activation status.

System
Service Direction For example: Bidirectional Displays the working modes of the
Ethernet port.
C-VLAN 1 to 4095 Displays the C-VLAN value.
S-VLAN 1 to 4095 Displays the S-VLAN value.
C-VLAN Priority - Displays the priority of C-VLAN.
S-VLAN Priority - Displays the priority of S-VLAN.
Table 4-46 Parameters for configuring VLAN filtering

VLAN ID 1 to 4095 Displays the VLAN ID and

configures the forwarding filter table.
VB Port For example: (1,3-4) Allocated automatically when the VB

Forwarding Physical For example: PORT1, Displays the physical port that is
Port VCTRUNK(5,8) actually attached to the VB link.
Activation Status For example: Active Activation Status (Ethernet LAN

Service) indicates that the service at
the port is in activation status.
Table 4-47 Parameters for configuring VLAN unicast

VLAN ID 1 to 4095 Only the VLAN ID specified in the

forwarding filter table can be
selected.
MAC Address 00-00-00-00-00-01 to FE- Displays the MAC address of VLAN

FF-FF-FF-FF-FF unicast.
VB Port For example: 1 Allocated automatically when the VB

Physical Port For example: PORT1 Displays the name of the port.
Aging Status For example: Static Displays the aging status of unicast
items, including static and dynamic.

System
Table 4-48 Parameters for configuring disable MAC address

VLAN ID 1 to 4095 Inhibits a MAC address in the VLAN

of a certain VB.
MAC Address 00-00-00-00-00-01 to FE- Enters a MAC address that is to be

FF-FF-FF-FF-FF inhibited. Hence, enters a MAC
address that is not associated to the
VLAN unicast of this VLAN.
Table 4-49 Parameters for bound path

Configurable Ports For example: VCTRUNKn Displays all the available

VCTRUNK ports on the
board.
Available Resources For example: VC4-1 Displays all the available

VC-4s.
Available Timeslots For example: VC12-1 Displays all the available

timeslots.
VCTRUNK Port VCTRUNKn Displays the number (n) of

the VCTRUNK port.
Level For example: VC12-xv Specifies the level of a path

that is bound with the
VCTRUNK.
Service Direction Bidirectional, Uplink, Specifies the direction of the

Downlink Ethernet service.
Default value: Bidirectional
Bound Path For example: VC4-1-VC12 Specifies the number of the

(1-3) path to be bound, for
example, VC4-1-VC12(1-3).
Bound Path Count For example: 3 Displays the number of

VCTRUNKs to be bound.
Activation Status Active, Deactive Displays whether the path is

active.
Display in Combination - If you select Display in

Combination, the bound
paths are displayed in a
centralized manner.
Otherwise, the bound paths
are displayed in a distributed
manner.

System

System
Configuration Guide 5 Modifying the Configuration Data
5 Modifying the Configuration Data
About This Chapter
You can modify the existing configuration data related to the topology and services.
5.1 Changing the Values of NE Attributes

You can change the values of the NE attributes.
5.2 Modifying the Board Configuration Data
You can modify the existing board configuration data.
5.3 Modifying the Fiber Configuration Data
You can modify the existing fiber configuration data.
5.4 Modifying the Service Configuration Data
You can modify the existing service configuration data according to the requirements.
5.5 Modifying the Protection Subnet
This topic describes how to modify the configuration data of the existing protection subnet.

System
5 Modifying the Configuration Data Configuration Guide
5.1 Changing the Values of NE Attributes

You can change the values of the NE attributes.
5.1.1 Changing the NE ID

The ECC protocol uses the NE ID as the unique identifier of an NE. You need to assign a unique
NE ID to each NE when planning a network. If an NE ID is the same as another NE ID, certain
ECC routes conflict with each other. As a result, the U2000 fail to manage certain NEs. You can
use the U2000 to change the NE ID when the original network planning needs to be modified
during the system commissioning or expansion.
5.1.2 Changing the NE Name
You can change the NE name according to the requirements. Changing the NE name does not
affect the operation of the NE.
5.1.3 Deleting an NE
If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes
all the information about the NE from the U2000 but does not affect the operation of the
equipment.
5.1.4 Changing the Parameter Values of the Gateway NE
During the network optimization and adjustment, you may need to change the type of the gateway
NE or modify the communication address of the gateway NE.
5.1.5 Changing the Gateway NE of a Non-Gateway NE
When changes occur on the only gateway NE to which a non-gateway NE belongs, you need to
assign this non-gateway NE to belong to another gateway NE. Otherwise, the communication
between this NE and the U2000 fails. If a gateway NE manages more than 50 NEs, it is
recommended that you assign certain NEs to belong to other gateway NEs to prevent the
communication between the U2000 and the NEs from being affected.
5.1.1 Changing the NE ID

The ECC protocol uses the NE ID as the unique identifier of an NE. You need to assign a unique
NE ID to each NE when planning a network. If an NE ID is the same as another NE ID, certain
ECC routes conflict with each other. As a result, the U2000 fail to manage certain NEs. You can
use the U2000 to change the NE ID when the original network planning needs to be modified
during the system commissioning or expansion.
Prerequisite
l The NE must be created.
Precautions
CAUTION
Changing the NE ID may interrupt the NE communication.

System
Procedure
Step 1 In the NE Explorer, select an NE and then choose Configuration > NE Attribute from the
Function Tree.
Step 2 Click Modify NE ID. Then, the Modify NE ID dialog box is displayed.
Step 3 Enter New ID and New Extended ID. Then, click OK.
Step 4 Click OK in the Warning dialog box that is displayed.
----End
5.1.2 Changing the NE Name

You can change the NE name according to the requirements. Changing the NE name does not
affect the operation of the NE.
Prerequisite
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 In NE Attribute list, enter a new NE name in Name. Click Apply. Then, a dialog box is
displayed, indicating that the operation is successful.
NOTE
An NE name can contain a maximum of 64 letters, symbols, and numerals, but cannot contain the following
special characters: | : * ? " < >.
Step 3 Click Close.
----End
5.1.3 Deleting an NE
If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes
all the information about the NE from the U2000 but does not affect the operation of the
equipment.
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
Precautions
CAUTION
If an NE is deleted, the links related to the NE are also deleted.

System
Procedure
l Delete a single NE.
1. Right-click the NE on the Main Topology and choose Delete from the shortcut menu.
The Confirm dialog box is displayed.
2. Click Yes. The Deletion Result dialog box is displayed.
3. Click Close, The NE icon is deleted from the Main Topology.
l Delete NEs in batches.
1. Choose Configuration > NE Configuration Data Management from the Main
Menu. Then, the NE Configuration Data Management window is displayed.
2. In the pane on the left, select multiple NEs and click . Then, the
Configuration Data Management List pane displays the configuration data of all
the selected NEs.
3. Right-click the NEs to be deleted and then choose Delete from the shortcut menu. The
Delete the NE dialog box is displayed.
4. Click OK to delete the selected NEs.
----End
5.1.4 Changing the Parameter Values of the Gateway NE

During the network optimization and adjustment, you may need to change the type of the gateway
NE or modify the communication address of the gateway NE.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Precautions
CAUTION
Changing the parameter values of the gateway NE may interrupt the communication.
Procedure
Step 1 Choose Administration > DCN Management from the Main Menu.
Step 2 In the Filter NE window that is displayed, choose the NEs. Click OK.
Step 3 Click the GNE tab. Select the gateway NE whose parameter values need to be changed. Right-
click and choose Modify GNE from the shortcut menu.
Step 4 In the Modify GNE dialog box that is displayed, set Gateway Type.
l When Gateway Type is set to IP Gateway, change IP Address.

System
l When Gateway Type is set to OSI Gateway, change NSAP Address.
NOTE
l It is recommended that you do not change Port No..

l Ensure that the IP address of the gateway NE is in the same network segment as the IP address of the
U2000. If they are not in the same network segment, set the corresponding network ports so that the
U2000 can log in to the gateway NE.
Step 5 Click OK. Then, click Close in the Operation Result dialog box indicating that the operation
succeeded.
----End
5.1.5 Changing the Gateway NE of a Non-Gateway NE

When changes occur on the only gateway NE to which a non-gateway NE belongs, you need to
assign this non-gateway NE to belong to another gateway NE. Otherwise, the communication
between this NE and the U2000 fails. If a gateway NE manages more than 50 NEs, it is
recommended that you assign certain NEs to belong to other gateway NEs to prevent the
communication between the U2000 and the NEs from being affected.
Procedure
Step 1 Choose Administration > DCN Management from the Main Menu.
Step 2 Click the NE tab.

System
Step 3 Double-click the Primary GNE1 field and select a gateway NE from the drop-down list.
succeeded.
Step 5 Click Refresh.
----End
5.2 Modifying the Board Configuration Data

5.2.1 Adding Boards

When manually configuring the NE data, you need to add the boards to the NE panel. You can
add the physical boards that actually operate on the NE or the logical boards that do not exist
on the NE to the NE panel.
5.2.2 Deleting Boards
To modify the network configuration or the NE configuration, you need to delete the boards
from the NE panel.
5.2.3 Modifying Board Configuration Parameters
5.2.1 Adding Boards

When manually configuring the NE data, you need to add the boards to the NE panel. You can
add the physical boards that actually operate on the NE or the logical boards that do not exist
on the NE to the NE panel.
Prerequisite
l The NE must be created.
l There must be idle slots on the NE panel.
l The physical boards are the actual boards inserted in the subrack. The logical boards are
created on the U2000 and are saved on the SCB board, but they do not exist on the actual
equipment.
l The NE panel shows the mapping relations between the slots that house the processing
boards and the slots that house the interface boards. If you click a processing board that is
paired with an interface board on the NE panel, the ID of the slot that houses the mapping
interface board is displayed in orange.
Procedure
Step 1 Double-click the icon of the NE to open the NE panel.
Step 2 Right-click the selected idle slot. Select the board you need to add from the drop-down list.

System
NOTE
If the physical cross-connect board is installed in the subrack, add its corresponding logical board on the
U2000.
----End
5.2.2 Deleting Boards

To modify the network configuration or the NE configuration, you need to delete the boards
from the NE panel.
Prerequisite
l The services and protection groups must be deleted.
Procedure
Step 1 Double-click the icon of the NE to display the NE Panel.
Step 2 Right-click the board you need to delete and choose Delete from the shortcut menu.
Step 3 Click OK in the Delete Board dialog boxes that are displayed sequentially.
----End
5.2.3 Modifying Board Configuration Parameters

Prerequisite
To change the values of different configuration parameters of different boards, you may need
to operate as NM users with different authorities. You must be an NM user with "NE operator"
authority or higher.
Procedure
Step 1 In the NE Explorer, select a board and choose the appropriate function entry from the Function
Tree.
Board Type Parameter
SDH board Laser Switch, Optical(Electrical) Interface

Loopback, VC4 Loopback
PDH board Tributary Loopback, Service Load

Indication, Re-timing Mode
Step 2 In the pane on the right, modify the existing parameter settings and click Apply.
----End

System
5.3 Modifying the Fiber Configuration Data

You can modify the existing fiber configuration data.
5.3.1 Deleting Fibers

If you need to delete an NE or change the links between NEs during network adjustment, delete
the related fiber connections between the NEs.
5.3.2 Changing Fiber/Cable Information
You can change the name, attenuation, length, and type of a fiber/cable according to its
connection status and physical features.
5.3.3 Deleting DCN Communication Cables
In certain scenarios such as network adjustment, you can delete the DCN communication cable
that is not applicable.
5.3.1 Deleting Fibers

If you need to delete an NE or change the links between NEs during network adjustment, delete
the related fiber connections between the NEs.
Prerequisite
Procedure
Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the Main Menu.
Step 2 Right-click the fiber you need to delete and then choose Delete Fiber/Cable from the shortcut
menu. Then, the Warning dialog box is displayed. Click OK to delete the fiber.
Step 3 Click Close in the Operation Result dialog box indicating that the operation succeeded.
----End
5.3.2 Changing Fiber/Cable Information

You can change the name, attenuation, length, and type of a fiber/cable according to its
connection status and physical features.
Prerequisite
Procedure
Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the Main Menu. All the
fiber information is displayed in the right pane.
Step 2 Select a fiber, right-click and choose Modify Fiber/Cable from the shortcut menu. In the Modify
Fiber/Cable dialog box, you can modify Name, Length(km), Attenuation, Medium Type,

System
Maintainer, Remarks, and Disabled Status. Click OK. Then, click Close in the Operation
Result dialog box indicating that the operation succeeded.
----End
5.3.3 Deleting DCN Communication Cables

In certain scenarios such as network adjustment, you can delete the DCN communication cable
that is not applicable.
Prerequisite
Procedure
Step 1 On the Main Topology, right-click the cable and choose Delete from the shortcut menu.
Step 2 Click Yes in the Confirm dialog box that is displayed.
----End
5.4 Modifying the Service Configuration Data

You can modify the existing service configuration data according to the requirements.
5.4.1 Modifying SDH Services

To modify an SDH service, you can use the modification function of the U2000, or delete the
service and then create the cross-connection again.
5.4.2 Deleting SDH Services
You can delete an existing SDH service.
5.4.3 Deleting Ethernet Private Line Services
Ethernet private line services need to be deleted when the Ethernet boards that are configured
with the Ethernet private line services need to be deleted or when the service configuration is
incorrect.
5.4.4 Deleting EPLAN Services
EPLAN services need to be deleted when the Ethernet boards that are configured with the
EPLAN services need to be deleted or when the configuration of the EPLAN services is incorrect.
5.4.5 Deleting EVPLAN Services
EVPLAN services need to be deleted when the Ethernet boards that are configured with the
EVPLAN services need to be deleted or when the configuration of the EVPLAN services is
incorrect.
5.4.1 Modifying SDH Services

To modify an SDH service, you can use the modification function of the U2000, or delete the
service and then create the cross-connection again.
Prerequisite

System
Precautions
CAUTION
Performing this operation interrupts the service that you modify.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > SDH Service Configuration
from the Function Tree.
Step 2 Select a cross-connection and choose Display > Expand to Unidirectional.
Step 3 If the service to be modified is active, you should deactivate the service. Select the service that
you need to modify and then click Deactivate.
CAUTION
Deactivation interrupts the services.
Step 4 Click OK in the Confirm dialog box that is displayed third. The Operation Result dialog box
is displayed, indicating that the operation is successful.
Step 5 Click Close.
Step 6 After the cross-connection is deactivated, modify the SDH service by using the method described
in Step Step 7 or Step 8.
NOTE
l By using the method described in Step Step 7, you can modify the source or sink of a service. Ensure
that the service source and sink are located on the same board before and after the modification.
l If the modification requirement cannot be met by using the method described in Step Step 7 (for
example, a pass-through service needs to be configured to the local equipment through modification),
you can delete the original service and create the cross-connection again by using the method described
in Step Step 8.
Step 7 Optional: To modify the SDH service, choose Modify from the shortcut menu.
1. Right-click the service that you need to modify and choose Modify from the shortcut menu.
Then, the Modify SDH Service dialog box is displayed.
2. Change Source VC4 or Sink VC4, Source Timeslot Range, and Sink Timeslot Range.
NOTE
By using this method, you can change only Source VC4 or Sink VC4. The source VC-4 and sink
VC-4 cannot be modified at the same time.
3. Click OK. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful.
4. Click Close.
5. Select the service that is modified and click Activate.

System
7. Click Close.
Step 8 Optional: To modify the SDH service, delete the service and then create the service again.
1. Select the service that you need to modify and click Delete.
3. Click Close. The service is deleted.
4. Create the service again according to the requirements. For details, see Creating SDH
Services.
----End
5.4.2 Deleting SDH Services

You can delete an existing SDH service.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > SDH Service Configuration
from the Function Tree.
Step 2 Click Query to query the existing services.
Step 3 If the service to be deleted is active, you should deactivate the service first. Select the service
that you need to delete and click Deactivate.
CAUTION
Deactivation interrupts the services.
Step 4 Select the service to be deleted and click Delete.
Step 5 Click OK in the Confirm dialog box that is displayed.
Step 6 Click Close in the Operation Result dialog box indicating that the operation succeeded.
----End
5.4.3 Deleting Ethernet Private Line Services

Ethernet private line services need to be deleted when the Ethernet boards that are configured
with the Ethernet private line services need to be deleted or when the service configuration is
incorrect.

System
Prerequisite
Procedure
Step 1 In the NE Explorer, select an Ethernet board and then choose Configuration > Ethernet
Step 2 Click Query.
Step 3 Select the Ethernet private line service to be deleted and click Delete. Click OK in the
Prompt dialog box that is displayed. Then, a dialog box is displayed, indicating that the operation
is successful, that is, the Ethernet private line service is deleted successfully.
Step 4 Click Query to check whether the Ethernet private line service is deleted.
Step 5 See 5.4.2 Deleting SDH Services to delete the cross-connections of the Ethernet private line
service.
----End
5.4.4 Deleting EPLAN Services

EPLAN services need to be deleted when the Ethernet boards that are configured with the
EPLAN services need to be deleted or when the configuration of the EPLAN services is incorrect.
Prerequisite
Context
CAUTION
When the EPLAN services are deleted, the VLAN unicast entries and disabled MAC address
entries are deleted.
Procedure
Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet
Step 2 Click Query.
Step 3 Select the EPLAN service to be deleted and click Delete. Click OK in the Prompt dialog box
that is displayed. Then, a dialog box is displayed, indicating that the operation is successful, that
is, the EPLAN service is deleted successfully.
Step 4 Click Query to check whether the EPLAN service is deleted.
Step 5 See 5.4.2 Deleting SDH Services to delete the cross-connections of the EPLAN service.
----End

System
5.4.5 Deleting EVPLAN Services

EVPLAN services need to be deleted when the Ethernet boards that are configured with the
EVPLAN services need to be deleted or when the configuration of the EVPLAN services is
incorrect.
Prerequisite
Deleting an EVPLAN service involves the following:
1. Deleting the VLAN filtering table
2. Deleting the service mounting configurations
Context
CAUTION
When the VLAN filtering table is deleted, the VLAN unicast entries and disabled MAC address
entries are deleted.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and then choose Configuration > Ethernet
Step 2 Click Query.
Step 3 Click the VLAN Filtering tab.
Step 4 Select the VLAN filtering entry to be deleted and click Delete.
Step 5 Click the Service Mount tab.
Step 6 Select the EVPLAN service to be deleted and click Delete. Click OK in the Prompt dialog box
that is displayed. Then, a dialog box is displayed, indicating that the operation is successful, that
is, the EVPLAN service is deleted successfully.
Step 7 Click Query to check whether the EVPLAN service is deleted.
Step 8 See 5.4.2 Deleting SDH Services to delete the cross-connections of the EVPLAN service.
----End
5.5 Modifying the Protection Subnet

This topic describes how to modify the configuration data of the existing protection subnet.
5.5.1 Deleting Protection Subnets

System
Before you delete an NE or a fiber/cable connection on the U2000, you need to delete the related
protection subnets.
5.5.2 Changing the Values of Protection Subnet Parameters
In the case of the SDH equipment, you can set the parameters of the MSP protection subnet by
using the protection subnet maintenance function.
5.5.1 Deleting Protection Subnets

Before you delete an NE or a fiber/cable connection on the U2000, you need to delete the related
protection subnets.
Prerequisite
l If trails are configured on the protection subnet that you need to delete, delete the trails
first.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnet from the Main
Menu.
Step 2 Right-click the protection subnet to be deleted and choose Delete from the NM, Delete from
the NE, or Delete All from the NM from the short-cut menu.
NOTE
The methods of deleting a protection subnet are as follows:

l Delete from the NM: If Delete from the NM is selected, the relations between the protection subnet and
each logical system on the NE side are deleted so that the fibers can be deleted and reloading can be
performed. This command is not delivered to the NE and does not affect the services. The deleted protection
subnet can be located by using the search feature. The U2000 locates it according to the NE layer protection
information.
l Delete from the NE: If Delete from the NE is selected, the protection subnet, logical systems on the NE
side, and all the services on the protection subnet are deleted. The deleted protection subnet cannot be restored
and needs to be created again.
l Delete All from the NM: If Delete All from the NM is selected, the data of the protection subnet except
the fibers at the network layer is deleted. The deleted protection subnet can be located by using the search
feature. It is recommended that you do not select this option, because a large amount of data is deleted.
Step 3 Click Yes in the Operation Prompt dialog box indicating that the operation succeeded. Then,
the Operation Result dialog box is displayed.
NOTE
If Delete from the NE is selected, you need to confirm the operation again.
Step 4 Click Close.
----End
5.5.2 Changing the Values of Protection Subnet Parameters

In the case of the SDH equipment, you can set the parameters of the MSP protection subnet by
using the protection subnet maintenance function.

System
Prerequisite
l The data of each NE must be configured and the fibers must be created on the U2000.
l The MSP protection subnet must be configured.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the Main
Menu. Then, the SDH Protection Subnet Common Attributes dialog box is displayed.
Step 2 Select an MSP protection subnet from the pane on the left. The attribute information of the
protection subnet is displayed in the pane on the right.
Step 3 Click the Protection Subnet Parameters tab.
Step 4 Click Query to query the parameters of the protection subnet on the MSP ring.
Step 5 Click the WTR Time(s) text box and enter a value.
NOTE
The default WTR time is 600s. You can also set the WTR time to a value from 300s to 720s.
Step 6 Optional: Select SD Condition.

succeeded.
----End

System
Configuration Guide 6 Equipment Information
6 Equipment Information
About This Chapter
You need to consider the service support capability of the boards used by the equipment and the
configuration requirements during the configuration process.
6.1 Service Support Capability of Ethernet Boards

Ethernet boards are classified into Ethernet transparent transmission boards and Ethernet
switching boards, based on the type of the accessed service. The Ethernet transparent
transmission boards support only EPL services, whereas the Ethernet switching boards support
EPL services, EVPL services, and Layer 2 switching function.
6.2 Requirements for Binding Paths with VCTRUNKs on Ethernet Boards
One VCTRUNK on an Ethernet board can only be bound with timeslots of the same level.
6.3 Ethernet Service Bandwidths Carried by VCTRUNKs of Ethernet Boards
To determine the level of the bandwidths to be bound with a VCTRUNK and the number of
paths that are required for an Ethernet service, you need to calculate the theoretical bandwidth
of the Ethernet service that can be carried by a VCTRUNK.

System
6 Equipment Information Configuration Guide
6.1 Service Support Capability of Ethernet Boards

Ethernet boards are classified into Ethernet transparent transmission boards and Ethernet
switching boards, based on the type of the accessed service. The Ethernet transparent
transmission boards support only EPL services, whereas the Ethernet switching boards support
EPL services, EVPL services, and Layer 2 switching function.
Table 6-1 Service support capability of Ethernet boards

Board Type Board Supported EPL Service Supported EPLAN Service
Name
Ethernet EGT1 EPL -

transparent
transmission board
Ethernet switching EFS8 EPL EVPLAN (IEEE 802.1q bridge), EPLAN

board EVPL (IEEE 802.1d bridge), and EVPLAN (IEEE
802.1ad bridge)
6.2 Requirements for Binding Paths with VCTRUNKs on

Ethernet Boards
One VCTRUNK on an Ethernet board can only be bound with timeslots of the same level.
Table 6-2 Requirements for binding paths with VCTRUNKs on Ethernet boards
Board Requirement for Binding Paths with a VCTRUNK
EGT1 l The VCTRUNKs can be bound with the VC-12 VC-3 and VC-4 paths.
l Only one VCTRUNK with a maximum bandwidth of 1.25 Gbit/s is supported.
l VCTRUNK1 can only be bound with the fourth VC-4, namely, VC4-4, if the path binding
is at VC-12 level.
l VCTRUNK1 can be bound with the first to eighth VC-4s, namely, VC4-1 to VC4-8, if the
path binding is at VC-3 level.
EFS8 l The VCTRUNKs can be bound with the VC-12 paths and VC-3 paths.
l Eight VCTRUNKs are supported. The maximum bandwidth of each VCTRUNK is 100
Mbit/s.
l VCTRUNK1 to VCTRUNK8 can only be bound with the fourth VC-4, namely, VC4-4, if
the path binding is at VC-12 level.
l VCTRUNK1 to VCTRUNK8 can be bound with the first to fourth VC-4s, namely, VC4-1
to VC4-4, if the path binding is at VC-3 level.

System
Configuration Guide 6 Equipment Information
6.3 Ethernet Service Bandwidths Carried by VCTRUNKs of

Ethernet Boards
To determine the level of the bandwidths to be bound with a VCTRUNK and the number of
paths that are required for an Ethernet service, you need to calculate the theoretical bandwidth
of the Ethernet service that can be carried by a VCTRUNK.
Bandwidth = Number of paths bound with the VCTRUNK x Payload rate of the binding
granularity x Encapsulation efficiency of the encapsulation protocol
The payload rate of the VC-12 is 2.176 Mbit/s; the payload rate of the VC-3 is 48.384 Mbit/s;
the payload rate of the VC-3 is 149.760 Mbit/s.
GFP encapsulation efficiency has different values in the following two scenarios:
l GFP encapsulation efficiency = Ethernet frame length/(Ethernet frame length + 12-byte
overhead), when the GFP protocol uses FCS32 as the check field.
l GFP encapsulation efficiency = Ethernet frame length/(Ethernet frame length + 8-byte
overhead), when the GFP protocol does not add the check field.
NOTE
When the Ethernet board uses the GFP protocol to encapsulate Ethernet services, you can determine
whether a check field is used during the encapsulation by setting the Check Field Length parameter. By
default, FCS32 is used as the check field. In this case, if the Ethernet board uses the default GFP parameter
settings, the theoretical bandwidth of the VCTRUNK bound with five VC-12 paths is 10.938 Mbit/s when
the Ethernet frame length is 1500 bytes and the theoretical bandwidth of the VCTRUNK bound with five
VC-12 paths is 12.025 bit/s when the Ethernet frame length is 64 bytes.
In actual situations, you can estimate the level and quantity of the paths according to the
following principle: One VC-12 path carries 2 Mbit/s services; one VC-3 path carries 48 Mbit/
s services; one VC-4 path carries 150 Mbit/s services. For example, in the case of a 10 Mbit/s
Ethernet service, the VCTRUNKs can be bound with five VC-12 paths.

System
Configuration Guide 7 List of Parameters
7 List of Parameters
About This Chapter
This section describes all the parameters that are used for configuring and querying the common
boards and functions on the U2000. Each parameter is described in terms of the description,
impact on the system, values, configuration guidelines, and relationship with other parameters.
7.1 Port Attributes (Ethernet Port)

7.2 Maximum Frame Length (Ethernet Port Attribute)
7.3 Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute)
7.4 Autonegotiation Flow Control Mode (Ethernet Port Attribute)
7.5 MAC Loopback (Ethernet Port Attribute)
7.6 PHY Loopback (Ethernet Port Attribute)
7.7 QinQ Type Area
7.8 Loop Detection (Ethernet Port Attribute)
7.9 Loop Port Shutdown (Ethernet Port Attribute)
7.10 Traffic Threshold(Mbit/s)(External Ethernet Port Attribute)
7.11 Broadcast Packet Suppression Threshold (Ethernet Interface Attributes)
7.12 Broadcast Packet Suppression (Ethernet Interface Attributes)
7.13 Zero-Flow Monitor (Ethernet Interface Attributes)
7.14 Port Traffic Threshold Time Window(Min)
7.15 Jumbo Frame Type
7.16 Default VLAN ID (Ethernet Port Attribute)
7.17 VLAN Priority (Ethernet Port Attribute)
7.18 Entry Detection (Ethernet Port Attribute)
7.19 TAG

System
7 List of Parameters Configuration Guide
7.20 Mapping Protocol

7.21 Scramble
7.22 Set Inverse Value for CRC
7.23 Check Field Length
7.24 FCS Calculated Bit Sequence
7.25 Operation Type (EPL Service)
7.26 Service Type (EPL Service)
7.27 Encapsulation Format of P Port (Network Attributes)
7.28 C-VLAN and S-VLAN
7.29 VLAN ID (For Creation of Ethernet Virtual Private Lines)
7.30 Bridge Learning Mode (Ethernet LAN Service)
7.31 MEP ID (Ethernet OAM)
7.32 Maintenance Point Type (Ethernet OAM)
7.33 CC Status (Ethernet OAM)
7.34 Test Result (LB and LT Test)
7.35 Responding MP Type (Ethernet LT Test)
7.36 Hop Count (Ethernet LT Test)
7.37 Packet Length (Ping Test)
7.38 Timeout (Ping Test)
7.39 Detect Attempts
7.40 Send Direction (Ethernet Test)
7.41 Error Frame Monitor Window (ms)
7.42 Error Frame Monitor Threshold(Entries)
7.43 Error Frame Period Window(Frames)
7.44 Error Frame Monitor Threshold(Frames)
7.45 Error Frame Second Window (s)
7.46 Error Frame Second Threshold(s)
7.47 Enable OAM Protocol
7.48 OAM Working Mode
7.49 Remote Alarm Support for Link Event
7.50 Unidirectional Operation
7.51 Loopback Status (OAM Parameter)
7.52 Flow Type (Flow Configuration)

System
7.53 Bound CAR (Flow Configuration)

7.54 Bound CoS (Flow Configuration)
7.55 CAR ID (CAR Configuration)
7.56 Enabled/Disabled (CAR Configuration)
7.57 Committed Information Rate (kbit/s) (CAR Configuration)
7.58 Committed Burst Size (kbyte) (CAR Configuration)
7.59 Peak Information Rate (kbit/s) (CAR Configuration)
7.60 Maximum Burst Size (kbyte) (CAR Configuration)
7.61 CoS ID (CoS Configuration)
7.62 CoS Type (CoS Configuration)
7.63 CoS Priority (CoS Configuration)
7.64 Port Priority (Link Aggregation)
7.65 System Priority (Link Aggregation)
7.66 Status (Link Aggregation)
7.67 Load Sharing(Ethernet Link Aggregation)
7.68 Protocol Enabled (Spanning Tree)
7.69 Protocol Type (Spanning Tree Protocol)
7.70 Priority (Bridge Parameters)
7.71 Max Age(s)
7.72 Hello Time(s) (Spanning Tree)
7.73 Forward Delay(s) (Spanning Tree)
7.74 TxHoldCount(per second) (Spanning Tree)
7.75 Root Path Cost
7.76 Hold Count (Spanning Tree)
7.77 Port ID
7.78 Designated Path Cost
7.79 Designated Root Bridge Priority
7.80 Designated Bridge Priority(Spanning Tree)
7.81 Designated Bridge MAC Address (Spanning Tree)
7.82 Edge Port Status (Spanning Tree)
7.83 Point to Point Attributes(External Ethernet Port Attributes)
7.84 Enabling LCAS
7.85 LCAS Mode

System
7.86 Hold-Off Time (ms) (LCAS)

7.87 WTR Time (s) (LCAS)
7.88 TSD (LCAS)
7.89 Min Members - Transmit Direction
7.90 LPT
7.91 Bearer Mode
7.92 Port-Type Port Hold-Off Time (ms)
7.93 VCTRUNK Port Hold-off Time (ms)
7.94 Protocol Enable (IGMP Snooping Protocol)
7.95 Multicast Aging Time(Min)
7.96 Frames to Send
7.97 Status
7.98 Set Frame Count
7.99 Received Response Test Frame Count
7.100 Test Frames to Receive
7.101 Send Mode (Ethernet Test)
7.102 Call Waiting Time(s)
7.103 Conference Call
7.104 Phone
7.105 Available Orderwire Port
7.106 No.(F1 Data Port)
7.107 Data Channel (F1 Data Port)
7.108 Overhead Byte (Broadcast Data Port)
7.109 Working Mode (Broadcast Data Port)
7.110 Broadcast Data Source (Broadcast Data Port)
7.111 Broadcast Data Sink (Broadcast Data Port)
7.112 External Clock Output Mode When 2M Output Synchronous Source Is Invalid
7.113 External Clock Output Mode
7.114 External Clock Output Timeslot
7.115 External Source Output Threshold
7.116 2M Phase-Locked Source Fail Condition
7.117 2M Phase-Locked Source Fail Action
7.118 Clock Source Threshold

System
7.119 AIS Alarm Generated

7.120 B1 BER Threshold-Crossing Generated
7.121 B2-EXC Alarm Generated
7.122 Higher Priority Clock Source Reversion Mode
7.123 Clock Source WTR Time
7.124 Lock Status
7.125 Synchronous Source
7.126 S1 Byte Synchronization Quality Information
7.127 NE Clock Working Mode
7.128 Data Output Method in Holdover Mode
7.129 Retiming Mode
7.130 Switching Mode (MSP)

System
7.1 Port Attributes (Ethernet Port)

Description
The Port Attributes (Ethernet Port) parameter specifies the position of a port in the network.
Different port attributes support different packets.
Impact on the System

The system operation is not affected.
Values
Board Name Valid Values Default Value
EFS8 UNI, C-Aware, S-Aware UNI
The following table lists the description of each value.
Value Description
UNI Indicates the interface between CE and PE. This port

processes the packets with TAG attributes specified in IEEE
802.1Q. Moreover, this port identifies and processes the
VLAN IDs of the received packets according to the supported
Tag Aware, Access or Hybrid.
C-Aware A C-Aware (C-VLAN Aware) port in the network is located

in the position as the UNI port at the client access side. This
port identifies and processes the VLAN (C-VLAN) in the
packets. If the value of QinQ TYPE is valid, this port treats
the outer labels of the packets as C-VLAN.
S-Aware A S-Aware (S-VLAN Aware) port in the network is located

in the position as the interface on the network side. This port
identifies and processes the VLAN (S-VLAN) in the packets.
If the value of QinQ TYPE is valid, this port treats the outer
labels of the packets as S-VLAN.
Configuration Guidelines
The port attribute depends on the port position in the network and the service. For this reason,
select a proper port attribute as required. Generally, select the default value.
l For the MPLS service, select P for the port that transmits or receives packets with MPLS
labels.
l For the QinQ service, select C-Aware or S-Aware for the port. Connecting to the port of
the client network, a C-Aware port identifies and processes the packets with C-VLAN

System
labels. Connecting to the port at the network side, an S-Aware port identifies and processes
the packets with S-VLAN tags. The configuration examples are described as follows:
– Add the S-VLAN tag to the service from Port A to Port B, and remove the S-VLAN
tag from the service from Port B to Port A. Then select C-Aware for Port A, and S-
Aware for Port B.
– Configure a service from Port A to Port B to transparently transmit the C-VLAN tags
at the client side. Then select C-Aware for Ports A and B.
– Configure a service from Port A to Port B to transparently transmit the S-VALN tags
at the network side. Then select S-Aware for Ports A and B.
– Configure a service from Port A to Port B to switch the C-VLAN tags at the client side.
Then select C-Aware for Ports A and B.
– Configure a service from Port A to Port B to switch the S-VALN tags at the network
side. Then select S-Aware for Ports A and B.
Relationship with Other Parameters

None.
Related Information
According to the position and role of the equipment in the networking, there are three types of
equipment: CE, PE (U-PE & N-PE), and P. Client Edge (CE) indicates the equipment at the
client side. Provider Edge (PE) indicates the edge equipment at the network side. Provider (P)
indicates the intermediate node at the network side.
7.2 Maximum Frame Length (Ethernet Port Attribute)

Description
The Maximum Frame Length (Ethernet Port Attribute) parameter specifies the maximum
frame length that is supported at an Ethernet port.

If the packet length exceeds the specified maximum frame length, the packets are discarded.
Alternatively, the packet length is minimized to the specified frame length. This parameter takes
effect only when the packet enters the port rather than when the packet that exits the port.
Values
Valid Values Default Value Unit
1518-9600 1522 Byte
Set the value as required. Generally, select the default value, unless otherwise specified.

System

None.
7.3 Non-Autonegotiation Flow Control Mode (Ethernet Port

Attribute)
Description
The Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute) specifies the flow
control mode adopted when an Ethernet port works in non-auto-negotiation mode.

Values
EFS8, EGT1 Disabled, Enable Symmetric Disable

Flow Control, Send Only,
Receive Only
Value Description
Disable Indicates that the port disables the flow control function.
Enable Symmetric Flow Indicates that the port can transmit PAUSE frames and
Control process the received PAUSE frames.
Send Only Indicates that the port sends the PAUSE frame only.
Receive Only Indicates that the port can only process the received PAUSE
frames.
This parameter is meaningful only when you configure the EPL service. You can select the value
as required.

None.

System
7.4 Autonegotiation Flow Control Mode (Ethernet Port

Attribute)
Description
The Autonegotiation Flow Control Mode (Ethernet Port Attribute) specifies the flow control
mode adopted when an Ethernet port works in auto-negotiation mode.

If the negotiation result is to enable the flow control function, the PAUSE frame is transmitted
to the upstream port.
Values
Valid Values Default Value
Disabled, Enable Dissymmetric Flow Disabled

Control, Enable Symmetric Flow Control,
Enable Symmetric/Dissymmetric Flow
Control
Value Description
Disabled Indicates that the port disables the flow control function.
Enable Dissymmetric Flow Indicates that the port only transmits flow control frames, but
Control does not process the received flow control frames.
Enable Symmetric Flow Indicates that the port can transmit PAUSE frames and
Control process the received PAUSE frames.
Enable Symmetric/ Indicates that the symmetric/dissymmetric flow control mode

Dissymmetric Flow Control is decided by the auto-negotiation result.
Generally, set this parameter to Enable Symmetric/Dissymmetric Flow Control, unless
otherwise specified.

System
7.5 MAC Loopback (Ethernet Port Attribute)

Description
The MAC Loopback (Ethernet Port Attribute) parameter specifies the MAC loopback state
at an Ethernet port. Port loopback setting is applied to locating faults only.

MAC loopback is a function of diagnosing faults. It may affect the services configured at the
port. If the loopback state is set to Inloop, the services at the port may be interrupted.
Values
Value Range Default Value
Non-Loopback, Inloop Non-Loopback
Value Description
Non-Loopback Indicates the normal state. If the equipment works normally,

you do not need to set the MAC loopback.
Inloop Loops back the services from the cross-connection side to the
cross-connection side within the equipment at the local end.
None.

None.
7.6 PHY Loopback (Ethernet Port Attribute)

Description
The PHY Loopback (Ethernet Port Attribute) parameter specifies the PHY loopback state at
an Ethernet port. Port loopback setting is applied to locating faults only.

System

PHY loopback is a function of diagnosing faults. It may affect the services configured at the
port. If the loopback state is set to Inloop, the services at the port may be interrupted.
Values
Non-Loopback, Inloop Default Value
Value Description
Non-Loopback Indicates the normal state. If the equipment works normally,

you do not need to set the PHY loopback.
Inloop Loops back the services from the cross-connection side to the
cross-connection side within the equipment at the local end.
None.

None.
7.7 QinQ Type Area

Description
The QinQ Type Area parameter indicates the VLAN protocol used by the packet that is
transmitted by QinQ.
The default value 0x8100 of this parameter is the protocol type that is specified by the related
standard. The original equipment of other vendors may use 0x88A8 or 0x9100 to represent the
VLAN protocol. To realize the interconnection with the original equipment, the user should set
this parameter accordingly.

If the values of the QinQ Type Area parameter set for the equipment at the two ends of the
interconnection are inconsistent, the service becomes unavailable.

System
Values
0x600-0xFFFF 0x8100
Set this parameter according to the supported value of QinQ Type Area of the opposite
equipment.
7.8 Loop Detection (Ethernet Port Attribute)

Description
The Loop Detection (Ethernet Port Attribute) parameter specifies the function of reporting
the self-loop alarms after one of the following loopback cases is detected.
l For the external physical interface of the board, the transmit direction is connected to the
receive direction by a fiber.
l The two external physical ports on the board are cross-connected to each other through
fibers.
l The cross-connection is created on the same VCTRUNK of the board.
l The cross-connection is created between different VCTRUNKs of the board.

After the self-loop check function is enabled for a port, the specified self-loop check packets are
transmitted from the port. One packet is transmitted each second.
Values
EFS8 Enabled, Disabled Disabled
To check the self-loop port, select Enabled.

The loop port shut-down function takes effect only after the loop check function is enabled.

System
7.9 Loop Port Shutdown (Ethernet Port Attribute)

Description
The Loop Port Shutdown (Ethernet Port Attribute) parameter is set to disable the self-loop
port after a self-loop port is detected if the loop port shutdown function is enabled. After the
self-loop port is shut down, the self-loop port only transmits or receives the self-loop detection
packets rather than any other packets. If the port is not a self-loop port, it starts to work again.

If a port enables the loop port shut-down function, the IEEE 802.3ah protocol blocks the port
once the port is detected to be a self-loop port. In this case, the services at the port are interrupted.
All the packets based on the upper-level protocol are discarded.
Values
EFS8 Enabled, Disabled Enabled
To block a self-loop port, select Enabled. Otherwise, select Disabled.

The loop port shutdown function takes effect only after the IEEE 802.3ah protocol and the loop
detection function are enabled.
7.10 Traffic Threshold(Mbit/s)(External Ethernet Port

Attribute)
Description
The Traffic Threshold(Mbit/s) (External Ethernet Port Attribute) parameter specifies the
data flow threshold at external physical ports.

If the data flow at external physical ports is greater than the specified threshold, the
FLOW_OVER alarm is generated.

System
Values
Board Name Valid Values Default Value Unit
EFS8 0-100 (FE), 0-1000 100 (FE), 1000 (GE) Mbit/s

(GE), in step length
of 1
Generally, select the value according to the bandwidth.

None.
7.11 Broadcast Packet Suppression Threshold (Ethernet

Interface Attributes)
Description
The Broadcast Packet Suppression Threshold(Ethernet Interface Attributes) parameter
allocates the specified bandwidth to the broadcast packets. The bandwidth is allocated on the
basis of the traffic proportion at the port. If the bandwidth allocated to the broadcast packets
reaches the specified threshold, the port discards the broadcast data packets that are received.

l If less bandwidth is allocated to the broadcast packets, some necessary broadcast services
are affected.
l If excessive bandwidth is allocated to the broadcast packets, excessive broadcast packets
may enter the network. Consequently, the network running is affected.
Values
Board Name Value Range Default Value
EFS8 10%-100% 30%
You can set this parameter according to the percentage of the traffic at the port. The value 10
means that the whole bandwidth is allocated to the port.
Generally, adopt the default value.

System

None.
7.12 Broadcast Packet Suppression (Ethernet Interface

Attributes)
Description
The Broadcast Packet Suppression (Ethernet Interface Attributes) parameter specifies
whether to enable the function for a port to suppress the broadcast packets and to control the
traffic of the broadcast data packets that enter the port. If the broadcast packet suppression
function is enabled, and if the broadcast traffic exceeds the specified threshold value, the
broadcast packets that enter the port are discarded.

If Broadcast Packet Suppression is set to Enabled, the port can effectively suppress the traffic
of the broadcast packets by using the statistic function of the network processor on the board.
Values
EFS8 Enabled, Disabled Disabled
You can set this parameter according to whether to control the traffic of the broadcast packets.

None.
7.13 Zero-Flow Monitor (Ethernet Interface Attributes)

Description
The Zero-Flow Monitor parameter specifies whether the traffic on a port is monitored.

After the zero traffic monitoring function is enabled, the port can report the zero traffic alarm
after the state of zero traffic lasts for a certain period. Hence, the user can check whether the
service is interrupted due to the fault on the equipment side.

System
Values
Enabled, Disabled Disabled
The following table provides the description of each value.
Value Description
Enabled The zero traffic monitoring function is enabled on the port.
Disabled The zero traffic monitoring function is disabled on the port.
Set this parameter according to the actual requirement of the user. Set this parameter to
Enabled if the traffic on a port needs to be monitored.
7.14 Port Traffic Threshold Time Window(Min)

Description
The Port Traffic Threshold Time Window(Min) parameter specifies the duration for a
VCTRUNK or a IP port to monitor the traffic after the zero traffic monitoring function of the
port is enabled.

If the value of this parameter is too large, the port may fail to report the zero traffic alarm. If the
value of this parameter is too small, the jitter due to the zero traffic alarm may occur on the port.
Values
Board Name Value Range Default Value Unit
EFS8 0-30 0 min
The user can set this parameter according to the actual service requirement.

System
7.15 Jumbo Frame Type

Description
Jumbo Frame Type specifies the value of the jumbo frame type on an Ethernet port. The jumbo
frame indicates the oversized Ethernet frame, whose maximum length is 65535 bytes. The
Ethernet service board determines whether the Ethernet frame is a jumbo frame according to the
value of the jumbo frame type.

Values
0 to 65535 34928
The value of this parameter must be the same as the value of the accessed jumbo frame type.
Otherwise, the Ethernet board does not consider the frame as a jumbo frame.

The maximum transmission unit (MTU) parameter is used for the Ethernet port. If the length of
Ethernet frames is greater than the length of the jumbo frame, the Ethernet port discards these
Ethernet frames. If the length of Ethernet frames is smaller than the length of the jumbo frame
but is greater than the MTU, the Ethernet port discards the Ethernet frames whose length is
greater than the MTU. If the length of Ethernet frames is smaller than the MTU, the Ethernet
port does not discard the received Ethernet frames.
7.16 Default VLAN ID (Ethernet Port Attribute)

Description
The Default VLAN ID (Ethernet Port Attribute) parameter specifies the default VLAN ID
of a port.


System
Values
EFS8 1-4095 1
Allocate the default VLAN ID according to the networking plan of the service carrier.

l If Tag is set to Access for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, their
VLAN IDs are peeled off.
l If Tag is set to Hybrid for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, the
VLAN IDs are peeled off if they are the same as the default VLAN IDs. Otherwise, these
packets are directly transmitted.
l If Tag is set to Tag Aware for a port, packets without VLAN IDs are discarded before they
enter the port. Otherwise, these packets are directly transmitted.
7.17 VLAN Priority (Ethernet Port Attribute)

Description
The VLAN Priority (Ethernet Port Attribute) parameter specifies the priority of the default
VLAN ID of a port. It indicates the priority of the service quality.

Values
EFS8 0-7 0
Set the VLAN priority according to the service requirements and the allocation of the service
carrier.

None.

System
7.18 Entry Detection (Ethernet Port Attribute)

Description
The Entry Detection (Ethernet Port Attribute) parameter specifies whether to identify the tag
labels in the data packets.

The entry detection function can be disabled in the port-based services only. If the entry detection
function is disabled, you may fail to configure other VLAN-based services.
Values
EFS8 Enabled, Disabled Enabled
Value Description
Enabled The port checks the Tag label. In this case, the Tag attribute
of the port is valid.
Disabled The port does not check the tag label. In this case, the Tag
attribute of the port is invalid.
l To transmit the data packet transparently, the user can disable the entry detection function.
l To forward the data packet according to the contents of the data packet, the user can enable
the entry detection function.

None.
7.19 TAG
Description
TAG indicates that the Ethernet port supports IEEE 802.1Q Ethernet packets that contain VLAN
tags. You can set three attributes to differentiate the packets from each other so that these packets
can be transmitted efficiently.

System

Values
Access, Tag Aware, Hybrid Tag Aware
Value Description
Access A port receives only the packets that do not

contain VLAN tags. After receiving the packets,
the port adds the default VLAN tag (PVID) to
these packets. When the packets are transmitted
from the port, the VLAN tags are stripped off the
packets.
Tag Aware A port receives only the packets that contain

VLAN tags and discards the packets that do not
contain VLAN tags. When the packets are
transmitted from the port, they are directly
forwarded to the next port.
Hybrid A port can receive all the packets regardless of

VLAN tags. After receiving the packets that do
not contain VLAN tags, the port adds the default
VLAN tag (PVID) to these packets. When the
packets are transmitted from the hybrid port, the
egress port determines whether the VLAN tags
contained in the packets are the same as the
PVID. If yes, the egress port strips the VLAN
tags off the packets and then forwards these
packets. Otherwise, the egress port directly
forwards these packets.
The tag attributes are configured for MAC ports and VCTRUNK ports. Hence, the VCTRUNK
ports at both ends of the trunk link can be configured with the tag attributes. In the case of a link,
the services are available only when the parameters of the tag attributes are the same for the
VCTRUNK ports on the source and sink ports. No requirements are proposed for the tag
attributes of MAC ports.

System

l If TAG is set to Access for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, their
VLAN IDs are peeled off.
l If TAG is set to Hybrid for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, the
VLAN IDs are peeled off if they are the same as the default VLAN IDs. Otherwise, these
packets are directly transmitted.
l If TAG is set to Tag Aware for a port, packets without VLAN IDs are discarded before
they enter the port. Otherwise, these packets are directly transmitted.
l For C-Aware and S-Aware ports, the tag attribute cannot be set.
Related Information
Mapping relationship between the packets handled by the port and the tag identifiers
Packet Type Attribute of the Ingress Handling Method
Port
Ethernet packets that contain Tag aware The port transmits these
tags packets.
Access The port discards these

packets.
Hybrid The port transmits these

packets.
Ethernet packets that do not Tag aware The port discards these
contain tags packets.
Access The port transmits these

packets after adding the
default VLAN ID to these
packets.
Hybrid The port transmits these

packets after adding the
default VLAN ID to these
packets.
7.20 Mapping Protocol

Description
The Mapping Protocol parameter specifies the mapping protocol of the VCTRUNK port.

System

The Mapping Protocol parameter of the VCTRUNK is the basic setting of the VCTRUNK port.
If the parameter value is different from that of Mapping Protocol for the VCTRUNK of the
interconnected equipment, the service is interrupted.
Values
Table 7-1 shows the value range of each type of board.
Table 7-1 The mapping protocol supported by each type of board

GFP, LAPS, HDLC GFP
Value Description
GFP Uses the GFP protocol to encapsulate the data of the

VCTRUNK port.
LAPS Uses the LAPS protocol to encapsulate the data of the

VCTRUNK port.
HDLC Uses the HDLC protocol to encapsulate the data of the

VCTRUNK port.
The value of Mapping Protocol for VCTRUNK of the local equipment must be the same as
that of Mapping Protocol for the VCTRUNK of the interconnected equipment.

None.
7.21 Scramble
Description
The Scramble parameter specifies whether to scramble the payload area of the encapsulation
protocol and the scramble mode.

If the value of Scramble for the VCTRUNK of the local equipment is different from that of
Scramble for the VCTRUNK of the interconnected equipment, the service is interrupted.

System
Values
Table 7-2 Scramble supported by each type of board

Unscrambled, Scrambling mode[X43+1], Scrambling mode Scrambling mode[X43+1]

[X48+1]
Value Description
Unscrambled Does not scramble the payload area.
Scrambling mode[X43+1] Scrambles the payload area in [X43+1] mode.
Scrambling mode[X48+1] Scrambles the payload area in [X481] mode.
The value of Scramble for VCTRUNK must be the same as that of Scramble for the VCTRUNK
of the interconnected equipment.

None.
7.22 Set Inverse Value for CRC

Description
The Set Inverse Value for CRC parameter specifies whether to set an inverse value for the
CRC field of the HDLC or LAPS protocol.

If the value of Set Inverse Value for CRC for the VCTRUNK of the local equipment is different
from that of Set Inverse Value for CRC for the VCTRUNK of the interconnected equipment,
the service is interrupted.
Values
EFS8, EGT1 Yes, No Yes

System
Value Description
Yes Sets an inverse value for the CRC field.
No Does not set an inverse value for the CRC field.
The value of Set Inverse Value for CRC for VCTRUNK of the local equipment must be the
same as that of Set Inverse Value for CRC for the VCTRUNK of the interconnected equipment.

This parameter takes effect only when Mapping Protocol is set to LAPS or HDLC.
7.23 Check Field Length

Description
The Check Field Length parameter specifies the length of the CRC field of the mapping
protocol.

If Mapping Protocol is set to HDLCor LAPS, and if the value of Check Field Length is
different from that for the interconnected VCTRUNKs at the two ends, the service is interrupted.
Values
Table 7-3 The length of the CRC field supported by each type of board
Mapping
Board Name Protocol Value Range Default Value
EFS8, EGT1 GFP l FCS32 FCS32

l No
LAPS l FCS32
HDLC l FCS32

System
Value Description
No The protocol frame does not contain the CRC field. Only the
GFP protocol supports this option.
FCS32 The CRC field of the protocol frame contains 32 bits.
If Mapping Protocol is set to HDLC or LAPS, the value of Check Field Length must be
consistent for the interconnected VCTRUNKs at the two ends.

If Mapping Protocol is set to HDLC or LAPS, select FCS32 only.
7.24 FCS Calculated Bit Sequence

Description
The FCS Calculated Bit Sequence parameter specifies the sequence of storing the bits in the
CRC field of the mapping protocol.

If the value of FCS Calculated Bit Sequence for the VCTRUNK of the local equipment is
different from that of FCS Calculated Bit Sequence for the VCTRUNK of the interconnected
equipment, the service is interrupted.
Values
Table 7-4 FCS calculated bit sequence supported by each type of boards
Mapping
Board Name Protocol Value Range Default Value
EFS8 l GFP Big endian l Mapping Protocol:

l LAPS Little endian GFP
l HDLC l FCS Calculated Bit
Sequence: Big endian
EGT1 l GFP Big endian l Mapping Protocol:

l LAPS GFP
l HDLC l FCS Calculated Bit
Sequence: Big endian

System
Value Description
Big endian Stores the FCS field based on Big endian.
Little endian Stores the FCS field based on Little endian.
The value of FCS Calculated Bit Sequence for the VCTRUNK of the local equipment must
the same as that of FCS Calculated Bit Sequence for the VCTRUNK of the interconnected
equipment.

None.
7.25 Operation Type (EPL Service)

Description
The Operation Type (EPL Service) parameter specifies whether to add, strip, translate or
transparently transmit VLAN labels for service packets at a port when Service Type is set to
EVPL(QinQ).

After you select an operation type, the system performs the relevant operation.

System
Values
EFS8 l For bidirectional services, the options are as Add S-VLAN

follows:
– Add S-VLAN
– Transparently Transmit C-VLAN
– Transparently Transmit S-VLAN
– Transparently Transmit S-VLAN and C-
VLAN
– Translate S-VLAN
l For unidirectional services, the options are as
follows:
– Add S-VLAN
– Transparently Transmit C-VLAN
– Transparently Transmit S-VLAN
– Transparently Transmit S-VLAN and C-
VLAN
– Translate S-VLAN
– Strip S-VLAN
Value Description
Add S-VLAN Indicates that the one layer of S-VLAN label is added to the
processed packets in the service.
Translate S-VLAN If the source S-VLAN labels of the packets processed in the
service are translated into the sink S-VLAN labels, the source
S-VLAN label must be different from the sink S-VLAN label.
Transparently transmit S- Forwards the service packets according to the port or S-VLAN.
VLAN After the packets are processed in the service, the S-VLAN
labels in the packets are not changed.
Transparently transmit C- Forwards the service packets according to the port or C-VLAN.
VLAN After the packets are processed in the service, the C-VLAN
labels in the packet are not changed.
Transparently Transmit S- Indicates that the Transparently transmit C-VLAN and

VLAN and C-VLAN Transparently transmit S-VLAN labels are added to the packets
processed in the service.
Strip S-VLAN Strips the S-VLAN label.

System
Select a proper item according to network planning and service model.

None.
7.26 Service Type (EPL Service)

Description
The Service Type (EPL Service) parameter specifies the Ethernet private line service type.

Values
EFS8 EPL, EVPL(QinQ) EPL
EGT1 EPL EPL
Value Description
EPL Indicates the transparent transmission service or the VLAN

private line service.
EVPL(QinQ) Indicates the Ethernet QinQ virtual private line service.
Select a service type as required.

None.
7.27 Encapsulation Format of P Port (Network Attributes)

Description
Encapsulation Format of P Port (Network Attributes) indicates that the board supports
receiving of data packets in the MPLS encapsulation format and normal Ethernet data packets.

System
The port needs to process different types of packets in different ways, so you need to set the port
to a PE port or a P port. The PE port is not configured with the encapsulation format, while the
P port is configured with the encapsulation format. The P port indicates a port for connecting
the equipment of the network provider, so the P port receives data packets in the MPLS
encapsulation format. You can set the packet encapsulation format of the P port by running the
configuration command.

If the encapsulation format of the data packet that enters the port is inconsistent with the
configured encapsulation format of the port, the data packet is discarded.
Values
MartinioE, stack VLAN MartinioE
Value Description
MartinioE Figure 7-1 shows the encapsulation format of

MartinioE.
Stack VLAN Figure 7-2 shows the encapsulation format of Stack

VLAN.
The user can choose an encapsulation format according to the requirements of the service.
Different encapsulation formats support different types of data packets. When the encapsulation
format is inconsistent with the type of the receive data packet, the data packet is discarded. When
configuring services, the user needs to make sure that the encapsulation format of the port is
consistent with the type of the data packet that is transmitted by the interconnected equipment.

None.
Related Information
Figure 7-1 Encapsulation format of MartinioE
DA SA 0x8847 Tunnel VC Ethernet Data

6 6 2 4 4 N

System
Figure 7-2 Encapsulation format of Stack VLAN
DA SA 0x8100 VLAN VLAN TAG L3Data
7.28 C-VLAN and S-VLAN

Description
The C-VLAN and S-VLAN parameter specifies the two types of VLAN tags defined in the
QinQ service and IEEE 802.1ad. C-VLAN is taken as the client VLAN tag. S-VLAN is taken
as the service VLAN tag. C-VLAN Tag (C-TAG) indicates the VLAN tag on the client side,
and S-VLAN Tag (S-TAG) indicates the VLAN tag at the service layer of the carrier.
DMAC SMAC S-VLAN C-VLAN Data FCS
6 bytes 6 bytes 4 bytes 4 bytes - 4 bytes

Values
Empty, 1-4095 Empty
Value Description
Empty Indicates that the port does not check the C-VLAN/S-VLAN.
The services are forwarded according to the port.
1-4095 Indicates that the port checks the C-VLAN/S-VLAN. The

services are forwarded according to the port and C-VLAN/S-
VLAN.

System
Select the value according to the network. Generally, select C-VLAN and S-VLAN allocated
by the carrier.

None.
7.29 VLAN ID (For Creation of Ethernet Virtual Private

Lines)
Description
VLAN ID-- stands for virtual local area network identifier. If port+VLAN is selected in the
policy of using a port, you can select different VLAN IDs (1-4095) to represent different Ethernet
services.

Values
1 to 4095 -
l The value range is relevant to the encapsulation format of the P port (Per-NE configuration).
In the case of Martinioe, the value ranges from 16 to 1023. In the case of stack VLAN, the
value ranges from 1 to 4095.
l The VLAN IDs at both ends of a link must be the same. In the case of different Ethernet
services, you can set the VLAN ID to different values.

This parameter is valid only when you set "Flow Type" to "Port+VLAN".
7.30 Bridge Learning Mode (Ethernet LAN Service)

Description
Bridge Learning Mode (Ethernet LAN Service) indicates how the bridge learns the MAC
address. Bridge Learning Mode is classified into the shared VLAN learning and independent
VLAN learning modes. The shared VLAN learning mode indicates learning and forwarding

System
based on the MAC address. The independent VLAN learning mode indicates learning and
forwarding based on the VLAN and MAC address.

The independent VLAN learning mode realizes the functions of broadcast packet constraint and
virtual workgroup and ensures that the data are transmitted safely on the network.
The shared VLAN learning mode indicates the MAC address that is learnt by this VLAN
interface is shared by all the other VLAN interfaces, which reduces the safety of data packets.
Values
IVL, SVL IVL (The bridge type is

compliant with IEEE 802.1q
or IEEE 802.1ad), SVL (The
bridge type is compliant with
IEEE802.1d or IEEE 802.1ad)
Value Description
SVL Indicates that in the shared VLAN learning mode, the

bridge learns all the data messages based on the MAC
address.
IVL Indicates that in the independent VLAN learning mode,

data packets of different VLAN interfaces are not
associated.
The user can set the parameter according to the networking requirements.

None.
7.31 MEP ID (Ethernet OAM)

Description
The MEP ID (Ethernet OAM) specifies the flag that uniquely identifies a maintenance point.
The bytes from higher bits to lower bits are respectively described here. The first byte indicates
the network number. The second byte indicates the number of the node in the local network.

System
The third and forth bytes indicate the ID of the maintenance point on the network node. The
maintenance point ID must be unique in the entire network.

Values
00-00-0001 to FF-FF-FF00 00-00-0001
The maintenance point ID must be unique in the entire network. Moreover, the U2000 can check
whether the maintenance point ID is duplicate.

None.
7.32 Maintenance Point Type (Ethernet OAM)

Description
The Maintenance Point Type (Ethernet OAM) specifies the maintenance point type defined
in IEEE 802.1ag. MEP stands for Maintenance association End Point, and MIP stands for
Maintenance association Intermediate Point.

Values
MEP, MIP MEP
None.

None.

System
7.33 CC Status (Ethernet OAM)

Description
The CC Status (Ethernet OAM) parameter specifies whether to activate the connectivity check
(CC) function at a maintenance point.

After the CC function is activated, the maintenance point starts the CC. If the check is initially
successful, the EX_ETHOAM_CC_LOS alarm is reported if a CC failure occurs later.
Values
Activate, Inactivate Inactivate
To start the connectivity check, activate the CC function at a maintenance endpoint.
To stop the connectivity check, deactivate the CC function.

The CC function can be activated at a maintenance endpoint only.
7.34 Test Result (LB and LT Test)

Description
The Test Result (LB and LT Test) parameter specifies the result derived from the LB or LT
test each time.

Values
Succeeded, Failed -

System
None.

None.
7.35 Responding MP Type (Ethernet LT Test)

Description
The Responding MP Type (Ethernet LT Test) parameter specifies the type of the responding
maintenance point in each LT test.

Values
MEP, MIP, Unknown Unknown
None.

The responding maintenance point must return the type, which is specified when this
maintenance point is created.
7.36 Hop Count (Ethernet LT Test)

Description
The Hop Count (Ethernet LT Test) parameter specifies the number of hops from the
maintenance source endpoint to an maintenance intermediate point, namely, the number of
responding intermediate points from the maintenance source point to a certain responding point.
As shown in Figure 7-3, MEP1 and MEP2 are the maintenance endpoints. MIP1, MIP2, MIP3
and MIP4 are the maintenance intermediate points. In this case, the number of hops from MEP1
to MEP2 is 5, and that from MEP1 to MIP3 is 3.

System
Figure 7-3 An example of number of hops

Values
If the value of Hop Count is 2, there are two hops.
None.

None.
7.37 Packet Length (Ping Test)

Description
The Packet Length (Ping Test) parameter specifies the maximum length of the Ping packets if
the Ping operation is initiated at a maintenance endpoint.

Values
64-1522, in step length of 1 64 Byte
Set the value according to the expected frame length.

System

None.
7.38 Timeout (Ping Test)

Description
The Timeout (Ping Test) parameter specifies the waiting period in which no response message
is received from the opposite end after a maintenance point initiates the Ping test. In this case,
the maintenance point regards that the Ping test fails. This waiting period is called the Ping
timeout time.

After initiating the Ping test, the maintenance point returns a Ping timeout message if it fails to
receive the response message from the opposite end when the Ping timeout time is reached.
Values
3-60, in step length of 1 5 Second
Set this parameter to a lower value if the requirement is high for the response time.
Set this parameter to a higher value if the requirement is low for the response time.

The values of Timeout and Ping Attempts decides the longest duration required to perform the
Ping test.
7.39 Detect Attempts

Description
The Detect Attempts parameter specifies the detection attempts for performing performance
detection defined in IEEE 802.1ag.

If the value of Detection Count is larger, the test result is more accurate in each performance
detection test. In this case, more system resources are used, and longer time is consumed.

System
Values
1-1000, in step length of 1 1 Attempt
Set this parameter to a proper value according to the test accuracy and the system resource used
in the test.

None.
7.40 Send Direction (Ethernet Test)

Description
Send Direction (Ethernet Test) indicates the transmit direction of the test packet.

Values
SDH Direction, / /
Value Description
SDH Direction, / Indicates that the test packet is transmitted from the
VC trunk port to the SDH side.
/ Indicates that the parameter is invalid.

This parameter is valid and displayed as SDH Direction only when Send Mode is set to Burst
Mode or Continue Mode. This parameter is displayed as / when Send Mode is set to
Disabled.

System
7.41 Error Frame Monitor Window (ms)

Description
The Error Frame Monitor Window (ms) parameter specifies the period during which the
number of error frames received at the port exceeds the specified upper threshold. In this case,
a link event alarm is reported.

After you set the Error Frame Monitor Threshold (Entries) and Error Frame Monitor
Window (ms) parameters, a link event alarm is reported if the actual number of error frames in
the link exceeds the specified threshold.
Values
1000-60000, in step length of 100 1000 ms
Set the value according to the actual port rate and the monitoring period.
Make sure that the value of Error Frame Monitor Threshold (Entries) is not greater than the
maximum number of frames received at the port within the time specified in Error Frame
Monitor Window (ms).

To set Error Frame Monitor Window (ms), set Error Frame Monitor Threshold
(Entries). Moreover, set Port Rate. For details, refer to the description of the Error Frame
Period Window(Frames) parameter.
7.42 Error Frame Monitor Threshold(Entries)

Description
The Error Frame Monitor Threshold(Entries) parameter specifies the upper threshold of error
frames received at the port. In this case, a link event alarm is reported.

After you set the Error Frame Monitor Threshold(Entries) and Error Frame Monitor
Window (ms) parameters, a link event alarm is reported if the actual number of error frames in
the link exceeds the specified threshold.

System
Values
1-4294967295 (in step length of 1) 2 Frame
If higher link performance is required, set the threshold to a lower value. Otherwise, set the
threshold to a higher value.
Make sure that the value of Error Frame Monitor Threshold(Entries) is not greater than the
maximum number of frames received at the port within the time specified in Error Frame
Monitor Window (ms).

To set Error Frame Monitor Threshold(Entries), set Error Frame Monitor Window
(ms). Moreover, set Port Rate. For details, refer to the description of the Error Frame Period
Window(Frames)parameter.
7.43 Error Frame Period Window(Frames)

Description
The Error Frame Period Window(Frames) parameter specifies the received N frames in which
the number of error frames reach the specified upper threshold. In this case, a link event alarm
is reported.

After you set the Error Frame Period Window(Frames) and Error Frame Period Threshold
(Frames) parameters, a link event alarm is reported if the number of error frames received within
a certain period reaches the specified upper threshold.
Values
Maxpps/10-Maxpps*60, in step length Maxpps Frame

of 1
Set the value according to the actual data frame transmission rate and the frames. If the data
transmission rate is high, set this parameter to a higher value. Otherwise, set this parameter to a
lower value.

System

The value range depends on the port rate.
Related Information
Maxpps: indicates the maximum number of frames per second.
Specifically,
l If the port rate is 10 Mbit/s, the Maxpps value is 14880.

l If the port rate is 10 Gbit/s, the Maxpps value is 14880000.
According to the rule of Maxpps/10 < Error Frame Period Window(Frames) < Maxpps*60,
you know the value range of the Error Frame Period Window(Frames) parameter for a certain
port rate.
7.44 Error Frame Monitor Threshold(Frames)

Description
The Error Frame Monitor Threshold(Frames) parameter specifies the received N frames in
which the number of error frames reach the specified upper threshold. In this case, a link event
alarm is reported.

After you set the Error Frame Period Window(Frames) and Error Frame Period Threshold
(Frames) parameters, a link event alarm is reported if the number of error frames received within
a certain period reaches the specified upper threshold.
Values
1-892800000, in step length of 1 1 Frame
None.

None.

System
7.45 Error Frame Second Window (s)

Description
The Error Frame Second Window (s) parameter specifies the error frame second when any
error frames are received at the port within one second. If the error frame seconds within a certain
time period reach the specified upper threshold, link event alarms are reported. The time period
in which error frames are received is called the error frame second window.

After you set the Error Frame Second Window (s) and Error Frame Second Threshold (s)
parameters, link event alarms are reported if the actual error frame seconds in the link reach the
specified upper threshold.
Values
Set the value according to the monitoring time period.
Make sure that the value of Error Frame Second Window (s) is not less than that of Error
Frame Second Threshold (s).

Set the Error Frame Second Window (s) parameter together with the Error Frame Second
Threshold (s) parameter.
7.46 Error Frame Second Threshold(s)

Description
The Error Frame Second Threshold(s) parameter specifies the second during which error
frames are received at the port. If the error frame seconds within a certain time period reach the
specified upper threshold, a link event alarm is reported. The upper threshold is called the error
frame second threshold.

After you set the Error Frame Second Threshold (s) parameter, link event alarms are reported
if the actual error frame seconds in the link reach the specified upper threshold.

System
Values
None.

None.
7.47 Enable OAM Protocol

Description
The Enable OAM Protocol parameter specified whether the end-to-end OAM protocol
(namely, the IEEE 802.3ah protocol) is enabled at a port.

Values
None.

None.
7.48 OAM Working Mode

Description
The OAM Working Mode parameter specifies a negotiation mode defined in IEEE 802.3ah. It
involves two modes: Passive and Active.

System

Before IEEE 802.3ah is enabled, the local and opposite ends fail to negotiate with each other if
OMA Working Mode is set to Passive.
Values
Active, Passive Active
Value Description
Active Indicates that a port actively transmits the IEEE 802.3 ah

packets.
Passive Indicates a port transmits the IEEE 802.3 ah packets to

the opposite end only after receiving IEEE 802.3 ah
packets from the opposite end.
None.

None.
7.49 Remote Alarm Support for Link Event

Description
The Remote Alarm Support for Link Event parameter specifies whether to report the detected
link events (for example, Error Frame Period Threshold, Error Frame Monitor
Threshold, and Error Frame Second Threshold) to the opposite end.

After the Remote Alarm Support for Link Event parameter is set to Enabled, link event alarms
are displayed in the opposite equipment if any link events occur.
Values
Enabled, Disabled Enabled

System
None.

None.
7.50 Unidirectional Operation

Description
The Unidirectional Operation parameter specifies the hardware capability. If a port fails at the
receive end, but can transmit data frames at the transmit end, it has the capability of performing
unidirectional operations. Otherwise, it does not have the capability of performing unidirectional
operations.
The unidirectional operation function specified in IEEE 802.3ah refers to whether the hardware
performs unidirectional operations if it has the capability of performing unidirectional
operations.
If the hardware does not have the capability of performing unidirectional operations, the
unidirectional operation function specified in IEEE 802.3ah is unavailable.

After the Unidirectional Operation parameter is set to Enabled, IEEE 802.3ah packets are still
transmitted to the opposite end if the receive end is faulty.
Values
If the hardware has the capability of performing unidirectional operations and supports
unidirectional software operations, generally, set Unidirectional Operation to Enabled.

This parameter depends on whether the port hardware has the capability of performing
unidirectional operations.

System
7.51 Loopback Status (OAM Parameter)

Description
The Loopback Status (OAM Parameter) parameter specifies whether a port on the board is
in the loopback state. If yes, the port is in the Initiate Loopback at Local or Respond Loopback
of Remote state.

Values
Initiate Loopback at Local, Respond Non-Loopback

Loopback of Remote, Non-Loopback
Value Description
Non-Loopback Indicates that the port is not in the loopback state defined
in IEEE 802.3ah.
Initiate Loopback at Local Indicates that the local end can transmit the loopback
packets to the remote end.
Respond Loopback of Remote Indicates that the local end can respond to the loopback
packets from the remote end.
None.

None.
7.52 Flow Type (Flow Configuration)

Description
The Flow Type(Flow Configuration) parameter specifies Flow Type of the flow in the Ethernet
data board. This parameter decides the method of binding the service with the flow.

System

If the Flow Type parameter is set incorrectly, that is, the flow classification method is incorrect,
the (Bound CAR or Bound CoS) parameter may fail to meet the expected result. For the effects
of CAR and CoS, refer to the relevant description.
Values
Port Flow, Port+VLAN Flow, Port+SVLAN Flow, Port Port Flow

+CVLAN+SVLAN Flow
Value Description
Port Flow All the packets entering the specified port are
regarded as one flow.
Port+VLAN Flow All the packets that enter the specified port, and
whose Tag VID is consistent with the specified VID,
are regarded as one flow.
Port+SVLAN Flow All the packets that enter from the specified port, and
whose SVLAN VID is consistent with the specified
VID, are regarded as one flow.
Port+CVLAN+SVLAN Flow All the packets that enter from the specified port, and
whose SVLAN VID and CVLAN VID are consistent
with the specified VID, are regarded as one flow.
Based on the required QoS and service type, set a proper value for Flow Type.

None.
7.53 Bound CAR (Flow Configuration)

Description
The Bound CAR (Flow Configuration) parameter specifies the method of binding a flow with
a CAR ID and querying the CAR ID bound with the flow. One flow can be bound with one CAR
ID only. The CAR takes effect only after the flow is bound with the CAR.

System

The CAR-based flow rate can take effect only after the flow is bound with the enabled CAR
policy.
Values
Created CAR ID -
The created flow can be bound with the created CAR policy only. For this reason, you can select
the value from the created CAR ID.

A flow can be bound with the CAR only after the flow and CAR are created.
7.54 Bound CoS (Flow Configuration)

Description
The Bound CoS (Flow Configuration) parameter specifies the method of binding a flow with
a CoS ID and querying the CoS ID bound with the flow. A flow can be bound with one CoS ID
only. The CoS policy can be used to divide the packet priority after the flow is bound with the
CoS.

The flow packets can be divided into different priorities based on the CoS rules only after the
flow is bound with the CoS.
Values
Created CoS ID -
The created flow can be bound with the created CoS policy only. For this reason, you can select
the value from the created CoS ID.

A flow can be bound with the CoS only after the flow and CoS are created.

System
7.55 CAR ID (CAR Configuration)

Description
The CAR ID (CAR Configuration) parameter specifies the ID of a committed access rate
(CAR). When a CAR is created, it needs to be specified with a CAR ID.

The system running is not affected.
Values
1-65535 1
You can set this parameter to any value in the value range as required. A CAR maps a CAR ID.

None.
7.56 Enabled/Disabled (CAR Configuration)

Description
The CAR Enabled/Disabled (CAR Configuration) parameter specifies whether a CAR can
limit the traffic volume.

After the CAR is enabled and bound with a flow, the traffic volume of the flow is limited
according to the value of the CAR parameter. If the transmitted traffic is greater than the specified
value, the excessive traffic is discarded.
Values

System
Value Description
Disabled A CAR is created, but does not take effect.
Enabled A CAR is created, and takes effect.
You can set this parameter to Enabled or Disabled, depending on whether to enable the CAR
to limit the traffic volume.

A CAR can limit the traffic of the flow only when it is set to Enabled and bound with a flow.
7.57 Committed Information Rate (kbit/s) (CAR

Configuration)
Description
The Committed Information Rate (kbit/s) (CAR Configuration) parameter specifies the
committed information rate (CIR) of the committed access rate (CAR). It specifies the minimum
guarantee bandwidth of a flow.

After the CAR is enabled and bound with a flow, the committed bandwidth of the flow is
guaranteed. If the traffic volume is greater than the guarantee bandwidth, the transmission of
excessive traffic cannot be guaranteed.
Values
Value Range Default Value Unit
An integer of 0-1048576, in step length of 64 0 kbit/s
Based on the actual requirement of QoS, you can set a proper value for Committed Information
Rate.
Generally, the value of Committed Information Rate is not less than the expected average rate
of transmitting the flow.

You can set Committed Information Rate of a CAR only after creating the CAR.

System
7.58 Committed Burst Size (kbyte) (CAR Configuration)

Description
The Committed Burst Size (kbyte) (CAR Configuration) parameter specifies the maximum
guaranteed data volume of a flow, which can be transmitted within a certain period.

After the CAR is enabled and bound with a flow, if the volume of burst data in the flow is less
than the value of Committed Burst Size (kbyte), the burst data can be guaranteed for
transmission. Otherwise, they cannot be guaranteed for transmission.
Values
0-32 0 Kbyte
Based on the actual requirements of QoS, you can set a proper value for Committed Burst Size
(kbyte).
Generally, the value of Committed Burst Size (kbyte) is not less than the possible size of
expected burst data flow to be transmitted.

You can set Committed Burst Size (kbyte) of a CAR only after creating the CAR.
7.59 Peak Information Rate (kbit/s) (CAR Configuration)

Description
The Peak Information Rate (kbit/s) (CAR Configuration) parameter specifies the peak
information rate (PIR) of the committed access rate (CAR). It specifies the allowed maximum
rate of a flow.

After the CAR is enabled and bound with a flow, the flow rate is limited according to the peak
bandwidth of the CAR parameter.
If the traffic volume is greater than the value of Peak Information Rate (kbit/s), the excessive
traffic is discarded.

System
Values
An integer of 0-1048576, in step length 0 kbit/s

of 64
Based on the actual requirement of QoS, you can set a proper value for Peak Information Rate
(kbit/s).
The value of Peak Information Rate (kbit/s) should not be less than the guarantee bandwidth.
Generally, the value of Peak Information Rate (kbit/s) is not greater than the expected
maximum rate of transmitting the flow.

You can set Peak Information Rate (kbit/s) of a CAR only after creating the CAR.
7.60 Maximum Burst Size (kbyte) (CAR Configuration)

Description
The Maximum Burst Size (kbyte) (CAR Configuration) parameter specifies the maximum
excessive data volume of a flow, which can be transmitted within a certain period.

After the CAR is enabled and bound with a flow, if the burst data volume of the flow is greater
than the value of Maximum Burst Size (kbyte), the excessive data is discarded.
Values
0-32 0 kbyte
Based on the actual requirement of QoS, you can set a proper value for Maximum Burst Size
(kbyte).
Generally, the value of Maximum Burst Size (kbyte) is not greater than the size of burst data
flow to be transmitted.

You can set Maximum Burst Size (kbyte) of a CAR only after creating the CAR.

System
7.61 CoS ID (CoS Configuration)

Description
The CoS ID (CAR Configuration) parameter specifies the ID of a class of service (CoS). When
a CoS is created, it needs to be specified with a unique CoS ID.

Values
The value ranges for each type of board is as follows:
1-65535 1
You can set this parameter to any value in the value range as required. A CoS maps a CoS ID.

None.
7.62 CoS Type (CoS Configuration)

Description
The CoS Type (CoS Configuration) parameter specifies the type of CoS of the flow in the
Ethernet data board. This parameter decides the method adopted to classify the flow in the
Ethernet data board.

If CoS Type is set incorrectly, packets cannot be correctly dispatched to a proper queue.
Values
Simple, VLAN priority, DSCP, IPTOS Simple

System
Value Description
Simple Assigns the CoS Priority based on the flow.
VLAN priority Assigns the CoS Priority based on the VLAN priority.
DSCP Assigns the CoS Priority based on the DSCP field in the IP
packet header.
IPTOS Assigns the CoS Priority based on the TOS field in the IP
packet header.
Based on the requirements of QoS, set a proper value for CoS Type.

None.
7.63 CoS Priority (CoS Configuration)

Description
The CoS Priority (CoS Configuration) parameter classifies packets into different levels based
on the CoS type, and maps these packets into different CoS priorities. The packets of higher
priorities are first processed.

The packets of higher priorities are transmitted before those of lower priorities. Moreover, better
service quality is available.
Values
For the CoS of the Simple type, follow Table 7-5 to set a simple CoS Priority.
Table 7-5 CoS priority of the simple type
CoS Parameter Value Range of CoS Value Range of Default Value of

Parameter CoS Priority CoS Priority
Invalid Invalid 0-7 0
For the CoS of the VLAN Priority type, follow Table 7-6 to set the mapping from VLAN
Priority to CoS Priority.

System
Table 7-6 CoS priority of the VLAN Priority type

User priority in 0-7 0-7 The same as that of

VLAN CoS priority
For the CoS of the DSCP type, follow Table 7-7 to set the mapping from DSCP Priority to CoS
Priority.
Table 7-7 CoS priority of the DSCP type

DSCP 000000-111111 (in 0-7 0

binary)
For the CoS of the IPTOS type, follow Table 7-8 to set the mapping from IPTOS Priority to
CoS Priority.
Table 7-8 CoS priority of the IPTOS type
CoS Value Range of Value Range of CoS Default Value of

Parameter CoS Parameter Priority CoS Priority
IPTOS 0000-1111 (in 0-7 0

binary)
Based on the requirements, you can map the packets into different queues by setting CoS
Priority.
If CoS Type is set to VLAN Priority, IPTOS or DSCP, generally, you can map the packets
into the proper CoS Priority according to the priority information contained in the packets.
At the application layer, if a service (for example, VOIP, video conference, video conferencing
call, and video on demand) has higher requirements for QoS, set a higher priority for the service
to get better bandwidth and service guarantee. To ensure good bandwidth multiplexing, be sure
to avoid a larger ratio of real-time services in the network. For a service (for example, Internet
access, E-Mail, and FTP) that has lower requirements for QoS, set a lower priority for the service
to provide better bandwidth sharing and contention mechanism.

None.

System
7.64 Port Priority (Link Aggregation)

Description
The Port Priority (Link Aggregation) parameter specifies the priority of the ports in the link
aggregation group of the LACP protocol. The port priority can be set. It indicates the priority
level of a port to be aggregated. If a port is of higher priority, this port is preferred to carry the
services. If a link aggregation group (for example, manual aggregation group) does not run the
LACP protocol, it does not take effect after the port priority is set.

If other conditions (for example, port rate, and port working mode) are the same, a port of higher
priority is preferred to carry the services.
Values
0-65535, in step length of 1 32768
If the value of Port Priority is smaller, the priority is higher.
When using a port to carry the services, set Port Priority to a smaller value. Otherwise, set Port
Priority to a greater value.

The member port state in the link aggregation group is decided according to these parameters,
such as port working mode, port working rate, whether the port receives LACP packets, port
priority, and LAG priority.
7.65 System Priority (Link Aggregation)

Description
The System Priority (Link Aggregation) parameter specifies the priority level of a link
aggregation group. It may affect the working state of the member ports in the link aggregation
group.

When the link aggregation groups at the local and opposite ends negotiate with each other by
sending LACP packets, they can get the system priority of the link aggregation groups from each
other. The result selected at the end of higher priority is taken as the result for the two ends. If

System
the system priority of the link aggregation group is the same at the two ends, the system MAC
addresses are compared. A MAC address is used if it is of lower value.
If the value of System Priority is smaller, the system priority of the link aggregation group is
higher.
Values
0-65535, in step length of 1 32768
To take the result selected by the static link aggregation group as the actual value, set System
Priority to a smaller value.

The member port state in the link aggregation group is decided according to these parameters,
such as port working mode, port working rate, whether the port receives LACP packets, port
priority, and system priority.
7.66 Status (Link Aggregation)

Description
The Status (Link Aggregation) parameter specifies the state, which is derived from logical
computation, of each member ports in a link aggregation group.

When a port is not configured with services, this port can be added to a link aggregation group.
If this port is in service in this link aggregation group, this port can share the service. If this port
is out of service in this link aggregation group, this port cannot share the service.
When a port is already configured with services, this port cannot be added to a link aggregation
group and cannot share the service.
Values
Unknown, In Service, Out of Service Unknown
Value Description
Unknown Indicates that the link aggregation group is not queried.

System
Value Description
In Service Indicates that the port can carry the service.
Out of Service Indicates that the port cannot carry the service.
This parameter is used for query only. No rules are provided for selecting a value.

l For static link aggregation, the LACP protocol is used. The member port state in the link
aggregation group is decided by these parameters, such as port working mode, port working
rate, port priority, and link aggregation group priority.
l For manual link aggregation, the LCAP protocol is not used. The member port state in the
link aggregation group is not related to these parameters, such as port working mode and
port working rate.
7.67 Load Sharing(Ethernet Link Aggregation)

Description
The Load Sharing parameter specifies the load sharing mode of an aggregation group.

Different load sharing modes have different effects. In load sharing mode, the ports in the
aggregation group can share the service. In load non-sharing mode, only one port in the
aggregation group can carry the service and the other port provides protection.
Values
Sharing, Non-Sharing Sharing
Value Description
Sharing Indicates that the ports in the aggregation group share the
service.
Non-Sharing Indicates that the ports in the aggregation group do not share
the service. Only one port in the aggregation group carries the
service.

System
If the bandwidth needs to be increased and several ports need to be enabled to share the service,
select the load sharing mode. If only one port needs to carry the service and protection is required
for this port, select the load non-sharing mode.
7.68 Protocol Enabled (Spanning Tree)

Description
Protocol Enabled (Spanning Tree) indicates whether the spanning tree protocol is enabled on
the VB.

After the protocol is enabled, and when the computation of the spanning tree is performed
according to the protocol type (STP/RSTP), the network topology changes and services are
interrupted temporarily.
Values
The user can set this parameter according to the actual service requirement.

This parameter can be set only when the VB is created and Protocol Type is selected.
Related Information
The rapid spanning tree protocol (RSTP) can realize all the functions of the spanning tree. Similar
to the STP, the RSTP avoids temporary loops. Different from the STP, the RSTP shortens the
time delay at the ports from blocking to forwarding, restores the network connectivity more
rapidly, and provides better services.
7.69 Protocol Type (Spanning Tree Protocol)

Description
Protocol Type (Spanning Tree) indicates that the Ethernet data board of the OptiX OSN
equipment supports two spanning tree protocols, that is, the spanning tree protocol (STP) and
the rapid spanning tree Protocol (RSTP).

System
l The STP is a Layer 2 management protocol that avoids Layer 2 loops by selectively
blocking redundant network links and supports the link backup.
l The RSTP develops from the STP and shortens the convergence time.

If this parameter is changed incorrectly, a network topology oscillation may occur and services
are severely affected.
Values
STP, RSTP RSTP
The RSTP and STP can be configured at the same time. The RSTP is compatible with the STP.
It is recommended that you use the default value RSTP.

None.
7.70 Priority (Bridge Parameters)

Description
VB Priority (Bridge Parameters) indicates the fixed parameters of the bridge, used for
selecting the role of the bridge and computing the topology of the spanning tree. As the value
of the parameter decreases, the VB priority increases and the bridge is more likely to be selected
as a root bridge.

Changing the value of Priority may affect the selection of a root bridge, which may finally affect
the entire network topology.
Values
0-65535, in step length of 4096 32768
Set this parameter according to what role the user expects the bridge to play in the spanning tree
topology.

System

None.
7.71 Max Age(s)

Description
The Max Age(s) parameter specifies the maximum life cycle of the configuration message. A
configuration message contains the message aging time and maximum aging time of the
message. The maximum life cycle of the configuration message is equivalent to the maximum
aging time of the message.

If the message aging time exceeds the maximum aging time of the message, the received message
is discarded and the port that receives the message becomes a designated port.
Values
6-40 20 s
When you set the value of this parameter, ensure that the following requirement is met:
2 x (Hello Time + 1) ≤ Max Age ≤ 2 x (Forward Delay - 1)

This parameter is related to the Hello Time and Forward Delay parameters. For details, refer
to the principles for setting these parameters.
7.72 Hello Time(s) (Spanning Tree)

Description
The Hello Time(s) parameter specifies the transmission period of the message.
The bridge time consists of the following parts: forward delay of the bridge, handshake time of
the bridge, maximum bridge aging time, and message aging time (0). The Hello Time parameter
is equivalent to the bridge handshake time.

This parameter ensures the stable operation of the STP.

System
Values
1-10 2 s
2 x (Hello Time + 1) ≤ Max Age ≤ 2 x (Forward Delay - 1)

This parameter is related to the Max Age and Forward Delay parameters. For details, refer to
the principles for setting these parameters.
7.73 Forward Delay(s) (Spanning Tree)

Description
The Forward Delay(s) parameter specifies the delay of the port state migration.
This parameter is actually a timer that is used by the ports in the listening state and in the learning
state to control the migration from the listening state to the learning state and the migration from
the learning state to the forwarding state. The timer is started when the port enters the listening
state. When the timer expires, the port automatically migrates to the learning state and the timer
is started again. When the timer expires the second time, the port automatically migrates to the
forwarding state and the timer is stopped.

The restoration time of the service from the learning state to the forwarding state is affected.
Values
4-30 15 s
2 x (Hello Time + 1) ≤ Max Age ≤ 2 x (Forward Delay - 1).

This parameter is related to the Hello Time and Max Age parameters. For details, refer to the
principles for setting these parameters.

System
7.74 TxHoldCount(per second) (Spanning Tree)

Description
The TxHoldCount(per second) parameter enables the transmission state machine of the port
to specify the maximum transmission rate of the BPDU packet.

This parameter ensures that the number of the BPDU packets transmitted within a period of hello
time does not exceed the preset value.
Values
1-10 times/s 6
Set this parameter according to the actual requirement of the user. It is recommended that you
use the default value.
7.75 Root Path Cost

Description
Each bridge has the root path cost. The root path cost of the root bridge is equal to 0. In the case
of non-root bridges, the root path cost of each bridge is equal to the sum of path cost values of
each port on the other bridges that a non-root bridge passes when the bridge receives the frame
from the root bridge along the minimum cost path. The path cost of each port can be managed.
The network segment in each LAN has the root path cost. The root path cost of the network
segment is equal to the root path cost of the bridge whose cost is the smallest among all the
bridges that are connected to the network segment through the bridge ports. In this case, the
bridge whose cost is the smallest is selected as the designated bridge. If the root path cost values
of two or more bridges are the same and the smallest, the bridge with a higher priority is selected
as the root bridge.
In the case of non-root bridges, the root path cost of each bridge is equal to the sum of path cost
values of each port on the other bridges that a non-root bridge passes when the bridge receives
the frame from the root bridge along the minimum cost path. That is, the value of the root path
cost is the sum of the path cost values of all bridges.

The root path cost can determine the designated bridge and the service flow in the STP.

System
Values
Based on the protocol, the value of this parameter is calculated according to the network
topology. This parameter is used for querying.
There are no principles for setting the value of this parameter because this parameter is used for
querying.
7.76 Hold Count (Spanning Tree)

Description
The Hold Count parameter indicates the maximum number of BPDUs that are actually
transmitted within a period of hello time.

The system is not affected because this parameter is used to check the counter of the BPDU
packet.
Values
This parameter is used for querying.
There are no principles for setting the value of this parameter because this parameter is used for
querying.
7.77 Port ID
Description
The Port ID parameter contains 16 bits, which show the port priority and the unique port number
in the bridge. The first eight bits indicate the port priority, and the later eight bits indicate the
port number. The port ID represents the priority in the spanning tree. If the value of the port ID
is smaller, the port priority in the bridge is higher. To enable the RSTP to be compatible with
the STP, the port priority is represented by eight bits, of which the later four bits are 0 for easy
management.

This parameter is for query only. The system is not affected.
Values
The parameter value is in decimal system. For example, Port ID = 32769.

System

You can change the parameter value by setting the port priority. In this case, however, the
topology of the spanning tree may be rearranged.
If the port priority is smaller, the port ID is smaller. When the port priorities are the same, the
port ID is smaller if the port number is smaller.
7.78 Designated Path Cost

Description
The Designated Path Cost parameter is applicable to the port and is used for the state machine
calculation of the spanning tree. Based on the port path cost, you can calculate the root path cost
of the port of the switch. The root path cost is equal to 0 in the case of a root bridge. In the case
of other bridges, the root path cost of the bridge refers to the path cost from the root bridge to
this bridge. The root path cost is the sum of the minimum root path cost of the port on this bridge
and the path cost of this port. The path cost of each port can be set through the management
module. Table 7-9 shows the recommended values of the port path cost. The values are generally
related to the MAC type and transmission rate.
Table 7-9 Recommended values of the port path cost
Parameter Link Speed Recommende Recommende Range

d value d range
Path Cost <=100 Kb/s 200000000 20000000-2000 1-200000000

00000
1 Mb/s 20000000 2000000-20000 1-200000000

0000
10 Mb/s 2000000 200000-200000 1-200000000

00
100 Mb/s 200000 20000-2000000 1-200000000
1 Gb/s 20000 2000-200000 1-200000000
10 Gb/s 2000 200-20000 1-200000000
100 Gb/s 200 20-2000 1-200000000
1 Tb/s 20 2-200 1-200000000
10 Tb/s 2 1-20 1-200000000

This parameter affects the calculation of the root path cost based on the STP and hence affects
the service flow in the spanning tree.

System
Values
1-65535 0
Value Description
1-65535 Indicates the cost required by the transmission of the bridge port.
If the port rate is greater, the designed path cost is smaller. It is recommended that you use the
default value.
7.79 Designated Root Bridge Priority

Description
The Designated Root Bridge Priority parameter indicates the priority of the root bridge that
is selected based on the STP. The selection is based on the bridge IDs in a network. A bridge
ID consists of the priority and MAC address of the bridge. The bridge whose ID is the smallest
is selected as the root bridge in this network.

This parameter is used for querying. It indicates the priority of the current root bridge and may
change in the case of a spanning tree topology change.
Values
0-65535 32768
There are no specific principles for setting the value of this parameter because this parameter is
used for querying.

System
7.80 Designated Bridge Priority(Spanning Tree)

Description
The Designated Bridge Priority parameter indicates the priority of each bridge during the
selection of the root bridge based on the STP. The bridge priority is a part of the bridge ID. A
bridge ID consists of the bridge priority and MAC address of the bridge. The bridge whose ID
is the smallest is selected as the root bridge in the network.

If the priority of a bridge is higher, the probability is higher that the bridge is selected as the root
bridge.
Values
0-61440 32768
If the value of the parameter is smaller, the priority of the bridge is higher. Set this parameter
according to the actual network condition.
7.81 Designated Bridge MAC Address (Spanning Tree)

Description
The Designated Bridge MAC Address parameter indicates the MAC address of a bridge.
To ensure that the bridge protocols operate normally, the following requirements should be met:
l The multicast MAC address must be unique and be identified by all the bridges in the LAN.
The multicast MAC address identifies the protocol entities of a bridge that is connected to
different and individual physical network segments.
l Each bridge has a unique ID in the entire LAN.
l Ports on a bridge have port IDs, which are different from each other. Ports IDs of different
bridges are different. The values of these IDs can be assigned independently. The values
can also be used by other bridges.
l Each bridge must provide the values of the parameters that are described previously or
provide the mechanism for assigning values for these parameters.

The MAC address of a bridge affects the priority of the bridge.

System
Values
unicast mac address 00-00-00-00-00-00
It is recommended that you use the default value.
7.82 Edge Port Status (Spanning Tree)

Description
The Edge Port Status parameter specifies whether a bridge port is an edge port. Edge ports are
directly connected to the terminal equipment and are no longer connected to any bridges. This
parameter is important in the RSTP. The status of these ports does not affect the connectivity of
the entire network, and does not cause any loops. Hence, these ports can enter the forwarding
state without any delay after the bridge starts.

After this parameter is enabled, convergence time of the RSTP is reduced and thus the reliability
of the system is improved.
Values
Value Description
Enabled Indicates that the edge port function is enabled. In this case,
the port can enter the forwarding state directly without any
delay during the calculation process of the state machine.
Disabled Indicates that the edge port function is disabled.
The user can set this parameter according to the network topology to reduce the delay in the case
of a state migration of the network edge port.

System
7.83 Point to Point Attributes(External Ethernet Port

Attributes)
Description
The Point to Point Attributes (External Ethernet Port Attributes) parameter specifies the
mode of connecting Ethernet ports to the external equipment. According to this parameter, the
spanning tree protocol (STP) decides whether to rapidly transit the port state from discarding to
forwarding.

If the connection is in shared media mode and if the port is not defined as an edge port, the STP
cannot rapidly transit the port state. After the STP updates the network topology, the service
restoration time becomes longer.
Values
Adaptive connection, Shared media, Link Adaptive connection

connection
Value Description
Adaptive connection If the port is a full-duplex port or a VCTRUNK port, and if

the port has the point-to-point attribute, the port state can be
transited rapidly.
Shared media If the port has the non-point-to-point attribute, the port state
cannot be transited rapidly.
Link connection If the port has the point-to-point attribute, the port state can
be transited rapidly.
If the port connection mode is known, select Shared media or Link connection. Otherwise,
select Adaptive connection.

None.

System
7.84 Enabling LCAS

Description
The Enabling LCAS parameter can increase or decrease the SDH network capacity without
affecting the service. The capacity is automatically decreased if a member fails, and is
automatically increased if the member recovers.

As a bidirectional protocol, the LCAS can work normally only when some bandwidth is available
in the bidirectional physical paths. If the bandwidth is available in the unidirectional physical
paths only, the LCAS may fail to correctly adjust the bandwidth.
Values
Value Description
Disabled Disables the LCAS protocol.
Enabled Enables the LCAS protocol.
You can set Enabling LCAS as required.

None.
7.85 LCAS Mode

Description
The LCAS Mode parameter specifies the sequence for the sink end to respond to the MST and
Rs_Ack messages received from the source end.


System
Values
Huawei Mode, Standard Huawei Mode

Mode
Value Description
Huawei Mode Inverts the RS_Ack message, and then transmits the MST
message.
Standard Mode Transmits the MST message, and then Inverts the RS_Ack
message.
To set the LCAS mode, follow the principles:
l If the interconnected equipment at the two ends are Huawei equipment, select Huawei
Mode.
l If Huawei equipment is interconnected to a third-party equipment, set the interconnected
equipment to the same mode according to the mode supported by the third-party equipment.

None.
7.86 Hold-Off Time (ms) (LCAS)

Description
The Hold-Off Time (ms)(LCAS) parameter is also called HO Procedure Timer Duration. It
specifies HO Procedure Timer Duration of the LCAS protocol. If the LCAS coexists with
another network-level protection scheme (for example, MSP or SNCP), you can set this
parameter to postpone the LCAS switching.

The LCAS switching tiime is affected.
For example, if both the MSP and the LCAS are available in a network, set the LCAS hold off
time to 2000 ms. If the network fails, only the MSP switching occurs, but the LCAS switching
does not occur.

System
Values
0 to 10000 (in step length of 100) 2000 ms
The User can set this parameter according to the expected hold off time of LCAS switching.

This parameter is valid only when Enabling LCAS is set to Enabled.
7.87 WTR Time (s) (LCAS)

Description
The WTR Time (s) parameter is also called WTR Procedure Timer Duration. It specifies
WTR Procedure Timer Duration of the LCAS protocol. Set this parameter to avoid impact
caused by the alarm jitter on the link status.

The fault recovery time of the LCAS protocol is affected. After the network recovers from a
fault, the LCAS protocol can recover only after a WTR duration.
Values
0 to 720 300 Second
The User can set this parameter according to the expected WTR duration of LCAS recovery.

7.88 TSD (LCAS)

Description
The TSD (LCAS) parameter specifies the B3 or BIP error status of a VCTRUNK member. TSD
stands for trail signal degrade. When this parameter is set to Enabled, and if a VCTRUNK

System
member has excessive B3 or BIP bit errors, the LCAS protocol regards that this member fails
and deletes it from the available members. If this parameter is set to Disabled, the LCAS protocol
does not monitor the status of the B3 or BIP bit errors of a VCTRUNK member.

Values
You can set whether to enable the TSD as required.

7.89 Min Members - Transmit Direction

Description
When the LCAS is enabled, the LCAS_PLCT alarm is reported if certain members in the transmit
direction fail and the number of valid members is smaller than a certain value. The Min
Members - Transmit Direction parameter specifies the certain number of the valid members
in the transmit direction.

When the LCAS is enabled, failure of certain paths does not affect the service in the case of
sufficient bandwidths. The user can set this parameter to enable the reporting of the LCAS_PLCT
alarm only when the number of the valid members in the transmit direction is smaller than a
certain value.
Values
2-256 256
Set this parameter according to the actual requirement of the user.

System
7.90 LPT
Description
The LPT parameter specifies whether the link state pass through (LPT) function is enabled. The
LPT is a technology developed by Huawei to increase the speed of the link state response.
Through the LPT protocol, the faults on the service access point and in the intermediate network
can be detected and reported.

When the LPT function is enabled, the faults on the service access point and in the intermediate
network can be detected and reported. For example, the service access point can be informed of
the fault in the intermediate network and thus can handle the fault accordingly (switch the service
to the backup link). When the LPT function is disabled, the link fault in the intermediate network
is not reported to the service access point.
Values
Yes, No No
Value Description
Yes Indicates that the LPT function is enabled.
No Indicates that the LPT function is disabled.
Set this parameter according to the actual requirement of the user. Set this parameter to Yes if
the LPT function is required.
7.91 Bearer Mode

Description
The Bearer Mode parameter specifies the frame format of the LPT protocol packet for
transmission. Three bearer modes are available, namely, GFP (HUAWEI), Ethernet, and GFP
(CSF).

System

All the equipment on the service access point and in the intermediate network should use the
same LPT bearer mode. Otherwise, the LPT function cannot work normally.
Values
GFP(HUAWEI), Ethernet, GFP(CSF) GFP(HUAWEI)
Value Description
GFP(HUAWEI) Indicates the frame format specially used by Huawei.
Ethernet Indicates the Ethernet frame format.
GFP(CSF) Indicates the standard CSF frame format.
Set this parameter according to the actual requirement of the user. Ensure that the configurations
of the two interconnected ports are consistent.
7.92 Port-Type Port Hold-Off Time (ms)

Description
The Port-Type Port Hold-Off Time (ms) parameter specifies the interval for the PORT to
transmit the LPT fault information after it receives the information.

The greater the hold-off time of the PORT, the slower is the transmission of fault information
between networks.
Values
0-10000 (in step length of 100) 0 ms

System
7.93 VCTRUNK Port Hold-off Time (ms)

Description
The VCTRUNK-Type Port Hold-off Time (ms) parameter specifies the interval for the
VCTRUNK port to transmit the LPT fault information after it receives the information.

The greater the hold-off time of the VCTRUNK port, the slower is the transmission of fault
information between networks.
Values
0-100000 0 ms
7.94 Protocol Enable (IGMP Snooping Protocol)

Description
IGMP Snooping is a Layer-2 multicast protocol. If the IGMP Snooping is supported, an Ethernet
board can detect the IGMP packets that are transmitted between IP multicast routers or switches
and IP multicast hosts, and then check the detected IGMP packets. After being successfully
checked, these packets are transmitted transparently. An Ethernet board retrieves the registration
information of the multicast group from the checked IGMP packets. Moreover, it configures the
relevant functions to generate route ports and multicast groups. The multicast service packets
are forwarded according to the multicast group information.
This parameter specifies whether to enable the IGMP Snooping protocol within the specified
virtual bridge (VB).

l If the IGMP Snooping protocol is enabled, the Ethernet physical port captures and analyzes
the received IGMP packets. Then the Ethernet physical port registers the multicast
information to generate the router port and the multicast group. Finally the Ethernet physical
port transparently transports the packets.
l If the IGMP Snooping protocol is disabled, the Ethernet physical port does not analyze the
received IGMP packets. Instead, the Ethernet physical port broadcasts the IGMP packets
as ordinary multicast packets.

System
Values
Value Description
Enabled If the IGMP Snooping protocol is enabled, multicast groups

and router ports can be generated.
Disabled If the IGMP Snooping protocol is disabled, multicast groups

and router ports cannot be generated.
l To create and maintain a multicast service, select Enabled.
l Otherwise, select Disabled.
7.95 Multicast Aging Time(Min)

Description
The Multicast Aging Time(Min) parameter specifies the aging time of the router port in the
multicast group. The time is learnt by the board port.
This parameter decides the valid time of the router port in the multicast group. Within the aging
time period, if the router port is learnt again, its aging time is reset. Otherwise, when the aging
time expires, the relevant router port in the multicast group is aged. After the router port is aged,
the whole multicast group is deleted if no other router ports exist in the multicast group.

The parameter value may affect the forwarding efficiency of the EVPLAN service.
l If the aging time is extremely long, and if the multicast MAC address table in the board
fails to be updated in time, the board forwards the service packets incorrectly.
Consequently, the forwarding efficiency is decreased.
l If the aging time is extremely short, the multicast MAC address table may be updated
rapidly. Moreover, a great number of received multicast service packets fail to be found in
the MAC address table. Consequently, the board broadcasts these data packets to all the
ports. As a result, the forwarding efficiency is also decreased.

System
Values
1-120, in step length of 1 8 Min
Generally, select the default value, unless otherwise specified. Otherwise, set the value according
to the requirements. Do not set the value beyond the range allowed by the board.

None.
7.96 Frames to Send

Description
Frames to Send indicates the number of test packets to be transmitted. With this parameter
enabled, the system transmits a test packet at the intervals of certain period of time until the
number of transmitted test packets reaches the specified value.

Values
0-255 0 Unit
The user can set the number of test packets to be transmitted as required.

This parameter is valid only when Send Mode is set to Burst Mode.
7.97 Status
Description
Status indicates the transmit status of the current test frames at the port. This parameter is
displayed as the current test status after you configure Send Mode and Frames to Send and
then click Apply.

System

Values
Sending, Finished Sending -
Value Description
Sending Indicates that the port is currently transmitting the test frames.
Finished Sending Indicates that the port finishes transmitting the test frames.
None.

None.
7.98 Set Frame Count

Description
Set Frame Count indicates the number of test frames that are transmitted by the VC trunk port
in the Ethernet test. This parameter value is accumulative. The value indicates the total number
of test frames that are transmitted from last time when the parameter value is cleared to this time
when the value is queried.

This parameter is for query only and does not affect the system operation.
Values
For example, the parameter value 5indicates that the port transmits five test frames.
None.

System

None.
7.99 Received Response Test Frame Count

Description
Received Response Test Frame Count indicates the number of response test frames that are
received by the VC trunk port in the Ethernet test. This parameter value is accumulative. The
value indicates the total number of response test frames that are received from last time when
the parameter value is cleared to this time when the value is queried.

Values
For example, the parameter value 5indicates that this port receives five response test frames.
None.

None.
7.100 Test Frames to Receive

Description
Test Frames to Receive indicates the number of test frames that are received by the VC trunk
port in the Ethernet test. This parameter value is accumulative. The value indicates the total
number of test frames that are transmitted from last time when the parameter value is cleared to
this time when the value is queried.

Values
For example, the parameter value 5indicates that the port receives five test frames.
None.

System

None.
7.101 Send Mode (Ethernet Test)

Description
Send Mode(Ethernet Test) is used to set the test frame and the transmit mode of the test frame.
The test frame is used for simulating packet transmission to check whether the link is normal.

Values
Disabled, Burst Mode, Continue Mode Disabled
Value Description
Disabled Indicates the test is not performed.
Burst Mode Indicates that the system transmits a test frame every one
second. The test ends after a specified number of test frames
are transmitted.
Continue Mode Indicates that the system continuously transmits test frames
with a frequency of 1 frame per second.
Set this parameter according to the requirements of the test.
l To perform the test continuously, set the parameter to Continue Mode.

l To stop the test, set the parameter to Disabled.

None..

System
7.102 Call Waiting Time(s)

Description
The Call Waiting Time(s) parameter specifies the timeout period of searching an orderwire
route. If the period of searching an orderwire route exceeds the specified value, the orderwire
phone changes to the busy tone status.

Values
1-9 9 s
For all the network elements (NEs) that communicate with each other over the orderwire phone,
this parameter must be set to the same value.
l If the number of NEs is less than 30, usually, set the value to 5 seconds.
l If the number of NEs is not less than 30, usually, set the value to 9 seconds.
Generally, set it to the default value (namely, 9 seconds).
7.103 Conference Call

Description
The Conference Call parameter specifies the phone numbers of networkwide orderwire calls.

Values
100-99999999 999

System
l For orderwire conference calls on each node of the same subnet, the phone number must
be the same.
l The length of an orderwire conference call number can be set as required. The value range
is 3-8.
l The length of an orderwire conference call number must be consistent with that of the
addressing call number.
OptiX OSN 550 equipment does not support this parameter.

None.
7.104 Phone
Description
The Phone parameter specifies the phone numbers of orderwire addressing calls. An addressing
call refers to a point-to-point call.

Values
100-99999999 101
l The phone numbers of orderwire addressing calls cannot be duplicate within the same
subnet.
l The length of an orderwire call number can be set as required. The value range is 3-8.
Within the same orderwire network, the length of orderwire call numbers must be consistent
for each node.
l The length of phone numbers used to make orderwire addressing calls must be consistent
with that of conference call numbers.
NOTE
OptiX OSN 550 equipment only supports Phone 1.

If the length of an orderwire phone number is set to another value, the orderwire addressing call
number is changed to the default phone number that maps the length.

System
For example, if the length of a phone number is set to contain three digits, the addressing call
number is changed to the default number 101. If the length of the phone number is set to contain
four digits, the addressing call number is changed to the default number 1001, and the rest may
be deduced by analogy.
7.105 Available Orderwire Port

Description
The Available Orderwire Port parameter specifies whether the optical interface is used to make
orderwire calls.

Values
Available Orderwire Port Bid-BidType-PortID
Value Description
Bid-BidType-PortID Indicates the available optical interface of a board in a slot,

which is used to set orderwire calls.
l Bid indicates the slot number of the board used to set
orderwire calls.
l BidType indicates the name of the board used to set
orderwire calls.
l PortID indicates the number of the optical interface on the
board used to set orderwire calls.
None.

None.

System
7.106 No.(F1 Data Port)

Description
The No. (F1 Data Port) parameter specifies the numbers of the F1 data ports that have the same
direction.

Values
1-88 -
None.

None.
7.107 Data Channel (F1 Data Port)

Description
The Data Channel (F1 Data Port) parameter specifies the uplink and downlink ports that pass
through the F1 data.

After the data channel is cancelled, the services that pass through the F1 data port are interrupted.
Values
F1, Bid-BidType-PortID -

System
Value Description
F1 Indicates the F1 data port of the NE.
Bid-BidType-PortID Indicates a port that can be used to set a slot of the F1 data
port.
When using the F1 data port, you need to configure its route. That is, set the 64 Kbit/s data being
added to or dropped from the NE, or passing through the NE.

You can correctly set the F1 data ports that have the same direction only when the F1 port is not
set to Transparent ECC Overhead Transmission.
7.108 Overhead Byte (Broadcast Data Port)

Description
The Overhead Byte (Broadcast Data Port) parameter specifies the number of the overhead
bytes, which are used to transmit orderwire broadcast data services, in the SDH frame header.

Values
SERIAL1, SERIAL2, SERIAL1

SERIAL3, SERIAL4
Value Description
SERIAL1 Indicates the S1 byte in the SDH frame header.

System
Select the value according to the configuration.

If the S1 byte, the S2 byte, the S3 byte, the S4 byte, or an optical interface is set to transparently
transmit DCC overhead, the broadcast data port may fail to be set.
7.109 Working Mode (Broadcast Data Port)

Description
The Working Mode (Broadcast Data Port) parameter specifies the working mode of the local
interface at which broadcast data services are added or dropped.

Values
Value Valid Values
RS232 RS232
Value Description
RS232 Indicates an asynchronous transmission mode, in which no

handshake signal is available. An NE operating in RS232
mode can communicate with an NE operating in RS232 or
RS422 mode directly; in this case, data transmission is
transparent and the maximum rate is 19.2 kbit/s.
None.

None.

System
7.110 Broadcast Data Source (Broadcast Data Port)

Description
The Broadcast Data Source (Broadcast Data Port) parameter specifies the source of the
orderwire broadcast data service.

Values
No Data, SERIALx, Bid- -

BidType-PortID
Value Description
No Data Clears all the broadcast data services.
SERIALx Indicates the local broadcast data port.

For example, SERIAL1.
Bid-BidType-PortID Indicates a port that is used to set a slot of the F1 data port.

If the S1 byte, the S4 byte, or an optical interface is set to transparently transmit DCC overhead,
the broadcast data service may fail to be set.
7.111 Broadcast Data Sink (Broadcast Data Port)

Description
The Broadcast Data Sink (Broadcast Data Port) parameter specifies the sink of the orderwire
broadcast data service.

System

Values
SERIALx, Bid-BidType- -
PortID
Value Description
SERIALx Indicates the local broadcast data port,

for example, SERIAL1.
Bid-BidType-PortID Indicates a port that is used to set a slot of the F1 data port.

If the S1 byte, the S4 byte, or an optical interface is set to transparently transmit DCC overhead,
the broadcast data service may fail to be set.
7.112 External Clock Output Mode When 2M Output

Synchronous Source Is Invalid
Description
The External Clock Output Mode When 2M Output Synchronous Source Is Invalidparameter is
used to specify an action to control the output mode of external clock source when all the clock
sources in the 2M phase-locked source priority table become invalid or when the clock quality
of the selected source is inferior to the output quality threshold of external clock source.


System
Values
Synchronization Quality Shut off

Unavailable, Output AIS,
Shut off
Parameter Description
Synchronization Quality Indicates that the synchronous source is unavailable when the
Unavailable S1 byte contains 0x0f.
Output AIS Indicates that all "1"s signal is sent.
Shut off Indicates that the output is shut down.
In actual application, this parameter can be set according to the requirements of the opposite NE
that connects to the specific external clock. By default, this parameter is set to Shut off.

None.
Related Information
None.
7.113 External Clock Output Mode

Description
The External Clock Output Mode parameter is used to set the output mode of the external
clock source to 2 Mbit/s or 2 MHz.

Modifying the output mode of the external clock source may result in the switching of the clock
sources, which may bring bit errors to the service.

System
Values
2 MHz, 2 Mbit/s 2 Mbit/s
Value Description
2 MHz Indicates that the output mode of the external clock source is
set to 2 MHz. That is, the external clock source outputs 2 MHz
clock signals.
2 Mbit/s Indicates that the output mode of the external clock source is
set to 2 Mbit/s.
The input mode of the two channels of external clock signals can be set to 2 MHz or 2 Mbit/s.
The default input mode is 2 Mbit/s. In actual application, make sure that the output mode matches
the input mode on the receive end.

None.
Related Information
None.
7.114 External Clock Output Timeslot

Description
The External Clock Output Timeslot parameter is used to set the output timeslot for the S1
byte of the external clock source. The external clock source transmits the S1 overhead byte
through certain timeslots. After starting the SSM protocol, make sure that the timeslot for
receiving the S1 byte is consistent with the timeslot for transmitting the S1 byte so that the S1
byte can be received correctly.

When the SSM protocol is enabled on the NEs, setting the S1 byte may result in the switching
of the clock sources. This may bring bit errors to the service when clock jitters occur.

System
Values
SA4, SA5, SA6, SA7, SA8, All versions

All versions
Value Description
SA4 Indicates that the S1 byte is transmitted through the SA4

timeslot of the external clock port.

timeslot of the external clock interface.



All versions Indicates that the S1 byte is transmitted through all timeslots
of the external clock interface.
None.

This parameter can be set only when the External Clock Output Mode parameter is set to 2
Mbit/s.
Related Information
None.
7.115 External Source Output Threshold

Description
The External Source Output Threshold parameter is used to set the output quality threshold
of the external clock source. When the output quality of the external clock source is inferior to
the threshold, the action specified for 2M phase-locked source failure is invoked to control the

System

Values
Threshold Disabled, Not Inferior to G. Threshold Disabled

813 SETS Signal, Not Inferior to G.812
Local Clock Signal, Not Inferior to G.
812 Transit Clock Signal, Not Inferior
to G.811 Clock Signal
Value Description
Threshold Disabled Indicates that the external source quality threshold is

disabled.
Not Inferior to G.813 SETS Signal Indicates that the external clock source becomes
invalid when its output quality is inferior to the G.813
signal.
Not Inferior to G.812 Local Clock Indicates that the external clock source becomes
Signal invalid when its output quality is inferior to the G.812
local clock signal.
Not Inferior to G.812 Transit Clock Indicates that the external clock source becomes
Signal invalid when its output quality is inferior to the G.812
transit office clock signal.
Not Inferior to G.811 Clock Signal Indicates that the external clock source becomes
invalid when its output quality is inferior to the G.811
signal.
The output quality of the external clock source should not be inferior to the specified quality
threshold. Therefore, the quality threshold should be set to a value that is inferior to or equal to
the output clock quality level.

This parameter is valid only when the Protection Status parameter is set to Start Standard
SSM Protocol.
Related Information
None.

System
7.116 2M Phase-Locked Source Fail Condition

Description
The 2M Phase-Locked Source Fail Condition parameter is used to set the failure condition of
the 2M phase-locked source.

Values
No Failure Condition, AIS, No Failure Condition

LOF, AIS OR LOF
Value Description
No Failure Condition Indicates that no failure condition is set. The 2M phase-lock

source remains valid when an AIS or LOF alarm of the
external clock signal occurs.
AIS Indicates that the failure condition is set to AIS. The 2M

phase-lock source becomes invalid when an AIS alarm of
external clock signal occurs.
LOF Indicates that the failure condition is set to an LOF alarm. The
2M phase-lock source becomes invalid when an LOF alarm
of external clock signal occurs.
AIS OR LOF Indicates that the failure condition is set to an AIS alarm or
LOF alarm. The 2M phase-lock source becomes invalid when
an AIS or LOF alarm of external clock signal occurs.
Failure condition can be set as required.

None.

System
Related Information
None.
7.117 2M Phase-Locked Source Fail Action

Description
The 2M Phase-Locked Source Fail Action parameter is used to specify the action to be invoked
in the case of 2M phase-locked source failure. When the reference clock signal for locking
external clock output is invalid or inferior to the threshold, the specific action is invoked to
control the external clock output by either shutting down the output or inserting an AIS alarm.

Values
Shut Down Output, Send AIS, Shut Down Output

2M Output S1 Byte
Unavailable
Value Description
Shut Down Output Indicates that the output of external clock signal is shut down.
Send AIS Indicates that the external clock sends all "1"s signals.
2M Output S1 Byte Indicated that the S1 byte sent by the external clock is
Unavailable unavailable. That is, the external clock sends 0x0f.
When the 2M phase-locked source is invalid, output action can be set as required. When the
External Clock Output Mode parameter is set to 2 MHz, the output of external clock signal
is shut down no matter what action is set.

None.
Related Information
None.

System
7.118 Clock Source Threshold

Description
The Clock Source Threshold parameter indicates the lower quality threshold of 2M external
clock source. When the clock quality level of the external clock source that is selected from the
2M phase-locked source priority table is inferior to the threshold, the 2M phase-locked source
becomes invalid, and the action specified for 2M phase-locked source failure is invoked to
control the external clock source output.

Values
No Threshold Value, G.813 No Threshold Value

SETS Signal, G.812 Lock Clock
Signal, G.812 Transit Clock
Signal, G.811 Clock Signal
Value Description
No Threshold Value Threshold disabled
G.813 SETS Signal Indicates that the lower threshold is not inferior to the
G.813 SETS signal.
G.812 Lock Clock Signal Indicates that the lower threshold is not inferior to the
G.812 lock clock signal.
G.812 Transit Clock Signal Indicates that the lower threshold is not inferior to the
G.812 transit clock signal.
G.811 Clock Signal Indicates that the lower threshold is not inferior to the
G.811 clock signal.
In actual application, the output quality threshold of external clock source should be determined
according to the quality information about the NE clock and the opposite NE.

None.

System
Related Information
None.
7.119 AIS Alarm Generated

Description
The AIS Alarm Generated parameter is used to specify whether an AIS alarm is a condition
for triggering the switching of clock sources.

Values
Yes, No No
Value Description
Yes Indicates that an AIS alarm is the sufficient condition to

trigger clock source switching.
No Indicates that an AIS alarm is not a condition for triggering

clock source switching.
It is recommended to set the AIS alarm as the condition for triggering clock source switching
in actual application to ensure system performance.

None.
Related Information
None.

System
7.120 B1 BER Threshold-Crossing Generated

Description
The B1 BER Threshold-Crossing Generated parameter is used to specify whether a B1 BER
threshold-crossing alarm is a condition for triggering clock source switching. B1 BER
Threshold-Crossing alarm is an index for measuring the performance of clock source signals.

Values
Yes, No No
Value Description
Yes Indicates that a B1 BER threshold-crossing alarm is the

sufficient condition for triggering clock source switching.
No Indicates that a B1 BER threshold-crossing alarm is not the

condition for triggering clock source switching.
A B1 BER threshold-crossing alarm indicates that the transmitted signal and the clock in the
signal are being interfered. Therefore, this parameter can be set as a condition for triggering
clock source switching in actual application to ensure system performance.

None.
Related Information
None.

System
7.121 B2-EXC Alarm Generated

Description
The B2-EXC Alarm Generated parameter is used to specify whether a B2-EXC alarm is a
condition for triggering clock source switching. B2-EXC alarm is an index for measuring the
performance of clock source signals.

Values
Yes, No No
Value Description
Yes Indicates that a B2-EXC alarm is the sufficient condition for

triggering clock source switching.
No Indicates that a B2-EXC alarm is not the condition for

triggering clock source switching.
A B2-EXC alarm indicates that the transmitted signal and the clock in the signal are being
interfered. Therefore, this parameter can be set as a condition for triggering clock source
switching in actual application to ensure system performance.

None.
Related Information
None.

System
7.122 Higher Priority Clock Source Reversion Mode

Description
The Higher Priority Clock Source Reversion Mode parameter specifies whether to switch
from the lower-priority clock source back to the higher-priority clock source after the higher-
priority clock source is restored to normal.

If the conditions for clock source switching are excessively strict, jitters may occur in the
monitoring results of the clock status. If the auto-revertive mode is selected, the frequent
switching of clock sources may affect the service.
Values
Non-Revertive, Auto- Auto-Revertive

Revertive
Value Description
Non-Revertive Indicates that the higher-priority clock source cannot be

selected automatically after it is restored to normal.
Auto-Revertive Indicates that the higher-priority clock source is selected

automatically after it is restored to normal.
If the conditions for clock source switching are properly set and the switching of clock sources
can be guaranteed, the Auto-Revertive mode can be selected to improve clock quality.
Otherwise, the Non-Revertive mode is recommended to avoid clock jitters.

None.
Related Information
None.

System
7.123 Clock Source WTR Time

Description
The Clock Source WTR Time parameter is used to specify the wait-to-restore (WTR) time
when the Higher Priority Clock Source Reversion Mode parameter is set to Auto-
Revertive. When a clock source is restored to its valid status, the system does not regard it as a
valid source immediately but verifies the validity of the clock source in a specific period of time.
The system regards the clock source as a valid source only if the clock source remains valid
during the specific period of time. This specific period of time is called the WTR time of the
clock source.

Insufficient WTR time may result in wrong judgments on clock source restoration and clock
status jitters, which may interrupt the service.
Values
0-12 5
The WRT time is counted in minutes. The shorter the WTR time is, the faster the clock is
recovered, and the higher the average clock quality is. On the other hand, the shorter the WTR
time is, the more likely the clock jitters are caused due to unstable clock signals. Therefore, do
not set the WTR time to 0 in actual application.

The setting of the WTR time is valid only when the Higher Priority Clock Source Reversion
Mode parameter is set to Auto-Revertive.
Related Information
None.
7.124 Lock Status

Description
The Lock Status parameter indicates the lock status of a clock source in the priority table.


System
Values
Lock, Unlock Unlock
Value Description
Lock Indicates that a certain channel of clock source in the priority

table is in the lock status where the switching of clock sources
is not allowed.
Unlock Indicates that a certain channel of clock source in the priority

table is in the unlock status where the switching of clock
sources is allowed.
None.

None.
Related Information
None.
7.125 Synchronous Source

Description
The Synchronous Source parameter indicates the synchronous clock source that is being traced.
The synchronous clock source here refers to a certain clock source contained in the system clock
priority table.

Values
Clock Source in System Clock None

Priority Table

System
Value Description
Clock Source in System Indicates that the system clock priority table contains the
Clock Priority Table tributary clock sources, line clock sources, external clock
sources, and internal clock sources.
The OptiX OSN 550 does not support External Clock Source.

None.
Related Information
None.
7.126 S1 Byte Synchronization Quality Information

Description
The S1 Byte Synchronization Quality Information parameter indicates the synchronization
quality information in the S1 byte that is output by the current traced synchronous source. The
S1 byte defined by the ITUT is used to transmit the quality information about the clock sources.
It indicates the quality information of 16 types of synchronous sources with bits 5-8 of the S1
byte in the section overhead. With this quality information and certain switching protocols, the
automatic protection switching of the synchronization clock can be realized in the synchronous
network.

Values
Synchronous Source -
Unavailable, Quality Unknown,
G.811 Reference Clock, G.812
Transit Clock, G.812 Local
Clock, SDH equipment timing
source (SETS) signal

System
Value Description
Synchronous Source Indicates that the SSM protocol is disabled and the S1 byte
Unavailable synchronization quality information output by the
synchronous source is not available.
Quality Unknown Indicates that the SSM protocol is started but the S1 byte
synchronization quality information output by the
synchronous source is unknown.
G.811 Reference Clock Indicates that the SSM protocol is started and the S1 byte
synchronous source is the G.811 reference clock.
G.812 Transit Clock Indicates that the SSM protocol is started and the S1 byte
synchronous source is the G.812 transit clock.
G.812 Local Clock Indicates that the SSM protocol is started and the S1 byte
synchronous source is the G.812 local clock.
SDH equipment timing Indicates that the SSM protocol is enabled and the S1 byte
source (SETS) signal synchronization quality information output by the
synchronous source is the synchronous equipment timing
source (SETS) clock.
None.

None.
Related Information
None.
7.127 NE Clock Working Mode

Description
The NE Clock Working Mode parameter is used to set the current working mode of the system
clock to the normal, holdover or free-run mode.


System
Values
Normal Mode, Holdover Mode, Free- -

Run Mode
Value Description
Normal Mode Indicates that the NE clock works in the tracing mode. That is, the
NE clock traces and locks the working mode of its upper-level
clock.
Holdover Mode Indicates that the NE clock works in the holdover mode. That is,
in this mode, the NE clock uses the frequency information that is
stored before all timing reference signals are lost as its timing
reference.
Free-Run Mode Indicates that the NE clock works in the free-run mode. That is,
the internal oscillator works in this mode when all external timing
reference signals are lost.
None.

None.
Related Information
None.
7.128 Data Output Method in Holdover Mode

Description
The Data Output Method in Holdover Mode parameter is used to specify whether the data is
output normally or the latest data is kept when the NE clock is in the holdover mode.


System
Values
Normal Data Output Mode, Normal Data Output Mode

Keep the Latest Data
Value Description
Normal Data Output Mode Indicates the normal data output mode. The duration of this
output mode is determined by the phase lock. This data output
mode can continue for a maximum of 24 hours.
Keep the Latest Data Indicates that the latest phase-locked data is kept. This data
output mode is a forced holdover mode.
The Keep the Latest Data mode is a forced holdover mode. Therefore, the clock accuracy is not
high. In actual application, the Normal Data Output mode is recommended.

The NE clock can work in three modes: the trace, holdover, and free-run modes. This parameter
is valid only when the NE clock is working in the holdover mode.
Related Information
None.
7.129 Retiming Mode

Description
The Retiming Mode parameter specifies whether the retiming clock, tributary clock, or cross-
connect (external) clock is used.

If the downstream board that corresponds to this board provides the clock source for the
downstream NE, the selection of the user affects the precision of the downstream NE.

System
Values
Normal, Retiming Mode of Normal

Tributary Clock, Retiming
Mode of Cross-Connect Clock
Value Description
Normal Indicates that the retiming clock is not used.
Retiming Mode of Tributary Indicates that the tributary clock is used as the retiming
Clock clock.
Retiming Mode of Cross- Indicates that the cross-connect (external) clock is used as
Connect Clock the retiming clock.
Select the proper clock according to the actual networking planning of the user.
The OptiX OSN equipment supports only Retiming Mode of Tributary Clock.
This parameter is applicable to only SP3D boards.
7.130 Switching Mode (MSP)

Description
The Switching Mode parameter specifies the switching mode of the linear MSP.

Values
Single-Ended Switching, Dual- Single-Ended Switching

Ended Switching

System
Value Description
Single-Ended Switching Indicates that the transmit end continues to transmit

signals to the broken fiber after the switching occurs at
the faulty end.
Dual-Ended Switching Indicates that the transmit end does not transmit signals
to the broken fiber after the switching occurs at the
transmit end and at the receive end.
In the case of the 1+1 MSP, you can set this parameter to Single-Ended Switching or Dual-
Ended Switching. In the case of the 1:N MSP, you can set this parameter to Dual-Ended
Switching only.

System
Configuration Guide A Glossary and Acronyms
A Glossary and Acronyms
Terms and abbreviations are listed in an alphabetical order.
A.1 Numerics
A.2 A
A.3 B
A.4 C
A.5 D
A.6 E
A.7 F
A.8 G
A.9 H
A.10 I
A.11 J
A.12 L
A.13 M
A.14 N
A.15 O
A.16 P
A.17 Q
A.18 R
A.19 S
A.20 T
A.21 U
A.22 V
Issue 02 (2011-06-30) Huawei Proprietary and Confidential A-1

System
A Glossary and Acronyms Configuration Guide
A.23 W
A-2 Huawei Proprietary and Confidential Issue 02 (2011-06-30)

System
A.1 Numerics
1+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection
SNC/trail and a permanent bridge. At the source end, the normal traffic signal is
permanently bridged to both the working and protection SNC/trail. At the sink end, the
normal traffic signal is selected from the better of the two SNCs/trails. Due to the
permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic
signal to be provided.
100BASE-T IEEE 802.3 Physical Layer specification for a 100 Mb/s CSMA/CD local area network.
100BASE-TX IEEE 802.3 Physical Layer specification for a 100 Mb/s CSMA/CD local area network
over two pairs of Category 5 unshielded twisted-pair (UTP) or shielded twisted-pair
(STP) wire.
10BASE-T An Ethernet specification that uses the twisted pair cable with the transmission speed as
10 Mbit/s and the transmission distance as 100 meters.
1:N protection An architecture that has N normal service signals, N working SNCs/trails, and one
protection SNC/trail. It may have one extra service signal.
1PPS Pulse per second, which, strictly speaking, is not a time synchronization signal. This is
because 1PPS provides only the "gauge" corresponding to the UTC second, but does not
provide the information about the day, month, or year. Therefore, 1PPS is used as the
reference for frequency synchronization. On certain occasions, 1PPS can also be used
on other interfaces for high precision timing.
3R Reshaping, Retiming, Regenerating.
A.2 A
ABR Available Bit Rate
AC Alternating Current
ACAP A channel configuration method, which uses two adjacent channels (a horizontal
polarization wave and a vertical polarization wave) to transmit two signals.
Active/Standby The process in which the standby cross-connect board automatically takes the place of
switching of cross- the active one. If there are two cross-connect boards on the SDH equipment, which are
connect board in hot back-up relation of each other, the operation reliability is improved. When both
the cross-connect boards are in position, the one inserted first is in the working status.
Unplug the active board, the standby one will run in the working status automatically.
When the active cross-connect board fails in self-test, the board is pulled out, the board
power supply fails or the board hardware operation fails, the standby cross-connect board
can automatically take the place of the active one.
add/drop multiplexer Network elements that provide access to all or some 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.
ADM See add/drop multiplexer

System
Administrative Unit The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and a AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
Administrative Unit One or more administrative units occupying fixed, defined positions in an STM payload.
Group An AUG consists of AU-4s.
Administrator A user who has authority to access all the Management Domains of the product. He or
she has access to the whole network and to all the management functionalities.
Aging time The time to live before an object becomes invalid.
AIS Alarm Indication Signal
Alarm A message reported when a fault is detected by a device or by the network management
system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
Alarm automatic A function wherein an alarm generated on the device side is immediately and
report automatically reported to the NMS. After an alarm is reported, an alarm panel prompts,
and the user can view the details of the alarm.
alarm cable The cable for generation of visual or audio alarms.
alarm filtering An alarm management method. Alarms are detected and reported to the NMS system,
and whether the alarm information is displayed and saved is decided by the alarm filtering
status. An alarm with the filtering status set to "Filter" is not displayed and saved on the
NMS, but is monitored on the NE.
alarm indication A function that indicates the alarm status of an NE. On the cabinet of an NE, there are
four indicators in different colors indicating the current alarm status of the NE. When
the green indicator is on, the NE is powered on. When the red indicator is on, a critical
alarm is generated. When the orange indicator is on, a major alarm is generated. When
the yellow indicator is on, a minor alarm is generated. The ALM alarm indicator on the
front panel of a board indicates the current status of the board.
Alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure
has been detected and alarmed. It is associated with multiple transport layers.
Alarm inversion For the port that has already been configured but has no service, this function can be
used to avoid generating relevant alarm information, thus preventing alarm interference.
The alarm report condition of the NE port is related to the alarm inverse mode (not
inverse, automatic recovery and manual recovery) setting of the NE and the alarm
inversion status (Enable and Disable) setting of the port. When the alarm inversion mode
of NE is set to no inversion, alarms of the port will be reported as usual no matter whatever
the inversion status of the port is. When the alarm inversion mode of the NE is set to
automatic recovery, and the alarm inversion state of the port is set to Enabled, then the
alarm of the port will be suppressed. The alarm inversion status of the port will
automatically recover to "not inverse" after the alarm ends. For the port that has already
been configured but not actually loaded with services, this function can be used to avoid
generating relevant alarm information, thus preventing alarm interference. When the
alarm inverse mode of the NE is set as "not automatic recovery", if the alarm inversion
status of the port is set as Enable, the alarm of the port will be reported.
Alarm Masking An alarm management method. Alarms that are set to be masked are not displayed on
the NMS or the NMS does not monitor unimportant alarms.

System
Alarm Severity The significance of a change in system performance or events. According to ITU-T
recommendations, an alarm can have one of the following severities: Critical, Major,
Minor, Warning.
Alarm suppression An alarm management method. Alarms that are set to be suppressed are not reported
from NEs any more.
ALS See Automatic laser shutdown
APS See Automatic Protection Switching
asynchronous Pertaining to, being, or characteristic of something that is not dependent on timing.
Asynchronous A protocol for the transmission of a variety of digital signals using uniform 53 byte cells.
Transfer Mode A transfer mode in which the information is organized into cells; it is asynchronous in
the sense that the recurrence of cells depends on the required or instantaneous bit rate.
Statistical and deterministic values may also be used to qualify the transfer mode.
ATM See Asynchronous Transfer Mode
ATPC See Automatic Transmit Power Control
attenuation Reduction of signal magnitude or signal loss, usually expressed in decibels.
AU See Administrative Unit
AUG See Administrative Unit Group
auto-negotiation An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices to
automatically exchange information over a link about speed and duplex abilities..
Automatic laser A technique (procedure) to automatically shutdown the output power of laser transmitters
shutdown and optical amplifiers to avoid exposure to hazardous levels.
Automatic Protection Capability of a transmission system to detect a failure on a working facility and to switch
Switching to a standby facility to recover the traffic.
Automatic Transmit A method of adjusting the transmit power based on fading of the transmit signal detected
Power Control at the receiver.
A.3 B
backplane An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
backup A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
BDI Backward Defect Indicator
BER See Bit Error Rate
BER tester Used to measure the bit error rate (BER) of signals during transmission.
Binding strap The binding strap is 12.7 mm wide, with one hook side (made of transparent
polypropylene material) and one mat side (made of black nylon material).

System
BIP A method of error monitoring. With even parity an X-bit code is generated by equipment
at the transmit end over a specified portion of the signal in such a manner that the first
bit of the code provides even parity over the first bit of all X-bit sequences in the covered
portion of the signal, the second bit provides even parity over the second bit of all X-bit
sequences within the specified portion, and so on. Even parity is generated by setting the
BIP-X bits so that there is an even number of 1s in each monitored partition of the signal.
A monitored partition comprises all bits which are in the same bit position within the X-
bit sequences in the covered portion of the signal. The covered portion includes the BIP-
X.
Bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
Bit Error Rate Ratio of received bits that contain errors. BER is an important index used to measure the
communications quality of a network.
BITS See Building Integrated Timing Supply
bound path A parallel path with several serial paths bundled together. It improves the data throughput
capacity.
BPDU See Bridge Protocol Data Unit
BPS Board Protection Switching
bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differs from repeaters because bridges
store and forward complete packets, while repeaters forward all electrical signals.
Bridges differ from routers because bridges use physical addresses, while routers use IP
addresses.
Bridge Protocol Data The data messages that are exchanged across the switches within an extended LAN that
Unit uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
broadcast The process of sending packets from a source to multiple destinations. All the ports of
the nodes in the network can receive packets.
Broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
BSC Base Station Controller
BSS Base Station Subsystem
Build-in WDM A function which integrates some simple WDM systems into products that belong to the
OSN series. That is, the OSN products can add or drop several wavelengths directly.
Building Integrated In the situation of multiple synchronous nodes or communication devices, one can use
Timing Supply a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
BWS Backbone WDM System

System
A.4 C
cabling The method by which a group of insulated conductors is mechanically assembled or
twisted together.
cable trough The trough which is used for cable routing in the cabinet.
captive nut See Floating nut
CAR See committed access rate
CAS Channel Associated Signaling
CBR See Constant Bit Rate
CBS Committed Burst Size
CCDP Co-Channel Dual Polarization
CCM Continuity Check Message
CDR Clock and Data Recovery
CDVT See Cell Delay Variation Tolerance
Cell Delay Variation This parameter measures the tolerance level a network interface has to aggressive
Tolerance sending (back-to-back or very closely spaced cells) by a connected device, and does not
apply to end-systems.
Centralized alarm The system that gathers all the information about alarms into a certain terminal console.
system
CES See circuit emulation service
CFM Connectivity Fault Management
Chain network One type of network that all network nodes are connected one after one to be in series.
channel A telecommunication path of a specific capacity and/or at a specific speed between two
or more locations in a network. Channels can be established through wire, radio
(microwave), fiber or a combination of the three. The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s, kb/s, Mb/s, Gb/s, and Tb/s.
CIR Committed Information Rate
Circuit A combination of two transmission channels permitting transmission in both directions
between two points.
circuit emulation A function with which the E1/T1 data can be transmitted through ATM networks. At the
service transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
CIST Common and Internal Spanning Tree
Class of Service CoS is a rule for queuing. It classifies the packets according to the service type field or
the tag in packets, and specifies different priorities for them. All the nodes in DiffServ
domain forwards the packets according to their priorities.

System
client A device that sends requests, receives responses, and obtains services from the server.
Clock Synchronization Also called frequency synchronization. The signal frequency traces the reference
frequency, but the start point does not need to be consistent.
Clock tracing The method to keep the time on each node being synchronized with a clock source in a
network.
CLP Cell Loss Priority
CM See Configuration Management
committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into Quality of Service (QoS) groups, and by which the input or output transmission rate
can be defined.
Concatenation A process that combines multiple virtual containers. The combined capacities can be
used a single capacity. The concatenation also keeps the integrity of bit sequence.
Configuration Data A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other NEs in an entire network. Configuration data is the key factor for
normal running of an entire network.
Configuration A network management function defined by the International Standards Organization
Management (ISO). It involves installing, reinitializing & modifying hardware & software.
Configure To set the basic parameters of an operation object.
congestion An extra intra-network or inter-network traffic resulting in decreasing network service
efficiency.
Connection point A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
Constant Bit Rate A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
Convergence A process in which multiple channels of low-rate signals are multiplexed into one or
several channels of required signals. It refers to the speed and capability for a group of
networking devices to run a specific routing protocol. It functions to keep the network
topology consistent.
Convergence service A service that provides enhancements to an underlying service in order to meet the
specific requirements of users.
corrugated tube Used to protect optical fibers.
CoS See Class of Service
CPU Central Processing Unit
CRC See Cyclic Redundancy Check
current alarm An alarm not handled or not acknowledged after being handled.

System
Current Performance Performance data stored currently in a register. An NE provides two types of registers,
Data namely, 15-minute register and 24-hour register, to store performance parameters of a
performance monitoring entity. The two types of registers stores performance data only
in the specified monitoring period.
Cyclic Redundancy A procedure used in checking for errors in data transmission. CRC error checking uses
Check a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
A.5 D
Data Communication A communication network used in a TMN or between TMNs to support the data
Network communication function.
Digital Data Network A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
DC Direct Current
DCC Data Communication Channel
DCD Data Carrier Detect
DCE Data Circuit-terminal Equipment
DCN See Data Communication Network
DDF See Digital Distribution Frame
DDN See Digital Data Network
Defect A limited interruption in the ability of an item to perform a required function.
Delay Measurement The time elapsed since the start of transmission of the first bit of the frame by a source
node until the reception of the last bit of the loopbacked frame by the same source node,
when the loopback is performed at the frame's destination node.
Demultiplexing A process applied to a composite signal formed by multiplexing, for recovering the
original independent signals, or groups of these signals.
Device set A collection of multiple managed devices. By dividing managed devices into different
device sets, users can manage the devices by using the U2000 in an easier way. If an
operation authority over one device set is assigned to a user (user group), the authority
over all the devices in the device set is assigned to the user (user group), thus making it
unnecessary to set the operation authority over all the devices in a device set separately.
It is recommended to configure device set by geographical region, network level, device
type, or another criterion.
Differentiated Services A marker in the header of each IP packet that prompts network routers to apply
Code Point differentiated grades of service to various packet streams. It is specified by the DiffServ
policy proposed by the IETF (Internet Engineering Task Force). This allows Internet and
other IP-based network service providers to offer different levels of service to customers.

System
DiffServ A service architecture that provides the end-to-end QoS function. It consists of a series
of functional units implemented at the network nodes, including a small group of per-
hop forwarding behaviors, packet classification functions, and traffic conditioning
functions such as metering, marking, shaping and policing.
Digital Distribution A type of equipment used between the transmission equipment and the exchange with
Frame transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,
cable patching, and test of loops that transmitting digital signals.
digital signal A signal in which information is represented by a limited number of discrete states
number of discrete states (for example, high and low voltages) rather than by fluctuating
levels in a continuous stream, as in an analog signal. In the pulse code modulation (PCM)
technology, the 8 kHz sampling frequency is used and a byte contains 8 bits in length.
Therefore, a digital signal is also referred to as a byte-based code stream. Digital signals,
with simple structures and broad bandwidth, are easy to shape or regenerate, and are not
easily affected by external interference.
Distributed Link A board-level port protection technology used to detect unidirectional fiber cuts and to
Aggregation Group negotiate with the opposite end. Once a link down failure occurs on a port or a hardware
failure occurs on a board, the services can automatically be switched to the slave board,
achieving 1+1 protection for the inter-board ports.
DLAG See Distributed Link Aggregation Group
DM See Delay Measurement
DNI See Dual Node Interconnection
domain A logical subscriber group based on which the subscriber rights are controlled.
DSCP See Differentiated Services Code Point
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
DSR Data Set Ready
DTE Data Terminal Equipments
DTR Data Terminal Ready
Dual Node DNI provides an alternative physical interconnection point, between the rings, in case
Interconnection of an interconnection failure scenario.
DVB-ASI Digital Video Broadcast- Asynchronous Serial Interface
DVMRP Distance Vector Multicast Routing Protocol
DWDM Dense Wavelength Division Multiplexing
A.6 E
E-AGGR See Ethernet aggregation
Ear bracket A piece of angle plate with holes in it on a rack. It is used to fix network elements or
components.
ECC See Embedded Control Channel
EFM Ethernet in the First Mile

System
E-LAN A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet

virtual connection).
ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at different
electrical potentials caused by direct contact or induced by an electrostatic field.
E-Line A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Embedded Control A logical channel that uses a data communications channel (DCC) as its physical layer,
Channel to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
EMS Element Management System
encapsulation A technology for layered protocols, in which a lower-level protocol accepts a message
from a higher-level protocol and places it in the data portion of the lower-level frame.
Protocol A's packets have complete header information, and are carried by protocol B
as data. Packets that encapsulate protocol A have a B header, an A header, followed by
the information that protocol A is carrying. Note that A could equal to B, as in IP inside
IP.
Enterprise System A path protocol which connects the host with various control units in a storage system.
Connection It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
Entity A part, device, subsystem, functional unit, equipment, or system that can be considered
individually.
EoD See Ethernet over Dual Domains
EPL See Ethernet Private Line
EPLAN See Ethernet virtual private LAN service
Equipment Serial A string of characters that identify a piece of equipment and ensures correct allocation
Number of a license file to the specified equipment. It is also called "equipment fingerprint".
ESCON See Enterprise System Connection
ESD See ElectroStatic Discharge
ESD jack Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or
cabinet to the insertion of ESD wrist strap.
ESN See Equipment Serial Number
Ethernet A LAN technology that uses Carrier Sense Multiple Access/Collision Detection. The
speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/
s. An Ethernet network features high reliability and is easy to maintain.
Ethernet aggregation A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual
connection).
Ethernet Alarm Group The Ethernet alarm group periodically obtain the statistics value to compare with the
configured threshold. If the value exceeds the threshold, an event is reported.
Ethernet over Dual A type of boards. EoD boards bridge the PSN and TDM networks, enabling Ethernet
Domains service transmission across PSN and TDM networks.
Ethernet Private LAN A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
service service is carried over a dedicated bridge and point-to-multipoint connections.

System
Ethernet Private Line A type of Ethernet service that is provided with dedicated bandwidth and point-to-point
connections on an SDH, PDH, ATM, or MPLS server layer network.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
private LAN service service is carried over a shared bridge and point-to-multipoint connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
private line service is carried over a shared bridge and point-to-point connections.
ETSI European Telecommunications Standards Institute
EVPL See Ethernet virtual private line
EVPLAN See Ethernet virtual private LAN service
Exercise Switching An operation to check whether the protection switching protocol functions properly. The
protection switching is not really performed.
Exerciser - Ring This command exercises ring protection switching of the requested channel without
completing the actual bridge and switch. The command is issued and the responses are
checked, but no working traffic is affected.
Extended ID The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The physical ID of an NE is comprised of the NE ID and extended
ID.
extra traffic The traffic that is carried over the protection channels when that capacity is not used for
the protection of working traffic. Extra traffic is not protected.
A.7 F
Failure If the fault persists long enough to consider the ability of an item with a required function
to be terminated. The item may be considered as having failed; a fault has now been
detected.
Fairness A feature in which for any link specified in a ring network, the source node is provided
with certain bandwidth capacities if the data packets transmitted by the source node are
constrained by the fairness algorithm.
fairness algorithm An algorithm designed to ensure the fair sharing of bandwidth among stations in the case
of congestion or overloading.
fault A failure to implement the function while the specified operations are performed. A fault
does not involve the failure caused by preventive maintenance, insufficiency of external
resources or intentional settings.
FC See Fiber Channel
FD See frequency diversity
FDDI See fiber distributed data interface
FDI Forward Defect Indicator
FE Fast Ethernet
feature code Code used to select/activate a service feature (for example, forwarding, using two or
three digit codes preceded by * or 11 or #, and which may precede subsequent digit
selection).
FEC See forwarding equivalence class

System
FEC See Forward Error Correction

fiber patch cord A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
Fiber Channel A high-speed transport technology used to build storage area networks (SANs). Fiber
channel can be on the networks carrying ATM and IP traffic. It is primarily used for
transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode
and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair
copper wires and coaxial cables. Fiber channel provides both connection-oriented and
connectionless services.
Fiber Connect A new generation connection protocol which connects the host to various control units.
It carries single byte command protocol through the physical path of fiber channel, and
provides higher rate and better performance than ESCON.
Fiber Connector A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and a optical source
(or a detector).
fiber distributed data A standard developed by the American National Standards Institute (ANSI) for high-
interface speed fiber-optic local area networks (LANs). FDDI provides specifications for
transmission rates of 100 megabits (100 million bits) per second on networks based on
the token ring network.
fiber/cable General name of optical fiber and cable. It refers to the physical entities that connect the
transmission equipment, carry transmission objects (user information and network
management information) and perform the transmission function in the transmission
network. The optical fiber transmits optical signal, while the cable transmits electrical
signal. The fiber/cable between NEs represents the optical fiber connection or cable
connection between NEs. The fiber/cable between SDH NEs represents the connection
relationship between NEs. At this time, the fiber/cable is of optical fiber type.
FICON See Fiber Connect
FIFO First In First Out
Floating nut Floating nuts (or as they are more correctly named, 'tee nuts') have a range of uses but
are more commonly used in the hobby for engine fixing (securing engine mounts to the
firewall), wing fixings, and undercarriage fixing.
Flow An aggregation of packets that have the same characteristics. On the network
management system or NE software, flow is a group of classification rules. On boards,
it is a group of packets that have the same quality of service (QoS) operation.
FLR See Frame loss ratio
Forced switch For normal traffic signals, switches normal traffic signal to the protection section, unless
an equal or higher priority switch command is in effect or SF condition exists on the
protection section, by issuing a forced switch request for that traffic signal.
Forward Error A bit error correction technology that adds the correction information to the payload at
Correction the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
forwarding equivalence A class-based forwarding technology that classifies the packets with the same forwarding
class mode. Packets with the same FEC are processed similarly on an MPLS network. The
division of FECs is flexible, and can be a combination of the source address, destination
address, source port, destination port, protocol type, and VPN.

System
FPGA Field Programmable Gate Array

frame A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements pre-
specified by the sending and receiving parties.
Frame loss ratio A ratio, is expressed as a percentage, of the number of service frames not delivered
divided by the total number of service frames during time interval T, where the number
of service frames not delivered is the difference between the number of service frames
arriving at the ingress ETH flow point and the number of service frames delivered at the
egress ETH flow point in a point-to-point ETH connection.
Free-run mode An operating condition of a clock, the output signal of which is strongly influenced by
the oscillating element and not controlled by servo phase-locking techniques. In this
mode the clock has never had a network reference input, or the clock has lost external
reference and has no access to stored data, that could be acquired from a previously
connected external reference. Free-run begins when the clock output no longer reflects
the influence of a connected external reference, or transition from it. Free-run terminates
when the clock output has achieved lock to an external reference.
frequency diversity A diversity scheme in which two or more microwave frequencies with a certain
frequency interval are used to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading.
FTP File Transfer Protocol
full-duplex A full-duplex, or sometimes double-duplex system, allows communication in both
directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line
telephone networks are full-duplex, since they allow both callers to speak and be heard
at the same time. A good analogy for a full-duplex system would be a two-lane road with
one lane for each direction.
A.8 G
Gain The difference between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
Gateway IP When an NE accesses a remote network management system or NE, a router can be used
to enable the TCP/IP communication. In this case, the IP address of the router is the
gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot
identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP
networks. An NE may have multiple IP addresses, for example, one IP address of the
network and one IP address of the Ethernet port.
Gateway Network A network element that is used for communication between the NE application layer and
Element the NM application layer.
GE Gigabit Ethernet
Generic Framing A framing and encapsulation method which can be applied to any data type. It has been
Procedure standardized by ITU-T SG15.
GFP See Generic Framing Procedure

System
GNE See Gateway Network Element

GPS Global Positioning System
GSM Global System for Mobile Communications
GTS Generic Traffic Shaping
GUI Graphic User Interface
A.9 H
half-duplex A transmitting mode in which a half-duplex system provides for communication in both
directions, but only one direction at a time (not simultaneously). Typically, once a party
begins receiving a signal, it must wait for the transmitter to stop transmitting, before
replying.
Hardware loopback A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
HDLC High level Data Link Control
HD-SDI See High Definition-Serial Digital Interface signal
HEC Header Error Control
Hierarchical Quality of A type of QoS that controls the traffic of users and performs the scheduling according
Service to the priority of user services. HQoS has an advanced traffic statistics function, and the
administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth
can be allocated reasonably through traffic analysis.
High Definition-Serial High definition video signal transported by serial digital interface.
Digital Interface signal
History alarm The confirmed alarm that has been saved in the memory and other external memories.
Historical performance The performance data that is stored in the history register or that is automatically reported
data and stored on the NMS.
HP Higher Order Path
HPT Higher Order Path Termination
HQoS See Hierarchical Quality of Service
A.10 I
IC Integrated Circuit
IDU Indoor Unit
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IF Intermediate Frequency
IGMP See Internet Group Management Protocol

System
IGMP Snooping A multicast constraint mechanism running on a layer 2 device. This protocol manages
and controls the multicast group by listening to and analyzing Internet Group
Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this
manner, the spread of the multicast data on layer 2 network can be prevented efficiently.
IMA See Inverse Multiplexing over ATM
IMA frame A control unit in the IMA protocol. It is a logical frame defined as M consecutive cells,
numbered 0 to M-l, transmitted on each of the N links in an IMA group.
Input jitter tolerance The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when
modulating the signal at an equipment input port, results in no more than two errored
seconds cumulative, where these errored seconds are integrated over successive 30-
second measurement intervals.
Intelligent power A mechanism used to reduce the optical power of all the amplifiers in an adjacent
adjusting regeneration section in the upstream to a safety level if the system detects the loss of
optical signals on the link. If the fiber is broken, the device performance degrades, or the
connector is not plugged well, the loss of optical signals may occur. With IPA,
maintenance engineers will not be hurt by the laser sent out from the slice of broken
fiber.
Interface board area The area for the interface boards on the subrack.
Internal cable The cables and optical fibers which are used for interconnecting electrical interfaces and
optical interfaces within the cabinet.
Internet Group One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
Management Protocol groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
multicast group memberships.
Inverse Multiplexing A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a
over ATM cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.
IP Internet Protocol
IP address A 32-bit (4-byte) binary digit that uniquely identifies a host (computer) connected to the
Internet for communication with other hosts in the Internet by transferring packets. An
IP address is expressed in dotted decimal notation, consisting of decimal values of its 4
bytes, separated by periods (,), for example, 127.0.0.1. The first three bytes of an IP
address identify the network to which the host is connected, and the last byte identifies
the host itself.
IP over DCC A technology that enables a DCC channel to carry TCP/IP protocol packets. The IP over
DCC technology provides the TCP/IP protocol without using any extra overheads or
service resources to ensure interconnection of management channels.
IPA See Intelligent power adjusting
IS-IS Intermedia System-Intermedia System
ISDN Integrated Services Digital Network
ISO International Standard Organization
ISP Internet Service Provider
IST Internal Spanning Tree
ITU-T International Telecommunication Union Telecommunication Standardization

System
A.11 J
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
jitter tolerance Jitter tolerance is defined as the peak-to-peak amplitude of sinusoidal jitter applied on
the input ATM-PON signal that causes a 1 dB optical power penalty at the optical
equipment.
A.12 L
Label A short identifier that is of fixed length and local significance. It is used to uniquely
identify the FEC to which a packet belongs. It does not contain topology information. It
is carried in the header of a packet and does not contain topology information.
LACP See Link Aggregation Control Protocol
LAG See link aggregation group
LAN Local Area Network
LAPS Link Access Procedure-SDH
Laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
Layer A concept used to allow the transport network functionality to be described hierarchically
as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.
layer 2 switch A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch
transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switch.
LB See Loopback
LBM Loopback Message
LBR Loopback Reply
LC Lucent Connector
LCAS See Link Capacity Adjustment Scheme
LCD Liquid Crystal Display
LCT Local Craft Terminal
License A permission that the vendor provides for the user with a specific function, capacity, and
duration of a product. A license can be a file or a serial number. Usually the license
consists of encrypted codes. The operation authority granted varies with the level of the
license.
Link In the topology view, a link is used to identify the physical or logical connection between
two topological nodes. A link is used to connect signaling points (SPs) and signaling
transfer points (STPs) and transmit signaling messages.

System
Link Aggregation A method of bundling a group of physical interfaces together as a logical interface to
Control Protocol increase bandwidth and reliability. For related protocols and standards, refer to IEEE
802.3ad.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
Link Capacity LCAS in the virtual concatenation source and sink adaptation functions provides a
Adjustment Scheme control mechanism to hitless increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the network and element management systems.
LLC Logical Link Control
LM See Loss Measurement
Locked switching When the switching condition is satisfied, this function disables the service from being
switched from the working channel to the protection channel. When the service has been
switched, the function enables the service to be restored from the protection channel to
the working channel.
LOF Loss of Frame
LOM Loss of Multiframe
Loopback A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
LOS Loss of Signal
Loss Measurement Loss measurement, a method used to collect counter values applicable for ingress and
egress service frames where the counters maintain a count of transmitted and received
data frames between a pair of MEPs.
Lower Threshold A lower performance limit which when exceeded by a performance event counter will
trigger a threshold-crossing event.
LP Lower Order Path
LPT Link State Pass Through
LSP Label Switched Path
LSR Label Switching Router
LT Link Trace
A.13 M
MA See Maintenance Association
MAC Medium Access Control
Maintenance TThat portion of a Service Instance, preferably all of it or as much as possible, the
Association connectivity of which is maintained by CFM. It is also a full mesh of Maintenance
Entities.

System
Maintenance Domain The network or the part of the network for which connectivity is managed by connectivity
fault management (CFM). The devices in a maintenance domain are managed by a single
Internet service provider (ISP).
MAN See Metropolitan Area Network
Manual switch Switches normal traffic signal to the protection section, unless a failure condition exists
on other sections (including the protection section) or an equal or higher priority switch
command is in effect, by issuing a manual switch request for that normal traffic signal.
Mapping A procedure by which tributaries are adapted into virtual containers at the boundary of
an SDH network.
Marking-off template A quadrate cardboard with four holes. It is used to mark the positions of the installation
holes for the cabinet.
MBS Maximum Burst Size
MCF Message Communication Function
MCR Minimum Cell Rate
MD See Maintenance Domain
Mean launched power The average power of a pseudo-random data sequence coupled into the fiber by the
transmitter.
MEP Maintenance End Point
Metropolitan Area A network that interconnects users with computer resources in a geographic area or
Network region larger than that covered by even a large LAN but smaller than the area covered
by an WAN. The term is applied to the interconnection of networks in a city into a single
larger network (which may then also offer efficient connection to a wide area network).
It is also used to mean the interconnection of several local area networks by bridging
them with backbone lines. The latter usage is also sometimes referred to as a campus
network.
MIB Management Information Base
MIP Maintenance Intermediate Point
MODEM MOdulator-DEModulator
MP Maintenance Point
MPID Maintenance Point Identification
MPLS See Multiprotocol Label Switching
MS Multiplex Section
MSA Multiplex Section Adaptation
MSOH See Multiplex Section Overhead
MSP See Multiplex Section Protection
MST Multiplex Section Termination
MSTI Multiple Spanning Tree Instance
MSTP See Multi-service transmission platform
MSTP See Multiple Spanning Tree Protocol
MTIE Maximum Time Interval Error

System
MTU Maximum Transmission Unit

Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different link
Switching layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
Multi-service A platform based on the SDH platform, capable of accessing, processing and transmitting
transmission platform TDM services, ATM services, and Ethernet services, and providing unified management
of these services.
Multicast A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
Tree Protocol redundant paths so that the loop network can be trimmed as a tree network. In this case,
the proliferation and endless cycling of packets is avoided in the loop network. The
protocol that introduces the mapping between VLANs and multiple spanning trees. This
solves the problem that data cannot be normally forwarded in a VLAN because in STP/
RSTP, only one spanning tree corresponds to all the VLANs.
Multiplex Section The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH
Overhead definition.
Multiplex Section A function, which is performed to provide capability for switching a signal between and
Protection including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
Multiplexing A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
A.14 N
NE See network element
NE Explorer The main operation interface, of the network management system, which is used to
manage the telecommunication equipment. In the NE Explorer, the user can query,
manage and maintain the NE, boards, and ports on a per-NE basis.
network element An NE contains both the hardware and the software running on it. One NE is at least
equipped with one system control and communication(SCC) board which manages and
monitors the entire network element. The NE software runs on the SCC board.
network node interface The interface at a network node which is used to interconnect with another network node.
network segment A part of an Ethernet or other network, on which all message traffic is common to all
nodes, that is, it is broadcast from one node on the segment and received by all others.
NLP Normal Link Pulse
NMS Network Management System
NNI See network node interface
NPC Network Parameter Control

System
nrt-VBR Non Real-Time Variable Bit Rate

NRZ Non Return to Zero code
NSAP Network Service Access Point
NTP Network Time Protocol
A.15 O
OA See Optical Amplifier
OADM See Optical Add/Drop Multiplexer
OAM Operations, Administration and Maintenance
OAM auto-discovery In the case of OAM auto-discovery, two interconnected ports, enabled with the Ethernet
in the First Mile OAM (EFM OAM) function, negotiate to determine whether the mutual
EFM OAM configuration match with each other by sending and responding to the OAM
protocol data unit (OAMPDU). If the mutual EFM OAM configuration match, the two
ports enter the EFM OAM handshake phase. In the handshake phase, the two ports
regularly send the OAMPDU to maintain the neighborhood relation.
OCP See Optical Channel Protection
ODF See Optical Distribution Frame
ODU Outdoor Unit
OFS Out-of-frame Second
OHA Overhead Access Function
OLT Optical Line Terminal
Online Help The capability of many programs and operating systems to display advice or instructions
for using their features when so requested by the user.
ONU Optical Network Unit
OOF Out of Frame
Optical Add/Drop A device that can be used to add the optical signals of various wavelengths to one channel
Multiplexer and drop the optical signals of various wavelengths from one channel.
Optical Amplifier Devices or subsystems in which optical signals can be amplified by means of the
stimulated emission taking place in a suitable active medium.
Optical attenuator A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
Optical Channel In an optical transmission link that contains multiple wavelengths, when a certain
Protection wavelength goes faulty, the services at the wavelength can be protected if the optical
channel protection is configured.
Optical Connector A component normally attached to an optical cable or a piece of apparatus to provide
frequent optical interconnection/disconnection of optical fibers or cables.
Optical Distribution A frame which is used to transfer and spool fibers.
Frame

System
Optical Interface A component that connects several transmit or receive units.

Optical Time Domain A device that sends a very short pulse of light down a fiber optic communication system
Reflectometer and measures the time history of the pulse reflection to measure the fiber length, the light
loss and locate the fiber fault.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
OSI Open Systems Interconnection
OSN Optical Switch Node
OSPF Open Shortest Path First
OTDR See Optical Time Domain Reflectometer
OTU See Optical transponder unit
Optical transponder A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2-
unit compliant WDM wavelength.
Output optical power The ranger of optical energy level of output signals.
Overhead Extra bits in a digital stream used to carry information besides traffic signals. Orderwire,
for example, would be considered overhead information.
A.16 P
Paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane.
pass-through The action of transmitting the same information that is being received for any given
direction of transmission.
Path A performance resource object defined in the network management system. The left end
of a path is a device node whose port needs to be specified and the right end of a path is
a certain IP address which can be configured by the user. By defining a path in the
network management system, a user can test the performance of a network path between
a device port and an IP address. The tested performance may be the path delay, packet
loss ratio or other aspects.
PBS Peak Burst Size
PC Personal Computer
PCM Pulse Code Modulation
PCR Peak Cell Rate
PDH See Plesiochronous Digital Hierarchy
PDU See Power distribution unit
PE See provider edge

System
Performance register The memory space for performance event counts, including 15-min current performance
register, 24-hour current performance register, 15-min historical performance register,
24-hour historical performance register, UAT register and CSES register. The object of
performance event monitoring is the board functional module, so every board functional
module has a performance register. A performance register is used to count the
performance events taking place within a period of operation time, so as to evaluate the
quality of operation from the angle of statistics.
performance threshold A limit for generating an alarm for a selected entity. When the measurement result
reaches or exceeds the preset alarm threshold, the performance management system
generates a performance alarm.
Permanent Virtual A connection between two ATM end hosts. The connection consists of PVPs between
Connection the ATM end hosts and their respective switches, and SVPs between the switches.
PGND Protection Ground
PGND cable A cable which connects the equipment and the protection grounding bar. Usually, one
half of the cable is yellow, whereas the other half is green.
PIM-SM Protocol Independent Multicast-Sparse Mode
PIR Peak Information Rate
plesiochronous Qualifying two time-varying phenomena, time-scales, or signals in which corresponding
significant instants occur at the same rate, any variations in rate being constrained within
specified limits. Note: Corresponding significant instants are separated by time intervals
having durations which may vary without limit.
Plesiochronous Digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
Hierarchy rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
PLL Phase-Locked Loop
Pointer An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which this pointer is supported.
POS Packet Over SDH
Power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
Power distribution unit A unit that performs AC or DC power distribution.
PPP Point-to-Point Protocol
PRBS See Pseudo Random Binary Sequence
PRC Primary Reference Clock
Primitive In the hierarchy of signaling system No.7, when the upper layer applies for services from
the lower layer or the lower layer transmits services to the upper layer, the data is
exchanged between the user and the service provider. The data transmitted between
adjacent layers is called primitive.
Private Line A line, such as a subscriber cable and trunk cable, which are leased by the
telecommunication carrier and are used to meet the special user requirements.
Protection path A specific path that is part of a protection group and is labeled protection.
Protection service A specific service that is part of a protection group and is labeled protection.

System
Protection subnet In the NMS, the protection subnet becomes a concept of network level other than
multiplex section rings or path protection rings. The protection sub-network involves
NEs and fiber cable connections.
Protection View The user interface, of the NMS, which is used to manage protection in the network.
provider edge A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. A PE performs the mapping and
forwarding of packets between the private network and the public channel. A PE can be
a UPE, an SPE, or an NPE.
PS Packet Switched
PSD Power Spectral Density
Pseudo Random Binary A sequence that is random in a sense that the value of an element is independent of the
Sequence values of any of the other elements, similar to real random sequences.
Pseudo Wire An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
Pseudo Sire Emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
edge-to-edge telecommunication service such as ATM, FR or Ethernet in a packet switched network
(PSN). PWE3 also emulates the essential attributes of low speed time division
multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
PVC See Permanent Virtual Connection
PW See Pseudo Wire
PWE3 See Pseudo Sire Emulation edge-to-edge
A.17 Q
QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It add a public VLAN
tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to
be transmitted over the service provider’s backbone network based on the public VLAN
tag. This provides a layer 2 VPN tunnel for customers and enables transparent
transmission of packets over private VLANs.
QoS See Quality of Service
Quality of Service A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
A.18 R
Rapid Spanning Tree An evolution of the Spanning Tree Protocol, providing for faster spanning tree
Protocol convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.

System
RDI Remote Defect Indication

Receiver Sensitivity The minimum acceptable value of average received power at point R to achieve a 1 x
10-12 BER (The FEC is open).
Reference clock A kind of stable and high-precision autonous clock providing frequencies for other clocks
for reference.
REG A piece of equipment or device that regenerates electrical signals.
Regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
Regenerator section The regenerator section overhead comprises rows 1 to 3 of the SOH of the STM-N signal.
overhead
Remote optical A remote optical amplifier subsystem designed for applications where power supply and
pumping amplifier monitoring systems are unavailable. The ROPA subsystem is a power compensation
solution to the ultra-long distance long hop (LHP) transmission.
Resilient Packet Ring A network topology being developed as a new standard for fiber optic rings.
RF Radio Frequency
RFA Request For Announcement
RFI Request for Information
ring network A type of network topology in which each node connects to exactly two other nodes,
forming a circular pathway for signals.
RNC Radio Network Controller
ROPA See Remote optical pumping amplifier
route The path that network traffic takes from its source to its destination. In a TCP/IP network,
each IP packet is routed independently. Routes can change dynamically.
router A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
RP Rendezvous Point
RPR See Resilient Packet Ring
RS232 A asynchronous transfer mode that does not involve 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 specification that defines the electrical characteristics of balanced voltage digital
interface circuits. The interface can change to RS232 via the hardware jumper and others
are the same as RS232.
RSTP See Rapid Spanning Tree Protocol
RTN Radio Transmission Node
RX Receiver

System
A.19 S
S1 byte A byte to transmit network synchronization status information. On an SDH network,
each NE traces hop by hop to the same clock reference source through a specific clock
synchronization path, realizing synchronization on the entire network. If a clock
reference source traced by an NE is missing, this NE will trace another clock reference
source of a lower level. To implement protection switching of clocks in the whole
network, the NE must learn about clock quality information of the clock reference source
it traces. Therefore, ITU-T defines S1 byte to transmit 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. Auto protection switching of clocks
in a synchronous network can be implemented using S1 byte and a proper switching
protocol.
SAN Storage Area Network
SC Square Connector
SCR Sustainable Cell Rate
SD See space diversity
SD See Signal Degrade
SD See Standard definition
SDH See Synchronous Digital Hierarchy
SDP Serious Disturbance Period
SD-SDI See Standard definition-Serial Digital Interface signal
SEC SDH Equipment Clock
Section The portion of a SONET transmission facility, including terminating points, between (i)
a terminal network element and a regenerator or (ii) two regenerators. A terminating
point is the point after signal regeneration at which performance monitoring is (or may
be) done.
Self-healing A function of establishing a replacement connection by network without the network
management connection function. When a connection failure occurs, the replacement
connection is found by the network elements and rerouted depending on network
resources available at that time.
Serial port extended The ECC channel realized by means of serial port.
ECC
server A network device that provides services to network users by managing shared resources,
often used in the context of a client-server architecture for a LAN.
Service protection A measure that ensures that the services can be received at the receive end.
SES Severely Errored Second
SETS Synchronous Equipment Timing Source
settings Parameters of a system or operation that can be selected by the user.
SF See Signal Fail

System
Signal Fail A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
SFP See Small Form-Factor Pluggable
SHDSL Single-line High speed Digital Subscriber Line
Side Mode Suppression The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total
Ratio source spectrum to the second largest peak.
signal cable Common signal cables cover the E1 cable, network cable, and other non-subscriber
signal cable.
Signal Degrade SD is a signal indicating the associated data has degraded in the sense that a degraded
defect (e.g., dDEG) condition is active.
Signal Fail SF is a signal indicating the associated data has failed in the sense that a near-end defect
condition (not being the degraded defect) is active.
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
slide rail Angle-bars on which shelves and chassis may slide and be supported within a cabinet or
shelf.
Small Form-Factor A specification for a new generation of optical modular transceivers.
Pluggable
SMSR See Side Mode Suppression Ratio
SNC SubNetwork Connection
SNCMP See Subnetwork connection multipath protection
SNCP See SubNetwork Connection Protection
SNCP node Set the SNC node on the protection sub-network to support sub-network connection
protection that spans protection sub-networks. The SNCP node of the ring sub-network
can support electric circuit dually feed and selectively receive a timeslot out of the ring,
thus implementing sub-network connection protection. The SNCP node is generally set
on the node on the line board with the path protection type of the dual fed and selectively
received.
SNCTP See Subnetwork Connection Tunnel Protection
SNMP See Simple Network Management Protocol
SNR Signal Noise Ratio
space diversity A diversity scheme that enables two or more antennas separated by a specific distance
to transmit/receive the same signal and selection is then performed between the two
signals to ease the impact of fading. Currently, only receive SD is used.
Spanning Tree Protocol STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant
network to block some undesirable redundant paths through certain algorithms and prune
a loop network into a loop-free tree network.
SPI Synchronous Physical Interface

System
SSM See Synchronization Status Message

SSU Synchronization Supply Unit
Standard definition Standard definition defines a video format with the resolution below 720P.
Standard definition- Standard definition video signal transported by serial digital interface.
Serial Digital Interface
signal
Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be
transmitted across a single physical channel. It dynamically allocates bandwidth only to
active input channels, to make better use of available bandwidth and allow more devices
to be connected than with other multiplexing techniques.
STM-4 SDH standard for transmission over optical fiber at 622.08 Mbit/s.
STP See Spanning Tree Protocol
Sub-network number A number used to differentiate network sections in a sub-network conference. A sub-
network ID consists of the first several digits (one or two) of a user phone number. An
order wire phone number consists of the sub-network ID and the user number.
subnet A type of smaller networks that form a larger network according to a rule, for example,
according to different districts. This facilitates the management of the large network.
subnet mask The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router matches with the IP address.
Subnetwork connection The only difference is that SNCP is of 1+1 protection and SNCMP is of N+1 protection.
multipath protection That is, several backup channels protect one active channel in SNCMP.
SubNetwork A function, which allows a working subnetwork connection to be replaced by a protection
Connection Protection subnetwork connection if the working subnetwork connection fails, or if its performance
falls below a required level.
Subnetwork SNCTP provides a VC-4 level channel protection. When the working channel is faulty,
Connection Tunnel the services of the entire VC-4 path can be switched over to the protection channel.
Protection
Support A part used to support and fix a cabinet on the antistatic floor. It is made of welded steel
plates and is used to block up the cabinets to facilitate floor layout and cabling. Before
the whole set of equipment is grounded, insulation plates must be installed under the
supports, and insulating coverings must be added to the expansion bolts to achieve good
insulation performance.
Suppression state An attribute set to determine whether an NE monitors the alarm. Under suppression
status, NE will not monitor the corresponding alarm conditions and the alarm will not
occur even when the alarm conditions are met.
SVC Switching Virtual Connection
Switching priority A priority of a board that is defined for protection switching. When several protected
boards need to be switched, a switching priority should be set for each board. If the
switching priorities of the boards are the same, services on the board that fails later cannot
be switched. Services on the board with higher priority can preempt the switching
resources of that with lower priority.

System
Switching restoration It refers to the period of time between the start of detecting and the moment when the
time line is switched back to the original status after protection switching occurs in the MSP
sub-network.
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Message Nodes on an SDH network and a synchronization network acquire upstream clock
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.
Synchronous Digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the
Hierarchy transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is used only for signals. SDH is suitable
for the fiber communication system with high speed and a large capacity since it uses
synchronous multiplexing and flexible mapping structure.
Synchronous source A clock providing timing services to connected network elements. This would include
clocks conforming to Recommendations G.811, G.812 and G.813.
A.20 T
Tandem Connection In the SDH transport hierarchy, the TCM is located between the AU/TU management
Monitor layer and HP/LP layer. It uses the N1/N2 byte of POH overhead to monitor the quality
of the transport channels on a transmission section (TCM section).
TCM See Tandem Connection Monitor
TCP/IP See Transmission Control Protocol/Internet Protocol
TDM Time Division Multiplexing
TIM Trace Identifier Mismatch
Timeslot Continuously repeating interval of time or a time period in which two devices are able
to interconnect.
Time Synchronization Also called the moment synchronization, time synchronization means that the
synchronization of the absolute time, which requires that the starting time of the signals
keeps consistent with the UTC time.
TM Terminal Multiplexer
TMN Telecommunications Management Network
ToS See Type of Service
TPS See Tributary Protection Switch
Trail management A network level management function of the network management system. This function
function enables you to configure end-to-end services, view graphic interface 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.
Transceiver A transmitter and receiver housed together in a single unit and having some circuits in
common, often for portable or mobile use.

System
Transmission Control Common name for the suite of protocols developed to support the construction of
Protocol/Internet worldwide internetworks.
Protocol
transparent A process during which the signaling protocol or data is not processed in the content but
transmission encapsulated in the format for the processing of the next phase.
Tray A component that can be installed in the cabinet for holding chassis or other devices.
Tributary loopback A fault can be located for each service path by performing loopback to each path of the
tributary board. There are three kinds of loopback modes: no loopback, outloop, and
inloop.
Tributary Protection A function that uses a standby tributary processing board to protect N tributary
Switch processing boards.
Tributary unit An information structure which provides adaptation between the lower order path layer
and the higher order path layer. It consists of an information payload (the lower order
VC) and a TU pointer which indicates the offset of the payload frame start relative to
the higher order VC frame start.
Tributary Unit Group One or more Tributary Units, occupying fixed, defined positions in a higher order VC-
n payload is termed a Tributary Unit Group (TUG). TUGs are defined in such a way that
mixed capacity payloads made up of different size Tributary Units can be constructed
to increase flexibility of the transport network.
TTL Time To Live
TU Tributary Unit
TUG See Tributary Unit Group
Tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.
Type of Service A field in an IP packet (IP datagram) used for quality of service (QoS). The TOS field
has 8 bits in length, which is divided into five subfields.
A.21 U
UART Universal Asynchronous Receiver/Transmitter
UAS Unavailable Second
UBR Unspecified Bit Rate
underfloor cabling The cables connected cabinets and other devices are routed underfloor.
UNI See User-to-Network Interface
Unprotected Pertaining to the transmission of the services that are not protected. The services cannot
be switched to the protection channel if the working channel is faulty or the service is
interrupted, because protection mechanism is not configured.
Unprotected sub- A sub-network without any protection mechanism. The purpose of such configuration
network is to provide the basic data of trail protection for subsequent trail management.

System
Upload An operation to report some or all configuration data of an NE to the NMS. The
configuration data then covers the configuration data stored at the NMS side.
UPM Uninterruptible Power Module
Upper threshold TThe critical value that can induce unexpected events if exceeded.
UPS Uninterruptible Power Supply
Upward cabling Cables or fibers connect the cabinet with other equipment from the top of the cabinet.
User Any entity external to the network which utilizes connections through the network for
communication. A person or other entity authorized by a subscriber to use some or all
of the services subscribed to by that subscriber.
User-to-Network The interface between user equipment and private or public network equipment (for
Interface example, ATM switches).
UTC Universal Time Coordinated
A.22 V
VB Virtual Bridge
VBR Variable Bit Rate
VC Virtual Concatenation
VC See Virtual Container
VCG Virtual Concatenation Group
VCI Virtual Channel Identifier
Virtual Container The information structure used to support path layer connections in the SDH. It consists
of information payload and path overhead (POH) information fields organized in a block
frame structure which repeats every 125 or 500 μs.
Virtual local area A logical grouping of two or more nodes which are not necessarily on the same physical
network network segment but which share the same IP network number. This is often associated
with switched Ethernet.
Virtual Private A system configuration, where the subscriber is able to build a private network via
Network connections to different network switches that may include private network capabilities.
VLAN See Virtual local area network
VP Virtual Path
VPI Virtual Path Identifier
VPN See Virtual Private Network
A.23 W
Wait to Restore The number of minutes to wait before services are switched back to the working line.
WAN Wide Area Network

System
Wander The long-term variations of the significant instants of a digital signal from their ideal
position in time (where long-term implies that these variations are of frequency less than
10 Hz).
washer A washer is a thin flat ring of metal or rubber which is placed over a bolt before the nut
is screwed on.
Wavelength Division A technology that utilizes the characteristics of broad bandwidth and low attenuation of
Multiplexing single mode optical fiber, uses multiple wavelengths as carriers, and allows multiple
channels to transmit simultaneously in a single fiber.
Wavelength protection Data for describing the wavelength protection structure. Its function is similar to that of
group the protection subnet for SDH NEs. The wavelength path protection can work only with
the correct configuration of the wavelength protection group.
WDM See Wavelength Division Multiplexing
WFQ Weighted Fair Queuing
Winding pipe A tool for fiber routing, which acts as the corrugated pipe.
Working path A path allocated to transport the normal traffic.
WRED Weighted Random Early Detection
WTR See Wait to Restore


Toaz - Info Optix Osn 550 Configuration Guide v100r003 PR

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Toaz - Info Optix Osn 550 Configuration Guide v100r003 PR

Uploaded by

Copyright:

Available Formats

OptiX OSN 550 Multi-Service CPE Optical

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2011-06-30) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX OSN 550 V100R003C00

iManager U2000 V100R005C00

This document is intended for:

l Data configuration engineer

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

Issue 02 (2011-06-30) Huawei Proprietary and Confidential iii

NOTE Provides additional information to emphasize or supplement

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Changes in Issue 02 (2011-06-30) Based on Product Version V100R003C00

Changes in Issue 01 (2011-04-30) Based on Product Version V100R003C00

iv Huawei Proprietary and Confidential Issue 02 (2011-06-30)

About This Document...................................................................................................................iii

2 Creating the Network................................................................................................................2-1

Issue 02 (2011-06-30) Huawei Proprietary and Confidential v

2.4.1 Creating Fibers Automatically.............................................................................................................2-11

3 Configuring SDH Services.......................................................................................................3-1

vi Huawei Proprietary and Confidential Issue 02 (2011-06-30)

3.4.3 Per-NE Configuration Process.............................................................................................................3-17

4 Configuring Ethernet Services................................................................................................4-1

Issue 02 (2011-06-30) Huawei Proprietary and Confidential vii

4.2.5 Encapsulation and Mapping Protocol..................................................................................................4-14

viii Huawei Proprietary and Confidential Issue 02 (2011-06-30)

4.11.4 Advanced Attributes.........................................................................................................................4-134

5 Modifying the Configuration Data.........................................................................................5-1

Issue 02 (2011-06-30) Huawei Proprietary and Confidential ix

7.6 PHY Loopback (Ethernet Port Attribute)......................................................................................................7-10

x Huawei Proprietary and Confidential Issue 02 (2011-06-30)

7.48 OAM Working Mode..................................................................................................................................7-43

Issue 02 (2011-06-30) Huawei Proprietary and Confidential xi

A Glossary and Acronyms..........................................................................................................A-1

xii Huawei Proprietary and Confidential Issue 02 (2011-06-30)

Issue 02 (2011-06-30) Huawei Proprietary and Confidential xiii

Figure 1-1 Client GUI..........................................................................................................................................1-5

Issue 02 (2011-06-30) Huawei Proprietary and Confidential xv

Figure 4-14 Structure of the PAUSE frame....................................................................................................... 4-14

xvi Huawei Proprietary and Confidential Issue 02 (2011-06-30)

Table 2-1 SDH board parameters.........................................................................................................................2-9

Issue 02 (2011-06-30) Huawei Proprietary and Confidential xvii

Table 4-21 Parameters of external ports on the Ethernet boards........................................................................4-62

xviii Huawei Proprietary and Confidential Issue 02 (2011-06-30)

About This Chapter

1.1 Starting or Shutting Down the U2000

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 1-1

1.1 Starting or Shutting Down the U2000

1.1.1 Starting the U2000 Server

Step 1 Double-click the shortcut icon to start U2000 Server.

1-2 Huawei Proprietary and Confidential Issue 02 (2011-06-30)

Periodically change the password and memorize it.

1.1.2 Logging In to the U2000 Client

1.1.3 Exiting a U2000 Client

Step 2 Click OK in the confirmation dialog box.

1.1.4 Shutting Down the U2000 Server

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 1-3