OSN 500 550 V100R007C00 Configuration Guide (Packet Transport Domain) 03

OptiX OSN 500/550 Multi-Service CPE Optical
Transmission System
V100R007C00
Configuration Guide (Packet
Transport Domain)
Issue 03
Date 2014-03-31
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. 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 a 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 03 (2014-03-31) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 500 V100R007C00
OptiX OSN 550 V100R007C00
iManager U2000 V100R009C00

Intended Audience
This document describes the features and functions of the OptiX OSN equipments. To be more
specific, this document describes the basic concepts, availability, realization principle,
application, configuration, and troubleshooting of these features and functions.
This document is intended for:
l Installation and commissioning engineer
l Data configuration engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
DANGER
DANGER indicates a hazard with a high level or medium
level of risk which, if not avoided, could result in death or
serious injury.
WARNING
WARNING indicates a hazard with a low level of risk which,
if not avoided, could result in minor or moderate injury.
Transmission System
Configuration Guide (Packet Transport Domain) About This Document
ii
Symbol Description
CAUTION
CAUTION indicates a potentially hazardous situation that,
if not avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
TIP
Provides a tip that may help you solve a problem or save time.
NOTE
Provides additional information to emphasize or supplement
important points in 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.
Updates in Issue 03 (2014-03-31) Based on Product Version V100R007C00
This document of the V100R007C00 version is of the third release. Compared with Issue 02,
Issue 03 includes the following updates in V100R007C00SPC200:
l "Logging In to the U2000 Client" is optimized in section "Starting or Shutting Down the
U2000."
This document of the V100R007C00 version is of the second release. Compared with Issue 01,
Issue 02 includes the following updates in V100R007C00SPC100:
l In topic "Configuration Task Collection", the description of "Creating an ATM Service by
Using the Trail Function" is added.
l "Modifying MPLS Tunnels" is optimized in section "Configuration Task Collection."
Transmission System
iii
This document is the first issue for the V100R007C00 product version.
Transmission System
iv
Contents
About This Document.....................................................................................................................ii
1 Getting Started...............................................................................................................................1
1.1 Starting or Shutting Down the U2000............................................................................................................................2
1.1.1 Starting the U2000 Server...........................................................................................................................................2
1.1.2 Logging In to the U2000 Client...................................................................................................................................2
1.1.3 Exiting a U2000 Client................................................................................................................................................3
1.1.4 Shutting Down the U2000 Server................................................................................................................................3
1.2 Main Windows and Common Operations of the U2000................................................................................................4
1.2.1 Components of the Client GUI....................................................................................................................................4
1.2.2 Key GUI Components.................................................................................................................................................6
1.2.3 Frequently Used Buttons.............................................................................................................................................7
1.2.4 Shortcut Icon................................................................................................................................................................9
1.2.5 Common Shortcut Keys.............................................................................................................................................13
1.2.6 Main Windows..........................................................................................................................................................13
1.2.6.1 Workbench..............................................................................................................................................................14
1.2.6.2 Main Topology.......................................................................................................................................................14
1.2.6.3 NE Explorer............................................................................................................................................................16
1.2.6.4 Clock View.............................................................................................................................................................17
1.2.6.5 NE Panel.................................................................................................................................................................18
1.2.6.6 Browse Alarm.........................................................................................................................................................18
1.2.6.7 Browse Event..........................................................................................................................................................18
1.2.6.8 Browse Performance Window................................................................................................................................19
2 Creating the Network.................................................................................................................20
2.1 Creating a Topology Subnet.........................................................................................................................................22
2.2 Creating NEs.................................................................................................................................................................22
2.2.1 Creating a Single NE.................................................................................................................................................22
2.2.2 Creating NEs in Batches............................................................................................................................................24
2.3 Configuring the NE Data..............................................................................................................................................26
2.3.1 Configuring the NE Data Manually...........................................................................................................................26
2.3.2 Replicating the NE Data............................................................................................................................................27
2.3.3 Uploading the NE Data..............................................................................................................................................28
2.4 Creating an NE User.....................................................................................................................................................29
Transmission System
Configuration Guide (Packet Transport Domain) Contents
v
2.5 Switching a Logged-In NE User..................................................................................................................................30
2.6 Creating Optical Fibers.................................................................................................................................................31
2.6.1 Creating Ethernet Fibers and Cables in the Packet Domain by Means of Search on the NMS................................31
2.6.2 Creating Fibers Manually..........................................................................................................................................32
2.7 Configuring the Inband DCN.......................................................................................................................................33
2.7.1 Setting the VLAN ID and Bandwidth Used by an Inband DCN...............................................................................34
2.7.2 Setting the Parameters for NMS Access....................................................................................................................34
2.7.3 Enabling the DCN Function for a Port......................................................................................................................35
2.7.4 Setting the Protocol Stack Used by an Inband DCN.................................................................................................35
2.7.5 Setting Inband DCN Packet Priority.........................................................................................................................36
2.7.6 Verifying the Inband DCN........................................................................................................................................36
2.8 Synchronizing the NE Time with the NMS..................................................................................................................37
2.9 Enabling, Disabling, and Setting Performance Monitoring of the NE.........................................................................38
3 Configuring ETH PWE3 Services.............................................................................................40
3.1 Basic Concepts.............................................................................................................................................................41
3.1.1 E-Line Services Carried by PWs...............................................................................................................................41
3.1.2 E-LAN Services Carried on PWs..............................................................................................................................43
3.1.3 Ethernet Port..............................................................................................................................................................47
3.1.4 VPLS.........................................................................................................................................................................48
3.1.5 Split Horizon Group..................................................................................................................................................48
3.2 Configuration Flow.......................................................................................................................................................49
3.2.1 E-Line Services Carried by PWs...............................................................................................................................49
3.2.2 E-LAN Services Carried by PWs..............................................................................................................................53
3.3 Configuration Example: E-Line Services Carried by PWs(Based on VLANs)...........................................................59
3.3.1 Networking Diagram.................................................................................................................................................60
3.3.2 Service Planning........................................................................................................................................................61
3.3.3 Configuration Process (in End-to-End Mode)...........................................................................................................65
3.3.4 Configuration Process (Configuration on a Per-NE Basis).......................................................................................71
3.3.5 Verifying the Correctness of E-Line Service Configuration.....................................................................................80
3.4 Configuration Example: E-Line Services Carried by PWs (Based on VLAN Priorities)............................................82
3.4.1 Networking Diagram.................................................................................................................................................82
3.4.2 Service Planning........................................................................................................................................................84
3.4.3 Configuration Process (in End-to-End Mode)...........................................................................................................88
3.4.4 Configuration Process (Configuration on a Per-NE Basis).......................................................................................95
3.4.5 Verifying E-Line Services.......................................................................................................................................103
3.5 Configuration Example: E-Line Services Carried by PWs (Based on VLAN Switching).........................................105
3.5.1 Networking Diagram...............................................................................................................................................105
3.5.2 Service Planning......................................................................................................................................................107
3.5.3 Configuration Process (in End-to-End Mode).........................................................................................................111
3.5.4 Configuration Process (Configuration on a Per-NE Basis).....................................................................................117
3.5.5 Verifying the Correctness of E-Line Service Configuration...................................................................................126
Transmission System
vi
3.6 Configuration Example (E-LAN Services Carried by PWs)......................................................................................128
3.6.3 Configuration Procedure (in End-to-End Mode).....................................................................................................135
3.6.4 Configuration Procedure (Configuration on a Per-NE Basis).................................................................................141
3.6.5 Verifying E-LAN Service Configurations...............................................................................................................150
4 Configuring Native Ethernet Services on the Packet Plane..............................................151
4.1 Basic Concepts...........................................................................................................................................................152
4.1.1 Ethernet Port Numbers............................................................................................................................................152
4.1.2 Auto-Negotiation.....................................................................................................................................................152
4.1.3 Flow Control Function.............................................................................................................................................154
4.1.4 Native Ethernet Service Types Based on the Packet Plane.....................................................................................155
4.1.4.1 Point-to-Point Transparently Transmitted E-Line Services.................................................................................155
4.1.4.2 VLAN-Based E-Line Services.............................................................................................................................157
4.1.4.3 QinQ-Based E-Line Services................................................................................................................................158
4.1.4.4 E-LAN Services Based on the 802.1d Bridge......................................................................................................161
4.1.4.5 E-LAN Services Based on 802.1q Bridge............................................................................................................162
4.1.4.6 E-LAN Services Based on 802.1ad Bridge..........................................................................................................163
4.1.5 Managing a MAC Address Table............................................................................................................................165
4.1.6 VLAN Forwarding Table........................................................................................................................................166
4.1.7 Split Horizon Group................................................................................................................................................167
4.2 Configuration Procedure.............................................................................................................................................168
4.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services).........................................168
4.2.2 Configuration Procedure (VLAN-Based E-Line Services).....................................................................................171
4.2.3 Configuration Procedure (QinQ-Based E-Line Services).......................................................................................175
4.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services)...............................................................179
4.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services)...............................................................184
4.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services).............................................................189
4.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)..............................................194
4.3.2.1 Service Planning (Ethernet Ports).........................................................................................................................195
4.3.2.2 Service Planning (Ethernet Services)...................................................................................................................196
4.3.2.3 Service Planning (QoS)........................................................................................................................................196
4.3.3 Configuration Process..............................................................................................................................................198
4.3.3.1 Configuration Process (Ethernet Ports)................................................................................................................198
4.3.3.2 Configuration Process (Service Information).......................................................................................................199
4.3.3.3 Configuration Process (QoS)................................................................................................................................200
4.4 Configuration Example (VLAN-Based E-Line Service)............................................................................................202
Transmission System
vii
4.4.4 Per-NE Configuration Process.................................................................................................................................215
4.5 Configuration Example (QinQ-Based E-Line Service)..............................................................................................219
4.5.3.4 Configuration Process (Verifying Ethernet Service Configurations)...................................................................233
4.6 Configuration Example (802.1d Bridge-Based E-LAN Service)...............................................................................244
Transmission System
viii
4.7 Configuration Example (802.1q Bridge-Based E-LAN Service)...............................................................................265
4.8 Configuration Example (802.1ad Bridge-Based E-LAN Service).............................................................................288
5 Configuring a Composite Service Consisting of E-Line and E-LAN Services..............312
5.1 Basic Concepts...........................................................................................................................................................313
5.2 Configuration Flow for a Composite Service Consisting of E-Line and E-LAN Services........................................314
5.3 Configuration Example: Composite Service Consisting of E-Line and E-LAN Services.........................................319
Transmission System
ix
5.3.4 Verifying the Composite Service Consisting of E-Line and E-LAN Services........................................................331
6 Configuring CES Services........................................................................................................334
6.1 Basic Concepts...........................................................................................................................................................335
6.2 Configuration Flow for the CES Services..................................................................................................................336
6.2.1 Configuration Flow for UNI-UNI CES Services....................................................................................................336
6.2.2 Configuration Flow for UNI-NNI CES Services....................................................................................................337
6.3 Configuration Example (UNI-UNI CES Services)....................................................................................................342
6.4 Configuration Example (UNI-NNI CES Services)....................................................................................................344
6.4.4 Configuration Process (Configuration on a Per-NE Basis).....................................................................................357
6.5 Verifying CES Services..............................................................................................................................................363
7 Configuring ATM PWE3 Services..........................................................................................366
7.1 Basic Concepts...........................................................................................................................................................367
7.1.1 ATM Service...........................................................................................................................................................367
7.1.2 ATM Traffic............................................................................................................................................................368
7.2 Configuration Procedure.............................................................................................................................................369
7.2.1 Configuration Flow for UNI-UNI ATM Services...................................................................................................369
7.2.2 Configuration Procedure (UNI-NNI ATM Services)..............................................................................................370
7.3 QoS Configuration Case of ATM Services................................................................................................................375
7.3.1 Case Description......................................................................................................................................................376
7.4 Configuration Example of the UNI-UNI ATM Service.............................................................................................380
7.4.3 Configuration Process in Per-NE Mode..................................................................................................................383
7.5 Configuration Example of the UNI-NNI ATM Service.............................................................................................387
7.5.3 Configuration Process in End-to-End Mode...........................................................................................................392
7.5.4 Configuration Process in Per-NE Mode..................................................................................................................418
7.6 Verifying ATM/IMA Services...................................................................................................................................438
8 Configuration Task Collection...............................................................................................441
8.1 Configuring an Ethernet Port......................................................................................................................................444
8.1.1 Setting the General Attributes of Ethernet Interfaces..............................................................................................445
8.1.2 Setting the Layer 2 Attributes of Ethernet Ports......................................................................................................446
Transmission System
x
8.1.3 Setting the Layer 3 Attributes of Ethernet Ports......................................................................................................447
8.1.4 Setting the Advanced Attributes of Ethernet Ports..................................................................................................447
8.1.5 Configuring Flow Control.......................................................................................................................................448
8.2 Configuring the NNIs.................................................................................................................................................448
8.2.1 Configuring the NNIs for Ethernet Services Carried by PWs.................................................................................448
8.2.2 Configuring the NNIs for Ethernet Services Carried by QinQ Links.....................................................................449
8.3 Configuring CES Ports...............................................................................................................................................450
8.3.1 Setting Basic Attributes of Smart E1 Ports.............................................................................................................450
8.3.2 Setting Advanced Attributes of Smart E1 Ports......................................................................................................451
8.3.3 Configuring Channelized STM-1 Ports...................................................................................................................451
8.4 Setting Serial Port Parameters....................................................................................................................................452
8.4.1 Creating Serial Ports................................................................................................................................................452
8.4.2 Setting Basic Attributes of Serial Ports...................................................................................................................453
8.5 Configuring ATM PWE3 Services.............................................................................................................................453
8.5.1 Configuring ATM Interfaces...................................................................................................................................453
8.5.2 Configuring ATM CoS Mapping............................................................................................................................457
8.5.3 Creating the ATM Policy........................................................................................................................................458
8.5.4 Creating an ATM Service by Using the Trail Function..........................................................................................459
8.6 Managing ATM/IMA Ports........................................................................................................................................462
8.6.1 Binding ATM TRUNKs..........................................................................................................................................462
8.6.2 Configuring an IMA group......................................................................................................................................463
8.6.3 Setting ATM Port Parameters..................................................................................................................................464
8.6.4 Querying Running Status of an IMA Group...........................................................................................................465
8.6.5 Querying Link Running Status of an IMA Group...................................................................................................465
8.7 ATM Traffic Management.........................................................................................................................................466
8.7.1 Creating an ATM Policy..........................................................................................................................................466
8.7.2 Modifying an ATM Policy......................................................................................................................................467
8.7.3 Creating an ATM-DiffServ Domain........................................................................................................................468
8.7.4 Modifying an ATM-Diffserv Domain.....................................................................................................................469
8.8 Configuring an MPLS Tunnel....................................................................................................................................471
8.8.1 Configuring LSR ID................................................................................................................................................471
8.8.2 Configuring an MPLS Tunnel in an End-to-End Mode..........................................................................................471
8.8.2.1 Configuring a Unidirectional MPLS Tunnel........................................................................................................471
8.8.2.2 Configuring a Bidirectional MPLS Tunnel..........................................................................................................474
8.8.3 Configuring an MPLS Tunnel on a Per-NE Basis...................................................................................................477
8.8.3.1 Configuring a Unidirectional MPLS Tunnel........................................................................................................477
8.8.3.2 Configuring a Bidirectional Static MPLS Tunnel................................................................................................478
8.9 Managing MPLS Tunnels...........................................................................................................................................479
8.9.1 Searching for MPLS Tunnels..................................................................................................................................479
8.9.2 Checking the MPLS Tunnel Topology....................................................................................................................480
8.9.3 Deploying MPLS Tunnels.......................................................................................................................................481
Transmission System
xi
8.9.4 Modifying MPLS Tunnels.......................................................................................................................................481
8.9.5 Deleting MPLS Tunnels..........................................................................................................................................483
8.9.6 Deleting MPLS Tunnels from the Network Side....................................................................................................484
8.9.7 Deleting MPLS Tunnels from the NE Side.............................................................................................................485
8.9.8 Managing Discrete MPLS Tunnels.........................................................................................................................485
8.10 Configuring MPLS Tunnel OAM.............................................................................................................................486
8.10.1 Configuring MPLS Tunnel OAM in End-to-End Mode.......................................................................................486
8.10.2 Configuring the MPLS Tunnel OAM on a Per-NE Basis.....................................................................................488
8.11 Configuring MPLS-TP Tunnel OAM.......................................................................................................................491
8.11.1 Configuring MPLS-TP Tunnel OAM....................................................................................................................491
8.11.2 Configuring MEPs of MPLS-TP Tunnel OAM....................................................................................................493
8.11.3 Configuring MIPs of MPLS-TP Tunnel OAM......................................................................................................493
8.11.4 Starting CC of MPLS-TP Tunnel OAM................................................................................................................494
8.11.5 Enabling AIS of MPLS-TP Tunnel OAM.............................................................................................................495
8.11.6 Performing LB of MPLS-TP Tunnel OAM..........................................................................................................495
8.11.7 Querying the Status of MPLS-TP Tunnel OAM...................................................................................................497
8.12 Configuring Tunnel APS..........................................................................................................................................497
8.12.1 Configuring a Tunnel APS in End-to-End Mode..................................................................................................498
8.12.2 Configuring Tunnel APS on a Per-NE Basis.........................................................................................................499
8.13 Managing Tunnel APS Protection Groups...............................................................................................................501
8.13.1 Automatically Discovering Protection Groups......................................................................................................501
8.13.2 Deploying Tunnel APS Protection Groups...........................................................................................................502
8.13.3 Renaming a Tunnel APS Protection Group...........................................................................................................502
8.13.4 Deleting Tunnel APS Protection Groups...............................................................................................................503
8.13.5 Deleting Tunnel APS Protection Groups from the Network Side.........................................................................503
8.13.6 Deleting Tunnel APS Protection Groups from the NE Side.................................................................................504
8.14 Configuring ML-PPP................................................................................................................................................504
8.14.1 Changing the E1 Frame Format and Frame Mode for a Channelized STM-1......................................................505
8.14.2 Creating MP Groups..............................................................................................................................................505
8.15 Configuring NE-Level TPID....................................................................................................................................506
8.16 Configuring the Address Resolution........................................................................................................................507
8.17 Configuring E-Line Services....................................................................................................................................508
8.17.1 Creating a QinQ Link............................................................................................................................................508
8.17.2 Creating a VLAN Forwarding Table Item............................................................................................................508
8.17.3 Configuring UNI-UNI E-Line Services................................................................................................................509
8.17.4 Configuring NNI-NNI E-Line Services................................................................................................................510
8.17.5 Configuring E-Line Services Carried by PWs in End-to-End Mode....................................................................511
8.17.6 Configuring E-Line Services Carried by PWs on a Per-NE Basis........................................................................513
8.17.7 Creating UNI-NNI E-Line Services Carried by QinQ Links................................................................................515
8.17.8 Creating E-Line Services over Native Ethernet in End-to-End Mode..................................................................515
8.18 Configuring E-LAN Services...................................................................................................................................519
Transmission System
xii
8.18.1 Configuring IEEE 802.1d Bridge-Based E-LAN Services...................................................................................519
8.18.2 Configuring IEEE 802.1q Bridge-Based E-LAN Services...................................................................................521
8.18.3 Configuring IEEE 802.1ad Bridge-Based E-LAN Services..................................................................................522
8.18.4 Changing Logical Ports Connected to a VB..........................................................................................................524
8.18.5 Creating E-LAN Services over Native Ethernet in End-to-End Mode..................................................................525
8.18.6 Configuring Global Attributes of VPLS Services.................................................................................................529
8.18.7 Creating E-LAN Services Carried by PWs on a Per-NE Basis.............................................................................531
8.18.8 Configuring E-LAN Services Carried by PWs in End-to-End Mode...................................................................533
8.19 Managing the MAC Address Table..........................................................................................................................535
8.19.1 Creating a Static MAC Address Entry..................................................................................................................536
8.19.2 Creating a Blacklist Entry of MAC Addresses......................................................................................................536
8.19.3 Configuring the Aging Parameters of a MAC Address Table...............................................................................537
8.19.4 Querying or Deleting a Dynamic MAC Address..................................................................................................538
8.20 Setting the Mode for Processing an Unknown Frame of the E-LAN Service..........................................................538
8.21 Configuring Transit Nodes for Ethernet Services....................................................................................................539
8.21.1 Configuring Transit NEs for Ethernet Services Carried by Ports..........................................................................539
8.21.2 Configuring Transit NEs for Ethernet Services Carried by PWs..........................................................................540
8.21.3 Configuring Transit NEs for Ethernet Services Carried by QinQ Links...............................................................540
8.22 Configuring a Composite Service.............................................................................................................................541
8.23 Managing Composite Services.................................................................................................................................543
8.23.1 Automatically Discovering Composite Services...................................................................................................543
8.23.2 Deploying Composite Services.............................................................................................................................544
8.24 Operation Tasks for Configuring CES Services.......................................................................................................544
8.24.1 Creating a CES Service in End-to-End Mode.......................................................................................................544
8.24.2 Creating UNI-UNI CES Services on a Per-NE Basis............................................................................................547
8.24.3 Creating UNI-NNI CES Services on a Per-NE Basis............................................................................................547
8.25 Configuring Transit NEs for CES Services..............................................................................................................548
8.26 Managing VPLS Services.........................................................................................................................................548
8.26.1 Checking the VPLS Service Topology..................................................................................................................548
8.26.2 Deploying VPLS Services.....................................................................................................................................549
8.26.3 Modifying VPLS Services.....................................................................................................................................549
8.26.4 Deleting VPLS Services........................................................................................................................................551
8.26.5 Deleting VPLS Services from the Network Side..................................................................................................551
8.27 Managing PWE3 Services........................................................................................................................................552
8.27.1 Checking the PWE3 Service Topology.................................................................................................................552
8.27.2 Deploying PWE3 Services....................................................................................................................................552
8.27.3 Modifying PWE3 Services....................................................................................................................................553
8.27.4 Deleting PWE3 Services.......................................................................................................................................554
8.27.5 Deleting PWE3 Services from the Network Side..................................................................................................555
8.27.6 Deleting PWE3 Services from the NE Side..........................................................................................................555
8.27.7 Managing Discrete PWE3 Services.......................................................................................................................556
Transmission System
xiii
8.28 Managing the QoS....................................................................................................................................................556
8.28.1 Modifying the Mapping Relationships for the DS Domain..................................................................................557
8.28.2 Changing the Ports in a DS Domain and Their Trusted Packet Types..................................................................558
8.28.3 Setting the Port That Uses the Port Policy............................................................................................................559
A Parameter Description.............................................................................................................561
A.1 Parameter Description: Attributes of Ethernet Ports.................................................................................................563
A.1.1 Basic Attributes......................................................................................................................................................563
A.1.2 Layer 2 Attributes...................................................................................................................................................569
A.1.3 Layer 3 Attributes...................................................................................................................................................572
A.1.4 Advanced Attributes...............................................................................................................................................575
A.1.5 Flow Control...........................................................................................................................................................578
A.2 Parameter Description: CES Port..............................................................................................................................580
A.2.1 Channelized STM-1 Port........................................................................................................................................580
A.2.2 E1 Port....................................................................................................................................................................583
A.3 Parameter Description: MPLS...................................................................................................................................587
A.3.1 Basic Configuration................................................................................................................................................587
A.3.2 Parameters for Configuring a Static Tunnel (on a Per-NE Basis)..........................................................................589
A.3.3 Parameters for Configuring a Static Tunnel (in End-to-End Mode)......................................................................595
A.3.4 OAM Parameters....................................................................................................................................................601
A.4 Parameter Description: Address Parse.......................................................................................................................603
A.5 Parameter Description: Ethernet Private Line Services (on a Per-NE Basis)............................................................604
A.5.1 E-Line Service Parameters.....................................................................................................................................604
A.5.2 UNI Parameters......................................................................................................................................................608
A.5.3 NNI Parameters......................................................................................................................................................608
A.5.4 VLAN Forwarding Table Item...............................................................................................................................613
A.5.5 Maintenance Association........................................................................................................................................613
A.5.6 MEP Point...............................................................................................................................................................614
A.6 Parameter Description: E-Line Services (End-to-End Mode)...................................................................................615
A.7 Parameter Description: E-LAN Service (on a Per-NE Basis)...................................................................................629
A.7.1 E-LAN Service Parameters.....................................................................................................................................630
A.7.2 UNI.........................................................................................................................................................................631
A.7.3 NNI.........................................................................................................................................................................632
A.7.4 Split Horizon Group...............................................................................................................................................637
A.7.5 MAC Address Learning Parameters.......................................................................................................................637
A.7.6 Unknown Frame Processing...................................................................................................................................638
A.7.7 Static MAC Address...............................................................................................................................................638
A.8 Parameter Description: E-LAN Services (in End-to-End Mode)..............................................................................639
A.9 Parameter Description: CES Services.......................................................................................................................649
A.9.1 Basic Attributes (UNI-NNI)...................................................................................................................................649
A.9.2 Basic Configuration Parameters (UNI-NNI)..........................................................................................................651
A.9.3 Advanced Attributes (UNI-NNI)............................................................................................................................654
Transmission System
xiv
A.10 Parameters for Configuring CES Services (in End-to-End Mode)..........................................................................660
A.11 Parameter Description: ATM Services....................................................................................................................669
A.11.1 Service Class Mapping Table...............................................................................................................................669
A.11.2 Policy Management..............................................................................................................................................671
A.11.3 Service Management............................................................................................................................................675
A.12 Parameters for Configuring IMA Services (on a Per-NE Basis).............................................................................682
A.12.1 Bound Path............................................................................................................................................................682
A.12.2 IMA Group Management.....................................................................................................................................684
A.12.3 Status of an IMA Group.......................................................................................................................................686
A.12.4 Status of an IMA Link..........................................................................................................................................688
A.12.5 Port Management..................................................................................................................................................690
A.13 Parameter Description: Parameters for Configuring ATM/IMA Services (in End-to-End Mode).........................690
A.14 Parameter Description: ATM OAM Management..................................................................................................699
A.14.1 Segment and End Attribute...................................................................................................................................699
A.14.2 CC Activate Flag..................................................................................................................................................702
A.14.3 Remote End Loopback Status...............................................................................................................................703
A.14.4 LLID.....................................................................................................................................................................704
A.15 Parameter Description: Inband DCN.......................................................................................................................705
A.15.1 Port Settings..........................................................................................................................................................705
A.15.2 Access Control......................................................................................................................................................706
A.15.3 Bandwidth Management.......................................................................................................................................707
A.15.4 Protocol settings....................................................................................................................................................707
A.15.5 Packet Control......................................................................................................................................................708
B Glossary......................................................................................................................................709
Transmission System
xv
1 Getting Started
About This Chapter
The following topics introduce some preparation operations that will ensure a smooth and
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. 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 increases your operation efficiency.
Transmission System
Configuration Guide (Packet Transport Domain) 1 Getting Started
1
1.1 Starting or Shutting Down the U2000
The U2000 uses the standard client/server architecture and multiple-user mode. 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 the U2000 server, and then start the U2000 application.
Prerequisites
l The computer time must be set correctly.
l The computer where the U2000 is installed must be started properly.
l The operating system of the U2000 server must be running properly and the database must
be started properly.
l The U2000 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. Then, click Login to display the
System Monitor window.
NOTE
The default user name is admin. The initial password of the admin user is Changeme_123 (It is
Admin_123 for a U2000 that comes preinstalled). The password must be changed during the first login to
ensure system security. Keep the password confidential and change it regularly.
You can log in to the U2000 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.
Transmission System
2
Prerequisites
The U2000 server must be started properly.
Procedure
Step 1 Double-click the U2000 Client shortcut icon.
Step 2 In the Login dialog box, enter the user name and password. Then, click Login.
NOTE
The default user name is admin. The initial password of the admin user is Changeme_123 (It is
Admin_123 for a U2000 that comes preinstalled). The password must be changed during the first login to
ensure system security. Keep the password confidential and change it regularly.
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.
Prerequisites
The U2000 client must be started properly.
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, the client automatically exits.
----End
1.1.4 Shutting Down the U2000 Server
When the U2000 server is managing the system properly, 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.
Prerequisites
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.
Transmission System
3
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 increases your operation efficiency.
1.2.1 Components of the Client GUI
This topic describes the components of the client GUI.
Figure 1-1 shows the client GUI.
Figure 1-1 Client GUI
1
2
3
4
6
5
1: Menu bar 2: Toolbar 3: Workbench list
4: Output pane 5: Status bar 6: Workbench

Transmission System
4
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.
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.
Transmission System
5
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:
Component Example
Button
Shortcut icon
Radio button
Check box
Tab
Field
Drop-down
menu
Menu
Transmission System
6
Component Example
Function Tree
Dialog box

1.2.3 Frequently Used Buttons
The frequently used buttons on the U2000 GUI are as follows:
Button Functionality
Selects the objects.
Expands all available options.
Collapses all available options.
Displays or hides a dialog box.
Selects the objects.
Transmission System
7
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.
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.
Transmission System
8
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.
Lock Terminal Locks the current client.
Main Topology Switches to the Main Topology.
Log Out Logs out of the current session.
Views the topology
in full screen.
Views the current window in full
screen.
Browse Current
Alarm
Displays the Current Alarms
window.
SDH Protection
Subnet
Maintenance
Accesses the SDH Protection Subnet
Common Attributes window.
SDH Trail
Management
Accesses the SDH Trail
Management window.
Transmission System
9
SDH Trail Creation Accesses the SDH Trail Creation
window.
WDM Trail
Management
Accesses the WDM Trail
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.
View History
Record
Queries the history record of policy
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
Performance
Accesses the Browse SDH
Performance window.
Browse WDM
Performance
Accesses the Browse WDM
Performance window.
Lay Out Lays out the NEs in the topology.
Print and Preview Prints and previews the current
topology view.
Transmission System
10
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.
Topology
Navigator
Views the navigation tree in the
Topology.
View Navigator Views the view navigation tree in the
Topology.
Legend&Filter&At
tribute
Opens the setting area of the view to
display the attribute, filter plane and
legends.
Overview To provide a general view of topology.
NE Statistics Views the quantity of the NE on the
network.
Save the Location
of the Current
Submap Icons
Saves the location of the current
submap icons.
Transmission System
11
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
Sychronization
Synchronizes the NE time and NMS
time.
Synchronize
Current Alarms
Synchronizes the current alarms of an
NE.
Browse Current
ALarms
Browses the current alarms of an NE.
Clear ALarm
Indication
Clears the current alarm indications of
an NE.
Refresh NE Panel
Status
Refreshes the NE panel status to make
the NE panel display the latest data.
Verify
Configuration
Verifies the configuration data. During
the verification, two risky operation
prompts are displayed.
Back Up NE
Database To SCC
Backs up the NE data to the SCC.
Display/Hide
Extended Slot
Displays or hides the extended slot on
the Extended Slot tab page.
Legend Displays a legend and its description.
Shrink all Shrinks Alarm/Event Name.
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
category
Classifies alarms by category.

Transmission System
12
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.
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.
Transmission System
13
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. 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.
Transmission System
14
Figure 1-2 Main Topology
1 2
3
4 5
6 7
8 9
10
11
12

1: Network management
system name
You can change the name for
the NMS.
2: Menu bar
You can operate the NM and
the NE with submenu bar,
include configure tasks,
manage tasks and so on.
3: Shortcut button
Click the button, you can
perform a simple task
quickly. For example: exit
NM, lock terminal, log out,
NMS user management, stop
the current alarm sound,
browse alarm, NE explorer,
creating connections, browse
performance window.
Transmission System
15
4: Shortcut button
Click the button, you can
perform a simple task quickly
on the Main Topology. For
example: zoom in or zoom
out or refresh or save the
view, show or hide the
navigators, search objects,
see object attributes, lock or
unlock the view.
5: Alarm button bar
The Alarm buttons for
alarms at different severity
levels are in different colors.
You can click the button to
view the number of the
alarms generated on the
current U2000. You can click
the button to view current
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.
6: Physical Root
Views all NEs managed by
the NMS. You can locate an
NE quickly from the Physical
Root.
7: Views the current location
of the cursor in the Main
Topology.
8: Physical Map
Views the managed
equipment.
On the Physical Map, you can
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.
9: Views the name which is
set by the current U2000
client, and views the IP
address of the current
U2000 server.
10: Views user name of the
logged-in U2000 user
currently.
11: Filter Tree and Legend
In this area, you can set the
display types of the objects in
a view, and view the
descriptions of legends in the
view. To locate an operation
object quickly.
12: Total elapsed time after
the current user is logged in
to the U2000.

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 operations easy. To display the configuration
Transmission System
16
window for an object, the user can just select the object and then choose a desired function in
the Function Tree.
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 to display the 1.2.6.5 NE Panel.
l Click the in NE Explorer window to switch to other NE.
1.2.6.4 Clock View
The Clock View provides a visible platform to enable NE clock settings, network-wide clock
synchronization status query, and clock tracing and search functions, supports the synchronous
Ethernet clock, 1588 clock, SDH clock, ACR clock, TDM clock, and E1 clock.
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.
l If you move the cursor onto the arrow, the optical port connected to the peer NE is
automatically displayed.
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.
Transmission System
17
NOTE
The rule of verifying an invalid clock tracing relation is as follows: First, verify whether a clock source is in
SSM protocol mode. In non-SSM protocol mode, verify the status of a clock source. The status directly
determines whether a clock tracing relation is invalid. In SSM protocol mode, verify the status of a clock source.
If the status is unavailable, 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 a vacant 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.
1.2.6.6 Browse Alarm
This topic describes the user interface for viewing the current and historical alarms, and 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.
Transmission System
18
GUI
Choose Fault > Browse Event Logs from the main menu.
1.2.6.8 Browse Performance Window
You can view the current and historical performance data, UAT events, and performance
threshold crossings.
GUI
Choose Performance > Browse SDH Performance from the main menu.
Transmission System
19
2 Creating the Network
About This Chapter
NEs and fibers/cables can be managed on the NMS only after their topologies are created.
2.1 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.2 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.3 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.4 Creating an NE User
This topic describes how to create an NE user and assign the user authority on the NMS. To
ensure security of NE data, it is recommended that you assign the user authority according to
the operation scope of the NE user.
2.5 Switching a Logged-In NE User
Different NE administrators cannot log in to or manage an NE by using the same NE user name.
If different NE administrators log in to an NE by using the same NE user name, a later login
forces the NE user that logs in earlier to log out automatically. This topic describes how to switch
the NE user by using the U2000.
2.6 Creating Optical Fibers
Before configuring services on the NMS, you need to create fiber connections between NEs on
the NMS.
2.7 Configuring the Inband DCN
Transmission System
Configuration Guide (Packet Transport Domain) 2 Creating the Network
20
During network planning, you do not need to set up an independent DCN for management and
control. Instead, you can use certain bandwidths of a service network to set up a DCN.
2.8 Synchronizing the NE Time with the NMS
In the case of NEs that do not have the NTP service configured, you need to check whether the
NE time is consistent with the NMS time, so that the NMS can correctly record the time of alarm
generation. Otherwise, manually synchronize the NE time with the NMS.
2.9 Enabling, Disabling, and Setting Performance Monitoring of the NE
By setting performance monitoring parameters of an NE properly and starting the performance
monitoring for the NE, you can obtain the detailed performance record during the running of
the NE. This facilitates the monitoring and analysis of the NE running status performed by
maintenance personnel.
Transmission System
21
2.1 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.
Prerequisites
You must be an NM user with "NM operator" authority or higher.
Background Information
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.2 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.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.
Transmission System
22
Prerequisites
l You are an NM user with Maintenance Group rights or higher.
l The NE Explorer instance of the NEs must be created.
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
NOTE
The IP address of an NE does not need to be manually set and varies with NE IDs. The format of an IP
address is 129.E.A.B. The second number E is the extended ID of the NE, which does not vary with the
NE IDs. The default value is 9. The third number A and fourth number B are the highest eight bits and
lowest eight bits of an NE ID. When the IP address of an NE is manually set, the mapping relationship
between the IP address and NE ID does not exist.
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
with NEs through the IP
protocol
Select IP from the Protocol drop-down list. Set IP
Address of the gateway NE and use the default value of the
Port number.
Transmission System
23
If ... Then ...
The U2000 communicates
with NEs through the OSI
protocol
Select OSI from the Protocol drop-down list. Set NSAP
Address of the gateway NE.

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
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.2.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.
Prerequisites
l You are an NM user with Administrators rights or higher.
l The U2000 must communicate with the gateway NE normally.
Transmission System
24
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.
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. The default value of Search
Address is 129.9.255.255.
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
Transmission System
25
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.3 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.1 Configuring the NE Data Manually
By configuring NE data manually, you can configure the slot layout information of an NE.
Prerequisites
l The NE must be created successfully.
l You are an NM user with Operator Group rights 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.
Transmission System
26
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,
thereby completing the basic configuration of the NEs. After the successful verification, the NEs start to
work normally.
----End
Follow-up Procedure
Configure logical ports for boards.
1. Double-click the configured NE in the Main Topology.
The NE Panel dialog box is displayed.
2. Select a board and then a port for which a logical port is to be configured. Right-click the
port and choose Add Port from the shortcut menu.
The Add Port dialog box is displayed.
3. Configure a logical port according to the board conditions. Then, click OK.
2.3.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.
Prerequisites
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.
Transmission System
27
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.3.3 Uploading the NE Data
By uploading the NE data, you can synchronize the current NE configuration data to the
U2000 directly.
Prerequisites
l The NE has been created successfully.
l The NE software version and NMS software version are correct.
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
Transmission System
28
2.4 Creating an NE User
This topic describes how to create an NE user and assign the user authority on the NMS. To
ensure security of NE data, it is recommended that you assign the user authority according to
the operation scope of the NE user.
Prerequisites
Procedure
Step 1 Choose Administration > NE Security Management > NE User Management from the Main
Menu.
Step 2 Select the NE in the NE Explorer and then click . In the Operation Result dialog box
indicating that the operation succeeded, click Close.
Step 3 Click Add. Then, the Add NE User dialog box is displayed. Set the parameters of the NE user
according to Table 2-1 and Table 2-2.
Table 2-1 NE user levels in a descending order
User Level Authority
Debug Level This user level has all security and configuration authorities, and has the right
to run debugging commands.
System Level This user level has all security and configuration authorities.
Maintenance
Level
This user level has some security authorities, some configuration authorities,
the communication setting authority, and the log management authority.
Operation
Level
This user level has all fault and performance setting authorities, some security
authorities, and some configuration authorities.
Monitor
Level
This user level has the right to use all query commands, to log in, to log out,
and to change its own password.

Table 2-2 NE user flags
NE User Flag Description
LCT NE User Indicates the NE users for NE management on the U2000 Local Craft
Terminal (LCT).
EMS NE User Indicates the NE users for NE management on the U2000.
CMD NE User Indicates the NE users for NE management on the CMD.
Transmission System
29
NE User Flag Description
General NE User Indicates the NE users for all NMS types.

Step 4 After the setting, click OK.
----End
2.5 Switching a Logged-In NE User
Different NE administrators cannot log in to or manage an NE by using the same NE user name.
If different NE administrators log in to an NE by using the same NE user name, a later login
forces the NE user that logs in earlier to log out automatically. This topic describes how to switch
the NE user by using the U2000.
Prerequisites
l More than one NE user must be created.
Procedure
Step 1 Choose Administration > NE Security Management > NE Login Management from the
Main Menu.
Step 2 Select the NE in the NE Explorer and then click .
Step 3 Click the NE Login Management tab and then select the NE from the NE Login Management
Table.
Step 4 Click Switch NE User at the lower right of the window. In the dialog box that is displayed, enter
User and Password of the NE user to switch.
Transmission System
30
----End
2.6 Creating Optical Fibers
Before configuring services on the NMS, you need to create fiber connections between NEs on
the NMS.
2.6.1 Creating Ethernet Fibers and Cables in the Packet Domain by
Means of Search on the NMS
You can detect fiber connections on a specific optical port by performing link search on the
NMS. If a link does not exist on the NMS, you can create the link immediately. To create a
network on the NMS, you can search for fiber connections on all optical ports and create fibers
networkwide after board configuration is completed.
Prerequisites
l Fibers are connected to optical ports on all NEs.
NOTE
Specify the IP address range before IP addresses are automatically allocated to ports. For details on how
to specify the IP address range, see step 1.
Procedure
Step 1 Optional: Set the IP address range for ports.
Transmission System
31
1. Choose Configuration > IP Address Management from the Main Menu.
2. In the displayed dialog box, click New to set the IP address range for ports.
Step 2 Choose File > Discovery > Link from the Main Menu.
Step 3 Optional: In the Link Search window, select one or more options including Links not exist in
the NMS, Links exist in the NMS, Conflicting links, and Links to be deleted. (The first option
is mandatory.)
Step 4 In the left pane, select the optical ports of one or more NEs and click . A progress bar is
displayed to show the link search progress.
Step 5 After the progress is 100% completed, a dialog box is displayed to indicate that the operation is
successful. Click Close.
Step 6 Select one or more links that do not exist on the NMS and click Create.
Step 7 After the creation is completed, a dialog box is displayed to indicate that the operation is
successful. Click Close. The Confirm dialog box is displayed to query "Are you sure to import
links as fibers/cables?"
Step 8 Click OK in the Confirm dialog box. In the displayed Import Link dialog box, select one or
more links.
Step 9 Click OK.
----End
2.6.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.
Prerequisites
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.
Transmission System
32
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.
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 Result dialog
box is displayed, indicating the information on the fiber connections.
----End
2.7 Configuring the Inband DCN
During network planning, you do not need to set up an independent DCN for management and
control. Instead, you can use certain bandwidths of a service network to set up a DCN.
Transmission System
33
2.7.1 Setting the VLAN ID and Bandwidth Used by an Inband DCN
If the equipment communicates with the NMS through the inband DCN, the network
management information is transmitted with the service information. In this case, the equipment
identifies the management information through a default VLAN ID. The bandwidth used by an
inband DCN can be adjusted according to the network status.
Prerequisites
You are an NM user with Maintenance Group rights or higher.
Context
l If the default VLAN ID of the inband DCN conflicts with the VLAN ID used by the service,
you can manually modify the VLAN ID of the inband DCN. Ensure that the DCNs on the
entire network use the same VLAN ID.
l If the DCN packet does not use all the preset bandwidth, the idle bandwidth can be shared
with the service packet.
l It is recommended that you perform modification first on the non-gateway NEs and then
on the gateway NE to prevent the non-gateway NEs from being unreachable to the NMS.
Procedure
Step 1 In the NE Explorer, select the NE and choose Communication > DCN Management from the
Function Tree.
Step 2 Click the Bandwidth Management tab, and set the required parameters.
NOTE
When you set these parameters, pay attention to the following points:
l Click Default, and the parameter takes the default value.
l Generally, use the default VLAN ID (4094). When the VLAN ID used by the service conflicts with
the VLAN ID used by a DCN channel, define another VLAN ID for the DCN channel. Ensure that the
DCN channels on the entire network use the same VLAN ID.
l The bandwidth ranges from 64 Mbit/s to 1000 Mbit/s. It is recommended that you set the bandwidth
to a value greater than 512 Mbit/s. Otherwise, the network management information is transmitted at
a low rate.
Step 3 Click Apply.
----End
2.7.2 Setting the Parameters for NMS Access
On a traditional DCN, the equipment is connected to the NMS through the SCC board. The
OptiX OSN equipment can also be connected to the NMS through the NM interface on the
Ethernet board. In this case, set the parameters of the Ethernet board for NM access so that the
equipment can normally communicate with the NMS.
Prerequisites
Transmission System
34
Precautions
NOTE
l Set these parameters only when the equipment is connected to the NMS through the Ethernet service
board.
l By default, Enabled Status is set to Disabled.
NOTICE
When the DCN port is interconnected with the NMS, the IP address of the NMS and the IP
address of the NNI on the equipment must be set to the same segment.
Procedure
Function Tree.
Step 2 Click the Access Control tab, and set the required parameters.
Step 3 Click Apply.
----End
2.7.3 Enabling the DCN Function for a Port
The network management information can be transmitted over the inband DCN when the DCN
function is enabled for the ports at both ends of a link.
Prerequisites
l When you configure an Ethernet service that exclusively occupies a port, disable the DCN
function of the port.
Procedure
Function Tree.
Step 2 Click the Port Settings tab.
Step 3 In the corresponding Enabled Status field of the related port, select Enabled.
Step 4 Click Apply.
----End
2.7.4 Setting the Protocol Stack Used by an Inband DCN
Inband DCN packets can be transmitted through the IP protocol or HWECC protocol.
Transmission System
35
Prerequisites
Procedure
Function Tree.
Step 2 Click the Protocol Settings tab. Set Protocol Type of the corresponding port.
NOTE
The HWECC protocol is an internal protocol of Huawei and is applicable to the Huawei equipment. When
inband DCN packets need to pass through the third-party network, you need to set Protocol Type to IP.
Step 3 Click Apply.
----End
2.7.5 Setting Inband DCN Packet Priority
This section describes how to set the inband DCN packet priority. When a network congestion
occurs, DCN packets are forwarded based on priority to ensure the communication between the
equipment and the NMS.
Prerequisites
Procedure
Step 1 Select the NE in the NE Explorer. Choose Communication > DCN Management from the
Function Tree.
Step 2 Select the Packet Control tab, and set Packet Priority of corresponding ports. For how to set
the parameter, see A.15.5 Packet Control.
Step 3 Click Apply.
----End
2.7.6 Verifying the Inband DCN
To check whether the configured inband DCN functions normally, verify whether all the basic
functions of the inband DCN are available.
Prerequisites
The inband DCN must be configured.
You can verify the MPLS APS in the following aspects:
Transmission System
36
l Create a non-gateway NE by using the U2000. After the creation, the user can log in to the
non-gateway NE and can upload the data of the NE to the U2000.
l Query the DCN management information about the non-gateway NE by using the
U2000. The inband DCN should be configured correctly.
l Change the parameters of the DCN, such as the protocol mode. The inband DCN should
function normally.
Procedure
Step 1 Create a non-gateway NE by using the U2000. After the creation, the user can log in to the non-
gateway NE and can upload the data of the NE to the U2000.
NOTE
Set Gateway Type to Non-Gateway, and then set Affiliated Gateway to the gateway NE on the inband
DCN.
Step 2 Query the DCN management information about the non-gateway NE by using the U2000. The
inband DCN should be configured correctly.
1. In the Main Menu, choose Administration > DCN Management.
2. Choose Filter Information in the Filter NE tab, then click OK.
3. Click the NE tab.
4. Click Refresh to check whether the Communication Status of the non-gateway NE is
Normal.
Step 3 Change the parameters of the DCN, such as the protocol mode. The inband DCN should function
normally.
NOTE
On a network where the inband DCN communications are adopted, the parameters of all the NEs must be
the same. The parameters such as the DCN protocol mode of non-gateway NEs need to be changed before
the parameters such as the DCN protocol mode of the gateway NEs are changed.
1. In the Main Topology, right-click the NE to be configured, and then choose NE
Explorer from the shortcut menu.
2. In the NE Explorer, select the NE to be configured, and then choose Communication >
DCN Management from the Function Tree.
3. Change the parameters, such as Bandwidth and Protocol Type.
4. Click Apply.
----End
Follow-up Procedure
If testing the inband DCN fails, rectify faults by referring to Troubleshooting.
2.8 Synchronizing the NE Time with the NMS
In the case of NEs that do not have the NTP service configured, you need to check whether the
NE time is consistent with the NMS time, so that the NMS can correctly record the time of alarm
generation. Otherwise, manually synchronize the NE time with the NMS.
Transmission System
37
Prerequisites
l The U2000 must be started at the center.
Maintenance Period
Daily
Tools, Equipment, and Materials
U2000
Precautions
NOTE
Synchronizing the NE time does not affect services. Before synchronizing the NE time, verify that the
system time on the NMS server is correct.
If you want to change the system time, exit the U2000 to reset the time and then start the NMS again.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 In the Object Tree, select one or more NEs and click .
Step 3 Click Close in the Operation Result dialog box indicating that the operation succeeded.
Step 4 Select one or more NEs in the list, right-click and choose Synchronize with NM Time from
the shortcut menu.
Step 5 Click Yes in the Time Synchronization Operation prompt box. Click Close in the Operation
Result dialog box indicating that the operation succeeded.
----End
2.9 Enabling, Disabling, and Setting Performance
Monitoring of the NE
By setting performance monitoring parameters of an NE properly and starting the performance
monitoring for the NE, you can obtain the detailed performance record during the running of
the NE. This facilitates the monitoring and analysis of the NE running status performed by
maintenance personnel.
Prerequisites
You are an NM user with Operator Group rights or higher.
NE time is synchronized with the U2000 server.
Transmission System
38
Impact on System
None.
U2000
Procedure
Step 1 Choose Performance > Set NE Performance Monitoring Time from the Main Menu.
Step 2 Select one or more NEs from the NE list. Click .
Step 3 Set the performance monitoring parameters according to the requirements.
1. Select Enabled or Disablein Set 15-Minute Monitoring or Set 24-Hour Monitoring to
enable/disable the monitoring of the NE performance.
2. Optional: Select 15-Minute or 24-Hour to set the monitoring period of the NE
performance.
3. Optional: Set the start time and end time of the performance monitoring.
NOTE
l The start time must be later than the current time of the network management system and the end
time must be later than the start time.
l If the end time is not set, the performance monitoring starts from the start time and does not stop.
Step 4 Click Apply and click Close in the Operation Result dialog box.
----End
Transmission System
39
3 Configuring ETH PWE3 Services
About This Chapter
You can configure the E-Line services to realize the point-to-point transmission of Ethernet
services. You can configure the E-LAN services to realize the multipoint-to-multipoint
transmission of Ethernet services.
3.1 Basic Concepts
Learning about the basic concepts helps to further understand Ethernet services.
3.2 Configuration Flow
The flowchart for configuring an ETH PWE3 service differs according to the type of the ETH
PWE3 service.
3.3 Configuration Example: E-Line Services Carried by PWs(Based on VLANs)
This topic uses an example to describe how to plan the engineering information and how to
configure the E-Line services carried by PWs for each NE according to the networking diagram.
3.4 Configuration Example: E-Line Services Carried by PWs (Based on VLAN Priorities)
In this example, services with a same VLAN ID but different VLAN priorities need to be mapped
to different PWs.
3.5 Configuration Example: E-Line Services Carried by PWs (Based on VLAN Switching)
configure the E-Line services carried by PWs (based on VLAN switching) for each NE according
to the networking diagram.
3.6 Configuration Example (E-LAN Services Carried by PWs)
This section uses an example to describe how to plan the engineering information and how to
configure E-LAN services carried by PWs on each NE according to the networking diagram.
Transmission System
Configuration Guide (Packet Transport Domain) 3 Configuring ETH PWE3 Services
40
3.1 Basic Concepts
Learning about the basic concepts helps to further understand Ethernet services.
3.1.1 E-Line Services Carried by PWs
In the topology, the E-Line services are point-to-point services. The E-Line services realize the
point-to-point transmission of Ethernet services.
E-Line Services Carried by PWs (Based on VLANs)
Figure 3-1 shows the networking diagram of the E-Line services carried by PWs.
The branches of Company A and Company B are located in City 1 and City 2, and need to
communicate with each other. The services of Company A and Company B need to be isolated
from each other. In this case, you can configure the E-Line services that are carried by PWs and
from the user side to the network side, to realize the communication between the branches of
Company A or Company B. In addition, different services are carried by different PWs, therefore
realizing the isolation of the services of Company A from the services of Company B.
The services that are accessed from the user side are encapsulated and transmitted to the PWs.
Then, the services are transmitted through the tunnel.
The E-Line services of different companies are carried by different PWs and then to the same
port on the network side. In this manner, the port resources on the network side are saved and
the bandwidth utilization is increased. In the uplink direction of the user side, layered QoS
configuration can be performed for data packets.
Figure 3-1 E-Line services carried by PWs (based on VLANs)
Company A
City2
Tunnel
PW
Company B
Company A
City1
Company B
PSN
NNI UNI
NE 1
NE2
NNI UNI
VLAN: 100
VLAN: 200

E-Line Services Carried by PWs (Based on VLAN Priorities)
Figure 3-2 shows the networking diagram of the E-Line services carried by PWs (based on
VLAN priorities). This type of E-Line maps packets with a same VLAN ID but different VLAN
priorities to different PWs.
Transmission System
41
Services from NodeB 1 and services from NodeB 2 have a same VLAN ID of 100 but different
VLAN priorities, and need to be transported to a same RNC. Services from NodeB 1 have a
VLAN priority of 3, and services from NodeB 2 have a VLAN priority of 2. To isolate services
from NodeB 1 and services from NodeB 2, the services are mapped to different PWs based on
Port+VLAN+VLAN PRI before being transported to the RNC.
The services that are received from the UNI are encapsulated into PWs and then carried on
tunnels. In the uplink direction of the UNI, hierarchical QoS configuration can be performed for
data packets.
Figure 3-2 E-Line services carried by PWs (based on VLAN priorities)
E-Line Services Carried by PWs (Based on VLAN Switching)
Figure 3-3 shows the networking diagram for E-Line services carried by PWs (based on VLAN
switching). To transport different NodeBs' services that have a same VLAN ID but are previously
transported to different RNCs to a same RNC, this type of E-Line services enables VLAN
switching to differentiate the services before they are transported to the RNC.
Services from NodeB 1 and services from NodeB 2 have a same VLAN ID of 100, and need to
be transported to a same RNC. To differentiate services from NodeB 1 and services from NodeB
2, VLAN switching is required. After VLAN switching, the VLAN ID of services from NodeB
1 remains unchanged, whereas the VLAN ID of services from NodeB 2 is changed to 200.
The services that are received from the UNI are encapsulated into PWs and then carried on
tunnels. In the uplink direction of the UNI, hierarchical QoS configuration can be performed for
data packets.
Transmission System
42
Figure 3-3 E-Line services carried by PWs (based on VLAN switching)
3.1.2 E-LAN Services Carried on PWs
The PW-carried E-LAN services are point-to-multipoint and multipoint-to-multipoint services.
The equipment realizes the point-to-multipoint and multipoint-to-multipoint transmission of
Ethernet services through the E-LAN.
Service Models
Table 3-1 defines the PW-carried E-LAN service models.
Table 3-1 PW-carried E-LAN service models
Service Model Service Flow Service
Direction
Port Mode Port
Encapsulation
Type
Description
Model 1 PORT+C-
VLAN (source)
PW (sink)
UNI-NNI Layer 2 (source)
Layer 3 (sink)
IEEE 802.1q
(source)
- (sink)
A UNI port
processes the
packets carrying
a specific C-
VLAN ID based
on its tag
attribute and
then sends the
packets to the
NNI side for
transmission on
PWs.
Transmission System
43
Service Model Service Flow Service
Direction
Port Mode Port
Encapsulation
Type
Description
Model 2 PORT+S-
VLAN (source)
PW (sink)
Layer 3 (sink)
QinQ (sink)
- (sink)
A UNI port
processes the
packets carrying
a specific S-
VLAN ID based
on its QinQ type
field, and then
sends the
packets to the
NNI side for
transmission on
PWs.
Model 3 PORT (source)
PW (sink)
Layer 3 (sink)
IEEE 802.1q or
QinQ (source)
- (sink)
A UNI port
processes the
received packets
based on its tag
attribute or
QinQ type field,
and then sends
the packets to
the NNI side for
transmission on
PWs.

Typical Application
Figure 3-4 shows the typical application of service model 1. Branch A and Branch B do not
communicate with each other, and the data of them should be separated from each other. The
headquarter, however, needs to communicate with all the branches.
Service 1 is present between Branch A and Branch A, service 2 is present between Branch B
and Branch B, and the two services are present between branches and headquarter, The two
services carry different VLAN IDs and need to be transmitted over a PSN.
On the UNI side of NE1, service 1 is received by port 1 and service 2 is received by port 2. On
the NNI side of NE1, service 1 and service 2 are transmitted separately on two PWs.
On the UNI side of NE2, service 1 and service 2 are received by port 1. On the NNI side of NE2,
service 1 and service 2 are transmitted separately on two PWs.
NE3 processes the two services in the same manner as NE1.
Transmission System
44
Figure 3-4 Typical application of service model 1
PSN
NE1 NE2
LSP
AC
AC
AC
Branch A
UNI NNI NNI
UNI
Port: 1(802.1Q)
VLAN ID: 100
Service 1
Port: 1(802.1Q)
VLAN ID: 100, 200
Service 1, 2
Port: 2(802.1Q)
VLAN ID: 200
Service 2
Branch B
NNI
UNI
Headquarter
Branch A Branch B
AC
AC
Port: 2(802.1Q)
VLAN ID: 200
Service 2
Port: 1(802.1Q)
VLAN ID: 100
Service 1
Packet transmission equipment
PW1
PW2
P
W
3
P
W
4
P
W
3
P
W
4

and Branch B, and the two QinQ services are present between branches and headquarter, The
two services carry different S-VLAN IDs and need to be transmitted over a PSN.
On the UNI side of NE2, service 1 and service 2 are received by port 1. On the NNI side of NE2,
service 1 and service 2 are transmitted separately on two PWs.
NE3 processes the two services in the same manner as NE1.
Transmission System
45
PSN
NE1 NE2
LSP
AC
AC
AC
Branch A
UNI NNI NNI
UNI
Port: 1(QinQ)
S-VLAN ID: 100
Service 1
Port: 1(QinQ)
S-VLAN ID: 100, 200
Service 1, 2
Port: 2(QinQ)
S-VLAN ID: 200
Service 2
Branch B
NNI
UNI
Headquarter
Branch A Branch B
AC
AC
Port: 2(QinQ)
S-VLAN ID: 200
Service 2
Port: 1(QinQ)
S-VLAN ID: 100
Service 1
PW1
PW2
P
W
3
P
W
4
P
W
3
P
W
4

and Branch B, and the two QinQ services are present between branches and headquarter, Service
1 carries various C-VLAN IDs, and service 2 carries various S-VLAN IDs. The two services
need to be transmitted over a PSN.
NE3 and NE3 process the two services in the same manner as NE1.
Transmission System
46
PSN
NE1 NE2
LSP
AC
AC
AC
Branch A
UNI NNI NNI UNI
Port: 1(802.1Q)
Service 1
Port: 1(802.1Q)
Service 1
Port: 2(QinQ)
Service 2
Branch B
NNI
UNI
Headquarter
Branch A Branch B
AC
AC
Port: 2(QinQ)
Service 2
Port: 1(802.1Q)
Service 1
Port: 2(QinQ)
Service 2
PW1
PW2
P
W
3
P
W
4
P
W
3
P
W
4

3.1.3 Ethernet Port
This section describes user-to-network interfaces (UNIs) that are connected to user equipment
and network-to-network interfaces (NNIs) that are connected to the packet transport network on
a network deployed with E-Line and E-LAN services.
UNI
A UNI refers to the Ethernet port that is connected to user equipment. A UNI is a physical port
and it is used for the user-side configuration of an Ethernet service.
A V-UNI is a logical virtual user-network interface. Each service on a UNI corresponds to a
logical V-UNI.
A UNI can receive multiple services, which means that a UNI may correspond to multiple V-
UNIs.
NNI
An NNI refers to the Ethernet port that is connected to the packet transport network. An NNI is
used for the network-side configuration of an Ethernet service.
To transmit PW-carried Ethernet services, create static MPLS tunnels at NNIs and then create
PWs to carry Ethernet services. This method enables different Ethernet services to be
encapsulated into different PWs and transmitted in a tunnel to the same NNI, decreasing the
number of occupied NNIs and improving bandwidth utilization.
Transmission System
47
3.1.4 VPLS
Virtual private LAN service (VPLS), also called transparent LAN service (TLS) or virtual
private switched network service, is a Layer 2 virtual private network (L2VPN) technology that
is based on Multiprotocol Label Switching (MPLS) and Ethernet technologies.
VPLS helps service providers provide users with Ethernet-based multipoint services over MPLS
backbone networks.
VPLS has the following basic concepts:
l Pseudo wire (PW): A PW is an emulated connection between two provider edge (PE) nodes
for transmitting frames. PWs are established and maintained by PE nodes through signaling
protocols. The status information of a PW is maintained by the two end PE nodes of a PW.
l Virtual switch instance (VSI): Each VSI provides independent VPLS services. VSIs have
Ethernet bridge functions and can terminate PWs.
3.1.5 Split Horizon Group
Convergence services received from different ports are isolated to prevent a broadcast storm
resulting from a service loop and improve service security. To implement service isolation, you
can configure a split horizon group for the E-LAN services at the specified nodes. The logical
ports in one split horizon group cannot forward packets to each other.
Figure 3-7 shows a typical application of the split horizon group. NEs on the network are
configured with E-LAN services, and the east and west ports and service access ports are
configured as mounted ports of a bridge. In this case, if a split horizon group is not configured
at NE1, broadcast storm occurs due to a network loop as the east and west ports can forward
packets to each other. If a split horizon group is created at NE1 and the east and west ports are
configured as members of the split horizon group, the east and west ports do not forward packets
to each other. Therefore, a service loop is prevented.
Figure 3-7 Split horizon group

Transmission System
48
3.2 Configuration Flow
The flowchart for configuring an ETH PWE3 service differs according to the type of the ETH
PWE3 service.
3.2.1 E-Line Services Carried by PWs
You need to configure the MPLS tunnel before configuring the E-Line services carried by PWs.
Table 3-2 describes the procedure for configuring the E-Line services carried by PWs.
Figure 3-8 Flow chart for configuring the E-Line services carried by PWs
Configure the UNI
Configuring the DCN
Function of a Port
Start
Required
Optional
End
Configure the QoS
Configure the NNI for
the services carried by
the static MPLS tunnel
Configure the MPLS
tunnel
Create the E-Line
services carried by
PWs

Transmission System
49
Table 3-2 Procedure for configuring the E-Line services carried by PWs
S
t
e
p
Operation Remarks
1 Configuring the UNI
(when the UNI is an
Ethernet port)
8.1.1 Setting the
General
Attributes of
Ethernet
Interfaces
Required.
The parameters are set as follows:
l Enable Port is set to Enabled.
l Port Mode is set to Layer 2.
l Generally, Encapsulation Type is set to
802.1Q. When the packets do not need to
be distinguished by VLAN tag,
Encapsulation Type is set to Null.
l Working Mode of the UNI needs to be the
same as the working mode of the Ethernet
equipment on the opposite end. Generally,
this parameter takes the default value
Auto-Negotiation.
l When JUMBO frames do not need to be
transmitted, Max Frame Length(byte)
takes the default value 1620. In other cases,
Max Frame Length(byte) is set to the
maximum length of the transmitted
JUMBO frames.
8.1.2 Setting the
Layer 2
Attributes of
Ethernet Ports
Optional.
l Tag needs to be set based on the type of
the packets that are transmitted from the
equipment on the opposite end.
If all the packets are untagged packets,
Tag is set to Access.
If all the packets are tagged packets,
Tag is set to Tag Aware.
If the packets contain untagged packets
and tagged packets, Tag is set to
Hybrid.
l When Tag is set to Access or Hybrid,
Default VLAN ID and VLAN Priority
need to be set for the untagged frames.
VLAN Priority needs to be set based on
the planned QoS.
Transmission System
50
S
t
e
p
Operation Remarks
8.1.5
Configuring
Flow Control
Optional.
l Generally, the PSN uses the QoS scheme
to prevent link congestion. Hence, Auto-
Negotiation Flow Control Mode and
Non-Autonegotiation Flow Control
Mode need to be set to the default value
Disabled, unless otherwise specified.
2 Configuring the DCN Function for a
Port
Optional.
This operation is applicable only when the
UNI is an Ethernet port. The parameters are
set as follows:
l The UNI is used for connecting the
external equipment and does not need to
transmit in-band DCN information.
Hence, Enable Port needs to be set to
Disabled for the UNI.
3 8.2.1 Configuring the NNIs for
Ethernet Services Carried by PWs
Required.
The parameters need to be set according to the
service planning.
l Enable Tunnel is set to Enabled.
l Specify IP Address is set to Manually and
IP Address and IP Mask need to be set
according to the service planning.
4 Config
uring
the
MPLS
tunnel
8.8 Configuring an MPLS
Tunnel
Required.
service planning.
Configuri
ng tunnel
OAM
8.10
Configuring
MPLS Tunnel
OAM
NOTE
Only OptiX OSN
550 and OptiX
OSN 500 support
MPLS Tunnel
OAM. OptiX
OSN 580 only
supports MPLS-
TP OAM.
Optional.
To ensure protection switching time within 50
ms, set Detection Packet Type to FFD and
Detection Packet Interval (ms) to 3.3. The
parameters are set as follows:
l OAM Status is set to Enabled.
l Detection Mode is set to Manual.
l Detection Packet Type is set to FFD.
l Detection Packet Period(ms) is set to
3.3.
Transmission System
51
S
t
e
p
Operation Remarks
NOTE
Configur
e MPLS
tunnel
OAM or
MPLS-
TP tunnel
OAM
accordin
g to the
service
plan.
8.11
Configuring
MPLS-TP
Tunnel OAM
(Optional) The parameters are set as follows:
l Set OAM Status to Enabled.
l If all the NEs along a tunnel are Huawei
equipment that supports IP-based MPLS-
TP OAM, it is recommended that you set
MEG ID Type to IP Based, so that you do
not need to plan MEG IDs, MEP IDs, and
RMEP IDs.
l If not all the NEs along a tunnel are Huawei
TP OAM or if there are special
requirements, it is recommended that you
set MEG ID Type to ICC Based. In this
case, plan MEG IDs, MEP IDs, and RMEP
IDs based on the following principles:
All the MEPs and MIPs along the same
tunnel must have the same MEG ID.
MEPs and MIPs along different tunnels
must have different MEG IDs.
Each MEP ID in an MEG must be
unique.
l It is recommended that you set this
parameter to the default value 7.
parameter to the default value Adaptive.
Detection Mode can be set only for ingress
nodes on bidirectional tunnels and egress
nodes.
l It is recommended that you retain the
default value 0 for both SD Threshold
(%) and SF Threshold(%).
l To suppress a PW fault alarm caused by a
tunnel fault on an NE on which an MS-PW
is configured, set AIS Status to Enabled.
l Set CC Packet Interval (ms) as follows:
If the CC function is used to trigger
APS, it is recommended that you set
CC Packet Interval(ms) to 3.33.
If the packet transmission delay
variation exceeds 3.33 ms, it is
recommended that you set CC Packet
Transmission System
52
S
t
e
p
Operation Remarks
Interval(ms) to a value greater than the
packet transmission delay variation.
If the CC function is used to check the
tunnel connectivity, it is recommended
that you set CC Packet Interval(ms)
to 1000.
CC Packet Interval(ms) can be set only
for egress nodes on bidirectional tunnels
and ingress nodes.
l It is recommended that you set CC Packet
Priority to the default value 7.CC Packet
Priority can be set only for egress nodes
on bidirectional tunnels and ingress nodes.
8.12 Configuring Tunnel
APS
Optional.
The tunnel APS parameters need to be set
NOTE
Tunnel APS is not used, select PW APS for service
protection. For the configuration of PW APS, see
Configuring PW APS.
5 Create
the E-
Line
service
s
carried
by
PWs
8.17.6 Configuring E-Line
Services Carried by PWs on
a Per-NE Basis
Required.
service planning. Follow instructions in 8.27
Managing PWE3 Services to manage PW-
carried Ethernet services.
8.17.5 Configuring E-Line
Services Carried by PWs in
End-to-End Mode
6 Configuring the QoS Feature Optional.
service QoS planning.

3.2.2 E-LAN Services Carried by PWs
You need to configure the MPLS tunnel before configuring the E-LAN services carried by PWs.
Table 3-3 describes the procedure for configuring the E-LAN services carried by PWs.
Transmission System
53
Figure 3-9 Flow chart for configuring the E-LAN services carried by PWs
Configure the UNI
Configuring the DCN
Function of a Port
Start
Required
Optional
End
Configure the QoS
Configure the MPLS
tunnel
Create the E-LAN
services carried by
PWs
Configuring Global
Attributes of VPLS
Services

Transmission System
54
Table 3-3 Procedure for configuring the E-LAN services carried by PWs
S
t
e
p
Operation Remarks
1 Configuring the UNI
(when the UNI is an
Ethernet port)
8.1.1 Setting the
General
Attributes of
Ethernet
Interfaces
Required.
l Enable Port is set to Enabled.
l Generally, Encapsulation Type is set to
802.1Q. When the packets do not need to
be distinguished by VLAN tag,
Encapsulation Type is set to Null.
l Working Mode of the UNI needs to be the
same as the working mode of the Ethernet
equipment on the opposite end. Generally,
this parameter takes the default value
Auto-Negotiation.
l When JUMBO frames do not need to be
transmitted, Max Frame Length(byte)
takes the default value 1620. In other cases,
Max Frame Length(byte) is set to the
maximum length of the transmitted
JUMBO frames.
8.1.2 Setting the
Layer 2
Attributes of
Ethernet Ports
Optional.
l Tag needs to be set based on the type of
the packets that are transmitted from the
equipment on the opposite end.
If all the packets are untagged packets,
Tag is set to Access.
If all the packets are tagged packets,
Tag is set to Tag Aware.
If the packets contain untagged packets
and tagged packets, Tag is set to
Hybrid.
l When Tag is set to Access or Hybrid,
Default VLAN ID and VLAN Priority
need to be set for the untagged frames.
VLAN Priority needs to be set based on
the planned QoS.
Transmission System
55
S
t
e
p
Operation Remarks
8.1.5
Configuring
Flow Control
Optional.
l Generally, the PSN uses the QoS scheme
to prevent link congestion. Hence, Auto-
Negotiation Flow Control Mode and
Non-Autonegotiation Flow Control
Mode need to be set to the default value
Disabled, unless otherwise specified.
2 Configuring the DCN Function for a
Port
Optional.
This operation is applicable only when the
UNI is an Ethernet port. The parameters are
set as follows:
l The UNI is used for connecting the
external equipment and does not need to
transmit in-band DCN information.
Hence, Enable Port needs to be set to
Disabled for the UNI.
3 8.2.1 Configuring the NNIs for
Ethernet Services Carried by PWs
Required.
service planning.
l Enable Tunnel is set to Enabled.
l Specify IP Address is set to Manually and
IP Address and IP Mask need to be set
4 8.18.6 Configuring Global Attributes
of VPLS Services
NOTE
This step is required for OptiX OSN 550 and
OptiX OSN 500. Skip this step for OptiX
OSN 580.
Optional.
service planning.
5 Config
uring
the
MPLS
tunnel
Tunnel
Required.
service planning.
Transmission System
56
S
t
e
p
Operation Remarks
Configuri
ng tunnel
OAM
NOTE
Configur
e MPLS
tunnel
OAM or
MPLS-
TP tunnel
OAM
accordin
g to the
service
plan.
8.10
Configuring
MPLS Tunnel
OAM
NOTE
Only OptiX OSN
550 and OptiX
OSN 500 support
MPLS Tunnel
OAM. OptiX
OSN 580 only
supports MPLS-
TP OAM.
Optional.
To ensure protection switching time within 50
ms, set Detection Packet Type to FFD and
Detection Packet Interval (ms) to 3.3. The
parameters are set as follows:
3.3.
Transmission System
57
S
t
e
p
Operation Remarks
8.11
Configuring
MPLS-TP
Tunnel OAM
MEG ID Type to IP Based, so that you do
not need to plan MEG IDs, MEP IDs, and
RMEP IDs.
TP OAM or if there are special
requirements, it is recommended that you
set MEG ID Type to ICC Based. In this
case, plan MEG IDs, MEP IDs, and RMEP
IDs based on the following principles:
tunnel must have the same MEG ID.
MEPs and MIPs along different tunnels
must have different MEG IDs.
unique.
nodes.
tunnel fault on an NE on which an MS-PW
is configured, set AIS Status to Enabled.
Transmission System
58
S
t
e
p
Operation Remarks
Interval(ms) to a value greater than the
packet transmission delay variation.
that you set CC Packet Interval(ms)
to 1000.
and ingress nodes.
Priority can be set only for egress nodes
on bidirectional tunnels and ingress nodes.
APS
Optional.
The tunnel APS parameters need to be set
NOTE
Configuring PW APS.
6 Create
the E-
LAN
service
s
carried
by
PWs
8.18.7 Creating E-LAN
Services Carried by PWs on
a Per-NE Basis
Required. The parameters need to be set
Set MAC Address Self-Learning to SVL.
Follow instructions in 8.26 Managing VPLS
Services to manage PW-carried Ethernet
services.
8.18.8 Configuring E-LAN
Services Carried by PWs in
End-to-End Mode
7 Configuring the QoS Feature Optional.
service QoS planning.

3.3 Configuration Example: E-Line Services Carried by PWs
(Based on VLANs)
Transmission System
59
3.3.1 Networking Diagram
The networking diagram shows the requirements for the E-Line services carried by PWs (based
on VLANs).
On the network shown in Figure 3-10, the service requirements of User A and User B are as
follows:
l User A1 and User B1 are connected to NE1 through the 4-EM6F-3 and 4-EM6F-4 ports
respectively.
l User A2 and User B2 are connected to NE4 through the 4-EM6F-3 and 4-EM6F-4 ports
respectively.
l The service between User A1 and User A2 is the common Internet access service of which
the CIR is 10 Mbit/s and the PIR is 30 Mbit/s.
l The service between User B1 and User B2 is the data service of which the CIR is 30 Mbit/
s and the PIR is 50 Mbit/s.
l The services of User A and User B each are carried on one PW link.
l The two PW links that carry the services of User A and User B share the bandwidth of one
tunnel.
l The service between User A and User B is configured with MPLS tunnel APS.
Working path: NE1-NE2-NE4
Protection path: NE1-NE3-NE4
Figure 3-10 Networking diagram of the E-Line services carried by PWs (based on VLANs)
User A2 User A1
User B1
User B2
UNI for A1:4-EM6F-3
UNI for B1:4-EM6F-4
MPLS Tunnel
PW
PSN
NNI:4-EM6F-2
UNI for A2:4-EM6F-3
UNI for B2:4-EM6F-4
NE1 NE4
NE2
NNI:4-EM6F-1
NNI:4-EM6F-2
NNI:4-EM6F-1
NNI:4-EM6F-2
NNI:4-EM6F-1
NE3
NOTE
l This topic considers the OptiX OSN 550 as an example to describe the board layout. In the case of
other products, the configuration method is the same, except for the slots. For the slot information, see
the Hardware Description of the relevant product.
l On a live data network, an Ethernet service is added to the source NE, passed through the transit NEs,
and dropped from the sink NE. Follow instructions in 8.21.2 Configuring Transit NEs for Ethernet
Services Carried by PWs to configure transit NEs for the Ethernet services carried by PWs.
Transmission System
60
NE IP Address IP Mask LSR ID
NE1 4-
EM6F-1
18.1.1.1 255.255.255.252 130.0.0.1
4-
EM6F-2
18.1.2.1 255.255.255.252
NE2 4-
EM6F-1
18.1.1.2 255.255.255.252 130.0.0.2
4-
EM6F-2
18.1.1.5 255.255.255.252
NE3 4-
EM6F-1
18.1.2.2 255.255.255.252 130.0.0.3
4-
EM6F-2
18.1.2.5 255.255.255.252
NE4 4-
EM6F-1
18.1.1.6 255.255.255.252 130.0.0.4
4-
EM6F-2
18.1.2.6 255.255.255.252

NOTE
l The IP addresses of the Ethernet ports on an NE cannot be in the same network segment.
l The IP addresses of the ports at both ends of a tunnel cannot be in the same network segment.

3.3.2 Service Planning
The engineering information for configuring the E-Line services carried by PWs contains the
engineering information for configuring the tunnel carrying the PWs, the engineering
information for configuring the PWs, and the engineering information for configuring the UNI-
NNI E-Line services carried by the PWs.
The PWs that carry the E-Line services are carried by a tunnel. Hence, you need to plan the
tunnel during the service planning. Therefore, planning the E-Line services carried by PWs
involves the following:
l Plan the tunnel that carries the PWs. Refer to Table 3-4 and Table 3-5.
l Plan MPLS tunnel OAM. Refer to Table 3-6.
l Plan MPLS tunnel APS. Refer to Table 3-7.
l Plan the PWs. Refer to Table 3-8.
l Plan the UNI-NNI E-Line services carried by PWs. Refer to Table 3-9.
Transmission System
61
Table 3-4 Basic attributes of the MPLS tunnels
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Protocol Type Signaling
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
10 MPLS Static CR Bidirec
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

Table 3-5 Parameters of the MPLS tunnels
M
P
L
S
T
u
n
n
el
I
D
N
o
d
e
Nod
e
Typ
e
In
Inte
rfac
e
In
La
bel
Rever
se In
Label
Out
Inte
rfac
e
O
ut
La
be
l
Re
ver
se
Ou
t
La
bel
Nex
t
Hop
Rev
erse
Nex
t
Hop
Sourc
e
Node
Sink
Nod
e
10 N
E
1
Ingre
ss
- - 103 4-
EM6
F-1
10
0
- 18.1.
1.2
- - 130.
0.0.4
N
E
2
Tran
sit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
10
1
103 18.1.
1.6
18.1.
1.1
130.0.
0.1
130.
0.0.4
N
E
4
Egre
ss
4-
EM6
F-1
10
1
- - 102 - 18.1.
1.5
130.0.
0.1
-
20 N
E
1
Ingre
ss
- - 203 4-
EM6
F-2
20
0
- 18.1.
2.2
- - 130.
0.0.4
N
E
3
Tran
sit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
20
1
203 18.1.
2.6
18.1.
2.1
130.0.
0.1
130.
0.0.4
N
E
4
Egre
ss
4-
EM6
F-2
20
1
- - 202 - 18.1.
2.5
130.0.
0.1
-

Transmission System
62
Table 3-6 Parameters of MPLS tunnel OAM
Parameter Parameter Planning
MPLS Tunnel ID 10 20
OAM Status Enabled Enabled
Detection Mode Manual Manual
Detection Packet
Type (ms)
FFD
NOTE
Detection Packet Period can be set only
when Detection Packet Type is FFD.
FFD
Detection Packet
Period
3.3
NOTE
Generally, the OAM packet is reported after
three periods. When Detection Packet
Period (ms) is set to 3.3, the switching time
can be less than 50 ms.
3.3

Table 3-7 Parameters of MPLS tunnel APS
Protection Type 1:1
Switching Mode Single-Ended
Working Tunnel ID 10
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
Revertive Mode Revertive
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE
The services are not protected by multiple protection schemes. Therefore, the
Hold-off Time (100ms) takes the default value 0.
Protocol State Enabled

Transmission System
63
Table 3-8 Planning information of the PWs
Parameter PW of User A PW of User B
PW ID 35 45
PW Signaling Type Static Static
PW Type Ethernet Tagged Mode Ethernet Tagged Mode
PW Direction Bidirectional Bidirectional
PW Incoming Label/Source
Port
20 30
PW Outgoing Label/Sink Port 20 30
Peer IP NE1 130.0.0.4 130.0.0.4
NE4 130.0.0.1 130.0.0.1
Tunnel No. NNE1_NE4_working NE1_NE4_working
Bandwidth Limit Enabled Enabled
CIR(kbit/s) 10240 30720
PIR(kbit/s) 30720 51200
CBS(bytes) 30720 51200
PBS(bytes) 30720 51200
Request VLAN 10 20

Table 3-9 Planning information of the E-Line services carried by the PWs from the user side to
the network side
Parameter User A User B
Service ID 1 2
Name E-Line-1 E-Line-2
Direction UNI-NNI UNI-NNI
UNI 4-EM6F-3 4-EM6F-4
VLANs 100 100
Bearer Type PW PW
PW ID 35 45
BPDU Not Transparently
Transmitted
Not Transparently
Transmitted
Transmission System
64
Parameter User A User B
MTU(bytes) - -

3.3.3 Configuration Process (in End-to-End Mode)
Before configuring E-Line services carried by PWs, configure the tunnels that carry the PWs,
MPLS tunnel OAM, and MPLS tunnel APS according to service planning.
Prerequisites
l You must be familiar with the networking requirements and service planning information
of the UNI-NNI E-Line services carried by the PWs.
l If a port needs to be occupied exclusively, you need to disable the DCN function of the
port. For details, see Configuring the DCN Function for a Port.
Procedure
Step 1 On NE1, NE2, NE3 and NE4, configure the tunnels that carry the PWs. For the configuration
procedures, see 8.8 Configuring an MPLS Tunnel.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

Transmission System
65
M
P
L
S
T
u
n
n
el
I
D
N
o
d
e
Nod
e
Typ
e
In
Inte
rfac
e
In
La
bel
Rever
se In
Label
Out
Inte
rfac
e
O
ut
La
be
l
Re
ver
se
Ou
t
La
bel
Nex
t
Hop
Rev
erse
Nex
t
Hop
Sourc
e
Node
Sink
Nod
e
10 N
E
1
Ingre
ss
- - 103 4-
EM6
F-1
10
0
- 18.1.
1.2
- - 130.
0.0.4
N
E
2
Tran
sit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
10
1
103 18.1.
1.6
18.1.
1.1
130.0.
0.1
130.
0.0.4
N
E
4
Egre
ss
4-
EM6
F-1
10
1
- - 102 - 18.1.
1.5
130.0.
0.1
-
20 N
E
1
Ingre
ss
- - 203 4-
EM6
F-2
20
0
- 18.1.
2.2
- - 130.
0.0.4
N
E
3
Tran
sit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
20
1
203 18.1.
2.6
18.1.
2.1
130.0.
0.1
130.
0.0.4
N
E
4
Egre
ss
4-
EM6
F-2
20
1
- - 202 - 18.1.
2.5
130.0.
0.1
-

Step 2 On NE1 and NE4, configure MPLS tunnel OAM. For the configuration procedures, see 8.10
Configuring MPLS Tunnel OAM.
Transmission System
66
Detection Packet
Type (ms)
FFD
NOTE
FFD
Detection Packet
Period
3.3
NOTE
3.3

Step 3 On NE1 and NE4, configure MPLS tunnel APS. For the configuration procedures, see 8.12
Configuring Tunnel APS.
Protection Type 1:1
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Step 4 Configure the common Internet access service between User A1 and User A2 in end-to-end
mode.
1. Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
2. Set the basic attributes of the common Internet access service between User A1 and User
A2.
Transmission System
67
Table 3-14 Parameters of the E-Line services between User A1 and User A2
Parameter Value in This Example
Service Type ETH
Service ID 1
Service Name E-Line-1
Protection Type Protection-Free

3. Configure the source NE and sink NE of the PWE3 service.
a. Under Node List, click Configure Source And Sink. Then, a dialog box is displayed.
b. Select the source NE from Physical Topology on the left.
c. Set the SAI attributes of the E-Line service in SAI Configuration. Then, click Add
Node.
Table 3-15 Parameters of the service ports between User A1 and User A2
Source ID 1
VLAN ID 100
Sink ID 1
VLAN ID 100

4. Click the PW tab and set the basic attributes of the PW.
Table 3-16 Parameters of the PW between User A1 and User A2
PW ID 35
Signaling Type Static
Forward Label 20
Reverse Label 20
Forward Type Static Binding
Forward Tunnel NE1_NE4_working
Reverse Type Static Binding
Reverse Tunnel NE1_NE4_working
Encapsulation Type MPLS

Transmission System
68
5. Click Detail, set the Advanced attributes of the PW.
a. Click the PW QoS tab and set the parameters of the PW QoS.
Table 3-17 Parameters of the service bandwidth between User A1 and User A2
Forward Bandwidth Limit Enabled
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720
Reverse Bandwidth Limit Enabled
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720

b. Click the Advanced PW Attribute tab and set the advanced attributes of the PW.
Table 3-18 Parameters of the advanced attributes of the PW between User A1 and User
A2
PW Type Ethernet Tagged Mode
Request VLAN 10
Other parameters Default values
NOTE
For details on how to configure the TPID, see 8.15
Configuring NE-Level TPID.

6. Optional: If alarms are automatically configured after the configuration of services, click
ETH OAM CC so that the connectivity check can be continuous.
NOTE
E-Line services carried by PWs based on neither VLAN priorities nor VLAN switching support ETH
OAM CC tests.
7. Click OK.
Step 5 Configure the data service between User A1 and User A2 in end-to-end mode.
Configure the data service between User B1 and User B2 according to Step 4.
Transmission System
69
Table 3-19 Parameters of the E-Line services between User B1 and User B2
Service Type ETH
Service ID 2

Table 3-20 Parameters of the service ports between User B1 and User B2
Source ID 2
VLAN ID 100
Sink ID 2
VLAN ID 100

Table 3-21 Parameters of the PW between User B1 and User B2
PW ID 45
Forward Label 30
Reverse Label 30

Table 3-22 Parameters of the service bandwidth between User B1 and User B2
Forward Bandwidth Limit Enabled
Transmission System
70
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200
Reverse Bandwidth Limit Enabled
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200

Table 3-23 Parameters of the advanced attributes of the PW between User B1 and User B2
Request VLAN 20
NOTE
For details on how to configure the TPID, see 8.15 Configuring NE-
Level TPID.

----End
Relevant Task
See 3.4.5 Verifying E-Line Services to check whether the E-Line services carried by PWs are
configured correctly.
3.3.4 Configuration Process (Configuration on a Per-NE Basis)
Before configuring E-Line services carried by PWs, configure the tunnels that carry the PWs,
MPLS tunnel OAM, and MPLS tunnel APS according to service planning.
Prerequisites
of the UNI-NNI E-Line services carried by the PWs.
Transmission System
71
Procedure
Step 1 On NE1, NE2, NE3 and NE4, configure the tunnels that carry the PWs. For the configuration
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

M
P
L
S
T
u
n
n
el
I
D
N
o
d
e
Nod
e
Typ
e
In
Inte
rfac
e
In
La
bel
Rever
se In
Label
Out
Inte
rfac
e
O
ut
La
be
l
Re
ver
se
Ou
t
La
bel
Nex
t
Hop
Rev
erse
Nex
t
Hop
Sourc
e
Node
Sink
Nod
e
10 N
E
1
Ingre
ss
- - 103 4-
EM6
F-1
10
0
- 18.1.
1.2
- - 130.
0.0.4
N
E
2
Tran
sit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
10
1
103 18.1.
1.6
18.1.
1.1
130.0.
0.1
130.
0.0.4
N
E
4
Egre
ss
4-
EM6
F-1
10
1
- - 102 - 18.1.
1.5
130.0.
0.1
-
20 N
E
1
Ingre
ss
- - 203 4-
EM6
F-2
20
0
- 18.1.
2.2
- - 130.
0.0.4
Transmission System
72
M
P
L
S
T
u
n
n
el
I
D
N
o
d
e
Nod
e
Typ
e
In
Inte
rfac
e
In
La
bel
Rever
se In
Label
Out
Inte
rfac
e
O
ut
La
be
l
Re
ver
se
Ou
t
La
bel
Nex
t
Hop
Rev
erse
Nex
t
Hop
Sourc
e
Node
Sink
Nod
e
N
E
3
Tran
sit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
20
1
203 18.1.
2.6
18.1.
2.1
130.0.
0.1
130.
0.0.4
N
E
4
Egre
ss
4-
EM6
F-2
20
1
- - 202 - 18.1.
2.5
130.0.
0.1
-

Detection Packet
Type (ms)
FFD
NOTE
FFD
Detection Packet
Period
3.3
NOTE
3.3

Transmission System
73
Protection Type 1:1
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Step 4 On NE1, configure the E-Line services of User A1.
1. In the NE Explorer, select NE1, and then choose Configuration > Packet
Configuration > Ethernet Service Management > E-Line Service from the Function
Tree.
2. Click New. Then, the New E-Line Service dialog box is displayed. Set the parameters of
the E-Line services of User A1.
Table 3-28 Parameters of the E-Line services carried by PWs of User A1
Service ID 1
Direction UNI-NNI
BPDU Not Transparently Transmitted
MTU (bytes) -
Service Tag Role -
Source Port 4-EM6F-3 (PORT-3)
Source VLANs 100
Transmission System
74
PRI -
Bearer Type PW
Protection Type Unprotected

3. Click Configure PW. Then, the Configure PW dialog box is displayed. Set the PW
parameters.
Table 3-29 PW parameters of the E-Line services of User A1
Basic Attributes PW ID 35
PW Signaling Type Static
PW Direction Bidirectional
PW Incoming Label/
Source Port
20
PW Outgoing Label/Sink
Port
20
Tunnel Type MPLS
Tunnel No. NE1_NE4_working
Peer LSR ID 130.0.0.4
QoS Bandwidth Limit Enabled
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720
Advanced Attributes Request VLAN 10
NOTE
For details on how to configure the TPID, see 8.15 Configuring
NE-Level TPID.

Step 5 On NE1, configure the E-Line services of User B1.
Transmission System
75
Refer to Step 4 and configure the E-Line services of User B1.
Table 3-30 Parameters of the E-Line services carried by PWs of User B1
Service ID 2
Direction UNI-NNI
MTU (bytes) -
Service Tag Role -
Source Port 4-EM6F-4 (PORT-4)
Source VLANs 100
PRI -
Bearer Type PW

Table 3-31 PW parameters of the E-Line services of User B1
Port
30
Port
30
Tunnel Type MPLS
CIR(kbit/s) 30720
PIR(kbit/s) 51200
Transmission System
76
CBS(bytes) 51200
PBS(bytes) 51200
NOTE
Level TPID.

Step 6 On NE3, configure the E-Line services of User A2 and User B2.
Refer to Step 4 and configure the E-Line services of User A2 and User B2.
Table 3-32 Parameters of the E-Line services carried by PWs of User A2
Service ID 1
Direction UNI-NNI
MTU (bytes) -
Service Tag Role -
Sink Port 4-EM6F-3 (PORT-3)
Sink VLANs 100
PRI -
Bearer Type PW

Table 3-33 PW parameters of the E-Line services of User A2
Transmission System
77
Port
20
Port
20
Tunnel Type MPLS
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720
NOTE
Level TPID.

Table 3-34 Parameters of the E-Line services carried by PWs of User B2
Service ID 2
Direction UNI-NNI
MTU (bytes) -
Service Tag Role -
Sink Port 4-EM6F-4 (PORT-4)
Sink VLANs 100
PRI -
Transmission System
78
Bearer Type PW

Table 3-35 PW parameters of the E-Line services of User B2
Port
30
Port
30
Tunnel Type MPLS
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200
NOTE
Level TPID.

----End
Relevant Task
See 3.3.5 Verifying the Correctness of E-Line Service Configuration to check whether the
E-Line services carried by PWs are configured correctly.
Transmission System
79
3.3.5 Verifying the Correctness of E-Line Service Configuration
The LB function provided by ETH OAM is used to test whether Ethernet services are available.
Prerequisites
l Ethernet services have been configured. For details on how to configure Ethernet services,
see 3 Configuring ETH PWE3 Services in the Configuration Guide (Packet Transport
Domain).
Application Scenario
The LB function in ETH OAM can be used to test the following services (PW-carried E-Line
services, for example):
l Native ETH-carried E-Line and E-LAN services
l PW-carried E-Line (based on VLAN) and E-LAN services
Precautions
For details on the feature dependencies and limitationshow to configure ETH OAM services,
Please see Feature Dependencies and Limitations in the Feature Description.
U2000
For details about the boards that support the ETH OAM function, see Availability of the ETH
OAM function in the Feature Description.
Huawei's Ethernet service processing boards can achieve ETH OAM in compliance with IEEE
802.1ag and IEEE 802.3ah. IEEE 802.1ag define the OAM standards for Ethernet services; IEEE
802.3ah defines the OAM standards for Ethernet ports. As shown in Figure 3-11, the two
recommendations are applied to provide a complete ETH OAM solution.
Transmission System
80
Figure 3-11 Application of IEEE 802.1ag and IEEE 802.3ah
Core layer
PE1
CE4
PE2
CE3
P
P
P
P
CE1
Router 3
Access layer
Access layer
Custom layer Custom layer
Router 1
Router 2
IEEE 802.1ag
IEEE
802.3ah
IEEE
802.3ah
CE2
OptiX NE

NOTE
The OptiX OSN is usually applied to the access layer of networks.
l Ethernet service OAM achieves end-to-end maintenance for Ethernet links. It functions
based on "maintenance domains" which segment the trail that an Ethernet service travels
along.
l Ethernet port OAM achieves point-to-point maintenance for Ethernet links. It functions
based on the two directly-connected devices of Ethernet in the First Mile (EFM). Ethernet
port OAM can be performed by means of auto-discovery, link performance monitoring,
fault detection, remote loopback, and self-loop detection.
Procedure
Step 1 Optional: Convert the Ethernet services that are created in per-NE mode to end-to-end PWE3
services.
1. Choose Service > Search for IP Service from the main menu.
2. In the dialog box that is displayed, set the auto-discovery policies.
3. Click Start.
4. After the auto-discovery is finished, click Close.
Step 2 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
Step 3 In the dialog box that is displayed, set the filter conditions. For example, set Protocol Type to
PW APS. Then click Filter.
Step 4 After all the PWE3 services that meet the filter conditions are displayed, select the desired
service, right-click, and choose Ethernet OAM > LB Test from the shortcut menu.
Step 5 In the dialog box that is displayed, select the source NE and sink NE. Then click Run.
Transmission System
81
Step 6 After the test is finished, click the LB Statistic Information tab and check the test results.
NOTE
The service under test has normal connectivity if the number of transmitted packets equals the number of
received packets.
----End
(Based on VLAN Priorities)
In this example, services with a same VLAN ID but different VLAN priorities need to be mapped
to different PWs.
on VLAN priorities).
On the network shown in Figure 3-12, services from NodeB 1 and services from NodeB 2 have
a same VLAN ID, and need to be mapped to different PWs based on Port+VLAN+VLAN
PRI before being transported to the RNC. Service requirements are as follows:
l Services from NodeB 1 and services from NodeB 2 are transported to NE1 through the 4-
EM6F-3 and 4-EM6F-4 ports respectively.
l NE4 converges services from NodeB 1 and NodeB 2, and transports the services to the
RNC.
l Services from NodeB 1 are common Internet access services of which the CIR is 10 Mbit/
l Services from NodeB 2 are data services of which the CIR is 30 Mbit/s and the PIR is 50
Mbit/s.
l Services from NodeB 1 have a VLAN ID of 100 and VLAN priorities of 3, 4, and 5; services
from NodeB 2 have a VLAN ID of 100 and a VLAN priority of 2. Services from NodeB
1 and NodeB 2 are mapped to two PWs based on Port+VLAN+VLAN PRI.
l Services from NodeB 1 and NodeB 2 are protected by tunnel APS.
Transmission System
82
Figure 3-12 Networking diagram of the E-Line services carried by PWs (based on VLAN
priorities)
NOTE
NE1 4-
EM6F-1
18.1.1.1 255.255.255.252 130.0.0.1
4-
EM6F-2
18.1.2.1 255.255.255.252
NE2 4-
EM6F-1
18.1.1.2 255.255.255.252 130.0.0.2
4-
EM6F-2
18.1.1.5 255.255.255.252
NE3 4-
EM6F-1
18.1.2.2 255.255.255.252 130.0.0.3
4-
EM6F-2
18.1.2.5 255.255.255.252
NE4 4-
EM6F-1
18.1.1.6 255.255.255.252 130.0.0.4
Transmission System
83
4-
EM6F-2
18.1.2.6 255.255.255.252

NOTE
l The IP addresses of the Ethernet ports on an NE must not be in the same network segment.
l The IP addresses of the ports at both ends of a tunnel must be in the same network segment.

The engineering information for configuring the E-Line services carried by PWs (based on
VLAN priorities) contains the engineering information for configuring the tunnels carrying the
PWs, the engineering information for configuring the PWs, and the engineering information for
configuring the UNI-NNI E-Line services carried by the PWs.
The PWs that carry the E-Line services are carried by tunnels. Therefore, you need to plan the
tunnels during the service planning. Planning the E-Line services carried by PWs involves the
following:
l Plan the tunnels that carry the PWs. Refer to Table 3-36 and Table 3-37.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

Transmission System
84
Table 3-37 Parameter planning for the MPLS tunnels
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Table 3-38 Parameter planning for MPLS tunnel OAM
Detection Packet
Type
FFD
NOTE
FFD
Transmission System
85
Detection Packet
Period (ms)
3.3
NOTE
Generally, an OAM alarm is reported after
can meet the requirement (less than 50 ms)
after a fault occurs.
3.3

Table 3-39 Parameter planning for MPLS tunnel APS
Protection Type 1:1
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE
setting of Hold-off Time (100 ms) is unnecessary.

Table 3-40 Parameter planning for the PWs
Parameter NodeB 1 PW NodeB 2 PW
PW ID 35 45
Port
20 30
Transmission System
86
Port
20 30
Peer LSR ID NE1 130.0.0.4 130.0.0.4
NE4 130.0.0.1 130.0.0.1
MPLS Tunnel name NE1_NE4_working NE1_NE4_working
CIR(kbit/s) 10240 30720
PIR(kbit/s) 30720 51200
CBS(bytes) 30720 51200
PBS(bytes) 30720 51200
Request VLAN 10 20
TPID 0x88A8 0x88A8

Table 3-41 Parameter planning for the UNI-NNI E-Line services carried by PWs
Parameter NodeB 1 NodeB 2 RNC
Service ID 1 2 1 2
Name E-Line-1 E-Line-2 E-Line-1 E-Line-2
Direction UNI-NNI UNI-NNI UNI-NNI UNI-NNI
Service Tag
Role
User User User User
UNI 4-EM6F-3 4-EM6F-4 4-EM6F-3 4-EM6F-3
VLANs 100 100 100 100
PRI 3, 4, 5 2 3, 4, 5 2
Bearer Type PW PW PW PW
PW ID 35 45 35 45
BPDU Not
Transparently
Transmitted
Not
Transparently
Transmitted
Not
Transparently
Transmitted
Not
Transparently
Transmitted
MTU (bytes) - - - -

Transmission System
87
This section describes how to configure E-Line services carried by PWs in end-to-end mode.
Prerequisites
l You must be familiar with the networking requirements and service plan of the E-Line
services carried by PWs (in the scenario of based on VLAN priorities).
Procedure
Step 1 See 8.8 Configuring an MPLS Tunnel to configure a tunnel for carrying PWs.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
Transmission System
88
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Step 2 See 8.10 Configuring MPLS Tunnel OAM to configure MPLS tunnel OAM.
Detection Packet
Type
FFD
NOTE
FFD
Detection Packet
Period (ms)
3.3
NOTE
3.3

Step 3 See 8.12 Configuring Tunnel APS to configure MPLS tunnel APS.
Protection Type 1:1
Transmission System
89
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Step 4 Configure common Internet access services on NodeB 1 in end-to-end mode.
1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
2. Set general attributes for the common Internet access services on NodeB 1.
Table 3-46 General attributes for the common Internet access services on NodeB 1
Service Type ETH
Service ID 1

3. Configure the source and sink NEs of the PWE3 service.
a. On the Node List tag page, click Configure Source And Sink. A dialog box is
displayed.
b. Select source and sink NEs in Physical Topology on the left.
c. In SAI Configuration, set the parameters for the service port on NodeB 1 and click
Add Node.
Transmission System
90
Table 3-47 Parameters for the service port on NodeB 1
Source ID 1
VLAN ID 100
Priority Type 802.1P
Priority Field 3,4,5
Sink ID 1
VLAN ID 100
Priority Field 3,4,5

4. Click the PW tab, and set the general attributes for the PW on NodeB 1.
Table 3-48 General attributes for the PW on NodeB 1
PW ID 35
Forward Label 20
Reverse Label 20

5. Click Detail and set the advanced attributes for the PW on NodeB 1.
a. Click the PW QoS tab and set the QoS parameters for the PW on NodeB 1.
Table 3-49 QoS parameters for the PW on NodeB 1
Forward Bandwidth Limited Enabled
CIR(kbit/s) 10240
PIR(kbit/s) 30720
Transmission System
91
CBS(bytes) 30720
PBS(bytes) 30720
ReverseBandwidth
Limited
Bandwidth Limited Enabled
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720

b. Click the Advanced PW Attribute tab and set the advanced attributes for the PW on
NodeB 1.
Table 3-50 Advanced attributes for the PW on NodeB 1
Request VLAN 10
TPID 0x88A8
NOTE

c. Click the Service Parameter tab and set the service tags for NodeB 1.
Table 3-51 Service tags for NodeB 1
Source Service Tag User
Sink Service Tag User

NOTE
OAM CC tests.
7. Click OK.
Step 5 Configure data services on NodeB 2 in end-to-end mode.
Transmission System
92
See Step 4 to configure data services on NodeB 2.
Table 3-52 General attributes for the data services on NodeB 2
Service Type ETH
Service ID 2

Source ID 2
VLAN ID 100
Priority Field 2
Sink ID 2
VLAN ID 100
Priority Field 2

PW ID 45
Forward Label 30
Reverse Label 30
Transmission System
93

CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200
Reverse Bandwidth Limited Enabled
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200

Request VLAN 20
TPID 0x88A8
NOTE
Level TPID.

Transmission System
94

----End
Related Task
This topic describes the process for configuring the E-Line services carried by PWs.
Prerequisites
of the E-Line services carried by PWs (based on VLAN priorities).
Procedure
Step 1 On NE1, NE2, NE3, and NE4, configure the tunnels that carry the PWs. For the configuration
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
Transmission System
95
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Detection Packet
Type
FFD
NOTE
FFD
Detection Packet
Period (ms)
3.3
NOTE
3.3

Transmission System
96
Protection Type 1:1
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Step 4 On NE1, configure an E-Line service for NodeB 1.
Tree.
2. Click New. Then, the New E-Line Service dialog box is displayed. Set the displayed
parameters.
Table 3-62 Parameters of the E-Line service carried by PWs of NodeB 1
Service ID 1
Direction UNI-NNI
BPDU (STP Packet) Not Transparently Transmitted
MTU (bytes) -
Service Tag Role User
Transmission System
97
Source Port 4-EM6F-3
Source VLANs 100
PRI 3, 4, 5
Bearer Type PW

parameters.
Table 3-63 PW parameters of the E-Line service of NodeB 1
General
Attributes
PW ID 35
PW Incoming Label/Source Port 20
PW Outgoing Label/Sink Port 20
Tunnel Type MPLS
Tunnel NE1_NE4_working
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720
Advance
d
Attributes
Request VLAN 10
TPID 0x88A8
NOTE
For details on how to configure the
TPID, see 8.15 Configuring NE-Level
TPID.
Transmission System
98
Other parameters Default Values

Refer to Step 4 and configure an E-Line service for NodeB 2.
Service ID 2
Direction UNI-NNI
MTU (bytes) -
Source VLANs 100
PRI 2
Bearer Type PW

General Attributes PW ID 45
Tunnel Type MPLS
Transmission System
99
Advanced
Attributes
Request VLAN 20
TPID 0x88A8
NOTE
TPID, see 8.15 Configuring NE-
Level TPID.

Table 3-66 QoS parameters of the E-Line service of NodeB 2
PW ID 45
Direction Ingress
Bandwidth Limit Enabled
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200

Step 6 On NE4, configure an E-Line service between NodeB 1 and the RNC, and an E-Line service
between NodeB 2 and the RNC.
Refer to Step 4 and configure the E-Line services.
Table 3-67 Parameters of the E-Line service carried by PWs between NodeB 1 and the RNC
Service ID 1
Direction UNI-NNI
MTU (bytes) -
Transmission System
100
Source VLANs 100
PRI 3, 4, 5
Bearer Type PW

Table 3-68 PW parameters of the E-Line service between NodeB 1 and the RNC
PW Incoming Label/
Source Port
20
PW Outgoing Label/
Sink Port
20
Tunnel Type MPLS
Advanced
Attributes
Request VLAN 10
TPID 0x88A8
NOTE
For details on how to configure the TPID, see
8.15 Configuring NE-Level TPID.

Table 3-69 QoS parameters of the E-Line service between NodeB 1 and the RNC
PW ID 35
Direction Ingress
Transmission System
101
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720

Service ID 2
Direction UNI-NNI
MTU (bytes) -
Source VLANs 100
PRI 2
Bearer Type PW

Port
30
Transmission System
102
Port
30
Tunnel Type MPLS
TPID 0x88A8
NOTE
TPID.

PW ID 45
Direction Ingress
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200

----End
Relevant Task
3.4.5 Verifying E-Line Services
After configuring E-Line services, verify the E-Line services by using the SmartBits.
Transmission System
103
Prerequisites
l E-Line services carried by PWs are configured.
SmartBits and U2000
Test Connection Diagram
Figure 3-13 shows the connections for testing E-Line services carried by PWs.
Figure 3-13 Connections for testing E-Line services carried by PWs
4-EM6F-3
MPLS tunnel
PW
PSN
4-EM6F-3
NE1 NE3 NE2
SmartBits SmartBits
NOTE
In this example, the SmartBits devices are connected to 4-EM6F-3 on NE1 (source) and 4-EM6F-3 on NE3
(sink). In actual situations, determine the source and sink as required, and follow the same testing procedure.

Context
NOTICE
l During a test, only test personnel are allowed in the testing environment.
l Exercise caution when touching cables and optical fibers.
Procedure
Step 1 Connect the SmartBits devices to 4-EM6F-3 on NE1 and 4-EM6F-3 on NE3.
Step 2 Log in to the U2000. See 2.9 Enabling, Disabling, and Setting Performance Monitoring of
the NE to start the 15-minute and 24-hour performance monitoring on NE1 and NE3.
NOTE
The performance monitoring tasks help analyze and locate a problem during the test.
Step 3 Use the SmartBits devices to perform a packet transmitting and receiving test.
Transmission System
104
NOTE
l Packets whose bytes are all 0s are considered as special packets. Do not use those packets for a packet
transmitting and receiving test.
l In the first packet transmitting and receiving period, learning the MAC addresses of the packets may
cause packet loss.
l If the service is normal, the number of received packets is equal to the number of transmitted packets.
If it is a VLAN-based service that involves VLAN switching, check whether VLAN switching functions
properly for transmitted and received packets.
l If packet loss occurred, rectify the fault. Then, perform 24-hour tests until no packet loss occurs.
----End
(Based on VLAN Switching)
configure the E-Line services carried by PWs (based on VLAN switching) for each NE according
to the networking diagram.
on VLAN switching).
On the network shown in Figure 3-14, services from NodeB 1 and services from NodeB 2 have
a same VLAN ID, and need VLAN switching before being transported to the RNC. Service
requirements are as follows:
l Services from NodeB 1 and services from NodeB 2 are transported to NE1 through the 4-
EM6F-3 and 4-EM6F-4 ports respectively.
l NE4 converges services from NodeB 1 and NodeB 2, and transports the services to the
RNC.
l Services from NodeB 1 are common Internet access services of which the CIR is 10 Mbit/
l Services from NodeB 2 are data services of which the CIR is 30 Mbit/s and the PIR is 50
Mbit/s.
l Services from NodeB 1 and services from NodeB 2 have a same VLAN ID of 100, and are
mapped to two PWs. After VLAN switching, the VLAN ID of services from NodeB 1
remains unchanged, whereas the VLAN ID of services from NodeB 2 is changed to 200.
l Services from NodeB 1 and NodeB 2 are protected by tunnel APS.
Transmission System
105
Figure 3-14 Networking diagram of the E-Line services carried by PWs (based on VLAN
switching)
NOTE
NE1 4-
EM6F-1
18.1.1.1 255.255.255.252 130.0.0.1
4-
EM6F-2
18.1.2.1 255.255.255.252
NE2 4-
EM6F-1
18.1.1.2 255.255.255.252 130.0.0.2
4-
EM6F-2
18.1.1.5 255.255.255.252
NE3 4-
EM6F-1
18.1.2.2 255.255.255.252 130.0.0.3
4-
EM6F-2
18.1.2.5 255.255.255.252
NE4 4-
EM6F-1
18.1.1.6 255.255.255.252 130.0.0.4
Transmission System
106
4-
EM6F-2
18.1.2.6 255.255.255.252

NOTE
l The IP addresses of the Ethernet ports on an NE must not be in the same network segment.
l The IP addresses of the ports at both ends of a tunnel must be in the same network segment.

The engineering information for configuring the E-Line services carried by PWs (based on
VLAN switching) contains the engineering information for configuring the tunnels carrying the
PWs, the engineering information for configuring the PWs, and the engineering information for
configuring the UNI-NNI E-Line services carried by the PWs.
The PWs that carry the E-Line services are carried by tunnels. Therefore, you need to plan the
tunnels during the service planning. Planning the E-Line services carried by PWs involves the
following:
l Plan the tunnels that carry the PWs. Refer to Table 3-73 and Table 3-74.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

Transmission System
107
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Detection Packet
Type
FFD
NOTE
FFD
Transmission System
108
Detection Packet
Period (ms)
3.3
NOTE
3.3

Protection Type 1:1
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Table 3-77 Parameter planning for the PWs
PW ID 35 45
Port
20 30
Transmission System
109
Port
20 30
Peer LSR ID NE1 130.0.0.4 130.0.0.4
NE4 130.0.0.1 130.0.0.1
MPLS Tunnel name NE1_NE4_working NE1_NE4_working
CIR(kbit/s) 10240 30720
PIR(kbit/s) 30720 51200
CBS(bytes) 30720 51200
PBS(bytes) 30720 51200
Request VLAN 10 20
TPID 0x8100 0x8100

Table 3-78 Parameter planning for the UNI-NNI E-Line services carried by PWs
Paramete
r
NodeB 1 NodeB 2 RNC
Service ID 1 2 1 2
Name E-Line-1 E-Line-2 E-Line-1 E-Line-2
Direction UNI-NNI UNI-NNI UNI-NNI UNI-NNI
Service
Tag Role
User Service User Service
UNI 4-EM6F-3 4-EM6F-4 4-EM6F-3 4-EM6F-3
VLANs 100 100 100 200
Bearer
Type
PW PW PW PW
PW ID 35 45 35 45
BPDU Not
Transparently
Transmitted
Not
Transparently
Transmitted
Not
Transparently
Transmitted
Not
Transparently
Transmitted
MTU
(bytes)
- - - -

Transmission System
110
This section describes how to configure E-Line services carried by PWs in end-to-end mode.
Prerequisites
l You must be familiar with the networking requirements and service plan of the E-Line
services carried by PWs (in the scenario of based on VLAN switching).
Procedure
Step 1 See 8.8 Configuring an MPLS Tunnel to configure a tunnel for carrying PWs.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
Transmission System
111
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Step 2 See 8.10 Configuring MPLS Tunnel OAM to configure MPLS tunnel OAM.
Detection Packet
Type
FFD
NOTE
FFD
Detection Packet
Period (ms)
3.3
NOTE
3.3

Step 3 See 8.12 Configuring Tunnel APS to configure MPLS tunnel APS.
Protection Type 1:1
Transmission System
112
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Step 4 Configure common Internet access services on NodeB 1 in end-to-end mode.
2. Set general attributes for the common Internet access services on NodeB 1.
Table 3-83 General attributes for the common Internet access services on NodeB 1
Service Type ETH
Service ID 1

3. Configure the source and sink NEs of the PWE3 service.
a. On the Node List tag page, click Configure Source And Sink. A dialog box is
displayed.
b. Select source and sink NEs in Physical Topology on the left.
c. In SAI Configuration, set the parameters for the service port on NodeB 1 and click
Add Node.
Transmission System
113
Source ID 1
VLAN ID 100
Sink ID 1
VLAN ID 100

4. Click the PW tab, and set the general attributes for the PW on NodeB 1.
PW ID 35
Forward Label 20
Reverse Label 20

5. Click Detail and set the advanced attributes for the PW on NodeB 1.
a. Click the PW QoS tab and set the QoS parameters for the PW on NodeB1.
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720
CIR(kbit/s) 10240
Transmission System
114
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720

b. Click the Advanced PW Attribute tab and set the advanced attributes for the PW on
NodeB 1.
Request VLAN 10
TPID 0x8100
NOTE

c. Click the Service Parameter tab and set the service tags for NodeB 1.

NOTE
OAM CC tests.
7. Click OK.
Step 5 Configure data services on NodeB 2 in end-to-end mode.
See Step 4 to configure data services on NodeB 2.
Table 3-89 General attributes for the data services on NodeB 2
Service Type ETH
Transmission System
115
Service ID 2

Source ID 2
VLAN ID 100
Sink ID 2
VLAN ID 200

PW ID 45
Forward Label 30
Reverse Label 30

CIR(kbit/s) 30720
PIR(kbit/s) 51200
Transmission System
116
CBS(bytes) 51200
PBS(bytes) 51200
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200

Request VLAN 20
TPID 0x8100
NOTE
Level TPID.

Source Service Tag Service
Sink Service Tag Service

----End
Related Task
This topic describes the process for configuring the E-Line services carried by PWs.
Transmission System
117
Prerequisites
of the E-Line services carried by PWs (based on VLAN switching).
Procedure
Step 1 On NE1, NE2, NE3, and NE4, configure the tunnels that carry the PWs. For the configuration
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
Transmission System
118
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Detection Packet
Type
FFD
NOTE
FFD
Detection Packet
Period (ms)
3.3
NOTE
3.3

Protection Type 1:1
Transmission System
119
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Tree.
2. Click New. Then, the New E-Line Service dialog box is displayed. Set the displayed
parameters.
Service ID 1
Direction UNI-NNI
MTU (bytes) -
Source VLANs 100
Bearer Type PW
Transmission System
120

parameters.
General
Attributes
PW ID 35
Tunnel Type MPLS
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720
Advance
d
Attributes
Request VLAN 10
TPID 0x8100
NOTE
TPID.

Refer to Step 4 and configure an E-Line service for NodeB 2.
Service ID 2
Transmission System
121
Direction UNI-NNI
MTU (bytes) -
Service Tag Role Service
Source VLANs 100
Bearer Type PW

Tunnel Type MPLS
Advanced
Attributes
Request VLAN 20
TPID 0x8100
NOTE
TPID, see 8.15 Configuring NE-
Level TPID.

Transmission System
122
Table 3-103 QoS parameters of the E-Line service of NodeB 2
PW ID 45
Direction Ingress
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200

Step 6 On NE4, configure an E-Line service between NodeB 1 and the RNC, and an E-Line service
between NodeB 2 and the RNC.
Refer to Step 4 and configure the E-Line services.
Service ID 1
Direction UNI-NNI
MTU (bytes) -
Source VLANs 100
Bearer Type PW

Transmission System
123
PW Incoming Label/
Source Port
20
PW Outgoing Label/
Sink Port
20
Tunnel Type MPLS
Advanced
Attributes
Request VLAN 10
TPID 0x8100
NOTE
For details on how to configure the TPID, see
8.15 Configuring NE-Level TPID.

PW ID 35
Direction Ingress
CIR(kbit/s) 10240
PIR(kbit/s) 30720
CBS(bytes) 30720
PBS(bytes) 30720

Transmission System
124
Service ID 2
Direction UNI-NNI
Service Tag Role Service
MTU (bytes) -
Source VLANs 200
Bearer Type PW

Port
30
Port
30
Tunnel Type MPLS
TPID 0x8100
NOTE
TPID.
Transmission System
125

PW ID 45
Direction Ingress
CIR(kbit/s) 30720
PIR(kbit/s) 51200
CBS(bytes) 51200
PBS(bytes) 51200

----End
Relevant Task
3.5.5 Verifying the Correctness of E-Line Service Configuration
After configuring E-Line services, verify the E-Line services by using the SmartBits.
Prerequisites
l E-Line services carried by PWs are configured.
SmartBits and U2000
Figure 3-15 shows the connections for testing E-Line services carried by PWs.
Transmission System
126
Figure 3-15 Connections for testing E-Line services carried by PWs
4-EM6F-3
MPLS tunnel
PW
PSN
4-EM6F-3
NE1 NE3 NE2
SmartBits SmartBits
NOTE
In this example, the SmartBits devices are connected to 4-EM6F-3 on NE1 (source) and 4-EM6F-3 on NE3
(sink). In actual situations, determine the source and sink as required, and follow the same testing procedure.

Context
NOTICE
l During a test, only test personnel are allowed in the testing environment.
l Exercise caution when touching cables and optical fibers.
Procedure
Step 1 Connect the SmartBits devices to 4-EM6F-3 on NE1 and 4-EM6F-3 on NE3.
Step 2 Log in to the U2000. See 2.9 Enabling, Disabling, and Setting Performance Monitoring of
the NE to start the 15-minute and 24-hour performance monitoring on NE1 and NE3.
NOTE
The performance monitoring tasks help analyze and locate a problem during the test.
Step 3 Use the SmartBits devices to perform a packet transmitting and receiving test.
NOTE
l Packets whose bytes are all 0s are considered as special packets. Do not use those packets for a packet
transmitting and receiving test.
l In the first packet transmitting and receiving period, learning the MAC addresses of the packets may
cause packet loss.
l If the service is normal, the number of received packets is equal to the number of transmitted packets.
If it is a VLAN-based service that involves VLAN switching, check whether VLAN switching functions
properly for transmitted and received packets.
l If packet loss occurred, rectify the fault. Then, perform 24-hour tests until no packet loss occurs.
----End
Transmission System
127
3.6 Configuration Example (E-LAN Services Carried by
PWs)
This section uses an example to describe how to plan the engineering information and how to
configure E-LAN services carried by PWs on each NE according to the networking diagram.
This section describes the networking of NEs.
The network shown in Figure 3-16 uses an E2E virtual private LAN service (VPLS) solution,
which implements VPLS at both access nodes and the convergence node. This reduces
configuration workload required for NodeB expansion or reparenting. The service requirements
are as follows:
l NE1 receives NodeB1's common Internet access services through 4-EM6F-3 and NodeB2's
data services through 4-EM6F-4, and NE2 receives NodeB3's common Internet access
services through 4-EM6F-3 and NodeB4's data services through 4-EM6F-4.
l NE4 converges and transmits services from NodeBs to the radio network controller (RNC).
l Services from NodeB1 and NodeB3 have the same VLAN ID (100), the same CIR (10
Mbit/s) and the same PIR (30 Mbit/s). CIR is short for committed information rate, and
PIR for peak information rate.
l Services from NodeB2 and NodeB4 have the same VLAN ID (200), the same CIR (30
Mbit/s) and the same PIR (50 Mbit/s).
l Services from NodeBs 1 to 4 are protected by tunnel automatic protection switching (APS).
For services from NodeB1 and NodeB2, the working path is NE1 -> NE2 -> NE4, and
the protection path is NE1 -> NE3 -> NE4.
For services from NodeB3 and NodeB4, the working path is NE2 -> NE4, and the
protection path is NE2 -> NE1 -> NE3 -> NE4.
Transmission System
128
Figure 3-16 Networking diagram for E-LAN services carried by PWs
NOTE
NE IP Address Mask LSR ID
NE1 4-
EM6F-1
18.1.1.1 255.255.255.252 130.0.0.1
4-
EM6F-2
18.1.2.1 255.255.255.252
NE2 4-
EM6F-1
18.1.1.2 255.255.255.252 130.0.0.2
4-
EM6F-2
18.1.1.5 255.255.255.252
NE3 4-
EM6F-1
18.1.2.2 255.255.255.252 130.0.0.3
4-
EM6F-2
18.1.2.5 255.255.255.252
NE4 4-
EM6F-1
18.1.1.6 255.255.255.252 130.0.0.4
Transmission System
129
NE IP Address Mask LSR ID
4-
EM6F-2
18.1.2.6 255.255.255.252

NOTE
l IP addresses of Ethernet ports on an NE must be on different network segments.
l IP addresses of ports at the two ends of a tunnel must be on the same network segment.

The engineering information for configuring E-LAN services carried by pseudo wires (PWs)
includes information for configuring tunnels carrying PWs, UNIs, PWs, and E-LAN services
carried by the PWs.
On the network, E-LAN services are carried by PWs. Therefore, you need to plan parameters
related to the PWs and MPLS tunnels.
To configure E-LAN services carried by PWs, plan the following data:
l Tunnels for carrying PWs (See Table 3-110 and Table 3-111.)
l MPLS tunnel OAM (See Table 3-112.)
l MPLS tunnel APS (See Table 3-113.)
l E-LAN services carried by PWs (See Table 3-114.)
l UNIs for all NEs (See Table 3-115.)
l PWs on NNIs of all NEs (See Table 3-116.)
l QoS policies for all NEs (See Table 3-117.)
NOTE
You can configure a split horizon group for each E-LAN service.
A split horizon group contains NNIs on all NEs involved in an E-LAN service. It prevents data from being
forwarded between NNIs on all NEs involved in the E-LAN service, therefore preventing broadcast storms.
You can configure unknown frames to be broadcast.
Table 3-110 Basic attributes of MPLS tunnels
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Pla
n
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected
Transmission System
130
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
NE2_NE4_w
orking
tional
Unprot
ected
NE2_NE4_pr
otection
tional
Unprot
ected

Table 3-111 MPLS tunnel parameters
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.
0.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.
0.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.
0.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.
0.0.1
-
30 N
E
2
Ingr
ess
- - 301 4-
EM6
F-2
300 - 18.1.
1.6
- - 130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
30
0
- - - 301 - 18.1.
1.5
130.
0.0.1
-
Transmission System
131
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
40 N
E
2
Ingr
ess
- - 405 4-
EM6
F-1
400 - 18.1.
1.1
- - 130.0
.0.4
N
E
1
Tra
nsit
4-
EM6
F-1
40
0
404 4-
EM6
F-2
401 405 18.1.
2.2
18.1.
1.2
- 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
40
1
403 4-
EM6
F-2
402 404 18.1.
2.6
18.1.
2.1
- 130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
40
2
- - - 403 - 18.1.
2.5
130.
0.0.2
-

Table 3-112 MPLS tunnel OAM parameters
Paramet
er
Plan
MPLS
Tunnel
ID
10 20 30 40
OAM
Status
Enabled Enabled Enabled Enabled
Detectio
n Mode
Manual Manual Manual Manual
Detectio
n Packet
Type
FFD
NOTE
Detection Packet
Period is valid only
when Detection Packet
Type is FFD.
FFD FFD FFD
Transmission System
132
Paramet
er
Plan
Detectio
n Packet
Period
(ms)
3.3
NOTE
Generally, an OAM
alarm is reported if the
alarm persists for three
periods. If Detection
Packet Period (ms) is
set to 3.3, the switching
time can meet the
requirement (less than 50
ms).
3.3 3.3 3.3

Table 3-113 MPLS tunnel APS parameters
Parameter Plan
Protection
Type
1:1 1:1
Switching
Mode
Single-Ended Single-Ended
Wo
rkin
g
Tun
nel
ID
10 30
Tun
nel
Nam
e
NE1_NE4_working NE2_NE4_working
Pro
tect
ion
Tun
nel
ID
20 40
Tun
nel
Nam
e
NE1_NE4_protection NE2_NE4_protection
Revertive
Mode
Revertive Revertive
WTR Time
(min)
5 5
Transmission System
133
Parameter Plan
Hold-off
Time (100
ms)
0
NOTE
Services are protected by a single
protection scheme. Therefore, retain the
default value 0 for Hold-off Time (100
ms).
0
Protocol
State
Enabled Enabled

Table 3-114 Parameters for configuring E-LAN services carried by PWs
Parameter NE1 NE2 NE4
Service ID 1 2 3
Service Name E-LAN-1 E-LAN-2 E-LAN-3
Tag Type C-Aware C-Aware C-Aware
Self-Learning MAC
Address
Enabled Enabled Enabled
MAC Address
Learning Mode
SVL SVL SVL

Table 3-115 UNI parameters
Interface 4-EM6F-3 4-EM6F-4 4-EM6F-3 4-EM6F-4 4-EM6F-3
VLAN ID 100 200 100 200 100, 200

Table 3-116 PW parameters
PW ID 10 20 10 20
PW Signaling
Type
Static Static Static Static
PW Type Ethernet Ethernet Ethernet Ethernet
PW Direction Bidirectional Bidirectional Bidirectional Bidirectional
Transmission System
134
PW Incoming
Label
20 30 20 30
PW Outgoing
Label
20 30 20 30
Ingress Tunnel NE1_NE4_wor
king
NE2_NE4_wor
king
NE1_NE4_wor
king
NE2_NE4_wor
king
Peer LSR ID 130.0.0.4 130.0.0.4 130.0.0.1 130.0.0.2
Egress Tunnel NE1_NE4_wor
king
NE2_NE4_wor
king
NE1_NE4_wor
king
NE2_NE4_wor
king

Table 3-117 QoS parameters
Parameter Data Service Common Internet Access
Service
CIR(kbit/s) 30720 102400
PIR(kbit/s) 51200 30720

3.6.3 Configuration Procedure (in End-to-End Mode)
This section describes the procedure for configuring E-LAN services carried by PWs in end-to-
end mode.
Prerequisites
l You are familiar with the networking requirements and service plan for E-LAN services
carried by PWs.
l The QoS policy has been configured according to the E-LAN service plan. For the
configuration method, see Creating the V-UNI Ingress Policy.
l If an E-LAN service carried by a PW needs to occupy a port exclusively, disable the DCN
function of the port. For details, see Configuring the DCN Function for a Port.
Procedure
Step 1 Configure tunnels carrying PWs by following instructions in 8.8 Configuring an MPLS
Tunnel.
Transmission System
135
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Pla
n
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected
NE2_NE4_w
orking
tional
Unprot
ected
NE2_NE4_pr
otection
tional
Unprot
ected

MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.
0.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.
0.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.
0.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.
0.0.1
-
Transmission System
136
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
30 N
E
2
Ingr
ess
- - 301 4-
EM6
F-2
300 - 18.1.
1.6
- - 130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
30
0
- - - 301 - 18.1.
1.5
130.
0.0.1
-
40 N
E
2
Ingr
ess
- - 405 4-
EM6
F-1
400 - 18.1.
1.1
- - 130.0
.0.4
N
E
1
Tra
nsit
4-
EM6
F-1
40
0
404 4-
EM6
F-2
401 405 18.1.
2.2
18.1.
1.2
- 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
40
1
403 4-
EM6
F-2
402 404 18.1.
2.6
18.1.
2.1
- 130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
40
2
- - - 403 - 18.1.
2.5
130.
0.0.2
-

Step 2 Configure MPLS tunnel OAM by following instructions in 8.10 Configuring MPLS Tunnel
OAM.
Paramet
er
Plan
MPLS
Tunnel
ID
10 20 30 40
OAM
Status
Detectio
n Mode
Transmission System
137
Paramet
er
Plan
Detectio
n Packet
Type
FFD
NOTE
Detection Packet
Type is FFD.
FFD FFD FFD
Detectio
n Packet
Period
(ms)
3.3
NOTE
Generally, an OAM
time can meet the
ms).
3.3 3.3 3.3

Step 3 Configure MPLS tunnel APS by following instructions in 8.12 Configuring Tunnel APS.
Parameter Plan
Protection
Type
1:1 1:1
Switching
Mode
Wo
rkin
g
Tun
nel
ID
10 30
Tun
nel
Nam
e
Pro
tect
ion
Tun
nel
ID
20 40
Tun
nel
Nam
e
Revertive
Mode
Revertive Revertive
Transmission System
138
Parameter Plan
WTR Time
(min)
5 5
Hold-off
Time (100
ms)
0
NOTE
ms).
0
Protocol
State
Enabled Enabled

Step 4 Configure E-LAN services carried by PWs in end-to-end mode.
1. Choose Service > VPLS Service > Create VPLS Service from the main menu.
2. In the upper left corner of the displayed tab page, set basic attributes of the VPLS service.
Table 3-122 Basic attributes of the VPLS service
Service Name E-LAN
Signaling Type LDP/Static
Networking Mode Full-Mesh VPLS
Service Type Service VPLS
VSI Name VSI1
VSI ID 25

3. Select the VPLS service node.
a. On the right of Node List, click Add and choose NPE.
b. Choose NE1, NE2, and NE3 under Physical Topology in the displayed dialog box.
4. Set parameters of the VPLS service node.
a. Sequentially select NE1, NE2 and NE4 from Node List, and click Detail.
b. Click the VSI Configuration tab and set parameters related to the VPLS service node.
Table 3-123 VPLS service parameters
Tag Type C-Aware
MAC Address Learning Enable
Transmission System
139
Learning Mode Unquality (SVL)

c. Configure a split horizon group for NE4. Click Split Horizon Group
Configuration and then set related parameters.
Table 3-124 Parameters for configuring a split horizon group
Select Components 2PW
Contained PWs PW ID:10
PW ID:20

5. Select tunnels for carrying the VPLS service.
a. Click the PW Configuration tab and select the PW between NE1 and NE4.
b. Click Modify. In the displayed dialog box, set PW parameters.
c. Set the PW between NE2 and NE4 by referring to the previous two steps.
NE1-NE4 NE2-NE4
Basic
attributes
PW ID 10 20
In Label 20 30
Out Label 20 30
Advance
d
attributes
Tunnel NE1_NE4_working NE2_NE4_working
Encapsulati
on Type
Ethernet Ethernet

d. Select the PW between NE1 and NE2 and click Delete.
6. Configure service access ports.
a. Click the SAI Configuration tab and select NE1 from NE List.
b. Click Create. In the displayed dialog box, set parameters for the service access port.
c. Set parameters for the service access ports on NE2 and NE4 by referring to the previous
two steps.
Transmission System
140
Table 3-126 Parameters for configuring service access ports
Par
am
eter
Value in This Example
NE1 NE2 NE4
Inte
rfac
e
4-EM6F-3 4-EM6F-4 4-EM6F-3 4-EM6F-4 4-EM6F-3
VL
AN
ID
100 200 100 200 100,200

7. Configure QoS.
a. Click the SAI QoS tab.
b. Select a port for which you need to configure QoS, and then set the QoS parameters.
Table 3-127 QoS parameters
Paramet
er
Value in This Example
NE1 NE2 NE4
Interface 4-EM6F-3 4-EM6F-4 4-EM6F-3 4-EM6F-4 4-EM6F-3
Directio
n
Ingress Ingress Ingress Ingress Ingress
Global
QoS
Policy
Templat
e
Select a predefined global QoS policy template.

----End
Related Tasks
Verify that the E-LAN services carried by PWs are configured correctly by following
instructions in 3.6.5 Verifying E-LAN Service Configurations.
3.6.4 Configuration Procedure (Configuration on a Per-NE Basis)
This section describes the procedure for configuring E-LAN services carried by PWs on a per-
NE basis.
Prerequisites
l You are familiar with the networking requirements and service plan for E-LAN services
carried by PWs.
Transmission System
141
l The QoS policy has been configured according to the E-LAN service plan. For the
configuration method, see Creating the V-UNI Ingress Policy.
l If an E-LAN service carried by a PW needs to occupy a port exclusively, disable the DCN
function of the port. For details, see Configuring the DCN Function for a Port.
Procedure
Step 1 Configure tunnels that carry PWs on NEs 1 to 4 by following instructions in 8.8 Configuring
an MPLS Tunnel.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Pla
n
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected
NE2_NE4_w
orking
tional
Unprot
ected
NE2_NE4_pr
otection
tional
Unprot
ected

MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.
0.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.
0.0.1
-
Transmission System
142
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.
0.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.
0.0.1
-
30 N
E
2
Ingr
ess
- - 301 4-
EM6
F-2
300 - 18.1.
1.6
- - 130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
30
0
- - - 301 - 18.1.
1.5
130.
0.0.1
-
40 N
E
2
Ingr
ess
- - 405 4-
EM6
F-1
400 - 18.1.
1.1
- - 130.0
.0.4
N
E
1
Tra
nsit
4-
EM6
F-1
40
0
404 4-
EM6
F-2
401 405 18.1.
2.2
18.1.
1.2
- 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
40
1
403 4-
EM6
F-2
402 404 18.1.
2.6
18.1.
2.1
- 130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
40
2
- - - 403 - 18.1.
2.5
130.
0.0.2
-

Step 2 Configure MPLS tunnel OAM on NE1, NE2 and NE4 by following instructions in 8.10
Transmission System
143
Paramet
er
Plan
MPLS
Tunnel
ID
10 20 30 40
OAM
Status
Detectio
n Mode
Detectio
n Packet
Type
FFD
NOTE
Detection Packet
Type is FFD.
FFD FFD FFD
Detectio
n Packet
Period
(ms)
3.3
NOTE
Generally, an OAM
time can meet the
ms).
3.3 3.3 3.3

Step 3 Configure MPLS tunnel APS on NE1, NE2 and NE4 by following instructions in 8.12
Parameter Plan
Protection
Type
1:1 1:1
Switching
Mode
Wo
rkin
g
Tun
nel
ID
10 30
Transmission System
144
Parameter Plan
Tun
nel
Nam
e
Pro
tect
ion
Tun
nel
ID
20 40
Tun
nel
Nam
e
Revertive
Mode
Revertive Revertive
WTR Time
(min)
5 5
Hold-off
Time (100
ms)
0
NOTE
ms).
0
Protocol
State
Enabled Enabled

Step 4 Configure an E-LAN service on NE4.
1. In the NE Explorer of NE4, choose Configuration > Packet Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
2. Click New. In the displayed New E-LAN Service dialog box, set the parameters for an E-
LAN service carried by a PW.
Table 3-132 Parameters for configuring an E-LAN service carried by a PW
Service ID 3
Service Name E-LAN-3
Tag Type C-Aware
Self-Learning MAC Address Enabled
MAC Address Learning Mode SVL
Transmission System
145

3. Click the UNI tab and click Configuration on the tab page. Set UNI parameters in the
displayed Configure Port dialog box. Click OK.
Port 4-EM6F-3
VLANs/CVLAN 100,200

4. Click the NNI tab and then the PW tab. Click Add. Set PW parameters in the displayed
Configure PW dialog box. Click OK.
Basic Attributes PW ID 10 20
PW Type Ethernet Ethernet
PW Incoming Label 20 30
PW Outgoing Label 20 30
Ingress Tunnel NE1_NE4_workin
g
NE2_NE4_workin
g
Peer LSR ID 130.0.0.1 130.0.0.2
Egress Tunnel NE1_NE4_workin
g
NE2_NE4_workin
g
Other parameters Default values Default values

5. Click the Split Horizon Group tab and click New on the tab page. Set parameters for the
split horizon group in the displayed New Split Horizon Group dialog box. Click OK.
Table 3-135 Parameters for configuring a split horizon group
Selected Interfaces PW(Ethernet,10)
PW(Ethernet,20)

6. Click Configure QoS. The Configure QoS dialog box is displayed.
Transmission System
146
7. Click the UNI tab. Set QoS parameters for the E-LAN service carried by a PW.
Table 3-136 QoS parameters for an E-LAN service carried by a PW
Interface 4-EM6F-3(PORT-3)
Direction Ingress
Policy Select a predefined QoS policy. For details
about how to define a QoS policy, see
Creating the V-UNI Ingress Policy.

Configure an E-LAN service carried by a PW on NE1 by referring to Step 4.
Service ID 1
Tag Type C-Aware

Port 4-EM6F-3 4-EM6F-4
VLANs/CVLAN 100 200

Transmission System
147
PW Type Ethernet
PW Incoming Label 20
PW Outgoing Label 20
Ingress Tunnel NE1_NE4_working
Egress Tunnel NE1_NE4_working

Interface 4-EM6F-3(PORT-3) 4-EM6F-4(PORT-4)
Direction Ingress Ingress
Policy Select a predefined QoS policy. For details about how to
define a QoS policy, see Creating the V-UNI Ingress Policy.

Configure an E-LAN service carried by a PW on NE2 by referring to Step 4.
Service ID 2
Tag Type C-Aware

Transmission System
148
Port 4-EM6F-3 4-EM6F-4
VLANs/CVLAN 100 200

PW Type Ethernet
PW Incoming Label 30
PW Outgoing Label 30
Ingress Tunnel NE2_NE4_working
Egress Tunnel NE2_NE4_working

Interface 4-EM6F-3(PORT-3) 4-EM6F-4(PORT-4)
Direction Ingress Ingress
Policy Select a predefined QoS policy. For details about how to
define a QoS policy, see Creating the V-UNI Ingress Policy.

----End
Related Tasks
Verify that the E-LAN services carried by PWs are configured correctly by following
instructions in 3.6.5 Verifying E-LAN Service Configurations.
Transmission System
149
3.6.5 Verifying E-LAN Service Configurations
After configuring E-LAN services carried by PWs, verify that all configurations are correct.
Prerequisites
l E-LAN services carried by PWs have been configured in accordance with actual conditions.
Procedure
Step 1 Optional: If the E-LAN services carried by PWs are configured on a per-NE basis, convert
discrete virtual private LAN services (VPLSs) into complete VPLS services.
1. Choose Service > Search for IP Service from the main menu.
2. Set a service search policy in the displayed dialog box.
3. Click Start.
4. After the searching is complete, click Close.
Step 2 Choose Service > VPLS Service > Manage VPLS Service from the main menu.
Step 3 In the displayed dialog box, set filter criteria and click Filter to query all E-LAN services that
meet the filter criteria.
Step 4 Right-click the desired PW-carried E-LAN service and choose Ethernet OAM > LB Test from
the shortcut menu.
Step 5 In the displayed dialog box, select the source NE and sink NE, and click Run.
Step 6 After the test is complete, click the LB Statistic Information tab to check service connectivity.
NOTE
If the number of received packets and the number of transmitted packets are the same, the service is
available.
----End
Transmission System
150
4 Configuring Native Ethernet Services on the
Packet Plane
About This Chapter
Native Ethernet services on the packet plane include Native E-Line services and Native E-LAN
services.
4.1 Basic Concepts
Before configuring the Ethernet services, you need to be familiar with the basic concepts.
4.2 Configuration Procedure
The service configuration procedure differs according to the specific service type.
4.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)
This section considers a point-to-point transparently transmitted E-Line service as an example
to describe how to configure the Ethernet service according to the network planning information.
4.4 Configuration Example (VLAN-Based E-Line Service)
This section considers a VLAN-based E-line service as an example to describe how to configure
the Ethernet service according to the network planning information.
4.5 Configuration Example (QinQ-Based E-Line Service)
This section considers a QinQ-based E-line service as an example to describe how to configure
4.6 Configuration Example (802.1d Bridge-Based E-LAN Service)
This section considers an 802.1d bridge-based E-LAN service as an example to describe how
to configure the Ethernet service according to the network planning information.
4.7 Configuration Example (802.1q Bridge-Based E-LAN Service)
This section considers an 802.1q bridge-based E-LAN service as an example to describe how
4.8 Configuration Example (802.1ad Bridge-Based E-LAN Service)
This section considers an 802.1ad bridge-based E-LAN service as an example to describe how
Transmission System
Configuration Guide (Packet Transport Domain) 4 Configuring Native Ethernet Services on the Packet Plane
151
4.1 Basic Concepts
Before configuring the Ethernet services, you need to be familiar with the basic concepts.
4.1.1 Ethernet Port Numbers
On the NMS, Ethernet ports are represented by PORTs.
l OptiX OSN 550:
For the EM6F, GE1 and GE2 correspond to PORT-1 and PORT-2 respectively; FE1 to
FE4 correspond to PORT-3 to PORT-6 respectively.
For the EM6T, GE1 and GE2 correspond to PORT-1 and PORT-2 respectively; FE1 to
For the EF8F, FE1 to FE8 correspond to PORT-1 to PORT-8 respectively.
For the EX1, 10GE1 corresponds to PORT-1.
For the EG4C: GE1 to GE4 and FE1 to FE4 both correspond to PORT-1 to PORT-4.
NOTE
The EG4C provides 4xGE/FE optical/electrical ports. The former four ports are pluggable SFP
optical ports and the latter four are fixed electrical ports. The ports with the same number cannot
be used simultaneously.
l OptiX OSN 500:
For the EM6F, GE1 and GE2 correspond to PORT-1 and PORT-2 respectively; FE1 to
For the EM6T, GE1 and GE2 correspond to PORT-1 and PORT-2 respectively; FE1 to
For the EF8F, FE1 to FE8 correspond to PORT-1 to PORT-8 respectively.
4.1.2 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.
Auto-Negotiation Function of FE Electrical Ports
NOTE
If auto-negotiating equipment does not support the half-duplex mode, the auto-negotiation result will be a
full-duplex mode at the corresponding rate level.
In the case of FE electrical ports, there are four common working modes: 10M half-duplex, 10M
full-duplex, 100M half-duplex, and 100M full-duplex. If the working mode of the local FE
electrical port does not match the working mode of the opposite FE electrical port, the two ports
cannot communicate with each other. With the auto-negotiation function, however, the two ports
can communicate with each other. The auto-negotiation function uses fast link pulses and normal
link pulses to transfer the negotiation information of the working mode so that the working mode
of the local FE electrical port matches the working mode of the opposite FE electrical port.
Table 4-1 lists the FE auto-negotiation rules.
Transmission System
152
Table 4-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adopts
the auto-negotiation mode)
Working Mode of the Opposite FE
Electrical Port
Auto-Negotiation Result
Auto-negotiation 100M full-duplex
10M half-duplex 10M half-duplex
10M full-duplex 10M half-duplex

NOTE
As provided in Table 4-1, when the working mode of the opposite FE electrical port is 10M full-duplex or 100M
full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the FE
electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the opposite
FE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of the local FE
electrical port to 10M full-duplex or 100M full-duplex.
When the FE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate the flow control function through the auto-negotiation function.
Auto-Negotiation Function of GE Electrical Ports
In the case of GE electrical ports, there are five working modes: 10M half-duplex, 10M full-
duplex, 100M half-duplex, 100M full-duplex, and 1000M full-duplex. The auto-negotiation
function of GE electrical ports is similar to the auto-negotiation function of FE electrical ports.
Table 4-2 lists the auto-negotiation rules of GE electrical ports.
Table 4-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adopts
the auto-negotiation mode)
Working Mode of the Opposite GE
Electrical Port
Auto-Negotiation Result
Auto-negotiation (GE electrical port) 1000M full-duplex
Auto-negotiation (FE electrical port) 100M full-duplex
1000M full-duplex 1000M full-duplex

Transmission System
153
NOTE
As provided in Table 4-2, when the working mode of the opposite GE electrical port is 10M full-duplex or
100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the
GE electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the
opposite GE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of the
local GE electrical port to 10M full-duplex or 100M full-duplex.
When the GE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate the flow control function through the auto-negotiation function.
Auto-Negotiation Function of GE Optical Ports
GE optical ports support only the 1000M full-duplex working mode. The auto-negotiation
function of GE optical ports is used only for negotiating the flow control function.
4.1.3 Flow Control Function
When the equipment fails to handle the flow received at the port due to poor data processing/
transferring capability, congestion occurs on the line. To reduce the number of discarded packets
caused by buffer overflow, 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 auto-negotiation mode, you can adopt the auto-negotiation flow
control function. The auto-negotiation flow control modes include the following:
l Asymmetric PAUSE toward the link partner
The port can transmit PAUSE frames in the case of congestion but cannot process the
received PAUSE frames.
l Symmetric PAUSE
The port can transmit PAUSE frames and process the received PAUSE frames.
l Both asymmetric and symmetric PAUSE
The port has the following capabilities:
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 Disabled
The port does not transmit or process PAUSE frames.
NOTE
The OptiX OSN equipment supports only two auto-negotiation flow control modes, namely, disabled mode and
symmetric PAUSE mode.
Transmission System
154
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 Symmetric
The port can transmit PAUSE frames and can also process received PAUSE frames.
l Disabled
The port does not transmit or process PAUSE frames.
NOTE
The OptiX OSN equipment supports only two non-auto-negotiation flow control modes, namely, disabled mode
and symmetric mode.
4.1.4 Native Ethernet Service Types Based on the Packet Plane
Based on the packet plane, Native Ethernet services are classified into six types.
4.1.4.1 Point-to-Point Transparently Transmitted E-Line Services
The point-to-point transparently transmitted E-Line services are the basic E-Line model. Point-
to-point transmission does not involve service bandwidth sharing, service isolation, or service
distinguishing; instead, Ethernet services are transparently transmitted between two service
access points.
Service Model
Table 4-3 describes the point-to-point transparently transmitted E-Line service model.
Table 4-3 Point-to-point transparently transmitted E-Line service model
Service Model Encapsulation
Type
Service Direction Traffic Flow Description
Model 1 Null (source)
Null (sink)
UNI-UNI PORT (source)
PORT (sink)
The source port
transparently
transmits all the
received Ethernet
frames to the sink
port.
Transmission System
155
Service Model Encapsulation
Type
Service Direction Traffic Flow Description
Model 2 802.1Q (source)
802.1Q (sink)
UNI-UNI PORT (source)
PORT (sink)
The source port
processes the
incoming Ethernet
frames based on its
TAG attribute, and
then sends the
processed Ethernet
frames to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.

NOTE
In service model 2, ports process the received Ethernet frames according to their TAG attributes. Therefore,
service model 2 is not a real transparent transmission model and is not recommended.
Typical Application
Figure 4-1 shows the typical application of service model 1.
Port 1
NE 1
NE 2
Port 2
Port 3
Port 1
Port 2
Port 3
Service 1
Service 2
Service 1
Service 2
E-Line
E-Line
Transmission
Network
Port 4 Port 4
E-Line
E-Line
In service model 1, Ethernet service 1 and Ethernet service 2, which carry no VLAN ID or carry
unknown VLAN IDs, are accessed to NE1 through port 1 and port 2 respectively. Port 1 and
port 2 transparently transmit Ethernet service 1 and Ethernet service 2 to port 3 and port 4,
respectively. Port 3 and port 4 then transmit Ethernet service 1 and Ethernet service 2 to NE2.
Service processing on NE2 is the same as on NE1.
In service model 2, Ethernet service 1 and Ethernet service 2, which carry unknown VLAN IDs,
are accessed to NE1 through port 1 and port 2 respectively. Port 1 and Port 2 process the incoming
packets based on their TAG attributes. Then, Port 1 and Port 2 send Ethernet service 1 and
Ethernet service 2 to Port 3 and Port 4 respectively. Port 3 and Port 4 process the incoming
packets based on their TAG attributes. Then, Port 3 and Port 4 send Ethernet service 1 and
Ethernet service 2 to NE2. Service processing on NE2 is the same as on NE1.
Transmission System
156
4.1.4.2 VLAN-Based E-Line Services
VLANs can be used to separate E-Line services. With the VLAN technology, multiple E-Line
services can share one physical channel. These services are VLAN-based E-Line services.
Models of Services
Table 4-4 shows the models of VLAN-based E-Line services.
Table 4-4 Models of VLAN-based E-Line services
Type of Service Encapsulation
Mode of Port
Direction of
Service
Flow of Service Description of
Service
VLAN-based E-
Line services
802.1Q (source)
802.1Q (sink)
UNI-UNI PORT+VLAN
(source)
PORT+VLAN
(sink)
NOTE
The VLAN ID of the
source and the VLAN
ID of the sink must be
the same.
The source port
processes the
incoming Ethernet
frames based on its
TAG attribute, and
then sends the
Ethernet frames
with a specific
VLAN ID to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.

Typical Applications
Figure 4-2 shows the typical application of VLAN-based E-Line services. Service 1 and Service
2 carry different VLAN IDs. Therefore, after the two Ethernet services are accessed to NE1
through Port 1 and Port 2 respectively, they can share the same transmission channel at Port 3.
On NE1, Port 1 and Port 2 process the incoming packets based on their own TAG attributes.
Then, Port 1 and Port 2 send Service 1 and Service 2 to Port 3. Port 3 processes all the outgoing
packets based on its TAG attribute, and then sends Service 1 and Service 2 to NE2. Due to the
different VLAN IDs, Service 1 and Service 2 can be transmitted through Port 3 at the same time.
NE2 processes Service 1 and Service 2 in the same manner as NE1.
Figure 4-2 Model of VLAN-based E-Line services
Port 1
NE 1
NE 2
Port 2
Port 3
E
-L
in
e
Port 1
Port 2
Port 3
E-Line
E
-L
in
e
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
E-Line Transmission
Network
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Transmission System
157

4.1.4.3 QinQ-Based E-Line Services
S-VLAN tags can be used to isolate E-Line services. Therefore, multiple E-Line services can
share one physical channel. These services are QinQ-based E-Line services.
NOTE
E-Line Services Carried on PWs describes QinQ-based E-Line services carried by PWs.
Model of Service
Table 4-5 shows the models of QinQ-based E-Line services.
Table 4-5 Models of QinQ-based E-Line Services
Model of Service Encapsulation
Mode of a Port
Direction Flow of Service Description of
Service
Model 1 Null (source)
QinQ (sink)
UNI-NNI PORT (source)
QinQ link (sink)
The source port adds
the S-VLAN tag that
corresponds to the
QinQ link to all the
Ethernet frames, and
then transmits the
Ethernet frames to
the sink port where
the QinQ link is
configured.
Model 2
802.1Q (source)
a
QinQ (sink)
UNI-NNI PORT (source)
QinQ link (sink)
The source port
accesses only the
Ethernet frames that
carry C-VLAN tags.
It adds the S-VLAN
tag that corresponds
to the QinQ link to
all the Ethernet
frames, and then
transmits the
Ethernet frames to
the sink port where
the QinQ link is
configured.
Transmission System
158
Model of Service Encapsulation
Mode of a Port
Direction Flow of Service Description of
Service
Model 3
802.1Q (source)
a
QinQ (sink)
UNI-NNI PORT+C-VLAN
(source)
QinQ link (sink)
The source port adds
the S-VLAN tag that
corresponds to the
QinQ link to all the
carry specific C-
VLAN tags, and
then transmits the
Ethernet frames to
the sink port where
the QinQ link is
configured.
Model 4 QinQ (sink)
QinQ (sink)
NNI-NNI QinQ link (source)
QinQ link (sink)
The source port
transmits the
carry the S-VLAN
tag to the sink port
where the sink QinQ
link is configured.
The S-VLAN tag
carried in the
Ethernet frames
corresponds to the
source QinQ link. If
the source and sink
QinQ links
correspond to
different S-VLAN
tags, the S-VLAN
tags carried in the
Ethernet frames are
exchanged.

NOTE
a: Set TAG to Tag Aware.
Service 1 and Service 2 include tagged frames and untagged frames. Service 1 is accessed to
NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the
corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to
Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1
and Service 2 to NE2.
Transmission System
159
Port 1
NE 1
NE 2
Port 2
Port 3
E
-L
in
e
Port 1
Port 2
Port 3
E
-Line
E
-L
in
e
Service 1
Service 2
E-Line Transmission
Network
Service 1
Service 2
Add S-VLAN Label Strip S-VLAN Label
Data(2)
Data(1)
S-VLAN(400)
S-VLAN(300)
Data(2)
Data( 1)
Data(2)
Data(1)
S-VLAN(400)
S-VLAN(300)
Data(2)
Data(1)
Service 1 and Service 2 carry different unknown C-VLAN tags. Service 1 is accessed to NE1
through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the corresponding
S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then,
Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to
NE2.
Port 1
NE 1
NE 2
Port 2
Port 3
E
-L
in
e
Port 1
Port 2
Port 3
E-Line
E
-L
in
e
Service 1
Unknown CVLAN
E-Line Transmission
Network
Data(2)
Data(1)
S-VLAN(400)
S-VLAN(300) C-VLAN
C-VLAN Data(2)
Data( 1)
C-VLAN
C-VLAN
Strip S-VLAN Label Add S-VLAN Label
Data(2)
Data( 1)
C-VLAN
C-VLAN
Data(2)
Data(1)
S-VLAN(400)
S-VLAN(300) C-VLAN
C-VLAN
Service 2
Unknown CVLAN
Service 1
Unknown CVLAN
Service 2
Unknown CVLAN
Service 1 and Service 2 carry different C-VLAN tags. Service 1 is accessed to NE1 through Port
1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the corresponding S-VLAN tag
to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and
Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2.
Transmission System
160
Port 1
NE 1
NE 2
Port 2
Port 3
E
-L
in
e
Port 1
Port 2
Port 3
E-Line
E
-L
in
e
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
E-Line Transmission
Network
Data(2)
Data(1)
S-VLAN(400)
S-VLAN(300) C-VLAN(100)
C-VLAN(200) Data(2)
Data( 1)
C-VLAN(200)
C-VLAN(100)
Strip S-VLAN Label Add S-VLAN Label
Data(2)
Data( 1)
C-VLAN(200)
C-VLAN(100)
Data(2)
Data(1)
S-VLAN(400)
C-VLAN(200)
Service 1 and Service 2 carry a same S-VLAN tag. Service 1 is accessed to NE1 through Port
1, and Service 2 is accessed to NE1 through Port 2. Port 1 changes the S-VLAN tag carried in
Service 1 and Port 2 changes the S-VLAN tag carried in Service 2 so that the S-VLAN tags
carried in Service 1 and Service 2 are different. Port 3 transmits Service 1 and Service 2 to NE2.
Port 1
NE 1
NE 2
Port 2
Port 3
E
-L
in
e
Port 1
Port 2
Port 3
E-Line
E
-L
in
e
Service 1
S-VLAN ID: 100
Service 2
S-VLAN ID: 100
E-Line Transmission
Network
Service 1
S-VLAN ID: 100
Service 2
S-VLAN ID: 100
Switching S-VLAN Label
Data(2)
Data(1)
S-VLAN(400)
S-VLAN(300)
Data(2)
Data( 1)
S-VLAN(100)
S-VLAN(100)
Switching S-VLAN Label
Data(2)
Data(1)
S-VLAN(100)
S-VLAN(100)
Data(2)
Data( 1)
S-VLAN(400)
S-VLAN(300)
4.1.4.4 E-LAN Services Based on the 802.1d Bridge
In the case of E-LAN services, packets can be forwarded only based on the MAC address table.
These E-LAN services are E-LAN services based on the 802.1d bridge.
Model of Service
Table 4-6 shows the model of E-LAN services based on the 802.1d bridge.
Transmission System
161
Table 4-6 Model of E-LAN services based on the 802.1d bridge
Type of
Service
Encapsulation
Mode of Port
Tag Attribute Type of
Logical Port
Learning
Mode
Sub-
Switching
Domain
E-LAN services
based on the
802.1d bridge
Null Tag-
Transparent
PORT SVL No division of
sub-switching
domains

Typical Application
Figure 4-7 shows the typical application of the model of service. The transmission network
needs to carry the A services accessed from NE2 and NE3. The two A services are converged
at the convergence node NE1. The services need not to be isolated. Therefore, an 802.1d bridge
is used at NE1 to groom services.
Figure 4-7 Model of E-LAN services based on the 802.1d bridge
Port 1
NE 1
User A1
Port 1
NE 2
User A2
NE 3
Port 2
Port 2
Port 3
Transmission
Network
Transmission
Network
802.1d bridge
Port 1
Port 2
User A3

4.1.4.5 E-LAN Services Based on 802.1q Bridge
E-LAN services can be separated by setting VLANs. In this case, a bridge is divided into multiple
sub-switching domains. Therefore, the E-LAN services separated by setting VLANs are E-LAN
services based on 802.1q bridge.
Model of Service
Table 4-7 shows the models of E-LAN services based on 802.1q bridge.
Transmission System
162
Table 4-7 Model of E-LAN services based on 802.1q bridge
Type of
Service
Encapsulation
Mode of Port
TAG
Attribute
Type of
Logical Port
Learning
Mode
Sub-
Switching
Domain
E-LAN services
based on 802.1q
bridge
802.1q C-Aware PORT+VLAN IVL Sub-switching
domains are
divided based on
VLANs.

Figure 4-8 shows the typical application of the model of E-LAN services based on 802.1q bridge.
The transmission network needs to carry G and H services accessed from NE2 and NE3. Both
types of services are converged on NE1. G and H services adopt different VLAN planning.
Therefore, 802.1q bridge is used on NEs and sub-switching domains are divided based on
VLANs, differentiating and separating the two types of services.
Figure 4-8 Model of E-LAN services based on 802.1q bridge
Port 1
NE 1
VLAN 100
VLAN 200
Port 2
User G1
User H1
Port 1
NE 2
User G2
Port 2
User H2
Port 1
NE 3
User G3
Port 2
User H3
VLAN 100
VLAN 200
VLAN 100
VLAN 200
Port 3
Port 3
Port 3
Port 4
Transmission
Network
Transmission
Network
802.1q bridge
802.1q bridge
802.1q bridge

NOTE
You can configure 4.1.4.2 VLAN-Based E-Line Services on NE2 and NE3 for service access.
4.1.4.6 E-LAN Services Based on 802.1ad Bridge
S-VLAN tags can be used to isolate E-LAN services. Therefore, a bridge is divided into multiple
independent sub-switching domains. These services are E-LAN services based on 802.1ad
bridge.
Transmission System
163
Model of Service
Table 4-8 shows the models of E-LAN services based on 802.1ad bridge.
Table 4-8 Models of E-LAN services based on 802.1ad bridge
Type of
Services
Encapsulation
Mode of Port
Tag Attribute Type of
Logical Port
Learning
Mode
Sub-
Switching
Domain
E-LAN services
based on
802.1ad bridge
Null or 802.1q
(UNI port)
a
QinQ (NNI port)
S-Aware PORT (The
encapsulation
mode of the UNI
port is Null.)
PORT or PORT
+C-VLAN (The
encapsulation
mode of the UNI
port is 802.1q.)
a
PORT+S-
VLAN (NNI
port)
IVL Sub-switching
domains are
divided based on
S-VLAN tags.

NOTE
a: When the encapsulation mode of port is 802.1q, the tag attribute must be Tag Aware.
Figure 4-9 shows the typical application of the model of service. The transmission network
needs to carry G and H services accessed from NE2 and NE3. The two types of services are
converged on NE1. Since G and H services have a same C-VLAN tag, you need to add different
S-VLAN tags to G and H services for service isolation.
Transmission System
164
Figure 4-9 Model of E-LAN services based on 802.1ad bridge
Port 1
NE 1
802.1ad bridge
SVLAN 300
SVLAN 400
Port 2
User G1
User H1
Port 1
NE 2
User G2
Port 2
User H2
Port 1
NE 3
User G3
Port 2
User H3
Port 3
Port 3
Port 4
Transmission
Network
Transmission
Network
CVLAN 100
CVLAN 100
SVLAN 300
SVLAN 400
SVLAN 300
SVLAN 400
Port 3
802.1ad bridge
802.1ad bridge
Add S-VLAN Label
NE 1
Strip S-VLAN Label
CVLAN 100
CVLAN 100
CVLAN 100
CVLAN 100
Data(H)
Data(G)
S-VLAN(400)
C-VLAN(100) Data(H)
Data( G)
C-VLAN(100)
C-VLAN(100)
Strip S-VLAN Label
NE 2
Add S-VLAN Label
Data(H)
Data( G)
C-VLAN(100)
C-VLAN(100)
Data(H)
Data(G)
S-VLAN(400)
C-VLAN(100)
Strip S-VLAN Label
NE 3
Add S-VLAN Label
Data(H)
Data( G)
C-VLAN(100)
C-VLAN(100)
Data(H)
Data(G)
S-VLAN(400)
C-VLAN(100)

NOTE
You can configure 4.1.4.3 QinQ-Based E-Line Services on NE2 and NE3 for service access.
4.1.5 Managing a MAC Address Table
The entries in a MAC address table indicate the corresponding relationship between MAC
addresses and ports. A MAC address table contains the following entries: dynamic entry, static
entry, and blacklist entry.
NOTE
If one dynamic entry is not updated in a certain period, that is, if no new packet from this MAC address is
received to enable the re-learning of this MAC address, this dynamic entry is automatically deleted. This
mechanism is called aging, and this period is called aging time.
l Dynamic entry
A dynamic entry is obtained by learning of a bridge through the SVL/IVL mode. The
dynamic entry ages.
l Static entry
Transmission System
165
A static entry is manually added by a network administrator to the MAC address table by
using the NMS. The static entry does not age. Generally, the static entry is configured when
a port corresponds to a device with its MAC address known and this device transmits large
traffic for a long time.
l Blacklist entry
A blacklist entry, that is, the MAC disabled entry, is used to discard the data frame that
contains the specified MAC address (source MAC address or destination MAC address).
A blacklist entry is also called a blackhole entry. The blacklist entry is configured by the
network administrator. The blacklist entry does not age, and is not lost after the Ethernet
processing board is reset.
4.1.6 VLAN Forwarding Table
Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If it is required to
change the VLAN IDs, you need to configure a VLAN forwarding table.
In the case of VLAN-based E-Line services, the VLAN IDs on the source and sink nodes are
usually set to the same value. If it is required that packets carry different VLAN IDs on the
source and sink nodes, the different VLAN IDs need to be set on the source and sink nodes of
the E-Line services. In addition, you need to configure a VLAN forwarding table to achieve the
exchange of VLAN IDs at the source and sink nodes.
Single Service Transmit
Figure 4-10 shows an application of the VLAN forwarding table. In this figure, Service 1 carries
a VLAN ID of 100 and is transmitted to NE1 through Port 1. On a transmission network, the
VLAN ID of Service 1 may be in conflict with the VLAN IDs of other services. To avoid this
situation, the VLAN ID of Service 1 must be changed to another value before it is transmitted
on the transmission network and then be changed to the original value after it is transmitted out
of the transmission network. Therefore, a VLAN forwarding table is configured at NE1 and
NE2, so that the VLAN IDs of services between Port 1 and Port 3 can be changed as required.
With regard to Service 1, when it traverses NE1, the VLAN ID is changed from 100 to 200 and
then changes to 100 again at NE2.
Figure 4-10 Application of VLAN forwarding tables to single E-Line service
VLAN Forwarding Table
Port 1
NE 1
NE 2
Port 3
Port 1
Service 1
VLAN ID: 100
Port 3
Service 1
VLAN ID: 100
E
-L
in
e
E
-L
in
e
Source
Interface
Port 1 Port 3 100 200
Port 3 Port 1 200 100
Sink
Interface
Source
VLAN ID
Sink
VLAN ID
Source
Interface
Port 1 Port 3 100 200
Port 3 Port 1 200 100
Sink
Interface
Source
VLAN ID
Sink
VLAN ID
Transmission
Network
Service 1
VLAN ID: 200
Service 1
VLAN ID: 200
E-Line Service Information Table
Source
Interface
Port 1 Port 3 100, 200
Sink
Interface
Source
VLAN ID
Sink
VLAN ID
E-Line Service Information Table
Source
Interface
Port 1 Port 3 100, 200
Sink
Interface
Source
VLAN ID
Sink
VLAN ID
100, 200 100, 200
Transmission System
166

Multi-Services Transmit
Figure 4-11 shows the application of VLAN forwarding tables. Service 1 and Service 2 carry
the same VLAN ID, and the services are accessed to NE1 through Port 1 and Port 2 respectively.
The services need to be separated so that they can be transmitted through one port at the same
time. Configure the VLAN forwarding table on NE1 for changing the VLAN ID of the service
transmitted between Port 1 and Port 3. After Service 1 is accessed into NE1, the VLAN ID of
Service 1 is changed from 100 to 200. Therefore, Service 1 and Service 2 carry different VLAN
IDs at Port 3 and the services are separated.
Figure 4-11 Application of VLAN forwarding tables to multi E-Line services
Port 1
NE 1
NE 2
Port 3
Port 1
Service 1
VLAN ID: 100
Port 3
Service 1
VLAN ID: 100
Service 2
VLAN ID: 100
Service 2
VLAN ID: 100
E
-L
in
e
E
-L
in
e
Source
Interface
Port 1 Port 3 100 200
Port 3 Port 1 200 100
Sink
Interface
Source
VLAN ID
Sink
VLAN ID
Source
Interface
Port 1 Port 3 100 200
Port 3 Port 1 200 100
Sink
Interface
Source
VLAN ID
Sink
VLAN ID
Transmission
Network
E
-L
in
e
Port 2
Service 2
VLAN ID: 100
Service 2
VLAN ID: 100
Service 1
VLAN ID: 200
Service 1
VLAN ID: 200
E
-L
in
e
Port 2

4.1.7 Split Horizon Group
Convergence services received from different ports are isolated to prevent a broadcast storm
resulting from a service loop and improve service security. To implement service isolation, you
can configure a split horizon group for the E-LAN services at the specified nodes. The logical
ports in one split horizon group cannot forward packets to each other.
Figure 4-12 shows a typical application of the split horizon group. NEs on the network are
configured with E-LAN services, and the east and west ports and service access ports are
configured as mounted ports of a bridge. In this case, if a split horizon group is not configured
at NE1, broadcast storm occurs due to a network loop as the east and west ports can forward
packets to each other. If a split horizon group is created at NE1 and the east and west ports are
configured as members of the split horizon group, the east and west ports do not forward packets
to each other. Therefore, a service loop is prevented.
Transmission System
167
Figure 4-12 Split horizon group

The service configuration procedure differs according to the specific service type.
4.2.1 Configuration Procedure (Point-to-Point Transparently
Transmitted E-Line Services)
This section describes how to perform parameter settings and other relevant operations as
required in the procedures for configuring point-to-point transparently transmitted E-Line
services.
Configuration Flow Chart
Figure 4-13 provides the procedures for configuring point-to-point transparently transmitted E-
Line services.
Transmission System
168
Figure 4-13 Configuration flow chart (point-to-point transparently transmitted E-Line services)
Start
Required
Optional
End
Configuring E-Line services
Configuring Ethernet ports
Verifying Ethernet service
configurations
Configuring QoS

The procedures in the configuration flow chart are described as follows.
Procedures for Configuring Ethernet Ports
Table 4-9 Procedures for configuring Ethernet ports
Operation Description
8.1.1 Setting
the General
Attributes of
Ethernet
Interfaces
Required. Set the parameters as follows:
l In the case of used ports, set Enable Port to Enabled. In the case of
unused ports, set Enable Port to Disabled.
l Set Encapsulation Type to Null.
l In the case of an Ethernet port that is connected to external equipment,
set Working Mode to be the same value as the external equipment (the
working mode of the external equipment is generally auto-negotiation).
In the case of an Ethernet port within the network, set Working
Mode to Auto-Negotiation.
l When jumbo frames are transmitted, set Max Frame Length(byte)
according to the actual length of the jumbo frames. Otherwise, it is
recommended that you set Max Frame Length(byte) to 1620.
Transmission System
169
8.1.5
Configuring
Flow Control
Required when the flow control function is enabled on the external
equipment to which the Ethernet port is connected. Set the parameters as
follows:
l When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
l When the external equipment uses the auto-negotiation flow control
function, set Negotiation Flow Control Mode to Enable Symmetric
Flow Control.
8.1.4 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.

Procedures for Configuring E-Line Services
Table 4-10 Procedures for configuring E-Line services
8.17.3
Configuring
UNI-UNI E-
Line Services
l Set Direction to UNI-UNI.
l Set Source Port and Sink Port according to the planning information.
l Source VLANs and Sink VLANs remain null.
8.17.2 Creating
a VLAN
Forwarding
Table Item
Required when the VLAN tags of the Ethernet service need to be swapped
at the source and sink.
Set the parameters according to the network planning information.
NOTE
The corresponding VLAN forwarding table entries need to be configured for the
source port and sink port.

Transmission System
170
Procedures for Configuring QoS
Table 4-11 Procedures for configuring QoS
8.28.1
Modifying the
Mapping
Relationships
for the DS
Domain
Required when the default mapping relationships for the DS domain do
not meet the actual requirements.
8.28.2
Changing the
Ports in a DS
Domain and
Their Trusted
Packet Types
Required when the packet type trusted by a port is not the default trusted
packet type (C-VLAN priority) applied to the DS domain.
Creating a DS
Domain
Required when multiple DS domains are to be created.
Creating a Port
Policy
Required when you need to apply QoS policies other than DS and port
shaping for a specific port.
Creating a
Traffic Flow
Required when you need to perform the ACL, CoS, CAR, or shaping
operation for a specific flow over the port.
8.28.3 Setting
the Port That
Uses the Port
Policy
Required when the new port policy is created.
Configuring
Port Shaping
Required if you need to limit the egress bandwidth that an Ethernet service
occupies.

4.2.2 Configuration Procedure (VLAN-Based E-Line Services)
This section describes the procedures for configuring the service information, port information,
protection information, and QoS information of a VLAN-based E-Line service and the procedure
for verifying the service configurations.
Figure 4-14 provides the procedures for configuring VLAN-based E-Line services.
Transmission System
171
Figure 4-14 Configuration flow chart (VLAN-based E-Line services)
Start
Required
Optional
End
configurations
Configuring QoS

8.1.1 Setting
the General
Attributes of
Ethernet
Interfaces
l Set Encapsulation Type to 802.1Q.
l In the case of the Ethernet port that is connected to the external
equipment, set Working Mode to be the same value as the external
equipment (generally, the working mode of the external equipment is
auto-negotiation). In the case of the Ethernet ports within the network,
set Working Mode to Auto-Negotiation.
Transmission System
172
8.1.5
Configuring
Flow Control
equipment to which the Ethernet port is connected. Set the parameters as
follows:
function, set Negotiation Flow Control Mode to Enable Symmetric
Flow Control.
8.1.2 Setting
the Layer 2
Attributes of
Ethernet Ports
l If all the accessed services carry VLAN tags (tagged frames), set
TAG to Tag Aware.
l If none of the accessed services carries VLAN tags (untagged frames),
set TAG to Access, and set Default VLAN ID and VLAN Priority
according to the network planning information.
l If the accessed services contain both tagged frames and untagged
frames, set TAG to Hybrid, and set Default VLAN ID and VLAN
Priority according to the network planning information.
8.1.4 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.

8.17.3
Configuring
UNI-UNI E-
Line Services
l Set Source Port and Sink Port according to the network planning
information.
l Set Source VLANs and Sink VLANs according to the network
planning information. The two parameters should be set to the same
value.
Transmission System
173
8.17.2 Creating
a VLAN
Forwarding
Table Item
Required when the VLAN tags of the Ethernet service need to be switched
at the source and sink.
The parameters need to be set according to the network planning
information.
NOTE
The corresponding VLAN forwarding table entries need to be configured for the
source port and sink port.

8.28.1
Modifying the
Mapping
Relationships
for the DS
Domain
8.28.2
Changing the
Ports in a DS
Domain and
Their Trusted
Packet Types
Creating a DS
Domain
Creating a Port
Policy
Creating a
Traffic Flow
8.28.3 Setting
the Port That
Uses the Port
Policy
Configuring
Port Shaping
occupies.

Transmission System
174
4.2.3 Configuration Procedure (QinQ-Based E-Line Services)
protection information, and QoS information of a QinQ-based E-Line service and the procedure
for verifying the service configurations.
Figure 4-15 provides the procedures for configuring QinQ-based E-Line services.
Figure 4-15 Configuration flow chart (QinQ-based E-Line services)
Start
Required
Optional
End
configurations
Configuring QoS

8.1.1 Setting the
General
Attributes of
Ethernet
Interfaces
Transmission System
175
8.1.5
Configuring
Flow Control
equipment to which the Ethernet port is connected. Set the parameters
as follows:
function, set Auto-Negotiation Flow Control Mode to Enable
Symmetric Flow Control.
8.1.2 Setting the
Layer 2
Attributes of
Ethernet Ports
Required.
In the case of an NNI that is connected to the external equipment, set
QinQ Type Domain according to the T-PID of the S-VLAN that is
supported by the external equipment. In the case of NNIs within the
network, QinQ Type Domain takes the default value.
8.1.4 Setting the
Advanced
Attributes of
Ethernet Ports
Optional.

8.17.1 Creating
a QinQ Link
Required.
8.17.7 Creating
UNI-NNI E-
Line Services
Carried by
QinQ Links
Required.

Transmission System
176
8.28.1
Modifying the
Mapping
Relationships
for the DS
Domain
8.28.2
Changing the
Ports in a DS
Domain and
Their Trusted
Packet Types
Creating a DS
Domain
Creating a Port
Policy
Creating a
Traffic Flow
8.28.3 Setting
the Port That
Uses the Port
Policy
Configuring
Port Shaping
occupies.

Transmission System
177
Procedures for Verifying Ethernet Service Configurations
Table 4-18 Procedures for verifying Ethernet service configurations
Creating an MD Required in the case of the NEs where the two Ethernet ports involved in
the service test are located. Set the parameters as follows:
l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of an Ethernet
service between two Ethernet ports on the same NE, set Maintenance
Domain Level to a value smaller than the value that is set in the test of
an Ethernet service between two internal NEs on the transport network.
Creating an MA Required in the case of the NEs where the two Ethernet ports involved in
l Set Maintenance Domain Name to the value of Maintenance
Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the same value for the two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transit Period to 1s.
Creating an
MEP Point
Required in the case of the NEs where the two Ethernet ports involved in
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MEP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l The MEP ID is used to identify the MEP during the CC test. Therefore,
set CC Status to Active.
Transmission System
178
Creating
Remote MEPs
in an MA
Required in the case of the NE where the Ethernet ports involved in the
OAM operation are located. Set the parameters as follows:
l To ensure that an MEP can respond to the OAM operations initiated
by the other MEPs in the same MA, you need to set the other MEPs to
be the remote MEPs of this MEP.
Perform an LB
test to test the
Ethernet service
configurations
Required.
The LB test result should show that no packet loss occurs.

4.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN
Services)
protection information, and QoS information of an IEEE 802.1d bridge-based E-LAN service
and the procedure for verifying the service configurations.
Figure 4-16 provides the procedures for configuring IEEE 802.1d-bridge-based E-LAN
services.
Figure 4-16 Configuration flow chart (IEEE 802.1d bridge-based E-LAN services)
Start
Required
Optional
End
Configuring E-LAN services
configurations
Configuring QoS
Transmission System
179

The procedures in the configuration flow chart are described as follows.
8.1.1 Setting
the General
Attributes of
Ethernet
Interfaces
l Set Encapsulation Type to Null.
l In the case of an Ethernet port that is connected to external equipment,
set Working Mode to be the same value as the external equipment
(generally, the working mode of the external equipment is auto-
negotiation). In the case of an Ethernet port within the network, set
Working Mode to Auto-Negotiation.
8.1.5
Configuring
Flow Control
For ports that carry E-LAN services, the flow control function is always
disabled.
8.1.4 Setting
the Advanced
Attributes of
Ethernet Ports
Required when you need to enable the port self-loop test and automatic
loopback shutdown functions or to enable the broadcast packet suppression
function.
Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast
Packet Suppression, and Broadcast Packet Suppression Threshold
according to the actual requirements.

Transmission System
180
Procedures for Configuring E-LAN Services
Table 4-20 Procedures for configuring E-LAN services
8.18.1 Configuring IEEE
802.1d Bridge-Based E-
LAN Services
l Set Tag Type to Tag-Transparent.
l Set Self-Learning MAC Address to Enabled according
to the planning information.
l In the UNI tab, set Port according to the planning
information and set VLANs/CVLAN to Null.
l To disable the packet forwarding between certain E-LAN
service ports, add the ports to Split Horizon Group
Member.
Managing
the MAC
address table
8.19.2
Creating a
Blacklist
Entry of
MAC
Addresses
Required when usage of E-LAN services needs to be disabled
on certain MAC address host.
Set the parameters according to the network planning
information.
8.19.1
Creating a
Static MAC
Address
Entry
Required if you need to set certain MAC address entries not
to age.
information.
8.19.3
Configuring
the Aging
Parameters
of a MAC
Address
Table
Required if the aging function needs to be disabled or if the
default aging time (five minutes) needs to be changed.
information.
8.20 Setting the Mode for
Processing an Unknown
Frame of the E-LAN
Service
Optional.

Transmission System
181
8.28.1
Modifying the
Mapping
Relationships
for the DS
Domain
8.28.2
Changing the
Ports in a DS
Domain and
Their Trusted
Packet Types
Creating a DS
Domain
Creating a Port
Policy
Creating a
Traffic Flow
8.28.3 Setting
the Port That
Uses the Port
Policy
Configuring
Port Shaping
occupies.

Transmission System
182
NEs.
Creating an
MEP Point
test.
Transmission System
183
Creating
Remote MEPs
in an MA
Perform an LB
test to test the
Ethernet service
configurations
Required.

4.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN
Services)
protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service
Figure 4-17 provides the procedures for configuring IEEE 802.1q bridge-based E-LAN services.
Figure 4-17 Configuration flow chart (IEEE 802.1q bridge-based E-LAN services)
Start
Required
Optional
End
configurations
Configuring QoS
Transmission System
184

The detailed information about the procedures in the flow chart is provided as follows.
8.1.1 Setting
the General
Attributes of
Ethernet
Interfaces
l Set Encapsulation Type to 802.1Q.
8.1.5
Configuring
Flow Control
disabled.
8.1.2 Setting
the Layer 2
Attributes of
Ethernet Ports
l If all the accessed services carry VLAN tags (tagged frames), set
TAG to Tag Aware.
l If none of the accessed services carries VLAN tags (untagged frames),
set TAG to Access, and set Default VLAN ID and VLAN Priority
l If the accessed services contain tagged frames and untagged frames,
set TAG to Hybrid, and set Default VLAN ID and VLAN Priority
8.1.4 Setting
the Advanced
Attributes of
Ethernet Ports
function.
according to the requirements.

Transmission System
185
802.1q Bridge-Based E-
LAN Services
l Set Tag Type to C-Aware.
l In the UNI tab, set the parameters according to the
planning information.
Member.
Managing
the MAC
address table
8.19.2
Creating a
Blacklist
Entry of
MAC
Addresses
information.
8.19.1
Creating a
Static MAC
Address
Entry
to age.
information.
8.19.3
Configuring
the Aging
Parameters
of a MAC
Address
Table
information.
Frame of the E-LAN
Service
Optional.

Transmission System
186
8.28.1
Modifying the
Mapping
Relationships
for the DS
Domain
8.28.2
Changing the
Ports in a DS
Domain and
Their Trusted
Packet Types
Creating a DS
Domain
Creating a Port
Policy
Creating a
Traffic Flow
8.28.3 Setting
the Port That
Uses the Port
Policy
Configuring
Port Shaping
occupies.

Transmission System
187
NEs.
Creating an
MEP Point
test.
Transmission System
188
Creating
Remote MEPs
in an MA
Perform an LB
test to test the
Ethernet service
configurations
Required.

4.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN
Services)
protection information, and QoS information of an IEEE 802.1ad bridge-based E-LAN service
Figure 4-18 provides the procedures for configuring IEEE 802.1ad bridge-based E-LAN
services.
Figure 4-18 Configuration flow chart (IEEE 802.1ad bridge-based E-LAN services)
Start
Required
Optional
End
configurations
Configuring QoS
Transmission System
189

The detailed information about the procedures in the flow chart is provided as follows.
8.1.1 Setting
the General
Attributes of
Ethernet
Interfaces
l If a UNI can access untagged frames, set Encapsulation Type to
Null. If a UNI can access tagged frames only, set Encapsulation
Type to 802.1Q.
l In the case of an NNI, set Encapsulation Type to QinQ.
8.1.5
Configuring
Flow Control
disabled.
8.1.2 Setting
the Layer 2
Attributes of
Ethernet Ports
l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set
TAG to Tag Aware (default value).
l In the case of an NNI that is connected to the external equipment, set
QinQ Type Domain according to the T-PID of the SVLAN that is
supported by the external equipment.
8.1.4 Setting
the Advanced
Attributes of
Ethernet Ports
function.
according to the requirements.

Transmission System
190
802.1ad Bridge-Based E-
LAN Services
l Set Tag Type to S-Aware.
l In the UNI and NNI tab pages, set the parameters
according to the planning information.
Member.
Managing
the MAC
address table
8.19.2
Creating a
Blacklist
Entry of
MAC
Addresses
information.
8.19.1
Creating a
Static MAC
Address
Entry
to age.
information.
8.19.3
Configuring
the Aging
Parameters
of a MAC
Address
Table
information.
Frame of the E-LAN
Service
Optional.

Transmission System
191
8.28.1
Modifying the
Mapping
Relationships
for the DS
Domain
8.28.2
Changing the
Ports in a DS
Domain and
Their Trusted
Packet Types
Creating a DS
Domain
Creating a Port
Policy
Creating a
Traffic Flow
8.28.3 Setting
the Port That
Uses the Port
Policy
Configuring
Port Shaping
occupies.

Transmission System
192
NEs.
Creating an
MEP Point
test.
Transmission System
193
Creating
Remote MEPs
in an MA
Perform an LB
test to test the
Ethernet service
configurations
Required.

4.3 Configuration Example (Point-to-Point Transparently
Transmitted E-Line Services)
This section considers a point-to-point transparently transmitted E-Line service as an example
to describe how to configure the Ethernet service according to the network planning information.
This section describes the networking information about the NEs.
As shown in Figure 4-19, NE1 is a terminal station of a backhaul network. The service
requirements are as follows:
l NE1 transparently transmits the Ethernet services from the NodeB to NE2 in point-to-point
manner.
l DSCP flags are used to identify the priorities of the Ethernet services from the NodeB.
To meet the preceding requirements, point-to-point transparently transmitted E-line services are
configured; in addition, corresponding QoS processing is configured.
Figure 4-19 Networking diagram (point-to-point transparently transmitted E-Line services)
NE2
NE1
Tranparent transmitted
E-Line service
Backhaul network
NodeB
BSC
Transmission System
194

NOTE
This topic considers the OptiX OSN 550 as an example to describe the board layout. In the case of other
products, the configuration method is the same, except for the slots. For the slot information, see the
Hardware Description of the relevant product.
The connections of Ethernet links shown in Figure 4-19 are described as follows.
Table 4-31 Connections of Ethernet links (NE1)
Link Port Description
Between NE1 and the NodeB 3-EM6T-3 Configure this port to access
services from the NodeB.
Between NE1 and NE2 3-EM6T-2 Configure this port to
transmit backhaul services
from a NodeB.

You need to plan the corresponding parameters information before configuring an Ethernet
service.
4.3.2.1 Service Planning (Ethernet Ports)
The service planning information contains the information about all the parameters required for
configuring Ethernet ports.
Table 4-32 provides the information about the Ethernet port involved in the service.
NOTE
l In this example, the GE port on the NodeB works in auto-negotiation mode. Hence, the GE port of each NE
that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in another mode,
the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the
network are planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1620 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
Normally, if the equipment is interconnected with NodeBs, the maximum frame length can also assume its
default value of 1620.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The planning information of flow control must be the same for the equipment at both ends.
Table 4-32 Ethernet port
Parameter 3-EM6T-3
3-EM6T-2
Encapsulation Type Null
Transmission System
195
Parameter 3-EM6T-3
3-EM6T-2
Working Mode Auto-Negotiation
Max Frame Length (bytes) 1620
Flow Control Disabled

4.3.2.2 Service Planning (Ethernet Services)
configuring Ethernet services.
Table 4-33 provides the detailed service planning information.
Table 4-33 Point-to-point transparently transmitted E-line service
Parameter NE1
Service ID 1
Service Name NodeBtoNE2_Eline
Direction UNI-UNI
Source Port 3-EM6T-3
Source VLANs Blank
Sink Port 3-EM6T-2
Sink VLANs Blank

4.3.2.3 Service Planning (QoS)
configuring QoS.
QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the NodeB
services be allocated according to the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the NodeB services are allocated with corresponding DSCP values according
to the service type, and the NEs allocate the PHB service classes according to the DSCP value,
as shown in Table 4-34. Each Ethernet port involved in the service uses the same DS
configuration.
Transmission System
196
Table 4-34 Service class and PHB service class
PHB Service Class DSCP Corresponding Service
Type
CS7 56 -
CS6 48 -
EF 40 Real-time voice service and
signaling service (R99
conversational and R99
streaming services)
AF4 32 -
AF3 24 Real-time OM and HSDPA
services (OM streaming and
HSPA streaming services)
AF2 16 Non-real-time R99 service
(R99 interactive and R99
background services)
AF1 8 -
BE 0 HSDPA data service (HSPA
interactive and background
services)

NOTE
l During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit
Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The required trusted packet type is not the C-VLAN priority but IP-DSCP value. Therefore, the trusted
packet type needs to be modified for service-associated Ethernet ports applied in the default DS domain.
QoS (Queue Scheduling Mode)
Generally, all Ethernet port involved in the service use the same queue scheduling mode.
Table 4-35 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
Table 4-35 Queue scheduling mode
PHB Service Class Queue Scheduling Mode
CS7 SP
CS6 SP
Transmission System
197
EF SP
AF4 WRR (weight = 5)
BE SP

QoS (CAR or Shaping for a Specified Service Flow)
Normally, flow control is already performed on 2G/3G base stations and BSCs/RNCs and
therefore CAR or shaping processing does not need to be performed again on the backhaul
network.
QoS (Port Shaping)
If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of
the aggregation services, you can perform port shaping at the edge node to limit the Ethernet
service traffic that travels to the aggregation node, preventing congestion at the aggregation
node.
In this example, you do not need to perform port shaping.
4.3.3 Configuration Process
This section describes the process for data configuration.
4.3.3.1 Configuration Process (Ethernet Ports)
This section describes the process for configuring Ethernet ports.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The Ethernet board must be added on the NE Panel.
U2000
Procedure
Step 1 8.1.1 Setting the General Attributes of Ethernet Interfaces.
The values for the relevant parameters are provided as follows.
Transmission System
198
Parameter Value
3-EM6T-3
3-EM6T-2
Enable Port Enabled
Port Mode Layer 2
Max Frame Length(bytes) 1620

----End
4.3.3.2 Configuration Process (Service Information)
This section describes the process for configuring service information.
Prerequisites
l The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line service.
U2000
Procedure
Step 1 8.17.3 Configuring UNI-UNI E-Line Services.
The values for the relevant parameters are provided as follows.
Parameter Value
Service ID 1
Service Name NodeBtoNE2_Tline
Direction UNI-UNI
MTU (bytes) -
Service Tag Role -
Source Port 3-EM6T-3
Transmission System
199
Parameter Value
Source VLANs Blank
Sink Port 3-EM6T-2
Sink VLANs Blank

----End
4.3.3.3 Configuration Process (QoS)
This section describes the procedures for configuring QoS.
Procedure
Step 1 See 8.28.1 Modifying the Mapping Relationships for the DS Domain and change the mapping
relationships for the DS domain.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 2
Mapping Relation Name Default Map 2

The values for the relevant parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
CVLAN SVLAN IP DSCP MPLS EXP PHB
0 0 Default value Default value BE
1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7

The values for the relevant parameters that need to be set in the Egress Mapping Relation tab
Transmission System
200
PHB CVLAN SVLAN IP DSCP MPLS EXP
BE 0 0 Default value Default value
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7

NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
Step 2 See 8.28.2 Changing the Ports in a DS Domain and Their Trusted Packet Types and change
the ports that are applied to the DS domain and their trusted packet types.
Selected Port Packet Type
3-EM6T-1
3-EM6T-2
ip-dscp

NOTE
The required trusted packet type is not the C-VLAN priority but IP-DSCP value. Therefore, the trusted packet
type needs to be modified for service-associated Ethernet ports applied in the default DS domain.
Step 3 See Creating a Port Policy and create the port policy.
The values for the related parameters are provided as follows.
Parameter Value
Policy ID 1
Policy Name Port_Comm
Grooming Police After Reloading SP (CS7, CS6, and EF)
WRR (AF4-AF1)
SP (BE)
Transmission System
201
Parameter Value
Policy Weight(%) 5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Bandwidth Limit Disabled (for all PHB service classes)

Step 4 See 8.28.3 Setting the Port That Uses the Port Policy and set the ports that use the port policy.
The values for the related parameters are provided as follows.
Parameter Value
Port_Comm
Port 3-EM6T-3
3-EM6T-2

----End
4.4 Configuration Example (VLAN-Based E-Line Service)
This section considers a VLAN-based E-line service as an example to describe how to configure
The section describes the networking information about the NEs.
Configure Ethernet services according to the following requirements:
l NodeB11, NodeB12, and NodeB15 provide FE ports whose port rate is 100 Mbit/s.
l Services transmitted by each NodeB carry VLAN IDs, and VLAN IDs on the entire network
are planned in a unified manner.
l VLAN priorities are configured on each NodeB according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for service
transmission on each NE; in addition, corresponding QoS processing is configured.
Transmission System
202
Figure 4-20 Networking diagram (VLAN-based E-Line services)
NE11
NE12 NE13
NE15
NE14
NE16
FE
FE
FE
GE
NodeB15
VLAN 120
NodeB11
VLAN 100
NodeB12
VLAN 110
Packet network

NOTE
Table 4-36 Connections of Ethernet links
NE Link Port Description
NE11 Between NE12 and
NE11
3-EM6T-1 Configure this port to
transmit Native
Ethernet services.
NE13
transmit backhaul
services from
NodeBs.
Between NE12 and
NE11
transmit Native
Ethernet services.
Between NE12 and
NodeB11
access services from
NodeB11.
NE14
transmit Native
Ethernet services.
Between NE13 and
NE15
transmit Native
Ethernet services.
Transmission System
203
Between NE13 and
NE12
transmit backhaul
services from
NodeBs.
NE13
transmit Native
Ethernet services.
Between NE14 and
NodeB12
NodeB12.
NE16
transmit Native
Ethernet services.
Between NE15 and
NE13
transmit Native
Ethernet services.
NE15
transmit Ethernet
services.
Between NE16 and
NodeB15
3-EM6T-3 Configure these
ports to access
services from
NodeB15.

You need to plan the corresponding parameter information before configuring an Ethernet
service.
Transmission System
204
NOTE
l In this example, the FE ports on all the NodeBs work in auto-negotiation mode. Therefore, the FE/GE port
of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in
another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports
inside the network are planned as auto-negotiation.
l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.
Table 4-37 Information about Ethernet ports
Parameter Value
NE NE11 NE12 NE13 NE14
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
Encapsulatio
n type
802.1Q
Port working
mode
Auto-negotiation
Max Frame
Length
(bytes)
1620
Flow control Disabled
Tag attribute Tag Aware

Table 4-38 Information about VLAN-based E-Line services
Param
eter
Value
NE NE12 NE13 NE14 NE15 NE16
Transmission System
205
Param
eter
Value
NE13
to
NE11
NE13
to
NE11
NodeB
11 to
NE11
NE14
to
NE12
NE15
to
NE12
NodeB
12 to
NE13
NE16
to
NE13
NodeB
15 to
NE15
Service
ID
1 2 3 1 2 1 1 1
Service
name
NE13to
NE11_
Vline
NE13to
NE11_
Vline
NodeB
11toNE
11_Vli
ne
NE14to
NE12_
Vline
NE15to
NE12_
Vline
NodeB
12toNE
13_Vli
ne
NE16to
NE13_
Vline
NodeB
15toNE
15_Vli
ne
Service
directio
n
UNI-UNI
BPDU Not transparently transmitted
Source
port
3-
EM6T-
1
3-
EM6T-
1
3-
EM6T-
3
3-
EM6T-
1
3-
EM6T-
2
3-
EM6T-
3
3-
EM6T-
1
3-
EM6T-
3
Source
VLANs
110 120 100 110 120 110 120 120
Sink
port
3-
EM6T-
2
3-
EM6T-
2
3-
EM6T-
2
4-
EM6T-
1
4-
EM6T-
1
3-
EM6T-
1
3-
EM6T-
2
3-
EM6T-
1
Sink
VLANs
110 120 100 110 120 110 120 120

configuring QoS.
QoS (Diffserv)
services be allocated by the service type. Then, the transmission network creates the
In this example, the NodeB services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 4-39. Each Ethernet port involved in the service uses the same DS
configuration.
Transmission System
206
PHB Service Class VLAN Priority Corresponding Service
Type
CS7 7 -
CS6 6 -
streaming services)
AF4 4 -
AF1 1 -
services)

NOTE
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore does not need to be modified.
in this example.
CS7 SP
CS6 SP
Transmission System
207
EF SP
BE SP

network.
QoS (Port Shaping)
node.
This section describes how to configure service parameters in end-to-end mode.
Procedure
Step 1 See 8.1.1 Setting the General Attributes of Ethernet Interfaces and set the basic attributes
of Ethernet ports.
Parameter Value
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-1
Transmission System
208
Parameter Value
Enable Port Enabled
Encapsulatio
n Type
802.1Q
Working
Mode
Auto-Negotiation
Max Frame
Length
(bytes)
1620

Step 2 See 8.1.2 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of
Ethernet ports.
Parameter Value
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
TAG Tag Aware

----End
Procedure
Step 1 See 8.17.8 Creating E-Line Services over Native Ethernet in End-to-End Mode to configure
Ethernet services between NE11 and NodeB11.
Table 4-41 Basic attributes of Ethernet services between NE11 and NodeB11
Parameter Value
Service Name NodeB11toNE11_Vline
BPDU Private Service No
Customer Empty
Remarks Empty

Transmission System
209
Table 4-42 Source and sink parameters of Ethernet services between NE11 and NodeB11
Parameter Value
NE12 NE11
Location Source Sink
Node NE12 NE11
Interface 3-EM6T-3 3-EM6T-3
C-VLAN 100 100
S-VLAN Empty Empty

Table 4-43 Explicit node parameters of Ethernet services between NE11 and NodeB11
Parameter Value
NE12 NE11
NE NE12 NE11
In Interface 3-EM6T-3 3-EM6T-1
In C-VLAN 100 100
In S-VLAN Empty Empty
Out Interface 3-EM6T-2 3-EM6T-3
Out C-VLAN 100 100
Out S-VLAN Empty Empty
MTU (bytes) - -
Service Tag User User

Step 2 Repeat Step 1 to configure Ethernet services between NE11 and NodeB12.
Parameter Value
Customer Empty
Remarks Empty

Transmission System
210
Parameter Value
NE14 NE11
Node NE14 NE11
C-VLAN 110 110
S-VLAN Empty Empty

Parameter Value
NE14 NE13 NE12 NE11
In Interface 3-EM6T-3 3-EM6T-1 3-EM6T-1 3-EM6T-1
In C-VLAN 110 110 110 110
In S-VLAN Empty Empty Empty Empty
Out Interface 3-EM6T-1 4-EM6T-1 3-EM6T-2 3-EM6T-3
Out C-VLAN 110 110 110 110
Out S-VLAN Empty Empty Empty Empty
MTU (bytes) - - - -
Service Tag User User User User

Step 3 Repeat Step 1 to configure Ethernet services between NE11 and NodeB15.
Parameter Value
Customer Empty
Remarks Empty

Transmission System
211
Parameter Value
NE16 NE11
Node NE16 NE11
C-VLAN 120 120
S-VLAN Empty Empty

Parameter Value
NE16 NE15 NE13 NE12 NE11
In Interface 3-EM6T-3 3-EM6T-1 3-EM6T-2 3-EM6T-1 3-EM6T-1
In C-VLAN 120 120 120 120 120
In S-VLAN Empty Empty Empty Empty Empty
Out Interface 3-EM6T-1 3-EM6T-2 4-EM6T-1 3-EM6T-2 3-EM6T-3
Out C-
VLAN
120 120 120 110 120
Out S-
VLAN
Empty Empty Empty Empty Empty
MTU (bytes) - - - - -
Service Tag User User User User User

----End
Procedure
Step 1 See 8.28.1 Modifying the Mapping Relationships for the DS Domain and modify the mapping
Transmission System
212
NOTE
The actual mapping relationships for the default DS domain comply with the network planning information.
Therefore, you can skip this step.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value

The values for the related parameters that need to be set in the Ingress Mapping Relation tab
0 Default value Default value Default value BE
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7

The values for the related parameters that need to be set in the Egress Mapping Relation tab
BE 0 Default value Default value Default value
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
Transmission System
213
CS7 7

Step 2 8.28.2 Changing the Ports in a DS Domain and Their Trusted Packet Types and change the
ports that are applied to the DS domain and their trusted packet types.
NOTE
The actual ports that are applied to the default DS domain and their trusted packet types comply with the network
planning information. Therefore, you can skip this step.
Parameter Value
NE NE12 NE13 NE14
NE16
NE15
Selected Port 3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2
Packet Type CVLAN

l The values for the related parameters of NE12 to NE16 are provided as follows.
Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

Parameter Port_Comm (Policy ID=1)
NE NE12 NE13 NE14
NE16
NE15
Transmission System
214
Port 3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2

----End
4.4.4 Per-NE Configuration Process
This section describes the process for data configuration on a per-NE basis.
Procedure
of Ethernet ports.
Parameter Value
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-1
Enable Port Enabled
Encapsulatio
n Type
802.1Q
Working
Mode
Auto-Negotiation
Max Frame
Length
(bytes)
1620

Ethernet ports.
Parameter Value
NE16
NE15
Transmission System
215
Parameter Value
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
TAG Tag Aware

----End
Procedure
Step 1 See 8.17.3 Configuring UNI-UNI E-Line Services and configure the E-Line services.
Param
eter
Value
NE13
to
NE11
NE13
to
NE11
NodeB
11 to
NE11
NE14
to
NE12
NE15
to
NE12
NodeB
12 to
NE13
NE16
to
NE13
NodeB
15 to
NE15
Service
ID
1 2 3 1 2 1 1 1
Service
Name
NE13to
NE11_
Vline
NE13to
NE11_
Vline
NodeB
11toNE
11_Vli
ne
NE14to
NE12_
Vline
NE15to
NE12_
Vline
NodeB
12toNE
13_Vli
ne
NE16to
NE13_
Vline
NodeB
15toNE
15_Vli
ne
Directi
on
UNI-UNI
BPDU Not transparently transmitted
MTU
(bytes)
-
Service
Tag
Role
-
Source
Port
3-
EM6T-
1
3-
EM6T-
1
3-
EM6T-
3
3-
EM6T-
1
3-
EM6T-
2
3-
EM6T-
3
3-
EM6T-
1
3-
EM6T-
3
Source
VLANs
110 120 100 110 120 110 120 120
Transmission System
216
Param
eter
Value
Sink
Port
3-
EM6T-
2
3-
EM6T-
2
3-
EM6T-
2
4-
EM6T-
1
4-
EM6T-
1
3-
EM6T-
1
3-
EM6T-
2
3-
EM6T-
1
Sink
VLANs
110 120 100 110 120 110 120 120

----End
Procedure
NOTE
follows.
Parameter Value

1 AF11
2 AF21
3 AF31
4 AF41
5 EF
Transmission System
217
6 CS6
7 CS7

AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7

NOTE
Parameter Value
NE NE12 NE13 NE14
NE16
NE15
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2
Packet Type CVLAN

Transmission System
218
Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

NE NE12 NE13 NE14
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2

----End
4.5 Configuration Example (QinQ-Based E-Line Service)
This section considers a QinQ-based E-line service as an example to describe how to configure
l NodeB11 to NodeB15 provide FE ports whose port rate is 100 Mbit/s.
l The VLAN ID used by the services on a NodeB is allocated by the RNC that controls the
NodeB. Therefore, the VLAN IDs of services on NodeBs that are controlled by different
RNCs may be the same. To solve this problem, an RNC allocates an S-VLAN ID for each
NodeB, and the S-VLAN IDs on the entire network are planned in a unified manner.
Transmission System
219
To meet the preceding requirements, QinQ-based E-Line services are configured for service
transmission on each NE; in addition, corresponding QoS processing is configured.
Figure 4-21 Networking diagram (QinQ-based E-Line services)
NE11
NE12 NE13
NE15
NE14
NE16
FE
FE
FE
GE
NodeB15
SVLAN 202
NodeB11
SVLAN 200
NodeB12
SVLAN 201
GE
RNC

NOTE
the RNC
transmit backhaul
services from
NodeBs.
Between NE11 and
NE12
transmit Native
Ethernet services.
NE13
transmit backhaul
services from
NodeBs.
Between NE12 and
NE11
transmit Native
Ethernet services.
Between NE12 and
NodeB11
NodeB11.
Transmission System
220
NE14
transmit Native
Ethernet services.
Between NE13 and
NE15
transmit Native
Ethernet services.
Between NE13 and
NE12
transmit backhaul
services from
NodeBs.
NE13
transmit Native
Ethernet services.
Between NE14 and
NodeB12
NodeB12.
NE16
transmit Native
Ethernet services.
Between NE15 and
NE13
transmit Native
Ethernet services.
NE15
transmit Ethernet
services.
Between NE16 and
NodeB15
NodeB15.

service.
Transmission System
221
NOTE
l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
l In this example, all the NNI ports are connected to Huawei equipment. Therefore, the QinQ type domain of
the NNI ports assumes the default value of 0x88a8.
Table 4-51 Information about Ethernet ports
Para
meter
Value
NE NE11 NE12 NE13 NE14 NE15 NE16
Port 3-
EM6T
-2
3-
EM6T
-1
3-
EM6T
-1
3-
EM6T
-2
3-
EM6T
-3
3-
EM6T
-1
3-
EM6T
-2
4-
EM6T
-1
3-
EM6T
-1
3-
EM6T
-3
3-
EM6T
-1
3-
EM6T
-2
3-
EM6T
-1
3-
EM6T
-3
Encap
sulatio
n type
QinQ QinQ 802.1
Q
QinQ QinQ 802.1
Q
QinQ QinQ 802.1
Q
Port
worki
ng
mode
Auto-negotiation
Max
Frame
Lengt
h
(bytes
)
1620
Flow
contro
l
Disabled
Tag
attribu
te
Tag Aware
Transmission System
222
Para
meter
Value
QinQ
type
domai
n
0x88a
8
0x88a
8
- 0x88a
8
0x88a
8
- 0x88a
8
0x88a
8
-

Para
met
er
Value
NE NE11 NE12 NE1
3
NE1
4
NE1
5
NE1
6
Nod
eB12
to
RNC
Nod
eB11
to
RNC
Nod
eB15
to
RNC
Nod
eB11
to
NE1
1
Nod
eB12
to
NE1
1
Nod
eB15
to
NE1
1
Nod
eB12
to
NE1
2
Nod
eB15
to
NE1
2
Nod
eB12
to
NE1
3
Nod
eB15
to
NE1
3
Nod
eB15
to
NE1
5
Servi
ce ID
1 2 3 1 2 3 1 2 1 1 1
Servi
ce
nam
e
Nod
eB12
toR
NC_
Qlin
e
Nod
eB11
toR
NC_
Qlin
e
Nod
eB15
toR
NC2
_Qli
ne
Nod
eB11
toNE
11_
Qlin
e
Nod
eB12
toNE
11_
Qlin
e
Nod
eB15
toNE
11_
Qlin
e
Nod
eB12
toNE
12_
Qlin
e
Nod
eB15
toNE
12_
Qlin
e
Nod
eB12
toNE
13_
Qlin
e
Nod
eB15
toNE
13_
Qlin
e
Nod
eB15
toNE
15_
Qlin
e
Servi
ce
direc
tion
UNI-NNI
BPD
U
Not transparently transmitted
Sour
ce
port
3-
EM6
T-2
3-
EM6
T-2
3-
EM6
T-2
3-
EM6
T-3
- - - - 3-
EM6
T-1
- 3-
EM6
T-3
Transmission System
223
Para
met
er
Value
Sour
ce
VLA
Ns
- - - - - - - - - - -
Qin
Q
link
(sour
ce)
- - - - ID: 2
Port:
3-
EM6
T-1
SVL
AN:
201
ID: 4
Port:
3-
EM6
T-1
SVL
AN:
202
ID: 1
Port:
3-
EM6
T-1
SVL
AN:
201
ID: 3
Port:
3-
EM6
T-2
SVL
AN:
202
- ID: 1
Port:
3-
EM6
T-1
SVL
AN:
202
-
Qin
Q
link
(sink
)
ID: 1
Port:
3-
EM6
T-1
SVL
AN:
201
ID: 2
Port:
3-
EM6
T-1
SVL
AN:
200
ID: 3
Port:
3-
EM6
T-1
SVL
AN:
202
ID: 1
Port:
3-
EM6
T-2
SVL
AN:
200
ID: 3
Port:
3-
EM6
T-2
SVL
AN:
201
ID: 5
Port:
3-
EM6
T-2
SVL
AN:
202
ID: 2
Port:
4-
EM6
T-1
SVL
AN:
201
ID: 4
Port:
4-
EM6
T-1
SVL
AN:
202
ID: 1
Port:
3-
EM6
T-1
SVL
AN:
201
ID: 2
Port:
3-
EM6
T-2
SVL
AN:
202
ID: 1
Port:
3-
EM6
T-1
SVL
AN:
202

configuring QoS.
QoS (Diffserv)
configuration.
Transmission System
224
Type
CS7 7 -
CS6 6 -
streaming services)
AF4 4 -
AF1 1 -
services)

NOTE
and therefore needs to be modified as required.
in this example.
CS7 SP
CS6 SP
Transmission System
225
EF SP
BE SP

network.
QoS (Port Shaping)
node.
Procedure
of Ethernet ports.
Param
eter
Value
NE16
NE15
Transmission System
226
Param
eter
Value
Port 3-
EM6T-2
3-
EM6T-1
3-
EM6T-1
3-
EM6T-2
3-
EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-
EM6T-
1
3-
EM6T-
3
3-
EM6T-
1
3-
EM6T-
2
Enable
Port
Enabled
Encaps
ulation
Type
QinQ QinQ 802.1Q QinQ QinQ 802.1Q QinQ
Workin
g Mode
Auto-Negotiation
Max
Frame
Length
(bytes)
1620

Step 2 See 8.1.2 Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of
Ethernet ports
Parameter Value
NE16
NE15
Port 3-EM6T-2
3-EM6T-1
3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2
TAG Tag Aware

----End
Procedure
Step 1 See 8.17.8 Creating E-Line Services over Native Ethernet in End-to-End Mode to configure
Ethernet services between the RNC and NodeB11.
Transmission System
227
Table 4-54 Basic attributes of Ethernet services between the RNC and NodeB11
Parameter Value
Service Name NodeB11toRNC_Vline
Customer Empty
Remarks Empty

Table 4-55 Source and sink parameters of Ethernet services between the RNC and NodeB11
Parameter Value
NE12 NE11
Node NE12 NE11
C-VLAN Empty Empty
S-VLAN 200 200

Table 4-56 Explicit node parameters of Ethernet services between the RNC and NodeB11
Parameter Value
NE12 NE11
NE NE12 NE11
In Interface 3-EM6T-3 3-EM6T-2
In C-VLAN Empty Empty
In S-VLAN 200 200
Out Interface 3-EM6T-2 3-EM6T-1
Out C-VLAN Empty Empty
Out S-VLAN 200 200
MTU (bytes) - -
Service Tag User User

Step 2 Repeat Step 1 to configure Ethernet services between the RNC and NodeB12.
Transmission System
228
Parameter Value
Customer Empty
Remarks Empty

Parameter Value
NE14 NE11
Node NE14 NE11
C-VLAN Empty Empty
S-VLAN 201 201

Parameter Value
NE14 NE13 NE12 NE11
In Interface 3-EM6T-3 3-EM6T-1 3-EM6T-1 3-EM6T-2
In C-VLAN Empty Empty Empty Empty
In S-VLAN 201 201 201 201
Out Interface 3-EM6T-1 4-EM6T-1 3-EM6T-2 3-EM6T-1
Out C-VLAN Empty Empty Empty Empty
Out S-VLAN 201 201 201 201
MTU (bytes) - - - -
Service Tag User User User User

Step 3 Repeat Step 1 to configure Ethernet services between the RNC and NodeB15.
Transmission System
229
Parameter Value
Customer Empty
Remarks Empty

Parameter Value
NE16 NE11
Node NE16 NE11
C-VLAN Empty Empty
S-VLAN 202 202

Parameter Value
NE16 NE15 NE13 NE12 NE11
In Interface 3-EM6T-3 3-EM6T-1 3-EM6T-2 3-EM6T-1 3-EM6T-2
In C-VLAN Empty Empty Empty Empty Empty
In S-VLAN 202 202 202 202 202
Out Interface 3-EM6T-1 3-EM6T-2 4-EM6T-1 3-EM6T-2 3-EM6T-1
Out C-
VLAN
Empty Empty Empty Empty Empty
Out S-
VLAN
202 202 202 202 202
MTU (bytes) - - - - -
Service Tag User User User User User
Transmission System
230

----End
Procedure
The values for the required parameters that are set in the main interface are as follows.
Parameter Value

1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7

AF11 1 1
Transmission System
231
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7

NOTE
ports that are applied to the DS domain and their trusted packet type.
NE Selected Port Packet Type
NE11
NE15
3-EM6T-2 SVLAN
3-EM6T-1 SVLAN
NE12 3-EM6T-3 CVLAN
3-EM6T-1 SVLAN
3-EM6T-2 SVLAN
NE13 3-EM6T-1 SVLAN
3-EM6T-2 SVLAN
4-EM6T-1 SVLAN
NE14
NE16
3-EM6T-3 CVLAN
3-EM6T-1 SVLAN

The values for the related parameters of NE11 to NE16 are provided as follows.
Parameter Value
Policy ID 1
Transmission System
232
Parameter Value
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

NE NE11
NE15
NE12 NE13 NE14
NE16
Port 3-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-3

----End
4.5.3.4 Configuration Process (Verifying Ethernet Service Configurations)
This section describes the process for verifying Ethernet service configurations.
Procedure
Step 1 See Creating an MD and configure the MD for NE11, NE12, NE14, and NE16.
The values for the required parameters are provided as follows.
Parameter Value
NE11 NE12 NE14 NE16
Maintenance
Domain Name
EdgeNE EdgeNE EdgeNE EdgeNE
Maintenance
Domain Level
4 4 4 4

Step 2 See Creating an MA and configure the MA for NE11, NE12, NE14, and NE16.
Transmission System
233
Paramete
r
Value
Maintenan
ce Domain
Name
EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE
Maintenan
ce
Associatio
n Name
11_Qline 12_Qline 15_Qline 11_Qline 12_Qline 15_Qline
Relevant
Service
1-
NodeB11_
Qline
2-
NodeB12_
Qline
5-
NodeB15_
Qline
1-
NodeB11_
Qline
1-
NodeB12_
Qline
1-
NodeB15_
Qline
CC Test
Transmit
Period
1s 1s 1s 1s 1s 1s

Step 3 See Creating an MEP Point and create the MEPs.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Board 3-EM6T 3-EM6T 3-EM6T 3-EM6T 3-EM6T 3-EM6T
Port 3-EM6T-1 3-EM6T-1 3-EM6T-1 3-EM6T-3 3-EM6T-3 3-EM6T-3
VLAN 100 110 140 - - -
MEP ID 1 2 3 4 5 6
Direction Ingress Ingress Ingress Ingress Ingress Ingress
CC Status Active Active Active Active Active Active

Step 4 See Creating Remote MEPs in an MA and create the remote MEPs of the MA for NE11, NE12,
NE14, and NE16.
Transmission System
234
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Remote
Maintenan
ce Point ID
(e.g:1,3-6)
4 5 6 1 2 3

Step 5 On NE1, perform LB tests to test the Ethernet service configurations.
l Perform the LB test by considering the MEP whose MEP ID is 4 as the source MEP and the
MEP whose MEP ID is 1 as the sink MEP.
No packet loss occurs.
----End
Procedure
of Ethernet ports.
Param
eter
Value
NE16
NE15
Transmission System
235
Param
eter
Value
Port 3-
EM6T-2
3-
EM6T-1
3-
EM6T-1
3-
EM6T-2
3-
EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-
EM6T-
1
3-
EM6T-
3
3-
EM6T-
1
3-
EM6T-
2
Enable
Port
Enabled
Encaps
ulation
Type
QinQ QinQ 802.1Q QinQ QinQ 802.1Q QinQ
Workin
g Mode
Auto-Negotiation
Max
Frame
Length
(bytes)
1620

Step 2 See 8.1.2 Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of
Ethernet ports
Parameter Value
NE16
NE15
Port 3-EM6T-2
3-EM6T-1
3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2
TAG Tag Aware

----End
Procedure
Step 1 See 8.17.1 Creating a QinQ Link and configure a QinQ link.
Transmission System
236
NE QinQ Link ID Board Port S-Vlan ID
NE11 1 3-EM6T 1 201
2 3-EM6T 1 200
3 3-EM6T 1 202
NE12 1 3-EM6T 2 200
2 3-EM6T 1 201
3 3-EM6T 2 201
4 3-EM6T 1 202
5 3-EM6T 2 202
NE13 1 3-EM6T 1 201
2 4-EM6T 1 201
3 3-EM6T 2 202
4 4-EM6T 1 202
NE14 1 3-EM6T 1 201
NE15 1 3-EM6T 1 202
2 3-EM6T 2 202
NE16 1 3-EM6T 1 202

Step 2 See 8.17.4 Configuring NNI-NNI E-Line Services and configure NNI-NNI E-Line services.
The method for configuring UNI-NNI E-Line services is the same as that for configuring NNI-
NNI E-Line services.
NOTE
Set Bearer Type to QinQ Link.
Para
met
er
Value
4
NE1
5
NE1
6
Nod
eB12
to
the
RNC
Nod
eB11
to
the
RNC
Nod
eB15
to
the
RNC
Nod
eB11
to
NE1
1
Nod
eB12
to
NE1
1
Nod
eB15
to
NE1
1
Nod
eB12
to
NE1
2
Nod
eB15
to
NE1
2
Nod
eB12
to
NE1
3
Nod
eB1
5 to
NE1
3
Nod
eB15
to
NE1
5
Servi
ce ID
1 2 3 1 2 3 1 2 1 1 1
Transmission System
237
Para
met
er
Value
Servi
ce
Nam
e
Nod
eB12
toR
NC_
Qlin
e
Nod
eB11
toR
NC_
Qlin
e
Nod
eB15
toR
NC_
Qlin
e
Nod
eB11
toNE
11_
Qlin
e
Nod
eB12
toNE
11_
Qlin
e
Nod
eB15
toNE
11_
Qlin
e
Nod
eB12
toNE
12_
Qlin
e
Nod
eB15
toNE
12_
Qlin
e
Nod
eB12
toNE
13_
Qlin
e
Nod
eB1
5toN
E13
_Qli
ne
Nod
eB15
toNE
15_
Qlin
e
Dire
ction
UNI-
NNI
UNI-
NNI
UNI-
NNI
UNI-
NNI
NNI-
NNI
NNI-
NNI
NNI-
NNI
NNI-
NNI
UNI-
NNI
NNI
-
NNI
UNI-
NNI
BPD
U
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Not
Tran
spar
ently
Tran
smitt
ed
Not
Tran
spare
ntly
Tran
smitt
ed
Sour
ce
Port
3-
EM6
T-2
3-
EM6
T-2
3-
EM6
T-2
3-
EM6
T-3
- - - - 3-
EM6
T-3
- 3-
EM6
T-3
Sour
ce
VLA
Ns
- - - - - - - - - - -
Qin
Q
Link
ID
1 2 3 1 - - - - 1 - 1
Qin
Q
Link
ID 1
- - - - 2 4 1 3 - 1 -
Qin
Q
Link
ID 2
- - - - 3 5 2 4 - 2 -
Bear
er
Type
1
- - - - Qin
Q
Link
Qin
Q
Link
Qin
Q
Link
Qin
Q
Link
- Qin
Q
Link
-
Transmission System
238
Para
met
er
Value
Bear
er
Type
2
- - - - Qin
Q
Link
Qin
Q
Link
Qin
Q
Link
Qin
Q
Link
- Qin
Q
Link
-
Bear
er
Type
Qin
Q
Link
Qin
Q
Link
Qin
Q
Link
Qin
Q
Link
- - - - Qin
Q
Link
- Qin
Q
Link
MT
U
(byte
s)
- - - - - - - - - - -
Servi
ce
Tag
Role
- - - - - - - - - - -

----End
Procedure
The values for the required parameters that are set in the main interface are as follows.
Parameter Value

1 1 AF11
Transmission System
239
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7

AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7

NOTE
ports that are applied to the DS domain and their trusted packet type.
NE11
NE15
3-EM6T-2 SVLAN
3-EM6T-1 SVLAN
NE12 3-EM6T-3 CVLAN
Transmission System
240
3-EM6T-1 SVLAN
3-EM6T-2 SVLAN
NE13 3-EM6T-1 SVLAN
3-EM6T-2 SVLAN
4-EM6T-1 SVLAN
NE14
NE16
3-EM6T-3 CVLAN
3-EM6T-1 SVLAN

The values for the related parameters of NE11 to NE16 are provided as follows.
Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

NE NE11
NE15
NE12 NE13 NE14
NE16
Port 3-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-3

----End
Transmission System
241
Procedure
Step 1 See Creating an MD and configure the MD for NE11, NE12, NE14, and NE16.
Parameter Value
NE11 NE12 NE14 NE16
Maintenance
Domain Name
Maintenance
Domain Level
4 4 4 4

Step 2 See Creating an MA and configure the MA for NE11, NE12, NE14, and NE16.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Relevant
Service
1-
NodeB11_
Qline
2-
NodeB12_
Qline
5-
NodeB15_
Qline
1-
NodeB11_
Qline
1-
NodeB12_
Qline
1-
NodeB15_
Qline
CC Test
Transmit
Period
1s 1s 1s 1s 1s 1s

Paramete
r
Value
Transmission System
242
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
VLAN 100 110 140 - - -
MEP ID 1 2 3 4 5 6

Step 4 See Creating Remote MEPs in an MA and create the remote MEPs of the MA for NE11, NE12,
NE14, and NE16.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Remote
Maintenan
ce Point ID
(e.g:1,3-6)
4 5 6 1 2 3

Transmission System
243
----End
4.6 Configuration Example (802.1d Bridge-Based E-LAN
Service)
This section considers an 802.1d bridge-based E-LAN service as an example to describe how
l The NodeB services are transparently transmitted.
l The functions of detecting looped services and suppressing broadcast packets need to be
provided on the network.
To meet the preceding requirements, IEEE 802.1d bridge-based E-LAN services are configured
to implement transmission of the NodeB services; in addition, the functions of detecting looped
services and suppressing broadcast packets and QoS processing are configured. See Figure
4-22.
Transmission System
244
Figure 4-22 Networking diagram (IEEE 802.1d bridge-based E-LAN services)
NodeB21
NE21
NE23
NE22 NE24
NodeB23
NodeB24
FE
FE
FE
802.1d bridge
802.1d bridge
802.1d bridge
Packet network

NOTE
the PSN
drop the Native E-
LAN services.
Between NE21 and
NE22
transmit Ethernet
services.
Between NE21 and
NE24
transmit Ethernet
services.
NE23
transmit Ethernet
services.
Transmission System
245
Between NE22 and
NodeB21
NodeB21.
Between NE22 and
NE21
transmit Ethernet
services.
NE24
transmit Ethernet
services.
Between NE23 and
NodeB23
NodeB23.
Between NE23 and
NE22
transmit Ethernet
services.
NE21
transmit Ethernet
services.
Between NE24 and
NodeB24
NodeB24.
Between NE24 and
NE23
transmit Ethernet
services.

service.
Transmission System
246
NOTE
l For ports that carry E-LAN services, the flow control function is always disabled.
l In this example, no loopback port shutdown function is enabled.
Parameter Value
NE NE21 NE22
NE23
NE24
Port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
Encapsulation type Null
Port working mode Auto-negotiation
Max Frame Length (bytes) 1620
Loopback check Enabled
Loopback port shutdown Disabled
Broadcast Packet
Suppression
Enabled
Broadcast Packet
Suppression Threshold
30

Table 4-64 provides the planning information of IEEE 802.1a bridge-based E-LAN services.
Transmission System
247
Table 4-64 Information about IEEE 802.1d bridge-based E-LAN services
Parameter NE21 NE22
NE23
NE24
Service ID 1 1
Service name Dlan Dlan
TAG type Tag-Transparent Tag-Transparent
Self-learning MAC address Enabled Enabled
MAC address learning mode SVL SVL
Mounted UNI port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3

configuring QoS.
QoS (Diffserv)
configuration.
Type
CS7 7 -
CS6 6 -
streaming services)
AF4 4 -
Transmission System
248
Type
AF1 1 -
services)

NOTE
in this example.
CS7 SP
CS6 SP
EF SP
BE SP

Transmission System
249
network.
QoS (Port Shaping)
node.
Procedure
of Ethernet ports.
Parameter Value
NE NE21 NE22
NE24
NE23
Port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
Enable Port Enabled
Max Frame Length
(bytes)
1620

Step 2 See 8.1.4 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes
of Ethernet ports.
Transmission System
250
Parameter Value
NE NE21 NE22
NE24
NE23
Port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
Loopback Check Enabled
Broadcast Packet
Suppression
Enabled
Broadcast Packet
Suppression
Threshold
30

----End
Procedure
Step 1 Configure E-LAN services over Native Ethernet in end-to-end mode.
1. Choose Service > Native Ethernet Service > Create E-LAN Service from the Main
Menu.
2. Set basic attributes for the E-LAN service.
Set Service Name to Dlan.
3. Configure bridge-mounted ports for the E-LAN service.
a. Double-click NE21 in the Physical Topology tab page.
b. Set Tag Type to Tag-Transparent.
c. Select 3-EM6T-1, 3-EM6T-2, and 4-EM6T-1 from the Available Interface list, and
click .
Transmission System
251
NOTE
If Port Mode of a port is Layer 3, the port is not displayed under Available Interface. To
display the port, right-click the NE in the Physical Topology tab page, choose NE Explorer
from the shortcut menu, and set Port Mode to Layer 2 by referring to 8.1.1 Setting the General
Attributes of Ethernet Interfaces.
d. OK
4. Repeat Step 1.3 to configure bridge-mounted ports on NE22, NE23, and NE24 according
to 4.6.2.2 Service Planning (Ethernet Services).
5. Set attributes for the bridge-mounted ports.
a. Click .
b. Click the Interface Information tab.
c. Set basic attributes for the bridge-mounted ports.
NE Port Enable Port Working Mode Max Frame
Length
(bytes)
NE21 3-EM6T-1 Enabled Auto-Negotiation 1620
3-EM6T-2 Enabled Auto-Negotiation 1620

6. Set advanced attributes for the bridge-mounted ports.
a. Click .
c. Select the bridge-mounted ports.
d. Click .
e. Click the Advanced Attributes tab and set the advanced attributes for the ports. For
details, see 8.1.4 Setting the Advanced Attributes of Ethernet Ports.
Transmission System
252
f. Click Apply.
NE Port Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
NE21 3-EM6T-1 Enabled Enabled 30
3-EM6T-2 Enabled Enabled 30

7. Select Deploy and click OK.
----End
Procedure
NOTE
follows.
Parameter Value
Transmission System
253

1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7

AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7

NOTE
AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid at
a time. In this example, AF11 is used. It is the same case with the AF2, AF3, and AF4.
Transmission System
254
NOTE
Parameter Value
NE NE21 NE22
NE23
NE24
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
Packet Type CVLAN

The values for the related parameters of each NE are provided as follows.
Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

NE NE21 NE22
NE23
NE24
Port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
Transmission System
255

----End
Procedure
Step 1 See Creating an MD and create the MDs.
Parameter Value
Maintenance
Domain Name
Maintenance
Domain Level
4 4 4 4

Step 2 See Creating an MA and create the MA.
Parameter Value
Maintenance
Domain Name
Maintenance
Association
Name
Dlan Dlan Dlan Dlan
Relevant
Service
1-Dlan 1-Dlan 1-Dlan 1-Dlan
CC Test
Transmit Period
1s 1s 1s 1s

Parameter Value
Transmission System
256
Parameter Value
Maintenance
Domain Name
Maintenance
Association
Name
Dlan Dlan Dlan Dlan
Board 3-EM6T 3-EM6T 3-EM6T 3-EM6T
Port 3-EM6T-1 3-EM6T-3 3-EM6T-3 3-EM6T-3
VLAN - - - -
MEP ID 1 2 3 4
Direction Ingress Ingress Ingress Ingress
CC Status Active Active Active Active

Step 4 See Creating Remote MEPs in an MA and create the remote MEP points.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Dlan Dlan Dlan Dlan Dlan Dlan
Remote
Maintenan
ce Point ID
(e.g:1,3-6)
2 3 4 1 1 1

Step 5 Perform an LB test to verify Ethernet service configurations.
There should be no packet lost during the LB tests.
----End
Transmission System
257
Procedure
of Ethernet ports.
Parameter Value
NE NE21 NE22
NE24
NE23
Port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
Enable Port Enabled
Max Frame Length
(bytes)
1620

of Ethernet ports.
Parameter Value
NE NE21 NE22
NE24
NE23
Port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
Broadcast Packet
Suppression
Enabled
Broadcast Packet
Suppression
Threshold
30
Transmission System
258

----End
Procedure
Step 1 See 8.18.1 Configuring IEEE 802.1d Bridge-Based E-LAN Services and configure the E-
LAN services.
l Parameters of NE21
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Service Name Dlan
Tag Type Tag-Transparent

The values for the related parameters that need to be set in the UNI tab page are provided as
follows.
Port SVLAN VLANs/CVLAN
3-EM6T-1 - Blank
3-EM6T-2 - Blank
4-EM6T-1 - Blank

l Parameters of NE22 and NE24
as follows.
Parameter Value
Service ID 1
Service Name Dlan

Transmission System
259
follows.
3-EM6T-1 - Blank
3-EM6T-2 - Blank
3-EM6T-3 - Blank

as follows.
Parameter Value
Service ID 1
Service Name Dlan

follows.
3-EM6T-1 - Blank
3-EM6T-2 - Blank
3-EM6T-3 - Blank

----End
Procedure
NOTE
Transmission System
260
follows.
Parameter Value

1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7

AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7

Transmission System
261
NOTE
AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid at
a time. In this example, AF11 is used. It is the same case with the AF2, AF3, and AF4.
NOTE
Parameter Value
NE NE21 NE22
NE23
NE24
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
Packet Type CVLAN

The values for the related parameters of each NE are provided as follows.
Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

Transmission System
262
NE NE21 NE22
NE23
NE24
Port 3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3

----End
Procedure
Parameter Value
Maintenance
Domain Name
Maintenance
Domain Level
4 4 4 4

Step 2 See Creating an MA and create the MA.
Parameter Value
Maintenance
Domain Name
Maintenance
Association
Name
Dlan Dlan Dlan Dlan
Relevant
Service
1-Dlan 1-Dlan 1-Dlan 1-Dlan
Transmission System
263
Parameter Value
CC Test
Transmit Period
1s 1s 1s 1s

Parameter Value
Maintenance
Domain Name
Maintenance
Association
Name
Dlan Dlan Dlan Dlan
VLAN - - - -
MEP ID 1 2 3 4

Step 4 See Creating Remote MEPs in an MA and create the remote MEP points.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Dlan Dlan Dlan Dlan Dlan Dlan
Remote
Maintenan
ce Point ID
(e.g:1,3-6)
2 3 4 1 1 1

Transmission System
264
Step 5 Perform an LB test to verify Ethernet service configurations.
There should be no packet lost during the LB tests.
----End
4.7 Configuration Example (802.1q Bridge-Based E-LAN
Service)
This section considers an 802.1q bridge-based E-LAN service as an example to describe how
l NodeB11 and NodeB12 belong to domain 1; NodeB15 belongs to domain 2. The NodeBs
in a domain have the same VLAN ID and the data from different domains is isolated from
each other by using the VLAN IDs.
To meet the preceding requirements, IEEE 802.1q bridge-based E-LAN services are configured
for service transmission on each NE; in addition, the functions of detecting looped services and
suppressing broadcast packets, and QoS processing are configured.
Transmission System
265
Figure 4-23 Networking diagram (IEEE 802.1q bridge-based E-LAN services)
NE12 NE13
NE15
NE14
NE16
FE
FE
FE
GE
NodeB15
VLAN 110
NodeB12
VLAN 100
Domain1
VLAN 100
Domain2
VLAN 110
NodeB11
VLAN 100
NE11
Packet network

NOTE
NE13
transmit backhaul
services from
NodeBs.
Between NE12 and
NE11
transmit Native
Ethernet services.
Between NE12 and
NodeB11
NodeB11.
NE14
transmit Native
Ethernet services.
Transmission System
266
Between NE13 and
NE15
transmit Native
Ethernet services.
Between NE13 and
NE12
transmit backhaul
services from
NodeBs.
NE13
transmit Native
Ethernet services.
Between NE14 and
NodeB12
NodeB12.
NE16
transmit Native
Ethernet services.
Between NE15 and
NE13
transmit Native
Ethernet services.
NE15
transmit Ethernet
services.
Between NE16 and
NodeB15
NodeB15.

service.
Transmission System
267
NOTE
the equipment, the maximum frame length is set to 1620(bytes). If the equipment needs to transmit jumbo
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.
Parameter Value
NE NE12 NE13 NE14
NE16
NE15
Port 3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
Encapsulation
type
802.1Q
Port working
mode
Auto-negotiation
Max Frame
Length (bytes)
1620
Loopback port
shutdown
Disabled
Broadcast
Packet
Suppression
Enabled
Broadcast
Packet
Suppression
Threshold
30

Transmission System
268
Table 4-68 provides the planning information of IEEE 802.1q bridge-based E-LAN services.
Table 4-68 Information about IEEE 802.1q bridge-based E-LAN services
Parameter NE12 NE13 NE14 NE15 NE16
Service ID 1 1 1 1 1
Service
name
Qlan Qlan Qlan Qlan Qlan
Tag type C-Aware C-Aware C-Aware C-Aware C-Aware
Self-learning
MAC
address
Enabled Enabled Enabled Enabled Enabled
MAC
address
learning
mode
IVL IVL IVL IVL IVL
Mounted
UNI port
3-EM6T-3
(VLAN ID:
100)
3-EM6T-2
(VLAN ID:
100, 110)
3-EM6T-1
(VLAN ID:
100, 110)
4-EM6T-1
(VLAN ID:
100, 110)
3-EM6T-2
(VLAN ID:
110)
3-EM6T-1
(VLAN ID:
100)
3-EM6T-1
(VLAN ID:
100)
3-EM6T-3
(VLAN ID:
100)
3-EM6T-1
(VLAN ID:
110)
3-EM6T-2
(VLAN ID:
110)
3-EM6T-1
(VLAN ID:
110)
3-EM6T-3
(VLAN ID:
110)

NOTE
In this example, the split horizon group is not used.
configuring QoS.
QoS (Diffserv)
Transmission System
269
configuration.
Type
CS7 7 -
CS6 6 -
streaming services)
AF4 4 -
AF1 1 -
services)

NOTE
in this example.
Transmission System
270
CS7 SP
CS6 SP
EF SP
BE SP

network.
QoS (Port Shaping)
node.
Procedure
of Ethernet ports.
Parameter Value
NE16
NE15
Transmission System
271
Parameter Value
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-1
Enable Port Enabled
Encapsulatio
n Type
802.1Q
Working
Mode
Auto-Negotiation
Max Frame
Length
(bytes)
1620

Ethernet ports.
Parameter Value
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
TAG Tag Aware

of Ethernet ports.
Parameter Value
NE NE12 NE13 NE14
NE16
NE15
Port 3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
Loopback
Check
Enabled
Broadcast
Packet
Suppression
Enabled
Transmission System
272
Parameter Value
Broadcast
Packet
Suppression
Threshold
30

----End
Procedure
Menu.
Set Service Name to Qlan.
b. Set Tag Type to C-Aware.
c. Select 3-EM6T-1, 3-EM6T-2, and 3-EM6T-3 from the Available Interface list, and
click .
NOTE
d. Set C-VLAN and Encapsulation Type for the selected interfaces according to 4.7.2.2
Service Planning (Ethernet Services).
e. OK
Transmission System
273
4. Repeat Step 1.3 to configure bridge-mounted ports on NE13, NE14, NE15, and NE16
according to 4.7.2.2 Service Planning (Ethernet Services).
a. Click .
Length
(bytes)

a. Click .
d. Click .
f. Click Apply.
Transmission System
274
NE Port Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold

----End
Procedure
NOTE
follows.
Parameter Value

Transmission System
275
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7

AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7

NOTE
Parameter Value
NE NE12 NE13 NE14
NE16
NE15
Transmission System
276
Parameter Value
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2
Packet Type CVLAN

Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

NE NE12 NE13 NE14
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2

----End
Transmission System
277
Procedure
Step 1 See Creating an MD and create the MDs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
EdgeNE EdgeNE EdgeNE
Maintenance
Domain Level
4 4 4

Step 2 See Creating an MA and create the MAs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
Maintenance
Association
Name
12_Qlan 15_Qlan 12_Qlan 15_Qlan
Relevant
Service
Qlan Qlan Qlan Qlan
CC Test
Transmit Period
1s 1s 1s 1s

Step 3 See Creating an MEP Point and create the MEPs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
Maintenance
Association
Name
VLAN 100 110 100 110
Transmission System
278
Parameter Value
MEP ID 1 2 3 4

Step 4 See Creating Remote MEPs in an MA and create the remote MEPs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
Maintenance
Association
Name
Remote
Maintenance
Point ID(e.g:
1,3-6)
3 4 1 2

----End
Procedure
of Ethernet ports.
Transmission System
279
Parameter Value
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
3-EM6T-1
Enable Port Enabled
Encapsulatio
n Type
802.1Q
Working
Mode
Auto-Negotiation
Max Frame
Length
(bytes)
1620

Ethernet ports.
Parameter Value
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
TAG Tag Aware

of Ethernet ports.
Parameter Value
NE NE12 NE13 NE14
NE16
NE15
Port 3-EM6T-1
3-EM6T-2
3-EM6T-3
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-2
Loopback
Check
Enabled
Transmission System
280
Parameter Value
Broadcast
Packet
Suppression
Enabled
Broadcast
Packet
Suppression
Threshold
30

----End
Procedure
Step 1 See 8.18.2 Configuring IEEE 802.1q Bridge-Based E-LAN Services and configure the E-
LAN services.
as follows.
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Aware

follows.
3-EM6T-2 - 100, 110
3-EM6T-3 - 100
3-EM6T-1 - 100, 110

as follows.
Transmission System
281
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Aware

follows.
4-EM6T-1 - 100, 110
3-EM6T-1 - 100
3-EM6T-2 - 110

as follows.
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Aware

follows.
3-EM6T-1 - 100
3-EM6T-3 - 100

as follows.
Transmission System
282
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Aware

follows.
3-EM6T-1 - 110
3-EM6T-2 - 110

as follows.
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Aware

follows.
3-EM6T-1 - 110
3-EM6T-3 - 110

----End
Transmission System
283
Procedure
NOTE
follows.
Parameter Value

1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7

AF11 1
AF21 2
AF31 3
Transmission System
284
AF41 4
EF 5
CS6 6
CS7 7

NOTE
Parameter Value
NE NE12 NE13 NE14
NE16
NE15
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2
Packet Type CVLAN

Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

Transmission System
285
NE NE12 NE13 NE14
NE16
NE15
Port 3-EM6T-1
3-EM6T-3
3-EM6T-2
3-EM6T-1
3-EM6T-2
4-EM6T-1
3-EM6T-3
3-EM6T-1
3-EM6T-1
3-EM6T-2

----End
Procedure
Step 1 See Creating an MD and create the MDs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
EdgeNE EdgeNE EdgeNE
Maintenance
Domain Level
4 4 4

Step 2 See Creating an MA and create the MAs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
Maintenance
Association
Name
Relevant
Service
Qlan Qlan Qlan Qlan
CC Test
Transmit Period
1s 1s 1s 1s

Transmission System
286
Step 3 See Creating an MEP Point and create the MEPs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
Maintenance
Association
Name
VLAN 100 110 100 110
MEP ID 1 2 3 4

Step 4 See Creating Remote MEPs in an MA and create the remote MEPs for NE12, NE14, and NE16.
Parameter Value
NE NE12 NE14 NE16
Maintenance
Domain Name
Maintenance
Association
Name
Remote
Maintenance
Point ID(e.g:
1,3-6)
3 4 1 2

----End
Transmission System
287
4.8 Configuration Example (802.1ad Bridge-Based E-LAN
Service)
This section considers an 802.1ad bridge-based E-LAN service as an example to describe how
l The RNC provides GE electrical ports whose port rate is 1000 Mbit/s.
l The VLAN ID used by the services on a NodeB is allocated by the RNC that controls the
NodeB.
l The VLAN IDs of services on NodeBs that are controlled by different RNCs may be the
same. Therefore, the transport network allocates an S-VLAN ID for services from the
NodeBs controlled by the same RNC, and the S-VLAN IDs on the entire network are
planned in a unified manner.
l The Ethernet services on the ring network are protected.
To meet the preceding requirements, IEEE 802.1ad bridge based E-LAN services are configured
to implement transmission of the NodeB services; in addition, the functions of detecting looped
services and suppressing broadcast packets and QoS processing are configured. See Figure
4-24.
Transmission System
288
Figure 4-24 Networking diagram (IEEE 802.1ad bridge-based E-LAN services)
NodeB21
CVLAN 100
SVLAN 200
NE21
NE23
NE22
NE24
RNC1
GE
FE
FE
FE
802.1ad bridge
802.1ad bridge
802.1ad bridge
802.1ad bridge
NodeB23
CVLAN 110
SVLAN 200
NodeB24
CVLAN 100
SVLAN 201
GE
RNC2

NOTE
RNC1
transmit backhaul
services from
NodeBs.
Between NE21 and
RNC2
transmit backhaul
services from
NodeBs.
Between NE21 and
NE22
transmit Native
Ethernet services.
Between NE21 and
NE24
transmit Native
Ethernet services.
Transmission System
289
NE23
transmit Native
Ethernet services.
Between NE22 and
NE21
transmit Native
Ethernet services.
Between NE22 and
NodeB21
NodeB21.
NE24
transmit Native
Ethernet services.
Between NE23 and
NE22
transmit Native
Ethernet services.
Between NE23 and
NodeB23
NodeB23.
NE23
transmit Native
Ethernet services.
Between NE24 and
NE21
transmit Native
Ethernet services.
Between NE23 and
NodeB24
NodeB24.

service.
Transmission System
290
NOTE
l In this example, the FE/GE ports on all the NodeBs/RNC work in auto-negotiation mode. Therefore, the
FE/GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port
works in another mode, the local Ethernet port must work in the same mode. The working modes of the
Ethernet ports inside the network are planned as auto-negotiation.
Parameter Value
NE NE21 NE22
NE23
NE24
Port 3-EM6T-2
3-EM6T-1
4-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
Encapsulation
type
QinQ 802.1q QinQ 802.1q
Port working
mode
Auto-negotiation
Max Frame
Length (bytes)
1620
Loopback port
shutdown
Disabled
Broadcast
Packet
Suppression
Enabled
Broadcast
packet
suppression
threshold
30

Table 4-72 provides the planning information of IEEE 802.1ad bridge-based E-LAN services.
Transmission System
291
Table 4-72 Information about IEEE 802.1ad bridge-based E-LAN services
Parameter NE21 NE22 NE23 NE24
Service ID 1 1 1 1
Service name ADlan ADlan ADlan ADlan
Tag type S-Aware S-Aware S-Aware S-Aware
Self-learning
MAC address
MAC address
learning mode
IVL IVL IVL IVL
Mounted UNI
port
4-EM6T-2
(CVLAN ID:
100, 110)
(SVLAN ID:
200)
3-EM6T-1
(CVLAN ID:
100) (SVLAN
ID: 201)
3-EM6T-3
(CVLAN ID:
100) (SVLAN
ID: 200)
3-EM6T-3
(CVLAN ID:
110) (SVLAN
ID: 200)
3-EM6T-3
(CVLAN ID:
100) (SVLAN
ID: 201)
Mounted NNI
port
3-EM6T-2
(SVLAN ID:
200, 201)
4-EM6T-1
(SVLAN ID:
200, 201)
3-EM6T-2
(SVLAN ID:
200, 201)
3-EM6T-1
(SVLAN ID:
200, 201)
3-EM6T-2
(SVLAN ID:
200, 201)
3-EM6T-1
(SVLAN ID:
200, 201)
3-EM6T-2
(SVLAN ID:
200, 201)
3-EM6T-1
(SVLAN ID:
200, 201)

configuring QoS.
QoS (Diffserv)
configuration.
Transmission System
292
Type
CS7 7 -
CS6 6 -
streaming services)
AF4 4 -
AF1 1 -
services)

NOTE
and therefore needs to be modified as required.
in this example.
CS7 SP
CS6 SP
Transmission System
293
EF SP
BE SP

network.
QoS (Port Shaping)
node.
Procedure
of Ethernet ports.
Parameter Value
NE NE21 NE22
NE23
NE24
Port 4-EM6T-1
3-EM6T-2
4-EM6T-2
3-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
Transmission System
294
Parameter Value
Enable Port Enabled
Encapsulation
Type
QinQ 802.1Q QinQ 802.1Q
Max Frame
Length(bytes)
1620

Ethernet ports.
Parameter Value
NE NE21 NE22
NE23
NE24
Port 4-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-2
3-EM6T-3
TAG Tag Aware

of Ethernet ports.
Parameter Value
NE NE21 NE22
NE23
NE24
Port 4-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-2
3-EM6T-3
Broadcast Packet
Suppression
Enabled
Broadcast Packet
30
Transmission System
295

----End
Procedure
Menu.
Set Service Name to ADlan.
b. Set Tag Type to S-Aware.
c. Select 3-EM6T-1, 3-EM6T-2, 4-EM6T-1, and 4-EM6T-2 from the Available
Interface list, and click .
NOTE
d. Set C-VLAN, S-VLAN, and Encapsulation Type for the selected interfaces
according to 4.8.2.2 Service Planning (Ethernet Services).
e. OK
4. Repeat Step 1.3 to configure bridge-mounted ports on NE22, NE23, and NE24 according
to 4.8.2.2 Service Planning (Ethernet Services).
a. Click .
Transmission System
296
Length
(bytes)

a. Click .
d. Click .
f. Click Apply.
NE Port Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
Transmission System
297
NE Port Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold

----End
Procedure
follows.
Parameter Value

Transmission System
298
1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7

AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7

NOTE
NE21 3-EM6T-2
4-EM6T-1
SVLAN
Transmission System
299
3-EM6T-1
4-EM6T-2
CVLAN
NE22
NE23
NE24
3-EM6T-3 CVLAN
3-EM6T-1
3-EM6T-2
SVLAN

l Parameters of NE21 to NE23
The values for the related parameters that need to be set in the main interface are as follows.
Parameter Value
Policy ID 1
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

NE NE21 NE22
NE23
NE24
Port 3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2

----End
Transmission System
300
Procedure
Parameter Value
Maintenance
Domain Name
Maintenance
Domain Level
4 4 4 4

Step 2 See Creating an MA and create an MA.
Parameter Value
Maintenance
Domain Name
Maintenance
Association
Name
ADlan ADlan ADlan ADlan
Relevant
Service
1-ADlan 1-ADlan 1-ADlan 1-ADlan
CC Test
Transmit Period
1s 1s 1s 1s

Step 3 See Creating an MEP Point and create MEPs.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
ADlan ADlan ADlan ADlan ADlan ADlan
Transmission System
301
Paramete
r
Value
VLAN 100 110 100 100 110 100
MEP ID 1 2 3 5 6 4

Step 4 See Creating Remote MEPs in an MA and create the remote MEPs.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Remote
Maintenan
ce Point ID
(e.g:1,3-6)
4 5 6 2 3 1

Step 5 Perform LB tests to verify Ethernet service configurations.
----End
Transmission System
302
Procedure
of Ethernet ports.
Parameter Value
NE NE21 NE22
NE23
NE24
Port 4-EM6T-1
3-EM6T-2
4-EM6T-2
3-EM6T-1
3-EM6T-1
3-EM6T-2
3-EM6T-3
Enable Port Enabled
Encapsulation
Type
QinQ 802.1Q QinQ 802.1Q
Max Frame
Length(bytes)
1620

Ethernet ports.
Parameter Value
NE NE21 NE22
NE23
NE24
Port 4-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-2
3-EM6T-3
TAG Tag Aware

of Ethernet ports.
Transmission System
303
Parameter Value
NE NE21 NE22
NE23
NE24
Port 4-EM6T-2
3-EM6T-1
4-EM6T-1
3-EM6T-2
3-EM6T-1
3-EM6T-2
3-EM6T-3
Broadcast Packet
Suppression
Enabled
Broadcast Packet
30

----End
Procedure
Step 1 See 8.18.3 Configuring IEEE 802.1ad Bridge-Based E-LAN Services and configure the E-
LAN services.
as follows.
Parameter Value
Service ID 1
Service Name ADlan
Tag Type S-Aware

follows.
4-EM6T-2 200 100, 110
Transmission System
304
3-EM6T-1 201 100

The values for the related parameters that need to be set in the NNI tab page are provided as
follows.
Port SVLANs
4-EM6T-1 200, 201
3-EM6T-2 200, 201

as follows.
Parameter Value
Service ID 1
Service Name ADlan
Tag Type S-Aware

follows.
3-EM6T-3 200 100

follows.
Port SVLANs
3-EM6T-1 200, 201
3-EM6T-2 200, 201

as follows.
Transmission System
305
Parameter Value
Service ID 1
Service Name ADlan
Tag Type S-Aware

follows.
3-EM6T-3 200 110

follows.
Port SVLANs
3-EM6T-1 200, 201
3-EM6T-2 200, 201

as follows.
Parameter Value
Service ID 1
Service Name ADlan
Tag Type S-Aware

follows.
3-EM6T-3 201 100

Transmission System
306
follows.
Port SVLANs
3-EM6T-1 200, 201
3-EM6T-2 200, 201

----End
Procedure
follows.
Parameter Value

1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7

Transmission System
307
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7

NOTE
NE21 3-EM6T-2
4-EM6T-1
SVLAN
3-EM6T-1
4-EM6T-2
CVLAN
NE22
NE23
NE24
3-EM6T-3 CVLAN
3-EM6T-1
3-EM6T-2
SVLAN

l Parameters of NE21 to NE23
The values for the related parameters that need to be set in the main interface are as follows.
Parameter Value
Policy ID 1
Transmission System
308
Parameter Value
WRR (AF4 to AF1)
SP (BE)
60 (AF3)
30 (AF2)
5 (AF1)

NE NE21 NE22
NE23
NE24
Port 3-EM6T-2
4-EM6T-1
3-EM6T-1
3-EM6T-2

----End
Procedure
Parameter Value
Maintenance
Domain Name
Maintenance
Domain Level
4 4 4 4

Transmission System
309
Step 2 See Creating an MA and create an MA.
Parameter Value
Maintenance
Domain Name
Maintenance
Association
Name
ADlan ADlan ADlan ADlan
Relevant
Service
1-ADlan 1-ADlan 1-ADlan 1-ADlan
CC Test
Transmit Period
1s 1s 1s 1s

Step 3 See Creating an MEP Point and create MEPs.
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
VLAN 100 110 100 100 110 100
MEP ID 1 2 3 5 6 4

Step 4 See Creating Remote MEPs in an MA and create the remote MEPs.
Transmission System
310
Paramete
r
Value
Maintenan
ce Domain
Name
Maintenan
ce
Associatio
n Name
Remote
Maintenan
ce Point ID
(e.g:1,3-6)
4 5 6 2 3 1

Step 5 Perform LB tests to verify Ethernet service configurations.
----End
Transmission System
311
5 Configuring a Composite Service Consisting
of E-Line and E-LAN Services
About This Chapter
This section describes the networking of and configuration method for a composite service
consisting of E-Line and E-LAN services.
5.1 Basic Concepts
Learning about the basic concepts of composite services helps to configure composite services.
5.2 Configuration Flow for a Composite Service Consisting of E-Line and E-LAN Services
This section describes how to configure a composite service consisting of E-Line and E-LAN
services, including configuring service information, ports, and protection schemes.
5.3 Configuration Example: Composite Service Consisting of E-Line and E-LAN Services
Transmission System
Configuration Guide (Packet Transport Domain)
5 Configuring a Composite Service Consisting of E-Line and
E-LAN Services
312
5.1 Basic Concepts
Learning about the basic concepts of composite services helps to configure composite services.
Purpose
Integrated service management is necessary for a network where services are received/
transmitted in various modes and are running in various scenarios.
The U2000 provides a composite service management function, which applies to scenarios
where a single service does not meet requirements. With this function, users can flexibly combine
pseudo wire emulation edge-to-edge (PWE3), and E-Line services into composite services to
meet the requirements of various solutions, such as IP RAN and IP core.
The U2000 also provides simplified and user-friendly service provisioning interfaces and
supports visual and end-to-end service management. These features significantly simplify
network O&M operations and improve the core competitiveness of carriers.
Definition
A composite service is a combination of multiple services, such as PWE3 service + E-Line
service.
A composite service consists of service components and connection points. Figure 5-1 shows
the model of a composite service.
Figure 5-1 Composite service

l Service component: A service component is a service that needs to be added to a composite
service. For example, the service components of a PWE3+E-Line composite service are
PWE3 and E-Line services.
l Connection point: A connection point connects two service components to form a
composite service. A connection point shows the connection mode between two service
components.
PW connection point: Service components are connected by PWs to form a composite
service.
Interface connection point: Service components are connected by service access
interfaces (interfaces connected to the user side) to form a composite service.
Transmission System
E-LAN Services
313
5.2 Configuration Flow for a Composite Service Consisting
services, including configuring service information, ports, and protection schemes.
Figure 5-2 shows the flowchart for configuring a composite service consisting of E-Line and
E-LAN services.
Figure 5-2 Flowchart for configuring a composite service consisting of E-Line and E-LAN
services
Configure the UNI
Configuring the DCN
Function of a Port
Start
Required
Optional
End
Configure the MPLS
tunnel
Create the E-Line
services carried by
PWs
Create the E-LAN
services carried by
PWs
Configuring a
Composite Service
Verifying the
Composite Service
Consisting of E-Line
and E-LAN Services

Table 5-1 provides details about operations in the flowchart.
Transmission System
E-LAN Services
314
Table 5-1 Process of configuring a composite service consisting of E-Line and E-LAN services
St
e
p
Operation Remarks
1 Configu
ring a
UNI
port
(when
the UNI
port is
an
Ethernet
port)
8.1.1 Setting the General
Attributes of Ethernet
Interfaces
Required. Set parameters as follows:
l Set Enable Port to Enabled.
l Set Port Mode to Layer 2.
l Generally, set Encapsulation Type
to 802.1Q. When packets do not need
to be distinguished according to their
VLAN tags, set Encapsulation
Type to Null.
l Set Working Mode to the same
value as on the peer Ethernet
equipment. Generally, retain the
default value Auto-Negotiation for
Working Mode.
l If jumbo frames do not need to be
transmitted, retain the default value
1620 for Max Frame Length
(byte). If jumbo frames need to be
transmitted, set Max Frame Length
(byte) to the maximum length of the
jumbo frame to be transmitted.
8.1.2 Setting the Layer 2
Attributes of Ethernet Ports
Optional. Set parameters as follows:
l Set Tag according to the types of
packets from the peer equipment.
If all packets are tagged frames,
set Tag to Tag Aware.
If all packets are untagged frames,
set Tag to Access.
If both tagged and untagged
frames are received, set Tag to
Hybrid.
l When Tag is set to Access or
Hybrid, set Default VLAN ID and
VLAN Priority for the untagged
frames. Set VLAN Priority based on
the QoS plan.
Transmission System
E-LAN Services
315
St
e
p
Operation Remarks
8.1.5 Configuring Flow Control Optional. Set parameters as follows:
l Generally, PSN uses QoS policies to
prevent link congestion. By default,
retain the default value Disabled for
Auto-Negotiation Flow Control
Mode and Non-Autonegotiation
Flow Control Mode.
2 Configuring the DCN Function for a Port Optional. Perform this operation only
when the UNI port is an Ethernet port.
Set parameters as follows:
l The UNI port connects to external
equipment and does not need to
transmit inband DCN information.
Therefore, set Enable Port to
Disabled for the UNI port.
3 8.2.1 Configuring the NNIs for Ethernet
Services Carried by PWs
Required. Set parameters as follows:
l Set Port Mode to Layer 3.
l Set Enable Tunnel to Enabled.
l Set Specify IP Address to
Manually, and set IP Address and
IP Mask according to the service
plan.
4 Configu
ring
MPLS
tunnels
Tunnel
Required. Set MPLS tunnel parameters
according to the service plan. For details
on how to manage MPLS tunnels, see
8.9 Managing MPLS Tunnels.
Configurin
g tunnel
OAM
NOTE
Configure
MPLS
tunnel
OAM or
MPLS-TP
tunnel
OAM
according
to the
service
plan.
8.10 Configuring
MPLS Tunnel
OAM
NOTE
Only OptiX OSN
550 and OptiX
OSN 500 support
MPLS Tunnel
OAM. OptiX OSN
580 only supports
MPLS-TP OAM.
Optional. Set parameters as follows:
l Set Detection Mode to Manual.
l Set Detection Packet Type to FFD.
l Set Detection Packet Period(ms) to
3.3.
Transmission System
E-LAN Services
316
St
e
p
Operation Remarks
8.11 Configuring
MPLS-TP
Tunnel OAM
(Optional) The parameters are set as
follows:
l If all the NEs along a tunnel are
Huawei equipment that supports IP-
based MPLS-TP OAM, it is
recommended that you set MEG ID
Type to IP Based, so that you do not
need to plan MEG IDs, MEP IDs, and
RMEP IDs.
l If not all the NEs along a tunnel are
based MPLS-TP OAM or if there are
special requirements, it is
recommended that you set MEG ID
Type to ICC Based. In this case, plan
MEG IDs, MEP IDs, and RMEP IDs
based on the following principles:
All the MEPs and MIPs along the
same tunnel must have the same
MEG ID. MEPs and MIPs along
different tunnels must have
different MEG IDs.
unique.
parameter to the default value
Adaptive.
Detection Mode can be set only for
ingress nodes on bidirectional
tunnels and egress nodes.
default value 0 for both SD
Threshold(%) and SF Threshold
(%).
l To suppress a PW fault alarm caused
by a tunnel fault on an NE on which
an MS-PW is configured, set AIS
Status to Enabled.
l Set CC Packet Interval (ms) as
follows:
Transmission System
E-LAN Services
317
St
e
p
Operation Remarks
If the CC function is used to
trigger APS, it is recommended
that you set CC Packet Interval
(ms) to 3.33.
recommended that you set CC
Packet Interval(ms) to a value
greater than the packet
transmission delay variation.
If the CC function is used to check
the tunnel connectivity, it is
recommended that you set CC
Packet Interval(ms) to 1000.
CC Packet Interval(ms) can be set
only for egress nodes on bidirectional
tunnels and ingress nodes.
l It is recommended that you set CC
Packet Priority to the default value
7.CC Packet Priority can be set only
for egress nodes on bidirectional
tunnels and ingress nodes.
8.12 Configuring Tunnel APS Optional. Set tunnel APS parameters
on how to manage tunnel APS groups,
see 8.13 Managing Tunnel APS
Protection Groups.
NOTE
Tunnel APS is not used, select PW APS for
service protection. For the configuration of
PW APS, see Configuring PW APS.
5 l 8.17.6 Configuring E-Line Services
Carried by PWs on a Per-NE Basis
l 8.17.5 Configuring E-Line Services
Carried by PWs in End-to-End Mode
Required. Set relevant parameters
on how to manage Ethernet services
carried by PWs, see 8.27 Managing
PWE3 Services.
6 l 8.18.7 Creating E-LAN Services
Carried by PWs on a Per-NE Basis
l 8.18.8 Configuring E-LAN Services
Carried by PWs in End-to-End Mode
Required. Set relevant parameters
on how to manage Ethernet services
carried by PWs, see 8.27 Managing
PWE3 Services.
Transmission System
E-LAN Services
318
St
e
p
Operation Remarks
7 8.22 Configuring a Composite Service Required. Set relevant parameters
on how to manage composite services,
see 8.23 Managing Composite
Services.
8 5.3.4 Verifying the Composite Service
Consisting of E-Line and E-LAN Services
Optional. After completing data
configuration, check whether the
configuration is correct by verifying the
configured services.

5.3 Configuration Example: Composite Service Consisting
The networking diagram shows the requirements for a composite service consisting of E-Line
and E-LAN services.
On the network shown in Figure 5-3, services with the same VLAN ID from User A1 and User
A2 are received/transmitted by different ports on NE1. NE1 transmits the services to NE4, which
then aggregates them and transmits them to User A3.
l Services from User A1 are received/transmitted by the 4-EM6F-3 port on NE1; services
from User A2 are received/transmitted by the 4-EM6F-4 port on NE1; services from User
A3 are received/transmitted by the 4-EM6F-3 port on NE4.
l Services between User A1 and User A3 are data services, of which the VLAN ID is 100,
CIR is 30 Mbit/s, and PIR is 50 Mbit/s.
l Services between User A2 and User A3 are data services, of which the VLAN ID is 100,
CIR is 30 Mbit/s, and PIR is 50 Mbit/s.
l Services between User A1/User A2 and User A3 are carried by PWs. E-Line services are
configured on NE1, and E-LAN services are configured on NE4.
l Services between User A1/User A2 and User A3 are protected by tunnel APS.
The working path is NE1-NE2-NE4.
The protection path is NE1-NE3-NE4.
Transmission System
E-LAN Services
319
Figure 5-3 Networking of a composite service consisting of E-Line and E-LAN services
NE2
NE1
NE3
NE4
User A1
4
-
E
M
6
F
-
3
4-EM6F-3
4-EM6F-1
4-EM6F-1 4-EM6F-2
4-EM6F-1
4-EM6F-2
4-EM6F-1 4-EM6F-2
4-EM6F-2
User A3
User A2
4
-E
M
6
F
-4
NOTE
NOTE
The method for configuring services from User A2 to User A3 is the same as that for configuring services
from User A1 to User A3. When planning and configuring services from User A2 to User A3, follow
instructions in sections that describe how to plan and configure services from User A1 to User A3.
NE1 4-
EM6F-1
18.1.1.1 255.255.255.252 130.0.0.1
4-
EM6F-2
18.1.2.1 255.255.255.252
NE2 4-
EM6F-1
18.1.1.2 255.255.255.252 130.0.0.2
4-
EM6F-2
18.1.1.5 255.255.255.252
NE3 4-
EM6F-1
18.1.2.2 255.255.255.252 130.0.0.3
4-
EM6F-2
18.1.2.5 255.255.255.252
NE4 4-
EM6F-1
18.1.1.6 255.255.255.252 130.0.0.4
4-
EM6F-2
18.1.2.6 255.255.255.252
Transmission System
E-LAN Services
320

NOTE
l The IP addresses of Ethernet ports on an NE must not be on the same network segment.
l The IP addresses of ports at both ends of a tunnel must be on the same network segment.

The engineering information for configuring a composite service consisting of E-Line and E-
LAN services includes information for configuring: tunnels that carry PWs, UNI-NNI E-Line
services carried by PWs, E-LAN services carried by PWs, and points that connect E-Line and
E-LAN services to form a composite service.
You need to plan a tunnel for carrying PWs according to the service plan. When planning a
composite service consisting of E-Line and E-LAN services:
l Plan a tunnel for carrying PWs by reference to Table 5-2 and Table 5-3.
l Plan MPLS tunnel OAM by reference to Table 5-4.
l Plan MPLS tunnel APS by reference to Table 5-5.
l Plan UNI-NNI E-Line services carried by PWs by reference to Table 5-6.
l Plan E-LAN services carried by PWs by reference to Table 5-7.
l Plan the composite service by reference to Table 5-8.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
Pla
nni
ng
NE1_NE4_w
orking
tional
Unprot
ected
NE1_NE4_pr
otection
tional
Unprot
ected

Transmission System
E-LAN Services
321
MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Detection Packet
Type
FFD
NOTE
FFD
Transmission System
E-LAN Services
322
Detection Packet
Period (ms)
3.3
NOTE
3.3

Protection Type 1:1
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Table 5-6 E-Line service parameters
Service Type ETH
Service ID 1
Service Name pwe3_NE1
Node List
Transmission System
E-LAN Services
323
Source NE1: 4-EM6F-3
VLAN ID 100
Unterminated > Sink 130.0.0.4
PW
PW ID 35
Forward Label 20
Reverse Label 20
PW QoS
CIR (kbit/s) 30000
PIR (kbit/s) 50000
Advanced attributes for PWs
PW Type Ethernet

Table 5-7 E-LAN service parameters
Service Name vpls
VSI Name vsi1
VSI ID 50
NPE NE4
VSI Configuration
Transmission System
E-LAN Services
324
MTU 1500
Tag Type C-Aware
MAC Address
Learning
Enable
Learning Mode Quality (IVL)
Enable BPDU
Transparent
Transmission
Not Transparently Transmitted
PW Configuration
Unterminated PW Set parameters as follows:
l Source NE: NE4
l Sink NE: NE1
l PW ID: 35
l Signaling Type: Static
l Incoming Label: 20
l Outgoing Label: 20
l Tunnel: NE1_NE4_working
l PW Type: Ethernet
l Bandwidth Limit: Enable
l CIR (kbit/s): 30000
l PIR (kbit/s): 50000
Service port configuration
NE NE4
Interface 4-EM6F-4
VLAN 100

Table 5-8 Composite service parameters
Service Name PWE3+VPLS
Creation Type Customize
Transmission System
E-LAN Services
325
Service Component Select service components as follows:
l PWE3: pwe3_NE1
l VPLS: vpls
PW Connection Point Set parameters as follows:
l Name: connection1
l PW1
PW ID: 35
Equipment Name: NE1
Service Name: pwe3_NE1
Service Type: PWE3
l PW2
PW ID: 35
Equipment Name: NE4
Service Name: vpls
Service Type: VPLS

services in end-to-end mode.
Prerequisites
l You must be familiar with the networking requirements and service plan of the composite
service.
Procedure
Step 1 Follow instructions in 8.8.2 Configuring an MPLS Tunnel in an End-to-End Mode to
configure a tunnel for carrying PWs.
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Par
ame
ter
NE1_NE4_w
orking
tional
Unprot
ected
Transmission System
E-LAN Services
326
Par
am
ete
r
MPLS
Tunnel
Name
MPLS
Tunnel ID
Type
Direct
ion
Protec
ted
Type
Pla
nni
ng
NE1_NE4_pr
otection
tional
Unprot
ected

MP
LS
Tu
nn
el
ID
N
o
d
e
No
de
Ty
pe
In
Inte
rfac
e
In
L
a
b
el
Rev
erse
In
Lab
el
Out
Inte
rfac
e
Ou
t
La
bel
Reve
rse
Out
Labe
l
Next
Hop
Reve
rse
Next
Hop
Sour
ce
Nod
e
Sink
Nod
e
10 N
E
1
Ingr
ess
- - 103 4-
EM6
F-1
100 - 18.1.
1.2
- - 130.0
.0.4
N
E
2
Tra
nsit
4-
EM6
F-1
10
0
102 4-
EM6
F-2
101 103 18.1.
1.6
18.1.
1.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-1
10
1
- - - 102 - 18.1.
1.5
130.0
.0.1
-
20 N
E
1
Ingr
ess
- - 203 4-
EM6
F-2
200 - 18.1.
2.2
- - 130.0
.0.4
N
E
3
Tra
nsit
4-
EM6
F-1
20
0
202 4-
EM6
F-2
201 203 18.1.
2.6
18.1.
2.1
130.0
.0.1
130.0
.0.4
N
E
4
Egr
ess
4-
EM6
F-2
20
1
- - - 202 - 18.1.
2.5
130.0
.0.1
-

Step 2 Follow instructions in 8.10 Configuring MPLS Tunnel OAM to configure MPLS tunnel OAM.
Transmission System
E-LAN Services
327
Detection Packet
Type
FFD
NOTE
FFD
Detection Packet
Period (ms)
3.3
NOTE
3.3

Step 3 Follow instructions in 8.12 Configuring Tunnel APS to configure MPLS tunnel APS.
Protection Type 1:1
Tunnel
Name
NE1_NE4_working
Protecti
on
Tunnel ID 20
Tunnel
Name
NE1_NE4_protection
WTR Time (min) 5
Hold-off Time (100
ms)
0
NOTE

Step 4 Configure PW-carried E-Line services in end-to-end mode.
On NE1, configure PW-carried E-Line services that are emulated using PWE3 and are
transmitted to NE4.
Transmission System
E-LAN Services
328
2. Configure PW-carried E-Line service by reference to the following table, and click OK
after setting the parameters. For details about the configuration process of PW-carried E-
Line services, see 8.17.5 Configuring E-Line Services Carried by PWs in End-to-End
Mode.
Table 5-13 E-Line service parameters
Service Type ETH
Service ID 1
Service Name pwe3_NE1
Node List
Source NE1: 4-EM6F-3
VLAN ID 100
Unterminated > Sink 130.0.0.4
PW
PW ID 35
Forward Label 20
Reverse Label 20
PW QoS
CIR (kbit/s) 30000
PIR (kbit/s) 50000
Advanced attributes for PWs
PW Type Ethernet

Step 5 Configure PW-carried E-Line services in end-to-end mode.
Configure PW-carried E-Line services on NE4.
Transmission System
E-LAN Services
329
1. Choose Service > VPLS Service > Create VPLS Service from the main menu.
2. Configure PW-carried E-Line service by reference to the following table, and click OK.
For details about the configuration process of PW-carried E-Line services, see 8.18.8
Configuring E-LAN Services Carried by PWs in End-to-End Mode.
Table 5-14 E-LAN service parameters
Service Name vpls
VSI Name vsi1
VSI ID 50
NPE NE4
VSI Configuration
MTU 1500
Tag Type C-Aware
MAC Address
Learning
Enable
Learning Mode Quality (IVL)
Enable BPDU
Transparent
Transmission
Not Transparently Transmitted
PW Configuration
Unterminated PW Set parameters as follows:
l Source NE: NE4
l Sink NE: NE1
l PW ID: 35
l Signaling Type: Static
l Incoming Label: 20
l Outgoing Label: 20
l Tunnel: NE1_NE4_working
l PW Type: Ethernet
l Bandwidth Limit: Enable
l CIR (kbit/s): 30000
l PIR (kbit/s): 50000
Transmission System
E-LAN Services
330
Service port configuration
NE NE4
Interface 4-EM6F-4
VLAN 100

Step 6 Configure a composite service.
1. Choose Service > Composite Service > Create Composite Service from the main menu.
2. Configure basic information for the composite service.
l Service Name: PWE3+VPLS
l Creation Type: Customize
3. Select the created service components from Service Component.
l Choose Select > VPLS, and select the created service named vpls.
l Choose Select > PWE3, and select the created service named pwe3_NE1.
4. In the Connection Point area, choose Create > PW and configure the connection point.
l Name: connection1
l PW1
PW ID: 35
Equipment Name: NE1
Service Name: pwe3_NE1
Service Type: PWE3
l PW2
PW ID: 35
Equipment Name: NE4
Service Name: vpls
Service Type: VPLS
5. Click OK.
----End
Related Task
Follow instructions in 5.3.4 Verifying the Composite Service Consisting of E-Line and E-
LAN Services to check whether the composite service is configured correctly.
5.3.4 Verifying the Composite Service Consisting of E-Line and E-
LAN Services
You can check whether packet loss has occurred in an Ethernet packet service by looping back
the service at one end and testing packet loss with a SmartBits at the other end.
Transmission System
E-LAN Services
331
Prerequisites
l Ethernet services have been configured. For details on how to configure Ethernet services,
see 3 Configuring ETH PWE3 Services in the Configuration Guide (Packet Transport
Domain).
l Data network performance analyzer
l U2000
Connection Diagram for the Test
Figure 5-4 shows a connection diagram for testing packet Ethernet services.
Figure 5-4 Connection diagram for testing packet Ethernet services
3-EM6F-1
NE1
NE2
SmartBits
3-EM6F-1
Dual-domain/
TDM domain/
Packet domain
network
MAC inloop
NOTE
The connection diagram is only an example. In this example, a MAC-layer inloop is performed on an
Ethernet port on NE1, and the SmartBits is connected to an Ethernet port on NE2. If required, you can
connect the SmartBits to any Ethernet board on the source or sink NE of a packet Ethernet service.

Precautions
NOTICE
l Keep irrelevant personnel away from the testing environment during a test.
l Do not touch fibers, electrical wires, or cables unless necessary.
Procedure
Step 1 According to the test connection diagram, connect the SmartBits to the Ethernet port on NE2.
Step 2 Log in to the U2000. Follow instructions in Enabling NE Performance Monitoring to enable 15-
minute and 24-hour performance monitoring for NE1 and NE2.
Transmission System
E-LAN Services
332
NOTE
Performance monitoring needs to be enabled in case that a fault detected in the test can be located.
Step 3 Log in to the U2000 and set a MAC-layer inloop for the Ethernet port on NE1.
1. In the Workbench view, double-click Main Topology to display the main topology.
2. Right-click the NE to be looped back on the Main Topology of the U2000, and choose NE
Explorer from the shortcut menu.
3. Select the Ethernet board to be looped back, and choose Configuration > Interface
Management > Ethernet Interface from the Function Tree.
4. Select Advanced Attributes.
5. In the list, select an Ethernet interface, and then double-click PHY Loopback or MAC
Loopback to select a loopback mode.
6. Click Query. After the Prompt dialog box is displayed, click OK.
7. After the Operation Result dialog box is displayed, click Close.
Step 4 Use the SmartBits to perform tests on packet receiving and transmission.
NOTE
l Packets with all 0s are regarded as special packets. Therefore, do not use packets of all 0s for testing
transmitted and received packets.
l When the SmartBits transmits and receives packets for the first time, packet loss occurs due to MAC
address learning. Therefore, it is normal that the number of transmitted packets is different from the
number of received packets.
l In the tests after the first time, if the number of transmitted packets is the same as the number of received
packets, the cross-domain service channels are normal.
l If packet loss occurs during the tests, troubleshoot the fault and then perform 24-hour tests until the
channels pass the tests.
----End
Transmission System
E-LAN Services
333
6 Configuring CES Services
About This Chapter
The circuit emulation service (CES) function supports direct access of TDM E1 services to the
packet domain. Therefore, the CES function helps achieve smooth evolution from the TDM
domain to the packet domain.
6.1 Basic Concepts
CES: By using the PWE3 technology, PWE3 packet headers are added to TDM traffic to create
circuit emulation services (CES). PWE3 packet headers carry the frame format information,
alarm information, signaling information, and synchronization and timing information of the
TDM traffic. The encapsulated PW packets are transmitted over the MPLS tunnel on the PSN.
After being decapsulated at the PW egress, the TDM circuit switched service traffic is re-created.
On a packet switching network, the transmit and receive ends of a CES service maintain clock
synchronization by means of adaptive clock recovery (ACR).
6.2 Configuration Flow for the CES Services
The configuration flow varies according to the types of the CES services.
6.3 Configuration Example (UNI-UNI CES Services)
This topic uses an example to describe how to configure UNI-UNI CES services.
6.4 Configuration Example (UNI-NNI CES Services)
This topic uses an example to describe how to configure UNI-NNI CES services.
6.5 Verifying CES Services
After configuring CES services, you need to test connectivity of end-to-end CES services to
ensure that they work properly.
Transmission System
Configuration Guide (Packet Transport Domain) 6 Configuring CES Services
334
6.1 Basic Concepts
CES: By using the PWE3 technology, PWE3 packet headers are added to TDM traffic to create
circuit emulation services (CES). PWE3 packet headers carry the frame format information,
alarm information, signaling information, and synchronization and timing information of the
TDM traffic. The encapsulated PW packets are transmitted over the MPLS tunnel on the PSN.
After being decapsulated at the PW egress, the TDM circuit switched service traffic is re-created.
On a packet switching network, the transmit and receive ends of a CES service maintain clock
synchronization by means of adaptive clock recovery (ACR).
Emulation Mode
The OptiX NG-SDH series equipment supports two types of CES services: structure-aware TDM
circuit emulation service over packet switched network (CESoPSN) CES and structure-agnostic
TDM over packet (SAToP) CES.
In the case of CESoPSN CES:
l The equipment senses the frame format, frame alignment mode, and timeslot information
in the TDM circuit.
l The equipment processes the overheads and extracts the payloads in TDM frames. Then,
the equipment loads timeslots to the packet payload in a certain sequence. As a result, the
services in each timeslot are fixed and visible in packets.
In the case of SAToP CES:
l The equipment does not sense any format in the TDM signal. Instead, it considers TDM
signals as bit flows at a constant rate, and therefore the entire bandwidth of TDM signals
is emulated.
l The overheads and payloads in TDM signals are transparently transmitted.
Service Type
CES services are classified into UNI-UNI CES services and UNI-UNI CES services by service
implementation point.
l UNI-UNI CES services
As shown in Figure 6-1, a single OptiX OSN NE completes access of TDM services.
Transmission System
335
Figure 6-1 UNI-UNI CES services
BTS
BSC
TDM link
NE
PSN

l UNI-NNI CES services
As shown in Figure 6-2, the OptiX OSN NEs set UNI-NNI CES services. In the case of a
UNI-NNI CES service, the OptiX OSN NEs access customer TDM services through E1
ports; CES PWs are created between the OptiX OSN NEs to emulate end-to-end TDM
services.
Figure 6-2 UNI-NNI CES services
BTS2
BSC
BTS1
TDM link
NE
NE
NE
PSN
Tunnel
PW

6.2 Configuration Flow for the CES Services
The configuration flow varies according to the types of the CES services.
6.2.1 Configuration Flow for UNI-UNI CES Services
This section describes the operation tasks for configuring UNI-UNI CES services and the
relationships between the operation tasks.
Transmission System
336
Table 6-1 provides the procedure for configuring UNI-UNI CES services.
Figure 6-3 Configuration flow for UNI-UNI CES services
2. Configure CES
service ports
3. Configure UNI-
UNI CES services
Required
End
1. Create the
network
Start
4. Verify CES
services

Table 6-1 Configuration flow for UNI-UNI CES services
St
ep
Operation Remarks
1 Creating the network Required.
Create NEs, configure NE data, create fibers, and
configure clocks.
2 Configurin
g CES
service
ports
8.3.1
Setting
Basic
Attributes
of Smart
E1 Ports
Port Mode is set to Layer 1.
3 Configuring UNI-UNI
CES services
Required.
Set service ID, service name, service source, and service
sink.
4 Verifying CES services Required.
Test CES services at each E1 port using BER testers.

6.2.2 Configuration Flow for UNI-NNI CES Services
This section describes the operation tasks for configuring UNI-NNI CES services and the
relationships between the operation tasks.
Table 6-2 provides the procedure for configuring UNI-NNI CES services.
Transmission System
337
Figure 6-4 Configuration flow for UNI-NNI CES services
2. Configure the LSR
IDs of NEs
6. Configure UNI-NNI
CES services
5. Configure CES
service ports
Start
Required
Optional
End
1. Create the network
3. Configure the NNIs
on the packet domain
4. Configure the MPLS
tunnels
7. Verfiy CES services

Table 6-2 Configuration flow for UNI-NNI CES services
St
e
p
Operation Remarks
1 Creating the network Required.
Create NEs, configure NE data, create fibers, and
configure clocks.
2 Configuring the LSR ID Required.
l Each NE requires a unique LSR ID.
l When the LSR ID is specified for the first
time, a warm-reset occurs on the NE but does
not affect services. If the specified LSR ID is
then changed, no warm-reset occurs on the NE
and services are not affected.
l If a tunnel exists, do not change the LSR ID.
Transmission System
338
St
e
p
Operation Remarks
3 Configuring NNI ports in the packet
domain
Required.
l Configure the general attributes of Ethernet
ports.
l Configure the Layer 3 attributes of Ethernet
ports, such as tunnel enabling status and IP
addresses.
NNI ports in the packet domain are configured for
carrying tunnels.
4 Configuri
ng MPLS
tunnels
8.8 Configuring an
MPLS Tunnel
Required.
An MPLS tunnel can be configured in per-NE or
end-to-end mode. Set tunnel ID, service name,
ingress node, egress node, and transit node; set
signaling type to static.
Configuri
ng tunnel
OAM
NOTE
Configur
e MPLS
tunnel
OAM or
MPLS-
TP
tunnel
OAM
accordin
g to the
service
plan.
8.10
Configur
ing
MPLS
Tunnel
OAM
Optional. To ensure protection switching time
within 50 ms, set Detection Packet Type to
FFD and Detection Packet Interval (ms) to
3.3. Set the following parameters:
l Detection Packet Period(ms) is set to 3.3.
Transmission System
339
St
e
p
Operation Remarks
8.11
Configur
ing
MPLS-
TP
Tunnel
OAM
equipment that supports IP-based MPLS-TP
OAM, it is recommended that you set MEG
ID Type to IP Based, so that you do not need
to plan MEG IDs, MEP IDs, and RMEP IDs.
equipment that supports IP-based MPLS-TP
OAM or if there are special requirements, it is
recommended that you set MEG ID Type to
ICC Based. In this case, plan MEG IDs, MEP
IDs, and RMEP IDs based on the following
principles:
tunnel must have the same MEG ID. MEPs
and MIPs along different tunnels must
have different MEG IDs.
Each MEP ID in an MEG must be unique.
l It is recommended that you set this parameter
to the default value 7.
l It is recommended that you set this parameter
to the default value Adaptive.
nodes.
l It is recommended that you retain the default
value 0 for both SD Threshold(%) and SF
Threshold(%).
tunnel fault on an NE on which an MS-PW is
configured, set AIS Status to Enabled.
If the CC function is used to trigger APS,
it is recommended that you set CC Packet
Interval(ms) to 3.33.
If the packet transmission delay variation
exceeds 3.33 ms, it is recommended that
you set CC Packet Interval(ms) to a value
greater than the packet transmission delay
variation.
Transmission System
340
St
e
p
Operation Remarks
that you set CC Packet Interval(ms) to
1000.
CC Packet Interval(ms) can be set only for
egress nodes on bidirectional tunnels and
ingress nodes.
Priority can be set only for egress nodes on
bidirectional tunnels and ingress nodes.
8.12 Configuring
Tunnel APS
Optional. Set the parameters of tunnel APS
NOTE
Configuring PW APS.
5 Configuri
ng CES
service
ports
8.3.1 Setting Basic
Attributes of Smart
E1 Ports
Required. Set the following parameters:
Port Mode is set to Layer 1.
8.3.2 Setting
Advanced Attributes
of Smart E1 Ports
Optional. Set the following parameters:
l If PW Type is set to CESoPSN, Frame
Format can be set to CRC-4 Multiframe or
Double Frame as planned. The value CRC-4
Multiframe is recommended for securing
transmission quality.
If PW Type is set to SAToP, Frame
Format can be set to Unframe only.
l Frame Mode is set to 31 for local ports. If
Frame Mode is set to 30 for the opposite port,
include timeslot No.16 in the service timeslots
configured on the local port.
6 Configuring UNI-NNI CES
services
Required.
1. Configure service ID and service name.
2. Configure service source and service sink.
3. Configure PWs, including PW type, PW label,
and tunnel type.
4. Configure advanced attributes, including RTP
header, jitter buffer time, and packet loading
time.
7 Verifying CES services Required.
Test CES services at each E1 port using BER
testers.
Transmission System
341

6.3 Configuration Example (UNI-UNI CES Services)
This topic uses an example to describe how to configure UNI-UNI CES services.
This topic describes the networking diagram of UNI-UNI CES services.
As shown in Figure 6-5, the service access bandwidth is 2 Mbit/s and a piece of OptiX OSN
equipment is used to support access of CES services between the two BTSs and the BSC. One
CES service is configured between BTS1 and the BSC and one CES service is configured
between BTS2 and the BSC.
Figure 6-5 Networking diagram of UNI-UNI CES services
TDM link
BSC
BTS1
NE 1
3-MD1-1(PORT-1)
3-MD1-2(PORT-2)
3-MD1-3(PORT-3)
3-MD1-4(PORT-4)
BTS2

The service planning information contains all the parameters required for configuring the NE
data.
A UNI-UNI CES service is generally configured to implement access of base station services
and transmission of base station services to the BSC. As shown in Figure 6-5, two CES services
are configured between the two BTSs and the BSC in this example.
Table 6-3 lists the planned parameters of NE1 and their values.
Table 6-3 UNI-UNI CES parameters (NE1)
Parameter Value
NE NE1 NE1
Service ID 1 2
Service Name CES1 CES2
Transmission System
342
Parameter Value
Level E1 E1
Mode UNI-UNI UNI-UNI
Source Port 3-MD1-1(PORT-1) 3-MD1-3(PORT-3)
Source High Channel - -
Source Low Channel 1 3
Source 64K Timeslot - -
Sink Port 3-MD1-2(PORT-2) 3-MD1-4(PORT-4)
Sink High Channel - -
Sink Low Channel 2 4
Sink 64K Timeslot - -

This topic describes the per-NE configuration of UNI-UNI CES services.
Prerequisites
l You must be an NM user with "NE operator" authority or higher.
l You must be familiar with the networking, requirements, and service planning of the
example.
l The network is already created.
Procedure
Step 1 Configure E1 ports, including BTS-side E1 ports and BSC-side E1 ports.
1. Configure BTS-side E1 ports.
a. In the NE Explorer, click NE1 and choose Configuration > Packet Configuration
> Interface Management > PDH Interface from the Function Tree to configure
NodeB-side ports.
b. Select 3-MD1-1 (port-1) and 3-MD1-3 (port-3) and set Port Mode to Layer-1.
c. Click Apply. The Operation Results dialog box is displayed to indicate that the
operation is successful. Click Close.
2. Configure BSC-side E1 ports in the same manner.
NOTE
When configuring BSC-side E1 ports, select 3-MD1-2 (port-2) and 3-MD1-4 (port-4).
Step 2 Create local CES service 1.
Transmission System
343
1. In the NE Explorer, click NE1 and choose Configuration > Packet Configuration > CES
Service Management from the Function Tree.
2. Click New and set the parameters of local CES service 1.
3. Click OK. The Operation Results dialog box is displayed to indicate that the operation is
Step 3 Create local CES service 2 in the same manner.
----End
6.4 Configuration Example (UNI-NNI CES Services)
This topic uses an example to describe how to configure UNI-NNI CES services.
This topic describes the networking diagram of UNI-NNI CES services.
As shown in Figure 6-6, the service requirements on the network are as follows:
l BTS1, BTS2, and the BSC need to access the PSN through CES boards.
l BTS1 and BTS2 need to communicate with the BSC. The services on BTS1 and BTS2 need
to be isolated from each other.
Figure 6-6 Networking diagram of UNI-NNI CES services
BSC
BTS1
TDM link
NE1
NE 2
NE3
PSN
Tunnel
PW
4-EM6F-1
4-EM6F-1
3-MD1
3-MD1
4-EM6F-2
4-EM6F-1
3-MD1
3-MD1
BTS2

The service planning information contains all the parameter information required for configuring
the NE data, including the information for planning NNI ports, MPLS tunnels, and services.
The OptiX OSN NEs access customer TDM services through TDM ports or channelized STM-1
ports. CES PWs are created between the OptiX OSN NEs to emulate end-to-end TDM services,
Transmission System
344
therefore implementing service transmission between the BTSs and the BSC. Figure 6-6 shows
an example network.
Planning NE Parameters
Table 6-4 Planning information of NE parameters (NE1, NE2, and NE3)
NE LSR ID Port Port IP
Address
IP Mask
NE1 130.0.0.1 4-EM6F-1
(PORT-1)
10.0.2.2 255.255.255.25
2
NE2 130.0.0.2 4-EM6F-1
(PORT-1)
10.0.1.1 255.255.255.25
2
NE3 130.0.0.3 4-EM6F-1
(PORT-1)
10.0.2.1 255.255.255.25
2
4-EM6F-2
(PORT-2)
10.0.1.2 255.255.255.25
2

Planning the Tunnel Between NE1 and NE3
Table 6-5 Planning information of tunnel parameters (tunnel between NE1 and NE3)
Parameter NE1 NE3
Tunnel ID 1 2 2 1
Tunnel Name NE1-NE3#1 NE3-NE1#1 NE3-NE1#1 NE1-NE3#1
Node Type Ingress Egress Ingress Egress
Bandwidth
(kbit/s)
100 Mbit/s - 100 Mbit/s -
In Board/Logic
Interface Type
- 4-EM6F - 4-EM6F
In Port - 1 (PORT-1) - 1 (PORT-1)
In Label - 17 - 16
Out Board/
Logic Interface
Type
4-EM6F - 4-EM6F -
Out Port 1 (PORT-1) - 1 (PORT-1) -
Out Label 16 - 17 -
Transmission System
345
Parameter NE1 NE3
Next Hop
Address
10.0.2.1 - 10.0.2.2 -
Source Node - 130.0.0.3 - 130.0.0.1
Sink Node 130.0.0.3 - 130.0.0.1 -

Planning the Tunnel Between NE2 and NE3
Parameter NE2 NE3
Tunnel ID 3 4 4 3
Bandwidth
(kbit/s)
In Board/Logic
Interface Type
- 4-EM6F - 4-EM6F
In Port - 1 (PORT-1) - 2 (PORT-2)
In Label - 19 - 18
Out Board/
Logic Interface
Type
4-EM6F - 4-EM6F -
Out Port 1 (PORT-1) - 2 (PORT-1) -
Out Label 18 - 19 -
Next Hop
Address
10.0.1.2 - 10.0.1.1 -
Source Node - 130.0.0.3 - 130.0.0.2
Sink Node 130.0.0.3 - 130.0.0.2 -

Transmission System
346
Planning the CES Service from NodeB1 to the BSC
Table 6-7 Planning information of the service parameters (UNI-NNI CES service between NE1
and NE3)
Parameter Value
NE NE1 NE3
Service ID 1 1
Level E1 E1
Mode UNI-NNI UNI-NNI
Source Board 3-MD1 3-MD1
Source 64K Timeslot 1-31 1-31
PW ID 1 1
PW Type CESoPSN CESoPSN
Port
20 20
Port
20 20
Tunnel Type MPLS MPLS
Tunnel No. NE1-NE3#1 NE3-NE1#1
Peer LSR ID 130.0.0.3 130.0.0.1
RTP Head Disabled Disabled
Jitter Compensation
Buffering Time(us)
8000 8000
Packet Loading Time(us) 1000 1000
Ingress Clock Mode - -
Egress Clock Mode - -
Enable CES Service Alarm
Transparent Transmission
Enable Enable
Transmission System
347
Parameter Value
Threshold of Entering R Bit
Inserting Status
100 100
Threshold of Exiting R Bit
Inserting Status
5 5
Sequence Number Mode Huawei mode Huawei mode

Planning the CES Service from NodeB2 to the BSC
Table 6-8 Planning information of the service parameters (UNI-NNI CES service between NE2
and NE3)
Parameter Value
NE NE2 NE3
Service ID 2 2
Level E1 E1
PW ID 2 2
Port
21 21
Port
21 21
Tunnel No. NE2-NE3#1 NE3-NE2#1
Peer LSR ID 130.0.0.3 130.0.0.2
RTP Head Disabled Disabled
Transmission System
348
Parameter Value
Jitter Compensation
Buffering Time(us)
8000 8000
Enable Enable
Inserting Status
100 100
Inserting Status
5 5

This topic describes how to configure UNI-NNI CES services on a per-NE basis.
Prerequisites
l You must be familiar with the service requirements and service planning information of
the example network.
l The network must be created, the equipment must operate properly, and the equipment
must communicate with the NMS properly.
Procedure
Step 1 Configure the LSR IDs of NE1, NE2, and NE3. For details, see 8.8.1 Configuring LSR ID.
NE LSR ID
NE1 130.0.0.1
NE2 130.0.0.2
NE3 130.0.0.3

Step 2 Configure the NNI ports of NE1, NE2, and NE3 on the packet domain.
Transmission System
349
Configuration > Interface Management > Ethernet Interface from the Function Tree.
Configure the NNI ports.
2. In the Basic Attributes tab, select 4-EM6F-1(PORT-1). Right-click the Port Mode field,
and select Layer 3. Set other parameters according to the actual requirements. Click
Apply.
Set the associated parameters as follows.
Parameter Value Remarks
Port Enabled Enabled -
Port Mode Layer 3 The port carries a tunnel.
Working Mode Auto-
Negotiation
Set the working modes of the local port and opposite
port to be the same.
Max Frame
Length (byte)
1620 Set this parameter according to the length of data
packets. All the received data packets that exceed the
maximum frame length are discarded.

3. Select 4-EM6F-1(PORT-1) in the Layer 3 Attributes tab. Right-click the Enable
Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually.
Then, set the parameters such as IP Address and IP Mask. Click Apply.
Enable Tunnel Enabled -
Specify IP Manually Manually indicates that you can set the IP address
of the port.
IP Address 10.0.2.2 -
IP Mask 255.255.255.252 -

4. Navigate to the NE Explorer of NE2 and NE3 separately. Set the parameters associated
with each port according to Step a to Step c.
Set the basic attributes of each port to be the same as the basic attributes of NE1-4-EM6F-1
(PORT-1).
Set the Layer 3 attributes of each port as follows.
l NE2-4-EM6F-1(PORT-1)
Parameter Value
Enable Tunnel Enabled
Specify IP Manually
IP Address 10.0.1.1
Transmission System
350
Parameter Value
IP Mask 255.255.255.252

Parameter Value
Specify IP Manually
IP Address 10.0.1.2
IP Mask 255.255.255.252

Parameter Value
Specify IP Manually
IP Address 10.0.2.1
IP Mask 255.255.255.252

Step 3 Configure the MPLS tunnel between NE1 and NE3 and the MPLS tunnel between NE2 and
NE3. For details, see 8.8.2 Configuring an MPLS Tunnel in an End-to-End Mode.
NOTE
This topic considers the MPLS tunnel between the NE1 and NE3 as an example. The operations for configuring
the MPLS tunnel between NE2 and NE3 are similar to operations for configuring the MPLS tunnel between
NE1 and NE3.
1. Choose Service > Tunnel > Create Tunnel from the Main Menu.
2. Set the basic information about the MPLS tunnel between NE1 and NE3.
Parameter Value
Tunnel Name NE1-NE3
Protocol Type MPLS
Signaling Type Static CR
Create Reverse Tunnel Selected

3. On the left side physical topology, double-click NE1 and NE3 to add them. On the right
configuration side, set the corresponding NE roles.
Transmission System
351
Parameter Value
Auto-Calculate route Deselected
NE Role NE1: Ingress
NE3: Egress
Deploy Selected

4. Click Details and set the advanced parameters of the forward and reverse MPLS tunnels
between NE1 and NE3.
Parameter Value
Tunnel ID Forward Tunnel: 1
Reverse Tunnel: 2
CIR (kbit/s) Forward and Reverse Tunnels: 100000
LSP Type Forward and Reverse Tunnels: E-LSP
EXP Forward and Reverse Tunnels: None
Out Interface Forward Tunnel:
l NE1: 4-EM6F-1
l NE3: -
Reverse Tunnel:
l NE3:4-EM6F-1
l NE1: -
Out Label Forward Tunnel:
l NE1: 16
l NE3: -
Reverse Tunnel:
l NE3: 17
l NE1: -
In Interface Forward Tunnel:
l NE1: -
l NE3: 4-EM6F-1
Reverse Tunnel:
l NE3: -
l NE1: 4-EM6F-1
Transmission System
352
Parameter Value
In Label Forward Tunnel:
l NE1: -
l NE3: 16
Reverse Tunnel:
l NE3: -
l NE1: 17
Next Hop Forward Tunnel:
l NE1: 10.0.2.1
l NE3: -
Reverse Tunnel:
l NE3: 10.0.2.2
l NE1: -

5. Refer to Steps Step 3.1 to Step 3.4 and configure the MPLS tunnel between NE2 and NE3.
Parameter Value
Tunnel Name NE2-NE3
Protocol Type MPLS
Signaling Type Static CR
Create Reverse Tunnel Selected
Auto-Calculate route Deselected
NE3: Egress
Deploy Selected
Tunnel ID Forward Tunnel: 3
Reverse Tunnel: 4
CIR (kbit/s) Forward and Reverse Tunnels: 100000
LSP Type Forward and Reverse Tunnels: E-LSP
EXP Forward and Reverse Tunnels: None
Transmission System
353
Parameter Value
l NE2: 4-EM6F-1
l NE3: -
Reverse Tunnel:
l NE3: 4-EM6F-2
l NE2: -
l NE1: 18
l NE3: -
Reverse Tunnel:
l NE3: 18
l NE1: -
l NE1: -
l NE3: 4-EM6F-1
Reverse Tunnel:
l NE3: -
l NE1: 4-EM6F-2
In Label Positive Tunnel
l NE1: -
l NE3: 19
Reverse Tunnel:
l NE3: -
l NE1: 19
l NE1: 10.0.1.2
l NE3: -
Reverse Tunnel:
l NE3: 10.0.1.1
l NE1: -

Step 4 Configure the CES service ports on NE1, NE2, and NE3. For details, see 8.3.3 Configuring
Channelized STM-1 Ports.
Step 5 Configure the CES service between NE1 and NE3. For details, see 8.24.1 Creating a CES
Service in End-to-End Mode.
Transmission System
354
2. Set the basic attributes.
Parameter Value
Service Type CES
Service ID 1
Service Name CES1

3. Click Configure Source And Sink. Then, the Configure Source And Sink dialog box is
displayed.
4. Select NE1 as the source NE from Physical Topology on the left. Set the associated
parameters and then click OK.
Parameter Value
Board 3-MD1
Port -
High TimeSlot -
Low TimeSlot 1
Channelized Deselected

5. Select NE3 as the sink NE from Physical Topology on the left. Set the associated
Parameter Value
Board 3-MD1
Port 1
Low TimeSlot 1
Channelized Deselected
64K Timeslot 1-31

6. Under PW, set the associated parameters.
Parameter Value
Forward Tunnel NE1-NE3
Reverse Tunnel NE3-NE1
PW ID 1
Forward Label 16
Transmission System
355
Parameter Value
Reverse Label 16

7. Click Detail and then set the Advanced PW Parameters.
Parameter Value
Control Channel Type CW
VCCV Verification Mode Ping
RTP Header Disabled
Jitter Compensation Buffering Time(us) 8000
Packet Loading Time(us) 1000

Step 6 Configure the CES service between NE2 and NE3. For details, see 8.24.1 Creating a CES
Service in End-to-End Mode.
2. Set the basic attributes.
Parameter Value
Service Type CES
Service ID 2
Service Name CES2

displayed.
4. Select NE2 as the source NE from Physical Topology on the left. Set the associated
Parameter Value
Board 3-MD1
Port -
High TimeSlot -
Low TimeSlot 1
Channelized Selected

5. Select NE3 as the sink NE from Physical Topology on the left. Set the associated
Transmission System
356
Parameter Value
Board 3-MD1
Port 2
High TimeSlot 1
Low TimeSlot 1
Channelized Selected
64K Timeslot 1-31

6. Under PW, set the associated parameters.
Parameter Value
Forward Tunnel NE2-NE3
Reverse Tunnel NE3-NE2
PW ID 1
Forward Label 17
Reverse Label 17

7. Click Detail and then set the Advanced PW Parameters.
Parameter Value
Control Channel Type CW
VCCV Verification Mode Ping
RTP Header Disabled
Jitter Compensation Buffering Time(us) 8000
Packet Loading Time(us) 1000

----End
This topic describes how to configure UNI-NNI CES services on a per-NE basis.
Prerequisites
l You must be familiar with the service requirements and service planning information of
the example network.
Transmission System
357
l The network must be created, the equipment must operate properly, and the equipment
must communicate with the NMS normally.
Procedure
Step 1 Configure the LSR IDs of NE1, NE2, and NE3. For details, see 8.8.1 Configuring LSR ID.
NE LSR ID
NE1 130.0.0.1
NE2 130.0.0.2
NE3 130.0.0.3

Step 2 Configure the NNI ports of NE1, NE2, and NE3 on the packet domain.
Configuration > Interface Management > Ethernet Interface from the Function Tree.
Configure the NNI ports.
2. In the Basic Attributes tab, select 4-EM6F-1(PORT-1). Right-click the Port Mode field,
and select Layer 3. Set other parameters according to the actual requirements. Click
Apply.
Port Enabled Enabled -
Port Mode Layer 3 The port carries a tunnel.
Working Mode Auto-
Negotiation
Set the working modes of the local port and opposite
port to be the same.
Max Frame
Length (byte)
1620 Set this parameter according to the length of data
packets. All the received data packets that exceed the
maximum frame length are discarded.

3. Select 4-EM6F-1(PORT-1) in the Layer 3 Attributes tab. Right-click the Enable
Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually.
Then, set the parameters such as IP Address and IP Mask. Click Apply.
Enable Tunnel Enabled -
Specify IP Manually Manually indicates that you can set the IP address
of the port.
Transmission System
358
IP Address 10.0.2.2 -
IP Mask 255.255.255.252 -

4. Navigate to the NE Explorer of NE2 and NE3 separately. Set the parameters associated
with each port according to Step a to Step c.
Set the basic attributes of each port to be the same as the basic attributes of NE1-4-EM6F-1
(PORT-1).
Set the Layer 3 attributes of each port as follows.
Parameter Value
Specify IP Manually
IP Address 10.0.1.1
IP Mask 255.255.255.252

Parameter Value
Specify IP Manually
IP Address 10.0.1.2
IP Mask 255.255.255.252

Parameter Value
Specify IP Manually
IP Address 10.0.2.1
IP Mask 255.255.255.252

Step 3 Configure the MPLS tunnel between NE1 and NE3 and the MPLS tunnel between NE2 and
NE3. For details, see 8.8.2.1 Configuring a Unidirectional MPLS Tunnel.
Transmission System
359
Parameter NE1 NE3
Tunnel ID 1 2 2 1
PIR (kbit/s) 100 Mbit/s - 100 Mbit/s -
In Board/Logic
Interface Type
- 4-EM6F - 4-EM6F
In Port - 1(PROT-1) - 1(PROT-1)
In Label - 17 - 16
Out Board/
Logic Interface
Type
4-EM6F - 4-EM6F -
Out Port 1 - 1 -
Out Label 16 - 17 -
Next Hop
Address
10.0.2.1 - 10.0.2.2 -
Source Node - 130.0.0.3 - 130.0.0.1
Sink Node 130.0.0.3 - 130.0.0.1 -

Parameter NE2 NE3
Tunnel ID 3 4 4 3
Bandwidth
(kbit/s)
In Board/Logic
Interface Type
- 4-EM6F - 4-EM6F
In Port - 1(PROT-1) - 2(PROT-2)
In Label - 19 - 18
Transmission System
360
Parameter NE2 NE3
Out Board/
Logic Interface
Type
4-EM6F - 4-EM6F -
Out Port 1 - 2 -
Out Label 18 - 19 -
Next Hop
Address
10.0.1.2 - 10.0.1.1 -
Source Node - 130.0.0.3 - 130.0.0.2
Sink Node 130.0.0.3 - 130.0.0.2 -

Step 4 Configure the CES service ports on NE1, NE2, and NE3. For details, see 8.3 Configuring CES
Ports.
Step 5 Configure the UNI-NNI CES service between NE1 and NE3 and the UNI-NNI CES service
between NE2 and NE3. For details, see 8.24.3 Creating UNI-NNI CES Services on a Per-NE
Basis.
Table 6-13 Planning information of the service parameters (UNI-NNI CES service between
NE1 and NE3)
Parameter Value
Station NE1 NE3
Service ID 1 1
Level E1 E1
PW ID 1 1
Transmission System
361
Parameter Value
Port
20 20
Port
20 20
RTP Header Disabled Disabled
Jitter Compensation
Buffering Time(us)
8000 8000
Enabled Enabled
Inserting Status
100 100
Inserting Status
5 5

Table 6-14 Planning information of the service parameters (UNI-NNI CES service between
NE2 and NE3)
Parameter Value
Station NE2 NE3
Service ID 2 2
Level E1 E1
PW ID 2 2
Transmission System
362
Parameter Value
Port
21 21
Port
21 21
RTP Header Disabled Disabled
Jitter Compensation
Buffering Time(us)
8000 8000
Enabled Enabled
Inserting Status
100 100
Inserting Status
5 5

----End
6.5 Verifying CES Services
After configuring CES services, you need to test connectivity of end-to-end CES services to
ensure that they work properly.
Prerequisites
l CES services must be configured as required. For details, see "Configuring CES Services"
in the Configuration Guide (Packet Transport Domain).
BER tester or SDH analyzer, the U2000
Transmission System
363
Figure 6-7 shows the connection diagram for testing connectivity of CES service. You can
replace the BER tester with a SDH analyzer.
Figure 6-7 Connection diagram for testing connectivity of CES services
Inloop
NE1 NE2
Packet
domain
DDF
BER tester

CAUTION
l Only commissioning engineers are present during the test.
l Do not touch the cable, unless necessary.
Procedure
Step 1 As shown in Figure 6-7, connect the CES service interface on NE1 to the BER tester.
Step 2 Perform an inloop for the UNI that receives CES services on NE2 on the U2000.
1. In the Main Topology of the U2000, right-click the required NE and then choose NE
Explorer from the shortcut menu. The NE Explorer window is displayed.
2. Select the board that provides CES services.
3. In the Function Tree, select the type of the interface that receives the CES services.
If an E1 interface receives the CES services, choose Configuration > Packet
Configuration > Interface Management > PDH Interface from the Function Tree.
4. Click the Advanced Attributes tab and then select the interface to perform a loopback.
5. Right-click the Loopback Mode field, and then choose Inloop from the shortcut menu.
6. Click Apply.
Step 3 Perform a 24-hour bit error test.
Transmission System
364
NOTE
Set the coding to HDB3 and pseudo-random binary sequence (PRBS) to 2
15
-1 for the signals transmitted
by the BER tester.
Set the BER tester according to the encapsulation method that the CES services adopt and the frame format
that the E1 interface adopts.
l If the CES services adopt the SATop method, you need to enable the BER tester to transmit unframed
signals, double-frame signals, or CRC-4 multiframe signals.
l If the CES services adopt the CESoPSN method and the interface adopts the double-frame format, you
need to enable the BER tester to transmit double-frame signals.
l If the CES services adopt the CESoPSN method and the interface adopts the CRC-4 multiframe format,
you need to enable the BER tester to transmit CRC-4 multiframe signals.
Step 4 Test the performance of the CES services. That is, check whether bit errors occur in the CES
services in the 24-hour period.
Step 5 Check for the alarms associated with the CES services. If there is any, see the Alarms and
Performance Events Reference and Troubleshooting to clear the alarms.
Step 6 Repeat Step 3 to Step 4 to perform the 24-hour bit error test again.
Step 7 Release the inloop that is set on the interface on NE2. For details, see Step 2.
Step 8 Reconnect the cable to the CES service interface on NE1.
Step 9 Repeat Step 1 to Step 8 to test the CES services on all the other 2 Mbit/s interfaces on NE1 and
NE2.
Step 10 Repeat Step 1 to Step 9 to test connectivity of the CES services on the other NEs.
----End
Transmission System
365
7 Configuring ATM PWE3 Services
About This Chapter
This topic describes the basic concepts of ATM services and tasks an example to describe how
to configure ATM services.
7.1 Basic Concepts
This topic describes the basic concepts of ATM services.
This chapter describes the procedure for configuring ATM services.
7.3 QoS Configuration Case of ATM Services
Configure an ATM policy and use the ATM policy for a specified ATM service. In this way,
the QoS for the ATM service is ensured. In addition, the tunnel QoS can be configured to control
the tunnel bandwidth of service flow.
7.4 Configuration Example of the UNI-UNI ATM Service
This section describes a configuration case of the UNI-UNI ATM service. The configuration
flow diagram is provided to describe the configuration process. The configuration case includes
service planning and ATM service configuration.
7.5 Configuration Example of the UNI-NNI ATM Service
This section describes a configuration example of the UNI-NNI ATM service. The configuration
flow diagram is provided to describe the configuration process. The configuration example
includes service planning and ATM service configuration.
7.6 Verifying ATM/IMA Services
Use the ATM OAM function to test the connectivity of UNI-NNI ATM/IMA services in order
to ensure that ATM/IMA services are normal.
Transmission System
Configuration Guide (Packet Transport Domain) 7 Configuring ATM PWE3 Services
366
7.1 Basic Concepts
This topic describes the basic concepts of ATM services.
7.1.1 ATM Service
This section provides the definition of ATM PWE3 and describes its purpose.
Definition
The ATM PWE3 technology emulates the basic behaviors and characteristics of ATM services
on a packet switched network (PSN) by using the PWE3 mechanism, so that the emulated ATM
services can be transmitted on a PSN.
Purpose
Aided by the ATM PWE3 technology, conventional ATM networks can be connected by a PSN.
Specifically, ATM PWE3 allows transmitting conventional ATM services over a PSN by
emulating the ATM services.
The networking type of ATM PWE3 can be one-to-one or N-to-one depending on the
encapsulation type of ATM PWE3 packets. It is obvious that ATM PWE3 helps to transmit
ATM services over the PSN, without adding ATM equipment or changing the configuration of
the ATM CE equipment.
Figure 7-1 Typical application of ATM PWE3 (in the one-to-one encapsulation mode)
PSN
PE1 PE2
1-to-1 ATM
PWE3
service
ATM PWE3
LSP
PW
AC
AC
CE2 CE1
NodeB
RNC
1-to-1 ATM
PWE3
service

Transmission System
367
Figure 7-2 Typical application of ATM PWE3 (in the N-to-one encapsulation mode)
PSN
PE1 PE2
N-to-1 ATM
PWE3
service
ATM PWE3
LSP
PW
AC
AC
CE4 CE2
CE1
CE3
NodeB
RNC
N-to-1 ATM
PWE3
service

NOTE
The cell encapsulation modes at both ends of a PW must be the same.
7.1.2 ATM Traffic
This section provides the definition of ATM traffic management and describes its purpose.
Definition
ATM traffic management is a mechanism provided by the ATM network. With the mechanism,
an ATM network assures services of expected QoS objectives such as amount of bandwidth,
delay, delay variation, and packet loss ratio in whatever situations, so that users can know the
expected service level.
The equipment can provide ATM services with ensured quality levels by applying ATM traffic
control policies.
Purpose
ATM traffic management aims to prevent occurrence of congestion in ATM services and
improve utilization of resources.
If ATM services are transmitted in PWE3 mode, service policies with appropriate priorities can
be provided for various categories of ATM services carried by VPCs or VCCs before the ATM
cells are encapsulated into PW packets. As shown in Figure 7-3, ATM traffic management
generally functions in the ingress direction of a UNI on a PE.
Transmission System
368
Figure 7-3 Functioning point of ATM traffic management
PSN
Functioning point of
ATM traffic control
CE PE
Ingress ATM cells
This chapter describes the procedure for configuring ATM services.
7.2.1 Configuration Flow for UNI-UNI ATM Services
This topic describes the operation tasks for configuring UNI-UNI ATM services and the
relationships between the operations tasks.
Table 7-1 provides the process for configuring UNI-UNI ATM services.
Figure 7-4 Configuration flow for UNI-UNI ATM services
2. Configure the ATM
Policy
Interface
Required
1.Creating Network
Start
End
4. Configure the UNI-
UNI ATM Service

Transmission System
369
Table 7-1 Tasks for configuring the UNI-UNI ATM service
Ste
p
Operation Remarks
1 2 Creating the
Network
Create NEs, configure NE data, create optical fibers, and configure
clocks.
2 8.5.3
Creating the
ATM Policy
The ATM policy is used for traffic management of the ATM service.
3 8.5.1
Configuring
ATM
Interfaces
The ATM interface accesses services from NodeB.
4 Configure the
UNI-UNI
ATM Service
Specify the service ID and service name, and select the source and
sink.

7.2.2 Configuration Procedure (UNI-NNI ATM Services)
This section describes the operation tasks for configuring UNI-NNI ATM services and the
relationships between the operations tasks.
Table 7-2 describes the procedure for configuring UNI-NNI ATM services.
Transmission System
370
Figure 7-5 Flow chart for configuring UNI-NNI ATM services
2. Configure the LSR ID.
3. Configure the NNI port.
Required
1. Create a network.
Start
End
4. Configure the MPLS
tunnel.
Optional
5. Set the basic attributes of
Smart E1 ports.
6. Bind ports to the ATM
trunk.
7. Configure an IMA group.
8. Configure management of
ATM ports.
policy.
10. Create a DS domain.
11. Create ATM services.

Transmission System
371
Table 7-2 Procedure for configuring UNI-NNI ATM services
St
e
p
Operation Remarks
1 2 Creating the Network Create NEs, configure NE data, create
optical fibers, and configure clocks.
2 8.8.1 Configuring LSR ID Set the LSR ID and the start of the global
label space.
3 Configuring NNI ports Set basic attributes and Layer 3 attributes
(including the tunnel enabled status and IP
address) for carrying tunnels.
4 Configuri
ng MPLS
tunnels
Tunnel
An MPLS tunnel can be configured in per-
NE or end-to-end mode. Set tunnel ID,
service name, ingress node, egress node, and
transit node; set signaling type to static.
Configuri
ng tunnel
OAM
NOTE
Configur
e MPLS
tunnel
OAM or
MPLS-
TP
tunnel
OAM
accordin
g to the
service
plan.
8.10
Configuring
MPLS
Tunnel OAM
Optional. To ensure protection switching
time within 50 ms, set Detection Packet
Type to FFD and Detection Packet
Interval (ms) to 3.3. Set the following
parameters:
3.3.
Transmission System
372
St
e
p
Operation Remarks
8.11
Configuring
MPLS-TP
Tunnel OAM
MEG ID Type to IP Based, so that you
do not need to plan MEG IDs, MEP IDs,
and RMEP IDs.
l If not all the NEs along a tunnel are
based MPLS-TP OAM or if there are
special requirements, it is recommended
that you set MEG ID Type to ICC
Based. In this case, plan MEG IDs, MEP
IDs, and RMEP IDs based on the
following principles:
All the MEPs and MIPs along the
same tunnel must have the same MEG
ID. MEPs and MIPs along different
tunnels must have different MEG IDs.
unique.
Detection Mode can be set only for
ingress nodes on bidirectional tunnels
and egress nodes.
l To suppress a PW fault alarm caused by
a tunnel fault on an NE on which an MS-
PW is configured, set AIS Status to
Enabled.
Transmission System
373
St
e
p
Operation Remarks
Interval(ms) to a value greater than
the packet transmission delay
variation.
tunnel connectivity, it is
Interval(ms) to 1000.
and ingress nodes.
l It is recommended that you set CC
Packet Priority to the default value
7.CC Packet Priority can be set only for
egress nodes on bidirectional tunnels and
ingress nodes.
APS
Optional. Set the parameters of MPLS tunnel
APS according to the service planning.
NOTE
Tunnel APS is not used, select PW APS for
service protection. For the configuration of PW
APS, see Configuring PW APS.
5 8.3.1 Setting Basic Attributes of Smart
E1 Ports
Required for ATM/IMA E1 ports. Set Port
Mode to Layer 2.
Required for fractional ATM/IMA ports.
1. Create serial ports.
2. Set basic attributes of the serial ports. Set
Port Mode to Layer 1.
6 8.6.1 Binding ATM TRUNKs Bind corresponding ports to ATM trunks.
l For fractional ATM/IMA ports, serial
ports need to be bound to ATM trunks.
l For ATM/IMA E1 ports, E1 ports need to
be bound to ATM trunks.
Transmission System
374
St
e
p
Operation Remarks
7 8.6.2 Configuring an IMA group l For ATM E1 or fractional ATM services,
set IMA Protocol Enable Status to
Disabled.
l For IMA E1 or fractional IMA services,
set IMA Protocol Enable Status to
Enabled. It is recommended that the
other parameters take their default
values. If otherwise specified, set the
other parameters based on requirements
of the equipment.
8 Configuring management of ATM
ports
Optional.
It is recommended that Port Type and ATM
Cell Payload Scrambling take their default
values. If otherwise specified, set Port
Type and ATM Cell Payload Scrambling
according to requirements of the equipment.
9 8.5.3 Creating the ATM Policy The ATM policy is configured for ATM
traffic management.
10 Creating an ATM-DiffServ Domain Optional.
Set parameters according to the service
11 Creating ATM services 1. Create ATM services; that is, set Service
ID, Service Name, and select Service
Type and Connection Type.
2. Configure ATM connections; that is, set
the source information, PW ID, sink
information, and policies.
3. Configure PWs; that is, set information
such as the PW type, PW label, and tunnel
type.
4. Configure CoS mappings; that is, set the
CoS policy for PWs.

7.3 QoS Configuration Case of ATM Services
Configure an ATM policy and use the ATM policy for a specified ATM service. In this way,
the QoS for the ATM service is ensured. In addition, the tunnel QoS can be configured to control
the tunnel bandwidth of service flow.
Transmission System
375
7.3.1 Case Description
This section describes the networking and data planning of this case.
As shown in Figure 7-6, the OptiX OSN access equipment has IMA connections to two NodeBs
through E1 ports, and receives ATM services from these NodeBs. The OpitX OSN access
equipment first encapsulates the incoming ATM services into PWE3 packets, and transports the
packets to the opposite OpitX OSN convergence equipment over a PSN. When receiving the
packets, the opposite OpitX OSN convergence equipment decapsulates the packets, and
transports the ATM services to the RNC through STM-1 optical interfaces.
Each NodeB transports services such as real-time voice services, signals, and data services. To
ensure QoS for different service types, the OptiX OSN equipment specifies different ATM
policies for different service types, and uses different PWs to carry these services of various
types.
Figure 7-6 Networking diagram for the QoS configuration of ATM services
Working Tunnel
NodeB 1
RNC
NE1
NE2
NE3
NE4
NE5
NE6
GE ring on
access layer
10 GE ring
on
convergence
layer
NodeB 2
pw1
pw3
pw2
IMA1
IMA2
ATM
STM-1
UNI NNI
VPI
1
VCI
100
1 101
1 R99
2 HSDPA
VPI
50
VCI
32
51 32
3 1 102
52 32
UNI
VPI
50
VCI
32
51 32
52 32
IMA1:
UNI NNI
VPI
1
VCI
100
1 101
1 R99
2 HSDPA
VPI
60
VCI
32
61 32
3 1 102
62 32
UNI
VPI
60
VCI
32
61 32
62 32
IMA2:
NNI
VPI
50
VCI
32
51 32
52 32
NNI
VPI
60
VCI
32
61 32
62 32
PW
Protection Tunnel

Figure 7-6 lists the service types of IMA traffic and QoS requirements.
Transmission System
376
Table 7-3 Service types and QoS requirements
Application Scenario ATM Policy PW
Bandw
idth
Tunnel Bandwidth
Voice service, which is
carried by the RT-VBR
type.
l Policy ID: 1
l Policy name: RT-
VBR
l Service type: RT-
VBR
l Traffic type:
ClpNoTag-
gingScrCdvt
l Clp01Pcr(cell/s):
4000
l Clp0Scr(cell/s): 1000
l MBS(cell): 100
l CDVT(us): 10000
l Enable Traffic Frame
Discarding Flag:
Disable
l UPC/NPC: Disable
Bandwi
dth: 4
Mbit/s
30 Mbit/s
Signaling service, which
is carried by the CBR
type.
l Policy ID: 2
l Policy name: CBR
l Service type: CBR
l Traffic type:
NoClpNoScr
l Clp01Pcr(cell/s): 800
Discarding Flag:
Disable
l UPC/NPC: Disable
Bandwi
dth: 1
Mbit/s
30 Mbit/s
Data service, which is
carried by the UBR type.
l Policy ID: 3
l Policy name: UBR
l Service type: UBR
l Traffic type:
NoTrafficDescriptor
Discarding Flag:
Disable
l UPC/NPC: Disabled
Bandwi
dth: 15
Mbit/s
30 Mbit/s

Transmission System
377
This section describes the configuration process for this example. The configuration steps
include ATM policy configuration and application.
Prerequisites
l Be aware of the networking and data planning of the example.
Procedure
Step 1 Configure the RT-VBR policy.
1. In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > QoS
Management > Policy Management > ATM Policy.
2. Click New, and set the parameters in the Create ATM Policy dialog box. Click OK.
Set the parameters for the RT-VBR policy as follows:
l Policy ID: 1
l Policy name: RT-VBR
l Service type: RT-VBR (Select the service type based on the type of incoming service.
Specifically, the voice service corresponds to RT-VBR, which is of the highest service
priority.)
l Traffic type: ClpNoTaggingScrCdvt (This parameter indicates that the two-level bucket
is valid. At one level, CLP01 is processed based on Clp01Pcr, and improper cells are
discarded. At the other level, CLP0 is processed based on Clp0Scr, and improper cells
are discarded.)
l Clp01Pcr(cell/s): 4000 (This parameter indicates the maximum permitted rate at which
cells are transmitted. Set the parameter based on the service rate.)
l Clp0Scr(cell/s): 1000 (This parameter indicates the sustainable cell rate at which cells
are transmitted. Set the parameter based on the service rate.)
l MBS(cell): 100 (This parameter indicates the maximum number of burst cells tolerated
by the equipment after the traffic exceeds Clp01Pcr.)
l CDVT(us): 10000 (This parameter indicates the capability of tolerating burst ATM
cells. When a cell arrives later than it is expected, the cell bursts. The burst volume is
measured by the time difference between the actual arrival time and expected arrival
time. If the burst volume of multiple consecutive cells exceeds the CDVT, the equipment
discards the improper cells. Set the parameter to a large value, when possible, to
minimize the number of lost packets.)
l Enable Traffic Frame Discarding: Disabled (The service encapsulated in AAL5 is sliced
into cells. This parameter specifies whether to discard cells or to discard the complete
AAL5 frames for the cells.)
l UPC/NPC: Enable (UPC and NPC stand for user parameter control and network
parameter control respectively. The bucket algorithm is based on the content of UPC/
NPC. UPC/NPC is intended to monitor the cells received by the equipment based on
the specified traffic parameters, and therefore to avoid network congestion. The Scr,
Transmission System
378
Pcr, MBS, and CDVT bucket parameters are functional only when UPC/NPC is enabled
for the ATM policy.)
3. Click OK.
Step 2 Configure the CBR policy.
Management > Policy Management > ATM Policy in the Function Tree.
2. Click New, set the parameters in the Create ATM Policy dialog box. Click OK.
Set the parameters for the CBR policy as follows:
l Policy ID: 2
l Policy name: CBR
l Service type: CBR (Select the service type based on the type of incoming service.
Specifically, the signal service corresponds to the CBR service, which is of the highest
service priority.)
l Traffic Type: NoClpNoScr (The bucket at the first level takes effect, processes the cells
with the Clp01 flags based on Clp01Pcr, and discards the cells without the Clp01 flags.)
l Clp01Pcr(cell/s): 800
l Enable Traffic Frame Discarding: Disabled
l UPC/NPC: Enable
3. Click OK.
Step 3 Configure the UBR policy.
Management > Policy Management > ATM Policy in the Function Tree.
2. Click New, and set the parameters in the Create ATM Policy dialog box. Click OK.
Set the parameters for the UBR policy as follows:
l Policy ID: 3
l Policy name: UBR (Select the service type based on the type of incoming service.
Specifically, the data service corresponds to the UBR service, which is of the lowest
service priority.)
l Service type: UBR (No QoS is ensured for the accessed service. In the case of network
congestion, the UBR cells are discarded at the earliest.)
l Traffic type: UBR (No QoS is ensured for the accessed service. In the case of network
congestion, the UBR cells are discarded at the earliest.)
l Enable Traffic Frame Discarding: Disabled
l UPC/NPC: Disabled
3. Click OK.
Step 4 Configure the ATM service.
When creating an ATM service, do as follows.
l Configure the ATM connection.
Specify the uplink and downlink ATM policy, that is, Policy 1(RT-VBR), for the ATM
connections that carry the voice services.
Transmission System
379
Specify the uplink and downlink ATM policy, that is, Policy 2(CBR), for the ATM
connections that carry the signal services.
Specify the uplink and downlink ATM policy, that is, Policy 3(UBR), for the ATM
connections that carry the data services.
l Configure the PW.
Specify the bandwidth for the PW in the QoS tab.
The bandwidth of PW 1 (corresponding to RT-VBR service type) is 4 Mbit/s.
The bandwidth of PW 2 (corresponding to CBR service type) is 1 Mbit/s.
The bandwidth of PW 3 (corresponding to UBR service type) is 15 Mbit/s.
l Configure the ATM CoS mapping relation.
Specify the ATM CoS mapping the ATM service. The mapping ID is 1 and the mapping
name is DefaultAtmCosMap.
NOTE
DefaultAtmCosMap is the default ATM CoS mapping table of the equipment and cannot be deleted. In this
example, the default CoS mapping table is used. The user can also create an ATM CoS mapping table as
required. For details on how to create an ATM CoS mapping table, see 8.5.2 Configuring ATM CoS
Mapping.
NOTE
For the ATM service configuration method, see 7.5 Configuration Example of the UNI-NNI ATM Service.
----End
7.4 Configuration Example of the UNI-UNI ATM Service
This section describes a configuration case of the UNI-UNI ATM service. The configuration
flow diagram is provided to describe the configuration process. The configuration case includes
service planning and ATM service configuration.
This section describes the networking diagram for the case where the R99 service, Signaling
service and HSDPA service are transported between NodeB1 and RNC, NodeB2 and RNC.
The networking diagram of UNI-UNI ATM services is shown in Figure 7-7. ATM services need
to be transmitted between the NodeB and the RNC. Connection 1 is used for transmitting R99
services, Connection 2 is used for transmitting HSDPA services, and Connection 3 is used for
transmitting signaling services. The NodeB transmits services to the RNC through NE1; NE1
uses the OptiX OSN equipment to receives services from the NodeB and transmit the services
to the RNC over three E1 links.
Transmission System
380
Figure 7-7 Networking of the ATM service
UNI UNI
IMA 1
VPI
1
VCI
100
1 101
Connection 1 R99
Connection 2 HSDPA
VPI
2
VCI
32
2 33
Node B NE 1 RNC
IMA 2

Figure 7-8 NE planning diagram
UNI UNI
IMA 1
Node B NE 1 RNC
3-MD1 4-MD1
IMA 2

To transport the R99, Signaling and HSDPA services between NodeB and RNC, three ATM
connections should be created.
Node B accesses the ATM service through IMA1, and then transmits the service to RNC. three
services that are connected to the N:1 VCC service should be created. Figure 7-7 shows the
VPI/VCI switching. The service shown in Figure 7-7 is taken as an example.
Table 7-4 lists the configuration parameters of NE1.
Table 7-4 Configuration parameters of NE1
Attribute Remarks
Base Station of Service NodeB
IMA Group IMA1
Port Accessing the IMA Group at NodeB NE1-3-MD1-1
Port Connected to RNC NE1-4-MD1-1
Transmission System
381
Attribute Remarks
Conn
ection
1
Source VPI(example:35,36-39)/VCI
(example:35,36-39)
1/100
Sink VPI(example:35,36-39)/VCI
(example:35,36-39)
2/32
Conn
ection
2
(example:35,36-39)
1/101
(example:35,36-39)
2/33
Conn
ection
3
(example:35,36-39)
1/102
(example:35,36-39)
2/34

Table 7-5 lists the configuration parameters of Qos.
Table 7-5 Service types and QoS requirements
Application
Scenario
ATM Policy PW Bandwidth Tunnel Bandwidth
Audio service, which
is carried by the RT-
VBR type.
l Policy ID: 1
l Policy name: RT-
VBR
l Service type: RT-
VBR
l Traffic type:
ClpNoTag-
gingScrCdvt
l Clp01Pcr(cell/s):
4000
l Clp0Scr(cell/s):
1000
l MBS(cell): 100
l CDVT(us):
10000
l Enable Traffic
Frame
Discarding Flag:
Disable
l UPC/NPC:
Disable
Bandwidth: 4 Mbit/s 30 Mbit/s
Transmission System
382
Application
Scenario
ATM Policy PW Bandwidth Tunnel Bandwidth
Signal service, which
is carried by the CBR
type.
l Policy ID: 2
l Policy name:
CBR
l Service type:
CBR
l Traffic type:
NoClpNoScr
l Clp01Pcr(cell/s):
800
l Enable Traffic
Frame
Discarding Flag:
Disable
l UPC/NPC:
Disable
Bandwidth: 1 Mbit/s
Data service, which
is carried by the UBR
type.
l Policy ID: 3
l Policy name:
UBR
l Service type:
UBR
l Traffic type:
NoTrafficDe-
scriptor
l Enable Traffic
Frame
Discarding Flag:
Disable
l UPC/NPC:
Disable
Bandwidth: 15
Mbit/s

7.4.3 Configuration Process in Per-NE Mode
This section describes the process of configuring a UNI-UNI ATM service on a per-NE basis.
Prerequisites
l You must understand the networking, requirements and service planning of the example.
l A network must be created.
Transmission System
383
Procedure
Step 1 Configure three ATM policies: CBR, RT-VBR, UBR.
1. Configure the CBR policy, refer to Step 2 of the QoS Configuration Case of ATM Services.
2. Configure the RT-VBR policy, refer to Step 1 of the QoS Configuration Case of ATM
Services.
3. Configure the UBR policy, refer to Step 3 of the QoS Configuration Case of ATM Services.
Step 2 Configure ATM interface: NodeB-side ATM interface and RNC-side ATM interface.
1. Configure the NodeB-side ATM interface.
a. In the NE Explorer, select NE1 and choose Configuration > Packet
Then, configure the NodeB-side interface.
b. Select 3-MD1-1(PORT-1). Right click the Port Mode field, and select Layer 2. Set
the parameters as required, and click Apply.
NOTE
Before setting the port mode, make sure that the port DCN is disabled.
The configuration parameters are as follows:
l Port: 3-MD1-1(PORT-1)
l Name: NodeB ATM (Set the port name as required. The port name distinguishes
the port from other ports and helps to query the port.)
l Port Mode: Layer 2 (The port transmits IMA signals.)
l Encapsulation: ATM (Default)
c. In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 3-
MD1-1(PORT-1). Click Apply.
l Port: 3-MD1-1(PORT-1)
l Frame Format: CRC-4 Multiframe (Set the Frame Format as the same as the
parameter of NodeB.)
l Frame Mode: 31
d. Choose Configuration > Packet Configuration > Interface Management > ATM
IMA Management from Function Tree, and click the Binding tab.
e. In the Binding tab, click Configuration and set the parameters such as Available
Boards, Configuration Ports. Then, click OK.
l Available Boards: 3-MD1 (Set this parameter according to networking planning.)
l Configuration Ports: 3-MD1-1(PORT-1) (Set this parameter according to
networking planning.)
l Available Bound Paths
Level: E1 (Select E1 for an ATM E1 board and VC12-xv for an ATM STM-1
board. Herein, the board is an ATM E1 board.)
Direction: Bidirectional (Default)
Transmission System
384
Optical Interface: - (This parameter need not be set for E1, but need be set for
VC12-xv. Herein, the path level is E1.)
l Available Resources: 3-MD1-1(PORT-1)
l Available Timeslots: - (This parameter need not be set for E1, but need be set for
VC12-xv.)
f. In the IMA Group Management tab, double-click the IMA Protocol Enable
Status field and select Enabled. Set the other parameters as required. Then, click
Apply.
Set the IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry
Mode, Maximum Delay Between Links, Minimum Number of Active
Transmitting Links, and Minimum Number of Active Receiving Links parameters
as the same as these parameters of NodeB.
g. In the ATM Interface Management tab, set the parameters such as Max. VPI and
Max. VCI for the interface. Then, click Apply.
l Port Type: UNI (A UNI interface is connected to the client equipment and an NNI
interface is connected to ATM equipment in the core network.)
l ATM Cell Payload Scrambling: Enabled
l Max. VPI: 255 (Set this parameter according to networking planning. Set Max.
VPI to specify the value range of VPI. The VPI ranges from 0 to Max. VPI.)
l Max. VCI: 65535 (Set this parameter according to networking planning. Set Max.
VCI to specify the value range of VCI. The VCI ranges from 32 to Max. VCI.)
l VCC-Supported VPI Count: 32 (Set this parameter according to networking
planning.)
l Loopback: Non-Loopback
2. Configure the RNC-side ATM ports in the same manner.
Step 3 Configure a UNI-UNI ATM service.
1. Choose Configuration > Packet Configuration > ATM Service Management from the
Function Tree.
2. In the Connection tab, click New. The New ATM Service window is displayed. In the
window, configure a UNI-UNI service.
l Service ID: 10
l Service Name: ATMService-10
l Service Type: UNI-UNI
l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection
can be modified; PVP indicates that only the VPI of the ATM connection can be
modified.)
3. Click the Connection tab and click Add to add connection 1, connection 2 and connection
3. Then, click OK.
l Connection 1
Transmission System
385
Connection Name: Connection 1
Source Board: 3-MD1
Source Port: 1(Port-1)
Source VPI(example:35,36-39): 1 (the VPI information transmitted with the service
from NodeB)
Source VCI(example:35,36-39): 100 (the VCI information transmitted with the
service from NodeB)
PW ID: -
Sink Board: 4-MD1
Sink Port: 1(PORT-1)
Sink VPI(example:35,36-39): 2 (The VPI information transmitted with the service
after VPI switching. The Sink VPI ranges from 0 to Max. VPI.)
Sink VCI(example:35,36-39): 32 (The VCI information transmitted with the service
after VCI switching. The Sink VCI ranges from 32 to Max. VCI.)
Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99
service.)
Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an
R99 service.)
l Connection 2
Source Board: 3-MD1
Source VPI(example:35,36-39): 1
Source VCI(example:35,36-39): 101
PW ID: -
Sink Board: 4-MD1
Sink VPI(example:35,36-39): 2
Sink VCI(example:35,36-39): 33
Uplink Policy: UBR (Select the UBR policy, because connection 2 is an HSDPA
service.)
Downlink Policy: UBR (Select the UBR policy, because connection 2 is an HSDPA
service.)
l Connection 3
Source Board: 3-MD1
Source VPI(example:35,36-39): 1 (the VPI information transmitted with the service
from NodeB)
Source VCI(example:35,36-39): 102 (the VCI information transmitted with the
service from NodeB)
Transmission System
386
PW ID: -
Sink Board: 4-MD1
Uplink Policy: CBR (Select the CBR policy, because connection 2 is a Signaling
service.)
Downlink Policy: CBR (Select the CBR policy, because connection 2 is a Signaling
service.)
----End
7.5 Configuration Example of the UNI-NNI ATM Service
This section describes a configuration example of the UNI-NNI ATM service. The configuration
flow diagram is provided to describe the configuration process. The configuration example
includes service planning and ATM service configuration.
This section describes the networking diagram for the case where the R99 service, Signaling
service and HSDPA service are transported between NodeB1 and RNC, NodeB2 and RNC.
The networking diagram of UNIs-NNI ATM services is shown in Figure 7-9. The 3G R99
services, signaling services, and HSDPA services need to be transmitted between two base
stations and the RNC. NE1 is interconnected with the MPLS network consisting of Hybrid MSTP
devices. NodeB1 is interconnected with NE1 through IMA1 and NodeB2 is interconnected with
NE1 through IMA2. The VPIs or VCIs are exchanged on NE1 and are transparently transmitted
on NE2 and NE3. Between NE1 and NE3, three PWs are used to carry R99 services, signaling
services, and HSDPA services respectively. By means of the STM-1 connection between NE3
and the RNC, ATM services are transparently transmitted over the MPLS network. NE1 uses
the OptiX OSN access equipment; NEs 2-6 use the OptiX OSN convergence equipment. ATM
services are carried by the working tunnel and a protection tunnel can be created for real-time
ATM services.
The working tunnel is NE1-NE2-NE3, and the protection tunnel is NE1-NE6-NE5-NE4-NE3.
Transmission System
387
Figure 7-9 Networking of the ATM service
Working Tunnel
NodeB 1
RNC
NE1
NE2
NE3
NE4
NE5
NE6
GE ring on
access layer
10GE ring on
convergence
layer
NodeB 2
pw1
pw3
pw2
IMA1
IMA2
ATM
STM-1
UNI NNI
VPI
1
VCI
100
1 101
Connection 1 R99
Connection 2 HSDPA
VPI
50
VCI
32
51 32
Connection 3 Signalling 1 102
52 32
UNI
VPI
50
VCI
32
51 32
52 32
IMA1:
UNI NNI
VPI
1
VCI
100
1 101
VPI
60
VCI
32
61 32
1 102
62 32
UNI
VPI
60
VCI
32
61 32
62 32
IMA2:
NNI
VPI
50
VCI
32
51 32
52 32
NNI
VPI
60
VCI
32
61 32
62 32
PW
Protection Tunnel
Connection 1 R99
Connection 2 HSDPA
Connection 3 Signalling

Figure 7-10 shows the NE planning diagram.
Figure 7-10 NE planning diagram
Working Tunnel
Protection Tunnel
NE1
NE2
NE3
NE4
NE5
NE6
3-EM6F-1(PORT-1)
18.0.0.1
3-PEG8-2(PORT-2)
18.0.0.2
3-EX2-2(PORT-2)
18.0.1.2
4-PEX2-1(PORT-1)
18.0.1.1
32-AFO1-1(PORT-1)
3-PEG8-2(PORT-2)
18.0.4.1
GE ring on
access layer
10GE ring on
convergence
layer
3-EX2-1(PORT-1)
18.0.2.1
3-PEX2-2(PORT-2)
18.0.2.2
3-PEX2-1(PORT-1)
18.0.3.1
4-PEX2-2(PORT-2)
18.0.3.2
3-PEG8-1(PORT-1)
18.0.4.2
3-PEG8-1(PORT-1)
18.0.5.2
3-EM6F-2(PORT-2)
18.0.5.1
RNC
NodeB 1
NodeB 2
4-MD1

Transmission System
388
To transport the R99, Signaling and HSDPA services between NodeB1 and RNC, NodeB2 and
RNC respectively, three ATM services must be created.
Between NE1 and NE3, the R99 service is carried by PW1, the HSDPA service is carried by
PW2, and the Signaling service is carried by PW3. Therefore, three ATM services should be
created. At the two base stations, the R99 service is aggregated and the Signaling service and
HSDPA service is accessed. Therefore, two ATM services connected to the N:1 VCC should be
created. The service shown in Figure 7-9 is taken as an example.
Table 7-6 Configuration parameters of NEs
NE LSR ID Port Port IP Address IP Mask
NE1 130.0.0.1 3-EM6F-1
(PORT-1)
18.0.0.1 255.255.255.252
3-EM6F-2
(PORT-2)
18.0.5.1 255.255.255.252
NE2 130.0.0.2 4-PEX2-1
(PORT-1)
18.0.1.1 255.255.255.252
3-PEG8-2
(PORT-2)
18.0.0.2 255.255.255.252
NE3 130.0.0.3 3-EX2-1
(PORT-1)
18.0.2.1 255.255.255.252
3-EX2-2
(PORT-2)
18.0.1.2 255.255.255.252
NE4 130.0.0.4 3-PEX2-2
(PORT-2)
18.0.2.2 255.255.255.252
3-PEX2-1
(PORT-1)
18.0.3.1 255.255.255.252
NE5 130.0.0.5 4-PEX2-2
(PORT-2)
18.0.3.2 255.255.255.252
3-PEG8-1
(PORT-1)
18.0.4.2 255.255.255.252
NE6 130.0.0.6 3-PEG8-2
(PORT-2)
18.0.4.1 255.255.255.252
3-PEG8-1
(PORT-1)
18.0.5.2 255.255.255.252

Transmission System
389
Table 7-7 Planning of Tunnel parameters
Parameters Working Tunnel Protection Tunnel
Tunnel ID 100 101 120 121
Name Working
Tunnel-Positive
Working
Tunnel-Reverse
Protection
Tunnel-Positive
Protection
Tunnel-Reverse
Signal Type Static Static Static Static
Scheduling
Type
E-LSP E-LSP E-LSP E-LSP
Bandwidth
(Kbit/s)
No Limit No Limit No Limit No Limit
Ingress Node NE1 NE3 NE1 NE3
Transit Node NE2 NE2 NE6, NE5, NE4 NE4, NE5, NE6
Egress Node NE3 NE1 NE3 NE1
Ingress Node
Route
Information
NE1
l Out Port: 3-
EM6F-1
(PORT-1)
l Out Label:
20
NE3
l Out Port: 3-
EX2-2
(PORT-2)
l Out Label:
21
NE1
l Out Port: 3-
EM6F-2
(PORT-2)
l Out Label:
22
NE3
l Out Port: 3-
EX2-1
(PORT-1)
l Out Label:
23
Transmission System
390
Parameters Working Tunnel Protection Tunnel
Transit Node
Route
Information
NE2
l In Port: 3-
PEG8-2
(PORT-2)
l In Label: 20
l Out Port: 4-
PEX2-1
(PORT-1)
l Out Label:
30
NE2
l In Port: 4-
PEX2-1
(PORT-1)
l In Label: 21
l Out Port: 3-
PEG8-2
(PORT-2)
l Out Label:
31
NE6
l In Port: 3-
PEG8-1
(PORT-1)
l In Label: 22
l Out Port: 3-
PEG8-2
(PORT-2)
l Out Label:
32
NE5
l In Port: 3-
PEG8-1
(PORT-1)
l In Label: 32
l Out Port: 4-
PEX2-2
(PORT-2)
l Out Label:
42
NE4
l In Port: 3-
PEX2-1
(PORT-1)
l In Label: 42
l Out Port: 3-
PEX2-2
(PORT-2)
l Out Label:
52
NE4
l In Port: 3-
PEX2-2
(PORT-2)
l In Label: 23
l Out Port: 3-
PEX2-1
(PORT-1)
l Out Label:
33
NE5
l In Port: 4-
PEX2-2
(PORT-2)
l In Label: 33
l Out Port: 3-
PEG8-1
(PORT-1)
l Out Label:
43
NE6
l In Port: 3-
PEG8-2
(PORT-2)
l In Label: 43
l Out Port: 3-
PEG8-1
(PORT-1)
l Out Label:
53
Egress Node
Route
Information
NE3
l In Port: 3-
EX2-2
(PORT-2)
l In Label: 30
NE1
l In Port: 3-
EM6F-1
(PORT-1)
l In Label: 31
NE3
l In Port: 3-
EX2-1
(PORT-1)
l In Label: 52
NE1
l In Port: 3-
EM6F-2
(PORT-2)
l In Label: 53

Transmission System
391
Attribute Remarks
Base
Station of
Service
NodeB1 NodeB2
IMA
Group
IMA1 IMA2
Source
Port
4-MD1-1(Port-1) 4-MD1-2(Port-2)
Service R99 HSDPA Signaling R99 HSDPA Signaling
Source
VPI/VCI
1/100 1/101 1/102 1/100 1/101 1/102
Sink VPI/
VCI
50/32 51/32 52/32 60/32 61/32 62/32
PW of
Service
PW1 PW2 PW3 PW1 PW2 PW3
PW ID 35 36 37 35 36 37

Attribute Remarks Remarks
Service R99 HSDPA Signaling R99 HSDPA Signaling
Source
VPI/VCI
50/32 51/32 52/32 60/32 61/32 62/32
Sink VPI/
VCI
50/32 51/32 52/32 60/32 61/32 62/32
PW of
Service
PW1 PW2 PW3 PW1 PW2 PW3
PW ID 35 36 37 35 36 37
Sink Port 32-N1AFO1-1(PORT-1)

7.5.3 Configuration Process in End-to-End Mode
This topic describes how to configure an ATM emulation service.
Transmission System
392
Prerequisites
l You must learn about the networking requirements and service planning described in the
example.
l A network must be created and Allocate IP addresses to ports automatically.
Procedure
Step 1 Set LSR IDs.
1. In the NE Explorer, select NE1 and choose Configuration > Packet Configuration >
MPLS Management > Basic Configuration from the Function Tree.
2. Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.
Parameter Example Value Principle for Value
Selection
LSR ID NE1: 130.0.0.1 Set this parameter
according to the network
planning. In addition, this
value is unique on the entire
network.
Start of Global Label Space 0 Set this parameter
planning.

3. Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the
preceding two steps to set the parameters, such as LSR ID.
Selection
LSR ID NE2: 130.0.0.2
NE3: 130.0.0.3
NE4: 130.0.0.4
NE5: 130.0.0.5
NE6: 130.0.0.6
Set this parameter
network.
planning.

Step 2 Create the working tunnel.
1. Choose Service > Tunnel > Create Tunnel from the main menu.
2. Set the basic information about the working tunnel.
Transmission System
393
Selection
Tunnel Name Working Tunnel Set this parameter
according to the service
planning.
Protocol Type MPLS Set this parameter
planning.
Signaling Type Static CR Set this parameter
planning.
Service Direction Unidirectional Set this parameter
planning.
Create Reverse Tunnel Selected This parameter is selected
when a reverse tunnel needs
to be created.
Protection Type 1:1 Set this parameter
planning.
Switching Mode Double-Ended Set this parameter
planning.

3. Configure the NE list. On the physical topology, double-click NE1, NE2, and NE3 to add
them to the NE list and set the corresponding NE roles.
Selection
NE2: Transit
NE3: Egress
An ingress is the incoming
node of a network. In this
example, NE1 is an ingress
node.
A transit is a pass-through
node. In this example, NE2
is a transit node.
An egress is the outgoing
example, NE3 is an egress
node.
Transmission System
394
Selection
Deploy Selected When this parameter is
selected, a tunnel is saved
on the U2000 and applied to
the corresponding NEs.
Enable Selected When this parameter is
selected, during tunnel
deployment, the tunnel is
automatically enabled.

4. Click Details to set the advanced parameters of the reverse tunnel. Click OK.
Selection
Tunnel ID l Forward Tunnel: 100
l Reverse Tunnel: 101
Set this parameter
planning.
CIR (Kbit/s) Forward and Reverse
Tunnels: 10000
Set this parameter
planning.
CBS (byte) Forward and Reverse
Tunnels: 10000
Set this parameter
planning.
PIR (Kbit/s) Forward and Reverse
Tunnels: 20000
Set this parameter
planning.
PBS (byte) Forward and Reverse
Tunnels: 20000
Set this parameter
planning.
MTU (bytes) Forward and Reverse
Tunnels: 1620
Set this parameter
planning.
LSP Type Forward and Reverse
Tunnels: E-LSP
Set this parameter
planning.
EXP Forward and Reverse
Tunnels: None
Set this parameter
planning.
Transmission System
395
Selection
l NE1: 3-EM6F-1
(PORT-1)
l NE2: 4-PEX2-1
(PORT-1)
Reverse Tunnel:
l NE3: 3-EX2-2
(PORT-2)
l NE2: 3-PEG8-2
(PORT-2)
Set this parameter
planning. Only this
parameter needs to be set
for only the ingress node
and transit node.
l NE1: 20
l NE2: 30
Forward Tunnel:
l NE3: 21
l NE2: 31
Set this parameter
planning.
l NE2: 3-PEG8-2
(PORT-2)
l NE3: 3-EX2-2
(PORT-2)
Reverse Tunnel:
l NE2: 4-PEX2-1
(PORT-1)
l NE1: 3-EM6F-1
(PORT-1)
Set this parameter
planning. Only this
for only the egress node and
transit node.
l NE2: 20
l NE3: 30
Reverse Tunnel:
l NE2: 21
l NE1: 31
Set this parameter
planning.
Transmission System
396
Selection
l NE1: 18.0.0.2
l NE2: 18.0.1.2
Reverse Tunnel:
l NE3: 18.0.1.1
l NE2: 18.0.0.1
Set this parameter
planning.

Step 3 Create the protection tunnel.
1. Create the protection tunnel by referring to Step 2
Set the basic Information as follows:
Selection
Tunnel Name Protection Tunnel Set this parameter
planning.
planning.
planning.
planning.
to be created.

Set the node information as follows:
Transmission System
397
Selection
NE6, NE5, NE4: Transit
NE3: Egress
node.
node. In this example, NE6,
NE5, and NE4 are transit
nodes.
node.
on the U2000 and delivered
to the corresponding NEs

Set the route information as follows:
Selection
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 1620
Set this parameter
planning.
Transmission System
398
Selection
Tunnels: E-LSP
Set this parameter
planning.
Tunnels: None
Set this parameter
planning.
l NE1: 3-EM6F-2
(PORT-2)
l NE6: 3-PEG8-2
(PORT-2)
l NE5: 4-PEX2-2
(PORT-2)
l NE4: 3-PEX2-2
(PORT-2)
Reverse Tunnel:
l NE3: 3-EX2-1
(PORT-1)
l NE4: 3-PEX2-1
(PORT-1)
l NE5: 3-PEG8-1
(PORT-1)
l NE6: 3-PEG8-1
(PORT-1)
Set this parameter
planning. Only this
and transit node.
l NE1: 22
l NE6: 32
l NE5: 42
l NE4: 52
Reverse Tunnel:
l NE3: 23
l NE4: 33
l NE5: 43
l NE6: 53
Set this parameter
planning.
Transmission System
399
Selection
l NE6: 3-PEG8-1
(PORT-1)
l NE5: 3-PEG8-1
(PORT-1)
l NE4: 3-PEX2-1
(PORT-1)
l NE3: 3-EX2-1
(PORT-1)
Reverse Tunnel:
l NE4: 3-PEX2-2
(PORT-2)
l NE5: 4-PEX2-2
(PORT-2)
l NE6: 3-PEG8-2
(PORT-2)
l NE1: 3-EM6F-2
(PORT-2)
Set this parameter
planning. Only this
transit node.
l NE6: 22
l NE5: 32
l NE4: 42
l NE3: 52
Reverse Tunnel:
l NE4: 23
l NE5: 33
l NE6: 43
l NE1: 53
Set this parameter
planning.
l NE1: 18.0.5.2
l NE6: 18.0.4.2
l NE5: 18.0.3.1
l NE4: 18.0.2.1
Reverse Tunnel:
l NE3: 18.0.2.2
l NE4: 18.0.3.2
l NE5: 18.0.4.1
l NE6: 18.0.2.1
Set this parameter
planning.
Transmission System
400

Step 4 Configure ports, including ATM ports on Node B and RNC.
1. Configure ATM ports on Node B.
Configuration > Interface Management > PDH Interface from the Function Tree
to configure ports on Node B.
b. Select the ports from 4-MD1-1(PORT-1) to 4-MD1-8(PORT-8), In the Port Mode
field, right-click, and choose Layer 2 from the shortcut menu. Click Apply.
NOTE
Before setting the frame format, ensure that the DCN of the port is disabled.
Set relevant parameters as follows:
l Port: ports from 4-MD1-1(PORT-1) to 4-MD1E-8(PORT-8)
l Name: NodeB ATM (You can set port names to distinguish different service ports
for easy location and query.)
l Port Mode: Layer 2 (IMA signals are carried.)
l Encapsulation Type: ATM
c. On the Advanced tab page, set Frame Format and Frame Mode for the ports from
4-MD1-1(PORT-1) to 4-MD1-8(PORT-8). Click Apply.
l Port: ports from 4-MD1-1(PORT-1) to 4-MD1-8(PORT-8)
l Frame Format: CRC-4 multiframe (The frame format must be same as the cell
format on Node B.)
l Frame Mode: 31
IMA Management from the Function Tree. Click the Binding tab.
e. On the Binding tab page, click Configuration. Then, set the bound ports for 4-MD1-1
(Port-1) and 4-MD1-2(Port-2). Click OK.
Set the parameters relevant to 4-MD1-1(Port-1) as follows:
l Available Boards: 4-MD1
l Configurable Ports: 4-MD1-1(Port-1)
Level: E1 (For the E1 card, when the E1 level is selected, the entire E1 channel
is used to transmit ATM IMA signals.)
Direction: Bidirectional (default)
Optical Interface: - (In the case of the E1 and fractional E1 levels, you need not
set this parameter. In the case of the VC12-xv level, you need to select the
corresponding optical port, that is, the E1 level in this example.)
l Available Resources: ports from 4-MD1-1(PORT-1) to 4-MD1-4(PORT-4)
l Available Timeslots: - (In the case of the E1 and fractional E1 levels, you need not
corresponding timeslot.)
Transmission System
401
Level: E1
Direction: Bidirectional
Optical Interface: -
l Available Timeslots: -
f. On the IMA Group Management tab page, double-click the IMA Protocol Enable
Status field to enable the IMA protocol. Set other relevant parameters as required.
Click Apply.
The settings of parameters need to be the same as those on Node B.
g. On the ATM Interface Management tab page, set the parameters, such Max. VPI
and Max. VCI. Click Apply.
l Port Type: UNI (A UNI port is used to connect to the client-side equipment, and
an NNI port is used to connect the ATM equipment on a core network.)
l VCC-Supported VPI Count: 32 (Set this parameter according to the networking
planning.)
l Loopback: No Loopback
2. Configure ATM ports on RNC.
Configuration > Interface Management > SDH Interface from the Function Tree
to configure ports on RNC.
b. On the Layer 2 Attributes tab page, select 32-N1AFO1-1(PORT-1) and set the
parameters, such as Max. VPI and Max. VCI, for the port. Click Apply.
planning.)
Step 5 Create three UNIs-NNI ATM services.
Transmission System
402
1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu. Create
the R99 service from NE1 to NE3.
Table 7-10 Parameters of general attributes
Selection
Service Type ATM Set this parameter
planning.
Service ID 1 A service ID uniquely
identifies a service on the
entire network.
Service Name ATMService-R99 Set this parameter
planning.
Protection Type Protection-free Set this parameter
planning.
Link Type ATM N-to-1 VCC Cell
Transport
Set this parameter
planning.

2. Click Configure Source And Sink.. A dialog box is displayed. On the Physical Topology
in the upper left portion of the window, set NE1 as the source NE, set NE3 as the sink NE.
Set relevant parameters and click OK.
Table 7-11 Parameters of the source node
Selection
SAI Type ATM Set this parameter
planning.

Table 7-12 Parameters of the sink node
Selection
planning.

Transmission System
403
3. In PW in the lower left portion of the window, set relevant parameters.
Selection
Forward Type Static Binding l If you set Forward
Type to Static
Binding, you need to
manually specify a
tunnel in the Forward
Tunnel area.
l If you set Reverse
Type to Select Policy,
you need to set the
tunnel priority in the
Reverse Tunnel area so
that the system selects a
tunnel according to the
priority.
Forward Tunnel Tunnel-001 Set this parameter
planning.
Reverse Type Static Binding l If you set Reverse
Type to Static
manually specify a
tunnel in the Reverse
Tunnel area.
you need to set the
priority.
Reverse Tunnel Tunnel-001_Reverse Set this parameter
planning.
PW ID 35 A PW ID uniquely
identifies a PW on the
entire network.
Transmission System
404
Selection
Signaling Type Static In the case of a static PW,
you need to configure
Forward Label and
Reverse Label for a static
PW.
Encapsulation Type MPLS Set this parameter
planning.

4. Click ATM Link. In the dialog box that is displayed, set the parameters relevant to the
connection.
Table 7-14 Parameter for configuring a connection
Selection
Connection Name Connection1 and
Connection2
Set this parameter
planning.
Role Working Set this parameter
planning.
Source SAI Connection1: 4-MD1-1
(Port-1)
Connection2: 4-MD1-2
(Port-2)
Set this parameter
planning.
Source VPI Connection1: 1
Connection2: 1
VPI information carried by
the service from a base
station.
Source VCI Connection1: 100
Connection2: 100
VCI information carried by
station.
Source ATM Policy Connection1: RT-VBR
Connection2: RT-VBR
Connection1 is an R99
service and you need to
select the RT-VBR policy
for it.
for it.
Transmission System
405
Selection
Sink SAI Connection1: 32-
N1AFO1-1(PORT-1)
Connection2: 32-
N1AFO1-1(PORT-1)
Set this parameter
planning.
Sink VPI Connection1: 50
Connection2: 60
the service after a VPI
switching. Max. VPI of an
ATM port is 255 according
to the planning and
therefore the value of the
VPI on the sink ranges
between 0 and 255.
Sink VCI Connection1: 32
Connection2: 32
the service after a VCI
switching. Max. VCI of an
to the planning and
between 32 and 127.
Sink ATM Policy Connection1: RT-VBR
Connection2: RT-VBR
for it.
for it.
Transit VPI - Set this parameter
planning.
Transit VCI - Set this parameter
planning.

5. Click Advanced and configure PW QoS and Advanced PW Attribute.
Transmission System
406
Table 7-15 Parameters of advanced attributes
Selection
Control Word Must use On an MPLS PSN network,
a control word carries the
packet information. A
control word is the
encapsulation packet
header that consists of four
bytes. A control word can
be used to identify the
packet sequence or used for
bit stuffing.
Control Channel Type CW A CW control word is used
to detect the connectivity of
a PW.
VCCV Verification Mode Ping The VCCV verification
mode is used to detect the
connectivity of a PW.
Source ATM CoS Map 1(mapping1) Set this parameter
planning.
Sink ATM CoS Map 1(mapping1) Set this parameter
planning.
Max. Concatenated Cells
Count
10 Maximum number of ATM
cells that can be
encapsulated into a packet.
Packet Loading Time (us) 1000 Set this parameter
planning.

Table 7-16 PW QoS parameters
Selection
EXP 1 Set this parameter
planning.
Bandwidth Limited Enabled Set this parameter
planning.
Transmission System
407
Selection
CIR (kbit/s) 10000 Set the bandwidth based on
the service traffic.
PIR (kbit/s) 30000 Set the bandwidth based on

6. Click OK. The ATMService-R99 service is created successfully.
7. Create the ATMService-HSDPA service. For details, refer to the preceding steps.
Selection
planning.
entire network.
Service Name ATMService-HSDPA Set this parameter
planning.
planning.
Transport
Set this parameter
planning.

Selection
planning.

Transmission System
408
Selection
planning.

Selection
Type to Static
manually specify a
Tunnel area.
l If you set Forward
Type, you need to set
the tunnel priority in the
Forward Tunnel area
so that the system
selects a tunnel
according to the
priority.
planning.
Type to Static
manually specify a
Tunnel area.
you need to set the
priority.
Transmission System
409
Selection
planning.
entire network.
Forward Label and
Reverse Label for a static
PW.
planning.

Selection
Connection2
Set this parameter
planning.
planning.
(Port-1)
(Port-2)
Set this parameter
planning.
Connection2: 1
station.
Connection2: 101
station.
Transmission System
410
Selection
Source ATM Policy Connection1: UBR
Connection2: UBR
Connection1 is an HSDPA
select the UBR policy for it.
N1AFO1-1(PORT-1)
Connection2: 32-
N1AFO1-1(PORT-1)
Set this parameter
planning.
Connection2: 61
to the planning and
between 0 and 255.
Connection2: 32
to the planning and
between 32 and 127.
Sink ATM Policy Connection1: UBR
Connection2: UBR
planning.
planning.

Transmission System
411
Selection
control word is the
bit stuffing.
a PW.
planning.
planning.
Count
cells that can be
planning.

Selection
planning.
planning.
Transmission System
412
Selection

8. Create the ATMService-Signaling service. For details, refer to the preceding steps.
Selection
planning.
entire network.
Service Name ATMService-Signaling Set this parameter
planning.
planning.
Transport
Set this parameter
planning.

Selection
planning.

Selection
planning.
Transmission System
413

Selection
Type to Static
manually specify a
Tunnel area.
l If you set Forward
Type, you need to set
the tunnel priority in the
Forward Tunnel area
so that the system
selects a tunnel
according to the
priority.
planning.
Type to Static
manually specify a
Tunnel area.
you need to set the
priority.
planning.
entire network.
Transmission System
414
Selection
Forward Label and Reverse
Label for a static PW.
planning.

Selection
Connection2
Set this parameter
planning.
planning.
(Port-1)
(Port-2)
Set this parameter
planning.
Connection2: 1
station.
Connection2: 102
station.
Source ATM Policy Connection1: CBR
Connection2: CBR
Connection1 is a signaling
select the CBR policy for it.
N1AFO1-1(PORT-1)
Connection2: 32-
N1AFO1-1(PORT-1)
Set this parameter
planning.
Transmission System
415
Selection
Connection2: 62
to the planning and
between 0 and 255.
Connection2: 32
to the planning and
between 32 and 127.
Sink ATM Policy Connection1: CBR
Connection2: CBR
planning.
planning.

Transmission System
416
Selection
control word is the
bit stuffing.
a PW.
planning.
planning.
Count
cells that can be
planning.

Selection
planning.
planning.
Transmission System
417
Selection

----End
7.5.4 Configuration Process in Per-NE Mode
This section describes the process of configuring a UNI-NNI ATM service on a per-NE basis.
Prerequisites
l You must understand the networking, requirements and service planning of the example.
l A network must be created.
Procedure
Step 1 Set LSR IDs.
1. In the NE Explorer, select NE1 and choose > Configuration > Packet Configuration >
MPLS Management > Basic Configuration from the Function Tree.
2. Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.
Selection
LSR ID NE1: 130.0.0.1 Set this parameter
network.
planning.

3. Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the
preceding two steps to set the parameters, such as LSR ID.
Transmission System
418
Selection
LSR ID NE2: 130.0.0.2
NE3: 130.0.0.3
NE4: 130.0.0.4
NE5: 130.0.0.5
NE6: 130.0.0.6
Set this parameter
network.
planning.

Step 2 Configure NNI interfaces.
Interface Management > Ethernet Interface from the Function Tree to configure the
network-side interface.
2. In the Basic Attributes tab, select the 3-EM6F-1(PORT-1) and 3-EM6F-2(PORT-2). Right
click the Port Mode field, and select Port Mode. Set the parameters as required, and click
Apply.
l Enable Port: Enabled
l Port Mode: Layer 3 (The port carries a tunnel.)
l Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite
port as the same.)
l Max Frame Length (byte): 1620 (Set this parameter according to the length of data
packets. All the received data packets that contain more bytes than the maximum frame
length are discarded.)
3. Select the 3-EM6T-1(PORT-1) and 3-EM6T-2(PORT-2) in the Layer 3 Attributes tab.
Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP
Address field and choose Manually. Then, set the parameters such as IP Address and IP
Mask. Click Apply.
l Enable Tunnel: Enabled
l Specify IP Address: Manually (Manually indicates that you can set the IP address of
the port.)
l 3-EM6F-1(PORT-1) IP Address: 18.0.0.1
l 3-EM6F-2(PORT-2) IP Address: 18.0.5.1
l IP Mask: 255.255.255.252
4. Display the NE Explorer for NE2, NE3, NE4, NE5, and NE6 separately. Perform 2.1
through 2.3 to set parameters of each related interface.
Set the parameters of each interface the same as NE1-3-EM6F-1(PORT-1).
The layer 3 attributes of each ports are as follows:
Transmission System
419
NE Port IP Address IP Mask
NE2 4-PEX2-1(PORT-1) 18.0.1.1 255.255.255.252
3-PEG8-2(PORT-2) 18.0.0.2 255.255.255.252
NE3 3-EX2-1(PORT-1) 18.0.2.1 255.255.255.252
3-EX2-2(PORT-2) 18.0.1.2 255.255.255.252
NE4 3-PEX2-2(PORT-2) 18.0.2.2 255.255.255.252
3-PEX2-1(PORT-1) 18.0.3.1 255.255.255.252
NE5 4-PEX2-2(PORT-2) 18.0.3.2 255.255.255.252
3-PEG8-1(PORT-1) 18.0.4.2 255.255.255.252
NE6 3-PEG8-2(PORT-2) 18.0.4.1 255.255.255.252
3-PEG8-1(PORT-1) 18.0.5.2 255.255.255.252

Step 3 Create the working tunnel.
1. Choose Service > Tunnel > Create Tunnel from the main menu.
2. Set the basic information about the working tunnel.
Selection
Tunnel Name Working Tunnel Set this parameter
planning.
planning.
planning.
planning.
to be created.
Protection Type 1:1 Set this parameter
planning.

Transmission System
420
3. Configure the NE list. On the physical topology, double-click NE1, NE2, and NE3 to add
them to the NE list and set the corresponding NE roles.
Selection
NE2: Transit
NE3: Egress
node.
node. In this example, NE2
is a transit node.
node.
the corresponding NEs

4. Click Details to set the advanced parameters of the reverse tunnel. Click OK.
Selection
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 1620
Set this parameter
planning.
Transmission System
421
Selection
Tunnels: E-LSP
Set this parameter
planning.
Tunnels: None
Set this parameter
planning.
l NE1: 3-EM6F-1
(PORT-1)
l NE2: 4-PEX2-1
(PORT-1)
Reverse Tunnel:
l NE3: 3-EX2-2
(PORT-2)
l NE2: 3-PEG8-2
(PORT-2)
Set this parameter
planning. Only this
and transit node.
l NE1: 20
l NE2: 30
Forward Tunnel:
l NE3: 21
l NE2: 31
Set this parameter
planning.
l NE2: 3-PEG8-2
(PORT-2)
l NE3: 3-EX2-2
(PORT-2)
Reverse Tunnel:
l NE2: 4-PEX2-1
(PORT-1)
l NE1: 3-EM6F-1
(PORT-1)
Set this parameter
planning. Only this
transit node.
l NE2: 20
l NE3: 30
Reverse Tunnel:
l NE2: 21
l NE1: 31
Set this parameter
planning.
Transmission System
422
Selection
l NE1: 18.0.0.2
l NE2: 18.0.1.2
Reverse Tunnel:
l NE3: 18.0.1.1
l NE2: 18.0.0.1
Set this parameter
planning.

Step 4 Create the protection tunnel.
1. Create the protection tunnel by referring toStep 3.
Set the basic Information as follows:
Selection
Tunnel Name Protection Tunnel Set this parameter
planning.
planning.
planning.
planning.
to be created.

Set the node information as follows:
Transmission System
423
Selection
NE6, NE5, NE4: Transit
NE3: Egress
node.
node. In this example, NE6,
NE5, and NE4 are transit
nodes.
node.
the corresponding NEs

Set the route information as follows:
Selection
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 1620
Set this parameter
planning.
Transmission System
424
Selection
Tunnels: E-LSP
Set this parameter
planning.
Tunnels: None
Set this parameter
planning.
l NE1: 3-EM6F-2
(PORT-2)
l NE6: 3-PEG8-2
(PORT-2)
l NE5: 4-PEX2-2
(PORT-2)
l NE4: 3-PEX2-2
(PORT-2)
Reverse Tunnel:
l NE3: 3-EX2-1
(PORT-1)
l NE4: 3-PEX2-1
(PORT-1)
l NE5: 3-PEG8-1
(PORT-1)
l NE6: 3-PEG8-1
(PORT-1)
Set this parameter
planning. Only this
and transit node.
l NE1: 22
l NE6: 32
l NE5: 42
l NE4: 52
Reverse Tunnel:
l NE3: 23
l NE4: 33
l NE5: 43
l NE6: 53
Set this parameter
planning.
Transmission System
425
Selection
l NE6: 3-PEG8-1
(PORT-1)
l NE5: 3-PEG8-1
(PORT-1)
l NE4: 3-PEX2-1
(PORT-1)
l NE3: 3-EX2-1
(PORT-1)
Reverse Tunnel:
l NE4: 3-PEX2-2
(PORT-2)
l NE5: 4-PEX2-2
(PORT-2)
l NE6: 3-PEG8-2
(PORT-2)
l NE1: 3-EM6F-2
(PORT-2)
Set this parameter
planning. Only this
transit node.
l NE6: 22
l NE5: 32
l NE4: 42
l NE3: 52
Reverse Tunnel:
l NE4: 23
l NE5: 33
l NE6: 43
l NE1: 53
Set this parameter
planning.
l NE1: 18.0.5.2
l NE6: 18.0.4.2
l NE5: 18.0.3.1
l NE4: 18.0.2.1
Reverse Tunnel:
l NE3: 18.0.2.2
l NE4: 18.0.3.2
l NE5: 18.0.4.1
l NE6: 18.0.2.1
Set this parameter
planning.
Transmission System
426

Step 5 Configure ports, including ATM ports on Node B and RNC.
1. Configure ATM ports on Node B.
Configuration > Interface Management > PDH Interface from the Function Tree
to configure ports on Node B.
b. Select the ports from 4-MD1-1(PORT-1) to 4-MD1-8(PORT-8), In the Port Mode
field, right-click, and choose Layer 2 from the shortcut menu. Click Apply.
NOTE
Before setting the frame format, ensure that the DCN of the port is disabled.
l Name: NodeB ATM (You can set port names to distinguish different service ports
for easy location and query.)
l Port Mode: Layer 2 (IMA signals are carried.)
l Encapsulation Type: ATM
c. On the Advanced tab page, set Frame Format and Frame Mode for the ports from
4-MD1-1(PORT-1) to 4-MD1-8(PORT-8). Click Apply.
l Frame Format: CRC-4 multiframe (The frame format must be same as the cell
format on Node B.)
l Frame Mode: 31
IMA Management from the Function Tree. Click the Binding tab.
e. On the Binding tab page, click Configuration. Then, set the bound ports for 4-MD1-1
(Port-1) and 4-MD1-2(Port-2). Click OK.
Level: E1 (For the E1 card, when the E1 level is selected, the entire E1 channel
is used to transmit ATM IMA signals.)
Direction: Bidirectional (default)
Optical Interface: - (In the case of the E1 and fractional E1 levels, you need not
corresponding optical port, that is, the E1 level in this example.)
l Available Timeslots: - (In the case of the E1 and fractional E1 levels, you need not
corresponding timeslot.)
Transmission System
427
Level: E1
Direction: Bidirectional
Optical Interface: -
l Available Timeslots: -
f. On the IMA Group Management tab page, double-click the IMA Protocol Enable
Status field field to enable the IMA protocol. Set other relevant parameters as
required. Click Apply.
The settings of parameters need to be the same as those on Node B.
g. On the ATM Interface Management tab page, set the parameters, such Max. VPI
and Max. VCI. Click Apply.
planning.)
l Loopback: No Loopback
2. Configure ATM ports on RNC.
Configuration > Interface Management > SDH Interface from the Function Tree
to configure ports on RNC.
b. On the Layer 2 Attributes tab page, select 32-N1AFO1-1(PORT-1) and set the
parameters, such as Max. VPI and Max. VCI, for the port. Click Apply.
planning.)
Step 6 Configure three UNIs-NNI ATM services.
Transmission System
428
ATM Service Management from the Function Tree. Then, create an R99 service from
NE1 to NE3.
2. Click New. The New ATM Service window is displayed. Then, set Service ID, Service
Name, Service Type, and Connection Type.
l Service ID: 1
l Service Name: ATMService-R99
l Service Type: UNIs-NNI
l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection
can be modified; PVP indicates that only the VPI of the ATM connection can be
modified.)
3. Click the Connection tab and click Add. The Configure Connection window is displayed.
Add connection 1 and connection 2.
l Connection 1
Source Board: 4-MD1
Source Port: 4-MD1-1(Port-1)
Source VPI(example:35,36-39): 1 (The VPI information transmitted with the service
from NodeB)
Source VCI(example:35,36-39): 100 (The VCI information transmitted with the
service from NodeB)
PW ID: 35
Sink Board: -
Sink Port: -
Sink VPI(example:35,36-39): 50 (The VPI information transmitted with the service
after VPI switching. Max. VPI of the ATM interface is planned to be 255, and
therefore the Sink VPI(example:35,36-39) ranges from 0 to 255.)
Sink VCI(example:35,36-39): 32 (The VCI information transmitted with the service
after VCI switching. Max. VCI of the ATM interface is planned to be 127, and
therefore the Sink VCI(example:35,36-39) ranges from 32 to 127.)
service.)
R99 service.)
l Connection 2
Source Board: 4-MD1
Transmission System
429
PW ID: 35
Sink Board: -
Sink Port: -
service.)
R99 service.)
4. Click the PW tab and click Add. The Configure PW window is displayed. In the window,
set attributes of the PW.
Set the parameters related to PW1 as follows:
l Basic Attributes
PW ID: 35
PW Signaling Type: Static (Static indicates that the ingress and egress labels are
manually added.)
PW Type: ATM n to one VCC cell transport (Select ATM n-to-one VPC cell
transport if multiple ATM connections are mapped to one PW; select ATM one-to-
one VCC Cell Mode if one ATM connection is mapped to one PW. Herein, two
ATM connections are mapped to one PW.)
PW Direction: Bidirectional
PW Incoming Label/Source Port: 33
PW Outgoing Label/Sink Port: 32
Tunnel Type: MPLS
Tunnel No.: 1 (Tunnel-0001)
Peer LSR ID: 130.0.0.3
l Advanced Attributes
Control Word: Must use
Control Channel Type: CW (CW realizes connectivity check of the PW.)
VCCV Verification Mode: Ping (PW Ping realizes connectivity check of the PW.)
Max. Concatenated Cell Count: 10 (The maximum number of ATM cells that can
be encapsulated in each packet.)
Packet Loading Time (us): 1000
l QoS
Ingress
EXP: 1
5. Click the CoS Mapping tab and set the QoS attribute of PW1.
Set the QoS mapping for PW1 as follows:
l PW ID: 35
l CoS Mapping: 1(Default AtmCosMap)
6. In the NE Explorer, select NE3. Then, create an ATMService-R99 service by following
6.1 to 6.5.
Transmission System
430
l The configuration parameters are as follows:
Service ID: 1
Service Name: ATMService-R99
Service Type: UNIs-NNI
Connection Type: PVC
l Configure ATM Connection:
Connection 1
Source Board: 32-N1AFO1
Source Port: 32-N1AFO1-1(PORT-1)
PW ID: 35
Sink Board: -
Sink Port: -
Uplink Policy: RT-VBR
Downlink Policy: RT-VBR
Connection 2
PW ID: 35
Sink Board: -
Sink Port: -
Uplink Policy: RT-VBR
Downlink Policy: RT-VBR
l Set the parameters related to PW1 as follows:
Basic Attributes
PW ID: 35
PW Signaling Type: Static
PW Type: ATM n to one VCC cell transport
Transmission System
431
Tunnel Type: MPLS
Advanced Attributes
Control Channel Type: CW
VCCV Verification Mode: Ping
Max. Concatenated Cell Count: 10
QoS
Ingress
EXP: 1
l Set the QoS mapping for PW1 as follows:
PW ID: 35
CoS Mapping: 1(Default AtmCosMap)
7. Create an ATMService-HSDPA service by following 6.1 to 6.6.
Set the parameters related to NE1 as follows:
Service ID: 2
Service Name: ATMService-HSDPA
Connection 1
Source Board: 4-MD1
PW ID: 36
Sink Board: -
Sink Port: -
Uplink Policy: UBR
Downlink Policy: UBR
Connection 2
Transmission System
432
Source Board: 4-MD1
PW ID: 36
Sink Board: -
Sink Port: -
Uplink Policy: UBR
Basic Attributes
PW ID: 36
Tunnel Type: MPLS
PeerLSR ID: 130.0.0.3
Advanced Attributes
QoS
Ingress
EXP: 3
l The CoS mapping of PW2 should be configured:
PW ID: 36
Service ID: 2
Service Name: ATMService-HSDPA
Transmission System
433
Connection 1
PW ID: 36
Sink Board: -
Sink Port: -
Sink VPI: 51
Sink VCI: 32
Uplink Policy: UBR
Connection 2
PW ID: 36
Sink Board: -
Sink Port: -
Uplink Policy: UBR
Basic Attributes
PW ID: 36
Tunnel Type: MPLS
Transmission System
434
Advanced Attributes
QoS
Ingress
EXP: 3
PW ID: 36
8. Create an ATMService-Signaling service by following 6.1 to 6.6.
Service ID: 3
Service Name: ATMService-Signaling
Connection 1
Source Board: 4-MD1
PW ID: 37
Sink Board: -
Sink Port: -
Uplink Policy: CBR
Downlink Policy: CBR
Connection 2
Source Board: 4-MD1
Transmission System
435
PW ID: 37
Sink Board: -
Sink Port: -
Uplink Policy: CBR
Basic Attributes
PW ID: 37
Tunnel Type: MPLS
Advanced Attributes
QoS
Ingress
EXP: 0
PW ID: 37
Service ID: 3
Service Name: ATMService-Signaling
Connection 1
Transmission System
436
PW ID: 37
Sink Board: -
Sink Port: -
Uplink Policy: CBR
Connection 2
PW ID: 37
Sink Board: -
Sink Port: -
Uplink Policy: CBR
Basic Attributes
PW ID: 37
Tunnel Type: MPLS
Advanced Attributes
Transmission System
437
QoS
Ingress
EXP: 0
PW ID: 37
----End
7.6 Verifying ATM/IMA Services
Use the ATM OAM function to test the connectivity of UNI-NNI ATM/IMA services in order
to ensure that ATM/IMA services are normal.
Prerequisites
l End-to-end UNI-NNI ATM/IMA services are configured.
U2000
Figure 7-11 shows the connections for testing the connectivity of ATM/IMA services.
Figure 7-11 Connections for testing the connectivity of ATM/IMA services
PSN
NE2
Inloop
NE1
Inloop
Procedure
Step 1 On NE1 and NE2, set the automatic loopback release function of the UNI ports receiving ATM/
IMA services to Disabled.
1. On the left side of the Automatic Disabling of NE Function window, select NE1 and NE2
in the Object Tree. Then, click . The Automatic Disabling of NE Function window
lists the selected NEs.
2. For SDH Optical/Electrical Interface Loopback of NE1 and NE2, set Auto Disabling
to Disabled.
Transmission System
438
NOTE
When Auto Disabling of SDH Optical/Electrical Interface Loopback on an NE is set to
Disabled, the automatic loopback release function is disabled for all SDH optical ports, PDH
electrical ports, and ATM/IMA groups on the NE.
Step 2 On NE1, set an inloop for the UNI port receiving ATM/IMA services as shown in the test
connection diagram.
1. In the Main Topology of the U2000, right-click NE1. Then, choose NE Explorer from the
shortcut menu. The NE Explorer window is displayed.
2. In the NE Explorer window, select NE1 and then choose Configuration > Packet
Configuration > Interface Management > ATM IMA Management from the Function
Tree.
3. Click the ATM Interface Management tab, and then select the IMA group carrying the
ATM/IMA service to be tested.
4. Double-click Loopback of the IMA group. In the menu that is displayed, select Inloop.
5. Click Apply.
Step 3 On NE2, set an inloop for the UNI port receiving ATM/IMA services as shown in the test
connection diagram with reference to Step 2.
Step 4 Select NE1 in the NE Explorer, and then choose Configuration > Packet Configuration >
ATM OAM Management from the Function Tree.
Step 5 Click the Remote Loopback Test tab, and select the ATM/IMA services to be tested.
Step 6 For the ATM/IMA services whose Connection Direction is Source, set Segment and End
Attribute to Endpoint.
NOTE
Segment and End Attribute of an ATM/IMA service specifies the type of ATM OAM cells transmitted
during an LB test.
l If Segment and End Attribute is set to Segment point, seg_LB cells will be transmitted.
l If Segment and End Attribute is set to Endpoint, e-t-e_LB cells will be transmitted.
Step 7 Set Loopback Point NE of the ATM/IMA services to be tested to NE2.
Step 8 Click Test to start an LB test. The test progress bar is displayed. In the Operation Result dialog
box that is displayed upon the completion of the test, click Close.
Step 9 Check Test Result of the tested ATM/IMA service.
1. Normally, Test Result should be Test Succeeded. If such is the display, view the new
performance events to verify that the LB test succeeded.
a. On the Main View, click the shortcut icon. In the Query Event Logs window
that is displayed, select Reporting of LB status information about the new
performance events.
b. Right-click Reporting of LB status information, and select Details .... from the
shortcut menu. In the window, view the additional information to confirm the test
result.
c. Normally, the test result should be a success. If it is a failure, handle the problem
according to the ATM/OAM service fault handling description in the Troubleshooting
Guide.
Transmission System
439
2. If the test result is Test Failed or other failure information, handle the problem according
to the ATM/OAM service fault handling description in the Fault Handling.
Step 10 On NE1 and NE2, release the inloops for the UNI ports receiving ATM/OAM services with
reference to Step 2.
Step 11 Repeat Step 2 to Step 10 to test the connectivity of the other ATM/OAM services on NE1 and
NE2.
Step 12 For SDH Optical/Electrical Interface Loopback on NE1 and NE2, set Automatic
Disabling to Enabled with reference to Step 1.
Step 13 Repeat Step 1 to Step 12 to test the connectivity of the ATM/IMA services on the other NEs.
----End
Transmission System
440
8 Configuration Task Collection
About This Chapter
This topic lists the relevant configuration tasks.
8.1 Configuring an Ethernet Port
This topic describes how to set the attributes of an Ethernet port. An Ethernet port can be used
to carry Ethernet packets or tunnels, depending on different settings of the port attributes. The
attributes of an Ethernet port include the general attributes, Layer 2 attributes, Layer 3 attributes,
advanced attributes, and flow control.
8.2 Configuring the NNIs
Configuring the NNIs is the basis of configuring the packet Ethernet services.
8.3 Configuring CES Ports
This topic describes how to configure channelized STM-1 ports and E1 ports to support access
of CES services.
8.4 Setting Serial Port Parameters
When some 64 kbit/s timeslots of a Smart E1 port are used for transmission of ATM services,
these timeslots can be considered as a serial port.
8.5 Configuring ATM PWE3 Services
This section describes the operation tasks for configuring ATM PWE3 services on the NMS.
8.6 Managing ATM/IMA Ports
On the OptiX OSN equipment, ATM/IMA ports are mapped into one ATM TRUNK.
8.7 ATM Traffic Management
ATM traffic management includes ATM-Diffserv management and ATM policy management.
8.8 Configuring an MPLS Tunnel
On a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. In
this manner, data packets can be transparently transmitted between NEs. One MPLS tunnel can
carry several PWs. Before configuring a service, you need to configure the MPLS tunnel that
carries the service. On the NMS, you can use the per-NE configuration scheme to configure an
MPLS tunnel.
8.9 Managing MPLS Tunnels
Transmission System
Configuration Guide (Packet Transport Domain) 8 Configuration Task Collection
441
MPLS tunnels are used to transmit PWE3 services and their quality determines transmission
stability of PWE3 services. Therefore, it is crucial to properly manage MPLS tunnels. Managing
MPLS tunnels involves checking the MPLS tunnel topology, deploying MPLS tunnels, deleting
MPLS tunnels, and managing discrete MPLS tunnels.
8.10 Configuring MPLS Tunnel OAM
MPLS OAM effectively detects, confirms, and locates the internal defects of an MPLS network,
and therefore monitors the network performance.
8.11 Configuring MPLS-TP Tunnel OAM
This section describes how to configure MPLS-TP tunnel OAM.
8.12 Configuring Tunnel APS
Tunnel APS protection is implemented based on the APS protocol. If tunnel APS is configured,
the services are switched from the working tunnel to the protection tunnel after the working
tunnel is faulty.
8.13 Managing Tunnel APS Protection Groups
stability of PWE3 services. Tunnel APS provides protection for MPLS tunnels. Therefore, it is
crucial to properly manage tunnel APS protection groups. Managing tunnel APS protection
groups involves automatically discovering, deploying, modifying, and deleting tunnel APS
protection groups.
8.14 Configuring ML-PPP
This section describes how to configure ML-PPP.
8.15 Configuring NE-Level TPID
When PW-carried Ethernet services use the request VLAN function, the request VLAN tags
added to the services must contain the same TPID so that the services can run properly.
8.16 Configuring the Address Resolution
On the NMS, the IP address and MAC address of each ARP table item can be created and queried.
8.17 Configuring E-Line Services
This topic describes how to configure E-Line services, including UNI-UNI E-Line services, E-
Line services carried by ports, E-Line services carried by PWs, and E-Line services carried by
QinQ links.
8.18 Configuring E-LAN Services
This section describes how to configure E-LAN services.
8.19 Managing the MAC Address Table
The MAC address table is the core of the E-LAN service. The OptiX OSN equipment provides
various functions for managing the MAC address table.
8.20 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC
address table or a multicast frame whose destination MAC address is not listed in the multicast
group. By default, the NE broadcasts the unknown frame. By setting the mode for processing
an unknown frame of the E-LAN service, you can change the processing mode so that unknown
frame can be discarded.
8.21 Configuring Transit Nodes for Ethernet Services
On a live data network, an Ethernet service is added to its source NE, passed through on its
transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs
for an Ethernet service.
Transmission System
442
8.22 Configuring a Composite Service
This section describes how to configure the basic attributes, service components, and connection
points for a composite service.
8.23 Managing Composite Services
Managing composite services includes automatically discovering and deploying composite
services.
8.24 Operation Tasks for Configuring CES Services
This topic describes the operation tasks for configuring CES services in per-NE mode and end-
to-end mode on the NMS.
8.25 Configuring Transit NEs for CES Services
for a CES service.
8.26 Managing VPLS Services
Quality of VPLS services has significant impacts on customer revenues; stable VPLS services
increase customer revenues. Therefore, it is crucial to properly manage VPLS services.
Managing VPLS services involves deploying, modifying, and deleting VPLS services, checking
the VPLS service topology.
8.27 Managing PWE3 Services
Quality of PWE3 services has significant impacts on customer revenues; stable PWE3 services
increase customer revenues. Therefore, it is crucial to properly manage PWE3 services.
Managing PWE3 services involves deploying, modifying, and deleting PWE3 services,
checking the PWE3 service topology, and managing discrete PWE3 services.
8.28 Managing the QoS
By managing the QoS, you can provide the services of different levels for different service types.
Transmission System
443
8.1 Configuring an Ethernet Port
This topic describes how to set the attributes of an Ethernet port. An Ethernet port can be used
to carry Ethernet packets or tunnels, depending on different settings of the port attributes. The
attributes of an Ethernet port include the general attributes, Layer 2 attributes, Layer 3 attributes,
advanced attributes, and flow control.
The application scenario of an Ethernet port depends on the settings of the port attributes. For
details, refer to Table 8-1.
Table 8-1 Application scenario of an Ethernet port
Application Scenario Port Type Required Port Attribute
Accessing the Ethernet
service
Ethernet port General attributes, Layer 2
attributes
Carrying the QinQ Link Ethernet port General attributes, Layer 2
attributes
Carrying the tunnel Ethernet port General attributes, Layer 3
attributes

NOTE
When the Ethernet port is used to carry the QinQ Link, the configuration procedure is similar to the
configuration procedure when the Ethernet port is used to carry the Ethernet service. In this case, however,
the encapsulation types are different. For details, see 8.1.2 Setting the Layer 2 Attributes of Ethernet
Ports.
Follow the procedure shown in Figure 8-1 to set the attributes of an Ethernet port.
Transmission System
444
Figure 8-1 Procedure for configuring an Ethernet port
Carry Ethernet packets
Carry tunnels
Set general attributes
Start
Set general attributes
Start
Configure the flow control
End
Set Layer 3
attributes
Required
Optional
Configure the flow control
End
Set Layer 2
attributes
Set advanced attributes Set advanced attributes

8.1.1 Setting the General Attributes of Ethernet Interfaces
Before you set the Layer 2 and Layer 3 attributes of an Ethernet port, you need to set the general
attributes of the corresponding Ethernet port. The general attributes of an Ethernet port define
the physical-layer information, such as the port mode, encapsulation type, and maximum frame
length.
Prerequisites
You are an NM user with Administrators rights or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration >
Interface Management > Ethernet Interface from the Function Tree.
Transmission System
445
Step 2 Click the Basic Attributes tab.
Step 3 Select the board and set the parameters as required. For details about the parameters, see A.1.1
Basic Attributes.
NOTE
l When Port Mode is set to Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ.
l When Port Mode is set to Layer 3, Encapsulation Type can be set to 802.1Q only. In this case, the
port can be used to carry the tunnel.
Step 4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation
is successful.
Step 5 Click Close.
----End
8.1.2 Setting the Layer 2 Attributes of Ethernet Ports
After the Layer 2 attributes of an Ethernet port are set, the port can be used for connecting to
the client-side equipment at the edge of an SDH network or for forwarding Ethernet packets
within the SDH network. The Layer 2 attributes of an Ethernet port define the related information
about the data link layer.
Prerequisites
l In Basic Attributes, Port Mode must be set to Layer 2.
Procedure
Step 2 Click the Layer 2 Attributes tab.
Step 3 Select the port and set the parameters as required. For details about the parameters, see A.1.2
Layer 2 Attributes.
NOTE
l QinQ Type Domain can be set only when Encapsulation Type is QinQ.
l TAG can be set only when Encapsulation Type is 802.1Q.
l Default VLAN ID and VLAN Priority can be set only when Encapsulation Type is 802.1Q.
Step 4 Click Apply. Click OK. Then, the Operation Result dialog box is displayed, indicating that
the operation is successful.
Transmission System
446
Step 5 Click Close.
----End
8.1.3 Setting the Layer 3 Attributes of Ethernet Ports
When an Ethernet port is used to carry a tunnel, you need to set the Layer 3 attributes of the
Ethernet port. The Layer 3 attributes of an Ethernet port define the related attributes of the
network layer.
Prerequisites
l In Basic Attributes, Port Mode must be set to Layer 3.
Procedure
Layer 3 Attributes.
NOTE
When changing the IP address of a port, ensure that the IP address of the port and the IP addresses of the
other ports configured with services are not in the same subnet.
is successful.
Step 5 Click Close.
----End
8.1.4 Setting the Advanced Attributes of Ethernet Ports
You can set the routine maintenance parameters by setting the advanced attributes of Ethernet
ports.
Prerequisites
Procedure
Step 2 Click the Advanced Attributes tab.
Transmission System
447
Advanced Attributes.
is successful.
Step 5 Click Close.
----End
8.1.5 Configuring Flow Control
When the flow control function is enabled, the Ethernet port sends a pause frame to the opposite
end and then the opposite end stops transmitting Ethernet packets, if a congestion occurs on the
link. As a result, the congestion is prevented.
Prerequisites
Procedure
Step 2 Click the Flow Control tab.
Flow Control.
is successful.
Step 5 Click Close.
----End
8.2 Configuring the NNIs
Configuring the NNIs is the basis of configuring the packet Ethernet services.
8.2.1 Configuring the NNIs for Ethernet Services Carried by PWs
To configure the Ethernet services that are carried by PWs, you need to set the attributes related
to the port of the PWs.
Prerequisites
Transmission System
448
Procedure
Set the general attributes of the port as follows:
l Enable Port: Enabled
l Port Mode: Layer 3
Set the other parameters as required.
Step 3 Click Apply.
Step 5 Select the desired port and set Enable Tunnel as Enabled. Set Specify IP to Manually. Set IP
Address and IP Mask according to the service planning information. For details about the
parameters, see A.1.3 Layer 3 Attributes.
NOTE
l When changing the IP address of the port, ensure that the IP address of this port and the IP addresses
of the other ports configured with services are not in the same subnet.
is successful.
Step 7 Click Close.
----End
8.2.2 Configuring the NNIs for Ethernet Services Carried by QinQ
Links
Before configuring Ethernet services that are carried by QinQ links, you need to set the general
attributes of the corresponding Ethernet port. The general attributes of an Ethernet port define
the physical-layer information, such as the port mode, encapsulation type, and maximum frame
length.
Prerequisites
Procedure
Step 3 Select the board and set the parameters as required.
Transmission System
449
NOTE
When Port Mode is set to Layer 2, Encapsulation Type can be set to QinQ. When Encapsulation
Type is set to QinQ, the port identifies the QinQ packets.
is successful.
Step 5 Click Close.
----End
8.3 Configuring CES Ports
This topic describes how to configure channelized STM-1 ports and E1 ports to support access
of CES services.
8.3.1 Setting Basic Attributes of Smart E1 Ports
The basic attributes of Smart E1 ports involve parameters such as the port name, port mode, and
encapsulation type.
Prerequisites
U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Packet
Step 3 Select the required port and set the parameters. For details of parameters, see A.2.2 E1 Port.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
Transmission System
450
8.3.2 Setting Advanced Attributes of Smart E1 Ports
The alarm attributes of Smart E1 ports define the parameters such as E1 frame type and loopback
mode.
Prerequisites
U2000
Procedure
Step 2 Click the Advanced Attributes tab.
Step 3 Select the required port and set the parameters for its advanced attributes. For details of
parameters, see A.2.2 E1 Port.
Step 4 Click Apply.
A confirmation dialog box is displayed.
Step 5 Click Yes. Then, close the dialog box that is displayed.
----End
8.3.3 Configuring Channelized STM-1 Ports
When configuring CES services carried by channelized STM-1 ports, you need to set basic
attributes and the frame format in the advanced attributes to ensure that the frame format of the
channelized STM-1 ports is the same as the service encapsulation format.
Prerequisites
Procedure
Step 1 In the NE Explorer, select an NE, and then choose Configuration > Packet Configuration >
Interface Management > SDH Interface from the Function Tree.
Step 2 Click the Basic Attributes tab and set the parameters according to the actual requirements. For
details about the parameters, see A.2.1 Channelized STM-1 Port.
Transmission System
451
NOTE
For a channelized STM-1 board on the OptiX OSN equipment, Port Mode can be set only to Layer 1. In
this case, the OptiX OSN equipment supports access of channelized STM-1 services.
Step 3 After setting the parameters, click Apply.
Step 4 Optional: Select a port and then check its associated services and logical port in the lower
window.
Step 5 Click the Advanced Attributes tab and set the parameters according to the actual requirements.
For details about the parameters, see A.2.1 Channelized STM-1 Port.
Step 7 In the NE Explorer, select the CQ1 and choose Configuration > Interface Management >
Path Configuration from the Function Tree. Set the parameters according to the actual
requirements.
----End
8.4 Setting Serial Port Parameters
When some 64 kbit/s timeslots of a Smart E1 port are used for transmission of ATM services,
these timeslots can be considered as a serial port.
8.4.1 Creating Serial Ports
When creating a serial port, you can set the 64 kbit/s timeslots to be bound with the serial port.
Prerequisites
l The ports that carry services are set to Layer 1.
U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Packet Configuration > Interface Management > Serial Interface from the Function Tree.
Step 3 Click New.
The New Serial Interface dialog box is displayed.
Transmission System
452
Step 4 Set the parameters for the serial port according to the planning information.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
8.4.2 Setting Basic Attributes of Serial Ports
The basic attributes of serial ports involve the parameters such as port mode and encapsulation
type.
Prerequisites
l Serial ports are added.
U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Packet Configuration > Interface Management > Serial Port from the Function Tree.
Step 3 Select the required port and set the parameters for the serial port according to the planning
information.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
8.5 Configuring ATM PWE3 Services
This section describes the operation tasks for configuring ATM PWE3 services on the NMS.
8.5.1 Configuring ATM Interfaces
The OptiX OSN equipment supports the access to ATM services through E1 boards and provides
different access modes at E1/VC12 level and Fractional E1 level. The access at Fractional E1
Transmission System
453
level achieves higher transmission efficiency by allowing multiple types of services (CES
services and ATM services) to be transmitted over 32 E1/VC12 timeslots.
Prerequisites
l The DCN function of the port that carries ATM IMA services is disabled.
For the OptiX OSN equipment, Frame Mode of the packets at the PDH interface or SDH
interfaces can be 30-timeslot or 31-timeslot.
l When Frame Mode is set to 30, timeslots 1-15 and 17-31 of an E1 frame are used to
transport service data, and timeslots 0 and 16 cannot be used for fractional E1.
l When Frame Mode is set to 31, timeslots 1-31 of an E1 frame are used to transport service
data, and timeslot 0 cannot be used for fractional E1.
When creating an IMA group of the fractional E1 level, create a serial port of the 64K
Timeslot level. An IMA group of the E1/VC12 level can be directly created.
Procedure
l Configure an interface at the Fractional E1 level.
1. In the NE Explorer, select an NE and choose Configuration > Packet
2. In the General Attributes tab, select 4-MD1-1(PORT-1) and 4-MD1-1(PORT-2).
Set the Port Mode to Layer 1, and click Apply.
3. Click Advanced Attributes tab, set Frame Format and Frame Mode according to
networking planning. Then, click Apply.
4. Choose Configuration > Packet Configuration > Interface Management > Serial
Interface from the Function Tree. Click New in the Basic Attributes tab, and the
New Serial Interface dialog box is displayed.
5. In the New Serial Interface dialog box, set the Level, Used Board, Used Port, and
64K Timeslot fields, and then click OK. Create serial interfaces of 4-MD1-1
(PORT-1) and 4-MD1-1(PORT-2).
6. Select the created serial interfaces, set Port Mode to Layer 2, and then click Apply.
7. Choose Configuration > Packet Configuration > Interface Management > ATM
IMA Management from the Function Tree. Then, click Configuration in the
Binding tab, and the Bound Path dialog box is displayed.
8. Select the bound board and port, select Fractional E1 for the Level field, and select
Available Resources. Then, click to add the bound board and port to
Selected Bound Paths.
9. Click Apply.
10. In the IMA Group Management tab, select the IMA group 4-MD1-1(PORT-1). Set
the parameters such as IMA Transmit Frame Length and IMA Symmetry Mode
according to the network planning. Then, set IMA Protocol Enable Status to
Enabled. Click Apply.
Transmission System
454
11. On the ATM Interface Management tab, click the IMA group 4-MD1-1(PORT-1).
Then, set the parameters such as MAX. VPI, MAX. VCI for the ports according to
the network planning. Click Apply.
l Configure an interface at the E1 level.
1. In the NE Explorer, select an NE and choose Configuration > Packet
2. In General Attributes tab, select 4-MD1-1(PORT-1) to 4-MD1-2(PORT-1). Set Port
Mode to Layer 2, and click Apply.
3. In Advanced Attributes tab, set Frame Format and Frame Mode according to
networking planning. Then, click Apply.
4. Choose Configuration > Packet Configuration > Interface Management > ATM
IMA Management from the Function Tree. Then, click Configuration in the
Binding tab, and the Bound Path dialog box is displayed.
5. Select E1 for the Level field for the available bound path, and select ports in Available
Resources. Then, click to add the bound board and port to Selected Bound
Paths
6. Click Apply.
7. On the IMA Group Management tab, select the IMA group 4-MD1-1(PORT-1). Set
the parameters such as IMA Transmit Frame Length and IMA Symmetry Mode
according to the network planning. Then, set IMA Protocol Enable Status to
Enabled. Click Apply.
----End
Result
When creating the IMA groups at both ends of the interconnected equipment is complete, you
can query the IMA group status on the U2000 to check whether the IMA groups are in proper
status.
1. In the NE Explorer, click an NE and choose Configuration > Packet Configuration >
Interface Management > ATM IMA Management from the Function Tree.
2. In the IMA Group States tab, click Query. Check Near-End Group Status, Far-End
Group Status, Number of Transmit Links, and Number of Receive Links.
l If Near-End Group Status and Far-End Group Status are displayed as
Operational, the negotiation of the IMA groups succeeded.
l If Near-End Group Status and Far-End Group Status are displayed as other status,
handle the anomaly with reference to Table 8-2.
3. In the IMA Link Status tab, click Query. Check Near-End Receiving Status, Near-End
Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status.
l If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving
Status, and Far-End Transmitting Status are displayed as Usable, it indicates that
the IMA link is normal.
l If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving
Status, and Far-End Transmitting Status are displayed as Unusable, it indicates that
the IMA link is faulty. For details on the IMA link status parameters, see Table 8-3.
Table 8-2 lists the IMA group status parameters.
Transmission System
455
Table 8-2 IMA group status parameters
Near-End/Far-End Group
Status
Description Suggestion
Start-Up This end is in the Start-Up
status and is waiting to be
indicated that the far-end is
also in the Start-Up status.
Start the IMA protocol for the
opposite IMA group and
check whether the IMA
groups are normal.
Start-Up-ACK This is a transitional state.
When both the near-end and
far-end groups start-up, they
move to this state.
The IMA groups are in the
progress of negotiation. Wait
for 500 ms and then check
whether the IMA groups are
normal.
Config-Aborted This state is entered when the
far-end tries to apply
unacceptable configuration
parameters.
Check whether the parameter
settings are consistent for the
IMA groups at both ends. If
not, re-set the inconsistent
parameters to ensure that all
the parameter settings are
consistent for the IMA
groups at both ends.
Insufficient-Links The status is displayed when
the parameter settings for the
IMA groups at both ends are
consistent but the link
resources are insufficient. In
this case, the number of
activated links is less than the
minimum number of
activated links for an IMA
group.
When the fault of the IMA
link is rectified, check
whether the IMA groups are
in proper status.
Blocked The group is blocked. The
group can be blocked for
maintenance purposes while
sufficient links are Active in
both transmitting and
receiving directions.
-
Operational The group is not inhibited
and has sufficient links in
both transmitting and
-

Table 8-3 lists the IMA link status parameters.
Transmission System
456
Table 8-3 IMA link status parameters
Receive/Transmit Status Description Suggestion
Unusable The status is displayed when
an IMA link is added to an
IMA group but the IMA link
is not available because of
fault-caused or manual
suppression.
When the fault of the IMA
link is rectified, check
whether the IMA links are in
proper status.
Usable This status indicates that the
link is availably and it is
displayed when you are
waiting for the remote
receive link to be activated.
In this case, this link is not
added to the cyclical
transmitting process of the
IMA group.
-
Active This status indicates that the
link is activated. If service
cells accessed, they can be
transmitted. This link is
added to the cyclical
transmitting process of the
IMA group.
-

8.5.2 Configuring ATM CoS Mapping
Configure the mapping between ATM service types and PHB service classes to ensure end-to-
end QoS for ATM services.
Prerequisites
The OptiX OSN equipment supports the flexible mapping between ATM service types and PHB
service classes. Table 8-4 lists the default ATM CoS mapping.
Table 8-4 Mapping between ATM service types and PHB service classes
Service Type PHB Service Class
UBR BE
CBR EF
Transmission System
457
Service Type PHB Service Class
RT-VBR AF31
NRT-VBR AF21
UBR+ AF11
PORT-TRANS AF11

NOTE
The default ATM CoS mapping cannot be modified or deleted.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Packet Configuration > QoS
Management > Diffserv Domain Management > ATM CoS Mapping Configuration from
the Function Tree.
Step 2 Click Create. The Create ATM CoS Mapping Relation dialog box is displayed.
Step 3 Set the following parameters in the dialog box.
l Mapping Relation ID
l Mapping Relation Name
l Mapping between the service type and CoS level
Step 4 Click OK.
----End
8.5.3 Creating the ATM Policy
Create the ATM policy to configure the service type and bandwidth for the ATM traffic.
Transmission System
458
Prerequisites
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > QoS
Management > Policy Management > ATM Policy from the Function Tree.
Step 2 Click New. The Create ATM Policy dialog box is displayed.
Step 3 Set the following parameters in the dialog box.
NOTE
When Policy ID and name is set , select one from the drop-down list that contains five levels of ATM service
policies. Alternatively, enter a policy name.
The service encapsulated in AAL5 is sliced into cells. Enable Traffic Frame Discarding Flag determines
whether to discard cells or to discard the complete AAL5 frames for the cells. When Enable Traffic Frame
Discarding Flag is set to Enabled, the equipment will discard the complete AAL5 frames for the cells.
The Scr, Pcr, MBS, and CDVT bucket parameters are functional only when UPC/NPC is enabled for the ATM
policy.
l Policy ID and name
l Service type
l Traffic parameter
l Frame discarding label
l UPC/NPC
Step 4 Click OK.
----End
8.5.4 Creating an ATM Service by Using the Trail Function
This topic describes how to use the trail function to create an ATM PWE3 service tunnel for
ATM signal transmission. The trail function allows you to fast configure the source and sink
nodes of an ATM service and PW attributes.
Prerequisites
l ATM interfaces are configured. If IMA services are transmitted, an IMA group is
configured.
l An ATM policy is configured.
l An MPLS tunnel is used.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set the parameters on the Attributestab.
Transmission System
459
NOTE
l Use a template to configure a service. Specifically, select a template in the Service Template field or
personally create another template.
l Set Service Type to ATM.
l If you set Protection Type to PW APS Protection, select Single Source and Dual Sink or Dual Source
and Single Sink on the Node List. You need to configure one source node and two sink nodes for Single
Source and Dual Sink, and two source nodes and one sink node for Dual Source and Single Sink. The
two PWs are the working PW and protection PW. In addition, PW APS Protection can be set to Single
Source and Single Sink.
Step 3 Select the source and sink NEs for a service.
1. Click Configure Source And Sink. A dialog box is displayed.
2. Select a source NE from Physical Root on the left. Then, the selected NE is displayed in
the upper right pane.
3. In the right portion of NE Panel, all slots and available boards of an NE are displayed.
According to the required service type, select an appropriate board.
4. Select an interface.
5. Set the service access interface attributes. Then, click Add Node. In the lower portion of
the window, the new source and sink NEs are displayed, click OK.
6. Configure the sink NE, protection NE and transit NE with the same method to align with
different protection types.
7. To configure multiple ATM connections for an ATM service at the same time, select
multiple ports for an NE in the same way.
NOTE
The same configuration method is applicable to the sink NE, transit NE, and source NE. This topic considers
the configuration of a source NE as an example.
Step 4 Optional: Click Configure Source And Sink, select the Unterminated in the left, specify the
LSR ID of an unterminated node, and click Add Node. In the lower portion of the window, the
unterminated source and sink NEs are displayed. Then, click OK.
Transmission System
460
NOTE
On a network, if the equipment at one end of a service can be managed by the U2000, and the equipment at the
other end of the service is from another vendor and therefore cannot be managed by the U2000, select
Unterminated to set the LSR ID at the opposite end of the service.
Currently, the OptiX OSN equipment in the same management domain can be used to configure unterminated
trails.
If Protection Type is PW APS Protection, the unterminated node cannot be set.
Step 5 Optional: Click Configure PW Switch Node to add working and protection transit NEs
between the source NE and sink NE.
Step 6 Set parameters for the source and sink NEs that are displayed in Node List. To view the topology
of a configured service, click the Service Topology tab in the upper-right area.
Step 7 Set parameters in the PW pane in the lower left portion of the window.
NOTE
PW ID can be automatically allocated.
Signaling Type can only be set to Static. Forward Label and Reverse Label can be assigned automatically
or manually.
Forward Type and Reverse Type can be set to Static Binding. In this case, manually specify a tunnel in the
Forward Tunnel field.
You may also set the forward tunnel and reverse tunnel by clicking the Service Topology tab in the upper right
area. Right-click a tunnel between the source NE and sink NE, and choose Select Forward Tunnel or Select
Reverse Tunnel from the shortcut menu. In the dialog box that is displayed, select the tunnel for static binding.
Step 8 Click ATM Link. In the dialog box that is displayed, add the ATM connection, and set relevant
parameters of the ATM connection.
NOTE
After you configure VPI/VCI of the source and sink, the U2000 assigns the transit VPI/VCI automatically.
Step 9 Optional: Click Detail. A pane is displayed in the lower right area.
Step 10 Optional: Click the PW QoS tab to configure the global template of a PW. Alternatively, select
one of the templates that are configured in the Global QoS Policy Template field, and set
parameters.
Step 11 Optional: Click the Advanced PW Attribute tab to set parameters for a PW.
Step 12 Optional: If the Protection Type is PW APS Protection, click Protection Parameter to set
the protection parameters.
Step 13 Select the Deploy check box, and click OK.
NOTE
If you clear the Deploy check box, the configuration data information is saved only on the U2000. If you select
the Deploy check box, the configuration data information is saved on the U2000 and applied to NEs. By default,
the Deploy check box is selected.
When you select the Deploy and Enable check boxes, a service is available on NEs only when enabled.
----End
Transmission System
461
Follow-up Procedure
After the service is created successful, the service is displayed in the PWE3 service management
window.
8.6 Managing ATM/IMA Ports
On the OptiX OSN equipment, ATM/IMA ports are mapped into one ATM TRUNK.
8.6.1 Binding ATM TRUNKs
An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial
ports (SPs) that transmit ATM/IMA services.
Prerequisites
l For ATM/IMA E1 services, set Port Mode in PDH Interface to Layer 2.
l For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and
configure 8.4 Setting Serial Port Parameters.
U2000
Procedure
Configuration > Interface Management > ATM IMA Management from the Function Tree.
Step 2 Click the Binding tab.
Step 3 Click Configuration.
The Bound Path dialog box is displayed.
Step 4 Configure the related parameters according to planning information. Then, click to
bind the required E1 ports or SPs to the ATM TRUNK.
Transmission System
462
NOTE
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports, select
E1 in Level.
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports,
select Fractional E1 in Level.
Step 5 Click Apply, and then close the dialog box that is displayed.
----End
Follow-up Procedure
If the IMA group is required, you need to bind the member links of the IMA group with the
ATM TRUNK, enable the IMA protocol for the ATM TRUNK, and then configure the
parameters of the IMA group.
8.6.2 Configuring an IMA group
If the ATM TRUNK binds IAM E1 links or Fractional IMA links, you need to configure the
parameters of the IMA group.
Prerequisites
U2000
Procedure
Transmission System
463
Step 2 Click the IMA Group Management tab.
Step 3 Configure the parameters of the IMA group according to planning information.
NOTE
l When the IMA protocol needs to be enabled for the links bound with the ATM TRUNK, set IMA
Protocol Enable Status to Enabled. Otherwise, set IMA Protocol Enable Status to Disabled.
l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound
with the ATM TRUNK are added to the IMA group.
l The OptiX OSN equipment supports Symmetrical Mode and Symmetrical Operation only.
Therefore, the parameters Minimum Number of Active Transmitting Links and Minimum Number
of Active Receiving Links must be set to the same value. In addition, these two parameters must take
the same value at the two ends of the IMA link.
l On the two ends of the IMA link, you need to set IMA Protocol Version, IMA Transmit Frame
Length, and Maximum Delay Between Links (ms) to the same values.
l When IMA links are interconnected, the parameter Clock Mode needs to be set to different values at
the interconnected ends. To be specific, if an NE is interconnected with a superior device (such as a
BSC), the NE needs to adopt the ITC mode and the BSC needs to adopt the CTC mode; if an NE is
interconnected with an inferior device (such as a NodeB), the NE needs to adopt the CTC mode and
the NodeB needs to adopt the ITC mode.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
8.6.3 Setting ATM Port Parameters
This topic describes how to configure ATM port parameters.
Prerequisites
U2000
Procedure
Step 2 Click the ATM Interface Management tab.
Step 3 Configure and adjust the ATM port attributes.
Transmission System
464
NOTE
l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface on
the common ATM network or to the user-side interface of the PE on the PSN network that transmits ATM
PWE3 services.
l NNI: the port connecting network-side devices. For example, the NNI port applies to the network-side
interface on the common ATM network.
l The ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is mapped
into E1 signals. Therefore, you need to set this parameter to Enabled.
l This parameter must assume the same value on the two ends of an ATM link. Otherwise, packet loss will
occur.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
8.6.4 Querying Running Status of an IMA Group
This topic describes how to query the running status of an IMA group.
Prerequisites
U2000
Procedure
Step 2 Click the IMA Group States tab. Then, close the dialog box that is displayed.
Step 3 Click Query, and then close the dialog box that is displayed.
Step 4 Query the running status of an IMA group.
----End
8.6.5 Querying Link Running Status of an IMA Group
This topic describes how to query the running status of the member links of an IMA group.
Prerequisites
U2000
Transmission System
465
Procedure
Step 2 Click the IMA Link States tab. Then, close the dialog box that is displayed.
Step 3 Click Query, and then close the dialog box that is displayed.
Step 4 Query the running status of the member links of an IMA group.
----End
8.7 ATM Traffic Management
ATM traffic management includes ATM-Diffserv management and ATM policy management.
8.7.1 Creating an ATM Policy
This section describes how to create an ATM policy for an ATM connection.
Prerequisites
U2000
Procedure
Configuration > QoS Management > Policy Management > ATM Policy from the Function
Tree.
Step 2 Click New.
The Create ATM Policy dialog box is displayed.
Step 3 Set ATM policy parameters according to the planning information.
Transmission System
466
Step 4 Click OK.
----End
8.7.2 Modifying an ATM Policy
This section describes how to modify the QoS parameters of an ATM policy.
Prerequisites
U2000
Procedure
Configuration > QoS Management > Policy Management > ATM Policy from the Function
Tree.
Step 2 Click Query.
Transmission System
467
Step 3 Select the required ATM policy and modify its parameters according to the planning information.
Step 4 Click Apply.
----End
8.7.3 Creating an ATM-DiffServ Domain
This section describes how to create an ATM-DiffServ domain. If the default ATM-DiffServ
domain does not serve the purpose, a new ATM-DiffServ domain needs to be created.
Prerequisites
U2000
Procedure
Configuration > QoS Management > Diffserv domain Management > ATM CoS Mapping
Configuration from the Function Tree.
Step 2 Click New.
The Create ATM CoS Mapping dialog box is displayed.
Step 3 Configure an ATM-DiffServ domain according to the planning information.
Transmission System
468
NOTE
l For eight queues, eight PHBs are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX OSN
equipment provides different QoS policies for queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than
delay or jitter limits.
NOTE
AF1 defines three sub-classes: AF11, AF12, and A13. Only AF11 can take effect. This rule also applies to
AF2, AF3, and AF4. To be specific, only AF21, AF31, and AF41 can take effect.
l BE: best effort, applicable to services that do not require special processing.
Step 4 Click OK, and close the dialog box that is displayed.
----End
8.7.4 Modifying an ATM-Diffserv Domain
This section describes how to modify an ATM-DiffServ domain. By performing this operation,
you can modify the mapping between ATM service categories and PHBs.
Prerequisites
U2000
Procedure
Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping
Configuration from the Function Tree.
Transmission System
469
Step 2 Click Query.
Step 3 Select the required ATM-DiffServ domain and modify its parameter settings according to the
NOTE
l For eight queues, eight PHBs are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX OSN
equipment provides different QoS policies for queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than
delay or jitter limits.
NOTE
AF1 defines three sub-classes: AF11, AF12, and A13. Only AF11 can take effect. This rule also applies to
AF2, AF3, and AF4. To be specific, only AF21, AF31, and AF41 can take effect.
l BE: best effort, applicable to services that do not require special processing.
Step 4 Click OK, and close the dialog box that is displayed.
----End
Transmission System
470
8.8 Configuring an MPLS Tunnel
On a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. In
this manner, data packets can be transparently transmitted between NEs. One MPLS tunnel can
carry several PWs. Before configuring a service, you need to configure the MPLS tunnel that
carries the service. On the NMS, you can use the per-NE configuration scheme to configure an
MPLS tunnel.
Context
NOTE
Before configuring MPLS tunnels, you need to plan MPLS tunnels according to the description of MPLS
tunnel numbers in "Functions and Features" of Hardware Description.
8.8.1 Configuring LSR ID
In the Basic Configuration interface, you can set LSR (Label Switch Router) ID.
Prerequisites
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration > MPLS
Management > Basic Configuration from the Function Tree.
Step 2 Set LSR ID.
For details about LSR ID, see A.3.1 Basic Configuration.
NOTE
l When the LSR ID is specified for the first time, a warm-reset occurs on the NE but does not affect
services. If the specified LSR ID is then changed, no warm-reset occurs on the NE and services are not
affected.
l If a tunnel exists, do not change the LSR ID.
----End
8.8.2 Configuring an MPLS Tunnel in an End-to-End Mode
This topic describes how to configure an MPLS tunnel in end-to-end mode by using the NMS.
8.8.2.1 Configuring a Unidirectional MPLS Tunnel
When creating a unidirectional MPLS tunnel in end-to-end mode, you select the source NE, sink
NE, or transit NE directly in the physical topology and then complete creation of the
unidirectional MPLS tunnel on the NMS.
Transmission System
471
Prerequisites
l The port attributes must be set correctly. For details on how to configure the port attributes,
see 8.2.1 Configuring the NNIs for Ethernet Services Carried by PWs.
l The LSR ID of each NE must be set correctly.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu. Then, the Create Tunnel
window is displayed.
Step 2 Set the basic information about the MPLS tunnel. For details about the parameters, see the A.
3.3 Parameters for Configuring a Static Tunnel (in End-to-End Mode).
l Protocol Type: MPLS
l Signaling Type: Static CR
l Select Create Reverse Tunnel.
Step 3 Set the information in NE List of the MPLS tunnel. For details about the parameters, see the A.
Transmission System
472
1. Select the source NE, sink NE, and transit NE, and adjust the position of the NE on the
entire MPLS tunnel.
Three methods can be used to select the source, sink, and transit NEs:
l Method 1: In Physical Topology at the upper right, right-click an NE and choose
Add.
l Method 2: In Physical Topology at the upper right, double-click an NE.
l Method 3:
a. Click the Add button and then choose NE from the drop-down menu.
b. Select an NE from the window that is displayed and then click OK.
NOTE
l You can specify the position of an NE on the entire tunnel by setting NE Role or adjust the
position of an NE on the entire tunnel by clicking Up or Down.
l Select Deploy to deliver the tunnel configuration data to the NEs.
Step 4 Click the Details button and set the information about the tunnel. For details about the
parameters, see the A.3.3 Parameters for Configuring a Static Tunnel (in End-to-End
Mode).
Transmission System
473
NOTE
l Click Auto-Assign following the Tunnel ID field box. Then, Tunnel ID is automatically allocated.
l Click the blank cell under Outbound Interface/Ring of an Ingress node and then click . Select
the output port of the ingress node in the list box that is displayed. Use the same method to select the
input and output ports of the transit node and the input port of the egress node.
l After the output port label is added at the ingress node and transit node, the next-hop address is generated
automatically.
l Click Auto-Assign Label at lower right of the window. Then, Outgoing Label of the ingress node,
Outgoing Label and Incoming Label of the transit node, and Incoming Label of the egress node are
allocated automatically.
l After you set the parameters of the forward tunnel, the parameters of the reverse tunnel are generated
automatically. Therefore, you need not set the parameters of the reverse tunnel manually.
l Click Configure TP OAM(Y.1731) and configure MPLS-TP OAM parameters. Ensure that the OAM
protocol version at the source and sink is Y.1731. Otherwise, the button will be grayed.
l When the configured tunnel bandwidth is larger than the available bandwidth at a port, the NMS will
reports an error. Therefore, plan and configure services based on the actual conditions.
Step 5 Click OK.
----End
8.8.2.2 Configuring a Bidirectional MPLS Tunnel
When creating a bidirectional MPLS tunnel in end-to-end mode, select the source NE, sink NE,
or transit NE directly in the physical topology and then complete creation of the bidirectional
MPLS tunnel on the NMS.
Prerequisites
Transmission System
474
l The port attributes must be set correctly. For details on how to configure the port attributes,
see 8.2.1 Configuring the NNIs for Ethernet Services Carried by PWs.
l You must complete the correct setting of the LSR ID for each NE.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu. Then, the Create Tunnel
window is displayed.
Step 2 Set the basic information about the MPLS tunnel. For details about the parameters, see the A.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: Bidirectional
Step 3 Set the information in NE List of the MPLS tunnel. For details about the parameters, see the A.
Transmission System
475
1. Select the source NE, sink NE, and transit NE, and adjust the position of the NE on the
entire MPLS tunnel.
Three methods can be used to select the source, sink, and transit NEs:
l Method 1: In Physical Topology at the upper right, right-click an NE and choose
Add.
l Method 2: In Physical Topology at the upper right, double-click an NE.
l Method 3:
a. Click the Add button and then choose NE from the drop-down menu.
b. Select an NE from the window that is displayed and then click OK.
NOTE
l You can specify the position of an NE on the entire tunnel by setting NE Role or adjust the
position of an NE on the entire tunnel by clicking Up or Down.
l Select Deploy to deliver the tunnel configuration data to the NEs.
Step 4 Click the Details button and set the information about the tunnel. For details about the
parameters, see the A.3.3 Parameters for Configuring a Static Tunnel (in End-to-End
Mode).
Transmission System
476
NOTE
l Click Auto-Assign following the Tunnel ID field box. Then, Tunnel ID is automatically allocated.
l Click the blank cell under Out Interface of an Ingress node and then click . Select the output
port of the ingress node in the list box that is displayed. Use the same method to select the input and
output ports of the transit node and the input port of the egress node.
l After the output port is added at the ingress node and transit node, the next-hop address is generated
automatically.
l After the input port is added at the egress node and transit node, the reverse next-hop address is
generated automatically.
l Click Auto-Assign Label at lower right of the window. Then, Out Label and Reverse In Label of
the ingress node, In Label, Out Label, Reverse In Label and Reverse Out Label of the transit node,
and In Label and Reverse Out Label of the egress node are allocated automatically.
Step 5 Click OK.
----End
8.8.3 Configuring an MPLS Tunnel on a Per-NE Basis
This topic describes how to configure an MPLS tunnel on a per-NE basis by using the U2000.
8.8.3.1 Configuring a Unidirectional MPLS Tunnel
You can configure an end-to-end unicast MPLS tunnel on a per-NE basis. You need to configure
the MPLS tunnel on each node that the MPLS tunnel traverses.
Transmission System
477
Prerequisites
l You must complete the correct configuration of the port attributes. For details on how to
configure the port attributes, see 8.2.1 Configuring the NNIs for Ethernet Services
Carried by PWs.
Procedure
Step 1 In the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration >
Packet Configuration > MPLS Management > Unicast Tunnel Management from Function
Tree.
Step 2 Click the Static Tunnel tab and click New > Unidirectional Tunnel. Then, the New Unicast
Tunnel dialog box is displayed.
Step 3 Set the parameters of the forward and reverse MPLS tunnels. For details about the parameters,
see A.3.2 Parameters for Configuring a Static Tunnel (on a Per-NE Basis).
NOTE
l When Node Type is set to Egress, Bandwidth(kbit/s) is the same as the tunnel bandwidth in the
Ingress direction and cannot be changed manually.
l Set Next Hop Address to be the IP address of the port of the next node.
Step 4 Click OK to complete the configuration of the static MPLS tunnel.
Step 5 Refer to steps 1-4 to configure the static MPLS tunnels on the intermediate NEs and sink NE.
----End
8.8.3.2 Configuring a Bidirectional Static MPLS Tunnel
You can configure an end-to-end bidirectional MPLS tunnel on a per-NE basis. You need to
configure the MPLS tunnel on each node that the MPLS tunnel traverses.
Prerequisites
l You must complete the correct configuration of the port attributes. For details on how to
configure the port attributes, see 8.2.1 Configuring the NNIs for Ethernet Services
Carried by PWs.
Transmission System
478
Procedure
Packet Configuration > MPLS Management > Unicast Tunnel Management from Function
Tree.
Step 2 Click the Static Tunnel tab and click New > Bidirectional Tunnel. Then, the New Unicast
Bidirectional Tunnel dialog box is displayed.
Step 3 Set the parameters of the bidirectional MPLS tunnels. For details about the parameters, see the
A.3.2 Parameters for Configuring a Static Tunnel (on a Per-NE Basis).
NOTE
l When Node Type is set to Transit, the In port, Out port, Forward In Label, Forward Out Label,
Reverse In Label, Reverse Out Label, Forward Next Hop Address, Reverse Next Hop Address,
Source Node and Sink Node parameters need to be set for the tunnel.
l When Node Type is set to Egress, the In port, Forward In Label, Reverse Out Label, Reverse Next
Hop Address and Source Node parameters need to be set for the tunnel.
Step 4 Click OK to complete the configuration of the static MPLS tunnel.
Step 5 Refer to steps 1-4 to configure the static MPLS tunnels on the intermediate NEs and sink NE.
----End
8.9 Managing MPLS Tunnels
stability of PWE3 services. Therefore, it is crucial to properly manage MPLS tunnels. Managing
MPLS tunnels involves checking the MPLS tunnel topology, deploying MPLS tunnels, deleting
MPLS tunnels, and managing discrete MPLS tunnels.
8.9.1 Searching for MPLS Tunnels
A complete MPLS tunnel has its source and sink NEs. An MPLS tunnel that is created on a per-
NE basis, however, is displayed as a discrete tunnel on the NMS. The tunnel search function on
the NMS helps convert a discrete MPLS tunnel to a complete tunnel, therefore facilitating tunnel
management. This section describes how to search for MPLS tunnels on the NMS.
Transmission System
479
Prerequisites
l MPLS tunnels have been created on a per-NE basis. For details on how to create an MPLS
tunnel on a per-NE basis, see 8.8.3 Configuring an MPLS Tunnel on a Per-NE Basis.
Procedure
Step 1 Choose Service > Search for IP Service from the main menu.
Step 2 In the dialog box that is displayed, set the tunnel discovery policy.
Step 3 Click Start.
Step 4 Click Close.
----End
8.9.2 Checking the MPLS Tunnel Topology
stability of PWE3 services. This section describes how to check the MPLS tunnel topology to
learn configuration information about MPLS tunnels, facilitating tunnel management.
Prerequisites
l MPLS tunnels have been created. For details on how to create an MPLS tunnel, see 8.8
Configuring an MPLS Tunnel.
NOTE
Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the MPLS
tunnel. For details on how to search for an MPLS tunnel, see 8.9.1 Searching for MPLS Tunnels.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Transmission System
480
Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to
MPLS and set Signaling Type to Static CR. Then, click Filter. Query all MPLS tunnels that
meet the filter conditions.
Step 3 Select the MPLS tunnel whose topology information you need to check and click the
Topology tab.
Step 4 In the MPLS tunnel topology view, right-click the NE and choose View Real-Time
Performance from the shortcut menu to check the real-time running status of the MPLS tunnel.
----End
8.9.3 Deploying MPLS Tunnels
After being created on the NMS, MPLS tunnels are stored on the NMS but not immediately
deployed to the corresponding NEs. This section describes how to deploy MPLS tunnels from
the NMS to the corresponding NEs.
Prerequisites
NOTE
Procedure
Step 2 In the dialog box that is displayed, set Deployment Status to Undeployed. Click Filter to check
all undeployed MSPLS tunnels.
Step 3 Select one or more MPLS tunnels to be deployed, right-click the MPLS tunnels, and choose
Deploy and Enable > Deploy from the shortcut menu.
NOTE
After an MPLS tunnel is successfully deployed, its Deployment Status is Deployed.
----End
8.9.4 Modifying MPLS Tunnels
This section describes how to modify MPLS tunnels in end-to-end mode and on a per-NE basis.
Transmission System
481
Prerequisite
NOTE
NOTICE
Modifying an MPLS tunnel may interrupt services.
Modifying an MPLS Tunnel in End-to-End Mode
Step 3 Select the desired tunnel information and click the Hop Information tab. Then, modify the
tunnel parameters.
Step 4 Optional: If only the basic attributes of a tunnel need to be modified, select the desired tunnel
and choose Details from the shortcut menu. Then, modify the basic attributes of the tunnel.
Step 5 Click Apply.
----End
Transmission System
482
Modifying an MPLS Tunnel on a Per-NE Basis
Step 1 Select the source NE of the tunnel from the NE Explorer. Choose Configuration > Packet
Configuration > MPLS Management > Unicast Tunnel Management from the Function
Tree. Then, click the Static Tunnel tab.
Step 2 Select the tunnel information and click Modify. Then, modify the tunnel parameters.
Step 3 Click OK. The Warning dialog box is displayed, prompting a possibility of service interruption.
Step 4 Click OK. The Result dialog box is displayed.
Step 5 Click OK.
Step 6 Repeat steps 1-5 to modify the tunnels on intermediate NEs and sink NE.
----End
8.9.5 Deleting MPLS Tunnels
After being deployed, MPLS tunnels are stored on the NMS and the corresponding NEs. This
section describes how to delete MPLS tunnels from the NMS and corresponding NEs.
Prerequisites
Transmission System
483
NOTE
Procedure
Step 3 Select one or more MPLS tunnels that you need to delete, right-click the tunnels, and choose
Delete Service > Delete from the shortcut menu.
----End
8.9.6 Deleting MPLS Tunnels from the Network Side
After being deployed, MPLS tunnels are stored on the NMS and the corresponding NEs. After
being deleted from the network side, MPLS tunnels are deleted from the NMS only but still
stored on the corresponding NEs. In addition, after being deleted from the network side, MPLS
tunnels are displayed as discrete tunnels on the NMS.
Prerequisites
NOTE
Procedure
Delete Service > Delete from Network Side from the shortcut menu.
----End
Transmission System
484
8.9.7 Deleting MPLS Tunnels from the NE Side
After being deployed, MPLS tunnels are stored on the NMS and the corresponding NEs. After
being deleted from the NE side, MPLS tunnels are deleted from the corresponding NEs only but
still stored on the NMS. In addition, after being deleted from the NE side, MPLS tunnels are
displayed as undeployed.
Prerequisites
NOTE
Procedure
Step 2 In the dialog box that is displayed, set Deployment Status to Deployed. Click Filter to check
all deployed MSPLS tunnels.
Deploy and Enable > Undeploy from the shortcut menu.
NOTE
After an MPLS tunnel is successfully deleted from the NE side, its Deployment Status is Undeployed.
----End
8.9.8 Managing Discrete MPLS Tunnels
MPLS tunnels without source or sink NEs and MPLS tunnels that are deleted from the network
side are displayed as discrete tunnels on the NMS. This section describes how to check discrete
MPLS tunnels, facilitating tunnel management.
Prerequisites
NOTE
Transmission System
485
Procedure
Step 1 Choose Service > Tunnel > Manage Discrete Tunnel from the main menu.
Step 3 Select an MPLS tunnel and click the Hops Information tab. In the tab page, check the port
information and label information about the MPLS tunnel.
Step 4 Optional: Select one or more MPLS tunnels and click Delete.
----End
8.10 Configuring MPLS Tunnel OAM
MPLS OAM effectively detects, confirms, and locates the internal defects of an MPLS network,
and therefore monitors the network performance.
8.10.1 Configuring MPLS Tunnel OAM in End-to-End Mode
Configuring MPLS OAM involves enabling the OAM status of the tunnel, setting the MPLS
OAM parameters of the tunnel, enabling the tunnel CV/FFD check, performing LSP ping test,
and performing the LSP Traceroute test.
Prerequisites
l The MPLS tunnel must be created.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set the filter conditions and then click
Filter.
NOTE
l You can perform filtering by Tunnel Name, Destination IP Address, or Tunnel IP.
l You can also perform filtering by other conditions.
Step 3 In Manage Tunnel, select the MPLS tunnel for which the MPLS OAM needs to be configured.
Step 4 Right-click the MPLS tunnel and then choose MPLS OAM > Enable Y.1711 OAM from the
shortcut menu.
Transmission System
486
Step 5 Right-click the MPLS tunnel and then choose MPLS OAM > Configure Y.1711 OAM from
the shortcut menu. For details about the parameters, see A.3.4 OAM Parameters.
Figure 8-2 Unidirectional Tunnel

Transmission System
487
Figure 8-3 Bidirectional Tunnel

NOTE
When you set these parameters, pay attention the following points:
l Detection Packet Period(ms): Detection Packet Period(ms) can only be set to 1000ms when
Detection Packet Type is CV.
l Detection Packet Period(ms) can be set to several values when Detection Packet Type is FFD. To
ensure that the MPLS tunnel APS switching time is shorter than 50 ms, set Detection Packet Period
(ms) to 3.3 in this example.
l Reverse Tunnel: When the egress node detects a defect, it transmits the BDI packet that carries the
defect information to the ingress node through the reverse tunnel. Therefore, the ingress node can learn
the defect status in time.
l When the Node Type of the Unidirectional tunnel is Egress, you can set the SD Threshold and SF
Threshold.
Step 6 Click Apply.
----End
8.10.2 Configuring the MPLS Tunnel OAM on a Per-NE Basis
Configuring MPLS OAM involves the following operations: enabling the OAM status of the
MPLS tunnel, setting the MPLS OAM parameters for the MPLS tunnel, enabling the tunnel CV/
FFD detection function, performing an LSP ping test, and performing an LSP Traceroute test.
Prerequisites
An MPLS tunnel must be created.
Transmission System
488
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > MPLS
Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameters tab. Select Enabled from the drop-down list of OAM Status.
Step 3 Set the parameters. For the details about the parameters, see A.3.4 OAM Parameters.
NOTE
l Detection Packet Period: When Detection Packet Type is set to CV, Detection Packet Period is
1 s and cannot be changed manually. When Detection Packet Type is set to FFD, Detection Packet
Period can be set manually.
l Reverse Tunnel: After detecting defects, the egress node sends the BDI packets that carry the defect
information over the reverse tunnel to the ingress node, so that the ingress node can learn the defect
status in time.
l When the Node Type of the Unidirectional tunnel is Egress, you can set the SD Threshold and SF
Threshold.
is successful.
Step 5 Click Close.
Step 6 Optional: Perform the CV/FFD. Click the OAM Parameters tab and select a tunnel. Click
OAM Operation and choose Start CV/FFD from the drop-down menu. Then, the Operation
Result dialog box is displayed, indicating that the operation is successful.
NOTE
When the Node Type of the unidirectional tunnel is Ingress, the CV/FFD can be enabled.
Step 7 Optional: Perform a ping test.
1. Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose
Ping Test from the drop-down menu. Then, the Ping Test dialog box is displayed.
Transmission System
489
NOTE
When the Node Type of the tunnel is Ingress, you can perform the ping test.
2. Set the parameters.
3. Click Start Test to check the ping test result.
Step 8 Optional: Perform an LSP Traceroute test.
1. Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose
Traceroute Test from the drop-down menu. Then, the Traceroute Test dialog box is
displayed.
Transmission System
490
NOTE
To support the Traceroute test, the Tunnel Type of the tunnel must be Ingress.
2. Set the parameters.
3. Click Start Test to check the Traceroute test result.
----End
8.11 Configuring MPLS-TP Tunnel OAM
This section describes how to configure MPLS-TP tunnel OAM.
8.11.1 Configuring MPLS-TP Tunnel OAM
This section describes how to smoothly switch the tunnel OAM standard from ITU-T Y.1711
with which the centralized MPLS tunnel OAM complies to ITU-T G.8113.1 with which MPLS-
TP tunnel OAM complies.
Prerequisites
l Tunnels have been created.
Transmission System
491
NOTE
Before managing a tunnel that is created on a per-NE basis, you need to search for the tunnel. For
details on how to search for a tunnel, see "Searching for MPLS Tunnels" in the Configuration
Guide (Packet Transport Domain).
NOTE
The Y.1731 mode indicates the ITU-T G.8113.1 compliant OAM mode.
Procedure
l Switching the tunnel OAM standard on a per-NE basis.
1. On the Main Topology, right-click the required NE and choose NE Explorer from
the shortcut menu.
2. In the NE Explorer, click the NE and choose Configuration > Packet
Configuration > MPLS Management > Unicast Tunnel Management.
3. Click the Static Tunnel tab, and select one or more tunnels.
NOTE
The OAM standard can be switched only for ingress nodes and egress nodes.
4. Right-click and choose Switch to Y.1731 from the shortcut menu. A dialog box is
displayed, indicating the operation result.
5. Click Close.
l Switching the tunnel OAM standard in end-to-end mode.
1. Choose Service > Tunnel > Manage Tunnel from the main menu.
2. In the dialog box that is displayed, set filter conditions; for example, set Protocol
Type to MPLS and set Signaling Type to Static CR. Then, click Filter. Query all
MPLS tunnels that meet the filter conditions.
3. Select one or more tunnels.
4. Right-click and choose OAM > Switch to Y.1731. A dialog box is displayed,
indicating the operation result.
5. Click Close.
----End
Transmission System
492
8.11.2 Configuring MEPs of MPLS-TP Tunnel OAM
This section describes how to configure MEPs of MPLS-TP tunnel OAM. MEPs are end points
of MEGs. MEPs can initiate and terminate OAM packets, which helps to implement fault
management and performance monitoring.
Prerequisites
l Global OAM parameters have been configured.
l Tunnels have been created. The tunnel OAM standard has been switched to ITU-T G.8113.1
with which MPLS-TP tunnel OAM complies.
Procedure
Step 1 On the Main Topology, right-click the required NE and choose NE Explorer from the shortcut
menu.
Step 2 In the NE Explorer, click the NE and choose Configuration > Packet Configuration > MPLS
Management > Unicast Tunnel Management.
Step 3 On the MPLS-TP OAM tab page, click the MEP tab.
Step 4 Set MPLS-TP tunnel OAM parameters for MEPs. Set OAM Status to Enabled.
NOTE
If you want to perform an LCK test on a tunnel, you need to set Lock Status to Lock.
Step 5 Click Apply. A dialog box is displayed, indicating the operation result.
Step 6 Click Close.
----End
8.11.3 Configuring MIPs of MPLS-TP Tunnel OAM
This section describes how to configure MIPs of MPLS-TP tunnel OAM. MIPs are intermediate
points of MEGs. MIPs can forward OAM packets and respond to some OAM packets, but cannot
initiate OAM packets. If MEG ID Type is not IP Based and an LT test needs to be performed,
you need to configure MIPs on transit nodes.
Prerequisites
l Global OAM parameters have been configured.
l Tunnels have been configured on transit nodes. The tunnel OAM standard has been
switched to ITU-T G.8113.1 with which MPLS-TP tunnel OAM complies.
Transmission System
493
Procedure
menu.
Step 3 On the MPLS-TP OAM tab page, click the MIP tab.
Step 4 Click New. In the Create Tunnel MIP dialog box, set MPLS-TP tunnel OAM parameters for
an MIP.
1. Select Tunnel and click . In the Select Tunnel dialog box, select the
corresponding tunnel and click OK.
2. Set MEG ID Type, MEG ID, and MIP ID.
Step 5 Click Apply. A dialog box is displayed, indicating the operation result.
Step 6 Click Close.
----End
8.11.4 Starting CC of MPLS-TP Tunnel OAM
This section describes how to start CC of MPLS-TP tunnel OAM. CC is used to check the
connectivity between two MEPs in an MEG.
Prerequisites
l Tunnels have been created, and MPLS-TP OAM has been configured.
Procedure
menu.
Step 4 Select one or more tunnels and set OAM Status to Enabled.
Transmission System
494
Step 5 Choose OAM Operation > Start CC. A dialog box is displayed, indicating the operation result.
Step 6 Click Close.
----End
8.11.5 Enabling AIS of MPLS-TP Tunnel OAM
If AIS of MPLS-TP tunnel OAM is enabled, a fault on a tunnel triggers AIS packet transmission
at the PW layer and an AIS alarm is generated.
Prerequisites
Procedure
menu.
Step 4 Select one or more tunnels and set AIS Status to Enabled.
Step 5 Click Apply.
----End
8.11.6 Performing LB of MPLS-TP Tunnel OAM
This section describes how to perform LB of MPLS-TP tunnel OAM. LB is used to check the
bidirectional connectivity between an MEP and an MIP or between a pair of MEPs.
Prerequisites
Transmission System
495
Procedure
menu.
Step 4 Select a tunnel and set OAM Status to Enabled.
NOTE
An LB test can be started only when OAM is enabled.
Step 5 Choose OAM Operation > Start LB. The LB Test dialog box is displayed.
Step 6 Set LB test parameters.
Step 7 Click Start Test. View the test result in Test Result.
Transmission System
496
----End
8.11.7 Querying the Status of MPLS-TP Tunnel OAM
This section describes how to query the status of MPLS-TP tunnel OAM.
Prerequisites
Procedure
menu.
Step 4 Select one or more tunnels and choose OAM Operation > Query LSP Status. View the status
of MPLS-TP tunnel OAM.
Step 5 Click Close.
----End
8.12 Configuring Tunnel APS
Tunnel APS protection is implemented based on the APS protocol. If tunnel APS is configured,
the services are switched from the working tunnel to the protection tunnel after the working
tunnel is faulty.
Transmission System
497
8.12.1 Configuring a Tunnel APS in End-to-End Mode
You can configure tunnel APS to protect the MPLS tunnel .Tunnel APS can be configured as
the 1:1 mode. When configuring tunnel APS, you need to configure tunnel APS on both the
source NE and the sink NE of the MPLS tunnel.
Prerequisites
l The MPLS working and protection tunnels must be created.
l The MPLS OAM of each MPLS tunnel in the protection group must be enabled
(Unidirectional tunnel need to enable the OAM of forward and reverse tunnel).
NOTE
The protection tunnel should not carry any extra services.
Procedure
Step 1 Choose Service > Tunnel > Create Protection Group from the Main Menu.
Step 2 In Create Protection Group, set Basic Information of the protection group.
Step 3 Click Add at the lower left of the Create Protection Group window. In the Set Filter
Criteria dialog box that is displayed, set the filter conditions and then click Filter.
NOTE
l You can perform filtering by Tunnel Name, Destination IP Address, or Tunnel IP.
l You can also perform filtering by other conditions.
Step 4 Select the tunnel in Select Tunnel dialog box that is displayed and then Click OK.
NOTE
l When configuring MPLS tunnel APS for unidirectional tunnels, you need to select four tunnels, which
function as the Forward Working tunnel, Forward Protection tunnel, Backward Working tunnel,
and Backward Protection tunnel.
l When configuring MPLS tunnel APS for bidirectional tunnels, you need to select two tunnels, which
function as the Working tunnel, and Protection tunnel.
Step 5 In the Tunnels field box, specify the tunnel type.
Transmission System
498
NOTE
l Set four unidirectional tunnels to be the Forward Working tunnel, Forward Protection tunnel,
Backward Working tunnel, and Backward Protection tunnel.
l Set two bidirectional tunnels to be the Working tunnel, and Protection tunnel.
Step 6 Set the MPLS tunnel APS attributes at the lower right of the window.
NOTE
l When configuring tunnel APS on a per-NE mode, set Protocol Status to Disabled. Start the protocol
only when tunnel APS is successfully configured at both ends of the MPLS tunnel.
l When configuring tunnel APS in end-to-end mode, set Protocol Status to Enabled.
Step 7 Click OK. The configuration for tunnel APS is complete.
----End
8.12.2 Configuring Tunnel APS on a Per-NE Basis
You can configure tunnel APS to protect MPLS tunnels. You can configure a 1:1 tunnel APS
protection group. You need to configure tunnel APS on the source and sink NEs of the MPLS
tunnel.
Prerequisites
l The working and protection MPLS tunnels must be created.
l The MPLS OAM of each MPLS tunnel in the protection group must be enabled
(Unidirectional tunnel need to enable the OAM of forward and reverse tunnel).
NOTE
The protection MPLS tunnel cannot carry any extra services.
Procedure
Packet Configuration > APS Protection Management from the Function Tree.
Transmission System
499
Step 2 Click New. Then, the New Tunnel Protection Group dialog box is displayed.
Step 3 Set the parameters for the MPLS tunnel protection group. Select the working and protection
MPLS tunnels.
l Protection Type: You can set Protection Type to 1:1.
l Switching Mode: You can set Switching Mode to Single-Ended or Dual-Ended.
l BDI Status: If Switching Mode is set to Single-Ended, set BDI Status to Enabled so that
BDI packets will be sent to the ingress node to trigger protection switching on the ingress
node when the egress node detects a fault.
l Revertive Mode: You can set Revertive Mode to Non-Revertive or Revertive. If you set
Revertive Mode to Revertive, you can specify the WTR time.
l Hold-off Time (100ms): The unit is 100 ms. You can set Hold-off Time (100ms) to be an
integer from 0 to 100, namely, 0 to 10 seconds.
NOTICE
When creating an APS protection group, you need to set Protocol Status to Disabled. Enable
the protocol only after the configuration of the APS protection group is complete on the source
and sink NEs.
Transmission System
500
Step 4 Click OK. The MPLS tunnel protection group is configured successfully.
NOTE
The bandwidth of the protection MPLS tunnel must be higher than the bandwidth of the working MPLS
tunnel. To increase the bandwidth of the working MPLS tunnel after the protection group is created, increase
the bandwidth of the protection MPLS tunnel first.
Step 5 Refer to steps 1-4 to configure the protection group on the sink NE.
Step 6 Enable the protocol of the MPLS APS protection group.
1. In the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration
> Packet Configuration > APS Protection Management from the Function Tree.
2. Right-click a created APS protection group and choose Start Protocol from the shortcut
menu.
3. A dialog box is displayed, indicating that the operation is successful. Protocol Status of
the APS protection group changes to Enabled.
----End
8.13 Managing Tunnel APS Protection Groups
stability of PWE3 services. Tunnel APS provides protection for MPLS tunnels. Therefore, it is
crucial to properly manage tunnel APS protection groups. Managing tunnel APS protection
groups involves automatically discovering, deploying, modifying, and deleting tunnel APS
protection groups.
8.13.1 Automatically Discovering Protection Groups
stability of PWE3 services. This section describes how to find tunnel APS protection groups by
using the automatic discovery function of the NMS, facilitating protection group management.
Prerequisites
l Tunnel APS protection groups have been created. For details on how to create a tunnel APS
protection group, see 8.12 Configuring Tunnel APS.
Procedure
Step 1 Choose Service > Tunnel > Search for Protection Group from the main menu.
Step 2 In the dialog box that is displayed, click Add. In the dialog box that is displayed, select the NE
for which you need to configure a tunnel APS protection group and then click OK.
Step 3 Click OK.
NOTE
After protection groups are automatically discovered, the NMS displays a dialog box showing the number
of found protection groups.
----End
Transmission System
501
8.13.2 Deploying Tunnel APS Protection Groups
After being created on the NMS, Tunnel APS protection groups are stored on the NMS but not
immediately deployed to the corresponding NEs. This section describes how to deploy tunnel
APS protection groups from the NMS to the corresponding NEs.
Prerequisites
Procedure
Step 1 Choose Service > Tunnel > Manage Protection Group from the main menu.
all undeployed tunnel APS protection groups.
Step 3 Select one or more tunnel APS protection groups to be deployed, right-click the protection
groups, and choose Deploy and Enable > Deploy from the shortcut menu.
NOTE
After a tunnel APS protection group is successfully deployed, its Deployment Status is Deployed.
----End
8.13.3 Renaming a Tunnel APS Protection Group
Basic information about a tunnel APS protection group can be represented by an appropriate
protection group name. This section describes how to change the name of a tunnel APS protection
group.
Prerequisites
Procedure
Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to 1:1.
Then, click Filter. Query all tunnel APS protection groups that meet the filter conditions.
Step 3 Select a tunnel APS protection group whose name you need to change, and then click Modify.
Transmission System
502
----End
8.13.4 Deleting Tunnel APS Protection Groups
After being deployed, Tunnel APS protection groups are stored on the NMS and the
corresponding NEs. This section describes how to delete tunnel APS protection groups from the
NMS and corresponding NEs.
Prerequisites
Procedure
Step 3 Select one or more tunnel APS protection groups that you need to delete, right-click the
protection groups, and choose Delete Service > Delete from the shortcut menu.
NOTE
If a tunnel APS protection group's Deployment Status is Deployed, right-click the protection groups, and
choose Undeploy from the shortcut menu.
----End
8.13.5 Deleting Tunnel APS Protection Groups from the Network
Side
corresponding NEs. After being deleted from the network side, Tunnel APS protection groups
are deleted from the NMS only but still stored on the corresponding NEs.
Prerequisites
Transmission System
503
Procedure
protection groups, and choose Delete Service > Delete from Network Side from the shortcut
menu.
----End
8.13.6 Deleting Tunnel APS Protection Groups from the NE Side
corresponding NEs. After being deleted from the NE side, Tunnel APS protection groups are
deleted from the corresponding NEs only but still stored on the NMS.
Prerequisites
Procedure
Step 2 In the dialog box that is displayed, set Deployment Status to Deployed. Click Filter to check
all deployed tunnel APS protection groups.
protection groups, and choose Deploy and Enable > Undeploy from the shortcut menu.
NOTE
After a tunnel APS protection group is successfully deleted from the NE side, its Deployment Status is
Undeployed.
----End
8.14 Configuring ML-PPP
This section describes how to configure ML-PPP.
Transmission System
504
8.14.1 Changing the E1 Frame Format and Frame Mode for a
Channelized STM-1
By default, the E1 frame format in a channelized STM-1 is CRC-4 multiframe and the frame
mode is PCM31.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The required board is already added on the NE panel.
U2000
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Path Configuration from the Function Tree.
Step 2 Set the required parameters.
Step 3 Click Apply.
----End
8.14.2 Creating MP Groups
To allow an MLPPP link to carry MPLS tunnels, you need to create an MP group.
Prerequisites
l Multiple serial ports have been configured with the PPP protocol activated.
U2000
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration > Packet
Configuration > Interface Management > MP Group Management from the Function Tree.
Step 3 Click New.
Step 4 Set MP group parameters.
Transmission System
505
Step 5 Click OK. Then, close the operation result dialog box that is displayed.
----End
8.15 Configuring NE-Level TPID
When PW-carried Ethernet services use the request VLAN function, the request VLAN tags
added to the services must contain the same TPID so that the services can run properly.
Prerequisites
Procedure
Step 1 In NE Explorer, select the desired NE and choose Configuration > Packet Configuration >
TPID Configuration from the navigation tree.
Step 2 Set TPID(Hexadecimal).
Transmission System
506
Step 3 Click Apply.
----End
8.16 Configuring the Address Resolution
On the NMS, the IP address and MAC address of each ARP table item can be created and queried.
Prerequisites
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration > Control
Plane Configuration > Address Parse from the Function Tree.
Step 2 Click Create. Then, the Add Address Parse dialogue box is displayed.
Step 3 Set the IP address and MAC address for each ARP table item, and then click Apply. For details
about the parameters, see A.4 Parameter Description: Address Parse.
CAUTION
When configuring the MAC address of each ARP table item, ensure that the first digit of the
address is an even number.
Step 4 After the setting is complete, click OK.
CAUTION
Configuring the address resolution refers to creating the static ARP table items. To delete the
dynamic ARP table items, click Clear. This operation, however, clears all the contents in the
ARP table items and interrupts the services. Hence, exercise caution when performing this
operation.
NOTE
Click Delete to delete the contents of the static ARP table items.
----End
Transmission System
507
8.17 Configuring E-Line Services
This topic describes how to configure E-Line services, including UNI-UNI E-Line services, E-
Line services carried by ports, E-Line services carried by PWs, and E-Line services carried by
QinQ links.
8.17.1 Creating a QinQ Link
In the case of the QinQ link, a layer of VLAN tag is added to the packets that are accessed over
a port, through QinQ encapsulation. Hence, the packets from different VLANs on the user-side
network can be encapsulated and then transmitted to the same VLAN on the transport network.
In this manner, the VLAN resources on the transport network are saved. The E-Line service can
be carried by the QinQ links on the network side.
Prerequisites
The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must
be the QinQ mode.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration >
Ethernet Service Management > QinQ Link from the Function Tree.
Step 2 Click New. Then, the New QinQ Link window is displayed.
Step 3 Click the Basic Attributes tab. Set QinQ Link ID, Board, Port and S-Vlan ID.
Step 4 Click OK.
----End
8.17.2 Creating a VLAN Forwarding Table Item
After the corresponding VLAN forwarding table item is created, the VLAN IDs of the service
packets can be switched at the source or sink end of the E-Line service.
Prerequisites
l The corresponding Ethernet board must be added to NE Panel.
l The UNI-UNI E-Line service must be created.
U2000
Transmission System
508
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Packet
Configuration > Ethernet Service Management > E-Line Service from the Function Tree.
Step 2 Select the E-Line service whose VLAN forwarding table entries need to be configured.
Step 3 Click the VLAN Forwarding Table Item tab.
Step 4 Click New.
Step 5 Set the attributes of the new VLAN forwarding table item.
----End
8.17.3 Configuring UNI-UNI E-Line Services
This topic describes how to create an E-Line service that is transparently transmitted end to end
or is transmitted based on VLANs.
Prerequisites
l The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line service.
U2000
Procedure
Configuration > Ethernet Service Management > E-Line Service from the Function Tree.
Step 2 Click New.
The New E-Line Service dialog box is displayed.
Step 3 Set Direction to UNI-UNI.
Step 4 Configure the attributes of the E-Line service.
Transmission System
509
----End
8.17.4 Configuring NNI-NNI E-Line Services
This topic describes how to configure S-VLAN-based E-Line services.
Prerequisites
l Ethernet boards have been added on the NE Panel.
l For ports that carry services, Port Mode has been set to Layer 2 and Encapsulation
Type has been set to QinQ.
U2000
Procedure
Tree.
Step 2 Click New.
The New E-Line Service dialog box is displayed.
Step 3 Set Direction to NNI-NNI.
Step 4 Set relevant attributes of the E-Line service.
Transmission System
510
----End
8.17.5 Configuring E-Line Services Carried by PWs in End-to-End
Mode
In the case of a UNI-NNI E-Line service carried by PWs, the user data is received by a UNI and
is then sent to a PW over an NNI. In this manner, point-to-point transparent transmission of the
user data is achieved. This topic describes how to configure the source node, sink node, and PW
attributes of UNI-NNI E-Line services carried by PWs on a GUI of the NMS, therefore quickly
completing the E-Line service configuration.
Prerequisites
l The MPLS tunnel that carries the PWs must be configured.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
Step 2 Set the attributes. For details about the parameters, see A.6 Parameter Description: E-Line
Services (End-to-End Mode).
Transmission System
511
NOTE
l You can configure the E-Line service according to the service template. That is, you can select a
template or create a service template in the Service Template field.
l Set Service Type to ETH.
l For rules of setting Protection Type, refer to descriptions about PW protection.
Step 3 Configure the source NE and sink NE of the PWE3 service.
NOTE
The configuration method is the same for the sink NE and source NE. Therefore, only the example for
configuring the source NE is provided as follows.
1. Under Node List, click Configure Source and Sink. Then, a dialog box is displayed.
2. Select a source NE from Physical Topology on the left. Select the service access port in
the pane on the right and set the associated parameters.
NOTE
l Priority Type is optional. It is set to 802.1P when packets are forwarded based on PORT+VLAN
+VLAN PRI.
l Priority Field is optional. It is set to any integer from 0 to 7 if packets need to be forwarded
based on PORT+VLAN+VLAN PRI. 7 is the highest priority.
3. After setting the parameters, click Add Node.
4. Refer to Step b and Step c and configure the sink NE.
5. Click OK.
NOTE
l To configure the source and sink NEs of the PWE3 service, you can also double-click the source and
sink NEs in Physical Topology and then set the SAI attributes in the dialog box that is displayed.
l When PW-carried Ethernet services use the request VLAN function, the request VLAN tags added to
the services must contain the same TPID so that the services can run properly.
l When Service Tag and PW Type are set to Service and Ethernet Tagged Mode, respectively, the
TPID of the port must be the same as that of the NE. Configure the TPID for the port first, and then
for the NE.
Step 4 Optional: Under Node List, click Configure PW Switch Node to add the switching NE
between the source and sink NE.
Step 5 Optional: Click Service Topology to check the configured service topology at upper right.
Step 6 Under PW, set the basic attributes of the PWs.
NOTE
l Double-click the blank box under Forward Tunnel and Reverse Tunnel, click , and then select
the tunnel that carries the PWs from the list.
l The PW ID can be Auto-Assign.
Transmission System
512
Step 7 Click Detail and configure the advanced attributes for PW-carried E-Line services. For details
about the parameters, see A.6 Parameter Description: E-Line Services (End-to-End
Mode).
Step 8 Optional: Click the SAI QoS tab and set the QoS of the service access port.
Step 9 Optional: Click the PW QoS tab and set the QoS of the PW.
Step 10 Optional: Click the Advanced PW Attribute tab and set the parameters associated with the
PW.
NOTE
l The Y.1731 mode indicates the ITU-T G.8113.1 compliant OAM mode.
Step 11 Optional: If alarms are automatically configured after the configuration of services, click ETH
OAM CC so that the connectivity check can be continuous.
NOTE
E-Line services carried by PWs based on neither VLAN priorities nor VLAN switching support ETH OAM
CC tests.
Step 12 Click OK.
----End
8.17.6 Configuring E-Line Services Carried by PWs on a Per-NE
Basis
In the case of the UNI-NNI E-Line services carried by PWs, the user data is accessed from a
UNI and is then sent to an NNI where the user data is carried by a PW. In this manner, the point-
to-point transparent transmission of the user data is realized.
Prerequisites
Procedure
Ethernet Service Management > E-Line Service from Function Tree.
Step 2 Click the UNI tab and click New. Then, the New E-Line Service dialog box is displayed.
Step 3 Set the parameters in the dialog box. For details, see A.5.1 E-Line Service Parameters.
Transmission System
513
NOTE
l Set Bearer Type to PW.
l You can set several VLAN values in Source VLANs. Separate consecutive values with "-" and separate
inconsecutive values with ",". For example, The VLAN values may be "1,3,5,8-10".
l If the MPLS tunnel carrying the PWs is not configured with MPLS tunnel APS, you can set Protection
Type to PW APS. In this case, you need to configure both the service PW and protection PW to
implement PW APS protection.
l PRI is optional. It is set to any integer from 0 to 7 when packets are forwarded based on PORT+VLAN
+VLAN PRI. 7 is the highest priority.
l Service Tag Role is set to User or Service.
l User: C-VLAN/S-VLAN tags in user packets are used as user VLAN tags. When a packet leaves
a PW, its user VLAN ID will not be changed.
l Service: C-VLAN/S-VLAN tags in user packets are used as service VLAN tags. When a packet
leaves a PW, its service VLAN ID will be changed to the VLAN ID configured for the services.
Step 4 Click Configure PW. Then, the Configure PW dialog box is displayed. In the dialog box, set
the PW-related parameters.
NOTE
l You can configure the protection PW only if Protection Type is set to PW APS.
l When PW Type is Ethernet Tagged Mode or Ethernet:
l Ethernet: C-VLAN/S-VLAN tags of packets are encapsulated into PWs without changes, and
transparently transmitted to downstream sites.
l Ethernet Tagged Mode: A VLAN tag specified by Request VLAN is added to packets.
l Set other PW-related parameters according to the planning information.
Step 5 Click OK to close the Configure PW dialog box.
Step 6 Click OK. Then, the Confirm dialog box is displayed.
Step 7 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set the
OAM-related parameters.
Transmission System
514
NOTE
Before setting the OAM-related parameters, you need to configure the MD first.
----End
8.17.7 Creating UNI-NNI E-Line Services Carried by QinQ Links
In the case of the UNI-NNI E-Line services carried by the QinQ link, the user data is accessed
from a UNI and is then sent to an NNI where the user data is carried by a QinQ link. Multiple
VLANs on the user network are encapsulated in QinQ mode into one VLAN on the transport
network. In this manner, the VLAN resources on the transport network are saved.
Prerequisites
l The QinQ link must be created for the NNIs.
l The services carried by the QinQ link do not support the creation of any maintenance point
(MP).
Procedure
Ethernet Service Management > E-Line Service from the Function Tree.
Step 2 Click the UNI tab and then click New. Then, the New E-Line Service dialog box is displayed.
Step 3 Set the parameters in the dialog box. For details of the parameters, see A.5.1 E-Line Service
Parameters.
NOTE
l Set Direction to UNI-NNI.
l Set Bearer Type to QinQ Link.
l Select a created QinQ link in QinQ Link ID.
Step 4 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is
----End
8.17.8 Creating E-Line Services over Native Ethernet in End-to-End
Mode
This section describes how to create E-Line services over Native Ethernet in end-to-end mode.
Prerequisites
l Port attributes have been correctly configured for each board on an NE.
l Fibers or cables for Ethernet links between NEs are connected on the main topology.
l Data is synchronized between the NE and the NMS.
Transmission System
515
Procedure
Step 1 Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
Step 2 Set basic attributes for the E-Line service.
The rules for setting these parameters are as follows:
l Service Name: This parameter is set according to the service plan or user convention.
l BPDU Private Service: This parameter is set to No.
l Customer: This parameter is set as required by a user.
l Remarks: This parameter is set as required by a user.
Step 3 Configure the source and sink of the E-Line service.
1. Double-click the source NE in the Physical Topology tab page.
The Select Source dialog box is displayed.
2. Select the source board and source port.
3. See the following table to set C-VLAN and S-VLAN for the service source.
Service Type C-VLAN S-VLAN
Transparently transmitted point-to-point
E-Line service
- -
VLAN-based E-Line service Set according to the
service plan
-
QinQ-based E-Line
service
PORT-based
service flow
sourced from a UNI
port
- -
PORT+C-VLAN-
based service flow
sourced from a UNI
port
Set according to the
service plan
-
Service flow
sourced from an
NNI port
- Set according to the
service plan

4. Click OK.
5. Refer to Step 3 to configure the sink of the E-Line service.
Transmission System
516
Step 4 Select Deploy and ETH OAM CC.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) within the same maintenance association (MA), and activates a continuity check (CC).
Step 5 Click Calculate Route.
The routes created are displayed in the Physical Topology tab page.
NOTE
If the routes created are incorrect, perform Step 6 and click Calculate Route.
Step 6 Optional: Configure the explicit node for the E-Line service.
1. Click Add.
The Select NE dialog box is displayed.
2. Select the NE in the left area and click .
3. Click OK.
4. Set Interface in the Explicit Node tab page.
Step 7 Optional: Under Node List, set C-VLANs and S-VLANs for each node based on the node type
and service type.
Table 8-5 Source NE
Service Type Out C-VLAN Out S-VLAN
Transparently transmitted point-to-point E-
Line service
Empty Empty
VLAN-based E-Line
service
VLAN switching not
performed on Out
Interface
Empty Empty
VLAN switching
performed on Out
Interface
service plan
Empty
QinQ-based E-Line
service
PORT-based service
flow with a UNI port
Out Interface
Empty Empty
Transmission System
517
Service Type Out C-VLAN Out S-VLAN
PORT+C-VLAN-
based service flow
with a UNI port Out
Interface
service plan
Empty
Service flow with an
NNI port Out
Interface
Empty Set according to the
service plan

Table 8-6 Sink NE
Service Type In C-VLAN In S-VLAN
Line service
Empty Empty
VLAN-based E-Line
service
VLAN switching not
performed on In
Interface
Empty Empty
VLAN switching
performed on In
Interface
service plan
Empty
QinQ-based E-Line
service
PORT-based service
flow with a UNI port
In Interface
Empty Empty
PORT+C-VLAN-
based service flow
with a UNI port In
Interface
service plan
Empty
Service flow with an
NNI port In
Interface
service plan

Table 8-7 Intermediate NE
Service Type Out C-VLAN and
In C-VLAN
Out S-VLAN and
In S-VLAN
Line service
Empty Empty
Transmission System
518
Service Type Out C-VLAN and
In C-VLAN
Out S-VLAN and
In S-VLAN
VLAN-based E-Line
service
VLAN switching not
performed on Out
Interface or In
Interface
Empty Empty
VLAN switching
performed on Out
Interface and In
Interface
service plan
Empty
QinQ-based E-Line
service
PORT-based service
flow with UNI ports
Out Interface and In
Interface
Empty Empty
PORT+C-VLAN-
based service flow
with UNI ports Out
Interface and In
Interface
service plan
Empty
Service flow with
NNI ports Out
Interface and In
Interface
service plan

Step 8 Click OK.
----End
8.18 Configuring E-LAN Services
This section describes how to configure E-LAN services.
8.18.1 Configuring IEEE 802.1d Bridge-Based E-LAN Services
The E-LAN service refers to the dynamic transmission of the Ethernet service in the multipoint-
to-multipoint mode through MAC address.
Prerequisites
l The Ethernet board has been added on the NE Panel.
l For ports carrying IEEE 802.1d bridge-based E-LAN services, Port Mode has been set to
Layer 2 and Encapsulation Type has been set to Null.
Transmission System
519
U2000
Procedure
Configuration > Ethernet Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The New E-LAN Service dialog box is displayed.
Step 3 Configure the attributes of the bridge.
NOTE
l The port parameter varies according to Tag Type.
Step 4 Configure the port that is mounted to the bridge on the UNI side of the E-LAN service.
1. Click the UNI tab.
2. Click Configuration, and then select the port that needs to be mounted to the bridge in the
Configure Port dialog box that is displayed.
3. Configure the ports mounted to the bridge on the UNI side.
4. Click OK.
Step 5 Optional: Configure the split horizon group.
1. Click the Split Horizon Group tab.
2. Click New, then the New Split Horizon Group dialog box is displayed.
3. Select a port from Available Interfaces, and then click .
Transmission System
520
4. Click OK.
----End
8.18.2 Configuring IEEE 802.1q Bridge-Based E-LAN Services
An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several
switching domains.
Prerequisites
l For the ports that carry the IEEE 802.1q bridge-based E-LAN services, Port Mode has
been set to Layer 2 and Encapsulation Type has been set to 802.1Q.
U2000
Procedure
Step 2 Click New.
Step 3 Set basic attributes of the E-LAN service as planned.
NOTE
Set Tag Type to C-Aware.
Transmission System
521
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration.The Configure Port dialog box is displayed.
4. Click OK.
4. Click OK.
----End
8.18.3 Configuring IEEE 802.1ad Bridge-Based E-LAN Services
An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several
switching domains.
Transmission System
522
Prerequisites
l For the board that transmits the IEEE 802.1ad bridge-based E-LAN service, Port Mode
has been set to Layer 2.
U2000
Procedure
Step 2 Click New.
Step 3 Set parameters of the E-LAN service as planned.
NOTE
Set Tag Type to S-Aware.
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration. The Configure Port dialog box is displayed.
4. Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1. Click NNI.
2. Click Configuration.The Configure Port dialog box is displayed.
3. Configure the ports mounted to the bridge on the NNI side.
4. Click OK.
Transmission System
523
4. Click OK.
----End
8.18.4 Changing Logical Ports Connected to a VB
This section describes how to change the logical ports connected to a VB and the attributes of
the ports.
Prerequisites
l The E-LAN services must be created.
U2000
Procedure
Step 2 Add or delete logical ports connected to a VB.
NOTE
l To add or delete ports connected to the VB on the UNI side, click the UNI tab.
l To add or delete ports connected to the VB on the NNI side, click the NNI tab.
1. Click Configuration. In the Configure Port dialog box that is displayed, select the port
to be added to or deleted from the list of ports connected to the VB.
2. Optional: Click to add ports to the list of ports connected to the VB.
3. Optional: Click to delete ports from the list of ports connected to the VB.
Transmission System
524
NOTE
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
4. In Selected Port List, set the attributes of the ports connected to the VB.
5. Click OK.
A dialog box is displayed for confirmation.
6. Click Yes.Then, close the dialog box that is displayed.
----End
8.18.5 Creating E-LAN Services over Native Ethernet in End-to-End
Mode
This section describes how to create E-LAN services over Native Ethernet in end-to-end mode.
Prerequisites
l Port attributes have been configured for each board on an NE.
l Fibers or cables for Ethernet links between NEs are connected on the main topology.
l Data is synchronized between the NE and the NMS.
Procedure
Step 1 Choose Service > Native Ethernet Service > Create E-LAN Service from the Main Menu.
Step 2 Set basic attributes for the E-LAN service.
l Service Type: This parameter takes the default value E-LAN.
l Service Name: This parameter is set according to the service plan or user-defined
conventions.
l Customer: This parameter is set as required by a user.
l Remarks: This parameter is set as required by a user.
Transmission System
525
Step 3 Configure bridge-mounted ports for the E-LAN service.
1. Double-click the NE in the Physical Topology tab page.
The Select Node and Port dialog box is displayed.
2. See the following table to set Tag Type.
Service Type Tag Type
IEEE 802.1d bridge-based E-LAN
service
Tag-Transparent
IEEE 802.1q bridge-based E-LAN
service
C-Aware
IEEE 802.1ad bridge-based E-LAN
service
S-Aware

3. Select the port to be mounted from Available Interface and click .
NOTE
If Port Mode of a port is Layer 3, the port is not displayed under Available Interface. To display
the port, right-click the NE in the Physical Topology tab page, choose NE Explorer from the shortcut
menu, and set Port Mode to Layer 2 by referring to 8.1.1 Setting the General Attributes of
Ethernet Interfaces.
4. See the following table to set C-VLAN, S-VLAN, and Encapsulation Type.
Table 8-8 E-LAN service types
Service Type C-VLAN S-VLAN Encapsulatio
n Type
IEEE 802.1d bridge-based E-LAN
service
- - Null
Transmission System
526
Service Type C-VLAN S-VLAN Encapsulatio
n Type
IEEE 802.1q bridge-based E-LAN
service
Set according
to the service
plan
- IEEE 802.1q
IEEE
802.1ad
bridge-
based E-
LAN service
PORT-based
service flow whose
bridge-mounted
port is a UNI port
- Set according
to the service
plan
Null
PORT+C-VLAN-
based service flow
whose bridge-
mounted port is a
UNI port
Set according
to the service
plan
Set according
to the service
plan
IEEE 802.1q
Service flow whose
bridge-mounted
port is an NNI port
- Set according
to the service
plan
QinQ

5. Click OK.
Step 4 Repeat Step 3 to configure the bridge-mounted ports on the other NEs for the E-LAN service.
Step 5 Set attributes for the bridge-mounted ports.
1. Click .
2. Click the Interface Information tab.
3. Set basic attributes for the bridge-mounted ports.
l Enable Port
If the port is in use, set Enable Port to Enabled.
If the port is not in use, set Enable Port to Disabled.
l Working Mode
If a bridge-mounted port is connected to an Ethernet port outside the E-LAN service
network, set this parameter to the same value for the two ports. Generally, the
Ethernet port outside the E-LAN service network works in Auto-Negotiation mode.
If a bridge-mounted port is connected to an Ethernet port on the same E-LAN service
network, set this parameter to Auto-Negotiation for the two ports.
l Max Frame Length (bytes): If jumbo frames are transmitted, set this parameter
according to the length of jumbo frames. If no jumbo frame is transmitted, it is
recommended that this parameter should take the default value 1620.
Transmission System
527
Step 6 Set advanced attributes for the bridge-mounted ports.
1. Click .
2. Click the Interface Information tab.
3. Select the bridge-mounted ports.
4. Click .
The NE Explorer window is displayed.
5. Click the Advanced Attributes tab and set the advanced attributes for the ports. For details,
see 8.1.4 Setting the Advanced Attributes of Ethernet Ports.
6. Click Apply.
Step 7 Optional: Configure Ethernet ring protection switching (ERPS).
1. Click .
2. Click the ERPS tab. Then, click Add.
The Add ERPS dialog box is displayed.
3. Set the parameters for the ERPS protection instance.
NOTE
l Only one node on an Ethernet ring can be configured as the RPL owner.
l The selected RPL owner needs to balance the traffic on each link of the Ethernet ring. Therefore,
the RPL owner should not be an aggregation node. Instead, it should be the NE farthest away
from the aggregation node.
l It is recommended that you set the east port of the RPL owner to RPL Port.
4. Click OK.
5. Set the parameters for the ERPS protocol.
NOTE
l Set the parameters according to the network plan. Default values are recommended.
l The control VLAN ID is different from the VLAN IDs carried by Ethernet services. The control VLAN
ID used by each ring node should be the same.
Step 8 Optional: Configure a split horizon group.
NOTE
The ports in the same split horizon group cannot communicate with each other.
1. Click .
2. Click the Split Horizon Group tab. Then, click Add.
The Add Split Horizon Group dialog box is displayed.
Transmission System
528
3. Select the desired ports and click .
4. Click OK.
Step 9 Select Deploy and ETH OAM CC.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) within the same maintenance association (MA), and activates a continuity check (CC).
Step 10 Click OK.
----End
8.18.6 Configuring Global Attributes of VPLS Services
This section describes the procedure for configuring global attributes of virtual private LAN
services (VPLSs), which is required before the configuration of VPLS services. The global
attributes of VPLS services include the number of virtual user-to-network interfaces (V-UNIs)
and the number of virtual local area networks (VLANs).
Prerequisites
Procedure
Step 1 In the NE Explorer of the desired NE, choose Configuration > Packet Configuration > VPLS
Management from the Function Tree.
Step 2 Set TPID(PW S-TAG) and VUNI Number.
Table 8-9 VPLS management parameters
Field Value Range Description
NE Name For example, NE (9-128) Displays the NE name.
TPID(PW S-TAG) 0x600-0xFFFF
Default: 0x88a8
Specifies the TPID of the S-
TAG carried in VPLS service
packets.
When VPLS service packets
are transmitted from an S-
aware V-UNI to a PW, the
TPID of the S-TAG carried in
the packets is changed to the
value of this parameter.
Transmission System
529
VUNI Number 1-1024
Default: 32
Specifies the maximum
number of V-UNIs used by
an NE to carry VPLS
services.
l The maximum number of
V-UNIs used by an NE to
carry VPLS services and
the maximum number of
VLANs for VPLS
services on an NE have a
mapping relationship, as
shown in Table 8-10.
l If the specified VUNI
Number is between two
values in the mapping
table, set VLAN
Number to the smaller
one of the corresponding
values. For example, if
VUNI Number is set to
50, which is between 32
and 64, set VLAN
Number to 2047, which
is the smaller one of 4096
and 2047.
VLAN Number For example, 4096 Specifies the maximum
number of VLANs for VPLS
services on an NE. The
parameter value is
determined by the value of
VUNI Number.

Table 8-10 Mapping between the number of V-UNIs and the number of VLANs
Number of V-UNIs Number of VLANs
32 4096
64 2047
128 1023
256 511
512 255
1024 127
Transmission System
530

Step 3 Click Apply.
----End
8.18.7 Creating E-LAN Services Carried by PWs on a Per-NE Basis
This section describes how to create PW-carried E-LAN services on the NMS on a per-NE basis.
Prerequisites
l The port attributes must be set correctly.
l The MPLS tunnel that carries the PWs must be created.
l If a port needs to be occupied exclusively, disable the DCN function of the port. For details,
see Configuring the DCN Function for a Port.
l If a QoS policy is required for configuring the QoS, you must create the QoS policy first.
Procedure
Ethernet Service Management > E-LAN Service from the Function Tree.
Step 2 Click New. In the New E-LAN Service dialog box, set parameters. For details about the
parameters, see A.7.1 E-LAN Service Parameters.
Service Type Tag Type MAC Address Learning Mode
OptiX OSN
550/500
OptiX OSN 580
IEEE 802.1d bridge-
based E-LAN
services
Tag-Transparent -
IEEE 802.1q bridge-
based E-LAN
services
C-Aware IVL
Transmission System
531
Service Type Tag Type MAC Address Learning Mode
OptiX OSN
550/500
OptiX OSN 580
IEEE 802.1ad
bridge-based E-LAN
services
S-Aware IVL
PW-carried E-LAN
services
C-Aware/S-Aware SVL SVL/IVL

NOTE
l Self-Learning MAC Address can be set to Enabled or Disabled. When Self-Learning MAC
Address is set to Enabled, the bridge supports MAC address self-learning and the forwarding table
items are generated through MAC address self-learning. You can also configure the static MAC address
forwarding table items manually. When Self-Learning MAC Address is set to Disabled, the bridge
does not support MAC address self-learning, and you can configure the static MAC address forwarding
table items only manually.
l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates shared VLAN learning. All
VLANs share a MAC address forwarding table. Each MAC address is unique in the forwarding table.
IVL indicates independent VLAN learning. The forwarding tables for different VLANs are
independent from each other. The MAC address forwarding tables for different VLANs, however, are
permitted to contain the same MAC addresses.
l Tag Type can be set to C-Aware, S-Aware, or Tag Transparent. C-Aware corresponds to the
accessed service packets with one C-VLAN tag. S-Aware corresponds to the accessed service packets
with one C-VLAN tag and one S-VLAN tag. Tag Transparent corresponds to the accessed service
packets without any VLAN tags.
Step 3 Click the UNI tab and click Configuration. In the Configure Port dialog box, set parameters.
For details about the parameters, see A.7.2 UNI.
Step 4 In the Available Ports list, select the port. Then, click to add the port to the Selected
Ports list.
Step 5 In the Selected Ports list, set VLANs for the port, and then click OK.
Step 6 Click the NNI tab. Click the PW tab. Click New and set the parameters related to the PW. Then,
click OK. For details about the parameters, see A.7.3 NNI.
Step 7 Click the Split Horizon Group tab. Click New. In the New Split Horizon Group dialog box,
set parameters. For details about the parameters, see A.7.4 Split Horizon Group.
Step 8 Set the split horizon group ID, and add the port that needs to be added into the split horizon
group to the Selected Interfaces area box. Click OK.
Step 9 Click OK. In the Result dialog box displayed to indicate that the operation is successful, click
Close.
Step 10 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min),
Address Table Specified Capacity, Address Detection Upper Threshold(%), and Address
Detection Lower Threshold(%). For details about the parameters, see A.7.5 MAC Address
Learning Parameters.
Transmission System
532
NOTE
Address Detection Upper Threshold(%) and Address Detection Lower Threshold(%) indicate the
upper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, the
equipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.
is successful. Click Close.
Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames
and multicast frames. The default value is broadcast. For details about the parameters, see A.
7.6 Unknown Frame Processing.
is successful. Click Close.
Step 14 Optional: Click the QoS tab. Set the QoS parameters.
Step 15 Optional: In the QoS tab, click the PW. Set EXP and LSP Mode. Click Apply. Then, the
Operation Result dialog box is displayed, indicating that the operation is successful. Click
Close.
NOTE
If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak
Information Rate(kbit/s). You can also select the QoS policy directly in Policy. Before selecting a policy,
you need to create the policy first.
Step 16 Optional: Click the Static MAC Address tab. You can set VLAN ID, MAC Address, and
Egress Interface. For details about the parameters, see A.7.7 Static MAC Address.
NOTE
The VLAN ID can be set only when MAC Address Learning Mode is set to IVL.
----End
8.18.8 Configuring E-LAN Services Carried by PWs in End-to-End
Mode
This section describes how to create E-LAN services carried by PWs in end-to-end mode.
Prerequisites
l If the E-LAN services carried by PWs need to occupy the UNIs exclusively, disable the
DCN function of the UNIs. For the method of disabling the DCN function of a port, see
Configuring the DCN Function for a Port.
Procedure
Step 1 Choose Service > VPLS Service > Create VPLS Service from the main menu.
Step 2 Set the parameters in the Basic Attribute tab. For details about the parameters, see A.8
Parameter Description: E-LAN Services (in End-to-End Mode).
Transmission System
533
Step 3 Select the VPLS service node.
l Method 1:
1. In "Node List", choose Add > NPE.
2. In the dialog box that is displayed, select the NEs on which you need to create the VPLS
services.
l Method 2:
1. In Physical Topology, right-click the NEs on which you need to create the VPLS
services and choose NPE from the shortcut menu.
Step 4 In "Node List", select an NE and click Detail. Click the VSI Configuration tab and set the VSI
parameters in the tab. For details about the parameters, see A.8 Parameter Description: E-
LAN Services (in End-to-End Mode).
Transmission System
534
NOTE
You need to set VSI attributes for all the NEs in "Node List".
Step 5 Click the PW Configuration tab and configure the PWs for carrying the services in the tab.
NOTE
l If you set Networking Mode to Full-Mesh VPLS, the NMS automatically creates the PWs between
NEs but you need to create the tunnel for carrying the PWs.
l If you set Networking Mode to Customized, select all the NEs in "Node List". Then, click Create,
and select Bidirectional PW or Unterminated PW as required. In the dialog box that is displayed,
set the PW information.
l To create an Unterminated PW, add an NPE node and create an Unterminated PW on the PW
Configuration tab.
Step 6 Configure the service access ports.
1. In "Node List", select an NE and click the SAI Configuration tab.
2. Click Create. In the dialog box that is displayed, select the ports to be added, set the relevant
parameters, and click OK.
3. Click the SAI QoS tab. Select a port. Click Configure and select Global QoS policy
Template or QoS CAR Template. In the dialog box that is displayed, set the QoS
parameters.
NOTE
l Before you set Global QoS policy Template, specify Global QoS Policy.
l When setting the QoS parameters of a service access port, you can directly select the service port
and set the global QoS policy or QoS CAR parameter.
Step 7 Optional: If you want to configure alarm-related data, select the ETH OAM CC check box in
the lower left corner to enable the regular OAM CC function for the equipment.
Step 8 Select Deploy and then click OK.
NOTE
l If you deselect Deploy, the service configuration is saved only on the NMS. If you select Deploy, the
service configuration is saved on the NMS and deployed to the NEs. By default, Deploy is selected.
l If Deploy and Enable are selected, services on the NE side are available only after the services are
activated.
----End
8.19 Managing the MAC Address Table
The MAC address table is the core of the E-LAN service. The OptiX OSN equipment provides
various functions for managing the MAC address table.
Transmission System
535
8.19.1 Creating a Static MAC Address Entry
Through the creation of a static MAC address entry, the host with a specified MAC address is
not affected by MAC address aging. In addition, the E-LAN service can be supported by the
host that receives packets only.
Prerequisites
l The E-LAN service must be created.
U2000
Procedure
Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to be
created.
Step 3 Click the Static MAC Address tab.
Step 4 Click New.
The New Static MAC Address dialog box is displayed.
Step 5 Configure the parameters of the static MAC address entry.
Step 6 Click OK, and then close the dialog box that is displayed.
----End
8.19.2 Creating a Blacklist Entry of MAC Addresses
Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC
address can be prohibited from using the E-LAN service.
Prerequisites
U2000
Transmission System
536
Procedure
Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses needs
to be created.
Step 3 Click the Disabled MAC Address tab.
Step 4 Click New.
The Create Disabled MAC Address dialog box is displayed.
Step 5 Configure the blacklist entry of MAC addresses.
Step 6 Click OK, and then close the dialog box that is displayed.
----End
8.19.3 Configuring the Aging Parameters of a MAC Address Table
By default, the aging function of a MAC address table is enabled and the aging time is five
minutes. By configuring the aging parameters of a MAC address table, you can modify such
parameters.
Prerequisites
U2000
Procedure
Step 2 On the main interface, select the E-LAN service whose aging parameters of the MAC address
table need to be configured.
Step 3 Click the MAC Address Learning Parameters tab.
Step 4 Configure the status of the aging function and set the aging time.
----End
Transmission System
537
8.19.4 Querying or Deleting a Dynamic MAC Address
By querying or deleting a dynamic MAC address, you can query or delete all the MAC address
entries that are learned by the E-LAN service.
Prerequisites
U2000
Procedure
Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to be
queried or cleared.
Step 3 Click the Self-Learning MAC Address tab.
Step 4 Optional: Select the board whose dynamic MAC address needs to be queried and then check
the dynamic MAC addresses in the MAC address table that is displayed.
Step 5 Optional: Click Clear MAC Address to clear the dynamic MAC addresses. Then, click OK
in the dialog box that is displayed for confirmation.
----End
8.20 Setting the Mode for Processing an Unknown Frame of
the E-LAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC
address table or a multicast frame whose destination MAC address is not listed in the multicast
group. By default, the NE broadcasts the unknown frame. By setting the mode for processing
an unknown frame of the E-LAN service, you can change the processing mode so that unknown
frame can be discarded.
Prerequisites
U2000
Transmission System
538
Procedure
Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown frame
needs to be set.
Step 3 Click the Unknown Frame Processing tab.
Step 4 Set the mode for processing an unknown frame of the E-LAN service.
----End
8.21 Configuring Transit Nodes for Ethernet Services
for an Ethernet service.
8.21.1 Configuring Transit NEs for Ethernet Services Carried by
Ports
for an Ethernet service carried by ports.
Prerequisites
l For the Ethernet service carried by ports, Port Mode is set to Later 2 and Encapsulation
Type is set to 802.1Q.
Procedure
Step 1 In the NE Explorer, select the required NE from the root list, and choose Configuration >
Packet Configuration > Ethernet Service Management > E-Line Service from the Function
Tree.
Step 2 Click New. Then, the New E-Line Service dialog box is displayed.
Transmission System
539
Step 3 Set parameters of transit NEs for an Ethernet service. For details about the parameters, see A.
5.1 E-Line Service Parameters.
NOTE
l For transit NEs for an Ethernet service, set Direction to UNI-UNI.
l For transit NEs for an Ethernet service, you do not need to set QoS parameters.
Step 4 Click OK.
Step 5 Click Query to check the configured Ethernet service.
----End
PWs
for an Ethernet service carried by PWs.
For transit NEs of an Ethernet service carried by PWs, you only need to configure MPLS tunnels
whose Node Type is Transit. For details on how to configure an MPLS tunnel, see 8.8
QinQ Links
for an Ethernet service carried by QinQ links.
Prerequisites
l For the Ethernet service carried by QinQ links, Port Mode is set to Later 2 and
Encapsulation Type is set to QinQ.
Transmission System
540
Procedure
Step 1 In the NE Explorer, select the required NE from the root list, and choose Configuration >
Packet Configuration > Ethernet Service Management > E-Line Service from the Function
Tree.
Step 2 Click New. Then, the New E-Line Service dialog box is displayed.
Step 3 Set parameters of transit NEs for an Ethernet service. For details about the parameters, see A.
5.1 E-Line Service Parameters.
NOTE
l For transit NEs for an Ethernet service, set Direction to UNI-UNI.
l For transit NEs for an Ethernet service, you do not need to set QoS parameters.
Step 4 Click OK.
Step 5 Click Query to check the configured Ethernet service.
----End
8.22 Configuring a Composite Service
This section describes how to configure the basic attributes, service components, and connection
points for a composite service.
Prerequisites
Procedure
Step 1 Choose Service > Composite Service > Create Composite Service from the main menu.
Step 2 Set parameters in the General area.
Transmission System
541
NOTE
Set Creation Type to Customize.
Step 3 Optional: Select Parameter Linkage.
NOTE
You can select Parameter Linkage when creating an EPL+PWE3 composite service to simplify the
creation process.
Step 4 In the Service Component area, select the required service type from Select. Select one or more
desired services from the displayed dialog box and click Select. The selected services are
displayed in the Service Component area and service topology.
NOTE
You may click Create to create services that are not listed.
Step 5 In the Connection Point area, configure the connection points. The configured connection points
are displayed in the Connection Point area and service topology.
l Click Auto-Calculate to obtain connection points for the composite service.
l Alternatively, manually create connection points as follows:
Transmission System
542
1. Choose the desired type of connection points from the Create drop-down list.
2. In the displayed dialog box, specify Name for the connection points or choose Auto-
Name.
3. Specify Type for the composite service.
4. Click to select PWs or ports.
5. Click OK to exit the dialog box.
Step 6 After completing the setting, click OK.
----End
8.23 Managing Composite Services
Managing composite services includes automatically discovering and deploying composite
services.
8.23.1 Automatically Discovering Composite Services
With the automatically discovering composite service function, you can discover composite
services and save them to the NMS. The composite service is composed of services associated
with interface connection points or PW connection points.
Prerequisites
Procedure
Step 1 Choose Service > Composite Service > Search for Composite Service from the Main Menu.
Step 2 In the dialog box that is displayed, set the tunnel discovery policy and click Start.
Step 3 After the composite service search is complete, click Close.
----End
Transmission System
543
8.23.2 Deploying Composite Services
After being created on the NMS, Composite services are stored on the NMS but not immediately
deployed to the corresponding NEs. This section describes how to deploy Composite services
from the NMS to the corresponding NEs.
Prerequisites
l The composite service has been created.
Procedure
Step 1 Choose Service > Composite Service > Manage Composite Service from the main menu.
Step 2 In the dialog box that is displayed, set Deployment Statusto Undeployed. Click Filter to check
all undeployed Composite services.
Step 3 Select one or more Composite services to be deployed, right-click the Composite services, and
choose Deploy from the shortcut menu.
NOTE
After a Composite service is successfully deployed, its Deployment Status is Deployed.
----End
8.24 Operation Tasks for Configuring CES Services
This topic describes the operation tasks for configuring CES services in per-NE mode and end-
to-end mode on the NMS.
8.24.1 Creating a CES Service in End-to-End Mode
This topic describes how to create CES service channels for transmitting TDM signals in end-
to-end mode. You can configure the source node, sink node, and PW attributes of a CES service
on a GUI of the NMS, therefore quickly completing the CES service configuration.
Prerequisites
l The CES service port must be configured. The port mode must set to Layer 1. The frame
format and frame mode must be set.
Transmission System
544
Context
You need to set the frame format for the UNI port that carries the CES service to be the same
as the service encapsulation format. If the encapsulation format of the CES service is CESoPSN,
you can set the frame format of the UNI port to CRC-4 multiframe (recommended value) or
Double frame. If the encapsulation format of the CES service is SAToP, set frame format of the
UNI port to unframed.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
Step 2 Set the parameters on the General Attributes tab page.
NOTE
l You can configure the CES service according to the service template. That is, you can select a service
template or create a service template in the Service Template field.
l Set Service Type to CES.
l Set Protection Type to Protection-Free.
Step 3 Select the source and sink NEs of the service.
NOTE
The configuration method is the same for the sink NE, source NE, and transit NE. Therefore, only the example
for configuring a source NE is provided as follows.
displayed.
2. Select a source NE from Physical Topology on the left. Then, the selected NE is displayed
in the upper right pane.
3. All slots and available boards on the NE are displayed. Select the appropriate board
according to the service type.
4. In SAI Configuration, set Low TimeSlot.
5. In SAI Configuration, set the SAI attribute of the CES access port. Click Add Node. Then,
the added source and sink NEs are displayed at the bottom of the pane. Then, click OK.
Step 4 Optional: Click Configure Source And Sink and then select Unterminated on the left. Set
the LSR ID of the unterminated node and click Add Node. Then, the added unterminated source
and sink nodes are displayed at the bottom. Then, click OK.
Transmission System
545
NOTE
Unterminated: On a network, if the equipment at one end of a service can be managed by the U2000, and the
equipment at the other end of the service is from another vendor and cannot be managed by the U2000, select
Unterminated to set the LSR ID of the opposite end of the service.
Step 5 Optional: Click Configure PW Switch Node to add working and protection switching NEs
between the source NE and the sink NE.
Step 6 Set parameters of the source and sink NEs that are displayed in Node List. To view the topology
of a configured service, click the Service Topology tab in the upper-right area.
Step 7 Click the PW tab at lower left to set basic attributes of the PW.
NOTE
l The PW ID can be automatically allocated.
l Signaling Type can be set to Static automatically or manually.
l Forward Label and Reverse Label can be allocated automatically and manually.
l Forward Type and Reverse Type support Static Binding. Forward Tunnel needs to be specified
manually.
l You can also set Forward Tunnel and Reverse Tunnel in Service Topology at upper right. Select the
tunnel service between the source NE and the sink NE, select Select Forward Tunnel or Select Reverse
Tunnel, and select the tunnel for static binding.
Step 8 Optional: Click Detail. Then, associated information is displayed in the pane at lower right.
Step 9 Optional: Click the Advanced PW Attribute tab and set the parameters associated with the
PW.
NOTE
l The packet loading time needs to be set to the same value for the NEs at both ends.
l The jitter compensation buffering time needs to be more than two times of the packet loading time.
Step 10 Select Deploy and then click OK.
NOTE
l In this case, If you select Enable, the service configuration is saved on the NMS and deployed to the NEs.
If you deselect Deploy, the service configured is saved only on the NMS but not deployed to NEs. By default,
Deploy is selected.
l When Deploy and Enable are selected, the NE-side tunnel is available only after the tunnel is enabled.
----End
Subsequent Operation
After the service is created successfully, the service is displayed in the PWE3 service
management window.
Transmission System
546
8.24.2 Creating UNI-UNI CES Services on a Per-NE Basis
When creating a CES service on a per-NE basis, you need to set associated service attributes for
the source node and the sink node separately.
Prerequisites
l The CES ports must be configured correctly.
Procedure
CES Service Configuration from the Function Tree.
Step 2 Click New. Set the CES service parameters in the Create CES Service dialog box that is
displayed.
----End
8.24.3 Creating UNI-NNI CES Services on a Per-NE Basis
If you create a CES service on a per-NE basis, you need to create relevant attributes of the service
separately on the source and sink nodes of the service. After the CES service is created, the
corresponding PW is automatically created.
Prerequisites
l The CES port must be configured. The port mode must set to Layer 1. The frame format
must be set if the CES port is a PDH port.
Procedure
CES Service Configuration from the Function Tree.
Step 2 Click New. Set the CES service parameters in the Create CES Service dialog box that is
displayed.
Step 3 Click Configure PW. Set the PW parameters in the Create PW dialog box that is displayed.
Step 4 Click the Basic Attributes tab and set the PW parameters of the CES service.
NOTE
l Set PW Signaling Type to Static.
l Set the other parameters according to the network planning information.
Step 5 Click the Advanced Attributes tab and set the advanced attributes of the CES service.
Transmission System
547
NOTE
l The packet loading time needs to be set to the same value for the NEs at both ends.
l The jitter compensation buffering time needs to be more than two times of the packet loading time.
Step 6 After setting the parameters, click OK.
Step 7 Click OK in the Create CES Service dialog box that is displayed.
Step 8 Navigate to the NE Explorer of the opposite NE and configure the reverse service according to
Step 1 to Step 9.
----End
8.25 Configuring Transit NEs for CES Services
for a CES service.
For transit NEs of a CES service, you only need to configure MPLS tunnels whose Node
Type is Transit. For details on how to configure an MPLS tunnel, see 8.8 Configuring an
MPLS Tunnel.
8.26 Managing VPLS Services
increase customer revenues. Therefore, it is crucial to properly manage VPLS services.
Managing VPLS services involves deploying, modifying, and deleting VPLS services, checking
the VPLS service topology.
8.26.1 Checking the VPLS Service Topology
increase customer revenues. This section describes how to check the topology information and
running status of a VPLS service, facilitating VPLS service management.
Prerequisites
l A VPLS service has been created.
Procedure
Step 2 In the dialog box that is displayed, set filter conditions. Then, click Filter. Query all VPLS
services that meet the filter conditions.
Step 3 Select the VPLS service whose topology information you need to check and click the
Topology tab.
Transmission System
548
Step 4 In the service topology view, right-click an NE, a port or a PW. Then you can query current
alarms, historical alarms or real-time performance data by choosing the related item from the
shortcut menu.
----End
8.26.2 Deploying VPLS Services
After being created on the NMS, VPLS services are stored on the NMS but not immediately
deployed to the corresponding NEs. This section describes how to deploy VPLS services from
Prerequisites
Procedure
all undeployed VPLS services.
Step 3 Select one or more VPLS services to be deployed, right-click the VPLS services, and choose
NOTE
After a VPLS service is successfully deployed, its Deployment Status is Deployed.
----End
8.26.3 Modifying VPLS Services
This section describes how to change values of VPLS service parameters, such as the service
name.
Transmission System
549
Prerequisites
Context
NOTICE
Modifying a VPLS service may interrupt other services.
Procedure
Step 3 Select the desired VPLS service and click the tab in the lower left corner of the interface. Then,
modify the parameters.
Step 4 Optional: If only the basic attributes of the VPLS service need to be modified, select the VPLS
service whose parameters you need to modify and click Details. In the dialog box that is
displayed, change the values of the VPLS services parameters as required.
----End
Transmission System
550
8.26.4 Deleting VPLS Services
After being deployed, VPLS services are stored on the NMS and the corresponding NEs. This
section describes how to delete VPLS services from the NMS and corresponding NEs.
Prerequisites
Procedure
Step 3 Select one or more VPLS services that you need to delete, right-click the services, and choose
----End
8.26.5 Deleting VPLS Services from the Network Side
After being deployed, VPLS services are stored on the NMS and the corresponding NEs. After
being deleted from the network side, VPLS services are deleted from the NMS only but still
stored on the corresponding NEs. In addition, after being deleted from the network side, VPLS
services are displayed as discrete services on the NMS.
Prerequisites
Procedure
Step 3 Select one or more VPLS services that you need to delete, right-click the services, and choose
----End
Transmission System
551
8.27 Managing PWE3 Services
increase customer revenues. Therefore, it is crucial to properly manage PWE3 services.
Managing PWE3 services involves deploying, modifying, and deleting PWE3 services,
checking the PWE3 service topology, and managing discrete PWE3 services.
8.27.1 Checking the PWE3 Service Topology
increase customer revenues. This section describes how to check the topology information and
running status of a PWE3 service, facilitating PWE3 service management.
Prerequisites
l The PWE3 service has been created.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to PW
APS Protection. Then, click Filter. Query all PWE3 services that meet the filter conditions.
Step 3 Select the PWE3 service whose topology information you need to check and click the
Topology tab.
Step 4 In the PWE3 service topology view, right-click an NE, and choose View Real-Time
Performance from the shortcut menu to check the real-time running status of the PWE3 service.
----End
8.27.2 Deploying PWE3 Services
After being created on the NMS, PWE3 services are stored on the NMS but not immediately
deployed to the corresponding NEs. This section describes how to deploy PWE3 services from
Prerequisites
Procedure
all undeployed PWE3 services.
Transmission System
552
Step 3 Select one or more PWE3 services to be deployed, right-click the PWE3 services, and choose
NOTE
After a PWE3 service is successfully deployed, its Deployment Status is Deployed.
----End
8.27.3 Modifying PWE3 Services
This section describes how to change values of PWE3 service parameters, such as the service
name.
Prerequisites
Context
NOTICE
Modifying a PWE3 service may interrupt other services.
Procedure
Step 3 Select the desired PWE3 service and click the tab in the lower left corner of the interface. Then,
modify the parameters.
Step 4 Optional: If only the basic attributes of the PWE3 service need to be modified, select the PWE3
service whose parameters you need to modify and click Details. In the dialog box that is
displayed, change the values of the PWE3 services parameters as required.
Transmission System
553
----End
8.27.4 Deleting PWE3 Services
After being deployed, PWE3 services are stored on the NMS and the corresponding NEs. This
section describes how to delete PWE3 services from the NMS and corresponding NEs.
Prerequisites
Procedure
Step 3 Select one or more PWE3 services that you need to delete, right-click the services, and choose
----End
Transmission System
554
8.27.5 Deleting PWE3 Services from the Network Side
After being deployed, PWE3 services are stored on the NMS and the corresponding NEs. After
being deleted from the network side, PWE3 services are deleted from the NMS only but still
stored on the corresponding NEs. In addition, after being deleted from the network side, PWE3
services are displayed as discrete services on the NMS.
Prerequisites
Procedure
----End
8.27.6 Deleting PWE3 Services from the NE Side
After being deployed, PWE3 services are stored on the NMS and the corresponding NEs. After
being deleted from the NE side, PWE3 services are deleted from the corresponding NEs only
but still stored on the NMS. In addition, after being deleted from the NE side, PWE3 services
are displayed as undeployed.
Prerequisites
Procedure
Deploy and Enable > Undeploy from the shortcut menu.
Transmission System
555
NOTE
After a PWE3 service is successfully deleted from the NE side, its Deployment Status is Undeployed.
----End
8.27.7 Managing Discrete PWE3 Services
This section describes how to find discrete PWE3 services, convert discrete PWE3 services to
unterminated services, and delete discrete PWE3 services.
Prerequisites
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Discrete Service from the main menu.
Step 2 In the dialog box that is displayed, set filter conditions and click Filter. Query all PWE3 services
that meet the filter conditions.
Step 3 Optional: Convert a PWE3 service to an unterminated service.
1. Select a PWE3 service and click Convert to Unterminated.
2. In the dialog box that is displayed, set attributes of the PWE3 service, such as the service
name.
NOTE
After a PWE3 service is converted to an unterminated service, its service information is displayed
in Manage PWE3 Service.
Step 4 Optional: Select one or more PWE3 services and click Delete Discrete Service.
----End
8.28 Managing the QoS
By managing the QoS, you can provide the services of different levels for different service types.
Transmission System
556
8.28.1 Modifying the Mapping Relationships for the DS Domain
This topic describes how to modify the mapping relationships between packet priorities and
PHB service classes in the ingress or egress direction of a DS domain.
Prerequisites
U2000
The OptiX OSN equipment has a default DS domain, whose Mapping Relation ID is 1 and
Mapping Relation Name is default map.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
Step 2 Select the created DS domain and change its attributes on the main interface.
NOTE
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Step 3 Optional: Change the mapping relationship in the ingress direction.
1. Click the Inbound Mapping Relation tab.
Transmission System
557
2. Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the ingress direction.
3. Click Apply. Then, close the dialog box that is displayed.
Step 4 Optional: Change the mapping relationship in the egress direction.
1. Click the Outbound Mapping Relation tab.
2. Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the egress direction.
3. Click Apply. Then, close the dialog box that is displayed.
----End
8.28.2 Changing the Ports in a DS Domain and Their Trusted Packet
Types
This topic describes how to add or delete a port in the DS domain and set the packet type over
the port.
Prerequisites
U2000
The OptiX OSN equipment has a default DS domain, whose Mapping Relation ID is 1 and
Mapping Relation Name is default map.
Procedure
Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain
Management from the Function Tree.
Step 2 Select the DS domain for which you need to add or delete an application port on the main
interface.
Step 3 Click the Application Object tab.
Step 4 Click Modify.
Step 5 Add or delete a port that uses the DS domain.
Transmission System
558
If... Then...
You need to add a port that uses the DS
domain
1. Select the board where the application
port is located from the drop-down list of
Board.
2. Select the port to be added from the drop-
down list of Available Port.
3. Click .
You need to delete a port that uses the DS
domain
1. Select the board where the application
port is located from the drop-down list of
Board.
2. Select the port to be deleted from the
port list of Selected Port.
3. Click .
You need to change the packet type
identified by the port
Select a new packet type from the drop-down
list of Packet Type.

NOTE
----End
8.28.3 Setting the Port That Uses the Port Policy
This section describes how to set the port that uses the port policy.
Transmission System
559
Prerequisites
Tools, Instruments, and Materials
U2000
Procedure
Configuration > QoS Management > Policy Management > Port Policy from the Function
Tree.
Step 2 Click the Application Object tab.
Step 3 Click Modify.
Then, the Configure Port dialog box is displayed.
Step 4 Set the port that uses the port policy.
1. Select Board where the port that needs to use the port policy from Application Port.
2. Select a port from Available Ports, and then click .
NOTE
Hold on the Ctrl key on the keyboard to select multiple ports.
3. Click OK. Then, close the dialog box that is displayed.
Step 5 Delete the port that uses the port policy.
1. Select the port to be deleted from Selected Ports and click .
NOTE
2. Click OK. Then, close the dialog box that is displayed.
----End
Transmission System
560
A Parameter Description
This topic describes the parameters related to the Ethernet services.
A.1 Parameter Description: Attributes of Ethernet Ports
This topic describes the attributes of Ethernet ports.
A.2 Parameter Description: CES Port
Before configuring a CES service, you must configure the CES port.
A.3 Parameter Description: MPLS
This topic describes the parameters related to MPLS.
A.4 Parameter Description: Address Parse
Configuring the address parse function is to set the parameters such as ARP List IP, ARP List
MAC, and ARP List Type.
A.5 Parameter Description: Ethernet Private Line Services (on a Per-NE Basis)
This topic describes the parameters related to Ethernet private line services.
A.6 Parameter Description: E-Line Services (End-to-End Mode)
Before creating E-Line services carried by PWs, you need to configure the tunnel for carrying
the PWs. This section describes the parameters for configuring E-Line services in end-to-end
mode.
A.7 Parameter Description: E-LAN Service (on a Per-NE Basis)
This topic describes the parameters related to the E-LAN Service configuration.
A.8 Parameter Description: E-LAN Services (in End-to-End Mode)
Before creating E-LAN services carried by pseudo wires (PWs), you need to configure the tunnel
that carries PWs and configure the virtual switch instance (VSI) attribute of NEs as NPE. This
section describes the parameters for configuring E-LAN services in end-to-end mode.
A.9 Parameter Description: CES Services
This topic describes the parameters related to CES services.
A.10 Parameters for Configuring CES Services (in End-to-End Mode)
This section describes the parameters for configuring CES services in end-to-end mode.
A.11 Parameter Description: ATM Services
This topic describes the parameters related to ATM services.
A.12 Parameters for Configuring IMA Services (on a Per-NE Basis)
Transmission System
Configuration Guide (Packet Transport Domain) A Parameter Description
561
This section describes the parameters for configuring IMA services on a per-NE basis.
A.13 Parameter Description: Parameters for Configuring ATM/IMA Services (in End-to-End
Mode)
This section describes the parameters that are used for configuring ATM/IMA services in end-
to-end mode.
A.14 Parameter Description: ATM OAM Management
This section describes the parameters for configuring ATM OAM on a per-NE basis.
A.15 Parameter Description: Inband DCN
This topic describes the parameters related to inband DCN.
Transmission System
562
A.1 Parameter Description: Attributes of Ethernet Ports
This topic describes the attributes of Ethernet ports.
A.1.1 Basic Attributes
Before configuring Ethernet services in packet mode, you need to set the basic attributes of
Ethernet ports.
Table A-1 Parameters for the basic attributes of an Ethernet port
Port Example: 1-EM6F-1
(PORT-1)
Displays the port name.
Name Example: Port 1 Enters the port name specified
by the user.
Enable Port Enabled, Disabled
Default value: Enabled
The Enable Port parameter
sets whether the Ethernet port
is usable.
Impact on the System:
When services are available on
the Ethernet port, setting this
port to disabled interrupts the
services.
Value description:
l Enabled: The port is
usable.
l Disabled: The port is
unusable.
Recommendations:
When a port is used for
transmitting services, enable
this port first.
Transmission System
563
Port Mode Layer 2, Layer 3
Default value: Layer 2
Selects the working mode of
the Ethernet port.
l If this field is set to Layer
2, the port can be used to
receive Ethernet services
from the user equipment or
to transmit Ethernet
services that exclusively
occupy the port.
l If this field is set to Layer
3, the port can carry
tunnels.
Transmission System
564
Encapsulation Type Null, 802.1Q, QinQ
Default value: 802.1Q
The Encapsulation Type
parameter sets the link layer
encapsulation type of the port,
and specifies the link layer
encapsulation type that can be
identified by this port.
Value description:
l Null: No link layer is
available, or the link layer
encapsulation is not
processed.
l 802.1Q: In the Layer 2
mode, the encapsulation
type of the Ethernet port is
802.1Q by default.
l QinQ: When the Ethernet
port is used for QinQ Link,
the port attribute should be
set to Layer 2, and the
encapsulation type should
be set to QinQ. In addition,
QinQ Type Domain of the
two interconnected
Ethernet ports should be set
to the same value.
Recommendations:
Currently, the encapsulation
type of the Ethernet port can be
set. In addition, the
encapsulation type can be
switched only when the port
does not carry services.
In the Layer 2 mode, the
encapsulation type of the
Ethernet port can be Null,
802.1Q, and QinQ. In the
Layer 3 mode, the
Ethernet port, which is fixed to
802.1Q, cannot be set.
Transmission System
565
Working Mode 10M Half-Duplex, 10M Full-
Duplex, Auto-Negotiation,
100M Half-Duplex, 100M
Full-Duplex, 1000M Full-
Duplex, 10G Full-Duplex
LAN, 10G Full-Duplex WAN
Default value: Auto-
Negotiation
NOTE
l For the OptiX OSN 500
equipment, this field cannot
be set to 10G Full-Duplex
LAN or 10G Full-Duplex
WAN.
Set the Working Mode
parameter to set the working
mode of the Ethernet port on
the board. The Working
Mode parameter indicates the
maximum transmission rate
and communication mode of a
port.
If the working modes of
interconnected Ethernet ports
are inconsistent, the services
are not available or have a
severe packet loss problem.
Value description:
l 10M Half-Duplex: The
maximum transmission
rate of the port is 10 Mbit/
s and the communication
mode is half-duplex.
l 10M Full-Duplex: The
mode is full-duplex.
l Auto-Negotiation: The
port uses the protocol to
automatically specify the
best working mode that
matches the opposite port
for communication.
l 100M Half-Duplex: The
mode is half-duplex.
mode is full-duplex.
rate of the port is 1000
Mbit/s and the
communication mode is
full-duplex.
Transmission System
566
l 10G Full-Duplex LAN:
The maximum
transmission rate of the
port is 10 Gbit/s and the
full-duplex. This value is
applicable to the Ethernet
port.
l 10G Full-Duplex WAN:
The maximum
transmission rate of the
port is 10 Gbit/s and the
full-duplex. This value is
applicable to the SDH port.
Recommendations:
The Auto-Negotiation
working mode is
recommended. If the
communication fails and the
working mode of the port is set
to Auto-Negotiation, you
need specify the working
mode of the port according to
the working mode of the
interconnected port.
If the working mode of the port
is set to any other mode instead
of Auto-Negotiation, the
working mode of the
interconnected port should be
the same. Otherwise, the
communication is not
available.
In the case of equipment
interconnection, set the
communication modes of the
interconnected ports to full-
duplex.
Transmission System
567
Max Frame Length(bytes) 64-9600
Default value: 1522
NOTE
The value ranges of the
parameters are different from
each other for different boards
and products, please refer to the
hardware description.
The Max Frame Length
(byte) parameter sets the
maximum length of the data
packets allowed to be received
by the Ethernet port.
After this parameter is set, all
the data packets of a length
longer than this parameter are
discarded.
Recommendations:
The maximum data packet
length has a filtering
mechanism, through which
this parameter is set to filter the
data packets received on the
Ethernet port of a length
longer than a certain length.
When setting this parameter,
consider the length of the data
packets transmitted from the
opposite end. If the parameter
value is less than the length of
the data packets transmitted
from the opposite end, this link
cannot normally transmit
service packets.
Auto-Negotiation Ability 10M Half-Duplex, 10M Full-
Duplex, 100M Half-Duplex,
100M Full-Duplex, 1000M
Half-Duplex, 1000M Full-
Duplex
Default value: 100M Full-
Duplex
Displays the auto-negotiation
capability of the Ethernet port.
l Auto-Negotiation Ability
is valid only when
Working Mode is set to
Auto-Negotiation.
l The PEG1, EG4C, EM6X,
EM6F, EM6T boards
support this parameter.
Logical Port Attribute No interface, Optical Port,
Electrical Port
Specifies displays the optical
attribute of the logical
Ethernet port.
Physical Port Attribute No interface, Single-mode
optical port, Multi-mode
optical port, Electrical port
Displays the optical attribute
of the physical Ethernet port
Transmission System
568
ARP Aging Time(min) -
NOTE
For the OptiX OSN 550/500
equipment, this field is
inapplicable.
Displays the ARP aging time
of Ethernet ports.
Running status - Displays the running status of
ports.
Optical Module Status In-Position, Not-in-Position
NOTE
inapplicable.
Displays the status of the
optical module.
Laser Interface Status On, Off
NOTE
inapplicable.
Specifies whether the status of
the laser interface.
Laser Transmission
Distance(m)
-
NOTE
inapplicable.
Displays the transmission
distance of a laser.
Traffic Policing Status Disabled, Enabled
Default value: Disabled
Specifies whether traffic
policing is enabled for a port.
To check whether traffic over
a port is normal, set Traffic
Policing Status to Enabled to
monitor traffic in the specified
Traffic Policing Period
(min).
Traffic Policing Period
(min)
1-30
Default value: 15
Specifies the period of traffic
policing.

A.1.2 Layer 2 Attributes
This topic describes the parameters related to Layer 2 attributes of Ethernet ports.
Table A-2 Parameters for Layer 2 attributes of Ethernet ports
Port Example:3-EM6F-1(PORT-1) Displays the port name.
Transmission System
569
QinQ Type Domain 0x0600-0xFFFF
Default value: 88A8
Specifies the QinQ type
domain.
This field is available only
when Encapsulation Type in
General Attributes is set to
QinQ.
Tag Tag Aware, Access, Hybrid
Default value: Tag Aware
Identifies the type of packets.
l Tag Aware: If the port is
set to Tag aware, the port
transparently transmits the
packets with a VLAN ID
(namely, tagged packets)
and discards the packets
without a VLAN ID
(namely, untagged
packets). At this time,
Default VLAN ID and
VLAN Priority are
unavailable.
l Access: If the port is set to
Access, the port attaches
the default VLAN ID to the
packets without a VLAN
ID (namely, untagged
packets) and discards the
packets with a VLAN ID
(namely, tagged packets).
l Hybrid: If the port is set to
Hybrid, the port attaches
the default VLAN ID to the
packets without a VLAN
ID (namely, untagged
packets) and transparently
transmits the packets with a
VLAN ID (namely, tagged
packets).
This field is unavailable if
Encapsulation Type in
General Attributes is set to
QinQ.
Transmission System
570
Default VLAN ID 1-4094
Default value: 1
Specifies the default VLAN ID
of the packets that can be
transmitted by the port.
l If TAG is set to Access, the
port discards the packets
that contain the VLAN ID,
but attaches the default
VLAN ID to the packets
that do not contain a VLAN
ID and then transmits these
packets.
l If TAG is set to Hybrid,
the port transmits the
packets that contain a TAG,
and attaches the default
VLAN ID to the packets
that do not contain a TAG
and then transmits these
packets.
VLAN Priority 0-7
Default value: 0
Specifies the quality of service.
For example, on a busy
network, the higher-priority
packets are processed first
whereas the lower-priority
packets may be discarded. The
value 0 indicates the lowest
priority, and the value 7
indicates the highest priority.
The default value is
recommended unless
otherwise specified.

Table A-3 Methods used by Ethernet interfaces to process data frames
Port Type of Data
Frame
Processing Method
Tag Aware Access Hybrid
Ingress UNI Tagged frame The port receives the
frame.
The port discards
the frame.
The port receives
the frame.
Transmission System
571
Port Type of Data
Frame
Processing Method
Tag Aware Access Hybrid
Untagged frame The port discards the
frame.
The ports add the
VLAN tag, to which
Default VLAN ID
and VLAN
Priority
correspond, to the
frame and receive
the frame.
The ports add the
VLAN tag, to which
Default VLAN ID
and VLAN
Priority
correspond, to the
frame and receive
the frame.
Egress UNI Tagged frame The port transmits
the frame.
The port strips the
VLAN tag from the
frame and then
transmits the frame.
l If the VLAN ID
in the frame is
Default VLAN
ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.

A.1.3 Layer 3 Attributes
This topic describes the parameters for the Layer 3 attributes of an Ethernet port.
Table A-4 Parameters for the Layer 3 attributes of an Ethernet port
Parameter Value Range Description
Port For example, 3-EM6F-1
(PORT-1)
Transmission System
572
Enable Tunnel Enabled, Disabled
The Enable Tunnel(Ethernet
Interface) parameter sets the
MPLS enabling state of the
port. When Enable Tunnel is
set to Enabled, it indicates that
the port can identify and
process the MPLS label.
If the MPLS is disabled, the
services on the port are
interrupted.
Value description:
l Enabled: The MPLS is
enabled.
l Disabled: The MPLS is
disabled.
Recommendations:
When the services are
configured, the MPLS should
not be disabled.
Max Reserved Bandwidth
(kbit/s)
For example, 102400 Sets the maximum bandwidth
used by the tunnel.
The maximum reserved
bandwidth should not exceed
the physical bandwidth of the
bearer port.
Available Bandwidth
(kbit/s)
- Displays the available
bandwidth of the port. The
Available Bandwidth value is
obtained from equipment and
refreshed automatically when
the Max Reserved
Bandwidth value of the port is
modified or the tunnel
traversing the port is adjusted.
Transmission System
573
Specify IP Address Manually, Unspecified
Default value: Unspecified
The Specify IP Address
parameter, set by port,
indicates the method of
specifying the IP address
parameter of a specified port.
The IP address parameter of
the port is the prerequisite for
MPLS service creation. If the
current IP address parameter is
invalid, the services cannot be
created.
Value description:
l Manually: Indicates the IP
parameter of the specified
port. If the IP address
parameter is valid, specify
an IP address to the current
port. If the IP address is
invalid, release the IP
address of the current port.
l Unspecified: Indicates that
the IP address of the port is
not specified.
Association with other
parameters:
The IP address parameter can
be configured only when the
port is in the Layer 3 mode.
IP Address For example, 192.168.0.1 Specifies the IP address of a
port.
This parameter is available
when Specify IP Address is
set to Manually.
IP addresses of Ethernet ports
on an NE cannot be in the same
network segment. IP addresses
of the ports at both ends of a
link, however, must be in the
same network segment.
Transmission System
574
IP Mask For example, 255.255.255.0 Specifies the subnet mask of a
port.
when Specify IP Address is
set to Manually.
An IP mask address
determines the range of
available IP addresses.

A.1.4 Advanced Attributes
This topic describes the parameters for the advanced attributes of an Ethernet port.
Table A-5 Parameters for the advanced attributes of an Ethernet port
Port For example, 1-EM6F-1
(PORT-1)
Port Physical Parameters For example: Port Enable:
Enabled, Working Mode:
Auto-Negotiation, Non-
Autonegotiation Flow Control
Mode: Disabled, MAC
Loopback: Non-Loopback,
PHY Loopback: Non-
Loopback
Displays physical parameters
of the port.
MAC Loopback Non-Loopback, Inloop,
Outloop
Default value: Non-Loopback
NOTE
The OptiX OSN equipment
supports only Non-Loopback
and Inloop.
This parameter specifies the
loopback state at the MAC
layer. When this parameter is
set to Inloop, the Ethernet
signals transmitted to the
opposite end are looped back.
In normal cases, it is
recommended that you use the
default value.
Transmission System
575
PHY Loopback Non-Loopback, Inloop,
Outloop
NOTE
supports only Non-Loopback
and Inloop.
The PHY Loopback
parameter indicates the
loopback status of the physical
layer of an Ethernet port. This
parameter is an advanced
attribute of the Ethernet port.
As a fault diagnosis function,
setting PHY loopback affects
the services configured on the
port. In the case of loopback,
services on the port are
interrupted.
Value description:
l Non-Loopback: Indicates
the normal status. When the
equipment is operating
normally, loopback is not
required.
l Inloop: At the local
equipment, the outgoing
services of an Ethernet port
are looped back at the
physical layer and input to
this Ethernet port.
l Outloop: At the local
equipment, the incoming
services of an Ethernet port
are looped back at the
physical layer and output to
this Ethernet port.
Recommendations:
The PHY loopback is mainly
used to locate a fault. When
setting this parameter,
determine the loopback type
according to the service flow
direction.
MAC Address For example,
00-5A-3D-03-4C-1B
Displays the MAC address of
an Ethernet port.
Transmitting Rate(kbit/s) Example: 1024 Displays the rate for
transmitting data packets.
Receiving Rate(kbit/s) Example: 1024 Displays the rate for receiving
data packets.
Transmission System
576
Loopback Check Enabled, Disabled Specifies whether loop
detection is enabled.
When loop detection is
enabled, the equipment
automatically detects whether
a loop exists on the link. If a
loop exists, the equipment
reports a loop alarm.
Loopback Port Block Enabled, Disabled Specifies whether the
automatic port shutdown
function is enabled.
When Loopback Check is set
to Enabled and Loopback
Port Block is set to Enabled,
the equipment automatically
detects whether a loop exists
on the link. If a loop exists, the
equipment automatically shuts
down the port to eliminate the
loop.
Egress PIR Bandwidth
(kbit/s)
1000-100000
NOTE
The OptiX OSN equipment does
not support this function.
Specifies the egress PIR
bandwidth.
Enabling Broadcast
Packet Suppression
Disabled, Enabled
Specifies whether the
broadcast packet suppression
function at the port is enabled
to limit the traffic rate of the
incoming broadcast packets. If
the broadcast packet
suppression function is
enabled, and if the traffic rate
of the incoming broadcast
packets exceeds the specified
value, the last received
broadcast packets are
discarded.
NOTE
Enabling Broadcast Packet
Suppression is valid for UNI
ports only.
Transmission System
577
Broadcast Packet
(Mbit/s)
0-10000
Default value: 30
Allocates the specified
bandwidth to the broadcast
packets according to the
proportion of the broadcast
packets in the total packets at
the port. If the actual
bandwidth of the broadcast
packets exceeds the specified
threshold, the port discards the
last received broadcast
packets.
Network Cable Mode Network Cable Mode Auto-
Sensing, MDIX, MDI
Specifies the mode of network
cables.
Optical Module Type Unknown, Two-Fiber
Bidirectional
Specifies whether an optical
module is inserted into a port
and the optical module type if
yes.
Value description:
l Unknown: No optical
module is inserted into the
port.
l Two-Fiber Bidirectional: A
two-fiber bidirectional
optical module is inserted
into the port.
Synchronous Clock
Enabled
Enabled, Disabled
NOTE
inapplicable.
Set this parameter to Enabled
if clock synchronization is
required.

A.1.5 Flow Control
This topic describes the parameters related to flow control at Ethernet ports.
Table A-6 Parameters for flow control at Ethernet ports
Port Example: 1-EM6F-1
(PORT-1)
Transmission System
578
Non-Autonegotiation
Flow Control Mode
Disabled, Enable Symmetric
Flow Control, Send Only,
Receive Only
NOTE
l For the OptiX OSN 550/500
be set to Send Only and
Receive Only.
If the port does not work in
auto-negotiation mode, this
field is set to Non-
Autonegotiation Flow
Control Mode.
l Enable Symmetric Flow
Control: The port can
transmit and receive the
PAUSE frame.
l Send Only The port only
transmits the PAUSE
frame. Receive Only: The
port only receives the
PAUSE frame.
The setting of this field must
match that of Non-
Autonegotiation Flow
Control Mode for the
equipment at the opposite end.
Auto-Negotiation Flow
Control Mode
Disabled, Enable
Dissymmetric Flow Control,
Enable Symmetric Flow
Control, Enable Symmetric/
Dissymmetric Flow Control
NOTE
l For the OptiX OSN 550/500
be set to Enable
Dissymmetric Flow
Control and Enable
Symmetric/Dissymmetric
Flow Control.
If the port works in auto-
negotiation mode, this field is
set to Auto-Negotiation Flow
Control Mode.
l Enable Dissymmetric
Flow Control: The port
only transmits the PAUSE
frame.
l Enable Symmetric Flow
Control: The port can
transmit and receive only
the PAUSE frame.
l Enable Symmetric/
Dissymmetric Flow
Control: The auto-
negotiation mode
determines the symmetric/
dissymmetric flow control
mode.
The setting of this field must
match that of Auto-
Negotiation Flow Control
Mode for the equipment at the
opposite end.

Transmission System
579
A.2 Parameter Description: CES Port
Before configuring a CES service, you must configure the CES port.
A.2.1 Channelized STM-1 Port
Configuring a channelized STM-1 port includes setting of the parameters such as the
encapsulation type of the port, the maximum data packet size, and the enabling status of the
laser.
Table A-7 Parameters for the attributes of an SDH port
Port For example, 21-CQ1-1
(PORT-1)
Name For example, port1 Specifies the name of the port
specified by the user.
Port Mode Layer 1 Displays the working mode
of the CES port Layer 1
indicates the channelized
STM port is currently
available.
currently supports only
Layer 1 in Port Mode. In
this case, the OptiX OSN
equipment can transmit
channelized STM-1 services.
Encapsulation Type Null Indicates the link layer
port. It specifies the link layer
encapsulation type that can
be identified and processed
by the port.
When Encapsulation Type
is set to Null, no link layer
encapsulation is available or
the link layer encapsulation is
not performed.
currently supports only
Layer 1 in Port Mode. For
this reason, Encapsulation
Type can only be set to Null
and cannot be changed.
Transmission System
580
Channelize Yes Displays whether the port is a
channelized port.
Channelize refers to the use
of the low-speed tributary
signals in the STM-N service.
One fiber is used to transmit
multiple channels of data that
are separated from each
other. Each channel of data
exclusively occupies the
bandwidth, in addition to the
starting point, terminating
point, and monitoring policy.
Max Data Packet Size (byte) - Specifies the maximum size
of the packets that can be
received by the port.
NOTE
This parameter is currently
inapplicable to the OptiX OSN
equipment.
Laser Interface Enabling
Status
On, Off
Default: On
Specifies the enabling status
of the laser on the port.
Laser Transmission Distance
(m)
- Displays the transmission
distance of the laser on the
port.
NOTE
equipment.
Scrambling Capability - Suppresses multiple 0s and
1s in the data when the
Scrambling Capability is
enabled.
NOTE
equipment.
CRC Check Length - Specifies the length of the
CRC field in the mapping
protocol.
NOTE
equipment.
Transmission System
581
Clock Mode - The Clock Mode parameter
specifies the re-timing mode
of a port.
NOTE
inapplicable to an SDH port.
Loopback Mode Non-loopback, Inloop,
Outloop
Default: Non-loopback
Specifies the loopback status
of the port.
The loopback mode is used
for locating a fault. Outloop
is used for testing whether the
port module and external
fiber or cable of a board are
proper. Inloop is used for
testing whether the cross-
connect unit and service path
of the equipment are proper.
CES Encapsulation Clock
Mode
Null, Line Clock Mode,
System Clock Mode
Default: Null
Specifies the encapsulation
mode of the clock signal on a
UNI port on the master side
of the CES service.
l Null: The clock signal is
not encapsulated in the
service packets.
l Line Clock Mode: The
clock frequency signal
extracted on a line port is
used as the time stamp,
which is encapsulated in
the RTP packet header
and transmitted to the
downstream.
l System Clock Mode:
The system frequency
signal is used as the time
stamp, which is
encapsulated in the RTP
packet header and
transmitted to the
downstream.
Transmission System
582
Poke
- Specifies the enabling status
of the CES encapsulation
clock poke.
NOTE
equipment.

Table A-8 Parameters for an associated service
Service Type For example, CES service Displays the type of the
service associated with the
port.
Service ID For example, 20 Displays the ID of the service
associated with the port.
When you select the value of
the service ID, the active
window changes to the
service management dialog
box of the corresponding
service type.
Service Name For example, CES Displays the name of the
port.
Used Resource For example, 64K
Timeslot1-31
Displays the resource used by
the service associated with
the port.

A.2.2 E1 Port
In addition to the general attributes of an E1 port, you need to set the frame format based on the
advanced attributes to ensure that the frame format specified for the E1 port is the same as the
service encapsulation format.
Table A-9 Parameters for the general attributes of a PDH port
Port Slot ID-Board name-Port
(Port No.)
Transmission System
583
Name For example, Port 1 Enters the port name
specified by the user.
Port Mode Layer 1, Layer 2 Specifies the working mode
of the PDH port.
When this parameter is set to
Layer 1, the port can transmit
TDM signals.
When this parameter is set to
Layer 2, the port can transmit
ATM signals.
Encapsulation Type Null Specifies Encapsulation
Type.
When Port Mode is set to
Layer 1, Encapsulation
Type is defaulted to Null and
cannot be changed.
When Port Mode is set to
Layer 2, Encapsulation
Type is defaulted to ATM
and cannot be changed.

Table A-10 Parameters for the advanced attributes of a PDH port
Port Slot ID-Board name-Port
(Port No.)
Frame Format Unframe, Double Frame,
CRC-4 Multiframe
Specifies the frame format.
When the E1 port transmits
CES services in CESoPSN
mode, this parameter can be
set to Double Frame or
CRC-4 Multiframe. It is
recommended that you set
this parameter to CRC-4
Multiframe. When the CES
services are in SAToP mode,
this parameter needs to be set
to Unframe.
Line Encoding Format HDB3 Displays the line encoding
format.
The HDB3 codes are
transmitted on the E1 port.
Transmission System
584
Clock Mode Master Mode, Slave Mode,
Line Clock Mode
Default: Master Mode
The Clock Mode parameter
specifies the re-timing mode
of a port.
l Master Mode: Indicates
that the internal clock is
adopted.
l Slave Mode: Indicates
that the clock from ACR
is adopted.
l Line Clock Mode:
Indicates that the clock
from line boards is
adopted.
Loopback Mode Non-loopback, Inloop,
Outloop
Specifies the loopback status
of the port.
Impedance 120 ohm Displays the impedance of
the port.
Frame Mode - Specifies the value of the
frame mode.
The frame modes of the local
port and opposite port need to
be consistent.
Transmission System
585
Mode
Null, Line Clock Mode,
System Clock Mode
Default: Null
Queries the encapsulation
mode of the clock signal on a
UNI port on the master side
of the CES service.
l Null: The clock signal is
not encapsulated in the
service packets.
l Line Clock Mode: The
clock frequency signal
extracted on a line port is
used as the time stamp,
which is encapsulated in
the RTP packet header
and transmitted to the
downstream.
l System Clock Mode:
The system frequency
signal is used as the time
stamp, which is
encapsulated in the RTP
packet header and
transmitted to the
downstream.

Table A-11 Parameters for an associated service
Service Type For example, CES service Displays the type of the
port.
Service ID For example, 20 Displays the ID of the service
associated with the port.
When you select the value of
the service ID, the active
window changes to the
service management dialog
box of the corresponding
service type.
Service Name For example, CES Displays the name of the
port.
Transmission System
586
Used Resource For example, 64K
Timeslot1-31
Displays the resource used by
the service associated with
the port.

A.3 Parameter Description: MPLS
This topic describes the parameters related to MPLS.
A.3.1 Basic Configuration
Basic MPLS configuration focuses on setting of equipment LSR IDs.
Table A-12 lists parameters for basic MPLS configuration.
Transmission System
587
Table A-12 Parameter for basic MPLS configuration
LSR ID Example: 10.70.73.156 In a packet switched network
(PSN), one NE must be
allocated with a unique LSR
ID.
When planning the LSR ID
for an NE, adhere to the
following principles:
l The IP address of an NNI
port can be an IP address
of standard class A, B, or
C (namely, an IP address
within the range from
1.0.0.1 to
223.255.255.254). The IP
address of an NNI port
cannot be a broadcast
address (*.*.*.255),
multicast address
(224.0.0.0 to
239.255.255.255),
reserved address
(240.0.0.0 to
255.255.255.255),
network address (*.*.*.
0), zero address (0.*.*.*),
loopback address
(127.*.*.*). The address
of the network segment
used with priority:
172.16.0.0-172.31.255.2
55. In this network
segment, the number of
the available IP address is
1048574 (the 172.16.0.0
and 172.31.255.255 are
exceptional).
l Each NE must have an
independent and globally
unique LSR ID on a
network.
l The LSR ID of an NE and
the IP address of the NE
must be different from
each other and must be in
different network
segments.
Transmission System
588
l The SLR ID of an NE
must be in a different
network segment from the
IP address of any service
port on the NE.
After setting LSR IDs, enable
the MPLS function.
Otherwise, other functions of
the MPLS network cannot be
set.
Start of Global Label Space Example: 0 Specifies or displays the start
of global label space.
Global Label Space Size Example: 32768 Displays the size of global
label space.
Start of Multicast Label
Space
Example: 32768 Displays the start of multicast
label space.

A.3.2 Parameters for Configuring a Static Tunnel (on a Per-NE
Basis)
A static tunnel may be a unidirectional tunnel or a bidirectional tunnel.
Table A-13 lists parameters for configuring a static tunnel.
Table A-13 Parameters for configuring a static tunnel
Tunnel ID Example: 1 Displays or specifies the
tunnel ID.
Tunnel Name Example: name1
NOTE
The tunnel name contains a
maximum of 64 bytes.
Displays or specifies the
name of a tunnel.
Node Type Ingress, Egress, Transit Displays the type of a node.
Direction Unidirectional, Bidirectional Displays the direction of a
tunnel.
For a unidirectional tunnel,
Direction is Unidirectional
by default. For a bidirectional
tunnel, Direction is
Bidirectional by default.
Transmission System
589
Committed Information Rate
(kbit/s)
1024 to 10000000, Unlimited
Default value: 4294967295
(FFFFFFFFFF is invalid)
Committed Information
Rate (kbit/s) specifies the
committed information rate
(CIR) of a queue. When the
packet rate is smaller than or
equal to the CIR, all packets
can be forwarded. If the
packet rate is greater than the
CIR, some packets are
discarded based on specified
packet discarding policy.
Recommendations:
The greater CIR, the higher
rate of allowed traffic, and
the more packets forwarded.
It is recommended that the
equal to the CIR.
parameters:
This parameter can be set
only when Bandwidth
Limit is set to Enabled.
If the specified CIR are
applied to function points,
such as PWs and ports,
ensure that the sum of CIRs
in all policies applied to the
function point is smaller than
or equal to the CIR for the
function point.
Committed Burst Size (byte) - Specifies the committed
burst size.
NOTE
For a or a static tunnel, this
parameter is unavailable.
Peak Information Rate (kbit/
s)
- Specifies the maximum rate
of services allowed by the
PIR.
NOTE
Peak Burst Size (byte) - Specifies the peak burst size.
NOTE
Transmission System
590
In Board/Logic Interface
Type
Slot ID-Board name Displays or specifies the
ingress board port type or
logical port type.
In Port Example: 2(PORT-2) Displays or specifies the
ingress port of a tunnel.
This parameter can be set for
only egress and transit nodes.
In Label Example: 17 Displays or specifies ingress
labels of a tunnel. The ingress
labels must be unique on the
entire network.
In labels are supported only
when the equipment is
configured with a
unidirectional tunnel.
Forward In Label Example: 17 Displays or specifies ingress
labels of a forward tunnel.
Reverse Out Label Example: 18 Displays or specifies egress
labels of a reverse tunnel.
Out Board/Logic Interface
Type
Slot ID-Board name Displays or specifies the
egress board port type or
logical port type.
Out Port Example: 2(PORT-2) Displays or specifies the
egress port of a tunnel.
only ingress and transit
nodes.
Out Label Example: 19 Displays or specifies egress
labels of a tunnel. The egress
label must be unique on the
entire NE.
only the ingress node and the
transit node.
Out labels are supported only
when the equipment is
configured with a
unidirectional tunnel.
Transmission System
591
Forward Out Label Example: 20 Displays or specifies egress
labels of a forward tunnel.
Forward out labels are
supported only when the
equipment is configured with
a bidirectional tunnel.
Reverse In Label Example: 70 Displays or specifies ingress
labels of a reverse tunnel.
Reverse in labels are
supported only when the
a bidirectional tunnel.
Next Hop Address Example: 192.168.0.2 Displays or specifies the
next-hop address of a tunnel.
only for ingress and transit
nodes.
Forward Next Hop Address Example: 192.168.0.3 Displays or specifies the
Reverse Next Hop Address Example: 192.168.0.4 Displays or specifies the
Source Node Example: 192.168.0.5 Displays or specifies the
source node of a tunnel.
A source node can be
specified only for egress and
transit nodes.
Sink Node Example: 192.168.0.6 Displays or specifies the sink
node of a tunnel.
A sink node can be specified
nodes.
Tunnel Type E-LSP, L-LSP
Default value: E-LSP
tunnel type of a tunnel.
l E-LSP: An E-LSP uses
the EXP field for
prioritizing packet
scheduling.
l L-LSP: An L-LSP uses
the MPLS label value for
prioritizing packet
scheduling priority.
Transmission System
592
EXP 0, 1, 2, 3, 4, 5, 6, 7, None
Default value: None
EXP is a field in MPLS
packets for identifying
packet priority.
E-LSP is used to set the EXP.
7 indicates the highest
priority.
Value description:
l 0: The values 0 to 7
correspond to the eight
levels of the CoS policy.
The value 0 corresponds
to BE.
to AF1.
to AF2.
to AF3.
to AF4.
to EF.
to CS6.
Transmission System
593
to CS7.
Recommendations:
A larger value indicates a
higher packet priority.
LSP Mode Pipe, Uniform
Default value: Pipe
NOTE
OptiX OSN 550/500 equipment
only supports Pipe.
LSP Mode specifies the
mode in which the MPLS
network processes packet
priorities.
When a label is allocated to a
tunnel, the CoS policy of the
packets may be changed.
Therefore, it is necessary to
determine whether the CoS
policy of the packets needs to
be restored when the tunnel
label is stripped from the
packets. LSP Mode specifies
whether the CoS policy of
packets needs to be restored.
Value description:
l Pipe: Indicates that the
CoS policy of packets
does not need to be
restored after tunnel
labels are peeled off.
l Uniform: Indicates that
the CoS policy of packets
needs to be restored after
tunnel labels are peeled
off.
MTU - Specifies the maximum
transmission unit (MTU)
value of MPLS packets.
When MTU is 0, there is no
restriction on the MPLS
MTU. If the MPLS MTU
needs to be restricted, the
MPLS MTU must be smaller
than or equal to the MTU of
physical ports where the
tunnel is located.
NOTE

Transmission System
594
A.3.3 Parameters for Configuring a Static Tunnel (in End-to-End
Mode)
This section describes parameters for configuring a static tunnel.
Tunnel Name For example, Tunnel 1 Specifies the name of the
tunnel.
Reverse Tunnel Name For example, Tunnel1_RVS Specifies the name of a
reverse tunnel.
parameters:
only when Create Reverse
Tunnel is selected.
Protection Tunnel Name For example, Tunnel1_PRT Specifies the name of
protection tunnel.
parameters:
only when Protection Type
is set to 1+1 or 1:1.
Reverse Protection Tunnel
Name
For example,
Tunnel1_RVS_PRT
Specifies the name of reverse
protection tunnel.
parameters:
only when Protection Type
is set to 1+1 or 1:1.
Protocol Type MPLS, IP
Default value: MPLS
NOTE
On the OptiX OSN equipment,
Protocol Type must be set to
MPLS.
Specifies the protocol type
used by the tunnel.
Signaling Type Static CR, RSVP TE, LDP,
Static
Default value: Static CR
NOTE
Signaling Type must be set to
Static CR.
Specifies the signaling type
of the tunnel.
This parameter is
configurable only when you
set Protocol Type to MPLS.
Transmission System
595
Template - Specifies the template that is
used to configure tunnel
details.
parameters:
only when Signaling Type is
set to RSVP TE.
Service Direction Unidirectional, Bidirectional
Default value: Unidirectional
Specifies the service
direction of a tunnel.
l If this parameter is set to
Unidirectional, you need
to create only a service
from the service source to
the service sink. That is,
there is traffic only in the
direction from the service
source to the sink port.
l If this parameter is set to
Bidirectional, you need
to create a service from
the service source to the
service sink and a service
from the service sink to
the service source. That
is, there is traffic in both
the direction from the
service source to the sink
port and in the direction
from the service sink to
the source port at the same
time.
Create Reverse Tunnel Checked, Unchecked If Create Reverse Tunnel is
checked, a reverse tunnel is
created when a forward
tunnel is created. If Create
Reverse Tunnel is
unchecked, only a forward
tunnel is created.
Protection Type Protection-Free, 1+1, 1:1
Default value: Protection-
Free
NOTE
Protection Type must be set to
Protection-Free or 1:1.
Specifies the protection type
of a tunnel.
Transmission System
596
Protection Group Name For example, protection
group 1
Specifies the name of a
protection group.
Switching Mode Single-ended switching,
Dual-ended switching
Default value: Single-ended
switching
Specifies the switching mode
to be adopted when a tunnel
fails.
Remarks For example, NE(9-7032)-
NE(9-7037)
Specifies the remarks.
Remarks for a specific tunnel
facilitate management and
maintenance of the tunnel.
Auto-Calculate route Sets the value by clicking the
check box.
Checked, Unchecked
Default: Unchecked
If Auto Calculate Route is
checked, the system
automatically computes the
route after you select the
source node and sink node
and specify the NEs as
explicit/inexplicit nodes in
the physical topology.
Restriction Bandwidth (Kbit/
s)
1-Maximum bandwidth of
the port, No Limit
Default: No Limit
Specifies the upper
bandwidth limit.
When automatically
computing a route, the NMS
checks whether the computed
route meets the requirement
of Restriction Bandwidth
(Kbit/s).
Deploy Sets the value by clicking the
check box.
Checked, Unchecked
Default: Checked
Saves the tunnel
configuration on the NMS
and delivers the
configuration to NEs during
tunnel deployment.
Enable Sets the value by clicking the
check box.
Checked, Unchecked
Default: Checked
Automatically enables the
tunnel during tunnel
deployment.

Tunnel ID For example, 1 Displays or specifies the
tunnel ID.
Transmission System
597
Tunnel Interface - Displays the interface used
by the tunnel.
Reverse Tunnel Interface - Displays the interface used
by the reverse tunnel.
Bandwidth Type - Displays the bandwidth type
of the tunnel.
CIR(kbit/s) 1-Maximum bandwidth of
the port, No limit
Default: No limit
PIR(kbit/s) 64-Maximum bandwidth of
the port, No limit
Default: No limit
Specifies the allowed
maximum traffic rate.
CBS(bytes) 1-131072, No limit
Default: No limit
Specifies the committed
burst size.
PBS(bytes) 1-16777216, No limit
Default: No limit
Specifies the peak burst size.
LSP Type E-LSP E-LSP: The scheduling type
and the discard priority are
set in the EXP field in the
MPLS label.
Transmission System
598
EXP 0, 1, 2, 3, 4, 5, 6, 7, None
Default value: None
EXP is a field in MPLS
packets for identifying
packet priority.
E-LSP is used to set the EXP.
7 indicates the highest
priority.
Value description:
to BE.
to AF1.
to AF2.
to AF3.
to AF4.
to EF.
to CS6.
Transmission System
599
to CS7.
Recommendations:
A larger value indicates a
higher packet priority.
MTU(bytes) - Specifies the maximum
transmission unit (MTU)
value of MPLS packets.
When MTU is 0, there is no
restriction on the MPLS
MTU. If the MPLS MTU
needs to be restricted, the
MPLS MTU must be smaller
than or equal to the MTU of
physical ports where the
tunnel is located.
NOTE
LSP Mode Pipe, Uniform
Default value: Uniform
NOTE
OptiX OSN 550/500 equipment
only supports Pipe.
LSP Mode specifies the
mode in which the MPLS
network processes packet
priorities.
When a label is allocated to a
tunnel, the CoS policy of the
packets may be changed.
Therefore, it is necessary to
determine whether the CoS
policy of the packets needs to
be restored when the tunnel
label is stripped from the
packets. LSP Mode specifies
whether the CoS policy of
packets needs to be restored.
Value description:
l Pipe: Indicates that the
CoS policy of packets
does not need to be
restored after tunnel
labels are peeled off.
l Uniform: Indicates that
the CoS policy of packets
needs to be restored after
tunnel labels are peeled
off.
Transmission System
600
Node For example:NE(9-7032) Displays the node name
related to the tunnel.
Node Type Ingress, Egress, Transit Displays the node type.
LSP Name - Displays the LSP name.
Inbound Interface/Ring For example, 2(PORT-2) Displays or specifies the
ingress port of a tunnel.
Incoming Label For example, 17 Displays or specifies ingress
labels of a tunnel. The ingress
label must be unique on the
entire NE.
Outbound Interface/Ring For example, 2(PORT-2) Displays or specifies the
egress port of a tunnel.
nodes.
Outgoing Label For example, 19 Displays or specifies egress
labels of a tunnel. The egress
labels must be unique on the
entire network.
nodes.
Next Hop For example, 192.168.0.2 Displays or specifies the
nodes.

A.3.4 OAM Parameters
OAM parameters include Tunnel ID, Tunnel Name, Node Type, and OAM Status.
Table A-16 lists parameters for the OAM function.
Transmission System
601
Table A-16 Parameters for the OAM function
Tunnel ID Example: 3 Displays the tunnel ID.
Tunnel Name Character string Displays the tunnel name.
Node Type Ingress, Egress, Transit Displays the node type.
OAM Status Enabled, Disabled Specifies or displays the
OAM status.
l Enabled: OAM-related
operations can be
performed.
l Disabled: OAM-related
operations cannot be
performed.
Detection Mode Auto-Sending, Manual Specifies or displays the
detection mode.
l Manual: checks tunnel
continuity based on the
user specified type of
packets to be received and
the interval for receiving
packets.
l Auto-Sending: checks
tunnel continuity based
on the type of packets
received and the interval
for receiving packets.
Detection Packet Type CV, FFD Specifies the detection
packet type on an ingress
node.
l CV: indicates
connectivity verification.
In this mode, the interval
for transmitting detection
packets is always 1s.
l FFD: indicates fast
failure detection. In this
mode, the interval for
transmitting detection
packets can be set as
required.
Transmission System
602
Detection Packet Period (ms) 3.3, 10, 20, 50, 100, 200, 500 Specifies or displays the
detection packet period.
When Detection Packet
Type is set to FFD,
Detection Packet Period
(ms) can be set as required.
When Detection Packet
Type is set to CV, Detection
Packet Period (ms) has a
fixed value of 1000.
Reverse Tunnel Example: 3 Specifies reverse tunnels.
CV/FFD Status Stop, Start Displays the CV/FFD status.
LSP Status Near-End Available, Near-
End Defect Available, Near-
End Defect Unavailable,
Near-End Unavailable,
Remote Available, Remote
Defect Available, Remote
Defect Unavailable, Remote
Unavailable, Initialized
Displays the LSP status.
LSP Defect Type dServer, dLOCV,
dTTSI_Mismatch,
dTTSI_Mismerge, dExcess,
dUnknown
Displays the LSP defect type.
Disable LSP Duration (ms) 0 to 655350 Displays the duration when
the tunnel is unavailable.
LSP Defect Location Example: 192.168.11.1 Displays defect location in a
network using an IP address.
Source Node Example: 192.168.11.2 Displays the source node of a
tunnel.
Sink Node Example: 192.168.11.3 Displays the sink node of a
tunnel.

A.4 Parameter Description: Address Parse
Configuring the address parse function is to set the parameters such as ARP List IP, ARP List
MAC, and ARP List Type.
Table A-17 lists the parameters for the address parse function.
Transmission System
603
Table A-17 Parameters for the address parse function
Parameter Value Description
ARP List IP Example: 129.9.1.23 Configure the IP address in
the ARP list.
ARP List MAC Example: 1C-C4-31-88-1C-
C4
Configure the MAC address
corresponding to the IP
address in the ARP list.
ARP List Type Static, Dynamic Display the type of the ARP
list.

A.5 Parameter Description: Ethernet Private Line Services
(on a Per-NE Basis)
This topic describes the parameters related to Ethernet private line services.
A.5.1 E-Line Service Parameters
You need to set the parameters such as Service Name, Service ID, Direction, and Bearer
Type when configuring an E-Line service.
Table A-18 lists the parameters that are used for configuring an E-Line service.
Table A-18 Parameters for an E-Line service
Field Value Description
Service ID Example: 11 Set and query the ID of the Ethernet service.
Service Name Example: test Set and query the name of the Ethernet service.
Source Node Example:3-EM6F-1
(Port-1)(14)
Display the source node of the E-Line service.
The format is Slot number - Board name - Port
name (VLAN ID).
Sink Node Example: PW-0 Display the sink node of the E-Line service. The
sink node can be a port, PW or QinQ Link.
Direction UNI-UNI, UNI-NNI,
NNI-NNI
In the case of the UNI-NNI direction, select the
network-side bearer type as PW Port or QinQ
Link.
Transmission System
604
Service Tag
Role
User, Service
Default: User
Specifies how C-VLAN/S-VLAN tags of
packets are processed.
l User: C-VLAN/S-VLAN tags in user
packets are used as user VLAN tags. When
a packet leaves a PW, its user VLAN ID will
not be changed.
l Service: C-VLAN/S-VLAN tags in user
packets are used as service VLAN tags.
When a packet leaves a PW, its service
VLAN ID will be changed to the VLAN ID
configured for the services.
Source Port Example:3-EM6F-1
(Port-1)(1-2)
Set and query the user-side port or network-side
port.
Source VLANs 1-4094 Set one or several VLAN IDs, or not set any
VLAN ID.
PRI 0 to 7
Default: null
UNI-NNI E-Line services can be mapped to
different PWs based on Port+VLAN+VLAN
PRI. If packets need to be forwarded based on
Port+VLAN+VLAN PRI, set PRI to an integer
ranging from 0 to 7. Value 7 represents the
highest priority.
PRI can be set to null, one value, or several
values. If PRI is set to several values, separate
the values using commas; if PRI is set to an
interval, represent the interval in a form like 2-5.
l If PRI is set to null, packets are mapped to
different PWs based on VLAN IDs. In this
case, packets whose PRI is set to a value
within the range from 0 to 7 can be carried
in the E-Line service.
l If PRI is not set to null, packets are mapped
to different PWs based on Port+VLAN
+VLAN PRI. In this case, one service
VLAN ID must be added for the E-Line
service.
Sink Port Example:3-EM6F-1
(Port-1)(1-2)
Set and query the user-side port or network-side
port.
The equipment does not support this parameter
when Direction is set to UNI-UNI.
Sink VLANs 1-4094 Set one or several VLAN IDs, or not set any
VLAN ID.
The equipment does not support this parameter
when Direction is set to UNI-UNI.
Transmission System
605
Bearer Type PW, QinQ Link
Default value: PW
The Bearer Type (E-Line Service) parameter
specifies the bearer type for different types of
Ethernet services. The value of this parameter
can be set to PW, or QinQ Link.
Value description:
l PW: The bearer is the PW, and the PW ID
needs to be specified.
l QinQ Link: The bearer is the QinQ link, and
the QinQ link ID needs to be specified.
Recommendations:
l The bearer of the E-Line service V-NNI can
be the PW, or QinQ link.
l The bearer of the E-LAN service V-NNI can
be the PW, or QinQ link.
QinQ Link ID Example: 5 Select and display the QinQ Link ID.
Transmission System
606
BPDU Transparently
Transmitted, Not
Transparently
Transmitted
Default value: Not
Transparently
Transmitted
The BPDU parameter sets whether the service
needs transparently transmit the bridge protocol
data unit (BPDU) packets. The BPDU is the
information transmitted between bridges. It is
used to switch information between bridges, and
then the spanning tree of the network is
computed.
If the BPDU transparent transmission identifier
of the Ethernet service of an NE is enabled, the
port where the service V-UNI resides cannot
process the BPDU packets. After the BPDU
transparent transmission is enabled, the BPDU
packets are transmitted.
Value description:
l Transparently Transmitted: BPDU packets
are transparently transmitted to and
processed on the opposite NE instead of
being terminated on the local NE.
l Not Transparently Transmitted: BPDU
packets are processed as service packets,
which are processed differently according to
port attributes. When the port attribute is Tag
Aware, BPDU packets are discarded
because they do not carry any VLAN IDs.
Recommendations:
If the BPDU packets need be transparently
transmitted to the opposite end of the network,
set the BPDU to Transparently Transmitted
during the service creation.
If the BPDU packets need be processed on the
local NE as service packets for computing the
network spanning tree, set the BPDU to Not
Transparently Transmitted during the service
creation.
Association with other parameters:
If the BPDU is set to Transparently
Transmitted for the Ethernet services carried
by an Ethernet port, the MSTP cannot be
enabled. After the MSTP is enabled on the port,
the BPDU transparent transmission services
cannot be configured on the port.

Transmission System
607
A.5.2 UNI Parameters
Setting UNI parameters for an E-Line service focuses on setting of the VLAN information about
UNI ports.
Table A-19 lists UNI parameters for an E-Line service.
Table A-19 Parameters for a UNI port
Port For example, 3-
EM6F-1 (port-1)(1-2)
Indicates the UNI port.
VLANs 1 to 4094 Specifies or displays VLAN IDs.
Priority 0 to 7 Indicates the QoS level. A larger value indicates
a higher priority. When a network is busy,
packets with a higher VLAN priority are
processed first while those with a lower priority
may be discarded.

A.5.3 NNI Parameters
NNI parameters are used for NNI Ethernet services. According to different service bearer modes,
NNI parameters include the parameters that are used for a PW and a QinQ link.
PW
Table A-20 Parameters for a PW
PW ID Example: 123 Specifies the ID of the PW carrying the Ethernet
service.
Working Status Working, Protection Display the working status of the PW.
PW Status Enable, Disable Specifies or displays the enable status of the PW.
PW Signaling
Type
Static For a static PW, the label is manually allocated.
The configuration at the two ends of a PW should
be consistent.
PW Type Ethernet, Ethernet
Tagged Mode
PWs of different types process the borne services
differently. For example, the PW in the Ethernet
tagged mode attaches the tag on the services on
this PW.
PW Direction Bidirectional Specifies the direction of the PW.
Transmission System
608
PW
Encapsulation
Type
MPLS Displays the encapsulation type of the PW.
PW Incoming
Label/Source
Port
Only 2048 consecutive
values are allowed in
the value range from 16
to 32768
Specifies the ingress label of the PW.
PPW Outgoing
Label/Sink Port
to 32768
Specifies the egress label of the PW.
Peer LSR ID Example: 10.70.71.123 Set the opposite LSR ID of the PW.
Tunnel Type MPLS Displays the type of the tunnel that carries the
PW.
Egress Tunnel Tunnel ID
Example: 55
Displays the reverse tunnel ID.
Ingress Tunnel Tunnel ID
Example: 55
Displays the forward tunnel ID.
Transmission System
609
Control Word Not in use, Use
preferred
Default value: Not in
use
The Control Word parameter specifies the PW
control word usage policy.
The control word is the 4-byte encapsulation
packet header. The control word is used to
identify the packet sequence or function as
stuffing bits.
Value description:
l Not in use: Indicates that the control word is
not used.
l Use preferred: Indicates that the control word
is recommended.
l If Control Word of the PW is Not in use, do
not set Control Channel Type of the VCCV
to CW; if Control Channel Type of the
VCCV is CW, do not modify Control
Word of the PW to Not in use.
l Before changing the parameter value of a
PW, you need to ensure that the PW is not
bound with the service. After the change, you
need to bind the PW with the service, and
then check whether the parameter value is
changed.
NOTE
The PW control word must be consistently configured
at the two ends of the PW.
Transmission System
610
Control
Channel Type
None, CW, Alert Label
Default value: CW
NOTE
l For PWE3 ETH
services, Control
Channel Type for
PCXLG/PCXGA/
PCXGB boards with
PCBs of Ver.B can
be set to CW; the
default value for
Control Channel
Type is Alert
Label.
l For PWE3 ETH
services, Control
Channel Type for
PCXLG/PCXGA/
PCXGB boards with
PCBs of Ver.A
cannot be set to
CW; the default
value for Control
Channel Type is
Alert Label.
l For PWE3 ETH
services, Control
Channel Type for
PCXLX/PCXX
boards can be set to
CW; the default
value for Control
Channel Type is
Alert Label.
The Control Channel Type parameter specifies
the type of channels for transmitting VCCV
packets.
VCCV packets are exchanged between PEs to
verify connectivity of PWs.
Value description:
l None: Indicates that the control word is not
used to indicate the VCCV control channel
information.
l CW: Indicates that the control word is used
to indicate the VCCV control channel
information.
l Alert Label: Indicates VCCV packets in
Alert Label encapsulation mode.
changed.
VCCV
Verification
Mode
Ping, None Verify the connectivity of a PW. The VCCV
verification mode is a tool used to manually
verify the connectivity of a virtual circuit.
Local
Operating
Status
Up, Down Display the working status of the PW at the local
end. Up indicates that the PW works normally.
Down indicates that the PW work abnormally.
Remote
Operating
Status
Up, Down Display the working status of the PW at the
remote end. Up indicates that the PW works
normally. Down indicates that the PW work
abnormally.
Overall
Operating
Status
Up, Down Display the compositive working status of the
PW. Up indicates that the PW works normally.
Transmission System
611
Request VLAN 1-4094, Non-specified
Default value: Non-
specified
The Request VLAN parameter specifies the
ETH request VLAN.
In the case of static PW, the local equipment adds
the VLAN tag to the packets when before PW
encapsulation. In the case of the dynamic PW,
the opposite equipment adds the VLAN tag to
the packets before PW encapsulation if the local
equipment cannot add the VLAN tag.
Recommendations:
When the Request VLAN parameter is set to
Non-specified, the packets are added with 0
VLAN tags.
You need to set the PW Type parameter to
Ethernet Tagged Mode.
Before changing the parameter value of a PW,
you need to ensure that the PW is not bound with
the service. After the change, you need to bind
the PW with the service, and then check whether
the parameter value is changed.
Deployment
Status
Deployed, Undeployed Display the deployment status of the PW.
Automatic
Tunnel
Selection
Policy
For example: Static
MPLS Tunnel;
Dynamic RSVP TE
Tunnnel; IP
Tunnel;GRE Tunnel;
When Tunnel Selection Mode is set to Auto
Select, the NMS selects automatically the tunnel
for carrying a PW based on the tunnel priority
set in Tunnel Automatic Selection Policy.
TPID 0x88A8 Displays the protocol identification.

QinQ Link
Table A-21 Parameters for a QinQ link
QinQ Link ID Example: 5 Displays the QinQ Link ID.
Port Example: 3-EM6F-1 (Port-1) Displays the board and port.
S-Vlan ID Example: 4 Displays the S-VLAN ID.

Transmission System
612
A.5.4 VLAN Forwarding Table Item
The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table
item is created. In this case, a service from Source Interface to Sink Interface carries the VLAN
ID specified in Sink VLAN ID when the service is transmitted from Sink Interface.
Table A-22 Parameters for VLAN forwarding table items
Source Interface Type - Display the network attribute
of the source interface.
Source Interface - Specifies the source
interface.
Source VLAN ID 1 to 4094 Specifies the VLAN ID of the
source service.
Sink Interface Type V-UNI Display the network attribute
of the sink interface.
Sink Interface - Specifies the sink interface.
Sink VLAN ID 1 to 4094 Specifies VLAN ID of the
sink service.

A.5.5 Maintenance Association
The maintenance association (MA) facilitates the connectivity check (CC) of a network that
transports services.
Table A-23 lists the parameters for an maintenance association.
Table A-23 Parameters for an maintenance association
Maintenance
Domain Name
1-8 characters Specifies an MD name that is unique in the entire
network.
Maintenance
Association
Name
1-8 characters Specifies an MA name that is unique in the same
MD.
Transmission System
613
CC Test
Transmit Period
3.33ms, 10ms, 100ms,
1s, 10s, 1m, 10m
Default value: 1s
The source end MEP constructs the CC frames,
and then transmits them periodically to the
destination MEP. After the destination MEP
receives the CCM messages from the source
end, the CC check function of the source MEP
is directly started. Within a certain period (3.5
times of the transmission period), if the
destination MEP does not receive the CC
packets from the source end, an alarm is
automatically reported. The CC Test Transmit
Period parameter indicates the transmission
period of the unidirectional connectivity check.
After the CC check is started, a portion of the
bandwidth on the port is used.
Recommendations:
It is recommended that you use three period
values, that is, 3.33ms for protection switching,
100ms for performance check, and 1s for
connectivity check. The configuration should
comply with user requirements. If the fast check
is required, set to 3.33ms. Hence, the fault can
be detected quickly. The bandwidth used,
however, descends with the period value.

A.5.6 MEP Point
A maintenance association end point (MEP) is an edge point in a maintenance association (MA).
Table A-24 lists parameters for an MEP.
Table A-24 Parameters for an MEP
Maintenance
Domain Name
1 to 8 characters The name of a maintenance domain (MD)
should be unique over the entire network.
Maintenance
Association
Name
1 to 8 characters The name of an MA should be unique in the
same MD.
Board Example: 3-MD1 Displays the board where the MEP is located.
The format is slot number - board name.
Port Example: 3-MD1-1
(Port-1)
Displays the port where the MEP is located. The
format is slot number - board name - port
information
Transmission System
614
VLAN Example: 22 Specifies the VLAN ID of a service.
MEP ID 1 to 8191 Specifies a unique ID for each MEP. The IDs are
required for OAM operations.
Direction Ingress, Egress Ingress indicates the direction in which packets
enter a board. Egress indicates the direction in
which packets leave a board.
CC Status Active, Inactive Activates or deactivates the continuity check
function of an MEP.

A.6 Parameter Description: E-Line Services (End-to-End
Mode)
Before creating E-Line services carried by PWs, you need to configure the tunnel for carrying
the PWs. This section describes the parameters for configuring E-Line services in end-to-end
mode.
Table A-25 Parameters for configuring PWE3 services
Service Template
NOTE
This parameter is optional and
helps users quickly configure
various services. If this
parameter value is not
specified, the subsequent
service configuration is not
affected.
DEFAULT_PWE3_CES_P
TN,
DEFAULT_PWE3_ETH_P
TN,
DEFAULT_PWE3_ATM_P
TN
NOTE
does not support the following
service templates:
l DEFAULT_PWE3_ATM_
ROUTER
l DEFAULT_PWE3_CES_
ROUTER
l DEFAULT_PWE3_ETH_
ROUTER
l DEFAULT_PWE3_IWF_
ROUTER
l DEFAULT_PWE3_IP_R
OUTER
Displays and specifies the
PWE3 service template.
Service Type varies with
Service Template.
Service Template improves
service configuration
efficiency.
NOTE
After you select a service
template, a dialog box is
displayed, saying After the
template is changed, the
parameters not contained in
the new template may be lost.
Are you sure to continue? You
can also select Apply the
template data to the
configured Objects.
Transmission System
615
Service Type ETH, CES, ATM
NOTE
Specifies the required service
type based on the service
configuration. When the
PWE3 Ethernet services,
Service Type is set to ETH.
When the equipment is
configured with PWE3 CES
services, Service Type is set to
CES. When the equipment is
configured with PWE3 ATM
ATM
type of each PWE3 service.
Service ID Auto-Assign, or manually
enter it.
Default: Auto-Assign
Specifies the ID of each
PWE3 service, which is
unique on the entire network.
Service Name For example, E-Line-1
NOTE
The value of this parameter
contains 1 to 64 bytes.
Protection Type No Protection, PW APS
Default: No Protection
Specifies the protection
mode of the PW.
only when Mode is UNI-
NNI.
If this parameter is set to PW
APS, working and protection
PWs need to be configured.
Description For example, E-Line-1
NOTE
service description.
Customer - Displays and specifies the
customer to which a service
belongs.
Remarks - Displays and specifies the
service remarks.
Transmission System
616
ETH OAM CC Selected, Unselected
Default: unselected
When creating a PWE3
service, select ETH OAM
CC so that the continuity
check can be continuous.
ETH OAM CC can be
selected only when Service
Type is ETH.

Table A-26 SAI parameters
ID For example, 1 Displays and specifies the ID
of the service access port.
VLAN ID - Displays and specifies the
VLAN ID of the service
access port.
Priority Type Null, 802.1p
Default: Null
Specifies the priority type.
Priority Field 0 to 7
Default: Null
UNI-NNI E-Line services
can be mapped into different
PWs based on Port+VLAN
+VLAN PRI. Set this
parameter if packets need to
be forwarded based on Port
+VLAN+VLAN PRI This
parameter takes an integral
value ranging from 0 to 7.
Value 7 represents the
highest priority.
NOTE
This parameter takes effect only
when Priority Type is 802.1P.
Transmission System
617
Service Tag User, Service
Default: User
Specifies the way C-VLAN/
S-VLAN tags in user packets
are processed.
l User: C-VLAN/S-VLAN
tags in user packets are
used as user VLAN tags.
When a packet leaves a
PW, its user VLAN ID
will not be changed.
l Service: C-VLAN/S-
VLAN tags in user
packets are used as
service VLAN tags.
When a packet leaves a
PW, its service VLAN ID
will be changed to the
VLAN ID configured for
the services.

Table A-27 PW parameters
Role Working, Protection Displays and specifies the
role of a PW.
Source NE NE-Slot ID-Board-Port-
Higher order timeslot
source NE of a PW.
Sink NE NE-Slot ID-Board-Port-
sink NE of a PW.
PW ID Auto-Assign, or manually
enter it.
For example, 35
identifier of a PW.
Signaling Type Static Displays and specifies the
signaling type of a PW.
If you set Signaling Type to
Static, you need to set the
PW ingress label and PW
egress label. If you set
Signaling Type to
Dynamic, the system
automatically allocates the
egress label.
Transmission System
618
Forward Label For example, 20 Displays and specifies the
label that the service carries
when entering a PW.
l If you set Signaling
Type to Dynamic,
Forward Label is
automatically allocated
and cannot be specified
manually.
Type to Static, Forward
Label can be
automatically allocated or
specified manually.
Reverse Label For example, 20 Displays and specifies the
when leaving a PW.
Type to Dynamic,
Reverse Label is
manually.
Type to Static, Reverse
Label can be
specified manually.
Forward Type Static Binding Displays and specifies the
binding type of a forward
tunnel.
Forward Tunnel For example, NE1-NE2#1 Displays or specifies the
name of a forward tunnel.
NOTE
supports only Static Binding.
Reverse Type Static Binding Displays and specifies the
binding type of a reverse
tunnel.
Reverse Tunnel For example, NE2-NE1#1 Displays or specifies the
name of a reverse tunnel.
NOTE
Transmission System
619
Encapsulation Type MPLS Displays and specifies the
encapsulation type of a PW.
NOTE
supports only one tunnel type,
namely, MPLS tunnel.

Table A-28 Advanced PW parameters
PW Trail - Displays the trail of a PW.
Direction Bidirectional Displays the direction of a
PW.
PW Type l Ethernet
l Ethernet Tagged Mode
Default: Ethernet
l Ethernet: C-VLAN/S-
VLAN tags of packets are
encapsulated into PWs
without changes, and
transparently transmitted
to downstream sites.
l Ethernet Tagged Mode:
A VLAN tag specified by
Request VLAN is added
to packets.
PWs of different types
process their carried services
differently. To tag the
services carried by a PW, set
PW Type to Ethernet
Tagged Mode for the PW;
otherwise, set PW Type to
Ethernet.
Transmission System
620
Control Word l PWE3 ETH services: Not
in use and Use preferred
l CES services: Use
required
l ATM services: Not in use
and Use required
Default:
l PWE3 ETH services: Not
in use
l CES services: Use
required
l ATM services: Use
required
NOTE
In ATM ONE-to-ONE mode,
Control Word must be set to
Use required.
The Control Word
parameter specifies the PW
The control word is the 4-
byte encapsulation packet
header. The control word is
used to identify the packet
sequence or function as
stuffing bits.
Value description:
l Not in use: Indicates that
the control word is not
used.
l Use preferred: Indicates
that the control word is
recommended.
l Use required: Indicates
that the control word must
be used.
parameters:
l If Control Word of the
PW is Not in use, do not
set Control Channel
Type of the VCCV to
CW; if Control Channel
Type of the VCCV is
CW, do not modify
Control Word of the PW
to Not in use.
l Before changing the
parameter value of a PW,
you need to ensure that
the PW is not bound with
the service. After the
change, you need to bind
the PW with the service,
and then check whether
the parameter value is
changed.
NOTE
The PW control word must be
consistently configured at the
two ends of the PW.
Transmission System
621
Control Channel Type None, CW, Alert Label
Default: CW
NOTE
l For PWE3 ETH services,
Control Channel Type for
PCXLG/PCXGA/PCXGB
boards with PCBs of Ver.B
can be set to CW; the
default value for Control
Channel Type is Alert
Label.
PCXLG/PCXGA/PCXGB
boards with PCBs of Ver.A
cannot be set to CW; the
Label.
PCXLX/PCXX boards can
be set to CW; the default
value for Control Channel
Type is Alert Label.
The Control Channel Type
parameter specifies the type
of channels for transmitting
VCCV packets.
VCCV packets are
exchanged between PEs to
Value description:
l None: Indicates that the
control word is not used to
indicate the VCCV
control channel
information.
l CW: Indicates that the
control word is used to
indicate the VCCV
control channel
information.
l Alert Label: Indicates
VCCV packets in Alert
Label encapsulation
mode.
parameters:
set Control Channel
Type of the VCCV to
Type of the VCCV is
CW, do not modify
to Not in use.
changed.
Transmission System
622
VCCV Verification Mode None, Ping
Default: Ping
VCCV Verification Mode
specifies the verification
mode for virtual circuit
connectivity verification
(VCCV) packets.
Value description:
VCCV function is
disabled.
l Ping: Indicates that
VCCV is performed in
ping mode.
parameters:
Before changing a parameter
of a PW, ensure that the PW
is not bound with any service.
After the change, bind the
PW with services, and then
check whether the parameter
value is changed.
Transmission System
623
Default: Non-specified
The Request VLAN
parameter specifies the ETH
request VLAN.
In the case of static PW, the
local equipment adds the
VLAN tag to the packets
when before PW
encapsulation. In the case of
the dynamic PW, the
opposite equipment adds the
before PW encapsulation if
the local equipment cannot
add the VLAN tag.
Recommendations:
When the Request VLAN
parameter is set to Non-
specified, the packets are
added with 0 VLAN tags.
parameters:
You need to set the PW
Type parameter to Ethernet
Tagged Mode.
Before changing the
parameter value of a PW, you
need to ensure that the PW is
not bound with the service.
After the change, you need to
bind the PW with the service,
and then check whether the
parameter value is changed.

Transmission System
624
Table A-29 QoS parameters for service access ports
Role For example, Working
Source
role of a service access port.
Based on different protection
types, service access ports
can be classified into
different roles, for example,
working source, working
sink, protection source,
protection sink, FRR source,
and FRR sink.
SAI - Displays and specifies the
service access port.
Direction Ingress, Egress Displays and specifies the
direction of a service access
port.
l Ingress indicates the
ingress direction of the
service.
l Egress indicates the
egress direction of the
service.
Bandwidth Limited Enabled, Disabled
Default: Disabled
Specifies or displays the
bandwidth limit.
If you set Bandwidth
Limited to Enabled,
bandwidth limit is performed
based on the specified CIR,
PIR, CBS, and PBS.
Transmission System
625
Committed Information Rate
(kbit/s)
1024 to 10000000, Unlimited
Default: 4294967295
Recommendations:
The greater CIR, the higher
rate of allowed traffic, and
the more packets forwarded.
equal to the CIR.
parameters:
only when Bandwidth
Limit is set to Enabled.
If the specified CIR are
applied to function points,
such as PWs and ports,
ensure that the sum of CIRs
in all policies applied to the
function point is smaller than
or equal to the CIR for the
function point.
Transmission System
626
Committed Burst Size (byte) 64-10000000
Default: 4294967295
The Committed Burst Size
(byte) parameter specifies
the committed burst size.
When the bandwidth is
insufficient, some packets
cannot be forwarded.
Therefore, a buffer is
required to store these
packets for forwarding when
the bandwidth is sufficient.
CBS is the size of the buffer.
When the size of the stored
packets is less than the CBS,
all these packets can be
forwarded.
Recommendations:
If the CBS is small, the buffer
easily overflows and some
packets are discarded when
the bandwidth is insufficient.
The greater the CBS is, the
more packets can be buffered
when the bandwidth is
insufficient, and the less the
packet loss ratio is. The
greater the CBS, the more
serious the delay jitter when
packets are forwarded.
For the OptiX OSN
equipment, the CBS is
reserved and cannot be set.
Peak Information Rate (kbit/
s)
64 to 10000000
Default: 4294967295
Peak Information Rate
(kbit/s) specifies the
maximum rate of services
allowed by the PIR.
Recommendations:
PIR be greater than or equal
to the (committed
information rate) CIR.
Transmission System
627
Peak Burst Size (byte) 64-10000000
Default: 4294967295
The Peak Burst Size (byte)
parameter specifies the size
of the PBS.
When the bandwidth is
insufficient and the CBS
buffer is full, the packets that
cannot be stored in the CBS
buffer are stored in the PBS
buffer. When the PBS buffer
is full, the extra packets are
discarded. The packets stored
in the PBS buffer may also
fail to be forwarded. The
packets whose rates are more
than the CIR and less than the
PIR attempt to preempt the
remaining bandwidth. The
packets are forwarded only
when they preempt the
remaining bandwidth.
Recommendations:
Although the packets in the
PBS buffer may also fail to be
forwarded, the PBS buffer
decreases the packet loss
ratio.
The greater the PBS, the less
the packet loss ratio, and the
more serious the delay jitter
when packets are forwarded.
Local QoS Policy - Displays the QoS policy at
the local end.
Transmission System
628
Default Forwarding Priority CS6, CS7, EF, AF1, AF2,
AF3, AF4, BE, None
Displays the service
forwarding priority.
Different values represent
different service classes.
l CS6-CS7: indicate the
highest service class,
which is mainly
applicable to signaling
transmission.
l EF: indicates the
expedited forwarding of
service, which is
applicable to services (for
example, voice services)
of low transmission delay
and low packet loss rate.
l AF1-AF4: indicate the
ensured forwarding class
of service, which is
applicable to services that
require an ensured rate
rather than delay or jitter
limit.
l BE: is applicable to
services that do not need
to be processed in a
special manner.
Default Packet Marking
Color
Red, Yellow, Green, None Displays the default packet
marking color.
Based on the labels carried by
the packets, different colors
are set for marking the
packets. Red packets have the
highest discarding priority.

A.7 Parameter Description: E-LAN Service (on a Per-NE
Basis)
This topic describes the parameters related to the E-LAN Service configuration.
Transmission System
629
A.7.1 E-LAN Service Parameters
This topic describes the parameters, such as Service ID and Service Name, for configuring an
E-LAN service.
Table A-30 lists the parameters for configuring an E-LAN service.
Table A-30 Parameters for configuring an E-LAN service
Service ID For example, 11 Specifies the ID of the Ethernet service.
Service Name For example, test Specifies the name of the Ethernet service.
BPDU Not Transparently
Transmitted
Displays whether bridge protocol data unit
(BPDU) packets can be transparently
transmitted.
The value is Not Transparently Transmitted
for E-LAN services
Tag Type l C-Aware
l S-Aware
l Tag-Transparent
Default: C-Aware
C-Aware: indicates that learning is based on the
C-TAG (client-side VLAN tag).
S-Aware: indicates that learning is based on the
S-TAG (operator service-layer VLAN tag). S-
Aware is valid only when Encapsulation
Type is set to QinQ for a port.
Tag-Transparent: indicates that all Ethernet
packets can be transmitted transparently when
Encapsulation Type is set to Null for a port.
Self-Learning
MAC Address
Enabled, Disabled
Default: Enabled
Adds self-learnt MAC addresses to the MAC
address forwarding table.
MAC Address
Learning Mode
l SVL
l IVL
Default: IVL
SVL indicates the shared VLAN learning. All
VLANs share a MAC address forwarding table.
Each MAC address is unique in the forwarding
table.
IVL indicates independent VLAN learning. The
forwarding tables for different VLANs are
independent from each other. It is acceptable
that the MAC address forwarding tables for
different VLANs have the same MAC address.
When Tag Type is set to Tag-Transparent, the
parameter value is SVL by default and is not
configurable.
NOTE
For the OptiX OSN 550/500 equipment, VPLS
services support only the SVL mode, and Native E-
LAN services support both the SVL and IVL modes.
Transmission System
630
MTU(bytes) 64 to 9600
Default value: 1500
NOTE
For the OptiX OSN
550/500 equipment, this
field is inapplicable.
Specifies the maximum transmission unit
(MTU). If the length of a packet received by a
port exceeds the MTU, the port discards the
packet.
Service Tag
Role
- Specifies the service-delimiting tag.
NOTE
E-LAN services on the OptiX OSN equipment do not
Multicast Ring
Protocol
Enabled, Disabled
Default value:
Disabled
If the networking mode of VPLS services is set
to Daisy Chain and the network bears multicast
services, this protocol should be enabled to
check the ring network status and adjust service
blocking configurations.
The Blocking of a PW on the NNI tab can be
configured only after Multicast Ring Protocol
is enabled.
NOTE
This parameter is available in V100R007C00 or later.
Protection Type l Unprotected
l PW APS
l Slave Protection
Pair
Specifies the protection type.

A.7.2 UNI
This section describes the user-to-network interface (UNI) parameters required for configuring
an E-LAN service. You need to configure VLAN information on UNIs.
For the OptiX OSN 550/500 equipment, Table A-31 lists UNI parameters required for
configuring an E-LAN service.
Table A-31 UNI parameters required for configuring an E-LAN service
Port Slot ID-Board name-Port ID
(PORT-Port ID)
For example, 3-EM6F-2
(PORT-2)
Specifies a UNI.
Transmission System
631
SVLAN/
SVLANs
1-4094 Specifies the VLAN ID of a service
provider.
VLANs/
CVLAN
1-4094 Specifies the VLAN ID of a customer.
You can leave this parameter blank or
configure one or more VLAN IDs.
VLAN Filtering
Table
1-4094 Specifies the VLAN filtering table.
l This parameter determines VLAN
packets that can be transmitted by the
UNI. The UNI can transmit packets
only from VLANs in the VLAN
filtering table.
l Only a virtual private LAN service
(VPLS) service that exclusively uses
a UNI supports this parameter.
l You can leave this parameter blank or
configure one or more VLANs. If
multiple VLANs are configured, use a
comma to separate each value or use
an en dash (-) to specify a value range
(for example, 2-5).

A.7.3 NNI
This section describes the network-to-network interface (NNI) parameters required for
configuring an E-LAN service. NNI parameters are categorized into PW parameters and port
parameters based on the service bearing mode.
PW Parameters
Table A-32 Parameters for a PW
PW ID Example: 123 Specifies the ID of the PW carrying the Ethernet
service.
Working Status Working, Protection Display the working status of the PW.
PW Status Enable, Disable Specifies or displays the enable status of the PW.
PW Signaling
Type
Static For a static PW, the label is manually allocated.
The configuration at the two ends of a PW should
be consistent.
Transmission System
632
Tagged Mode
PWs of different types process the borne services
differently. For example, the PW in the Ethernet
tagged mode attaches the tag on the services on
this PW.
PW Direction Bidirectional Specifies the direction of the PW.
PW
Encapsulation
Type
MPLS Displays the encapsulation type of the PW.
PW Incoming
Label/Source
Port
to 32768
Specifies the ingress label of the PW.
PPW Outgoing
Label/Sink Port
to 32768
Specifies the egress label of the PW.
Peer LSR ID Example: 10.70.71.123 Set the opposite LSR ID of the PW.
Tunnel Type MPLS Displays the type of the tunnel that carries the
PW.
Egress Tunnel Tunnel ID
Example: 55
Displays the reverse tunnel ID.
Ingress Tunnel Tunnel ID
Example: 55
Displays the forward tunnel ID.
Transmission System
633
Control Word Not in use, Use
preferred
Default value: Not in
use
The Control Word parameter specifies the PW
The control word is the 4-byte encapsulation
packet header. The control word is used to
identify the packet sequence or function as
stuffing bits.
Value description:
l Not in use: Indicates that the control word is
not used.
l Use preferred: Indicates that the control word
is recommended.
changed.
NOTE
The PW control word must be consistently configured
at the two ends of the PW.
Transmission System
634
Control
Channel Type
None, CW, Alert Label
Default value: CW
NOTE
l For PWE3 ETH
services, Control
Channel Type for
PCXLG/PCXGA/
PCXGB boards with
PCBs of Ver.B can
be set to CW; the
default value for
Control Channel
Type is Alert
Label.
l For PWE3 ETH
services, Control
Channel Type for
PCXLG/PCXGA/
PCXGB boards with
PCBs of Ver.A
cannot be set to
CW; the default
value for Control
Channel Type is
Alert Label.
l For PWE3 ETH
services, Control
Channel Type for
PCXLX/PCXX
boards can be set to
CW; the default
value for Control
Channel Type is
Alert Label.
The Control Channel Type parameter specifies
the type of channels for transmitting VCCV
packets.
VCCV packets are exchanged between PEs to
Value description:
l None: Indicates that the control word is not
used to indicate the VCCV control channel
information.
l CW: Indicates that the control word is used
to indicate the VCCV control channel
information.
l Alert Label: Indicates VCCV packets in
Alert Label encapsulation mode.
changed.
VCCV
Verification
Mode
Ping, None Verify the connectivity of a PW. The VCCV
verification mode is a tool used to manually
verify the connectivity of a virtual circuit.
Local
Operating
Status
Up, Down Display the working status of the PW at the local
end. Up indicates that the PW works normally.
Remote
Operating
Status
Up, Down Display the working status of the PW at the
remote end. Up indicates that the PW works
normally. Down indicates that the PW work
abnormally.
Overall
Operating
Status
Up, Down Display the compositive working status of the
PW. Up indicates that the PW works normally.
Transmission System
635
Default value: Non-
specified
The Request VLAN parameter specifies the
ETH request VLAN.
In the case of static PW, the local equipment adds
the VLAN tag to the packets when before PW
encapsulation. In the case of the dynamic PW,
the opposite equipment adds the VLAN tag to
the packets before PW encapsulation if the local
equipment cannot add the VLAN tag.
Recommendations:
When the Request VLAN parameter is set to
Non-specified, the packets are added with 0
VLAN tags.
You need to set the PW Type parameter to
Ethernet Tagged Mode.
Before changing the parameter value of a PW,
you need to ensure that the PW is not bound with
the service. After the change, you need to bind
the PW with the service, and then check whether
the parameter value is changed.
Deployment
Status
Deployed, Undeployed Display the deployment status of the PW.
Automatic
Tunnel
Selection
Policy
For example: Static
MPLS Tunnel;
Dynamic RSVP TE
Tunnnel; IP
Tunnel;GRE Tunnel;
When Tunnel Selection Mode is set to Auto
Select, the NMS selects automatically the tunnel
for carrying a PW based on the tunnel priority
set in Tunnel Automatic Selection Policy.
TPID 0x88A8 Displays the protocol identification.

Port Parameters
Table A-33 NNI parameters for configuring an E-LAN service
Port Slot ID-Board name-
Port ID(PORT-Port
ID)
For example: 3-
EM6F-2(PORT-2)
Specifies the NNI.
SVLANs 1-4094 Specifies the VLAN ID of a service provider.

Transmission System
636
A.7.4 Split Horizon Group
A split horizon group is a group of V-UNIs or V-NNIs that do not allow for interconnection at
one station. The split horizon group prevents a cycling route and a loop.
Table A-34 lists the parameters for a split horizon group.
Table A-34 Parameters for a split horizon group
Split Horizon
Group ID
For example, 1 The Split Horizon Group ID parameter
identifies the split horizon group.
Split Horizon
Group Member
For example, PW-100,
3-EM6F-1(PORT-1)
The Split Horizon Group Member parameter
indicates the logical port member in a split
horizon group.

A.7.5 MAC Address Learning Parameters
This topic describes the parameters, such as Aging Ability, Aging Time, and Address Table
Specified Capacity, for configuring the MAS address learning function.
Table A-35 lists the parameters for MAC address learning.
Table A-35 Parameters for MAC address learning
Aging Ability Enabled, Disabled
Default: Enabled
If no packets of an MAC address listed in the
MAC address table are received during a period,
the MAC address is deleted from the MAC
address table.
Aging Time
(min)
1-640
Default: 5
Set the Aging Time (min) parameter to set the
aging time of the learnt MAC address. The
Aging Time (min) parameter indicates that the
MAC address is automatically aged after the
timing is set.
Address Table
Specified
Capacity
0-65534
Default: 512
Sets the capacity of the MAC address table.
NOTE
Address Table Specified Capacity restricts dynamic
MAC addresses and does not restrict static MAC
addresses.
Transmission System
637
Address
Detection Upper
Threshold (%)
80-100
Default: 95
Sets a value of Address Table Specified
Capacity to the upper threshold for address
detection. The upper threshold needs to be
higher than the value of Address Detection
Lower Threshold (%). If the number of MAC
addresses actually learnt is more than the upper
threshold, the FDBSIZEALM_ELAN alarm is
generated.
Address
Detection
Lower
Threshold (%)
60-100
Default: 90
Sets a value of Address Table Specified
Capacity to the lower threshold for address
detection. The lower threshold needs to be lower
than the value of Address Detection Upper
Threshold (%).

A.7.6 Unknown Frame Processing
If the MAC address table fails to learn the MAC address of a packet, the MAC address table
considers this packet as an unknown frame.
Table A-36 lists the parameters for unknown frame processing.
Table A-36 Parameters for unknown frame processing
Frame Type Unicast, Multicast Displays the type of the received unknown
frames.
Handing Mode Discard, Broadcast
Default: Broadcast
Selects the mode for handling the unknown
frames. Discard indicates that unknown frames
are directly discarded. Broadcast indicates that
unknown frames are broadcast at the forwarding
port.

A.7.7 Static MAC Address
Static MAC addresses refer to a MAC address table manually set for the service. Entries in the
MAC address table are not automatically aged. Hence, unnecessary entries need to be manually
deleted.
Table A-37 lists the parameters for a static MAC address.
Transmission System
638
Table A-37 Parameters for a static MAC address
VLAN ID For example, 12 Sets the ID of the service.
MAC Address For example, 00-e0-
fc-39-80-34
Sets a static MAC address.
Egress Interface For example, PW-100 Sets the egress interface, which can be a PW,
port.

A.8 Parameter Description: E-LAN Services (in End-to-End
Mode)
Before creating E-LAN services carried by pseudo wires (PWs), you need to configure the tunnel
that carries PWs and configure the virtual switch instance (VSI) attribute of NEs as NPE. This
section describes the parameters for configuring E-LAN services in end-to-end mode.
Table A-38 Parameters for the basic VPLS attributes
Service Name For example, E-LAN Specifies the name of the E-
LAN service.
Signal Type l LDP/Static
l BGP
Specifies the signaling type.
l LDP/Static:
LDP: indicates the
label distribution
protocol used for
configuring or
maintaining PWs.
Static: you need to set
the incoming and
outgoing labels of a
PW manually.
l BGP: indicates the
boundary gateway
protocol, which is used
for signaling exchanges
on a mesh network.
NOTE
currently supports only manual
Static allocation mode. This
parameter can only set to LDP/
Static
Transmission System
639
Service Template - Specifies the service
template. You can select a
predefined service template
mapping to the related NE
type. If you do not select a
predefined service template,
you need to manually set all
VPLS parameters.
Networking Mode l Full-Mesh VPLS
l H-VPLS
l Daisy Chain
l Hub-Spoke
l Ring
l Customized
Specifies the networking
mode of Ethernet services.
l If Networking Mode is
set to Full-Mesh VPLS,
only the network provider
edge (NPE) attribute of an
NE can be specified.
set to H-VPLS, the NPE
or user-end provider edge
(UPE) attribute of an NE
can be specified.
set to Daisy Chain, only
the UPE attribute of an
NE can be specified.
set to Customized, only
the PE attribute of an NE
can be specified.
NOTE
This parameter can be set only
to Full-Mesh VPLS, H-
VPLS, Ring or Customized
for the OptiX OSN equipment.
Transmission System
640
Service Type l Service VPLS
l Management VPLS
l E-Tree
Specifies the VPLS type.
l Service VPLS: indicates
a common end-to-end
VPLS service.
l Management VPLS:
indicates a VPLS service
that monitors or manages
one or more common end-
to-end VPLS services.
l E-Tree: indicates a point
to multipoint (PTMP)
Ethernet multicast
service.
NOTE
to Service VPLS or
Management VPLS for the
OptiX OSN equipment.
VSI Name For example, VPLS1 Specifies the VPLS service
name.
VSI: indicates the virtual
switching instance. The VSI
name on an NE must be
unique.
VSI ID For example, 31 Specifies the VSI ID.
The VSI ID can be
automatically assigned.
The value of VSI ID cannot
be changed. Each VSI ID on
an NE must be unique.
VSI Description - Specifies description
information (usually
information about functions)
about a VSI.
Customer - Specifies the customer who
has the configured service.
Remarks - Specifies remarks related to
the configured service.
Transmission System
641
ETH OAM CC Select or clear the check box.
The check box is cleared by
default.
Ethernet OAM continuity
check (CC) function is
enabled. If the ETH OAM
CC check box is selected
during VPLS service
creation, Ethernet OAM CCs
will be performed regularly.

Table A-39 Parameters for ring
Ring Name - Indicates the name of a ring.
parameters:
only when Networking
Mode is Ring.
Ring ID - Indicates the ID of a ring.
parameters:
Mode is Ring.

Table A-40 Parameters for the basic VSI attributes
VSI's signal type l LDP/Static
l BGP
Specifies the signaling type.
l LDP/Static: indicates the
LDP protocol used to
configure or maintain
PWs.
l BGP: indicates the
Border Gateway Protocol
(BGP) used for
exchanging signaling
information on mesh
networks.
NOTE
does not support this parameter.
Transmission System
642
VSI Name For example, VPLS1 Specifies the VPLS service
name.
VSI ID For example, 31 Specifies the VSI ID.
The VSI ID can be
The value of VSI ID cannot
be changed. Each VSI ID on
an NE must be unique.
VSI Type l Service VPLS
l Management VPLS
l E-Tree
Specifies the VSI type
mapping to a VPLS service
type.
l IfService Type is set to
Service VPLS for a
VPLS service, set this
parameter to Service
VPLS.
l IfService Type is set to
Management VPLS for
a VPLS service, set this
parameter to
Management VPLS or
Service VPLS.
l If Service Type is set to
E-Tree for a VPLS
service, set this parameter
to E-Tree or Service
VPLS.
Encapsulation Type - Specifies the encapsulation
type of incoming and
outgoing packets at AC-side
ports on L2VPNs.
NOTE
MTU - Specifies the maximum
transmission unit (MTU) of a
VSI.
NOTE
Transmission System
643
Tunnel Policy - Specifies the policy used to
select a tunnel for carrying
VPLS services between PEs.
The policy also specifies
whether to use the load-
sharing mode.
NOTE
Tag Type l C-Aware
l S-Aware
l Tag-Transparent
Default: C-Aware
Specifies the tag type.
C-Aware: indicates that
learning is based on the C-
TAG (customer-side VLAN
tag).
S-Aware: indicates that
learning is based on the S-
TAG (operator service-layer
VLAN tag). This value is
valid only when
Encapsulation Type is set to
QinQ for a port.
Tag-Transparent: indicates
that all Ethernet packets can
be transparently transmitted
if Encapsulation Type is set
to Null for a port.
NOTE
to C-Aware or S-Aware for the
OptiX OSN equipment.
Service Tag Role - Specifies the service-
delimiting tag.
NOTE
Bound to mVSI - This parameter is valid only
when VSI Type is set to
Service VPLS.
NOTE
Description - Specifies description
information (usually
information about functions)
about a VSI.
Transmission System
644

Table A-41 Parameters for forwarding control
MAC Address Learning Enable, Disable
Default: Enable
Specifies whether to enable
the MAC address learning
function.
Learning Mode Qualify(IVL), Unqualify
(SVL)
Specifies the bridge learning
mode of E-LAN services.
l Qualify(IVL): The
bridge type is IEEE
802.1q or IEEE 802.1ad.
MAC address learning is
based on VLANs of the
VSI. Each VLAN has its
MAC address space. The
MAC address space of
different VLANs can be
overlapped.
l Unqualify(IVL): The
bridge type is IEEE
802.1d or IEEE 802.1ad.
MAC address learning is
based on VSIs. Each VSI
has an MAC address
space.
NOTE
equipment, VPLS services
support only the SVL mode,
and Native E-LAN services
support both the SVL and IVL
modes.
Max.Leant MAC Addresses Default: 512 Specifies the maximum
number of learnt MAC
addresses.
MAC Address Aging Enable, Disable
Default: Enable
Specifies whether to enable
the MAC address aging
function.
After the MAC address aging
function is enabled, a MAC
address is deleted from the
MAC address table if no
packets that contain the MAC
address are received within a
certain period of time.
Transmission System
645
MAC Address Aging Time Default: 300 Specifies the aging time of
MAC addresses.
If the MAC address aging
function is enabled, the
system deletes a MAC
address if no packets that
contain the MAC address are
received after the aging time
expires.
If the MAC address aging
function is disabled, this
MAC Address Detection
Upper Threshold
80% to 100%
Default: 95%
Specifies the upper threshold
of detected MAC addresses.
The value of MAC Address
Detection Upper
Threshold needs to be
greater than the value of
Lower Threshold. When the
number of learnt MAC
addresses is greater than the
upper threshold, an alarm is
reported.
Lower Threshold
60% to 100%
Default: 90%
Specifies the lower threshold
of MAC addresses detection.
Multicast Broadcast, Discard
Default: Broadcast
Specifies how to process
unknown multicast packets.
Unicast Broadcast, Discard
Default: Broadcast
Specifies how to process
unknown unicast packets.
Enable BPDU Transparent
Transmission
Not Transparently
Transmitted
Specifies whether to
transparently transmit BPDU
packets.

role of a PW.
Transmission System
646
source NE of a PW.
sink NE of a PW.
enter it.
For example, 35
identifier of a PW.
Signaling Type to
Dynamic, the system
egress label.
when entering a PW.
Type to Dynamic,
Forward Label is
manually.
Label can be
specified manually.
Transmission System
647
when leaving a PW.
Type to Dynamic,
Reverse Label is
manually.
Label can be
specified manually.
tunnel.
NOTE
tunnel.
NOTE
NOTE
Transmission System
648
Forward Blocking Point Enable, Disable
Default value: Disable
If this parameter is
configured, the U2000
controls packet loopbacks to
protect multicast services.
parameters:
Mode is Ring.
Reverse Blocking Point Enable, Disable
If this parameter is
configured, the U2000
controls packet loopbacks to
protect multicast services.
parameters:
Mode is Ring.

A.9 Parameter Description: CES Services
This topic describes the parameters related to CES services.
A.9.1 Basic Attributes (UNI-NNI)
This section describes parameters for configuring and displaying basic attributes of CES
services.
Table A-43 Parameters for basic attributes of PWs
Service ID For example, 1 Displays the service ID.
Service Name For example, CES-1 Displays the CES service name.
Level E1 Displays the level of received CES
services.
Mode UNI-NNI Displays the CES service mode.
UNI-NNI indicates CES services
from the user side to the network
side.
Transmission System
649
Source Board Slot-Board Name-Port
(Port No.)
For example, 3-MD1-1
(PORT-1)
Specifies the source board of a CES
service.
Source High Channel - Specifies the source higher order
path.
For a line port, set the number of the
VC-4 path.
NOTE
OptiX OSN equipment does not support
this parameter.
Source Low Channel For example, 1 Specifies the source lower order
path.
For an E1 port, specify the number of
the E1 port; for a line port, you need
to set the number of the VC-12 path.
Source 64K Timeslot For example, 1 to 31 Specifies the source 64 kbit/s
timeslot for compression.
NOTE
You must specify two or more 64 kbit/s
timeslots.
Sink Board Slot-Board Name-Port
(Port No.)
For example, 4-MD1-2
(PORT-2)
Specifies the sink board of a CES
service.
Sink High Channel - Specifies the sink higher order path.
VC-4 path.
NOTE
OptiX OSN equipment does not support
this parameter.
Sink Low Channel For example, 1 Specifies the sink lower order path.
the E1 port; for a line port, you need
to set the number of the VC-12 path.
Sink 64K Timeslot For example, 1 to 31 Specifies the source 64 kbit/s
NOTE
timeslots.

Transmission System
650
A.9.2 Basic Configuration Parameters (UNI-NNI)
This section describes parameters for configuring and querying CES services.
Table A-44 Parameters for basic information of CES service management
Service ID (e.g.1,3-6) Example: 1 Displays the service ID.
Service Name Example: CES-1 Displays the CES service name.
Level E1 Displays the level of received CES
services.
Mode UNI-NNI Displays the CES service mode.
UNI-NNI indicates CES services
from the user side to the network
side.
Source Board Slot-Board Name-Port
(Port No.)
Example: 4-MD1-1
(PORT-1)
Specifies the source board of a CES
service.
Source High Channel - Specifies the source higher order
path.
VC-4 path.
Source Low Channel (e.g.
1,3-6)
Example: 1 Specifies the source lower order
path.
the E1 port; for a line port, set the
number of the VC-12 path.
Source 64K Timeslot (e.g.
1,3-6)
Example: 1 to 31 Specifies the source 64 kbit/s
NOTE
timeslots.
Priority List CS7, CS6, EF, AF4,
AF3, AF2, AF1, BE
Specifies the UNI priority.
Transmission System
651
PW Type CESoPSN, SAToP Specifies the PW type.
l CESoPSN: indicates structure-
aware TDM circuit emulation
service over packet switched
network. Timeslot compression
can be set.
l SAToP: indicates structure-
agnostic TDM over packet.
Timeslot compression cannot be
set.
Protection Mode No Protection, PW
APS, Slave Protection
Pair
Specifies the protection mode of a
PW.
If working and protection PWs in
multiple PW APS slave protection
pairs respectively have the same
source and sink as working and
protection PWs in an existing PW
APS protection group, these slave
protection pairs can be bound with
the existing protection group to share
OAM resources and achieve
synchronous detection and
switching.

Table A-45 General attributes of a PW
PW ID Example: 1 Specifies the PW ID.
Transmission System
652
PW Signaling Type Static PW Signaling Type specifies the
allocation mode (automatic or
manual) of ingress and egress nodes
of a PW.
When PW Signaling Type is set to
Automatic, the ingress and egress
nodes of a PW are allocated
automatically. When PW Signaling
Type is set to Manual, the ingress
and egress nodes of a PW must be set
manually.
Value description:
Static: Indicates that ingress and
egress nodes of a PW manually must
be set manually.
Recommendations:
OptiX OSN equipment currently
supports only Static allocation
mode.
Tagged Mode
Displays the PW type.
When Service Type is set to
Ethernet Service, PW Type can be
set to only Ethernet or Ethernet
Tagged Mode.
Direction Bidirectional Displays the direction of a PW.
PW Encapsulation Type MPLS Displays the encapsulation type of
packets on a PW.
PW Ingress Label/Source
Port
Example: 17 This parameter needs to be set when
PW Signaling Type is set to Static.
PW Egress Label/Sink Port Example: 18 This parameter needs to be set when
PW Signaling Type is set to Static.
Tunnel Section Mode Manually Specifies a tunnel that carries PWs.
Tunnel Type MPLS Displays the type of a tunnel that
carries PWs.
Tunnel Example: 43 Selects a created tunnel. If no tunnel
is available, PW creation fails.
Opposite LSR ID Example:
10.70.71.123
Specifies the LSR ID of a PW at the
remote end.
If Tunnel is selected, Opposite LSR
ID is automatically assigned on the
NMS.
Transmission System
653

A.9.3 Advanced Attributes (UNI-NNI)
This topic describes the parameters that are used for configuring and querying the advanced
attributes of CES services.
Table A-46 Parameters for the advanced attributes of a PW
RTP Header Disable, Enable the
Huawei RTP, Enable a
Standard RTP
NOTE
OptiX OSN equipment
does not support Enable
a Standard RTP.
The RTP Header parameter
specifies whether the RTP header
function is enabled.
The RTP header is used to load clock
signals.
Value description:
l Disable: Indicates that the RTP is
disabled.
l Enable the Huawei RTP:
Indicates that the Huawei RTP is
enabled.
l Enable a Standard RTP: Indicates
that a standard RTP is enabled.
Transmission System
654
Jitter Compensation
Buffering Time (us)
375-16000
Default value: 8000
The Jitter Compensation
Buffering Time (us) parameter
specifies the size of the jitter buffer.
The jitter compensation buffering
time is configured to absorb jitters on
the network side.
The jitter compensation buffering
time affects the delay of services.
If the jitter compensation buffering
time is set, the subsequent operations
are performed after the system has
received packets for more than a half
of the jitter compensation buffering
time.
Recommendations:
The value of the jitter compensation
buffering time ranges from 125 to
64000 in steps of 125.
parameters:
The packet loading time is closely
related to the jitter compensation
buffering time. The jitter
compensation buffering time must be
greater than double packet loading
time.
Transmission System
655
Packet Loading Time (us) 125-5000
Default value: 1000
The Packet Loading Time (us)
parameter specifies the packet
loading duration.
The efficiency of packet loading can
be improved after the packet loading
time is set.
The packet loading time affects the
number of frames of E1 signals in
each packet.
Recommendations:
The value of the packet loading time
ranges from 125 to 5000 in steps of
125.
parameters:
The packet loading time is closely
related to the jitter compensation
buffering time. The jitter
compensation buffering time is
suggested to be greater than double
packet loading time.
If the PW is bound with services,
Packet Loading Time cannot be
changed.
Ingress Clock Mode - Specifies the clock mode for the
ingress PW of the CES service.
NOTE
This parameter is inapplicable to PWs.
Egress Clock Mode - Specifies the clock mode for the
egress PW of the CES service.
NOTE
This parameter is inapplicable to PWs.
Enabled, Disabled
Default value:
Disabled
Specifies whether the alarm
information of the CES service can
be transparently transmitted.
If this function is enabled, the fault
on the AC side of the CES service is
notified to the remote end. On
receiving the fault notification from
the network side or the remote end,
the local NE inserts the
corresponding alarm on the AC side.
Transmission System
656
Threshold of Entering R bit
Inserting Status
1 to 65535
Default value: 100
Specifies the threshold of entering R
bit inserting status.
If the alarm information of the CES
service is transparently transmitted
and the number of consecutive lost
packets crosses the threshold, the
logic inserts the R bit to the network
side and reports the corresponding
alarm.
Threshold of Exiting R bit
Inserting Status
1 to 65535
Default value: 5
Specifies the threshold of exiting R
bit inserting status.
If the number of consecutive lost
packets crosses the threshold, the
logic quits inserting the R bit to the
network side and reporting the
corresponding alarm.
Sequence Number Mode Huawei Mode,
Standard Mode
Specifies the sequence number
mode.
The Sequence Number Mode must
be set to the same value at both ends
of a radio link.
Control Chanel Type None, CW, Alert Label
Default value: CW
Specifies the mode of PW
connectivity check.
l The value None indicates that the
control word is not supported.
That is, the PW connectivity
check is not supported.
l The value CW indicates that the
control word is supported.
l The value Alert Label Indicates
VCCV packets in Alert Label
encapsulation mode.
parameters:
If Control Word of the PW is Not
in use, do not set Control Channel
Type of the VCCV to CW; if
Control Channel Type of the
VCCV is CW, do not modify
Control Word of the PW to Not in
use.
Transmission System
657
Default value: None
Specifies the VCCV verification
mode. The VCCV verification is
used for PW connectivity check.
If the VCCV Ping test is required, set
this parameter to Ping.

Table A-47 Parameters for the protection group in slave protection pair mode
Protection Mode Slave Protection Pair Displays Protection Mode as Slave
Protection Pair.
Protection Group ID For example, 1 Specifies the ID of the protection
group by selecting a resource. The
protection group ID needs to be
manually specified.
Working PW ID For example, 10 Displays the ID of the working PW.
After Protection Group ID is set, the
ID of the working PW is
automatically assigned here.
Protection PW ID For example, 20 Displays the ID of the protection PW.
After Protection Group ID is set, the
ID of the protection PW is
automatically assigned here.

Table A-48 Parameters for the protection group in PW APS mode
Protection Type PW APS Displays Protection Type as PW
APS.
Protection Group ID For example, 1 Specifies the ID of the protection
group by selecting a resource. The
protection group ID needs to be
manually specified.
Enabling Status Disabled, Enabled
Default value:
Disabled
Specifies whether the protection
group is enabled or disabled.
Transmission System
658
Protection Mode 1:1, 1+1
Default value: 1:1
NOTE
The OptiX OSN
equipment supports
only 1:1.
The Protection Mode parameter
specifies the protection type of a PW
APS protection group.
Value description:
l 1+1: The service is dually
transmitted to the working and
protection channels at the
transmit end and selectively
received at the receive end.
l 1:1: The service is transmitted to
the working or protection channel
and is received from the working
or protection channel based on the
status of the protection group.
Recommendations:
When you create a protection group
in 1:1 protection mode, the protection
channel cannot be configured with
extra services. For this reason, the
actual applications of 1+1 and 1:1
protection groups are the same,
except for the configuration.
Working PW ID - Displays the ID of the working PW.
This parameter cannot be set if
Protection Type is set to PW APS.
Protection PW ID - Displays the ID of the protection PW.
This parameter cannot be set if
Protection Type is set to PW APS.
Switchover Mode Single-ended
switching, Dual-ended
switching
Displays the switching status of a
protection group.
Restoration Mode Non-Revertive,
Revertive
Displays the restoration mode of the
PW APS protection group.
Switchover Restoration
Time(min)
1 to 12
Default value: 1
Specifies the switchover restoration
time.
Switchover Delay Time
(100ms)
0 to 100
Default value: 0
Specifies the switchover delay time.

Transmission System
659
Table A-49 Parameters for PW OAM in PW APS mode
OAM Status Disabled, Enabled Specifies the status of PW OAM.
l Enabled: The PW OAM can be
performed.
l Disabled: The PW OAM cannot
be performed.
Detection Mode Auto-Sending, Manual
Default: Auto-Sending
Displays or specifies the detection
mode. This parameter can be set only
for the tunnel in Egress direction.
l Manual: The connectivity check
(CC) packets are sent at the
interval specified by the user.
l Auto-Sending: The connectivity
check (CC) packets are sent at the
interval of packet receiving.
Detection Packet Type CV, FFD
Default: CV
Specifies the type of the detection
packet.
l CV: The detection packets are
sent at a fixed interval.
l FFD: The detection packets are
sent at the interval specified by
the user.
Detection Packet Period
(ms)
3.3, 10, 20, 50, 100,
200, 500
Displays or specifies the detection
packet period.
If Detection Packet Type is FFD,
this parameter can be set; if
Detection Packet Type is CV, the
value is always 1000.
LSR ID to Be Received For example, 130.0.0.1 Specifies the LSR ID to be received.
Transmitted PW ID For example, 1 Specifies the transmitted PW ID.

A.10 Parameters for Configuring CES Services (in End-to-
End Mode)
This section describes the parameters for configuring CES services in end-to-end mode.
Transmission System
660
Service Template
NOTE
affected.
DEFAULT_PWE3_CES_P
TN,
DEFAULT_PWE3_ETH_P
TN,
DEFAULT_PWE3_ATM_P
TN
NOTE
l Only the service template
DEFAULT_PWE3_CES_
PTN can be used for
configuring CES services.
l The OptiX OSN equipment
does not support the
following service
templates:
l DEFAULT_PWE3_A
TM_ROUTER
l DEFAULT_PWE3_C
ES_ROUTER
l DEFAULT_PWE3_E
TH_ROUTER
l DEFAULT_PWE3_I
WF_ROUTER
l DEFAULT_PWE3_IP
_ROUTER
Service Type varies with
Service Template.
Service Template improves
service configuration
efficiency.
NOTE
displayed, saying "After the
parameters not contained in the
new template may be lost. Are
you sure to continue?" You can
also select Apply the template
data to the configured
Objects.
Service Type ETH, CES
NOTE
configuration. When the
PWE3 Ethernet services,
Service Type is set to ETH.
When the equipment is
configured with PWE3 CES
CES. In this task of configuring
PWE3 CES services, set this
parameter to CES.
enter it.
Default value: Auto-Assign
Specifies the ID of each
PWE3 service, which is
unique on the entire network.
Service Name For example, E-Line-1
NOTE
Transmission System
661
Default value: No Protection
mode of the PW.
only when Mode is UNI-
NNI.
Description For example, E-Line-1
NOTE
belongs.
service remarks.
ID For example, 1 Displays and specifies the ID
of the service access port.

role of a PW.
source NE of a PW.
sink NE of a PW.
enter it.
For example, 35
identifier of a PW.
Transmission System
662
Signaling Type to
Dynamic, the system
egress label.
when entering a PW.
Type to Dynamic,
Forward Label is
manually.
Label can be
specified manually.
when leaving a PW.
Type to Dynamic,
Reverse Label is
manually.
Label can be
specified manually.
tunnel.
Transmission System
663
NOTE
tunnel.
NOTE
NOTE

PW.
Transmission System
664
PW Type l Ethernet
Default: Ethernet
to packets.
PW Type to Ethernet
Ethernet.
Transmission System
665
l CES services: Use
required
and Use required
Default:
in use
l CES services: Use
required
l ATM services: Use
required
NOTE
Use required.
The Control Word
stuffing bits.
Value description:
used.
recommended.
be used.
parameters:
set Control Channel
Type of the VCCV to
Type of the VCCV is
CW, do not modify
to Not in use.
changed.
NOTE
two ends of the PW.
Transmission System
666
Default: CW
NOTE
PCXLG/PCXGA/PCXGB
Label.
PCXLG/PCXGA/PCXGB
Label.
VCCV packets.
VCCV packets are
Value description:
indicate the VCCV
control channel
information.
indicate the VCCV
control channel
information.
Label encapsulation
mode.
parameters:
set Control Channel
Type of the VCCV to
Type of the VCCV is
CW, do not modify
to Not in use.
changed.
Transmission System
667
Default: Ping
(VCCV) packets.
Value description:
VCCV function is
disabled.
ping mode.
parameters:
value is changed.
Transmission System
668
The Request VLAN
request VLAN.
when before PW
the dynamic PW, the
add the VLAN tag.
Recommendations:
parameters:
Tagged Mode.
Before changing the

A.11 Parameter Description: ATM Services
This topic describes the parameters related to ATM services.
A.11.1 Service Class Mapping Table
This topic describes the parameters for a service class mapping table of ATM services.
Transmission System
669
Table A-53 Parameters for a service class mapping table
Mapping Relation ID 2-8
Default value: 2
Displays or specifies the ID of a
mapping table.
Mapping Relation Name - Displays or specifies the name of a
mapping table.
UBR BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33,
AF41, AF42, AF43, EF, CS6, CS7
Default value: BE
Displays or specifies the service
class of UBR.
l Eight PHB service classes are
available: BE, AF1, AF2, AF3,
AF4, EF, CS6, and CS7. The
OptiX OSN equipment provides
different QoS policies for the
queues of different service
classes.
l CS6-CS7: indicate the highest
service classes, mainly for
signaling transmission.
l EF: indicates expedited
forwarding, applicable to
services of a low transmission
delay and low packet loss ratio,
such as voice and video services.
l AF1-AF4: indicate assured
forwarding, applicable to
services that require an assured
rate but no delay or jitter limit.
l BE: indicates that the traffic is
forwarded in best-effort manner
without special processing.
NOTE
The AF1 class includes three
subclasses: AF11, AF12, and AF13.
Only one of these subclasses can
take effect for one queue. It is the
same case with AF2, AF3, and AF4.
Each AF class has three different
discarding priorities (indicated by
different colors). For AF1,
l AF11: green. Traffic of a green
priority can pass.
l AF12: yellow. Traffic of a
yellow priority is discarded as
required when congestion
occurs.
l AF13: red. Traffic of a red
priority is discarded first.
Transmission System
670
CBR BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33,
Default value: EF
class of CBR.
RT-VBR BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33,
Default value: AF31
class of RT-VBR.
NRT-VBR BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33,
Default value: AF21
class of NRT-VBR.
UBR+ BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33,
Default value: AF11
class of UBR+.
PORT-RRANS BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33,
Default value: BE
class of PORT-RRANS.

A.11.2 Policy Management
This topic describes the parameters for policy management of ATM services.
Table A-54 Parameters for policy management
Policy ID Example: 1 Specifies the policy ID of the
ATM service. The policy ID
can also be automatically
allocated.
Policy Name Synchronous signal,
Signaling, Voice, Data,
Video
Default value: Synchronous
signal
Specifies the policy name of
the ATM service. The
maximum length of the value
is 64 bytes.
NOTE
You can select one of the five
ATM service policy names
from the drop-down list or enter
the policy name.
Transmission System
671
Service Type UBR, CBR, RT-VBR, NRT-
VBR, UBR+
Default value: UBR
Specifies the type of the
ATM service.
l The UBR service is
characterized by non-
real-time applications and
many bursts. The UBR
service does not specify
traffic-related service
guarantees. To be
specific, the UBR service
only requires that the
network side provides the
service with the best
effort. The network side
does not provide any
assured QoS for the UBR
service. In the case of
network congestion, the
UBR cells are discarded
first.
l The CBR service requires
tightly constrained delay
variation and requires that
data be transmitted at a
constant rate. In addition,
the CBR service requests
a static amount of
bandwidth and the
highest priority. The CBR
service is characterized
by stable traffic and few
bursts.
l The rt-VBR service
requires tightly
constrained delay and
delay variation.
Compared with the CBR
service, the rt-VBR
service allows sources to
transmit data at a rate that
varies with time.
Equivalently, the sources
can be described as
bursty. In addition, the rt-
VBR service does not
require a static amount of
bandwidth.
Transmission System
672
l Compared with the rt-
VBR service, the nrt-
VBR service does not
require tightly
constrained delay or delay
variation, and is intended
for non-real-time
applications.
l The UBR+ service is
supplementary to the
UBR service and is
intended for applications
that require assured
minimum cell rate, which
is indicated by the
minimum cell rate (MCR)
parameter. The other
characteristics of the
UBR+ service are the
same as the
corresponding
characteristics of the
UBR service.
Traffic Type - For the mapping
relationships between ATM
service types, ATM traffic
type descriptors, and traffic
parameters, see Table A-55.
ATM policies are configured
based on these mapping
relationships.
Clp01Pcr(cell/s) 90 to 74539
Clp01Scr(cell/s) 90 to 74539
Clp0Pcr(cell/s) 90 to 74539
Clp0Scr(cell/s) 90 to 74539
Max. Cell Burst Size (cell) 2 to 200000
Cell Delay Variation
Tolerance (0.1us)
7 to 13300000
Discard Traffic Frame Enabled, Disabled
Specifies the frame
discarding mark in ATM
policies. This parameter is
effective to AAL5 traffic.
Transmission System
673
UPC/NPC Enabled, Disabled
l UPC is user-side
parameter control and
NPC is network-side
parameter control.
l After UPC/NPC is
enabled, the cells with a
frame discarding mark
will be discarded in
network congestion.

Table A-55 Mapping relationship between ATM service types, ATM traffic types, and traffic parameters
ATM
Service
Type
ATM Traffic Type
Descriptor
Traffic
Parameter 1
Traffic
Parameter 2
Traffic
Parameter 3
Traffic
Parameter 4
UBR NoTrafficDescriptor - - - -
NoClpTaggingNoScr Clp01Pcr CDVT - -
NoClpNoScr Clp01Pcr - - -
NoClpNoScrCdvt Clp01Pcr CDVT - -
CBR ClpTransparentNoScr Clp01Pcr CDVT - -
ClpNoTaggingNoScr Clp01Pcr Clp0Pcr - -
ClpTaggingNoScr Clp01Pcr Clp0Pcr - -
NoClpNoScr Clp01Pcr - - -
NoClpNoScrCdvt Clp01Pcr CDVT - -
nrtVBR NoClpScr Clp01Pcr Clp01Scr MBS -
ClpNoTaggingScr Clp01Pcr Clp0Scr MBS -
ClpTaggingScr Clp01Pcr Clp0Scr MBS -
rtVBR ClpTransparentScr Clp01Pcr Clp01Scr MBS CDVT
NoClpScrCdvt Clp01Pcr Clp01Scr MBS CDVT
ClpNoTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
ClpTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
UBR+ atmnotrafficdescriptormcr Clp01Mcr - - -
atmnoclpmcr Clp01Pcr Clp01Mcr - -
atmnoclpmcrcdvt Clp01Pcr Clp01Mcr CDVT -
Transmission System
674

A.11.3 Service Management
This topic describes the parameters for the main interface, connection, port attributes, PW, and
CoS mapping of ATM services.
Table A-56 Main interface parameters
Service ID 1 to 4294967295 Specifies the service ID.
If Auto-Assign is selected, the
system automatically allocates
service IDs.
Service Name - Specifies the service name.
Service Type UNIs-NNI, UNI-UNI
Default value: UNIs-NNI
Specifies the type of the ATM
service.
l UNIs-NNI: This value applies to
ATM PWE3 services. The
attributes in Connection, PW,
and CoS Mapping need to be
configured.
l UNI-UNI: This value applies to
common ATM services. Only
the attributes in Connection
need to be configured.
Transmission System
675
Connection Type PVC, PVP
Default value:
l UNIs-NNI: PVC
l UNI-UNI: PVC
Specifies the connection type of the
ATM service.
For common ATM services (UNI-
UNI):
l PVP: Only the VPIs of the
source and sink are exchanged.
l PVC: The VPIs and VCIs of the
source and sink are exchanged.
For ATM PWE3 services (UNIs-
NNI):
l PVP: This value applies to the
N-to-1/1-to-1 VPC
encapsulation mode. It is
recommended that you set the
VPIs to the same value on the
two ends of the ATM
connection.
l PVC: This value applies to the
N-to-1/1-to-1 VCC
encapsulation mode. It is
recommended that you set the
VPIs/VCIs to the same value on
the two ends of the ATM
connection.
Default value: No Protection
Specifies the protection mode of the
PW.
l Specifies the protection mode of
the PW. This parameter is
available only when Service
Type is UNIs-NNI.
l Set this parameter according to
the planning information.
Auto-Assign Selected, Not selected
Default value: Not selected
Specifies whether to automatically
allocate service IDs.

Table A-57 Connection parameters
Connection Name - Specifies the name of the ATM
connection.
Transmission System
676
Source Board - Specifies the source board of the
ATM service.
Source Port - Specifies the source port of the
ATM service.
Source VPI(eg.35,36-39) UNI: 0 to 255, NNI: 0 to 4095 Specifies the VPI of the source port
of the ATM service.
Source VCI(eg.35,36-39) 32 to 4095 Specifies the VCI of the source port
of the ATM service.
PW ID 1 to 4294967295 Specifies the ID of the PW that
carries services.
Sink Board - Specifies the sink board of the ATM
service.
NOTE
This parameter does not need to be set
if Service Type is UNIs-NNI. This
parameter needs to be set if Service
Type is UNI-UNI and the value must
be different from that of the source
board.
Sink Port - Specifies the sink board of the ATM
service.
NOTE
This parameter does not need to be set
if Service Type is UNIs-NNI. This
parameter needs to be set if Service
Type is UNI-UNI and the value must
be different from that of the source port.
Sink VPI(eg.35,36-39) 1 to 4095 Specifies the VPI of the sink port of
the ATM service.
Sink VCI(eg.35,36-39) 1 to 4095 Specifies the VCI of the sink port of
the ATM service.
Uplink Policy - Specifies the QoS policy of the
uplink ATM connection.
Down link Policy - Specifies the QoS policy of the
downlink ATM connection.

PW ID - Specifies the ID of the PW that
carries services.
Transmission System
677
Working Status - Displays the working status of the
PW.
NOTE
This parameter is available only after
the PW parameters are configured.
Enable Status - Displays the enabling status of the
PW.
NOTE
This parameter is available only after
the PW parameters are configured.
PW Signaling Type Static Labels for static PWs need to be
manually assigned.
PW Type The ATM connection type is PVC:
l ATM n to one VCC cell transport
l ATM one-to-one VCC Cell
Mode
The ATM connection type is PVP:
l ATM n to one VPC cell transport
l ATM one-to-one VPC Cell
Mode
Specifies the type of the PW.
l In the case of ATM 1_to_1
encapsulation, one PW carries
one VPC or VCC.
l In the case of ATM n_to_1
encapsulation, one PW carries
one or more VPCs or VCCs.
Direction Bidirectional Displays the direction of the PW.
PW Encapsulation Type MPLS Displays the encapsulation type of
the packets on the PW.
PW Ingress Label / Source Port 16 to 1048575 Specifies the PW Ingress label.
PW Egress Label / Sink Port 16 to 1048575 Specifies the PW Egress label.
Tunnel Selection Mode Manually Displays the method to select
tunnels.
Tunnel Type MPLS Displays the type of the tunnel that
carries the PW.
Tunnel - A tunnel needs to be selected. If no
tunnel is available, creation of a PW
will fail.
Opposite LSR ID - Specifies the LSR ID of the PW at
the remote end. If an existing tunnel
is selected, the LSR ID will be

Transmission System
678
Table A-59 QoS parameters
Bandwidth Limit Enable, Disable
bandwidth limit is enabled.
l This function can be used
to limit the bandwidth of
one or more PWs, or the
bandwidth of one or more
ATM PWE3 services, in
an MPLS tunnel. (One
ATM PWE3 service
corresponds to one PW.)
l An ATM PWE3 service
corresponds to a PW.
Therefore, this function
can also limit the
bandwidth of ATM
PWE3 services in an
MPLS tunnel.
Policy - The OptiX OSN equipment
does not support this
parameter.
CIR (Kbit/s) - Specifies the committed
information rate (CIR) of the
PW.
It is recommended that you
set this parameter to the same
value as PIR.
CBS (kbyte) - Specifies the excess burst
size of the PW.
set this parameter to 0.
PIR (kbit/s) - Specifies the peak
information rate (PIR) of the
PW.
set this parameter to the same
value as CIR.
PBS (kbyte) - Specifies the maximum
excess burst size of the PW.
set this parameter to 0.

Transmission System
679
Table A-60 Parameters of Advanced Attributes
Control Word Use required, Not in use
Default value: Use required
NOTE
In ATM ONE-to-ONE mode, Control
Word must be set to Use required.
Specifies whether to use the control
word. In the MPLS packet switching
network, the control word is used to
transmit packet information.
parameters:
l If Control Word of the PW is
Not in use, do not set Control
Channel Type of the VCCV to
CW; if Control Channel Type
of the VCCV is CW, do not
modify Control Word of the
PW to Not in use.
l Before changing the parameter
value of a PW, you need to
ensure that the PW is not bound
with the service. After the
change, you need to bind the PW
with the service, and then check
whether the parameter value is
changed.
Transmission System
680
Control Channel Type CW, None, Alert Label
Default value: CW
l Specifies the mode of PW
connectivity check.
l The value None indicates that
supported. That is, the PW
connectivity check is not
supported.
l The value CW indicates that the
control word is supported.
l The value Alert Label indicates
VCCV packets in Alert Label
encapsulation mode.
parameters:
l If Control Word of the PW is
Not in use, do not set Control
Channel Type of the VCCV to
CW; if Control Channel Type
of the VCCV is CW, do not
modify Control Word of the
PW to Not in use.
l Before changing the parameter
value of a PW, you need to
ensure that the PW is not bound
with the service. After the
change, you need to bind the PW
with the service, and then check
whether the parameter value is
changed.
VCCV Verification Mode Ping, None
Default value: Ping
l Specifies the VCCV verification
mode. The VCCV verification is
used for PW connectivity check.
l If the VCCV-Ping test is
required, set this parameter to
Ping.
Max. Concatenated Cell Count 1-31
Default value: 10
l Specifies the maximum number
of concatenated cells.
l If the value 1 is assumed, only
one ATM cell is encapsulated in
one packet. If the value from 2 to
31 is assumed, a maximum of 2
to 31 ATM cells are
encapsulated into one packet.
Transmission System
681
Packet Loading Time (us) 100-50000
Default value: 1000
l Specifies the packet loading
time. Once the packet loading
time expires, the packet is sent
out even if the concatenated cells
are less than the maximum.
l If Max. Concatenated Cell
Count assumes the value 1, this
parameter is ineffective. That is,
the packet will be sent out once
the cell is loaded.

A.12 Parameters for Configuring IMA Services (on a Per-NE
Basis)
This section describes the parameters for configuring IMA services on a per-NE basis.
A.12.1 Bound Path
This topic describes the parameters for bound paths of IMA services.
Table A-61 Parameters for bound paths
Available Boards For example, 4-MD1 Displays or specifies the
configurable board.
Configurable Port For example, 4-MD1-1
(Port-1)
configurable port.
VCTRUNK For example, 4-MD1-1
(Port-1)
Displays the VCTRUNK.
Transmission System
682
Level E1, Fractional E1
Default value: E1
Displays the level of bound
paths.
l If ATM/IMA services
need to be mapped into an
ATM trunk that binds to
one or more E1 ports for
transmission, select E1 in
Level.
l If ATM/IMA services
need to be mapped into an
ATM trunk that binds to
one or more SP ports for
transmission, select
Fractional E1 in Level.
Direction For example, Bidirectional Displays the direction of
bound paths. The value is
always Bidirectional.
Optical Interface -
NOTE
Available Resources For example, 4-MD1-1
(PORT-1)
Displays the ports available
for configuring bound paths
of the IMA service.
Ports on a service board can
function as Available
Resources when their Port
Mode is set to Layer 2.
Available Timeslots -
NOTE
Bound Path For example, 4-MD1-(1) Displays the bound path.
Number of Bound Paths For example, 4 Displays the number of
bound paths for the IMA
service.
NOTE
Here, the number of bound
bidirectional paths is displayed.
For example, the number of
bound paths is 4 when two E1
ports are bound.
Display in Combination Selected, deselected
Default value: selected
Displays whether the bound
IMA paths are displayed in
combination.

Transmission System
683
A.12.2 IMA Group Management
This topic describes the parameters for IMA group management.
Table A-62 Parameters for IMA group management
VCTRUNK For example, 4-MD1-1
(Port-1)
Displays the VCTRUNK.
IMA Protocol Enable Status Enabled, Disabled
Specifies the IMA protocol
status.
Minimum Number of Active
Transmitting Links
1-16
Default value: 1
You need to set this
parameter for each IMA
group. An IMA group can be
activated only when the
number of activated links in
the IMA group reaches the
value of this parameter.
Minimum Number of Active
Receiving Links
1-16
Default value: 1
You need to set this
parameter for each IMA
group. An IMA group can be
activated when the number of
activated links in the IMA
group reaches the value of
this parameter.
IMA Protocol Version 1.0, 1.1
Default value: 1.1
Specifies the IMA protocol
version.
NOTE
The IMA protocol version at the
local end needs to be the same
as that at the peer end.
IMA Transmit Frame Length 32, 64, 128, 256
Default value: 128
Specifies the IMA transmit
frame length.
In order for the receive end to
rebuild the ATM cell stream
from diversely-delayed links,
the transmit end periodically
sends ICP cells on each link.
The number of ATM cells
between each two ICP cells is
the IMA transmit frame
length.
Transmission System
684
IMA Symmetry Mode Symmetrical Mode and
Symmetrical Operation,
Symmetrical Mode and
Asymmetrical Operation,
Asymmetrical Mode and
Asymmetrical Operation
Default value: Symmetrical
Mode and Symmetrical
Operation
Specifies the configuration
and running modes of the
links in an IMA group.
Symmetrical Operation:
Each link in an IMA group is
configured with capabilities
in both the Tx and Rx
directions (symmetrical
configuration). In addition,
when one direction of a link
is interrupted, the other
direction of the link is also
interrupted (symmetrical
operation).
Asymmetrical Operation:
in both the Tx and Rx
directions (symmetrical
direction of the link can still
work (asymmetrical
operation).
Asymmetrical Mode and
Asymmetrical Operation:
in either the Tx or Rx
direction (asymmetrical
direction of the link can still
work (asymmetrical
operation).
NOTE
supports only Symmetrical
Mode and Symmetrical
Operation.
Maximum Delay Between
Links(ms)
1-120
Default value: 25
Specifies the maximum delay
between links in an IMA
group.
Transmission System
685
Clock Mode CTC Mode, ITC Mode
Default value: CTC Mode
Specifies the clock mode of
an IMA group.
l CTC Mode: common
transmit clock (CTC)
mode. In this mode, the
transmit clocks of all links
in an IMA group come
from the same clock
source.
l ITC Mode: independent
transmit clock (ITC)
mode. In this mode, the
transmit clocks of
different links in an IMA
group come from
different clock sources.

A.12.3 Status of an IMA Group
During configuration of IMA services, set parameters that are used for configuring the status of
an IMA group according to service requirements.
Table A-63 Parameters that are used for configuring the status of an IMA group
VCTRUNK Example: 4-MD1-1(Trunk-1) Display the VCTRUNK.
Transmission System
686
Near-End Group Status Not Configured, Start-Up, Start-Up-
ACK, Config-Aborted, Insufficient-
Links, Blocked, Operational
Display the near-end group status.
l Not Configured: The group
does not exist.
l Start-Up: This end is in the
Start-Up status and is waiting to
be indicated that the far-end is
also in the Start-Up status.
l Start-Up-ACK: This is a
transitional state. When both the
near-end and far-end groups
start-up, they move to this state.
l Config-Aborted: This state is
entered when the far-end tries to
apply unacceptable
configuration parameters.
l Insufficient-Links: This state
implies that the group has
accepted the far-end group
parameters and has been
indicated that the far-end has
also accepted its own group
parameters, and does not have
sufficient links to move into the
Operational state.
l Blocked: The group is blocked
(for example, inhibited by the
UM). The group can be blocked
for maintenance purposes while
sufficient links are Active in both
transmitting and receiving
directions.
l Operational: The group is not
inhibited and has sufficient links
in both transmitting and
Far-End Group Status Not Configured, Start-Up, Start-Up-
ACK, Config-Aborted, Insufficient-
Links, Blocked, Operational
Display the Far-end group status.
Transmit Rate (cell/s) For example: 1000 Display the transmit rate.
Receive Rate (cell/s) For example: 1000 Display the receive rate.
Number of Transmit Links 1 to 16 Display the number of transmit
links.
Number of Receive Links 1 to 16 Display the number of receive links.
Transmission System
687
Number of Activated Transmit
Links
1 to 16 Display the number of activated
transmit links.
Number of Activated Receive Links 1 to 16 Display the number of activated
receive links.

A.12.4 Status of an IMA Link
During configuration of IMA services, set parameters that are used for configuring the status of
an IMA link according to service requirements.
Table A-64 Parameters that are used for configuring the status of an IMA link
VCTRUNK For example, 4-MD1-1(Trunk-1) Displays the VCTRUNK.
E1 Link For example, 4-MD1-1(PORT-1)-1 Displays the E1 link information.
Differential Delay Check Status Unknown, Valid, Invalid Queries the delay state of the IMA
link.
Near-End Receiving Status Not In Group, Unusable, Usable,
Active
Displays the near-end receiving
status.
l Not In Group: The link is not
included in the IMA group.
l Unusable: The link is added to
the IMA group but is unavailable
due to a fault or manual
suppression.
l Usable: The link for receiving
ATM signals is configured and
waiting for the transmit end of
FE services to be available or
activated.
l Active: The link is transmitting
services.
Transmission System
688
Near-End Transmitting Status Not In Group, Unusable, Usable,
Active
Displays the near-end transmitting
status.
configured.
l Unusable: The link is
configured, but not in use
because of fault, inhibition, and
so on.
l Usable: The link is ready to bear
services, but waiting for the
other end to be Usable or Active.
l Active: The link is bearing
services.
Far-End Receiving Status Not In Group, Unusable, Usable,
Active
Displays the far-end receiving
status.
configured.
so on.
services.
Far-End Transmitting Status Not In Group, Unusable, Usable,
Active
Displays the far-end transmitting
status.
configured.
so on.
services.

Transmission System
689
A.12.5 Port Management
During configuration of IMA services, set parameters that are used for configuring port
management according to service requirements.
Table A-65 Parameters that are used for configuring port management
Port For example, 4-MD1-1(Port-1) Displays a port.
Name For example, Port1 Specifies the name of a self-defined
port.
Port Type UNI, NNI
Default value: UNI
Specifies the type of cells processed
by an ATM port on the access side.
The parameter value for an ATM
port must be consistent with that for
the peer.
UNI: indicates that a UNI ATM cell
(with the GFC field in the header) is
received through IMA.
NNI: indicates that an NNI ATM
cell (with no GFC field in the
header) is received through IMA.
ATM Cell Payload Scrambling Disabled, Enabled
Determines whether to enable
scrambling of the 48-byte payload in
an ATM cell to improve security.
Recommended value: Enabled
Loopback Non-Loopback, Outloop, Inloop
Specifies a loopback state for a port.

A.13 Parameter Description: Parameters for Configuring
ATM/IMA Services (in End-to-End Mode)
This section describes the parameters that are used for configuring ATM/IMA services in end-
to-end mode.
Transmission System
690
Field Valid Value Description
Service Template
NOTE
affected.
DEFAULT_PWE3_CES_P
TN,
DEFAULT_PWE3_ETH_P
TN,
DEFAULT_PWE3_ATM_P
TN
NOTE
l Only
DEFAULT_PWE3_ATM_
PTN is valid for ATM
services.
l The OptiX OSN equipment
does not support the
following service
templates:
l DEFAULT_PWE3_A
TM_ROUTER
l DEFAULT_PWE3_C
ES_ROUTER
l DEFAULT_PWE3_E
TH_ROUTER
l DEFAULT_PWE3_I
WF_ROUTER
l DEFAULT_PWE3_IP
_ROUTER
Service Type depends on
Service Template.
Configuring services using a
service templates improves
the configuration efficiency.
NOTE
displayed, saying "After the
parameters not contained in the
new template may be lost. Are
you sure to continue?" You can
also select Apply the template
data to the configured
Objects.
Service Type ETH, CES, ATM
NOTE
configuration. To configure
PWE3 ETH services, set this
parameter to ETH; to configure
PWE3 CES services, set it to
CES; to configure PWE3 ATM
services, set it to ATM. In this
task of configuring ATM
services, set it to ATM.
PWE3 service type.
enter it.
Default: Auto-Assign
Specifies the PWE3 service
ID, which is unique on the
entire network.
Service Name For example: E-Line-1
NOTE
PWE3 service name.
Transmission System
691
Field Valid Value Description
Protection Type Protection-Free, PW APS
Default: Protection-Free
scheme of the PW.
This parameter is valid only
when Mode is UNI-NNI.
Description For example: E-Line-1
NOTE
belongs.
remarks.
Transport, ATM 1-to-1 VCC
Cell Transport, ATM N-to-1
VPC Cell Transport, ATM 1-
to-1 VPC Cell Transport
Default: ATM N-to-1 VCC
Cell Transport
Specifies the type of the
working link.

role of a PW.
source NE of a PW.
sink NE of a PW.
enter it.
For example, 35
identifier of a PW.
Transmission System
692
Signaling Type to
Dynamic, the system
egress label.
when entering a PW.
Type to Dynamic,
Forward Label is
manually.
Label can be
specified manually.
when leaving a PW.
Type to Dynamic,
Reverse Label is
manually.
Label can be
specified manually.
tunnel.
Transmission System
693
NOTE
tunnel.
NOTE
NOTE

PW.
Transmission System
694
PW Type l Ethernet
Default: Ethernet
to packets.
PW Type to Ethernet
Ethernet.
Transmission System
695
l CES services: Use
required
and Use required
Default:
in use
l CES services: Use
required
l ATM services: Use
required
NOTE
Use required.
The Control Word
stuffing bits.
Value description:
used.
recommended.
be used.
parameters:
set Control Channel
Type of the VCCV to
Type of the VCCV is
CW, do not modify
to Not in use.
changed.
NOTE
two ends of the PW.
Transmission System
696
Default: CW
NOTE
PCXLG/PCXGA/PCXGB
Label.
PCXLG/PCXGA/PCXGB
Label.
VCCV packets.
VCCV packets are
Value description:
indicate the VCCV
control channel
information.
indicate the VCCV
control channel
information.
Label encapsulation
mode.
parameters:
set Control Channel
Type of the VCCV to
Type of the VCCV is
CW, do not modify
to Not in use.
changed.
Transmission System
697
Default: Ping
(VCCV) packets.
Value description:
VCCV function is
disabled.
ping mode.
parameters:
value is changed.
Transmission System
698
The Request VLAN
request VLAN.
when before PW
the dynamic PW, the
add the VLAN tag.
Recommendations:
parameters:
Tagged Mode.
Before changing the

A.14 Parameter Description: ATM OAM Management
This section describes the parameters for configuring ATM OAM on a per-NE basis.
A.14.1 Segment and End Attribute
To configure ATM OAM functions, first set parameters for configuring segment and end
attributes.
Transmission System
699
Table A-69 Parameters for configuring segment and end attributes
Source For example, 3-MD1-3
(Trunk-3)-36-37
Displays the source node of an
ATM/IMA service.
Sink For example, PW(ATM n-to-one
VCC cell transport,26)-38-39
Displays the sink node of an ATM/
IMA service.
Connection Direction Source, Sink Displays the direction of an ATM
connection.
l Source: the direction in which an
ATM OAM cell stream enters an
ATM connection.
l Sink: the direction in which an
ATM OAM cell stream leaves an
ATM connection.
Transmission System
700
Segment and End Attribute Non segment and Endpoint,
Segment point, Endpoint, Segment
and Endpoint
Default value: Non segment and
Endpoint
Specifies the segment and end
attributes of the source and sink of
an ATM connection.
l Non segment and endpoint:
intermediate point, which refers
to an OAM node between two
segment points or two end
points. Therefore, intermediate
points can be further classified
into intermediate points between
segment points, and intermediate
points between end points.
Upon detecting a fault, an
intermediate point reports
associated alarms and inserts
segment AIS cells and end
AIS cells in the downstream.
Afterwards, the intermediate
point periodically sends these
cells.
An intermediate point does
not capture any AIS/RDI
cells.
l Segment point: an end point of a
segment. One ATM link consists
of multiple segments.
Upon detecting a fault, a
segment point reports
associated alarms and inserts
end AIS cells in the
downstream. Afterwards, the
segment point periodically
sends these cells.
A segment point captures
segment only AIS/RDI cells.
l End point: an end point of an
ATM link. It is usually an edge
point on the ATM network.
Upon detecting a fault, an end
point reports associated
alarms but does not insert any
AIS cells.
An end point captures only
end AIS/RDI cells.
Transmission System
701
l Segment and endpoint: a
segment-end point, or an edge
point of a segment and an end.
Upon detecting a fault, a
segment-end point reports
associated alarms but does
not insert any AIS cells.
A segment-end point
captures the AIS/RDI cells of
a segment and an end.

A.14.2 CC Activate Flag
To configure ATM OAM functions, first set parameters for configuring CC activate flag.
Table A-70 Parameters for configuring CC activate flag
(Trunk-3)-36-37
ATM/IMA service.
IMA service.
Connection Direction Source, Sink Specifies the connection direction.
ATM connection.
ATM connection.
Segment and End Attribute Segment point, Endpoint Specifies the segment and end
attributes of nodes.
Transmission System
702
CC Activate Flag Deactivate, Source activate, Sink
activate, Source + sink activate
Specifies the CC activation flag.
l Deactivate: A node does not
transmit or receive CC cells.
l Source activate: A node
transmits but does not receive
CC cells.
l Sink activate: A node receives
but does not transmit CC cells. If
the node does not receive any
service cells or CC cells within a
time interval of 3.5 (0.5)
seconds, it will report the LOC
alarm and transmit AIS cells in
the forward direction. Once the
node receives any CC cells or
service cells, the LOC alarm will
be cleared.
l Source + sink activate: A node
transmits and receives CC cells.
If the node does not receive any
service cells or CC cells within a
time interval of 3.5 (0.5)
seconds, it will report the LOC
alarm and transmit AIS cells in
the forward direction. Once the
node receives any CC cells or
service cells, the LOC alarm will
be cleared.

A.14.3 Remote End Loopback Status
This section describes parameters that are related to the remote end loopback status of ATM
OAM.
Table A-71 Parameters on the Main Interface
(Trunk-3)-36-37
ATM/IMA service.
IMA service.
Transmission System
703
Connection Direction Source, Sink Displays the direction of an ATM
connection.
ATM connection.
ATM connection.
Segment and End Attribute Segment point, Endpoint Specifies segment and end
attributes.
Loopback Point NE For example, NE(126-888) Specifies an NE where the loopback
point is located.
l Before an end-to-end LB test, set
end points in the test domain.
After the test, remove the end
points.
l Before a segment-to-segment
LB test, set segment points in the
test domain. After the test,
remove the segment points.
Test Result For example, Test succeed Displays test results.

A.14.4 LLID
This section describes parameters for configuring local loopback IDs (LLIDs).
Table A-72 Parameters for configuring LLIDs
Country Code (Hexadecimal) -
Default value: [2BYTE]00 00
Displays or specifies the country
code of an ATM service. The value
is 2 bytes in length.
Network Code (Hexadecimal) -
Default value: [2BYTE]00 00
Displays or specifies the network
code of an ATM service. The value
is 2 bytes in length.
Transmission System
704
NE Code (Hexadecimal) -
Default value: [11BYTE]00 30 00
0E 00 00 00 00 00 00 00
Displays or specifies the NE code of
an ATM service. The value is 11
bytes in length.
l The default NE code can be used
if it is unique on the network.
l NE codes and NE IDs are
associated. Therefore, each NE
on a network has a unique NE
code.

A.15 Parameter Description: Inband DCN
This topic describes the parameters related to inband DCN.
A.15.1 Port Settings
Configuring in-band DCN bandwidth management focuses on setting of VLAN ID and
Bandwidth (kbps) for a board.
Table A-73 lists parameters for in-band DCN bandwidth management.
Table A-73 Parameters for in-band DCN bandwidth management
Ethernet Board VLANID 2 to 4094
Default value: 4094
Sets the VALN ID used by
the DCN. Set this parameter
when the NMS and NEs are
connected through Ethernet
ports, or NEs are connected
through Ethernet ports.
The default value is
recommended for this
parameter.
Bandwidth(Kbit/s) 64 to 1000
Default value: 512
Sets the bandwidth used by
when the NMS and NEs are
connected through Ethernet
ports, or NEs are connected
through Ethernet ports.
Transmission System
705
E1 Port Bandwidth(Kbit/s) 64 to 2048
Default value: 192
when E1 ports are used to
carry services between NEs.
NOTE
OptiX OSN equipment does not
Tunnel Bandwidth(Kbit/s) 64 to 2048
Default value: 1024
when tunnels are used to
NOTE
IF Port Bandwidth(Kbit/s) 64 to 2048 Sets the bandwidth used by
when radio links are used to
NOTE

A.15.2 Access Control
Configuring the in-band DCN access control function focuses on setting of IP Address and
Subnet Mask for a port.
Table A-74 lists parameters for in-band DCN access control.
Table A-74 Parameters for in-band DCN access control
Port Name For example, 3-EM6F-1
(PORT-1)
Displays Ethernet ports that
can be connected to the
network management system
(NMS).
Transmission System
706
Enabled Status Enabled, Disabled
Enables or disables a port.
l Enabled: Management
information of the
U2000 can be received
and transmitted through
this port.
l Disabled: Management
information of the
U2000 cannot be received
and transmitted through
this port.
IP Address For example, 1.1.1.2 Sets the IP address for a port.
Subnet Mask For example, 255.255.255.0 Sets the subnet mask for a
port.

A.15.3 Bandwidth Management
Configuring an in-band DCN port focuses on setting of Enabled Status.
Table A-75 lists parameters for configuring an in-band DCN port.
Table A-75 Parameters for configuring an in-band DCN port
Port Name For example, 3-EM6F-1
(PORT-1)
Displays ports used for
transmitting management
information between NEs.
Enabled Status Enabled, Disabled
Enables or disables a port.
l Enabled: Management
information between NEs
can be transmitted
through this port.
l Disabled: Management
information between NEs
cannot be transmitted
through this port.

A.15.4 Protocol settings
This section describes the parameters for inband DCN protocol settings.
Table A-76 provides the parameters for inband DCN protocol settings.
Transmission System
707
Table A-76 Parameters for inband DCN protocol settings
Port Name Slot-Board Name-Port(Port
No.)
For example: 3-EM6F-1
(PORT-1)
Displays the Ethernet port
that can access the NMS
information.
Protocol Type IP, HWECC Sets the type of protocol used
by DCN.

A.15.5 Packet Control
This section describes parameters for inband DCN packet control.
Table A-77 provides parameters for inband DCN packet control.
Table A-77 Parameters for inband DCN packet control
Packet Type VLAN, DSCP Displays the DCN packet
type.
Supported Application ALL Sets the packet control range.
Packet Priority BE, AF1, AF2, AF3, AF4,
EF, CS6
Sets the inband DCN packet
priority.
Transmission System
708
B Glossary
Numerics
1+1 backup A backup method in which two components mirror each other. If the active component
goes down, the standby component takes over services from the active component to
ensure that the system service is not interrupted.
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.
3G See 3rd Generation.
3R reshaping, retiming, regenerating
3rd Generation (3G) The third generation of digital wireless technology, as defined by the International
Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to
19.2 kbit/s offered by second generation technology.
A
A/D analog/digit
AAA See Authentication, Authorization and Accounting.
AAL See ATM Adaptation Layer.
AAL2 ATM Adaptation Layer Type 2
AAL5 ATM Adaptation Layer Type 5
ABR See available bit rate.
ACAP See adjacent channel alternate polarization.
ACH associated channel header
ACL See access control list.
ACL rule A rule for controlling the access of users.
ADM add/drop multiplexer
AF See assured forwarding.
Transmission System
Configuration Guide (Packet Transport Domain) B Glossary
709
AGC automatic gain control
AIO asynchronous input/output
AIS alarm indication signal
AIS insertion Insertion of AIS in a channel with excessive errors to indicate that it is unavailable. For
a line board, it can be set whether to insert AIS when there are excessive errors in the
B1, B2 and B3 bytes. For tributary board at the E1/T1 level, it can be set whether to
insert AIS when there are excessive errors in BIP-2. For tributary board at the E3 level
or higher, it can be set whether to insert AIS when there are excessive errors in the B3
byte.
ALS See automatic laser shutdown.
AM See adaptive modulation.
AMI See alternate mark inversion.
ANSI See American National Standards Institute.
APD See avalanche photodiode.
APID access point identifier
APS automatic protection switching
APS 1+1 protection A protection architecture that comprises one protection facility and one working facility
and performs switchover by using the Automatic Protection Switching (APS) protocol.
Normally, signals are sent only over the working facility. If an APS switchover event is
detected by the working facility, services are switched over to the protection facility.
ARP See Address Resolution Protocol.
AS See autonomous system.
ASCII American Standard Code for Information Interchange
ASK amplitude shift keying
ATM asynchronous transfer mode
ATM Adaptation
Layer (AAL)
An interface between higher-layer protocols and Asynchronous Transfer Mode (ATM).
The AAL provides a conversion function to and from ATM for various types of
information, including voice, video, and data.
ATM protection group Logically bound ATM VP network/subnetwork connections that share the same physical
transmission channel. In the VP Group (VPG), a pair of VP connections (working
connection and its protective connection) is used for monitoring the automatic protection
switching, called monitoring connections (APS VPCs). If the monitoring connections
switch over, the whole VPG will switch over to quicken the ATM protection switching
(as quick as the protection switching of the SDH layer).
ATPC See automatic transmit power control.
AU See administrative unit.
AUG See administrative unit group.
AWG arrayed waveguide grating
Transmission System
710
Address Resolution
Protocol (ARP)
An Internet Protocol used to map IP addresses to MAC addresses. The ARP protocol
enables hosts and routers to determine link layer addresses through ARP requests and
responses. The address resolution is a process by which the host converts the target IP
address into a target MAC address before transmitting a frame. The basic function of
ARP is to use the target equipment's IP address to query its MAC address.
American National
Standards Institute
(ANSI)
An organization that defines U.S standards for the information processing industry.
Authentication,
Authorization and
Accounting (AAA)
A mechanism for configuring authentication, authorization, and accounting security
services. Authentication refers to the verification of user identities and the related
network services; authorization refers to the granting of network services to users
according to authentication results; and accounting refers to the tracking of the
consumption of network services by users.
access A link between the customer and the telecommunication network. Many technologies,
such as the copper wire, optical fiber, mobile, microwave and satellite, are used for
access.
access control list
(ACL)
A list of entities, together with their access rights, which are authorized to access a
resource.
access layer A layer that connects the end users (or last mile) to the ISP network. The access layer
devices are cost-effective and have high-density interfaces. In an actual network, the
access layer includes the devices and cables between the access points and the UPEs.
access point Any entity that has station functionality and provides access to the distribution services,
via the wireless medium (WM) for associated stations.
accumulation The sum of the service usage, consumption, and recharge fees of a subscriber.
active link A link in the link aggregation group, which is connected to the active interface.
active mode A working mode of EFM OAM. The discovery and remote loopback can only be initiated
by the interface in the active mode.
adaptive modulation
(AM)
A technology that is used to automatically adjust the modulation mode according to the
channel quality. When the channel quality is favorable, the equipment uses a high-
efficiency modulation mode to improve the transmission efficiency and the spectrum
utilization of the system. When the channel quality is degraded, the equipment uses the
low-efficiency modulation mode to improve the anti-interference capability of the link
that carries high-priority services.
adjacency A portion of the local routing information which pertains to the reachability of a single
neighbor ES or IS over a single circuit. Adjacencies are used as input to the Decision
Process for forming paths through the routing domain. A separate adjacency is created
for each neighbor on a circuit, and for each level of routing (i.e. level 1 and level 2) on
a broadcast circuit.
adjacent channel
alternate polarization
(ACAP)
A channel configuration method, which uses two adjacent channels (a horizontal
polarization wave and a vertical polarization wave) to transmit two signals.
adjacent concatenation A situation where the virtual containers (VC) to carry concatenated services in SDH are
consecutive in terms of their service in the frame structures, so that they use the same
path overhead (POH).
Transmission System
711
administrative unit
(AU)
The information structure that enables adaptation between the higher order path layer
and the multiplex section layer. The administrative unit consists of an information
payload (the higher order VC) and an AU pointer, which indicates the offset of the
payload frame start relative to the multiplex section frame start.
administrative unit
group (AUG)
One or more administrative units occupying fixed, defined positions in an STM payload.
An AUG consists of AU-4s.
advanced ACL An ACL that defines ACL rules based on the source addresses, target addresses, protocol
type, such as TCP source or target port, the type of the ICMP protocol, and message
codes.
aggregated link Multiple signaling link sets between two nodes.
aging time The time to live before an object becomes invalid.
air interface The interface between the cellular phone set or wireless modem (usually portable or
mobile) and the active base station.
alarm A message reported when a fault is detected by a device or by the network management
system during the device polling process. Each alarm corresponds to a clear alarm. After
a clear alarm is received, the corresponding alarm is cleared.
alarm box A device that reflects the status of an alarm in visual-audio mode. The alarm box notifies
you of the alarm generation and alarm severity after it is connected to the Signaling
Network Manager server or client and the related parameters are set.
alarm cascading The method of cascading alarm signals from several subracks or cabinets.
alarm correlation
analysis
A process to analyze correlated alarms. For example, if alarm 2 is generated within five
seconds after alarm 1 is generated, and it complies with the conditions defined in the
alarm correlation analysis rule, you can either mask the alarm or raise the level of alarm
2 according to the behavior defined in the alarm correlation rule.
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 mechanism to indicate the alarm status of equipment. On the cabinet of an NE, four
differently-colored indicators specify the current status of the NE. When the green
indicator is on, the NE is powered on. When the red indicator is on, a critical alarm has
been generated. When the orange indicator is on, a major alarm has been generated.
When the yellow indicator is on, a minor alarm has been generated. The ALM alarm
indicator on the front panel of a board indicates the current status of the board.
alarm inversion mode A mode for an NE that indicates whether the port is automatically restored to the normal
status after the service is accessed or the fault is removed. There are three alarm inversion
modes: normal, revertible and non-revertible.
alarm notification When an error occurs, the performance measurement system sends performance alarms
to the destination (for example, a file and/or fault management system) designated by
users.
alarm suppression A method to suppress alarms for the alarm management purpose. Alarms that are
suppressed are no longer reported from NEs.
alternate mark
inversion (AMI)
A synchronous clock encoding technique which uses bipolar pulses to represent logical
1 values.
Transmission System
712
analog signal A signal in which information is represented with a continuously variable physical
quantity, such as voltage. Because of this constant changing of the wave shape with
regard to its passing a given point in time or space, an analog signal might have a virtually
indefinite number of states or values. This contrasts with a digital signal that is expressed
as a square wave and therefore has a very limited number of discrete states. Analog
signals, with complicated structures and narrow bandwidth, are vulnerable to external
interference.
assured forwarding
(AF)
One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.
It is suitable for certain key data services that require assured bandwidth and short delay.
For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that
exceeds the bandwidth limit, AF degrades the service class and continues to forward the
traffic instead of discarding the packets.
attack An attempt to bypass security controls in a system with the mission of using that system
or compromising it. An attack is usually accomplished by exploiting a current
vulnerability.
attenuation Reduction of signal magnitude or signal loss, usually expressed in decibels.
attenuator A device used to increase the attenuation of an Optical Fiber Link. Generally used to
ensure that the signal at the receive end is not too strong.
automatic laser
shutdown (ALS)
A technique (procedure) to automatically shutdown the output power of laser transmitters
and optical amplifiers to avoid exposure to hazardous levels.
automatic transmit
power control (ATPC)
A method of adjusting the transmit power based on fading of the transmit signal detected
at the receiver
autonomous system
(AS)
A network set that uses the same routing policy and is managed by the same technology
administration department. Each AS has a unique identifier that is an integer ranging
from 1 to 65535. The identifier is assigned by IANA. An AS can be divided into areas.
availability A capability of providing services at any time. The probability of this capability is called
availability.
available bit rate (ABR) A kind of service categories defined by the ATM forum. ABR only provides possible
forwarding service and applies to the connections that does not require the real-time
quality. It does not provide any guarantee in terms of cell loss or delay.
avalanche photodiode
(APD)
A semiconductor photodetector with integral detection and amplification stages.
Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher voltages
than other semiconductor electronics.
average delay A performance indicator indicating the average RTT of multiple ping operations or other
probe operations. It is expressed in milliseconds.
B
B-ISDN See broadband integrated services digital network.
BA booster amplifier
BBE background block error
BC boundary clock
BCD binary coded decimal
Transmission System
713
BDI See backward defect indication.
BDI packet A packet used to notify the upstream LSR of the failure event which has occurred on the
downstream LSR through the reverse LSP. The BDI packet can be used in the 1:1/N
protective switchover service.
BE See best effort.
BER bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIP See bit interleaved parity.
BIP-8 See bit interleaved parity-8.
BIP-X bit interleaved parity-X
BITS See building integrated timing supply.
BMC best master clock
BNC See bayonet-neill-concelman.
BOM bill of materials
BPDU See bridge protocol data unit.
BPS board protection switching
BSC See base station controller.
BSS base station subsystem
BTS base transceiver station
BW See bandwidth.
BWS backbone wavelength division multiplexing system
Bidirectional
Forwarding Detection
(BFD)
A fast and independent hello protocol that delivers millisecond-level link failure
detection and provides carrier-class availability. After sessions are established between
neighboring systems, the systems can periodically send BFD packets to each other. If
one system fails to receive a BFD packet within the negotiated period, the system regards
that the bidirectional link fails and instructs the upper layer protocol to take actions to
recover the faulty link.
backbone network A network that forms the central interconnection for a connected network. The
communication backbone for a country is WAN. The backbone network is an important
architectural element for building enterprise networks. It provides a path for the exchange
of information between different LANs or subnetworks. A backbone can tie together
diverse networks in the same building, in different buildings in a campus environment,
or over wide areas. Generally, the backbone network's capacity is greater than the
networks connected to it.
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 data stored in a database for the purposes of
recovering the data if an error occurs. The backup also refers to the data synchronization
between active and standby boards.
Transmission System
714
backward defect
indication (BDI)
A function that the sink node of a LSP, when detecting a defect, uses to inform the
upstream end of the LSP of a downstream defect along the return path.
bandwidth (BW) A range of transmission frequencies a transmission line or channel can carry in a network.
In fact, the bandwidth is the difference between the highest and lowest frequencies in
the transmission line or channel. The greater the bandwidth, the faster the data transfer
rate.
base station area An area of radio coverage consisting of cells served by one or more Base Transceiver
Stations (BTSs) in the same base station site.
base station controller
(BSC)
A logical entity that connects the BTS with the MSC in a GSM/CDMA network. It
interworks with the BTS through the Abis interface, the MSC through the A interface.
It provides the following functions: radio resource management, base station
management, power control, handover control, and traffic measurement. One BSC
controls and manages one or more BTSs in an actual network.
baseband A form of modulation in which the information is applied directly onto the physical
transmission medium.
bayonet-neill-
concelman (BNC)
A connector used for connecting two coaxial cables.
bearer An information transmission path with defined capacity, delay and bit error rate.
bearer network A network used to carry the messages of a transport-layer protocol between physical
devices.
best effort (BE) A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of the
network and routers. The amount of resource that a diagram can use depends of the time
it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss
ratio, and high reliability.
best-effort service A unitary and simple service model. Without being approved, but after notifying the
network, the application can send any number of packets at any time. The network tries
its best to send the packets, but delay and reliability cannot be ensured. Best-Effort is
the default service model of the Internet. It can be applied to various networks, such as
FTP and E-Mail. It is implemented through the First In First-Out (FIFO) queue.
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
bit interleaved parity
(BIP)
A method of error monitoring. With even parity, the transmitting equipment generates
an X-bit code 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 forth. Even parity is generated by setting
the BIP-X bits so that an even number of 1s exist in each monitored partition of the
signal. A monitored partition comprises all bits 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 interleaved parity-8
(BIP-8)
Consists of a parity byte calculated bit-wise across a large number of bytes in a
transmission transport frame. Divide a frame is into several blocks with 8 bits (one byte)
in a parity unit and then arrange the blocks in matrix. Compute the number of "1" or "0"
over each column. Then fill a 1 in the corresponding bit for the result if the number is
odd, otherwise fill a 0.
Transmission System
715
blacklist A method of filtering packets based on their source IP addresses. Compared with ACL,
the match condition for the black list is much simpler. Therefore, the black list can filter
packets at a higher speed and can effectively screen the packet sent from the specific IP
address.
bound path A parallel path with several serial paths bundled together. It improves the data throughput
capacity.
bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ 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
unit (BPDU)
Data messages exchanged across switches within an extended LAN that uses a spanning
tree protocol (STP) topology. BPDU packets contain information on ports, addresses,
priorities, and costs, and they ensure that the data reaches its intended destination. BPDU
messages are exchanged across bridges to detect loops in a network topology. These
loops are then removed by shutting down selected bridge interfaces and placing
redundant switch ports in a backup, or blocked, state.
bridging The act of simultaneously transmitting identical traffic on the working and protection
channels.
broadband integrated
services digital network
(B-ISDN)
A standard defined by the ITU-T to handle high-bandwidth applications, such as voice.
It currently uses the ATM technology to transmit data over SONNET-based circuits at
155 to 622 Mbit/s or higher speed.
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
broadcast address A network address in computer networking that allows information to be sent to all nodes
on a network, rather than to a specific network host.
broadcast domain A group of network stations that receives broadcast packets originating from any device
within the group. The broadcast domain also refers to the set of ports between which a
device forwards a multicast, broadcast, or unknown destination frame.
building integrated
timing supply (BITS)
In the situation of multiple synchronous nodes or communication devices, one can use
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.
built-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.
burst A process of forming data into a block of the proper size, uninterruptedly sending the
block in a fast operation, waiting for a long time, and preparing for the next fast sending.
C
CAC See connection admission control.
CAR committed access rate
Transmission System
716
CAS multiframe A multiframe set up based on timeslot 16. Each CAS multiframe contains 16 E1 PCM
frames. Among the 8 bits of timeslot 16 in the first frame, the first 4 bits are used for
multiframe synchronization. The multiframe alignment signal (MFAS) for
synchronization is 0000. The last 4 bits are used as the not multiframe alignment signal
(NMFAS). The NMFAS is XYXX. For the other 15 frames, timeslot 16 is used to
transmit exchange and multiplexing (E&M) signaling corresponding to each timeslot.
CBR See constant bit rate.
CBS See committed burst size.
CC See continuity check.
CCDP See co-channel dual polarization.
CCS See Common Channel Signaling.
CDVT cell delay variation tolerance
CE See customer edge.
CES See circuit emulation service.
CFM connectivity fault management
CFR cell fill rate
CIR committed information rate
CIST See Common and Internal Spanning Tree.
CLEI common language equipment identification
CLK clock card
CLNP connectionless network protocol
CLP See cell loss priority.
CMI coded mark inversion
CO central office
CPU See central processing unit.
CR connection request
CRC See cyclic redundancy check.
CRC-4 multiframe A multiframe recommended by ITU-T G.704 and set up based on the first bit of timeslot
0. The CRC-4 multiframe is different from the CAS multiframe in principle and
implementation. Each CRC-4 multiframe contains 16 PCM frames. Each CRC-4
multiframe consists of two CRC-4 sub-multiframes. Each CRC-4 sub-multiframe is a
CRC-4 check block that contains 2048 (256 x 8) bits. Bits C1 to C4 of a check block can
check the previous check block.
CSA Canadian Standards Association
CSES consecutive severely errored second
CSF Client Signal Fail
CSMA/CD See carrier sense multiple access with collision detection.
CST See common spanning tree.
Transmission System
717
CTC common transmit clock
CV connectivity verification
CV packet A type of packet that is generated at the frequency of 1/s on the source end LSR of an
LSP, and is terminated on the destination end LSR of the LSP. A CV packet is transmitted
from the source end LSR to the destination LSR along the LSP. A CV packet contains
the unique identifier (TTSI) of the LSP so that all types of abnormalities on the path can
be detected.
CW control word
CWDM See coarse wavelength division multiplexing.
Common Channel
Signaling (CCS)
A signaling system used in telephone networks that separates signaling information from
user data. A specified channel is exclusively designated to carry signaling information
for all other channels in the system.
Common and Internal
Spanning Tree (CIST)
The single spanning tree jointly calculated by STP and RSTP, the logical connectivity
using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the
bridged local area network are simply and fully connected.
cabinet Free-standing and self-supporting enclosure for housing electrical and/or electronic
equipment. It is usually fitted with doors and/or side panels which may or may not be
removable.
cable distribution plate A component, which is used to arrange cables in order.
cable tie A tie used to bind cables.
carrier An organization that has telecom network resources and can provide communications
service.
carrier sense multiple
access with collision
detection (CSMA/CD)
Carrier sense multiple access with collision detection (CSMA/CD) is a computer
networking access method in which:
l A carrier sensing scheme is used.
l A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
cell loss priority (CLP) A field in the ATM cell header that determines the probability of a cell being dropped
if the network becomes congested. Cells with CLP = 0 are insured traffic, which is
unlikely to be dropped. Cells with CLP = 1 are best-effort traffic, which might be
dropped.
central processing unit
(CPU)
The computational and control unit of a computer. The CPU is the device that interprets
and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
centralized alarm The alarms of all the hosts connecting to the Operation and Maintenance Unit (OMU).
Transmission System
718
channel A telecommunication path of a specific capacity and/or speed between two or more
locations in a network. The channel can be established through wire, radio (microwave),
fiber, or any 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 (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s
(1012 bit/s).
channel spacing The center-to-center difference in frequencies or wavelengths between adjacent channels
in a WDM device.
check criteria A set of rules for checking and analyzing device echo information. The check criteria
for an alarm collection item need to be set through the configuration file.
circuit emulation
service (CES)
A function with which the E1/T1 data can be transmitted through ATM networks. At the
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.
clock selection An algorithm used for selecting the best clock for clock synchronization. For different
peers (multiple servers or peers configured for a client), a peer sends clock
synchronization packets to each server or passive peer. After receiving the response
packets, it uses the clock selection algorithm to select the best clock.
clock source A device that provides standard time for the NTP configuration.
clock synchronization A process of synchronizing clocks, in which the signal frequency traces the reference
frequency, but the start points do not need to be consistent. This process is (also known
as frequency synchronization).
clock tracing The method of keeping the time on each node synchronized with a clock source in the
network.
co-channel dual
polarization (CCDP)
A channel configuration method, which uses a horizontal polarization wave and a vertical
polarization wave to transmit two signals. The Co-Channel Dual Polarization has twice
the transmission capacity of the single polarization.
coarse wavelength
division multiplexing
(CWDM)
A signal transmission technology that multiplexes widely-spaced optical channels into
the same fiber. CWDM spaces wavelengths at a distance of several nm. CWDM does
not support optical amplifiers and is applied in short-distance chain networking.
collision A condition in which two packets are being transmitted over a medium at the same time.
Their interference makes both unintelligible.
committed burst size
(CBS)
A parameter used to define the capacity of token bucket C, that is, the maximum burst
IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of an
IP packet to be forwarded.
common spanning tree
(CST)
A single spanning tree that connects all the MST regions in a network. Every MST region
is considered as a switch; therefore, the CST can be considered as their spanning tree
generated with STP/RSTP.
composite service An aggregation of a series of services relevant to each other.
conference An IP multimedia session that have two or more participants. Each conference has a
focus and can be identified uniquely.
Transmission System
719
congestion Extra intra-network or inter-network traffic resulting in decreased network service
efficiency.
congestion
management
A flow control measure to solve the problem of network resource competition. When
the network congestion occurs, it places packets into the queue for buffer and determines
the packet forwarding order.
connection An association of transmission channels or telecommunication circuits, switching and
other functional units set up to provide for the transfer of signals between two or more
network points, to support a single communication.
connection admission
control (CAC)
A control process in which the network takes actions in the call set-up phase (or call re-
negotiation phase) to determine which connection request is admitted.
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.
connectionless Pertaining to a method of data presentation. The data has a complete destination address
and is delivered by the network on a best-effort basis, independent of other data being
exchanged between the same pair of users.
constant bit rate (CBR) 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.
container A set of hardware or software devices. In software domain, it refers to the environment
variables and processes. In hardware domain, it refers to a type of topology node that
contains nodes, usually refers to one device with multiple frames; each node stands for
a frame.
continuity check (CC) An Ethernet connectivity fault management (CFM) method used to detect the
connectivity between MEPs by having each MEP periodically transmit a Continuity
Check Message (CCM).
control VLAN A VLAN that transmits only protocol packets.
control channel The channel used to transmit digital control information from the base station to a cell
phone or vice-versa.
convergence layer A "bridge" between the access layer and the core layer. The convergence layer provides
the convergence and forwarding functions for the access layer. It processes all the traffic
from the access layer devices, and provides the uplinks to the core layer. Compared with
the access layer, the convergence layer devices should have higher performance, fewer
interfaces and higher switching rate. In the real network, the convergence layer refers to
the network between UPEs and PE-AGGs.
cooling system The system that controls or influences climate by decreasing the air temperature only.
core layer A layer that functions as the backbone of high speed switching for networks and provides
high speed forwarding communications. It has a backbone transmission structure that
provides high reliability, high throughput, and low delay. The core layer devices must
have a good redundancy, error tolerance, manageability, adaptability, and they support
dual-system hot backup or load balancing technologies. In a real network, the core layer
includes the IP/MPLS backbone network consisting of NPEs and backbone routers.
Transmission System
720
correlation The similarities when two random processes vary with time.
corruption The alteration of the information in IMS networks for the purpose of deception. For
example, attackers corrupt the correct charging information to evade being charged.
cross-connection The connection of channels between the tributary board and the line board, or between
line boards inside the NE. Network services are realized through the cross-connections
of NEs.
crossover cable A twisted pair patch cable wired in such a way as to route the transmit signals from one
piece of equipment to the receive signals of another piece of equipment, and vice versa.
crystal oscillator An oscillator that produces electrical oscillations at a frequency determined by the
physical characteristics of a piezoelectric quartz crystal.
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly connecting
to the Service Provider (SP) network. A CE can be a router, switch, or host.
cutover To migrate the data of an application system to another application system, which then
provides services.
cyclic redundancy
check (CRC)
A procedure used to check for errors in data transmission. CRC error checking uses a
complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before performing the transmission and includes the
generated number in the packet it sends to the receiving device. The receiving device
then repeats the same calculation. If both devices obtain the same result, the transmission
is considered to be error free. This procedure is known as a redundancy check because
each transmission includes not only data but extra (redundant) error-checking values.
D
D/A digital-analog converter
DB database
DC direct current
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common
(with ground) (DC-C)
A power system, in which the BGND of the DC return conductor is short-circuited with
the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return isolate (with
ground) (DC-I)
A power system, in which the BGND of the DC return conductor is short-circuited with
the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See data communications channel.
DCE See data circuit-terminating equipment.
DCF data communication function
DCM See dispersion compensation module.
DCN See data communication network.
DDF digital distribution frame
Transmission System
721
DDN See digital data network.
DHCP See Dynamic Host Configuration Protocol.
DLAG See distributed link aggregation group.
DM See delay measurement.
DNI dual node interconnection
DRDB dynamic random database
DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP differentiated services code point
DSL See digital subscriber line.
DSLAM See digital subscriber line access multiplexer.
DSP digital signal processing
DTE See data terminal equipment.
DTR data terminal ready
DVB digital video broadcasting
DVB-ASI digital video broadcast-asynchronous serial interface
DVMRP See Distance Vector Multicast Routing Protocol.
DWDM See dense wavelength division multiplexing.
Distance Vector
Multicast Routing
Protocol (DVMRP)
An Internet gateway protocol based primarily on the RIP. The DVMRP protocol
implements a typical dense mode IP multicast solution and uses IGMP to exchange
routing datagrams with its neighbors.
Dynamic Host
Configuration Protocol
(DHCP)
A client-server networking protocol. A DHCP server provides configuration parameters
specific to the DHCP client host requesting information the host requires to participate
on the Internet network. DHCP also provides a mechanism for allocating IP addresses
to hosts.
data backup A method of copying key data to the backup storage area to prevent data loss in case the
original storage area is damaged or a failure occurs.
data circuit-
terminating equipment
(DCE)
The equipment that provides the signal conversion and coding between the data terminal
equipment (DTE) and the line. A DCE is located at a data station. The DCE may be
separate equipment, or an integral part of the DTE or intermediate equipment. The DCE
may perform other functions that are normally performed at the network end of the line.
data communication
network (DCN)
A communication network used in a TMN or between TMNs to support the data
communication function.
data communications
channel (DCC)
The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
transmit information on the operation, management, maintenance, and provisioning
(OAM&P) between NEs. The DCC channel composed of bytes D1-D3 is referred to as
the 192 kbit/s DCC-R channel. The other DCC channel composed of bytes D4-D12 is
referred to as the 576 kbit/s DCC-M channel.
Transmission System
722
data flow A process that involves processing the data extracted from the source system, such as
filtering, integration, calculation, and summary, finding and solving data inconsistency,
and deleting invalid data so that the processed data meets the requirements of the
destination system for the input data.
data mapping An algorithm that is used to convert the data between heterogeneous data models.
data restoration A method for retrieving data that is lost due to damage or misoperations.
data terminal
equipment (DTE)
A user device composing the UNI. The DTE accesses the data network through the DCE
equipment (for example, a modem) and usually uses the clock signals produced by DCE.
datagram A kind of protocol data unit (PDU) which is used in Connectionless Network Protocol
(CLNP), such as IP datagram, UDP datagram.
defect A limited interruption in the ability of an item to perform a required function.
delay measurement
(DM)
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.
demodulation In communications, the means by which a modem converts data from modulated carrier
frequencies (waves that have been modified in such a way that variations in amplitude
and frequency represent meaningful information) over a telephone line. Data is converted
to the digital form needed by a computer to which the modem is attached, with as little
distortion as possible.
dense wavelength
division multiplexing
(DWDM)
The technology that utilizes the characteristics of broad bandwidth and low attenuation
of single mode optical fiber, employs multiple wavelengths with specific frequency
spacing as carriers, and allows multiple channels to transmit simultaneously in the same
fiber.
designated port A port defined in the STP protocol. On each switch that runs the STP protocol, the traffic
from the root bridge is forwarded to the designated port. The subnet connected to the
STP switch receives the data traffic from the root bridge. All the ports on the root bridge
are designated ports. On each subnet, there is only one designated port. When a network
topology is stable, only the root port and the designated port forward traffic. Other non-
designated ports are in the blocking state, and they receive STP packets, but does not
forward user traffic.
destruction A process during which the information and resources in a network are changed
unexpectedly and the meanings of the information and resources are deleted or changed.
digital data network
(DDN)
A data transmission network that is designed to transmit data on digital channels (such
as the fiber channel, digital microwave channel, or satellite channel).
digital modulation A method that controls the changes in amplitude, phase, and frequency of the carrier
based on the changes in the baseband digital signal. In this manner, the information can
be transmitted by the carrier.
digital network A telecommunication network where information is first converted into distinct
electronic pulses and then transmitted to a digital bit stream.
Transmission System
723
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.
digital subscriber line
(DSL)
A technology for providing digital connections over the copper wire or the local
telephone network. DSL performs data communication over the POTS lines without
affecting the POTS service.
access multiplexer
(DSLAM)
A network device, usually situated in the main office of a telephone company, that
receives signals from multiple customer Digital Subscriber Line (DSL) connections and
uses multiplexing techniques to put these signals on a high-speed backbone line.
dispersion The dependence of refraction on the wavelength of light. Different wavelengths are
transmitted in an optical medium at different speeds. Wavelengths reach the end of the
medium at different times. As a result, the light pulse spreads and the dispersion occurs.
dispersion
compensation module
(DCM)
A type of module that contains dispersion compensation fibers to compensate for the
dispersion of the transmitting fiber.
distributed link
aggregation group
(DLAG)
A board-level port protection technology that detects unidirectional fiber cuts and
negotiates with the opposite port. In the case of a link down failure on a port or hardware
failure on a board, services are automatically switched to the slave board, thereby
achieving 1+1 protection for the inter-board ports.
domain A logical subscriber group based on which the subscriber rights are controlled.
dotted decimal notation A format of IP address. IP addresses in this format are separated into four parts by a dot
"." with each part is in the decimal numeral.
download To obtain data from an upper-layer device or the server.
downstream In an access network, the direction of transmission toward the subscriber end of the link.
dual-ended switching A protection method in which switching is performed at both ends of a protected entity,
such as a connection or path, even if a unidirectional failure occurs.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves
orthogonally polarized.
E
E-Aggr See Ethernet aggregation.
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
EA encryption algorithm
EBS See excess burst size.
ECC See embedded control channel.
EDFA See erbium-doped fiber amplifier.
Transmission System
724
EEPROM See electrically erasable programable read-only memory.
EF See expedited forwarding.
EFCI explicit forward congestion indication
EFM Ethernet in the First Mile
EFM OAM Ethernet in the first mile OAM
EIA See Electronic Industries Alliance.
EIR See excess information rate.
EMC See electromagnetic compatibility.
EMI See electromagnetic interference.
EMS element management system
EPD early packet discard
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
ERPS Ethernet ring protection switching
ESC See electric supervisory channel.
ESCON See enterprise system connection.
ESD electrostatic discharge
ESN See equipment serial number.
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVC Ethernet virtual connection
EVPL See Ethernet virtual private line.
EVPLAN See Ethernet virtual private LAN service.
EXP See experimental bits.
Electronic Industries
Alliance (EIA)
An association based in Washington, D.C., with members from various electronics
manufacturers. It sets standards for electronic components. RS-232-C, for example, is
the EIA standard for connecting serial components.
EoD See Ethernet over dual domains.
Ethernet A LAN technology that uses the carrier sense multiple access with collision detection
(CSMA/CD) media access control method. The Ethernet network is highly reliable and
easy to maintain. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000
Mbit/s, or 10,000 Mbit/s.
Ethernet aggregation
(E-Aggr)
A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual
connection).
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Transmission System
725
Ethernet local area
network (E-LAN)
A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
virtual connection).
Ethernet over dual
domains (EoD)
A type of boards. EoD boards bridge the PSN and TDM networks, enabling Ethernet
service transmission across PSN and TDM networks.
Ethernet private LAN
service (EPLAN)
A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
networks. This service is carried over dedicated bandwidth between multipoint-to-
multipoint connections.
Ethernet private line
(EPL)
networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual
private LAN service
(EVPLAN)
networks. This service is carried over shared bandwidth between multipoint-to-
multipoint connections.
Ethernet virtual
private line (EVPL)
networks. This service is carried over shared bandwidth between point-to-point
connections.
European
Telecommunications
Standards Institute
(ETSI)
A standards-setting body in Europe. Also the standards body responsible for GSM.
eSFP enhanced small form-factor pluggable
egress The egress LER. The group is transferred along the LSP consisting of a series of LSRs
after the group is labeled.
electric supervisory
channel (ESC)
A technology that implements communication among all the nodes and transmission of
monitoring data in an optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
electrically erasable
programable read-only
memory (EEPROM)
A type of EPROM that can be erased with an electrical signal. It is useful for stable
storage for long periods without electricity while still allowing reprograming. EEPROMs
contain less memory than RAM, take longer to reprogram, and can be reprogramed only
a limited number of times before wearing out.
electromagnetic
compatibility (EMC)
A condition which prevails when telecommunications equipment is performing its
individually designed function in a common electromagnetic environment without
causing or suffering unacceptable degradation due to unintentional electromagnetic
interference to or from other equipment in the same environment.
electromagnetic
interference (EMI)
Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
limits the performance of electronics/electrical equipment.
embedded control
channel (ECC)
A logical channel that uses a data communications channel (DCC) as its physical layer
to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.
emergency
maintenance
A type of measure taken to quickly rectify an emergency fault to recover the proper
running of the related system or device and to reduce losses.
Transmission System
726
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.
engineering label A mark on a cable, a subrack, or a cabinet for identification.
enterprise system
connection (ESCON)
A path protocol that connects the host to various control units in a storage system.
Enterprise system connection is a serial bit stream transmission protocol that operates a
rate of 200 Mbit/s.
entity A part, device, subsystem, functional unit, equipment, or system that can be considered
individually.
equalization A method of avoiding selective fading of frequencies. Equalization can compensate for
the changes of amplitude frequency caused by frequency selective fading.
equipment serial
number (ESN)
A string of characters that identify a piece of equipment and ensures correct allocation
of a license file to the specified equipment. It is also called "equipment fingerprint".
erbium-doped fiber
amplifier (EDFA)
An optical device that amplifies optical signals. This device uses a short optical fiber
doped with the rare-earth element, Erbium. The signal to be amplified and a pump laser
are multiplexed into the doped fiber, and the signal is amplified by interacting with
doping ions. When the amplifier passes an external light source pump, it amplifies the
optical signals in a specific wavelength range.
error tolerance The ability of a system or component to continue normal operation despite the presence
of erroneous inputs.
event An event indicates the information record of the status change between the system and
the managed object, including the threshold alarm of the system and the alarm reported
by the managed object.
excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode, traffic
control is achieved by token buckets C and E. The excess burst size parameter defines
the capacity of token bucket E, that is, the maximum burst IP packet size when the
information is transferred at the committed information rate. This parameter must be
greater than 0 but should be not less than the maximum length of an IP packet to be
forwarded.
excess information rate
(EIR)
The bandwidth for excessive or burst traffic above the CIR; it equals the result of the
actual transmission rate without the safety rate.
exercise switching An operation to check whether the protection switching protocol functions properly. The
protection switching is not really performed.
expedited forwarding
(EF)
The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF
traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP
value of EF PHB is "101110".
experimental bits
(EXP)
A field in the MPLS packet header, three bits long. This field is always used to identify
the CoS of the MPLS packet.
Transmission System
727
extended ID The number of the subnet to which an NE belongs, used to identify different network
segments in a wide area network (WAN). Together, the ID and extended ID form the
physical ID of the NE.
external links The links between the current Web site and other Web sites. Generally, external links
refer to links from other Web sites to the current Web site.
extract To read the data required by the destination system from the source system.
F
F1 byte The user path byte, which belongs to the family of regenerator section overhead bytes.
F1 bytes are reserved for network providers, who use them primarily as a temporary data
or voice channel to transmit maintenance information.
FC See Fibre Channel.
FDB flash database
FDD See frequency division duplex.
FDDI See fiber distributed data interface.
FDI See forward defect indication.
FDI packet See forward defect indication packet.
FDV See frame delay variation.
FE port See fast Ethernet port.
FEC See forward error correction.
FFD fast failure detection
FFD packet A path failure detection method independent from CV. Different from a CV packet, the
frequency for generating FFD packets is configurable to satisfy different service
requirements. By default, the frequency is 20/s. An FFD packet contains information the
same as that in a CV packet. The destination end LSR processes FFD packets in the same
way for processing CV packets.
FICON See Fiber Connect.
FIFO first in first out queuing
FLR See frame loss ratio.
FPGA See field programmable gate array.
FPS See fast protection switching.
FQ See flow queue.
FR See frame relay.
FRU field replaceable unit
FTN FEC to NHLFE
FTP File Transfer Protocol
Fiber Connect
(FICON)
A new generation connection protocol that connects the host to various control units. It
carries a single byte command protocol through the physical path of fiber channel, and
provides a higher transmission rate and better performance than ESCON.
Transmission System
728
Fibre Channel (FC) A high-speed transport technology used to build SANs. FC is primarily used for
transporting SCSI traffic from servers to disk arrays, but it can also be used on networks
carrying ATM and IP traffic. FC supports single-mode and multi-mode fiber
connections, and can run on twisted-pair copper wires and coaxial cables. FC provides
both connection-oriented and connectionless services.
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.
fast Ethernet port (FE
port)
The port that provides a rate of 100 Mbit/s.
fast protection
switching (FPS)
A type of pseudo wire automatic protection switching (PW APS). When the working
PW is faulty, the source transmits services to the protection PW and the sink receives
the services from the protection PW. FPS generally works with the interworking function
(IWF) to provide end-to-end protection for services.
fault A failure to operate correctly. A fault does not include failures caused by preventative
maintenance, insufficient external resources, or intentional settings.
fault alarm A type of alarm caused by hardware and/or software faults, for example, board failure,
or by the exception that occurs in major functions. After handling, a fault alarm can be
cleared, upon which the NE reports a recovery alarm. Fault alarms are of higher severity
than event alarms.
fault detection The process of determining that a fault has occurred.
fault notification A process wherein a fault is notified. For example, when a fault occurs on the local
interface, the local interface notifies the peer of the fault through OAMPDUs. The local
interface then records the fault in the log, and reports it to the NMS.
feeder 1. A radio frequency transmission line interconnecting an antenna and a transmitter or
receiver. 2. For an antenna comprising more than one driven element, a radio frequency
transmission Line interconnecting the antenna input and a driven element.
fiber distributed data
interface (FDDI)
A standard developed by the American National Standards Institute (ANSI) for high-
speed fiber-optic LANs. FDDI provides specifications for transmission rates of 100
megabits per second on token ring networks.
fiber trough A trough used for routing fibers.
field programmable
gate array (FPGA)
A semi-customized circuit that is used in the Application Specific Integrated Circuit
(ASIC) field and developed based on programmable components. FPGA remedies many
of the deficiencies of customized circuits, and allows the use of many more gate arrays.
firewall A combination of a series of components set between different networks or network
security domains. By monitoring, limiting, and changing the data traffic across the
firewall, it masks the interior information, structure and running state of the network as
much as possible to protect the network security.
fixed bandwidth The bandwidth that is fully reserved and is allocated periodically in a GPON system to
ensure the quality of cell transmission. If a T-CONT is provided with a fixed bandwidth
and does not transmit cells, the OLT can still allocate/assign the fixed bandwidth.
Therefore, idle cells are transmitted to the upstream OLT from the ONU/ONT.
Transmission System
729
flash memory A type of special electrically erasable programmable read-only memory (EEPROM) and
can be erased and rewritten in blocks at a time instead of only one byte. The data stored
in flash memory will not be lost if the flash memory is powered off.
flooding A type of incident, such as insertion of a large volume of data, that results in denial of
service.
flow An aggregation of packets that have the same characteristics. On boards, it is a group of
packets that have the same quality of service (QoS) operation.
flow queue (FQ) The same type of services of a user is considered one service flow. HQoS performs queue
scheduling according to the services of each user. The service flows of each user are
classified into four FQs, namely, CS, EF, AF, and BE. CS is assigned a traffic shaping
percentage for Priority Queuing (PQ); EF, AF, and BE are assigned weights for Weighted
Fair Queuing (WFQ). The preceding two scheduling modes occupy a certain bandwidth
each; they can act at the same time without interfering each other.
forward defect
indication (FDI)
A packet generated and traced forward to the sink node of the LSP by the node that first
detects defects. It includes fields to indicate the nature of the defect and its location. Its
primary purpose is to suppress alarms being raised at affected higher level client LSPs
and (in turn) their client layers.
forward defect
indication packet (FDI
packet)
A packet that responds to the detected failure event. It is used to suppress alarms of the
upper layer network where failure has occurred.
forward error
correction (FEC)
A bit error correction technology that adds correction information to the payload at the
transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
fragmentation A process of breaking a packet into smaller units when transmitting over a network node
that does not support the original size of the packet.
frame delay variation
(FDV)
A measurement of the variations in the frame delay between a pair of service frames,
where the service frames belong to the same CoS instance on a point to point ETH
connection.
frame loss ratio (FLR) 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.
frame relay (FR) A packet-switching protocol used for WANs. Frame relay transmits variable-length
packets at up to 2 Mbit/s over predetermined, set paths known as PVCs (permanent
virtual circuits). It is a variant of X.25 but sacrifices X.25's error detection for the sake
of speed.
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.
Transmission System
730
frequency division
duplex (FDD)
An application in which channels are divided by frequency. In an FDD system, the uplink
and downlink use different frequencies. Downlink data is sent through bursts. Both
uplink and downlink transmission use frames with fixed time length.
full rate A type of data transmission rate. The service bandwidth can be 9.6 kbit/s, 4.8 kbit/s, or
2.4 kbit/s.
fuse A safety device that protects an electric circuit from excessive current, consisting of or
containing a metal element that melts when current exceeds a specific amperage, thereby
opening the circuit.
G
G-ACH generic associated channel header
GAL generic associated channel header label
GCC general communication channel
GCRA generic cell rate algorithm
GFC generic flow control
GFP See Generic Framing Procedure.
GNE See gateway network element.
GPS See Global Positioning System.
GRE See Generic Routing Encapsulation.
GSM See Global System for Mobile Communications.
GTS See generic traffic shaping.
GUI graphical user interface
Generic Framing
Procedure (GFP)
A framing and encapsulated method that can be applied to any data type. GFP is defined
by ITU-T G.7041.
Generic Routing
Encapsulation (GRE)
A mechanism for encapsulating any network layer protocol over any other network. GRE
is used for encapsulating IP datagrams tunneled through the Internet. GRE serves as a
Layer 3 tunneling protocol and provides a tunnel for transparently transmitting data
packets.
Global Positioning
System (GPS)
A global navigation satellite system that provides reliable positioning, navigation, and
timing services to users worldwide.
Global System for
Mobile
Communications
(GSM)
The second-generation mobile networking standard defined by European
Telecommunications Standards Institute (ETSI). It is aimed at designing a standard for
global mobile phone networks. The standard allows a subscriber to use a phone globally.
GSM consists of three main parts: mobile switching subsystem (MSS), base station
subsystem (BSS), and mobile station (MS).
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 A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
Transmission System
731
gateway network
element (GNE)
An NE that serves as a gateway for other NEs to communicate with a network
management system.
general flow control A flow control that is applicable to the A interface, C/D interface, and trunks and can be
achieved by integrating multiple function modules. It is adopted when the traffic is heavy,
or location update and authentication of multiple subscribers are performed after the
system restarts. It can efficiently prevent system breakdown caused by link congestion
or CPU overload.
generic traffic shaping
(GTS)
A traffic control measure that proactively adjusts the output speed of the traffic. This is
to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
ground terminal A connection terminal on a communication device. It is used to connect the device with
ground cables, maintaining a tight connection between the device and the grounding
electrode.
H
HCS higher order connection supervision
HDB3 high density bipolar of order 3 code
HDLC High-Level Data Link Control
HDTV See high definition television.
HEC See header error control.
HPA higher order path adaptation
HPT higher order path termination
HQoS See hierarchical quality of service.
HSDPA See High Speed Downlink Packet Access.
HSI high-speed Internet
High Speed Downlink
Packet Access
(HSDPA)
A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement
for asymmetric uplink and downlink transmission of data services. It enables the
maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
hang up A call processing mode used by an attendant to end the conversation with a user.
hardware loopback A connection mode in which a fiber jumper is used to connect the input optical interface
of a board to the output optical interface of the board to achieve signal loopback.
header error control
(HEC)
A field within the ATM frame whose purpose is to correct any single bit error in the cell
Header and also to detect any multi-bit errors. It actually performs a CRC check in the
first four header bits and also at the receiving end.
hello packet The commonest packet which is periodically sent by a router to its neighbors. It contains
information about the DR, Backup Designated Router (BDR), known neighbors and
timer values.
Transmission System
732
hierarchical quality of
service (HQoS)
A type of QoS that controls the traffic of users and performs the scheduling according
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
television (HDTV)
A type of TV that is capable of displaying at least 720 progressive or 1080 interlaced
active scan lines. It must be capable of displaying a 16:9 image using at least 540
progressive or 810 interlaced active scan lines.
historical performance
data
Performance data that is stored in the history register or that has been automatically
reported and stored in the NMS.
hop A network connection between two distant nodes. For Internet operation a hop represents
a small step on the route from one main computer to another.
hot patch A patch that is used to repair a deficiency in the software or add a new feature to a program
without restarting the software and interrupting the service. For the equipment using the
built-in system, a hot patch can be loaded, activated, confirmed, deactivated, deleted, or
queried.
I
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICC ITU carrier code
ICMP See Internet Control Message Protocol.
ICP IMA Control Protocol
IDU See indoor unit.
IEEE See Institute of Electrical and Electronics Engineers.
IF See intermediate frequency.
IGMP See Internet Group Management Protocol.
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.
IGP See Interior Gateway Protocol.
ILM incoming label map
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.
IP Internet Protocol
IP address A 32-bit (4-byte) binary number that uniquely identifies a host connected to the Internet.
An IP address is expressed in dotted decimal notation, consisting of the decimal values
of its 4 bytes, separated with periods; for example, 127.0.0.1. The first three bytes of the
IP address identify the network to which the host is connected, and the last byte identifies
the host itself.
Transmission System
733
IPA See intelligent power adjustment.
IPTV See Internet Protocol television.
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
IS-IS See Intermediate System to Intermediate System.
ISDN integrated services digital network
ISO International Organization for Standardization
ISP See Internet service provider.
IST internal spanning tree
ITC independent transmit clock
ITU See International Telecommunication Union.
IWF Interworking Function
Institute of Electrical
and Electronics
Engineers (IEEE)
A professional association of electrical and electronics engineers based in the United
States, but with membership from numerous other countries. The IEEE focuses on
electrical, electronics, and computer engineering, and produces many important
technology standards.
Interior Gateway
Protocol (IGP)
A routing protocol that is used within an autonomous system. The IGP runs in small-
sized and medium-sized networks. The commonly used IGPs are the routing information
protocol (RIP), the interior gateway routing protocol (IGRP), the enhanced IGRP
(EIGRP), and the open shortest path first (OSPF).
Intermediate System to
Intermediate System
(IS-IS)
A protocol used by network devices (routers) to determine the best way to forward
datagram or packets through a packet-based network.
International
Telecommunication
Union (ITU)
A United Nations agency, one of the most important and influential recommendation
bodies, responsible for recommending standards for telecommunication (ITU-T) and
radio networks (ITU-R).
Internet Assigned
Numbers Authority
(IANA)
A department operated by the IAB. IANA delegates authority for IP address-space
allocation and domain-name assignment to the NIC and other organizations. IANA also
maintains a database of assigned protocol identifiers used in the TCP/IP suite, including
autonomous system numbers.
Internet Control
Message Protocol
(ICMP)
A network layer protocol that provides message control and error reporting between a
host server and an Internet gateway.
Internet Group
Management Protocol
(IGMP)
One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
multicast group memberships.
Internet Protocol
television (IPTV)
A system that provides TV services over the IP network. In the IPTV system, media
streams from satellites, terrestrial, and studios are converted by the encoder to the media
streams applicable to the IP network. Then the media streams are transmitted to the
terminal layer on the IP network. Media content is displayed on a TV set after media
streams are processed by specified receiving devices (for example, an STB).
Transmission System
734
Internet Protocol
version 4 (IPv4)
The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers together
are used for routing, and the host number is used to address an individual host within the
network or subnetwork.
Internet Protocol
version 6 (IPv6)
An update version of IPv4, which is designed by the Internet Engineering Task Force
(IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
Internet service
provider (ISP)
An organization that offers users access to the Internet and related services.
inbound Data transmission from the external link to the router for the routers that support the
NetStream feature.
indicator Description of a performance feature collected from the managed devices by the
performance collector.
indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
input jitter tolerance The measure of a receiver's ability to tolerate jitter on an incoming waveform.
insertion loss The loss of power that results from inserting a component, such as a connector, coupler,
or splice, into a previously continuous path.
integrated circuit (IC) A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
intelligent power
adjustment (IPA)
A technology that reduces the optical power of all the amplifiers in an adjacent
regeneration section in the upstream to a safe level if the system detects the loss of optical
signals on the link. IPA helps ensure that maintenance engineers are not injured by the
laser escaping from a broken fiber or a connector that is not plugged in properly.
interleaving A process of systematically changing the bit sequence of a digital signal, usually as part
of the channel coding, in order to reduce the influence of error bursts that may occur
during transmission.
intermediate frequency
(IF)
The transitional frequency between the frequencies of a modulated signal and an RF
signal.
inverse multiplexing
over ATM (IMA)
A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a
cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations, and
control system instability.
jumper A connection wire for connecting two pins.
K
Transmission System
735
K byte A general designation of K1 byte and K2 byte in the SDH.
L
L2 switching The switching based on the data link layer.
L2VPN Layer 2 virtual private network
LACP See Link Aggregation Control Protocol.
LACPDU Link Aggregation Control Protocol data unit
LAG See link aggregation group.
LAN See local area network.
LAPS Link Access Protocol-SDH
LB See loopback.
LBM See loopback message.
LBR See loopback reply.
LC Lucent connector
LCAS See link capacity adjustment scheme.
LCN local communications network
LCT local craft terminal
LDP Label Distribution Protocol
LED See light emitting diode.
LER See label edge router.
LIFO See last in first out.
LIU logical interface unit
LL logical link
LLC See logical link control.
LLID local loopback ID
LM See loss measurement.
LOC loss of continuity
LOM loss of multiframe
LOP loss of pointer
LOS See loss of signal.
LP lower order path
LPA lower order path adaptation
LPF See low-pass filter.
LPT link-state pass through
LSP See label switched path.
Transmission System
736
LSR See label switching router.
LT linktrace
LTM See linktrace message.
LTR See linktrace reply.
LU line unit
Layer 2 switching 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
switching.
Link Aggregation
Control Protocol
(LACP)
A dynamic link aggregation protocol that improves the transmission speed and
reliability. The two ends of the link send LACP packets to inform each other of their
parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
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.
label distribution Packets with the same destination address belong to an FEC. A label out of an MPLS
label resource pool is allocated to the FEC. LSRs record the relationship of the label and
the FEC. Then, LSRs sends a message and advertises to upstream LSRs about the label
and FEC relationship in message. The process is called label distribution.
label edge router (LER) A device that sits at the edge of an MPLS domain, that uses routing information to assign
labels to datagrams and then forwards them into the MPLS domain.
label space Value range of the label allocated to peers.
label switched path
(LSP)
A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label
switching mechanisms. A label-switched path can be chosen dynamically, based on
common routing mechanisms or through configuration.
label switching router
(LSR)
Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is
composed of two parts: control unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label forwarding table, creating and
removing the label switch path; the latter forwards the labels according to groups
received in the label forwarding table.
laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. Semi-conductor lasers provide the light
used in a fiber system.
last in first out (LIFO) A play mode of the voice mails, the last voice mail is played firstly.
layer A concept used to allow transport network functionality to be described hierarchically
as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.
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.
Transmission System
737
light emitting diode
(LED)
A display and lighting technology used in almost every electrical and electronic product
on the market, from a tiny on/off light to digital readouts, flashlights, traffic lights, and
perimeter lighting. LEDs are also used as the light source in multimode fibers, optical
mice, and laser printers.
line rate The maximum packet forwarding capacity on a cable. The value of line rate equals the
maximum transmission rate capable on a given type of media.
linear MSP linear multiplex section protection
link aggregation group
(LAG)
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
adjustment scheme
(LCAS)
LCAS in the virtual concatenation source and sink adaptation functions provides a
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.
link monitoring A mechanism for an interface to notify the peer of the fault when the interface detects
that the number of errored frames, errored codes, or errored frame seconds reaches or
exceeds the specified threshold.
link protection Protection provided by the bypass tunnel for the link on the working tunnel. The link is
a downstream link adjacent to the point of local repair (PLR). When the PLR fails to
provide node protection, the link protection should be provided.
linktrace message
(LTM)
The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP.
LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.
linktrace reply (LTR) For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called LTR. LTR also includes the TTL that equals the result of the TTL of LTM minus
1.
load balancing The distribution of activity across two or more servers or components in order to avoid
overloading any one with too many requests or too much traffic.
loading A process of importing information from the storage device to the memory to facilitate
processing (when the information is data) or execution (when the information is
program).
local MEP An MEP of a device on a network enabled with Ethernet CFM.
local area network
(LAN)
A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building, featuring high speed and low error rate. Current
LANs are generally based on switched Ethernet or Wi-Fi technology and run at 1,000
Mbit/s (that is, 1 Gbit/s).
logical interface An interface that does not exist physically and comes into being through configuration.
It can also exchange data.
logical link control
(LLC)
According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper
sublayer of the OSI data link layer. The LLC is the same for the various physical media
(such as Ethernet, token ring, WLAN).
Transmission System
738
loopback (LB) 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.
loopback message
(LBM)
The loopback packet sent by the node that supports 802.2ag MAC Ping to the destination
node. LBM message carries its own sending time.
loopback reply (LBR) A response message involved in the 802.2ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the LBM.
The LBR carries the sending time of LBM, the receiving time of LBM and the sending
time of LBR.
loss measurement (LM) 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.
loss of signal (LOS) No transitions occurring in the received signal.
low-pass filter (LPF) A filter designed to transmit electromagnetic frequencies below a certain value, while
excluding those of a higher frequency.
lower threshold A lower performance limit which when exceeded by a performance event counter will
trigger a threshold-crossing event.
M
MA maintenance association
MAC See Media Access Control.
MAC address A link layer address or physical address. It is six bytes long.
MAC address aging A function that deletes MAC address entries of a device when no packets are received
from this device within a specified time period.
MADM multiple add/drop multiplexer
MAN See metropolitan area network.
MBS maximum burst size
MCF message communication function
MCR minimum cell rate
MD See maintenance domain.
MDP message dispatch process
ME See maintenance entity.
MEG maintenance entity group
MEL maintenance entity group level
MEP See maintenance entity group end point.
MFAS See multiframe alignment signal.
MIP See maintenance entity group intermediate point.
MLD See multicast listener discovery.
MP maintenance point
Transmission System
739
MPID maintenance point identification
MPLS See Multiprotocol Label Switching.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MS multiplex section
MSA multiplex section adaptation
MSB most significant bit
MSOH multiplex section overhead
MSP See multiplex section protection.
MST See multiplex section termination.
MST region See Multiple Spanning Tree region.
MSTI See multiple spanning tree instance.
MSTP See Multiple Spanning Tree Protocol.
MTBF See mean time between failures.
MTIE maximum time interval error
MTTR See mean time to repair.
MTU See maximum transmission unit.
MUX See multiplexer.
Media Access Control
(MAC)
A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
Multiple Spanning
Tree Protocol (MSTP)
A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
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.
Multiple Spanning
Tree region (MST
region)
A region that consists of switches that support the MSTP in the LAN and links among
them. Switches physically and directly connected and configured with the same MST
region attributes belong to the same MST region.
Multiprotocol Label
Switching (MPLS)
A technology that uses short tags of fixed length to encapsulate packets in different link
layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols.
Transmission System
740
main topology A basic component of a human-machine interface. It is the default client interface of the
NMS and intuitively displays the structure of a network, NEs on the network, subnets in
the network as well as the NE communication and running status, reflecting the overall
network running status.
maintenance domain
(MD)
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).
maintenance entity
(ME)
An ME consists of a pair of maintenance entity group end points (MEPs), two ends of a
transport trail, and maintenance association intermediate points (MIPs) on the trail.
maintenance entity
group end point (MEP)
An end point of a MEG, which is able to initialize and stop the transmission of OAM
data packets for fault management and performance monitoring.
maintenance entity
group intermediate
point (MIP)
An intermediate point in a MEG, which is able to forward OAM packets and respond to
some OAM packets, but unable to initiate the transmission of OAM packets or perform
any operations on network connections.
management
information
The information that is used for network management in a transport network.
unit (MTU)
The largest packet of data that can be transmitted on a network. MTU size varies,
depending on the network576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
mean time between
failures (MTBF)
The average time between consecutive failures of a piece of equipment. It is a measure
of the reliability of the system.
mean time to repair
(MTTR)
The average time that a device will take to recover from a failure.
measurement period The interval for NEs to report measurement results to the Network Management System
(NMS).
medium A physical medium for storing computer information. A medium is used for data
duplication and keeping the data for some time. Original data can be obtained from a
medium.
member A basic element for forming a dimension according to the hierarchy of each level. Each
member represents a data element in a dimension. For example, January 1997 is a typical
member of the time dimension.
metropolitan area
network (MAN)
A medium-scale computer network with area larger than that covered by a LAN and
smaller than that covered by a WAN. It interconnects multiple LAN networks in a
geographic region of a city.
microwave The portion of the electromagnetic spectrum with much longer wavelengths than infrared
radiation, typically above about 1 mm.
mirroring The duplication of data for backup or to distribute network traffic among several
computers with identical data.
Transmission System
741
monitoring A method that an inspector uses to inspect a service agent. By monitoring a service agent,
an inspector can check each detailed operation performed by the service agent during
the conversation and operate the GUI used by the service agent. The inspector helps the
service agent to provide better service.
mounting An auxiliary or associated condition or component of a device.
mounting ear A piece of angle plate on a rack. The mounting ear has holes that can be used to fix
network elements or components.
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.
multicast listener
discovery (MLD)
A protocol used by an IPv6 router to discover the multicast listeners on their directly
connected network segments, and to set up and maintain member relationships. On IPv6
networks, after MLD is configured on the receiver hosts and the multicast router to which
the hosts are directly connected, the hosts can dynamically join related groups and the
multicast router can manage members on the local network.
multiframe alignment
signal (MFAS)
A distinctive signal inserted into every multiframe or once into every n multiframes,
always occupying the same relative position within the multiframe, and used to establish
and maintain multiframe alignment.
multiple spanning tree
instance (MSTI)
A type of spanning trees calculated by MSTP within an MST Region, to provide a simply
and fully connected active topology for frames classified as belonging to a VLAN that
is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to
multiple MSTIs.
multiplex section
protection (MSP)
A function, which is performed to provide capability for switching a signal between and
including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiplex section
termination (MST)
A function that generates the multiplex section overhead (MSOH) during the formation
of an SDH frame signal and that terminates the MSOH in the reverse direction.
multiplexer (MUX) Equipment that combines a number of tributary channels onto a fewer number of
aggregate bearer channels, the relationship between the tributary and aggregate channels
being fixed.
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.
multiprotocol label
switching virtual
private network
(MPLS VPN)
An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label
switching (MPLS) technology. It applies the MPLS technology for network routers and
switches, simplifies the routing mode of core routers, and combines traditional routing
technology and label switching technology. It can be used to construct the broadband
Intranet and Extranet to meet various service requirements.
N
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
NAS network access server
Transmission System
742
NC See NTP client.
NE ID An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NGN See next generation network.
NHLFE next hop label forwarding entry
NLP normal link pulse
NM network management
NMC network management center
NNI network-to-network interface
NP See network processor.
NPC See network parameter control.
NPE network provider edge
NRT-VBR non-real-time variable bit rate
NRZ non-return to zero
NRZ code non-return-to-zero code
NRZI non-return to zero inverted
NSAP See network service access point.
NSF non-stop forwarding
NTP Network Time Protocol
NTP client (NC) A bottom-level device in the time synchronization network. An NTP client obtains time
from its upper-level NTP server without providing the time synchronization service.
Compared with the top-level NTP server, the intermediate NTP server sometimes is
called an NTP client.
network layer Layer 3 of the seven-layer OSI model of computer networking. The network layer
provides routing and addressing so that two terminal systems are interconnected. In
addition, the network layer provides congestion control and traffic control. In the TCP/
IP protocol suite, the functions of the network layer are specified and implemented by
IP protocols. Therefore, the network layer is also called IP layer.
network parameter
control (NPC)
During communications, UPC is implemented to monitor the actual traffic on each virtual
circuit that is input to the network. Once the specified parameter is exceeded, measures
will be taken to control. NPC is similar to UPC in function. The difference is that the
incoming traffic monitoring function is divided into UPC and NPC according to their
positions. UPC locates at the user/network interface, while NPC at the network interface.
network processor (NP) An integrated circuit which has a feature set specifically targeted at the networking
application domain. Network Processors are typically software programmable devices
and would have generic characteristics similar to general purpose CPUs that are
commonly used in many different types of equipment and products.
network segment Part of a network on which all message traffic is common to all nodes; that is, a message
broadcast from one node on the segment is received by all other nodes on the segment.
network service A service that needs to be enabled at the network layer and maintained as a basic service.
Transmission System
743
network service access
point (NSAP)
A network address defined by ISO, at which the OSI Network Service is made available
to a Network service user by the Network service provider.
network storm A phenomenon that occurs during data communication. To be specific, mass broadcast
packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by network
connection or configuration problems.
next generation
network (NGN)
A packet-based network aimed to address requirement of various services. It adopts an
integrated and open network framework. In NGN, services are separated from call
control; call control is separated from bearer. In this way, services are independent of
network. NGN can provide various services, such as voice services, data services,
multimedia services or the integration of several services.
noise figure A measure of degradation of the signal-to-noise ratio (SNR), caused by components in
a radio frequency (RF) signal chain. The noise figure is defined as the ratio of the output
noise power of a device to the portion thereof attributable to thermal noise in the input
termination at standard noise temperature T0 (usually 290 K). The noise figure is thus
the ratio of actual output noise to that which would remain if the device itself did not
introduce noise. It is a number by which the performance of a radio receiver can be
specified.
non-GNE See non-gateway network element.
non-gateway network
element (non-GNE)
A network element that communicates with the NM application layer through the
gateway NE application layer.
O
O&M operation and maintenance
OA optical amplifier
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
OAU See optical amplifier unit.
OC ordinary clock
OCP optical channel protection
OCS optical core switching
ODF optical distribution frame
ODU See outdoor unit.
OFS out-of-frame second
OHA overhead access
OHP overhead processing
OLT optical line terminal
ONU See optical network unit.
OPEX operating expense
Transmission System
744
OPU optical channel payload unit
OSC See optical supervisory channel.
OSN optical switch node
OSNR See optical signal-to-noise ratio.
OSPF See Open Shortest Path First.
OTDR See optical time domain reflectometer.
OTM optical terminal multiplexer
OTN optical transport network
OTU See optical transponder unit.
OTUk optical channel transport unit - k
Open Shortest Path
First (OSPF)
A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
cost as its routing metric. A link state database is constructed of the network topology,
which is identical on all routers in the area.
offline Pertaining to the disconnection between a device or a service unit and the system or the
network, or no running of a device and service unit.
online A state indicating that a computer device or program is activated and is ready for
operations, and can communicate with a computer or can be controlled by the computer.
operation,
administration and
maintenance (OAM)
A set of network management functions that cover fault detection, notification, location,
and repair.
optical add/drop
multiplexer (OADM)
A device that can be used to add the optical signals of various wavelengths to one channel
and drop the optical signals of various wavelengths from one channel.
optical amplifier unit
(OAU)
A board that is mainly responsible for amplifying optical signals. The OAU can be used
in both the transmitting direction and the receiving direction.
optical attenuator A passive device that increases the attenuation in a fiber link. An optical attenuator is
used to ensure that the optical power of a signal at the receive end is not excessively
high.
optical connector A component attached to the end of an optical fiber that allows the fiber to connect to
another fiber or an optical source.
optical fiber A thin filament of glass or other transparent material, through which a signal-encoded
light beam may be transmitted using total internal reflection.
optical interface A component that connects several transmit or receive units.
optical network unit
(ONU)
A form of Access Node that converts optical signals transmitted via fiber to electrical
signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical signal-to-noise
ratio (OSNR)
The ratio of signal power to noise power in a transmission link. OSNR is the most
important index for measuring the performance of a DWDM system.
Transmission System
745
optical splitter A passive component, which is used for splitting and sending optical power to multiple
ONUs connected by an optical fiber. In a GPON system that consists of the OLT, ONU,
splitter, and optical fibers, according to the split ratio, the optical signal over the optical
fiber connected to the OLT is splitted into multiple channels of optical signals and send
each channel to each ONU. Split ratio determines how many channels of optical signals
an optical fiber can be split to.
optical supervisory
channel (OSC)
A technology that uses specific optical wavelengths to realize communication among
nodes in optical transmission network and transmit the monitoring data in a certain
channel.
optical time domain
reflectometer (OTDR)
A device that sends a series of short pulses of light down a fiber-optic cable and measures
the strength of the return pulses. An OTDR is used to measure fiber length and light loss,
and to locate fiber faults.
optical transponder
unit (OTU)
A device or subsystem that converts accessed client signals into a G.694.1/G.694.2-
compliant WDM wavelength.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
outdoor unit (ODU) The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for radio frequency (RF) signals.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PA power amplifier
PADR PPPoE active discovery request
PBS See peak burst size.
PCB See printed circuit board.
PCM See pulse code modulation.
PCR See peak cell rate.
PCS physical coding sublayer
PDH See plesiochronous digital hierarchy.
PDU See power distribution unit.
PE See provider edge.
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.
PHB See per-hop behavior.
PIM-DM Protocol Independent Multicast - Dense Mode
PIM-SM Protocol Independent Multicast - Sparse Mode
PKT partition knowledge table
PLL See phase-locked loop.
Transmission System
746
PM performance monitoring
PMD polarization mode dispersion
POH path overhead
POS See packet over SDH/SONET.
PPD partial packet discard
PPI PDH physical interface
PPP Point-to-Point Protocol
PPPoE Point-to-Point Protocol over Ethernet
PPS port protection switching
PQ See priority queuing.
PRBS See pseudo random binary sequence.
PRC primary reference clock
PSD See power spectrum density.
PSN See packet switched network.
PSTN See public switched telephone network.
PSU power supply unit
PT payload type
PTI payload type indicator
PTN packet transport network
PTP Precision Time Protocol
PVC permanent virtual channel
PVID See port default VLAN ID.
PVP See permanent virtual path.
PW See pseudo wire.
PWE3 See pseudo wire emulation edge-to-edge.
packet discarding A function of discarding the packets from unknown VLAN domain or broadcast packets.
Packet Discarding is used to prevent the situation where unknown packets or broadcast
packets use the bandwidth on a link, improving the reliability of service transmission.
packet forwarding An action performed by a router to forward a received datagram, where the destination
IP address does not match the IP address of the router, to another router or destination
host on the router list.
packet loss The discarding of data packets in a network when a device is overloaded and cannot
accept any incoming data at a given moment.
packet over SDH/
SONET (POS)
A MAN and WAN technology that provides point-to-point data connections. The POS
interface uses SDH/SONET as the physical layer protocol, and supports the transport of
packet data (such as IP packets) in MAN and WAN.
Transmission System
747
packet rate The number of bits or bytes passed within a specified time. It is expressed in bits/s or
bytes/s.
packet switched
network (PSN)
A telecommunications network that works in packet switching mode.
packet switching A network technology in which information is transmitted by means of exchanging
packets and the bandwidth of a channel can be shared by multiple connections.
paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane.
parity bit A check bit appended to an array of binary digits to make the sum of all the binary digits,
including the check bit, always odd or always even.
parity check A method for character level error detection. An extra bit is added to a string of bits,
usually a 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd or
even parity). Both ends of a data transmission must use the same parity. When the
transmitting device frames a character, it counts the numbers of 1s in the frame and
attaches the appropriate parity bit. The recipient counts the 1s and, if there is parity error,
may ask for the data to be retransmitted.
parts replacement A maintenance operation of removing a faulty part or a part to be examined from a
running device and then installing a new part.
passive mode A working mode of EFM OAM. An interface in the passive mode cannot initiate the
discovery and remote loopback.
patch An independent software unit used for fixing the bugs in software.
peak burst size (PBS) A parameter that defines the capacity of token bucket P, that is, the maximum burst IP
packet size when the information is transferred at the peak information rate.
peak cell rate (PCR) The maximum rate at which an ATM connection can accept cells.
peer BGP speakers that exchange information with each other.
per-hop behavior
(PHB)
IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).
performance alarm An alarm generated when the actual result of a measurement entity equals the predefined
logical expression for threshold or exceeds the predefined threshold.
performance
parameters
The performance parameters identify some indexes to scale the general performance of
the system. The indexes include the number of managed nodes, number of supported
clients and log database capacity. The parameters are sorted into static parameters,
dynamic parameters and networking bandwidth parameters.
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.
Transmission System
748
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 path
(PVP)
Virtual path that consists of PVCs.
phase The relative position in time within a single period of a signal.
phase-locked loop
(PLL)
A circuit that consists essentially of a phase detector that compares the frequency of a
voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency generator. The output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
physical layer Layer 1 in the Open System Interconnection (OSI) architecture; the layer that provides
services to transmit bits or groups of bits over a transmission link between open systems
and which entails electrical, mechanical and handshaking.
physical link The link between two physical network elements (NEs). When the user creates NEs or
refreshes the device status, the system automatically creates the physical link according
to the topology structure information on the device. The remark information of a physical
link can be modified, but the physical link cannot be deleted.
ping A method used to test whether a device in the IP network is reachable according to the
sent ICMP Echo messages and received response messages.
ping test A test that is performed to send a data packet to the target IP address (a unique IP address
on the device on the network) to check whether the target host exists according to the
data packet of the same size returned from the target host.
plesiochronous digital
hierarchy (PDH)
A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
point-to-point service
(P2P)
A service between two terminal users. In P2P services, senders and recipients are
terminal users.
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.
polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
policy A set of rules that are applied when the conditions for triggering an event are met.
policy template A template that is used to define the calculation rules of a charging event, for example,
rating, debiting and accumulating. A policy template may contain the parameters to be
instantiated. They can be used when the attributes of the condition judgment, calculation
method, and action functions are carried out.
polling A mechanism for the NMS to query the agent status and other data on a regular basis.
port default VLAN ID
(PVID)
A default VLAN ID of a port. It is allocated to a data frame if the data frame carries no
VLAN tag when reaching the port.
Transmission System
749
port priority The priority that is used when a port attaches tags to Layer 2 packets. Packets received
on ports with higher priorities are forwarded preferentially.
power adjustment A method for dynamically and properly assigning power according to the real-time status
of a wireless network. When an AP runs under an AC for the first time, the AP uses its
maximum transmit power. When getting reports from its neighbors (that is, other APs
that are detected by the AP and managed by the same AC), the AP determines to increase
or decrease its power according to the report conclusion.
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 control A process in which the MS or BS uses certain rules to adjust and control the transmit
power according to the change in the channel condition and the power of the received
signal.
power distribution unit
(PDU)
A unit that performs AC or DC power distribution.
power module The module that converts the external power input into the power supply for internal
use. Power modules are classified into AC power modules and DC power modules.
power off An operation that switches off devices during upgrade or expansion.
power on To start up a computer; to begin a cold boot procedure; to turn on the power
power spectrum
density (PSD)
The power layout of random signals in the frequency domain.
printed circuit board
(PCB)
A board used to mechanically support and electrically connect electronic components
using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
priority queuing (PQ) A queue scheduling algorithm based on the absolute priority. According to the PQ
algorithm, services of higher priorities are ensured with greater bandwidth, lower
latency, and less jitter. Packets of lower priorities must wait to be sent till all packets of
higher priorities are sent. In this manner, services of higher priorities are processed earlier
than others.
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 path in a protection group that transports services when a fault occurs on the working
path.
provider edge (PE) 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.
pseudo random binary
sequence (PRBS)
A sequence that is random in the sense that the value of each element is independent of
the values of any of the other elements, similar to a real random sequence.
pseudo wire (PW) 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.
Transmission System
750
pseudo wire emulation
edge-to-edge (PWE3)
An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
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.
public switched
telephone network
(PSTN)
A telecommunications network established to perform telephone services for the public
subscribers. Sometimes it is called POTS.
pulse A variation above or below a normal level and a given duration in electrical energy.
pulse code modulation
(PCM)
A method of encoding information in a signal by changing the amplitude of pulses.
Unlike pulse amplitude modulation (PAM), in which pulse amplitude can change
continuously, pulse code modulation limits pulse amplitudes to several predefined
values. Because the signal is discrete, or digital, rather than analog, pulse code
modulation is more immune to noise than PAM.
Q
QA Q adaptation
QAM See quadrature amplitude modulation.
QPSK See quadrature phase shift keying.
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.
quadrature amplitude
modulation (QAM)
Both an analog and a digital modulation scheme. It conveys two analog message signals,
or two digital bit streams, by changing (modulating) the amplitudes of two carrier waves,
using the amplitude-shift keying (ASK) digital modulation scheme or amplitude
modulation (AM) analog modulation scheme. These two waves, usually sinusoids, are
out of phase with each other by 90 and are thus called quadrature carriers or quadrature
components hence the name of the scheme.
quadrature phase shift
keying (QPSK)
A modulation method of data transmission through the conversion or modulation and
the phase determination of the reference signals (carrier). It is also called the fourth period
or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are
evenly distributed on a circle. On these phases, each QPSK character can perform two-
bit coding and display the codes in Gray code on graph with the minimum BER.
quality of service (QoS) 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.
R
RADIUS See Remote Authentication Dial In User Service.
Transmission System
751
RAI remote alarm indication
RDI remote defect indication
RED See random early detection.
REG See regenerator.
REI remote error indication
RF See radio frequency.
RIP See Routing Information Protocol.
RMEP remote maintenance association end point
RNC See radio network controller.
ROPA See remote optical pumping amplifier.
RP rendezvous point
RPR resilient packet ring
RS232 See Reference Standard 232.
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.
RSL See received signal level.
RSOH regenerator section overhead
RSSI See received signal strength indicator.
RST regenerator section termination
RSTP See Rapid Spanning Tree Protocol.
RTN radio transmission node
RTP See Real-Time Transport Protocol.
Rapid Spanning Tree
Protocol (RSTP)
An evolution of the Spanning Tree Protocol (STP) that provides faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Real-Time Transport
Protocol (RTP)
A protocol defined by the IETF for transmitting audio and video streams. RTP is based
on UDP. In the RTP header, a time stamp is defined to ensure that audio and video data
can be transmitted and synchronized in real time. H.323 is based on RTP.
Reference Standard
232 (RS232)
A standard that defines the electrical characteristics, timing, and meaning of signals, and
the physical size and pinout of connectors.
Remote Authentication
Dial In User Service
(RADIUS)
A security service that authenticates and authorizes dial-up users and is a centralized
access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
RoHS restriction of the use of certain hazardous substances
Transmission System
752
Routing Information
Protocol (RIP)
A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route
based on the smallest hop count between the source and destination. RIP is a distance
vector protocol that routinely broadcasts routing information to its neighboring routers
and is known to waste bandwidth.
radio frequency (RF) A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
radio network
controller (RNC)
A device in a radio network subsystem that is in charge of controlling the usage and
integrity of radio resources.
radio propagation
model
An empirical mathematical formulation for the characterization of radio wave
propagation as a function of frequency, distance and other conditions. A single model is
usually developed to predict the behavior of propagation for all similar links under
similar constraints.
random early detection
(RED)
A packet loss algorithm used in congestion avoidance. It discards the packet according
to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulting from traditional tail drop can be prevented.
rate limiting A traffic management technology used to limit the total rate of packet sending on a
physical interface or a Tunnel interface. Rate limiting is directly enabled on the interface
to control the traffic passing the interface.
real-time variable bit
rate (rt-VBR)
A parameter intended for real-time applications, such as compressed voice over IP
(VoIP) and video conferencing. The rt-VBR is characterized by a peak cell rate (PCR),
sustained cell rate (SCR), and maximum burst size (MBS). You can expect the source
device to transmit in bursts and at a rate that varies with time.
reboot To start the system again. Programs or data will be reloaded to all boards.
received signal level
(RSL)
The signal level at a receiver input terminal.
received signal strength
indicator (RSSI)
The received wide band power, including thermal noise and noise generated in the
receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a reference point
at an input to a receiver optical connector) to achieve a 1x10-12 BER when the FEC is
enabled.
recognition Consumer awareness of having seen or heard an advertising message.
reference clock A stable and high-precision autonomous clock that provides frequencies as a reference
for other clocks.
reflectance The ratio of the reflected optical power to the incident optical power.
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 (REG) A piece of equipment or device that regenerates electrical signals.
Transmission System
753
relay An electronic control device that has a control system and a system to be controlled. The
relay of the telepresence system is used to control the power of telepresence equipment
and is controlled by the telepresence host.
remote optical
pumping amplifier
(ROPA)
A remote optical amplifier subsystem designed for applications where power supply and
monitoring systems are unavailable. The ROPA subsystem is a power compensation
solution to the ultra-long distance long hop (LHP) transmission.
reservation An action that the charging module performs to freeze a subscriber's balance amount,
free resources, credits, or quotas before the subscriber uses services. This action ensures
that the subscriber has sufficient balance to pay for services.
resistance The ability to impede (resist) the flow of electric current. With the exception of
superconductors, all substances have a greater or lesser degree of resistance. Substances
with very low resistance, such as metals, conduct electricity well and are called
conductors. Substances with very high resistance, such as glass and rubber, conduct
electricity poorly and are called nonconductors or insulators.
resource sharing A physical resource belonging to two or more protection subnetworks.
response A message that is returned to the requester to notify the requester of the status of the
request packet.
robustness The ability of a system to maintain function even with changes in internal structure or
external environment.
rollback A return to a previous condition through cancellation of a certain operation.
root alarm An alarm directly caused by anomaly events or faults in the network. Some lower-level
alarms always accompany a root alarm.
route The path that network traffic takes from its source to its destination. 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.
routing The determination of a path that a data unit (frame, packet, message) traverses from
source to destination.
routing protocol A formula used by routers to determine the appropriate path onto which data should be
forwarded.
rt-VBR See real-time variable bit rate.
S
Transmission System
754
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
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SC square connector
SCR sustainable cell rate
SD See signal degrade.
SD trigger flag A signal degrade trigger flag that determines whether to perform a switching when SD
occurs. The SD trigger flag can be set by using the network management system.
SD-SDI See standard definition-serial digital interface signal.
SDH See synchronous digital hierarchy.
SDP serious disturbance period
SDRAM See synchronous dynamic random access memory.
SELV safety extra-low voltage
SEMF synchronous equipment management function
SES severely errored second
SETS SDH equipment timing source
SF See signal fail.
SFP small form-factor pluggable
SFTP See Secure File Transfer Protocol.
SHDSL See single-pair high-speed digital subscriber line.
SMSR side mode suppression ratio
SNC subnetwork connection
SNCMP subnetwork connection multipath protection
SNCP subnetwork connection protection
SNCTP subnetwork connection tunnel protection
SNMP See Simple Network Management Protocol.
SNR See signal-to-noise ratio.
SOH section overhead
Transmission System
755
SONET See synchronous optical network.
SPE See superstratum provider edge.
SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
SSMB synchronization status message byte
SSU synchronization supply unit
STD system target decoder
STP Spanning Tree Protocol
SVC switched virtual connection
Secure File Transfer
Protocol (SFTP)
A network protocol designed to provide secure file transfer over SSH.
Secure Sockets Layer
(SSL)
A security protocol that works at a socket level. This layer exists between the TCP layer
and the application layer to encrypt/decode data and authenticate concerned entities.
Simple Network
Management Protocol
(SNMP)
A network management protocol of TCP/IP. It enables remote users to view and modify
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.
Synchronization Status
Message (SSM)
A message that carries the quality levels of timing signals on a synchronous timing link.
SSM messages provide upstream clock information to nodes on an SDH network or
synchronization network.
security Protection of a computer system and its data from harm or loss. A major focus of
computer security, especially on systems accessed by many people or through
communication lines, is preventing system access by unauthorized individuals.
security service A service, provided by a layer of communicating open systems, which ensures adequate
security of the systems or of data transfer.
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 An input/output location (channel) that sends and receives data to and from a computer's
CPU or a communications device one bit at a time. Serial ports are used for serial data
communication and as interfaces with some peripheral devices, such as mice and printers.
service flow An MAC-layer-based unidirectional transmission service. It is used to transmit data
packets, and is characterized by a set of QoS parameters, such as latency, jitter, and
throughput.
service level The level of service quality of an evaluated party in a specified period, determined by
an evaluating party.
service protection A measure that ensures that services can be received at the receive end.
Transmission System
756
session A logical connection between two nodes on a network for the exchange of data. It
generally can apply to any link between any two data devices. A session is also used
simply to describe the connection time.
shaping A process of delaying packets within a traffic stream to cause it to conform to specific
defined traffic profile.
signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded defect
condition is active.
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio
(SNR)
The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB.
signaling The information exchange concerning the establishment and control of a
telecommunication circuit and the management of the network.
single-ended switching A protection mechanism that takes switching action only at the affected end of the
protected entity in the case of a unidirectional failure.
single-pair high-speed
(SHDSL)
A symmetric digital subscriber line technology developed from HDSL, SDSL, and
HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user
terminal through the plain telephone subscriber line and uses trellis coded pulse
amplitude modulation (TC-PAM) technology to transmit high-speed data and provide
the broadband access service.
single-polarized
antenna
An antenna intended to radiate or receive radio waves with only one specified
polarization.
slicing Dividing data into the information units proper for transmission.
smooth upgrade Process of upgrading the system files without service interruption
span The physical reach between two pieces of WDM equipment.
standard definition-
serial digital interface
signal (SD-SDI)
Standard definition video signal transported by serial digital interface.
static ARP A protocol that binds some IP addresses to a specified gateway. The packet of these IP
addresses must be forwarded through this gateway.
static route A route that cannot adapt to the change of network topology. Operators must configure
it manually. When a network topology is simple, the network can work in the normal
state if only the static route is configured. It can improve network performance and ensure
bandwidth for important applications. Its disadvantage is as follows: When a network is
faulty or the topology changes, the static route does not change automatically. It must
be changed by the operators.
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.
Transmission System
757
steering A protection switching mode defined in ITU-T G.8132, which is applicable to packet-
based T-MPLS ring networks and similar to SDH transoceanic multiplex section
protection (MSP). In this mode, the switching is triggered by the source and sink nodes
of a service.
stress The force, or combination of forces, which produces a strain; force exerted in any
direction or manner between contiguous bodies, or parts of bodies, and taking specific
names according to its direction, or mode of action, as thrust or pressure, pull or tension,
shear or tangential stress.
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 device and is matched
with the IP address.
superstratum provider
edge (SPE)
Core devices that are located within a VPLS full-meshed network. The UPE devices that
are connected with the SPE devices are similar to the CE devices. The PWs set up
between the UPE devices and the SPE devices serve as the ACs of the SPE devices. The
SPE devices must learn the MAC addresses of all the sites on UPE side and those of the
UPE interfaces that are connected with the SPE. SPE is sometimes called NPE.
switching capacity The backplane bandwidth or switching bandwidth. The switching capacity is the
maximum data that can be processed by the interface processor of a switch and the data
bus. The backplane bandwidth indicates the overall data switching capability of a switch,
in Gbit/s.
switching priority A priority assigned to boards that share protection. If multiple boards that are sharing
protection fail, the services of the board with the highest priority are switched to the
protection board. If two or more boards have the same priority, the services of whichever
board fails first are switched.
synchronous digital
hierarchy (SDH)
A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH defines the
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.
synchronous dynamic
random access memory
(SDRAM)
A new type of DRAM that can run at much higher clock speeds than conventional
memory. SDRAM actually synchronizes itself with the CPU's bus and is capable of
running at 100 MHz, about three times faster than conventional FPM RAM, and about
twice as fast as EDO DRAM or BEDO DRAM. SDRAM is replacing EDO DRAM in
computers.
synchronous optical
network (SONET)
A high-speed network that provides a standard interface for communications carriers to
connect networks based on fiber optical cable. SONET is designed to handle multiple
data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbit/s, but
multiples of this base rate go as high as 2.488 Gbit/s.
T
TCI tag control information
TCM tandem connection monitor
TCN topology change notification
Transmission System
758
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TDC tunable dispersion compensator
TDM See time division multiplexing.
TE terminal equipment
TFTP See Trivial File Transfer Protocol.
TIM trace identifier mismatch
TLV See type-length-value.
TM See terminal multiplexer.
TMN See telecommunications management network.
TOD time of day
TPID tag protocol identifier
TPS See tributary protection switching.
TPS protection The equipment level protection that uses one standby tributary board to protect N
tributary boards. When a fault occurs on the working board, the SCC issues the switching
command, and the payload of the working board can be automatically switched over to
the specified protection board and the protection board takes over as the working board.
After the fault is rectified, the service is automatically switched to the original board.
TSD trail signal degrade
TTI trail trace identifier
TTL See time to live.
TTSI See trail termination source identifier.
TU tributary unit
TU-LOP tributary unit loss of pointer
TUG tributary unit group
Tc committed rate measurement interval
Telnet A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet allows users
to log in to remote systems and use resources as if they were connected to a local system.
Telnet is defined in RFC 854.
Transmission Control
Protocol (TCP)
The protocol within TCP/IP that governs the breakup of data messages into packets to
be sent using Internet Protocol (IP), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
Trivial File Transfer
Protocol (TFTP)
A small and simple alternative to FTP for transferring files. TFTP is intended for
applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication.
Transmission System
759
tail drop A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
tangent ring A concept borrowed from geometry. Two tangent rings have a common node between
them. The common node often leads to single-point failures.
telecommunications
management network
(TMN)
A protocol model defined by ITU-T for managing open systems in a communications
network. TMN manages the planning, provisioning, installation, and OAM of
equipment, networks, and services.
terminal multiplexer
(TM)
A device used at a network terminal either to multiplex multiple channels of low rate
signals into one channel of high rate signals, or to demultiplex one channel of high rate
signals into multiple channels of low rate signals.
threshold A limitation on an amount, scale, or level. Changes will occur when a threshold is
reached.
threshold alarm The alarm occurs when the monitored value exceeds the threshold.
throughput The maximum transmission rate of the tested object (system, equipment, connection,
service type) when no packet is discarded. Throughput can be measured with bandwidth.
throughput capability The data input/output capability of the data transmission interface.
time division
multiplexing (TDM)
A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
(TSn, n=0, 1, 2, 3), and the sampling value codes of multiple signals engross time slots
in a certain order, forming multiple multiplexing digital signals to be transmitted over
one channel.
time to live (TTL) A specified period of time for best-effort delivery systems to prevent packets from
looping endlessly.
timer Symbolic representation for a timer object (for example, a timer object may have a
primitive designated as T-Start Request). Various MAC entities utilize timer entities that
provide triggers for certain MAC state transitions.
timestamp The current time of an event that is recorded by a computer. By using mechanisms such
as the Network Time Protocol (NTP), a computer maintains accurate current time,
calibrated to minute fractions of a second.
token bucket algorithm The token bucket is a container for tokens. The capacity of a token bucket is limited, and
the number of tokens determines the traffic rate of permitted packets. The token bucket
polices the traffic. Users place the tokens into the bucket regularly according to the preset
rate. If the tokens in the bucket exceed the capacity, no tokens can be put in. Packets can
be forwarded when the bucket has tokens, otherwise they cannot be transferred till there
are new tokens in the bucket. This scheme adjusts the rate of packet input.
topology The configuration or layout of a network formed by the connections between devices on
a local area network (LAN) or between two or more LANs.
topology discovery A technique to accurately determine the exact layout of a network using a few
assumptions about the network architecture and simple tools.
trTCM See two rate three color marker.
traceroute A program that prints the path to a destination. Traceroute sends a sequence of datagrams
with the time-to-live (TTL) set to 1,2, and so on, and uses ICMP time exceeded messages
that return to determine routers along the path.
Transmission System
760
traffic The product of the number of calls made and received and the average duration of each
call in a measurement period.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the entire
network. In this way, different traffic packets can be treated differently.
traffic policy A full set of QoS policies formed by association of traffic classification and QoS actions.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in the
scenario that the traffic matches network resources provided by the lower layer devices,
avoiding packet loss and congestion.
traffic statistics An activity of measuring and collecting statistics of various data on devices and
telecommunications networks. With the statistics, operators can be aware of the
operating status, signaling, users, system resource usage of the devices or networks. The
statistics also help the operators manage the device operating, locate problems, monitor
and maintain the networks, and plan the networks.
trail management
function
A network level management function of the network management system. This 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.
trail termination source
identifier (TTSI)
A TTSI uniquely identifies an LSP in the network. A TTSI is carried in the connectivity
verification (CV) packet for checking the connectivity of a trail. If it matches the TTSI
received by the sink point, the trail has no connectivity defect.
transaction Business between the customer and carrier, such as payment, and account adjustment.
transfer A process of transferring the account balance of an account to another account.
transit A packet is transmitted along an LSP consisting of a series of LSRs after the packet is
labeled. The intermediate nodes are named transits.
transit node All the nodes except the master node on an RRPP ring.
transmission delay The period from the time when a site starts to transmit a data frame to the time when the
site finishes the data frame transmission. It consists of the transmission latency and the
equipment forwarding latency.
transmit power control A technical mechanism used within some networking devices in order to prevent too
much unwanted interference between different wireless networks.
transparent
transmission
A process during which the signaling protocol or data is not processed in the content but
encapsulated in the format for the processing of the next phase.
tray A component that can be installed in a cabinet for holding chassis or other components.
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
switching (TPS)
A function that uses a standby tributary processing board to protect N tributary
processing boards.
trunk Physical communications line between two offices. It transports media signals such as
speech, data and video signals.
Transmission System
761
trunk link A link used to transport VLAN communication between two switches.
trunk port A switch port used to connect to other switches. The trunk port can connect to only the
trunk link. Only VLANs allowed to pass through a trunk port can be configured on the
trunk port.
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.
tunnel ID A group of information, including the token, slot number of an outgoing interface, tunnel
type, and location method.
twisted pair cable A type of cable that consists of two independently insulated wires twisted around one
another for the purposes of canceling out electromagnetic interference which can cause
crosstalk. The number of twists per meter makes up part of the specifications for a given
type of cable. The greater the number of twists is, the more crosstalk is reduced.
two rate three color
marker (trTCM)
An algorithm that meters an IP packet stream and marks its packets based on two rates,
Peak Information Rate (PIR) and Committed Information Rate (CIR), and their
associated burst sizes to be either green, yellow, or red. A packet is marked red if it
exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it
exceeds or does not exceed the CIR.
type-length-value
(TLV)
An encoding type that features high efficiency and expansibility. It is also called Code-
Length-Value (CLV). T indicates that different types can be defined through different
values. L indicates the total length of the value field. V indicates the actual data of the
TLV and is most important. TLV encoding features high expansibility. New TLVs can
be added to support new features, which is flexible in describing information loaded in
packets.
U
UART universal asynchronous receiver/transmitter
UAS unavailable second
UAT See unavailable time event.
UBR unspecified bit rate
UBR+ Unspecified Bit Rate Plus
UDP See User Datagram Protocol.
UNI See user-to-network interface.
UPC See usage parameter control.
UPE user-end provider edge
UPI user payload identifier
UPM uninterruptible power module
UPS uninterruptible power supply
Transmission System
762
User Datagram
Protocol (UDP)
A TCP/IP standard protocol that allows an application program on one device to send a
datagram to an application program on another. UDP uses IP to deliver datagrams. UDP
provides application programs with the unreliable connectionless packet delivery
service. That is, UDP messages may be lost, duplicated, delayed, or delivered out of
order. The destination device does not actively confirm whether the correct data packet
is received.
unavailable time event
(UAT)
An event that is reported when the monitored object generates 10 consecutive severely
errored seconds.
unicast The process of sending data from a source to a single recipient.
unknown multicast
packet
A packet for which no forwarding entry is found in the multicast forwarding table.
uplink A transmission channel through which radio signals or other signals are transmitted to
the central office.
uplink tunnel GTP Tunnel from the Mobile Node to the SGSN.
upper limit A maximum consumption amount that a carrier sets for a subscriber in a bill cycle. If
the consumption amount if a subscriber exceeds the maximum consumption amount, the
OCS system deducts only the maximum consumption amount from the account of the
subscriber.
upstream In an access network, the direction that is far from the subscriber end of the link.
upstream board A board that provides the upstream transmission function. Through an upstream board,
services can be transmitted upstream to the upper-layer device.
usage parameter
control (UPC)
During communications, UPC is implemented to monitor the actual traffic on each virtual
circuit that is input to the network. Once the specified parameter is exceeded, measures
will be taken to control. NPC is similar to UPC in function. The difference is that the
incoming traffic monitoring function is divided into UPC and NPC according to their
positions. UPC locates at the user/network interface, while NPC at the network interface.
user-to-network
interface (UNI)
The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
V-NNI virtual network-network interface
V-UNI See virtual user-network interface.
V.24 The physical layer interface specification between DTE and DCE defined by the ITU-
T. It complies with EIA/TIA-232.
VAS See value-added service.
VB virtual bridge
VBR See variable bit rate.
VC trunk See virtual container trunk.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
Transmission System
763
VCI virtual channel identifier
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VIP very important person
VLAN virtual local area network
VLAN mapping A technology that enables user packets to be transmitted over the public network by
translating private VLAN tags into public VLAN tags. When user packets arrive at the
destination private network, VLAN mapping translates public VLAN tags back into
private VLAN tags. In this manner, user packets are correctly transmitted to the
destination.
VLAN mapping table One of the properties of the MST region, which describes mappings between VLANs
and spanning tree instances.
VLAN stacking A technology that adds a VLAN tag to each incoming packet. The VLAN stacking
technology implements transparent transmission of C-VLANs in the ISP network to
realize the application of Layer 2 Virtual Private Network (VPN).
VP See virtual path.
VPI See virtual path identifier.
VPLS See virtual private LAN service.
VPN virtual private network
VRRP See Virtual Router Redundancy Protocol.
VSI virtual switch interface
Virtual Router
Redundancy Protocol
(VRRP)
A protocol designed for multicast or broadcast LANs such as an Ethernet. A group of
routers (including an active router and several backup routers) in a LAN is regarded as
a virtual router, which is called a backup group. The virtual router has its own IP address.
The host in the network communicates with other networks through this virtual router.
If the active router in the backup group fails, one of the backup routers in this backup
group becomes active and provides routing service for the host in the network.
value-added service
(VAS)
A service provided by carriers and service providers (SPs) together for subscribers based
on voice, data, images, SMS messages, and so on. Communication network technologies,
computer technologies, and Internet technologies are used to provide value-added
services.
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.
virtual channel
connection (VCC)
A VC logical trail that carries data between two end points in an ATM network. A point-
to-multipoint VCC is a set of ATM virtual connections between two or multiple end
points.
virtual circuit A channel or circuit established between two points on a data communications network
with packet switching. Virtual circuits can be permanent virtual circuits (PVCs) or
switched virtual circuits (SVCs) .
virtual concatenation
group (VCG)
A group of co-located member trail termination functions that are connected to the same
virtual concatenation link.
Transmission System
764
virtual container trunk
(VC trunk)
The logical path formed by some cascaded VCs.
virtual fiber The fiber that is created between different devices. A virtual fiber represents the optical
path that bears SDH services in a WDM system.
virtual path (VP) A bundle of virtual channels, all of which are switched transparently across an ATM
network based on a common VPI.
virtual path identifier
(VPI)
The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which
virtual path the cell belongs.
virtual private LAN
service (VPLS)
A type of point-to-multipoint L2VPN service provided over the public network. VPLS
enables geographically isolated user sites to communicate with each other through the
MAN/WAN as if they are on the same LAN.
virtual user-network
interface (V-UNI)
A virtual user-network interface, works as an action point to perform service
classification and traffic control in HQoS.
voltage drop The voltage developed across a component or conductor by the flow of current through
the resistance or impedance of that component or conductor.
W
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WFQ See weighted fair queuing.
WLAN See wireless local area network.
WRED See weighted random early detection.
WRR weighted round robin
WTR See wait to restore.
Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
Wideband Code
Division Multiple
Access (WCDMA)
A standard defined by the ITU-T for the third-generation wireless technology derived
from the Code Division Multiple Access (CDMA) technology.
wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.
wavelength The distance between successive peaks or troughs in a traveling wave, that is, the distance
over which a wave is transmitted within a vibration period.
weighted fair queuing
(WFQ)
A fair queue scheduling algorithm based on bandwidth allocation weights. This
scheduling algorithm allocates the total bandwidth of an interface to queues, according
to their weights and schedules the queues cyclically. In this manner, packets of all priority
queues can be scheduled.
weighted random early
detection (WRED)
A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
Transmission System
765
wireless local area
network (WLAN)
A hybrid of the computer network and the wireless communication technology. It uses
wireless multiple address channels as transmission media and carriers out data interaction
through electromagnetic wave to implement the functions of the traditional LAN.
working path A path allocated to transport the normal traffic.
working service A specific service that is part of a protection group and is labeled working.
wrapping A protection switching mode defined in ITU-T G.8132, which is applicable to packet-
based T-MPLS ring networks and similar to SDH two-fiber bidirectional multiplex
section protection (MSP). In this mode, the switching is triggered by the node that detects
a failure. For details, see ITU-T G.841.
X
X.21 ITU-T standard for serial communications over synchronous digital lines. It is mainly
used in Europe and Japan.
X.25 A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
Y
Y.1731 The OAM protocol introduced by the ITU-T. Besides the contents defined by
IEEE802.1ag, ITU-T Recommendation Y.173 also defines the following combined
OAM messages: Alarm Indication Signal (AIS), Remote Defect Indication (RDI),
Locked Signal (LCK), Test Signal, Automatic Protection Switching (APS), Maintenance
Communication Channel (MCC), Experimental (EXP), and Vendor Specific (VSP) for
fault management and performance monitoring, such as frame loss measurement (LM),
and delay measurement (DM).
Transmission System
766

OSN 500 550 V100R007C00 Configuration Guide (Packet Transport Domain) 03

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OSN 500 550 V100R007C00 Configuration Guide (Packet Transport Domain) 03

Caricato da

Copyright:

Formati disponibili

OptiX OSN 500/550 Multi-Service CPE Optical

Potrebbero piacerti anche