OG For RTN NE Management - (V100R002C01 - 02) PDF

iManager U2000 Unified Network Management
System
V100R002C01
Operation Guide for RTN NE

Management
Issue 02
Date 2010-09-24
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2010-09-24) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
Operation Guide for RTN NE Management About This Document
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager U2000 V100R002C01
Intended Audience
This document describes the operations, such as how to configure the communication, clock and
service of the RTN equipment on the U2000. This document also provides the glossary and the
acronyms and abbreviations.
This document guides the user to understand basic operations of the U2000.
This document is intended for:
l Network Monitoring Engineer

l Data Configuration Engineer
l NMS Administrators
l System Maintenance Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

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

if not avoided, could result in minor or moderate injury.
WARNING
Issue 02 (2010-09-24) Huawei Proprietary and Confidential iii

About This Document Operation Guide for RTN NE Management
Symbol Description
Indicates a potentially hazardous situation, which if not

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

important points of the main text.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

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

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

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
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.
iv Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Operation Guide for RTN NE Management About This Document
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2010-09-24) Based on Product Version V100R002C01

The second release of the iManager U2000 V100R002C01.
Some bugs in the manual of the previous version are fixed.
Updates in Issue 01 (2010-08-16) Based on Product Version V100R002C01

The first release of the iManager U2000 V100R002C01.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential v

Operation Guide for RTN NE Management Contents
Contents
About This Document...................................................................................................................iii

1 Creating NEs, Links, and Topology Subnets........................................................................1-1
1.1 Creating NEs...................................................................................................................................................1-2
1.1.1 Creating NEs in Batches........................................................................................................................1-2
1.1.2 Creating a Single NE..............................................................................................................................1-4
1.2 Configuring the NE Data.................................................................................................................................1-5
1.2.1 Configuring the NE Data Manually.......................................................................................................1-6
1.2.2 Replicating the NE Data.........................................................................................................................1-7
1.2.3 Uploading the NE Data..........................................................................................................................1-8
1.3 Checking Board Parameters............................................................................................................................1-8
1.4 Creating Links...............................................................................................................................................1-13
1.4.1 Creating Fibers Automatically.............................................................................................................1-13
1.4.2 Automatically Creating Radio Links....................................................................................................1-15
1.4.3 Manually Creating Radio Links...........................................................................................................1-16
1.5 Creating a Topology Subnet..........................................................................................................................1-16
2 DCN Management.....................................................................................................................2-1
2.1 DCN Overview................................................................................................................................................2-3
2.1.1 Background of DCN...............................................................................................................................2-4
2.1.2 DCN Solutions.......................................................................................................................................2-5
2.1.3 HWECC Features and Functions...........................................................................................................2-5
2.1.4 HWECC Application..............................................................................................................................2-6
2.1.5 Basic Concepts of IP over DCC.............................................................................................................2-7
2.1.6 Features and Functions of IP over DCC.................................................................................................2-8
2.1.7 Application of IP over DCC...................................................................................................................2-8
2.1.8 Basic Concepts of OSI over DCC........................................................................................................2-12
2.1.9 Features and Functions of OSI over DCC............................................................................................2-13
2.1.10 Application of OSI over DCC............................................................................................................2-13
2.2 DCN Management Flow...............................................................................................................................2-15
2.3 Configuring ECC Communication................................................................................................................2-16
2.3.1 Modifying the NE ID...........................................................................................................................2-17
2.3.2 Configuring an Extended ECC Communication..................................................................................2-18
2.3.3 Viewing the ECC Route for an NE......................................................................................................2-19
Issue 02 (2010-09-24) Huawei Proprietary and Confidential vii

Contents Operation Guide for RTN NE Management
2.3.4 Adding the Manual ECC Route for an NE...........................................................................................2-20

2.3.5 Customizing Communication Channels Between NEs........................................................................2-20
2.3.6 Configuring Communication for Third-Party Equipment Interconnection..........................................2-21
2.4 Configuring IP Over DCC Communication..................................................................................................2-21
2.4.2 Setting NE Communication Parameters...............................................................................................2-23
2.4.3 Configuring the IP Static Route for an NE..........................................................................................2-23
2.4.5 Viewing the Communication Status of DCC Channel.........................................................................2-24
2.4.6 Querying the OSPF Protocol Status.....................................................................................................2-25
2.4.7 Configuring Proxy ARP.......................................................................................................................2-25
2.5 Configuring OSI Over DCC Communication...............................................................................................2-25
2.5.2 Setting the NSAP Address for an NE...................................................................................................2-27
2.5.3 Configuring the Node Type for an NE.................................................................................................2-28
2.5.4 Configuring the Communication Protocol Stack and LAPD Role for an Optical Port........................2-29
2.5.5 Configuring OSI Tunnel.......................................................................................................................2-29
2.5.7 Querying the Route Information of a Node.........................................................................................2-30
2.5.8 Creating an OSI GNE...........................................................................................................................2-31
2.6 Configuring DCC Transparent Transmission...............................................................................................2-31
2.6.1 Configuring Communication for Third-Party Equipment Interconnection..........................................2-32
2.6.2 Configuring DCC Transparent Transmission Through External Clock Interfaces..............................2-33
2.6.3 Configuring DCC Transparent Transmission Through F1 Data Interfaces.........................................2-35
2.7 Modifying GNE Parameters..........................................................................................................................2-35
2.8 Changing the GNE for NEs...........................................................................................................................2-36
2.9 Configuring Standby GNEs for NEs.............................................................................................................2-37
2.10 Changing a GNE to a Normal NE...............................................................................................................2-38
2.11 Changing a Normal NE to a GNE...............................................................................................................2-39
2.12 Checking GNE Switching Status................................................................................................................2-39
2.13 Testing the Communication Between the U2000 and the GNE..................................................................2-39
2.14 Checking the Network Communication Status...........................................................................................2-40
2.14.1 Overview of the Inband DCN............................................................................................................2-41
2.14.2 Basic Concepts...................................................................................................................................2-42
2.14.3 Application of the Inband DCN.........................................................................................................2-43
2.14.4 Configuring an Inband DCN..............................................................................................................2-43
2.14.4.1 Setting NE Communication Parameters..........................................................................................2-44
2.14.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN....................................................2-45
2.14.4.3 Setting the U2000 Access Parameters.............................................................................................2-45
2.14.4.4 Enabling the Port DCN...................................................................................................................2-46
2.14.4.5 Enabling the Tunnel DCN...............................................................................................................2-47
3 Configuring Clocks....................................................................................................................3-1
viii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

3.1 Clock Configuration Process...........................................................................................................................3-3

3.2 Clock Synchronization Scheme...................................................................................................................... 3-4
3.3 Basic Concepts................................................................................................................................................3-8
3.3.1 Clock Synchronization...........................................................................................................................3-9
3.3.2 SSM Protocol and Clock ID.................................................................................................................3-10
3.3.3 Clock Subnet........................................................................................................................................3-13
3.3.4 Clock Protection...................................................................................................................................3-13
3.4 Viewing Clock Synchronization Status.........................................................................................................3-14
3.5 Viewing the Clock Tracing Status................................................................................................................3-14
3.6 Configuring the Clock Sources.....................................................................................................................3-15
3.7 Configuring Protection for Clock Sources ...................................................................................................3-17
3.8 Configuring Switching Conditions for Clock Sources..................................................................................3-20
3.9 Configuring the Clock Source Reversion......................................................................................................3-20
3.10 Modifying the Parameters of the External Clock Output............................................................................3-21
3.11 Setting the Clock Source Quality................................................................................................................3-22
3.12 Configuring the SSM Output......................................................................................................................3-23
3.13 Configuring the Ethernet Clock Source......................................................................................................3-24
3.14 Viewing the Clock Tracing Status..............................................................................................................3-24
3.15 Checking the Clock Switching Status.........................................................................................................3-25
3.16 Switching a Clock Source...........................................................................................................................3-25
4 Configuring PTP Clock.............................................................................................................4-1

4.1 Introduction to the PTP Clock.........................................................................................................................4-2
4.2 Basic Information............................................................................................................................................4-3
4.3 Application of the PTP Clock......................................................................................................................... 4-6
4.4 Configuration Flow for the PTP Clock...........................................................................................................4-7
4.5 Configuring the PTP Clock.............................................................................................................................4-9
4.5.1 Setting the Frequency Selection Mode.................................................................................................4-10
4.5.2 Setting the PTP System Time...............................................................................................................4-11
4.5.3 Setting the PTP Clock Subnet..............................................................................................................4-11
4.5.4 Setting the Attributes of the External Time Interface..........................................................................4-12
4.5.5 Setting the PTP NE Attributes.............................................................................................................4-13
4.5.6 Creating the PTP Clock Port................................................................................................................4-14
4.5.7 Creating the PTP Clock Service...........................................................................................................4-14
4.5.8 Setting the PTP Packet Period..............................................................................................................4-16
4.5.9 Setting the PTP Clock Port Status........................................................................................................4-17
4.5.10 Setting the Cable Transmitting Wrap.................................................................................................4-18
4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source............................................................4-19
4.5.12 Setting the PTP Clock Source Priority...............................................................................................4-19
5 Configuring Orderwire.............................................................................................................5-1
5.1 Configuring Orderwire....................................................................................................................................5-2
5.2 Configuring F1 Data Port Services................................................................................................................. 5-2
5.2.1 F1 Data Port Services.............................................................................................................................5-2
Issue 02 (2010-09-24) Huawei Proprietary and Confidential ix

5.2.2 Configuring F1 Data Port Services........................................................................................................5-3

5.3 Configuring Asynchronous Data Services......................................................................................................5-4
5.3.1 Asynchronous Data Services..................................................................................................................5-5
5.3.2 Configuring Asynchronous Data Services.............................................................................................5-5
5.4 Configuration Example (Synchronous Data Services RTN 600)....................................................................5-6
5.4.1 Networking Diagram..............................................................................................................................5-7
5.4.2 Service Planning.....................................................................................................................................5-7
5.4.3 Configuration Process............................................................................................................................5-9
5.5 Configuration Example (Asynchronous Data Services RTN 600)...............................................................5-10
5.5.1 Networking Diagram............................................................................................................................5-11
5.5.2 Service Planning...................................................................................................................................5-11
5.5.3 Configuration Process..........................................................................................................................5-13
6 Configuring Environment Monitor Interfaces.....................................................................6-1

6.1 Configuring External Alarms..........................................................................................................................6-2
6.2 Configuration Example (External Alarms RTN 600).....................................................................................6-3
6.2.1 Networking Diagram..............................................................................................................................6-3
6.2.2 Service Planning.....................................................................................................................................6-4
6.2.3 Configuration Process............................................................................................................................6-5
7 Configuring Interfaces (RTN 600)...........................................................................................7-1

7.1 Checking Board Parameters............................................................................................................................7-2
7.2 Configuring the Parameters of Various Ports ................................................................................................7-6
7.2.1 Configuring the Parameters of SDH Interfaces .....................................................................................7-6
7.2.2 Configuring the Parameters of PDH Interfaces .....................................................................................7-8
7.2.3 Setting the Parameters of IF Ports........................................................................................................7-11
7.2.4 Setting the Parameters of ODU Ports...................................................................................................7-17
7.3 Configuring Ethernet Ports............................................................................................................................7-20
7.3.1 Configuring External Ethernet Ports....................................................................................................7-20
7.3.2 Configuring the Internal Port of the Ethernet Board............................................................................7-29
7.3.3 Modifying the Type Field of Jumbo Frames........................................................................................7-36
7.3.4 Modifying the Type Field of QinQ Frames.........................................................................................7-37
7.3.5 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth........................................................7-38
7.4 Disabling an Ethernet Port............................................................................................................................7-39
7.5 Configuring a Service Load Indication.........................................................................................................7-40
8 Configuring Interfaces (RTN 900)...........................................................................................8-1

8.1 Configuring SDH Interfaces............................................................................................................................8-3
8.1.1 Setting the General Attributes of SDH Interfaces..................................................................................8-3
8.1.2 Setting the Advanced Attributes of SDH Interfaces..............................................................................8-4
8.1.3 Querying the Running Status of PPP.....................................................................................................8-4
8.1.4 Resetting the PPP...................................................................................................................................8-5
8.2 Configuring PDH Interfaces............................................................................................................................8-5
8.2.1 Setting General Attributes of PDH Interfaces........................................................................................8-7
x Huawei Proprietary and Confidential Issue 02 (2010-09-24)

8.2.2 Setting the Layer 3 Attributes of PDH Interfaces..................................................................................8-8

8.2.3 Setting the Advanced Attributes of PDH Interfaces.............................................................................. 8-8
8.2.4 Querying the Running Status of PPP..................................................................................................... 8-9
8.2.5 Resetting the PPP...................................................................................................................................8-9
8.3 Configuring Ethernet Interfaces....................................................................................................................8-10
8.3.1 Setting the General Attributes of Ethernet Interfaces..........................................................................8-11
8.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces...........................................................................8-11
8.3.3 Setting the Layer 3 Attributes of an Ethernet Interface........................................................................8-12
8.3.4 Setting the Advanced Attributes of Ethernet Interfaces.......................................................................8-13
8.3.5 Configuring Flow Control....................................................................................................................8-13
8.4 Configuring Microwave Interfaces...............................................................................................................8-14
8.4.1 Setting the General Attributes of Microwave Interfaces......................................................................8-16
8.4.2 Setting the IF Attributes of Microwave Interfaces...............................................................................8-17
8.4.3 Setting the Layer 2 Attributes of Microwave Interfaces......................................................................8-17
8.4.4 Setting the Layer 3 Attributes of Microwave Interfaces......................................................................8-18
8.4.5 Setting the Advanced Attributes of Microwave Interfaces..................................................................8-19
8.4.6 Setting the Parameters of ODU Ports(RTN900V1R1)........................................................................8-19
8.4.7 Setting the Parameters of ODU Ports(RTN900V1R2)........................................................................8-21
8.5 Configuring Serial Interfaces........................................................................................................................8-24
8.5.1 Creating Serial Interfaces.....................................................................................................................8-24
8.5.2 Setting the General Attributes of a Serial Interface.............................................................................8-25
8.5.3 Setting the Layer 3 Attributes of Serial Interfaces...............................................................................8-25
8.5.4 Querying the Running Status of PPP...................................................................................................8-26
8.5.5 Resetting the PPP.................................................................................................................................8-26
8.6 Configuring ML-PPP....................................................................................................................................8-27
8.6.1 Overview of the ML-PPP.....................................................................................................................8-29
8.6.2 Basic Concepts.....................................................................................................................................8-29
8.6.3 ML-PPP Application............................................................................................................................8-30
8.6.4 Creating MP Groups.............................................................................................................................8-31
8.6.5 Configuring Member Interfaces of MP Groups...................................................................................8-31
8.7 Configuring an Ethernet Virtual Interface.....................................................................................................8-32
8.7.1 Setting the General Attributes of Ethernet Virtual Interfaces..............................................................8-32
8.7.2 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces..............................................................8-33
8.8 Configuring an IMA Group...........................................................................................................................8-33
8.8.1 Configuring Bound Channels in an ATM IMA Group........................................................................8-35
8.8.2 Configuring Attributes of an ATM IMA Group..................................................................................8-36
8.8.3 Configuring ATM Interface Attributes................................................................................................8-36
8.8.4 Querying IMA Group States................................................................................................................8-37
8.8.5 Querying IMA Link States...................................................................................................................8-37
8.8.6 Resetting an IMA Group......................................................................................................................8-38
8.8.7 Modifying an IMA Group....................................................................................................................8-38
8.8.8 Deleting an IMA Group.......................................................................................................................8-39
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xi

9 Configuring Radio Links..........................................................................................................9-1

9.1 Radio Link.......................................................................................................................................................9-2
9.2 Configuring the IF/ODU Information of a Radio Link...................................................................................9-2
9.3 Configuring the ATPC Function.....................................................................................................................9-8
9.4 Creating an XPIC Workgroup.......................................................................................................................9-11
9.5 Configuring the Hybrid/AM Attribute..........................................................................................................9-13
9.6 Hop Management..........................................................................................................................................9-13
9.6.1 Introduction to the Hop Management..................................................................................................9-14
9.6.2 Starting HOP Management..................................................................................................................9-14
10 Configuring Board 1+1 Protection......................................................................................10-1

10.1 Querying Board 1+1 Protection Group.......................................................................................................10-2
10.2 Verifying the Board 1+1 Protection Switching...........................................................................................10-2
11 Configuring the IF 1+1 Protection...................................................................................... 11-1

11.1 1+1 HSB......................................................................................................................................................11-2
11.1.1 Feature Description............................................................................................................................11-2
11.1.2 Availability.........................................................................................................................................11-2
11.1.3 Relation with Other Features..............................................................................................................11-3
11.1.4 Realization Principle..........................................................................................................................11-3
11.1.4.1 SDH/PDH Microwave.....................................................................................................................11-4
11.1.4.2 Hybrid Microwave..........................................................................................................................11-6
11.1.5 Planning Guide...................................................................................................................................11-9
11.2 1+1 FD.........................................................................................................................................................11-9
11.2.1 Feature Description..........................................................................................................................11-10
11.2.2 Availability.......................................................................................................................................11-10
11.2.3 Relation with Other Features............................................................................................................11-11
11.2.4 Realization Principle........................................................................................................................11-11
11.2.4.1 SDH/PDH Microwave...................................................................................................................11-11
11.2.4.2 Hybrid Microwave........................................................................................................................11-14
11.2.5 Planning Guide.................................................................................................................................11-17
11.3 1+1 SD.......................................................................................................................................................11-18
11.3.2 Availability.......................................................................................................................................11-19
11.3.3 Relation with Other Features............................................................................................................11-19
11.3.4.1 SDH/PDH Microwave...................................................................................................................11-20
11.3.4.2 Hybrid Microwave........................................................................................................................11-22
11.3.5 Planning Guide.................................................................................................................................11-26
11.4 Creating IF 1+1 Protection........................................................................................................................11-27
11.5 Modifying the Parameters of IF 1+1 Protection........................................................................................11-28
12 Configuring Network Level Protection.............................................................................12-1

12.1 Basic Concept..............................................................................................................................................12-3
xii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

12.1.1 Multiplex Section...............................................................................................................................12-3

12.1.2 MSP Protection Switching Priority....................................................................................................12-4
12.1.3 SNCP Protection................................................................................................................................12-6
12.1.4 N+1 Protection...................................................................................................................................12-9
12.2 Configuring N+1 Protection......................................................................................................................12-10
12.2.2 Availability.......................................................................................................................................12-13
12.2.3.1 2+1 Protection Configuration........................................................................................................12-13
12.2.3.2 3+1 Protection Configuration........................................................................................................12-15
12.2.4 Configuration Guide.........................................................................................................................12-17
12.2.4.1 Configuration Flow.......................................................................................................................12-17
12.2.4.2 Creating REGs...............................................................................................................................12-18
12.2.4.3 Creating an N+1 Protection Group................................................................................................12-21
12.2.4.4 Enabling the N+1 Protection Control Protocol.............................................................................12-23
12.2.4.5 Verifying the N+1 Protection Switching.......................................................................................12-24
12.3 Configuring Linear Multiplex Section Protection.....................................................................................12-25
12.3.1.1 Protection Type.............................................................................................................................12-27
12.3.2 Availability.......................................................................................................................................12-28
12.3.3.1 1+1 Linear MSP............................................................................................................................12-29
12.3.3.2 1:N Linear MSP............................................................................................................................12-31
12.3.4.1 Creating Linear MSP.....................................................................................................................12-32
12.3.4.2 Verifying Linear MSP Switching..................................................................................................12-36
12.3.4.3 Setting an MS Node Number........................................................................................................12-37
12.4 Configuring Two-Fiber Bidirectional Ring MSP......................................................................................12-38
12.4.2 Availability.......................................................................................................................................12-40
12.4.3.1 Configuring the Ring MSP............................................................................................................12-42
12.5 Configuring Sub-Network Connection Protection....................................................................................12-45
12.5.2 Availability.......................................................................................................................................12-47
12.5.4.1 Creating Cross-Connections for SNCP Services..........................................................................12-49
12.5.4.2 Setting SNCP Service Control Attributes.....................................................................................12-53
12.5.4.3 Setting the Automatic Switching Conditions of SNCP Services..................................................12-54
12.5.4.4 Verifying the SNCP Service Switching........................................................................................12-55
12.5.4.5 Converting Non-Protection Services into SNCP Services............................................................12-56
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xiii

12.5.4.6 Converting SNCP Services into Non-Protection Services............................................................12-60

12.6 Configuring MPLS Tunnel Protection......................................................................................................12-60
12.6.1 Introduction to MPLS APS..............................................................................................................12-61
12.6.2 Basic Concepts.................................................................................................................................12-64
12.6.3 MPLS APS Application...................................................................................................................12-65
12.6.4 Creating an MPLS Tunnel Protection Group...................................................................................12-67
12.6.5 Perform MPLS Tunnel Protection Switching..................................................................................12-69
12.6.6 Deleting an MPLS Tunnel Protection Group...................................................................................12-70
12.7 Ethernet Ring Protection...........................................................................................................................12-70
12.7.1 Introduction to Ethernet Ring Protection.........................................................................................12-71
12.7.2 Basic Concepts.................................................................................................................................12-71
12.7.3 Availability.......................................................................................................................................12-74
12.7.4 Function Implementation.................................................................................................................12-74
12.7.5 Application of Ethernet Ring Protection..........................................................................................12-78
12.7.6 Configuring Ethernet Ring Protection..............................................................................................12-79
12.7.6.1 Configuration Rules......................................................................................................................12-80
12.7.6.2 Creating Ethernet Ring Protection................................................................................................12-80
12.7.6.3 Modifying Parameters of Ethernet Ring Protection......................................................................12-80
12.8 Configuring Link Aggregation..................................................................................................................12-81
12.8.1 Overview..........................................................................................................................................12-81
12.8.2 Availability.......................................................................................................................................12-83
12.8.3 Principle...........................................................................................................................................12-84
12.8.4.1 Creating an LAG...........................................................................................................................12-86
12.8.4.2 Modifying LAG Parameters..........................................................................................................12-87
12.8.4.3 Querying Port LACP Packet Statistics..........................................................................................12-87
12.8.4.4 Querying Detailed LAG Information............................................................................................12-88
13 Configuring SDH/PDH Services.........................................................................................13-1

13.1 Numbering Schemes for SDH Timeslots ...................................................................................................13-3
13.2 Configuring E1 Services............................................................................................................................. 13-4
13.3 Configuring Cross-Connections..................................................................................................................13-6
13.3.1 Creating Cross-Connections of Point-to-Point Services....................................................................13-8
13.3.2 Creating Cross-Connections for SNCP Services............................................................................... 13-9
13.3.3 Setting the Automatic Switching Conditions of SNCP Services.....................................................13-14
13.3.4 Deleting the Cross-Connections of a Point-to-Point Service...........................................................13-15
13.3.5 Deleting the Cross-Connections of a Service...................................................................................13-16
13.4 Configuring SNCP Services......................................................................................................................13-17
13.5 Converting Between SNCP and Non-Protection Services........................................................................13-20
13.5.1 Converting Non-Protection Services into SNCP Services...............................................................13-20
13.5.2 Converting SNCP Services into Non-Protection Services...............................................................13-24
13.6 Configuring Overhead Bytes.....................................................................................................................13-24
13.6.1 Configuring RSOHs.........................................................................................................................13-25
xiv Huawei Proprietary and Confidential Issue 02 (2010-09-24)

13.6.2 Configuring VC-4 POHs..................................................................................................................13-26

13.6.3 Configuring VC-3 POHs..................................................................................................................13-30
13.6.4 Configuring VC-12 POHs................................................................................................................13-32
13.7 Configuration Example (Hop Between Two IDU 620s)...........................................................................13-34
13.7.1 Networking Diagram........................................................................................................................13-35
13.7.2 Service Planning...............................................................................................................................13-36
13.7.3 Configuring NE1..............................................................................................................................13-45
13.7.4 Configuring NE2..............................................................................................................................13-49
13.7.5 Configuring NE3..............................................................................................................................13-57
13.7.6 Configuring NE4 .............................................................................................................................13-61
13.7.7 Configuring NE5..............................................................................................................................13-64
13.8 Configuration Example (Hop Between Two IDU 605s)...........................................................................13-64
13.8.3 Configuring NE1..............................................................................................................................13-69
13.8.4 Configuring NE2..............................................................................................................................13-72
13.9 Configuration Example (Hop between the IDU 605 and the IDU 620)....................................................13-76
13.9.3 Configuring NE1 to NE4 .................................................................................................................13-80
13.9.4 Configuring NE5..............................................................................................................................13-80
14 Ethernet Feature(RTN 600)...................................................................................................14-1

14.1 Creating Ethernet Services..........................................................................................................................14-2
14.1.1 Basic Concepts...................................................................................................................................14-3
14.1.1.1 Formats of Ethernet Frames............................................................................................................14-3
14.1.1.2 Internal Ports and External Ports.....................................................................................................14-6
14.1.1.3 Auto-Negotiation.............................................................................................................................14-6
14.1.1.4 Flow Control...................................................................................................................................14-8
14.1.1.5 Encapsulation and Mapping Protocol...........................................................................................14-10
14.1.1.6 Virtual Concatenation...................................................................................................................14-10
14.1.1.7 Tag Attributes................................................................................................................................14-12
14.1.1.8 Bridge............................................................................................................................................14-13
14.1.2 Configuring the Cross-Connections of Ethernet Services................................................................14-17
14.1.2.1 Creating Cross-Connections of Ethernet Services........................................................................14-17
14.1.2.2 Deleting the Cross-Connections of an Ethernet Service...............................................................14-17
14.1.3 Configuring EPL Services................................................................................................................14-18
14.1.3.1 EPL Service Configuration Process..............................................................................................14-19
14.1.3.2 Setting Port Attributes and Bound Paths for an Ethernet Board...................................................14-20
14.1.3.3 Creating Ethernet Line Service.....................................................................................................14-20
14.1.3.4 Testing Ethernet Services..............................................................................................................14-25
14.1.3.5 Deleting an Ethernet Private Line Service....................................................................................14-26
14.1.4 Configuring Ethernet LAN Services................................................................................................14-27
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xv

14.1.4.1 Ethernet LAN Service Configuration Process..............................................................................14-27

14.1.4.3 Creating the Ethernet LAN Service...............................................................................................14-29
14.1.4.4 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge............................14-33
14.1.4.5 Creating the VLAN Filter Table...................................................................................................14-37
14.1.4.7 Deleting an Ethernet LAN Service................................................................................................14-40
14.1.5 Configuring EVPL (QinQ) Services................................................................................................14-41
14.1.5.1 EVPL(QinQ) Service Configuration Process................................................................................14-41
14.1.5.3 Modifying the Type Field of QinQ Frames..................................................................................14-43
14.1.5.4 Creating QinQ Line Services........................................................................................................14-43
14.1.6 Configuration Example (Point-to-Point EPL Services)...................................................................14-49
14.1.6.1 Networking Diagram.....................................................................................................................14-49
14.1.6.2 Service Planning............................................................................................................................14-50
14.1.6.3 Configuring NE1...........................................................................................................................14-52
14.1.6.4 Configuring NE2...........................................................................................................................14-55
14.1.7 Configuration Example (PORT-Shared EVPL Services)................................................................14-56
14.1.7.3 Configuring NE1...........................................................................................................................14-59
14.1.7.4 Configuring NE2 and NE3............................................................................................................14-65
14.1.8 Configuration Example (VCTRUNK-Shared EVPL Services).......................................................14-65
14.1.8.3 Configuring NE1...........................................................................................................................14-69
14.1.8.4 Configuring NE2...........................................................................................................................14-73
14.1.9 Configuration Example (802.1d Bridge-Based EPLAN Services)..................................................14-73
14.1.9.3 Configuring NE1...........................................................................................................................14-77
14.1.9.4 Configuring NE2 and NE3............................................................................................................14-82
14.1.10 Configuration Example (802.1q Bridge-Based EVPLAN Services).............................................14-83
14.1.10.1 Networking Diagram...................................................................................................................14-83
14.1.10.2 Service Planning..........................................................................................................................14-84
14.1.10.3 Configuring NE1.........................................................................................................................14-88
14.1.10.4 Configuring NE2 and NE3..........................................................................................................14-96
14.1.11 Configuration Example (EVPL Services Based on QinQ)............................................................14-96
14.1.12 Configuration Example (EVPLAN Services Based on the IEEE 802.1ad Bridge).......................14-98
14.1.13 Configuring Services Based on the Hybrid Microwave.................................................................14-99
14.1.13.1 Networking Diagram.................................................................................................................14-100
xvi Huawei Proprietary and Confidential Issue 02 (2010-09-24)

14.1.13.2 Service Planning (Microwave Services)...................................................................................14-101

14.1.13.3 Service Planning (Ethernet Services Accessed Through the EMS6 Board).............................14-106
14.1.13.4 Service Planning (Ethernet Services Accessed Through the IFH2 Board)...............................14-110
14.1.13.5 Configuring NE1 (Microwave Services)...................................................................................14-112
14.1.13.6 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board).............................14-116
14.1.13.7 Configuring NE2 (Microwave Services)...................................................................................14-125
14.1.13.8 Configuring NE2 (Ethernet Services Accessed Through the EMS6 Board).............................14-132
14.1.13.9 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board)..............................14-141
14.1.13.10 Configuring NE3 (Ethernet Services).....................................................................................14-142
14.2 Configuring QinQ...................................................................................................................................14-145
14.2.1 Feature Description........................................................................................................................14-146
14.2.2 Basic Concepts...............................................................................................................................14-146
14.2.2.1 Frame Format..............................................................................................................................14-147
14.2.2.2 Network Attributes......................................................................................................................14-148
14.2.2.3 Application of the QinQ Technology in Line Services...............................................................14-149
14.2.2.4 Application of the QinQ Technology in LAN Services..............................................................14-151
14.2.3 Availability.....................................................................................................................................14-154
14.2.4 Relation with Other Features..........................................................................................................14-154
14.2.5 Realization Principle......................................................................................................................14-154
14.2.6 Planning Guide...............................................................................................................................14-156
14.2.6.1 EVPL Services Based on QinQ...................................................................................................14-156
14.2.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge..............................................................14-158
14.2.7 Configuration Guide.......................................................................................................................14-159
14.2.7.1 Configuration Flow (EVPL Services Based on QinQ)...............................................................14-160
14.2.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge)..........................14-161
14.2.7.3 Modifying the Type Field of QinQ Frames................................................................................14-163
14.2.7.4 Creating QinQ Line Services......................................................................................................14-164
14.2.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge..........................14-168
14.3 Configuring Features of Ethernet Ports...................................................................................................14-172
14.3.2 Basic Concepts...............................................................................................................................14-173
14.3.2.1 Auto-Negotiation Function.........................................................................................................14-174
14.3.2.2 Jumbo Frames.............................................................................................................................14-176
14.3.2.3 Flow Control Function................................................................................................................14-176
14.3.3 Availability.....................................................................................................................................14-177
14.3.5.1 Auto-Negotiation Function.........................................................................................................14-178
14.3.5.2 Flow Control Function................................................................................................................14-179
14.3.6 Planning Guide...............................................................................................................................14-180
14.3.7.1 Configuring External Ethernet Ports...........................................................................................14-181
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xvii

14.3.7.2 Modifying the Type Field of Jumbo Frames...............................................................................14-190

14.4 Configuring Encapsulation and Mapping of Ethernet Services..............................................................14-190
14.4.2 Basic Concepts...............................................................................................................................14-192
14.4.2.1 Encapsulation and Mapping Protocols........................................................................................14-192
14.4.2.2 Virtual Concatenation.................................................................................................................14-193
14.4.2.3 LCAS...........................................................................................................................................14-194
14.4.3 Availability.....................................................................................................................................14-194
14.4.5.1 Encapsulation and Mapping........................................................................................................14-195
14.4.5.2 Virtual Concatenation.................................................................................................................14-199
14.4.5.3 LCAS...........................................................................................................................................14-200
14.4.6 Planning Guide...............................................................................................................................14-204
14.4.7 Configuring Guide..........................................................................................................................14-205
14.4.7.1 Configuring the Internal Port of the Ethernet Board...................................................................14-205
14.4.7.2 Configuring LCAS......................................................................................................................14-213
14.5 Configuring VLAN.................................................................................................................................14-214
14.5.2 Basic Concepts...............................................................................................................................14-216
14.5.2.1 Frame Format..............................................................................................................................14-216
14.5.2.2 TAG Attribute.............................................................................................................................14-217
14.5.2.3 Application..................................................................................................................................14-218
14.5.3 Availability.....................................................................................................................................14-219
14.5.6 Planning Guide...............................................................................................................................14-220
14.5.7.1 Configuration Flow.....................................................................................................................14-221
14.5.7.2 Creating Ethernet Line Service...................................................................................................14-223
14.5.8 Configuration Example (PORT-Shared EVPL Service)................................................................14-228
14.5.9 Configuration Example (VCTRUNK-Shared EVPL Service).......................................................14-229
14.6 Configuring Layer 2 Switching...............................................................................................................14-230
14.6.2 Basic Concepts...............................................................................................................................14-232
14.6.2.1 Bridge..........................................................................................................................................14-233
14.6.2.2 STP/RSTP...................................................................................................................................14-236
14.6.2.3 IGMP Snooping...........................................................................................................................14-237
14.6.2.4 Broadcast Packet Suppression.....................................................................................................14-239
14.6.3 Availability.....................................................................................................................................14-240
xviii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

14.6.5.1 Bridge..........................................................................................................................................14-241
14.6.5.2 STP/RSTP...................................................................................................................................14-241
14.6.5.3 IGMP Snooping...........................................................................................................................14-246
14.6.6 Planning Guide...............................................................................................................................14-248
14.6.8 Creating the Ethernet LAN Service................................................................................................14-249
14.6.9 Modifying the Mounted Port of a Bridge.......................................................................................14-254
14.6.10 Creating the VLAN Filter Table..................................................................................................14-257
14.6.11 Creating the Entry of a MAC Address Table Manually ..............................................................14-259
14.6.12 Modifying the Aging Time of the MAC Address Table Entry....................................................14-260
14.6.13 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry...................14-261
14.6.14 Configuring the Spanning Tree Protocol ....................................................................................14-262
14.6.15 Querying the Running Information About the Spanning Tree Protocol......................................14-267
14.6.16 Configuring the IGMP Snooping Protocol...................................................................................14-267
14.6.17 Querying the Running Information About the IGMP Snooping Protocol ..................................14-269
14.6.18 Modifying the Aging Time of the Multicast Table Item..............................................................14-270
14.6.19 Querying the Multicast Router Port.............................................................................................14-271
14.6.20 Configuring the Static Multicast Table Item................................................................................14-271
14.6.21 Querying the Multicast Table Item..............................................................................................14-272
14.7 Configuring QoS.....................................................................................................................................14-272
14.7.2 Basic Concepts...............................................................................................................................14-274
14.7.2.1 Flow Classification......................................................................................................................14-275
14.7.2.2 CAR.............................................................................................................................................14-275
14.7.2.3 CoS..............................................................................................................................................14-276
14.7.2.4 Traffic Shaping............................................................................................................................14-277
14.7.3 Availability.....................................................................................................................................14-278
14.7.5.1 CAR.............................................................................................................................................14-279
14.7.5.2 Traffic Shaping............................................................................................................................14-281
14.7.5.3 Egress Queue Scheduling............................................................................................................14-282
14.7.6 Planning Guide...............................................................................................................................14-284
14.7.7.1 Creating a Flow...........................................................................................................................14-286
14.7.7.2 Creating the CAR........................................................................................................................14-289
14.7.7.3 Creating the CoS.........................................................................................................................14-292
14.7.7.4 Binding the CAR/CoS.................................................................................................................14-294
14.7.7.5 Configuring the Traffic Shaping.................................................................................................14-295
14.7.7.6 Configuring the CoS of the IFH2 Board.....................................................................................14-297
14.7.7.7 Setting the Queue Scheduling Mode...........................................................................................14-298
14.7.7.8 Creating a Flow by Using a Template.........................................................................................14-299
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xix

14.7.7.9 Modifying CAR Parameters........................................................................................................14-300

14.7.7.10 Modifying CoS Parameters.......................................................................................................14-300
14.7.8 Configuring the Clock Sources......................................................................................................14-301
14.7.9 Configuring the Ethernet Clock Source.........................................................................................14-303
15 Ethernet Feature(RTN 900)...................................................................................................15-1

15.1 Configuring the QoS Policy........................................................................................................................15-2
15.1.1 Overview of the QoS..........................................................................................................................15-2
15.1.2 Basic Concepts...................................................................................................................................15-3
15.1.2.1 DiffServ...........................................................................................................................................15-4
15.1.2.2 HQoS...............................................................................................................................................15-6
15.1.3 Application of the QoS.......................................................................................................................15-7
15.1.3.1 Tunnel-Based QoS..........................................................................................................................15-7
15.1.3.2 QoS Policy.......................................................................................................................................15-7
15.1.4 Configuring the DiffServ Domain......................................................................................................15-8
15.1.4.1 Creating a DiffServ Domain...........................................................................................................15-8
15.1.4.2 Modifying a DiffServ Domain......................................................................................................15-10
15.1.4.3 Deleting a DiffServ Domain.........................................................................................................15-11
15.1.5 Configuring the Port Policy..............................................................................................................15-11
15.1.5.1 Creating the Port Policy................................................................................................................15-11
15.1.5.2 Modifying the Port Policy.............................................................................................................15-12
15.1.5.3 Deleting the Port Policy................................................................................................................15-13
15.1.6 Creating the CAR Policy..................................................................................................................15-13
15.1.7 Configuring the V-UNI Ingress Policy............................................................................................15-14
15.1.7.1 Creating the WFQ Scheduling Policy...........................................................................................15-15
15.1.7.2 Creating the V-UNI Ingress Policy...............................................................................................15-16
15.1.7.3 Modifying the V-UNI Ingress Policy............................................................................................15-17
15.1.7.4 Querying the V-UNI Ingress Policy-Applied Object....................................................................15-17
15.1.7.5 Deleting the V-UNI Ingress Policy...............................................................................................15-18
15.1.8 Configuring the ATM CoS Mapping...............................................................................................15-18
15.1.9 Configuring the ATM Policy...........................................................................................................15-19
15.1.9.1 Creating the ATM Policy..............................................................................................................15-20
15.1.9.2 Modifying the ATM Policy...........................................................................................................15-21
15.1.9.3 Querying the ATM Policy-Applied Object...................................................................................15-21
15.1.9.4 Deleting the ATM Policy..............................................................................................................15-22
15.2 Configuring an Ethernet Service...............................................................................................................15-22
15.2.1 Basic Concepts.................................................................................................................................15-23
15.2.1.1 E-Line Service...............................................................................................................................15-23
15.2.1.2 E-LAN Service..............................................................................................................................15-27
15.2.1.3 E-AGGR Service...........................................................................................................................15-27
15.2.2 Configuring an E-Line Service(RTN 900 V100R001)....................................................................15-28
15.2.2.1 Configuration Flow for the E-Line Service...................................................................................15-29
15.2.2.2 Creating a UNI-UNI E-Line Service.............................................................................................15-32
xx Huawei Proprietary and Confidential Issue 02 (2010-09-24)

15.2.2.3 Creating a UNI-NNI E-Line Service Carried by a Port................................................................15-33

15.2.2.4 Creating a UNI-NNI E-Line Service Carried by a PW.................................................................15-33
15.2.2.5 Creating a QinQ Link....................................................................................................................15-34
15.2.2.6 Creating a UNI-NNI E-Line Service Carried by the QinQ Link..................................................15-35
15.2.2.7 Modifying an E-Line Service........................................................................................................15-36
15.2.2.8 Deleting an E-Line Service...........................................................................................................15-37
15.2.3 Configuring an E-Line Service (RTN 900 V100R002)...................................................................15-37
15.2.3.1 Configuration Flow for the E-Line Service...................................................................................15-38
15.2.3.2 Creating a UNI-UNI E-Line Service.............................................................................................15-39
15.2.3.4 Creating a UNI-NNI E-Line Service Carried by the QinQ Link..................................................15-41
15.2.3.5 Modifying an E-Line Service........................................................................................................15-41
15.2.3.6 Deleting an E-Line Service...........................................................................................................15-42
15.2.4 Configuring an E-LAN Service........................................................................................................15-42
15.2.4.1 Configuration Flow for E-LAN Service........................................................................................15-43
15.2.4.3 Creating an E-LAN Service..........................................................................................................15-45
15.2.4.4 Managing the Blacklist..................................................................................................................15-47
15.2.4.5 Setting the Broadcast Storm Suppression.....................................................................................15-48
15.2.4.6 Modifying E-LAN Service............................................................................................................15-49
15.2.4.7 Deleting E-LAN Service...............................................................................................................15-49
15.2.5 Configuring an E-AGGR Service....................................................................................................15-50
15.2.5.1 Configuration Flow for the E-AGGR Service...............................................................................15-50
15.2.5.2 Creating an E-AGGR Service.......................................................................................................15-52
15.2.5.3 Modifying an E-AGGR Service....................................................................................................15-53
15.2.5.4 Deleting an E-AGGR Service.......................................................................................................15-53
15.3 Configuring Port Mirroring.......................................................................................................................15-54
16 Configuring Cross-Polarization Interference Cancellation...........................................16-1

16.1 Feature Description.....................................................................................................................................16-2
16.2 Availability..................................................................................................................................................16-2
16.3 Realization Principle...................................................................................................................................16-3
16.4 Creating an XPIC Workgroup.....................................................................................................................16-3
17 Configuring Automatic Transmit Power Control Function...........................................17-1

17.2 Availability..................................................................................................................................................17-3
17.4 Configuring the ATPC Function.................................................................................................................17-5
18 Configuring Hybrid Microwave.........................................................................................18-1

18.2 Basic Concepts............................................................................................................................................18-2
18.2.1 Service Transmission Mode...............................................................................................................18-3
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxi

18.2.2 AM..................................................................................................................................................... 18-3

18.2.3 Working Mode...................................................................................................................................18-5
18.2.4 QoS Control for Ethernet Services.....................................................................................................18-6
18.3 Availability..................................................................................................................................................18-7
18.5 Configuration Guide....................................................................................................................................18-9
19 Configuring the MSTP..........................................................................................................19-1

19.1 Overview of the MSTP...............................................................................................................................19-3
19.2 Basic Concepts............................................................................................................................................19-6
19.3 MSTP Application.......................................................................................................................................19-8
19.4 Configuring a Port Group............................................................................................................................19-9
19.5 Configuring Bridge Parameters...................................................................................................................19-9
19.6 Configuring CIST and MSTI Parameters..................................................................................................19-10
19.7 Querying the CIST Running Information.................................................................................................19-11
19.8 Configuring Protocol Transfer for Ports...................................................................................................19-11
20 Configuring the Control Plane............................................................................................20-1

20.1 Basic Concepts............................................................................................................................................20-3
20.1.1 IGP-ISIS Protocol..............................................................................................................................20-3
20.1.2 MPLS-LDP Protocol..........................................................................................................................20-4
20.1.3 MPLS-RSVP Protocol........................................................................................................................20-6
20.1.4 ARP Protocol......................................................................................................................................20-7
20.2 Configuring the IGP-ISIS Protocol...........................................................................................................20-10
20.2.1 Setting Node Attributes....................................................................................................................20-10
20.2.2 Setting Port Attributes......................................................................................................................20-11
20.2.3 Configuring Parameters of Route Importing....................................................................................20-11
20.2.4 Querying the Link TE Information..................................................................................................20-12
20.3 Configuring the MPLS-LDP Protocol.......................................................................................................20-12
20.3.1 Creating MPLS-LDP Peer Entities..................................................................................................20-12
20.3.2 Configuring the MPLS-LDP Protocol..............................................................................................20-13
20.4 Configuring the MPLS-RSVP Protocol....................................................................................................20-13
20.5 Configuring the OSPF Protocol................................................................................................................20-14
20.5.1 Setting Node Attributes....................................................................................................................20-14
20.5.2 Setting Port Attributes......................................................................................................................20-15
20.5.3 Configuring Parameters of Route Importing....................................................................................20-16
20.5.4 Querying the Link TE Information..................................................................................................20-16
20.6 Configuring the MP-BGP..........................................................................................................................20-17
20.7 Configuring Static Routes.........................................................................................................................20-17
20.8 Configuring the Address Parse..................................................................................................................20-18
21 Configuring an MPLS Tunnel.............................................................................................21-1

21.1 Basic Concepts............................................................................................................................................21-2
21.1.1 MPLS and MPLS Tunnel...................................................................................................................21-2
xxii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

21.1.2 Application of the MPLS Tunnel.......................................................................................................21-2

21.2 Configuring an MPLS Tunnel.....................................................................................................................21-4
21.2.1 Configuring Basic Attributes of the MPLS........................................................................................21-4
21.2.2 Creating an MPLS Tunnel..................................................................................................................21-5
21.2.3 Deleting an MPLS Tunnel..................................................................................................................21-6
21.3 Querying the Tunnel Label Information.....................................................................................................21-6
22 Configuring an IP Tunnel....................................................................................................22-1
22.1 IP Tunnel.....................................................................................................................................................22-2
22.2 Configuring a UDP PW Port.......................................................................................................................22-2
22.3 Creating IP Tunnels.....................................................................................................................................22-3
22.4 Deleting IP Tunnels.....................................................................................................................................22-3
23 Configuring a GRE Tunnel..................................................................................................23-1

23.1 GRE Tunnel.................................................................................................................................................23-2
23.2 Creating GRE Tunnels................................................................................................................................23-2
23.3 Deleting GRE Tunnels................................................................................................................................23-3
24 Configuring an MPLS PW....................................................................................................24-1

24.1 Querying an MPLS PW...............................................................................................................................24-2
24.2 Querying QoS-Related Parameters of an MPLS PW..................................................................................24-2
24.3 Querying the PW Label Information...........................................................................................................24-2
25 Configuring CES Services....................................................................................................25-1

25.1 CES Service Type.......................................................................................................................................25-2
25.2 Configuration Flow of CES Services..........................................................................................................25-5
25.3 Configuring a CES Service.........................................................................................................................25-7
25.3.1 Creating a UNI-UNI CES Service.....................................................................................................25-8
25.3.2 Creating a UNI-NNI CES Service.....................................................................................................25-8
25.3.3 Deleting a CES Service....................................................................................................................25-10
26 Configuring an ATM Service...............................................................................................26-1

26.1 Basic Concepts............................................................................................................................................26-2
26.1.1 IMA....................................................................................................................................................26-2
26.1.2 Application of the IMA......................................................................................................................26-3
26.1.3 ATM Service......................................................................................................................................26-4
26.1.4 ATM Traffic.......................................................................................................................................26-5
26.2 ATM Service Configuration Flow..............................................................................................................26-7
26.3 Configuring an IMA Group.......................................................................................................................26-12
26.3.1 Configuring Bound Channels in an ATM IMA Group....................................................................26-14
26.3.2 Configuring Attributes of an ATM IMA Group..............................................................................26-15
26.3.3 Configuring ATM Interface Attributes............................................................................................26-15
26.3.4 Querying IMA Group States............................................................................................................26-16
26.3.5 Querying IMA Link States...............................................................................................................26-16
26.3.6 Resetting an IMA Group..................................................................................................................26-17
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxiii

26.3.7 Modifying an IMA Group................................................................................................................26-17

26.3.8 Deleting an IMA Group................................................................................................................... 26-18
26.4 Configuring the ATM Service...................................................................................................................26-18
26.4.1 Creating ATM Services....................................................................................................................26-19
26.4.2 Modifying ATM Services................................................................................................................ 26-22
26.4.3 Deleting ATM Services....................................................................................................................26-22
27 Configuring the BFD.............................................................................................................27-1

27.1 Overview of the BFD..................................................................................................................................27-2
27.2 Basic Concepts............................................................................................................................................27-2
27.3 Creating a BFD Session..............................................................................................................................27-3
27.4 Configuring Parameters of the BFD Session..............................................................................................27-3
27.5 Querying the BFD Session Information......................................................................................................27-4
27.6 Deleting a BFD Session..............................................................................................................................27-4
28 Configuring the IGMP Snooping.......................................................................................28-1

28.1 Overview of the IGMP Snooping................................................................................................................28-3
28.2 Basic Concepts............................................................................................................................................28-4
28.3 Application of the IGMP Snooping............................................................................................................28-6
28.4 Configuring the IGMP Snooping Parameters.............................................................................................28-7
28.5 Configuring the Router Management..........................................................................................................28-8
28.6 Configuring the Route Member Port Management.....................................................................................28-8
28.7 Configuring the Packet Statistics................................................................................................................28-9
29 OAM Management................................................................................................................29-1
29.1 Configuring ETH OAM..............................................................................................................................29-2
29.1.1 Feature Introduction...........................................................................................................................29-2
29.1.2 Basic Concept.....................................................................................................................................29-3
29.1.2.1 IEEE 802.1ag OAM Management..................................................................................................29-4
29.1.2.2 IEEE 802.1ag OAM Operation.......................................................................................................29-7
29.1.2.3 IEEE 802.3ah OAM Operations......................................................................................................29-8
29.1.3 Availability.........................................................................................................................................29-9
29.1.4 Function Implementation................................................................................................................. 29-10
29.1.4.1 802.1ag OAM................................................................................................................................29-10
29.1.4.2 802.3ah OAM................................................................................................................................29-14
29.1.5 Using the IEEE 802.1ag OAM.........................................................................................................29-23
29.1.5.1 Creating MDs................................................................................................................................29-24
29.1.5.2 Creating MAs................................................................................................................................29-25
29.1.5.3 Creating MPs.................................................................................................................................29-26
29.1.5.4 Performing a Continuity Check.....................................................................................................29-27
29.1.5.5 Performing a Loopback Check......................................................................................................29-28
29.1.5.6 Performing a Link Trace Check....................................................................................................29-29
29.1.5.7 Activating the AIS(RTN 600).......................................................................................................29-31
29.1.5.8 Performing a Ping Test(RTN 600)................................................................................................29-31
xxiv Huawei Proprietary and Confidential Issue 02 (2010-09-24)

29.1.5.9 Performing Performance Detection(RTN 600).............................................................................29-32

29.1.6 Using the IEEE 802.3ah OAM.........................................................................................................29-33
29.1.6.1 Enabling the Auto-Discovery Function of OAM..........................................................................29-33
29.1.6.2 Enabling the Link Event Notification...........................................................................................29-34
29.1.6.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold................................29-35
29.1.6.4 Performing the Remote Loopback................................................................................................29-37
29.1.6.5 Enabling the Self-Loop Detection (RTN 600)..............................................................................29-38
29.2 Configuring the MPLS OAM....................................................................................................................29-38
29.2.1 Overview of the MPLS OAM..........................................................................................................29-39
29.2.2 Basic Concepts.................................................................................................................................29-39
29.2.3 Application of the MPLS OAM.......................................................................................................29-41
29.2.4 Enabling the MPLS OAM of a Tunnel............................................................................................29-42
29.2.5 Setting the MPLS OAM Parameters of a Tunnel.............................................................................29-42
29.2.6 Starting the CV/FFD for a Tunnel....................................................................................................29-43
29.2.7 Performing an LSP Ping Test...........................................................................................................29-44
29.2.8 Performing an LSP Traceroute Test.................................................................................................29-45
29.3 Configuring the PW OAM........................................................................................................................29-46
29.3.1 Overview of the PW OAM...............................................................................................................29-46
29.3.2 Basic Concepts.................................................................................................................................29-46
29.3.3 Application of the PW OAM...........................................................................................................29-47
29.3.4 Performing the PW Ping Test...........................................................................................................29-47
29.4 Configuring ATM OAM...........................................................................................................................29-48
29.4.1 Overview of the ATM OAM............................................................................................................29-49
29.4.2 Basic Concepts.................................................................................................................................29-49
29.4.3 Application of the ATM OAM.........................................................................................................29-50
29.4.4 Setting Segment End Attribute.........................................................................................................29-51
29.4.5 Setting the CC Activation Status......................................................................................................29-52
29.4.6 Setting Remote Loopback Test........................................................................................................29-53
29.4.7 Setting Local Loopback ID..............................................................................................................29-53
30 Configuring Link State Pass Through...............................................................................30-1

30.2 Availability..................................................................................................................................................30-4
30.3.1 Point-to-Point Service(RTN 600).......................................................................................................30-4
30.3.2 Point-to-Multipoint Service(RTN 600)..............................................................................................30-6
30.4 LPT Configuration....................................................................................................................................30-10
31 Configuring Remote Monitoring Feature.........................................................................31-1

31.2 Basic Concepts............................................................................................................................................31-2
31.2.1 SNMP.................................................................................................................................................31-2
31.2.2 RMON Management Groups.............................................................................................................31-3
31.2.3 List of RMON Alarm Entries and RMON Performance Entries.......................................................31-5
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxv

31.3 Availability..................................................................................................................................................31-7
31.5.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port...................................31-10
31.5.2 Configuring an Alarm Group for an Ethernet Port.......................................................................... 31-10
31.5.3 Configuring a History Control Group..............................................................................................31-11
31.5.4 Browsing the Performance Data in the History Group of an Ethernet Port.....................................31-11
31.5.5 Setting Performance Monitoring Status for an Ethernet Port.......................................................... 31-12
32 Configuring Synchronous Ethernet....................................................................................32-1

32.2 Availability..................................................................................................................................................32-2
33 Modifying the Configuration Data.....................................................................................33-1

33.1 Modifying NE Attributes............................................................................................................................33-2
33.1.1 Modifying the NE ID.........................................................................................................................33-2
33.1.2 Modifying the NE Name....................................................................................................................33-3
33.1.3 Deleting NEs......................................................................................................................................33-3
33.1.4 Modifying GNE Parameters...............................................................................................................33-4
33.1.5 Changing the GNE for NEs................................................................................................................33-5
33.2 Modifying the Board Configuration Data...................................................................................................33-6
33.2.1 Adding Boards....................................................................................................................................33-6
33.2.2 Deleting Boards..................................................................................................................................33-7
33.2.3 Modifying Board Configuration Parameters......................................................................................33-8
33.3 Modifying the Fiber Configuration Data....................................................................................................33-8
33.3.1 Modifying Fiber/Cable Information...................................................................................................33-9
33.3.2 Deleting Fibers...................................................................................................................................33-9
33.3.3 Deleting DCN Communication Cables............................................................................................33-10
33.4 Modifying the Service Configuration Data...............................................................................................33-10
33.4.1 Modifying SDH Services.................................................................................................................33-11
33.4.2 Deleting SDH Services.....................................................................................................................33-12
33.4.3 Deleting EPL Services..................................................................................................................... 33-13
33.4.4 Deleting EVPL Services...................................................................................................................33-13
33.4.5 Deleting EPLAN Services................................................................................................................33-14
33.4.6 Converting a Normal Service to an SNCP Service..........................................................................33-15
33.4.7 Converting an SNCP Service to a Normal Service..........................................................................33-16
34 Common Maintenance Operations.....................................................................................34-1

34.1 Checking the Network Communication Status...........................................................................................34-3
34.2 Turning On and Off a Laser........................................................................................................................34-3
34.3 Setting a Scheduled Task............................................................................................................................34-4
34.4 Checking Networkwide Maintenance Status..............................................................................................34-5
xxvi Huawei Proprietary and Confidential Issue 02 (2010-09-24)

34.4.1 Checking Path Loopback Status.........................................................................................................34-6

34.4.2 Checking Port Laser Status................................................................................................................34-6
34.4.3 Checking Path Loading Status...........................................................................................................34-7
34.4.4 Checking Path Alarm Reversion Status.............................................................................................34-8
34.4.5 Checking Path Alarm Suppression Status..........................................................................................34-9
34.4.6 Checking the DCC Enabling Status.................................................................................................34-10
34.5 Checking Protection Switching Status......................................................................................................34-10
34.5.1 Checking the SNCP Service Switching Status.................................................................................34-11
34.5.2 Checking Linear MSP Switching Status..........................................................................................34-11
34.5.3 Checking 1+1 Board Switching Status.............................................................................................34-12
34.5.4 Checking the Switching Status of 1+1 Intermediate Frequency Protection.....................................34-12
34.5.5 Check the Switching Status of the N+1 Protection..........................................................................34-13
34.5.6 Checking GNE Switching Status.....................................................................................................34-13
34.5.7 Checking the Clock Switching Status..............................................................................................34-14
34.6 Resetting Boards.......................................................................................................................................34-14
34.6.1 Reset.................................................................................................................................................34-15
34.6.2 Resetting the SCC Board..................................................................................................................34-15
34.6.3 Resetting a Non-SCC Board............................................................................................................34-15
34.6.4 Resetting a Board.............................................................................................................................34-16
34.7 Performing a Loopback.............................................................................................................................34-16
34.7.1 Setting a Loopback for an SDH Interface........................................................................................34-17
34.7.2 Setting a Loopback for a PDH Interface..........................................................................................34-19
34.7.3 Setting a Loopback for an Ethernet Interface...................................................................................34-20
34.7.4 Setting a Loopback for an IF Interface.............................................................................................34-21
34.7.5 Setting a Loopback for an ODU Interface........................................................................................34-23
34.7.6 Setting a Loopback for a Digital Interface.......................................................................................34-24
34.7.7 Setting a Loopback for a VC4 Path..................................................................................................34-25
34.7.8 Setting a Loopback for a VC3 Path..................................................................................................34-27
34.8 Setting Automatic Laser Shutdown...........................................................................................................34-28
34.9 Disabling Service-Affecting Settings Automatically................................................................................34-29
34.10 Performing a PRBS Test.........................................................................................................................34-29
34.11 Diagnosing Ethernet Protocol Faults.......................................................................................................34-30
34.12 Checking the Network Communication Status.......................................................................................34-31
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxvii

Operation Guide for RTN NE Management Figures
Figures
Figure 2-1 DCN network......................................................................................................................................2-3

Figure 2-2 Positions of DCC bytes in SDH overheads........................................................................................2-5
Figure 2-3 Networking that involves only Huawei equipment............................................................................2-6
Figure 2-4 Networking that involves Huawei equipment and third-party equipment..........................................2-7
Figure 2-5 Gateway NE mode..............................................................................................................................2-8
Figure 2-6 Gateway NE mode (by default gateway)............................................................................................2-9
Figure 2-7 Direct connection mode (by static routes)........................................................................................2-10
Figure 2-8 Direct connection mode through a router (by static routes).............................................................2-11
Figure 2-9 Format of a simple NSAP address....................................................................................................2-12
Figure 2-10 Format of a complicated NSAP address.........................................................................................2-12
Figure 2-11 Third-party equipment forwarding OAM information of Huawei equipment...............................2-14
Figure 2-12 Huawei equipment forwarding OAM information of third-party equipment.................................2-15
Figure 2-13 DCN management flow..................................................................................................................2-16
Figure 2-14 External clock interfaces used to transparently transmit DCC information (example)..................2-33
Figure 2-15 External clock interfaces used to transparently transmit DCC information (example)..................2-34
Figure 2-16 Inband DCN networking mode.......................................................................................................2-41
Figure 2-17 Inband networking scheme.............................................................................................................2-42
Figure 2-18 Outband networking scheme..........................................................................................................2-43
Figure 3-1 Configuration flow when SSM protocol is disabled..........................................................................3-3
Figure 3-2 Configuration flow when standard SSM protocol is enabled.............................................................3-3
Figure 3-3 Configuration flow when extended SSM protocol is enabled............................................................3-3
Figure 3-4 Clock synchronization scheme for a chain network...........................................................................3-4
Figure 3-5 Clock synchronization scheme for a tree network..............................................................................3-5
Figure 3-6 Clock synchronization scheme for a ring network (the entire ring network line is an SDH line)
...............................................................................................................................................................................3-6
Figure 3-7 Clock synchronization scheme for a ring network (not the entire ring network line is an SDH line)
...............................................................................................................................................................................3-7
Figure 3-8 Clock synchronization scheme for networking with convergence at tributary ports.........................3-8
Figure 3-9 Clock synchronization......................................................................................................................3-10
Figure 4-1 Architecture of the IEEE 1588V2 clock.............................................................................................4-4
Figure 4-2 Master-slave synchronization process................................................................................................4-5
Figure 4-3 Networking diagram for typical application of the PTP clock...........................................................4-7
Figure 4-4 Configuration flow for the PTP clock................................................................................................4-8
Figure 5-1 Configuring the F1 data port service..................................................................................................5-3
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxix

Figures Operation Guide for RTN NE Management
Figure 5-2 Networking diagram...........................................................................................................................5-7

Figure 5-3 Timeslot allocation of synchronous data services..............................................................................5-8
Figure 5-4 Networking diagram.........................................................................................................................5-11
Figure 5-5 Timeslot allocation diagram ............................................................................................................5-12
Figure 6-1 Networking diagram...........................................................................................................................6-3
Figure 8-1 Procedure for configuring a PDH interface........................................................................................8-6
Figure 8-2 Procedure for configuring an microwave interface..........................................................................8-15
Figure 8-3 Procedure for configuring an MP group...........................................................................................8-28
Figure 8-4 ML-PPP packet format.....................................................................................................................8-30
Figure 8-5 ML-PPP application scenario...........................................................................................................8-31
Figure 8-6 IMA group configuration flow.........................................................................................................8-34
Figure 9-1 Classification of Radio Stations.........................................................................................................9-2
Figure 9-2 Radio link.........................................................................................................................................9-14
Figure 11-1 1+1 HSB protection........................................................................................................................11-2
Figure 11-2 1+1 HSB realization principle (before the switching, in the transmit direction)...........................11-4
Figure 11-3 1+1 HSB realization principle (before the switching, in the receive direction).............................11-4
Figure 11-4 1+1 HSB realization principle (after the switching, in the receive direction)................................11-5
Figure 11-5 1+1 HSB realization principle (after the switching, in the transmit direction)..............................11-5
Figure 11-6 1+1 HSB realization principle (before the switching, in the transmit direction)...........................11-6
Figure 11-7 1+1 HSB realization principle (before the switching, in the receive direction).............................11-7
Figure 11-8 1+1 HSB realization principle (after the switching, in the receive direction)................................11-8
Figure 11-9 1+1 HSB realization principle (after the switching, in the transmit direction)..............................11-8
Figure 11-10 1+1 FD protection.......................................................................................................................11-10
Figure 11-11 1+1 FD realization principle (before the switching, in the transmit direction)..........................11-12
Figure 11-12 1+1 FD realization principle (before the switching, in the receive direction)............................11-12
Figure 11-13 1+1 FD HSB realization principle (after the switching, in the receive direction)......................11-13
Figure 11-14 1+1 FD HSM realization principle (after the switching, in the receive direction).....................11-13
Figure 11-15 1+1 FD realization principle (before the switching, in the transmit direction)..........................11-14
Figure 11-16 1+1 FD realization principle (before the switching, in the receive direction)............................11-15
Figure 11-17 1+1 HSB realization principle (after the switching, in the transmit direction)..........................11-16
Figure 11-18 1+1 FD HSB realization principle (after the switching, in the receive direction)......................11-16
Figure 11-19 1+1 FD HSM realization principle (after the switching, in the receive direction).....................11-17
Figure 11-20 1+1 SD protection.......................................................................................................................11-18
Figure 11-21 1+1 SD realization principle (before the switching, in the transmit direction)..........................11-20
Figure 11-22 1+1 SD realization principle (before the switching, in the receive direction)............................11-21
Figure 11-23 1+1 SD HSB realization principle (after the switching, in the receive direction)......................11-21
Figure 11-24 1+1 SD HSB realization principle (after the switching, in the transmit direction)....................11-22
Figure 11-25 1+1 SD HSM realization principle (after the switching, in the receive direction).....................11-22
Figure 11-26 1+1 SD realization principle (before the switching, in the transmit direction)..........................11-23
Figure 11-27 1+1 SD realization principle (before the switching, in the receive direction)............................11-24
Figure 11-28 1+1 SD HSB realization principle (after the switching, in the receive direction)......................11-25
Figure 11-29 1+1 SD HSB realization principle (after the switching, in the transmit direction)....................11-25
xxx Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Figure 11-30 1+1 SD HSM realization principle (after the switching, in the receive direction).....................11-26
Figure 12-1 Multiplex section schematic diagram.............................................................................................12-4
Figure 12-2 SNCP service pair...........................................................................................................................12-7
Figure 12-3 SNCP service..................................................................................................................................12-7
Figure 12-4 N+1 protection .............................................................................................................................12-11
Figure 12-5 Realization principle of 2+1 protection (before the switching)....................................................12-14
Figure 12-6 Realization principle of 2+1 protection (after the switching).......................................................12-14
Figure 12-7 Realization principle of the 3+1 protection (before the switching)..............................................12-15
Figure 12-8 Realization principle of the 3+1 protection (after the switching).................................................12-16
Figure 12-9 Configuration flow for the N+1 protection mode.........................................................................12-18
Figure 12-10 1+1 linear MSP ..........................................................................................................................12-26
Figure 12-11 1:N linear MSP ..........................................................................................................................12-27
Figure 12-12 Realization principle of 1+1 linear MSP (before the switching)................................................12-29
Figure 12-13 Realization principle of 1+1 linear MSP (after the switching, in the single-ended mode)........ 12-30
Figure 12-14 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended mode)...........12-30
Figure 12-15 Realization principle of 1:1 linear MSP (before the switching).................................................12-31
Figure 12-16 Realization principle of 1:1 linear MSP (after the switching)....................................................12-31
Figure 12-17 Two-fiber bidirectional MSP ring.............................................................................................. 12-39
Figure 12-18 Realization principle of the two-fiber bidirectional ring MSP (before the switching)...............12-40
Figure 12-19 Realization principle of the two-fiber bidirectional ring MSP (after the switching)..................12-41
Figure 12-20 Sub-Network Connection Protection..........................................................................................12-46
Figure 12-21 SNCP service pair.......................................................................................................................12-47
Figure 12-22 SNCP realization principle (before the switching).....................................................................12-48
Figure 12-23 SNCP realization principle (after the switching)........................................................................12-48
Figure 12-24 MPLS APS 1+1 protection.........................................................................................................12-62
Figure 12-25 MPLS APS 1:1 protection..........................................................................................................12-63
Figure 12-26 MPLS APS 1+1 protection.........................................................................................................12-66
Figure 12-27 MPLS APS 1:1 protection..........................................................................................................12-66
Figure 12-28 R-APS format.............................................................................................................................12-72
Figure 12-29 ERPS switching process (upon a fault not on the RPL link)......................................................12-76
Figure 12-30 ERPS switching process (upon a fault on the RPL link)............................................................12-77
Figure 12-31 Ethernet ring protection switching............................................................................................. 12-79
Figure 12-32 Link aggregation group.............................................................................................................. 12-82
Figure 12-33 Application of the LACP protocol..............................................................................................12-84
Figure 12-34 Application of the link aggregation group..................................................................................12-85
Figure 13-1 Numbering VC-12 timeslots by order............................................................................................13-3
Figure 13-2 Numbering VC-12 timeslots in the interleaved scheme ................................................................13-4
Figure 13-3 Chain network.................................................................................................................................13-7
Figure 13-4 SNCP ring with unprotected chain...............................................................................................13-19
Figure 13-5 Networking diagram.....................................................................................................................13-35
Figure 13-6 Planning the radio link..................................................................................................................13-37
Figure 13-7 IDU board configuration (NE1)....................................................................................................13-38
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxxi


Figure 13-10 IDU board configuration (NE4)..................................................................................................13-38
Figure 13-12 Timeslot allocation diagram.......................................................................................................13-42
Figure 13-13 Clock Synchronization Scheme..................................................................................................13-44
Figure 13-14 Networking diagram...................................................................................................................13-65
Figure 13-15 Planning the radio link................................................................................................................13-66
Figure 13-16 IDU board configuration (NE1 and NE2)..................................................................................13-67
Figure 13-18 Planning the radio link................................................................................................................13-78
Figure 14-1 Ethernet frame format.....................................................................................................................14-4
Figure 14-2 Positions of the TPID and TCI in the frame structure....................................................................14-4
Figure 14-3 TCI structure of the C-TAG...........................................................................................................14-5
Figure 14-4 TCI structure of the S-TAG ...........................................................................................................14-5
Figure 14-5 External ports and internal ports on Ethernet boards......................................................................14-6
Figure 14-6 Waveform of a single FLP..............................................................................................................14-7
Figure 14-7 Consecutive FLP and NLP bursts ..................................................................................................14-8
Figure 14-8 Structure of the PAUSE frame.......................................................................................................14-9
Figure 14-9 VC-3-Xv/VC-4-Xv multiframe and sequence indicator...............................................................14-12
Figure 14-10 Relation between VB, LP, external port, and VCTRUNK port.................................................14-14
Figure 14-11 Transparent bridge and virtual bridge.........................................................................................14-15
Figure 14-12 EPL service configuration process.............................................................................................14-19
Figure 14-13 Ethernet test................................................................................................................................14-26
Figure 14-14 Ethernet LAN service configuration process..............................................................................14-28
Figure 14-16 EVPL(QinQ) service configuration process...............................................................................14-42
Figure 14-19 IDU board configuration ...........................................................................................................14-50
Figure 14-20 Configuring Ethernet services....................................................................................................14-50
Figure 14-21 Timeslot allocation of Ethernet services.....................................................................................14-51
xxxii Huawei Proprietary and Confidential Issue 02 (2010-09-24)


Figure 14-41 Networking diagram.................................................................................................................14-101
Figure 14-42 Link planning diagram .............................................................................................................14-102
Figure 14-43 Board layout of the IDU (NE1)................................................................................................14-104
Figure 14-46 Timeslot allocation diagram.....................................................................................................14-105
Figure 14-47 Clock synchronization scheme.................................................................................................14-106
Figure 14-48 Configuration information of Ethernet parameters...................................................................14-107
Figure 14-49 Configuration diagram of the Ethernet services between NE2 and NE3.................................14-111
Figure 14-50 Format of the Ethernet frame with only a C-TAG...................................................................14-147
Figure 14-51 Format of the Ethernet frame with a C-TAG and an S-TAG...................................................14-148
Figure 14-52 Format of the Ethernet frame with only an S-TAG..................................................................14-148
Figure 14-53 EVPL (QinQ) Services.............................................................................................................14-154
Figure 14-54 Example of the EVPLAN (802.1ad bridge) service.................................................................14-155
Figure 14-55 Ports used by the QinQ line services........................................................................................14-157
Figure 14-56 Configuration flow for the QinQ line service...........................................................................14-160
Figure 14-57 Configuration flow for the EVPLAN service that is based on the 802.1ad bridge..................14-162
Figure 14-58 Waveform of a single FLP........................................................................................................14-179
Figure 14-59 Consecutive FLP bursts and NLPs ..........................................................................................14-179
Figure 14-60 Structure of the PAUSE frame.................................................................................................14-180
Figure 14-61 Internal port of the Ethernet service board...............................................................................14-191
Figure 14-62 Structure of the GFP frame ......................................................................................................14-196
Figure 14-63 GFP type field format...............................................................................................................14-197
Figure 14-64 VC-3-Xv/VC-4-Xv multiframe and sequence indicator ..........................................................14-200
Figure 14-65 Capacity adjustment process (addition of a member) ..............................................................14-202
Figure 14-66 Capacity adjustment process (deletion of a member) ..............................................................14-203
Figure 14-67 Capacity adjustment process (one member link restored after a failure).................................14-203
Figure 14-68 Tagged frame format................................................................................................................14-216
Figure 14-69 PORT-shared EVPL service.....................................................................................................14-218
Figure 14-70 VCTRUNK-shared EVPL service............................................................................................14-219
Figure 14-71 Configuration flow of the EPL service that uses the VLAN feature (PORT-shared or VCTRUNK-
shared EVPL service) .....................................................................................................................................14-221
Figure 14-72 Relations among the VB, LP, external port, and VCTRUNK port..........................................14-233
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxxiii

Figure 14-73 802.1d bridge and 802.1q bridge..............................................................................................14-234

Figure 14-74 802.1ad Bridge..........................................................................................................................14-234
Figure 14-75 Transmission of the multicast packet (with IGMP Snooping disabled)...................................14-238
Figure 14-76 Transmission of the multicast packet (with IGMP Snooping enabled)....................................14-239
Figure 14-77 FIFO queue...............................................................................................................................14-273
Figure 14-78 SP queue...................................................................................................................................14-274
Figure 14-79 Basic principle of the token bucket algorithm..........................................................................14-279
Figure 14-80 Basic principle of the algorithm that is used by the CAR........................................................14-280
Figure 14-81 Basic principle of the algorithm that is used by the traffic shaping......................................... 14-281
Figure 14-82 SP queue...................................................................................................................................14-282
Figure 14-83 WRR scheduling algorithm......................................................................................................14-283
Figure 14-84 SP+WRR scheduling algorithm................................................................................................14-284
Figure 15-1 Networking diagram for the DiffServ model..................................................................................15-4
Figure 15-2 HQoS function points and corresponding QoS processing............................................................15-7
Figure 15-3 UNI-UNI E-Line service..............................................................................................................15-24
Figure 15-4 UNI-NNI E-Line service carried by ports....................................................................................15-24
Figure 15-5 UNI-NNI E-Line service carried by a PW...................................................................................15-25
Figure 15-6 UNI-NNI E-Line service carried by a QinQ link.........................................................................15-26
Figure 15-7 NNI-NNI E-Line service carried by a QinQ link.........................................................................15-27
Figure 15-8 E-AGGR service...........................................................................................................................15-28
Figure 15-9 Flow diagram for configuring the E-LAN service.......................................................................15-44
Figure 15-10 Configuration flow for the E-AGGR service..............................................................................15-51
Figure 16-1 Channel configuration in ACAP mode (without the application of the XPIC technology)...........16-2
Figure 16-2 Channel configuration in CCDP mode (with the application of the XPIC technology)................16-2
Figure 16-3 Realization principle of XPIC........................................................................................................16-3
Figure 17-1 ATPC realization principle.............................................................................................................17-4
Figure 18-1 Application of the Hybrid microwave feature................................................................................18-2
Figure 18-2 Multiplexing E1 services and Ethernet services into the Hybrid microwave frame......................18-3
Figure 18-3 Working principle of the Hybrid microwave .................................................................................18-4
Figure 18-4 AM switching (before the switching).............................................................................................18-8
Figure 18-5 AM switching (after the switching)................................................................................................18-9
Figure 19-1 STP/RSTP.......................................................................................................................................19-3
Figure 19-2 Limitations of the STP/RSTP.........................................................................................................19-4
Figure 19-3 MSTI in an MST region.................................................................................................................19-5
Figure 19-4 Example of the MSTP....................................................................................................................19-6
Figure 19-5 Example of the MST region...........................................................................................................19-7
Figure 20-1 LSP tunnel created by using the MPLS-RSVP..............................................................................20-7
Figure 20-2 ARP frame format..........................................................................................................................20-8
Figure 20-3 ARP address resolution..................................................................................................................20-9
Figure 21-1 MPLS tunnel in the MPLS network...............................................................................................21-2
Figure 21-2 Transparent transmission of point-to-point data packets................................................................21-3
Figure 21-3 Protection principle for unicast tunnels..........................................................................................21-4
xxxiv Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Figure 22-1 ATM PWE3 over IP tunnel............................................................................................................22-2

Figure 23-1 ATM PWE3 over GRE tunnel........................................................................................................23-2
Figure 25-1 CES service networking sample.....................................................................................................25-3
Figure 25-2 External Clock synchronization of CES service clock...................................................................25-4
Figure 25-3 UNI-UNI CES service configuration flow.....................................................................................25-5
Figure 25-4 UNI-NNI CES service configuration flow.....................................................................................25-6
Figure 26-1 ATM IMA group............................................................................................................................26-2
Figure 26-2 IMA networking diagram 1............................................................................................................26-3
Figure 26-3 IMA networking diagram 2............................................................................................................26-3
Figure 26-4 IMA networking diagram...............................................................................................................26-4
Figure 26-5 ATM connection convergence sample...........................................................................................26-4
Figure 26-6 Configuration flow of the UNI-UNI ATM service.........................................................................26-8
Figure 26-7 Configuration flow of the UNIs-NNI ATM service.......................................................................26-9
Figure 26-8 IMA group configuration flow.....................................................................................................26-13
Figure 28-1 Application of the IGMP Snooping-Supported Equipment in the Network..................................28-3
Figure 28-2 Multicast forwarding......................................................................................................................28-6
Figure 29-1 Ethernet OAM solution..................................................................................................................29-3
Figure 29-2 Logical diagram of maintenance domain layers.............................................................................29-6
Figure 29-3 IEEE 802.1ag OAMPDU.............................................................................................................29-11
Figure 29-4 Continuity check diagram.............................................................................................................29-12
Figure 29-5 Loopback test diagram..................................................................................................................29-13
Figure 29-6 Link trace test diagram.................................................................................................................29-14
Figure 29-7 IEEE 802.3ah OAMPDU.............................................................................................................29-15
Figure 29-8 Packet format of the information OAMPDU...............................................................................29-17
Figure 29-9 Packet format of event notification OAMPDU............................................................................29-21
Figure 29-10 Packet format of the loopback control OAMPDU.....................................................................29-22
Figure 29-11 Connectivity check of the MPLS OAM.....................................................................................29-40
Figure 29-12 Application scenarios of MPLS OAM.......................................................................................29-41
Figure 29-13 Application scenario of the PW OAM.......................................................................................29-47
Figure 30-1 Point-to-Point LPT networking diagram........................................................................................30-2
Figure 30-2 Point-to-Multipoint LPT networking diagram...............................................................................30-3
Figure 32-1 Application of the synchronous Ethernet in the wireless access network......................................32-2
Figure 32-2 Realization principle of the synchronous Ethernet.........................................................................32-4
Figure 34-1 Outloop.........................................................................................................................................34-18
Figure 34-2 Inloop............................................................................................................................................34-18
Figure 34-3 Outloop.........................................................................................................................................34-19
Figure 34-4 Inloop............................................................................................................................................34-20
Figure 34-5 Inloop............................................................................................................................................34-21
Figure 34-6 Outloop.........................................................................................................................................34-22
Figure 34-7 Inloop............................................................................................................................................34-22
Figure 34-8 Outloop.........................................................................................................................................34-23
Figure 34-9 Inloop............................................................................................................................................34-23
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxxv

Figure 34-10 Outloop.......................................................................................................................................34-24

Figure 34-11 Inloop..........................................................................................................................................34-25
Figure 34-12 Outloop.......................................................................................................................................34-26
Figure 34-13 Inloop..........................................................................................................................................34-26
Figure 34-14 Outloop.......................................................................................................................................34-27
Figure 34-15 Inloop..........................................................................................................................................34-28
xxxvi Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Operation Guide for RTN NE Management Tables
Tables
Table 1-1 SDH board parameters.........................................................................................................................1-9

Table 1-2 PDH board parameters.......................................................................................................................1-10
Table 1-3 RTN board parameters.......................................................................................................................1-10
Table 1-4 Data board parameters........................................................................................................................1-11
Table 3-1 SSM allocation...................................................................................................................................3-11
Table 3-2 Methods of selecting clock sources in different modes.....................................................................3-12
Table 5-1 Configuration of the synchronous data port.........................................................................................5-8
Table 5-2 Configuration of the synchronous data port.........................................................................................5-8
Table 5-3 Configuration of the asynchronous data services...............................................................................5-11
Table 5-4 Configuration of the asynchronous data services...............................................................................5-12
Table 6-1 Configuration of the external alarms....................................................................................................6-4
Table 6-2 Configuration of the external alarms....................................................................................................6-4
Table 7-1 SDH board parameters.........................................................................................................................7-2
Table 7-2 PDH board parameters.........................................................................................................................7-3
Table 7-3 RTN board parameters.........................................................................................................................7-3
Table 7-4 Data board parameters..........................................................................................................................7-4
Table 7-5 Methods used by ports to process data frames...................................................................................7-28
Table 7-6 Methods used by ports to process data frames...................................................................................7-35
Table 8-1 Application scenario of PDH interfaces...............................................................................................8-5
Table 8-2 Application scenario of Ethernet interfaces.......................................................................................8-10
Table 8-3 Application scenario of microwave interfaces...................................................................................8-14
Table 11-1 Availability of the 1+1 HSB feature................................................................................................11-3
Table 11-2 Availability of the 1+1 HSB feature................................................................................................11-3
Table 11-3 Availability of the 1+1 FD feature.................................................................................................11-10
Table 11-4 Availability of the 1+1 FD feature.................................................................................................11-10
Table 11-5 Availability of the 1+1 SD feature.................................................................................................11-19
Table 11-6 Availability of the 1+1 SD feature.................................................................................................11-19
Table 12-1 MSP type..........................................................................................................................................12-4
Table 12-2 Preemptible relation of priorities of MSP protection switching......................................................12-5
Table 12-3 SNCP parameters.............................................................................................................................12-8
Table 12-4 Availability of the N+1 protection feature.....................................................................................12-13
Table 12-5 Availability of the N+1 protection feature.....................................................................................12-13
Table 12-6 Description of the configuration flow of the N+1 protection mode...............................................12-18
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxxvii

Tables Operation Guide for RTN NE Management
Table 12-7 Availability of the linear MSP solution.........................................................................................12-29

Table 12-8 Availability of the linear MSP solution.........................................................................................12-29
Table 12-9 Availability of the two-fiber bidirectional ring MSP.....................................................................12-40
Table 12-10 Availability of the SNCP solution................................................................................................12-47
Table 12-11 Availability of the SNCP solution................................................................................................12-47
Table 12-12 Parameters for MPLS APS 1+1 protection..................................................................................12-62
Table 12-13 Parameters for MPLS APS 1:1 protection...................................................................................12-63
Table 12-14 Description of each filed in R-APS specific information............................................................12-72
Table 12-15 Boards and equipment versions of the OptiX RTN 910, OptiX RTN 950, OptiX RTN 620 and NMS
versions that support the ERPS protection........................................................................................................12-74
Table 12-16 Availability of the LAG feature...................................................................................................12-83
Table 12-17 Availability of the LAG feature...................................................................................................12-83
Table 13-1 Service requirements......................................................................................................................13-36
Table 13-2 Planning information of the radio link...........................................................................................13-37
Table 13-3 Attributes of the IF 1+1 protection ................................................................................................13-39
Table 13-4 Information of IF ports (NE1 and NE2).........................................................................................13-39
Table 13-5 Information of IF ports (NE3, NE4, and NE5)..............................................................................13-40
Table 13-6 Information of ODU ports (NE1 and NE2)....................................................................................13-40
Table 13-7 Information of ODU ports (NE3, NE4, and NE5).........................................................................13-41
Table 13-8 Clock information..........................................................................................................................13-44
Table 13-9 Orderwire information...................................................................................................................13-44
Table 13-10 Planning information of the radio link.........................................................................................13-66
Table 13-11 Attributes of the IF 1+1 protection...............................................................................................13-67
Table 13-12 Information of IF ports.................................................................................................................13-67
Table 13-13 Information of ODU ports............................................................................................................13-68
Table 13-14 PDH service configuration...........................................................................................................13-68
Table 13-15 Orderwire information.................................................................................................................13-68
Table 13-16 Planning information of the radio link between NE3 and NE5...................................................13-78
Table 13-17 Attributes of the IF 1+1 protection (NE5)....................................................................................13-79
Table 13-18 Information of ODU ports (NE5).................................................................................................13-79
Table 13-19 PDH service configuration (NE5)................................................................................................13-80
Table 13-20 Orderwire information.................................................................................................................13-80
Table 14-1 Tag types defined by using the TPID...............................................................................................14-5
Table 14-2 Processing mode of data frames at ports with different tags..........................................................14-13
Table 14-3 Transparent bridge and virtual bridge............................................................................................14-15
Table 14-4 Types of bridges supported by the Ethernet boards.......................................................................14-16
Table 14-5 Parameters of external Ethernet ports............................................................................................14-51
Table 14-6 Parameters of internal Ethernet ports.............................................................................................14-51
Table 14-7 Parameters of external Ethernet ports............................................................................................14-58
Table 14-8 Parameters of internal Ethernet ports.............................................................................................14-58
Table 14-9 Parameters of EPL services............................................................................................................14-58
Table 14-10 Parameters of external Ethernet ports..........................................................................................14-67
Table 14-11 Parameters of internal Ethernet ports...........................................................................................14-67
xxxviii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Table 14-12 Parameters of EPL services..........................................................................................................14-68

Table 14-15 Parameters of Ethernet LAN services..........................................................................................14-76
Table 14-18 Parameters of Ethernet LAN services..........................................................................................14-87
Table 14-19 Link capacity..............................................................................................................................14-102
Table 14-20 Information for planning a radio link.........................................................................................14-103
Table 14-21 Attributes of the IF 1+1 protection.............................................................................................14-104
Table 14-22 Clock information...................................................................................................................... 14-106
Table 14-23 Orderwire information............................................................................................................... 14-106
Table 14-24 Parameters of external ports of the EMS6 board....................................................................... 14-107
Table 14-25 Parameters of external ports of the IFH2 board.........................................................................14-108
Table 14-26 Parameters of Ethernet private line services (NE1)...................................................................14-108
Table 14-27 Parameters of Ethernet private line services (NE2)...................................................................14-108
Table 14-28 Flow configuration.....................................................................................................................14-109
Table 14-29 Parameters of the CARa.............................................................................................................14-109
Table 14-30 Parameters of the CoS................................................................................................................14-110
Table 14-31 Parameters of the link aggregation group.................................................................................. 14-110
Table 14-32 Parameters of external Ethernet ports........................................................................................ 14-111
Table 14-33 Parameters of the CoS of the IFH2 board (NE2).......................................................................14-111
Table 14-34 Parameters of Ethernet services (NE3)...................................................................................... 14-111
Table 14-35 Line services between C-aware ports.........................................................................................14-149
Table 14-36 Line services between a C-aware port and an S-aware port...................................................... 14-150
Table 14-37 Line services between S-aware ports.........................................................................................14-151
Table 14-38 Characteristics of the IEEE 802.1ad bridge...............................................................................14-151
Table 14-39 LAN services that enter and exit the IEEE 802.1ad bridge through the C-aware port..............14-152
Table 14-40 LAN services that enter and exit the IEEE 802.1ad bridge through the S-aware port...............14-153
Table 14-41 Availability of the QinQ feature................................................................................................ 14-154
Table 14-42 Description of the configuration flow of the QinQ line service.................................................14-160
Table 14-43 Description of the configuration flow of the EVPLAN service that is based on the 802.1ad bridge
.........................................................................................................................................................................14-162
Table 14-44 Auto-negotiation rules of FE electrical ports (when the local port adopts the auto-negotiation mode)
.........................................................................................................................................................................14-174
Table 14-45 Auto-negotiation rules of GE electrical ports (when the local port adopts the auto-negotiation mode)
.........................................................................................................................................................................14-175
Table 14-46 Availability of the Ethernet port feature.................................................................................... 14-177
Table 14-47 Methods used by ports to process data frames...........................................................................14-189
Table 14-48 Availability of the Ethernet encapsulation and mapping feature...............................................14-194
Table 14-49 UPI values of the client management frame.............................................................................. 14-198
Table 14-50 LCAS CTRL words ...................................................................................................................14-201
Table 14-51 Methods used by ports to process data frames...........................................................................14-212
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xxxix

Tables Operation Guide for RTN NE Management
Table 14-52 Data frame processing method of the switch port......................................................................14-217

Table 14-53 Availability of the VLAN..........................................................................................................14-219
Table 14-54 Configuration flow of the EVPL service that uses the VLAN feature (PORT-shared EVPL service)
.........................................................................................................................................................................14-222
Table 14-55 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNK-shared EVPL
service)............................................................................................................................................................14-222
Table 14-56 Three Types of Bridges Supported by the Ethernet Switching Board.......................................14-234
Table 14-57 Availability of Layer 2 Switching..............................................................................................14-240
Table 14-58 CoS Type....................................................................................................................................14-277
Table 14-59 Availability of the QoS Feature.................................................................................................14-278
Table 15-1 Scheduling and application..............................................................................................................15-6
Table 15-2 Table for mapping relations between the RTN equipment and the supported QoS policies...........15-8
Table 15-3 PHB service level and mapping PHB service quality......................................................................15-9
Table 15-4 Mapping relation between the ATM service type and PHB service class.....................................15-19
Table 15-5 Tasks for configuring the UNI-UNI E-Line service......................................................................15-29
Table 15-6 Tasks for configuring the UNI-UNI E-Line service carried by a port...........................................15-30
Table 15-7 Tasks for configuring the UNI-NNI E-Line service carried by PWs.............................................15-30
Table 15-8 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link...................................15-31
Table 15-9 Tasks for configuring the UNI-UNI E-Line service......................................................................15-38
Table 15-10 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link.................................15-39
Table 16-1 Availability of the XPIC feature......................................................................................................16-2
Table 17-1 ATPC performance..........................................................................................................................17-2
Table 17-2 Availability of the ATPC feature.....................................................................................................17-3
Table 17-3 Availability of the ATPC feature.....................................................................................................17-3
Table 18-1 Radio work modes in the case of hybrid microwave frames...........................................................18-5
Table 18-2 Availability of the Hybrid microwave feature.................................................................................18-7
Table 18-3 Availability of the Hybrid microwave feature.................................................................................18-7
Table 25-1 CES service clock type.....................................................................................................................25-4
Table 25-2 Tasks for configuring the UNI-UNI CES service............................................................................25-5
Table 25-3 Tasks for configuring the UNIs-NNI CES service..........................................................................25-6
Table 26-1 ATM service type and traffic...........................................................................................................26-5
Table 26-2 Tasks for configuring the UNI-UNI ATM service...........................................................................26-8
Table 26-3 Tasks for configuring the UNIs-NNI ATM service.........................................................................26-9
Table 26-4 ATM Interface................................................................................................................................26-11
Table 29-1 Availability of the ETH-OAM Feature..........................................................................................29-10
Table 29-2 Availability of the ETH-OAM Feature..........................................................................................29-10
Table 29-3 Mapping relation between values and OMA packet types (non-standard MP).............................29-11
Table 29-4 Mapping relation between code values and OAM packet types....................................................29-15
Table 29-5 Details of OAM configuration bytes..............................................................................................29-18
Table 29-6 Mapping relation between OAM working modes and OAM functions.........................................29-20
Table 29-7 Application scenarios of MPLS OAM detection methods.............................................................29-41
Table 29-8 Classification of the OAM function layers....................................................................................29-49
Table 29-9 Application scenarios of ATM OAM detection methods..............................................................29-51
xl Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Table 30-1 Availability of the LPT feature(RTN600)........................................................................................30-4

Table 30-2 Availability of the LPT feature(RTN900)........................................................................................30-4
Table 30-3 Parameter of the Point-to-Point LPT(RTN600).............................................................................30-13
Table 30-4 Parameter of the Point-to-Multipoint LPT(RTN600)....................................................................30-14
Table 30-5 Parameter of the LPT(RTN900).....................................................................................................30-14
Table 31-1 List of RMON alarm entries............................................................................................................31-5
Table 31-2 List of RMON performance entries.................................................................................................31-5
Table 31-3 Availability of the RMON Feature..................................................................................................31-7
Table 31-4 Availability of the RMON Feature..................................................................................................31-8
Table 32-1 Availability of the synchronous Ethernet feature.............................................................................32-2
Issue 02 (2010-09-24) Huawei Proprietary and Confidential xli

Operation Guide for RTN NE Management 1 Creating NEs, Links, and Topology Subnets
1 Creating NEs, Links, and Topology Subnets
About This Chapter
On the U2000, you can create NEs , Links, and Topology Subnets to perform management
through the U2000.
1.1 Creating NEs

Each set of the 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
ways of creating NEs: creating a single NE (manually) and creating NEs in batches (through
search). When you add an NE or certain NEs to a large network, for example, during deployment,
it is recommended to create NEs in batches through search. In other scenarios, it is recommended
to create a single NE manually.
1.2 Configuring the NE Data
Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the U2000 can manage and operate the NE.
1.3 Checking Board Parameters
To learn about board parameter status, you can check board parameters. Before actual
configuration operations in networking, you need to check board parameters, to make sure that
the board parameter status meets the requirements of actual networking.
1.4 Creating Links
You need to create fibers before managing services on the U2000 in the end-to-end manner.
1.5 Creating a Topology Subnet
The subnet created here is based on a topological concept to facilitate management. In the case
of topology objects in the same network area or with similar attributes, you can allocate them
in one topology subnet.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential 1-1

1 Creating NEs, Links, and Topology Subnets Operation Guide for RTN NE Management
1.1 Creating NEs

Each set of the 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
ways of creating NEs: creating a single NE (manually) and creating NEs in batches (through
search). When you add an NE or certain NEs to a large network, for example, during deployment,
it is recommended to create NEs in batches through search. In other scenarios, it is recommended
to create a single NE manually.
1.1.1 Creating NEs in Batches

When the U2000 communicates properly with the GNE, you can create NEs in batches by
searching for all NEs that communicate with the GNE, by using the IP address of the GNE or
the network segment to which the IP address is associated, or by using the NSAP address of the
NE. This method is quicker and more accurate than manual creation.
1.1.2 Creating a Single NE
After the NE is created, you can use the U2000 to manage the NE. Although creating a single
NE is not as fast and exact as creating NEs in batches, you can use this method regardless of
whether the data is configured on the NE or not.
1.1.1 Creating NEs in Batches

When the U2000 communicates properly with the GNE, you can create NEs in batches by
searching for all NEs that communicate with the GNE, by using the IP address of the GNE or
the network segment to which the IP address is associated, or by using the NSAP address of the
NE. This method is quicker and more accurate than manual creation.
Prerequisite
l You must be an NM user with "NE administrator" authority or higher.
l The U2000 must communicate properly with the GNE.
l The NE Explorer instance of the NEs must be created.
Procedure
Step 1 Choose File > Discovery > NE from the main menu. The Auto Discovery window is displayed.
Step 2 Click the Transport NE Search tab.
Step 3 Optional: Enter the network segment or IP addresses NEs to search for the NEs.
1. Click Add and the Input Search Domain dialog box is displayed.
2. Set Address type to IP Address Range of GNE, IP Address of GNE or NSAP
Address, and enter the information of the search address. Click OK.
1-2 Huawei Proprietary and Confidential Issue 02 (2010-09-24)

NOTE
You can repeat Steps 2 through 3 to add more search fields. You can delete the system default search
field.
l If you use IP address to search for NEs, and the IP address of the U2000 computer and that of
the GNE are within the same network segment, you can select IP Address Range of GNE or
IP Address of GNE.
l If the IP addresses are not within the same network segment, select only IP Address of GNE.
l If you use NSAP address, you can only select NSAP address.
Step 4 Optional: If you fail to enter a network segment correctly, enable IP auto discovery and enter
the User Name and Password of the NEs.
NOTE
After enabling IP auto discovery, you can obtain the IP address of the GNE and search out all the NEs
related to the GNE.
Step 5 In the Search for NE area, perform the following operations:

l Select Search for NE. All NEs in the selected domain are searched out.
l Select Create device after search, enter the NE User and Password.
NOTE
l The default NE user is root.

l The default password is password.
l Select Upload after create. The data related to the NEs are uploaded to the U2000 after
the NEs are created.
NOTE
You can select all options in the Search for NE area to search for NEs, create NEs, and upload the NE
data at a time.
Step 6 Click Next and the Result area is displayed.

Step 7 When the search ends or if you click Stop, select the uncreated NEs in the Result list and click
Create. The Create dialog box is displayed.
Step 8 Enter the NE user name and password.

NOTE
l The default NE user is root.

l The default password is password.
Step 9 Click OK.
----End
Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
1.1.2 Creating a Single NE

After the NE is created, you can use the U2000 to manage the NE. Although creating a single
NE is not as fast and exact as creating NEs in batches, you can use this method regardless of
whether the data is configured on the NE or not.
Prerequisite
l You must be an NM user with "NM operator" authority or higher.
l The license must be installed and the license must support creating the NE of the type.
l The NE Explorer instance of the NEs must be created.
Context
First create a GNE, and then create a non-gateway NE.
If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray color.
Procedure
Step 1 Choose File > Create > NE from the main menu. The Create NE dialog box is displayed.
Step 2 Select the NE type from the Object Type tree.
Step 3 Complete the following information: ID, Extended ID, Name and Remarks.
Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.
Step 5 Choose Gateway Type, Protocol and set the IP address or serial port number and serial port
rate.
1. Select Gateway from the Gateway Type drop-down list.
2. Select the Protocol type.

If the U2000 Do...

communicates with
NEs through
IP protocol Select IP from the Protocol drop-down list. Enter the IP

Address and use the default value for the Port number of
the GNE.
OSI protocol Select OSI from the Protocol drop-down list. Enter the
NSAP Address of the GNE.
NOTE
The domain address that contains a maximum of 13 bytes is entered by the user. NSEL is the port
number of the network-level protocol, with a fixed value of 1d (one byte).
Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NE
is associated to from the Affiliated Gateway drop-down list.
Step 7 Enter the NE User and Password.
NOTE
The default NE user is root, and the default password is password.
Step 8 Click OK. Click in the blank space of the Main Topology and the NE icon appears in the position
where you clicked.
----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.
Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as the IP address of the NE and NE ID.
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
1.2 Configuring the NE Data

Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the U2000 can manage and operate the NE.
1.2.1 Configuring the NE Data Manually

You need to manually configure the NE data during initialization. The operation clears original
service data from NEs and then deliver the new configuration data to NEs.
1.2.2 Replicating the NE Data

You can replicate the data of an existing NE to a new NE, if the existing NE is already
configuration and if the existing NE is of the same NE type and the same NE version as the new
NE.
1.2.3 Uploading the NE Data
By uploading the NE data, you can synchronize the current NE configuration data to the network
management system directly.
1.2.1 Configuring the NE Data Manually

You need to manually configure the NE data during initialization. The operation clears original
service data from NEs and then deliver the new configuration data to NEs.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The NE must be created successfully.
Background Information
When you manually configure the NE data, the original service data is cleared from the NEs.
Therefore, the communications between the NEs and the U2000 may be interrupted and the
subsequent procedures of manually configuring the NE data cannot be performed. In the case
of the RTN NEs, this operation is used for configuring gateway NEs for the first time.
Procedure
Step 1 Select the NE whose data you want to configure. Double-click the unconfigured NE on the Main
Topology. The NE Configuration Wizard dialog box is displayed.
Step 2 Choose Manual Configuration and click Next. The Confirm dialog box is displayed indicating
that manual configuration clears the data on the NE side.
Step 3 Click OK. The Confirm dialog box is displayed indicating that manual configuration interrupts
the service on the NE.
Step 4 Click OK. The Set NE Attribute dialog box is displayed.
Step 5 Set NE Name, Equipment Type, NE Remarks and Subrack Type and then click Next. The
NE slot 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 on the slot to add a board. Click Next to display the Send Configuration window.
Step 9 Choose Verify and Run as required and click Finish.
NOTE
Verification is to run the verification command. Click Finish to deliver the configuration to NEs and the
basic configuration of the NEs is complete. After the successful verification, the NEs start to work normally.
----End

1.2.2 Replicating the NE Data

You can replicate the data of an existing NE to a new NE, if the existing NE is already
configuration and if the existing NE is of the same NE type and the same NE version as the new
NE.
Prerequisite
The type and NE software version of the source NE must be consistent with the type and software
version of the replicated NE.
Procedure
Step 1 Select the NE whose data you need to replicate.
NE to Be Configured Operation
RTN equipment Double-click the unconfigured NE on the

Main Topology. Then, the NE
Configuration Wizard dialog box is
displayed.
Step 2 Select Copy NE Data and click Next. The NE Replication dialog box is displayed.
Step 3 Select the NE from the drop-down list and click Start. The Confirm dialog box is displayed,
indicating that the replication operation copies all the data of the source NE to overwrite all the
data of the selected NE.
NOTE
After the NE data is replicated, only the data on the U2000 side is changed, but the data on the equipment
side is not changed.
Data coping between the NEs of different equipment type is not recommended.
Step 4 Click OK. 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 copied.
Step 5 Click OK to start the replication. The Operation Result dialog box is displayed after a few
seconds.

Step 6 Click Close.
----End
1.2.3 Uploading the NE Data

By uploading the NE data, you can synchronize the current NE configuration data to the network
management system directly.
Prerequisite
Procedure
Step 1 Select the NE whose data you need to Replicate.
NE to Be Configured Operation
RTN equipment Double-click the unconfigured NE on the

Main Topology. The NE Configuration
Wizard dialog box is displayed.
Step 2 Select Upload and click Next. The Confirm dialog box is displayed, indicating that the upload
may take a long time.
Step 3 Click OK to start the upload. The Operation Result dialog box is displayed when the uploading
is complete.
Step 4 Click Close.
----End

Procedure
Step 1 Select the corresponding navigation path and check the related board parameters.
1. Check SDH board parameters. For the SDH board parameters, see Table 1-1.

Table 1-1 SDH board parameters

Board Type Parameter Navigation Path Application
Scenario
SDH Laser Switch a. In the NE When configuring

Explorer, select services on an
a board. optical interface of
b. Choose a board, enable this
Configuration parameter.
> SDH
Optical(Electrical) l Non-loopback:
Interface from
Interface Loopback It is a normal
the Function
state. When the
Tree.
equipment runs
c. Click By normally, set
Board/Port this parameter to
(channel) and non-loopback.
select Port from
l Inloop: The loop
the drop-down
is performed
list.
toward the local
NE.
l Outloop: The
loop is
performed
toward the
opposite NE.
Inloop and
outloop of an
optical interface
affect services.
They are used to
locate faults.
2. Check PDH board parameters. For the PDH board parameters, see Table 1-2.

Table 1-2 PDH board parameters
Boar
Paramet Navigation
d Application Scenario
er Path
Type
Tributary l Non-loopback: It is a normal state. When

Loopback the equipment runs normally, set this
parameter to non-loopback.
l Inloop: When input service signals reach
the tributary board of the target NE, the
a. In the NE signals revert to the original trail. This
Explorer, function is used to locate faults of each
select a board. service path.
b. Choose l Outloop: When input service signals reach
Configuratio the tributary board through the input port
n > PDH of the local NE, the signals are looped back
Interface directly to the service output end.
from the
PDH Service Function l Non-loaded: The service path does not
Load Tree. process the services that are carried, to
Indication c. Click By suppress alarms in non-loaded service
Board/Port paths.
(channel) l Load: The service path processes the
and select services that are carried. In the case of a
Port from the tributary board that has services, set this
drop-down parameter to Load.
list.
Retiming Normal, Retiming Mode of Tributary Clock,
Mode Retiming Mode of Cross-Connect Clock
Default: Normal
Sets the retiming mode of the board. The
default value is usually selected.
3. Check RTN board parameters. For the RTN board parameters, see Table 1-3.
Table 1-3 RTN board parameters
Boar
Paramet Navigation
er Path
Type
Radio a. In the NE Specifies the microwave working mode. Its

Work Explorer, formats are service capacity, working
Mode select a board. bandwidth and modulation mode.
b. Choose The transmit end and the receive end must
RTN have the same settings of the microwave
Configuratio
n > IF working mode.
Radio Interface Radio Link ID: 1 to 4094

Link ID from the

Boar
Paramet Navigation
er Path
Type
IF Port Function Sets the loopback status of an intermediate

Loopback Tree. frequency interface on the equipment.
c. Click By Non-Loopback refers to the normal status. It
Board/Port is not required to set loopback during normal
(channel) equipment operation.
and select
Outloop means that the input signal passes
Port from the
through the ingress port and reaches the
drop-down
intermediate frequency board at the local NE
list.
and then is directly loopbacked to the service
egress end.
Inloop means that the input signal returns
from the intermediate frequency board of the
destination NE along the original trail.
This function is usually used to locate faults
for various IF interfaces. Performing loopback
on an intermediate frequency interface is a
diagnosis function which may affect services
of related ports. Exercise caution before
performing this function.
2M Enables or disables a 2 Mbit/s bypath service.

Wayside This parameter is available only when you set
Enable Radio Work Mode to STM-1,28MHz,
Status 128QAM.
ATPC When the ATPC is enabled, according to the

Enable current receive power of the ODU and the set
Status ATPC thresholds, the ATPC module inserts
the ATPC overhead. According to the ATPC
overhead, the opposite ODU adjusts the
transmit power.
When the ATPC is disabled, the ATPC
module does not insert any ATPC overhead.
4. Check data board parameters. For the data board parameters, see Table 1-4.
Table 1-4 Data board parameters

Boar
Parame
d Navigation Path Application Scenario
ter
Type
Enabled/ a. In the NE Explorer,

Ethern Disabled select a board. When configuring Ethernet board port
et b. Choose services, set the port to Enabled.
Configuration >

Boar
Parame
ter
Type
Working Ethernet Interface Set the working mode of Ethernet ports

Mode Management > according to networking configuration
Ethernet requirements.
Interface from the
Maximu Function Tree. When a packet exceeds the maximum
m Frame frame length that is set, the packet is
c. Click External
Length discarded. Alternatively, the packet
Port.
length is minimized to satisfy the
d. Click the Basic specified frame length. By default, the
Attributes tab. value is set to 1522, unless otherwise
specified.
MAC l Non-loopback: It is a normal state.

Loopbac When the equipment runs normally,
k set this parameter to non-loopback.
l Inloop: Inside the equipment,
services from the cross-connect side
are looped back to the cross-connect
side. This operation affects services
configured on ports and is used to
locate faults.
PHY l Non-loopback: It is a normal state.

locate faults.
TAG l Tag Aware: If the client-side

a. In the NE Explorer, equipment sends tag packets, set the
select a board. TAG attribute of external ports to
Tag Aware.
b. Choose
Configuration > l Access: If the client-side equipment
Ethernet Interface sends untag packets, set the TAG
Management > attribute of external ports to Access.
Ethernet l Hybrid: If the client-side equipment
Interface from the sends tag and untag packets, set the
Function Tree. TAG attribute of external ports to
c. Click External Hybrid.
Port.
Entry This parameter is used to identify tags in
Detectio d. Click the TAG data packets. During the configuration of
n Attributes tab. VLAN services, set this parameter to
Enabled.

Step 2 Modify board parameters according to service planning and actual board configurations.
----End
1.4 Creating Links

You need to create fibers before managing services on the U2000 in the end-to-end manner.
1.4.1 Creating Fibers Automatically

Fiber links are often created through search. By using the fiber search function, you can obtain
the information about the fiber link to which the specified optical interface is connected. Then,
the radio link to which the optical interface is connected can be created on the Fiber links are
often created through search. By using the fiber search function, you can obtain the information
about the fiber link to which the specified optical interface is connected. Then, the radio link to
which the optical interface is connected can be created on the in the fast manner. In a new
network, after you configure the boards of the NEs on the , you need to search all optical interface
to create the fiber links networkwide. Then, you can easily monitor the actual working status of
each fiber link. This method is often used to create fiber links. in the fast manner. In a new
network, after you configure the boards of the NEs on the U2000
1.4.2 Automatically Creating Radio Links
Using the fiber/cable search function, you can know whether any radio links are connected at a
specified IF interface. This helps you quickly create radio links at the IF interface. For a newly
created network, you can search for all the IF interfaces networkwide to create radio links after
you complete the board configuration on the U2000. In this way, you can monitor the actual
working state of each radio link.
1.4.3 Manually Creating Radio Links
After you manually fill in the table, the U2000 can create radio links according to the
configuration information about the links. This operation is often used when actual radio link is
not formed.
1.4.1 Creating Fibers Automatically

Fiber links are often created through search. By using the fiber search function, you can obtain
the information about the fiber link to which the specified optical interface is connected. Then,
the radio link to which the optical interface is connected can be created on the Fiber links are
often created through search. By using the fiber search function, you can obtain the information
about the fiber link to which the specified optical interface is connected. Then, the radio link to
which the optical interface is connected can be created on the in the fast manner. In a new
network, after you configure the boards of the NEs on the , you need to search all optical interface
to create the fiber links networkwide. Then, you can easily monitor the actual working status of
each fiber link. This method is often used to create fiber links. in the fast manner. In a new
network, after you configure the boards of the NEs on the U2000
Prerequisite
l You must be an NM user with "NE maintainer" authority or higher.
l The optical interfaces of every NE must be connected using fibers.
l The boards of every NE must be created on the U2000.

Context
l If conflicting fibers are found during the creation, delete the conflicting fibers on the
U2000 before you start creating fibers.
l When a fiber between two SDH NEs passes through a WDM NE, if the normal fiber
between an SDH NE and a WDM NE has been created on the U2000, the fiber found by
the trail search function is created as a virtual fiber. If the WDM NE is not created on the
U2000, the fiber is created as a normal fiber.
l When a fiber is created, it is usually bidirectional. But when the fiber is connected to the
ports of the REG functions or the SDH and WDM equipment, the fiber is unidirectional.
CAUTION
Fiber/Cable search may interrupt services. Exercise caution when performing this operation.
Procedure
Step 1 CChoose File > Discovery > Fiber from the main menu. The Search for Fiber/Cable window
is displayed.
Step 2 In the left pane select some ports from one or more NEs and click Search to search for the fibers
or cables. A progress bar is displayed showing the progress of the search.
NOTE
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system
only searches for the ports that do not have fibers.
l To check if the created fiber is consistent with the actual fiber connection, leave the check box
unchecked.
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, and if all
the selected ports have fibers created, the system displays a message indicating that the search field is
null.
Step 3 A prompt is displayed indicating that the operation is successful. Click Close.
Step 4 To create fibers, select one or more fibers from the Physical Fiber/Cable Link List list and
click Create Fiber/Cable.
NOTE
l When one or more fibers are selected in the Physical Fiber/Cable Link List list, fibers that conflict
with the selected fibers, are shown in the Logical Fiber/Cable Link List list. If there is any conflicting
fiber, proceed to Step 5 and delete it before creating fibers.
l During fiber creation, if all the selected fibers are in the Already created state, the system displays
the message as follows: No fiber to create.
Step 5 To delete the conflicting fibers, from the Logical Fiber/Cable Link List list select one or more
fibers whose values are Yes for the Conflict with logical link (Y/N) parameter in the
Misconnected Fiber list. Click Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the fiber that is created through search is incomplete, you can
supplement the information about the fiber by modifying the fiber/cable information.

1.4.2 Automatically Creating Radio Links

Using the fiber/cable search function, you can know whether any radio links are connected at a
specified IF interface. This helps you quickly create radio links at the IF interface. For a newly
created network, you can search for all the IF interfaces networkwide to create radio links after
you complete the board configuration on the U2000. In this way, you can monitor the actual
working state of each radio link.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
The IF board for each NE must be created on the U2000.
Context
The radio frequency wireless signals within the frequency range of 300 MHz to 300 GHz are
called radio signals. The links that transmit radio signals are called radio links.
Procedure
Step 1 Choose File > Discovery > Fiber from the main menu.
Step 2 In the left-hand pane, select IF interfaces for one or multiple radio NEs. Click Search. A progress
bar is displayed.
NOTE
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system
does not search for the ports at which radio links are already created.
l If you need to check consistency between the created radio links and the actual radio links, do not check
this check box.
l If you check this check box and if all the selected ports radio links are created, a dialog box is displayed
after the search is complete, telling that the search domain is empty.
Step 3 After the search is complete, a dialog box is displayed, telling that the operation was successful.
Click Close.
Step 4 In the Physical Fiber/Cable Link List list, select one or multiple radio links. Click Create
Fiber/Cable.
NOTE
l When you select one or multiple radio links in the Physical Fiber/Cable Link List list, the radio links
that conflict with the selected ones are automatically displayed in the Logical Fiber/Cable Link
List list. In this case, refer to Step 5 to delete the conflicting radio links before the creation.
l During the creation of radio links, if the selected links are all in the Already created state, the system
prompts No fiber to create.
Step 5 In the Logical Fiber/Cable Link List list, select one or multiple conflicting radio links (the
Conflict with logical link (Y/N) value of which in the Misconnected Fiber list is displayed as
Yes), Click Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the radio link that is created through search is incomplete, you can
supplement the information about the radio link by modifying the fiber/cable information.

1.4.3 Manually Creating Radio Links

After you manually fill in the table, the U2000 can create radio links according to the
configuration information about the links. This operation is often used when actual radio link is
not formed.
Prerequisite
l The boards to be connected with radio links must be created.
Context
Usually, the radio frequency wireless signal within the frequency range of 300 MHz to 300 GHz
is called a radio signal. The link that transmits radio signals is called a radio link.
Procedure
Step 1 Click the shortcut icon on the toolbar of the U2000 Main Topology and the cursor changes
to a + sign.
Step 2 Click the source NE of the radio link on the U2000 Main Topology.
Step 3 Select the source board and port in the Select Fiber/Cable Source dialog box.
Step 4 Click OK and the cursor changes to a + sign.
Step 5 Click the sink NE of the radio link on the U2000 Main Topology.
Step 6 Select the sink board and port in the Select Fiber/Cable Sink dialog box.
TIP
When selecting the wrong source or sink NE, right-click and click OK in the Object Selection dialog box
to exit.
Step 7 Click OK. Enter the information of the fiber or cable in the Create Link dialog box.
Step 8 Click OK. The created radio link appears between the source and sink NEs on the U2000 Main
Topology.
----End
1.5 Creating a Topology Subnet

The subnet created here is based on a topological concept to facilitate management. In the case
of topology objects in the same network area or with similar attributes, you can allocate them
in one topology subnet.
Prerequisite
You must be an NM user with "NM operator" authority or higher.
A topology subnet is created only to simplify the user interface and has no impact on the NEs.

Procedure
Step 1 Right-click in the blank space of the U2000 Main Topology and choose New > Subnet from
the shortcut menu.
Step 2 On the subnet tree of the displayed dialog box, select the type of subnet to be created.
Step 3 Click the Property tab. Enter the attributes of the subnet.
Step 4 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane
and click to add the NEs or subnet to the Select Objects pane.
NOTE
In the case of a similar dialog box for selecting objects,

l indicates that objects on the left pane are selected one by one to the right pane.
l indicates that all objects are selcted from the left pane to the right pane.
Step 5 Click OK.
----End

Operation Guide for RTN NE Management 2 DCN Management
2 DCN Management
About This Chapter
The U2000 communicates with NEs, and manages and maintains network nodes through a
DCN. In the DCN, the U2000 and NEs are considered as nodes, which are connected by using
the Ethernet or DCC physical channels. In practice, the U2000 and NEs may be located at
different floors of the same building, different buildings or different cities. Hence, U2000 and
NEs are connected through a DCN, which consists of switches and routers. The DCN between
the NEs is referred to as an internal DCN.
2.1 DCN Overview

The element management system (EMS) sets up communication with NEs through a data
communication network (DCN), to manage and maintain these NEs.
2.2 DCN Management Flow
This section describes operation tasks of creating and maintaining the DCN by using the
U2000. It also describes the relation between the operation tasks.
2.3 Configuring ECC Communication
ECC configuration is simple. By default, all Huawei equipment support the ECC protocol and
the physical transmission channel is D1-D3 bytes. When the NE ID is set and fibers are
connected, the ECC communication is established without any configurations. If you want to
modify the ECC communication parameters, locally modify them. Do not remotely modify the
parameters because ECC communication may be interrupted and cannot be recovered. If you
have to remotely modify the parameters, start from the farthest end.
2.4 Configuring IP Over DCC Communication
The IP over DCC communication transmits DCC data by the using IP data packets. The IP over
DCC directly operates and maintains remote NEs by using standard TCP/IP protocol. In addition,
it realizes the application functions, such as FTP, Telnet, and SNMP. As essential parts of the
IP over DCC communication, the dynamic and static routing protocols are used to create route
information.
2.5 Configuring OSI Over DCC Communication
The OSI protocol is a widely used communication protocol in a network. By using the OSI over
DCC communication, a network that consists of equipment from multiple vendors transparently
transmits management information at the network layer. Hence, the interconnection with the
equipment that supports OSI protocol from the third party is realized.

2 DCN Management Operation Guide for RTN NE Management
2.6 Configuring DCC Transparent Transmission

In the case of hybrid networking composed by equipment from Huawei and other vendors, the
service channel can be used to transparently transmit the DCC information to the third-party
network. The DCC information enters the service channel through the external clock interface
or the F1 data interface, and then reaches the third-party network over the related service channel.
In this way, the DCC information is transparently transmitted.
2.7 Modifying GNE Parameters
During the network optimization and adjustment, you may need to change the GNE type or
modify the communication address.
2.8 Changing the GNE for NEs
When the GNE that the non-gateway NE belongs to is changed and this non-gateway NE does
not belong to another GNE, you need to change the GNE to maintain the communication between
the NEs and the U2000. When the number of NEs managed by a certain GNE exceeds a certain
number (It is recommended that the number of non-gateway NEs that a GNE manages be no
more than 50 or 60 at most.), change the GNE for certain NEs so that the communication between
the U2000 and the NEs is not affected.
2.9 Configuring Standby GNEs for NEs
You can configure standby GNEs for NEs, to avoid service interruption due to GNE failure.
When the GNE for NEs fails, after an automatic switching to the standby GNE, the NEs are
connected to the U2000 through the standby GNE. During the switching of GNEs for NEs, the
communication may be interrupted transiently. But, this does not affect the services. You can
configure up to three standby GNEs for an NE.
2.10 Changing a GNE to a Normal NE
When you adjust the communication link between the GNE and the U2000, you can change the
GNE to a normal NE.
2.11 Changing a Normal NE to a GNE
When you adjust the communication link between the GNE and the U2000, you can change a
normal NE to a GNE.
2.12 Checking GNE Switching Status
If the active GNE of an NE fails, and the NE has a standby GNE, the NE automatically
communicates with the U2000 through the standby GNE. To detect the GNE communication
failure in time, you need to check the GNE switching status to ensure that the NEs communicate
correctly with the U2000 through the GNE.
2.13 Testing the Communication Between the U2000 and the GNE
When the network communication fails, you can view the communication between the GNE
and the U2000.
2.14 Checking the Network Communication Status
On some occasions, the U2000 cannot manage some NEs during the running of the network. By
checking the communication status of the network, you can learn the communication status
between the U2000 and NEs.

2.1 DCN Overview

The element management system (EMS) sets up communication with NEs through a data
communication network (DCN), to manage and maintain these NEs.
In a DCN, the EMS and NEs are both regarded as network nodes, which can be connected through
Ethernet or physical data communication channels (DCCs).
In practical networking, the EMS and NEs can be located on different floors in a building, in
different buildings, or even in different cities. Therefore, the connection between the EMS and
NEs usually requires an external DCN that is composed of equipment such as LAN switch and
routers. On the other hand, the DCN among NEs is referred to as an internal DCN. This section
describes the internal DCN composed of SDH NEs. See Figure 2-1.
Figure 2-1 DCN network
U2000
IP/OSI External
DCN DCN
HW ECC or
IP/OSI over
DCC
Internal DCN
OptiX NE
LAN switch
2.1.1 Background of DCN

With the development of network scale, OAM of a network becomes more and more difficult.
A stable and robust DCN management network helps lower the OAM cost.
2.1.2 DCN Solutions
The OptiX series equipment of Huawei provide multiple DCN solutions.
2.1.3 HWECC Features and Functions
To help the U2000 to manage NEs in a network, the embedded control channel (ECC) transmits
operation, administration and maintenance (OAM) information by using the D bytes.

2.1.4 HWECC Application

The ECC that Huawei implements provides a more flexible networking mode. The NEs can be
connected through an optical port or the Ethernet port for ECC communication. In some special
conditions, the Huawei equipment can transparently transmit the OAM information from the
third-party equipment.
2.1.5 Basic Concepts of IP over DCC
This section introduces the basic concept of IP over DCC.
2.1.6 Features and Functions of IP over DCC
IP over DCC has the functions and features that are different from the traditional DCC.
2.1.7 Application of IP over DCC
An Ethernet port is used to connect the U2000 and NEs. The NEs are connected to each other
through fibers or Ethernet.
2.1.8 Basic Concepts of OSI over DCC
This section introduces the basic concept of OSI over DCC.
2.1.9 Features and Functions of OSI over DCC
When a transmission network consists of equipment from multiple vendors, the OSI over DCC
transparently transmits the management information at the network layer, thereby offering
greater flexibility in networking. A user can use the existing DCC resources to uniformly manage
the equipment from multiple vendors without creating extra DCN channels.
2.1.10 Application of OSI over DCC
According to different network situations, OSI over DCC has two major applications.
2.1.1 Background of DCN

With the development of network scale, OAM of a network becomes more and more difficult.
A stable and robust DCN management network helps lower the OAM cost.
In a DCN, the DCC bytes in SDH overheads are used as physical channels for DCN management.
The customer does not need to set up private DCN channels so that the network construction
cost is greatly lowered. For a DCN, the SDH provides the following bandwidth:
l By using the D1-D3 bytes in SDH regenerator section overheads (RSOH), the SDH
provides a 192 kbit/s bandwidth for the DCN.
l By using the D4-D12 bytes in SDH multiplex section overheads (MSOH), the SDH
provides a 576 kbit/s bandwidth for the DCN.
l By using the D1-D12 bytes in SDH section overheads, the SDH provides a 768 kbit/s
bandwidth for the DCN.
Figure 2-2 shows the positions of DCC bytes in SDH overheads.

Figure 2-2 Positions of DCC bytes in SDH overheads
A1 A1 A1 A2 A2 A2 J0
B1 E1 F1 RSOH
D1 D2 D3
AU PTR
B2 B2 B2 K1 K2
D4 D5 D6
D7 D8 D9 MSOH
D10 D11 D12
S1 M1 E2
2.1.2 DCN Solutions

The OptiX series equipment of Huawei provide multiple DCN solutions.
The OptiX series equipment support the DCN networking by using the following three protocols:
l HWECC
l TCP/IP (IP over DCC)
l OSI (OSI over DCC)
The HWECC protocol is a private protocol developed by Huawei to support the DCN networking
of OptiX equipment. The HWECC protocol features easy configuration and application. As it
is private, the HWECC protocol does not meet the management requirements for hybrid
networking with equipment from other vendors.
The TCP/IP and OSI protocols are standard communication protocols that solve the management
issue in the case of hybrid networking with equipment from other vendors. These two protocols
can also be used in a network that is composed of only Huawei equipment.
NOTE
When OptiX equipment is interconnected with other vendors' equipment that does not support the TCP/IP
and OSI standard communication protocols, Huawei provides the transparent transmission function for
DCC bytes, and provides relevant Ethernet service channels to transparently transmit the OAM information.
2.1.3 HWECC Features and Functions

To help the U2000 to manage NEs in a network, the embedded control channel (ECC) transmits
operation, administration and maintenance (OAM) information by using the D bytes.
The HWECC protocol is mainly applied to transmit OAM information between Huawei optical
equipment. The HWECC protocol stake itself does not recognize the OAM information of the
third-party equipment. When the networking involves third-party equipment, the OAM
information cannot be interconnected but Huawei optical equipment can transparently transmit

the OAM information of the third-party equipment. Hence, customers can use the current DCC
resources to manage all equipment.
2.1.4 HWECC Application

The ECC that Huawei implements provides a more flexible networking mode. The NEs can be
connected through an optical port or the Ethernet port for ECC communication. In some special
conditions, the Huawei equipment can transparently transmit the OAM information from the
third-party equipment.
There are two typical applications of the HWECC protocol for networking schemes.
Application 1 Networking That Involves Only Huawei Equipment

Figure 2-3 shows the networking that involves only Huawei equipment.
Figure 2-3 Networking that involves only Huawei equipment
HUB1 NE HUB2
GNE1 NE6 NE7 NE12
NM 6
computer
NE2 NE5 NE8 NE11
Network cable
NE3 NE4 NE9 NE10
Subnet 1 Subnet 2
Fiber
Such networking requires that one gateway NE (GNE) be present for the communication
between other NEs and the U2000 through the Ethernet interface. The NEs communicate with
each other through an optical port or Ethernet interfaces. The subnetworks in Figure 2-3 perform
the extended ECC communication through Ethernet interfaces, such as NE6 and NE7.
NOTE
Extended ECC means the ECC communication by using the Ethernet when there is no connected optical
path between two or more NEs.
Application 2 Networking That Involves Huawei Equipment and Third-Party

Equipment
Figure 2-4 shows the networking that involves Huawei equipment and third-party equipment.

Figure 2-4 Networking that involves Huawei equipment and third-party equipment
HUB NE NE NE
Third-party NM
NE NE
Third-party
equipment
NE
NE NE NE
Huawei
equipment
NE
For such networking, the OAM information of the third-party equipment should travel through
Huawei equipment, which provides the function to transparently transmit the DCC. During the
transmission, Huawei equipment does not analyze the data. For the DCC transparent
transmission, perform the corresponding configuration at each NE along the data transmitting
trail.
2.1.5 Basic Concepts of IP over DCC

This section introduces the basic concept of IP over DCC.
IP over DCC
The IP over DCC protocol follows the TCP/IP protocol and is applied to control remote NEs
through the Internet. For the IP over DCC protocol, the D bytes (D1-D3 by default) of the
overhead are used for communication. Huawei optical equipment supports dynamic and static
routing.
OSPF
The open shortest path first (OSPF) protocol is a dynamic routing protocol based on the link
state. The NEs update the route table of each NE dynamically by using the OSPF protocol. The
OSPF protocol divides an autonomous domain into different areas so that routes are updated
within an area or between areas. Normally, the gateway NE (GNE) and all the non-gateway NEs
(non-GNEs) managed by it must be within the same OSPF area.
Remote Access
l Gateway NE mode: The ECC protocol is used. U2000 logs in to the GNE that is connected
to the computer. Then other NEs can be accessed through the NE ID. After the IP over
DCC feature is added, this mode can still be used to access remote NEs.
l Direct connection mode: The IP over DCC feature is used, and the remote NE can be
connected directly through the IP address. You just need to enter the destination IP address

in the login interface. For this mode, however, you need to add in advance the static route
or default gateway in the U2000 and the NE that needs to be accessed directly.
2.1.6 Features and Functions of IP over DCC

IP over DCC has the functions and features that are different from the traditional DCC.
The DCC is used to transmit the OAM (operation, maintenance, and administration) data
between NEs. The protocol stacks used by different vendors are not compatible with each other.
Thus, extra overhead bytes or service resources need to be allocated to transmit DCC data
transparently in a network composed of multi-vendor products.
The IP over DCC meets most of the networking requirements in existing networks without
occupying extra overhead bytes or service resources. The IP over DCC simplifies the network
structure, saves network resources, and meets the networking requirements quickly.
The IP over DCC supports the following features:
l Adopting the standard TCP/IP protocol, which makes it be compatible with other vendor's
equipment and simplifies the network management
l Adopting the forwarding function of the third layer in the protocol stack, which requires
extra overhead bytes or service paths
l Bringing flexible networking models
l Bringing simple upgrade modes and great compatibility. It is easy for IP over DCC to work
with new forwarding or multi-protocol features on the application layer
2.1.7 Application of IP over DCC

An Ethernet port is used to connect the U2000 and NEs. The NEs are connected to each other
through fibers or Ethernet.
Application 1: Gateway NE Mode

If the U2000 and the GNE connect to the same Ethernet (the U2000 and the GNE need to be in
the same subnet), and other NEs are accessed in the gateway NE mode, you need not to add any
static routes.
As shown in Figure 2-5, the U2000 with the IP address of 129.9.0.100 uses the nearby NE1 as
the GNE to access other NEs. You need not to add static routes on the U2000 or NEs.
Figure 2-5 Gateway NE mode

NM computer
IP address 129.9.0.100
NE4
Subnet mask 255.255.255.0
133.168.0.4
255.255.255.0
NE1 NE3
129.9.0.2 133.168.0.3
255.255.255.0 255.255.255.0
NE2
NE name 133.168.0.2
IP address 255.255.255.0
Subnet mask

Application 2: Gateway NE Mode (by Default Gateway)

If the U2000 is connected to the GNE through a router and other NEs are accessed in the gateway
NE mode, you need to add a default gateway on the U2000 and on the GNE.
As shown in Figure 2-6, the U2000 with the IP address of 10.100.11.12 connects with the GNE
(NE1) through a router and accesses other NEs in the gateway NE mode. In this case, you need
to set a default gateway on both the U2000 and NE1. Set the default gateway on the U2000 to
10.100.11.1, and that on NE1 to 129.9.0.254.
Figure 2-6 Gateway NE mode (by default gateway)

NM computer
IP address 10.100.11.12
Default gateway 10.100.11.1
10.100.11.1
255.255.255.0
Router NE4
133.168.0.4
129.9.0.254
255.255.255.0 255.255.255.0
NE1
NE3
129.9.0.2
133.168.0.3
255.255.255.0
255.255.255.0
NE name 129.9.0.254
IP address
Subnet mask NE2
255.255.255.0
Application 3: Direct Connection Mode (by Static Routes)

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

Figure 2-7 Direct connection mode (by static routes)

NM computer
Destination:
Static routes 133.168.0.0
Mask:
255.255.255.0 NE4
133.168.0.4
255.255.255.0
NE1 NE3
129.9.0.2 133.168.0.3
255.255.255.0 255.255.255.0
NE name NE2
Default gateway
Static routes
Application 4: Direct Connection Mode through a Router (by Static Routes)

The U2000 connects to the Ethernet port of a certain NE through a router and accesses other
NEs in the direct connection mode. You need to perform the following operations.
l On the U2000, set the static route to the GNE and non-GNEs.
l On the GNE, set the default route to the U2000.
l Add static routes to the U2000 on the destination station and the intermediate station.
As shown in Figure 2-8, the U2000 with the IP address of 10.100.11.12 connects to NE1 through
a router and accesses NE3 in the direct connection mode. Suppose the IP address of the
U2000 is 10.100.11.0 (subnet mask 255.255.255.0). Perform the listed operations:
l Add the static route on the U2000 to the gateway 129.9.0.2.
l Set the default gateway on NE1 to 129.9.0.254.
l Add the static route on NE2 to 10.100.11.0, with the next hop address as 129.9.0.2.
l Add the static route on NE3 to 10.100.11.0, with the next hop address as 133.168.0.2.

Figure 2-8 Direct connection mode through a router (by static routes)
NM computer
IP address 10.100.11.12
Static routes
Destination:129.9.0.2
Mask:255.255.255.0
Destination:133.168.0.0
Mask:255.255.255.0
10.100.11.1
255.255.255.0
NE4
Router 133.168.0.4
129.9.0.254 255.255.255.0
255.255.255.0 NE3
NE1 133.168.0.3
129.9.0.2 255.255.255.0
255.255.255.0 Static routes
129.9.0.254 Destination:10.100.11.0
Mask: 255.255.255.0
Next hop:133.168.0.2
NE2
NE name 133.168.0.2
IP address 255.255.255.0
Subnet mask Static routes
Default gateway Destination:10.100.11.0
Static routes Mask: 255.255.255.0
Next hop:129.9.0.2
Configuration Requirements
If NEs communicate with each other through IP over DCC, note the following rules for setting
the network scale. It is recommended that the number of non-gateway NEs (including the
extended ECC) that a GNE manages be no more than 50 or 60 at most.
If NEs communicate with each other through IP over DCC, note the following rules for setting
the IP address.
l If NEs communicate through IP addresses on the network layer, each NE need to have a
unique IP address to avoid routing error due to conflict.
l NEs support standard A, B, C types of IP addresses, that is, the IP address ranges from
1.0.0.1 to 223.255.255.254. The 127.x.x.x, a loopback address, cannot be used.
l The IP address must be used with the subnet mask. The subnet mask supports consecutive
masks in addition to natural masks, for example, 255.255.224.0.
l When the IP over DCC communication is used between a GNE and a non-GNE, the IP
addresses can be of different network sections.

l The GNE and non-GNEs cannot be in the same IP subnet. The NEs managed through the
same GNE can be in different IP subnets.
l Do not configure one GNE and one non-GNE into the same IP subnet.
l The Ethernets in the network must belong to different subnets. Otherwise, a routing error
will occur in the whole network. This is not allowed.
l The subnet masks of the NEs must be the same.
l The priority of static routes is higher than that of dynamic routes. If there is a conflict, static
routes take priority.
2.1.8 Basic Concepts of OSI over DCC

This section introduces the basic concept of OSI over DCC.
NSAP
The OSI protocol takes the network service access point (NSAP) address as the protocol
identification for nodes. The format of a simple NSAP address is shown in Figure 2-9.
Figure 2-9 Format of a simple NSAP address
AREA ID SYS ID NSEL
1-13 bytes 6 bytes 1 byte
AREA ID: The length is adjustable and ranges from 1 to 13 bytes. The AREA ID is used for L2
routing addressing within a domain. The values should be the same in the L1 route domain and
be different in the L2 route domain.
SYS ID: The length is fixed to six bytes. The SYS ID is used for route addressing within a
domain. For Huawei optical equipment, the former three bytes are fixed to 0x08003E and the
latter three bytes are the same with the NE ID.
NSEL: The NSEL value is fixed to 0x1D.
The AREA ID of Huawei optical equipment is 47000400060001.
The ISO8348/AD2 defines a complicated format of the NSAP address, as shown in Figure
2-10.
Figure 2-10 Format of a complicated NSAP address
IDP DSP
Higher-Order DSP
AFI IDI+pad DFI ORG RES RD AREA
Area Address SYS ID NSEL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

This manual does not cover the naming details and functions of each character in the NSAP
address format. For the OSI protocol, only the simple NSAP address format needs to be noticed.
Huawei equipment applies the simple NSAP address format, which does not affect the
interconnection between Huawei equipment and third-party equipment. The configuration of
the NSAP address requires that the AREA ID in the same domain should be the same.
l AFI: 47
l IDI: 0005
l DFI: 80
l ORG: 000000
l RES: 0000
l RD: 0001
l AREA: 0001
l SYS ID: 00206005FA68
l NSEL: 1D
When a networking involves Huawei equipment and third-party equipment within the same
domain, set the AREA ID to 4700058000000000000001 0001.
TP4
The TP4 protocol locates at the transport layer of the OSI protocol stake. The TP4 protocol is
applied to create a reliable communication connection. The TP4 protocol can handle the
problems as data packet loss, repetition and falsification, which are caused by network faults.
2.1.9 Features and Functions of OSI over DCC

When a transmission network consists of equipment from multiple vendors, the OSI over DCC
transparently transmits the management information at the network layer, thereby offering
greater flexibility in networking. A user can use the existing DCC resources to uniformly manage
the equipment from multiple vendors without creating extra DCN channels.
The OSI protocol supports the following three types of network nodes: ES (End System), L1-
IS (Level 1 Intermediate Systems) and L2-IS (Level 2 Intermediate Systems).
The ES only supports limited routing functions. To communicate with other network nodes, an
ES can only forward data packets to them by L1-IS or L2-IS that is directly connected to the ES
and has the routing function. As a result, only the nodes at the tips of a network rather than the
nodes amid a network are allowed to be set to ES. Because of the limited routing function that
may be an obstacle in network expansion, it is recommended not to set an NE to an ES during
the networking. The networking system of Huawei acts as an ES network node.
L1-IS is the default node type of Huawei optical network equipment. It only supports the routing
within an area, also known as Level 1 Routing. If a piece of equipment requires the routing
across multiple areas, also known as Level 2 Routing, you need to set the node type of the
equipment to L2-IS. An L2-IS-type node is in charge of two routing tables, one for intra-area
routing and the other one for inter-area routing.
2.1.10 Application of OSI over DCC

According to different network situations, OSI over DCC has two major applications.

Application 1 Third-Party Equipment Forwarding OAM Information of Huawei

Equipment
As shown in Figure 2-11, Huawei equipment locates at the edge of the network and third-party
equipment locates at the core. The third-party equipment forwards the OAM information
between Huawei equipment and the Huawei U2000. In this case, at least one GNE should be
configured in the subnet of the Huawei equipment.
Figure 2-11 Third-party equipment forwarding OAM information of Huawei equipment

Huawei NM Third-party NM
ES
OSI LAN
OSI DCN
Level 2 Routing
Area
GNE
Legacy Network
GNE
New Network Third-party NE
Huawei NE
Application 2 Huawei Equipment Forwarding OAM Information of Third-Party

Equipment
As shown in Figure 2-12, Huawei equipment locates at the core of the network while third-party
equipment at the edge. Huawei equipment forwards the OAM information between the third-
party NM and equipment.

Figure 2-12 Huawei equipment forwarding OAM information of third-party equipment

Huawei NM Third-party NM
ES
OSI LAN
OSI DCN
Level 2 Routing
Area
GNE
Legacy Network
GNE
New Network Third-party NE
Huawei NE
2.2 DCN Management Flow

This section describes operation tasks of creating and maintaining the DCN by using the
U2000. It also describes the relation between the operation tasks.
To configure and maintain the DCN, see the flow chart in Figure 2-13. During network
deployment, set up the communication between NEs according to the planned communication
mode. You can perform adjustment during the maintenance according to network situations.

Figure 2-13 DCN management flow

Required
Optional
Configuring ECC Configuring IP Over DCC Configuring OSI Over Common Maintenance
Communication Communication DCC Communication Operations
Modifying GNE
Modifying the NE ID Modifying the NE ID Modifying the NE ID
Parameters
Configuring an Setting NE Setting the NSAP Changing the GNE

Extended ECC Communication Address for an NE for NEs
Communication Parameters
Viewing the ECC Configuring the IP Configuring the Node Configuring Standby
Route for an NE Static Route for an Type for an NE GNEs for NEs
NE
Adding the Manual Customizing Configuring the Changing a GNE to a

ECC Route for an NE Communication Communication Normal NE
Channels Between Protocol Stack and
NEs LAPD Role for an
Customizing Optical Port
Changing a Normal
Communication Viewing the NE to a GNE
Channels Between Communication
NEs Status of DCC Configuring OSI
Channel Tunnel
Checking GNE
Configuring Switching Status
Communication for Querying the OSPF Customizing
Third-Party Protocol Status Communication
Equipment Channels Between Testing the
Interconnection NEs Communication
Configuring Proxy Between the NMS
ARP and the GNE
Configuring Querying the Route
Overhead Services Information of a Node
Checking the Network
Communication
Status
Creating an OSI GNE
2.3 Configuring ECC Communication

ECC configuration is simple. By default, all Huawei equipment support the ECC protocol and
the physical transmission channel is D1-D3 bytes. When the NE ID is set and fibers are
connected, the ECC communication is established without any configurations. If you want to
modify the ECC communication parameters, locally modify them. Do not remotely modify the
parameters because ECC communication may be interrupted and cannot be recovered. If you
have to remotely modify the parameters, start from the farthest end.
2.3.1 Modifying the NE ID

The ECC protocol uses the NE ID as the unique identifier of an NE. Hence, you need to assign
a unique NE ID to each NE when planning a network. If an NE ID conflicts with another NE
ID, it causes an ECC route conflict and the U2000 cannot manage certain NEs. During the
commissioning or expansion process, when you need to adjust the original network planning
and change NE IDs, you can use the U2000 to change NE IDs.

2.3.2 Configuring an Extended ECC Communication

You can establish an extended ECC communication between two shelves without fiber
connections through an Ethernet line. In this way, the U2000 manages the equipment in a
centralized manner.
2.3.3 Viewing the ECC Route for an NE
You can check whether the ECC route is correct. If the ECC route is incorrect, you need to re-
configure it.
2.3.4 Adding the Manual ECC Route for an NE
If the ECC route of an NE is inconsistent with the planned route, you can modify the ECC route
by manually adding it.
2.3.5 Customizing Communication Channels Between NEs
NEs communicate with each other through data communications channel (DCC). To meet the
requirements of the network management in a complex network, you can configure D1-D3, D4-
D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC
rate and allocate DCC resources according to DCC channel types.
2.3.6 Configuring Communication for Third-Party Equipment Interconnection
In the case of multi-vendor networking, you need to allocate the DCC bytes of Huawei's
equipment to ensure that the bytes are transmitted transparently.

Prerequisite
l You must be an NM user with "NE operator" authority or higher.
l The NE must be created.
Precautions
CAUTION
Modifying the NE ID may interrupt NE communication and reset the NE.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
Step 3 Enter the New ID and the New Extended ID. Click OK.

Step 4 Click OK in the Warning dialog box.
----End
2.3.2 Configuring an Extended ECC Communication

You can establish an extended ECC communication between two shelves without fiber
connections through an Ethernet line. In this way, the U2000 manages the equipment in a
centralized manner.
Prerequisite
l NEs are properly connected with crossover cables.
Context
CAUTION
This operation may restore the settings of communication, and may interrupt services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > ECC Management from the
Function Tree.
Step 2 Select the ECC Extended Mode.
If you set ECC Extended Mode to Then
Auto mode You need not set other parameters.

If you set ECC Extended Mode to Then
Specified mode If the NE serves as the server, set Port in the Set
Server.
If the NE serves as the client, set Opposite IP and
Port in the Set Client area.
NOTE
l Some NEs can be set as the server and client at the same
time.
l If you need to set the NE as the server and client at the
same time, the port number when the NE serves as the
server cannot be duplicate with the port number when the
NE serves as the client.
NOTE
l Auto mode: Establish an extended ECC connection automatically. Though this mode is convenient,
extra connections will be established and the resource availability is low. It is recommended when there
are less than four NEs. No extended ECC can be established automatically unless both the NEs between
which an extended ECC is to be established are set to the automatic mode.
l Specified mode: Specifies that an extended ECC is to be established between the server and the client.
The connection is highly reliable and the bandwidth availability is high. This mode is usually used to
establish an extended ECC connection.
l For an NE, the two modes cannot be used at the same time to extend ECC.
Step 3 Click Apply and the Warning dialog box is displayed. Click OK.
----End
Postrequisite
After you complete the settings for one NE, you need to configure the settings for the opposite
NE to enable the extended ECC communication. Note the following points:
l If you set ECC Extended Mode to Auto mode for an NE, configure the same settings for
the opposite NE.
l If you set ECC Extended Mode to Specified mode for an NE, configure the same settings
for the opposite NE. In addition, the roles of the two NEs must be different. That is, if an
NE serves as the server, the opposite NE must be the client.
2.3.3 Viewing the ECC Route for an NE

You can check whether the ECC route is correct. If the ECC route is incorrect, you need to re-
configure it.
Prerequisite

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > NE ECC Link
Management from the Function Tree.
Step 2 Click Refresh and the ECC route for an NE is displayed in the NE ECC Link Management
Table.
----End
2.3.4 Adding the Manual ECC Route for an NE

If the ECC route of an NE is inconsistent with the planned route, you can modify the ECC route
by manually adding it.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > NE ECC Link
Step 2 Click Add Manual Route and the Add Manual Route dialog box is displayed. Set Destination
NE, Transfer NE, Distance and Level.
Step 3 Click OK. and then click Close in the Operation Result dialog box.
----End

Prerequisite
Context
The NE uses D1-D3 as the DCC by default to communicate through the DCC.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the
Function Tree.
Step 2 Click the DCC Rate Configuration tab, click New. Set Port, Channel Type and Protocol
Type in the dialog box that is displayed.
Step 3 Click OK and then click Close in the Operation Result dialog box.
----End

2.3.6 Configuring Communication for Third-Party Equipment

Interconnection
Prerequisite
Context
In the case of multi-vendor networking, the DCC bytes of the equipment from other vendors are
transmitted transparently. You can allocate the DCC bytes of Huawei's equipment through the
idle DCC bytes of the third-party's equipment so that the bytes are transmitted transparently.
This may occur in one of the following three ways:
l Huawei's equipment is in the network center, while a third party's equipment is at the edge
of the network. The Huawei equipment and third-party equipment are managed by their
respective network management systems by using the D1 to D3 bytes. In this case, Huawei's
equipment transparently transmits the third party's DCC bytes through three consecutive
bytes between D4 and D12.
l Huawei's equipment is at the edge of the network, while a third party's equipment is in the
network center. The Huawei equipment and third-party equipment are managed by their
equipment adjusts its own D1-D3 bytes to three consecutive bytes between D4 and D12.
Hence, Huawei's equipment transparently transmits the network management information
through the third-party's equipment.
l Huawei's equipment also transparently transmits the other overhead bytes, for example,
E2, F1, or X1-X4, through the idle D bytes.
For the DCC transparent transmission, perform the corresponding configuration at each NE
along the data transmitting trail.
Procedure
Step 1 In the NE Explorer, click an NE and choose Communication > DCC Management from the
Function Tree. Click the DCC Transparent Transmission Management tab.
Step 2 Click Create and the Create DCC Transparent Transmission Byte dialog box is displayed.
Select the source and the sink timeslot, port and overhead bytes.
----End
2.4 Configuring IP Over DCC Communication

The IP over DCC communication transmits DCC data by the using IP data packets. The IP over
DCC directly operates and maintains remote NEs by using standard TCP/IP protocol. In addition,
it realizes the application functions, such as FTP, Telnet, and SNMP. As essential parts of the
IP over DCC communication, the dynamic and static routing protocols are used to create route
information.


In the commissioning or expansion process, when you need to adjust the original planning and
change the NE ID, you can use the U2000 to achieve it.
2.4.2 Setting NE Communication Parameters
When configuring the IP Over DCC communication, you need to set the parameters including
IP, Subnet Mask, Gateway IP, Extended ID, and Connection Mode for the NE.
2.4.3 Configuring the IP Static Route for an NE
A static route forwards the data between NEs, or between a router and the computer where the
U2000 is installed.
2.4.5 Viewing the Communication Status of DCC Channel
You can view the communication status of DCC channel.
2.4.6 Querying the OSPF Protocol Status
You can query the Open Shortest Path First (OSPF) protocol status.
2.4.7 Configuring Proxy ARP
The address resolution protocol (ARP) helps you to query the MAC address of the destination
equipment using its IP address. If you enable proxy ARP for a GNE, the GNE can answer ARP
requests for other non-gateway NEs, so that you can set IP addresses of NEs of the same network
in the same network segment.

Prerequisite
Context
CAUTION
Modifying the NE ID may interrupt NE communication.
Procedure
Tree.

----End
2.4.2 Setting NE Communication Parameters

Prerequisite
l The IP GNE must be created.
Context
CAUTION
The operation of modifying the NE communication parameters interrupts the communication
and affects the services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication
Parameters from the Function Tree.
Step 2 Set the NE communication parameters, including IP, Subnet Mask, Gateway IP, Extended
ID, NSAP Address.
Step 3 Click Apply and then click OK in the Warning dialog box that appears twice. in the Warning
dialog box that appears twice. Click Close in the Operation Result dialog box.
----End
2.4.3 Configuring the IP Static Route for an NE

A static route forwards the data between NEs, or between a router and the computer where the
U2000 is installed.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > IP Protocol Stack
Management from the Function Tree. Click the IP Route Management tab.
Step 2 Click New and the Create an IP Route dialog box is displayed. Set the Destination Address,
Subnet Mask and Gateway.

----End

Prerequisite
Context
Procedure
Function Tree.
----End
2.4.5 Viewing the Communication Status of DCC Channel

You can view the communication status of DCC channel.
Prerequisite
Procedure
Function Tree. Click the DCC Rate Configuration tab.
Step 2 Click Query, and view the communication status of DCC channel.
----End

2.4.6 Querying the OSPF Protocol Status

You can query the Open Shortest Path First (OSPF) protocol status.
Prerequisite
Context
OSPF is a link-state, hierarchical IGP routing algorithm . OSPF features include least-cost
routing, multipath routing, and load balancing. OSPF was derived from an early version of the
IS-IS protocol.
Procedure
Management from the Function Tree. Click the OSPF Parameter Settings tab.
Step 2 Click Query to check if the OSPF protocol status is normal.
----End
2.4.7 Configuring Proxy ARP

The address resolution protocol (ARP) helps you to query the MAC address of the destination
equipment using its IP address. If you enable proxy ARP for a GNE, the GNE can answer ARP
requests for other non-gateway NEs, so that you can set IP addresses of NEs of the same network
in the same network segment.
Prerequisite
Procedure
Management from the Function Tree. Click the Proxy ARP tab.
Step 2 Optional: Click Query.
Step 3 Set Value to Disabled or Enabled from the drop-down list.
Step 4 Click Apply.
----End
Postrequisite
After you enable proxy ARP, you need to create a static route for each NE.
2.5 Configuring OSI Over DCC Communication

The OSI protocol is a widely used communication protocol in a network. By using the OSI over
DCC communication, a network that consists of equipment from multiple vendors transparently

transmits management information at the network layer. Hence, the interconnection with the
equipment that supports OSI protocol from the third party is realized.

2.5.2 Setting the NSAP Address for an NE
If the U2000 sets up a TP4 connection with an NE, after you modify the NSAP address range
that was previously set according to network planning, the communication between the
U2000 and the GNE is interrupted, so you need to re-create the communication. You can use
the U2000 to create a TCP connection with an NE, set the NSAP address range for the NE, and
then modify the connection mode between the U2000 and the NE to TP4.
2.5.3 Configuring the Node Type for an NE
Based on the network planning, you can set the node type to ES, L1 IS or L2 IS for an NE. For
easy expansion of the network, avoid the ES type.
2.5.4 Configuring the Communication Protocol Stack and LAPD Role for an Optical Port
The default protocol stack enabled for optical ports on an NE depends on products. If the current
protocol stack enabled for an optical port differs from the planned one, you can configure it on
the U2000. If an optical port uses the OSI protocol stack, the link access procedure on the D
channel (LAPD) role of all optical ports is User by default. You can set the LAPD role for each
optical port based on network planning. The local LAPD role depends on the remote LAPD role.
Ensure that the two LAPD roles are different.
2.5.5 Configuring OSI Tunnel
When the OSI-protocol-based third-party equipment needs to transfer information through an
IP network that consists of Huawei equipment, you can create a virtual OSI tunnel to
transparently transmit the information.
2.5.7 Querying the Route Information of a Node
After you finish configuring and connecting the fibers, you can check whether the route
information of each node is correct. If the route information is correct, it means that the nodes
can normally communicate with each other.
2.5.8 Creating an OSI GNE
After you configure the NSAP address of an NE, you can create an OSI GNE in the TP4
connection mode.

Prerequisite

Context
CAUTION
Modifying the NE ID may interrupt NE communication.
Procedure
Tree.
----End
2.5.2 Setting the NSAP Address for an NE

If the U2000 sets up a TP4 connection with an NE, after you modify the NSAP address range
that was previously set according to network planning, the communication between the
U2000 and the GNE is interrupted, so you need to re-create the communication. You can use
the U2000 to create a TCP connection with an NE, set the NSAP address range for the NE, and
then modify the connection mode between the U2000 and the NE to TP4.
Prerequisite
Procedure
Step 2 Set the NSAP Address.
Step 3 Click Apply.
Step 4 Choose Administration > DCN Management from the main menu. Click the GNE tab.
Step 5 Right-click a GNE and choose Modify GNE from the shortcut menu.
Step 6 In the Modify GNE dialog box, select OSI Gateway from the Gateway Type drop-down list,
and enter the NSAP Address.

----End
2.5.3 Configuring the Node Type for an NE

Based on the network planning, you can set the node type to ES, L1 IS or L2 IS for an NE. For
easy expansion of the network, avoid the ES type.
Prerequisite
Context
CAUTION
Setting the Configuration Role of an NE may cause service interruption.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > OSI Management from the
Function Tree. Click the Network Layer Parameters tab.
Step 2 Double-click the Configuration Role and select a node type from the drop-down list.
Step 3 Click Apply and click OK in the Confirm dialog box. dialog box. Then, click Close in the
Operation Result dialog box.
----End

2.5.4 Configuring the Communication Protocol Stack and LAPD

Role for an Optical Port
The default protocol stack enabled for optical ports on an NE depends on products. If the current
protocol stack enabled for an optical port differs from the planned one, you can configure it on
the U2000. If an optical port uses the OSI protocol stack, the link access procedure on the D
channel (LAPD) role of all optical ports is User by default. You can set the LAPD role for each
optical port based on network planning. The local LAPD role depends on the remote LAPD role.
Ensure that the two LAPD roles are different.
Prerequisite
Procedure
Function Tree. Click the DCC Rate Configuration tab.
Step 3 Select the optical port you want to set and click Delete.
Step 4 Click New and set parameters in the Create dialog box.
Step 5 Click OK.
----End
2.5.5 Configuring OSI Tunnel

When the OSI-protocol-based third-party equipment needs to transfer information through an
IP network that consists of Huawei equipment, you can create a virtual OSI tunnel to
transparently transmit the information.
Prerequisite
Context
As OSI tunnel is an end-to-end function, you must configure this function at both ends of a
tunnel.

Procedure
Function Tree. Click the OSI Tunnel tab.
Step 2 Click New. In the Create OSI Tunnel window, set Remote IP Address and LAPD Actor.
NOTE
LAPD Actor refers to the LAPD role at an end. When setting this parameter, you must configure different
roles for the two ends of a tunnel.
Step 4 Set the parameters in the LAPD Parameter pane.
NOTE
Set the same parameter settings for both ends of a tunnel.
Step 5 Click Apply and then click Close in the Operation Result dialog box.
----End

Prerequisite
Context
Procedure
Function Tree.
----End
2.5.7 Querying the Route Information of a Node

After you finish configuring and connecting the fibers, you can check whether the route
information of each node is correct. If the route information is correct, it means that the nodes
can normally communicate with each other.
Prerequisite
You must be an NM user with "NE monitor" authority or higher.

Procedure
Function Tree. Click the Routing Table tab.
Step 2 Optional: Click Refresh to query the route information on the NE.
Step 3 View the information in the Link Adjacency Table and ensure that the information is correct.
Step 4 Click the L1 Routing and the L2 Routing tabs to check if the respective route information is
correct.
----End
2.5.8 Creating an OSI GNE

After you configure the NSAP address of an NE, you can create an OSI GNE in the TP4
connection mode.
Prerequisite
Procedure
Step 1 Choose File > Create > NE from the main menu.
Step 2 In the Add Object dialog box, select the NE type from the Object Type tree. Enter the ID,
Extended ID, Name and Remarks.
Step 3 Select Gateway from the Gateway Type drop-down list.
Step 4 Select OSI from the Protocol drop-down list.
Step 5 Enter the NSAP Address of the GNE.
NOTE
The NSAP address consists of hexadecimal digits of up to 20 bytes, and its format is: domain address
+08003e+NE ID+NSEL. The domain address is composed of 13 bytes and is entered by the user. The
NSEL is the port number of the network-layer protocol, with a fixed value of 1d (one byte).
Step 6 Enter the NE user and password.

NOTE
The default NE user of the U2000 must be root, and the default password is password.
Step 7 Click OK. Click on the Main Topology and the NE icon is displayed in the position where you
click.
NOTE
If the NE is not created properly or the communication between the NE and the U2000 is abnormal, the
NE is displayed in gray.
----End
2.6 Configuring DCC Transparent Transmission

In the case of hybrid networking composed by equipment from Huawei and other vendors, the
service channel can be used to transparently transmit the DCC information to the third-party

network. The DCC information enters the service channel through the external clock interface
or the F1 data interface, and then reaches the third-party network over the related service channel.
In this way, the DCC information is transparently transmitted.
2.6.1 Configuring Communication for Third-Party Equipment Interconnection

2.6.2 Configuring DCC Transparent Transmission Through External Clock Interfaces
If a third-party network exists between networks composed of Huawei equipment, the external
clock interfaces can be used to transparently transmit the DCC information. In this way, the
U2000 can uniformly manage the networks composed of Huawei equipment.
2.6.3 Configuring DCC Transparent Transmission Through F1 Data Interfaces
You can configure the F1 data interface on the SCC board, to transparently transmit the data
communication channel (DCC) information between back-to-back NEs.
2.6.1 Configuring Communication for Third-Party Equipment

Interconnection
Prerequisite
Context
In the case of multi-vendor networking, the DCC bytes of the equipment from other vendors are
transmitted transparently. You can allocate the DCC bytes of Huawei's equipment through the
idle DCC bytes of the third-party's equipment so that the bytes are transmitted transparently.
This may occur in one of the following three ways:
l Huawei's equipment is in the network center, while a third party's equipment is at the edge
of the network. The Huawei equipment and third-party equipment are managed by their
equipment transparently transmits the third party's DCC bytes through three consecutive
bytes between D4 and D12.
l Huawei's equipment is at the edge of the network, while a third party's equipment is in the
network center. The Huawei equipment and third-party equipment are managed by their
equipment adjusts its own D1-D3 bytes to three consecutive bytes between D4 and D12.
Hence, Huawei's equipment transparently transmits the network management information
through the third-party's equipment.
l Huawei's equipment also transparently transmits the other overhead bytes, for example,
E2, F1, or X1-X4, through the idle D bytes.
For the DCC transparent transmission, perform the corresponding configuration at each NE
along the data transmitting trail.

Procedure
Step 1 In the NE Explorer, click an NE and choose Communication > DCC Management from the
Function Tree. Click the DCC Transparent Transmission Management tab.
Step 2 Click Create and the Create DCC Transparent Transmission Byte dialog box is displayed.
Select the source and the sink timeslot, port and overhead bytes.
----End
2.6.2 Configuring DCC Transparent Transmission Through

External Clock Interfaces
If a third-party network exists between networks composed of Huawei equipment, the external
clock interfaces can be used to transparently transmit the DCC information. In this way, the
U2000 can uniformly manage the networks composed of Huawei equipment.
Prerequisite
l The 2M external clock interface signals must be accessed to the E1 tributary board through
a cable.
Context
As shown in Figure 2-14, when a third-party network exists, external clock interfaces can be
used to transmit DCC information. In this way, the U2000 can configure and manage ring 2.
Figure 2-14 External clock interfaces used to transparently transmit DCC information (example)
NMS
NE1 NE2
Third Party
Ring 1 Transport Ring 2
network
DCC DCC
NOTE
If the third-party network does not exist, you can use a cable to connect the external clock interfaces of NE1
and NE2 to transparently transmit the DCC information.
Figure 2-15 shows how to connect NE1 and NE2. Through the third-party network, NE1 and
NE2 can exchange E1 (DCC) signals.

Figure 2-15 External clock interfaces used to transparently transmit DCC information (example)
SDH processing SDH processing
NE1 board board NE2
Third-party
network
External External
clock PDH processing clock PDH processing
interface board interface board
E1(DCC) E1(DCC)
The network planning is as follows:
NOTE
l The external clock interfaces of NE1 and NE2 are connected to the first interface of the tributary board.
l Configure a bidirectional cross-connection between the first VC-12 timeslot of the tributary board and the
first VC-12 timeslot in the first VC-4 of the line board.
l The RTN equipment can be connected to the third-party network by using the line board or intermediate
frequency (IF) board.
Procedure
Step 1 Configure the DCC transparent transmission through the external clock interface of NE 1.
1. In the NE Explorer, click an NE and choose Communication > DCC Management from
the Function Tree.
2. Click DCC Rate Configuration. Click Create. In the Create dialog box displayed, select
an external clock interface and set the parameters such as the channel type and protocol
type. Click OK. Then, in the Operation Result dialog box, click Close.
3. Select the external clock interface and set its enabling status to Enabled.
4. Click Apply. The Operation Result dialog box is displayed indicating that the operation
was successful. Click Close.
Step 2 Configure a bidirectional cross-connection between the tributary board and the line board.
Step 3 Disable the DCC communication of the line board interconnected with the third-party network.
1. Select the port of the corresponding line board, click Enable Status, and select Disable.
The Warning dialog box is displayed.
2. Click OK.
3. Click Apply. The Confirmation dialog box is displayed.
4. Click OK. The Operation Result dialog box is displayed indicating that the operation was
successful.
Step 4 Follow Steps 1 to 3 to perform the configuration on NE2.
----End

2.6.3 Configuring DCC Transparent Transmission Through F1 Data

Interfaces
You can configure the F1 data interface on the SCC board, to transparently transmit the data
communication channel (DCC) information between back-to-back NEs.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Orderwire from the Function
Tree.
Step 2 Click the F1 tab.
Step 3 In the Available Data Channel area, select two data channels and click .
Step 4 Click Apply. In the Operation Result dialog box displayed, click Close.
----End
2.7 Modifying GNE Parameters

Prerequisite
Precautions
CAUTION
This operation is risky, because it may interrupt the communication.
Procedure
Step 2 Select the GNE to be modified, right-click and choose Modify GNE from the shortcut menu.
Step 3 In the Modify GNE dialog box displayed, set Gateway Type.
l When Gateway Type is set to IP Gateway, modify IP Address.

l When Gateway Type is set to OSI Gateway, modify NSAP Address.
NOTE
l Do not modify the Port No..

l Make sure that the IP address of the GNE is in the same network segment as the IP address of the
U2000. If they are not in the same network segment, set the corresponding network ports, to make sure
that the U2000 can log in to the GNE.
Step 4 Click OK. In the Operation Result dialog box that is displayed, click Close.
----End
2.8 Changing the GNE for NEs

Prerequisite

Precautions
CAUTION
This operation may interrupt the NE communication.
Procedure
Step 1 Choose Administration > DCN Management from the main menu.
Step 2 Click the NE tab.
Step 3 Select an NE. Double-click the Primary GNE1 field and select a GNE from the drop-down list.
Step 4 Click Apply. Click Close in the Operation Result dialog box.
Step 5 Click Refresh. Test the modification with reference to Checking the Network Communication
Status.
----End
2.9 Configuring Standby GNEs for NEs

You can configure standby GNEs for NEs, to avoid service interruption due to GNE failure.
When the GNE for NEs fails, after an automatic switching to the standby GNE, the NEs are
connected to the U2000 through the standby GNE. During the switching of GNEs for NEs, the
communication may be interrupted transiently. But, this does not affect the services. You can
configure up to three standby GNEs for an NE.
Prerequisite
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the NE tab.
Step 2 Select an NE. Double-click GNE2 and select a GNE from the drop-down list.

l To configure multiple standby GNEs, select a GNE from the GNE3 and GNE4 drop-down
lists.
l When the active GNE and standby GNEs fail one by one, the switching sequence is Primary
GNE1, GNE2, GNE23, and GNE4.
l You can select multiple lines at a time to set standby NEs in batches.
----End
2.10 Changing a GNE to a Normal NE

When you adjust the communication link between the GNE and the U2000, you can change the
GNE to a normal NE.
Prerequisite
Context
CAUTION
This operation may interrupt the service.
Procedure
Step 2 Right-click the GNE that you want to change and choose Delete GNE from the shortcut menu.
Click OK in the Confirm and Reconfirm dialog box. Click Close in the Operation Result
dialog box.
----End
Postrequisite
After changing the GNE to a normal NE, modify the attributes of the NE that uses the GNE and
select another GNE.

2.11 Changing a Normal NE to a GNE

When you adjust the communication link between the GNE and the U2000, you can change a
normal NE to a GNE.
Prerequisite
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the NE tab.
Step 2 Right-click a normal NE and choose Change to GNE from the shortcut menu.
Step 3 Click OK. Click Close in the Operation Result dialog box.
NOTE
The NE is now changed to a GNE and appears in the GNE tab.
----End
2.12 Checking GNE Switching Status

Prerequisite
The active and standby GNEs must be created for an NE.
Procedure
Step 3 Click Refresh to query the GNE switching status.
----End
2.13 Testing the Communication Between the U2000 and the

GNE
When the network communication fails, you can view the communication between the GNE
and the U2000.

Prerequisite
Procedure
Step 2 Right-click the GNE to be tested and choose Test GNE from the shortcut menu.
Step 3 Click Close in the Operation Result dialog box.
----End

Prerequisite
Context
l When an NE uses IP over DCC, to check the NE communication status by using the ping
function, you can right-click the NE on the Main Topology and choose Ping from the
shortcut menu.
l You can use the ping function after installing the OSI software on the NE that uses OSI
over DCC and the computer where the U2000 resides.
Procedure
l Check the communication status between the U2000 and a non-gateway NE.
1. Choose Administration > DCN Management from the main menu.
2. Click the NE tab. Click Refresh to view the communication status of all NEs.
3. Select an NE. Right-click in the Communication Status column and choose Test
NE from the shortcut menu.
4. The Operation Result dialog box is displayed indicating the test result of the non-
gateway NE.
l Check the communication status between the U2000 and the GNE.
2. Click the GNE tab. Click Refresh to view the communication status of the GNE.
3. Right-click an NE and choose Test GNE from the shortcut menu.
4. The Operation Result dialog box is displayed indicating the test result of the GNE.
----End
2.14.1 Overview of the Inband DCN

Inband DCN refers to the networking mode that uses service paths provided by the managed
equipment to realize the management of network equipment. In this mode, the network
management information is transmitted over service paths of the equipment.
2.14.2 Basic Concepts
The DCN contains two networking modes, which are inband networking and outband
networking.
2.14.3 Application of the Inband DCN
When no special DCN is available for transmitting network management information, you can
perform the networking in the inband DCN mode.
2.14.4 Configuring an Inband DCN
This section describes how to configure an inband DCN.
2.14.1 Overview of the Inband DCN

Inband DCN refers to the networking mode that uses service paths provided by the managed
equipment to realize the management of network equipment. In this mode, the network
management information is transmitted over service paths of the equipment.
Objectives and Benefits

A characteristic of the inband DCN mode is the convenient and flexible networking that does
not require additional equipment. In this mode, you need not separately provide a network for
the DCN and thus save the operation cost.
Realization Principle
As shown in Figure 2-16, in the inband DCN mode, the DCN information and service
information share the same path for transmission.
Figure 2-16 Inband DCN networking mode

NMS
Ethernet Link Ethernet Link
Service
DCN information


The DCN contains two networking modes, which are inband networking and outband
networking.
Inband DCN Scheme

The inband DCN networking involves using the service channels provided by the managed
devices to manage the devices in the network. In this mode, the network management
information is transmitted through the service channels of the devices.
The inband DCN networking is flexible and does not require additional devices. Figure 2-17
shows the networking diagram.
Figure 2-17 Inband networking scheme
Managed network
Firewall
NOTE
l The devices managed by the U2000 are connected to the IP core network. The NMS center only needs
to be connected to the nearby IP devices in the IP core network. You can manage all the devices in the
network by configuring the route.
l The mode of connection between the NMS center and the IP core network is based on the location of
the IP devices near the NMS center. If the U2000 and the nearby IP device are in the same equipment
room, you can adopt the LAN networking mode. In the case of the long distance transmission, the
networking is realized through private line services.
Outband Networking Scheme

The outband networking scheme involves using other channels except service channels to
transmit the network management information and thus realizing the network management.
Compared with the inband networking, the outband working scheme provides more reliable
management channels. When faults occur on the service channels, you can obtain the network
management information in time and perform the real-time monitoring.
In the outband mode, you need provide a dedicated communication channel as the maintenance
channel that is unrelated to the service channel.
In the outband networking scheme, the NMS center can set up the DCN network with the
equipment managed in various ways, such as the E1 private line or Ethernet. The U2000 manages
the equipment within the management range through the DCN network. Figure 2-18 shows the
networking diagram.

Figure 2-18 Outband networking scheme
DCN
Firewall
Managed network
NOTE
The U2000 uses the dedicated communication channels to transmit the management information to the
managed networks.
2.14.3 Application of the Inband DCN

When no special DCN is available for transmitting network management information, you can
perform the networking in the inband DCN mode.
When network management information is transmitted through Ethernet ports, the NE

distinguishes between network management information and service information by special
VLAN ID. When network management information is transmitted through E1 ports, the NE
distinguishes between network management information and service information by special
MPLS tag.
2.14.4 Configuring an Inband DCN

This section describes how to configure an inband DCN.
Context
The configuration of an inband DCN includes the following contents:
2.14.4.1 Setting NE Communication Parameters
2.14.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN

The RTN equipment communicates with the U2000 in inband DCN mode. The network
management information is transmitted with the service information, and the equipment marks
the management information with a default VLAN ID. You can adjust the bandwidth of an
inband DCN.
2.14.4.3 Setting the U2000 Access Parameters
In the case of the traditional DCN network, the equipment accesses to the U2000 through the
SCC board. The RTN equipment can also access to the U2000 through the network interface of
the Ethernet board. When the RTN equipment accesses to the U2000 by using the network
interface of the Ethernet board, set the access parameters of the Ethernet board for the equipment
to communicate with the U2000.
2.14.4.4 Enabling the Port DCN
The NM information can be transported in the inband DCN only when the DCN access function
is enabled for the ports at two ends of the link.
2.14.4.5 Enabling the Tunnel DCN
The NM information can be transported in the IP/GRE Tunnel only when the DCN access
function is enabled for the IP/GRE tunnel.
2.14.4.1 Setting NE Communication Parameters

Prerequisite
l The IP GNE must be created.
Context
CAUTION
The operation of modifying the NE communication parameters interrupts the communication
and affects the services.
Procedure
Step 2 Set the NE communication parameters, including IP, Subnet Mask, Gateway IP, Extended
ID, NSAP Address.
Step 3 Click Apply and then click OK in the Warning dialog box that appears twice. in the Warning
dialog box that appears twice. Click Close in the Operation Result dialog box.
----End

2.14.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN

The RTN equipment communicates with the U2000 in inband DCN mode. The network
management information is transmitted with the service information, and the equipment marks
the management information with a default VLAN ID. You can adjust the bandwidth of an
inband DCN.
Prerequisite
Context
l If the default VLAN ID of the DCN conflicts with the VLAN ID used by the service,
manually modify the VLAN ID of the DCN to ensure that the networkwide DCN uses the
same VLAN ID.
l If the DCN packets do not use all the available bandwidth, the idle bandwidth can be shared
with the service packets.
l It is recommended to perform the modification on non-gateway NEs and then the gateway
NE, to prevent the non-gateway NEs from being unreachable to the U2000.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the
Function Tree.
Step 2 Click the Bandwidth Management tab, and enter parameters.

NOTE
When setting the parameters, note the following points:
l Click Default to adopt the default value.
l Generally, use the default VLAN ID. When the VLAN ID used by a service conflicts with that used
by a DCN channel, you can define another VLAN ID. Make sure that the networkwide VLAN ID is
consistent.
Step 3 Click Apply.
----End
2.14.4.3 Setting the U2000 Access Parameters

In the case of the traditional DCN network, the equipment accesses to the U2000 through the
SCC board. The RTN equipment can also access to the U2000 through the network interface of
the Ethernet board. When the RTN equipment accesses to the U2000 by using the network
interface of the Ethernet board, set the access parameters of the Ethernet board for the equipment
to communicate with the U2000.
Prerequisite

Context
NOTE
l You need to set the parameters only when the U2000 accesses the equipment by using an Ethernet
service board.
l By default, the Enabled Status is Disabled.
CAUTION
In the case of the OptiX RTN equipment, when the DCN port is interconnected to the U2000,
the IP address of the U2000 and the IP address of the NNI should not be set to the same subnet.
This operation may affect the communication between the U2000 and NEs.
Procedure
Function Tree.
Step 2 Click the Access Control tab, and enter parameters.
Step 3 Click Apply.
----End
2.14.4.4 Enabling the Port DCN

The NM information can be transported in the inband DCN only when the DCN access function
is enabled for the ports at two ends of the link.
Prerequisite
Procedure
Function Tree.
Step 2 Click the Port Settings tab.
Step 3 Select different interface types, and set the corresponding attributes.
NOTE
Take the following precautions when enabling the DCN:

l When you configure an Ethernet service that exclusively uses a port, disable the DCN function of the
port.
l When an E1 port accesses the CES and IMA services, disable the DCN function of the port.
l After you enable DCN for an port, the VLAN IDs of other services configured for the port cannot be
the same as the VLAN IDs of DCN packets.
Step 4 Click Apply.
----End

2.14.4.5 Enabling the Tunnel DCN

The NM information can be transported in the IP/GRE Tunnel only when the DCN access
function is enabled for the IP/GRE tunnel.
Prerequisite
Procedure
Function Tree.
Step 2 Click the Tunnel Settings tab.
Step 3 Select different tunnel types, and set the corresponding attributes.
Step 4 Click Apply.
----End

Operation Guide for RTN NE Management 3 Configuring Clocks
3 Configuring Clocks
About This Chapter
A clock is the basis for the normal running of NEs. You must configure clocks for all NEs prior
to configuring services. In addition, you need to configure clock protection for complex
networks.
3.1 Clock Configuration Process
This section describes the process of clock configuration based on a flow chart.
3.2 Clock Synchronization Scheme
This section describes the clock synchronization schemes. You need choose the clock
synchronization scheme according to the actual networking architecture.
3.3 Basic Concepts
Before clock configuration, you need to master the basic concepts.
3.4 Viewing Clock Synchronization Status
If the clocks between NEs in the network are not synchronous, the pointer justification, bit error,
even service interruption may occur on NE. Using the U2000, you can learn and monitor the
synchronization status of the NE clocks.
3.5 Viewing the Clock Tracing Status
Correct clock tracing relationships are critical to ensure the clock synchronization within the
entire network. Using the U2000, you can monitor the clock trace status of each NE.
3.6 Configuring the Clock Sources
This topic describes how to configure the clock source according to the planned the clock
synchronization scheme, thus ensuring that all the NEs in a network trace the same clock.
3.7 Configuring Protection for Clock Sources
This section describes how to configure protection for clock sources. In the case of simple
networks such as chain networks, you need not configure protection for the clock sources. The
clock sources are protected according to the clock source priority table. In the case of complex
clock networks such as ring networks or tangent rings and intersecting rings deriving from ring
networks, protection for the clock sources need to be implemented through the standard SSM
protocol or extended SSM protocol.
3.8 Configuring Switching Conditions for Clock Sources

3 Configuring Clocks Operation Guide for RTN NE Management
If the traceable clock source of an NE is line clock, you can customize switching conditions for
the clock source, so that the NE switches to other clocks when the clock source fails. In this
manner, services are less affected.
3.9 Configuring the Clock Source Reversion
When there are multiple clock sources for an NE, set the clock sources to automatic reversion
mode, so that the deteriorated clock source automatically becomes the traceable timing reference
after it recovers.
3.10 Modifying the Parameters of the External Clock Output
The NE outputs the 2 Mbit/s external clock regardless of the clock quality.
3.11 Setting the Clock Source Quality
In a complex clock network, there may be some unknown clock sources. You can uniformly
define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.
The NE obtains their quality information automatically for clock sources that are allocated to
an NE. You should define the quality level of clock sources only during test and maintenance.
3.12 Configuring the SSM Output
If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages
automatically. You can prevent clock sources from sending SSM messages to other clock
subnets. This helps you to ensure that the equipment of different clock subnets do not affect each
other at the edge of clock networks.
3.13 Configuring the Ethernet Clock Source
Configure the Ethernet clock source of the IDU 605 1F/2F according to the planned clock
synchronization strategy to ensure that all the NEs in the network trace the same clock.
3.15 Checking the Clock Switching Status
Clock failure may interrupt services. To detect failure of the clock source in time, you need to
check the clock switching status.
3.16 Switching a Clock Source
When the traceable clock source in a network deteriorates, NEs may not be able to execute a
switch on the clock source. You need to manually switch the clock source to prevent clock
deterioration from affecting the normal running of NEs.

3.1 Clock Configuration Process

This section describes the process of clock configuration based on a flow chart.
The details of the clock configuration flow varies with the situation. See Figure 3-1, Figure
3-2, and Figure 3-3.
Figure 3-1 Configuration flow when SSM protocol is disabled

Required
Optional
Set switching Set the clock View the clock

Set the clock Switch a clock
conditions for source synchronization
source priority clock sources source
reversion status
Figure 3-2 Configuration flow when standard SSM protocol is enabled

Required
Optional
Set the clock Set switching Set the clock View the clock Set the phase-locked
Set the clock Set the clock Switch a clock
source conditions for source synchronization source for external
source priority clock sources
source quality source
protection reversion status clock output
Enable the standard

SSM protocol
Set the affiliated clock

subnet for the NE
Figure 3-3 Configuration flow when extended SSM protocol is enabled

Required
Optional
Set the clock Set switching Set the clock View the clock Set the phase-locked
Set the clock Set the clock Switch a clock
source conditions for source synchronization source for external
source priority clock sources
source quality source
protection reversion status clock output
Enable the extended

SSM protocol
Set the affiliated clock

subnet for the NE
Set the ID for clock
NOTE
l The horizontal direction of the figure shows the three stages when you use the U2000 to configure
clocks.
l The vertical direction of the figure shows the relations between operation tasks at each stage.

3.2 Clock Synchronization Scheme

This section describes the clock synchronization schemes. You need choose the clock
synchronization scheme according to the actual networking architecture.
Clock Synchronization Scheme for a Chain/Tree Network

The clock synchronization schemes for chain/tree networks are as follows:
l If the main (first) node accesses a clock source (external clock or line clock), configure this
clock source for this node.
l Configure the clock source of the higher-level radio link for other nodes.
l When the higher-level radio link adopts 1+1 protection, configure two clock sources for
the corresponding node. Note that the clock source priority of the main radio link should
be higher than the clock source priority of the standby radio link.
l When multiple higher-level radio links exist, (for example, when the radio link is
configured with XPIC or N+1 protection), the node configures a microwave clock source
for each radio link and allocates different clock priority levels based on the situation of
each radio link.
l Do not configure the synchronization status message (SSM) or extended SSM protection.
Figure 3-4 shows the clock synchronization scheme of a chain network.
l The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence,
the clock source priority levels are external clock source 1 and internal clock source in the
descending order.
l The IF1A boards in slots 5 and 7 on NE2 form an IF 1+1 protection group (the board in
slot 5 is the main board) and provide the radio link from NE1 to NE2. Hence, the clock
source level priority levels are 5-IF1A-1, 7-IF1A-1, and internal clock source in the
descending order.
l The IF1A board in slot 5 on NE2 provides the radio link from NE3 to NE2. Hence, the
clock source level priority levels are 5-IF1A-1 and internal clock source in the descending
order.
order.
l Do not configure the SSM or extended SSM protection.
Figure 3-4 Clock synchronization scheme for a chain network

NE1 NE2 NE3 NE4
5-IF1A-1/
External 1/ 5-IF1A-1/ 5-IF1A-1/
7-IF1A-1/
Internal Internal Internal
Internal
Master clock

Figure 3-5 shows the clock synchronization scheme of a tree network.
l The SL1 board in slot 4 on NE1 accesses the line clock source. Hence, the clock source
level priority levels are 4-SL1-1 and internal clock source in the descending order.
l The IFX boards in slots 5 and 7 on NE2 form an XPIC workgroup (the IFX board in slot
5 works on polarization V and the IFX board in slot 7 is works on polarization H) and
provide the radio link from NE1 to NE2. Hence, the clock source level priority levels are
5-IF1A-1, 7-IF1A-1, and internal clock source in the descending order.
order.
order.
Figure 3-5 Clock synchronization scheme for a tree network
NE3
NE1 NE2
5-IF1A-1/
Internal
NE4
5-IFX-1/
4-SL1-1/
7-IFX-1/
Internal
Internal
Master clock 5-IF1A-1/

Internal
Clock Synchronization Scheme for a Ring Network

The clock synchronization schemes for a ring network formed by the OptiX RTN equipment
only or formed by the OptiX RTN equipment and other OptiX equipment are as follows:
l When the entire ring network line is an SDH line, set the SSM or extended SSM according
to the clock synchronization schemes of an optical transmission network.

l When a PDH section exists on the line of the ring network, divide the ring network into
two chains and set the synchronization according to the clock synchronization schemes of
a chain network.
Figure 3-6 shows the clock synchronization scheme of a ring network of which the entire ring
network line is an SDH line.
l The SSM or extended SSM protection is enabled on all the nodes in the ring network.
descending order.
l The clock source priority levels of other nodes are the west clock source, east clock source,
and internal clock source in the descending order.
Figure 3-6 Clock synchronization scheme for a ring network (the entire ring network line is an
SDH line)
NE2 NE6
NE1
West/ West/
East/ East/
Internal Internal
External 1/
Internal
West/ West/
East/ East/
Internal Internal
NE3 NE4 NE5
West/
Master clock East/
Internal
Figure 3-7 shows the clock synchronization scheme of a ring network of which not the entire
ring network line is an SDH line.
l This ring network is formed by PDH microwave. Hence, divide the ring network at the
main node NE1 into two chains: from NE1 to NE2 and from NE3 to NE4.
l The SL1 board in slot 4 on NE1 accesses the line clock source. Hence, the clock source
level priority levels are 4-SL1-1 and internal clock source in the descending order.
l NE2 traces the clock of the main node. Hence, the clock source level priority levels are the
west clock source and internal clock source in the descending order.
l NE4 traces the clock of the main node. Hence, the clock source level priority levels are the
east clock source and internal clock source in the descending order.
l NE3 traces the clock of NE4. Hence, the clock source level priority levels are the east clock
source and internal clock source in the descending order.

Figure 3-7 Clock synchronization scheme for a ring network (not the entire ring network line
is an SDH line)
NE1
NE2 NE4
4-SL1-1/
Internal
NE3
West/ East/
Internal Internal
Master clock
East/
Internal
Clock Synchronization Scheme for Networking with Convergence at Tributary

Ports
Networking with convergence at tributary ports indicates that several OptiX RTN 600 NEs are
converged to the higher-level OptiX RTN NE through the E1/E3 cable. The clock
synchronization schemes for networking with convergence at tributary ports are as follows:
l The higher-level NE accesses the clock source (external clock source or line clock source).
l The lower-level NEs trace the tributary clock sources (port 1 and port 5 of the PO1/PH1/
PD1 board can be used as the tributary clock sources).
l When a lower-level NE is connected to multiple hops of radio links, abnormal pointer
adjustments may occur if the lower-level NE traces the tributary clock. Therefore, the
lower-level NEs should trace the external clock output by the higher-level NE.
Figure 3-8shows the clock synchronization scheme for networking with convergence at
tributary ports.
descending order.
order.

l NE3 converges services TO NE2 through ports 1-4 of the PO1 board in slot 4. Hence, the
clock source level priority levels are 4-PO1-1 and internal clock source in the descending
order.
l Multiple microwave hops exist in the downstream of NE4. In this case, the downstream
nodes will report point adjustments if NE4 adopts the tributary clock source. Hence, NE4
adopts the external clock output from NE2 as the external clock input to the PXC board in
slot 1.
Figure 3-8 Clock synchronization scheme for networking with convergence at tributary ports
NE3
NE1 NE2
4-PO1-1/
Internal
NE4
External 1/ 5-IF1A-1/
Internal Internal
External/
Internal
Master clock E1 External clock
Precautions for Making the Clock Synchronization Scheme

The precautions for making the clock synchronization scheme are as follows:
l The number of the NEs on the long clock chain must not exceed 20. It is recommended
that the long clock chain contains less than 10 NEs. If the long clock chain contains too
many NEs, new clock sources need be added to the chain for use compensation.
l Use SDH interface boards to converge services at the convergence node. Thus, the clock
signals can be passed over SDH signals not over PDH signals, which ensures the high
quality of the clock.
3.3 Basic Concepts

Before clock configuration, you need to master the basic concepts.
3.3.1 Clock Synchronization

By keeping the clock synchronization of each NE in the network, you can avoid pointer
justification events, jitters, and bit errors thus caused when the clocks are not synchronous. All
NEs trace the same PRC through a specific clock synchronization path, thus realizing the
networkwide synchronization.
3.3.2 SSM Protocol and Clock ID
The synchronization status message (SSM) protocol and clock ID are used for clock protection.
3.3.3 Clock Subnet
The nodes that have clock tracing relations between each other comprise a clock subnet.
3.3.4 Clock Protection
Clock protection ensures that each node traces the correct clock source even when a fault occurs
in a network.
3.3.1 Clock Synchronization

By keeping the clock synchronization of each NE in the network, you can avoid pointer
justification events, jitters, and bit errors thus caused when the clocks are not synchronous. All
NEs trace the same PRC through a specific clock synchronization path, thus realizing the
networkwide synchronization.
Working Modes and Timing Methods of the Clock

Currently, the communication network adopts the master-slave synchronization mode. That is,
the master clock that is with high precision and stability transfers clock signals to slave clocks
of each level through the clock network. Each slave clock is synchronous with the clock signal
that is from the upper level. Thus, the networkwide synchronization is realized. In this mode,
the slave clock usually has the following three working modes:
l Tracing mode: It is the normal working mode. In this mode, the local clock is synchronized
with the input reference clock signals.
l Holdover mode: When all timing reference signals are lost, the slave clock enters into the
holdover mode. In this mode, the slave clock takes timing reference from the last frequency
information saved before the loss of timing reference signals. This mode can be used to
cope with an interruption of external timing signals lasting many days.
l Free-run mode: When all timing reference signals are lost and the slave clock losses the
saved configuration data about the timing reference or the slave clock fails to enter the
holdover mode, the internal oscillator of the slave clock enters the free-run mode from the
holdover mode.
The clock source has the following four timing methods:

l External clock source: 2M timing signals from the external clock interface of an NE
l Line clock source: timing signals extracted from optical signals that the line board receives
l Tributary clock source: timing signals extracted from optical signals that the tributary board
receives
l Internal clock source: The internal timing source is available for each NE. When the
external source is lost, the NE can use the internal timing source.
Clock Synchronization
Generally, an NE can obtain the PRC through several paths. In Figure 3-9, NE4 can trace the
clock from NE3 and the clock from NE5. These two clock sources are from the same PRC.

Figure 3-9 Clock synchronization

BITS
NE1
NE2 NE6
NE3 NE5
NE4
Clock Signal Flow
3.3.2 SSM Protocol and Clock ID

The synchronization status message (SSM) protocol and clock ID are used for clock protection.
S1 Byte
The S1 byte is located in row 9 and column 1 in the multiplex section overhead in an SDH frame
structure. The lower four bits (bit 5-bit 8) of the S1 byte are allocated to transport a
synchronization status of an NE, which is referred to as the synchronization status message byte
(SSMB). Table 3-1 shows the meaning of clock quality that the SSMB stands for. The smaller
the SSMB value, the higher the quality of the clock source that the SSMB represents.
In a clock network, the node that is connected to an external clock extracts a reference timing
source from the BITS equipment, writes an SSMB to bit 5-bit 8 of S1 byte, and transports the
SSMB to downstream nodes. In this way, the SSMB is output. A downstream node extracts the
timing source from a line signal, and obtains the clock quality level from bit 5-bit 8 of S1 byte.
In this way, the downstream node often determines whether the current clock source is effective
and transmits back 0xf to the upstream node through bit 5-bit 8 of S1 byte. 0xf means the returned

clock source is unavailable. This prevents two nodes from tracing the timing source mutually.
Each node obtains the quality of all clock sources from the S1 byte, and choose to trace a clock
source according to the preset priority level.
Table 3-1 SSM allocation
Bit 5-bit 8 of S1 byte SDH Synchronization Quality Level
0000 The synchronization quality is unknown (the

existing synchronous network).
0001 Retained
0010 G.811 clock signal
0011 Retained
0100 SSU-ANote 1
0101 Retained
0110 Retained
0111 Retained
1000 SSU-BNote 1
1001 Retained
1010 Retained
1011 Synchronous equipment timing source

(SETS) signal
1100 Retained
1101 Retained
1110 Retained
1111 Not used for synchronization
Note 1: The "G.812 Transit Exchange" and "G.812 Local Clock" terms are used in the previous
version of ITU-T Recommendations. In the new version of ITU-T G.812, the clock definition
is changed to synchronization supply unit (SSU). The SSU has A and B types. The SSU-A
corresponds to the "G.812 Transit Exchange" and the SSU-B corresponds to the "G.812 Local
Clock" that are previously used.
SSM Protocol
The standard SSM protocol is mechanism of network synchronization management. It uses bit
5-bit 8 of S1 byte to exchange the quality information of clock sources between nodes. This
ensures that the equipment automatically selects the clock source of the highest quality and
priority levels, to prevent an interlock of clocks. The standard SSM protocol improves the
performance of a synchronous network, and realizes synchronization of different network

structures in an easy manner. The standard SSM protocol applies to the interconnection of
equipment from different vendors.
In the case that the S1 byte is enabled for clock protection, the concept of clock ID is introduced.
That is, clock protection is extended based on the original SSM protocol. In this manner, the
extended SSM protocol is developed.
In the case of the extended SSM protocol, Huawei introduces the concept of clock ID based on
the standard SSM protocol. The extended SSM protocol uses b1 through b4 of S1 byte as the
unique ID of a clock source and transports the clock ID with an SSM. After a node receives the
S1 byte, the node verifies the clock ID (bit 1-bit 4) to determine whether the clock is locally
output. If the clock is locally output, the node regards the clock as unavailable. This prevents a
timing loop. The extended SSM protocol is mainly used to realize the interconnection of
transmission equipment from Huawei.
When an NE works in different clock protection modes, the method of selecting a clock source
during automatic clock switching is changed accordingly, as shown in Table 3-2.
Table 3-2 Methods of selecting clock sources in different modes
Working Mode Clock Source Selection
Non-SSM protocol mode The NE selects a clock source with the highest
priority according to the clock source priority
list. If the clock source with the highest
priority is lost, the NE selects and trace the
clock source with the second highest priority.
Standard SSM protocol mode The NE selects a clock source according to

the priority and quality of the clock source.
The clock source with highest quality is
preferred. If the clock sources are of the same
quality, the NE selects the clock with the
highest priority.
Extended SSM protocol mode The NE selects a clock source according to

the priority, quality, and clock source ID.
Specifically, the NE selects and traces the
clock source that is with the highest quality
and priority but not transmitted from the NE
itself.
Clock ID
A clock ID use bit 1-bit 4 of S1 byte, and the value range is 0x0 to 0xf. Basically, a clock ID is
used to distinguish the clock information between local and other nodes, to prevent a node from
tracing the clock signal that is locally transmitted and comes from the negative direction. Hence,
a timing loop is prevented.
A value of 0 indicates that a clock ID is invalid. Hence, the default value of a clock ID is 0 when
an ID is not set for a clock source. When enabling the extended SSM protocol, an NE does not
select the clock source whose ID is 0 as the current clock source.

A clock ID is a tag set for a reference timing source. The clock sources at the same quality level
that carry different IDs mean different timing signals and are not different in priority levels and
other aspects.
Set the clock ID according to the following principles:

l Allocate a clock ID to each external BITS.
l Allocate a clock ID to the internal clock source of each node that has an external BITS.
l Allocate a clock ID to the internal clock source of each node that enters into another ring
network from one chain or ring network.
l Allocate a clock ID to the line clock source of the node that enters into another ring network
from one chain or ring network, when the line clock source exists.
3.3.3 Clock Subnet

The nodes that have clock tracing relations between each other comprise a clock subnet.
During the configuration of a clock subnet, pay attention to the following points:
l All the NEs that trace the same clock source should be divided to the same clock subnet.
l To make sure that the clock tracing chain is not too long, configure at most 20 NEs to
prevent the clock precision from being degraded.
l You must divide the NEs that have the SSM clock protection to clock subnets. Otherwise,
SSM is not enabled for the NEs that are not divided to the clock subnets. This results in
incorrect traced clock switching.
3.3.4 Clock Protection

Clock protection ensures that each node traces the correct clock source even when a fault occurs
in a network.
Clock protection refers to the process during which a timing source selects a new route so that
the entire network continues to trace the PRC, when services are switched and select a standby
route to realize protection because an optical path is interrupted or a node fails. In other words,
clock protection is a process during which, when one PRC fails in the network, a new route is
selected to trace another PRC networkwide.
In Figure 3-9, NE4 traces the clock that is from NE3. If this clock is lost, NE4 can automatically
switches to trace the clock that is from NE5. When automatic protection switching occurs in a
clock, the new clock source may trace the same PRC as the original clock source or another PRC
with worse quality, such as another standby BITS.
The clock protection switching is performed based on the following principles:

l If the clock source priority is set, the NE selects the clock source of the highest quality level
as the synchronization source and sends the synchronization status message bit (SSMB) to
downstream NEs.
l If multiple clock sources of the same quality level exist, the NE selects the clock source of
the highest priority level as the synchronization source and sends the SSMB to downstream
NEs.
l If NE B traces the clock source that is output from NE A, the clock of NE B is an unavailable
source for NE A.
l If the extended SSM protocol is enabled, the NE does not select the clock that has the same
ID as the local clock, or the clock whose ID is 0, as the clock source.

3.4 Viewing Clock Synchronization Status

If the clocks between NEs in the network are not synchronous, the pointer justification, bit error,
even service interruption may occur on NE. Using the U2000, you can learn and monitor the
synchronization status of the NE clocks.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Synchronization
Status from the Function Tree.
NOTE
To view the clock synchronization status of NEs in batches, Choose Configuration > NE Batch
Configuration > Batch Clock Operation from the main menu. Then, click the Clock Synchronization
Status tab. In the Object Tree, select the desired NEs and click .
Step 2 Click Query. You can view the information about the clock synchronization status queried from
the NE side.
----End

Prerequisite
Context
When the clock tracing relationships are changed, the U2000 refreshes the tracing status in the
Clock View automatically.
Procedure
Step 1 In the Main Topology window, selectClock View from the Current View drop-down list.
Step 2 Select the NE to be queried or configured from the object tree. In the Clock View, right-click
and choose Search Clock Link from the shortcut menu.
Step 3 In the Operation Result dialog box, click Close.
----End

3.6 Configuring the Clock Sources

Prerequisite
The PXC boards and input/output clock source boards must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Source Priority from the Function Tree.
Step 2 Click Create.
The Add Clock Source dialog box is displayed.
Step 3 Select the clock sources.
TIP
By pressing the Ctrl key, you can select multiple clock sources at one time.
Step 4 Click OK.
Step 5 Optional: Repeat Step 2 to Step 4 to add other clock sources.
Step 6 Optional: Select a clock source and click or to adjust the priority level of
this clock source.
The clock priority levels are arranged in the descending order from the first row to the last row.
The internal clock source is fixed with the lowest priority.
Step 7 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external
clock sources.

Step 8 Click Apply.
----End
Parameters
Parameter Value Range Default Value Description
Clock Source - - l External clock source 1 indicates the

external clock source at the port of the
PXC board in slot 1. External clock
source 2 indicates the external clock
source at the port of the PXC board in
slot 3.
l IFH2-1(SDH) indicates the microwave
clock source.
l IFH2-2(ETH) indicates the clock source
of the synchronous Ethernet.
l The internal clock source is fixed with
the lowest priority and indicates that the
NE works in the free-run mode.
l Determine the clock sources and the
corresponding clock source priority
levels according to the clock
synchronization schemes.
External Clock 2 Mbit/s, 2 MHz 2 Mbit/s l This parameter indicates the type of the
Source Mode external clock source signal.
l Set this parameter depending on the
external clock signal. Generally, the
external clock signal is a 2 Mbit/s signal.
Synchronization SA4-SA8 SA4 l This parameter is valid only when

Status Byte External Clock Source Mode is set to
2 Mbit/s.
l This parameter indicates which bit of the
TS0 in odd frames of the external clock
signal is used to transmit the SSM.
l This parameter need to be set only when
the SSM or extended SSM is enabled.
Generally, the external clock sources use
the SA4 to pass the SSM.

3.7 Configuring Protection for Clock Sources

This section describes how to configure protection for clock sources. In the case of simple
networks such as chain networks, you need not configure protection for the clock sources. The
clock sources are protected according to the clock source priority table. In the case of complex
clock networks such as ring networks or tangent rings and intersecting rings deriving from ring
networks, protection for the clock sources need to be implemented through the standard SSM
protocol or extended SSM protocol.
Prerequisite
The clock source priority table must be configured.
Procedure
Subnet Configuration from the Function Tree.
Step 2 Enable the clock protection protocol.

1. Click the Clock Subnet tab.
2. Enable the clock protection protocol and set the protocol parameters.
3. Click Apply.
Step 3 Set the SSM output port.

1. Click the SSM Output Control tab.
2. Set the SSM output port.

3. Click Apply.
Step 4 Optional: Set the clock ID output port.
1. Click the Clock ID Status tab.
2. Set the clock ID output port.
3. Click Apply.
----End
Parameters
Protection Status Start Extended SSM Stop SSM Protocol l The SSM protocol is a scheme used for
Protocol, Start synchronous management in an SDH
Standard SSM network and indicates that the SSM is
Protocol, Stop SSM passed by the lower four bits of the S1
Protocol byte and can be exchanged between the
nodes. The SSM protocol ensures that
the equipment automatically select the
clock source with the highest quality and
highest priority, thus preventing clock
mutual tracing.
l The extended SSM protocol is the
extension of the standard SSM protocol.
It defines the unique ID for each clock
source and uses the higher four bits of the
S1 byte to pass the ID. The extended
SSM protocol can be used to prevent the
NEs from tracing their own clocks.
l If third-party equipment exists in the ring
network, enable the SSM protocol. If
only OptiX equipment exists in the ring
network and clock mutual tracing can be
prevented through certain
configurations of the clock sources, the
SSM protocol can also be enabled.
l If only OptiX equipment exists in the
ring network, it is recommended that the
extended SSM protocol is used.

Affiliated Subnet 0-255 0 l This parameter is used when the clock

subnet need to be created on the NMS.
l The NEs that trace the same clock source
should be allocated with the same clock
subnet ID.
Clock Source ID (None), 0-15 (None) l This parameter is valid only when the
SSM protocol is enabled.
l Allocate the clock source ID for the
following clock sources only:
External clock sources
Internal clock source of the node that
accesses the external clock sources
Internal clock source of the joint node
of a ring and a chain or the joint node
of two rings
Line clock source that enters the ring
when the intra-ring line clock source
is configured at the joint node of a
ring and a chain or the joint node of
two rings
Control Status Enabled, Disabled Enabled l This parameter is valid only when the
SSM protocol or the extended SSM
protocol is enabled.
l This parameter indicates whether the
SSM is output at the line port.
l When the line port is connected to an NE
in the same clock subnet, set this
parameter to Enabled; otherwise, set
this parameter to Disabled.
Enable Status Enabled, Disabled. Enabled l This parameter is valid only when the
SSM protocol is enabled.
clock source ID is output at the line port.
l When the line port is connected to an NE
in the same clock subnet and the
extended SSM protocol is enabled at the
remote NE, set this parameter to
Enabled; otherwise, set this parameter
to Disabled.

3.8 Configuring Switching Conditions for Clock Sources

If the traceable clock source of an NE is line clock, you can customize switching conditions for
the clock source, so that the NE switches to other clocks when the clock source fails. In this
manner, services are less affected.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source
Switching from the Function Tree. Click the Clock Source Switching Condition tab.
Step 2 Click Query to query the existing parameter settings.
Step 3 Double-click the parameter column and set the alarms and performance events that are to be
used as the clock source switching conditions to Yes.
Step 4 Click Apply. In the Operation Result dialog box, click Close.
----End
3.9 Configuring the Clock Source Reversion

When there are multiple clock sources for an NE, set the clock sources to automatic reversion
mode, so that the deteriorated clock source automatically becomes the traceable timing reference
after it recovers.
Prerequisite
Procedure
Switching from the Function Tree. Click the Clock Source Reversion Parameter tab.
NOTE
To set the clock source reversion for multiple NEs in batches, Choose Configuration > NE Batch
Configuration > Batch Clock Operation from the main menu. . Click the Clock Source Reversion
Parameter tab. In the Object Tree, select the desired NEs and click .
Step 2 Double-click and set the reversion mode and the WTR time.

NOTE
Do not set Clock Source WTR Time(min) to 0 to avoid repeated switching when the clock is unstable.
----End
3.10 Modifying the Parameters of the External Clock Output

The NE outputs the 2 Mbit/s external clock regardless of the clock quality.
Prerequisite
The PXC board must be configured.
Precautions
In the OptiX RTN 600, external clock source 1 indicates the external clock on the PXC board
in slot 1 and external clock source 2 indicates the external clock on the PXC board in slot 3.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Phase-Locked Source Output by External Clock from the Function Tree.
Step 2 Modify the clock output parameters.
Step 3 Click Apply.
----End
Parameters
External Clock 2 Mbit/s, 2 MHz 2 Mbit/s l This parameter indicates the mode of the
Output Mode output clock.
l Set this parameter according to the
requirements of the interconnected
equipment. Generally, the output clock
signal is a 2 Mbit/s signal.

External Clock SA4-SA8, ALL ALL l This parameter is valid only when
Output Timeslot External Clock Output Mode is set to
2 Mbit/s.
l When this parameter is set to ALL, it
indicates that each bit can transmit the
SSM.
l It is recommended that this parameter
takes the default value.
External Clock Threshold Disabled, Threshold Disabled l This parameter indicates the lowest
Output Threshold Not Inferior to G. clock quality of the output clock. When
813 SETS Signal, the clock quality is lower than the
Not Inferior to G. parameter value, the signal is not output.
812 Local Clock l When this parameter is set to Threshold
Signal, Not Inferior Disabled, it indicates that the clock
to G.812 Transit signal is continuously output.
Clock Signal, Not
Inferior to G.811 l It is recommended that this parameter
Clock Signal takes the default value.
2M Phase-Locked No Failure No Failure l This parameter indicates the conditions

Source Fail Condition, AIS, Condition when the 2M phase-locked clock source
Condition LOF, AIS OR LOF fails.
l It is recommended that you use the
default value.
2M Phase-Locked Shut Down Output, Shut Down Output l This parameter is valid only when 2M
Source Fail Action 2M Output S1 Byte Phase-Locked Source Fail Condition
Unavailable, Send is No Failure Condition.
AIS l This parameter indicates the action of the
2M phase-locked loop when 2M Phase-
Locked Source Fail Condition is met.
default value.
3.11 Setting the Clock Source Quality

In a complex clock network, there may be some unknown clock sources. You can uniformly
define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.
The NE obtains their quality information automatically for clock sources that are allocated to
an NE. You should define the quality level of clock sources only during test and maintenance.
Prerequisite

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Subnet
Configuration from the Function Tree. Click the Clock Quality tab.
Step 2 Click Query to query the existing parameter settings.
Step 3 Click the Clock Source Quality tab and set Configuration Quality to a desired level.
NOTE
Generally, use the default Automatic Extraction.
Step 5 If the quality level of a clock source is zero, you can specify the level manually. Click the Manual
Setting of 0 Quality Level tab and set Manual Setting of 0 Quality Level to a desired level.
NOTE
To set the clock source quality for multiple NEs in batches, Choose Configuration > NE Batch
Configuration > Batch Clock Operation from the main menu. Click the Manual Setting of 0 Quality
Level tab. In the Object Tree, select the desired NEs and click .
----End
3.12 Configuring the SSM Output

If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages
automatically. You can prevent clock sources from sending SSM messages to other clock
subnets. This helps you to ensure that the equipment of different clock subnets do not affect each
other at the edge of clock networks.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Subnet
Configuration from the Function Tree. Click the SSM Output Control tab.
Step 2 Set the Control Status of the clock source.

----End
3.13 Configuring the Ethernet Clock Source

Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock Source
Priority from the Function Tree.
Step 2 Set Use the clock source of the data port.
Step 3 Click Apply.
----End
Parameters
Use the clock source Yes, No No When this parameter is set to Yes, the IDU
of the data port 605 1F/2F traces the clock source that is
recovered from the signal flow on the
Ethernet PORT.

Prerequisite

Context
When the clock tracing relationships are changed, the U2000 refreshes the tracing status in the
Clock View automatically.
Procedure
Step 1 In the Main Topology window, selectClock View from the Current View drop-down list.
Step 2 Select the NE to be queried or configured from the object tree. In the Clock View, right-click
and choose Search Clock Link from the shortcut menu.
----End
3.15 Checking the Clock Switching Status

Prerequisite
l You must be an NM user with "NE monitor" authority or higher.
l The reference clock source must be set.
Procedure
Switching from the Function Tree.
Step 2 Click the Clock Source Switching tab, and click Query to query the current switching status
of the current clock source.
----End
3.16 Switching a Clock Source

When the traceable clock source in a network deteriorates, NEs may not be able to execute a
switch on the clock source. You need to manually switch the clock source to prevent clock
deterioration from affecting the normal running of NEs.

Prerequisite
l The clock source has been created.
Context
CAUTION
Performing clock source switching may cause signal jitter and bit errors.
Procedure
Switching from the Function Tree. Click the Clock Source Switching tab.
Step 2 Click Query to query the current switching status of a clock source.
Step 3 Optional: If the Lock Status is Lock, right-click and choose Release Lockout.
Step 4 Right-click the clock source that you want to switch and choose a switching operation.
NOTE
Before switching the clock source, make sure that the new clock source that is not locked and that is of a
good quality is created in the priority table.
Step 5 Optional: To restore the automatic clock source selection mode, right-click the switched clock
source and choose Clear Switching.
----End

Operation Guide for RTN NE Management 4 Configuring PTP Clock
4 Configuring PTP Clock
About This Chapter
The equipment complies with the IEEE 1588V2 protocol and can achieve frequency
synchronization and time synchronization.
4.1 Introduction to the PTP Clock
The precision time protocol (PTP) clock complies with the IEEE 1588V2 protocol and achieves
nanosecond-level precision, which meets the requirements of 3G and Long Term Evolution
(LTE).
4.2 Basic Information
Before configuring the IEEE 1588V2 clock, you should be familiar with the BMC algorithm,
clock architecture, master-slave synchronization, and IEEE 1588V2 protocol packets and their
functions.
4.3 Application of the PTP Clock
By using the IEEE 1588V2 protocol, the OptiX RTN equipment can transfer the precise time
information to achieve clock synchronization and time synchronization for equipment in the
network. This meets the requirement of the telecommunications network for precise time. The
equipment with the PTP clock can achieve networkwide frequency synchronization and time
synchronization in the packet switching network (PSN). The telecommunications network carry
various services. Certain services require precise time synchronization, such as the network
voting and charging services. In such a scenario, the IEEE 1588V2 clock is applicable and
ensures precise time synchronization.
4.4 Configuration Flow for the PTP Clock
This section describes the flow of configuring the PTP clock in different modes.
4.5 Configuring the PTP Clock
To achieve time synchronization and clock synchronization between NEs, configure the PTP
clock.

4 Configuring PTP Clock Operation Guide for RTN NE Management
4.1 Introduction to the PTP Clock

The precision time protocol (PTP) clock complies with the IEEE 1588V2 protocol and achieves
nanosecond-level precision, which meets the requirements of 3G and Long Term Evolution
(LTE).
Objective and Benefit

As the rate at which the Ethernet data is transmitted is increased to the gigabit-per-second level,
the synchronization of the Ethernet fails to meet the requirements. To solve the synchronization
problem, the network time protocol (NTP) is presented, which helps achieve the precision of
clock synchronization at 200 us. The precision, however, fails to meet the precision requirements
of the test instruments and industrial control. To improve the synchronization precision, in 2002,
the IEEE committee presented the IEEE 1588 clock protocol. Then, the protocol evolved to the
current IEEE 1588V2 protocol, which helps achieve nanosecond-level precision.
There are two synchronization modes, that is, clock (frequency) synchronization and time
(phase) synchronization. Time (phase) synchronization is applicable to the networks where the
absolute networkwide time should be of certain precision, such as the power system network
and 3G network. Though the GPS at every node can also solve the precision problem, the high
cost limits the application scope of this solution.
The traditional clock protocols can achieve only frequency synchronization. The IEEE 1588V2
protocol is the clock protocol that can achieve both frequency synchronization and phase
synchronization.
The IEEE 1588V2 protocol is applicable for time synchronization at every node in the distributed
network that requires precise synchronization. The hardware and software synchronize the
system clock of the network equipment (client) with the primary clock in the network at a
nanosecond precision level. In the Ethernet where the IEEE 1588V2 protocol is not enabled,
there is a 1000 us delay. In the Ethernet where the IEEE 1588V2 protocol is enabled, the timing
synchronization is improved to a great extent.
The approach of adopting the IEEE 1588V2 protocol to achieve clock synchronization and time
synchronization marks a technical innovation for the transformation of the carrier-class IP
network.
The IEEE 1588V2 protocol helps achieve clock synchronization and time synchronization that
meet the requirements of Node B and RNC in a 3G network.
NOTE
l Clock synchronization refers to frequency synchronization.

l Time synchronization refers to phase synchronization, which requires that both the time and frequency
should be synchronous.
Standards and Protocols Compliance

The IEEE 1588V2 clock complies with 1588 IEEE Standard for a Precision Clock
Synchronization Protocol for Networked Measurement and Control Systems, IEEE, 2002.

4.2 Basic Information

Before configuring the IEEE 1588V2 clock, you should be familiar with the BMC algorithm,
clock architecture, master-slave synchronization, and IEEE 1588V2 protocol packets and their
functions.
BMC Algorithm
In a PTP clock network, the equipment computes the best clock source according to the BMC
algorithm.
The BMC algorithm compares the descriptive data of two clocks and detects the better one,
which is selected as the clock source. The BMC algorithm includes the following algorithms:
l Data set comparison algorithm: The NE selects the clock of better quality as the clock
source. If an NE receives two or more channels of clock signals from the same grandmaster
clock (GMC), the NE selects one channel of the clock signals that traverses the least nodes
as the clock source.
l State decision algorithm: The result of data set comparison determines the next state of the
port.
Clock Architecture
Figure 4-1 shows the architecture of the IEEE 1588V2 clock.

Figure 4-1 Architecture of the IEEE 1588V2 clock
BITS
OC GMC
Master
TC
Slave
BC BC
Master Master Slave Master
Slave
TC+OC OC
OC Slave
NOTE
l Master: A master port provides a time source for the downstream equipment.
l Slave: A slave port receives the clock signals from the upstream port.
The OptiX RTN equipment supports four architectures of the IEEE 1588V2 clock.
l Ordinary clock (OC): The OC equipment provides only one port to extract the IEEE 1588
packets. The OC equipment can work as a slave clock equipment and maintains
synchronization with the upstream clock. The equipment extracts the clock packets from
the port that supports the IEEE 1588 packets and recovers the clock. The equipment can
also work as a master clock equipment, which inputs the external time from the external
time interface, and outputs the clock signals to the downstream through the port that
supports the IEEE 1588 packets.
l Boundary clock (BC): When used as a BC, the equipment provides multiple ports to extract
the IEEE 1588 packets. The BC can work as either master clock equipment or slave clock
equipment. The BC equipment can distribute the clock packets to the downstream through
multiple ports, but the OC equipment can distribute the clock packets to the downstream
through only one port.
l Transparent clock (TC): The TC equipment transparently transmits the IEEE 1588 packets
and records the period when the packets stay on the equipment. During the period, the TC

equipment transports the packets to the slave clock equipment for processing. The TC
equipment only transparently transmits the clock, and does not recover the clock.
End-to-end TC: The TC equipment adopts the end-to-end delay measurement
mechanism between the master and slave clocks.
Peer-to-peer TC: The TC adopts the point-to-point delay measurement mechanism.
l TC+OC: The TC+OC equipment corrects and transparently transmits the time stamps for
the IEEE 1588V2 packets, and achieves clock synchronization. By adopting the BMC
algorithm, the TC+OC equipment selects the clock source, which is then sent to the system
clock module. If necessary, the clock source can be used as the system clock of the
equipment.
NOTE
The end-to-end TC and peer-to-peer TC adopt different mechanisms to realize delay transmission, and
cannot operate in the same communication channel alternatively. That is, the adjacent TC equipment along
one time channel adopts either the end-to-end TC or peer-to-peer TC, but not both at the same time.
Master-Slave Synchronization
In the case of master-slave synchronization, each slave clock maintains synchronization with
the master clock by exchanging the synchronization packets with the master clock.
Figure 4-2 shows the master-slave synchronization process of the equipment.
Figure 4-2 Master-slave synchronization process

Time stamp at
Master clock Slave clock slave clock
Sync packets
t1
t2 t1t2
Delay_Req
packets
t3 t1t2t3
t4
Delay_Resp t1t2t3t4
packets
l At time point t1, the master clock sends the Sync packets that contain time stamp t1 to the
slave clock.
l At time point t2, the slave clock receives the Sync packets and obtains time stamp t1.
l At time point t3, the slave clock sends the Delay_Req packets to the master clock.

l At time point t4, the master clock receives the Delay_Req packets. Then, the master clock
sends the Delay_Resp packets that contain time stamp t4 to the slave clock.
NOTE
A time stamp (TS) is used to transmit the time information. The Sync packets, Delay_Req packets, and
Delay_Resp packets are used to generate or communicate the time information. The OC equipment and
BC equipment maintain synchronization by processing related time information.
The slave clock computes the delay and offset from the master clock according to time stamps
t1, t2, t3, and t4. Then, the slave clock corrects the time according to the delay and offset.
l Delay = [(t4-t1)-(t3-t2)]/2
l Offset = [(t2-t1)+(t3-t4)]/2
Protocol Packets and Their Functions

The IEEE 1588 protocol defines the Event messages and General messages. The Event messages
are timing messages. To transmit and receive the Event messages, the equipment should generate
the precise time stamp. To transmit and receive the General messages, the equipment does not
need to generate the precise time stamp.
The Event messages include the following packets:
l Sync
l Delay_Req
l Pdelay_Req
l Pdelay_Resp
The General messages include the following packets:
l Announce
l Delay_Resp
l Management
l Signaling
The Sync, Delay_Req, and Delay_Resp packets are used to generate or transport the timing
information. The OC and BC maintains synchronization by using the timing information and
adopting the delay request-response mechanism.
The Pdelay_Req and Pdelay_Resp packets are used to measure the link delay between two clock
ports that support the Pdelay mechanism. The link delay is used to correct the timing information
contained in the Sync packets in the P2P TC system. The OC and BC maintain synchronization
according to the link delay and the timing information contained in the Sync messages.
NOTE
The Pdelay mechanism is intended to measure the point-to-point transmission time between two
communication ports that support the Pdelay mechanism. The point-to-point transmission time is the link
delay. The P2P TC has to compute the link delay by adopting the Pdelay mechanism.
The Announce messages are used to set up the synchronization system.
4.3 Application of the PTP Clock

By using the IEEE 1588V2 protocol, the OptiX RTN equipment can transfer the precise time
information to achieve clock synchronization and time synchronization for equipment in the

network. This meets the requirement of the telecommunications network for precise time. The
equipment with the PTP clock can achieve networkwide frequency synchronization and time
synchronization in the packet switching network (PSN). The telecommunications network carry
various services. Certain services require precise time synchronization, such as the network
voting and charging services. In such a scenario, the IEEE 1588V2 clock is applicable and
ensures precise time synchronization.
Figure 4-3 shows the scenario where the PTP clock is applicable.
Figure 4-3 Networking diagram for typical application of the PTP clock
Node B
NE E
GPS
RTN 910
NE B OC
NE A
BC
NE C
RNC BC
NE D BC RTN 910
BC NE F
OC
RTN 910
External time signals Node B
RTN 950 PTP time signals
As shown in Figure 4-3, BITS sends clock signals to NE A and RNC. NE A works as BC
equipment and sends the PTP packets to two ports. NE E and NE F, which are connected to
Node B, work as the OC equipment, recover the PTP clock, and send the clock to Node B through
the external time interface.
4.4 Configuration Flow for the PTP Clock

This section describes the flow of configuring the PTP clock in different modes.
Figure 4-4 shows the flow for configuring the PTP clock.

Figure 4-4 Configuration flow for the PTP clock

Required
Start
Optional
Setting the Frequency
Selection Mode
Setting the PTP System

Time
Setting the PTP Clock

Subnet
Setting the Attributes of the

External Time Interface
Setting the PTP NE

Attributes
Creating the PTP Clock

Port
Creating the PTP Clock

Service
Setting the PTP Packet

Period
Setting the PTP Clock Port

Status
Setting the Cable

Transmitting Wrap
Setting the WTR Time for

the PTP Clock Sourc
Setting the PTP Clock

Source Priority
End

The PTP priority service needs to be configured only when the PTP clock works in the TC or
TC+OC mode.
The PTP clock source priority needs to be configured only when the PTP clock works in the TC
+OC mode.
4.5 Configuring the PTP Clock

To achieve time synchronization and clock synchronization between NEs, configure the PTP
clock.
4.5.1 Setting the Frequency Selection Mode

The OptiX RTN equipment supports two synchronization modes, that is, physical
synchronization mode and PTP synchronization mode. The frequency source selection mode is
used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock,
you should set the frequency source selection mode to the PTP synchronization mode.
4.5.2 Setting the PTP System Time
If the OptiX RTN equipment is used as the grandmaster clock in the PTP clock network, you
should set the PTP system time on the OptiX RTN equipment. Hence, the downstream OptiX
RTN equipment can trace the clock.
4.5.3 Setting the PTP Clock Subnet
According to the actual networking, the networking planner plans the clock network and divides
the entire network into clock domains. In each clock domain, the clock and time of the equipment
are synchronized. Each BC, OC or TC+OC equipment can be configured with only one clock
domain. The equipment selects the source in only one clock domain, and discards the clock
packets from other clock domains.
4.5.4 Setting the Attributes of the External Time Interface
If the equipment uses the external time interface to input or output time signals, you should set
the corresponding interface attributes. The external time interface attributes include the basic
attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to
compensate the time for the equipment.
4.5.5 Setting the PTP NE Attributes
The NE attributes include Work Mode, Transmitting Message Multi-cast Mode, and Time
Adjusting.
4.5.6 Creating the PTP Clock Port
When a PTP clock port is created, the PTP clock port can access the PTP packets. You can set
the clock reference source number on the PTP clock port created in the BC or OC mode.
4.5.7 Creating the PTP Clock Service
When the NE works in the TC or TC+OC mode, you need to create a PTP clock service on the
NE so that the NE transparently transmits the PTP clock packets.
4.5.8 Setting the PTP Packet Period
When setting the PTP packet period, you can set the periods of the ANNOUNCE, SYNC,
DELAY, and PDELAY packets.
4.5.9 Setting the PTP Clock Port Status
In the scenario where the OptiX RTN equipment is connected to the client equipment, properly
set the status of the PTP clock port. For example, if the PTP packets should contain VLAN ID

or the PTP packets from the client side should be forwarded (Layer 2 or Layer 3), set the status
of the PTP clock port accordingly. By default, the equipment performs Layer 2 forwarding for
the PTP packets.
4.5.10 Setting the Cable Transmitting Wrap
The cable transmitting distance wrap indicates the transmitting time difference of the cables
between two sets of equipment in the transmit and receive directions. During deployment, you
can use the GPS to compute the transmitting time difference between the two directions. Set the
cable transmitting wrap, and thus the equipment performs the clock compensation. The wrap
modes includes the length wrap and time wrap. The equipment can choose only one mode.
4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source
When a clock port recovers from a failure, the system acknowledges the validity of the port a
certain period later. This period is referred to as the wait-to-restore (WTR) time. During the
WTR time, the system considers the clock signals as unavailable and the clock signals are not
involved in the clock source selection.
4.5.12 Setting the PTP Clock Source Priority
If the NE works in the TC+OC mode, you need to set the priorities for the clock sources traced
by the OC. Normally, the OC traces the PTP clock source of the highest priority. If the PTP
clock source of the highest priority fails, the OC traces the PTP clock source of the second highest
priority. The priority table is configured with a source ID. When a local port receives a clock
source in the priority table, the port checks whether the domain that the clock source belongs to
is consistent with the domain configured at the local end.
4.5.1 Setting the Frequency Selection Mode

The OptiX RTN equipment supports two synchronization modes, that is, physical
synchronization mode and PTP synchronization mode. The frequency source selection mode is
used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock,
you should set the frequency source selection mode to the PTP synchronization mode.
Prerequisite
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > Frequency Selection Mode from the
Function Tree.
Step 2 In Frequency Selection Mode, you can select one of the clock synchronization mode.
CAUTION
l When the external time interface is set to the external time input interface, the NE can run
in only the physical synchronization mode. That is, the frequency selection mode of the
equipment that accesses the external clock must be set to the physical synchronization mode.
l When the NE is running in the PTP synchronization mode, the external interface cannot be
set to the external time input interface.

Step 3 Click Apply.
----End
4.5.2 Setting the PTP System Time

If the OptiX RTN equipment is used as the grandmaster clock in the PTP clock network, you
should set the PTP system time on the OptiX RTN equipment. Hence, the downstream OptiX
RTN equipment can trace the clock.
Prerequisite
The PTP system time can be set only when the current time of the NE traces the local clock.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization
Attribute.
Step 2 In PTP System Time, click to set the system time.
NOTE
Move the cursor to the time bar. To increase the value, click or right-click the time bar. To decrease the
value, hold the Shift key, and click or right-click the time bar.
Step 3 Click Apply.
----End
4.5.3 Setting the PTP Clock Subnet

According to the actual networking, the networking planner plans the clock network and divides
the entire network into clock domains. In each clock domain, the clock and time of the equipment
are synchronized. Each BC, OC or TC+OC equipment can be configured with only one clock
domain. The equipment selects the source in only one clock domain, and discards the clock
packets from other clock domains.

Prerequisite
The working mode of the equipment clock should not be TC.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Subnet
Configuration from the Function Tree.
Step 2 Select the Clock Subnet tab to set the clock subnet number.
Step 3 Click Apply.
Step 4 Click the BMC tab to set the parameters related to the BMC in the clock subnet.
Step 5 Click Apply.
----End
4.5.4 Setting the Attributes of the External Time Interface

If the equipment uses the external time interface to input or output time signals, you should set
the corresponding interface attributes. The external time interface attributes include the basic
attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to
compensate the time for the equipment.
Prerequisite
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > External Time Interface.
Step 2 Click the Basic Attribute tab.
Step 3 Set Interface Mode of the external time interface.
Step 4 Optional: If Interface Mode is set to External Time Interface, you can set Direction,
Interface Protocol Type, and Interface Eletricity.
NOTE
l OptiX RTN 910 and 950: Interface Protocol Type is set according to the type of the external time
protocol. Interface Protocol Type can be set to DCLS or 1PPS+TIME.
l OptiX RTN 910 and 950: Interface Level is set according to the setting of the external time interface.
Interface Level can be set to RS422.
Step 5 Click the BMC tab to set the BMC-related parameters.

NOTE
The BMC-related parameters can be set only the working mode is set to BC or OC, and when the Interface
Mode of the External Time Interface is set to External Time Interface.
Step 6 Click Apply.

Step 7 Click the Cable Transmitting Distance tab to set the cable parameters for the clock
compensation such as Transmitting Distance Mode, Transmitting Length(m), and
Transmitting Time(ns).
NOTE
Transmitting Distance Mode can be set to Time or Length.

l When Transmitting Distance Mode is set to Time, the transmitting time ranges from 0 ns to 1350 ns.
l When Transmitting Distance Mode is set to Length, the length range is 0-300 m.
l 1 m is equivalent to 4.5 ns.
Step 8 Click Apply.
----End
4.5.5 Setting the PTP NE Attributes

The NE attributes include Work Mode, Transmitting Message Multi-cast Mode, and Time
Adjusting.
Prerequisite
Procedure
Attribute from the Function Tree.
Step 2 Set Work Mode, SLAVE_ONLY, Time Adjusting, and Transmitting Packet Multi-cast
Mode.
Step 3 According to the working mode of the NE in the network, set Work Mode.
NOTE
The PTP standard defines four working modes, that is, BC, OC, TC, and TC+OC. When the NE working
mode is TC or TC+OC, if the PTP clock service or the clock source priority table is already configured,
you cannot modify the working mode.
Step 4 When Work Mode is set to OC, SLAVE_ONLY can be set to SLAVE_ONLY or
NON_SLAVE_ONLY.
NOTE
l SLAVE_ONLY indicates that the NE in the OC mode can only trace other PTP clocks.
l NON_SLAVE_ONLY indicates that in the OC mode the NE can function as the standy clock to trace
other PTP clocks and the NE can also function as the primary clock. Whether the NE functions as the
standby clock or primary clock depends on the quality of the PTP clock.
Step 5 When Work Mode is set to BC or OC, Time Adjusting is configurable.

NOTE
If the NE requires time synchronized, Time Adjusting needs to be set to Enabled.
Step 6 When Work Mode is set to BC or OC, Transmitting Packet Multi-cast Mode is configurable.
NOTE
If the mode is set to Entire Multi-cast, the equipment multicasts all the PTP packets. If the mode is set to
Part Multi-cast, the equipment unicasts the DELAY packets.

Step 7 When Work Mode is set to BC or OC, Protocol Packet Format is configurable.
NOTE
The Protocol Packet Format can be set to NMEA or UBX. The default parameter value is NMEA. This
parameter is valid only when Interface Protocol Type of the external time interface is set to 1PPS
+Time. When Interface Protocol Type of the external time interface is set to DCLS, the parameter can
still be set but the parameter value is invalid.
----End
4.5.6 Creating the PTP Clock Port

When a PTP clock port is created, the PTP clock port can access the PTP packets. You can set
the clock reference source number on the PTP clock port created in the BC or OC mode.
Prerequisite
Procedure
Step 2 Click the Port Status tab, and then click New to display the Create PTP Clock Port dialog
box.
Step 3 Select the corresponding board, and then select the corresponding port from Available Port.
Click .
Step 4 Click OK.
----End
4.5.7 Creating the PTP Clock Service

When the NE works in the TC or TC+OC mode, you need to create a PTP clock service on the
NE so that the NE transparently transmits the PTP clock packets.
Prerequisite
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Service from the
Function Tree.
Step 2 Click New to display the New Clock Service dialog box.
Step 3 Set Service ID and Service Name.
Step 4 In the dialog box, click the UNI tab. Then, click Configuration to display the Configure
Port dialog box.

Step 5 Select the port from the Available Port list, and then click to add the port to the
Selected Port list.
NOTE
l When the PTP packets contain VLAN tags, you need to set a VLAN tag for the port. The OptiX
RTN equipment supports the setting of only one VLAN tag.
l When two TC services share a port, set a VALN tag for the port if the port is a UNI port.
l If the port is Layer 3 port, the port can be used only as a UNI port for the TC service. The encapsulation
mode should be ETH and no VLAN tag can be set.
Step 6 Click OK, and thus the UNI configuration is complete.

Step 7 Optional: If the PTP packets need to be carried by the MPLS tunnel, you can set the related
NNI parameters.
1. In the dialog box, click the NNI tab. Then, click New to display the New PW dialog box.
2. Click the General Attributes tab to set PW ID, PW Type, PW Ingress Label, and PW
Egress Label.
3. Click to display Resource Selection Window. Select the tunnel that carries the
PW, and then click OK.
NOTE
Select the static MPLS tunnel, because the dynamic MPLS tunnel cannot carry the PTP packets.
4. Optional: Click the Advanced Attributes tab to set the corresponding parameters.

5. Click OK in the New PW dialog box to finish the PW configuration on the NNI side.
Step 8 Click OK in the New Clock Service dialog box to complete the configuration of the clock
service.
----End
4.5.8 Setting the PTP Packet Period

When setting the PTP packet period, you can set the periods of the ANNOUNCE, SYNC,
DELAY, and PDELAY packets.
Prerequisite
A PTP clock port must be created.
Procedure
Step 2 Click the Port Message tab to set P/E Mode and the corresponding packet periods.
NOTE
In P2P mode, the TC equipment transmits only the PDELAY packets. You can set the period for the TC
equipment to transmit the PDELAY packets.
Step 3 Click Apply.
----End

4.5.9 Setting the PTP Clock Port Status

In the scenario where the OptiX RTN equipment is connected to the client equipment, properly
set the status of the PTP clock port. For example, if the PTP packets should contain VLAN ID
or the PTP packets from the client side should be forwarded (Layer 2 or Layer 3), set the status
of the PTP clock port accordingly. By default, the equipment performs Layer 2 forwarding for
the PTP packets.
Prerequisite
The working mode of the NE must be set to BC or OC.
Procedure
Step 2 Click the Port Status tab and set PTP Message Format.
NOTE
If the port is configured with a clock service, do not change the PTP message format of the port.
Step 3 Optional: If the working mode of the NE is set to BC or OC, and the PTP packets contain VLAN
IDs, set PTP Message VLAN to a proper VLAN value accordingly.
NOTE
In the case of interconnection with the client equipment, if the client equipment forwards the PTP packets
according to VLAN IDs, the PTP packets should contain VLAN IDs.
Step 4 Optional: If the working mode of the NE is set to BC or OC, set Port Status accordingly.
NOTE
l Set Port Status to MASTER+SLAVE, MASTER, or SLAVE.

l When the Port Status is MASTER, Actual Port Status should not be SLAVE.
l When the Port Status is SLAVE, Actual Port Status should not be MASTER.
l If the NE is set to SLAVE_ONLY in the synchronization attributes, set Port Status only to
SLAVE.
Step 5 Optional: If the working mode of the NE is set to BC or OC, double-click the blank line below
Selected Clock Source to display the Clock Source Coding Configuration dialog box.
Step 6 Optional: Set the parameters related to the clock source and click OK.

CAUTION
The clock sources at the local port should be numbered in the same manner as the clock sources
at the upstream port, or the clock sources do not need to be numbered. Otherwise, clock tracing
fails if the working mode of the NE is set to BC or OC.
NOTE
When one PTP clock port receives multiple channels of clock signals, number the clock sources so that
the NE selects one clock source. For example, multiple TC clock services from the upstream equipment
are converged onto one clock port on the local equipment and then are transmitted to the downstream
equipment. As a result, the port on the downstream equipment connected to the upstream equipment
receives the multiple TC clock services. In this case, you need to number the clock sources at the port on
the downstream equipment.
Step 7 Click Apply.
----End
4.5.10 Setting the Cable Transmitting Wrap

The cable transmitting distance wrap indicates the transmitting time difference of the cables
between two sets of equipment in the transmit and receive directions. During deployment, you
can use the GPS to compute the transmitting time difference between the two directions. Set the
cable transmitting wrap, and thus the equipment performs the clock compensation. The wrap
modes includes the length wrap and time wrap. The equipment can choose only one mode.
Prerequisite
Procedure
Attribute.
Step 2 Click the Cable Transmitting Wrap tab.
Step 3 Set Wrap Direction. Positive direction indicates that the transmitting distance or transmitting
time of the clock receive end is longer than the transmitting distance or transmitting time at the
clock transmit end. Negative direction indicates that the transmitting distance or transmitting
time of the clock transmit end is longer than the transmitting distance or transmitting time at the
clock receive end.
Step 4 Wrap Mode can be set to Length or Time.
Step 5 According to Wrap Mode, set Wrap Length(m) or Wrap Time(ns).
NOTE
l The range of Wrap Length(m) is 0-14562 m.

l The range of Wrap Time(ns) is 0-65529 ns.
l 1 m is equivalent to 4.5 ns.
Step 6 Click Apply.
----End

4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source
When a clock port recovers from a failure, the system acknowledges the validity of the port a
certain period later. This period is referred to as the wait-to-restore (WTR) time. During the
WTR time, the system considers the clock signals as unavailable and the clock signals are not
involved in the clock source selection.
Prerequisite
The working mode of the NE must be set to BC, OC or TC+OC.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority
Table from the NE Explorer.
Step 2 Click the Clock Source Reversion Parameter tab and set Clock Source WTR Time(min.).
NOTE
Set Clock Source WTR Time(min.) within the range of 0 minutes to 12 minutes at a spacing of 1 minute.
By default, the WTR time is 5 minutes.
Step 3 Click Apply.
----End
4.5.12 Setting the PTP Clock Source Priority

If the NE works in the TC+OC mode, you need to set the priorities for the clock sources traced
by the OC. Normally, the OC traces the PTP clock source of the highest priority. If the PTP
clock source of the highest priority fails, the OC traces the PTP clock source of the second highest
priority. The priority table is configured with a source ID. When a local port receives a clock
source in the priority table, the port checks whether the domain that the clock source belongs to
is consistent with the domain configured at the local end.
Prerequisite
The working mode of the NE must be set to TC+OC.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority
Table from the NE Explorer.
Step 2 Click the Clock Source Priority Table tab and click New to create a clock source.
You can change the working mode of NE only after you delete the PTP clock source priority.
Step 3 Select a clock source and click or to adjust the priority of the clock source.

Step 4 Click Apply.
----End

Operation Guide for RTN NE Management 5 Configuring Orderwire
5 Configuring Orderwire
About This Chapter
You can configure orderwire for NEs by using the U2000.

5.1 Configuring Orderwire
To provide the maintenance personnel with a dedicated express orderwire channel, you can
configure orderwire for NEs.
5.2 Configuring F1 Data Port Services
You can use the U2000 to configure F1 Data port services.
5.3 Configuring Asynchronous Data Services
You can configure Asynchronous data services by using the U2000.
5.4 Configuration Example (Synchronous Data Services RTN 600)
This topic uses an example to describe how to plan the service parameters and complete the
entire process of configuring the parameters of each NE according to the synchronous data
service requirements.
5.5 Configuration Example (Asynchronous Data Services RTN 600)
entire process of configuring the parameters of each NE according to the point-to-point
asynchronous data service requirements.

5 Configuring Orderwire Operation Guide for RTN NE Management
5.1 Configuring Orderwire

To provide the maintenance personnel with a dedicated express orderwire channel, you can
configure orderwire for NEs.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Orderwire from the Function
Tree. Click the General tab.
Step 2 Click Query to query information from the NE.
Step 3 Set Call Waiting Time(s), Telephone No. and orderwire ports.
NOTE
l Call Waiting Time(s) should be set to the same value for all NEs with orderwire communication.
When the number of NEs is smaller than 30, set the value to 5 seconds. Otherwise, set it to 9 seconds.
l The telephone number must be unique in an orderwire subnet.
l Set the length of the telephone number according to the actual requirements. The maximum length is
eight digits and the minimum length is three digits. In the same orderwire subnet, the number length
must be the same.
Step 4 Click Apply.
----End
5.2 Configuring F1 Data Port Services

You can use the U2000 to configure F1 Data port services.
5.2.1 F1 Data Port Services

The F1 Data Port Services is a point-to-point (P2P) service that is transparently transmitted by
using the F1 byte.
5.2.2 Configuring F1 Data Port Services
The F1 Data Port Services uses the F1 byte (section user channel byte) to transparently transmit
services. If a maintenance engineer requires extra overhead bytes to temporarily set up orderwire
connections, the engineer can create F1 data port services. The transmission rate is 64 kbit/s,
that is, E0 level.
5.2.1 F1 Data Port Services

The F1 Data Port Services is a point-to-point (P2P) service that is transparently transmitted by
using the F1 byte.
The F1 data port is a transparent data port that transports codirectional P2P services at the rate
of 64 kbit/s. It does not support data broadcast. Hence, only the P2P services can be turned up
at an F1 data port.
When you use the F1 data port, you only need to configure routes for the 64 kbit/s data, that is,
whether the data is added to, dropped from or passes through the port. If you manually configure
the port, you need to use the U2000 to configure each node along the communication channel.
After the configurations take effect, the data can be transmitted.

Example for Configuring the F1 Data Port Services

Figure 5-1 shows how a F1 Data Port Services is configured.
Figure 5-1 Configuring the F1 data port service

F1 Data Port F1 Data Port
Node A Node B Node C
Node A and node C transmit data through the F1 data port. You can use the U2000 to configure
each node as follows:
l Configure added or dropped services at node A. Select the F1 data port and a port on the
intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port
service from the client side is added or dropped from the F1 data port of the orderwire
board, and is transmitted through the a port on the intermediate frequency (IF) board.
l Configure pass-through services at node B. Select two a port on the intermediate frequency
(IF) board as the data channel ports. In this case, the F1 data port service passes through
the two a port on the intermediate frequency (IF) board at this node.
l Configure added or dropped services at node C. Select the F1 data port and a port on the
intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port
service is cross-connected from the a port on the intermediate frequency (IF) board to the
orderwire board, and then added or dropped from the F1 data port of the orderwire board.
5.2.2 Configuring F1 Data Port Services

The F1 Data Port Services uses the F1 byte (section user channel byte) to transparently transmit
services. If a maintenance engineer requires extra overhead bytes to temporarily set up orderwire
connections, the engineer can create F1 data port services. The transmission rate is 64 kbit/s,
that is, E0 level.
Prerequisite
The boards that are related to the synchronous data services must be configured.
Context
In the case of the RTN 610/620, the synchronous data services are transmitted over the F1
overhead bytes in the SDH/PDH radio frame or STM-N frame.In the case of the RTN 605, the
synchronous data services are transmitted over the F1 overhead bytes in the radio frame.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
from the Function Tree.

Step 2 Click the F1 Data Port tab.

Step 3 Press the Ctrl key and select two data channels from Available Data Channel. Click
NOTE
Data Channel 1 and Data Channel 2: Depending on the board configuration, the following ports can be
selected.
l SDH optical/electrical port: When the SDH optical/electrical line port is selected, the F1 byte in the
SDH frame of this port is used.
l IF port: When the IF port is selected, the self-defined F1 byte in the radio frame of this port is used.
l F1 port: When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1
port conforms to the G.703 and the rate is 64 kbit/s.
l external clock port of the PXC board: When the PXC-1 is selected, the external clock port of the PXC
board is used. In this case, the external clock port is used as the output port of the overhead bytes.
When the F1 data channel of the RTN 605 transmits the synchronous data services, the F1 data channel is
bound with the working channel in most cases.
Step 4 Click Apply.

----End
5.3 Configuring Asynchronous Data Services

You can configure Asynchronous data services by using the U2000.
5.3.1 Asynchronous Data Services

The asynchronous data interfaces of the RTN equipment uses RS232 to implement universal
asynchronous receiver/transmitter (UART) full-duplex communication. The data is transmitted
transparently, and it is not required to configure interface rate or transmission control protocols
by using the U2000. The maximum bit rate is 19.2 kbit/s. You can connect an NE to the data
terminal equipment through this asynchronous data interface, and configure the communication
mode as point to point.
5.3.2 Configuring Asynchronous Data Services
To configure the asynchronous data services, you need to set the broadcast data port of the RTN
equipment. In the case of the RTN 610/620, the Serial byte in the SDH/PDH radio overheads or

any of the bytes Serial1-Serial4 in the normal SDH overheads is used to transparently transmit
the asynchronous data services. In the case of the RTN 605, the Serial byte in the PDH radio
overheads is used to transmit the asynchronous data services. The asynchronous data services
need to not be configured, but are automatically activated.
5.3.1 Asynchronous Data Services

The asynchronous data interfaces of the RTN equipment uses RS232 to implement universal
asynchronous receiver/transmitter (UART) full-duplex communication. The data is transmitted
transparently, and it is not required to configure interface rate or transmission control protocols
by using the U2000. The maximum bit rate is 19.2 kbit/s. You can connect an NE to the data
terminal equipment through this asynchronous data interface, and configure the communication
mode as point to point.
Asynchronous data services use the overhead bytes (serial) in the SDH or PDH microwave or
any one byte (serial1 through serial4) in the ordinary SDH overhead as the broadcast data
communication channel.
5.3.2 Configuring Asynchronous Data Services

To configure the asynchronous data services, you need to set the broadcast data port of the RTN
equipment. In the case of the RTN 610/620, the Serial byte in the SDH/PDH radio overheads or
any of the bytes Serial1-Serial4 in the normal SDH overheads is used to transparently transmit
the asynchronous data services. In the case of the RTN 605, the Serial byte in the PDH radio
overheads is used to transmit the asynchronous data services. The asynchronous data services
need to not be configured, but are automatically activated.
Prerequisite
The boards that are related to the asynchronous data services must be configured.
Context
The asynchronous data port of the OptiX RTN 600 is an RS-232 port and can implement the
universal asynchronous receiver/transmitter (UART) full-duplex communication. The service
transmission is required to be point-to-point transparent transmission. Therefore, the port rate
and transmission control protocol need not be configured and the maximum communication rate
is 19.2 kbit/s. Hence, the asynchronous data port is also considered as the transparent data port.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
Step 2 Click the Broadcast Data Port tab.
Step 3 Set the parameters of the broadcast data port.

NOTE
l Overhead Byte: SERIAL1-SERIAL4, and default value is SERIAL1.

l In the case of an SDH optical/electrical line, the preset overhead byte is used to transmit the
asynchronous data services.
l In the case of a radio link, a self-defined Serial overhead byte in the radio frame is used to transmit
the asynchronous data services.
l Broadcast Data Source/Broadcast Data Sink: Depending on the board configuration, the following
values can be selected.
l SERIAL1-SERIAL4: When this parameter is set so that it is the same as the SERIAL byte
corresponding to the Overhead Byte, the asynchronous data port on the SCC board is used.
l SDH optical/electrical port: When this parameter is set to the SDH optical/electrical line port, the
Overhead Byte of this port is used.
l IF port: When this parameter is set to IF port, the self-defined Serial byte in the radio frame of this
port is used.
l external clock port of the PXC board: When this parameter is set to the external clock port on the
PXC board, the external clock port on the PXC board is used. In this case, the external clock port
is used as the output port of overhead bytes.
Step 4 Click Apply.
----End
5.4 Configuration Example (Synchronous Data Services

RTN 600)
entire process of configuring the parameters of each NE according to the synchronous data
5.4.1 Networking Diagram

The networking diagram forms the foundation of service planning. In the following example,
the networking diagram shows the NE networking mode and service requirements.
5.4.2 Service Planning
According to the service requirements and the equipment specifications that are shown in the
networking diagram, the network planning department can plan all the services of the NEs. In
the following example, the service planning covers all the parameter information required for
configuring the NEs.
5.4.3 Configuration Process
You can configure the synchronous data services of each NE based on the parameters of the
service planning, by using the NMS.

As shown in Figure 5-2, NE1, NE2, and NE3 are the OptiX RTN 600 NEs configured with the
IDU 620. The new service requirements are as follows: the data communication equipment
between NE1 and NE3 must communicate with each other, and the required bandwidth must be
64 kbit/s.
Figure 5-2 Networking diagram

NE 1 NE 2 NE 3
64kbit/s 64kbit/s

Board Configuration Information

The SCC boards of NE1 and NE3 need to provide the F1 synchronous data ports. In the case of
the OptiX RTN 600, the SL61SCC VER.C provides the F1 synchronous data port whereas the
SL61SCC VER.B does not provide the F1 synchronous data port.

Configuring the Synchronous Data Port
Table 5-1 Configuration of the synchronous data port
Parameter NE1 NE2 NE3
Data Channel 1 6-SL1 5-IF1A 5-IF1A
Data Channel 2 F1 6-SL1 F1
Table 5-2 Configuration of the synchronous data port
Data Channel 1 6-SL1 5-IF0A 8-IF0-1
Data Channel 2 F1 6-SL1 F1
Timeslot Allocation Information
Figure 5-3 Timeslot allocation of synchronous data services
Station NE1 NE2 NE3
Timeslot 6-SL1-1 6-SL1-1 5-IF1A-1 5-IF1A-1
F1 F1
2-SCC: F1 2-SCC: F1
Add/Frop
Forward
Station NE1 NE2 NE3
Timeslot 6-SL1-1 6-SL1-1 5-IF0A-1 8-IF0-1
F1 F1
2-SCC: F1 2-SCC: F1
Add/Frop
Forward
l The F1 port on the SCC board in slot 2 of NE1 and F1 port on the SCC board in slot 2 of
NE3 are used to add/drop the synchronous data services.
l The F1 overhead byte on the SDH line between the SL1 board in slot 6 of NE1 and the SL1
board in slot 6 of NE2 is used to transmit the synchronous data services.
l The F1 overhead byte on the radio link between the IF1A board in slot 5 of NE2 and the
IF1A board in slot 5 of NE3 is used to transmit the synchronous data services.

l The synchronous data services are passed through between the SL1 board in slot 6 and the
IF1A board in slot 5 of NE2.
l The F1 port on the SCC board in slot 2 of NE1 and F1 port on the SCC board in slot 2 of
NE3 are used to add/drop the synchronous data services.
l The F1 overhead byte on the SDH line between the SL1 board in slot 6 of NE1 and the SL1
board in slot 6 of NE2 is used to transmit the synchronous data services.
l The F1 overhead byte on the radio link between the IF0A board in slot 5 of NE2 and the
IF board in logical slot 8 of NE3 is used to transmit the synchronous data services.
l The synchronous data services are passed through between the SL1 board in slot 6 and the
IF0A board in slot 5 of NE2.

You can configure the synchronous data services of each NE based on the parameters of the
Prerequisite
All the required boards must be added.
Procedure
Step 1 5.2.2 Configuring F1 Data Port Services.
1. In the NE Explorer, select NE1 and then choose Configuration > Orderwire from the
Function Tree.
2. Click the F1 Data Port tab.
3. Hold down the Ctrl key and select two data channels from Available Data Channel. Then,
click Apply.
Parameter Value Range Description
Data Channel 1 6-SL1-1 When the 6-SL1-1 port is selected, the F1 byte in
the SDH frame of this port is used.
Data Channel 2 F1 When the F1 port is selected, the F1 synchronous

data port on the SCC board is used. The F1 port
complies with ITU-T G.703 and the rate is 64 kbit/
s.

Function Tree.
click Apply.

Data Channel 1 6-SL1-1 When the 6-SL1-1 port is selected, the F1 byte in
the SDH frame of this port is used.
Data Channel 2 5-IF1A-1 When the 5-IF1A-1 port is selected, the self-
defined F1 byte in the radio frame of this port is
used.

Function Tree.
click Apply.
Data Channel 1 5-IF1A-1 When the 5-IF1A-1 port is selected, the self-
defined F1 byte in the radio frame of this port is
used.
Data Channel 2 F1 When the F1 port is selected, the F1 synchronous

data port on the SCC board is used. The F1 port
complies with ITU-T G.703 and the rate is 64 kbit/
s.
----End
5.5 Configuration Example (Asynchronous Data Services

RTN 600)
entire process of configuring the parameters of each NE according to the point-to-point
asynchronous data service requirements.

The timeslot allocation can be planned for the asynchronous data services based on the
networking diagram.
You can configure the asynchronous data services of each NE based on the parameters of the


As shown in Figure 5-4, NE1, NE2, and NE3 are the OptiX RTN 600 NEs configured with the
IDU 620. Asynchronous data services need to be activated between NE1 and NE3. The service
requirements are as follows:
l NE1 must be connected to the monitor server.

l NE3 must be connected to the environment monitor.
l Point-to-point communication must exist between the monitor server and the environment
monitor, through services at the asynchronous data ports.
l The requirements for the environment monitor are as follows:
The level of the port must be RS-232. Logic "1" stands for -5 V to -15 V, and logic "0"
stands for +5 V to +15 V.
When no data is transmitted, the port must be of high RS-232 level (about -9 V).

NE 1 NE 2 NE 3
RS-232 RS-232

The timeslot allocation can be planned for the asynchronous data services based on the
networking diagram.
Configuration of the Asynchronous Data Services
Table 5-3 Configuration of the asynchronous data services
Overhead Byte SERIAL1 SERIAL1 SERIAL1
Broadcast Data 6-SL1-1 5-IF1A-1 5-IF1A-1

Source
Broadcast Data Sink S1 6-SL1-1 S1

Table 5-4 Configuration of the asynchronous data services
Overhead Byte SERIAL1 SERIAL1 SERIAL
Broadcast Data 6-SL1-1 5-IF0A-1 8-IF0-1

Source
Broadcast Data Sink S1 6-SL1-1 S1
Figure 5-5 Timeslot allocation diagram
Station NE1 NE2 NE3
Timeslot 6-SL1-1 6-SL1-1 5-IF1A-1 5-IF1A-1
Serial1 Serial1
2-SCC: S1 2-SCC: S1
Add/Frop
Forward
Station NE1 NE2 NE3
Timeslot 6-SL1-1 6-SL1-1 5-IF0A-1 8-IF0-1
Serial1 Serial
2-SCC: S1 2-SCC: S1
Add/Frop
Forward
As shown in the timeslot allocation diagram, the asynchronous data services are as follows:
l The S1 port on the SCC board in slot 2 of NE1 and S1 port on the SCC board in slot 2 of
NE3 are used to add and drop the asynchronous data services.
l The S1 port on the SCC board in slot 2 of NE1 and S1 port of NE3 are used to add and
drop the asynchronous data services.
l The SERIAL1 overhead byte on the SDH optical line between the SL1 board in slot 6 of
NE1 and the SL1 board in slot 6 of NE2 is used to transmit the asynchronous data services.
l The self-defined SERIAL byte on the radio link between the IF1A board in slot 5 of NE2
and the IF1A board in slot 5 of NE3 to transmit the asynchronous data services.
l The self-defined SERIAL byte on the radio link between the IF0A board in slot 5 of NE2
and the IF0 board in logical slot 8 of NE3 to transmit the asynchronous data services.
l The asynchronous data services are passed through between port 1 of the SL1 board in slot
6 and port 1 of the IF1A board in slot 5 of NE2.
l The asynchronous data services are passed through between port 1 of the SL1 board in slot
6 and port 1 of the IF0A board in slot 5 of NE2.


You can configure the asynchronous data services of each NE based on the parameters of the
Prerequisite
Procedure
Step 1 5.3.2 Configuring Asynchronous Data Services.
Function Tree.
2. Click the Broadcast Data Port tab. After setting the parameters, click Apply.
Overhead Byte SERIAL1 l In this example, Overhead Byte is set to

SERIAL1.
l In the case of a radio link, a self-defined
SERIAL overhead byte in the radio frame is
used to transmit the asynchronous data
services.
Broadcast Data 6-SL1-1 l In this example, Broadcast Data Source is

Source set to 6-SL1-1.
l When this parameter is set to the SDH
optical/electrical line port, Overhead Byte of
this port is used.
Selected S1 l In this example, Broadcast Data Sink is set

Broadcast Data to S1.
Sink l When this parameter is set so that it is the
same as Overhead Byte, the asynchronous
data port on the SCC board is used.

Function Tree.


SERIAL1.
services.
Broadcast Data 6-SL1-1 l In this example, Broadcast Data Source is

Source set to 6-SL1-1.
l When this parameter is set to the SDH
optical/electrical line port, Overhead Byte of
this port is used.
Selected 5-IF1A-1 l In this example, Selected Broadcast Data

Broadcast Data Sink is set to 5-IF1A-1.
Sink l When this parameter is set to IF port, the self-
defined SERIAL byte in the radio frame of
this port is used.

Function Tree.

SERIAL1.
services.
Broadcast Data 5-IF1A-1 l In this example, Broadcast Data Source is

Source set to 5-IF1A-1.
l When this parameter is set to IF port, the self-
defined SERIAL byte in the radio frame of
this port is used.
Selected S1 l In this example, Selected Broadcast Data

Broadcast Data Sink is set to S1.
Sink l When this parameter is set so that it is the
same as Overhead Byte, the asynchronous
data port on the SCC board is used.
----End

Operation Guide for RTN NE Management 6 Configuring Environment Monitor Interfaces
6 Configuring Environment Monitor

Interfaces
About This Chapter
6.1 Configuring External Alarms

To configure external alarms, you need to configure the environment monitor port. After the
outputting of external alarms is configured, the alarm information of the OptiX RTN can be
output to other equipment. After the inputting of external alarms is configured, the alarm
information of other equipment can be input to the OptiX RTN and then to the processing
equipment at the remote end.
6.2 Configuration Example (External Alarms RTN 600)
This topic uses an example to describe how to plan the parameters of the external alarms and
complete the data configuration according to the external alarm requirements.

6 Configuring Environment Monitor Interfaces Operation Guide for RTN NE Management
6.1 Configuring External Alarms

To configure external alarms, you need to configure the environment monitor port. After the
outputting of external alarms is configured, the alarm information of the OptiX RTN can be
output to other equipment. After the inputting of external alarms is configured, the alarm
information of other equipment can be input to the OptiX RTN and then to the processing
equipment at the remote end.
Prerequisite
Apply to the EOW, AUX and CXP boards.
Context
The external alarms are also considered as housekeeping alarms. The external alarm port is a
relay port. This port can be either in the "on" state or in the "off" state.
The alarm input ports report the RELAY_ALARM alarm (the alarm parameter indicates the port
number of the input alarm) after the external alarm is triggered. To ensure that the external alarm
port works normally, the external alarm cables must be correctly connected.
Procedure
Step 1 Select the board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the Function
Tree.
Step 2 In the case of RTN 600 NEs:

1. Configure the input alarm.
a. Select Input Relay from the drop-down list.
b. Set the parameters of the input alarm.
c. Click Apply.
2. Configure the output alarm.
a. Select Output Relay from the drop-down list.
b. Set the parameters of the output alarm.

c. Click Apply.
1. Select the attributes you want to configure from the drop-down list.
2. Click Query to query parameter values.
3. Double-click a field to select or enter a value. click Apply.
----End
6.2 Configuration Example (External Alarms RTN 600)

This topic uses an example to describe how to plan the parameters of the external alarms and
complete the data configuration according to the external alarm requirements.

The networking diagram forms the foundation of service planning. This topic describes the
external alarm requirements.
The engineering design department plans the external alarm setting based on the networking
diagram.
You can configure the external alarm services based on the parameters of the service planning,
by using the NMS.

The networking diagram forms the foundation of service planning. This topic describes the
external alarm requirements.
An OptiX RTN 600 NE must meet the following external alarm requirements:
l Outputs two external alarmsone external alarm, and reports a critical alarm and a major
alarmreports a critical alarm. The alarm modes are the same, that is,mode is as follows: the
port enters the "off" state when an alarm is generated.
l Inputs three external alarms. The alarm modes are the same, that is, an alarm is generated
when the port enters the "on" state.
Alarm In1
Alarm In2
Alarm In3
Alarm Out

Alarm In1
Alarm In2
Alarm In3
Alarm Out1
Alarm Out2

The engineering design department plans the external alarm setting based on the networking
diagram.
Table 6-1 Configuration of the external alarms

Port No. Alarm Mode Alarm Trigger Condition
Alarm output port 1 An Alarm is Generated if the Critical Alarm Auto Trigger
Relay Turns Off and Low
Level is Caused
Alarm output port 2 An Alarm is Generated if the Major Alarm Auto Trigger
Level is Caused
Alarm input port 1 An Alarm is Generated if the -

Relay Turns On and High
Level is Caused

Level is Caused

Level is Caused
Table 6-2 Configuration of the external alarms

Alarm output port An Alarm is Generated if the Critical Alarm Auto Trigger
Level is Caused

Level is Caused


Level is Caused

Level is Caused

You can configure the external alarm services based on the parameters of the service planning,
by using the NMS.
Prerequisite
You must be logged in to the NE.
Procedure
Step 1 Configure external alarms.
1. In the NE Explorer, select the EOW board and then choose Configuration > Environment
Monitor Configuration > Environment Monitor Interface from the Function Tree.
2. Configure the input alarm. Select Input Relay from the drop-down list. Click Apply.
Paramet Value Range Description

er
EOW-1 EOW-2 EOW-3
Using Used In this example, Using Status of

Status the alarm interface is set to
Used.
Alarm An Alarm is Generated if the Relay The alarm is generated when the
Mode Turns On and High Level is Caused relay is on.
3. Configure the output alarm. Select Output Relay from the drop-down list. Click Apply.
EOW-1
Use or Not Used In this example, Use or Not of the alarm interface
is set to Used.
Working Mode Automatic Changing the status of the output relay according
to Alarm Trigger Conditions and Alarm
Mode.

EOW-1
Alarm Trigger Critical Alarm The status of the output relay is changed
Conditions Auto Trigger automatically according to the preset value.
Alarm Mode An Alarm is The alarm is generated when the relay is off.
Generated if the
Relay Turns Off
and Low Level is
Caused
EOW-1 EOW-2
Use or Not Used In this example, Use or Not of the alarm

interface is set to Used.
Working Automatic Changing the status of the output relay

Mode according to Alarm Trigger
Conditions and Alarm Mode.
Alarm Critical Major Alarm The status of the output relay is changed
Trigger Alarm Auto Auto Trigger automatically according to the preset
Conditions Trigger value.
Alarm An Alarm is Generated if the The alarm is generated when the relay is
Mode Relay Turns Off and Low off.
Level is Caused
----End

Operation Guide for RTN NE Management 7 Configuring Interfaces (RTN 600)
7 Configuring Interfaces (RTN 600)
About This Chapter
This section describes how to set the interface attributes of the boards.

7.2 Configuring the Parameters of Various Ports
This topic describes how to set the parameters of various ports. Normally, the default values of
the parameters are adopted to meet the relevant requirements. In certain cases, however, the
parameters of the ports need to be modified.
7.3 Configuring Ethernet Ports
The Ethernet ports contain the internal Ethernet ports and external Ethernet ports. The external
Ethernet ports are the physical ports that are used to connect the Ethernet equipment. The internal
Ethernet ports (VCTRUNKs) are internal paths that implement Ethernet over SDH.
7.4 Disabling an Ethernet Port
It is recommended that you disable an unused Ethernet port to suppress the reporting of the
alarms related to the port.
7.5 Configuring a Service Load Indication
There are two service load indications, which are Non-Loaded and Load. If a path is configured
with services and carries real services, set Service Load Indication to Load. If a path is
configured with services but does not carry real services, set Service Load Indication to Non-
Loaded to suppress the reporting of certain alarms.

7 Configuring Interfaces (RTN 600) Operation Guide for RTN NE Management

Procedure
Step 1 Select the corresponding navigation path and check the related board parameters.
1. Check SDH board parameters. For the SDH board parameters, see Table 7-1.
Table 7-1 SDH board parameters

Board Type Parameter Navigation Path Application
Scenario
SDH Laser Switch a. In the NE When configuring

Explorer, select services on an
a board. optical interface of
b. Choose a board, enable this
Configuration parameter.
> SDH
Optical(Electrical) l Non-loopback:
Interface from
Interface Loopback It is a normal
the Function
state. When the
Tree.
equipment runs
c. Click By normally, set
Board/Port this parameter to
(channel) and non-loopback.
select Port from
l Inloop: The loop
the drop-down
is performed
list.
toward the local
NE.
l Outloop: The
loop is
performed
toward the
opposite NE.
Inloop and
outloop of an
optical interface
affect services.
They are used to
locate faults.
2. Check PDH board parameters. For the PDH board parameters, see Table 7-2.

Table 7-2 PDH board parameters
Boar
Paramet Navigation
er Path
Type
Tributary l Non-loopback: It is a normal state. When

Loopback the equipment runs normally, set this
parameter to non-loopback.
l Inloop: When input service signals reach
the tributary board of the target NE, the
a. In the NE signals revert to the original trail. This
Explorer, function is used to locate faults of each
select a board. service path.
b. Choose l Outloop: When input service signals reach
Configuratio the tributary board through the input port
n > PDH of the local NE, the signals are looped back
Interface directly to the service output end.
from the
PDH Service Function l Non-loaded: The service path does not
Load Tree. process the services that are carried, to
Indication c. Click By suppress alarms in non-loaded service
Board/Port paths.
(channel) l Load: The service path processes the
and select services that are carried. In the case of a
Port from the tributary board that has services, set this
drop-down parameter to Load.
list.
Retiming Normal, Retiming Mode of Tributary Clock,
Mode Retiming Mode of Cross-Connect Clock
Default: Normal
Sets the retiming mode of the board. The
default value is usually selected.
3. Check RTN board parameters. For the RTN board parameters, see Table 7-3.
Table 7-3 RTN board parameters
Boar
Paramet Navigation
er Path
Type
Radio a. In the NE Specifies the microwave working mode. Its

Work Explorer, formats are service capacity, working
Mode select a board. bandwidth and modulation mode.
b. Choose The transmit end and the receive end must
RTN have the same settings of the microwave
Configuratio
n > IF working mode.
Radio Interface Radio Link ID: 1 to 4094

Link ID from the

Boar
Paramet Navigation
er Path
Type
IF Port Function Sets the loopback status of an intermediate

Loopback Tree. frequency interface on the equipment.
c. Click By Non-Loopback refers to the normal status. It
Board/Port is not required to set loopback during normal
(channel) equipment operation.
and select
Outloop means that the input signal passes
Port from the
through the ingress port and reaches the
drop-down
intermediate frequency board at the local NE
list.
and then is directly loopbacked to the service
egress end.
Inloop means that the input signal returns
from the intermediate frequency board of the
destination NE along the original trail.
This function is usually used to locate faults
for various IF interfaces. Performing loopback
on an intermediate frequency interface is a
diagnosis function which may affect services
of related ports. Exercise caution before
performing this function.
2M Enables or disables a 2 Mbit/s bypath service.

Wayside This parameter is available only when you set
Enable Radio Work Mode to STM-1,28MHz,
Status 128QAM.
ATPC When the ATPC is enabled, according to the

Enable current receive power of the ODU and the set
Status ATPC thresholds, the ATPC module inserts
the ATPC overhead. According to the ATPC
overhead, the opposite ODU adjusts the
transmit power.
When the ATPC is disabled, the ATPC
module does not insert any ATPC overhead.
4. Check data board parameters. For the data board parameters, see Table 7-4.
Table 7-4 Data board parameters

Boar
Parame
ter
Type
Enabled/ a. In the NE Explorer,

Ethern Disabled select a board. When configuring Ethernet board port
et b. Choose services, set the port to Enabled.
Configuration >

Boar
Parame
ter
Type
Working Ethernet Interface Set the working mode of Ethernet ports

Mode Management > according to networking configuration
Ethernet requirements.
Interface from the
Maximu Function Tree. When a packet exceeds the maximum
m Frame frame length that is set, the packet is
c. Click External
Length discarded. Alternatively, the packet
Port.
length is minimized to satisfy the
d. Click the Basic specified frame length. By default, the
Attributes tab. value is set to 1522, unless otherwise
specified.
MAC l Non-loopback: It is a normal state.

locate faults.
PHY l Non-loopback: It is a normal state.

locate faults.
TAG l Tag Aware: If the client-side

a. In the NE Explorer, equipment sends tag packets, set the
select a board. TAG attribute of external ports to
Tag Aware.
b. Choose
Configuration > l Access: If the client-side equipment
Ethernet Interface sends untag packets, set the TAG
Management > attribute of external ports to Access.
Ethernet l Hybrid: If the client-side equipment
Interface from the sends tag and untag packets, set the
Function Tree. TAG attribute of external ports to
c. Click External Hybrid.
Port.
Entry This parameter is used to identify tags in
Detectio d. Click the TAG data packets. During the configuration of
n Attributes tab. VLAN services, set this parameter to
Enabled.

Step 2 Modify board parameters according to service planning and actual board configurations.
----End
7.2 Configuring the Parameters of Various Ports

This topic describes how to set the parameters of various ports. Normally, the default values of
the parameters are adopted to meet the relevant requirements. In certain cases, however, the
parameters of the ports need to be modified.
7.2.1 Configuring the Parameters of SDH Interfaces
This section describes how to set the parameters of SDH interfaces, including loopback of the
SDH interface board and the enabling/disabling of the lasers at the SDH optical ports.
7.2.2 Configuring the Parameters of PDH Interfaces
When the IDU 610/620 is used, you can set the loopback status and service loading indication
of the tributary boards, by performing the operations. In the case of the E1 interface board, you
can also set the tributary retiming function. In the case of the E3/T3 interface board, you can
also set the service type and signal equalization. When the IDU 605 is used, you can set the path
usage status, tributary loopback status, and path impedance, by performing the operations.
7.2.3 Setting the Parameters of IF Ports
This topic describes how to configure the parameters of IF ports, including the IF attributes and
ATPC attributes of the IF boards.
7.2.4 Setting the Parameters of ODU Ports
This section describes how to set the parameters of ODU ports, including the RF attributes,
power attributes, and advanced attributes of the ODU.
7.2.1 Configuring the Parameters of SDH Interfaces

This section describes how to set the parameters of SDH interfaces, including loopback of the
SDH interface board and the enabling/disabling of the lasers at the SDH optical ports.
Prerequisite
The required SDH interface boards must be added.
Procedure
Step 1 Select the SDH interface board from the Object Tree in the NE Explore. Choose
Configuration > SDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel) (default option of the system).
Step 3 Select Port from the dropdown list and set the parameters of the SDH interface board.

Step 4 Click Apply.

A dialog box is displayed and click OK.
Step 5 Select VC4 Channel from the dropdown list.
Step 6 Configure VC-4 path loopback.
Step 7 Click Apply.

----End
Parameters
Parameter Value Default Value Description
Laser Switcha Open, Close Open l This parameter indicates whether the
laser is enabled to receive/transmit
optical signals.
l Normally, this parameter takes the
default value.
Optical (Electrical) Non-Loopback, Non-Loopback l Optical (electrical) inloop indicates that

Interface Loopback Inloop, Outloop loopback occurs in the SDH optical
(electrical) signals to be transmitted to
the opposite end.
l Optical (electrical) outloop indicates that
loopback occurs in the SDH optical
(electrical) signals to be received.
default value.

Parameter Value Default Value Description
VC4 Loopback Non-Loopback, Non-Loopback l VC-4 path inloop indicates that loopback
Inloop, Outloop occurs in the VC-4 signals to be
transmitted to the opposite end.
l VC-4 path outloop indicates that
loopback occurs in the VC-4 signals to
be received.
default value.
NOTE
a: Only SDH optical interface boards support this parameter.
7.2.2 Configuring the Parameters of PDH Interfaces

When the IDU 610/620 is used, you can set the loopback status and service loading indication
of the tributary boards, by performing the operations. In the case of the E1 interface board, you
can also set the tributary retiming function. In the case of the E3/T3 interface board, you can
also set the service type and signal equalization. When the IDU 605 is used, you can set the path
usage status, tributary loopback status, and path impedance, by performing the operations.
Prerequisite
The required PDH interface boards must be added.
Procedure
Step 1 Select the PDH interface board from the Object Tree in the NE Explorer. Choose
Configuration > PDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel) (default value).
Step 3 Select Port from the drop-down list, Set the parameters of the PDH interface.
Step 4 Select Port from the drop-down list, Set the parameters of the PDH interfaces according to the
types of the PDH interfaces.
l Set the parameters of the PDH interfaces on the E1 interface board.

l Set the parameters of the PDH interface on the E3/T3 interface board.
Step 5 Click Apply.

----End
Parameters
Tributary Loopback Non-Loopback, Non-Loopback l Tributary inloop indicates that loopback

Inloop, Outloop occurs in the tributary signals to be
transmitted to the remote end.
l Tributary outloop indicates that
loopback occurs in the tributary signals
to be received.
l Generally, this parameter takes the
default value.
Path Impedance 75 ohms, 120 ohms 75 ohms Generally, this parameter takes the default
value.
Service Load Load, Non-Loaded Load l This parameter is valid for the tributary
Indication ports that are configured with services.
l When this parameter is set to Load, the
board detects whether alarms exist in this
path.
l When this parameter is set to Non-
Loaded, the board does not detect
whether alarms exist in this path.
default value.

Retiming Modea Normal, Retiming Normal l By using the retiming function, the
Mode of Tributary retiming reference signal from the SDH
Clock, Retiming network and the service data signal are
Mode of Cross- combined and then sent to the client
Connect Clock equipment, thus decreasing the output
jitter in the signal. In this way, the
retiming function ensures that the service
code flow can normally transfer the
retiming reference signal.
l When this parameter is set to Normal,
the retiming function is not used.
l When this parameter is set to Retiming
Mode of Tributary Clock, the retiming
function is used with the clock of the
upstream tributary unit traced.
l When this parameter is set to Retiming
Mode of Cross-Connect Clock, the
retiming function is used with the clock
of the cross-connect unit traced.
l It is recommended that the external
clock, instead of the retiming function, is
used to provide an external clock for the
client equipment.
l If the retiming function is required, it is
recommended that you adopt Retiming
Mode of Cross-Connect Clock.
Port Service Typeb E3, T3 E3 l This parameter indicates the type of the
services the tributary board processes.
l Set this parameter according to the type
of the accessed services.
Input Signal Unequalized, Unequalized l This parameter is valid only when

Equalizationb Equalized Service Type is set to T3.
input signals are equalized.
l If the trunk cable exceeds 70 m, it is
recommended that you set this parameter
to Equalized. Otherwise, adopt the
default value.

Output Signal Unequalized, Unequalized l This parameter is valid only when

Equalizationb Equalized Service Type is set to T3.
output signals are equalized.
l If the trunk cable exceeds 70 m, it is
to Equalized. Otherwise, adopt the
default value.
NOTE
l a: Only E1 interface boards support this parameter.

l b: Only E3/T3 interface boards support the parameters.
7.2.3 Setting the Parameters of IF Ports

This topic describes how to configure the parameters of IF ports, including the IF attributes and
ATPC attributes of the IF boards.
Prerequisite
The required IF boards must be added.
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree. Choose Configuration > IF
Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
Step 3 Set each parameter for the IF attributes.
NOTE
The IFH1 board of the IDU 605 1F/2F does not support the setting of the Radio Work Mode.
The IFH2 board of the IDU 620 does not support the setting of the Radio Work Mode.
Step 4 Click Apply.

Step 5 Click the ATPC Attributes tab.
Step 6 Set each parameter for the ATPC attributes.

NOTE
The IF0 board of the IDU 605 1A/1B/2B does not support the ATPC Automatic Threshold Enable
Status.
Step 7 Click Apply.
----End

Parameters
Radio Work Mode l In the case of the 1,4E1,7MHz,QPSK l This parameter indicates the radio work
IDU 610/620, (IF1A/B) mode in "work mode, service capacity,
the value range is 5,16E1,28MHz,QP channel spacing, modulation mode"
as follows: SK (IF0A/B) format.
1,4E1,7MHz,QP 7,STM-1,28MHz, l The IF1A/B board supports radio work
SK 128QAM (IFX) modes 1 to 15. The IF0A/B board
2,4E1,3.5MHz, supports radio work modes 5, 16, 17, and
5,16E1,28MHz,QP 18. The IFX board supports radio work
16QAM SK (IF0) mode 7 only.
3,8E1,14MHz,Q
PSK l The IFH1 board of the IDU 605 1F/2F
does not support the setting of the Radio
4,8E1,7MHz, Work Mode.
16QAM
l The IFH2 board of the IDU 620 does not
5,16E1,28MHz, support the setting of the Radio Work
QPSK Mode.
6,16E1,14MHz, l Set this parameter according to the
16QAM network planning. The radio work
7,STM-1,28MH modes of the IF boards at both the radio
z,128QAM link must be the same.
8,E3,28MHz,QP
SK
9,E3,14MHz,
16QAM
10,22E1,14MHz
,32QAM
11,26E1,14MHz
,64QAM
12,32E1,14MHz
,128QAM
13,35E1,28MHz
,16QAM
14,44E1,28MHz
,32QAM
15,53E1,28MHz
,64QAM
16,5E1,7MHz,Q
PSK
17,10E1,14MHz
,QPSK
18,2E1,3.5MHz,
QPSK
l In the case of the
IDU 605 1A/1B/
2B, the value

range is as
follows:
5,16E1,28MHz,
QPSK
16,5E1,7MHz,Q
PSK
17,10E1,14MHz
,QPSK
18,2E1,3.5MHz,
QPSK
Radio Link ID 1 to 4094 1 l As the identifier of a radio link, this

parameter is used to avoid
misconnection of radio links between
sites.
l If this parameter is different from
Received Link ID, the NE reports the
MW_LIM alarm and inserts the AIS into
the downstream.
planning. Each radio link of an NE
should have a unique Link ID, and the
Link IDs at both the ends of a radio link
should be the same.
IF Port Loopbacka Non-Loopback, Non-Loopback l IF port inloop indicates that loopback

Inloop, Outloop occurs in the IF signals to be transmitted
to the remote end.
l IF port outloop indicates that loopback
occurs in the IF signals to be received.
default value.

2M Wayside Enable Enabled, Disabled Disabled l In the case of the IFX board, this
Statusb parameter is valid only when Radio
Work Mode is set to 7,STM-1,28MHz,
128QAM.
l In the case of the IF1A/B board, this
parameter is valid only when Radio
Work Mode is set to 7,STM-1,28MHz,
128QAM, 8,E3,28MHz,QPSK, or
9,E3,14MHz,16QAM.
radio link transmits the wayside E1
service.
l The wayside E1 service is a 2.048 kbit/s
service that is transmitted by the
microwave frame overhead. The IDU
610/620 accesses the wayside E1 service
through the external clock interface on
the PXC board.
2M Wayside Input 1, 3 1 l This parameter is valid only when 2M

Boardb Wayside Enable Status is set to
Enabled.
l This parameter indicates the slot in
which the PXC board accesses the
wayside E1 service through the external
clock port.
XPIC Enablec Enabled, Disabled Enabled l This parameter indicates whether the
XPIC function is enabled.
l If the IF board does not use the XPIC
function, set this parameter to
Disabled. In this case, use the XPIC
cable to perform self-loop at the XPIC
port.

ATPC Enable Enabled, Disabled Disabled l This parameter indicates whether the
Statusd ATPC function is enabled. The ATPC
function ensures that the TX power of
the transmitter automatically traces the
changes of the RX level at the receive
end, within the ATPC controlled range.
l It is recommended that you set this
parameter to Disabled in areas where
fast fading severely affects the radio
transmission.
l To ensure that the TX power does not
change during the commissioning
process, set this parameter to Disabled.
After the commissioning is complete,
you can set this parameter to another
value.
ATPC Upper -20 dBm to -75 dBm -45 dBm l Set the central value of the ATPC upper
Threshold (dBm)d threshold and the ATPC lower threshold
so that the central value is equal to the
ATPC Lower -35 dBm to -90 dBm -70dBm required value of the receive power.
Threshold (dBm)d l Ensure that the difference between
values of the automatic ATPC upper
threshold and the automatic ATPC lower
threshold is not less than 5 dB.
ATPC Automatic Enabled, Disabled Enabled l This parameter sets whether to enable
Threshold Enable the ATPC. The ATPC function enables
Status the transmit power of a transmitter to
automatically trace the change of the
received signal level (RSL) at the receive
end within the ATPC control range.
l When the function is enabled, the
manually set ATPC upper and lower
thresholds are invalid. The equipment
automatically uses the preset ATP upper
and lower thresholds based on the
working mode of the IF board.
l When the function is disabled, the
thresholds are used.
l The IF0 board of the IDU 605 1A/1B/2B
does not support the ATPC Automatic
Threshold Enable Status.

NOTE
l a: The IFH2 and IFX boards do not support the loopback on the IF ports.
l b: The IFH2 and IF0A/B boards do not support wayside E1 services.
l c: The IFH2, IF0A/B, and IF1A/B boards do not support the XPIC function.
l d: The ATPC attributes need to be set to the same values at both ends of a radio link.
7.2.4 Setting the Parameters of ODU Ports

Prerequisite
The corresponding ODU must be added in the slot layout diagram.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Step 2 Click the Radio Frequency Attributes tab.
Step 3 Configure the TX frequency and T/R spacing.
Step 4 Click Apply.
Step 5 Click the Power Attributes tab.
Step 6 Configure the transmit power and receive power of the ODU.
Step 7 Click Apply.
Step 8 Click the Advanced Attributes tab.
Step 9 Set Configure Transmission Status.
Step 10 Click Apply.
----End

Parameters
Transmit Frequency - - l The parameter specifies the channel

(MHz) center frequency.
l This parameter cannot be set to a value
that is less than the minimum Transmit
frequency supported by the ODU + 50%
channel spacing or more than the
maximum Transmit frequency
supported by the ODU - 50% channel
spacing.
l The difference between the Transmit
frequencies of both the ends of a radio
link is a T/R spacing.
planning.
Maximum Transmit - - l This parameter cannot be set to a value

Power (dBm) that exceeds the rated power range
supported by the ODU.
l Set this parameter to limit the maximum
transmit power of the ODU within this
preset value. The maximum transmit
power adjusted by ATPC should not
exceed this value.
planning.
Transmit Power - - l This parameter cannot be set to a value

(dBm) that exceeds the nominal power range
l The Transmit power of the ODU should
be set to the same value at both the ends
of a radio link.
planning.

Receive Power - - l This parameter is used to set the

(dBm) expected receive power of the ODU and
is mainly used in the antenna alignment
stage. After this parameter is set, the NE
automatically enables the antenna
misalignment indicating function.
l When the antenna misalignment
indicating function is enabled, if the
actual receive power of the ODU
exceeds the range of receive power3
dB, the ODU LED of the IF board
connected to the ODU is on (yellow) for
300 ms and off for 300 ms repeatedly,
indicating that the antenna is not aligned.
l After the antenna alignment, after the
state that the antenna is aligned lasts for
30 minutes, the NE automatically
disables the antenna misalignment
indicating function.
planning.
T/R Spacing (MHz) 0-4294967.295 - l This parameter indicates the spacing

between the TX power and receive
power of the ODU. If Station Type of
the ODU is TX high, the TX power is
one T/R spacing higher than the receive
power. If Station Type of the ODU is
TX low, the TX power is one T/R
spacing lower than the receive power.
l If the ODU supports only one T/R
spacing, set this parameter to 0,
indicating that the T/R spacing
supported by the ODU is used.
l The T/R spacing of the ODU should be
set to the same value at both the ends of
a radio link.
Configure mute, unmute unmute l When this parameter is set to mute, the
Transmission Status transmitter of the ODU does not work
but the ODU can normally receive
microwave signals.
l When this parameter is set to unmute,
the ODU can normally receive and
transmit microwave signals.
default value.

7.3 Configuring Ethernet Ports

The Ethernet ports contain the internal Ethernet ports and external Ethernet ports. The external
Ethernet ports are the physical ports that are used to connect the Ethernet equipment. The internal
Ethernet ports (VCTRUNKs) are internal paths that implement Ethernet over SDH.
7.3.1 Configuring External Ethernet Ports
When an NE uses the external ports (that is, PORTs) of the Ethernet boards to access Ethernet
services, the attributes of the external ports need to be configured so that the external ports can
work with the data communication equipment on the client side to provide the normal access to
the Ethernet services.
7.3.2 Configuring the Internal Port of the Ethernet Board
When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK)
of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board
works with the Ethernet board on the opposite side to realize the transmission of the Ethernet
services in the network.
7.3.3 Modifying the Type Field of Jumbo Frames
By default, the type field of Jumbo frames processed by Ethernet boards is set to "0x8700".
7.3.4 Modifying the Type Field of QinQ Frames
By default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernet
switching boards is set to "0x8100".
7.3.5 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth
When the LCAS function is enabled on an NE, you can dynamically increase or decrease the
VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect
services.
7.3.1 Configuring External Ethernet Ports

Prerequisite
The Ethernet board must be included in the NE Panel.
Precautions
l The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
Ethernet ports FE1-FE4 of an EFT4 board correspond to PORT1-PORT4 respectively.
The EFT4 board does not support the setting of TAG attributes, network attributes, and
advanced attributes.
Ethernet ports FE1-FE4 of an EMS6 board correspond to PORT1-PORT4 respectively.
Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.

l The IDU 605 IF/2F supports the Ethernet board EMS4 (a logical board).
Ethernet ports FE1-FE3 of an EMS4 board (a logical board) correspond to PORT1-
PORT3 respectively. Port FE4/GE1 of an EMS4 board corresponds to PORT4.
Ethernet ports FE1-FE2 of an EM4T board correspond to PORT1-PORT2 respectively.
Ports GE1 and GE2 of an EM4T board corresponds to PORT3 and PORT4 respectively.
l The following procedures describe how to configure the external port of an EMS6 board.
The EFT4 board does not support the configuration of the TAG attributes, network
attributes, and advanced attributes.
l The Hybrid IF board (IFH2) provides the GE port for accessing Ethernet services and it
supports certain Ethernet service access functions. The procedure for configuring the
Ethernet port of the IFH2 board is similar to the procedure for configuring the external
Ethernet port. The IFH2 board, however, supports the configuration of only the basic
attributes and flow control function.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree. Select External Port.
NOTE
If you need to configure the attributes of the Ethernet port on the IFH2 board, select the IFH2 board in the
NE Explorer.
Step 2 Set the basic attributes of the port.

1. Click the Basic Attributes tab.
2. Set the basic attributes of the port.
3. Click Apply.
Step 3 Set the flow control mode of the port.

1. Click the Flow Control tab.
2. Set the flow control mode of the port.
3. Click Apply.
Step 4 Optional: Set the TAG attributes of the port.

1. Click the TAG Attributes tab.
2. Set the TAG attributes of the port.

3. Click Apply.
Step 5 Optional: Set the network attributes of the port.
1. Click the Network Attributes tab.
2. Set the network attributes of the port.
3. Click Apply.
Step 6 Optional: Set the advanced attributes of the port.
1. Click the Advanced Attributes tab.
2. Set the advanced attributes of the port.
3. Click Apply.
----End
Parameters
Enabled/Disabled Enabled, Disabled Disabled l In the case of the port that accesses
services, set this parameter to Enabled.
In the case of other ports, set this
parameter to Disabled.
l If this parameter is set to Enabled for the
port that does not access services, an
ETH_LOS alarm may be generated.

Working Mode 10M Full-Duplex, Auto-Negotiation l The Ethernet ports of different types
100M Full-Duplex, support different working modes.
Auto-Negotiation l When the equipment on the opposite side
(EFT4) works in the auto-negotiation mode, set
10M Half-Duplex, the working mode of the equipment on
10M Full-Duplex, the local side to Auto-Negotiation.
100M Half-Duplex, l When the equipment on the opposite side
100M Full-Duplex, works in the full-duplex mode, set the
1000M Full- working mode of the equipment on the
Duplex, Auto- local side to 10M Full-Duplex, 100M
Negotiation (EMS6) Full-Duplex, or 1000M Full-Duplex
Auto-Negotiation, depending on the port rate of the
10M Full-Duplex, equipment on the opposite side.
100M Full-Duplex, l When the equipment on the opposite side
1000M Full-Duplex works in the half-duplex mode, set the
(IFH2) working mode of the equipment on the
10M Half-Duplex, local side to 10M Half-Duplex, 100M
10M Full-Duplex, Half-Duplex, or Auto-Negotiation
100M Half-Duplex, depending on the port rate of the
Auto-Negotiation (a l The GE optical interface on the EMS6
logical board EMS4, board supports the 1000M full-duplex
PORT1-PORT3) mode only.
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M Full-
Duplex, Auto-
Negotiation (a
logical board EMS4,
PORT4)

Maximum Frame 1518-1535 (EFT4) 1522 The value of this parameter should be
Length 1518-9600 (EMS6) greater than the maximum length of a frame
among all the data frames to be transported.
1522/1632 (a logical
board EMS4) In the case of the EFT4 board, this parameter
is invalid for Jumbo frames. In the case of
the EMS6 board, this parameter has a
restriction on Jumbo frames.
If Jumbo frames are not considered and the
accessed services are ordinary Ethernet
frames that use VLAN tags or do not have
VLAN tags, it is recommended that you use
the default value. If the access services
include services that use double tags such as
QinQ services, it is recommended that you
set this parameter to 1526.
In the case of the IDU 605 1F/2F, set
Maximum Frame Length of all the ports
on the logical EMS4 board to the same
value.
MAC Loopback Non-Loopback, Non-Loopback l When this parameter is set to Inloop, the
Inloop Ethernet frame signals that are to be sent
to the remote end are looped back.
l In normal cases, use the default value.
PHY Loopback Non-Loopback, Non-Loopback l When this parameter is set to Inloop, the
Inloop Ethernet physical signals that are to be
sent to the remote end are looped back.

Non- Disabled, Enable Disabled l This parameter is used when Working

Autonegotiation Symmetric Flow Mode is not set to Auto-Negotiation.
Flow Control Mode Control, Send Only, l When this parameter is set to Enable
Receive Only (EFT4 Symmetric Flow Control, the port can
and EMS6) send PAUSE frames and process
Disabled, Enable received PAUSE frames.
Symmetric Flow l When this parameter is set to Send
Control (IFH2) Only, the port can send PAUSE frames
Disabled, Enable (a in the case of congestion but cannot
logical board process received PAUSE frames.
EMS4) l When this parameter is set to Receive
Only, the port can process received
PAUSE frames but cannot send PAUSE
frames in the case of congestion.
l When this parameter is set to Enable for
the logical EMS4 board, the port can
send PAUSE frames and process
received PAUSE frames.
l The non-autonegotiation flow control
mode of the equipment on the local side
must match the non-autonegotiation
flow control mode of the equipment on
the opposite side.

Autonegotiation Disabled, Enable Disabled l This parameter is used when Working

Flow Control Mode Symmetric/ Mode is set to Auto-Negotiation.
Dissymmetric Flow l When this parameter is set to Enable
Control, Enable Symmetric Flow Control, the port can
Symmetric Flow send and process PAUSE frames.
Control, Enable
Control (EFT4 and Dissymmetric Flow Control, the port
EMS6) can send PAUSE frames in the case of
congestion but cannot process received
Disabled, Enable PAUSE frames.
Symmetric Flow
Control (IFH2) l When this parameter is set to Enable
Symmetric/Dissymmetric Flow
Disabled, Enable Control, the port can perform as
Symmetric Flow follows:
Control (a logical
board EMS4) Sends and processes PAUSE frames.
Sends but does not process PAUSE
frames.
Processes but does not send PAUSE
frames.
l The autonegotiation flow control mode
of the equipment on the local side must
match the autonegotiation flow control
mode of the equipment on the opposite
side.
Entry Detection Enabled, Disabled Enabled l This parameter specifies whether to

check the incoming packets from the
port according to the TAG attributes.
l Set this parameter according to actual
situations.
TAG Access, Tag Aware, Tag Aware l When ports are configured with TAG
Hybrid flags, the ports process frames by using
the methods provided in Table 7-5.
l If all the accessed services are frames
with the VLAN tag (tagged frames), set
this parameter to Tag Aware.
that do not have the VLAN tag (untagged
frames), set this parameter to Access.
l When the accessed services contain
tagged frames and untagged frames, set
this parameter to Hybrid.

Default VLAN ID 1 to 4095 1 l This parameter is valid only when

TAG is set to Access or Hybrid.
l For using this parameter, see Table 7-5.
situations.
VLAN Priority 0 to 7 0 l This parameter is valid only when

l When the VLAN priority is required to
divide streams or to be used for other
purposes, set this parameter according to
actual situations. Generally, it is
recommended that you use the default
value.
Port Attributes UNI, C-Aware, S- UNI l When this parameter is set to UNI, the
Aware port processes data frames according to
the tag attributes.
l When this parameter is set to C-Aware
or S-Aware, the port does not process
data frames according to the tag
attributes but processes the data frames
according to the way of processing QinQ
services.
l In the case of QinQ services, set this
parameter to the default value because
the NE automatically sets network
attributes according to the operation type
that is set when the QinQ services are
created.
Enabling Broadcast Enabled, Disabled Disabled This parameter specifies whether to restrict
Packet Suppression the traffic of broadcast packets according to
the ratio of the broadcast packets to the total
packets. When a broadcast storm may occur
in the equipment on the opposite side, set
this parameter to Enabled.
Broadcast Packet 10% to 100% 30% The port discards the received broadcast
Suppression packets when the ratio of the received
Threshold broadcast packets to the total packets
exceeds the value of this parameter. The
value of this parameter should be greater
than the ratio of the broadcast packets to the
total packets when the broadcast storm does
not occur. Generally, set this parameter to
30% or a greater value.

Loop Detection Disabled, Enabled Disabled Sets whether to enable loop detection, which
is used to check whether a loop exists at the
port.
Loop Port Shutdown Disabled, Enabled Enabled Sets whether to enable the loop port
shutdown function. After the loop port
shutdown function is enabled, the port is
automatically shut down when a self-loop is
detected. It is recommended that this
parameter adopts the default value.
Table 7-5 Methods used by ports to process data frames

Direction Type of Data How to Process
Frame
Tag aware Access Hybrida
Ingress Tagged frame The port receives the The port discards the The port receives the
frame. frame. frame.
Untagged frame The port discards the The port adds the The port adds the
frame. VLAN tag to which VLAN tag to which
Default VLAN ID Default VLAN ID
and VLAN and VLAN
Priority Priority
correspond, to the correspond, to the
frame, and receives frame, and receives
the frame. the frame.
Egress Tagged frame The port transmits The port strips the l If the VLAN ID
the frame. VLAN tag from the in the frame is
frame and then Default VLAN
transmits the frame. 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.

NOTE
a: When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by the IDU 605
1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same as the packet that enters
the bridge.
7.3.2 Configuring the Internal Port of the Ethernet Board

Prerequisite
The Ethernet board must be included in the slot layout.
Precautions
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
l The EFT4 board supports VCTRUNKs 1-4, which are bound with PORTs 1-4 respectively.
The EFT4 board does not support the setting of TAG attributes and network attributes.
l The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be
transmitted depending on information of the created Ethernet services.
The following procedures describe how to configure the internal port of an EMS6 board. The
EFT4 board does not support the configuration of the TAG attributes and network attributes.
Procedure
Management > Ethernet Interface from the Function Tree. Choose Internal Port.
Step 2 Set the encapsulation and mapping protocol used by the port.
1. Click the Encapsulation/Mapping tab.
2. Set Mapping Protocol and the protocol parameters.
3. Click Apply.
Step 3 Set the VC paths to be bound with the port.

1. Click the Bound Path tab.
2. Click Configuration.
The system displays the Bound Path Configuration dialog box.
3. In Configurable Ports, select a VCTRUNK as the port to be configured.
4. In Available Bound Paths, set Level and Direction of the bound paths.

5. Select required items in Available Resources and Available Timeslots and click .
6. Optional: Repeat Step 3.5 and bind other VCTRUNKs.
7. Click OK. Then, click Yes in the dialog box that is displayed.
Step 4 Configure the LCAS function for the port.

1. Click the LCAS tab.
2. Set the Enabling LCAS parameter and other LCAS parameters.
3. Click Apply.

3. Click Apply.


3. Click Apply.
----End
Parameters
Mapping Protocol GFP, LAPS, HDLC GFP It is recommended that you use the default
value.
Scramble Unscrambled, Scrambling Mode l This parameter specifies the scrambling

Scrambling Mode [X43+1] polynomial used by the mapping
[X43+1], protocol.
Scrambling Mode l It is recommended that you use the
[X48+1] default value.
Set Inverse Value Yes, No Yes l This parameter is valid only when
for CRC Mapping Protocol is set to LAPS or
HDLC.
l When this parameter is set to Yes, the
FCS is the result after you perform a
negation operation for the CRC.
l When this parameter is set to No, the
FCS is the CRC.
Check Field Length FCS32, FCS16, No FCS32 l When this parameter is set to FCS32, a
32-bit FCS is used.
l When this parameter is set to FCS16, a
16-bit FCS is used.
l When the Ethernet board uses the GFP
mapping protocol, this parameter can be
set to FCS32, FCS16, or No.
l When the Ethernet board uses the HDLC
set to FCS32 or FCS16.
l When the Ethernet board uses the LAPS
default value.

FCS Calculated Bit Big endian, Little l Big endian l When this parameter is set to Big
Sequence endian (GFP) endian, the least significant byte of the
l Little endian FCS is placed first and the most
(LAPS or significant byte is placed last.
HDLC) l When this parameter is set to Little
endian, the most significant byte of the
FCS is placed first and the least
significant byte is placed last.
default value.
Extension Header No, Yes No l This parameter specifies whether the

Option GFP payload header contains the
extension header and eHEC.
default value.
Configurable Ports VCTRUNKs VCTRUNK 1 This parameter specifies the VCTRUNK

whose VC paths are to be configured.
Available Bound - - Adhere to the following principles to plan

Paths and set this parameter:
l The capacity of VCTRUNKs should be
determined by the actual bandwidth
required by services.
l Bind only the paths in a VC-4 for a
VCTRUNK if possible. If the paths in
several VC-4s need to be bound, the
VC-4s that have the same transmission
path take priority.
l Each VC-4 of an Ethernet board can
have only VC-3 paths or only VC-12
paths. Hence, when a VCTRUNK needs
to be bound with VC-3 paths, select
VC-3 paths first from the VC-4 certain
of whose VC-3 paths are already bound.
When a VCTRUNK needs to be bound
with VC-12 paths, select VC-12 paths
first from the VC-4 certain of whose
VC-12 paths are already bound.
l Give priority to the paths in the VC-4-1
if a VCTRUNK needs to be bound with
VC-3 paths because the VC-4-1s of the
EFT4 board and EMS6 board support
only VC-3 paths whereas the VC-4-2s
support both VC-12 paths and VC-3
paths.
l Generally, bidirectional paths are bound.

Enabling LCAS Enabled, Disabled Disabled l This parameter specifies whether the
LCAS function is enabled.
l The LCAS can dynamically adjust the
number of virtual containers for
mapping required services to meet the
bandwidth requirements of the
application. As a result, the bandwidth
utilization ratio is improved.
LCAS Mode Huawei Mode, Huawei Mode l This parameter specifies the sequence in
Standard Mode which the LCAS sink sends the MST
control packet and Rs-Ack control
packet.
l When this parameter is set to Huawei
Mode, the LCAS sink first sends the Rs-
Ack and then sends the MST.
l When this parameter is set to Standard
Mode, the LCAS sink first sends the
MST and then sends the Rs-Ack.
l If the equipment on the opposite side is
the third-party equipment and does not
support the Huawei mode, it is
to Standard Mode. Otherwise, set this
parameter to Huawei Mode.
Hold Off Time (ms) 0, any integer that 2000 l When a member link is faulty, the LCAS
ranges from 2000 to performs switching after a delay of time
10000 and has a step to prevent the situation where an NE
of 100 simultaneously performs a protection
switching such as SNCP and performs an
LCAS switching. This parameter
specifies the duration of the delay.
l If the paths of the VCTRUNK are
configured with protection, it is
to 2000 ms. Otherwise, set this
parameter to 0.
WTR Time(s) 0 to 720 300 l When the time after a member link is
restored to normal reaches the set value
of this parameter, the VCG uses the
restored member link.
default value.

TSD Enabled, Disabled Disabled l This parameter specifies whether the

TSD is used as a condition for
determining whether a member link is
faulty. In the case of the VC-12, the TSD
refers to the BIP_SD. In the case of the
VC-3, the TSD refers to the
B3_SD_VC3.
default value.

situations.

situations.

value.

the tag attributes.
services.
created.
Activation Status Activated, - Displays whether the VCTRUNK is

Inactivated activated.
NOTE
l The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must
be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the
transmission line.
l The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line
must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other
end of the transmission line.
l The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a
transmission line.

Frame
Tag Aware Access Hybrid
and VLAN and VLAN
Priority Priority


Frame
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.
7.3.3 Modifying the Type Field of Jumbo Frames

Prerequisite
Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.
Procedure
Management > Jumbo Frame from the Function Tree.
Step 2 Modify the type field of Jumbo frames.
Step 3 Click Apply.
----End

Parameters
Jumbo Frame 00 00 to FF FF 88 70 This parameter specifies the type

field of Jumbo frames. Set this
parameter according to the type
field of the accessed Jumbo frames.
7.3.4 Modifying the Type Field of QinQ Frames

Prerequisite
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Advanced Attributes
> QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Step 3 Click Apply.
----End
Parameters
QinQ Type Area 81 00, 98 A8, 91 00 81 00 This parameter specifies the type field of
(Hexadecimal) QinQ frames. Set this parameter according
to the type field of the accessed QinQ
frames.

7.3.5 Dynamically Increasing/Decreasing the VCTRUNK

Bandwidth
When the LCAS function is enabled on an NE, you can dynamically increase or decrease the
VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect
services.
Prerequisite
Procedure
Step 1 Select the Ethernet board from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree. Select
Internal Port.
Step 2 Click the Bound Path tab.
Step 3 Click Configuration.

Step 4 Optional: Dynamically increase the VCTRUNK bandwidth.

1. In Configurable Ports, select a VCTRUNK as the configurable port.
3. Select desired items in Available Resources and Available Timeslots and click .
4. Optional: Repeat Step 4.3 and bind other VC paths.
Step 5 Optional: Dynamically decrease the VCTRUNK bandwidth.

1. Do not select the Display in Combination check box.
2. Select the VC paths to be deleted in Selected Bound Paths and click .

3. Optional: Repeat Step 5.2 to delete other VC paths.
Step 6 Click OK.
----End
Parameters
For specific parameters, see 7.3.2 Configuring the Internal Port of the Ethernet Board.
7.4 Disabling an Ethernet Port

It is recommended that you disable an unused Ethernet port to suppress the reporting of the
alarms related to the port.
Prerequisite
l There must be no service at the Ethernet port to be disabled.
Context
CAUTION
Disabling an Ethernet port may interrupt services.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree.
Step 2 Click the External Port option button.
Step 3 Click the Basic Attributes tab. Double-click Enabled/Disabled of the port to be disabled and
select Disabled.
Step 4 Click Apply. In the Prompt dialog box, click OK. In the Operation Result dialog box, click
Close.
----End

7.5 Configuring a Service Load Indication

There are two service load indications, which are Non-Loaded and Load. If a path is configured
with services and carries real services, set Service Load Indication to Load. If a path is
configured with services but does not carry real services, set Service Load Indication to Non-
Loaded to suppress the reporting of certain alarms.
Prerequisite
Context
CAUTION
If you set the service load indication to Non-Loaded, the services may be interrupted or you
may fail to log in to certain NEs.
Procedure
Step 1 In the NE Panel, select a board, right-click, and choose Service Load Indication from the
shortcut menu.
Step 2 Double-click Service Load Indication of the corresponding path, and select Load or Non-
Loaded.
NOTE
If you select Non-Loaded, you need not click OK in the Confirm dialog box.
----End
Postrequisite
In the case of a path that is configured with services but does not carry real services, if you set
Service Load Indication to Non-Loaded, you need to change the value of Service Load
Indication to Load at both ends of the services after the path carries real services in the future.

8 Configuring Interfaces (RTN 900)
About This Chapter
This section describes how to set the interface attributes of the boards.
8.1 Configuring SDH Interfaces

This section describes how to set the attributes of SDH interfaces. The attributes of SDH
interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advanced
attributes.
8.2 Configuring PDH Interfaces
This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH
interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different
settings of the interface attributes. The attributes of a PDH interface include the general
attributes, layer 2 attributes, layer 3 attributes and advanced attributes.
8.3 Configuring Ethernet Interfaces
This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the
Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different
settings of the interface attributes. The attributes of the Ethernet interface include the general
attributes, Layer 3 attributes, advanced attributes and flow control.
8.4 Configuring Microwave Interfaces
This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU
information of the radio link, microwave interface attributes, and ODU interface parameters.
8.5 Configuring Serial Interfaces
This topic describes how to set the attributes of serial interfaces.
8.6 Configuring ML-PPP
This section describes how to configure Multilink PPP (MP) group. MP is a technology used to
bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports
PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP
links in the MP group to the same destination.
8.7 Configuring an Ethernet Virtual Interface
This section describes how to configure an Ethernet virtual interface. After you configure the
Ethernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulated

Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3
attributes.
8.8 Configuring an IMA Group
When the RTN equipment accesses IMA services, configure an ATM IMA group at the access
node.

8.1 Configuring SDH Interfaces

This section describes how to set the attributes of SDH interfaces. The attributes of SDH
interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advanced
attributes.
8.1.1 Setting the General Attributes of SDH Interfaces
The general attributes of an SDH interface define the physical-layer information, such as the
port mode, encapsulation type, and maximum data packet length.
8.1.2 Setting the Advanced Attributes of SDH Interfaces
The routine maintenance parameters can be set by setting the advanced attributes of SDH
interfaces.
8.1.3 Querying the Running Status of PPP
In the case of a network failure, you can query the running status of the PPP to analyze the cause
of the failure.
8.1.4 Resetting the PPP
In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends
of a link to re-negotiate.
8.1.1 Setting the General Attributes of SDH Interfaces

The general attributes of an SDH interface define the physical-layer information, such as the
port mode, encapsulation type, and maximum data packet length.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH
Step 2 Select the desired board.
Step 3 Set the parameters as required.

NOTE
Note the following issues during parameter settings:

l When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case,
channelized STM-N services can be accessed.
l When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATM
services can be accessed.
l If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, the
interface does not enable the PPP, and thus the equipment bears less load. If you select PPP, the interface
can access the MPLS or IP service.
l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet
contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets
in the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
8.1.2 Setting the Advanced Attributes of SDH Interfaces

The routine maintenance parameters can be set by setting the advanced attributes of SDH
interfaces.
Prerequisite
Procedure
Step 3 Select the board to be configured and set the parameters as required.
successful.
Step 5 Click Close.
----End

of the failure.
Prerequisite
The encapsulation type of the created SDH interface must be PPP.
Procedure
Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The
PPP Running Status dialog box is displayed.
Step 3 Click Close.
----End


Prerequisite
The encapsulation type of the created SDH interface must be PPP.
Context
CAUTION
Resetting the PPP will interrupt services.
Procedure
Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed,
indicating that the operation will interrupt the services.
Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful.
Step 4 Click Close.
----End
8.2 Configuring PDH Interfaces

This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH
interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different
settings of the interface attributes. The attributes of a PDH interface include the general
attributes, layer 2 attributes, layer 3 attributes and advanced attributes.
Context
The application scenario of a PDH interface depends on the setting of the interface attributes.
For details, refer to Table 8-1.
Table 8-1 Application scenario of PDH interfaces
Application Scenario Interface Type Required Interface

Attribute
Carrying the CES service E1 interface General attributes, Advanced

attributes


Attribute
Carrying the ATM service E1 interface General attributes, Layer 2

attributes
Carrying the tunnel E1 interface General attributes, Layer 3

attributes
NOTE
When the E1 interface is used to carry the CES service, set the general attributes and an advanced attribute, that
is, frame format, to ensure that the frame format is the same as the service encapsulation format. When the
emulation mode of a CES service is CESoPSN, it is recommended that you set the frame format at the interface
to CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame format at the interface
should be set to non-framing.
When the E1 interface is used to carry the ATM service, the Layer 2 attributes should be set. In addition, the
IMA group should be created. When setting the layer 2 attributes of the E1 interface, set Port Mode to Layer
2 in 8.2.1 Setting General Attributes of PDH Interfaces.
When the E1 interface is used to carry the tunnels, the Layer 3 attributes should be set. In addition, create the
ML-PPP group, and configure the interface as an ML-PPP member.
Follow the procedure shown in Figure 8-1 to configure a PDH interface.
Figure 8-1 Procedure for configuring a PDH interface

Carry CES service Carry ATM service Carry Tunnel
Start Start Start
Configure general Configure general Configure general

attributes attributes attributes
Configure advanced Configure advanced Configure layer 3

attributes attributes attributes
End End Configure advanced

attributes
End
Required
Optional
8.2.1 Setting General Attributes of PDH Interfaces

Before you create services, you need to set the general attributes of the corresponding PDH
interfaces. The general attributes of a PDH interface define the related information of the physical
layer.
8.2.2 Setting the Layer 3 Attributes of PDH Interfaces
Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface.
The layer 3 attributes of a PDH interface define the related attributes of the network layer.
8.2.3 Setting the Advanced Attributes of PDH Interfaces
The advanced attributes of PDH interfaces include frame format, line encoding format and
loopback mode.
of the failure.
8.2.1 Setting General Attributes of PDH Interfaces

Before you create services, you need to set the general attributes of the corresponding PDH
interfaces. The general attributes of a PDH interface define the related information of the physical
layer.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH
Step 2 Select the desired board.

NOTE

l When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case,
TDM services can be accessed.
l When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATM
services can be accessed.
l If the PDH interface is used for the inband DCN, the Port Mode cannot be set to Layer 1 or Layer
2.
l If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, the
interface does not enable the PPP protocol, and thus the equipment bears less load. If you select PPP,
the interface can carry the MPLS.
successful.

Step 5 Click Close.
----End
8.2.2 Setting the Layer 3 Attributes of PDH Interfaces

Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface.
The layer 3 attributes of a PDH interface define the related attributes of the network layer.
Prerequisite
l In General Attributes, Port Mode must be set to Layer 3.
l In General Attributes, Encapsulation Type must be set to PPP.
Procedure
Step 2 Click the Layer 3 Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
successful.
Step 5 Click Close.
----End
8.2.3 Setting the Advanced Attributes of PDH Interfaces

The advanced attributes of PDH interfaces include frame format, line encoding format and
loopback mode.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > PDH

NOTE
In the case of the OptiX RTN , Frame Mode of the packets at the PDH interface can be set to 30 or 31. In
hybrid networking, make sure that the frame modes of the local port and opposite port should be the same.
l 30: In the E1 frame format, timeslots 1-15 and 17-31 are used to transport service data.
l 31: In the E1 frame format, timeslots 1-31 are used to transport service data.
successful.
Step 5 Click Close.
----End

of the failure.
Prerequisite
l The encapsulation type of the created PDH interface must be PPP.
Procedure
Step 3 Click Close.
----End

Prerequisite
l The encapsulation type of the created PDH interface must be PPP.
Context
CAUTION

Procedure
Step 4 Click Close.
----End
8.3 Configuring Ethernet Interfaces

This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the
Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different
settings of the interface attributes. The attributes of the Ethernet interface include the general
attributes, Layer 3 attributes, advanced attributes and flow control.
Context
The application scenario of an Ethernet interface depends on the setting of the interface attributes.
For details, refer to Table 8-2.
Table 8-2 Application scenario of Ethernet interfaces

Attribute
Accessing the Ethernet Ethernet interface General attributes

service
Carrying the tunnel Ethernet interface General attributes, Layer 3

attributes
Follow the procedure shown in to configure an Ethernet interface.

8.3.1 Setting the General Attributes of Ethernet Interfaces
Before you configure the layer 3 attributes of an Ethernet interface, you need to configure the
general attributes of the corresponding Ethernet interface. The general attributes of an Ethernet
interface define the physical-layer information, such as the port mode, encapsulation type, and
maximum frame length.
8.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces
After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting
to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets
within the PSN network. The Layer 2 attributes of an Ethernet interface define the related
information of the data link layer.
8.3.3 Setting the Layer 3 Attributes of an Ethernet Interface

When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes
of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related
attributes of the network layer.
8.3.4 Setting the Advanced Attributes of Ethernet Interfaces
The routine maintenance parameters can be set through setting the advanced attributes of
Ethernet interfaces.
8.3.5 Configuring Flow Control
In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet
interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting
Ethernet packets. As a result, congestion is avoided.
8.3.1 Setting the General Attributes of Ethernet Interfaces

Before you configure the layer 3 attributes of an Ethernet interface, you need to configure the
general attributes of the corresponding Ethernet interface. The general attributes of an Ethernet
interface define the physical-layer information, such as the port mode, encapsulation type, and
maximum frame length.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
Step 2 Click the General Attributes tab.
NOTE
l When Port Mode is set to Layer 2, the Encapsulation Type support Null.
l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface
can be used by tunnel.
l When Port Mode is set to Layer Mix, the port can carry layer 2 services and layer 3 services. To create
a VLAN sub-interface, set the port mode to Layer Mix.
l Before changing Layer 3 to Layer Mix, make sure that route protocols, such as IGP-ISIS not enabled
on the port. Before changing Layer Mix to Layer 3, make sure that no VLAN tag is added to the port
and no Layer 2 service is configured on the port.
successful.
Step 5 Click Close.
----End
8.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces

After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting
to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets

within the PSN network. The Layer 2 attributes of an Ethernet interface define the related
information of the data link layer.
Prerequisite
Procedure
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 are valid when TAG is access or hybrid.
Step 4 Click Apply. Click OK, The Operation Result dialog box is displayed indicating that the
operation is successful.
Step 5 Click Close.
----End
8.3.3 Setting the Layer 3 Attributes of an Ethernet Interface

When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes
of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related
attributes of the network layer.
Prerequisite
Procedure

NOTE

l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved
bandwidth of the tunnels carried by port cannot exceed the physical bandwidth of the port.
l When modifying the IP address of the interface, make sure that the IP address of this interface and the
IP addresses of other interfaces configured with services are not in the same subnet.
successful.
Step 5 Click Close.
----End
8.3.4 Setting the Advanced Attributes of Ethernet Interfaces

Ethernet interfaces.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management >
successful.
Step 5 Click Close.
----End
8.3.5 Configuring Flow Control

In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet
interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting
Ethernet packets. As a result, congestion is avoided.
Prerequisite
Procedure
Step 2 Click the Flow Control tab.

successful.
Step 5 Click Close.
----End
8.4 Configuring Microwave Interfaces

This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU
information of the radio link, microwave interface attributes, and ODU interface parameters.
Context
The application scenario of an microwave interface depends on the setting of the interface
attributes. For details, refer to Table 8-3.
Table 8-3 Application scenario of microwave interfaces

Interface Attributes Signal to Carry Functioning Location
Layer 2 attributes Ethernet packets UNI side or NNI side
Layer 3 attributes Tunnels NNI side
NOTE
When the microwave interface is used to carry the QinQ Link, the configuration procedure is similar to the
configuration procedure when the microwave interface is used to carry the Ethernet service. In this case, however,
the encapsulation types are different. For details, see 8.4.3 Setting the Layer 2 Attributes of Microwave
Interfaces.
Follow the procedure shown in Figure 8-2 to configure an microwave interface.

Figure 8-2 Procedure for configuring an microwave interface
Carry Ethernet Packets Carry Tunnel
Start Start
Creating IF 1+1 Creating IF 1+1

Protection Protection
Configuring the IF/ Configuring the IF/

ODU Information of a ODU Information of a
Radio Link Radio Link
Setting the General Setting the General

Attributes Attributes
Setting the IF Setting the IF

Setting the Layer 2 Setting the Layer 3

Setting the Advanced Setting the Advanced

Setting the Parameters Setting the Parameters

of ODU Ports of ODU Ports
End End
Required
Optional
8.4.1 Setting the General Attributes of Microwave Interfaces

Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to
configure the general attributes of the corresponding microwave interface. The general attributes
of an microwave interface define the physical-layer information, such as the port mode,
encapsulation type, and maximum frame length.
8.4.2 Setting the IF Attributes of Microwave Interfaces
The IF information of the microwave interface specifies the relevant information of the IF board,
including the AM attribute and ATPC attribute.

8.4.3 Setting the Layer 2 Attributes of Microwave Interfaces

After the layer 2 attributes of an microwave interface are set, the interface can be used for
connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet
packets within the PSN network. The Layer 2 attributes of an microwave interface define the
related information of the data link layer.
The layer 3 attributes of an microwave interface define the related attributes of the network layer.
8.4.5 Setting the Advanced Attributes of Microwave Interfaces
microwave interfaces.
8.4.6 Setting the Parameters of ODU Ports(RTN900V1R1)
8.4.1 Setting the General Attributes of Microwave Interfaces

Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to
configure the general attributes of the corresponding microwave interface. The general attributes
of an microwave interface define the physical-layer information, such as the port mode,
encapsulation type, and maximum frame length.
Prerequisite
The IF board and the ODU that connects to the IF board must be added.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the General Attributes tab.
NOTE
l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ.
l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface
can be used by tunnel.
l In the case an NNI interface, MTU(byte), which indicates the maximum data packet length, must be
set to a value larger than 960. A DCN packet contains a maximum of 960 bytes. If MTU(byte) is
smaller than 960, the DCN packets in the receive direction may be lost.
successful.
Step 5 Click Close.
----End

8.4.2 Setting the IF Attributes of Microwave Interfaces

The IF information of the microwave interface specifies the relevant information of the IF board,
including the AM attribute and ATPC attribute.
Prerequisite
Procedure
Step 2 Click the IF Attributes tab.
NOTE
l When you set Assured Capacity Modulation and Full Capacity Modulation, note the following
points:
This parameter is valid only when Enable AM is set to Enable.
l When you set Manually Specified Modulation, note the following points:
This parameter is valid only when Enable AM is set to Disable.
l When you set ATPC Upper Threshold(dBm), note the following points:
Generally, ATPC Upper Threshold(dBm) should be 20 dB to 30 dB higher than ATPC Lower
Threshold(dBm), and must not be less than 15 dB. If the difference between the upper threshold and
the lower threshold is big, the number of ATPC adjustments is reduced and the system load is also
reduced. If the difference between the upper threshold and the lower threshold is small, the transmit
power is adjusted in a timely manner and the interference to adjacent systems is reduced.
l When you set ATPC Lower Threshold(dBm), note the following points:
Generally, set this parameter to a value of 10 dB or greater than the receiver sensitivity to prevent
sudden fast fading because sudden fast fading makes the RSL value lower than the receiver sensitivity.
successful.
Step 5 Click Close.
----End

After the layer 2 attributes of an microwave interface are set, the interface can be used for
connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet
packets within the PSN network. The Layer 2 attributes of an microwave interface define the
related information of the data link layer.
Prerequisite

Procedure
NOTE
When you set QinQ Type Domain, note the following points:
QinQ Type Domain can be set only when Encapsulation Type is QinQ.
successful.
Step 5 Click Close.
----End

The layer 3 attributes of an microwave interface define the related attributes of the network layer.
Prerequisite
Procedure
NOTE

bandwidth of the tunnel that is carried by a port cannot exceed the physical bandwidth of the port.
l Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are
interrupted.
successful.
Step 5 Click Close.
----End

8.4.5 Setting the Advanced Attributes of Microwave Interfaces

microwave interfaces.
Prerequisite
Procedure
NOTE
When you set Radio Link ID, note the following points:
l If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts
the AIS into the downstream.
l Set this parameter according to the planning. Each radio link of an NE should have a unique Link ID,
and the Link IDs at both the ends of a radio link should be the same.
l Before performing the loopback operation for the IF board, disable the AM function at the two ends
of a link.
successful.
Step 5 Click Close.
----End

Prerequisite
Procedure


NOTE
l When you set Transmission Frequency (MHz), note the following points:
l The parameter specifies the channel center frequency.
l This parameter cannot be set to a value that is less than the minimum TX frequency supported by
the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU
- 50% channel spacing.
l The difference between the TX frequencies of both the ends of a radio link is a T/R spacing.
l Set this parameter according to the planning.
l When you set T/R Spacing (MHz), note the following points:
l This parameter indicates the spacing between the TX power and receive power of the ODU. If
Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive
power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the
receive power.
l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing
l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
Step 4 Click Apply.
Step 6 Configure the TX power of the ODU.

NOTE
Note the following when setting the Transmit Power(dBm) parameters.

l This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU.
l The TX power of the ODU should be set to the same value at both the ends of a radio link.
Note the following when setting the TX High Threshold(dBm) and TX Low Threshold(dBm)
parameters.
l When the actual launched power of the ODU is higher than TX High Threshold(dBm), the system
records the time when the actual launched power is higher than TX High Threshold(dBm) and the
time when the actual launched power is higher than TX Low Threshold(dBm) as performance events.
l When the actual launched power of the ODU is within the range from TX Low Threshold(dBm) to
TX High Threshold(dBm), the system records the time when the actual launched power of the ODU
is higher than TX Low Threshold(dBm) as a performance event.
l When the actual launched power of the ODU is lower than TX Low Threshold(dBm), no record is
saved.
l The TX High Threshold(dBm) and TX Low Threshold(dBm) parameters are valid only when the
ATPC function is enabled.
Note the following when setting the RX High Threshold(dBm) and RX Low Threshold(dBm).
l When the actual received power of the ODU is lower than RX Low Threshold(dBm), the system
records the time when the actual received power is lower than RX High Threshold(dBm) and the time
when the actual received power is lower than RX Low Threshold(dBm) as performance events.
l When the actual received power of the ODU is within the range from RX Low Threshold(dBm) to
RX High Threshold(dBm), the system records the time when the actual received power of the ODU
is higher than RX Low Threshold(dBm) as a performance event.
l When the actual received power of the ODU is higher than RX Low Threshold(dBm), no record is
saved.
Step 7 Click Apply.

----End

Prerequisite
Procedure
Step 4 Click Apply.
Step 6 Configure the transmit power and receive power of the ODU.
Step 7 Click Apply.
----End

Parameters
Transmit Frequency - - l The parameter specifies the channel

that is less than the minimum Transmit
maximum Transmit frequency
supported by the ODU - 50% channel
spacing.
l The difference between the Transmit
planning.
Maximum Transmit - - l This parameter cannot be set to a value

Power (dBm) that exceeds the rated power range
l Set this parameter to limit the maximum
transmit power of the ODU within this
preset value. The maximum transmit
power adjusted by ATPC should not
exceed this value.
planning.
Transmit Power - - l This parameter cannot be set to a value

(dBm) that exceeds the nominal power range
l The Transmit power of the ODU should
be set to the same value at both the ends
of a radio link.
planning.

Receive Power - - l This parameter is used to set the

(dBm) expected receive power of the ODU and
is mainly used in the antenna alignment
stage. After this parameter is set, the NE
automatically enables the antenna
misalignment indicating function.
l When the antenna misalignment
indicating function is enabled, if the
actual receive power of the ODU
exceeds the range of receive power3
dB, the ODU LED of the IF board
connected to the ODU is on (yellow) for
300 ms and off for 300 ms repeatedly,
indicating that the antenna is not aligned.
l After the antenna alignment, after the
state that the antenna is aligned lasts for
30 minutes, the NE automatically
disables the antenna misalignment
indicating function.
planning.
T/R Spacing (MHz) 0-4294967.295 - l This parameter indicates the spacing

between the TX power and receive
power of the ODU. If Station Type of
the ODU is TX high, the TX power is
one T/R spacing higher than the receive
power. If Station Type of the ODU is
TX low, the TX power is one T/R
spacing lower than the receive power.
indicating that the T/R spacing
a radio link.
Configure mute, unmute unmute l When this parameter is set to mute, the
Transmission Status transmitter of the ODU does not work
but the ODU can normally receive
microwave signals.
default value.

8.5 Configuring Serial Interfaces

This topic describes how to set the attributes of serial interfaces.
8.5.1 Creating Serial Interfaces
You can create a serial interface at the VC12 level or 64 kbit/s timeslot level.
8.5.2 Setting the General Attributes of a Serial Interface
Before you set the layer 3 attributes of a serial interface, you need to set the general attributes
of the serial interface. The general attributes of a serial interface define the related information
of the physical layer.
8.5.3 Setting the Layer 3 Attributes of Serial Interfaces
In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data.
The layer 3 attributes of a serial interface define the related attributes of the network layer.
of the failure.
8.5.1 Creating Serial Interfaces

You can create a serial interface at the VC12 level or 64 kbit/s timeslot level.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial
Step 2 Click New in the General Attributes tab and the New Serial Interface dialog box is displayed.

NOTE
l In the case of the serial interface at the VC12 level, currently a serial interface can be bound to only
one timeslot.
l In the case of the serial interface at the 64 kbit/s level, when the E1 frame mode is 30, timeslots 0 and
16 are unavailable. When the E1 frame mode is 31, timeslot 0 is unavailable.
successful.
Step 5 Click Close.
----End

8.5.2 Setting the General Attributes of a Serial Interface

Before you set the layer 3 attributes of a serial interface, you need to set the general attributes
of the serial interface. The general attributes of a serial interface define the related information
of the physical layer.
Prerequisite
A serial interface must be created.
Procedure

NOTE
When you set Port Mode to Layer 2, Encapsulation Type is ATM. The serial interface supports IMA
binding.
When you set Port Mode to Layer 3, you can set Encapsulation Type to PPP or Null. When you set
Encapsulation Type to PPP, you can add the serial interface to an MP group. The serial interfaces that
are bound to the same MP group have the same E1 frame mode. When Encapsulation Type is Null, Port
Mode can be changed to Layer 2.
In the case an NNI interface,Max Data Packet Size (byte) must be larger than 960. A DCN packet contains
a maximum of 960 bytes. If Max Data Packet Size (byte) is smaller than 960, the DCN packets in the
receive direction may be lost.
Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was
successful.
Step 4 Click Close.
----End
8.5.3 Setting the Layer 3 Attributes of Serial Interfaces

In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data.
The layer 3 attributes of a serial interface define the related attributes of the network layer.
Prerequisite
In General Attributes, Encapsulation Type must be set to PPP.
Procedure
Step 2 Click the Layer 3 Attributes tab and set the parameters as required.

NOTE

bandwidth of the tunnels carried by port should be not more than the physical bandwidth of the port.
l Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are
interrupted.
l When changing Specify IP Address from Manually to Unnumbered IP, manually specify the invalid
IP address (255.255.255.255) and invalid IP mask (255.255.255.255) to release the IP address manually
specified.
successful.
Step 4 Click Close.
----End

of the failure.
Prerequisite
The encapsulation type of the created serial interface must be PPP.
Procedure
Step 3 Click Close.
----End

Prerequisite
The encapsulation type of the created serial interface must be PPP.

Context
CAUTION
Procedure
Step 4 Click Close.
----End
8.6 Configuring ML-PPP

This section describes how to configure Multilink PPP (MP) group. MP is a technology used to
bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports
PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP
links in the MP group to the same destination.
Context
Follow the procedure shown in Figure 8-3 to configure an MP group.

Figure 8-3 Procedure for configuring an MP group
Start
Enable the PPP at the

interface
Create MP
group
Configure members to an
MP group
End
Required
Optional
8.6.1 Overview of the ML-PPP

The Multilink PPP, also ML-PPP or MP, indicates that multiple point-to-point protocol (PPP)
links are bundled and used. In this document, the Multilink PPP is referred to as ML-PPP.
Before configuring the ML-PPP, you need to know the basic concepts, such as the packet format
of the ML-PPP.
8.6.3 ML-PPP Application
In the case of the ML-PPP, several ports that adopt the PPP encapsulation are bundled into one
logical port to increase the transmission bandwidth. The ML-PPP allows that packets be divided
into fragments, which are transported over several PPP links to the same destination. The ML-
PPP is applicable to the PPP-supported ports, such as the E1 interface.
8.6.4 Creating MP Groups
You can bind E1 interfaces on which PPP is enabled by creating an MP group, so that the bound
E1 interfaces are used as a logical port to carry tunnels.
8.6.5 Configuring Member Interfaces of MP Groups
To modify the bandwidth of the MP group, add or delete the member interfaces into or from the
MP group.

8.6.1 Overview of the ML-PPP

The Multilink PPP, also ML-PPP or MP, indicates that multiple point-to-point protocol (PPP)
links are bundled and used. In this document, the Multilink PPP is referred to as ML-PPP.
The ML-PPP function benefits the network in the following aspects:
l Bandwidth increased.
l Load shared and backed up.
l Delay shortened by fragments.
The ML-PPP complies with RFC1990 (PPP multilink protocol). The ML-PPP protocol focuses
on the transmission of fragments of data packets over multiple data links, reassembly and
sequence of these fragments.

Before configuring the ML-PPP, you need to know the basic concepts, such as the packet format
of the ML-PPP.
ML-PPP Packet Format

The ML-PPP packets have the following formats, shown as Figure 8-4:
l Long sequence number fragment format (LSNFF): The sequence number field has 24 bits.
This format is the default format.
l Short sequence number fragment format (SSNFF): The sequence number field has 12 bits.
The fragment format of transmitted packets can be different from that of received packets on
the condition of mutual negotiation. If the negotiation does not allow that the received packets
are of the LSNFF format, the MP packets of the SSNFF format should be transmitted.

Figure 8-4 ML-PPP packet format
Adress
0xFF
0xFF Control
0x03
PPP Header
Protocol
0x003d
0x003d
B E 0 0 0 0 0 0 sequence
number
ML-PPP Header

sequence number
fragment data
....
PPP FCS FCS
Long Sequence Number Fragment Format
Adress
0xFF
0xFF Control
0x03
PPP Header
Protocol
0x003d
0x003d
ML-PPP Header B E 0 0
sequence number
fragment data
....
FCS
PPP FCS
Short Sequence Number Fragment Format
8.6.3 ML-PPP Application

In the case of the ML-PPP, several ports that adopt the PPP encapsulation are bundled into one
logical port to increase the transmission bandwidth. The ML-PPP allows that packets be divided
into fragments, which are transported over several PPP links to the same destination. The ML-
PPP is applicable to the PPP-supported ports, such as the E1 interface.
As shown in Figure 8-5, the ML-PPP bundles several PPP links into one logical port.

Figure 8-5 ML-PPP application scenario

NE1 ML-PPP NE2
PPP link
PPP link
PPP link
8.6.4 Creating MP Groups

You can bind E1 interfaces on which PPP is enabled by creating an MP group, so that the bound
E1 interfaces are used as a logical port to carry tunnels.
Prerequisite
l E1 interfaces on which PPP is enabled must be created.
l The E1 Frame Format of the local MP group and the opposite MP group should be
consistent.
Context
NOTE
The MP group can be bound only with the E1 interfaces of the same board.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP
Group Management from the Function Tree.
Step 2 Click New in the General Attributes tab and the New MP Group dialogue box is displayed.
successful.
Step 5 Click Close.
----End
8.6.5 Configuring Member Interfaces of MP Groups

To modify the bandwidth of the MP group, add or delete the member interfaces into or from the
MP group.
Prerequisite
l An MP group must be configured.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP
Group Management from the Function Tree.
Step 2 Select an MP group and click Configuration. The Config Member Interface dialog box is
displayed.
Step 4 Click Apply. The Warning dialog box is displayed, indicating that the operation may interrupt
the services.
NOTE
Deleting the member interface of the MP group may damage the service.
The member interface in the same MP group must have the same frame mode. That is, the values of Frame
Mode are all 30 or 31. for the parameters of Frame Mode, to see E1 Frame Format.
Step 5 Click Yes. A dialog box is displayed, indicating that the operation is successful.
Step 6 Click Close.
----End
8.7 Configuring an Ethernet Virtual Interface

This section describes how to configure an Ethernet virtual interface. After you configure the
Ethernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulated
Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3
attributes.
8.7.1 Setting the General Attributes of Ethernet Virtual Interfaces
The general attributes of an Ethernet virtual interface define the related information of the ATM
adaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you need
to configure the general attributes of the Ethernet virtual interface.
8.7.2 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces
The Layer 3 attributes of an Ethernet virtual interface include the IP address and tunnel enabling
status. You can create a tunnel after setting the Layer 3 attributes.
8.7.1 Setting the General Attributes of Ethernet Virtual Interfaces

The general attributes of an Ethernet virtual interface define the related information of the ATM
adaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you need
to configure the general attributes of the Ethernet virtual interface.
Prerequisite
Procedure
Ethernet Virtual Interface from the Function Tree.

Step 2 Click Query. The Operation Result dialog box is displayed dialog box is displayed indicating
that the operation is successful.
Step 3 Click Close. The general attributes of an Ethernet virtual interface are displayed in the field.
Step 4 Specify the port name as required.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful. Click Close.
----End
8.7.2 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces

The Layer 3 attributes of an Ethernet virtual interface include the IP address and tunnel enabling
status. You can create a tunnel after setting the Layer 3 attributes.
Prerequisite
The general attributes of Ethernet virtual interface must be set.
Procedure
Ethernet Virtual Interface from the Function Tree.
Step 2 Click the Layer 3 Attributes tab, set the Specify IP to Manually and set the IP Address and
IP Mask for the port.
Step 3 Double-click the Enable Tunnel field, and select Enabled.
Step 4 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.
----End

node.
Context
Figure 8-6 shows the flow for configuring an IMA group.

Figure 8-6 IMA group configuration flow
Start
Configure bound
paths for an
ATM IMA group
Configure IMA
group attributes
Configure ATM
interface attributes
Query the states

Query the IMA Reset an IMA Modify an IMA Delete an IMA
of the link of an
group states group group group
IMA group
End
Required
Optional
8.8.1 Configuring Bound Channels in an ATM IMA Group

When the RTN equipment accesses IMA services, configure bound channels in an ATM IMA
group at the access node. One ATM IMA group corresponds to one ATM trunk port. Bind
channels with the ATM trunk port and then enable the IMA group. The ATM trunk port can be
bound with one or several E1 or Fractional E1 ports.
8.8.2 Configuring Attributes of an ATM IMA Group
After configuring the channels bound with the IMA group, enable the IMA protocol and
configure attributes of the IMA group to make the IMA group meet the service requirements.
8.8.3 Configuring ATM Interface Attributes
This section describes methods of configuring the ATM interface parameters.
8.8.4 Querying IMA Group States
In the case of routine maintenance and troubleshooting, the operator need query information on
states of an IMA group to check whether the IMA group is normal.
8.8.5 Querying IMA Link States
states of an IMA link to check whether the IMA link is normal.
8.8.6 Resetting an IMA Group
In the case of deployment and troubleshooting, the operator can reset an IMA group to re-enable
the IMA group protocol.

8.8.7 Modifying an IMA Group

When attributes of an IMA group displayed on the U2000 are not consistent with those in the
network, modify attributes of this IMA group. If any service is configured and activated at the
ATM Trunk port for an IMA group, modification of the IMA group may interrupt services.
8.8.8 Deleting an IMA Group
Delete the redundant or idle IMA groups to release the resources. If any service is configured
and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt
the services.

Prerequisite
When the MLPPP or CES services is configured or the DCN is enabled on the VCTRUNK, the
VCTRUNK resources are occupied and thus the IMA group cannot be created.
When an E1or Fractional E1 port is bound with an IMA group, Port Mode should be set to
Layer 2.
Context
NOTE
Only the E1 ports on the same processing board can be bound.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the Binding tab and click Configuration. The Bound Path dialog box is displayed.
Step 3 Configure boards and VCTRUNK ports in Available Boards and Configurable Ports
respectively.
Step 4 Select E1, Fractional E1 for Level.
Step 5 Select a port in Available Resources. Click to bind the port to the VCTRUNK. Click
to cancel binding of the port to the VCTRUNK.

CAUTION
The VCTRUNK that is first added into the IMA group should be deleted at last.
The ports that are bound to the same VCTRUNK must have the same E1 frame mode or VC12
frame mode.
When the member links of an IMA group are at the serial ports of the 64K level, there are the
following restrictions:
l One serial port should be bound with a minimum of three 64K timeslots.
l The number of bound 64K timeslots should be the same for different serial ports.
l In one E1, only one serial port can be used as a member link of an IMA group.
Step 6 Click OK. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End

Prerequisite
Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Interface Management > ATM
Step 2 Click the IMA Group Management tab, enable the IMA protocol, and configure attributes of
the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds.
Click Close.
NOTE
Take the following precautions when setting parameters.

l You can enable or disable the IMA Protocol Enable Status of the IMA group only after configuring the
bound path of the corresponding VCTRUNK of the IMA group.
l IMA Transmit Frame Length: The optional values are 32, 64, 128 and 256.
l When IMA Symmetry Mode be set to Symmetric Mode and Symmetric Operation, Minimum Number
of Active Transmitting Links should be consistent with Minimum Number of Active Receiving Links.
l Maximum Delay Between Links: This parameter indicates the maximum delay variance among different
links in one IMA group. The value ranges from 1 ms to 120 ms, with 1 ms spacing.
l If the IMA protocol is enabled, only Minimum Number of Active Transmitting Links, Minimum
Number of Active Receiving Links and Maximum Delay Between Links can be set.
l You can modify the IMA Protocol Version, IMA Transmit Frame Length and IMA Symmetry Mode
only after you disable the IMA Protocol Enable Status.
----End


Prerequisite
Procedure
IMA Management from the Function Tree. Click the ATM Interface Management tab.
Step 2 Optional: Click Query to query the current attributes of each interface.
Step 3 Set relevant attributes of the interfaces bound with the IMA group as required.
successful.
Step 5 Click Close.
----End

Prerequisite
l You must complete the configuration of an IMA group.
Procedure
Step 2 Click the IMA Group States tab and select the IMA group for query. Click Query. A dialog
box is displayed, indicating that the operation succeeds. Click Close.
----End

Prerequisite
l You must complete the configuration of an IMA link.
Procedure

Step 2 Click the IMA Link States tab and select the IMA link for query. Click Query. A dialog box
is displayed, indicating that the operation succeeds. Click Close.
----End

Prerequisite
l You must complete the creation of the IMA group.
Procedure
Step 2 Click the IMA Group Management tab and select the IMA group. Click Reset. A dialog box
----End

Prerequisite
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification
of the IMA group may interrupt services. Exercise caution for this.
Procedure
Step 2 Click the IMA Group Management tab and modify related attributes of the IMA group. Click
Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End


the services.
Prerequisite
l The IMA Protocol Enable Status of the IMA group must be Disabled.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting
the IMA group may interrupt the services. Exercise caution for this.
Procedure
IMA Management from the Function Tree.
Step 2 Click the Banding tab and select an IMA group. Click Delete. A dialog box is displayed,
indicating that the operation may interrupt the services. Click OK. A dialog box is displayed,
indicating that the operation is successful. Click Close.
----End

Operation Guide for RTN NE Management 9 Configuring Radio Links
9 Configuring Radio Links
About This Chapter
Before creating a radio link between two radio sites, you must configure the corresponding radio
link information.
9.1 Radio Link
A radio link is the channel that is used to transmit the information between stations. This chapter
describes basic concepts of the radio link.
9.2 Configuring the IF/ODU Information of a Radio Link
You can set the IF/ODU information that is frequently used by the radio link based on each radio
link.
9.3 Configuring the ATPC Function
To configure the ATPC function, set the ATPC attributes of the IF board.
9.4 Creating an XPIC Workgroup
When two IF boards that form an XPIC workgroup are installed on an IDU, you can create an
XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode,
transmission frequency, TX power, and ATPC attributes.
9.5 Configuring the Hybrid/AM Attribute
The Hybrid microwave supports the transmission of E1 services and Ethernet services and
supports the adaptive modulation (AM) function. Hence, the Hybrid microwave ensures the
reliable transmission of the E1 services and flexible transmission of the Ethernet services whose
bandwidth is large and changes dynamically.
9.6 Hop Management
The Hop management is based on per link and the equipment at the two ends of a link is managed
at the same time.

9 Configuring Radio Links Operation Guide for RTN NE Management
9.1 Radio Link

A radio link is the channel that is used to transmit the information between stations. This chapter
describes basic concepts of the radio link.
The radio frequency signal whose frequency ranges from 300 MHz to 300 GHz is usually called
to be the radio signal. The line that transmit the radio signal is the radio link.
NOTE
During the creation of a radio link, the link ID at local end must be consistent with that at the opposite end,
to ensure the communication.
Refer to Figure 9-1. The communication channel between two radio stations is the radio link.
The radio stations are classified by function as follows:
Figure 9-1 Classification of Radio Stations
Relay Terminal
Station Station
Add/Drop Pivotal
Station Station
Terminal Terminal
Station Station
l Terminal station: A station located at either end of the link or at the endpoint of a tributary
link.
l Relay station: A station located in the middle of the link without adding or dropping voice
channels.
l Pivotal station: A station located in the backbone link to communicate with other stations
in various directions.
l Add/drop station: A station located in the middle of the link to add/drop tributaries and
realize the communication in two directions of the backbone link.
9.2 Configuring the IF/ODU Information of a Radio Link

You can set the IF/ODU information that is frequently used by the radio link based on each radio
link.
Prerequisite
The IF board and the ODU that connects to the IF board or IF port must be added.

Precautions
l In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In
this case, you need configure only the IF/ODU information of the main equipment.
l In 1+1 FD protection mode, one protection group corresponds to one radio link. In this
case, you need configure the IF/ODU information of the main equipment and the ODU
information of the standby equipment.
l In the case of XPIC radio links, one XPIC workgroup corresponds to two radio links. The
IF/ODU information of the radio links should be configured in the XPIC workgroup.
l In the case of N+1 radio links, one N+1 protection group corresponds to N+1 radio links
and the IF/ODU information of the N+1 radio links should be set respectively.
NOTE
In the example in the preceding figure:

l 1+1HSB: indicates that the IF 1+1 HSB protection is configured for the NE.
l 3-IFX2: indicates the IF card that is being configured.
l 4-IFX2: S indicates the standby IF card of the 1+1 protection.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002 NEs, select the NE from the Object Tree in
the NE Explorer. Choose Configuration > Link Configuration from the Function Tree.
Step 2 In the case of RTN 900 V100R001 NEs, select the NE from the Object Tree in the NE Explorer.
Choose Configuration > Microwave Link Configuration from the Function Tree.
Step 3 Click IF/ODU Configuration.
Step 4 Click an IF board icon or ODU icon.

Then, the system displays the IF/ODU information of the radio link to which the IF board
belongs.
Step 5 Set the corresponding IF information of the radio link.
Step 6 Click Apply.
Step 7 Set the corresponding ODU information of the radio link.

Step 8 Click Apply.

NOTE
Click Apply after you set the IF information of the radio link and after you set the ODU information of the radio
link.
----End
Parameters
Work Mode l 1,4E1,7MHz,Q The default value l This parameter indicates the radio work
PSK varies with different mode in "work mode, service capacity,
l 2,4E1,3.5MHz, IF boards. channel spacing, modulation mode"
16QAM format.
l 3,8E1,14MHz, l The IFH1 board of the RTN 605 does not
QPSK support the setting of the Work Mode.
l 4,8E1,7MHz, l The IF1A/IF1B board supports radio
16QAM work modes 1-15 and the IF0A/IF0B
board supports radio work modes 5 and
l 5,16E1,28MHz, 16-18. The IFX board supports radio
QPSK work mode 7.
l 6,16E1,14MHz, l The IFH2 board of the RTN 620 does not
16QAM support the setting of the Work Mode.
l 7,STM-1,28MH l Set this parameter according to the
z,128QAM planning. The radio work modes of the
l 8,E3,28MHz,Q IF boards at both the radio link must be
PSK the same.
l 9,E3,14MHz,
16QAM
l 10,22E1,14MH
z,32QAM
l 11,26E1,14MH
z,64QAM
l 12,32E1,14MH
z,128QAM
l 13,35E1,28MH
z,16QAM
l 14,44E1,28MH
z,32QAM
l 15,53E1,28MH
z,64QAM
l 16,5E1,7MHz,
QPSK
l 17,10E1,14MH
z,QPSK
l 18,2E1,3.5MHz
,QPSK

Link ID 1-4094 1 l As the identifier of a radio link, this

parameter is used to avoid misconnection
of radio links between sites.
l If this parameter is different from
Received Link ID, the NE reports the
MW_LIM alarm and inserts the AIS into
the downstream.
planning. Each radio link of an NE
should have a unique Link ID, and the
Link IDs at both the ends of a radio link
should be the same.
ATPC Enable Status Enabled, Disabled Disabled l This parameter indicates whether the
ATPC function is enabled. The ATPC
function ensures that the TX power of the
transmitter automatically traces the
changes of the RX level at the receive
end, within the ATPC controlled range.
parameter to Disabled in areas where fast
fading severely affects the radio
transmission.
l To ensure that the TX power does not
change during the commissioning
process, set this parameter to Disabled.
After the commissioning is complete,
you can set this parameter to another
value.
ATPC Automatic Enabled, Disabled Enabled l The ATPC function enables the transmit
Threshold Enable power of a transmitter to automatically
Status trace the change of the received signal
level (RSL) at the receive end within the
ATPC control range.
automatically uses the preset ATPC
upper and lower thresholds based on the

TX Frequency 0-4294967.295 0.0 l The parameter specifies the channel

that is less than the minimum TX
maximum TX frequency supported by
the ODU - 50% channel spacing.
l The difference between the TX
planning.
Range of Frequency For example: 22017 - Sets the range of the transmit frequencies of
(MHz) to 23025 an ODU board.
TX Power (dBm) -10.0 to +35.0 -10.0 l This parameter cannot be set to a value
that exceeds the nominal power range
l The TX power of the ODU should be set
to the same value at both the ends of a
radio link.
planning.
T/R Spacing (MHz) 0-4294967.295 0.0 l This parameter indicates the spacing
between the TX frequency and receive
frequency of the ODU. If Station Type
of the ODU is TX high, the TX
frequency is one T/R spacing higher than
the receive power. If Station Type of the
ODU is TX low, the TX frequency is one
T/R spacing lower than the receive
power.
indicating that the T/R spacing supported
by the ODU is used.
a radio link.

TX Status mute, unmute unmute l When this parameter is set to mute, the
transmitter of the ODU does not work but
the ODU can normally receive
microwave signals.
default value.
TX Power (dBm) -10.0 to 35.0 - Sets the transmit power for a radio frequency
port.
TX High Threshold -10.0 to 35.0 - Sets the higher threshold of the transmitted
optical power.
TX Low Threshold -10.0 to 35.0 - Sets the lower threshold of the transmitted
optical power.
RX High Threshold -90.0 to -20.0 - Sets the higher threshold of the received
optical power.
RX Low Threshold -90.0 to -20.0 - Sets the lower threshold of the received
optical power.
Range of Power For example: 12 - Sets the range of the transmitted optical
(dBm) power of the ODU board.
Enable AM Enabled, Disabled Disabled Sets the enable statue of AM.
Channel Space 7M, 14M, 28M, 7M Sets the channel spacing of the
56M corresponding radio links.
Assured Capacity QPSK, 16QAM, QPSK This parameter specifies the lowest
Modulation 32QAM, 64QAM, modulation scheme that the AM function
128QAM, supports. Generally, the value of this
256QAM parameter is determined by the service
transmission bandwidth that the Hybrid
microwave must ensure and the availability
of the radio link that corresponds to this
modulation scheme.
This parameter is valid only when Enable
AM is set to Enabled.

Full Capacity QPSK, 16QAM, QPSK This parameter specifies the highest
Modulation 32QAM, 64QAM, modulation scheme that the AM function
128QAM, supports. Generally, the value of this
256QAM parameter is determined by the bandwidth of
the services that need to be transmitted over
the Hybrid microwave and the availability of
the radio link that corresponds to this
modulation scheme.
This parameter is valid only when Enable
AM is set to Enabled.
Manually Specified QPSK, 16QAM, QPSK This parameter specifies the modulation
Modulation 32QAM, 64QAM, scheme that the radio link uses for the
128QAM, transmission.
256QAM This parameter is valid only when Enable
AM is set to Disabled.
NOTE
The ATPC attributes at both the ends of a radio link should be set to the same.

Prerequisite
The related IF board must be added.
Precautions
l In the case of the IF boards that are configured with the 1+1 protection, set only the ATPC
attributes of the main IF board.
l The following procedure describes the configuration of ATPC parameters in the IF interface
configuration dialog box of the IF board. You can also set ATPC parameters in the following
configuration dialog boxes:
Create an XPIC working group
IF/ODU configuration
l In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be
modified.
l The transmit power of the two ODUs that are in an XPIC working group should be the
same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper
threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value
for the IF boards that are in an XPIC working group.

l In the case of the Hybrid microwave, the AM switching is controlled through detection of
the change in the ATPC information and returned microwave message.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002 NEs.
1. Select the IF board from the Object Tree in the NE Explorer. Choose Configuration > IF
2. Click the ATPC Attributes tab.
3. Set the ATPC attributes.
NOTE
The IF0 board of the RTN 605 does not support the ATPC Automatic Threshold Enable Status.
4. Click Apply.
Step 2 In the case of RTN 900 V1R1 NEs, see Configuring the IF Attributes of Microwave
Interfaces to take the details of configuration.
----End
Parameters
ATPC Enable Status Enabled, Disabled Disabled l This parameter specifies whether the
function enables the transmit power of a
transmitter to automatically trace the
change of the received signal level
(RSL) at the receive end within the
ATPC control range.
l In the case of areas where fast fading is
severe, it is recommended that you set

ATPC Upper -20 to -75 -45 l When the ATPC function is enabled, if
Threshold (dBm) the RSL at the receive end is higher than
the preset ATPC upper threshold at the
receive end, the receiver notifies the
transmitter to decrease the transmit
power according to the preset ATPC
adjustment step at the transmit end until
the RSL is lower than the ATPC upper
threshold.
l Generally, ATPC Upper Threshold
(dBm) should be 20 dB to 30 dB higher
than ATPC Lower Threshold (dBm),
and must not be less than 15 dB. If the
difference between the upper threshold
and the lower threshold is big, the
number of ATPC adjustments is reduced
and the system load is also reduced. If
the difference between the upper
threshold and the lower threshold is
small, the transmit power is adjusted in
a timely manner and the interference to
adjacent systems is reduced.
ATPC Lower -35 to -90 -70 l When the ATPC function is enabled, if
Threshold (dBm) the RSL at the receive end is lower than
the preset ATPC lower threshold, the
receiver notifies the transmitter to
increase the transmit power according to
the preset ATPC adjustment step at the
transmit end until the RSL is higher than
the ATPC lower threshold.
l Generally, set this parameter to a value
of 10 dB or greater than the receiver
sensitivity to prevent sudden fast fading
because sudden fast fading makes the
RSL value lower than the receiver
sensitivity.

ATPC control range.
l The IF0 board of the RTN 605 does not
support the ATPC Automatic
NOTE
l Set ATPC parameters consistent at the two sides of a hop of microwave link.
l During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not
changed. After the commissioning, re-set the ATPC attributes.
l It is recommended that you disable the ATPC function for areas where fast fading is severe.
l To prevent that the RSL is lower than the receiver sensitivity caused by sudden fast fading, set the ATPC
lower threshold 10 dB or more higher than the receiver sensitivity.
l Generally, the ATPC upper threshold should be 20 dB to 30 dB higher than the ATPC lower threshold, and
must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big,
the number of ATPC adjustments can be reduced and the system load can also be reduced. If the difference
between the upper threshold and the lower threshold is small, the transmit power can be adjusted in a timely
manner and the interference to adjacent systems can be reduced.
l It is recommended that you set the ATPC adjustment step to 5 dB.
l In the case of hybrid radio links, the automatic ATPC threshold is recommended. In the case of SDH/PDH
radio links, the automatic ATPC threshold is recommended or you can make adjustment according to
multipath fading situation.

Prerequisite
The IF boards and the ODUs to which the IF boards are connected must be created.
The XPIC Enabled parameter must be set to Enabled for the IF boards.

Context
l Relation with the 1+1 Protection Configuration: The two IF boards in an XPIC working
group cannot be configured into one 1+1 protection group, but the two IF boards in different
XPIC working groups can be configured into one 1+1 protection group. Therefore, the four
IF boards in two XPIC working groups can form two 1+1 protection groups.
l Relation with the N+1 Protection: Each member of an XPIC working group can work as
the working channel or the protection channel of the N+1 protection.
l Relation with the ATPC Feature: The transmit power of the two ODUs that are in an XPIC
working group should be the same if possible. Hence, each of the ATPC parameters (ATPC
enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment)
should be set to the same value for the IFX boards that are in an XPIC working group.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
Step 2 Click the XPIC tab.
Step 3 Click New.
Step 4 In the dialog displayed box, Set the parameters for the XPIC workgroup.
For RTN 600 NEs:
NOTE
l When CCDP is applied to the STM-1 microwave links, the IFX/IFX2 boards must be installed and the
XPIC function must be enabled.
l An XPIC working group must be configured to ensure that the XPIC working group is configured with
the same working mode, transmission frequency, transmit power, and ATPC attributes.
l When the used ODUs support two T/R spacings, ensure that the two ODUs of an XPIC working group
adopt the same T/R spacing.

Step 5 Click OK.
----End
Postrequisite
Generally, you do not need to configure the IF/ODU information after you configure an XPIC
workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU
Configuration tab page if the used ODU supports two T/R spacings.
9.5 Configuring the Hybrid/AM Attribute

The Hybrid microwave supports the transmission of E1 services and Ethernet services and
supports the adaptive modulation (AM) function. Hence, the Hybrid microwave ensures the
reliable transmission of the E1 services and flexible transmission of the Ethernet services whose
bandwidth is large and changes dynamically.
Prerequisite
Procedure
Step 1 Select the target Hybrid IF board in the NE Explorer. Then, choose Configuration > Hybrid/
AM Configuration from the Function Tree.
Step 2 Click Query.
Step 3 Set the parameters related to the Hybrid/AM function.
Step 4 Optional: In the case of a card that supports the function of enabling E1 priority, click the
Advanced Attributes tab to set the minimum number of E1 services in different modulation
modes and check the bandwidth of data services.
Step 5 Click Apply.
----End
9.6 Hop Management

at the same time.
9.6.1 Introduction to the Hop Management

Based on Hop management, the system can simultaneously display the information of the two
ends of a link. Thus, you can view and set the information of a hop in an easy manner. The Hop
management supports the functions such as the setting and query of the intermediate frequency
(IF) and radio frequency (RF) information, and the configuration of services and protection.
9.6.2 Starting HOP Management
Based on HOP management, the system can simultaneously display the information of the two
ends of a link. By selecting an IF card, you can switch to the radio link in the corresponding

direction and search out the peer NE quickly. The HOP management integrates all functions in
one GUI, in which a user can perform all maintenance operations.
9.6.1 Introduction to the Hop Management

Based on Hop management, the system can simultaneously display the information of the two
ends of a link. Thus, you can view and set the information of a hop in an easy manner. The Hop
management supports the functions such as the setting and query of the intermediate frequency
(IF) and radio frequency (RF) information, and the configuration of services and protection.
The Hop management function is used to view and set the information based on a pair of
equipment, one of which transmits signals and the other receives signals.
In the case of the radio equipment, the configuration parameters are complicated. You need to
ensure the consistency of parameters between the equipment at the two ends of a radio link. By
using the Hop management function, you can perform operations on the equipment at the two
ends of a link at the same time. This facilitates the parameter configuration. In Figure 9-2, a
radio link represents a hop.
Figure 9-2 Radio link
at the same time. This ensures the consistency of configuration data between NEs at the two
ends.
9.6.2 Starting HOP Management

Based on HOP management, the system can simultaneously display the information of the two
ends of a link. By selecting an IF card, you can switch to the radio link in the corresponding
direction and search out the peer NE quickly. The HOP management integrates all functions in
one GUI, in which a user can perform all maintenance operations.
Prerequisite
The radio link must be created.
Procedure
1. In the NE Explorer, select an NE and choose Configuration > Link Configuration from
the Function Tree.
2. Click the IF/ODU Configuration tab.

3. Select the IF board, right-click, and choose HOP Management from the shortcut menu.
4. In the HOP Management window, choose Configuration > Link Configuration from
the Function Tree. Then, click the IF/ODU Configuration tab.
Step 2 In the case of RTN 900 V1R1 NEs
1. Double click the NE on the main topology, select the IF board in the NE panel, right-click,
and choose HOP Management from the shortcut menu.
2. In the NE Explorer, select an NE and choose Configuration > Microwave Link
Step 3 In the IF/ODU Configuration tab, set the related parameters.
CAUTION
Modifying the value of Transmit Frequency interrupts the link. Exercise caution when you
perform this operation.
Step 4 Click Apply.
----End

Operation Guide for RTN NE Management 10 Configuring Board 1+1 Protection
10 Configuring Board 1+1 Protection
About This Chapter
BPS is a protection mode based on the board. BPS requires two boards: active and standby.
When a link is down or a hardware failure is detected on the active board at any port, services
are switched from the active board to the protection board. In this way, services are protected.
10.1 Querying Board 1+1 Protection Group

After a redundant board is created, the equipment automatically configures a board 1+1
protection group. You can view the configuration information of the protection group.
10.2 Verifying the Board 1+1 Protection Switching
By using the U2000, you can perform or clear protection switching for a board. During
deployment and commissioning, you can perform switching to test whether the board protection
switching works properly. In fault maintenance, you can perform this operation to locate faults.

10 Configuring Board 1+1 Protection Operation Guide for RTN NE Management
10.1 Querying Board 1+1 Protection Group

After a redundant board is created, the equipment automatically configures a board 1+1
protection group. You can view the configuration information of the protection group.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Board 1+1 Protection from the
Function Tree.
Step 2 Click Query to query the configuration of the board 1+1 protection group.
----End
10.2 Verifying the Board 1+1 Protection Switching

By using the U2000, you can perform or clear protection switching for a board. During
deployment and commissioning, you can perform switching to test whether the board protection
Prerequisite
l The 1+1 board protection group must be available.
l The protection board works properly.
Context
CAUTION
If the protection board is abnormal, services may be interrupted when you perform switching.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the
Function Tree.
Step 2 Click Query to view the active board and the current working board.
Step 3 Select a 1+1 protection group and click Working/Protection Switching. The Confirm dialog
box is displayed.
Step 4 Click OK. The Operation Result dialog box is displayed.
Step 5 Click Close.

Operation Guide for RTN NE Management 10 Configuring Board 1+1 Protection
Step 6 Click Query to refresh the switching status of the 1+1 protection group.
NOTE
In the case of SCC protection pair, you can query standby status of the SCC board.
----End

Operation Guide for RTN NE Management 11 Configuring the IF 1+1 Protection
11 Configuring the IF 1+1 Protection
About This Chapter
The IF 1+1 protection includes the 1+1 HSB protection, 1+1 FD protection, and 1+1 SD
protection.
11.1 1+1 HSB

1+1 HSB is a configuration mode of 1+1 protection. The equipment provides a 1+1 hot standby
configuration for the IF board and ODU at the two ends of each hop of a radio link to realize
the protection by using the 1+1 HSB.
11.2 1+1 FD
1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the system
uses two channels that have a frequency spacing between them, to transmit and receive the same
service signal. The opposite end selects signals from the two received signals. With the 1+1 FD
protection, the impact of the fading on signal transmission is reduced.
11.3 1+1 SD
1+1 SD is a configuration mode of 1+1 protection. In the 1+1 SD protection mode, the system
uses two antennas that have a space distance between them, to receive the same RF signal. The
equipment selects signals from the two received signals. With the 1+1 SD protection, the impact
of the fading on signal transmission is reduced.
11.4 Creating IF 1+1 Protection
If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding
IF 1+1 protection group.
11.5 Modifying the Parameters of IF 1+1 Protection
The working mode and other parameters of the protection group can be modified.

11 Configuring the IF 1+1 Protection Operation Guide for RTN NE Management
11.1 1+1 HSB

1+1 HSB is a configuration mode of 1+1 protection. The equipment provides a 1+1 hot standby
configuration for the IF board and ODU at the two ends of each hop of a radio link to realize
the protection by using the 1+1 HSB.
11.1.1 Feature Description

This topic describes the 1+1 HSB protection through its application.
11.1.2 Availability
The 1+1 HSB feature requires the support of the applicable equipment and boards.
11.1.3 Relation with Other Features
The 1+1 HSB protection is related to the microwave work mode, 1+1 FD protection, 1+1 SD
protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave.
11.1.4 Realization Principle
The realization principle of the 1+1 HSB for the Hybrid microwave is different from the
realization principle of the 1+1 HSB for the SDH/PDH microwave.
11.1.5 Planning Guide
In the case of the radio links whose transmission performance is slightly affected by multipath
fading, it is recommended that you adopt the 1+1 HSB protection configuration.

This topic describes the 1+1 HSB protection through its application.
Figure 11-1 shows application of the 1+1 HSB protection.
Figure 11-1 1+1 HSB protection

Main channel Main channel
MODEM Transmitter Transmitter MODEM
Service Service
Standby channel Standby channel
In the case of the 1+1 HSB protection configuration, the main channel of the transmit end
transmits the RF signal to the opposite end. the main channel and standby channel of receive
end received the same RF signal respectively. When the main channel if faulty, the service unit
of receive end receives the signal from the standby channel. In this manner, the protection
switching is realized.
11.1.2 Availability
The 1+1 HSB feature requires the support of the applicable equipment and boards.

Table 11-1 Availability of the 1+1 HSB feature
Applicable Board Applicable Equipment
- RTN 605
IF0A/IF0B
IF1A/IF1B
RTN 620
IFX
IFH2
Table 11-2 Availability of the 1+1 HSB feature
IFE2
IF1
RTN 910/950
IFU2
IFX2

The 1+1 HSB protection is related to the microwave work mode, 1+1 FD protection, 1+1 SD
l The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 HSB protection.
l The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD,
or 1+1 SD. The configuration mode in one direction can be different from that in another
direction.
l The two IF boards in an XPIC working group cannot be configured into one 1+1 HSB
protection group, but the two IF boards in different XPIC working groups can be configured
into one 1+1 HSB protection group. Therefore, the four IF boards in two XPIC working
groups can form two 1+1 HSB protection groups.
l The IF boards in a 1+1 HSB protection group cannot be configured to provide the N+1
protection.
l The radio link with the 1+1 HSB configuration can work only as the service sink of an
SNCP service pair, and cannot work as the working source or the protection source.
l The Hybrid microwave supports the 1+1 HSB protection.

The realization principle of the 1+1 HSB for the Hybrid microwave is different from the
realization principle of the 1+1 HSB for the SDH/PDH microwave.

11.1.4.1 SDH/PDH Microwave

This topic considers the configuration with one 1+1 HSB protection group as an example to
describe the principle of the 1+1 HSB protection switching for the SDH/PDH microwave.
11.1.4.2 Hybrid Microwave
describe the principle of the 1+1 HSB protection switching for the Hybrid microwave.

describe the principle of the 1+1 HSB protection switching for the SDH/PDH microwave.
Before the Switching
Figure 11-2 1+1 HSB realization principle (before the switching, in the transmit direction)
Main Main Cross-connect Service
ODU IF board board board
Hybrid
Antenna
coupler
Standby Standby
ODU IF board
In the transmit direction:

1. The service board sends the received service signal to the cross-connect board.
2. The cross-connect board transmits the service signal to both the main IF board and the
standby IF board.
3. The main IF board and the standby IF board send the processed analog IF signal to the main
ODU and the standby ODU respectively.
4. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal
to the antenna. The standby ODU mutes (that is, the standby ODU does not send the RF
signal).
Figure 11-3 1+1 HSB realization principle (before the switching, in the receive direction)
Hybrid
Antenna
coupler
Standby Standby
ODU IF board

In the receive direction:
1. The hybrid coupler splits the RF signal received from the antenna to two signals and sends
them to both the main ODU and the standby ODU.
2. The main ODU and the standby ODU send the processed analog IF signal to the main IF
board and the standby IF board respectively.
3. The main IF board and the standby IF board send the service signal to the cross-connect
board.
4. The cross-connect board selects the service signal from the main IF board and sends the
signal to the service board.
5. The service board sends the service signal to the equipment at the opposite end.
After the Switching
Figure 11-4 1+1 HSB realization principle (after the switching, in the receive direction)
Hybrid
Antenna
coupler
Standby Standby
ODU IF board
Figure 11-5 1+1 HSB realization principle (after the switching, in the transmit direction)
Hybrid
Antenna
coupler
Standby Standby
ODU IF board
After a 1+1 HSB switching:
l In the receive direction, the cross-connect board selects the service signal from the standby
IF board.

l In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler,
which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU
does not send the RF signal).
NOTE
In the case of the RTN 605, the multiplexing sub-unit that is embedded in the IF unit replaces the cross-connect
unit of the IDU 620 to realize the dual fed and selective receiving function.

describe the principle of the 1+1 HSB protection switching for the Hybrid microwave.
Figure 11-6 1+1 HSB realization principle (before the switching, in the transmit direction)
Hybrid
coupler
Antenna
Standby Standby EMS6

ODU IF board board
1. The service board multiplexes the received E1 service signal into the VC-4 and then sends
the VC-4 to the cross-connect board.
2. The cross-connect board transmits the E1 service signal tin the VC-4 o the main IF board
and the standby IF board.
3. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet
service port of the standby IF board is in LinkDown state. The Ethernet board EMS6
transmits the Ethernet service to the Ethernet service port of the main IF board through the
LAG function.
4. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service
signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes
the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave
frame.
5. The IF processing units of the main IF board and the standby IF board receive the Hybrid
microwave frame that is multiplexed by their corresponding IF board and modulate the
Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the

main IF board and the standby IF board send the analog IF signal to the main ODU and the
standby ODU respectively.
to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the
RF signal).
Figure 11-7 1+1 HSB realization principle (before the switching, in the receive direction)
Main
ODU Main Cross-connect Service
IF board board board
Hybrid
coupler
Antenna
Standby
Standby EMS6
IF board
ODU board

1. The hybrid coupler splits the RF signal received from the antenna into two signals and
sends them to the main ODU and the standby ODU.
3. The main IF board and the standby IF board demodulate the Hybrid frame from the IF
signal.
4. The MUX units of the main IF board and the standby IF board receive the Hybrid frame
that is demultiplexed from their corresponding IF board and then separate the Hybrid frame
into the E1 service signal and Ethernet service signal.
5. The E1 service signal is transmitted to the cross-connect board after being multiplexed into
the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF
board.
6. The cross-connect board receives the E1 service signal from the main IF board and cross-
connects the service signal to the corresponding service board.
7. The EMS6 board receives the Ethernet service signal from the main IF board because the
Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service
port of the standby IF board is in LinkDown state.

After the Switching
Figure 11-8 1+1 HSB realization principle (after the switching, in the receive direction)
Main
ODU Main Cross-connect Service
Hybrid
coupler
Antenna
Standby
Standby EMS6
IF board
ODU board
Hybrid
coupler
Antenna

ODU IF board board
After a 1+1 HSB switching:

l In the receive direction:
The analog IF signal received at the standby IF board is separated into the E1 service signal
and Ethernet service signal by the MUX unit. The Ethernet service port of the main IF board
is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp
state. The cross-connect board and the EMS6 board receive the service signal from the
standby IF board.
l In the transmit direction:
The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service
port of the standby IF board is in LinkUp state. The IF processing units of the main IF board
and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the
MUX unit of their corresponding IF board into the analog IF signal. The main IF board and

the standby IF board send the analog IF signal to the main ODU and the standby ODU. The
standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to
the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF
signal).
NOTE
l The two built-in IF units of theRTN 605 realize the functions of two IF boards of the RTN 620.

In the case of the radio links whose transmission performance is slightly affected by multipath
fading, it is recommended that you adopt the 1+1 HSB protection configuration.
Procedure
Step 1 Plan the parameters relevant to the protection configuration.
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from
five minutes to twelve minutes. It is recommended that you set the value to ten minutes.
l It is recommended that you enable the reverse switching. If reverse switching is enabled, and
both the main IF board and the standby IF board at the sink end report a service alarm, a
reverse switching occurs at the source end.
l In the case of the RTN 620, although the 1+1 HSB protection has no restriction on the slot
of the IF board, it is recommended that you install a pair of main and standby IF boards in
slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot
6 is the main board).
----End
11.2 1+1 FD
1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the system
uses two channels that have a frequency spacing between them, to transmit and receive the same
service signal. The opposite end selects signals from the two received signals. With the 1+1 FD
protection, the impact of the fading on signal transmission is reduced.

This topic describes the 1+1 FD protection through its application.
11.2.2 Availability
The 1+1 FD feature requires the support of the applicable equipment and boards.
The 1+1 FD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD
The realization principle of the 1+1 FD for the Hybrid microwave is different from the realization
principle of the 1+1 FD for the SDH/PDH microwave.
If there are sufficient spectrum resources, it is recommended that you adopt the 1+1 FD
protection configuration.


Figure 11-10 shows the application of the 1+1 FD protection.
Figure 11-10 1+1 FD protection

F1 F1
Service Service
F2 F2
In the case of the 1+1 FD protection configuration, the main channel and the standby channel
of the receive end receive RF signals of different frequencies which from the transmit end
respectively. When the quality of the microwave signal received by the main antenna is degraded,
bit errors occur in the service on the main channel. The service unit then receives the service
signal from the standby channel to protect the service.
In addition, the 1+1 FD protection supports the 1+1 HSB protection switching.
11.2.2 Availability
The 1+1 FD feature requires the support of the applicable equipment and boards.
Table 11-3 Availability of the 1+1 FD feature
- RTN 605
IF0A/IF0B
IF1A/IF1B
RTN 620
IFX
IFH2
Table 11-4 Availability of the 1+1 FD feature
IFE2 RTN 910/950

IF1
IFU2
IFX2

The 1+1 FD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD
l The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 FD protection.
direction.
l The two IF boards in an XPIC working group cannot be configured into one 1+1 FD
into one 1+1 FD protection group. Therefore, the four IF boards in two XPIC working
groups can form two 1+1 FD protection groups.
l The IF boards in a 1+1 FD protection group cannot be configured to provide the N+1
protection.
l The radio link with the 1+1 FD configuration can work only as the service sink of an SNCP
service pair, and cannot work as the working source or the protection source.
l The Hybrid microwave supports the 1+1 FD protection.

The realization principle of the 1+1 FD for the Hybrid microwave is different from the realization
principle of the 1+1 FD for the SDH/PDH microwave.

This topic considers the configuration with one 1+1 FD protection group as an example to
describe the principle of the 1+1 FD protection switching for the SDH/PDH microwave.
This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an
example to describe the principle of the 1+1 FD protection switching for the Hybrid microwave.

This topic considers the configuration with one 1+1 FD protection group as an example to
describe the principle of the 1+1 FD protection switching for the SDH/PDH microwave.

Figure 11-11 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna
f1
f2
Antenna Standby Standby

ODU IF board

standby IF board.
4. The main ODU and the standby ODU transmit RF signals at different frequencies and send
the signals to their respective antennas.
Figure 11-12 1+1 FD realization principle (before the switching, in the receive direction)
Antenna
Standby Standby
Antenna
ODU IF board

1. The antennas receive RF signals and send the signals to their respective ODUs.
3. The multiplex unit of the IF board sends the processed baseband signal to itself and to the
multiplex unit of its paired board.
4. The main IF board and the standby IF board select their own baseband signal.

After the Switching
Figure 11-13 1+1 FD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby Standby
Antenna
ODU IF board
After a 1+1 FD HSB switching:
l In the receive direction, the IF boards select their own service signal. The cross-connect
board selects the signal from the standby IF board.
l In the transmit direction, no processing is required.
Figure 11-14 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby Standby
Antenna
ODU IF board
After a 1+1 FD HSM switching:
l In the receive direction, the IF boards select the baseband signal from their own paired IF
board.
NOTE
l The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620.
l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of
the cross-connect board of the IDU 620.


This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an
example to describe the principle of the 1+1 FD protection switching for the Hybrid microwave.
Figure 11-15 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna ODU IF board board
board
f1
f2

Antenna IF board board
ODU
2. The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board
LAG function.
frame.
microwave frame that is multiplexed by the main IF board and modulate the Hybrid
microwave frame into the analog IF signal. Then, the IF processing units of the main IF
board and the standby IF board send the analog IF signal to the main ODU and the standby
ODU respectively.
6. The main ODU transmits the RF signal at frequency f1 to the main antenna. The standby
ODU transmits the RF signal at frequency f2 to the standby antenna.

Figure 11-16 1+1 FD realization principle (before the switching, in the receive direction)
Main
Antenna ODU Main Cross-connect Service
f1 IF board board board
f2 Standby
Antenna Standby EMS6
IF board
ODU board

1. The antennas receive RF signals at different frequencies and send the signals to their
corresponding main ODU and standby ODU.
3. The main IF board and the standby IF board demodulate the Hybrid frame from the IF
signal. The Hybrid microwave frame of the standby IF board is transmitted to the main IF
board through the protection bus.
board.

After the Switching
board
f1
f2

ODU
Figure 11-18 1+1 FD HSB realization principle (after the switching, in the receive direction)
Main
f2 Standby
IF board
ODU board
After a 1+1 FD HSB switching:

The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service
port of the standby IF board is in LinkUp state. The IF processing units of the main IF board
and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the
MUX unit of their corresponding IF board into the analog IF signal. The main IF board and
the standby IF board send the analog IF signal to the main ODU and the standby ODU
respectively. The main ODU transmits the RF signal at frequency f1 to the main antenna
and the standby ODU transmits the RF signal at frequency f2 to the standby antenna.


The Hybrid microwave frame demultiplexed by the main IF board is transmitted to the
standby IF board through the protection bus. The MUX unit of the main IF board receives
the Hybrid microwave frame that is multiplexed by the main IF board and then separates
the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The
MUX unit of the standby IF board receives the Hybrid microwave frame that is multiplexed
by the standby board and then separates the Hybrid microwave frame into the E1 service
signal and Ethernet service signal. The Ethernet service port of the main IF board is in
LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state.
The cross-connect board and the EMS6 board receive the service signal from the standby
IF board.
Figure 11-19 1+1 FD HSM realization principle (after the switching, in the receive direction)
Main
f2 Standby
IF board
ODU board
After a 1+1 FD HSM switching:

The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is
transmitted from the standby IF board through the protection bus and then separates the
Hybrid microwave frame into the E1 service signal and Ethernet service signal. The cross-
connect board and the EMS6 board receive the service signal from the main IF board.
NOTE
l The two built-in IF units of the IDU 605 2F realize the functions of two IF boards of the IDU 620.

If there are sufficient spectrum resources, it is recommended that you adopt the 1+1 FD
protection configuration.
Procedure

l The spacing between the emission frequency of the main ODU and that of the standby ODU
should be greater than 56 MHz to prevent adjacent-channel interference.
l In the case of the RTN 620, a pair of main and standby IF boards must be installed in slots
5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is
the main board). In the case of the RTN 605 , the active/standby relation of the IF unit is
fixed. Hence, planning is not required.
----End
11.3 1+1 SD
1+1 SD is a configuration mode of 1+1 protection. In the 1+1 SD protection mode, the system
uses two antennas that have a space distance between them, to receive the same RF signal. The
equipment selects signals from the two received signals. With the 1+1 SD protection, the impact
of the fading on signal transmission is reduced.

11.3.2 Availability
The 1+1 SD feature requires the support of the applicable equipment and boards.
The 1+1 SD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD
The realization principle of the 1+1 SD for the Hybrid microwave is different from the realization
principle of the 1+1 SD for the SDH/PDH microwave.
In the case of the radio links whose transmission performance is significantly affected by
multipath fading, it is recommended that you adopt the 1+1 SD protection configuration.

Figure 11-20 shows the application of the 1+1 SD protection.
Figure 11-20 1+1 SD protection

T2
T2
T1 T1
Service Service
T2
T1

In the case of the 1+1 SD protection configuration, the two antennas at the receive end receive
the same RF signals from the transmit end. When the quality of the microwave signal that is
received by the main antenna is degraded, bit errors may occur in the service on the main channel.
Due to the space diversity, the signal that is received by the standby antenna may not be degraded.
In this case, the service unit receives the service from the standby receive channel to protect the
service.
In addition, the 1+1 SD protection supports the 1+1 HSB protection switching.
11.3.2 Availability
The 1+1 SD feature requires the support of the applicable equipment and boards.
Table 11-5 Availability of the 1+1 SD feature
- RTN 605
IF0A/IF0B
IF1A/IF1B
RTN 620
IFX
IFH2
Table 11-6 Availability of the 1+1 SD feature
IFE2
IF1
RTN 910/950
IFU2
IFX2

The 1+1 SD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD
l The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 SD protection.
direction.
l The two IF boards in an XPIC working group cannot be configured into one 1+1 SD

into one 1+1 SD protection group. Therefore, the four IF boards in two XPIC working
groups can form two 1+1 SD protection groups.
l The IF boards in a 1+1 SD protection group cannot be configured to provide the N+1
protection.
l The radio link with the 1+1 SD configuration can work only as the service sink of an SNCP
l The Hybrid microwave supports the 1+1 SD protection switching.

The realization principle of the 1+1 SD for the Hybrid microwave is different from the realization
principle of the 1+1 SD for the SDH/PDH microwave.

This topic considers the configuration with one 1+1 SD protection group as an example to
describe the principle of the 1+1 SD protection switching for the SDH/PDH microwave.
describe the principle of the 1+1 SD protection switching for the Hybrid microwave.

describe the principle of the 1+1 SD protection switching for the SDH/PDH microwave.
Figure 11-21 1+1 SD realization principle (before the switching, in the transmit direction)
Antenna

ODU IF board
standby IF board.

to the antenna. The standby ODU mutes (that is, the standby ODU does not send the RF
signal).
Figure 11-22 1+1 SD realization principle (before the switching, in the receive direction)
Antenna
Standby Standby
Antenna
ODU IF board

1. The antennas receive RF signals and send the signals to their respective ODUs.
3. The multiplex unit of the IF board sends the processed baseband signal to itself and to the
multiplex unit of its paired board.
4. The main IF board and the standby IF board select their own baseband signal.
After the Switching
Figure 11-23 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby Standby
Antenna
ODU IF board

Figure 11-24 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna

ODU IF board
After a 1+1 SD HSB switching:
l In the receive direction, the IF boards select their own service signal. The cross-connect
board selects the signal from the standby IF board.
l In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler,
which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU
does not send the RF signal).
Figure 11-25 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby Standby
Antenna
ODU IF board
After a 1+1 SD HSM switching:
l In the receive direction, the IF boards select the baseband signal from their own paired IF
board.
NOTE
l The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620.
l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of
the cross-connect board of the IDU 620.

describe the principle of the 1+1 SD protection switching for the Hybrid microwave.

Figure 11-26 1+1 SD realization principle (before the switching, in the transmit direction)
board

ODU

2. The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board
LAG function.
frame.
microwave frame that is multiplexed by the main IF board and modulate the Hybrid
microwave frame into the analog IF signal. Then, the IF processing units of the main IF
board and the standby IF board send the analog IF signal to the main ODU and the standby
ODU respectively.
6. The main ODU transmits the RF signal to the antenna. The standby ODU is muted (that is,
the standby ODU does not transmit the RF signal).

Figure 11-27 1+1 SD realization principle (before the switching, in the receive direction)
Main
Standby
IF board
ODU board

1. The antennas receive RF signals and transmit the signals to their corresponding main ODU
and standby ODU.
3. The main IF board and the standby IF board demodulate the IF signal into the Hybrid
microwave frame. The Hybrid microwave frame of the standby IF board is transmitted to
the main IF board through the protection bus.
board.

After the Switching
Figure 11-28 1+1 SD HSB realization principle (after the switching, in the receive direction)
Main
Standby
IF board
ODU board
Figure 11-29 1+1 SD HSB realization principle (after the switching, in the transmit direction)
board

ODU
After a 1+1 SD HSB switching:

The MUX unit of the standby IF board receives the Hybrid microwave frame that is
multiplexed by the standby IF board. The cross-connect board receives the E1 service signal
that is demultiplexed from the Hybrid microwave frame received at the standby IF board
and cross-connects the E1 service signal to the corresponding service board. The EMS6
board receives the Ethernet service signal from the standby IF board because the Ethernet
service port of the main IF board is in LinkDown state and the Ethernet service port of the
standby IF board is in LinkUp state.


The Ethernet service port of the main IF board is in LinkDown state. The Ethernet service
port of the standby IF board is in LinkUp state. The main IF board and the standby IF board
receive the Hybrid microwave frame that is multiplexed by the standby IF board and then
transmit the modulated Hybrid microwave frame to the main ODU and the standby ODU
respectively. The standby ODU transmits the RF signal to the antenna. The main ODU is
muted (that is, the main ODU does not transmit the RF signal).
Figure 11-30 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna ODU IF board board board

Antenna board
ODU IF board
After a 1+1 SD HSM switching:

The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is
transmitted from the standby IF board through the protection bus and then separates the
Hybrid microwave frame into the E1 service signal and Ethernet service signal. The cross-
connect board and the EMS6 board receive the service signal from the main IF board.
NOTE
The two built-in IF units of the IDU 605 2F realize the functions of two IF boards of the IDU 620.

In the case of the radio links whose transmission performance is significantly affected by
multipath fading, it is recommended that you adopt the 1+1 SD protection configuration.
Procedure
l There should be a height difference between the two antennas so that the dependence of the
diversity-received microwave signals on the space is minimized.

l It is recommended that you enable the reverse switching. If reverse switching is enabled, and
both the main IF board and the standby IF board at the sink end report a service alarm, a
reverse switching occurs at the source end.
l In the case of the IDU 620, a pair of main and standby IF boards must be installed in slots 5
and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is
the main board). In the case of the IDU 605 2B/2F, the active/standby relation of the IF unit
is fixed. Hence, planning is not required.
----End
11.4 Creating IF 1+1 Protection

If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding
IF 1+1 protection group.
Prerequisite
The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included
in the NE Panel.
When a 1+0 service is converted into a 1+1 service by configuring the 1+1 protection, the original
services are not interrupted.
Precautions
The 18,2E1,3.5MHz,QPSK work mode does not support IF 1+1 protection.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002/V100R001C02 NEs.
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
2. Click New. Set the parameters of the IF 1+1 protection group in the displaying dialog box.
3. Click OK.
Step 2 In the case of RTN 900 V100R001C00 and RTN 900 V100R001C01 NEs.
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Microwave Link Configuration from the Function Tree.

2. Click the IF 1+1 Protection tab.

3. Click New. Set the parameters of the IF 1+1 protection group in the displaying dialog box.
4. Click OK.
----End
Postrequisite
l In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the
IF/ODU information of the active microwave link later. The standby microwave link
automatically copies the related information of the active microwave link except the
transmission status of the ODU.
l In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the
active microwave link and the information of the standby ODU later. The standby
microwave link automatically copies the IF information of the active microwave link.
NOTE
The default TX Status of an ODU is Unmute. Hence, you do not need to configure the TX Status of the standby
ODU after you create an IF 1+1 protection group.
11.5 Modifying the Parameters of IF 1+1 Protection

The working mode and other parameters of the protection group can be modified.
Prerequisite
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > IF 1
+1 Protection from the Function Tree.
Step 2 Modify the parameters of the IF 1+1 protection.
Step 3 Click Apply.
----End

Parameters
Working Mode HSB, FD, SD HSB l In the 1+1 HSB protection mode, the
equipment provides a 1+1 hot standby
configuration for the IF board and ODU
at the two ends of each hop of a radio link
to realize the protection.
l In the 1+1 FD protection mode, the
system uses two channels that have a
frequency spacing between them, to
transmit and receive the same signal. The
opposite end selects signals from the two
received signals. With the 1+1 FD
protection, the impact of the fading on
signal transmission is reduced.
l In the 1+1 SD protection mode, the
system uses two antennas that have a
space distance between them, to receive
the same signal. The equipment selects
signals from the two received signals.
With the 1+1 SD protection, the impact
of the fading on signal transmission is
reduced.
l The 1+1 FD protection mode and 1+1
SD protection mode are compatible with
the 1+1 HSB switching function.
planning information.
Revertive Mode Revertive, Non- Revertive l When this parameter is set to

Revertive Revertive, the NE that is in the
switching state releases the switching
and enables the former working channel
to return to the normal state some time
after the former working channel is
restored to normal.
Revertive, the NE that is in the
switching state keeps the current state
unchanged unless another switching
occurs even though the former working
channel is restored to normal.
default value.

WTR Time(s) 300 to 720 - l This parameter is valid only when

Revertive Mode is set to Revertive.
l When the time after the former working
channel is restored to normal reaches the
set wait-to-restore (WTR) time, a
revertive switching occurs.
default value.
Enable Reverse Enable, Disable Enable l When both the main IF board and the
Switching standby IF board at the sink end report
service alarms, they send the alarms to
the source end by using the MWRDI
overhead in the microwave frame. When
this parameter at the source end is set to
Enable and the reverse switching
conditions are met, the IF 1+1 protection
switching occurs at the source end.
l This parameter is valid only when
Working Mode is set to HSB or SD.
default value.
NOTE
Each of the following parameters should be set to the same value at the two ends of a microwave link: Working
Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching.
Postrequisite
l In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the
IF/ODU information of the active microwave link later. The standby microwave link
automatically copies the related information of the active microwave link except the
transmission status of the ODU.
l In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the
active microwave link and the information of the standby ODU later. The standby
microwave link automatically copies the IF information of the active microwave link.
NOTE
The default TX Status of an ODU is Unmute. Hence, you do not need to configure the TX Status of the standby
ODU after you create an IF 1+1 protection group.

Operation Guide for RTN NE Management 12 Configuring Network Level Protection
12 Configuring Network Level Protection
About This Chapter
The network level protection includes the linear MSP, SNCP protection, MPLS tunnel protection
and LAG.
12.1 Basic Concept

To configure the network-level protection, you need to master basic concepts.
12.2 Configuring N+1 Protection
The N+1 protection refers to the protection configuration in which N working channels in a
microwave direction share one protection channel.
12.3 Configuring Linear Multiplex Section Protection
The linear MSP is applicable to point-to-point physical networks. The linear MSP provides
protection for the services between two nodes at the multiplex section level.
12.4 Configuring Two-Fiber Bidirectional Ring MSP
The two-fiber bidirectional ring MSP scheme is applicable to an SDH ring network of the STM-4
or higher level formed by fibers, and provides protection at the MS level for services between
the nodes of a ring network.
12.5 Configuring Sub-Network Connection Protection
The sub-network connection protection (SNCP) scheme protects the services that are across
subnets. The subnet can be a chain, a ring, or a more complicated network.
12.6 Configuring MPLS Tunnel Protection
When you configure an MPLS tunnel on a per-NE basis, you can configure 1+1 protection and
1:1 protection for the MPLS tunnel. You can also create an MPLS tunnel protection group,
perform switching, and delete an MPLS tunnel protection group.
12.7 Ethernet Ring Protection
Based on the traditional Ethernet mechanism, the Ethernet ring protection switching (ERPS)
uses the ETH-OAM function and the ring automatic protection switching (R-APS) protocol to
achieve fast protection switching on the Ethernet ring network.
12.8 Configuring Link Aggregation

12 Configuring Network Level Protection Operation Guide for RTN NE Management
Link aggregation allows multiple links that are attached to the same equipment to be aggregated
to form a link aggregation group (LAG) so that the bandwidths and availability of the links
increase. The aggregated links can be considered as a single logical link.

12.1 Basic Concept

To configure the network-level protection, you need to master basic concepts.
12.1.1 Multiplex Section

Multiplex section protection (MSP) is a protection mode, which is commonly used to configure
the protection.
12.1.2 MSP Protection Switching Priority
MSP protection switching can be triggered by automatic switching conditions and external
switching requests. Automatic switching is triggered by signal failure (SF) (for example, LOS,
LOF, MS_AIS and B2OVER raised on the equipment) and signal degrade (SD) (for example,
B2SD raised on the equipment). External switching is performed after you issue an external
switching command, and thus brings a status change of the multiplex section. External switching
requests include lockout, forced switching, manual switching, exercise switching, and clear of
switching.
12.1.3 SNCP Protection
Subnetwork connection protection (SNCP) is a type of 1+1 protection that uses single-ended
switching. SNCP is mainly used to protect services across subnets. This function is dual fed and
selective receiving.
12.1.4 N+1 Protection
The N+1 protection is to use a standby channel to protect the services on N (N3) active
channels. When the services on the active channel are normal, the standby channel can transmit
extra services. When the receive end detects that the signal is unavailable, the receive end checks
whether the standby channel is available and whether the standby channel is already occupied
by the services that are switched from another active channel for protection. The N+1 protection
has two protection schemes: single-NE N+1 protection and dual-NE N+1 protection. This section
describes the typical networking of the two schemes.
12.1.1 Multiplex Section

Multiplex section protection (MSP) is a protection mode, which is commonly used to configure
the protection.
The SDH transmission system can be divided into four layers on a functional basis. From the
bottom to the top layer, there is a physical layer, section layer, path layer and circuit layer. Among
the four layers, the section layer is used to ensure the integrity of the signals transmitted between
the nodes within an SDH network. The section layer consists of the regenerator section and the
multiplex section. The regenerator section refers to the section between the regenerator section
terminals (RSTs) of two pieces of equipment. The equipment contains two RSTs and the fibers
in between. The multiplex section refers to the section between the multiplex section terminals
(MSTs) of two pieces of equipment. The equipment contains two MSTs and the fibers in
between. See Figure 12-1.

Figure 12-1 Multiplex section schematic diagram

MST RST SPI ... ... SPI RST MST
... ...
RS
MS
SPI: SDH Physical Interface RST: Regenerator Section Termination
MST: Multiplex Section Termination
Table 12-1 describes the commonly used MSP types.
Table 12-1 MSP type

Type Capacity Description
1+1 linear MSP The maximum service This is a linear networking

capacity is STM-N. mode that provides 1+1
protection based on the MSP
protocol for the services. If a
fault occurs on the
transmission link, this
networking mode enables the
working service to switch to
the other link according to the
MSP protocol. In this way,
the service is protected.
1:N(N3) linear MSP The maximum service This is a linear networking

capacity is (1+N) STM-N. mode that provides 1:N
protection based on the MSP
protocol for the services. If a
fault occurs on the
transmission link, this
networking mode enables the
working service to switch to
the other link according to the
MSP protocol. In this way,
the service is protected.
NOTE
N is the number of working
links.
12.1.2 MSP Protection Switching Priority

MSP protection switching can be triggered by automatic switching conditions and external
switching requests. Automatic switching is triggered by signal failure (SF) (for example, LOS,
LOF, MS_AIS and B2OVER raised on the equipment) and signal degrade (SD) (for example,

B2SD raised on the equipment). External switching is performed after you issue an external
switching command, and thus brings a status change of the multiplex section. External switching
requests include lockout, forced switching, manual switching, exercise switching, and clear of
switching.
For MSP protection, the following switching requests can bring a status change of the multiplex
section. For their switching (or preemption) priorities, refer to Table 12-2.
NOTE
l The following table lists the switching priorities in a descending order, that is, LP_S (SF_P) has the highest
priority, and NR has the lowest. The requests of lockout, forced switching, manual switching and exercise
switching can be cleared as required.
l For LP_S (SF_P), the lockout of protection is available for only the span instead of the ring. LP_S and SF_P
have the same priority, and perform the same action on both the protocol and service. LP_S is triggered by
an external command, and SF_P is triggered by the protection channel failure in a four-fiber ring.
l The span switching has a higher priority than the ring switching.
l External commands are issued on the U2000. After a command is executed, the NE keeps this request until
the command is cleared or is preempted by another command of a higher priority. If there is a switching
request of a higher priority in the network, the external command cannot be executed, and thus the NE loses
this external command request.
Table 12-2 Preemptible relation of priorities of MSP protection switching
No. Switching Description Cause

Request
1 LP_S(SF_P) Span lockout SF in the protection

channel of a four-
fiber ring or the issue
of an external
command
2 FS_S Forced switching of a Issue of an external

span command
3 FS_R Forced switching of a Issue of an external

ring command
4 SF_S SF of a span SF in the working

channel of a span on
a four-fiber ring
5 SF_R SF of a ring SF in the working

channel of a four-
fiber or two-fiber
ring
6 SD_P SD of the protection SD in the protection

channel channel of a four-
fiber or two-fiber
ring
7 SD_S SD of a span SD in the working

channel of a span on
a four-fiber ring

No. Switching Description Cause

Request
8 SD_R SD of a ring SD in the working

channel of a four-
fiber or two-fiber
ring
9 MS_S Manual switching of Issue of an external

a span command
10 MS_R Manual switching of Issue of an external

a ring command
11 WTR Wait-to-restore Status request during

a switching
12 EXER_S Exercise switching Issue of an external

of a span command
13 EXER_R Exercise switching Issue of an external

of a ring command
14 RR_S Reverse request of a Reverse request

span during a switching
15 RR_R Reverse request of a Reverse request

ring during a switching
16 NR No request
12.1.3 SNCP Protection

Subnetwork connection protection (SNCP) is a type of 1+1 protection that uses single-ended
switching. SNCP is mainly used to protect services across subnets. This function is dual fed and
selective receiving.
Principle
The transmit end of an SNCP service transmits two service sources, and the receive end checks
the service sources and selectively receives one. In this way, the service is protected. Hence,
SNCP is dual fed and selective receiving, which is similar to path protection (PP). The difference
between the SNCP and PP is about the specific implementation. When a service is selectively
received at the receive end, in path protection, the tributary board verifies the selective receiving.
In SNCP protection, the cross-connect board verifies the selective receiving. Hence, SNCP can
protect services on the line, and PP protects only services on the local tributary board.
Subnet-Related Concepts
The definitions in ITU-T G.805 are as follows:
l Subnetwork: A topological component used to effect routing of specific characteristic
information.

l Subnetwork connection: A "transport entity" that transfers information across a

subnetwork, it is formed by the association of "ports" on the boundary of the subnetwork.
l Subnetwork connection protection: A protection type that is modeled by a sublayer that is
generated by expanding the "subnetwork" "connection point".
Implementation Principle
l Service pair:
SNCP service pair is the service structure that consists of a working source, a protection
source, and a service sink. See Figure 12-2.
Figure 12-2 SNCP service pair
Protection
Working source
source
Service sink
SNCP service is from line to line. A service that is added to and dropped from the local
tributary board is not an SNCP service and an SNCP service pair cannot be generated. See
Figure 12-3.
Figure 12-3 SNCP service
SCC
Issue data/
Collect data
Cross-connect
board
Line Line
board Intra-board Intra-board board
communication communication
l Check point: In an SNCP service pair, the status of the sink node is not checked. The two
source nodes are two check points of the protection group. The line board of the
corresponding service source checks the status of a check point (SF, SD, or Normal).
l Check point migration: An SNCP service pair usually has two check points. When a
network contains SNCP and MSP, several types of protection exists. Hence, some standby
check points are added accordingly. The line board enables the standby check point

according to a command, and disables the original check point to realize migration of the
check point.
l SNCP service number: It uniquely identifies a service pair. The SNCP service number
information is saved to the SCC, cross-connect board, and line board. The SNCP protection
switching on the line board and cross-connect board handles according to SNCP service
number. Hence, ensure that the SNCP service number on the line board is consistent with
that on the cross-connect board.
l Condition of generating an SNCP service pair: The node attributes must contain or imply
the SNCP attribute. The service must across rings.
l SCC board side: The SCC verifies the SNCP service, analyzes service route, and issues the
configuration data. The tasks contain setting check points, issuing SNCP service attribute
data, collecting the SNCP service status from the cross-connect board, and reporting the
SNCP service status.
l Cross-connect board side: The cross-connect board collects the SNCP service status from
the line board, realizes the switching process of the service source, and reports changes of
the SNCP service status to the SCC.
l Line board side: The line board mainly monitors the SNCP service and periodically reports
the service monitoring status to the cross-connect board. When the service status changes,
the line board notifies the cross-connect board of the change in real time.
l Service flow: The flow of the SNCP service is the flow that the system configures the
service. Because of the special dual fed and selective receiving attribute, SNCP attribute
must be specified during service configuration.
SNCP Protection Parameters

Table 12-3 lists the parameters of the SNCP protection.
Table 12-3 SNCP parameters
Protection Revertive Switching Default WTR Switching

Type Mode Time Time Condition
(Trigger by
Any One
Condition)
SNCP Revertive <= 50 ms 600s R_LOS

R_LOF
Non-revertive <= 50 ms -
AU_LOP
TU_LOP
MS_AIS
TU_AIS
HP_UNEQ
HP_TIM
B2_EXC
B3_EXC
B3_SD
BIP_EXC
BIP_SD

12.1.4 N+1 Protection

The N+1 protection is to use a standby channel to protect the services on N (N3) active
channels. When the services on the active channel are normal, the standby channel can transmit
extra services. When the receive end detects that the signal is unavailable, the receive end checks
whether the standby channel is available and whether the standby channel is already occupied
by the services that are switched from another active channel for protection. The N+1 protection
has two protection schemes: single-NE N+1 protection and dual-NE N+1 protection. This section
describes the typical networking of the two schemes.
l You need to configure the line board whose rate is at the STM-1 for the N+1 protection.
l Protection schemes:
Single-NE N+1 protection: When N is equal to or less than 2, an NE is required for the
protection.
Dual-NE N+1 protection: When N is equal to 3, two NEs are required for the protection.
NOTE
The single-NE N+1 protection and dual-NE N+1 protection shown are only schematic drawings. On the
real equipment, a dual-polarized antenna has only two interfaces. When multiple ODUs are connected,
every two ODUs are installed on a combiner and then the combiner is connected to the antenna.
Single-NE N+1 Protection

Take the 2+1 as an example.
Protect ODU ODU Protect

Dual-Polarized
IF IF Antennas IF IF
F SL1 IF ODU ODU F SL1 IF
A A
N PXC SD1 N PXC SD1
PXC SCC ODU ODU
PXC SCC
Add/Drop Add/Drop
Services Services
The realization principles of the 2+1 protection are as follows:
l A standby channel is used to protect the services on two active channels.

l Line board: The rate level of the line board should be STM-1.
l Others: The SCC board and the integrated power, cross-connect and clock (PXC) board
are required.
Dual-NE N+1 Protection


IF ODU ODU IF
F Secondary NE F IF
IF
A A
PXC SD1 ODU ODU N PXC SD1
N
PXC SCC Dual-Polarized PXC SCC
Antennas
Fiber Fiber
Interconnection Interconnection
SD1 IF ODU ODU SD1 IF

F F SD1 IF
SD1 IF
A Primary NE A
N
PXC SCC PXC SCC
Add/Drop Add/Drop
Services Services

l A standby channel is used to protect the services on three active channels. The IF 3+1
protection needs two OptiX RTN 620. One is the primary NE and the other is the secondary
NE. You need to configure the REG on the NEs and then create the IF 3+1 protection on
the primary NE.
l Line board: The line board should support the interaction between the primary and
secondary NEs. Slot 4 is the optimum location for the line board. Two more line boards
are needed for adding and dropping services.
are required.
12.2 Configuring N+1 Protection

The N+1 protection refers to the protection configuration in which N working channels in a
microwave direction share one protection channel.

This topic considers the application of the N+1 protection as an example to describe the N+1
protection.
12.2.2 Availability
The N+1 protection feature requires the support of the applicable equipment and boards.
The N+1 protection uses the N+1 protection protocol to realize the switching. The N+1
protection protocol is similar to the 1:N linear multiplex section protection protocol.
12.2.4 Configuration Guide
This topic describes the configuration flow and the corresponding configuration tasks of the N
+1 protection mode. An example is provided as additional information to help understand the
configuration.


This topic considers the application of the N+1 protection as an example to describe the N+1
protection.
The N+1 protection realizes protection for microwave channels. The IF board, ODU, and radio
link on the working channel can be protected through the N+1 protection. The N+1 protection
provides N working channels and one protection channel. When the working channel becomes
faulty, the normal services on the working channel can be switched to the protection channel for
transmission. When the working channel is restored to normal, the protection channel can
transmit the extra services.
Figure 12-4 shows the application of the N+1 protection.
Figure 12-4 N+1 protection

Site A Working Site B
channel 1
Normal Normal
service 1 service1
... Working ...
channel N
Normal Normal
service N service N
Protection
channel
Extra Extra
service service
Protection switching
Site A Working Site B

channel 1
Normal Normal
service 1 service1
... Working ...
channel N
Normal Normal
service N service N
Protection
channel
Extra Extra
service service
l You need to configure the line board whose rate is at the STM-1 for the N+1 protection.
l Protection schemes:
Single-NE N+1 protection: When N is equal to or less than 2, an NE is required for the
protection.
Dual-NE N+1 protection: When N is equal to 3, two NEs are required for the protection.
NOTE
The single-NE N+1 protection and dual-NE N+1 protection shown are only schematic drawings. On the
real equipment, a dual-polarized antenna has only two interfaces. When multiple ODUs are connected,
every two ODUs are installed on a combiner and then the combiner is connected to the antenna.

Single-NE N+1 Protection

Protect ODU ODU Protect

Dual-Polarized
IF IF Antennas IF IF
F SL1 IF ODU ODU F SL1 IF
A A
N PXC SD1 N PXC SD1
PXC SCC ODU ODU
PXC SCC
Add/Drop Add/Drop
Services Services
l A standby channel is used to protect the services on two active channels.

l Line board: The rate level of the line board should be STM-1.
are required.
Dual-NE N+1 Protection

IF ODU ODU IF
F Secondary NE F IF
IF
A A
N
PXC SCC Dual-Polarized PXC SCC
Antennas
Fiber Fiber
Interconnection Interconnection
SD1 IF ODU ODU SD1 IF

F F SD1 IF
SD1 IF
A Primary NE A
N
PXC SCC PXC SCC
Add/Drop Add/Drop
Services Services
l A standby channel is used to protect the services on three active channels. The IF 3+1
protection needs two OptiX RTN 620. One is the primary NE and the other is the secondary
NE. You need to configure the REG on the NEs and then create the IF 3+1 protection on
the primary NE.

l Line board: The line board should support the interaction between the primary and
secondary NEs. Slot 4 is the optimum location for the line board. Two more line boards
are needed for adding and dropping services.
are required.
12.2.2 Availability
The N+1 protection feature requires the support of the applicable equipment and boards.
Table 12-4 Availability of the N+1 protection feature

IF1A/IF1B RTN 620
IFX
Table 12-5 Availability of the N+1 protection feature

IFU2 RTN 910/950
IFX2
NOTE
The Hybrid microwave does not support the N+1 protection.

The N+1 protection uses the N+1 protection protocol to realize the switching. The N+1
protection protocol is similar to the 1:N linear multiplex section protection protocol.
12.2.3.1 2+1 Protection Configuration

In the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realize
protection switching.
In the case of the 3+1 protection configuration, the primary NE forms a 3+1 protection group
to realize protection switching and the secondary NE forms two STM-1 REGs to realize
transparent transmission of byte K.

In the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realize
NOTE
The following describes the switching principle of the 2+1 protection as an example.

Figure 12-5 Realization principle of 2+1 protection (before the switching)

PXC
4-SD1-1 5-IF1B-1 15-ODU
6-SL1-1 7-IF1B-1 17-ODU
4-SD1-2 8-IF1B-1 18-ODU
Working channel Protection channel
Figure 12-6 Realization principle of 2+1 protection (after the switching)

PXC
4-SD1-1 5-IF1B-1 15-ODU
6-SL1-1 7-IF1B-1 17-ODU
4-SD1-2 8-IF1B-1 18-ODU
In this example, port 1 of the IF1B board in slot 5, port 1 of the IF1B board in slot 7, and port 1
of the IF1B board in slot 8 form a 2+1 protection group.
When a working channel fails, the switching principle of the 2+1 protection configuration is as
follows:
1. Before the switching, the NE sends and receives normal traffic signals on the working
channel, and sends and receives extra traffic signals on the protection channel.
2. On detecting that the signals on a working channel fail (for example, the IF1B board in slot
5 detects that an MW_LOF alarm is generated on port 1), the IF board notifies the SCC
board.
3. The SCC board controls the PXC board to realize the transmission of the working traffic
signals (port 1 of the SD1 board in slot 4) on the protection channel (port 1 of the IF1B
board in slot 8). The SCC board also interacts with the NE on the opposite side through
byte K to enable the NE on the opposite side to perform synchronous switching.

NOTE
The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSP
protocol. For details, see Realization Principle of 1:N Linear MSP.

In the case of the 3+1 protection configuration, the primary NE forms a 3+1 protection group
to realize protection switching and the secondary NE forms two STM-1 REGs to realize
transparent transmission of byte K.
NOTE
The following describes the switching principle of the 3+1 protection as an example.
Figure 12-7 Realization principle of the 3+1 protection (before the switching)
Primary NE
PXC
6-SD1-1 5-IF1B-1 15-ODU
6-SD1-2 7-IF1B-1 17-ODU
8-SD1-1 4-SD1-1
8-SD1-2 4-SD1-2
Secondary NE
PXC
4-SD1-1 5-IF1B-1 15-ODU
4-SD1-2 7-IF1B-1 17-ODU

Figure 12-8 Realization principle of the 3+1 protection (after the switching)
Primary NE
PXC
6-SD1-1 5-IF1B-1 15-ODU
6-SD1-2 7-IF1B-1 17-ODU
8-SD1-1 4-SD1-1
8-SD1-2 4-SD1-2
Secondary NE
PXC
4-SD1-1 5-IF1B-1 15-ODU
4-SD1-2 7-IF1B-1 17-ODU
In this example, port 1 of the IF1B board in slot 5 of the primary NE, port 1 of the IF1B board
in slot 7 of the primary NE, and ports 1 and 2 of the SD1 board in slot 4 of the primary NE form
a 3+1 protection group. An REG is established between port 1 of the IF1B board in slot 5 of the
secondary NE and port 1 of the SD1 board in slot 4 of the secondary NE. Another REG is
established between port 1 of the IF1B board in slot 7 of the secondary NE and port 2 of the
SD1 board in slot 4 of the secondary NE.
When a working channel fails, the switching principle of the 3+1 protection configuration is as
follows:
1. Before the switching, the primary NE sends and receives normal traffic signals on the
working channel, and sends and receives extra traffic signals on the protection channel.
The secondary NE works as an REG to transparently transmit VC signals and multiplex
section overheads.
2. On detecting that the signals on a working channel fail (for example, the IF1B board in slot
5 detects that an MW_LOF alarm is generated on port 1), an IF board of the secondary NE
inserts the MS_AIS alarm and transparently transmits the multiplex section overheads and
VC signals to port 1 of the SD1 board in slot 4 of the primary NE through port 1 of the SD1
board in slot 4 of the secondary NE.

3. On detecting the MS_AIS alarm, the SD1 board in slot 4 of the primary NE reports the
alarm to the SCC board.
4. The SCC board controls the PXC board to realize the transmission of the working traffic
signals (port 1 of the SD1 board in slot 8) on the protection channel (port 2 of the SD1
board in slot 4). The SCC board also interacts with the NE on the opposite side through
byte K to enable the NE on the opposite side to perform synchronous switching. When the
primary NE exchanges byte K with the NE on the opposite side, the secondary NE always
transparently transmits byte K because byte K belongs to the multiplex section overheads.
NOTE
l In this example, the working channels of the secondary NE fail. If the working channels of the primary NE
fail, the IF board directly reports the alarm to the SCC board to trigger the protection switching.
l The REG formed by the secondary NE is slightly different from an ordinary REG. The REG formed by the
secondary NE does not insert an AU_AIS alarm but inserts an MS_AIS alarm to trigger the N+1 protection
switching when an MW_LOF alarm or a regenerator section alarm (for example, R_LOS, R_LOC, and
R_LOF) is generated.
l The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the
MSP protocol. For details, see Realization Principle of 1:N Linear MSP.

This topic describes the configuration flow and the corresponding configuration tasks of the N
+1 protection mode. An example is provided as additional information to help understand the
configuration.
12.2.4.1 Configuration Flow
This topic describes the configuration flow for the N+1 protection mode.
12.2.4.2 Creating REGs
In the case of the 3+1 protection, you need to configure REGs for the secondary NE.
12.2.4.3 Creating an N+1 Protection Group
When the OptiX RTN NE transmits two or three STM-1 microwave services in the point-to-
point mode, you can adopt the N+1 protection configuration.
12.2.4.4 Enabling the N+1 Protection Control Protocol
When the N+1 protection control protocol is in the disabled status, if you want to restore the
normal protection function, you need to enable the N+1 protection control protocol.
12.2.4.5 Verifying the N+1 Protection Switching
On the U2000, you can perform the external switching commands such as the clear switching,
lockout of switching and forced switching, to meet the requirements in certain scenarios.

This topic describes the configuration flow for the N+1 protection mode.

Figure 12-9 Configuration flow for the N+1 protection mode
Start
1
Create an N+1
protection group
Is the 3+1 No
protection mode
used?
Yes
2
Create REGs
End
Table 12-6 Description of the configuration flow of the N+1 protection mode
Number Description
1 l In the case of the 3+1 protection, an N+1 protection group needs to be

created only for the primary NE.
l For the configuration process, see 12.2.4.3 Creating an N+1 Protection
Group.
2 l Create REGs between two IF boards of the secondary NE and two ports
of the SD1 board that is connected to the primary NE.
l For the configuration process, see 12.2.4.2 Creating REGs.
Relation with other features

l The members of an N+1 protection group cannot be configured with the 1+1 protection.
l Each member of an XPIC working group can work as the working channel or the protection
channel of the N+1 protection.
l The radio link with the N+1 protection configuration can work only as the service sink of
an SNCP service pair, and cannot work as the working source or the protection source.
12.2.4.2 Creating REGs

In the case of the 3+1 protection, you need to configure REGs for the secondary NE.

Prerequisite
The STM-1 optical/electrical interface board that is connected to the primary NE must be created.
The IF boards must work in the STM-1 mode.
Context
In the case of the 3+1 protection, you need to two configure REGs for the secondary NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Protection
Configuration > REG Configuration from the Function Tree.
The system displays the Create REG dialog box.
Step 3 Set the SD Enabled parameter.
Step 4 Set the slot mapping relation.
1. In Slot Mapping Direction, select West Line.
2. In Select Mapping Mode, select the line port to which the west line corresponds and click
.
3. In Slot Mapping Direction, select East Line.
4. In Select Mapping Mode, select the line port to which the east line corresponds and click

Step 5 Click OK.

Step 6 Repeat Step 2 to Step 5, Create another REG.
----End

Parameters
SD Enabled Enabled, Disabled Enabled l When this parameter is set to Enabled,

the REG inserts an MS-AIS alarm when
a B2_SD alarm is generated.
default value.
Slot Mapping - - It is recommended that you map the IF port

Relation as West Line and the port of the STM-1
optical/electrical interface board as East
Line.
12.2.4.3 Creating an N+1 Protection Group

When the OptiX RTN NE transmits two or three STM-1 microwave services in the point-to-
point mode, you can adopt the N+1 protection configuration.
Prerequisite
The STM-1 optical/electrical interface boards (only in the case of the primary NE that is to be
configured with 3+1 protection) must be created.
The IF boards must work in the STM-1 mode.
When an N+0 service is converted into an N+1 service by configuring the N+1 protection, the
original services are not interrupted.
NOTE
It is recommended that you configure the channels in the ACAP mode.
Procedure
Step 1 Select a navigation path:
l In the NE Explorer, select the NE from the Function Tree and then choose Configuration >
Link Configuration from the Function Tree. Click the N+1 Protection tab.
l In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
Protection Configuration > N+1 Protection from the Function Tree.

The system displays the Create an N+1 Protection Group dialog box.
Step 3 Set the attributes of the N+1 protection group.


1. In Select Mapping direction, select Working Unit.
2. In Select Mapping Mode, select the line port to which a working channel corresponds and
click .
3. Repeat Step 4.2 to select the line ports to which other working channels correspond.
4. In Select Mapping direction, select Protection Unit.
5. In Select Mapping Mode, select the line port to which the protection channel corresponds
and click .
NOTE
l Set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that
you set the value to ten minutes.
l It is recommended that you use SD as a switching condition.
Step 5 Click OK.
----End
Parameters
WTR Time(s) 300 to 720 600 l When the time after the former working
default value.

SD enable Enabled, Disabled Enabled l When SD enable is set to Enabled, the

B2_SD alarm is considered as a
switching condition.
default value.
Slot Mapping - - l In the case of 2+1 protection, map two

Relation IF ports as Working Unit and map the
remaining IF port as Protection Unit.
l In the case of the 3+1 protection, it is
recommended that you map the two IF
ports and the first line port of the STM-1
optical/electrical interface board that is
connected to the secondary NE as
Working Unit, and map the other line
port as Protection Unit.
NOTE
The N+1 protection groups of the equipment at both ends must have the same attributes.
12.2.4.4 Enabling the N+1 Protection Control Protocol

When the N+1 protection control protocol is in the disabled status, if you want to restore the
normal protection function, you need to enable the N+1 protection control protocol.
Prerequisite
l Protocol Status of the N+1 protection must be Disabled.
Context
After maintaining the equipment, enable the N+1 protection control protocol, to restore the
normal protection function of the equipment.
Procedure
Step 1 In the NE Explorer, select Link Configuration from the Function Tree, click the N+1
Protection tab. Select the N+1 protection group and click Start Protocol.
Step 2 A prompt is displayed indicating that the operation is successful. Click OK.
Step 3 Click Query and the current protocol status is displayed.
----End

Postrequisite
NOTE
Before maintaining the equipment, disable the N+1 protection control protocol, to avoid the protection
switching caused by the equipment maintenance.
l In the NE Explorer, select Configuration > N+1 Protection from the Function Tree. Select
the IF N+1 protection group and click Stop Protocol.
l A prompt is displayed indicating that the operation is successful. Click OK.
l Click Query and the current protocol status is displayed.
12.2.4.5 Verifying the N+1 Protection Switching

On the U2000, you can perform the external switching commands such as the clear switching,
lockout of switching and forced switching, to meet the requirements in certain scenarios.
Prerequisite
l The N+1 protection group must be created.
Context
The external switching commands are as follows: clear switching, lockout of protection, forced
switching to protection, manual switching to protection, and exercise switching.
l Clear switching: This command can be used to clear the forced switching, manual
switching, lockout of switching, and exercise switching.
l Lockout of protection: No service, including the normal and extra services, is allowed to
be switched from the working channel to the protection channel. If the service is already
switched to the protection channel, the command will force it back to the working channel
even if the working channel is abnormal.
CAUTION
Therefore, if the protection switching already occurs, running this command will interrupt
services.
l Forced switching to protection: That means to forcibly switch the services from the working
channel to protection channel regardless of the state of the protection channel. After the
forced switching, the system will be always in the switching status, and will not be switched
back to the working channel unless manual interference.
l Manual switching to protection: That means to switch the services from the working
channel to protection channel. If the protection channel is normal, the switching will occur.
If the protection channel fails or is satisfying a switching of higher priority, the manual
switching will not occur. After the manual switching, the system will not be switched back
to the working channel unless manual interference.
l Exercise switching: This command is used to test whether the switching protocol works
normally. Actually, no switching occurs and the service will not be affected

Procedure
Step 1 Select the NE to be queried. In the NE Explorer, choose Configuration > Link
Configuration from the Function Tree. In the right pane, click the N+1 Protection tab.
Step 2 In Slot Mapping Relation, right-click the working or protection unit and choose corresponding
external switching command from the shortcut menu.
Step 3 In the prompt displayed, click OK.
Step 4 Click Query to query the switching status.
----End
12.3 Configuring Linear Multiplex Section Protection

The linear MSP is applicable to point-to-point physical networks. The linear MSP provides
protection for the services between two nodes at the multiplex section level.
The OptiX IDU 610 supports a maximum of two linear MSP groups for the STM-1 optical/
electrical line. The OptiX IDU 620 supports a maximum of five linear MSP groups, or a
combination of three linear MSP groups for the optical/electrical line and one STM-4 linear
MSP group.
This topic considers the application of the linear MSP as an example to describe the linear MSP
feature.
12.3.2 Availability
The linear MSP solution requires the support of the applicable equipment and boards.
The 1+1 protection and the 1:N protection have different switching principles.

This topic considers the application of the linear MSP as an example to describe the linear MSP
feature.
The linear MSP is applicable to the point-to-point network. The OptiX RTN 600 supports the 1
+1 linear MSP and 1:N linear MSP.
l 1+1 linear MSP
To realize the 1+1 linear MSP, one working channel and one protection channel are
required. When the working channel becomes unavailable, services are switched to the
protection channel for transmission. Figure 12-10 shows the application of the 1+1 linear
MSP.

Figure 12-10 1+1 linear MSP
NE A Working NE B
channel
Protection
channel
NE A Working NE B
channel
Protection
channel
l 1:N linear MSP

To realize the 1:N linear MSP, N working channels and one protection channel are required.
The working channels transmit normal services and the protection channel transmits extra
services. When a working channel becomes unavailable, the services on this channel are
switched to the protection channel for transmission. As a result, the extra services
previously transmitted on this protection channel are interrupted. Figure 12-11 shows the
application of the 1:N linear MSP.

Figure 12-11 1:N linear MSP

NE A Working NE B
channel 1
Normal Normal
service 1 service1
... Working ...
channel N
Normal Normal
service N service N
Protection
channel
Extra Extra
service service
NE A Working NE B
channel 1
Normal Normal
service 1 service1
... Working ...
channel N
Normal Normal
service N service N
Protection
channel
Extra Extra
service service
12.3.1.1 Protection Type

The linear MSP can be classified in terms of the protection mechanism, switching mode, and
revertive mode.
12.3.1.1 Protection Type

The linear MSP can be classified in terms of the protection mechanism, switching mode, and
revertive mode.
In terms of the protection mechanism, the linear MSP is classified into the dedicated protection
and the shared protection.
l Dedicated protection
Dedicated protection refers to the case that one working channel exclusively uses one
protection channel. The dedicated protection channel cannot carry extra services. The 1+1
protection is the dedicated protection.
l Shared protection
Shared protection refers to the case that one or more working channels share one protection
channel. The shared protection channel can carry extra services. The 1:N (including the
1:1) protection is the shared protection.
In terms of the switching mode, the linear MSP is classified into the single-ended switching and
the dual-ended switching.
l Single-ended switching

In the single-ended switching mode, the switching occurs only at one end and the state of
the other end remains unchanged.
l Dual-ended switching
In the dual-ended switching mode, the switching occurs at both ends at the same time.
In terms of the revertive mode, the linear MSP is classified into the revertive mode and the non-
revertive mode.
l Revertive mode
When an NE is in the switching state, the NE releases the switching and enables the former
working channel to return to the normal state some time after the former working channel
is restored to normal. The period from the time the former working channel is restored to
normal to the time the NE releases the switching is called the wait to restore (WTR) time.
To prevent frequent switching events due to an unstable working channel, it is
recommended that you set the WTR time to five to twelve minutes.
l Non-revertive mode
When an NE is in the switching state, the NE keeps the current state unchanged unless
another switching occurs even though the former working channel is restored to normal.
Hence, the linear MSP is classified into the following eight modes:
l 1+1 dual-ended revertive mode

l 1+1 dual-ended non-revertive mode
l 1+1 single-ended revertive mode
l 1+1 single-ended non-revertive mode
l 1:N dual-ended revertive mode
l 1:N dual-ended non-revertive mode
l 1:N single-ended revertive mode
l 1:N single-ended non-revertive mode
The OptiX RTN 600/900 supports the following five linear MSP modes:
l 1+1 dual-ended revertive mode

l 1+1 dual-ended non-revertive mode
l 1+1 single-ended revertive mode
l 1+1 single-ended non-revertive mode
l 1:N (N3) dual-ended revertive mode
The 1:N dual-ended revertive mode is switched according to the MSP protocol of the linear MSP
described in ITU-T G.841. The 1+1 dual-ended mode uses the protocol that is compatible with
the 1:N mode. The switching in the 1+1 single-ended mode does not use protocols.
NOTE
Huawei realizes two multiplex section protocols, the new protocol and the restructure protocol. The new protocol
is more mature and the restructure protocol is in better compliance with the standards.
12.3.2 Availability
The linear MSP solution requires the support of the applicable equipment and boards.

Table 12-7 Availability of the linear MSP solution
SL4 RTN 620
SL1/SD1 RTN 610/620
SLE/SDE
Table 12-8 Availability of the linear MSP solution
SL1D RTN 910/950

The 1+1 protection and the 1:N protection have different switching principles.
12.3.3.1 1+1 Linear MSP
The 1+1 linear MSP adopts the dual fed and selective receiving mechanism to realize the
switching.
12.3.3.2 1:N Linear MSP
The 1:N linear MSP adopts the automatic bridging mechanism to realize the switching.
12.3.3.1 1+1 Linear MSP

The 1+1 linear MSP adopts the dual fed and selective receiving mechanism to realize the
switching.
NOTE
The following describes the switching principle of the 1+1 linear MSP. The switching triggered by the signal
failure on the working channel is provided as an example.
Figure 12-12 Realization principle of 1+1 linear MSP (before the switching)
NE B Working NE A
Protection
Working
Protection
Normal service

Figure 12-13 Realization principle of 1+1 linear MSP (after the switching, in the single-ended
mode)
NE B Working NE A
Protection
Working
Protection
Normal service
Figure 12-14 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended
mode)
NE B Working NE A
Protection
Working
Protection
Normal service
When the signal on the working channel fails, the switching principle in the single-ended mode
is as follows:
1. Before the switching, the source sends traffic signals to both the working channel and the
protection channel. The sink selects the traffic signals from the working channel.
2. On detecting that the signal on the working channel fails, the line board at the sink in a
certain direction (NE A) reports the event to the SCC board.
3. After confirming that the signal on the working channel fails and that the signal on the
protection channel is normal, the SCC board enables the cross-connect board to complete
the cross-connection between the protection channel and the service sink.
When the signal on the working channel fails, the switching principle in the dual-ended mode
is as follows:

1. Before the switching, the source sends traffic signals to both the working channel and the
protection channel. The sink selects the traffic signals from the working channel.
2. On detecting that the signal on the working channel fails, the sink in a certain direction (NE
A) sends byte K to the source (NE B) on the protection channel (the request type is "signal
fail").
3. NE B sends byte K to NE A also on the protection channel (the request type is "reverse
request").
4. NE A receives the traffic signals from the protection channel.
5. NE B also receives the traffic signals from the protection channel.
12.3.3.2 1:N Linear MSP

The 1:N linear MSP adopts the automatic bridging mechanism to realize the switching.
NOTE
The following describes the switching principle of the 1:N linear MSP. The 1:1 linear MSP switching triggered
by the signal failure on the working channel is provided as an example.
Figure 12-15 Realization principle of 1:1 linear MSP (before the switching)
NE B Working NE A
Protection
Working
Protection
Normal service Extra service
Figure 12-16 Realization principle of 1:1 linear MSP (after the switching)
NE B Working NE A
Protection
Working
Protection
Normal service Extra service

When the signal on the working channel fails, the switching principle in the 1:1 mode is as
follows:
1. Before the switching, both the source and the sink send and receive normal traffic signals
on the working channel, and send and receive extra traffic signals on the protection channel.
2. On detecting that the signal on the working channel fails, the sink in a certain direction (NE
A) sends byte K to the source (NE B) on the protection channel (the request type is "signal
fail").
3. NE B performs a bridge of the normal traffic signals onto the protection channel and sends
byte K to NE A on the protection channel (the request type is "reverse request").
4. NE A receives the normal traffic signals from the protection channel and performs a bridge
of the normal traffic signals onto the protection channel.
5. NE B receives the normal traffic signals from the protection channel.
NOTE
Actually, to speed up the switching, NE B does not perform a service bridge in Step 3 but performs it in Step 5.
12.3.4.1 Creating Linear MSP

To protect the services carried by the optical fibers or STM-1e cables between two nodes,
configure the linear MSP.
12.3.4.2 Verifying Linear MSP Switching
During deployment and commissioning, you can perform switching to test whether the linear
MSP switching works properly. In fault maintenance, you can perform this operation to locate
faults.
12.3.4.3 Setting an MS Node Number
Generally, when you create an MSP ring, the U2000 assigns an MS node number to each node
automatically. In addition, you can also set the MS node number manually in the case of network
expansion and reconstruction.
12.3.4.1 Creating Linear MSP

To protect the services carried by the optical fibers or STM-1e cables between two nodes,
configure the linear MSP.
Prerequisite
The boards where the working unit and the protection unit are located must be configured.
When an unprotected service is converted into a linear MSP service by configuring the linear
MSP, the original services are not interrupted.

WARNING
l The line that is configured with the linear MSP can work only as the sink of an SNCP service
pair, and cannot work as the working source or the protection source.
l The line that is configured with the linear MSP cannot be configured to form an MSP ring.
Procedure
Configuration > Linear MS from the Function Tree.
The system displays the Create a Linear Multiplex Section dialog box.
Step 3 Set the attributes of the linear MSP group.
NOTE
When Protection Type is set to 1:N Protection. A prompt is displayed, indicating that the service that is
configured in the protection timeslot is changed to an extra service.

1. In Select Mapping direction, select West Working Unit.
2. In Select Mapping Mode, select the line port to which the working channel corresponds
and click .
3. In Select Mapping direction, select West Protection Unit.
and click .

NOTE
l It is recommended that you select the 1+1 single-ended non-revertive mode or the 1:1 dual-ended revertive
mode, depending on the requirements.
l In the 1+1 single-ended non-revertive mode, the realization is simple and the switching speed is high.
In addition, the equipment at both sides need not be interconnected.
l In the 1:N dual-ended revertive mode, extra services can be transmitted.
l Plan the parameters relevant to the protection configuration.
l The MS protocols used at both sides must be consistent. It is recommended that you adopt the new
protocol when both sides use the OptiX equipment.
l It is recommended that the working channel uses the line ports of one line board and the protection
channel uses those of another line board to prevent the situation in which the failure of a line board
causes the protection to fail.
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes
to twelve minutes. It is recommended that you set the value to ten minutes.
Step 5 Click OK.
----End

Parameters
Protection Type 1+1 Protection, 1:N 1+1 Protection l In the single-ended mode, if the services
Protection on the working channels in a certain
direction need to be switched, only the
Switching Mode l Single-Ended l Single-Ended services on the working channels in the
Switching, Dual- Switching (1+1 direction are switched to the protection
Ended Switching protection) channels.
(1+1 protection) l Dual-Ended
l In the dual-ended mode, the services on
l Dual-Ended Switching (1:N the working channels in two directions
Switching (1:N protection) are switched to the protection channels.
protection)
l When Revertive Mode is set to
Revertive Mode l Non-Revertive, l Non-Revertive Revertive, the NE that is in the
Revertive (1+1 (1+1 protection) switching state releases the switching
protection) and enables the former working channel
l Revertive (1:N
l Revertive (1:N protection)
protection)
restored to normal.
l When Revertive Mode is set to Non-
l When extra services need to be
transmitted or several working channels
exist, select 1:N protection.
l In the case of other situations, it is
recommended that you select the 1+1
single-ended and non-revertive mode.
WTR Time(s) 300 to 720 600 l This parameter is valid only when
default value.

default value.

Protocol Type New Protocol, New Protocol l The new protocol is more mature than
Restructure Protocol the restructure protocol but the
restructure protocol is in better
compliance with the standards than the
new protocol.
l It is recommended that you select the
new protocol. When the OptiX
equipment is interconnected with the
third-party equipment, select the
restructure protocol if an interconnection
problem occurs when the new protocol
is adopted.
Slot Mapping - - l In the case of 1+1 protection, only one

Relation line port can be mapped as West
Working Unit; in the case of 1:N
protection, a maximum of three line
ports can be mapped as West Working
Unit.
l Only one line port can be mapped as
West Protection Unit.
l Ensure that the line port that is mapped
as West Protection Unit and the line
port that is mapped as West Working
Unit are not on the same board, if
possible.
NOTE
Ensure that the MSP groups of the equipment at both ends of the linear multiplex section are set with the same
attributes.
Postrequisite
l In the case of the 1:N linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later. If extra services need to be transmitted,
it is necessary to configure bidirectional cross-connections between the extra services and
the protection channels.
l In the case of the 1+1 linear MSP, you need to configure unidirectional cross-connections
between the services and the protection channels, in addition to configuring the
bidirectional cross-connections between the services and the working channels.
12.3.4.2 Verifying Linear MSP Switching

During deployment and commissioning, you can perform switching to test whether the linear
MSP switching works properly. In fault maintenance, you can perform this operation to locate
faults.

Prerequisite
l The linear MSP must be created.
Context
The external switching for MSP protection includes lockout, forced switching, manual
switching, and exercise switching.
l In the event of lockout of switching, the switching request for the port is denied, but the
reversion of switching is allowed. Regardless of the status of the working and protection
channels, the services are locked in the working channel.
l Forced switching has a higher priority than signal failure and signal degrade, on the
protection section. This switching is performed regardless of the protection channel state,
unless the protection channel is satisfying a higher priority bridging request.
l Manual switching has a lower priority than signal failure and signal degrade, on the
protection section. The manual switching request is valid only when there is no signal
failure or signal degrade on the protection section.
l The exercise switching is used to test the APS protocol. In fact services are not switched
to the protection section, and only the calculation result of the protocol is displayed.
CAUTION
Switching other than the exercise switching may interrupt services.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Protection Configuration >
Linear MS from the Function Tree.
Step 2 In the slot mapping table, right-click a direction and choose a switching or lockout option from
the shortcut menu. Click Close in the Operation Result dialog box.
NOTE
The switching is performed only when the direction is not locked.
----End
12.3.4.3 Setting an MS Node Number

Generally, when you create an MSP ring, the U2000 assigns an MS node number to each node
automatically. In addition, you can also set the MS node number manually in the case of network
expansion and reconstruction.
Prerequisite
l An MSP ring must be created.

Context
CAUTION
Setting an MS node number may affect the existing service.
Procedure
l In the NE Explorer, select an NE and choose Configuration > Protection
Configuration > Ring MS from the Function Tree.
l Double-click Local Node, West Node, and East Node respectively and enter a new value.
NOTE
For the rules of setting an MS node number, see 12.4.3.1 Configuring the Ring MSP.
l Click Apply. In the Confirm dialog box, click Yes. In the Operation Result dialog box,
click Close.
----End
12.4 Configuring Two-Fiber Bidirectional Ring MSP

The two-fiber bidirectional ring MSP scheme is applicable to an SDH ring network of the STM-4
or higher level formed by fibers, and provides protection at the MS level for services between
the nodes of a ring network.
The IDU 620 supports a maximum of one STM-4 two-fiber bidirectional MSP ring.
This topic considers the application of the two-fiber bidirectional MSP ring as an example to
describe the two-fiber bidirectional MSP ring feature.
12.4.2 Availability
The two-fiber bidirectional ring MSP needs the support of the corresponding equipment and
boards.
The two-fiber bidirectional ring MSP adopts the automatic bridging mechanism between
working channels and protection channels to realize the switching.

This topic considers the application of the two-fiber bidirectional MSP ring as an example to
describe the two-fiber bidirectional MSP ring feature.
On a two-fiber bidirectional MSP ring, the first half of VC-4s on each STM-N line is allocated
to the working channel, and the other half of VC-4s is allocated to the protection channel. In
normal cases, services are transmitted on the working channel. The services transmitted on two
fibers flow in inverse directions. When a fiber cut occurs and the working channel becomes
unavailable, the services on the two ends of the faulty point are both switched from the working
channel of the faulty fiber to the protection channel of the reverse directional fiber for
transmission. Figure 12-17 shows the application of the two-fiber bidirectional MSP ring.

Figure 12-17 Two-fiber bidirectional MSP ring

NE A
East West
West East
STM-4 two-fiber
NE B bidirectional MSP ring NE D
East
West
West East
NE C
Protection swicthing
NE A
East West
West East
STM-4 two-fiber
West
East
East
West
NE C
Service between NE A and NE C
The two-fiber bidirectional MSP ring is applicable to the ring on which the services are
distributed. When the services are converged on the ring, the maximum service capacity of this
ring is STM-N/2. When the services are evenly distributed on the ring, the maximum service
capacity of this ring is M x STM-N/2, where M indicates the number of nodes on the ring.
Protection Type
The two-fiber bidirectional ring MSP has the following characteristics in terms of the protection
type:
l A ring network uses two fibers. One fiber is used to receive signals and the other fiber is
used to transmit signals.
l Services are received and transmitted on the same route.
l The normal services between different nodes share the protection channel. The protection
channel can be used to transfer extra services. In a two-fiber bidirectional MSP ring, the

first half of the VC-4s are the working channels and the second half of the VC-4s are the
protection channels.
l The two-fiber bidirectional ring MSP adopts the revertive mode. That is, an NE that is in
the switching state releases the switching and enables the former working channel to return
to the normal state some time after the former working channel is restored to normal. The
period from the time the former working channel is restored to normal to the time the NE
releases the switching is called the wait-to-restore (WTR) time. To prevent frequent
switching events due to an unstable working channel, it is recommended that you set the
WTR time to five to twelve minutes.
12.4.2 Availability
The two-fiber bidirectional ring MSP needs the support of the corresponding equipment and
boards.
Table 12-9 Availability of the two-fiber bidirectional ring MSP
Feature Applicable Board Applicable Equipment
Two-fiber bidirectional ring SL4 (all the versions) IDU 620

MSP

The two-fiber bidirectional ring MSP adopts the automatic bridging mechanism between
working channels and protection channels to realize the switching.
NOTE
The following section describes the switching principle of the two-fiber bidirectional ring MSP. The protection
switching triggered by a unidirectional signal failure on a two-fiber bidirectional MSP ring formed by four NEs
is provided as an example.
Figure 12-18 Realization principle of the two-fiber bidirectional ring MSP (before the
switching)
NE A
East West
#1 VC-4
West East
STM-4 two-fiber
East
West
West East
NE C
Service between NE A and NE C

Figure 12-19 Realization principle of the two-fiber bidirectional ring MSP (after the switching)
NE A
East West
#3VC-4
West East
STM-4 two-fiber
#3 VC-4
West
East
#1 VC-4 East
West
NE C
Service from NE A to NE C
When the signal on the working channel fails, the switching principle of the two-fiber
bidirectional ring MSP is as follows:
1. When the network is in the normal state, the service between NE A and NE C is transmitted
in certain timeslots of the first VC-4 in the line. The service route is shown in Figure
12-18.
2. On detecting that the signal on the working channel in the receive direction fails, the west
line board of NE B sends byte K (the request type being SF_R and the state being MS-RDI)
on the short path (NE B -> NE A) and also sends byte K (the request type being SF_R and
the state being idle) on the long path (NE B -> NE C -> NE D -> NE A).
3. After receiving byte K sent from NE B to NE A, NE C and NE D transparently transmit
the received byte K.
4. After receiving byte K on the short path, the east line board of NE A sends byte K (the
request type being RR_R and the state being idle) on the short path (NE A -> NE B) and
also sends byte K (the request type being SF_R and the state being idle) on the long path
(NE A -> NE D -> NE C -> NE B).
5. After receiving byte K on the long path, the west line board of NE A sends byte K (the
request type being RR_R and the state being the bridging and switching) on the short path
(NE A -> NE B) and also sends byte K (the request type being SF_R and the state being
the bridging and switching) on the long path (NE A -> NE D -> NE C -> NE B).
NE A enters the east switching state. That is, NE A receives the services that should be
received from the east working channels in normal cases from the west protection channels,
and transmits the services that should be transmitted to the east working channels in normal
cases to the west protection channels. In the case of the service between NE A and NE C,
NE A transmits the service to the first VC-4 path in the east direction in the normal state,
but transmits the service to the third VC-4 path in the west direction in the east switching
state.
6. After receiving byte K (the request type being SF_R and the state being the bridging and
switching) sent from NE A to NE B, NE C and NE D enter the pass-through state. When
NE C and NE D pass through byte K, NE C and NE D also pass through the information
carried on the protection channels.
7. After receiving byte K (the request type being SF_R and the state being the bridging and
switching) sent from NE A, NE B sends byte K (the request type being SF_R and the state
being the bridging and switching) on the long path (NE B -> NE C -> NE D -> NE A).

NE B enters the west switching state. That is, NE A receives the services that should be
received from the west working channels in normal cases from the east protection channels,
and transmits the services that should be transmitted to the west working channels in normal
cases to the east protection channels. In the case of the service between NE A and NE C,
NE B receives the service from the first VC-4 path in the west direction and transmits the
service to the first VC-4 in the east direction in the normal state, but receives the service
from the third VC-4 path in the east direction and transmits the service to the first VC-4
path in the east direction in the west switching state.
12.4.3.1 Configuring the Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you can
configure the ring MSP.
12.4.3.1 Configuring the Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you can
configure the ring MSP.
Prerequisite
The boards where the working unit and the protection unit are located must be configured.
When an unprotected service is converted into a ring MSP service by configuring the ring MSP,
the original services are not interrupted.
NOTE
l The line of a two-fiber bidirectional MSP ring cannot be configured with the linear MSP.
l The line of a two-fiber bidirectional MSP ring can work only as the sink of an SNCP service pair, and cannot
work as the working source or the protection source.
Procedure
Configuration > Ring MS from the Function Tree.

A prompt is displayed, indicating that the service that is configured in the protection timeslot is
changed to an extra service.
Step 3 Click OK.

The system displays the Create a Ring Multiplex Section dialog box.
Step 4 Set the attributes of the ring MSP protection group according to the networking plan.

1. Set Local Node, West Node, and East Node according to the networking plan.
2. In Select Mapping Direction, select West Line 1.

3. In Select Mapping Mode, select the line port to which the working channel corresponds
and click .
4. In Select Mapping Direction, select East Line 1.
and click .
NOTE
l Allocate a node ID to each NE.

l The number of NE nodes must not exceed 16. The value range of a node ID is from 0 to 15.
l In the case of a newly-built ring network, it is recommended that you set the node ID of the central
station in the network to 0 and allocate node IDs to the other NEs one by one counterclockwise, with
the node ID of each NE being one more than the node ID of the previous NE.
l If you add an NE in an existing ring network, it is recommended that you set the node ID of the new NE
to the number that is one less than the maximum number of the nodes (including the new NE) in the
ring network.
l The MSP protocols used in a ring network must be consistent. It is recommended that you select the new
protocol.
l Set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that
you set the value to ten minutes.
Step 6 Click OK.
----End

Parameters
Level - - The value is always set to STM-4.
Protection Type - - The value is always set to 2-fiber

Bidirectional Multiplex Section.
Local Node 0 to 15 0 l This parameter specifies the node ID

allocated to the local NE.
l The node ID of each NE must be unique.
West Node 0 to 15 0 This parameter specifies the node ID that is

allocated to the NE to which the west line
board of the local NE is connected.
East Node 0 to 15 0 This parameter specifies the node ID that is

allocated to the NE to which the east line
board of the local NE is connected.
WTR Time(s) 300 to 720 600 l When the time after the former working
set value of this parameter, a revertive
switching occurs.
default value.

default value.
Protocol Type New Protocol, New Protocol l The new protocol is more mature than
Restructure Protocol the restructure protocol but the
restructure protocol is in better
compliance with the standards than the
new protocol.
l It is recommended that you select the
new protocol. When the OptiX
equipment is interconnected with the
third-party equipment, select the
restructure protocol if an interconnection
problem occurs when the new protocol
is adopted.
Slot Mapping - - It is recommended that you map the line port

Relation of the SL4 board in slot 6 as West Line 1
and map the line port of the SL4 board in
slot 8 as East Line 1.

Map as VC4 Selected, Not Not selected l If you select Map as VC4, the VC-4 is
selected considered as the unit of the settings in
the slot mapping relation.
default value.
NOTE
The protection groups of the NEs that form a ring multiplex section must be set with the same attributes except
Local Node, West Node, and East Node.
Postrequisite
In the case of a two-fiber bidirectional MSP ring, you need to configure bidirectional cross-
connections between the services and the timeslots of the working channel (the first half of the
timeslots of the line port) later. If extra services need to be transmitted, you need to configure
bidirectional cross-connections between the extra services and the timeslots of the protection
channel (the second half of the timeslots of the line port).
12.5 Configuring Sub-Network Connection Protection

The sub-network connection protection (SNCP) scheme protects the services that are across
subnets. The subnet can be a chain, a ring, or a more complicated network.
The OptiX IDU 610 supports a maximum of 84 SNCP groups and the OptiX IDU 620 supports
a maximum of 210 SNCP groups.
This topic considers the application of the SNCP as an example to describe the SNCP feature.
12.5.2 Availability
The SNCP solution requires the support of the applicable equipment and boards.
SNCP is realized based on the dual fed and selective receiving mechanism.
This topic describes the configuration tasks related to SNCP services.

This topic considers the application of the SNCP as an example to describe the SNCP feature.
The SNCP protection scheme, which requires one working subnetwork and one protection
subnetwork, is to select one service from the dually transmitted services. The SNCP is applicable
to the ring, intersecting rings, ring with a chain, or mesh network. Figure 12-20 shows the
application of the SNCP.

Figure 12-20 Sub-Network Connection Protection
Working SNC
Trail source Trail sink
NE A NE B
Protection SNC
Working SNC
NE A NE B
Protection SNC
Protection Type
SNCP is classified into the revertive mode and the non-revertive mode.
l Revertive mode
When an NE is in the switching state, the NE releases the switching and enables the former
working channel to return to the normal state some time after the former working channel
is restored to normal. The period from the time the former working channel is restored to
normal to the time the NE releases the switching is called the wait to restore (WTR) time.
To prevent frequent switching events due to an unstable working channel, it is
recommended that you set the WTR time to five to twelve minutes.
l Non-revertive mode
When an NE is in the switching state, the NE keeps the current state unchanged unless
another switching occurs even though the former working channel is restored to normal.
SNCP Service Pair

An SNCP service pair is a basic unit of SNCP. It consists of a working source, a protection
source, and a service sink.

Figure 12-21 SNCP service pair

Working source Protection source
Service sink
The working source and the protection source can be of the fiber line, STM-1e cable, or radio
link, and can be of different line types. The service sink can be of any line or tributary type.
12.5.2 Availability
The SNCP solution requires the support of the applicable equipment and boards.
Table 12-10 Availability of the SNCP solution

IF1A/IF1B IDU 610/620
SL1/SD1
SLE/SDE
IFX IDU 620
SL4
Table 12-11 Availability of the SNCP solution

SL1D RTN 910/950
IF1
IFU2
IFX2
CSTA RTN 910
CSHC

SNCP is realized based on the dual fed and selective receiving mechanism.
NOTE
The following describes the switching principle of SNCP. The switching triggered by the signal failure of the
working SNC is provided as an example.

Figure 12-22 SNCP realization principle (before the switching)
Working SNC
NE A NE B
Protection SNC
Figure 12-23 SNCP realization principle (after the switching)
Working SNC
NE A NE B
Protection SNC
When the working SNC fails, the SNCP switching principle is as follows:
1. Before the switching, the trail source of the SNC (NE A) sends normal service signals to
the trail sink (NE B) through both the working SNC and the protection SNC.
2. On detecting that the signal of the working SNC fails, the line board of NE B reports the
event to the SCC board.
3. After confirming that the signal of the working SNC fails and that the signal of the
protection SNC is normal, the SCC board of NE B enables the cross-connect board to
complete the cross-connection between the protection SNC and the service sink.

This topic describes the configuration tasks related to SNCP services.
12.5.4.1 Creating Cross-Connections for SNCP Services
The cross-connection of SNCP services is a cross-connection that a working source and a
protection source correspond to a service sink.
12.5.4.2 Setting SNCP Service Control Attributes

When the control attributes that you set when creating an SNCP service are not applicable any
more, you can modify the attributes.
12.5.4.3 Setting the Automatic Switching Conditions of SNCP Services
In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic
switching conditions.
12.5.4.4 Verifying the SNCP Service Switching
During deployment and commissioning, you can perform switching to test whether SNCP
12.5.4.5 Converting Non-Protection Services into SNCP Services
After converting the non-protection services into the SNCP services, you can convert the
unidirectional cross-connection of the non-protection services into the unidirectional cross-
connection in the receive direction of the SNCP services.
12.5.4.6 Converting SNCP Services into Non-Protection Services
After converting the SNCP services into the non-protection services, you can convert the SNCP
cross-connection in the receive direction into the unidirectional cross-connection of the non-
protection services.
12.5.4.1 Creating Cross-Connections for SNCP Services

Prerequisite
The boards where the source and the sink are must be configured.
Context
l The MSP line can work only as the service sink of an SNCP service pair and cannot work
as the working source or the protection source.
l The radio link with the 1+1 protection configuration can work only as the service sink of
l The radio link with the XPIC configuration can work only as the service sink of an SNCP
l The Hybrid radio link can work only as the service sink of an SNCP service pair, and cannot
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Click Options. Then, select Interleaved or Complete Service to change the VC-12 timeslot
numbering policy used by the cross-connection.
Step 3 Click Create SNCP.

The system displays the Create SNCP Service dialog box.
Step 4 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP
service.
NOTE
l Adhere to the following principles when planning the trails:

l Do not overlap the working SNC and the protection SNC if possible.
l The OptiX RTN 600 does not support the line with the MSP, 1+1 protection configuration or N+1
protection configuration as the working source or the protection source of SNCP.
l It is recommended that the working SNC uses the line ports of one line board and the protection SNC uses
those of another line board to prevent the situation in which the failure of a line board causes the protection
to fail.
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to
twelve minutes. It is recommended that you set the value to ten minutes.
Step 5 Click OK.

NOTE
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may
fail due to the limited number of licenses.
l The calculation of the required number of licenses is based on the total number of service timeslots of all
the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4
services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For
example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of
licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number
of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require
the number of licenses that are used for 16xE1.
----End

Parameters
Service Type SNCP SNCP -
Level VC12, VC3, VC4 VC12 l Specifies the level of the cross-
connection to be created.
l If the service is an E1 service or a data
service that is bound with VC-12 paths,
set this parameter to VC12.
l If the service is an E3/T3 service or a data
l If all the services in a VC-4 pass through
the NE, set this parameter to VC4.
Revertive Mode Non-Revertive, Non-Revertive l When this parameter is set to

restored to normal.
parameter to Revertive.
Direction Unidirectional, Bidirectional l When this parameter is set to

Bidirectional Unidirectional, only the cross-
connections in the SNCP receive
direction are created.
l When this parameter is set to
Bidirectional, both the cross-
direction and the cross-connections in
the SNCP transmit direction are created.
parameter to Bidirectional.

Hold-off Time 0 to 100 0 l When a line fault occurs, an NE can

(100ms) perform SNCP switching after a delay of
time to prevent the situation where the
NE performs SNCP switching and other
protection switching at the same time.
This parameter specifies the duration of
the delay.
default value because the SNCP cannot
co-exist with other protection switching
modes in the OptiX RTN 600.
default value.
Source Slot - - Indicates the source slot of the service.
Source VC4 - - Specifies the number of the VC-4 where the

service source exists.
Source Timeslot - - l Specifies the timeslot range to which the

Range(e.g.1,3-6) service source corresponds.
l You can set this parameter to a number
or several numbers. When you set this
parameter to several numbers, use "," to
separate these discrete values and use "-"
to indicate continuous numbers. For
example, "1, 3-6" indicates numbers 1,
3, 4, 5, and 6.
l In the case of an IF board that works in
the PDH mode, the first to the nth E1s/
E3s transmitted by microwaves
correspond to the first to the nth VC-12/
VC-3 timeslots respectively. Similarly,
the first to the nth ports of an E1 interface
board or an E3/T3 interface board
VC-3 timeslots respectively.
Sink Slot - - Indicates the sink slot of the service.
Sink VC4 - - Specifies the number of the VC-4 where the

service sink exists.

Sink Timeslot - - l Specifies the timeslot range to which the

Range(e.g.1,3-6) service sink corresponds.
3, 4, 5, and 6.
Configure SNCP Checked, Unchecked After you select the Configure SNCP
Tangent Ring Unchecked Tangent Ring check box, you can configure
the SNCP services on tangent points of
SNCP rings in a fast manner.
Generally, it is not recommended to select
this check box.
Activate Yes, No Yes Sets whether to immediately activate the

Immediately cross-connection that is configured.
If you need to immediately deliver the cross-
connection that is configured to NEs, set the
value of this parameter to Yes.
Postrequisite
If Direction is set to Unidirectional, the cross-connection only in the SNCP receive direction
is created. Hence, you need to configure a unidirectional cross-connection between the service
and the working trail, and later, a unidirectional cross-connection between the service and the
protection trail.
12.5.4.2 Setting SNCP Service Control Attributes

When the control attributes that you set when creating an SNCP service are not applicable any
more, you can modify the attributes.
Prerequisite
l The SNCP service must be configured.

Procedure
Step 1 In the NE Explorer, click NE and choose Configuration > Protection Configuration > SNCP
Service Control from the Function Tree.
Step 3 In the Working Cross-Connections or Protection Cross-Connections pane, select the SNCP
service for which you want to modify the control attributes.
Step 4 Double click the parameter that you want to modify, select or input a new value, and click
Apply. In the dialog box displayed, click OK according to the actual situation.
NOTE
l You can modify the WTR Time only when you set Revertive Mode to Revertive.
l After you modify the initiation condition, you need to click OK.
----End
12.5.4.3 Setting the Automatic Switching Conditions of SNCP Services

Prerequisite
An SNCP protection group at the VC-4 level must be configured.
Procedure
Configuration > SNCP Service Control from the Function Tree.
Step 2 Select the SNCP protection group. Double-click Initiation Condition to which the working
service corresponds.
The system displays the Initiation Condition dialog box.
Step 3 Select SD switching conditions. Then, click OK.
Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protection

Step 5 Repeat Step 3.
Step 6 Click Apply.

The system displays a prompt box asking you whether to carry out the switching.
Step 7 Click Yes.
----End
Parameters
UNEQ Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the HP_UNEQ alarm
as an SD switching condition.
default value.
TIM Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the HP_TIM alarm as
an SD switching condition.
default value.
SD Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the B3_SD alarm as an
SD switching condition.
default value.
EXC Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the B3_EXC alarm as
default value.
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation
Condition of the protection service.
12.5.4.4 Verifying the SNCP Service Switching

During deployment and commissioning, you can perform switching to test whether SNCP
Prerequisite
l The SNCP services must be configured.

Context
The external switching for SNCP protection includes: lockout, forced switching and manual
switching.
l In the event of lockout of switching, the switching request for the port is denied, but the
reversion of switching is allowed. Regardless of the status of the working and protection
channels, the services are locked in the working channel.
l Forced switching has a higher priority than signal failure and signal degrade, on the
protection section. This switching is performed regardless of the protection channel state,
unless the protection channel is satisfying a higher priority bridging request.
l Manual switching has a lower priority than signal failure and signal degrade, on the
protection section. The manual switching request is valid only when there is no signal
failure or signal degrade on the protection section.
CAUTION
All switching may interrupt services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Protection Configuration >
SNCP Service Control from the Function Tree.
Step 2 In the Working Service pane, select a service that you want to switch, right-click the Current
Status of the service, and choose the corresponding item from the shortcut menu to switch or
lock the service.
NOTE
A service can be switched only when it is not locked.
Step 3 In the Confirm dialog box displayed, click OK.
Step 4 Click Query to query the switching status.
----End
12.5.4.5 Converting Non-Protection Services into SNCP Services

Prerequisite
The unidirectional cross-connection of non-protection services must be configured and the

source of the cross-connection must be a line board.

When this task is performed to convert a non-protection service into an SNCP service, the
Procedure
Step 2 Optional: Query the data.

1. Click Query.
Then, the Confirm dialog box is displayed, prompting This operation will query service
at the NE and update service data at the NM. Are you sure to continue?.
2. Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation Succeeded.
3. Click Close.
Step 3 Select the bidirectional cross-connection of the non-protection service in Cross-connection.

Then, right-click and choose Expand to Unidirectional from the shortcut menu.
Step 4 Select the unidirectional cross-connection of the normal service in Cross-connection. Then,
right-click and choose Convert to SNCP from the shortcut menu.
Then, the Confirm dialog box is displayed, prompting If the non-protection service is convert
into a SNCP service, the service may be interrupted. Are you sure to continue?.
Step 5 Click OK.
service.

Step 7 Click OK.
----End
Parameters

restored to normal.

the delay.
default value.



3, 4, 5, and 6.


3, 4, 5, and 6.
Postrequisite
The SNCP service after the conversion is the SNCP service only in the receive direction. Later,
you need to configure a unidirectional cross-connection between the service and the working
trail, and a unidirectional cross-connection between the service and the protection trail. The non-

protection service can be converted into the SNCP service both in the receive direction and the
transmit direction only after the configuration.
12.5.4.6 Converting SNCP Services into Non-Protection Services

Prerequisite
The current service is transmitted in the working path.
The SNCP cross-connection in the receive direction must be configured.
When this task is performed to convert an SNCP service into a non-protection service, the
Procedure
Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection. Right-click and
choose Convert to Non-Protection Service from the shortcut menu.
Step 3 Choose Working or Protection from the displayed menu.
Step 4 Then, the Prompt dialog box is displayed, prompting If the SNCP service is converted into a
non-protection service, the service may be interrupted. Are you sure to continue?.
Step 5 Click OK.
----End
Postrequisite
You need to delete the unidirectional cross-connection between the service and the working path
or the unidirectional cross-connection between the service and the protection path. The SNCP
service can be converted into the non-protection service both in the receive direction and the
transmit direction only after the deletion.
12.6 Configuring MPLS Tunnel Protection

When you configure an MPLS tunnel on a per-NE basis, you can configure 1+1 protection and
1:1 protection for the MPLS tunnel. You can also create an MPLS tunnel protection group,
perform switching, and delete an MPLS tunnel protection group.
12.6.1 Introduction to MPLS APS

MPLS APS is a network protection mechanism. In the case of MPLS APS, a protection tunnel
is created to protect the working tunnel when the working tunnel fails.


Basic concepts related to the MPLS APS protection include the switching mode, revertive mode,
wait-to-restore (WTR) time, hold-off time, and protocol state.
12.6.3 MPLS APS Application
To realize the MPLS APS function, you need to configure two different tunnels which the source
and the sink is same but the route is different. When the working tunnel is faulty, services are
switched to the protection tunnel that is previously created.
12.6.4 Creating an MPLS Tunnel Protection Group
You can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure
1+1 protection and 1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnel
protection group, the MPLS tunnel protection group must be configured at the source and sink
NEs of the MPLS tunnel.
12.6.5 Perform MPLS Tunnel Protection Switching
On the U2000, you can perform MPLS tunnel protection switching. The protection switching
operations include forced switching, exercise switching, manual to working, and manual to
protection.
12.6.6 Deleting an MPLS Tunnel Protection Group
To delete an MPLS Tunnel protection group, the MPLS Tunnel protection groups must be
deleted at the source NE and sink NE.
12.6.1 Introduction to MPLS APS

MPLS APS is a network protection mechanism. In the case of MPLS APS, a protection tunnel
is created to protect the working tunnel when the working tunnel fails.
Purpose and Benefit

The purpose of adopting the MPLS APS mechanism is to protect certain important working
tunnels in the network and thus preventing service interruption in the case of the tunnel failure.
The APS mechanism can determine whether to perform switching based on detection at the
physical layer and the link layer.
l At the physical layer, the loss of signal is detected in microseconds.
l At the link layer, the detection is conducted by MPLS OAM in 10 ms. Set Detection Packet
Period to 3.3 ms so that the protection switching time is less than 50 ms.
In MPLS APS, detection at the link layer is performed by MPLS OAM. Thus, you must set the
MPLS OAM parameters for relevant tunnels before configuring MPLS APS.
MPLS APS 1+1 Protection

In the case of the MPLS APS 1+1 protection, the transmit end dually feeds the service to the
working and protection tunnels and the receive end selectively receives the service. When the
equipment detects a fault of the working tunnel, the receive end receives the service from the
protection tunnel.
Figure 12-24 shows MPLS APS 1+1 protection supported by the equipment.

Figure 12-24 MPLS APS 1+1 protection

Service detection point Service detection point
Working path
Subnetwork
Processing board Processing board
Access switching switching Access

Protection path/
protocol path
Subnetwork
The APS protocol is transmitted through the protection tunnel to exchange the protocol state
and the switching state. The equipment at the two ends performs service switching and
selectively receives services according to the protocol state and switching state.
Table 12-12 lists parameters for MPLS APS 1+1 protection.
Table 12-12 Parameters for MPLS APS 1+1 protection

Switching Revertive Switching Switching Switching Default
Mode Mode Protocol Time Hold-off Recovery
Time Time
(100ms)
1+1 single- Non- APS 50 ms 0 to 100 (0 by -

ended revertive protocol default)
switching
1+1 dual- Non- APS 50 ms 0 to 100 (0 by -

switching
1+1 single- Revertive APS 50 ms 0 to 100 (0 by 5 minutes

ended protocol default)
switching
1+1 dual- Revertive APS 50 ms 0 to 100 (0 by 5 minutes

switching
Any of the following conditions triggers the switching:

l The board has a hardware or software failure.
l A cold reset is performed on the board.
l A switching command is manually issued.
l MPLS OAM detects that the working tunnel is faulty at the link layer.

MPLS APS 1:1 Protection

In MPLS APS 1:1 protection, a protection tunnel is used to protect services transmitted on the
working tunnel. When the working tunnel fails, the services are switched to the protection tunnel.
The 1:1 protection adopts the single fed and single receiving mechanism.
Figure 12-25 shows MPLS APS 1:1 protection supported by the equipment.
Figure 12-25 MPLS APS 1:1 protection

Service detection point Service detection point
Working path
Subnetwork
Access switching switching Access
Subnetwork
Protection path
Protocol path
In MPLS APS 1:1 protection, services accessed are transmitted through the working tunnel.
When the working tunnel fails, the services are switched to the protection tunnel. Then, the
services are transmitted through the protection tunnel and the receive end receive the services
from the protection tunnel. The APS protocol is transmitted through the protection tunnel to
exchange the protocol state and the switching state. The equipment at the two ends performs
service switching and selectively receives services according to the protocol state and switching
state.
Table 12-13 lists parameters for MPLS APS 1:1 protection.
Table 12-13 Parameters for MPLS APS 1:1 protection

Time Time
(100ms)
1:1 dual- Non- APS 50 ms 0 to 100 (0 by -

switching
1:1 dual- Revertive APS 50 ms 0 to 100 (0 by 5 minutes

switching


Time Time
(100ms)
Any of the following conditions triggers the switching:

l The board has a hardware or software failure.
l A cold reset is performed on the board.
l A switching command is manually issued.
l MPLS OAM detects that the working tunnel is faulty at the link layer.
Compliant Standards and Protocols

MPLS APS complies with ITU-T Y.1720.

Basic concepts related to the MPLS APS protection include the switching mode, revertive mode,
wait-to-restore (WTR) time, hold-off time, and protocol state.
APS
The automatic protection switching (APS) protocol is used to coordinate actions of the source
and the sink in the case of bidirectional protection switching. By the APS protocol, the source
and the sink cooperate with each other to perform functions such as protection switching,
switching delay, and WTR function.
According to ITU-T Y.1720, the source and the sink both need to select channels in the APS.
In this case, the APS protocol is required for coordination. In the case of bidirectional protection
switching, the APS protocol needs to be used regardless of the revertive mode.
The APS protocol is always transmitted through the protection tunnel. Then, the equipment at
either end knows that the tunnel from which the APS protocol is received is the protection tunnel
of the opposite end and thus to determine whether the configuration about the working tunnel
and the protection tunnel is consistent at the two ends.
When the equipment cannot receive any APS packet, services should be always transmitted and
received from the working tunnel.
Switching Mode
MPLS APS provides two switching modes, that is, single-ended switching and dual-ended
switching.
In the case of single-ended switching, when one end detects a fault, it only performs switching
on the local end and does not instruct the opposite end to perform any switching.
In the case of dual-ended switching, when one end detects a fault, it performs switching on the
local end and also instructs the opposite end to perform switching.
Single-ended switching does not require the APS protocol for negotiation and it features rapid
and stable switching.

Dual-ended switching ensures that the services are transmitted in a consistent channel, which
facilitates service management.
Revertive Mode
The MPLS APS function supports two revertive modes, that is, revertive mode and non-revertive
mode.
In the non-revertive mode, services are not switched from the protection tunnel to the working
tunnel even the working tunnel is restored to the normal state.
In the revertive mode, services are switched from the protection tunnel to the original working
tunnel if the working tunnel is restored to the normal state within the WTR time.
WTR Time
The WTR time refers to the period from the time when the original working tunnel is restored
to the time when the services are switched from the protection tunnel to the original working
tunnel.
In certain scenarios, the state of the working tunnel is unstable. In this case, setting the WTR
time can prevent frequent switching of services between the working tunnel and the protection
tunnel.
By default, the WTR time of the equipment is 5 minutes.
Hold-off Time
The hold-off time refers to the period from the time when the equipment detects a fault to the
time when the switching operation is performed.
When the equipment is configured with the MPLS APS protection and other protection, setting
the hold-off time can ensure that other protection switching operations are performed first.
By default, the hold-off time of the equipment is 0s.
Protocol State
The protocol state indicates whether the APS protocol of the protection group is valid currently.
In the case of configuring the MPLS APS protection, the protocol state is disabled by default.
If you enable the APS protocol at the local NE first and then the opposite NE when configuring
the MPLS APS protection, the opposite NE may has an anomaly in receiving services. After the
MPLS APS protection group is configured at the two ends, start the protocol.
12.6.3 MPLS APS Application

To realize the MPLS APS function, you need to configure two different tunnels which the source
and the sink is same but the route is different. When the working tunnel is faulty, services are
switched to the protection tunnel that is previously created.
MPLS APS 1+1 Protection

In the case of MPLS APS 1+1 protection, a protection tunnel is used to protect the working
tunnel. The 1+1 protection adopts the dual fed and selective receiving mechanism. The services
are switched to the protection tunnel only when the working tunnel fails.

Figure 12-26 shows the MPLS APS 1+1 protection.
Figure 12-26 MPLS APS 1+1 protection
Working Tunnel
NE A NE B
Protection Tunnel
There are two MPLS tunnels as shown in the figure. Normally, services are transmitted through
the working tunnel, and the protection tunnel is used to transmit the APS protocol.
MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source
sends connectivity check packets periodically and the sink performs the check. Set the OAM
packet type to FFD and the sending period to 3.3 ms to ensure that the APS switching time is
less than 50 ms.
The switching mode of the MPLS APS 1+1 protection includes single-ended and dual-ended
switching.
MPLS APS 1:1 Protection

In the case of MPLS APS 1:1 protection, a protection tunnel is used to protect the working tunnel.
Normally, services are transmitted through the working tunnel. The services are switched to the
protection tunnel only when the working tunnel fails.
Figure 12-27 shows the MPLS APS 1:1 protection.
Figure 12-27 MPLS APS 1:1 protection
Working Tunnel
NE A NE B
Protection Tunnel
There are two MPLS tunnels as shown in the figure. The continuous line indicates the working
tunnel and the dashed line indicates the protection tunnel. Normally, services are transmitted
through the working tunnel, and the protection tunnel is used to transmit the APS protocol.

MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source
sends connectivity check packets periodically and the sink performs the check. Set the OAM
packet type to FFD and the sending period to 3.3 ms to ensure that the APS switching time is
less than 50 ms.
The switching mode of the MPLS APS 1:1 protection includes single-ended and dual-ended
switching.
Guide to Configuring the MPLS APS Protection

Pay attention to the following when configuring the MPLS APS protection.
l Enable MPLS OAM of the tunnels before configuring the APS protection.
l Set the MPLS OAM packet type to FFD and the sending period to 3.3 ms.
l Set the APS protocol to the enabled state after the nodes at both ends are configured with
the APS protection group.
12.6.4 Creating an MPLS Tunnel Protection Group

You can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure
1+1 protection and 1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnel
protection group, the MPLS tunnel protection group must be configured at the source and sink
NEs of the MPLS tunnel.
Prerequisite
l The working and protection tunnels of an MPLS tunnel must be created.
l You must have enabled the MPLS OAM state of each MPLS tunnel in the protection group.
l The OAM packet type must be set to FFD and transmission period to 3.3 ms.
WARNING
l The protection tunnel should not carry any extra service.
Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click New. The New Tunnel Protection Group dialog box is displayed.

Step 3 Set parameters for the tunnel protection group.

l Protection Type: You can select 1+1 or 1:1.
l Switching Mode: You can select Single-Ended or Dual-Ended. When the protection type is
1:1, the switching mode must be dual-ended.
l Revertive Mode: You can select Non-revertive or Revertive.
l Hold-off Time(100ms): The unit is 100 millisecond. You can enter an integer from 0 to 100,
that is, 0 to 10 seconds.
CAUTION
When creating an APS protection group, disable Protocol Status. Start the protocol only when
the configuration of the APS protection group is complete at both nodes.
Step 4 Click OK. The MPLS tunnel protection group is successfully configured.
NOTE
The bandwidth of the protection tunnel should exceed that of the working tunnel. To increase the bandwidth
of the working tunnel after the protection group is created, increase the bandwidth of the protection tunnel
first.
Step 5 Refer to Steps 1 through 4 to configure the protection group on the sink NE of the tunnel.
Step 6 Start the protocol state of the MPLS APS protection group.

1. Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS
Protection Management from the Function Tree.
2. Right-click a created APS protection group, and select Start Protocol.
3. A dialog box is displayed indicating that the operation is successful. Protocol Status of
the APS protection group turns to Enabled.
----End
12.6.5 Perform MPLS Tunnel Protection Switching

On the U2000, you can perform MPLS tunnel protection switching. The protection switching
operations include forced switching, exercise switching, manual to working, and manual to
protection.
Prerequisite
l You must complete the creation of the MPLS tunnel protection group and you must have
enable the protocol status.
Context
CAUTION
When other switching operations, excluding the exercise switching, are performed, the services
may be interrupted.
Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection
Step 2 Select a protection group that you want to perform protection switching.
Step 3 Click Function tab.
Step 4 Choose the switching operation to be performed from the displayed shortcut menu.

Step 5 Confirm in the confirmation dialog box.
----End
12.6.6 Deleting an MPLS Tunnel Protection Group

To delete an MPLS Tunnel protection group, the MPLS Tunnel protection groups must be
deleted at the source NE and sink NE.
Prerequisite
Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection
Step 2 Select a protection group that you want to delete.
Step 3 Click Delete. A dialog box is displayed for confirmation.
Step 4 Click Yes. The Operation Result dialog box is displayed.
Step 5 Click Close.
----End
12.7 Ethernet Ring Protection

12.7.1 Introduction to Ethernet Ring Protection

Based on the traditional Ethernet mechanism, ERPS uses the R-APS protocol to achieve fast
protection switching on the Ethernet ring network.
This section describes the basic concepts of ERPS to help you better understand ERPS.
12.7.3 Availability
This section describes the equipment type and software versions that support the ERPS
protection.
12.7.4 Function Implementation
12.7.5 Application of Ethernet Ring Protection
This section describes the application scenario of Ethernet ring protection.
12.7.6 Configuring Ethernet Ring Protection
This section describes the configuration of Ethernet ring protection, including the creation and
deletion of Ethernet ring protection, and the modification and description of parameters.

12.7.1 Introduction to Ethernet Ring Protection

Definition
Objective
The following are objectives of Ethernet ring protection:
l To provide guaranteed network connectivity.

l To provide rapid service restoration (less than 50 ms).
l To provide protection at any physical or server layer for any type of client signals.
l To support flexible networking modes.
l To reduce operational expenditure (OpEx) and capital expenditure (CapEx) for vendors.

This section describes the basic concepts of ERPS to help you better understand ERPS.
Ethernet Ring
An Ethernet ring is a collection of Ethernet ring nodes forming a closed loop whereby each node
is connected to two adjacent nodes through a full-duplex communication link.
RPL
The RPL is the ring link that is blocked at one end or both ends under normal conditions to
prevent loops. One Ethernet ring has only one RPL.
RPL Owner
The RPL owner is an Ethernet ring node adjacent to the RPL. It is responsible for blocking and
unblocking the RPL port. Under normal conditions, the RPL owner blocks the RPL port to
prevent loops.
R-APS message
R-APS message is a protection switching protocol defined for the ERPS, which contains the
messages, requests, or states required by the protection switching. Through the R-APS message
between ring nodes, it is ensured that the nodes perform consistent operations to complete the
l R-APS (NR, RB): A type of R-APS message that is sent by the RPL owner to indicate that
the ring is in normal state and the RPL port is blocked.
l R-APS (SF): A type of R-APS message that is sent by the node detecting the link fault to
indicate that an SF event occurs at the local node.

l R-APS (NR): A type of R-APS message that is sent by the node detecting the link recovery
to indicate that the SF event at the local node is cleared.
Control VLAN
The ERPS uses an independent VLAN channel to carry the R-APS messages. The control VLAN
ID cannot be the same as the service VLAN ID.
R-APS Format
R-APS information is carried in the R-APS protocol data unit (PDU), which is transmitted
through R-APS messages. R-APS messages ensure that all nodes on the ring perform consistent
operations. R-APS frame format is a type of ETH-OAM frame formats. See Figure 12-28. The
default destination MAC address of R-APS message is 01-19-A7-00-00-01. In Figure 12-28,
the gray part indicates the 32-byte R-APS specific information.
Figure 12-28 R-APS format
Table 12-14 lists the description of each filed in R-APS specific information.
Table 12-14 Description of each filed in R-APS specific information
Field Length Value Description
Request/State 4 bits 1011 Indicates signal fail (SF).
0000 Indicates no request (NR).
Others Reserved.
Resv1 4 bits 0000 Reserved.
Status RB (RPL 1 bit 1 Indicates the RPL is blocked.

Blocked)
0 l Indicates the RPL is not blocked.
l In the case of a node other than the
RPL owner, the value of RB should
be set to 0.

Field Length Value Description
DNF (Do 1 bit 1 Indicates that the ring node should not
Not Flush) update the MAC address table.
0 Indicates that the ring node should

update the MAC address table.
Status 6 bits - Reserved.

Reserved
Node ID 6 bytes - Indicates the MAC address of a ring

node. The MAC address is unique.
Reserved 24 bytes All 0s Reserved.
R-APS Timer
During the ERPS process, three timers are used, that is, guard timer, wait-to-restore (WTR)
timer, and holdoff timer.
l Guard Timer
R-APS messages are periodically transmitted over the ring and the status of the ring
nodes may change at any moment. This can result in an outdated and useless R-APS
message being received by ring nodes. The reception or forwarding of the outdated
messages may result in erroneous protection switching decisions. The guard timer is
used to prevent ring nodes from receiving outdated R-APS messages.
The period of the guard timer may be configured in 10 ms steps between 10 ms and 2s,
with a default value of 500 ms.
When the guard timer is running, the received R-APS message is discarded. When the
guard timer expires, the received R-APS message is forwarded directly.
l WTR Timer
The period from the time when the original working channel is recovered to normal to
the time when the NE releases the switching is called the wait-to-restore (WTR) time.
When the original working channel is recovered to normal, the WTR timer on the RPL
owner starts. While the timer is running, a WTR running signal is continuously
generated. After the timer expires and no switching request of higher priority is received,
the WTR timer stops generating the WTR running signal but starts to continuously
generate the WTR expire signal.
The period of the WTR timer may be configured in 1 minute steps between 5 minutes
and 12 minutes, with a default value of 5 minutes.
The WTR timer is used to prevent the frequent switching actions due to instability of
the working channel.
l Holdoff Timer
When a new fault or more faults occur, the holdoff timer starts if the preset holdoff timer
value is non-zero. When the holdoff timer is running, the fault is not reported to ERPS.
When the holdoff timer expires, the link state is checked regardless of whether the defect
persists. If there is a fault, the fault is reported to ERPS for protection switching. The
reported fault need not be the same as the fault that starts the holdoff timer.

The period of the holdoff timer may be configured in 100 ms steps between 0s and 10s
with an accuracy of 5 ms. The default value is 0s.
The holdoff timer is used to coordinate protection switching time between ERPS and
other existing protection schemes. Its purpose is to allow the protection switching at
another layer or level (for example, the LAG protection at ports) to have a chance to fix
the problem before ERPS switching.
12.7.3 Availability
This section describes the equipment type and software versions that support the ERPS
protection.
Table 12-15 Boards and equipment versions of the OptiX RTN 910, OptiX RTN 950, OptiX
RTN 620 and NMS versions that support the ERPS protection
Board Type Equipment Version
EM6T OptiX RTN 910 V100R002

OptiX RTN 950 V100R002
EFP6 OptiX RTN 620

Trigger Condition
The automatic Ethernet ring protection switching can be triggered on any of the following
conditions:
l Board fault: A key board is faulty (for example, the line board is powered off or offline).
l In the case of system-side ports,
If link capacity adjustment scheme (LCAS) is not enabled, the trigger conditions are as
follows: TU_LOP, AU_LOP, MS_AIS, AU_AIS, TU_AIS, B3_EXC, BIP_EXC,
HP_UNEQ, LP_UNEQ, VCAT_SQM_VC4, VCAT_SQM_VC3, VCAT_LOM_VC4,
VCAT_LOM_VC3, and VCAT_LOA.
If LCAS is enabled, the trigger condition is the unavailability of all members in the
virtual concatenation group (VCG).
l In the case of Ethernet ports, the trigger conditions are R_LOS, LINK_ERR, and
LSR_NO_FITED.
NOTE
If a VCG port is not bound with any VC, it indicates that the VCG port is normal and will not trigger ERPS
switching.

Switching Time
In the case of the LINK_LOS state at the ports on the client side, the switching time is less than
50 ms. In other cases, the switching time is 200 ms.
Switching Mode
Revertive means that the service is switched to the working channel after the working channel
becomes normal. Non-Revertive means that the service is not switched to the working channel
after the working channel becomes normal.
Switching State
The switching states are idle, wait-to-restore, automatic switching, idle (protection channel is
active), and SF switching.
Working Principle
ERPS uses the R-APS protocol to achieve protection switching. Figure 12-29 and Figure
12-30 show the working principle of ERPS.
NOTE
In this document, R-APS (SF), R-APS (NR), and R-APS (NR, RB) messages are referred to as SF, NR,
and NR, RB respectively.

Figure 12-29 ERPS switching process (upon a fault not on the RPL link)
RPL
NE A NE B NE C NE D
RPL Owner
W E W E W E W E
Normal 1
NR, RB (DNF) NR, RB (DNF) NR, RB (DNF) NR, RB (DNF)
State
2 Failure
4 SF
SF Flush Flush SF SF SF
5 Flush Flush
6
SF SF SF SF
Protection
State 7 Recovery
Guard timer
8 NR
NR NR NR NR
WTR timer
NR, RB (DNF) NR, RB (DNF) NR, RB (DNF) Flush NR, RB (DNF)
Normal 10
State Flush NR, RB (DNF) Flush NR, RB (DNF) Flush NR, RB (DNF) NR, RB (DNF)
As shown in Figure 12-29, the ERPS switching actions are as follows:
1. In normal state, the RPL owner (NE D) blocks the east port and sends the NR, RB message
at the east and west ports.
2. The RPL link between NE A and NE B becomes faulty.
3. NE A and NE B detect the SF condition. After the holdoff timer expires, NE A and NE B
block the ports connecting to the faulty link and flush filtering database (FDB).
4. NE A and NE B keep forwarding the SF message to the Ethernet ring periodically while
the SF condition persists.
5. The node receiving the SF message on the ring flushes FDB. When the RPL owner receives
the SF message, it unblocks the blocked RPL port.
6. The ERPS switching is complete and the ring enters stable state.
7. The fault on the link between NE A and NE B is rectified.
8. NE A and NE B detect that the SF condition is cleared. Then, NE A and NE B start the
guard timer and initiate periodical transmission of the NR message at both ring ports. When
the guard timer is running, the received R-APS message is discarded. After the guard timer
expires, NE A and NE B accept the new R-APS message that they receive.

9. When the RPL owner receives the NR message, it starts the WTR timer. At expiration of
the WTR timer, the RPL owner blocks the RPL port, sends the NR, RB message, and flushes
FDB.
10. When NE A and NE B receive the NR, RB message, they unblock the blocked ports and
stop forwarding the NR message. In addition, NE A, NE B, and NE C flush FDB when
receiving the NR, RB message. Then, the Ethernet ring returns to normal state.
Figure 12-30 ERPS switching process (upon a fault on the RPL link)
RPL
NE A NE B NE C NE D
RPL Owner
W E W E W E W E
Normal 1
State
2 Failure
4 SF (DNF) SF (DNF) SF (DNF) SF (DNF)
5 Recovery
Protection
State Guard timer
6 NR NR NR NR NR
WTR timer
Normal
8
State
As shown in Figure 12-30, the ERPS switching actions are as follows:
1. In normal state, the RPL owner (NE D) blocks the east port.
2. The RPL link between NE A and NE D becomes faulty.
3. NE A and NE D detect the SF condition. After the holdoff timer expires, NE A and NE D
block the ports connecting to the faulty link.
4. NE A and NE D keep forwarding the SF message to the Ethernet ring periodically while
the SF condition persists. The SF message contains the Do Not Flush (DNF) indication,
which prevents every node on the Ethernet ring from flushing FDB under any condition.
The RPL owner receives the SF message with the DNF indication, but the SF message is
ignored because there is a local higher priority request (local SF). When receiving the SF
message with the DNF indication, the other NEs on the ring are informed of the RPL link
fault. The other NEs, however, do not flush FDB under any condition. Then, the ring enters
stable state. There is the SF message with the DNF indication on the ring.

5. The fault on the link between NE A and NE D is rectified.

6. NE A and NE D detect that the SF condition is cleared. Then, NE A and NE D start the
guard timer and initiate periodical transmission of the NR message at both ring ports. The
guard timer prevents NE A and NE D from receiving R-APS messages. After the guard
timer expires, NE A and NE D accept the new R-APS message that they receive.
7. When the RPL owner receives the NR message, it starts the WTR timer. At expiration of
the WTR timer, the RPL owner blocks the RPL port, sends the NR, RB message with the
DNF indication. This message prevents every node on the ring from flushing FDB under
any condition.
8. When NE A receives the NR, RB message, it unblock the blocked west port and stop
forwarding the NR message. In addition, when receiving the NR, RB message, NE A, NE
B, and NE C are informed of the RPL link recovery and are required not to flush FDB under
any condition. Then, the Ethernet ring returns to normal state.
12.7.5 Application of Ethernet Ring Protection

This section describes the application scenario of Ethernet ring protection.
As shown in Figure 12-31, project T is a ring network that consists of stations A, B, C, and D.
The ring network is configured with the Ethernet ring protection. Figure 12-31 shows the
situation when ERPS occurs.
In this ring network, the RPL owner (NE D) blocks the east port on the RPL under normal
conditions. That is, all services are transmitted through the west port. When a certain link or NE
on the ring is faulty, NE D unblocks the blocked east RPL port so that the affected services can
be transmitted through the east port.

Figure 12-31 Ethernet ring protection switching
VB
RPL Owner
NE A
VB VB
NE B NE D
VB
Normal State
NE C
Failure VB
RPL Owner
NE A
VB VB
NE B NE D
VB
Protection State
NE C
Ethernet service direction
12.7.6 Configuring Ethernet Ring Protection

This section describes the configuration of Ethernet ring protection, including the creation and
deletion of Ethernet ring protection, and the modification and description of parameters.
12.7.6.1 Configuration Rules

This section describes the rules for configuring the Ethernet ring protection.
12.7.6.2 Creating Ethernet Ring Protection
Ethernet ring protection is applicable to ring networks. It uses the R-APS protocol to achieve
fast protection switching on an Ethernet ring network.
12.7.6.3 Modifying Parameters of Ethernet Ring Protection
The parameters of the created Ethernet ring protection can be queried and modified by using the
U2000.

12.7.6.1 Configuration Rules

This section describes the rules for configuring the Ethernet ring protection.
The rules for configuring the Ethernet ring protection are as follows:
l The Ethernet ring protection is applicable only to ring networks and supports the network
consisting of only one ring currently.
l At least one EM6T board must be configured at each station.
l The revertive mode must be set to revertive.
12.7.6.2 Creating Ethernet Ring Protection

Ethernet ring protection is applicable to ring networks. It uses the R-APS protocol to achieve
fast protection switching on an Ethernet ring network.
Prerequisite
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Protection > ERPS
Step 2 Click New. Then, the Create Ethernet Ring Protection Protocol Instance dialog box is
displayed.
Step 3 The protection parameters should be set according to network planning.
NOTE
For one ring network, specify one NE as the RPL owner.
Step 4 Click OK. After the operation succeeds, the Operation Result dialog box is displayed. Click
Close.
Step 5 Set Hold-Off Time(ms), Guard Time(ms), WTR Time(min), Packet Transmit Interval(s),
and Entity Level according to network planning. Click Apply.
Step 6 Display the NE Explorer of the other nodes on the ring in turn and repeat Steps 1 through 5 to
create Ethernet ring protection at each node. Then, the creation of the protection ring is complete.
Step 7 Optional: Select an instance and click Delete. Click OK in the Confirm dialog box displayed.
Then, the Operation Result dialog box is displayed, indicating that the operation is successful.
Click Close. In this case, the instance is deleted.
----End
12.7.6.3 Modifying Parameters of Ethernet Ring Protection

The parameters of the created Ethernet ring protection can be queried and modified by using the
U2000.
Prerequisite

12.7.6.2 Creating Ethernet Ring Protection must be complete.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Protection > ERPS
Step 2 Click Query. Then, the parameters of the current protection instance are displayed.
Step 3 Optional: Double-click the required field or click the drop-down list and then you can modify
the parameter value or choose a new value. In the case of Ethernet ring protection, the following
parameters can be modified: Control VLAN, Hold-Off Time(ms), Guard Time(ms), WTR
Time(min), Packet Transmit Interval(s), and Entity Level.
Step 4 Click Apply to deliver the configuration.
----End
12.8 Configuring Link Aggregation

12.8.1 Overview
12.8.2 Availability
The LAG feature requires the support of the applicable equipment and boards.
12.8.3 Principle
The LACP protocol is used to realize dynamic aggregation and de-aggregation of links. The
LACP protocol is developed based on IEEE 802.3ad.
You can bind multiple links that are connected to the same equipment by configuring an Ethernet
link aggregation.
12.8.1 Overview
The LAG aggregates multiple physical links to form a logical link that is at a higher rate. Link
aggregation functions between adjacent equipment. Hence, link aggregation is not related to the
architecture of the entire network. Link aggregation is also called port aggregation because each
link corresponds to a port in an Ethernet.
As shown in Figure 12-32, link aggregation provides the following functions:
l Increased bandwidth
The LAG provides the telecom operators with a cost-effective method of increasing the
link bandwidth. The telecom operators obtain data links with higher bandwidths by

combining multiple physical links into one logical link without upgrading the existing
equipment. The bandwidth of the logical link is equal to the sum of the bandwidths of the
physical links. The aggregation module distributes the traffic to different members by using
the load sharing algorithm, thus realizing the load sharing function at the link level.
l Increased availability
The links in a LAG provide backup to each other dynamically. When a link fails, another
link in the LAG quickly replaces the failed link. The process in which link aggregation
starts the backup link relates only to the links in the same LAG and does not relate to the
links that are not in the LAG.
Figure 12-32 Link aggregation group
Link 1
Link 2
Ethernet Link 3 Ethernet

packets packets
LAG
Standard and protocol compliance

The LAG feature complies with the IEEE 802.3ad Carrier Sense Multiple Access with Collision
Detection (CSMA/CD) Access Method and Physical Layer Specifications.
LAG Types
Types of Aggregation: Link aggregation is available in the following two types.
l Manual aggregation
A user manually creates a LAG. When a user adds or deletes a member port, the LACP
protocol is disabled. A port can be in the up or down state. The system determines whether
to perform aggregation depending on the physical status of a port (up or down).
Manual aggregation is not as accurate or effective as static aggregation in controlling link
aggregation.
l Static aggregation
A user manually creates a LAG. When a user adds or deletes a member port, the LACP
protocol is enabled. A port can be in the selected, unselected, or standby state. The
equipment exchanges aggregation information by using the LACP protocol to reach
agreement on aggregation.
Static aggregation is more accurate and more effective than manual aggregation in
controlling link aggregation.
Load Sharing Modes: The LAG supports the following load sharing modes.
l Load sharing mode
Each member link in a LAG carries traffic. That is, the member links in the LAG share the
load. In load sharing mode, the bandwidth of the link increases. When a member in a LAG
changes or a certain link fails, the traffic is re-allocated automatically.

l Load non-sharing mode

Only one member link in a LAG carries traffic and the other links in the LAG are in the
standby state. This is equivalent to the hot standby mechanism. This is because when an
active link in a LAG fails, the system selects a link among the standby links in the LAG as
an active link to replace the failed link.
Port Types
NOTE
l The main port number cannot appear in the slave port number list.
l A slave port can be added to an LAG only when no service is configured for the port. A main port can
be added to an LAG even if you configure services for the port, and the services of the port are not
affected.
l You can modify or query the attributes of a main port. You cannot set the logical attributes of a slave
port, but can query it.
l FE port and GE port can not in the same LAG.
Main Port
l The Main Port indicates the LAG member port available for creating services. Each LAG
has only one main port. If the load sharing parameter is set to Non-Sharing, the main port
carries the services. When the main port becomes faulty, the services are switched to and
carried by the slave port.
l Every Ethernet port on the NE can be used as the main port.
Slave Port
l The slave ports in a link aggregation group are fixed. Unless they are manually modified,
the system does not automatically add them to or delete them from the link aggregation
group.
l Add the relevant slave port to the link aggregation group as required.
12.8.2 Availability
The LAG feature requires the support of the applicable equipment and boards.
Table 12-16 Availability of the LAG feature
EMS6, EFP6 RTN 620
EM4T RTN 605
Table 12-17 Availability of the LAG feature
IFU2 RTN 910/950
IFX2
EM6T

EM6F
CSHA RTN 910
CSHB
CSHC
12.8.3 Principle
The LACP protocol is used to realize dynamic aggregation and de-aggregation of links. The
LACP protocol is developed based on IEEE 802.3ad.
The LACP protocol is developed based on IEEE 802.3ad and performs the following functions:
l The LACP protocol provides the data switching equipment with a standard negotiation
mode. Hence, the system automatically forms aggregation links according to its
configuration and enables the aggregation links to transmit and receive data.
l After an aggregation link is formed, the LACP protocol maintains the status of the
aggregation link. When the aggregation conditions change, the LACP protocol
automatically adjusts or releases the LAG.
As shown in Figure 12-33, the LACP protocol aggregates links as follows:
1. Equipment A and equipment B exchange LACP packets through port 1, port 2, port 3, and
port 4. Each LACP packet contains the system priority, system MAC address, port priority,
port number, and operational key. The operational key reflects the aggregation capability
of the port. The key value is determined by certain factors such as the physical
characteristics of the port (for example, rate and duplex), configuration constraints set by
the network administrator, characteristics of the port, and limitations of the port.
2. After equipment B receives an LACP packet from equipment A, equipment B compares
the information in the LACP packet with the information stored by the other ports and
selects the ports that can be aggregated.
3. After equipment A receives an LACP packet from equipment B, equipment A compares
the information in the LACP packet with the information stored by the other ports and
selects the ports that can be aggregated.
4. Equipment A and equipment B reach agreement on the ports that can be added into a LAG,
and then, form a LAG.
Figure 12-33 Application of the LACP protocol
Equipment A Equipment B
PORT1 PORT1
PORT2 PORT2
PORT3 PORT3
PORT4 PORT4

The characteristics of the LACP protocol are as follows:

l The systems realize auto-negotiation by exchanging LACP packets. Each LACP packet
contains the configuration and current status of the system that sends the LACP packet.
l The LACP packets are sent in any of the following modes:
Event triggering mode
A change in the local status or local configuration triggers the generation and sending
of a new LACP packet.
Periodical sending mode
When an aggregation link works stably, the system periodically sends the current state
to maintain the aggregation link.
l The LACP packet is not numbered. Hence, both parties use the timer and periodical sending
mechanism, instead of the detection and re-transmission of lost packets mechanism, to
prevent loss of information.
l The number of LACP packets that are sent in one second does not exceed five.

You can bind multiple links that are connected to the same equipment by configuring an Ethernet
link aggregation.
The aggregated links can be regarded as a link, as shown in Figure 12-34.
Figure 12-34 Application of the link aggregation group
LAG
Configure a link aggregation as follows:

12.8.4.1 Creating an LAG
Link aggregation allows all the members in an LAG to share the incoming and outgoing service
loads, thus increasing bandwidth. In addition, the members in the same LAG provide backup to
each other dynamically. This increases the availability of the connection.
12.8.4.2 Modifying LAG Parameters
After you create a link aggregation group (LAG), you can modify the port priority and system
priority of the links as required. In the case of the static LAG, the port with highest priority is
preferred to transmit services.
12.8.4.3 Querying Port LACP Packet Statistics
By querying the port LACP packet statistics, you can determine the current link aggregation
state.
12.8.4.4 Querying Detailed LAG Information

By querying the LAG details, you can obtain detailed information of the current LAG.
12.8.4.1 Creating an LAG

Link aggregation allows all the members in an LAG to share the incoming and outgoing service
loads, thus increasing bandwidth. In addition, the members in the same LAG provide backup to
each other dynamically. This increases the availability of the connection.
Prerequisite
The physical network topology must be established.
The Ethernet and IF boards that need to be aggregated must be created.
When IF boards are used to create an LAG, the attributes of all member ports must be consistent.
Context
NOTE
In the case of RTN600V100R004 NEs, RTN900V100R002 NEs and the NEs after the versions, when the Load
Sharing is Sharing, you can not set or query the Revertive Mode.
Procedure
1. In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Interface Management > Ethernet Link Aggregation Management from the Function
Tree.
2. Click the Link Aggregation Group Management tab.
3. Click New and the Create Link Aggregation Group dialog box is displayed. Set the
parameters.
4. Click OK.
5. Optional: Click the Link Aggregation Parameters tab. Set Port Priority and System
Priority.
NOTE
l The port ID consists of Port and Port Priority. The port that has the smallest port ID in an LAG
has the priority to be aggregated first.
l The system ID consists of System Priority and System MAC Address. When the system
negotiates with the remote system, the system with the smallest ID has the priority to choose the
port. In this example, the system refers to the board, and the system MAC address refers to the
MAC address of the board. The factory-set MAC address is globally unique and cannot be
modified.

1. In the NE Explorer, select the NE and choose Configuration > Interface Management
> Link Aggregation Group Management from the Function Tree.
2. Click New and set the parameters in the dialog box displayed.
l You can select an Ethernet port or multiple IF boards to create an LAG group.

l You can select the ports on different boards of the same type, but not of different types,
to configure an LAG group. For example, you cannot select an Ethernet board and an
IF board to configure an LAG group.
3. Click OK.
4. Optional: Click the Port Priority tab. Set Port Priority for ports.
----End
12.8.4.2 Modifying LAG Parameters

After you create a link aggregation group (LAG), you can modify the port priority and system
priority of the links as required. In the case of the static LAG, the port with highest priority is
preferred to transmit services.
Prerequisite
The LAG must be created.
Procedure
Tree.
NOTE
The LAG where the LACP protocol is not used, such as a manual LAG, the setting of the port priority
does not take effect.
3. You can set the System Priority of a LAG as required.
1. In the NE Explorer, select the NE and choose Configuration > Interface Management
> Link Aggregation Group Management from the Function Tree.
2. Click Modify and set the parameters in the dialog box displayed.
3. Click OK.
4. Optional: Click the Port Priority tab. You can modify Port Priority for ports as required.
----End
12.8.4.3 Querying Port LACP Packet Statistics

By querying the port LACP packet statistics, you can determine the current link aggregation
state.
Prerequisite
It is only applicable to LAGs of the static aggregation mode.

Procedure
Step 1 In the case of RTN 600:
Tree.
Step 2 In the case of RTN 900: In the NE Explorer, select the NE and choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 3 Select an LAG of the static aggregation mode. Right-click the LAG and choose Link LACP
Packet Statistics. You can view the statistics in the dialog box is displayed.
----End
12.8.4.4 Querying Detailed LAG Information

By querying the LAG details, you can obtain detailed information of the current LAG.
Prerequisite
It is only applicable to LAGs of the static aggregation mode.
Procedure
Step 1 In the case of RTN 600:
Tree.
Step 2 In the case of RTN 900: In the NE Explorer, select the NE and choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 3 Select an LAG of the static aggregation mode. Right-click the LAG and choose Link
Aggregation Group Details. You can view the information in the dialog box is displayed.
----End

Operation Guide for RTN NE Management 13 Configuring SDH/PDH Services
13 Configuring SDH/PDH Services
About This Chapter
The SDH/PDH services are classified into point-to-point services and SNCP services according
to the cross-connection mode.
13.1 Numbering Schemes for SDH Timeslots
Two numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines or
SDH radio links.
13.2 Configuring E1 Services
This topic describes how to configure the E1 services according to the service requirements.
13.3 Configuring Cross-Connections
When you configure microwave services, you need to configure cross-connections for each
station that the services pass through, according to the service direction.
13.4 Configuring SNCP Services
SNCP services can be dual-fed and selectively received and are applicable for protecting services
across subnets. When configuring microwave services on a per-NE basis, you can create SNCP
services to protect services across subnets.
13.5 Converting Between SNCP and Non-Protection Services
During network expansion or handover, you may need to change the type of a protection ring
or the protection type of services. This function is used for quick conversion between SNCP
services and non-protection services.
13.6 Configuring Overhead Bytes
This topic describes how to configure overhead bytes. Normally, the default values of the
overhead bytes to be received or transmitted are adopted to meet the relevant requirements. In
certain cases, however, the overhead bytes to be received or transmitted need to be modified.
13.7 Configuration Example (Hop Between Two IDU 620s)
entire process of configuring the parameters of each NE according to SDH/PDH service
requirements. This topic provides examples for configuring the OptiX RTN 600 (IDU 605) in
the two common networking modes.

13 Configuring SDH/PDH Services Operation Guide for RTN NE Management
This section describes how to plan the service parameters and complete the entire process of
configuring the parameters of each NE according to E1 service requirements, through an
example.
13.9 Configuration Example (Hop between the IDU 605 and the IDU 620)
example.

13.1 Numbering Schemes for SDH Timeslots

Two numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines or
SDH radio links.
VC-12 Timeslot Numbering

Two numbering schemes are applicable to SDH optical/electrical lines or SDH radio links when
you create cross-connections.
l By order
This timeslot numbering scheme is also considered as timeslot scheme, where the
numbering formula is as follows: VC-12 number = TUG-3 number + (TUG-2 number - 1)
x 3 + (TU-12 number -1) x 21.
This scheme is the numbering scheme recommended by ITU-T G.707, which is the default
scheme adopted by the OptiX equipment.
l Interleaved scheme
This timeslot numbering scheme is also considered as line scheme, where the numbering
formula is as follows: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number -1) x
3 + TU-12 number.
The OptiX equipment can adopt this scheme when it interconnects with the equipment that
adopts the interleaved scheme or when specific timeslot numbering scheme is required.
Figure 13-1 Numbering VC-12 timeslots by order

TUG-2
1 2 3 4 5 6 7
1 4 7 10 13 16 19 1
1
{ 22
43
25
46
28
49
31
52
34
55
37
58
40
61
2
3
1
{
2 5 8 11 14 17 20
TUG-3 TU-12
2 23 26 29 32 35 38 41 2
44 47 50 53 56 59 62 3
3 6 9 12 15 18 21 1
3
{ 24
45
27
48
30
51
33
54
36
57
39
60
42
63
2
3

Figure 13-2 Numbering VC-12 timeslots in the interleaved scheme

TUG-2
1 2 3 4 5 6 7
1 4 7 10 13 16 19 1
1
{ 2
3
5
6
8
9
11
12
14
15
17
18
20
21
2
3
1
{
22 25 28 31 34 37 40
TUG-3 TU-12
2 23 26 29 32 35 38 41 2
24 27 30 33 36 39 42 3
43 46 49 52 55 58 61 1
3
{ 44
45
47
48
50
51
53
54
56
57
59
60
62
63
2
3
VC-3 Timeslot Numbering

A VC-3 timeslot number corresponds to a TUG-3 number. If you need to configure VC-3 cross-
connections and VC-12 cross-connections in a VC-4 path at the same time, note that the timeslots
in the TUG-3 that are occupied by the VC-3 cross-connections cannot be configured for VC-12
cross-connections.
13.2 Configuring E1 Services

This topic describes how to configure the E1 services according to the service requirements.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explore. Choose Configuration > Cross-
Connection Configuration.
Step 2 Select the used E1 port.

Step 3 Click Apply.
----End
Parameters
Parameter Value Default Value Frequency of Recurrence
l E1-1 to E1-5 Selected, Not Selected l An E1 port corresponds to a microwave

(IDU 605 1A) Selected E1 timeslot, that is, E1-1 corresponds to
l E1-1 to E1-16 the first E1 timeslot in the microwave
(IDU 605 1B/ and E1-2 corresponds to the second E1
2B) timeslot. Hence, if the microwave
capacity is 2xE1, 5xE1, or 10xE1, only
l E1-1 to E1-16 the service over the first two E1 ports,
(IDU 605 1F/2F) the first five E1 ports, or the first ten E1
l The number of ports is transmitted over microwave.
E1 ports is l The system does not monitor the E1
related to the services of the ports that are not selected.
Hybrid/AM The E1 services, however, are still
attribute (IDU transmitted over microwave.
605 1F/2F).
l Set the parameters according to the
working mode of the radio link and the
used E1 port.
l In the case of the IDU 605 1F/2F, you
can set the number of E1 ports to be the
same as E1 Capacity.

13.3 Configuring Cross-Connections

When you configure microwave services, you need to configure cross-connections for each
station that the services pass through, according to the service direction.
For OptiX RTN 605
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > SDH Service Configuration from
the Function Tree.
Step 2 Optional: Click Query to query the cross-connection services from the NE.
Step 3 Select the E1 ports of the service, click Apply.
----End
For OptiX RTN 6x0
Procedure
the Function Tree.
Step 3 Click New and the Create SDH Service dialog box is displayed.
Step 4 Set the Level, the Direction, the source and the sink of the service.
Step 5 Click OK.
----End

Sample Configuration
In Figure 13-3, NE1, NE2, NE3 and NE4 comprise an unprotected chain. Services are
transmitted by microwave between NE1 and NE2, and NE3 and NE4. Services are transmitted
by fiber between NE2 and NE3.
Figure 13-3 Chain network
NE1 NE2 NE3 NE4
Two point-to-point bidirectional E1 services are transmitted between NE1 and NE2. The services
use the first and the second VC12 timeslot of a tributary board, and the first and the second VC12
timeslot of an intermediate frequency board.
Two bidirectional E1 services are transmitted between NE1 and NE4. The services use the third
and the fourth VC12 timeslots of the tributary board, the third and the fourth VC12 timeslots of
the intermediate frequency board, and the third and the fourth VC12 timeslots in the first VC4
of a line board.
The service flow of the E1 services between NE1 and NE2 is as follows: E1tributary board
at NE1intermediate frequency board at NE1intermediate frequency board at NE2
tributary board at NE2
The service flow of the E1 services between NE1 and NE4 is as follows: E1tributary board
at NE1intermediate frequency board at NE1intermediate frequency board at NE2
line board at NE2line board at NE3intermediate frequency board at NE3
intermediate frequency board at NE4tributary board at NE4
According to the service flow, you need to perform the configuration as follows:
l Configure add or drop VC12 services for NE1. The source and the sink timeslots of the
bidirectional services between the tributary board and the intermediate frequency board
range from 1 to 4.
bidirectional services between the intermediate frequency board and the tributary board
range from 1 to 2.
l Configure pass-through VC12 services for NE2. The source and the sink timeslots of the
bidirectional services between the intermediate frequency board and the line board range
from 3 to 4.
l Configure pass-through VC12 services for NE3. The source and the sink timeslots of the
bidirectional services between the line board and the intermediate frequency board range
from 3 to 4.
range from 3 to 4.
13.3.1 Creating Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service

sink.
13.3.2 Creating Cross-Connections for SNCP Services
13.3.3 Setting the Automatic Switching Conditions of SNCP Services
13.3.4 Deleting the Cross-Connections of a Point-to-Point Service
When a point-to-point service is not used, you can delete the cross-connections of this service
to release the corresponding resources.
13.3.5 Deleting the Cross-Connections of a Service
When a service is not used, you can delete the cross-connections of this service to release the
corresponding resources.
13.3.1 Creating Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service
sink.
Prerequisite
l The source and sink boards must be configured.
Procedure
Step 2 Optional: Click Options. Then, select Interleaved or Complete Service to change the VC-12
timeslot numbering policy used by the cross-connection.
Then, the Create SDH Service dialog box is displayed.
Step 4 Configure the cross-connections of the service.

Step 5 Click OK.

NOTE
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation
may fail due to the limited number of licenses.
l The calculation of the required number of licenses is based on the total number of service timeslots of
all the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3
or VC-4 services, the VC-3 or VC-4 services need to be converted into E1 services that have the same
capacity. For example, the cross-connections of one E3 service from a PL3 board to an IF board require
the number of licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards
requires the number of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards
to one PO1 board require the number of licenses that are used for 16xE1.
----End
13.3.2 Creating Cross-Connections for SNCP Services

Prerequisite
The boards where the source and the sink are must be configured.
Context
l The MSP line can work only as the service sink of an SNCP service pair and cannot work
as the working source or the protection source.
l The radio link with the 1+1 protection configuration can work only as the service sink of
l The radio link with the XPIC configuration can work only as the service sink of an SNCP
l The Hybrid radio link can work only as the service sink of an SNCP service pair, and cannot

Procedure
Step 2 Click Options. Then, select Interleaved or Complete Service to change the VC-12 timeslot
numbering policy used by the cross-connection.
Step 3 Click Create SNCP.
The system displays the Create SNCP Service dialog box.
service.
NOTE
l Adhere to the following principles when planning the trails:

l Do not overlap the working SNC and the protection SNC if possible.
l The OptiX RTN 600 does not support the line with the MSP, 1+1 protection configuration or N+1
protection configuration as the working source or the protection source of SNCP.
l It is recommended that the working SNC uses the line ports of one line board and the protection SNC uses
those of another line board to prevent the situation in which the failure of a line board causes the protection
to fail.
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to
twelve minutes. It is recommended that you set the value to ten minutes.
Step 5 Click OK.

NOTE
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may
fail due to the limited number of licenses.
l The calculation of the required number of licenses is based on the total number of service timeslots of all
the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4
services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For
example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of
licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number
of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require
the number of licenses that are used for 16xE1.
----End
Parameters
Service Type SNCP SNCP -
Level VC12, VC3, VC4 VC12 l Specifies the level of the cross-
connection to be created.
l If the service is an E1 service or a data
l If the service is an E3/T3 service or a data
l If all the services in a VC-4 pass through
the NE, set this parameter to VC4.

restored to normal.


Bidirectional Unidirectional, only the cross-
direction are created.
Bidirectional, both the cross-
direction and the cross-connections in
the SNCP transmit direction are created.
parameter to Bidirectional.

the delay.
default value.



3, 4, 5, and 6.


3, 4, 5, and 6.
Configure SNCP Checked, Unchecked After you select the Configure SNCP
Tangent Ring Unchecked Tangent Ring check box, you can configure
the SNCP services on tangent points of
SNCP rings in a fast manner.
Generally, it is not recommended to select
this check box.

Activate Yes, No Yes Sets whether to immediately activate the

Immediately cross-connection that is configured.
If you need to immediately deliver the cross-
connection that is configured to NEs, set the
value of this parameter to Yes.
Postrequisite
If Direction is set to Unidirectional, the cross-connection only in the SNCP receive direction
is created. Hence, you need to configure a unidirectional cross-connection between the service
and the working trail, and later, a unidirectional cross-connection between the service and the
protection trail.
13.3.3 Setting the Automatic Switching Conditions of SNCP

Services
Prerequisite
An SNCP protection group at the VC-4 level must be configured.
Procedure
Configuration > SNCP Service Control from the Function Tree.
Step 2 Select the SNCP protection group. Double-click Initiation Condition to which the working
Step 3 Select SD switching conditions. Then, click OK.
Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protection

Step 5 Repeat Step 3.

Step 6 Click Apply.
The system displays a prompt box asking you whether to carry out the switching.
Step 7 Click Yes.
----End
Parameters
UNEQ Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the HP_UNEQ alarm
as an SD switching condition.
default value.
TIM Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the HP_TIM alarm as
default value.
SD Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the B3_SD alarm as an
SD switching condition.
default value.
EXC Selected, Not Not selected l When this item is selected, the SNCP
selected service considers the B3_EXC alarm as
default value.
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation
Condition of the protection service.
13.3.4 Deleting the Cross-Connections of a Point-to-Point Service

When a point-to-point service is not used, you can delete the cross-connections of this service
Prerequisite
The cross-connections of the point-to-point service must be configured and the point-to-point
service is not used.

Procedure
Step 2 Query the data.

1. Click Query.
at the NE and update service date at the NM. Are you sure to continue?.
2. Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
3. Click Close.
Step 3 Select the cross-connection of the point-to-point service that needs to be deleted in Cross-
Connection.
Step 4 Deactivate the service.

1. Click Deactivate.
Then, the Confirm dialog box is displayed, prompting Are you sure to deactivate all
selected services (only for activated services)?.
2. Click OK. Another Confirm dialog box is displayed, prompting This services of the NE
will be cleared by this operation. Are you sure to continue?.
3. Click OK.
4. Click Close.
Step 5 Delete the service.

1. Click Delete.
Then, the Confirm dialog box is displayed, prompting Are you sure to delete all the
selected services (only for inactive services)?.
2. Click OK.
3. Click Close.
Step 6 Click Query.

At this time, the cross-connection of the point-to-point service is already deleted.
----End
13.3.5 Deleting the Cross-Connections of a Service

When a service is not used, you can delete the cross-connections of this service to release the
corresponding resources.
Prerequisite
The cross-connections of the service must be configured and the service is not be used.

Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > SDH Service
1. Click Query.
2. Click OK.
3. Click Close.
Step 3 Select the cross-connection of the SNCP service that needs to be deleted in Cross-
Connection.
selected services (only for activated services?).
3. Click OK.
4. Click Close.
1. Click Delete.
Then, the OK dialog box is displayed, prompting Are you sure to delete all the selected
services (only for inactive services)?.
2. Click OK.
3. Click Close.
Step 6 Click Query.
At this time, the cross-connection of the SNCP service is already deleted.
----End
13.4 Configuring SNCP Services

SNCP services can be dual-fed and selectively received and are applicable for protecting services
across subnets. When configuring microwave services on a per-NE basis, you can create SNCP
services to protect services across subnets.
Procedure
the Function Tree.

Step 3 Click Create SNCP and the Create SNCP Service dialog box is displayed.
Step 4 Set the Service Type, Level, Revertive Mode, Direction, Hold-off Time and WTR Time. Set
the Working Service and Protection Service of SNCP.
Step 5 Click OK.
----End
Sample Configuration
In Figure 13-4, NE1, NE2, NE3 and NE4 comprise a unidirectional SNCP ring, and NE4 and
NE5 comprise a unprotected chain. The SNCP ring transmits services by fiber, and the
unprotected chain transmits services by microwave.

Figure 13-4 SNCP ring with unprotected chain
NE 1
West East
West East
STM-1
NE 2 NE 4 NE 5
SNCP Ring
East West
West East
NE 3
Four bidirectional E1 services are transmitted between NE1 and NE5. The services use the first
through fourth VC12 timeslots of a tributary board, the first through fourth VC12 timeslots of
an intermediate frequency board, and the first through fourth VC12 timeslots in the first VC4
of a line board.
The E1 services are bidirectional. The service from NE1 to NE5 and the service from NE5 to
NE1 use diverse routes.
l When the network is normal, the service flow between NE1 and NE5 is as follows: E1
tributary board at NE1east line board at NE1west line board at NE2east line board
at NE2west line board at NE3east line board at NE3west line board at NE4
intermediate frequency board at NE4intermediate frequency board at NE5tributary
board at NE5
l When the network is normal, the service flow between NE5 and NE1 is as follows: E1
tributary board at NE5intermediate frequency board at NE5intermediate frequency
board at NE4east line board at NE4west line board at NE1tributary board at NE1
According to the service flow, you need to perform the configuration as follows:
l Configure add or drop VC12 services for NE1. Configure a bidirectional SNCP service,
and select a east line board as the source of Working Service, an west line board as the
source of Protection Service, and a tributary board as the sink. The source and the sink
timeslots range from 1 to 4.
l Configure pass-through VC12 services for NE2. Configure bidirectional services between
the west and the east line boards. The source and the sink timeslots range from 1 to 4.
l Configure pass-through VC12 services for NE3. Configure bidirectional services between
the west and the east line boards. The source and the sink timeslots range from 1 to 4.
l Configure add or drop VC12 services for NE4. Configure a bidirectional SNCP service,
and select a west line board as the source of Working Service, an east line board as the
source of Protection Service, and an intermediate frequency board as the sink. The source
and the sink timeslots range from 1 to 4.

range from 1 to 4.
13.5 Converting Between SNCP and Non-Protection

Services
During network expansion or handover, you may need to change the type of a protection ring
or the protection type of services. This function is used for quick conversion between SNCP
services and non-protection services.
13.5.1 Converting Non-Protection Services into SNCP Services

13.5.2 Converting SNCP Services into Non-Protection Services
13.5.1 Converting Non-Protection Services into SNCP Services

Prerequisite
The unidirectional cross-connection of non-protection services must be configured and the

source of the cross-connection must be a line board.
When this task is performed to convert a non-protection service into an SNCP service, the
Procedure
Step 2 Optional: Query the data.

1. Click Query.
at the NE and update service data at the NM. Are you sure to continue?.
2. Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation Succeeded.

3. Click Close.
Step 3 Select the bidirectional cross-connection of the non-protection service in Cross-connection.
Then, right-click and choose Expand to Unidirectional from the shortcut menu.
Step 4 Select the unidirectional cross-connection of the normal service in Cross-connection. Then,
right-click and choose Convert to SNCP from the shortcut menu.
Then, the Confirm dialog box is displayed, prompting If the non-protection service is convert
into a SNCP service, the service may be interrupted. Are you sure to continue?.
Step 5 Click OK.
service.
Step 7 Click OK.
----End

Parameters

restored to normal.

the delay.
default value.



3, 4, 5, and 6.


3, 4, 5, and 6.
Postrequisite
The SNCP service after the conversion is the SNCP service only in the receive direction. Later,
you need to configure a unidirectional cross-connection between the service and the working
trail, and a unidirectional cross-connection between the service and the protection trail. The non-

protection service can be converted into the SNCP service both in the receive direction and the
transmit direction only after the configuration.
13.5.2 Converting SNCP Services into Non-Protection Services

Prerequisite
The current service is transmitted in the working path.
The SNCP cross-connection in the receive direction must be configured.
When this task is performed to convert an SNCP service into a non-protection service, the
Procedure
Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection. Right-click and
choose Convert to Non-Protection Service from the shortcut menu.
Step 3 Choose Working or Protection from the displayed menu.
Step 4 Then, the Prompt dialog box is displayed, prompting If the SNCP service is converted into a
non-protection service, the service may be interrupted. Are you sure to continue?.
Step 5 Click OK.
----End
Postrequisite
You need to delete the unidirectional cross-connection between the service and the working path
or the unidirectional cross-connection between the service and the protection path. The SNCP
service can be converted into the non-protection service both in the receive direction and the
transmit direction only after the deletion.
13.6 Configuring Overhead Bytes

This topic describes how to configure overhead bytes. Normally, the default values of the
overhead bytes to be received or transmitted are adopted to meet the relevant requirements. In
certain cases, however, the overhead bytes to be received or transmitted need to be modified.
13.6.1 Configuring RSOHs

This topic describes how to configure the J0 byte in the regenerator section overheads when the
J0_MM alarm is reported at the local or remote NE.

13.6.2 Configuring VC-4 POHs

This section describes how to configure the J1 byte or C2 byte in the VC-4 path overheads
(POHs) when the HP_TIM or HP_SLM alarm is reported on the line board at the local or remote
NE.
You need to configure the J1 or C2 byte in the VC-3 path overheads, when the E3/T3 interface
board on the local or opposite NE reports the LP_TIM or LP_SLM alarm or when the Ethernet
board on the local or opposite NE reports the LP_TIM_VC3 or LP_SLM_VC3 alarm.
You need to configure the signal indicator of the J2 or V5 byte in the VC-12 path overheads,
when the E1 interface board on the local or opposite NE reports the LP_TIM or LP_SLM alarm
or when the Ethernet board on the local or opposite NE reports the LP_TIM_VC12 or
LP_SLM_VC12 alarm.
13.6.1 Configuring RSOHs

This topic describes how to configure the J0 byte in the regenerator section overheads when the
J0_MM alarm is reported at the local or remote NE.
Prerequisite
The required SDH interface boards must be added.
Procedure
Step 1 Select the SDH interface board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > Regenerator Section Overhead from the
Function Tree.
Step 2 Set the J0 byte.

1. Double-click the parameter to be modified.
Then, the Please Input Overhead Byte dialog box is displayed.
2. Set the overhead byte.
3. Click OK.

Step 3 Click Apply.

Then, a prompt box is displayed. Confirm the operations in this prompt box.
Step 4 Click OK.
----End
Parameters
J0 to Be Sent - [16 Byte]HuaWei l Two byte modes are supported: single

([Mode]Content) SBS byte mode and 16-byte mode (the first
byte is generated automatically).
l If the remote NE reports the J0_MM
alarm, set this parameter according to the
J0 byte to be received at the remote NE.
J0 to Be Received - Disable l Three byte modes are supported: single

([Mode]Content) byte mode, 16-byte mode (the first byte
is generated automatically), and disable
mode.
l When this parameter is set to Disable
Mode, the board does not detect the
received J0 byte.

This section describes how to configure the J1 byte or C2 byte in the VC-4 path overheads
(POHs) when the HP_TIM or HP_SLM alarm is reported on the line board at the local or remote
NE.
Prerequisite
The required line boards must be added.
Procedure
Step 1 Select the line board from the Object Tree in the NE Explorer. Choose Configuration >
Overhead Management > VC4 Path Overhead from the Function Tree.
Step 2 Optional: Set the J1 byte.
1. Click the Trace Byte J1 tab.

4. Click OK.
5. Click Apply.
6. Click OK.
Step 3 Optional: Set the C2 byte.

1. Click the Signal Flag C2 tab.
2. Set the C2 byte.
3. Click OK.
4. Click Apply.
Step 4 Optional: Set the termination mode of the VC-4 POHs.

1. Click the Overhead Termination tab.
2. Set the termination mode of the VC-4 POHs.
3. Click Apply.
4. Click OK.
----End

Parameters
J1 to Be Sent - [16 Byte]HuaWei l Three byte modes are supported: single

([Mode]Content) SBS byte mode, 16-byte mode (the first byte
is generated automatically), and 64-byte
mode (synchronization bit 0x0D, 0x0A).
l If the remote NE reports the HP_TIM
alarm, set this parameter according to the
J1 byte to be received at the remote NE.
J1 to Be Received - Disable l Three byte modes are supported: 16-byte

([Mode]Content) mode (the first byte is generated
automatically), 64-byte mode
(synchronization bit 0x0D, 0x0A), and
disable mode.
received J1 byte.
C2 to Be Sent (0x00)Unequipped, (0x02) TUG If the remote NE reports the HP_SLM

(0x01)Reserved, Structure alarm, set this parameter according to the C2
(0x02) TUG byte to be received at the remote NE.
Structure, (0x03)
Locked TU-n,
(0x04)34M/45M
into C-3, (0x05)
Experimental
Mapping, (0x12)
140M into C-4
asynchronization,
(0x13)ATM
Mapping, (0x14)
MAN DQDB
Mapping, (0x15)
FDDI Mapping,
(0x16)HDLC/PPP
Mapping, (0x17)
Reserved for Special
Purpose, (0x18)
HDLC/LAPS
Mapping, (0x19)
Purpose, (0x1A)
10G Ethernet
Frame, (0x1B)GFP
Mapping, (0xCF)
Reserved, (0xE1)
Reserved, (0xFC)
Reserved, (0xFE)O.

C2 to Be Received 181 Test Signal, If the local NE reports the HP_SLM alarm,
(0xFF)VC-AIS set this parameter according to the C2 byte
to be transmitted from the remote NE.
VC4 Overhead Auto, Pass- Auto l When this parameter is set to Pass-
Termination Through, Through, the local NE detects the VC-4
Termination overheads (the C2 byte is not detected)
and then forwards the original
overheads.
Termination, the local NE detects the
VC-4 overheads (the C2 byte is not
detected) and then generates new VC-4
overheads according to the board
settings.
l When this parameter is set to Auto, the
VC-4 overhead termination of VC-4
pass-through services is Pass-Through
and the overhead termination of the
VC-3/VC-12 services is Termination.


You need to configure the J1 or C2 byte in the VC-3 path overheads, when the E3/T3 interface
board on the local or opposite NE reports the LP_TIM or LP_SLM alarm or when the Ethernet
board on the local or opposite NE reports the LP_TIM_VC3 or LP_SLM_VC3 alarm.
Prerequisite
The corresponding E3/T3 interface board or Ethernet board must be added.
Procedure
Step 1 Select the E3/T3 interface board or Ethernet board from the Object Tree in the NE Explorer.
Choose Configuration > Overhead Management > VC3 Path Overhead from the Function
Tree.
4. Click OK.
5. Click Apply.
6. Click OK.
Step 3 Optional: Set the C2 byte.
1. Click the Signal Flag C2 tab.
2. Set the C2 byte.

3. Click OK.
4. Click Apply.
----End
Parameters
J1 to Be Sent - [16 Byte]HuaWei l Three byte modes are supported: single

([Mode]Content) SBS byte mode, 16-byte mode (the first byte
is generated automatically), and 64-byte
mode (synchronization bit 0x0D, 0x0A).
l If the remote NE reports the LP_TIM or
LP_TIM_VC3 alarm, set this parameter
according to the J1 byte to be received at
the remote NE.

disable mode.
received J1 byte.
C2 to Be Sent (0x00)Unequipped, (0x04)34M/45M If the remote NE reports the LP_TIM or

(0x01)Reserved, into C-3 (E3/T3 LP_TIM_VC3 alarm, set this parameter
(0x02) TUG interface boards) according to the C2 byte to be received at
Structure, (0x03) (0x02) TUG the remote NE.
Locked TU-n, Structure (Ethernet
(0x04)34M/45M boards)
into C-3, (0x05)
Experimental
Mapping, (0x12)
140M into C-4
asynchronization,
(0x13)ATM
Mapping, (0x14)
MAN DQDB
Mapping, (0x15)
FDDI Mapping,
(0x16)HDLC/PPP
Mapping, (0x17)
Purpose, (0x18)
HDLC/LAPS
Mapping, (0x19)

C2 to Be Received Reserved for Special If the local NE reports the LP_TIM or

Purpose, (0x1A) LP_TIM_VC3 alarm, set this parameter
10G Ethernet according to the C2 byte to be transmitted
Frame, (0x1B)GFP from the remote NE.
Mapping, (0xCF)
Reserved, (0xE1)
Reserved, (0xFC)
Reserved, (0xFE)O.
181 Test Signal,
(0xFF)VC-AIS

You need to configure the signal indicator of the J2 or V5 byte in the VC-12 path overheads,
when the E1 interface board on the local or opposite NE reports the LP_TIM or LP_SLM alarm
or when the Ethernet board on the local or opposite NE reports the LP_TIM_VC12 or
LP_SLM_VC12 alarm.
Prerequisite
The corresponding E1 interface board or Ethernet board must be added.
Procedure
Step 1 Select the E1 interface board or Ethernet board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.



4. Click OK.
5. Click Apply.
6. Click OK.
Step 3 Optional: Set the signal flag.
1. Click the Signal Flag tab.
2. Set the signal flag in the V5 byte.
3. Click Apply.
4. Click OK.
----End
Parameters
J2 to Be Sent - [16 Byte]HuaWei l Two byte modes are supported: single

([Mode]Content) SBS byte mode and 16-byte mode (the first
byte is generated automatically).
l If the remote NE reports the LP_TIM or
LP_TIM_VC3 alarm, set this parameter
according to the J1 byte to be received at
the remote NE.


disable mode.
received J2 byte.
V5 to Be (0x00)Unequipped (0x02) If the remote NE reports the LP_SLM or

Transmitted or Supervisory- Asynchronous LP_SLM_VC3 alarm, set this parameter
Unequipped, (0x01) according to the V5 byte to be received at
Equipped-Non- the remote NE.
Specific Payload,
V5 to Be Received (0x02) If the local NE reports the LP_SLM or
Asynchronous, LP_SLM_VC3 alarm, set this parameter
(0x03)Bit according to the V5 byte to be transmitted
Synchronization, from the remote NE.
(0x04)Byte
Synchronization,
(0x05)Retained
Signal Flag, (0x06)
O.181 Test Signal,
(0x07)VC_AIS

entire process of configuring the parameters of each NE according to SDH/PDH service
requirements. This topic provides examples for configuring the OptiX RTN 600 (IDU 605) in
the two common networking modes.

13.7.3 Configuring NE1
This topic describes how to configure the data of NE1 based on the parameters of the service
planning, by using the NMS.

This topic describes how to configure the microwave service data of NE2 based on the parameters
of the service planning, by using the NMS.
NE5 is the OptiX RTN 600 that adopts the IDU 605. Therefore, the configuration of NE5 is not
contained in this manual.

Figure 13-5 shows a tree network. Basic information of this network is as follows:
l NE1, NE2, and NE3 are the OptiX RTN 600 that is configured with IDU 620.
l NE4 is the OptiX RTN 600 that is configured with IDU 610.
l NE5 is the OptiX RTN 600 that is configured with IDU 605 1B.
l The E1 services need to be converged from each NE to the STM-1 optical line board at the
client side. Table 13-1 lists the service requirements.

NE1 NE2 NE4
SDH
OptiX RTN 600 OptiX RTN 600 OptiX RTN 600

(IDU 620) (IDU 620) (IDU 610)
NE3 NE5
OptiX RTN 600 OptiX RTN 600

(IDU 620) (IDU 605 1B)

Table 13-1 Service requirements

Source Sink
NE1 NE2 NE3 NE4 NE5
STM-1 optical line 8xE1 8xE1 8xE1 20xE1 2xE1

board at the client
side

In the following example, the engineering planning covers all the information required for
configuring NE1-NE5.
NE Attributes
Parameter NE1 NE2 NE3 NE4 NE5
Equipment IDU 620 IDU 620 IDU 620 IDU 610 IDU 605
Type
NE ID 101 102 103 104 105
Extended ID 9 (the same 9 (the same 9 (the same 9 (the same 9 (the same
as the default as the default as the default as the default as the default
value) value) value) value) value)
NE IP 129.9.0.101 129.9.0.102 129.9.0.103 129.9.0.104 129.9.0.105
Planning the Radio Link

All the ODUs adopted by the OptiX RTN 600 on the tree network work at subband A of the 15
GHz frequency band with the T/R spacing of 420 MHz, thus decreasing the types of the required
spare parts.

Figure 13-6 Planning the radio link

NE4
(IDU 610)
NE1 V-polarization NE2

14547MHz
(IDU 620) (IDU 620)
Tx Low Tx Hi
14967MHz
Tx Hi 14930 MHz
V-polarization
14510 MHz
Tx Low Tx Low
14532 MHz V-polarization
NE3 NE5
14952 MHz (IDU 620) (IDU 605)
H-polarization Tx Hi 14930 MHz

Tx Hi
14510 MHz
Tx Low
Table 13-2 Planning information of the radio link

Parameter Link 1 Link 2 Link 3 Link 4
TX High NE1 NE3 NE4 NE3
TX Low NE2 NE2 NE2 NE5
Transmit Frequency 14930 14952 14967 14930

of TX High Station
(MHz)
Transmit Frequency 14510 14532 14547 14510

of TX High Station
(MHz)
T/R Spacing (MHz) 420 420 420 420
Radio Work Mode STM-1, 28MHz, 16E1, 14MHz, 22E1, 14MHz, 2E1, 3.5MHz,
128QAM 16QAM 32QAM QPSK
Link Protection 1+1 1+0 1+0 1+0

Mode
Polarization V (vertical H ((horizontal V (vertical V (vertical

Directiona polarization) polarization) polarization) polarization)
NOTE
a: Information other than the polarization direction, which is not related to the link planning is not provided in this section.

Figure 13-7 IDU board configuration (NE1)
EXT
IF1A Slot7 EXT Slot8
EXT
IF1A Slot5 EXT
SL1 Slot6
FAN
FAN
PXC
PXC Slot3 EXT
PO1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
EXT
IF1A Slot7 IF1A
EXT Slot8
EXT
IF1A Slot5 EXT
IF1A Slot6
FAN
FAN
PXC
PXC Slot3 EXT
PO1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
EXT
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PO1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
PD1 Slot3 IF1A Slot4
PXC Slot1 SCC Slot2
PW SCC EOW PF1 IF0

Slot 1 Slot 2 Slot 3 Slot 4 Slot 8

NOTE
The ODU that is connected to the IF board in slot n occupies logical slot 10+n. The logical slot of the ODU is
not displayed in the board configuration diagram. In the case of the IDU 620, n ranges from 5 to 8. In the case
of the IDU 610, n is fixed to 4. In the case of the IDU 605, n can be 7 or 8.
Attributes of the IF 1+1 Protection
Table 13-3 Attributes of the IF 1+1 protection

Parameter NE1 NE2
Protection Group ID 1 1
Protection Type HSB (default value) HSB (default value)
Working Slot Slot 5 Slot 5
Protection Slot Slot 7 Slot 7
Revertive Mode Revertive (default value) Revertive (default value)
WTR Time 600s (default value) 600s (default value)
Enable Reverse Switching Enabled (default value) Enabled (default value)
Information of IF Ports
Table 13-4 Information of IF ports (NE1 and NE2)

Parameter NE1 NE2
5-IF1A (7-IF1A) 5-IF1A (7-IF1A) 6-IF1A 8-IF1A
IF Radio Work Work Mode: 7 Work Mode: 7 Work Mode: 6 Work Mode: 10
Attri Mode Service Capacity: Service Capacity: Service Capacity: Service Capacity:
butes STM-1 STM-1 16xE1 22xE1
Signal Bandwidth: Signal Bandwidth: Signal Bandwidth: Signal Bandwidth:
28 MHz 28 MHz 14 MHz 14 MHz
Modulation: Modulation: Modulation: Modulation:
128QAM 128QAM 16QAM 32QAM
Radio Link ID 101 101 102 103
Wayside Enable Enabled Enabled Not supported Not supported

Status
Wayside Input Slot 1 Slot 1 - -

Board
ATP Enable Status Enabled Enabled Enabled Enabled

C

Parameter NE1 NE2
5-IF1A (7-IF1A) 5-IF1A (7-IF1A) 6-IF1A 8-IF1A
ATPC Automatic Enabled Enabled Enabled Enabled

Threshold Enable
Status
Table 13-5 Information of IF ports (NE3, NE4, and NE5)

5-IF1A 7-IF0A 5-IF1A 8-IF0
IF Radio Work Work Mode: 6 Work Mode: 18 Work Mode: 10 Work Mode: 18
Attri Mode Service Capacity: Service Capacity: Service Capacity: Service Capacity:
butes 16xE1 2xE1 22xE1 2xE1
Signal Bandwidth: Signal Bandwidth: Signal Bandwidth: Signal Bandwidth:
14 MHz 3.5 MHz 14 MHz 3.5 MHz
Modulation: Modulation: Modulation: Modulation:
16QAM QPSK 32QAM QPSK
Radio Link ID 102 104 103 104
Wayside Enable Not supported Not supported Not supported Not supported
Status
Wayside Input - - - -
Board
ATP Enable Status Enabled Enabled Enabled Enabled

C
ATPC Automatic Enabled Enabled Enabled Enabled
Threshold Enable
Status
Information of ODU Ports
Table 13-6 Information of ODU ports (NE1 and NE2)

Parameter NE1 NE2
15-ODU (17- 15-ODU (17- 16-ODU 18-ODU

ODU) ODU)
Radio Transmission 14930 14510 14532 14547

Frequency Frequency
Properties (MHz)

Parameter NE1 NE2
15-ODU (17- 15-ODU (17- 16-ODU 18-ODU

ODU) ODU)
T/R Spacing 420 420 420 420

(MHz)
Power Transmit Power 10 10 10 10

Attributes (dBm)
Equipment Station Type TX High TX Low TX Low TX Low

Attributes (The
equipment
attributes can be
planned but
cannot be set.)
NOTE
Note: The attributes of the main and standby ODUs on NE1 and NE2 are the same.
Table 13-7 Information of ODU ports (NE3, NE4, and NE5)

15-ODU 17-ODU 15-ODU 18-ODU
Radio Transmission 14952 14930 14967 14510

Frequency Frequency
Properties (MHz)
T/R Spacing 420 420 420 420

(MHz)
Power Transmit Power 10 10 10 10

Attributes (dBm)
Equipment Station Type TX High TX High TX High TX Low

Attributes (The
equipment
attributes can be
planned but
cannot be set.)


NE1
Station
NE1
Timeslot 6-SL1
VC12: 1-8
VC4-1
4-PO1:1-8
Links-1: NE1 - NE2 - NE3 -NE5

Station
NE1 NE2 NE3 NE5
Timeslot 6-SL1 5-IF1A 5-IF1A 6-IF1A 5-IF1A 7-IF0A 8-IF0
VC12: 9-16 VC12: 9-16
4-PO1:1-8
VC12: 17-24 VC12: 17-24 VC12:1-8
VC4-1 4-SL1 4-PO1:1-8
VC12:25-26 VC12:25-26 VC12:9-10 VC12:1-2
4-SL1 4-PF1:1-2
Links-2: NE1 - NE2 - NE4

Station NE1 NE2 NE4
Timeslot 6-SL1 5-IF1A 5-IF1A 8-IF1A 5-IF1A
VC12: 27-46 VC12: 27-46 VC12: 1-20
VC4-1
4-SL1 4-PD1:1-20
Add/Drop
Foward
NOTE
On the radio links of NE3, NE4, and NE5, the E1 signals are directly mapped into the timeslots
corresponding to the PDH radio frames. Figure 13-12 considers VC-12 timeslots as an example to illustrate
how the timeslots are allocated.
Figure 13-12 shows the timeslot allocation for the services between the NEs.
l E1 services of NE1:
The services are added to/dropped from ports 1-8 of the PO1 board in slot 4 on NE1.
The E1 services occupy VC-12 timeslots 1-8 on the optical line of the SL1 board in slot
6 on NE1.
The services occupy VC-12 timeslots 9-16 on the radio link of the IF1A board in slot
5 on NE1 and on the radio link of the IF1A board in slot 5 on NE2.
The services are passed through between the IF1A board in slot 5 and the SL1 board in
slot 6 on NE1.

The services occupy VC-12 timeslots 1-8 on the radio link of the IF1A board in slot 6
on NE2 and on the radio link of the IF1A board in slot 5 on NE3.
The services are passed through between the IF1A board in slot 5 and the IF1A board
in slot 6 on NE2.
slot 6 on NE1.
The services are added to/dropped from ports 1-20 of the PD1 board in slot 4 on NE4.
in slot 8 on NE2.
slot 6 on NE1.
The services are added to/dropped from ports 1-2 of the PF1 board in slot 4 on NE5.
The services occupy VC-12 timeslots 1-2 on the radio link of the IF1A board in slot 7
on NE3 and on the radio link of the IF1A board in slot 8 on NE5.
in slot 7 on NE3.
in slot 6 on NE2.
slot 6 on NE1.

Clock Information
Figure 13-13 Clock Synchronization Scheme

NE1 NE2 NE4
SDH
6-SL1/Internal 5-IF1A/7-IF1A/ 5-IF1A/Internal

Internal
NE3 NE5
Master clock 5-IF1A/Internal 8-IF0/Internal
Table 13-8 Clock information
Cl First 6-SL1 5-IF1A 5-IF1A 5-IF1A 8-IF0

oc Clock
k Source
So
ur Second Internal 7-IF1A Internal Internal Internal
ce Clock Clock Clock Clock Clock
Source Source Source Source Source
Third - Internal - - -
Clock Clock
Source Source
Orderwire Information
Table 13-9 Orderwire information
Telephone 101 102 103 104 105

No.
Call Waiting 5 5 5 5 5
Time (s)

Orderwire 5-IF1A-1, 6- 5-IF1A-1, 6- 5-IF1A-1, 7- 5-IF1A-1 8-IF0

Port SL1-1 IF1A-1, 8- SL1-1
IF1A-1
Orderwire E1 E1 E1 E1 E1
Occupied
Bytes

This topic describes how to configure the data of NE1 based on the parameters of the service
Prerequisite
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 101

l New Extended ID: 9
Step 2 Modify the IP address of an NE.
l IP: 129.9.0.101
Step 3 Configure IF 1+1 protection.

1. In the NE Explorer, select NE1 and then choose Configuration > Link Configuration
3. Click New.
Then, the Create IF 1+1 Protection dialog box is displayed. Click OK.
Protection 1 If Protection Group ID is set to 1, it indicates the

Group ID first protection group of the NE.

Working Mode HSB In the 1+1 HSB protection mode, the equipment
provides a 1+1 hot standby configuration for the IF
board and ODU at both ends of each hop of a radio
link to realize the protection.
Revertive Mode Revertive l When this parameter is set to Revertive, the NE

that is in the switching state releases the
switching and enables the former working
channel to return to the normal state after the
WTR time (when the former working channel is
restored to normal) expires.
l In this example, this parameter adopts the default
value.
WTR Time(s) 600 l After the working path is restored to normal and
the normal state lasts for 600s, the switching
restoration occurs.
value.
Enable Reverse Enable l When the reverse switching conditions are met,
Switching the IF 1+1 protection switching occurs at the
source end.
value.
Working Board 5-IF1A-1 In the 1+1 HSB mode, the IF boards can be installed
in slots 5-8. It is recommended that you install two
Protection Board 7-IF1A-1 IF boards in a pair in slots 5 and 7 (the IF board in
slot 5 is the main board) or in slots 6 and 8 (the IF
board in slot 6 is the main board).
Step 4 Configure the IF/ODU information of a radio link.

3. Set the information about the 5-IF1A and 15-ODU on the radio link. After setting the
information about the 5-IF1A or 15-ODU on the radio link, click Apply.
Work Mode 7,STM-1,28MH -

z,128QAM
Link ID 101 l As the identifier of a radio link, this parameter

is used to prevent incorrect connection of
radio links between sites.
l In this example, the radio link ID is 101.

ATPC Enable Enabled This parameter indicates whether the ATPC

Status function is enabled. The ATPC function ensures
that the transmit power of the transmitter
automatically traces the changes of the receive
level at the receive end, within the ATPC
controlled range.
TX Frequency 14930.0 The transmit frequency needs to be set according

(MHz) to the service planning.
T/R Spacing 420.0 In this example, the spacing between the transmit
(MHz) frequency and receive frequency of the ODU is
420 MHz.
TX Power 10.0 The transmit power needs to be set according to

(dBm) the service planning.
TX Status unmute l When TX Status is set to unmute, the ODU

receives and transmits microwave signals
normally.
l In this example, this parameter adopts the
default value.
Step 5 Configure the ATPC attributes.

1. In the NE Explorer, select the 5-IF1A and then choose Configuration > IF Interface from
the Function Tree.
2. Click the IF Attributes tab. After setting the parameters, click Apply.
ATPC Enable Status Enabled This parameter indicates whether the ATPC
function is enabled. The ATPC function
ensures that the transmit power of the
transmitter automatically traces the changes of
the receive level at the receive end, within the
ATPC controlled range.
ATPC Automatic Enabled When the function is enabled, the manually set
Threshold Enable ATPC upper and lower thresholds are invalid.
Status The equipment automatically uses the preset
ATPC upper and lower thresholds based on the
Step 6 Create the cross-connections of point-to-point services.

1. In the NE Explorer, select NE1 and then choose Configuration > Cross-Connection
2. Click New. The Create SDH Service dialog box is displayed. After setting the parameters.
Then, click OK.

l Configure the cross-connections of the add/drop services as follows.

Level VC12 l In this example, VC-12 data services are

bound.
l This parameter indicates the level of the
cross-connections.
Direction Bidirectional l When Direction is set to Bidirectional,

create the cross-connections from the
service source to the service sink and from
the service sink to the service source.
default value.
Source 6-SL1 In this example, the 6-SL1 is the service source.
Source 1-8 In this example, the timeslots to which the

Timeslot service source corresponds are timeslots 1-8.
Range(e.g.
1,3-6)
Sink 4-PO1 In this example, the 4-PO1 is the service sink.
Sink Timeslot 1-8 In this example, the timeslots to which the

Range(e.g. service sink corresponds are timeslots 1-8.
1,3-6)
l Configure the cross-connections of the pass-through services as follows.


bound.
cross-connections.

default value.
Source 5-IF1A In this example, the 5-IF1A is the service

source.

Range(e.g.
1,3-6)
Sink 6-SL1 In this example, the 6-SL1 is the service sink.


1,3-6)
Step 7 Configure the orderwire.

l Phone 1: 101
l Orderwire Port: 5-IF1A-1, 6-SL1-1
Step 8 Configure the clock source.
1. In the NE Explorer, select NE1 and then choose Configuration > Clock > Clock Source
2. Click Create. The Add Clock Source dialog box is displayed. Select the clock sources.
Then, click OK.
Clock Source 6-SL1-1 In this example, the 6-SL1-1 is the clock source.
3. Select a clock source and click or to adjust the priority level of this
clock source. Set Clock Source and Clock Source Priority Sequence(1 is the highest).
Then, click Apply.
Clock 6-SL1-1 Internal In this example, the 6-SL1-1 and

Source Clock Source internal clock source are set as the
available clock sources.
Clock 1 2 l This parameter specifies the priority

Source level of a clock source.
Priority l The priority level of the 6-SL1-1
Sequence(1 clock source is 1 and the priority
is the level of the internal clock source is
highest) 2.
----End

Prerequisite


Procedure
l New ID: 102
l IP: 129.9.0.102
3. Click New.


value.
restoration occurs.
value.

source end.
value.
Working Board 5-IF1A-1 In the 1+1 HSB mode, the IF boards can be installed
Protection Board 7-IF1A-1 IF boards in a pair in slots 5 and 7 (the IF board in

3. Set the information about the 5-IF1A and 15-ODU on the first radio link, the information
about the 6-IF1A and 16-ODU on the second radio link, and the information about the 8-
IF1A and 18-ODU on the third radio link. Then, click Apply.
l Set the parameters of the 5-IF1A and 15-ODU as follows.
Work Mode 7,STM-1,28MH -

z,128QAM
Link ID 101 l As the identifier of a radio link, this

parameter is used to prevent incorrect
connection of radio links between sites.

controlled range.
TX Frequency 14510.0 The transmit frequency needs to be set

(MHz) according to the service planning.
T/R Spacing 420.0 In this example, the spacing between the

(MHz) transmit frequency and receive frequency of the
ODU is 420 MHz.



normally.
default value.

Work Mode 6,16E1,14MHz, -

16QAM


controlled range.


ODU is 420 MHz.


normally.
default value.

Work Mode 10,22E1,14MH -

z,32QAM



controlled range.


ODU is 420 MHz.


normally.
default value.

the Function Tree.

Status function is enabled. The ATPC function
transmitter automatically traces the changes
of the receive level at the receive end, within
the ATPC controlled range.
ATPC Enabled When the function is enabled, the manually

Automatic set ATPC upper and lower thresholds are
Threshold invalid. The equipment automatically uses
Enable Status the preset ATPC upper and lower thresholds
based on the working mode of the IF board.
3. Repeat Step 5.1 to Step 5.2 to set the ATPC parameters of the 6-IF1A and 8-IF1A to the
same values. Click Apply.




Then, click OK.

bound.
cross-connections.

default value.

source.

Range(e.g.
1,3-6)

1,3-6)
l Configure the cross-connections of the services that pass through NE3 as follows.


bound.
cross-connections.

default value.

source.

Range(e.g.
1,3-6)
Sink 6-IF1A In this example, the 6-IF1A is the service sink.

1,3-6)

bound.
cross-connections.

default value.

source.

Range(e.g.
1,3-6)


1,3-6)
l Phone 1: 102
l Orderwire Port: 5-IF1A-1, 6-IF1A-1, 8-IF1A-1

Then, click OK.
Clock Source 5-IF1A-1 In this example, the 5-IF1A-1 is the clock source.
7-IF1A-1 In this example, the 7-IF1A-1 is the clock source.
Then, click Apply.

er
Clock 5-IF1A-1 7-IF1A-1 Internal In this example, the 5-IF1A-1, 7-

Source Clock IF1A-1, and internal clock source
Source are set as the available clock
sources.
Clock 1 2 3 l This parameter specifies the

Source priority level of a clock
Priority source.
Sequence l The priority level of the 5-
(1 is the IF1A-1 clock source is 1. The
highest) priority level of the 7-IF1A-1
clock source is 2. The priority
level of the internal clock
source is 3.
----End


Prerequisite
Procedure
l New ID: 103
l IP: 129.9.0.103
3. Set the information about the 5-IF1A and 15-ODU on one radio link and the information
about the 7-IF0A and 17-UDU on the other radio link. Then, click Apply.
Work Mode 6,16E1,14MHz, -

16QAM


controlled range.



ODU is 420 MHz.


normally.
default value.

Work Mode 18,2E1,3.5MHz -

,QPSK


controlled range.


ODU is 420 MHz.


normally.
default value.

the Function Tree.


3. Repeat Step 4.1 to Step 4.2 to set the ATPC parameters of the 7-IF0A to the same values.
Click Apply.



1. In the NE Explorer, select NE3 and then choose Configuration > Clock > Cross-
Connection Configuration from the Function Tree.
Then, click OK.

bound.
cross-connections.


default value.

source.

Range(e.g.
1,3-6)

1,3-6)

bound.
cross-connections.

default value.

source.

Timeslot service source corresponds are timeslots 9 and
Range(e.g. 10.
1,3-6)

Range(e.g. service sink corresponds are timeslots 1 and 2.
1,3-6)


l Phone 1: 103
l Orderwire Port: 5-IF1A-1, 7-IF0A-1
Then, click OK.
Clock Source 5-IF1A-1 In this example, the 5-IF1A-1 is the clock source.
Then, click Apply.
Clock 5-IF1A-1 Internal In this example, the 5-IF1A-1 and

Source Clock Source internal clock source are set as the clock
sources.

Priority l The priority level of the 5-IF1A-1
highest) 2.
----End

Prerequisite
Procedure

l New ID: 104

l IP: 129.9.0.104
Step 3 Configuring the IF/ODU information of a radio link

3. Set the information about the 4-IF1A and 14-ODU on the radio link. Then, click Apply.
Work Mode 10,22E1,14MHz -

,32QAM


controlled range.

420 MHz.


normally.
default value.

the Function Tree.




1. In the NE Explorer, select NE4 and then choose Configuration > Cross- Connection
2. Click New. Then, the Create SDH Service dialog box is displayed. Configure the cross-
connections of the add/drop services. Click OK.

bound.
l This parameter indicates the level of the cross-
connections.
Direction Bidirectional l When Direction is set to Bidirectional, create

the cross-connections from the service source
to the service sink and from the service sink to
the service source.
default value.
Source 4-IF1A In this example, the 4-IF1A is the service source.
Source 1-20 In this example, the timeslots to which the service

Timeslot Range source corresponds are timeslots 1-20.
(e.g.1,3-6)
Sink 3-PD1 In this example, the 3-PD1 is the service sink.
Sink Timeslot 1-20 In this example, the timeslots to which the service
Range(e.g. sink corresponds are timeslots 1-20.
1,3-6)

l Phone 1: 104
l Orderwire Port: 4-IF1A-1
Then, click OK.
Clock Source 4-IF1A-1 In this example, the 4-IF1A-1 is selected as the

clock source.
Then, click Apply.
Clock 4-IF1A-1 Internal In this example, the 4-IF1A-1 and

Source Clock Source internal clock source are selected as the
clock sources.

Priority l The priority level of the 4-IF1A-1
highest) 2.
----End

NE5 is the OptiX RTN 600 that adopts the IDU 605. Therefore, the configuration of NE5 is not
contained in this manual.
For details, refer to the 13.9.4 Configuring NE5.

example.


You can configure the data of NE1 based on the parameters of the engineering planning, by
using the NMS.
You can configure the data of NE2 based on the parameters of the service planning, by using
the NMS.

Figure 13-14 shows a point to point network. The basic information of this network is as follows:
l NE1and NE2 are the OptiX RTN 600 that is configured with the IDU 605 2B.
l The service requirement between NE1 and NE2 is 12xE1.
NE1 NE2
(IDU 605 2B) (IDU 605 2B)

In the following example, the engineering planning covers all the information required for
configuring NE1 and NE2.
NE Attributes
Parameter NE1 NE2
Equipment Type IDU 605 2B IDU 605 2B
NE ID 101 102

Parameter NE1 NE2
Extended ID 9 (the same as the default 9 (the same as the default

value) value)
NE IP 129.9.0.101 129.9.0.102

GHz frequency band with the T/R spacing of 420 MHz.
NE1 V-polarization
NE2
(IDU 605 2B) (IDU 605 2B)
Tx Hi 14952 MHz
14532 MHz
Tx Low
Table 13-10 Planning information of the radio link

Parameter Link
TX High Station NE1
TX Low Station NE2
Transmit Frequency of TX High Station (MHz) 14952
Transmit Frequency of TX Low Station (MHz) 14532
T/R Spacing (MHz) 420
Work Mode 16E1,28MHz,QPSK
Link Protection Mode 1+1 HSB
Polarization Directiona V (vertical polarization)
NOTE

Board Configuration
Figure 13-16 IDU board configuration (NE1 and NE2)
IDU 605 2B
PW SCC EOW PH1 IF0 IF0

Slot 1 Slot 2 Slot 3 Slot 4 Slot 7 Slot 8
NOTE
not displayed in the board configuration diagram. In the case of the IDU 605, n can be 7 or 8.
Parameter NE1 NE2
Protection group ID 1 1
Active board Slot 8 Slot 8
Protection board Slot 7 Slot 7
Recovery time 600s (default value) 600s (default value)
Information of IF Ports
Table 13-12 Information of IF ports
Parameter NE1 NE2
8-IF0 (7-IF0) 8-IF0 (7-IF0)
IF Radio Work Mode Work Mode: 5 Work Mode: 5

Attributes Service Capacity: 16E1 Service Capacity: 16E1
Signal Bandwidth: 28 MHz Signal Bandwidth: 28 MHz
Modulation: QPSK Modulation: QPSK
Radio Link ID 101 101
ATPC Enable status Enabled Enabled

Parameter NE1 NE2
8-IF0 (7-IF0) 8-IF0 (7-IF0)
ATPC Upper Threshold (dBm) -40 -40
ATPC Lower Threshold -60 -60

(dBm)
Table 13-13 Information of ODU ports

Parameter NE1 NE2
18-ODU (17-ODU) 18-ODU (17-ODU)
Radio Frequency Transmission Frequency 14952 14532

Properties (MHz)
T/R Spacing (MHz) 420 420
Power Properties Transmit Power (dBm) 10 10
Equipment Attributes (can Station Type TX High TX Low

be planned but cannot be
set)
NOTE
Note: The attributes of the main and standby ODUs on NE1 and NE2 are the same.
PDH Service Configuration
Table 13-14 PDH service configuration

Parameter NE1 NE2
E1 ports E1-1 to E1-12 E1-1 to E1-12

Parameter NE1 NE2
Telephone No. 101 102
Call waiting time 5 seconds 5 seconds


You can configure the data of NE1 based on the parameters of the engineering planning, by
using the NMS.
Prerequisite
Procedure
l New ID: 101

l IP: 129.9.0.101
Step 3 Modify the IF 1+1 protection.

2. Click the IF 1+1 Protection tab. After setting the parameters, click Apply.
Working Mode HSB l In the 1+1 HSB protection mode, the

configuration for the IF board and ODU at the
two ends of each hop of a radio link to realize
the protection.
l You can set this parameter according to the
network planning.
Revertive Revertive l When this parameter is set to Revertive, the

Mode NE that is in the switching state releases the
WTR time (when the former working channel
is restored to normal) expires.
default value.

WTR Time(s) 600 l This parameter is valid only when the

Revertive Mode parameter is set to
Revertive.
l After the working path is restored to normal
and the normal state lasts for 600s, the
switching restoration occurs.
default value.
Enable Reverse Enable l If the main and standby IF boards of NE2

Switching reports service alarms, the alarms are reported
to the local equipment through the MWRDI
overhead in the radio frame. When the reverse
switching conditions are met, the IF 1+1
protection switching occurs at the local end.
l This parameter is valid only when Working
Mode is set to HSB or SD.
default value.

3. Set the information about the 8-IF0. Click Apply. Set the information about the 18-ODU.
Click Apply.
Work Mode 5,16E1,28MHz, l This parameter indicates the radio work mode
QPSK in "work mode, service capacity, channel
spacing, modulation mode" format.
l This parameter needs to be set according to the
service planning.

is used to prevent misconnection of radio links
between sites.
service planning.

ATPC Enable Enabled l When this parameter is set to Enabled, the

Status transmit power of the transmitter
controlled range.
service planning.
TX Frequency 14952.0 l This parameter specifies the central frequency

(MHz) of a channel.
service planning.
T/R Spacing 420.0 l This parameter indicates the spacing between

(MHz) the TX frequency and receive frequency of the
ODU.
service planning.
TX Power 10.0 This parameter needs to be set according to the

(dBm) service planning.

normally.
l Generally, this parameter should be set to
unmute.

1. In the NE Explorer, select the 8-IF0 board and then choose Configuration > IF
2. Click the ATPC Attributes tab. After setting the parameters, click Apply.

controlled range.
ATPC Upper -40.0 l Set the central value of the ATPC upper
Threshold threshold and the ATPC lower threshold so
(dBm) that the central value is equal to the required
value of the receive power.
l Ensure that the difference between values of
the automatic ATPC upper threshold and the

ATPC Lower -60.0 automatic ATPC lower threshold is not less

Threshold than 5 dB.
(dBm)
NOTE
The ATPC attributes should be set to the same value at both ends of a radio link.
Step 6 Configure E1 services.

2. Select the used E1 port. After setting the parameters, click Apply.
E1-1 to E1-12 Selected l In this example, the E1-1 to E1-12 ports are
selected.
l One E1 port corresponds to one E1 in the
microwave. That is, E1-1 corresponds to the
first E1 in the microwave and E1-2
corresponds to the second E1 in the
microwave.

l Phone 1: 101
l Call Waiting Time(s): 5
----End

the NMS.
Prerequisite
Procedure

l New ID: 102

l IP: 129.9.0.102
Step 3 Modify IF 1+1 protection.

2. Click the IF 1+1 Protection tab. After setting the parameters, click Apply.
Working Mode HSB l In the 1+1 HSB protection mode, the

configuration for the IF board and ODU at
both ends of each hop of a radio link to realize
the protection.
Revertive Revertive l When this parameter is set to Revertive, the

Mode NE that is in the switching state releases the
WTR time (when the former working channel
is restored to normal) expires.
default value.
WTR Time(s) 600 l This parameter is valid only when the

Revertive Mode parameter is set to
Revertive.
l After the working path is restored to normal
and the normal state lasts fro 600s, the
switching restoration occurs.
default value.
Enable Reverse Enable l When both the main IF board and the standby
Switching IF board of NE2 report service alarms, they
send the alarms to the source end by using the
MWRDI overhead in the microwave frame.
When the reverse switching conditions are
met, the IF 1+1 protection switching occurs at
the source end.
l This parameter is valid only when Working
Mode is set to HSB or SD.
default value.


Click Apply.
Work Mode 5,16E1,28MHz, l This parameter indicates the radio work mode
service planning.

between sites.
service planning.

controlled range.
service planning.

(MHz) of a channel.
service planning.

ODU.
service planning.


normally.
unmute.

Step 5 Set the ATPC attributes.

1. In the NE Explorer, select the 8-IF0 and then choose Configuration > IF Interface from
the Function Tree.
2. Click the ATPC Attributes tab. After setting the parameters, click Apply.

controlled range.
ATPC Upper -40.0 l Set the central value of the ATPC upper
Threshold threshold and the ATPC lower threshold so
(dBm) that the central value is equal to the required
value of the receive power.
ATPC Lower -60.0
l Ensure that the difference between values of
Threshold
the automatic ATPC upper threshold and the
(dBm)
automatic ATPC lower threshold is not less
than 5 dB.
NOTE
Each of the ATPC parameters must be set to the same value at the two ends of a radio link.

2. Select the used E1 port. After setting the parameters, click Apply.
E1-1 to E1-12 Selected l In this example, the E1-1 to E1-12 ports are
selected.
l One E1 port corresponds to one E1 in the
microwave. That is, E1-1 corresponds to the
first E1 in the microwave and E1-2
corresponds to the second E1 in the
microwave.
l Phone 1: 102
----End

13.9 Configuration Example (Hop between the IDU 605 and

the IDU 620)
example.

13.9.3 Configuring NE1 to NE4
You can configure the data of NE1 to NE4 based on the parameters of the service planning, by
using the NMS.
the NMS.

Figure 13-17 shows a tree network. Basic information of this network is as follows:
l NE1, NE2, and NE3 are the OptiX RTN 600 that is configured with IDU 620.
l NE4 is the OptiX RTN 600 that is configured with IDU 610.
l NE5 is the OptiX RTN 600 that is configured with IDU 605 1B.
l The E1 services need be converged from each NE to the STM-1 optical line board at the
client side. The service requirement in NE5 is 2xE1.


NE1 NE2 NE4
SDH
OptiX RTN 600 OptiX RTN 600 OptiX RTN 600

(IDU 620) (IDU 620) (IDU 610)
NE3 NE5
OptiX RTN 600 OptiX RTN 600

(IDU 620) (IDU 605 1B)

In the following example, the engineering planning covers the information required for
configuring NE5 only. For information required for configuring NE1-NE4, see the OptiX RTN
600 Radio Transmission System IDU 610/620 Configuration Guide.
NE Attributes
Parameter NE5
Equipment Type IDU 605 1A
NE ID 105
Extended ID 9 (the same as the default value)
NE IP 129.9.0.105

GHz frequency band with the T/R spacing of 420 MHz, thus decreasing the types of the required
spare parts.


NE4
(IDU 610)
NE1 V-polarization NE2

14547MHz
(IDU 620) (IDU 620)
Tx Low Tx Hi
14967MHz
Tx Hi 14930 MHz
V-polarization
14510 MHz
Tx Low Tx Low
14532 MHz V-polarization
NE3 NE5
14952 MHz (IDU 620) (IDU 605)
H-polarization Tx Hi 14930 MHz

Tx Hi
14510 MHz
Tx Low
Table 13-16 Planning information of the radio link between NE3 and NE5
Parameter Link 4
TX High NE3
TX Low NE5
Work Mode 2E1,3.5MHz,QPSK
Link Protection Mode 1+0
Polarization Directiona V (vertical polarization)
NOTE
Board Configuration
PW SCC EOW PF1 IF0

Slot 1 Slot 2 Slot 3 Slot 4 Slot 8

NOTE
not displayed in the board configuration diagram.
Table 13-17 Attributes of the IF 1+1 protection (NE5)

Parameter NE5
8-IF0
IF Attributes Radio Work Mode Work Mode: 18

Service Capacity: 2xE1
Signal Bandwidth: 3.5 MHz
Modulation: QPSK
Radio Link ID 104
ATPC Enable status Enabled
ATPC Upper Threshold (dBm) -45
ATPC Lower Threshold (dBm) -70
Table 13-18 Information of ODU ports (NE5)

Parameter NE5
18-ODU
Radio Frequency Properties Transmission Frequency (MHz) 14510
Power Properties Transmit Power (dBm) 10
Equipment Attributes (can be Station Type TX Low

planned but cannot be set)

PDH Service Configuration
Table 13-19 PDH service configuration (NE5)

Parameter NE5
E1 ports E1-1 to E1-2

Parameter NE5
Telephone No. 105
Call waiting time 5 seconds
13.9.3 Configuring NE1 to NE4

You can configure the data of NE1 to NE4 based on the parameters of the service planning, by
using the NMS.
For the data configurations of NE1 to NE4, see OptiX RTN 600 Radio Transmission System IDU
610/620 Configuration Guide.

the NMS.
Prerequisite
Procedure
l New ID: 105
l IP: 129.9.0.105


Click Apply.
Work Mode 18,2E1,3.5MHz, l This parameter indicates the radio work mode
service planning.

between sites.
service planning.

controlled range.
service planning.

(MHz) of a channel.
service planning.

ODU.
service planning.


normally.
unmute.

1. In the NE Explorer, select NE5 and then choose Configuration > Service
2. Select the ports E1-1 and E1-2 and click Apply.
l Phone 1: 105
----End

Operation Guide for RTN NE Management 14 Ethernet Feature(RTN 600)
14 Ethernet Feature(RTN 600)
About This Chapter
Displays the Ethernet feature of OptiX RTN 600 NEs.
14.1 Creating Ethernet Services

The IDU 610 supports Ethernet private line services. The IDU 620 supports Ethernet private
line services and Ethernet LAN services. The IDU 605 1F/2F supports Ethernet LAN services.
14.2 Configuring QinQ
The Ethernet switching processing board supports the line services that are based on QinQ
(802.1q in 802.1q). The function complies with IEEE 802.1q and IEEE 802.1ad.
14.3 Configuring Features of Ethernet Ports
To effectively work with the data communication equipment at the client side, the Ethernet port
supports the auto-negotiation function, Jumbo frames, and flow control function.
14.4 Configuring Encapsulation and Mapping of Ethernet Services
To transparently transmit Ethernet frames through the optical transmission network and the radio
transmission network, it is necessary to encapsulate the Ethernet frames and map them into VC
containers at the access point.
14.5 Configuring VLAN
The Ethernet switching processing board supports the virtual local area network (VLAN)
function that complies with IEEE 802.1q.
14.6 Configuring Layer 2 Switching
To realize the EPLAN service, the Ethernet switching and processing board can create one bridge
or multiple bridges. Each bridge can realize the Layer 2 switching of packets among mounted
ports and relevant features.
14.7 Configuring QoS
In legacy IP networks, all packets are processed according to the first in first out (FIFO) and
best effort strategies. This method cannot meet the requirement of the new service for the
bandwidth, delay, and delay jitter. Hence, the QoS technology is developed.

14 Ethernet Feature(RTN 600) Operation Guide for RTN NE Management
14.1 Creating Ethernet Services

The IDU 610 supports Ethernet private line services. The IDU 620 supports Ethernet private
line services and Ethernet LAN services. The IDU 605 1F/2F supports Ethernet LAN services.
Before you configure Ethernet boards with services, you need to learn the basic concepts
including external port, internal port, logical port, and bridge so that you can understand the
service configuration process and the signal flow when the boards process the services.
14.1.2 Configuring the Cross-Connections of Ethernet Services
In the case of Ethernet over SDH, you need to configure the cross-connections of the Ethernet
services.
14.1.3 Configuring EPL Services
You can configure EPL services on a per-NE basis.
14.1.4 Configuring Ethernet LAN Services
You can configure Ethernet LAN services on a per-NE basis by following the instructions below.
14.1.5 Configuring EVPL (QinQ) Services
You can configure EVPL (QinQ) services on a per-NE basis.
14.1.6 Configuration Example (Point-to-Point EPL Services)
entire process of configuring the parameters of each NE according to the point-to-point EPL
14.1.7 Configuration Example (PORT-Shared EVPL Services)
entire process of configuring the parameters of each NE according to the PORT-shared EVPL
14.1.8 Configuration Example (VCTRUNK-Shared EVPL Services)
entire process of configuring the parameters of each NE according to the VCTRUNK-shared
EVPL service requirements.
14.1.9 Configuration Example (802.1d Bridge-Based EPLAN Services)
entire process of configuring the parameters of each NE according to the requirements for the
802.1d bridge-based EPLAN services.
14.1.10 Configuration Example (802.1q Bridge-Based EVPLAN Services)
802.1q bridge-based EVPLAN services.
14.1.11 Configuration Example (EVPL Services Based on QinQ)
This topic provides an example to describe how to configure QinQ line services.
14.1.12 Configuration Example (EVPLAN Services Based on the IEEE 802.1ad Bridge)
This topic considers an example to describe how to configure the EVPLAN services that are
based on the IEEE 802.1ad bridge.
14.1.13 Configuring Services Based on the Hybrid Microwave
The Hybrid microwave that the OptiX RTN 600 supports can transmit E1 services and Ethernet
services at the same time. When E1 services are transmitted over the Hybrid microwave, you

need to create the cross-connections. When Ethernet services are transmitted over the Hybrid
microwave, you need not configure the encapsulation and mapping in the VCTRUNKs or the
cross-connections between the VCTRUNKs and line timeslots.

Before you configure Ethernet boards with services, you need to learn the basic concepts
including external port, internal port, logical port, and bridge so that you can understand the
service configuration process and the signal flow when the boards process the services.
14.1.1.1 Formats of Ethernet Frames
To implement the VLAN and QinQ functions, the IEEE 802.1q and IEEE 802.1ad protocols
define different formats of the Ethernet frames, which contain different VLAN information.
14.1.1.2 Internal Ports and External Ports
External ports on Ethernet boards are used to access the services on the user side. Internal ports
on Ethernet boards are used to encapsulate and map the services to the transmission network for
transparent transmission.
14.1.1.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
14.1.1.4 Flow Control
When the data processing/transferring capability of the equipment fails to handle the flow
received at the port, congestion occurs on the line. To reduce the number of discarded packets
due to buffer overflowing, proper flow control measures must be taken.
14.1.1.5 Encapsulation and Mapping Protocol
To ensure that Ethernet frames can be transparently transmitted over the optical transmission
network, the Ethernet frames need to be encapsulated and mapped into VC containers at the
access point. encapsulation and mapping protocols used by the Ethernet service board include
the high-level data link control (HDLC), link access procedure - SDH (LAPS), and generic
framing procedure (GFP).
14.1.1.6 Virtual Concatenation
The rate of the Ethernet service does not adapt to the rate of the standard VC container. Hence,
if you directly map the Ethernet service data into a standard VC container, there is a great waste
of the transmission bandwidth. To solve the problem, use the virtual concatenation technology
to concatenate many standard VC containers to a large VC container that adapts to the rate of
the Ethernet service.
14.1.1.7 Tag Attributes
When data frames enter or exit a port on an Ethernet board, the processing mode of the data
frames is determined by the tag attributes of this port.
14.1.1.8 Bridge
The bridge is the functional unit used to implement the interconnection between two or more
LANs.
14.1.1.1 Formats of Ethernet Frames

To implement the VLAN and QinQ functions, the IEEE 802.1q and IEEE 802.1ad protocols
define different formats of the Ethernet frames, which contain different VLAN information.

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

802.1q frame format
Destination Source MAC FCS Check

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

one C-VLAN tag
Destination Source MAC FCS Check

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

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

Length/Type
MAC Address Address Character
Variable
6 bytes 6 bytes 4 bytes 4 bytes 2 bytes 4 bytes
length
The length of the data field is variable. maximum length of the data field depends on the
maximum frame length that the ports of the equipment support.
The four-byte S-VLAN or C-VLAN field is divided into two sub-fields: the tag protocol ID
(TPID) and the tag control Information (TCI).
Both the TPID and TCI consist of two bytes. See Figure 14-2.
Figure 14-2 Positions of the TPID and TCI in the frame structure
S-VLAN C-VLAN
Destination Source MAC TPID TCI TPID TCI Length/Type Data FCS Check
MAC Address Address Character
Variable
6 bytes 6 bytes 2 2 bytes 2 bytes 2 bytes 2bytes 2 bytes 4 bytes
length

l TPID structure
The TPID consists of two bytes and indicates the VLAN tag type. TPID of the C-VLAN is
always 0x8100 whereas the TPID of the S-VLAN can be customized. Refer to Table 14-1.
Table 14-1 Tag types defined by using the TPID
Tag Type Name Value
C-VLAN tag 802.1q tag protocol type 0x8100
S-VLAN tag 802.1q service tag Customizable
NOTE
The IEEE 802.1ad specifies the TPID of the S-VLAN to 0x88a8. In actual application, the setting of TPID
for the S-VLAN tag varies according to the equipment manufacturer. To ensure compatibility between
interconnected equipment, it is recommended that you set the TPIDs of the S-VLAN tags of the
interconnected equipment to the same value within 0X600-FFFF.
l TCI structure
The TCI structure of the S-TAG is basically the same as the TCI structure of the C-TAG. VLAN
ID (VID) field consists of 12 bits and ranges from 0 to 4095. difference is that the TCI of the S-
TAG contains the drop eligible (DE) indication and works with the priority code point (PCP) to
indicate the priority of the S-TAG frame.
The TCI structures of the C-TAG and S-TAG are shown in Figure 14-3 and Figure 14-4.
Figure 14-3 TCI structure of the C-TAG
Octets: 1 2
PCP CFI VID VID
Bits: 8 6 5 4 1 8 1
The TCI length of the C-TAG is 2 byte, including the following:

l PCP: 3 bits
l CFI: 1 bit
Figure 14-4 TCI structure of the S-TAG
Octets: 1 2
PCP DE VID VID
Bits: 8 6 5 4 1 8 1

The TCI field of the S-TAG consists of the following bytes:
l PCP: 3 bits
l DE: 1 bit
l VID: 12 bits
14.1.1.2 Internal Ports and External Ports

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

External port VCTRUNK port
Backplane
Cross-
Interface Service Encapsulation/ Interface connect unit
module processing Mapping conversion
module module module Cross-
connect unit
Ethernet board
14.1.1.3 Auto-Negotiation
The working modes of the interconnected ports on the equipment at both ends must be the same.
Otherwise, the services are unavailable.
If the working mode of the port on the opposite equipment is full duplex and if the working
mode of the port on the local equipment is auto-negotiation, the local equipment works in the
half-duplex mode. That is, the working modes of the interconnected ports at both ends are
different, and thus packets may be lost. Hence, when the working mode of the port on the opposite
equipment is full duplex, you need to set working mode of the port on the local equipment to
full duplex.

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

Figure 14-7 Consecutive FLP and NLP bursts

T5
T4
FLP bursts
NLPs
T4: 2 ms T5: 16 ms
14.1.1.4 Flow Control

due to buffer overflowing, proper flow control measures must be taken.
The half-duplex Ethernet port applies the back-pressure mechanism to control the flow. full-
duplex Ethernet port applies PAUSE frames to control the flow. Currently, the half-duplex
Ethernet function is not widely applied. Hence, the flow control function realized by Ethernet
service boards is used for the full-duplex Ethernet ports.
The flow control function realized by Ethernet service boards is classified into two types: auto-
negotiation flow control and non-auto-negotiation flow control.
Auto-Negotiation Flow Control

When the Ethernet port works in the auto-negotiation mode, you can adopt the auto-negotiation
flow control function. auto-negotiation flow control modes include the following:
l Enable dissymmetric flow control
The port can transmit PAUSE frames in the case of congestion but cannot process the
l Enable symmetric flow control
The port can transmit PAUSE frames and process the received PAUSE frames.
l Enable symmetric/dissymmetric flow control
The port has the following abilities:
Transmits and processes PAUSE frames.
Transmits PAUSE frames but cannot process the received PAUSE frames.
Processes the received PAUSE frames but cannot transmit PAUSE frames.
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. 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
l Receive only
The port can process the received PAUSE frames but cannot transmit PAUSE frames in
the case of congestion.
l Send and receive
The port can transmit PAUSE frames and process the received PAUSE frames.
Realization Principle
The realization principle of the flow control function is described as follows:
1. When congestion occurs in the receive queue of an Ethernet port (the data in the receive
buffer exceeding a certain threshold) and the port is capable of sending PAUSE frames,
the port sends a PAUSE frame to the opposite end. Pause-time value in the frame is N (0
< N 65535).
2. If the Ethernet port at the opposite end is capable of processing PAUSE frames, this Ethernet
port stops sending data within a specified period of time N (the unit is the time needed for
sending 521 bits) after receiving the PAUSE frame.
3. If the congestion at the receive port is cleared (the data in the receive buffer is below a
certain threshold) but the pause-time does not end, the port sends a PAUSE frame whose
pause-time is 0 to notify the opposite end to send data.
IEEE 802.3 defines the format of the PAUSE frame as follows:
l Destination address: 01-80-C2-00-00-01 (multicast address)

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

XX-XX 2 octets
(pause-time)
Reserved

14.1.1.5 Encapsulation and Mapping Protocol

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

if you directly map the Ethernet service data into a standard VC container, there is a great waste
of the transmission bandwidth. To solve the problem, use the virtual concatenation technology
to concatenate many standard VC containers to a large VC container that adapts to the rate of
the Ethernet service.
The concatenation is defined in ITU-T G.707 are contiguous concatenation and virtual
concatenation. Both concatenation methods provide concatenated bandwidth of X times
Container-N at the path termination.
Contiguous concatenation concatenates the contiguous VC-4s in the same STM-N into an entire
structure to transport. It maintains the contiguous bandwidth throughout the whole transport.
Virtual concatenation concatenates many individual VC containers (VC-12 containers, VC-3

containers, or VC-4 containers) into a bit virtual structure to transport. virtual concatenation
breaks the contiguous bandwidth into individual VCs, transports the individual VCs, and
recombines these VCs to a contiguous bandwidth at the transmission termination point.
In the case of virtual concatenation, transport of each VC container may occupy different paths
and there may be a transport delay difference between VC containers. Hence, there are
difficulties to restore the client signal. Virtual concatenation requires concatenation functionality
only at the path termination equipment and it can flexibly allocate bandwidth. Hence, the virtual
concatenation technology is widely used.
Virtual concatenation is available in two types: virtual concatenation in a higher order path and
virtual concatenation in a lower order path. A higher order virtual concatenation VC-4-Xv
provides a payload of X Container-4s (VC-4s). payload is mapped individually into X
independent VC-4s. Each VC-4 has its own POH. A lower order virtual concatenation VC-12-
Xv provides a payload of X Container-12s (VC-12s). payload is mapped individually into X
independent VC-12s. Each VC-12 has its own POH. It is the same case with the virtual
concatenation of VC-3s.
VC-4-Xv and VC-3-Xv

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

Figure 14-9 VC-3-Xv/VC-4-Xv multiframe and sequence indicator

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

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

Table 14-2 Processing mode of data frames at ports with different tags
Direction Data Frame Type Processing Mode
Ingress port Frames with VLAN Transparently Discards the frames. Transparently
tags transmits the transmits the
frames. frames.
Frames without Discards the frames. Adds the VLAN tags that contain Default
VLAN tags VLAN ID and VLAN Priority and
transparently transmits the frames.
Egress port Frames with VLAN Transparently Strips the VLAN l If the VLAN IDs
tags transmits the tags and transmits contained in the
frames. the frames. data frames are
Default VLAN
ID, strips the
VLAN tag and
transmits the
data frames.
l If the VLAN IDs
contained in the
data frames are
not Default
VLAN ID,
transparently
transmits the
data frames.
NOTE
The tag setting is valid only if the following conditions are met:
l The port type is PE or UNI.
l The entry detection function is enabled. When the Ethernet switching board works in the Ethernet
transparent transmission state and when the entry detection function is disabled, the ports transparently
transmit the received data frames regardless of whether the data frames have the VLAN tags.
Based on the tag aware, access, and hybrid features, adhere to the following principles when
setting the tag for a port:
l If it is certain that the data packets transmitted from the interconnected equipment have the
VLAN tags, set the local port to the tag aware mode.
l If it is certain that the data packets transmitted from the interconnected equipment do not
have the VLAN tags, set the local port to the access mode.
l If it is uncertain whether the data packets transmitted from the interconnected equipment
have the VLAN tags, set the local port to the hybrid mode.
14.1.1.8 Bridge
The bridge is the functional unit used to implement the interconnection between two or more
LANs.

VB and LP
The various bridge (VB) is the unique concept for Huawei products. In the case of the Ethernet
data boards that have the Layer 2 switching capability, the switching domain can be divided into
multiple sub-switching domains. As a result, if no services are interconnected, different VBs
cannot access each other. Each VB has an independent configuration mode and uses an
independent VLAN. Different VBs can use the same VLAN.
A VB can contain a number of logical ports (LPs). By configuring the mounting relation, you
can mount multiple MAC ports and VCTRUNK ports to the same VB.
Figure 14-10 shows the relation between VB, LP, external port, and VCTRUNK port.
Figure 14-10 Relation between VB, LP, external port, and VCTRUNK port
Ethernet switching board
VB1
PORT1 LP1 LP4 VCTRUNK1
VB2
Transparent Bridge and Virtual Bridge

l The services of different transparent bridges are isolated but the services of the same
transparent bridge are not isolated. entire transparent bridge is a switching domain.
l The services of different virtual bridges are isolated and the services with different VLAN
IDs in the same virtual bridge are also isolated. switching domain of the entire virtual bridge
is divided into multiple sub-switching domains according to the VLAN IDs.
NOTE
As shown in Figure 14-11, the same logical port may belong to one or more sub-switching domains with
different VLAN IDs. On the U2000, the same logical port can belong to multiple filtering tables for different
VLAN IDs.

Figure 14-11 Transparent bridge and virtual bridge
VCTRUNK1 VCTRUNK1
PORT1 PORT1 VLAN1
VCTRUNK2 VCTRUNK2
VLAN1
VCTRUNK3 VLAN2 VCTRUNK3
PORT2 VLAN2 PORT2
VCTRUNK4 VCTRUNK4
VLAN3
... VCTRUNK5 VCTRUNK5
PORT3 VCTRUNK6 PORT3 VLAN3
VCTRUNK6
Pure bridge Virtual bridge
Logical port
Table 14-3 Transparent bridge and virtual bridge

Item Transparent Bridge Virtual Bridge
VLAN filtering table It need not be configured. It must be configured.
Ingress filtering The validity of VLAN tags is The validity of VLAN tags is
not checked. All the data checked. If the VLAN ID in
frames that enter the bridge the VLAN tag is not the same
are considered as valid. as defined in the VLAN
filtering table, the data frame
is discarded.
MAC address learning mode SVLa IVLb
Data frame forwarding mode Queries the MAC address Queries the MAC address
table to obtain the forwarding table to obtain the forwarding
port according to the port according to the
destination MAC address of destination MAC address and
the data frame. VLAN ID of the data frame.
Broadcast range Forwards the broadcast data Forward the broadcast

frames to all the ports of the frames to the forwarding
bridge. ports defined in the VLAN
filtering table.
NOTE
To forward a Layer 2 switching service, a bridge must learn the MAC address. A bridge learns the MAC
address in one of the following two ways: shared VLAN learning (SVL) and independent VLAN learning
(IVL).
l a: When the bridge adopts the SVL learning mode, the entry in the MAC address table is created
according to the source MAC address and source port of the data frame. entry is valid for all the VLANs.
l b: When the bridge adopts the IVL learning mode, the entry in the MAC address table is created
according to the source MAC address, VLAN ID, and source port of the data frame. entry is not valid
for all the VLANs.
Types of Bridges
As listed in Table 14-4, the Ethernet boards support three types of bridges.

Table 14-4 Types of bridges supported by the Ethernet boards
Type of Bridge Bridge Switch Mode Bridge Learning Ingress

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

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

Enable
IEEE 802.1ad 1 SVL/Ingress Filter SVL Disabled

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

The entries in the MAC address table indicate the corresponding relation between the MAC
addresses and the ports. MAC address table contains the following entries:
l Dynamic entry
Indicates the entry that the bridge obtains by adopting the SVL/IVL learning mode. dynamic
entry ages and is even lost after the Ethernet switching board is reset.
l Static entry
Indicates the entry corresponding to the MAC address and the port that the network
administrator manually adds in the MAC address table on the U2000. dynamic entry does
not age and is not lost after the Ethernet switching board is reset.
l Blackhole entry
Indicates the entry used to discard the data frame that contains the specified destination
MAC address, and is also referred to as the MAC address disable entry. blackhole entry is

configured by the network administrator. This entry does not age and is not lost after the
Ethernet switching board is reset.
NOTE
l If a routing entry is not updated within a specific period of time, that is, if the MAC address fails to be learnt
because the new data frame from the MAC address is not received, this routing entry is automatically deleted.
This mechanism is considered as aging, and this period of time is considered as the aging time. aging time
of the MAC address table is five minutes by default and can be set by using the U2000.
l A limited number of MAC addresses can be learnt at a time.
Hub/Spoke
Generally, the central station and non-central stations can access each other but the non-central
stations cannot access each other in the case of convergence services. Hence, the ports mounted
to the bridge need to be defined as Hub ports or Spoke ports.
l Hub port
Hub ports can access each other. Hub ports and Spoke ports can also access each other.
l Spoke port
Spoke ports cannot access each other. Hub ports and Spoke ports can access each other.
The mounted ports are Hub ports by default.
14.1.2 Configuring the Cross-Connections of Ethernet Services

In the case of Ethernet over SDH, you need to configure the cross-connections of the Ethernet
services.
14.1.2.1 Creating Cross-Connections of Ethernet Services

This topic describes how to create the timeslot connections between the bound paths and the
line board, thus to ensure that the Ethernet services are transmitted in specified timeslots over
the transmission line.
14.1.2.2 Deleting the Cross-Connections of an Ethernet Service
When the cross-connections of an Ethernet service are deleted, the corresponding cross-
connection resources are released.
14.1.2.1 Creating Cross-Connections of Ethernet Services

This topic describes how to create the timeslot connections between the bound paths and the
line board, thus to ensure that the Ethernet services are transmitted in specified timeslots over
the transmission line.
See 13.3.1 Creating Cross-Connections of Point-to-Point Services to create the cross-

connections of the Ethernet services. If SNCP is configured for the Ethernet services, see 13.3.2
Creating Cross-Connections for SNCP Services to create the cross-connections of the SNCP
Ethernet services.
14.1.2.2 Deleting the Cross-Connections of an Ethernet Service

When the cross-connections of an Ethernet service are deleted, the corresponding cross-
connection resources are released.

Prerequisite
Procedure
1. Click Query.
2. Click OK.
3. Click Close.
Step 3 Select the cross-connection of the Ethernet service that needs to be deleted in Cross-
Connection.
selected services (only for activated services?).
3. Click OK.
4. Click Close.
1. Click Delete.
Then, the Confirm dialog box is displayed, prompting Are you sure to delete all the
selected services (only for inactive services)?.
2. Click OK.
3. Click Close.
Step 6 Click Query.
At this time, the cross-connection of the Ethernet service is already deleted.
----End
14.1.3 Configuring EPL Services

You can configure EPL services on a per-NE basis.
14.1.3.1 EPL Service Configuration Process
This section describes the EPL service configuration process that consists of deploying a
network, configuring source NEs, configuring sink NEs, configuring pass-through NEs, and
verifying services.

14.1.3.2 Setting Port Attributes and Bound Paths for an Ethernet Board
You need to set the port attributes and bound paths for an Ethernet board prior to creating Ethernet
services.
14.1.3.3 Creating Ethernet Line Service
To enable the Ethernet switching board to transmit the line service, perform certain operations
to configure the related information, such as the service source and service sink.
14.1.3.4 Testing Ethernet Services
You can enable an Ethernet board to send Ethernet test frames for the purpose of fault location.
14.1.3.5 Deleting an Ethernet Private Line Service
When an Ethernet private line service is not used, you can delete the Ethernet private line service
14.1.3.1 EPL Service Configuration Process

This section describes the EPL service configuration process that consists of deploying a
network, configuring source NEs, configuring sink NEs, configuring pass-through NEs, and
verifying services.
Figure 14-12 shows the process for configuring EPL services.
Figure 14-12 EPL service configuration process

Required
Optional
Deploying a Configure Configure Configure

Verify service
Network source NE sink NE pass-through NE
Creating and Creating Cross-

Setting External Setting External Test the Ethernet
Configuring NEs Connection
Ports Attributes of Ports Attributes of Services
Between Ethernet
Ethernet Boards Ethernet Boards and Line Boards
Creating Fibers
Setting Internal Setting Internal

Ports Attributes of Ports Attributes of
Configuring Ethernet Boards Ethernet Boards
Communication
Setting the NE Setting Bound Setting Bound

Time Paths of Ethernet Paths of Ethernet
Boards Boards
Configuring Clocks Creating Cross-

Creating Cross-
Connection Connection
Between Ethernet Between Ethernet
Configuring and Line Boards and Line Boards
Orderwire
Creating EPL Creating EPL

Configuring Services Services
Protection

NOTE
l In the case of the EFT4 board for the RTN equipment, the EPL service is written to the board. Thus,
Creating EPL Services is not needed for the source or sink NE.
l In the landscape orientation of the configuration flow chart by using U2000, there are five main phases
of EPL service configuration process. They are deploying a network, configuring source NEs,
configuring sink NEs, configuring pass-through NEs, and verifying services.
l The portrait orientation of the flow chart shows the relations between operation tasks in each phase.
services.
Prerequisite
The Ethernet board must be created.
Procedure
Step 1 Configure the external port of a board. For details, refer to 14.4.7.1 Configuring the Internal
Port of the Ethernet Board.
Step 2 Configure the internal port of a board. For details, refer to 14.3.7.1 Configuring External
Ethernet Ports.
----End

Prerequisite
The Ethernet switching board must be added in the slot layout.
Precautions
l This topic does not describe the method for creating the QinQ service.
l IDU 620 supports the Ethernet switching board EMS6. The EFT4 board is an Ethernet
transparent transmission board, and the PORTs of the EFT4 board correspond to the
VCTRUNKs. Hence, you do not need to create the Ethernet line service.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Click New.

The Create Ethernet Line Service dialog box is displayed.

Step 3 Set the attributes of the Ethernet line service.
Step 4 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the
result of directly setting the Ethernet service port attributes.
Step 5 Optional: Set the bound path.

The Bound Path Configuration dialog box is displayed.
5. Optional: Repeat Step 5.4 to bind other VC paths.

NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.
6. Click OK.
Step 6 Click OK.
----End
Parameters
Service Type EPL, EVPL (QinQ) EPL When creating the non-QinQ private line
service, set this parameter to EPL.
Direction Unidirectional, Bidirectional l When setting this parameter to

Bidirectional Unidirectional, create the service only
from the service source to the service
sink. That is, the service source is
forwarded only to the sink port.
l When setting this parameter to
Bidirectional, create the service from
the service source to the service sink and
the service from the service sink to the
service source. That is, when the service
source is forwarded to the sink port, the
service sink is forwarded to the source
port.
l Generally, it is recommended that you
use the default value.

Source Port A specific PORT or PORT1 l This parameter indicates the port where
VCTRUNK the service source resides.
l When creating the bidirectional Ethernet
service from a PORT to a VCTRUNK,
use a specific PORT as the source port.
Source VLAN (e.g. 1-4095 - l You can set this parameter to null, a
1,3-6) number, or several numbers. When
setting this parameter to several
numbers, use "," to separate these
discrete values and use "-" to indicate
continuous numbers. For example, "1,
3-6" indicates numbers 1, 3, 4, 5, and 6.
l The number of VLANs set in this
parameter should be the same as the
number of VLANs set in Sink C-VLAN
(e.g. 1,3-6).
l When you set this parameter to null, all
the services of the source port work as
the service source.
l When you set this parameter to a non-
null value, only the services of the source
port whose VLAN IDs are included in
the set value of this parameter work as
the service source.
Sink Port A specific PORT or PORT1 l This parameter indicates the port where
VCTRUNK the service sink resides.
l Do not set the value of this parameter to
the same as the value of Source Port.
use a VCTRUNK as the sink port.

Sink VLAN (e.g. 1-4095 - l You can set this parameter to null, a
number of VLANs set in Source C-
VLAN (e.g. 1,3-6).
the services of the sink port work as the
service sink.
null value, only the services of the sink
the service sink.
Port Enabled Enabled, Disabled - When the source port or the sink port is set
to a PORT, set Port Enabled to Enabled.
TAG Access, Tag Aware, Tag Aware l When all the accessed services are
Hybrid frames with the VLAN tag (tagged
frames), set this parameter to Tag
Aware.
l When all of the accessed services are not
frames with the VLAN tag (untagged



path take priority.
paths.


Prerequisite
l The Ethernet services must be created.
Context
l Test the Ethernet service as follows:
As shown in Figure 14-13, when Ethernet services are unavailable between router A and
router B, you can send test frames between NE1 and NE2 to determine whether a fault
occurs. NE1 sends test frames to NE2, and NE2 sends response frames after it receives the

test frames. According to the response frames from NE2, NE1 determines whether a fault
occurs.
Figure 14-13 Ethernet test

NE1 NE2 NE3
Test
Frame
Answer
Frame
Router A Router B
l This test does not affect the service.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Ethernet Maintenance >
Ethernet Test from the Function Tree.
Step 2 Select the internal port that you want to test and set the test parameters.
NOTE
Set an NE to send test frames when you want to test whether a network is normal or not. The Send Mode and
Frames to send parameters can be edited. When setting Send Mode, note the following:
l If you select the Continue Mode, you can continuously send one test packet every 1s until you stop.
l If you select the Burst Mode, you can set the number of frames you want to send. The sending duration is
50 ms.
l If you select the Disabled mode, you stop sending test frames.
----End
14.1.3.5 Deleting an Ethernet Private Line Service

When an Ethernet private line service is not used, you can delete the Ethernet private line service
Prerequisite
The Ethernet private line service must be configured and the service is not be used.

Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration >
Ethernet Service > Ethernet Line Service from the Function Tree.
Step 2 Click Query.
Click OK in the dialog box that is displayed.
Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete.
Step 4 Click Query.
At this time, the Ethernet private line service is already deleted.
----End
14.1.4 Configuring Ethernet LAN Services

You can configure Ethernet LAN services on a per-NE basis by following the instructions below.
14.1.4.1 Ethernet LAN Service Configuration Process
This section describes the process for Ethernet LAN service configuration process that consists
of deploying a network, configure source NE, configure sink NE, configure pass-through NE
and verify service.
services.
14.1.4.3 Creating the Ethernet LAN Service
To enable the Ethernet switching board to transmit the LAN service, perform certain operations
to create the bridge and set the attributes of the bridge and to configure the mounted ports of the
bridge.
14.1.4.4 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge
To enable the Ethernet switching board to transmit the EVPLAN services that are based on the
IEEE 802.1ad bridge, you need to create the bridge, set the attributes of the bridge, select the
ports that are mounted to the bridge, and select the operation type.
14.1.4.5 Creating the VLAN Filter Table
You need to create the VLAN filter table for the bridge when you create the EVPLAN service.
14.1.4.7 Deleting an Ethernet LAN Service
When an Ethernet LAN service is not used, you can delete the Ethernet LAN service to release
the corresponding resources.
14.1.4.1 Ethernet LAN Service Configuration Process

This section describes the process for Ethernet LAN service configuration process that consists
and verify service.
Figure 14-14 shows the process for configuring Ethernet LAN services.

Figure 14-14 Ethernet LAN service configuration process

Required
Optional

Verify service
Creating and Test the Ethernet

Configuring NEs Setting External Setting External Configuring SDH
Services
Ethernet Boards Ethernet Boards
Creating Fibers Checking the

Connectivity of
Setting Internal Setting Internal Ethernet Service
Communication Checking the
Connectivity of
Ethernet Port
Creating Cross- Creating Cross-
Setting the NE
Time
and Line Boards and Line Boards
Configuring Clocks
Creating EPLAN Creating EPLAN
Services Services
Configuring
Orderwire
Creating VALN Creating VALN
Configuring
Protection
Configuring QOS Configuring QOS
Configuring LPT Configuring LPT
Configuring LCAS Configuring LCAS
Configuring Configuring
Ethernet Service Ethernet Service
OAM OAM
Configuring the Configuring the

Ethernet Port OAM Ethernet Port OAM
NOTE
of Ethernet LAN service configuration process. They are deploying a network, configure source NE,
configure sink NE, configure pass-through NE and verify service.
services.

Prerequisite
Procedure
Ethernet Ports.
----End
14.1.4.3 Creating the Ethernet LAN Service

bridge.
Prerequisite
The Ethernet switching board must be included in the slot layout.
Precautions
l This task describes only how to create the 802.1d bridge and how to create the 802.1q
bridge.
l The IDU 620 supports the Ethernet switching board EMS6.
l The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the attributes of the bridge according to the bridge type.
l Set the attributes of the 802.1q bridge.

l Set the attributes of the 802.1d bridge.
Step 4 Configure the mounted ports of the bridge.

1. Click Configure Mount.
The Service Mount Configuration dialog box is displayed.
2. Select a port from the ports listed in Available Mounted Ports, and then click .
3. Optional: Repeat Step 4.2 to select other mounted ports.

4. Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to
the VCTRUNK.
3. In Available Bound Paths, set Level and Service Direction of the bound paths.
NOTE
6. Click OK.
Step 6 Click OK.
----End

Parameters
VB Name - - This parameter is a string that describes the

bridge. It is recommended that you set this
string to a value that contains the specific
purpose of the bridge.
Bridge Type 802.1q, 802.1d, 802.1q l When setting this parameter to 802.1q,
802.1ad (EMS6) create the 802.1q bridge.
802.1q, 802.1d l When setting this parameter to 802.1d,
(EM4T, a logical create the 802.1d bridge.
board EMS4) l Using the 802.1q bridge is a priority. If
the conditions of the VLAN that is used
by the user are not known and if the user
does not require the isolation of the data
among VLANs, you can also use the
802.1d bridge.
l This task describes only how to create
the 802.1d bridge and how to create the
802.1q bridge.
Bridge Switch Mode IVL/Ingress Filter IVL/Ingress Filter l When the bridge uses the SVL mode, all
Enable (802.1q), Enable (802.1q), the VLANs share one MAC address
SVL/Ingress Filter SVL/Ingress Filter table. When the bridge uses the IVL
Disable (802.1d) Disable (802.1d) mode, all the VLANs correspond to their
respective MAC address tables.
l If the ingress filter is enabled, the VLAN
tag is checked at the ingress port. If the
VLAN ID does not equal the VLAN ID
of the port defined in the VLAN filtering
table, the packet is discarded. If the
ingress filter is disabled, the preceding
described check is not conducted.
Mount Port - - l Only the port that is selected as the

mounted port of a bridge functions in the
packet forwarding process of the bridge.
situations.
Configurable Ports Mount each - This parameter specifies the VCTRUNK

VCTRUNK of the whose VC paths are to be configured.
port.


determined by the actual bandwidth of
the service needs.
l Bind only the paths in a VC-4 if possible.
If the paths of several VC-4s need to be
bound, the VC-4s that have the same
transmission path take priority.
of whose VC-3 paths are already bound;
when a VCTRUNK needs to be bound
l As the VC-4-1s of the EFT4 board and
EMS6 board support only VC-3 paths
whereas the VC-4-2s support both
VC-12 paths and VC-3 paths, give
priority to the paths in the VC-4-1 if a
VCTRUNK needs to be bound with
VC-3 paths.

Prerequisite
Precautions

Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Ethernet
Step 2 Click New.

Step 3 Set the attributes of the IEEE 802.1ad bridge.
Step 4 Configure service mounting relations.

2. Set the parameters for configuring mounted services.
3. Click Add Mount Port.
4. Repeat Step 4.2 to Step 4.3 to add the other mount ports.
5. Click OK.
the VCTRUNK.
4. Select the required items in Available Resources and Available Timeslots and click
.

NOTE
The result of setting the port attributes during the configuration of the private network service is consistent
with the result of directly setting the attributes of the Ethernet service port.
6. Click OK.
----End
Parameters

VB Type 802.1q, 802.1d, 802.1q l In this example, the IEEE 802.1d bridge
802.1ad and IEEE 802.1q bridge need not be
created. Hence, do not set VB Type to
802.1d or 802.1q.
Enable Enable the VLANs share one MAC address
SVL/Ingress Filter table. When the bridge uses the IVL
Disable mode, all the VLANs correspond to their
VLAN ID is not equal to the VLAN ID

Operation Type Add S-VLAN Base Add S-VLAN Base For the meaning of each operation type, see
for Port for Port 14.2.2.4 Application of the QinQ
Add S-VLAN Base Technology in LAN Services.
for Port and C-
VLAN
Mount Port
Mount Port and
Base for Port and S-
VLAN
VB Port - - This parameter specifies the ID of the

logical port of the bridge.
Mount Port - - Select the external physical port or internal

VCTRUNK port of the Ethernet switching
board that is mounted to the IEEE 802.1ad
bridge.
C-VLAN 1-4095 - This parameter is valid only when

Operation Type is set to Add S-VLAN
Base for Port and C-VLAN.
This parameter specifies the mapping
relation between the C-VLAN tag carried by
the data frame and the S-VLAN tag to be
added.
S-VLAN 1-4095 - l When Operation Type is set to Add S-

VLAN Base for Port, this parameter
specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN tag.
l When Operation Type is set to Add S-
VLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify the
mapping relation between the S-VLAN
tag to be added and the C-VLAN tag
carried by the data frame that enters the
IEEE 802.1ad bridge.
l When Operation Type is set to Mount
Port, this parameter is invalid.
Port and Base for Port and S-VLAN,
this parameter specifies the S-VLAN tag
to be carried by the data frames that enter
the IEEE 802.1ad bridge.

port.

Available Bound - - Adhere to the following principles when

Paths planning and setting this parameter:
the service needs.
l The VC-4-1s of the EMS6 board support
only VC-3 paths, whereas the VC-4-2s
of the EMS6 board support both VC-12
paths and VC-3 paths. Hence, give
VC-3 paths.
14.1.4.5 Creating the VLAN Filter Table

Prerequisite
The EVPLAN service must be created.
Precautions
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).

Procedure
Step 2 Select the bridge that is already created, and click the VLAN Filtering tab.
Step 3 Create the VLAN filter table.
1. Click New.
The Create VLAN dialog box is displayed.
2. Set VLAN ID (e.g:1,3-6).
3. Select a port from the ports listed in Available forwarding ports, and then click .
4. Optional: Repeat Step 3.3 to select other forwarding ports.
5. Click OK.
----End

Parameters
VLAN ID (e.g: 1-4095 - l You can set this parameter to a number

1,3-6) or several numbers. When you set this
3, 4, 5, and 6.
situations.
selected forwarding This parameter - l The packets can be forwarded between

ports indicates the ports the selected forwarding ports only.
that are mounted to a l The ports that are in selected
bridge. forwarding ports can forward only the
packet that carries the VLAN ID (e.g:
1,3-6) tag. These ports discard the packet
that carries other VLAN tags.
l The broadcast packet that is transmitted
by the ports in selected forwarding
ports is broadcast only to the ports
included in selected forwarding ports.

Prerequisite
Context
occurs.


NE1 NE2 NE3
Test
Frame
Answer
Frame
Router A Router B
Procedure
NOTE
50 ms.
----End
14.1.4.7 Deleting an Ethernet LAN Service

When an Ethernet LAN service is not used, you can delete the Ethernet LAN service to release
the corresponding resources.
Prerequisite
The Ethernet LAN service must be configured and the service is not used.
Deleting an Ethernet LAN service involves the following tasks:
1. Deleting the VLAN filtering table

2. Deleting the VB mounting relation
Procedure
Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Click Query.
Then, click OK in the dialog box that is displayed.
Step 3 Click the VLAN Filtering tab.
Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete.
Step 5 Click the Service Mount tab.
Step 6 Select the Ethernet LAN service that needs to be deleted and then click Delete.
Step 7 Click Query.
At this time, the Ethernet private line service is already deleted.
----End
14.1.5 Configuring EVPL (QinQ) Services

You can configure EVPL (QinQ) services on a per-NE basis.
14.1.5.1 EVPL(QinQ) Service Configuration Process

This section describes the process for EVPL(QinQ) service configuration process that consists
and verify service.
services.
14.1.5.3 Modifying the Type Field of QinQ Frames
14.1.5.4 Creating QinQ Line Services
To enable the Ethernet switching board to transmit QinQ line services, perform this task to
configure the related information such as service source and service sink.
14.1.5.1 EVPL(QinQ) Service Configuration Process

This section describes the process for EVPL(QinQ) service configuration process that consists
and verify service.

Figure 14-16 shows the process for configuring EVPL(QinQ) services.
Figure 14-16 EVPL(QinQ) service configuration process

Required
Optional

Verify service
Creating and Creating Cross-

Setting External Setting External Test the Ethernet
Configuring NEs Connection
Between Ethernet
Ethernet Boards Ethernet Boards and Line Boards
Creating Fibers
Setting Internal Setting Internal

Communication
Setting Bound Setting Bound

Setting the NE
Paths of Ethernet Paths of Ethernet
Time
Boards Boards
Configuring Clocks Creating Cross- Creating Cross-

and Line Boards and Line Boards
Configuring
Orderwire
Creating Creating
EVPL(QinQ) EVPL(QinQ)
Configuring Services Services
Protection
NOTE
of EVPL(QinQ) service configuration process. They are deploying a network, configure source NE,
configure sink NE, configure pass-through NE and verify service.
services.
Prerequisite
Procedure

Ethernet Ports.
----End

Prerequisite
Precautions
Procedure
Step 3 Click Apply.
----End
Parameters
frames.

Prerequisite

Precautions
Procedure
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.
The system displays the Create Ethernet Line Service dialog box.
NOTE
The result of configuring the port attributes during the Ethernet line service configuration process is the same
as the result of directly configuring the Ethernet service port attributes.

Step 6 Click OK.
----End
Parameters
Service Type EPL, EVPL(QinQ) EPL When creating the QinQ line service, set this
parameter to EVPL(QinQ).

Bidirectional Unidirectional, only the service from
the service source to the service sink is
created.
Bidirectional, both the service from the
service source to the service sink and the
service from the service sink to the
service source are created.
Operation Type Transparently Add S-VLAN l For the meanings of the values, see
transmit C-VLAN, 14.2.2.3 Application of the QinQ
Translate C-VLAN, Technology in Line Services.
Add S-VLAN, l Set this parameter according to actual
Transparently situations.
transmit S-VLAN,
Translate S-VLAN,
Strip S-VLAN (only
for unidirectional
services)
service from a PORT to a VCTRUNK, it
is recommended that you use a specific
PORT as the source port.

Source C-VLAN 1 to 4095 - l You can set this parameter to null, a

(e.g. 1,3-6) number, or several numbers. When you
set this parameter to several numbers,
use "," to separate these discrete values
and use "-" to indicate continuous
numbers. For example, "1, 3-6" indicates
numbers 1, 3, 4, 5, and 6.
l The number of C-VLANs set in this
number of C-VLANs set in Sink C-
VLAN (e.g. 1,3-6).
the service source.
port whose C-VLAN IDs are included in
the set value range of this parameter
work as the service source.
Source S-VLAN 1 to 4095 - l This parameter must be set to a

numerical value.
l Only the services of the source port
whose S-VLAN IDs are equal to the
value of this parameter work as the
service source.
VCTRUNK as the sink port.

Sink C-VLAN (e.g. 1 to 4095 - l You can set this parameter to null, a
1,3-6) number, or several numbers. When you
numbers 1, 3, 4, 5, and 6.
VLAN (e.g. 1,3-6).
service sink.
work as the service sink.
Sink S-VLAN 1 to 4095 - l This parameter must be set to a

numerical value.
l Only the services of the sink port whose
S-VLAN IDs are equal to the value of
this parameter work as the service sink.
C-VLAN Priority AUTO, Priority0- AUTO l This parameter specifies the priority of
Priority7 the newly added C-VLAN tag.
l When this parameter is set to AUTO, the
priority of the C-VLAN tag is 0.
l When QoS operations do not need to be
performed according to the C-VLAN
priority, it is recommended that you use
the default value.
S-VLAN Priority AUTO, Priority0- AUTO l This parameter is valid only when
Priority7 Operation Type is set to Add S-
VLAN.
l This parameter specifies the priority of
the newly added S-VLAN tag.
priority of the S-VLAN tag is 0.
performed according to the S-VLAN
the default value.


Prerequisite
Context
occurs.

NE1 NE2 NE3
Test
Frame
Answer
Frame
Router A Router B
Procedure

NOTE
50 ms.
----End
14.1.6 Configuration Example (Point-to-Point EPL Services)

entire process of configuring the parameters of each NE according to the point-to-point EPL
14.1.6.1 Networking Diagram
14.1.6.2 Service Planning
networking diagram, the network planning department can plan all the parameters that are
required for configuring the new Ethernet services of the NEs.
14.1.6.3 Configuring NE1
You can configure the Ethernet transparent transmission services of NE1 based on the parameters
You can configure the point-to-point Ethernet private line services of NE2 based on the
parameters of the service planning, by using the NMS.

As shown in Figure 14-18, NE1 and NE2 adopt the OptiX RTN 600 NEs configured with the
IDU 620. The new service requirements are as follows:
l The two branches of User A that are located at NE1 and NE2 need communicate with each
other over Ethernet. A 10 Mbit/s bandwidth is required.
l The two branches of User B that are located at NE1 and NE2 need communicate with each
other over Ethernet. A 20 Mbit/s bandwidth is required.
l The service of User A need be isolated from the service of User B.
l The Ethernet equipment of User A and User B provide 100 Mbit/s Ethernet electrical ports
of which the working mode is auto-negotiation, and does not support VLAN.


User A1 User A2
NE 1 NE2
User B1 User B2

In the following example, NE1 and NE2 can use Ethernet transparent transmission boards to
create point-to-point EPL services.

Slot 8 on NE1/NE2 houses the EFT4 board.
Figure 14-19 IDU board configuration
EXT
IF1A Slot7 EXT
EFT4 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PH1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
Ethernet Parameter Configuration
Figure 14-20 Configuring Ethernet services

NE1:8-EFT4 NE2:8-EFT4
PORT1 VCTRUNK1 PORT1

VCTRUNK1
User A1 User A2
VC4-2:VC12:1-5 VC4-2:VC12:1-5
PORT2 VCTRUNK2 PORT2
VCTRUNK2
User B1 User B2
VC4-2:VC12:6-15 VC4-2:VC12:6-15
SDH

Table 14-5 Parameters of external Ethernet ports
Parameter NE1 NE2
Board 8-EFT4 8-EFT4
Port PORT1 PORT2 PORT1 PORT2
Enabled/ Enabled Enabled Enabled Enabled

Disabled
Working Mode Auto- Auto- Auto- Auto-

Negotiation Negotiation Negotiation Negotiation
Maximum 1522 1522 1522 1522

Frame Length
Flow Control Disabled Disabled Disabled Disabled
Table 14-6 Parameters of internal Ethernet ports
Parameter NE1 NE2
Board 8-EFT4 8-EFT4
Port VCTRUNK1 VCTRUNK2 VCTRUNK1 VCTRUNK2
Encapsulation GFP GFP GFP GFP

Mapping
Protocol
LCAS Enabled Enabled Enabled Enabled Enabled
Bound Path VC4-2: VC4-2: VC4-2: VC4-2:

VC12-1- VC12-6- VC12-1- VC12-6-
VC12-5 VC12-15 VC12-5 VC12-15
Figure 14-21 Timeslot allocation of Ethernet services
Station
NE1 NE2
Timeslot 5-IF1A-1 5-IF1A1-1
VC12:17-21
1#VC4 8-EFT4 8-EFT4
VC4-2:1-5 VC4-2:1-5
VC12:22-31
8-EFT4 8-EFT4
VC4-2:6-15 VC4-2:6-15
Add/Drop

l The EPL service of User A is as follows:

Occupies VC-12 timeslots 17-21 of the first VC-4 on the radio link between NE1 and
NE2.
Uses VC-12 timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE1 and
VC-12 timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/drop
services.
l The EPL service of User B is as follows:
NE2.
Uses VC-12 timeslots 6-15 in the second VC-4 of the EFT4 board in slot 8 of NE1 and
VC-12 timeslots 6-15 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/
drop services.

You can configure the Ethernet transparent transmission services of NE1 based on the parameters
Prerequisite
The EFT4 board must be added.
Procedure
Step 1 Configure Ethernet external ports.
1. In the NE Explorer, select the EFT4 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2. Click the Basic Attributes tab. After setting the parameters, click Apply.
Port PORT1 PORT2 l The basic attributes of PORT1 and

PORT2 need to be set.
l The services of user A1 use PORT1
and the services of user B1 use
PORT2.
Enabled/ Enabled In the case of the port that accesses

Disabled services, set this parameter to Enabled.
Working Auto-Negotiation The Ethernet equipment of users work

Mode in auto-negotiation mode. Hence, the
Working Mode of the external ports
should be set to Auto-Negotiation.
Step 2 Configure Ethernet internal ports.

1. In the NE Explorer, select the EFT4 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select Internal
Port. Set the parameters of VCTRUNK1 and VCTRUNK2.
2. Set the encapsulation and mapping protocol used by the port.
a. Click the Encapsulation/Mapping tab.
b. Set Mapping Protocol and the protocol parameters. After setting the parameters, click
Apply.
Paramete Value Range Description

r
Port VCTRUN VCTRU l The mapping protocol needs to be set for

K1 NK2 VCTRUNK1 and VCTRUNK2.
l In this example, Mapping Protocol is set to
Mapping GFP
GFP.
Protocol
3. Configure the LCAS function of the VCTRUNKs.

a. Click the LCAS tab.
b. Set Enabling LCAS and other LCAS parameters. After setting the parameters, click
Apply.

r
Port VCTRU VCTRUN Enabling LCAS needs to be set for VCTRUNK1

NK1 K2 and VCTRUNK2.
Enabling Enabled l In this example, the LCAS function is

LCAS enabled.
number of virtual containers for mapping
required services to meet the bandwidth
requirements of the application. As a result,
the bandwidth utilization ratio is improved.
4. Set the VC paths to be bound with the VCTRUNKs.

a. Click the Bound Path tab.
b. Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
c. In Configurable Ports, select VCTRUNK1 and VCTRUNK2 as the ports to be
configured.
d. In Available Bound Paths, set Level and Service Direction of the bound paths. After
setting the parameters, click OK. Then, click Yes in the dialog box that is displayed.

r
Configura VCTRUN VCTRUN In this example, VCTRUNK1 and

ble Ports K1 K2 VCTRUNK2 need to be bound with VC paths.


r
Level VC12 In this example, the bound path is at the VC-12

level.
Service Bidirectional l If Service Direction is set to

Direction Bidirectional, the services from the service
source to the service sink and from the
service sink to the service source are
created.
default value.
Available VC4-2 In this example, VC4-2 is the available

Resources resource.
Available VC12-1 to VC12-6 to l VCTRUNK1 is bound with timeslots

Timeslots VC12-5 VC12-15 VC12-1 to VC12-5.
l VCTRUNK2 is bound with timeslots
VC12-6 to VC12-15.
Activation Activated Indicates that VCTRUNK1 and VCTRUNK2

Status are active.
Step 3 Create the cross-connections of Ethernet services.

1. In the NE Explorer, select NE1 from the Object Tree and then choose Configuration >
SDH Service Configuration from the Function Tree.
2. Click Create. The Create SDH Service dialog box is displayed. After setting the
parameters. Then, click OK.
l Set the parameters of the cross-connections of VCTRUNK1 as follows.
Level VC12 In this example, the cross-connection is at

the VC-12 level.
Direction Bidirectional l If Direction is set to Bidirectional, the

services from the service source to the
service sink and from the service sink
to the service source are created.
l In this example, this parameter adopts
the default value.

source.
Source Timeslot 17-21 In this example, the timeslots to which the

Range(e.g.1,3-6) service source corresponds are timeslots
17-21.

Sink 8-EFT4 In this example, the 8-EFT4 is the service

sink.
Sink VC4 VC4-2 In this example, the service sink is located

in VC4-2.

Range(e.g.1,3-6) service sink corresponds are timeslots 1-5.
Activate Yes Delivers the configured cross-connection

Immediately to NEs immediately.
Level VC12 In this example, the cross-connection is at

the VC-12 level.

service sink and from the service sink
to the service source are created.
l In this example, this parameter adopts
the default value.

source.
Source Timeslot 22-31 In this example, the timeslots to which the

Range(e.g.1,3-6) service source corresponds are timeslots
22-31.
Sink 8-EFT4 In this example, the 8-EFT4 is the service

sink.
Sink VC4 VC4-2 In this example, the service sink is located

in VC4-2.

Range(e.g.1,3-6) service sink corresponds are timeslots
6-15.
Activate Yes Delivers the configured cross-connection

Immediately to NEs immediately.
----End

You can configure the point-to-point Ethernet private line services of NE2 based on the

The procedures for configuring NE2 are the same as the procedures for configuring NE1. For
details, see 14.1.6.3 Configuring NE1.
14.1.7 Configuration Example (PORT-Shared EVPL Services)

entire process of configuring the parameters of each NE according to the PORT-shared EVPL
You can configure the PORT-shared Ethernet private line services of NE1 based on the
14.1.7.4 Configuring NE2 and NE3
You can configure the Ethernet services of NE2 and NE3 based on the parameters of the service

As shown in Figure 14-22, NE1, NE2, and NE3 are the OptiX RTN 600 NEs that are configured
with the IDU 620. 16xE1 services exist between NE1, NE2, and NE3. The new service
l The headquarters C1 of User C are located at NE1 and the two branches of User C (C2 and
C3) are located at NE2 and NE3. The services between C1 and C2 are transmitted in the
VLAN of which the VLAN ID ranges from 100 to 110. The services between C1 and C3
are transmitted in the VLAN of which the VLAN ID ranges from 200 to 210.
l The services of C2 are isolated from the services of C3. The services of C2 and C3 require
a 20 Mbit/s bandwidth respectively.
l The Ethernet equipment of C1, C2, and C3 provide 100 Mbit/s Ethernet electrical ports of
which the working mode is auto-negotiation, and supports VLAN.

User C2
NE 1 NE2
User C1
VLAN100-110
VLAN200-210
NE3
User C3


In the following example, NE1 needs to use Ethernet switching boards to create PORT-shared
EVPL services. NE2 and NE3 can use Ethernet transparent transmission boards to create PORT-
shared EVPL services.

Slot 8 of NE1 houses the EMS6 board. Slot 8 on NE2/NE3 houses the EFT4 board.
EXT
IF1A Slot7 EXT
EMS6 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PD1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
EXT Slot7 EXT

EFT4 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PH1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2

NE2:8-EFT4
VCTRUNK1 PORT1
NE1:8-EMS6 User C2
VC4-2:VC12:1-10
VCTRUNK1
PORT1 VC4-2:VC12:1-10
User C1
VCTRUNK2
VC4-2:VC12:11-20 NE3:8-EFT4
VCTRUNK1 PORT1
User C3
VC4-2:VC12:1-10
SDH

Board 8-EMS6 8-EFT4 8-EFT4
Port PORT1 PORT1 PORT1
Enabled/Disabled Enabled Enabled Enabled
Working Mode Auto-Negotiation Auto-Negotiation Auto-Negotiation
Maximum Frame 1522 1522 1522

Length
Flow Control Disabled Disabled Disabled
TAG Tag Aware - -
Entry Detection Enabled - -

Mapping
Protocol
Enabling LCAS Enabled Enabled Enabled Enabled
TAG Tag Aware Tag Aware - -
Entry Detection Enabled Enabled - -

VC12-1- VC12-11- VC12-1- VC12-1-
VC12-10 VC12-20 VC12-10 VC12-10
Table 14-9 Parameters of EPL services
Parameter NE1
Private Line Service 1 Private Line Service 2
Board 8-EMS
Service Type EPL

Parameter NE1
Private Line Service 1 Private Line Service 2
Direction Bidirectional
Source Port PORT1 PORT1
Source C-VLAN (e.g. 1,3-6) 100-110 200-210
Sink Port VCRTUNK1 VCTRUNK2
Sink C-VLAN (e.g. 1,3-6) 100-110 200-210
Station
NE2 NE1 NE3
Timeslot 5-IF1A-1 5-IF1A1-1 7-IF1A1-1 5-IF1A1-1
VC12:17-26 VC12:17-26
1#VC4 8-EMS6 8-EMS6
8-EFT4 8-EFT4
VC4-2:1-10 VC4-2:1-10 VC4-2:11-20 VC4-2:1-10
Add/Drop
l The EVPL service from C1 to C2 is as follows:

NE2.
Uses VC-12 timeslots 1-10 in the second VC-4 of the EMS6 board in slot 8 of NE1 and
VC-12 timeslots 1-10 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/
drop services.
l The EVPL service from C1 to C3 is as follows:
NE3.
Uses VC-12 timeslots 11-20 in the second VC-4 of the EMS6 board in slot 8 of NE1
and VC-12 timeslots 1-20 in the second VC-4 of the EFT4 board in slot 8 of NE3 to
add/drop services.

You can configure the PORT-shared Ethernet private line services of NE1 based on the
Prerequisite

The EMS6 board must be added.
Procedure
1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Port.
Port PORT1 l Set the basic attributes of PORT1.

l The services of user C1 use PORT1.
Enabled/ Enabled In the case of the port that accesses services, set
Disabled this parameter to Enabled.
Working Mode Auto- The Ethernet equipment of users work in auto-

Negotiation negotiation mode. Hence, the Working Mode of
the external ports should be set to Auto-
Negotiation.
3. Click the TAG Attributes tab. After setting the parameters, click Apply.
Port PORT1 l The tag attributes of PORT1 need to be set.

l The services of user C1 use PORT1.
TAG Tag Aware l If TAG is set to Tag Aware, the packets that
carry VLAN tags are received.
l If TAG is set to Tag Aware, the packets that
do not carry VLAN tags are discarded.
Entry Detection Enabled In this example, the incoming packets from the
port need to be checked according to the tag
attributes.

Port. Set the parameters of VCTRUNK1 and VCTRUNK2.
Apply.


r
Port VCTRUN VCTRU l The encapsulation protocol needs to be set for

Mapping GFP
GFP.
Protocol

Apply.

r


LCAS enabled.
Port VCTRUNK1 VCTRUNK2 TAG Attributes need to be set for

VCTRUNK1 and VCTRUNK2.
TAG Tag Aware l If TAG is set to Tag Aware, the

packets that carry VLAN tags are
received.
l If TAG is set to Tag Aware, the
packets that do not carry VLAN tags
are discarded.
Entry Enabled In this example, the incoming packets

Detection from the port need to be checked
according to the tag attributes.

c. In Configurable Ports, select VCTRUNK1 as the port to be configured.

d. In Available Bound Paths, set Level and Direction of the bound paths. After setting
the parameters, click OK. Then, click Yes in the dialog box that is displayed.

r


level.

created.
default value.

Resources resource.
Available VC12-1 to VC12-11 l VCTRUNK1 is bound with timeslots

Timeslots VC12-10 to VC12-1 to VC12-10.
VC12-20 l VCTRUNK1 is bound with timeslots
VC12-11 to VC12-20.

Status are active.
Step 3 Create Ethernet private line services.

2. Click New. The Create Ethernet Line Service dialog box is displayed. After setting the
parameters, click OK.
l Set the parameters of the Ethernet private line services on PORT1 and VCTRUNK1 as
follows.
Service Direction Bidirectional l If Service Direction is set to

Bidirectional, the services from the
the service sink to the service source are
created.
default value.
Source Port PORT1 In this example, PORT1 is the service source

port.

Source VLAN 100-110 The services whose VLAN IDs range from
(e.g. 1,3-6) 100 to 110 are the source services.
Sink Port VCTRUNK1 In this example, the VCTRUNK1 is the

service sink port.
Sink VLAN (e.g. 100-110 The services whose VLAN IDs range from
1,3-6) 100 to 110 are the sink services.
follows.

created.
default value.

port.
Source VLAN 200-210 The services whose VLAN IDs range from
(e.g. 1,3-6) 200 to 210 are the source services.
Sink Port VCTRUNK2 In this example, the VCTRUNK2 is the

service sink port.
Sink VLAN (e.g. 200-210 The services whose VLAN IDs range from
1,3-6) 200 to 210 are the sink services.

Level VC12 In this example, the cross-connection is at the

VC-12 level.


default value.

source.

Range(e.g.
1,3-6)
Sink 8-EMS6 In this example, the 8-EMS6 is the service sink.
Sink VC4 VC4-2 In this example, the service sink is located in

VC4-2.

1,3-6)
Activate Yes Delivers the configured cross-connection to

Immediately NEs immediately.

VC-12 level.

default value.

source.

Range(e.g.
1,3-6)

VC4-2.


1,3-6)

----End

The Ethernet services of NE2 and NE3 are point-to-point EPL services, and therefore should be
configured according to the configuration example of point-to-point EPL services. For details,
see 14.1.6.3 Configuring NE1.
14.1.8 Configuration Example (VCTRUNK-Shared EVPL Services)

entire process of configuring the parameters of each NE according to the VCTRUNK-shared
EVPL service requirements.

You can configure the VCTRUNK-shared Ethernet private line services of NE1 based on the

As shown in Figure 14-27, NE1 and NE2 are the OptiX RTN 600 NEs configured with the IDU
620. 16xE1 services exist between NE1 and NE2. The new service requirements are as follows:
l The two branches of User D are located at NE1 and NE2, and need to communicate with
each other.

l The two branches of User E are located at NE1 and NE2, and need to communicate with
each other.
l The services of User D need to be isolated from the services of User E. The traffic of User
D and User E, however, is supplementary to each other, and thus can share the 20 Mbit/s
bandwidth.
l The Ethernet equipment of User D and User E provide 100 Mbit/s Ethernet electrical ports

User D1 User D2
NE 1 NE2 12
User E1 User E2

In the following example, NE1 and NE2 need to use Ethernet switching boards to create
VCTRUNK-shared EVPL services.

Slot 8 on NE1/NE2 houses the EMS6 board.
EXT Slot7 EXT

EMS6 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PH1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2


NE1:8-EMS6 NE2:8-EMS6
PORT1 PORT1
User D1 EPL1 EPL1 User D2
VCTRUNK1 VCTRUNK1
PORT2 VC4-2:VC12:1-10 VC4-2:VC12:1-10 PORT2
User E1 EPL2 EPL2 User E2
SDH
Parameter NE1 NE2
Board 8-EMS6 8-EMS6
Port PORT1 PORT2 PORT1 PORT2

Disabled

Maximum 1522 1522 1522 1522

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

ID
VLAN Priority 0 0 0 0
Parameter NE1 NE2
Board 8-EMS6 8-EMS6
Port VCTRUNK1 VCTRUNK1
Encapsulation Mapping GFP GFP

Protocol
Enabling LCAS Enabled Enabled

Parameter NE1 NE2
TAG Tag Aware Tag Aware
Entry Detection Enabled Enabled
Bound Path VC4-2: VC12-1-VC12-10 VC4-2: VC12-1-VC12-10
Table 14-12 Parameters of EPL services
Parameter NE1 NE2
EPL Service 1 EPL Service 2 EPL Service 1 EPL Service 2
Board 8-EMS 8-EMS
Service Type EPL EPL
Direction Bidirectional Bidirectional
Source Port PORT1 PORT2 PORT1 PORT2
Source C- 100 200 100 200

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

(e.g. 1,3-6)
Station
NE1 NE2
Timeslot 5-IF1A-1 5-IF1A1-1
VC12:17-26
1#VC4
8-EMS6 8-EMS6
VC4-2:1-10 VC4-2:1-10
Add/Drop
l The VCTRUNK-shared EVPL services of User D and User E occupy VC-12 timeslots
17-26 in the first VC-4 on the radio link from NE1 to NE2.
l VC-12 timeslots 1-10 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12
timeslots 1-10 in the second VC-4 of the EMS6 board in slot 8 of NE2 are used to add/drop
the services.


Prerequisite
Procedure
Port.

l The services of user D1 use PORT1
and the services of user E1 use
PORT2.


Port PORT1 PORT2 l The tag attributes of PORT1 and

l The services of user D1 use PORT1
and the services of user E1 use
PORT2.
TAG Access If TAG is set to Access:

l The packets that carry VLAN tags
are discarded.
l The packets that do not carry VLAN
tags are tagged with Default VLAN
ID and are then received.

Default 100 200 l In this example, Default VLAN ID

VLAN ID is set to 100 for PORT1.
l In this example, Default VLAN ID
is set to 200 for PORT2.


Port.
Apply.
Parameter Value Description

Range
Port VCTRUNK l The encapsulation protocol of VCTRUNK1 needs to

1 be set.
l In this example, Mapping Protocol is set to GPF.
Mapping GFP
Protocol
3. Configure the LCAS function of the VCTRUNK.

Apply.
Parameter Value Description

Range
Port VCTRUN In this example, Enabling LCAS needs to be set for

K1 VCTRUNK1.
Enabling Enabled l In this example, the LCAS function is enabled.

LCAS l The LCAS can dynamically adjust the number of
virtual containers for mapping required services to
meet the bandwidth requirements of the application. As
a result, the bandwidth utilization ratio is improved.

Port VCTRUNK1 The tag attributes of VCTRUNK1 need to be set.
TAG Tag Aware l If TAG is set to Tag Aware, the packets that
carry VLAN tags are received.
Entry Detection Enabled In this example, the incoming packets from the
attributes.

c. In Configurable Ports, select VCTRUNK1 as the port to be bound.

r
Configura VCTRUNK1 In this example, VCTRUNK1 needs to be

ble Ports bound with VC paths.

level.

created.
default value.

Resources resource.
Available VC12-1 to VC12-10 l VCTRUNK1 is bound with timeslots

Timeslots VC12-1 to VC12-10.
VC12-11 to VC12-20.

Status are active.
Step 3 Create Ethernet private line services.

2. Click New. The Create Ethernet Line Service dialog box is displayed. After setting the
follows.

created.
default value.

port.
Source VLAN 100 The service that has the VLAN ID of 100 is
(e.g. 1,3-6) the source service.
Sink Port VCTRUNK1 In this example, VCTRUNK1 is the service

sink port.
Sink VLAN (e.g. 100 The service that has the VLAN ID of 100 is
1,3-6) the sink service.
follows.

created.
default value.

port.
Source VLAN 200 The service that has the VLAN ID of 200 is
(e.g. 1,3-6) the source service.
Sink Port VCTRUNK1 In this example, VCTRUNK1 is the service

sink port.
Sink VLAN (e.g. 200 The service that has the VLAN ID of 200 is
1,3-6) the sink service.


1. In the NE Explorer, select NE1 and then choose Configuration > SDH Service
2. Click Create.
Then, the Create SDH Service dialog box is displayed. Click OK.
Level VC12 In this example, the cross-connection is at the VC-12

level.
Direction Bidirectional l When Direction is set to Bidirectional, create

the cross-connections from the service source to
the service sink and from the service sink to the
service source.
value.
Source 5-IF1A In this example, the 5-IF1A is the service source.
Source Timeslot 17-26 In this example, the timeslots to which the service
Range(e.g.1,3-6) source corresponds are timeslots 17-26.
Sink VC4 VC4-2 In this example, the service sink is located in VC4-2.
Range(e.g.1,3-6) sink corresponds are timeslots 1-10.
Activate Yes Delivers the configured cross-connection to NEs

Immediately immediately.
----End

The procedures for configuring NE2 are the same as the procedures for configuring NE1. For
details, see 14.1.8.3 Configuring NE1.
14.1.9 Configuration Example (802.1d Bridge-Based EPLAN

Services)
802.1d bridge-based EPLAN services.



You can configure the transparent bridge-based Ethernet LAN services of NE1 based on the

l The three branches of User F, which are F1, F2, and F3, are located at NE1, NE2, and NE3.
F1 need communicate with F2 and F3, and thus a 10 Mbit/s bandwidth is required.
Communication is not required between F2 and F3.
l The Ethernet equipment of User F provides 100 Mbit/s Ethernet electrical ports, of which
the working mode is auto-negotiation, and supports VLAN. The VLAN ID and the number
of the VLANs are unknown and may be changed.

NE2
User F2
NE 1
User F1
NE3
User F3


In the following example, the 802.1q VB is used to implement EPLAN services of which the
user VLAN is not defined. NE1 needs to be configured with Ethernet switching boards. NE2
and NE3 need to be configured with Ethernet transparent transmission boards.

EXT
IF1A Slot7 EXT
EMS6 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PD1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
EXT Slot7 EXT

EFT4 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PH1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2

NE2:8-EFT4
VCTRUNK1 PORT1
NE1:8-EMS6 User F2
VC4-2:VC12:1-5
VCTRUNK1
PORT1 VC4-2:VC12:1-5
User F1
VCTRUNK2
VC4-2:VC12:6-10 NE3:8-EFT4
VB1
VCTRUNK1 PORT1
User F3
VC4-2:VC12:1-5
SDH


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

Length
Flow Control Disabled Disabled Disabled
Entry Detection Disabled - -


Mapping
Protocol
Enabling LCAS Enabled Enabled Enabled Enabled
Entry Detection Disabled Disabled - -

VC12-1- VC12-6- VC12-1- VC12-1-
VC12-5 VC12-10 VC12-5 VC12-5
Table 14-15 Parameters of Ethernet LAN services

Parameter Ethernet LAN services of NE1
Board 8-EMS
VB Name VB1
VB Type 802.1d
Bridge Switch Mode IVL/Ingress Filter Enable
VB Mount Port PORT1, VCTRUNK1, VCTRUNK2
Hub/Spoke PORT1 Hub
VCTRUNK1 Spoke
VCTRUNK2 Spoke

Station
NE2 NE1 NE3
VC12:17-21 VC12:17-21
1#VC4 8-EMS6 8-EMS6
8-EFT4 8-EFT4
8-EMS6
VC4-2:1-5 VC4-2:1-5 VC4-2:6-10 VC4-2:1-5
VC4-2:6-15
Add/Drop
l The Ethernet LAN service of User F occupies VC-12 timeslots 17-21 in the first VC-4 on
the radio link from NE1 to NE2 and VC-12 timeslots 17-21 in the first VC-4 on the radio
link from NE1 to NE3.
timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/drop the Ethernet
LAN service from NE1 to NE2.
timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE3 to add/drop the Ethernet
LAN service from NE1 to NE3.

You can configure the transparent bridge-based Ethernet LAN services of NE1 based on the
Prerequisite
Procedure
Port.
Port PORT1 l The basic attributes of PORT1 need to be set.

l The services of user F1 use PORT1.


Negotiation.

l The services of user F1 use PORT1.
Entry Detection Disabled If Entry Detection is set to Disabled, the VLAN

IDs of the packets are not checked.

Port. Set the parameters of VCTRCUNK1 and VCTRCUNK2.
Apply.

r
Port VCTRUN VCTRU l The encapsulation protocol needs to be set for

Mapping GFP
GFP.
Protocol

Apply.

r



r

LCAS enabled.
Port VCTRUNK1 VCTRUNK2 TAG Attributes need to be set for

VCTRUNK1 and VCTRUNK2.
Entry Disabled If Entry Detection is set to Disabled,

Detection the VLAN IDs of the packets are not
checked.


r


level.

created.
default value.

Resources resource.


r
Available VC12-1 to VC12-6 to l VCTRUNK1 is bound with timeslots

Timeslots VC12-5 VC12-10 VC12-1 to VC12-5.
VC12-6 to VC12-10.

Status are active.
Step 3 Create Ethernet LAN services.

2. Click New. The Create Ethernet LAN Service dialog box is displayed. Set the parameters
as follows.
VB Name VB1 In this example, VB Name is set to VB1.
VB Type 802.1d In this example, an IEEE 802.1d bridge is created.
Bridge Switch SVL/Ingress In this example, a transparent bridge is created,

Mode Filter Disable and the VLAN IDs of the packets over each port
(802.1d) need not be checked.
3. Click Configure Mount. The Service Mount Configuration dialog box is displayed. After
setting the parameters, click OK.
selected PORT1, PORT1, VCTRUNK1, and VCTRUNK2 are

forwarding VCTRUNK1, connected to the bridge.
ports VCTRUNK2
4. Click OK.
Step 4 Modify the mounted port of bridge.
2. Select the created bridge. Click the Service Mount tab. After setting the parameters, click
Apply.


er
Mount PORT1 VCTRUN VCTRUN l Select PORT1, VCTRUNK1,

Port K1 K2 and VCTRUNK2 as the mount
ports.
l Only the port that is selected as
Mount Port of a bridge
functions in the packet
forwarding process of the
bridge.
Hub/ Hub Spoke Spoke The Spoke ports cannot access

Spoke each other. The Hub port and the
Spoke port can access each other.
The Hub ports can access each
other.
Activatio Activated Indicates that the VCTRUNK is

n Status active.


VC-12 level.

default value.

source.

Range(e.g.
1,3-6)

VC4-2.


1,3-6)


VC-12 level.

default value.

source.

Range(e.g.
1,3-6)

VC4-2.

1,3-6)

----End

The Ethernet service of NE2/NE3 is a point-to-point EPL service, and therefore should be

14.1.10 Configuration Example (802.1q Bridge-Based EVPLAN

Services)
802.1q bridge-based EVPLAN services.

You can configure the 802.1q bridge-based EVPLAN services of NE1 based on the parameters

l The three branches of User G are located at NE1, NE2, and NE3 respectively, need form
a LAN, and share a 10 Mbit/s bandwidth.
l The three branches of User H are located at NE1, NE2, and NE3 respectively, need form
a LAN, and share a 20 Mbit/s bandwidth.
l The service of User G need be isolated from the service of User H.
l The Ethernet equipment of User G and User H provide 100 Mbit/s Ethernet electrical ports

NE2 User G2
User H2
User G1
NE 1
User H1
User G3
NE3
User H3

In the following example, NE1 needs to use Ethernet switching boards to create Ethernet LAN
services. NE2 and NE3 can use Ethernet transparent transmission boards to create Ethernet LAN
services.

EXT
IF1A Slot7 EXT
EMS6 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PD1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2

EXT Slot7 EXT

EFT4 Slot8
EXT
FAN
FAN
PXC
PXC Slot3 EXT
PH1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
Configuring Ethernet Services

Based on the networking diagram, you can plan the configuration diagram and parameters of
the Ethernet services on the two VLANs that are implemented by using the 802.1q network
bridge.

NE2:8-EFT4
VCTRUNK1 PORT1
User G2
NE1:8-EMS6 VC4-2:VC12:1-5
VCTRUNK2 PORT2
VLAN 100 User H2
VCTRUNK1 VC4-2:VC12:6-15
PORT1 VC4-2:VC12:1-5
User G1
VCTRUNK2
VC4-2:VC12:6-10
VLAN 200 VCTRUNK3 NE3:8-EFT4
PORT2
VC4-2:VC12:11-20
User H1
VCTRUNK4 VCTRUNK1 PORT1
User G3
VC4-2:VC12:21-30 VC4-2:VC12:1-5
VB1 VCTRUNK2 PORT2
User H3
VC4-2:VC12:6-15
SDH
Paramete NE1 NE2 NE3

r
Port PORT1 PORT2 PORT1 PORT2 PORT1 PORT2
Enabled/ Enabled Enabled Enabled Enabled Enabled Enabled

Disabled
Working Auto- Auto- Auto- Auto- Auto- Auto-

Mode Negotiatio Negotiatio Negotiatio Negotiatio Negotiatio Negotiatio
n n n n n n

Paramete NE1 NE2 NE3

r
Maximum 1522 1522 1522 1522 1522 1522

Frame
Length
Flow Disabled Disabled Disabled Disabled Disabled Disabled

Control
TAG Access Access - - - -
Entry Enabled Enabled - - - -

Detection
Default 100 200 - - - -

VLAN ID
VLAN 0 0 - - - -
Priority

Param NE1 NE2 NE3
eter
Port VCTR VCTR VCTR VCTR VCTR VCTR VCTR VCTR

UNK1 UNK2 UNK3 UNK4 UNK1 UNK2 UNK1 UNK2
Encaps GFP GFP GFP GFP GFP GFP GFP GFP

ulation
Mappin
g
Protoco
l
Enablin Enable Enable Enable Enable Enable Enable Enable Enable

g d d d d d d d d
LCAS
TAG Access Access Access Access - - - -
Entry Enable Enable Enable Enable - - - -

Detecti d d d d
on
Default 100 100 200 200 - - - -

VLAN
ID
VLAN 0 0 0 0 - - - -
Priority

Param NE1 NE2 NE3

eter
Bound VC4-2: VC4-2: VC4-2: VC4-2: VC4-2: VC4-2: VC4-2: VC4-2:

Path VC12- VC12- VC12- VC12- VC12- VC12- VC12- VC12-
1- 6- 11- 21- 1- 6- 1- 6-
VC12- VC12- VC12- VC12- VC12- VC12- VC12- VC12-
5 10 20 30 5 15 5 15
Table 14-18 Parameters of Ethernet LAN services
Parameter Ethernet LAN services of NE1
Board 8-EMS
VB Name VB1
VB Type 802.1q
Bridge Switch Mode IVL/Ingress Filter Enable
Mount Port PORT1, PORT2, VCTRUNK1, VCTRUNK2, VCTRUNK3,

VCTRUNK4
VLAN Filtering VLAN Filtering Table 1 VLAN Filtering Table 2

Filtering Table
Table
VLAN ID 100 200
Forwarding PORT1, VCTRUNK1, PORT2, VCTRUNK3,

Port VCTRUNK2 VCTRUNK4
Station
NE2 NE1 NE3
VC12:17-21 VC12:17-21
1#VC4 8-EFT4 8-EMS6 8-EMS6 8-EFT4
VC4-2:1-5 VC4-2:1-5 VC4-2:6-10 VC4-2:1-5
VC12:22-31 VC12:22-31
8-EFT4 8-EMS6 8-EMS6 8-EFT4
VC4-2:6-15 VC4-2:11-20 VC4-2:21-30 VC4-2:6-15
Add/Drop
l The Ethernet LAN service of User G:

Occupies VC-12 timeslots 17-21 in the first VC-4 on the radio link from NE1 to NE2
and VC-12 timeslots 17-21 in the first VC-4 on the radio link from NE1 to NE3.
services between NE1 and NE2.
services between NE1 and NE3.
l The Ethernet LAN service of User H:
Occupies VC-12 timeslots 22-31 in the first VC-4 on the radio link from NE1 to NE2
and VC-12 timeslots 22-31 in the first VC-4 on the radio link from NE1 to NE3.
add/drop services between NE1 and NE2.
add/drop services between NE1 and NE3.

You can configure the 802.1q bridge-based EVPLAN services of NE1 based on the parameters
Prerequisite
Procedure
Port.

l The services of user G1 use PORT1
and the services of user H1 use
PORT2.



Port PORT1 PORT2 l The tag attributes of PORT1 and

l The services of user G1 use PORT1
and the services of user H1 use
PORT2.
TAG Access l If TAG is set to Access, the packets

that carry VLAN tags are discarded.
l If TAG is set to Access, the packets
that do not carry VLAN tags are
tagged with Default VLAN ID and
are then received.
Default 100 200 l In this example, Default VLAN ID

VLAN ID is set to 100 for PORT1.
l In this example, Default VLAN ID
is set to 200 for PORT2.


Port.
Apply.
Param Value Range Description

eter
Port VCTRU VCTRU VCTR VCTRU l The encapsulation protocol

NK1 NK2 UNK3 NK4 needs to be set for
VCTRUNK1, VCTRUNK2,
VCTRUNK3, and
VCTRUNK4.


eter
Mappi GFP l In this example, Mapping

ng Protocol is set to GFP.
Protoc
ol

Apply.

eter
Port VCTRU VCTRU VCTR VCTRU Enabling LCAS needs to be set

NK1 NK2 UNK3 NK4 for VCTRUNK1, VCTRUNK2,
VCTRUNK3, and VCTRUNK4.
Enabli Enabled l In this example, the LCAS

ng function is enabled.
LCAS l The LCAS can dynamically
adjust the number of virtual
containers for mapping
required services to meet the
bandwidth requirements of
the application. As a result,
the bandwidth utilization
ratio is improved.
eter
Port VCTRU VCTRU VCTR VCTRU TAG Attributes need to be set

NK1 NK2 UNK3 NK4 for VCTRUNK1, VCTRUNK2,
VCTRUNK3, and VCTRUNK4.
TAG Access l If TAG is set to Access, the

packets that carry VLAN tags
are discarded.
l If TAG is set to Access, the
packets that do not carry
VLAN tags are tagged with
Default VLAN ID and
VLAN Priority and are then
received.


eter
Entry Enabled In this example, the incoming

Detecti packets from the port need to be
on checked according to the tag
attributes.


eter
Config VCTRU VCTRU VCTR VCTRU In this example, VCTRUNK1,

urable NK1 NK2 UNK3 NK4 VCTRUNK2, VCTRUNK3, and
Ports VCTRUNK4 are used to bind
VC paths.
Level VC12 In this example, the bound path

is at the VC-12 level.

Directi Bidirectional, the services
on from the service source to the
service sink and from the
service sink to the service
source are created.
l In this example, this
parameter adopts the default
value.
Availa VC4-2 In this example, VC4-2 is the

ble available resource.
Resour
ces


eter
Availa VC12-1 VC12-6 VC12- VC12-2 l VCTRUNK1 is bound with

ble to to 11 to 1 to timeslots VC12-1 to VC12-5.
Timesl VC12-5 VC12-1 VC12- VC12-3 l VCTRUNK2 is bound with
ots 0 20 0 timeslots VC12-6 to
VC12-10.
l VCTRUNK3 is bound with
timeslots VC12-11 to
VC12-20.
l VCTRUNK4 is bound with
timeslots VC12-21 to
VC12-30.
Activat Activated Indicates that VCTRUNK1,

ion VCTRUNK2, VCTRUNK3, and
Status VCTRUNK4 are active.

as follows.
VB Type 802.1q In this example, an IEEE 802.1q bridge is created.
Bridge Switch IVL/Ingress If the ingress filter is enabled, the VLAN tags are
Mode Filter Enable checked at the ingress port. If the VLAN ID does
(802.1q) not equal the VLAN ID of the port defined in the
VLAN filtering table, the packet is discarded.
selected PORT1, PORT2, PORT1, PORT2, VCTRUNK1, VCTRUNK2,

forwarding VCTRUNK1, VCTRUNK3, and VCTRUNK4 are connected
ports VCTRUNK2, to the bridge.
VCTRUNK3,
VCTRUNK4
4. Click OK.
Step 4 Create a VLAN filtering table.

2. Select the created bridge. Click the VLAN Filtering tab. After setting the parameters, click
OK.
Set the parameters of VLAN filtering table 1 as follows.
VLAN ID(e.g: 100 -

1,3-6)

ports VCTRUNK2
Set the parameters of VLAN filtering table 2 as follows.
VLAN ID(e.g: 200 -

1,3-6)

ports VCTRUNK4

2. Click Create. Then, the Create SDH Service dialog box is displayed. After setting the

VC-12 level.

default value.

source.


Range(e.g.
1,3-6)

VC4-2.

1,3-6)



VC-12 level.

default value.

source.

Range(e.g.
1,3-6)

VC4-2.

1,3-6)



VC-12 level.

default value.

source.

Range(e.g.
1,3-6)

VC4-2.

1,3-6)


VC-12 level.

default value.

source.

Range(e.g.
1,3-6)


VC4-2.

1,3-6)

----End

The Ethernet service of NE2/NE3 is a point-to-point EPL service, and therefore should be
14.1.11 Configuration Example (EVPL Services Based on QinQ)

This topic provides an example to describe how to configure QinQ line services.
Precautions
NOTE
For details on the services configured in this example, see the description of the EVPL service that is based on
QinQ in 14.2.6.1 EVPL Services Based on QinQ.
Procedure
Step 1 Set the attributes of the ports of NE1 and NE4. For details, see 14.3.7.1 Configuring External
Ethernet Ports.
Step 2 Set the attributes of the VCTRUNKs of NE1-NE4. For details, see 14.4.7.1 Configuring the
Internal Port of the Ethernet Board.
Step 3 Configure a QinQ service from PORT1 to VCTRUNK1 of NE1. For details, see 14.1.5.4
Creating QinQ Line Services.
l Set Direction to Bidirectional.
l Set Operation Type to Add S-VLAN.
l Set Source Port to PORT1.
l Do not set Source C-VLAN (e.g. 1,3-6).
l Set Sink Port to VCTRUNK1.
l Do not set Sink C-VLAN (e.g. 1,3-6).

l Set Sink S-VLAN to 100.

Step 4 Configure a QinQ service from PORT2 to VCTRUNK1 of NE1. For details, see 14.1.5.4
Creating QinQ Line Services.
l Set Operation Type to Add S-VLAN.
l Do not set Source C-VLAN (e.g. 1,3-6).
l Do not set Sink C-VLAN (e.g. 1,3-6).
Step 5 Configure the QinQ services of NE4. For details, see Steps Step 3-Step 4.
Step 6 Configure the QinQ service to which the traffic stream of customer a at NE2 corresponds. For
details, see 14.1.5.4 Creating QinQ Line Services.
l Set Operation Type to Transparently transmit S-VLAN.
l Set Source S-VLAN to 100.
Step 7 Configure the QinQ service to which the traffic stream of customer b at NE2 corresponds. For
l Set Operation Type to Transparently transmit S-VLAN.
Step 8 Configure the QinQ service to which the traffic stream of customer a at NE3 corresponds. For
l Set Operation Type to Translate S-VLAN.
l Set Source Port to VCTRUNK2.


Step 9 Configure the QinQ service to which the traffic stream of customer b at NE3 corresponds. For
l Set Operation Type to Translate S-VLAN.
l Set Source Port to VCTRUNK2.
Step 10 Create the cross-connection from the paths that are bound to the VCTRUNK to the corresponding
timeslots on the line.
----End
14.1.12 Configuration Example (EVPLAN Services Based on the

IEEE 802.1ad Bridge)
This topic considers an example to describe how to configure the EVPLAN services that are
based on the IEEE 802.1ad bridge.
Precautions
NOTE
For details on the services configured in this example, refer to the example described in 14.2.6.2 EVPLAN
Services Based on the IEEE 802.1ad Bridge.
The following configuration flow is based on the configuration of services on convergence node NE3.
Procedure
Step 1 Set Network Attributes of PORT1 and PORT2 of the Ethernet switching board of NE3 to C-
Aware. For details, see 14.3.7.1 Configuring External Ethernet Ports.
Step 2 Set Network Attributes of VCTRUNNK1 and VCTRUNK2 of the Ethernet switching board
of NE3 to C-Aware. For details, see 14.4.7.1 Configuring the Internal Port of the Ethernet
Board.
Step 3 Configure the EVPLAN services that are based on the IEEE 802.1ad bridge for NE3. For details,
see 14.1.4.4 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad
Bridge.
Set the parameters for the IEEE 802.1ad bridge as follows:
l Set VB Name to VB1.
l Set VB Type to 802.1ad.
l Set Bridge Switch Mode to IVL\Ingress Filter Enable.
l Bridge Learning Mode is set to IVL automatically.
l Ingress Filter is set to Enabled automatically.

Set the parameters for service mounting as follows:
Parameter Parameter Value
Operation Add S-VLAN Base for Port Add S-VLAN Base for Port and C-
Type VLAN
VB Port 1 2 3 4
Mount Port PORT1 PORT2 VCTRUNK1 VCTRUNK2
C-VLAN - - 10 20 30 40
S-VLAN 100 200 100 200 100 200
Step 4 Create the VLAN filtering table. For details, see 14.1.4.5 Creating the VLAN Filter Table.
Set the parameters for the VLAN filtering table of the VoIP services as follows:
l Set VLAN ID to 100.

l Select the corresponding forwarding ports, including PORT1, VCTRUNK1, and
VCTRUNK2.
Set the parameters for the VLAN filtering table of the HSI services as follows:
l Set VLAN ID to 200.

l Select the corresponding forwarding ports, including PORT2, VCTRUNK1, and
VCTRUNK2.
----End
14.1.13 Configuring Services Based on the Hybrid Microwave

The Hybrid microwave that the OptiX RTN 600 supports can transmit E1 services and Ethernet
services at the same time. When E1 services are transmitted over the Hybrid microwave, you
need to create the cross-connections. When Ethernet services are transmitted over the Hybrid
microwave, you need not configure the encapsulation and mapping in the VCTRUNKs or the
cross-connections between the VCTRUNKs and line timeslots.

14.1.13.2 Service Planning (Microwave Services)
14.1.13.3 Service Planning (Ethernet Services Accessed Through the EMS6 Board)

14.1.13.4 Service Planning (Ethernet Services Accessed Through the IFH2 Board)
14.1.13.5 Configuring NE1 (Microwave Services)
You can configure the microwave service data of NE1 based on the parameters of the service
14.1.13.6 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board)
You can configure the Ethernet services that are accessed through the EMS6 board of NE1 based
on the parameters of the service planning, by using the NMS.
14.1.13.9 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board)
You can configure the attributes and CoS of the Ethernet ports of the IFH2 board based on the
parameters of the engineering plan so that Ethernet services can be accessed to the IFH2 board
normally, thus meeting the requirement for CoS scheduling.
14.1.13.10 Configuring NE3 (Ethernet Services)
You can configure the Ethernet service data of NE3 based on the parameters of the service

In the network shown in Figure 14-41, NE1 and NE2 use the IDU 620 and NE3 uses the IDU
605. The service requirements are as follows:
l The Ethernet equipment of user A, user B, and user C provides 100 Mbit/s auto-negotiative
Ethernet electrical interfaces. The Ethernet equipment of user A does not support VLAN
tags. The services of user A are frames that do not carry VLAN tags, namely, untagged
framed. The Ethernet equipment of user B and user C supports VLAN tags. Hence, the
services of user B and user C are frames that carry VLAN tags, namely, tagged frames.
l User A has two branches (user A1 and user A2), which are located at NE1 and NE2. There
are 4xE1 services and Ethernet services between the two branches. The Ethernet services
are Internet services, whose maximum bandwidth is 10 Mbit/s. The bandwidth of the
Internet services can be allocated flexibly. After the user services are accessed, the default
VLAN ID of 300 is added to the services.
l User B has two branches (user B1 and B2), which are located at NE1 and NE2. There are
2xE1 services and Ethernet services between the two branches. One part of the Ethernet
services are voice over IP (VoIP) services, whose maximum bandwidth is 4 Mbit/s. The
transmission of the VoIP services must be stable. The VLAN ID is 100. The other part of

the Ethernet services are Internet services, whose maximum bandwidth is 20 Mbit/s. The
bandwidth of the Internet services can be allocated flexibly. The VLAN ID is 200.
l The radio link between NE1 and NE2 uses the 1+1 HSB configuration.
l User C has two branches, which are located at NE2 and NE3. There are 4xE1 services and
Ethernet services between the two branches. One part of the Ethernet services are VoIP
services, whose maximum bandwidth is 4 Mbit/s. The transmission of the VoIP services
must be stable and the VLAN priority level is 7. The other part of the Ethernet services are
Internet services, whose maximum bandwidth is 20 Mbit/s. The bandwidth of the Internet
services can be allocated flexibly and the VLAN priority level is 1.

User A2
User A1
User C2
NE2
(IDU 620)
NE1
(IDU 620)
User B1
User B2
User C1
NE3
(IDU 605 1F)
14.1.13.2 Service Planning (Microwave Services)

The engineering planning information includes all the information that is required for
configuring the microwave services on NE1, NE2, and NE3.
NE Attributes
Equipment Type IDU 620 IDU 620 IDU 605 1F
NE ID 101 102 103
Extended ID 9 (default value) 9 (default value) 9 (default value)

NE IP 129.9.0.101 129.9.0.102 129.9.0.103
Planning a Radio Link

As described in the engineering requirements, there are two Hybrid radio links, which are the
radio link between NE1 and NE2 and the radio link between NE2 and NE3. Figure 14-42 shows
the link planning information.
Figure 14-42 Link planning diagram
NE1 H-polarization
NE2
(IDU 620) (IDU 620)
Tx Hi 14930 MHz
14510 MHz
Tx Low Tx Low
14532 MHz
NE3
14952 MHz (IDU 605 1F)
V-polarization
Tx Hi
NOTE
NE1, NE2, and NE3 use the ODUs that operate on sub-band A of the 15 GHz frequency band with a T/R
spacing of 420 MHz. Hence, fewer types of spare parts are required.
In addition, the networking diagram shows the capacity information of the two Hybrid radio
links, as listed in Table 14-19.
Table 14-19 Link capacity
Radio Link Number of Capacity of Assured Maximum

E1 Services E1 Services Ethernet Service Ethernet Service
(Mbit/s) Capacity (Mbit/ Capacity (Mbit/s)
s)
Link between 6 12 4 34
NE1 and NE2
Link between 4 8 4 24
NE2 and NE3

The Hybrid radio link can be planned properly according to the previous information and the
actual engineering requirements. Table 14-20 provides the planning information of the Hybrid
radio link in this example.
Table 14-20 Information for planning a radio link

Parameter Link 1 Link 2
TX High Station NE1 NE3
TX Low Station NE2 NE2
TX Frequency at the TX High 14930 14952

Station (MHz)
TX Frequency at the TX Low 14510 14532

Station (MHz)
T/R Spacing(MHz) 420 420
TX Power(dBm) 10 (The TX power must be the same 10 (The TX power must be the same
at both ends.) at both ends.)
Channel Spacing(MHz) 14 14
E1 Capacity of the Hybrid Network 6 4
AM Enable Status Enable Enable
AM Mode Asymmetric Asymmetric
Modulation Mode of the Assured QPSK QPSK

AM Capacity
Modulation Mode of the Full AM 32QAM 32QAM

Capacity
Radio Link ID 101 102
ATPC Enable Status Disabled Disabled
Link Protection Mode 1+1 HSB 1+0
Polarization Directiona H (horizontal polarization) V (vertical polarization)
NOTE
a: The planning information that is not related to the configuration of the IDU (except for the polarization direction) is not provided
in this example.

Board Layout
Figure 14-43 Board layout of the IDU (NE1)
EXT
IFH2 Slot7 EXT Slot8
EXT
IFH2 Slot5 EXT
EMS6 Slot6
FAN
FAN
PXC
PXC Slot3 EXT
PH1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
EXT
IFH2 Slot7 IFH2
EXT Slot8
EXT
IFH2 Slot5 EXT
EMS6 Slot6
FAN
FAN
PXC
PXC Slot3 EXT
PH1 Slot4
Slot 20
PXC
PXC Slot1 SCC
SCC Slot2
PW48B SCC EOW PH1 EMS4 IFH1

Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 8
NOTE
not shown in the board layout diagram. In the case of the IDU 620, "n" ranges from five to eight whereas in the
case of the IDU 605, "n" is 7 or 8.

Parameter NE1 NE2
Protection Group ID 1 1
Working Slot Slot 5 Slot 5
Protection Slot Slot 7 Slot 7

Parameter NE1 NE2
WTR Time(s) 600 (default value) 600 (default value)
Timeslot Allocation
NE1 NE2 NE3

Station
5-IFH2 5-IFH2 8-IFH2 8-IFH1
E1: 1-4
4-PH1:7-10 4-PH1:1-4
Timeslot E1: 1-6
4-PH1:1-6 4-PH1:1-6
Add/Drop
As shown in Figure 14-46, the timeslots are allocated for the services between the NEs as
follows.
l The timeslot allocation for the E1 services of NE1 is as follows:
The services that are added or dropped over ports 1-6 of the PH1 board in slot 4 of NE1
occupy the 1-6 E1 timeslots on the radio link between the IFH2 board in slot 5 of NE1 and
the IFH2 board in slot 5 of NE2.
The services are that added or dropped over ports 1-6 of the PH1 board in slot 4 of NE2
occupy the 1-6 E1 timeslots on the radio link between the IFH2 board in slot 5 of NE1
and the IFH2 board in slot 5 of NE2.
The services are that added or dropped over ports 7-10 of the PH1 board in slot 4 of
NE2 occupy the 1-4 E1 timeslots on the radio link between the IFH2 board in slot 8 of
NE2 and the IFH1 board in slot 8 of NE3.
The services are that added or dropped over ports 1-4 of the PH1 board in slot 4 of NE3
occupy the 1-4 E1 timeslots on the radio link between the IFH2 board in slot 8 of NE2 and
the IFH1 board in slot 8 of NE3.

Clock Information
Figure 14-47 Clock synchronization scheme

NE2 NE1
BITS
External clock 5-IFH2(SDH-1)/
source 1/Internal 7-IFH2(SDH-1)/
clock source Internal clock source
Direction of the main clock
Table 14-22 Clock information

Parameter NE1 NE2
Clock First Clock 5-IFH2(SDH-1) External clock source 1

Source Source
Second 7-IFH2(SDH-1) Internal clock source

Clock
Source
Third Clock Internal clock source -

Source

Telephone No. 101 102 103
Call Waiting Time(s) 5 5 -
Selected Orderwire 5-IFH2-1 5-IFH2-1 -

Port
Orderwire Occupied E1 E1 -
Bytes
14.1.13.3 Service Planning (Ethernet Services Accessed Through the EMS6 Board)

Configuration Information of Ethernet Parameters
Figure 14-48 Configuration information of Ethernet parameters

NE1: 5-IFH2 NE2: 5-IFH2
(main) NE1: NE2: (main)
15-ODU 15-ODU
(main) (main)
NE1: NE2:
PORT1 PORT1
6-EMS6 6-EMS6
PORT3 PORT3
(main) (main)
PORT1 PORT1
User User
A1 A2
User LAG LAG User
B1 B2
PORT2 PORT2
NE1: NE2:
PORT4 PORT4
17-ODU 17-ODU (slave)
(slave) (standby) (standby)
PORT1
PORT1
NE1: 7-IFH2 NE2: 7-IFH2

(standby) (standby)
Network cable
IF cable
Table 14-24 Parameters of external ports of the EMS6 board

Parameter NE1 NE2
Board 6-EMS6 6-EMS6
Port PORT1-PORT4 PORT1-PORT4
Enabled/Disabled Enabled Enabled
Working Mode Auto-Negotiation Auto-Negotiation
Maximum Frame Length 1522 1522
Flow Control Disabled Disabled
TAG PORT1: Access (default PORT1: Access (default

VLAN ID: 300) VLAN ID: 300)
PORT2-PORT4: Tag Aware PORT2-PORT4: Tag Aware
Entry Detection Enabled Enabled

Table 14-25 Parameters of external ports of the IFH2 board

Parameter NE1 NE2
Board 5-IFH2 7-IFH2 5-IFH2 7-IFH2

Disabled

Table 14-26 Parameters of Ethernet private line services (NE1)

Parameter NE1
Private Line Private Line Private Line

Service 1 (User A1) Service 2 (User B1, Service 3 (User B1,
VoIP Service) Internet Service)
Board 6-EMS
Service Type EPL EPL EPL
Service Direction Bidirectional Bidirectional Bidirectional
Source Port PORT1 PORT2 PORT2
Source C-VLAN 300 100 200

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

1,3-6)
Table 14-27 Parameters of Ethernet private line services (NE2)

Parameter NE2

Board 6-EMS
Service Type EPL EPL EPL
Service Direction Bidirectional Bidirectional Bidirectional
Source Port PORT1 PORT2 PORT2

Parameter NE2

Source C-VLAN 300 100 200

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

1,3-6)
Configuration Information of the QoS
Table 14-28 Flow configuration

Paramet NE1 NE2
er
User A1 User B1, User B1, User A2 User B2, User B2,
VoIP Internet VoIP Internet
Service Service Service Service
Board 6-EMS 6-EMS
Flow PORT PORT PORT PORT PORT PORT

Type +VLAN +VLAN +VLAN +VLAN +VLAN +VLAN
Flow Flow Flow Flow Flow Flow
Port PORT1 PORT2 PORT2 PORT1 PORT2 PORT2
VLAN 300 100 200 300 100 200

ID
Bound 1 - 2 1 - 2
CAR
Bound 3 1 2 3 1 2
CoS
Table 14-29 Parameters of the CARa

Parameter NE1 NE2
Board 6-EMS 6-EMS
CAR ID 1 2 1 2
Enabled/Disabled Enabled Enabled Enabled Enabled

Parameter NE1 NE2
Committed Information Rate (kbit/ 10240 20480 10240 20480

s)
Committed Burst Size (kbyte) 0 0 0 0
Peak Information Rate (kbit/s) 20480 40960 20480 40960
Maximum Burst Size (kbyte) 0 0 0 0
NOTE
a: You can limit the Ethernet service rate on a port of the EMS6 board, by performing the corresponding
configuration of the CAR that is bound with the port.
Table 14-30 Parameters of the CoS

Parameter NE1 NE2
Board 6-EMS 6-EMS
CoS ID 1 2 3 1 2 3
CoS Type simple simple simple simple simple simple
CoS Priority 7 3 2 7 3 2
Configuration Information of the Link Aggregation Group
Table 14-31 Parameters of the link aggregation group

Parameter NE1 NE2
Board 6-EMS 6-EMS
LAG No. 1 1
LAG Name LAG_1 LAG_1
LAG Type Manual Manual
Load Sharing Non-Sharing Non-Sharing
Main Port PORT3 PORT3
Selected Slave Ports PORT4 PORT4
14.1.13.4 Service Planning (Ethernet Services Accessed Through the IFH2 Board)

Figure 14-49 Configuration diagram of the Ethernet services between NE2 and NE3
NE2: NE3: NE3:
8-IFH2 8-IFH1 5-EMS4
NE2: NE3:
18-ODU 18-ODU
PORT1 PORT1
User User
C2 C1
Network cable
IF cable
Parameter NE2 NE3
Board 8-IFH2 5-EMS4
Port PORT1 PORT1
Enabled/Disabled Enabled Enabled
Working Mode Auto-Negotiation Auto-Negotiation
Autonegotiation Flow Enable Symmetric Flow Control Disabled

Control Mode
Table 14-33 Parameters of the CoS of the IFH2 board (NE2)
CoS Parameter CoS Priority
User Priority 7 in the VLAN Tag 3
User Priority 1 in the VLAN Tag 1
Table 14-34 Parameters of Ethernet services (NE3)
Parameter Ethernet LAN Service
Board 5-EMS4
VB Name VB1
VB Type 802.1d

Parameter Ethernet LAN Service
Bridge Switch Mode SVL/Ingress Filter Disable
Mount Port PORT1, IFUP1

Prerequisite
Procedure
l New ID: 101

l IP: 129.9.0.101

1. In the NE Explorer, select NE1 and then choose Configuration > IF 1+1 Protection from
the Function Tree.
2. Click Create.



value.
restoration occurs.
value.
source end.
value.
Working Board 5-IFH2-1 In the 1+1 HSB mode, the IF boards can be installed
Protection Board 7-IFH2-1 IF boards in a pair in slots 5 and 7 (the IF board in
Step 4 Configure the Hybrid/AM attribute.

1. In the NE Explorer, select the 5-IFH2 board and then choose Configuration > Hybrid/
AM Configuration from the Function Tree.
2. Click the Hybrid/AM Configuration tab. After setting the parameters, click Apply.
IF Channel 14M l In this example, the spacing between radio links

Bandwidth is 14 MHz.
values listed in service planning (microwave
services).
E1 Capacity 6 A maximum of 6xE1 services can be transmitted in

Hybrid work mode. The value of this parameter
cannot exceed the maximum number of E1 services
permitted in Modulation Mode of the Assured AM
Capacity.
AM Mode Asymmetric An AM switching in one direction of the radio link

does not cause an AM switching in the other
direction of the radio link.

AM Enable Enable The radio link uses the corresponding modulation

Status mode according to the channel conditions.
Modulation QPSK l In this example, the lowest modulation mode that

Mode of the the AM function supports is QPSK.
Assured AM l The value of this parameter is determined by the
Capacity link capacity and must ensure the reliable
transmission of E1 services.
Modulation 32QAM l In this example, the highest modulation mode

Mode of the Full that the AM function supports is set to 32QAM.
AM Capacity l The value of this parameter is determined by the
link capacity and must ensure that the maximum
capacity of Hybrid microwave services can be
transmitted when the radio link is in good
conditions.
NOTE
The 5-IFH2 and 7-IFH2 boards are configured as a 1+1 HSB protection group. The 5-IFH2 functions as
the main IF board and the 7-IFH2 functions as the standby IF board. The system automatically sets the
relevant parameters of the standby board (7-IFH2). Hence, you need not set the parameters manually.

3. Set the information about the 5-IFH2. Then, click Apply. Set the information about the 15-
ODU on the radio link. Then, click Apply.

ATPC Enable Disabled -

Status

420 MHz.



normally.
default value.
Step 6 Create the cross-connections of services.

2. Click Create. Then, the Create SDH Service dialog box is displayed. Configure the cross-
connections of the service. Click OK.

bound.
l This parameter indicates the level of the cross-
connections.
Direction Bidirectional l When this parameter is set to Bidirectional,

create the cross-connections from the service
source to the service sink and from the service
sink to the service source.
default value.
Source 4-PH1 In this example, the 4-PH1 is the service source.
Source 1-6 In this example, the timeslots to which the service

Timeslot Range source corresponds are timeslots 1-6.
(e.g.1,3-6)
Sink 5-IFH2 In this example, the 5-IFH2 is the service sink.
Sink Port 1 In this example, port 1 is the service sink port.

VC4-1.
Range(e.g. sink corresponds are timeslots 1-6.
1,3-6)
l Phone 1: 101
l Orderwire Port: 5-IFH2-1


2. Click Create. The Add Clock Source dialog box is displayed. After setting the parameters,
click OK.
Clock Source 5-IFH2-1(SDH) In this example, the 5-IFH2-1(SDH) is the clock

source.
7-IFH2-1(SDH) In this example, the 7-IFH2-1(SDH) is the clock

source.
Then, click Apply.
er
Clock 5-IFH2-1 7-IFH2-1 Internal In this example, the 5-IFH2-1

Source (SDH) (SDH) Clock (SDH), 7-IFH2-1(SDH), and
Source internal clock source are set as the
clock sources.
Clock 1 2 3 l This parameter specifies the

Source priority level of a clock
Priority source.
Sequence l The priority level of the 5-
(1 is the IFH2-1(SDH) clock source is
highest) 1. The priority level of the 7-
IFH2-1(SDH) clock source is
2. The priority level of the
internal clock source is 3.
----End
Prerequisite
The IFH2 board must be added.

Procedure
Step 1 Configure Ethernet external ports of the IFH2 board.
1. In the NE Explorer, select the IFH2 board and then choose Configuration > Ethernet
Port.
2. Click the Basic Attributes tab. After setting the basic attributes of the port, click Apply.

l The user services use PORT1.
Working Mode Auto- In this example, the port works in auto-

Negotiation negotiation mode.
3. Click the Flow Control tab. After setting the flow control mode of the port, click Apply.
Port PORT1 l The flow control mode of PORT1 need to be

set.
Non- Disabled l In this example, the non-auto-negotiation flow

Autonegotiatio control is disabled.
n Flow Control l In this example, this parameter adopts the
Mode default value.
Autonegotiatio Disabled l In this example, the auto-negotiation flow

n Flow Control control is disabled.
Mode l In this example, this parameter adopts the
default value.
Step 2 Configure Ethernet external ports of the EMS6 board.

Port.
2. Click the Basic Attributes tab. After setting the basic attributes of the ports, click
Apply.

Port PORT1-PORT4 l The basic attributes of PORT1, PORT2,

PORT3, and PORT4 need to be set.
l The services of user A1 use PORT1 and the
services of user B1 use PORT2.
l PORT3 and PORT4 form an LAG. PORT3 is
the main port and PORT4 is the slave port.

3. Click the Flow Control tab. After setting the flow control mode of the ports, click
Apply.
Port PORT1-PORT4 l The flow control mode of PORT1, PORT2,


Mode default value.

default value.
Port PORT1-PORT4 l The tag attributes of PORT1, PORT2,


TAG l In this If TAG is set to Access:

example, l The packets that carry VLAN tags are
TAG is set to discarded.
Access for
PORT1. l The packets that do not carry VLAN tags are
tagged with Default VLAN ID and are then
l In this received.
example,
TAG is set to If TAG is set to Tag Aware:
Tag Aware l The packets that carry VLAN tags are
for PORT2- received.
discarded.
Default VLAN 300 In this example, Default VLAN ID is set to 300

ID for PORT1.
Entry Detection Enabled l In this example, the incoming packets from the
attributes.
default value.
Step 3 Create Ethernet private line services of the EMS6 board.

2. Click New. Then, the Create Ethernet Line Service dialog box is displayed.
3. Set the attributes of the three Ethernet private line services. Then, click OK.
l Set the parameters of Ethernet private line service 1 as follows.
Service Type EPL When creating the non-QinQ private line

Service Bidirectional l If Direction is set to Bidirectional, the

Direction services from the service source to the
service sink and from the service sink to the
default value.

port.
Source VLAN 300 The service that has the VLAN ID of 300 is the
(e.g.1, 3-6) source service.
Sink Port PORT3 In this example, PORT3 is the service sink port.

Sink VLAN 300 The service that has the VLAN ID of 300 is the
(e.g.1, 3-6) sink service.

Service Bidirectional l If Direction is set to Bidirectional, the

Direction services from the service source to the
default value.

port.


default value.

port.

Step 4 Configure the QoS of the EMS6 board.

1. Create the flow.
a. In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b. Click the Flow Configuration tab.
c. Click New. The New Flow dialog box is displayed. Set the parameters of the three
flows. Then, click OK.
l Set the parameters of the Internet service of user A1 as follows:
Flow Type PORT+VLAN When Flow Type is set to PORT+VLAN

Flow Flow, the packets that are from the same port
and have the same VLAN ID are classified as a
type of flow.
Port PORT1 In this example, PORT1 is the source port of the

Ethernet service associated with the flow.
VLAN ID 300 In this example, the source VLAN ID is 300.
l Set the parameters of the VoIP service of user B1 as follows.

type of flow.

l Set the parameters of the Internet service of user B1 as follows.

type of flow.

2. Create the CAR.

b. Click the CAR Configuration tab.
c. Click New. The New CAR dialog box is displayed. Select the parameters of the two
CARs. Then, click OK.
l Set the parameters of user A1 as follows.
CAR ID 1 In this example, CAR 1 is used to bind the flow

to an associated CAR operation.
Enabled/ Enabled In this example, CAR1 is enabled.

Disabled
Committed 10240 l In this example, the CIR is 10240 kbit/s.

Information l When the rate of the packets is not more than
Rate(kbit/s) the CIR, these packets pass the restriction of
the CAR and are forwarded first even in the
case of network congestion.
Committed 0 In this example, the CBS is 0.

Burst Size
(kbyte)
Peak 20480 l In this example, the PIR is 20480 kbit/s.

Information l When the rate of the packets is more than the
Rate(kbit/s) PIR, these packets that exceed the rate
restriction are directly discarded. When the
rate of the packets is more than the CIR but
is not more than the PIR, the packets whose
rate is more than the CIR can pass the
restriction of the CAR and are marked
yellow, which enables these packets to be
discarded first in the case of network
congestion.
Maximum 0 In this example, the MBS is 0.

Burst Size
(kbyte)


Enabled/ Enabled In this example, CAR 2 is enabled.

Disabled



Burst Size
(kbyte)

congestion.

Burst Size
(kbyte)
3. Create the CoS.

b. Click the CoS Configuration tab.
c. Click New. The New CoS dialog box is displayed. Set the parameters of the three
CoSs. Then, click OK..
CoS ID 1 In this example, CoS 1 is used to bind the flow

to an associated CoS operation.
CoS Type simple If the CoS Type of a flow is set to simple, all
the packets in this flow are directly scheduled
to a specified egress queue.
CoS Priority 7 The queue whose CoS priority is 7 is an SP

queue.
l Set the parameters of the Ethernet service of user B1 as follows.


CoS Priority 3 The queues whose priorities are from 0 to 6 are

WRR queues. The weighted proportion of these
WRR queues are 1:2:4:8:16:32:64 (from
priority 0 to priority 6).
l Set the parameters of the Ethernet service of user A1 as follows.



4. Bind the CAR/CoS.

b. Click the Flow Configuration tab. After setting the parameters, click OK.

er
Port PORT1 PORT2 PORT2 In this example, PORT1 and

PORT2 are the source ports of the
Ethernet services associated with
the flows.
Flow PORT PORT PORT When Flow Type is set to PORT

Type +VLAN +VLAN +VLAN +VLAN Flow, the packets that
Flow Flow Flow are from the same port and have
the same VLAN ID are classified
as a type of flow.
VLAN ID 300 100 200 The source VLAN IDs of the

ports are 300, 100, and 200.


er
Bound 1 - 2 The flow is bound with the

CAR corresponding CAR, according to
the service plan.
Bound 3 1 2 The flow is bound with the

CoS corresponding CoS, according to
the service plan.
Step 5 Create an LAG of the EMS6 board.

Tree.
3. Click New. The Create Link Aggregation Group dialog box is displayed. After setting
the parameters, click OK. Then, click OK in the dialog box that is displayed.
LAG No. 1 In this example, LAG No. is set to 1.
LAG Name LAG_1 In this example, LAG Name is set to LAG_1.
LAG Type Manual The user creates the LAG manually. The LACP is
not enabled to add or delete a member port. The
member ports may be in the UP or DOWN state. The
equipment determines whether to perform the
aggregation according to the status of the specific
port.
Load Sharing Non-Sharing Only one member link of a link aggregation group
carries traffic and the other member links are in the
Standby state. In this case, a hot backup scheme is
provided.
Main Port PORT3 In this example, PORT3 is the main port.
Selected Slave PORT4 In this example, PORT4 is the slave port.

Ports
----End

Prerequisite


Procedure
l New ID: 102
l IP: 129.9.0.102
1. In the NE Explorer, select NE1 and then choose Configuration > IF 1+1 Protection from
the Function Tree.
2. Click Create.


value.
restoration occurs.
value.
source end.
value.

Working Board 5-IFH2-1 In the 1+1 HSB mode, the IF boards can be installed
Protection Board 7-IFH2-1 IF boards in a pair in slots 5 and 7 (the IF board in
Step 4 Configure the Hybrid/AM attribute.

1. In the NE Explorer, select the 5-IFH2 and then choose Configuration > Hybrid/AM
IF Channel 14M l In this example, the spacing between radio

Bandwidth links is 14 MHz.
services).
E1 Capacity 6 A maximum of 6xE1 services can be transmitted

in Hybrid work mode. The value of this parameter
cannot exceed the maximum number of E1
services permitted in Modulation Mode of the
Assured AM Capacity.
AM Mode Asymmetric When this parameter is set to Asymmetric, an

AM switching in one direction of the radio link
AM Enable Enable The radio link uses the corresponding modulation

Status mode according to the channel conditions.
Modulation QPSK l In this example, the lowest modulation mode

Mode of the that the AM function supports is QPSK.
Assured AM l The value of this parameter is determined by
Capacity the link capacity and must ensure the reliable
Modulation 32QAM l In this example, the highest modulation mode

Mode of the that the AM function supports is set to
Full AM 32QAM.
Capacity l The value of this parameter is determined by
the link capacity and must ensure that the
maximum capacity of Hybrid microwave
services can be transmitted when the radio
links are in good conditions.

NOTE
The 5-IFH2 and 7-IFH2 boards are configured as a 1+1 HSB protection group. The 5-IFH2 functions
as the main IF board and the 7-IFH2 functions as the standby IF board. The system automatically
sets the relevant parameters of the standby board (7-IFH2). Hence, you need not set the parameters
manually.
3. In the NE Explorer, select the 8-IFH2 and then choose Configuration > Hybrid/AM
IF Channel 14M l In this example, the spacing between radio

Bandwidth links is 14 MHz.
services).
E1 Capacity 4 A maximum of 4xE1 services can be transmitted

in Hybrid work mode. The value of this parameter
cannot exceed the maximum number of E1
services permitted in Modulation Mode of the
Assured AM Capacity.
AM Mode Asymmetric When this parameter is set to Asymmetric, an

AM switching in one direction of the radio link
AM Enable Enable l When this parameter is set to Enable, the radio

Status link uses the corresponding modulation mode
according to the channel conditions.
default value.
Modulation QPSK l In this example, the lowest modulation mode

Mode of the that the AM function supports is QPSK.
Assured AM l The value of this parameter is determined by
Capacity the link capacity and must ensure the reliable
Modulation 32QAM In this example, the available highest modulation

Mode of the mode that the AM function supports is set to
Full AM 32QAM.
Capacity l In this example, the highest modulation mode
that the AM function supports is set to
32QAM.
l The value of this parameter is determined by
the link capacity and must ensure that the
maximum capacity of Hybrid microwave
services can be transmitted when the radio
links are in good conditions.


3. Set the information about the 5-IFH2 and 15-ODU on one radio link. Then, click Apply.
Set the information about the 8-IFH2 and 18-ODU on the other radio link. Then, click
Apply.
l Set the parameters of the 5-IFH2 and 15-ODU as follows.


Status


ODU is 420 MHz.


normally.
default value.
l Set the parameters of the 8-IFH2 and 18-ODU as follows:


Status


ODU is 420 MHz.



normally.
default value.
Step 6 Create the cross-connections of services.

l Configure the cross-connections of the E1 services of NE1 and NE2 as follows.

bound.
cross-connections.
Direction Bidirectional l When this parameter is set to

Bidirectional, create the cross-connections
from the service source to the service sink
and from the service sink to the service
source.
default value.

Range(e.g.
1,3-6)

VC4-1.

1,3-6)
l Configure the cross-connections of the E1 services of NE2 and NE3 as follows.


bound.
cross-connections.
Direction Bidirectional l When this parameter is set to

Bidirectional, create the cross-connections
from the service source to the service sink
and from the service sink to the service
source.
default value.

Range(e.g.
1,3-6)

VC4-1.

1,3-6)

l Phone 1: 102
l Orderwire Port: 5-IFH2-1
Then, click OK.
Clock Source External Clock In this example, external clock source 1 is

Source 1 selected as the clock source.

Then, click Apply.
Clock External Internal In this example, external clock source 1

Source Clock Source Clock Source and the internal clock source are
1 selected as the clock sources.

Priority l The priority level of external clock
Sequence(1 source 1 is 1. The priority level of the
is the internal clock source is 2.
highest)
----End
Prerequisite
Procedure
Step 1 Configure Ethernet external ports of the IFH2 board.
Port.
2. Click the Basic Attributes tab. After setting the basic attributes of the port, click Apply.



3. Click the Flow Control tab. After setting the flow control mode of the port, click Apply.
Port PORT1 l The flow control mode of PORT1 need to be

set.

Mode default value.

default value.
Step 2 Configure Ethernet external ports of the EMS6 board.

Port.
2. Click the Basic Attributes tab. After setting the basic attributes of the ports, click
Apply.
Port PORT1-PORT4 l The basic attributes of PORT1, PORT2,


3. Click the Flow Control tab. After setting the flow control mode of the ports, click
Apply.

Port PORT1-PORT4 l The flow control mode of PORT1, PORT2,


Mode default value.

default value.
Port PORT1-PORT4 l The tag attributes of PORT1, PORT2,

TAG l In this If TAG is set to Access:

example, l The packets that carry VLAN tags are
TAG is set to discarded.
Access for
tagged with Default VLAN ID and are then
l In this received.
example,
TAG is set to If TAG is set to Tag Aware:
Tag Aware l The packets that carry VLAN tags are
for PORT2- received.
discarded.
Default VLAN 300 In this example, Default VLAN ID is set to 300

ID for PORT1.
Entry Detection Enabled l In this example, the incoming packets from the
attributes.
default value.

Step 3 Create Ethernet private line services of the EMS6 board.

2. Click New. Then, the Create Ethernet Line Service dialog box is displayed.
3. Set the attributes of the three Ethernet private line services. Then, click OK.


default value.

port.


default value.

port.

l Set the parameters of Ethernet private line service 3 as follows:


default value.

port.
Step 4 Configure the QoS of the EMS6 board.

1. Create the flow.
c. Click New. The New Flow dialog box is displayed. Select the parameters of the eight
flows. Then, click OK.
l Set the parameters of the Internet service of user A2 as follows:

type of flow.



type of flow.


Flow Flow, the packets that are from the same port and
have the same VLAN ID are classified as a type
of flow.

2. Create the CAR.

b. Click the CAR Configuration tab.
c. Click New. The New CAR dialog box is displayed. Set the parameters of the two
CARs. Then, click OK.
l Set the parameters of user A1 as follows.


Disabled


Burst Size
(kbyte)


congestion.

Burst Size
(kbyte)


Disabled


Burst Size
(kbyte)

congestion.

Burst Size
(kbyte)

3. Create the CoS.

c. Click New. The New CoS dialog box is displayed. Set the parameters of the three
CoSs. Then, click OK.

CoS Priority 7 The queue whose CoS priority is 7 is an SP

queue.
l Set the parameters of the Ethernet service of user B2 as follows.


l Set the parameters of the Ethernet service of user A2 as follows.




b. Click the Flow Configuration tab. After setting the parameters, click OK.

er
Port PORT1 PORT2 PORT2 In this example, PORT1 and

PORT2 are the source ports of the
Ethernet services associated with
the flows.
Flow PORT PORT PORT When Flow Type is set to PORT

Type +VLAN +VLAN +VLAN +VLAN Flow, the packets that
Flow Flow Flow are from the same port and have
the same VLAN ID are classified
as a type of flow.
VLAN ID 300 100 200 The source VLAN IDs of the

ports are 300, 100, and 200.
Bound 1 - 2 The flow is bound with the

CAR corresponding CAR, according to
the service plan.
Bound 3 1 2 The flow is bound with the

CoS corresponding CoS, according to
the service plan.
Step 5 Create an LAG of the EMS6 board.

Tree.
3. Click New. The Create Link Aggregation Group dialog box is displayed. After setting
the parameters, click OK. Then, click OK in the dialog box that is displayed.
LAG No. 1 In this example, LAG No. is set to 1.
LAG Name LAG_1 In this example, LAG Name is set to LAG_1.
LAG Type Manual The user creates the LAG manually. The LACP is
not enabled to add or delete a member port. The
member ports may be in the UP or DOWN state. The
equipment determines whether to perform the
aggregation according to the status of the specific
port.

Load Sharing Non-Sharing Only one member link of a link aggregation group
carries traffic and the other member links are in the
Standby state. In this case, a hot backup scheme is
provided.
Main Port PORT3 In this example, PORT3 is the main port.
Selected Slave PORT4 In this example, PORT4 is the slave port.

Ports
----End
14.1.13.9 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board)
You can configure the attributes and CoS of the Ethernet ports of the IFH2 board based on the
parameters of the engineering plan so that Ethernet services can be accessed to the IFH2 board
normally, thus meeting the requirement for CoS scheduling.
Prerequisite
Procedure
Step 1 Configure the Ethernet ports of the IFH2 board.
Port.
2. Set the basic attributes of the ports. Click the Basic Attributes tab. After setting the
parameters, click Apply.

Enabled/ Enabled In the case of the port that accesses services, set this
Disabled parameter to Enabled.
Working Mode Auto-Negotiation In this example, the port works in auto-negotiation

mode.

Autonegotiation control is disabled.
Flow Control l In this example, this parameter adopts the default
Mode value.

Autonegotiation Enable When this parameter is set to Enable Symmetric

Flow Control Symmetric Flow Flow Control, PORT1 transmits and processes
Mode Control PAUSE frames.
Step 2 Configure the CoS of the IFH2 board.

1. In the NE Explorer, select the IFH2 board and then choose Configuration > QoS
2. Click the Flow Configuration tab.
3. Set CoS Parameter and CoS Priority. After setting the parameters, click Apply.
CoS Priority 7 in Priority 1 in The data flows correspond to Priority 7

Parameter the VLAN the VLAN in the VLAN Tag and Priority 7 in the
Tag Tag VLAN Tag, respectively.
CoS Priority 3 1 l The data flow of Priority 7 in the

VLAN Tag has the CoS priority of
3. The data flow of Priority 1 in the
VLAN Tag has the CoS priority of
1.
l This parameter specifies the queue to
which a packet should be scheduled.
----End
14.1.13.10 Configuring NE3 (Ethernet Services)

You can configure the Ethernet service data of NE3 based on the parameters of the service
Prerequisite
Procedure
1. In the NE Explorer, select the 5-EMS4 board and then choose Configuration > Ethernet
Port.


l The services of user C use PORT1.

Negotiation.
Maximum 1522 -
Frame Length
PHY Loopback Non-Loopback l In this example, PHY Loopback is set to

Non-Loopback.
default value.
3. Click the Flow Control tab. After setting the parameters, click Apply.
Port PORT1 l The flow control of PORT1 needs to be set.


Mode default value.

default value.

TAG Tag Aware l The packets that carry VLAN tags are
received.

1. In the NE Explorer, select the 5-EMS4 board and then choose Configuration > Ethernet
as follows:
VB Type 802.1d In this example, an IEEE 802.1d bridge is created.
Bridge Switch SVL/Ingress In this example, a transparent bridge is created,

Mode Filter Disable and the VLAN IDs of the packets over each port
(802.1d) need not be checked.
selected PORT1, IFUP1 PORT1 and IFUP1 are connected to the bridge.
forwarding
ports
4. Click OK.
Step 3 Configure the QoS.

1. Configure the flow.
a. In the NE Explorer, select the 5-EMS4 and then choose Configuration > QoS
Management > Flow Configuration from the Function Tree.
c. Click New. The Create SDH Service dialog box is displayed. After setting the
Flow Type Port Flow The packets from the same port are classified as a
type of flow.
Port PORT1 The packets from the PORT1 are classified as a

type of flow.
2. Configure the CoS.

a. In the NE Explorer, select the 5-EMS4 and then choose Configuration > QoS
c. Click New. The New CoS dialog box is displayed. After setting the parameters. Then,
click OK.

CoS ID 1 In this example, CoS 1 is used to

bind the flow to an associated CoS
operation.
CoS Type VLAN Priority This parameter determines the

queues to which the packets are
scheduled according to the user
priority level in the VLAN tag.
CoS Priority 7 in the Priority 1 in In this example, the queue

Parameter VLAN Tag the VLAN scheduling mode is set SP. Hence,
Tag the packets in the queue with priority
level 1 in the VLAN tag are
CoS Priority 3 1 transmitted first.

a. In the NE Explorer, select the 5-EMS4 board and then choose Configuration > QoS
b. Click the Flow Configuration tab. After setting the parameters, click Apply.
Flow Type Port Flow The packets from the same port are classified as
a type of flow.
Port PORT1 -
Bound CAR - -
Bound CoS 1 The flow is bound with CoS 1.
----End
14.2 Configuring QinQ

The Ethernet switching processing board supports the line services that are based on QinQ
(802.1q in 802.1q). The function complies with IEEE 802.1q and IEEE 802.1ad.

QinQ provides a Layer 2 virtual private network (VPN) solution that is much cheaper and easier
than provided by multi-protocol label switch (MPLS). By using the VLAN QinQ technology,
the data packets carry two VLAN tags to distinguish different services. This changes the
limitation that only one VLAN tag is used to mark the data packets, and increases the number
of VLAN IDs. The inner VLAN is called the C-VLAN, representing the customer VLAN. The
outer VLAN is called S-VLAN, representing the service provider VLAN.
This topic describes the basic concepts that you need to be familiar with before you use the QinQ
feature.

14.2.3 Availability
The QinQ technology is applicable to the Ethernet private line service and the Ethernet LAN
service.
The QinQ technology is applied to the Ethernet line service and LAN service of the Ethernet
switching board.
The attributes of QinQ packets are closely related to the port attributes and service type.
Plan related parameters according to the specific application of the QinQ feature.
This topic describes the configuration flow and the corresponding configuration tasks of the
QinQ line service. An example is provided as additional information to help understand the
configuration.

QinQ provides a Layer 2 virtual private network (VPN) solution that is much cheaper and easier
than provided by multi-protocol label switch (MPLS). By using the VLAN QinQ technology,
the data packets carry two VLAN tags to distinguish different services. This changes the
limitation that only one VLAN tag is used to mark the data packets, and increases the number
of VLAN IDs. The inner VLAN is called the C-VLAN, representing the customer VLAN. The
outer VLAN is called S-VLAN, representing the service provider VLAN.
The functions of the QinQ technology are as follows:
l With the application of the QinQ technology, the number of VLAN IDs can reach 4096 x
4096. This solves the problem that the number of VLAN IDs cannot meet the requirement.
l Operators can plan VLAN resources independently and flexibly, thus simplifying network
configuration and maintenance.
l The QinQ technology, providing a cheaper and simpler L2 VPN solution, replaces the
MPLS technology.
l The QinQ technology enables the expansion of Ethernet services from local area networks
(LANs) to wide area networks (WANs).
The QinQ technology complies with the following standards:
l IEEE 802.1q
l IEEE 802.1ad

This topic describes the basic concepts that you need to be familiar with before you use the QinQ
feature.
14.2.2.1 Frame Format

The QinQ technology defines three types of Ethernet frames: Ethernet frame with only a C-
TAG, Ethernet frame with a C-TAG and an S-TAG, and Ethernet frame with only an S-TAG.
14.2.2.2 Network Attributes
The network attribute of each port (PORT or VCTRUNK) can be set to UNI, C-aware, or S-
aware depending on how the port processes the C-TAG and S-TAG.

14.2.2.3 Application of the QinQ Technology in Line Services

Introduction of the QinQ technology provides many new applications for line services.
14.2.2.4 Application of the QinQ Technology in LAN Services
The use of the QinQ technology provides the application of the EVPLAN service that is based
on the 802.1ad bridge.

The QinQ technology defines three types of Ethernet frames: Ethernet frame with only a C-
TAG, Ethernet frame with a C-TAG and an S-TAG, and Ethernet frame with only an S-TAG.
Ethernet Frame with Only a C-TAG

The Ethernet frame with only a C-TAG has the same format as the tagged frame defined in IEEE
802.1Q. Hence, the tagged frame defined in IEEE 802.1Q is an Ethernet frame that contains a
C-VLAN tag. For details on the format of a tagged frame, see Format of the tagged frame.
Figure 14-50 Format of the Ethernet frame with only a C-TAG

4 bytes
Destination Source FCS
C-TAG Length/Type Data
address address (CRC-32)
TCI
TPID PCP CFI VID
16 bits 3 bits 1 bit 12 bits
Ethernet Frame with a C-TAG and an S-TAG

In the case of an Ethernet frame that contains a C-TAG and an S-TAG, the S-TAG is added
before the C-TAG. The differences between the S-TAG and the C-TAG are as follows:
l The TPID is different.
As defined in IEEE 802.1ad, the value of the TPID in the S-TAG is 0x88a8, whereas the
value of the TPID in the C-TAG is 0x8100.
NOTE
The TPID in the S-TAG that is supported by the Ethernet switching board has the same value as the TPID
in the C-TAG. The TPID value is 0x8100. The TPID value in the S-TAG can be modified. For details,
see 14.2.7.3 Modifying the Type Field of QinQ Frames.
l The drop eligible indicator (DEI) replaces the CFI.
The DEI works with the PCP to indicate the priority of the S-TAG.

Figure 14-51 Format of the Ethernet frame with a C-TAG and an S-TAG
4 bytes
S-TAG C-TAG Length/Type Data
TCI
TPID PCP DEI VID
NOTE
Certain vendors use the Ethernet frames each of which contains a C-TAG and an S-TAG but whose type field
is not set to 0x8100. To ensure that the OptiX RTN 600 can be interconnected with the equipment of the vendors,
the Ethernet switching board of Huawei supports manual setting of the type field.
Ethernet Frame with Only an S-TAG

The Ethernet frame with only an S-TAG contains only an S-TAG and does not contain a C-
TAG.
Figure 14-52 Format of the Ethernet frame with only an S-TAG

4 bytes
S-TAG Length/Type Data
TCI
TPID PCP DEI VID
14.2.2.2 Network Attributes

The network attribute of each port (PORT or VCTRUNK) can be set to UNI, C-aware, or S-
aware depending on how the port processes the C-TAG and S-TAG.
UNI Port
A UNI port verifies and processes the outer tag of an Ethernet frame according to the TAG
attributes of the port. UNI ports cannot be used in the case of QinQ services.

C-Aware Port
A C-aware port is in an equivalent position as a UNI port in a network. A C-aware port considers
that an accessed packet does not contain an S-TAG. C-aware ports can be used in the case of
QinQ services.
NOTE
l C-TAG frames and untagged frames can normally enter and exit C-aware ports.
l When an S-TAG frame enters and exits a C-aware port, the port processes the S-TAG as a C-TAG.
l When a frame that contains an S-TAG and a C-TAG enters and exits a C-aware port, the port processes the
S-TAG as a C-TAG and does not process the inner C-TAG.
S-Aware Port
An S-aware port is in an equivalent position as a NNI port in a network. An S-aware port
considers that an accessed packet contains an S-TAG. S-aware ports can be used in the case of
QinQ services.
NOTE
l S-TAG frames or the frames that contain an S-TAG and a C-TAG can normally enter and exit S-aware ports.
l When a C-TAG frame enters and exits an S-aware port, the port processes the C-TAG frame as an S-TAG
frame.
l When an untagged frame enters and exits an S-aware port, the port discards the frame.
l When a frame that contains an S-TAG and a C-TAG enters and exits an S-aware port of an EMS6 board,
the port processes only the S-TAG and does not process the inner C-TAG.
14.2.2.3 Application of the QinQ Technology in Line Services

Introduction of the QinQ technology provides many new applications for line services.
Line Services Between C-Aware Ports

The line services between C-aware ports have two applications.
Table 14-35 Line services between C-aware ports
Type of Packet Operation Type Direction Description

(Type of Source
Port)
Data frames that Transparently Unidirectional/ Transparently

contain a C-VLAN transmit C-VLAN Bidirectional transmits packets
tag (C-aware port) according to the C-
VLAN.
Data frames that Transparently Unidirectional/ Transparently

contain a C-VLAN transmit C-VLAN Bidirectional transmits packets.
tag or do not contain
a C-VLAN tag (C-
aware port)

Line Services Between a C-Aware Port and an S-Aware Port

The line services between a C-aware port and an S-aware port have three applications.
Table 14-36 Line services between a C-aware port and an S-aware port
Type of Operation Direction Description
Packet (Type Type
of Source
Port)
Data frames that Add S-VLAN Unidirectional Transmits packets according to the
contain a C- C-VLAN and adds an S-VLAN tag
VLAN tag (C- to each packet.
aware port)
Bidirectional In the case of the service from a C-
aware port to an S-aware port, the
port transmits the packets according
to the C-VLAN and adds an S-
VLAN tag to each packet.
In the case of the service from an S-
aware port to a C-aware port, the
port transmits the packets according
to the C-VLAN and strips the S-
VLAN tag from each packet.
Data frames that Add S-VLAN Unidirectional Transmits packets and adds an S-
contain a C- VLAN tag to each packet.
VLAN tag or do
not contain a C- Bidirectional In the case of the service from a C-
VLAN tag (C- aware port to an S-aware port, the
aware port) port adds an S-VLAN tag to each
packet.
In the case of the service from an S-
aware port to a C-aware port, the
port strips the S-VLAN tag from
each packet.
S-TAG or S- Strip S-VLAN Unidirectional Transmits packets according to the

TAG + C-TAG S-VLAN and strips the S-VLAN
(S-aware port) tag from each packet.
NOTE
The priority of the S-VLAN tag added by the "Add S-VLAN" operation is 0 by default. The priority can be set.
Line Services Between S-Aware Ports

The line services between S-aware ports have two applications.

Table 14-37 Line services between S-aware ports
Type of Operation Direction Description

Packet (Type Type
of Source
Port)
S-TAG or S- Transparently Unidirectional/ Transparently transmits packets

TAG + C-TAG transmit S- Bidirectional according to the S-VLAN.
(S-aware port) VLAN
Translate S- Unidirectional/ Transmits packets according to the

VLAN Bidirectional S-VLAN, which is translated.
14.2.2.4 Application of the QinQ Technology in LAN Services

The use of the QinQ technology provides the application of the EVPLAN service that is based
on the 802.1ad bridge.
The IEEE 802.1ad bridge supports the data frame that has double VLAN tags. The outer VLAN
tag (namely, S-VLAN tag) is used to isolate VLANs. The IEEE 802.1ad bridge supports only
the port whose network attribute is set to C-aware or S-aware.
The IEEE 802.1ad bridge supports the following two switching modes. For details, refer to
Table 14-38.
1. The IEEE 802.1ad bridge does not check the contents of the VLAN tags in the data frames
that enter the bridge but performs Layer 2 switching according to the destination MAC
addresses of the data frames.
2. The IEEE 802.1ad bridge checks the contents of the VLAN tags in the data frames that
enter the bridge and performs Layer 2 switching according to the destination MAC
addresses and S-VLAN IDs of the data frames.
Table 14-38 Characteristics of the IEEE 802.1ad bridge
Bridge Type Bridge Switch Mode Bridge Ingress Filter

Learning
Mode
IEEE 802.1ad 1 SVL/Ingress Filter SVL Disabled

bridge Disable
2 IVL/Ingress Filter IVL Enabled
Enable
The C-aware ports are used to add and strip the S-VLAN tags. The S-aware ports are used to
transparently transmit the S-VLAN tags.
The ports that are mounted to the IEEE 802.1ad bridge support the following operation types:
l Add S-VLAN base for port

l Add S-VLAN base for port and C-VLAN

l Mount port
l Mount port and base for port and S-VLAN
This topic describes the four operation types when Bridge Switch Mode of the IEEE 802.1ad
bridge is set to IVL/Ingress Filter Enabled.
LAN Services That Enter and Exit the C-Aware Port

Table 14-39 lists the applications of the LAN services that enter and exit the C-aware port.
Table 14-39 LAN services that enter and exit the IEEE 802.1ad bridge through the C-aware port
Type of Data Operation Direction Description

Frame Type
Data frames that Add S-VLAN Ingress 1. When the data frames enter the
contain a C- Base for Port bridge through the C-aware port,
VLAN tag or do the data frames are added with
not contain a C- the preset S-VLAN tag.
VLAN tag 2. After the data frames enter the
bridge, the data frames are
forwarded in the bridge
according to the S-VLAN
filtering table.
Egress When the data frames leave the

bridge through the C-aware port,
the S-VLAN tag is stripped.
Data frames that Add S-VLAN Ingress 1. The entry detection is performed
contain a C- Base for Port for the data frames according to
VLAN tag and C-VLAN the C-VLAN tag.
2. The corresponding S-VLAN
tags are added to the data frames
according to the mapping
relation between the C-VLAN
tags and the S-VLAN tags of the
data frames (a). If the mapping
relation does not exist, the data
frames are discarded.
3. After the data frames enter the
filtering table.

bridge through the C-aware port,
the S-VLAN tag is stripped.

NOTE
a:
l The same C-aware port supports the mapping of different C-VLAN tags to the same S-VLAN tag. For
example, the data frames whose C-VLAN IDs are 1, 2, and 3 can be added with the same S-VLAN tag
whose ID is 100.
l The same C-aware port supports the mapping of different C-VLAN tags to different S-VLAN tags.
For example, the data frames whose C-VLAN IDs are 1, 2, and 3 can be added with the S-VLAN tags
whose IDs are 100, 200, and 300 respectively.
l The same C-aware port does not support the mapping of the same C-VLAN tag to different S-VLAN
tags at the same time. For example, the data frame whose C-VLAN ID is 1 cannot be added with the
S-VLAN tags whose IDs are 100, 200, and 300 at the same time.
LAN Services That Enter and Exit the S-Aware Port

Table 14-40 lists the applications of the LAN services that enter and exit the S-aware port.
Table 14-40 LAN services that enter and exit the IEEE 802.1ad bridge through the S-aware port
Type of Data Operation Direction Description

Frame Type
Data frames that Mount Port Ingress 1. The data frames that enter the
contain an S- bridge through the S-aware port
VLAN tagb are not filtered.
filtering table.

bridge through the S-aware port, the
data frames are transparently
transmitted.
Mount Port and Ingress 1. The entry filtering is performed

Base for Port according to the preset S-VLAN
and S-VLAN tag. The data frames that do not
belong to the S-VLAN are
discarded.
filtering table.

bridge through the S-aware port, the
data frames are transparently
transmitted.

NOTE
b:The data frame that enters the S-aware port must contain an S-VLAN tag. Otherwise, the port discards
the data frame.
14.2.3 Availability
The QinQ technology is applicable to the Ethernet private line service and the Ethernet LAN
service.
Table 14-41 Availability of the QinQ feature

EVPL (QinQ) EMS6 (all the versions) IDU 620
EVPLAN (IEEE 802.1ad

bridge)

The QinQ technology is applied to the Ethernet line service and LAN service of the Ethernet
switching board.
Relation with Other Features

QinQ is applied to the Layer 2 Switching, namely, the EVPLAN (802.1ad bridge) service.

The attributes of QinQ packets are closely related to the port attributes and service type.
Realization of QinQ in the Ethernet Line Service

This section, using the QinQ services illustrated in Figure 14-53 as an example, describes how
data frames are processed on a QinQ network.
Figure 14-53 EVPL (QinQ) Services
C-VLAN1 Service
NE1
network A
NE2 NE3
C-VLAN1
S-VLAN1 C-VLAN1 S-VLAN3 C-VLAN1
S-VLAN2 C-VLAN1 S-VLAN4 C-VLAN1
S-VLAN1 C-VLAN1
S-VLAN2 C-VLAN1 NE4 C-VLAN1
Service
network B
Frame of customer a
C-VLAN1
Frame of customer b

On the network, the data frames from NE1 to NE4 are processed as follows:
1. NE1 adds an S-TAG to each data frame from customer a and customer b that are connected
to NE1, and forwards the frames to NE2. NE1 adds an S-VLAN1 tag to each data frame
from customer a and an S-VLAN2 tag to each frame from customer b.
2. Based on the S-VLAN tags, NE2 transparently transmits the data frames of customer a and
customer b to NE3 of service provider B.
3. Because service provider B plans different S-VLAN tags for customer a and customer b,
NE3 translates the data frame that contains an S-VLAN1 tag into a data frame that contains
an S-VLAN3 tag, translates the data frame that contains an S-VLAN2 tag into a data frame
that contains an S-VLAN4 tag, and forwards the data frames to NE4.
4. NE4 removes the S-VLAN3 tag and S-VLAN4 tag, and forwards the data frames to the
Ethernet ports of customer a and customer b.
The data frame process from NE4 to NE1 is reverse to the preceding process.
Realization of QinQ in the Ethernet LAN Service

This section, using the EVPLAN (802.1ad bridge) service illustrated in Figure 14-54 as an
example, describes how data frames are processed on the 802.1ad bridge.
Figure 14-54 Example of the EVPLAN (802.1ad bridge) service

NE1 Node B1
Service C-VLAN
VoIP PORT1 VoIP 10
NE3 HSI 20
VCTRUNK1
PORT1
Node B2
HSI NE2
PORT2 VCTRUNK2
PORT1 Service C-VLAN
VoIP 30
HSI 40
NE3:EMS6 NE1
PORT1
S-VLAN 100 Node B1
PORT1
VoIP VCTRUNK1
S-VLAN 200 NE2

VCTRUNK2
PORT2
HSI
PORT1
Node B2
802.1ad bridge
PORT VCTRUNK
Strip S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
C-VLAN(10/30) Data(VoIP) S-VLAN(100) C-VLAN(10/30) Data(VoIP) C-VLAN(10/30) Data(VoIP)
C-VLAN(20/40) Data(HSI) S-VLAN(200) C-VLAN(20/40) Data(HSI) C-VLAN(20/40) Data(HSI)

As shown in Figure 14-54, the transmission network needs to carry the voice over IP (VoIP)
service and the high speed Internet (HSI) service. The VoIP service and the HSI service of Node
B1 and Node B2 that are connected to NE1 and NE2 respectively use different C-VLANs that
have been planned. To mark and schedule the VoIP service and the HSI service in a unified
manner on the aggregation node NE3, on the transmission network the planned S-VLAN tags
are added to the two types of services from the user side.
On the network, NE3 processes the data frames as follows:
1. The VoIP service and the HSI service of Node B1 and Node B2 are transparently transmitted
to NE3 through NE1 and NE2 respectively.
2. NE3 adds S-VLAN tag 100 to the VoIP service of Node B1, Node B2, and VoIP server
(with the C-VLANs 10 and 30).
3. NE3 adds S-VLAN tag 200 to the HSI service of Node B1, Node B2, and HSI server (with
the C-VLANs 20 and 40).
4. After these data frames carrying the S-VLAN tag enter the 802.1ad bridge, the Layer 2
switching is performed according to the Ethernet port specified in the S-VLAN filtering
table. When the data frames carrying the S-VLAN tag leave the bridge from the
corresponding port due to being forwarded, the S-VLAN tag is removed.

Plan related parameters according to the specific application of the QinQ feature.
14.2.6.1 EVPL Services Based on QinQ

Plan related parameters according to the specific application of the QinQ technology in the EVPL
service.
14.2.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge
Plan related parameters according to the application of the QinQ technology in the LAN services.
14.2.6.1 EVPL Services Based on QinQ

Plan related parameters according to the specific application of the QinQ technology in the EVPL
service.
Prerequisite
You must have understood the specific applications of the QinQ feature.
Procedure
Step 1 Plan the network attributes of the ports according to the actual requirements.
Adhere to the following principles when planning the network attributes of the ports:
l If packets need to be forwarded according to C-VLAN tags or C-VLAN tags need to be

translated, select the line services between C-aware ports.
l If S-VLAN tags need to be added/stripped, select the line services between a C-aware port
and an S-aware port.
l If packets need to be forwarded according to S-VLAN tags or S-VLAN tags need to be
translated, select the line services between S-aware ports.

Step 2 Select a QinQ operation type according to the actual requirements.
Adhere to the following principles when planning the QinQ operation type:
l Check whether operations are based on ports, based on ports + C-VLAN, or based on ports
+ S-VLAN.
l Check whether unidirectional operations or bidirectional operations are required.
Step 3 Allocate S-VLAN tags for customers.
Adhere to the following principles when planning S-VLAN tags:
l The S-VLAN tag allocated to each customer must be unique.

l If a customer requires multiple S-VLAN tags, allocate a section of consecutive S-VLAN tags
to the customer. For example, allocate 100-109 to customer a and 110-119 to customer b.
----End
Example
The following describes how to plan QinQ line services. The QinQ services illustrated in Figure
14-53 are provided as an example. The ports used in this example are shown in Figure 14-55.
Figure 14-55 Ports used by the QinQ line services
Service
PORT1 NE1 network A
Service
NE2 NE3 network B
PORT2
VCTRUNK1
VCTRUNK1
VCTRUNK1
VCTRUNK2 VCTRUNK2
PORT1
NE4
VCTRUNK1
PORT2
1. Plan the network attributes of the ports.

In the case of NE1 and NE4, plan the network attribute of the related PORTs as C-Aware
and the network attribute of the related VCTRUNKs as S-Aware because NE1 and NE4
need to add/remove S-VLAN tags.
In the case of NE2 and NE3, plan the network attribute of the related VCTRUNKs as S-
Aware because NE2 and NE3 need to forward packets according to S-VLAN tags.
2. Plan QinQ operation types.
In the case of NE1 and NE4, select the bidirectional "Add S-VLAN" operation because
NE1 and NE4 can forward all the packets based on ports and do not need to recognize the
packet type.
In the case of NE2, select the bidirectional "Transparently transmit S-VLAN" operation
because NE2 needs to transparently transmit packets according to S-VLAN tags.

In the case of NE3, select the bidirectional "Translate S-VLAN" operation because NE3
needs to translate S-VLAN tags according to S-VLAN tags and does not translate S-VLAN
tags based on ports.
3. Plan S-VLAN tags.
Plan S-VLAN tags on an overall basis. The S-VLAN tags allocated to customer a and
customer b by service provider A are 100 and 110 respectively, and the S-VLAN tags
allocated to customer a and customer b by service provider B are 200 and 210 respectively.
14.2.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge

Plan related parameters according to the application of the QinQ technology in the LAN services.
Prerequisite
You must be familiar with the specific application of the QinQ feature.
Procedure
Step 1 Plan the network attributes of the ports that are mounted to the IEEE 802.1ad bridge according
to the actual requirements.
Adhere to the following principles when planning the network attributes of the ports:
l If the packets that enter the port do not contain a VLAN tag or contain a C-VLAN tag, plan
the network attribute of the port as C-Aware.
l If the packets that enter the port contain an S-VLAN tag, plan the network attribute of the
port as S-Aware.
Step 2 Select a QinQ operation type according to the actual requirements.
Adhere to the following principles when planning the QinQ operation type:
l In the case of the C-aware port, select "Add S-VLAN Base for Port" or "Add S-VLAN Base
for Port and C-VLAN". For details, refer to Table 14-39.
l In the case of the S-aware port, select "Mount Port" or "Mount Port and Base for Port and
S-VLAN". For details, refer to Table 14-40.
Step 3 Allocate S-VLAN tags to customers or service types.
Adhere to the following principles when planning S-VLAN tags:
l The S-VLAN tag allocated to each customer or each service type must be unique.
l If a customer or service type requires multiple S-VLAN tags, allocate a section of consecutive
S-VLAN tags to the customer or service type. For example, allocate S-VLAN tags 100-109
to customer A or service type A (for example, VoIP services), and allocate S-VLAN tags
110-119 to customer B or service type B (for example, HSI services).
----End
Example
This topic considers the EVPLAN services (IEEE 802.1ad bridge) that are illustrated in Figure
14-54 as an example to describe the planning method.

1. Plan the network attributes of the ports.

Plan the network attributes of PORT1, PORT2, VCTRUNK1, and VCTRUNK2 as C-
Aware because NE3 needs to add and strip S-VLAN tags.
Plan the network attributes of the related PORTs as UNI because NE2 and NE3 need to
transparently transmit the services.
2. Plan QinQ operation types.
Planning NE3 is more complicated than planning NE1 and NE2.
Port Accessed Service Planned Operation Type
PORT1 VoIP services Add S-VLAN Base for Port
PORT2 HSI services Add S-VLAN Base for Port
VCTRUNK1 VoIP services of node B1 (C- Add S-VLAN Base for Port and
VLAN 10) C-VLAN
HSI services of node B1 (C-
VLAN 20)
VCTRUNK2 VoIP services of node B2 (C- Add S-VLAN Base for Port and
VLAN 30) C-VLAN
HSI services of node B2 (C-
VLAN 40)
In the case of NE1 and NE2, you need not plan QinQ operation types because NE1 and
NE2 transparently transmit the Ethernet services.
3. Plan S-VLAN tags.
Plan S-VLAN tags on an overall basis. The S-VLAN tag allocated to the VoIP services (C-
VLAN IDs being 10 and 30) is 100 and the S-VLAN tag allocated to the HSI services (C-
VLAN IDs being 20 and 40) is 200 on the transport network side.

QinQ line service. An example is provided as additional information to help understand the
configuration.
14.2.7.1 Configuration Flow (EVPL Services Based on QinQ)
This topic describes the configuration flow of the EVPL service that is based on QinQ.
14.2.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge)
This topic describes the configuration flow of the EVPLAN service that is based on the 802.1ad
bridge.

14.2.7.1 Configuration Flow (EVPL Services Based on QinQ)

This topic describes the configuration flow of the EVPL service that is based on QinQ.
Figure 14-56 Configuration flow for the QinQ line service
Start
Is the type field of Yes

QinQ frames processed by the
interconnected equipment
set to "0x8100"?
No
1
Modify the type field of QinQ frames
2
Configure the external port of the
Ethernet board
3
Configure the internal port of the
Ethernet board
4
Create QinQ line services
5
Create cross-connections
for Ethernet services
End
Table 14-42 Description of the configuration flow of the QinQ line service
Number Description
1 For the configuration flow, see 14.2.7.3 Modifying the Type Field of QinQ
Frames.

Number Description
2 For the configuration flow, see 14.3.7.1 Configuring External Ethernet

Ports.
3 For the configuration flow, see 14.4.7.1 Configuring the Internal Port of
the Ethernet Board.
4 For the configuration flow, see 14.2.7.4 Creating QinQ Line Services.
5 Create the cross-connection from the paths that are bound to the VCTRUNK
to the corresponding timeslots on the line.
NOTE
To configure the QoS feature for the QinQ line service, see 14.7 Configuring QoS.
14.2.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge)
This topic describes the configuration flow of the EVPLAN service that is based on the 802.1ad
bridge.

Figure 14-57 Configuration flow for the EVPLAN service that is based on the 802.1ad bridge
Start
Is the type field of QinQ

Yes
frames processed by the
interconnected equipment
set to "0x8100"?
No
1
Modify the type field of QinQ frames
2
Configure the external port of the Ethernet
board
3
Configure the internal port of the Ethernet
board
4
Create the EVPLAN services based on
IEEE 802.1ad bridge
5
Create the VLAN filter table
6
Modify the Hub/Spoke attribute of the port
mounted to a bridge
7
Create cross-connections for Ethernet
services
End
Table 14-43 Description of the configuration flow of the EVPLAN service that is based on the
802.1ad bridge
Number Description
1 For the configuration process, see 14.2.7.3 Modifying the Type Field of
QinQ Frames.

Number Description
2 For the configuration process, see 14.3.7.1 Configuring External Ethernet

Ports.
3 For the configuration process, see 14.4.7.1 Configuring the Internal Port
of the Ethernet Board.
4 For the configuration process, see 14.2.7.5 Creating the EVPLAN Services
That Are Based on the IEEE 802.1ad Bridge.
5 For the configuration process, see 14.1.4.5 Creating the VLAN Filter
Table.
6 For the configuration process, see 14.6.9 Modifying the Mounted Port of a
Bridge.
If the communication between ports needs to be isolated, you need to set the
Hub/Spoke attribute to "Spoke". In this case, Step 6 is required.
NOTE
l To configure the Layer 2 switching feature for the EVPLAN services that are based on the IEEE 802.1ad
bridge, see 14.6 Configuring Layer 2 Switching.
l To configure the QoS feature for the EVPLAN services that are based on the IEEE 802.1ad bridge, see
14.7 Configuring QoS.

Prerequisite
Precautions
Procedure

Step 3 Click Apply.
----End
Parameters
frames.

Prerequisite
Precautions
Procedure
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.
The system displays the Create Ethernet Line Service dialog box.

NOTE
The result of configuring the port attributes during the Ethernet line service configuration process is the same
as the result of directly configuring the Ethernet service port attributes.
Step 6 Click OK.
----End
Parameters
Service Type EPL, EVPL(QinQ) EPL When creating the QinQ line service, set this
parameter to EVPL(QinQ).


Bidirectional Unidirectional, only the service from
the service source to the service sink is
created.
Bidirectional, both the service from the
service source to the service sink and the
service from the service sink to the
Operation Type Transparently Add S-VLAN l For the meanings of the values, see
transmit C-VLAN, 14.2.2.3 Application of the QinQ
Translate C-VLAN, Technology in Line Services.
Add S-VLAN, l Set this parameter according to actual
Transparently situations.
transmit S-VLAN,
Translate S-VLAN,
Strip S-VLAN (only
for unidirectional
services)
PORT as the source port.
Source C-VLAN 1 to 4095 - l You can set this parameter to null, a

(e.g. 1,3-6) number, or several numbers. When you
numbers 1, 3, 4, 5, and 6.
l The number of C-VLANs set in this
number of C-VLANs set in Sink C-
VLAN (e.g. 1,3-6).
the service source.
work as the service source.

Source S-VLAN 1 to 4095 - l This parameter must be set to a

numerical value.
l Only the services of the source port
whose S-VLAN IDs are equal to the
value of this parameter work as the
service source.
VCTRUNK as the sink port.
Sink C-VLAN (e.g. 1 to 4095 - l You can set this parameter to null, a
1,3-6) number, or several numbers. When you
numbers 1, 3, 4, 5, and 6.
VLAN (e.g. 1,3-6).
service sink.
work as the service sink.
Sink S-VLAN 1 to 4095 - l This parameter must be set to a

numerical value.
l Only the services of the sink port whose
S-VLAN IDs are equal to the value of
this parameter work as the service sink.

C-VLAN Priority AUTO, Priority0- AUTO l This parameter specifies the priority of
Priority7 the newly added C-VLAN tag.
priority of the C-VLAN tag is 0.
performed according to the C-VLAN
the default value.
S-VLAN Priority AUTO, Priority0- AUTO l This parameter is valid only when
Priority7 Operation Type is set to Add S-
VLAN.
l This parameter specifies the priority of
the newly added S-VLAN tag.
priority of the S-VLAN tag is 0.
performed according to the S-VLAN
the default value.
Prerequisite
Precautions
Procedure
Step 2 Click New.


Step 3 Set the attributes of the IEEE 802.1ad bridge.
Step 4 Configure service mounting relations.

2. Set the parameters for configuring mounted services.
3. Click Add Mount Port.
4. Repeat Step 4.2 to Step 4.3 to add the other mount ports.
5. Click OK.
the VCTRUNK.
4. Select the required items in Available Resources and Available Timeslots and click
.

NOTE
The result of setting the port attributes during the configuration of the private network service is consistent
with the result of directly setting the attributes of the Ethernet service port.
6. Click OK.
----End
Parameters

VB Type 802.1q, 802.1d, 802.1q l In this example, the IEEE 802.1d bridge
802.1ad and IEEE 802.1q bridge need not be
created. Hence, do not set VB Type to
802.1d or 802.1q.
Enable Enable the VLANs share one MAC address
SVL/Ingress Filter table. When the bridge uses the IVL
Disable mode, all the VLANs correspond to their
VLAN ID is not equal to the VLAN ID

Operation Type Add S-VLAN Base Add S-VLAN Base For the meaning of each operation type, see
for Port for Port 14.2.2.4 Application of the QinQ
Add S-VLAN Base Technology in LAN Services.
for Port and C-
VLAN
Mount Port
Mount Port and
Base for Port and S-
VLAN
VB Port - - This parameter specifies the ID of the

logical port of the bridge.
Mount Port - - Select the external physical port or internal

VCTRUNK port of the Ethernet switching
board that is mounted to the IEEE 802.1ad
bridge.
C-VLAN 1-4095 - This parameter is valid only when

Operation Type is set to Add S-VLAN
Base for Port and C-VLAN.
This parameter specifies the mapping
relation between the C-VLAN tag carried by
the data frame and the S-VLAN tag to be
added.
S-VLAN 1-4095 - l When Operation Type is set to Add S-

VLAN Base for Port, this parameter
specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN tag.
l When Operation Type is set to Add S-
VLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify the
mapping relation between the S-VLAN
tag to be added and the C-VLAN tag
carried by the data frame that enters the
IEEE 802.1ad bridge.
Port, this parameter is invalid.
Port and Base for Port and S-VLAN,
this parameter specifies the S-VLAN tag
to be carried by the data frames that enter
the IEEE 802.1ad bridge.

port.

Available Bound - - Adhere to the following principles when

Paths planning and setting this parameter:
the service needs.
l The VC-4-1s of the EMS6 board support
only VC-3 paths, whereas the VC-4-2s
of the EMS6 board support both VC-12
paths and VC-3 paths. Hence, give
VC-3 paths.
14.3 Configuring Features of Ethernet Ports

To effectively work with the data communication equipment at the client side, the Ethernet port
supports the auto-negotiation function, Jumbo frames, and flow control function.

When the external port (namely, PORT) of the Ethernet service board is interconnected with the
data communication equipment on the client side, you need to set the major attributes of the
external port so that the Ethernet services on the client side can be accessed normally.
This topic describes the basic concepts that you need to be familiar with before you use the
Ethernet port feature.
14.3.3 Availability
The Ethernet port feature requires the support of the applicable equipment and boards.
The auto-negotiation function, Jumbo frames, and flow control function do not affect other
features.


The auto-negotiation function and the flow control function comply with IEEE 802.3.
Before you plan Ethernet port features, obtain the information of the client-side equipment.
This topic describes the configuration tasks relevant to the Ethernet port feature.

When the external port (namely, PORT) of the Ethernet service board is interconnected with the
data communication equipment on the client side, you need to set the major attributes of the
external port so that the Ethernet services on the client side can be accessed normally.
The external port of the Ethernet service board is the external physical interface and is also called
the user-side interface. The external port is used to access the Ethernet services on the user side.
The features relevant to the external port of the Ethernet service board include the auto-
negotiation, Jumbo frame, and flow control.
Auto-Negotiation Function
The external port of the Ethernet service board and the data communication equipment at the
opposite end must work in the same duplex mode and operate at the same rate. If the working
modes at the two ends do not match, the transmission efficiency is reduced and the data may
even be lost.
Jumbo Frames
An Ethernet frame requires that the maximum size of the payload must not exceed 1500 bytes.
This requirement severely affects the transmission efficiency of certain high-speed data services.
To improve the transmission efficiency, the Jumbo frame technology is developed. A Jumbo
frame adopts the structure of an ordinary Ethernet frame but does not have a requirement for the
maximum size of the payload. To differentiate a Jumbo frame from an ordinary Ethernet frame,
we define the type field of a Jumbo frame as "0x8870".
Flow Control Function

due to buffer overflow, proper flow control measures must be taken.

Ethernet port feature.
14.3.2.1 Auto-Negotiation Function

14.3.2.2 Jumbo Frames
The maximum length of the payload of an Ethernet frame must not exceed 1500 bytes. This
requirement greatly affects the transmission efficiency of certain high-speed data services. To
improve the transmission efficiency, the Jumbo frame technology emerged.
14.3.2.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.

NOTE
The following sections describe the basic concepts related to the auto-negotiation function, including all
the working modes. The working mode supported by each Ethernet port of the equipment may be different.
For details, refer to 14.3.7.1 Configuring External Ethernet Ports.
Auto-Negotiation Function of FE Electrical Ports

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 an Ethernet port
does not match that of its opposite port, the two ports cannot communicate. 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 to enable the working mode of the local Ethernet port to match
the working mode of the opposite end.
Table 14-44 lists the auto-negotiation rules of FE electrical ports.
Table 14-44 Auto-negotiation rules of FE electrical ports (when the local port adopts the auto-
negotiation mode)
Working Mode of the Opposite Port Auto-Negotiation Result
Auto-negotiation 100M full-duplex
10M half-duplex 10M half-duplex
10M full-duplex 10M half-duplex

NOTE
From Table 14-44, it is evident that when the working mode of the opposite equipment is 10M full-duplex or
100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of both
sides. As a result, certain packets are lost. Hence, when the working mode of the opposite equipment is 10M
full-duplex or 100M full-duplex, set the working mode of the local equipment to 10M full-duplex or 100M full-
duplex.
When the FE electrical ports on both sides are working in the auto-negotiation mode, the
equipment on both sides 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 14-45 lists the auto-negotiation rules of GE electrical ports.
Table 14-45 Auto-negotiation rules of GE electrical ports (when the local port adopts the auto-
negotiation mode)
Working Mode of the Opposite 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
From Table 14-45, it is evident that when the working mode of the opposite equipment is 10M
full-duplex or 100M full-duplex, the auto-negotiation result cannot realize the matching between
the working modes of both sides. As a result, certain packets are lost. Hence, when the working
mode of the opposite equipment is 10M full-duplex or 100M full-duplex, set the working mode
of the local equipment to 10M full-duplex or 100M full-duplex.
When the GE electrical ports on both sides are working in the auto-negotiation mode, the
equipment on both sides 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.

NOTE
If the GE optical port of the equipment on one side works in the 1000M full-duplex mode and the GE optical
port of the equipment on the other side works in the auto-negotiation mode, a link error occurs due to an auto-
negotiation failure, and as a result, a LINK_ERR alarm is generated.
14.3.2.2 Jumbo Frames

The maximum length of the payload of an Ethernet frame must not exceed 1500 bytes. This
requirement greatly affects the transmission efficiency of certain high-speed data services. To
improve the transmission efficiency, the Jumbo frame technology emerged.
A Jumbo frame adopts the structure of a common Ethernet frame but does not have the
requirement for the maximum length of the payload. Furthermore, the type field of the Jumbo
frame is defined as 0x8870 to differentiate a Jumbo frame from a common Ethernet frame.
Both the EFT4 and EMS6 boards can receive and transmit the Jumbo frame whose length does
not exceed 9600 bytes; however, the ways for these two boards to process the Jumbo frame are
different.
l The Ethernet port of the EFT4 board checks the type field in an Ethernet frame to determine
whether the Ethernet frame is a Jumbo frame. If the Ethernet frame is a Jumbo frame, the
maximum frame length is not restricted.
l The Ethernet port of the EMS6 board checks whether an Ethernet frame whose length
exceeds 1536 bytes is a Jumbo frame. All the frames are restricted by the maximum frame
length.
l VCTRUNKs 1-4 of the EFT4 board and VCTRUNKs 5-8 of the EMS6 board check whether
an Ethernet frame is a Jumbo frame. If an Ethernet frame is not a Jumbo frame but its length
exceeds the maximum frame length, the board discards the frame. VCTRUNKs 1-4 of the
EMS6 board do not check Jumbo frames. The EMS6 board discards any frame whose length
exceeds the maximum frame length.
l The maximum frame length (namely, the MTU), is a parameter of the Ethernet port. In the
case of common Ethernet frames, the Ethernet service board discards the frame whose
length exceeds the value of this parameter.
The default type field of a Jumbo frame is "0x8870".

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 uses back pressure to control flow. The full-duplex Ethernet uses
PAUSE frames to control flow. Currently, because the half-duplex Ethernet is seldom applied,
the flow control function realized by the equipment is developed for only the full-duplex
Ethernet.
The full-duplex Ethernet flow control function realized by the equipment is classified into two
types: auto-negotiation flow control and non-auto-negotiation flow control.
NOTE
The following sections describe the basic concepts related to the flow control function, including all the
flow control modes. The flow control mode supported by each Ethernet port of the equipment may be
different. For details, refer to 14.3.7.1 Configuring External Ethernet Ports.

Auto-Negotiation Flow Control

When the Ethernet port is working in the auto-negotiation mode, you can adopt the auto-
negotiation flow control function. The auto-negotiation flow control mode includes the
following:
l Asymmetric PAUSE toward the link partner
In the case of congestion, the port can send PAUSE frames but cannot process received
PAUSE frames.
l Symmetric PAUSE
The port can send and process PAUSE frames.
l Both asymmetric and symmetric PAUSE
The port has the following three capabilities:
Sends and processes PAUSE frames.
Sends but does not process PAUSE frames.
Processes but does not send PAUSE frames.
l Disabled
The port does not send or process PAUSE frames.
Non-Auto-Negotiation Flow Control

When the Ethernet port is working in a fixed working mode, you can adopt the non-auto-
negotiation flow control function. The non-auto-negotiation flow control modes includes the
following:
l Send only
In case of congestion, the port can send PAUSE frames but cannot process received PAUSE
frames.
l Receive only
In case of congestion, the port can process received PAUSE frames but cannot send PAUSE
frames.
l Send and receive
The port can send PAUSE frames and can also process received PAUSE frames.
l Disabled
The port does not send or process PAUSE frames.
14.3.3 Availability
The Ethernet port feature requires the support of the applicable equipment and boards.
Table 14-46 Availability of the Ethernet port feature
Auto-negotiation EFT4 (all the versions) IDU 610/620
EMS6 (all the versions) IDU 620
- IDU 605 1F/2F

IFH2 (all the versions) IDU 620
Jumbo frame EFT4 (all the versions) IDU 610/620
Flow control EFT4 (all the versions) IDU 610/620
- IDU 605 1F/2F
IFH2 (all the versions) IDU 620

The auto-negotiation function, Jumbo frames, and flow control function do not affect other
features.

The auto-negotiation function and the flow control function comply with IEEE 802.3.
The auto-negotiation function uses fast link pulses and normal link pulses to transfer information
of the working mode in such a manner that no packet or upper layer protocol overhead is added.
The Ethernet board adopts PAUSE frames to realize the flow control function.

The auto-negotiation function uses fast link pulses and normal link pulses to transfer information
of the working mode in such a manner that no packet or upper layer protocol overhead is added.
NOTE
The following describes the realization principle of the auto-negotiation function. The auto-negotiation function
of FE electrical ports is provided as an example.
The fast link pulse (FLP) is called the 10BASE-T link integrity test pulse sequence. Each device
must be capable of issuing FLP bursts at power up, on command from management, or due to
user interaction. The FLP burst consists of a series of link integrity test pulses that form an
alternating clock/data sequence. Extraction of the data bits from the FLP burst yields a link code
word that identifies the working modes supported by the remote device, as well as certain
information used for the handshake mechanism of the auto-negotiation function.
To maintain interoperability with existing 10BASE-T devices, the auto-negotiation function also
supports the reception of 10BASE-T compliant link integrity test pulses. 10BASE-T link pulse
activity is referred to as the normal link pulse (NLP) sequence. A device that fails to respond to
the FLP burst sequence by returning only the NLP sequence is treated as a 10BASE-T compatible
device.
The first pulse in an FLP burst is defined as a clock pulse. Clock pulses within an FLP burst are
spaced at 125 us. Data pulses occur in the middle of two adjacent clock pulses. The presence of

a positive pulse represents a logic one and the absence of a pulse represents a logic zero. An
FLP burst consists of 17 clock pulses and 16 data pulses (if all data bits are 1). The NLP waveform
is simpler than the FLP waveform. The NLP sends a positive pulse every 16 ms when no data
frame needs to be transmitted.
Figure 14-58 Waveform of a single FLP
T3 T1
Clock pulses
T2
First bit on wire
Data 1 1 0 1
Encoding D D D D
0 1 2 3
T1: 100 ns T2: 62.5 us T3: 125 us
Figure 14-59 Consecutive FLP bursts and NLPs

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

The Ethernet board adopts PAUSE frames to realize the flow control function.
The realization principle of the flow control function is as follows:
1. When congestion occurs in the receive queue of an Ethernet port (the data in the receive
buffer exceeding a certain threshold) and the port is capable of sending PAUSE frames,
the port sends a PAUSE frame to the opposite end. The pause-time value in the frame is N
(0<N65535).
2. After receiving the PAUSE frame, and being capable of processing PAUSE frames, the
Ethernet port at the opposite end stops sending data within a specified period of time N
(whose unit is the time needed for sending 521 bits).

3. If the congestion at the receive port is cleared (the data in the receive buffer is below a
certain threshold) but the pause-time does not end, the port sends a PAUSE frame whose
pause-time is 0 to notify the opposite end to start sending data.
IEEE 802.3 defines the format of the PAUSE frame as follows:
l Destination address: 01-80-C2-00-00-01 (multicast address)

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

XX-XX 2 octets
(pause-time)
Reserved

Before you plan Ethernet port features, obtain the information of the client-side equipment.
Procedure
Step 1 Plan the working mode of the Ethernet port.
Ensure that the working modes of the Ethernet ports at the two ends should be the same.
Step 2 Plan the parameter MTU.
In the case of the EFT4 board, adhere to the following principles when planning the MTU of
the Ethernet port:
l The MTU must be greater than the length of the maximum frame among all the L2 data
frames that are to be transmitted.
l The value of the MTU ranges from 1518 to 1535 bytes.
l The default value of the MTU is 1522 bytes, which is the sum of the length of the maximum
basic frame and the length of the VLAN label.
l The MTU is invalid for the Jumbo frame.

In the case of the EMS6 board, adhere to the following principles when planning the MTU of
the Ethernet port:
l The MTU should be greater than the length of the maximum frame among all L2 data frames
to be transmitted.
l The value of the MTU ranges from 1518 to 9600 bytes.
l The default value of the MTU is 1522 bytes, which is the sum of the length of the maximum
basic frame and the length of the VLAN label.
l The MTU parameter restricts the maximum length of a Jumbo frame.
Step 3 Plan the flow control parameters for the Ethernet port.
Adhere to the following principles when planning the flow control parameters for the Ethernet
port:
l The flow control parameters are valid only for the full-duplex Ethernet.
l The flow control parameters are valid only for the Ethernet transparent transmission service.
l When the Ethernet port works in the auto-negotiation mode, use the auto-negotiation flow
control parameter.
l When the Ethernet port works in a fixed working mode, use the non-auto-negotiation flow
control parameter.
l The flow control parameters at both sides must match each other. The flow control function
must not be enabled at one side and disabled at the other side.
l It is recommended that you enable the flow control function for the Ethernet board and for
the opposite equipment on the network with flow bursts.
----End

This topic describes the configuration tasks relevant to the Ethernet port feature.
14.3.7.1 Configuring External Ethernet Ports

14.3.7.2 Modifying the Type Field of Jumbo Frames
14.3.7.1 Configuring External Ethernet Ports

Prerequisite
The Ethernet board must be included in the NE Panel.

Precautions
l The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
Ethernet ports FE1-FE4 of an EFT4 board correspond to PORT1-PORT4 respectively.
The EFT4 board does not support the setting of TAG attributes, network attributes, and
advanced attributes.
Ethernet ports FE1-FE4 of an EMS6 board correspond to PORT1-PORT4 respectively.
Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.
l The IDU 605 IF/2F supports the Ethernet board EMS4 (a logical board).
Ethernet ports FE1-FE3 of an EMS4 board (a logical board) correspond to PORT1-
PORT3 respectively. Port FE4/GE1 of an EMS4 board corresponds to PORT4.
Ethernet ports FE1-FE2 of an EM4T board correspond to PORT1-PORT2 respectively.
Ports GE1 and GE2 of an EM4T board corresponds to PORT3 and PORT4 respectively.
l The following procedures describe how to configure the external port of an EMS6 board.
The EFT4 board does not support the configuration of the TAG attributes, network
attributes, and advanced attributes.
l The Hybrid IF board (IFH2) provides the GE port for accessing Ethernet services and it
supports certain Ethernet service access functions. The procedure for configuring the
Ethernet port of the IFH2 board is similar to the procedure for configuring the external
Ethernet port. The IFH2 board, however, supports the configuration of only the basic
attributes and flow control function.
Procedure
Management > Ethernet Interface from the Function Tree. Select External Port.
NOTE
If you need to configure the attributes of the Ethernet port on the IFH2 board, select the IFH2 board in the
NE Explorer.
Step 2 Set the basic attributes of the port.

1. Click the Basic Attributes tab.
2. Set the basic attributes of the port.
3. Click Apply.
Step 3 Set the flow control mode of the port.
1. Click the Flow Control tab.
2. Set the flow control mode of the port.

3. Click Apply.
3. Click Apply.
3. Click Apply.
Step 6 Optional: Set the advanced attributes of the port.
1. Click the Advanced Attributes tab.
2. Set the advanced attributes of the port.
3. Click Apply.
----End

Parameters
Enabled/Disabled Enabled, Disabled Disabled l In the case of the port that accesses
services, set this parameter to Enabled.
In the case of other ports, set this
parameter to Disabled.
l If this parameter is set to Enabled for the
port that does not access services, an
ETH_LOS alarm may be generated.
Working Mode 10M Full-Duplex, Auto-Negotiation l The Ethernet ports of different types
Auto-Negotiation l When the equipment on the opposite side
(EFT4) works in the auto-negotiation mode, set
10M Half-Duplex, the working mode of the equipment on
10M Full-Duplex, the local side to Auto-Negotiation.
100M Full-Duplex, works in the full-duplex mode, set the
1000M Full- working mode of the equipment on the
Duplex, Auto- local side to 10M Full-Duplex, 100M
Negotiation (EMS6) Full-Duplex, or 1000M Full-Duplex
Auto-Negotiation, depending on the port rate of the
100M Full-Duplex, l When the equipment on the opposite side
1000M Full-Duplex works in the half-duplex mode, set the
(IFH2) working mode of the equipment on the
10M Half-Duplex, local side to 10M Half-Duplex, 100M
10M Full-Duplex, Half-Duplex, or Auto-Negotiation
100M Half-Duplex, depending on the port rate of the
Auto-Negotiation (a l The GE optical interface on the EMS6
logical board EMS4, board supports the 1000M full-duplex
PORT1-PORT3) mode only.
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M Full-
Duplex, Auto-
Negotiation (a
logical board EMS4,
PORT4)

Maximum Frame 1518-1535 (EFT4) 1522 The value of this parameter should be
Length 1518-9600 (EMS6) greater than the maximum length of a frame
among all the data frames to be transported.
1522/1632 (a logical
board EMS4) In the case of the EFT4 board, this parameter
is invalid for Jumbo frames. In the case of
the EMS6 board, this parameter has a
restriction on Jumbo frames.
If Jumbo frames are not considered and the
accessed services are ordinary Ethernet
frames that use VLAN tags or do not have
VLAN tags, it is recommended that you use
the default value. If the access services
include services that use double tags such as
QinQ services, it is recommended that you
set this parameter to 1526.
In the case of the IDU 605 1F/2F, set
Maximum Frame Length of all the ports
on the logical EMS4 board to the same
value.
MAC Loopback Non-Loopback, Non-Loopback l When this parameter is set to Inloop, the
Inloop Ethernet frame signals that are to be sent
to the remote end are looped back.
PHY Loopback Non-Loopback, Non-Loopback l When this parameter is set to Inloop, the
Inloop Ethernet physical signals that are to be
sent to the remote end are looped back.

Non- Disabled, Enable Disabled l This parameter is used when Working

Autonegotiation Symmetric Flow Mode is not set to Auto-Negotiation.
Flow Control Mode Control, Send Only, l When this parameter is set to Enable
Receive Only (EFT4 Symmetric Flow Control, the port can
and EMS6) send PAUSE frames and process
Disabled, Enable received PAUSE frames.
Symmetric Flow l When this parameter is set to Send
Control (IFH2) Only, the port can send PAUSE frames
Disabled, Enable (a in the case of congestion but cannot
logical board process received PAUSE frames.
EMS4) l When this parameter is set to Receive
Only, the port can process received
PAUSE frames but cannot send PAUSE
frames in the case of congestion.
l When this parameter is set to Enable for
the logical EMS4 board, the port can
send PAUSE frames and process
l The non-autonegotiation flow control
mode of the equipment on the local side
must match the non-autonegotiation
flow control mode of the equipment on
the opposite side.

Autonegotiation Disabled, Enable Disabled l This parameter is used when Working

Flow Control Mode Symmetric/ Mode is set to Auto-Negotiation.
Control, Enable Symmetric Flow Control, the port can
Symmetric Flow send and process PAUSE frames.
Control, Enable
Control (EFT4 and Dissymmetric Flow Control, the port
EMS6) can send PAUSE frames in the case of
congestion but cannot process received
Disabled, Enable PAUSE frames.
Symmetric Flow
Control (IFH2) l When this parameter is set to Enable
Symmetric/Dissymmetric Flow
Disabled, Enable Control, the port can perform as
Symmetric Flow follows:
Control (a logical
board EMS4) Sends and processes PAUSE frames.
Sends but does not process PAUSE
frames.
Processes but does not send PAUSE
frames.
l The autonegotiation flow control mode
of the equipment on the local side must
match the autonegotiation flow control
mode of the equipment on the opposite
side.

situations.


l For using this parameter, see Table
14-47.
situations.

14-47.
value.
the tag attributes.
services.
created.
Enabling Broadcast Enabled, Disabled Disabled This parameter specifies whether to restrict
Packet Suppression the traffic of broadcast packets according to
the ratio of the broadcast packets to the total
packets. When a broadcast storm may occur
in the equipment on the opposite side, set
this parameter to Enabled.
Broadcast Packet 10% to 100% 30% The port discards the received broadcast
Suppression packets when the ratio of the received
Threshold broadcast packets to the total packets
exceeds the value of this parameter. The
value of this parameter should be greater
than the ratio of the broadcast packets to the
total packets when the broadcast storm does
not occur. Generally, set this parameter to
30% or a greater value.

Loop Detection Disabled, Enabled Disabled Sets whether to enable loop detection, which
is used to check whether a loop exists at the
port.
Loop Port Shutdown Disabled, Enabled Enabled Sets whether to enable the loop port
shutdown function. After the loop port
shutdown function is enabled, the port is
automatically shut down when a self-loop is
detected. It is recommended that this
parameter adopts the default value.

Frame
Tag aware Access Hybrida
and VLAN and VLAN
Priority Priority
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.

NOTE
a: When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by the IDU 605
1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same as the packet that enters
the bridge.
14.3.7.2 Modifying the Type Field of Jumbo Frames

Prerequisite
Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.
Procedure
Management > Jumbo Frame from the Function Tree.
Step 2 Modify the type field of Jumbo frames.
Step 3 Click Apply.
----End
Parameters
Jumbo Frame 00 00 to FF FF 88 70 This parameter specifies the type

field of Jumbo frames. Set this
parameter according to the type
field of the accessed Jumbo frames.
14.4 Configuring Encapsulation and Mapping of Ethernet

Services
To transparently transmit Ethernet frames through the optical transmission network and the radio
transmission network, it is necessary to encapsulate the Ethernet frames and map them into VC
containers at the access point.


When an NE transmits Ethernet services to a microwave transmission network through an
internal port (namely, VCTRUNK) of an Ethernet service board, you need to set the attributes
of the internal port so that the Ethernet service board of the local NE can work with the Ethernet
service board of the NE at the opposite end to realize the transmission of the Ethernet services
on the microwave transmission network.
Ethernet service encapsulation and mapping feature.
14.4.3 Availability
The Ethernet encapsulation and mapping feature requires the support of the applicable equipment
and boards.
The Ethernet service encapsulation, virtual concatenation, and LCAS technology do not have
any impact on other features.
This topic describes the realization of the encapsulation and mapping protocols of the Ethernet
service, the relevant virtual concatenation, and the LCAS technology.
Before you plan the Ethernet encapsulation and mapping features, obtain the information of the
opposite equipment.
14.4.7 Configuring Guide

When an NE transmits Ethernet services to a microwave transmission network through an
internal port (namely, VCTRUNK) of an Ethernet service board, you need to set the attributes
of the internal port so that the Ethernet service board of the local NE can work with the Ethernet
service board of the NE at the opposite end to realize the transmission of the Ethernet services
on the microwave transmission network.
The internal port of the Ethernet service board is the internal VCTRUNK interface and is also
called the system-side interface in certain scenarios. The services are encapsulated and mapped
at the internal port and are transmitted to the microwave transmission network, as shown in
Figure 14-61.
Figure 14-61 Internal port of the Ethernet service board

External port VCTRUNK port
Backplane
Cross-
Interface Service Encapsulation/ Interface connect unit
module processing Mapping conversion
module module module Cross-
connect unit
Ethernet board

The features relevant to the external port of the Ethernet service board include the encapsulation
and mapping protocol, virtual concatenation, and LCAS.
Encapsulation and Mapping Protocols

The Ethernet services are a type of packet services. The SDH optical transmission network and
SDH/PDH microwave, however, realize transmission of data based on time division
multiplexing. Hence, the Ethernet services can be transmitted on the transmission network only
after transmission tunnels are established by using the encapsulation and mapping protocols.
Virtual Concatenation
if you directly map the Ethernet service data into a standard VC container, the transmission
bandwidth is wasted to a great extent. To solve the problem, use the virtual concatenation
technology to concatenate many standard VC containers to a large VC container that adapts to
the rate of the Ethernet service.
LCAS
The LCAS is applied on the basis of virtual concatenation and can improve the performance of
virtual concatenation. The LCAS can dynamically adjust the number of virtual containers for
mapping required services to meet the bandwidth requirements of the application. As a result,
the bandwidth utilization is improved.

Ethernet service encapsulation and mapping feature.
14.4.2.1 Encapsulation and Mapping Protocols

Ethernet service is a type of packet switching service but SDH optical transmission and SDH/
PDH microwave transmission are both based on the TDMA. Therefore, tunnels must be set up
for the transmission of the Ethernet service on the transmission network.
if you directly map the Ethernet service data into a standard VC container, a large amount of
transmission bandwidth is wasted. To solve this problem, use the virtual concatenation
14.4.2.3 LCAS
The link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenation
and can improve the performance of virtual concatenation. The LCAS can dynamically adjust
the number of virtual containers for mapping the required services, to meet the bandwidth
requirements of the application. As a result, the bandwidth utilization ratio is improved.
14.4.2.1 Encapsulation and Mapping Protocols

Ethernet service is a type of packet switching service but SDH optical transmission and SDH/
PDH microwave transmission are both based on the TDMA. Therefore, tunnels must be set up
for the transmission of the Ethernet service on the transmission network.

HDLC
The HDLC is a general data link control procedure. When using the HDLC protocol, the system
encapsulates data services into HDLC-like frames as information bits and maps the frames to
SDH VC containers.
LAPS
The LAPS is also a data link control procedure. It is developed based the HDLC. The LAPS
complies with ITU-T X.86.
GFP
The GFP is the most widely applied general encapsulation and mapping protocol currently. It
provides a general mechanism to adapt higher-layer client signal flows into the transport network
and can map the variable-length payload into the byte-synchronized transport path. Client signals
can be protocol data units (PDU-oriented, such as IP/PPP and Ethernet), block-code data (block-
code-oriented, such as FC and ESCON), or common bit streams. The GPF protocol complies
with ITU-T G.7041.
The GFP defines the following two modes to adapt to client signals:
l Frame-mapping GFP (GFP-F)

The GFP-F is a PDU-oriented processing mode. It encapsulates the entire PDU into the
GFP payload area and does not modify the encapsulated data. According to requirements,
it determines whether to add a detection area for the payload area.
l Transparent GFP (GFP-T)
The GFP-T is a block-code (8B/10B code block) oriented processing mode. It extracts a
single character from the received data block and maps the character into the fixed-length
GFP frame.
All Ethernet boards of the OptiX RTN 600 use the GFP-F mode to perform encapsulation and
mapping.

if you directly map the Ethernet service data into a standard VC container, a large amount of
transmission bandwidth is wasted. To solve this problem, use the virtual concatenation
The concatenation is defined in ITU-T G.707. There are two concatenation methods: contiguous
concatenation and virtual concatenation. Both methods provide concatenated bandwidth of X
times Container-N at the path termination.
Contiguous concatenation concatenates the contiguous C-4s in the same STM-N into an entire
structure to be transported. It maintains the contiguous bandwidth throughout the whole
transport. Virtual concatenation concatenates many individual VC containers (VC-12
containers, VC-3 containers, or VC-4 containers) into a bit virtual structure to be transported.
The virtual concatenation breaks the contiguous bandwidth into individual VCs, transports the
individual VCs, and recombines these VCs to a contiguous bandwidth at the end point of the
transmission.

In the case of the virtual concatenation, each VC container may be transported in different paths
and there may be a transport delay difference between VC containers. Hence, there are
difficulties in restoring the client signal. Virtual concatenation only requires that the path
termination equipment provides the concatenation function and it can allocate bandwidth
flexibly. Hence, virtual concatenation is a widely applied concatenation technology.
Virtual concatenation is available in two types, virtual concatenation in a higher order path and
virtual concatenation in a lower order path. A higher order virtual concatenation VC-4-Xv
provides a payload area of X Container-4 (VC-4). The payload is mapped individually into X
independent VC-4s. Each VC-4 has its own POH. Similarly, a lower order virtual concatenation
VC-12-Xv provides a payload area of X Container-12 (VC-12). The payload is mapped
individually into X independent VC-12s. Each VC-12 has its own POH, as does the virtual
concatenation of VC-3s.
Physical channels formed by virtual concatenation are called VCTRUNKs and are also called
internal ports of the Ethernet board. The Ethernet board does not support VC-4-Xv.
14.4.2.3 LCAS
The link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenation
and can improve the performance of virtual concatenation. The LCAS can dynamically adjust
the number of virtual containers for mapping the required services, to meet the bandwidth
requirements of the application. As a result, the bandwidth utilization ratio is improved.
The LCAS technology has the following advantages:
l The LCAS can dynamically adjust (add, delete, or modify) the service bandwidth without
affecting the availability of the existing service.
l If there are failed physical channels in virtual concatenation, the LCAS shields these
physical channels. Other physical channels in virtual concatenation can transfer services.
Hence, this prevents a situation where the failure of a single physical channel causes
interruption of services. After the failed physical channels are restored, they can transfer
services.
14.4.3 Availability
The Ethernet encapsulation and mapping feature requires the support of the applicable equipment
and boards.
Table 14-48 Availability of the Ethernet encapsulation and mapping feature
Mapping protocol (GFP, EFT4 IDU 610/620

HDLC, and LAPS)
EMS6 IDU 620
Virtual concatenation EFT4 IDU 610/620
EMS6 IDU 620
LCAS EFT4 IDU 610/620
EMS6 IDU 620
EFP6


The Ethernet service encapsulation, virtual concatenation, and LCAS technology do not have
any impact on other features.

This topic describes the realization of the encapsulation and mapping protocols of the Ethernet
service, the relevant virtual concatenation, and the LCAS technology.
14.4.5.1 Encapsulation and Mapping
The HDLC/LAPS/GFP protocol encapsulates and maps Ethernet frames as PDUs.
The virtual concatenation is realized by using byte H4 or K4 as the virtual concatenation-specific
multiframe indicator and sequence indicator.
14.4.5.3 LCAS
The LCAS realizes the capacity adjustment of the virtual container by exchanging the control
information between both the source and the sink side.
14.4.5.1 Encapsulation and Mapping

The HDLC/LAPS/GFP protocol encapsulates and maps Ethernet frames as PDUs.
Among the HDLC, LAPS, and GFP protocols, the GFP protocol is most widely applied. Hence,
this topic takes the GFP protocol as an example to describe how Ethernet frames are encapsulated
and mapped.

Structure of the GFP Frame
Figure 14-62 Structure of the GFP frame

Octet transmission order
1
2
Core header 4
3
4
5
Payload area 4-65535
1 2 3 4 5 6 7 8 Octet transmission order

a) Frame size and transmission order
16-bit payload
length indicator
c-HEC
(CRC-16)
Core header
Payload
headers
(4-64 bytes)
Payload area
Client
payload
information
field
Optional
payload FCS
(CRC-32)
b) Field constituting a GFP client frame
A GFP frame consists of a core header and a payload area. The Idle frame does not have the
payload area.
The GFP core header includes the following fields:

l Payload length indicator (PLI)

The PLI field represents the number of octets in the GFP payload area. The minimum value
of the PLI field in a GFP client frame is 4 octets. PLI values 0 to 3 are reserved for GFP
control frame usage.
l Core HEC (cHEC)
The cHEC field protects the integrity of the contents of the core header by enabling both
single-bit error correction and multi-bit error detection.
The GFP payload area includes the payload header, client payload information field, and payload
frame check sequence. The payload header consists of the type, type HEC (tHEC), extension
header field, and extension HEC (eHEC). The type field includes the following:
l Payload type identifier (PTI)
The PTI identifies the type of GFP client frame. Two kinds of client frames are currently
defined, user data frames (PTI = 000) and client management frames (PTI = 100).
l Payload FCS indicator (PFI)
The PFI indicates the presence (PFI = 1) or absence (PFI = 0) of the payload FCS field.
l Extension header identifier (EXI)
The EXI indicates the presence or absence of the extension header. When EXI = 0, there
is no extension header. This frame format applies to a logical point-to-point configuration.
l User payload identifier (UPI)
The UPI identifies the type of the client frame.
Figure 14-63 GFP type field format

Octet transmission order
15 14 13 12 11 10 9 8 Bit number
5 PTI PFI EXI

6 UPI
7 6 5 4 3 2 1 0 Bit number
1 2 3 4 5 6 7 8 Octet transmission order
The tHEC field protects the integrity of the type field by enabling both single-bit error correction
and multi-bit error detection.
The extension header field and eHEC field are used to support special data link header
technologies and are seldom used in actual situations.
Type of the GFP Frame

There are two types of GFP frame: GFP control frame and GFP client frame.
Currently, the GFP control frame is available only in one type: the Idle frame. The Idle frame
is a four-octet GFP control frame consisting of only a GFP core header. The Idle frame is intended
for the GFP source adaptation process to facilitate the adaptation of the GFP octet stream to any
given transport medium where the transport medium channel has a high capacity.
Two types of GFP client frames are currently defined: client data frame and client management
frame. GFP client data frames are used to transport data from the client signal. GFP client

management frames are used to transport information associated with the management of the
client signal or GFP connection. The type field of the client data frames uses the following
values:
l PTI = 100
l PFI = Payload specific
l EXI = Payload specific
l UPI = See Table 14-49.
Table 14-49 UPI values of the client management frame

UPI Value Usage
0000 0000 Reserved

1111 1111
0000 0001 Client signal fail (loss of client signal)
0000 0010 Client signal fail (loss of character

synchronization)
0000 0011 Reserved for future use

through
1111 11110
Ethernet Frame Encapsulation

The Ethernet board adopts the GFP-F adaptation mode to encapsulate Ethernet frames into the
corresponding virtual container.
The encapsulation process is as follows:
1. The Ethernet MAC octets from the destination address through the frame check sequence,
inclusive, are placed in the GFP payload information field. Octet-alignment is maintained
and bit identification within octets is maintained.
Ethernet MAC frame GFP frame
Octets
2 PLI
2 cHEC
Octets 2 Type
7 Preamble 2 tHEC
1 Start of frame delimiter 0-60 GFP extension header
6 Destination Address (DA)
6 Source Address (SA)
2 Length/Type GFP
MAC client data payload
Pad
4 Frame Check Sequence (FCS)
1 2 3 4 5 6 7 8 Bits 1 2 3 4 5 6 7 8 Bits
2. Calculate other fields of the GFP client data frame over the content of the payload.
3. Scramble the core header and the payload area to maintain DC balance of the transported
data.

4. Map GFP client data frames into virtual containers and insert the Idle frame to realize the
rate adaptation between the variable-length PDUs and the defined virtual containers.
The decapsulation process is as follows:
1. Check for a correct cHEC, byte by byte in the payload of the virtual container. Once a
correct cHEC is detected, a GFP frame is found.
2. Check for subsequent GFP frames frame by frame according to the PLI in the GFP frame
and discard Idle frames.
3. Descramble the payload area in the found GFP frame and extract the Ethernet MAC octets
from the destination address through the frame check sequence, inclusive.

The virtual concatenation is realized by using byte H4 or K4 as the virtual concatenation-specific
multiframe indicator and sequence indicator.
VC-4-Xv and VC-3-Xv

The virtual container that is formed by a VC-4-Xv/VC-3-Xv can be mapped into X individual
VC-4/VC-3s which form the VC-4-Xv/VC-3-Xv. Each VC-4/VC-3 has its own POH. The POH
has the same specifications as the ordinary VC-4 POH. The H4 byte in the POH is used for the
virtual concatenation-specific multiframe indicator (MFI) and sequence indicator (SQ).
The MFI indicates the position of a frame in the multiframe. Each frame sent by the source
carries the MFI information. The sink combines the frames with the same MFI into the C-n-Xv.
There are MFI-1 and MFI-2. The MFI-1 uses H4, bit 5 to bit 8 and counts from 0 to 15. The
MFI-2 uses H4, bit 1 to bit 4 in frame 0 (MFI-2 bits 1-4) and 1 (MFI-2 bits 5-8). Hence, the
MFI-2 counts from 0 to 255. The resulting overall multiframe is 4096 frames (= 512 ms) long.
The SQ indicates the position of a frame in the C-n-Xv. The source inserts the SQ information
into the frame according to the payload allocation sequence. The sink decides the sequence to
extract the payload from the frames that form C-n-Xv according to the SQ. The SQ is transported
in bits 1 to 4 of the H4 bytes, using frame 14 (SQ bits 1-4) and 15 (SQ bits 5-8) of MFI-1.

Figure 14-64 VC-3-Xv/VC-4-Xv multiframe and sequence indicator

C-3-X/C-4-X C-3-Xv/C-4-Xv
SQ = X-1
H
1 X SQ = 0 =0
POH
MFI-1 = 0 =0
MFI-2 = 0 X-1
SQ = 0 =1
POH
MFI-1 = 1 =0
MFI-2 = 0
Multiframe (MF)
SQ = X-1
H
SQ = 0 = 15
POH
MFI-1 = 15 = 0
MFI-2 = 0 X-1
SQ = 0 =0
POH MFI-1 = 0 = 15
MFI-2 = 1
H SQ = X-1
SQ = 0 = 15
POH
MFI-1 = 15 = 255
MFI-2 = 255 X-1
SQ = 0 =0
POH
MFI-1 = 0 =0
MFI-2 = 0
With the MFI and SQ, the sink can correctly restore the position of each frame in the C-n-Xv to
avoid the frame alignment problem due to the different propagation delays of the frames.
VC-12-Xv
The virtual container that is formed by a VC-12-Xv can be mapped into X individual VC-12s
which form the VC-12-Xv. Each VC-12 has its own POH. The POH has the same specifications
as the ordinary VC-12 POH. Bit 2 of the K4 byte in the POH is used for the virtual concatenation-
specific frame count and sequence indicator.
Bit 2s of the K4 bytes in every 32 multiframes (one multiframe comprising four VC-12s) are
extracted to form a 32-bit character string to express the frame count and sequence indicator.
Bits 1-5 of the string express the frame count, whose value range is between 0 and 31. The
structure formed by 32 multiframes has 128 frames. Hence, the resulting overall multiframe is
1096 frames (= 512 ms) long. Bits 6-11 of the string express the sequence indicator. The frame
count/sequence indicator in the VC-12-Xv has the same usage as the multiframe indicator/
sequence indicator in the VC-4-Xv/VC-3-Xv.
14.4.5.3 LCAS
The LCAS realizes the capacity adjustment of the virtual container by exchanging the control
information between both the source and the sink side.
Control Information
Synchronization of changes in the capacity of the transmitter (So) and the receiver (Sk) is
achieved by a control packet. Each control packet describes the state of the link during the next

control packet. Changes are sent in advance so that the receiver can switch to the new
configuration as soon as it arrives.
The control packet is transported in byte H4 (higher order path) or bit 2 of byte K4 (lower order
path).
The control packet includes the following:
l MFI or frame count

MFI is used for the VC-4-Xv/VC-3-Xv and the frame count is used for the VC-12-Xv. Both
are used to indicate the position of a multiframe. For the usage, see 14.4.5.2 Virtual
Concatenation.
l SQ
SQ is used to indicate the position of a frame in the C-n-Xv. For the usage, see 14.4.5.2
Virtual Concatenation.
l GID
The GID is used for identification of the VCG. The GID bit of all members of the same
VCG has the same value. The VCG refers to a group of co-located member trail termination
functions that are connected to the same virtual concatenation link. The members of a VCG
are the virtual containers that form the VCG. The VCG is equivalent to the generally spoken
VCTRUNK.
l Control field (CTRL)
The control field is used to transfer the link information from the source to the sink. It must
provide the status of the individual member of the link.
Table 14-50 LCAS CTRL words
Command Remarks
FIXED This is an indication that this end uses fixed

bandwidth (non-LCAS mode).
ADD This member is about to be added to the

group.
NORM Normal transmission
EOS End of sequence indication and normal

transmission
IDLE This member is not part of the group or

about to be removed.
DNU Do not use (the payload). The sink side

reported FAIL status.
l CRC
The CRC check is performed on every control packet after it has been received, and the
contents rejected if the test fails.
l Member status field (MST)
It reports the member status from the sink to the source. There are two states, OK and FAIL.

l Re-sequence acknowledge (RS-Ack) bit

When a change of the status of the members in a VCG is detected at the sink side, a
notification to the source has to be performed by toggling (that is, change from '0' to '1' or
from '1' to '0') the RS-Ack bit.
The forward control packets from the source to the sink include the MFI, SQ, GID, CTRL, and
CRC. The backward control packets from the sink to the source include the MST, RS-Ack, and
CRC.
Capacity Adjustment Process
Figure 14-65 Capacity adjustment process (addition of a member)

Source (EOS) Source (new) Sink (new) Source (EOS)
Ctrl=ADD
MST=OK
Ctrl=EOS
RS-Ack
Ctrl=NORM
When a member is added to a VCTRUNK on the NMS, the LCAS capacity adjustment process
is as follows:
1. The LCAS source assigns a sequence number (one larger than the currently highest
sequence number) to the new member and sends a forward control packet with its CTRL
word being ADD to the sink.
2. The LCAS sink performs continuity check for the new member. If the link of the new
member is normal, the sink sends a backward control packet in which MST = OK to the
source.
3. The LCAS source sends a forward control packet with its CTRL code being EOS to the
sink for the new member, indicating that the SQ of the new member is the currently highest
number in the VCG.
4. The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ.
5. The LCAS source sends a forward control packet with its CTRL code being NORM to the
sink for the member whose original state is EOS, indicating that the member is normally
transmitted but is not the one with the highest SQ.
6. Both the source and the sink use the new member to transport the payload.

Figure 14-66 Capacity adjustment process (deletion of a member)

Source(SQ>removed Sink(SQ>removed
member's SQ) Source(removed) Sink(removed) member's SQ)
Ctrl=IDLE
MST=FAIL
RS-Ack
Ctrl=EOS/NORM
RS-Ack
When a member is deleted from a VCTRUNK on the NMS, the LCAS capacity adjustment
process is as follows:
1. The LCAS source sends a forward control packet with its CTRL code being IDLE to the
sink for the deleted member.
2. The LCAS sink sets the status of the member to FAIL and sends a backward control packet
in which MST = FAIL to the source and also sends the RS-Ack to acknowledge the change
of the SQ.
3. The LCAS source reallocates SQs for all the members whose SQ is higher than that of the
deleted member (SQ decremented successively by 1). It also sends a forward control packet
with its CTRL code being EOS or NORM to the sink to indicate the change of the SQ.
4. The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ.
5. Both the source and the sink do not use the deleted member to transport the payload.
Figure 14-67 Capacity adjustment process (one member link restored after a failure)
Source (link error) Sink
MST=FAIL
Ctrl=DNU
...
MST=OK
Ctrl=NORM
When a member link of a VCTRUNK is restored after a failure, the process of adjusting the
LCAS capacity is as follows:
1. On detecting that a member link is faulty, the LCAS sink sends a backward control packet
in which MST = FAIL to the source.
2. The LCAS source sends a forward control packet with its CTRL code being DNU to the
sink for the member, indicating that the member is temporarily unavailable.
3. If the original status of the member is EOS, the LCAS source sends a forward control packet
with its CTRL word being EOS to the sink for the member whose SQ is one lower than
EOS.
4. Both the source and the sink do not use the faulty link member to transport the payload.

5. On detecting that the member link is restored, the LCAS sink sends a backward control
packet in which MST = OK to the source.
6. The LCAS source sends a forward control packet with its CTRL code being NORM or
EOS to the sink for the member, indicating that the member is restored and available.
7. If the original status of the member is EOS, the LCAS source sends a forward control packet
with its CTRL word being NORM to the sink for the member whose status is set to EOS.
8. Both the source and the sink use the restored member to transport the payload.
NOTE
l The LCAS source can adopt the Huawei mode or the standard mode to send the two control packets MST
and Rs-Ack. In the Huawei mode, the Rs-Ack is sent before the MST. In the standard mode, the MST is
sent before the Rs-Ack. You can set the mode on the NMS.
l The LCAS sink uses the trail signal fail (TSF) or the loss of multiframe (LOM) as a required condition to
determine whether a link is faulty. It uses the trail signal degraded (TSD) as an optional condition. In the
case of the VC-12, the TSD is the BIP_SD. In the case of the VC-3, the TSD is the B3_SD_VC3. You can
enable or disable the TSD on the NMS.
l When a member link is faulty, the LCAS performs a protection switching after a delay of time to prevent
the situation where an NE simultaneously performs a protection switching such as SNCP and deletes the
member. You can set the delay time on the NMS.
l A VCG uses a member to transport payload some time after the member link is restored. You can set the
WTR time on the NMS.

Before you plan the Ethernet encapsulation and mapping features, obtain the information of the
opposite equipment.
Procedure
Step 1 Plan the Ethernet encapsulation and mapping protocol.
Adhere to the following principles when planning the encapsulation and mapping of the Ethernet
port:
l Plan the same encapsulation and mapping protocol for both sides. It is recommended that
you adopt the GFP protocol.
l The parameters of the encapsulation and mapping protocol at both sides should be consistent.
It is recommended that you adopt the default parameters of the protocol.
Step 2 Plan VCTRUNKs.
Adhere to the following principles when planning VCTRUNKs:
l The capacity of VCTRUNKs should be determined by the actual bandwidth of the service
needs.
l Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound,
the VC-4s that have the same transmission path take priority.
l As each VC-4 of the Ethernet board can bind only VC-3 or VC-12, give priority to the VC-4s
whose paths are already bound with the VC-12 or VC-3.
l As the VC-4-1 of the EFT4 board and EMS6 board can bind only VC-3 paths whereas the
VC-4-2 can bind both VC-12 and VC-3 paths, give priority to the paths in the VC-4-1 if
VC-3 paths are to be bound.

Step 3 Plan the LCAS.

Adhere to the following principles when planning the LCAS:
l The LCAS at both sides must be enabled or disabled.
l If the LCAS is enabled at both sides, the used LCAS parameters at both sides must be
consistent.
l If the opposite equipment is the third-party equipment and does not support the Huawei mode,
set the LCAS mode to the standard mode. Otherwise, set the mode to the Huawei mode at
both sides.
l It is recommended that you set the delay time to 2000 ms.
l It is recommended that you set the WTR time to 300 seconds.
l It is recommended that you disable the TSD.
----End
14.4.7 Configuring Guide
14.4.7.1 Configuring the Internal Port of the Ethernet Board

14.4.7.2 Configuring LCAS
After you enable LCAS, an NE dynamically adjusts service bandwidth without affecting the
usability of services.
14.4.7.1 Configuring the Internal Port of the Ethernet Board

Prerequisite
Precautions
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
l The EFT4 board supports VCTRUNKs 1-4, which are bound with PORTs 1-4 respectively.
The EFT4 board does not support the setting of TAG attributes and network attributes.
l The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be
transmitted depending on information of the created Ethernet services.
The following procedures describe how to configure the internal port of an EMS6 board. The
EFT4 board does not support the configuration of the TAG attributes and network attributes.

Procedure
Management > Ethernet Interface from the Function Tree. Choose Internal Port.
Step 2 Set the encapsulation and mapping protocol used by the port.
1. Click the Encapsulation/Mapping tab.
2. Set Mapping Protocol and the protocol parameters.
3. Click Apply.
Step 3 Set the VC paths to be bound with the port.
1. Click the Bound Path tab.
3. In Configurable Ports, select a VCTRUNK as the port to be configured.
6. Optional: Repeat Step 3.5 and bind other VCTRUNKs.
7. Click OK. Then, click Yes in the dialog box that is displayed.
Step 4 Configure the LCAS function for the port.

1. Click the LCAS tab.
2. Set the Enabling LCAS parameter and other LCAS parameters.

3. Click Apply.
3. Click Apply.
3. Click Apply.
----End
Parameters
Mapping Protocol GFP, LAPS, HDLC GFP It is recommended that you use the default
value.
Scramble Unscrambled, Scrambling Mode l This parameter specifies the scrambling

Scrambling Mode [X43+1] polynomial used by the mapping
[X43+1], protocol.
Scrambling Mode l It is recommended that you use the
[X48+1] default value.

Set Inverse Value Yes, No Yes l This parameter is valid only when
for CRC Mapping Protocol is set to LAPS or
HDLC.
l When this parameter is set to Yes, the
FCS is the result after you perform a
negation operation for the CRC.
l When this parameter is set to No, the
FCS is the CRC.
Check Field Length FCS32, FCS16, No FCS32 l When this parameter is set to FCS32, a
32-bit FCS is used.
l When this parameter is set to FCS16, a
16-bit FCS is used.
l When the Ethernet board uses the GFP
set to FCS32, FCS16, or No.
l When the Ethernet board uses the HDLC
l When the Ethernet board uses the LAPS
default value.
FCS Calculated Bit Big endian, Little l Big endian l When this parameter is set to Big
Sequence endian (GFP) endian, the least significant byte of the
l Little endian FCS is placed first and the most
(LAPS or significant byte is placed last.
HDLC) l When this parameter is set to Little
endian, the most significant byte of the
FCS is placed first and the least
significant byte is placed last.
default value.
Extension Header No, Yes No l This parameter specifies whether the

Option GFP payload header contains the
extension header and eHEC.
default value.



path take priority.
paths.
Enabling LCAS Enabled, Disabled Disabled l This parameter specifies whether the
LCAS function is enabled.
number of virtual containers for
mapping required services to meet the
bandwidth requirements of the
application. As a result, the bandwidth
utilization ratio is improved.

LCAS Mode Huawei Mode, Huawei Mode l This parameter specifies the sequence in
Standard Mode which the LCAS sink sends the MST
control packet and Rs-Ack control
packet.
l When this parameter is set to Huawei
Mode, the LCAS sink first sends the Rs-
Ack and then sends the MST.
l When this parameter is set to Standard
Mode, the LCAS sink first sends the
MST and then sends the Rs-Ack.
l If the equipment on the opposite side is
the third-party equipment and does not
support the Huawei mode, it is
to Standard Mode. Otherwise, set this
parameter to Huawei Mode.
Hold Off Time (ms) 0, any integer that 2000 l When a member link is faulty, the LCAS
ranges from 2000 to performs switching after a delay of time
10000 and has a step to prevent the situation where an NE
of 100 simultaneously performs a protection
switching such as SNCP and performs an
LCAS switching. This parameter
specifies the duration of the delay.
l If the paths of the VCTRUNK are
configured with protection, it is
to 2000 ms. Otherwise, set this
parameter to 0.
WTR Time(s) 0 to 720 300 l When the time after a member link is
restored to normal reaches the set value
of this parameter, the VCG uses the
restored member link.
default value.
TSD Enabled, Disabled Disabled l This parameter specifies whether the

TSD is used as a condition for
determining whether a member link is
faulty. In the case of the VC-12, the TSD
refers to the BIP_SD. In the case of the
VC-3, the TSD refers to the
B3_SD_VC3.
default value.


situations.

14-51.
situations.

14-51.
value.

the tag attributes.
services.
created.

NOTE
l The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must
be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the
transmission line.
l The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line
must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other
end of the transmission line.
l The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a
transmission line.

Frame
and VLAN and VLAN
Priority Priority


Frame
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.
14.4.7.2 Configuring LCAS

After you enable LCAS, an NE dynamically adjusts service bandwidth without affecting the
usability of services.
Prerequisite
Context
l The configuration that complies with the LCAS protocol should meet the following two
requirements:
The configured services should be bidirectional services that adopt virtual
concatenation.
The networking topology should be of the point-to-point mode.
l When configuring the LCAS function, you must set the LCAS parameters to the same
values for the equipment at the two ends.
The LCAS enable/disable attribute of the equipment at the two ends must be the same.
The equipment at the two ends must be set to the same LCAS mode.
Procedure
Step 1 Select an NE in the NE explore, choose Configuration > Cross-Connection Configuration
from the Function tree.
Step 2 Click the Create button below the right-side pane, configure the SDH services between the
Ethernet board and the line board according to the requirement.

Step 3 Click OK.

Step 4 Repeat Steps 1 to 3 to configure the SDH services between the Ethernet board and the line board
on the sink NE.
Step 5 In the Board Tree, select the Ethernet board to be configured with services. In the Function Tree,
choose Configuration > Ethernet Interface Management > Ethernet Interface.
Step 6 Select Internal Port, and the internal port configuration interface is displayed.
Step 7 In the Internal Port page, select the Bound Path tab.
Step 8 Click Configuration, and the bound path configuration dialog box is displayed.
Step 9 Based on the service requirement, set each parameter of the bound path one by one.
Step 10 Click OK.
Step 11 Select the LCAS tab, and the LCAS configuration interface is displayed.
Step 12 Set the LCAS parameters. .
Step 13 Click Apply. The Operation Result dialog box is displayed, showing that the operation
succeeded.
NOTE
The class of bound path configured for the Ethernet board on the source NE must be the same as that on
the sink NE. Otherwise, the LCAS function fails to be configured.
----End
14.5 Configuring VLAN

The Ethernet switching processing board supports the virtual local area network (VLAN)
function that complies with IEEE 802.1q.

According to specific rules, a real network topology can be divided into several logical subnets,
which are referred to as VLANs. The broadcast packets of a VLAN can be transmitted only
within this VLAN. That is, one VLAN corresponds to a specific broadcast domain. The VLAN
allows users to solve the broadcast flooding problem at low costs. In addition, the VLAN offers
several revolutionary benefits.


This topic decribes the basic concepts that you need to be familiar with before you use the VLAN
feature.
14.5.3 Availability
The VLAN feature requires the support of the applicable equipment and boards.
The port whose VLAN feature is enabled cannot transparently transmit Ethernet services.
Realization of the VLAN function is related to the port attribute and service type.
Plan related parameters according to the specific application of VLAN.
EVPL service that uses the VLAN feature. Two examples are provided as a supplement to the
configuration.
14.5.8 Configuration Example (PORT-Shared EVPL Service)
This topic provides an example to describe how to configure the PORT-shared EVPL service
14.5.9 Configuration Example (VCTRUNK-Shared EVPL Service)
This topic provides an example to describe how to configure the VCTRUNK-shared EVPL
service.

According to specific rules, a real network topology can be divided into several logical subnets,
which are referred to as VLANs. The broadcast packets of a VLAN can be transmitted only
within this VLAN. That is, one VLAN corresponds to a specific broadcast domain. The VLAN
allows users to solve the broadcast flooding problem at low costs. In addition, the VLAN offers
several revolutionary benefits.
Improving Bandwidth Utilization

The generation of a large number of unnecessary broadcast packets is avoided because the
broadcast packets are forwarded within the range of a specific VLAN rather than on the entire
LAN. This improves the bandwidth utilization. In addition, because a VLAN is actually a small
broadcast domain, if the routing of a packet is not discovered, the switch transmits this packet
only to the ports that belong to this VLAN rather than to all ports of the switch. Hence, the packet
forwarding is restricted to a specific VLAN, which also improves the network utilization.
Isolating Users and Improving Network Security

The packets of a VLAN are forwarded within the range of this VLAN, but not forwarded to the
network equipment of other VLAN users. Hence, using VLANs can isolate different users and
can protect the privacy of user information.
Realizing Virtual Workgroups

The final goal of using VLANs is to establish the virtual workgroup model, that is, to establish
a dynamic organization environment. This enables the members of the same VLAN to
communicate with each other as if they were in the same VLAN, even when they move to other

positions of the network. The broadcast packets are restricted to this VLAN without affecting
the members of other VLANs. If the network location of one member is changed but the VLAN
to which the member belongs is not changed, the configuration of this member can remain
unchanged. If the physical location of one member is not changed but the VLAN to which the
member belongs is changed, the network administrator needs to modify the configuration of this
member.
The virtual workgroup is a long-term goal, which requires support in other aspects.

This topic decribes the basic concepts that you need to be familiar with before you use the VLAN
feature.

To realize the VLAN function, IEEE 802.1q defines the Ethernet frame that contains the VLAN
information, namely, the tagged frame. The tagged frame is also called the 802.1q frame.
Compared with the common Ethernet frame, this type of frame is added with a 4-byte 802.1q
header.
14.5.2.2 TAG Attribute
Depending on the different methods for processing the tagged frame and the untagged frame,
the TAG attribute of a switch port can be set to tag aware, access, and hybrid.
14.5.2.3 Application
A VLAN allows new application scenarios for the Ethernet private line (EPL) service and the
Ethernet private LAN (EPLAN) service.

To realize the VLAN function, IEEE 802.1q defines the Ethernet frame that contains the VLAN
information, namely, the tagged frame. The tagged frame is also called the 802.1q frame.
Compared with the common Ethernet frame, this type of frame is added with a 4-byte 802.1q
header.
Figure 14-68 Tagged frame format

4 bytes
Destination Source 802.1q FCS
Length/Type Data
address address header (CRC-32)
TCI
TPID PCP CFI VID
The 4-byte 802.1q header is divided into two parts: tag protocol identifier (TPID) and tag control
information (TCI). The TCI is divided into three parts: user_priority, canonical format indicator
(CFI), and VLAN identifier (VID).

l TPID
The TPID is a 2-byte field, and it identifies an Ethernet frame as a tagged frame. The value
is always 0x8100. When the network equipment that cannot identify the tagged frame
receives the tagged frame, the equipment discards this frame.
l PCP
The priority code point (PCP) identifies the priority of an Ethernet frame. This field can be
used to provide the requirement for the service quality.
l CFI
The CFI is a 1-bit filed, and it is used in certain physical networks that adopt the ring
topology. This field is not processed in the Ethernet.
l VID
The VLAN ID is a 12-bit field, and it indicates the VLAN that the frame belongs to.
Restricted to the field length, the value of the VID ranges from 1 to 4095.
14.5.2.2 TAG Attribute

Depending on the different methods for processing the tagged frame and the untagged frame,
the TAG attribute of a switch port can be set to tag aware, access, and hybrid.
Table 14-52 Data frame processing method of the switch port

Direction Type of Frame Processing Method
Tag Aware Access Hybrida
Ingress Tagged frame Receives the Discards the Receives the

Untagged frame Discards the Receives the Receives the

frame. frame after the frame after the
untagged frame untagged frame
is added with the is added with the
port VID PVID.
(PVID).
Egress Tagged frame Transmits the Transmits the Transmits the

frame. frame after the frame after the
PVID of the PVID of the
tagged frame is tagged frame is
stripped. stripped if the
VID equals the
PVID.
Directly
transmits the
frame if the VID
does not equal
the PVID.

NOTE
l The untagged frame cannot be transmitted through the port.

l When the Ethernet switching board works in the Ethernet switching state, it can be considered as an Ethernet
switch. In this case, the ports of the Ethernet switching board can be classified into two categories: the
external port (PORT) and the internal port (VCTRUNK). Each port corresponds to a specific TAG attribute.
l When the Ethernet switching board works in the Ethernet transparent transmission state, it does not check
the TAG attribute. Hence, the port transparently transmits the tagged frame and the untagged frame.
CAUTION
a:When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by
the IDU 605 1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same
as the packet that enters the bridge.
14.5.2.3 Application
A VLAN allows new application scenarios for the Ethernet private line (EPL) service and the
Ethernet private LAN (EPLAN) service.
In the case of the EPL service, after the VLAN is adopted, the Ethernet board can divide the
flow by port and VLAN ID other than only by port, which allows the development of the EPL
service to the Ethernet virtual private line (EVPL) service. In the case of the EPLAN service,
after the VLAN is adopted, the Ethernet board can create the 802.1q bridge, which allows the
development of the EPLAN service to the Ethernet virtual private LAN (EVPLAN) service.
This topic only describes the application of the VLAN in the EPL service. For details about the
802.1q bridge, see 14.6.2.1 Bridge.
PORT-Shared EVPL Service

Figure 14-69 shows an example of the PORT-shared EVPL service. The service between the
headquarters and branch A is transmitted over the VLANs whose VIDs are from 100 to 110,
and the service between the headquarters and branch B is transmitted over the VLANs whose
VIDs are from 200 to 210. If the Ethernet board at NE1 supports VLAN, use an Ethernet port
whose port attribute is tag aware to access the services from the headquarters. Then, map the
services of different VLANs into different VCTRUNKs. In this way, the services of different
VLANs are isolated during transmission.
Figure 14-69 PORT-shared EVPL service

VLAN100-110
VLAN100-110 VCTRUNK1
VLAN200-210
NE2 Branch A
PORT1
VLAN200-210
Headquaters
VCTRUNK2
NE1 NE3 Branch B

VCTRUNK-Shared EVPL Service

Figure 14-70 shows an example of the VCTRUNK-shared EVPL service. Department A and
department B at NE1 need to transmit services to their respective departments at NE2. If the
Ethernet board supports VLAN, use two Ethernet ports at NE1 whose port attributes are access
and that have different PVIDs to access the services of department A and department B at NE1.
Then, map the services into the same VCTRUNK. In this way, the services of different VLANs
are transmitted over the same VCTRUNK. Because the services of the two departments can
share the bandwidth, the bandwidth utilization is improved.
Figure 14-70 VCTRUNK-shared EVPL service
PORT1 VLAN100 VLAN100 PORT1

A A
NE1 VCTRUNK1 NE2
VLAN200 VLAN200
PORT2 PORT2
B B
14.5.3 Availability
The VLAN feature requires the support of the applicable equipment and boards.
Table 14-53 Availability of the VLAN
VLAN EMS6 (all the versions) IDU 620
- IDU 605 1F/2F a
NOTE
a: IDU 605 1F/2F supports the LAN service that is based on the VLAN, but does not support the Ethernet
line service.

The port whose VLAN feature is enabled cannot transparently transmit Ethernet services.

Realization of the VLAN function is related to the port attribute and service type.
When the VLAN function is enabled, the switch processes a data frame as follows:
1. Processes the data frame that is input into the switch through a port, according to the
attribute of this port. For details, see Table 14-52.

2. Forwards this data frame according to the service type.

l In the case of the line service, the switch forwards this data frame to the corresponding
ports based on the service configuration.
l In the case of the VLAN service, the switch forwards this data frame to the
corresponding port based on the MAC address table. For details, see 14.6.5.1 Bridge.
3. Processes the data frame that is output from this port on the switch, according to the attribute
of this port. For details, see Table 14-52.

Plan related parameters according to the specific application of VLAN.
Prerequisite
You must learn about the specific application of VLAN.
Precautions
NOTE
This topic describes the planning based on the cases in 14.5.2.3 Application.
Procedure
Step 1 According to the actual requirements, plan the line service type.
When planning the line service type, adhere to the following principles:
l In the case of the point-to-point service, use the Ethernet transparent transmission service.
l If the service of the same PORT needs to be divided by VLAN and if the service frame is
the tagged frame, use the PORT-shared EVPL service.
l If the services of different PORTs need to share one transmission channel and if the service
frame is the untagged frame, use the VCTRUNK-shared EVPL service.
l In the case of other requirements that are not contained in the preceding description, use the
QinQ service or Layer 2 switching service.
Step 2 Optional: Plan the PORT-shared EVPL service.
When planning the PORT-shared EVPL service, adhere to the following principles:
l Set TAG of the PORT to Tag Aware.
l Allocate the VLAN service of this PORT to different VCTRUNKs by VLAN ID.
Step 3 Optional: Plan the VCTRUNK-shared EVPL service.
When planning the VCTRUNK-shared EVPL service, adhere to the following principles:
l Set TAG of the PORT to Access.
l Because the PVIDs of different PORTs should be different, configure the PVIDs of PORTs
by user. For example, if the PVIDs of the PORTs used by user A range from 100 to 199, the
PVIDs of the PORTs used by user B should range from 200 to 299.
l The services of different PORTs should share one VCTRUNK.
----End


EVPL service that uses the VLAN feature. Two examples are provided as a supplement to the
configuration.
This topic describes the configuration flow of the EVPL service that uses the VLAN feature.

This topic describes the configuration flow of the EVPL service that uses the VLAN feature.
Figure 14-71 Configuration flow of the EPL service that uses the VLAN feature (PORT-shared
or VCTRUNK-shared EVPL service)
Start
1
Configure the
Ethernet external port
2
Configure the
Ethernet internal port
3
Create the
Ethernet line service
4 Create the cross-

connection of the
Ethernet service
End

Table 14-54 Configuration flow of the EVPL service that uses the VLAN feature (PORT-shared
EVPL service)
Number Description
1 l Set the TAG attributes of the PORT as follows:

Set TAG to Tag Aware.
Set Ingress Check to Enabled.
l For the configuration process, see 14.3.7.1 Configuring External
Ethernet Ports.
2 l Configure one VCTRUNK corresponding to each data stream that is from

the service of the PORT.
l Set the TAG attributes of the VCTRUNK as follows:
Set TAG to Tag aware.
l For the configuration process, see 14.4.7.1 Configuring the Internal Port
3 l Configure the EVPL service from the PORT+VLAN to the specified

VCTRUNK.
l For the configuration process, see 14.5.7.2 Creating Ethernet Line
Service.
Table 14-55 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNK-
shared EVPL service)
Number Description
1 l Set the TAG attributes of the PORT as follows:

Set TAG to Access.
Set Default VLAN ID of PORTs to different values.
l For the configuration process, see 14.3.7.1 Configuring External
Ethernet Ports.
2 l Configure a shared VCTRUNK. Set the TAG attributes of the VCTRUNK

as follows:
l Set TAG to Tag aware.
l Set Ingress Check to Enabled.
l For the configuration process, see 14.4.7.1 Configuring the Internal Port

Number Description
3 l Configure the EVPL service from the PORT to the specified VCTRUNK
+VLAN.
l For the configuration process, see 14.5.7.2 Creating Ethernet Line
Service.
NOTE
If the QoS of the EVPL service needs to be set, see 14.7 Configuring QoS.

Prerequisite
The Ethernet switching board must be added in the slot layout.
Precautions
l This topic does not describe the method for creating the QinQ service.
l IDU 620 supports the Ethernet switching board EMS6. The EFT4 board is an Ethernet
transparent transmission board, and the PORTs of the EFT4 board correspond to the
VCTRUNKs. Hence, you do not need to create the Ethernet line service.
Procedure
Step 2 Click New.
The Create Ethernet Line Service dialog box is displayed.

NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the
result of directly setting the Ethernet service port attributes.
Step 5 Optional: Set the bound path.


NOTE
6. Click OK.
Step 6 Click OK.
----End
Parameters
Service Type EPL, EVPL (QinQ) EPL When creating the non-QinQ private line
Direction Unidirectional, Bidirectional l When setting this parameter to

Bidirectional Unidirectional, create the service only
from the service source to the service
sink. That is, the service source is
forwarded only to the sink port.
l When setting this parameter to
Bidirectional, create the service from
the service source to the service sink and
the service from the service sink to the
service source. That is, when the service
source is forwarded to the sink port, the
service sink is forwarded to the source
port.

use a specific PORT as the source port.
Source VLAN (e.g. 1-4095 - l You can set this parameter to null, a
number of VLANs set in Sink C-VLAN
(e.g. 1,3-6).
the service source.
the service source.
use a VCTRUNK as the sink port.

Sink VLAN (e.g. 1-4095 - l You can set this parameter to null, a
VLAN (e.g. 1,3-6).
service sink.
the service sink.
TAG Access, Tag Aware, Tag Aware l When all the accessed services are
Hybrid frames with the VLAN tag (tagged
frames), set this parameter to Tag
Aware.
l When all of the accessed services are not
frames with the VLAN tag (untagged



path take priority.
paths.

14.5.8 Configuration Example (PORT-Shared EVPL Service)

This topic provides an example to describe how to configure the PORT-shared EVPL service
Precautions
NOTE
l For details about the service configured in this example, refer to the description of the PORT-shared EVPL
service in 14.5.2.3 Application.
l Because NE2 and NE3 in this example are both configured with the point-to-point EVPL service, only the
configuration of NE1 is described here.
Procedure
Step 1 Set the port attributes of PORT. See 14.3.7.1 Configuring External Ethernet Ports.

Set TAG attributes of PORT1 as follows:
l Set TAG to Tag Aware.

Step 2 Set the port attributes of VCTRUNK1 and VCTRUNK2. See14.4.7.1 Configuring the Internal
Set the TAG attributes of VCTRUNK1 and VCTRUNK2 as follows:
l Set TAG to Tag Aware.

Step 3 Configure the EVPL service between PORT1 and VCTRUNK1. See14.5.7.2 Creating Ethernet
Line Service.

l Set Source C-VLAN (e.g.1,3-6) to 100-110.
l Set Sink C-VLAN (e.g.1,3-6) to 100-110.
Step 4 Configure the EVPL service between PORT1 and VCTRUNK2. See 14.5.7.2 Creating
Ethernet Line Service.

l Set Source C-VLAN (e.g.1,3-6) to 200-210.
l Set Sink C-VLAN (e.g.1,3-6) to 200-210.
----End
14.5.9 Configuration Example (VCTRUNK-Shared EVPL Service)

This topic provides an example to describe how to configure the VCTRUNK-shared EVPL
service.
Precautions
NOTE
l For details about the service configured in this example, refer to the description of the VCTRUNK-shared
EVPL service in14.5.2.3 Application.
l Because the service configuration of NE1 is the same as the service configuration of NE2 in this example,
only the configuration of NE1 is described here.
Procedure
Step 1 Set the port attributes of PORT1. See 14.3.7.1 Configuring External Ethernet Ports.

Set the TAG attributes of PORT1 as follows:

l Set TAG to Access.
l Set Default VLAN ID to 100.
Step 2 Set the port attributes of PORT2. See 14.3.7.1 Configuring External Ethernet Ports.
Set the TAG attributes of PORT2 as follows:
l Set TAG to Access.
l Set Default VLAN ID to 200.
Line Service.
l Set Source C-VLAN (e.g.1,3-6) to 100.
l Set Sink C-VLAN (e.g.1,3-6) to 100.
Line Service.
l Set Source C-VLAN (e.g.1,3-6) to 200.
l Set Sink C-VLAN (e.g.1,3-6) to 200.
----End
14.6 Configuring Layer 2 Switching

To realize the EPLAN service, the Ethernet switching and processing board can create one bridge
or multiple bridges. Each bridge can realize the Layer 2 switching of packets among mounted
ports and relevant features.
The Layer 2 switching refers to the packet switching among switch ports by using the 802.1d,
802.1q, or 802.1ad algorithm. This topic describes the bridge, and the features relevant to the
Layer 2 switching, such as STP/RSTP, IGMP Snooping, and broadcast packet suppression,
which is the core of the Layer 2 switching.
This topic describes the basic concepts that you need to be familiar with before you use the Layer
2 switching feature.

14.6.3 Availability
The Layer 2 switching feature requires the support of the applicable equipment and boards.
The Layer 2 switching has different relations with other features.
The bridge, STP/RSTP, and IGMP Snooping comply with the relevant IEEE standards.
Plan the relevant parameters of the Layer 2 switching service according to the actual situation
of microwave links.
This topic describes the configuration tasks relevant to the Layer 2 switching feature.
14.6.8 Creating the Ethernet LAN Service
bridge.
14.6.9 Modifying the Mounted Port of a Bridge
This operation enables the user to modify the mounted port of a bridge, the enabled state of the
mounted port, and Hub/Spoke attribute of the port.
14.6.10 Creating the VLAN Filter Table
14.6.11 Creating the Entry of a MAC Address Table Manually
The bridge can obtain the dynamic entry of a MAC address table by using the SVL or IVL mode.
In addition, you can manually add the entry of a MAC address table. The manually created
entries of a MAC address table can be classified into two categories: unicast entry (that is, static
entry) and disabled entry (that is, blacklist entry).
14.6.12 Modifying the Aging Time of the MAC Address Table Entry
In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5
minutes by default.
14.6.13 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry
By querying the actual capacity of the MAC address table and the dynamic entry, you can learn
about the MAC address learning situation of the bridge.
14.6.14 Configuring the Spanning Tree Protocol
In the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridge
and set bridge parameters and port parameters.
14.6.15 Querying the Running Information About the Spanning Tree Protocol
The running information about the spanning tree protocol includes the bridge running
information and port running information.
14.6.16 Configuring the IGMP Snooping Protocol
If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP
Snooping protocol and configure the method for processing the unknown multicast packet.
14.6.17 Querying the Running Information About the IGMP Snooping Protocol
The running information about the IGMP Snooping protocol includes the current multicast router
port and multicast table item.
14.6.18 Modifying the Aging Time of the Multicast Table Item

In the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutes
by default.
14.6.19 Querying the Multicast Router Port
The multicast router port refers to the port that transmits the IGMP query packet to routers. The
Ethernet data board considers the port that receives the IGMP query packet as the router port.
14.6.20 Configuring the Static Multicast Table Item
You can manually specify the static multicast table item that can be forwarded to the
corresponding port in multicast mode.
14.6.21 Querying the Multicast Table Item
You can query the multicast item that the IGMP Snooping protocol dynamically learns and the
static multicast item that is manually created.

The Layer 2 switching refers to the packet switching among switch ports by using the 802.1d,
802.1q, or 802.1ad algorithm. This topic describes the bridge, and the features relevant to the
Layer 2 switching, such as STP/RSTP, IGMP Snooping, and broadcast packet suppression,
which is the core of the Layer 2 switching.
Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs. In
the case of the Ethernet service boards that have the Layer 2 switching capability, the switching
domain can be divided into multiple independent sub-switching domains. As a result, different
bridges can access each other only when there are interconnected services. Each bridge is
configured independently and uses VLANs independently. That is, different bridges can use the
same VLAN.
STP/RSTP
Spanning Tree Protocol (STP) applies to a loop network to realize path redundancy backup by
using certain algorithms. STP prunes a loop network into a tree network without loops. This
helps to avoid proliferation and infinite loop of packets on the loop network.
The rapid spanning tree protocol (RSTP) is an update version of the STP. Compared with the
STP, the RSTP can stabilize the network topology more rapidly.
IGMP Snooping
If the multicast router exists on the network, the bridge can start the IGMP Snooping to realize
the multicast function with the cooperation of the router.
Broadcast Packet Suppression

To prevent broadcast storm from flooding, enable the broadcast packet suppression function for
an Ethernet port to limit the traffic of the broadcast packets that enter the Layer 2 switch.

This topic describes the basic concepts that you need to be familiar with before you use the Layer
2 switching feature.

14.6.2.1 Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs.
14.6.2.2 STP/RSTP
When the network topology of the Ethernet service forms loops, enable the STP or RSTP.
14.6.2.3 IGMP Snooping
If the multicast router exists in the network, enable the IGMP Snooping for the bridge to realize
14.6.2.4 Broadcast Packet Suppression
You can enable the broadcast packet suppression function that is based on the Ethernet port to
prevent spreading of the broadcast storm, through restricting the traffic of the broadcast packet
that enters the Layer 2 switch.
14.6.2.1 Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs.
VB and LP
VB, which is originally put forward by Huawei, is short for various bridge. In the case of the
Ethernet boards that have the Layer 2 switching capability, the switching domain can be divided
into multiple independent sub-switching domains.
A VB contains several logic ports (LPs). By configuring the mounting relation, you can mount
multiple external ports and VCTRUNK ports to one VB. One external port or VCTRUNK port
cannot be mounted to different LPs on one VB.
Figure 14-72 lists the relations among the VB, LP, external port, and VCTRUNK port.
Figure 14-72 Relations among the VB, LP, external port, and VCTRUNK port
Ethernet Switching Board
VB1
Bridge Type
The Ethernet switching board supports three types of bridges: 802.1d bridge, 802.1q bridge, and
802.1ad bridge.
As shown in Figure 14-73, the services on different 802.1d bridges are isolated, but the services
of different VLANs on one bridge are not isolated. The services on different 802.1q bridges are
isolated and the services of different VLANs on one bridge are also isolated.

Figure 14-73 802.1d bridge and 802.1q bridge
VCTRUNK1 VCTRUNK1
PORT1 PORT1 VLAN1
VCTRUNK2 VCTRUNK2
VLAN1
VCTRUNK3 VLAN2 VCTRUNK3
PORT2 VLAN2 PORT2
VCTRUNK4 VCTRUNK4
VLAN3
PORT3 VCTRUNK6 PORT3 VLAN3
VCTRUNK6
802.1d bridge 802.1q bridge
Logical port
As shown in Figure 14-74, two conditions may occur for the 802.1ad bridge.
l When Bridge Switch Mode is set to SVL/Ingress Filter Disable, the services on different
bridges are isolated but the services of different S-VLANs on one bridge are not isolated.
l When Bridge Switch Mode is set to IVL/Ingress Filter Enable, the services on different
bridges are isolated and the services of different S-VLANs on one bridge are also isolated.
Figure 14-74 802.1ad Bridge
VCTRUNK1 VCTRUNK1
PORT1 PORT1 S-VLAN1
VCTRUNK2 VCTRUNK2
S-VLAN1
VCTRUNK3 S-VLAN2 VCTRUNK3
PORT2 S-VLAN2 PORT2
VCTRUNK4 VCTRUNK4
S-VLAN3
PORT3 PORT3 S-VLAN3
VCTRUNK6 VCTRUNK6
802.1ad bridge 802.1ad bridge
IVL/Ingress Filter Enable SVL/Ingress Filter Disable

Logic Port
Table 14-56 Three Types of Bridges Supported by the Ethernet Switching Board
802.1d Bridge 802.1q Bridge 802.1ad Bridge
Bridge switch SVL/Ingress IVL/Ingress SVL/Ingress IVL/Ingress

mode Filter Enable Filter Enable Filter Disable Filter Enable
VLAN filtering Not configured Required Not configured Required

table

802.1d Bridge 802.1q Bridge 802.1ad Bridge
Ingress filtering Disabled: Does Enabled: Disabled: Does Enabled:

not check the Checks the not check the Checks the S-
VLAN tag. VLAN tag. If VLAN tag. VLAN tag. If the
the VLAN ID VLAN ID does
does not equal not equal the
the VLAN ID of VLAN ID of the
the port defined port defined in
in the VLAN the VLAN
filtering table, filtering table,
the packet is the packet is
discarded. discarded.
Bridge learning SVLa IVLb SVLa IVLb

mode
Packet Obtains the Obtains the Obtains the Obtains the

forwarding packet packet packet packet
mode forwarding port forwarding port forwarding port forwarding port
by querying the by querying the by querying the by querying the
MAC address MAC address MAC address MAC address
table, according table, according table, according table, according
to the to the to the to the
destination destination destination destination
MAC address of MAC address MAC address of MAC address
the packet. and VLAN ID the packet. and VLAN ID of
of the packet. the packet.
Range of Forwards the Forwards the Forwards the Forwards the

broadcasting broadcast broadcast broadcast broadcast packet
packet to all the packet to the packet to all the to the ports that
ports on the ports that are ports on the are specified in
bridge. specified in the bridge. the S-VLAN
VLAN filtering filtering table.
table.
Mount port UNI UNI C-aware C-aware

attribute S-aware S-aware
NOTE
l a: When the bridge uses the shared VLAN learning (SVL) mode, it creates an entry according to the source
MAC address and the source port of a packet. This entry is valid to all VLANs.
l b: When the bridge uses the independent VLAN learning (IVL) mode, it creates an entry according to the
source MAC address, VLAN ID, and source port of a packet. This entry is valid to only this VLAN.
l For details about the 802.1ad bridge, see 14.2.2.4 Application of the QinQ Technology in LAN
Services.
MAC Address Table

Entries of a MAC address table provide the mapping relations between MAC addresses and
ports. The entries can be classified into the following categories:

l Dynamic entry
A dynamic entry is obtained by a bridge through the SVL/IVL mode. The dynamic entry
ages, and is lost after the Ethernet switching board is reset.
l Static entry
A static entry, which corresponds to a specific MAC address and port, is manually added
by the network administrator into the MAC address table on the NM. A static entry is also
called a unicast entry. The static entry does not age, and is not lost after the Ethernet
switching board is reset.
l Blacklist entry
A blacklist entry is used to discard the data frame that contains the specified destination
MAC address, that is, the MAC disabled entry. A blacklist entry is also called a blackhole
entry. The blackhole entry is configured by the network administrator. The blackhole entry
does not age, and is not lost after the Ethernet switching board is reset.
NOTE
l If one routing 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 routing entry is automatically deleted. This
mechanism is called aging, and this period is called aging time. The aging time of a MAC address table is
5 minutes by default. You can set this value on the NM.
l The number of entries in a MAC address table is limited. The MAC address capacity of each bridge in the
case of the Ethernet switching board is 16K.
Hub/Spoke
In the case of the convergence service, the mutual access between the non-central stations and
central stations is required but the access between non-central stations is not required. In this
case, specify a mounted port as a Hub port or a Spoke port.
l Hub port
Hub ports can mutually access each other. Hub ports and Spoke ports can mutually access
each other.
l Spoke port
Spoke ports cannot mutually access each other. Hub ports and Spoke ports can mutually
access each other.
A mounted port is a Hub port by default.
14.6.2.2 STP/RSTP
When the network topology of the Ethernet service forms loops, enable the STP or RSTP.
STP
The spanning tree protocol (STP) is used in the looped network. This protocol realizes the routing
redundancy by adopting certain algorithms and releases the looped network into loop-free tree
network, thus preventing the packets from increasing and cycling in an endless manner in the
looped network.
The STP meets the following requirements:
l Configures any activated topology of any bridge to a single spanning tree, and releases the
redundant data loop if there is any between two stations in the network topology.

l Re-configures the spanning tree topology in the case of a bridge fault or an interrupted
route, thus providing a certain protection, and prevents temporary data loops by
automatically containing the bridges and ports of the bridges that are newly added into the
LAN.
l Stabilizes the activated topology in a rapid manner.
l The finally activated topology can be predicted and repeated. In addition, the topology can
be selected by managing the parameters of certain algorithms.
l Operations to the end stations are transparent. For example, the end stations are unaware
of their attachment to a single LAN or a bridged LAN.
l A small part of the available bandwidth of the link is used to create or maintain the spanning
tree, and the bandwidth does not increase with the expanding network size.
The Ethernet switching board supports the STP, which complies with IEEE 802.1d.
RSTP
The rapid spanning tree protocol (RSTP) is an optimized version of STP. Compared to the STP,
the RSTP can stabilize the network topology in a shorter time. The RSTP is compatible with the
STP. These two topologies can be identified by the bridge that uses the RSTP for calculating
the spanning tree.
The Ethernet switching board supports the RSTP, which complies with IEEE 802.1w.

If the multicast router exists in the network, enable the IGMP Snooping for the bridge to realize
Multicast Protocol
The multimedia network applications, such as video conference, E-learning, and video on
demand (VOD) service, require that the information is transmitted from one source to multiple
destinations, that is, transmitted in one-to-many transmission mode. Because the data traffic of
the multimedia information is large, simulating the one-to-many transmission through one-to-
one mode occupies a large volume of bandwidth. In addition, information flooding is generated
if the broadcast is used. Hence, the one-to-many multicast protocol is required.
The IP multicast protocol is based on the IP protocol stack. The IP multicast protocol uses a D-
type IP address that is similar to the unicast address to indicate a group. When the packet is
transmitted to all the IP hosts in a multicast group, the calling and access mode is similar to the
calling and access mode of the unicast. The hosts in an IP multicast group can join or quit this
multicast group at any time and at any location, with unlimited number of members. The
multicast router does not store the member relations of all the hosts. The router stores the
information only about whether any host in the physical subnetwork on the physical interface
belongs to a specific multicast group. The host stores the information only about the multicast
groups that it joins.
The IP multicast protocol is classified into two categories: communication protocol among the
multicast routers and the protocol among the multicast routers, hosts, and Layer 2 switches.
l The communication protocol among multicast routers is used to obtain the multicast routing
information. This type of protocol contains the protocol independent multicast-dense mode

(PIM-DM), protocol independent multicast-sparse mode (PIM-SM), and distance vector

multicast routing protocol (DVMRP).
l The protocol among the multicast routers, hosts, and Layer 2 switches is used to forward
the multicast packet according to the multicast routing information. This type of protocol
contains the Internet group management protocol (IGMP), IGMP Snoop, IGMP Proxy.
IGMP is a Layer 3 multicast protocol, and IGMP Snooping, IGMP Proxy are Layer 2
multicast protocols.
IGMP
The IGMP contained in the TCP/IP suite is used to manage members of the IP multicast group.
It creates and maintains the member relations of the multicast group between the host and its
adjacent multicast router.
The host notifies the local router of joining a specific multicast group and of accepting the
information from this multicast group through this protocol. The router periodically queries
whether a member of a specific group in the LAN is activated through this protocol (that is,
whether the member of a specific multicast group still exists in the network segment), and thus
collects and maintains the member relations of groups that are connected to the router. By using
this mechanism, the multicast router establishes a table, which contains the ports of the router
and members of each specific group in the subnetworks corresponding to each port. When
receiving the packet of a specific group, the router forwards the packet only to these ports that
have the members of this group.
The router uses the IP multicast address to forward multicast packets. Each multicast group
corresponds to a specific IP multicast address. The IP multicast address is a D-type IP address,
which ranges from 224.0.0.0 to 239.255.255.255.
IGMP Snooping
When the multicast router is connected to the host by using the bridge, the switch broadcasts the
multicast packet at Layer 2 if the bridge disables the Layer 2 multicast protocol. See Figure
14-75. When the multicast router is connected to the host by using the bridge, if the bridge
enables the Layer 2 multicast protocol (such as IGMP Snooping), the bridge can establish the
mapping relations between group members and switch ports and thus can forward the packet
only to the ports that have group members.
Figure 14-75 Transmission of the multicast packet (with IGMP Snooping disabled)
Video stream
Internet/
Intranet
VOD server
Multicast router
Video stream
Layer 2 Ethernet
switch
Video Video Video

stream stream stream
Multicast Non-multicast Non-multicast

group member group member group member

Figure 14-76 Transmission of the multicast packet (with IGMP Snooping enabled)
Video stream
Internet/
Intranet
VOD server
Multicast router
Video stream
Layer 2 Ethernet
switch
Video
stream
Multicast Non-multicast Non-multicast

group member group member group member
The IGMP Snooping creates and maintains the mapping relations between group members and
switch ports by sensing the IGMP packet. After the IGMP Snooping is enabled, the bridge
considers the port that receives the IGMP request as the router port. When detecting the response
that is transmitted to the router port, the bridge adds the port that receives the response and the
router port into a specific multicast group. When detecting that a certain port in a multicast group
does not respond to the IGMP request for consecutive times and that the times exceed the
threshold, the bridge deletes this port from the multicast group.
After the IGMP Snooping is enabled, when receiving the multicast packet, the bridge queries
the multicast table in which the source port is the router port. If a multicast group that matches
the multicast address exists in the multicast table, the bridge forwards the packet to this multicast
group. If no multicast group exists, the bridge discards the multicast packet or broadcasts the
packet depending on the NM setting.
Three versions of IGMP requests are available, and they are, V1, V2, and V3. The Ethernet
switching board can process versions V1 and V2. The Ethernet switching board also supports
the aging of the router port and multicast table item.
NOTE
l If a router port is not updated in a certain period (that is, no IGMP request from this port is received), all the
multicast tables that are related to this router port are deleted. This mechanism is called aging, and this period
is called aging time. The aging time of a router port is 5 minutes by default. You cannot set this value on
the NM.
l Similarly, the multicast table item (that is, multicast group) ages. The aging time is 8 minute by default. You
can set this value on the NM.
14.6.2.4 Broadcast Packet Suppression

You can enable the broadcast packet suppression function that is based on the Ethernet port to
prevent spreading of the broadcast storm, through restricting the traffic of the broadcast packet
that enters the Layer 2 switch.

Based on the ratio of the number of broadcast packets to the total number of packets, the broadcast
packet suppression function determines whether the system restricts the broadcast traffic. When
the ratio of the number of broadcast packets to the total number of packets exceeds the value set
by the user, the system discards the broadcast traffic to decrease the ratio of the broadcast packets
so that the ratio is in a reasonable range. In this manner, the broadcast storm can be prevented
and the network congestion is avoided, which ensures the normal operation of the network.
PORTs of the Ethernet switching board support the broadcast packet suppression function.
14.6.3 Availability
The Layer 2 switching feature requires the support of the applicable equipment and boards.
Table 14-57 Availability of Layer 2 Switching

Bridge (802.1q bridge and EMS6, EFP6 IDU 620

802.1d bridge)
EM4T IDU 605
Bridge (802.1ad bridge) EMS6, EFP6 IDU 620
IGMP Snooping
STP/RSTP EMS6, EFP6 IDU 620
EM4T IDU 605
Broadcast packet EMS6, EFP6 IDU 620

suppression
- IDU 605

The Layer 2 switching has different relations with other features.
l The port that is used by the bridge cannot be configured with the line service.
l The STP/RSTP is applicable only to the bridge.
l The IGMP Snooping is applicable only to the bridge.
l The broadcast packet suppression function is applicable only to the PORT on the bridge.
l The port on the bridge supports the QoS function.

The bridge, STP/RSTP, and IGMP Snooping comply with the relevant IEEE standards.
14.6.5.1 Bridge
A bridge forwards a packet according to the entry of a MAC address table.
14.6.5.2 STP/RSTP
The realization of the STP complies with IEEE 802.1d, and the realization of the RSTP complies
with IEEE 802.1w.

The IGMP Snooping establishes and creates the mapping relations between the group members
and switch ports by sensing the IGMP packet. This ensures that the multicast packet is
transmitted only to the ports that are connected to the multicast users.
14.6.5.1 Bridge
A bridge forwards a packet according to the entry of a MAC address table.
A bridge forwards a packet as follows:
1. In the case of an 802.1q bridge, it checks the VLAN ID of a data frame that is received at
the port. If the VLAN ID of this frame does not equal the VLAN ID of the port that is
defined in the VLAN filter table, the bridge discards this frame.
2. If the broadcast packet suppression function of the bridge port is enabled and the traffic of
the broadcast packet exceeds the pre-set threshold value, the port discards the received
broadcast frame.
3. If the IGMP Snooping protocol of the bridge is enabled, the bridge processes the IGMP
packet and multicast packet that are received at the port, according to the principle described
in 14.6.5.3 IGMP Snooping.
4. If the bridge receives the multicast packet but the IGMP Snooping protocol is disabled, it
forwards the multicast packet among all the ports of the bridge or among all the mounted
ports of the VLAN (excluding the source port).
5. According to the learning mode, the bridge adds or updates the entry corresponding to the
source MAC address of the data frame in the MAC address table, and thus establishes the
mapping relation between the MAC address and the receive port.
6. The bridge checks the MAC address table according to the destination MAC address of the
data frame.
l If the blacklist entry corresponding to the destination MAC address exists, the bridge
discards this data frame.
l If the dynamic entry or the static entry corresponding to the destination MAC address
exists, the bridge forwards this data frame to the destination port indicated by the entry.
l If no corresponding entry exists, the bridge forwards the packet among all the ports of
the bridge or among all the mounted ports of the VLAN (excluding the source port),
according to the bridge type (802.1d bridge or 802.1q bridge).
7. The bridge needs to determine whether the source port and the destination port are Hub or
Spoke when forwarding the data frame. If the source port is the Hub port, the bridge
forwards the packet to the Hub port and the Spoke port. If the source port is the Spoke port,
the bridge forwards the packet to the Hub port.
NOTE
If the STP or the RSTP of the bridge is enabled, only the port in the forwarding state can forward the data frame.
14.6.5.2 STP/RSTP
The realization of the STP complies with IEEE 802.1d, and the realization of the RSTP complies
with IEEE 802.1w.
Basic Concepts
l Bridge protocol data unit (BPDU)

The STP transmits the BPDU among pieces of equipment to determine the network
topology. The BPDU contains adequate information that is required to implement the
calculation of the spanning tree. The BPDU is classified into the following categories:
Configuration BPDU (CBPDU)
The CBPDU refers to a packet that is used to calculate the spanning tree and maintain
the spanning tree topology. The CBPDU contains the root bridge ID, root path cost,
designated bridge ID, designated port ID, and related timing information.
Topology change Notification BPDU (TCN BPDU)
The TCN BPDU refers to a packet that is used to notify the relevant equipment of the
network topology change in the case of topology change.
l Bridge ID
The bridge ID is used to indicate a bridge. The bridge ID is 64-bit long. The most significant
16 bits indicate the priority of the bridge, and the least significant 48 bits indicate the MAC
address of a certain bridge port. In the STP, the bridge ID also indicates the priority of the
bridge. The smaller the value of the bridge ID, the higher the priority.
l Port ID
The port ID is used to indicate a port on the bridge. The port ID is 16-bit long. The most
significant eight bits indicate the priority of the port, and the least significant eight bits
indicate the port number. In the STP, the port ID also indicates the priority of the port. The
smaller the value of the port ID, the higher the priority.
l Root bridge
In a network that enables the STP, only one root bridge exists. The root bridge is selected
based on the running of the STP. The bridge with the smallest bridge ID is selected as the
root bridge. When a network that enables the STP is stabilized, only the root bridge
generates and transmits the CBPDU periodically. Other bridges only relay the CBPDU.
This can ensure a stable network topology. If the network topology is changed, the root
bridge may also change.
l Root port
The root port refers to a port on the bridge that transmits/receives frames to/from the root
bridge. Each non-root bridge has only one root port. The root port is selected based on the
running of the STP. The port of a bridge whose root path cost is the smallest is selected as
the root port. If more than one port whose root path cost is the smallest exist, the port with
the smallest port ID is selected as the root port.
l Designated port
The designated port refers to a port of a LAN that transmits/receives frames to/from the
root bridge. Each LAN has only one designated port. The designated port is selected based
on the running of the STP. The port that is connected to the LAN and whose root path cost
is the smallest is selected as the designated port. If more than one port whose root path cost
is the smallest exist and if these ports are on different bridges, the port whose bridge ID is
the smallest is selected as the designated port. If more than one port whose root path cost
is the smallest exist and if these ports are on the same bridge, the port with the smallest port
ID is selected as the designated port.
l Path cost
The path cost is used to indicate the status of the network that is connected to the port. The
higher the rate of the port, the smaller the path cost.
l Root path cost

The root path cost refers to the cost of the path from a certain port to the root bridge. That
is, the sum of path cost of all the passed ports from this port to the root bridge.
l Port state
In a network that enables the STP, the port state can be any of the following states:
Blocking
A port in the blocking state receives and processes the BPDU and does not transmit the
BPDU. When a port is in the blocking state, it does not learn the MAC address and does
not forward the user packet.
Listening
It is a transitional state. A port in the listening state transmits, receives, and processes
the BPDU. When a port is in the listening state, it neither learns the MAC address nor
forwards the user packet.
Learning
It is a transitional state. A port in the learning state transmits, receives, and processes
the BPDU. When a port is in the learning state, it learns the MAC address but does not
forward the user packet.
Forwarding
A port in the forwarding state transmits, receives, and processes the BPDU. When a
port is in the learning state, it learns the MAC address and forwards the user packet.
Disabled
A port in the disabled state does not forward frames, and does not implement the
spanning tree algorithm and STP.
l Timer
Port timers are classified into the following categories:
Hold timer
The hold timer is used to measure the interval between two CBPDU transmissions. The
timeout value is the Hold Time of the bridge.
Message age timer
The message age timer is used to measure the age of the CBPDU packet recorded by a
port. When the age of the CBPDU packet stored by the bridge exceeds the Message Age
parameter, the bridge discards the packet. The Message Age parameter determines the
initialization age when the CBPDU packet is stored in the bridge. The Message Age
parameter is 0 when the root bridge generates the packet. Each time the packet is
forwarded to a port, a fixed increment value is added to the Message Age parameter.
Forward delay timer
The forward delay timer is used to measure the holding time of a port in the listening
state and in the learning state. When the listening state remains for a period that is the
same as the value of the Forward Delay parameter, the port state is changed to learning.
When the learning state remains for a period that is the same as the value of the Forward
Delay parameter, the port state is changed to forwarding.
Bridge timers are classified into the following categories:
Hello timer
The hello timer is used to measure the interval when the bridge transmits the CBPDU
packet. The timeout value is the Bridge Hello Time of the bridge.
Topology change notification timer

The topology change notification timer indicates the duration when the bridge
periodically transmits the TCN. The timer is used to notify the designated bridge in the
LAN that is attached to the root port of the bridge of any detected topology change. The
timeout value is the Bridge Hello Time of the bridge.
Topology change timer
In the case of the root bridge, when receiving the TCN, the bridge transmits the TCN
after the topology change is complete and the time period indicated by the topology
change timer times out. The timeout value is the Topology Change Time of the bridge.
NOTE
The Max Age, Hello Time, and Forward Delay parameters that are used by different bridges are unified
to the values of these three parameters that are used by the root bridge, by mutually transmitting the
CBPDU.
STP Algorithm
The STP algorithm is conducted as follows:
1. In the initialization state, all the ports on all the bridges are in the listening state. In this
case, each port generates the CBPDU, and the CBPDU considers the bridge where the port
resides as the root bridge and the root path cost of the CBPDU is 0. Each port transmits the
CBPDU periodically, and the period is the Hello Time of the bridge.
2. The bridge compares the information about the CBPDU that is received at the port with
the CBPDU information that is stored by that port.
The bridge compares the information that is carried by the CBPDU as follows:
(1) The bridge first compares the root bridge IDs. The smaller the ID, the better.
(2) If the root bridge IDs are the same, the bridge compares the root path cost values. The
smaller the root path cost, the better.
(3) If the root path cost values are the same, the bridge compares the designated bridge
IDs. The smaller the designated bridge ID, the better.
(4) If the designated bridge IDs are the same, the bridge compares the designated port
IDs. The smaller the designated port ID, the better.
3. If the information about the CBPDU that is received at the port is better, the bridge replaces
the information about the CBPDU that is originally stored by the port. If the root bridge ID
or the root path cost in the information about the CBPDU that replaces the information
about the CBPDU originally stored by the port is smaller than the information originally
stored by the port, the bridge needs to process this new CBPDU as follows:
l The bridge stores the information about the CBPDU (including the root bridge ID, root
path cost, message age, and corresponding timers).
l The bridge updates the root bridge ID and root path cost (the root path cost of the bridge
equals the sum of the root path cost of the port that stores the packet and the root path
cost of the port that receives the CBPDU).
l The designated port updates the designated root bridge and the root path cost at the same
time (the root path cost of the designated port equals the sum of the root path cost of
the bridge and the path cost of the port).
l The designated port relays the CBPDU.
If the information about the CBPDU that is received at the port is worse than the information
about the CBPDU that is stored by the port, the port transmits the CBPDU that is stored as
a response.

4. If the bridge maintains a root bridge ID that is the same as its bridge ID and if the root path
cost is 0, the bridge is a root bridge. The root bridge sets the path cost of each port to 0.
5. If the bridge is a non-root bridge, it considers the port that receives the best CBPDU
information as the root port.
6. If the bridge is a non-root bridge, it considers any of the following ports as the designated
port:
l The bridge ID and port ID of the port are the same as the designated bridge ID and port
ID recorded by the port.
l The root bridge ID recorded by the port is different from the root bridge ID of the bridge.
l The root path cost of the port (sum of the root path cost of the bridge and the path cost
of the port) is smaller than the root path cost recorded by the port.
l The root path cost of the port is the same as the root path cost recorded by the port, but
the bridge ID is smaller than the designated bridge ID of the port.
l The root path cost of the port is the same as the root path cost recorded by the port, and
the bridge ID is the same as the designated bridge ID of the port. The port ID, however,
is smaller than the designated ID of the port.
7. When the Forward Delay parameter set for the listening state timer of the port expires, the
states of the root port and the designated port transition to learning. When the learning state
remains for a period that is the same as the value of the Forward Delay parameter, the states
of the root port and the designated port transition to forwarding. The states of these ports
whose states are not changed to forwarding transition to blocking.
8. If a trail becomes faulty, the root port on this trail no longer receives new CBPDUs, and
therefore, the original CBPDU is discarded due to timeout. In this case, the calculation of
the spanning tree is conducted again, and a new trail will be available to replace the faulty
trail, thus restoring the connectivity of the network.
Improvement in the RSTP

Compared with the STP, the RSTP is improved as follows:
l Classification of port roles
The port roles in the RSTP are classified into the following categories: root port, designated
port, alternate port, and backup port. The alternate port refers to a port that is in the blocking
state due to the learning of the BPDU transmitted by other bridges. The backup port refers
to a port that is in the blocking state due to the learning of the BPDU transmitted by the
bridge the port resides in.
l Classification of port states
The blocking, listening, and disabled states are combined into the discarding state in the
RSTP.
l Rapid transition of port states
To support the rapid transition of port states, the RSTP defines the point-to-point attribute
of a port and an edge port.
Point-to-point attribute
The point-to-point attribute of a port can be set to adaptive connection, shared media,
or link connection. If the attribute of a port is set to adaptive connection, the bridge
determines the actual point-to-point attribute of the port according to the actual working
mode of the port. If the actual working mode of the port is full-duplex, the actual point-
to-point attribute of the port is "true". If the actual working mode of the port is half-
duplex, the actual point-to-point attribute of the port is "false". If the point-to-point

attribute of a port is set to shared media, the actual point-to-point attribute of the port
is "false". If the point-to-point attribute of a port is set to link connection, the actual
point-to-point attribute is "true". Only the port whose point-to-point attribute is "true"
can transmit the rapid transition request and response.
Edge port
The edge port refers to the bridge port that is connected only to the LAN. If a port is set
to an edge port and if this port can receive the BPDU, the port is actually an edge port.
If the port role of this edge port is a designated port, the port can realize the rapid state
transition.
The rapid transition among port states can be classified into the rapid port state transition
of the root port, rapid port state transition of the designated port, and the rapid port state
transition of the alternate port and backup port.
Rapid port state transition of the root port
A root port that does not function as a backup port recently (that is, in a recent period
that is less than double times of the Hello Time) transition to the forwarding state without
any delay, and this root port enables the designated port that functions as the root port
recently (that is, in a recent period that is less than Forward Delay) to transition to the
discarding state.
Rapid port state transition of the designated port
If an edge port is also a designated port, the port state transitions to the forwarding state
without any delay. The designated port whose actual point-to-point attribute is "true"
can realize the rapid transition among port states through rapid switching between the
request process and response process.
Rapid port state transition of the alternate port and the backup port
The port state of the alternate port and the backup port transitions to the disabled state
without any delay.

The IGMP Snooping establishes and creates the mapping relations between the group members
and switch ports by sensing the IGMP packet. This ensures that the multicast packet is
transmitted only to the ports that are connected to the multicast users.
Basic Concepts
l Router port
The router port refers to a port that connects to a multicast router.
l Multicast member port
The multicast member port refers to a port that connects to a multicast group member. The
multicast group member refers to a host that joins a multicast group.
l Multicast group
The multicast group records the mapping relations among the router ports, MAC multicast
addresses, and multicast group members. A multicast group is also called a multicast table
item.
l Maximum query response time
When transmitting the IGMP specific query packet to the multicast member port, the 802.1q
bridge starts the maximum query response timer. If the bridge does not receive the IGMP
response packet within the maximum query response time, the bridge adds one to the no-

response times of the port. When the no-response times of the port exceeds the pre-set
threshold, the bridge deletes the multicast member from the multicast group.
l IGMP general query packet
The IGMP general query packet refers to a packet that is transmitted by a multicast router
to the multicast group members. The IGMP general query packet is used to query which
multicast groups have members.
l IGMP specific query packet
The IGMP specific query packet refers to a packet that is transmitted by a multicast router
to the multicast group members. The IGMP specific query packet is used to query whether
specific multicast groups have members.
l IGMP report packet
The IGMP report packet refers to a report packet that is transmitted by a host to a multicast
router. The IGMP report packet is used to apply for the joining of a multicast group or to
respond to the IGMP query packet.
Processing Flow
The 802.1q bridge processes the IGMP Snooping as follows:
1. If receiving the IGMP general query packet or the IGMP specific query packet, the bridge
processes this packet as follows:
(1) The bridge checks whether the port that receives the packet is already learnt as the
router port.
(2) If this port is already learnt, the bridge re-sets the aging time of the router port. If this
port is not learnt, the bridge records the port as the router port and starts the aging
timer of the port.
(3) If the received packet is the IGMP specific query packet and the port that receives this
packet is already recorded as the router port, the bridge broadcasts this packet in the
specific multicast group and starts the timer for the maximum query response time if
the multicast group that is specified in this packet exists. Otherwise, the bridge
broadcasts this packet in the VLAN domain of the 802.1q bridge.
2. If receiving the IGMP report packet, the bridge processes this packet as follows:
(1) The bridge checks whether the multicast record is already learnt in the VLAN domain
of the 802.1q bridge.
(2) If this multicast record is not learnt and if the multicast group does not exist, the bridge
creates the multicast group and establishes the mapping relations among the router
ports, MAC multicast addresses, and multicast group members by considering this
port as the multicast member port. If this multicast record is not learnt and this port is
not contained in the multicast member ports of the multicast group, the multicast group
adds this port as the multicast member port. If this multicast record is learnt, the bridge
re-sets the counting of no-response times for this multicast member.
3. If receiving the multicast packet, the bridge processes this packet as follows:
l The bridge queries the multicast table that uses the router port as the source port.
l If a multicast group that matches the multicast address exists in the multicast table, the
bridge forwards the packet to this multicast group.
l If no multicast group exists, the bridge discards the multicast packet or broadcasts the
packet in the VLAN range depending on the NM setting.

4. The bridge processes the aging as follows.

l If the maximum query response time times out, the bridge adds one to the no-response
times of the multicast member.
l If the no-response times of a multicast member exceeds the threshold, the bridge deletes
this multicast member port.
l If a multicast group does not have any multicast member port, the bridge deletes this
multicast group.
The 802.1d bridge processes the IGMP Snooping similarly. The difference is as follows: The
802.1d learns the packet by using the SVL mode other than by using the IVL mode, and the
802.1d bridge broadcasts the packet without the restriction of the VLAN domain.
Version
Three versions of IGMP requests are available, and they are, V1, V2, and V3. The Ethernet
switching board can process versions V1 and V2.
V2 is compatible with V1. Compared with V1, V2 is improved as follows:
l Supports the multicast group leave packet.

This packet can efficiently decrease the delay generated in the process of deleting the
multicast group.
l Supports the specific query packet.
This packet allows broadcasting the IGMP query packet in the specific multicast group.

Plan the relevant parameters of the Layer 2 switching service according to the actual situation
of microwave links.
Prerequisite
You must learn the situation of the microwave links.
Procedure
Step 1 Plan the bridge.
Adhere to the following principles when planning the bridge:
l Using the 802.1q bridge is a priority. If the conditions of the VLAN that is used by the user
are not known and if the user does not require the isolation of the data among VLANs, you
can also use the 802.1d bridge.
l If the Layer 2 switching services from several branch nodes are converged at a convergence
node, set this convergence node to Hub and set these branch nodes to Spoke. In the case of
the multipoint-to-multipoint Layer 2 switching service, set each node to Hub.
Step 2 Plan the MAC address table.
Adhere to the following principles when planning the MAC address table:
l If the node that only receives data frames exists in the network, configure the corresponding
VLAN unicast entry.

l If certain nodes are not allowed to transmit data frames, configure the corresponding MAC
disabled entries for the bridge that accesses these nodes.
l Set the aging time of the MAC address table to the same value as the aging time of the
interconnected Ethernet equipment. It is recommended that you set the aging time of the
MAC address table to 5 minutes (default value).
Step 3 Plan the STP/RSTP.
Adhere to the following principles when planning the STP/RSTP:
l In the service networking process, it is recommended that you prevent the loop from forming
in the case of the Layer 2 service and thus avoid enabling the STP or RSTP.
l If the loop is already formed in the service networking, you must enable the STP or RSTP.
The protocol type should be set according to the requirement of the interconnected Ethernet
equipment. It is recommended that you use the RSTP.
l The bridge priority, port priority, and port path cost should be set according to the requirement
of the interconnected Ethernet equipment. Use the default values, unless otherwise specified.
l The Max Age, Hello Time, and Forward Delay parameters should be set to the same values
as these parameters of the interconnected Ethernet equipment. Use the default values, unless
otherwise specified.
Step 4 Plan the IGMP Snooping protocol.
Adhere to the following principles when planning the IGMP Snooping protocol:
l If the IGMP multicast router exists in the interconnected Ethernet network, enable the IGMP
Snooping protocol according to the requirement of the router. Otherwise, do not enable the
IGMP Snooping protocol.
l Set the processing method for the unknown multicast packet and multicast aging time
according to the requirement of the IGMP multicast router. It is recommended that you use
the default values.
----End

This topic describes the configuration tasks relevant to the Layer 2 switching feature.
14.6.8 Creating the Ethernet LAN Service

bridge.
Prerequisite
Precautions
l This task describes only how to create the 802.1d bridge and how to create the 802.1q
bridge.

l The IDU 620 supports the Ethernet switching board EMS6.

l The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 2 Click New.
Step 3 Set the attributes of the bridge according to the bridge type.
l Set the attributes of the 802.1q bridge.
l Set the attributes of the 802.1d bridge.

Step 4 Configure the mounted ports of the bridge.

The Service Mount Configuration dialog box is displayed.
2. Select a port from the ports listed in Available Mounted Ports, and then click .
3. Optional: Repeat Step 4.2 to select other mounted ports.
4. Click OK.
the VCTRUNK.

3. In Available Bound Paths, set Level and Service Direction of the bound paths.
NOTE
6. Click OK.
Step 6 Click OK.
----End
Parameters

Bridge Type 802.1q, 802.1d, 802.1q l When setting this parameter to 802.1q,
802.1ad (EMS6) create the 802.1q bridge.
802.1q, 802.1d l When setting this parameter to 802.1d,
(EM4T, a logical create the 802.1d bridge.
board EMS4) l Using the 802.1q bridge is a priority. If
the conditions of the VLAN that is used
by the user are not known and if the user
does not require the isolation of the data
among VLANs, you can also use the
802.1d bridge.
l This task describes only how to create
the 802.1d bridge and how to create the
802.1q bridge.

Enable (802.1q), Enable (802.1q), the VLANs share one MAC address
SVL/Ingress Filter SVL/Ingress Filter table. When the bridge uses the IVL
Disable (802.1d) Disable (802.1d) mode, all the VLANs correspond to their
VLAN ID does not equal the VLAN ID
Mount Port - - l Only the port that is selected as the

mounted port of a bridge functions in the
packet forwarding process of the bridge.
situations.

port.


the service needs.
l As the VC-4-1s of the EFT4 board and
EMS6 board support only VC-3 paths
whereas the VC-4-2s support both
VC-12 paths and VC-3 paths, give
VC-3 paths.

14.6.9 Modifying the Mounted Port of a Bridge

This operation enables the user to modify the mounted port of a bridge, the enabled state of the
mounted port, and Hub/Spoke attribute of the port.
Prerequisite
The Ethernet LAN service must be created.

Precautions
CAUTION
Modifying the ports that are mounted to the bridge may interrupt the service.
CAUTION
Incorrect configuration of Hub/Spoke attribute interrupts the service.

Procedure
Step 2 Select the bridge that is already created, and click the Service Mount tab.
Step 3 Modify the mounted port of this bridge and the related attributes of the mounted port.
To change the port that is connected to the 802.1d/802.1q bridge, click the corresponding Mount
Port. After selecting the corresponding option from the drop-down list, click Apply.
To change the port that is connected to the 802.1ad bridge, click Configure Mount. After
changing the settings in the dialog box that is displayed, click OK.
----End
Parameters
VB Port 1 to 14 - This parameter specifies the ID of the logical

port of the bridge.
Mount Port Unconnected, a - l Only the port that is selected as the

specific PORT, a mounted port of a bridge functions in the
specific packet forwarding process of the bridge.
VCTRUNK, IFUP1 l Set this parameter according to actual
situations.
Port Enabled Enabled, Disabled Enabled Set Port Enabled to Enabled. Otherwise,
the port cannot forward the service.

Hub/Spoke Hub, Spoke Hub l The Spoke ports cannot access each
other. The Hub port and the Spoke port
can access each other. The Hub ports can
access each other.
situations.
Working Mode 10M Half-Duplex, Auto-Negotiation l The Ethernet ports of different types
100M Full-Duplex, works in the auto-negotiation mode, set
Auto-Negotiation (a the working mode of the equipment on
logical board the local side to Auto-Negotiation.
EMS4, PORT1-
PORT3) l When the equipment on the opposite side
works in the full-duplex mode, set the
10M Half-Duplex, working mode of the equipment on the
10M Full-Duplex, local side to 10M Full-Duplex, 100M
100M Half-Duplex, Full-Duplex, or 1000M Full-Duplex
100M Full-Duplex, depending on the port rate of the
1000M Full- equipment on the opposite side.
Duplex, Auto-
Negotiation (a l When the equipment on the opposite side
logical board works in the half-duplex mode, set the
EMS4, PORT4) working mode of the equipment on the
local side to 10M Half-Duplex, 100M
10M Half-Duplex, Half-Duplex, or Auto-Negotiation
10M Full-Duplex, depending on the port rate of the
100M Half-Duplex, equipment on the opposite side.
100M Full-Duplex,
1000M Full-
Duplex, Auto-
Negotiation
(EMS6)


14.6.10 Creating the VLAN Filter Table

Prerequisite
The EVPLAN service must be created.
Precautions
Procedure
Step 2 Select the bridge that is already created, and click the VLAN Filtering tab.
Step 3 Create the VLAN filter table.
1. Click New.
The Create VLAN dialog box is displayed.
2. Set VLAN ID (e.g:1,3-6).
3. Select a port from the ports listed in Available forwarding ports, and then click .
4. Optional: Repeat Step 3.3 to select other forwarding ports.

5. Click OK.
----End
Parameters
VLAN ID (e.g: 1-4095 - l You can set this parameter to a number

1,3-6) or several numbers. When you set this
3, 4, 5, and 6.
situations.
selected forwarding This parameter - l The packets can be forwarded between

ports indicates the ports the selected forwarding ports only.
that are mounted to a l The ports that are in selected
bridge. forwarding ports can forward only the
packet that carries the VLAN ID (e.g:
1,3-6) tag. These ports discard the packet
that carries other VLAN tags.
l The broadcast packet that is transmitted
by the ports in selected forwarding
ports is broadcast only to the ports
included in selected forwarding ports.

14.6.11 Creating the Entry of a MAC Address Table Manually

The bridge can obtain the dynamic entry of a MAC address table by using the SVL or IVL mode.
In addition, you can manually add the entry of a MAC address table. The manually created
entries of a MAC address table can be classified into two categories: unicast entry (that is, static
entry) and disabled entry (that is, blacklist entry).
Prerequisite
The VLAN filter table must be created.
Precautions
Procedure
Step 2 Optional: Create the unicast entry manually.

1. Select the bridge that is already created, and click the VLAN Unicast tab.
2. Click New.
The Create VLAN Unicast dialog box is displayed.
3. Set the parameters of the unicast entry.
4. Click OK.
Step 3 Optional: Create the disabled entry manually.

1. Select the bridge that is already created, and click the Disable MAC Address tab.
2. Click New.
The Disable MAC Address Creation dialog box is displayed.
3. Set the parameters of the disabled entry.

4. Click OK.
----End
Parameters
VLAN ID (e.g. 1-4095 - l In the case of the 802.1d bridge and the
1,3-6) 802.1ad bridge, this parameter is invalid
VLAN ID if the SVL mode is used. The set entry
applies to all the VLANs.
l In the case of the 802.1q bridge and the
802.1ad bridge, the set entry applies only
to the VLAN whose ID is equal to the set
value of this parameter if the IVL mode
is used.
situations.
MAC Address - - Set this parameter according to actual

situations.
Physical Port Each port that is - This parameter indicates the Ethernet port
mounted to a bridge corresponding to a MAC address. Set this
parameter according to actual situations.
14.6.12 Modifying the Aging Time of the MAC Address Table Entry
In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5
minutes by default.
Prerequisite
Precautions

Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
Step 2 Modify the aging time of the MAC address table entry.
1. Double-click MAC Address Aging Time corresponding to this Ethernet switching board.
The MAC Address Aging Time dialog box is displayed.
2. Set the duration and unit of the aging time.
3. Click OK.
Step 3 Click Apply.
----End
Parameters
MAC Address 1 Min to 120 Day 5 Min l If one entry is not updated in a certain
Aging Time period, that is, if no new packet from this
MAC address is received to enable the
re-learning of this MAC address, this
entry is automatically deleted. This
mechanism is called aging, and this
period is called aging time.
l If this parameter is set to a very large
value, the bridge stores excessive MAC
address table entries that are outdated,
which exhausts the resources of the
MAC address forwarding table.
l If this parameter is set to a very small
value, the bridge may delete the MAC
address table entry that is needed, which
reduces the forwarding efficiency.
default value.
14.6.13 Querying the Actual Capacity of the MAC Address Table

and the Dynamic Entry
By querying the actual capacity of the MAC address table and the dynamic entry, you can learn
about the MAC address learning situation of the bridge.

Prerequisite
Precautions
The IDU 620 supports the Ethernet switching board EMS6, which supports the querying of the
VLAN MAC address table capacity and the self-learning MAC address.
The IDU 605 IF/2F supports the Ethernet switching board EMS4 (a logical board), which
supports the querying of the self-learning MAC address only.
Procedure
Step 2 Query the actual capacity of the MAC address table.

1. Select the bridge that is already created, and click the VLAN MAC Address Table
Capacity tab.
2. Click Query.
3. View the actual capacity of the MAC address table.
Step 3 Query the actual capacity of the MAC address table.

1. Select the bridge that is already created, and click the Self-learning MAC Address tab.
2. Optional: Click First page, Previous, or Next to view the dynamic entries of the MAC
address table by page.
----End
14.6.14 Configuring the Spanning Tree Protocol

In the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridge
and set bridge parameters and port parameters.
Prerequisite
Precautions

Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
Step 2 Optional: Set the enabled status of the protocol.
1. Click the Protocol Enable tab.
2. Configure parameters of the enabled protocol.
3. Click Apply.
Step 3 Optional: Set bridge parameters.
1. Click the Bridge Parameter tab.
2. Set bridge parameters.
3. Click Apply.
Step 4 Optional: Set port parameters.
1. Click the Port Parameter tab.
2. Set port parameters.
3. Click Apply.
Step 5 Optional: If you are enabling the RSTP, set the point-to-point attribute of the Ethernet port.
1. Click the Point to Point Attribute tab.
2. Set the point-to-point attribute.
3. Click Apply.
----End

Parameters
Protocol Enabled Enabled, Disabled Disabled l This parameter determines whether to

enable the spanning tree protocol.
l It is recommended that you do not enable
the STP or RSTP in the service
networking process, because this can
prevent the Layer 2 service from forming
the loop.
l If the loop is already formed in the
service networking, you must start the
STP or RSTP.
Protocol Type STP, RSTP RSTP l This parameter is valid only when
Protocol Enabled is set to Enabled.
l The protocol type should be set
according to the requirement of the
interconnected Ethernet equipment.
Generally, it is recommended that you
Priority (Bridge 0-61440 32768 l The most significant 16 bits of the bridge
Parameter) ID indicates the priority of the bridge.
l The smaller the value of this parameter,
the higher the priority and the higher the
possibility that the bridge is selected as
the root bridge.
l If the priorities of all the bridges in the
STP network use the same value, the
bridge whose MAC address is the
smallest is selected as the root bridge.
Max Age (s) 6-40 20 l This parameter indicates the maximum

age of the CBPDU packet that is
recorded by the port.
l The greater the value, the longer the
transmission distance of the CBPDU,
which indicates that the network
diameter is greater. When the value of
this parameter is greater, it is less
possible that the bridge detects the link
fault in a timely manner and thus the
network adaptation ability is reduced.

Hello Time (s) 1-10 2 l This parameter indicates the interval of

transmitting the CBPDU packet of the
bridge.
l The greater the value of this parameter,
the less the network resources that are
occupied by the spanning tree. The
topology stability, however, decreases.
Forward Delay (s) 4-30 15 l This parameter indicates the holding

time of a port in the listening state and in
the learning state.
l The greater the value, the longer the
delay time of the network state change.
Hence, the topology changes are slower
and the recovery in the case of faults is
slower.
TxHoldCout (per 1-10 6 This parameter indicates the number of

second) times the port transmits the CBPDU in every
second.
Priority (Port 0-240 128 l The most significant eight bits of the port
Parameters) ID indicate the port priority.
l The smaller the value of this parameter,
the higher the priority.
Port Path Cost 1-65535 - l This parameter indicates the status of the
network that the port is connected to.
l In the case of the bridges on both ends of
the path, set this parameter to the same
value.
Admin Edge Enabled, Disabled Disabled l This parameter is valid only when the
Attribute RSTP is used.
l This parameter determines whether to
set the port to an edge port. The edge port
refers to the bridge port that is connected
only to the LAN. The edge port receives
the BPDU and does not transmit the
BPDU.
l This parameter is set to Enabled only
when the Ethernet port of the Ethernet
board is directly connected to the data
communication terminal equipment,
such as a computer. In other cases, it is
value.

Protocol Enabled Enabled, Disabled Enabled l Specifies whether the STP/RSTP

protocol is enabled for the port.
l When this parameter is set to Disabled,
the BPDU cannot be processed and
transmitted.
adopts the default value.
Auto Edge Enabled, Disabled Disabled l This parameter is valid only when
Detection Admin Edge Attribute is set to
Enabled.
l When this parameter is set to Enabled,
if the bridge detects that this port is
connected to the port of other bridges,
the RSTP considers this port as a non-
edge port.
l If Admin Edge Attribute is set to
Enabled, set this parameter to
Enabled. In other cases, it is
value.
Point-to-Point Adaptive Adaptive l This parameter is valid only when the

Attribute connection, Link connection RSTP is used.
connection, Shared l If this parameter is set to Adaptive
media connection, the bridge determines the
actual point-to-point attribute of the port
according to the actual working mode of
the port. If the actual working mode of
the port is full-duplex, the actual point-
to-point attribute of the port is "true". If
the actual working mode of the port is
half-duplex, the actual point-to-point
attribute of the port is "false".
l If this parameter is set to Link
connection, the actual point-to-point
attribute of the port is "true".
l If this parameter is set to Shared
media, the actual point-to-point attribute
of the port is "false".
l Only the port whose point-to-point
attribute is "true" can transmit the rapid
transition request and response.
default value.

NOTE
l In the service networking process, it is recommended that you prevent the loop from forming in the case of
the Layer 2 service and thus avoid enabling the STP or RSTP.
l Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in
charge of maintaining the opposite Ethernet equipment and set the related parameters as instructed, before
enabling the STP or RSTP.
14.6.15 Querying the Running Information About the Spanning

Tree Protocol
The running information about the spanning tree protocol includes the bridge running
information and port running information.
Prerequisite
The STP or RSTP of the bridge must be enabled.
Precautions
Procedure
Switching Management > Spanning Tree from the Function Tree.
Step 2 Query the bridge running information.
1. Click the Bridge Running Info tab.
2. Click Query.
3. View the bridge running information.
Step 3 Query the port running information.
1. Click the Port Running Info tab.
2. Click Query.
3. View the port running information.
----End
14.6.16 Configuring the IGMP Snooping Protocol

If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP
Snooping protocol and configure the method for processing the unknown multicast packet.
Prerequisite


The VLAN filter table must be created.
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2
Switching Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Click the Protocol Enable tab.
Step 3 Set the information related to the IGMP Snooping protocol.
Step 4 Click Apply.
----End
Parameters
Protocol Enable Enabled, Disabled Disabled l This parameter determines whether to

enable the IGMP Snooping protocol.
l If the bridge accesses a LAN where the
IGMP multicast server exists, you can
enable the IGMP Snooping protocol
according to the requirement.

The Discarded Tag Enabled, Disabled Enabled l This parameter is valid only when
of the Packet Protocol Enabled is set to Enabled.
Excluded in the l If the 802.1q bridge or the 802.1ad bridge
Multicast Group receives a multicast packet whose
multicast address has no mapping item in
the multicast table (that is, this multicast
packet is an unknown multicast packet),
this parameter indicates the method for
processing this packet.
l When this parameter is set to Enabled,
The unknown multicast packet is
discarded.
l When this parameter is set to Disabled,
the unknown multicast packet is
broadcast in the VLAN.
requirement of the IGMP multicast
server.
14.6.17 Querying the Running Information About the IGMP

Snooping Protocol
The running information about the IGMP Snooping protocol includes the current multicast router
port and multicast table item.
Prerequisite
The IGMP Snooping protocol of the bridge must be enabled.
Precautions
Procedure
Step 2 Query the information about the router port.

1. Click the Multicast Router Port Management tab.
2. Click Query.

3. View the information about the router port.

Step 3 Query the information about the multicast table item.
1. Click the Multicast Table Item tab.
2. Click Query.
3. View the information about the multicast table item.
----End
14.6.18 Modifying the Aging Time of the Multicast Table Item

In the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutes
by default.
Prerequisite
The IGMP Snooping protocol of the bridge must be enabled.
Precautions
Procedure
Step 2 Click the Multicast Aging Time tab.
Step 3 Modify the aging time of the multicast table item.
Step 4 Click Apply.
----End

Parameters
Multicast Aging 1-120 8 l When a table item is not updated

Time (Min) in a certain period (that is, no
IGMP request from this
multicast address is received),
this table item is automatically
deleted. This mechanism is
called aging, and this period is
called aging time.
l If this parameter is set to a very
large value, the bridge stores
excessive multicast table items
that are outdated, which
exhausts the resources of the
multicast table.
l If this parameter is set to a very
small value, the bridge may
delete the multicast table item
that is needed, which reduces the
forwarding efficiency.
14.6.19 Querying the Multicast Router Port

The multicast router port refers to the port that transmits the IGMP query packet to routers. The
Ethernet data board considers the port that receives the IGMP query packet as the router port.
Prerequisite
l The Ethernet data board supports the IGMP Snooping protocol.
l The Ethernet LAN services must be created.
l The IGMP Snooping protocol must be enabled.
Procedure
Step 1 In the NE Explorer, select the Ethernet data board. Choose Configuration > Layer-2 Switching
Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Click the Multicast Router Port Management tab.
Step 3 Click Query to query the multicast router ports.
----End
14.6.20 Configuring the Static Multicast Table Item

You can manually specify the static multicast table item that can be forwarded to the
corresponding port in multicast mode.

Prerequisite
l The Ethernet LAN services must be created.
Procedure
Step 2 Click the Static Multicast Table tab. Click New to display the Create Static Multicast Item
dialog box.
Step 3 Configure the parameters of the static multicast item.
Step 4 Click OK or Apply.
----End
14.6.21 Querying the Multicast Table Item

You can query the multicast item that the IGMP Snooping protocol dynamically learns and the
static multicast item that is manually created.
Prerequisite
l The Ethernet LAN services must be created
Procedure
Step 2 Select the Multicast Table Item tab.
Step 3 Click Query.
----End
14.7 Configuring QoS

In legacy IP networks, all packets are processed according to the first in first out (FIFO) and
best effort strategies. This method cannot meet the requirement of the new service for the
bandwidth, delay, and delay jitter. Hence, the QoS technology is developed.

QoS refers to the ability of the communication network to ensure the expected service quality
in the aspects of bandwidth, delay, delay jitter, and packet loss ratio, and thus to ensure that the
request and response from the user or the request and response from the application meet the
expected service class.


This topic describes the basic concepts that you need to be familiar with before you use the QoS
feature.
14.7.3 Availability
The QoS feature requires the support of the applicable equipment and boards.
In the case of the 605 1F/2F Ethernet port, the broadcast packet suppression function and the
CAR function are mutually exclusive, and cannot be used at the same time.
This topic describes the flow of processing the QoS, and algorithms that are used for the CAR,
traffic shaping, and egress queue scheduling.
Plan related parameters according to the specific application of the QoS feature.
This topic describes the configuration tasks relevant to the QoS feature.
14.7.8 Configuring the Clock Sources
14.7.9 Configuring the Ethernet Clock Source

QoS refers to the ability of the communication network to ensure the expected service quality
in the aspects of bandwidth, delay, delay jitter, and packet loss ratio, and thus to ensure that the
request and response from the user or the request and response from the application meet the
expected service class.
Newly emerging services have special requirements for transmission performances such as the
bandwidth, delay, and delay jitter. The traditional network in the best effort service mode,
however, does not provide complete service capabilities. The QoS technology is developed to
solve this problem.
To support voice, video, and data services that have different service requirements, a network
must be able to differentiate communication types and thus provide relevant services.
Figure 14-77 shows, when congestion occurs on a network, how packets are transmitted through
an interface that does not support QoS.
Figure 14-77 FIFO queue

Packets to be Packets
transmitted through transmitted out
Queue
the interface of the interface
FIFO Out-of-queue
grooming
The urgency of packets decreases from left to right.

All packets to be transmitted through this interface enter the tail of the FIFO queue according
to the sequence of their arrival at the interface. The interface transmits these packets from the
head of the queue. The packets are not differentiated during the transmission, and the quality of
packet transmission is not guaranteed.
Figure 14-77 uses the PQ to support QoS packet transmission.
Figure 14-78 SP queue

Queue Priority Packets
Packets to be
Classification transmitted out
transmitted through Queue 8 Highest of the interface
the interface
Queue 7 High Out-of-queue
grooming
Queue 6 Low
...
Queue 1 Lowest
After packets arrive at the interface, the packets are classified first and then enter the tail of a
queue according to the classification. The interface transmits the packets in the queue with high
priority first, and then transmits the packets in the queue with low priority. In this way, the
packets with higher priority are always transmitted first and these packets have a short delay. In
addition, the performance specifications of these packets, including the packet loss ratio and the
delay jitter, can also be guaranteed.
The Ethernet switching board provides the following QoS functions: flow classification,
committed access rate (CAR), class of service (CoS), and traffic shaping. These functions
comply with IEEE 802.1p, RFC 2697, RFC 2698, RFC 2309, RFC 2597, and RFC 2598.

This topic describes the basic concepts that you need to be familiar with before you use the QoS
feature.
14.7.2.1 Flow Classification

Flow refers to a collection of packets with the same characteristics. In the case of the Ethernet
switching board, the flow refers to a packet collection that corresponds to the same QoS
operations. Flow classification means, according to certain rules, classifying a packet into several
flow types on which different QoS operations are performed. Flow classification is a prerequisite
and basis for the QoS operations.
14.7.2.2 CAR
CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the
rate of the traffic in a certain period (including the rate in the long term and in the short term).
The CAR sets the packet whose rate does not exceed the specified rate to high priority and
discards the packet whose rate exceeds the specified rate or downgrades this type of packet, thus
restricting the traffic into the transmission network.

14.7.2.3 CoS
By using the CoS, the packets in a flow can be scheduled to different queues of different priorities
and can be processed according to the priority of each queue. This ensures that the packets of
different priorities can be processed according to different QoS requirements.
14.7.2.4 Traffic Shaping
The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables
the packet to be transmitted at an even rate. The Ethernet switching board shapes the irregular
traffic or the traffic that does not conform to the specified traffic characteristics based on the
generic traffic shaping (GTS) technology.
14.7.2.1 Flow Classification

Flow refers to a collection of packets with the same characteristics. In the case of the Ethernet
switching board, the flow refers to a packet collection that corresponds to the same QoS
operations. Flow classification means, according to certain rules, classifying a packet into several
flow types on which different QoS operations are performed. Flow classification is a prerequisite
and basis for the QoS operations.
The flow type is based on the associated Ethernet service type of the flow. The flow types that
are supported by Ethernet switching board EMS6 are as follows:
l Port flow
The packets from a certain port are classified as a type of flow. The associated Ethernet
service of this flow type is the line service that uses this port as the service source. The
Layer 2 switching service can also be classified as a port flow.
l Port + VLAN flow
The packets that are from a certain port with a specified VLAN ID are classified as a type
of flow. The associated Ethernet service of this flow type is the line service that uses this
port + VLAN as the service source.
l Port + S-VLAN flow
The packets that are from a certain port and have a specified S-VLAN are classified as a
type of flow. The associated Ethernet service of this flow type is the EVPL service (based
on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this port + S-VLAN
as the service source.
l Port + C-VLAN + S-VLAN flow
The packets that are from a certain port and have a specified C-VLAN + S-VLAN are
classified as a type of flow. The associated Ethernet service of this flow type is the EVPL
service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this
port + C-VLAN + S-VLAN as the service source.
NOTE
IDU 605 1F/2F supports only port flow.
14.7.2.2 CAR
CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the
rate of the traffic in a certain period (including the rate in the long term and in the short term).
The CAR sets the packet whose rate does not exceed the specified rate to high priority and
discards the packet whose rate exceeds the specified rate or downgrades this type of packet, thus
The Ethernet switching board processes the flow whose CAR feature is enabled as follows:

l When the rate of packets is not more than the set committed information rate (CIR), these
packets pass the restriction of the CAR and are forwarded first even in the case of network
congestion.
l When the rate of packets exceeds the set peak information rate (PIR), the packets whose
rate is higher than the PIR are directly discarded.
l When the rate of packets is higher than the CIR but is not higher than the PIR, the packets
whose rate is higher than the CIR can pass the restriction of the CAR and are colored yellow,
which enables these packets to be discarded first in case of network congestion.
l When the rate of packets that pass the restriction of the CAR is not higher than CIR in a
certain period, certain packets can burst and these packets can be forwarded first even in
case of network congestion. The maximum traffic of burst packets is determined by the
committed burst size (CBS). The CBS contains two parts: fixed part and variable part. The
fixed part is determined by the CIR and the variable part is set on the NM.
l When the rate of the packets that pass the restriction of the CAR is higher than the CIR but
is not higher than the PIR, certain packets can burst and are marked yellow, which enables
these packets to be discarded first in case of network congestion. The maximum traffic of
burst packets is determined by the maximum burst size (MBS). The MBS contains two
parts: fixed part and variable part. The fixed part is determined by the PIR and the variable
part is set on the NM.
NOTE
The CIR and PIR of IDU 605 1F/2F must be set to be the same and the CBS and PBS cannot be set.
14.7.2.3 CoS
Each port on the Ethernet switching board EMS6 that is supported by the IDU 620 provides
eight outgoing queues with the CoS priorities from 0 to 7. If the traffic shaping feature of all the
queues is enabled or disabled, the queue with CoS priority 7 is a strict priority (SP) queue, and
the other queues with CoS priorities 0 to 6 are weighted round robin (WRR) queues. The weight
proportion of these WRR queues (with priorities from 0 to 6 respectively) is 1:2:4:8:16:32:64.
If the traffic shaping feature of certain queues is enabled, according to the preset CIR, bandwidth
is allocated first to the queue whose traffic shaping feature is enabled. By using the SP + WRR
algorithm, the remaining bandwidth is allocated to the queues whose traffic shaping is disabled.
The Ethernet port on the IFH2 board that is supported by the IDU 620 provides four outgoing
queues. The corresponding CoS priorities are 0-3 respectively and the queue scheduling mode
is SP. The higher the CoS priority, the higher the queue priority. The IFH2 board supports only
the CoS type of VLAN priority. The data frames that do not carry the VLAN tag are scheduled
to the queue with the lowest priority by default.
The Ethernet port on the IDU 605 1F/2F provides four outgoing queues. The corresponding CoS
priorities are 0-3 respectively. The higher the CoS priority, the higher the queue priority. The
queue scheduling mode is SP or WRR (the weight proportion is 1:2:4:8). These two scheduling
modes cannot be used at the same time.
Table 14-58 lists the CoS types that are supported by the equipment.

Table 14-58 CoS Type
CoS Type Description IDU 620 IDU 605 1F/2F
EMS6 IFH2
Simple If the CoS type Supports Does not Does not

of a flow is set to support support
simple, all the
packets in this
flow are directly
scheduled to a
specified
outgoing queue.
VLAN priority If the CoS type Supports Supports Supports

of a flow is set to
VLAN priority,
the packets in
this flow are
scheduled to a
specified
outgoing queue
according to
user priority in
the VLAN tag.
DSCP If the CoS type Supports Does not Supports

of a flow is set to support
differentiated
services code
point (DSCP),
the packets in
this flow are
scheduled to a
specified
outgoing queue
according to the
DSCP in the IP
tags of these
packets.
NOTE
In the case of the simple type, the maximum number of CoSs supported by the EMS6 board is 8. In the
case of the VLAN priority type, the maximum number of CoSs supported by the EMS6 board is 6. In the
case of the DSCP type, the maximum number of CoSs supported by the EMS6 board is 6.
The EMS4 board (a logical board) that is used on the IDU 605 1F/2F supports one board-level CoS.

the packet to be transmitted at an even rate. The Ethernet switching board shapes the irregular

traffic or the traffic that does not conform to the specified traffic characteristics based on the
generic traffic shaping (GTS) technology.
In the case of the port queue whose traffic shaping feature is enabled, the Ethernet switching
board processes the packets as follows before they enter the queue:
l When the rate of the packets is not more than the set CIR, these packets directly enter the
egress queue.
l When the rate of the packets is more than the set PIR, these packets enter the buffer. When
the buffer overflows, the packets are discarded.
l When the rate of the packets is more than the CIR but not more than the PIR, the packets
whose rate is more than the CIR enter the buffer of the CIR. When the buffer overflows,
these packets are marked yellow and enter the egress queue. In this case, these packets are
discarded in the case of queue congestion.
l When the rate of the packets that pass the restriction of the traffic shaping in a certain period
is not more than the CIR, certain burst packets enter the egress queue. The maximum traffic
of the burst packets is determined by the CBS. The value of the CBS is determined by the
CIR, and cannot be set.
l When the rate of the packets that pass the restriction of the traffic shaping in a certain period
is more than the CIR but not more than the PIR, certain burst packets enter the buffer of
the CIR. The maximum traffic of the burst packets is determined by the MBS. The value
of the MBS is determined by the PIR, and cannot be set.
As is evident from the preceding processing mechanism, the difference of the traffic shaping
from the CAR is as follows:
l In the processing of the CAR, the packet that does not conform to the traffic characteristics
is downgraded in priority or directly discarded.
l In the processing of the traffic shaping, the packet that does not conform to the traffic
characteristics is stored in the buffer. The packet is downgraded in priority or directly
discarded only when the buffer overflows.
14.7.3 Availability
The QoS feature requires the support of the applicable equipment and boards.
Table 14-59 Availability of the QoS Feature
Feature Applicable Board Applicable

Equipment
QoS Traffic classification EMS6, EFP6 IDU 620
EM4T IDU 605
CAR EMS6, EFP6 IDU 620
EM4T IDU 605
CoS EMS6, EFP6 IDU 620
EM4T IDU 605
IFH2 IDU 620

Feature Applicable Board Applicable

Equipment
Traffic shaping EMS6, EFP6 IDU 620

In the case of the 605 1F/2F Ethernet port, the broadcast packet suppression function and the
CAR function are mutually exclusive, and cannot be used at the same time.

This topic describes the flow of processing the QoS, and algorithms that are used for the CAR,
traffic shaping, and egress queue scheduling.
14.7.5.1 CAR
The CAR uses the dual token bucket three color marker algorithm.
The traffic shaping uses the dual token bucket three color marker algorithm that is similar to the
algorithm used by the CAR. The buffer queue, however, is added before the token bucket in the
algorithm used by the traffic shaping.
14.7.5.3 Egress Queue Scheduling
An egress guarantees the scheduling priority, probability, and bandwidth by using the shaping
and the CoS methods.
14.7.5.1 CAR
The CAR uses the dual token bucket three color marker algorithm.
Token Bucket Algorithm

Figure 14-79 shows the basic principle of the token bucket algorithm.
Figure 14-79 Basic principle of the token bucket algorithm
Tokens are placed

...
into the token bucket

Packets that need to at a specified rate Tokens
Packets that
be sent from this port leave this port
Classi-
fication
Token bucket
Packets are discarded or

processed in another way

In this algorithm, the token bucket is a container that has a certain capacity for storing tokens.
The tokens are placed into the bucket at a specified rate. When the number of tokens in the bucket
exceeds the capacity of the bucket, the number of tokens no longer increases. A token indicates
certain packet traffic. When the packets are transmitted, certain tokens are removed from the
buckets according to the length of the packet. When the number of tokens that are stored in the
token bucket cannot support the transmitting of the packets, these packets are discarded or
processed in another way. When the token bucket is filled with tokens, the packets that are
represented by these tokens can be transmitted, which allows the transmission of the burst data.
Hence, the traffic of the burst packets is determined by the capacity of the bucket.
Dual Token Bucket Three Color Marker Algorithm

Figure 14-80 shows the basic principle of the dual token bucket three color marker algorithm
that is used by the CAR.
Figure 14-80 Basic principle of the algorithm that is used by the CAR
...
...
PIR CIR
Classi-
Tp Tc
fication
This algorithm uses two token buckets Tc and Tp, and marks colors for packets according to the
situations when these packets pass the token bucket.
NOTE
In the case of the EMS6 board, the marked colors are only internal tags and do not change original priorities
of packets.
The parameters of these two token buckets are as follows:
l The packet is placed into the Tc token bucket at the rate of CIR, and the capacity of the Tc
token bucket equals the CBS.
l The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp
token bucket equals the MBS.
A packet is marked as follows:
l If a packet obtains the Tc token, this packet is marked green.

This kind of packet can pass the restriction of the CAR and is forwarded first even in the

l If a packet obtains the Tp token but does not obtain the Tc token, this packet is marked
yellow.
This kind of packet can pass the restriction of the CAR but is discarded first in the case of
network congestion.
l If a packet does not obtain the Tp token, this packet is marked red.
This kind of packet is directly discarded.

The traffic shaping uses the dual token bucket three color marker algorithm that is similar to the
algorithm used by the CAR. The buffer queue, however, is added before the token bucket in the
algorithm used by the traffic shaping.
Figure 14-81 shows the basic principle of the dual token bucket three color marker algorithm
that is used by the traffic shaping.
NOTE
In the case of the EMS6 board, the marked colors are only internal tags and do not change original priorities
of packets.
Figure 14-81 Basic principle of the algorithm that is used by the traffic shaping
...
...
PIR CIR
Tp Tp Tc Tc
buffer queue token bucket buffer queue token bucket
This algorithm uses two token buckets Tc and Tp, and places packets into different queues
according to the situations when these packets pass the token bucket.
The parameters of these two token buckets are as follows:
l The packet is placed into the Tc token bucket at the rate of CIR, and the capacity of the Tc
token bucket equals the CBS.
l The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp
token bucket equals the EBS.
A packet is placed into a queue as follows:
l If a packet obtains the Tc token, this packet is directly placed into the egress queue.
l If a packet obtains the Tp token but does not obtain the Tc token, this packet is placed into
the Tc buffer queue.

When the Tc buffer queue overflows, the overflow packet is marked yellow and then enters
the egress queue, which indicates that the packet is discarded first in the case of network
congestion.
l If a packet does not obtain the Tp token, this packet is placed into the Tp buffer queue.
When the Tp buffer queue overflows, the overflow packet is directly discarded.
14.7.5.3 Egress Queue Scheduling

An egress guarantees the scheduling priority, probability, and bandwidth by using the shaping
and the CoS methods.
Basic Concepts
Port available bandwidth: The system allocates bandwidth to a port.
l For an external Ethernet port, the port available bandwidth is determined by the working
mode of the port. For example, if the working mode of a port is 1000M full duplex, the
available bandwidth of the port is 1000 Mbit/s.
l For a VCTRUNK port, the available bandwidth is determined by the total bandwidth of
the virtual concatenation (VC) paths that is bound to the port virtual concatenation group
(VCG).
SP Queue Scheduling Algorithm

Figure 14-82 illustrates the strict-priority (SP) queue scheduling algorithm.
Figure 14-82 SP queue

Queue Priority Packets
Packets to be
transmitted through Queue 8 Highest of the interface
the interface
Queue 7 High Out-of-queue
grooming
Queue 6 Low
...
Queue 1 Lowest
The SP queue scheduling algorithm is designed for key service applications. A key service must
be processed with the highest priority when congestion occurs so that the response delay can be
shortened. This is an important feature for a key service. For example, a port provides eight
outgoing queues, which are prioritized from 7 to 0 in a descending order.
During the SP queue scheduling, packets are transmitted in a descending order of priority. When
a queue with a higher priority is empty, the packets in the queue with a lower priority can be
transmitted. In this way, if packets of key service are put into queues with high priority and
packets of non-key services (such as E-mail service) into queues with lower priority, the packets

of key service can be sent first and the packets of non-key service are sent when the data of key
service is not processed.
The disadvantage of the SP scheduling algorithm is as follows: if there are packets existing in
the queues with high priority when congestion occurs, packets in the queues with low priority
cannot be transmitted all the time.
WRR Scheduling Algorithm

Figure 14-83 illustrates the weighted round robin (WRR) scheduling algorithm.
Figure 14-83 WRR scheduling algorithm

Queue Weight Packets
Packets to be
transmitted through Queue 4 50 of the interface
the interface
Queue 3 30 Out-of-queue
grooming
Queue 2 10
Queue 1 10
The WRR scheduling algorithm divides each port into several outgoing queues and schedules
the packets in these queues in turn. This ensures that each queue obtains a certain service period.
For example, a port provides four queues. In a descending order of priority, the WRR configure
the w3, w2, w1, and w0 weights for the four queues respectively. Each weight stands for the
proportion of resources that the relevant queue can obtain from the total resources. If this port
is a 100M port and the weights of its four queues are set to 50, 30, 10, and 10 (corresponding to
w3, w2, w1, and w0 respectively) by the WRR scheduling algorithm, then a minimum of 10
Mbit/s bandwidth is guaranteed for the queue with the lowest priority. This prevents the
disadvantage that in the SP queue scheduling, packets in the queues with lower priority may fail
to obtain service for a long time.
Another advantage of WRR scheduling is that, although scheduling of multiple queues is

performed in the polling manner, time segment allocated to each queue is not fixed. That is,
when a queue is empty, the packets of the next queue are scheduled immediately. In this way,
the bandwidth resources can be fully utilized.
SP+WRR scheduling algorithm

As shown in Figure 14-84, by combining the advantages of the SP and WRR algorithms, the
SP+WRR scheduling algorithm sets one of the outgoing queues as an SP queue. In this way,
packets in this queue are always scheduled first, which ensures that the key services are processed
first. The other outgoing queues adopt the WRR scheduling algorithm so that each queue can
obtain a certain service time segment.

Figure 14-84 SP+WRR scheduling algorithm

Queues Weight
Packets that need to Packets that leave this
Queue 8 Strict priority
be sent from this port port
Classi- Queue 7 64 Egress

fication scheduling
Queue 6 32
...
Queue 1 1
Queue where packets are arranged according to

emergency level in a descending order from left to right
Use the port that supports eight outgoing queues as an example.

l Queue 8 (whose CoS value is 7) uses the SP algorithm. When there are packets existing in
this queue, these packets are transmitted first. When there is no packet existing in this queue,
the packets in other queues can be transmitted.
l Service time segment is allocated to each queue of queues 1-7 (whose CoS values 0-6
respectively) according to the weight proportions 1:2:4:8:16:32:64, and at each time
segment the packets in the corresponding queue are transmitted. If there is no packet
existing in the queue that corresponds to a time segment, this time segment is neglected
and the packets in the queue that corresponds to the next time segment are transmitted. For
example, if the port that supports four queues is used as an example and the four queues
are weighted as follows: 1:2:4:8, the WRR allocates the service time segments in the form
of cyclic sequence with a period 432443414342434.
If the traffic shaping of some queues is enabled, according to the set CIR, the bandwidth is first
allocated to the queue whose traffic shaping is enabled. By using the preceding algorithm, the
remaining bandwidth is allocated to the queue whose traffic shaping is disabled. For example,
the traffic shaping of queues 5 and 7 is enabled, the preset CIR of both queues is 10 Mbit/s, and
the total port bandwidth is 25 Mbit/s. In this case, the service time segments are allocated to
queue 5, queue 7, and the remaining queues according to the WRR algorithm in which the weight
proportion is 10:10:5. When a service time segment corresponding to the collection of the
remaining queues arrives, this service time segment is allocated to the remaining queues based
on the SP + WRR algorithms. That is, this service time segment is first allocated to queue 8, and
then is allocated to queues 1, 2, 3, 4, and 6 according to the weight proportion 1:2:4:8:32 of these
queues.
When congestion occurs on the outgoing queues, the packet that is colored yellow in the CAR
or in the traffic shaping is first discarded.

Plan related parameters according to the specific application of the QoS feature.

Prerequisite
l You must know the type and specific situation of the Ethernet service that requires the QoS
application.
l You must know the functions of the QoS feature.
Procedure
Step 1 Select the proper QoS function according to the requirement.
Adhere to the following principles when selecting the QoS function:
l First select the CAR. This can control the service traffic on the ingress side.
l In the case of the important service that requires to improve the traffic fluctuation, select the
traffic shaping function.
l If differentiated services are required for different service types or different user classes,
select the CoS function.
Step 2 Optional: Plan the CAR.
Adhere to the following principles when planning the CAR:
l Bind a CAR to a flow. Do not bind a CAR to multiple flows.
l The sum of CIRs of all the CARs that are associated with a particular PORT or VCTRUNK
should not exceed the physical bandwidth of that particular PORT or VCTRUNK.
Step 3 Optional: Plan the traffic shaping and CoS.
Adhere to the following principles when planning the traffic shaping and CoS:
l Allocate the service of low delay or the service of low delay commitment (such as the
signaling data, VoIP data, and network management protocol packet) into the queues of strict
priority.
l Allocate the service that does not require low delay or that does not provide low delay
commitment (such as the Internet service) into the WRR queue.
l The sum of CIRs of all the queues that are associated with a particular PORT or VCTRUNK
should not exceed the physical bandwidth of that particular PORT or VCTRUNK.
l Plan the parameters of the traffic shaping according to the traffic characteristics, thus
preventing the buffer from overflowing frequently.
----End

This topic describes the configuration tasks relevant to the QoS feature.
14.7.7.1 Creating a Flow
In the case of the Ethernet switching board, a flow refers to the collection of packets on which
the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR
and CoS operations.
14.7.7.2 Creating the CAR
CAR is a type of traffic policing technologies. After the flow classification, the CAR assesses
the rate of the traffic in a certain period (including in the long term and in the short term). The
CAR sets the packet whose rate does not exceed the specified rate to high priority and discards

the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus
14.7.7.3 Creating the CoS
14.7.7.4 Binding the CAR/CoS
To enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS.
14.7.7.5 Configuring the Traffic Shaping
the packets to be transmitted at an even rate.
14.7.7.6 Configuring the CoS of the IFH2 Board
The IFH2 board supports scheduling packets into different queues according to the
corresponding user priority levels in the VLAN tags.
14.7.7.7 Setting the Queue Scheduling Mode
The IDU 605 1F/2F supports the setting of the board-level queue scheduling mode of the EMS4
board (a logical board).
14.7.7.8 Creating a Flow by Using a Template
This topic describes how to create a flow by using a template. The use of a template improves
the efficiency of creating a flow.
14.7.7.9 Modifying CAR Parameters
The committed access rate (CAR) is the traffic policing technology that is used to check the
traffic rate within a specific period (a long time or short time) after the flow classification. The
CAR allocates the packets whose rates do not exceed the rate limit of the packets of higher
priority, and discards or downgrades the packets whose rates exceed the rate limit. In this process,
restriction of the service access to the transport network is realized. That is, you can adjust the
rate limit by adjusting the parameters such as the committed information rate and the peak
information rate.
14.7.7.10 Modifying CoS Parameters
The class of service (CoS) schedules packets into different priority queues and processes the
packets according to the priority levels of the specific queues. Modifying the CoS parameters
may affect the priority of the egress packets.
14.7.7.1 Creating a Flow

In the case of the Ethernet switching board, a flow refers to the collection of packets on which
the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR
and CoS operations.
Prerequisite
The associated Ethernet service must be created.

Context
This topic describes how to create a flow without a QoS template. For details of how to create
a flow by using a QoS template, see14.7.7.8 Creating a Flow by Using a Template.
Precautions
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board), which
supports the creation of port flow only.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Step 2 Click the Flow Configuration tab.
Step 3 Click New.
The New Flow dialog box is displayed.
Step 4 Set the flow parameters.
Step 5 Click OK.
----End

Parameters
Flow Type Port Flow, Port Port Flow Port flow: The packets from a certain port
+VLAN Flow, Port are classified as a type of flow. The Ethernet
+SVLAN Flow, service associated with this flow type is the
Port+CVLAN line service or Layer 2 switching service that
+SVLAN Flow uses this port as the service source.
Port+VLAN flow: The packets that are from
a certain port and have a specified VLAN
ID are classified as a type of flow. The
associated Ethernet service of this flow type
is the line service that uses this port+VLAN
as the service source.
Port+SVLAN flow: The packets that are
from a certain port and have a specified
SVLAN ID are classified as a type of flow.
The associated Ethernet service of this flow
type is the EVPL service (based on QinQ)
or EVPLAN service (based on the 802.1ad
bridge) that uses this port + S-VLAN as the
service source.
Port+CVLAN+SVLAN flow: The packets
that are from a certain port and have a
specified CVLAN+SVLAN are classified
as a type of flow. The associated Ethernet
service of this flow type is the EVPL service
(based on QinQ) or EVPLAN service (based
on the 802.1ad bridge) that uses this port +
C-VLAN + S-VLAN as the service source.
Port PORT1-PORT6, PORT1 l When the associated service is the line

VCTRUNK1- service, set this parameter to the source
VCTRUNK8 port or sink port of the associated
(EMS6) Ethernet service.
PORT1-PORT4 l When the associated service is the Layer
(EMS4) 2 switching service, set this parameter to
a mounted port of the bridge.
VLAN ID 1-4095 1 l This parameter is valid only when Flow

Type is set to Port+VLAN Flow.
l Set this parameter to the source VLAN
of the associated Ethernet service.
C-VLAN 1-4095 1 l This parameter is valid only when Flow

Type is set to Port+SVLAN+CVLAN
Flow.
l Set this parameter to the source C-
VLAN of the associated Ethernet
service.

S-VLAN 1-4095 1 l This parameter is valid only when Flow

Type is set to Port+SVLAN Flow or set
to Port+SVLAN+CVLAN Flow
l Set this parameter to the source S-VLAN
of the associated Ethernet service.
Postrequisite
After creating a flow, bind it to the corresponding CAR or CoS operation as required.
14.7.7.2 Creating the CAR

CAR is a type of traffic policing technologies. After the flow classification, the CAR assesses
the rate of the traffic in a certain period (including in the long term and in the short term). The
CAR sets the packet whose rate does not exceed the specified rate to high priority and discards
the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus
Prerequisite
Precautions
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board). In the case
of the EMS4 board, the values of the CIR and PIR should be set the same and the setting of the
CBS and MBS is not supported.
Procedure
Step 2 Click the CAR Configuration tab.
Step 3 Click New.
The New Car dialog box is displayed.
Step 4 Set the CAR parameters.

Step 5 Click OK.
----End
Parameters
CAR ID 1-65535 (EMS6) - This parameter identifies a CAR

1-1024 (a logical board operation, and is used to bind a flow
EMS4) to an associated CAR operation.
Enabled/Disabled Enabled, Disabled Disabled This parameter determines whether

to enable the CAR operation
performed on the flow bound to the
CAR.
Committed Information An integer ranging from 0 0 l When the rate of the packets is
Rate (kbit/s) to 1048576, with a step of not more than the CIR, these
64 packets pass the restriction of
the CAR and are forwarded first
even in the case of network
congestion.
l The value of this parameter
should not be more than the PIR.

Committed Burst Size 0-1024 0 When the rate of the packets that
(kbyte)a pass the restriction of the CAR is
not more than the CIR in a certain
period, certain packets can burst
and can pass the restriction of the
CAR. These packets can be
forwarded first even in the case of
network congestion. The maximum
traffic of the burst packets is
determined by the CBS. Note that
the CBS has an inherent size, and
this parameter indicates the
increment value only. The inherent
size of the CBS is determined by the
CIR. The greater the CIR, the
greater the CBS.
Peak Information Rate An integer ranging from 0 0 l When the rate of the packets is
(kbit/s)a to 1048576, with a step of more than the PIR, these packets
64 that exceed the rate restriction
are directly discarded. When the
rate of the packets is more than
the CIR but is not more than the
PIR, the packets whose rate is
more than the CIR can pass the
restriction of the CAR and are
marked yellow, which enables
these packets to be discarded
first in the case of network
congestion.
l The value of this parameter
should not be more than the
bandwidth at the port.
Maximum Burst Size 0-1024 0 When the rate of the packets that
(kbyte)a pass the restriction of the CAR is
more than the CIR but is not more
than the PIR, certain packets can
burst and are marked yellow, which
enables these packets to be
discarded first in the case of
network congestion. The maximum
traffic of the burst packets is
determined by the set MBS. Note
that the MBS has an inherent size,
and this parameter indicates the
increment value only. The inherent
size of the MBS is determined by
the PIR. The greater the PIR, the
greater the MBS.

NOTE
a: In the case of the IDU 605 1F/2F, the values of the CIR and PIR should be set the same and the setting
of the CBS and MBS is not supported.
Postrequisite
After creating the CAR, bind the flow to the corresponding CAR operation as required.
14.7.7.3 Creating the CoS

Prerequisite
Precautions
Procedure
Step 2 Click the CoS Configuration tab.
Step 3 Click New.

The New CoS dialog box is displayed.
Step 4 Set the CoS parameters.

Step 5 Click OK.
----End
Parameters
CoS ID 1-65535 1 This parameter identifies a CoS operation,

and is used to bind a flow to an associated
CoS operation.
In the case of the EMS4 board (logical
board), only one CoS can be created. When
the CoS is bound, this CoS operation is valid
for all the ports on the board.
CoS Type In the case of the - l If the CoS type of a flow is set to simple,
EMS6 board: all the packets in this flow are directly
l simple scheduled to a specified egress queue.
l VLAN priority l If the CoS type of a flow is set to VLAN
priority, the packets in this flow are
l DSCP scheduled to specified egress queues
l IPTOS according to the user priorities specified
In the case of the in the VLAN tags of these packets.
EMS4 board (a l If the CoS type of a flow is set to DSCP,
logical board), the packets in this flow are scheduled to
EM4T board: specified egress queues according to
l VLAN priority differentiated services code point
(DSCP) in the IPv6 tags of these packets.
l DSCP
l If the CoS type of a flow is set to IPTOS,
the packets in this flow are scheduled to
specified egress queues according to IP
TOS in the IPv4 tags of these packets.

CoS Priority In the case of the 0 This parameter specified which queue a
EMS6 board: 0-7 packet is scheduled to.
In the case of the In the case of the EMS6 board:
EMS4 board (a l Each port on the EMS6 board supports
logical board): 0-3 eight egress queues, and the CoS
priorities of these eight queues are from
0 to 7.
l If the traffic shaping feature of all the
queues is enabled or disabled, the queue
whose CoS priority is 7 is an SP queue,
and the other queues whose priorities are
from 0 to 6 are WRR queues. The
weighted proportion of these WRR
queues are 1:2:4:8:16:32:64 (from
l If the traffic shaping feature of certain
queues is enabled, the bandwidth is
allocated first to the queue whose traffic
shaping feature is enabled, according to
the set CIR. The remaining bandwidth is
allocated to the queues whose traffic
shaping is disabled, according to the SP
+WRR algorithm.
In the case of the EMS4 board (a logical
board):
l The Ethernet port on the EMS4 board
supports four egress queues, and the CoS
priorities of these four queues are from 0
to 3. When the CoS priority is higher, the
priority of the queue is higher.
l When the WRR algorithm is used, the
weighted proportion of the queues
whose CoS priorities are from 0-3 is
1:2:4:8.
Postrequisite
After creating the CoS, bind the flow to the corresponding CoS operation as required.
14.7.7.4 Binding the CAR/CoS

To enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS.
Prerequisite

The flow and CAR/CoS must be created.
Precautions
Procedure
Management > Flow Management.
Step 3 Bind the CAR/CoS.
Step 4 Click Apply.
----End
Parameters
Bound CAR - - This parameter indicates the CAR ID

corresponding to a CAR operation.
Different CAR IDs should be bound to
different flows, even though the parameters
of the CAR operations are the same.
Bound CoS - - This parameter indicates the CoS ID

corresponding to a CoS operation.
In the case of the EMS6 board, different CoS
IDs should be bound to different flows, even
though the parameters of the CoS operations
are the same.
In the case of the EMS4 board (logical
board), only one CoS can be created. When
the CoS is bound, this CoS operation is valid
for all the ports on the board.
14.7.7.5 Configuring the Traffic Shaping

the packets to be transmitted at an even rate.

Prerequisite
Precautions
Procedure
Management > Port Shaping Management from the Function Tree.
Step 2 In Port List, select a port.
Step 3 Set the traffic shaping information about the port queue.
Step 4 Click Apply.
----End
Parameters
Port A specific PORT or - This parameter indicates the port whose

VCTRUNK traffic is shaped.
Enabled/Disabled Enabled, Disabled Disabled l This parameter determines whether to

enable the traffic shaping of an egress
queue.
l If the traffic shaping feature of certain
queues is enabled, the bandwidth is
allocated first to the queue whose traffic
shaping feature is enabled, according to
the set CIR. The remaining bandwidth is
allocated to the queues whose traffic
shaping is disabled, according to the SP
+WRR algorithm.
CIR (kbit/s) An integer ranging 0 l When the rate of the packets is not more
from 0 to 1048574, than the CIR, these packets directly enter
with a step of 64 the egress queue.
l The value of this parameter should not
be more than the PIR.

PIR (kbit/s) An integer ranging 0 l When the rate of the packets is more than
from 0 to 1048574, the PIR, the packets that exceed the rate
with a step of 64 restriction are directly discarded. When
the rate of the packets is more than the
CIR but not more than the PIR, the
packets whose rate is more than the CIR
enter the buffer of the CIR. When the
buffer overflows, the packets are marked
yellow and enter the egress queue, which
enables these packets to be discarded
first in the case of queue congestion.
l The value of this parameter should not
be more than the bandwidth at the port.
14.7.7.6 Configuring the CoS of the IFH2 Board

The IFH2 board supports scheduling packets into different queues according to the
corresponding user priority levels in the VLAN tags.
Prerequisite
The IFH2 board must be added in the NE Panel.
Procedure
Step 1 Select the IFH2 board in the NE Explorer. Then, choose Configuration > QoS Management
> Flow Management from the Function Tree.
Step 2 Set CoS Priority for User Priority 0 in the VLAN Tag to User Priority 7 in the VLAN
Tag.
Step 3 Click Apply.
----End

Parameters
CoS Parameter User Priority 0 in the - This parameter specifies the data flows. The
VLAN Tag. User IFH2 boards supports differentiating the
Priority 1 in the data flows according to the user priority
VLAN Tag, User levels in the VLAN tags of packets.
Priority 2 in the
VLAN Tag, User
Priority 3 in the
VLAN Tag, User
Priority 4 in the
VLAN Tag, User
Priority 5 in the
VLAN Tag, User
Priority 6 in the
VLAN Tag, User
Priority 7 in the
VLAN Tag
CoS Priority 0-3 0 l This parameter specifies the queue to

which a packet should be scheduled.
l The IFH2 board supports four queues.
The corresponding CoS priority levels
that correspond to the four queues are
0-3 and the scheduling scheme is SP. The
higher the CoS priority, the higher is the
queue priority.
14.7.7.7 Setting the Queue Scheduling Mode

The IDU 605 1F/2F supports the setting of the board-level queue scheduling mode of the EMS4
board (a logical board).
Prerequisite
Procedure
Management > Board Shaping Management from the Function Tree.
Step 2 Select a board-level Queue Scheduling Mode.
Step 3 Click Apply.
----End

Parameters
Queue Scheduling WRR, SP SP l If this parameter is set to SP, the SP

Mode algorithm is used for the service
grooming on egress ports on the EMS4
board (a logical board). The higher is the
priority of the CoS corresponding to the
queue, the higher is the priority of the
queue.
l If this parameter is set to WRR, the
WRR algorithm is used for the service
grooming on egress ports on the EMS4
board (a logical board). The weight
proportion of the four queues is 1:2:4:8.
14.7.7.8 Creating a Flow by Using a Template

This topic describes how to create a flow by using a template. The use of a template improves
the efficiency of creating a flow.
Prerequisite
A QoS template must be created.
Context
When you create a flow by using a template, the CAR is automatically bound with the flow.
Procedure
Step 3 Click Quick New QoS.
Step 4 In the dialog box that is displayed, specify parameters, such as Flow Type.
Step 5 Select a QoS template that is created.

NOTE
After you modify the values of the parameters in the template and click Save Parameters, the new values
are saved to the template.
Step 6 Click OK.
----End

14.7.7.9 Modifying CAR Parameters

The committed access rate (CAR) is the traffic policing technology that is used to check the
traffic rate within a specific period (a long time or short time) after the flow classification. The
CAR allocates the packets whose rates do not exceed the rate limit of the packets of higher
priority, and discards or downgrades the packets whose rates exceed the rate limit. In this process,
restriction of the service access to the transport network is realized. That is, you can adjust the
rate limit by adjusting the parameters such as the committed information rate and the peak
information rate.
Prerequisite
The CAR must be configured.
Precautions
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board). In the case
of the EMS4 board, the values of the CIR and PIR should be set the same and the setting of the
CBS and MBS is not supported.
Procedure
QoS Management > Flow Management from the Function Tree.
Step 2 Click the CAR Configuration tab.
Step 3 Click Query.
Step 4 Select CAR ID that needs to be changed.
Step 5 Modify the other parameters that need to be modified.
Step 6 Click Apply.
----End
Parameters
For details, see 14.7.7.2 Creating the CAR.
14.7.7.10 Modifying CoS Parameters

The class of service (CoS) schedules packets into different priority queues and processes the
packets according to the priority levels of the specific queues. Modifying the CoS parameters
may affect the priority of the egress packets.

Prerequisite
The CoS must be configured.
Precautions
Procedure
QoS Management > Flow Management from the Function Tree.
Step 2 Click the CoS Configuration tab.
Step 3 Click Query.
Step 4 Select the CoS ID that needs to be changed.
Step 5 Select the CoS Parameter that needs to be changed.
Step 6 Modify CoS Priority.
Step 7 Click Apply.
----End
Parameters
For details, see 14.7.7.3 Creating the CoS.
14.7.8 Configuring the Clock Sources


Prerequisite
The PXC boards and input/output clock source boards must be configured.
Procedure
Source Priority from the Function Tree.
The Add Clock Source dialog box is displayed.
Step 3 Select the clock sources.
TIP
By pressing the Ctrl key, you can select multiple clock sources at one time.
Step 4 Click OK.

Step 5 Optional: Repeat Step 2 to Step 4 to add other clock sources.
Step 6 Optional: Select a clock source and click or to adjust the priority level of
this clock source.
The clock priority levels are arranged in the descending order from the first row to the last row.
The internal clock source is fixed with the lowest priority.
Step 7 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external
clock sources.
Step 8 Click Apply.
----End

Parameters
Clock Source - - l External clock source 1 indicates the

external clock source at the port of the
PXC board in slot 1. External clock
source 2 indicates the external clock
source at the port of the PXC board in
slot 3.
l IFH2-1(SDH) indicates the microwave
clock source.
l IFH2-2(ETH) indicates the clock source
of the synchronous Ethernet.
l The internal clock source is fixed with
the lowest priority and indicates that the
NE works in the free-run mode.
l Determine the clock sources and the
corresponding clock source priority
levels according to the clock
synchronization schemes.
External Clock 2 Mbit/s, 2 MHz 2 Mbit/s l This parameter indicates the type of the
Source Mode external clock source signal.
l Set this parameter depending on the
external clock signal. Generally, the
external clock signal is a 2 Mbit/s signal.
Synchronization SA4-SA8 SA4 l This parameter is valid only when

Status Byte External Clock Source Mode is set to
2 Mbit/s.
l This parameter need to be set only when
the SSM or extended SSM is enabled.
Generally, the external clock sources use
the SA4 to pass the SSM.
14.7.9 Configuring the Ethernet Clock Source

Prerequisite

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock Source
Step 2 Set Use the clock source of the data port.
Step 3 Click Apply.
----End
Parameters
Use the clock source Yes, No No When this parameter is set to Yes, the IDU
of the data port 605 1F/2F traces the clock source that is
recovered from the signal flow on the
Ethernet PORT.

15 Ethernet Feature(RTN 900)
About This Chapter
Displays the Ethernet feature of OptiX RTN 900 NEs.
15.1 Configuring the QoS Policy

For service of different types, configure different QoS policies to provide different QoS, and to
ensure availability of important services in the case of network congestion.
15.2 Configuring an Ethernet Service
On the U2000, you can configure an E-Lineor an E-AGGR service. The user side uses ports and
the port+VLANs mode to access Ethernet services. The network side uses PWs, QinQ Links or
physical ports to carry the accessed services. On the U2000, you can create a V-UNI group to
perform QoS settings for several Ethernet services.
15.3 Configuring Port Mirroring
You can configure port mirroring to analyze only packets for mirrored ports. In this way, you
can monitor all mirrored ports. This helps you to manage the ports.

15.1 Configuring the QoS Policy

For service of different types, configure different QoS policies to provide different QoS, and to
ensure availability of important services in the case of network congestion.
15.1.1 Overview of the QoS
The overview of the QoS describes in terms of the purposes, compliant standards and
suggestions.
Before configuring the quality of service (QoS) policy, familiar yourself with the basic concepts
related to the QoS, and the QoS polices supported by the RTN equipment.
15.1.3 Application of the QoS
The application of the QoS describes the tunnel-based QoS control and application of several
QoS policies.
15.1.4 Configuring the DiffServ Domain
As a node in the DiffServ domain, the RTN equipment can perform QoS control over the service
traffic. For this purpose, first configure a DiffServ domain for the equipment.
15.1.5 Configuring the Port Policy
The port policy should be configured to realize the QoS control over ports.
15.1.6 Creating the CAR Policy
The CAR policy is used to control the each traffic classification in the V-UNI ingress policy.
15.1.7 Configuring the V-UNI Ingress Policy
Configure the V-UNI ingress policy at the access side of the euqipment to perform the QoS
control over the ingress traffic.
15.1.8 Configuring the ATM CoS Mapping
Configure the mapping relation between the ATM service type and PHB service class to ensure
the end-to-end QoS for ATM services.
15.1.9 Configuring the ATM Policy
For ATM services, configure the ATM policy to perform the QoS control over the traffic.
15.1.1 Overview of the QoS

The overview of the QoS describes in terms of the purposes, compliant standards and
suggestions.
Purpose of the QoS

Quality of service (QoS) indicates the performance of the data flow that travels through the
network. The purpose of the QoS is to ensure the end-to-end service quality.
The QoS cannot increase the bandwidth, but can reduce the delay and jitter in the network to
the minimum by reasonably allocating and monitoring network resources. In this way, the quality
of important services is ensured.
The specifications used to measure the QoS are as follows.
l Service availability, which indicates the ensured normal running time of a service.

l Delay, which indicates the period between transmission and receiving of data packets
between two reference points.
l Jitter, which indicates the time interval difference for the receive side to receive a group of
data packets transmitted on the same route.
l Packet loss rate, which indicates the maximum ratio of discarded data packets among the
transmitted data packets in the network. Data packets are discarded mainly due to network
congestion.

RFC1349 Type of Service in the Internet Protocol Suite
RFC2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
RFC2475 An Architecture for Differentiated Services
RFC2597 Assured Forwarding PHB Group
RFC2598 An Expedited Forwarding PHB
RFC2698 A Two Rate Three Color Marker
RFC3086 Definition of Differentiated Services Per Domain Behaviors and Rules for their
Specification
RFC3140 Per Hop Behavior Identification Codes
RFC3246 An Expedited Forwarding PHB (Per-Hop Behavior)
RFC3247 Supplemental Information for the New Definition of the EF PHB (Expedited
Forwarding Per-Hop Behavior)
RFC3248 A Delay Bound alternative revision of RFC 2598
RFC3260 New Terminology and Clarifications for Diffserv
RFC3270 Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
RFC3289 Management Information Base for the Differentiated Services Architecture
RFC3290 An Informal Management Model for Diffserv Routers
RFC3317 Differentiated Services Quality of Service Policy Information Base
The ATM Forum Traffic Management Specification Version 4.1

Before configuring the quality of service (QoS) policy, familiar yourself with the basic concepts
related to the QoS, and the QoS polices supported by the RTN equipment.
15.1.2.1 DiffServ
As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended.
15.1.2.2 HQoS
When used as an edge DS node, the RTN equipment supports hierarchical QoS (HQoS).

15.1.2.1 DiffServ
As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended.
Figure 15-1 shows the application of the DiffServ model.
Figure 15-1 Networking diagram for the DiffServ model
DS node
Non-DS node DS node DS node Non-DS node
The DS (DiffServ) domain consists of a group of network nodes (DS nodes) that provide the
same service policy and realize the same PHB (per-hop behavior).
The DS nodes are classified into edge DS nodes and internal DS nodes. The edge DS nodes
classify the traffic that enters the DS domain. For the service traffic of different types, different
PHB service levels are marked. The internal DS nodes control the flow according to the PHB
service level.
As a node in the DS domain, the RTN equipment uses the following technologies to realize the
end-to-end QoS control.
Flow Classification
The RTN equipment supports two flow classifying schemes, that is, simple flow classification
and complex flow classification.
l Simple flow classification
The priorities of the accessed packets are mapped into the specified PHB service level. In
this way, when crossing the DS domain, these packets can be provided with a uniform PHB
service.
The simple flow classification is mainly used for the internal nodes in a DS domain. The
flow classifying rules of all nodes in a DS domain should be the same.
The RTN equipment can access Ethernet, IP and MPLS packets, and supports the mutual
mapping between the VLAN priority, IP DSCP, MPLS EXP and the PHB service level.
l Complex flow classification
The complex flow classification is mainly used for the edge nodes in a DS domain.
The RTN equipment can perform the complex flow classification for Ethernet and IP
packets, and thus provides more specific and more flexible flow classification for the user.
CAR Control
Committed access rate (CAR) is used at the access side of the RTN equipment to perform dual-
rate three-color management for the accessed traffic.

In normal cases, when the traffic is lower than the committed information rate (CIR), packets
are marked green and normally pass. When the traffic is higher than the CIR and lower than the
peak information rate (PIR), the packets that exceed the CIR are marked yellow and normally
pass. When the traffic exceeds the PIR, the packets that exceed the PIR are marked red and are
directly discarded.
The RTN equipment supports two colorizing modes, that is, color-blind and color-aware. The
difference between the two modes lies in that the current colors of packets should be considered
in the case of the color-aware mode. The RTN equipment supports the configuration of
processing methods for packets with different colors.
Congestion Management
When network congestion occurs or aggregates, specific packet discarding policies are used to
ensure the QoS of services of higher priorities.
Three common packet discarding policies are available.
l Tail drop policy
When the queue is full, packets that arrive latterly are discarded.
l Random early detection (RED) policy
In the case of the RED policy, when the queue reaches a certain length, packets are randomly
discarded. In this way, overall synchronization caused by the TCP slow-start mechanism
is prevented.
l Weighted random early detection (WRED) policy
In the case of the WRED, the queue length and priorities of packets (color) should be
considered for packet discarding. The user can make the configuration that packets of higher
discarding priorities, such as red packets and yellow packets, are discarded first, and these
packets are more likely to be discarded.
The RTN equipment supports the tail drop policy and the WRED policy. In addition, it supports
the configuration of discarding starting point and discarding rate of the WRED.
Queue Scheduling
In the case of congestion, the RTN equipment provides the ensured QoS for services at the higher
service level by using different queue scheduling schemes. The RTN uses two queue scheduling
schemes, that is, priority queuing (PQ) and weighted fair queuing (WFQ).
Table 15-1 lists the features and application of the two queue scheduling schemes.

Table 15-1 Scheduling and application
Schedu Basic Concept Scheduling Feature RTN Application

ling
Mode
PQ The PQ is a strict priority This queue scheduling For queues of highest

queue scheduling scheme. In scheme ensures low priorities, which
the case of the PQ, packets in delay for forwarding carry CS7, CS6 or EF
queues are scheduled strictly packets in queues of packets, use the PQ
according to the queue higher priorities. Packets scheme to schedule
priority. Only when the in queues of lower queues.
queues of higher priorities are priorities, however, may
empty, packets in queues of not be processed.
lower priorities are
transmitted.
WFQ In the case of the WFQ, This scheduling scheme For queues of higher
queues are scheduled not only ensures low priorities, which
according to the weight delay for forwarding carry AF4, AF3, AF2
allocated to each queue. packets in queues of and AF1 packets, use
Generally, more weights and higher priorities, but also the WFQ scheme to
bandwidth are allocated to ensures that packets in schedule queues.
queues of higher priorities, queues of lower priorities
and less weights and are effectively
bandwidth are allocated to processed.
queues of lower priorities.
NOTE
For queues of the lowest priorities, which carry BE packets, the QoS is not ensured. In the case of
congestion, the RTN equipment does not schedule queues that provide this service level (BE).
15.1.2.2 HQoS
When used as an edge DS node, the RTN equipment supports hierarchical QoS (HQoS).
To increase the QoS control efficiency in the network, the HQoS control is always realized at
edge nodes in the network and only simple QoS processing is performed at internal nodes in the
network.
As an edge DS node, the RTN equipment provides multi-layer QoS function points to realize
the HQoS control function.
Compared with the traditional QoS, the HQoS provided by the RTN equipment has the following
advantages.
l The hierarchical scheduling mechanism is used to realize the scheduling based on port,
service, PW or QinQ link. In this way, the QoS control granularities are further divided.
l The hierarchical flow control mechanism is used to control the traffic based on port, service,
PW or QinQ link. In this way, the service QoS can be fully controlled.
l The WFQ and WRED policies can be configured to increase the flexibility of the QoS
control.

Figure 15-2 shows where the HQoS function points are and how the QoS processing is
performed.
Figure 15-2 HQoS function points and corresponding QoS processing
Acce s s s ide Ne twork s ide
QoS function
Port V-UNI PW/QinQ Tunnel Port
point
Apply PW
Apply
policy / Control
V-UNI
Control PW tunnel
ingrees Control bandwidth bandwidth Apply
Apply policy
QoS V-UNI port
port group
ma na ge me nt policy policy
Apply bandwidth Apply
V-UNI QinQ
egrees policy
policy
Service flow
15.1.3 Application of the QoS

The application of the QoS describes the tunnel-based QoS control and application of several
QoS policies.
15.1.3.1 Tunnel-Based QoS

The RTN equipment can use the tunnel-based QoS control.
15.1.3.2 QoS Policy
For the RTN equipment, the configurable QoS policies include the port policy, V-UNI ingress
policy and ATM policy. This section briefly describes how the QoS policy is applied.
15.1.3.1 Tunnel-Based QoS

The RTN equipment can use the tunnel-based QoS control.
At the ingress or egress of a network, the RTN equipment supports the pseudo wire emulation
edge-to-edge (PWE3) function. Different services are adapted to different PWs, and then the
PWs are transmitted in the Tunnel.
One tunnel can carry the PWs of the same destination.
15.1.3.2 QoS Policy

For the RTN equipment, the configurable QoS policies include the port policy, V-UNI ingress
policy and ATM policy. This section briefly describes how the QoS policy is applied.

First the RTN equipment establishes the mapping relation between the service priority and PHB
forwarding type.
Then the RTN equipment can use the following QoS polices to realize the end-to-end QoS
control.
l Establish the port QoS policy.
l Establish the V-UNI ingress policy.
The V-UNI ingress policy is used to control the traffic based on services respectively in
the ingress directions.
l Establish the ATM policy.
The ATM policy is used to control the ATM traffic.
Table 15-2 Table for mapping relations between the RTN equipment and the supported QoS
policies
Port V-UNI V-UNI PW QINQ ATM WFQ WRED

Policy Ingres Egress Policy Policy Policy Sched Policy
s Policy uling
Policy Policy
RTN Support Not Not Not Not Suppor Support Support

910 ed support support support support ted ed ed
ed ed ed ed
RTN Support Not Not Not Not Suppor Support Support

950 ed support support support support ted ed ed
ed ed ed ed
15.1.4 Configuring the DiffServ Domain

As a node in the DiffServ domain, the RTN equipment can perform QoS control over the service
traffic. For this purpose, first configure a DiffServ domain for the equipment.
15.1.4.1 Creating a DiffServ Domain
To create a DiffServ domain, create mapping relations in the DiffServ domain, and configure
ports that use the mapping relations.
15.1.4.2 Modifying a DiffServ Domain
The RTN equipment supports modifying parameters of a created DiffServ domain.
15.1.4.3 Deleting a DiffServ Domain
A DiffServ domain not used can be deleted.
15.1.4.1 Creating a DiffServ Domain

To create a DiffServ domain, create mapping relations in the DiffServ domain, and configure
ports that use the mapping relations.
Prerequisite

l You must complete the configuration of the control plane on the RTN equipment.
Context
As a node in the DiffServ domain, the RTN equipment supports creating the DiffServ domain
according to the physical ports. Each RTN NE supports a maximum of eight DiffServ domains.
By default, there is a DiffServ domain for the RTN equipment. Before any DiffServ domain is
created, all ports belong to this default domain.
To create a DiffServ domain, perform the following operations.
l Create mapping relations in the DiffServ domain, which include the mapping relation
between the priorities of user packets in both the ingress and egress directions, and the PHB
service levels.
l Configure the physical ports that use the mapping relations, that is, add the physical ports
to this domain.
Table 15-3 lists the service quality that corresponds to the PHB service level.
Table 15-3 PHB service level and mapping PHB service quality
PHB Service PHB Service Quality
Level
BE The focus is on the reachability. The quality of forwarding services is

not required. BE is the default PHB service level. All DS nodes should
support the BE PHB.
AF1 The service traffic is allowed to exceed the specified range. For the
traffic within the specified range, forwarding quality is ensured. For
AF2 the traffic beyond the specified range, the forwarding quality is lowered
AF3 and such traffic is not simply discarded.
This PHB service level is applicable for transmission of multimedia
AF4 services.
Each AF level is further divided into three discarding priorities (color).
For example, the AF1 level is further divided into the following
discarding priorities.
l AF11, green priority. Traffic with this priority can normally pass.
l AF12, yellow priority. Packets with this priority are discarded in
the case of congestion according to requirements.
l AF13, red priority. Packets with this priority are discarded first.
EF On any conditions, traffic sent by any DS node should be at the

specified rate or higher.
CS6
The forwarding effect in a virtual lease line is then simulated. In this
CS7 way, the forwarding service of low packet loss ratio, low delay and
high bandwidth is provided. This PHB service level is applicable to
video services and VoIP services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > DiffServ
Domain Management from the Function Tree.
Step 2 Click Create. The Create DS Mapping Relation dialog box is displayed. Set the following
parameters in the dialog box.
l ID and name of the DS domain mapping relation, and mapping packet type.
l Mapping relation between priorities of ingress and egress packets, and the PHB service level.
(When no configuration is performed, the mapping relation recommended by the system is
used.)
NOTE
Regarding the DSCP priority, if the DSCP value is not within the range specified in the Ingress
Mapping Relation table, the PHB service level is BE.
l Ports that use the mapping relation.
Step 3 Click OK.
----End
15.1.4.2 Modifying a DiffServ Domain

The RTN equipment supports modifying parameters of a created DiffServ domain.
Prerequisite
Context
The default DiffServ cannot be modified or deleted.
Procedure
Step 2 Select the DiffServ domain to be modified. For a DiffServ domain, the following parameters
can be modified.

l Modify the name of the domain mapping relation, and then click Apply.
l In the Ingress Mapping Relation tab, modify the mapping relation, and then click Apply.
l In the Egress Mapping Relation tab, modify the mapping relation, and then click Apply.
l In the Apply Port tab, click Modify. In the displayed Config Ports dialog box, modify the
applied port. Then, click OK.
----End
15.1.4.3 Deleting a DiffServ Domain

A DiffServ domain not used can be deleted.
Prerequisite
Context
l To delete a DiffServ domain, first delete the ports involved in the DiffServ domain, and
then delete the mapping relations in the DiffServ domain. If the DiffServ domain contains
any port, the mapping relations cannot be successfully deleted.
l The default DiffServ cannot be deleted.
Procedure
Step 2 Select the DiffServ domain to be deleted. Click Modify in the Apply Port tab. The Config
Ports dialog box is displayed.
Step 3 All ports chosen in this domain are deleted. Click OK.
Step 4 Click Delete in the Ingress Mapping Relation tab. The Confirm dialog box is displayed, Click
OK.
----End
15.1.5 Configuring the Port Policy

The port policy should be configured to realize the QoS control over ports.
15.1.5.1 Creating the Port Policy
The traffic at the port can be controlled by configuring the port policy.
15.1.5.2 Modifying the Port Policy
The created port policy can be modified. The port policy name, CAR parameter for different
CoS, and packet discarding parameter can be modified.
15.1.5.3 Deleting the Port Policy
Delete the port policy not required. If used by a port, this policy cannot be deleted.
15.1.5.1 Creating the Port Policy

The traffic at the port can be controlled by configuring the port policy.

Prerequisite
NOTE
When a physical port is configured with both the port policy and UNI ingress policy, only the UNI ingress
policy functions. Configuring one physical port with both the port policy and UNI ingress policy is not
recommended.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Step 2 Click the Port Policy tab. Click New in the tab. The Create Port Policy dialog box is displayed.
Set the following parameters in the dialog box.
l Policy ID , Policy Name.
Step 3 In the Create Port Policy dialog box, click OK.
Step 4 Select the port policy created. Click the Applied Object tab, and then click Modify.
Step 5 In the displayed Configure Port dialog box, select the port to be applied, and then click OK.
NOTE
The OptiX RTN 910/950 supports the port policy at the ML-PPP port.
----End
Related Operation
Use the copy function to fast create a new port policy based on the created port policy. The
detailed operation is as follows:
1. In the Port Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog box,
select the policy to be copied, and then enter the new policy name. Then, click OK.
2. Modify the related parameters of the newly created policy, and then make the new policy
meet the QoS requirement.
NOTE
l For the method of modifying the port policy, see 15.1.5.2 Modifying the Port Policy.
l In the case of the copy function, the application policy of port can not be copied.
15.1.5.2 Modifying the Port Policy

The created port policy can be modified. The port policy name, CAR parameter for different
CoS, and packet discarding parameter can be modified.
Prerequisite
The policy is not applied.

Procedure
Step 2 Click the Port Policy tab. In the tab, select the port policy to be modified. The following
parameters can be modified.
l Policy name.
l Parameters of traffic classification bandwidth sharing.
l CoS parameters.
In the CoS Configuration tab, modify the traffic control parameters and packet discarding
policy, and then click Apply.
l Traffic classification rule.
Click the Traffic Classification Configuration tab.
Select the traffic classification rule to be modified, and then click Traffic Classification
Rule. In the Traffic Classification Configuration dialog box, modify the traffic
classification rule, and then click OK.
Click New. In the displayed Create Traffic Classification dialog box, configure the new
ACL rule, and then click OK.
Select the traffic classification rule to be deleted, and then click Delete.
l Applied port.
Click Applied Object tab, and then click Modify.
In the displayed Configure Port dialog box, modify the applied port, and then click
OK.
----End
15.1.5.3 Deleting the Port Policy

Delete the port policy not required. If used by a port, this policy cannot be deleted.
Prerequisite
l The policy to be deleted is not used.
Procedure
Step 2 Click the Port Policy tab. In the tab, select the port policy to be deleted.
Step 3 Click Delete.
----End
15.1.6 Creating the CAR Policy

The CAR policy is used to control the each traffic classification in the V-UNI ingress policy.

Prerequisite
Procedure
Step 2 Click the CAR Policy tab.
Step 3 Click New. The Create CAR Policy dialog box is displayed.
Step 4 Set the Policy ID, Policy Name, CAR parameters and Coloration Mode.
Step 5 Set the handing mode of the packet with different color.
Step 6 Click OK.
----End
15.1.7 Configuring the V-UNI Ingress Policy

Configure the V-UNI ingress policy at the access side of the euqipment to perform the QoS
control over the ingress traffic.
15.1.7.1 Creating the WFQ Scheduling Policy
The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues.
If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the
default template, that is, the 1:1:1:1 mode.
15.1.7.2 Creating the V-UNI Ingress Policy
Create the V-UNI ingress policy to classify the accessed traffic, and to specify the parameters
such as CoS.
15.1.7.3 Modifying the V-UNI Ingress Policy

Modify the V-UNI ingress policy that is successfully created. The policy name, CoS parameters
and traffic classification parameters.
15.1.7.4 Querying the V-UNI Ingress Policy-Applied Object
The created V-UNI ingress policy is applied to a certain service to perform the QoS control. The
RTN equipment supports querying the V-UNI ingress policy-applied objects, including service
ID and V-UNI ID.
15.1.7.5 Deleting the V-UNI Ingress Policy
Delete the V-UNI ingress policy not required. If used by a service, this policy cannot be deleted.
15.1.7.1 Creating the WFQ Scheduling Policy

The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues.
If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the
default template, that is, the 1:1:1:1 mode.
Prerequisite
Context
The default WFQ schedule policy (Policy ID: 1; Policy Name: WFQ Default Scheduling) cannot
be created, modified or deleted.
In the case of the OptiX RTN , the WFQ scheduling policy can be applied to the Port policy.
Procedure
Management > WFQ Schedule Policy from the Function Tree.
Step 2 Click New. The Create WFQ Schedule Policy dialog box is displayed. Set the following
parameters in the dialog box.
l Policy ID and name.
l AF scheduling weight.
NOTE
The total schedule weights of AF1-AF4 should not exceed 100.
Step 3 Click OK.
----End

15.1.7.2 Creating the V-UNI Ingress Policy

Create the V-UNI ingress policy to classify the accessed traffic, and to specify the parameters
such as CoS.
Procedure
ManagementV-UNI Ingress Policy from the Function Tree.
Step 2 Click New. The Create V-UNI Ingress Policy dialog box is displayed.
Step 3 Set the Policy ID and Policy Name.
Step 4 Click New. Then, configure the following attributes in the displayed Create Traffic
Classification dialog box.
Step 5 Set Traffic Classification ID, ACL Action and Logical Relation Between Matched Rules.
NOTE
In the case of OptiX RTN , the default value of ACL Action is Permit and cannot be set.
Logical Relation Between Matched Rules can be set to And or Or.
And indicates that all the traffic classification rules must be followed. Or indicates that just one traffic
classification rule need be followed.
In the case of OptiX RTN , the default value of Logical Relation Between Matched Rules is Or and
cannot be set.
Step 6 Click Add and configure the traffic classification rules. You can set more traffic classification
rules.
NOTE
In the case of OptiX RTN , the match type of the traffic classification rule can be set to CVlan ID or SVlan
ID.
Step 7 Click OK to exit the Create Traffic Classification dialog box.
Step 8 Click OK to exit the Create V-UNI Ingress Policy dialog box.
----End
Related Operation
Use the copy function to fast create a new V-UNI Ingress policy based on the created V-UNI
Ingress policy. The detailed operation is as follows:
1. In the V-UNI Ingress Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog
box, select the policy to be copied, and then enter the new policy name. Then, click OK.
2. Modify the related parameters of the newly created policy, and then make the new policy
meet the QoS requirement.
NOTE
l For the method of modifying the V-UNI ingress policy, see 15.1.7.3 Modifying the V-UNI Ingress
Policy.
l In the case of the copy function, the application information of the policy can not be copied.

15.1.7.3 Modifying the V-UNI Ingress Policy

Modify the V-UNI ingress policy that is successfully created. The policy name, CoS parameters
and traffic classification parameters.
Prerequisite
l The policy is not applied.
Procedure
Management > V-UNI Ingress Policy from the Function Tree.
Step 2 Select the V-UNI ingress policy to be modified.
Step 3 Modify the following parameters.

l Policy name.
l Applied WFQ scheduling policy.
l Traffic classification bandwidth sharing.
Step 4 Modify the CoS parameters.
In the CoS Configuration tab, modify the CoS parameters. Then, click Apply.
Step 5 Modify the traffic classification parameters.

1. Click the Traffic Classification Configuration tab.
2. Add new traffic classification.
Click New. In the displayed Create Traffic Classification dialog box, enter the new traffic
classification parameters, and then click OK.
3. Create the traffic classification parameters.
l Select the traffic classification to be modified.
l Modify ACL action, CAR parameters, and then click Apply.
l Modify traffic classification rule.
Click Traffic Classification Rule. In the displayed Traffic Classification
Configuration dialog box, add, modify or delete the traffic classification rule, and then
click OK.
l Modify the processing mode of the colorized packets.
Click Colorize. In the displayed Advanced Attributes dialog box, modify the
processing mode of the colorized packets, and then click OK.
----End
15.1.7.4 Querying the V-UNI Ingress Policy-Applied Object

The created V-UNI ingress policy is applied to a certain service to perform the QoS control. The
RTN equipment supports querying the V-UNI ingress policy-applied objects, including service
ID and V-UNI ID.

Prerequisite
l You must use the V-UNI ingress policy to a service.
Procedure
Step 2 Select the V-UNI ingress policy for the query.
Step 3 Click the Applied Object tab and click Query. Information on the service that uses this policy
is displayed.
----End
15.1.7.5 Deleting the V-UNI Ingress Policy

Delete the V-UNI ingress policy not required. If used by a service, this policy cannot be deleted.
Prerequisite
Procedure
Step 2 Select the V-UNI ingress policy to be deleted.
----End
15.1.8 Configuring the ATM CoS Mapping

Configure the mapping relation between the ATM service type and PHB service class to ensure
the end-to-end QoS for ATM services.
Prerequisite
Context
The OptiX RTN equipment supports the flexible mapping between the ATM service type and
PHB service class. Table 15-4 lists the default ATM CoS mapping relation.

Table 15-4 Mapping relation between the ATM service type and PHB service class
Service Type PHB Service Class
CBR EF
RT-VBR AF31
NRT-VBR AF21
UBR+ AF11
UBR BE
NOTE
The default ATM CoS mapping cannot be modified or deleted.
Procedure
Step 1 In the NE Explorer, click the NE and choose 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
15.1.9 Configuring the ATM Policy

For ATM services, configure the ATM policy to perform the QoS control over the traffic.

15.1.9.1 Creating the ATM Policy

Create the ATM policy to configure the service type and bandwidth for the ATM traffic.
15.1.9.2 Modifying the ATM Policy
Modify the ATM policy that is successfully created. The policy name, ATM service type and
traffic parameter can be modified.
15.1.9.3 Querying the ATM Policy-Applied Object
The created ATM policy is applied to a certain service to perform the QoS control. The RTN
equipment supports querying the ATM policy-applied objects, including the service ID, service
name, link ID and direction.
15.1.9.4 Deleting the ATM Policy
Delete the ATM policy not required. If used by a service, this policy cannot be deleted.
15.1.9.1 Creating the ATM Policy

Create the ATM policy to configure the service type and bandwidth for the ATM traffic.
Prerequisite
Procedure
Management > ATM Policy from the Function Tree.
Step 2 Click New. The Create ATM Policy dialog box is displayed. Set the following parameters in
the dialog box.
l Policy ID and name
l Service type
l Traffic parameter
l UPC/NPC

NOTE
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 RTN equipment will discards the complete AAL5 frames for the
cells.
Step 3 Click OK.
----End
15.1.9.2 Modifying the ATM Policy

Modify the ATM policy that is successfully created. The policy name, ATM service type and
traffic parameter can be modified.
Prerequisite
l The policy is not applied.
Procedure
Step 2 Click the ATM Policy tab and select the ATM policy to be modified. The following parameters
can be modified.
l Policy name.
l Service type.
l ATM traffic parameter.
l Frame discarding label.
l UPC/NPC.
Step 3 Click Apply.
----End
15.1.9.3 Querying the ATM Policy-Applied Object

The created ATM policy is applied to a certain service to perform the QoS control. The RTN
equipment supports querying the ATM policy-applied objects, including the service ID, service
name, link ID and direction.
Prerequisite
l You must use the ATM policy for a service.
Procedure

Step 2 Click the ATM Policy tab and select the ATM policy for the query.
Step 3 Click the Applied Object tab and click Query. Information on the service that uses this policy
is displayed.
----End
15.1.9.4 Deleting the ATM Policy

Delete the ATM policy not required. If used by a service, this policy cannot be deleted.
Prerequisite
Procedure
Step 2 Click the ATM Policy tab and select the ATM policy to be deleted.
----End
15.2 Configuring an Ethernet Service

On the U2000, you can configure an E-Lineor an E-AGGR service. The user side uses ports and
the port+VLANs mode to access Ethernet services. The network side uses PWs, QinQ Links or
physical ports to carry the accessed services. On the U2000, you can create a V-UNI group to
perform QoS settings for several Ethernet services.

Before configuring the Ethernet service, familiar yourself with the E-Line serviceand E-AGGR
service, and application scenarios of these services.
15.2.2 Configuring an E-Line Service(RTN 900 V100R001)
On the U2000, you can configure an E-Line service to provide a point-to-point Ethernet service.
The equipment transports packets of certain user-side ports or packets of specific VLANs in a
port to physical ports, a PW or a QinQ Link at the network side. In this way, user data packets
can be transparently transmitted in a point-to-point manner. Configuration of an E-Line service
includes creation, modification and deletion of the E-Line service.
15.2.3 Configuring an E-Line Service (RTN 900 V100R002)
port to physical ports, a QinQ Link at the network side. In this way, user data packets can be
transparently transmitted in a point-to-point manner. Configuration of an E-Line service includes
creation, modification and deletion of the E-Line service.
15.2.4 Configuring an E-LAN Service
On the U2000, the user can configure the multipoint-to-multipoint E-LAN service. The
configuration of the E-LAN service includes the service creation, modification and deletion.

15.2.5 Configuring an E-AGGR Service

On the U2000, the user can configure the multipoint-to-point E-AGGR service. The equipment
can aggregate the Ethernet data packets accessed from multiple ports to the sink node. The
configuration of the E-AGGR service includes the service creation, modification and deletion.

Before configuring the Ethernet service, familiar yourself with the E-Line serviceand E-AGGR
service, and application scenarios of these services.
15.2.1.1 E-Line Service

In the topology, the EPL service is a point-to-point service. The equipment transmits the packets
of a specific port or of specific VLANs of a specific port at the user side to a PW at the network
side. In this way, the user data can be transparently transmitted in a point-to-point manner.
15.2.1.2 E-LAN Service
In topology, the E-LAN service is a multipoint-to-multipoint service. The equipment forwards
the packets of a specific port or of specific VLANs of a specific port at the user side to multiple
ports at the network side. In this way, the user data can be transparently transmitted in a
multipoint-to-multipoint manner.
15.2.1.3 E-AGGR Service
In topology, the E-AGGR service is a multipoint-to-point service. The OptiX RTN equipment
can aggregate the services accessed from multiple ports to one UNI port or aggregate the services
accessed from multiple ports to an NNI port. In addition, the OptiX RTN equipment can
aggregate the services carried by PWs of multiple NNI ports to one UNI port.
15.2.1.1 E-Line Service

In the topology, the EPL service is a point-to-point service. The equipment transmits the packets
of a specific port or of specific VLANs of a specific port at the user side to a PW at the network
side. In this way, the user data can be transparently transmitted in a point-to-point manner.
According to the service transmission mode, the E-Line service can be classified into the
following types:
l UNI-UNI E-Line service

l UNI-NNI E-Line service carried by ports
l UNI-NNI E-Line service carried by a PW
l UNI-NNI E-Line service carried by a QinQ link
UNI-UNI E-Line Service

Figure 15-3 shows the networking diagram for the UNI-UNI E-Line service.
In City 1, Company A and Company B, connected to the RTN equipment, need communication
between each other. The communication requirement can be met by creating a UNI-UNI E-Line
service.
In this case, the equipment equals a Layer 2 switch, which only exchanges data of Company A
and Company B. In the uplink direction of the user side at the two ends, complex traffic
classification can be performed for data packets, and different QoS policies can be used
according to the traffic classification.

Figure 15-3 UNI-UNI E-Line service

PE
UNI
PE PE
A Company
Switching Network
B Company UNI
City1 PE
UNI-NNI E-Line Service Carried by Ports

Figure 15-4 shows the networking diagram for the UNI-NNI E-Line service carried by ports.
In City 1 and City 2, Company A has branches, which need communication. The communication
requirement can be met by creating a UNI-NNI E-Line service carried by ports.
In this case, each branch of Company A can exclusively use the UNI. Each physical port involved
in the E-Line service network can be exclusively used by the E-Line service. In City 1, if small
branches in Company A need service isolation, services at the same UNI can be differentiated
through "port + VLANs". For a single station, in the uplink direction of the user side, complex
traffic classification can be performed for data packets, and different QoS policies can be used
according to the traffic classification.
Figure 15-4 UNI-NNI E-Line service carried by ports
Switching Network
A Company
A Company
City2
City1
UNI NNI NNI UNI
UNI-NNI E-Line Service Carried by a PW

Figure 15-5 shows the networking diagram for the UNI-NNI E-Line service carried by a PW.
In City 1 and City 2, Company A and Company B have branches. Communication between
branches of the same company is needed, but services between the two companies need to be
isolated. In this case, the communication between branches of Company A and Company B can
be realized by creating a UNI-NNI E-Line service carried by a PW. Services between the two
companies are isolated because different services are carried by different PWs.

Hence, the company service accessed at the user side is encapsulated into a PW, and then is
carried by the Tunnel.
Different E-Line services of different companies are carried by different PWs, and then are
transmitted to the same NNI. As a result, the number of NNIs is saved, and the bandwidth
utilization is increased. In the uplink direction of the user side, the hierarchical QoS can be
performed for data packets.
Figure 15-5 UNI-NNI E-Line service carried by a PW
Package Switching
NE 1 NE2 A Company
Network
A Company
B Company
B Company City2
City1 UNI NNI NNI UNI
Tunnel
PW
UNI-NNI E-Line Service Carried by a QinQ Link

In the case of the QinQ link carrying, the packets with the C-VLAN in the user-side network
are added with an S-VLAN header of the transport network. The packets then travel through the
transport network with two VLANs. In this way, a simple L2-VPN tunnel is provided for the
user. Figure 15-6 shows the networking diagram for the UNI-NNI E-Line service carried by a
QinQ link.
Both Company A and Company B have branches in City 1 and City 2. Branches of each company
need to communicate with each other. The traffic from the two companies must be isolated. The
internal VLANs of Company A range from 1 to 100 and the internal VLANs of Company B
range from 1 to 200. In this case, you can configure a UNI-NNI E-Line service carried by a
QinQ link to meet the communication requirements. As different services are carried by QinQ
links of different values, traffic of different companies is isolated and the VLAN resources of
the packet switch network (PSN) are also saved.
In this case, different packets accessed at the user side from different companies are added with
different VLANs, and then carried by the same link at the network side.
As the E-Line services of different companies are added with one VLAN and transported to the
same port, the network-side port resources are saved and the bandwidth utilization is increased.
Also as only a small number of VLANs in the PSN are used, the VLAN resources of the network
are saved. To realize the QoS for the service carried by a QinQ link, configure the QinQ policy.

Figure 15-6 UNI-NNI E-Line service carried by a QinQ link

The internal
network of A
Company
VLAN = 1-100
A VLAN tag (VLAN = 30)
is added to the packet of
A Company
NE 1
A Company The internal
City1 Packet network of A
Switching Company
Network VLAN = 1-100
NE2
B Company
The internal network

of B Company A Company
VLAN = 1-200 A VLAN tag (VLAN = 40) City2
is added to the packet of
B Company
B Company
The internal
QinQ Link network of B
Company
VLAN = 1-200
NNI-NNI E-Line Service Carried by a QinQ Link

An NNI-NNI E-Line service is exchanged and forwarded by means of statically configured S-
VLAN tag. In the case of an end-to-end E-Line service, you need to configure tags on a per-NE
basis.
Currently, only one-layer VLANs are supported. A QinQ link is used to encapsulate or strip off
an S-VLAN on an edge port and to exchange an S-VLAN on the intermediate node.
A QinQ link adds a layer of VLAN to an accessed packet on a port in the QinQ encapsulation
mode. In this case, multiple packets with different VLANs on the user-side network are
encapsulated to an VLAN for transmission. This saves the VLAN resources on the network.

Figure 15-7 NNI-NNI E-Line service carried by a QinQ link

E-LINE A
C-VLAN1 S-VLAN1 S-VLAN3 C-VLAN1
UserA UserC
C-VLAN2 S-VLAN2 S-VLAN4 C-VLAN2

UserB UserD
E-LINE B
RTN NE
15.2.1.2 E-LAN Service

In topology, the E-LAN service is a multipoint-to-multipoint service. The equipment forwards
the packets of a specific port or of specific VLANs of a specific port at the user side to multiple
ports at the network side. In this way, the user data can be transparently transmitted in a
multipoint-to-multipoint manner.
The EPLAN services can be accessed from a minimum of two nodes. Hence, the services of
different users need not share the bandwidth. That is, in the case of EPLAN services, a bandwidth
is exclusively occupied by the service of a user and the services of different users are isolated.
In addition, the extra security scheme are not required.
There is more than one node. Hence, the nodes need to learn the MAC addresses and forward
data according to MAC addresses. Therefore, Layer 2 switching is involved.
The user side networks respectively access the carrier networks through the FE. Each user side
network has its own VLAN label. The user side networks require access between each other.
The user side networks can communicate with each other through the configuration of the E-
LAN service.
15.2.1.3 E-AGGR Service

In topology, the E-AGGR service is a multipoint-to-point service. The OptiX RTN equipment
can aggregate the services accessed from multiple ports to one UNI port or aggregate the services
accessed from multiple ports to an NNI port. In addition, the OptiX RTN equipment can
aggregate the services carried by PWs of multiple NNI ports to one UNI port.
Figure 15-8 shows the networking diagram for the E-AGGR service.
One operator wants to construct a 3G network. Services of each Node B are aggregated and
transmitted to the RNC. At each station, the service of Node B that is connected to the station
is aggregated to the PW at the network side. The Tunnel that aggregates the Node B service with
multiple stations is aggregated again at the station that connects the RNC, and then the service
is transmitted to the RNC.

Figure 15-8 E-AGGR service
FE
FE
NE 1
MPLS Tunnel 1 NE 3 RNC
GE
MPLS Tunnel 2
FE
NE 2
FE
Node B
15.2.2 Configuring an E-Line Service(RTN 900 V100R001)

port to physical ports, a PW or a QinQ Link at the network side. In this way, user data packets
can be transparently transmitted in a point-to-point manner. Configuration of an E-Line service
includes creation, modification and deletion of the E-Line service.
15.2.2.1 Configuration Flow for the E-Line Service

The E-Line service includes the UNI-UNI E-Line service, UNI-NNI E-Line service carried by
ports, UNI-NNI E-Line service carried by a PW and UNI-NNI E-Line service carried by QinQ
Link.
15.2.2.2 Creating a UNI-UNI E-Line Service
A UNI-UNI E-Line service indicates that users can be interconnected through equipment. The
Ethernet data packets do not pass the network side, but are transparently transmitted at the user
side.
15.2.2.3 Creating a UNI-NNI E-Line Service Carried by a Port
The service is accessed at the user side, and transported to one port at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. In
this way, this port is exclusively used.
15.2.2.4 Creating a UNI-NNI E-Line Service Carried by a PW

The service is accessed at the user side, and transported to one PW at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. For
such a application, create a UNI-NNI E-Line service carried by a PW.
15.2.2.5 Creating a QinQ Link
The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ
encapsulation mode. In this way, multiple VLAN packets from the user-side network are
encapsulated into a VLAN in the transport network for transport. The VLAN resources in the
transport network are saved. The E-Line service can be carried by the QinQ link at the network
side.
15.2.2.6 Creating a UNI-NNI E-Line Service Carried by the QinQ Link
The services accessed on the user side are carried by the QinQ link on the network side. Multiple
VLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transport
network. In this way, the VLAN resources in the transport network are saved.
15.2.2.7 Modifying an E-Line Service
For an E-Line service, some attributes can be modified, such as the service name, MTU, user-
side VLAN and QoS-related parameters. For the PW and QinQ Link that carries the service,
only QoS-related parameters can be modified, such as the overall bandwidth and applied policy
template.
15.2.2.8 Deleting an E-Line Service
When a user-to-network E-Line service carried by a PW is deleted, the PW is also deleted.

ports, UNI-NNI E-Line service carried by a PW and UNI-NNI E-Line service carried by QinQ
Link.
UNI-UNI E-Line service

The complete process of configuring a UNI-UNI E-Line service is shown in following table.
Table 15-5 Tasks for configuring the UNI-UNI E-Line service
Task Remarks
1. Creating To create a network, you need to create NEs, configure NE data, and
Network create fibers.
2. Configure the The QoS policy is used for traffic management of the E-Line service.
QoS Policy
3. Configure the The Ethernet interface accesses services from NodeB.

user-side
Interface
4. Configure the To configure the UNI-UNI E-Line service, you need to specify the
UNI-UNI E-Line service ID, service name and service VLan.
Service

UNI-NNI E-Line Service Carried by Ports

The complete process of configuring a UNI-NNI E-Line service carried by ports is shown in
following table.
Table 15-6 Tasks for configuring the UNI-UNI E-Line service carried by a port
Task Remarks
QoS Policy

Interface
4. Configure the To configure the UNI-NNI E-Line service, you need to specify the
UNI-NNI E-Line service ID, service name and service VLan.
Service
UNI-NNI E-Line Service Carried by PWs

The complete process of configuring a UNI-NNI E-Line service carried by PWs is shown in
following table.
Table 15-7 Tasks for configuring the UNI-NNI E-Line service carried by PWs
Task Remarks
2. Configure the Configure the LSR ID of the NE and start of global label space.
LSR ID
3. Configure the Set the general attributes and Layer 3 attributes (tunnel enable status and
network-side IP address) for interfaces to carry the tunnel carrying.
interface

Task Remarks
4. Configure the Set the protocol parameters related to the control plane to create the
control plane tunnel.
l To create a static MPLS tunnel to transmit the E-Line service, the
parameters related to the control plane need not be set.
l To create a dynamic MPLS tunnel to transmit the E-Line service, you
need to set the following protocol parameters:
1. Set the IGP-ISIS protocol parameters.
2. Set the MPLS-RSVP protocol parameters.
To create a dynamic PW to transmit the service, you need to set the
parameters related to the MPLS-LDP protocol and the IGP-ISIS
protocol.
5. Configure the A tunnel transmits the service.

Tunnel l If an static MPLS tunnel is required, configure an MPLS tunnel in
the per-NE or per-trail mode. Specify the tunnel ID, set signaling
type to static, name the service, and specify the ingress node, egress
node, and transit node.
l If a dynamic MPLS Tunnel is required, name the service, set
signaling type to dynamic, and specify the source node and sink node
for the tunnel.
QoS Policy

user-side
Interface
8. Configure the 1. Create an E-Line service: Specify the service ID, name the service,
UNI-NNI E-Line and set service VLan.
service 2. Configure a PW: Set the PW type, label, and tunnel type.
3. Configure QoS: Set the QoS of UNI and PW.
UNI-NNI E-Line Service Carried by QinQ Link

The complete process of configuring a UNI-NNI E-Line service carried by QinQ Link is shown
in following table.
Table 15-8 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link
Task Remarks
2. Configure the The E-Line policy is used for traffic management of the E-Line service.
QoS Policy

Task Remarks

Interface
4. Configure Create the QinQ link, and set the ID, board, port, S-VlAN, and QoS
QinQ Link information of the QinQ link.
The QinQ link encapsulates multiple VLAN packets to a VLAN on the
network side for transmission. This saves the VLAN resources on the
network.
5. Configure the Set the service ID, name, VLAN, and QinQ link ID.
UNI-NNI E-Line
service

side.
Prerequisite
If a port need be exclusively used, disable the DCN function of the port that carries the service.
For details, see 2.14.4.4 Enabling the Port DCN.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service
Management > E-Line Service from Function Tree.
Step 2 Click New. The dialog box is displayed.
Step 3 Set parameters in the dialog box.

NOTE
When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The
transparently transmitted service does not support configuring the alarm performance, OAM and QoS.
For Direction, select UNI-UNI.
For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANs
with ",". For example, "1,3,5,8-10".
Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed.
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding
Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line
Service dialog box is displayed.
Step 6 Click OK. A dialog box is displayed for confirmation.
----End

15.2.2.3 Creating a UNI-NNI E-Line Service Carried by a Port

The service is accessed at the user side, and transported to one port at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. In
this way, this port is exclusively used.
Prerequisite
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management
> E-Line Service from Function Tree.
Step 2 Click New. The New E-Line Service dialog box is displayed.

NOTE
l When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The
l For Direction, select UNI-NNI.
l For Bearer Type, select Port.
l For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive
VLANs with ",". For example, "1,3,5,8-10".
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding
Step 6 Click OK. A dialog box is displayed for confirmation.
----End
15.2.2.4 Creating a UNI-NNI E-Line Service Carried by a PW

The service is accessed at the user side, and transported to one PW at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. For
such a application, create a UNI-NNI E-Line service carried by a PW.
Prerequisite
You must complete the creation of the MPLS tunnel that carries PWs.
If a port need be exclusively used, disable the DCN function of the port at the UNI side. For
details, see 2.14.4.4 Enabling the Port DCN.

Procedure
> E-Line Service from Function Tree.

NOTE
l When BPDU is set to Transparently Transmitted, you cannot set VLANs. The transparently
transmitted service does not support configuring the alarm performance, OAM and QoS.
l For Direction, select UNI-NNI.
l For Bearer Type, select PW.
l For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive
VLANs with ",". For example, "1,3,5,8-10".
Step 4 Click Configure PW. The Configure PW dialog box is displayed. In the dialog box, set PW-
related parameters.
NOTE
For PW ID, select the PW ID set in Step 3.
Step 5 Click OK and close the Configure PW dialog box.
Step 6 Click Configure QoS. The Configure QoS dialog box displayed.
Step 7 In the UNItab, set Policy, Default Forwarding Priority and Default Packet Relabeling
Color for the ingress direction.
Step 8 Click the PW tab. Set EXP in the ingress direction and LSP Mode in the egress direction. Click
OK. The New E-Line Service dialog box is displayed.
Step 9 Click OK to finish the creation.
----End

side.
Prerequisite
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, click the NE and choose Configuration > Ethernet Service
Management > QinQ Link from the Function Tree.

Step 2 Click New. The New QinQ Link window is displayed.
Step 3 Set QinQ Link ID, Board, Port and S-Vlan ID.
Step 4 Click OK.
----End

Prerequisite
The QinQ link must be created for the network-side ports.
Procedure
Management > E-Line Service from the Function Tree.
Step 3 Set each parameter in the dialog box.

NOTE
l When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The
l Set Direction to UNI-NNI.
l Set Bearer Type to QinQ Link.
l Select a created QinQ link in QinQ Link ID.
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Policy, Default Forwarding
Step 6 Click OK. The Operation Result dialog box is displayed, indicating that the operation is
successful. Click Close.
----End

For an E-Line service, some attributes can be modified, such as the service name, MTU, user-
side VLAN and QoS-related parameters. For the PW and QinQ Link that carries the service,
only QoS-related parameters can be modified, such as the overall bandwidth and applied policy
template.
Prerequisite
Context
CAUTION
If you modify the E-Line service, the E-Line service may be interrupted.
Procedure
Step 1 Select the NE from NE Explorer. Choose Configuration > Ethernet Service Management >
E-Line Service from Function Tree.
Step 2 Select the E-Line service to be modified. The Service Name and MTU can be modified. After
the modification is complete, click Apply.
NOTE
After the service transmitted in a PW is created, the MTU value of the service cannot be changed. After
the service transmitted through a port or in the QinQ is created, however, the MTU value of the service
can be changed. The reason is as follows: In the case of the service transmitted in a PW, the MTU value
needs to be negotiated when the PW is created and cannot be changed after creation.
Step 3 Click the UNI tab. In the tab, you can modify VLANS of ports. After the modification is
complete, click Apply. A dialog box is displayed for confirmation, click OK.

Step 4 Click the QoS tab. The QoS-related parameters for the UNI port, PW and QinQ Link can be
modified. After the modification is complete, click Apply. A dialog box is displayed for
confirmation, click OK.
----End

When a user-to-network E-Line service carried by a PW is deleted, the PW is also deleted.
Prerequisite
Context
CAUTION
If you delete the E-Line service, the E-Line service is interrupted.
Procedure
E-Line Service from the Function Tree.
Step 2 Select the E-Line service to be deleted and click Delete. A dialog box is displayed for
confirmation. Click OK. A dialog box is displayed, indicating that the E-Line service is
successfully deleted. Click Close.
----End
15.2.3 Configuring an E-Line Service (RTN 900 V100R002)

port to physical ports, a QinQ Link at the network side. In this way, user data packets can be
transparently transmitted in a point-to-point manner. Configuration of an E-Line service includes
creation, modification and deletion of the E-Line service.

ports, NNI-NNI E-Line service carried by QinQ Link and UNI-NNI E-Line service carried by
QinQ Link.
side.

side.
For an E-Line service, some attributes can be modified, such as the service name, and user-side
VLAN.
You can delete the existing E-Line services that are not applicable.

ports, NNI-NNI E-Line service carried by QinQ Link and UNI-NNI E-Line service carried by
QinQ Link.
UNI-UNI E-Line service

The complete process of configuring a UNI-UNI E-Line service is shown in following table.
Table 15-9 Tasks for configuring the UNI-UNI E-Line service

Task Remarks
QoS Policy

user-side
Interface
4. Configure the To configure the UNI-UNI E-Line service, you need to specify the
UNI-UNI E-Line service ID, service name and service VLan.
Service
UNI-NNI E-Line Service Carried by QinQ Link

The complete process of configuring a UNI-NNI E-Line service carried by QinQ Link is shown
in following table.

Table 15-10 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link
Task Remarks
2. Configure the The E-Line policy is used for traffic management of the E-Line service.
QoS Policy

Interface
4. Configure Create the QinQ link, and set the ID, board, port, S-VlAN, and QoS
QinQ Link information of the QinQ link.
The QinQ link encapsulates multiple VLAN packets to a VLAN on the
network side for transmission. This saves the VLAN resources on the
network.
5. Configure the Set the service ID, name, VLAN, and QinQ link ID.
UNI-NNI E-Line
service

side.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service
Management > E-Line Service from Function Tree.
Step 3 Set parameters for the source and sink in the dialog box.

NOTE
l For Direction, select UNI-UNI.

l For Source VLAN and Sink VLAN, you can set several VLANs. Separate consecutive VLANs with
"-", and inconsecutive VLANs with ",". For example, "1,3,5,8-10".
Step 4 Click OK.
----End

side.
Prerequisite
be the QinQ mode.
Procedure
Step 4 Click OK.
----End


Prerequisite
The QinQ link must be created for the network-side ports.
Procedure
Management > E-Line Service from the Function Tree.
Step 3 Set parameters for the source and sink in the dialog box.
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. Click OK in the dialog box displayed.
----End

For an E-Line service, some attributes can be modified, such as the service name, and user-side
VLAN.
Prerequisite
Context
CAUTION
If you modify the E-Line service, the E-Line service may be interrupted.
Procedure
E-Line Service from Function Tree.
Step 2 Select the E-Line service to be modified. The Service Name, MTU(byte) can be modified. After
the modification is complete, click Apply.

Step 3 Click the tabs such as UNI. In these tabs, you can modify the parameters such as VLANs,
EXP of ports. After the modification is complete, click Apply. A dialog box is displayed for
confirmation, click OK.
----End

You can delete the existing E-Line services that are not applicable.
Prerequisite
Context
CAUTION
If you delete the E-Line service, the E-Line service is interrupted.
Procedure
E-Line Service from the Function Tree.
Step 2 Select the E-Line service to be deleted and click Delete. A dialog box is displayed for
confirmation. Click OK. A dialog box is displayed, indicating that the E-Line service is
successfully deleted. Click Close.
----End
15.2.4 Configuring an E-LAN Service

On the U2000, the user can configure the multipoint-to-multipoint E-LAN service. The
configuration of the E-LAN service includes the service creation, modification and deletion.
15.2.4.1 Configuration Flow for E-LAN Service

The configuration flow of the E-LAN service include creating network, configuring the QoS
policy, configuring interfaces, configuring the control plane, configuring MPLS tunnel and
configuring E-LAN service.
side.
15.2.4.3 Creating an E-LAN Service
On the U2000, the E-LAN service can be created. Multiple types of E-LAN services can be
realized by configuring the UNI and NNI ports. The NNI port or QinQ link can carry the service
by using the port.

15.2.4.4 Managing the Blacklist

Managing the blacklist can prevent the illegal packets from the network side or user side from
attacking the equipment. Hence, the equipment can run stably in the network. Managing the
blacklist includes querying the blacklist, creating the blacklist, and deleting the blacklist.
15.2.4.5 Setting the Broadcast Storm Suppression
The broadcast storm suppression function can restrain the broadcast traffic on the port that carries
the ELAN service. Hence, the bandwidth resource of the equipment can be properly used. Setting
the broadcast storm suppression function includes enabling the broadcast storm suppression and
setting the broadcast suppression threshold.
15.2.4.6 Modifying E-LAN Service
The attributes of the E-LAN service can be partially modified, including the service name, and
UNI and NNI ports used at the service access point.
15.2.4.7 Deleting E-LAN Service
If you delete the E-LAN service, the E-LAN service is interrupted. Exercise caution when you
15.2.4.1 Configuration Flow for E-LAN Service

The configuration flow of the E-LAN service include creating network, configuring the QoS
policy, configuring interfaces, configuring the control plane, configuring MPLS tunnel and
configuring E-LAN service.
Figure 15-9 shows the flow for configuring an E-LAN service.

Figure 15-9 Flow diagram for configuring the E-LAN service

Required
Start
Optional
Creating Network
Configuring the QoS

Policy
Configuring
Interfaces
Configuring E-LAN Configuring the Configuring QinQ

Service Control Plane Link
Creating a V-UNI Configuring an MPLS Configuring E-LAN

Group Tunnel Service
End Configuring E-LAN Creating a V-UNI

Service Group
Creating a V-UNI End

Group
End
The columns in the figure shows the three sub processes. From left to right, the sub systems
indicate the NNI carried by ports, NNI carried by PWs, and NNI carried by QinQ Link
respectively.
Before configuring the E-LAN service, you should complete configuring network (including 1
Creating NEs, Links, and Topology Subnets, Configuring Inband DCN, Configuring the NE
Time, 3 Configuring Clocks, and Configuring the Equipment-Level Protection), 15.1
Configuring the QoS Policy, and 8.3 Configuring Ethernet Interfaces.
Perform the following operations according to the NNI bearer type.
l In the case that the operations mentioned above are completed, when the port is set to Bearer
Type, the E-LAN service can be configured.
l When the PW is set to Bearer Type, the MPLS tunnel need be configured. See the following
contents according to the MPLS tunnel type.
When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE
basis or by using the trail function. See Creating a Static MPLS Tunnel by Using the
Trail Function and 21.2.2 Creating an MPLS Tunnel. When the static MPLS tunnel
is used, 20 Configuring the Control Plane can be skipped.

When the dynamic MPLS tunnel is used, see Creating a Dynamic MPLS Tunnel by
Using the Trail Function.
l If the network side is carried by the QinQ Link, 15.2.4.2 Creating a QinQ Link need be
complete.
When configuring the E-LAN service, see 15.2.4 Configuring an E-LAN Service.

side.
Prerequisite
be the QinQ mode.
Procedure
Step 4 Click OK.
----End
15.2.4.3 Creating an E-LAN Service

On the U2000, the E-LAN service can be created. Multiple types of E-LAN services can be
realized by configuring the UNI and NNI ports. The NNI port or QinQ link can carry the service
by using the port.
Prerequisite
You must complete the correct configuration of the port attributes.
If the port need be exclusively used, disable the DCN function of the port that carries the service.
For the operation steps, see 2.14.4.4 Enabling the Port DCN.
If the service need be carried by a QinQ link, you must configure a QinQ link first.

CAUTION
l The ML-PPP line should not carry any E-LAN service.
l On the network side, the E-LAN service does not support the LMSP, FRR, MPLS APS, and
LAG protection.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 Click New to display the New E-LAN Service dialog box. Then, set Service ID, Service
Name.
NOTE
l Self-Learning MAC Address is set to enabled. When Self-Learning MAC Address is set to enabled,
the bridge supports the MAC address self-learning, the forwarding table items are generated through
the MAC address self-learning. You can also manually configure the static MAC address forwarding
table items.
l MAC Address Learning Mode is set to IVL. IVL indicates the 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.
l Tag Type can be set to C-Awared, S-Awared or Tag Transparent. C-Awared corresponds to the
accessed service packets with one C-VLAN. S-Awared corresponds to the accessed service packets
with one C-VLAN and one S-VLAN. Tag Transparent corresponds to the accessed service packets
without any VLAN.
Step 3 Click OK to display the dialog box, which indicates that the operation is successful. Then, click
Close.
Step 4 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.
Step 5 In the Available Ports list, select the port. Then, click to add the port to the Selected
Ports list.
Step 6 In the Selected Ports list, set VLANs/CVLAN of the port, and then click OK.
Step 7 Click the NNI tab.

l If configuring the NNI interface carried by the port, click the Port tab. See Step 4 to Step
6 to add and configure the NNI port. Then, click OK.
l If configuring the NNI interface carried by the QinQ link, click the QinQ Link tab.
1. Click Add. The QinQ Link Management window is displayed.
2. Select a QinQ link ID and click OK.
3. Click Apply. The Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close,
NOTE
The services carried by the QinQ link can not support to create MP.
Step 8 Click the Split Horizon Group tab. Then, click New to display the New Split Horizon
Group dialog box.

Step 9 Configure the split horizon group id, and add the interface that need be added into the split
horizon group to the Selected Interfaces pane. Click OK to display the dialog box, which
indicates that the operation is successful. Then, 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(%).
NOTE
Address Detection Upper Threshold(%) and Address Detection Upper 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.
Step 11 Click Apply. The dialog box is displayed, indicating that the operation 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.
Step 13 Click Apply. The dialog box is displayed, indicating that the operation is successful. Click
Close.
Step 14 Optional: Click the Static MAC Address tab. Manually bind the VLAN ID, MAC Address
and Egress Interface.
NOTE
Set the VLAN ID only when MAC Address Learning Mode is set IVL.
Step 15 Optional: Click the Maintenance Association tab and the MEP Point tab. Set the OAM-related
parameters.
NOTE
Before setting OAM-related parameters, configure the MD.
----End
15.2.4.4 Managing the Blacklist

Managing the blacklist can prevent the illegal packets from the network side or user side from
attacking the equipment. Hence, the equipment can run stably in the network. Managing the
blacklist includes querying the blacklist, creating the blacklist, and deleting the blacklist.
Prerequisite
You must complete the creation of E-LAN services.
Context
After the MAC address blacklist is created on a port that carries the ELAN service, if the
destination MAC or source MAC information carried by a packet enters this port is consistent
with a random MAC address created in the blacklist, this packet is discarded.
NOTE
The MAC address that is added to the static route should not be added to the MAC address of the blacklist.

Procedure
Step 2 In the Disabled MAC Address tab page, select Query to query the added MAC address of the
blacklist.
Step 3 Click New and the Create Disabled MAC Address dialog box is displayed. Set VLAN ID and
MAC Address.
Step 4 Click OK.

Step 5 Optional: In the interface, select the information of a MAC address, and then click Delete.
Hence, the MAC address information is deleted from the blacklist.
----End
15.2.4.5 Setting the Broadcast Storm Suppression

The broadcast storm suppression function can restrain the broadcast traffic on the port that carries
the ELAN service. Hence, the bandwidth resource of the equipment can be properly used. Setting
the broadcast storm suppression function includes enabling the broadcast storm suppression and
setting the broadcast suppression threshold.
Prerequisite
You must complete the creation of E-LAN services.
Context
The broadcast suppression is enabled on a port that carries the ELAN service. In this case, when
the packets that enter this port are unknown unicast packets, unknown multicast packets, or
broadcast packets, if the traffic exceeds the broadcast suppression threshold set for the port, the
packets that exceeds the bandwidth are discarded.
NOTE
Currently, the equipment supports the broadcast suppression function for the UNI only. The broadcast
suppression function for the NNI is not supported.

Procedure
Step 2 In the UNI tab page, select the corresponding port. Double-click the Enabled Broadcast Packet
Suppression parameter field, and then select Enabled.
Step 3 Double-click the Broadcast Suppression Threshold parameter field, and then set the threshold
value.
Step 4 Click Apply.
----End
15.2.4.6 Modifying E-LAN Service

The attributes of the E-LAN service can be partially modified, including the service name, and
UNI and NNI ports used at the service access point.
Prerequisite
Context
CAUTION
If you modify the E-AN service, the E-LAN service may be interrupted.
Procedure
Step 2 Select the E-LAN service to be modified. The service name can be modified. After the
modification is complete, click Apply.
Step 3 Click the UNI tab. Select the port to be modified. Click Configuration. After the attributes are
modified, click OK to return to the UNI tab. Then, click Apply.
Step 4 Click Port in the NNI tab. Click Configuration. After the attributes are modified, click OK to
return to the NNItab. Click Apply.
----End
15.2.4.7 Deleting E-LAN Service

If you delete the E-LAN service, the E-LAN service is interrupted. Exercise caution when you
Prerequisite

Context
CAUTION
If you delete the E-LAN service, the E-LAN service is interrupted.
Procedure
Step 2 Select the E-LAN service to be deleted and click Delete. A prompt dialog box is displayed. Click
OK.
----End
15.2.5 Configuring an E-AGGR Service

On the U2000, the user can configure the multipoint-to-point E-AGGR service. The equipment
can aggregate the Ethernet data packets accessed from multiple ports to the sink node. The
configuration of the E-AGGR service includes the service creation, modification and deletion.
15.2.5.1 Configuration Flow for the E-AGGR Service

Configuring an E-AGGR service contains creating the network, and configuring the QoS policy,
interfaces, control plane, MPLS tunnel, and E-AGGR service.
15.2.5.2 Creating an E-AGGR Service
On the U2000, the creation of an E-AGGR service can be complete in one interface. The
equipment supports the multipoint-to-point service aggregation, and supports the service
aggregation from the NNI carried by multiple PWs to one UNI port.
15.2.5.3 Modifying an E-AGGR Service
The E-AGGR service supports the modification of some attributes, such as the service name,
access port at the user side, VLAN table at the user side, and QoS policy template at the service
access point.
15.2.5.4 Deleting an E-AGGR Service
When the E-AGGR service is configured, the PW that carries the service, VLAN switching table
items, and QoS and OAM parameters of the service, are configured at the same time. When the
E-AGGR service is deleted, the PW that carries the service, VLAN switching table items, and
related QoS and OAM parameters, are deleted at the same time.
15.2.5.1 Configuration Flow for the E-AGGR Service

Configuring an E-AGGR service contains creating the network, and configuring the QoS policy,
interfaces, control plane, MPLS tunnel, and E-AGGR service.
Figure 15-10 shows the flow for configuring an E-AGGR service.

Figure 15-10 Configuration flow for the E-AGGR service
Required Start
Optional
Creating Network
Configuring the QoS

Policy
Configuring
Interfaces
Configuring a UNIs-NNI Configuring the

Configuring a UNIs-UNI
E-AGGR Service for NEs Control Plane
E-AGGR Service for NEs
Configuring an MPLS
Creating a V-UNI Configuring a NNIs-UNI Tunnel
Group E-AGGR Service for NEs
Configuring a UNIs-NNI
End Creating a V-UNI E-AGGR Service for NEs
Group
End Configuring a NNIs-UNI

E-AGGR Service for NEs
Creating a V-UNI
Group
End
The columns in the figure shows the three sub processes, which are for the configuration of a
UNI-UNI E-AGGR service, the configuration of an E-AGGR service carried by ports on the
NNI side, and the configuration of an E-AGGR service carried by PWs on the NNI side from
the left to right.
Before configuring the UNI-UNI E-AGGR service, you should complete configuring network
(including 1 Creating NEs, Links, and Topology Subnets, Configuring Inband DCN,
Configuring the NE Time, 3 Configuring Clocks, and Configuring the Equipment-Level
Protection), 15.1 Configuring the QoS Policy, Configuring Interfaces, 20 Configuring the
Control Plane, and 21 Configuring an MPLS Tunnel. When configuring the E-AGGR service,
see 15.2.5 Configuring an E-AGGR Service.
When the MPLS tunnel is configured, see the following contents according to the MPLS tunnel
type.
l When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE
basis or by using the trail function. See Creating a Static MPLS Tunnel by Using the Trail
Function and 21.2.2 Creating an MPLS Tunnel.
l When the dynamic MPLS tunnel is used, see Creating a Dynamic MPLS Tunnel by Using
the Trail Function.

15.2.5.2 Creating an E-AGGR Service

On the U2000, the creation of an E-AGGR service can be complete in one interface. The
equipment supports the multipoint-to-point service aggregation, and supports the service
aggregation from the NNI carried by multiple PWs to one UNI port.
Prerequisite
You must complete the correct configuration of port attributes.
You must complete the creation of the MPLS tunnel that carries the PW.
For detail, see 2.14.4.4 Enabling the Port DCN.
Procedure
> E-AGGR Service from the Function Tree.
Step 2 Click New to display the New E-AGGR Service dialog box. Then, configure Service ID,
Service Name and MTU(byte).
Step 3 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.
Step 4 In the Available Port list, select the desired port and click to add the port to the
Selected Port list.
NOTE
The port of the E-AGGR service does not support the S-Aware attribute.
Step 5 In the Selected Port list, configure Location and VLANs of the port, and then click OK.
NOTE
Location can be set to the source end or the sink end. Multiple source ends can be set, but only one sink
end can be set. Otherwise, the E-AGGR service cannot be correctly configured.
Step 6 Click the NNI tab.

l To configure the NNI interface carried by the port, click the Port tab. When adding and
setting the port at the NNI side, see Step 3 and Step 5. Then, click OK.
l To configure the NNI interface carried by the PW, click the PW tab. Click New to set
related parameters of the PW. Then, click OK.
NOTE
l For PW Signaling Type, select Dynamic or Static. Dynamic indicates that the LDP signaling is used
to create a PW.
l For PW Type, select Ethernet or Ethernet Tagged Mode.
Step 7 Select VLAN Forwarding Table Item. Click New to display the New VLAN Forwarding
Table Item window to set the forwarding attributes. Then, click OK.
NOTE
The service is forwarded based on VLAN, and thus the forwarding attributes should be set in VLAN
Forwarding Table Item from each source interface to sink interface.

Step 8 Optional: Click Configure QoS. Set the parameters of the QoS.
l Click the UNI tab to set Default Forwarding Priority and Default Packet Relabeling
Color.
l Click the PW tab to set EXP and LSP Mode.
Step 9 Click OK to display the confirmation dialog box. Then, close the dialog box.
----End
15.2.5.3 Modifying an E-AGGR Service

The E-AGGR service supports the modification of some attributes, such as the service name,
access port at the user side, VLAN table at the user side, and QoS policy template at the service
access point.
Prerequisite
Context
CAUTION
If you modify the E-AGGR service, the E-AGGR service may be interrupted.
Procedure
Step 2 Select the E-AGGR service to modify the service name and MTU. After the modification, click
Apply.
Step 3 Click the UNI tab to select the port to be modified. Click Configuration. After the modification
of attributes, click OK to return to the UNI tab. Then, click Apply.
Step 4 Select the Port tab from the NNI tab. Click Configuration. After the modification of attributes,
click OK to return to the NNI tab. Then, click Apply.
Step 5 Click the QoS tab to modify the UNI port and QoS parameters of the PW. After the modification,
click Apply. A dialog box is displayed for confirmation, click OK.
----End
15.2.5.4 Deleting an E-AGGR Service

When the E-AGGR service is configured, the PW that carries the service, VLAN switching table
items, and QoS and OAM parameters of the service, are configured at the same time. When the
E-AGGR service is deleted, the PW that carries the service, VLAN switching table items, and
related QoS and OAM parameters, are deleted at the same time.

Prerequisite
Context
CAUTION
If you delete the E-AGGR service, the E-AGGR service is interrupted.
Procedure
Step 2 Select the E-AGGR service to be deleted and click Delete. A dialog box is displayed for
confirmation. Click OK. The Operation Result dialog box is displayed, indicating that the E-
AGGR service is successfully deleted. Click Close.
----End
15.3 Configuring Port Mirroring

You can configure port mirroring to analyze only packets for mirrored ports. In this way, you
can monitor all mirrored ports. This helps you to manage the ports.
Prerequisite
The mirror listener port should contain no Ethernet service, and has not be aggregated.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Port Mirroring from the Function
Tree.
Step 2 Click New.
Step 3 In the window is displayed, set Mirror Name, Direction, Mirror Listener Port and Listened
Port.
Step 4 Click OK.
----End

Operation Guide for RTN NE Management 16 Configuring Cross-Polarization Interference Cancellation
16 Configuring Cross-Polarization
Interference Cancellation
About This Chapter
Cross-polarization interference cancellation (XPIC) is a technology used together with co-

channel dual-polarization (CCDP). The application of the two technologies doubles the wireless
link capacity over the same channel.
16.1 Feature Description
This topic considers the application of the XPIC as an example to describe the XPIC feature.
16.2 Availability
The XPIC feature requires the support of the applicable equipment and boards.
16.3 Realization Principle
The IF boards of XPIC receive signals in the horizontal and vertical directions. The signals in
the two directions are then processed and the original signals are recovered.

16 Configuring Cross-Polarization Interference Cancellation Operation Guide for RTN NE Management

This topic considers the application of the XPIC as an example to describe the XPIC feature.
The application of the XPIC technology enables using the same channel bandwidth to transmit
service signals whose capacity is two times the capacity of application without XPIC. The
transmission of 2xSTM-1 signals in one direction of the radio link is considered as an example.
When the XPIC technology is not used, the adjacent channel alternate polarization (ACAP)
technology should be used in channel configuration. Thus, the bandwidth of two RF channels
should be used to transmit these 2xSTM-1 signals. See Figure 16-1. When the XPIC technology
is used, the bandwidth of one RF channel can transmit 2xSTM-1 signals by using the CCDP
channel configuration mode. See Figure 16-2.
Figure 16-1 Channel configuration in ACAP mode (without the application of the XPIC
technology)
Site A Site B
IDU IDU
ODU 1 ODU 1
f1 f1 f1
Service Service
H
V
Service f2 f2 f2 Service
ODU 2 ODU 2
Figure 16-2 Channel configuration in CCDP mode (with the application of the XPIC
technology)
Site A Site B
IDU IDU
ODU 1 f1 ODU 1
Service f1 f1 Service
H
V
Service f1 f1 Service
ODU 2 ODU 2
16.2 Availability
The XPIC feature requires the support of the applicable equipment and boards.
Table 16-1 Availability of the XPIC feature

IFX (all the versions) RTN 620

IFU2 RTN 910/950
EM6T/F
IFX2

The IF boards of XPIC receive signals in the horizontal and vertical directions. The signals in
the two directions are then processed and the original signals are recovered.
Figure 16-3 Realization principle of XPIC

Horizontal
polarization
XPIC module of IF board
Modem
horizontal A/D Filter Decision
Coefficient
control
Cross
interference Filter
Cross XPIC module of IFX

Filter
interference
Coefficient
control
Modem
A/D Filter Decision
vertical
Vertical
polarization
The realization principle is as follows:

1. The transmitter transmits two signals with the same frequency over a horizontal polarization
wave and a vertical polarization wave.
2. Due to XPD of the antenna and channel degradation, cross-polarization interference exists
in the signals received by the ODU and also in the IF signals transmitted from the ODU to
the IF boards of XPIC.
3. The XPIC module on the XPIC board receives the IF signal from the ODU and also the IF
signal from the other IF board of XPIC, and processes the IF signals, for example, A/D
conversion.
4. The XPIC module on the XPIC board controls the coefficient of the feed forward equalizer
filters (FFF) of the two IF signals by using the decision feedback equalizer (DFE). As a
result, after filtering and combination, the interference is cancelled in the two IF signals.


16 Configuring Cross-Polarization Interference Cancellation Operation Guide for RTN NE Management
Prerequisite
The XPIC Enabled parameter must be set to Enabled for the IF boards.
Context
l Relation with the 1+1 Protection Configuration: The two IF boards in an XPIC working
group cannot be configured into one 1+1 protection group, but the two IF boards in different
XPIC working groups can be configured into one 1+1 protection group. Therefore, the four
IF boards in two XPIC working groups can form two 1+1 protection groups.
l Relation with the N+1 Protection: Each member of an XPIC working group can work as
the working channel or the protection channel of the N+1 protection.
l Relation with the ATPC Feature: The transmit power of the two ODUs that are in an XPIC
working group should be the same if possible. Hence, each of the ATPC parameters (ATPC
enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment)
should be set to the same value for the IFX boards that are in an XPIC working group.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
Step 2 Click the XPIC tab.
Step 3 Click New.
Step 4 In the dialog displayed box, Set the parameters for the XPIC workgroup.
For RTN 600 NEs:

NOTE
l When CCDP is applied to the STM-1 microwave links, the IFX/IFX2 boards must be installed and the
XPIC function must be enabled.
l An XPIC working group must be configured to ensure that the XPIC working group is configured with
the same working mode, transmission frequency, transmit power, and ATPC attributes.
l When the used ODUs support two T/R spacings, ensure that the two ODUs of an XPIC working group
adopt the same T/R spacing.
Step 5 Click OK.
----End
Postrequisite
Generally, you do not need to configure the IF/ODU information after you configure an XPIC
workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU
Configuration tab page if the used ODU supports two T/R spacings.

Operation Guide for RTN NE Management 17 Configuring Automatic Transmit Power Control Function
17 Configuring Automatic Transmit Power

Control Function
About This Chapter
The automatic transmit power control (ATPC) function is an important function of the radio
transmission system. The ATPC function reduces the interference from a transmitter to adjacent
systems and also reduces the residual bit error rate.

The ATPC function enables the transmit power of a transmitter to automatically trace the change
of the received signal level (RSL) at the receive end within the ATPC control range.
17.2 Availability
The ATPC feature requires the support of the applicable equipment and boards.
The ATPC function uses the ATPC overhead in the microwave frame to realize.

17 Configuring Automatic Transmit Power Control Function Operation Guide for RTN NE Management

The ATPC function enables the transmit power of a transmitter to automatically trace the change
of the received signal level (RSL) at the receive end within the ATPC control range.
Functions and Performance of ATPC

When the ATPC function is enabled, the following two cases are possible:
l If the RSL at the receive end is lower than the preset ATPC lower threshold, the receiver
notifies the transmitter to increase the transmit power according to the preset ATPC
adjustment step at the transmit end until the RSL is higher than the ATPC lower threshold.
l If the RSL at the receive end is higher than the preset ATPC upper threshold, the receiver
notifies the transmitter to decrease the transmit power according to the preset ATPC
adjustment step at the transmit end until the RSL is lower than the ATPC upper threshold.
Table 17-1 provides the ATPC performance of the OptiX RTN 600.
Table 17-1 ATPC performance

ATPC Control Range Value Range of ATPC Adjustment
the ATPC Speed (dB/s)
Lower Threshold Upper Threshold Adjustment Step
(dBm) (dBm) (dB)
-6 (SP ODU series) Rated maximum 1 to 5 10 (when the

Rated minimum transmit power + 1.5 adjustment step is set
transmit power (HP/ dB (SP ODU series) to 1 dB)
SPA/LP ODU series) Rated maximum 20 (when the
transmit power (HP/ adjustment step is set
SPA/LP ODU series) to 2 dB)
30 (when the
adjustment step is set
to a value, which
ranges from 3 dB to 5
dB)
Automatic ATPC Threshold Setting

The functions of the automatic ATPC threshold setting are as follows:
l When the automatic ATPC threshold setting is enabled, the ATPC lower threshold and the
ATPC upper threshold that are manually set do not take effect. The equipment uses the
preset ATPC lower threshold and ATPC upper threshold according to the IF work mode.
l When the automatic ATPC threshold setting is disabled, the ATPC lower threshold and the
ATPC upper threshold that are manually set are used.

17.2 Availability
The ATPC feature requires the support of the applicable equipment and boards.
Table 17-2 Availability of the ATPC feature

- RTN 605
IF1A/IF1B (all the versions) RTN 610/620
IF0A/IF0B (all the versions)
IFX (all the versions) RTN 620
IFH2 (all the versions)
Table 17-3 Availability of the ATPC feature

IF1
IFU2 RTN 910/950
IFX2

The ATPC function uses the ATPC overhead in the microwave frame to realize.

Figure 17-1 ATPC realization principle

Transmitter Receiver
RSL out of ATPC

adjustment range
Microwave frame (ATPC overhead
indicates to adjust the transmit power)
Adjust the ODU power

once according to the
ATPC adjustment step

indicates to adjust the transmit power)
Adjust the ODU power

once according to the
ATPC adjustment step

RSL within ATPC
adjustment range
indicates not to adjust the transmit power)
Does not adjust the

ODU power

The realization principle is as follows:

1. The receiver detects the RSL.
2. After the ATPC function is enabled, when the RSL is lower than the lower ATPC threshold
or higher than the upper ATPC threshold, the receiver sets the ATPC overhead in the
microwave frame to be sent to the transmitter, to indicate an increase or decrease in the
transmit power.
NOTE
To prevent continuous adjustment to ODU power at the transmit end from occupying a large number of
resources, the receiver does not set the ATPC overhead in each microwave frame to indicate an increase
or decrease in the transmit power. Instead, the receiver sets the ATPC overhead every several microwave
frames.
3. The transmitter detects the ATPC overhead in the received microwave frame.
4. When the transmitter detects that the ATPC overhead in a microwave frame indicates an
increase or decrease in the transmit power, the transmitter increases or decreases the
transmit power of the ODU according to the preset ATPC adjustment step.
5. When the receiver detects that the RSL is within the ATPC adjustment range, the receiver
sets the ATPC overhead in the microwave frame again to make the ATPC overhead indicate
not to adjust the transmit power.

6. When the transmitter does not detect the ATPC overhead that indicates an increase or
decrease in the transmit power, the transmitter does not change the transmit power of the
ODU.

Prerequisite
The related IF board must be added.
Precautions
l In the case of the IF boards that are configured with the 1+1 protection, set only the ATPC
attributes of the main IF board.
l The following procedure describes the configuration of ATPC parameters in the IF interface
configuration dialog box of the IF board. You can also set ATPC parameters in the following
configuration dialog boxes:
Create an XPIC working group
IF/ODU configuration
l In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be
modified.
l The transmit power of the two ODUs that are in an XPIC working group should be the
same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper
threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value
for the IF boards that are in an XPIC working group.
l In the case of the Hybrid microwave, the AM switching is controlled through detection of
the change in the ATPC information and returned microwave message.
Procedure
1. Select the IF board from the Object Tree in the NE Explorer. Choose Configuration > IF
2. Click the ATPC Attributes tab.
3. Set the ATPC attributes.
NOTE
The IF0 board of the RTN 605 does not support the ATPC Automatic Threshold Enable Status.
4. Click Apply.

Step 2 In the case of RTN 900 V1R1 NEs, see Configuring the IF Attributes of Microwave
Interfaces to take the details of configuration.
----End
Parameters
ATPC Enable Status Enabled, Disabled Disabled l This parameter specifies whether the
function enables the transmit power of a
transmitter to automatically trace the
change of the received signal level
(RSL) at the receive end within the
ATPC control range.
l In the case of areas where fast fading is
severe, it is recommended that you set
ATPC Upper -20 to -75 -45 l When the ATPC function is enabled, if
Threshold (dBm) the RSL at the receive end is higher than
the preset ATPC upper threshold at the
receive end, the receiver notifies the
transmitter to decrease the transmit
power according to the preset ATPC
adjustment step at the transmit end until
the RSL is lower than the ATPC upper
threshold.
l Generally, ATPC Upper Threshold
(dBm) should be 20 dB to 30 dB higher
than ATPC Lower Threshold (dBm),
and must not be less than 15 dB. If the
difference between the upper threshold
and the lower threshold is big, the
number of ATPC adjustments is reduced
and the system load is also reduced. If
the difference between the upper
threshold and the lower threshold is
small, the transmit power is adjusted in
a timely manner and the interference to
adjacent systems is reduced.

ATPC Lower -35 to -90 -70 l When the ATPC function is enabled, if
Threshold (dBm) the RSL at the receive end is lower than
the preset ATPC lower threshold, the
receiver notifies the transmitter to
increase the transmit power according to
the preset ATPC adjustment step at the
transmit end until the RSL is higher than
the ATPC lower threshold.
l Generally, set this parameter to a value
of 10 dB or greater than the receiver
sensitivity to prevent sudden fast fading
because sudden fast fading makes the
RSL value lower than the receiver
sensitivity.
ATPC control range.
l The IF0 board of the RTN 605 does not
support the ATPC Automatic

NOTE
l Set ATPC parameters consistent at the two sides of a hop of microwave link.
l During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not
changed. After the commissioning, re-set the ATPC attributes.
l It is recommended that you disable the ATPC function for areas where fast fading is severe.
l To prevent that the RSL is lower than the receiver sensitivity caused by sudden fast fading, set the ATPC
lower threshold 10 dB or more higher than the receiver sensitivity.
l Generally, the ATPC upper threshold should be 20 dB to 30 dB higher than the ATPC lower threshold, and
must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big,
the number of ATPC adjustments can be reduced and the system load can also be reduced. If the difference
between the upper threshold and the lower threshold is small, the transmit power can be adjusted in a timely
manner and the interference to adjacent systems can be reduced.
l It is recommended that you set the ATPC adjustment step to 5 dB.
l In the case of hybrid radio links, the automatic ATPC threshold is recommended. In the case of SDH/PDH
radio links, the automatic ATPC threshold is recommended or you can make adjustment according to
multipath fading situation.

Operation Guide for RTN NE Management 18 Configuring Hybrid Microwave
18 Configuring Hybrid Microwave
About This Chapter
The Hybrid microwave refers to the microwave that transmits E1 services and Ethernet services.

This topic describes the application of the Hybrid microwave feature.
18.2 Basic Concepts
This topic describes the basic concepts you need to be familiar with before you use the Hybrid
microwave feature.
18.3 Availability
The Hybrid microwave feature requires the support of the applicable equipment and boards.
This topic describes the principle of the AM switching of the hybrid microwave.
18.5 Configuration Guide
This topic describes how to configure hybrid microwave.

18 Configuring Hybrid Microwave Operation Guide for RTN NE Management

This topic describes the application of the Hybrid microwave feature.
Figure 18-1 shows the functional block diagram of the Hybrid microwave feature. E1 services
and Ethernet services are multiplexed into Hybrid microwave frames at the local MUX unit.
Then, the Hybrid frames are transmitted to the opposite end by the transmitter after being
modulated by the MODEM unit. After the receiver at the opposite end receives the signals, the
MODEM unit at the opposite end demodulates the signals into Hybrid microwave frames, which
are finally separated into E1 services and Ethernet services by the DEMUX unit.
Figure 18-1 Application of the Hybrid microwave feature
Ethernet E1 OH Ethernet E1 OH
E1 E1
Microwave Microwave
frame frame
MUX MODEM Transmitter Receiver MODEM DMUX
Ethernet Ethernet
OH: Overheads of the Hybrid microwave frame
The Hybrid microwave feature of the OptiX RTN realizes optimization for service reliability
and service capacity by using technologies such as combined transmission of E1 services and
Ethernet services, adaptive modulation (AM), and Ethernet QoS control.
18.2 Basic Concepts

This topic describes the basic concepts you need to be familiar with before you use the Hybrid
microwave feature.
18.2.1 Service Transmission Mode

In the case of the Hybrid microwave, different Hybrid microwave frames are defined for different
work modes. The accessed E1 services and Ethernet services are multiplexed into one Hybrid
microwave frame.
18.2.2 AM
The Hybrid microwave supports the AM technology. With the application of the AM technology,
the Hybrid microwave uses the high-efficiency modulation scheme when the channel is of better
quality. Hence, more user services can be transmitted and thus the transmission efficiency and
spectrum utilization are improved. When the quality of the channel is degraded, the Hybrid
microwave uses the low-efficiency modulation scheme, in which only the services of a high
priority are transmitted. Hence, the anti-interference capability of links is enhanced and
availability of the links on which the high-priority services are transmitted is ensured.
18.2.3 Working Mode
When the AM function is enabled for the Hybrid microwave, the Hybrid microwave can select
the best working mode from the working modes that are already set by the user according to the

condition of the channel. When the AM function is disabled, the Hybrid microwave uses the
working mode that is set by the user.
18.2.4 QoS Control for Ethernet Services
The Hybrid microwave provides various functions to ensure that Ethernet services can meet the
requirements of variable transmission bandwidth due to the application of the AM technology,
and thus to ensure the QoS of services.
18.2.1 Service Transmission Mode

In the case of the Hybrid microwave, different Hybrid microwave frames are defined for different
work modes. The accessed E1 services and Ethernet services are multiplexed into one Hybrid
microwave frame.
The characteristics of the Hybrid microwave frame are as follows:
l The Hybrid microwave frame is transmitted at a fixed interval.
l The Hybrid microwave frame remains the frame length unchanged in the case of a certain
modulation scheme or bandwidth.
l The E1 services that are multiplexed into the Hybrid microwave frame use a certain
proportion of the bandwidth of this Hybrid microwave frame. That is, the bandwidth used
by these E1 services in the Hybrid microwave frame is equal to the total bandwidth of these
E1 services. Hence, characteristics of these E1 services transmitted over Hybrid microwave
frames are the same as the characteristics of the E1 services transmitted over PDH
microwave, and the TDM feature of the E1 services is not affected in the case of Hybrid
microwave transmission.
l The Ethernet services that are multiplexed into the Hybrid microwave frame use the
remaining bandwidth of this Hybrid microwave frame. This does not affect the Ethernet
services because the Ethernet frames undergo certain encapsulation and adaptation
processes. See Figure 18-2.
Figure 18-2 Multiplexing E1 services and Ethernet services into the Hybrid microwave frame
T
OH E1 E1 Ethernet
Features of Hybrid Microwave Service Access

l In the case of E1 services: The equipment accesses E1 services through the E1 service
interface board, SDH/PDH service interface board, microwave IF board, and the E1 service
interface unit in the other directions.
l In the case of Ethernet services: The equipment accesses Ethernet services through the FE
interface or GE interface of the Ethernet board, the GE interface of the IF board, or through
the Ethernet interface of the equipment.
18.2.2 AM
The Hybrid microwave supports the AM technology. With the application of the AM technology,
the Hybrid microwave uses the high-efficiency modulation scheme when the channel is of better
quality. Hence, more user services can be transmitted and thus the transmission efficiency and

spectrum utilization are improved. When the quality of the channel is degraded, the Hybrid
microwave uses the low-efficiency modulation scheme, in which only the services of a high
priority are transmitted. Hence, the anti-interference capability of links is enhanced and
availability of the links on which the high-priority services are transmitted is ensured.
E1 services are of the highest priority in the AM-based Hybrid microwave transmission. Ethernet
services are classified into flows of different priorities based on the CoS technology. When the
Hybrid microwave uses the lowest-efficiency modulation scheme, the equipment transmits E1
services only (if the service bandwidth is higher than the total bandwidth of the E1 services, the
Ethernet services of a high priority can be transmitted). When the Hybrid microwave uses other
modulation schemes, the increased bandwidth can be used to transmit Ethernet services. In this
case, availability of the links on which the E1 services and Ethernet services of a high priority
are transmitted can be ensured and the capacity for transmitting Ethernet services increases.
Figure 18-3 shows the working principle of the Hybrid microwave that uses the AM technology.
Figure 18-3 Working principle of the Hybrid microwave
256QAM
QPSK
16QAM
64QAM
128QAM
256QAM
Channel
capability
E1 services
Ethernet
services
Figure 18-3 shows the transmission mode of the Hybrid microwave. The orange column
represents E1 services, and the blue column represents Ethernet services. When an Ethernet
service is nearer the edge of the column, the priority of this Ethernet service is lower. As shown
in Figure 18-3, the E1 services use a constant bandwidth irrespective of the real-time condition
of the channel. Hence, the availability of E1 services is ensured. The bandwidth of the Ethernet
services is variable depending on the condition of the channel. When the quality of the channel
is degraded, the Ethernet services of a low priority are discarded.
NOTE
When only the Ethernet services are transmitted over the Hybrid microwave, the bandwidth originally used
by the E1 services as shown in Figure 18-3 is allocated to the Ethernet services of a high priority.
The features of the AM function are as follows:

1. The AM function switches the modulation scheme step by step. The highest-efficiency
modulation scheme and lowest-efficiency modulation scheme can be configured.

2. The AM function retains the transmit frequency, receive frequency, and channel spacing
when switching the modulation scheme.
3. AM Mode is Asymmetric, an AM switching in one direction of the radio link does not
trigger the AM switching in the other direction of the radio link.
18.2.3 Working Mode

When the AM function is enabled for the Hybrid microwave, the Hybrid microwave can select
the best working mode from the working modes that are already set by the user according to the
condition of the channel. When the AM function is disabled, the Hybrid microwave uses the
working mode that is set by the user.
Radio Work Mode
Table 18-1 Radio work modes in the case of hybrid microwave frames
Channel Spacing Service Capacity Maximum Number

(MHz)a, b Modulation Scheme (Mbit/s) of E1s in servicec
7 QPSK 10 5
7 16QAM 20 10
7 32QAM 25 12
7 64QAM 32 15
7 128QAM 38 18
7 256QAM 44 21
14 (13.75) QPSK 20 10
14 (13.75) 16QAM 42 20
14 (13.75) 32QAM 51 24
14 (13.75) 64QAM 66 31
14 (13.75) 128QAM 78 37
14 (13.75) 256QAM 90 43
28 (27.5) QPSK 42 20
28 (27.5) 16QAM 84 40
28 (27.5) 32QAM 105 50
28 (27.5) 64QAM 133 64
28 (27.5) 128QAM 158 75
28 (27.5) 256QAM 183 75
56 QPSK 84 40
56 16QAM 168 75

56 32QAM 208 75
56 64QAM 265 75
56 128QAM 313 75
56 256QAM 363 75
40d 64QAM - 75
NOTE
1. The channel spacings 13.75 MHz and 27.5 MHz are applied to the 18 GHz frequency band.
2. The channel spacings listed in the table are the minimum channel spacings supported. The channel spacings
larger than the values are also supported.
3. The E1 services consume the corresponding bandwidth of the service capacity. After the E1 service capacity
is deducted from the service capacity, the remaining bandwidth of the service capacity can be used for the
Ethernet services.
4. This modes are the super PDH modes that do not support the transmission of Ethernet services.
18.2.4 QoS Control for Ethernet Services

The Hybrid microwave provides various functions to ensure that Ethernet services can meet the
requirements of variable transmission bandwidth due to the application of the AM technology,
and thus to ensure the QoS of services.
The AM function of the Hybrid microwave is related to the QoS processing for services. In the
case of an AM switching, services should be processed according to different QoS levels and
services of higher priority should lose any packet.
QoS Control of the OptiX RTN 620

In the case of the QoS control implemented by the OptiX RTN 620, two cases are available.
When only the IFH2 board is used, the QoS control of the IDU 620 supports the following
functions:
l Flow classification that complies with IEEE 802.1p.
l Four-level priority SP queue scheduling
When the EMS6 and IFH2 boards are used, the QoS control of the OptiX RTN 620 supports the
following functions in addition to the functions that are supported when only the IFH2 board is
used:
l Flow classification
The following flow classification modes are supported.
Flow classification based on PORT
Flow classification based on PORT+CVLAN
Flow classification based on PORT+SVLAN
Flow classification based on PORT+CVLAN+SVLAN
l CAR based on the flow
l CoS based on the flow

l Traffic shaping based on PORT

When the bandwidth on the air interface of the OptiX RTN 620 changes, the EMS6 is informed
of this change through the in-band packet so that the EMS6 can control the bandwidth on the
port.
NOTE
For details about the Ethernet QoS, see 14.7 Configuring QoS.
QoS Control of the OptiX RTN 605

The QoS control of the OptiX RTN 605 is realized through the internal logic unit of the
equipment. The QoS control of the OptiX RTN 605 supports the following functions:
l Flow classification based on PORT
l CAR based on the flow
l CoS based on the flow
The CoS can be classified based on the VLAN priority or DSCP.
l Egress queue scheduling based on SP and WRR
QoS Control of the RTN 900

For details about the Ethernet QoS, see 15.1 Configuring the QoS Policy.
18.3 Availability
The Hybrid microwave feature requires the support of the applicable equipment and boards.
Table 18-2 Availability of the Hybrid microwave feature
- RTN 605
IFH2 RTN 620
Table 18-3 Availability of the Hybrid microwave feature
IFU2
RTN 910/950
IFX2

This topic describes the principle of the AM switching of the hybrid microwave.
The AM engine is the core for controlling the AM switching.

On the one hand, the AM engine communicates with the remote AM engine through the
information channel that is provided by the radio link so that the transmit end is informed of the
quality of the signals at the receive end.
On the other hand, the AM engine determines the attributes of the modulation scheme that is
switched to, based on the real-time quality of the link. When the switching of modulation scheme
is required, the AM engine sends the AM switching indication signal to the Tx path.
AM Working Principle (Before the Switching)

1. The switching unit grooms services at different priority levels to the IF port on an IF board,
and the multiplexing unit multiplexes the services to microwave frames. E1 services and
Ethernet services are multiplexed to hybrid microwave frames by the multiplexing unit.
NOTE
In hybrid microwave, E1 services have the highest priority.
2. The hybrid microwave frames are transmitted to the opposite end over the Tx path after
being modulated by the IF unit.
3. The opposite end receives the IF signals from the Rx path. In addition, the opposite end
checks the quality of the received signals based on the received signal to noise ratio (SNR).
In the current working modulation scheme, the opposite end determines that the quality of
the received signals is degraded if the value of the received SNR is lower than the threshold.
Then, the opposite end sends signal quality indication signal to the AM engine.
4. The AM engine at the opposite end sends the hybrid microwave frame to the local end after
the switching indication signal is placed into the overhead of the hybrid microwave frame.
5. The IF unit at the local end processes the received IF signals and sends the AM switching
indication signal to the AM engine at the local end.
6. The AM engine at the local end sends the switching indication signal to the service signal
processing unit and IF signal modulation unit. Hence, the service signal transmission unit
and IF signal modulation unit perform the switching of service frames and modulation
schemes after N frames. See Figure 18-4.
Figure 18-4 AM switching (before the switching)
IF Module IF Module
Microwave Microwave
frame frame MUX
MUX Tx Path Rx Path
Unit Unit
INDI SNR
INDI AM
AM Messages AM
Engine Engine
INDI
SNR INDI
Microwave
frame MUX
MUX Tx Path Unit
Unit Microwave Rx Path
frame
High Priority Service SNR: signal to noise ratio

Low Priority Service INDI: Modulation scheme indication signal

AM Working Principle (After the Switching)

1. When an IF module detects that the SNR is higher than the modulation mode threshold for
triggering service switching, the IF module notifies the opposite end to switch the
modulation mode. The opposite packet switching unit performs QoS processing on services
based on the bandwidth change of the services, and then grooms the corresponding services
to the IF port.
2. According to the QoS processing result, the opposite packet switching unit discards low-
priority services and grooms high-priority services to the IF port. The bandwidth of
microwave frames decreases, as shown in Figure 18-5. When the IF module detects that
the SNR is higher than the modulation mode threshold for triggering service switching, the
IF module notifies the opposite end to switch the modulation mode in the same manner.
Figure 18-5 AM switching (after the switching)
IF Module IF Module
Microwave Microwave
frame frame MUX
MUX Tx Path Rx Path
Unit Unit
INDI SNR
INDI AM
AM Messages AM
Engine Engine
INDI
SNR INDI
MUX
MUX Tx Path
Rx Path Microwave Unit
Unit Microwave
frame frame
High Priority Service SNR: signal to noise ratio

Low Priority Service INDI: Modulation scheme indication signal
3. The change of modulation schemes implemented through the AM function is based on the
frame boundary of the signal. The Rx path of the receive end sends the signal indicating
the receive mode change of the current frame to the MUX unit when detecting the change
of the modulation scheme. Hence, the MUX unit receives and processes service signals
according to the new modulation scheme.

This topic describes how to configure hybrid microwave.
For details on how to configure the hybrid microwave service of RTN 900 NEs, see Configuring
the Hybrid/AM Attribute.
For details on how to configure the hybrid microwave service of RTN 600 NEs, see Configuring
Services Based on the Hybrid MicrowaveConfiguring Services Based on the Hybrid
Microwave.

NOTE
The procedure of configuring hybrid microwave of the RTN 900 is similar to the procedure of the RTN 600.
Hence, the details are not described here.

Operation Guide for RTN NE Management 19 Configuring the MSTP
19 Configuring the MSTP
About This Chapter
The MSTP is one of the spanning tree protocols. It is compatible with the spanning tree protocol
(STP) and rapid spanning tree protocol (RSTP), and it also fixes the defects of the STP and
RSTP.
19.1 Overview of the MSTP

This section describes the MSTP, in terms of the aim and compliant standard and protocol.
19.2 Basic Concepts
This section describes related concepts of the MSTP.
19.3 MSTP Application
In the case of the Ethernet user network where loops exist, the MSTP generates the tree topology
according to VLAN IDs of the Ethernet packets. Thus, the broadcast storm is avoided and the
network traffic is balanced according to the VLAN IDs of the Ethernet packets.
19.4 Configuring a Port Group
When both the RTN equipment and the user network need run the MSTP, configure the ports
as one port group. As a network bridge (switch), where the MSTP protocol is running, the port
group is involved in calculation of the spanning tree of the user network.
19.5 Configuring Bridge Parameters
The bridge parameters include the bridge parameters and port parameters. The bridge parameters
define the parameters of the port group as the MST bridge, and the port parameters define the
role of each port in the MSTP protocol.
19.6 Configuring CIST and MSTI Parameters
Configure the bridge priority of the port group to specify the root of the spanning tree. Configure
the MSTI port parameters to specify the MSTI priority and active/standby protection of the root
bridges.
19.7 Querying the CIST Running Information
Query the CIST running information to know the operation status of the MSTP protocol on the
port group.
19.8 Configuring Protocol Transfer for Ports
When a network has a switch where the STP protocol is running, the ports of the RTN equipment
connected to the switch are automatically switched to the STP-compatible mode. When such a

19 Configuring the MSTP Operation Guide for RTN NE Management
switch becomes absent in the network, these ports still work in the STP-compatible mode. In
this case, manually configure the port to recover the running of the MSTP protocol on the port.

19.1 Overview of the MSTP

This section describes the MSTP, in terms of the aim and compliant standard and protocol.
Overview of the STP/RSTP/MSTP

The MSTP is one of the spanning tree protocols. It is compatible with the spanning tree protocol
(STP) and rapid spanning tree protocol (RSTP), and it also fixes the defects of the STP and
RSTP.
For the Ethernet network with physical loops, IEEE puts forward the STP protocol (IEEE
802.1D, 1998 Edition) to prevent the generation of the network storm. In addition, IEEE puts
forward the RSTP protocol (IEEE 802.1w-2001) to fix the defects of the STP, which result in
slow convergence rate.
The STP/RSTP aims to divide a bridged LAN into a single spanning tree on the logical topology.
Thus, the network storm can be avoided. See Figure 19-1.
Figure 19-1 STP/RSTP

Switch A Switch B Switch A Switch B
Switch C Switch D Switch C Switch D
Switch E Switch F Switch E Switch F
Root: Switch F
Limitations of the STP/RSTP

During the fast development of the VLAN technology (IEEE 802.1Q), the limitations of the
STP/RSTP gradually emerge. The STP/RSTP protocol divides the network topology into a single
spanning tree, and thus the following problems occur:
l When the link is congested, it cannot bear any traffic. Thus, the bandwidth is wasted.
l When the network structure is dissymmetrical, a portion of the VLAN packets may not be
forwarded.
As shown in Figure 19-2, Host B and Host C belong to VLAN 2. The VLAN tag with 2 as the
VID is added to the Ethernet frames sent by Host B and Host C after the frames enter the switch.
Host A and Host D belong to VLAN 3. The VLAN tag with 3 as the VID is added to the Ethernet
frames sent by Host A and Host D after the frames enter the switch. As shown in Figure 19-2,

the corresponding VLAN packets can only pass through links marked with VLAN 2 or VLAN
3. Packets of VLAN 2 and VLAN 3 cannot pass through other links.
After the STP/RSTP protocol is enabled, the network topology is divided into a single spanning
tree, which congests other ports. The link between Switch C and Switch D is congested, and
other links cannot forward packets of VLAN 2. Thus, communication between Host B and Host
C is unavailable.
Figure 19-2 Limitations of the STP/RSTP

Host A Switch A Switch B Host B
VLAN 3 VLAN 2
VLAN 2
Switch C Switch D
VLAN 2
VLAN 3
VLAN 3
Host C Switch E Switch F Host D
Ethernet link
Spanning tree
Root switch
Improvement of the MSTP

The MSTP fixes the defects of the STP and RSTP. The convergence rate of the MSTP is fast.
In addition, traffic of different VLANs passes through corresponding trails, which provides a
well load balancing mechanism.
The MSTP divides a switching network into different regions, each of which is called an MST
region. Within each region, there are multiple spanning trees, which are independent from each
other. Each spanning tree is a multiple spanning tree instance (MSTI).
The MSTP sets the VLAN mapping table, which specifies the mapping relation between VLAN
and MSTI.
NOTE
Each VLAN corresponds to one MSTI. In other words, the data in the same VLAN can only be transmitted
on one MSTI. One MSTI, however, may correspond to multiple VLANs.

The network shown in Figure 19-2 can be considered as an MST region when MSTP is used.
Thus, Figure 19-3 shows the result. It is computed that two spanning trees are generated for
VLAN 2 and VLAN 3 respectively.
l MSTI 1 takes Switch B as the root switch to forward packets of VLAN 2.
l MSTI 2 takes Switch F as the root switch to forward packets of VLAN 3.
In this way, all VLAN packets can be properly forwarded. In addition, different VLAN packets
are forwarded through different paths. Thus, the load is balanced.
Figure 19-3 MSTI in an MST region
Host A Switch A Switch B Host B
VLAN 3 VLAN 2
VLAN 2
Switch C Switch D
VLAN 2
VLAN 3
VLAN 3
Host C Switch E Switch F Host D
Switch B
Switch A (Root) Switch A Switch B
VLAN 2 VLAN 3 VLAN 2
VLAN 2
Switch C Switch D Switch C Switch D
VLAN 2 VLAN 2
VLAN 3 VLAN 3
VLAN 3
Switch E Switch F Switch E Switch F

(Root)
MSTI 1 -> VLAN 2 MSTI 2 -> VLAN 3
Compliant Standard and Protocol

The MSTP complies with IEEE 802.1s, Virtual Bridged Local Area Networks - Amendment 3:
Multiple Spanning Trees.

19.2 Basic Concepts

This section describes related concepts of the MSTP.
In this section, examples in Figure 19-4 and Figure 19-5 show the related concepts of the MSTP.
Figure 19-4 Example of the MSTP

A0
A0
VLAN1 -> MSTI 1
VLAN2 -> MSTI 2
Other VLAN ->MSTI 0
D0 B0
VLAN1 -> MSTI 1

VLAN1 -> MSTI 1
VLAN2 -> MSTI 2
VLAN2 -> MSTI 2
Other VLAN ->MSTI 0
VLAN3 -> MSTI 2 C0
A0
Other VLAN ->MSTI 0
VLAN1--> MSTI 1
Other VLAN-->MSTI 0
CST

Figure 19-5 Example of the MST region
D0
Switch A MSTI 1
Root: Switch B
MSTI 2
Root: Switch D
Switch D Switch B MSTI 0 (IST)

Root: Switch A
VLAN 1 -> MSTI 1

VLAN 2 -> MSTI 2
VLAN 3 -> MSTI 2
Switch C Other VLAN -> MSTI 0
MST Region
The MST region consists of switches that support the MSTP in the LAN and network sections
among them. Switches physically and directly connected and configured with the same MST
region attributes belong to the same MST region. The attributes for the same MST region are as
follows:
l Same region name

l Same revision level
l Same mapping relation between the VLAN ID to MSTI
Within a LAN, there can be multiple MST regions, which are physically and directly or indirectly
connected to each other. For example, as shown in Figure 19-4, there are four MST regions,
A0, B0, C0 and D0.
MSTI
Within an MST region, there can be multiple spanning trees, which are independent from each
other and correspond to different VLANs. Each spanning tree is an MSTI. For example, in the
MST region D0, there are three MSTIs, MSTI 0, MSTI 1 and MSTI 2. See Figure 19-5.
CIST
The common and internal spanning tree (CIST), computed by using the RSTP algorithm, is a
single spanning tree connecting all the switches within a switching network. In the CIST, the
common spanning tree (CST) is the portion connected to each MST region. In the CIST, the
portion in each MST region is the internal spanning tree (IST) of each MST region.

CST
The CST, a spanning tree connected to all MST regions in a switching network, is the portion
responsible for connecting each MST region in the CIST. If each MST region is considered as
a switch, the CST is a spanning tree for the switch. For example, as shown in Figure 19-4, the
dashed lines indicate the CST of the network.
IST
The IST, a spanning tree in each MST region, is a section of the CIST in an MST region.
Normally, it is considered as the MSTI 0. For example, the MSTI 0 is shown in Figure 19-5.
When a packet with a VLAN tag is transmitted in an MST region, if the VLAN ID has no
corresponding MSTI, the packet is transmitted in the IST.
VLAN Mapping Table

The VLAN mapping table is an attribute of the MST region. It describes the mapping relation
between the VLAN and MSTI in this MST region.
Regional Root
The regional root consists of the CIST regional root and MSTI regional root.
l The CIST regional root is the root of the IST. For example, as shown in Figure 19-5, Switch
A is the CIST regional root of the MST region D0.
l The MSTI regional root is the root of each MSTI. For example, as shown in Figure 19-5,
Switch B is the MSTI regional root of the MSTI 1, and Switch D is the MSTI regional root
of the MSTI 2.
CIST Root
The CIST root is the root switch of the CIST.
19.3 MSTP Application

In the case of the Ethernet user network where loops exist, the MSTP generates the tree topology
according to VLAN IDs of the Ethernet packets. Thus, the broadcast storm is avoided and the
network traffic is balanced according to the VLAN IDs of the Ethernet packets.
At the client side, the RTN equipment supports the MSTP. At the network side, it does not
support the MSTP, but it can transparently transmit the MST bridge protocol data unit (BPDU).
There are three application scenarios of the MSTP.
l When multiple ports of the RTN equipment are connected to the same user network, these
ports should enable the MSTP protocol with the user network to avoid loops. These ports
connected to the user network should be first divided into a port group, which equals a
network bridge (switch) where the MSTP protocol is running.
l One CE equipment of the user is connected to two RTN NEs. Then, the channel switching
is performed by using the MSTP protocol. In this way, the two RTN NEs only transparently
transmit the BPDU packets, but they are not involved in the topology computation of the
MSTP protocol.

l When the user network requires that the STP be enabled across networks of different
carriers, the RTN equipment only transparently transmits the BPDU packets without the
involvement of the MSTP computation.
19.4 Configuring a Port Group

When both the RTN equipment and the user network need run the MSTP, configure the ports
as one port group. As a network bridge (switch), where the MSTP protocol is running, the port
group is involved in calculation of the spanning tree of the user network.
Prerequisite
Precautions
NOTE
l The sum of Ethernet ports enabled MSTP on one RTN equipment do not exceed one hundred.
l If an Ethernet port service is configured, this port can not be added to the port group.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab. Click Create to display the Create Port Group dialog
box.
Step 3 Set Protocol Type and Enable Protocol for the port group as required.
Step 4 Click Board and select the boards, to which the ports to be added to the port group belong, from
the drop-down list.
Step 5 Select the ports to be added to the port group from Available Port List. Click to add
the ports to Selected Port List.
Step 6 When all ports to be added to the port group are added to Selected Port List, click OK. and the
Operation Result dialog box is displayed, indicating that the operation is successful.
Step 7 Click Close. The created port group is then listed in the port group list.
----End
19.5 Configuring Bridge Parameters

The bridge parameters include the bridge parameters and port parameters. The bridge parameters
define the parameters of the port group as the MST bridge, and the port parameters define the
role of each port in the MSTP protocol.
Prerequisite

You must complete the creation of a port group.
Procedure
Step 2 Click the Bridge Parameters tab, and select the port group. Configure MST Domain Name
and Redaction Level. Click Apply.
Step 3 If the mapping relation of the VLAN of the port group and MSTI need be modified, double-
click Mapping List of the port group to display the Mapping List dialog box. In the Mapping
List dialog box, set the mapping relation of the VLAN ID and MSTI ID. Then, click Apply.
NOTE
Two means are available for setting the mapping relation between the VLAN ID and MSTI ID.
l Click the Set Mapping List tab, and enter the VLAN ID in the text box behind the MSTI ID. By default,
all VLAN IDs are mapped to MSTI 0.
l Click the Set Mapping Model tab, and enter the mapping module value (1-48) in the text box. Then,
the equipment distributes VLAN IDs (1-4094) equally to the MSTI whose mapping module ranges
from 1 to the mapping module value (1-16).
Two VLAN IDs (0, 4095) always map with MSTI 0.
Step 4 Select the port group and click the Bridge Parameters tab. Then, set MST Domain Max Hop
Count, Network Diameter, Hello Time, Max Age and Forward Delay for the port group.
Click Apply when the settings are completed.
Step 5 Select the port group and click the Port Parameter tab. Then, set Enable Edge Attribute,
Point-to-Point Attribute and Max Transmit Packet Count for each member port in the port
group. Click Apply when the settings are completed.
----End
19.6 Configuring CIST and MSTI Parameters

Configure the bridge priority of the port group to specify the root of the spanning tree. Configure
the MSTI port parameters to specify the MSTI priority and active/standby protection of the root
bridges.
Prerequisite
Procedure
Step 2 Click the CIST Parameters tab, and select the port group to be configured in Port Group.
Step 3 Each MSTI list of the port group is displayed in the upper pane. Double-click Bridge Priority
for the MSTI to modify the bridge priority of the MSTI. Click Apply when the setting is
completed.

Step 4 Each member port list of the port group is displayed in the lower pane. Double-click Priority
and Path Cost for Port to modify the port priority and path cost of the member port. Click
Apply when the setting is completed.
----End
19.7 Querying the CIST Running Information

Query the CIST running information to know the operation status of the MSTP protocol on the
port group.
Prerequisite
Procedure
Step 2 Click the CIST Running Information tab. The upper pane lists information on the bridge status
of the port group, which works as a bridge where the MSTP is running. The lower pane lists
information on the status of each port in the port group.
----End
19.8 Configuring Protocol Transfer for Ports

When a network has a switch where the STP protocol is running, the ports of the RTN equipment
connected to the switch are automatically switched to the STP-compatible mode. When such a
switch becomes absent in the network, these ports still work in the STP-compatible mode. In
this case, manually configure the port to recover the running of the MSTP protocol on the port.
Prerequisite
Procedure
Step 2 Click the Port Group Parameters tab, and click the port group that contains the ports requiring
protocol transfer in the upper pane.
Step 3 Click the ports requiring protocol transfer in the lower pane. Click Protocol Transfer.
----End

Operation Guide for RTN NE Management 20 Configuring the Control Plane
20 Configuring the Control Plane
About This Chapter
The control plane, responsible for the call control and connection control, consists of a group of
communication entities. The control plane creates, releases, monitors and maintains the
connection through signaling, and it automatically recovers the connection upon failure.
20.1 Basic Concepts

This section describes the related protocols of the control plane and application scenarios of
these protocols when the control plane is configured.
20.2 Configuring the IGP-ISIS Protocol
If the dynamic MPLS tunnel is required, the IGP-ISIS protocol must be configured. The IGP-
ISIS protocol is used to discover the network topology. Through the IGP-ISIS protocol, each
NE can obtain the information of the adjacent NE. When the IGP-ISIS protocol is used with the
RSVP-TE protocol, the creation of the MPLS tunnel is complete. The IGP-ISIS protocol
configuration includes the configuration of node and port attributes, query and configuration of
route importing information, and query of the TE link information.
20.3 Configuring the MPLS-LDP Protocol
If the dynamic PW need be configured, the MPLS-LDP protocol must be configured. The MPLS-
LDP is used to create the dynamic PW and to distribute the PW label. The NE can only obtain
the information of the adjacent NE through the IGP-ISIS protocol. In the case of a single service,
the NEs at the two ends can known each other by configuring the MPLS-LDP peer entity of the
MPLS-LDP protocol. On the U2000, the MPLS-LDP peer entities can be created and the MPLS-
LDP protocol can be configured.
20.4 Configuring the MPLS-RSVP Protocol
The MPLS-RSVP protocol is used to create dynamic MPLS tunnel and to distribute the tunnel
label. On the U2000, the parameters of the MPLS-RSVP protocol can be queried. This protocol
does not need special configuration, and thus the user can configure each parameter according
to requirements.
20.5 Configuring the OSPF Protocol
On the network, the OSPF protocol transfers the link state information and computes routes to
obtain the routing information according to the link state information. Through the OSPF
protocol, each NE can obtain the information of the adjacent NE. When the OSPF protocol is
used with the RSVP-TE protocol, the creation of the MPLS tunnel is complete. The OSPF

20 Configuring the Control Plane Operation Guide for RTN NE Management
protocol configuration includes the configuration of node and port attributes, query and
configuration of route importing information, and query of the TE link information.
20.6 Configuring the MP-BGP
MP-BGP means that the BGP runs in the interior of the autonomous system. In an L3VPN, route
switching between the PE equipment is realized through the MP-BGP.
20.7 Configuring Static Routes
The static routes are selected according to the preset route options in the network. On the
U2000, the static routes can be queried and created.
20.8 Configuring the Address Parse
On the U2000, the IP address and MAC address of the ARP table items can be created and
queried.

20.1 Basic Concepts

This section describes the related protocols of the control plane and application scenarios of
these protocols when the control plane is configured.
20.1.1 IGP-ISIS Protocol

The intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol,
belongs to the internal gateway protocol and is applicable to the internal of the autonomous
system. The equipment uses the IS-IS routing protocol, which is used with the label distribution
protocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP.
20.1.2 MPLS-LDP Protocol
The multi-protocol label switch label distribution protocol (MPLS-LDP) is used for the label
switched routers (LSR) to distribute labels in the network.
20.1.3 MPLS-RSVP Protocol
Multi-protocol label switch resource reservation protocol (MPLS-RSVP) supports the
distribution of MPLS labels. In addition, when transmitting the label binding message, it carries
the resource reservation information, used as a signaling protocol to create, delete or modify the
tunnel in the MPLS network.
20.1.4 ARP Protocol
Address resolution protocol (ARP) is used to map the IP address (alias: logical address) at the
network layer into the MAC address (alias: physical address) at the data link layer.
20.1.1 IGP-ISIS Protocol

The intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol,
belongs to the internal gateway protocol and is applicable to the internal of the autonomous
system. The equipment uses the IS-IS routing protocol, which is used with the label distribution
protocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP.
The IS-IS routing protocol used by the equipment creates and synchronizes the link state database
(LSD) through routing protocol packets, such as link state PDUs. Based on the LSDB and path
cost, the equipment uses the optimized shortest path first (SPF) algorithm to generate the routing
table, and uses the IS-IS TE of the IS-IS routing protocol to generate the traffic engineering
database (TEDB). The TEDB and routing table are the bases of creating the MPLS LSP. The
TEDB computes the route that the MPLS LSP travels through. The routing table forwards the
RSVP-TE and LDP protocol packets to realize label distribution. In this way, the MPLS LSP is
dynamically created.
Three features of the IS-IS routing protocol are supported by the equipment, that is, three types
of IS-IS routing protocol packets, optimized SPF algorithm, path cost, and IS-IS traffic
engineering (IS-IS TE).
Three Types of IS-IS Routing Protocol Packets

The IS-IS routing protocol belongs to the network player of the OSI protocol model. The IS-IS
routing protocol runs directly at the data link layer. When the IS-IS routing protocol is processed,
the decapsulation of the network layer is absent. With the preceding feature, the IS-IS routing
protocol is more applicable to the RTN transport network using the MPLS packet switching
technology.

The IS-IS routing protocol packets use the uniform encapsulation format. The length of the
packets is changeable and the extensibility is strong. The complexity of the protocol is decreased,
because the types of the protocol packets are few. Thus, the running is more reliable and efficient.
The equipment realizes the following three types of IS-IS routing protocol packets:
l Hello packets
Hello packets are used to construct and maintain neighbor relation between network nodes.
Hence, Hello packets are also called IS-to-IS hello (IIH) PDUs.
l Link state PDUs
Link state PDUs are used to exchange the link state information. In a network running the
IS-IS routing protocol, each network node generates a link state PDU, which contains all
the link state information of this network node. To generate its own LSDB, each network
node collects all the link state PDUs within the local domain and between domains.
l SNP packets
Sequence number PDUs (SNP) describe the link state PDUs in all or part of the LSDB.
The SNP is used to synchronize and maintain the LSDB of each network node in the
RTN network.
Optimized SPF Algorithm

The IS-IS routing protocol realized by the equipment uses the optimized SPF algorithm for route
computation and update. When the topology is changed, the resources (network bandwidth,
processing capability of network nodes, and memory) for updating the new route are few, and
thus the convergence rate of the entire network is improved.
Path Cost
The equipment supports the manual setting of path cost, and controls the route that the MPLS
LSP travels through when it is dynamically created.
IS-IS TE
When the MPLS constructs the LSP, the traffic engineering information of all the links in the
local domain should be known. The IS-IS TE realized by the equipment supports the construction
of the MPLS LSP. The equipment obtains the traffic engineering information (link utilization
and path cost) of all the links in the network through the IS-IS routing protocol. It constructs
and synchronizes the TEDB, and uses the constrained shortest path first (CSPF) algorithm used
by the TEDB to compute the route that the MPLS LSP travels through.
20.1.2 MPLS-LDP Protocol

The multi-protocol label switch label distribution protocol (MPLS-LDP) is used for the label
switched routers (LSR) to distribute labels in the network.
MPLS-LDP Peer Entities

The MPLS-LDP peer entities refer to two NEs, where LDP session exists, use the MPLS-LDP
to exchange labels mapping relation.

MPLS-LDP Session
The MPLS-LDP session is used to exchange label mapping and releasing messages between
different equipment. The MPLS-LDP session consists the following two types:
l Local MPLS-LDP session, in which the two NEs used to set up the session is directly
connected.
l Remote MPLS-LDP session, in which the two NEs used to set up the session is not directly
connected.
MPLS-LDP Message Types

The MPLS-LDP protocol mainly uses the following four types of messages:
l Discovery message, which is used to notify and maintain the existence of the equipment
in the network.
l Session message, which is used to set up, maintain and end the session between MPLS-
LDP peer entities.
l Advertisement message, which is used to create, change and delete the label mapping.
l Notification message, which is used to provide the constructive message and error
notification.
Working Mode of the MPLS-LDP

The label distribution process has two modes. The main difference between the two modes is
whether the label mapping is released in the upstream request mode or downstream unsolicited
distribution mode. The two label releasing modes are as follows:
l Upstream request mode, in which the equipment in the upstream sends the label request
message to the equipment in the downstream. The equipment in the downstream returns
the bound labels to the equipment in the upstream through label mapping message. When
the equipment in the downstream returns the label mapping message is determined by the
label control mode used by the equipment.
If the ordered mode is used, only when the equipment receives the label mapping
message returned by the equipment in the downstream, it sends the label mapping
information to the upstream.
If the independent mode is used, the equipment immediately sends the label mapping
message to the upstream, regardless of whether it receives the label mapping message
returned by the equipment in the downstream.
l Downstream unsolicited distribution mode, in which the equipment in the downstream take
the initiative to release the label mapping message to the equipment in the upstream after
the MPLS-LDP session is successfully set up. The equipment in the upstream saves the
label mapping information, and manages the received label mapping information according
to the route table information.
Basic Operation of the MPLS-LDP

In sequence, the MPLS-LDP operation consists of the following four phases:
l Development phase: In this phase, the equipment that expects to set up a session
periodically sends Hello message to the adjacent equipment to notify the adjacent node of
the local peer relation. In this process, the equipment can automatically discover its LDP
peer entity without manual configuration.

l Session set-up and maintenance: After the peer relation is set up, the equipment begins to
set up the session.
l PW set-up and maintenance: The set-up of the PW is based on the MPLS-LDP protocol.
l Session cancellation: A life state timer is set up for each session. When each LDP PDU is
received, this timer is refreshed. If the timer times out before a new LDP PDU is received,
the equipment takes that the session is interrupted and the peer relation is invalid. The
equipment shuts down the corresponding connection at the transmission layer to end the
session.
20.1.3 MPLS-RSVP Protocol

Multi-protocol label switch resource reservation protocol (MPLS-RSVP) supports the
distribution of MPLS labels. In addition, when transmitting the label binding message, it carries
the resource reservation information, used as a signaling protocol to create, delete or modify the
tunnel in the MPLS network.
Basic Concepts of the MPLS-RSVP

The MPLS-RSVP is a notification mechanism of the resource reservation in the network, which
realizes the bandwidth reservation on the control plane. As a label distribution protocol, it is
used to set up the LSP in the MPLS network.
For details of the MPLS-RSVP extension, refer to RFC3209.
Resource Reservation Style

The LSP set up by using the MPLS-RSVP is of a certain reservation style. When the RSVP
session is set up, the receive end determines which reservation style to be used, and thus
determines which LSP to be used.
l Fixed-filter (FF) style: When this style is used, resources are reserved for each transmit end
individually. Thus, transmit ends in the same session cannot share the resources with each
other.
l Shared-explicit (SE) style: When this style is used, resources are reserved for all transmit
ends in the same session. Thus, transmit ends can share the resources.
MPLS-RSVP Message Type

The MPLS-RSVP uses the following message types:
l Path message: The transmit end sends this type of message in the transmission direction of
data packets. In addition, the path state is saved on all the nodes along the trail.
l Resv message: The receive end sends this type of message in the reverse transmission
direction of data packets. In addition, the resource reservation is requested, and the
reservation state is created and maintained on all the nodes along the trail.
Tunnel Created by Using the MPLS-RSVP

As shown in Figure 20-1, the creation process of the LSP tunnel by using the MPLS-RSVP is
listed as follows:
l The ingress equipment generates the Path message, which is transmitted in the direction of
the egress equipment.

l After the egress equipment receives the Path message, the Resv message is generated and
then is returned to the ingress equipment. In addition, the Resv message reserves resources
on the equipment along the trail.
l When the ingress equipment receives the Resv message, the LSP is successfully created.
The LSP created by using the MPLS-RSVP has the resource reservation function. The
equipment along the trail can distribute some resources to the LSP to ensure the services
on the LSP.
Figure 20-1 LSP tunnel created by using the MPLS-RSVP

Egress
Ingress
Path Path
Resv Resv
Receiver
Sender
Parameters of the MPLS-RSVP State Timer

The parameters of the MPLS-RSVP state timer include the refreshing period of the Path or Resv
message, multiple of the path state block (PSB) timeout and reservation state block (RSB)
timeout.
In the case of the creation of the LSP, the transmit end adds the LABEL_REQUEST object to
the Path message. When the receive end receives the Path message with the LABEL_REQUEST
object, it distributes one label and adds the label to the LABEL object of the Resv message.
The LABEL_REQUEST object is saved in the PSB of the upstream node, and the LABEL object
is saved in the RSB of the downstream node. When the message indicating that the number of
message refreshing times exceeds the multiple of the PSB or RSB timeout is not continuously
received, the corresponding state in the PSB or RSB is deleted.
Assume that there is a resource reservation request, which does not pass the access control on
some nodes. In some cases, this request is not supposed to be immediately deleted, but it cannot
stop other requests from using its reserved resources. In this case, the node enters the blockade
state, and the blockade state block (BSB) is generated on the node of the downstream. When the
message indicating that the number of the message refreshing times exceeds the multiple of the
PSB or RSB timeout is continuously received, the corresponding state in the BSB is deleted.
20.1.4 ARP Protocol

Address resolution protocol (ARP) is used to map the IP address (alias: logical address) at the
network layer into the MAC address (alias: physical address) at the data link layer.
ARP Frame Format

Figure 20-2 shows the ARP frame format.

Figure 20-2 ARP frame format
Destination Source
Frame
MAC MAC ARP request/answer
type
address address
6 4 2
MAC IP address
IP MAC IP MAC address Destination
address at the Destination
protocol addres address OP at the transmit MAC
transmit IP address
type type s length length end address
end
2 2 1 1 2 6 4 6 4
l Destination MAC address: six bytes. When an ARP request is sent, the destination MAC
address is the broadcast MAC address, that is, 0xFF.FF.FF.FF.FF.FF.
l Source MAC address: six bytes.
l Frame type: two bytes. The value of this field is 0x0806.
l MAC address type: two bytes. It defines the address type in the network that runs the ARP.
Value 1 indicates the Ethernet address.
l IP protocol type: two bytes. It defines the protocol type. Value 0x0800 indicates the IP
address.
l MAC address length: one byte. It defines the length of the physical address expressed in
bytes. In the case of an ARP request or answer, the value of this field is 6.
l IP address length: one byte. It defines the length of the logical address expressed in bytes.
In the case of an ARP request or answer, the value of this field is 4.
l OP: two bytes. It defines the ARP packet type. Value 1 indicates the ARP request and value
2 indicates the ARP answer.
l MAC address at the transmit end: six bytes. It defines the MAC address of the transmit
station.
l IP address at the transmit end: four bytes. It defines the IP address of the transmit station.
l Destination MAC address: six bytes. It defines the destination MAC address. In the case
of an ARP request packet, the value of this field is all-zero.
l Destination IP address: four bytes. It defines the destination IP address.
Static ARP
Static ARP means that there is a fixed mapping relation between the IP address and the MAC
address, and thus you cannot adjust this relation dynamically on the equipment or the router.
For the static ARP, you need to manually create a table that is stored on each equipment in the
network.
The static ARP table is used in the following scenarios:
l When a packet is transmitted to a destination address beyond the local network segment,
this packet is bound with a specific network interface card (NIC) in order to be forwarded
through this gateway.

l To filter out certain illegal IP addresses, you can bind these addresses with an MAC address
that does not exist to realize the filtering.
Dynamic ARP
Dynamic ARP means that the mapping relation between the IP address and the MAC address is
constantly refreshed and adjusted through address learning.
Changing the NIC or moving the host to another network usually changes the physical address.
The corresponding MAC address can be obtained in a timely manner based on the dynamic ARP
address resolution.
ARP Principle
When a host or other network equipment needs to transmit data to another host or equipment,
IP data packets must be encapsulated into frames to be transmitted in the physical network.
During the transmission, the destination MAC address must be available.
When the equipment on the transmit station wants to obtain the MAC address of another
equipment in the network, the transmit station searches for the MAC address corresponding to
the IP address in the ARP table. If the ARP table is available, the transmit station obtains the
MAC address from the ARP table directly. Otherwise, the ARP function is enabled. As shown
in Figure 20-3, host A sends data to host B to obtain the MAC address of host B.
To obtain the MAC address of the station whose IP address is 10.1.1.2, host A broadcasts an
ARP request packet in the network. The packet carries the information about the MAC address
and IP address of the transmit station, and the IP address of the destination station. All the
equipment in the network receives and handles the ARP request packet. Only host B on the
destination station, however, can identify the IP address and return an ARP answer packet.
According to the MAC address of the transmit station in the request packet, host B sends the
ARP answer packet to the request station in unicast mode. After receiving the ARP answer
packet, host A obtains the MAC address of host B.
Figure 20-3 ARP address resolution
Transmit station: A-A-B;10.1.1.2

Host A Destination station: A-A-A;10.1.1.1 Host B
IP: 10.1.1.1 IP: 10.1.1.2
MAC: A-A-A MAC: A-A-B
ARP answer packet
ARP request packet
Transmit station: A-A-A;10.1.1.1

Destination station: 10.1.1.2
Host C Host D
IP: 10.1.1.3 IP: 10.1.1.4
MAC:A-A-C MAC:A-A-D

20.2 Configuring the IGP-ISIS Protocol

If the dynamic MPLS tunnel is required, the IGP-ISIS protocol must be configured. The IGP-
ISIS protocol is used to discover the network topology. Through the IGP-ISIS protocol, each
NE can obtain the information of the adjacent NE. When the IGP-ISIS protocol is used with the
RSVP-TE protocol, the creation of the MPLS tunnel is complete. The IGP-ISIS protocol
configuration includes the configuration of node and port attributes, query and configuration of
route importing information, and query of the TE link information.
20.2.1 Setting Node Attributes

On the U2000, the parameters of nodes managed by the IGP-ISIS protocol can be queried and
set.
20.2.2 Setting Port Attributes
On the U2000, the parameters of ports managed by the IGP-ISIS protocol can be queried and
set.
20.2.3 Configuring Parameters of Route Importing
On the U2000, the parameters of route importing can be queried and set.
20.2.4 Querying the Link TE Information
On the U2000, the parameters of the link TE can be queried.

On the U2000, the parameters of nodes managed by the IGP-ISIS protocol can be queried and
set.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-ISIS Configuration from the Function Tree.
Step 2 Click the Node Configuration tab.

NOTE
Currently, the equipment supports only one IS-IS instance.
Step 3 Optional: Select the ISIS Instance, you can modify the parameter of nodes managed by the IGP-
ISIS protocol.
Step 4 Click Apply to complete the setting of parameters.
Step 5 Click Query to query the parameters of a node.
----End


On the U2000, the parameters of ports managed by the IGP-ISIS protocol can be queried and
set.
Prerequisite
l Enable Tunnel of the layer 3 attributes must be set to Enabled.
Procedure
Step 2 Click the Port Configuration tab.
Step 3 Optional: Select the port, you can modify the parameter of ports managed by the IGP-ISIS
protocol.
Step 4 Click Apply to complete the setting of port parameters.
Step 5 Click Query to query the parameters of each port.
----End

Prerequisite
Procedure
Step 2 Click the Route Import tab.
Step 3 Click Import to display the Route Import dialog box, and then set parameters of the imported
routes.
Step 4 Click Apply to complete the setting of parameters of the imported routes. Then, click OK.
Step 5 Click Query to query the parameters of the imported routes.

CAUTION
When modifying the parameters of the imported routes, click Delete to delete the original
settings, and then click Import to re-set. This operation, however, interrupts the services. Thus,
exercise caution when performing this operation.
----End

Prerequisite
Procedure
Step 2 Click the Link TE Info tab.
Step 3 Click Query to query the information on the parameters of the link TE.
----End
20.3 Configuring the MPLS-LDP Protocol

If the dynamic PW need be configured, the MPLS-LDP protocol must be configured. The MPLS-
LDP is used to create the dynamic PW and to distribute the PW label. The NE can only obtain
the information of the adjacent NE through the IGP-ISIS protocol. In the case of a single service,
the NEs at the two ends can known each other by configuring the MPLS-LDP peer entity of the
MPLS-LDP protocol. On the U2000, the MPLS-LDP peer entities can be created and the MPLS-
LDP protocol can be configured.
20.3.1 Creating MPLS-LDP Peer Entities

On the U2000, the LDP peer entities can be created. Thus, the MPLS-LDP session is available
between NEs, and the NEs can obtain the label mapping messages of each other.
20.3.2 Configuring the MPLS-LDP Protocol
On the U2000, the parameters of the MPLS-LDP protocol can be set.
20.3.1 Creating MPLS-LDP Peer Entities

On the U2000, the LDP peer entities can be created. Thus, the MPLS-LDP session is available
between NEs, and the NEs can obtain the label mapping messages of each other.
Prerequisite

Context
For the local session and remote session, you only need to create bidirectional LDP peers between
the source equipment and sink equipment. That is, you need to create peers from the source to
the sink, and from the sink to source.
Procedure
> MPLS-LDP Configuration from the Function Tree.
Step 2 Click Create to display the Create LDP Peer Entity dialog box.
Step 3 For the Local LSR ID and Opposite IP fields, enter LSR ID of the opposite NE. Then, click
Apply.
Step 4 After the setting is complete, click OK.
Step 5 Click Query to query the parameters of the MPLS-LDP peer entities.
NOTE
Click Delete to delete the MPLS-LDP peer entities.
----End
20.3.2 Configuring the MPLS-LDP Protocol

On the U2000, the parameters of the MPLS-LDP protocol can be set.
Prerequisite
Procedure
> MPLS-LDP Configuration from the Function Tree.
Step 2 Set the parameters of the MPLS-LDP protocol.
Step 3 Click Apply to complete the setting of the parameters of the MPLS-LDP protocol.
Step 4 Click Query to query the parameters of the MPLS-LDP protocol.
----End
20.4 Configuring the MPLS-RSVP Protocol

The MPLS-RSVP protocol is used to create dynamic MPLS tunnel and to distribute the tunnel
label. On the U2000, the parameters of the MPLS-RSVP protocol can be queried. This protocol
does not need special configuration, and thus the user can configure each parameter according
to requirements.
Prerequisite

Procedure
> MPLS-RSVP Configuration from the Function Tree.
Step 2 Set the parameters of the MPLS-RSVP protocol.
Step 3 Click Apply to complete the setting of the parameters of the MPLS-RSVP protocol.
Step 4 Click Query to query the parameters of the MPLS-RSVP protocol.
----End
20.5 Configuring the OSPF Protocol

On the network, the OSPF protocol transfers the link state information and computes routes to
obtain the routing information according to the link state information. Through the OSPF
protocol, each NE can obtain the information of the adjacent NE. When the OSPF protocol is
used with the RSVP-TE protocol, the creation of the MPLS tunnel is complete. The OSPF
protocol configuration includes the configuration of node and port attributes, query and
configuration of route importing information, and query of the TE link information.

On the U2000, the OSPF Instance can be added.
On the U2000, the parameters of ports managed by the OSPF protocol can be queried and set.

On the U2000, the OSPF Instance can be added.
Prerequisite
Procedure
> IGP-OSPF Configuration from the Function Tree.
Step 2 Click the Node Configuration tab.
Step 3 Click New. Set the parameters of the node in the Create IGP-OSPF Protocol Instance dialog
box displayed.

Step 4 Click OK.
----End

On the U2000, the parameters of ports managed by the OSPF protocol can be queried and set.
Prerequisite
l Enable Tunnel of the layer 3 attributes must be set to Enabled.
Procedure
Step 2 Click the Port Configuration tab.
Step 3 Click New. Add ports managed by the OSPF protocol in the Config IGP-OSPF Protocol
Interface dialog box displayed.

NOTE
The OSPF protocol port can be an Ethernet interface, Ethernet virtual interface, or MP group.
Step 4 Click OK.
----End

Prerequisite
Procedure
Step 2 Click the Route Import tab.
Step 3 Click Import to display the Route Import dialog box, and then set parameters of the imported
routes.
Step 4 Click Apply to complete the setting of parameters of the imported routes. Then, click OK.
Step 5 Click Query to query the parameters of the imported routes.
CAUTION
When modifying the parameters of the imported routes, click Delete to delete the original
settings, and then click Import to re-set. This operation, however, interrupts the services. Thus,
exercise caution when performing this operation.
----End

Prerequisite

Procedure
Step 2 Click the Link TE Info tab.
Step 3 Click Query to query the information on the parameters of the link TE.
----End
20.6 Configuring the MP-BGP

MP-BGP means that the BGP runs in the interior of the autonomous system. In an L3VPN, route
switching between the PE equipment is realized through the MP-BGP.
Prerequisite
Procedure
> MP-BGP Configuration from the Function Tree.
Step 2 Click the MP-BGP Configuration tab. Click New and the Create MP-BGP Protocol
Instance dialog box is displayed.
Step 3 Set MP-BGP Protocol Instance and AS Number.
Step 4 Click OK and the Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click the Peer Configuration tab. Click New, and the Create Peer dialog box is displayed.
Step 6 Configure the peer of the MP-BGP protocol instance. You can select the MP-BGP Protocol
Instance that is already configured, and set the Remote IP Address and the Remote AS
Number that corresponds to the MP-BGP protocol instance.
Step 7 Click OK and the Operation Result dialog box is displayed indicating that the operation is
successful.
----End
20.7 Configuring Static Routes

The static routes are selected according to the preset route options in the network. On the
U2000, the static routes can be queried and created.
Prerequisite
l You must complete the setting of the basic attributes and Layer 3 attributes of the port.

Procedure
> Static Route Management from the Function Tree.
Step 2 Click Create to create the static routes, and then click Apply.
NOTE
l When selecting boards or ports, select those that have Layer 3 attributes.
l When the static route is configured, the port IP address and the next hop IP address must be in the same
network section.
l When the last digit of the IP address of the destination is not 0, the subnet mask is 255.255.255.255.
For example, if the IP address is 193.168.3.2, the mask of the destination node is 255.255.255.255.
l When the last digit of the IP address of the destination is 0, the subnet mask is 255.255.255.0 or
255.255.255.255. For example, if the IP address is 193.168.3.0, the mask of the destination node is
255.255.255.255 or 255.255.255.0.
Step 4 Click Query to query the parameters of the static routes.

NOTE
Click Delete to delete the original static routes.
----End
20.8 Configuring the Address Parse

On the U2000, the IP address and MAC address of the ARP table items can be created and
queried.
Prerequisite
Procedure
Step 1 In the NE Explorer, click the NE, and choose Configuration > Control Plane Configuration
> Address Parse from the Function Tree.
Step 2 Click Create and the Add Address Parse dialogue box is displayed.
Step 3 Set the IP address and MAC address of the ARP table items separately, and then click Apply.

CAUTION
When configuring the MAC address of the ARP table items, the first digit of the address must
be of an even number.
CAUTION
The configuration of the address resolution refers to the creation of 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. Thus, exercise caution when
performing this operation.
NOTE
Click Delete to delete the contents of the ARP table items.
----End

Operation Guide for RTN NE Management 21 Configuring an MPLS Tunnel
21 Configuring an MPLS Tunnel
About This Chapter
In a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. In
this way, data packets can be transparently transmitted among NEs. One MPLS tunnel can carry
several PWs. Before configuring a service, first configure a MPLS tunnel that carries the service.
On the U2000, you can use the trail function or per-NE configuration scheme to configure an
MPLS tunnel.
21.1 Basic Concepts

Before configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, and
application scenarios of the MPLS tunnel.
21.2 Configuring an MPLS Tunnel
The per-NE configuration scheme can be used to create an MPLS tunnel. At each node involved
in the tunnel, set the tunnel-related parameters. The per-NE configuration scheme can be used
to create a unicast MPLS tunnel. On the U2000, the user can create or delete a unicast MPLS
tunnel.
21.3 Querying the Tunnel Label Information
On the NE, the label for each tunnel is unique. By querying the tunnel label information, you
can learn the usage of tunnel labels. Thus, you can avoid the conflict of labels when creating a
static tunnel.

21 Configuring an MPLS Tunnel Operation Guide for RTN NE Management
21.1 Basic Concepts

Before configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, and
application scenarios of the MPLS tunnel.
21.1.1 MPLS and MPLS Tunnel

As a transmission technology, the multi-protocol label switching (MPLS) can realize transparent
transmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLS
protocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmission
and carries the PWs related to the service.
21.1.2 Application of the MPLS Tunnel
As the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmit
service packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLAN and
MPLS packets, and ATM packets. The MPLS Tunnel is mainly used for transparent transmission
of point-to-point data service packets and Tunnel protection group.
21.1.1 MPLS and MPLS Tunnel

As a transmission technology, the multi-protocol label switching (MPLS) can realize transparent
transmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLS
protocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmission
and carries the PWs related to the service.
Figure 21-1 shows how the MPLS tunnel is used as the service transmission channel.
Figure 21-1 MPLS tunnel in the MPLS network
IMA E1 Ingress node Transit node Egress node IMA E1
FE FE
MPLS tunnel
ATM STM-1 ATM STM-1
PW
The MPLS tunnel only provides an end-to-end channel, and does not care which service is
encapsulated in the PW it carries. Data packets are first encapsulated in the PW, which is stuck
with an MPLS label and sent to the MPLS tunnel for transmission. At the sink end, data packets
are recovered and retain the original service features. In the tunnel, the intermediate nodes are
called Transit nodes. Hence, a tunnel contains the Ingress node, Egress node and Transit nodes.
21.1.2 Application of the MPLS Tunnel

As the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmit
service packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLAN and
MPLS packets, and ATM packets. The MPLS Tunnel is mainly used for transparent transmission
of point-to-point data service packets and Tunnel protection group.

Transparent Transmission of Point-to-Point Data Packets

Commonly, the MPLS tunnel is used to provide a point-to-point service channel for services
such as the E-Line service. In this way, provider edges (PEs) in a PSN network can transparently
transmit services. Figure 21-2 shows how point-to-point data packets are transparently
transmitted.
Figure 21-2 Transparent transmission of point-to-point data packets

Node B
PE
MPLS tunnel
Node B
PE PE RNC
MPLS tunnel
MPLS tunnel
PE
Node B
An edge node in one network accesses the services from Node B, and transports the services to
the RNC connected to another PE. For such transport, one point-to-point MPLS tunnel can be
used. On the U2000, two schemes can be used to create such a unicast tunnel.
l Configuration on a per-NE basis: Configure the ingress port and the IP address of the next
hop at each NE involved in the MPLS tunnel. In this way, one unicast MPLS tunnel is
created.
l Configuration by trail: This configuration is classified into static configuration and dynamic
configuration.
Static configuration: Specify the source and sink NEs for the MPLS tunnel, and each
NE involved in the tunnel. In this way, one unicast MPLS tunnel is created.
Dynamic configuration: Only specify the source and sink NEs of the MPLS tunnel. The
equipment then creates a unicast MPLS tunnel through signaling.
Tunnel Protection Group

The MPLS tunnels of the same type are created in one tunnel protection group. In this way, 1
+1 or 1:1 protection is provided to these MPLS tunnels. If the working MPLS tunnel fails, the
Tunnel protection group ensures that services can still normally run.

By using the U2000, the user can configure 1+1 or 1:1 protection for MPLS tunnels that carry
important services.
Figure 21-3 shows the protection principle for unicast tunnels.
Figure 21-3 Protection principle for unicast tunnels
CE
CE
Working
tunnel
Ingress Egress
node Protection node
tunnel
Configuration of source Configuration of sink

protection group protection group
21.2 Configuring an MPLS Tunnel

The per-NE configuration scheme can be used to create an MPLS tunnel. At each node involved
in the tunnel, set the tunnel-related parameters. The per-NE configuration scheme can be used
to create a unicast MPLS tunnel. On the U2000, the user can create or delete a unicast MPLS
tunnel.
21.2.1 Configuring Basic Attributes of the MPLS

In the Basic Configuration interface, you can set LSR ID, Start of Global Label Space and
Start of Multicast Label Space.
21.2.2 Creating an MPLS Tunnel
You can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel,
create a tunnel at each node involved in the tunnel.
21.2.3 Deleting an MPLS Tunnel
To delete an MPLS tunnel using the single-station scheme, delete the MPLS tunnel at each node
involved in the tunnel.
21.2.1 Configuring Basic Attributes of the MPLS

In the Basic Configuration interface, you can set LSR ID, Start of Global Label Space and
Start of Multicast Label Space.
Prerequisite

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > Basic
Step 2 Set LSR ID, Start of Global Label Space and Start of Multicast Label Space.
CAUTION
If there are services on the NE, modifying LSR ID may result in NE reset and service
interruption.
----End
21.2.2 Creating an MPLS Tunnel

You can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel,
create a tunnel at each node involved in the tunnel.
Prerequisite
l You must complete the correct configuration of the port attributes.
l You must complete the correct setting of the LSR ID for each NE.
Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS
Management > Unicast Tunnel Management from Function Tree.
Step 2 Click the Static Tunnel tab and click New. The New Unicast Tunnel dialog box is displayed.
Step 3 Select New Reverse Tunnel to set parameters for the forward and reverse tunnels.
NOTE
When Node Type is set to Egress, Bandwidth(kbit/s) must be consistent with the tunnel bandwidth in
the Ingress direction and cannot be set.
For Next Hop Address, select the IP address of the interface of the next node, or the LSR ID of the next
node.
Step 4 Click OK to finish creation of the static tunnel.
Step 5 Follow Steps 1 - 4 to create static tunnels for Transit nodes and the Egress node.
Step 6 Optional: Select the created tunnel. Double-click the Vlan ID filed, and differentiate different
tunnels by adding a VLAN ID.
NOTE
If the created tunnel is carried by VLAN sub-interfaces, Vlan ID cannot be set for the tunnel.
----End

21.2.3 Deleting an MPLS Tunnel

To delete an MPLS tunnel using the single-station scheme, delete the MPLS tunnel at each node
involved in the tunnel.
Prerequisite
Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS
Management > Unicast Tunnel Management from Function Tree.
Step 2 Click the Static Tunnel tab. Select the tunnel to be deleted from the static MPLS tunnel list.
Step 3 Click Delete. A dialog box is displayed for confirmation.
Step 4 Follow Steps 1 - 3 to delete static tunnels for Transit nodes and the Egress node.
----End
21.3 Querying the Tunnel Label Information

On the NE, the label for each tunnel is unique. By querying the tunnel label information, you
can learn the usage of tunnel labels. Thus, you can avoid the conflict of labels when creating a
static tunnel.
Prerequisite
You must complete the creation of an MPLS tunnel.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLS
Label Management from the Function Tree.
Step 2 In the Tunnel Label tab, click Query to view the tunnel label information.
----End

Operation Guide for RTN NE Management 22 Configuring an IP Tunnel
22 Configuring an IP Tunnel
About This Chapter
When the services that cross an IP network need to be created, the OptiX RTN equipment
supports carrying PWs over the IP tunnel. In this way, services can be transparently transmitted
in an IP network.
22.1 IP Tunnel
IP tunnel can be used to carry the ATM PWE3 service or the CES service.
22.2 Configuring a UDP PW Port
Use the UDP port ID to encapsulate PW so that the service carried by the PW can be transmitted
transparently through the third-part IP network. The UDP PW can only be carried on an IP tunnel,
but not on a GRE tunnel.
22.3 Creating IP Tunnels
you can transmit the client services by connecting an IP tunnel to the DSLAM.
22.4 Deleting IP Tunnels
To release ports for other services, you can delete redundant IP tunnels.

22 Configuring an IP Tunnel Operation Guide for RTN NE Management
22.1 IP Tunnel
IP tunnel can be used to carry the ATM PWE3 service or the CES service.
If ATM or CES emulation service that travels through an IP network is required, the RTN
equipment can use the IP tunnel to carry the service. This complies with RFC 4023 as shown in
Figure 22-1. In the case of the IP tunnel, the situation is similar to that where "IP header" replaces
the MPLS external label (MPLS tunnel label) to establish a tunnel in the IP network. An ATM
emulation service can be provided between NE A and NE B, even though the IP network between
NE A and NE B does not support the MPLS.
Figure 22-1 ATM PWE3 over IP tunnel
ATM ATM
RTN Router Router RTN
switch switch
IP network
NE A NE B
ATM ATM ATM ATM

E1/STM-1 PWE3 PWE3 E1/STM-1
PW Label PW Label
IP IP
Ethernet Ethernet
22.2 Configuring a UDP PW Port

Use the UDP port ID to encapsulate PW so that the service carried by the PW can be transmitted
transparently through the third-part IP network. The UDP PW can only be carried on an IP tunnel,
but not on a GRE tunnel.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > IP/GRE Tunnel
Management > Basic Configuration from the Function Tree.
Step 2 Configure the parameters related to the port of UDP PW. Click Apply.
----End

Operation Guide for RTN NE Management 22 Configuring an IP Tunnel
22.3 Creating IP Tunnels

you can transmit the client services by connecting an IP tunnel to the DSLAM.
Prerequisite
l The static route must be configured.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > IP/GRE Tunnel
Management > IP Tunnel Management from the Function Tree.
Step 2 Click New and the Create IP Tunnel dialog box is displayed.
Step 3 Set parameters.
Step 4 Click OK. A prompt appears indicating that the operation was successful. Click Close.
NOTE
Step 6 Click Apply.
----End
22.4 Deleting IP Tunnels

To release ports for other services, you can delete redundant IP tunnels.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > IP Tunnel Management from the
Function Tree.
Step 2 Select an IP tunnel and click Delete. The Confirm dialog box is displayed. Click OK. A dialog
box is displayed indicating that the operation is successful.
Step 3 Click Close.
----End

Operation Guide for RTN NE Management 23 Configuring a GRE Tunnel
23 Configuring a GRE Tunnel
About This Chapter
When the services that cross an IP network need to be created, the OptiX RTN equipment
supports carrying ATM PWE3 services over generic routing encapsulation (GRE) tunnels. In
this way, services can be transparently transmitted in an IP network.
23.1 GRE Tunnel

GRE tunnel can be used to carry the PWE3 service or the CES service.
23.2 Creating GRE Tunnels
you can transmit the client services by connecting an GRE tunnel to the digital subscriber line
access multiplexer (DSLAM).
23.3 Deleting GRE Tunnels
To release ports for other services, you can delete redundant GRE tunnels.

23 Configuring a GRE Tunnel Operation Guide for RTN NE Management
23.1 GRE Tunnel

GRE tunnel can be used to carry the PWE3 service or the CES service.
If ATM or CES emulation service that travels through an IP network is required, the RTN
equipment can use the GRE tunnel to carry the service. This complies with RFC 4023 as shown
in Figure 23-1. In the case of the GRE tunnel, the situation is similar to that where "GRE
encapsulation + IP header" replaces the MPLS external label (MPLS tunnel label) to establish
a tunnel in the IP network. An ATM emulation service can be provided between NE A and NE
B, even though the IP network between NE A and NE B does not support the MPLS.
Figure 23-1 ATM PWE3 over GRE tunnel
ATM ATM
RTN Router Router RTN
switch switch
IP network
NE A NE B
ATM ATM ATM ATM
E1/STM-1 PWE3 PWE3 E1/STM-1
PW Label PW Label
GRE GRE
IP IP
Ethernet Ethernet
23.2 Creating GRE Tunnels

you can transmit the client services by connecting an GRE tunnel to the digital subscriber line
access multiplexer (DSLAM).
Prerequisite
l The static route must be configured.
Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > IP/GRE Tunnel Management >
GRE Tunnel Management from the Function Tree.
Step 2 Click New and the Create GRE Tunnel dialog box is displayed.
NOTE
When Loopback Port is set to Used, Source Board and Source Port, is unavailable.
Step 3 Set parameters.

Operation Guide for RTN NE Management 23 Configuring a GRE Tunnel
NOTE
Step 6 Click Apply.
----End
23.3 Deleting GRE Tunnels

To release ports for other services, you can delete redundant GRE tunnels.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > GRE Tunnel Management from
the Function Tree.
Step 2 Select a GRE tunnel and click Delete. The Confirm dialog box is displayed. Click OK. A dialog
box is displayed indicating that the operation is successful.
Step 3 Click Close.
----End

Operation Guide for RTN NE Management 24 Configuring an MPLS PW
24 Configuring an MPLS PW
About This Chapter
PWs should exist with services. When create or delete a services, create or delete the PW. The
U2000 provides a specific function to manage PWs. With this function, you can query reference
information of a PW, set QoS parameters and OAM parameters of a PW, modify and delete a
PW.
24.1 Querying an MPLS PW

When you create a service on the U2000, a PW is created. The PWs not bundled with services,
however, are not displayed. Hence, you need to query these PWs in the PW Management
interface. In the PW Management interface, you can query all PWs created on the equipment,
and parameters such as PW type, QoS parameters, OAM parameters and bearer tunnel.
24.2 Querying QoS-Related Parameters of an MPLS PW
The PW supports querying the QoS parameters.
24.3 Querying the PW Label Information
In an PSN, the label for each PW is unique. By querying the PW label information, you can learn
the usage of PW labels. Thus, you can avoid the conflict of labels when creating a PW.

24 Configuring an MPLS PW Operation Guide for RTN NE Management
24.1 Querying an MPLS PW

When you create a service on the U2000, a PW is created. The PWs not bundled with services,
however, are not displayed. Hence, you need to query these PWs in the PW Management
interface. In the PW Management interface, you can query all PWs created on the equipment,
and parameters such as PW type, QoS parameters, OAM parameters and bearer tunnel.
Prerequisite
l You must complete the creation of an MPLS PW during creating of a service.
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > MPLS Management > PW
Management from Function Tree.
Step 2 Click Query. All MPLS PWs created on the NE are displayed.
Step 3 Click the Advanced Attributes tab to view the advanced attributes of the MPLS PW.
----End
24.2 Querying QoS-Related Parameters of an MPLS PW

The PW supports querying the QoS parameters.
Prerequisite
l You must complete the creation of an MPLS PW when creating a service.
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > MPLS Management > PW
Management from Function Tree.
Step 2 Click Query. All MPLS PWs created on the NE are displayed in the upper pane.
Step 3 In the QoS information below, query the QoS parameters.
----End
24.3 Querying the PW Label Information

In an PSN, the label for each PW is unique. By querying the PW label information, you can learn
the usage of PW labels. Thus, you can avoid the conflict of labels when creating a PW.
Prerequisite

Operation Guide for RTN NE Management 24 Configuring an MPLS PW
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLS
Label Management from the Function Tree, and then click the PW Label tab.
Step 2 Click Query to view the PW label information.
----End

Operation Guide for RTN NE Management 25 Configuring CES Services
25 Configuring CES Services
About This Chapter
The CES service is a type of technology that carries layer 2 services. In the packet switched
network (PSN), the CES service tries to emulate basic behaviors and characteristics of the low-
rate TDM service, SONET and SDH services. The CES service configuration contains fast
configuration and configuration on a per-NE basis. In the fast configuration mode, you need to
specify the source and sink nodes in the trail configuration user interface, and then you can fast
configurate a complete CES service. In the configuration on a per-NE basis mode, you need to
configure the CES service seperately on the source node and sink node, and then you can
configure an entire CES service.
25.1 CES Service Type

Circuit emulation service (CES) applies the PWE3 emulation technology. For a CES service,
the PWE3 packet headers contain the frame format information, alarm information, signaling
information, and synchronous timing information of the TDM service flow. After encapsulated
by the protocol, the PW packets are transported over the MPLS tunnel, IP Tunnel, GRE Tunnel
in the PSN network. When reaching the PW egress, the PW packets are decapsulated to rebuild
the TDM circuit-switching service flow.
25.2 Configuration Flow of CES Services
This section describes the operation tasks for configuring CES services, and relations among
these tasks. When configuring or managing CES services, follow the configuration flows.
25.3 Configuring a CES Service
When configuring a CES service on a per-NE basis, you need to configure the attributes of the
source node and sink node of each station one by one. The efficiency of configuring the service
on a per-NE basis is low. It is recommended to use the trail function to configure the services.

25 Configuring CES Services Operation Guide for RTN NE Management
25.1 CES Service Type

Circuit emulation service (CES) applies the PWE3 emulation technology. For a CES service,
the PWE3 packet headers contain the frame format information, alarm information, signaling
information, and synchronous timing information of the TDM service flow. After encapsulated
by the protocol, the PW packets are transported over the MPLS tunnel, IP Tunnel, GRE Tunnel
in the PSN network. When reaching the PW egress, the PW packets are decapsulated to rebuild
the TDM circuit-switching service flow.
Application Mode
The CES service allows a metropolitan Ethernet network (MEN) carrier to provide TDM services
to customers that have only the TDM equipment. This enlarges the service range and the number
of users of the MEN carriers, and provides a way to transform the traditional circuit network to
the wideband data network.
The CES service mainly applies to the wireless service and the enterprise private line service.
The application scenarios include UNI-NNI and UNI-UNI, as shown in Figure 25-1.
l UNI-NNI CES service: The RTN equipment accesses the TDM services of customers by
using the TDM interface. The CES PW can be created between the RTN equipments to
emulate the end-to-end TDM service. To customers, the CES services are similar to actual
TDM services.
l UNI-UNI CES service: The RTN equipment accesses the TDM services by using a single
point.
NOTE
Now only the point-to-point service is supported. That is, the service of one E1 interface mapping to one
PW is supported. But converged services of several TDM interfaces mapping to one PW are not supported.

Figure 25-1 CES service networking sample
UNI-UNI
BTS
UNI-NNI
BSC
PE
PE
BTS PE
TDM Link
cSTM Link
PW BTS
Tunnel
Emulation Mode
The RTN equipment supports two types of CES services: structure-aware TDM circuit emulation
service over packet switched network (CESoPSN) and structure-agnostic TDM over packet
(SAToP).
In the CESoPSN mode:
l The RTN equipment senses frame structures, frame alignment modes and timeslots in the
TDM circuit.
l The RTN equipment processes the overhead and extracts the payload in TDM frames. Then,
the RTN equipment delivers the timeslot of each channel to the packet payload according
to certain sequence. As a result, the service in each channel in the packet is fixed and visible.
l Each Ethernet frame that carries the CES service loads TDM frames of a fixed number.
Usually the loading time is 0.125 to 5 ms.
In the SAToP mode:

l The equipment regards TDM signals as constant rate bit flows, instead of sensing structures
in the TDM signals. The entire bandwidth of TDM signals is emulated.
l The overhead and payload in the TDM signal are transparently transmitted.
l The Ethernet frame carries the CES service. Usually the loading time is 1 ms.
In the CESoPSN mode, for the free 64 kbit/s timeslot in TDM E1 signal, the RTN equipment
provides the compression function to save the transmission bandwidth. The timeslot number
ranges from 0 to 31. The timeslot number of 0 indicates a reserved timeslot for transmitting
signaling.
Service Clock
The TDM service has high requirements for the clock synchronization. The RTN equipment
provides two solutions to the CES service clock synchronization. See Table 25-1.
Table 25-1 CES service clock type

Synchroni PRC Access Whether the Clock is Description
zation Position Transmitted in
Solution Carrying Ethernet
External PE equipment No Introduces the PRC/GPS clock

Clock to the PE equipment, and uses
Synchroniza this clock as the transmit clock
tion of the CES port service
(retiming).
The CE system clock
synchronizes the PE service
clock. This realizes the
synchronization of all PEs and
CEs, and ensures that transmit
clocks of TDM services on all
CEs and PEs are synchronous,
and indirectly realizes the
transfer of the TDM service
clock.
See Figure 25-2.
Figure 25-2 External Clock synchronization of CES service clock
PRC/GPS PRC/GPS
CES
CE TDM+Clock PE PE TDM+Clock CE

25.2 Configuration Flow of CES Services

This section describes the operation tasks for configuring CES services, and relations among
these tasks. When configuring or managing CES services, follow the configuration flows.
Configure and manage UNI-NNI CES services by following the configuration flow shown in
Figure 25-4.
Figure 25-3 UNI-UNI CES service configuration flow

Required
Start
Optional
Creating a Network
Configure inferface
Configure UNI-UNI
CES Service
End
Table 25-2 Tasks for configuring the UNI-UNI CES service

Task Remarks
Creating Network To create a network, you need to create NEs,

configure NE data, and create fibers.
Configuring the Interface Use the E1 board to access the CES service
from the BTS.
Configuring the UNI-UNI CES Service To configure the UNI-UNI CES service, you
need to specify the service ID and service
name, select the source board and the sink
board.

Figure 25-4 UNI-NNI CES service configuration flow

Required
Start
Optional
Creating a Network
Configure inferface
Configure Control
Plan
Configure Tunnel
Configure UNI-NNI
CES Service
End
Table 25-3 Tasks for configuring the UNIs-NNI CES service

Task Remarks
Creating Network To create a network, you need to create NEs,

configure NE data, and create fibers.
Configuring the LSR ID Configure the LSR ID of the NE and start of

global label space.
Configuring the Network-Side Interface Set the general attributes and Layer 3
attributes (tunnel enable status and IP
address) for interfaces to carry the tunnel
carrying.

Task Remarks
Configuring the Control Plane Set the protocol parameters related to the
control plane to create the tunnel.
l To create a static MPLS tunnel to transmit
the ATM service, the parameters related
to the control plane need not be set.
l To create a dynamic MPLS tunnel to
transmit the ATM service, you need to set
the following protocol parameters:
1. Set the IGP-ISIS protocol parameters.
2. Set the MPLS-RSVP protocol
parameters.
To create a dynamic PW to transmit the
service, you need to set the parameters
related to the MPLS-LDP protocol.
Configuring the Tunnel A tunnel transmits the service.

l If an static MPLS tunnel is required,
configure an MPLS tunnel in the per-
NE or per-trail mode. Specify the tunnel
ID, set signaling type to static, name the
service, and specify the ingress node,
egress node, and transit node.
l If a dynamic MPLS Tunnel is required,
name the service, set signaling type to
dynamic, and specify the source node and
sink node for the tunnel.
Configuring the Service Interface Use the E1 board to access the CES service
from the BTS.
Configuring the UNIs-NNI CES service 1. Create a CES service: Set the service ID
and specify a service name.
2. Setting the source: Select the board and
the specific channel.
3. Configure a PW: Set the PW type, PW
label, and tunnel type.
4. Set advanced attributes: Set the jitter
buffer time, packet loading time, and
clock mode.
25.3 Configuring a CES Service

When configuring a CES service on a per-NE basis, you need to configure the attributes of the
source node and sink node of each station one by one. The efficiency of configuring the service
on a per-NE basis is low. It is recommended to use the trail function to configure the services.
25.3.1 Creating a UNI-UNI CES Service

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.
25.3.2 Creating a UNI-NNI CES Service
separately on the source and sink nodes of the service. After the CES service is created, the
corresponding PW is automatically created.
25.3.3 Deleting a CES Service
When you delete a CES service on a per-NE basis, you need to delete relevant attributes of the
service separately on the source and sink nodes of the service. After the CES service is deleted,
the corresponding PW is automatically deleted.
25.3.1 Creating a UNI-UNI CES Service

separately on the source and sink nodes of the service.
Prerequisite
The ports must be configured.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from
the Function Tree.
Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configure
the UNI-UNI service.
NOTE
l In the case of the UNI-UNI service, PW do not need to be set.
Step 3 Set attributes related to the UNI-UNI service.

1. Configure the parameters of the service.
NOTE
Note the following when setting the parameters:

Mode: UNI-UNI.
2. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
----End
25.3.2 Creating a UNI-NNI CES Service

separately on the source and sink nodes of the service. After the CES service is created, the
corresponding PW is automatically created.
Prerequisite

l The tunnel must be created. For configuration method, see 21.2.2 Creating an MPLS
Tunnel.
Procedure
the Function Tree.
Step 2 Click New, and the Create CES Service dialog box is displayed.
NOTE
In the case of the UNI-NNI service, set PW.
Step 3 Set attributes related to the UNI-NNI service.

1. Configure the parameters of the service.
NOTE

l Mode: UNI-NNI.
l In the case of PW Signaling Type, if you select Static, you need to set PW Ingress Label/
Source Port and PW Engress Label/Sink Port. If you select Dynamic, the system automatically
allocates PW Ingress Label/Source Port and PW Engress Label/Sink Port.
l PW Ingress Label/Source Port: the label that indicates a service is encapsulated into a PW.
l PW Engress Label/Sink Port: the label that indicates the service is decapsulated from the PW.
l Tunnel: Select the tunnel to carry the services.
2. Click QoS tab.
3. Set the parameters of QoS.

NOTE

EXP: Set the Ingress value only. 7 indicates the highest priority.
4. Click OK.
5. Click Advanced Attributes tab.

6. Configure parameters in the Advanced Attributes tab.

NOTE

Generally, Packet Loading Time(us) for carrying the CES service packets is 1 ms.
The value of Jitter Compensation Buffering Time(us) must be greater than the value of Packet
Loading Time(us) on the opposite end.
7. Click OK.
8. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
----End
25.3.3 Deleting a CES Service

When you delete a CES service on a per-NE basis, you need to delete relevant attributes of the
service separately on the source and sink nodes of the service. After the CES service is deleted,
the corresponding PW is automatically deleted.
Prerequisite
Procedure
the Function Tree.
Step 2 Select the service that you want to delete. Click Delete, and the Prompt dialog box is displayed.
Step 3 Confirm the deletion, and the Operation Result dialog box is displayed, indicating that the
Step 4 Click Close.
----End

Operation Guide for RTN NE Management 26 Configuring an ATM Service
26 Configuring an ATM Service
About This Chapter
You can configure an ATM service per trail or per NE. In the case of the per-trail configuration,
to configure a complete ATM service is to specify the source and sink nodes in the Trail
Management interface. In the case of the per-NE configuration, to configure a complete ATM
service is to configure an ATM service at each NE involved in the service trail.
26.1 Basic Concepts

Before using the U2000 to configure and manage ATM services, make yourself familiar with
the basic concepts related to the ATM service. The information facilitates the operations related
to ATM services.
26.2 ATM Service Configuration Flow
This section describes the operation tasks for configuring the ATM service, and relations among
these tasks. When configuring and managing the ATM services, follow the configuration flow.
The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services.
node.
26.4 Configuring the ATM Service
You can configure an ATM PWE3 service path for transmitting ATM signals on a per-NE basis.
When the ATM service is configured on a per-NE basis, the service attributes should be
configured at the source end and sink end separately. In this way, a complete ATM service is
configured. The configuration of the ATM services on a per-NE basis is of low efficiency, and
thus the configuration on an end-to-end basis is recommended.

26 Configuring an ATM Service Operation Guide for RTN NE Management
26.1 Basic Concepts

Before using the U2000 to configure and manage ATM services, make yourself familiar with
the basic concepts related to the ATM service. The information facilitates the operations related
to ATM services.
26.1.1 IMA
The inverse multiplexing for ATM (IMA) technology, demultiplexes an ATM cell flow to
multiple low-speed links, which are then multiplexed at the far end so that the cell flow is restored
to its original form. In this way, the multiplexing of multiple low-speed links becomes flexible
and easy.
26.1.2 Application of the IMA
The ATM IMA service is mainly used to interconnect the wireless base station to the equipment
at the transmission access side.
26.1.3 ATM Service
Asynchronous transfer mode (ATM) is a technology used to transport packets in cells with
ensured QoS. ATM meets the requirements of real-time services and non-real-time services.
The OptiX RTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATM
service.
26.1.4 ATM Traffic
The ATM communicates through virtual connections, which are uniquely identified by the VPI/
VCI in the cell header. During data transmission, you need to control the traffic of each virtual
connection to ensure the quality of service (QoS).
26.1.1 IMA
The inverse multiplexing for ATM (IMA) technology, demultiplexes an ATM cell flow to
multiple low-speed links, which are then multiplexed at the far end so that the cell flow is restored
to its original form. In this way, the multiplexing of multiple low-speed links becomes flexible
and easy.
This functionality applies to E1 interconnections between ATM networks, and does not have
special requirements for service types. See Figure 26-1.
Figure 26-1 ATM IMA group
Physical Link#0
Physical Link#1
Single ATM Physical Link#2 Single ATM Cell

Cell Stream Stream from
from ATM Layer IMA Virtual Link
ATM Layer

26.1.2 Application of the IMA

The ATM IMA service is mainly used to interconnect the wireless base station to the equipment
at the transmission access side.
The ATM IMA service has the following two scenarios.

l As shown in Figure 26-2, the ATM service on Node B is directly interconnected to the
RTN equipment at the access side through the E1 links.
l As shown in Figure 26-3, the ATM service on Node B is accessed to the SDH equipment
through the E1 links, and then the ATM service is aggregated to the STM-1 link. At last,
the IMA protocols are interconnected on the RTN equipment at the access side.
Figure 26-2 IMA networking diagram 1
IMA 1
IMA 2
Node B RTN
E1 Link
Figure 26-3 IMA networking diagram 2
Node B
PTN
SDH
Node B
SDH
E1 Link
Node B cSTM-1 Link
The ATM IMA service has the following scenarios.
As shown in Figure 26-4, the ATM service on Node B is directly interconnected to the RTN
equipment through the E1 links.

Figure 26-4 IMA networking diagram
IMA 1
IMA 2
Node B RTN
E1 Link
26.1.3 ATM Service

Asynchronous transfer mode (ATM) is a technology used to transport packets in cells with
ensured QoS. ATM meets the requirements of real-time services and non-real-time services.
The OptiX RTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATM
service.
ATM services mainly apply to wireless services. The application scenarios include UNIs-NNI
and UNI-UNI.
l UNIs-NNI ATM service: The RTN equipment accesses the ATM services of customers by
using the IMA link respectively. You can create the ATM PW between the RTN equipment
to emulate end-to-end ATM services. At the source end, the ATM cells are encapsulated
in the PW. Then, data packets are transparently transmitted in the MPLS network. At the
sink end, the ATM services are decapsulated and forwarded to the connected customer
network. To customers, the UNIs-NNI ATM services are similar to actual ATM services.
l UNI-UNI ATM services: The RTN equipment switches and transmits the ATM services
at a single point.
The ATM UNIs-NNI service supports the convergence of multiple ATM connections into a PW
for transmission. As shown in Figure 26-5, three ATM connections are encapsulated into a PW.
Figure 26-5 ATM connection convergence sample

26.1.4 ATM Traffic

The ATM communicates through virtual connections, which are uniquely identified by the VPI/
VCI in the cell header. During data transmission, you need to control the traffic of each virtual
connection to ensure the quality of service (QoS).
ATM Traffic Modes

As shown in Table 26-1, the RTN equipment supports four traffic modes. During traffic control,
you need to set different traffic parameters according to different service types.
Table 26-1 ATM service type and traffic

Application Type Application Traffic Parameter Remarks
Instance
Constant bit rate Voice services, video PCR, CDVT The CBR supports
(CBR) service services of a constant the strict
bit rate, and circuit requirements for
emulation services CTD and CDV, but
does not support
services with
variable delay.
Unspecified bit rate LAN emulation, IP PCR, CDVT The UBR does not
(UBR) service over ATM, and non- require a strict delay
special traffic and the delay
services variation. Besides, it
does not provide a
special QoS or
ensure the output.
UBR+ LAN emulation, IP PCR, CDVT There are UBR+

over ATM, and non- services on many
special traffic NodeBs. The UBR+
services services are
configured with the
MCR. When the
service rate does not
exceed the
configured MCR, the
normal service
transmission is
ensured. The features
of the UBR+ service
other than the MCR
are the same as the
features of the UBR
service.

Application Type Application Traffic Parameter Remarks

Instance
Real time variable bit Audio services, and PCR, SCR, CDVT, The rtVBR supports
rate (rtVBR) service video services of a MBS time-sensitive
variable bit rate service applications
and have restrictions
on the delay and
delay variation.
Non real time Data packet PCR, SCR, MBS The nrtVBR does not
variable bit rate transmission, have restrictions on
(nrtVBR) service terminal meeting, the delay and delay
and file transmission variation but
supports application
of services with the
variable rate and
burst traffic features.
The meanings of the traffic parameters in the table are as follows:

l Peak cell rate (PCR): It defines the maximum cell rate at which cells are transmitted to a
network.
l Sustainable cell rate (SCR): It defines the maximum sustainable average cell rate at which
cells are transmitted to a network.
l Cell delay variation tolerance (CDVT): When multiple connected cells are converged, at
the convergence egress, the transmission of a connected cell may be delayed because of
the insertion of other connected cells. Similarly, the transmission delay may also be caused
by the insertion of physical layer overheads and OAM cells. In other words. the cells do
not evenly arrive at the receive station. The arrival intervals of consecutive cells are
different in different periods. The maximum tolerance of this difference is called CDVT.
l Maximum burst size (MBS): It limits the maximum cell burst amount within the maximum
rate permitted.
Users require each service type to provide a certain QoS and comply with a certain traffic
protocol, which is realized by traffic control. During transmission, only user cells complying
with the protocol can be successfully transmitted. Cells that do not comply with the protocol are
labelled or discarded according to different situations.
Basic Principle of Traffic Control

In general, the control of ATM services combines the preventive control and reactive control
methods. Preventive control is the main method, but when congestion occurs, the network can
take measures to clear the congestion.
In point of effect, the ATM traffic control can be classified into two parts as follows:
l Traffic parameter control: preventive control
l Congestion control: reactive control

Traffic Parameter Control

The function of traffic parameter control is used to set up proper connections and to control the
connected cell flow according to the traffic parameters. If the control of these parameters fails,
traffic congestion may occur. The traffic parameter control includes the following methods:
l Usage parameter control (UPC)/network parameter control (NPC)
l Traffic shaping
UPC/NPC
UPC/NPC monitors and controls the traffic to judge whether cell violation occurs according to
the negotiated parameters. If cell violation occurs, corresponding measures will be taken to
prevent network resources from being invaded viciously or unintentionally. This ensures that
one link never violates the traffic control.
UPC is an act of connection monitoring at the UNI (dedicated or public), and NPC is an act of
connection monitoring at the NNI (dedicated or public).
According to different traffic types. the UPC includes the following measures:
l Allow cells to pass through: The cells are considered protocol-abiding by the UPC.
l Label cells: This operation is performed on the cell loss priority (CLP). The UPC labels
only cells whose CLP values are 0 by changing the CLP values to 1. In this case, these cells
are in conflict with the traffic convention. If the bandwidth is sufficient, these cells are
allowed to pass through. If the bandwidth is insufficient, however, these labeled cells are
discarded.
l Discard cells: The cells violate the protocol and thus cannot be transmitted continuously.
Traffic Shaping
Traffic shaping is a method of changing the traffic feature of a cell flow to realize a higher
network efficiency and ensure the QoS index. Traffic shaping helps the cell flow to be transmitted
more evenly, maximize the efficiency, and eases the network burden.
Congestion Control
Traffic parameter control is based on the connection and cells, but congestion control relates to
different service types.
If a network requires discarding cells, a better solution of congestion is to discard packets rather
than cells. When an NE discards cells, it also discards a part of the packet. As a result, the upper
layer protocol, such as the TCP/IP protocol, is retransmitted, and thus congestion or even collapse
occurs.
26.2 ATM Service Configuration Flow

This section describes the operation tasks for configuring the ATM service, and relations among
these tasks. When configuring and managing the ATM services, follow the configuration flow.
The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services.
UNI-UNI ATM service

Figure 26-6 shows the configuration flow of the UNI-UNI ATM service. For details of each
step, see the related section.

Figure 26-6 Configuration flow of the UNI-UNI ATM service
Required
Start
Optional
Creating Network
Configure the ATM

Policy
Configure the ATM

Interface
Configure the UNI-

UNI ATM Service
End
Table 26-2 Tasks for configuring the UNI-UNI ATM service

Task Remarks
1. Creating To create a network, you need to create NEs, configure NE data, create
Network fibers, and configure the clock.
2. Configure the The ATM policy is used for traffic management of the ATM service.
ATM Policy
The ATM interface accesses services from NodeB.
4. Configure the To configure the UNI-UNI ATM service, you need to specify the
UNI-UNI ATM service ID and service name, select the connection type, and configure
Service the connection.
UNIs-NNI ATM service

Figure 26-7 shows the configuration flow of the UNIs-NNI ATM service. For details of each
step, see the related section.

Figure 26-7 Configuration flow of the UNIs-NNI ATM service
Required
Start
Optional
Creating Network
Configure the
network-side interface
Configure the LSR ID
Configure the control

plane
Configure the Tunnel
Configure the ATM

Policy
Configure the ATM

Interface
Configure the UNIs-

NNI ATM service
End
Table 26-3 Tasks for configuring the UNIs-NNI ATM service

Task Remarks
1. Creating To create a network, you need to create NEs, configure NE data, create
Network fibers, and configure the clock.
2. Configure the Configure the LSR ID of the NE and start of global label space.
LSR ID

Task Remarks
3. Configure the Set the general attributes and Layer 3 attributes (tunnel enable status and
network-side IP address) for interfaces to carry the tunnel carrying.
interface
20 Configuring Set the protocol parameters related to the control plane to create the
the Control tunnel.
Plane4. l To create a static MPLS tunnel to transmit the ATM service, the
Configure the parameters related to the control plane need not be set.
control plane
l To create a dynamic MPLS tunnel to transmit the ATM service, you
need to set the following protocol parameters:
1. Set the IGP-ISIS protocol parameters. For details, see 20.2
Configuring the IGP-ISIS Protocol.
2. Set the MPLS-RSVP protocol parameters. For details, see 20.4
Configuring the MPLS-RSVP Protocol.
To create a dynamic PW to transmit the service, you need to set the
parameters related to the IGP-ISIS protocol and the MPLS-LDP
protocol.
5. Configure the A tunnel transmits the service.

Tunnel l If an static MPLS tunnel is required, configure an MPLS tunnel in
the per-NE or per-trail mode. Specify the tunnel ID, set signaling
type to static, name the service, and specify the ingress node, egress
node, and transit node.
l If a dynamic MPLS Tunnel is required, name the service, set
signaling type to dynamic, and specify the source node and sink node
for the tunnel.
6. Configure the The ATM policy is used for traffic management of the ATM service.
ATM Policy
7. Configure the The ATM interface accesses services from NodeB.

ATM Interface
8. Configure the 1. Create an ATM service: Specify the service ID, name the service,
UNIs-NNI ATM and select the service type and connection type.
service 2. Configure the connection: Set the source information, PW ID, sink
information, and policy.
3. Configure a PW: Set the PW type, label, and tunnel type.
4. Configure CoS mapping: Set the CoS policy for the PW.

Table 26-4 ATM Interface

Support Leve Configuration Method
ed l
Board
Type
E1 1. In General attributes for the PDH interface, set the port mode to
Layer 2. For details, see 8.2.1 Setting General Attributes of PDH
Interfaces.
2. In Advanced Attributes for the PDH interface, set the Frame
Format and Frame Mode. For details, see 8.2.3 Setting the
Advanced Attributes of PDH Interfaces.
3. Configuring bound channels in an ATM IMA Group, for details, see
26.3.1 Configuring Bound Channels in an ATM IMA Group in
the .
4. Set attributes of the ATM IMA group. In particular, specify the IMA
Transmit Frame Length, set the IMA Symmetry Mode, and enable
the IMA protocol. For details, see 26.3.2 Configuring Attributes of
an ATM IMA Group in the .
5. Set attributes of the ATM interface. In particular, set the interface
type, maximum VPI, and maximum VCI. For details, see 26.3.3
Configuring ATM Interface Attributes in the .
E1 board
(For 64K 1. In General attributes for the PDH interface, set the port mode to
example: times Layer 1. For details, see 8.2.1 Setting General Attributes of PDH
) lots Interfaces.
2. In Advanced Attributes for the PDH interface, set the Frame
Format and Frame Mode. For details, see 8.2.3 Setting the
Advanced Attributes of PDH Interfaces.
3. Create a serial port and specify the timeslots used by the service. Set
the port mode to Layer 2 and the encapsulation type is ATM. For
details, see 8.5.1 Creating Serial Interfaces.
the .

Support Leve Configuration Method

ed l
Board
Type
VC1 1. Configuring bound channels in an ATM IMA Group, for details, see
2 26.3.1 Configuring Bound Channels in an ATM IMA Group in
the .
Channeli
zed
STM-1 64K 1. Create a serial port and specify the timeslots used by the service. Set
board times the port mode to Layer 2 and the encapsulation type is ATM. For
(For lots details, see 8.5.1 Creating Serial Interfaces.
example:
CD1)
the .

node.
Context
Figure 26-8 shows the flow for configuring an IMA group.

Figure 26-8 IMA group configuration flow
Start
Configure bound
paths for an
ATM IMA group
Configure IMA
group attributes
Configure ATM
interface attributes
Query the states

Query the IMA Reset an IMA Modify an IMA Delete an IMA
of the link of an
group states group group group
IMA group
End
Required
Optional



the services.

Prerequisite
When the MLPPP or CES services is configured or the DCN is enabled on the VCTRUNK, the
VCTRUNK resources are occupied and thus the IMA group cannot be created.
When an E1or Fractional E1 port is bound with an IMA group, Port Mode should be set to
Layer 2.
Context
NOTE
Only the E1 ports on the same processing board can be bound.
Procedure
Step 2 Click the Binding tab and click Configuration. The Bound Path dialog box is displayed.
Step 3 Configure boards and VCTRUNK ports in Available Boards and Configurable Ports
respectively.
Step 4 Select E1, Fractional E1 for Level.
Step 5 Select a port in Available Resources. Click to bind the port to the VCTRUNK. Click
to cancel binding of the port to the VCTRUNK.

CAUTION
The VCTRUNK that is first added into the IMA group should be deleted at last.
The ports that are bound to the same VCTRUNK must have the same E1 frame mode or VC12
frame mode.
When the member links of an IMA group are at the serial ports of the 64K level, there are the
following restrictions:
l One serial port should be bound with a minimum of three 64K timeslots.
l The number of bound 64K timeslots should be the same for different serial ports.
l In one E1, only one serial port can be used as a member link of an IMA group.
Step 6 Click OK. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End

Prerequisite
Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Interface Management > ATM
Step 2 Click the IMA Group Management tab, enable the IMA protocol, and configure attributes of
the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds.
Click Close.
NOTE
Take the following precautions when setting parameters.

l You can enable or disable the IMA Protocol Enable Status of the IMA group only after configuring the
bound path of the corresponding VCTRUNK of the IMA group.
l IMA Transmit Frame Length: The optional values are 32, 64, 128 and 256.
l When IMA Symmetry Mode be set to Symmetric Mode and Symmetric Operation, Minimum Number
of Active Transmitting Links should be consistent with Minimum Number of Active Receiving Links.
l Maximum Delay Between Links: This parameter indicates the maximum delay variance among different
links in one IMA group. The value ranges from 1 ms to 120 ms, with 1 ms spacing.
l If the IMA protocol is enabled, only Minimum Number of Active Transmitting Links, Minimum
Number of Active Receiving Links and Maximum Delay Between Links can be set.
l You can modify the IMA Protocol Version, IMA Transmit Frame Length and IMA Symmetry Mode
only after you disable the IMA Protocol Enable Status.
----End


Prerequisite
Procedure
IMA Management from the Function Tree. Click the ATM Interface Management tab.
Step 2 Optional: Click Query to query the current attributes of each interface.
Step 3 Set relevant attributes of the interfaces bound with the IMA group as required.
successful.
Step 5 Click Close.
----End

Prerequisite
l You must complete the configuration of an IMA group.
Procedure
Step 2 Click the IMA Group States tab and select the IMA group for query. Click Query. A dialog
box is displayed, indicating that the operation succeeds. Click Close.
----End

Prerequisite
l You must complete the configuration of an IMA link.
Procedure

Step 2 Click the IMA Link States tab and select the IMA link for query. Click Query. A dialog box
----End

Prerequisite
l You must complete the creation of the IMA group.
Procedure
Step 2 Click the IMA Group Management tab and select the IMA group. Click Reset. A dialog box
----End

Prerequisite
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification
of the IMA group may interrupt services. Exercise caution for this.
Procedure
Step 2 Click the IMA Group Management tab and modify related attributes of the IMA group. Click
Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End


the services.
Prerequisite
l The IMA Protocol Enable Status of the IMA group must be Disabled.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting
the IMA group may interrupt the services. Exercise caution for this.
Procedure
IMA Management from the Function Tree.
Step 2 Click the Banding tab and select an IMA group. Click Delete. A dialog box is displayed,
indicating that the operation may interrupt the services. Click OK. A dialog box is displayed,
----End
26.4 Configuring the ATM Service

You can configure an ATM PWE3 service path for transmitting ATM signals on a per-NE basis.
When the ATM service is configured on a per-NE basis, the service attributes should be
configured at the source end and sink end separately. In this way, a complete ATM service is
configured. The configuration of the ATM services on a per-NE basis is of low efficiency, and
thus the configuration on an end-to-end basis is recommended.
26.4.1 Creating ATM Services

This section describes how to create an ATM PWE3 service channel that transports ATM signals
on a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you need
to separately configure the service attributes at the source and sink ends of the service first.
26.4.2 Modifying ATM Services
If the configuration information on an ATM service on the U2000 is inconsistent with that in
the network, modify the ATM service on a per-NE basis.
26.4.3 Deleting ATM Services
If any ATM service channels are redundant, delete the ATM service channels to release
resources. To delete an ATM service on a per-NE basis, delete the ATM service specified at the
source NE and sink NE.

26.4.1 Creating ATM Services

This section describes how to create an ATM PWE3 service channel that transports ATM signals
on a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you need
to separately configure the service attributes at the source and sink ends of the service first.
Prerequisite
l You must complete the configuration of the control plane. For configuration method, see
20 Configuring the Control Plane.
l If IMA services are accessed, you must complete the configuration of an IMA group. For
configuration method, see Configuring the IMA.
l You must complete the configuration of the ATM policy. For configuration method, see
15.1.9.1 Creating the ATM Policy.
l You must complete the creation of a tunnel. For configuration method, see 21.2.2 Creating
an MPLS Tunnel.
Context
The OptiX RTN equipment can access services at the E1/VC-12 level or 64K timeslot level.
When the OptiX RTN equipment accesses the services at the E1/VC-12 level, all the available
timeslots of the E1/VC-12 channels are used to transport services. When the OptiX RTN
equipment accesses the services at the 64K timeslot level, one E1/VC-12 channel can be used
to transport both the ATM services and CES services (certain timeslots allocated for ATM
services and others for CES services). In this manner, the E1/VC-12 channels are used flexibly.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management
Step 2 Click New. The New ATM Service window is displayed. In the window, configure a UNIs-
NNI or UNI-UNI service.

NOTE
l For the UNIs-NNI service, set the attributes in the Connection, PW and CoS Mapping tabs.
l For the UNI-UNI service, set only the attributes in the Connection tab.
Step 3 To create a UNI-UNI service, go to Step 4. To create a UNIs-NNI service, go to Step 5.
Step 4 Optional: Create a UNI-UNI service.

1. Set ATM-related general attributes.
NOTE
Select UNI-UNI for the service type.

For the connection type, select the following.
l PVP: Only the VPI value of the ATM connection can be modified.
l PVC: The VPI and VCI values of the ATM connection can be modified.
2. Click the Connection tab and click Add. In the window displayed, set connection attributes.
NOTE
The Sink VPI value ranges from 0 to (2MaxVPIbits-1).

The Sink VCI value ranges from 32 to (2MaxVCIbits-1).
3. Click OK.
Step 5 Optional: Create a UNIs-NNI service.

1. Set ATM-related general attributes.

NOTE
Select UNIs-NNI for the service type.

For the connection type, select the following.
l PVP: Only the VPI value of the ATM connection can be modified.
l PVC: The VPI and VCI values of the ATM connection can be modified.
2. Click the Connection tab and click Add. In the window displayed, set connection attributes.
3. Click the PW tab and click Add. The Configure PW window is displayed. In the window,
set attributes of the PW.
4. Click the General Attributes tab and set the general attributes of PW.
5. Optional: Click the QoS tab and set the QoS attribute of PW.
6. Optional: Click the Advanced Attributes tab and set the advanced attributes of PW.
7. Click the CoS Mapping tab and click Add to configure the CoS mapping table.
NOTE
You can configure the CoS mapping only after configuring the parameters in the PW tab.
8. Click OK.
Step 6 In the New ATM Service window, click OK. A dialog box is displayed, indicating that the
operation is successful. Click Close.
----End

26.4.2 Modifying ATM Services

If the configuration information on an ATM service on the U2000 is inconsistent with that in
the network, modify the ATM service on a per-NE basis.
Prerequisite
Context
CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.
Procedure
Step 2 Select a created service and click the Connection tab. In the tab, click Configure Connection
to modify connection attributes of the service. Click OK. A dialog box is displayed, indicating
that the operation affects services. Click OK. A dialog box is displayed, indicating that the
Step 3 Click the PW tab. In the tab, modify PW attributes of the service. Click Apply. A dialog box is
displayed, indicating that the operation affects services. Click OK. A dialog box is displayed,
NOTE
You can modify parameters only in the QoS and Advanced Attributes tabs of the PW, but not the
parameters in the General Attributes tab.
Step 4 Select a created service and click the CoS Mapping tab. Modify the CoS mapping attributes of
the service. Click OK. Click Apply. A dialog box is displayed, indicating that the operation
affects services. Click OK. A dialog box is displayed, indicating that the operation is successful.
Click Close.
----End
26.4.3 Deleting ATM Services

If any ATM service channels are redundant, delete the ATM service channels to release
resources. To delete an ATM service on a per-NE basis, delete the ATM service specified at the
source NE and sink NE.
Prerequisite

Context
CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.
Procedure
from Function Tree.
Step 2 Select a created service and click the Connection tab. In the tab, click Delete. A dialog box is
displayed indicating that the operation affects services. Click OK. A dialog box is displayed
telling you that the operation was successful. Click Close.
----End

Operation Guide for RTN NE Management 27 Configuring the BFD
27 Configuring the BFD
About This Chapter
The BFD is a protocol that uses the UDP packets to quickly detect the link status. The detection
time can reach Milliseconds.
27.1 Overview of the BFD

Similar to a simple Hello protocol, the BFD is adopted to detect faults on the route layer.
27.2 Basic Concepts
This section describes the basic BFD-related concepts such as session, single-hop detection and
diagnosis word.
27.3 Creating a BFD Session
The BFD session is the main part of the configuration, management and check. Before the BFD
check, you need to create a BFD session to test the link state.
27.4 Configuring Parameters of the BFD Session
After creating the BFD session, configure parameters for the BFD session.
27.5 Querying the BFD Session Information
Query the BFD session information as required.
27.6 Deleting a BFD Session
In the case of many BFD sessions, delete some BFD sessions to release resources.

27 Configuring the BFD Operation Guide for RTN NE Management
27.1 Overview of the BFD

Similar to a simple Hello protocol, the BFD is adopted to detect faults on the route layer.
Objective and Benefit

The BFD can fast detect the communication failure between the two adjacent systems. In other
words, a pair of systems periodically sends detection packets on the channel on which session
between the two systems is created. If a system does not receive any detection packet from the
opposite end in a specific time, the system regards that a failure occurs in some part of the
bidirectional channel to the adjacent system. In this way, when a fault occurs, a substitute channel
can be created quickly or the services are quickly switched to another link. The BFD is similar
to the neighbor check of many protocols in many aspects, but the BFD takes a shorter detection
time. The BFD sends the user datagram protocol (UDP) packets.
The BFD has the following functions:

l Performs fault detection that brings light load and lasts for a short time for the channel
where the BFD session is set up.
l Adopts a uniform mechanism to detect faults for any medium and any protocol layer in a
real-time manner.
l Reduces the lost data.

The BFD complies with IETF: draft-ietf-bfd-base-04, IETF: draft-ietf-bfd-v4v6-1hop-04 and
IETF: draft-ietf-bfd-multihop-04.
27.2 Basic Concepts

This section describes the basic BFD-related concepts such as session, single-hop detection and
diagnosis word.
Session
Before performing the BFD detection, set up the peer session at both ends of the channel. After
the session is set up, each end transmits the BFD control packets to the opposite end at the
negotiated rate.
Single-Hop Detection
The single-hop detection quickly detects and monitors the connectivity of the link of direct
connection. Single-hop detection is applicable to the scenario where the link between BFD peers
does not traverse the third-party equipment.
Diagnosis Word
The diagnosis word indicates the cause of the state change of the latest session in the local BFD
system.

Operation Guide for RTN NE Management 27 Configuring the BFD
27.3 Creating a BFD Session

The BFD session is the main part of the configuration, management and check. Before the BFD
check, you need to create a BFD session to test the link state.
Prerequisite
l The port where the BFD session can be created must be a Ethernet port configured with
Layer 3 attributes. In the case of a Lay 3 port, you must enable the MPLS.
l The Port enable tunnel.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Click New. The Create BFD dialog box is displayed.
Step 3 Set the parameters related to the BFD session.

NOTE
Take the following precautions when setting these parameters.

If Session Type is set to Single-Hop, select Board and Port, that is, select a port on a board that transmits
the BFD packets.
Step 4 Click OK.
----End
27.4 Configuring Parameters of the BFD Session

After creating the BFD session, configure parameters for the BFD session.
Prerequisite
l The BFD session must be created.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Select a BFD session, and configure parameters for the BFD session.
It is recommended that you set the following parameters:
l Admin Status: Up
l Local Send Interval of Packets: 1000
l Local Receive Interval of Packets: 1000

27 Configuring the BFD Operation Guide for RTN NE Management
l Local Detection Multiple of Packets: 3

Step 3 Click Apply.
----End
27.5 Querying the BFD Session Information

Query the BFD session information as required.
Prerequisite
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Select a BFD session and click Query. Check the BFD session information.
NOTE
If Admin Status is set to Down, Session Status is displayed only as Down.
----End
27.6 Deleting a BFD Session

In the case of many BFD sessions, delete some BFD sessions to release resources.
Prerequisite
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Select a BFD session and click Delete.
Step 3 A dialog box is displayed for confirmation. Click OK.
----End

Operation Guide for RTN NE Management 28 Configuring the IGMP Snooping
28 Configuring the IGMP Snooping
About This Chapter
The IGMP Snooping enhances the capability of managing the multicast of the Layer 2 switching
services. The IGMP Snooping avoids the broadcast of the service flow on the Layer 2 equipment,
and thus increases the resource utilization of the equipment and links.
28.1 Overview of the IGMP Snooping

This section describes the IGMP Snooping, in terms of the aim, compliant standard and protocol,
and related concepts.
28.2 Basic Concepts
This section describes the basic concepts of the IGMP Snooping, which is used for understanding
and applying the IGMP Snooping. The basic concepts covers the enabling of the IGMP snooping
protocol, router port, member port, aging time of the router port, maximum non-response times
for multicast group members, multicast strategy, and quick deletion of member port.
28.3 Application of the IGMP Snooping
The IGMP Snooping enhances the resource utilization through multicast forwarding, enhances
the security of the U2000 through restriction on user access, and enhances the network reliability
through quick response to the link change.
28.4 Configuring the IGMP Snooping Parameters
Parameters related to the IGMP Snooping include Enabled Protocol, Router Port Aging Time
(min), Maximum times of No Response from Multicast Members and Maximum Number
of Multicast Groups. Configure these parameters for the IGMP Snooping to work normally.
After configuring the IGMP Snooping parameters for multicast services that are created, you
can set some ports for the multicast service as quick leave ports. The multicast user on each
quick leave port can then switch the multicast service channels quickly.
28.5 Configuring the Router Management
The user manually creates the router port, through which the equipment responds to the packets
of the router for querying the IGMP Snooping. The router port is not aged automatically, and
thus always exists unless manually deleted.
28.6 Configuring the Route Member Port Management
To define the multicast scope, configure the route member ports. The static multicast member
ports are not aged automatically, and thus always exist unless manually deleted.

28 Configuring the IGMP Snooping Operation Guide for RTN NE Management
28.7 Configuring the Packet Statistics

Set the status of the protocol packet statistics to start, stop or clear the packet statistics. The
packet statistics data indicates the running status of multicast services.

28.1 Overview of the IGMP Snooping

This section describes the IGMP Snooping, in terms of the aim, compliant standard and protocol,
and related concepts.

The IGMP protocol applies to the router and host, such as the switch, hub, or DSLAM. It is used
to manage the addition and deletion of group members. The RTN equipment with the IGMP
Snooping enabled dynamically learns the router port, multicast group and group members
through snooping of the IGMP protocol packets between the multicast management router and
host. Thus, the multicast packets are prevent from being broadcast in the Layer 2 switch. The
equipment can transmit the multicast services, such as the IPTV or conference call, through the
IGMP Snooping. The IGMP Snooping has a strong capability of managing the multicast services,
such as dynamic response to IGMP Join/Leave requests of customers. Thus, it is applied to the
equipment at the edge/access and convergence layers.
Figure 28-1 shows the networking diagram of the multicast services with the IGMP protocol.
The networking diagram consists of the multicast service source, multicast management router,
RTN equipment, and hosts In the actual networking, the RTN equipment and multicast
management router, and the multicast management router and the service source may be
connected through complex networks respectively.
Figure 28-1 Application of the IGMP Snooping-Supported Equipment in the Network
Multicast management router
Host Host Host Host

(Non-multicast (Multicast member)(Multicast member) (Non-multicast
member) member)
Physical connection
Flow direction of the multicast service

The advantages of the application of the IGMP Snooping are as follows:

l The network bandwidth can be saved.
l Signals are forwarded based on the VLAN. Hence, the information security is increased.
l Quick response is made to the link fault. Hence, the reliability is enhanced.

The IGMP complies with RFC 4541, Considerations for Internet Group Management Protocol
(IGMP) and Multicast Listener Discovery (MLD) Snooping Switches
28.2 Basic Concepts

This section describes the basic concepts of the IGMP Snooping, which is used for understanding
and applying the IGMP Snooping. The basic concepts covers the enabling of the IGMP snooping
protocol, router port, member port, aging time of the router port, maximum non-response times
for multicast group members, multicast strategy, and quick deletion of member port.
Enabling of the IGMP Snooping Protocol

After the IGMP Snooping protocol is enabled, the equipment begins to perform the multicast
group learning and aging. Then, the multicast services are multicast in corresponding multicast
groups.
If the IGMP Snooping is disabled, the equipment does not perform the multicast group learning
and aging. In addition, the equipment deletes all the learned dynamic multicast groups.
Router Port
The router port refers to the port that faces the multicast router. The E-LAN service of the RTN
equipment takes the port that receives the IGMP query packets as the router port. The router
port consists of the following two types:
l Dynamic router port, which relies on the protocol packets exchanged between the router
and host, and can be dynamically maintained. Each of this port can enable a router port
aging timer. When the timer times out, this router port is invalid.
l Static router port, which is specified by users by using configuration commands, cannot be
aged.
Member Port
The multicast member port refers to the port that faces the host of the member. The switch
transmits the multicast packets from this port. The multicast group member port, referred to as
member port for short, consists of the following two types:
l Dynamic member port, which can receive the IGMP report packets. This port, relies on the
protocol packets exchanged between the router and host, can be dynamically maintained.
Each of this port can enable a member port aging timer. When the timer times out, that is,
when the times of not receiving the IGMP report packets exceed certain times, this member
port becomes invalid.

l Static member port, which is specified by users by using configuration commands, cannot
be aged.
Aging Time of the Router Port

The IGMP protocol requires that the router periodically transmit the IGMP query packets, which
are used to obtain the information indicating whether the host is added to the multicast group.
After the E-LAN service of the RTN equipment learns the router port in a broadcast domain,
the aging timer should be enabled for this port. When the aging timer of the router port times
out but this port does not receive any query packet, the IGMP Snooping sub-system takes that
this port is invalid, and then the sub-system ages this port.
If this port receives the query packet, including the query packet of the specified group, before
the aging timer times out, the aging timer of the router port should be re-set.
Maximum Non-Response Times for Multicast Group Members

The equipment should learn the deletion information on the multicast members in a timely
manner. Otherwise, the equipment continuously transmits service packets to the multicast group
members deleted from the multicast group, which consumes the resources of the RTN equipment
and downstream equipment. Thus, when the response packet of the first member in the multicast
group is received, the response packet is unicast to the router port instead of being multicast in
the multicast group. In this way, the RTN equipment can snoops whether the query packet is
responded on each group member.
When the equipment receives the IGMP response packet sent by a port for the first time, the
equipment first adds the port to the corresponding multicast group, and then enables the count
of the query non-response times for this multicast member. When the query packet is sent to a
multicast member and the response packet is not received within the required response period,
the count of the query non-response times for this multicast member is started. When the count
value reaches a threshold, the equipment considers that the multicast member leaves the
multicast group, and thus deletes the multicast member. In this case, the equipment connected
to this port cannot receive the multicast services. If the member receives the response packet
within the aging time, re-set the count value.
Multicast Strategy
The RTN equipment determines the member relation in this network section according to the
received IGMP group member report packet. The range of the multicast groups can be restrained
through the ACL. By default, the ACL is not set. Thus, the host can be added to any multicast
groups.
Quick Deletion of the Member Port

When only one multicast service receive end is connected to the multicast member port, the
quick deletion function can be set on this port. In other words, when the member port receives
the deletion packet, it immediately deletes the member port, and it stops forwarding the query
packet for a specified group. During the channel switching, the multicast service management
equipment that should be connected to the terminal of the IPTV service such as the set top box
has this function.
If the port with the enabled quick deletion function connects to multiple multicast receive
members, when a member is deleted from the multicast group, the RTN equipment cuts the
multicast services. In this way, other members cannot continue to receive the multicast services.

Thus, when this function is used, you should make sure that only one multicast service receive
end is connected to this port.
28.3 Application of the IGMP Snooping

The IGMP Snooping enhances the resource utilization through multicast forwarding, enhances
the security of the U2000 through restriction on user access, and enhances the network reliability
through quick response to the link change.
Multicast Forwarding
The IGMP Snooping is configured on RTN-1 and RTN-2. When the multicast packets reach
RTN-1 or RTN-2, the packets are distributed at the port, which has the group member host in
the downstream.
Figure 28-2 Multicast forwarding
Internet
/Intranet
Source
Host 1 Host 2 Host3 Host 4 Host 5
Group member Group member Group member
Multicast
packets
Restriction on the User Access

Illegal users are prevent from using multicast services by configuring the attributes of the
multicast strategy, static multicast group, static router port and unknown multicast service

forwarding. As shown in Figure 28-2, the multicast group strategy is configured on RTN-1 and
RTN-2. In this way, the range of the group addresses that can be accessed by users through the
access control list (ACL) is set. Thus, the multicast packets that can be received by the user host
can be controlled.
Quick Response to the Link Change

When the topology of the network where the RTN equipment resides changes, the switching
equipment in the downstream of the RTN equipment should set up new forwarding table items
in minutes after receiving the subsequent multicast query packet. As a result, the multicast
services are interrupted for a long time. The IGMP Snooping notifies the change of the response
spanning tree topology and fast transmits the query packets for the router. In this way, the
switching equipment in the downstream can fast learn the multicast information and decrease
the service interruption time.
28.4 Configuring the IGMP Snooping Parameters

Parameters related to the IGMP Snooping include Enabled Protocol, Router Port Aging Time
(min), Maximum times of No Response from Multicast Members and Maximum Number
of Multicast Groups. Configure these parameters for the IGMP Snooping to work normally.
After configuring the IGMP Snooping parameters for multicast services that are created, you
can set some ports for the multicast service as quick leave ports. The multicast user on each
quick leave port can then switch the multicast service channels quickly.
Prerequisite
The E-LAN service is already created.
Procedure
Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab to configure the required parameters. Click Apply.
NOTE
When setting parameters, note the following:

l Enabled Protocol: Enable or disable the IGMP Snooping function.
l Router Port Aging Time(min): The value ranges from 1 to 120, and defaults to 8. Set this parameter
when the IGMP Snooping function is enabled.
l Maximum times of No Response from Multicast Members: The value ranges from 1 to 4, and
defaults to 3. Set this parameter when the IGMP Snooping function is enabled.
l Maximum Number of Multicast Groups: The value range depends on the maximum specification
of the equipment. Set this parameter when the IGMP Snooping function is enabled.
l Maximum Number of Multicast Groups Member: The value range depends on the maximum
specification of the equipment. Set this parameter when the IGMP Snooping function is enabled.

Step 3 Select the multicast service that requires setting of the quickly delete member port. The lower
pane lists the multicast service.
Step 4 Configure the parameters related to the quickly delete member port for the multicast service.
The parameters include VLAN ID, Port Type and Port. Double-click the parameters to modify
them.
NOTE
To set a port for a multicast service as a quickly delete member port, the port should have only one multicast
service user. Otherwise, different users on the port affect each other when receiving multicast services.
Step 5 Click Apply.
----End
28.5 Configuring the Router Management

The user manually creates the router port, through which the equipment responds to the packets
of the router for querying the IGMP Snooping. The router port is not aged automatically, and
thus always exists unless manually deleted.
Prerequisite
You must complete creation of the E-LAN service.
Procedure
Step 2 Click the Router Management tab. Click New to display the Create Router Port dialog box.
In the dialog box, set the required parameters and select the multicast router ports to be added.
NOTE

l Service ID: Select the ID of the service that belongs to the router port. In other words, Service ID is
the ID of the E-LAN service.
l VLAN ID: Set the VLAN ID according to the application. The VLAN ID ranges from 1 to 4094.
l Available Port: Select the corresponding port. The added ports must belong to the VLAN of the service.
Step 3 Click OK.
----End
28.6 Configuring the Route Member Port Management

To define the multicast scope, configure the route member ports. The static multicast member
ports are not aged automatically, and thus always exist unless manually deleted.
Prerequisite

E-LAN service is created.
Procedure
Step 2 Click the Route Member Port Management tab, and then click New to display the Create
Member Port dialog box.

NOTE

l Service ID: Select the ID of the service that belongs to the router interface. In other words, Service ID is
the ID of the E-LAN service.
l VLAN ID: Set the VLAN ID according to the application. The VLAN ID ranges from 1 to 4094.
l Multicast MAC Address: The value ranges from 01-00-5E-00-01-00 to 01-00-5E-7F-FF-FF.
l Available Port: Select the corresponding port. The added ports must belong to the VLAN of the service.
Step 4 Click OK.
----End
28.7 Configuring the Packet Statistics

Set the status of the protocol packet statistics to start, stop or clear the packet statistics. The
packet statistics data indicates the running status of multicast services.
Prerequisite
The route member port is configured.
Procedure
Step 2 Click the Packet Statistics tab, and set parameters for the IGMP protocol packet statistics. Then,
click Apply.

NOTE

l Service ID is the ID of the E-LAN service.
l The VLAN ID ranges from 1 to 4094.
l Port Type: The port type is V-UNI or V-NNI. This parameter cannot be set.
l Port: Select the corresponding port.
l Packet Statistic Status: The status is Stop, Start or Clear. The default status is Stop.
l IGMPv1 Query Packet Count: This parameter is of the query result, and thus cannot be set.
l IGMP Leaving Packet Count: This parameter is of the query result, and thus cannot be set.
l IGMPv1 Member Report Packet Count: This parameter is of the query result, and thus cannot be set.
l Unrecognized or Unprocessed Packet Count: This parameter is of the query result, and thus cannot be
set.
l Discarded Incorrect Packet Count: This parameter is of the query result, and thus cannot be set.
Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is
----End

Operation Guide for RTN NE Management 29 OAM Management
29 OAM Management
About This Chapter
Operation, administration and maintenance (OAM) is a network monitoring tool. Based on the
feedback of OAM, network administrators can find and locate network faults in time.
29.1 Configuring ETH OAM

Ethernet OAM detects and monitors the connectivity and performance of the trails of services
by using outband packets. Therefore, services are not affected.
29.2 Configuring the MPLS OAM
You can configure the MPLS OAM.
29.3 Configuring the PW OAM
This section describes how to configure the PW OAM.
29.4 Configuring ATM OAM
How to use the U2000 to configure ATM OAM is described.

29 OAM Management Operation Guide for RTN NE Management
29.1 Configuring ETH OAM

Ethernet OAM detects and monitors the connectivity and performance of the trails of services
by using outband packets. Therefore, services are not affected.
29.1.1 Feature Introduction

Ethernet OAM enhances the Ethernet Layer 2 maintenance to strongly support the service
continuity verification, service deployment commissioning and network fault locating. The
Ethernet board provides complete Ethernet OAM solutions according to the standards that are
defined in the IEEE 802.1ag and IEEE 802.3ah protocols.
29.1.2 Basic Concept
This topic describes certain basic concepts required for the application of Ethernet OAM
features.
29.1.3 Availability
The ETH-OAM feature requires the support of the applicable equipment and boards.
Ethernet OAM realizes different OAM operations through different OAM packets.
29.1.5 Using the IEEE 802.1ag OAM
By using the IEEE 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.
29.1.6 Using the IEEE 802.3ah OAM
By using the IEEE 802.1ag OAM, you can maintain the Ethernet link in a point-to-point manner.
29.1.1 Feature Introduction

Ethernet OAM enhances the Ethernet Layer 2 maintenance to strongly support the service
continuity verification, service deployment commissioning and network fault locating. The
Ethernet board provides complete Ethernet OAM solutions according to the standards that are
defined in the IEEE 802.1ag and IEEE 802.3ah protocols.
As a protocol based on the MAC layer, Ethernet OAM checks Ethernet links by transmitting
OAM protocol packets. Compared with the transmission medium, this protocol is independent.
The OAM packets are processed only at the MAC layer, having no impact at other layers in the
Ethernet. Moreover, as a low-rate protocol, the Ethernet OAM protocol occupies low bandwidth.
Thus, this protocol does not affect services carried on the link.
Compared with the traditional Ethernet maintenance and fault location, the features of Ethernet
OAM are as follows:
l As a low rate protocol, the Ethernet OAM protocol uses very little network bandwidth.
Hence, this function does not affect services transmitted by the link.
l You can perform the OAM on the services that are encapsulated in different formats by
using the Ethernet OAM, which is irrelevant to the Ethernet encapsulation formats. You
can perform the OAM, however, on only the services of the same encapsulation format by
using traditional test frames.
l The current frame test method is based on only the encapsulation format where the data of
the same type is contained. Thus, this test method is not applicable to other encapsulation
formats (such as GFP encapsulation format and HDLC encapsulation format) where the
data of different types is contained.

l The current port loopback function focuses on all packets at the port. Thus, the loopback
cannot be performed for a specific service selectively.
l Ethernet OAM can detect hardware faults.
l Ethernet OAM can detect and locate faults automatically.
The OptiX RTN equipment provides the Ethernet OAM solution based on the IEEE 802.1ag
and IEEE 802.3ah protocols, as shown in Figure 29-1.
Figure 29-1 Ethernet OAM solution
IEEE 802.3ah IEEE 802.1ag IEEE 802.3ah
Transmission Network
Client-side Ethernet Equipment
RTN Equipment
l IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. Based on
services, IEEE 802.1ag OAM realizes the end-to-end check by detecting each maintenance
domain successively. That is, it performs segmental management on each network segment
that is involved in the same service in the network.
l IEEE 802.3ah OAM focuses on the point-to-point Ethernet link maintenance between two
sets of directly-connected equipment in Ethernet in the first mile (EFM). IEEE 802.3ah
OAM does not focus on the specific service. It maintains the Ethernet point-to-point link
by performing OAM auto-discovery, link performance monitoring, fault check, remote
loopback and selfloop check.
29.1.2 Basic Concept

This topic describes certain basic concepts required for the application of Ethernet OAM
features.
29.1.2.1 IEEE 802.1ag OAM Management

IEEE 802.1ag OAM focuses on the maintenance of the end-to-end Ethernet links. By defining
the maintenance domain (MD), maintenance association (MA), and maintenance point (MP),
IEEE 802.1ag OAM can manage service flows by segment and by layer.
29.1.2.2 IEEE 802.1ag OAM Operation
The Ethernet board supports the IEEE 802.1ag Ethernet OAM operations as follows: continuity
check (CC), link trace (LT), loopback (LB), ping, alarm indication signal (AIS) activation, and
performance check.

29.1.2.3 IEEE 802.3ah OAM Operations

The Ethernet board supports the IEEE 802.3ah Ethernet OAM operations as follows: OAM auto-
discovery, link event notification, error frame monitoring, remote loopback, and self-loop test.
29.1.2.1 IEEE 802.1ag OAM Management

IEEE 802.1ag OAM focuses on the maintenance of the end-to-end Ethernet links. By defining
the maintenance domain (MD), maintenance association (MA), and maintenance point (MP),
IEEE 802.1ag OAM can manage service flows by segment and by layer.
As a protocol based on the MAC layer, the Ethernet service OAM detects Ethernet links by
transmitting OAM packets. The OAM packets are processed at only the MAC layer.
The Ethernet service OAM defines the following concepts.
l Maintenance domain (MD): The MD is a network that requires the OAM.
l Maintenance association (MA): The MA can be considered as a service-related domain,
which consists of many maintenance end points (MEPs) and Maintenance intermediate
points (MIPs).
l Maintenance point (MP): The MP include MEPs and MIPs.
Maintenance end point (MEP): The MEP is the transmitting and terminating points of
all OAM packets. It is relevant to services. In a network, the MA and MEP ID can
uniquely determine an MEP.
Maintenance intermediate point (MIP): For the non-standard protocol, the MIP can
respond to and forward LB and LT packets, but can only forward CC packets. For the
standard protocol, the MIP can forward CC and LB packets, but respond to and forward
LT packets.
Maintenance Domain
In a network, the network segments focused on by users, service providers and operators are
different. Thus, the management should be based on network segment to perform maintenance
on network segments where a service passes through in the network. At the same time, different
service traffics need be managed separately.
IEEE 802.1ag OAM realizes the Ethernet maintenance by performing the end-to-end check
based on the maintenance domain. For OAM, maintenance domain is the collection of all
maintenance points (MP) in a service application. The MPs include the maintenance association
end points (MEP) and maintenance association intermediate points (MIP).
For the management segment to be maintained, establish MEPs at two ends and set the range of
the maintenance domain. Moreover, establish MIPs at other positions in this management
segment. Perform the operations on these maintenance points, including MEPs and MIPs. Based
on relations and responses among these maintenance points, the state of the whole management
segment is under control. In this way, the fault detection and location are realized.
Maintenance Association
An MA is a part of an MD. An MD can be divided into one MA or multiple MAs.
In the network of a carrier, a VLAN is corresponding to a service instance. On the equipment,
a VLAN is corresponding to an MA or multiple MAs. By dividing MAs, you can check the
connectivity of the network that transmits a certain service instance and detect faults of the
network.

The level of an MA is the same as the level of the MD to which the MA belongs.
Maintenance Point
The maintenance point (MP) refers to function entity of IEEE 802.1ag OAM, including the
maintenance end point (MEP) and maintenance intermediate point (MIP).
Each maintenance point has a maintenance point identification (MPID), and this ID is unique
in the entire network. The information of each maintenance point is recorded in the MAC address
table, maintenance point table and route table. The key contents contained in the MP
configuration information are the service type, service ID and VLAN tag. In the case of non-
standard MP, once a maintenance point is created successfully, it transmits the protocol packets
where the MP information is contained to the entire network periodically in the form of
broadcasting. After receiving these protocol packets, other maintenance points record the
information for backup.
l Maintenance association End Points

The MEP defines the start position of the maintenance domain. The MEP is the transmitting
and terminating points of all OAM packets. It is relevant to services. In a network, the MA
and MEP ID can uniquely determine an MEP.
As shown in Figure 29-2, the MEP is always marked by an arrow. The direction of arrow
indicates the direction of the MEP.
An MEP has following features.
It must allow all service packets to pass through the point, neglecting their directions.
It must check all OAM message packets that pass through the MEP in the direction of
the arrow.
It allows the OAM message packets whose levels are higher than the level of this
MEP layer to pass through the point directly without further check.
It terminates all message packets whose levels are lower than or equals to the level
of this MEP layer.
It must check all OAM message packets that pass through this MEP in the reverse
direction of the arrow.
It allows the OAM message packets whose levels are higher than the level of this
MEP layer to pass through the point directly without further check.
It processes the OAM message packets that belong to this MEP layer.
It terminates all message packets whose levels are lower than the level of this MEP
layer.
It generates the OAM message packets whose level is equal to the MEP level at this
layer, and transmits these packets in the specified direction.
l Maintenance association Intermediate Points
As shown in Figure 29-2, the MIP is always marked by an ellipse. Moreover, the MIP has
no direction.
An MIP should have following features.
It must allow all service packets to pass through this MIP.
It must check all OAM message packets that pass through this MIP.
It must allow the OAM message packets whose levels are higher than the level of this
MEP layer to pass through the MIP.

According to some special operational codes or destination MAC addresses, choose one
of the following processing methods.
Transparent transmission
Transparent transmission and processing
Extract and process all OAM message packets that belong to this MIP layer
According to some special operational codes, discard all OAM message packets whose
level is lower than the level of this MIP layer.
NOTE
Only the MEP can initiate the OAM operations, while the MIP cannot initiate any OAM operation or send
any OAM packet.
Layered Management
IEEE 802.1ag OAM adds the management level fields to OAM protocol packets. In this way,
the layered management is realized. The higher management domain can cross the lower
management domain, but the lower management domain cannot cross the higher management
domain. Based on such layered management, the maintenance of a service traffic can be realized
segmentally. Moreover, the management of different service traffics can be realized as well.
Figure 29-2shows the logical diagram of the maintenance domain layer relation.
Figure 29-2 Logical diagram of maintenance domain layers

CE Operator A Provider Bridges Operator B Provider Bridges CE
a b c d e f
Customer ME Level
Service Provider ME Level
Operator ME Level
Physical ME Level
Bridge with Bridge Ports

Logical path of
Maintenance End Ports CFM Messages
Maintenance Intermediate Points Maintenance
Entities
AIS Convergence Function
Currently, the protocol supports the eight-layer division from layer 0 to layer 7. Eight
maintenance entities (ME) levels correspond to the user, supplier or operator accordingly.
l ME levels for the user: 7, 6, 5

l ME levels for the supplier: 4, 3

l ME levels for the operator: 2, 1, 0

Layer levels from the higher to the lower: user ME level > Supplier ME level > Operator ME
level.
The dashed lines in the diagram show the logic channels where IEEE 802.1ag OAM packets
pass through. Methods for maintenance points at different layers to process OAM protocol
packets are as follows.
l For the OAM protocol packets whose level is higher, the maintenance point processes them
transparently.
l For the OAM protocol packets whose level is lower, the maintenance point discards them
directly.
l For the OAM protocol packets whose level is the same, the maintenance point gives
response or ends the packets accordingly to messages types of the OAM protocol packets.
29.1.2.2 IEEE 802.1ag OAM Operation

The Ethernet board supports the IEEE 802.1ag Ethernet OAM operations as follows: continuity
check (CC), link trace (LT), loopback (LB), ping, alarm indication signal (AIS) activation, and
performance check.
Continuity Check
The connectivity between maintenance end points (MEPs) are detected through continuity check
messages (CCMs) that are transmitted between MEPs periodically. This detection is named as
continuity check (CC). You can check the link status in one direction by performing the CC.
The application scenario is as follows: The link status is checked in real time.
l After receiving the CCM packets from the source MEP, the sink MEP directly enables the
CC function that focuses on this source MEP.
l If the sink MEP fails to receive the CCM packets from the source MEP within a check
period, the non-standard MP reports the EX_ETHOAM_CC_LOS alarm automatically
until the link is recovered, and the standard MP reports the ETH_CFM_LOS alarm. That
is, the sink MEP does not clear the alarm until it receives the CCM packets from the sink
MEP.
Loopback Test
The loopback (LB) can be used to test the state of any MP link from the source MEP to the
maintenance domain.
The application scenario is as follows: The location or check is performed on one end.
l The loopback (LB) can be used to test the state of any node link from the source to the
maintenance domain. For the non-standard MP, as the sink MP can be the MIP, the loopback
can be used to locate the faults.
l Compared with the continuity test, the loopback test is not a continuous test. Thus, you
need start the test manually each time.
Link Trace Test

Compared with the LB test, the link trace (LT) test provides enhanced fault locating capability.
That is, the faulty network segment can be located the first time in the LT test.

The application scenario is as follows: The fault is located on site.
PING
OAM ping test provides the online test. By using this function, you can simulate the packet loss
ratio and delay period of a service, which are caused by bit errors. Besides the continuity test,
the OAM-Ping test further manages the performance of the Ethernet link at the MAC layer.
The application scenario is as follows: The service performance is checked in real time.
l The OMA_Ping test provides a method to test the in-service packet loss ratio and hold-off
time that result from bit errors. Compared with the continuity test, the OAM_Ping test
provides more detailed and accurate OAM information.
l In this case, the OAM not only ensures the service continuity, but also detects the packet
loss and service delay to a greater extent.
AIS Activation
The alarm indication signal (AIS) is used to report errors to a superstratum node during Ethernet
OAM. When the AIS is active, errors can be reported. If the AIS is inactive, errors cannot be
reported.
Performance Check
After the connectivity between the MPs of the processing boards of Ethernet services is checked,
the performance check realizes the on-line test of the packet loss ratio and delay time of the
services.
29.1.2.3 IEEE 802.3ah OAM Operations

The Ethernet board supports the IEEE 802.3ah Ethernet OAM operations as follows: OAM auto-
discovery, link event notification, error frame monitoring, remote loopback, and self-loop test.
OAM Auto-Discovery
By exchanging the information OAM protocol data unit (OAMPDU) periodically, the equipment
at local end is informed that the opposite end supports the IEEE 802.3ah OAM protocol.
The application scenario is as follows: OAM auto-discovery is a prerequisite to realize the link
performance monitoring and remote loopback. The following functions are available at the port
only when the OAM auto-discovery succeeds: link performance monitoring and loopback. If
the OAM auto-discovery fails, the ETHOAM_DISCOVER_FAIL alarm is reported.
Link Performance Monitoring

Link performance monitoring is used to monitor the bit error performance (error frames or error
signals). When the local end detects that the bit errors cross the threshold, the bit error event is
transmitted to the opposite end over the specified OAMPDU. In this case, the opposite end
reports the alarm accordingly.
To perform performance statistics from different aspects, the link performance monitoring is
classified into bit error frame event monitoring, error frame second event monitoring, error frame
period event monitoring.

l Triggering condition of error frame events: Within a period of the error frame monitor
window, the number of actually received error frames is larger than the configured threshold
value.
NOTE
The period of the error frame monitor window indicates the time period for each error frame statistics.
l Triggering condition of error frame second events: Within the specific seconds, the detected
error frame seconds is larger than defined threshold value.
NOTE
When the error frame number is larger than 0 within a second, this second is called an error frame
second.
l Triggering condition of error frame period events: Among the received frames of a specific
amount, the number of error frames is larger than defined threshold value.
Application scenarios are as follows:
l The link performance monitoring function is used to precisely analyze and monitor the link
performance within a specific range.
l According to actual requirements, you can configure window values and threshold values
of three link performance events respectively on the U2000. In this case, whether the link
performance degrades to the threshold can be detected.
Remote Loopback
The OAM entity at the local end transmits the loopback control OAMPDU packets to the remote
OAM for applying for the loopback. According to loopback data analysis, the fault locating and
link performance test are performed. The IDU 620 do not support responding the remote
loopback, the IDU 605 support responding the remote loopback.
The application scenario is as follows: The loopback is a method to locate the faults and test the
performance. Compare the number of transmitted packets with that of received packets in
loopback. The result can be used to detect link performance and link faults in this link
bidirectionally from the loopback initiation end to the loopback response end.
Self-Loop Test
After the self-loop test function is enabled on an Ethernet service processing board, you can
detect the self-loop that occurs when the fiber in the transmit direction of a port is connected to
the same port in the receive direction, and the intra-board loopback between two connected port
on the same board.
The application scenario is as follows: When the self-loop function is enabled at all ports on the
equipment, the ring network that is available during the networking can be detected. Moreover,
the ETHOAM_SELF_LOOP alarm is reported.
29.1.3 Availability
The ETH-OAM feature requires the support of the applicable equipment and boards.

Table 29-1 Availability of the ETH-OAM Feature

EMS6 RTN 620
EFP6
EM4T RTN 605
Table 29-2 Availability of the ETH-OAM Feature

IFU2
IFX2
EM4T
RTN 910/950
EM4F
EM6T
EM6F
CSHA
CSHB RTN 910
CSHC

Ethernet OAM realizes different OAM operations through different OAM packets.
29.1.4.1 802.1ag OAM

When the IEEE 802.1ag OAM protocol is used, OAM operations are realized through the
exchange of OAMPDUs between MPs.
29.1.4.2 802.3ah OAM
When the IEEE 802.3ah OAM protocol is used, OAM operations are realized through the
exchange of OAMPDUs between the equipment at both ends of a link.
29.1.4.1 802.1ag OAM

When the IEEE 802.1ag OAM protocol is used, OAM operations are realized through the
exchange of OAMPDUs between MPs.
Figure 29-3 shows the IEEE 802.1ag OAMPDU.

Figure 29-3 IEEE 802.1ag OAMPDU
OAM Mac Destination Address
OAM Mac Source Address
Ether Type(VLAN) VLAN Tag

Ether Type(OAM) VER OAM Type
Type Length
Service-ID
OAM Date
Frame Check Sequence
l OAM Mac destination address: Indicates the MAC address of the destination MP.
l OAM Mac source address: Indicates the MAC address of the source MP.
l Ether type (VLAN): Indicates the Ethernet data type, such as 0x8100.
l VLAN tag: Indicates the VLAN value of the service traffic.
l Ether Type (OAM): Indicates the packet type of the ETH-OAM protocol. The standard
IEEE The packet type of 802.1ag OAM protocol is 0x8902. The non-standard (Huawei,
Draft 3.0)IEEE The packet type of 802.1ag OAM protocol is 0x8809.
l OAM type: Indicates that the MP differs and responds to various OAM operations
according to types of OAM packets. OAM For mapping relation between values and OMA
packet types, refer to Table 29-3.
Table 29-3 Mapping relation between values and OMA packet types (non-standard MP)
OAM Type OAMPDU Usage
1 Loopback message (LBM) Loopback test
2 Link trace message (LTM) Link trace test
3 Continuity check message (CCM) Continuity test
4 MAC query MAC address query
5 Loopback return (LBR) Loopback test
6 Link trace reply (LTR) Link trace test
7 MacAck MAC address confirmation

notification
8 MacBroadcast MAC address broadcast

Continuity Check
The source MEP constructs the continuity check message (CCM) packets and transmits them
periodically. After receiving the CCM packets from the source MEP, the sink MEP directly
enables the CC function that focuses on this source MEP.
If the sink MEP fails to receive the CCM packets from the source MEP within a check period,
it reports the alarm automatically until the link is recovered. That is, the sink MEP does not clear
the alarm until it receives the CCM packets from the sink MEP.
As shown inFigure 29-4, the CC function of the MEP1 is enabled. The MEP1 transmits the
CCM packets externally. After receiving the first CCM packet, the MEP2, MEP3 and MEP4 in
the same maintenance domain start the timer respectively to receive all CCM packets from the
MEP1 periodically. Once the link is faulty, the sink MEP fails to receive the CCM packets within
a check period. In this case, the sink MEP reports the EX_ETHOAM_CC_LOS alarm. The alarm
is not cleared until the link is recovered.
Figure 29-4 Continuity check diagram
MEP1
VB
MEP2
MEP4 VB
VB MEP3
When the CC function is enabled at MEP1, MEP2, MEP3 and MEP4 at the same time, each
MEP is both the source end and sink end for the CC function. In this way, the bidirectional
continuity test is realized.
NOTE
Only the MEP can enable the continuity check and be the receive respond end for the check.
Loopback Test
Based on the bidirectional service, the loopback is a test performed manually at a time. The
source MEP constructs the loopback message (LBM) packets and adds the destination MP (MIP
or MEP) IDs to the packets. When the packets are transmitted, the timer is started.
After receiving the LBM packets, the sink MP constructs the loopback return (LBR) packets
and transmits them back to the source MEP. In this case, the loopback succeeds. If the source
MEP timer expires and fails to receive the LBR from the sink MP, the loopback fails.
As shown in Figure 29-5, the MEP1 transmits the LBM packets to the sink MEP2. After
receiving the packets, the MIP2 and MIP3 in the same maintenance domain detect that the sink

MPIDs contained in the packets are different from those of them. In this case, the MIP2 and
MIP3 transparently transmit the packets. After receiving the packets, the sink MEP2 transmits
the LBR packets back to the source MEP1. At this moment, the loopback is complete.
Figure 29-5 Loopback test diagram
MEP1 MIP2 MIP3 MEP4
LBM
LBR
NOTE
For the non-standard IEEE 802.1ag OAM, only the MEP can initiate the loopback test, while both the MEP
and MIP can be the receive end in the test.
Link Trace Test

The source MEP constructs the link trace message (LTM) packets and adds the ID of the sink
MEP to the packets for transmission. At the same time, the timer is started.
All MIPs that belong to this maintenance domain in the link continuously transmit the packets
to the sink MEP. At the same time, a link trace replay (LTR) packet is transmitted back to the
source MEP.
After the sink MEP receives the LTM packets, the packet transmission is complete. Then the
sink MEP transmits LTR packets back to the sink. In this case, the link trace test is successful.
If the source MEP timer expires and fails to receive the LTR from the sink MEP, the loopback
fails.
Additionally, the parameter hop is added to the packet that is transmitted back. The hop is used
to indicate the MP ID of the returned maintenance point in the link during the link trace test. If
the first MP passed through the LTM is on the same board with the source MP, the hop starts
from 0 and accumulates in the sequence. Otherwise, the hop starts from 1.
The function of the link trace test is similar to the function of the loopback test. The difference
lies in the response to the LBM frames. In the loopback test, only the sink MP responds to the
LBM frames. In the link trace test, all MPs in the link respond to the LTM frames. According
to these response messages, all MIPs that are involved from the source MEP to the destination
MEP can be recognized, as shown in Figure 29-6.

Figure 29-6 Link trace test diagram
MEP1 MIP2 MIP3 MEP4

LTM LTR
1 4
LTR LTM LTR LTM

2 3
1. The source MEP1 transmits the LTM packets to the destination MEP4.
2. After receiving the LTM packets, the MIP2 transmits the LTR packets to the source MEP1
and forwards the LTM packets at the same time.
3. After receiving the LTM packets, the MIP3 transmits the LTR packets to the source MEP1
and forwards the LTM packets at the same time.
4. After receiving the LTM packets, the destination MEP4 concludes the LTM packets and
transmits the LTR packets to the source MEP1.
NOTE
Only the MEP can initiate the link trace test and be the termination of the test.
OAM_Ping Test
The OAM_Ping test includes:
l MPID-Ping: In the case that both the Ethernet service processing boards of Huawei
equipment at two ends support the IEEE 802.1ag OAM protocol, the ping test is initiated
from the maintenance point on the local Ethernet service processing board to that on the
opposite board.
l IP-Ping: In the case that both the equipment at two ends supports the ARP protocol and
ICMP protocol, only the Huawei equipment can initiate the ping test. Moreover, the Huawei
equipment does not respond to the ping test of the opposite end.
The transmit end in OAM_Ping acquires the IP address of the maintenance point first, and then
constructs the ARP packets and ICMP packets for transmission. The maintenance point that
receives the ARP packets or ICMP packets analyzes the packets and then transmits the response
packets back to the transmit end. After receiving the response packets, the OAM_Ping transmit
end reports the test results of the OAM_Ping according to the information contained in the
response packets. The results include the packet loss ratio and delay information.
29.1.4.2 802.3ah OAM

When the IEEE 802.3ah OAM protocol is used, OAM operations are realized through the
exchange of OAMPDUs between the equipment at both ends of a link.
Figure 29-7 shows IEEE 802.3ah OAMPDUs.

Figure 29-7 IEEE 802.3ah OAMPDU

Octets
6 MAC Destination Address
6 MAC Source Address
2 Type
1 Subtype
2 Flags Field
1 Code
42-1496 Data/Pad Field
4 Frame Check Sequence
l Mac Destination Address: Indicates the low-speed protocol multicast address whose value
is fixed to 0x01-80-C2-00-00-02.
l Mac Source Address: Indicates the MAC address of the port.
l Type: Indicates the low-speed protocol type whose value is fixed to 0x8809.
l Subtype: Indicates that the specified type of the low-speed protocol is IEEE 802.3ah OAM,
which is fixed to 0x03.
l Flags Filed: Includes some important state information such as link fault, dying gasp,
critical event. The realization of the fault locating depends on the state information
mentioned previously.
l Code: Identifies the IEEE 802.3ah OAM protocol packets of different types. The main
packet types are information OAMPDU, event notification OAMPDU and loopback
control OAMPDU. They are corresponding to OAM auto-discovery, link performance
monitoring and remote loopback respectively. For the mapping relation between code
values and OAM packet types, see Table 29-4.
Table 29-4 Mapping relation between code values and OAM packet types
Code OAMPDU Usage
0x00 Information Exchanges the OAM information at the

local end and opposite end.
0x01 Event notification Notifies the opposite equipment that bit

error performance events occur on the
link.

Code OAMPDU Usage
0x02 Variable request Applies for one or multiple specific MIB

information.
0x03 Variable response Responds to one or multiple specific MIB

information.
0x04 Loopback control Enables or disables the remote OAM

loopback.
0x05-0x Reserved Reserved.

FD
0xFE Organization specific Indicates the selective extended

OAMPDU function used by different
equipment manufacturers.
0xFF Reserved Reserved.
l Data/Pad Field: Indicates the OAMPDU data whose fields can be extended, with a length
range from 42 bytes to 1496 types. When the OAMPDU packet length is less than the
minimum 64 bytes, the extended bytes are contained in the field.
l Frame check sequence
Auto-Discovery
As shown in Figure 29-8, the Code filed of the OAMPDU is 0x00. This indicates that the
OAMPDU is the information OAMPDU and used for OAM auto-discovery.

Figure 29-8 Packet format of the information OAMPDU

Fixed
Octets Fields Values
1 Information Type 0x01
1 Information Length 0x10
1 OAM Version 0x01
2 Revision
1 State
Octets Fields Fixed Values 1 OAM Configuration
2 OAMPDU Configuration
6 Destination Address 01-80-c2-00-00-02
3 OUI
6 Source Address 4 Vendor Specific Information
2 Length/Type 88-09
1 Subtype 0x03
LOCAL INFORMATION TLV
2 Flags
1 Code 0x00 1 Information Type 0x02
1 Information Length 0x10
42-1496 Data/Pad
1 OAM Version 0x01
4 FCS 2 Revision
1 State
INFORMATION 1 OAM Configuration
OAMPDU 2 OAMPDU Configuration
3 OUI
4 Vendor Specific Information
REMOTE INFORMATION
TLV
1 Information Type 0xFE

1 Information Length
1 OUI
2 Organization Specific Value
ORGANIZATION
SPECIFIC
INFORMATION TLV
The Data field of the information OAMPDU includes local information type-length-value (TLV)
domain and remote information type-length-value (TLV) domain. A OAM configuration byte
is contained in the TLV domain. When the link is normal, successful OAM auto-discovery
depends on information of bit digits in the OAM configuration bytes. Also, the information of
bit digits decides what functions are performed after OAM auto-discovery succeeds.
Table 29-5 lists details of OAM configuration bytes.

Table 29-5 Details of OAM configuration bytes

Bit Digit Name Description
7 to 5 Reserved Sets reserved bits to 0 when

the OAMPDU is transmitted
and ignores these bits in
receiving.
4 Variable Retrieval l Sets the value to 1, which

indicates that the data
terminal equipment
(DTE) supports the
transmission of the
variable response
OAMPDU.
l Sets the value to 0, which
indicates that the DTE
does not support the
transmission of the
variable response
OAMPDU.
3 Link Events l Sets the value to 1, which

supports the monitoring
on bit error performance
(error frames or error
signals) of links. When bit
errors cross the threshold,
the bit error event is
transmitted to the
opposite end over the
specified OAMPDU.
monitoring on bit error
performance of links.

Bit Digit Name Description
2 OAM Remote Loopback l Sets the value to 1, which

Support indicates that the DTE
supports the loopback
request of the remote end.
When the loopback
command is issued at the
remote end, the local end
transmits all packets back
to the remote end for
loopback, excluding
OAMPDU packets.
remote loopback.
1 Unidirectional Support l Sets the value to 1, which

indicates that the local
end can transmit the
OAMPDU packets to the
local end when the fault
occurs in the receive
direction.
indicates that the local
end cannot transmit the
OAMPDU packets to the
local end when the route
is faulty in the receive
direction.
0 OAM Mode l Sets the value to 1, which

indicates that the OAM
mode of the DTE is set to
Active.
indicates that the OAM
mode of the DTE is set to
Passive. When the local
end works in the passive
mode, some OAM
functions cannot be
enabled. For details, see
Table 29-6.

Table 29-6 Mapping relation between OAM working modes and OAM functions
OAM Capability OAM Mode
Active Mode Passive Mode
Initiates OAM auto- Yes No

discovery process
Reacts to OAM auto- Yes Yes

discovery process
Required to send information Yes Yes

OAMPDUs.
Permitted to send event Yes Yes

notification OAMPDUs
Permitted to send variable Yes No

request OAMPDUs
Permitted to send variable Yes Yes

response OAMPDUs
Permitted to send loopback Yes No

control OAMPDUs
Reacts to loopback control Yes Yes

OAMPDUs
Permitted to send Yes Yes

organization specific
OAMPDUs
When the IEEE 802.3ah OAM protocol is enabled for the port on the Ethernet service processing
board, the information OAMPDU is broadcast periodically. At the same time, the information
OAMPDU from the opposite port is received and processed. In this way, two peer ends exchange
the OAM information (including OAM configuration information and OAM state information)
to establish the OAM connection between two ends.
Link Performance Monitoring

As shown in Figure 29-9 the Code filed of the OAMPDU is 0x01. This indicates that the
OAMPDU is the event notification OAMPDU and used for notifying the bit error performance
event mutually.

Figure 29-9 Packet format of event notification OAMPDU

Fixed
Octets Fields Values
2 Sequence Number
SEQUENCE NUMBER
1 Event Type 0x01
1 Event Length 0x28
2 Event Time Stamp
8 Errored Svmbol Window
8 Errored Svmbol Threshol
8 Errored Svmbol
8 Error Running Total
4 Event Running Total
ERRORED SYMBOL PERIOD EVENT
1 Event Type 0x02
Octets Fields Fixed Values 1 Event Length 0x1A
6 Destination Address 01-80-c2-00-00-02 2 Event Time Stamp
6 Source Address 2 Errored Frame Window
4 Errored Frame Threshol
2 Length/Type 88-09 4 Errored Frames
1 Subtype 0x03 8 Error Running Total
2 Flags
ERRORED FRAME ENENT
1 Code 0x01 1 Event Type 0x03
42-1496 Data/Pad 1 Event Length 0x1
2 Event Time Stamp C
4 FCS
4 Errored Frame Window
ENENT 4 Errored Frame Threshol
NOTIFICATION 4 Errored Frames
OAMPDU
ERRORED FRAME PERIOD EVENT
1 Event Type 0x04
1 Event Length 0x12
2 Event Time Stamp
2 Err.Fr.Sec.Sum.Window
2 Err.Fr.Sec.Sum.Threshol
2 Err.Fr.Sec.Summary
ERRORED FRAME SECONDS SUMMARY
1 Event Type 0xF
1 Event Length E
3 OUI
x Organization Specific Value
ORGANIZATION SPECIFIC EVENT
To perform performance statistics from different aspects, the link performance monitoring is
classified into bit error event monitoring, error frame second event monitoring, error frame
period event monitoring.
l Triggering condition of error frame events: Within a period of the error frame monitor
window, the number of actually received error frames is larger than the configured threshold
value.

l Triggering condition of error frame second events: Within the specific seconds, the detected
error frame seconds is larger than defined threshold value.
l Triggering condition of error frame period events: Among the received frames of a specific
amount, the number of error frames is larger than defined threshold value.
When the IEEE 802.3ah OAM protocol is enabled at a port, the protocol queries the RMON
statistic count of the hardware chip periodically to acquire the information such as the number
of accurate packets and the number of error packets. You can find out whether the preceding
three performance events occur or not according to corresponding processing of these
information. In the case that a performance event occurs, the opposite end is informed of this
event over the event notification OAMPDU. After receiving the notification, the opposite
equipment reports the ETHOAM_RMT_SD alarm for maintenance personnel to perform
troubleshooting.
Remote Loopback
As shown in Figure 29-10, the code filed of the OAMPDU is 0x04. This indicates that the
OAMPDU is the loopback control OAMPDU and used for the loopback test.
Figure 29-10 Packet format of the loopback control OAMPDU

Octets Fields Fixed Values
6 Destination Address 01-80-c2-00-00-02
6 Source Address
2 Length/Type 88-09
Fixed
1 Subtype 0x03 Octets Fields Values
2 Flags 1 Remote Loopback Command 0x01
1 Code 0x04 ENABLE REMOTE
1+41 Data/Pad LOOPBACK COMMAND
4 FCS
1 Remote Loopback Command 0x02
LOOPBACK
DISABLE REMOTE
CONTROL OAMPDU
LOOPBACK COMMAND
The loopback transmit end transmits the loopback control OAMPDU packets to the opposite
end first. After receiving the packets, the opposite end checks whether it can respond to the
remote loopback first. If it can respond to the remote loopback, the opposite end starts remote
loopback and transmits a response packet back to the end that initiates the loopback at the same
time.
After receiving the response packets from the response end, the transmit end analyzes the packets
to confirm that the opposite end is in the response loopback state. Then the transmit end starts
the loopback. In this way, the whole process of loopback initiation is complete.
Self-Loop Test
The self-loop test is a function developed by Huawei on the basis of IEEE 802.3ah protocol.

The self-loop test packets are constructed as the IEEE 802.3ah OAM protocol packets, with a
packet type of protocol reservation type 6. The first eight significant reserved bits in the flag
fields are used to carry the ID of the transmit port.
When the self-loop test is enabled at a port, the specified self-loop check packets are transmitted
from the port. One packet is transmitted each second.
When a port receives the self-loop check packets, it compares the source MAC address carried
in the packets with its own MAC address. If the former MAC address is the same with the later,
it indicates that the local port and the opposite port are located in the same Ethernet service
processing board. At this moment, further compare IDs of two ports. If the IDs are the same,
they are the same port actually. In this case, this indicates the port self-loop. If the IDs are
different, it indicates the intra-board port self-loop.
29.1.5 Using the IEEE 802.1ag OAM

By using the IEEE 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.
29.1.5.1 Creating MDs

A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of
different levels and scopes can provide differentiated OAM services to users.
29.1.5.2 Creating MAs
A maintenance domain (MD) can be divided into several independent maintenance associations
(MA). By creating MAs, operators can associate specific Ethernet services with the MAs for
easy Ethernet OAM operation.
29.1.5.3 Creating MPs
The functions of the IEEE 802.1ag OAM can be used only after MPs are created.
29.1.5.4 Performing a Continuity Check
After the continuity check (CC) test, the unidirectional link status can be checked automatically
and periodically. After the CC test is started at the source, if the link is fault, the source equipment
reports the EX_ETHOAM_CC_LOS(Huawei MP) or ETH_CFM_LOS(Standard MP) alarm.
29.1.5.5 Performing a Loopback Check
During a loopback (LB) check, you can check the bidirectional connectivity between the source
MEP and any MP in the same traffic stream.
29.1.5.6 Performing a Link Trace Check
Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate
faults. That is, the faulty network segment can be located through only one test.
29.1.5.7 Activating the AIS(RTN 600)
After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the
AIS packet to superstratum MP for the notification of the fault.
29.1.5.8 Performing a Ping Test(RTN 600)
By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the
processing board of an Ethernet service and the data communications equipment, such as a switch
and router, the packet loss ratio of a service, and the delay time.
29.1.5.9 Performing Performance Detection(RTN 600)
the performance detection realizes the on-line test of the packet loss ratio and delay time of the
services.

29.1.5.1 Creating MDs

A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of
different levels and scopes can provide differentiated OAM services to users.
Prerequisite
The board that supports the creation of the MD must be created.
Procedure
1. In the NE Explorer interface, select an NE, and choose Configuration > Ethernet
Maintenance > Ethernet Service OAMfrom the Function Tree.
2. In the right-hand pane, click OAM Configuration to display the OAM Configuration
dialog box.
NOTE
In this user interface, you can maintain or delete OAM MDs.

1. In the NE Explorer interface, select an NE, and choose Configuration > Ethernet OAM
Management > Ethernet Service OAM Managementfrom the Function Tree.
Step 3 Click New and select Create MD from the drop-down list.
Step 4 In the New Maintenance Domain dialog box displayed, configure the corresponding
parameters.
Step 5 ClickApply.
Step 6 Click Close.
----End

29.1.5.2 Creating MAs

A maintenance domain (MD) can be divided into several independent maintenance associations
(MA). By creating MAs, operators can associate specific Ethernet services with the MAs for
easy Ethernet OAM operation.
Prerequisite
Ethernet services must be already created.
The MD must be created.
Procedure
1. In the NE Explorer interface, select an NE, and choose Configuration > Ethernet
Maintenance > Ethernet Service OAMfrom the Function Tree.
2. Click OAM Configuration in the right window to display the OAM Configuration dialog
box.
NOTE
In this user interface, you can create or delete OAM maintenance Association (MAs).
3. Click New, select Create MA from the drop-down list.
4. In the dialog box of New Maintenance Association displayed, configure the OAM
parameters.
5. ClickApply. The Operation Result dialog box is displayed, indicating that the operation
was successful.
6. Click Close.
1. In the NE Explorer, click NE and choose Configuration > Ethernet OAM
Management > Ethernet Service OAM Managementfrom the Function Tree.
2. Click New. Select New Maintenance Association to display the New Maintenance
Association dialog box.
3. Set the parameters.
4. Click Apply. The Operation Result dialog box is displayed, indicating that the operation
was successful.
5. Click Close.
----End

29.1.5.3 Creating MPs

The functions of the IEEE 802.1ag OAM can be used only after MPs are created.
Prerequisite
The Ethernet service must be created and activated.
The MA and MD must be created before creating a stadard MP.
Precaution
In an OAM test, all maintenance points that are involved in the operating of the same service
flow must be in the same maintenance domain. In an existing maintenance domain involved in
the same service flow, creating a maintenance point of the same level or a higher level may
damage the existing maintenance domain. As a result, the OAM test fails.
Procedure
Maintenance > Ethernet Service OAM from the Function Tree.
2. Click New and the Create MP dialog box is displayed. Complete the information.
NOTE
l VLAN ID: Leave this field blank for PORT services. For PORT+VLAN services, set the VLAN
ID of the services to be monitored.
l Service Direction: Only MEPs have the directions.
3. Optional: Click Advanced. In the dialog box displayed, set the corresponding parameters
and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configuration.
l Activate the CC and configure the sending period of the CC test.
l Set the timeout time for the LB or LT test.
4. Click OK. A prompt is displayed indicating that the operation is successful. Click Close
to finish the operation.
Step 2 In the case of RTN 900 NEs: Creating a MEP Maintenance Point

NOTE
Ethernet OAM detects the connectivity of an channel based on the maintenance end points (MEP) at two
ends of the channel. MEP is the source and sink of all the Ethernet OAM packets and it is the end point
that forms the maintenance association (MA). After an MEP is successfully created, users can check the
connectivity of a segment within an MA.
Management > Ethernet Service OAM Management from the Function Tree.
2. Click New. Select New MEP Point to display the New MEP Maintenance Point dialog
box.
NOTE
l Direction: Ingress indicates that packets are transported to the network side. Egress indicates that
packets are transported to the user side.
l CC Status: When it is set as Active, the link can be checked in a real-time manner.
was successful.
5. Click Close.
Step 3 In the case of RTN 900 NEs: Adding a Remote MEP of the MA
NOTE
This section describes how to add a remote maintenance end point (MEP) of the maintenance association
(MA). When processing OAM packets, the remote MEP checks whether the OAM packets are transmitted
by the MEP in the same MA.
2. Click OAM and choose Manage Remote MEP Point from the drop-down menu. The
Manage Remote Maintenance Point dialog box is displayed.
3. Click New and the Add Maintenance Association Remote Maintenance Point dialog
box is displayed.
is successful.
6. Click Close.
----End
29.1.5.4 Performing a Continuity Check

After the continuity check (CC) test, the unidirectional link status can be checked automatically
and periodically. After the CC test is started at the source, if the link is fault, the source equipment
reports the EX_ETHOAM_CC_LOS(Huawei MP) or ETH_CFM_LOS(Standard MP) alarm.
Prerequisite
The MEP maintenance point must be created.
Only the MEP can have the CC test enabled and work as the receiving and responding end in
the test.

Context
l During the CC check, the source MEP constructs and transmits CC frames periodically.
The destination MEP receives the CC frames and starts the CC check. If the destination
MEP does not receive the CC frames from the source within a specified period of time (for
example, 3.5 times the transmit period), the standard MP automatically reports the
ETH_CFM_LOS alarm and the Huawei MP automatically reports the
EX_ETHOAM_CC_LOC alarm.
l Performing a CC check does not affect the service.
Procedure
1. In the NE Explorer, click an Ethernet board and choose Configuration > Ethernet
2. Select the node that you want to monitor, click OAM Operation and select Activate
CC. A prompt is displayed indicating that the operation is successful. Click Close.
TIP
l Alternatively, you can select a node, right-click, and then choose Activate CC from the shortcut
menu to start the CC test.
l You can select a node, right-click, and then choose Inactivate CC from the shortcut menu to
stop the CC test.
NOTE
Before you perform the check, set an appropriate CCM Sending Period (ms) as required.

2. Select Maintenance Domain, and select Maintenance Association. Select MEP Point.
3. Click OAM and choose Activate CC from the drop-down menu, The Operation Result
dialog box is displayed indicating that the operation is successful.
4. Click Close.
----End
29.1.5.5 Performing a Loopback Check

During a loopback (LB) check, you can check the bidirectional connectivity between the source
MEP and any MP in the same traffic stream.
Prerequisite
The source and sink MEPs, and MIPs in the same maintenance domain must be created.

Only MEPs can initiate the LB test, and the MEP can work as the receive end in the test. For
the non-standard protocol, the MIP also can work as the receive end in the test.
The CC function must be enabled before the LB test can be performed on a standard MP.
Context
During the LB check, the source MEP constructs and transmits the LBM frames and starts the
timer. If the destination MP receives the LBM frames, it sends the LBR frames back to the source
MEP. This indicates that the loopback is successful. If the source MEP timer times out, it
indicates that the loopback fails.
Procedure
2. Select the node that you want to monitor, click OAM Operation and select Start LB. The
LB Test dialog box is displayed.
3. Enter the LB test source maintenance point ID and sink maintenance point ID.
4. Click Start LB and the check result is displayed.
TIP
Alternatively, you can select a node, right-click, and then choose Start LB from the shortcut menu
to start the LB test.
NOTE
Before you perform the check, set an appropriate LB Timeout(ms) as required.

3. Click OAM and choose Start LB from the drop-down menu. The LB Test dialog box is
displayed.
5. Click Start Test. The Operation Result dialog box is displayed, indicating that the
6. Click Close. View the test result.
----End
29.1.5.6 Performing a Link Trace Check

Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate
faults. That is, the faulty network segment can be located through only one test.

Prerequisite
Only MEPs can initiate the LT test and work as the termination point in the test.
In the case of a standard MP, you must activate CC before LT check.
Context
l During the LT check, the source MEP constructs and transmits LTM frames and starts the
timer. All the MPs that receive the LTM frames send the LTR frame response. According
to the LTR frame response, you can verify all the MIPs that pass from the source MEP to
the destination MEP.
l Performing an LT check does not affect the service.
Procedure
2. Select the node that you want to monitor, click OAM Operation and select Start LT. The
LT Test dialog box is displayed.
3. Enter the LT test source maintenance point ID and sink maintenance point ID.
4. Click Start LT and the check result is displayed.
TIP
Alternatively, you can select a node, right-click, and then choose Start LT from the shortcut menu
to start the LT test.
NOTE
Before you perform the check, set an appropriate LT Timeout(ms) as required.

3. Click OAM and choose Start LT from the drop-down menu. The LT Test dialog box is
displayed.
5. Click Start Test. The Operation Result dialog box is displayed, indicating that the

6. Click Close. View the test result.
----End
29.1.5.7 Activating the AIS(RTN 600)

After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the
AIS packet to superstratum MP for the notification of the fault.
Prerequisite
The source and sink MEPs and MIP must be created in the same maintenance domain (MD).
Procedure
Step 1 In the NE Explorer, select the Ethernet board, choose the Configuration > Ethernet
Maintenance > Ethernet Service OAM from the function tree.
Step 2 Select the node to be monitored. Double-click AIS Active State and then select Active or
Deactive, or right-click the AIS Active State and then choose Active or Deactive from the
shortcut menu.
Step 3 Click Apply.
----End
29.1.5.8 Performing a Ping Test(RTN 600)

By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the
processing board of an Ethernet service and the data communications equipment, such as a switch
and router, the packet loss ratio of a service, and the delay time.
Prerequisite
The OAM maintenance node of a service must be created for an Ethernet board. The type of the
maintenance node is MEP.
The MEP where the ping test is initiated must be created on an external physical port.
The tag attribute of the external physical port where the MEP resides must be Access.
Context
l The ping test can be initiated only from the Ethernet service processing board to the
interconnected data communication equipment.
l The ping test is performed in the direction from the board to which the MEP belongs to the
interconnected data communication equipment of the board.
l A legal IP address is allocated to the MEP, and the IP addresses of the MEP and the
interconnected data communication equipment must be in the same network segment.
By default, the IP address of an MP is 0.0.0.0.
The IP address of an MP cannot be any of the following:

Zero address: 0.*.*.*

Local loopback address: 127.*.*.*
Multicast address: 224.0.0.0 - 239.255.255.255
Reserved address: 240.0.0.0 - 255.255.255.255
Network address: *.*.*.0
Broadcast address: *.*.*.255
l Performing a ping test does not affect the service.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Step 2 Optional: Click Query to query OAM information from the NE.
Step 3 Select a node, click OAM Operation and select Start Ping. The Ping Test window is displayed.
TIP
To display the Ping Test window, you can also right-click a node and choose Start Ping from the shortcut
menu.
Step 4 Set Send Mode.

l Burst Mode, you need to set Frame Length, Timeout, and Ping Attempts.
l If you select Continue Mode, you need to set Frame Length, and Timeout.
Step 5 In the IP Address Configuration area, set Destination IP Address and Local IP Address.
NOTE
l The value entered in Local IP Address is the IP address of the local maintenance point.
l Set legal IP addresses for Local IP Address and Destination IP Address and make sure that the two
IP addresses in the same network segment.
Step 6 Click Start Ping and view the returned result in the Detail pane.
----End
29.1.5.9 Performing Performance Detection(RTN 600)

the performance detection realizes the on-line test of the packet loss ratio and delay time of the
services.
Prerequisite
Context
l The source maintenance point that initiates a performance test must be an MEP. The sink
maintenance point that responds to the performance test can be an MEP or MIP.
l Performing performance detection does not affect the service.

Procedure
Step 2 Optional: Click Query to query OAM information from the NE.
Step 3 Select a node, click OAM Operation and select Performance Detect. The Performance
Detect window is displayed.
TIP
To display the Performance Detect window, you can also right-click a node and choose Performance
Detect from the shortcut menu.
Step 4 Set Send Mode.

l Burst Mode, you need to set Frame Length, Timeout, and Detect Attempts.
l If you select Continue Mode, you need to set Frame Length, and Timeout.
Step 5 In the Maintenance Point area, set Source MP ID and Destination MP ID.
Step 6 Click Start Detect and view the returned result in the Detail pane.
----End
29.1.6 Using the IEEE 802.3ah OAM

By using the IEEE 802.1ag OAM, you can maintain the Ethernet link in a point-to-point manner.
29.1.6.1 Enabling the Auto-Discovery Function of OAM

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM auto-
discovery succeeds, the equipment automatically monitors the fault and performance of the link.
29.1.6.2 Enabling the Link Event Notification
After the link event notification is enabled on the local equipment, if the OAM detects a link
fault and link performance event, the opposite equipment is informed.
29.1.6.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold
The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link
performance. Usually, the default value is used. You can modify the value according to the
situation of the link.
29.1.6.4 Performing the Remote Loopback
After the Ethernet port on the local equipment sends data to the port on the interconnected
equipment, the local end can request the opposite end to return the data.
29.1.6.5 Enabling the Self-Loop Detection (RTN 600)
After enabling the self-loop detection on an Ethernet port, you can check the loopback of the
port and the loopback between the port and other Ethernet ports on the board.
29.1.6.1 Enabling the Auto-Discovery Function of OAM

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM auto-
discovery succeeds, the equipment automatically monitors the fault and performance of the link.
Prerequisite

Context
The OAM auto-discovery is realized through the auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After
the OAM auto-discovery succeeds, the link performance is performed according to the error
frame threshold. You can set the error frame threshold on the U2000.
l The OAM mode includes the active mode and the passive mode. For two interconnected
systems, the OAM mode of one system must be the active mode. Otherwise, the OAM
auto-discovery fails.
l if the OAM modes of the two systems are both active modes, a link fault occurs, or one
system fails to receive the OAM protocol message, an alarm is reported, indicating that the
OAM auto-discovery fails.
Procedure
Step 1 In the case of RTN 600 NEs, select an Ethernet board in the NE Explorer and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Click
.
Step 2 In the case of RTN 900 NEs, click the NE in the NE Explorer and choose Configuration >
Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree.
Click .
Step 3 Click the OAM Parameter tab, Set OAM Working Mode. In the Enable OAM Protocol drop-
down list, select Enabled.
Step 4 Click Apply.
Step 5 Click the Remote OAM Parameter tab. Click Query.
----End
29.1.6.2 Enabling the Link Event Notification

After the link event notification is enabled on the local equipment, if the OAM detects a link
fault and link performance event, the opposite equipment is informed.
Prerequisite
Make sure that the OAM auto-discovery succeeds.

Context
When the OAM auto-discovery succeeds at the two ends, the link fault detection and
performance detection are automatically started.
l To report the detected link fault event to the opposite equipment, Remote Alarm Support
for Link Event must be set to Enabled for the local equipment.
l To report the detected link fault event to the opposite equipment, the following operations
must be performed for the local equipment.
Set Remote Alarm Support for Link Event to Enabled.
Set Error Frame Period Window (Frame) and Error Frame Monitor Threshold.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite end detects link performance degradation, you can query the
ETHOAM_RMT_SD alarm , which is reported on the local end, by using the U2000. Based
on the alarm, you can determine the type of the link performance event.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite equipment detects a link fault event or encounters a fault that makes the
equipment fail to be restored (such as a power failure), you can query the
ET_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the U2000.
Based on the alarm, you can determine the fault type.
Procedure
Step 1 In the case of RTN 600 NEs, select an Ethernet board in the NE Explorer and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM. Click .
Step 2 In the case of RTN 900 NEs, click NE in the NE Explorer and choose Configuration > Ethernet
OAM Management > Ethernet Port OAM Management. Click .
Step 3 Click the OAM Parameter tab. Set Remote Alarm Support for Link Event to Enabled.
Step 4 Click Apply.
----End
29.1.6.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold
The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link
performance. Usually, the default value is used. You can modify the value according to the
situation of the link.
Prerequisite

The IEEE 802.3ah OAM function must be enabled on the remote equipment.
Context
After the OAM auto-discovery succeeds, set Error Frame Period Window (Frame) and Error
Frame Monitor Threshold, and set Remote Alarm Support for Link Event to Enabled for the
local equipment. If the local equipment detects a link event in the receive direction, it informs
the opposite equipment of the link event. If the remote alarm for the link event is also supported
on the opposite end, the opposite equipment can also inform the local equipment of the link
event that is detected on the side of the opposite end. Then, the ETHOAM_RMT_SD alarm is
reported on the local end, prompting the maintenance personnel to handle the link event.
Procedure
Maintenance > Ethernet Port OAM from the Function Tree. Click the OAM Error
Frame Monitor tab.
2. Select a port and set the error frame monitoring parameters.

3. Click Apply. A prompt appears indicating that the operation was successful.
4. Click Close.

1. In the NE Explorer, select the NE and choose Configuration > Ethernet OAM
Management > Ethernet Port OAM Management from the Function Tree. Click the
OAM Error Frame Monitor tab.
2. Select a port and set the OAM parameters of the port.
NOTE
l Error Frame Monitor Window: If the number of error frames on the link crosses the error frame monitor
threshold in the specified error frame monitor time window, the performance event is reported.
l Error Frame Period Window: If the number of error frames on the link crosses the error frame period
monitor threshold in the error frame period monitor window, the performance event is reported.
l Error Frame Second Window: If the number of error frame seconds on the link crosses the error frame
second monitor threshold in the specified error frame second monitor time window, the performance
event is reported.
l Error Frame Signal Periodic Monitor Window: In a specified number of signals, if the number of error
signals on the link crosses the defined threshold, the performance event is reported.
3. Click Apply. A dialog box is displayed, indicating that the operation was successful. Click
Close.
----End

29.1.6.4 Performing the Remote Loopback

After the Ethernet port on the local equipment sends data to the port on the interconnected
equipment, the local end can request the opposite end to return the data.
Prerequisite
Make sure that the OAM auto-discovery succeeds.
For the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
The equipment that responds to the loopback must have the capability of supporting the remote
loopback.
Context
l The IDU 620 do not support responding the remote loopback, and the IDU 605 support
responding the remote loopback.
l If a port is capable of responding to loopbacks, it enters the Respond Loopback of Remote
state and reports the loopback responding alarm when receiving the command of enabling
the remote loopback function sent from the opposite OAM port. In this case, the equipment
that initiates the loopback enters the initiate loopback at local state and reports the loopback
initiating alarm.
l After the remote loopback function is enabled, normally, service packets, except the
OAMPDU, are looped back at the remote end.
l After using the remote loopback function to complete the fault locating and the link
performance detection, you should disable the remote loopback function at the end where
the loopback is initiated and then restore the services. At this time, the alarm is automatically
cleared.
Procedure
Maintenance > Ethernet Port OAM. Click .
2. Click OAM Parametertab. Select the port that needs to initiate a loopback, and choose
Enable Remote Loopback from the drop-down list of OAM.
3. Click Apply.

1. In the NE Explorer, select the NE and choose Configuration > Ethernet OAM
Management > Ethernet Port OAM Management.
2. Click the Remote OAM Parameter tab.
3. Select a port and click Query. A dialog box is displayed, indicating that the operation is
----End

29.1.6.5 Enabling the Self-Loop Detection (RTN 600)

After enabling the self-loop detection on an Ethernet port, you can check the loopback of the
port and the loopback between the port and other Ethernet ports on the board.
Prerequisite
All the external physical ports of the Ethernet service processing board are enabled.
Context
When the self-loop detection is enabled for an external physical port, if the self-loop situation
occurs at the port, the ETHOAM_SELF_LOOP alarm is reported.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface
Management > Ethernet Interface. Click .
Step 2 Configure the external physical port.
1. Select External Port. Click the Advanced Attributes tab.
2. Set Loop Detection to Enabled.
3. Click Apply.
----End
29.2 Configuring the MPLS OAM

You can configure the MPLS OAM.
29.2.1 Overview of the MPLS OAM

Based on the MPLS OAM mechanism, you can effectively detect, confirm, and locate internal
defects from the network of the MPLS layer. The equipment uses the OAM detection state to
trigger the protection switching. As a result, fast fault detection and service protection can be
realized. Thus, a carrier-class quality of service (QoS) in a packet transport network can be
ensured.
The basic concepts of MPLS OAM include CV/FFD, Ping and Traceroute.
29.2.3 Application of the MPLS OAM
MPLS OAM provides end-to-end detection methods in the MPLS network.

29.2.4 Enabling the MPLS OAM of a Tunnel

You need to enable the OAM function of the corresponding tunnel before performing the MPLS
OAM operation.
29.2.5 Setting the MPLS OAM Parameters of a Tunnel
Based on different MPLS OAM parameters, the MPLS OAM operation results are different.
You need to set the MPLS OAM parameters before performing the MPLS OAM operation.
29.2.6 Starting the CV/FFD for a Tunnel
You can test the unidirectional connectivity of a tunnel by performing a connectivity verification
(CV)/fast failure detection (FFD).
29.2.7 Performing an LSP Ping Test
You can check whether a label switch path (LSP) is successfully created by performing an LSP
ping test.
29.2.8 Performing an LSP Traceroute Test
You can locate the place where a fault occurs by performing an LSP traceroute test.
29.2.1 Overview of the MPLS OAM

Based on the MPLS OAM mechanism, you can effectively detect, confirm, and locate internal
defects from the network of the MPLS layer. The equipment uses the OAM detection state to
trigger the protection switching. As a result, fast fault detection and service protection can be
realized. Thus, a carrier-class quality of service (QoS) in a packet transport network can be
ensured.

The MPLS is a key carrying technology of the extended next generation network (NGN). This
technology provides a QoS-ensured multi-service capability and introduces a unique network
layer, which may cause some faults. Therefore, an MPLS network must have the OAM
capability.
The MPLS supports many layer 3 and layer 2 protocols, such as the IP, ATM, and Ethernet
protocols. By providing an OAM mechanism independent of any upper layer or lower layer, the
MPLS OAM supports the following features:
l Provide the query based on requirements and the consecutive detection so that at any
moment you can learn whether the monitored LSP has defects.
l Detect, analyze, and locate any defect that occurs, and notify the U2000 of the relevant
information.
l Trigger a protection switching immediately after a defect or fault occurs on a link.

The MPLS OAM complies ITU-T Y.1711 and ITU-T Y.1731.
l ITU-T Y.1711 Operation & Maintenance mechanism for MPLS networks

l ITU-T Y.1731 OAM functions and mechanisms for Ethernet based networks

The basic concepts of MPLS OAM include CV/FFD, Ping and Traceroute.

CV/FFD
You can check the connectivity of a label switch path (LSP) by performing a connectivity
verification (CV) or fast failure detection (FFD). The process of a CV is consistent with that of
an FFD. The difference lies in that the CV transmits CV packets at the frequency of 1 frame per
second and the frequency cannot be set, but the FFD transmits FFD packets at a frequency that
can be self-defined. Figure 29-11 shows the process of a CV and an FFD.
Figure 29-11 Connectivity check of the MPLS OAM

Transit
LSR
CV/FFD
CV/FFD
Ingress
Egress
LSR
LSR
BDI
BDI
Transit
LSR
1. The ingress node transmits CV or FFD packets, and the transit node transparently transmits
packets. The packets reach the egress node through the detected LSP.
2. The egress node compares the received information fields, such as packet type, frequency,
and TTSI, with the fields recorded in the local to check the correctness of the packets. It
also performs statistics to the numbers of correct packets and incorrect packets during the
detection period, which is 3s for a CV and three times as long as the transmission period
for an FFD. In this way, the connectivity of an LSP is monitored in real time.
3. When detecting a defect of the LSP, the egress node analyzes the defect type, and then
transmits the backward defect indication (BDI) packets that carry the defect information
to the ingress node through a reverse channel so that the ingress node can learn the defect
status in time. If a protection group is correctly configured, the corresponding protection
switching is also triggered.
When configuring basic detection functions of the OAM, you can bind a reverse channel for the
detected LSP. The reverse channel is an LSP that has opposite ingress and egress nodes to the
detected LSP, or is a non-MPLS path that can connect to the ingress and egress nodes of the
detected LSP. The reverse channel that carries BDI packets can be one of the following types:
l Dedicated reverse LSP: Each forward LSP has a corresponding reverse LSP. This method
is relatively stable but may waste resources.
l Shared reverse LSP: Many forward LSPs share a reverse LSP. All LSPs return BDI packets
through this reverse LSP. This method saves resources, but a congestion may occur on the
reverse LSP when many forward LSPs have defects at the same time.
At present, only the dedicated reverse LSP is supported.

Ping/Traceroute
In MPLS, if the LSP fails to forward data, the MPLS control plane responsible for constructing
the tunnel cannot detect this fault. Thus, the network maintenance is difficult. The MPLS Ping/
Traceroute provides a mechanism for detecting the LSP faults and locating the invalid nodes in
a timely manner.
The MPLS Ping/Traceroute uses the MPLS Echo Request and MPLS Echo Reply to detect the
usability of the LSP. The MPLS Echo Request carries the information of the forwarding
equivalence class (FEC) for detection, which is transmitted along the LSP with other packets
belonging to this FEC. In this way, the LSP is checked.
l The MPLS Ping and Echo Request messages should reach the Egress node of the tunnel.
Then, the control plane of the Egress node determines whether this node is the Egress of
this FEC. Whether the LSP is successfully created can be checked by the MPLS Ping.
l The MPLS Traceroute and Echo Request messages should be transmitted to each Transit
node. The control plane of the Transit node determines whether the local node is an
intermediate node on this path. The location of the network fault can be determined through
the Traceroute function.
29.2.3 Application of the MPLS OAM

MPLS OAM provides end-to-end detection methods in the MPLS network.
MPLS OAM is mainly applied to the LSP of the core layer in the network. See Figure 29-12.
Figure 29-12 Application scenarios of MPLS OAM
CE
CE
Access layer Core layer Custom layer
OptiX RTN 950

LSP
OptiX RTN 910
Table 29-7 lists different application scenarios of the CV/FFD, Ping and Traceroute.
Table 29-7 Application scenarios of MPLS OAM detection methods

OAM Type Usage Application Scenario
CV/FFD Unidirectional connectivity Real-time detection of the

check tunnel state

Ping Unidirectional connectivity Fault location or detection at

check a single end
Traceroute Fault location Tunnel route detection
29.2.4 Enabling the MPLS OAM of a Tunnel

You need to enable the OAM function of the corresponding tunnel before performing the MPLS
OAM operation.
Prerequisite
l An MPLS tunnel must be created.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast
Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameters tab. In the OAM Status area, click Enabled.
successful.
Step 4 Click Close.
----End
29.2.5 Setting the MPLS OAM Parameters of a Tunnel

Based on different MPLS OAM parameters, the MPLS OAM operation results are different.
You need to set the MPLS OAM parameters before performing the MPLS OAM operation.
Prerequisite
l You must enable the Tunnel OAM function.
Procedure
Step 2 Select the tunnel, click the OAM Parameters tab and set the parameters.

NOTE
Note the following during parameter settings:

l Detection Packet Period: When the Detection Packet Type is set to CV, the Detection Packet
Period is 1 s and cannot be set. When the Detection Packet Type is set to FFD, the Detection Packet
Period can be set.
l Reverse Tunnel: Send the BDI packets that carry the defect information to the ingress node so that
the ingress node can learn the defect status in time.
l When the Tunnel Type is set to Egress, you can set the SD Threshold and SF Threshold. The SD
Threshold is smaller than or equal to the SF Threshold.
Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is
successful.
Step 4 Click Close.
----End
29.2.6 Starting the CV/FFD for a Tunnel

You can test the unidirectional connectivity of a tunnel by performing a connectivity verification
(CV)/fast failure detection (FFD).
Prerequisite
l You must enable the MPLS OAM function.
Procedure
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Start
CV/FFD from the drop-down menu. The Operation Result dialog box is displayed, indicating
that the operation is successful.
NOTE
When the Node Type of the tunnel is Ingress, the CV/FFD can be enabled.
Step 3 Click Close.
----End

29.2.7 Performing an LSP Ping Test

You can check whether a label switch path (LSP) is successfully created by performing an LSP
ping test.
Prerequisite
l In the case of a static MPLS tunnel, enable the IS-IS protocol at both the source and sink
ports of the MPLS tunnel, for details, see 20.2.2 Setting Port Attributes. Also, you can
start a ping test at the local end and configure a static route on the opposite NE.
Procedure
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Ping
Test from the drop-down menu. The Ping Test dialog box is displayed.
NOTE
When the Node Type of the tunnel is Ingress, you can perform the ping test.

Step 3 Set the parameters.
Step 4 Click Start Test. View the ping test result.
----End
29.2.8 Performing an LSP Traceroute Test

You can locate the place where a fault occurs by performing an LSP traceroute test.
Prerequisite
l In the case of a static MPLS tunnel, enable the IS-IS protocol at both the source and sink
ports of the MPLS tunnel. Also, you can start a ping test at the local end and configure a
static route on the opposite NE.
Procedure
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose
Traceroute Test from the drop-down menu. The Traceroute Test dialog box is displayed.

NOTE
To support the traceroute test, the Tunnel Type of the tunnel must be Ingress.
Step 3 Set the parameters.
Step 4 Click Start Test and view the traceroute test result.
----End
29.3 Configuring the PW OAM

This section describes how to configure the PW OAM.
29.3.1 Overview of the PW OAM

As an mechanism for maintaining and managing PWs, PW OAM detects the connectivity of
PWs by using ping packets.
The basic concept of the PW OAM is Ping.
29.3.3 Application of the PW OAM
The PW OAM provides end-to-end detection at the PW layer.
29.3.4 Performing the PW Ping Test
By performing the PW Ping test, you can check whether the PW runs normally.
29.3.1 Overview of the PW OAM

As an mechanism for maintaining and managing PWs, PW OAM detects the connectivity of
PWs by using ping packets.

The OptiX RTN equipment encapsulates service packets into PWs and then transmits the
services over a tunnel. On the RTN, there are two layers, that is, tunnel layer and PW layer. The
MPLS tunnels can be maintained and managed by MPLS OAM. The PWs can be maintained
and managed by PW OAM. Currently, the OptiX RTN equipment can detect the connectivity
of a PW by using the PW packets and can report the detection result to the U2000.
The local equipment encapsulates the ping packets into PWs and then transmits the packets over
a tunnel. When receiving the over-tunnel packets, the opposite equipment decapsulates the
packets, processes the packets, and responds to the packets. Then, the opposite equipment
transmits the response packets back to the local equipment. In this manner, the local equipment
determines the connectivity of the PW according to whether it can receive the response packets
from the opposite equipment.

The PW OAM complies with the RFC 4379 Detecting MPLS Data Plane Failures.

The basic concept of the PW OAM is Ping.

Ping
PW Ping is a tool for manually checking the connection status of virtual circuits, which is similar
to the LSP Ping. When the PW fails to forward data, the control plane that is responsible to create
the PW cannot detect this fault. This makes the network maintenance difficult. PW Ping provides
the mechanism of detecting faults of PWs to users.
During the PW forwarding, the Ping packets are encapsulated into the PW at the ingress and are
transmitted along the virtual circuit. Thus, the PW is checked.
29.3.3 Application of the PW OAM

The PW OAM provides end-to-end detection at the PW layer.
The main detection method of the PW OAM is PW Ping, as shown in Figure 29-13. Between
NE1 and NE2, a CES service that is carried by a PW exists. NE1 initiates the PW Ping test. You
can view the test result and check the running status of the PW.
Figure 29-13 Application scenario of the PW OAM
TDM E1 CES PW
TDM E1
NE1 PW ping NE2

NodeB RNC
29.3.4 Performing the PW Ping Test

By performing the PW Ping test, you can check whether the PW runs normally.
Prerequisite
l The PW that carries services must be created.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > PW
Step 2 Right-click a PW and choose PW Ping Test from the shortcut menu. The Ping Test dialog box
is displayed.

Step 3 Configure corresponding parameters.

NOTE
A PW can only initialize a Ping test at a time.

The value of Packet length ranges from 64 to 1400. If the value is not within the range, the Ping fails.
Step 4 Click Start Test. View the Ping test result.
----End
29.4 Configuring ATM OAM

How to use the U2000 to configure ATM OAM is described.
29.4.1 Overview of the ATM OAM

The ATM OAM is an end-to-end OAM function for services. It can detect the quality of an ATM
link that transits multiple NEs.
This section describes basic concepts about the ATM OAM.
29.4.3 Application of the ATM OAM
ATM OAM includes two detection methods: CC and LB.

29.4.4 Setting Segment End Attribute

You need to set the segment end attribute of the connection before performing ATM OAM
maintenance. The segment end attributes determines how the port handles the OAM cell.
29.4.5 Setting the CC Activation Status
You can perform continuity check (CC) on the ATM service to check the continuity of the service
for troubleshooting.
29.4.6 Setting Remote Loopback Test
You can perform remote loopback (LB) check on the ATM connection without interrupting the
service. In this way, you can check the connectivity of the connection for troubleshooting.
29.4.7 Setting Local Loopback ID
You must set the local loopback ID (LLID) for an NE before performing the loopback (LB) test
on it.
29.4.1 Overview of the ATM OAM

The ATM OAM is an end-to-end OAM function for services. It can detect the quality of an ATM
link that transits multiple NEs.
Objective and Benefits

As an OAM function based on the ATM layer, the ATM OAM supports the following functions:
l Verify the connectivity of ATM services.
l Detect faults.
l Locate faults.

The ATM OAM complies with the ITU-T I.610 recommendations-B-ISDN operation and
maintenance principles and functions.

This section describes basic concepts about the ATM OAM.
You can use the ATM OAM function to detect an ATM link by inserting OAM cells with
standard cell structure into the user cell flow. In an ATM network, the OAM function is classified
into five layers. See Table 29-8.
Table 29-8 Classification of the OAM function layers

Layer Description
F1: regenerator section layer Physical layer OAM: The physical layer
OAM flow depends on the transmission
F2: digital section layer mechanism of a specific transmission system.
F3: transmission channel layer An ATM network contains the following
three types of transmission mechanisms:
1. SDH-based transmission system
2. Cell-based transmission system
3. PDH-based transmission system

Layer Description
F4: virtual path (VP) layer ATM OAM: The ATM OAM is based on the
VP/VC and independent of the transmission
F5: virtual channel (VC) layer system.
At the ATM layer, the operation flows of F4 and F5 are defined. The F4 flow is an OAM cell
flow in the virtual path connect (VPC) and provides the operation management and maintenance
functions of the VP level. The F5 flow is an OAM cell flow in the virtual channel connect (VCC)
and provides the operation management and maintenance functions of the VC level. After the
OAM is activated at the F4 and F5, the specific OAM cell is inserted into user cells. As a result,
the functions of continuity check (CC) and loopback (LB) check without service interruption
are realized.
The ATM OAM defines the following concepts:
l Endpoint: Only the OAM cells at the end can be terminated.
l Segment point: Only the OAM cells at the segment can be terminated.
l Segment and Endpoint: The OAM cells at the segment and end can be terminated.
l Non segment and Endpoint: The OAM cells are not terminated.
29.4.3 Application of the ATM OAM

ATM OAM includes two detection methods: CC and LB.
As ATM OAM provides end-to-end detection methods for specific services. In the case of the
UNIs-NNI ATM service, you can check the service connectivity between the UNI and the NNI.
In the case of the UNI-UNI ATM service, you can check the service connectivity between the
two UNIs.
CC
After the CC detection function at the source end and sink end is enabled, the source end regularly
forms and sends CC cells. If the sink end fails to receive CC cells from the source end within
seconds, it automatically reports the LOC alarm and inserts the corresponding AIS cells to the
downstream.
LB
Perform the remote loopback (LB) detection. The source end forms and sends LB cells and
enable the timer for timing. If the sink end receives the LB cells, it sends the cells back to the
source end. If the source end detects the returned LB cells within the given time, the loopback
succeeds; otherwise, the loopback fails.
Table 29-9 lists different application scenarios of the CC and LB.

Table 29-9 Application scenarios of ATM OAM detection methods
CC Unidirectional connectivity Real-time detection of the

check link state
LB Bidirectional connectivity Fault location or detection at

check a single end
29.4.4 Setting Segment End Attribute

You need to set the segment end attribute of the connection before performing ATM OAM
maintenance. The segment end attributes determines how the port handles the OAM cell.
Prerequisite
The ATM service must be created and activated.
Context
The segment end attribute of ATM CPs (Connection Points) contains Segment point and Non
segment and Endpoint.
The ways that the port handles the OAM cell in different segment end attributes are described
as follows:
l If the segment end attribute is set to Endpoint, only the OAM cell at the end can be
terminated.
l If the segment end attribute is set to Segment point, only the OAM cell at the segment can
be terminated.
l If the segment end attribute is set to Segment and Endpoint, the OAM cells at the segment
and end can be terminated.
l If the segment end attribute is set to Non segment and Endpoint, the OAM cell is not
terminated.
CAUTION
You cannot set OAM segment endpoint or activate CC at the protection connection to which 1
+1 source or 1+1 sink protection group is applied. You cannot set segment end attribute at the
connection that is added to a protection group.
Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management.
Step 2 Set the Segment and End Attribute of the connection point.

----End
29.4.5 Setting the CC Activation Status

You can perform continuity check (CC) on the ATM service to check the continuity of the service
for troubleshooting.
Prerequisite
Context
After you activate the CC check at the source and sink ends of a service, the source ends
periodically builds and sends a CC cell. If the sink end does not receive the CC cell from the
source in 3-4 seconds, it automatically reports a CCLOS alarm and inserts an e-to-e_VP_AIS
alarm to the downstream. seconds, it automatically reports LOC alarm and inserts the
corresponding AIS cells to the downstream.
NOTE
When activating the CC, you need to activate the source and sink ends almost at the same time in a short
period. You are recommended to activate the sink first and then the source. Otherwise, the NE may report
timeout.
Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management. Click
the CC Activation Status tab.
Step 2 Set the CC Activate Flag of the port and the Segment and End Attribute of the CC cell.
NOTE
l Segment and End Attribute sets the segment end attribute of the CC cell. It corresponds to the segment
end attribute of the port. The CC cell terminates at the port of the same segment attribute.
l After the CC Activate Flag is activated, the CC check is started.

----End
29.4.6 Setting Remote Loopback Test

You can perform remote loopback (LB) check on the ATM connection without interrupting the
service. In this way, you can check the connectivity of the connection for troubleshooting.
Prerequisite
Segment end attribute must be set.
Context
During the remote loopback check, the source end builds a LB cell, sends the cell and starts the
timer. If the sink end receives the LB cell, it sends the cell back to the source. If the source end
detects the returned LB cell in a specified time, the loopback is successful. Otherwise, the
loopback fails.
Procedure
the Remote Loopback Test tab.
Step 2 Set the Loopback PointLoopback Point NE and Segment and End Attribute.
Step 3 Click Test to start the remote loopback test.

Step 4 Click Test Result to view the test result.
----End
29.4.7 Setting Local Loopback ID

You must set the local loopback ID (LLID) for an NE before performing the loopback (LB) test
on it.
Prerequisite

Context
The LB test recognizes an NE by LLID, so the LLID must be unique in the network. After the
LLID is set for an NE, the LLID value is sent to all the boards to keep consistency of LLID
values on all the boards.
Procedure
the LLID tab.
Step 2 Set the Country Code, Network Code, and NE Code.
----End

Operation Guide for RTN NE Management 30 Configuring Link State Pass Through
30 Configuring Link State Pass Through
About This Chapter
The link state pass through (LPT) is used to detect the faults that occur at the service access node
and in the intermediate transmission network. The LPT notifies the equipment at two ends in
the transmission network of starting the backup network at the earliest time for communication,
thus making sure the normal transmission of the important data.

LPT is a service-based protection scheme, supporting the Ethernet line service of the point-to-
point and point-to-multipoint.
30.2 Availability
The LPT feature requires the support of the applicable equipment and boards.
LPT is realized by transmitting different packets that varies according to different types of faults.
30.4 LPT Configuration
When enabling the LPT function for an Ethernet service, you need to configure the LPT port
and the related information.

30 Configuring Link State Pass Through Operation Guide for RTN NE Management

LPT is a service-based protection scheme, supporting the Ethernet line service of the point-to-
point and point-to-multipoint.
The link state pass through (LPT) is used to detect and report the faults that occur at the service
access node and in the intermediate transmission network. The LPT notifies the equipment at
two ends in the transmission network of starting the backup network at the earliest time for
communication, thus making sure the normal transmission of the important data.
LPT Application
As a link-based protection scheme, the LPT passes through states of the point-to-point link and
point-to-multipoint link. In this way, the LPT makes sure the network level protection for the
transmission of point-to-point private line services and for the transmission of the point-to-
multipoint convergence services.
l The following description is based on the point-to-point networking. Figure 30-1 shows
the point-to-point networking.
Figure 30-1 Point-to-Point LPT networking diagram
Backup network
Service
Network
Access NE1 NE2 Access

Router A Node Link 1 Node Link 2 Router B
Working Link
Protection Link
In normal situations, data of router A and router B is exchanged over the network service
equipment. In the diagram preceding, the network equipment refers to the Huawei OptiX
RTN equipment, namely NE1 and NE2. When faults occur at the link between router A
and router B, the communication between router A and router B is interrupted.
For the important user, however, even when such fault occurs, the important data must be
transmitted normally. Thus, the system must be able to detect and report faults at the earliest
time and then start the backup network to make sure the communication.

When the LPT function is enabled, the OptiX equipment detects and reports the faults at
the service access node and in the intermediate network. Then the data communication
equipment such as routers switches to the backup network at the earliest time for
communication, thus making sure the normal transmission of the important data.
l The following description is based on the point-to-multipoint networking. Figure 30-2
shows the point-to-multipoint networking.
Figure 30-2 Point-to-Multipoint LPT networking diagram
Backup
network
Port1 Port2 Router B
NE2
Port3 Service
network
Port1 Port2
Port2
Router A NE1
Port1
Port3 Router C
NE3
Backup
network
Protection link Router D
Working link
Normally, the data among router A, router B, router C and router D is transmitted through
a server network. When the link between router A and NE1 becomes faulty, router A fails
to communicate with router B, router C and router D. When the link fault occurs, the
important data of VIP users must still be normally transmitted. Hence, the system should
detect and notify the fault in time, and start the backup network to retain communication.
LPT Capability
When the LPT function is enabled, the notification interval is less than two seconds after the
fault occurs.
LPT Bearer Mode

To meet a condition that the LPT frame can pass through different Layer 2 networks, the LPT
is defined at Layer 2.5. In this case, the LPT can be carried by the medium access control (MAC)
frame and generic framing procedure (GFP) management frame.

The LPT bearer mode varies with the different LPT packets. When the bearer mode of the
received LPT packets is not consistent with that of the equipment at the receive end, the LPT
packet is discarded.
30.2 Availability
The LPT feature requires the support of the applicable equipment and boards.
Table 30-1 Availability of the LPT feature(RTN600)
Point-to-point LPT SL61EFT4VER.B RTN 610/620

feature
SL61EMS6VER.B, EFP6 RTN 620
Point-to-multipoint SL61EMS6VER.B, EFP6 RTN 620

LPT feature
Table 30-2 Availability of the LPT feature(RTN900)
EM6T
RTN 910/950
EM4F
CSHA
CSHB RTN 910
CSHC

LPT is realized by transmitting different packets that varies according to different types of faults.
30.3.1 Point-to-Point Service(RTN 600)

In the case of a point-to-point service, the LPT function is realized differently in the following
two scenarios: the access point is faulty and the transmission network is faulty.
30.3.2 Point-to-Multipoint Service(RTN 600)
In the case of a point-to-multipoint service, the LPT function is realized differently in the
following two scenarios: the access point is faulty and the transmission network is faulty.
30.3.1 Point-to-Point Service(RTN 600)

In the case of a point-to-point service, the LPT function is realized differently in the following
two scenarios: the access point is faulty and the transmission network is faulty.

Point-to-Point LPT Service Network Fault

l Fault locating
Broken Broken
Access Service Service Service Access
Node 1 Equipment Network Equipment Node 2
A B
Both service equipment A and B detect that the service network is unavailable and then transmit
the Broken packets to the opposite ends respectively. At the same time, equipment A and B cut
the connection to local users.
NOTE
l If the service network fault is bidirectional, service equipment A and B can detect the fault in the service
network. As a result, either of the two sets of the equipment can cut the connection between the local
end and the user, and transmit the Broken packets to the opposite end at the same time.
l If the service network fault is unidirectional, for example, if the link in the direction from service
equipment A to B is faulty, only service equipment A can detect the service network fault. In this case,
service equipment A cuts the connection between the local end and access node 1 and transmits the
Broken packets to equipment B in the direction from equipment A to B over the service network where
no fault occurs. After receiving the Broken packets, service equipment B cuts the connection between
the local end and access node 2. In this way, the fault in the service network is detected.
l According to different transmission modes, the Broken packets can be transmitted through specific
GFP management frames or MAC frames.
l Link restoration
Non_ Non_
Broken Broken Service
Access Service Service Access
A B
Both service equipment A and B detects that the service network is recovered, and then notify
the opposite end that the link is recovered by transmitting the Non_Broken packets respectively.
At the same time, equipment A and B recover the connection with local users.
Access Service Service Service Access

A B
Service equipment A and B recovers the local link when any of the following condition is
satisfied. 1. Equipment A and B receive the Non_Broken packets transmitted by the opposite
ends respectively. 2. Timeout occurs for waiting the Broken frame.
Point-to-Point LPT Access Node Link Fault

l Fault locating

Disconnect the link

Report the link Service and report the
fault alarm Network LPT_RFI alarm
Service Broken Service
Access Access
Equipment Equipment
Node 1 Node 2
A B
1. Service equipment A detects that the link at the access node is faulty, and then reports the
alarm of the fault that occurs at the local end. At the same time, equipment A transmits the
Broken control frame to equipment B.
2. After receiving the Broken control frame, service equipment B disconnects the local end
and reports the LPT_RFI alarm at the same time.
l Link restoration
Service
Clear the link Network Recover the
fault alarm link
Service Non_Broken Service
Access Access
Equipment Equipment
Node 1 Node 2
A B
1. Service equipment A detects that the link at the access node is recovered, and then transmits
the Non_Broken control frame to service equipment B.
2. After receiving the Non_Broken control frame, service equipment B recovers the
connection at the local end.
30.3.2 Point-to-Multipoint Service(RTN 600)

In the case of a point-to-multipoint service, the LPT function is realized differently in the
following two scenarios: the access point is faulty and the transmission network is faulty.
Context
The point-to-multipoint LPT function processes faults in unidirectional service network and
bidirectional service network by using the same means.
Point-to-Multipoint LPT Service Network Fault

l Fault locating
Disconnect the link
and report the
LPT_RFI alarm
Disconnect the link
and report the Service
Broken Access
LPT_RFI alarm Equipment
Node 1
B
Service
Convergence Disconnect the link
Equipment
Node and report the
A
LPT_RFI alarm
Service
Broken Access
Equipment
Node 2
C

The bidirectional fault occurs in the service network between service equipment A and B. In
this case, equipment A and B cut the local connections respectively and report the LPT_RFI
alarms. At the same time, equipment A transmits the Broken packets to equipment C. In this
case, service equipment C cuts the local connection and reports the LPT_RFI alarm.
l Link restoration
Recover the link
and clear the
Recover the link LPT_RFI alarm
Service
and clear the Non_Broken Access
Equipment
LPT_RFI alarm Node 1
B
Service
Convergence Recover the link
Equipment
Node and clear the
A
LPT_RFI alarm
Service
Access
Non_Broken Equipment
Node 2
C
The bidirectional fault is cleared in the service network between service equipment A and B. In
this case, equipment A and B recovers the local connections respectively and report the clearance
of the LPT_RFI alarms. At the same time, equipment A transmits the Non-Broken packets to
equipment C. In this case, service equipment C recovers the connection to the local end and then
reports the clearance of the LPT_RFI alarm.
Point-to-Multipoint LPT Access Node Link Fault at the Convergence Node Side
l Fault locating
Disconnect the
link and report the
LPT_RFI alarm
Service
Access
Report the link Broken Equipment
Node 1
fault alarm B
Service Disconnect the
Convergence Equipment link and report
Node A the LPT_RFI
Service alarm
Broken Access
Equipment
Node 2
C
Service Equipment A that connects to the convergence node detects that the link at the access
node is faulty, and then reports the alarm of the fault that occurs at the local end. At the same
time, service equipment A transmits Broken packets to service equipment B and C. After
receiving the packets, equipment B and C disconnect the local end. In this case, equipment B
and C report the LPT_RFI alarms.
l Link restoration

Recover
Service the link
Non_Broken Access
Equipment
Node 1
Clear the link B
fault alarm Service
Convergence
Equipment
Node
A
Recover
Service the link Access
Node 2
C
Service Equipment A that connects to the convergence node detects the link restoration at the
access nod, and then reports the clearance of the local fault alarm. At the same time, service
equipment A transmits Non-Broken packets to service equipment B and C. After receiving the
packets, equipment B and C recover the connections to the local end. In this case, equipment B
and C report the clearance of LPT_RFI alarms.
Point-to-Multipoint LPT Access Node Link Fault at the Access Node Side
l Scenario 1
Fault locating
Report the link
Disconnect the
fault alarm
link and report Service
Access
the LPT_RFI Broken Equipment
Node 1
alarm B
Service
Convergence
Equipment
Node Report the link
A
fault alarm
Service
Access
Broken Equipment
Node 2
C
1. Service equipment B that connects to access node 1 detects that the link at the access
node is faulty, and then reports the alarm of the local access node fault. At the same
time, equipment B transmits the Broken packets to service equipment A.
2. After receiving the packets, equipment A reports the LPT_RFI alarm and transmits
the Broken packets to equipment C at the same time.
3. In this case, service equipment C disconnects the local end and reports the LPT_RFI
alarm.
Link restoration
Clear the link
Service fault alarm Access
Node 1
Recover B
the link Service
Convergence
Equipment
Node
A
Recover
Service the link
Non_Broken Access
Equipment
Node 2
C

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

Recover the link

Service
and clear the Access
Equipment
B
Service
Convergence
Equipment
Node Recover
A Access
the link
Service Node 2
C
Access
Node 3
Service Equipment C that connects to the access node 2 detects the link at the access node
is restored, and then reports the clearance of the fault alarm at the local end. At the same
time, service equipment C transmits Non-Broken packets to service equipment A. After
receiving the packets, equipment A recovers the local connection and reports the clearance
of the LPT_RFI alarm.
Recover the link
and clear the
LPT_RFI alarm
Service
Non_Broken Access
Equipment
Node 1
B
Service
Convergence
Equipment
Node
A Access
Service Node 2
Non_Broken_Ack Equipment
C
Access
Recover the link
Node 3
and clear the
LPT_RFI alarm
After receiving the Non_Broken packets where the response confirmation frame is
contained, service equipment A transmits the Non_Broken packets to service equipment
B. After receiving the Non_Broken_Ack packets, service equipment C recovers the
connection to access node 3 and reports the clearance of the LPT_RFI alarm. After
recovering the Non_Broken packets from equipment A, service equipment B disconnects
the local end and reports the clearance of the LPT_RFI alarm.
30.4 LPT Configuration

When enabling the LPT function for an Ethernet service, you need to configure the LPT port
and the related information.
Prerequisite
The Ethernet data board supports the LPT function.
The port-based Ethernet private line service must be created and activated.
The data service is configured as the pure transparent service.

Precautions
NOTE
l Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On one board, you can select
only one configuration mode to realize the LPT function.
l The data service of the point-to-point LPT is configured as the pure transparent service.
CAUTION
Before configuring the point-to-multipoint LPT function, make sure that the following two
conditions are met. Otherwise, the services may be interrupted.
l The data services are displayed in the tree topology.
l The data service topology is consistent with that of the LPT.
Procedure
Step 1 In the case of RTN 600 NEs.
Interface Management > LPT Management from the Function Tree.
2. Optional: Configuring Point-to-Point LPT.
a. Click Query. The Operation Result dialog box is displayed. Click Close.
b. Select a PORT and a VCTRUNK port, and then set the following parameters. For
parameters of the point-to-point LPT, see Table 30-3.
NOTE
If LPT is enabled, you can set Port-Type Port Hold-Off Time(ms) and VCTRUNK Port
Hold-Off Time(ms) as required.
c. Click Apply and a prompt appears telling you the operation was successful.
d. Click Close.
e. Repeat Steps 1 through 2 to configure point-to-point LPT for the opposite NE.
3. Optional: Configuring Point-to-Multipoint LPT.
a. Click PtoMP LPT.
b. In the LPT Management window, click New.
c. In the Create LPT window, select Port from the Convergence Point pane, and set
Hold-Off Time(ms).

NOTE
If the port at the convergence point is a VCTRUNK port, you need to set Bearer Mode.
d. In the Access Point pane, select an appropriate Port and click . Double-
click Bearer Mode and select an appropriate bearer mode from the drop-down
list.For parameters of the point-to-multipoint LPT, see Table 30-4.
NOTE
l If the port at the convergence point is not a VCTRUNK port, do not set Bearer Mode.
l If you want to modify Bearer Mode, you can modify it in the Modify LPT window.
e. Click OK. Click Close in the Operation Result dialog box.
f. Repeat Steps 1 and Steps 3 to configure point-to-multipoint LPT for other NEs.
Step 2 In the case of RTN 900 NEs.
1. In the NE Explorer, click the NE and choose Configuration > LPT Management from
the Function Tree.
2. Click New. The dialog box is displayed.
3. In the dialog box, set related parameters.
NOTE
l One port should belong to only one LPT group.

l Multiple ports can be selected as access ports.
l You can select multiple IF boards to configure a LPT group.
4. Click Apply.
----End

Parameter
Table 30-3 Parameter of the Point-to-Point LPT(RTN600)

Field Value Default Description
Port For - The external port of board.

example:
PORT1
VCTRUNK For - The VCTRUNK port where

Port example: EPL services are transparently
VCTRU transmitted.
NK1
Direction Positive, - The direction of the EPL

Reverse services that are transparently
transmitted.
The direction is Positive if the
source port is a PORT port and
the sink port is a VCTRUNK
port. The direction is Reverse
if the source port is a
VCTRUNK port and the sink
port is a PORT port.
LPT Yes, No No Sets whether to use LPT.
Bearer Mode GFP GFP(HUAWEI) This parameter is valid only

(HUAW when the LPT occurs.
EI), The bearer mode of LPT
Ethernet frames.
Port-Type 0 to 100 This parameter is valid only

Port Hold-Off 10000 when the LPT occurs.
Time (ms) When the LPT switching is
enabled, the port informs the
opposite end after the hold-off
time.
VCTRUNK 0 to 100 This parameter is valid only

Port Hold-Off 10000 when the LPT occurs.
Time (ms) When the LPT switching is
enabled, the port informs the
opposite end after the hold-off
time.

Table 30-4 Parameter of the Point-to-Multipoint LPT(RTN600)

Convergence Port PORT1 to PORT1 The port where

Point PORT6, the convergence
VCTRUNK1 to point resides.
VCTRUNK8
Bearer Mode GFP GFP The bearer

(HUAWEI), (HUAWEI) mode of the port
Ethernet where the access
point resides.
This parameter
can be edited
only when it is
supported by a
board.
Hold-Off Time 0 to 10000 0 If LPT

(ms) switching is
enabled, the port
notifies the
opposite end
after the hold-
off time.
Access Point Port PORT1 to - The port where

PORT6, the access point
VCTRUNK1 to resides.
VCTRUNK8
Bearer Mode GFP GFP The bearer

(HUAWEI), (HUAWEI) mode of the port
Ethernet where the access
point resides.
This parameter
can be edited
only when it is
supported by a
board.
Table 30-5 Parameter of the LPT(RTN900)

Board For example: 7- - Sets the convergence

EM4F-EM4F board and access
board to configure
the LPT.

Port For example: 1 - Sets the convergence

(PORT-1) port and access port
to configure the LPT.

Operation Guide for RTN NE Management 31 Configuring Remote Monitoring Feature
31 Configuring Remote Monitoring Feature
About This Chapter
The remote monitoring (RMON) feature is used to monitor the data traffic on a network segment
or on an entire network. Currently, the RMON standard is one of the most widely applied network
management standards.

The RMON feature is based on the management information base (MIB) in the architecture of
the simple network management protocol (SNMP). Through the RMON function, you can
monitor the performance of the Ethernet port as you monitor the performance of the SDH/PDH
port.
31.2 Basic Concepts
RMON feature.
31.3 Availability
The RMON feature requires the support of the applicable equipment and boards.
The RMON agent is embedded in an Ethernet board. The Web LCT server or U2000 server
functions as the NMS. The NMS exchanges data information with the agent through basic SNMP
commands. Thus, the statistical network data is collected.
The RMON function need not be configured and can be directly used.

31 Configuring Remote Monitoring Feature Operation Guide for RTN NE Management

The RMON feature is based on the management information base (MIB) in the architecture of
the simple network management protocol (SNMP). Through the RMON function, you can
monitor the performance of the Ethernet port as you monitor the performance of the SDH/PDH
port.
In the case of the Ethernet port of the transmission product, the port performance needs to be
measured and the port data needs to be managed. Therefore, the RMON should provide the
following functions:
l Storage of statistical data at the agent end; offline operations on the network management
station (NMS)
l History data storage
This facilitates fault diagnosis.
l Error detection and reporting
l Multiple management stations
To implement the preceding functions, the RMON defines a series of statistical formats and
functions to realize the data exchange between the control stations and detection stations that
comply with the RMON standards, and thus to implement management on the Ethernet port.
The RMON provides flexible detection modes and control mechanisms to meet the requirements
of different networks. Furthermore, the RMON provides the function of error diagnosis of the
entire network, and the functions of planning and receiving of the performance events.
The RMON complies with RFC 1757 and RFC 2819.
31.2 Basic Concepts

RMON feature.
31.2.1 SNMP
Currently, the SNMP is the most widely used network management protocol in the network.
The SNMP is used to ensure transport of the management information between any two nodes
in the network. This facilitates the network administrator to retrieve information, modify
information, locate a fault, diagnose a fault, plan capacity, and generate a report on any node in
the network.
31.2.2 RMON Management Groups
The Ethernet board provides the following RMON management groups specified in IETF
RFC2819: statistics group, history group, alarm group, and history control group.
31.2.3 List of RMON Alarm Entries and RMON Performance Entries
The RMON alarm entries and RMON performance entries supported by the Ethernet service
processing board comply with RFC2819.
31.2.1 SNMP
Currently, the SNMP is the most widely used network management protocol in the network.
The SNMP is used to ensure transport of the management information between any two nodes

in the network. This facilitates the network administrator to retrieve information, modify
information, locate a fault, diagnose a fault, plan capacity, and generate a report on any node in
the network.
Architecture of the SNMP

The SNMP is divided into the network management station (NMS) and the agent.
l NMS
The NMS is a workstation where the client program runs. When the RMON function is
used, the Web LCT or U2000 server functions as the NMS.
l Agent
The agent is the server software that runs on the network equipment. When the RMON
function is used, the agent is embedded in the Ethernet board.
The NMS can send the GetRequest, GetNextRequest, or SetRequest packet to the agent. After
receiving such a request packet, the agent reads or writes the packet according to the type of the
packet, generates the Response packet, and sends the Response packet to the NMS.
When an exception occurs in the equipment or the state of the equipment changes (for example,
the equipment restarts), the agent sends the Trap packet to the NMS and reports the event to the
NMS.
The transmission of SNMP packets is based on the connectionless transport layer UDP. Hence,
the OptiX RTN 600 can be connected to a wide variety of equipment without a block.
MIB
In SNMP packets, managed variables are used to describe the managed objects in the equipment.
The SNMP uses the architecture naming solution to uniquely identify each managed object in
the equipment. The overall architecture is like a tree. The nodes on the tree indicate the managed
objects. Each node can be uniquely identified by a path starting from the root. The MIB is used
to describe the architecture of the tree and is the collection of the definitions of the standard
variables of the monitored network equipment. The RMON is a common MIB defined according
to IETF RFC2819.
31.2.2 RMON Management Groups

The Ethernet board provides the following RMON management groups specified in IETF
RFC2819: statistics group, history group, alarm group, and history control group.
Statistics Group
The statistics group counts the absolute performance values from the time the statistics group is
created until the current time.
The Ethernet board supports port-based statistics groups. In the case of a board, you can create
a statistics group for only one port. The sampling interval of a statistics group can be set. The
value range of the sampling interval is from 1 second to 100 seconds.

Alarm Group
The alarm group monitors the specified alarm objects (for example, the performance data of
ports). When the value of the monitored data crosses the configured threshold, an alarm event
is generated.
The Ethernet board supports port-based alarm groups. You can create only one alarm group for
a board. The number of alarm entries in an alarm group must not exceed ten. You can set the
following items to which the alarm object corresponds: monitored object, sampling interval,
report mode (report in case of upper threshold-crossing, report in case of lower threshold-
crossing, report all), upper threshold, and lower threshold.
History Control Group

The history control group specifies the methods of monitoring history performance data. The
Ethernet board periodically collects the required statistical network information and temporarily
stores the information in the board according to the attributes of the history control group. The
history control group has the following attributes:
l History table type

You can set the history table type to 30-second, 30-minute, custom period 1, or custom
period 2. In the case of a custom period, you need to manually set the required sampling
interval.
l Monitored object
This specifies the port on which performance data is collected. You can set monitored
objects for each history table type.
l Number of items
This specifies the number of history performance data entries that are stored in the Ethernet
board. Because the history performance data is stored in the wrap mode, the stored data is
the latest history performance data. For example, if the number of items is set to 10, the
Ethernet board stores the latest ten history performance data entries. You can set the number
of items for each history table type. The number of items can be set to 50 at most.
History Group
The history group specifies the methods of querying history performance data. The Ethernet
board filters the history performance data stored in the board according to the attributes of the
history group and returns the history performance data that meets the filtering conditions. The
history group has the following attributes:
l History table type

This specifies the sampling period to which the history performance data corresponds. You
can set the history table type to 30-second, 30-minute, custom period 1, or custom period
2.
l Monitored object
This specifies the port to which the history performance data corresponds.
l Performance entry
This specifies the performance entries to which the history performance data corresponds.
The list of performance entries is the same as the list of performance entries that can be
added into a statistics group.

l Query conditions
This specifies the relative time to which the history performance data corresponds. 1
represents the oldest item. You can query a maximum of ten entries at a time.
31.2.3 List of RMON Alarm Entries and RMON Performance

Entries
The RMON alarm entries and RMON performance entries supported by the Ethernet service
processing board comply with RFC2819.
Table 31-1 List of RMON alarm entries
Alarm Name Description
DropEvent The total number of events in which packets are dropped crosses
a threshold.
UndersizePkts The number of undersized packets crosses a threshold.
OversizePkts The number of oversized packets crosses a threshold.
Fragments The number of fragments crosses a threshold.
Jabbers The number of jabbers crosses a threshold.
FCSErrors The number of the packets with FCS errors crosses a threshold.
Table 31-2 List of RMON performance entries
Category of Name of a Performance Entry

Performance
Entries
Basic performance Packets received (64 octets in length) (packets/second)
Packets received (65-127 octets in length) (packets/second)
Drop events (times/second)
Multicast packets received (packets/second)
Broadcast packets received (packets/second)
Undersized packets received (packets/second)
Oversized packets received (packets/second)


Performance
Entries
Fragments (packets/second)
Jabbers (packets/second)
Octets received (bytes/second)
Packets received (packets/second)
Extended Packets transmitted (64 octets in length) (packets/second)

performance
Packets transmitted (65-127 octets in length) (packets/second)
Unicast packets received (packets/second)
Unicast packets transmitted (packets/second)
Multicast packets transmitted (packets/second)
Broadcast packets transmitted (packets/second)
Pause frames received (frames/second)
Pause frames transmitted (frames/second)
FCS errors (frames/second)
Packets received and transmitted (64 octets in length) (packets/

second)
Packets received and transmitted (65-127 octets in length) (packets/

second)

second)

second)
Packets received and transmitted (512-1023 octets in length)

(packets/second)
Packets received and transmitted (1024-1518 octets in length)

(packets/second)
Good full frame speed received (bytes/second)
Good full frame speed transmitted (bytes/second)


Performance
Entries
Good full frame octets received (bytes/second)
Good full frame octets transmitted (bytes/second)
Control frames received (frames/second)
Packets transmitted (packets/second)
Octets transmitted (bytes/second)
VCG performance Octets received (bytes/second)
Octets transmitted (bytes/second)
Packets received (packets/second)
Packets transmitted (packets/second)
Good packets received (packets/second)
Good packets transmitted (packets/second)
Full frame speed received (bytes/second)
Full frame speed transmitted (bytes/second)
NOTE
The PORTs of the EMS6 board, EFT4 board, and IFH2 board support basic performance entries and extended
performance entries. The VCTRUNKs of the EMS6 board support VCG performance entries. The VCTRUNKs
of the EFT4 board do not support RMON performance entries. The IDU 605 1F/2F PORT and IFUP support
basic performance and extended performance.
31.3 Availability
The RMON feature requires the support of the applicable equipment and boards.
Table 31-3 Availability of the RMON Feature
EFT4 RTN 610/620
EMS6 RTN 620
EFP6
IFH2 RTN 620
- RTN 605

Table 31-4 Availability of the RMON Feature
EM6T
EM6F
EM4T
RTN 910/950
EM4F
IFU2
IFX2
CSHA
CSHB RTN 910
CSHC
NOTE
l The EFT4 board supports the RMON of PORTs only.

l The EMS6 board supports the RMON of PORTs and VCTRUNK.
l The IFH2 board supports the RMON of PORTs only.
l The RTN 605 board supports the RMON of PORTs and IFUP.

The RMON agent is embedded in an Ethernet board. The Web LCT server or U2000 server
functions as the NMS. The NMS exchanges data information with the agent through basic SNMP
commands. Thus, the statistical network data is collected.
Statistics Group
The processing flow is as follows:
1. A maintenance engineer clicks Resetting begins.

2. The NMS sends the corresponding request packet to the RMON agent.
3. The RMON agent embedded in the Ethernet board resets the corresponding current
performance counting register and returns the corresponding response packet to the NMS
according to the information of the statistics group in the request packet.
4. The NMS sends a request packet to the RMON agent at sampling intervals. The RMON
agent returns the value of the current performance counting register through the response
packet.
5. The maintenance engineer clicks Stop.
6. The NMS stops sending the corresponding request packet to the RMON agent.

NOTE
l If the maintenance engineer clicks Start, the RMON agent does not reset the performance counting register.
l If the maintenance engineer does not select Display Accumulated Value, the NMS obtains the performance
value of a sampling interval by performing a subtraction operation between the sampled value returned at
the end of the sampling interval and the sampled value returned at the end of the previous sampling interval.
Alarm Group
1. The maintenance engineer clicks Apply.

3. The RMON agent embedded in the Ethernet board monitors the corresponding alarm object
according to the information of the alarm group in the request packet.
4. When the alarm object crosses the configured threshold in the corresponding direction, the
RMON agent sends the corresponding trap packet to the NMS.
5. The NMS generates the corresponding RMON alarm according to the information in the
packet.
History Control Group

1. The maintenance engineer clicks Apply.

3. The RMON agent embedded in the Ethernet board periodically counts the performance
value of the monitored object and stores the performance value in the corresponding history
performance register according to the information of the history control group in the request
packet.
History Group
1. The maintenance engineer clicks Query.

3. The RMON agent embedded in the Ethernet board queries the history performance registers
that meet the requirements and returns the performance values in the registers to the NMS
through the response packet according to the information of the history group in the request
packet.

The RMON function need not be configured and can be directly used.
31.5.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
After you configure an RMON statistics group for an Ethernet port, you can browse the real-
time statistical performance data of the port.
31.5.2 Configuring an Alarm Group for an Ethernet Port

After you configure an RMON alarm group for an Ethernet port, you can monitor whether the
performance value of the port crosses the configured thresholds in the long term.
31.5.3 Configuring a History Control Group
When configuring a history control group for an Ethernet port, you configure how the history
performance data of the port is monitored. The Ethernet board monitors the history performance
data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50
history performance data items.
31.5.4 Browsing the Performance Data in the History Group of an Ethernet Port
After you configure an RMON history group for an Ethernet port, you can browse the statistical
history performance data of the port.
31.5.5 Setting Performance Monitoring Status for an Ethernet Port
By setting status and period of the RMON performance monitoring, the performance data can
be periodically collected.
31.5.1 Browsing the Performance Data in the Statistics Group of an

Ethernet Port
After you configure an RMON statistics group for an Ethernet port, you can browse the real-
time statistical performance data of the port.
Prerequisite
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performance
Step 2 Click the Statistics Group tab.
Step 3 Set the required parameters for the statistics group.
Step 4 Click Resetting begins.
NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
31.5.2 Configuring an Alarm Group for an Ethernet Port

After you configure an RMON alarm group for an Ethernet port, you can monitor whether the
performance value of the port crosses the configured thresholds in the long term.
Prerequisite
Applies to OptiX RTN 600 NEs.

Procedure
Step 2 Click the Alarm Group tab.
Step 3 Set the required parameters for the alarm group.
Step 4 Click Apply.
----End
31.5.3 Configuring a History Control Group

When configuring a history control group for an Ethernet port, you configure how the history
performance data of the port is monitored. The Ethernet board monitors the history performance
data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50
history performance data items.
Prerequisite
Procedure
1. Select the Ethernet board in the NE Explorer. Choose Performance > RMON
Performance from the Function Tree.
2. Click the History Control Group tab.
3. Set the required parameters for the history control group.
4. Click Apply.
1. Click the NE in the NE Explorer. Choose Performance > RMON History Control
Group from the Function Tree.
2. Set the required parameters for the history control group.
3. Click Query.
----End
31.5.4 Browsing the Performance Data in the History Group of an

Ethernet Port
After you configure an RMON history group for an Ethernet port, you can browse the statistical
history performance data of the port.
Prerequisite

The monitored objects and the corresponding history table type must be set in the History
Control Group tab.
Procedure
Step 2 Click the History Group tab.
Step 3 Set the required parameters for the history group.
Step 4 Click Query.
----End
31.5.5 Setting Performance Monitoring Status for an Ethernet Port

By setting status and period of the RMON performance monitoring, the performance data can
be periodically collected.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > RMON
Performance from the Function Tree.
Step 2 Click the RMON Setting tab.
Step 3 Select ports in the upper pane, click Query.
Step 4 Select the object from Object, set the monitor status, and enable or disable each collecting period.
NOTE
Enable or disable the collecting period in the Object interface only after you enable the collecting period
in the RMON history control group interface.
Step 5 Select the performance event in Event and set the enable status for each monitor period.
Step 6 Click Apply. Click Close in the dialog box displayed.
----End

Operation Guide for RTN NE Management 32 Configuring Synchronous Ethernet
32 Configuring Synchronous Ethernet
About This Chapter
The synchronous Ethernet technology realizes the transfer of the clock signal through the
Ethernet interface so that the clock frequencies of the equipment are synchronous.

The synchronous Ethernet is a clock frequency synchronization technology of the Ethernet
physical layer. The synchronous Ethernet can directly extract the clock signal from the serial bit
stream on the Ethernet line and transmit data by using the clock signal to realize the transfer of
the clock signal.
32.2 Availability
The synchronous Ethernet feature requires the support of the applicable equipment and boards.
The realization of the synchronous Ethernet feature complies with ITU-T G.8261.
By default, the NEs consider that all the Ethernet links provide the clock signal. Hence, you need
only to configure the clock source for the NEs that require the synchronous Ethernet clock.

32 Configuring Synchronous Ethernet Operation Guide for RTN NE Management

The synchronous Ethernet is a clock frequency synchronization technology of the Ethernet
physical layer. The synchronous Ethernet can directly extract the clock signal from the serial bit
stream on the Ethernet line and transmit data by using the clock signal to realize the transfer of
the clock signal.
Application of the Synchronous Ethernet

The OptiX RTN 600 radio transmission system provides the mobile communication network
with backhaul links. Currently, the synchronous Ethernet links are used to transfer the clock
signal in the wireless access network so that the reliable transfer of the clock signal is ensured.
As shown in Figure 32-1, the synchronous Ethernet provided by the microwave transmission
equipment realizes the transfer of the timing information between the RNC equipment and node
B.
Figure 32-1 Application of the synchronous Ethernet in the wireless access network
NE2 NE1
FE
Node B FE/GE
RNC
FE
Ethernet clock signal

Node B
Ethernet link
Performance of the Synchronous Ethernet

The synchronous Ethernet complies with ITU-T G.8261. The clock signal recovered by the
synchronous Ethernet meets the requirement of 50 ppb frequency accuracy.
32.2 Availability
The synchronous Ethernet feature requires the support of the applicable equipment and boards.
Table 32-1 Availability of the synchronous Ethernet feature
IFH2 RTN 620
- RTN 605

Operation Guide for RTN NE Management 32 Configuring Synchronous Ethernet
EM6T
RTN 910/950
EM6F
CSHA
CSHB RTN 910
CSHC

The realization of the synchronous Ethernet feature complies with ITU-T G.8261.
As shown in Figure 32-2, the microwave equipment performs the following operations to realize
the synchronous Ethernet function:
1. The data sub-system extracts the clock information (namely, recovery clock) from the
packets that the upstream Ethernet port receives.
2. The data sub-system sends the Ethernet recovery clock to the clock processing module.
Then, the clock processing module locks the Ethernet recovery clock to the local system
clock and provides the system synchronous clock.
3. The system synchronous clock provides a reference clock for the other modules of the
system and the services (for example, microwave services or node B that is interconnected
with the downstream Ethernet port) so that the system is synchronized with the Ethernet.

32 Configuring Synchronous Ethernet Operation Guide for RTN NE Management
Figure 32-2 Realization principle of the synchronous Ethernet

Microwave Orderwire
services
NMS
...
Orderwire and
CPU sub-system IF sub-system auxiliary Other
interface modules
module
System
synchronous clock
Local system clock

Clock processing module
Ethernet
recovered
clock
Ethernet services
Data sub-system

By default, the NEs consider that all the Ethernet links provide the clock signal. Hence, you need
only to configure the clock source for the NEs that require the synchronous Ethernet clock.
l In the case of the IDU 620, see 14.7.8 Configuring the Clock Sources to configure the
Ethernet clock source.
l In the case of the IDU 605 1F/2F, see 14.7.9 Configuring the Ethernet Clock Source to
configure the Ethernet clock source.

Operation Guide for RTN NE Management 33 Modifying the Configuration Data
33 Modifying the Configuration Data
About This Chapter
When you need to adjust the existing configuration data related to topologies and services, you
can modify the configuration data.
33.1 Modifying NE Attributes

You can modify the existing NE configuration data that needs adjustment.
33.2 Modifying the Board Configuration Data
You can modify the existing board configuration data that needs adjustment.
33.3 Modifying the Fiber Configuration Data
You can modify the existing fiber configuration data that needs adjustment.
33.4 Modifying the Service Configuration Data
You can modify the existing service configuration data that needs adjustment.

33 Modifying the Configuration Data Operation Guide for RTN NE Management
33.1 Modifying NE Attributes

You can modify the existing NE configuration data that needs adjustment.

33.1.2 Modifying the NE Name
You can modify the NE name as required. This operation does not affect the running of the NE.
33.1.3 Deleting NEs
If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes
all information of the NE from the U2000 but does not affect the running of the equipment.
33.1.4 Modifying GNE Parameters
33.1.5 Changing the GNE for NEs

Prerequisite
Precautions
CAUTION
Modifying the NE ID may interrupt NE communication and reset the NE.

Procedure
Tree.
----End
33.1.2 Modifying the NE Name

You can modify the NE name as required. This operation does not affect the running of the NE.
Prerequisite
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 In the NE Attribute dialog box, enter a new NE name in Name. Click Apply. A prompt is
displayed indicating that the operation is successful.
NOTE
An NE name consists of up to 64 characters, including letters, symbols, and numerals, except the following
special characters | : * ? " < >.
Step 3 Click Close.
----End
33.1.3 Deleting NEs

If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes
all information of the NE from the U2000 but does not affect the running of the equipment.
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
Context
When the NE is not logged in, you can delete the NE on the U2000.
CAUTION
If an NE is deleted, the links related to the NE are also deleted.
When a GNE is deleted, if no standby GNE is provided for the NEs that were originally managed
by the deleted GNE, the communication between those NEs and the U2000 is interrupted.

Procedure
l Delete a single or RTN NE.
1. Right-click the NE on the Main Topology and choose Delete > Delete Device from
the shortcut menu. The Confirm dialog box is displayed.
2. Click Yes. The NE icon is deleted from the Main Topology.
l Delete NEs in batches.
1. Choose Configuration > NE Configuration Data Management from the main
menu. The Configuration Data Management window is displayed.
2. In the left-hand pane, select multiple NEs and click . The Configuration Data
Management List pane displays the configuration data of all the selected NEs.
3. Select the NEs to be deleted, right-click and choose Delete from the shortcut menu.
The Delete the NE dialog box is displayed.
4. Click OK.
----End
33.1.4 Modifying GNE Parameters

Prerequisite
Precautions
CAUTION
This is a potential service affecting operation. Specifically, it may interrupt the communication
between a GNE and the U2000, and the communication between the GNE and the non-gateway
NEs that are managed by the GNE.
Procedure
Step 2 Select the GNE to be modified, right-click and choose Modify GNE from the shortcut menu.
Step 3 In the Modify GNE dialog box displayed, set Gateway Type .
l When Gateway Type is set to IP Gateway, modify IP Address.

l When Gateway Type is set to OSI Gateway, modify NSAP Address.
NOTE
l It is not recommended to modify the Port No..

l Make sure that the IP address of the GNE is in the same network segment as the IP address of the
U2000. When the U2000 server and the GNE are in different network segments, you need to set the
network port attributes of the router through which the U2000 server and the GNE are connected. In
this way, the U2000 can log in to the GNE.
Step 4 Click OK. In the Operation Result dialog box that is displayed, click Close.
----End
33.1.5 Changing the GNE for NEs

Prerequisite

Precautions
CAUTION
This operation may interrupt the NE communication.
Procedure
Step 3 Select an NE. Double-click the Primary GNE1 field and select a GNE from the drop-down list.
Step 5 Click Refresh. Test the modification with reference to Checking the Network Communication
Status.
----End
33.2 Modifying the Board Configuration Data

33.2.1 Adding Boards

When manually configuring the NE data, you need to add boards on the NE Panel. You can
either add the physical boards that actually operate on the NE or add the logical boards that do
not exist on the actual equipment.
33.2.2 Deleting Boards
To modify the network configuration or the NE configuration, you may need to delete the boards
from the NE Panel.
33.2.3 Modifying Board Configuration Parameters
33.2.1 Adding Boards

When manually configuring the NE data, you need to add boards on the NE Panel. You can
either add the physical boards that actually operate on the NE or add the logical boards that do
not exist on the actual equipment.

Prerequisite
l There must be idle slot on the NE Panel.
Context
The physical boards are the actual boards inserted in the shelf. A logical board refers to a board
that is created on the U2000. After a logical board is created, you can configure the relevant
services. If the corresponding physical board is online, the configured services can be available.
NOTE
The NE panel is able to indicate the mapping relation between slots that house processing boards and
interface boards. When you click a processing board that is paired with an interface board in the NE panel,
the ID of the slot that houses the mapping interface board is displayed in orange.
Procedure
Step 1 Open the NE Panel.
For the RTN equipment, double-click the icon of the NE.
NOTE
Currently, the OptiX OSN 6800 and OptiX OSN 8800 T32 equipments can be managed individually as an
NE, and can also be managed in an optical NE. For the two equipments, you can double-click the NE On
the Main Topology, the NE Panel is displayed.
Step 2 Right-click the selected idle slot. Select the board you want to add from the drop-down list.
----End
33.2.2 Deleting Boards

To modify the network configuration or the NE configuration, you may need to delete the boards
from the NE Panel.
Prerequisite
l The services and protection groups must be deleted.
Procedure
Step 1 Open the NE Panel.
For the RTN equipment, double-click the icon of the NE.
Step 2 Right-click the board you want to delete and choose Delete from the shortcut menu.
NOTE
Certain boards, such as AUX boards, cannot be deleted. The boards that can be deleted vary with different
types of equipment. For details, see the Hardware Description of each type of the equipment.
Step 3 Click OK in the Delete Board dialog box.

Step 4 Click OK to delete the board.
----End
33.2.3 Modifying Board Configuration Parameters

Prerequisite
To modify different configuration parameters of different boards, you may need to operate as
NM users with different authorities. You must be an NM user with "NE operator" authority or
higher. must be available at least.
Procedure
Step 1 In the NE Explorer, select a board and choose a proper item from the Function Tree.
Board Type Parameters Application Scenario
SDH board Multiplex section shared See Configuring SDH

attribute, laser enabling/ Boards.
disabling, optical interface
loopback, hardware REG
enabling
PDH board Tributary loopback, service See Configuring PDH

load indication Boards.
Ethernet board Port enabling, working See Configuring Ethernet

mode, maximum frame Boards.
length, MAC loopback, PHY
loopback, TAG, entry test
Step 2 In the right-hand pane, modify the existing parameter settings and click Apply.
----End
33.3 Modifying the Fiber Configuration Data

You can modify the existing fiber configuration data that needs adjustment.
33.3.1 Modifying Fiber/Cable Information

You can modify the name, attenuation, length, and type of a fiber/cable according to its
connection status and physical features.
33.3.2 Deleting Fibers
When adjusting the network if you need to delete the NEs or change the links between NEs, you
need to delete the fiber connections between the NEs.
33.3.3 Deleting DCN Communication Cables
In certain scenarios such as network adjustment, you can delete an unwanted DCN
communication cable that is created previously.

33.3.1 Modifying Fiber/Cable Information

You can modify the name, attenuation, length, and type of a fiber/cable according to its
connection status and physical features.
Prerequisite
Procedure
Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the main menu. The
information of all fiber/cable is displayed in the pane on the right.
Step 2 Modifying the fiber/cable information.
l In the Name column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu. In the Modify Fiber/Cable dialog box displayed, enter a
proper name for the fiber/cable and click OK. Click Close in the Operation Result dialog
box.
l In the Length(km) column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu. In the Modify Fiber/Cable dialog box displayed, enter the
actual length for the fiber/cable and click OK. Click Close in the Operation Result dialog
box.
l Modify the attenuation of a fiber.
1. In the Attenuation column, right-click the value for a fiber and choose Modify Fiber/
Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box, enter the actual loss and click OK. Click
Close in the Operation Result dialog box.
l Modify the type of the fiber.
1. In the Type column, right-click the value for a fiber and choose Modify Fiber/
Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box displayed, select the actual type of the fiber
from the drop-down list and click OK. Click Close in the Operation Result dialog
box.
----End
33.3.2 Deleting Fibers

When adjusting the network if you need to delete the NEs or change the links between NEs, you
need to delete the fiber connections between the NEs.
Prerequisite
Procedure
Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the main menu.
Step 2 Select the fiber you want to delete, right-click and choose Delete Fiber/Cable from the shortcut
menu. The Warning dialog box is displayed. Click OK to delete the fiber/cable.

CAUTION
The deletion of the fiber/cable will delete the related protection subnets, trails and user-defined
information. Exercise caution before you delete the fiber/cable. You can export the script of the
entire network first to avoid deletion by mistake.
----End
33.3.3 Deleting DCN Communication Cables

In certain scenarios such as network adjustment, you can delete an unwanted DCN
communication cable that is created previously.
Prerequisite
Procedure
Step 1 On the Main Topology, select a cable, right-click and choose Delete from the shortcut menu.
Step 2 In the Delete Link dialog box displayed, click OK.
----End
33.4 Modifying the Service Configuration Data

You can modify the existing service configuration data that needs adjustment.
33.4.1 Modifying SDH Services

To modify an SDH service, you can use the modification function of the U2000, or delete the
service and then create the cross-connection again.
33.4.2 Deleting SDH Services
You can delete an existing SDH service.
33.4.3 Deleting EPL Services
You can delete an existing EPL service.
33.4.4 Deleting EVPL Services
You can delete an existing EVPL service.
33.4.5 Deleting EPLAN Services

You can delete an existing EPLAN service.

33.4.6 Converting a Normal Service to an SNCP Service
The SNCP service features the dual fed function and is used to protect cross-subnet services.
When configuring RTN services on a per-NE basis, you can perform this operation to convert
a configured normal service to an SNCP service.
33.4.7 Converting an SNCP Service to a Normal Service
a configured SNCP service to a normal service.
33.4.1 Modifying SDH Services

To modify an SDH service, you can use the modification function of the U2000, or delete the
service and then create the cross-connection again.
Prerequisite
Context
CAUTION
Performing this operation interrupts the service that you modify.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > SDH Service Configuration
Step 2 Select a cross-connection and choose Display > Expand to Unidirectional.
Step 3 Optional: If the service to be modified is active, you should deactivate the service. Select the
service that you want to modify, and click Deactivate.
CAUTION
Deactivation will interrupt services.
Step 4 Click OK in the Confirm dialog box is displayed twice. The Operation Result dialog box is
displayed telling you that the operation was successful.
Step 5 Click Close.
Step 6 After the cross-connection is deactivated, modify the SDH service in the mode in Step 7 or Step
8.

NOTE
l By using the mode in Step 7, you can modify the source or sink of a service, but the source and sink
must be on the same board before and after the modification.
l If the modification requirement cannot be met in the mode in Step 7 (for example, a pass-through
service needs to be configured to the local through modification), you can delete the original service
and create the cross-connection again in the mode in Step 8, to achieve the modification.
Step 7 Optional: To modify the SDH service, choose Modify from the shortcut menu.
1. Select the service that you want to modify, right-click, and choose Modify from the shortcut
menu. The Modify SDH Service dialog box is displayed.
2. Modify Source VC4 or Sink VC4, Source Timeslot Range, and Sink Timeslot Range.
NOTE
In this mode, you can modify only Source VC4 or Sink VC4. The source VC4 and sink VC4 cannot
be modified at the same time.
3. Click OK. The Operation Result dialog box is displayed telling you that the operation
was successful.
4. Click Close.
5. Select the service that is modified, and click Activate.
6. Click OK. The Operation Result dialog box is displayed.
7. Click Close.
Step 8 Optional: To modify the SDH service, delete the service and then create the service again.
1. Select the service that you want to modify, and click Delete.
2. Click OK and the Operation Result dialog box is displayed telling you that the operation
was successful.
3. Click Close. The service is deleted.
4. Create the service again as required. For details, see Creating SDH Services.
----End
33.4.2 Deleting SDH Services

You can delete an existing SDH service.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > SDH Service Configuration
Step 2 Click Query to query existing services.
Step 3 Optional: If the service to be deleted is active, you should deactivate the service. Select the
service that you want to delete and click Deactivate.

CAUTION
Deactivation will interrupt services.
Step 4 Select the desired service and click Delete.
Step 5 In the Confirm dialog box displayed, click OK.
Step 6 In the Operation Result dialog box displayed, click Close.
----End
33.4.3 Deleting EPL Services

You can delete an existing EPL service.
Prerequisite
l The EPL service must be created.
Context
CAUTION
Deleting EPL services interrupts services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service > Ethernet
Line Service from the Function Tree.
Step 2 Select the desired EPL service and click Delete.
Step 3 In the Warning dialog box displayed, click Yes.
----End
33.4.4 Deleting EVPL Services

You can delete an existing EVPL service.
Prerequisite
l The EVPL service must be created.

Context
CAUTION
Deleting EVPL services interrupts services.
Procedure
Line Service from the Function Tree.
Step 2 Select the desired EVPL service and click Delete.
Step 3 In the Warning dialog box displayed, click Yes.
----End
33.4.5 Deleting EPLAN Services

You can delete an existing EPLAN service.
Prerequisite
The EPLAN service must be created
Context
CAUTION
Deleting EPLAN services interrupts services.
Procedure
LAN Service from the Function Tree.
Step 2 Select the desired EPLAN service and click Delete.
Step 3 In the Hint dialog box displayed, click Yes.
----End

33.4.6 Converting a Normal Service to an SNCP Service

a configured normal service to an SNCP service.
Prerequisite
The normal service must be created.
Procedure
the Function Tree.
Step 3 Click Display and choose Expand from the drop-down list, to display every service.
Step 4 Right-click a non-SNCP service and choose Convert to SNCP from the shortcut menu.
Step 5 Configure the protection service and click OK.
----End

33.4.7 Converting an SNCP Service to a Normal Service

a configured SNCP service to a normal service.
Prerequisite
The SNCP service must be created.
Procedure
the Function Tree.
Step 3 Right-click an SNCP service and choose SNCP Working Service Change to Normal
Service from the shortcut menu. The protection service is then deleted.
NOTE
To convert the service in the protection path into a normal service, right-click the SNCP service and choose
SNCP Protection Service Change to Normal Service from the shortcut menu. The working service is
then deleted.
----End

Operation Guide for RTN NE Management 34 Common Maintenance Operations
34 Common Maintenance Operations
About This Chapter
To ensure that the transmission equipment can be normally running for long, you need to
periodically maintain the transmission equipment or perform some simple operations of
troubleshooting on existing problems.

34.2 Turning On and Off a Laser
You can turn off or turn on a laser when necessary. For example, if an optical port does not carry
services, you can turn off the laser to prevent hazardous laser radiation exposure from causing
permanent eye damage. You can turn on the laser when the optical port needs to carry services.
34.3 Setting a Scheduled Task
The U2000 can automatically executing certain tasks in a scheduled time without manual
intervention. You can set and modify these scheduled tasks as required.
34.4 Checking Networkwide Maintenance Status
By checking the networkwide maintenance status, network maintenance personnel can learn the
running status of a network in a timely manner, to avoid impact on services due to
misconfiguration.
34.5 Checking Protection Switching Status
During the equipment maintenance or in other cases that require you to check the protection
switching status, you can check the protection switching status, to help to locate the fault and
learn the current network running status.
34.6 Resetting Boards
You can reset a board by using the U2000 by following the instructions below.
34.7 Performing a Loopback
The loopback is a common and effective way to locate equipment faults. By using the U2000
you can set a loopback for equipment.
34.8 Setting Automatic Laser Shutdown

34 Common Maintenance Operations Operation Guide for RTN NE Management
You can enable the automatic laser shut down function. In the event of a fiber cut, the laser at
an optical port is automatically off, to prevent hazardous laser radiation exposure from causing
permanent eye damage.
34.9 Disabling Service-Affecting Settings Automatically
Loopback and laser shutdown are useful NE maintenance functions. Performing these functions
may interrupt services at the port and may also interrupt the communication between the NE
and the U2000. Hence, you can set automatic disabling before performing loopback or laser
shutdown so that the NE automatically cancels the loopback or laser shutdown.
34.10 Performing a PRBS Test
You can perform a PRBS test on a path to check the quality of the path. The test result is displayed
in the coordinates pane.
34.11 Diagnosing Ethernet Protocol Faults
In the case of an Ethernet service fault, you can diagnose the Ethernet protocol and then restart
the protocol state machine by restoring the protocol, to remove the protocol faults.


Prerequisite
Context
shortcut menu.
Procedure
gateway NE.
----End
34.2 Turning On and Off a Laser

You can turn off or turn on a laser when necessary. For example, if an optical port does not carry
services, you can turn off the laser to prevent hazardous laser radiation exposure from causing
permanent eye damage. You can turn on the laser when the optical port needs to carry services.
Prerequisite
l The related board must be created.

Context
CAUTION
If you turn off a laser, services may be interrupted or you may fail to log in to certain NEs.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > SDH Interface from the
Function Tree.
Step 2 Click By Board/Port (channel) and select Port from the drop-down list.
Step 3 Double-click Laser Switch and set the laser status of each port to Open or Close as required.
NOTE
If you set Laser Switch to Close, you need to click OK in the Confirm dialog box. In the Prompt dialog
box, click OK.
----End
34.3 Setting a Scheduled Task

The U2000 can automatically executing certain tasks in a scheduled time without manual
intervention. You can set and modify these scheduled tasks as required.
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
If a large number of performance data need to be collected, this may cause communication
congestion and thus the communication between the U2000 and NEs stops. Hence, observe the
following rules to collect the performance data:
l When creating a single performance data collection task, the number of NEs related to the
same GNE does not exceed 5.
l Run the performance data collection task when network traffic is low.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management from the main menu.
Step 2 Optional: Create a scheduled task.
1. Click New and the New Task is displayed.
2. Enter a task name and select the task type of the scheduled task and the run type. Then,
click Next.
3. Set the Time Setting or the Period Setting. Click Next.

4. Follow the task creation wizard to set the parameters of the scheduled task and click
Next for several times until the Finish button is displayed.
5. Click Finish. A scheduled task is successfully created.
Step 3 Optional: Double-click a scheduled task to modify the parameters of the task.
Step 4 Optional: Right-click a scheduled task and choose Timely Suspend/Resume to set the suspend
time or the resume time for the task.
Step 5 Optional: Right-click a scheduled task and choose Run At Once to start executing the task.
NOTE
Run At Once means to immediately execute the task, no matter the scheduled time comes or not.
Resume means to start the scheduled task. The task is executed at the scheduled time.
----End
34.4 Checking Networkwide Maintenance Status

By checking the networkwide maintenance status, network maintenance personnel can learn the
running status of a network in a timely manner, to avoid impact on services due to
misconfiguration.
To check the networkwide maintenance status, check the following:
l Which ports are looped back.
l Which lasers are off.
l Which paths are in Non-loaded state.
l Which alarms are suppressed.
l Which alarms are inserted.
l Which alarms are reversed.
l Which ports have disabled DCCs.
34.4.1 Checking Path Loopback Status
You can view all optical or electrical ports for which you configure loopback in the network and
view the loopback status. You can also cancel the loopback, to avoid impact on services due to
a loopback that should not be performed.
34.4.2 Checking Port Laser Status
You can view all lasers that are in the off state in the network and modify their status, to avoid
impact on services due to misconfiguration.
34.4.3 Checking Path Loading Status
You can view all paths that are set to the non-loaded state in the network and modify the loading
status, to avoid impact on services due to misconfiguration.
34.4.4 Checking Path Alarm Reversion Status
You can view all paths for which you configure alarm reversion in the network and modify the
alarm reversion status, to avoid impact on services due to misconfiguration.
34.4.5 Checking Path Alarm Suppression Status

You can view all alarms for which you configure alarm suppression in the network. You can
also restore the suppression status of an alarm to the default value, so that the alarm monitoring
of the service is not affected by improper settings.
34.4.6 Checking the DCC Enabling Status
You can view all ports where DCC is in the shutdown state in the network, and you can modify
the DCC enabling status for the ports.
34.4.1 Checking Path Loopback Status

You can view all optical or electrical ports for which you configure loopback in the network and
view the loopback status. You can also cancel the loopback, to avoid impact on services due to
a loopback that should not be performed.
Prerequisite
Procedure
Step 1 Click the networkwide maintenance status icon on the toolbar, and the Networkwide
Maintenance Status dialog box is displayed.
Step 2 Choose Loopback Status, select the NEs from the Object Tree and click , view the
loopback status for a path from U2000.
Step 3 Click Query, view the loopback status from the NE.
NOTE
If the queried information is null, it indicates that no path is set to loopback.
Step 4 Optional: Select a loopback status and then click Apply. A prompt is displayed indicating that
the operation is successful. Click Close.
CAUTION
Setting a loopback may interrupt services. Exercise caution when you perform this operation.
NOTE
You must be an NM user with "NE operator" authority or higher to set loopback for a path.
----End
34.4.2 Checking Port Laser Status

You can view all lasers that are in the off state in the network and modify their status, to avoid
impact on services due to misconfiguration.
Prerequisite

You must be an NM user with "NE operator" authority or higher to set the laser status for an
optical port.
Procedure
Step 2 Choose Laser Status, select the NEs from the Object Tree and click , view the laser
status for an optical port from U2000.
Step 3 Click Query, view the laser status from the NE.
NOTE
If the queried information is null, it indicates that the laser of the equipment is not shut down.
Step 4 Optional: Set the laser status and then click Apply. If you want to enable the laser, in the OK
dialog box displayed, click OK. A prompt is displayed indicating that the operation is successful.
Click Close.
WARNING
Enabling a laser is a dangerous operation. Misoperation may cause injuries to human eyes.
Exercise caution when you perform this operation.
CAUTION
Close the Laser will interrupt the service.
----End
34.4.3 Checking Path Loading Status

You can view all paths that are set to the non-loaded state in the network and modify the loading
status, to avoid impact on services due to misconfiguration.
Prerequisite
Procedure
Step 2 Choose Maintenance Status > Path Loading and view the loading status for a path.

NOTE
If the queried information is null, it indicates that no path is set to Non-Loaded.
Step 3 Optional: Set the loading status and then click Apply. A prompt is displayed indicating that the
CAUTION
Set the path to be Non-Loaded will interrupt the service.
NOTE
You must be an NM user with "NE operator" authority or higher to set the loading status for a path.
----End
34.4.4 Checking Path Alarm Reversion Status

You can view all paths for which you configure alarm reversion in the network and modify the
alarm reversion status, to avoid impact on services due to misconfiguration.
Prerequisite
Applies to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.

Procedure
Step 2 Choose Alarm Reversion, select one or more NEs from the Object Tree and click ,
view the alarm reversion status for a path.
NOTE
If the queried information is null, it indicates that the alarm reversion is not set for any port.
Step 3 Optional: Set the alarm reversion status and then click Apply. A prompt is displayed indicating
that the operation is successful. Click Close.
NOTE
l If the alarm reversion is set for a port, the alarm status of this port is opposite to the actual status. That
is, when an alarm exists, the status is displayed as normal. This setting helps filter out negligible alarms.
When alarm suppression is set for a LOS alarm of the port, you cannot set alarm reversion at the same
time.
l You must be an NM user with "NE operator" authority or higher to set the alarm reversion status for
a path.
----End
34.4.5 Checking Path Alarm Suppression Status

You can view all alarms for which you configure alarm suppression in the network. You can
also restore the suppression status of an alarm to the default value, so that the alarm monitoring
of the service is not affected by improper settings.
Prerequisite
Applies to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.
Procedure
Step 2 Choose Alarm Suppression, select one or more NEs from the Object Tree and click ,
view the alarm suppression status for a path.
NOTE
If the queried information is null, it indicates that the alarm suppression is not set for any path.
Step 3 Optional: To restore the suppression status to the default value, right-click and choose
Default from the shortcut menu. Click Apply. A prompt is displayed indicating that the operation
is successful. Click Close.

NOTE
You must be an NM user with "NE operator" authority or higher to set the alarm suppression status for a
path.
----End
34.4.6 Checking the DCC Enabling Status

You can view all ports where DCC is in the shutdown state in the network, and you can modify
the DCC enabling status for the ports.
Prerequisite
Procedure
Step 2 Choose Maintenance Status > DCC Enabling Status and view the DCC enabling status for
the ports where DCC is in the shutdown state.
Step 3 Optional: Select a port for which you want to modify its DCC enabling status, right-click and
choose Enabled from the shortcut menu to modify its status to Enabled. Click Apply. A prompt
is displayed indicating that the operation is successful. Click Close.
NOTE
You must be an NM user with "NE operator" authority or higher to modify the DCC enabling status for a
port.
----End
34.5 Checking Protection Switching Status

During the equipment maintenance or in other cases that require you to check the protection
switching status, you can check the protection switching status, to help to locate the fault and
learn the current network running status.
34.5.1 Checking the SNCP Service Switching Status

By checking the SNCP service switching status, a network maintenance engineer can detect
faults in the NE or in the fibers of the SNCP protection subnet, in a timely manner. The engineer
can also locate the faulty point by checking the switching status of each NE in the protection
subnet.
34.5.2 Checking Linear MSP Switching Status
To detect faults in NEs or in the fibers of a linear MSP protection subnet, the maintenance
engineers can check the switching status of the linear MSP. The engineers can then locate the
point where the fault is generated, according to the switching status of each NE in the protection
subnet.
34.5.3 Checking 1+1 Board Switching Status

If board 1+1 protection switching is triggered, it indicates that the protected board has failed.
The network maintenance engineers can check 1+1 board switching status to detect the faults
that caused the failure.
34.5.4 Checking the Switching Status of 1+1 Intermediate Frequency Protection
If 1+1 intermediate frequency switching takes place, it indicates that the protection intermediate
frequency board becomes faulty. By checking the switching status of 1+1 intermediate frequency
protection, you can know the fault timely and thus prevent it from affecting services.
34.5.5 Check the Switching Status of the N+1 Protection
After configuring the N+1 protection, you can query the switching status of the protection on
the U2000.
34.5.6 Checking GNE Switching Status
34.5.7 Checking the Clock Switching Status
34.5.1 Checking the SNCP Service Switching Status

By checking the SNCP service switching status, a network maintenance engineer can detect
faults in the NE or in the fibers of the SNCP protection subnet, in a timely manner. The engineer
can also locate the faulty point by checking the switching status of each NE in the protection
subnet.
Prerequisite
l The SNCP service must be configured.
Context
Lockout switching means regardless of the status of the working and protection channels, the
services are locked in the working channel.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > SNCP Service Control from the
Function Tree.
All SNCP groups are displayed.
Step 2 Select an SNCP group, click Function and choose Query Switching Status from the drop-down
list.
----End
34.5.2 Checking Linear MSP Switching Status

To detect faults in NEs or in the fibers of a linear MSP protection subnet, the maintenance
engineers can check the switching status of the linear MSP. The engineers can then locate the

point where the fault is generated, according to the switching status of each NE in the protection
subnet.
Prerequisite
l The MSP protection group must be created.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Linear MS from the Function
Tree.
Step 2 In the pane on the right, select an MSP protection group. The Status of each node in the protection
group is displayed in the pane on the right.
Step 3 Click Query and select Query Switching Status to query the switching status of the nodes.
----End
34.5.3 Checking 1+1 Board Switching Status

If board 1+1 protection switching is triggered, it indicates that the protected board has failed.
The network maintenance engineers can check 1+1 board switching status to detect the faults
that caused the failure.
Prerequisite
The protection board must be created.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the
Function Tree.
Step 2 Click Query to query the 1+1 board switching status.
Step 3 Click Close.
----End
34.5.4 Checking the Switching Status of 1+1 Intermediate

Frequency Protection
If 1+1 intermediate frequency switching takes place, it indicates that the protection intermediate
frequency board becomes faulty. By checking the switching status of 1+1 intermediate frequency
protection, you can know the fault timely and thus prevent it from affecting services.
Prerequisite
l The 1+1 Intermediate Frequency Protection must be created.

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > IF 1+1 Protection from the
Function Tree.
Step 2 Select a protection group, and click Query.
Step 3 View the Switching Status of NE and Switching Status of Channel.
----End
34.5.5 Check the Switching Status of the N+1 Protection

After configuring the N+1 protection, you can query the switching status of the protection on
the U2000.
Prerequisite
l The N+1 protection group must be created.
Procedure
Step 1 Select the NE to be queried. In the NE Explorer, choose Configuration > N+1 Protection from
the Function Tree.
Step 2 Select the IF N+1 protection group and click Query. In Slot Mapping Relation, view Switching
Status.
NOTE
l The conditions that trigger the switching are as follows:

l SF: R_LOS, R_LOC, R_LOF, MS_AIS and B2_EXC alarms, removal of the board, and cold reset
of the board.
l SD: B2_SD alarm.
l The switching statuses are as follows: lockout, forced switching, SD switching, SF switching, manual
switching, wait to restore, exercise switching, non-revertive request and normal.
----End
34.5.6 Checking GNE Switching Status

Prerequisite
The active and standby GNEs must be created for an NE.

Procedure
Step 3 Click Refresh to query the GNE switching status.
----End
34.5.7 Checking the Clock Switching Status

Prerequisite
l The reference clock source must be set.
Procedure
Switching from the Function Tree.
Step 2 Click the Clock Source Switching tab, and click Query to query the current switching status
of the current clock source.
----End
34.6 Resetting Boards

You can reset a board by using the U2000 by following the instructions below.
34.6.1 Reset
Reset is a protection scheme for applications and data files on the equipment. When a board is
not running properly, you can reset the board so that it returns to the normal state. Reset is of
two types: warm reset and cold reset. A cold reset takes more time than a warm reset. After a
board is reset, the data on the board is not lost, but the resetting process may interrupt services.
34.6.2 Resetting the SCC Board
You can reset the SCC board by using the U2000. Resetting the SCC is a maintenance method
used in the case of an improper SCC working status.
34.6.3 Resetting a Non-SCC Board

You can reset a non-SCC board by using the U2000. Resetting a board is a maintenance method
used in the case of an improper board working status.
34.6.4 Resetting a Board
You can reset a board by using the U2000. Resetting a board is a maintenance method used in
the case of an improper board working status.
34.6.1 Reset
Reset is a protection scheme for applications and data files on the equipment. When a board is
not running properly, you can reset the board so that it returns to the normal state. Reset is of
two types: warm reset and cold reset. A cold reset takes more time than a warm reset. After a
board is reset, the data on the board is not lost, but the resetting process may interrupt services.
l Performing a warm reset restores the applications and data to the normal state. Warm reset
usually does not affect services.
l Performing a cold reset restores the applications and data to the normal state before a CPU
power failure. Cold reset usually affects services.
34.6.2 Resetting the SCC Board

You can reset the SCC board by using the U2000. Resetting the SCC is a maintenance method
used in the case of an improper SCC working status.
Prerequisite
When the SCC is being reset, network communication is interrupted temporarily until the SCC
returns to the normal state. This may affect service switching. You can reset the SCC in the
following three ways:
l Performing a reset to the SCC by using the U2000.
l Performing a reset to the SCC by removing and inserting it.
l Performing a reset to the SCC by pushing the Reset button on the SCC.
Procedure
Step 1 Double-click an NE on the Main Topology and the slot layout is displayed.
Step 2 Right-click the SCC and choose SCC Reset from the shortcut menu.
Step 3 In the Warning dialog box displayed, click OK.
Step 4 Click Close in the dialog box displayed.
----End
34.6.3 Resetting a Non-SCC Board

You can reset a non-SCC board by using the U2000. Resetting a board is a maintenance method
used in the case of an improper board working status.

Prerequisite
Performing a warm reset usually does not affect services, but performing a cold reset usually
affects running services. You can reset a non-SCC board in the following two ways:
l Performing a warm or cold reset to the board by using the U2000.
l Performing a cold reset to the board by removing and inserting it.
Procedure
Step 1 Double-click an NE on the Main Topology and the slot layout is displayed.
Step 2 Right-click a non-SCC board and choose Cold Reset or Warm Reset from the shortcut menu.
Step 3 In the Warning dialog box displayed, click OK.
Step 4 Click Close in the prompt dialog box.
----End
34.6.4 Resetting a Board

You can reset a board by using the U2000. Resetting a board is a maintenance method used in
the case of an improper board working status.
Prerequisite
Context
Performing a cold reset usually affects services. You can reset a board in the following two ways:
l Performing a warm or cold reset to the board by using the U2000.
l Performing a cold reset to the board by removing and inserting it.
Procedure
Step 1 Double-click an NE on the Main Topology and the Slot Layout is displayed.
Step 2 Right-click a non-SCC board and choose Cold Reset or Warm Reset from the shortcut menu.
Click OK in the Warning dialog box to confirm the reset.
Step 3 Click Close in the prompt dialog box.
----End
34.7 Performing a Loopback

The loopback is a common and effective way to locate equipment faults. By using the U2000
you can set a loopback for equipment.

The support for loopback functions depends on equipment types. For details, refer to the specific
equipment manuals.
A loopback can be performed for different objects.
34.7.1 Setting a Loopback for an SDH Interface
You can set a loopback for an SDH interface by using the U2000. The SDH interface loopback
is a common fault location method used to test and maintain the SDH board. The SDH interface
loopback is used to test the fiber connections and interfaces on the SDH board, and is also used
to test the SDH service processing module and the cross-connect board.
34.7.2 Setting a Loopback for a PDH Interface
You can set a loopback for a PDH interface by using the U2000. The PDH interface loopback
is a common fault location method used to test and maintain the PDH board. The PDH interface
loopback is used to test the fiber connections and interfaces on the PDH board, and is also used
to test the PDH service processing module and the cross-connect board.
34.7.3 Setting a Loopback for an Ethernet Interface
You can set a loopback for an Ethernet interface by using the U2000. The Ethernet interface
loopback is a common fault location method used to test and maintain the Ethernet board. The
Ethernet interface loopback is used to test the fiber connections on the Ethernet board, physical
and MAC layers of the Ethernet interface, and SDH layer (that is, the line).
34.7.4 Setting a Loopback for an IF Interface
You can to set loopback for an intermediate frequency (IF) interface by using the U2000. The
IF interface loopback is a commonly used way of fault location during the test and maintenance
of the IF boards. By performing loopback for an IF interface, the system can determine whether
the IF interface and the fibers (cables) connected to the IF board are normal and whether the IF
board service processing module and the cross-connect board are normal.
34.7.5 Setting a Loopback for an ODU Interface
You can set a loopback for an ODU interface by using the U2000. The ODU interface loopback
is a common fault location method used to test and maintain the ODU board. The ODU interface
loopback is used to test the radio frequency (RF) link and interfaces on the ODU board, as well
as to test the ODU service processing module and the cross-connect board.
34.7.6 Setting a Loopback for a Digital Interface
This section describes how to set the loopback for the digital interface on the U2000. The digital
interface loopback is a commonly used way of fault location during the test and maintenance of
the IF boards. By performing the loopback at a digital interface, the system can determine
whether the IF interface and the fibers/cables connected to the IF board are normal and whether
the IF board service processing module and the cross-connect board are normal.
34.7.7 Setting a Loopback for a VC4 Path
You can set a loopback for a VC4 path by using the U2000. The VC4 path loopback is a common
fault location method used to test and maintain the SDH board. The VC4 path loopback is used
to test the fiber connections and interfaces on the SDH board, and is also used to test the SDH
service processing module and the cross-connect board.
The VC3 path loopback is a common fault location method to test and maintain the board. The
VC3 path loopback is used to test the fiber connections and SDH interfaces on the board, and
is also used to test the SDH service processing module and the cross-connect board.
34.7.1 Setting a Loopback for an SDH Interface

You can set a loopback for an SDH interface by using the U2000. The SDH interface loopback
is a common fault location method used to test and maintain the SDH board. The SDH interface

loopback is used to test the fiber connections and interfaces on the SDH board, and is also used
to test the SDH service processing module and the cross-connect board.
Prerequisite
Context
The SDH interface loopback can be set to an outloop or an inloop.
l When an outloop is used, the SDH signal received by the NE is returned at the SDH
interface. See Figure 34-1. An outloop is used to test the fibers connections and interfaces
on the SDH board.
Figure 34-1 Outloop
l When an inloop is used, the SDH signal transmitted by the NE is returned to the cross-
connect board at the SDH interface. See Figure 34-2. An inloop is used to test the SDH
Figure 34-2 Inloop
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Function Tree.

Step 2 Select By function and select Optical (Electrical) Interface Loopback.
Step 3 Select an SDH interface from the list and double-click Optical (Electrical) Interface
Loopback to choose a loopback mode.
Step 4 Click Apply and the Confirm dialog box is displayed.
Step 5 Click OK and the Prompt dialog box is displayed.
Step 6 Click OK. A prompt is displayed indicating that the operation is successful.
Step 7 Click Close.

NOTE
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
34.7.2 Setting a Loopback for a PDH Interface

You can set a loopback for a PDH interface by using the U2000. The PDH interface loopback
is a common fault location method used to test and maintain the PDH board. The PDH interface
loopback is used to test the fiber connections and interfaces on the PDH board, and is also used
to test the PDH service processing module and the cross-connect board.
Prerequisite
Context
The PDH interface loopback can be set to an outloop or an inloop.
l When an outloop is used, the PDH signal received by the NE is returned at the PDH
interface. See Figure 34-3. An outloop is used to test the fibers connections and interfaces
on the PDH board.
Figure 34-3 Outloop
l When an inloop is used, the PDH signal transmitted by the NE is returned to the cross-
connect board at the PDH interface. See Figure 34-4. An inloop is used to test the PDH

Figure 34-4 Inloop
CAUTION
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > PDH Interface from the
Function Tree.
Step 2 Select By function and select Tributary Loopback.
Step 3 Select a PDH interface from the list and double-click Tributary Loopback to choose the
loopback mode.
Step 6 Click Close.

NOTE
----End
34.7.3 Setting a Loopback for an Ethernet Interface

You can set a loopback for an Ethernet interface by using the U2000. The Ethernet interface
loopback is a common fault location method used to test and maintain the Ethernet board. The
Ethernet interface loopback is used to test the fiber connections on the Ethernet board, physical
and MAC layers of the Ethernet interface, and SDH layer (that is, the line).
Prerequisite
You can perform an inloop for an Ethernet interface by using the U2000.

When an inloop is used, the Ethernet signal transmitted by the NE is returned to the SDH layer
at the Ethernet interface. See Figure 34-5. The physical layer inloop is used to test the MAC
layer and the SDH layer. The MAC layer inloop is used to test the SDH layer.
Figure 34-5 Inloop
CAUTION
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree.
Step 2 Select External Port and click the Basic Attributes tab.
Step 3 Select an Ethernet interface from the list and double-click MAC Loopback or PHY
Loopback to choose the loopback mode.
Step 4 Click Apply and the U2000 prompts that this operation may interrupt the service.
----End
34.7.4 Setting a Loopback for an IF Interface

You can to set loopback for an intermediate frequency (IF) interface by using the U2000. The
IF interface loopback is a commonly used way of fault location during the test and maintenance
of the IF boards. By performing loopback for an IF interface, the system can determine whether
the IF interface and the fibers (cables) connected to the IF board are normal and whether the IF
board service processing module and the cross-connect board are normal.
Context
IF interface loopback can be set to an outloop or an inloop.
l When an outloop is used, the IF service received by NE is returned at the IF interface. See
Figure 34-6. An outloop can be used to test the IF interface and the fibers or cables
connected to the IF interface.

Figure 34-6 Outloop
l When an inloop is used, the IF service transmitted by NE is returned to the cross-connect

board at the IF interface. See Figure 34-7. An inloop can be used to test the IF board service
processing module and the cross-connect board.
Figure 34-7 Inloop
CAUTION
fault is removed.
Procedure
Step 1 In the NE Explorer, select an IF board and choose Configuration > IF Interface from the
Function Tree.
Step 2 Select By Function and select IF Port Loopback.
Step 3 Select an IF interface from the list and double-click IF Port Loopback to select a loopback
mode.
Step 6 Click Close.

NOTE
----End
34.7.5 Setting a Loopback for an ODU Interface

You can set a loopback for an ODU interface by using the U2000. The ODU interface loopback
is a common fault location method used to test and maintain the ODU board. The ODU interface
loopback is used to test the radio frequency (RF) link and interfaces on the ODU board, as well
as to test the ODU service processing module and the cross-connect board.
Context
The ODU interface loopback can be set to an outloop or an inloop.
l When an outloop is used, the RF service received by an NE is returned at the ODU interface.
See Figure 34-8. An outloop can be used to test the ODU interface and the RF link
connected to the ODU board.
Figure 34-8 Outloop
l When an inloop is used, the RF service transmitted by NE is returned to the cross-connect

board at the ODU interface. See Figure 34-9. An inloop can be used to test the ODU service
processing module and the cross-connect board.
Figure 34-9 Inloop

CAUTION
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > ODU Interface.
Step 2 Select By Function. Select RF Loopback.
Step 3 Select an RF interface from the list and double-click RF Loopback to select a loopback mode.
Step 6 Click Close.

NOTE
----End
34.7.6 Setting a Loopback for a Digital Interface

This section describes how to set the loopback for the digital interface on the U2000. The digital
interface loopback is a commonly used way of fault location during the test and maintenance of
the IF boards. By performing the loopback at a digital interface, the system can determine
whether the IF interface and the fibers/cables connected to the IF board are normal and whether
the IF board service processing module and the cross-connect board are normal.
Context
The digital interface loopback includes the outloop and inloop.
l When an outloop is used, the IF service received by the NE is returned at the IF interface.
See Figure 34-10. An outloop can be used to test the IF interface and the fibers/cables
connected to the IF interface.
Figure 34-10 Outloop

l When an inloop is used, the IF service transmitted by the NE is returned to the cross-connect
board at the IF interface. See Figure 34-11. An inloop can be used to test the IF board
Figure 34-11 Inloop
CAUTION
fault is removed.
Procedure
Step 1 In the NE Explorer, select an IF board and choose Configuration > Digital Interface from the
Function Tree.
Step 2 Select By Function. Select VC4 Loopback.
Step 3 Choose an digital interface from the list and double-click VC4 Loopback to select the loopback
mode.
Step 6 Click Close.
NOTE
----End

You can set a loopback for a VC4 path by using the U2000. The VC4 path loopback is a common
fault location method used to test and maintain the SDH board. The VC4 path loopback is used
to test the fiber connections and interfaces on the SDH board, and is also used to test the SDH
Prerequisite

The VC4 path loopback can be set to an outloop or an inloop.
l When an outloop is used, the VC4 signal received by the NE is returned over the VC4 path.
In Figure 34-12, an outloop is set for the first VC4 path on the line board. An outloop is
used to test the fibers connections and interfaces on the SDH board.
l When an inloop is used, the VC4 signal transmitted by the NE is returned to the cross-
connect board over the VC4 path. In Figure 34-13, an inloop is set for the first VC4 path
on the line board. An inloop is used to test the SDH service processing module and the
cross-connect board.
Figure 34-13 Inloop
CAUTION
fault is removed.
Procedure
Function Tree.
NOTE
For the intermediate frequency board: In the NE Explorer, select the board and choose Configuration > Digital

Step 2 Select By function and select VC4 Loopback.
Step 3 Select an SDH interface from the list and double-click VC4 Loopback to choose the loopback
mode.
Step 6 Click Close.

NOTE
----End

The VC3 path loopback is a common fault location method to test and maintain the board. The
VC3 path loopback is used to test the fiber connections and SDH interfaces on the board, and
is also used to test the SDH service processing module and the cross-connect board.
Prerequisite
l The related bound path must be configured.
Context
The VC3 path loopback can be set to an outloop or an inloop.
l When an outloop is used, the VC3 signal received by the NE is returned over the VC3 path.
In Figure 34-14, an outloop is set for the first VC3 path in the first VC4 path on the STM-1
line board. An outloop is used to test the fibers connections and interfaces on the SDH
board.
l When an inloop is used, the VC3 signal transmitted by the NE is returned over the VC3
path. In Figure 34-15, an inloop is set for the first VC3 path in the first VC4 path on the
STM-1 line board. An inloop is used to test the SDH service processing module and the
cross-connect board.

Figure 34-15 Inloop
CAUTION
fault is removed.
Procedure
Function Tree.
NOTE
For the intermediate frequency board: In the NE Explorer, select the board and choose Configuration > Digital
Step 2 Select By function and select VC3 Loopback.
Step 3 Select an SDH interface from the list and double-click VC3 Loopback to choose the loopback
mode.
Step 6 Click Close.

NOTE
----End
34.8 Setting Automatic Laser Shutdown

You can enable the automatic laser shut down function. In the event of a fiber cut, the laser at
an optical port is automatically off, to prevent hazardous laser radiation exposure from causing
permanent eye damage.
Prerequisite
The optical interface board must be created.

Procedure
Step 1 In the NE Explorer, click a board and choose Configuration > Automatic Laser Shutdown
Step 2 Set Auto ShutDown to Enabled. Set the On Period (ms), Off Period (ms) and Continuously
On-Test Period (ms).
Step 3 Click Apply.
----End
34.9 Disabling Service-Affecting Settings Automatically

Loopback and laser shutdown are useful NE maintenance functions. Performing these functions
may interrupt services at the port and may also interrupt the communication between the NE
and the U2000. Hence, you can set automatic disabling before performing loopback or laser
shutdown so that the NE automatically cancels the loopback or laser shutdown.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher..
If a port is the only way for an NE to communicate with the U2000, performing a loopback or
laser shutdown at the port results in the loss of communication. Before performing a loopback
or laser shutdown, you must set automatic disabling for this NE. Otherwise, after the
communication is lost, you cannot use the U2000 to log in to the NE to disable the loopback or
laser shutdown.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function
from the main menu.
Step 2 Select an NE and click the double-right-arrow button (red).
Step 3 Select a value in the Auto Disabling and Auto Disabling Time(min).
Step 4 Click Apply.
----End
34.10 Performing a PRBS Test

You can perform a PRBS test on a path to check the quality of the path. The test result is displayed
in the coordinates pane.

Prerequisite
l A service must be configured for the port for which you want to perform a PRBS test.
l The opposite port must be looped back before you perform a PRBS test.
Precaution
CAUTION
Performing a PRBS test interrupts services.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > PRBS Test from the Function
Tree.
Step 2 Select a channel or a port and set Duration and Measured in Time in the Set Test
Parameters area.
Step 3 Optional: Select Accumulating Mode. The test result is displayed in the coordinates pane in
an accumulative manner.
Step 4 Click Start to Test. A dialog box is displayed, indicating that this operation may interrupt the
service.
Step 5 Click Yes to start the PRBS test. After the test is complete, view the test result in the coordinates
pane.
----End
Postrequisite
You need to release loopback on the opposite port after the test is complete.
34.11 Diagnosing Ethernet Protocol Faults

In the case of an Ethernet service fault, you can diagnose the Ethernet protocol and then restart
the protocol state machine by restoring the protocol, to remove the protocol faults.
Prerequisite
Procedure
Maintenance > Protocol Fault Management from the Function Tree.
Step 2 Click the Protocol Type tab and click Diagnosis.

The user interface of the U2000 displays the diagnosis result.
----End

Prerequisite
Context
shortcut menu.
Procedure
gateway NE.
----End


OG For RTN NE Management - (V100R002C01 - 02) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OG For RTN NE Management - (V100R002C01 - 02) PDF

Uploaded by

Copyright:

Available Formats

iManager U2000 Unified Network Management

Operation Guide for RTN NE

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24) Huawei Proprietary and Confidential i

About This Document

Product Name Version

iManager U2000 V100R002C01

This document is intended for:

l Network Monitoring Engineer

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

Indicates a hazard with a medium or low level of risk, which

Issue 02 (2010-09-24) Huawei Proprietary and Confidential iii

Indicates a potentially hazardous situation, which if not

NOTE Provides additional information to emphasize or supplement

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

iv Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Updates in Issue 02 (2010-09-24) Based on Product Version V100R002C01

Updates in Issue 01 (2010-08-16) Based on Product Version V100R002C01

Issue 02 (2010-09-24) Huawei Proprietary and Confidential v

About This Document...................................................................................................................iii

Issue 02 (2010-09-24) Huawei Proprietary and Confidential vii

2.3.4 Adding the Manual ECC Route for an NE...........................................................................................2-20

viii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

3.1 Clock Configuration Process...........................................................................................................................3-3

4 Configuring PTP Clock.............................................................................................................4-1

Issue 02 (2010-09-24) Huawei Proprietary and Confidential ix

5.2.2 Configuring F1 Data Port Services........................................................................................................5-3

6 Configuring Environment Monitor Interfaces.....................................................................6-1

7 Configuring Interfaces (RTN 600)...........................................................................................7-1

8 Configuring Interfaces (RTN 900)...........................................................................................8-1

x Huawei Proprietary and Confidential Issue 02 (2010-09-24)

8.2.2 Setting the Layer 3 Attributes of PDH Interfaces..................................................................................8-8

Issue 02 (2010-09-24) Huawei Proprietary and Confidential xi

9 Configuring Radio Links..........................................................................................................9-1

10 Configuring Board 1+1 Protection......................................................................................10-1

11 Configuring the IF 1+1 Protection...................................................................................... 11-1

12 Configuring Network Level Protection.............................................................................12-1

xii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

12.1.1 Multiplex Section...............................................................................................................................12-3

Issue 02 (2010-09-24) Huawei Proprietary and Confidential xiii

12.5.4.6 Converting SNCP Services into Non-Protection Services............................................................12-60

13 Configuring SDH/PDH Services.........................................................................................13-1

xiv Huawei Proprietary and Confidential Issue 02 (2010-09-24)

13.6.2 Configuring VC-4 POHs..................................................................................................................13-26

14 Ethernet Feature(RTN 600)...................................................................................................14-1

Issue 02 (2010-09-24) Huawei Proprietary and Confidential xv

14.1.4.1 Ethernet LAN Service Configuration Process..............................................................................14-27

xvi Huawei Proprietary and Confidential Issue 02 (2010-09-24)

14.1.13.2 Service Planning (Microwave Services)...................................................................................14-101

Issue 02 (2010-09-24) Huawei Proprietary and Confidential xvii

14.3.7.2 Modifying the Type Field of Jumbo Frames...............................................................................14-190

xviii Huawei Proprietary and Confidential Issue 02 (2010-09-24)

Issue 02 (2010-09-24) Huawei Proprietary and Confidential xix