RTN 950 Configuration Guide (U2000) - (V100R002C01 - 01)

OptiX RTN 950 Radio Transmission System
V100R002C01
Configuration Guide (U2000)
Issue 01
Date 2010-09-25
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 01 (2010-09-25) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide (U2000) About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX RTN 950 V100R002C01
iManager U2000 V100R002C01
Intended Audience
This document describes how to configure various services on the equipment. This document
describes the basic information and configuration process, and uses configuration examples to
show how to set specific parameters.
The intended audience of this document are:
l Installation and commissioning engineer

l Data configuration engineer
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.
Indicates a hazard with a medium or low level

of risk, which if not avoided, could result in
minor or moderate injury.
Issue 01 (2010-09-25) Huawei Proprietary and Confidential iii

About This Document Configuration Guide (U2000)
Symbol Description
Indicates a potentially hazardous situation,

which if not avoided, could result in
equipment damage, data loss, performance
degradation, or unexpected results.
Indicates a tip that may help you solve a

problem or save time.
Provides additional information to emphasize

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

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

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

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

vertical bars. One item is selected or no item is selected.
iv Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Configuration Guide (U2000) About This Document
{ x | y | ... }* Optional items are grouped in braces and separated by

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

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

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

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 01 (2010-09-25) Based on Product Version V100R002C01

This document is the first release of the V100R002C01 product version.
Issue 01 (2010-09-25) Huawei Proprietary and Confidential v

Configuration Guide (U2000) Contents
Contents
About This Document...................................................................................................................iii

1 Configuration Preparations......................................................................................................1-1
1.1 Preparing Documents and Tools.....................................................................................................................1-2
1.2 Checking Configuration Conditions................................................................................................................1-2
1.3 Specifying the Configuration Procedure ........................................................................................................1-2
2 Configuring the Network Topology.......................................................................................2-1

2.1 Basic Concepts................................................................................................................................................2-2
2.1.1 DCN.......................................................................................................................................................2-2
2.1.2 GNE and Non-GNE...............................................................................................................................2-4
2.1.3 ID and IP Address of an NE...................................................................................................................2-4
2.1.4 Physical Boards and Logical Boards......................................................................................................2-5
2.1.5 Fiber/Cable Types..................................................................................................................................2-6
2.1.6 Subnet.....................................................................................................................................................2-6
2.2 Configuration Procedure.................................................................................................................................2-7
2.3 Configuration Example (Chain Network).....................................................................................................2-11
2.3.1 Networking Diagram............................................................................................................................2-12
2.3.2 Board Configuration.............................................................................................................................2-12
2.3.3 Service Planning...................................................................................................................................2-13
2.3.4 Configuration Process..........................................................................................................................2-14
2.4 Configuration Example (Ring Network).......................................................................................................2-17
2.4.2 Board Configuration.............................................................................................................................2-18
3 Configuring Radio Links..........................................................................................................3-1

3.1 Basic Concepts................................................................................................................................................3-2
3.1.1 Adaptive Modulation..............................................................................................................................3-2
3.1.2 CCDP and XPIC.....................................................................................................................................3-4
3.1.3 RF Configuration Modes........................................................................................................................3-5
3.2 Configuration Procedure.................................................................................................................................3-6
3.3 Configuration Example (Radio Links on the TDM Radio Chain Network).................................................3-14
Issue 01 (2010-09-25) Huawei Proprietary and Confidential vii

Contents Configuration Guide (U2000)

3.4 Configuration Example (Radio Links on the TDM Radio Ring Network)...................................................3-26
3.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network)...............................................3-36
3.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)................................................3-51
4 Configuring TDM Services......................................................................................................4-1

4.1 Basic Concepts................................................................................................................................................4-2
4.1.1 Protection Modes for TDM Services.....................................................................................................4-2
4.1.2 Timeslots for TDM Services on IF Boards............................................................................................4-5
4.1.3 Numbering Schemes for SDH Timeslots ..............................................................................................4-6
4.1.4 TDM Timeslot Planning Schemes.........................................................................................................4-7
4.2 Configuration Procedure...............................................................................................................................4-10
4.3 Configuration Example (TDM Services on a TDM Radio Chain Network)................................................4-13
4.4 Configuration Example (TDM Services on a TDM Radio Ring Network)..................................................4-21
4.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network)..............................................4-28
4.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network)................................................4-37
5 Configuring Packet-Based Ethernet Services.......................................................................5-1

5.1 Basic Concepts................................................................................................................................................5-2
5.1.1 IF_ETH Port...........................................................................................................................................5-3
5.1.2 Auto-Negotiation....................................................................................................................................5-3
5.1.3 Flow Control Function...........................................................................................................................5-5
viii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

5.1.4 Ethernet Service Types Based on the Packet Plane............................................................................... 5-6

5.1.4.1 Point-to-Point Transparently Transmitted E-Line Service..................................................................5-6
5.1.4.2 VLAN-based E-Line Services.............................................................................................................5-7
5.1.4.3 QinQ-Based E-Line Services..............................................................................................................5-9
5.1.4.4 E-LAN Services Based on the IEEE 802.1d Bridge.........................................................................5-13
5.1.4.5 E-LAN Services Based on the IEEE 802.1q Bridge.........................................................................5-14
5.1.4.6 E-LAN Services Based on the IEEE 802.1ad Bridge.......................................................................5-15
5.1.5 Typical Networking of Ethernet Services on a Mobile Carrier Network.............................................5-17
5.1.5.1 Networking of VLAN-Based E-Line Services..................................................................................5-18
5.1.5.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services...........................................................5-18
5.1.5.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services...........................................................5-19
5.1.5.4 Comparison Between the Three Networking Modes........................................................................5-20
5.1.6 Managing a MAC Address Table.........................................................................................................5-24
5.1.7 VLAN Forwarding Table.....................................................................................................................5-24
5.1.8 Split Horizon Group.............................................................................................................................5-25
5.1.9 Protection for Ethernet Services Based on the Packet Plane................................................................5-26
5.1.10 QoS Based on the Packet Plane..........................................................................................................5-29
5.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services)......................5-34
5.2.2 Configuration Procedure (VLAN-Based E-Line Services)..................................................................5-40
5.2.3 Configuration Procedure (QinQ-Based E-Line Services)....................................................................5-46
5.2.4 Procedures for Configuring 802.1d Bridge-Based E-LAN Services...................................................5-52
5.2.5 Configuration Procedure (802.1q-Bridge-Based E-LAN Services).....................................................5-59
5.2.6 Configuration Procedure (802.1ad-Bridge-Based E-LAN Services)...................................................5-65
5.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services).................................5-72
5.3.2.1 Service Planning (Ethernet Ports).....................................................................................................5-74
5.3.2.2 Service Planning (Ethernet Protection).............................................................................................5-75
5.3.2.3 Service Planning (Ethernet Services)................................................................................................5-75
5.3.2.4 Service Planning (QoS).....................................................................................................................5-76
5.3.3.1 Configuration Process (Ethernet Ports).............................................................................................5-78
5.3.3.2 Configuration Process (Ethernet Protection).....................................................................................5-79
5.3.3.3 Configuration Process (Service Information)...................................................................................5-79
5.3.3.4 Configuration Process (QoS)............................................................................................................5-79
5.3.3.5 Configuration Process (Verifying Ethernet Service Configurations)................................................5-81
5.4 Configuration Example (VLAN-Based E-Line Service)..............................................................................5-83
Issue 01 (2010-09-25) Huawei Proprietary and Confidential ix


5.4.3.2 Configuration Process (Ethernet Protection)...................................................................................5-101
5.4.3.3 Configuration Process (Service Information).................................................................................5-102
5.4.3.4 Configuration Process (QoS)..........................................................................................................5-105
5.4.3.5 Configuration Process (Verifying Ethernet Service Configurations)..............................................5-110
5.5 Configuration Example (QinQ-Based E-Line Service)...............................................................................5-115
5.5.1 Networking Diagram..........................................................................................................................5-115
5.5.2 Service Planning.................................................................................................................................5-118
5.5.2.1 Service Planning (Ethernet Ports)...................................................................................................5-119
5.5.2.2 Service Planning (Ethernet Protection)...........................................................................................5-123
5.5.2.3 Service Planning (Ethernet Services)..............................................................................................5-123
5.5.2.4 Service Planning (QoS)...................................................................................................................5-127
5.5.3 Configuration Process........................................................................................................................5-130
5.5.3.1 Configuration Process (Ethernet Ports)...........................................................................................5-130
5.6 Configuration Example (802.1d-Bridge-Based E-LAN Service)...............................................................5-154
5.7 Configuration Example (802.1q-Bridge-Based E-LAN Service)...............................................................5-175
x Huawei Proprietary and Confidential Issue 01 (2010-09-25)


5.8 Configuration Example (802.1ad-Bridge-Based E-LAN Service)..............................................................5-206
5.9 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)........................5-232
6 Configuring EoPDH-Based Ethernet Services.....................................................................6-1

6.1 Basic Concepts................................................................................................................................................6-2
6.1.1 VCTRUNK.............................................................................................................................................6-2
6.1.2 Bridging Ports on the EFP8 Board.........................................................................................................6-2
6.1.3 Transmission Modes of Ethernet Services.............................................................................................6-3
6.1.4 Hub/Spoke..............................................................................................................................................6-4
6.1.5 EoPDH-Based Ethernet Services...........................................................................................................6-4
6.1.5.1 Point-to-Point Transparently Transmitted EPL Services....................................................................6-5
6.1.5.2 EVPL Services Based on the VLAN...................................................................................................6-5
6.1.5.3 QinQ-based EVPL Services................................................................................................................6-7
6.1.5.4 EPLAN Services Based on the 802.1d Bridge..................................................................................6-10
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xi

6.1.5.5 EVPLAN Services Based on the 802.1q Bridge...............................................................................6-11

6.1.5.6 EVPLAN Services Based on 802.1ad Bridge...................................................................................6-13
6.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted EPL Services)..........................6-15
6.2.2 Configuration Procedure (VLAN-Based EVPL Services)...................................................................6-20
6.2.3 Configuration Procedure (QinQ-Based EVPL Services).....................................................................6-26
6.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN Services)...........................................6-33
6.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN Services)........................................6-39
6.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based EVPLAN Services)......................................6-46
6.3 Configuration Example (Ethernet Services Based on TDM Radio).............................................................6-53
6.3.2.4 Service Planning (Ethernet Service Cross-Connections)..................................................................6-61
6.3.3.2 Configuration Process (Ethernet Protection).....................................................................................6-68
6.3.3.3 Configuration Process (Ethernet Services).......................................................................................6-69
6.3.3.4 Configuration Process (Cross-Connections) ....................................................................................6-70
6.3.3.5 Configuration Process (QoS)............................................................................................................6-72
6.3.3.6 Configuration Process (Verifying Ethernet Service Configurations)................................................6-72
6.4 Configuration Example (Ethernet Services Traversing a TDM Network)....................................................6-75
6.4.2.1 Service Planning (Ethernet Ports on the Packet Plane).....................................................................6-78
6.4.2.2 Service Planning (Ethernet Services on the Packet Plane)................................................................6-79
6.4.2.3 Service Planning (QoS on the Packet Plane)....................................................................................6-79
6.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board)......................................................................6-81
6.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board).............................................................6-83
6.4.2.6 Service Planning (Ethernet Services on the EFP8 Board)................................................................6-84
6.4.2.7 Service Planning (Cross-Connections)..............................................................................................6-85
6.4.2.8 Service Planning (QoS of the EFP8 Board)......................................................................................6-86
6.4.3.1 Configuration Process (Ethernet Ports on the Packet Plane) ...........................................................6-89
6.4.3.2 Configuration Process (Ethernet Services on the Packet Plane) ......................................................6-90
6.4.3.3 Configuration Process (QoS on the Packet Plane)............................................................................6-90
6.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board).............................................................6-93
6.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board).....................................................6-95
6.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board)........................................................6-96
xii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

6.4.3.7 Configuration Process (Cross-Connections) ....................................................................................6-97

6.4.3.8 Configuration Process (QoS on the EFP8 Board).............................................................................6-98
7 Configuring the Clock...............................................................................................................7-1

7.1 Basic Concepts................................................................................................................................................7-2
7.1.1 Clock Source..........................................................................................................................................7-2
7.1.2 Clock Protection Schemes......................................................................................................................7-2
7.1.3 Clock Synchronization Policy................................................................................................................7-6
7.3 Configuration Example (Clock for a TDM Radio Chain Network)..............................................................7-16
7.4 Configuration Example (Clock for a TDM Radio Ring Network)...............................................................7-20
7.5 Configuration Example (Clock for a Hybrid Radio Chain Network)...........................................................7-24
7.6 Configuration Example (Clock for a Hybrid Radio Ring Network).............................................................7-27
7.7 Configuration Example (Clocks Across a Third-party TDM Network).......................................................7-30
8 Configuring Auxiliary Ports and Functions..........................................................................8-1

8.1 Auxiliary Ports and Functions.........................................................................................................................8-2
8.2 Configuration Example (Orderwire)...............................................................................................................8-4
8.2.1 Networking Diagram..............................................................................................................................8-5
8.2.2 Service Planning.....................................................................................................................................8-6
8.2.3 Configuration Process............................................................................................................................8-8
8.3 Configuration Example (Synchronous Data Services)....................................................................................8-9
8.3.1 Networking Diagram..............................................................................................................................8-9
8.4 Configuration Example (Asynchronous Data Services)...............................................................................8-12
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xiii


8.5 Configuration Example (Wayside E1 Services)............................................................................................8-15
8.6 Configuration Example (External Alarms)...................................................................................................8-17
9 Adding and Modifying Configuration Data........................................................................9-1

9.1 Common Task Collection (Network Topology).............................................................................................9-2
9.2 Common Task Collection (Radio Links)........................................................................................................9-3
9.3 Common Task Collection (TDM Services)....................................................................................................9-7
9.4 Common Task Collection (Packet-Plane Ethernet Services)..........................................................................9-8
9.5 Common Task Collection (EoPDH-Plane Ethernet Services)......................................................................9-10
A Task Collection.........................................................................................................................A-1
A.1 Managing NEs...............................................................................................................................................A-3
A.1.1 Creating NEs by Using the Search Method..........................................................................................A-3
A.1.2 Creating NEs by Using the Manual Method........................................................................................A-5
A.1.3 Configuring the Logical Board.............................................................................................................A-6
A.1.4 Changing the NE ID.............................................................................................................................A-7
A.1.5 Changing the NE Name........................................................................................................................A-8
A.1.6 Synchronizing the NE Time.................................................................................................................A-9
A.1.7 Localizing the NE Time.....................................................................................................................A-12
A.1.8 Configuring Standard NTP Keys........................................................................................................A-12
A.2 Configuring the NE Data.............................................................................................................................A-13
A.2.1 Uploading the NE Data......................................................................................................................A-14
A.3 Configuring the Performance Monitoring Status of NEs............................................................................A-14
A.4 Connecting Fibers or Cables.......................................................................................................................A-15
A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method........................A-16
A.4.2 Creating a Radio Link by Using the Manual Method........................................................................A-17
A.4.3 Creating an SDH Optical Transmission Link by Using the Manual Method.....................................A-18
A.4.4 Creating an Extended ECC.................................................................................................................A-19
A.4.5 Creating a Back-to-Back Radio Connection......................................................................................A-20
A.5 Managing Subnets.......................................................................................................................................A-21
A.5.1 Creating a Subnet...............................................................................................................................A-21
A.5.2 Copying Topology Objects.................................................................................................................A-22
A.5.3 Moving Topology Objects..................................................................................................................A-22
A.6 Managing Communications.........................................................................................................................A-23
A.6.1 Setting NE Communication Parameters.............................................................................................A-24
A.6.2 Configuring DCCs..............................................................................................................................A-25
A.6.3 Configuring the Extended ECC..........................................................................................................A-26
xiv Huawei Proprietary and Confidential Issue 01 (2010-09-25)

A.6.4 Configuring DCC Transparent Transmission.....................................................................................A-27

A.6.5 Creating Static IP Routes....................................................................................................................A-28
A.6.6 Setting Parameters of the OSPF Protocol...........................................................................................A-29
A.6.7 Enabling the ARP Proxy....................................................................................................................A-30
A.6.8 Configuring the CLNS Role...............................................................................................................A-30
A.6.9 Configuring the OSI Tunnel...............................................................................................................A-31
A.6.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN.............................................A-32
A.6.11 Configuring the Enable Status of the Inband DCN Function on Ports.............................................A-33
A.6.12 Configuring the Protocol Type of the Inband DCN.........................................................................A-34
A.6.13 Querying ECC Routes......................................................................................................................A-34
A.6.14 Querying IP Routes..........................................................................................................................A-35
A.6.15 Querying OSI Routes.......................................................................................................................A-35
A.6.16 Configuring Access Control.............................................................................................................A-36
A.7 Configuring Service Access of NEs ...........................................................................................................A-37
A.7.1 Configuring LCT Access to NEs........................................................................................................A-37
A.7.2 Configuring Ethernet Access to NEs..................................................................................................A-38
A.7.3 Configuring Serial Interface Access to NEs.......................................................................................A-38
A.8 Managing Radio Links................................................................................................................................A-39
A.8.1 Creating an IF 1+1 Protection Group.................................................................................................A-40
A.8.2 Creating an XPIC Protection Group...................................................................................................A-41
A.8.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link..................................................A-42
A.8.4 Configuring the IF/ODU Information of a Radio Link......................................................................A-43
A.8.5 Setting IF Attributes...........................................................................................................................A-44
A.8.6 Configuring the ATPC Attributes......................................................................................................A-45
A.8.7 Setting the Hybrid/AM Attributes......................................................................................................A-46
A.8.8 Setting Advanced AM Attributes.......................................................................................................A-47
A.8.9 Modifying the Priorities of E1 Services.............................................................................................A-48
A.8.10 Creating an N+1 Protection Group...................................................................................................A-49
A.8.11 Querying the ATPC Adjustment Records........................................................................................A-50
A.8.12 Querying the History Transmit Power and Receive Power..............................................................A-50
A.8.13 Querying the AM Status...................................................................................................................A-51
A.8.14 Querying the IF 1+1 Protection Status.............................................................................................A-52
A.8.15 Querying the IF N+1 Protection Status............................................................................................A-52
A.8.16 IF 1+1 Protection Switching.............................................................................................................A-53
A.8.17 IF N+1 Protection Switching............................................................................................................A-53
A.8.18 Starting/Stopping the N+1 Protection Protocol................................................................................A-54
A.9 Managing the MSP......................................................................................................................................A-55
A.9.1 Configuring Linear MSP....................................................................................................................A-55
A.9.2 Querying the Status of the Linear MSP..............................................................................................A-56
A.9.3 Performing Linear MSP Switching....................................................................................................A-57
A.9.4 Starting/Stopping the Linear MSP Protocol.......................................................................................A-58
A.10 Managing TDM Services..........................................................................................................................A-58
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xv

A.10.1 Creating the Cross-Connections of Point-to-Point Services............................................................A-59

A.10.2 Creating Cross-Connections of SNCP Services...............................................................................A-60
A.10.3 Inserting TU_AIS.............................................................................................................................A-60
A.10.4 Configuring the Automatic Switching of SNCP Services................................................................A-61
A.10.5 Deleting Cross-Connections.............................................................................................................A-62
A.10.6 Converting a Normal Service into an SNCP Service.......................................................................A-63
A.10.7 Converting an SNCP Service to a Normal Service..........................................................................A-64
A.10.8 Querying TDM Services...................................................................................................................A-65
A.10.9 Switching SNCP Services................................................................................................................A-65
A.10.10 Querying the Protection Status of SNCP Services.........................................................................A-66
A.10.11 Testing the E1 Service Through PRBS..........................................................................................A-66
A.11 Managing the Clock..................................................................................................................................A-68
A.11.1 Configuring the Clock Sources........................................................................................................A-69
A.11.2 Configuring Clock Subnets..............................................................................................................A-70
A.11.3 Self-Defined Clock Quality..............................................................................................................A-71
A.11.4 Configuring the SSM Output Status.................................................................................................A-72
A.11.5 Configuring the Clock ID Output Status..........................................................................................A-73
A.11.6 Modifying the Parameters of the Clock Output...............................................................................A-74
A.11.7 Changing the Conditions for Clock Source Switching.....................................................................A-74
A.11.8 Modifying the Recovery Parameter of the Clock Source.................................................................A-75
A.11.9 Querying the Clock Synchronization Status.....................................................................................A-75
A.12 Configuring Ethernet Services and Features on the Packet Plane.............................................................A-76
A.12.1 Managing the ERPS ........................................................................................................................A-77
A.12.1.1 Creating Ethernet Ring Protection Instances.................................................................................A-77
A.12.1.2 Setting the Parameters of Ethernet Ring Protocol.........................................................................A-78
A.12.1.3 Querying the Status of the Ethernet Ring Protocol.......................................................................A-79
A.12.2 Managing the LAG...........................................................................................................................A-79
A.12.2.1 Creating a LAG.............................................................................................................................A-80
A.12.2.2 Setting Parameters for LAGs.........................................................................................................A-81
A.12.2.3 Querying the Protocol Information of the LAG............................................................................A-82
A.12.3 Configure the Ethernet Service........................................................................................................A-83
A.12.3.1 Configuring the QinQ Link...........................................................................................................A-83
A.12.3.2 Configuring the E-Line Service.....................................................................................................A-84
A.12.3.3 Creating a VLAN Forwarding Table Item....................................................................................A-86
A.12.3.4 Configuring the E-LAN Service....................................................................................................A-86
A.12.3.5 Changing Logical Ports Connected to a VB..................................................................................A-90
A.12.3.6 Deleting an E-Line Service...........................................................................................................A-91
A.12.3.7 Deleting E-LAN Services..............................................................................................................A-92
A.12.3.8 Testing the Ethernet Service..........................................................................................................A-92
A.12.4 Managing the MAC Address Table..................................................................................................A-96
A.12.4.1 Creating a Static MAC Address Entry..........................................................................................A-97
A.12.4.2 Creating a Blacklist Entry of MAC Addresses..............................................................................A-98
xvi Huawei Proprietary and Confidential Issue 01 (2010-09-25)

A.12.4.3 Configuring the Aging Parameters of a MAC Address Table.......................................................A-98

A.12.4.4 Querying or Deleting a Dynamic MAC Address..........................................................................A-99
A.12.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service................................A-100
A.12.6 Setting the Parameters of Ethernet Ports........................................................................................A-100
A.12.6.1 Setting the General Attributes of Ethernet Ports.........................................................................A-101
A.12.6.2 Configuring the Traffic Control of Ethernet Ports......................................................................A-101
A.12.6.3 Setting the Layer 2 Attributes of Ethernet Ports.........................................................................A-102
A.12.6.4 Setting the Advanced Attributes of Ethernet Ports......................................................................A-103
A.12.7 Setting the General Attributes of the IF_ETH Port........................................................................A-104
A.12.7.1 Setting the General Attributes of the IF_ETH Port.....................................................................A-104
A.12.7.2 Setting the Layer 2 Attributes of the IF_ETH Port.....................................................................A-104
A.12.7.3 Setting the Advanced Attributes of the IF_ETH Port.................................................................A-105
A.12.8 Managing the MSTP.......................................................................................................................A-106
A.12.8.1 Creating the MSTP Port Group...................................................................................................A-106
A.12.8.2 Setting the Bridge Parameters of the MSTP................................................................................A-107
A.12.8.3 Setting the Parameters of the CIST.............................................................................................A-108
A.12.8.4 Querying the CIST Running Information....................................................................................A-109
A.12.8.5 Changing the Spanning Tree Protocol Used by the Port Group..................................................A-110
A.12.8.6 Enabling/Disabling the MSTP Protocol......................................................................................A-110
A.12.8.7 Modifying the Configuration Data of the MSTP Port Group......................................................A-111
A.12.9 Managing the IGMP Snooping.......................................................................................................A-112
A.12.9.1 Configuring the IGMP Snooping Protocol..................................................................................A-113
A.12.9.2 Querying the Port Information of the Routers.............................................................................A-113
A.12.9.3 Querying the Information About the Multicast Groups..............................................................A-114
A.12.9.4 Creating Static Router Ports........................................................................................................A-115
A.12.9.5 Creating a Member of a Static Multicast Group..........................................................................A-116
A.12.9.6 Adding a Quickly Deleted Port...................................................................................................A-117
A.12.9.7 Calculating IGMP Packets..........................................................................................................A-117
A.12.10 Managing the QoS........................................................................................................................A-118
A.12.10.1 Creating a DS Domain...............................................................................................................A-118
A.12.10.2 Modifying the DS Domain........................................................................................................A-120
A.12.10.3 Changing the Ports That Use the DS Domain...........................................................................A-121
A.12.10.4 Creating a Port Policy................................................................................................................A-122
A.12.10.5 Modifying the Port Policy.........................................................................................................A-123
A.12.10.6 Creating the Traffic...................................................................................................................A-124
A.12.10.7 Setting the Port That Uses the Port Policy................................................................................A-125
A.12.10.8 Configuring Port Shaping..........................................................................................................A-127
A.12.10.9 Querying the Port Policy...........................................................................................................A-127
A.12.10.10 Querying the DS Domain of a Port.........................................................................................A-128
A.12.11 Using the IEEE 802.1ag OAM.....................................................................................................A-129
A.12.11.1 Creating an MD.........................................................................................................................A-130
A.12.11.2 Creating an MA.........................................................................................................................A-131
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xvii

A.12.11.3 Creating an MEP Point..............................................................................................................A-131

A.12.11.4 Creating Remote MEPs in an MA.............................................................................................A-132
A.12.11.5 Creating an MIP........................................................................................................................A-133
A.12.11.6 Performing a CC Test................................................................................................................A-134
A.12.11.7 Performing an LB Test..............................................................................................................A-135
A.12.11.8 Performing an LT Test..............................................................................................................A-136
A.12.12 Using the IEEE 802.3ah OAM ....................................................................................................A-137
A.12.12.1 Enabling the OAM Auto-Discovery Function..........................................................................A-138
A.12.12.2 Enabling the Link Event Notification .......................................................................................A-139
A.12.12.3 Modifying the OAM Error Frame Monitoring Threshold ........................................................A-140
A.12.12.4 Performing Remote Loopback..................................................................................................A-141
A.12.12.5 Enabling Self-Loop Detection ..................................................................................................A-142
A.12.13 LPT Configuration........................................................................................................................A-143
A.13 Configuring Ethernet Services and Features on the EoPDH Plane.........................................................A-144
A.13.1 Managing LAGs ............................................................................................................................A-145
A.13.1.1 Creating a LAG...........................................................................................................................A-145
A.13.1.2 Setting Parameters for LAGs.......................................................................................................A-147
A.13.1.3 Querying the Protocol Information of LAGs..............................................................................A-148
A.13.2 Configuring Ethernet Services.......................................................................................................A-149
A.13.2.1 Creating Ethernet Private Line Services......................................................................................A-150
A.13.2.2 Creating Ethernet LAN Services.................................................................................................A-152
A.13.2.3 Changing the Ports Connected to a VB.......................................................................................A-156
A.13.2.4 Creating the VLAN Filtering Table............................................................................................A-157
A.13.2.5 Creating QinQ-Based EVPL Services.........................................................................................A-158
A.13.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services..........................................................A-160
A.13.2.7 Deleting an Ethernet Private Line Service..................................................................................A-163
A.13.2.8 Deleting an Ethernet LAN Service..............................................................................................A-164
A.13.3 Managing the MAC Address Table................................................................................................A-164
A.13.3.1 Creating a Static MAC Address Entry........................................................................................A-165
A.13.3.2 Creating a Blacklist Entry of a MAC Address............................................................................A-166
A.13.3.3 Setting the Aging Time of a MAC Address Table Entry ...........................................................A-166
A.13.3.4 Querying or Deleting a Dynamic MAC Address........................................................................A-167
A.13.3.5 Querying the Actual Capacity of a MAC Address Table............................................................A-167
A.13.4 Configuring Ethernet Ports.............................................................................................................A-168
A.13.4.1 Configuring External Ethernet Ports...........................................................................................A-169
A.13.4.2 Configuring VCTRUNKs on an Ethernet Board.........................................................................A-170
A.13.4.3 Modifying the Type Field of QinQ Frames.................................................................................A-172
A.13.4.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth...............................................A-173
A.13.5 Managing the Spanning Tree Protocol...........................................................................................A-174
A.13.5.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol..................................A-175
A.13.5.2 Setting the Parameters of Spanning Tree Protocol......................................................................A-175
A.13.5.3 Querying the Running Information About the Spanning Tree Protocol.....................................A-176
xviii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

A.13.6 Managing the IGMP Snooping Protocol........................................................................................A-177

A.13.6.1 Configuring the IGMP Snooping Protocol..................................................................................A-177
A.13.6.2 Configuring Static Multicast Entries...........................................................................................A-178
A.13.6.3 Modifying the Aging Time of a Multicast Table Entry..............................................................A-179
A.13.6.4 Querying the Running Information of the IGMP Snooping Protocol.........................................A-180
A.13.7 Managing the QoS..........................................................................................................................A-181
A.13.7.1 Creating a Flow...........................................................................................................................A-181
A.13.7.2 Creating the CAR........................................................................................................................A-182
A.13.7.3 Creating the CoS..........................................................................................................................A-183
A.13.7.4 Binding the CAR/CoS.................................................................................................................A-185
A.13.7.5 Configuring Traffic Shaping for Egress Queues.........................................................................A-186
A.13.8 Using the IEEE 802.1ag OAM ......................................................................................................A-186
A.13.8.1 Creating MDs..............................................................................................................................A-187
A.13.8.2 Creating MAs..............................................................................................................................A-188
A.13.8.3 Creating MPs...............................................................................................................................A-189
A.13.8.4 Performing a CC Test..................................................................................................................A-191
A.13.8.5 Performing an LB Test................................................................................................................A-191
A.13.8.6 Performing an LT Test................................................................................................................A-193
A.13.8.7 Activating the AIS.......................................................................................................................A-194
A.13.8.8 Performing a Ping Test ...............................................................................................................A-194
A.13.8.9 Performing Performance Check..................................................................................................A-195
A.13.9 Using the IEEE 802.3ah OAM.......................................................................................................A-196
A.13.9.1 Enabling the OAM Auto-Discovery Function............................................................................A-196
A.13.9.2 Enabling the Link Event Notification..........................................................................................A-197
A.13.9.3 Modifying the OAM Error Frame Monitoring Threshold...........................................................A-198
A.13.9.4 Performing the Remote Loopback...............................................................................................A-199
A.13.10 Configuring LPT..........................................................................................................................A-200
A.13.10.1 Configuring LPT for Point-to-Point Services............................................................................A-200
A.13.10.2 Configuring LPT for Point-to-Multipoint Services...................................................................A-201
A.14 Using the RMON.....................................................................................................................................A-203
A.14.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port.................................A-204
A.14.2 Configuring an Alarm Group for an Ethernet Port.........................................................................A-204
A.14.3 Configuring a History Control Group............................................................................................A-205
A.14.4 Browsing the Performance Data in the History Group of an Ethernet Port...................................A-206
A.15 Setting the Parameters of ODU Ports......................................................................................................A-206
A.15.1 Setting the Transmit Frequency Attribute of the ODU..................................................................A-207
A.15.2 Querying the ODU Attribute..........................................................................................................A-207
A.15.3 Setting the Power Attributes of the ODU.......................................................................................A-208
A.15.4 Setting the Advanced Attributes of the ODU.................................................................................A-208
A.15.5 Setting the State of an ODU Transmitter.......................................................................................A-209
A.16 Setting the Parameters of SDH Ports.......................................................................................................A-210
A.17 Setting the Parameters of PDH Ports.......................................................................................................A-211
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xix

A.18 Configuring Overhead Bytes...................................................................................................................A-211

A.18.1 Configuring RSOHs.......................................................................................................................A-212
A.18.2 Configuring VC-4 POHs................................................................................................................A-213
A.18.3 Configuring VC-12 POHs..............................................................................................................A-214
A.19 Configuring Auxiliary Ports and Functions............................................................................................A-215
A.19.1 Configuring the Orderwire.............................................................................................................A-215
A.19.2 Configuring the Synchronous Data Service...................................................................................A-216
A.19.3 Configuring the Asynchronous Data Service.................................................................................A-217
A.19.4 Configuring the Wayside E1 Service.............................................................................................A-218
A.19.5 Configure External Alarms.............................................................................................................A-219
A.20 Testing the Protection Switching.............................................................................................................A-220
A.20.1 Testing the IF 1+1 Switching.........................................................................................................A-221
A.20.2 Testing the N+1 Protection Switching...........................................................................................A-224
A.20.3 Testing the SNCP Switching..........................................................................................................A-227
A.20.4 Testing the ERPS............................................................................................................................A-230
A.20.5 Testing the Linear MSP Switching.................................................................................................A-232
A.21 Testing the AM Switching.......................................................................................................................A-235
A.21.1 Testing the AM Switching by Using a BER Tester.......................................................................A-236
A.21.2 Testing the AM Switching Without a BER Tester.........................................................................A-238
B Parameters Description............................................................................................................B-1
B.1 Parameters for NE Management....................................................................................................................B-3
B.1.1 Parameter Description: NE Searching..................................................................................................B-3
B.1.2 Parameter Description: NE Creation....................................................................................................B-8
B.1.3 Parameter Description: Attribute_Changing NE IDs.........................................................................B-10
B.1.4 Parameter Description: NE Time Synchronization.............................................................................B-11
B.1.5 Parameter Description: Localization Management of the NE Time...................................................B-14
B.1.6 Parameter Description: Standard NTP Key Management..................................................................B-15
B.1.7 Parameter Description: License Management....................................................................................B-16
B.1.8 Parameter Description: Automatic Disabling of the Functions of NEs..............................................B-17
B.2 Parameters for Cable Management..............................................................................................................B-18
B.2.1 Parameter Description: Fiber Search..................................................................................................B-18
B.2.2 Parameter Description: Fiber Creation...............................................................................................B-20
B.2.3 Parameter Description: Radio Link Creation......................................................................................B-22
B.3 Parameters for Communications Management............................................................................................B-23
B.3.1 Parameter Description: NE Communication Parameter Setting.........................................................B-24
B.3.2 Parameter Description: DCC Management_DCC Rate Configuration...............................................B-25
B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management..............B-27
B.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECC.........................................B-29
B.3.5 Parameter Description: NE ECC Link Management..........................................................................B-31
B.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management...............................B-32
B.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation................B-34
B.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings..........................B-34
xx Huawei Proprietary and Confidential Issue 01 (2010-09-25)

B.3.9 Parameter Description: IP Protocol Stack_Proxy ARP......................................................................B-37

B.3.10 Parameter Description: OSI Management_Network Layer Parameter.............................................B-38
B.3.11 Parameter Description: OSI Management_Routing Table...............................................................B-39
B.3.12 Parameter Description: OSI Management_OSI Tunnel....................................................................B-40
B.3.13 Parameter Description: DCN Management_Bandwidth Management.............................................B-44
B.3.14 Parameter Description: DCN Management_Port Setting.................................................................B-45
B.3.15 Parameter Description: DCN Management_Protocol Setting..........................................................B-46
B.3.16 Parameter Description: DCN Management_Access Control............................................................B-47
B.3.17 Parameter Description: Access Control............................................................................................B-48
B.3.18 Parameter Description: LCT Access Control...................................................................................B-48
B.4 Radio Link Parameters.................................................................................................................................B-49
B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation.........................................B-50
B.4.2 Parameter Description: Link Configuration_XPIC............................................................................B-54
B.4.3 Parameter Description: N+1 Protection_Create..................................................................................B-62
B.4.4 Parameter Description: N+1 Protection..............................................................................................B-63
B.4.5 Parameter: IF 1+1 Protection_Create..................................................................................................B-65
B.4.6 Parameter Description: IF 1+1 Protection..........................................................................................B-67
B.4.7 Parameter: Link Configuration_IF/ODU Configuration....................................................................B-70
B.5 Multiplex Section Protection Parameters.....................................................................................................B-78
B.5.1 Parameter Description: Linear MSP_Creation...................................................................................B-78
B.5.2 Parameter Description: Linear MSP...................................................................................................B-82
B.6 SDH/PDH Service Parameters.....................................................................................................................B-85
B.6.1 Parameter Description: SDH Service Configuration_Creation..........................................................B-85
B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation..................................B-87
B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services
......................................................................................................................................................................B-90
B.6.4 Parameter Description: SDH Service Configuration..........................................................................B-93
B.6.5 Parameter Description: SNCP Service Control..................................................................................B-95
B.6.6 Parameter Description: TU_AIS Insertion..........................................................................................B-98
B.7 Clock Parameters.........................................................................................................................................B-99
B.7.1 Parameter Description: Clock Source Priority Table........................................................................B-100
B.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet...........................................................B-101
B.7.3 Parameter Description: Clock Subnet Setting_Clock Quality..........................................................B-105
B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control................................................B-108
B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status........................................B-109
B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters................B-111
B.7.7 Parameter Description: Clock Source Switching_Clock Source Switching.....................................B-113
B.7.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions..................B-114
B.7.9 Parameter Description: Output Phase-Locked Source of the External Clock Source......................B-116
B.7.10 Parameter Description: Clock Synchronization Status...................................................................B-118
B.8 RMON Parameters.....................................................................................................................................B-120
B.8.1 Parameter Description: RMON Performance_Statistics Group........................................................B-120
B.8.2 Parameter Description: RMON Performance_History Group..........................................................B-121
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxi

B.8.3 Parameter Description: RMON Performance_History Control Group.............................................B-122

B.8.4 Parameter Description: RMON Performance_RMON Setting.........................................................B-123
B.9 Parameters for Ethernet Services and Ethernet Features on the Packet Plane...........................................B-125
B.9.1 Parameters for Ethernet Services......................................................................................................B-125
B.9.1.1 Parameter Description: E-Line Service_Creation..........................................................................B-126
B.9.1.2 Parameter Description: E-Line Service..........................................................................................B-132
B.9.1.3 Parameter Description: VLAN Forwarding Table Item_Creation.................................................B-138
B.9.1.4 Parameter Description: E-LAN Service_Creation.........................................................................B-139
B.9.1.5 Parameter Description: E-LAN Service.........................................................................................B-144
B.9.1.6 Parameter Description: QinQ Link_Creation................................................................................B-156
B.9.2 Parameters for Ethernet Protocols....................................................................................................B-157
B.9.2.1 Parameter Description: ERPS Management_Creation..................................................................B-158
B.9.2.2 Parameter Description: ERPS Management..................................................................................B-160
B.9.2.3 Parameter Description: MSTP Configuration_Port Group Creation.............................................B-166
B.9.2.4 Parameter Description: MSTP Configuration_Port Group Configuration....................................B-168
B.9.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters...............................................B-168
B.9.2.6 Parameter Description: MSTP Configuration_CIST Parameters..................................................B-174
B.9.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST.................B-176
B.9.2.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration.........................B-184
B.9.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted.....B-188
B.9.2.10 Parameter Description: IGMP Snooping Configuration_Route Management............................B-189
B.9.2.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation................B-190
B.9.2.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management......B-191
B.9.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation
....................................................................................................................................................................B-192
B.9.2.14 Parameter Description: IGMP Snooping Configuration_Data Statistics.....................................B-193
B.9.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation......................B-194
B.9.2.16 Parameter Description: Ethernet Link Aggregation_Link Aggregation......................................B-200
B.9.2.17 Parameter Description: LPT Management_Creation...................................................................B-201
B.9.2.18 Parameter Description: Port Mirroring_Creation........................................................................B-202
B.9.3 Parameters for the Ethernet OAM....................................................................................................B-203
B.9.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation....B-204
B.9.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation
....................................................................................................................................................................B-205
B.9.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation..............................B-206
B.9.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation................B-207
B.9.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation...............................B-208
B.9.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling................................B-209
B.9.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling.................................B-210
B.9.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter................................B-212
B.9.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring.........B-215
B.9.4 QoS Parameters.................................................................................................................................B-216
B.9.4.1 Parameter Description: Diffserv Domain Management.................................................................B-217
xxii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

B.9.4.2 Parameter Description: DiffServ Domain Management_Create...................................................B-222

B.9.4.3 Parameter Description: DiffServ Domain Applied Port_Modification.........................................B-227
B.9.4.4 Parameter Description: Policy Management.................................................................................B-229
B.9.4.5 Parameter Description: Port Policy................................................................................................B-234
B.9.4.6 Parameter Description: Port Policy_Traffic Classification Configuration....................................B-240
B.9.4.7 Parameter Description: Port Shaping Management_Creation.......................................................B-251
B.9.5 Parameters for the Ports on Ethernet Boards....................................................................................B-253
B.9.5.1 Parameter Description: Ethernet Interface_Basic Attributes......................................................... B-253
B.9.5.2 Parameter Description: Ethernet Interface_Flow Control.............................................................B-256
B.9.5.3 Parameter Description: Ethernet Interface_Layer 2 Attributes......................................................B-257
B.9.5.4 Parameter Description: Ethernet Interface_Advanced Attributes..................................................B-261
B.10 Parameters for Ethernet Services and Ethernet Features on the EoPDH Plane....................................... B-263
B.10.1 Parameters for Ethernet Services....................................................................................................B-264
B.10.1.1 Parameter Description: Ethernet Line Service_Creation............................................................. B-264
B.10.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services
....................................................................................................................................................................B-268
B.10.1.3 Parameter Description: Ethernet Line Service.............................................................................B-272
B.10.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE
802.1d/802.1q Bridge.................................................................................................................................B-274
B.10.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN
Service........................................................................................................................................................B-277
B.10.1.6 Parameter Description: Ethernet LAN Service............................................................................B-282
B.10.1.7 Parameter Description: VLAN Filtering Table_Creation............................................................B-288
B.10.1.8 Parameter Description: Aging Time of MAC Address Table Entries.........................................B-290
B.10.2 Parameters for Ethernet Protocols.................................................................................................B-290
B.10.2.1 Parameter Description: Spanning Tree_Protocol Enabling.........................................................B-291
B.10.2.2 Parameter Description: Spanning Tree_Bridge Parameters.........................................................B-292
B.10.2.3 Parameter Description: Spanning Tree_Port Parameters.............................................................B-294
B.10.2.4 Parameter Description: Spanning Tree_Bridge Running Information........................................B-295
B.10.2.5 Parameter Description: Spanning Tree_Port Running Information.............................................B-296
B.10.2.6 Parameter Description: Spanning Tree_Point-to-Point Attribute................................................B-297
B.10.2.7 Parameter Description: IGMP Snooping Protocol_Enabling......................................................B-298
B.10.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries
....................................................................................................................................................................B-299
B.10.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries......B-300
B.10.2.10 Parameter Description: Ethernet Link Aggregation_Creation of LAGs....................................B-301
B.10.2.11 Parameter Description: Ethernet Link Aggregation_Link Aggregation.................................... B-303
B.10.2.12 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT................B-304
B.10.2.13 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT.......B-305
B.10.2.14 Parameter Description: Port Mirroring_Creation......................................................................B-306
B.10.3 Parameters for the Ethernet OAM..................................................................................................B-307
B.10.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs..............................................B-308
B.10.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs..............................................B-309
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxiii

B.10.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs..............................................B-310

B.10.3.4 Parameter Description: Ethernet Service OAM_Enabling LB....................................................B-312
B.10.3.5 Parameter Description: Ethernet Service OAM_Enabling LT....................................................B-313
B.10.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter....................................................B-314
B.10.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring.............................B-315
B.10.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter......................................B-316
B.10.4 QoS Parameters...............................................................................................................................B-317
B.10.4.1 Parameter Description: QoS Management_Creation of Flows....................................................B-318
B.10.4.2 Parameter Description: QoS Management_Creation of CAR.....................................................B-320
B.10.4.3 Parameter Description: QoS Management_Creation of CoS.......................................................B-322
B.10.4.4 Parameter Description: QoS Management_Creation of CAR/CoS.............................................B-324
B.10.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues.................B-325
B.10.5 Parameters for the Ports on Ethernet Boards..................................................................................B-326
B.10.5.1 Parameter Description: Ethernet Port_External Port...................................................................B-326
B.10.5.2 Parameter Description: Ethernet Port_Internal Port....................................................................B-332
B.10.5.3 Parameter Description: Type Field of QinQ Frames...................................................................B-337
B.11 Parameters for the Orderwire and Auxiliary Interfaces...........................................................................B-338
B.11.1 Parameter Description: Orderwire_General....................................................................................B-338
B.11.2 Parameter Description: Orderwire_Advanced................................................................................B-340
B.11.3 Parameter Description: Orderwire_F1 Data Port............................................................................B-341
B.11.4 Parameter Description: Orderwire_Broadcast Data Port................................................................B-342
B.11.5 Parameter Description: Environment Monitoring Interface...........................................................B-343
B.12 Parameters for Board Interfaces...............................................................................................................B-346
B.12.1 Parameter Description: IF Interface_IF Attribute...........................................................................B-347
B.12.2 Parameter Description: IF Interface_ATPC Attribute....................................................................B-349
B.12.3 Parameter Description: Hybrid/AM Configuration........................................................................B-351
B.12.4 Parameter Description: Hybrid_AM Configuration_Advanced Attributes....................................B-354
B.12.5 Parameter Description: ATPC Adjustment Records.......................................................................B-355
B.12.6 Parameter Description: PRBS Test.................................................................................................B-355
B.12.7 Parameter Description: ODU Interface_Radio Frequency Attribute..............................................B-356
B.12.8 Parameter Description: ODU Interface_Power Attributes..............................................................B-358
B.12.9 Parameter Description: ODU Interface_Equipment Information...................................................B-362
B.12.10 Parameter Description: ODU Interface_Advanced Attributes......................................................B-364
B.12.11 Parameter Description: SDH Interfaces........................................................................................B-365
B.12.12 Parameter Description: Automatic Laser Shutdown.....................................................................B-367
B.12.13 Parameter Description: PDH Interfaces........................................................................................B-367
B.12.14 Parameter Description: Microwave Interface_Basic Attributes...................................................B-370
B.12.15 Parameter Description: Microwave Interface_Layer 2 Attributes................................................B-371
B.12.16 Parameter Description: Microwave Interface_Advanced Attributes............................................B-373
B.13 Parameters for Overhead..........................................................................................................................B-375
B.13.1 Parameter Description: Regenerator Section Overhead..................................................................B-375
B.13.2 Parameter Description: VC-4 POHs...............................................................................................B-376
xxiv Huawei Proprietary and Confidential Issue 01 (2010-09-25)

B.13.3 Parameter Description: VC-12 POHs.............................................................................................B-378
C Glossary......................................................................................................................................C-1
C.1 0-9..................................................................................................................................................................C-2
C.2 A-E.................................................................................................................................................................C-2
C.3 F-J..................................................................................................................................................................C-7
C.4 K-O..............................................................................................................................................................C-10
C.5 P-T................................................................................................................................................................C-12
C.6 U-Z...............................................................................................................................................................C-16
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxv

Configuration Guide (U2000) Figures
Figures
Figure 2-1 HWECC solution................................................................................................................................2-3

Figure 2-2 Inband DCN solution..........................................................................................................................2-4
Figure 2-3 Networking diagram (chain network)...............................................................................................2-12
Figure 2-4 Board configuration of NEs on a TDM chain radio network...........................................................2-13
Figure 2-5 Board configuration of NEs on a Hybrid chain radio network.........................................................2-13
Figure 2-6 Allocated IDs and IP addresses (chain network)..............................................................................2-14
Figure 2-7 Networking diagram (ring network).................................................................................................2-18
Figure 2-8 Board configuration of NEs on the TDM radio ring network..........................................................2-19
Figure 2-9 Board configuration of NEs on the Hybrid radio ring network........................................................2-20
Figure 2-10 Allocated IDs and IP addresses (ring network)..............................................................................2-21
Figure 3-1 AM......................................................................................................................................................3-3
Figure 3-2 Single-polarized transmission.............................................................................................................3-4
Figure 3-3 CCDP transmission.............................................................................................................................3-4
Figure 3-4 Configuration flow chart (radio links)................................................................................................3-7
Figure 3-5 Networking diagram (TDM radio chain network)............................................................................3-15
Figure 3-6 Networking diagram (TDM radio ring network)..............................................................................3-27
Figure 3-7 Networking diagram (Hybrid radio chain network).........................................................................3-38
Figure 3-8 Networking diagram (Hybrid radio ring network)...........................................................................3-53
Figure 4-1 1+1 linear MSP...................................................................................................................................4-3
Figure 4-2 1:N linear MSP...................................................................................................................................4-4
Figure 4-3 SNCP..................................................................................................................................................4-5
Figure 4-4 Numbering VC-12 timeslots by order ...............................................................................................4-6
Figure 4-5 Numbering VC-12 timeslots in the interleaved scheme ....................................................................4-7
Figure 4-6 Timeslot allocation diagram...............................................................................................................4-8
Figure 4-7 Configuration flow chart (TDM services)........................................................................................4-11
Figure 4-8 Networking diagram (TDM services on a TDM radio chain network)............................................4-14
Figure 4-9 Timeslot allocation diagram (TDM services on the TDM radio chain network).............................4-16
Figure 4-10 Networking diagram (TDM services on a TDM radio ring network) ...........................................4-21
Figure 4-11 Timeslot allocation diagram (TDM service on the TDM radio ring network)...............................4-23
Figure 4-12 Networking diagram (TDM services on a Hybrid radio chain network) .......................................4-29
Figure 4-13 Timeslot allocation diagram (Hybrid services on the Hybrid chain radio network)......................4-32
Figure 4-14 Networking diagram (TDM services on a Hybrid radio ring network) .........................................4-38
Figure 4-15 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)...........................4-40
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxvii

Figures Configuration Guide (U2000)
Figure 5-1 Typical application of the service model............................................................................................5-7

Figure 5-2 Typical application of service model 1...............................................................................................5-9
Figure 5-4 Typical application of service model 1.............................................................................................5-11
Figure 5-8 Model of E-LAN services based on the IEEE 802.1d bridge...........................................................5-14
Figure 5-9 Model of E-LAN services based on the IEEE 802.1q bridge...........................................................5-15
Figure 5-10 Model of E-LAN services based on the IEEE 802.1ad bridge.......................................................5-17
Figure 5-11 Networking diagram of VLAN-based E-Line services..................................................................5-18
Figure 5-12 Networking diagram of IEEE 802.1d bridge-based E-LAN services.............................................5-19
Figure 5-13 Networking diagram of IEEE 802.1q bridge-based E-LAN services.............................................5-20
Figure 5-14 Application of VLAN forwarding tables to E-Line services..........................................................5-25
Figure 5-15 Split horizon group.........................................................................................................................5-25
Figure 5-16 Implementation of ERPS................................................................................................................5-27
Figure 5-17 LAG................................................................................................................................................5-28
Figure 5-18 Prevention of network loops on the access side.............................................................................5-29
Figure 5-19 CAR processing..............................................................................................................................5-31
Figure 5-20 SP queue scheduling algorithm......................................................................................................5-32
Figure 5-21 WRR scheduling algorithm............................................................................................................5-33
Figure 5-22 SP+WRR scheduling algorithm......................................................................................................5-33
Figure 5-23 Configuration flow chart (point-to-point transparently transmitted E-Line services)....................5-35
Figure 5-24 Configuration flow chart (VLAN-based E-Line services).............................................................5-40
Figure 5-25 Configuration flow chart (QinQ-based E-Line services)................................................................5-46
Figure 5-26 Configuration flow chart (802.1d bridge-based E-LAN services).................................................5-52
Figure 5-27 Configuration flow chart (802.1q-bridge-based E-LAN services).................................................5-59
Figure 5-28 Configuration flow chart (802.1ad-bridge-based E-LAN services)...............................................5-66
Figure 5-29 Networking diagram (point-to-point transparently transmitted E-Line services)..........................5-73
Figure 5-30 Networking diagram (VLAN-based E-Line services)....................................................................5-84
Figure 5-31 Networking diagram (QinQ-based E-Line services)....................................................................5-116
Figure 5-32 Networking diagram (IEEE 802.1d bridge-based E-LAN services) ...........................................5-155
Figure 5-33 Networking diagram (IEEE 802.1q bridge-based E-LAN services)............................................5-176
Figure 5-34 Networking diagram (IEEE 802.1ad bridge-based E-LAN services) .........................................5-207
Figure 5-35 Networking diagram.....................................................................................................................5-233
Figure 6-1 Bridging ports on the EFP8 board......................................................................................................6-3
Figure 6-2 Hybrid radio........................................................................................................................................6-3
Figure 6-3 Typical application of the service model............................................................................................6-5
xxviii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Configuration Guide (U2000) Figures

Figure 6-10 Model of EPLAN services based on the 802.1d bridge..................................................................6-11
Figure 6-11 Model of EVPLAN services based on the 802.1q bridge...............................................................6-12
Figure 6-12 Model of EVPLAN services based on 802.1ad bridge...................................................................6-14
Figure 6-13 Configuration flow chart (point-to-point transparently transmitted EPL services)........................6-15
Figure 6-14 Configuration flow chart (VLAN-based EVPL services) .............................................................6-21
Figure 6-15 Configuration flow chart (QinQ-based EVPL services) ................................................................6-27
Figure 6-16 Configuration flow chart (802.1d bridge-based EPLAN services)................................................6-33
Figure 6-17 Configuration flow chart (IEEE 802.1q bridge-based EVPLAN services)....................................6-40
Figure 6-18 Configuration flow chart (IEEE 802.1ad bridge-based EVPLAN services)..................................6-47
Figure 6-19 Networking diagram (Ethernet services based on TDM radio)......................................................6-54
Figure 6-20 Board configuration (Ethernet services based on TDM radio) ......................................................6-54
Figure 6-21 Timeslot allocation diagram (Ethernet services based on TDM radio) .........................................6-62
Figure 6-22 Networking diagram (Ethernet services traversing a TDM network) ...........................................6-76
Figure 6-23 Board configuration (Ethernet services traversing a TDM network).............................................6-76
Figure 7-1 Clock source protection based on priorities........................................................................................7-3
Figure 7-2 SSM protection...................................................................................................................................7-4
Figure 7-3 Extended SSM protection...................................................................................................................7-6
Figure 7-4 Clock synchronization policy for a chain network.............................................................................7-7
Figure 7-5 Clock synchronization policy for a tree network................................................................................7-8
Figure 7-6 Clock synchronization policy for a ring network (on which only the SDH signal is transmitted)
...............................................................................................................................................................................7-9
Figure 7-7 Clock synchronization policy for a ring network (on which not only the SDH signal is transmitted)
.............................................................................................................................................................................7-10
Figure 7-8 Clock synchronization policy for a port aggregation network (aggregation only through the tributary
port).....................................................................................................................................................................7-11
Figure 7-9 Clock synchronization policy for transmission across TDM network.............................................7-12
Figure 7-10 Tributary retiming...........................................................................................................................7-13
Figure 7-11 Configuration flow chart (clocks)...................................................................................................7-14
Figure 7-12 Networking diagram (clocks on a TDM radio chain network).......................................................7-17
Figure 7-13 Clock source information (TDM radio chain network)..................................................................7-19
Figure 7-14 Networking diagram (clocks on a TDM radio ring network).........................................................7-20
Figure 7-15 Clock source information (TDM radio ring network)....................................................................7-22
Figure 7-16 Networking diagram (clocks on a Hybrid radio chain network)....................................................7-24
Figure 7-17 Networking diagram (clock for a Hybrid radio chain network).....................................................7-26
Figure 7-18 Networking diagram (clocks on a Hybrid radio ring network)......................................................7-28
Figure 7-19 Clock source information (Hybrid radio ring network)..................................................................7-29
Figure 7-20 Networking diagram (clocks across a third-party TDM network).................................................7-31
Figure 7-21 Board configuration (clocks across a third-party TDM network)..................................................7-31
Figure 7-22 Information about clock sources (Hybrid radio chain network) ....................................................7-32
Figure 8-1 Circuits for the input external alarms.................................................................................................8-4
Figure 8-2 Networking diagram (orderwire)........................................................................................................8-5
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxix

Figures Configuration Guide (U2000)
Figure 8-3 Networking diagram (for orderwire)..................................................................................................8-7

Figure 8-4 Networking diagram (synchronous data services)..............................................................................8-9
Figure 8-5 Networking diagram (asynchronous data services)..........................................................................8-13
Figure 8-6 Networking diagram (wayside E1 services).....................................................................................8-16
Figure 8-7 Networking diagram (external alarms).............................................................................................8-18
Figure A-1 Networking diagram for testing the Ethernet service.....................................................................A-93
Figure A-2 Configuration for testing the IF 1+1 switching............................................................................A-221
Figure A-3 Configuration for testing the N+1 protection...............................................................................A-224
Figure A-4 Configuration for testing the SNCP switching.............................................................................A-227
Figure A-5 Configuration for testing the ERPS..............................................................................................A-230
Figure A-6 Configuration for testing the Ethernet service..............................................................................A-233
xxx Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Configuration Guide (U2000) Tables
Tables
Table 1-1 Initial configuration..............................................................................................................................1-2

Table 1-2 Network adjustment.............................................................................................................................1-3
Table 2-1 Mapping relations between the physical boards and logical boards....................................................2-5
Table 2-2 Procedures for configuring the network topology...............................................................................2-7
Table 3-1 Procedures for configuring TDM radio links.......................................................................................3-8
Table 3-2 Procedure for configuring a Hybrid radio link (with the XPIC function enabled)............................3-10
Table 3-3 Procedure for configuring a Hybrid radio link (with the XPIC function disabled)...........................3-12
Table 3-4 Service capacity accessed by each BTS.............................................................................................3-14
Table 3-5 Connections of radio links (NE1)......................................................................................................3-15
Table 3-10 Connections of radio links (NE6)....................................................................................................3-16
Table 3-11 Basic information about radio links.................................................................................................3-17
Table 3-12 Power and ATPC information..........................................................................................................3-18
Table 3-13 Information of IF boards..................................................................................................................3-19
Table 3-14 Service capacity accessed by each BTS...........................................................................................3-27
Table 3-21 Information of IF boards..................................................................................................................3-30
Table 3-23 Common service priorities...............................................................................................................3-37
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxxi

Tables Configuration Guide (U2000)

Table 3-31 Hybrid/AM attribute information.....................................................................................................3-40
Table 3-33 Information about IF boards.............................................................................................................3-42
Table 3-35 Common service priorities...............................................................................................................3-52
Table 3-41 Hybrid/AM attribute information.....................................................................................................3-55
Table 3-43 Information about IF boards.............................................................................................................3-57
Table 4-1 Procedures for configuring TDM services.........................................................................................4-12
Table 4-2 Connections of TDM links (NE1)......................................................................................................4-14
Table 4-8 Linear MSP........................................................................................................................................4-17
Table 4-10 Connections of TDM links (NE2)....................................................................................................4-22
Table 4-13 SNCP................................................................................................................................................4-24
Table 4-21 Linear MSP......................................................................................................................................4-33
Table 4-27 SNCP................................................................................................................................................4-41
Table 5-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adopts the auto-negotiation
mode).....................................................................................................................................................................5-3
xxxii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Table 5-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adopts the auto-
negotiation mode)..................................................................................................................................................5-4
Table 5-3 Point-to-point transparently transmitted E-Line service model...........................................................5-7
Table 5-4 Models of VLAN-based E-Line services.............................................................................................5-8
Table 5-5 Models of QinQ-based E-Line Services............................................................................................5-10
Table 5-6 Model of E-LAN services based on the IEEE 802.1d bridge............................................................5-13
Table 5-7 Model of E-LAN services based on the IEEE 802.1q bridge............................................................5-14
Table 5-8 Models of E-LAN services based on the IEEE 802.1ad bridge.........................................................5-16
Table 5-9 Comparison between the three networking modes............................................................................5-21
Table 5-10 Procedures for configuring Ethernet ports.......................................................................................5-35
Table 5-11 Procedures for configuring a LAG...................................................................................................5-37
Table 5-12 Procedures for configuring point-to-point transparently transmitted E-Line services.....................5-38
Table 5-13 Procedures for configuring QoS.......................................................................................................5-38
Table 5-14 Procedures for verifying Ethernet service configurations................................................................5-39
Table 5-17 Procedures for configuring VLAN-based E-Line services..............................................................5-44
Table 5-22 Procedures for configuring QinQ-based E-Line services................................................................5-50
Table 5-27 Procedures for configuring ERPS protection...................................................................................5-56
Table 5-28 Procedures for configuring 802.1d-bridge-based E-LAN services..................................................5-56
Table 5-34 Procedures for configuring 802.1q-bridge-based E-LAN services..................................................5-63
Table 5-40 Procedures for configuring 802.1ad-bridge-based E-LAN services................................................5-70
Table 5-43 Connections of Ethernet links (NE1)...............................................................................................5-73
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxxiii

Table 5-44 Ethernet port.....................................................................................................................................5-74

Table 5-45 Ethernet port.....................................................................................................................................5-75
Table 5-46 Point-to-point transparently transmitted E-line service...................................................................5-75
Table 5-47 Service class and PHB service class................................................................................................5-76
Table 5-48 Queue scheduling mode...................................................................................................................5-77
Table 5-55 Ethernet port (NE1)..........................................................................................................................5-87
Table 5-61 IF_ETH port (NE1)..........................................................................................................................5-89
Table 5-67 LAG information..............................................................................................................................5-91
Table 5-68 VLAN-based E-Line service (NE1).................................................................................................5-92
Table 5-76 CAR parameters...............................................................................................................................5-96
Table 5-77 Connections of Ethernet links (NE1).............................................................................................5-116
Table 5-83 Ethernet port (NE1)........................................................................................................................5-119
xxxiv Huawei Proprietary and Confidential Issue 01 (2010-09-25)


Table 5-89 IF_ETH port (NE1)........................................................................................................................5-121
Table 5-95 LAG information............................................................................................................................5-123
Table 5-96 QinQ-based E-Line service (NE1).................................................................................................5-123
Table 5-100 QinQ-based E-Line service (NE5)...............................................................................................5-126
Table 5-101 QinQ-based E-Line service (NE6)...............................................................................................5-127
Table 5-102 Service class and PHB service class............................................................................................5-127
Table 5-103 Queue scheduling mode...............................................................................................................5-128
Table 5-104 CAR parameters...........................................................................................................................5-129
Table 5-105 Shaping parameters......................................................................................................................5-129
Table 5-106 Connections of Ethernet links (NE1)...........................................................................................5-155
Table 5-110 Ethernet port (NE1)......................................................................................................................5-158
Table 5-114 IF_ETH port.................................................................................................................................5-160
Table 5-115 IF_ETH port.................................................................................................................................5-160
Table 5-116 IF_ETH port.................................................................................................................................5-160
Table 5-117 IF_ETH port.................................................................................................................................5-160
Table 5-118 LAG information..........................................................................................................................5-161
Table 5-119 ERPS instance..............................................................................................................................5-161
Table 5-120 802.1d-bridge-based E-LAN service............................................................................................5-162
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxxv


Table 5-129 Information about Ethernet ports (NE1)......................................................................................5-179
Table 5-135 Information about the IF_ETH ports (NE1).................................................................................5-182
Table 5-142 Information about IEEE 802.1q bridge-based E-LAN services...................................................5-184
Table 5-154 IF_ETH port.................................................................................................................................5-212
Table 5-155 IF_ETH port.................................................................................................................................5-212
Table 5-156 IF_ETH port.................................................................................................................................5-213
Table 5-157 IF_ETH port.................................................................................................................................5-213
Table 5-159 ERPS instance..............................................................................................................................5-214
Table 5-160 802.1ad-bridge-based E-LAN service..........................................................................................5-215
xxxvi Huawei Proprietary and Confidential Issue 01 (2010-09-25)


Table 5-183 Information about point-to-point transparently transmitted E-Line services (NE1)....................5-241
Table 5-184 Information about point-to-point transparently transmitted E-Line services (NE6)....................5-241
Table 5-185 Information about IEEE 802.1d bridge-based E-LAN services...................................................5-242
Table 5-186 Information about IEEE 802.1d bridge-based E-LAN services (NE3)........................................5-242
Table 5-192 Shaping parameters......................................................................................................................5-246
Table 6-1 Point-to-point transparently transmitted EPL service model...............................................................6-5
Table 6-2 Models of the EVPL service based on the VLAN...............................................................................6-6
Table 6-3 Main service model of QinQ-based EVPL services.............................................................................6-8
Table 6-4 Model of EPLAN services based on the 802.1d bridge.....................................................................6-11
Table 6-5 Models of EVPLAN services based on the 802.1q bridge.................................................................6-12
Table 6-6 Models of EVPLAN services based on 802.1ad bridge.....................................................................6-13
Table 6-7 Procedures for configuring Ethernet ports.........................................................................................6-16
Table 6-8 Procedure for configuring a LAG......................................................................................................6-18
Table 6-9 Procedure for configuring point-to-point transparently transmitted EPL services............................6-19
Table 6-10 Procedure for configuring the QoS..................................................................................................6-19
Table 6-11 Procedure for testing Ethernet services............................................................................................6-20
Table 6-12 Procedure for configuring Ethernet ports.........................................................................................6-22
Table 6-13 Procedure for configuring a LAG....................................................................................................6-24
Table 6-14 Procedure for configuring VLAN-based EVPL services ................................................................6-25
Table 6-19 Procedure for configuring QinQ-based EVPL services...................................................................6-31
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxxvii


Table 6-24 Procedure for configuring IEEE 802.1d bridge-based EPLAN services.........................................6-37
Table 6-29 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services......................................6-44
Table 6-34 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services.....................................6-51
Table 6-42 Information about Ethernet external ports (NE1)............................................................................6-57
Table 6-45 Information about VCTRUNKs (NE1)............................................................................................6-58
Table 6-48 Information about the LAG..............................................................................................................6-60
Table 6-49 Information about VLAN-based EVPL services (NE1)..................................................................6-60
Table 6-50 VLAN-based EVPL services (NE4)................................................................................................6-61
Table 6-51 VLAN-based EVPL services (NE5)................................................................................................6-61
Table 6-52 Cross-connections of Ethernet services (NE1).................................................................................6-63
Table 6-59 Information about Ethernet ports (NE1)..........................................................................................6-78
Table 6-60 Information about the IF_ETH port (NE1)......................................................................................6-79
Table 6-61 Information about Ethernet services (NE1).....................................................................................6-79
xxxviii Huawei Proprietary and Confidential Issue 01 (2010-09-25)


Table 6-68 Information about the LAG (NE1)...................................................................................................6-83
Table 6-69 Information about the LAG (NE7)...................................................................................................6-84
Table 6-74 Flow parameters (NE1)....................................................................................................................6-86
Table 6-75 Flow parameters (NE7)....................................................................................................................6-87
Table 6-76 CoS attributes of the EFP8 board (NE1 and NE7)...........................................................................6-87
Table 6-77 CoS parameters and corresponding BTS service types of the EFP8 board (NE1 and NE7)...........6-88
Table 7-1 Procedures for configuring clocks.....................................................................................................7-15
Table 7-2 Clock connections (NE1)...................................................................................................................7-17
Table 7-10 Clock connections (NE3).................................................................................................................7-21
Table 7-22 Clock link connections (NE1)..........................................................................................................7-32
Table 7-23 Clock link connections (NE7)..........................................................................................................7-32
Table 8-1 Orderwire phone connections (NE1)....................................................................................................8-5
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xxxix


Table 8-7 Information about orderwire ports.......................................................................................................8-7
Table 8-8 Connections of synchronous data services (NE1)..............................................................................8-10
Table 8-9 Connections of synchronous data services (NE2)..............................................................................8-10
Table 8-10 Connections of synchronous data services (NE3)............................................................................8-10
Table 8-13 Information about the synchronous data service..............................................................................8-11
Table 8-14 Connections of asynchronous data services (NE1)..........................................................................8-13
Table 8-19 Information about the asynchronous data service............................................................................8-14
Table 8-20 Information about wayside E1 services...........................................................................................8-16
Table 8-21 Information about input alarms........................................................................................................8-18
Table 8-22 Information about output alarms......................................................................................................8-19
Table 9-1 Common task collection (NE attributes)..............................................................................................9-2
Table 9-2 Common task collection (radio links)..................................................................................................9-3
Table 9-3 Common task collection (TDM services)............................................................................................9-7
Table 9-4 Common task collection (Packet-plane Ethernet services)..................................................................9-8
Table 9-5 Task Collection (EoPDH-plane Ethernet services)............................................................................9-11
Table B-1 Parameters on the main interface......................................................................................................B-99
Table B-2 Methods used by Ethernet interfaces to process data frames.........................................................B-260
Table B-3 Parameters on the main interface....................................................................................................B-265
Table B-4 Parameters for port attributes..........................................................................................................B-266
Table B-5 Parameters for bound paths.............................................................................................................B-267
Table B-6 Parameters on the main interface....................................................................................................B-268
Table B-7 Parameters of port attributes...........................................................................................................B-271
Table B-8 Parameters for bound paths.............................................................................................................B-271
Table B-9 Parameters on the main interface (Display QinQ Shared Service is not selected)......................B-272
Table B-10 Parameters on the main interface (Display QinQ Shared Service is selected)...........................B-272
Table B-11 Parameters for port attributes........................................................................................................B-273
Table B-12 Parameters for bound paths...........................................................................................................B-274
Table B-13 Parameters on the main interface..................................................................................................B-274
Table B-14 Parameters for mounting services.................................................................................................B-275
Table B-15 Parameters for mounting configuration........................................................................................B-276
Table B-18 Parameters of service mounting....................................................................................................B-279
xl Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Table B-19 Parameters of service mounting....................................................................................................B-280

Table B-22 Parameters for mounting services.................................................................................................B-283
Table B-23 Parameters for VLAN filtering table............................................................................................B-285
Table B-24 Parameters for VLAN unicast.......................................................................................................B-286
Table B-25 Parameters for disabling MAC addresses.....................................................................................B-286
Table B-27 Parameters for self-learned MAC addresses.................................................................................B-287
Table B-28 Parameters for VLAN MAC address table capacity.....................................................................B-288
Table B-29 Parameters for VB port MAC address table capacity...................................................................B-288
Table B-41 Parameters for advanced attributes...............................................................................................B-311
Table B-52 Parameters for the basic attributes................................................................................................B-326
Table B-53 Parameters for flow control..........................................................................................................B-328
Table B-54 Parameters for the tag attributes...................................................................................................B-329
Table B-55 Parameters for the network attributes...........................................................................................B-329
Table B-56 Parameters for the advanced attributes.........................................................................................B-330
Table B-57 Methods used by ports to process data frames.............................................................................B-331
Table B-58 Parameters for the tag attributes...................................................................................................B-332
Table B-59 Parameters for encapsulation or mapping.....................................................................................B-333
Table B-60 Parameters for the network attributes...........................................................................................B-333
Issue 01 (2010-09-25) Huawei Proprietary and Confidential xli

Table B-61 Parameters for the LCAS..............................................................................................................B-334

Table B-63 Methods used by ports to process data frames.............................................................................B-336
Table B-65 Data frame processing..................................................................................................................B-372
xlii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Configuration Guide (U2000) 1 Configuration Preparations
1 Configuration Preparations
About This Chapter
Before configuring the NE data, you must make the required preparations.
1.1 Preparing Documents and Tools

The relevant documents and tools must be available to ensure the proper configuration of data.
1.2 Checking Configuration Conditions
Before the configuration, check whether the configuration conditions meet the requirements.
1.3 Specifying the Configuration Procedure
You can select the proper configuration procedure according to the actual configuration
scenarios.
Issue 01 (2010-09-25) Huawei Proprietary and Confidential 1-1

1 Configuration Preparations Configuration Guide (U2000)
1.1 Preparing Documents and Tools

The relevant documents and tools must be available to ensure the proper configuration of data.
Documents
l Network planning documents, such as the XXX Network Planning
l OptiX RTN 950 Radio Transmission System Configuration Guide
Tools
l A computer where the U2000 server software is installed
l A computer where the U2000 client software is installed
NOTE
For information about the software and hardware required for the U2000 and the installation method, see the
documents that accompany the U2000.
1.2 Checking Configuration Conditions

Before the configuration, check whether the configuration conditions meet the requirements.
Ensure that the following requirements are met:
l All the NEs on the network must be powered on properly.

l The DCN communication between the gateway NE and the non-gateway NEs must be
normal.
l The network communication between the U2000 server and the gateway NE must be
normal.
l The U2000 client can log in to the U2000 server and has the "network operator" authority
or higher.
1.3 Specifying the Configuration Procedure

You can select the proper configuration procedure according to the actual configuration
scenarios.
Initial Configuration
Initial configuration of a radio network refers to configuring the network-wide service data by
using the U2000 for the first time after the NE commissioning is complete. Table 1-1 describes
the configuration procedure.
Table 1-1 Initial configuration
Step Operation Description
1 2 Configuring the Network Required.

Topology
1-2 Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Configuration Guide (U2000) 1 Configuration Preparations
2 3 Configuring Radio Links Required.
3 4 Configuring TDM Required when the TDM

Services services need to be
transmitted.
4 5 Configuring Packet- Required when the Ethernet

Based Ethernet Services services need to be
transmitted.
6 Configuring EoPDH-
Based Ethernet Services
5 7 Configuring the Clock Required.
6 8 Configuring Auxiliary Required when the orderwire

Ports and Functions information, wayside E1
service, or synchronous/
asynchronous data service
needs to be transmitted or
when the external alarm
input/output function needs
to be enabled.
Network Adjustment
Network adjustment involves adding and adjusting configuration data in the equipment
commissioning and operation phases. You can find the corresponding configuration operations
according to the actual network adjustment requirements in Table 1-2.
Table 1-2 Network adjustment

Operation Description
9.1 Common Task Collection (Network This common task collection lists
Topology) configuration operations associated with NE
attributes, including changing the ID and IP
address of an NE.
9.2 Common Task Collection (Radio This common task collection lists
Links) configuration operations associated with
radio links, including changing the working
mode of a TDM radio link and changing the
number of E1s on a Hybrid radio link.
9.3 Common Task Collection (TDM This common task collection lists
Services) configuration operations associated with
TDM services, including deleting TDM
services and upgrading a normal service to an
SNCP service.

1 Configuration Preparations Configuration Guide (U2000)
9.4 Common Task Collection (Packet- This common task collection lists
Plane Ethernet Services) configuration operations associated with
Ethernet services, including configuring or
9.5 Common Task Collection (EoPDH- modifying Ethernet interface parameters and
Plane Ethernet Services) deleting Ethernet services.

Configuration Guide (U2000) 2 Configuring the Network Topology
2 Configuring the Network Topology
About This Chapter
You can manage a transport network by using the U2000 only after configuring the network
topology on the network.
2.1 Basic Concepts

Before configuring the network topology, you need to be familiar with the basic concepts.
2.2 Configuration Procedure
This section describes the procedures for configuring the four topological objects, namely, NEs,
boards, fibers/cables, and subnets.
2.3 Configuration Example (Chain Network)
This section considers a chain radio network as an example to describe how to configure the
network topology according to the network planning information.
2.4 Configuration Example (Ring Network)
This section considers a radio ring network as an example to describe how to configure the

2 Configuring the Network Topology Configuration Guide (U2000)
2.1 Basic Concepts

Before configuring the network topology, you need to be familiar with the basic concepts.
2.1.1 DCN
To manage and maintain an NE, the U2000 needs to communicate with the NE through the data
communication network (DCN).
2.1.2 GNE and Non-GNE
The gateway NE (GNE) refers to the NE whose application layer communicates directly with
the application layer of the NMS. A non-GNE refers to an NE whose application layer
communicates with the application layer of the NMS by forwarding data through the application
layer of its GNE.
2.1.3 ID and IP Address of an NE
The ID and IP address are the unique identifiers of an NE on the DCN.
2.1.4 Physical Boards and Logical Boards
The NE software considers a physical board as one or more logical boards when managing the
physical board. The U2000 also considers a physical board as one or more logical boards when
managing the physical board.
2.1.5 Fiber/Cable Types
You can obtain the clear fiber/cable connection relations between NEs by using the fiber
management function of the U2000. You can manage the fibers and cables by using the
U2000, including SDH fibers, radio links, extended ECC cables, and back-to-back radio
connections.
2.1.6 Subnet
NEs in a same domain or with similar attributes can be allocated to a same subnet. In this way,
they can be displayed as a whole on the U2000, thus facilitating the NE management.
2.1.1 DCN
To manage and maintain an NE, the U2000 needs to communicate with the NE through the data
communication network (DCN).
On a DCN, the U2000 and all the NEs are considered as nodes on the DCN. The DCN between
the U2000 and all the NEs is considered as the external DCN, and the DCN between the NEs is
considered as the internal DCN. The OptiX RTN 950 supports several DCN solutions, including
HWECC, IP over DCC, and inband DCN. HWECC is the commonest DCN solution.
HWECC is the default DCN solution provided by the OptiX RTN 950. In the case of HWECC,
the network management (NM) message is encapsulated in the proprietary HWECC protocol
stack. Hence, the HWECC solution is easy to configure. As a proprietary protocol stack,
however, HWECC can be used only when there is one isolated OptiX RTN 950 NE or when the
OptiX RTN 950 NE networks with other OptiX equipment that supports HWECC.
Figure 2-1 shows how the NM message is transmitted when HWECC is used. The NM message
encapsulated in the HWECC protocol stack can be transmitted on the DCC channels over the
optical fiber or microwave, and can also be transmitted over the Ethernet between the Ethernet
NM ports or between the NE cascade ports. If there are no fiber connections or radio links
between two NEs, ensure that the Ethernet connection is set up between the corresponding
Ethernet NM ports or NE cascade ports on the NEs. Otherwise, the communication between the

two NEs fails. The Ethernet connection between the corresponding Ethernet NM ports or NE
cascade ports functions as the extended channel for transmitting the HWECC protocol stack and
is hence considered as the extended ECC. The extended ECC function is enabled by default.
Figure 2-1 HWECC solution

Message
HWECC
Message DCC
HWECC
ETH
Message
HWECC
DCC
Message
HWECC
DCC
NMS
Message Message
HWECC HWECC
DCC DCC
OptiX radio
OptiX optical transmission equipment
transmission equipment
Radio link Fiber Ethernet link
In addition, the inband DCN is enabled by default. In the inband DCN solution, the NM
management message occupies part of the Ethernet service bandwidth and is transmitted over
Hybrid radio link or through FE/GE ports. The inband DCN solution applies to the scenarios
where the OptiX RTN 950 networks OptiX packet switching equipment, as shown in Figure
2-2.

Figure 2-2 Inband DCN solution
OptiX Msg
IP stack
NMS
Hybrid MW
OptiX Msg
IP stack
ETH OptiX Msg
IP stack
Inband DCN OptiX Msg
IP stack
FE/GE
OptiX RTN 910/950 OptiX PTN equipment Ethernet link
In the inband DCN solution, the NM management message occupies part of the Ethernet service
bandwidth. Hence, the DCN function of the ports that are not connected to the OptiX packet
switching equipment must be disabled.
2.1.2 GNE and Non-GNE

The gateway NE (GNE) refers to the NE whose application layer communicates directly with
the application layer of the NMS. A non-GNE refers to an NE whose application layer
communicates with the application layer of the NMS by forwarding data through the application
layer of its GNE.
GNE
Generally, the GNE is connected to the NMS through a LAN/WAN. The application layer of
the NMS can directly communicate with the application layer of the GNE. One set of NMS
needs to be connected to one or more GNEs.
Disable the extended ECC function of the GNEs, to prevent oversized DCN that is caused due
to the ECC communication between the GNEs.
Non-GNE
A non-GNE communicates with the GNE through the DCN channels between NEs. It is
recommended that fewer than 50 GNEs are affiliated to a GNE.
2.1.3 ID and IP Address of an NE

The ID and IP address are the unique identifiers of an NE on the DCN.

ID of an NE
At the application layer of each DCN solution, the OptiX NE uses the NE ID as the address of
the NE. Hence, the ID of each NE on the DCN must be unique and complies with the uniform
DCN planning.
The NE ID has 24 bits. The highest eight bits represent the subnet ID (or the extended ID) and
the lowest 16 bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnet
ID of the NE is 9 and the basic ID is 1.
IP Address of an NE
An NE uses the IP address as its unique identifier during the TCP/IP communication.
In the HWECC solution, the IP addresses of the NEs on the DCN are used in the following
scenarios:
l The GNE communicates with the U2000 over TCP/IP based on the IP address. The IP
address must comply with the uniform planning of the external DCN.
l Different NEs communicate with each other over extended ECC channels based on the IP
addresses. The IP addresses of the NEs must be within the same network segment. By
default, the IP address of an NE is within the 129.9.0.0 network segment.
In the DCN solutions (for example, inband DCN) where the NM message is transmitted over
TCP/IP, the IP address of an NE is used as the NE address at the network layer. Hence, the IP
of each NE on the DCN must be unique and complies with the uniform planning of the DCN.
By default, that is, if the IP address of an NE is not changed manually, the IP address and ID of
the NE interlock each other. That is, when the NE ID is changed, the IP address is automatically
modified to 0x81000000 + ID. For example, when the NE ID is changed to 0x090001, the IP
address is automatically changed to 129.9.0.1. After the IP address is changed manually, the
interlocking relation between the ID and IP address fails.
2.1.4 Physical Boards and Logical Boards

The NE software considers a physical board as one or more logical boards when managing the
physical board. The U2000 also considers a physical board as one or more logical boards when
managing the physical board.
Table 2-1 provides the mapping relations between the physical boards and logical boards.
Table 2-1 Mapping relations between the physical boards and logical boards
Physical Board Logical Board
CST CST in the same slot
CSH CSH in the same slot
AUX AUX in the same slot
IF1 IF1 in the same slot
IFU2 IFU2 in the same slot
IFX2 IFX2 in the same slot

Physical Board Logical Board
SL1D SL1D in the same slot
EM6T EM6T in the same slot
EM6F EM6F in the same slot
EFP8 EFP8 in the same slot
SP3S SP3S in the same slot
SP3D SP3D in the same slot
PIU PIU in the same slot
FAN FAN in the same slot
ODU ODU in the slot whose number is 20 plus the

slot number of the IF board that is connected
to the ODU
2.1.5 Fiber/Cable Types

You can obtain the clear fiber/cable connection relations between NEs by using the fiber
management function of the U2000. You can manage the fibers and cables by using the
U2000, including SDH fibers, radio links, extended ECC cables, and back-to-back radio
connections.
l SDH fibers
SDH fibers refer to the fiber connections between different sets of equipment. That is, SDH
fibers indicate the connection relations between different SDH optical ports.
l Radio links
Radio links refer to the radio connections between different sets of radio equipment. That
is, the radio links indicate the connection relations between different IF ports.
l Extended ECC cables
Extended ECC cables refer to the extended ECC channels between the NEs. That is, the
extended ECC cables indicate the connection relations between the NEs.
l Back-to-back radio connections
Back-to-back radio connections refer to the NE cascading relations. That is, the back-to-
back radio connections indicate the connection relations between the NEs.
NOTE
Fibers and cables are topological objects on the U2000. Hence, operations on the fibers or cables do not affect
the normal running of the NEs.
2.1.6 Subnet
NEs in a same domain or with similar attributes can be allocated to a same subnet. In this way,
they can be displayed as a whole on the U2000, thus facilitating the NE management.

The subnets are topological objects on the U2000. Hence, operations on the subnets do not affect
the normal running of the NEs. In the case of a large number of topological objects, subnets that
contain multiple NEs simplify the topology view on the U2000.

This section describes the procedures for configuring the four topological objects, namely, NEs,
boards, fibers/cables, and subnets.
Table 2-2 Procedures for configuring the network topology

1 Creating A.1.2 It is recommended that you perform this operation

NEs on the Creating to add one or more NEs to a large existing network
U2000 NEs by on the U2000.
Using the
Manual
Method
A.1.1 It is recommended that you perform this operation

Creating to create NEs on the U2000 in other cases. The
NEs by following parameters need to be set:
Using the l Search Domain: When the IP address of the
Search GNE is known, it is recommended that you set
Method the IP address range of the GNE as the search
domain. In the case of initial configuration, it is
recommended that you set the 129.9.255.255
network segment as the search domain.
l Search for NE: It is recommended that you
select Search for NE, Create device after
search NE User, and Upload after create. By
default, NE User is root and Password is
password.
2 A.2.1 Uploading the If you select Upload after create during A.1.1
NE Data Creating NEs by Using the Search Method, skip
this operation.
3 A.1.4 Changing the NE Required. Set the parameters as follows:

ID l Change New ID to be the NE ID specified during
the planning of the DCN.
l If the extended NE ID is required, change New
Extended ID.

4 A.6.1 Setting NE Required. Set the parameters as follows:

Communication l In the case of the GNE, set IP Address and
Parameters Subnet Mask according to the planning of the
external DCN.
l In the case of the GNE, set Gateway IP
Addr... if the external DCN requires.
l In the case of non-GNEs, it is recommended that
you set IP Address to 0x81000000 + NE ID.
That is, if the NE ID is 0x090001, set IP
Address to 129.9.0.1. Set Subnet Mask to
255.255.0.0.
NOTE
If the IP address of an NE is not changed manually, the IP
address changes according to the NE ID and is always
0x81000000 + NE ID. In this case, the IP address of a non-
GNE does not need to be changed manually.
5 A.1.5 Changing the NE Optional.

Name
6 A.1.3 Configuring the Required.

Logical Board
7 A.6.3 Configuring the Required in the case of the GNE. Set the parameters
Extended ECC as follows:
l Set ECC Extended Mode to Specified Mode.
l Adopt the default values for the other parameters.
NOTE
This operation is performed to disable the automatic
extended ECC function of the GNE.
8 A.6.10 Configuring the In the case of an NE interconnecting with packet

VLAN ID and switching equipment, perform this operation to
Bandwidth Used by an change the VLAN ID and bandwidth of the inband
Inband DCN DCN that are planned for the packet switching
equipment to the default values. The default VLAN
ID is 4094 and the default bandwidth is 512 kbit/s.
9 A.6.11 Configuring the Required in the case of the Hybrid radio network. Set
Enable Status of the the parameters as follows:
Inband DCN Function l In the case of the Ethernet ports and microwave
on Ports ports that interconnect with the packet switching
equipment, set Enabled Status to Enabled.
l In the case of the other ports, set Enabled
Status to Disabled.
10 A.3 Configuring the The 15-minute and 24-hour NE performance

Performance monitoring functions are enabled by default and thus
Monitoring Status of do not need to be set manually.
NEs

11 Creating A.4.1 It is recommended that you perform this operation

radio links Creating to create radio links or SDH fibers on the U2000
or SDH an when the physical radio links or SDH fibers exist.
fibers Optical
Transmis
sion Line
or Radio
Link by
Using the
Search
Method
A.4.2 Perform this operation to create the radio links on the

Creating U2000 that do not exist currently.
a Radio
Link by
Using the
Manual
Method
A.4.3 Perform this operation to create the SDH fibers on

Creating the U2000 that do not exist currently.
an SDH
Optical
Transmis
sion Link
by Using
the
Manual
Method

12 Synchroni A.1.6 Required.

zing the Synchron l To synchronize the NEs with the NM server, set
NE time izing the the relevant parameters as follows:
NE Time
– Set Synchronous Mode to NM.
– Right-click and choose the operation from the
shortcut menu to ensure that the NE are
synchronized with the NM time immediately.
– Set the synchronization parameters according
to the requirements. It is recommended that
the parameters adopt the default values.
l To synchronize the NEs with the NTP server, set
the relevant parameters as follows:
– Set Synchronous Mode to Standard NTP.
– Set Standard NTP Authentication
according to the requirements for the NTP
server.
– It is recommended that you set the upper level
NTP server that the NEs trace as follows:
– In the case of the GNE, set the external
NTP server to the upper level NTP server.
Set Standard NTP Server Identifier to
IP and set Standard NTP Server to the
IP address of the external NTP server.
– In the case of a non-GNE, set the GNE to
the upper level NTP server. If the non-
GNE needs to communicate with the GNE
through the HWECC protocol, set
Standard NTP Server Identifier to NE
ID and set Standard NTP Server to the
NE ID of the GNE. If the non-GNE needs
to communicate with the GNE through the
IP protocol, set Standard NTP Server
Identifier to IP and set Standard NTP
Server to the IP address of the GNE.
– Set Standard NTP Server Key according
to the requirements for the NTP server.
A.1.7 Required if the DST scheme is used at the local area.

Localizin Set the parameters according to the planning of the
g the NE DST at the local area.
Time
A.1.8 Required if the standard NTP authentication is used

Configuri to synchronize the NEs with the NTP server.
ng Set the parameters according to the identification
Standard authentication of the NTP.
NTP Keys

13 A.4.4 Creating an Optional when NEs are connected through extended

Extended ECC ECC channels.
14 A.4.5 Creating a Back- Optional when there are cascading NEs on the
to-Back Radio network.
Connection
15 Configuri A.5.1 Optional.

ng the Creating
subnet a Subnet
A.5.2 Optional.
Copying
Topology
Objects
A.5.3 Optional.
Moving
Topology
Objects
NOTE
l If the NE ID and NE name are changed in the NE commissioning process and if the NE communication
parameters, logical boards, VLAN ID and bandwidth of the inband DCN are set during the NE
commissioning, the configuration data is automatically synchronized onto the U2000 in the NE data
uploading process. Hence, you need not perform the corresponding operations in the initial configuration
process.
l The preceding configuration procedure is applicable to the scenarios wherein HWECC is used as the DCN
solution. When a DCN solution other than HWECC is used, the DCN-related operations described in the
preceding configuration procedure may be inapplicable.
2.3 Configuration Example (Chain Network)

This section considers a chain radio network as an example to describe how to configure the
2.3.1 Networking Diagram

This section describes the networking information about the NEs.
2.3.2 Board Configuration
Before performing the networking planning, you need to be familiar with the board configuration
of each NE.
2.3.3 Service Planning
The service planning information contains the information about all the parameters required for
configuring the NE data.
2.3.4 Configuration Process
This section describes the procedures for the data configuration.


Figure 2-3 shows a backhaul radio subnet for a mobile base station. On this network, if no fiber
connections are set up between NE2 and NE3, NE2 and NE3 are connected through an Ethernet
cable. In this case, the extended ECC communication is implemented through the Ethernet NM
ports or the NE cascading ports.
Figure 2-3 Networking diagram (chain network)

NMS
BTS2
NE4
BTS3
NE3 NE2 NE1 BSC
BTS1
NE6 NE5
BTS5 BTS4

of each NE.
NOTE
The board configuration information provided in this configuration example also applies to the configuration
examples of radio links, TDM services, and Ethernet services.
Board Configuration of NEs on a TDM Chain Radio Network

Figure 2-4 shows the board configuration of each NE on a TDM chain radio network.

Figure 2-4 Board configuration of NEs on a TDM chain radio network
NE3 NE2 NE1

NE4 CST CST CST
CST IF1 IF1 IF1 IF1
E1 NE6 NE6 NE6
IF1
IF1 BTS2 IF1 IF1 IF1
NE6 SPS SL1D
IF1 SL1D SL1D
S
SP3S
STM-1
E1 E1
BTS3 STM-1
BTS1
BSC
CST CST
IF1
NE6
IF1 NE6
IF1 IF1
SP3S SP3S
NE6 NE5 E1
E1
BTS4
BTS5
Board Configuration of NEs on a Hybrid Chain Radio Network

Figure 2-5 shows the board configuration of each NE on a Hybrid chain radio network.
Figure 2-5 Board configuration of NEs on a Hybrid chain radio network
NE cascade NE1
FE NE3 NE2
NE4 CSH CSH CSH
CSH IFU2 IFU2 IFU2 IFU2
IFU2
E1 NE6 IFU2 NE6 NE6
IFU2
BTS2 IFU2 IFU2
NE6
IFU2 EM6T SP3S EM6T SP3D EM6F SL1D
EM6T SP3S
GE
E1 E1
FE FE E1
BTS3 GE STM-1
BTS1 BSC
CSH CSH
IFU2
NE6
IFU2 NE6
IFU2 IFU2
EM6T SP3S EM6T SP3S
NE6 NE5 E1
FE
FE E1
BTS4
BTS5
NOTE
"NE cascade" indicates that an Ethernet cable is used to connect two NEs through the Ethernet NM ports or NE
cascading ports.


l The U2000 is connected to NE1 through the LAN. Hence, NE1 is the GNE and the other
NEs are non-GNEs, which access the U2000 through NE1.
l The chain network comprises only OptiX RTN 950. Hence, HWECC is preferred as the
DCN solution. In the HWECC solution, NE2 and NE3 communicate with each other
through the extended ECC that is enabled by default, because no fiber connections are set
up between NE2 and NE3. The other NEs communicate with each other through the DCC
channels over microwave.
l NE1 is the GNE. Hence, the extended ECC function of NE1 needs to be disabled.
l On this chain network, the OptiX RTN 950 does not interconnect with OptiX packet
switching equipment. Hence, the inband DCN function needs to be disabled for all the
Hybrid microwave ports and FE ports in the case of the Hybrid radio network.
l Figure 2-6 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
Figure 2-6 Allocated IDs and IP addresses (chain network)

NMS
9-4 10.0.0.100/16
129.9.0.4
0.0.0.0
NE4 9-3 9-2 9-1
129.9.0.3 129.9.0.2 10.0.0.1
0.0.0.0 0.0.0.0 0.0.0.0
NE3 NE2
9-5
9-6 129.9.0.5
129.9.0.6 0.0.0.0
0.0.0.0
NE5 Extended ID-Basic ID
NE6 IP address
Gatew ay
NOTE
l The subnet mask for the IP address of each NE is 255.255.0.0.

l The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence,
if the IP address of an NE (not NE1) is not changed manually, the NE automatically changes the IP
address to be the planned value after the NE ID is changed.
l In this example, the policy of synchronizing the NE with the NM server is used. The
automatic synchronization period is one day. The daylight saving time (DST) scheme is
not used at the local area.
l In this configuration example, no subnets need to be configured.

Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.

Procedure
Step 1 See A.1.1 Creating NEs by Using the Search Method and create the NEs.
The values for the related parameters are provided as follows.
Parameter Value
Search Domain Network Segment 129.9.255.255
Search User root
Search for NE Search for NE Selected
Create device after search Selected

NE User
Upload after create Selected
NE User root
Password password
NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and is not
known. Hence, you need to search for and create the NEs by using the 129.9.255.255 network segment as the
search domain. If the IP address of the GNE is known, it is recommended that you use the IP address of the
GNE as the search domain.
The icons of NE1 to NE6 should be displayed on the Main Topology and all the NE data should
be uploaded successfully.
Step 2 See A.1.4 Changing the NE ID and change the NE ID.
Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
New ID 1 2 3 4 5 6
New 9 (default 9 (default 9 (default 9 (default 9 (default 9 (default

Extended value) value) value) value) value) value)
ID
Step 3 See A.6.1 Setting NE Communication Parameters and set the NE communication parameters.
Parameter Value
NE1
IP Address 10.0.0.1

Parameter Value
NE1
Gateway IP Addr... 0.0.0.0 (default value)
Subnet Mask 255.255.0.0 (default value)
Extended ID 9
NOTE
The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence, you need
not change the values of the NE communication parameters manually.
Step 4 See A.1.3 Configuring the Logical Board and configure the logical boards.
Configure the logical boards according to the mapping relations between the physical boards
and logical boards.
Step 5 See A.6.3 Configuring the Extended ECC and configure the extended ECC.
Parameter Value
NE1
ECC Extended Mode Specified mode
Port (on the server side) 1601 (default value)
Opposite IP (on the client side) 0.0.0.0 (default value)
Port (on the client side) 1601 (default value)
NOTE
This operation is performed to disable the automatic extended ECC function of NE1.
Step 6 In the case of the Hybrid radio network, see A.6.11 Configuring the Enable Status of the
Inband DCN Function on Ports and disable the inband DCN function of the port.
Parameter Value
All the Ports on All the NEs
Enabled Status Disabled
Step 7 See A.1.6 Synchronizing the NE Time and synchronize the NE time.

Parameter Value
Synchronous Mode NM
Synchronization Period(days) 1
Step 8 See A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search
Method and create radio links or SDH fiber connections.
Normally, all the radio links or SDH fiber connections should be created successfully on the
Main Topology.
Step 9 When an Ethernet cable is used to connect NE2 and NE3 through the Ethernet NM ports or NE
cascading ports, see A.4.4 Creating an Extended ECC and create the extended ECC
connections.
Parameter Value
Source NE NE2
Sink NE NE3
Step 10 See A.4.5 Creating a Back-to-Back Radio Connection and create back-to-back radio
connections.
Parameter Value
Source NE NE2
Sink NE NE3
----End
2.4 Configuration Example (Ring Network)

This section considers a radio ring network as an example to describe how to configure the

of each NE.


Figure 2-7 shows a backhaul radio subnet for a mobile base station.
Figure 2-7 Networking diagram (ring network)
NMS
NE1
BSC
BTS1
NE2 NE4 BTS4
BTS2
NE3
BTS3

of each NE.
NOTE
The board configuration information provided in this configuration example also applies to the configuration
examples of radio links, TDM services, and Ethernet services.
Board Configuration of NEs on the TDM Radio Ring Network

Figure 2-8 shows the board configuration of each NE on the TDM radio ring network.

Figure 2-8 Board configuration of NEs on the TDM radio ring network
NE1
CST
IF1 IF1
BSC NE6
IF1 IF1
E1 SP3S
E1 NE2
CST NE4
BTS2 IF1
NE6 CST
IF1 IF1 IF1
SP3S NE6
IF1 IF1 E1
EM6T SP3S
E1
BTS3 FE
BTS4
NE3
CST
NE6
IF1 IF1
SP3S
E1
BTS3
Board Configuration of NEs on the Hybrid Radio Ring Network

Figure 2-9 shows the board configuration of each NE on the Hybrid radio ring network.

Figure 2-9 Board configuration of NEs on the Hybrid radio ring network
NE1
CSH
IFU2 IFU2
BSC NE6
IFU2 IFU2
GE EM6T SP3S
E1
FE
NE2
CSH NE4
BTS2 E1 IFU2
NE6 CSH
IFU2 IFU2 IFU2
FE EM6T SP3S NE6
IFU2 IFU2 E1
EM6T SP3S
E1
BTS3 FE
BTS4
NE3
CSH
NE6
IFU2 IFU2
EM6T SP3S
FE E1
BTS3

l The OptiX RTN 950 is connected to NE1 through the LAN. Hence, NE1 is the GNE and
the other NEs are non-GNEs, which access the OptiX RTN 950 through NE1.
l The ring network comprises only OptiX RTN 950. Hence, HWECC is preferred as the DCN
solution. In the HWECC solution, the NEs communicate with each other through the DCC
channels over microwave.
l NE1 is the GNE. Hence, the extended ECC function of NE1 should be disabled.
l On this ring network, the OptiX RTN 950 does not interconnect with OptiX packet
switching equipment. Hence, the inband DCN function needs to be disabled for all the
Hybrid microwave ports and FE ports in the case of the Hybrid radio network.
l Figure 2-10 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.

Figure 2-10 Allocated IDs and IP addresses (ring network)
10.0.0.100/16
9-1
10.0.0.1
0.0.0.0
NE1 9-4
9-2
129.9.0.2 129.9.0.4
0.0.0.0 0.0.0.0
NE2 9-3 NE4

129.9.0.3
0.0.0.0
Extended ID-Basic ID
NE3 IP address
Gatew ay
NOTE
l The subnet mask for the IP address of each NE is 255.255.0.0.

l The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence,
if the IP address of an NE (not NE1) is not changed manually, the NE automatically changes the IP
address to be the planned value after the NE ID is changed.
l In this example, the policy of synchronizing the NE with the NM server is used. The
automatic synchronization period is one day. The daylight saving time (DST) scheme is
not used at the local area.
l In this configuration example, no subnets need to be configured.

Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.1.1 Creating NEs by Using the Search Method and create the NEs.
Parameter Value
Search Domain Network Segment 129.9.255.255
Search User root
Search for NE Search for NE Selected
Create device after search Selected

NE User

Parameter Value
Upload after create Selected
NE User root
Password password
NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and the IP
addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using the
129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is recommended
that you use the IP address of the GNE as the search domain.
The icons of NE1 to NE4 should be displayed on the Main Topology and all the NE data should
be uploaded successfully.
Step 2 See A.1.4 Changing the NE ID and change the NE ID.
Parameter Value
NE1 NE2 NE3 NE4
New ID 1 2 3 4
New Extended 9 (default value) 9 (default value) 9 (default value) 9 (default value)
ID
Step 3 See A.6.1 Setting NE Communication Parameters and set the NE communication parameters.
Parameter Value
NE1
IP Address 10.0.0.1
Gateway IP Addr... 0.0.0.0 (default value)
Subnet Mask 255.255.0.0 (default value)
Extended ID 9
NOTE
The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence, you need
not change the values of the NE communication parameters manually.
Step 4 See A.1.3 Configuring the Logical Board and configure logical boards.

Configure the logical boards according to the mapping relations between the physical boards
and logical boards.
Step 5 See A.6.3 Configuring the Extended ECC and configure the extended ECC.
Parameter Value
NE1
ECC Extended Mode Specified mode
Port (on the server side) 1601 (default value)
Opposite IP (on the client side) 0.0.0.0 (default value)
Port (on the client side) 1601 (default value)
NOTE
This operation is performed to disable the automatic extended ECC function of NE1.
Step 6 In the case of the Hybrid radio network, see A.6.11 Configuring the Enable Status of the
Inband DCN Function on Ports and disable the inband DCN function of the port.
Parameter Value
Enabled Status Disabled
Step 7 See A.1.6 Synchronizing the NE Time and synchronize the NE time.
Parameter Value
Synchronous Mode NM
Synchronization Period(days) 1
Method and create radio links or SDH fiber connections.
Normally, all the radio links or SDH fiber connections should be created successfully on the
Main Topology.
----End

Configuration Guide (U2000) 3 Configuring Radio Links
3 Configuring Radio Links
About This Chapter
Before configuring services on a radio link, you need to configure the radio link.
3.1 Basic Concepts

Before configuring the radio link, you need to be familiar with the basic concepts.
The configuration procedures of different radio link configuration methods are different.
3.3 Configuration Example (Radio Links on the TDM Radio Chain Network)
This section considers radio links on a TDM radio chain network as examples to describe how
to configure radio links according to the planning information.
3.4 Configuration Example (Radio Links on the TDM Radio Ring Network)
This section considers TDM radio links on a TDM radio ring network as examples to describe
how to configure radio links according to the network planning information.
3.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network)
This section considers radio links on a Hybrid radio chain network as examples to describe how
to configure radio links according to the network planning information.
3.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)
This section considers radio links on a Hybrid radio ring network as examples to describe how

3 Configuring Radio Links Configuration Guide (U2000)
3.1 Basic Concepts

Before configuring the radio link, you need to be familiar with the basic concepts.
3.1.1 Adaptive Modulation

The AM function adjusts the modulation scheme according to the quality of the channel.
3.1.2 CCDP and XPIC
The CCDP and XPIC are two technologies that are developed based on microwave polarization
characteristics. The CCDP, wherein two signals are transmitted over two orthogonal polarization
waves, doubles the transmission capacity; the XPIC cancels the cross-polarization interference
between the two polarization waves.
3.1.3 RF Configuration Modes
The OptiX RTN 950 supports five RF configuration modes, namely, 1+0 non-protection
configuration, N+0 non-protection configuration, 1+1 protection configuration, N+1 protection
configuration, and cross-polarization interference cancellation (XPIC) configuration.
3.1.1 Adaptive Modulation

The AM function adjusts the modulation scheme according to the quality of the channel.
When the AM technology is adopted, in the case of the same channel spacing, the microwave
service bandwidth varies according to the modulation mode. The higher the modulation
efficiency, the higher the bandwidth of the transmitted services.
l When the channel quality is good (such as on days when weather conditions are favorable),
the equipment adopts a higher modulation mode to transmit more user services. In this
manner, the transmission efficiency and the spectrum utilization of the system are
improved.
l When the channel quality is degraded (such as on days when there is a storm or fog), the
equipment adopts a lower modulation mode to transmit only the services with a higher
priority within the available bandwidth and to discard the services with a lower priority. In
this manner, the anti-interference capability of the radio link is improved and the link
availability of the services with a higher priority is ensured.
The Hybrid radio equipment supports the AM technology, in which the priorities of E1 services
and Ethernet services can be set. With the AM technology adopted, service transmission is
controlled based on the service bandwidth and QoS policy corresponding to the current
modulation mode.
l Priorities of E1 services
The priorities of E1 services are assigned based on the number of E1 services that each
modulation mode can transmit. When a shift between modulation modes occurs, only the
E1 services whose number is specified in the new modulation mode can be transmitted and
the excess E1 services are discarded.
l Priorities of Ethernet services
The priorities of Ethernet services are assigned based on the mirroring through QoS
technology. To be specific, Ethernet services of various types are scheduled to queues with
different priorities through the QoS technology. Then, the services in different queues are
transmitted to the microwave port after computation of the SP or WRR algorithm. When
a shift between modulation modes occurs, certain queues may be congested due to

insufficient capacity at the air interface. In this case, certain services or all the services in
these queues are discarded.
Figure 3-1 shows the change in services brought by the AM technology. The orange part
indicates E1 services. The blue part indicates Ethernet services. The closer to the edge, the lower
the service priority. Under all channel conditions, the service capacity varies according to the
modulation mode. When the channel is in bad conditions, the service with a lower priority is
discarded.
Figure 3-1 AM
256QAM
128QAM
64QAM
32QAM
16QAM
QPSK
16QAM
Channel
Capability 32QAM
64QAM
128QAM
E1 Services
256QAM
Ethernet
Services
The AM technology adopted by the OptiX RTN 950 has the following features:
l The AM technology can use the QPSK, 16QAM, 32QAM, 64QAM, 128QAM, and
256QAM modulation mode.
l The lowest modulation mode (also called "reference mode") and the highest modulation
mode (also called "nominal mode") actually used by the AM can be configured.
l When the modulation modes of AM are switched, the transmit frequency, receive
frequency, and channel spacing do not change.
l When the modulation modes of AM are switched, the step-by-step switching mode is
adopted.
l AM switching is a hitless switch. When the AM scheme is downshifted, high-priority
services will not be affected due to the mode switching when the low-priority services are
discarded. The switching rate meets the requirement of the 100dB/s fast channel fading.

3.1.2 CCDP and XPIC

The CCDP and XPIC are two technologies that are developed based on microwave polarization
characteristics. The CCDP, wherein two signals are transmitted over two orthogonal polarization
waves, doubles the transmission capacity; the XPIC cancels the cross-polarization interference
between the two polarization waves.
Microwave transmission can be classified into single-polarized transmission and CCDP

transmission by polarization transmission mode.
l In the case of the single-polarized transmission, a signal is transmitted over the horizontally
polarized wave or the vertically polarized wave on the same channel, as shown in Figure
3-2.
l In the case of the CCDP transmission, two signals are transmitted over the horizontally
polarized wave and the vertically polarized wave on the same channel, as shown in Figure
3-3.
Therefore, the capacity in CCDP transmission mode is double the capacity in single-polarized
transmission mode.
Figure 3-2 Single-polarized transmission
Figure 3-3 CCDP transmission
The ideal situation of CCDP transmission is that no interference exists between the two
orthogonal signals that operate at the same frequency, and thus the receiver can easily recover
the two signals. In actual engineering conditions, however, regardless of the orthogonality of
the two signals, certain interference between the signals exists, due to cross-polarization
discrimination (XPD) of the antenna and channel degradation. To cancel the interference, the
XPIC technology is adopted. In the XPIC technology, the signals in the horizontal and vertical
directions are received and then processed. In this manner, the original signals are recovered.
The characteristics of the XPIC function supported by the OptiX RTN 950 are as follows:
l The XPD tolerance is increased, and the notch performance is improved.

l The XPIC function is realized completely through hardware.
3.1.3 RF Configuration Modes

The OptiX RTN 950 supports five RF configuration modes, namely, 1+0 non-protection
configuration, N+0 non-protection configuration, 1+1 protection configuration, N+1 protection
configuration, and cross-polarization interference cancellation (XPIC) configuration.
1+0 Non-Protection Configuration

The 1+0 non-protection configuration indicates that the radio link has one working channel and
no protection channel.
N+0 Non-Protection Configuration

The N+0 non-protection configuration indicates that the radio link has N working channels and
no protection channel.
The OptiX RTN 950 supports N+0 protection (1 < N ≤5).
1+1 Protection Configuration

The 1+1 protection configuration indicates that the radio link has one working channel and one
protection channel.
The 1+1 protection configuration is classified into 1+1 HSB, 1+1 FD, and 1+1 SD.
l In the 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration
for the IF boards and ODUs at both ends of each hop of radio link, thus realizing the
protection.
l In the 1+1 FD protection mode, the system uses two channels with a specific frequency
interval to transmit and receive the same service signal. The opposite end selects from the
two received signals. With the 1+1 FD protection, the impact of the fading on signal
transmission is reduced.
The 1+1 FD protection also supports the 1+1 HSB protection.
l In the 1+1 SD protection mode, the system uses two antennas with a space distance to
receive the same RF signal. The equipment selects from the two received signals. With the
1+1 SD protection, the impact of the fading on signal transmission is reduced.
The 1+1 SD protection also supports the 1+1 HSB protection.
N+1 Protection Configuration

The N+1 protection configuration indicates that the radio link has N working channels and one
protection channel.
The OptiX RTN 950 supports N+1 protection only in the case of STM-1 radio and Hybrid radio.
The N+1 protection is implemented through the N+1 MSP similar to l:N linear MSP.
The OptiX RTN 950 supports N+1 protection (1 ≤ N ≤ 4).

XPIC Configuration
The XPIC adopts both the horizontally polarized wave and the vertically polarized wave over
one channel to transmit two channels of signals. The radio link capacity in the case of XPIC
configuration is double the radio link capacity in the case of 1+0 configuration.
The OptiX RTN 950 supports only the XPIC configuration for the Hybrid radio link.

The configuration procedures of different radio link configuration methods are different.
Figure 3-4 provides the procedures for configuring radio links.

Figure 3-4 Configuration flow chart (radio links)

Procedure for configuring TDM Procedure for configuring Hybrid radio Procedure for configuring Hybrid radio
radio links links (with the XPIC function enabled) links (with the XPIC function disabled)
Start Start Start
Configure IF 1+1 protection Create an XPIC workgroup Configure IF 1+1 protection
Set the IF/ODU information of Set Hybrid/AM attributes of Set the IF/ODU information of
radio links the XPIC workgroup radio links
Configure the ATPC function Configure IF 1+1 protection Set IF attributes
Set ODU power attributes Set IF attributes Configure the ATPC function
Set AM advanced attributes

Configure N+1protection Set Hybrid/AMattributes
Create radio links by Set ODU power attributes

Set AM advanced attributes
searching for the radio links
End
Set ODU power attributes Configure N+1protection
Create radio links by

Create radio links by
End
Required End
Optional
The procedures in the configuration flow chart are described as follows.

Procedures for Configuring TDM Radio Links
Table 3-1 Procedures for configuring TDM radio links

1 A.8.1 Required when the radio links are configured with 1+1
Creating an protection.
IF 1+1 Set the parameters according to the network planning
Protection information.
Groupa
2 A.8.4 Required. Set the parameters as follows:

Configuring l Set Work Mode and Link ID according to the network
the IF/ODU planning information.
Information
of a Radio l Set TX Frequency(MHz), T/R Spacing(MHz), and TX
Power(dBm) according to the network planning
Linka
information.
l Set TX Status to unmute.
3 A.8.6 Required when the ATPC function needs to be used.

Configuring l If the ATPC function needs to be used, set ATPC Enable
the ATPC Status to Enabled.
Attributesa
l During site commissioning, set ATPC Enable Status to
Disabled.
l It is recommended that you set ATPC Upper Threshold
(dBm) to the central value plus 10 dB.
l It is recommended that you set ATPC Lower Threshold
(dBm) to the central value minus 10 dB.
l It is recommended that you set ATPC Automatic
Threshold Enable Status to Disabled.

4 A.15.3 Required.
Setting the l Set Power to Be Received(dBm) to the received signal
Power level specified in the network planning information. The
Attributes antenna non-alignment indication function is enabled only
of the ODUa after this parameter is set. When the antenna non-
alignment indication function is enabled, if the actual
receive power of the ODU is beyond the range of preset
receive power (-3 dBm to +3 dBm), the ODU indicator on
the IF board connected to the ODU blinks yellow (300 ms
on, 300 ms off), indicating that the antennas are not
aligned. After the antennas are aligned for consecutive 30
minutes, the NE automatically disables the antenna non-
alignment indication function.
l To set the maximum transmit power that is supported by
the ATPC adjustment, you need to set Maximum
Transmit Power(dBm) according to the actual
requirements.
l TX High Threshold(dBm), TX Low Threshold(dBm),
RX High Threshold(dBm), and RX Low Threshold
(dBm) affect only the performance events associated with
ATPC. Therefore, determine whether to set these
parameters according to the actual requirements.
5 A.8.10 Required when the radio links are configured with N+1
N+1 Set the attributes of the N+1 protection group to the same
Protection values for the equipment at both ends.
Group
Set the parameters according to the network planning
information.
6 A.4.1 In normal cases, the main topology displays the previously

Creating an created radio links.
Optical
Transmissio
n Line or
Radio Link
by Using the
Search
Method

NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,
however, you need to reset ATPC Enable Status.
l In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information
on the main radio link only. In the case of radio links configured with 1+1 FD, you need to configure the IF
and ODU information on the main radio link and the ODU information on the standby radio link.
l In the case of TDM radio links configured with N+1 protection, you need to configure the IF and ODU
information on each link. Work Mode must be configured as 7, STM-1, 28MHz, 128QAM.
Configuration Procedure of Hybrid Radio Links

The configuration process greatly depends on whether the XPIC is used for configuring Hybrid
radio.
Table 3-2 Procedure for configuring a Hybrid radio link (with the XPIC function enabled)
1 A.8.2 Required.
Creating an Set the parameters according to the network planning
XPIC information.
Protection
Group
2 A.8.3 Required.
Setting the Set the parameters according to the network planning
Hybrid/AM information. The parameters in both polarization directions
Attributes need to take the same values.
of the XPIC
Hybrid
Radio Link
3 A.8.1 Required when two XPIC workgroups need to form two 1+1
Creating an protection groups.
Group
NOTE
One XPIC workgroup cannot form a 1+1 protection group. The radio
link in the horizontal/vertical polarization direction of the XPIC
workgroup can form a 1+1 protection group with the radio link in the
horizontal/vertical polarization direction of the other XPIC
workgroup.
4 A.8.5 Required.
Setting IF l When the XPIC function is enabled on the IFX2 board, set
Attributes XPIC Enabled to Enabled (default value).
l In the case of interconnection with Packet radio
equipment, set Enable IEEE-1588 Timeslot to
Enabled.

5 A.8.7 Optional.
Setting the To enable the E1 priority function, set Enable E1 Priority to
Hybrid/AM Enabled. In addition, set Guarantee E1 Capacity and Full
Attributes E1 Capacity according to the network planning information.
6 A.8.8 Optional.
Setting To ensure that a specific number of E1s can be transmitted in
Advanced intermediate modulation schemes, adjust the E1 capacity in
AM each modulation scheme according to the network planning
Attributes information. Generally, it is recommended that you use the
default values.
7 A.15.3 Required.
of the ODU after this parameter is set. When the antenna non-

Optical
Transmissio
n Line or
Radio Link
by Using the
Search
Method

NOTE
l The preceding parameters need to set to the same values, separately for the radio links in the vertical and
horizontal polarization directions.
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC link
according to Table 3-3.
Table 3-3 Procedure for configuring a Hybrid radio link (with the XPIC function disabled)
1 A.8.1 Required when the radio links are configured with 1+1
Groupa
2 A.8.4 Required. Set the parameters as follows:

Configuring l Set AM Enable Status and IF Channel Bandwidth
the IF/ODU according to the network planning information.
Information
of a Radio l When the AM function is enabled on the radio links, set
Modulation Mode of the Guarantee AM Capacity and
Linka
Modulation Mode of the Full AM Capacity according
to the network planning information.
l When the AM function is disabled on the radio links, set
Manually Specified Modulation Mode according to the
network planning information.
l During site commissioning, set AM Enable Status to
Disabled. In addition, set Manually Specified
Modulation Mode to Modulation Mode of the
Guarantee AM Capacity that is planned.
l Set Full E1 Capacity and Link ID according to the
l Set TX Frequency(MHz), T/R Spacing(MHz), and TX
Power(dBm) according to the network planning
information.
l Set TX Status to unmute.
l To enable the E1 priority function, set Enable E1
Priority to Enabled. In addition, set Guarantee E1
Capacity and Full E1 Capacity according to the network
planning information.
3 A.8.5 Required.
Setting IF l When the XPIC function on the IFX2 board is not
Attributesa required, set XPIC Enabled to Disabled.
l In the case of interconnection with Packet radio
equipment, set Enable IEEE-1588 Timeslot to
Enabled.

4 A.8.6 Required when the ATPC function needs to be used.

Configuring l If the ATPC function needs to be used, set ATPC Enable
the ATPC Status to Enabled.
Attributesa
l During site commissioning, set ATPC Enable Status to
Disabled.
l It is recommended that you set ATPC Upper Threshold
(dBm) to the central value plus 10 dB.
l It is recommended that you set ATPC Lower Threshold
(dBm) to the central value minus 10 dB.
l It is recommended that you set ATPC Automatic
Threshold Enable Status to Disabled.
5 A.8.8 Optional.
Setting To ensure that a specific number of E1s can be transmitted in
Advanced intermediate modulation schemes, adjust the E1 capacity in
AM each modulation scheme according to the network planning
Attributesa information. Generally, it is recommended that you use the
default values.
6 A.15.3 Required.
of the ODUa after this parameter is set. When the antenna non-
l To set the maximum transmit power that is supported by
the ATPC adjustment function, you need to set Maximum
Transmit Power(dBm) according to the actual
requirements.
7 A.8.10 Required when the radio links are configured with N+1
N+1 Set the attributes of the N+1 protection group to the same
Protection values for the equipment at both ends.
Group
Set the parameters according to the network planning
information.


Optical
Transmissio
n Line or
Radio Link
by Using the
Search
Method
NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,
however, you need to reset AM Enable Status and ATPC Enable Status.
l To configure Hybrid radio links with N+1 protection, you need to configure the IF and ODU information
on each link.
3.3 Configuration Example (Radio Links on the TDM Radio

Chain Network)
This section considers radio links on a TDM radio chain network as examples to describe how
to configure radio links according to the planning information.


Based on 2.3 Configuration Example (Chain Network), configure the TDM radio links
according to the following network planning information (as shown in Figure 3-5):
l The service capacity accessed by each BTS is provided in Table 3-4.
Table 3-4 Service capacity accessed by each BTS

BTS BTS1 BTS2 BTS3 BTS4 BTS5
Number of 16 8 8 14 8
E1 services

l To improve transmission reliability of important services, the radio links between NE1 and
NE2, between NE3 and NE4, and between NE3 and NE5 are configured with 1+1 HSB
protection.
l The ATPC function is enabled to reduce inter-site interference.
Figure 3-5 Networking diagram (TDM radio chain network)

102
14952M 101
BTS2 14930M
14532M
16E1,14M,16QAM 14510M
STM-1,28M,128QAM
1+1 HSB
1+1 HSB
H-polarization
V-polarzation
BTS3
Tx high NE3 NE2 NE1
104 Tx low
14930M NE4 Tx high
Tx low
14510M Tx high Tx low
8E1,7M,16QAM
1+0 103 BSC
H-polarzation 14967M
14547M BTS1
Tx high 22E1,14M,32QAM
NE5 1+1 HSB Link ID
Tx low V-polarization Tx high station Tx Freq.
Tx low station Tx Freq.
NE6 Radio work mode
BTS4 RF configuarion
BTS5 Polarization
The connections of radio links shown in Figure 3-5 are described as follows.
Table 3-5 Connections of radio links (NE1)

Link Port Description
Between NE1 and NE2 3-IF1 (main IF board) Configure the ports as a 1+1
HSB protection group.
5-IF1 (standby IF board)





Between NE5 and NE6 3-IF1 Configure this port to receive

and transmit radio service
signals.


signals.


Basic Information About Radio Links

According to the spectrum allocation on the radio network and the required radio transmission
capacity, you can obtain the basic information about the radio links, as provided in Table
3-11.
Table 3-11 Basic information about radio links
Parameter Link 1 Link 2 Link 3 Link 4
Link ID 101 102 103 104
Tx high site NE1 NE4 NE5 NE5
Tx low site NE2 NE3 NE3 NE6
Tx frequency at 14930 14952 14967 14930

the Tx high site
(MHz)
Tx frequency at 14510 14532 14547 14510

the Tx low site
(MHz)
T/R spacing 420 420 420 420

(MHz)
Radio working STM-1, 16E1, 14MHz, 22E1, 14MHz, 8E1, 7MHz,

mode 28MHz, 16QAM 32QAM 16QAM
128QAM
RF 1+1 HSB 1+1 HSB 1+1 HSB 1+0

configuration
mode
Polarization V (vertical H (horizontal V (vertical H (horizontal

direction polarization) polarization) polarization) polarization)
NOTE
l To prevent interference on a microwave site, it is recommended that you plan the microwave site as
only a TX high site or a TX low site at a time.
l To prevent interference between two radio links on a microwave site that use transmit frequencies with
a small spacing between, it is recommended that you set the two radio links to operate in different
polarization directions.
l The planning information that is not related to the configuration of the IDU (except for the polarization
direction) is not provided in this example.
Power and ATPC Information

By using the radio network planning software such as the Pathloss, you can analyze and compute
the availability of services and parameters of radio links. Then, you can obtain the power and
ATPC information of the radio links as provided in Table 3-12.

Table 3-12 Power and ATPC information

Transmit power 5 (NE1) 10 (NE3) 10 (NE3) 15 (NE5)

(dBm) 5 (NE2) 10 (NE4) 10 (NE5) 15 (NE6)
Receive power -42 (NE1) -44 (NE3) -43 (NE3) -48 (NE5)
(dBm) -42 (NE2) -44 (NE4) -43 (NE5) -48 (NE6)
ATPC enabling Enabled Enabled Enabled Enabled
ATPC Disabled Disabled Disabled Disabled

automatic
threshold
enabling
Upper threshold -32 (NE1) -34 (NE3) -33 (NE3) -38 (NE5)
of ATPC -32 (NE2) -34 (NE4) -33 (NE5) -38 (NE6)
adjustment
(dBm)
Lower threshold -52 (NE1) -54 (NE3) -53 (NE3) -58 (NE5)
of ATPC -52 (NE2) -54 (NE4) -53 (NE5) -58 (NE6)
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if
there is no such a requirement.
l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value
between the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper
threshold to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive
power.
l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.
When this parameter is not specified, the value of the parameter is the rated maximum transmit power of
the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with
the spectrum configuration profile. Hence, this parameter is not set generally.
Information of IF Boards
According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1
protection, you can obtain the information of IF boards as provided in Table 3-13.

Table 3-13 Information of IF boards
Main IF board 3-IF1 (NE1) 3-IF1 (NE3) 4-IF1 (NE3) 3-IF1 (NE5)
3-IF1 (NE2) 3-IF1 (NE4) 4-IF1 (NE5) 3-IF1 (NE6)
Standby IF 5-IF1 (NE1) 5-IF1 (NE3) 6-IF1 (NE3) -

board 5-IF1 (NE2) 5-IF1 (NE4) 6-IF1 (NE5)
RF 1+1 HSB 1+1 HSB 1+1 HSB 1+0

configuration
mode
Revertive mode Revertive Revertive Revertive -

(default value) (default value) (default value)
WTR time(s) 600 (default 600 (default 600 (default -

value) value) value)
Reverse Disabled Disabled Disabled -

switching
enabling
l It is recommended that you configure the two IF boards that construct the 1+1 HSB
protection group in slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is
recommended that you configure the main IF board in the slot with the smaller slot number.
l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD
l If there are no special requirements, the other parameters of the 1+1 HSB/FD/SD all take
default values.

Procedure
Step 1 See A.8.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE1 to NE5.
l The values for the relevant parameters of NE1 are provided as follows.
Parameter Value
NE1
Working Mode HSB
Revertive Mode Revertive mode
WTR Time(s) 600

Parameter Value
NE1
Enable Reverse Switching Disabled
Working Board 3-IF1
Protection Board 5-IF1
Parameter Value
NE2
Working Mode HSB
WTR Time(s) 600
Working Board 3-IF1
Parameter Value
NE3
Working Mode HSB HSB
Revertive Mode Revertive mode Revertive mode
WTR Time(s) 600 600
Enable Reverse Switching Disabled Disabled
Working Board 3-IF1 4-IF1
Protection Board 5-IF1 6-IF1
Parameter Value
NE4
Working Mode HSB
WTR Time(s) 600

Parameter Value
NE4
Working Board 3-IF1
Parameter Value
NE5
Working Mode HSB
WTR Time(s) 600
Working Board 4-IF1
Step 2 See A.8.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU
information of the radio link.
Parameter Value
3-IF1 and 23-ODU
Work Mode 7,STM-1,28MHz,128QAM
Link ID 101
TX Frequency(MHz) 14930
T/R Spacing(MHz) 420
TX Power(dBm) 5
TX Status unmute
Parameter Value
3-IF1 and 23-ODU
Work Mode 7,STM-1,28MHz,128QAM

Parameter Value
3-IF1 and 23-ODU
Link ID 101
TX Power(dBm) 5
TX Status unmute
Parameter Value
3-IF1 and 23-ODU 4-IF1 and 24-ODU
Work Mode 6,16E1,14MHz,16QAM 8,22E1,14MHz,32QAM
Link ID 102 103
TX Frequency(MHz) 14532 14547
T/R Spacing(MHz) 420 420
TX Power(dBm) 10 10
TX Status unmute unmute
Parameter Value
3-IF1 and 23-ODU
Work Mode 6,16E1,14MHz,16QAM
Link ID 102
TX Power(dBm) 10
TX Status unmute
Parameter Value

Parameter Value
Link ID 104 103
TX Power(dBm) 15 10
Parameter Value
3-IF1 and 23-ODU
Work Mode 4,8E1,7MHz,16QAM
Link ID 104
TX Power(dBm) 15
TX Status unmute
Step 3 See A.8.6 Configuring the ATPC Attributes and configure the ATPC function.
Parameter Value
3-IF1 and 23-ODU
ATPC Enable Status Enabled
ATPC Upper Threshold(dBm) -32
ATPC Lower Threshold(dBm) -52
ATPC Automatic Threshold Enable Disabled

Status
Parameter Value
3-IF1 and 23-ODU

Parameter Value
3-IF1 and 23-ODU

Status
Parameter Value
ATPC Enable Status Enabled Enabled
ATPC Upper Threshold -34 -33

(dBm)
ATPC Lower Threshold -54 -53

(dBm)
ATPC Automatic Disabled Disabled

Threshold Enable Status
Parameter Value
3-IF1 and 23-ODU

Status
Parameter Value

(dBm)

(dBm)

Parameter Value

Parameter Value
3-IF1 and 23-ODU

Status
Step 4 See A.15.3 Setting the Power Attributes of the ODU and set the ODU power attributes.
Parameter Value
3-IF1 and 23-ODU
Power to Be Received(dBm) -42
Parameter Value
3-IF1 and 23-ODU
Parameter Value
Power to Be Received -44 -43

(dBm)

Parameter Value
3-IF1 and 23-ODU
Parameter Value

(dBm)
Parameter Value
3-IF1 and 23-ODU
Method and create radio links connections.
The main topology should display all the created radio links.
----End
3.4 Configuration Example (Radio Links on the TDM Radio

Ring Network)
This section considers TDM radio links on a TDM radio ring network as examples to describe
how to configure radio links according to the network planning information.


Based on 2.4 Configuration Example (Ring Network), configure the TDM radio links
according to the network planning information (as shown in Figure 3-6):

BTS BTS1 BTS2 BTS3 BTS4
Number of E1 4 4 4 4
services
NE2 and the radio links between NE1 and NE4 are configured with 1+1 HSB protection.
l The ATPC function is enabled to reduce inter-site interference.
Figure 3-6 Networking diagram (TDM radio ring network)
BSC
101 104
14930M 14958M
14510M 14538M
16E1,14M,16QAM NE1 16E1,14M,16QAM
1+1 HSB 1+1 HSB
V-polarzation V-polarization
Tx high Tx high
Tx low Tx low
BTS1
Tx low Tx low
NE2 NE4 BTS4
Tx high Tx high
BTS2 102 103
14958M 14930M
14538M 14510M
16E1,14M,16QAM 4E1 16E1,14M,16QAM
1+0 1+0
H-polarization NE3 H-polarzation
BTS3
Link ID
Tx high station Tx Freq.
Radio work mode
RF configuarion
Polarization


signals.

signals.

signals.

signals.



capacity, you can obtain the basic information about the radio links as provided in Table 3-19.
Link ID 101 102 103 104
Tx frequency at 14930 14958 14930 14958

the Tx high site
(MHz)
Tx frequency at 14510 14538 14510 14538

the Tx low site
(MHz)
T/R spacing 420 420 420 420

(MHz)
Radio working 16E1, 14MHz, 16E1, 14MHz, 16E1, 14MHz, 16E1, 14MHz,
mode 16QAM 16QAM 16QAM 16QAM
RF 1+1 HSB 1+0 1+0 1+1 HSB

configuration
mode
Polarization V (vertical H (horizontal H (horizontal V (vertical

NOTE
The planning information that is not related to the configuration of the IDU (except for the polarization

the availability of services and parameters of radio links. Then, you can obtain the power and
ATPC information about the radio links, as provided in Table 3-20.
Transmit power 9 (NE1) 10 (NE3) 10 (NE3) 8 (NE1)

(dBm) 9 (NE2) 10 (NE2) 10 (NE4) 8 (NE4)

(dBm) -46 (NE2) -44 (NE2) -43 (NE4) -47 (NE4)
ATPC enabling Enabled Enabled Enabled Enabled
ATPC Disabled Disabled Disabled Disabled

automatic
threshold
enabling
Upper threshold -36 (NE1) -34 (NE3) -33 (NE3) -37 (NE1)
of ATPC -36 (NE2) -34 (NE2) -33 (NE4) -37 (NE4)
adjustment
(dBm)
Lower threshold -56 (NE1) -54 (NE3) -53 (NE3) -57 (NE1)
of ATPC -56 (NE2) -54 (NE2) -53 (NE4) -57 (NE4)
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if
there is no such a requirement.
l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value of
the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper threshold
to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive power.
l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.
When this parameter is not specified, the value of the parameter is the rated maximum transmit power of
the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with
the spectrum configuration profile. Hence, this parameter is not set generally.
Information About IF Boards

protection, you can obtain the information about IF boards as provided in Table 3-21.
Table 3-21 Information of IF boards
Main IF board 4-IF1 (NE1) 4-IF1 (NE2) 4-IF1 (NE3) 4-IF1 (NE4)
3-IF1 (NE2) 3-IF1 (NE3) 3-IF1 (NE4) 3-IF1 (NE1)
Standby IF 6-IF1 (NE1) - - 6-IF1 (NE4)

board 5-IF1 (NE2) 5-IF1 (NE1)

RF 1+1 HSB 1+0 1+0 1+1 HSB

configuration
mode
Revertive mode Revertive - - Revertive

(default value) (default value)
WTR time(s) 600 (default - - 600 (default

value) value)
Reverse Disabled - - Disabled

switching
enabling
NOTE
l It is recommended that you configure the two IF boards that construct the 1+1 HSB protection group in slot
3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main
IF board in the slot with the smaller slot number.
l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD protection group in
slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the
main IF board in the slot with the smaller slot number.
l If there are no special requirements, the other parameters of the 1+1 HSB/FD/SD all take default values.

Procedure
Step 1 See A.8.1 Creating an IF 1+1 Protection Group and configure the 1+1 protection groups for
NE1, NE2, and NE4.
Parameter Value
NE1
WTR Time(s) 600 600
Working Board 3-IF1 4-IF1
Protection Board 5-IF1 6-IF1

Parameter Value
NE2
Working Mode HSB
WTR Time(s) 600
Working Board 3-IF1
Parameter Value
NE4
Working Mode HSB
WTR Time(s) 600
Working Board 4-IF1
Parameter Value
Link ID 104 101
TX Power(dBm) 8 9

Parameter Value
Work Mode 6, 16E1,14MHz, 16QAM 6, 16E1, 14MHz, 16QAM
Link ID 101 102
TX Power(dBm) 9 10
Parameter Value
Work Mode 6, 16E1, 14MHz, 16QAM 6, 16E1, 14MHz, 16QAM
Link ID 102 103
TX Power(dBm) 10 10
Parameter Value
Work Mode 6, 16E1, 14MHz, 16QAM 6, 16E1, 14MHz, 16QAM
Link ID 103 104
TX Power(dBm) 10 8

Parameter Value

(dBm)

(dBm)

Parameter Value

(dBm)

(dBm)

Parameter Value

(dBm)

(dBm)


Parameter Value

(dBm)

(dBm)

Parameter Value

(dBm)
Parameter Value

(dBm)
Parameter Value

(dBm)
Parameter Value

(dBm)

Step 5 A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search
----End
3.5 Configuration Example (Radio Links on the Hybrid

Radio Chain Network)
This section considers radio links on a Hybrid radio chain network as examples to describe how

This section provides the information about all the parameters required for configuring the NE
data.

Based on 2.3 Configuration Example (Chain Network), configure the Hybrid radio links
according to the following network planning information (as shown in Figure 3-7):
l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
NE2, between NE3 and NE4, and between NE3 and NE5 are configured with 1+1 HSB
protection.

Number of 4 2 2 2 2
high-
priority E1s
Number of 0 0 2 2 2
low-priority
E1s

Capacity of 2 1 1 1 1
high-
priority
Ethernet
services
(Mbit/s)
Capacity of 35 15 20 20 15
low-priority
Ethernet
services
(Mbit/s)
NOTE
High-priority services are guaranteed with sufficient transmission resources and are not discarded even in
the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources
and may be discarded in the case of an AM switch. The common service priorities are provided in Table
3-23.
Table 3-23 Common service priorities

Service Type Service Class
TDM E1s that transmit 2G base station High-priority services

services
ATM E1s (IMA E1s are not used) that High-priority services
transmit 3G base station services
E1s (of a bandwidth not lower than the High-priority service

high-priority service bandwidth) in the
IMA E1 group that transmits 3G base
station services
Other E1s in the IMA E1 group that Low-priority services

transmits 3G base station services
Voice, signaling, and OM Ethernet High-priority services

services
Streaming media, background, and Low-priority services

interactive Ethernet services, for example,
Internet services

Figure 3-7 Networking diagram (Hybrid radio chain network)

102
14952M 101
BTS2 14930M
14532M
14M 14510M
28M
1+1 HSB
1+1 HSB
H-polarization
V-polarzation
BTS3
Tx high NE3 NE2 NE1
104 Tx low
14930M NE4 Tx high
Tx low
14510M Tx high Tx low
7M
1+0 BSC
103
H-polarzation 14967M
14547M BTS1
Tx high 14M
NE5 1+1 HSB Link ID
Tx low V-polarization Tx high station Tx Freq.
NE6 Channel spacing
BTS4 RF configuarion
BTS5 Polarization

Between NE1 and NE2 3-IFU2 (main IF board) Configure the ports as a 1+1
5-IFU2 (standby IF board)





Between NE5 and NE6 3-IFU2 Configure this port to receive

signals.


signals.

data.

capacity, you can obtain the basic information of the radio links, as provided in Table 3-30.

Link ID 101 102 103 104

Tx frequency at 14930 14952 14967 14930

the Tx high site
(MHz)
Tx frequency at 14510 14532 14547 14510

the Tx low site
(MHz)
T/R spacing 420 420 420 420

(MHz)
Channel 28 14 14 7
spacing (MHz)
RF 1+1 HSB 1+1 HSB 1+1 HSB 1+0

configuration
mode
Polarization V (vertical H (horizontal V (vertical H (horizontal

NOTE
Hybrid/AM Attribute Information

According to the capacity of E1 and Ethernet services and the availability requirement, you can
calculate the Hybrid/AM attribute information, as provided in Table 3-31.
Table 3-31 Hybrid/AM attribute information

Number of E1s 12 4 4 2
in AM
guaranteed
capacity mode
in AM full
capacity mode
Capacity of 6 2 2 1
high-priority
Ethernet
services (Mbit/
s)

Capacity of low- 105 35 35 15

priority
Ethernet
services (Mbit/
s)
AM enabling Enabled Enabled Enabled Enabled
AM guaranteed QPSK QPSK QPSK QPSK

capacity mode
AM full 128QAM 32QAM 64QAM 32QAM

capacity mode
E1 priority Enabled Enabled Enabled Enabled

enabling
NOTE
The Hybrid radio capacity and the AM function require the proper license file.

the parameters of radio links and obtain the power and ATPC information of the radio links, as
provided in Table 3-32.

Transmit power 16.5 (NE1) 16.5 (NE3) 16 (NE3) 20 (NE5)

(dBm) 16.5 (NE2) 16.5 (NE4) 16 (NE5) 20 (NE6)
(dBm) -46 (NE2) -44 (NE4) -43 (NE5) -48 (NE6)
ATPC enabling Disabled Disabled Disabled Disabled
ATPC - - - -
automatic
threshold
enabling
Upper threshold - - - -
of ATPC
adjustment
(dBm)

Lower threshold - - - -
of ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
l The transmit power is calculated in AM guaranteed capacity mode.

l The receive power is calculated in AM guaranteed capacity mode.
l In this example, the ATPC function is disabled.

protection, you can obtain the information about IF boards, as provided in Table 3-33.
Table 3-33 Information about IF boards
Main IF board 3-IFU2 (NE1) 3-IFU2 (NE3) 4-IFU2 (NE3) 3-IFU2 (NE5)
3-IFU2 (NE2) 3-IFU2 (NE4) 4-IFU2 (NE5) 3-IFU2 (NE6)
Standby IF 5-IFU2 (NE1) 5-IFU2 (NE3) 6-IFU2 (NE3) -

board 5-IFU2 (NE2) 5-IFU2 (NE4) 6-IFU2 (NE5)
RF 1+1 HSB 1+1 HSB 1+1 HSB 1+0

configuration
mode
Revertive mode Revertive Revertive Revertive -

(default value) (default value) (default value)
WTR time(s) 600 (default 600 (default 600 (default -

value) value) value)
Reverse Disabled Disabled Disabled -

switching
enabling
l It is recommended that you configure the two IF boards that construct the 1+1 HSB

l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD
l If there are no special requirements, it is recommended that you plan the other parameters
of the 1+1 HSB/FD/SD to be the default values.

Procedure
NE1 to NE5.
Parameter Value
NE1
Working Mode HSB
WTR Time(s) 600
Working Board 3-IFU2
Protection Board 5-IFU2
Parameter Value
NE2
Working Mode HSB
WTR Time(s) 600

Parameter Value
NE3
WTR Time(s) 600 600
Working Board 3-IFU2 4-IFU2
Protection Board 5-IFU2 6-IFU2
Parameter Value
NE4
Working Mode HSB
WTR Time(s) 600
Parameter Value
NE5
Working Mode HSB
WTR Time(s) 600

Parameter Value
3-IFU2 and 23-ODU
IF Channel Bandwidth 28M
AM Enable Status Enabled
Modulation Mode of the Guarantee AM QPSK

Capacity
Modulation Mode of the Full AM 128QAM

Capacity
Enable E1 Priority Enabled
Guarantee E1 Capacity 12
Full E1 Capacity 18
Link ID 101
TX Power(dBm) 16.5
TX Status unmute
Parameter Value
3-IFU2 and 23-ODU

Capacity

Capacity
Full E1 Capacity 18
Link ID 101
TX Power(dBm) 16.5

Parameter Value
3-IFU2 and 23-ODU
TX Status unmute
Parameter Value
3-IFU2 and 23-ODU 4-IFU2 and 24-ODU
IF Channel Bandwidth 14M 14M
AM Enable Status Enabled Enabled
Modulation Mode of the QPSK QPSK

Guarantee AM Capacity
Modulation Mode of the 32QAM 64QAM

Full AM Capacity
Enable E1 Priority Enabled Enabled
Guarantee E1 Capacity 4 4
Full E1 Capacity 6 8
Link ID 102 103
TX Power(dBm) 16.5 16
Parameter Value
3-IFU2 and 23-ODU

Capacity

Capacity

Parameter Value
3-IFU2 and 23-ODU
Full E1 Capacity 6
Link ID 102
TX Power(dBm) 16.5
TX Status unmute
Parameter Value
Modulation Mode of the QPSK QPSK


Full AM Capacity
Enable E1 Priority Enabled Enabled
Full E1 Capacity 4 8
Link ID 104 103
TX Power(dBm) 20 16
Parameter Value
3-IFU2 and 23-ODU

Parameter Value
3-IFU2 and 23-ODU

Capacity

Capacity
Full E1 Capacity 4
Link ID 104
TX Power(dBm) 20
TX Status unmute
Step 3 See A.8.5 Setting IF Attributes and set the IF attributes.

Parameter Value
3-IFU2 and 23-ODU
Enable IEEE-1588 Timeslot Disabled
Parameter Value
3-IFU2 and 23-ODU
Parameter Value
Enable IEEE-1588 Disabled Disabled

Timeslot

Parameter Value
3-IFU2 and 23-ODU
Parameter Value

Timeslot
Parameter Value
3-IFU2 and 23-ODU
Parameter Value
3-IFU2 and 23-ODU
ATPC Enable Status Disabled
Parameter Value
3-IFU2 and 23-ODU
Parameter Value
ATPC Enable Status Disabled Disabled

Parameter Value
3-IFU2 and 23-ODU
Parameter Value
Parameter Value
3-IFU2 and 23-ODU
Parameter Value
3-IFU2 and 23-ODU
Parameter Value
3-IFU2 and 23-ODU
Parameter Value

(dBm)

Parameter Value
3-IFU2 and 23-ODU
Parameter Value

(dBm)
Parameter Value
3-IFU2 and 23-ODU
Step 6 A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search
----End
3.6 Configuration Example (Radio Links on the Hybrid

Radio Ring Network)
This section considers radio links on a Hybrid radio ring network as examples to describe how

data.

Based on 2.4 Configuration Example (Ring Network), configure the Hybrid radio links
according to the network planning information (as shown in Figure 3-8):

l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
NE2 and the radio links between NE1 and NE4 are configured with 1+1 HSB protection.

Number of 4 4 4 4
high-priority
E1s
Number of 0 0 0 0
low-priority
E1s
Capacity of 0 0 0 0
high-priority
Ethernet
services (Mbit/
s)
Capacity of 10 10 10 10
low-priority
Ethernet
services (Mbit/
s)
NOTE
High-priority services are guaranteed with sufficient transmission resources and are not discarded even in
the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources
and may be discarded in the case of an AM switch. The common service priorities are provided in Table
3-35.
Table 3-35 Common service priorities

TDM E1s that transmit 2G base station High-priority services

services
ATM E1s (IMA E1s are not used) that High-priority services
transmit 3G base station services
E1s (of a bandwidth not lower than the High-priority service

high-priority service bandwidth) in the
IMA E1 group that transmits 3G base
station services

Other E1s in the IMA E1 group that Low-priority services

transmits 3G base station services
Voice, signaling, and OM Ethernet High-priority services

services
Streaming media, background, and Low-priority services

interactive Ethernet services, for example,
Internet services
Figure 3-8 Networking diagram (Hybrid radio ring network)
BSC
101 104
14930M 14958M
14510M 14538M
14M NE1 14M
1+1 1+1
V-polarzation V-polarization
Tx high Tx high
Tx low Tx low
BTS1
Tx low Tx low
NE2 NE4 BTS4
Tx high Tx high
BTS2 102 103
14958M 14930M
14538M 14510M
14M 4E1 14M
1+0 1+0
H-polarization NE3 H-polarzation
BTS3
Link ID
Tx high station Tx Freq.
Channel spacing
RF configuarion
Polarization



signals.


signals.

signals.


signals.

data.


capacity, you can obtain the basic information about the radio links, as provided in Table
3-40.
Link ID 101 102 103 104
Tx frequency at 14930 14958 14930 14958

the Tx high site
(MHz)
Tx frequency at 14510 14538 14510 14538

the Tx low site
(MHz)
T/R spacing 420 420 420 420

(MHz)
Channel 14 14 14 14
spacing (MHz)
RF 1+1 HSB 1+0 1+0 1+1 HSB

configuration
mode
Polarization V (vertical H (horizontal H (horizontal V (vertical

NOTE
Hybrid/AM Attribute Information

According to the capacity of E1 and Ethernet services and the availability requirement, you can
calculate the Hybrid/AM attribute information as provided in Table 3-41.
Table 3-41 Hybrid/AM attribute information
in guaranteed
capacity mode

Number of E1s - - - -
in AM full
capacity mode
Capacity of 0 0 0 0
high-priority
Ethernet
services (Mbit/
s)
Capacity of low- 40 40 40 40
priority
Ethernet
services (Mbit/
s)
AM enabling Enabled Enabled Enabled Enabled
AM guarantee 16QAM 16QAM 16QAM 16QAM

capacity mode
AM full 128QAM 128QAM 128QAM 128QAM

capacity mode
E1 priority Disabled Disabled Disabled Disabled

enabling
NOTE
l In this example, all E1 services are high-priority services. Therefore, the E1 priority function need not
be enabled.
l According to the Hybrid ring protection scheme, each Hybrid radio link must carry all the services on
the ring.
l The Hybrid radio capacity and the AM function require the appropriate license file.

the parameters of radio links and obtain the power and ATPC information of the radio links, as
Transmit power 16.5 (NE1) 16.5 (NE3) 16 (NE3) 15 (NE1)

(dBm) 16.5 (NE2) 16.5 (NE2) 16 (NE4) 15 (NE4)
(dBm) -42 (NE2) -44 (NE2) -43 (NE4) -45 (NE4)

ATPC enabling Disabled Disabled Disabled Disabled
ATPC - - - -
automatic
threshold
enabling
Upper threshold - - - -
of ATPC
adjustment
(dBm)
Lower threshold - - - -
of ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
NOTE
l The transmit power is calculated in AM guaranteed capacity mode.

l The receive power is calculated in AM guaranteed capacity mode.
l In this example, the ATPC function is disabled.

protection, you can obtain the information about IF boards, as provided in Table 3-43.
Table 3-43 Information about IF boards

Main IF board 4-IFU2 (NE1) 4-IFU2 (NE2) 4-IFU2 (NE3) 4-IFU2 (NE4)
3-IFU2 (NE2) 3-IFU2 (NE3) 3-IFU2 (NE4) 3-IFU2 (NE1)
Standby IF 6-IFU2 (NE1) - - 6-IFU2 (NE4)

board 5-IFU2 (NE2) 5-IFU2 (NE1)
RF 1+1 HSB 1+0 1+0 1+1 HSB

configuration
mode
Revertive mode Revertive - - Revertive

(default value) (default value)
WTR time(s) 600 (default - - 600 (default

value) value)

Reverse Disabled - - Disabled

switching
enabling
NOTE
l It is recommended that you configure the two IF boards that construct the 1+1 HSB protection group in slot
3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main
IF board in the slot with the smaller slot number.
l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD protection group in
slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the
main IF board in the slot with the smaller slot number.
l If there are no special requirements, it is recommended that you plan the other parameters of the 1+1 HSB/
FD/SD to be the default values.

Procedure
NE1, NE2, and NE4.
Parameter Value
NE1
WTR Time(s) 600 600
Working Board 3-IFU2 4-IFU2
Protection Board 5-IFU2 6-IFU2
Parameter Value
NE2
Working Mode HSB
WTR Time(s) 600

Parameter Value
NE2
Parameter Value
NE4
Working Mode HSB
WTR Time(s) 600
Parameter Value


Full AM Capacity
Enable E1 Priority Disabled Disabled
Link ID 104 101
TX Power(dBm) 15 16.5

Parameter Value
Parameter Value


Full AM Capacity
Link ID 101 102
TX Power(dBm) 16.5 16.5
Parameter Value


Full AM Capacity
Link ID 102 103

Parameter Value
TX Power(dBm) 16.5 16
Parameter Value


Full AM Capacity
Link ID 104 103
TX Power(dBm) 15 16
Step 3 See A.8.5 Setting IF Attributes and set the IF attributes

Parameter Value

Timeslot

Parameter Value

Timeslot
Parameter Value

Timeslot
Parameter Value

Timeslot
Parameter Value
Parameter Value
Parameter Value

Parameter Value
Parameter Value

(dBm)
Parameter Value

(dBm)
Parameter Value

(dBm)
Parameter Value

(dBm)
----End

Configuration Guide (U2000) 4 Configuring TDM Services
4 Configuring TDM Services
About This Chapter
The key to configuring TDM services is configuring the corresponding service cross-
connections.
4.1 Basic Concepts

Before configuring the TDM service, you need to be familiar with the basic concepts.
This section describes the procedures for configuring the cross-connections and protection of a
TDM service and the procedures for setting the SDH/PDH port parameters.
4.3 Configuration Example (TDM Services on a TDM Radio Chain Network)
This section considers a TDM radio chain network as an example to describe how to configure
TDM services according to the network planning information.
4.4 Configuration Example (TDM Services on a TDM Radio Ring Network)
This section considers a TDM radio ring network as an example to describe how to configure
4.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network)
This section considers a Hybrid radio chain network as an example to describe how to configure
4.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network)
This section considers a Hybrid radio ring network as an example to describe how to configure

4 Configuring TDM Services Configuration Guide (U2000)
4.1 Basic Concepts

Before configuring the TDM service, you need to be familiar with the basic concepts.
4.1.1 Protection Modes for TDM Services

OptiX RTN 950 supports linear MSP and SNCP for TDM services.
4.1.2 Timeslots for TDM Services on IF Boards
When TDM services need to be transmitted on a radio link, you need to configure the
corresponding cross-connections between the service timeslots on the service board and the
service timeslots on the IF board. The timeslots for the TDM services on the IF board are closely
related to the type of the radio services transmitted by the IF board and the radio capacity.
4.1.3 Numbering Schemes for SDH Timeslots
Two numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines or
SDH radio links.
4.1.4 TDM Timeslot Planning Schemes
TDM timeslot planning schemes include the TDM timeslot planning scheme for chain networks
and the TDM timeslot planning scheme for ring networks.
4.1.1 Protection Modes for TDM Services

OptiX RTN 950 supports linear MSP and SNCP for TDM services.
Linear MSP
Linear MSP applies to point-to-point physical networks. Linear MSP provides protection for the
services between two multiplex section termination (MST) modules. That is, when a linear MSP
switching occurs, the services are switched from the working section to the protection section.
In the case of the OptiX RTN 950, linear MSP provides protection for TDM services that are
transmitted over SDH fibers.
Linear MSP is classified into 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. The protection channel does not transmit extra services. When the working
channel becomes unavailable, services are switched to the protection channel for
transmission. Figure 4-1 shows the application of 1+1 linear MSP. According to the
revertive mode, 1+1 linear MSP is classified into dual-ended revertive, dual-ended non-
revertive, single-ended revertive, and single-ended non-revertive modes. The single-ended
non-revertive mode is the most common linear MSP mode.

Figure 4-1 1+1 linear MSP

Working NE B
NE A
channel
Protection
channel
Protection switching
Working
NE A 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 4-2 shows the
application of the 1:N linear MSP. The 1:N linear MSP is available only in dual-ended
revertive mode.

Figure 4-2 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
SNCP
In the case of subnetwork connection protection (SNCP), the protection subnetwork connection
takes over when the working subnetwork connection fails or deteriorates. In the case of the
OptiX RTN 950, SNCP provides protection for TDM services that are transmitted on STM-1
fiber ring networks, TDM radio ring networks, Hybrid radio ring networks, or hybrid ring
networks that comprise optical network equipment and Hybrid radio equipment.
The SNCP protection scheme, which requires one working subnetwork and one protection
subnetwork, selects one service from the dually transmitted services. In the case of SNCP, the
services are switched to the protection subnetwork for transmission when the working
subnetwork connection fails or deteriorates. Figure 4-3 shows the application of SNCP.

Figure 4-3 SNCP
Working SNC
Trail source Trail sink
NE A NE B
Protection SNC
Working SNC
Trail source Trail sink
NE A NE B
Protection SNC
The OptiX RTN 950 supports the coexistence of SNCP and the 1+1 protection or N+1 protection.
In the case of coexistence of the SNCP and the 1+1 protection or N+1 protection, you can set
the hold-off time for SNCP so that the protection switching for the radio link can be performed
first, thus preventing circular switchings.
4.1.2 Timeslots for TDM Services on IF Boards

When TDM services need to be transmitted on a radio link, you need to configure the
corresponding cross-connections between the service timeslots on the service board and the
service timeslots on the IF board. The timeslots for the TDM services on the IF board are closely
related to the type of the radio services transmitted by the IF board and the radio capacity.
TDM Radio
When the IF board works in PDH radio mode and when the radio capacity is nxE1, the first to
nth VC-12 timeslots on the IF board are available and correspond to first to nth E1s that are
transmitted over microwave. For example, if the radio capacity is 4xE1, only the first to fourth
VC-12 timeslots in VC4-1 on the IF board are available. If a cross-connection is configured
between the E1 port of a service board and the second VC-12 in VC4-1 on the IF board, the E1
services that are accessed from the E1 port are sent to the second E1 timeslot that is transmitted
over radio. If the radio capacity is E3, only the first VC-3 timeslot in VC4-1 on the IF board is
available and corresponds to the E3 timeslot that is transmitted over microwave.

When the IF board works in STM-1 radio mode, all the timeslots in VC4-1 on the IF board are
available and correspond to the timeslots in the VC-4 that is transmitted on microwave.
Hybrid Radio
When the IF board works in Hybrid radio mode and when the E1 Capacity is set to n in Hybrid/
AM Configuration, the first to nth VC-12 timeslots on the IF board are available and correspond
to the first to nth E1 timeslots that are transmitted over microwave. For example, if the E1
capacity is 75xE1, only the first to sixty-third VC-12 timeslots in VC4-1 and the first to twelfth
VC-12 timeslots in VC4-2 on the IF board are available. If a cross-connection is configured
between the E1 port of a service board and the second VC-12 in VC4-2 on the IF board, the E1
services that are accessed from the E1 port are sent to the sixty-fifth E1 timeslot that is transmitted
over microwave.
4.1.3 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. 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 and is the default
scheme adopted by the OptiX equipment.
l Interleaved scheme
This timeslot numbering scheme is also considered as line scheme. 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 a specific timeslot numbering scheme is required.
Figure 4-4 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 4-5 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 cross-
connections of VC-3s and VC-12s in the same VC-4, 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.
4.1.4 TDM Timeslot Planning Schemes

TDM timeslot planning schemes include the TDM timeslot planning scheme for chain networks
and the TDM timeslot planning scheme for ring networks.
Timeslot Allocation Diagram

The timeslot allocation diagram provides significant references for configuring TDM services.
Before planning TDM timeslots, you need to be familiar with the meanings shown in the timeslot
allocation diagram.

Figure 4-6 Timeslot allocation diagram

Site
NE1 NE2 NE3 NE4
Interface Interface Interface Interface Interface Interface
Timeslot board 2 board 5 board 6
board 1 board 3 board 4
Timeslot 1
Tributary board: Tributary board:
port No. Timeslot 2 Timeslot 4
port No.
Tributary board: Tributary board:
port No. Timeslot 3 port No. Timeslot 5
VC4-1
Tributary board: Tributary board: Tributary board: Tributary board:
port No. port No. port No. port No.
VC4-2 ......
Site area Add/Drop

......
Foward
Timeslot area
Pass-through
Timeslot allocation
Add/Drop (SNCP path)
area
As shown in Figure 4-6, the timeslot allocation diagram contains three areas, namely, site area,
timeslot area, and timeslot allocation area.
The site area contains the NE icons and interface boards that carry radio links.
l The start and end NEs each have only one interface board, which is located under the NE
icon. The intermediate NEs each have two interface boards, which are located at the two
sides of the vertical line under the NE icon. The interface boards may be IF boards or line
boards.
l The interface board on the left side of the vertical line under an NE icon is connected to
the interface board on the right side of the vertical line under its upstream NE icon. The
interface board on the right side of the vertical line under an NE icon is connected to the
interface board on the left side of the vertical line under its downstream NE icon.
l In the case of a ring radio link, before planning the site area, you need to divide the ring
radio link into a chain radio link and ensure that the start and end NEs are the same one.
The timeslot area represents the VC-4 timeslot resources. For example, in the case of radio links,
timeslots occupied by an STM-1 service are all in the first VC-4.
In the timeslot allocation area, each straight line represents a service and the numeric above the
straight line represents the timeslot occupied by this service.
l A black dot indicates that services are added to or dropped from the NE. The board under
a black dot indicates the board and corresponding ports on the board that are used for adding
or dropping services.
l An arrow indicates that services are transferred on the NE.
l If a straight line passes a vertical line without any arrow or black dot, it indicates that
services pass through the NE.
l In the case of protection configuration (for example, 1+1 HSB protection) wherein the
working service and protection service have the uniform route, you only need to draw a
continuous line to represent the working service. In the case of protection configuration

(for example, SNCP) wherein the working service and protection service have different
routes, you need to draw a continuous line to represent the working service and a dotted
line to represent the protection service.
TDM Timeslot Planning Scheme for Chain Networks

On the backhaul network for a mobile BTS, the services are accessed from different nodes and
then aggregated to the same node for transmission. In this case, allocate the timeslots on the
chain radio network as follows:
1. Select the chain that contains the maximum of hops as the main chain. Then, divide the
chain network into several sub-chains by considering the main chain as the reference.
Consider the E1 channels or fiber connections that are used for transferring services
between NEs as links.
2. Allocate the timeslots for the add/drop or pass-through services on the NEs of the main
chain one after another, in the descending order of the NE distance.
3. Repeat the previous step to configure the timeslots for the services on all the sub-chains.
This timeslot allocation method ensures that only the numbers of the timeslots that the services
on the nodes of the aggregation sub-chain occupy may change.
The principles for obtaining the timeslot cross-connection configurations from the non-SNCP
service timeslot allocation diagram are as follows:
l A straight line without any dot at either side represents a pass-through service. A straight
line with one dot represents an add/drop service. A straight line with an arrow represents
a transferred service. The vertical line under the NE name is considered as the reference.
l If a straight line representing a pass-through service crosses the vertical line, it indicates
that cross-connections are configured between the boards on both sides of the vertical line.
The corresponding cross-connected timeslots are marked over the straight line.
l If there is a straight line with one dot on one side of the vertical line, it indicates that cross-
connections are configured between the board on this side of the vertical line and the board
under the straight line with one dot. The corresponding cross-connected timeslots are
marked over the straight line with one dot.
l If there is a straight line with an arrow on both sides of the vertical line, it indicates that
cross-connections are configured between the two boards on both sides of the vertical line.
The corresponding cross-connected timeslots on each board are marked over the straight
line with an arrow on the side of this board.
For details, see 4.3 Configuration Example (TDM Services on a TDM Radio Chain
Network) and 4.5 Configuration Example (TDM Services on a Hybrid Radio Chain
Network).
TDM Timeslot Planning Scheme for Ring Networks

On a backhaul network for a mobile BTS, the services are accessed from different nodes and
then aggregated to the same node for transmission. Hence, you can perform the following
operations to allocate the timeslots on the SNCP radio ring network:
1. Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate
the minimum VC-12 timeslot number to the service on the nearest NE. The number of the
timeslot each service occupies does not change on the ring network.
2. Repeat the previous step to configure the timeslots for the services on all the sub-chains.

This timeslot allocation method ensures that only the timeslots that the services on the nodes of
the aggregation sub-chain occupy change.
The principles for obtaining the timeslot cross-connection configurations from the SNCP service
timeslot allocation diagram are as follows:
l A straight line without any dot at either side represents a pass-through service. A straight
line with one dot represents an add/drop service. A straight line with an arrow represents
a transferred service. The vertical line under the NE name is considered as the reference.
l If a straight line representing a pass-through service crosses the vertical line, it indicates
that cross-connections are configured between the boards on both sides of the vertical line.
The corresponding cross-connected timeslots are marked over the straight line.
l If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP
cross-connections are configured between the board on this side of the vertical line and the
board under the straight line with one dot. The corresponding cross-connected timeslots
are marked over the straight line with one dot.
For details, see 4.4 Configuration Example (TDM Services on a TDM Radio Ring
Network) and 4.6 Configuration Example (TDM Services on a Hybrid Radio Ring
Network).

This section describes the procedures for configuring the cross-connections and protection of a
TDM service and the procedures for setting the SDH/PDH port parameters.
Figure 4-7 provides the procedures for configuring TDM services.

Figure 4-7 Configuration flow chart (TDM services)
Required
Start
Optional
Configuring linear MSP
Creating TDM service cross-

connections
Configuring the automatic switching

conditions of SNCP services
Modifying the priorities of E1 services
Configuring the overhead bytes
Setting parameters
of SDH port
Setting parameters of PDH ports
Performing PRBS tests for E1

services
End

Table 4-1 Procedures for configuring TDM services

1 A.9.1 Configuring Required when linear MSP is configured for the

Linear MSP optical transmission line.
The parameters need to be set according to the
service planning.
2 Configuri A.10.1 Required when the TDM service is a point-to-point

ng the Creating service.
cross- the Cross- The parameters need to be set according to the
connectio Connectio service planning.
ns of the ns of
TDM Point-to-
servicea Point
Services
A.10.2 Required when the TDM service is an SNCP service.

Creating The parameters need to be set according to the
Cross- service planning.
Connectio
ns of
SNCP
Services
3 A.10.4 Configuring the Optional when the TDM service is an SNCP service.
Automatic Switching
of SNCP Services
4 A.8.9 Modifying the Required when the working source, protection

Priorities of E1 source, or sink of an SNCP service is a link where
Services the AM function and the E1 priority function are
enabled.
E1 Priority needs to be modified according to the
service planning information.
5 Configuri A.18.1 Required when the J0_MM alarm is generated on the

ng the Configuri local or remote equipment.
overhead ng
bytes RSOHs
A.18.2 Required when the TIM or SLM alarm is generated

Configuri on the local or remote equipment.
ng VC-4
POHs
A.18.3 Required when the TIM or SLM alarm is generated

Configuri on the local or remote equipment.
ng VC-12
POHs
6 A.16 Setting the Optional.

Parameters of SDH
Ports

7 A.17 Setting the Optional.

Parameters of PDH
Ports
8 A.10.11 Testing the E1 The test results should show that each E1 service
Service Through contains no bit errors.
PRBS
NOTE
a: In the case of 1+1 protection configuration or 1+1 linear MSP, you need to configure the TDM service on the
working channel only. In the case of N+1 protection configuration or 1:N linear MSP, you also need to configure
the extra services on the protection channel if required.
4.3 Configuration Example (TDM Services on a TDM Radio

Chain Network)


Based on 3.3 Configuration Example (Radio Links on the TDM Radio Chain Network),
configure the TDM services according to the following network planning information (as shown
in Figure 4-8):
l To ensure reliable transmission of the services between NE1 and the BSC, linear MSP is
configured for the optical transmission line.
l Services are transferred between NE2 and NE3 through STM-1 optical ports.

Figure 4-8 Networking diagram (TDM services on a TDM radio chain network)
8xE1
BTS2
STM-1 STM-1
8xE1 NE4
BTS3
16xE1
NE3 NE2 NE1 BSC
14xE1 BTS1
8xE1
NE6 NE5
BTS5 BTS4
The connections of TDM links shown in Figure 4-8 are described as follows.
Table 4-2 Connections of TDM links (NE1)
Between NE1 and the BSC 1-SL1D-1 (working port) Configure the ports as a 1+1
linear MSP group.
1-SL1D-2 (protection port)
Between NE2 and BTS1 2-SP3S (1-16) Configure the ports to access
services from BTS1.
Between NE2 and NE3 1-SL1D-1 Configure this port to

transmit TDM services.
Between NE3 and NE2 1-SL1D-1 Configure this port to



services from BTS2 and
Between NE4 and BTS3 BTS3.

services from BTS4.

signals.

services from BTS5.

signals.



Figure 4-9 shows the timeslots that are allocated for the TDM services according to the service
Figure 4-9 Timeslot allocation diagram (TDM services on the TDM radio chain network)
Links-1: NE1 - NE2 - NE3 -NE6
Station BS
NE1 NE2 NE3 NE5 NE6
C
Timeslot 1-SL1D-1 3-IF1 3-IF1 1-SL1D-1 1-SL1D-1 4-IF1 4-IF1 3-IF1 3-IF1
VC12: 1-8
VC12: 9-22 2-SP3S:1-8
VC12: 23-38 2-SP3S:1-14

VC4-1
VC12: 39-54
2-SP3S:1-16
Links-2: NE3-NE4
Station NE3 NE4
Timeslot 1-SL1D-1 3-IF1 3-IF1
VC12: 23-38 VC12: 1-16
VC4-1
2-SP3S:1-16
Pass through
Add/Drop
Foward
As shown in Figure 4-9, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l E1 services on NE6:
– The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 2 of NE6.
– The E1 services occupy the first to eighth VC-12 timeslots on the link between the first
optical port on the SL1D board in slot 1 of NE1 and the IF1 board in slot 3 of NE6.
– The E1 services are added to or dropped from the first to fourteenth ports on the SP3S
board in slot 2 of NE5.
– The E1 services occupy the ninth to twenty-second VC-12 timeslots on the link between
the first optical port on the SL1D board in slot 1 of NE1 and the IF1 board in slot 3 of
NE5.
– The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
– The E1 services occupy the twenty-third to thirty-eighth VC-12 timeslots on the link
between the first optical port on the SL1D board in slot 1 of NE1 and the SL1D board
in slot 1 of NE3.

– The E1 services occupy the first to sixteenth VC-12 timeslots on the link between the
IF1 board in slot 3 of NE3 and the IF1 board in slot 3 of NE4.
– The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
– The E1 services occupy the thirty-ninth to fifty-fourth VC-12 timeslots on the link
between the first optical port on the SL1D board in slot 1 of NE1 and the IF1 board in
slot 3 of NE2.
Linear MSP
In this configuration example, no extra services need to be transmitted. Hence, the single-ended
non-revertive 1+1 linear MSP is configured to protect the optical transmission line between NE1
and BSC. Table 4-8 provides the related planning information.
Table 4-8 Linear MSP
Parameter NE1
Protection Type 1+1 Linear MSP
Switching Mode Single-Ended Switching
Revertive Mode Non-Revertive
SD Enable Enabled (default value)
Protocol Type New Protocol (default value)
West Working Unit 1-SL1D-1
West Protection Unit 1-SL1D-2
NOTE
Unless otherwise specified, SD Enable, Protocol Type take the default values.

Procedure
Step 1 See A.9.1 Configuring Linear MSP and configure 1+1 linear MSP.
Parameter Value
NE1

Parameter Value
NE1
WTR Time(s) 600
SD Enable Enabled
Protocol Type New Protocol
Mapped Board l West Working Unit: 1-SL1D-1

l West Protection Unit: 1-SL1D-2
Step 2 See A.10.1 Creating the Cross-Connections of Point-to-Point Services and create the point-
to-point service cross-connections.
l The values for the related parameters of NE1 are provided as follows.
Parameter Value
NE1
Level VC-12
Direction Bidirectional
Source Slot 1-SL1D-1
Source VC4 VC4-1
Source Timeslot Range(e.g.1,3-6) 1-54
Sink Slot 3-IF1-1
Sink VC4 VC4-1
Sink Timeslot Range(e.g.1,3-6) 1-54
Parameter Value
NE2
Level VC-12 VC-12
Direction Bidirectional Bidirectional
Source Slot 3-IF1-1 3-IF1-1
Source VC4 VC4-1 VC4-1
Source Timeslot Range 1-38 39-54

(e.g.1,3-6)

Parameter Value
NE2
Sink Slot 1-SL1D-1 2-SP3S
Sink VC4 VC4-1 -
Sink Timeslot Range(e.g. 1-38 1-16

1,3-6)
Parameter Value
NE3
Level VC-12 VC-12
Source Slot 1-SL1D-1 1-SL1D-1

(e.g.1,3-6)
Sink Slot 4-IF1-1 3-IF1-1
Sink VC4 VC4-1 VC4-1

1,3-6)
Parameter Value
NE4
Level VC-12
Source Slot 3-IF1-1
Source VC4 VC4-1
Sink Slot 2-SP3S
Sink VC4 -

Parameter Value
NE5
Level VC-12 VC-12
Source Slot 4-IF1-1 4-IF1-1

(e.g.1,3-6)
Sink Slot 3-IF1-1 2-SP3S
Sink VC4 VC4-1 -

1,3-6)
Parameter Value
NE6
Level VC-12
Source Slot 3-IF1-1
Source VC4 VC4-1
Sink Slot 2-SP3S
Sink VC4 -
Step 3 See A.10.11 Testing the E1 Service Through PRBS and test the E1 services.
Test two E1 services on each BTS. The test results should show that the E1 services contain no
bit errors.
----End

4.4 Configuration Example (TDM Services on a TDM Radio

Ring Network)


Based on 3.4 Configuration Example (Radio Links on the TDM Radio Ring Network),
configure the TDM services according to the service requirements. To ensure reliable
transmission of the services between the BTSs and the BSC, SNCP is configured to provide
protection for TDM services on the ring network. See Figure 4-10.
Figure 4-10 Networking diagram (TDM services on a TDM radio ring network)
16xE1
NE1
BSC
4xE1
BTS1 4xE1
4xE1 NE2 NE4 BTS4
BTS2
4xE1
NE3
BTS3


Between NE1 and the BSC 2-SP3S (1-16) Configure the ports to access
services from the BSC.
Between NE1 and NE2 4-IF1 (main IF board of a 1+1 Configure the ports as east
HSB protection group) ports.
6-IF1 (standby IF board of a

1+1 HSB protection group)
Between NE1 and NE4 3-IF1 (main IF board of a 1+1 Configure the ports as west


Between NE2 and NE1 3-IF1 (main IF board of a 1+1 Configure the ports as west

Between NE2 and NE3 4-IF1 Configure this port as an east

port.

services from BTS3.
Between NE3 and NE2 3-IF1 Configure this port as a west

port.
Between NE3 and NE4 4-IF1 Configure this port as an east

port.

services from BTS4.
Between NE4 and NE1 4-IF1 (main IF board of a 1+1 Configure the ports as east

Between NE4 and NE3 3-IF1 Configure this port as a west

port.


Figure 4-11 shows the timeslots that are allocated for the TDM services according to the service
Figure 4-11 Timeslot allocation diagram (TDM service on the TDM radio ring network)
Station NE2
NE1 NE3 NE4 NE1
Timeslot 4-IF1 3-IF1 4-IF1 3-IF1 4-IF1 3-IF1 4-IF1 3-IF1
VC12: 1-8 VC12: 1-8
2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8
VC12: 9-12 VC12: 9-12
VC4-1 2-SP3S:9-12 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:9-12
VC12: 13-16 VC12: 13-16
2-SP3S:13-16 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:13-16
Pass through (SNCP w orking path)

Pass through (SNCP protection path)
Add/Drop (SNCP w orking path)
Add/Drop (SNCP protection path)
in slot 2 of NE2.
in slot 2 of NE1.
– The E1 services occupy the first to eighth VC-12 timeslots on the ring.

– The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 2 of NE3.
– The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S
– The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.
in slot 2 of NE4.
– The E1 services are added to or dropped from the thirteenth to sixteenth ports on the
SP3S board in slot 2 of NE1.
– The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
SNCP
Table 4-13 provides the information about SNCP.
Table 4-13 SNCP
Parameter NE1
Working Source See the timeslot allocation diagram.
Protection Source See the timeslot allocation diagram.
Revertive Mode Revertive
WTR Time 600s (default value)
Hold-Off Time 0 (default value)
Switching Condition Necessary conditions for an SNCP switching (default

values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.

Procedure
Step 1 See A.10.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.

Parameter Value
NE1
Level VC-12 VC-12
Hold-off Time(100ms) 0 0
Revertive Mode Revertive Revertive
WTR Time(s) 600 600
Source Slot 4-IF1-1 (working service) 3-IF1-1 (working service)

3-IF1-1 (protection service) 4-IF1-1 (protection service)
Source VC4 VC4-1 (working service) VC4-1 (working service)

VC4-1 (protection service) VC4-1 (protection service)

(e.g.1,3-6)
Sink Slot 2-SP3S 2-SP3S
Sink VC4 - -

1,3-6)
Parameter Value
NE2
Level VC-12
Hold-off Time(100ms) 0
WTR Time(s) 600
Source Slot 3-IF1-1 (working service)

4-IF1-1 (protection service)
Source VC4 VC4-1 (working service)

VC4-1 (protection service)
Sink Slot 2-SP3S
Sink VC4 -

Parameter Value
NE2
Parameter Value
NE3
Level VC-12
WTR Time(s) 600


Sink Slot 2-SP3S
Sink VC4 -
Parameter Value
NE4
Level VC-12
WTR Time(s) 600


Parameter Value
NE4

Sink Slot 2-SP3S
Sink VC4 -
Step 2 See A.10.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE2, NE3, and NE4.
Parameter Value
NE2
Level VC-12
Source Slot 3-IF1-1
Source VC4 VC4-1
Sink Slot 4-IF1-1
Sink VC4 VC4-1
Parameter Value
NE3
Level VC-12
Source Slot 3-IF1-1
Source VC4 VC4-1
Source Timeslot Range(e.g.1,3-6) 1-8,13-16
Sink Slot 4-IF1-1

Parameter Value
NE3
Sink VC4 VC4-1
Sink Timeslot Range(e.g.1,3-6) 1-8,13-16
Parameter Value
NE4
Level VC-12
Source Slot 3-IF1
Source VC4 VC4-1
Sink Slot 4-IF1-1
Sink VC4 VC4-1
bit errors.
----End
4.5 Configuration Example (TDM Services on a Hybrid

Radio Chain Network)

data.


Based on 3.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure the TDM services according to the following network planning information (as shown
in Figure 4-12):
l To ensure reliable transmission of the services between NE1 and the BSC, linear MSP is
configured for the optical transmission line.
l Services are transferred between NE2 and NE3 through E1 channels.
Number of 4 2 2 2 2
high-
priority E1
services
Number of 0 0 2 2 2
low-priority
E1 services
Figure 4-12 Networking diagram (TDM services on a Hybrid radio chain network)
2E1
BTS2
E1 STM-1
4E1 NE4
BTS3
4E1
NE3 NE2 NE1 BSC
4E1 BTS1
4E1
NE6 NE5
BTS5 BTS4
Between NE1 and the BSC 2-SL1D-1 (working port) Configure the ports as a 1+1
linear MSP group.
2-SL1D-2 (protection port)


Between NE2 and BTS1 2-SP3D (15-18) Configure the ports to access
services from BTS1.
Between NE2 and NE3 2-SP3D (1-14) Configure the ports to


Between NE3 and NE2 2-SP3S (1-14) Configure the ports to




services from BTS4.

signals.

services from BTS5.

signals.

data.

Figure 4-13 shows the timeslots that are allocated for the TDM services according to the network

Figure 4-13 Timeslot allocation diagram (Hybrid services on the Hybrid chain radio network)
Links-1: NE1 - NE2 - NE3 -NE5
Station
BSC NE1 NE2 NE3 NE5 NE6
Timeslot 2-SL1D 3-IFU2 3-IFU2 2-SP3D 2-SP3S 4-IFU2 4-IFU2 3-IFU2 3-IFU2
VC12: 1-2
VC12: 3-4 2-SP3S:1-2
2-SP3S:3-4
VC12: 5-6
2-SP3S:1-2
VC12: 7-8
2-SP3S:3-4
VC12: 9-12
VC4-1
VC12: 13-14
VC12: 15-18
2-SP3D:15-18
Links-2: NE3-NE4
Station NE3 NE4
Timeslot 2-SP3S 3-IFU2 3-IFU2
VC12: 9-12 VC12: 1-4
VC4-1
VC12: 13-14 2-SP3S:1-4
VC12: 5-6
2-SP3S:5-6
/ Pass through(low/high)
/ Add/Drop(low/high)
/ Foward(low/high)
l E1 services of NE6:
in slot 2 of NE6. Ports 1 and 2 add and drop high-priority services and ports 3 and 4
add and drop low-priority services.
– The E1 services occupy the first to fourth VC-12 timeslots on the link between the first
optical port on the SL1D board in slot 2 of NE1 and the IFU2 board in slot 3 of NE6.
Ports 1 and 2 transmit high-priority services and ports 3 and 4 transmit low-priority
services.
in slot 2 of NE5. Ports 1 and 2 add and drop high-priority services and ports 3 and 4
add and drop low-priority services.
– The E1 services occupy the fifth to eighth VC-12 timeslots on the link between the first
optical port on the SL1D board in slot 2 of NE1 and the IFU2 board in slot 4 of NE5.
Ports 5 and 6 transmit high-priority services and ports 7 and 8 transmit low-priority
services.
– The E1 services are added to or dropped from the first to sixth ports on the SP3S board
in slot 2 of NE4. Ports 1 to 4 add and drop high-priority services and ports 5 and 6 add
and drop low-priority services.

– The E1 services occupy the ninth to fourteenth VC-12 timeslots on the link between the
first optical port on the SL1D board in slot 2 of NE1 and the SP3S board in slot 2 of
NE3. Ports 9 to 12 transmit high-priority services and ports 13 and 14 transmit low-
priority services.
– The E1 services occupy the first to sixth VC-12 timeslots on the link between the IFU2
board in slot 3 of NE3 and the IFU2 board in slot 3 of NE4. Ports 1 to 4 transmit high-
priority services and ports 5 and 6 transmit low-priority services.
– The E1 services are added to or dropped from the fifteenth to eighteenth ports on the
– The E1 services occupy the fifteenth to eighteenth VC-12 timeslots on the link between
the first optical port on the SL1D board in slot 2 of NE1 to the IFU2 board in slot 3 of
NE2.
Linear MSP
In this configuration example, no extra services need to be transmitted. Hence, the single-ended
non-revertive 1+1 linear MSP is configured to protect the optical transmission line between NE1
and BSC. Table 4-21 provides the related planning information.
Table 4-21 Linear MSP
Parameter NE1
SD Enable Enabled (default value)
West Working Unit 2-SL1D-1
West Protection Unit 2-SL1D-2
NOTE
Unless otherwise specified, SD Enable, Protocol Type take the default values.

Procedure
Step 1 See A.9.1 Configuring Linear MSP and configure the linear MSP.
The values for the relevant parameters are provided as follows.

Parameter Value
NE1
WTR Time(s) 600
SD Enable Enabled
Protocol Type New Protocol
Mapped Board l West Working Unit: 2-SL1D-1

l West Protection Unit: 2-SL1D-2
Step 2 See A.10.1 Creating the Cross-Connections of Point-to-Point Services and create point-to-
point service cross-connections.
Parameter Value
NE1
Level VC12 VC12
Source Timeslot Range 1-2,5-6,9-12,15-18 3-4,7-8,13-14

(e.g.1,3-6)
Sink Slot 3-IFU2-1 3-IFU2-1
Sink Timeslot Range(e.g. 1-2,5-6,9-12,15-18 3-4,7-8,13-14

1,3-6)
E1 Priority High Low
Parameter Value
NE2
Level VC12 VC12

Parameter Value
NE2
Source Slot 3-IFU2-1 3-IFU2-1
Source Timeslot Range 1-2,5-6,9-12,15-18 3-4,7-8,13-14

(e.g.1,3-6)
Sink Slot 2-SP3D 2-SP3D
Sink VC4 - -
Sink Timeslot Range(e.g. 1-2,5-6,9-12,15-18 3-4,7-8,13-14

1,3-6)
Parameter Value
NE3
Level VC12 VC12 VC12 VC12
Direction Bidirectional Bidirectional Bidirectional Bidirectional
Source Slot 2-SP3S 2-SP3S 2-SP3S 2-SP3S
Source VC4 - - - -
Source 1-2,5-6 9-12 3-4,7-8 13-14

Timeslot
Range(e.g.
1,3-6)
Sink Slot 4-IFU2-1 3-IFU2-1 4-IFU2-1 3-IFU2-1
Sink VC4 VC4-1 VC4-1 VC4-1 VC4-1
Sink Timeslot 1-2,5-6 1-4 3-4,7-8 5-6

Range(e.g.
1,3-6)
E1 Priority High High Low Low
Parameter Value
NE4
Level VC12 VC12

Parameter Value
NE4

(e.g.1,3-6)
Sink VC4 - -

1,3-6)
Parameter Value
NE5
Level VC12 VC12 VC12 VC12
Direction Bidirectional Bidirectional Bidirectional Bidirectional
Source Slot 4-IFU2-1 4-IFU2-1 4-IFU2-1 4-IFU2-1
Source VC4 VC4-1 VC4-1 VC4-1 VC4-1
Source 1-2 5-6 3-4 7-8

Timeslot
Range(e.g.
1,3-6)
Sink Slot 3-IFU2-1 2-SP3S 3-IFU2-1 2-SP3S
Sink VC4 VC4-1 - VC4-1 -
Sink Timeslot 1-2 1-2 3-4 3-4

Range(e.g.
1,3-6)
E1 Priority High High Low Low

Parameter Value
NE6
Level VC12 VC12

(e.g.1,3-6)
Sink VC4 - -

1,3-6)
bit errors.
----End
4.6 Configuration Example (TDM Services on a Hybrid

Radio Ring Network)

data.

configure the TDM services according to the service requirements. To ensure reliable
transmission of the services between the BTSs and the BSC, SNCP is configured to provide

protection for TDM services on the ring network. See Figure 4-14. The service capacity accessed
by each BTS is provided in Table 4-22.
Figure 4-14 Networking diagram (TDM services on a Hybrid radio ring network)
16xE1
NE1
BSC
4xE1
BTS1 4xE1
4xE1 NE2 NE4 BTS4
BTS2
4xE1
NE3
BTS3
Between NE1 and the BSC 2-SP3S (1-16) Configure the ports to access
services from the BSC.
Between NE1 and NE2 4-IFU2 (main IF board of a 1 Configure the ports as east
+1 HSB protection group) ports.
6-IFU2 (standby IF board of

a 1+1 HSB protection group)
Between NE1 and NE4 3-IFU2 (main IF board of a 1 Configure the ports as west


Between NE2 and NE1 3-IFU2 (main IF board of a 1 Configure the ports as west

Between NE2 and NE3 4-IFU2 Configure this port as an east

port.
services from BTS3.
Between NE3 and NE2 3-IFU2 Configure this port as a west

port.
Between NE3 and NE4 4-IFU2 Configure this port as an east

port.
services from BTS4.
Between NE4 and NE1 4-IFU2 (main IF board of a 1 Configure the ports as east

Between NE4 and NE3 3-IFU2 Configure this port as a west

port.

data.


Figure 4-15 shows the timeslots that are allocated for the TDM services according to the network
Figure 4-15 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)
Station
NE1 NE2 NE3 NE4 NE1
Timeslot 4-IFU2 3-IFU2 4-IFU2 3-IFU2 4-IFU2 3-IFU2 4-IFU2 3-IFU2
VC12: 1-8 VC12: 1-8
2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8
VC12: 9-12 VC12: 9-12
VC4-1 2-SP3S:9-12 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:9-12
VC12: 13-16 VC12: 13-16
2-SP3S:13-16 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:13-16
Pass through (SNCP w orking path)

Pass through (SNCP protection path)
Add/Drop (SNCP w orking path)
Add/Drop (SNCP protection path)
in slot 2 of NE2.
in slot 2 of NE1.
– The E1 services occupy the first to eighth VC-12 timeslots on the ring.
in slot 2 of NE3.
– The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S
– The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.
in slot 2 of NE4.
– The E1 services are added to or dropped from the thirteenth to sixteenth ports on the
– The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
SNCP
Table 4-27 provides the information about SNCP.

Table 4-27 SNCP
Parameter NE1
Working Source See the timeslot allocation diagram.
Protection Source See the timeslot allocation diagram.
WTR Time 600s (default value)
Hold-Off Time 0 (default value)
Switching Condition Necessary conditions for an SNCP switching (default

values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.

Procedure
Step 1 See A.10.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.
Parameter Value
NE1
Level VC-12 VC-12
Hold-off Time(100ms) 0 0
Revertive Mode Revertive Revertive
WTR Time(s) 600 600
Source Slot 4-IFU2-1 (working service) 3-IFU2-1 (working service)

3-IFU2-1 (protection 4-IFU2-1 (protection
service) service)
Source VC4 VC4-1 (working service) VC4-1 (working service)

VC4-1 (protection service) VC4-1 (protection service)

(e.g.1,3-6)

Parameter Value
NE1
Sink VC4 - -

1,3-6)
Parameter Value
NE2
Level VC-12
WTR Time(s) 600
Source Slot 3-IFU2-1 (working service)

4-IFU2-1 (protection service)

Sink Slot 2-SP3S
Sink VC4 -
Parameter Value
NE3
Level VC-12
WTR Time(s) 600

Parameter Value
NE3


Sink Slot 2-SP3S
Sink VC4 -
Parameter Value
NE4
Level VC-12
WTR Time(s) 600


Sink Slot 2-SP3S
Sink VC4 -
Step 2 See A.10.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE2, NE3, and NE4.

Parameter Value
NE2
Level VC-12
Source Slot 3-IFU2-1
Source VC4 VC4-1
Sink Slot 4-IFU2-1
Sink VC4 VC4-1
E1 Priority -
Parameter Value
NE3
Level VC-12
Source VC4 VC4-1
Source Timeslot Range(e.g.1,3-6) 1-8,13-16
Sink Slot 4-IFU2-1
Sink VC4 VC4-1
Sink Timeslot Range(e.g.1,3-6) 1-8,13-16
E1 Priority -
Parameter Value
NE4
Level VC-12

Parameter Value
NE4
Source VC4 VC4-1
Sink Slot 4-IFU2-1
Sink VC4 VC4-1
E1 Priority -
bit errors.
----End

Configuration Guide (U2000) 5 Configuring Packet-Based Ethernet Services
5 Configuring Packet-Based Ethernet Services
About This Chapter
Ethernet services on the packet plane are classified into E-Line services and E-LAN services.
5.1 Basic Concepts

Before configuring the Ethernet services, you need to be familiar with the basic concepts.
The service configuration procedure differs according to the specific service type.
5.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)
This section considers a point-to-point transparently transmitted E-Line service as an example
to describe how to configure the Ethernet service according to the network planning information.
5.4 Configuration Example (VLAN-Based E-Line Service)
This section considers a VLAN-based E-line service as an example to describe how to configure
the Ethernet service according to the network planning information.
5.5 Configuration Example (QinQ-Based E-Line Service)
This section considers a QinQ-based E-line service as an example to describe how to configure
5.6 Configuration Example (802.1d-Bridge-Based E-LAN Service)
This section considers an 802.1d-bridge-based E-LAN service as an example to describe how
to configure the Ethernet service according to the network planning information.
5.7 Configuration Example (802.1q-Bridge-Based E-LAN Service)
This section considers an 802.1q-bridge-based E-LAN service as an example to describe how
5.8 Configuration Example (802.1ad-Bridge-Based E-LAN Service)
This section considers an 802.1ad-bridge-based E-LAN service as an example to describe how
5.9 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)
This section describes how to configure a radio network that transmits E-Line services and E-
LAN services at the same time according to the network planning information.

5 Configuring Packet-Based Ethernet Services Configuration Guide (U2000)
5.1 Basic Concepts

Before configuring the Ethernet services, you need to be familiar with the basic concepts.
5.1.1 IF_ETH Port

When Ethernet services need to be transmitted over Hybrid radio, you need to configure the
Ethernet services between the FE/GE port on the Ethernet port board and the IF_ETH port on
the Hybrid IF board.
5.1.2 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
5.1.3 Flow Control Function
When the equipment fails to handle the flow received at the port due to poor data processing/
transferring capability, congestion occurs on the line. To reduce the number of discarded packets
caused by buffer overflow, proper flow control measures must be taken.
5.1.4 Ethernet Service Types Based on the Packet Plane
Based on the packet plane, Ethernet services can be classified into six types.
5.1.5 Typical Networking of Ethernet Services on a Mobile Carrier Network
Generally, a mobile carrier network adopts three basic networking modes to implement
transmission of Ethernet services.
5.1.6 Managing a MAC Address Table
The entries in a MAC address table indicate the corresponding relationship between MAC
addresses and ports. A MAC address table contains the following entries: dynamic entry, static
entry, and blacklist entry.
5.1.7 VLAN Forwarding Table
Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If it is required to
change the VLAN IDs, you need to configure a VLAN forwarding table.
5.1.8 Split Horizon Group
To better isolate services that are converged and to prevent broadcast storm resulting from a
service loop, you can configure a split horizon group for the E-LAN services at the specified
nodes. The logical ports in one split horizon group cannot forward packets to each other.
5.1.9 Protection for Ethernet Services Based on the Packet Plane
Based on the packet plane, the OptiX RTN 950 supports three protection modes for Ethernet
services, namely, Ethernet ring protection switching (ERPS), link aggregation (LAG), and
multiple spanning tree protocol (MSTP).
5.1.10 QoS Based on the Packet Plane
The quality of service (QoS) refers to the ability of a communication network to ensure the
expected service quality in the aspects of the 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 requirements of an expected service class. The OptiX RTN 950 supports
the following QoS functions, namely, differentiated service (DiffServ), flow classification,
CAR, traffic shaping, and queue scheduling.

5.1.1 IF_ETH Port

When Ethernet services need to be transmitted over Hybrid radio, you need to configure the
Ethernet services between the FE/GE port on the Ethernet port board and the IF_ETH port on
the Hybrid IF board.
The IF_ETH port is an internal Ethernet port on the Hybrid IF board. In the transmit direction
of Hybrid radio, the Ethernet services transmitted to the MUX/DEMUX unit of the Hybrid IF
board through the IF_ETH port and are then mapped into the Hybrid microwave frames. In the
receive direction of Hybrid radio, the Ethernet services are demapped from the Hybrid
microwave frames and then transmitted to the packet switching unit through the IF_ETH port.
The main differences between the IF_ETH port and the GE/FE port are as follows:
l The IF_ETH port is an internal Ethernet port. It transmits and receives MAC frames and
does not have PHY-layer functions.
l The bandwidth over the IF_ETH port is equal to the Ethernet service bandwidth that the
Hybrid radio supports. Hence, when the AM function is enabled in the case of Hybrid radio,
the bandwidth over the IF_ETH port changes according to the modulation scheme.
5.1.2 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
Auto-Negotiation Function of FE Electrical Ports

In the case of FE electrical ports, there are four common working modes: 10M half-duplex, 10M
full-duplex, 100M half-duplex, and 100M full-duplex. If the working mode of the local FE
electrical port does not match the working mode of the opposite FE electrical port, the two ports
cannot communicate with each other. With the auto-negotiation function, however, the two ports
can communicate with each other. The auto-negotiation function uses fast link pulses and normal
link pulses to transfer the negotiation information of the working mode so that the working mode
of the local FE electrical port matches the working mode of the opposite FE electrical port.
Table 5-1 lists the FE auto-negotiation rules.
Table 5-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adopts
the auto-negotiation mode)
Working Mode of the Opposite FE Auto-Negotiation Result

Electrical Port
Auto-negotiation 100M full-duplex
10M half-duplex 10M half-duplex
10M full-duplex 10M half-duplex

NOTE
As provided in Table 5-1, when the working mode of the opposite FE electrical port is 10M full-duplex or 100M
full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the FE
electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the opposite
FE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of the local FE
electrical port to 10M full-duplex or 100M full-duplex.
When the FE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate the flow control function through the auto-negotiation function.
Auto-Negotiation Function of GE Electrical Ports

In the case of GE electrical ports, there are five working modes: 10M half-duplex, 10M full-
duplex, 100M half-duplex, 100M full-duplex, and 1000M full-duplex. The auto-negotiation
function of GE electrical ports is similar to the auto-negotiation function of FE electrical ports.
Table 5-2 lists the auto-negotiation rules of GE electrical ports.
Table 5-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adopts
the auto-negotiation mode)
Working Mode of the Opposite GE Auto-Negotiation Result

Electrical Port
Auto-negotiation (GE electrical port) 1000M full-duplex
Auto-negotiation (FE electrical port) 100M full-duplex
1000M full-duplex 1000M full-duplex
NOTE
As provided in Table 5-2, when the working mode of the opposite GE electrical port is 10M full-duplex or
100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the
GE electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the
opposite GE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of the
local GE electrical port to 10M full-duplex or 100M full-duplex.
When the GE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate the flow control function through the auto-negotiation function.
Auto-Negotiation Function of GE Optical Ports

GE optical ports support only the 1000M full-duplex working mode. The auto-negotiation
function of GE optical ports is used only for negotiating the flow control function.

5.1.3 Flow Control Function

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

When the Ethernet port works in the auto-negotiation mode, you can adopt the auto-negotiation
flow control function. The auto-negotiation flow control modes include the following:
l Asymmetric PAUSE toward the link partner

The port can transmit PAUSE frames in the case of congestion but cannot process the
received PAUSE frames.
l Symmetric PAUSE
The port can transmit PAUSE frames and process the received PAUSE frames.
l Both asymmetric and symmetric PAUSE
The port has the following capabilities:
– Transmits and processes PAUSE frames.
– Transmits PAUSE frames but cannot process the received PAUSE frames.
– Processes the received PAUSE frames but cannot transmit PAUSE frames.
l Disabled
The port does not transmit or process PAUSE frames.
NOTE
The OptiX RTN 950 supports only two auto-negotiation flow control modes, namely, disabled mode and
symmetric PAUSE mode.
Non-Auto-Negotiation Flow Control

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

l Disabled
The port does not transmit or process PAUSE frames.
NOTE
The OptiX RTN 950 supports only two non-auto-negotiation flow control modes, namely, disabled mode and
symmetric mode.
5.1.4 Ethernet Service Types Based on the Packet Plane

Based on the packet plane, Ethernet services can be classified into six types.
5.1.4.1 Point-to-Point Transparently Transmitted E-Line Service

The point-to-point transparently transmitted E-Line service are the basic E-Line model. Point-
to-point transmission does not involve service bandwidth sharing, service isolation, or service
distinguishing; instead, Ethernet services are transparently transmitted between two service
access points.
5.1.4.2 VLAN-based E-Line Services
VLANs can be used to separate E-Line services. With the VLAN technology, multiple E-Line
services can share one physical channel. These services are VLAN-based E-Line services.
5.1.4.3 QinQ-Based E-Line Services
S-VLAN tags can be used to isolate E-Line services. Therefore, multiple E-Line services can
share one physical channel. These services are QinQ-based E-Line services.
5.1.4.4 E-LAN Services Based on the IEEE 802.1d Bridge
In the case of E-LAN services, packets can be forwarded only based on the MAC address table.
This type of E-LAN services is called the E-LAN service based on the IEEE 802.1d bridge.
5.1.4.5 E-LAN Services Based on the IEEE 802.1q Bridge
E-LAN services can be separated by setting VLANs. In this case, a bridge is divided into multiple
sub-switching domains. Therefore, the E-LAN services separated by setting VLANs are E-LAN
services based on the IEEE 802.1q bridge.
5.1.4.6 E-LAN Services Based on the IEEE 802.1ad Bridge
S-VLAN tags can be used to isolate E-LAN services. Therefore, a bridge is divided into multiple
independent sub-switching domains. These services are E-LAN services based on the IEEE
802.1ad bridge.
5.1.4.1 Point-to-Point Transparently Transmitted E-Line Service

The point-to-point transparently transmitted E-Line service are the basic E-Line model. Point-
to-point transmission does not involve service bandwidth sharing, service isolation, or service
distinguishing; instead, Ethernet services are transparently transmitted between two service
access points.
Service Model
Table 5-3 describes the point-to-point transparently transmitted E-Line service model.

Table 5-3 Point-to-point transparently transmitted E-Line service model

Encapsulation Type Service Direction Traffic Flow Description
Null (source) UNI-UNI PORT (source) The source port

Null (sink) PORT (sink) transparently transmits all
the received Ethernet
frames to the sink port.
Typical Application
Figure 5-1 shows the typical application scenarios of the point-to-point transparently transmitted
E-Line service model.
Ethernet service 1 and Ethernet service 2 gain access to NE1 through port 1 and port 2
respectively, regardless of whether the two Ethernet services do not carry any VLAN ID or carry
unknown VLAN IDs. Port 1 and port 2 transparently transmit Ethernet service 1 and Ethernet
service 2 to port 3 and port 4, respectively. Port 3 and port 4 then transmit Ethernet service 1
and Ethernet service 2 to NE2.
Service processing on NE2 is the same as on NE1.
Figure 5-1 Typical application of the service model

NE 1 NE 2
Port 1 Port 3 Port 3 Port 1
E-Line E-Line
Service 1 Transmission Service 1
Network
E-Line E-Line
Service 2 Service 2
5.1.4.2 VLAN-based E-Line Services

services can share one physical channel. These services are VLAN-based E-Line services.
Models of Services
Table 5-4 shows the models of VLAN-based E-Line services.

Table 5-4 Models of VLAN-based E-Line services

Model of Service Flow of Service Direction of Encapsulation Description of
Service Mode of Port Service
Model 1 PORT (source) UNI-UNI 802.1Q (source) The source port

PORT (sink) 802.1Q (sink) processes the
incoming Ethernet
frames based on its
TAG attribute, and
then sends the
processed Ethernet
frames to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.
Model 2 PORT+VLAN UNI-UNI 802.1Q (source) The source port

(source) 802.1Q (sink) processes the
PORT+VLAN incoming Ethernet
(sink) frames based on its
TAG attribute, and
then sends the
Ethernet frames
with a specific
VLAN ID to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.
Typical Applications
Figure 5-2 shows the typical application of service model 1.
Service 1 and Service 2 carry unknown VLAN IDs, and the two Ethernet services are accessed
to NE1 through Port 1 and Port 2 respectively. Port 1 and Port 2 process the incoming packets
based on their own TAG attributes. Then, Port 1 and Port 2 send Service 1 and Service 2 to Port
3 and Port 4 respectively. Port 3 and Port 4 process the incoming packets based on their own
TAG attributes. Then, Port 3 and Port 4 send Service 1 and Service 2 to NE2.
NE2 processes Service 1 and Service 2 in the same manner as NE1.

Figure 5-2 Typical application of service model 1

NE 1 NE 2
E-Line E-Line
Network
E-Line E-Line
Service 2 Service 2
NOTE
The application of service model 1 is similar to point-to-point transparent transmission of Ethernet services.
The difference is that ports need to process packets based on their TAG attributes in the application of
service model 1.
Figure 5-3 shows the typical application of service model 2. Service 1 and Service 2 carry
different VLAN IDs. Therefore, after the two Ethernet services are accessed to NE1 through
Port 1 and Port 2 respectively, they can share the same transmission channel at Port 3.
On NE1, Port 1 and Port 2 process the incoming packets based on their own TAG attributes.
Then, Port 1 and Port 2 send Service 1 and Service 2 to Port 3. Port 3 processes the incoming
packets based on its own TAG attribute, and then sends Service 1 and Service 2 to NE2. Due to
the different VLAN IDs, Service 1 and Service 2 can be transmitted through Port 3 at the same
time.

NE 1 NE 2
Port 1 Port 1
Service 1 E-Line Service 1
Port 3 Transmission Port 3 E-Line
VLAN ID: 100 Network VLAN ID: 100
Service 2 e Service 1 Service 1 E-Lin Service 2
VLAN ID: 200 E-Lin e
Port 2 VLAN ID: 100 VLAN ID: 100 Port 2 VLAN ID: 200
Service 2 Service 2
VLAN ID: 200 VLAN ID: 200
5.1.4.3 QinQ-Based E-Line Services

S-VLAN tags can be used to isolate E-Line services. Therefore, multiple E-Line services can
share one physical channel. These services are QinQ-based E-Line services.
Model of Service
Table 5-5 shows the models of QinQ-based E-Line services.

Table 5-5 Models of QinQ-based E-Line Services

Model of Service Flow of Service Direction Encapsulation Description of
Mode of a Port Service
Model 1 PORT (source) UNI-NNI Null (source) The source port adds
QinQ link (sink) QinQ (sink) the S-VLAN tag that
corresponds to the
QinQ link to all the
Ethernet frames, and
then transmits the
Ethernet frames to
the sink port where
the QinQ link is
configured.
Model 2 PORT (source) UNI-NNI 802.1Q (source)a The source port

QinQ link (sink) accesses only the
QinQ (sink)
Ethernet frames that
carry C-VLAN tags.
It adds the S-VLAN
tag that corresponds
to the QinQ link to
all the Ethernet
frames, and then
transmits the
Ethernet frames to
the sink port where
the QinQ link is
configured.
Model 3 PORT+C-VLAN UNI-NNI 802.1Q (source)a The source port adds

(source) the S-VLAN tag that
QinQ (sink)
QinQ link (sink) corresponds to the
QinQ link to all the
carry specific C-
VLAN tags, and
then transmits the
Ethernet frames to
the sink port where
the QinQ link is
configured.

Model of Service Flow of Service Direction Encapsulation Description of

Mode of a Port Service
Model 4 QinQ link (source) NNI-NNI QinQ (sink) The source port
QinQ link (sink) QinQ (sink) transmits the
carry the S-VLAN
tag to the sink port
where the sink QinQ
link is configured.
The S-VLAN tag
carried in the
Ethernet frames
corresponds to the
source QinQ link. If
the source and sink
QinQ links
correspond to
different S-VLAN
tags, the S-VLAN
tags carried in the
Ethernet frames are
exchanged.
NOTE
a: Set TAG to Tag Aware.
Service 1 and Service 2 include tagged frames and untagged frames. Service 1 is accessed to
NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the
corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to
Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1
and Service 2 to NE2.

NE 1 NE 2
Port 1 Port 1
E-Line
Service 1 Port 3 Transmission Port 3 E-Line Service 1
Network
Service 2 e E-Lin Service 2
E-Lin e
Port 2 Port 2
Strip S-VLAN Label Add S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
Data( 1) S-VLAN(300) Data(1) S-VLAN(300) Data(1) Data(1)
Data(2) S-VLAN(400) Data(2) S-VLAN(400) Data(2) Data(2)


Service 1 and Service 2 carry different unknown C-VLAN tags. Service 1 is accessed to NE1
through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the corresponding
S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then,
Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to
NE2.

Strip S-VLAN Label Add S-VLAN Label
C-VLAN Data( 1) S-VLAN(300) C-VLAN Data(1)
C-VLAN Data(2) S-VLAN(400) C-VLAN Data(2)
NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
Port 3 Transmission Port 3 E-Line Service 1
Unknown CVLAN Network Unknown CVLAN
Unknown CVLAN E-Lin e Unknown CVLAN
Port 2 Port 2
Add S-VLAN Label Strip S-VLAN Label
S-VLAN(300) C-VLAN Data(1) C-VLAN Data( 1)
S-VLAN(400) C-VLAN Data(2) C-VLAN Data(2)

Service 1 and Service 2 carry different C-VLAN tags. Service 1 is accessed to NE1 through Port
1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the corresponding S-VLAN tag
to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and
Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2.

C-VLAN(100) Data( 1) S-VLAN(300) C-VLAN(100) Data(1)
C-VLAN(200) Data(2) S-VLAN(400) C-VLAN(200) Data(2)
NE 1 NE 2
Port 1 Port 1
Service 1 E-Line Service 1
Port 3 Transmission Port 3 E-Line
VLAN ID: 200 E-Lin e
Port 2 Port 2 VLAN ID: 200
S-VLAN(300) C-VLAN(100) Data(1) C-VLAN(100) Data( 1)
S-VLAN(400) C-VLAN(200) Data(2) C-VLAN(200) Data(2)

Service 1 and Service 2 carry a same S-VLAN tag. Service 1 is accessed to NE1 through Port
1, and Service 2 is accessed to NE1 through Port 2. Port 1 changes the S-VLAN tag carried in
Service 1 and Port 2 changes the S-VLAN tag carried in Service 2 so that the S-VLAN tags
carried in Service 1 and Service 2 are different. Port 3 transmits Service 1 and Service 2 to NE2.

Switching S-VLAN Label
S-VLAN(100) Data( 1) S-VLAN(300) Data(1)
S-VLAN(100) Data(2) S-VLAN(400) Data(2)
NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
S-VLAN ID: 100 Network S-VLAN ID: 100
S-VLAN ID: 100 E-Lin e
Port 2 Port 2 S-VLAN ID: 100
5.1.4.4 E-LAN Services Based on the IEEE 802.1d Bridge

In the case of E-LAN services, packets can be forwarded only based on the MAC address table.
This type of E-LAN services is called the E-LAN service based on the IEEE 802.1d bridge.
Model of Service
Table 5-6 shows the model of E-LAN services based on the IEEE 802.1d bridge.
Table 5-6 Model of E-LAN services based on the IEEE 802.1d bridge
Type of Tag Attribute Encapsulation Type of Learning Sub-

Service Mode of Port Logical Port Mode Switching
Domain
E-LAN services Tag- Null PORT SVL No division of

based on the Transparent sub-switching
IEEE 802.1d domains
bridge
Typical Application
Figure 5-8 shows the typical application of the model of service. The transmission network
needs to carry the A services accessed from NE2 and NE3. The two A services are converged
at the convergence node NE1. The services need not be isolated. Therefore, an IEEE 802.1d
bridge is used at NE1 to groom services.

Figure 5-8 Model of E-LAN services based on the IEEE 802.1d bridge
NE 2
Port 2 Port 1
User A2
NE 1 Transmission
Network
Port 1 Port 2
User A1
Port 3
802.1d bridge NE 3
Transmission
Network
Port 1
User A3
Port 2
5.1.4.5 E-LAN Services Based on the IEEE 802.1q Bridge

E-LAN services can be separated by setting VLANs. In this case, a bridge is divided into multiple
sub-switching domains. Therefore, the E-LAN services separated by setting VLANs are E-LAN
services based on the IEEE 802.1q bridge.
Model of Service
Table 5-7 shows the models of E-LAN services based on the IEEE 802.1q bridge.
Table 5-7 Model of E-LAN services based on the IEEE 802.1q bridge
Type of TAG Encapsulation Type of Learning Sub-

Service Attribute Mode of Port Logical Port Mode Switching
Domain
E-LAN services C-Awared 802.1q PORT+VLAN IVL Sub-switching

based on the domains are
IEEE 802.1q divided based on
bridge VLANs.
Figure 5-9 shows the typical application of the model of E-LAN services based on the IEEE
802.1q bridge. The transport network needs to carry G and H services accessed from NE2 and
NE3. Both types of services converge on NE1. G and H services adopt different VLAN planning.
Therefore, the IEEE 802.1q bridge is used on NEs and sub-switching domains are divided based
on VLANs, differentiating and separating the two types of services.

Figure 5-9 Model of E-LAN services based on the IEEE 802.1q bridge
NE 2
VLAN 100
Port 1
User G2
Port 3
NE 1
VLAN 200
Transmission Port 2
VLAN 100
Port 1 Network User H2
User G1
Port 3
802.1q bridge
VLAN 200
Port 2 Port 4
User H1 NE 3
Transmission
VLAN 100
Network
802.1q bridge Port 1
User G3
VLAN 200
Port 3 Port 2
User H3
802.1q bridge
NOTE
You can configure 5.1.4.2 VLAN-based E-Line Services on NE2 and NE3 for accessing services.
5.1.4.6 E-LAN Services Based on the IEEE 802.1ad Bridge

S-VLAN tags can be used to isolate E-LAN services. Therefore, a bridge is divided into multiple
independent sub-switching domains. These services are E-LAN services based on the IEEE
802.1ad bridge.
Model of Service
Table 5-8 shows the models of E-LAN services based on the IEEE 802.1ad bridge.

Table 5-8 Models of E-LAN services based on the IEEE 802.1ad bridge
Type of Tag Attribute Encapsulation Type of Learning Sub-
Services Mode of Port Logical Port Mode Switching
Domain
E-LAN services S-Awared Null or 802.1q PORT (The IVL Sub-switching

based on the (UNI port) a encapsulation domains are
IEEE 802.1ad mode of the UNI divided based on
QinQ (NNI port)
bridge port is Null.) S-VLAN tags.
PORT or PORT
+C-VLAN (The
encapsulation
mode of the UNI
port is 802.1q.) a
PORT+S-
VLAN (NNI
port)
NOTE
a: When the encapsulation mode of port is 802.1q, the tag attribute must be Tag Aware.
Figure 5-10 shows the typical application of the model of service. The transmission network
needs to carry G and H services accessed from NE2 and NE3. The two types of services are
converged on NE1. Since G and H services have a same C-VLAN tag, you need to add different
S-VLAN tags to G and H services for service isolation.

Figure 5-10 Model of E-LAN services based on the IEEE 802.1ad bridge
NE 2
S-VLAN(300) C-VLAN(100) Data(G) C-VLAN(100) Data( G)
S-VLAN(400) C-VLAN(100) Data(H) C-VLAN(100) Data(H)
NE 2
SVLAN 300
Port 1
User G2
CVLAN 100
Port 3
SVLAN 400
NE 1 Port 2
Transmission User H2
SVLAN 300 Network CVLAN 100
Port 1 Port 3
User G1 802.1ad bridge
CVLAN 100
SVLAN 400
NE 3
Port 2
User H1
CVLAN 100 Port 4 SVLAN 300
Transmission
Port 1
Network
802.1ad bridge User G3
CVLAN 100
SVLAN 400
Port 3 Port 2
NE 1 User H3
CVLAN 100
C-VLAN(100) Data( G) S-VLAN(300) C-VLAN(100) Data(G) 802.1ad bridge
C-VLAN(100) Data(H) S-VLAN(400) C-VLAN(100) Data(H)

NE 3
NOTE
You can configure 5.1.4.3 QinQ-Based E-Line Services on NE2 and NE3 for service access.
5.1.5 Typical Networking of Ethernet Services on a Mobile Carrier

Network
Generally, a mobile carrier network adopts three basic networking modes to implement
transmission of Ethernet services.
5.1.5.1 Networking of VLAN-Based E-Line Services

services can share one physical channel.
5.1.5.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services
In the case of IEEE 802.1d bridge-based E-LAN service networking, data is forwarded based
on MAC addresses instead of VLAN IDs.
5.1.5.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services

In the case of IEEE 802.1q bridge-based E-LAN service networking, services are isolated by
means of VLAN IDs. That is, the IEEE 802.1q bridge is divided into multiple sub-switching
domains, which are isolated from each other.
5.1.5.4 Comparison Between the Three Networking Modes
The three networking modes differ from each other.
5.1.5.1 Networking of VLAN-Based E-Line Services

services can share one physical channel.
On the mobile carrier network shown in Figure 5-11, the VLAN IDs that received BTS services
carry are planned in a unified manner and are unique globally. The BTS services share the
Ethernet service bandwidth on the Hybrid radio network (NE1 to NE5) and are isolated from
each other by means of VLAN IDs. The BTS services are aggregated at NE1 and then transmitted
through the regional backhaul network to the BSC. Therefore, in this example, services on the
Hybrid radio network of the mobile carrier network are configured as VLAN-based E-Line
services.
Figure 5-11 Networking diagram of VLAN-based E-Line services
FE
BTS
VLAN 1 NE3
FE
NE2 Regional
BTS Hybrid microwave transmission network Backhaul Network
VLAN 2 GE
NE1 BSC
FE
BTS
VLAN 3 NE4
NE5
FE
BTS
VLAN 4
5.1.5.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services

In the case of IEEE 802.1d bridge-based E-LAN service networking, data is forwarded based
on MAC addresses instead of VLAN IDs.
As shown in Figure 5-12, the mobile carrier network need not sense whether the received BTS
services carry any VLAN IDs. Services from each BTS are aggregated at NE1 and then
transmitted through the regional backhaul network to the BSC. Therefore, in this example, the
services on the Hybrid radio network (NE1 to NE6) of the mobile carrier network are configured
as IEEE 802.1d bridge-based E-LAN services. The Hybrid radio network checks the destination
ports in the MAC address table according to the destination MAC addresses carried by the BTS
services and then forwards BTS services to the ports.

NOTE
IEEE 802.1d bridge-based E-LAN service packets are forwarded based on MAC addresses and may be broadcast
among all ports connected to the IEEE 802.1d bridge. Therefore, isolate the ports that need not communicate
with each other by adding the ports into a split horizon group.
Figure 5-12 Networking diagram of IEEE 802.1d bridge-based E-LAN services
FE
BTS
NE3
FE
NE2
Regional backhaul
BTS Hybrid microwave transmission network network GE
NE1 BSC
FE
BTS
NE5 NE4
FE
BTS NE6
Split horizon group
5.1.5.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services

In the case of IEEE 802.1q bridge-based E-LAN service networking, services are isolated by
means of VLAN IDs. That is, the IEEE 802.1q bridge is divided into multiple sub-switching
domains, which are isolated from each other.
On the mobile carrier network shown in Figure 5-13, the VLAN IDs that received BTS services
carry are planned in a unified manner and are unique within each domain. BTS services in
different domains are isolated from each other by means of VLAN IDs and BTSs in the same
domain can communicate with each other. The BTS services are aggregated at NE1 and then
transmitted through the regional backhaul network to the BSC. Therefore, in this example, the
services on the Hybrid radio network of the mobile carrier network are configured as IEEE
802.1q bridge-based E-LAN services. The Hybrid radio network checks the destination ports in
the MAC address table according to the destination MAC addresses carried by the BTS services
and then forwards BTS services to the ports.
NOTE
IEEE 802.1q bridge-based E-LAN service packets can be broadcast within each domain. Therefore, isolate the
ports that need not communicate with each other by adding the ports into a split horizon group.

Figure 5-13 Networking diagram of IEEE 802.1q bridge-based E-LAN services
FE
BTS
VLAN 1 NE3
FE
NE2 Domain 1
BTS VLAN 1 Regional backhaul
VLAN 1 network
Domain 2 GE
VLAN 2 NE1 BSC
Hybrid radio
network
FE
BTS
NE5 NE4
VLAN 2
FE
BTS
VLAN 2 NE6
Split horizon group
5.1.5.4 Comparison Between the Three Networking Modes

The three networking modes differ from each other.
Table 5-9 compares the three networking modes.

Table 5-9 Comparison between the three networking modes

Networkin Application Scenario Service Service Configurati Network
g Mode Stability Security on Scalability
Applicable Applicable Complexity
Network VLAN ID
Size Allocation
Networking This l The High l Very high l The l The

of VLAN- networking VLAN l Services configurat network is
based E-Line mode is IDs that from ion difficult to
services applicable to received different operations expand.
all network BTS BTSs are are l To add the
sizes. services isolated complex. new
carry are from each l Only VLAN ID
planned in other. point-to- after a
a unified point BTS is
manner configurat added,
and are ion is you need
unique supported to change
globally. . the E-Line
l BTS configurat
services ions on all
share the NEs
Ethernet that the
service new
bandwidt service
hs and are path
isolated traverses.
by means
of VLAN
IDs.


Network VLAN ID
Size Allocation
Networking It is l The Medium l Low l The l The

of IEEE recommende network l The configurat network is
802.1d d that the need not service ion easy to
bridge-based network sense packets operations expand.
E-LAN contains less whether can be are l After a
services than 50 BTSs. the broadcast simple. BTS is
received on the l Point-to- added,
BTS entire multipoint you need
services network. configurat not
carry any ion is change
VLAN supported the
IDs. . configurat
l Services ions of
need not other NEs
be on the
isolated network.
between Instead,
different you only
ports need to
connected change
to the the
same mounted
bridge. a ports on
the NE
connected
to the base
station.


Network VLAN ID
Size Allocation
Networking This l The Medium l High l The l The

of IEEE networking VLAN l The configurat network is
802.1q mode is IDs that service ion easy to
bridge-based applicable to received packets operations expand.
E-LAN all network BTS are are l After a
services sizes, services broadcast simple. BTS is
especially to a carry are within l Point-to- added in a
network that planned in each multipoint domain,
is divided into a unified domain configurat you need
several manner and are ion is not
domains. and are isolated supported change
unique between . the
within different configurat
each domains. ions of the
domain. other NEs
l The BTS in the
services domain or
from the
different configurat
domains ions of
are NEs in the
isolated other
from each domains.
other by Instead,
means of you only
VLAN need to
IDs. change
l BTS the
services mounted
within a ports on
domain the NE
need not connected
be to the base
isolated station.
from each
other. a
NOTE
a: To block communication between certain ports connected to a bridge, you need to add the ports into a split
horizon group.

5.1.6 Managing a MAC Address Table

The entries in a MAC address table indicate the corresponding relationship between MAC
addresses and ports. A MAC address table contains the following entries: dynamic entry, static
entry, and blacklist entry.
l Dynamic entry
A dynamic entry is obtained by learning of a bridge through the SVL/IVL mode. The
dynamic entry ages.
l Static entry
A static entry is manually added by a network administrator to the MAC address table by
using the NMS. The static entry does not age. Generally, the static entry is configured when
a port corresponds to a device with its MAC address known and this device transmits large
traffic for a long time.
l Blacklist entry
A blacklist entry, that is, the MAC disabled entry, is used to discard the data frame that
contains the specified MAC address (source MAC address or destination MAC address).
A blacklist entry is also called a blackhole entry. The blacklist entry is configured by the
network administrator. The blacklist entry does not age, and is not lost after the Ethernet
processing board is reset.
NOTE
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.
5.1.7 VLAN Forwarding Table

Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If it is required to
change the VLAN IDs, you need to configure a VLAN forwarding table.
In the case of VLAN-based E-Line services, the VLAN IDs on the source and sink nodes are
usually set to the same value. If it is required that packets carry different VLAN IDs on the
source and sink nodes, the different VLAN IDs need to be set on the source and sink nodes of
the E-Line services. In addition, you need to configure a VLAN forwarding table to achieve the
switch of VLAN IDs at the source and sink nodes.
Figure 5-14 shows an application of the VLAN forwarding table. In this figure, Service 1 carries
a VLAN ID of 100, and it is transmitted to NE1 through Port 1. On a transmission network, the
VLAN ID of Service 1 may be in conflict with the VLAN IDs of other services. To avoid this
situation, the VLAN ID of Service 1 must be changed to another value before it is transmitted
on the transmission network and then be changed to the original value after it is transmitted out
of the transmission network. Therefore, a VLAN forwarding table is configured at NE1 and
NE2, so that the VLAN IDs of services between Port 1 and Port 3 can be changed as required.
With regard to Service 1, when it traverses NE1, the VLAN ID is changed from 100 to 200 and
then changes to 100 again at NE2.

Figure 5-14 Application of VLAN forwarding tables to E-Line services

NE 1 NE 2
Port 1 Port 1
Service 1 Service 1
Transmission
VLAN ID: 100 Port 3 Port 3 VLAN ID: 100
Network e
E-Lin
e E-Lin
Service 1 Service 1
VLAN Forwarding Table VLAN Forwarding Table

Source Source Sink Sink Source Source Sink Sink
Interface VLAN ID Interface VLAN ID Interface VLAN ID Interface VLAN ID
Port 1 100 Port 3 200 Port 1 100 Port 3 200
Port 3 200 Port 1 100 Port 3 200 Port 1 100
E-Line Service Information Table E-Line Service Information Table

Source Source Sink Sink Source Source Sink Sink
Interface VLAN ID Interface VLAN ID Interface VLAN ID Interface VLAN ID
Port 1 100, 200 Port 3 100, 200 Port 1 100, 200 Port 3 100, 200
5.1.8 Split Horizon Group

To better isolate services that are converged and to prevent broadcast storm resulting from a
service loop, you can configure a split horizon group for the E-LAN services at the specified
nodes. The logical ports in one split horizon group cannot forward packets to each other.
Figure 5-15 shows a typical application of the split horizon group. NEs on the network are
configured with E-LAN services, and the east and west ports and service access ports are
configured as mounted ports of a bridge. In this case, if a split horizon group is not configured
at NE1, broadcast storm occurs due to a network loop as the east and west ports can forward
packets to each other. If a split horizon group is created at NE1 and the east and west ports are
configured as members of the split horizon group, the east and west ports do not forward packets
to each other. Therefore, a service loop is prevented.
Figure 5-15 Split horizon group
NE1
BSC Split horizon group
BTS
NE2 NE4 BTS
BTS
NE3
BTS

NOTE
l ERPS can prevent a service loop on a ring network. Therefore, if ERPS is already enabled for a ring network,
a split horizon group is not needed as it may affect normal operation of ERPS.
l On the OptiX RTN 950, only the configuration of a split horizon group based on physical ports is supported.
Therefore, if a physical port is mapped into several logical ports and one of these logical ports is a member
of a split horizon group, the other logical ports are added to the split horizon group automatically.
5.1.9 Protection for Ethernet Services Based on the Packet Plane

Based on the packet plane, the OptiX RTN 950 supports three protection modes for Ethernet
services, namely, Ethernet ring protection switching (ERPS), link aggregation (LAG), and
multiple spanning tree protocol (MSTP).
ERPS
ERPS is applicable to ring physical networks and can provide protection for the E-LAN services
between all the nodes on the ring network. Generally, when a ring network is configured with
ERPS, the RPL node blocks the RPL port on one side so that all the services are transmitted
through the ports on the other side. In this manner, service loops are prevented. If a section of
link fails or an NE becomes faulty, the RPL node unblocks its RPL port so that the services are
switched from the faulty point to the RPL port for transmission. In this manner, protection for
the ring network is realized.
The Ethernet ring network shown in Figure 5-16 is configured with ERPS. Generally, the RPL
node (NE D) blocks its RPL port that is connected to NE A, and all the services are transmitted
over the link NE A <-> NE B <-> NE C <-> NE D. When the link between NE A <-> NE B
becomes faulty, NE D unblocks the blocked port so that the services can be transmitted over the
link NE A <-> NE D <-> NE C <-> NE B.

Figure 5-16 Implementation of ERPS
NE A
NE B NE D
NE C
Failure NE A
NE B NE D
NE C
Link
Ethernet service direction
Blocked port
LAG
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.
As shown in Figure 5-17, the LAG provides the following functions:
l Increases the link capacity.

The LAG provides the telecom operators with a cost-effective method of increasing the
link bandwidth. The 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 Improves the link availability.
The links in a LAG provide backup to each other dynamically. When a link fails, another
link in the LAG quickly takes over. The process in which link aggregation starts the backup
link is related only to the links in the same LAG and is not related to the links that are not
in the LAG.
Figure 5-17 LAG
Link 1
Link 2
Ethernet Link 3 Ethernet
packet packet
Link aggregation
group
MSTP
The OptiX RTN 950 supports only the MSTP protocol that uses the common and internal
spanning tree (CIST). The MSTP that uses the CIST can be used as a rapid spanning tree protocol
(RSTP). The RSTP is applicable in the case of a network loop. This protocol adopts certain
algorithms to reconstruct a loop network into a loop-free tree network and thus prevents Ethernet
frames from increasing and cycling in an endless manner on the loop network.
In the case of the OptiX RTN 950, the MSTP is used to prevent a network loop on the access
side.
See Figure 5-18. When the user equipment accesses the OptiX RTN 950 through two different
trails, you can configure the ports on the OptiX RTN 950 that are connected to the user network
into a port group. This port group, together with the switch on the user network, can run the
MSTP. Hence, if a service access link becomes faulty, the MSTP enables a re-configuration to
generate the spanning tree topology, thus providing protection for the user network that is
configured with multiple access points.

Figure 5-18 Prevention of network loops on the access side
Root Root
Port group
CIST
Blocked Port
5.1.10 QoS Based on the Packet Plane

The quality of service (QoS) refers to the ability of a communication network to ensure the
expected service quality in the aspects of the 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 requirements of an expected service class. The OptiX RTN 950 supports
the following QoS functions, namely, differentiated service (DiffServ), flow classification,
CAR, traffic shaping, and queue scheduling.
DiffServ
DiffServ (DS) is an end-to-end QoS control model and performs the QoS processing function
as follows:
1. The DS edge node checks the QoS information carried by the packets that enter the DS
domain. Then, the DS edge node aggregates the packets that are at the same QoS levels
into the same behavior aggregates (BAs) and maps the BAs into corresponding per-hop
behavior (PHB) service class.
2. The DS edge node controls the traffic of the BAs according to the PHB service class, and
forwards the BAs to the DS interior node.
3. The DS internal node controls the traffic of the BAs according to the PHB service class,
and forwards the BAs to the DS edge node of the next hop.
The OptiX RTN 950 supports eight PHB service class, namely, BE, AF1, AF2, AF3, AF4, EF,
CS6, and CS7. Packets can be mapped into the corresponding PHB level according to the
CVLAN priority, SVLAN priority, or DSCP value.
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. It is the same case with the AF2, AF3, and AF4.
l In the case of a point-to-point transparently transmitted E-Line service, the OptiX RTN 950 supports only
mapping the PHB service classes according to the DSCP values in the Ethernet frames.

Flow Classification
The OptiX RTN 950 supports two flow classification methods, namely, simple flow
classification and complex flow classification. In the case of the simple flow classification,
different services on specified ports are mapped into different PHB service classes according to
the C-VLAN priority, S-VLAN priority, or DSCP value. In the case of the complex flow
classification, specified services mapped into different PHB service classes according to the
CVLAN/SVLAN ID, CVLAN/SVLAN priority, or DSCP value.
The OptiX RTN 950 supports the following complex flow types:
l Flow classified according to the specified CVLAN ID

The packets that carry the specified CVLAN ID are classified as a flow.
l Flow classified according to the CVLAN priority
The packets that are from a certain port and have a specified CVLAN priority are classified
as a flow.
l Flow classified according to the specified SVLAN ID
The packets that are from a certain port and have a specified SVLAN ID are classified as
a flow.
l Flow classified according to the specified SVLAN priority
The packets that are from a certain port and have a specified SVLAN priority are classified
as a flow.
l Flow classified according to the DSCP value
The packets that are from a certain port and have a specified DSCP value are classified as
a flow.
The flow can be further classified according to the combination of CVLAN ID+CVLAN priority
or SVLAN ID+SVLAN priority.
In the case of complex flows, the following QoS processing operations can be performed:
l Passes or discards the flow according the access control list (ACL).
l Maps the flow into a new PHB service class.
l In the ingress direction, restrict the rate of the flow by using the CAR.
l In the egress direction, perform the flow shaping.
CAR
The CAR is a type of traffic policing technology. When the CAR is used, the rate of the traffic
after flow classification is assessed in a certain period (including in the long term and in the short
term); the packet rate of which does not exceed the specified value is set to a high priority and
the packet rate of which exceeds the specified value is discarded or downgraded. In this manner,
the CAR restricts the traffic into the transmission network.
The OptiX RTN 950 supports the CAR processing for a complex flow in the ingress direction.
The CAR processing operations are as follows:
l When the rate of packets is lower than or equal to the preset committed information rate
(CIR), these packets are marked green and pass the policing of the CAR. These packets are
always forwarded first in the case of network congestion.

l When the rate of packets exceeds the preset peak information rate (PIR), these packets at
a rate higher than the PIR are marked red and directly discarded.
l When the rate of packets is higher than the CIR but is lower than the PIR, the packets at a
rate higher than the CIR can pass the restriction but are marked yellow. Yellow packets
can be set to "discard", "pass", or "remark". If packets are set to "remark", these packets
are mapped to another specified queue with a certain priority (that is, the priority of these
packets is changed) and then forwarded.
l When the rate of packets that pass the restriction of the CAR is lower than or equal to the
CIR in a certain period, certain packets can burst and these packets are always forwarded
first in the case of network congestion. The maximum traffic of the burst packets is
determined by the committed burst size (CBS).
l When the rate of packets that pass the restriction of the CAR is higher than the CIR but is
lower than or equal to the PIR, certain packets can burst and these packets are marked
yellow. The maximum traffic of the burst packets is determined by the peak burst size
(PBS).
Figure 5-19 shows the traffic change after the CAR processing. The packets that are marked
red are directly discarded, and the packets that are marked yellow and green pass the policing
of the CAR. In addition, the packets that are marked yellow are processed according to the preset
value.
Figure 5-19 CAR processing
MBS
PIR
CBS
CIR
MBS
PIR PIR
CBS
CIR CAR CIR
Traffic Shaping
When the traffic shaping function is used, the traffic and burst size of an outgoing connection
of a network can be restricted. In this manner, the packet can be transmitted at an even rate.
The OptiX RTN 950 supports the shaping of a complex flow, the PHB service class, or the port
in the egress direction.
Queue Scheduling
In the case of the OptiX RTN 950, each Ethernet port has eight egress queues, which correspond
to eight PHB service classes. The OptiX RTN 950 supports three queue scheduling methods,
namely, strict-priority (SP), weighted round robin (WRR), and SP+WRR.
l SP Scheduling Algorithm
Figure 5-20 shows the SP scheduling algorithm. 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 manner,
packets of key services are placed into the queues with higher priorities and packets of non-
key services (such as email services) are placed into queues with lower priorities. Hence,
the packets of key services can be always transmitted first, and the packets of non-key
services are transmitted when the data of key services is not processed.
When the SP queue scheduling algorithm is used, all the resources are used to ensure the
QoS of the services of the highest priority. If there are packets in the queues with higher
priorities when congestion occurs, the packets in the queues with lower priorities cannot
be transmitted all the time.
Figure 5-20 SP queue scheduling algorithm

Queues Priorities
Packets to be transmitted Packets transmitted out of
Queue 8 Highest the interface
through this interface
Egress
Classific Queue 7 Higher
queue
ation scheduling
Queue 2 Normal
...
Queue 1 Lowest
Queue in which the priorities of packets are

in a descending order from left to right
l WRR Scheduling Algorithm

Figure 5-21 shows the WRR scheduling algorithm. The WRR scheduling algorithm divides
each port into several egress queues and schedules the packets in these queues in turn. This
ensures that each queue obtains a certain service period. In addition, the WRR allocates a
weight value for each queue and then allocates the service time period for each queue
according to the weight value. The port transmits the Ethernet frames of the corresponding
queue in the corresponding service period. If the queue to which the service period
corresponds contains no Ethernet frames, a time period is extracted to transmit the Ethernet
frames that correspond to the subsequent time periods. That is, the WRR ensures the
bandwidth resource allocation based on the weight values of the queues in the case of a
link congestion and full bandwidth utilization in the case of no link congestion. For
example, a port provides four queues. The weight proportion of the four queues is 5:3:1:1.
Hence, when congestions occur in all the queues, the four queues are allocated with the 50
Mbit/s, 30 Mbit/s, 10 Mbit/s, and 10 Mbit/s bandwidths respectively. If the first queue
contains no Ethernet frames and congestions occur in the other three queues, the other three
queues are allocated with the 60 Mbit/s, 20 Mbit/s, and 20 Mbit/s bandwidths respectively.
Compared with the SP scheduling algorithm, the WRR scheduling algorithm prevents the
disadvantage that packets in the queues with lower priorities may fail to obtain service for
a long time. In the case of the WRR algorithm, however, all the bandwidth resources cannot
be used when congestions occur in the services of higher priorities.

Figure 5-21 WRR scheduling algorithm

Packets to be transmitted Queues Weights
through this interface Packets transmitted out of
Queue 4 50 the interface
Egress
Queue 3 30
Classific queue
ation scheduling
Queue 2 10
Queue 1 10
Queue in which the priorities of packets are

in a descending order from left to right
l SP+WRR Scheduling Algorithm

Figure 5-22 shows the SP+WRR scheduling algorithm. In the case of SP+WRR scheduling
algorithm, a group of WRR queues must be allocated with the same queue priority. The SP
+WRR scheduling algorithm is described as follows:
– If the queues that have higher priorities than the WRR queues contain Ethernet frames,
the Ethernet frames are transmitted according to the SP scheduling algorithm. In this
case, the Ethernet frames in the WRR queues are not transmitted.
– If the queues that has higher priorities than the WRR queues do not contain Ethernet
frames, the Ethernet frames in the WRR queues are transmitted according to the WRR
scheduling algorithm.
– If the WRR queues and the queues that has higher priorities than the WRR queues do
not contain Ethernet frames, the Ethernet frames in the queues that has lower priorities
than the WRR queues are transmitted according to the SP algorithm.
Figure 5-22 SP+WRR scheduling algorithm

SP
Priorities
Queues
Packets to be transmitted
Queue 8 Highest Packets transmitted
through this interface
WRR out of the interface
Weights (%)
Queues Queue 7 Higher
25 Queue 5
Queue 6 Normal
Egress queue
Classifi 25 scheduling
Queue 4
cation WRR Queue lower
25
Queue 3
Queue 1 Lowest
25 Queue 2
Queue in which the priorities of packets are in a

descending order from left to right
In the case of the OptiX RTN 950, the SP+WRR scheduling algorithm is the default queue
scheduling mode for each Ethernet port. The queue priority levels are CS7, CS6, EF, AF4, AF3,
AF2, AF1, and BE in the descending order or priority. AF1 to AF4 are WRR queues. Except

for the default settings, the WRR queues and SP queues cannot be interleaved if you set the SP
+WRR scheduling algorithm manually.

5.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services)

This section describes how to perform parameter settings and other relevant operations as
required in the procedures for configuring point-to-point transparently transmitted E-Line
services.
5.2.2 Configuration Procedure (VLAN-Based E-Line Services)
required in the procedures for configuring VLAN-based E-Line services.
5.2.3 Configuration Procedure (QinQ-Based E-Line Services)
required in the procedures for configuring QinQ-based E-Line services.
5.2.4 Procedures for Configuring 802.1d Bridge-Based E-LAN Services
required in the procedures for configuring 802.1d-bridge-based E-LAN services.
5.2.5 Configuration Procedure (802.1q-Bridge-Based E-LAN Services)
required in the procedures for configuring 802.1q-bridge-based E-LAN services.
5.2.6 Configuration Procedure (802.1ad-Bridge-Based E-LAN Services)
required in the procedures for configuring 802.1ad-bridge-based E-LAN services.
5.2.1 Configuration Procedure (Point-to-Point Transparently

Transmitted E-Line Services)
required in the procedures for configuring point-to-point transparently transmitted E-Line
services.
Configuration Flow Chart

Figure 5-23 provides the procedures for configuring point-to-point transparently transmitted E-
Line services.

Figure 5-23 Configuration flow chart (point-to-point transparently transmitted E-Line services)
Required Start
Optional
Configuring Ethernet
ports
Configuring LAGs
Configuring E-Line
services
Configuring QoS
Verifying Ethernet
service configurations
End
Procedures for Configuring Ethernet Ports
Table 5-10 Procedures for configuring Ethernet ports
Setting the A.12.6.1 Required. Set the parameters as follows:

parameters Setting the l In the case of used ports, set Enable Port to Enabled. In
of Ethernet General the case of unused ports, set Enable Port to Disabled.
ports Attributes
of Ethernet l Set Encapsulation Type to Null.
Ports l In the case of an Ethernet port that is connected to external
equipment, set Working Mode to be the same value as the
external equipment (the working mode of the external
equipment is generally auto-negotiation). In the case of an
Ethernet port within the network, set Working Mode to
Auto-Negotiation.
l When jumbo frames are transmitted, set Max Frame
Length(byte) according to the actual length of the jumbo
frames. Otherwise, it is recommended that you set Max
Frame Length(byte) to 1536.

A.12.6.2 Required when the flow control function is enabled on the

Configuring external equipment to which the Ethernet port is connected.
the Traffic Set the parameters as follows:
Control of l When the external equipment uses the non-auto-
Ethernet negotiation flow control function, set Non-
Ports Autonegotiation Flow Control Mode to Enable
Symmetric Flow Control.
l When the external equipment uses the auto-negotiation
flow control function, set Auto-Negotiation Flow
Control Mode to Enable Symmetric Flow Control.
A.12.6.4 Optional.
Setting the
Advanced
Attributes
of Ethernet
Ports
Setting the A.12.7.1 Required.

parameters Setting the Set Encapsulation Type to Null.
of IF_ETH General
ports Attributes
of the
IF_ETH
Port
A.12.7.3 Optional.
Setting the When the IF_ETH port transmits an Ethernet service that
Advanced permits bit errors, such as a voice service or a video service,
Attributes you can set Error Frame Discard Enabled to Disabled.
of the
IF_ETH
Port

Procedures for Configuring a LAG
Table 5-11 Procedures for configuring a LAG

A.12.2.1 Required if the LAG is configured to protect the FE/GE ports or if the
Creating a Hybrid radio uses the N+0/XPIC configuration mode. Set the parameters
LAG as follows:
l Set LAG Type to the same value as the opposite equipment. Generally,
set LAG Type to Static for the equipment at both ends.
l The Hybrid/AM attributes must be set to the same value for the IF ports
in a LAG.
l In the case of FE/GE ports, set Load Sharing to the same value as the
opposite equipment. If the LAG is configured only to provide
protection, it is recommended that you set Load Sharing to Non-
Sharing for the equipment at both ends. If the LAG is configured to
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l When the Hybrid radio uses the N+0/XPIC configuration mode, set
Load Sharing to Sharing for the equipment at both ends.
l Set Revertive Mode to the same value as the opposite equipment.
Generally, set Revertive Mode to Revertive for the equipment at both
ends. This parameter is valid to only LAGs whose Load Sharing is set
to Non-Sharing.
l Set Load Sharing Hash Algorithm to the same value as the opposite
equipment. Unless otherwise specified, this parameter takes the default
value. This parameter is valid to only LAGs whose Load Sharing is
set to Sharing.
l It is recommended that you set this parameter to the same value for the
main and slave ports of the LAGs at both ends. In this case, you can
set System Priority according to the actual requirements. It is
recommended that this parameter takes the default value. This
parameter is valid to only static LAGs.
l Set Main Board, Main Port, and Selected Slave Ports according to
the planning information. It is recommended that you set this parameter
to the same value for the main and slave ports of the LAGs at both ends.
NOTE
The members of a 1+1 XPIC workgroup cannot be used to construct any LAG.
A.12.2.2 Optional.
Setting
Parameters for
LAGs

Procedures for Configuring Point-to-Point Transparently Transmitted E-Line

Services
Table 5-12 Procedures for configuring point-to-point transparently transmitted E-Line services
A.12.3.2 Required. Set the parameters as follows:

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

A.12.10.1 Required.
Creating a DS Set the parameters according to the network planning information.
Domain
NOTE
Point-to-point transparently transmitted services support mapping the PHB service
classes based on the DSCP type only. The default DS, however, maps the PHB
service classes according to the CLAN priorities. Therefore, you need to configure
a new DS.
A.12.10.4 Required when you need to apply QoS policies other than DS and port
Creating a Port shaping for a specific port.
Policy Set the parameters according to the network planning information.
A.12.10.6 Required when you need to perform the CAR or shaping operation for a
Creating the specific flow over the port.
Traffic Set the parameters according to the network planning information.
A.12.10.7 Required when the new port policy is created.

Setting the Set the parameters according to the network planning information.
Port That Uses
the Port Policy
A.12.10.8 Required if you need to limit the egress bandwidth that an Ethernet service
Configuring occupies.
Port Shaping Set the parameters according to the network planning information.

Procedures for Verifying Ethernet Service Configurations
Table 5-14 Procedures for verifying Ethernet service configurations
A.12.11.1 Required in the case of the NEs where the two Ethernet ports involved in
Creating an the service test are located. Set the parameters as follows:
MD l Set Maintenance Domain Name and Maintenance Domain Level to
the same values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance Domain
Level takes the default value 4. In the test of an Ethernet service
between two internal NEs on the transport network, set Maintenance
Domain Level to a value smaller than 4. In the test of an Ethernet
service between two Ethernet ports on the same NE, set Maintenance
Domain Level to a value smaller than the value that is set in the test of
an Ethernet service between two internal NEs on the transport network.
MA l Set Maintenance Domain Name to the value of Maintenance
Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the same value for the two
NEs.
l Set Relevant Service to the same service for the two NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
MEP Point l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l The MP ID is used to identify the MEP during the LB test. Therefore,
set CC Status to Active.
A.12.11.4 Required in the case of the NE where the Ethernet ports involved in the
Creating OAM operation are located. Set the parameters as follows:
Remote MEPs l Set Maintenance Domain Name to the value of Maintenance
in an MA Domain Name that is set in the preceding step.
l Set Maintenance Association Name to the value of Maintenance
l If MEPs may initiate OAM operations to another MEP in the same MA,
set the MEPs to be remote MEPs.

perform an LB Required.
test to test the The LB test result should show that no packet loss occurs.
Ethernet
service
configurations
5.2.2 Configuration Procedure (VLAN-Based E-Line Services)

required in the procedures for configuring VLAN-based E-Line services.

Figure 5-24 provides the procedures for configuring VLAN-based E-Line services.
Figure 5-24 Configuration flow chart (VLAN-based E-Line services)

Required Start
Optional
ports
Configuring LAGs
Configuring E-Line
services
Configuring QoS
Verifying Ethernet
End



ports Attributes
of Ethernet l Set Encapsulation Type to 802.1Q.
Ports l In the case of the Ethernet port that is connected to the
external equipment, set Working Mode to be the same
value as the external equipment (generally, the working
mode of the external equipment is auto-negotiation). In the
case of the Ethernet ports within the network, set Working
Mode to Auto-Negotiation.


Setting the l If all the accessed services carry VLAN tags (tagged
Layer 2 frames), set TAG to Tag Aware.
Attributes
of Ethernet l If none of the accessed services carries VLAN tags
Ports (untagged frames), set TAG to Access, and set Default
VLAN ID and VLAN Priority according to the network
l When the accessed services contain tagged frames and
untagged frames, set TAG to Hybrid, and set Default
A.12.6.4 Optional.
Setting the
Advanced
Attributes
of Ethernet
Ports


parameters Setting the Set Encapsulation Type to 802.1Q.
of IF_ETH General
ports Attributes
of the
IF_ETH
Port

Layer 2 frames), set Tag to Tag Aware.
Attributes
of the l If none of the accessed services carries VLAN tags
IF_ETH (untagged frames), set Tag to Access, and set Default
Port VLAN ID and VLAN Priority according to the network
untagged frames, set Tag to Hybrid, and set Default
A.12.7.3 Optional.
of the
IF_ETH
Port


LAG as follows:
l The Hybrid/AM attribute must be set to the same value for the IF ports
in a LAG.
opposite equipment. If the LAG is configured only to realize protection,
it is recommended that you set Load Sharing to Non-Sharing for the
equipment at both ends. If the LAG is configured to increase the
bandwidth, it is recommended that you set Load Sharing to Sharing
for the equipment at both ends.
to Non-Sharing.
equipment. Unless otherwise specified, this parameter adopts the
default value. This parameter is valid to only LAGs whose Load
Sharing is set to Sharing.
main and slave ports. In this case, you can set System Priority
according to the requirements. It is recommended that this parameter
adopts the default value. This parameter is valid only to static LAG.
to the same values for the main and slave ports.
NOTE
A.12.2.2 Optional.
Setting
Parameters for
LAGs

Procedures for Configuring VLAN-Based E-Line Services
Table 5-17 Procedures for configuring VLAN-based E-Line services


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

A.12.10.1 Required.
Domain
NOTE
a new DS.

Port That Uses
the Port Policy


NEs.
test.

Ethernet
service
configurations
5.2.3 Configuration Procedure (QinQ-Based E-Line Services)

required in the procedures for configuring QinQ-based E-Line services.

Figure 5-25 provides the procedures for configuring QinQ-based E-Line services.
Figure 5-25 Configuration flow chart (QinQ-based E-Line services)

Required Start
Optional
ports
Configuring LAGs
Configuring E-Line
services
Configuring QoS
Verifying Ethernet
End


Setting the parameters of A.12.6.1 Setting the Required. Set the parameters
Ethernet ports General Attributes of as follows:
Ethernet Ports l In the case of used ports,
set Enable Port to
Enabled. In the case of
unused ports, set Enable
Port to Disabled.
l When jumbo frames are
transmitted, set Max
Frame Length(byte)
according to the actual
length of the jumbo
frames. Otherwise, it is
recommended that you set
Max Frame Length
(byte) to 1536.
A.12.6.2 Configuring the Required when the flow

Traffic Control of Ethernet control function is enabled on
Ports the external equipment to
which the Ethernet port is
connected. Set the
parameters as follows:
l When the external
equipment uses the non-
auto-negotiation flow
control function, set Non-
Autonegotiation Flow
Control Mode to Enable
Symmetric Flow
Control.
l When the external
equipment uses the auto-
negotiation flow control
function, set Auto-
Negotiation Flow
Control Mode to Enable
Symmetric Flow
Control.

A.12.6.3 Setting the Layer 2 Required.

Attributes of Ethernet In the case of an NNI that is
Ports connected to the external
equipment, set QinQ Type
Domain according to the T-
PID of the SVLAN that is
supported by the external
equipment. In the case of
NNIs within the network,
QinQ Type Domain takes
the default value.
A.12.6.4 Setting the Optional.

Advanced Attributes of
Ethernet Ports
Setting the parameters of A.12.7.1 Setting the Optional.

IF_ETH ports General Attributes of the
IF_ETH Port
A.12.7.2 Setting the Layer 2 Optional.

Attributes of the IF_ETH In the case of an NNI that is
Port connected to the external
equipment, set QinQ Type
Domain according to the T-
PID of the SVLAN that is
supported by the external
equipment. In the case of
NNIs within the network,
QinQ Type Domain takes
the default value.
A.12.7.3 Setting the Optional.

Advanced Attributes of the
IF_ETH Port


LAG as follows:
in a LAG.
to Non-Sharing.
set to Sharing.
NOTE
A.12.2.2 Optional.
Setting
Parameters for
LAGs

Procedures for Configuring QinQ-Based E-Line Services
Table 5-22 Procedures for configuring QinQ-based E-Line services

A.12.3.1 Required.
Configuring Set the parameters according to the network planning information.
the QinQ Link
A.12.3.2 Required.
Configuring Set the parameters according to the network planning information.
the E-Line
Service

A.12.10.1 Required.
Domain
NOTE
a new DS.

Port That Uses
the Port Policy

NEs.
test.

Ethernet
service
configurations
5.2.4 Procedures for Configuring 802.1d Bridge-Based E-LAN

Services
required in the procedures for configuring 802.1d-bridge-based E-LAN services.

Figure 5-26 provides the procedures for configuring 802.1d-bridge-based E-LAN services.
Figure 5-26 Configuration flow chart (802.1d bridge-based E-LAN services)

Required Start
Optional
Configuring Ethernet ports
Configuring LAGs
Configuring ERPS protection
Configuring E-LAN services
Configuring QoS
Verifying Ethernet service

configurations
End



ports Attributes
of Ethernet l Set Encapsulation Type to Null.
Ports l In the case of an Ethernet port that is connected to external
equipment, set Working Mode to be the same value as the
external equipment (generally, the working mode of the
external equipment is auto-negotiation). In the case of an
Ethernet port within the network, set Working Mode to
Auto-Negotiation.

A.12.6.4 Required when you need to enable the port self-loop test and
Setting the automatic loopback shutdown functions or to enable the
Advanced broadcast packet suppression function.
Attributes Set Loopback Check, Loopback Port Shutdown, Enabling
of Ethernet Broadcast Packet Suppression, and Broadcast Packet
Ports Suppression Threshold according to the actual
requirements.

parameters Setting the Set Encapsulation Type to Null.
of IF_ETH General
ports Attributes
of the
IF_ETH
Port

A.12.7.3 Optional.
of the
IF_ETH
Port


LAG as follows:
in a LAG.
to Non-Sharing.
set to Sharing.
NOTE
A.12.2.2 Optional.
Setting
Parameters for
LAGs

Procedures for Configuring ERPS Protection
Table 5-27 Procedures for configuring ERPS protection

A.12.1.1 Required if the Ethernet services are configured with ERPS.

Creating
Ethernet Ring
Protection
Instances
A.12.1.2 Required if the values of the default parameters of the ERPS timers need
Setting the to be changed.
Parameters of Set Hold-Off Time(ms), Guard Time(ms), WTR Time(min), and
Ethernet Ring Packet Transmit Interval(s) according to the actual requirements. Set
Protocol these parameters to the same values for all the NEs on the network.
Procedures for Configuring 802.1d-Bridge-Based E-LAN Services
Table 5-28 Procedures for configuring 802.1d-bridge-based E-LAN services

A.12.3.4 Configuring the E- Required. Set the parameters as follows:

LAN Service l Set Tag Type to Tag-Transparent.
l Set Self-Learning MAC Address to Enabled according
to the planning information.
l In the UNI tab page, set Port according to the planning
information and set VLANs/CVLAN to Null.
l To disable the packet forwarding between certain E-LAN
service ports, add the ports to Split Horizon Group
Member.
Managing A.12.4.2 Required when usage of E-LAN services needs to be disabled

the MAC Creating a on certain MAC address host.
address table Blacklist Set the parameters according to the network planning
Entry of information.
MAC
Addresses
A.12.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static MAC Set the parameters according to the network planning
Address information.
Entry

A.12.4.3 Required if the aging function needs to be disabled or if the

Configuring default aging time (five minutes) needs to be changed.
the Aging Set the parameters according to the network planning
Parameters information.
of a MAC
Address
Table
A.12.5 Setting the Mode for Optional.

Processing an Unknown
Frame of the E-LAN
Service

A.12.10.1 Required.
Domain
NOTE
a new DS.

Port That Uses
the Port Policy

NEs.
test.

Ethernet
service
configurations
5.2.5 Configuration Procedure (802.1q-Bridge-Based E-LAN

Services)
required in the procedures for configuring 802.1q-bridge-based E-LAN services.

Figure 5-27 provides the procedures for configuring 802.1q-bridge-based E-LAN services.
Figure 5-27 Configuration flow chart (802.1q-bridge-based E-LAN services)

Required Start
Optional
Configuring LAGs
Configuring QoS

configurations
End

The detailed information about the procedures in the flow chart is provided as follows.


ports Attributes
of Ethernet l Set Encapsulation Type to 802.1Q.
Ports l In the case of the Ethernet port that is connected to the


Layer 2 frames), set TAG to Tag Aware.
Attributes
of Ethernet l If none of the accessed services carries VLAN tags
Ports (untagged frames), set TAG to Access, and set Default
untagged frames, set TAG to Hybrid, and set Default

Ports Suppression Threshold according to the requirements.

parameters Setting the Set Encapsulation Type to 802.1Q.
of IF_ETH General
ports Attributes
of the
IF_ETH
Port

Layer 2 frames), set Tag to Tag Aware.
Attributes
of the l If none of the accessed services carries VLAN tags
IF_ETH (untagged frames), set Tag to Access, and set Default
Port VLAN ID and VLAN Priority according to the network
untagged frames, set Tag to Hybrid, and set Default
A.12.7.3 Optional.
of the
IF_ETH
Port


Creating
Ethernet Ring
Protection
Instances


LAG as follows:
in a LAG.
to Non-Sharing.
set to Sharing.
NOTE

A.12.2.2 Optional.
Setting
Parameters for
LAGs
Procedures for Configuring 802.1q-Bridge-Based E-LAN Services
Table 5-34 Procedures for configuring 802.1q-bridge-based E-LAN services


LAN Service l Set Tag Type to Tag-Transparent.
l In the UNI tab page, set Port according to the planning
information and set VLANs/CVLAN to Null.
Member.

MAC
Addresses
Creating a to age.
Entry

of a MAC
Address
Table

Frame of the E-LAN
Service


A.12.10.1 Required.
Domain
NOTE
a new DS.

Port That Uses
the Port Policy


NEs.
test.
Ethernet
service
configurations
5.2.6 Configuration Procedure (802.1ad-Bridge-Based E-LAN

Services)
required in the procedures for configuring 802.1ad-bridge-based E-LAN services.

Figure 5-28 provides the procedures for configuring 802.1ad-bridge-based E-LAN services.

Figure 5-28 Configuration flow chart (802.1ad-bridge-based E-LAN services)

Required Start
Optional
Configuring LAGs
Configuring QoS

configurations
End
The detailed information about the procedures in the flow chart is provided as follows.



ports Attributes
of Ethernet l If a UNI can access untagged frames, set Encapsulation
Ports Type to Null. If a UNI can access tagged frames only, set
Encapsulation Type to 802.1Q.
l In the case of an NNI, set Encapsulation Type to QinQ.
l In the case of the Ethernet port that is connected to the


Setting the l In the case of a UNI, if Encapsulation Type is set to
Layer 2 802.1Q, set TAG to Tag Aware (default value).
Attributes
of Ethernet l In the case of an NNI that is connected to the external
Ports equipment, set QinQ Type Domain according to the T-
PID of the SVLAN that is supported by the external
equipment.
Ports Suppression Threshold according to the requirements.


parameters Setting the l If a UNI can access untagged frames, set Encapsulation
of IF_ETH General Type to Null. If a UNI can access tagged frames only, set
ports Attributes Encapsulation Type to 802.1Q.
of the
IF_ETH l In the case of an NNI, set Encapsulation Type to QinQ.
Port

Setting the l In the case of a UNI, if Encapsulation Type is set to
Layer 2 802.1Q, set Tag to Tag Aware (default value).
Attributes
of the l In the case of an NNI that is connected to the external
IF_ETH equipment, set QinQ Type Domain according to the T-
Port PID of the SVLAN that is supported by the external
equipment. In the case of an NNI within the network,
QinQ Type Domain takes the default value.
A.12.7.3 Optional.
of the
IF_ETH
Port


Creating
Ethernet Ring
Protection
Instances


LAG as follows:
in a LAG.
to Non-Sharing.
set to Sharing.
NOTE
A.12.2.2 Optional.
Setting
Parameters for
LAGs

Procedures for Configuring 802.1ad-Bridge-Based E-LAN Services
Table 5-40 Procedures for configuring 802.1ad-bridge-based E-LAN services


LAN Service l Set Tag Type to S-Awared.
l In the UNI and NNI tab pages, set the parameters
according to the planning information.
Member.

MAC
Addresses
Creating a to age.
Entry

of a MAC
Address
Table

Frame of the E-LAN
Service


A.12.10.1 Required.
Domain
NOTE
a new DS.

Port That Uses
the Port Policy


NEs.
test.
Ethernet
service
configurations
5.3 Configuration Example (Point-to-Point Transparently

Transmitted E-Line Services)
This section considers a point-to-point transparently transmitted E-Line service as an example
to describe how to configure the Ethernet service according to the network planning information.



You need to plan the corresponding parameter information before configuring an Ethernet
service.
This section describes the process for data configuration.

As shown in Figure 5-29, NE1 is a terminal station of a backhaul network. The service
requirements are as follows:
l NE1 transparently transmits the Ethernet services from the BTS to NE2 in point-to-point
manner.
l DSCP flags are used to identify the priorities of the Ethernet services from the BTS.
To meet the preceding requirements, point-to-point transparently transmitted E-line services are
configured; in addition, corresponding QoS processing is configured.
Figure 5-29 Networking diagram (point-to-point transparently transmitted E-Line services)

Tranparent transmitted
E-Line service
Backhaul network
NE1 NE2 BSC

BTS
The connections of Ethernet links shown in Figure 5-29 are described as follows.
Table 5-43 Connections of Ethernet links (NE1)

Between NE1 and the BTS 1-EM6T-3 Configure this port to access
services from the BTS.
Between NE1 and NE2 3-IFU2-1 Configure this port to

transmit backhaul services
from a BTS.
The Hybrid radio link
between NE1 and NE2
adopts the 1+0 non-
protection configuration. In
addition, the AM function is
enabled for the Hybrid radio
link.


service.
5.3.2.1 Service Planning (Ethernet Ports)

configuring Ethernet ports.
5.3.2.2 Service Planning (Ethernet Protection)
configuring Ethernet protection.
5.3.2.3 Service Planning (Ethernet Services)
configuring Ethernet services.
5.3.2.4 Service Planning (QoS)
configuring QoS.

Ethernet Port
Table 5-44 provides the information about the Ethernet port involved in the service.
Table 5-44 Ethernet port

Parameter 1-EM6T-3
Encapsulation Type Null
Working Mode Auto-Negotiation
Maximum Frame Length (byte) 1536
Flow Control Disabled

NOTE
l In this example, the GE port on the BTS works in the auto-negotiation mode. Hence, the FE port that accesses
the BTS must work in the auto-negotiation mode. If the peer Ethernet port works in another mode, the local
Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are
planned as auto-negotiation.
l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse
the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo
frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The flow control planning on the NE must match the flowing control planning on the peer
equipment.
Information About the IF_ETH Ports

Table 5-45 provides the information about the IF_ETH ports that carry services.
Table 5-45 Ethernet port

Parameter 3-IFU2-1
Error Frame Discard Enabled Enabled
NOTE
The majority of the backhaul services on the BTS are Internet services. Hence, the error frame discarding function
needs to be enabled.

In this example, Ethernet protection is not used.

Table 5-46 provides the detailed service planning information.
Table 5-46 Point-to-point transparently transmitted E-line service

Parameter NE1
Service ID 1
Service Name BTStoNE2_Tline
Direction UNI-UNI
BPDU Not Transparently Transmitted

Parameter NE1
Source Port 1-EM6T-3
Source C-VLANs Blank
Sink Port 3-IFU2-1
Sink C-VLANs Blank

configuring QoS.
QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated according to the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding DSCP values according to
the service type, and the NEs allocate the PHB service classes according to the DSCP value, as
shown in Table 5-47. Each Ethernet port involved in the service uses the same DS configuration.
Table 5-47 Service class and PHB service class

PHB Service Class DSCP Corresponding Service
Type
CS7 56 -
CS6 48 -
EF 40 Real-time voice service and

signaling service (R99
conversational and R99
streaming services)
AF4 32 -
AF3 24 Real-time OM and HSDPA

services (OM streaming and
HSPA streaming services)
AF2 16 Non-real-time R99 service

(R99 interactive and R99
background services)
AF1 8 -


Type
BE 0 HSDPA data service (HSPA

interactive and background
services)
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit
Ethernet protocol packets or inband DCN packets on the NE.
QoS (Queue Scheduling Mode)

Generally, each Ethernet port involved in the service uses the same queue scheduling mode.
Table 5-48 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
Table 5-48 Queue scheduling mode

PHB Service Class Queue Scheduling Mode
CS7 SP
CS6 SP
EF SP
AF4 WRR (weight = 5)
BE SP
QoS (CAR or Shaping for a Specified Service Flow)

To perform the CAR or shaping processing for a specified service flow, you need to configure
the DS edge node accordingly.
In this example, no CAR or shaping processing needs to be performed on the services transmitted
from the BTS.
QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of
the aggregation services, you can perform port shaping at the edge node to limit the Ethernet
service traffic that travels to the aggregation node, thus preventing congestion at the aggregation
node.

In this example, you do not need to perform port shaping.

5.3.3.1 Configuration Process (Ethernet Ports)

This section describes the process for configuring Ethernet ports.
5.3.3.2 Configuration Process (Ethernet Protection)
5.3.3.3 Configuration Process (Service Information)
This section describes the process for configuring service information.
5.3.3.4 Configuration Process (QoS)
This section describes the procedures for configuring QoS.
5.3.3.5 Configuration Process (Verifying Ethernet Service Configurations)
This section describes the process for verifying Ethernet service configurations.

Procedure
Step 1 See A.12.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes
of the Ethernet port.
Parameter Value
1-EM6T-3
Enable Port Enabled
Max Frame Length(byte) 1536
Step 2 See A.12.7.1 Setting the General Attributes of the IF_ETH Port and set the general attributes
of the IF_ETH port.
Parameter Value
3-IFU2-1

----End


Procedure
Step 1 See A.12.3.2 Configuring the E-Line Service and configure the E-Line services.
Parameter Value
Service ID 1
Service Name BTStoNE2_Tline
Direction UNI-UNI
Source VLANs Blank
Sink Port 3-IFU2-1
Sink VLANs Blank
----End

Procedure
Step 1 See A.12.10.1 Creating a DS Domain and create a DS domain.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Mapping Relation ID 2
Mapping Relation Name DiffservForBackhaul

Parameter Value
Packet Type ip-dscp
The values for the relevant parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
CVLAN SVLAN IP DSCP PHB
0 BE
8 AF11
16 AF21
24 AF31
32 AF41
40 EF
48 CS6
56 CS7
The values for the relevant parameters that need to be set in the Egress Mapping Relation tab
PHB CVLAN SVLAN IP DSCP
BE 0
AF11 8
AF21 16
AF31 24
AF41 32
EF 40
CS6 48
CS7 56
NOTE
The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid.
In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
The values for the relevant parameters that need to be set in the Application Port tab page are
provided as follows.

Parameter Value
Selected Port 1-EM6T-3

3-IFU2-1
Step 2 See A.12.10.4 Creating a Port Policy to create the port policy.
Parameter Value
Policy ID 1
Policy Name Port_Comm
Grooming Police After Reloading SP (CS7, CS6, and EF)

WRR (AF4-AF1)
SP (BE)
Policy Weight(%) 5 (AF4)

60 (AF3)
30 (AF2)
5 (AF1)
Bandwidth Limit Disabled (for all PHB service classes)
Step 3 See A.12.10.7 Setting the Port That Uses the Port Policy and set the ports that use the port
policy.
Parameter Value
Port_Comm
Port 1-EM6F-1
3-IFU2-1
----End

Context
NOTE
This section describes how to configure the point-to-point transparently transmitted Ethernet service on NE1
and how to configure the ETH OAM data on NE2 for testing the Ethernet service.

Procedure
Step 1 See A.12.11.1 Creating an MD and create an MD.
Parameter Value
NE1 NE2
Maintenance Domain InterNE InterNE

Name
Maintenance Domain 3 3
Level
Step 2 See A.12.11.2 Creating an MA and create an MA.
Parameter Value
NE1 NE2

Name
Maintenance Association BTS_Tline BTS_Tline

Name
Relevant Service 1-BTStoNE2_Tline 1-BSCtoBTS_TlineA
CC Test Transmit Period 1s 1s
NOTE
a: BSCtoBTS_Tline is the name of the point-to-point Ethernet service that is transparently transmitted from NE2
to NE1. The service ID is 1.
Step 3 See A.12.11.3 Creating an MEP Point and create MEP points.
Parameter Value
NE1 NE2

Name

Name
Board 1-EM6T 3-IFU2

Parameter Value
NE1 NE2
Port 1-EM6T-3 3-IFU2-1
VLAN - -
MP ID 101 102
Direction Ingress Egress
CC Status Active Active
Step 4 A.12.11.4 Creating Remote MEPs in an MA.
Parameter Value
NE1 NE2

Name

Name
Remote Maintenance Point 102 101

ID(e.g:1,3-6)
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line service.
Use MP 101 as the source maintenance point and MP 102 as the sink maintenance point to
perform the LB test.
No packet loss occurs.
----End
5.4 Configuration Example (VLAN-Based E-Line Service)

This section considers a VLAN-based E-line service as an example to describe how to configure

service.


configure Ethernet services according to the following requirements:
l BTS1 to BTS5 provide FE ports whose port rate is 100 Mbit/s.

l The BSC provides GE ports whose port rate is 1000 Mbit/s.
l The maximum Ethernet bandwidth is specified for each BTS/BSC on the network.
l GE links to the BSC are configured with LAG protection.
l Services transmitted by each BTS carry VLAN tags, and VLAN IDs on the entire network
are planned in a unified manner.
l VLAN priorities are configured on each BTS according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for service
transmission on each NE; in addition, corresponding LAG protection and QoS processing are
configured.
Figure 5-30 Networking diagram (VLAN-based E-Line services)

BTS2
15 Mbit/s
VLAN 110-119
FE
GE GE
FE NE4
BTS3
20 Mbit/s FE
VLAN 120-129
NE3 NE2 NE1 BSC
120 Mbit/s
VLAN 100-149
FE BTS1
FE 45 Mbti/s
NE6 NE5 VLAN 100-109
BTS4
BTS5 25 Mbit/s
15 Mbit/s VLAN 130-139
VLAN 140-149
Link Port Port Description Description
Between NE1 and 1-EM6F-1 Main port of a LAG Configure these ports
the BSC into a load non-
1-EM6F-2 Slave port of a LAG sharing LAG,
therefore improving
link reliability.

Between NE1 and 3-IFU2-1 Main IF board of a 1 Configure this port to

NE2 +1 HSB protection transmit Ethernet
group services on Hybrid
radio.
5-IFU2-1 Standby IF board of a
1+1 HSB protection
group

Between NE2 and 1-EM6T-1 - Configure this port to

NE3 transmit backhaul
services from a BTS.

BTS1 access services from
BTS1.

radio.
1+1 HSB protection
group


radio.
1+1 HSB protection
group

radio.
1+1 HSB protection
group




radio.
1+1 HSB protection
group

BTS2.

BTS3.

Between NE5 and 3-IFU2-1 - Configure this port to

NE6 transmit Ethernet
services on Hybrid
radio.

radio.
1+1 HSB protection
group

BTS4.


transmit Ethernet services on
Hybrid radio.
Between NE6 and BTS5 1-EM6T-3 Configure this port to access

services from BTS5.

service.

configuring QoS.

Ethernet Ports
Table 5-55 to Table 5-60 provide the information about each Ethernet port involved in the
service.
Table 5-55 Ethernet port (NE1)
Parameter 1-EM6F-1 1-EM6F-2
Encapsulation Type 802.1Q 802.1Q
Working Mode Auto-Negotiation Auto-Negotiation
Maximum Frame Length 1536 1536

(byte)

Flow Control Disabled Disabled
Tag Tag Aware Tag Aware

Parameter 1-EM6T-3 1-EM6T-1

(byte)

Parameter 1-EM6T-1
Encapsulation Type 802.1Q
Tag Tag Aware


(byte)

Parameter 1-EM6T-3
Tag Tag Aware
Parameter 1-EM6T-3
Tag Tag Aware
NOTE
l In this example, the FE ports on all the BTSs work in the auto-negotiation mode. Hence, the FE port of each
NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet port works in another
mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside
the network are planned as auto-negotiation.
equipment.
l In this example, all the services carry VLAN tags. Therefore, the tag attributes of all the ports are tag-aware.
Information About the IF_ETH Port

Table 5-61 to Table 5-66 provide the information about the IF_ETH ports that carry services.
Table 5-61 IF_ETH port (NE1)
Parameter 3-IFU2-1 5-IFU2-1

Error Frame Discard Enabled Enabled Enabled
Parameter 3-IFU2-1 5-IFU2-1 4-IFU2-1 6-IFU2-1
Encapsulation 802.1Q 802.1Q 802.1Q 802.1Q

Type
Tag Tag Aware Tag Aware Tag Aware Tag Aware
Error Frame Enabled Enabled Enabled Enabled

Discard
Enabled
Parameter 3-IFU2-1 4-IFU2-1 6-IFU2-1
Encapsulation Type 802.1Q 802.1Q 802.1Q
Tag Tag Aware Tag Aware Tag Aware

Enabled

Parameter 3-IFU2-1
Tag Tag Aware
NOTE
The majority of the backhaul services on the BTS are the Internet services. Hence, the error frame discarding
function needs to be enabled.

To improve the reliability of service transmission, NE1 and the BSC are interconnected through
the LAG formed by two GE links. Table 5-67 provides the planning information.
Table 5-67 LAG information
Parameter NE1
LAG Type Static (default value)
Load Sharing Non-Sharing (default value)
System Priority 32768 (default value)
Main Port 1-EM6F-1
Slave Port 1-EM6F-2
NOTE
In this example, the bandwidth of the Ethernet service to be transmitted is 120 Mbit/s, much smaller than the
bandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing mode
to increase the bandwidth.

Table 5-68 to Table 5-73 provide the detailed service planning information.

Table 5-68 VLAN-based E-Line service (NE1)
Parameter NE1
NE2 to BSC
Service ID 1
Service Name NE2toBSC_Vline
Direction UNI-UNI
Source Port 3-IFU2-1
Source C-VLANs 100-149
Sink Port 1-EM6F-1
Sink C-VLANs 100-149
Parameter NE2
NE3 to NE1 BTS1 to NE1
Service ID 1 2
Service Name NE3toNE1_Vline BTS1toNE1_Vline
Direction UNI-UNI UNI-UNI
BPDU Not Transparently Not Transparently

Transmitted Transmitted
Source Port 1-EM6T-1 1-EM6T-3
Source C-VLANs 110-149 100-109
Sink Port 3-IFU2-1 3-IFU2-1
Sink C-VLANs 110-149 100-109
Parameter NE3
NE4 to NE2 NE5 to NE2
Service ID 1 2
Service Name NE4toNE2_Vline NE5toNE2_Vline

Parameter NE3

Source Port 3-IFU2-1 4-IFU2-1
Sink Port 1-EM6T-1 1-EM6T-1
Sink C-VLANs 110-129 130-149

Parameter NE4
BTS2 to NE3 BTS3 to NE3
Service ID 1 2
Service Name BTS2toNE3_Vline BTS3toNE3_Vline

Sink C-VLANs 110-119 120-129

Parameter NE5
Service ID 1 2

Source Port 3-IFU2-1 1-EM6T-3

Parameter NE5
Sink C-VLANs 140-149 130-139

Parameter NE6
BTS5 to NE5
Service ID 1
Service Name BTS5toNE5_Vline
Direction UNI-UNI
Source C-VLANs 140-149
Sink Port 3-IFU2-1
Sink C-VLANs 140-149

configuring QoS.
QoS (Diffserv)
services be allocated by the service type. Then, the transmission network creates the
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 5-74. Each Ethernet port involved in the service uses the same DS
configuration.

PHB Service Class VLAN Priority Corresponding Service

Type
CS7 7 -
CS6 6 -

streaming services)
AF4 4 -


AF1 1 -

services)
NOTE

in this example.
CS7 SP
CS6 SP
EF SP

BE SP

In this example, the CAR processing needs to be performed on the DS edge node in the uplink
direction (from the BTS to the BSC) of the non-real-time R99 service on each BTS (that is, the
service with VLAN priority 2). Table 5-76 lists the CAR parameters.
Table 5-76 CAR parameters

Parameter Value
CIR 4096 kbit/s
CBS 51200 bytes
PIR 8192 kbit/s
PBS 102400 bytes
"Yellow" Packet Processing Mode Mapped to the EF queue
NOTE
The CBS/PBS is in direct proportion to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more the
burst packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytes
that are transmitted at CIR and PIR during a 100 ms period.
QoS (Port Shaping)

node.



This section describes the process for configuring Ethernet protection.


Procedure
of Ethernet ports.
Parameter Value
1-EM6F-1 1-EM6F-2
Enable Port Enabled Enabled
Max Frame Length(byte) 1536 1536
Parameter Value
1-EM6T-3 1-EM6T-1
Parameter Value
1-EM6T-1
Enable Port Enabled

Parameter Value
1-EM6T-1
Parameter Value
1-EM6T-3 1-EM6T-4
Parameter Value
1-EM6T-3
Enable Port Enabled
Parameter Value
1-EM6T-3
Enable Port Enabled
Step 2 See A.12.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes
of Ethernet ports.

Parameter Value
1-EM6F-1 1-EM6F-2
TAG Tag Aware Tag Aware
Parameter Value Range
1-EM6T-3 1-EM6T-1
Parameter Value
1-EM6T-1
TAG Tag Aware
Parameter Value
1-EM6T-3 1-EM6T-4
Parameter Value
1-EM6T-3
TAG Tag Aware
Parameter Value
1-EM6T-3
TAG Tag Aware
of IF_ETH ports.

Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1 4-IFU2-1 6-IFU2-1

Type
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 4-IFU2-1 6-IFU2-1
Encapsulation 802.1Q 802.1Q 802.1Q

Type
Parameter Value
3-IFU2-1
Step 4 See A.12.7.2 Setting the Layer 2 Attributes of the IF_ETH Port and set the Layer 2 attributes
of IF_ETH ports.

Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1 4-IFU2-1 6-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 4-IFU2-1 6-IFU2-1
Parameter Value
3-IFU2-1
Tag Tag Aware
----End


Procedure
Step 1 See A.12.2.1 Creating a LAG and create the LAG for NE1.
follows.
Parameter Value
LAG No. Select Automatically Assign
LAG Name ToBSC
LAG Type Static
Load Sharing Non-Sharing
System Priority 32768
The values for the relevant parameters that need to be set in the Port Settings tab page are
Parameter Value
Main Board 1-EM6F
Main Port 1 (PORT-1)
Selected Slave Ports 1-EM6F-2
----End

Procedure
Parameter Value
NE2 to BTS
Service ID 1
Service Name NE2toBSC_Vline
Direction UNI-UNI

Parameter Value
NE2 to BTS
Source VLANs 100-149
Sink Port 1-EM6F-1
Sink VLANs 100-149
Parameter Value
Service ID 1 2
Service Name NE3toNE1_Vline BTS1toNE1_Vline

Source VLANs 110-149 100-109
Sink VLANs 110-149 100-109
Parameter Value
Service ID 1 2
Service Name NE4toNE2_Vline NE5toNE2_Vline

Source Port 3-IFU2-1 4-IFU2-1
Source VLANs 110-129 130-149
Sink Port 1-EM6T-1 1-EM6T-1
Sink VLANs 110-129 130-149

Parameter Value
Service ID 1 2

Source VLANs 110-119 120-129
Sink VLANs 110-119 120-129
Parameter Value
Service ID 1 2

Source Port 3-IFU2-1 1-EM6T-3
Source VLANs 140-149 130-139
Sink VLANs 140-149 130-139
Parameter Value
BTS5 to NE5
Service ID 1
Service Name BTS5toNE5_Vline
Direction UNI-UNI

Parameter Value
BTS5 to NE5
Source VLANs 140-149
Sink Port 3-IFU2-1
Sink VLANs 140-149
----End

Procedure
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter Value
Packet Type CVLAN
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
0 BE
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7

The values for the related parameters that need to be set in the Egress Mapping Relation tab
BE 0
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7
NOTE
The values for the related parameters that need to be set in the Application Port tab page are
Paramete Value
r
Selected 3-IFU2-1 1-EM6T-3 3-IFU2-1 3-IFU2-1 1-EM6T-3 1-EM6T-3

Port 1-EM6F-1 1-EM6T-1 4-IFU2-1 1-EM6T-3 3-IFU2-1 3-IFU2-1
3-IFU2-1 1-EM6T-1 1-EM6T-4 4-IFU2-1
NOTE
The mapping relation defined in the default DS domain is the same as the mapping relation defined in the DS
domain that is created in this step. Therefore, you can skip this step.
Step 2 See A.12.10.4 Creating a Port Policy and create the port policy.
l The values for the related parameters of NE2, NE4, NE5, and NE6 are provided as follows.
Parameter Value
Policy ID 1 2
Policy Name Port_Comm Port_Car

Parameter Value
Grooming Police After SP (CS7, CS6, and EF) SP (CS7, CS6, and EF)
Reloading WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE)
Policy Weight(%) 5 (AF4) 5 (AF4)

60 (AF3) 60 (AF3)
30 (AF2) 30 (AF2)
5 (AF1) 5 (AF1)
Bandwidth Limit Disabled (for all PHB Disabled (for all PHB
service classes) service classes)
l The values for the related parameters of NE1 and NE3 are provided as follows.
Parameter Value
Policy ID 1

WRR (AF4 to AF1)
SP (BE)

60 (AF3)
30 (AF2)
5 (AF1)
Step 3 See A.12.10.6 Creating the Traffic and create the traffic on NE2, NE4, NE5, and NE6.
follows.
Parameter Value
Port_Car (Policy ID=2)
Traffic Classification ID 1
ACL Action Permit
The values for the related parameters that need to be set in the INGRESS tab page are provided
as follows.

Parameter Value
Match Type CVlan priority
Match Value 2
Wildcard 0
CoS -
Bandwidth Limit Enabled
CIR(kbit/s) 4096
PIR(kbit/s) 8192
CBS(byte) 51200
PBS(byte) 102400
Handling Mode Discard (red)

Remark (yellow)
Pass (green)
Relabeled CoS - (red)

EF (yellow)
- (green)
The values for the related parameters that need to be set in the EGRESS tab page are provided
as follows.
Parameter Value
Bandwidth Limit Disabled
policy.
Parameter Value
Port_Comm (Policy ID=1)
Port 3-IFU2-1
1-EM6F-1

Parameter Value
Port_Comm (Policy Port_Car (Policy ID=2)

ID=1)
Port 1-EM6T-1 1-EM6T-3

3-IFU2-1
Parameter Value
Port 3-IFU2-1
4-IFU2-1
1-EM6T-1
Parameter Value

ID=1)
Port 3-IFU2-1 1-EM6T-3

1-EM6T-4
Parameter Value

ID=1)

4-IFU2-1
Parameter Value

ID=1)
----End


Procedure
Step 1 See A.12.11.1 Creating an MD and configure the MD for NE1, NE2, NE4, NE5, and NE6.
Parameter Value
NE1 NE2 NE4 NE5 NE6
Maintenanc EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE

e Domain
Name
Maintenanc 4 4 4 4 4
e Domain
Level
Step 2 See A.12.11.2 Creating an MA and create the maintenance association (MA) for NE1, NE2,
NE4, NE5, and NE6.
Parameter Value
Maintenan EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE

ce Domain
Name
Maintenan BTS1_Vlin BTS2_Vlin BTS3_Vlin BTS4_Vlin BTS5_Vlin

ce e e e e e
Association
Name
Relevant 1- 1- 1- 1- 1-
Service NE2toBSC_ NE2toBSC_ NE2toBSC_ NE2toBSC_ NE2toBSC_
Vline Vline Vline Vline Vline
CC Test 1s 1s 1s 1s 1s
Transmit
Period
Parameter Value
Maintenance Domain Name EdgeNE
Maintenance Association Name BTS1_Vline
Relevant Service 2-BTS1toNE1_Vline

Parameter Value
CC Test Transmit Period 1s
Parameter Value
Maintenance Domain EdgeNE EdgeNE

Name
Maintenance Association BTS2_Vline BTS3_Vline

Name
Relevant Service 1-BTS2toNE3_Vline 2-BTS3toNE3_Vline
Parameter Value
Parameter Value
Step 3 See A.12.11.3 Creating an MEP Point and create the MEP for NE1, NE2, NE4, NE5, and NE6.
Parameter Value

ce Domain
Name

Parameter Value
Maintenan BTS1_Vlin BTS2_Vlin BTS3_Vlin BTS4_Vlin BTS5_Vlin

ce e e e e e
Association
Name
Board 1-EM6F 1-EM6F 1-EM6F 1-EM6F 1-EM6F
Port 1-EM6F-1 1-EM6F-1 1-EM6F-1 1-EM6F-1 1-EM6F-1
VLAN 100 110 120 130 140
MP ID 101 102 103 104 105
Direction Ingress Ingress Ingress Ingress Ingress
CC Status Active Active Active Active Active
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 100
MP ID 201
Direction Ingress
CC Status Active
Parameter Value

Name

Name
Board 1-EM6T 1-EM6T
VLAN 110 120
MP ID 401 402
Direction Ingress Ingress

Parameter Value
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 130
MP ID 501
Direction Ingress
CC Status Active
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 140
MP ID 601
Direction Ingress
CC Status Active
Step 4 See A.12.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1,
NE2, NE4, NE5, and NE6.
The values for the related parameters of NE1 are provided as follows.
Parameter Value

e Domain
Name

Parameter Value
Maintenanc BTS1_Vline BTS2_Vline BTS3_Vline BTS4_Vline BTS5_Vline

e
Association
Name
Remote 201 401 402 501 601

Maintenanc
e Point ID
(e.g:1,3-6)
Parameter Value
Remote Maintenance Point ID(e.g:1,3-6) 101
Parameter Value

Name

Name

ID(e.g:1,3-6)
Parameter Value
Parameter Value

Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services
on NE1.
l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 201 as the sink MEP.
There should be no packets lost during the LB tests.
----End
5.5 Configuration Example (QinQ-Based E-Line Service)

This section considers a QinQ-based E-line service as an example to describe how to configure

service.

configure Ethernet services according to the following actual requirements:

l The VLANs used by the services on a BTS must allocated by the BTS. Therefore, the
VLANs of services on different BTSes may be the same. To solve this problem, the BSC
allocates an S-VLAN tag for each BTS, and the S-VLAN IDs on the entire network are
planned in a unified manner.

To meet the preceding requirements, QinQ-based E-Line services are configured for service
transmission on each NE; in addition, corresponding LAG protection and QoS processing are
configured.
Figure 5-31 Networking diagram (QinQ-based E-Line services)

BTS2
15 Mbit/s
S-VLAN 110
FE
GE GE
FE NE4
BTS3
20 Mbit/s FE
S-VLAN 120
NE3 NE2 NE1
BSC
120 Mbit/s
FE BTS1 S-VLAN 100, 110,120,130,140
FE 45 Mbit/s
NE6 NE5 S-VLAN 100
BTS4
BTS5 25 Mbit/s
15 Mbit/s S-VLAN 130
S-VLAN 140
NOTE
In this example, the BSC is capable of processing S-VLAN tags.

therefore improving
link reliability.

radio.
1+1 HSB protection
group



BTS1.

radio.
1+1 HSB protection
group

radio.
1+1 HSB protection
group

radio.
1+1 HSB protection
group


radio.


1+1 HSB protection
group

BTS2.

BTS3.


services on Hybrid
radio.

radio.
1+1 HSB protection
group

BTS4.


Hybrid radio.

services from BTS5.

service.


configuring QoS.

Ethernet Port
service.
Encapsulation Type QinQ QinQ

(byte)
QinQ Type Domain 0x8100 0x8100
Encapsulation Type Null QinQ

(byte)

QinQ Type Domain - 0x88a8

Parameter 1-EM6T-1
Encapsulation Type QinQ
QinQ Type Domain 0x88a8

Encapsulation Type Null Null

(byte)
QinQ Type Domain - -

Parameter 1-EM6T-3
QinQ Type Domain -

Parameter 1-EM6T-3
QinQ Type Domain -
NOTE
l If the Ethernet services on each BTS do not contain any untagged frames, you can set Encapsulation
Type to 802.1Q and set Tag to Tag Aware for the FE port that accesses the Ethernet services on each BTS.
l In this example, the FE ports on all the BTSs work in the auto-negotiation mode. Hence, the FE port of each
NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet port works in another
mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside
the network are planned as auto-negotiation.
equipment.
l In this example, the SVLAN T-PID that the BSC can identify is 0x8100. Hence, you need to set QinQ Type
Domain to 0x8100 for the two GE ports connecting to the BSC. The other NNI ports connect to internal
equipment. Hence, you need to set QinQ Type Domain to 0x88a8 for the other NNI ports.

Tag 0x88a8 0x88a8
Tag 0x88a8 0x88a8

Encapsulation QinQ QinQ QinQ QinQ

Type
Tag 0x88a8 0x88a8 0x88a8 0x88a8

Discard
Enabled
Tag 0x88a8 0x88a8
Encapsulation Type QinQ QinQ QinQ
Tag 0x88a8 0x88a8 0x88a8

Enabled
Parameter 3-IFU2-1
Tag 0x88a8

NOTE
l The IF_ETH ports connect to internal equipment. Hence, you need to set QinQ Type Domain to 0x88a8
for the IF_ETH ports.
l The majority of the backhaul services on the BTS are Internet services. Hence, the error frame discarding

Parameter NE1
Main Port 1-EM6F-1
Slave Port 1-EM6F-2
NOTE

Table 5-96 to Table 5-101 provide the detailed service planning information.
Table 5-96 QinQ-based E-Line service (NE1)
Parameter NE1
BTS1 to BTS2 to BTS3 to BTS4 to BTS5 to

BSC BSC BSC BSC BSC
Service ID 1 2 3 4 5
Service BTS1_Qline BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline

Name

Parameter NE1

BSC BSC BSC BSC BSC
Direction NNI-NNI NNI-NNI NNI-NNI NNI-NNI NNI-NNI
BPDU Not Not Not Not Not

Transparentl Transparentl Transparentl Transparentl Transparentl
y y y y y
Transmitted Transmitted Transmitted Transmitted Transmitted
Source Port - - - - -
Source C- - - - - -
VLANs
Source QinQ ID: 6 ID: 7 ID: 8 ID: 9 ID: 10

link Port: 3- Port: 3- Port: 3- Port: 3- Port: 3-
IFU2-1 IFU2-1 IFU2-1 IFU2-1 IFU2-1
S-VLAN: S-VLAN: S-VLAN: S-VLAN: S-VLAN:
100 110 120 130 140
Sink QinQ ID: 1 ID: 2 ID: 3 ID: 4 ID: 5

EM6F-1 EM6F-1 EM6F-1 EM6F-1 EM6F-1
100 110 120 130 140

Parameter NE2

NE1 NE1 NE1 NE1 NE1
Service BTS1_Qline BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline

Name
Direction UNI-NNI NNI-NNI NNI-NNI NNI-NNI NNI-NNI

Transparentl Transparentl Transparentl Transparentl Transparentl
y y y y y
Source Port 1-EM6T-3 - - - -
Source C- Blank - - - -
VLANs

Parameter NE2

NE1 NE1 NE1 NE1 NE1
Source QinQ - ID: 6 ID: 7 ID: 8 ID: 9

link Port: 1- Port: 1- Port: 1- Port: 1-
EM6T-1 EM6T-1 EM6T-1 EM6T-1
S-VLAN: S-VLAN: S-VLAN: S-VLAN:
110 120 130 140
Sink QinQ ID: 1 ID: 2 ID: 3 ID: 4 ID: 5

IFU2-1 IFU2-1 IFU2-1 IFU2-1 IFU2-1
100 110 120 130 140

Parameter NE3
BTS2 to NE1 BTS3 to NE1 BTS4 to NE1 BTS5 to NE1
Service ID 1 2 3 4
Service Name BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline
Direction NNI-NNI NNI-NNI NNI-NNI NNI-NNI
BPDU Not Not Not Not

Transparently Transparently Transparently Transparently
Transmitted Transmitted Transmitted Transmitted
Source Port - - - -
Source C- - - - -
VLANs
Source QinQ ID: 5 ID: 6 ID: 7 ID: 8

link Port: 3-IFU2-1 Port: 3-IFU2-1 Port: 4-IFU2-1 Port: 4-IFU2-1
S-VLAN: 110 S-VLAN: 120 S-VLAN: 130 S-VLAN: 140
Sink QinQ link ID: 1 ID: 2 ID: 3 ID: 4

Port: 1-EM6T-1 Port: 1-EM6T-1 Port: 1-EM6T-1 Port: 1-EM6T-1
S-VLAN: 110 S-VLAN: 120 S-VLAN: 130 S-VLAN: 140


Parameter NE4
Service ID 1 2
Service Name BTS2_Qline BTS3_Qline
Direction UNI-NNI UNI-NNI

Source C-VLANs Blank Blank
Source QinQ link - -
Sink QinQ link ID: 1 ID: 2

Port: 3-IFU2-1 Port: 3-IFU2-1
S-VLAN: 110 S-VLAN: 120

Parameter NE5
Service ID 1 2
Direction UNI-NNI NNI-NNI

Source Port 1-EM6T-3 -
Source C-VLANs Blank -
Source QinQ link - ID: 3

Port: 3-IFU2-1
S-VLAN: 140
Sink QinQ link ID: 1 ID: 2

Port: 4-IFU2-1 Port: 4-IFU2-1
S-VLAN: 130 S-VLAN: 140

Parameter NE6
BTS5 to NE5
Service ID 1
Service Name BTS5_Qline
Direction UNI-NNI
Source QinQ link -
Sink QinQ link ID: 1

Port: 3-IFU2-1
S-VLAN: 140

configuring QoS.
QoS (Diffserv)
configuration.

Type
CS7 7 -
CS6 6 -

streaming services)


Type
AF4 4 -


AF1 1 -

services)
NOTE

in this example.

CS7 SP
CS6 SP
EF SP
BE SP

QoS (CAR or Shaping for a Specified Service)

To perform the CAR or shaping processing for a specified service, you need to configure the
DS edge node accordingly.
Parameter Value
CIR 4096 kbit/s
CBS 51200 bytes
PIR 8192 kbit/s
PBS 102400 bytes
In this example, the shaping processing needs to be performed in the uplink direction (from the
BTS to the BSC) of the real-time OM and HSDPA services on each BTS. Table 5-105 lists the
shaping parameters.
Table 5-105 Shaping parameters
Parameter Value
CIR 2048 kbit/s
CBS 25600 bytes
PIR 4096 kbit/s
PBS 51200 bytes
NOTE
QoS (Port Shaping)

node.




Procedure
of Ethernet ports.
Parameter Value
1-EM6F-1 1-EM6F-2
Parameter Value
1-EM6T-3 1-EM6T-1
Encapsulation Type Null QinQ

Parameter Value
1-EM6T-1
Enable Port Enabled
Parameter Value
1-EM6T-3 1-EM6T-4
Parameter Value
1-EM6T-3
Enable Port Enabled
Parameter Value
1-EM6T-3
Enable Port Enabled

Step 2 See A.12.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of
Ethernet ports for NE1.
Parameter Value
1-EM6F-1 1-EM6F-2
QinQ Type Domain 81 00 81 00
of IF_ETH ports.
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1 4-IFU2-1 6-IFU2-1

Type
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 4-IFU2-1 6-IFU2-1
Encapsulation QinQ QinQ QinQ

Type

Parameter Value
3-IFU2-1
----End

Procedure
follows.
Parameter Value
LAG Name ToBSC
LAG Type Static
Parameter Value
Main Board 1-EM6F
----End


Procedure
Step 1 See A.12.3.1 Configuring the QinQ Link and configure a QinQ link.
QinQ Link ID Board Port S-Vlan ID
1 1-EM6F 1 100
2 1-EM6F 1 110
3 1-EM6F 1 120
4 1-EM6F 1 130
5 1-EM6F 1 140
6 3-IFU2 1 100
7 3-IFU2 1 110
8 3-IFU2 1 120
9 3-IFU2 1 130
10 3-IFU2 1 140
1 3-IFU2 1 100
2 3-IFU2 1 110
3 3-IFU2 1 120
4 3-IFU2 1 130
5 3-IFU2 1 140
6 1-EM6T 1 110
7 1-EM6T 1 120
8 1-EM6T 1 130
9 1-EM6T 1 140
1 1-EM6T 1 110
2 1-EM6T 1 120
3 1-EM6T 1 130

4 1-EM6T 1 140
5 3-IFU2 1 110
6 3-IFU2 1 120
7 4-IFU2 1 130
8 4-IFU2 1 140
1 3-IFU2 1 110
2 3-IFU2 1 120
1 4-IFU2 1 130
2 4-IFU2 1 140
3 3-IFU2 1 140
1 3-IFU2 1 140
Parameter Value

BSC BSC BSC BSC BSC
Service BTS1_Qlin BTS2_Qlin BTS3_Qlin BTS4_Qlin BTS5_Qlin

Name e e e e e

Parameter Value

BSC BSC BSC BSC BSC

Transparent Transparent Transparent Transparent Transparent
ly ly ly ly ly
QinQ Link 6 7 8 9 10
ID 1
QinQ Link 1 2 3 4 5
ID 2
Parameter Value

NE1 NE1 NE1 NE1 NE1

Name e e e e e

Transparent Transparent Transparent Transparent Transparent
ly ly ly ly ly
Source Port 1-EM6T-3 - - - -
Source Blank - - - -
VLANs
QinQ Link 1 - - - -
ID
QinQ Link - 6 7 8 9
ID 1
QinQ Link - 2 3 4 5
ID 2
Parameter Value
Service ID 1 2 3 4

Parameter Value
Service Name BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline
Direction NNI-NNI NNI-NNI NNI-NNI NNI-NNI
BPDU Not Not Not Not

Transparently Transparently Transparently Transparently
Transmitted Transmitted Transmitted Transmitted
QinQ Link ID 5 6 7 8
1
QinQ Link ID 1 2 3 4
2
Parameter Value
Service ID 1 2
Direction UNI-NNI UNI-NNI

Source VLANs Blank Blank
QinQ Link ID 1 2
Parameter Value
Service ID 1 2
Direction UNI-NNI NNI-NNI

Source Port 1-EM6T-3 -
Source VLANs Blank -

Parameter Value
QinQ Link ID 1 -
QinQ Link ID 1 - 3
QinQ Link ID 2 - 2
Parameter Value
BTS5 to NE5
Service ID 1
Service Name BTS5_Qline
Direction UNI-NNI
Source VLANs Blank
QinQ Link ID 1
----End

Procedure
follows.
Parameter Value
Packet Type CVLAN

0 0 BE
1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7
BE 0 0
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7
NOTE
Paramete Value
r

3-IFU2-1 1-EM6T-1 1-EM6T-4 4-IFU2-1

Step 2 See A.12.10.3 Changing the Ports That Use the DS Domain and change the ports that use the
DS domain.
Selected Port Packet Type
3-IFU2-1 SVLAN
SVLAN
1-EM6F-1 SVLAN
1-EM6T-3 CVLAN
1-EM6T-1 SVLAN
3-IFU2-1 SVLAN
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
1-EM6T-1 SVLAN
1-EM6T-3 CVLAN
1-EM6T-4 CVLAN
3-IFU2-1 SVLAN
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
1-EM6T-3 cvlan

3-IFU2-1 SVLAN
1-EM6T-3 CVLAN
Parameter Value
Policy ID 1

WRR (AF4 to AF1)
SP (BE)

60 (AF3)
30 (AF2)
5 (AF1)
Parameter Value
Policy ID 1 2 3
Policy Name Port_Comm Port_Car Port_Shaping
Grooming Police SP (CS7, CS6, and SP (CS7, CS6, and SP (CS7, CS6, and
After Reloading EF) EF) EF)
WRR (AF4 to AF1) WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE) SP (BE)
Policy Weight(%) 5 (AF4) 5 (AF4) 5 (AF4)

60 (AF3) 60 (AF3) 60 (AF3)
30 (AF2) 30 (AF2) 30 (AF2)
5 (AF1) 5 (AF1) 5 (AF1)
Bandwidth Limit Disabled (for all Disabled (for all Disabled (for all
PHB service PHB service PHB service
classes) classes) classes)

Parameter Value
Policy ID 1 2
Policy Name Port_Car Port_Shaping
SP (BE) SP (BE)

60 (AF3) 60 (AF3)
30 (AF2) 30 (AF2)
5 (AF1) 5 (AF1)
Step 4 See A.12.10.6 Creating the Traffic and create the traffic for NE2, NE4, NE5, and NE6.
l Parameters of NE2
The values for the related parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Port_Car (Policy ID=2) Port_Shaping (Policy

ID=3)
Traffic Classification ID 1 1
ACL Action Permit Permit
The values for the related parameters that need to be set in the INGRESS tab page are
Parameter Value
Port_Car (Policy Port_Shaping (Policy ID=3)

ID=2)
Match Type CVlan priority SVlan ID SVlan priority
Match Value 2 100 3
CoS - -
Bandwidth Limit Enabled Disabled
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -

Parameter Value

ID=2)
CBS(byte) 51200 -
PBS(byte) 102400 -
Handling Mode Discard (red) -

Remark (yellow)
Pass (green)
Relabeled CoS - (red) -

EF (yellow)
- (green)
as follows.
Parameter Value

ID=3)
Bandwidth Limit Disabled Enabled
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE4
as follows.
Parameter Value

ID=1)
Traffic 1 1 2
Classification ID
ACL Action Permit Permit Permit

Parameter Value
Port_Car Port_Shaping (Policy Port_Shaping (Policy

(Policy ID=2, Traffic ID=2, Traffic
ID=1) Classification ID=1) Classification ID=2)
Match CVlan SVlan ID SVlan SVlan ID SVlan

Type priority priority priority
Match 2 110 3 120 3

Value
CoS - - -
Bandwidth Enabled Disabled Disabled

Limit
CIR(kbit/s) 4096 - -
PIR(kbit/s) 8192 - -
CBS(byte) 51200 - -
PBS(byte) 102400 - -
Handling Discard - -
Mode (red)
Remark
(yellow)
Pass (green)
Relabeled - (red) - -
CoS EF (yellow)
- (green)
as follows.
Parameter Value
Port_Car (Policy Port_Shaping Port_Shaping

ID=1) (Policy ID=2, (Policy ID=2,
Traffic Traffic
Classification Classification
ID=1) ID=2)
Bandwidth Limit Disabled Enabled Enabled
CIR(kbit/s) - 2048 2048
PIR(kbit/s) - 4096 4096
CBS(byte) - 25600 25600

Parameter Value

Traffic Traffic
ID=1) ID=2)
PBS(byte) - 51200 51200
l Parameters of NE5
as follows.
Parameter Value

ID=3)
Parameter Value

ID=2)
Match Value 2 130 3
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -

Remark (yellow)
Pass (green)

Parameter Value

ID=2)

EF (yellow)
- (green)
as follows.
Parameter Value

ID=3)
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE6:
as follows.
Parameter Value

ID=2)
Parameter Value

ID=1)
Match Value 2 140 3

Parameter Value

ID=1)
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -

Remark (yellow)
Pass (green)

EF (yellow)
- (green)
as follows.
Parameter Value

ID=2)
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
policy.
Parameter Value
Port 3-IFU2-1
1-EM6F-1

Parameter Value
Port_Comm Port_Car (Policy Port_Shaping

(Policy ID=1) ID=2) (Policy ID=3)
Port 1-EM6T-1 1-EM6T-3 3-IFU2-1
Parameter Value
Port 3-IFU2-1
4-IFU2-1
1-EM6T-1
Parameter Value

ID=2)

1-EM6T-4
Parameter Value

Port 3-IFU2-1 1-EM6T-3 4-IFU2-1
Parameter Value

ID=2)
----End


Procedure
Parameter Value
NE1 NE2 NE4 NE5 NE6

e Domain
Name
e Domain
Level
Step 2 See A.12.11.2 Creating an MA and create the MA for NE1, NE2, NE4, NE5, and NE6.
Parameter Value

ce Domain
Name
Maintenan BTS1_Qlin BTS2_Qlin BTS3_Qlin BTS4_Qlin BTS5_Qlin

ce e e e e e
Association
Name
Relevant 1- 2- 3- 4- 5-
e e e e e
Transmit
Period
Parameter Value
Maintenance Association Name BTS1_Qline
Relevant Service 1-BTS1_Qline

Parameter Value
Parameter Value

Name
Maintenance Association BTS2_Qline BTS3_Qline

Name
Relevant Service 1-BTS2_Qline 2-BTS3_Qline
Parameter Value
Parameter Value
Parameter Value

ce Domain
Name

Parameter Value
Maintenan BTS1_Qlin BTS2_Qlin BTS3_Qlin BTS4_Qlin BTS5_Qlin

ce e e e e e
Association
Name
VLAN 100 110 120 130 140
MP ID 101 102 103 104 105
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 201
Direction Ingress
CC Status Active
Parameter Value

Name

Name
Board 1-EM6T 1-EM6T
VLAN - -
MP ID 401 402

Parameter Value
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 501
Direction Ingress
CC Status Active
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 601
Direction Ingress
CC Status Active
Parameter Value

e Domain
Name

Parameter Value
Maintenanc BTS1_Qline BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline

e
Association
Name
Remote 201 401 402 501 601

Maintenanc
e Point ID
(e.g:1,3-6)
Parameter Value
Parameter Value

Name

Name

ID(e.g:1,3-6)
Parameter Value
Parameter Value

Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services
on NE1.
----End
5.6 Configuration Example (802.1d-Bridge-Based E-LAN

Service)
This section considers an 802.1d-bridge-based E-LAN service as an example to describe how

service.

Based on 3.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network),

l The Ethernet services on the ring network are protected.
l The BTS services must be transparently transmitted.

To meet the preceding requirements, IEEE 802.1d bridge-based E-LAN services are configured
to implement transmission of the BTS services; in addition, corresponding LAG protection,
ERPS protection, and QoS processing are configured. See Figure 5-32.
Figure 5-32 Networking diagram (IEEE 802.1d bridge-based E-LAN services)

BSC
40 Mbit/s 802.1d bridge
BTS1
10 Mbit/s GE
NE1
FE
FE
FE
ERPS
BTS2 NE2 NE4 BTS4

10 Mbit/s 802.1d bridge 802.1d bridge
10 Mbit/s
FE
NE3
802.1d bridge BTS3
10 Mbit/s

Between NE1 and 1-EM6T-1 Main port of a LAG Configure these ports
1-EM6T-2 Slave port of a LAG sharing LAG,
therefore improving
link reliability.
Between NE1 and 4-IFU2-1 East port of an ERPS Configure this port to
NE2 ring node transmit Ethernet
Main IF board of a 1 services on Hybrid
+1 HSB protection radio.
group

1+1 HSB protection
group

Between NE1 and 3-IFU2-1 West port of an Configure this port to

NE4 ERPS ring node transmit Ethernet
group

1+1 HSB protection
group

services on Hybrid
radio.

BTS1.

BTS2.

group

1+1 HSB protection
group

Between NE3 and 4-IFU2-1 l East port of an Configure this port to

l RPL port services on Hybrid
radio.


BTS3.

services on Hybrid
radio.
group

1+1 HSB protection
group

BTS4.

services on Hybrid
radio.

service.



configuring QoS.

Ethernet Port
service.

(byte)
Loopback Check Disabled Disabled
Loopback Port Shutdown Disabled Disabled
Enabling Broadcast Packet Disabled Disabled

Suppression
Broadcast Packet - -
Suppression Threshold

(byte)


Suppression

Parameter 1-EM6T-3
Loopback Check Disabled
Loopback Port Shutdown Disabled (default value)
Enabling Broadcast Packet Suppression Disabled (default value)
Broadcast Packet Suppression Threshold -

Parameter 1-EM6T-3
Loopback Check Disabled (default value)
Loopback Port Shutdown Disabled (default value)
Enabling Broadcast Packet Suppression Disabled (default value)

NOTE
l In this example, the FE/GE port on the BTS/BSC works in the auto-negotiation mode. Hence, the FE/GE
port of each NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet port
works in another mode, the local Ethernet port must work in the same mode. The working modes of the
Ethernet ports inside the network are planned as auto-negotiation.
equipment.
l In this example, the loopback check, loopback port shutdown, and broadcast packet suppression functions
need not be enabled.

Table 5-114 IF_ETH port
Encapsulation Null Null Null Null

Type

Discard
Encapsulation Type Null Null Null
Encapsulation Type Null Null Null

NOTE
The majority of the backhaul services on the BTS are Internet services. Hence, the error frame discarding function
needs to be enabled.

LAG
Parameter NE1
Main Port 1-EM6T-1
Slave Port 1-EM6T-2
NOTE
ERPS Instance
Table 5-119 provides the information about ERPS.
Table 5-119 ERPS instance
Parameter NE1 NE2 NE3 NE4
East Port 4-IFU2-1 4-IFU2-1 4-IFU2-1 4-IFU2-1
West Port 3-IFU2-1 3-IFU2-1 3-IFU2-1 3-IFU2-1

RPLOwner No No Yes No
Ring Node Flag
RPL Port - - 4-IFU2-1 -
Control VLAN 4093 4093 4093 4093
Packet Transmit 5s (default 5s (default 5s (default 5s (default

Interval value) value) value) value)
Entity Level 4 (default value) 4 (default value) 4 (default value) 4 (default value)
WTR Time 600s (default 600s (default 600s (default 600s (default
value) value) value) value)
Guard Time 500 ms (default 500 ms (default 500 ms (default 500 ms (default
Hold-Off Time 0s (default 0s (default 0s (default 0s (default

NOTE
l In this example, all the services are aggregated on NE1. Hence, the NE that is farthest from NE1 needs to
function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link is
relatively even.
l The control VLAN needs to use a VLAN that is not used by any service. Considering that the inband DCN
uses VLAN 4094, it is recommended that the control VLAN use VLAN 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally use the default
values.

Table 5-120 802.1d-bridge-based E-LAN service
Service ID 1 1 1 1
Service Name Dlan Dlan Dlan Dlan
Tag Type Tag- Tag- Tag- Tag-

Transparent Transparent Transparent Transparent
Self-Learning Enabled Enabled Enabled Enabled

MAC Address

MAC Address SVL SVL SVL SVL

Learning Mode
Mounted UNI 1-EM6T-1 1-EM6T-3 1-EM6T-3 1-EM6T-3

Port 3-IFU2-1 1-EM6T-4 3-IFU2-1 3-IFU2-1
4-IFU2-1 3-IFU2-1 4-IFU2-1 4-IFU2-1
4-IFU2-1
NOTE
In this example, ERPS is adopted to prevent network loop. Therefore, the split horizon group cannot be used.

configuring QoS.
QoS (Diffserv)
configuration.

Type
CS7 7 -
CS6 6 -

streaming services)
AF4 4 -



Type

AF1 1 -

services)
NOTE

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

from the BTS.

QoS (Port Shaping)

node.



Procedure
Step 1 See A.12.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
1-EM6T-1 1-EM6T-2

1-EM6T-3 1-EM6T-4
1-EM6T-3
Enable Port Enabled
Step 2 See A.12.7.1 Setting the General Attributes of the IF_ETH Port and set the basic attributes
of the IF_ETH ports.
3-IFU2-1 4-IFU2-1 5-IFU2-1 6-IFU2-1

Type
3-IFU2-1 4-IFU2-1 5-IFU2-1
Encapsulation Null Null Null

Type
l The values for the relevant parameters of N3 are provided as follows.
3-IFU2-1 4-IFU2-1

3-IFU2-1 4-IFU2-1 6-IFU2-1

Type
----End

Procedure
Step 1 See A.12.2.1 Creating a LAG and create the LAG on NE1.
follows.
LAG No. Select Automatically Assign.
LAG Name ToBSC
LAG Type Static
The values for the related parameters that need to be set in Port Settings are provided as follows.
Main Board 1-EM6T
Selected Slave Ports 1-EM6T-2
Step 2 See A.12.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.

NE1 NE2 NE3 NE4
ERPS ID 1 1 1 1
Ring Node Flag
Control VLAN 4093 4093 4093 4093
----End

Procedure
Step 1 See A.12.3.4 Configuring the E-LAN Service and configure the E-LAN services.
l Parameters of NE1
as follows.
Service ID 1
Service Name Dlan
Tag Type Tag-Transparent
Self-Learning MAC Address Enabled
The values for the related parameters that need to be set in the UNI tab page are provided as
follows.
Port SVLAN VLANs/CVLAN
1-EM6T-1 - Blank
3-IFU2-1 - Blank
4-IFU2-1 - Blank
l Parameters of NE2

as follows.
Service ID 1
Service Name Dlan
follows.
1-EM6T-3 - Blank
1-EM6T-4 - Blank
3-IFU2-1 - Blank
4-IFU2-1 - Blank
l Parameters of NE3 and NE4

as follows.
Service ID 1
Service Name Dlan
follows.
1-EM6T-3 - Blank
3-IFU2-1 - Blank
4-IFU2-1 - Blank
----End


Procedure
follows.
Packet Type CVLAN
0 BE
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7
BE 0
AF11 1
AF21 2
AF31 3

AF41 4
EF 5
CS6 6
CS7 7
NOTE
The values for the related parameters that need to be set in the Apply Port tab page are provided
as follows.
NE1 NE2 NE3 NE4
Selected Port 1-EM6T-1 1-EM6T-3 1-EM6T-3 1-EM6T-3

3-IFU2-1 1-EM6T-4 3-IFU2-1 3-IFU2-1
4-IFU2-1 3-IFU2-1 4-IFU2-1 4-IFU2-1
4-IFU2-1
The values for the related parameters of each NE are provided as follows.
Policy ID 1

WRR (AF4 to AF1)
SP (BE)

60 (AF3)
30 (AF2)
5 (AF1)
Step 3 See A.12.10.7 Setting the Port That Uses the Port Policy and set the port that uses the port
policy.

Port 1-EM6T-1
3-IFU2-1
4-IFU2-1
Port 1-EM6T-3
1-EM6T-4
3-IFU2-1
4-IFU2-1
Port 1-EM6T-3
3-IFU2-1
4-IFU2-1
----End

Procedure
Step 1 See A.12.11.1 Creating an MD and create the MDs.
NE1 NE2 NE3 NE4
Maintenance EdgeNE EdgeNE EdgeNE EdgeNE

Domain Name

NE1 NE2 NE3 NE4
Maintenance 4 4 4 4
Domain Level
Step 2 See A.12.11.2 Creating an MA and create the MA.
NE1 NE2 NE3 NE4

Domain Name
Maintenance Dlan Dlan Dlan Dlan

Association
Name
Relevant 1-Dlan 1-Dlan 1-Dlan 1-Dlan

Service
CC Test 1s 1s 1s 1s
Transmit
Period
Step 3 See A.12.11.3 Creating an MEP Point and create the MEP points.
NE1 NE2 NE3 NE4

e Domain
Name
Maintenanc Dlan Dlan Dlan Dlan Dlan

e
Association
Name
Board 1-EM6T 1-EM6T 1-EM6T 1-EM6T 1-EM6T
Port 1-EM6T-1 1-EM6T-3 1-EM6T-4 1-EM6T-3 1-EM6T-3
VLAN - - - - -
MP ID 101 201 202 301 401

NE1 NE2 NE3 NE4
Step 4 See A.12.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1
to NE4.
Parameter Value

Domain Name
Maintenance Dlan Dlan Dlan Dlan

Association
Name
Remote 201 202 301 401

Maintenance
Point ID(e.g:
1,3-6)
Parameter Value
Maintenance Association Name Dlan
Parameter Value
Parameter Value

Step 5 See perform an LB test to test the Ethernet service configurations and test the E-LAN
services.
----End
5.7 Configuration Example (802.1q-Bridge-Based E-LAN

Service)
This section considers an 802.1q-bridge-based E-LAN service as an example to describe how

You need to plan the corresponding parameter information before service configuration.


l BTS1 to BTS3 belong to domain 1; BTS4 and BTS5 belong to domain 2. The base stations
in a domain have the same VLAN ID and the data from different domains is isolated from
each other by using the VLAN IDs.
l The BSC provides GE optical ports whose port rate is 1000 Mbit/s.
To meet the preceding requirements, IEEE 802.1q bridge-based E-LAN services are configured
for service transmission on each NE; in addition, corresponding LAG protection and QoS
processing are configured.

Figure 5-33 Networking diagram (IEEE 802.1q bridge-based E-LAN services)

BTS2
15 Mbit/s
VLAN 110-119
FE
Domain 1
VLAN 110-119
FE NE4
BTS3
20 Mbit/s GE GE
VLAN 110-119
FE
NE3 NE2 NE1 BSC
120 Mbit/s
Domain 2 VLAN 110-129
BTS1
VLAN 120-129 45 Mbti/s
VLAN 110-119
FE
FE
NE6 NE5
BTS4
BTS5 25 Mbit/s
15 Mbit/s VLAN 120-129
VLAN 120-129

therefore improving
link reliability.

radio.
1+1 HSB protection
group




BTS1.

radio.
1+1 HSB protection
group


radio.
1+1 HSB protection
group

radio.
1+1 HSB protection
group



radio.
1+1 HSB protection
group


BTS2.

BTS3.


services on Hybrid
radio.

radio.
1+1 HSB protection
group

BTS4.


Hybrid radio.

services from BTS5.


This section provides the information about all the parameters required for configuring Ethernet
ports.


protection.
services.
configuring QoS.

ports.
Information About Ethernet Ports

service.
Table 5-129 Information about Ethernet ports (NE1)
Encapsulation type 802.1Q 802.1Q
Port working mode Auto-negotiation Auto-negotiation
Maximum frame length 1536 1536

(byte)
Flow control Disabled Disabled
TAG attribute Tag Aware Tag Aware
Loopback check Disabled Disabled
Loopback port shutdown Disabled Disabled
Enabling broadcast packet Disabled Disabled

suppression
Broadcast packet - -
suppression threshold


(byte)

suppression
Parameter 1-EM6T-1
Encapsulation type 802.1Q
Port working mode Auto-negotiation
Maximum frame length (byte) 1536
Flow control Disabled
TAG attribute Tag Aware
Loopback check Disabled
Loopback port shutdown Disabled
Enabling broadcast packet suppression Disabled
Broadcast packet suppression threshold -

(byte)


suppression

Parameter 1-EM6T-3

Parameter 1-EM6T-3

NOTE
l In this example, the FE/GE port on the BTS/BSC works in auto-negotiation mode. Therefore, the FE/GE
port on each NE that transmits/receives services must work in auto-negotiation mode. For example, if the
peer Ethernet port changes to another working mode, the local Ethernet port also needs to change to the
same working mode accordingly. Plan the Ethernet ports within a network to work in auto-negotiation mode.
l In this example, all the services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag
Aware.
QoS processing. The flow control planning on the NE must match the flow control planning on the peer
equipment.
l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is
enabled.

Table 5-135 to Table 5-140 provide the information about the IF_ETH ports that carry the
Ethernet service.
Table 5-135 Information about the IF_ETH ports (NE1)

Error frame discard Enabled Enabled



type
TAG attribute Tag Aware Tag Aware Tag Aware Tag Aware
Error frame Enabled Enabled Enabled Enabled

discard

Encapsulation type 802.1Q 802.1Q 802.1Q
TAG attribute Tag Aware Tag Aware Tag Aware
Error frame discard Enabled Enabled Enabled
Parameter 3-IFU2-1
Error frame discard Enabled
NOTE
The majority of the backhaul services on the BTS are Internet services. Therefore, the errored frame discarding

protection.
Parameter NE1

Parameter NE1
Main Port 1-EM6F-1
Slave Port 1-EM6F-2
NOTE

services.
Table 5-142 provides the planning information about the Ethernet service.
Table 5-142 Information about IEEE 802.1q bridge-based E-LAN services

Paramete NE1 NE2 NE3 NE4 NE5 NE6
r
Service ID 1 1 1 1 1 1
Service Qlan Qlan Qlan Qlan Qlan Qlan

name
TAG type C-awared C-awared C-awared C-awared C-awared C-awared
Self- Enabled Enabled Enabled Enabled Enabled Enabled

learning
MAC
address
MAC IVL IVL IVL IVL IVL IVL

address
learning
mode

Paramete NE1 NE2 NE3 NE4 NE5 NE6

r
Mounted 1-EM6F-1 1-EM6T-1 3-IFU2-1 3-IFU2-1 3-IFU2-1 3-IFU2-1

UNI port (VLAN (VLAN (VLAN (VLAN (VLAN (VLAN
ID: ID: ID: ID: ID: ID:
110-129) 110-129) 110-119) 110-119) 120-129) 120-129)
3-IFU2-1 1-EM6T-3 4-IFU2-1 1-EM6T-3 4-IFU2-1 1-EM6T-3
(VLAN (VLAN (VLAN (VLAN (VLAN (VLAN
ID: ID: ID: ID: ID: ID:
110-129) 110-119) 120-129) 110-119) 120-129) 120-129)
3-IFU2-1 1-EM6T-1 1-EM6T-4 1-EM6T-3
(VLAN (VLAN (VLAN (VLAN
ID: ID: ID: ID:
110-129) 110-129) 110-119) 120-129)
NOTE
In this example, the split horizon group is not used.

configuring QoS.
QoS (Diffserv)
configuration.

Type
CS7 7 -
CS6 6 -

streaming services)
AF4 4 -


Type


AF1 1 -

services)
NOTE

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


Parameter Value
CIR 4096 kbit/s
CBS 51200 bytes
PIR 8192 kbit/s
PBS 102400 bytes
NOTE
QoS (Port Shaping)

node.




Procedure
of Ethernet ports.
Parameter Value
1-EM6F-1 1-EM6F-2
Parameter Value
1-EM6T-3 1-EM6T-1
Parameter Value
1-EM6T-1
Enable Port Enabled
Parameter Value
1-EM6T-3 1-EM6T-4

Parameter Value
1-EM6T-3 1-EM6T-4
Parameter Value
1-EM6T-3
Enable Port Enabled
Parameter Value
1-EM6T-3
Enable Port Enabled
of Ethernet ports.
Parameter Value
1-EM6F-1 1-EM6F-2
1-EM6T-3 1-EM6T-1

Parameter Value
1-EM6T-1
TAG Tag Aware
Parameter Value
1-EM6T-3 1-EM6T-4
Parameter Value
1-EM6T-3
TAG Tag Aware
Parameter Value
1-EM6T-3
TAG Tag Aware
of IF_ETH ports.
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1

Parameter Value
3-IFU2-1 5-IFU2-1 4-IFU2-1 6-IFU2-1

Type
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 4-IFU2-1 6-IFU2-1
Encapsulation 802.1Q 802.1Q 802.1Q

Type
Parameter Value
3-IFU2-1
of IF_ETH ports.
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1

Parameter Value
3-IFU2-1 5-IFU2-1 4-IFU2-1 6-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 4-IFU2-1 6-IFU2-1
Parameter Value
3-IFU2-1
Tag Tag Aware
----End

Procedure
follows.
Parameter Value
LAG Name ToBSC
LAG Type Static

Parameter Value
Parameter Value
Main Board 1-EM6F
----End

Procedure
l Parameters of NE1
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Awared
The values for the relevant parameters that need to be set in the UNI tab page are provided
as follows.
1-EM6F-1 - 110-129
3-IFU2-1 - 110-129
l Parameters of NE2

as follows.
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Awared
as follows.
1-EM6T-1 - 110-129
1-EM6T-3 - 110-119
3-IFU2-1 - 110-129
l Parameters of NE3
as follows.
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Awared
as follows.
1-EM6T-1 - 110-129
3-IFU2-1 - 110-119
4-IFU2-1 - 120-129
l Parameters of NE4
as follows.

Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Awared
as follows.
1-EM6T-3 - 110-119
1-EM6T-4 - 110-119
3-IFU2-1 - 110-119
l Parameters of NE5
as follows.
Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Awared
as follows.
1-EM6T-3 - 120-129
3-IFU2-1 - 120-129
4-IFU2-1 - 120-129
l Parameters of NE6
as follows.

Parameter Value
Service ID 1
Service Name Qlan
Tag Type C-Awared
as follows.
1-EM6T-3 - 120-129
3-IFU2-1 - 120-129
----End

Procedure
follows.
Parameter Value
Packet Type CVLAN
0 BE
1 AF11
2 AF21

3 AF31
4 AF41
5 EF
6 CS6
7 CS7
BE 0
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6
CS7 7
NOTE
Paramete Value
r

3-IFU2-1 1-EM6T-1 1-EM6T-4 4-IFU2-1

NOTE
The mapping relation defined in the default DS domain is the same as the mapping relation defined in the DS
domain that is created in this step. Therefore, you can skip this step.
l The values for the related parameters of NE2, NE4, NE5, and NE6 are provided as follows.
Parameter Value
Policy ID 1 2
SP (BE) SP (BE)

60 (AF3) 60 (AF3)
30 (AF2) 30 (AF2)
5 (AF1) 5 (AF1)
Parameter Value
Policy ID 1

WRR (AF4 to AF1)
SP (BE)

60 (AF3)
30 (AF2)
5 (AF1)
follows.

Parameter Value
ACL Action Permit
as follows.
Parameter Value
Match Value 2
Wildcard 0
CoS -
CIR(kbit/s) 4096
PIR(kbit/s) 8192
CBS(byte) 51200
PBS(byte) 102400

Remark (yellow)
Pass (green)

EF (yellow)
- (green)
as follows.
Parameter Value
policy.

Parameter Value
Port 3-IFU2-1
1-EM6F-1
Parameter Value

ID=1)

3-IFU2-1
Parameter Value
Port 3-IFU2-1
4-IFU2-1
1-EM6T-1
Parameter Value

ID=1)

1-EM6T-4
Parameter Value

ID=1)

4-IFU2-1

Parameter Value

ID=1)
----End

Procedure
Step 1 See A.12.11.1 Creating an MD and create the MDs for NE1, NE2, NE4, NE5, and NE6.
Parameter Value
NE1 NE2 NE4 NE5 NE6

e Domain
Name
e Domain
Level
Step 2 See A.12.11.2 Creating an MA and create the maintenance associations (MAs) for NE1, NE2,
NE4, NE5, and NE6.
Parameter Value

ce Domain
Name
Maintenan BTS1_Qlan BTS2_Qlan BTS3_Qlan BTS4_Qlan BTS5_Qlan

ce
Association
Name
Relevant 1-Qlan 1-Qlan 1-Qlan 1-Qlan 1-Qlan

Service
Transmit
Period

Parameter Value
Maintenance Association Name BTS1_Qlan
Relevant Service 1-Qlan
Parameter Value

Name
Maintenance Association BTS2_Qlan BTS3_Qlan

Name
Relevant Service 1-Qlan 1-Qlan
Parameter Value
Parameter Value

Parameter Value

ce Domain
Name
Maintenan BTS1_Qlan BTS2_Qlan BTS3_Qlan BTS4_Qlan BTS5_Qlan

ce
Association
Name
VLAN 110 110 110 120 120
MP ID 101 102 103 104 105
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 110
MP ID 201
Direction Ingress
CC Status Active
Parameter Value

Name

Name
Board 1-EM6T 1-EM6T

Parameter Value
VLAN 110 110
MP ID 401 402
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 120
MP ID 501
Direction Ingress
CC Status Active
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN 120
MP ID 601
Direction Ingress
CC Status Active
The values for the relevant parameters of NE1 are provided as follows.

Parameter Value

e Domain
Name
Maintenanc BTS1_Qlan BTS2_Qlan BTS3_Qlan BTS4_Qlan BTS5_Qlan

e
Association
Name
Remote 201 401 402 501 601

Maintenanc
e Point ID
(e.g:1,3-6)
Parameter Value
Parameter Value

Name

Name

ID(e.g:1,3-6)
Parameter Value

Parameter Value
services on NE1.
----End
5.8 Configuration Example (802.1ad-Bridge-Based E-LAN

Service)
This section considers an 802.1ad-bridge-based E-LAN service as an example to describe how




l Each BTS must independently plan VLANs for its services.
l The BSC must be capable of processing S-VLAN tags.
l The BSC must allocate an S-VLAN to each BTS, and the S-VLAN IDs on the entire network
are planned in a unified manner.
l The Ethernet services on the ring network are protected.
To meet the preceding requirements, IEEE 802.1ad bridge-based E-LAN services are configured
to implement transmission of the BTS services; in addition, ERPS is configured to protect
services on the ring network. See Figure 5-34.
Figure 5-34 Networking diagram (IEEE 802.1ad bridge-based E-LAN services)

BSC
40 Mbit/s
S-VLAN 100, 110, 120, 130
BTS1
802.1ad bridge
10 Mbit/s
S-VLAN 100 GE
NE1
BTS4
FE 10 Mbit/s
S-VLAN 130
FE
FE
ERPS
NE2 NE4
802.1ad bridge
802.1ad bridge
FE
NE3
802.1ad bridge BTS3
10 Mbit/s
S-VLAN 120
Between NE1 and 1-EM6T-1 Main port of a LAG Configure these ports
1-EM6T-2 Slave port of a LAG sharing LAG,
therefore improving
link reliability.

group

1+1 HSB protection
group

group

1+1 HSB protection
group

services on Hybrid
radio.

BTS1.

BTS2.

group

1+1 HSB protection
group


Between NE3 and 4-IFU2-1 l East port of an Configure this port to

l RPL port services on Hybrid
radio.

BTS3.

services on Hybrid
radio.

group

1+1 HSB protection
group

BTS4.

services on Hybrid
radio.




configuring QoS.

Ethernet Port
service.

(byte)
QinQ Type Domain 0x8100 0x8100

Suppression

(byte)

QinQ Type Domain - -

Suppression
Parameter 1-EM6T-3
QinQ Type Domain -
Loopback Port Shutdown Disabled
Enabling Broadcast Packet Suppression Disabled
Parameter 1-EM6T-3
QinQ Type Domain -
Loopback Port Shutdown Disabled
Enabling Broadcast Packet Suppression Disabled

Parameter 1-EM6T-3
NOTE
l If the Ethernet services on each BTS do not contain any untagged frames, you can set Encapsulation
Type to 802.1Q and set Tag to Tag Aware for the FE port that accesses the Ethernet services on each BTS.
l In this example, the FE/GE port on the BTS/BSC works in the auto-negotiation mode. Hence, the FE/GE
port of each NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet port
works in another mode, the local Ethernet port must work in the same mode. The working modes of the
Ethernet ports inside the network are planned as auto-negotiation.
equipment.
l In this example, the loopback check, loopback port shutdown, and broadcast packet suppression functions
l In this example, the SVLAN T-PID that the BSC can identify is 0x8100. Hence, you need to set QinQ Type
Domain to 0x8100 for the two GE ports connecting to the BSC.

Tag 802.1Q 802.1Q 802.1Q 802.1Q
QinQ Type 0x88a8 0x88a8 0x88a8 0x88a8

Domain

Discard
Enabled
Tag 802.1Q 802.1Q 802.1Q
QinQ Type Domain 0x88a8 0x88a8 0x88a8

Enabled


Tag 802.1Q 802.1Q
QinQ Type Domain 0x88a8 0x88a8

Tag 802.1Q 802.1Q 802.1Q
QinQ Type Domain 0x88a8 0x88a8 0x88a8

Enabled
NOTE
l The IF_ETH ports connect to internal equipment. Hence, you need to set QinQ Type Domain to 0x88a8
for the IF_ETH ports.
l The majority of the backhaul services on the BTS are Internet services. Hence, the error frame discarding

LAG

Parameter NE1
Main Port 1-EM6T-1
Slave Port 1-EM6T-2

NOTE
ERPS Instance
Table 5-159 provides the information about ERPS.
Table 5-159 ERPS instance
Ring Node Flag
Control VLAN 4093 4093 4093 4093
Packet Transmit 5s (default 5s (default 5s (default 5s (default

Interval value) value) value) value)
Entity Level 4 (default value) 4 (default value) 4 (default value) 4 (default value)
WTR Time 600s (default 600s (default 600s (default 600s (default
Guard Time 500 ms (default 500 ms (default 500 ms (default 500 ms (default
Hold-Off Time 0s (default 0s (default 0s (default 0s (default

NOTE
l In this example, all the services are aggregated on NE1. Hence, the NE that is farthest from NE1 needs to
function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link is
relatively even.
l The control VLAN needs to use a VLAN that is not used by any service. Considering that the inband DCN
uses VLAN 4094, it is recommended that the control VLAN use VLAN 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally use the default
values.


Table 5-160 802.1ad-bridge-based E-LAN service

Service ID 1 1 1 1
Service Name ADlan ADlan ADlan ADlan
Tag Type S-Awared S-Awared S-Awared S-Awared
Self-Learning Enabled Enabled Enabled Enabled

MAC Address
MAC Address IVL IVL IVL IVL

Learning Mode
Mounted UNI - 1-EM6T-3 (C- 1-EM6T-3 (C- 1-EM6T-3 (C-

Port VLAN ID: VLAN ID: VLAN ID:
blank, S-VLAN blank, S-VLAN blank, S-VLAN
ID: 100) ID: 120) ID: 130)
1-EM6T-4 (C-
VLAN ID:
blank, S-VLAN
ID: 110)
Mounted NNI 3-IFU2-1 (S- 3-IFU2-1 (S- 3-IFU2-1 (S- 3-IFU2-1 (S-
Port VLAN ID: VLAN ID: VLAN ID: VLAN ID:
100,110,120,13 100,110,120,13 100,110,120,13 100,110,120,13
0) 0) 0) 0)
4-IFU2-1 (S- 4-IFU2-1 (S- 4-IFU2-1 (S- 4-IFU2-1 (S-
VLAN ID: VLAN ID: VLAN ID: VLAN ID:
100,110,120,13 100,110,120,13 100,110,120,13 100,110,120,13
0) 0) 0) 0)
1-EM6T-1 (S-
VLAN ID:
100,110,120,13
0)

configuring QoS.
QoS (Diffserv)
configuration.


Type
CS7 7 -
CS6 6 -

streaming services)
AF4 4 -


AF1 1 -

services)
NOTE

in this example.
CS7 SP
CS6 SP
EF SP

BE SP
QoS (Diffserv)
configuration.

Type
CS7 7 -
CS6 6 -

streaming services)
AF4 4 -


AF1 1 -

services)
NOTE

QoS (Port Shaping)

node.



Procedure
Ethernet ports.
Parameter Value
1-EM6T-1 1-EM6T-2

Parameter Value
1-EM6T-3 1-EM6T-4
Parameter Value
1-EM6T-3
Enable Port Enabled
of Ethernet ports for NE1.
Parameter Value
1-EM6T-1 1-EM6T-2
QinQ Type Domain 81 00 81 00
Step 3 See A.12.7.1 Setting the General Attributes of the IF_ETH Port and set the attributes of the
IF_ETH ports.
Parameter Value
3-IFU2-1 4-IFU2-1 5-IFU2-1 6-IFU2-1

Type

Parameter Value
3-IFU2-1 4-IFU2-1 5-IFU2-1

Type
l The values for the relevant parameters of N3 are provided as follows.

Parameter Value
3-IFU2-1 4-IFU2-1
Parameter Value
3-IFU2-1 4-IFU2-1 6-IFU2-1

Type
----End

Procedure
Step 1 See A.12.2.1 Creating a LAG and create the LAG on NE1.
follows.
LAG No. Select Automatically Assign.
LAG Name ToBSC
LAG Type Static
The values for the related parameters that need to be set in Port Settings are provided as follows.

Main Board 1-EM6T
Selected Slave Ports 1-EM6T-2
Step 2 See A.12.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.
NE1 NE2 NE3 NE4
ERPS ID 1 1 1 1
Ring Node Flag
Control VLAN 4093 4093 4093 4093
----End

Procedure
l Parameters of NE1
as follows.
Parameter Value
Service ID 1
Service Name ADlan
Tag Type S-Awared

The values for the relevant parameters that need to be set in the NNI tab page are provided
as follows.
Port SVLANs
3-IFU2-1 100,110,120,130
4-IFU2-1 100,110,120,130
1-EM6T-1 100,110,120,130
l Parameters of NE2
as follows.
Parameter Value
Service ID 1
Service Name ADlan
Tag Type S-Awared
as follows.
1-EM6T-3 100 Blank
1-EM6T-4 110 Blank
as follows.
Port SVLANs
3-IFU2-1 100,110,120,130
4-IFU2-1 100,110,120,130
l Parameters of NE3
as follows.
Parameter Value
Service ID 1

Parameter Value
Service Name ADlan
Tag Type S-Awared
as follows.
1-EM6T-3 120 Blank
as follows.
Port SVLANs
3-IFU2-1 100,110,120,130
4-IFU2-1 100,110,120,130
l Parameters of NE4
as follows.
Parameter Value
Service ID 1
Service Name ADlan
Tag Type S-Awared
as follows.
1-EM6T-3 130 Blank
as follows.

Port SVLANs
3-IFU2-1 100,110,120,130
4-IFU2-1 100,110,120,130
----End

Procedure
follows.
Parameter Value
Packet Type CVLAN
0 0 BE
1 1 AF11
2 2 AF21
3 3 AF31
4 4 AF41
5 5 EF
6 6 CS6
7 7 CS7

BE 0 0
AF11 1 1
AF21 2 2
AF31 3 3
AF41 4 4
EF 5 5
CS6 6 6
CS7 7 7
NOTE
Parameter Value
NE1 NE2 NE3 NE4
Selected Port 1-EM6T-1 1-EM6T-3 1-EM6T-3 1-EM6T-3

3-IFU2-1 1-EM6T-4 3-IFU2-1 3-IFU2-1
4-IFU2-1 3-IFU2-1 4-IFU2-1 4-IFU2-1
4-IFU2-1
Step 2 See A.12.10.3 Changing the Ports That Use the DS Domain and change the ports that use the
DS domain.
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
1-EM6T-1 SVLAN
1-EM6T-3 CVLAN

1-EM6T-4 CVLAN
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
1-EM6T-3 CVLAN
3-IFU2-1 SVLAN
4-IFU2-1 SVLAN
l Parameters of NE1
Parameter Value
Policy ID 1

WRR (AF4 to AF1)
SP (BE)

60 (AF3)
30 (AF2)
5 (AF1)
l Parameters of NE2, NE3, and NE4

The values for the related parameters of NE2, NE3, and NE4 are provided as follows.
Parameter Value
Policy ID 1 2
SP (BE) SP (BE)

Parameter Value

60 (AF3) 60 (AF3)
30 (AF2) 30 (AF2)
5 (AF1) 5 (AF1)
Step 4 See A.12.10.6 Creating the Traffic and create the traffic for NE2, NE3, and NE4.
follows.
Parameter Value
ACL Action Permit
as follows.
Parameter Value
Match Value 2
Wildcard 0
CoS -
CIR(kbit/s) 4096
PIR(kbit/s) 8192
CBS(byte) 51200
PBS(byte) 102400

Remark (yellow)
Pass (green)

Parameter Value

EF (yellow)
- (green)
as follows.
Parameter Value
Step 5 See A.12.10.7 Setting the Port That Uses the Port Policy and set the port that uses the port
policy.
Parameter Value
Port 3-IFU2-1
4-IFU2-1
1-EM6F-1
Parameter Value

ID=1)

4-IFU2-1 1-EM6T-4
Parameter Value

ID=1)

4-IFU2-1

----End

Procedure
Step 1 See A.12.11.1 Creating an MD and create the MDs.
NE1 NE2 NE3 NE4

Domain Name
Maintenance 4 4 4 4
Domain Level
Step 2 See A.12.11.2 Creating an MA and create an MA.
Parameter Value
NE1 NE2 NE3 NE4

Domain Name
Maintenance ADlan ADlan ADlan ADlan

Association
Name
Relevant 1-ADlan 1-ADlan 1-ADlan 1-ADlan

Service
CC Test 1s 1s 1s 1s
Transmit
Period
Step 3 See A.12.11.3 Creating an MEP Point and create the MEP points.
l The values for the relevant parameters of NE1 are provided as follows,
Parameter Value

Domain Name

Parameter Value

Association
Name
Board 1-EM6T 1-EM6T 1-EM6T 1-EM6T
Port 1-EM6T-1 1-EM6T-1 1-EM6T-1 1-EM6T-1
VLAN 100 110 120 130
MP ID 101 102 103 104
Direction Ingress Ingress Ingress Ingress
CC Status Active Active Active Active
Parameter Value

Name
Maintenance Association ADlan ADlan

Name
Board 1-EM6T 1-EM6T
VLAN - -
MP ID 201 202
Parameter Value
Maintenance Association Name ADlan
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 301
Direction Ingress

Parameter Value
CC Status Active
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 401
Direction Ingress
CC Status Active
Step 4 See A.12.11.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1
to NE4.
Parameter Value

Domain Name

Association
Name
Remote 201 202 301 401

Maintenance
Point ID(e.g:
1,3-6)
Parameter Value

Name
Maintenance Association ADlan ADlan

Name

Parameter Value

ID(e.g:1,3-6)
Parameter Value
Parameter Value
services.
----End
5.9 Configuration Example (Hybrid Configuration of E-Line

Services and E-LAN Services)
This section describes how to configure a radio network that transmits E-Line services and E-
LAN services at the same time according to the network planning information.

The section describes the networking information about the NEs.



l The BSC provides GE optical ports whose port rate is 1000 Mbit/s.
l Whether the Ethernet services on each BTS carry a VLAN ID or whether the carried VLAN
IDs conflict is unknown. Therefore, in this example, the point-to-point transparently
transmitted E-Line services are configured for point-to-point transparent service
transmission, and the IEEE 802.1d bridge-based E-LAN services are configured for service
convergence.
l DSCP values are configured on each BTS according to service types.
l The BTSs need not communicate with each other.
Figure 5-35 Networking diagram

BTS2
15 Mbit/s
FE
GE GE
BTS3 FE
NE4
20 Mbit/s FE
NE3 NE2 NE1 BSC
120 Mbit/s
FE BTS1
FE 45 Mbit/s
NE6 NE5
BTS4
BTS5 25 Mbit/s
15 Mbit/s
Point-to-point transparently
transmitted E-Line service
IEEE 802.1d bridge
Split horizon group

therefore improving
link reliability.

radio.
1+1 HSB protection
group


BTS1.

radio.
1+1 HSB protection
group

radio.
1+1 HSB protection
group


radio.
1+1 HSB protection
group



radio.
1+1 HSB protection
group

BTS2.

BTS3.


services on Hybrid
radio.

radio.
1+1 HSB protection
group


BTS4.


Hybrid radio.

services from BTS5.


ports.
services.
This section provides the information about all the parameters required for configuring QoS.

ports.

service.


Encapsulation type Null Null

(byte)


(byte)

suppression

Parameter 1-EM6T-1
Encapsulation type Null


(byte)

suppression
Parameter 1-EM6T-3
Parameter 1-EM6T-3

NOTE
l In this example, the planned encapsulation type is null because whether the Ethernet services on each BTS
carry a VLAN ID or whether the carried VLAN IDs conflict is unknown.
l In this example, the FE/GE port on the BTS/BSC works in auto-negotiation mode. Therefore, the FE/GE
port on each NE that transmits/receives services must work in auto-negotiation mode. For example, if the
peer Ethernet port changes to another working mode, the local Ethernet port also needs to change to the
same working mode accordingly. Plan the Ethernet ports within a network to work in auto-negotiation mode.
QoS processing. The flow control planning on the NE must match the flow control planning on the peer
equipment.
l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is
enabled.

Table 5-176 to Table 5-181 provide the information about the IF_ETH ports that carry the
Ethernet service.




type
Error frame Enabled Enabled Enabled Enabled

discard



Encapsulation type Null Null Null
Error frame discard Enabled Enabled Enabled

Parameter 3-IFU2-1
Error frame discard Enabled
NOTE
The majority of the backhaul services on the BTS are Internet services. Therefore, the errored frame discarding


Parameter NE1
Main Port 1-EM6F-1
Slave Port 1-EM6F-2

NOTE

services.
Information About Point-to-Point Transparently Transmitted E-Line Services

NE1 and NE6 need to be configured with point-to-point transparently transmitted E-Line
services. Table 5-183 and Table 5-184 provide the planning information about the Ethernet
service.
Table 5-183 Information about point-to-point transparently transmitted E-Line services (NE1)
Parameter NE1
Between NE2 and the BSC
Service ID 1
Service name NE2toBSC_Tline
Service direction UNI-UNI
BPDU No transparent transmission
Source port 3-IFU2-1
Sink port 1-EM6F-1
Sink C-VLANs Blank
Table 5-184 Information about point-to-point transparently transmitted E-Line services (NE6)
Parameter NE6
Between NE5 and BTS5
Service ID 1
Service name NE5toBTS5_Tline

Parameter NE6
Source port 1-EM6T-3
Sink port 3-IFU2-1
Sink C-VLANs Blank
Information About IEEE 802.1d Bridge-Based E-LAN Services

NE2 to NE5, where a VLAN ID conflict may occur, need to be configured with IEEE 802.1d
bridge-based E-LAN services. In addition, the split horizon group needs to be configured for
preventing the BTSs from communicating with each other. Table 5-185 to Table 5-188 provide
the planning information about the Ethernet service.
Table 5-185 Information about IEEE 802.1d bridge-based E-LAN services

Parameter NE2
Service ID 1
Service name Dlan
TAG type Tag-transparent
Self-learning MAC address Enabled
Mounted UNI port 1-EM6T-1

1-EM6T-3
3-IFU2-1
Split horizon group 1-EM6T-1

1-EM6T-3
Table 5-186 Information about IEEE 802.1d bridge-based E-LAN services (NE3)
Parameter NE3
Service ID 1
Service name Dlan

Parameter NE3

3-IFU2-1
4-IFU2-1
Split horizon group 3-IFU2-1

4-IFU2-1
Parameter NE4
Service ID 1
Service name Dlan

1-EM6T-4
3-IFU2-1
Split horizon group 1-EM6T-3

1-EM6T-4
Parameter NE5
Service ID 1
Service name Dlan
Mounted UNI port 3-IFU2-1

4-IFU2-1
1-EM6T-3
Split horizon group 3-IFU2-1

1-EM6T-3


This section provides the information about all the parameters required for configuring QoS.
QoS (Diffserv)
services be allocated according to the service type. Then, the transmission network creates the
In this example, the BTS services are allocated with corresponding DSCP values according to
the service type, and the NEs allocate the PHB service classes according to the DSCP value, as
shown in Table 5-189. Each Ethernet port involved in the service uses the same DS
configuration.

Type
CS7 56 -
CS6 48 -

streaming services)
AF4 32 -


AF1 8 -

services)
NOTE


in this example.

CS7 SP
CS6 SP
EF SP
BE SP

In this example, CAR processing needs to be performed on the DS edge node in the uplink
service with the DSCP value being 16). Table 5-191 lists the CAR parameters.

Parameter Value
CIR 4096 kbit/s
CBS 51200 bytes
PIR 8192 kbit/s
PBS 102400 bytes
"Yellow" packet processing mode Mapped to the EF queue
In this example, traffic shaping also needs to be performed on the DS edge node in the uplink
direction (from the BTS to the BSC) of the OM and HSDPA real-time services on each BTS
(that is, the service with the DSCP value being 24). Table 5-192 lists the shaping parameters.

Table 5-192 Shaping parameters
Parameter Value
CIR 2048 kbit/s
CBS 25600 bytes
PIR 4096 kbit/s
PBS 51200 bytes
NOTE
The CBS/PBS is proportional to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more the burst
packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytes that are
transmitted at CIR and PIR during a 100 ms period.
QoS (Port Shaping)

node.



Procedure
of Ethernet ports.

Parameter Value
1-EM6F-1 1-EM6F-2
Parameter Value
1-EM6T-3 1-EM6T-1
Parameter Value
1-EM6T-1
Enable Port Enabled
Parameter Value
1-EM6T-3 1-EM6T-4

Parameter Value
1-EM6T-3
Enable Port Enabled
Parameter Value
1-EM6T-3
Enable Port Enabled
of IF_ETH ports.
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1 4-IFU2-1 6-IFU2-1

Type

Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 4-IFU2-1 6-IFU2-1

Type
Parameter Value
3-IFU2-1
----End

Procedure
follows.
Parameter Value
LAG Name ToBSC
LAG Type Static

Parameter Value
Main Board 1-EM6F
----End

Procedure
Step 1 See A.12.3.2 Configuring the E-Line Service and configure the E-Line services on NE1 and
NE6.
Parameter Value
Between NE2 and the BSC
Service ID 1
Service Name NE2toBSC_Tline
Direction UNI-UNI
Source VLANs Blank
Sink Port 1-EM6F-1
Sink VLANs Blank
Parameter Value
Service ID 1
Service Name NE5toBTS5_Tline
Direction UNI-UNI

Parameter Value
Source VLANs Blank
Sink Port 3-IFU2-1
Sink VLANs Blank
Step 2 See A.12.3.4 Configuring the E-LAN Service and configure the E-LAN services on NE2 to
NE5.
The values for the relevant parameters of NE2 that need to be set in the main interface are
Parameter Value
Service ID 1
Service Name Dlan
The values for the relevant parameters that need to be set in the UNI tab page are provided as
follows.
1-EM6T-1 - Blank
3-IFU2-1 - Blank
4-IFU2-1 - Blank
The values for the relevant parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
Split Horizon Group ID Split Horizon Group Member
1 1-EM6T-1, 1-EM6T-3

Parameter Value
Service ID 1
Service Name Dlan
follows.
1-EM6T-1 - Blank
3-IFU2-1 - Blank
4-IFU2-1 - Blank
1 3-IFU2-1, 4-IFU2-1
Parameter Value
Service ID 1
Service Name Dlan
follows.
1-EM6T-3 - Blank

1-EM6T-4 - Blank
3-IFU2-1 - Blank
1 1-EM6T-3, 1-EM6T-4
Parameter Value
Service ID 1
Service Name Dlan
follows.
1-EM6T-3 - Blank
3-IFU2-1 - Blank
4-IFU2-1 - Blank
1 3-IFU2-1, 1-EM6T-3
----End


Procedure
follows.
Parameter Value
Packet Type IP-DSCP
The values for the relevant parameters that need to be set in the Ingress Mapping Relation tab
0 BE
8 AF11
16 AF21
24 AF31
32 AF41
40 EF
48 CS6
56 CS7
The values for the relevant parameters that need to be set in the Egress Mapping Relation tab
BE 0
AF11 8
AF21 16
AF31 24

AF41 32
EF 40
CS6 48
CS7 56
NOTE
The values for the relevant parameters that need to be set in the Apply Port tab page are provided
as follows.
Paramete Value
r

3-IFU2-1 1-EM6T-1 1-EM6T-4 4-IFU2-1
l The values for the relevant parameters of NE1 and NE3 are provided as follows.
Parameter Value
Policy ID 1

WRR (AF4 to AF1)
SP (BE)

60 (AF3)
30 (AF2)
5 (AF1)
Parameter Value
Policy ID 1 2 3

Parameter Value
Policy Name Port_Comm Port_Car Port_Shaping
Grooming Police SP (CS7, CS6, and SP (CS7, CS6, and SP (CS7, CS6, and
After Reloading EF) EF) EF)
WRR (AF4 to AF1) WRR (AF4 to AF1) WRR (AF4 to AF1)
SP (BE) SP (BE) SP (BE)
Policy Weight(%) 5 (AF4) 5 (AF4) 5 (AF4)

60 (AF3) 60 (AF3) 60 (AF3)
30 (AF2) 30 (AF2) 30 (AF2)
5 (AF1) 5 (AF1) 5 (AF1)
Bandwidth Limit Disabled (for all Disabled (for all Disabled (for all
PHB service PHB service PHB service
classes) classes) classes)
Parameter Value
Policy ID 1 2
Policy Name Port_Car Port_Shaping
SP (BE) SP (BE)

60 (AF3) 60 (AF3)
30 (AF2) 30 (AF2)
5 (AF1) 5 (AF1)
l Parameters of NE2
as follows.
Parameter Value

ID=3)

Parameter Value

ID=3)
The values for the relevant parameters that need to be set in the INGRESS tab page are
Parameter Value

ID=3)
Match Type DSCP value DSCP value
Match Value 16 24
Wildcard 0 0
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -

Remark (yellow)
Pass (green)

EF (yellow)
- (green)
The values for the relevant parameters that need to be set in the EGRESS tab page are
Parameter Value

ID=3)
CIR(kbit/s) - 2048

Parameter Value

ID=3)
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE4
as follows.
Parameter Value

ID=1)
Traffic 1 1 2
Classification ID
ACL Action Permit Permit Permit
Parameter Value

Traffic Traffic
ID=1) ID=2)
Match Type DSCP value DSCP value DSCP value
Match Value 16 24 24
Wildcard 0 0 0
CoS - - -
Bandwidth Limit Enabled Disabled Disabled
CIR(kbit/s) 4096 - -
PIR(kbit/s) 8192 - -
CBS(byte) 51200 - -
PBS(byte) 102400 - -

Parameter Value

Traffic Traffic
ID=1) ID=2)
Handling Mode Discard (red) - -

Remark (yellow)
Pass (green)
Relabeled CoS - (red) - -

EF (yellow)
- (green)
Parameter Value

Traffic Traffic
ID=1) ID=2)
Bandwidth Limit Disabled Enabled Enabled
CIR(kbit/s) - 2048 2048
PIR(kbit/s) - 4096 4096
CBS(byte) - 25600 25600
PBS(byte) - 51200 51200
l Parameters of NE5
as follows.
Parameter Value

ID=3)

Parameter Value

ID=3)
Match Value 16 24
Wildcard 0 0
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -

Remark (yellow)
Pass (green)

EF (yellow)
- (green)
Parameter Value

ID=3)
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
l Parameters of NE6
as follows.

Parameter Value

ID=2)
Parameter Value

ID=2)
Match Value 16 24
Wildcard 0 0
CoS - -
CIR(kbit/s) 4096 -
PIR(kbit/s) 8192 -
CBS(byte) 51200 -
PBS(byte) 102400 -

Remark (yellow)
Pass (green)

EF (yellow)
- (green)
Parameter Value

ID=2)

Parameter Value

ID=2)
CIR(kbit/s) - 2048
PIR(kbit/s) - 4096
CBS(byte) - 25600
PBS(byte) - 51200
policy.
Parameter Value
Port 3-IFU2-1
1-EM6F-1
Parameter Value

Port 1-EM6T-1 1-EM6T-3 3-IFU2-1
Parameter Value
Port 3-IFU2-1
4-IFU2-1
1-EM6T-1
Parameter Value

ID=2)

1-EM6T-4

Parameter Value

Port 3-IFU2-1 1-EM6T-3 4-IFU2-1
Parameter Value

ID=2)
----End

Procedure
Parameter Value
NE1 NE2 NE4 NE5 NE6

e Domain
Name
e Domain
Level
Step 2 See A.12.11.2 Creating an MA and configure the MDs for NE1, NE2, NE4, NE5, and NE6.
Parameter Value

ce Domain
Name

Parameter Value
Maintenan BTS1 BTS2 BTS3 BTS4 BTS5

ce
Association
Name
Relevant 1- 1- 1- 1- 1-
Service NE2toBSC NE2toBSC NE2toBSC NE2toBSC NE2toBSC
Transmit
Period
Parameter Value
Maintenance Association Name BTS1
Relevant Service 2-BTS1toNE1
Parameter Value

Name
Maintenance Association BTS2 BTS3

Name
Relevant Service 1-BTS2toNE3 2-BTS3toNE3
Parameter Value

Parameter Value
Step 3 See A.12.11.3 Creating an MEP Point and create the MAs for NE1, NE2, NE4, NE5, and NE6.
Parameter Value

ce Domain
Name
Maintenan BTS1 BTS2 BTS3 BTS4 BTS5

ce
Association
Name
VLAN - - - - -
MP ID 101 102 103 104 105
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 201
Direction Ingress
CC Status Active

Parameter Value

Name

Name
Board 1-EM6T 1-EM6T
VLAN - -
MP ID 401 402
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 501
Direction Ingress
CC Status Active
Parameter Value
Board 1-EM6T
Port 1-EM6T-3
VLAN -
MP ID 601
Direction Ingress

Parameter Value
CC Status Active
Step 4 See A.12.11.4 Creating Remote MEPs in an MA and create the MEP for NE1, NE2, NE4,
NE5, and NE6.
Parameter Value

e Domain
Name
Maintenanc BTS1 BTS2 BTS3 BTS4 BTS5

e
Association
Name
Remote 201 401 402 501 601

Maintenanc
e Point ID
(e.g:1,3-6)
Parameter Value
Parameter Value

Name

Name

ID(e.g:1,3-6)

Parameter Value
Parameter Value
Step 5 See perform an LB test to test the Ethernet service configurations and test the Ethernet
services on NE1.
----End

Configuration Guide (U2000) 6 Configuring EoPDH-Based Ethernet Services
6 Configuring EoPDH-Based Ethernet

Services
About This Chapter
EoPDH-based Ethernet services are classified into EPL services, EVPL services, EPLAN
services, and EVPLAN services.
6.1 Basic Concepts

This section describes the basic concepts that are related to EoPDH services.
6.3 Configuration Example (Ethernet Services Based on TDM Radio)
This section considers an Ethernet service based on TDM radio as an example to describe how
to configure Ethernet services according to the service planning information.
6.4 Configuration Example (Ethernet Services Traversing a TDM Network)
This section considers an Ethernet service traversing a TDM network as an example to describe
how to configure Ethernet services according to the service planning information.

6 Configuring EoPDH-Based Ethernet Services Configuration Guide (U2000)
6.1 Basic Concepts

This section describes the basic concepts that are related to EoPDH services.
6.1.1 VCTRUNK
When Ethernet services need to be transmitted in EoS or EoPDH mode, you need to configure
the Ethernet services between corresponding FE/GE ports and VCTRUNKs on Ethernet boards.
6.1.2 Bridging Ports on the EFP8 Board
The bridging ports on the EFP8 board are used to connect the EoPDH plane to the packet plane.
6.1.3 Transmission Modes of Ethernet Services
The OptiX RTN 950 supports two transmission modes of Ethernet services in EoPDH mode,
namely, EoPDH and Hybrid radio.
6.1.4 Hub/Spoke
In the case of convergence services, mutual access between non-central stations and central
stations is needed but mutual access between non-central stations is not needed. Therefore, you
need to specify a mounted port as a Hub port or a Spoke port.
6.1.5 EoPDH-Based Ethernet Services
Based on the EoPDH mode, Ethernet services can be classified into six types.
6.1.1 VCTRUNK
When Ethernet services need to be transmitted in EoS or EoPDH mode, you need to configure
the Ethernet services between corresponding FE/GE ports and VCTRUNKs on Ethernet boards.
A VCTRUNK is a path that comprises virtual containers (VCs) and is also the internal port on
an Ethernet board. In the case of EoPDH, multiple individual E1 channels are concatenated into
a bigger virtual path for service transmission.
The EFP8 is an EoPDH Ethernet board and provides VCTRUNKs binding E1 channelsa.
NOTE
a: On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKs that bind VC-12 channels.
6.1.2 Bridging Ports on the EFP8 Board

The bridging ports on the EFP8 board are used to connect the EoPDH plane to the packet plane.
PORT9 and PORT10 are the bridging ports on the EFP8 board, as shown in Figure 6-1. The
functions of the bridging ports are described as follows:
l PORT9 and PORT10 are back-to-back internal GE ports.

l PORT10 is connected to the packet plane, which is provided by the packet switching unit
of the system control, switching, and clock board. The Ethernet services on the packet plane
are transmitted to the EoPDH plane through PORT10.
l PORT9 is connected to the EoPDH plane, which is provided by the Ethernet switching unit
of the EFP8 board. The Ethernet services from the packet plane are transferred to an FE
port or a VCTRUNK of the EFP8 board through PORT9.

Figure 6-1 Bridging ports on the EFP8 board
System control,
EFP8
FE PORT1 switching, and
timing board
Ethernet PORT9 PORT10

Packet
...
switching switching
FE PORT8 unit unit
GE GE
VCTRUNK1 ... VCTRUNK16
6.1.3 Transmission Modes of Ethernet Services

The OptiX RTN 950 supports two transmission modes of Ethernet services in EoPDH mode,
namely, EoPDH and Hybrid radio.
EoPDH
In EoPDH mode, Ethernet services are encapsulated and mapped into E1 channels according to
a corresponding encapsulation and mapping protocol, and are then transmitted over the SDH/
PDH network. The configurations for EoPDH transmission are similar to the configurations for
EoS transmission.
The OptiX RTN 950 provides the following transmission lines to implement EoPDH
transmission: SDH optical line, E1 line, TMD radio link constructed by the IF1 boards, and E1
line constructed by the IFU2/IFX2 boards in Hybrid radio mode.
Hybrid Radio
The OptiX RTN 950 embeds the MADM and the packet processing platform. The MADM
transmits E1 services that are received locally or extracted from the SDH services to the
microwave port. The packet processing platform processes the received Ethernet services in a
unified manner and then transmits the Ethernet services to the microwave port. The microwave
port maps the E1 services and the Ethernet services into Hybrid microwave frames and then
transmits the Hybrid microwave frames.
Figure 6-2 Hybrid radio

IDU
E1 Hybrid radio
ODU
TDM
cross-connect
matrix
Ethernet
Packet
switching
Native E1 and native Ethernet

6.1.4 Hub/Spoke
In the case of convergence services, mutual access between non-central stations and central
stations is needed but mutual access between non-central stations is not needed. Therefore, you
need to 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.
– Spoke ports and Hub ports can mutually access each other.
NOTE
A mounted port is a Hub port by default. During configuration, you can configure the mounted port of a
central station to a Hub port, and configure the mounted port of a non-central station to a Spoke port. This
can ensure that a central station can communicate with any non-central station, but non-central stations
cannot communicate with each other.
6.1.5 EoPDH-Based Ethernet Services

Based on the EoPDH mode, Ethernet services can be classified into six types.
6.1.5.1 Point-to-Point Transparently Transmitted EPL Services

In the case of EPL services, the source port transparently transmits all the received Ethernet
packets to the sink port, and the services occupy the bandwidth exclusively. These services are
point-to-point transparently transmitted EPL services.
6.1.5.2 EVPL Services Based on the VLAN
VLANs can be used to separate EVPL services. With the VLAN technology, multiple EVPL
services can share one physical channel. This type of EVPL services is called the EVPL service
based on the VLAN.
6.1.5.3 QinQ-based EVPL Services
S-VLAN tags can be used to separate EVPL services. Thus, multiple EVPL services can share
one physical channel. Such services are called QinQ-based EVPL services.
6.1.5.4 EPLAN Services Based on the 802.1d Bridge
In the case of EPLAN services, packets can be forwarded only based on the MAC address table.
This type of EPLAN services is called the EPLAN service based on the 802.1d bridge.
6.1.5.5 EVPLAN Services Based on the 802.1q Bridge
EVPLAN services can be separated by setting VLANs, and then a bridge is divided into multiple
sub-switching domains. This type of EVPLAN services is called the EVPLAN service based on
802.1q bridge.
6.1.5.6 EVPLAN Services Based on 802.1ad Bridge
S-VLAN tags can be used to separate EVPLAN services. Therefore, a bridge is divided into
multiple independent sub-switching domains. Such services are called EVPLAN services based
on 802.1ad bridge.

6.1.5.1 Point-to-Point Transparently Transmitted EPL Services

In the case of EPL services, the source port transparently transmits all the received Ethernet
packets to the sink port, and the services occupy the bandwidth exclusively. These services are
point-to-point transparently transmitted EPL services.
Service Model
Table 6-1 describes the point-to-point transparently transmitted EPL service model.
Table 6-1 Point-to-point transparently transmitted EPL service model
Traffic Flow Network Attribute Entry Detection Description
PORT (source) UNI (source) Disabled (source) The source port

PORT (sink) UNI (sink) Disabled (sink) transparently transmits all
the received Ethernet
frames to the sink port, and
the sink port processes the
Ethernet frames and sends
out the Ethernet frames.
Typical Application
Figure 6-3 shows the typical application scenarios of the point-to-point transparently transmitted
EPL service model.
Ethernet service 1 gains access to NE1 through port 1, regardless of whether the Ethernet service
carries an unknown VLAN ID or does not carry a VLAN ID. Port 1 processes the received
packets and transparently transmits Ethernet service 1 to port 3. Port 3 then processes the received
packets and transmits Ethernet service 1 to NE2.
Service processing on NE2 is the same as on NE1.
Figure 6-3 Typical application of the service model

NE 1 NE 2
Port 1 Port 3 Transmission Port 3 Port 1

EPL network EPL
Service 1 Service 1
6.1.5.2 EVPL Services Based on the VLAN

VLANs can be used to separate EVPL services. With the VLAN technology, multiple EVPL
services can share one physical channel. This type of EVPL services is called the EVPL service
based on the VLAN.
Service Model
Table 6-2 shows the models of the EVPL service based on the VLAN.

Table 6-2 Models of the EVPL service based on the VLAN

Service Model Service Flow Network Ingress Check Service
Attribute Description
Model 1 PORT (source) UNI (source) Enabled (source) The source port
PORT (sink) UNI (sink) Enabled (sink) processes the
incoming Ethernet
frames based on its
TAG attribute, and
then sends the
processed Ethernet
frames to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
sends the processed
Ethernet frames.
Model 2 PORT+VLAN UNI (source) Enabled (source) The source port

(source) UNI (sink) Enabled (sink) processes the
PORT+VLAN incoming Ethernet
(sink) frames based on its
TAG attribute, and
then sends the
Ethernet frames
with a specific
VLAN ID to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
sends the processed
Ethernet frames.
Ethernet Service 1 and Service 2 carry unknown VLAN IDs. Service 1 is accessed to NE1
through Port 1, and Service 2 is accessed to NE2 through Port 2. Port 1 and Port 2, based on
their own TAG attributes, process the incoming packets. Then, Port 1 sends Service 1 to Port 3,
and Port 2 sends Service 2 to Port 4. Port 3 and Port 4, based on their own TAG attributes, process
the incoming packets. Then, Port 3 sends Service 1 to NE2, and Port 4 sends Service 2 to NE2.


NE 1 NE 2
EVPL EVPL
Network
EVPL EVPL
Service 2 Service 2
NOTE
The application of service model 1 is similar to point-to-point transparent transmission of Ethernet services.
The difference lies in that ports need to process packets based on their TAG attributes in the application
of service model 1.
Figure 6-5 shows the typical application of service model 2. Service 1 and Service 2 carry
different VLAN IDs. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to
NE1 through Port 2. They share the transmission channel at Port 3 and are isolated by using
VLANs.
On NE1, Port 1 and Port 2, based on their own TAG attributes, process the incoming packets.
Then, Port 1 sends Service 1 to Port 3, and Port 2 sends Service 2 to Port 3. Port 3, based on
their own TAG attributes, processes the incoming packets, and then sends Service 1 and Service
2 to NE2. Service 1 and Service 2 carry different VLAN IDs, so they can be transmitted through
Port 3 with separated from each other.

NE 1 NE 2
Port 1 Port 1
Service 1 EVPL Service 1
Port 3 Transmission Port 3 EVPL
Service 2 L Service 1 Service 1 EVP Service 2
VLAN ID: 200 EVP L
Port 2 VLAN ID: 100 VLAN ID: 100 Port 2 VLAN ID: 200
Service 2 Service 2
6.1.5.3 QinQ-based EVPL Services

S-VLAN tags can be used to separate EVPL services. Thus, multiple EVPL services can share
one physical channel. Such services are called QinQ-based EVPL services.
Service Model
Table 6-3 shows a main service model of QinQ-based EVPL services.

Table 6-3 Main service model of QinQ-based EVPL services
Service Model Service Flow Network Operation of Tag Description of

(Bidirectional) Attribute Service
Model 1 PORT (source) C-Aware (Source) Adding S-VLAN The source port adds
PORT+S-VLAN S-Aware (Sink) tags (C-Aware port) S-VLAN tags to all
(sink) the received
Ethernet packets,
and then transmits
the packets to the
sink port.
Model 2 PORT+C-VLAN C-Aware (Source) Adding S-VLAN The source port adds
(source) S-Aware (Sink) tags (C-Aware port) S-VLAN tags to all
PORT+C-VLAN the received
+S-VLAN (sink) Ethernet packets
that carry the
specified C-VLAN
tags, and then
transmits the
packets to the sink
port.
Model 3 PORT+S-VLAN S-Aware (source) Transparently The source port

(source) S-Aware (sink) transmitting S- transparently
PORT+S-VLAN VLAN tags (S- transmits the
(sink) Aware port) Ethernet packets
that carry the
specified S-VLAN
tags to the sink port.
Model 4 PORT+S-VLAN S-Aware (source) Switching S-VLAN The source port

(source) S-Aware (sink) tags (S-Aware port) transmits the
PORT+S-VLAN Ethernet packets
(sink) that carry the
specified S-VLAN
tags to the sink port.
If the source and
sink QinQ links
correspond to
different S-VLAN
tags, the S-VLAN
tags carried in the
Ethernet frames are
switched.
Ethernet Service 1 and Service 2 include tagged frames and untagged frames. Service 1 is
accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds

the corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to
Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1
and Service 2 to NE2.

NE 1 NE 2
Port 1 Port 1
EVPL Transmission EVPL
Service 1 Port 3 Port 3 Service 1
Network
Service 2 L EVP Service 2
EVP L
Port 2 Port 2
Strip S-VLAN Label Add S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
Data( 1) S-VLAN(300) Data(1) S-VLAN(300) Data(1) Data(1)
Data(2) S-VLAN(400) Data(2) S-VLAN(400) Data(2) Data(2)

Service 1 and Service 2 carry different VLAN IDs. Service 1 is accessed to NE1 through Port
1, and Service 2 is accessed to NE 1 through Port 2. Port 1 adds the corresponding S-VLAN tag
to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and
Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2.

C-VLAN(100) Data( 1) S-VLAN(300) C-VLAN(100) Data(1)
C-VLAN(200) Data(2) S-VLAN(400) C-VLAN(200) Data(2)
NE 1 NE 2
Port 1 Port 1
Service 1 EVPL Service 1
Port 3 Transmission Port 3 EVPL
VLAN ID: 200 EVP L
Port 2 Port 2 VLAN ID: 200
S-VLAN(300) C-VLAN(100) Data(1) C-VLAN(100) Data( 1)
S-VLAN(400) C-VLAN(200) Data(2) C-VLAN(200) Data(2)

Service 1 and Service 2 carry different VLAN IDs. After Service 1 is accessed to NE1 through
Port 1 and Service 2 is accessed to NE1 through Port 2, they share the same transmission channel
at Port 3 and are separated from each other through S-VLAN tags. On NE1, Port 1 and Port 2
transparently transmit Service 1 and Service 2 respectively to Port 3. Port 3 transmits Service 1
and Service 2 to NE2. With the different S-VLAN tags, Service 1 and Service 2 can be
transmitted through Port 3 at the same time.


NE 1 NE 2
Port 1 Port 1
Service 1 EVPL Transmission EVPL Service 1
S-VLAN ID: 100 Port 3 Port 3 S-VLAN ID: 100
Network
S-VLAN ID: 200 EVP Service 1 Service 1 L S-VLAN ID: 200
Port 2 Port 2
S-VLAN ID: 100 S-VLAN ID: 100
Service 2 Service 2
S-VLAN ID: 200 S-VLAN ID: 200

Service 1 and Service 2 carry a same S-VLAN tag. Service 1 is accessed to NE1 through Port
1, and Service 2 is accessed to NE1 through Port 2. Port 1 changes the S-VLAN tag carried in
Service 1 and Port 2 changes the S-VLAN tag carried in Service 2 so that the S-VLAN tags
carried in Service 1 and Service 2 are different. Then, Port 1 and Port 2 transmit Service 1 and
Service 2 to Port 3 respectively. Port 3 transmits Service 1 and Service 2 to NE2.

NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
S-VLAN ID: 100 Network S-VLAN ID: 100
S-VLAN ID: 100 E-Lin e
Port 2 Port 2 S-VLAN ID: 100
6.1.5.4 EPLAN Services Based on the 802.1d Bridge

In the case of EPLAN services, packets can be forwarded only based on the MAC address table.
This type of EPLAN services is called the EPLAN service based on the 802.1d bridge.
Service Model
Table 6-4 shows the model of EPLAN services based on the 802.1d bridge.

Table 6-4 Model of EPLAN services based on the 802.1d bridge

Type of Service Service Flow Learning/ Attribute of a Sub-Switching
Switching Mode Mounted Port Domain
of a Bridge
EPLAN services PORT SVL/Ingress filter UNI No classification of

based on the 802.1d disable sub-switching
bridge domains
Figure 6-10 shows a typical application based on the model of service. The transmission network
needs to carry the A services accessed from NE2 and NE3. The two A services are aggregated
at the convergence node NE1. The services need not be isolated. Therefore, an 802.1d bridge is
used at NE1 to groom services.
Figure 6-10 Model of EPLAN services based on the 802.1d bridge

NE 2
Port 2 Port 1
User A2
NE 1 Transmission
Network
Port 1 Port 2
User A1
Port 3
802.1d bridge NE 3
Transmission
Network
Port 1
User A3
Port 2
6.1.5.5 EVPLAN Services Based on the 802.1q Bridge

EVPLAN services can be separated by setting VLANs, and then a bridge is divided into multiple
sub-switching domains. This type of EVPLAN services is called the EVPLAN service based on
802.1q bridge.
Service Model
Table 6-5 shows the models of EVPLAN services based on the 802.1q bridge.

Table 6-5 Models of EVPLAN services based on the 802.1q bridge

Type of Service Service Flow Attribute of a Learning/ Sub-Switching
Mounted Port Switching Mode Domain
of a Bridge
EVPLAN service PORT+VLAN UNI IVL/Ingress filter Division of sub-

based on the 802.1q enablea switching domains
bridge based on VLANs
NOTE
a: A VLAN filter table must be configured to check the VLAN tag. If a packet carries a VLAN ID different
from the VLAN ID of the port specified in the VLAN filter table, the packet is discarded.
Figure 6-11 shows the typical application of the model of the EVPLAN service based on the
802.1q bridge. The transmission network needs to carry G and H services accessed from NE2
and NE3. Both types of services are aggregated on NE1. G and H services adopt different VLAN
planning. Therefore, a 802.1q bridge is used on NEs and sub-switching domains are divided
based on VLANs, differentiating and separating the two types of services.
Figure 6-11 Model of EVPLAN services based on the 802.1q bridge

NE 2
VLAN 100
Port 1
User G2
Port 3
NE 1
VLAN 200
Transmission Port 2
VLAN 100
Port 1 Network User H2
User G1
Port 3
802.1q bridge
VLAN 200
Port 2 Port 4
User H1 NE 3
Transmission
VLAN 100
Network
802.1q bridge Port 1
User G3
VLAN 200
Port 3 Port 2
User H3
802.1q bridge
NOTE
You can also configure 6.1.5.2 EVPL Services Based on the VLAN on NE2 and NE3 for service access.

6.1.5.6 EVPLAN Services Based on 802.1ad Bridge

S-VLAN tags can be used to separate EVPLAN services. Therefore, a bridge is divided into
multiple independent sub-switching domains. Such services are called EVPLAN services based
on 802.1ad bridge.
Model of Service
Table 6-6 lists the models of EVPLAN services based on 802.1ad bridge.
Table 6-6 Models of EVPLAN services based on 802.1ad bridge
Type of Model of Learning/ Mount port Operation of Sub-

Service Service Switching attribute Tag Switching
Mode of a Domain
Bridge
EVPLAN Model 1 IVL/Ingress C-Aware port Adding S- Division of sub-

services based filter enable VLAN tags switching
on 802.1ad a based on PORT domains based
bridge Adding S- on S-VLAN tags
VLAN tags
based on PORT
and C-VLAN
S-Aware port Mount Port and

base for PORT
and S-VLAN
Model 2 SVL/Ingress C-Aware port Adding S- Division of sub-

filter disable VLAN tags switching
based on PORT domains based
Adding S- on S-VLAN tags
VLAN tags
based on PORT
and C-VLAN
S-Aware port Mount port

Mount Port and
base for PORT
and S-VLAN
NOTE
a: When Bridge Learning Mode is set to IVL, the VLAN filtering table must be configured so that the
bridge can check the contents of the VLAN tags. If the VLAN ID does not equal the VLAN ID of the port
defined in the VLAN filtering table, the packet is discarded.
Figure 6-12 shows the typical application of the model of service. The transport network needs
to carry G and H services accessed from NE2 and NE3. The two types of services converge on

NE1. Since G and H services have a same C-VLAN tag, you need to add different S-VLAN tags
to G and H services for service isolation.
Figure 6-12 Model of EVPLAN services based on 802.1ad bridge

NE 2
NE 2
SVLAN 300
Port 1
User G2
CVLAN 100
Port 3
SVLAN 400
NE 1 Port 2
Transmission User H2
SVLAN 300 Network CVLAN 100
Port 1 Port 3
User G1 802.1ad bridge
CVLAN 100
SVLAN 400
NE 3
Port 2
User H1
CVLAN 100 Port 4 SVLAN 300
Transmission
Port 1
Network
802.1ad bridge User G3
CVLAN 100
SVLAN 400
Port 3 Port 2
NE 1 User H3
CVLAN 100
C-VLAN(100) Data( G) S-VLAN(300) C-VLAN(100) Data(G) 802.1ad bridge
C-VLAN(100) Data(H) S-VLAN(400) C-VLAN(100) Data(H)

NE 3
NOTE
You can configure 6.1.5.3 QinQ-based EVPL Services on NE2 and NE3 for service access.

6.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted EPL Services)

required in the procedure for configuring point-to-point transparently transmitted EPL services.
6.2.2 Configuration Procedure (VLAN-Based EVPL Services)
required in the procedure for configuring VLAN-based EVPL services.
6.2.3 Configuration Procedure (QinQ-Based EVPL Services)

required in the procedure for configuring QinQ-based EVPL services.
6.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN Services)
required in the procedure for configuring IEEE 802.1d bridge-based EPLAN services.
6.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN Services)
required in the procedure for configuring IEEE 802.1q bridge-based EVPLAN services.
6.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based EVPLAN Services)
required in the procedure for configuring IEEE 802.1ad bridge-based EVPLAN services.
6.2.1 Configuration Procedure (Point-to-Point Transparently

Transmitted EPL Services)
required in the procedure for configuring point-to-point transparently transmitted EPL services.

Figure 6-13 provides the procedures for configuring point-to-point transparently transmitted
EPL services.
Figure 6-13 Configuration flow chart (point-to-point transparently transmitted EPL services)
Required Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring Ethernet Line

Services
Configuring QoS
Verifying Ethernet Service

Configurations
End


A.13.4.1 l You need to set Basic Attributes. Set the parameters as follows:
Configuring – In the case of used ports, set Enabled/Disabled to Enabled. In the
External case of unused ports, set Enabled/Disabled to Disabled.
Ethernet Ports
– In the case of an Ethernet port that is connected to external
equipment, set Working Mode to be the same value as the external
equipment (generally, the working mode of the external equipment
is auto-negotiation). In the case of Ethernet ports for connection
within the network, set Working Mode to Auto-Negotiation.
– When JUMBO frames are transmitted, set Max Frame Length
according to the actual length of a JUMBO frame. Otherwise, it is
recommended that Max Frame Length takes the default value.
l Click the Flow Control tab if the flow control function is enabled on
the external equipment to which the Ethernet port is connected. Set the
– When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
– When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l You need to set TAG Attributes. In the case of a point-to-point
transparently transmitted EPL service, set Entry Detection to
Disabled.
l In the case of a point-to-point transparently transmitted EPL service,
set Port Attributes in the Network Attributes tag page to UNI.
l You need to set Bound Path. Configure bound channels according to
the network planning information.
NOTE
The EFP8 of the OptiX RTN 950 is an EoPDH Ethernet board, which supports
VCTRUNKs that bind E1 channels. On the NMS, VCTRUNKs that bind E1
channels are displayed as VCTRUNKs that bind VC-12 channels.
l Determine whether to set Advanced Attributes according to actual
requirements.

A.13.4.2 Required when internal ports need to be used.

Configuring l You need to set TAG Attributes. In the case of a point-to-point
VCTRUNKs transparently transmitted EPL service, set Entry Detection to
on an Ethernet Disabled.
Board
l Determine whether to set Encapsulation/Mapping according to actual
requirements. It is recommended that the parameters take the default
values and are the same for both ends of a link.
l In the case of a point-to-point transparently transmitted EPL service,
set Port Attributes in the Network Attributes tag page to UNI.
l Determine whether to configure the LCAS function according to actual
requirements. If the LCAS function is required, set Enabling LCAS
to Enabled and set LCAS Mode according to the type of third-party
equipment. In addition, it is recommended that the other parameters
take the default values. Ensure that the parameter settings are consistent
at both ends of a link.
NOTE
requirements.

Procedure for Configuring a LAG
Table 6-8 Procedure for configuring a LAG

A.13.1.1 Required when a LAG needs to be configured. Set the major parameters
Creating a as follows:
LAG l Set LAG Type to the same value as the opposite equipment. LAG
Type is generally set to Static for the equipment at both ends.
l Set Load Sharing to the same value as the opposite equipment. If the
LAG is configured only to implement protection, it is recommended
that you set Load Sharing to Non-Sharing for the equipment at both
ends. If the LAG is configured to increase the bandwidth, it is
recommended that you set Load Sharing to Sharing for the equipment
at both ends.
Generally, set Revertive Mode to Revertive Mode for the equipment
at both ends. This parameter is valid to only LAGs whose Load
Sharing is set to Non-Sharing.
l Set Sharing Mode to the same value as the opposite equipment. Unless
otherwise specified, this parameter takes the default value. This
parameter is valid to only LAGs whose Load Sharing is set to
Sharing.
l Set Main Port and Selected Slave Ports according to the network
planning information. It is recommended that the main and slave ports
at both ends adopt the same settings.
A.13.1.2 Optional.
Setting
Parameters for
LAGs

Procedure for Configuring Point-to-Point Transparently Transmitted EPL Services
Table 6-9 Procedure for configuring point-to-point transparently transmitted EPL services

Creating l Set Service Type to EPL.
Ethernet
Private Line l Set Direction to Bidirectional.
Services l Set Source Port and Sink Port according to the network planning
information.
l Set Source VLAN(e.g. 1,3-6) and Sink VLAN(e.g. 1,3-6) to null.
l If any VCTRUNK to which no paths are bound is used as Source
Port or Sink Port, configure corresponding bound channels according
NOTE
The EFP8 is an EoPDH Ethernet board, which supports VCTRUNKs that bind
E1 channels. On the NMS, VCTRUNKs that bind E1 channels are displayed as
VCTRUNKs that bind VC-12 channels.
Procedure for Configuring the QoS
Table 6-10 Procedure for configuring the QoS

A.13.7.1 Required when you need to perform CAR or CoS operations. Before
Creating a performing any CAR or CoS operations, you need to create flows.
Flow Set the relevant parameters according to the network planning information.
A.13.7.2 Required if you need to perform CAR or CoS operations for a specific flow
Creating the over a port.
CAR Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network planning information.
A.13.7.3
Creating the
CoS
A.13.7.4
Binding the
CAR/CoS
A.13.7.5 Required if you need to perform queue scheduling over an egress port or
Configuring limit the bandwidth of queues over an egress port.
Traffic Set the relevant parameters according to the network planning information.
Shaping for
Egress Queues

Procedure for Testing Ethernet Services

NOTE
It is recommended that you use standard MPs for testing Ethernet services. The following table only provides
the description about standard MPs.
Table 6-11 Procedure for testing Ethernet services
A.13.8.1 Creating Required in the case of the NEs where the two Ethernet ports involved in the service test
MDs are located. Set the parameters as follows:
l Set Maintenance Domain Name and Maintenance Domain Level to the same
values for the two NEs.
l In the test of an Ethernet service between two edge nodes on the transport network,
it is recommended that Maintenance Domain Level takes the default value 4. In the
test of an Ethernet service between two internal NEs on the transport network, set
Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet
service between two Ethernet ports on the same NE, set Maintenance Domain
Level to a value smaller than the value that is set in the test of an Ethernet service
between two internal NEs on the transport network.
MAs are located. Set the parameters as follows:
l Set Maintenance Domain Name to the value of Maintenance Domain Name that
is set in the preceding step.
l Set Maintenance Association Name to the same value for the two NEs.
MPs are located. Set the major parameters as follows:
l Set Maintenance Association Name to the value of Maintenance Association
Name that is set in the preceding step.
l Set Node to the Ethernet ports that are involved in the service test.
l If the OAM information initiated by the MEP travels through the Ethernet switching
unit on the EFP8 board, set Direction of the MEP to Ingress. Otherwise, set
Direction to Egress.
l If the MP ID is used to identify an MEP, set CC Status to Active.
l It is recommended that you set CCM Sending Period(ms) to 1000 ms.
perform an LB test to Required.

test the Ethernet The LB test result should show that the test is successful.
service
configurations
6.2.2 Configuration Procedure (VLAN-Based EVPL Services)

required in the procedure for configuring VLAN-based EVPL services.


Figure 6-14 provides the procedures for configuring VLAN-based EVPL services.
Figure 6-14 Configuration flow chart (VLAN-based EVPL services)

Required Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End

Procedure for Configuring Ethernet Ports
Table 6-12 Procedure for configuring Ethernet ports

Ethernet Ports
l You need to set TAG Attributes.
– In the case of a VLAN-based EVPL service, set Entry Detection
to Enabled.
– Set TAG, Default VLAN ID, and VLAN Priority as planned.
Default VLAN ID and VLAN Priority are valid only when
TAG is Access or Hybrid.
l In the case of a VLAN-based EVPL service, set Port Attributes in the
Network Attributes tab page to UNI.
requirements.


Configuring l You need to set TAG Attributes.
VCTRUNKs
on an Ethernet – In the case of a VLAN-based EVPL service, set Entry Detection
Board to Enabled.
– Set TAG, Default VLAN ID, and VLAN Priority as planned.
Default VLAN ID and VLAN Priority are valid only when
TAG is Access or Hybrid.
l In the case of a VLAN-based EVPL service, it is recommended that
you set Port Attributes in the Network Attributes tab page to UNI.
NOTE
requirements.


at both ends.
Sharing.
A.13.1.2 Optional.
Setting
Parameters for
LAGs

Procedure for Configuring VLAN-Based EVPL Services
Table 6-14 Procedure for configuring VLAN-based EVPL services
A.13.2.1 Required. Set the major parameters as follows:

Creating l Set Service Type to EPL.
Ethernet
Private Line l Set Direction to Bidirectional.
Services l Set Source Port and Sink Port according to the network planning
information.
l Set Source VLAN(e.g. 1,3-6) and Sink VLAN(e.g. 1,3-6) according
NOTE
A.13.7.3
Creating the
CoS
A.13.7.4
Binding the
CAR/CoS
Shaping for
Egress Queues


NOTE

service
configurations
6.2.3 Configuration Procedure (QinQ-Based EVPL Services)

required in the procedure for configuring QinQ-based EVPL services.


Figure 6-15 provides the procedures for configuring QinQ-based EVPL services.
Figure 6-15 Configuration flow chart (QinQ-based EVPL services)

Required Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End


Ethernet Ports
l In the case of a QinQ-based EVPL service, set Port Attributes in the
Network Attributes tab page to C-Aware or S-Aware.
NOTE
requirements.


Configuring l Determine whether to set Encapsulation/Mapping according to actual
VCTRUNKs requirements. It is recommended that the parameters take the default
on an Ethernet values and are the same for both ends of a link.
Board
l In the case of a QinQ-based EVPL service, set Port Attributes in the
Network Attributes tab page to C-Aware or S-Aware.
NOTE
requirements.


at both ends.
Sharing.
A.13.1.2 Optional.
Setting
Parameters for
LAGs

Procedure for Configuring QinQ-Based EVPL Services
Table 6-19 Procedure for configuring QinQ-based EVPL services

A.13.2.5 Required. Set the major parameters as follows:

Creating NOTE
QinQ-Based Before setting the parameters, select Display QinQ Shared Service.
EVPL Services l Set Service Type to EVPL (QinQ).
l Set Direction to Bidirectional.
l Set Operation Type, Source Port, Source C-VLAN (e.g. 1, 3-6),
Source S-VLAN, Sink Port, Sink C-VLAN(e.g. 1, 3-6), Sink S-
VLAN, C-VLAN Priority, and S-VLAN Priority according to the
NOTE

A.13.7.3
Creating the
CoS
A.13.7.4
Binding the
CAR/CoS
Shaping for
Egress Queues


NOTE


service
configurations

6.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN

Services)
required in the procedure for configuring IEEE 802.1d bridge-based EPLAN services.

Figure 6-16 provides the procedures for configuring IEEE 802.1d bridge-based EPLAN
services.
Figure 6-16 Configuration flow chart (802.1d bridge-based EPLAN services)

Required Start
Optional
Configuring LAGs
Configuring Ethernet LAN

Services
Configuring QoS

Configurations
End


Ethernet Ports
l In the case of an IEEE 802.1d bridge-based EPLAN service, set Port
Attributes in the Network Attributes tab page to UNI.
l To enable the broadcast packet suppression function, you need to set
Advanced Attributes.
Set the relevant parameters according to the network planning
information.


Board
l In the case of an IEEE 802.1d bridge-based EPLAN service, set Port
NOTE
requirements.


at both ends.
Sharing.
A.13.1.2 Optional.
Setting
Parameters for
LAGs

Procedure for Configuring IEEE 802.1d Bridge-Based EPLAN Services
Table 6-24 Procedure for configuring IEEE 802.1d bridge-based EPLAN services
A.13.2.2 Creating Ethernet Required. Set the major parameters as follows:

LAN Services l Set VB name according to the network planning
information.
l Set Bridge Type to 802.1d.
l Set Mount Port according to the network planning
information.
l If any VCTRUNK to which no channels are bound is used
as Mount Port, configure corresponding bound channels
according to the network planning information.
NOTE
The EFP8 of the OptiX RTN 950 is an EoPDH Ethernet board,
which supports VCTRUNKs that bind E1 channels. On the NMS,
VCTRUNKs that bind E1 channels are displayed as VCTRUNKs
that bind VC-12 channels.
Managing A.13.3.2 Required when usage of EPLAN services needs to be disabled

the MAC Creating a on certain MAC address hosts.
address table Blacklist The parameters need to be set according to network planning.
Entry of a
MAC
Address
Creating a to age.
Static MAC The parameters need to be set according to network planning.
Address
Entry
A.13.3.3 Required if you need to disable the aging function or change

Setting the the aging time (five minutes by default).
Aging Time The parameters need to be set according to network planning.
of a MAC
Address
Table Entry
A.13.2.3 Changing the Required if you need to change a port connected to a VB,
Ports Connected to a VB enabled status of a port connected to a VB, or Hub/Spoke
attribute of a port connected to a VB.


A.13.7.3
Creating the
CoS
A.13.7.4
Binding the
CAR/CoS
Shaping for
Egress Queues

NOTE



service
configurations
6.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN

Services)
required in the procedure for configuring IEEE 802.1q bridge-based EVPLAN services.

Figure 6-17 provides the procedures for configuring IEEE 802.1q bridge-based EVPLAN
services.

Figure 6-17 Configuration flow chart (IEEE 802.1q bridge-based EVPLAN services)
Required Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End


Ethernet Ports
l TAG is mandatory.
Set TAG, Default VLAN ID, and VLAN Priority as required. Default
VLAN ID and VLAN Priority are valid only when TAG is Access or
Hybrid.
l In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port
information.


Configuring l TAG is mandatory.
VCTRUNKs
on an Ethernet Set TAG, Default VLAN ID, and VLAN Priority. Default VLAN
Board ID and VLAN Priority are valid only when TAG is Access or
Hybrid.
l In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port
NOTE
requirements.


at both ends.
Sharing.
A.13.1.2 Optional.
Setting
Parameters for
LAGs

Procedure for Configuring IEEE 802.1q Bridge-Based EVPLAN Services
Table 6-29 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services
A.13.2.2 Creating Ethernet Required. Set the major parameters as follows:

LAN Services l Set VB name according to the network planning
information.
l Set Bridge Type to 802.1q.
information.
NOTE
A.13.2.4 Creating the Required.

VLAN Filtering Table Set VLAN ID(e.g.1,3-6) and Selected forwarding ports
Managing A.13.3.2 Required when usage of EVPLAN services needs to be

the MAC Creating a disabled on certain MAC address hosts.
Entry of a information.
MAC
Address
Creating a to age.
Entry

Aging Time Set the parameters according to the network planning
of a MAC information.
Address
Table Entry


A.13.7.3
Creating the
CoS
A.13.7.4
Binding the
CAR/CoS
Shaping for
Egress Queues

NOTE



service
configurations
6.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based

EVPLAN Services)
required in the procedure for configuring IEEE 802.1ad bridge-based EVPLAN services.

Figure 6-18 provides the procedures for configuring IEEE 802.1ad bridge-based EVPLAN
services.

Figure 6-18 Configuration flow chart (IEEE 802.1ad bridge-based EVPLAN services)
Required Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End


Ethernet Ports
l In the case of an IEEE 802.1ad bridge-based EVPLAN service, set
Port Attributes in the Network Attributes tab page to C-Aware or
S-Aware.
information.


Board
l In the case of an IEEE 802.1ad bridge-based EVPLAN service, set
Port Attributes in the Network Attributes tab page to C-Aware or
S-Aware.
NOTE
requirements.


at both ends.
Sharing.
A.13.1.2 Optional.
Setting
Parameters for
LAGs

Procedure for Configuring IEEE 802.1ad Bridge-Based EVPLAN Services
Table 6-34 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services
A.13.2.6 Creating IEEE Required. Set the parameters as follows:

802.1ad Bridge-Based l Set VB name according to the network planning
EVPLAN Services information.
l Set Bridge Type to 802.1ad.
information.
NOTE
A.13.2.4 Creating the Required if you set Bridge Switch Mode to IVL/Ingress
VLAN Filtering Table Filter Enable.
Set VLAN ID(e.g.1,3-6) and Selected forwarding ports
Managing A.13.3.2 Required when usage of EVPLAN services needs to be

the MAC Creating a disabled on certain MAC address hosts.
address table Blacklist The parameters need to be set according to network planning.
Entry of a
MAC
Address
Creating a to age.
Entry

Aging Time Set the parameters according to the network planning
of a MAC information.
Address
Table Entry


A.13.7.3
Creating the
CoS
A.13.7.4
Binding the
CAR/CoS
Shaping for
Egress Queues

NOTE



service
configurations
6.3 Configuration Example (Ethernet Services Based on

TDM Radio)
This section considers an Ethernet service based on TDM radio as an example to describe how
to configure Ethernet services according to the service planning information.

service based on TDM radio.

configure the Ethernet services on the TDM radio chain network shown in Figure 6-19,
according to the following requirements:

l In this example, few Ethernet services are transmitted only on BTS3 and BTS4. To meet
the service requirements, the radio network need not be upgraded and the EoPDH mode is
adopted to transmit Ethernet services.
l The Ethernet services on BTS3 occupy a 4 Mbit/s bandwidth and the Ethernet services on
BTS4 occupy a 10 Mbit/s bandwidth.
l Ethernet services transmitted by BTS3 and BTS4 carry VLAN tags, and VLAN IDs on the
entire network are planned in a unified manner.
l FE links to the BSC are configured with LAG protection.
l QoS processing is not required.
l Figure 6-20 shows the board configuration of each NE on the radio network.
Figure 6-19 Networking diagram (Ethernet services based on TDM radio)
E1
BTS2
STM-1
FE+E1 NE4 FE+STM-1
BTS3
4 Mbit/s E1
VLAN 120
NE3 NE2 NE1
BSC
FE+E1 BTS1
E1
NE6 NE5
BTS4
BTS5 10 Mbit/s
VLAN 130
Figure 6-20 Board configuration (Ethernet services based on TDM radio)
NE3 NE2 NE1

NE4 CST CST CST
CST IF1 IF1 IF1 IF1
E1 NE6 NE6 NE6
IF1
IF1 BTS2 IF1 IF1 IF1 EFP8
NE6
IF1 SL1D SL1D SP3S SL1D
EFP8
SP3S FE
STM-1
E1 E1
BTS3 STM-1 FE
BTS1
BSC
CST CST
IF1
NE6
IF1 NE6
IF1 IF1
SP3S EFP8 SP3S
NE6 NE5 FE E1
E1
BTS4
BTS5
The connections of Ethernet links are described as follows.


Between NE1 and the BSC 4-EFP8-PORT1 (main port l Configure these ports to
of a LAG) aggregate the Ethernet
services backhauled from
4-EFP8-PORT2 (slave port BTS3 and BTS4 to the
of a LAG) BSC.
l Configure these ports into
a load non-sharing LAG,
therefore improving link
reliability.
Between NE1 and NE2 3-IF1 (main IF board of a 1+1 Configure these ports to
HSB protection group) transmit Ethernet services
encapsulated in E1s.

Between NE2 and NE3 1-SL1D-1 Configure these ports to

transmit Ethernet services

Between NE3 and NE2 1-SL1D-1 Configure these ports to

transmit Ethernet services


Between NE4 and BTS3 4-EFP8-PORT1 Configure this port to support

access of services from BTS3
and transmit the services in
EoPDH mode.
Between NE5 and BTS4 1-EFP8-PORT1 Configure this port to support

access of services from BTS4
and transmit the services in
EoPDH mode.

service based on TDM radio.

ports.
protection.

services.
6.3.2.4 Service Planning (Ethernet Service Cross-Connections)
service cross-connections.
In this example, the QoS function is not used.

ports.
Information About Ethernet External Ports

Table 6-42 to Table 6-44 provide the information about the Ethernet ports that transmit the
Ethernet services.
Table 6-42 Information about Ethernet external ports (NE1)

Parameter 4-EFP8-PORT1 4-EFP8-PORT2
Port enabled Enabled Enabled
Entry detection Enabled Enabled
Network attribute UNI UNI

Parameter 4-EFP8-PORT1
Port enabled Enabled
Maximum frame length 1522
Entry detection Enabled
Network attribute UNI

NOTE
l In this example, the FE ports on all the BTSes/BSC work in auto-negotiation mode. Therefore, the FE
ports on the NEs that receive services from and transmit services to the BTSes/BSC must also work in
auto-negotiation mode. If the peer Ethernet ports work in a mode other than the auto-negotiation mode,
plan the local Ethernet ports to work in the same mode as the peer Ethernet ports. In the case of Ethernet
ports within a network, plan the Ethernet ports to work in auto-negotiation mode.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate
for QoS processing. The planning information of flow control must be the same for the equipment at
both ends.
l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the
ports are Tag Aware.
l In this example, the maximum frame length is planned to be the default value, 1522. If required, change
the maximum frame length according to the requirements of the specific BTS.
Information About VCTRUNKs

Table 6-45 to Table 6-47 provide the information about the VCTRUNKs that are configured
to transmit the Ethernet services.
Table 6-45 Information about VCTRUNKs (NE1)
Parameter 4-EFP8-VCTRUNK1 (Receiving 4-EFP8-VCTRUNK2 (Receiving

and Transmitting Ethernet and Transmitting Ethernet
Services Between BTS4 and the Services Between BTS3 and the
BSC) BSC)

attribute
Entry Enabled Enabled

detection
Network UNI UNI

attribute

Parameter 4-EFP8-VCTRUNK1 (Receiving 4-EFP8-VCTRUNK2 (Receiving

and Transmitting Ethernet and Transmitting Ethernet
Services Between BTS4 and the Services Between BTS3 and the
BSC) BSC)
Mapping GFP GFP

protocol
LCAS Enabled Enabled
Bound paths VC4-1-VC12(1-5) VC4-1-VC12(6-7)

Parameter 4-EFP8-VCTRUNK1 (Receiving and
Transmitting Ethernet Services
Between BTS3 and the BSC)
Mapping protocol GFP
LCAS Enabled
Bound paths VC4-1-VC12(1-2)

Parameter 1-EFP8-VCTRUNK1 (Receiving and
Transmitting Ethernet Services
Between BTS4 and the BSC)
Mapping protocol GFP
LCAS Enabled
Bound paths VC4-1-VC12(1-5)

protection.

To improve reliability of service transmission, NE1 and the BSC are interconnected through the
LAG formed by two FE links. Table 6-48 provides the planning information.
Table 6-48 Information about the LAG
Parameter NE1
LAG type Static
Revertive mode Non-Revertive
Load sharing Non-Sharing
System priority 32768
Main port 4-EFP8-PORT1
Slave port 4-EFP8-PORT2
NOTE
In this example, the bandwidth of the Ethernet services to be transmitted is 14 Mbit/s, which is much lower
than the bandwidth of an FE port. Therefore, you need not configure the LAG to the load-sharing mode to
increase the bandwidth.

services.
Ethernet services received by each BTS carry the specific VLAN ID. Therefore, you need to
configure VLAN-based EVPL services in this example. Table 6-49 to Table 6-51 provide the
service planning information.
Table 6-49 Information about VLAN-based EVPL services (NE1)
Parameter Between BTS4 and the Between BTS3 and the

BSC BSC
Board 4-EFP8 4-EFP8
Service type EPL EPL
Service direction Bidirectional Bidirectional
Source port VCTRUNK1 VCTRUNK2
Source VLAN 130 120
Sink port PORT1 PORT1
Sink VLAN 130 120

Table 6-50 VLAN-based EVPL services (NE4)

Parameter Between BTS3 and the BSC
Board 4-EFP8
Service type EPL
Service direction Bidirectional
Source port PORT1
Source VLAN 120
Sink port VCTRUNK1
Sink VLAN 120
Table 6-51 VLAN-based EVPL services (NE5)

Parameter Between BTS4 and the BSC
Board 1-EFP8
Service type EPL
Source port PORT1
Source VLAN 130
Sink port VCTRUNK1
Sink VLAN 130
6.3.2.4 Service Planning (Ethernet Service Cross-Connections)

service cross-connections.
Timeslot Allocation
Figure 6-21 shows the timeslots that are allocated to the TDM radio-based Ethernet services
according to the service planning information. 4.1.4 TDM Timeslot Planning Schemes
describes the meanings of the timeslot allocation diagram and how to plan the timeslot allocation
diagram.

Figure 6-21 Timeslot allocation diagram (Ethernet services based on TDM radio)
Links-1: NE1 - NE2 - NE3 -NE5-NE6
Station NE1 NE2 NE3 NE5 NE6
Timeslot 3-IF1 3-IF1 1-SL1D-1 1-SL1D-1 4-IF1 4-IF1 3-IF1 3-IF1
VC12:1-5
4-EFP8-1 (VCTRUNK1) 1-EFP8-1 (VCTRUNK1)

VC4-1:VC12:1-5 VC4-1:VC12:1-5
VC4-1
VC12:6-7
4-EFP8-1(VCTRUNK2)
VC4-1:VC12:6-7
Links-2: NE3-NE4
Station NE3 NE4
Timeslot 1-SL1D-1 3-IF1 3-IF1
VC4-1 VC12:6-7 VC12:1-2
4-EFP8 -1(VCTRUNK1)
VC4-1:VC12:1-2
Pass through
Add/Drop
Foward
As shown in Figure 6-21, the information about the timeslots that the TDM radio-based Ethernet
services occupy on each NE is as follows:
l Ethernet services on NE5:

– The Ethernet services are added to or dropped from the first to fifth VC-12 timeslots in
the first VC-4 of VCTRUNK1 on the EFP8 board in slot 1 of NE5.
– The Ethernet services are added to or dropped from the first to fifth VC-12 timeslots in
the first VC-4 of VCTRUNK1 on the EFP8 board in slot 4 of NE1.
– The Ethernet services occupy the first to fifth VC-12 timeslots on the link between the
IF1 board in slot 3 of NE1 and the IF1 board in slot 4 of NE5.
l Ethernet services on NE4:
– The Ethernet services are added to or dropped from the first and second VC-12 timeslots
in the first VC-4 of VCTRUNK1 on the EFP8 board in slot 4 of NE4.
– The Ethernet services are added to or dropped from the sixth and seventh VC-12
timeslots in the first VC-4 of VCTRUNK2 on the EFP8 board in slot 4 of NE1.
– The Ethernet services occupy the sixth and seventh VC-12 timeslots on the link between
the IF1 board in slot 3 of NE1 and the first optical port on the SL1D board in slot 1 of
NE3.
– The Ethernet services occupy the first and second VC-12 timeslots on the link from the
IF1 board in slot 3 of NE3 to the IF1 board in slot 3 of NE4.
Information About Cross-Connections of Ethernet Services

Based on the timeslot allocation information shown in Figure 6-21, you can plan the Ethernet
service cross-connections. Table 6-52 to Table 6-56 provide the information about cross-
connections of the Ethernet services.

Table 6-52 Cross-connections of Ethernet services (NE1)

Parameter Value
Service level VC12
Source slot 4-EFP8
Source port 1
Source VC4 VC4-1
Source timeslot range 1-7
Sink slot 3-IF1
Sink port 1
Sink VC4 VC4-1
Sink timeslot range 1-7

Parameter Value
Service level VC12
Source slot 3-IF1
Source port 1
Source VC4 VC4-1
Sink slot 1-SL1D
Sink port 1
Sink VC4 VC4-1

Parameter Value
Service level VC-12 VC-12

Parameter Value
Source slot 1-SL1D 1-SL1D
Source port 1 1
Source timeslot range 1-5 6-7
Sink slot 4-IF1 3-IF1
Sink port 1 1
Sink timeslot range 1-5 1-2

Parameter Value
Service level VC12
Source slot 4-EFP8
Source port 1
Source VC4 VC4-1
Sink slot 3-IF1
Sink port 1
Sink VC4 VC4-1

Parameter Value
Service level VC12
Source slot 1-EFP8
Source port 1
Source VC4 VC4-1

Parameter Value
Sink slot 4-IF1
Sink port 1
Sink VC4 VC4-1


6.3.3.3 Configuration Process (Ethernet Services)
This section describes the process for configuring the Ethernet service information.
6.3.3.4 Configuration Process (Cross-Connections)
This section describes the process for configuring the cross-connections.

Procedure
Step 1 See A.13.4.1 Configuring External Ethernet Ports and configure the Ethernet external ports.
Parameter Value
4-EFP8-PORT1 4-EFP8-PORT2
Enabled/Disabled Enabled Enabled

Parameter Value
Max Frame Length 1522 1522
Non-Autonegotiation Disabled Disabled

Flow Control Mode
Autonegotiation Flow Disabled Disabled

Control Mode
Entry Detection Enabled Enabled
Port Attributes UNI UNI
Parameter Value
4-EFP8-PORT1
Enabled/Disabled Enabled
Max Frame Length 1522
Non-Autonegotiation Flow Control Disabled

Mode
Autonegotiation Flow Control Mode Disabled
TAG Tag Aware
Entry Detection Enabled
Port Attributes UNI
Parameter Value
1-EFP8-PORT1

Mode

Parameter Value
1-EFP8-PORT1
TAG Tag Aware
Port Attributes UNI
Step 2 See A.13.4.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs.
Parameter Value
4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2
Mapping Protocol GFP GFP
Enabling LCAS Enabled Enabled
Level VC-12-Xv VC-12-Xv
Bound Path VC4-1-VC12(1-5) VC4-1-VC12(6-7)
Parameter Value
4-EFP8-VCTRUNK1
TAG Tag Aware
Mapping Protocol GFP
Port Attributes UNI
Enabling LCAS Enabled
Level VC-12-Xv
Bound Path VC4-1-VC12(1-2)

Parameter Value
1-EFP8-VCTRUNK1
TAG Tag Aware
Mapping Protocol GFP
Port Attributes UNI
Enabling LCAS Enabled
Level VC-12-Xv
Bound Path VC4-1-VC12(1-5)
----End

Procedure
Step 1 See A.13.1.1 Creating a LAG and create the LAG.
Parameter Value
4-EFP8
LAG No 1
LAG Name ToBSC
LAG Type Static
Main Port PORT1
Selected Slave Ports PORT2
Step 2 See A.13.1.2 Setting Parameters for LAGs and set the parameters for LAGs.

Parameter Value
4-EFP8
LAG No 1
LAG Name ToBSC
----End
6.3.3.3 Configuration Process (Ethernet Services)

This section describes the process for configuring the Ethernet service information.
Procedure
Step 1 See A.13.2.1 Creating Ethernet Private Line Services and create the Ethernet private line
service.
Parameter Value
Between BTS4 and the Between BTS3 and the

BSC BSC
Board 4-EFP8 4-EFP8
Service Type EPL EPL
Source Port VCTRUNK1 VCTRUNK2
Source VLAN(e.g. 1,3-6) 130 120
Sink Port PORT1 PORT1
Sink VLAN(e.g. 1,3-6) 130 120
Parameter Value
Between BTS3 and the BSC
Board 4-EFP8
Service Type EPL
Source Port PORT1

Parameter Value
Source VLAN(e.g. 1,3-6) 120
Sink Port VCTRUNK1
Sink VLAN(e.g. 1,3-6) 120
Parameter Value
Board 1-EFP8
Service Type EPL
Source Port PORT1
Source VLAN(e.g. 1,3-6) 130
Sink Port VCTRUNK1
Sink VLAN(e.g. 1,3-6) 130
----End

Procedure
Step 1 On NE1, NE4, and NE5, see A.10.1 Creating the Cross-Connections of Point-to-Point
Services and create the service cross-connections.
Parameter Value
Level VC12
Source Slot 4-EFP8-1
Source VC4 VC4-1
Sink Slot 3-IF1-1

Parameter Value
Sink VC4 VC4-1
Activate Immediately Yes
Parameter Value
Level VC12
Source Slot 3-IF1-1
Source VC4 VC4-1
Sink Slot 1-SL1D-1
Sink VC4 VC4-1
Parameter Value
Level VC12 VC12

(e.g.1,3-6)
Sink Slot 4-IF1-1 3-IF1-1

1,3-6)
Activate Immediately Yes Yes

Parameter Value
Level VC12
Source VC4 VC4-1
Sink Slot 3-IF1-1
Sink VC4 VC4-1
Parameter Value
Level VC12
Source VC4 VC4-1
Sink Slot 4-IF1-1
Sink VC4 VC4-1
----End


Procedure
Step 1 On NE1, NE4, and NE5, see A.13.8.1 Creating MDs and create the maintenance domain.
The values for the required parameters are provided as follows.

Parameter Value
NE1 NE4 NE5
Maintenance EdgeNE EdgeNE EdgeNE

Domain Name
Maintenance 4 4 4
Domain Level
Step 2 On NE1, NE4, and NE5, see A.13.8.2 Creating MAs and create the maintenance association.
Parameter Value

Name

Name
Parameter Value
Parameter Value
Step 3 On NE1, NE4, and NE5, see A.13.8.3 Creating MPs and create the maintenance points.
Parameter Value

Name

Name
Node 4-EFP8-PORT1 4-EFP8-PORT1
VLAN ID 120 130
MP ID 103 104

Parameter Value
Type MEP MEP
CC Status Activate Activate
CCM Sending Period(ms) 1000 1000
Parameter Value
Node 4-EFP8-PORT1
VLAN ID 120
MP ID 401
Type MEP
Direction Ingress
CC Status Activate
CCM Sending Period(ms) 1000
Parameter Value
Node 1-EFP8-PORT1
VLAN ID 130
MP ID 501
Type MEP
Direction Ingress
CC Status Activate
Step 4 On NE1, perform LB tests to test the Ethernet service configurations.

l Perform the LB test by considering the maintenance point whose MP ID is 103 as the source
maintenance point and considering the maintenance point whose MP ID is 401 as the sink
maintenance point.
maintenance point and considering the maintenance point whose MP ID is 501 as the sink
maintenance point.
All LB tests should show that the tests are successful.
----End
6.4 Configuration Example (Ethernet Services Traversing a

TDM Network)
This section considers an Ethernet service traversing a TDM network as an example to describe
how to configure Ethernet services according to the service planning information.

service traversing a TDM network.

On the network shown in Figure 6-22, all the Ethernet services from BTS1-BTS5 are aggregated
through Hybrid radio links to NE1, traverse the leased TDM network, and then are transmitted
to the BSC. Based on 3.5 Configuration Example (Radio Links on the Hybrid Radio Chain
Network), configure the Ethernet services according to the following requirements:
l NE1 uses the EFP8 board to receive Ethernet services from and transmit Ethernet services
to BTS6.
l NE1 and NE7 use the EoPDH technology, wherein Ethernet services are encapsulated into
E1 services so that Ethernet services traverse the TDM network successfully.
NOTE
To facilitate description of service configurations in this example, NE7 is an IDU that supports the EoPDH
function. In actual networking scenarios, NE7 can also be OptiX MSTP equipment that supports the
EoPDH function.
l Each BTS is allocated with a specific Ethernet bandwidth and a total of 40 Mbit/s bandwidth
is required. Therefore, 20 E1 lines need to be leased.
l The services transmitted by each BTS carry VLAN tags, and VLAN IDs on the entire
network are planned in a unified manner. Therefore, the VLAN-based E-Line services are
configured for service transmission in this example.
l VLAN priorities are configured on each BTS according to service types and QoS processing
is required.

l Figure 6-23 shows the board configuration of each NE on the radio network.
NOTE
This section describes only how to configure Ethernet services on NE1 and NE7. For details on how to
configure Ethernet services on NE2 to NE6, see 5.4 Configuration Example (VLAN-Based E-Line
Service).
Figure 6-22 Networking diagram (Ethernet services traversing a TDM network)

BTS2
4 Mbit/s
VLAN 110
BTS6
8 Mbit/s
FE VLAN 150
FE
GE
FE NE4
BTS3 TDM
4 Mbit/s FE E1 network
VLAN 120
NE3 NE2 NE1
E1
FE
FE BTS1
FE 8 Mbti/s
NE6 NE5 VLAN 100 NE7
BSC
BTS4
BTS5 8 Mbit/s
8 Mbit/s VLAN 130
VLAN 140
Figure 6-23 Board configuration (Ethernet services traversing a TDM network)
NE3 NE cascade NE2 NE1

NE4 FE CSH CSH CSH
E1 NE6 NE6 NE6
IFU2 EFP8 FE
IFU2 IFU2 IFU2 IFU2
NE6 BTS2
IFU2 EM6T SP3S EM6T SP3D SP3D
EM6T SP3S E1
GE
E1 E1 BTS6
FE BTS3 FE E1 TDM
BTS1 network
E1
CSH
CSH CSH
IFU2 NE6
NE6
IFU2 NE6
IFU2 IFU2
EFP8
SP3D
EM6T SP3S EM6T SP3S
NE6 NE5 E1 NE7 FE
FE
FE E1
BTS4
BTS5 BSC
The connections of Ethernet links are described as follows.

Between NE1 and the leased 2-SP3D(1-20) Configure these ports to be

TDM network connected to the leased E1
lines.
Between NE1 and BTS6 4-EFP8-PORT1 Configure this port to receive

Ethernet services from and
transmit Ethernet service to
BTS6.
Between NE1 and NE2 4-EFP8-PORT9 PORT9 and PORT10 bridge

between the EoPDH plane
4-EFP8-PORT10 and the packet plane. PORT9
bridges the EoPDH plane and
PORT10 bridges the packet
plane.
3-IFU2 (main IF board of a 1 Configure this port to receive

+1 HSB protection group) Ethernet services from and
transmit Ethernet services to
5-IFU2 (standby IF board of NE2.
Between NE7 and the leased 2-SP3D(1-20) Configure these ports to be

TDM network connected to the leased E1
lines.
Between NE7 and the BSC 4-EFP8-PORT1 Configure this port to

aggregate the Ethernet
services backhauled from the
BTSs to the BSC.
NOTE
In this example, 20 E1 lines are used to transmit Ethernet services only. In actual networking scenarios,
extra E1 lines need to be leased for transmitting E1 services.

service traversing a TDM network.
6.4.2.1 Service Planning (Ethernet Ports on the Packet Plane)

ports on the packet plane.

6.4.2.2 Service Planning (Ethernet Services on the Packet Plane)

services on the packet plane.
6.4.2.3 Service Planning (QoS on the Packet Plane)
This section provides the information about all the parameters required for configuring QoS on
the packet plane.
6.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board)
ports on the EFP8 board.
6.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board)
protection for the EFP8 board.
6.4.2.6 Service Planning (Ethernet Services on the EFP8 Board)
services on the EFP8 board.
6.4.2.7 Service Planning (Cross-Connections)
This section provides the information about all the parameters required for configuring cross-
connections.
6.4.2.8 Service Planning (QoS of the EFP8 Board)
This section provides the information about all the parameters required for configuring QoS of
the EFP8 board.
6.4.2.1 Service Planning (Ethernet Ports on the Packet Plane)

ports on the packet plane.

Table 6-59 provides the information about the Ethernet ports that transmit the Ethernet service.


NOTE
l In this example, all the services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag
Aware.
l In the case of the EFP8 board, the flow control function is enabled only when the NE or the peer equipment
is inadequate for QoS processing. The planning information of flow control must be the same for the
equipment at both ends.
l In this example, the maximum frame length is planned to be the default value, 1522. If required, change the
maximum frame length according to the requirements of the specific BTS.

Table 6-60 provides the information about the IF_ETH ports that carry the Ethernet service.
Table 6-60 Information about the IF_ETH port (NE1)
Parameter 3-IFU2 5-IFU2
6.4.2.2 Service Planning (Ethernet Services on the Packet Plane)

services on the packet plane.
Table 6-61 provides the planning information about the Ethernet service.
Table 6-61 Information about Ethernet services (NE1)
Parameter Between NE2 and the TDM Network
Service ID 1
Service name NE2toTDM_Vline
Source port 4-EFP8-PORT10
Source C-VLAN 100, 110, 120, 130, 140
Sink port 3-IFU2
Sink C-VLAN 100, 110, 120, 130, 140
6.4.2.3 Service Planning (QoS on the Packet Plane)

This section provides the information about all the parameters required for configuring QoS on
the packet plane.

QoS (Diffserv)
configuration.

Type
CS7 7 -
CS6 6 -

streaming services)
AF4 4 -


AF1 1 -

services)
NOTE

in this example.

CS7 SP
CS6 SP
EF SP
BE SP

from the BTS.
QoS (Port Shaping)

node.
6.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board)

ports on the EFP8 board.
Information About Ethernet External Ports

Table 6-64 and Table 6-65 provide the information about the Ethernet ports that transmit the
Ethernet services.
Port enabled Enabled Enabled

NOTE
l In this example, the FE ports on all the BTSes/BSC work in auto-negotiation mode. Therefore, the FE
ports on the NEs that receive services from and transmit services to the BTSes/BSC must also work in
auto-negotiation mode. If the peer Ethernet ports work in a mode other than the auto-negotiation mode,
plan the local Ethernet ports to work in the same mode as the peer Ethernet ports. In the case of Ethernet
ports within a network, plan the Ethernet ports to work in auto-negotiation mode.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate
for QoS processing. The planning information of flow control must be the same for the equipment at
both ends.
l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the
ports are Tag Aware.
l In this example, the maximum frame length is planned to be the default value, 1522. If required, change
the maximum frame length according to the requirements of the specific BTS.
Information About VCTRUNKs

In EoPDH mode, a VCTRUNK can bind a maximum of 16 VC-12 channels. In this example, a
total of 40 Mbit/s Ethernet bandwidth is required, that is, 20 VC-12 channels are occupied.
Therefore, you need to configure two VCTRUNKs. In this example, configure the two
VCTRUNKs with the same number of VC-12 channels and then create the two VCTRUNKs
into a load-sharing LAG. Table 6-66 and Table 6-67 provide the information about the
VCTRUNKs that are configured to transmit the Ethernet services.

Parameter 4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2
Mapping protocol GFP GFP
Parameter 4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2
Mapping protocol GFP GFP
6.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board)

protection for the EFP8 board.
According to the information about the VCTRUNKs in this example, you need to configure the
two VCTRUNKs into a load-sharing LAG to increase the bandwidth. Table 6-68 and Table
6-69 provide the planning information of LAGs.
Table 6-68 Information about the LAG (NE1)
Parameter NE1
LAG type Static aggregation
Revertive mode -
Load sharing type Load sharing
Load sharing mode Load sharing based on IP

Parameter NE1
Main port 4-EFP8-VCTRUNK1
Slave port 4-EFP8-VCTRUNK2
Table 6-69 Information about the LAG (NE7)
Parameter NE7
LAG type Static aggregation
Revertive mode -
Load sharing type Load sharing
Load sharing mode Load sharing based on IP
Main port 4-EFP8-VCTRUNK1
Slave port 4-EFP8-VCTRUNK2
6.4.2.6 Service Planning (Ethernet Services on the EFP8 Board)

services on the EFP8 board.
LAGs are created on NE1 and NE7 in this example. Therefore, you need to configure services
only on the main ports. Table 6-70 and Table 6-71 provide the service planning information.
Parameter NE1
Between BTS6 and the Between NE2 and the

TDM Network TDM Network
Board 4-EFP8 4-EFP8
Service type EPL EPL
Source port VCTRUNK1 VCTRUNK1
Source VLAN 150 100, 110, 120, 130, 140
Sink port PORT1 PORT9
Sink VLAN 150 100, 110, 120, 130, 140


Parameter NE7
Between the TDM Network and the

BSC
Board 4-EFP8
Service type EPL
Source port VCTRUNK1
Source VLAN 100, 110, 120, 130, 140, 150
Sink port PORT1
Sink VLAN 100, 110, 120, 130, 140, 150
6.4.2.7 Service Planning (Cross-Connections)

This section provides the information about all the parameters required for configuring cross-
connections.
In this example, VC-12 timeslot cross-connections are set up between the first to twentieth
VC-12 timeslots (bound with VCTRUNKs) in VC4-1 on the 4-EFP8 board and the first to
twentieth ports on the 2-SP3D board. Table 6-72 and Table 6-73 provide the information about
cross-connections of the Ethernet services.

Parameter Value
Service level VC12
Source slot 4-EFP8
Source port 1
Source VC4 VC4-1
Sink slot 2-SP3D
Sink port -
Sink VC4 -

Parameter Value
Service level VC-12
Source slot 4-EFP8
Source port 1
Source VC4 VC4-1
Sink slot 2-SP3D
Sink port -
Sink VC4 -
6.4.2.8 Service Planning (QoS of the EFP8 Board)

This section provides the information about all the parameters required for configuring QoS of
the EFP8 board.
QoS (Flow)
Traffic classification is the prerequisite for configuring QoS of the EFP8 board. In this example,
VLAN-based EVPL services are created. Therefore, you need to create PORT+VLAN-based
flows. Table 6-74 and Table 6-75 provide the planning information of flows.
Table 6-74 Flow parameters (NE1)
Paramete Value
r
Flow type PORT PORT PORT PORT PORT PORT

+VLAN- +VLAN- +VLAN- +VLAN- +VLAN- +VLAN-
based flow based flow based flow based flow based flow based flow
Port 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8-

PORT1 PORT9 PORT9 PORT9 PORT9 PORT9
VLAN ID 150 100 110 120 130 140
Bound - - - - - -
CAR ID
Bound 1 1 1 1 1 1
CoS ID

Table 6-75 Flow parameters (NE7)

Paramete Value
r
Flow type PORT PORT PORT PORT PORT PORT

+VLAN- +VLAN- +VLAN- +VLAN- +VLAN- +VLAN-
based flow based flow based flow based flow based flow based flow
Port 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8-

VLAN ID 100 110 120 130 140 150
Bound - - - - - -
CAR ID
Bound 1 1 1 1 1 1
CoS ID
NOTE
According to the service classes of the BTS services, CoS with the ID of 1 schedules BTS services with different
VLAN priorities into egress queues with different forwarding priorities.
QoS (CAR)
In this example, CAR need not be configured.
QoS (CoS)
In this example, the BTS services are configured with corresponding VLAN priorities or DSCPs
based on the service types. The EFP8 board performs CoS processing for a BTS service
according to its VLAN priority or DSCP.
In this example, BTSs allocate VLAN priorities to services according to the service types.
Therefore, you need to configure CoS on Ethernet ports that receive services from and transmit
services to the BTSs, according to the service types. Table 6-76 and Table 6-77 provide the
CoS planning information.
Table 6-76 CoS attributes of the EFP8 board (NE1 and NE7)
Parameter Value
CoS ID 1
CoS type VLAN priority

Table 6-77 CoS parameters and corresponding BTS service types of the EFP8 board (NE1 and
NE7)
CoS Parameter CoS Priority Corresponding BTS
Service Type
User priority 0 in the VLAN 0 HSDPA data services (HSPA

tag interactive and HSPA
User priority 1 in the VLAN 3 -

tag
User priority 2 in the VLAN 4 R99 non-real-time services

tag (R99 interactive and R99
User priority 3 in the VLAN 5 OM and HSDPA real-time

tag services (OM streaming and

tag
User priority 5 in the VLAN 7 Real-time voice service and

tag signaling service (R99
streaming services)

tag

tag
NOTE
Queue 8 (namely, CoS priority 7) is the SP queue and queues 1 to 7 (namely, CoS priorities 0 to 6) are WRR
queues. Therefore, you need to map all high-priority services into queue 8 so that high-priority services can be
scheduled in time.
QoS (Shaping Based on the Egress Queues)

In this example, you need not configure traffic shaping based on the egress queues.

6.4.3.1 Configuration Process (Ethernet Ports on the Packet Plane)

This section describes the process for configuring Ethernet ports on the packet plane.
6.4.3.2 Configuration Process (Ethernet Services on the Packet Plane)
This section describes the process for configuring Ethernet services on the packet plane.
6.4.3.3 Configuration Process (QoS on the Packet Plane)

This section describes the procedure for configuring QoS on the packet plane.
6.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board)
This section describes the process for configuring Ethernet ports on the EFP8 board.
6.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board)
This section describes the process for configuring Ethernet protection on the EFP8 board.
6.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board)
This section describes the process for configuring Ethernet services on the EFP8 board.
6.4.3.8 Configuration Process (QoS on the EFP8 Board)
This section describes the procedures for configuring QoS on the EFP8 board.
6.4.3.1 Configuration Process (Ethernet Ports on the Packet Plane)

This section describes the process for configuring Ethernet ports on the packet plane.
Procedure
the Ethernet ports.
Parameter Value
4-EFP8-PORT10
of the Ethernet ports.
Parameter Value
4-EFP8-PORT10
TAG Tag Aware
Step 3 See A.12.7.1 Setting the General Attributes of the IF_ETH Port and set the basic attributes

Parameter Value
3-IFU2-1 5-IFU2-1
Parameter Value
3-IFU2-1 5-IFU2-1
----End
6.4.3.2 Configuration Process (Ethernet Services on the Packet Plane)

This section describes the process for configuring Ethernet services on the packet plane.
Procedure
Step 1 See A.12.3.2 Configuring the E-Line Service and create the E-Line services.
Parameter Value
Between NE2 and the TDM Network
Service ID 1
Service Name NE2toTDM_Vline
Direction UNI-UNI
Source Port 4-EFP8-PORT10
Source VLANs 100, 110, 120, 130, 140
Sink Port 3-IFU2-1
Sink VLANs 100, 110, 120, 130, 140
----End
6.4.3.3 Configuration Process (QoS on the Packet Plane)

This section describes the procedure for configuring QoS on the packet plane.

Procedure
Step 1 See A.12.10.1 Creating a DS Domain and create the DS domain.
follows.
Parameter Value
Packet Type CVLAN
0 BE
1 AF11
2 AF21
3 AF31
4 AF41
5 EF
6 CS6
7 CS7
BE 0
AF11 1
AF21 2
AF31 3
AF41 4
EF 5
CS6 6

CS7 7
NOTE
Parameter Value
NE1
Selected Port 3-IFU2-1

4-EFP8-PORT10
NOTE
The mapping relationship defined in the default DS domain is the same as the mapping relationship defined in
the DS domain that is created in this step. Therefore, you can skip this step.
Parameter Value
Policy ID 1

WRR (AF4 to AF1)
SP (BE)

60 (AF3)
30 (AF2)
5 (AF1)
policy.

Parameter Value
Port 3-IFU2-1
4-EFP8-PORT10
----End
6.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board)

This section describes the process for configuring Ethernet ports on the EFP8 board.
Procedure
Step 1 See A.13.4.1 Configuring External Ethernet Ports and configure the Ethernet external ports.
Parameter Value
Enabled/Disabled Enabled Enabled
Max Frame Length 1522 1522
Non-Autonegotiation Disabled Disabled

Flow Control Mode
Autonegotiation Flow Disabled Disabled

Control Mode
Parameter Value
4-EFP8-PORT1

Mode

Parameter Value
4-EFP8-PORT1
TAG Tag Aware
Port Attributes UNI
Step 2 See A.13.4.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs.
Parameter Value
Mapping Protocol UNI UNI
Port Attributes GFP GFP
Parameter Value
Mapping Protocol UNI UNI
Port Attributes GFP GFP

----End
6.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board)

This section describes the process for configuring Ethernet protection on the EFP8 board.
Procedure
Step 1 See A.13.1.1 Creating a LAG and create the LAGs.
Parameter Value
4-EFP8
LAG No 1
LAG Name ToTDM
LAG Type Static
Load Sharing Sharing
Sharing Mode IP Sharing Mode
Main Port VCTRUNK1
Selected Slave Ports VCTRUNK2
Parameter Value
4-EFP8
LAG No 1
LAG Name ToBSC
LAG Type Static
Load Sharing Sharing
Sharing Mode IP Sharing Mode
Main Port VCTRUNK1
Selected Slave Ports VCTRUNK2
Step 2 See A.13.1.2 Setting Parameters for LAGs and set the parameters for LAGs.

Parameter Value
4-EFP8
LAG No 1
LAG Name ToTDM
Parameter Value
4-EFP8
LAG No 1
LAG Name ToBSC
----End
6.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board)

This section describes the process for configuring Ethernet services on the EFP8 board.
Procedure
Step 1 See A.13.2.1 Creating Ethernet Private Line Services and create the Ethernet private line
services.
Parameter Value
Between BTS6 and the Between NE2 and the

TDM Network TDM Network
Board 4-EFP8 4-EFP8
Service Type EPL EPL
Source Port VCTRUNK1 VCTRUNK1
Source VLAN(e.g. 1,3-6) 150 100, 110, 120, 130, 140
Sink Port PORT1 PORT9
Sink VLAN(e.g. 1,3-6) 150 100, 110, 120, 130, 140

Parameter Value
Between the TDM Network and the

BSC
Board 4-EFP8
Service Type EPL
Source Port VCTRUNK1
Source VLAN(e.g. 1,3-6) 100, 110, 120, 130, 140, 150
Sink Port PORT1
Sink VLAN(e.g. 1,3-6) 100, 110, 120, 130, 140, 150
----End

Procedure
Step 1 See A.10.1 Creating the Cross-Connections of Point-to-Point Services and create the service
cross-connections.
Parameter Value
Level VC12
Source VC4 VC4-1
Sink Slot 2-SP3D
Sink VC4 -

Parameter Value
Level VC-12
Source VC4 VC4-1
Sink Slot 2-SP3D
Sink VC4 -
----End
6.4.3.8 Configuration Process (QoS on the EFP8 Board)

This section describes the procedures for configuring QoS on the EFP8 board.
Procedure
Step 1 See A.13.7.1 Creating a Flow and create the flows.
Paramet Value
er
4-EFP8
Flow Port Port Port Port Port Port

Type +VLAN +VLAN +VLAN +VLAN +VLAN +VLAN
Flow Flow Flow Flow Flow Flow
Port PORT1 PORT9 PORT9 PORT9 PORT9 PORT9
VLAN ID 150 100 110 120 130 140
Paramet Value
er
4-EFP8


Paramet Value
er
4-EFP8
VLAN ID 100 110 120 130 140 150
Step 2 See A.13.7.3 Creating the CoS and create the CoS.
Parameter Value
4-EFP8
CoS ID 1
CoS Type VLAN priority
CoS Parameter CoS Priority
User Priority 0 in the VLAN Tag 0
Parameter Value
4-EFP8
CoS ID 1
CoS Type VLAN priority

Step 3 See A.13.7.4 Binding the CAR/CoS and bind the CAR/CoS.
Paramet Value
er
4-EFP8

C-VLAN 150 100 110 120 130 140
Bound - - - - - -
CAR
Bound 1 1 1 1 1 1
CoS
Paramet Value
er
4-EFP8

C-VLAN 150 100 110 120 130 140
Bound - - - - - -
CAR
Bound 1 1 1 1 1 1
CoS
----End


Procedure
Step 1 See A.13.8.1 Creating MDs and create the maintenance domain on NE1 and NE7.
The values for the required parameters are provided as follows.
Parameter Value
NE1 NE7

Name
Maintenance Domain 4 4
Level
Step 2 See A.13.8.2 Creating MAs and create the maintenance domain on NE1 and NE7.
Parameter Value
Paramet Value
er
Maintena EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE

nce
Domain
Name
Maintena BTS1_Vli BTS2_Vli BTS3_Vli BTS4_Vli BTS5_Vli BTS6_Vli

nce ne ne ne ne ne ne
Associati
on Name
Step 3 See A.13.8.3 Creating MPs and create the maintenance domain on NE1 and NE7.
Parameter Value

Parameter Value
Node 4-EFP8-PORT1
VLAN ID 150
MP ID 101
Type MEP
Direction Ingress
CC Status Activate
Paramet Value
er
Maintena EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE

nce
Domain
Name
Maintena BTS1_Vli BTS2_Vli BTS3_Vli BTS4_Vli BTS5_Vli BTS6_Vli

nce ne ne ne ne ne ne
Associati
on Name
Node 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8- 4-EFP8-

VLAN ID 100 110 120 130 140 150
MP ID 701 702 703 704 705 706
Type MEP MEP MEP MEP MEP MEP
Direction Ingress Ingress Ingress Ingress Ingress Ingress
CC Activate Activate Activate Activate Activate Activate

Status
CCM 1000 1000 1000 1000 1000 1000

Sending
Period
(ms)
Step 4 On NE7, perform an LB test to test the Ethernet service configurations.

maintenance point and the maintenance point whose MP ID is 101 as the sink maintenance
point.

maintenance point and the maintenance point whose MP ID is 201 as the sink maintenance
point.
MEP and the maintenance point whose MP ID is 401 as the sink MEP.
NOTE
The sink maintenance points whose MP IDs are 201, 401, 501, and 601 need to be created on NE2 to NE6
respectively. The process for creating these sink maintenance points is not described in this section.
All LB tests should show that the tests are successful.
----End

Configuration Guide (U2000) 7 Configuring the Clock
7 Configuring the Clock
About This Chapter
To ensure that clocks of all the nodes on the transmission network are synchronized, configure
the clocks for these nodes according to a unified clock synchronization policy.
7.1 Basic Concepts

Before configuring the clock, you need to be familiar with the basic concepts.
This section describes the procedures for configuring the clock source, clock protection, and
output clock.
7.3 Configuration Example (Clock for a TDM Radio Chain Network)
the clock according to the network planning information.
7.4 Configuration Example (Clock for a TDM Radio Ring Network)
7.5 Configuration Example (Clock for a Hybrid Radio Chain Network)
clocks according to the network planning information.
7.6 Configuration Example (Clock for a Hybrid Radio Ring Network)
7.7 Configuration Example (Clocks Across a Third-party TDM Network)
This section considers Ethernet services transmitted across a third-party TDM network as an
example and describes how to configure clocks according to the planning information.

7 Configuring the Clock Configuration Guide (U2000)
7.1 Basic Concepts

Before configuring the clock, you need to be familiar with the basic concepts.
7.1.1 Clock Source

The clock source is used to synchronize parts of an NE, or upstream and downstream NEs, and
to provide stable and accurate operating frequency for the functional module and chip of an NE.
In this manner, the service can be transmitted correctly and in strict order.
7.1.2 Clock Protection Schemes
The OptiX RTN 950 supports the clock source protection based on priorities, synchronization
status message (SSM) protection, and extended SSM protection.
7.1.3 Clock Synchronization Policy
Users should plan a proper clock synchronization policy according to the network topology.
7.1.1 Clock Source

The clock source is used to synchronize parts of an NE, or upstream and downstream NEs, and
to provide stable and accurate operating frequency for the functional module and chip of an NE.
In this manner, the service can be transmitted correctly and in strict order.
The OptiX RTN 950 supports the following clock sources:
l Line clock source
Refers to a clock source that is extracted from the received SDH signal.
l Radio clock source
Refers to a clock source that is extracted from the received radio signal.
l Tributary clock source
Refers to a clock source that is extracted from the received PDH signal.
l Ethernet clock source
Refers to a clock source that is extracted from the FE/GE signal by using the synchronous
Ethernet function.
l External clock source
Refers to a clock source that is extracted from the 2 Mbit/s or 2 MHz signal that is received
at the external clock port.
l Internal clock source
Refers to a clock source that is generated through the free-run oscillation of the built-in
clock of an NE.
7.1.2 Clock Protection Schemes

The OptiX RTN 950 supports the clock source protection based on priorities, synchronization
status message (SSM) protection, and extended SSM protection.
Clock Source Protection Based on Priorities

The clock source protection is provided based on the priorities specified in the clock source
priority list. When the clock source of a higher priority fails, the clock source of a lower priority
is used.

As shown in Figure 7-1, the radio links between NE1 and NE2 adopt the 1+1 protection. NE2
needs to trace the clock on the radio links to keep synchronous with NE1. In this case, the clock
sources extracted by the main and standby IF boards can be configured in the clock source
priority list. The clock source extracted by the main IF board, however, has a higher priority.
Thus, if the 1+1 IF protection switching occurs on the radio links, the clock can be switched at
the same time.
Figure 7-1 Clock source protection based on priorities
1+1 protection
configuration
BITS NE1 NE2

Clock
SSM Protection
The SSM protection uses the SSM protocol specified in ITU-T G.781 to realize the clock
protection. According to the SSM protocol, the SDH NE transmits the SSM protocol through
bits 5-8 of the S1 byte, realizes the automatic protection switching of clock sources, and prevents
the timing loop. The OptiX RTN 950 supports the SSM protection on the SDH optical
transmission lines and STM-1 radio links. After the SSM protection is enabled on an NE, the
automatic protection switching of clock sources conforms to the following rules:
l According to the clock source priority list, the NE selects the clock source of the best quality
as the synchronization source.
l If multiple clock sources have the best quality, the NE selects the one of the highest priority
l By using the S1 byte, the NE broadcasts the information of the synchronization source
quality to the downstream NEs, and also notifies the upstream NE that the clock source
from the NE cannot be used for synchronization.
Figure 7-2 is an STM-1 radio ring where the SSM protection is enabled.
When the network operates normally, the NEs on the ring select the clock source as follows:
1. NE1 selects the external clock source as the synchronization source and notifies NE2 and
NE4 of the external clock quality.
2. NE2 and NE4 select the clock source from NE1 as the synchronization source and notify
NE1 that the clock sources from NE2 and NE4 are unusable.
3. NE3 detects that the clock sources from NE2 and NE4 have the same quality and selects
the clock source of a higher priority (the clock source from NE2) as the synchronization
source. In addition, NE3 transmits the information of the synchronization source quality to
NE4 and notifies NE2 that the clock source from NE3 is unusable.
4. NE4 detects that the clock sources from NE1 and NE3 have the same quality and selects
the clock source of a higher priority (the clock source from NE3) as the synchronization

source. In addition, NE4 transmits the information of the synchronization source quality to
NE1 and notifies NE3 that the clock source from NE4 is unusable.
5. According to the clock quality in west and east directions and the configured clock source
priorities, NE2, NE3, and NE4 determine that the synchronization source requires no
modifications. Thus, the clock source selection is finished.
When the radio links between NE1 and NE2 become faulty, the NEs on the ring select the clock
source as follows:
1. NE2 selects the internal source as the synchronization source and transmits the information
of the synchronization source quality to NE1 and NE3.
2. NE3 selects NE2 as the clock source and informs NE4 of the clock quality.
3. After detecting that the quality of the clock from NE1 is higher than the quality of the clock
from NE3, NE4 transmits the clock quality information to NE3 and informs NE1 that the
clock from NE4 is unavailable.
4. After detecting that the quality of the clock from NE4 is higher than the quality of the clock
from NE2, NE3 selects the clock source from NE4 as the synchronization source, transmits
the information of the synchronization source quality to NE2, and notifies NE4 that the
clock source from NE3 is unusable.
5. After detecting that the quality of the clock from NE3 is higher than the quality of the
internal clock source, NE2 selects the clock source from NE3 as the synchronization source,
transmits the information of the synchronization source quality to NE1, and notifies NE3
that the clock source from NE2 is unusable.
6. According to the clock quality in west and east directions and the configured clock source
priorities, NE2, NE3, and NE4 determine that the synchronization source requires no
modifications. Thus, the clock source selection is finished.
NOTE
The SSM protection does not provide a complete solution to the timing loop. Thus, when you configure clock
sources, the clocks cannot form a loop as on NE1 in this example.
Figure 7-2 SSM protection

BITS NE1
Extenal/
Internal
E W
W E
West/East/
West/East/
Internal
Internal
NE2 W NE4
E
W E
Master clock West/East/

NE3 Internal

Extended SSM Protection

The extended SSM protection uses the extended SSM protocol to provide the clock protection.
The extended SSM protocol, developed by Huawei on the basis of the SSM protocol, introduces
the concept of clock ID. Through the extended SSM protocol, you can define a clock ID for any
clock source. The clock ID of the synchronization source can be transmitted together with the
SSM protocol and be used for the automatic clock switching. The extended SSM protection is
available on the SDH optical transmission lines and the STM-1 radio links.
After the extended SSM protection is enabled on an NE, the automatic clock switching conforms
to the following rules:
l According to the clock source priority list, the NE selects the clock source of the best quality
l If the clock ID of a certain clock source indicates that the clock source is from the NE itself,
the clock source is not processed.
l If multiple clock sources have the best quality, the NE selects the one of the highest priority
l By using the S1 byte, the NE broadcasts the information of the synchronization source
quality to the downstream NEs, and also notifies the upstream NE that the clock source
from the NE cannot be used for synchronization.
The clock ID takes a value from 0 to 15. 0 is the default value, indicating that the clock ID is
invalid. After the extended SSM protocol is enabled on the NE, the NE does not select clock
source 0 as the current clock source.
The following principles need to be followed when allocating clock ID:
l When the extended SSM is used, the clock ID of an external clock source cannot be
automatically extracted and needs to be allocated.
l At all the nodes that access external clock sources, the internal clock sources should have
a clock ID.
l At all the intersection nodes of a ring/chain and a ring, the internal clock sources should
have a clock ID.
l At all the intersection nodes of a ring/chain and a ring, the line clock sources that are
accessed into the ring should have a clock ID.
l The clock sources other than the preceding four types should have a default clock ID of 0.
l Clock IDs are used for timing reference only. They do not indicate any priority difference.
Thus, the clock source has the same priority regardless of whether the clock ID is 1 or 15.
Figure 7-3 is an STM-1 radio ring where the extended SSM protection is enabled.
On the ring, the following clock sources require a clock ID:
l External clock source 1
l External clock source 2
l Internal clock source on NE1
l Internal clock source on NE3

Figure 7-3 Extended SSM protection

Master BITS NE1
Extenal/ West/
East/Internal
E W
W E
West/East/ West/East/
Internal
Internal
NE2 E W NE4
W E
West/
East/
NE3 Extenal/
Master clock Internal
Slave BITS
NOTE
l The extended SSM protection provides a complete solution to the timing loop. Thus, when you configure
clock sources, the clocks can form a loop.
l The extended SSM protection is advantageous in the complex networking of clock protection, for example,
the dual external clocks. Hence, the extended SSM protection is used in only a few cases.
7.1.3 Clock Synchronization Policy

Users should plan a proper clock synchronization policy according to the network topology.
Clock Synchronization Policy for a Chain Network

In the case of a chain network consisting of radio links, the clock synchronization policy should
be planned according to the following principles:
l The master (source) node accesses one clock source (which can be an external clock, a line
clock, or an Ethernet clock). On this node, the accessed clock source should be configured.
l In the case of the other nodes, the clock sources for their upper level radio links should be
configured.
l If the upper level radio link is configured with 1+1 protection, a node should be configured
with two radio clock sources, and the clock source for the main radio link should have a
higher priority than the clock source for the standby radio link.
l If a node has multiple upper level radio links (for example, the upper level radio links are
configured with XPIC or N+1 protection), each radio link should be configured with one
radio clock source on this node. In addition, these radio clock sources should be configured
with different priorities according to the actual condition.
l The SSM or extended SSM protection need not be configured.
Figure 7-4 shows the clock synchronization policy for a chain network.

l The master node (NE1) accesses one external clock source. In this case, the clock source
priorities for NE1 in a descending order are as follows: external clock source > internal
clock source.
l The IF1 boards in slots 3 and 5 on NE2 form a 1+1 IF protection group, where the IF1
board in slot 3 functions as the main board. In addition, the radio links between NE1 and
NE2 comprise the two IF1 boards. Hence, the clock source priorities for NE2 in a
descending order are as follows: 3-IF1-1 > 5-IF1-1 > internal clock source.
l The radio link between NE3 and NE2 comprises the IF1 board in slot 3 on NE3, and thus
the clock source priorities for NE3 in a descending order are as follows: 3-IF-1 > internal
clock source.
Figure 7-4 Clock synchronization policy for a chain network
NE1 NE2 NE3
BITS 3-IF1-1/
Extenal/ 3-IF1-1/
5-IF1-1/
Internal Internal
Internal
Clock
Clock Synchronization Policy for a Tree Network

A tree network can be considered the derivation of a chain network. Hence, a tree network can
adopt the same clock synchronization policy as a chain network.
Figure 7-5 shows the clock synchronization policy for a tree network.
l In the case of the master node (NE1), the port 1 on the EM6T board in slot 2 accesses the
Ethernet link, which functions as a clock source. Hence, the clock source priorities for NE1
in a descending order are as follows: 2-EMT6-1 > internal clock source.
l The IFX2 boards in slots 3 and 5 on NE2 form an XPIC working group, where the IFX2
board in slot 3 uses the vertical polarization mode and the IFX2 board in slot 5 uses the
horizontal polarization mode. In addition, the radio links between NE1 and NE2 comprise
the two IFX2 boards. Hence, the clock source priorities for NE2 in a descending order are
as follows: 3-IFX2-1 > 5-IFX2-1 > internal clock source.
l The radio link between NE3 and NE2 comprises the IFU2 board in slot 3 on NE3, and thus
the clock source priorities for NE3 in a descending order are as follows: 3-IFU2-1 > internal
clock source.
clock source.

clock source.
Figure 7-5 Clock synchronization policy for a tree network

NE3
3-IFU2-1/
NE1 NE2 Internal
NE4 NE5
BSC
2-EM6T-1/ 3-IFX2-1/
Internal 5-IFX2-1/
Internal
Clock 3-IFU2-1/ 3-IFU2-1/
Internal Internal
Clock Synchronization Policy for a Ring Network

If a ring network comprises only radio links or comprises radio links and optical transmission
lines, plan the clock synchronization policy according to the following principles:
l If only the SDH signal is transmitted on the ring, configure the SSM or extended SSM
protection according to the clock policy for an optical transmission network.
l If the PDH radio or Hybrid radio is used on certain segments of the ring, equally divide the
ring into two chains, and then plan the clock synchronization policy according to the
relevant policy for a chain network.
Figure 7-6 shows the clock synchronization policy for a ring on which only the SDH signal is
transmitted.
l Configure the SSM or extended SSM protection for all the nodes on the ring.
priorities in a descending order for NE1 are as follows: external clock source > internal
clock source.
l The clock source priorities for the other nodes in a descending order are as follows: west
clock source > east clock source > internal clock source.

Figure 7-6 Clock synchronization policy for a ring network (on which only the SDH signal is
transmitted)
BITS
NE2 NE1
NE6
West/East/ West/East/
Internal E Internal
W Extenal/ W E
E Internal W
W E
West/East/ E W
W E West/East/
Internal
Internal
NE3 NE5
NE4
West/East/
Master clock Internal
Figure 7-7 shows the clock synchronization policy for a ring on which not only the SDH signal
is transmitted.
l The ring uses the Hybrid radio for transmission. Thus, divide the ring into the following
chains at the master node (NE1): NE1-NE2-NE3 and NE1-NE4.
l In the case of the master node (NE1), the port 1 on the EM6T board in slot 2 accesses the
Ethernet link, which functions as a clock source. Hence, the clock source priorities for NE1
in a descending order are as follows: 2-EMT6-1 > internal clock source.
l NE2 traces the clock of the master node, and thus the clock source priorities for NE2 in a
descending order are as follows: west clock source > internal clock source.
l NE3 traces the clock of NE2, and thus the clock source priorities for NE3 in a descending
order are as follows: west clock source > internal clock source.
l NE4 traces the clock of the master node (NE1), and thus the clock source priorities for NE4
in a descending order are as follows: east clock source > internal clock source.

Figure 7-7 Clock synchronization policy for a ring network (on which not only the SDH signal
is transmitted)
BSC NE1
2-EM6T-1/
Internal
E W
W E
West/ East/
Internal Internal
NE2 W NE4
E
W E
West/
Internal
NE3
Clock
Clock Synchronization Policy for a Port Aggregation Network

On a port aggregation network, services of several OptiX RTN NEs are aggregated to the upper
level RTN NE through the optical transmission line, tributary, or Ethernet. Plan the clock
synchronization policy for a port aggregation network according to the following principles:
l The upper level NE accesses a clock source (which can be an external clock source, a line
clock source, or an Ethernet clock source).
l If the service of a lower-level NE is aggregated to the upper level NE through the optical
transmission line or Ethernet, the lower-level NE should trace the upper level line clock or
Ethernet clock.
l If the service of a lower-level NE is aggregated to the upper level NE only through the E1
signal, the lower-level NE should trace the tributary clock source (E1 ports 1 and 5 on the
E1 tributary board support the tributary clock source).
l If the service of a lower-level NE is aggregated to the upper level NE only through the E1
signal and the lower-level NE is connected to many hops of downstream radio links, tracing
the tributary clock source causes anomalies such as pointer justifications. In this case, the
lower-level NE should trace the external clock source output by the upper level NE.
Figure 7-8 shows the clock synchronization policy for a tributary port aggregation network.
priorities for NE1 in a descending order are as follows: external clock source > internal
clock source.
l The IF1 boards in slots 3 and 5 on NE2 form a 1+1 IF protection, where the IF1 board in
slot 3 functions as the main board. In addition, the radio links between NE1 and NE2
comprise the two IF1 boards. Hence, the clock source priorities for NE2 in a descending
order are as follows: 3-IF1-1 > 5-IF1-1 > internal clock source.

l The service of NE3 is aggregate to NE2 through ports 1 to 4 on the SP3S board in slot 1.
Hence, the clock source priorities for NE3 in a descending order are as follows: 1-SP3S-1
> internal clock source.
l NE4 is connected to many hops of downstream radio links. In this case, if it traces the
tributary clock source, pointer justifications occur on the downstream nodes. Hence, NE4
traces the external clock source output by NE2.
l The SSM protection or extended SSM protection need not be configured.
Figure 7-8 Clock synchronization policy for a port aggregation network (aggregation only
through the tributary port)
NE3
NE1 NE2
1-SP3S-1/
Internal
External/ 3-IF1-1/ NE4
Internal 5-IF1-1/
Internal
External/
Clock Internal
Clock Synchronization Policy for Transmission Across TDM Network

The clock synchronization policy for transmission across a leased TDM network is similar to
that for a chain network. The difference is that the lower-level node connected to the TDM
network needs to trace the tributary clock on the TDM network.
Figure 7-9 shows the clock synchronization policy for transmission across a TDM network.
l The main node NE1 is synchronized with the BSC through the FE port, and thus the clock
source priorities for NE1 in a descending order are as follows: 3-EFP8-1 > internal clock
source.
NOTE
The FE ports on the EFP8 board (PORT1 to PORT8) support synchronous Ethernet.
l On NE2, the SP3D board in slot 2 provides the E1 link connected to the TDM network,
and the NE is a lower-level node connected to the TDM network. Therefore, the clock
source priorities for NE2 in a descending order are as follows: 2-SP3D-1 > internal clock
source.
l The IFU2 boards in slots 3 and 5 on NE3 form a 1+1 IF protection group, where the IFU2
board in slot 3 functions as the main board. In addition, the radio links between NE3 and
NE2 comprise the two IFU2 boards. Hence, the clock source priorities for NE3 in a
descending order are as follows: 3-IFU2-1 > 5-IFU2-1 > internal clock source.
l The SSM protection or extended SSM protection is not configured.

Figure 7-9 Clock synchronization policy for transmission across TDM network
BSC NE1 NE2 NE3 BTS
FE E1 E1 FE
TDM network
3-EFP8-1 / 2-SP3D-1/ 3-IFU2-1/

Internal Internal 5-IFU2-1/
Internal
Clock
Precautions of Planning a Clock Synchronization Policy

When planning a clock synchronization policy, pay attention to the following points:
l The number of NEs on a long clock chain should not be more than 20. A number smaller
than 10 is recommended. If a large number of NEs exist on a long clock chain, add one
more clock source for signal compensation in the middle of the chain.
l It is recommended that the SDH optical port should be used at a convergence node to
converge the TDM service. In this manner, the clock signal can be transmitted over the
SDH signal rather than over the PDH signal, which ensures the quality of the clock signal.
Clock Synchronization Policy for a Base Station

If a synchronization signal is transmitted to a BTS through the radio transmission network, plan
the synchronization policy according to the following principles:
If the BTS can access the transmission network through an SDH optical port or Ethernet port,
use the SDH optical port or Ethernet port to provide the timing reference signal for the BTS.
If the BTS can access the transmission network only through the E1 signal, the external clock
port is preferred to transmit the timing reference signal to the BTS.
If the BTS can access the transmission network only through the E1 signal and the external clock
port cannot be used, use the E1 port to transmit the timing reference signal to the BTS. If the
output clock does not meet the requirement of the BTS, the NE that is connected to the BTS can
use the tributary retiming function.
If the BTS can be accessed to the transmission network through Ethernet only and does not
support the synchronous Ethernet function, you can provide the timing reference signal to the
BTS through the external clock port.
Tributary Retiming
When being transmitted by the OptiX RTN 950, the PDH signal must undergo mapping and
demapping processes, during which the jitter occurs. In addition, pointer justifications during
the network transmission process cause the jitter of the PDH signal.
Tributary retiming helps to reduce the jitter of the PDH signal when it is transmitted on a
transmission network. Tributary retiming realizes the transmission of the signal that combines

the timing reference signal and the PDH service signal. Hence, the transmitted PDH signal carries
the timing information that is synchronized with the timing reference signal.
Figure 7-10 shows how a BSC transmits the synchronization information to a BTS through the
radio transmission network after the tributary retiming function is enabled. The radio
transmission network extracts the tributary clock from the E1 signal that is transmitted from the
BSC. This tributary clock functions as the synchronization reference clock for the radio
transmission network to be synchronized with the clock of the BSC. The tributary retiming
function is enabled on NE3. In this manner, NE3 transmits the E1 signal that carries the retiming
clock information to the BTS (NE3 selects the system clock as the retiming clock). In addition,
NE3 is synchronized with the BSC. Hence, the BTS can extract the clock signal of the BSC from
the tributary signal.
The basic working principle of tributary retiming is as follows: The tributary signal is written
into a large-capacity first in first output (FIFO), and then the tributary signal is read from the
FIFO through the retiming clock. In this manner, the output signal contains the retiming clock
information, and FIFO eliminates the jitter and wander in the original tributary signal. The OptiX
RTN 950 can select the system clock or the line clock in the uplink E1 signal as the retiming
clock, depending on the specific networking. In general cases, the system clock is selected as
the retiming clock.
Figure 7-10 Tributary retiming
NE1 NE2 NE3
E1 E1
BSC
NE3
Write clk
Clock (downlink E1 clk)
E1 E1
FIFO
Read clk
(retiming clk)
When using the tributary retiming function, pay attention to the following points:
l The retiming clock should be synchronized with the clock of the BSC, and the retiming
clock should not undergo mapping and demapping processes.
l The tributary retiming function uses the FIFO, which causes a delay of 125 us or more. Use
this function when it is necessary.
l The retiming function requires that the entire transmission network should be synchronized
with the service network that requires retiming. If certain NEs on the transmission network
are not synchronized, slips occur.
l The transmission network can meet the retiming requirement of only one service network.


This section describes the procedures for configuring the clock source, clock protection, and
output clock.
Figure 7-11 provides the procedures for configuring clocks.
Figure 7-11 Configuration flow chart (clocks)

Required
Start
Optional
Configuring clock sources
Configuring the SSM or

extended SSM protection
Modifying clock switching

conditions
Modifying clock restoration

parameters
Modifying parameters of
the output clock
Setting parameters of PDH

ports
Querying the clock

synchronization status
End

Table 7-1 Procedures for configuring clocks

1 A.11.1 Configuring the Required. The parameters are set as follows:

Clock Sources l According to the clock source that is planned, set
Clock Source.
l The External Clock Source Mode and
Synchronous Status Byte parameters are valid
only for the external clock source. Set the two
parameters according to the actual condition of
the external clock. In general cases, the two
parameters take the default values.
2 Configuri A.11.2 Required when the SSM or extended SSM

ng the Configuri protection is used. Set the parameters as follows:
SSM or ng Clock l Set Protection Status according to the used
extended Subnets protocol type.
SSM
protection l If the clock uses the extended SSM protection,
set Clock Source ID for the following clock
sources:
– External clock source
– Internal clock source of the NE that accesses
the external clock source
– Internal clock source of the NE that connects
the intersecting ring and chain or connects the
intersecting rings
– Line clock source that is accessed to the ring
through the NE that connects the intersecting
ring and chain or connects the intersecting
rings and is configured with the line clock
source on the ring
The values of Clock Source ID for these clock
sources should be different.
A.11.4 Required when the SSM or extended SSM

Configuri protection.
ng the When a line port is connected to the NE on the same
SSM clock subnet, set Control Status to Enabled. In
Output other cases, set Control Status to Disabled.
Status
A.11.5 Required when the SSM or extended SSM

Configuri protection is used.
ng the When a line port is connected to the NE on the same
Clock ID clock subnet, set Enabled Status to Enabled. In
Output other cases, set Enabled Status to Disabled.
Status

A.11.3 Optional.
Self-
Defined
Clock
Quality
3 A.11.7 Changing the Optional.

Conditions for Clock
Source Switching
4 A.11.8 Modifying the Optional.

Recovery Parameter of
the Clock Source
5 A.11.6 Modifying the Optional when the external clock port is used to
Parameters of the transmit the clock reference signal for the customer
Clock Output equipment.
Set the parameters according to the requirement of
the customer equipment. In general cases, these
parameters take the default values.
6 A.17 Setting the Optional when the output tributary clock requires
Parameters of PDH retiming.
Ports Set Retiming Mode to Retiming Mode of Cross-
Connect Clock for the tributary port.
7 A.11.9 Querying the l When a clock subnet uses the internal clock
Clock Synchronization source of an NE as the reference clock, set NE
Status Clock Working Mode to Free-Run Mode for
this NE; set NE Clock Working Mode to
Tracing Mode for the other NEs.
l When a clock subnet uses the clock out of the
subnet as the reference clock, set NE Clock
Working Mode to Tracing Mode for all the
NEs.
7.3 Configuration Example (Clock for a TDM Radio Chain

Network)




configure the clocks according to the following network planning information (as shown in
Figure 7-12):
l The radio transmission network is directly synchronized with the clock of the BSC.
l Clock synchronization signals are transmitted to the BTSs over E1 signals.
Figure 7-12 Networking diagram (clocks on a TDM radio chain network)
BTS2 E1
STM-1 STM-1
E1
NE4
BTS3
E1
NE3 NE2 NE1 BSC
E1 BTS1
E1
NE6 NE5
BTS5 BTS4
The clock connections shown in Figure 7-12 are described as follows.
Table 7-2 Clock connections (NE1)

Between NE1 and the BSC 1-SL1D-1 (working port of a The ports are used to
linear MSP group) synchronizing NE1 with the
clock of the BSC.
1-SL1D-2 (protection port of
a linear MSP group)

Between NE2 and NE1 3-IF1 (main IF board of a 1+1 The ports are used to
HSB protection group) synchronizing NE2 with the
clock of the BSC.

Between NE3 and NE2 1-SL1D-1 This port is used to

synchronizing NE3 with the
clock of the BSC.
clock of the BSC.
clock of the BSC.
Between NE6 and NE5 3-IF1 This port is used to

clock of the BSC.

Clock Source Information

According to 7.1.3 Clock Synchronization Policy, Figure 7-13 shows the clock source
information.

Figure 7-13 Clock source information (TDM radio chain network)

3-IF1-1/5-IF1-1
Internal
STM-1 STM-1
NE4
NE3 NE2 NE1 BSC

3-IF1-1/ 1-SL1D-1/
1-SL1D-1/ 5-IF1-1/ 1-SL1D-2/
Internal Internal
Internal
NE6 NE5
4-IF1-1/
3-IF1-1/ 6-IF1-1/
Internal
Internal
Clock
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on
priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio network is synchronized with the BSC through the SDH optical port
and transmits the timing reference signal through the E1 port. Hence, the E1 retiming function

Procedure
Step 1 See A.11.1 Configuring the Clock Sources and configure the clock sources.
Paramete Value
r
Clock 1-SL1D-1 3-IF1-1 1-SL1D-1 3-IF1-1 4-IF1-1 3-IF1-1

Source 1-SL1D-2 5-IF1-1 Internal 5-IF1-1 6-IF1-1 Internal
Internal Internal Clock Internal Internal Clock
Clock Clock Source Clock Clock Source
Source Source Source Source
Step 2 See A.11.9 Querying the Clock Synchronization Status and query the clock synchronization
status of the NEs.

NE Clock Working Mode of all the NEs should be Tracing Mode.
----End
7.4 Configuration Example (Clock for a TDM Radio Ring

Network)


Based on 3.4 Configuration Example (Radio Links on the TDM Radio Ring Network),
Figure 7-14):
l The radio transmission network is directly synchronized with the clock of the BSC.
l Clock synchronization signals are transmitted to the BTSs over E1 signals.
Figure 7-14 Networking diagram (clocks on a TDM radio ring network)
E1
NE1
BSC
E1
BTS1 E1
E1 NE2 NE4 BTS4
BTS2
E1
NE3
BTS3


Between NE1 and the BSC 2-SP3S This port is used to

clock of the BSC.

clock of the BSC.
Between NE2 and BTS1 2-SP3S The ports are used for
enabling the re-timing
Between NE2 and BTS2 2-SP3S function so that the BTSs can
be more precisely
synchronized with the clock
of the BSC.

Between NE3 and NE2 3-IF1 This port is used to

clock of the BSC.
Between NE3 and BTS3 2-SP3S This port is used for enabling
the re-timing function so that
the BTS can be more
precisely synchronized with
the clock of the BSC.

clock of the BSC.

Between NE4 and BTS4 2-SP3S This port is used to

clock of the BSC.


information.
Figure 7-15 Clock source information (TDM radio ring network)

2-SP3S-1/
Internal
E1
NE1
BSC
NE2 NE4
3-IF1-1/ 4-IF1-1/
5-IF1-1 6-IF1-1
Internal Internal
NE3
Clock
3-IF1-1/
Internal
Clock Protection
In this example, a PDH radio ring network is set up. Thus, only the clock source protection based
on priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio network is synchronized with the BSC through the E1 port and
transmits the timing reference signal through the E1 port. Hence, the E1 retiming function needs
to be enabled. The retiming function needs to be enabled for the following ports:
l NE2: 2-SP3S-1, 2-SP3S-5

l NE3: 2-SP3S-1
l NE4: 2-SP3S-1
NOTE
In application, the external clock port, rather than the E1 port, is preferred to transmit the timing reference signal
to a BTS.

Procedure
Parameter Value
NE1 NE2 NE3 NE4
Clock Source 2-SP3S-1 3-IF1-1 3-IF1-1 4-IF1-1

Internal Clock 5-IF1-1 Internal Clock 6-IF1-1
Source Internal Clock Source Internal Clock
Source Source
Step 2 See A.17 Setting the Parameters of PDH Ports and set the PDH port parameters.
Parameter Value
NE2 NE3 NE4
Retiming Mode Retiming Mode of Retiming Mode of Retiming Mode of

Tributary Clock (2- Tributary Clock (2- Tributary Clock (2-
SP3S-1) SP3S-1) SP3S-1)
Retiming Mode of Normal (other ports) Normal (other ports)
Tributary Clock (2-
SP3S-5)
Normal (other ports)
status of the NEs.
----End

7.5 Configuration Example (Clock for a Hybrid Radio Chain

Network)
clocks according to the network planning information.


Figure 7-16):
l The radio transmission network is directly synchronized with the clock of the BSC through
a LAG consisting of two GE links.
l Clock synchronization signals are transmitted to the BTSs over FE signals.
Figure 7-16 Networking diagram (clocks on a Hybrid radio chain network)
FE
BTS2
GE GE
FE NE4
BTS3
FE
NE3 NE2 NE1 BSC
FE BTS1
FE
NE6 NE5
BTS5 BTS4


Between NE1 and the BSC 1-EM6F-1 (main port of a The ports are used to
LAG) synchronizing NE1 with the
clock of the BSC.
1-EM6F-2 (slave port of a
LAG)

Between NE2 and NE1 3-IFU2 (main IF board of a 1 The ports are used to
+1 HSB protection group) synchronizing NE2 with the
clock of the BSC.

Between NE3 and NE2 1-EM6T-1 This port is used to

clock of the BSC.

clock of the BSC.

clock of the BSC.

Between NE6 and NE5 3-IFU2 This port is used to

clock of the BSC.


information.
Figure 7-17 Networking diagram (clock for a Hybrid radio chain network)
3-IFU2-1/
5-IFU2-1
Internal
GE
NE4 GE
NE3 NE2 NE1 BSC

1-EM6T-1/ 3-IFU2-1/ 1-EM6F-1/
Internal 5-IFU2-1 1-EM6F-2/
Internal Internal
NE6 NE5
4-IFU2-1/
3-IFU2-1/ 6-IFU2-1
Internal Internal
Clock
NOTE
Separately configure the Ethernet clock source for each link in the LAG.
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on
priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio transmission network is synchronized with the BSC through the GE
port, and transmits the timing reference signal to the BTS through the FE port.


Procedure
Paramete Value
r
Clock 1-EM6F-1 3-IFU2-1 1-EM6F-1 3-IFU2-1 4-IFU2-1 3-IFU2-1

Source 1-EM6F-2 5-IFU2-1 Internal 5-IFU2-1 6-IFU2-1 Internal
Internal Internal Clock Internal Internal Clock
Clock Clock Source Clock Clock Source
Source Source Source Source
status of the NEs.
----End
7.6 Configuration Example (Clock for a Hybrid Radio Ring

Network)


Figure 7-18):

l The radio transmission network is directly synchronized with the clock of the BSC through
a LAG consisting of two GE links.
l Clock synchronization signals are transmitted to the BTSs over FE signals.
Figure 7-18 Networking diagram (clocks on a Hybrid radio ring network)
GE
NE1
BSC
FE
BTS1 FE
FE NE2 NE4 BTS4
BTS2
FE
NE3
BTS3

Between NE1 and the BSC 1-EM6T-5 (main port of a The ports are used to
LAG) synchronizing NE1 with the
clock of the BSC.
1-EM6T-6 (slave port of a
LAG)

clock of the BSC.


Between NE3 and NE2 3-IFU2 This port is used to

clock of the BSC.

clock of the BSC.


information.
Figure 7-19 Clock source information (Hybrid radio ring network)

1-EM6T-5/
1-EM6T-6/
Internal
FE
NE1
BSC
NE2 NE4
3-IFU2-1/ 4-IFU2-1/
5-IFU2-1 6-IFU2-1
Internal Internal
Clock NE3
3-IFU2-1/
Internal

NOTE
Separately configure the Ethernet clock source for each link in the LAG.
Clock Protection
In this example, a Hybrid radio ring network is set up. Thus, only the clock source protection
based on priorities is needed, whereas the SSM or extended SSM protection need not be
configured.

In this example, the radio transmission network is synchronized with the BSC through the FE
port, and transmits the timing reference signal to the BTS through the FE port.

Procedure
Parameter Value
NE1 NE2 NE3 NE4
Clock Source 1-EM6T-5 3-IFU2-1 3-IFU2-1 4-IFU2-1

1-EM6T-6 5-IFU2-1 Internal Clock 6-IFU2-1
Internal Clock Internal Clock Source Internal Clock
Source Source Source
status of the NEs.
----End
7.7 Configuration Example (Clocks Across a Third-party

TDM Network)
This section considers Ethernet services transmitted across a third-party TDM network as an
example and describes how to configure clocks according to the planning information.

The service planning information contains all the parameters required for configuring the NE
data.


This section describes the process for the data configuration.

Based on 6.4 Configuration Example (Ethernet Services Traversing a TDM Network),
Figure 7-20):
l The transmission network is directly synchronized with the clock of the BSC through FE
ports.
l Clock synchronization signals are transmitted to the BTS over FE ports.
NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2-
NE6, see 7.5 Configuration Example (Clock for a Hybrid Radio Chain Network).
Figure 7-20 Networking diagram (clocks across a third-party TDM network)

BTS2
BTS6
FE
FE
GE
FE NE4 TDM
FE E1 network
NE3 NE2 NE1
E1
FE
FE BTS1
FE
NE6 NE5 NE7
BSC
BTS4
BTS5
Figure 7-21 Board configuration (clocks across a third-party TDM network)
NE3 NE cascade NE2 NE1

NE4 FE CSH CSH CSH
E1 NE6 NE6 NE6
IFU2 EFP8 FE
IFU2 IFU2 IFU2 IFU2
NE6 BTS2
IFU2 EM6T SP3S EM6T SP3D SP3D
EM6T SP3S E1
GE
E1 E1 BTS6
FE BTS3 FE E1 TDM
BTS1 network
E1
CSH
CSH CSH
IFU2 NE6
NE6
IFU2 NE6
IFU2 IFU2
EFP8
SP3D
EM6T SP3S EM6T SP3S
NE6 NE5 E1 NE7 FE
FE
FE E1
BTS4
BTS5 BSC

The following figure shows the clock link connections of NE1 and NE7.
Table 7-22 Clock link connections (NE1)
Link Used Clock Port Description
Connected to the leased 2-SP3D-1 Used for synchronization

TDM network with the TDM network.
Table 7-23 Clock link connections (NE7)
Link Used Clock Port Description
Connected to the BSC 4-EFP8-1 Used for synchronization

with the BSC.

The service planning information contains all the parameters required for configuring the NE
data.

Based on 7.1.3 Clock Synchronization Policy, you can obtain the clock source information as
shown in Figure 7-22.
Figure 7-22 Information about clock sources (Hybrid radio chain network)
3-IFU2-1/
5-IFU2-1
Internal
GE
NE4 TDM
E1 network
NE3 NE2 NE1
1-EM6T-1/ 3-IFU2-1/ 2-SP3D-1/ E1
Internal 5-IFU2-1 Internal
FE
Internal
NE6 NE5
4-IFU2-1/ NE7
3-IFU2-1/ 6-IFU2-1 BSC
Internal Internal 4-EFP8-1/
Internal
Clock
NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2-
NE6, see 7.5 Configuration Example (Clock for a Hybrid Radio Chain Network).

Clock Protection
In this example, a chain network is set up. Therefore, only the clock source protection based on
priorities is configured and the SSM or extended SSM protection is not configured.

In this example, the radio transmission network is synchronized with the BSC through the FE
port on the EFP8 board of NE7, and transmits the timing reference signal to the base station
through the FE ports that accesses services from the base station.

This section describes the process for the data configuration.
Procedure
NE1 NE7
Clock Source 9-SP3D-1 4-EFP8-1

Internal Clock Source Internal Clock Source
status of the NEs.
For all NEs, set NE Clock Working Mode to Tracing Mode.
----End

Configuration Guide (U2000) 8 Configuring Auxiliary Ports and Functions
8 Configuring Auxiliary Ports and Functions
About This Chapter
The OptiX RTN 950 provides multiple auxiliary ports and functions. These functions require
certain data configuration.
8.1 Auxiliary Ports and Functions

This section describes the auxiliary ports and functions supported by the OptiX RTN 950,
namely, the orderwire, synchronous data services, asynchronous data services, and wayside
services, and external alarms.
8.2 Configuration Example (Orderwire)
This section considers the orderwire on a radio network as an example to describe how to plan
the orderwire according to network planning information.
8.3 Configuration Example (Synchronous Data Services)
This section considers a synchronous data service that transmits the network management
information as an example to describe how to configure a synchronous data service according
8.4 Configuration Example (Asynchronous Data Services)
This section considers an asynchronous data service that transmits the NM messages as an
example to describe how to configure an asynchronous data service according to the network
8.5 Configuration Example (Wayside E1 Services)
This section considers a wayside E1 service that transmits the NM messages as an example to
describe how to configure a wayside E1 service according to the network planning.
8.6 Configuration Example (External Alarms)
This section considers the centralized control of environment monitoring and equipment alarms
through external alarms as an example to describe how to configure external alarms according

8 Configuring Auxiliary Ports and Functions Configuration Guide (U2000)
8.1 Auxiliary Ports and Functions

This section describes the auxiliary ports and functions supported by the OptiX RTN 950,
namely, the orderwire, synchronous data services, asynchronous data services, and wayside
services, and external alarms.
Orderwire
The OptiX RTN 950 supports one orderwire phone so that the operation or maintenance
engineers at different workstations can perform voice communication through microwave or
SDH overhead bytes.
When using the orderwire phone, take the following precautions:
l The orderwire phone numbers of all the NEs on the network must be of the same length.
It is recommended that the orderwire telephone number is a 3-digit number and all orderwire
telephone numbers on the entire network are unique.
l The dialing method of the orderwire phone of each node is dual-tone multifrequency.
l The call waiting time of each node should be set to the same value. If less than 30 nodes
exist in the orderwire subnet, it is recommended that you set the call waiting time to five
seconds. If more than 30 nodes exist in the orderwire subnet, it is recommended that you
set the call waiting time to nine seconds.
l The equipment supports the orderwire group call function. When one set of the OptiX RTN
equipment dials the orderwire group call number "888", the orderwire phones of all the
OptiX equipment on the orderwire subnet ring. When an orderwire phone receives the call,
the orderwire phones on the other NEs stop ringing. In this case, the orderwire point-to-
multipoint group call changes to a point-to-point ordinary orderwire call.
l When the orderwire signals are transmitted over a radio link, they are always transmitted
through one customized overhead byte. When the orderwire signals are transmitted over
SDH fibers, they are transmitted through the E1 or E2 byte.
l By default, all the line ports, IF ports, and unconfigured synchronous data ports on the
equipment function as the orderwire ports. Therefore, in normal cases, the orderwire ports
needs to be configured only at the edge of the orderwire subnet.
l The equipment supports the transmission of orderwire overhead bytes through the 64 kbit/
s synchronous data ports or external clock ports.
l If multiple radio links or optical transmission lines exist between two NEs, the ports
corresponding to these links should be configured as the orderwire ports. In this case, except
for the hybrid radio links in N+1 protection, if one radio link is available between two NEs,
the orderwire transmission between two NEs is normal. When the orderwire signals are
transmitted over the hybrid radio links in N+1 protection, the protection link cannot transmit
the orderwire signals.
l The equipment provides the orderwire ports on the AUX board. For definitions of the pins
on the ports, see the OptiX RTN 950 IDU Hardware Description.
Synchronous Data Services

The synchronous data service is also called the F1 data service. The OptiX RTN 950 supports
one synchronous data service. The microwave/SDH overhead bytes transmitted between two
NEs can be used for transmitting one 64 kbit/s synchronous data service.

When using the synchronous data service, take the following precautions:
l The synchronous data service is fully transparently transmitted, and the transmission rate
at the port is 64 kbit/s.
l The synchronous data service is clock-sensitive. If the clock is not synchronized, bit errors
occur.
l The ports on the equipment comply with ITU-T G.703.
l When the orderwire signals are transmitted over a radio link, they are always transmitted
SDH fibers, they are always transmitted through the F1 byte.
l The equipment supports the transmission of the overhead bytes in the synchronous data
service through the external clock ports to realize the service spanning function.
l When the synchronous data service is transmitted over the protected radio links or optical
transmission lines, the synchronous data service is also protected.
l The equipment provides the synchronous data service ports on the AUX. For definitions
of the pins on the ports, see the OptiX RTN 950 IDU Hardware Description.
Asynchronous Data Services

The asynchronous data service is also called a transparent data service or a broadcast data port
service. The OptiX RTN 950 supports one asynchronous data service. The microwave/SDH
overhead bytes transmitted between two sites can be used for realizing full-duplex
communication between the universal asynchronous receiver/transmitter (UART).
When using the asynchronous data service, take the following precautions:
l The asynchronous data service is fully transparently transmitted. The transmission rate and
transmission control protocol need not be configured. The transmission rate at the port is
19.2 kbit/s.
l The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit errors
occur.
l The equipment provides the RS-232 electrical port that complies with ITU-T V.24/V.28.
l The equipment supports only point-to-point communications.
l When the orderwire signals are transmitted over radio links, they are always transmitted
SDH fibers, they are transmitted through any of the SERIAL 1 to SERIAL 4 bytes.
l The equipment supports the transmission of the overhead bytes in the asynchronous data
service through the external clock ports to realize the service spanning function.
l When the asynchronous data service is transmitted over the protected radio links or optical
transmission lines, the asynchronous data service is also protected.
l The equipment provides the asynchronous data ports on the AUX board. For definitions of
the pins on the ports, see the OptiX RTN 950 IDU Hardware Description.
Wayside E1 Services
The OptiX RTN 950 supports one wayside E1 service. The transmitted overhead bytes in the
STM-1 radio signals can be used for transmitting one wayside E1 service between two sites in
one hop of STM-1 radio link.
When using the wayside E1 service, take the following precautions:

l The wayside E1 service is supported by only STM-1 radio links or E1 radio links.
l The wayside E1 service is fully and transparently transmitted, and the transmission rate at
the port is 2048 kbit/s.
l The wayside E1 service is clock-sensitive. If the clock is not synchronized, bit errors occur.
l The equipment does not support the pass-through of the wayside E1 service. Therefore, the
wayside E1 service is transmitted only between two sites on one hop of radio link.
l When the wayside E1 service is transmitted over the radio links in 1+1 or N+1 protection
mode, the wayside E1 service is also protected.
l The equipment adds or drops the wayside E1 service through the external clock port on the
SCC, cross-connect and clock board. The external clock port complies with ITU-T G.703,
and the impedance on the path is 120 ohms. For definitions of the pins on the external clock
ports, see the OptiX RTN 950DU Hardware Description.
External Alarms
External alarms are also called Boolean alarms or relay alarms. The OptiX RTN 950 provides
external alarms.
Figure 8-1 shows the port circuits of the input external alarms. When the external relay is
switched off, the port circuit generates a high-level signal. When the external relay is switched
on, the port circuit generates a low-level signal. The board generates the corresponding alarm
based on the level that is generated by the port circuit. Input external alarms are mainly used for
accessing the relay alarms generated by the environmental alarm generator.
Figure 8-1 Circuits for the input external alarms
Circuit for external +3.3 V/+5 V External

alarm input Pull-up system
resistance Relay
Output level
The port circuits for the output external alarms function the same as the external system shown
in Figure 8-1. When the external alarm output conditions specified for the NE are met, the NE
drives the relay to turn on or off the switch according to the conditions that result the alarm.
Otherwise, the NE drives the relay to change the switch to the reverse status that results in the
alarm. Output external alarms are mainly used for indicating the alarm status of the equipment
that is contained by the centralized alarming devices.
The equipment provides the external alarm ports on the AUX board. For definitions of the pins
on the ports, see the OptiX RTN 950 IDU Hardware Description.
8.2 Configuration Example (Orderwire)

This section considers the orderwire on a radio network as an example to describe how to plan
the orderwire according to network planning information.



In the networking diagram shown in Figure 8-2, each NE needs to be configured with the
orderwire. Except that the radio links between NE1 and NE2 are configured with 1+1 protection,
all the other radio links are configured with 1+0 non-protection.
Figure 8-2 Networking diagram (orderwire)
1+0
1+1
NE4 E1
1+0
NE3 NE2 NE1
1+0
NE6 NE5
Table 8-1 Orderwire phone connections (NE1)
Between NE1 and NE2 3-IFU2 (main IF board) Configure the ports to
implement IF 1+1 protection.
Between NE2 and NE1 3-IFU2 (main IF board) Configure the ports to
implement IF 1+1 protection.
Between NE2 and NE3 F1 The two NEs are

interconnected through
synchronous data ports.




signals.

signals.


signals.


signals.

signals.


signals.


Information About Orderwire Phone Numbers

In this example, the number of NEs is very small. Therefore, the orderwire phone numbers are
allocated in the format of 100+NE ID, as shown in Figure 8-3.
Figure 8-3 Networking diagram (for orderwire)
1+0
104 1+1
NE4
1+0 E1
NE3 NE2 NE1
1+0
101
102
103
NE6 NE5
105
106
Information About Orderwire Ports

l In this example, the service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The 64 kbit/s synchronous data service port is used
for service spanning.
l NE2 to NE6 are located on the orderwire subnet. Hence, they use the default orderwire
ports (all the IF ports, line ports, and unconfigured synchronous data ports) that are
automatically mapped by the equipment.
l NE1 is not located at the edge of the orderwire subnet. Hence, it is configured according
to the situation of NE2 to NE6. If NE1 is located at the edge of the orderwire subnet and
if it is connected to an IF ports or line ports on the other orderwire subnets, the IF ports or
line ports are deleted from the orderwire ports through the NMS.
l The information about orderwire ports of each NE is provided in Table 8-7.
Table 8-7 Information about orderwire ports
NE Orderwire Port
NE1 3-IFU2-1
5-IFU2-1
NE2 3-IFU2-1
5-IFU2-1
F1
NE3 3-IFU2-1
4-IFU2-1
F1

NE Orderwire Port
NE4 3-IFU2-1
NE5 3-IFU2-1
4-IFU2-1
NE6 3-IFU2-1
NOTE
l An external clock port can also be used to realize service spanning between NE2 and NE3. In this case, the
external clock port needs to be added to the orderwire port through the NMS.
l Certain orderwire ports are unnecessary. These ports do not, however, affect the orderwire phones if they
do not receive orderwire signaling.
Information About Orderwire Parameters

l Fewer than 30 NEs exist on the orderwire subnet. Hence, the call waiting time needs to be
set to five seconds for these NEs.
l In this example, the SDH optical transmission equipment is not involved on the orderwire
subnet. Therefore, the overhead byte is set to E1 by default.

Procedure
Step 1 See A.19.1 Configuring the Orderwire and configure the orderwire.
Paramete Value
r
Call 5 5 5 5 5 5
Waiting
Time(s)
Phone 1 101 102 103 104 105 106
Selected 3-IFU2-1 3-IFU2-1 3-IFU2-1 3-IFU2-1 3-IFU2-1 3-IFU2-1

Orderwir 5-IFU2-1 5-IFU2-1 4-IFU2-1 4-IFU2-1
e Port
F1 F1
----End

8.3 Configuration Example (Synchronous Data Services)

This section considers a synchronous data service that transmits the network management
information as an example to describe how to configure a synchronous data service according


In the networking diagram shown in Figure 8-4, the radio network transmits the network
management messages of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management messages carried by the Ethernet
network into the network management messages carried by the 64 kbit/s synchronous data
service. Hence, the radio network needs to transparently transmit the corresponding synchronous
data only.
l NE1 and NE6 add or drop 64 kbit/s synchronous data services. NE2, NE3, and NE5 pass
through 64 kbit/s synchronous data services.
l Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all
the other radio links are configured with 1+0 non-protection.
Figure 8-4 Networking diagram (synchronous data services)

3rd party NM
1+0
1+1
3rd party ETH
equipment NE4 E1 64kbps
1+0
NE3 NE2 NE1 64k/ETH
1+0
ETH Converter
64kbps
NE6 NE5
64k/ETH
Converter

Table 8-8 Connections of synchronous data services (NE1)

Between NE1 and a protocol F1 Configure this port to access

converter synchronous data services.
Between NE1 and NE2 3-IFU2 (main IF board of a 1 Configure the main IF board
+1 protection group) to transmit synchronous data
services.

+1 protection group) to transmit synchronous data
services.


Between NE3 and NE5 4-IFU2 Configure this port to

transmit synchronous data
services.



services.

services.


services.
Between NE6 and a protocol F1 Configure this port to access

converter synchronous data services.

l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The two synchronous data ports between NE2 and
NE3 are interconnected with each other to realize the service spanning function.
l According to the service path, you can obtain the synchronous data service information
Table 8-13 Information about the synchronous data service
NE Data Channel 1 Data Channel 2
NE1 F1 3-IFU2-1
NE2 3-IFU2-1 F1
NE3 F1 4-IFU2-1
NE5 4-IFU2-1 3-IFU2-1
NE6 3-IFU2-1 F1
NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3.
l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active
link is configured with the synchronous data service.

Procedure
Step 1 See A.19.2 Configuring the Synchronous Data Service and configure the synchronous data
services.

Parameter Value
NE1 NE2 NE3 NE5 NE6
Data F1 3-IFU2-1 F1 4-IFU2-1 3-IFU2-1

Channel 1
Data 3-IFU2-1 F1 4-IFU2-1 3-IFU2-1 F1

Channel 2
----End
8.4 Configuration Example (Asynchronous Data Services)

This section considers an asynchronous data service that transmits the NM messages as an
example to describe how to configure an asynchronous data service according to the network


In the networking diagram shown in Figure 8-5, the radio network transmits the network
management information of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management information carried by the
Ethernet network into the network management information carried by the RS-232 synchronous
data service. Hence, the radio network needs to transparently transmit the corresponding
synchronous data only.
l NE1 and NE6 add or drop asynchronous data services. NE2, NE3, and NE5 pass through
asynchronous data services.
l Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all
the other radio links are configured with 1+0 non-protection.

Figure 8-5 Networking diagram (asynchronous data services)

3rd party NM
1+0
1+1
3rd party ETH
equipment NE4 E1 RS-232
1+0
NE3 NE2 NE1 RS-232/ETH
1+0
ETH Converter
RS-232
NE6 NE5
RS-232/ETH
Converter
Table 8-14 Connections of asynchronous data services (NE1)
Between NE1 and a protocol SERIAL1 Configure this port to access

converter asynchronous data services.
+1 protection group) to transmit asynchronous
data services.
+1 protection group) to transmit asynchronous
data services.
Between NE2 and NE3 SERIAL1 The two NEs are

asynchronous data ports.

transmit asynchronous data
services.
Between NE3 and NE2 SERIAL1 The two NEs are

asynchronous data ports.


services.

services.

services.
Between NE6 and a protocol SERIAL1 Configure this port to access

converter asynchronous data services.

l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The two asynchronous data ports between NE2
and NE3 are interconnected with each other to realize the service spanning function.
l In this example, the SDH equipment is not required to jointly transmit the asynchronous
data service. Hence, the overhead byte is set to SERIAL1.
l According to the service path, you can obtain the asynchronous data service information
Table 8-19 Information about the asynchronous data service
NE Broadcast Data Source Broadcast Data Sink
NE1 SERIAL1 3-IFU2-1
NE2 3-IFU2-1 SERIAL1
NE3 SERIAL1 4-IFU2-1
NE5 4-IFU2-1 3-IFU2-1
NE6 3-IFU2-1 SERIAL1

NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3.
l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active
link is configured with the asynchronous data service.

Procedure
Step 1 See A.19.3 Configuring the Asynchronous Data Service and configure the asynchronous data
services.
Parameter Value
NE1 NE2 NE3 NE5 NE6
Overhead SERIAL1 SERIAL1 SERIAL1 SERIAL1 SERIAL1

Byte
Broadcast SERIAL1 3-IFU2-1 SERIAL1 4-IFU2-1 3-IFU2-1

Data Source
Selected 3-IFU2-1 SERIAL1 4-IFU2-1 3-IFU2-1 SERIAL1

Broadcast
Data Sink
----End
8.5 Configuration Example (Wayside E1 Services)

This section considers a wayside E1 service that transmits the NM messages as an example to
describe how to configure a wayside E1 service according to the network planning.


In the networking shown in Figure 8-6, the STM-1 radio network transmits the network
management information of the third-party equipment. The third-party equipment and the NMS

use the protocol converter to convert the network management information carried by the
Ethernet network into the network management information carried by the wayside E1 service.
To maximize the bandwidth utilization, the NEs transmit the service over the wayside E1
channel.
Figure 8-6 Networking diagram (wayside E1 services)
3rd party 3rd party

equipment NM
3-IF1 to NE1 3-IF1 to NE2

ETH ETH
E1 E1
STM-1
E1/ETH NE2 NE1 E1/ETH

Converter Converter

According to the service path, you can obtain the wayside E1 service information provided in
Table 8-20.
Table 8-20 Information about wayside E1 services
NE IF Board Whether to Enable Input Slot of the

the Wayside E1 Wayside E1
Service Service
NE1 3-IF1 Enabled 7
NE2 3-IF1 Enabled 7
NOTE
In the case of radio links configured with 1+1 or N+1 protection, only the active link is configured with the
wayside E1 service.

Procedure
Step 1 See A.19.4 Configuring the Wayside E1 Service and configure the wayside E1 service.

Parameter Value
NE1 NE2
Port NE1-3-IF1-1 NE2-3-IF1-1
2M Wayside Enable Status Enabled Enabled
2M Wayside Input Board 7 7
----End
8.6 Configuration Example (External Alarms)

This section considers the centralized control of environment monitoring and equipment alarms
through external alarms as an example to describe how to configure external alarms according


In the networking diagram shown in Figure 8-7, the external alarms on NE1 are required as
follows:
l External alarm input port 1 is used for connecting the alarm port on the smoke sensor. When
the alarm port on the smoke sensor is closed, NE1 should report a fire alarm.
l External alarm input port 2 is used for connecting the alarm port on the water sensor. When
the alarm port on the water sensor is closed, NE1 should report a water alarm.
l External alarm input port 3 is used for connecting the alarm port on the magnetic door
switch sensor. When the alarm port on the magnetic door switch sensor is closed, NE1
should report an alarm, indicating that the cabinet door is open.
l External alarm output port 1 is used for connecting the centralized alarming boxes. When
a major or critical alarm is generated on NE1, the alarm output port is closed.

Figure 8-7 Networking diagram (external alarms)

2-AUX
Input 1
Smoke sensor
Input 2
NE1
Output 1
Water sensor Input 3
Magnetic door
Centralized
switch sensor
alarming box

Information About Input Alarms

According to the requirements, you can obtain the input alarm information provided in Table
8-21.
Table 8-21 Information about input alarms

Input External Usage Status Alarm Mode Alarm Name Severity
Alarm
Interface 1 Used An alarm is Fire alarm Major

generated when
the port is
closed.
Interface 2 Used An alarm is Water alarm Major

generated when
the port is
closed.
Interface 3 Used An alarm is Open cabinet Major

generated when door
the port is
closed.
Information About Output Alarms

According to the requirements, you can obtain the output alarm information provided in Table
8-22.

Table 8-22 Information about output alarms

Output External Alarm Usage Status Working Mode
Interface 1 Used Automatic Mode
NOTE
The OptiX RTN 950 supports the automatic mode and the manual mode. The manual mode is used for
commissioning the output alarms.

Procedure
Step 1 See A.19.5 Configure External Alarms and configure the external alarms.
l The values for the input alarm parameters are provided as follows.
Parameter Value
NE1
Operation Object NE1-2-AUX- NE1-2-AUX- NE1-2-AUX-

CSK-1 CSK-2 CSK-3
Path Name Fire alarm Water alarm Open cabinet door
Using Status Used Used Used
Alarm Mode Relay Turns On/ Relay Turns On/ Relay Turns On/
Low Level Low Level Low Level
Alarm Severity Major Alarm Major Alarm Major Alarm
l The values for the output alarm parameters are provided as follows.
Parameter Value
NE1
Operation Object NE1-2-AUX-CSK-1
Use or Not Used
----End

Configuration Guide (U2000) 9 Adding and Modifying Configuration Data
9 Adding and Modifying Configuration Data
About This Chapter
During the equipment commissioning and operating phases, you need to add or modify certain
configuration data according to the actual requirements.
9.1 Common Task Collection (Network Topology)

Common tasks associated with the network topology include common configuration tasks
associated with NE attributes.
9.2 Common Task Collection (Radio Links)
This section describes the common configuration tasks associated with radio links.
9.3 Common Task Collection (TDM Services)
This section describes the common configuration tasks associated with TDM services.
9.4 Common Task Collection (Packet-Plane Ethernet Services)
This section describes the common configuration tasks associated with packet-plane Ethernet
services.
9.5 Common Task Collection (EoPDH-Plane Ethernet Services)
This section describes the common configuration tasks associated with EoPDH-plane Ethernet
services.

9 Adding and Modifying Configuration Data Configuration Guide (U2000)
9.1 Common Task Collection (Network Topology)

Common tasks associated with the network topology include common configuration tasks
associated with NE attributes.
Table 9-1 Common task collection (NE attributes)
Task Application Configuration Description

Scenario Operation
Creating NEs When using the NMS A.1.1 Creating NEs by l Generally, NEs
to perform centralized Using the Search are created by
management of NEs, Method or A.1.2 searching for the
create the icons of the Creating NEs by Using NE on the NMS.
NEs to be managed at the Manual Method l The manual NE
corresponding creation method
positions on the Main is applicable only
Topology. when several NEs
need to be created
on a large radio
transmission
network.
Changing an You need to change an A.1.4 Changing the NE -

NE ID NE ID, if the NE ID ID
does not meet the
network planning
requirements (for
example, if the NE ID
is the same as another
NE ID).
Changing the You need to change the Changing the IP -

IP address of an IP address of the address of an NE
NE gateway NE if changes
occur in the external
DCN between the
NMS server and the
gateway NE.
Synchronizing After you conduct the A.1.6 Synchronizing To ensure that the NE
NE time settings on the NMS, the NE Time time is synchronized
the NE time is correctly, the time
synchronized and time domain of
automatically and the NMS server must
periodically. You can be set correctly.
also synchronize the
NE time manually if
the NE time is lost due
to NE faults.

9.2 Common Task Collection (Radio Links)

This section describes the common configuration tasks associated with radio links.
CAUTION
When you add or modify the configurations of a radio link, you need to modify the configurations
of the NE that is located far from the NMS server and then modify the configurations of the NE
that is located near to the NMS server.
NOTE
l In the case of 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main
radio link.
l In the case of 1+1 FD protection, you need to configure the IF/ODU information of the main radio link
and the ODU information of the standby radio link.
l In the case of XPIC configuration, you need to configure the IF/ODU information of the two radio
links in different polarization directions separately.
l In the case of N+1 protection, you need to configure the IF/ODU information of the N+1 radio links
respectively.
Table 9-2 Common task collection (radio links)

Scenario Operation
Changing the You need to change the 1. A.10.5 Deleting If the capacity of the
radio working radio working mode of Cross-Connections existing TDM
mode of a a TDM radio link, if the services exceeds the
TDM radio link TDM radio link does capacity of the TDM
not meet the service radio link after the
capacity requirements. change, you need to
delete the cross-
connections of the
excessive TDM
services.
2. A.8.4 Configuring Before you change

the IF/ODU the radio working
Information of a Radio mode, it is
Link recommended that
you consult the
network planning
department to check
whether the radio link
supports the new
radio working mode.


Scenario Operation
Configuring The ATPC function A.8.6 Configuring the To enable the ATPC
the ATPC needs to be enabled for ATPC Attributes function, set ATPC
function the radio link or the Enable Status to
values of ATPC Enabled and change
parameters need to be other ATPC
changed. parameter values
according to the
planning
information.
Changing the You can change the A.8.4 Configuring the In Power Attributes
transmit power transmit power if the IF/ODU Information of the ODU, change
fading margin is of a Radio Link TX Power(dBm) or
insufficient but the parameter values
transmit power can still associated with
be increased. power.
Upgrading a 1 To improve reliability 1.A.8.1 Creating an IF In the case of IF 1+1

+0 radio link to of a 1+0 radio link, 1+1 Protection Group protection, the
a 1+1 HSB/SD/ upgrade the 1+0 radio original IF board
FD radio link link to a 1+1 HSB/SD/ functions as the main
FD radio link. IF board.
2.A.8.4 Configuring the Ensure that TX

IF/ODU Information Status of the standby
of a Radio Link ODU is Unmute.
Changing the When the original A.8.4 Configuring the l Before using the
modulation modulation scheme IF/ODU Information new modulation
scheme of a does not meet the of a Radio Link scheme, contact
Hybrid radio service requirements, the network
link you need to use another planning
modulation scheme. department to
confirm that the
Hybrid radio link
supports the new
Modulation
Mode of the
Guarantee AM
Capacity and
Modulation
Mode of the Full
AM Capacity.
l Ensure that the
parameter values
are the same at
both ends of the
Hybrid radio link.


Scenario Operation
Changing the To adjust the number A.8.4 Configuring the l To reduce E1s
number of E1s of E1s and Ethernet IF/ODU Information with high
on a Hybrid bandwidth, you need to of a Radio Link priorities, you
radio link change the number of need to delete the
E1s on the Hybrid corresponding
radio link. cross-connections
before changing
Guarantee E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
l To increase E1s
with high
priorities, you
need to add the
corresponding
cross-connections
after changing
Guarantee E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
NOTE
The number of
added E1s should
be within the
specified range.
l To reduce E1s
with low
priorities, you
need to delete the
corresponding
cross-connections
before changing
Full E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
l To increase E1s
with low


Scenario Operation
priorities, you
need to add the
corresponding
cross-connections
after changing
Full E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
NOTE
The number of
added E1s should
be within the
specified range.
l The
MW_CFG_MIS
MATCH alarm
occurs when the
number of E1
services is
different on both
ends of the radio
link. The alarm
clears when the
number of E1
services is the
same on both ends
of the radio link.


Scenario Operation
Changing the You can change the A.8.9 Modifying the l When you change
priority of E1 priority of E1 services Priorities of E1 the priority of an
services on a on a Hybrid radio link. Services E1, the E1 is
Hybrid radio interrupted
link transiently.
l If the number of
E1s with high
priorities exceeds
the value of
Modulation
Mode of the
Guarantee AM
Capacity, you
need to increase
the value of
Modulation
Mode of the
Guarantee AM
Capacity before
changing the
priorities.
9.3 Common Task Collection (TDM Services)

This section describes the common configuration tasks associated with TDM services.
Table 9-3 Common task collection (TDM services)

Scenario Operation
Adding TDM More TDM services A.10.1 Creating the -

services need to be accessed on Cross-Connections of
the network. Point-to-Point Services
or A.10.2 Creating
Cross-Connections of
SNCP Services
Deleting TDM If the line resources are A.10.5 Deleting Cross- -

services insufficient, you need Connections
to delete the TDM
services that are not
used to release the
corresponding
resources.


Scenario Operation
Upgrading an Upgrade an A.9.1 Configuring In the case of linear

unprotected unprotected link to a Linear MSP MSP, the existing
link to a linear linear MSP link to line port functions as
MSP link improve service the working port.
reliability. Upgrading an
unprotected link to a
linear MSP link does
not interrupt the
existing services.
Upgrading Upgrade normal A.10.6 Converting a Only the normal

normal services to SNCP Normal Service into an services in the
services to services to improve SNCP Service receive direction are
SNCP services service reliability. converted to SNCP
services. Therefore,
you need to configure
the unidirectional
cross-connections
from the SNCP
services to the
working trail and
from the SNCP
services to the
protection trail so that
the normal services
both in the receive
direction and in the
transmit direction are
converted to SNCP
services.
9.4 Common Task Collection (Packet-Plane Ethernet

Services)
This section describes the common configuration tasks associated with packet-plane Ethernet
services.
Table 9-4 Common task collection (Packet-plane Ethernet services)

Task Application Configuration Operation Description
Scenario
Creating Create the Ethernet 5 Configuring Packet-Based -

Ethernet services according to Ethernet Services
services the service planning
information.


Scenario
Setting or The service A.12.6 Setting the Parameters -

modifying the requirements or of Ethernet Ports
parameters of configuration at the
Ethernet ports opposite end change.
As a result, the
parameters of the
Ethernet port need to be
changed.
Deleting Delete the Ethernet A.12.3.6 Deleting an E-Line -

Ethernet services that are not Service or A.12.3.7 Deleting
services used to release the E-LAN Services
corresponding
resources.
Creating a l When the available A.12.2.1 Creating a LAG l When using

LAG bandwidth is the LAG,
insufficient, you can set the port
create a LAG to that is
increase the configured
bandwidth. with
l To improve link services to
reliability, you can the main
bind the links into a port.
LAG. l This
operation
briefly
interrupts
the existing
services.
Changing The E-LAN service A.12.3.5 Changing Logical You need to

logical ports requirements change. Ports Connected to a VB add or delete a
connected to a As a result, the logical logical port
VB ports connected to the connected to a
VB need to be changed. VB, or modify
attributes
associated with
a logical port
connected to
the VB
according to the
actual planning
information.


Scenario
Managing the l To disable certain A.12.4 Managing the MAC -

MAC address MAC address hosts Address Table
table to use E-LAN
services, you need
to create MAC
address blacklist
entries.
l To prevent certain
MAC address
entries from being
aged, you need to
create static MAC
address entries.
l To disable the aging
function or modify
the default aging
time (five minutes),
you need to set the
aging parameters of
corresponding
MAC addresses.
Adjusting The service A.12.10 Managing the QoS Change the

QoS requirements change. values of QoS
As a result, QoS needs parameters to
to be adjusted. ensure that the
QoS control
adapts to the
changes in the
service
requirements.
9.5 Common Task Collection (EoPDH-Plane Ethernet

Services)
This section describes the common configuration tasks associated with EoPDH-plane Ethernet
services.

Table 9-5 Task Collection (EoPDH-plane Ethernet services)

Task Application Configuration Operation Remarks
Scenario
Creating Create the Ethernet 6 Configuring EoPDH-Based -

Ethernet services according to Ethernet Services
services the service planning
information.
Setting or The service A.13.4 Configuring Ethernet -

modifying the requirements or Ports
parameters of configuration at the
Ethernet ports opposite end change.
As a result, the
parameters of the
Ethernet port need to be
changed.
Deleting Delete the Ethernet A.13.2.7 Deleting an Ethernet -

Ethernet services that are not Private Line Service or A.
services used to release the 13.2.8 Deleting an Ethernet
corresponding LAN Service
resources.
Creating a l When the available A.13.1 Managing LAGs l When using

LAG bandwidth is the LAG,
insufficient, you can set the port
create a LAG to that is
increase the configured
bandwidth. with
l To improve link services to
reliability, you can the main
bind the links into a port.
LAG. l This
operation
briefly
interrupts
the existing
services.
Changing The Ethernet LAN A.13.2.3 Changing the Ports You need to
logical ports service requirements Connected to a VB add or delete
connected to a change. As a result, the the logical port
VB logical ports connected connected to a
to the VB need to be VB, or modify
changed. attributes
associated with
the logical port
connected to
the VB
according to the
actual planning
information.

Task Application Configuration Operation Remarks

Scenario
Managing the l To disable certain A.13.3 Managing the MAC -

MAC address MAC address hosts Address Table
table to use Ethernet LAN
services, you need
to create MAC
address blacklist
entries.
l To prevent certain
MAC address
entries from being
aged, you need to
create static MAC
address entries.
l To disable the aging
function or modify
the default aging
time (five minutes),
you need to set the
aging parameters of
corresponding
MAC addresses.
Adjusting The service A.13.7 Managing the QoS Change the

QoS requirements change. values of QoS
As a result, QoS needs parameters to
to be adjusted. ensure that the
QoS control
adapts to the
changes in the
service
requirements.

Configuration Guide (U2000) A Task Collection
A Task Collection
This topic describes various tasks involved in this document.

A.1 Managing NEs
Before you configure NEs, ensure that the NEs can be managed on the NMS.
A.2 Configuring the NE Data
If an NE is not configured after being created successfully, you need to configure the NE data
so that the NMS can manage this NE.
A.3 Configuring the Performance Monitoring Status of NEs
By default, the performance monitoring of NEs is enabled. You can disable or enable this
function manually and set the period of the performance monitoring of NEs manually.
A.4 Connecting Fibers or Cables
To implement the end-to-end management on the NMS, you need to connect fibers or cables.
A.5 Managing Subnets
To facilitate NE management, you can allocate the NEs that are in the same domain or have
similar attributes into the same subnet.
A.6 Managing Communications
To manage the NE by the NMS, ensure that the DCN communication is normal.
A.7 Configuring Service Access of NEs
You can ensure the security of a network by setting service access of the NEs on the network.
A.8 Managing Radio Links
Before you configure the radio link between two microwave sites, you need to configure the
corresponding information about the radio link.
A.9 Managing the MSP
The OptiX RTN 950 supports the linear MSP.
A.10 Managing TDM Services
The TDM services involve the SDH service and the PDH service.
A.11 Managing the Clock
To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.12 Configuring Ethernet Services and Features on the Packet Plane
Issue 01 (2010-09-25) Huawei Proprietary and Confidential A-1

A Task Collection Configuration Guide (U2000)
Configurations of Ethernet services and features on the packet plane include Ethernet port
configuration, protection configuration, service configuration, protocol configuration, and OAM
configuration.
A.13 Configuring Ethernet Services and Features on the EoPDH Plane
Configurations of Ethernet services and features on the EoPDH plane include relevant Ethernet
port configuration, protection configuration, service configuration, protocol configuration, and
OAM configuration.
A.14 Using the RMON
The remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment
or on the entire network. Currently, it is one of the widely used network management standards.
A.15 Setting the Parameters of ODU Ports
This section describes how to configure the parameters of ODU ports, including the transmit
frequency attribute, power attribute, ODU attribute, and advanced attributes.
A.16 Setting the Parameters of SDH Ports
The parameters of SDH ports are used to configure the loopback on the SDH interface bboard
and the laser status.
A.17 Setting the Parameters of PDH Ports
The parameters of PDH ports are used to configure the tributary loopback, service load
indication, and tributary retiming.
A.18 Configuring Overhead Bytes
Generally, the default overload bytes can meet the requirements of the device. In certain special
application scenarios, however, such as device interconnection, you need to change the overload
bytes according to the requirements of the interconnected device.
A.19 Configuring Auxiliary Ports and Functions
The auxiliary ports and functions supported by the OptiX RTN 950 include the orderwire,
synchronous data service, asynchronous data service, wayside E1 service, and external alarm.
A.20 Testing the Protection Switching
By testing the protection switching, you can check whether the protection switching is normal
over radio links.
A.21 Testing the AM Switching
By testing the AM switching, you can check whether the AM switching is normal over radio
links.
A-2 Huawei Proprietary and Confidential Issue 01 (2010-09-25)

A.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS.
A.1.1 Creating NEs by Using the Search Method

The U2000 can find all NEs that communicate with a specific gateway NE by using the IP address
of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition,
the U2000 can create the NEs that are found in batches. Compared with the method of manually
creating NEs, this method is faster and more reliable.
A.1.2 Creating NEs by Using the Manual Method
You can only create NEs one by one by using the manual method. The manual method, unlike
the search method, does not allow creating NEs in batches.
A.1.3 Configuring the Logical Board
If the logical board corresponding to the physical board is not added in the slot layout, add the
logical board in the slot layout. If the physical board is inconsistent with the logical board in the
slot layout, delete the inconsistent logical board and add the correct logical board.
A.1.4 Changing the NE ID
Modify the NE ID according to the engineering planning to guarantee that each NE ID is unique.
Modifying the NE ID does not interrupt services.
A.1.5 Changing the NE Name
To better identify the NE in the Main Topology, name the NE according to the NE geographical
location or the device connected to the NE.
A.1.6 Synchronizing the NE Time
By setting the NE time to be synchronous with the time on the NMS or standard NTP server,
you can record the exact time when alarms and abnormal events occur.
A.1.7 Localizing the NE Time
When the daylight saving time (DST) is used in the area where the NE is located, you need to
localize the NE time to synchronize the NE time with the local time.
A.1.8 Configuring Standard NTP Keys
When the NE time is synchronized with the time on the NTP server and the identity
authentication is required, you need to configure NTP keys.

The U2000 can find all NEs that communicate with a specific gateway NE by using the IP address
of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition,
the U2000 can create the NEs that are found in batches. Compared with the method of manually
creating NEs, this method is faster and more reliable.
Prerequisite
l The communication between the NMS and the NE must be normal.
l You must be an NM user with NE operator authority or higher.
Tools, Equipment, and Materials

U2000

Procedure
Step 1 Choose File > Discovery > NE from the Main Menu.
Step 2 Select Search Mode.
Step 3 Optional: If Search Mode is set to Search for NE, you need to add a search domain.
1. Click Add, and then the Input Search Domain dialog box is displayed.
2. Select an address type and enter the search address.
NOTE
l When Address Type is set to NSAP Address, ensure that the U2000 is installed with the OSI protocol
stack software.
l When Address Type is set to IP Address of GNE or IP Address Range of GNE, and the U2000
server and gateway NE are not in the same network segment, ensure that the IP routes of the network
segments to which the U2000 server and gateway NE belong are configured on the U2000 and related
routers.
3. Click OK.
Step 4 Optional: Repeat Step 3 to add several search domains.
Step 5 In Search for NE dialog box, to perform the operations described in the Note part.
NOTE
l If Create NE after search is selected, you need to specify NE User and Password.
l You can select either Create NE after search or Upload after Create or both Create NE after search and
Upload after Create. In this manner, after the NE searching is complete, the system automatically creates
an NE and uploads the NE.
Step 6 Click Next, and then the Transport NE Search dialog box is displayed.
After the search is complete, all the NEs that are found are displayed in the Result list.
Step 7 Create NEs.

1. Select an NE that is not created from the Result list.
2. Optional: Select the GNE ID of the NE.
3. Click Create.
The Create dialog box is displayed.
4. Specify User Name and Password.
5. Click OK.
The icon of the created NE is displayed in the Main Topology.
Step 8 Optional: Repeat Step 7 to create other NEs that are not created.

Step 9 Click Search.
----End
Related References
B.1.1 Parameter Description: NE Searching

You can only create NEs one by one by using the manual method. The manual method, unlike
the search method, does not allow creating NEs in batches.
Prerequisite
l The communication between the NMS and the NE to be created must be normal.
l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be created
belongs must be created.
Procedure
Step 1 In the Physical ViewPhysical Root, right-click New > NE.
The Create NE dialog box is displayed.
Step 2 Choose RTN Series > OptiX RTN 950 from the Object Tree.
Step 3 Enter the following information: ID, Extended ID, Name, and Remarks.
Step 4 Set Gateway Type for the NE.
If ... Then ...

The Gateway Type parameter is set to Proceed to the next step.
Gateway
The Gateway Type parameter is set to Non- Select the gateway to which the NE belongs,
Gateway and go to Step 6.
Step 5 Specify the protocol and IP address that the NE uses.
If ... Then ...

If the Protocol parameter is set to IP Enter the IP Address of the NE.
If the Protocol parameter is set to OSI Enter the NSAP Address of the NE.

Step 6 Specify NE User and Password.

The default user name is root and the default password is password.
Step 7 Click OK.
Step 8 Click the Main Topology.

The icon of the NE is displayed at the cursor position.
----End
Related References
B.1.2 Parameter Description: NE Creation
A.1.3 Configuring the Logical Board

If the logical board corresponding to the physical board is not added in the slot layout, add the
logical board in the slot layout. If the physical board is inconsistent with the logical board in the
slot layout, delete the inconsistent logical board and add the correct logical board.

Prerequisite
l All the boards must be installed correctly.

U2000
Procedure
Step 1 Double-click the NE icon to open the NE layout diagram.
Step 2 Optional: On the slot to which the board is to be added, right-click, and then select Add
XXX. XXX is the name of the board to be added.
Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then select Delete.
1. A dialog box is displayed for confirmation, click OK.
2. A dialog box is displayed again for confirmation, click OK.
NOTE
Before deleting the board, delete the data, such as the service, clock, orderwire, and protection, on the
board.
----End

Modify the NE ID according to the engineering planning to guarantee that each NE ID is unique.
Modifying the NE ID does not interrupt services.

Prerequisite
You must be an NM user with NE operator authority or higher.

U2000
Procedure
Step 1 In the Main Topology, right-click the NE whose ID needs to be modified.
Step 2 Choose Object Attributes.

The Attributes dialog box is displayed.
Step 3 Click the NE Attribute[xxx] tab.

NOTE
xxx indicates the current name of the NE.
Step 4 Click Modify NE ID.

The Modify NE ID dialog box is displayed.
Step 5 Specify New ID and New Extended ID.
Step 6 Click OK.

A dialog box is displayed for confirmation, click OK.
Step 7 Click OK.
----End
Related References
B.1.3 Parameter Description: Attribute_Changing NE IDs
A.1.5 Changing the NE Name

To better identify the NE in the Main Topology, name the NE according to the NE geographical
location or the device connected to the NE.
Prerequisite

U2000

Procedure
Step 1 In the Main Topology, select the NE whose name is to be modified, and then right-click.
Step 2 Select the Object Attributes, then, the Attributes dialog box is displayed.
Step 3 Click the NE Attribute [xxx] tab.

NOTE
xxx is the current name of the NE.
Step 4 Enter the name of the NE in Name.

NOTE
The name of an NE cannot contain any space or Chinese characters.
Step 5 Click OK, and then close the dialog box that is displayed indicating the operation result.
The new name of the NE is displayed below the NE icon in the Main Topology.
----End

By setting the NE time to be synchronous with the time on the NMS or standard NTP server,
you can record the exact time when alarms and abnormal events occur.
Prerequisite
l When you need to synchronize the NE time with the time on the NMS server, the time zone
and time must be set correctly on the PC or server that is installed with the NMS software.
l When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the NE Time Synchronization tab.
Step 3 In the physical view, select the NE whose time needs to be synchronized, and then click

Step 4 When you need to synchronize the NE time with the NMS time, set the time synchronization
mode and the related parameters.
1. Set Synchronous Mode to NM.
2. Optional: The NE time is synchronized with the NMS time immediately.
a. Right-click the NE whose time needs to be synchronized, and then choose
Synchronize with NM Time from the short-cut menu.
b. In the dialog box that is displayed for confirmation, click Yes.

c. Close the dialog box that is displayed indicating the operation result.
3. Click Apply.
4. Optional: Set auto synchronization parameters.
a. Set auto synchronization parameters.
b. Click Apply.
c. In the dialog box that is displayed for confirmation, click Yes.
d. Close the dialog box that is displayed indicating the operation result.
NOTE
l When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM.
l When you need to synchronize the NE time with the time on the NTP server, set Synchronous Mode to
Standard NTP. Configure Standard NTP Authentication according to the requirements of the NTP server.
Step 5 When you need to synchronize the NE time with the time on the NTP server, set the time
synchronization mode and the related parameters.
1. Set Synchronous Mode to Standard NTP.
2. Configure Standard NTP Authentication according to the requirements of the NTP
server.
3. Click Apply.
4. Click Close, and then close the dialog box that is displayed indicating the operation result.
5. Configure the upper-layer NTP server.
a. Select the NE, right-click in the configuration box where the standard NTP server is
configured, and then choose New.

b. Configure the parameters related to the NTP server.
c. Click Apply.
6. Optional: Copy the configuration of the upper-layer NTP server.
a. Select the NE to be copied, right-click, and then choose Copy Standard NTP
Server.
b. Select the NE to be pasted, right-click, and then choose Paste Standard NTP
Server.
c. In the dialog box that is displayed for confirmation, click Yes.
----End
Related References
B.1.4 Parameter Description: NE Time Synchronization


When the daylight saving time (DST) is used in the area where the NE is located, you need to
localize the NE time to synchronize the NE time with the local time.
Prerequisite

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the Main Menu.
Step 2 Select the NE for time localization management from the Object Tree, and then click
Step 3 Click the Time Zone drop-down list, and then set the time zone of the NE.
Step 4 Optional: Click DST, and then configure the related parameters.
Step 5 Click Apply, and then close the dialog box that is displayed.
----End
Related References
B.1.5 Parameter Description: Localization Management of the NE Time

When the NE time is synchronized with the time on the NTP server and the identity
authentication is required, you need to configure NTP keys.
Prerequisite
l Set Synchronous Mode used by the NE to Standard NTP and Standard NTP
Authentication to Enabled.
l The NTP protocol is normal and the NTP identity authentication is enabled on the NTP
server.

U2000

Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the Standard NTP Key Management tab.
Step 3 In the physical view, select the NE whose NTP keys need to be configured, and then click
.
Step 4 Click Add.
The Add Key and Password dialog box is displayed.
Step 5 After the related parameters are configured, click OK.
----End
Related References
B.1.6 Parameter Description: Standard NTP Key Management
A.2 Configuring the NE Data

If an NE is not configured after being created successfully, you need to configure the NE data
so that the NMS can manage this NE.
A.2.1 Uploading the NE Data

Uploading the NE data is commonly used for configuring the NE data. By uploading the NE
data, the data such as the configuration, alarm, and performance data of the NE is uploaded to
the NMS.
A.2.1 Uploading the NE Data

Uploading the NE data is commonly used for configuring the NE data. By uploading the NE
data, the data such as the configuration, alarm, and performance data of the NE is uploaded to
the NMS.
Prerequisite
l An NE must be logged in to successfully.

U2000
Procedure
Step 1 Select the corresponding operation steps according to the status of the NE.
If ... Then ...

An NE is not configured and the NE data In the Main Topology, double-click the NE
needs to be uploaded. that is not configured, and then refer to Step
2-Step 4.
An NE is configured with data and NE data Refer to Step 5-Step 8.
needs to be uploaded.
Step 2 In the displayed NE Configuration Wizard dialog box, select Upload, and then click Next.
A dialog box is displayed for confirmation.
Step 3 Click OK.
Step 4 Click Close.
Step 5 Choose Configuration > NE Configuration Data Management from the Main Menu.
Step 6 Select the NE whose data needs to be uploaded from the Object Tree, and then click .
Step 7 Select the NE, click Upload, a dialog box is displayed for confirmation, and then click OK.
The uploading is started. After the uploading is complete, the Operation Result dialog box is
displayed.
Step 8 Click Close.
----End
A.3 Configuring the Performance Monitoring Status of NEs

By default, the performance monitoring of NEs is enabled. You can disable or enable this
function manually and set the period of the performance monitoring of NEs manually.

Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE
Performance Monitoring Time from the Function Tree.
Step 2 Configure the parameters of the performance monitoring of NEs.
1. Select 15-Minute or 24-Hour.
2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
NOTE
l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
l You can specify the start time of the performance monitoring function, only after selecting Enable in
the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
l You can specify the end time of the performance monitoring function, only after selecting Enable and
then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
4. Click Apply, and then close the dialog box that is displayed.
----End
A.4 Connecting Fibers or Cables

To implement the end-to-end management on the NMS, you need to connect fibers or cables.
A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method
Through the search method, the NMS can check the information about the radio link that is
connected to a specified IF port. In this manner, a radio link can be created rapidly. The search
method is commonly used for creating a radio link.

A.4.2 Creating a Radio Link by Using the Manual Method

After you manually fill in the table, the NMS can create a radio link according to the configured
link information. This method is used when the actual radio link is not formed.
A.4.3 Creating an SDH Optical Transmission Link by Using the Manual Method
link information.
A.4.4 Creating an Extended ECC
An NE can communicate with the NMS through the Ethernet port or serial port. In addition, the
NEs can communicate with each other through the extended embedded control channel (ECC).
You can create different communication cables on the NMS according to different
communication modes.
A.4.5 Creating a Back-to-Back Radio Connection
The back-to-back radio connection refers to the NE cascading relation.
A.4.1 Creating an Optical Transmission Line or Radio Link by

Using the Search Method
Through the search method, the NMS can check the information about the radio link that is
connected to a specified IF port. In this manner, a radio link can be created rapidly. The search
method is commonly used for creating a radio link.
Prerequisite
l The IF boards of various NEs must be created on the NMS.

U2000
Procedure
Step 1 Choose File > Discovery > Fiber from the Main Menu.
Step 2 Select the board of the NE on which the fiber needs to be searched for or the IF board of the NE
on which radio links need to be searched for from the Subject Tree.
Step 3 Click Search.
NOTE
l If Do not search the ports with Fiber/Cable created on NMS is selected, the port whose radio link
is created is not searched on the NMS.
l If you need to check whether the connection of a created radio link is the same as the actual connection
of the radio link, do not select Do not search the ports with Fiber/Cable created on NMS.
l If Do not search the ports with Fiber/Cable created on NMS is selected and all the selected ports
are created with radio links, a dialog box is displayed after the search, indicating that the search domain
is null.
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Then, click Close.
Step 5 In Physical Fiber/Cable Link List, select one or multiple optical transmission lines or radio
links, and then click Create Fiber/Cable.

NOTE
l When you select one or multiple optical transmission lines or radio links from Physical Fiber/Cable
Link List, the conflicting optical transmission lines or radio links are automatically displayed in
Logical Fiber/Cable Link List. In this manner, you need to delete such conflicting optical transmission
lines or radio links by referring to Step 5, and then create the links.
l When you create an optical transmission line or radio link, if the selected optical transmission line or
radio link is in the Already created state, No fiber to create is displayed.
Step 6 When you select one or multiple conflicting optical transmission lines or radio links from
Logical Fiber/Cable Link List, click Delete Fiber/Cable.
----End
Subsequent Handling
If the information about the optical transmission line or radio link that is created through the
search method, you can supplement the information by changing the information about the
optical transmission line or cable.
Related References
B.2.1 Parameter Description: Fiber Search

link information. This method is used when the actual radio link is not formed.
Prerequisite
l The IF boards of various NEs must be created on the NMS.

U2000
Procedure
Step 1 Choose File > Create > Link from the Main Menu. The Create Link dialog box is displayed.
Step 2 Choose Fiber/Cable > Microwave Link from the Object Tree.
Step 3 Configure the attributes of the created radio link according to the data plan.

Step 4 Click OK.

In the Main Topology, the created radio link is displayed between the source NE and the sink
NE.
----End
Related References
B.2.3 Parameter Description: Radio Link Creation
A.4.3 Creating an SDH Optical Transmission Link by Using the

Manual Method
link information.
Prerequisite
l The board to be connected with the optical transmission line or cable must be created.

U2000
Procedure

Step 2 Choose Fiber/Cable > Fiber from the Object Tree.
Step 3 Configure the attributes of the created SDH optical transmission link according to the data plan.
Step 4 Click OK.

In the Main Topology, the created SDH optical transmission link is displayed between the source
NE and the sink NE.
----End
Related References
B.2.2 Parameter Description: Fiber Creation
A.4.4 Creating an Extended ECC

An NE can communicate with the NMS through the Ethernet port or serial port. In addition, the
NEs can communicate with each other through the extended embedded control channel (ECC).
You can create different communication cables on the NMS according to different
communication modes.
Prerequisite

U2000

Procedure
Step 2 Choose Link > Extended ECC.
Step 3 Configure the attributes of the created extended ECC according to the data plan.
Step 4 Click OK.

In the Main Topology, the created extended ECC is displayed between the source NE and the
sink NE.
----End
A.4.5 Creating a Back-to-Back Radio Connection

The back-to-back radio connection refers to the NE cascading relation.
Prerequisite
l The corresponding IF board must be added on the NE Panel.

U2000
Procedure
Step 1 In the Main Topology, choose File > Create > Link.
The Create Link dialog box is displayed.
Step 2 Select Fiber/Cable > Microwave Back To Back.
Step 3 Select the source NE from the drop-down list of Source NE.
Step 4 Select the sink NE from the drop-down list of Sink NE.
Step 5 Configure the attributes of the back-to-back radio connection.

Step 6 Click OK.

The created back-to-back radio connection is displayed in the Main Topology.
----End
A.5 Managing Subnets

To facilitate NE management, you can allocate the NEs that are in the same domain or have
similar attributes into the same subnet.
A.5.1 Creating a Subnet

In the Main Topology, you can create a subnet object and allocate an NE to this subnet.
A.5.2 Copying Topology Objects
In the current topology, you can copy topology objects from one subnet to another subnet.
A.5.3 Moving Topology Objects
In the current topology, you can move topology objects from one subnet to another subnet.
A.5.1 Creating a Subnet

In the Main Topology, you can create a subnet object and allocate an NE to this subnet.
Prerequisite

U2000
Procedure
Step 1 In the Main Topology, right-click, and then choose New > Subnet.
The Create Physical Subnet dialog box is displayed.
Step 2 Click the Property tab.
Step 3 Enter the attributes of the subnet.
Step 4 Click the Select Object tab, select a created NE from Available Objects, and then click
to add the NE to Selected Objects.

NOTE
l Click to add the selected object in the left pane to the right pane.
l Click to add all the objects in the left pane to the right pane.
Step 5 Click OK.

Step 6 In the Main Topology, click in a blank area, and then the created subnet is displayed in the
position where you click.
----End
A.5.2 Copying Topology Objects

In the current topology, you can copy topology objects from one subnet to another subnet.
Prerequisite

U2000
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be copied.
Step 2 Choose Edit > Copy to.
The Select a Parent Subnet dialog box is displayed.
Step 3 Select the subnet that the NE or subnet needs to be pasted.
Step 4 Click OK.
----End
A.5.3 Moving Topology Objects

In the current topology, you can move topology objects from one subnet to another subnet.
Prerequisite

U2000
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be moved.
Step 2 Choose Edit > Move to.

The Select a Parent Subnet dialog box is displayed.
Step 3 Select the subnet that the NE or subnet needs to be moved to.
Step 4 Click OK.
----End
A.6 Managing Communications

To manage the NE by the NMS, ensure that the DCN communication is normal.
A.6.1 Setting NE Communication Parameters

The communication parameters of an NE include the IP address of the NE, the gateway IP
address, and the subnet mask.
A.6.2 Configuring DCCs
To meet the requirements for managing a complex network, you need to set the channel type,
protocol type, or enable status of the DCCs according to the network planning information.
A.6.3 Configuring the Extended ECC
When there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading
ports on the system control unit of the NEs to realize communication through the extended ECC.
A.6.4 Configuring DCC Transparent Transmission
The OptiX equipment supports the DCC transparent transmission function. With this function,
the equipment can transparently transmit NM messages when the OptiX equipment is used
together with other equipment to form a network and can also transparently transmit the NM
messages between ECC subnets.
A.6.5 Creating Static IP Routes
When dynamic routes fail to meet the planning requirements, you need to create the
corresponding static IP routes manually.
A.6.6 Setting Parameters of the OSPF Protocol
When the IP over DCC solution is used to realize the interconnection between the OptiX
equipment and the third-party equipment, you need to set the parameters of the OSPF protocol
according to the requirements of the third-party equipment, thus implementing the route protocol
interworking between the OptiX equipment and the third-party equipment.
A.6.7 Enabling the ARP Proxy
The proxy ARP enables the NEs in the same network segment but different domains to
communicate with each other.
A.6.8 Configuring the CLNS Role
When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the
CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS
role of the OptiX RTN 950 is L1.
A.6.9 Configuring the OSI Tunnel
The OSI tunnel function involves the creation of a virtual LAPD channel between the NEs on
the IP network. In this manner, the NM message encapsulated in compliance with the OSI
protocol can be transparently transmitted.
A.6.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN

The VLAN ID used by an inband DCN must be different from the VLAN ID used by services
and the bandwidth by an inband DCN must meet the requirements of the transmission network
for managing messages.
A.6.11 Configuring the Enable Status of the Inband DCN Function on Ports
The network management information can be transmitted over a link by the inband DCN only
when the inband DCN function is enabled on the ports at both ends of the link.
A.6.12 Configuring the Protocol Type of the Inband DCN
The inband DCN supports two types of protocol: IP and HWECC. The IP is the default protocol
supported by the inband DCN. Generally, it is recommended that you use the default value.
A.6.13 Querying ECC Routes
By querying ECC routes, you can check whether the correct HWECC solution is configured and
whether the communication between NEs is normal.
A.6.14 Querying IP Routes
By querying IP routes, you can check whether the IP over DCC solution and inband DCN
solution is configured correctly and whether the communication between NEs is normal.
A.6.15 Querying OSI Routes
By querying OSI routes, you can check whether the OSI over DCC solution is configured
correctly and whether the communication between NEs is normal.
A.6.16 Configuring Access Control
When the equipment is connected to the NMS through an Ethernet service port, you need to
configure access control.

The communication parameters of an NE include the IP address of the NE, the gateway IP
address, and the subnet mask.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.
Step 2 Configure the communication parameters of the NE.
NOTE
When you configure multiple parameters, click Apply respectively.

----End
Related References
B.3.1 Parameter Description: NE Communication Parameter Setting

To meet the requirements for managing a complex network, you need to set the channel type,
protocol type, or enable status of the DCCs according to the network planning information.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Management from the Function Tree.
Step 2 Click the DCC Rate Configuration tab.
Step 3 Optional: Change the enable status of the DCC.

1. Double-click the cell in the Enabled/Disabled column to which the DCC corresponds.
Select the required state from the drop-down list.
2. Click Apply.
Step 4 Optional: Change the protocol type of the DCC.

1. Double-click the cell in the Protocol Type column to which the DCC corresponds. Select
the required protocol type from the drop-down list.
2. Click Apply.
NOTE
In this figure, 7-CSH-1 corresponds to the external clock interface on the CSH board in slot 7.
Step 5 Optional: Create DCCs.

1. Click Create.
Then, the Create dialog box is displayed.
2. Set the attributes of the DCC.
3. Click OK.
----End
Related References
B.3.2 Parameter Description: DCC Management_DCC Rate Configuration

When there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading
ports on the system control unit of the NEs to realize communication through the extended ECC.
Prerequisite

U2000
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
Step 2 Set the ECC Extended Mode.

Step 3 Set other parameters when the ECC extended mode is set to the specified mode.
Step 4 Click Apply. A dialog box is displayed indicating that this operation will reset the
communication between NEs.
Step 5 Click OK.
----End
Related References
B.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECC

The OptiX equipment supports the DCC transparent transmission function. With this function,
the equipment can transparently transmit NM messages when the OptiX equipment is used
together with other equipment to form a network and can also transparently transmit the NM
messages between ECC subnets.
Prerequisite
The DCC bytes required by the transparent transmission function must not be used.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Step 2 Click the DCC Transparent Transmission Management tab.
Step 3 Click Create.

Then, the Create DCC Transparent Transmission Byte dialog box is displayed.
Step 4 Set the parameters of the DCC transparent transmission byte.

Step 5 Click OK.
----End
Related References
B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management

When dynamic routes fail to meet the planning requirements, you need to create the
corresponding static IP routes manually.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol
Stack Management from the Function Tree.
Step 2 Click the IP Route Management tab.
Step 3 Click New.

Then, the Create an IP Route dialog box is displayed.
Step 4 Set the parameters of the static IP route.
NOTE
The created static route has a lower priority than a dynamic route.
Step 5 Click OK.
----End

Related References
B.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation

When the IP over DCC solution is used to realize the interconnection between the OptiX
equipment and the third-party equipment, you need to set the parameters of the OSPF protocol
according to the requirements of the third-party equipment, thus implementing the route protocol
interworking between the OptiX equipment and the third-party equipment.
Prerequisite

U2000
Procedure
Step 2 Click the OSPF Parameter Settings tab.
Step 3 Set the parameters of the OSPF protocol.
Step 4 Click Apply.
----End
Related References
B.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings


The proxy ARP enables the NEs in the same network segment but different domains to
communicate with each other.
Prerequisite
Procedure
Step 2 Click the Proxy ARP tab.
Step 3 Set the enable status of the proxy ARP.
Step 4 Click Apply.
----End
Related References
B.3.9 Parameter Description: IP Protocol Stack_Proxy ARP

When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the
CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS
role of the OptiX RTN 950 is L1.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Step 2 Click the Network Layer Parameters tab.
Step 3 Set the CLNS role of the NE.
NOTE
When Configuration Role is set to L2, the NE has the functions of the L1 role and the L2 role.
Step 4 Click Apply.

The system displays the prompt.

Step 5 Click Yes.
----End
Related References
B.3.10 Parameter Description: OSI Management_Network Layer Parameter

The OSI tunnel function involves the creation of a virtual LAPD channel between the NEs on
the IP network. In this manner, the NM message encapsulated in compliance with the OSI
protocol can be transparently transmitted.
Prerequisite

U2000
Procedure
Step 2 Click the OSI Tunnel tab.
Step 3 Click New.
Then, the Create OSI Tunnel dialog box is displayed.
Step 4 Set Remote IP Address and LAPD Actor.
Step 5 Click OK.

Step 6 Configure the attributes of the OSI tunnel according to the network planning.

Step 7 Click Apply.
----End
Related References
B.3.12 Parameter Description: OSI Management_OSI Tunnel
A.6.10 Configuring the VLAN ID and Bandwidth Used by an

Inband DCN
The VLAN ID used by an inband DCN must be different from the VLAN ID used by services
and the bandwidth by an inband DCN must meet the requirements of the transmission network
for managing messages.
Prerequisite
You must be an NM user with NE administrator authority or higher.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Step 2 Click the Bandwidth Management tab.
Step 3 Set the VLAN ID and bandwidth used by an inband DCN.
Step 4 Click Apply.
----End
Related References
B.3.13 Parameter Description: DCN Management_Bandwidth Management

A.6.11 Configuring the Enable Status of the Inband DCN Function

on Ports
The network management information can be transmitted over a link by the inband DCN only
when the inband DCN function is enabled on the ports at both ends of the link.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Step 2 Click the Port Settings tab.
Step 3 Select FE/GE.
Step 4 Configure the enable status of the inband DCN function on ports.
Step 5 Click Apply.
Step 6 Select IF.
Step 7 Configure the enable status of the inband DCN function on ports.
Step 8 Click Apply.
----End
Related References
B.3.14 Parameter Description: DCN Management_Port Setting


The inband DCN supports two types of protocol: IP and HWECC. The IP is the default protocol
supported by the inband DCN. Generally, it is recommended that you use the default value.
Prerequisite
l The corresponding board must be added to the NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose
Communication > DCN Management from the Function Tree.
Step 2 Click the Protocol Settings tab.
Step 3 Set the protocol type of the inband DCN.
Step 4 Click Apply.
----End
Related References
B.3.15 Parameter Description: DCN Management_Protocol Setting

By querying ECC routes, you can check whether the correct HWECC solution is configured and
whether the communication between NEs is normal.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.

Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link
Management List.
----End
Related References
B.3.5 Parameter Description: NE ECC Link Management

By querying IP routes, you can check whether the IP over DCC solution and inband DCN
solution is configured correctly and whether the communication between NEs is normal.
Prerequisite

U2000
Procedure
Step 2 Click the IP Route Management tab.
Step 3 Click Query. Then, close the dialog box that is displayed.
Step 4 Check whether the IP routes and related parameters in the routing table are in accordance with
the planning information.
----End
Related References
B.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management

By querying OSI routes, you can check whether the OSI over DCC solution is configured
correctly and whether the communication between NEs is normal.
Prerequisite

U2000

Procedure
Step 2 Click the Routing Table tab.
Step 3 Check whether the information in Link Adjacency Table meets the planning requirements.
Step 4 Click the L1 Routing tab to check whether the information about the L1 routes is correct.
Step 5 Click the L2 Routing tab to check whether the information about the L2 routes is correct.
----End
Related References
B.3.11 Parameter Description: OSI Management_Routing Table

When the equipment is connected to the NMS through an Ethernet service port, you need to
configure access control.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
DCN Management from the Function Tree.
Step 2 Click the Access Control tab.
Step 3 Set the parameters for configuring access control.
Step 4 Click Apply.
----End
Related References
B.3.16 Parameter Description: DCN Management_Access Control

A.7 Configuring Service Access of NEs

You can ensure the security of a network by setting service access of the NEs on the network.
A.7.1 Configuring LCT Access to NEs

When an NE is managed by the NMS, the LCT cannot access this NE by default.
A.7.2 Configuring Ethernet Access to NEs
By default, the NMS can access an NE by using Ethernet ports.
A.7.3 Configuring Serial Interface Access to NEs
By default, the NMS can access an NE through serial interfaces.
A.7.1 Configuring LCT Access to NEs

When an NE is managed by the NMS, the LCT cannot access this NE by default.
Prerequisite

U2000
Context
l If the LCT requests to log in to an NE to which the NMS has logged in, the NE determines
whether to permit the login of the LCT according to the status of LCT Access Control
Switch.
l If the LCT requests to log in to an NE to which the NMS has not logged in, the NE permits
the login of the LCT regardless of the status of LCT Access Control Switch. The NMS,
however, can log in to an NE to which the LCT has logged in. That is, the login of the LCT
does not affect the login of the NMS. After the NMS user logs in to the NE successfully,
the logged LCT user is not affected. If LCT Access Control Switch is set to Disable
Access, the logged LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT Access
Control from the Function Tree.
Step 2 Click Access Allowed to enable the LCT access function.

NOTE
To disable the LCT access function, click Disable Access.
----End

A.7.2 Configuring Ethernet Access to NEs

By default, the NMS can access an NE by using Ethernet ports.
Prerequisite

U2000
Background Information
l It is recommended that the LCT accesses an NE through Ethernet ports.
l If you need to initialize an NE or perform software loading by using the LCT, the LCT
needs to access the NE through Ethernet ports.
Procedure
Access Control from the Function Tree.
Step 2 Set the status of the network port to Enabled and enable the Ethernet access function of the NE.
NOTE
To disable the Ethernet access function of an NE, set the status of the network port to Disabled.
Step 3 Click Apply.

Then, a confirmation dialog box is displayed.
Step 4 Click OK. Then, close the operation result dialog box that is displayed.
----End
A.7.3 Configuring Serial Interface Access to NEs

By default, the NMS can access an NE through serial interfaces.
Prerequisite

U2000

Context
If the LCT cannot access an NE through serial interfaces when the Enable Serial Port Access
check box is selected, the LCT access function may be disabled.
Procedure
Access Control from the Function Tree.
Step 2 Select the Enable Serial Port Access check box and select Access NM.
Step 3 Click Apply. and then close the displayed prompt dialog box.
Step 4 Optional: Select the baud rate of the serial interface from the Baud Rate drop-down list. Click
Apply, and then close the displayed prompt dialog box.
----End
A.8 Managing Radio Links

Before you configure the radio link between two microwave sites, you need to configure the
corresponding information about the radio link.
A.8.1 Creating an IF 1+1 Protection Group
If the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1
+1 protection group.
A.8.2 Creating an XPIC Protection Group
If you configure two XPIC radio links after binding the two radio links as an XPIC workgroup,
the parameter settings including the channel bandwidth, transmit frequency, transmit power, and
ATPC attribute are ensured to be the same for the two radio links.
A.8.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link
After the XPIC protection group is created, you need to configure the Hybrid/AM attributes of
the XPIC Hybrid radio link according to the planned values.
A.8.4 Configuring the IF/ODU Information of a Radio Link
By performing this operation, you can configure the IF/ODU information for a radio link.
A.8.5 Setting IF Attributes
In the case of different IF boards, different parameters need to be set.
A.8.6 Configuring the ATPC Attributes

To configure the ATPC function, set the ATPC attributes of the IF board.
A.8.7 Setting the Hybrid/AM Attributes
By configuring the Hybrid/AM attributes, you can set the working mode of the Hybrid IF boards.
A.8.8 Setting Advanced AM Attributes
By performing this operation, you can query and adjust the E1 capacity in each modulation
scheme.
A.8.9 Modifying the Priorities of E1 Services
This section describes how to adjust the priorities of E1 services.
A.8.10 Creating an N+1 Protection Group
When multiple STM-1 or Hybrid microwave services are transmitted in the point-to-point mode,
you can adopt the N+1 protection configuration.
A.8.11 Querying the ATPC Adjustment Records
By querying the ATPC adjustment records, you can be familiar with the running status of the
ATPC function.
A.8.12 Querying the History Transmit Power and Receive Power
Querying the change trend of the history transmit power and receive power can provide reference
for radio link troubleshooting.
A.8.13 Querying the AM Status
By querying the AM status, you can trace the change of the modulation mode when the AM
function is used.
A.8.14 Querying the IF 1+1 Protection Status
You can learn about the current information of the IF 1+1 protection by querying the IF 1+1
protection status.
A.8.15 Querying the IF N+1 Protection Status
You can learn about the current information of the IF N+1 protection by querying the IF N+1
protection status.
A.8.16 IF 1+1 Protection Switching
You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection
switching.
A.8.17 IF N+1 Protection Switching
You can perform external switching on the IF N+1 protection by performing IF N+1 protection
switching.
A.8.18 Starting/Stopping the N+1 Protection Protocol
If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be
restored to the initial state.

If the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1
+1 protection group.
Prerequisite

l The IF boards and the ODUs to which the IF boards are connected must be added on the
NE Panel.
l The IF boards of an IF 1+1 FD/SD protection group must be configured in two paired slots.

U2000
When a 1+0 service is converted into a 1+1 HSB protection through the configuration of the IF
1+1 protection group, the original service is not interrupted. The board where the original service
exists, however, needs to be set to the working board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.

The Create IF 1+1 Protection dialog box is displayed.
Step 3 Configure the parameters of the IF 1+1 protection group.
----End
Related References
B.4.5 Parameter: IF 1+1 Protection_Create

If you configure two XPIC radio links after binding the two radio links as an XPIC workgroup,
the parameter settings including the channel bandwidth, transmit frequency, transmit power, and
ATPC attribute are ensured to be the same for the two radio links.
Prerequisite
l The IFX2 boards and the ODUs to which the IFX2 boards are connected must be added on
the NE Panel.


U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Configuration from the Function Tree.
Step 2 Click the XPIC tab.
Step 3 Click New.
The Create XPIC Protection Group dialog box is displayed.
Step 4 Configure the parameters for the XPIC protection group.
Step 5 Click OK.
----End
Related References
B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
A.8.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio

Link
After the XPIC protection group is created, you need to configure the Hybrid/AM attributes of
the XPIC Hybrid radio link according to the planned values.
Prerequisite

l The XPIC protection group must be created.

U2000
The IFX2 board (XPIC IF board) supports Hybrid radio. Therefore, the Hybrid/AM attributes
can be set for the IFX2 board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Step 2 Click the XPIC tab.
Step 3 Click the Hybrid/AM Configuration tab.
Step 4 Configure the Hybrid/AM attributes of the XPIC Hybrid radio link.
Step 5 Click Apply.
----End
Related References
B.4.2 Parameter Description: Link Configuration_XPIC

By performing this operation, you can configure the IF/ODU information for a radio link.
Prerequisite
NE Panel.

U2000

Precautions
l In the case of 1+1 HSB/SD protection, you need to configure only the IF/ODU information
of the main radio link.
l In the case of 1+1 FD protection, you need to configure the IF/ODU information of the
main radio link and the ODU information of the standby radio link.
l In the case of XPIC configuration, you need to configure the IF/ODU information of the
two radio links in different polarization directions separately.
l In the case of N+1 protection, you need to configure the IF/ODU information of the N+1
radio links respectively.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
Step 2 Click the IF/ODU Configuration tab.
Step 3 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 or
ODU to which the IF board is connected belongs.
Step 4 Configure the corresponding IF information of the radio link.

Step 5 Click Apply.
Step 6 Configure the corresponding ODU information of the radio link.
Step 7 Click Apply.
----End
Related References
B.4.7 Parameter: Link Configuration_IF/ODU Configuration

In the case of different IF boards, different parameters need to be set.

Prerequisite

U2000
Context
l The IF1 board is used for TDM microwave.
l The IFU2 board is used for Hybrid.
l The IFX2 board is used for XPIC Hybrid.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > IF Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
Step 3 Configure the parameters of IF attributes.

l In the case of the IF1:
l In the case of the IFU2:
l In the case of the IFX2:
Step 4 Click Apply.
----End
Related References
B.12.1 Parameter Description: IF Interface_IF Attribute

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisite

Precautions
l For the IF boards that are configured with 1+1 protection, configure 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 configure ATPC parameters in the
following configuration dialog boxes:
Create an XPIC working group

U2000
Procedure
Step 2 Click the ATPC Attributes tab.
Step 3 Configure the parameters of ATPC attributes.
Step 4 Click Apply.
----End
Related References
B.12.2 Parameter Description: IF Interface_ATPC Attribute

By configuring the Hybrid/AM attributes, you can set the working mode of the Hybrid IF boards.
Prerequisite

U2000
The OptiX RTN 950 supports the Hybrid/AM function and the corresponding IF boards are
IFU2 and IFX2.

Procedure
Step 1 In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose
Configuration > Hybrid/AM Configuration from the Function Tree.
Step 3 Configure the parameters of the Hybrid/AM attribute.
Step 4 Click Apply.
----End
Related References
B.12.3 Parameter Description: Hybrid/AM Configuration

By performing this operation, you can query and adjust the E1 capacity in each modulation
scheme.
Prerequisite
l The corresponding IF boards must be added in the NE Panel.
l The E1 priority function must be enabled.

U2000
The OptiX RTN 950 allows the E1 priority function to be configured for the IFU2 and IFX2
boards.
Procedure
Step 1 In the NE Explorer, select the Hybrid IF board, and then choose Configuration > Hybrid/AM
Step 2 Click the Advanced Attributes tab.
Step 3 Set each parameter for the advanced AM attributes.

Step 4 Click Apply.
----End
Related References
B.12.4 Parameter Description: Hybrid_AM Configuration_Advanced Attributes
A.8.9 Modifying the Priorities of E1 Services

This section describes how to adjust the priorities of E1 services.
Prerequisite
l The corresponding source and sink boards must be added in the NE Panel.
l The E1 cross-connections must be created. The IF boards in the cross-connections must
support the E1 priority function. The E1 priorities must be set already and need to be
modified.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service
Step 2 Select an E1 service in Cross-Connection Configuration.
Step 3 Right-click the E1 service and choose Expand from the shortcut menu.
Step 4 Double-click E1 Priority and select the target E1 priority from the drop-down list.
NOTE
For an SNCP service, you need to modify E1 Priority of only the services that are transmitted to the
working source and the protection source of the SNCP service.

Step 5 Click Apply. Then, close the dialog box that is displayed.
----End

When multiple STM-1 or Hybrid microwave services are transmitted in the point-to-point mode,
you can adopt the N+1 protection configuration.
Prerequisite
NE Panel.
l The IF1 boards must work in the STM-1 mode.

U2000
l When an N+0 service is converted into an N+1 service through the configuration of the N
+1 protection group, the original service is not interrupted.
l In the case of Hybrid radio links, the Hybrid/AM attributes must be the same for all the N
+1 radio links in the N+1 protection group.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
The Create N+1 Protection dialog box is displayed.
Step 3 Configure the Attribute of the N+1 protection group.

Step 4 Configure the mapping relation between the board and the slot.
1. Select Work Unit from Select Mapping Direction.
2. Select a port to which a working channel corresponds from Select Mapping Way, and then
click .
3. Repeat Step 4.2 to select the ports to which other working channels correspond. Click
.
4. Select Protection Unit from Select Mapping Direction.
5. Select a port to which a protection channel corresponds from Select Mapping Way, and
then click .
Step 5 Click OK. Click OK to close the confirmation dialog box that is displayed. Then, click OK to
close the dialog box that is displayed, indicating that the operation is successful.
----End
Related References
B.4.3 Parameter Description: N+1 Protection_Create

By querying the ATPC adjustment records, you can be familiar with the running status of the
ATPC function.
Prerequisite
l The corresponding IF board must be added.

U2000
Procedure
Configuration > ATPC Adjustment Records from the Function Tree.
Step 2 Click Query to query the running information of the ATPC function.
----End
Related References
B.12.5 Parameter Description: ATPC Adjustment Records
A.8.12 Querying the History Transmit Power and Receive Power

Querying the change trend of the history transmit power and receive power can provide reference
for radio link troubleshooting.

Prerequisite
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.

U2000
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration >
Performance Graph Analyse from the Function Tree.
Step 2 Specify the start time and end time of a specific time span.
NOTE
The time span starts from the last routine maintenance time to the current time.
Step 3 Set Monitoring Period and Power.

Step 4 Click Draw. The history transmit and receive power curve of the ODU in the specified time
span is displayed.
----End

By querying the AM status, you can trace the change of the modulation mode when the AM
function is used.
Prerequisite
l The corresponding IF boards must be added in the NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose
Step 3 Click Query.
Step 4 Query the AM status.
----End
Related References


You can learn about the current information of the IF 1+1 protection by querying the IF 1+1
protection status.
Prerequisite
l You must be an NM user with NE administrator authority or higher.
l The IF 1+1 protection must be configured.

U2000
Procedure
Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check the
IF 1+1 protection groups.
Step 3 Select the IF 1+1 protection group whose protection status needs to be queried.
Step 4 Click Query Switch Status, and then close the displayed prompt dialog box. In Slot Mapping
Relation, check the protection status of the IF 1+1 protection group.
----End
Related References
B.4.6 Parameter Description: IF 1+1 Protection

You can learn about the current information of the IF N+1 protection by querying the IF N+1
protection status.
Prerequisite
l The IF N+1 protection must be configured.

U2000
Procedure
Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check the
IF N+1 protection groups.

Step 3 Select the protection group whose protection status needs to be queried.
Step 4 Click Query Switch Status, and then close the displayed dialog box. In Slot Mapping
Relation, check the IF N+1 protection status.
----End
Related References
B.4.4 Parameter Description: N+1 Protection
A.8.16 IF 1+1 Protection Switching

You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection
switching.
Prerequisite
l The IF 1+1 protection must be configured.

U2000
Procedure
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 4 Choose the required switching mode from the shortcut menu,.
Step 5 In the dialog box that is displayed, click OK.

The system displays the dialog box that indicates the successful operation.
Step 6 Click Close.
Step 7 Click Query Switching Status and check whether the switching is successful.
----End
A.8.17 IF N+1 Protection Switching

You can perform external switching on the IF N+1 protection by performing IF N+1 protection
switching.
Prerequisite


U2000
Procedure
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 4 Choose the required switching mode from the shortcut menu.
Step 5 In the dialog box that is displayed, click OK.
The system displays the dialog box that indicates the successful operation.
Step 6 Click Close.
Step 7 Click Query Switch Status to check whether the switching operation is successful.
----End
A.8.18 Starting/Stopping the N+1 Protection Protocol

If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be
restored to the initial state.
Prerequisite

U2000
Precautions
l Stopping the N+1 protection protocol causes a failure of the N+1 protection.
l When services are switched onto the protection channel, stopping the N+1 protection
protocol causes switchover of the services back to the working tunnel. At this time, if the
working channel is normal, the services are transiently interrupted. If the working channel
is faulty, the services are interrupted until the working channel is restored to normal or the
N+1 protection protocol is started.
Procedure
Step 2 In Protection Group, select the protection group whose N+1 protection protocol needs to be
started.

Step 3 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box.
Step 4 Click Query to check the protocol status.
----End
A.9 Managing the MSP

The OptiX RTN 950 supports the linear MSP.
A.9.1 Configuring Linear MSP

You can configure linear MSP to protect services over the optical fibers between two nodes.
A.9.2 Querying the Status of the Linear MSP
By using this operation, you can know the current information about the linear MSP.
A.9.3 Performing Linear MSP Switching
By using this operation, you can perform the external switching on the linear MSP.
A.9.4 Starting/Stopping the Linear MSP Protocol
If you first stop the linear MSP protocol and then start it, the linear MSP status can be restored
to the initial state.

You can configure linear MSP to protect services over the optical fibers between two nodes.
Prerequisite
l The corresponding board must be added on the NE Panel.

U2000
When an unprotected service is converted into a linear MSP service by configuring the linear
MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.

The system displays the Create a Linear Multiplex Section dialog box.
Step 3 Set the parameters of the linear MSP group.

Step 4 Click OK, and then close the dialog box that is displayed.
----End
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 bidirectional cross-connections
between the services and the working channels later.
Related References
B.5.1 Parameter Description: Linear MSP_Creation

By using this operation, you can know the current information about the linear MSP.

Prerequisite
l The linear MSP must be configured.

U2000
Procedure
Step 2 Click Query > Query Protection Group to query the current linear MSP group.
Step 3 In Protection Group, click the linear MSP group to be queried.
Step 4 Click Query > Query Switching Status, and then close the dialog box that is displayed. In Slot
Mapping Relation, query the status of the linear MSP.
----End
Related References
B.5.2 Parameter Description: Linear MSP
A.9.3 Performing Linear MSP Switching

By using this operation, you can perform the external switching on the linear MSP.
Prerequisite

U2000
Procedure
Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Relation, select
the working unit or protection unit, and then right-click.
Step 3 Right-click and select the required switching mode, and then close the dialog box that is
displayed.
----End

A.9.4 Starting/Stopping the Linear MSP Protocol

If you first stop the linear MSP protocol and then start it, the linear MSP status can be restored
to the initial state.
Prerequisite

U2000
Precautions
l Stopping the ring MSP protocol causes failure of ring MSP.
l When services are switched onto the protection channel, stopping the ring MSP protocol
causes the services to switch back to the working channel. At this time, if the working
channel is normal, the services are transiently interrupted; if the working channel is faulty,
the services are interrupted until the working channel is restored to normal or the protocol
is started.
Procedure
Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be stopped.
Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that is displayed.
Step 4 Click Query > Query Protection Group to query the Protocol Status.
----End
A.10 Managing TDM Services

The TDM services involve the SDH service and the PDH service.
A.10.1 Creating the Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service
sink.
A.10.2 Creating Cross-Connections of 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.
A.10.3 Inserting TU_AIS
On an SNCP ring that adopt the IF1 board and Hybrid IF boards, if an NE houses a Hybrid IF
board and an IF1 board as its east and west IF interface boards, you need to enable the E1_AIS
insertion function for the pass-through E1 services (that is, the services cross-connected to the
IF1 board).
A.10.4 Configuring the Automatic Switching of SNCP Services

You can manually add certain alarms for the automatic switching of SNCP services.
A.10.5 Deleting Cross-Connections
When a service is not used, you can delete the cross-connections of this service to release the
corresponding resources.
A.10.6 Converting a Normal Service into an SNCP Service
By converting a normal service into an SNCP service, you can convert the unidirectional cross-
connections of a normal service into the unidirectional cross-connection in the receive direction
of the SNCP service.
A.10.7 Converting an SNCP Service to a Normal Service
By converting an SNCP service to a normal service, you can convert the SNCP cross-connection
in the receive direction into the unidirectional cross-connection of the normal service.
A.10.8 Querying TDM Services
You can learn about the TDM services that are configured for an NE by querying TDM services.
A.10.9 Switching SNCP Services
You can perform external switching on SNCP services by performing this operation.
A.10.10 Querying the Protection Status of SNCP Services
You can know the current information of an SNCP service by querying the protection status of
SNCP services.
A.10.11 Testing the E1 Service Through PRBS
If no BER tester is available, you can test the E1 service by using the PRBS test system embedded
in the equipment.

In a cross-connection of point-to-point services, one service source corresponds to one service
sink.
Prerequisite
l The corresponding source and sink boards must be added on NE Panel.

U2000
Procedure

The Create SDH Service dialog box is displayed.
Step 3 Configure the parameters of a new SDH service.
----End

Related References
B.6.1 Parameter Description: SDH Service Configuration_Creation

The cross-connection of SNCP services is a cross-connection that a working source and a
protection source correspond to a service sink.
Prerequisite
l The corresponding source and sink boards must be added on NE Panel.

U2000
Procedure
Step 2 Click Create SNCP Service.

The Create SNCP Service dialog box is displayed.
Step 3 Configure the parameters of a new SNCP service.
----End
Related References
B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation

On an SNCP ring that adopt the IF1 board and Hybrid IF boards, if an NE houses a Hybrid IF
board and an IF1 board as its east and west IF interface boards, you need to enable the E1_AIS
insertion function for the pass-through E1 services (that is, the services cross-connected to the
IF1 board).
Prerequisite
l The IFU2/IFX2 board must be added in the NE Panel.

U2000

Procedure
Step 1 In the NE Explorer, select the IFU2/IFX2 board from the Object Tree and choose Alarm >
Triggered Alarm Insertion from the Function Tree.
Step 2 Select the E1 channels on the IFU2/IFX2 board that are involved in the SNCP and then set
Insert TU_AIS to E1_AIS to Enable.
Step 3 Click Apply.
----End
Related References
B.6.6 Parameter Description: TU_AIS Insertion

You can manually add certain alarms for the automatic switching of SNCP services.
Prerequisite
l The SNCP protection group must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service
Step 2 Select the SNCP protection group, and then right-click Initiation Condition to which the
working service corresponds.
Step 3 Set the initiation condition for the working service. Click OK.
Step 4 Right-click Initiation Condition to which the protection service corresponds.
Step 5 Set the initiation condition for the protection service. Click OK.

NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation
Condition of the protection service.
----End
Related References
B.6.5 Parameter Description: SNCP Service Control
A.10.5 Deleting Cross-Connections

When a service is not used, you can delete the cross-connections of this service to release the
Prerequisite
l The cross-connections of the service must be configured and the service must not be used.

U2000
Procedure
Step 2 Query the related data.

1. Click Query.
Then, a dialog box is displayed, indicating that this operation will update the service data
saved on the NMS.
2. Click OK. Then, close the dialog box that is displayed.
Step 3 Deactivate the service.

1. Right-click the service and choose Deactivate from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to deactivate the selected
service.
2. Click OK.
Then, a dialog box is displayed, indicating that this operation will clear the corresponding
service data on the NE side.
Step 4 Delete the service.

1. Right-click the service and choose Delete from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to delete the selected service.

Step 5 Click Query. The queried information should show that the cross-connection is already deleted.
----End

By converting a normal service into an SNCP service, you can convert the unidirectional cross-
connections of a normal service into the unidirectional cross-connection in the receive direction
of the SNCP service.
Prerequisite
l The unidirectional cross-connection of the normal service must be configured and the
source of the cross-connection must be a line board.

U2000
When this task is performed to convert a normal service into an SNCP service, the original
services are not interrupted.
Procedure
Step 2 Optional: If a bidirectional SDH service is created, select this service in Cross-Connection.
Right-click the selected service and choose Expand to Unidirectional from the shortcut menu.
Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to SNCP
Service from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to perform this operation. Then, the
Convert to SNCP Service dialog box is displayed.
Step 4 Click OK.
Then, the Create SNCP Service dialog box is displayed.
Step 5 Set the parameters of the SNCP service.

Step 6 Click OK.
----End
Related References
B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into
SNCP Services
A.10.7 Converting an SNCP Service to a Normal Service

By converting an SNCP service to a normal service, you can convert the SNCP cross-connection
in the receive direction into the unidirectional cross-connection of the normal service.
Prerequisite
l The SNCP cross-connection in the receive direction must be configured.
l The current service must be transmitted on the working path.

U2000
When this task is performed to convert an SNCP service into a normal service, the original
services are not interrupted.
Procedure
Configuration > SDH Service Configuration > Cross-Connection Configuration from the
Function Tree.

Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and choose
Convert to Non-Protection Service from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to perform this operation.
Step 3 Click OK.
----End
Postrequisite
You also need to delete the unidirectional cross-connection between the service source and the
working path or the unidirectional cross-connection between the service source and the
protection path. The SNCP service can be converted into the normal service both in the receive
direction and the transmit direction only after the deletion.

You can learn about the TDM services that are configured for an NE by querying TDM services.
Prerequisite
l TDM services must be configured.

U2000
Procedure
Step 2 Click Query.
Step 3 In the displayed dialog box for confirmation, click OK.
Step 4 Close the displayed prompt dialog box. In Cross-Connection, query the TDM services.
----End
Related References
B.6.4 Parameter Description: SDH Service Configuration
A.10.9 Switching SNCP Services

You can perform external switching on SNCP services by performing this operation.
Prerequisite


U2000
Procedure
Step 2 Select the SNCP protection group for SNCP service switching.
Step 3 Click Function. Select the required switching mode from the displayed menu.
Step 4 In the displayed dialog box for confirmation, click OK.
Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then, close
the displayed prompt dialog box.
Step 6 Choose Function > Query Switch Status to check whether the switching operation is
successful.
----End

You can know the current information of an SNCP service by querying the protection status of
SNCP services.
Prerequisite

U2000
Procedure
Step 2 Select the SNCP protection group whose service protection status needs to be queried.
Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box.
----End
Related References
A.10.11 Testing the E1 Service Through PRBS

If no BER tester is available, you can test the E1 service by using the PRBS test system embedded
in the equipment.

Prerequisite
l The NE equipment must be configured with E1 services, and the E1 services must be
transmitted through the DDF.
l The communication between the NMS and the NE must be normal.

U2000
Precautions
CAUTION
l When a PRBS test is performed, the services carried on the tested path are interrupted.
l The PRBS test can be performed only in a unidirectional manner and on one path at a time.
Procedure
Step 1 On the NMS, perform an inloop for the corresponding E1 port at the remote site.
1. Select the PDH interface board in the Object Tree.
2. In the Function Tree, choose Configuration > PDH Interface.
3. Select By Function and select Tributary Loopback from the drop-down menu.
4. In Tributary Loopback, select Inloop.
5. Click Apply.
The Confirm dialog box is displayed.
6. Click OK.
7. Click OK.
The Operation Result dialog box is displayed.
8. Click Close.
Step 2 At the central site, on the NMS, select the PDH interface board in the Object Tree.
Step 3 In the Function Tree, choose Configuration > PRBS Test.
Step 4 Select the first E1 port, and then set the following PRBS-related parameters:
l Direction: Cross
l Duration: a value from 120 to 180
l Measured in Time: seconds

Step 5 Click Start to Test.

The system displays a dialog box indicating The operation may interrupt the service, Are
you sure to continue?
Step 6 Click OK.
Step 7 When the Progress column is 100%, click Query to check the test result.
The curve diagram should be green.
Step 8 Release the inloop set in Step 1.
4. In Tributary Loopback, select Non-Loopback.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
Step 9 Repeat Step 1 through Step 8 to test all other E1 ports.
----End
A.11 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.11.1 Configuring the Clock Sources

This topic describes how to configure the clock source according to the planned clock
synchronization scheme to ensure that all the NEs on the network trace the same clock.
A.11.2 Configuring Clock Subnets
For simple networks, such as chain networks, you need not configure the clock source protection
or you only need to configure the clock priority to implement the clock source protection. For
complex networks, such as ring networks or intersecting and tangent rings that are derived from
ring networks, you need to configure clock subnets and enable the standard SSM protocol or
extended SSM protocol to implement the clock source protection.

A.11.3 Self-Defined Clock Quality

By default, the NE considers the clock quality extracted from the clock source as the clock
quality. If the clock quality is zero (the synchronization quality is unknown), the clock is
considered as unavailable clock. In the case of any special requirements, the user can define the
clock quality for which the source clock quality and clock quality are zero.
A.11.4 Configuring the SSM Output Status
After the SSM protocol is enabled or extended, the NE transmits the SSM to other NEs through
the SDH radio link or optical line by default. To prevent two clock subnets from affecting each
other, the NE needs to forbid the clock ID from being transmitted on the link that is connected
to other clock subnets.
A.11.5 Configuring the Clock ID Output Status
After the SSM protocol is enabled or is extended, the NE transmits the clock ID to other NEs
through the radio link or optical line by default. To prevent two clock subnets from affecting
each other, the NE needs to forbid the clock ID from being transmitted on the link that is
connected to other clock subnets.
A.11.6 Modifying the Parameters of the Clock Output
The NE outputs the 2-Mbit/s external clock regardless of the clock quality.
A.11.7 Changing the Conditions for Clock Source Switching
You can change the default conditions for clock source switching of the NE for special purposes.
A.11.8 Modifying the Recovery Parameter of the Clock Source
In the case of the special requirements, you can modify the recovery parameter of the clock
source.
A.11.9 Querying the Clock Synchronization Status
You can know the current clock synchronization status of an NE by querying the clock
synchronization status.

This topic describes how to configure the clock source according to the planned clock
synchronization scheme to ensure that all the NEs on the network trace the same clock.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Source Priority.
Step 2 Click the System Clock Source Priority List tab.

The Add Clock Source dialog box is displayed.

Step 4 Select the clock sources.

TIP
By pressing the Ctrl key on the keyboard, you can select multiple clock sources at one time.
Step 5 Click OK.
Step 6 Optional: Repeat Step 3 to Step 5 to add other clock sources.
Step 7 Optional: Select a clock source and click or to adjust the priority of this
clock source.
NOTE
The clock priorities levels are arranged in a descending order from the first row to the last row. The internal
clock source is always of the lowest priority.
Step 8 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external
clock sources.
Step 9 Click Apply.
----End
Related References
B.7.1 Parameter Description: Clock Source Priority Table

For simple networks, such as chain networks, you need not configure the clock source protection
or you only need to configure the clock priority to implement the clock source protection. For
complex networks, such as ring networks or intersecting and tangent rings that are derived from
ring networks, you need to configure clock subnets and enable the standard SSM protocol or
extended SSM protocol to implement the clock source protection.

Prerequisite
l The priority list of the clock source must be configured.

U2000
Procedure
Subnet Configuration.
Step 2 Click the Clock Subnet tab.
Step 3 Start the clock protection protocol and configure its parameters.
Step 4 Click Apply.
----End
Related References
B.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet

By default, the NE considers the clock quality extracted from the clock source as the clock
quality. If the clock quality is zero (the synchronization quality is unknown), the clock is
considered as unavailable clock. In the case of any special requirements, the user can define the
clock quality for which the source clock quality and clock quality are zero.
Prerequisite
l The priority level of a clock source must be set.

U2000

Procedure
Step 2 Click the Clock Quality tab.
Step 3 Click the Clock Source Quality tab.
Step 4 Set the self-defined clock quality.
NOTE
Generally, it is recommended that you use the default value.
Step 5 Click Apply.
Step 6 Click the Manual Setting of 0 Quality Level tab.
Step 7 Set the clock quality for which the quality level is zero.
NOTE
Generally, it is recommended that you use the default value.
Step 8 Click Apply.
----End
Related References
B.7.3 Parameter Description: Clock Subnet Setting_Clock Quality

After the SSM protocol is enabled or extended, the NE transmits the SSM to other NEs through
the SDH radio link or optical line by default. To prevent two clock subnets from affecting each
other, the NE needs to forbid the clock ID from being transmitted on the link that is connected
to other clock subnets.
Prerequisite
l The SSM protocol must be enabled or extended.

U2000

Procedure
Step 2 Click the SSM Output Control tab.
Step 3 Set the SSM control status.
Step 4 Click Apply.
----End
Related References
B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control

After the SSM protocol is enabled or is extended, the NE transmits the clock ID to other NEs
through the radio link or optical line by default. To prevent two clock subnets from affecting
each other, the NE needs to forbid the clock ID from being transmitted on the link that is
connected to other clock subnets.
Prerequisite
l The extended SSM protocol must be enabled.

U2000
Procedure
Step 2 Click the Clock ID Status tab.
Step 3 Set the clock ID control status.
Step 4 Click Apply.
----End
Related References
B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status


The NE outputs the 2-Mbit/s external clock regardless of the clock quality.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Phase-Locked Source Output by External Clock.
Step 2 Modify the parameters of the clock output.
Step 3 Click Apply.
----End
Related References
B.7.9 Parameter Description: Output Phase-Locked Source of the External Clock Source

You can change the default conditions for clock source switching of the NE for special purposes.
Prerequisite

U2000
Procedure
Source Switching.
Step 2 Click the Clock Source Switching Condition tab.
Step 3 Change the conditions for clock source switching.

Step 4 Click Apply.
----End
Related References
B.7.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions

In the case of the special requirements, you can modify the recovery parameter of the clock
source.
Prerequisite

U2000
Procedure
Source Switching.
Step 2 Click the Clock Source Reversion Parameter tab.
Step 3 Set the recovery parameter of the clock source.
Step 4 Click Apply.
----End
Related References
B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters

You can know the current clock synchronization status of an NE by querying the clock
synchronization status.
Prerequisite

U2000

Procedure
Synchronization Status.
Step 2 Query the clock synchronization status.
----End
Related References
B.7.10 Parameter Description: Clock Synchronization Status
A.12 Configuring Ethernet Services and Features on the

Packet Plane
Configurations of Ethernet services and features on the packet plane include Ethernet port
configuration, protection configuration, service configuration, protocol configuration, and OAM
configuration.
A.12.1 Managing the ERPS

The Ethernet ring protection switching (ERPS) on the FE/GE ring or Hybrid radio ring can be
configured to protect the Ethernet service.
A.12.2 Managing the LAG
Link aggregation allows one or multiple links that are attached to the same equipment to be
aggregated together to form a LAG. The aggregated links can be considered as a single logical
link by the MAC address. In this manner, the bandwidth is increased and the availability of the
links is improved.
A.12.3 Configure the Ethernet Service
The Ethernet service is classified into two types, namely, E-Line service and E-LAN service.
A.12.4 Managing the MAC Address Table
The MAC address table is the core of the E-LAN service. The OptiX RTN 950 provides various
functions for managing the MAC address table.
A.12.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC
address table or a multicast frame whose destination MAC address is not listed in the multicast
group. By default, the NE broadcasts the unknown frame. By setting the mode for processing
an unknown frame of the E-LAN service, you can change the processing mode so that unknown
frame can be discarded.
A.12.6 Setting the Parameters of Ethernet Ports
This section describes how to configure the parameters of Ethernet ports, including general
attributes, traffic control, layer 2 (L2) attributes, and advanced attributes.
A.12.7 Setting the General Attributes of the IF_ETH Port
The IF_ETH port is the internal Ethernet port in a Hybrid IF board, which is used to access
Ethernet services over Hybrid radio.
A.12.8 Managing the MSTP
The OptiX RTN 950 supports only the MSTP that generates the CIST.
A.12.9 Managing the IGMP Snooping

If the multicast router exists on a network, the bridge can enable the IGMP Snooping protocol
to realize the multicast function with the operation of the router.
A.12.10 Managing the QoS
By managing the QoS, you can provide the services of different levels for different service types.
A.12.11 Using the IEEE 802.1ag OAM
By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.
A.12.12 Using the IEEE 802.3ah OAM
By using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links.
A.12.13 LPT Configuration
If a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automatically
disabled through the LPT function.
A.12.1 Managing the ERPS

The Ethernet ring protection switching (ERPS) on the FE/GE ring or Hybrid radio ring can be
configured to protect the Ethernet service.
A.12.1.1 Creating Ethernet Ring Protection Instances

The Ethernet ring protection switching (ERPS) protection is configured through creation of
Ethernet ring protection instances.
A.12.1.2 Setting the Parameters of Ethernet Ring Protocol
The parameters to be set include the hold-off time, WTR time, and guard time.
A.12.1.3 Querying the Status of the Ethernet Ring Protocol
By using this operation, you can know the current status of the Ethernet ring protection switching
(ERPS).

The Ethernet ring protection switching (ERPS) protection is configured through creation of
Ethernet ring protection instances.
Prerequisite
l The Ethernet boards or hybrid IF boards must be added to the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
Step 2 Click New.
The Create Ethernet Ring Protection Protocol Instance dialog box is displayed.
Step 3 Set the parameters for the ERPS protection instance.

Step 4 Click OK.
----End
Related References
B.9.2.1 Parameter Description: ERPS Management_Creation

The parameters to be set include the hold-off time, WTR time, and guard time.
Prerequisite
l The protection instance of the ERPS must be created.

U2000
Procedure
Protection > ERPS Management from the Function Tree.
Step 2 Optional: Double-click Control VLAN, and then modify the VLAN ID.
Step 3 Optional: Set the parameters of Ethernet ring protocol.

Step 4 Click Apply.
----End
Related References
B.9.2.2 Parameter Description: ERPS Management

By using this operation, you can know the current status of the Ethernet ring protection switching
(ERPS).
Prerequisite

U2000
Procedure
Step 2 Click Query.
Step 3 Query the status of the Ethernet ring protocol.
----End
Related References
A.12.2 Managing the LAG

Link aggregation allows one or multiple links that are attached to the same equipment to be
aggregated together to form a LAG. The aggregated links can be considered as a single logical
link by the MAC address. In this manner, the bandwidth is increased and the availability of the
links is improved.
A.12.2.1 Creating a LAG

Between two NEs, if the bandwidth and availability of the Ethernet links need to be improved,
the new LAG must be created.
A.12.2.2 Setting Parameters for LAGs
The parameters for a LAG include port priorities. In a static LAG, traffic is always carried by a
port with a higher priority.
A.12.2.3 Querying the Protocol Information of the LAG
Through this operation, you can learn about the running information of the LACP used for the
LAG.


Between two NEs, if the bandwidth and availability of the Ethernet links need to be improved,
the new LAG must be created.
Prerequisite
l The board on which the LAG port to be created must be added to the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 2 Click the Link Aggregation Group Management tab.
Step 3 Click New.
The system displays the Create Link Aggregation Group dialog box.
Step 4 Set the attributes of the LAG in Attribute Settings.
Step 5 Set the LAG port in Port Settings.

1. Set Main Board and Main Port.
2. In Available Slave Ports, select Board of the slave port.
3. In Port, select the slave port, and then click .

TIP
Hold on the Ctrl key or the Shift key on the keyboard to select multiple ports.

4. Click OK. A dialog box is displayed for confirmation. Click OK. Then, a dialog box is
displayed, indicating that the operation is successful. Close this dialog box.
----End
Related References
B.9.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation

The parameters for a LAG include port priorities. In a static LAG, traffic is always carried by a
port with a higher priority.
Prerequisite
l The board on which the LAG to be created must be added to NE Panel.

U2000
Procedure
Step 2 Click the Port Priority tab.
Step 3 Set the port priority.
----End

Related References
B.9.2.16 Parameter Description: Ethernet Link Aggregation_Link Aggregation
A.12.2.3 Querying the Protocol Information of the LAG

Through this operation, you can learn about the running information of the LACP used for the
LAG.
Prerequisite
l The LAG must be created.

U2000
Procedure
Step 3 Click Query. A dialog box is displayed, indicating that the operation is successful. Then, close
this dialog box.
Step 4 In the Main Interface, select the LAG to be queried.
Step 5 Query port status of the main and slave ports.

NOTE
The system displays the information about the slave port in the lower part of the Main Interface.
Step 6 Right-click on the selected LAG and choose the specific information about the LAG from the
shortcut menu.
Step 7 Click the Port Priority tab.
Step 8 Click Query. A dialog box is displayed, indicating that the operation is successful. Close this
dialog box.
Step 9 Query the port priority of the LAG.
----End

A.12.3 Configure the Ethernet Service

The Ethernet service is classified into two types, namely, E-Line service and E-LAN service.
A.12.3.1 Configuring the QinQ Link

Configuring the QinQ link is the prerequisite for configuring QinQ private line services.
A.12.3.2 Configuring the E-Line Service
The E-Line service refers to the static transmission of the Ethernet service in the point-to-point
mode.
A.12.3.3 Creating a VLAN Forwarding Table Item
After the corresponding VLAN forwarding table item is created, the VLAN IDs of the service
packets can be switched at the source or sink end of the E-Line service.
A.12.3.4 Configuring the E-LAN Service
The E-LAN service refers to the dynamic transmission of the Ethernet service in the multipoint-
to-multipoint mode through MAC address.
A.12.3.5 Changing Logical Ports Connected to a VB
This section describes how to change the logical ports connected to a VB and the attributes of
the ports.
A.12.3.6 Deleting an E-Line Service
When an E-Line service is not used, you need to delete the E-line service to release the
A.12.3.7 Deleting E-LAN Services
When an E-LAN service is not required, you can delete this E-LAN service to release
corresponding Ethernet resources.
A.12.3.8 Testing the Ethernet Service
By testing the Ethernet service, you can check whether the Ethernet service is available over
radio links. The Ethernet service can be tested through the ETH-OAM function. Thus, no tester
is required.

Configuring the QinQ link is the prerequisite for configuring QinQ private line services.
Prerequisite
l The Ethernet board must be added on the NE Panel.
l On associated ports, the Encapsulation Type is set to QinQ.

U2000
Procedure
Service Management > QinQ Link from the Function Tree.

Step 2 Click New.

Step 3 Configure the basic attributes of the QinQ link.
Step 4 Click OK.
----End
Related References
B.9.1.6 Parameter Description: QinQ Link_Creation

The E-Line service refers to the static transmission of the Ethernet service in the point-to-point
mode.
Prerequisite

U2000
Procedure
Service Management > E-Line Service from the Function Tree.
Step 2 Click New.
The New E-Line Service dialog box is displayed.
Step 3 Configure Direction of the E-Line service.
Step 4 Configure the attributes of the E-Line service.
NOTE
The port parameter varies according to Direction.

Step 5 Click OK.

Step 6 Ensure that the parameters are set correctly and then click OK.
NOTE
To check the parameters that are configured in the preceding step, click Configure the source and sink.
----End

Related References
B.9.1.1 Parameter Description: E-Line Service_Creation

After the corresponding VLAN forwarding table item is created, the VLAN IDs of the service
packets can be switched at the source or sink end of the E-Line service.
Prerequisite
l The corresponding Ethernet board must be added to NE Panel.
l The UNI-UNI E-Line service must be created.

U2000
Procedure
Step 2 Click the VLAN Forwarding Table Item tab.
Step 3 Click New.
Step 4 Set the attributes of the new VLAN forwarding table item.
Step 5 Click OK. Then, close the dialog box that is displayed.
----End
Related References
B.9.1.3 Parameter Description: VLAN Forwarding Table Item_Creation

The E-LAN service refers to the dynamic transmission of the Ethernet service in the multipoint-
to-multipoint mode through MAC address.
Prerequisite

U2000

Procedure
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The New E-LAN Service dialog box is displayed.
Step 3 Configure the attributes of the bridge.
NOTE
l The port parameter varies according to Tag Type.


Step 4 Configure the port that is mounted to the bridge on the UNI side of the E-LAN service.
1. Click the UNI tab.
2. Click Configuration, and then select the port that needs to be mounted to the bridge in the
Configure Port dialog box that is displayed.
TIP
Hold on the Ctrl key on the keyboard to select multiple ports.
3. Click .
4. Optional: Configure the attributes of the port that needs to be mounted to the bridge in the
Selected Ports dialog box.
NOTE
The parameter that can be configured varies according to Tag Type.

5. Click OK.
Step 5 Optional: Configure the logical port on the NNI side.

NOTE
This step takes effect only when Tag Type is set to S-Awared.
Step 6 Optional: Configure the split horizon group.

1. Click the Split Horizon Group tab.

2. Click New, then the New Split Horizon Group dialog box is displayed.
3. Select a port from Available Interfaces, and then click .

TIP

4. Click OK.
Step 7 Click OK.
Step 8 Optional: Select Split Horizon Group.

1. Click Create.
Then, the Create Split Horizon Group dialog box is displayed.
2. Select the port to be added from Available Port List and then click .
NOTE
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
3. Click OK.
----End
Related References
B.9.1.4 Parameter Description: E-LAN Service_Creation
A.12.3.5 Changing Logical Ports Connected to a VB

This section describes how to change the logical ports connected to a VB and the attributes of
the ports.
Prerequisite
l The E-LAN services must be created.


U2000
Procedure
Step 2 Add or delete logical ports connected to a VB.

NOTE
l To add or delete ports connected to the VB on the UNI side, click the UNI tab.
l To add or delete ports connected to the VB on the NNI side, click the NNI tab.
1. Click Configuration. In the Configure Port dialog box that is displayed, select the port
to be added to or deleted from the list of ports connected to the VB.
2. Optional: Click to add ports to the list of ports connected to the VB.
3. Optional: Click to delete ports from the list of ports connected to the VB.
TIP
4. In Selected Port List, set the attributes of the ports connected to the VB.
----End
A.12.3.6 Deleting an E-Line Service

When an E-Line service is not used, you need to delete the E-line service to release the
Prerequisite
l The E-Line service must be configured and the service is not used.

U2000
Procedure
Step 2 Click Query, and then close the dialog box that is displayed.
Step 3 Select the Ethernet-line service that needs to be deleted and then click Delete.
Then, a dialog box is displayed, querying whether you need to perform this operation.
Step 4 Click OK.

Step 5 Click Query.

At this time, the E-line service is already deleted.
----End
A.12.3.7 Deleting E-LAN Services

When an E-LAN service is not required, you can delete this E-LAN service to release
corresponding Ethernet resources.
Prerequisite
l A configured E-LAN service is not required.

U2000
Procedure
Step 2 Click Query. Then, close the dialog box that is displayed.
Step 3 Select the E-LAN service to be deleted and click Delete.

Then, a confirmation dialog box is displayed.
Step 4 Click OK.
Step 5 Click Query.

At this time, the E-LAN service is already deleted.
----End
A.12.3.8 Testing the Ethernet Service

By testing the Ethernet service, you can check whether the Ethernet service is available over
radio links. The Ethernet service can be tested through the ETH-OAM function. Thus, no tester
is required.
Prerequisite
Ethernet services must be configured.
NOTE
It is recommended that you test low-priority Ethernet services in good weather conditions, where the AM
function works in the highest modulation mode.

U2000

Test Connection Diagram

The following test procedure considers the Ethernet service from PORT2 on NE2 and PORT3
on NE3 to PORT1 on NE1 as an example, as shown in Figure A-1.The three Ethernet ports are
not on the EFP8 boards.
Figure A-1 Networking diagram for testing the Ethernet service
NE 2 PORT 2
VLAN ID=100
NE 1
PORT 1
NE 3
PORT 3
Microwave network
VLAN ID=200
The VLAN ID of the Ethernet service from NE2 to NE1 is 100, and the VLAN ID of the Ethernet
service from NE3 to NE1 is 200.
NOTE
If the Ethernet ports are on the EFP8 boards, you can still perform the following steps to test the Ethernet
services by eliminating the need to set up the remote maintenance end point. In addition, the operations on
the NMS are different. For details, see A.13.8.1 Creating MDs, A.13.8.2 Creating MAs, A.13.8.3
Creating MPs, and A.13.8.5 Performing an LB Test.
Procedure
Step 1 Configure the maintenance domains of NE1, NE2, and NE3.
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
2. Choose New > New Maintenance Domain.
The New Maintenance Domain dialog box is displayed.
3. Configure the parameters of the new maintenance domains.
l Maintenance Domain Name: MD1 for NE1, NE2, and NE3
l Maintenance Domain Level: 4 for NE1, NE2, and NE3
NOTE
The maintenance domain names of the NEs can be different, but the maintenance domain levels
of the NEs must be the same.

4. Click OK to close the displayed dialog box.

Step 2 Configure the maintenance associations of NE1, NE2, and NE3.
2. Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.
The New Maintenance Association dialog box is displayed.
3. Configure the parameters of the new maintenance associations.
l Maintenance Association Name: MA1 for NE1, NE2, and NE3
l Relevant Service: services from NE1 to NE2 and NE3
NOTE
Click in Relevant Service, and select relevant services in the New Maintenance
Association dialog box.

Step 3 Configure the MEPs of NE1, NE2, and NE3.
2. Click the Maintenance Association tab.
3. Select the maintenance association in which an MEP needs to be created. Choose New >
New MEP Point.
The system displays the New MEP Point dialog box.
4. Configure the parameters of the new MEPs.
l MP ID: 101 for NE1, 102 for NE2, and 103 for NE3
l Direction: Ingress for NE1, NE2, and NE3
l CC Status: activation for NE1, NE2, and NE3

Step 4 Configure the remote MEPs for the maintenance associations of NE1, NE2, and NE3.
3. Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point
dialog box is displayed.
4. Click New.
Then, the Add Maintenance Association Remote Maintenance Point dialog box is
displayed.
5. Set the parameters of the new remote MEPs.
l Remote Maintenance Point ID: 102 and 103 for NE1, and 101 for NE2 and NE3
NOTE
Set the Remote Maintenance Point ID of NE1 to the MP ID of NE2 and NE3, and set the
Remote Maintenance Point ID of NE2 and NE3 to the MP ID of NE1.
Step 5 Test the availability of the Ethernet services from NE1 to NE2 and NE3.
1. Select an NE from the Object Tree in the NE Explorer of the NE1, and then choose
Configuration > Ethernet OAM Management > Ethernet Service OAM.
2. Select the MD, MA, and MEP that correspond to Port 1, click OAM.
3. Select Start LB.
The LB Test window is displayed.
4. Select Destination Maintenance Point ID, and set the parameters in Test Node.
l Source Maintenance Point ID: 101 (maintenance point ID of NE1)
l Destination Maintenance Point ID: 102 (maintenance point ID of NE2)
l Transmitted Packet Count: 20 (recommended)

l Transmitted Packet Length: 64 (64 is a recommended value, and the parameter can
also be set to 128, 256, 512, 1024, and 1280 for testing the Ethernet services of different
packet lengths.)
NOTE
The maximum Packet Length is 1400.

l Transmitted Packet Priority: 7 (recommended)
5. Click Start Test.

6. Check Detection Result.
The LossRate in the Detection Result should be 0.
7. Repeat Step 5.4 to Step 5.6 to test the Ethernet services from NE1 to NE3.
l Source Maintenance Point ID: 101 (maintenance point ID of NE1)
l Destination Maintenance Point ID: 103 (maintenance point ID of NE3)
l Transmitted Packet Count: 20 (recommended)
l Transmitted Packet Length: 64 (recommended)
l Transmitted Packet Priority: 7 (recommended)
----End

The MAC address table is the core of the E-LAN service. The OptiX RTN 950 provides various
functions for managing the MAC address table.
A.12.4.1 Creating a Static MAC Address Entry

Through the creation of a static MAC address entry, the host with a specified MAC address is
not affected by MAC address aging. In addition, the E-LAN service can be supported by the
host that receives packets only.
A.12.4.2 Creating a Blacklist Entry of MAC Addresses

Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC
address can be prohibited from using the E-LAN service.
A.12.4.3 Configuring the Aging Parameters of a MAC Address Table
By default, the aging function of a MAC address table is enabled and the aging time is five
minutes. By configuring the aging parameters of a MAC address table, you can modify such
parameters.
A.12.4.4 Querying or Deleting a Dynamic MAC Address
By querying or deleting a dynamic MAC address, you can query or delete all the MAC address
entries that are learned by the E-LAN service.

Through the creation of a static MAC address entry, the host with a specified MAC address is
not affected by MAC address aging. In addition, the E-LAN service can be supported by the
host that receives packets only.
Prerequisite
l The E-LAN service must be created.

U2000
Procedure
Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to be
created.
Step 3 Click the Static MAC Address tab.
Step 4 Click New.

The New Static MAC Address dialog box is displayed.
Step 5 Configure the parameters of the static MAC address entry.
----End
Related References
B.9.1.5 Parameter Description: E-LAN Service


Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC
address can be prohibited from using the E-LAN service.
Prerequisite

U2000
Procedure
Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses needs
to be created.
Step 3 Click the Disabled MAC Address tab.
Step 4 Click New.
The Create Disabled MAC Address dialog box is displayed.
Step 5 Configure the blacklist entry of MAC addresses.
----End
Related References

By default, the aging function of a MAC address table is enabled and the aging time is five
minutes. By configuring the aging parameters of a MAC address table, you can modify such
parameters.
Prerequisite

U2000

Procedure
Step 2 On the main interface, select the E-LAN service whose aging parameters of the MAC address
table need to be configured.
Step 3 Click the MAC Address Learning Parameters tab.
Step 4 Configure the status of the aging function and set the aging time.
----End
Related References

By querying or deleting a dynamic MAC address, you can query or delete all the MAC address
entries that are learned by the E-LAN service.
Prerequisite

U2000
Procedure
Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to be
queried or cleared.
Step 3 Click the Self-Learning MAC Address tab.
Step 4 Optional: Select the board whose dynamic MAC address needs to be queried and then check
the dynamic MAC addresses in the MAC address table that is displayed.
Step 5 Optional: Click Clear MAC Address to clear the dynamic MAC addresses. Then, click OK
in the dialog box that is displayed for confirmation.
----End

Related References
A.12.5 Setting the Mode for Processing an Unknown Frame of the

E-LAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC
address table or a multicast frame whose destination MAC address is not listed in the multicast
group. By default, the NE broadcasts the unknown frame. By setting the mode for processing
an unknown frame of the E-LAN service, you can change the processing mode so that unknown
frame can be discarded.
Prerequisite

U2000
Procedure
Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown frame
needs to be set.
Step 3 Click the Unknown Frame Processing tab.
Step 4 Set the mode for processing an unknown frame of the E-LAN service.
----End
Related References
A.12.6 Setting the Parameters of Ethernet Ports

This section describes how to configure the parameters of Ethernet ports, including general
attributes, traffic control, layer 2 (L2) attributes, and advanced attributes.
A.12.6.1 Setting the General Attributes of Ethernet Ports

The general attributes of Ethernet ports define the physical-layer information, such as the
interface mode, encapsulation type, and maximum frame length.

A.12.6.2 Configuring the Traffic Control of Ethernet Ports

After the traffic control is enabled, the Ethernet port sends the pause frame to notify the peer
end of stop sending Ethernet packets for a period if the link is congested, thus eliminating link
congestion.
A.12.6.3 Setting the Layer 2 Attributes of Ethernet Ports
The L2 attributes of Ethernet ports define the link-layer information.
A.12.6.4 Setting the Advanced Attributes of Ethernet Ports
The advanced attributes of Ethernet ports are used to configure the MAC/PHY loopback and
query the traffic rate on the port.

The general attributes of Ethernet ports define the physical-layer information, such as the
interface mode, encapsulation type, and maximum frame length.
Prerequisite

U2000
Procedure
Management > Ethernet Interface from the Function Tree.
Step 2 Click the General Attributes tab.
Step 3 Configure the general attributes of Ethernet ports.
----End
Related References
B.9.5.1 Parameter Description: Ethernet Interface_Basic Attributes

After the traffic control is enabled, the Ethernet port sends the pause frame to notify the peer
end of stop sending Ethernet packets for a period if the link is congested, thus eliminating link
congestion.

Prerequisite

U2000
Procedure
Step 2 Click the Flow Control tab.
Step 3 Configure the traffic control of Ethernet ports.
----End
Related References
B.9.5.2 Parameter Description: Ethernet Interface_Flow Control

The L2 attributes of Ethernet ports define the link-layer information.
Prerequisite

U2000
Procedure
Step 2 Click the Layer 2 Attributes tab.

Step 3 Configure the L2 attributes of Ethernet ports.
----End
Related References
B.9.5.3 Parameter Description: Ethernet Interface_Layer 2 Attributes

The advanced attributes of Ethernet ports are used to configure the MAC/PHY loopback and
query the traffic rate on the port.
Prerequisite

U2000
Procedure
Step 3 Configure the advanced attributes of Ethernet ports.
----End
Related References
B.9.5.4 Parameter Description: Ethernet Interface_Advanced Attributes

A.12.7 Setting the General Attributes of the IF_ETH Port

The IF_ETH port is the internal Ethernet port in a Hybrid IF board, which is used to access
Ethernet services over Hybrid radio.
A.12.7.1 Setting the General Attributes of the IF_ETH Port

The general attributes of the IF_ETH port specify the basic information, including the port mode
and encapsulation mode.
A.12.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
The Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer,
including the tag attribute and QinQ type domain.
A.12.7.3 Setting the Advanced Attributes of the IF_ETH Port
The advanced attributes of the IF_ETH port are used to specify whether to discard the error
frames, specify whether to perform loopback at the MAC layer, and to check the port rate.

The general attributes of the IF_ETH port specify the basic information, including the port mode
and encapsulation mode.
Prerequisite
l The corresponding IF board must be added to NE Panel.

U2000
Procedure
Management > Microwave Interface from the Function Tree.
Step 2 Click the Basic Attributes tab.
Step 3 Set the general attributes of the IF_ETH port.
----End
Related References
B.12.14 Parameter Description: Microwave Interface_Basic Attributes

The Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer,
including the tag attribute and QinQ type domain.

Prerequisite

U2000
Procedure
Step 2 Click the Layer 2 Attributes tab.
Step 3 Setting the Layer 2 attributes of the IF_ETH port.
----End
Related References
B.12.15 Parameter Description: Microwave Interface_Layer 2 Attributes

The advanced attributes of the IF_ETH port are used to specify whether to discard the error
frames, specify whether to perform loopback at the MAC layer, and to check the port rate.
Prerequisite

U2000
Procedure
Step 3 Setting the advanced attributes of the IF_ETH port.

----End
Related References
B.12.16 Parameter Description: Microwave Interface_Advanced Attributes
A.12.8 Managing the MSTP

The OptiX RTN 950 supports only the MSTP that generates the CIST.
A.12.8.1 Creating the MSTP Port Group

When the NE needs to run the MSTP protocol together with the user network, the ports on the
NE that are connected to the user network need to be configured as a port group. All the members
in the port group are involved in the spanning tree algorithm of the user network.
A.12.8.2 Setting the Bridge Parameters of the MSTP
This topic describes how to set the bridge parameters and port parameters of the MSTP.
A.12.8.3 Setting the Parameters of the CIST
This topic describes how to set the CIST parameters, including the bridge priority, port priority,
and path overheads.
A.12.8.4 Querying the CIST Running Information
By querying the CIST running information, you can be familiar with the current information of
the CIST.
A.12.8.5 Changing the Spanning Tree Protocol Used by the Port Group
When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTP
protocol) for the equipment that runs the spanning tree together with the local NE, you need to
change the spanning tree protocol used by the port group on the local NE to be the same.
A.12.8.6 Enabling/Disabling the MSTP Protocol
This topic describes how to enable or disable the MSTP protocol of a port group or members of
the port group.
A.12.8.7 Modifying the Configuration Data of the MSTP Port Group
This topic describes how to modify the configuration data of the MSTP port group.

When the NE needs to run the MSTP protocol together with the user network, the ports on the
NE that are connected to the user network need to be configured as a port group. All the members
in the port group are involved in the spanning tree algorithm of the user network.
Prerequisite
l The boards where the member ports are located must be added in NE Panel.

U2000

Procedure
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab.
Step 3 Click Create. The Create Port Group dialog box is displayed.
Then, the Create Port Group dialog box is displayed.
Step 4 Set the attributes of the port group.

1. Set Protocol Type and Enable Protocol.
2. Select the board where the member port is located from the drop-down list of Board under
Apply Port.
3. Select the member port from Available Port List. Then, click .
TIP
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting
the ports.
4. Click OK.
----End
Related References
B.9.2.3 Parameter Description: MSTP Configuration_Port Group Creation

This topic describes how to set the bridge parameters and port parameters of the MSTP.
Prerequisite
l The port group must be created.


U2000
Procedure
Step 2 Click the Bridge Parameters tab.
Step 3 Select the port group ID.
Step 4 Click the Bridge Parameters tab.
Step 5 Set the attributes of the bridge.
Step 6 Click Apply.
Step 7 Click the Port Parameter tab.
Step 8 Set the parameters of each member of the port group.
Step 9 Click Apply.
----End
Related References
B.9.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters

This topic describes how to set the CIST parameters, including the bridge priority, port priority,
and path overheads.
Prerequisite
l The port group must be created.

U2000
Procedure

Step 2 Click the CIST&MSTI Parameters tab.
Step 3 Select the port group from the drop-down list of Port Group.
Step 4 Set the parameters of the port group.
Step 5 Click Apply.
----End
Related References
B.9.2.6 Parameter Description: MSTP Configuration_CIST Parameters

By querying the CIST running information, you can be familiar with the current information of
the CIST.
Prerequisite
l The MSTP port group must be created.

U2000
Procedure
Step 2 Click the CIST Running Information tab.

Step 3 Click Query.
Step 4 Query the CIST running information.
----End
Related References
B.9.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST
A.12.8.5 Changing the Spanning Tree Protocol Used by the Port Group
When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTP
protocol) for the equipment that runs the spanning tree together with the local NE, you need to
change the spanning tree protocol used by the port group on the local NE to be the same.
Prerequisite

U2000
Procedure
Step 3 Select the target protocol type from the Protocol Type drop-down list of the port group whose
spanning tree protocol needs to be changed.
Step 4 Click Apply.
----End
A.12.8.6 Enabling/Disabling the MSTP Protocol

This topic describes how to enable or disable the MSTP protocol of a port group or members of
the port group.
Prerequisite

U2000

Procedure
Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group for
which the MSTP protocol needs to be enabled or disabled.
Step 4 Click Apply.

Step 5 Select Enabled or Disabled from the Enable Protocol drop-down list in Port Group to enable
or disable the MSTP protocol of a port.
Step 6 Click Apply.
----End

This topic describes how to modify the configuration data of the MSTP port group.
Prerequisite

U2000
Procedure
Step 3 Click Configuration.
Then, the Configure Port Group dialog box is displayed.
Step 4 Modify the configuration data of the MSTP port group.
Option Description
If ... Then ...

Option Description
A member port needs to be added 1. Select the board where the member ports are located
from the drop-down list of Board.
2. Select the port to be added from Available Port
List.
3. Click .
A member port needs to be deleted 1. Select the port to be deleted from Selected Port
List.
2. Click .
TIP
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the ports.
Step 5 Click OK.
----End
Related References
B.9.2.4 Parameter Description: MSTP Configuration_Port Group Configuration
A.12.9 Managing the IGMP Snooping

If the multicast router exists on a network, the bridge can enable the IGMP Snooping protocol
to realize the multicast function with the operation of the router.
A.12.9.1 Configuring the IGMP Snooping Protocol

This topic describes how to configure the IGMP Snooping protocol for a specific E-LAN service.
A.12.9.2 Querying the Port Information of the Routers
By querying the port information of the router, you can be familiar with the port information of
each router that runs the IGMP Snooping protocol.
A.12.9.3 Querying the Information About the Multicast Groups

This topic describes how to query the information about each multicast group in the IGMP
Snooping protocol.
A.12.9.4 Creating Static Router Ports
Static router ports are not aged.
A.12.9.5 Creating a Member of a Static Multicast Group
The members of a static multicast group are not aged.
A.12.9.6 Adding a Quickly Deleted Port
If an Ethernet port is connected to only one host, you can set this Ethernet port as a quickly
deleted port.
A.12.9.7 Calculating IGMP Packets
By calculating IGMP packets, you can be familiar with the information about the IGMP packets
received and transmitted through the IGMP Snooping protocol.

This topic describes how to configure the IGMP Snooping protocol for a specific E-LAN service.
Prerequisite

U2000
Procedure
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab.
Step 3 Set the attributes of the IGMP Snooping protocol.
Step 4 Click Apply.
----End
Related References
B.9.2.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration

By querying the port information of the router, you can be familiar with the port information of
each router that runs the IGMP Snooping protocol.

Prerequisite

U2000
Procedure
Step 2 Click the Router Port Management tab.
Step 3 Click Query.
Step 4 Query the port information of the routers.
----End
Related References
B.9.2.10 Parameter Description: IGMP Snooping Configuration_Route Management

This topic describes how to query the information about each multicast group in the IGMP
Snooping protocol.
Prerequisite

U2000
Procedure
Step 2 Click the Route Member Port Management tab.
Step 3 Click Query.
Step 4 Query the information about the multicast groups.
----End
Related References
B.9.2.12 Parameter Description: IGMP Snooping Configuration_Route Member Port
Management


Static router ports are not aged.
Prerequisite
l The NNI port must be configured for the E-LAN service.

U2000
Procedure
Step 2 Click the Router Port Management tab.
Step 3 Click New.
Step 4 Set the attributes of the static router ports.

1. Set Service ID and VLAN ID.
1. Select the static router port from the drop-down list of Available Port. Click .
TIP
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting
the ports.
2. Click OK.
----End
Related References
B.9.2.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation


The members of a static multicast group are not aged.
Prerequisite
l The UNI port must be configured for the E-LAN service.

U2000
Procedure
Step 2 Click the Route Member Port Management tab.
Step 3 Click New.
Step 4 Set the attributes of members in the static multicast group.
1. Set Service ID and VLAN ID.
2. Select the member ports from the drop-down list of Available Port. Click .
TIP
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.
3. Click OK.
----End
Related References
B.9.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group
Member Creation


If an Ethernet port is connected to only one host, you can set this Ethernet port as a quickly
deleted port.
Prerequisite

U2000
Procedure
Step 2 Click the Protocol Configuration tab.
Step 3 Click Add.
Step 4 Set the attributes of the quickly deleted port.
Step 5 Click Apply.
----End
Related References
B.9.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly
Deleted

By calculating IGMP packets, you can be familiar with the information about the IGMP packets
received and transmitted through the IGMP Snooping protocol.
Prerequisite
l Dynamic or static multicast member ports must be configured.

U2000

Procedure
Step 2 Click the Packet Statistics tab.
Step 3 Click Query.
Step 4 Calculate the IGMP packets.
----End
Related References
B.9.2.14 Parameter Description: IGMP Snooping Configuration_Data Statistics

By managing the QoS, you can provide the services of different levels for different service types.
A.12.10.1 Creating a DS Domain

By creating a DS domain, you can create the mapping relation of a new DS domain and configure
the ports that use this mapping relationship.
A.12.10.2 Modifying the DS Domain
This section describes how to change the mapping relationships in the created DS domain.
A.12.10.3 Changing the Ports That Use the DS Domain
This topic describes how to add or delete a port that uses the DS domain and set the packet type
over the port.
A.12.10.4 Creating a Port Policy
By creating a port policy, you can create a new port policy.
A.12.10.5 Modifying the Port Policy
This section describes how to change the parameter values of a created DS domain.
A.12.10.6 Creating the Traffic
By creating the traffic, you can configure ACL, CAR and shaping for a specified traffic stream
on a specified port.
A.12.10.7 Setting the Port That Uses the Port Policy
This section describes how to set the port that uses the port policy.
A.12.10.8 Configuring Port Shaping
This topic describes how to configure the traffic shaping for an egress port.
A.12.10.9 Querying the Port Policy
This topic describes how to query the port policy of a port.
A.12.10.10 Querying the DS Domain of a Port
This topic describes how to query the mapping relation between a port and a DS domain.

By creating a DS domain, you can create the mapping relation of a new DS domain and configure
the ports that use this mapping relationship.

Prerequisite
l The board of the Ethernet ports must be added on NE Panel.

U2000
The OptiX RTN 950 has a default DS domain, whose Mapping Relation ID is 1 and Mapping
Relation Name is default map. Before another DS domain is created, all the ports belong to this
default DS domain. The default DS domain cannot be modified or deleted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
Step 2 Click New.
The Create DS Mapping Relation dialog box is displayed.
Step 3 On the main interface, configure the attributes of the DS domain.
Step 4 Click the Ingress Mapping Relation tab.

Step 5 Configure the mapping relations between the priorities of ingress packets and PHB service
classes.
Step 6 Click the Egress Mapping Relation tab.
Step 7 Configure the mapping relations between the priorities of egress packets and PHB service
classes.
Step 8 Select Board where the application ports exist from Application Port.
Step 9 Select a port from Available Port, and then click .

TIP

Step 10 Click OK.
----End
Related References
B.9.4.2 Parameter Description: DiffServ Domain Management_Create
A.12.10.2 Modifying the DS Domain

This section describes how to change the mapping relationships in the created DS domain.
Prerequisite
l The DS domain must be created.

U2000

Procedure
Function Tree.
Step 2 Select the created DS domain and change its attributes on the main interface.
Step 3 Optional: Change the mapping relationship in the ingress direction.

1. Click the Ingress Mapping Relation tab.
2. Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the ingress direction.
3. Click Apply.
Step 4 Optional: Change the mapping relationship in the egress direction.

1. Click the Egress Mapping Relation tab.
2. Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the egress direction.
3. Click Apply.
Step 5 Click OK.
----End

This topic describes how to add or delete a port that uses the DS domain and set the packet type
over the port.
Prerequisite
l The DS domain must be created.

U2000

Procedure
Function Tree.
Step 2 Select the DS domain for which you need to add or delete an application port on the main
interface.
Step 3 Click the Apply Port tab.
Step 4 Click Modify.
Step 5 Add or delete a port that uses the DS domain.
Option Description
If ... Then ...
You need to add a port that uses the DS 1. Select the board where the application port is
domain located from the drop-down list of Board.
2. Select the port to be added from the drop-
down list of Available Port.
3. Click .
You need to delete a port that uses the DS 1. Select the board where the application port is
domain located from the drop-down list of Board.
2. Select the port to be deleted from the drop-
down list of Available Port.
3. Click .
You need to change the packet type Select a new packet type from the drop-down list
identified by the port of Packet Type.
TIP
Step 6 Click OK.
----End
Related References
B.9.4.3 Parameter Description: DiffServ Domain Applied Port_Modification

By creating a port policy, you can create a new port policy.
Prerequisite
l The board of the Ethernet ports must be added on NE Panel.


U2000
Procedure
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Create a port policy by adding a port policy on the NMS.

1. Click New. The Create Port Policy dialog box is displayed.
2. Set the ID and name of the port policy.
3. Configure the scheduling, weight, and shaping of the egress queues.
4. Click OK.
Step 3 Create a port policy by duplicating an existing port policy.

1. Select a similar port policy and click Copy.
Then, the Duplicate QoS Policy dialog box is displayed.
2. Change the name of the port policy.
3. Click OK.
4. Select the duplicated port policy and change the scheduling, weight, and shaping of the
egress queues.
5. Click Apply.
----End
Related References
B.9.4.5 Parameter Description: Port Policy
A.12.10.5 Modifying the Port Policy

This section describes how to change the parameter values of a created DS domain.
Prerequisite
l The port policy must be created.


U2000
Procedure
Step 2 Select the port policy whose parameter values need to be changed.
Step 3 Double-click the parameters whose values need to be changed and change the queue scheduling,
weight, and queue shaping of the port queues.
Step 4 Click Apply.
----End

By creating the traffic, you can configure ACL, CAR and shaping for a specified traffic stream
on a specified port.
Prerequisite
l The port policy must be created.

U2000
Procedure
Management > Policy Management from the Function Tree.
Step 2 Click the Traffic Classification Configuration tab.
Step 3 Click New. The Create Traffic Classification dialog box is displayed.
The Create Traffic Classification dialog box is displayed.
Step 4 Configure the attributes of a new traffic.

Step 5 Click OK.
Step 6 Click Apply.
----End
Related References
B.9.4.6 Parameter Description: Port Policy_Traffic Classification Configuration

This section describes how to set the port that uses the port policy.
Prerequisite
Tools, Instruments, and Materials

U2000
Procedure

Step 2 Click the Applied Object tab.
Step 3 Click Modify.

Then, the Configure Port dialog box is displayed.
Step 4 Set the port that uses the port policy.

1. Select Board where the port that needs to use the port policy from Applied Port.
2. Select a port from Available Port, and then click .

TIP
3. Click OK.
Step 5 Delete the port that uses the port policy.
1. Select the port to be deleted from Selected Port and click .

TIP

2. Click OK.
----End
Related References
B.9.4.4 Parameter Description: Policy Management

This topic describes how to configure the traffic shaping for an egress port.
Prerequisite
l The Ethernet board must be created on the NE Panel.

U2000
Procedure
Management > Port Shaping Management from the Function Tree.
Step 2 Click New.

The New dialog box is displayed.
Step 3 Set the parameters for the shaping of a port.
Step 4 Click OK.
----End
Related References
B.9.4.7 Parameter Description: Port Shaping Management_Creation

This topic describes how to query the port policy of a port.

Prerequisite

U2000
Procedure
Step 2 Click the CoS Queue Configuration tab.
Step 3 Click Query.
Step 4 Query the CoS configuration of the port policy.
Step 5 Click the Traffic Classification Configuration tab.
Step 6 Click Query.
Step 7 Query the traffic classification of the port policy.
Step 8 Click the Applied Object tab.
Step 9 Click Query.
Step 10 Query the ports that use the port policy.
----End
Related References

This topic describes how to query the mapping relation between a port and a DS domain.
Prerequisite

U2000

Procedure
Management > Diffserv Domain Management from the Function Tree.
Step 2 Click the Ingress Mapping Relation tab.
Step 3 Click Query.
Step 4 Query the attributes of the DS domain and the mapping relation between the priority level of
the packets in the ingress direction and the PHB service class.
Step 5 Click the Egress Mapping Relation tab.
Step 6 Click Query.
Step 7 Query the attributes of the DS domain and the mapping relation between the priority level of
the packets in the egress direction and the PHB service class.
Step 8 Click the Apply Port tab.
Step 9 Click Query.
Step 10 Query the ports that use the DS domain.
----End
Related References
B.9.4.1 Parameter Description: Diffserv Domain Management

By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.
A.12.11.1 Creating an MD
A maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of different
ranges and levels can provide users with differentiated OAM services.
A.12.11.2 Creating an MA
An MD can be divided into several independent maintenance associations (MAs). By creating
MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM
operations.
A.12.11.3 Creating an MEP Point
An MEP is the starting and end positions of all the OAM packets. By creating an MEP, you can
check the Ethernet channel of the MEPs that belong to a same MA through the OAM operation.
A.12.11.4 Creating Remote MEPs in an MA
To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the
same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
A.12.11.5 Creating an MIP
The maintenance association intermediate points (MIPs) can respond to specific OAM packets.
By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA into
several segments, thus facilitating the detection of the Ethernet link.
A.12.11.6 Performing a CC Test

After the continuity check (CC) test, the unidirectional link status can be checked automatically
and periodically. If the link is fault after the CC test is started at the source end, the sink equipment
reports the corresponding alarm.
A.12.11.7 Performing an LB Test
During a loopback (LB) test, you can check the bidirectional connectivity between the source
MEP and any MEP in the same maintenance association (MA).
A.12.11.8 Performing an LT Test
Based on the LB test, the link trace (LT) test further improves the capability to locate faults.
That is, the faulty network segment can be located according to the MIP through only one test.
A maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of different
ranges and levels can provide users with differentiated OAM services.
Prerequisite

U2000
Procedure
Step 2 Click the Maintenance Association tab.
Step 3 Choose New > New Maintenance Domain.

The system displays the New Maintenance Domain dialog box.
Step 4 Set the parameters of the MD.
----End
Related References
B.9.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain
Creation

An MD can be divided into several independent maintenance associations (MAs). By creating
MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM
operations.
Prerequisite
l The MD must be created.
l The Ethernet service must be created.

U2000
Procedure
Step 3 Select the maintenance domain in which a maintenance association needs to be created. Choose
New > New Maintenance Association.
The system displays the New Maintenance Association dialog box.
Step 4 Set the parameters of the MA.
NOTE
Click in Relevant Service. Select the corresponding services in the Select Service dialog box
that is displayed.
----End
Related References
B.9.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association
Creation

An MEP is the starting and end positions of all the OAM packets. By creating an MEP, you can
check the Ethernet channel of the MEPs that belong to a same MA through the OAM operation.

Prerequisite
l The MA must be created.

U2000
Procedure
Step 3 Select the maintenance association in which an MEP needs to be created. Choose New > New
MEP Point.
The system displays the New MEP Point dialog box.
Step 4 Set the parameters of the MEP point.
----End
Related References
B.9.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation

To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the
same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
Prerequisite


U2000
PORT 10 on the EFP8 board does not support this operation.
Procedure
Step 3 Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog
box is displayed.
Step 4 Click New.

Then, the Add Maintenance Association Remote Maintenance Point dialog box is displayed.
Step 5 Set the parameters of the new remote MEPs.
----End
Related References
B.9.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation

The maintenance association intermediate points (MIPs) can respond to specific OAM packets.
By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA into
several segments, thus facilitating the detection of the Ethernet link.
Prerequisite

U2000

Procedure
Step 2 Click the MIP Point tab.
Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New.
Then, the New MIP Maintenance Point dialog box is displayed.
Step 4 Set the parameters of the new MIP.
----End
Related References
B.9.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation

and periodically. If the link is fault after the CC test is started at the source end, the sink equipment
Prerequisite
l The MEP must be created.
l The remote MEPs must be created.

U2000
l Only the MEP can enable the CC test and function as the receiving and responding end in
the test.
l During the CC check, the source MEP constructs and transmits continuity check message
(CCM) packets periodically. After receiving the CCM packets from the source MEP, the
sink MEP directly enables the CC function for this source MEP. If the sink MEP fails to
receive the CCM packets from the source MEP within the check period (that is, 3.5 times
of the transmit period), it reports the alarm automatically.
l Performing a CC test does not affect the services.

Procedure
Step 3 Select the MEP where you need to perform the CC test and then choose OAM > Activate
CC.
Then, a dialog box is displayed, indicating that the operation is successful.
NOTE
l Before the CC test, you can set CC Test Transmit Period according to the actual requirements.
l To disable a CC test, select the MEP where the CC test is performed and then choose OAM >
Deactivate.
TIP
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC from
the shortcut menu.
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Deactivate CC
from the shortcut menu.
Step 4 Click Close.
----End

MEP and any MEP in the same maintenance association (MA).
Prerequisite
l The source and sink MEPs in the same maintenance domain must be created.
l The CC function must be enabled.

U2000
l Only MEPs can initiate the LB test and function as the receive end in the test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink 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.
l Performing a LB test does not affect the services.

Procedure
Step 3 Select the maintenance domain and maintenance association for the LB test.
Step 4 Choose OAM > Start LB.

Then, the LB Test dialog box is displayed.
TIP
To enable a LB test, you can also right-click an MEP and then choose Start LB from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LB
test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID.

l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address.
Step 6 Click Start Test. Then, the LB test result is displayed in the Detection Result window.
----End
Related References
B.9.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling

Based on the LB test, the link trace (LT) test further improves the capability to locate faults.
That is, the faulty network segment can be located according to the MIP through only one test.
Prerequisite
l The source and sink MEPs in the same MD must be created.
l The CC function must be enabled.

U2000

l Only MEPs can initiate the LT test and work as the termination point in the test.
l During the LT test, the source MEP constructs and transmits the 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 sink MEP.
l Performing a LT test does not affect the services.
Procedure
Step 3 Select the maintenance domain and maintenance association for the LT test.
Step 4 Choose OAM > Start LT.

Then, the LT Test dialog box is displayed.
TIP
To enable a LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LT
test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID.

l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address.
Step 6 Click Start Test. Then, the LT test result is displayed in the Detection Result window.
----End
Related References
B.9.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

By using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links.
A.12.12.1 Enabling the OAM Auto-Discovery Function
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.
A.12.12.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.
A.12.12.3 Modifying 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. Generally, the default value is used. You can modify the value according to the
situation of the link.
A.12.12.4 Performing 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.
A.12.12.5 Enabling Self-Loop Detection
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.

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

U2000
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 monitored according to the error
frame threshold. You can set the error frame threshold on the NMS.
NOTE
Procedure
OAM Management > Ethernet Port OAM Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the port, and set OAM Working Mode.

NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems, the
OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-discovery
fails.
l If the OAM modes of the two systems are both passive modes, a fault occurs on the line, or one system
fails to receive the OAM protocol message, an alarm is reported, indicating that the OAM auto-
discovery fails.

Step 4 Set Enable OAM Protocol to Enabled.
Step 5 Click Apply, and then close the displayed prompt dialog box.
Step 6 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the
opposite end, and then close the displayed prompt dialog box.
----End
Related References
B.9.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter

Prerequisite
l The OAM auto-discovery operation must successful on the equipment at both ends.

U2000
After the OAM auto-discovery operation is successful at both ends, the link fault detection and
performance detection are automatically started.
l To report the detected link fault event to the opposite equipment, you need to set Link
Event Notification to Enabled for the local equipment.
l To report the detected link fault event to the opposite equipment, you need to set Link
Event Notification to Enabled and set Error Frame Period Window (ms) and Error
Frame Monitor Threshold (frame) for the local equipment.
l After Link Event Notification is set to Enabled at the opposite port, if the opposite end
detects link performance degradation, you can query the ETH_EFM_EVENT alarm, which
is reported on the local end, by using the NMS. According to the alarm, you can determine
the type of the link performance event.
l After Link Event Notification is set to Enabled at the opposite port, if the opposite
equipment detects a link fault event, you can query the ETH_EFM_REMFAULT alarm,
which is reported at the local end, by using the NMS. According to the alarm, you can
determine the fault type.

NOTE
Procedure
Step 3 Select the corresponding port and set Link Event Notification to Enabled.
----End
Related References

Prerequisite
l The IEEE 802.3ah OAM function must be enabled on the remote equipment and the OAM
auto-discovery operation must be successful on the equipment at both ends.

U2000
After the OAM auto-discovery operation is successful, the remote link event notification
function is enabled and the monitoring time and errored frame threshold are set at the local end.
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 at the opposite
end, the opposite equipment can also inform the local equipment of the link event that is detected
at the opposite end. Then, the corresponding alarm is reported at the local end.
NOTE

Procedure
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
----End
Related References
B.9.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame
Monitoring
A.12.12.4 Performing Remote Loopback

Prerequisite
l The OAM auto-discovery operation must be successful at both ends of the link.
l On the equipment that initiates the loopback, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support the remote loopback.

U2000
l If a port is capable of responding to loopbacks, it enters the loopback responding state and
reports the loopback responding alarm after 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 loopback initiating state and reports the loopback initiating
alarm.
l Generally, after the remote loopback function is enabled, 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 need to 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.
NOTE
Procedure
Step 3 Select the port and set Remote Side Loopback Response to Enabled.
Step 5 Choose Enable Remote Loopback from the drop-down menu of OAM. Then, close the dialog
box that is displayed.
----End
A.12.12.5 Enabling Self-Loop Detection

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
l The required board is already added on the NE Panel.
l All the external physical ports on the Ethernet service processing board must be enabled.

U2000
l After the loopback detection is enabled at an Ethernet port, the ETHOAM_SELF_LOOP
alarm is reported if a loopback occurs at the port.
l On the EFP8 board, only PORT 10 supports this operation.

Procedure
Step 3 Set Loopback Check to Enabled.
----End

If a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automatically
disabled through the LPT function.
Prerequisite
l The corresponding board must be added to the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Step 2 Click New.
The Create LPT dialog box is displayed.

Step 3 Configure the board and port of the Convergence Point.

Step 4 Set Access Point.
1. In the Board list, select the board of the access point.
2. In Port, select the required port, and then click .

Step 5 Click OK.
----End
Related References
B.9.2.17 Parameter Description: LPT Management_Creation
A.13 Configuring Ethernet Services and Features on the

EoPDH Plane
Configurations of Ethernet services and features on the EoPDH plane include relevant Ethernet
port configuration, protection configuration, service configuration, protocol configuration, and
OAM configuration.
A.13.1 Managing LAGs

Link aggregation enables one or multiple links that are connected to the same equipment to be
aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC
layer. In this manner, bandwidth and availability of radio links are improved.
A.13.2 Configuring Ethernet Services

The EFP8 board supports EPL, EVPL, EPLAN, and EPVLAN services.
The MAC address table is the core of the Ethernet LAN service. The EFP8 board provides
various functions for managing the MAC address table.
A.13.4 Configuring Ethernet Ports
The EFP8 board supports external FE ports and internal VCTRUNK ports.
A.13.5 Managing the Spanning Tree Protocol
The OptiX RTN OptiX RTN 950 supports Spanning Tree Protocol (STP) and Rapid Spanning
Tree Protocol (RSTP).
A.13.6 Managing the IGMP Snooping Protocol
If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to
implement the multicast function together with the router.
By managing the QoS, you can provide differentiated services for different service types.
By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end
manner.
By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links.
A.13.10 Configuring LPT
After enabling the LPT function for an Ethernet service, you need to configure the LPT port and
the relevant information.
A.13.1 Managing LAGs

Link aggregation enables one or multiple links that are connected to the same equipment to be
aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC
layer. In this manner, bandwidth and availability of radio links are improved.
To improve bandwidth and availability of Ethernet links between two NEs, you need to create
the corresponding LAG.
The parameters for a LAG include port priorities and system priorities. In a static LAG that uses
the static aggregation mode, a port with a higher priority is always selected for transmitting
services.
A.13.1.3 Querying the Protocol Information of LAGs
This section describes how to learn about the running information of the LACP protocol used
by LAGs.

To improve bandwidth and availability of Ethernet links between two NEs, you need to create
the corresponding LAG.

Prerequisite
l The EFP8 board where the LAG ports are located must be added in the NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration >
Ethernet Interface Management > Ethernet Link Aggregation Management from the
Function Tree.
Step 3 Click New.
The Create Link Aggregation Group dialog box is displayed.
Step 4 In Attributes Settings, set the parameters of the LAG.
Step 5 In Port Settings, set the LAG ports.

1. Set Main Port.
2. Select a slave port from Available Slave Ports and then click .
TIP
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the ports.

Step 6 Click OK.

A confirmation dialog box is displayed.
Step 7 Click OK.
----End
Related References
B.10.2.10 Parameter Description: Ethernet Link Aggregation_Creation of LAGs

The parameters for a LAG include port priorities and system priorities. In a static LAG that uses
the static aggregation mode, a port with a higher priority is always selected for transmitting
services.
Prerequisite

U2000
Procedure
Function Tree.
Step 2 Click the Link Aggregation Parameters tab.
Step 3 Set the parameters associated with the system priority and port priority.

Step 4 Click Apply .
----End
Related References
A.13.1.3 Querying the Protocol Information of LAGs

This section describes how to learn about the running information of the LACP protocol used
by LAGs.
Prerequisite

U2000
Procedure
Function Tree.
Step 3 In the main interface, select the LAG to be queried.
Step 4 Click Query to check the working status of the main and slave ports in the LAG.

NOTE
The system automatically displays the working status of the slave port at the bottom of the main interface.
Step 5 Right-click the LAG and select an option from the drop-down list. A dialog box is displayed,
indicating the query result.
Step 6 Click Close.
Step 7 Click the Link Aggregation Parameters tab.
Step 8 Click Query to check the parameters associated with the port priority and system priority.
----End
A.13.2 Configuring Ethernet Services

The EFP8 board supports EPL, EVPL, EPLAN, and EPVLAN services.
A.13.2.1 Creating Ethernet Private Line Services

This section describes how to create EPL services and VLAN-based EVPL services.
A.13.2.2 Creating Ethernet LAN Services
This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE
802.1q bridge-based EVPLAN services.
A.13.2.3 Changing the Ports Connected to a VB
This section describes how to change the ports connected to a VB, the enabling status of the
ports, and Hub/Spoke attribute of the ports.
A.13.2.4 Creating the VLAN Filtering Table
To create an Ethernet LAN service in IVL learning mode, you need to create the VLAN filtering
table for the VB.
A.13.2.5 Creating QinQ-Based EVPL Services
When creating a QinQ-based EVPL service, you need to set service information such as the
service source, service sink, and QinQ type.
A.13.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services
To create EVPLAN services that are based on the IEEE 802.1ad bridge, you need to set relevant
service information, including the attributes of the bridge and the ports that are connected to the
bridge.
A.13.2.7 Deleting an Ethernet Private Line Service
When an Ethernet private line service is not used, you need to delete the Ethernet private line
service to release the corresponding resources.
A.13.2.8 Deleting an Ethernet LAN Service
When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to
release the corresponding resources.


This section describes how to create EPL services and VLAN-based EVPL services.
Prerequisite
l The EFP8 board must be added in the NE Panel.

U2000
Precautions
For the method of creating QinQ-based Ethernet private line services, see A.13.2.5 Creating
QinQ-Based EVPL Services.
Procedure
Ethernet Service > Ethernet Line Service from the Function Tree.
Step 2 Deselect Display QinQ Shared Service.
Step 3 Click New.
The Create Ethernet Line Service dialog box is displayed.
Step 4 Set the attributes of the Ethernet private line service.

Step 5 Set the port attributes.

NOTE
The result of setting the port attributes during the Ethernet private line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.
Step 6 Optional: Set the bound path.

1. Click Configuration.
The Bound Path Configuration dialog box is displayed. Set the attributes of the bound
path.

2. In Configurable Ports, select a VCTRUNK as the configurable port.

3. In Available Bound Paths, set Direction of the bound path.
4. Select required items in Available Resources and Available Timeslots and click
.
5. Optional: Repeat Step 6.4 to bind other VC paths.
6. Click OK.
7. Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the result
of directly setting the attributes of VCTRUNKs.
----End
Related References
B.10.1.1 Parameter Description: Ethernet Line Service_Creation
B.10.1.3 Parameter Description: Ethernet Line Service

This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE
802.1q bridge-based EVPLAN services.
Prerequisite


U2000
Precautions
For the method of creating the IEEE 802.1ad bridge, see A.13.2.6 Creating IEEE 802.1ad
Bridge-Based EVPLAN Services.
Procedure
Ethernet 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 IEEE 802.1q bridge.
l Set the attributes of the IEEE 802.1d bridge.

Step 4 Set the ports to be connected to 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 mount other ports.

4. Click OK.

path.

.

6. Click OK.
7. Click Yes.
NOTE
----End
Related References
B.10.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services
Based on IEEE 802.1d/802.1q Bridge
B.10.1.6 Parameter Description: Ethernet LAN Service
A.13.2.3 Changing the Ports Connected to a VB

This section describes how to change the ports connected to a VB, the enabling status of the
ports, and Hub/Spoke attribute of the ports.
Prerequisite
l Ethernet LAN services must be created.

U2000
Procedure
Step 2 Select the VB that is already created, and click the Service Mount tab.
Step 3 Change the ports connected to the VB.

1. To delete a mounted port, double-click the port under Mount Port and select
Unconnected from the drop-down list.
2. To add a mounted port, double-click the cell without any port under Mount Port and select
the port to be connected to the VB.
Step 4 To change any parameter value of a mounted port, double-click the parameter value and specify
a new value.
----End


To create an Ethernet LAN service in IVL learning mode, you need to create the VLAN filtering
table for the VB.
Prerequisite
l The IEEE 802.1q/802.1ad bridge-based Ethernet LAN services must be created.
l In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the
VB must be IVL.
Procedure
Step 2 Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
Step 3 Create the VLAN filtering 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.
----End
Related References
B.10.1.7 Parameter Description: VLAN Filtering Table_Creation


When creating a QinQ-based EVPL service, you need to set service information such as the
service source, service sink, and QinQ type.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8 board, and choose Configuration > Ethernet Service >
Ethernet Line Service from the Function Tree.
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.
The Create Ethernet Line Service dialog box is displayed.
Step 4 Set the attributes of the QinQ-based EVPL service.

Step 5 Optional: Set the port attributes.

NOTE
The result of setting the port attributes during the Ethernet private line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.

path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
Related References
B.10.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line
Services

To create EVPLAN services that are based on the IEEE 802.1ad bridge, you need to set relevant
service information, including the attributes of the bridge and the ports that are connected to the
bridge.
Prerequisite


U2000
Procedure
Step 2 Click New.

The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the IEEE 802.1ad bridge.
Step 4 Set service mounting relationships.

1. Click Configure Mount.
The Service Mount Configuration dialog box is displayed.
2. Set the parameters for configuring mounted services.
3. Click Add Mount Port.

4. Repeat Step 4.2 and Step 4.3 to add the other mounted ports.
5. Click OK.
6. Optional: You can change the Ethernet port attributes of the mounted ports in the Service
Mount window.

path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
Related References
B.10.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based
Ethernet LAN Service
A.13.2.7 Deleting an Ethernet Private Line Service

When an Ethernet private line service is not used, you need to delete the Ethernet private line
service to release the corresponding resources.
Prerequisite
l The Ethernet private line service must be configured and the service is not used.

U2000
Procedure
Step 2 Click Query.
Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete.
Step 4 Click Yes.
Step 5 Click Query. At this time, the Ethernet private line service is already deleted.
----End

A.13.2.8 Deleting an Ethernet LAN Service

When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to
release the corresponding resources.
Prerequisite
l The Ethernet LAN services must be configured and the service is not used.

U2000
Deleting an Ethernet LAN service involves the following tasks:
1. Deleting the VLAN filtering table
2. Deleting the service mounting configuration
Procedure
Step 2 Click Query.
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 Yes.
Step 6 Click the Service Mount tab.
Step 7 Select the Ethernet LAN service to be deleted and click Delete.
Step 8 Click Yes.
Step 9 Click Query. At this time, the Ethernet LAN service is already deleted.
----End

The MAC address table is the core of the Ethernet LAN service. The EFP8 board provides
various functions for managing the MAC address table.

By performing this operation, you can ensure that the hosts with specific MAC addresses are
not affected after the MAC addresses are aged and that Ethernet LAN services are also applicable
to the hosts only receiving and not transmitting packets.

A.13.3.2 Creating a Blacklist Entry of a MAC Address

By performing this operation, you can ensure that the hosts with specific MAC addresses cannot
use Ethernet LAN services.
A.13.3.3 Setting the Aging Time of a MAC Address Table Entry
The aging time of a MAC address table is five minutes by default.
This section describes how to query and delete self-learnt MAC addresses of Ethernet LAN
services.
A.13.3.5 Querying the Actual Capacity of a MAC Address Table
This section describes how to query the actual capacity of a MAC address table.

By performing this operation, you can ensure that the hosts with specific MAC addresses are
not affected after the MAC addresses are aged and that Ethernet LAN services are also applicable
to the hosts only receiving and not transmitting packets.
Prerequisite
l The Ethernet LAN services must be created.

U2000
Procedure
Step 2 Select the bridge that is already created, and click the VLAN Unicast tab.
Step 3 Click New.

The Create VLAN Unicast dialog box is displayed.
Step 4 Set the parameters of the unicast entries.
----End

A.13.3.2 Creating a Blacklist Entry of a MAC Address

By performing this operation, you can ensure that the hosts with specific MAC addresses cannot
use Ethernet LAN services.
Prerequisite

U2000
Procedure
Step 2 Select the created bridge and click the Disable MAC Address tab.
Step 3 Click New.

The Disable MAC Address Creation dialog box is displayed.
Step 4 Set the parameters of the disabled MAC address entries.
----End

The aging time of a MAC address table is five minutes by default.
Prerequisite

U2000

Procedure
Step 1 In the NE Explorer, select the EFP8 board, and 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 the EFP8 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
Related References
B.10.1.8 Parameter Description: Aging Time of MAC Address Table Entries

This section describes how to query and delete self-learnt MAC addresses of Ethernet LAN
services.
Prerequisite

U2000
Procedure
Step 2 Select the created bridge and click the Self-learning MAC Address tab.
Step 3 Click First Page, Previous Page, or Next Page to view the dynamic entries of a MAC address
table page by page.
Step 4 Optional: Select a MAC address to be deleted, and then click Clear MAC address. Then, close
the dialog box that is displayed.
----End
A.13.3.5 Querying the Actual Capacity of a MAC Address Table

This section describes how to query the actual capacity of a MAC address table.

Prerequisite

U2000
Precautions
l In the case of EVPLAN services, you can query the capacity of a MAC address table where
MAC addresses are queried based on VLAN IDs and the capacity of a MAC address table
where MAC addresses are queried based on VB logical ports.
l In the case of EPLAN services, you can query the capacity of a MAC address table where
MAC addresses are queried based on VB logical ports.
Procedure
Step 2 Select a created bridge.
Step 3 Query the actual number of dynamically learnt MAC addresses based on the VLAN IDs.
1. Click the VLAN MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of the
MAC address table.
Step 4 Query the actual number of dynamically learnt MAC addresses based on the VB ports.
1. Click the VB Port MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of the
MAC address table.
----End
A.13.4 Configuring Ethernet Ports

The EFP8 board supports external FE ports and internal VCTRUNK ports.
A.13.4.1 Configuring External Ethernet Ports

When an NE uses external ports on the EFP8 board to support access of Ethernet services, you
need to set the attributes of the external ports so that external ports can work with the data
communication equipment on the client side and therefore support normal access of Ethernet
services.
A.13.4.2 Configuring VCTRUNKs on an Ethernet Board
When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK)
on an Ethernet board, you need to set the attributes of the VCTRUNK so that the Ethernet board
works with the Ethernet board at the opposite end to implement transmission of the Ethernet
services on the network.
A.13.4.3 Modifying the Type Field of QinQ Frames

The default type field of QinQ frames is 0x8100.

A.13.4.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth
When the LCAS function is enabled on an NE, you can dynamically increase or decrease the
paths bound with a VCTRUNK to increase or decrease the bandwidth. The operation does not
affect services.

When an NE uses external ports on the EFP8 board to support access of Ethernet services, you
need to set the attributes of the external ports so that external ports can work with the data
communication equipment on the client side and therefore support normal access of Ethernet
services.
Prerequisite

U2000
Precautions
l Ethernet ports FE1-FE8 on the EFP8 board correspond to PORT1-PORT8 respectively.
l PORT9 on the EFP8 board is used to connect the EoPDH plane to the packet plane.
l PORT9 is provided by the Ethernet switching unit of the EFP8 board and is connected to
the EoPDH plane. PORT9 forwards the Ethernet services from the packet plane to FE ports
or VCTRUNKs on the EFP8 board.
Procedure
Step 1 In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet Interface
Step 2 Select External Port.
Step 3 Set the basic attributes of the port.

1. Click the Basic Attributes tab.
2. Set the basic attributes of the port.
3. Click Apply. Then, close the dialog box that is displayed.
Step 4 Set the flow control mode of the port.

1. Click the Flow Control tab.
2. Set the flow control mode of the port.

Step 5 Set the TAG attribute of the port.

1. Click the TAG Attributes tab.
2. Set the TAG attribute of the port.
Step 6 Set the network attributes of the port.

1. Click the Network Attributes tab.
2. Set the network attributes of the port.
Step 7 Set the advanced attributes of the port.

1. Click the Advanced Attributes tab.
2. Set the advanced attributes of the port.
----End
Related References
B.10.5.1 Parameter Description: Ethernet Port_External Port

When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK)
on an Ethernet board, you need to set the attributes of the VCTRUNK so that the Ethernet board
works with the Ethernet board at the opposite end to implement transmission of the Ethernet
services on the network.
Prerequisite

U2000
Precautions
The EFP8 board supports VCTRUNKs 1-16. VCTRUNKs 1-16 determine the services to be
transmitted depending on information about the created Ethernet services.

Procedure
Step 2 Select Internal Port.
Step 3 Optional: Set the TAG attribute of the VCTRUNK.
1. Click the TAG Attributes tab.
2. Set the TAG attribute of the VCTRUNK.

Step 4 Set the encapsulation and mapping protocol used by the VCTRUNK.
1. Click the Encapsulation/Mapping tab.
2. Set Mapping Protocol and the protocol parameters.

Step 5 Optional: Set the network attributes of the VCTRUNK.
1. Click the Network Attributes tab.
2. Set the network attributes of the VCTRUNK.

Step 6 Configure the LCAS function for the port.
1. Click the LCAS tab.
2. Set the Enabling LCAS parameter and other LCAS parameters.

path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
Related References
B.10.5.2 Parameter Description: Ethernet Port_Internal Port

The default type field of QinQ frames is 0x8100.
Prerequisite

U2000

Procedure
Advance Attribute > QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Step 3 Click Apply.
----End
Related References
B.10.5.3 Parameter Description: Type Field of QinQ Frames
A.13.4.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth

When the LCAS function is enabled on an NE, you can dynamically increase or decrease the
paths bound with a VCTRUNK to increase or decrease the bandwidth. The operation does not
affect services.
Prerequisite

U2000
Procedure
Step 2 Select Internal Port.
Step 3 Click the Bound Path tab.
Step 4 Click Configuration.

The Bound Path Configuration dialog box is displayed.
Step 5 Optional: Dynamically increase the VCTRUNK bandwidth.

2. In Available Bound Paths, set Level and Direction of the bound paths.


Step 6 Optional: Dynamically decrease the VCTRUNK bandwidth.
1. Deselect the Display in Combination check box.
2. Select the VC paths to be deleted in Selected Bound Paths, and then click .
3. Optional: Repeat Step 6.2 to delete other VC paths.
Step 7 Click OK.
Step 8 Click Yes.
----End
A.13.5 Managing the Spanning Tree Protocol

The OptiX RTN OptiX RTN 950 supports Spanning Tree Protocol (STP) and Rapid Spanning
Tree Protocol (RSTP).
A.13.5.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol
If a loop is formed in an Ethernet LAN service, you need to enable the STP or RSTP for the
bridge.
A.13.5.2 Setting the Parameters of Spanning Tree Protocol
If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters
of the STP or RSTP according to the requirements of the reachable data communications
equipment.
A.13.5.3 Querying the Running Information About the Spanning Tree Protocol
By performing this operation, you can learn the bridge running information and the port running
information when the bridge runs the spanning tree protocol.

If a loop is formed in an Ethernet LAN service, you need to enable the STP or RSTP for the
bridge.
Prerequisite

U2000
Procedure
Layer-2 Switching Management > Spanning Tree from the Function Tree.
Step 2 Click the Protocol Enabled tab.
Step 3 Set Protocol Enabled and Protocol Type.
Step 4 Click Apply.
----End
Related References
B.10.2.1 Parameter Description: Spanning Tree_Protocol Enabling

If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters
of the STP or RSTP according to the requirements of the reachable data communications
equipment.
Prerequisite

U2000

Procedure
Layer-2 Switching Management > Spanning Tree from the Function Tree.
Step 2 Set bridge parameters.
1. Click the Bridge Parameters tab.
2. Set bridge parameters.
3. Click Apply.
Step 3 Set port parameters.
1. Click the Port Parameters tab.
2. Set port parameters.
3. Click Apply.
Step 4 Optional: If Protocol Type is set to RSTP, specify the point-to-point attribute of the Ethernet
port.
1. Click the Point to Point Attribute tab.
2. Set the point-to-point attribute of the port.
3. Click Apply.
----End
Related References
B.10.2.2 Parameter Description: Spanning Tree_Bridge Parameters
B.10.2.3 Parameter Description: Spanning Tree_Port Parameters
B.10.2.6 Parameter Description: Spanning Tree_Point-to-Point Attribute
By performing this operation, you can learn the bridge running information and the port running
information when the bridge runs the spanning tree protocol.
Prerequisite

l The STP or RSTP must be enabled for the bridge.

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching
Management > Spanning Tree from the Function Tree.
Step 2 Query the bridge running information.

1. Click the Bridge Running Information tab.
2. Click Query.
3. Check the bridge running information.
Step 3 Query the port running information.

1. Click the Port Running Information tab.
2. Click Query.
3. Check the port running information.
----End
Related References
B.10.2.4 Parameter Description: Spanning Tree_Bridge Running Information
B.10.2.5 Parameter Description: Spanning Tree_Port Running Information
A.13.6 Managing the IGMP Snooping Protocol

If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to
implement the multicast function together with the router.

This section describes how to enable the IGMP Snooping protocol for a bridge and how to
configure the method for the bridge to process unknown multicast packets.
A.13.6.2 Configuring Static Multicast Entries
This section describes how to configure and query information about static multicast entries.
A.13.6.3 Modifying the Aging Time of a Multicast Table Entry
The aging time of a MAC address table is eight minutes by default.
A.13.6.4 Querying the Running Information of the IGMP Snooping Protocol
By performing this operation, you can learn the information about the multicast table entries and
router port when the bridge runs the IGMP Snooping protocol.

This section describes how to enable the IGMP Snooping protocol for a bridge and how to
configure the method for the bridge to process unknown multicast packets.

Prerequisite
l The VLAN filtering table must be created.

U2000
Procedure
Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Click the Enable IGMP Snooping Protocol tab.
Step 3 Set the information about the IGMP Snooping protocol.
Step 4 Click Apply.
----End
Related References
B.10.2.7 Parameter Description: IGMP Snooping Protocol_Enabling

This section describes how to configure and query information about static multicast entries.
Prerequisite
l The VLAN filtering table must be created.
l The IGMP Snooping protocol must be enabled for the bridge.

U2000
Procedure
Step 2 Click the Static Multicast Table tab.

Step 3 Click New.

The Create Static Multicast Item dialog box is displayed.
Step 4 Set the attributes of static multicast entries.

1. Set VB ID, VLAN ID, and MAC Address.
2. In Multicast Port, select the member ports corresponding to the static multicast entries.
Click .
TIP
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the ports.
3. Click OK.
----End
Related References
B.10.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table
Entries

The aging time of a MAC address table is eight minutes by default.
Prerequisite


U2000
Procedure
Step 2 Click the Multicast Aging Time tab.
Step 3 Modify the aging time of the multicast table entries.
Step 4 Click Apply.
----End
Related References
B.10.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table
Entries
A.13.6.4 Querying the Running Information of the IGMP Snooping Protocol

By performing this operation, you can learn the information about the multicast table entries and
router port when the bridge runs the IGMP Snooping protocol.
Prerequisite

U2000
Procedure
Step 2 Query the information about the router port.

1. Click the Multicast Router Port Management tab.
2. Click Query. Check the information about the router port.
Step 3 Query the information about the multicast table entries.

1. Click the Multicast Table Item tab.

2. Click Query. Check the information about the multicast table entries.
----End

By managing the QoS, you can provide differentiated services for different service types.
A.13.7.1 Creating a Flow

A flow refers to a collection of packets on which the same QoS operation is performed. Creating
a flow is the prerequisite for performing CAR and CoS operations.
A.13.7.2 Creating the 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 in the long term and in the short term). The CAR
allocates the packets whose rates do exceed the specified rate with higher priorities and discards
the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus
restricting the traffic into the transmission network.
A.13.7.3 Creating the 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.
A.13.7.4 Binding the CAR/CoS
To enable the CAR or CoS function, you need to bind the corresponding flow to the created
CAR/CoS.
A.13.7.5 Configuring Traffic Shaping for Egress Queues
This section describes how to enable traffic shaping for egress queues and how to set shaping-
associated parameters.

A flow refers to a collection of packets on which the same QoS operation is performed. Creating
a flow is the prerequisite for performing CAR and CoS operations.
Prerequisite
l The associated Ethernet services must be created.

U2000
Procedure
QoS Management > Flow Management from the Function Tree.
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
Related References
B.10.4.1 Parameter Description: QoS Management_Creation of Flows

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 in the long term and in the short term). The CAR
allocates the packets whose rates do exceed the specified rate with higher priorities and discards
the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus
restricting the traffic into the transmission network.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8 board, and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the CAR Configuration.
Step 3 Click New.

The New CAR dialog box is displayed.
Step 4 Set the CAR parameters.

Step 5 Click OK.
----End
Related References
B.10.4.2 Parameter Description: QoS Management_Creation of CAR

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.
Prerequisite

U2000
Procedure
QoS Management > Flow Management from the Function Tree.
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
Related References
B.10.4.3 Parameter Description: QoS Management_Creation of CoS

To enable the CAR or CoS function, you need to bind the corresponding flow to the created
CAR/CoS.
Prerequisite
l The flow must be created.
l The CAR/CoS must be created.

U2000
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose
Configuration > QoS Management > Flow Management from the Function Tree.
Step 2 Click the Flow Configuration tab.

Step 3 Double-click Bound CAR and select the CAR to be bound.

Step 4 Double-click Bound CoS and select the CoS to be bound.
Step 5 Click Apply.
----End
Related References
B.10.4.4 Parameter Description: QoS Management_Creation of CAR/CoS

This section describes how to enable traffic shaping for egress queues and how to set shaping-
associated parameters.
Prerequisite

U2000
Procedure
QoS Management > Port Shaping Management from the Function Tree.
Step 2 In Port List, select a port. In Port Queue Shaping Information, set the traffic shaping
information about the egress queues.
Step 3 Click Apply.
----End
Related References
B.10.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues

By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end
manner.
A.13.8.1 Creating MDs

A maintenance domain (MD) defines the scope and level of the 802.1ag OAM. The MDs of
different levels and scopes can provide differentiated OAM services to users.
A.13.8.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.
A.13.8.3 Creating MPs
MPs refer to function entities of IEEE 802.1ag OAM, including MEPs and MIPs. The functions
of the IEEE 802.1ag OAM can be used only after MPs are created.
and periodically. If the link is fault after the CC test is started at the source, the source equipment
MEP and any MP in the same maintenance association (MA).
Based on the LB test, the linktrace (LT) test further improves the capability to locate faults. That
is, the faulty network segment can be located through only one test.
A.13.8.7 Activating the AIS
After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a
higher level MP so that the higher level MP is informed of the fault information.
A.13.8.8 Performing a Ping Test
In a ping test, the ARP and ICMP Layer 3 protocol packets are used to test the connectivity,
packet loss ratio, and delay of the service between the Ethernet service processing board and the
data communication equipment (such as a switch or a router).
A.13.8.9 Performing Performance Check
A performance check achieves on-line detection of the packet loss ratio and delay of the service
based on the check of the connectivity between the MPs on the Ethernet service processing
board.

A maintenance domain (MD) defines the scope and level of the 802.1ag OAM. The MDs of
different levels and scopes can provide differentiated OAM services to users.
Prerequisite

U2000

Procedure
Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 In the right pane, click OAM Configuration.
The OAM Configuration dialog box is displayed.
NOTE
In this GUI interface, you can maintain or delete OAM MDs.
Step 3 Click New and choose Create MD from the drop-down list.
The Create MD dialog box is displayed.
Step 4 Set the parameters of the new MD.
Step 5 Click OK.
----End
Related References
B.10.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs

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

l The MD must be created.

U2000
Procedure
Step 2 In the right pane, click OAM Configuration.

The OAM Configuration dialog box is displayed.
NOTE
In this GUI interface, you can maintain or delete OAM MAs.
Step 3 Click New and choose Create MA from the drop-down list.
1. The Create MA dialog box is displayed.
Step 4 Set the parameters of the new MA.
Step 5 Click OK.
----End
Related References
B.10.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs

MPs refer to function entities of IEEE 802.1ag OAM, including MEPs and MIPs. The functions
of the IEEE 802.1ag OAM can be used only after MPs are created.
Prerequisite
l The Ethernet services must be created and activated.
l The MD and MA must be created.


U2000
Precautions
In an OAM test, all MPs that are involved in the operation of the same service flow must be in
the same MD. In an existing MD involved in the same service flow, creating an MP of the same
level or a higher level may damage the existing MD. As a result, the OAM test fails.
Procedure
Step 2 Click New.
The Create MP dialog box is displayed.
Step 3 Set the parameters of the new MP.
Step 4 Optional: Click Advanced. In the dialog box that is displayed, set the corresponding parameters
and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configurations:
l Activate the CC and set the sending period of the CC test.
l Set the timeout time for the LB or LT test.
Step 5 Click OK.
----End
Related References
B.10.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs


and periodically. If the link is fault after the CC test is started at the source, the source equipment
Prerequisite
l The Ethernet services must be created and activated.
l The MD and MA must be created.
l The MEPs must be created.

U2000
l Only the MEP can enable the continuity test and function as the receive respond end for
the test.
l The source MEP constructs CCM packets and transmits them periodically. After receiving
the CCM packet from the source MEP, the sink MEP directly enables the CC function for
this source MEP. If the sink MEP fails to receive the CCM packet from the source MEP
within the check period (that is, 3.5 times of the transmission interval), it reports the specific
alarm automatically.
l Performing a CC test does not affect the services.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Activate CC.
NOTE
l Before the CC test, you can set CCM Sending Period(ms) according to the actual requirements.
l To disable a CC test, right-click the MEP where the CC test is performed and then choose Activate
CC from the shortcut menu.
TIP
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC from
the shortcut menu.
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Inactivate CC
from the shortcut menu.
----End

MEP and any MP in the same maintenance association (MA).

Prerequisite
l In the case of a standard MP, you must activate CC before an LB test.

U2000
l Only an MEP can initiate an LB test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink 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.
l Performing an LB test does not affect the services.
Procedure
Step 2 Select the node that requires an LB test, click OAM Operation, and select Start LB.
The LB Test dialog box is displayed.
Step 3 Set the parameters involved in the LB test.

NOTE
l In the case of standard MPs, when an MIP functions as the receive end in the LB test, you need to select
Test based on the MAC Address and set LB Sink MP MAC Address.
l Before the LB test, you can set LB Timeout(ms) according to the actual requirements.
Step 4 Click Start LB. Then, the test result is displayed.

TIP
To enable an LB test, you can also right-click an MEP and then choose Start LB from the shortcut menu.
----End
Related References
B.10.3.4 Parameter Description: Ethernet Service OAM_Enabling LB


Based on the LB test, the linktrace (LT) test further improves the capability to locate faults. That
is, the faulty network segment can be located through only one test.
Prerequisite
l In the case of a standard MP, you must activate CC before an LT test.

U2000
l Only an MEP can initiate the LT test, and the MEP can work as the receive end in the test.
l During the LT test, the source MEP constructs and transmits the 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 sink MEP.
l Performing an LT test does not affect the services.
Procedure
Step 2 Select the node that requires an LT test, click OAM Operation, and select Start LT.
Step 3 Set the parameters involved in the LT test.
NOTE
Before the test, you can set LT Timeout(ms) according to the actual requirements.
Step 4 Click Start LT. Then, the test result is displayed.

TIP
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
----End
Related References
B.10.3.5 Parameter Description: Ethernet Service OAM_Enabling LT

A.13.8.7 Activating the AIS

After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a
higher level MP so that the higher level MP is informed of the fault information.
Prerequisite
l Only a standard MP supports this function.

U2000
Procedure
Step 2 Select the node to be monitored. Double-click or right-click AIS Active State and then select
Active or Inactive.
Step 3 Click Apply.
----End
A.13.8.8 Performing a Ping Test

In a ping test, the ARP and ICMP Layer 3 protocol packets are used to test the connectivity,
packet loss ratio, and delay of the service between the Ethernet service processing board and the
data communication equipment (such as a switch or a router).
Prerequisite
l You must be aware of the IP addresses of the source MP and the sink MP in the ping test.

U2000
The source end of the ping test obtains the IP addresses of the source MP and sink MP, and
constructs and sends ARP packets and ICMP packets. The MP that receives the ARP packets or
ICMP packets parses the packets, and responds to the source end. After receiving the response

packet, the source end reports the ping test result to the NE software (including the ratio of packet
loss and time delay) based on the response packet.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Start Ping.
The Ping Test dialog box is displayed.
Step 3 Select Send Mode. Then, set Packet Length, Timeout, and Ping Attempts for the ping packet.
Step 4 Set Destination IP Address and Local IP Address.
Step 5 Click Start Ping. Then, the test result is displayed.
----End
A.13.8.9 Performing Performance Check

A performance check achieves on-line detection of the packet loss ratio and delay of the service
based on the check of the connectivity between the MPs on the Ethernet service processing
board.
Prerequisite

U2000
The performance check method provides an in-service test of packet loss ratio and delay based
on the check of the connectivity between the MPs on the Ethernet service processing unit.
A performance check is implemented as follows: The source MP initiates several LB tests and
counts different packet loss ratio and delay values.

Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Performance Detect.
The Performance Detect dialog box is displayed.
Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Detect Attempts for the test packet.
Step 4 Set Source MP ID and Destination MP ID.
Step 5 Click Start Detect. Then, the check result is displayed.
----End

By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links.

The IEEE 802.3ah OAM is achieved based on the OAM auto-discovery function. After the OAM
auto-discovery succeeds, the equipment automatically monitors the faults and performance of
the link.
A.13.9.4 Performing the Remote Loopback

The IEEE 802.3ah OAM is achieved based on the OAM auto-discovery function. After the OAM
auto-discovery succeeds, the equipment automatically monitors the faults and performance of
the link.
Prerequisite

U2000
The OAM auto-discovery is achieved based on auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After

OAM auto-discovery is successful, the link performance is monitored according to the error
frame threshold. You can set the error frame threshold on the NMS.
Procedure
Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
Step 3 Select the port and set OAM Working Mode.
NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems, the
OAM mode of either or both systems must be the active mode. Otherwise, OAM auto-discovery fails.
l If the OAM modes of the two systems are passive modes, if a fault occurs on the link, or if one system
fails to receive the OAM protocol message within five consecutive seconds, an alarm is reported,
indicating that OAM auto-discovery fails.
Step 4 Select Enabled from the Enable OAM Protocol drop-down list.
Step 5 Click Apply.

Step 6 Click the Remote OAM Parameter tab. Click Query to check the OAM capability of the
opposite end.
----End
Related References
B.10.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter

Prerequisite
l The OAM auto-discovery operation must be successful on the equipment at both ends.

U2000

After the OAM auto-discovery operation is successful at both 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, you need to set Remote
Alarm Support for Link Event to Enabled and set Error Frame Period Window
(Frame) and Error Frame Monitor Threshold for the local equipment.
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 ETH_RMT_SD
alarm , which is reported on the local end, by using the NMS. According to 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 NMS.
Based on the alarm, you can determine the fault type.
Procedure
Step 3 Select the corresponding port and set Remote Alarm Support for Link Event to Enabled.
Step 4 Click Apply.
----End
Related References
B.10.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter

Prerequisite
l The IEEE 802.3ah OAM function must be enabled on the remote equipment and the OAM
auto-discovery operation must be successful on the equipment at both ends.


U2000
After the OAM auto-discovery operation is successful, 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 at the opposite end, the opposite equipment can also inform the
local equipment of the link event that is detected at the opposite end. Then, the corresponding
alarm is reported at the local end.
Procedure
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
Step 4 Click Apply.
----End
Related References
B.10.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring
A.13.9.4 Performing the Remote Loopback

Prerequisite
l The OAM auto-discovery operation must be successful on the equipment at both ends.
l On the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support remote loopbacks.

U2000

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 loopback initiating state and reports the
loopback initiating alarm.
l Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU packets, are looped back at the remote end.
l After using the remote loopback function to locate faults and test link performance, 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 clears automatically.
Procedure
Step 3 Choose Enable Remote Loopback from the OAM drop-down menu. Then, close the dialog
box that is displayed.
----End
A.13.10 Configuring LPT

After enabling the LPT function for an Ethernet service, you need to configure the LPT port and
the relevant information.
A.13.10.1 Configuring LPT for Point-to-Point Services

When a point-to-point service uses the LPT function, you need to set LPT parameters both in
the positive and reverse directions.
A.13.10.2 Configuring LPT for Point-to-Multipoint Services
To configure LPT for point-to-multipoint services, you need to specify the corresponding
relationships between aggregation ports and access ports and LPT parameters.

When a point-to-point service uses the LPT function, you need to set LPT parameters both in
the positive and reverse directions.
Prerequisite
l The PORT-based Ethernet private line services must be created and activated.

l The data services must be configured as EPL services that are transmitted from PORTs to
VCTRUNKs and do not carry any VLAN tags.
l An Ethernet port on which the LPT function is enabled must be in auto-negotiation mode.

U2000
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select
only one configuration mode to implement the LPT function.
Procedure
Ethernet Interface Management > LPT Management from the Function Tree.
Step 2 Click Query.
Step 3 Select a PORT and a VCTRUNK, and then set the following parameters.
NOTE
If LPT is enabled, you can set PORT-Type Port Hold-Off Time(ms) and VCTRUNK Port Hold-Off
Time(ms) according to actual requirements.
Step 4 Click Apply.
----End
Related References
B.10.2.12 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT

To configure LPT for point-to-multipoint services, you need to specify the corresponding
relationships between aggregation ports and access ports and LPT parameters.
Prerequisite
l The VLAN-based EVPL services must be created and activated.

l An Ethernet port on which the LPT function is enabled must be in auto-negotiation mode.

U2000
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select
only one configuration mode to implement the LPT function.
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 the topology of the LPT.
Procedure
Ethernet Interface Management > LPT Management from the Function Tree.
Step 2 Click PtoMP LPT. Then, the LPT Management dialog box appears.
Step 3 Click New.
The Create LPT dialog box is displayed.

Step 4 Set the parameters in Convergence Point.

Step 5 Set the parameters in Access Point.
1. Select the ports from Port and then click .

2. If you select a VCTRUNK, set Bearer Mode.
Step 6 Click OK.
----End
Related References
B.10.2.13 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service
LPT
A.14 Using the RMON

The remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment
or on the entire network. Currently, it is one of the widely used network management standards.
A.14.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.
A.14.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.
A.14.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. A maximum of 50 historical
performance entries can be saved.
A.14.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.
A.14.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
l The corresponding board must be added in the NE Panel.

U2000
Procedure
Performance > RMON Performance from the Function Tree.
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
Related References
B.8.1 Parameter Description: RMON Performance_Statistics Group

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
l The corresponding boards must be added in the NE Panel.


U2000
Procedure
Step 2 Click the RMON Setting tab.
Step 3 Click the Object tab and set the corresponding parameters.
Step 4 Click the Event tab and set the corresponding parameters.
----End
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting

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. A maximum of 50 historical
performance entries can be saved.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History
Control Group.
Step 2 Set the parameters of the history control group.
----End
Related References
B.8.3 Parameter Description: RMON Performance_History Control Group

A.14.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
l The objects and performance events to be monitored must be set.

U2000
Procedure
Step 2 Click the History Group tab.
Step 3 Set the parameters of the history group.
Step 4 Click Apply.
----End
Related References
A.15 Setting the Parameters of ODU Ports

This section describes how to configure the parameters of ODU ports, including the transmit
frequency attribute, power attribute, ODU attribute, and advanced attributes.
A.15.1 Setting the Transmit Frequency Attribute of the ODU

The transmit frequency attribute of the ODU is used to configure the transmit frequency of the
ODU and T/R spacing.
A.15.2 Querying the ODU Attribute
The ODU attribute is used to query the information about the ODU.
A.15.3 Setting the Power Attributes of the ODU
The power attribute of the ODU is used to configure the transmit power and receive power of
the ODU.
A.15.4 Setting the Advanced Attributes of the ODU
The advanced attributes of the ODU are used to configure the transmit status of the ODU.
A.15.5 Setting the State of an ODU Transmitter
The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the
unmute state, the ODU transmits and receives microwave signals normally. When the ODU

transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive
microwave signals.

The transmit frequency attribute of the ODU is used to configure the transmit frequency of the
ODU and T/R spacing.
Prerequisite
NE Panel.

U2000
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
Step 2 Click the Radio Frequency Attributes tab.
Step 3 Configure Transmit Frequency(MHz) and T/R Spacing(MHz) of the ODU.
Step 4 Click Apply.
----End
Related References
B.12.7 Parameter Description: ODU Interface_Radio Frequency Attribute

The ODU attribute is used to query the information about the ODU.
Prerequisite
NE Panel.

U2000

Procedure
Configuration > ODU Interface from the Function Tree.
Step 2 Click the Equipment Information tab.
Step 3 Click Query to obtain the information about the ODU.
----End
Related References
B.12.9 Parameter Description: ODU Interface_Equipment Information

The power attribute of the ODU is used to configure the transmit power and receive power of
the ODU.
Prerequisite
l The related IF board must be added.

U2000
Procedure
Step 2 Click the Power Attributes tab.
Step 3 Configure the power attribute parameters of the ODU.
Step 4 Click Apply.
----End
Related References
B.12.8 Parameter Description: ODU Interface_Power Attributes

The advanced attributes of the ODU are used to configure the transmit status of the ODU.

Prerequisite
NE Panel.

U2000
Procedure
Step 3 Configure the parameters of the ODU, such as Configure Transmission Status.
Step 4 Click Apply.
----End
Related References
B.12.10 Parameter Description: ODU Interface_Advanced Attributes
A.15.5 Setting the State of an ODU Transmitter

The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the
unmute state, the ODU transmits and receives microwave signals normally. When the ODU
transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive
microwave signals.
Prerequisite
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.

U2000
Procedure
Step 3 Set Configure Transmission Status for the ODU.

Step 4 Click Apply.
----End

The parameters of SDH ports are used to configure the loopback on the SDH interface bboard
and the laser status.
Prerequisite

U2000
Procedure
Configuration > SDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Step 3 Set the parameters of SDH ports.

1. Choose Port from the drop-down list, and then configure the parameters of SDH ports.
Click Apply.
2. Click OK.
The dialog box is displayed again for confirmation.
3. Click OK, and then close the dialog box that is displayed indicating the operation result.
Step 4 Set the parameters of VC-4 paths.

1. Choose VC4 Channel from the drop-down list, and then configure the parameters of VC-4
paths. Click Apply.
2. Click OK.
A dialog box is displayed again for confirmation.
----End
Related References
B.12.11 Parameter Description: SDH Interfaces


The parameters of PDH ports are used to configure the tributary loopback, service load
indication, and tributary retiming.
Prerequisite

U2000
Procedure
Configuration > PDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel).
Step 3 Select Port from the list box.
Step 4 Configure the parameters of PDH ports.
Step 5 Click Apply, and then close the dialog box that is displayed indicating the operation result.
----End
Related References
B.12.13 Parameter Description: PDH Interfaces
A.18 Configuring Overhead Bytes

Generally, the default overload bytes can meet the requirements of the device. In certain special
application scenarios, however, such as device interconnection, you need to change the overload
bytes according to the requirements of the interconnected device.
A.18.1 Configuring RSOHs
When the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte in
regenerator section overheads (RSOHs).
A.18.2 Configuring VC-4 POHs
When the HP_TIM or HP_SLM alarm is reported by the line board of the local or peer NE, you
need to configure the J1 or C2 byte in VC-4 path overheads (POHs).
When the E1 port board of the local or remote NE reports the LP_TIM or LP_SLM alarm, you
need to configure the signal flag in the J2 or V5 byte in VC-12 path overheads (POHs).


When the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte in
regenerator section overheads (RSOHs).
Prerequisite
Procedure
Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
Step 2 Configure the J0 byte.

1. Double-click the parameter whose value needs to be changed.
The Please input the overhead byte dialog box is displayed.
2. Configure overhead bytes.
3. Click OK.
Step 3 Click Apply.

----End
Related References
B.13.1 Parameter Description: Regenerator Section Overhead


When the HP_TIM or HP_SLM alarm is reported by the line board of the local or peer NE, you
need to configure the J1 or C2 byte in VC-4 path overheads (POHs).
Prerequisite
Procedure
Step 1 Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration >
Overhead Management > VC4 Path Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Optional: Configure the J1 byte.

1. Click the Trace Byte J1 tab.
The Please Input Overhead Byte dialog box is displayed.
4. Click OK.
5. Click Apply.
Step 4 Optional: Configure the C2 byte.

1. Click the Signal Flag C2 tab.
2. Configure the required parameters.
3. Click Apply.
4. Click OK. Close the dialog box that is displayed indicating the operation result.
Step 5 Configure the termination mode of the VC-4 overhead.

1. Click the Overhead Termination tab.
2. Configure VC4 Overhead Termination.
3. Click Apply.
----End
Related References
B.13.2 Parameter Description: VC-4 POHs


When the E1 port board of the local or remote NE reports the LP_TIM or LP_SLM alarm, you
need to configure the signal flag in the J2 or V5 byte in VC-12 path overheads (POHs).
Prerequisite
Procedure
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.
Step 2 Configure the J2 byte.
1. Click the Trace Byte J2 tab.
The Please input the overhead byte dialog box is displayed.
4. Click OK.
5. Click Apply.
6. Click OK, and then close the dialog box that is displayed.
Step 3 Configure the signal flag.
1. Click the Signal Flag tab.
2. Click Options.
The Options dialog box is displayed.
3. Click Extended Mode.
4. Click OK.

5. Configure the signal flag in the V5 byte.
6. Click Apply.
7. Click OK, and then close the dialog box that is displayed.
----End
Related References
A.19 Configuring Auxiliary Ports and Functions

The auxiliary ports and functions supported by the OptiX RTN 950 include the orderwire,
synchronous data service, asynchronous data service, wayside E1 service, and external alarm.
A.19.1 Configuring the Orderwire

The orderwire for an NE provides a dedicated communication channel that the network
maintenance personnel can use.
A.19.2 Configuring the Synchronous Data Service
The OptiX RTN 950 supports the transmission of a channel of 64-kbit/s synchronous data service
through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N
frame. Such a service is also called F1 data port service.
A.19.3 Configuring the Asynchronous Data Service
The OptiX RTN 950 supports the transmission of a channel of asynchronous data service with
a maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any byte
within the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also called
broadcast data port service.
A.19.4 Configuring the Wayside E1 Service
The OptiX RTN 950 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service
through 32 user-defined bytes in the SDH microwave frame.
A.19.5 Configure External Alarms
After the outputting of external alarms is configured, the alarm information of the OptiX RTN
950 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 950.

The orderwire for an NE provides a dedicated communication channel that the network
maintenance personnel can use.
Prerequisite


U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
Step 2 Click the General tab.
Step 3 Configure the orderwire information.
Step 4 Click Apply.
Step 5 Optional: Change the overhead bytes occupied by the orderwire.

1. Click the Advanced tab.
2. Configure Orderwire Occupied Bytes.
3. Click Apply.
----End
Related References
B.11.1 Parameter Description: Orderwire_General
B.11.2 Parameter Description: Orderwire_Advanced

The OptiX RTN 950 supports the transmission of a channel of 64-kbit/s synchronous data service
through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N
frame. Such a service is also called F1 data port service.

Prerequisite
l The board involved in the synchronous data service must be configured.

U2000
Procedure
Step 2 Click the F1 Data Port tab.
Step 3 Hold on the Ctrl key, select two data channels from Available Data Path, and then click
Step 4 Click Apply.
----End
Related References
B.11.3 Parameter Description: Orderwire_F1 Data Port

The OptiX RTN 950 supports the transmission of a channel of asynchronous data service with
a maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any byte
within the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also called
broadcast data port service.
Prerequisite
l The board involved in the asynchronous data service must be configured.


U2000
Procedure
Step 2 Click the Broadcast Data Port tab.
Step 3 Configure the parameters of the broadcast data port.
Step 4 Click Apply.
----End
Related References
B.11.4 Parameter Description: Orderwire_Broadcast Data Port

The OptiX RTN 950 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service
through 32 user-defined bytes in the SDH microwave frame.
Prerequisite
l The IF1 board must be added on the NE Panel.
l The DCC channels corresponding to external clocks must be disabled.

U2000

The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM,
8,E3,28MHz,QPSK, or 9,E3,14MHz,16QAM mode.
Procedure
Step 2 Click the IF Attributes tab.
Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.
Step 4 Click Apply.
----End
Related References

After the outputting of external alarms is configured, the alarm information of the OptiX RTN
950 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 950.
Prerequisite
l The AUX board must be added on the NE Panel.

U2000
Context
The external alarms of the OptiX RTN 950 are also considered as housekeeping alarms. The
external alarm port of the OptiX RTN 950 is a relay port. This port can be either in the "on" state
or in the "off" state.
The OptiX RTN 950 provides two alarm output ports and four alarm input ports. 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 AUX board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the Function
Tree.
Step 2 Configure the input alarm.
1. Select Input Relay from the drop-down list.
2. Configure the parameters of the input alarm.
Step 3 Configure the output alarm.
1. Select Output Relay from the drop-down list.
2. Configure the parameters of the output alarm.
----End
Related References
B.11.5 Parameter Description: Environment Monitoring Interface
A.20 Testing the Protection Switching

By testing the protection switching, you can check whether the protection switching is normal
over radio links.
A.20.1 Testing the IF 1+1 Switching

You can verify whether the IF 1+1 protection works normally by checking the working board
of the IF 1+1 protection group before and after the switching.
A.20.2 Testing the N+1 Protection Switching
You can verify whether the IF N+1 protection works normally by checking the working board
of the IF N+1 protection group before and after the switching.
A.20.3 Testing the SNCP Switching
You can verify whether the SNCP works normally by checking the working port of the SNCP
protection group before and after the switching.
A.20.4 Testing the ERPS
You can verify whether the ERPS works normally by checking the port status of the ERPS
A.20.5 Testing the Linear MSP Switching

You can verify whether the linear MSP group works normally by checking the working port of
the linear MSP group before and after the switching.
A.20.1 Testing the IF 1+1 Switching

You can verify whether the IF 1+1 protection works normally by checking the working board
of the IF 1+1 protection group before and after the switching.
Prerequisite
l Aligning the antennas is complete.
l The equipment is configured with the IF 1+1 protection.
l The E1 service is configured.

l U2000
l BER tester
Figure A-2 Configuration for testing the IF 1+1 switching
NE A and NE B are configured as follows:

l Main IF board: IFU2 in slot 3
l Standby IF board: IFU2 in slot 5
l Main ODU: ODU in slot 23
l Standby ODU: ODU in slot 25
NE A NE B
As shown in Figure A-2, the following procedures consider the E1 service between NE A and
NE B that is configured with the 1+1 HSB protection as an example.
NOTE
l If Working Mode of the IF 1+1 protection is set to HSB, TX Status should be set to mute for the ODU on
the main channel of NE A, and Enable Reverse Switching should be set to Disable. The switching occurs
at NE A.
l If Working Mode of the IF 1+1 protection is set to SD, TX Status should be set to mute for the ODU on
the main channel of NE A, and Enable Reverse Switching should be set to Enable. The switching occurs
at NE A.
l If Working Mode of the IF 1+1 protection is set to FD, TX Status should be set to mute for the ODU on
the main channel of NE B. The switching occurs at NE A.

Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Board of Device or Active Board
of Channel in Protection Group when the protection switching occurs and after the protection switching is
complete.
Procedure
Step 1 Check whether a BER tester is available at the central site.
If... Then...
A BER tester is available on site Perform Step 2 to Step 11.
No BER tester is available on site Perform Step 6 to Step 10.
Step 2 At the central site NE A, connect one E1 port to the BER tester.
Step 3 At the remote site NE B, perform a software inloop at the E1 port by using the NMS.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
Step 4 Test the BER by using the BER tester.
The BER tester should show that no bit errors occur.
Step 5 Set Enable Reverse Switching in the 1+1 HSB protection group for NE A.
1. Select the required NE from the Object Tree in the NE Explorer of NE A, and then choose
Configuration > IF 1+1 Protection from the Function Tree.
2. Select the corresponding protection group in Protection Group, and set Enable Reverse
Switching to Enable.
3. Click Apply.
Step 6 Before the switching, query the status of the protection group that is configured on NE A.
1. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose
2. Select the corresponding protection group in Protection Group, and then click Query.
3. In Protection Group, the value of Active Board of Device should be the main IF board
3-IFU2.

Step 7 Set TX Status to Unmute for the main ODU 23-ODU of NE A.

Configuration > Link Configuration from the Function Tree.
2. Click the IF/ODU Configuration tab.
3. Select the required ODU, and set TX Status to mute.
4. Click Apply.
Step 8 Check the availability of the service after the switching.
If... Then...
A BER tester is available on site Check the test result on the BER tester. It
should show that the service is restored after a
transient interruption.
No BER tester is available on site, and the See A.10.11 Testing the E1 Service Through
E1 service is transmitted on the radio link. PRBS to test the availability of the E1 service.
No BER tester is available on site, and the See A.12.3.8 Testing the Ethernet Service to
Ethernet service is transmitted on the radio test the availability of the Ethernet service.
link.
Step 9 After the switching, query the status of the protection group that is configured on NE A.
2. Select the corresponding protection group in Protection Group, and then click Query.
3. In Protection Group, the value of Active Board of Device should be the standby IF board
5-IFU2.

3. Select the required ODU, and set TX Status to Unmute.
4. Click Apply.
Step 11 Release the loopback set in Step 3.
5. Click Apply.
6. Click OK.
7. Click OK.

8. Click Close.
Step 12 Restore the setting of Enable Reverse Switching in Step 5.

1. Select the required NE from the Object Tree in the NE Explorer of NE A, and then choose
2. Select the corresponding protection group in Protection Group, and set Enable Reverse
Switching to Disable.
3. Click Apply.
----End
A.20.2 Testing the N+1 Protection Switching

You can verify whether the IF N+1 protection works normally by checking the working board
of the IF N+1 protection group before and after the switching.
Prerequisite
l Aligning the antennas must be complete.
l The equipment must be configured with the N+1 protection.

l U2000
l BER tester
Figure A-3 Configuration for testing the N+1 protection
NE A and NE B are configured as follows:

l Main IF boards: IFU2 in slot 3 and IFU2 in slot 5
l Main ODUs: ODU in slot 23 and ODU in slot 25
NE A NE B
NE B that is configured with the N+1 (N=2) configuration as an example.

Precautions
NOTE
If no BER tester is available on site, you can compare the values of Switching Status in Slot Mapping
Relation when the protection switching occurs and after the protection switching is complete.
Procedure
If... Then...
Step 3 At the remote site NE B, perform a software inloop at the E1 port by using the NMS.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.

Step 5 Before the switching, query the status of the protection group that is configured on NE B.
1. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose
Configuration > N+1 protection from the Function Tree.
2. Select the ID of the protection group to be queried, and then click Query.
3. In Slot Mapping Relation, Switching Status of the working units 3-IFU2-13-IFU2-1 and
5-IFU2-1 and the protection unit 4-IFU2-1 should be Normal.
NOTE
If a fault arises, you must rectify the fault and then proceed with the N+1 protection testing.
Step 6 Set TX Status to mute for the main ODU 23-ODU of NE A.



4. Click Apply.
If... Then...
No BER tester is available on site, and the See A.12.3.8 Testing the Ethernet Service to
Ethernet service is transmitted on the radio test the availability of the Ethernet service.
link.
Step 8 After the switching, query the status of the protection group that is configured on NE B.
1. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose
Configuration > N+1 protection from the Function Tree.
2. Select the ID of the protection group to be queried, and then click Query.
3. In Slot Mapping Relation, the Switching Status of the working unit 3-IFU2-1 for the
service that is configured with the N+1 protection should be SF.

4. Click Apply.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
----End

A.20.3 Testing the SNCP Switching

You can verify whether the SNCP works normally by checking the working port of the SNCP
Prerequisite
l The equipment must be configured with the SNCP.

l U2000
l BER tester

NE C that is configured with the SNCP as an example. Figure A-4 shows a network composed
of radio links, and the test procedures are similar in the case of a network composed of optical
fiber links.
Figure A-4 Configuration for testing the SNCP switching

NE A and NE C are configured as follows:
l West IF board: IFU2 in slot 3
l East IF board: IFU2 in slot 4
l West ODU: ODU in slot 23
l East ODU: ODU in slot 24
NE A
Working
Protecting SNC SNC
NE D
NE B
NE C

Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Channel in Working Service when
the protection switching occurs and after the protection switching is complete.
Procedure
If... Then...
Step 3 At the remote site NE C, perform a software inloop at the E1 port by using the NMS.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
Step 5 Before the switching, query the status of the protection group that is configured on NE C.
1. Select the NE from the Object Tree in the NE Explorer of NE C, and then choose
Configuration > SNCP Service Control from the Function Tree.
2. In Working Service, select an SNCP service that is already created, then click Function,
and finally select Query Switching Status.
3. The current SNCP status of the equipment is displayed in Working Service and Protection
Service.
In Current Status, Normal should be displayed. In Active Channel, Working
Channel should be displayed.

Step 6 Set TX Status to mute for the west ODU 23-ODU of NE A.

4. Click Apply.
If... Then...
Step 8 After the switching, query the status of the protection group that is configured on NE C.
1. Select the NE from the Object Tree in the NE Explorer of NE C, and then choose
Configuration > SNCP Service Control from the Function Tree.
2. Click Function, and then select Query Switching Status.
3. The current SNCP status of the equipment is displayed in Working Service and Protection
Service.
In Current Status, the service switching mode is displayed. In Active Channel,
Protection Channel should be displayed.
Step 9 Set TX Status to unmute for the west ODU 23-ODU of NE A.

4. Click Apply.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
----End
A.20.4 Testing the ERPS

You can verify whether the ERPS works normally by checking the port status of the ERPS
Prerequisite
l The equipment must be configured with the ERPS.
l The network cable for carrying the working and protection Ethernet services of the ERPS
must be properly connected.

U2000

As shown in Figure A-5, the following procedures consider the Ethernet service between NE
A and NE D that is configured with the ERPS as an example, the owner node is NE D.
Figure A-5 Configuration for testing the ERPS

NE A,NE B, NE C and NE D are configured as follows:
l Main IF board: IFU2 in slot 3
l Main ODU: ODU in slot 23

East West
NE B
Protection channel East
West
NE A NE D
East
West
Working channel
NE C
West
East
Procedure
Step 1 Before the switching, query the status of the protection group that is configured on NE D.
1. Select the NE from the Object Tree in the NE Explorer of NE D, and then choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2. Select the ERPS protection group to be queried, and then click Query.
3. The value of Status of State Machine should be Idle.
Step 2 See A.12.3.8 Testing the Ethernet Service to test the availability of the Ethernet service.
Step 3 Set TX Status to mute for the west ODU 23-ODU of NE A.

4. Click Apply.
Step 4 After the switching, query the status of the protection group that is configured on NE D.
1. Select the NE from the Object Tree in the NE Explorer of NE D, and then choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2. Select the ERPS protection group to be queried, and then click Query.
3. The value of Status of State Machine should be Protection.
Step 5 See A.12.3.8 Testing the Ethernet Service to test the availability of the Ethernet service.
Step 6 Set TX Status to unmute for the west ODU 23-ODU of NE A.
4. Click Apply.
----End
A.20.5 Testing the Linear MSP Switching

You can verify whether the linear MSP group works normally by checking the working port of
the linear MSP group before and after the switching.
Prerequisite
l The equipment must be configured with the linear MSP.
l The working and protection optical fibers of the linear MSP are connected properly.

l U2000
l BER tester

Figure A-6 shows the linear MSP composed of the OptiX RTN equipment through the
connection of optical fibers. The following procedures consider the E1 service from NE A to
NE B as an example.

Figure A-6 Configuration for testing the Ethernet service
NE A Working channel NE B
Protection channel
Precautions
NOTE
If no BER tester is available on site, you can compare the values of West Switching Status in Slot Mapping
Relation when the protection switching occurs and after the protection switching is complete.
Procedure
If... Then...
Step 3 At the remote site NE B, perform a software inloop at the corresponding E1 port by using the
NMS.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur.
If bit errors occur, see the Maintenance Guide for handling the bit errors.
Step 5 Before the switching, query the status of the protection group that is configured on NE A.
Configuration > Linear MS from the Function Tree.

2. In Slot Mapping Relation, select Working Unit.

3. Click Query, and then select Query Switching Status.
In Slot Mapping Relation, the value of West Switching Status should be Idle.
NOTE
In the case of the working and protection units of the service that is configured with the linear MSP, the
values of West Switching Status should be Idle. If a fault arises, you must rectify the fault and proceed
with the linear MSP switching testing.
Step 6 Shut down the laser for the working unit on NE A.

1. Select the required optical interface board from the Object Tree in the NE Explorer of NE
A.
2. Choose Configuration > SDH Interface from the Function Tree.
3. Select By Function and then select Laser Switch from the drop-down list.
4. Select the laser port that corresponds to the working unit, and then set Laser Switch to
Close.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
If... Then...
The BER tester is available on site Check the test result on the BER tester. It
E1 service is transmitted on the optical fiber PRBS to test the availability of the E1 service.
link.
Step 8 After the switching, query the status of the protection group that is configured on NE A.
Configuration > Linear MS from the Function Tree.
2. In Slot Mapping Relation, select Working Unit.
3. Click Query, and then select Query Switching Status.
In Slot Mapping Relation, the value of West Switching Status should be Switch upon
signal failure.

NOTE
In the case of the 1+1 linear MSP, Revertive Mode can be set to Revertive or Non-Revertive. In the case
of the 1:N linear MSP, Revertive Mode is always set to Revertive.
l After the automatic switching occurs on the equipment, the service is restored. If Revertive Mode is
set to Revertive for the linear MSP, the change in values of West Switching Status and Protected
Unit can be queried after the WTR time expires.
l After the automatic switching occurs on the equipment, the service is restored. If Revertive Mode is
set to Non-Revertive for the linear MSP, stop and then start the MSP protocol to restore the value of
West Switching Status to Idle.
Step 9 Turn on the laser for the working unit on NE A.

1. Select the required optical interface board from the Object Tree in the NE Explorer of NE
A.
2. Choose Configuration > SDH Interface from the Function Tree.
3. Select By Function and then select Laser Switch from the drop-down list.
4. Select the laser port that corresponds to the working unit, and then set Laser Switch to
Open.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
----End
A.21 Testing the AM Switching

By testing the AM switching, you can check whether the AM switching is normal over radio
links.
A.21.1 Testing the AM Switching by Using a BER Tester

If a BER tester is available, the BER tester can be used to test the AM switching.

A.21.2 Testing the AM Switching Without a BER Tester

If no BER tester is available, you can test the AM switching by querying the bit errors over radio
links.
A.21.1 Testing the AM Switching by Using a BER Tester

If a BER tester is available, the BER tester can be used to test the AM switching.
Prerequisite
l The radio links must be Hybrid radio links for which the AM function is enabled.
l The E1 service must be configured.
l The weather is favorable.

l U2000
l BER tester
Precautions
The following test procedure considers the E1 service between NEs as an example.
Procedure
Step 1 Connect the BER tester to an E1 port on the local NE.
NOTE
Test the E1 services with the highest priority, which are not discarded in the lowest-order modulation mode.
Step 2 On the remote NE, perform an inloop at the E1 port by using the NMS.
5. Click Apply.
6. Click OK.
7. Click OK.
8. Click Close.
Step 3 Configure the Hybrid/AM attribute on the local NE.
1. Select the IF board from the NE Explorer, and then choose Configuration > Hybrid/AM
2. On the local NE, set the AM attribute to Disable, and set Manually Specified Modulation
Mode to the same value as Modulation Mode of the Guarantee AM Capacity.

3. Click Apply.
Step 4 Querying the AM working status on the local NE.
2. Click Query.
Transmit-End Modulation Mode should be Manually Specified Modulation Mode of
a pre-set value.
Step 5 Use the BER tester to test the bit errors.

The test result should show that no bit error occurs.
Step 6 Configure the Hybrid/AM attribute to the planned values on the local NE.
2. On the local NE, set the AM attribute to Enable, and set Modulation Mode of the
Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned
values.
3. Click Apply.
2. Click Query.
Transmit-End Modulation mode should be Modulation Mode of the Full AM
Capacity of a preset value.
NOTE
In the case of unfavorable weather, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
Step 8 Check the BER test result.

There should be no bit errors.
Step 9 Release the inloop set in Step 2.
5. Click Apply.
6. Click OK.
7. Click OK.


8. Click Close.
----End
A.21.2 Testing the AM Switching Without a BER Tester

If no BER tester is available, you can test the AM switching by querying the bit errors over radio
links.
Prerequisite
l The radio links must be Hybrid radio links for which the AM function is enabled.
l The weather is favorable.

U2000
Procedure
Step 1 Configure the Hybrid/AM attribute on the local NE.
2. On the local NE, set the AM attribute to Disable, and set Manually Specified Modulation
Mode to the same value as Modulation Mode of the Guarantee AM Capacity.
3. Click Apply.
Step 2 Query the 15-minute performance value of the IF board on the local NE.
1. Select the required IF board from the Object Tree in NE Explorer.
2. In the Function Tree, choose Performance > Current Performance.
3. In Monitored Object Filter Condition, select All.
4. Set Monitor Period to 15-Minute.
5. In Count, select Other Errors. In Display Options, select Consecutive Severely Errored
Seconds Second.
6. Click Query.
In performance events, the value of FEC_BEF_COR_ER should be 0.

2. Click Query.
Transmit-End Modulation Mode should be Manually Specified Modulation Mode of
a pre-set value.

Step 4 Reset the performance event register.

1. Select the required IF board from the Object Tree in NE Explorer.
2. In the Function Tree, choose Performance > Current Performance.
3. Click Reset.
The confirmation dialog box is displayed.
4. Click OK.
Step 5 Configure the Hybrid/AM attribute to the planned values on the local NE.
2. On the local NE, set the AM attribute to Enable, and set Modulation Mode of the
Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned
values.
3. Click Apply.
Step 6 Repeat Step 2. Wait for a period, and query the 15-minute performance value of the IF board
on the local NE.
In performance events, the value of FEC_BEF_COR_ER should be 0.
2. Click Query.
Transmit-End Modulation mode should be Modulation Mode of the Full AM
Capacity of a preset value.
NOTE
In the case of unfavorable weather, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
----End

Configuration Guide (U2000) B Parameters Description
B Parameters Description
This topic describes the parameters used in this document.
B.1 Parameters for NE Management

This topic describes the parameters that are used for managing network elements (NEs).
B.2 Parameters for Cable Management
This topic describes the parameters that are used for managing cables.
B.3 Parameters for Communications Management
This topic describes the parameters that are used for communications management.
B.4 Radio Link Parameters
This topic describes the parameters that are related to radio links.
B.5 Multiplex Section Protection Parameters
This topic describes the parameters that are related to multiplex section protection (MSP).
B.6 SDH/PDH Service Parameters
This topic describes the parameters that are related to SDH/PDH services.
B.7 Clock Parameters
This topic describes the parameters that are related to clocks.
B.8 RMON Parameters
This topic describes the parameters that are related to RMON performances.
B.9 Parameters for Ethernet Services and Ethernet Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the
packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port
parameters, and QoS parameters.
B.10 Parameters for Ethernet Services and Ethernet Features on the EoPDH Plane
EoPDH plane, including service parameters, protocol parameters, OAM parameters, Ethernet
port parameters, and QoS parameters.
B.11 Parameters for the Orderwire and Auxiliary Interfaces
This topic describes the parameters that are related to the orderwire and auxiliary interfaces.
B.12 Parameters for Board Interfaces
This topic describes the parameters that are related to board interfaces.
Issue 01 (2010-09-25) Huawei Proprietary and Confidential B-1

B Parameters Description Configuration Guide (U2000)
B.13 Parameters for Overhead

This topic describes the parameters that are related to overhead.
B-2 Huawei Proprietary and Confidential Issue 01 (2010-09-25)

B.1 Parameters for NE Management

This topic describes the parameters that are used for managing network elements (NEs).

This topic describes the parameters that are used for searching for NEs.
This topic describes the parameters that are related to NE creation.
This topic describes the parameters that are used for changing NE IDs.
This topic describes the parameters that are used for synchronizing the time of NEs.
B.1.5 Parameter Description: Localization Management of the NE Time
This parameter describes the parameters that are used for localization management of the NE
time.
This topic describes the parameters that are used for managing the standard NTP key.
B.1.7 Parameter Description: License Management
This topic describes the parameters that are used for managing the license.
B.1.8 Parameter Description: Automatic Disabling of the Functions of NEs
This parameter describes the parameters that are used for automatically disabling the functions
of an NE.

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Choose File > Discovery > NE from the Main Menu.

Parameters for the Search Field

Parameter Value Range Default Value Description
Address Type IP Address of GNE IP Address Range of GNE l If the OSI protocol is
NSAP Address used on the DCN, you
can search for an NE
IP Address Range of GNE based on NSAP
Address only.
l If the IP protocol is
used on the DCN, you
can search for an NE
based on IP Address
of GNE or IP Address
Range of GNE.
l To search for all the
NEs that communicate
with the gateway NE,
select IP Address
Range of GNE.
l To select the gateway
NE only, select IP
Address of GNE.
NOTE
If Address Type is set to IP
Address of GNE or IP
Address Range of GNE,
and if the U2000 (server)
and the gateway NE are
located in different network
segments, ensure that the
U2000 and relevant routers
are configured with the IP
routes for the network
segment in which the
U2000 and gateway NE are
located.
If Address Type is set to
NSAP Address, ensure that
the OSI protocol stack is
installed.

Search Address - - l If Address Type is set

to IP Address of
GNE, enter the IP
address of the gateway
NE, such as 129.9.x.x.
l If Address Type is set
to IP Address Range
of GNE, enter the
number of the IP
network segment in
which the gateway NE
is located, such as
129.9.255.255.
l If Address Type is set
to NSAP Address,
enter the NSAP
address of the gateway
NE.
User Name - - This parameter specifies

the user name of the
gateway NE.
Password - - This parameter specifies

the password of the
gateway NE.

Parameter for Searching for NEs

Create NE after search Selected Deselected l To create NEs in

Deselected batches, it is
recommended that you
select Create NE
after search. The NEs
are automatically
created after they are
found.
l After Create NE after
search is selected,
enter NE User and
Password that are
used for creating an
NE.
NOTE
If only Create NE after
search is selected, Search
for NE is selected
automatically.
NE User - - l This parameter

specifies the user name
to be entered when an
NE is created.
l This parameter is valid
only when Create NE
after search is
selected.
Password - - l This parameter

specifies the password
NE is created.
only when Create NE
after search is
selected.

Upload after create Selected Deselected l This parameter

Deselected specifies whether to
automatically upload
the NE data after the
NE is found and
created.
l If only Upload after
create is selected,
Search for NE and
Create NE after
search are selected
automatically.
Parameter for the Found NEs

NE ID - - This parameter indicates

the ID of the found NE,
which consists of
extended ID and NE ID.
For example, in the case of
NE9-25, the value 9
indicates the extended ID,
and the value 25 indicates
the NE ID.
GNE Address - - This parameter indicates

the address of the gateway
NE that is connected to the
found NE.
GNE ID - - This parameter indicates

the ID of the gateway NE
that is connected to the
found NE.
Created As GNE Yes Yes l This parameter

No specifies the password
NE is created.
only when Create NE
after search is
selected.

Connection Mode Common Common The communication

Security SSL between the client and the
server is encrypted if this
parameter is set to
Security SSL.
Port - 1400 This parameter specifies

the communication port.
NE Status Created - This parameter indicates

Uncreated whether the found NE is
created.
Related Tasks

This topic describes the parameters that are related to NE creation.
Navigation Path
1. In the Physical ViewPhysical Root, right-click New > NE.
2. Choose RTN Series > OptiX RTN 950 from the Object Tree.
Parameters on the Main Interface

Type - - This parameter indicates

the type of the NE to be
created.
ID 1 to 49135 - l The ID refers to the

basic ID. If the
extended ID is not
used, the basic ID of an
NE must be unique on
the networks that are
managed by the same
NMS.
l This parameter is set
according to the
NOTE
The NE ID consisting of the
basic ID and extended ID
identifies an NE on the
NMS.

Extended ID 1 to 254 9 If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
the extended ID.
Name - - l This parameter

specifies the name of
the NE.
l After you specifies the
name of the NE, the
name is displayed
under the icon of the
NE.
Remarks - - This parameter specifies

the remarks of the NE.
Gateway Type Non-Gateway Non-Gateway l This parameter is set to

Gateway Gateway if the new
NE is a gateway NE.
l This parameter is set to
Non-Gateway if the
new NE is a non-
gateway NE.
according to the DCN
planning if the new NE
can function as a
gateway NE or a non-
gateway NE.
Affiliated Gateway - - This parameter indicates

the gateway NE of the new
NE when Gateway Type
is set to Non-Gateway.
Affiliated Gateway IP IP l This parameter needs

Protocol OSI to be set when
Gateway Type is set
to Gateway.
l When the OSI over
DCC solution is used,
this parameter is set to
OSI.
l In other cases, this
parameter is set to IP.

IP Address - - This parameter indicates

the IP address of the new
NE. This parameter needs
to be set when Affiliated
Gateway Protocol is set
to IP.
Connection Mode Common Common The communication

Security SSL between the client and the
server is encrypted if this
parameter is set to
Security SSL.
Port - 1400 This parameter specifies

the communication port.
NE User - - This parameter specifies

the user name to be
entered when an NE is
created.
Password - - This parameter specifies

the password to be entered
when an NE is created.
NSAP Address - - This parameter indicates

the NSAP address of the
new NE. This parameter
needs to be set when
Affiliated Gateway
Protocol is set to OSI.
You need to set the area ID
only, and the other parts
are automatically
generated by the NE.
Related Tasks

This topic describes the parameters that are used for changing NE IDs.
Navigation Path
1. In the Main Topology, right-click the NE whose ID needs to be modified.
2. Choose Object Attributes.
3. Click Modify NE ID.

Parameters for Changing NE IDs

New ID - - l The new ID refers to

the basic ID. If the
extended ID is not
used, the basic ID of an
NE must be unique on
the networks that are
managed by the same
NMS.
according to the
NOTE
The NE ID consisting of the
basic ID and extended ID
identifies an NE on the
NMS.
New Extended ID 1 to 254 9 If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
the extended ID.
Related Tasks

This topic describes the parameters that are used for synchronizing the time of NEs.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Synchronization from
the Main Menu.
2. Click the NE Time Synchronization tab.
Parameters for NE Time Synchronization

NE Name - - This parameter indicates

the name of the NE.
NE ID - - This parameter indicates

the ID of the NE.

Synchronous Mode Standard NTP Null l If this parameter is set

NM to NM, the NE
synchronizes the time
Null of the NMS server.
l If this parameter is set
to Standard NTP, the
NE synchronizes the
Network Time
Protocol (NTP) server
through the standard
NTP.
Standard NTP Enabled Disabled This parameter is valid

Authentication Disabled only when Synchronous
Mode is set to Standard
NTP.
Parameters for the Standard NTP Server

Standard NTP Server NE ID NE ID l If the NE functions as

Identifier IP the gateway NE, this
l If the NE functions as
a non-gateway NE and
communicates with
the gateway NE
through the HWECC
protocol, this
parameter is set to NE
ID.
a non-gateway NE and
communicates with
the gateway NE
through the IP
protocol, this

Standard NTP Server - - l If the NE functions as

the gateway NE, this
parameter is set to the
IP address of the
external NTP server.
a non-gateway NE,
the ID or IP address of
the gateway NE.
Standard NTP Server 0 to 1024 0 l If the NTP server does

Key not need to
authenticated, this
parameter is set to the
value "0".
l If the NTP server
needs to be
authenticated, the
authentication is
performed according
to the allocated key of
the NTP server. In this
case, the NE
authenticates the NTP
server based on the key
and the corresponding
password (specified in
the management of the
standard NTP key).
Parameters for Setting Automatic Synchronization

Synchronization - - l This parameter

Starting Time specifies the start time
of the synchronization
period. After this
parameter is specified,
the NMS and the NE
synchronize the time
once at the intervals of
Synchronization
Period(days).
l It is recommended that
you use the default
value.

DST Selected Deselected l This parameter

Deselected indicates whether
Synchronization
Starting Time is the
daylight saving time.
situation.
Synchronization Period 1 to 300 1 l This parameter

(days) indicates the period of
synchronizing the time
of the NE with the time
of the NMS.
you use the default
value.
Related Tasks
B.1.5 Parameter Description: Localization Management of the NE

Time
This parameter describes the parameters that are used for localization management of the NE
time.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Localization
Management from the Main Menu.
2. Select the NE for time localization management from the Object Tree, and then click
Parameters for Localization Management of the NE Time

NE - - This parameter indicates the name of the

NE.
TimeZone - - This parameter indicates the time zone.
DST - - This parameter indicates whether DST is

enabled.

Parameters for Time Zone

Time Zone - - l After the time zone is changed, the

current time of the NE is changed
accordingly.
l This parameter is set according to the
place where the NE is located.
DST Selected Deselected l The parameters related to daylight

Deselected saving time can be valid only when this
parameter is selected.
situation whether daylight saving time is
used in the place where the NE is located.
Offset 1 to 120 - This parameter specifies the offset value of

Unit: minute(s) the daylight saving time.
Start Rule WEEK WEEK This parameter specifies the method of

DATE adjusting the daylight saving time.
Start Time - - This parameter specifies the start daylight

saving time.
End Rule WEEK WEEK This parameter specifies the method of

DATE adjusting the daylight saving time.
End Time - - This parameter specifies the end daylight

saving time.
Related Tasks

This topic describes the parameters that are used for managing the standard NTP key.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Synchronization from
the Main Menu.
2. Click the Standard NTP Key Management tab.


Key 1 to 1024 - l This parameter

indicates the key for
NTP authentication.
according to the
requirements of the
Password - - l This parameter

indicates the password
that corresponds to
Key.
according to the
requirements of the
Trusted Yes Yes l When this parameter is

No set to No, the key
verification is not
trusted. After
receiving the key, the
NE rejects the clock
synchronization
service.
l When this parameter is
set to Yes, the key
verification is trusted.
After receiving the
key, the NE provides
the clock
synchronization
service.
l After receiving an
unknown or incorrect
key, the NE rejects the
clock synchronization
service. Hence, it is
set a trusted key only.
Related Tasks
B.1.7 Parameter Description: License Management

This topic describes the parameters that are used for managing the license.

Navigation Path
1. In the NE Explorer, select the NE and then choose Configuration > License
2. Click the License Management tab.
Parameters for Managing Licenses

Board - - This parameter displays the boards that need

to be supported by licenses.
File Type - - This parameter displays the license type

corresponding to each board.
Capacity - - This parameter displays the capacity of each

board.
Load Yes - This parameter displays whether the

No corresponding license file is loaded to each
board.
B.1.8 Parameter Description: Automatic Disabling of the Functions

of NEs
This parameter describes the parameters that are used for automatically disabling the functions
of an NE.
Navigation Path
1. On the Main Topology, choose Configuration > NE Batch Configuration > Automatic
Disabling of NE Function.
2. Select the NE whose functions need to be automatically disabled from the Object Tree, and
then click .
Parameters for Automatically Disabling the Functions of NEs

NE Name - - This parameter indicates the name of the

NE.
NE Type OptiX RTN 950 - This parameter indicates the type of the NE.
Operation Type - - This parameter indicates the type of the

operation, such as loopback, and shutdown
of the laser.

Auto Disabling Disabled Enabled This parameter specifies whether to

Enabled automatically disable the operations such as
loopback, and shutdown of the laser.
Auto Disabling 1 to 2880 5 This parameter specifies the time of

Time(min) automatically disabling the operations such
as loopback, and shutdown of the laser.
B.2 Parameters for Cable Management

This topic describes the parameters that are used for managing cables.

This topic describes the parameters that are used for searching for fibers.
This parameter describes the parameters that are used for creating fibers.
This topic describes the parameters that are used for creating radio links.

This topic describes the parameters that are used for searching for fibers.
Navigation Path
1. Choose File > Discovery > Fiber from the Main Menu.
2. Select the board of the NE on which the fiber needs to be searched for or the IF board of
the NE on which radio links need to be searched for from the Subject Tree.
3. Click Search.
Parameters for Searching For Fibers

Source NE - - This parameter indicates

the name of the source NE
on which fibers or radio
links are found.
Source Board - - This parameter indicates

the board and slot of the
source NE on which fibers
or radio links are found.

Source Port - - This parameter indicates

the number of the port on
the board of the source NE
links are found.
Sink NE - - This parameter indicates

the name of the sink NE on
which fibers or radio links
are found.
Sink Board - - This parameter indicates

the board and slot of the
sink NE on which fibers or
radio links are found.
Sink Port - - This parameter indicates

the number of the port on
the board of the sink NE
links are found.
Level - - This parameter indicates

the level of the found fiber
or the working mode of
the found radio link.
Name - - This parameter indicates

the name of the found
fiber or radio link.
Direction Two-Fiber Bidirectional - This parameter indicates

Single-Fiber the direction of the found
Unidirectional fiber.
Conflict with logical link Yes - This parameter indicates

(Y/N) No whether the found fiber or
radio link conflicts with
the fiber or radio link
displayed on the NMS.
Operation Result Succeeded - This parameter indicates

Failed whether the cable is
created successfully.
Fiber/Cable Type - - This parameter indicates

the type of the found fiber
or cable.
Related Tasks
A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method


This parameter describes the parameters that are used for creating fibers.
Navigation Path
1. Choose File > Create > Link from the Main Menu. The Create Link dialog box is
displayed.
2. Choose Fiber/Cable > Fiber from the Object Tree.
Parameters for Fibers

Create Ways Common Ways Common Ways l If Common Ways is

Batch Ways selected, fibers need to
be created one by one.
l If Batch Ways is
selected, fibers can be
created in batches.
Fiber/Cable Type Fiber Fiber This parameter indicates

that Fiber/Cable Type to
be created is a fiber.
Name - - This parameter specifies

the name of the fiber to be
created. The name
consists of up to 255
characters, excluding
certain special marks such
as | * ? " < >.

the remark information
customized by the user.
Source NE - - This parameter specifies

the source NE on which
the fiber needs to be
created.
Source NE Shelf-Slot- - - This parameter specifies

Board Type-Port the board, slot, and port of
the fiber needs to be
created.
Rate Level - - This parameter indicates

the level that corresponds
to the port on the board.

Medium Type G.652 G.652 This parameter specifies

G.653 the medium type of the
fiber.
G.654
G.655-LEAF
G.655-TWC
G.655-TWRS
G.655-LS
Sink NE - - This parameter specifies

the sink NE on which the
fiber needs to be created.
Sink NE Shelf-Slot- - - This parameter specifies

fiber needs to be created.
Direction Two-Fiber Bidirectional - This parameter specifies

Single-Fiber the direction of the fiber to
Unidirectional be created.
Length(km) 0 to 100000 - This parameter specifies

the length of the fiber to be
created.
Attenuation(dB) - - This parameter specifies

the attenuation of the fiber
to be created.
Created On - - This parameter specifies

the time when the fiber is
created.
Creator - - This parameter specifies

the name of the person
who creates the fiber.
Maintainer - - This parameter specifies

who maintains the fiber.
Automatically Allocate - No This parameter displays

IP Address whether to allocate IP
addresses automatically.
Related Tasks
A.4.3 Creating an SDH Optical Transmission Link by Using the Manual Method


This topic describes the parameters that are used for creating radio links.
Navigation Path
1. Choose File > Create > Link from the Main Menu. The Create Link dialog box is
displayed.
2. Choose Fiber/Cable > Microwave Link from the Object Tree.
Parameters for Microwave Links

Fiber/Cable Type Radio Link Radio Link This parameter indicates

that a radio link needs to
be created is Fiber/Cable
Type.

the name of the radio link
to be created. The name
consists of up to 255
characters, excluding
certain special marks such
as | * ? " < >.

the remark information
customized by the user.
Source NE - - The parameter specifies

the radio link needs to be
created.
Source NE Shelf-Slot- - - This parameter specifies

the radio link needs to be
created.
Rate Level - - This parameter indicates

the level that corresponds
to the port on the IF board.
Sink NE - - The parameter specifies

radio link needs to be
created.

Sink NE Shelf-Slot- - - This parameter specifies

radio link needs to be
created.
Length(km) 0 to 100000 - This parameter specifies

the length of the radio link
to be created.
Created On - - This parameter indicates

the time when the radio
link is created.
Creator - - This parameter specifies

who creates the radio link.
Maintainer - - This parameter specifies

who maintains the radio
link.
Automatically Allocate - No This parameter displays

IP Address whether to allocate IP
addresses automatically.
Related Tasks
B.3 Parameters for Communications Management

This topic describes the parameters that are used for communications management.

This topic describes the parameters that are used for NE communication setting.
B.3.2 Parameter Description: DCC Management_DCC Rate Configuration
This topic describes the parameters that are used for configuring the DCC rate.
B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management
This topic describes the parameters that are used for DCC transparent transmission management.
B.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECC
This topic describes the parameters that are related to the extended ECCs of Ethernet ports.
This topic describes the parameters that are used for NE ECC link management.
B.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management
This topic describes the parameters that are used for IP route management.

B.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation

This topic describes the parameters that are used for new static IP routes.
B.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
This topic describes the parameters that are used for OSPF settings.
This topic describes the parameters that are used for configuring the proxy ARP.
B.3.10 Parameter Description: OSI Management_Network Layer Parameter
This topic describes the parameters that are related to the network layer of the OSI protocol
model.
This topic describes the parameters that are related to OSI routing tables.
This topic describes the parameters that are related to the OSI tunnels.
B.3.13 Parameter Description: DCN Management_Bandwidth Management
This topic describes the parameters that are used for bandwidth management of the inband DCN.
This topic describes the parameters that are used for setting ports of the inband DCN.
This topic describes the parameters that are used for setting a protocol of the inband DCN.
This section describes the parameters for configuring access control.
B.3.17 Parameter Description: Access Control
This topic describes the parameters that are used for access control of the NMS.
B.3.18 Parameter Description: LCT Access Control
This topic describes the parameters that are used for LCT access control.

This topic describes the parameters that are used for NE communication setting.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.

Parameters for NE Communication Setting

Parameter Value Default Description
Range Value
IP Address - Before In the HWECC solution, an IP

delivery, the address is set according to the
IP address of following rules:
the NE is set l The IP address, subnet
to 129.9.0.x. mask, and default gateway
The letter x of the gateway NE should
indicates the meet the planning
basic ID. requirements of the
external DCN.
Gateway IP Addr... - 0.0.0.0
l If an NE uses the extended
Subnet Mask - 255.255.0.0 ECC, the IP address must
be in the same network
segment.
l The IP address of other
NEs should be set
according to the NE ID. In
this case, the IP address of
an NE should be set in the
format of 0x81000000
+ID. That is, if the ID is
0x090001, the IP address
should be set to 129.9.0.1.
Extended ID 1 to 254 9 l Do not change the

extended ID when the
number of actual NEs does
not exceed the range
permitted by the basic NE
ID.
this parameter takes the
default value.
Related Tasks
B.3.2 Parameter Description: DCC Management_DCC Rate

Configuration
This topic describes the parameters that are used for configuring the DCC rate.

Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
2. Click the DCC Rate Configuration tab.
Parameters for DCC Rate Configuration

Port - - This parameter indicates the port that is

connected to the DCC channel.
NOTE
On the NMS interface, the first interface on the
system control, switching, and clock board (like
7-CSH-1) corresponds to its external clock
interface.
Enabled/Disabled Enabled Enabled (for line It is recommended that you use the default
Disabled ports) value, except for the following cases:
Disabled (for l If the port is connected to the other ECC
external clock subnet, Enabled/Disabled is set to
interfaces) Disabled.
l If the port is connected to a third-party
network and does not exchange the
network management information with
other ports, Enabled/Disabled is set to
Disabled.
l If external clock interfaces are used to
transmit the DCC solution, Enabled/
Disabled is set to Enabled for the
external clock interfaces.
Channel Type D1-D3 D1-D1 (for the PDH It is recommended that you use the default
D4-D12 radio whose value, except for the following cases:
transmission l If the IP over DCC or OSI over DCC
D1-D12 capacity is less than solution is adopted, Channel Type for
D1-D1 16xE1) the SDH line ports is set to a value that
D1-D3 (for other is the same as the value for third-party
cases) network.
l If the DCC transparent transmission
solution is adopted, the value of
Channel Type for the SDH line ports
should not conflict with the value that is
set for the third-party network.
DCC Resources - - This parameter indicates the DCC

resources.
Communication - - This parameter indicates the

Status communication status.

Protocol Type HWECC TCP/IP It is recommended that you use the default
TCP/IP value, except for the following cases:
OSI l If the IP over DCC solution is adopted,
Protocol Type is set to TCP/IP.
l If the OSI over DCC solution is adopted,
Protocol Type is set to OSI.
LAPD Role User User l This parameter is valid only when

Network Protocol Type is set to OSI.
l In the case of a DCC channel, LAPD
Role must be set to User for one end and
must be set to Network for the other end.
LAPD MTU - - Displays the maximum LAPD packet size.
Related Tasks
B.3.3 Parameter Description: DCC Management_DCC Transparent

Transmission Management
This topic describes the parameters that are used for DCC transparent transmission management.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
2. Click the DCC Transparent Transmission Management tab.
3. Click Create.
Parameters for DCC Transparent Transmission Management

Source Timeslot/ - - This parameter specifies the source timeslot

Porta or port.

Transparent D1 - l Only one overhead byte can be selected

Transmission of D2 each time.
Overhead Bytes at l X1, X2, X3, and X4 indicate the
Source Port D3
customized overhead bytes that are used
D4 for transmitting asynchronous data
D5 services.
D6 l An overhead byte cannot be a byte that
D7 is used. For example, an overhead byte
cannot be a byte in the used DCC
D8
channel.
D9
D10
D11
D12
E1
E2
F1
K1
K2
X1
X2
X3
X4
Sink Timeslot/ - - This parameter specifies the sink timeslot or

Porta port.

Transparent D1 - l Only one overhead byte can be selected

Transmission of D2 each time.
Overhead Bytes at l An overhead byte cannot be a byte that
Sink Port D3
is used. For example, an overhead byte
D4 cannot be a byte in the used DCC
D5 channel.
D6 l Generally, Transparent Transmission
D7 of Overhead Bytes at Sink Port can be
set to a value that is the same as or
D8
different from the value in the case of
D9 Source Timeslot/Port.
D10
D11
D12
E1
E2
F1
K1
K2
X1
X2
X3
X4
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functions
the same regardless of the source port or sink port.
Related Tasks
B.3.4 Parameter Description: ECC Management_Ethernet Port

Extended ECC
This topic describes the parameters that are related to the extended ECCs of Ethernet ports.
Navigation Path
Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.

Parameters for the ECC Extended Mode

ECC Extended Auto mode Auto mode It is recommended that you use the default
Mode Specified mode value.
Parameters for Setting the Server

IP - - This parameter indicates the IP address of

the server.
Port 1601 to 1699 0 l This parameter is valid only when ECC

Extended Mode is set to Specified
mode.
l This parameter can be set only when the
NE functions as the server of the
extended ECC. In normal cases, the NE
that is close to the NMS functions as the
server.
l This parameter can be set to any value
from 1601 to 1699.
Parameters for Setting the Client

Opposite IP - 0.0.0.0 l This parameter is valid only when ECC

Extended Mode is set to Specified
Port 1601 to 1699 0 mode.
l This parameter can be set only when the
NE functions as the client of the
extended ECC. Except for the NE that
functions as the server, all other NEs that
use the extended ECC can function as the
client.
l Opposite IP and Port are respectively
set to the IP address of the server NE and
the specified pot number.
Related Tasks


This topic describes the parameters that are used for NE ECC link management.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Parameter for NE ECC Link Management

Destination NE - - This parameter specifies the sink NE of the

ECC connection.
Transfer NE - - This parameter specifies the next transfer

NE and the direction of the ECC route.
Distance 0 to 64 - l This parameter specifies the number of

NEs (excluding the source NE and sink
NE) through which the ECC route
passes, namely, the number of ECC
packet forwarding attempts. The value
can be set to a value that is greater than
the number of actual ECC packet
forwarding attempts. If the value is set to
a value that is less than the number of
actual ECC packet forwarding attempts,
however, the destination NE fails to be
accessed.
l If the value is set to 0, it indicates that the
source NE is adjacent to the destination
NE.
Level 4 - l This parameter indicates that multiple

5 ECC routes from the source NE to the
destination NE may be available. An
ECC route of a higher priority is selected
to transmit the packets to the destination
NE.
l If the ECC route is generated
automatically, the priority is 4.
l If the ECC route is added manually, the
priority is 5.
Mode Manual - This parameter indicates the ECC routing

Automatic mode.
SCC No. - - This parameter specifies the physical port

through which the ECC route passes. The
value of this parameter is automatically
assigned the NE.

Related Tasks
B.3.6 Parameter Description: IP Protocol Stack Management_IP

Route Management
This topic describes the parameters that are used for IP route management.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
2. Click the IP Route Management tab.
Parameters for IP Route Management

Destination - - This parameter indicates the destination

Address address of the packets. This parameter can
be set to a valid IP address of class A, B, or
C only, but cannot be set to the IP address
of the local host or the loopback address
with the 127 field.
Subnet Mask - - This parameter indicates the subnet mask of

the destination address of the packets.
Gateway - - This parameter indicates the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of the
next hop of the packets.

Protocol DIRECT - l DIRECT: indicates the route between

STATIC the local NE and an adjacent NE.
OSPF l STATIC: indicates the route that is
created manually.
RIP
l OSPF: indicates the route between the
OSPF_ASE local NE and a non-adjacent NE.
OSPF_NSSA l RIP: indicates the route that is
discovered by the routing information
protocol.
l OSPF_ASE: indicates the route whose
Destination Address is beyond the
OSPF domain.
l OSPF_NSSA: indicates the route whose
Destination Address is in a not so
stubby area (NSSA).
l A route can be deleted in the case of
STATIC only, but cannot be edited in
the other cases.
l Compared with a dynamic route, a static
route has a higher priority. If any conflict
occurs, the static route is preferred.
Interface - - This parameter indicates the interface that is

used on the route. Interface is a concept
specified in the TCP/IP protocol stack. In
the TCP/IP protocol stack, you can create
multiple types of interface, such as a
loopback interface (namely, the interface
whose IP address is 127.0.0.1), an Ethernet
interface, and PPP interface. Each interface
must have a unique interface name.
Metric 0 to 65535 - This parameter indicates the maximum

number of routers through which the
packets are transmitted. Metric is used to
indicate the overhead bytes that are
transmitted to the destination address. The
smaller the value, the less the overhead
bytes. If multiple routes can reach the same
destination address, a route whose overhead
is less is preferred to transmit the packets.
Related Tasks

B.3.7 Parameter Description: IP Protocol Stack Management_IP

Route Management Creation
This topic describes the parameters that are used for new static IP routes.
Navigation Path
2. Click the IP Route Management tab.
3. Click New.
Parameters for Creating IP Routes

Destination - - This parameter specifies the destination

Address address of the packets. This parameter can
be set to a valid IP address of class A, B, or
C only, but cannot be set to the IP address
of the local host or the loopback address
with the 127 field.
Subnet Mask - - This parameter indicates the subnet mask of

the destination address of the packets.
Gateway - - This parameter specifies the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of the
next hop of the packets.
Related Tasks
B.3.8 Parameter Description: IP Protocol Stack Management_OSPF

Parameter Settings
This topic describes the parameters that are used for OSPF settings.
Navigation Path
2. Click the OSPF Parameter Settings tab.

OSPF Parameters
Area - 0.0.0.0 l The OSPF protocol supports the division

of NEs into multiple areas. Only the NEs
in the same area can transmit the OSPF
packets to each other to generate the
route.
l When setting the area for the NEs, you
need to set the NEs that run the OSPF
protocol to the same area.
DCC Hello Timer 1 to 255 10 l DCC Hello Timer(s) specifies the Hello
(s) packet timer at the DCC interface.
l The Hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l DCC Hello Timer(s) determines the
interval for the hello packet timer to
transmit the hello packets.
l In the case of two interconnected NEs,
DCC Hello Timer(s) must be set to the
same value.
DCC Neighbor 1 to 65535 40 l DCC Neighbor Dead Time(s) specifies

Dead Time(s) the dead time of a neighbor router at the
DCC interface.
l If the local router fails to receive the
hello packets from the connected
neighbor router within the time specified
in DCC Neighbor Dead Time(s), it
considers that the neighbor router is
unavailable.
l DCC Neighbor Dead Time(s) should
be set to a value that is a minimum of
twice the value of DCC Hello Timer
(s).
l In the case of adjacent NEs, DCC
Neighbor Dead Time(s) must be set to
the same value. Otherwise, the OSPF
protocol fails to operate normally.
DCC 1 to 65535 5 DCC Retransmission Timer(s) specifies

Retransmission the interval for transmitting a request
Timer(s) through the DCC interface to retransmit the
link state advertisement (LSA) packets.

DCC Delay(s) 1 to 3600 1 l DCC Delay(s) specifies the delay time

to transmit the LSA packets through the
DCC interface.
l The LSA packets in the LSA database of
the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the age
of the LSA packets based on the value of
DCC Delay(s).
LAN Hello Timer 1 to 255 10 l DCC Hello Timer(s) specifies the hello
(s) packet timer at the LAN interfaces.
l The hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l LAN Hello Timer(s) determines the
interval for the hello packet timer of the
NE to transmit the hello packets.
l In the case of two interconnected NEs,
LAN Hello Timer(s) must be set to the
same value.
LAN Neighbor 1 to 65535 40 l LAN Neighbor Dead Time(s) specifies

Dead Time(s) the dead time of a neighbor router at the
LAN interface.
l If the local router fails to receive the
hello packets from the connected
neighbor router within the time specified
in LAN Neighbor Dead Time(s), it
considers that the neighbor router is
unavailable.
l LAN Neighbor Dead Time(s) should be
set to a value that is a minimum of two
times the value of LAN Neighbor Dead
Time(s).
l In the case of adjacent NEs, DCC
Neighbor Dead Time(s) must be set to
the same value. Otherwise, the OSPF
protocol fails to operate normally.

LAN 1 to 65535 5 LAN Retransmission Timer(s) specifies

Retransmission the time for transmitting a request for
Timer(s) retransmission of the LSA packets through
the LAN interface.
LAN Delay(s) 1 to 3600 1 l LAN Delay(s) specifies the delay time

to transmit the LSA packets through the
LAN interface.
l The LSA packets in the LSA database of
the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the age
of the LSA packets based on the value of
LAN Delay(s).
Port Type lan lan l Displays the port type.

l lan indicates the Ethernet NM interface.
Use Flag Disabled Disabled l Specifies whether to enable the OSPF at

Enabled the Ethernet NM interface.
l If this parameter is set to Enabled, it
indicates that the Ethernet NM interface
is interconnected with other equipment.
OSPF Import Direct route - l Specifies the import route type.

Route Type Static route l Direct route: the route detected by the
RIP route link layer protocol.
l Static route: the route manually
configured by the network
administrator.
l RIP route: the route detected by the
routing protocol.
l Set this parameter as required.
Related Tasks

This topic describes the parameters that are used for configuring the proxy ARP.
Navigation Path

2. Click the Proxy ARP tab.
Parameters for configuring the proxy ARP

Proxy ARP Disabled Disabled l The proxy ARP enables the NEs in the
Enabled same network segment but different
domains to communicate with each
other.
l To realize communication between such
NEs, the source NE sends the ARP
broadcast packet to address the route to
the destination NE. The NE with the
proxy ARP function enabled checks the
routing table after sensing the ARP
broadcast packet. If the routing table
contains the destination address that the
ARP broadcast packet looks for, the NE
returns an ARP spoofing packet, which
enables the NE that sends the ARP
broadcast packet to consider that the
MAC address of the NE that returns the
ARP spoofing packet is the MAC
address of the destination NE. In this
manner, the packet that is to be sent to
the destination NE is first sent to the NE
with the proxy ARP function enabled
and then forwarded to the destination
NE.
Related Tasks
B.3.10 Parameter Description: OSI Management_Network Layer

Parameter
This topic describes the parameters that are related to the network layer of the OSI protocol
model.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
2. Click the Network Layer Parameters tab.

Network Layer Parameters


NE.
Configuration Role L1 L1 l Configuration Role cannot be set to

L2 ES.
l An NE whose Configuration Role is set
to L1 cannot function as a neighbor of an
NE in the other area. It uses a route in the
local area only and access the other area
by distributing the default route of the
nearest L2 NE.
l An NE whose Configuration Role is set
to L2 can function as a neighbor of an
NE in the other area and can use a route
in the backbone area. The backbone area
is a collection that is formed by
consecutive L2 NEs. That is, the L2 NE
of all the roles must be consecutive
(connected to each other).
Current Role - - This parameter indicates the current role.
Related Tasks

This topic describes the parameters that are related to OSI routing tables.
Navigation Path
2. Click the Routing Table tab.
Parameters for Routing Tables

Port - - This parameter indicates the port used for

OSI communication.
Data Link Layer - - This parameter indicates the protocol that is

used at the data link layer.

Adjacency No. - - l This parameter specifies the identifier of

the adjacency that is set up by two NEs
through the OSI protocol. One adjacency
number corresponds to an OSI
adjacency.
l The value is dynamically allocated by
the NE.
Adjacency Type - - This parameter indicates the type of the

adjacency.
Adjacency State - - This parameter indicates the state of the

adjacency.
Peer End Area ID - - This parameter indicates the area ID that is

contained in the NSAP address of the
opposite NE.
Peer End System - - This parameter indicates the system ID of

ID the opposite NE. Generally, the system ID
is the MAC address.
Destination Area - - This parameter indicates the area ID of the

ID destination NE.
Destination SYSID - - This parameter indicates the system ID of

the destination NE. Generally, the system
ID is the MAC address.
Metric - - ++This parameter indicates the number of

hops that reach the destination NE or
destination area.
Adjacency No.1 - - This parameter indicates the number of the

adjacent link that is connected to the
destination NE.
Adjacency No.2 - - This parameter indicates the number of the

adjacent link that is connected to the
destination NE.
Related Tasks

This topic describes the parameters that are related to the OSI tunnels.

Navigation Path
2. Click the OSI Tunnel tab.
Parameters for OSI Tunnel Attributes

Remote IP Address - - This parameter indicates the IP address of

the opposite end of the OSI tunnel.
LAPD Actor User User l This parameter specifies the LAPD

Network actor.
l If the adjacent NEs run the OSI protocol,
they can perform the LAPD negotiation
only when the LAPD actor is set to
User at one end and is set to Network at
the other end.
Efficient LAPD - - This parameter indicates whether the

Enable current LAPD is enabled.
Configurable Enabled Enabled This parameter specifies whether the LAPD

LAPD Enable Disabled is enabled.
LAPD Parameters
Remote IP Address - - This parameter indicates the IP address of

the opposite end of the OSI tunnel.
L2 Wait Time to 1 to 20 1 l This parameter specifies L2 Wait Time

Retry(s) to Retry(s).
l L2 Wait Time to Retry(s) indicates the
interval for retransmitting packets at the
LAPD link layer.
l L2 Wait Time to Retry(s) needs to be
set according to the network situation. If
the network is in good situation, L2 Wait
Time to Retry(s) can be set to a smaller
value. Otherwise, it is recommended that
you set L2 Wait Time to Retry(s) to a
greater value.
l This parameter needs to be set according
to the planning information. In normal
cases, it is recommended that you use the
default value.

L2 Retry Times 2 to 6 3 l This parameter specifies L2 Retry

Times.
l L2 Retry Times indicates the maximum
number of packet retransmission
attempts at the LAPD link layer.
l L2 Retry Times needs to be set
according to the network situation. If the
network is in good situation, L2 Retry
Times can be set to a smaller value.
Otherwise, it is recommended that you
set L2 Retry Times to a greater value.
default value.
L3 Hello Timer(s) 1 to 100 3 l This parameter specifies L3 Hello

Timer(s).
l L3 Hello Timer(s) indicates the Hello
packet timer at the LAPD link network
layer. It is used for periodical
transmission of the Hello packets.
l The Hello timer determines the interval
for transmitting the Hello packets once.
L3 Hello Timer(s) needs to be set
network is in good situation, L3 Hello
Timer(s) can be set to a greater value.
set L3 Hello Timer(s) to a smaller value.
default value.

L3 ES Timer(s) 1 to 200 50 l This parameter specifies L3 ES Timer

(s).
l L3 ES Timer(s) indicates the ES
configuration timer at the LAPD link
network layer. It is used for setting the
time to transmit the configuration
information on the ES route.
l L3 ES Timer(s) needs to be set
network is in good situation, L3 ES
Timer(s) can be set to a greater value.
set L3 Hello Timer(s) to a smaller value.
default value.
L3 IS Timer(s) 1 to 200 10 l This parameter specifies L3 IS Timer

(s).
l L3 IS Timer(s) indicates the IS
configuration timer at the LAPD link
network layer. It is used for setting the
time to transmit the configuration
information through the L1/L2 router.
l L3 IS Timer(s) needs to be set according
to the network situation. If the network
is in good situation, L3 IS Timer(s) can
be set to a greater value. Otherwise, it is
recommended that you set L3 IS Timer
(s) to a smaller value.
default value.

L3 Hold Timer(s) 2 to 63 5 l This parameter specifies L3 Hold Timer

(s).
l L3 Hold Timer(s) indicates the hold
timer at the LAPD link network layer.
l L3 Hold Timer(s) needs to be set
network is in good situation, L3 Hold
Timer(s) can be set to a smaller value.
set L3 IS Timer(s) to a greater value.
default value.
COST 1 to 63 20 l This parameter specifies COST.

l COST indicates the overhead value of
the virtual LAPD that corresponds to the
OSI tunnel.
l The overhead value determines whether
this link is perverted. If the overhead
value is smaller, this link has a higher
priority to be selected.
l This parameter needs to set according to
the planning information.
Related Tasks
B.3.13 Parameter Description: DCN Management_Bandwidth

Management
This topic describes the parameters that are used for bandwidth management of the inband DCN.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
2. Click the Bandwidth Management tab.

Parameters for Bandwidth Management

Ethernet Board 2 to 4094 4094 l The equipment on the traditional DCN

VLAN ID can be connected to the NMS through the
SCC board, but the OptiX RTN 950 can
also be connected to the NMS through an
Ethernet interface. If an Ethernet port is
used to carry the network management
information, the NE differentiates the
network management information and
Ethernet service information according
to the VLAN ID.
l If the default VLAN ID of the inband
DCN conflicts with the VLAN ID in the
service, the VLAN ID of the inband DCN
can be changed manually. The same
VLAN ID must be, however, is used on
the network-wide inband DCN.
Bandwidth(Kbit/s) 64 to 1000 512 Specifies the bandwidth for inband DCN

messaging on the Ethernet link.
E1 Port - - The OptiX RTN 950 does not support this

Bandwidth(Kbit/s) parameter.
Tunnel Bandwidth - - The OptiX RTN 950 does not support this
(Kbit/s) parameter.
IF Port Bandwidth 64 to 1000 512 Specifies the bandwidth for inband DCN
(Kbit/s) messaging on the radio link.
Related Tasks
A.6.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN

This topic describes the parameters that are used for setting ports of the inband DCN.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
2. Click the Port Settings tab.

Parameters for Setting FE or GE Ports

Port Name - - This parameter indicates the name of the FE

or GE port.
Enabled Status Enabled Enabled l This parameter specifies whether the FE

Disabled or GE port is enabled.
l The inband DCN can transmit the
network management information over
the link only after the inband DCN
function is enabled at the FE or GE ports
Parameters for Setting IF Ports

Port Name - - This parameter indicates the name of the IF

port.
Enabled Status Enabled Enabled l This parameter specifies whether the IF

Disabled port is enabled.
l The inband DCN can transmit the
network management information over
the link only after the IF ports at both
ends of a link are enabled on the inband
DCN.
Related Tasks
A.6.11 Configuring the Enable Status of the Inband DCN Function on Ports

This topic describes the parameters that are used for setting a protocol of the inband DCN.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree, and then choose
2. Click the Protocol Settings tab.
Parameters for Setting a Protocol

Port Name - - Displays the port name.

Protocol Type IP IP l If the values of Protocol Type are

HWECC different from each other, the equipment
at both ends cannot be interconnected
with each other. Therefore, Protocol
Type must be set to the same value for
the equipment at both ends of a link.
to the planning information. Generally,
it is recommended that you set this
parameter to IP.
Related Tasks

This section describes the parameters for configuring access control.
Navigation Path
l In the NE Explorer, select the NE from the Object Tree and then choose
l Click the Access Control tab.
Parameters
Port Name - - Displays the Ethernet ports that support this

function.
Enabled Status Disabled Disabled l Specifies the enabling status of the port.
Enabled l If this parameter is set to Enabled, this
port can be used to support access of the
management information from the
NMS.
l If this parameter is set to Disabled, this
port cannot be used to support access of
the management information from the
NMS.
IP Address - 0.0.0.0 Specifies the IP address of the port.
Subnet Mask - 0.0.0.0 Specifies the submask of the port.

Related Tasks
B.3.17 Parameter Description: Access Control

This topic describes the parameters that are used for access control of the NMS.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Access
Parameters for Ethernet Access Control

The First Network Enabled Enabled After The First Network Port is set to
Port Disabled Enabled for Ethernet access, the NE can
access the NMS through the Ethernet port.
Parameters for Access Control over Serial Ports

Enable Serial Port Selected Selected After Enable Serial Port Access is
Access Deselected selected, the NE can access the NMS or
command lines through the serial port.
Access Command Selected Deselected If Access Command Line is selected, the

Line Deselected serial interface can be used to access the
command line terminal.
Access NM Selected Selected If Access NM is selected, the serial interface

Deselected can be used to access the NMS.
Baud Rate 1200 9600 l This parameter specifies the data

2400 transmission rate in the communications
through serial ports.
4800
9600 rate of the serial port at the opposite end,
19200 and the rates at both ends must be the
38400 same.
57600
115200
B.3.18 Parameter Description: LCT Access Control

This topic describes the parameters that are used for LCT access control.

Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Security > LCT Access
Parameters for LCT Access Control


NE.
LCT Access Access Allowed Access Allowed l No NMS user logs in to the NE. In this
Control Switch Disable Access case, when the LCT requests an LCT
user to log in to the NE, the NE does not
check the status of LCT Access Control
Switch, and directly allows the LCT user
to log in to the NE.
l An NMS user first logs in to the NE. In
this case, when the LCT requests an LCT
user to log in to the NE, the NE
determines whether to allow the LCT
user to log in to the NE through the LCT
according to the status of LCT Access
Control Switch.
l An LCT user first logs in to the NE. In
this case, when the NMS requests an
NMS user to log in to the NE, the NMS
user can directly log in to the NE. After
the NMS user successfully logs in to the
NE, the online LCT user is not affected.
l When both the LCT user and NMS user
log in to the NE, the online LCT user is
not affected after LCT Access Control
Switch is set to Disable Access.
B.4 Radio Link Parameters

This topic describes the parameters that are related to radio links.
B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
This topic describes the parameters that are related to the XPIC function.
This topic describes the parameters that are used for creating an IF N+1 protection group.
This topic describes the parameters that are related to IF N+1 protection.

This topic describes the parameters that are used for creating an IF 1+1 protection group.
This topic describes the parameters that are related to IF 1+1 protection.
This topic describes the parameters that are used for configuring the IF/ODU.

Workgroup_Creation
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
2. Click the XPIC tab.
3. Click New.
Parameters
IF Channel 7M - l This parameter specifies the working

Bandwidth 14M bandwidth of the radio link.
28M l When this parameter is set to 56M, the
high-power ODU must be used.
56M
l The OptiX RTN 950 does not support
7M and 14M.
Polarization - - l This parameter indicates the polarization

direction-V direction of a radio link.
l It is recommended that you install the
Polarization
two IFX2 boards that form an XPIC
direction-H
workgroup in the slots that are at the
same layer or in the same column, and
set the IF port on the IFX2 board that has
a smaller slot number to Link ID-V and
the IF port on the other IFX2 board to
Link ID-H.
Link ID-V 1 to 4094 1 l Set Link ID-V and Link ID-H.

l A link ID is an identifier of a radio link
and is used to prevent the radio links
between sites from being wrongly
connected.
l When the link ID received by an NE is
different from the link ID set for the NE,
the NE reports an MW_LIM alarm and
inserts the AIS.

Link ID-H 2 l These two parameters are set according

to the planning information. These two
parameters must be set to different
values, but Link ID-V must be set to the
same value at both ends of a link and
Link ID-H must also be set to the same
value at both ends of a link.
Transmit Power - - l This parameter specifies the transmit

(dBm) power of an ODU. The value of this
parameter must not exceed the rated
power range supported by the ODU.
l The transmit power of the ODU must be
set to the same value at both ends of a
radio link.
l Consider the receive power of the ODU
at the opposite end when you set this
parameter. Ensure that the receive power
of the ODU at the opposite end can
ensure stable radio services.
Maximum - - l This parameter specifies the maximum

Transmit Power transmit power of the ODU. This
(dBm) parameter cannot be set to a value that
exceeds the nominal power rang of the
ODU in the guaranteed capacity
modulation module..
l This parameter is set to limit the
maximum transmit power of the ODU
within this preset range.
l The maximum transmit power adjusted
by using the ATPC function should not
exceed this value.

Transmission - - l This parameter indicates the channel

Frequency(MHz) central frequency.
l The value of this parameter must not be
less than the sum of the lower transmit
frequency limit supported by the ODU
and a half of the channel spacing, and
must not be more than the difference
between the upper transmit frequency
limit supported by the ODU and a half of
the channel spacing.
T/R Spacing(MHz) - - l This parameter specifies the spacing

between the transmit frequency and the
receive frequency of an ODU to prevent
mutual interference between the
transmitter and the receiver.
l If Station Type of the ODU is TX
high, the transmit frequency is one T/R
spacing higher than the receive
frequency. If Station Type of the ODU
is TX low, the transmit frequency is one
T/R spacing lower than the receive
frequency.
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 A valid T/R spacing value is determined
by the ODU itself, and the T/R spacing
should be set according to the technical
specifications of the ODU.
l The T/R spacing of the ODU should be
set to the same value at both the ends of
a radio link.
Transmission unmute unmute l When this parameter is set to mute, the

Status mute ODU does not transmit microwave
signals but can normally receive
microwave signals.
l When this parameter is set to unmute,
the ODU normally transmits and
receives microwave signals.
l In normal cases, this parameter is set to
unmute.

ATPC Enabled Disabled Disabled l This parameter specifies whether the

Enabled ATPC function is enabled.
l When this parameter is set to Enabled
and if the RSL at the receive end is 2 dB
higher or lower than the central value
between the ATPC upper threshold and
the ATPC lower threshold at the receive
end, the receiver notifies the transmitter
to decrease or increase the transmit
power until the RSL is within the range
that is 2 dB higher or lower than the
central value between the ATPC upper
threshold and the ATPC lower threshold.
l The settings of the ATPC attributes must
be consistent at both ends of a radio link.
l In the case of areas where fast fading
severely affects the radio transmission, it
is recommended that you set this
parameter to Disabled.
l During the commissioning process, set
this parameter to Disabled to ensure that
the transmit power is not changed. After
the commissioning, re-set the ATPC
attributes.
ATPC Upper -75.0 to -20.0 -45.0 l The central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold is set as the expected receive
ATPC Lower -35.0 to -90.0 -70.0 power.
Threshold(dBm)
l It is recommended that you set ATPC
Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
value between the ATPC upper
threshold and the ATPC lower threshold
and 10 dB.
l You can set the ATPC upper threshold
only when ATPC Automatic
Threshold Enable Status is set to
Disabled.

ATPC Automatic Disabled Disabled l This parameter specifies whether the

Threshold Enable Enabled automatic threshold function is enabled.
Status l If this parameter is set to Enabled, the
equipment automatically uses the preset
ATPC upper and lower thresholds
according to the work mode of the radio
link.
Related Tasks

Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
2. Click the XPIC tab.

Group ID - - This parameter indicates the ID of the work

group.
Polarization - - This parameter indicates the IF port to which

direction-V the polarization direction V corresponds.
Link ID-V - - This parameter indicates the link ID to

which the polarization direction V
corresponds.

direction-H the polarization direction H corresponds.
Link ID-H - - This parameter indicates the link ID to

which the polarization direction H
corresponds.

IF Channel 7M - l IF Channel Bandwidth refers to the

Bandwidth 14M channel spacing of the corresponding
radio links.
28M
l The OptiX RTN 950 does not support
56M 7M and 14M.
Power to Be -90.0 to -20.0 -10.0 l This parameter is used to set the

Received -V(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 power±3
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.
l When this parameter takes the default
value, the antenna misalignment
indicating function is disabled.

Power to Be -90.0 to -20.0 -10.0 l This parameter is used to set the

Received -H(dBm) expected receive power of the ODU and
is mainly used in the antenna alignment
stage. After this parameter is set, the NE
exceeds the range of receive power±3

modulation module..
exceed this value.

Transmit Power - - l This parameter indicates or specifies the

(dBm) transmit power of the ODU. This
parameter cannot be set to a value that
exceeds the nominal power range of the
ODU.
l The transmit power of the ODU should
be set to the same value at both ends of
a radio link.
Transmission - - l This parameter indicates or specifies the

Frequency(MHz) transmit frequency of the ODU, namely,
the channel central frequency.
less than the sum of the lower TX
between the upper TX frequency limit
supported by the ODU and a half of the
channel spacing.
l The difference between the transmit
frequencies of both the ends of a radio
link should be one T/R spacing.

T/R Spacing(MHz) - - l This parameter indicates or specifies the

spacing between the transmit frequency
and receive frequency of the ODU to
prevent mutual interference between the
transmitter and receiver.
l If the ODU is a Tx high station, the
transmit frequency is one T/R spacing
higher than the receive frequency. If the
ODU is a Tx low station, the transmit
frequency is one T/R spacing lower than
the receive frequency.
spacing, this parameter is set to 0,
indicating that the T/R spacing
supported by the ODU is used.
radio link.
Transmission unmute unmute l This parameter indicates or specifies the

Status mute transmit status of the ODU.
l If this parameter is set to mute, the
transmitter of the ODU does not work
but can normally receive microwave
signals.
l If this parameter is set to unmute, the
ODU can normally transmit and receive
microwave signals.
unmute.
Parameters for Hybrid/AM Configuration

Group ID - - This parameter indicates the ID of the work

group.

direction the polarization direction H or the
polarization direction V corresponds.

AM Enable Status Disabled Disabled l When this parameter is set to Disabled,

Enabled the radio link uses only the specified
modulation scheme. In this case, you
need to select Manually Specified
Modulation Mode.
l When this parameter is set to Enabled,
the radio link uses the corresponding
modulation scheme according to the
channel conditions.
Hence, the Hybrid radio can ensure the
reliable transmission of the E1 services and
provide bandwidth adaptively for the
Ethernet services when the AM function is
enabled.
Modulation Mode QPSK - This parameter specifies the highest-gain

of the Guarantee 16QAM modulation scheme that the AM function
AM Capacity supports. This parameter is set according to
32QAM the planning information. Generally, the
64QAM value of this parameter is determined by the
128QAM bandwidth of the services that need to be
transmitted over the Hybrid radio and the
256QAM availability of the radio link that
corresponds to this modulation scheme.
NOTE
Modulation Mode of the Full AM Capacity
must be higher than Modulation Mode of the
Guarantee AM Capacity.
This parameter is valid only when AM
Enable Status is set to Enabled.

of the Full AM 16QAM modulation scheme that the AM function
Capacity supports. This parameter is set according to
256QAM availability of the radio link that
NOTE

Manually Specified QPSK QPSK This parameter specifies the modulation

Modulation Mode 16QAM scheme that the radio link uses for signal
transmission.
32QAM
64QAM Enable Status is set to Disabled.
128QAM
256QAM
Transmit-End - - Displays the modulation mode at the

Modulation Mode transmit end.
Receive-End - - Displays the modulation mode at the receive

Modulation Mode end.
Guarantee E1 - - l When AM Enable Status is set to

Capacity Enabled, this parameter depends on IF
Channel Bandwidth and Modulation
Mode of the Guarantee AM Capacity
and cannot be set.
l When AM Enable Status is set to
Disabled, this parameter depends on IF
Channel Bandwidth and Manually
Specified Modulation Mode and
cannot be set.
Full E1 Capacity 1 to 75 - This parameter specifies the number of E1

services that can be transmitted in Hybrid
work mode. The value of this parameter
cannot exceed the Guarantee E1
Capacity.
The Full E1 Capacity must be set to the
same value at both ends of a radio link.
Parameters for ATPC Management

Group ID - - This parameter indicates the object to be set.

ATPC Enable Disabled - l This parameter specifies whether the

Status Enabled ATPC function is enabled.
l If this parameter is set to Enabled and if
the RSL at the receive end is 2 dB higher
or lower than the central value between
the ATPC upper threshold and the ATPC
lower threshold at the receive end, the
receiver notifies the transmitter to
decrease or increase the transmit power
until the RSL is within the range that is
2 dB higher or lower than the central
value between the ATPC upper threshold
and the ATPC lower threshold.
attributes.
ATPC Upper -75.0 to -20.0 - l Set the central value between the ATPC
threshold to a value for the expected
ATPC Lower -35.0 to -90.0 - receive power.
Threshold(dBm)
Lower Threshold(dBm) o the
and the ATPC lower threshold and 10
dB.
l You can set this parameter only when
ATPC Automatic Threshold Enable
Status is set to Disabled.

ATPC Automatic Disabled - l This parameter specifies whether the

Threshold Enable Enabled ATPC automatic threshold function is
Status enabled.
l If this parameter is set to Enabled, the
link.
l If this parameter is set to Disabled, you
need to manually set ATPC Upper
Threshold(dBm) and ATPC Lower
Threshold(dBm).
Related Tasks
A.8.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link

This topic describes the parameters that are used for creating an IF N+1 protection group.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
2. Click Create.

WTR time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
l When the time after the former working
channel is restored to normal reaches the
set WTR time, a revertive switching
occurs.
l It is recommended that you use the
default value.

Enabled Enabled Enabled l This parameter specifies whether the SD

Disabled switching function of N+1 protection is
enabled.
the SD condition is considered as a
trigger condition of protection
switching.
l It is recommended that you set this
parameter to Enabled.
Slot Mapping Relation Parameters

Select Mapping Work Unit Work Unit l This parameter specifies the mapping
Direction Protection Unit direction of N+1 protection.
Select Mapping - - l In the case of N+1 protection, map N IF

Way ports as Work Unit and map the
remaining IF port as Protection Unit.
Mapped Board - - This parameter indicates the working unit

and protection unit that have been set.
Related Tasks

This topic describes the parameters that are related to IF N+1 protection.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1

Protection Group Parameters

Protection Group - - This parameter indicates the ID of the

ID protection group.
WTR Time(s) 300 to 720 - l This parameter indicates or specifies the

WTR time.
occurs.
default value.
SD Enable Enabled - l This parameter indicates or specifies

Disabled whether the SD switching function of N
+1 protection is enabled.
the SD condition is considered as a
trigger condition of protection
switching.
Protocol Status - - This parameter indicates the status of the

switching control protocol.
Protection Unit Parameters

Protection Unit - - This parameter indicates the protection unit.
Line - - This parameter indicates the information

about the working board or protection
board.
Switching Status - - This parameter indicates the switching state.
Protected Unit - - This parameter indicates the protected unit.
Remote/Local End - - This parameter indicates the local end or

Indication remote end.
Related Tasks


This topic describes the parameters that are used for creating an IF 1+1 protection group.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
2. Click Create.
Parameters
Working Mode HSB HSB l This parameter specifies the working

FD mode of the IF 1+1 protection.
SD l In HSB 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.
l In FD mode, the system uses two
channels that have a frequency spacing
between them, to transmit and receive
the same signal. The remote end selects
signals from the two received signals.
With FD protection, the impact of the
fading on signal transmission is reduced.
l In SD 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 SD
protection, the impact of the fading on
signal transmission is reduced.
l The FD mode and SD mode are
compatible with the HSB switching
function.

Revertive Mode Revertive Mode Revertive Mode l This parameter specifies the revertive
Non-Revertive mode of the IF 1+1 protection.
Mode l When this parameter is set to Revertive
Mode, 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.
l When this parameter is set to Non-
Revertive Mode, 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.
parameter to Revertive Mode.
WTR Time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
occurs.
l You can set WTR Time(s) only when
Revertive Mode is set to Revertive
Mode.
default value.
Enable Reverse Enabled Enabled l This parameter indicates whether the

Switching Disabled reverse switching function is enabled.
l When both the main IF board and the
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
Enabled 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.
l Generally, if Working Mode is set to
HSB, it is recommended that you set this
parameter to Disabled; if Working
Mode is set to SD, it is recommended
that you set this parameter to Enabled.

Working Board - - This parameter specifies the working board

of the protection group.
Protection Board - - This parameter specifies the protection

board of the protection group.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s), and Enable Reverse
Switching must be set to the same value at both ends of a radio hop.
Related Tasks

This topic describes the parameters that are related to IF 1+1 protection.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection Group Parameters



Working Mode HSB - l This parameter indicates the working

FD mode of the created IF 1+1 protection
group.
SD
l In HSB 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.
l In FD mode, the system uses two
channels that have a frequency spacing
between them, to transmit and receive
the same signal. The remote end selects
signals from the two received signals.
With FD protection, the impact of the
fading on signal transmission is reduced.
l In SD 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 SD
protection, the impact of the fading on
signal transmission is reduced.
l The FD mode and SD mode are
compatible with the HSB switching
function.
Revertive Mode Revertive Mode - l This parameter indicates or specifies the

Non-Revertive revertive mode of the protection group.
Mode l When this parameter is set to Revertive
Mode, 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 Mode, the NE that is in the
parameter to Revertive Mode.


WTR time.
occurs.
Revertive Mode is set to Revertive
Mode.
default value.
Enable Reverse Enabled - l This parameter indicates or specifies

Switching Disabled whether the reverse switching function is
enabled.
l When both the main IF board and the
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
Enabled and the reverse switching
conditions are met, the IF 1+1 protection
switching occurs at the source end.
Working Mode is set to HSB or SD.
Switching Status of - - l This parameter indicates the switching

Device state on the equipment side.
l Unknown is displayed when the
switching state on the channel side is not
queried or not obtained after a query.
Switching Status of - - l This parameter indicates the switching

Channel state on the channel side.
l Unknown is displayed when the
switching state on the channel side is not
queried or not obtained after a query.
Active Board of - - This parameter indicates the current

Device working board on the equipment side.
Active Board of - - This parameter indicates the current

Channel working board on the channel side.
NOTE
Each of the parameters Working Mode, Revertive Mode, and WTR Time(s) must be set to the same
value at both ends of a radio hop.


Unit - - This parameter indicates the working board

and protection board.
Slot Mapping - - This parameter indicates the names and

Relation ports of the working board and protection
board.
Working Status of - - This parameter indicates the working state

Device on the equipment side.
Signal Status of - - This parameter indicates the status of the

Channel link signal.
Related Tasks

This topic describes the parameters that are used for configuring the IF/ODU.
Navigation Path
1. In the NE Explorer, select the NE and then choose Configuration > Link

Parameters for Configuring the IF

Work Mode 1,4E1,7MHz,QPSK - l This parameter indicates or specifies the

2,4E1,3.5MHz, work mode of the radio link in "work
16QAM mode number, service capacity, channel
spacing, modulation mode" format.
3,8E1,14MHz,QPS
K l This parameter is set according to the
planning information. The work modes
4,8E1,7MHz, of the IF boards at the two ends of a radio
16QAM link must be the same.
5,16E1,28MHz,QP NOTE
SK This parameter is not applicable to the IFU2
6,16E1,14MHz, board and the IFX2 board.
16QAM
7,STM-1,28MHz,
128QAM
8,E3,28MHz,QPSK
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

Link ID 1 to 4094 1 l This parameter indicates or specifies the

ID of a radio link. As the identifier of a
radio link, this parameter is used to
prevent incorrect connections of radio
links between sites.
l If the value of Received Radio Link
ID does not match the preset value of
Link ID at the local end, the local end
inserts the AIS signal to the downstream
direction of the service. At the same
time, the local end reports MW_LIM
alarm to the NMS, indicating that the
link IDs do not match.
l Each radio link of an NE should have a
unique link ID, and the link IDs at both
ends of a radio link should be the same.
Received Link ID - - This parameter indicates the received ID of

the radio link.
NOTE
When the radio link becomes faulty, this
parameter is displayed as an invalid value.
IF Channel 7M - IF Channel Bandwidth indicates the

Bandwidth 14M channel spacing of the corresponding radio
link. This parameter is set according to the
28M planning information.
56M NOTE
This parameter is not applicable to the IF1 board.
AM Mode - - This parameter is not applicable to the

OptiX RTN 950.
AM Enable Status Disabled Disabled l When this parameter is set to Disabled,

Enabled the radio link uses only the specified
Modulation Mode.
the radio link uses the corresponding
channel conditions.
l Hence, the Hybrid radio can ensure the
reliable transmission of the E1 services
and provide bandwidth adaptively for
the Ethernet services when the AM
function is enabled.
NOTE

Manually Specified QPSK QPSK This parameter specifies the modulation

Modulation Mode 16QAM scheme that the radio link uses for signal
transmission.
32QAM
64QAM
Enable Status is set to Disabled.
128QAM NOTE
256QAM This parameter is not applicable to the IF1 board.
Modulation Mode QPSK QPSK l This parameter is valid only when AM

of the Guarantee 16QAM Enable Status is set to Enabled.
AM Capacity l This parameter specifies the lowest-gain
32QAM
modulation scheme that the AM function
64QAM supports. This parameter is set according
128QAM to the planning information. Generally,
256QAM the value of this parameter is determined
by the service transmission bandwidth
that the Hybrid radio must ensure and the
availability of the radio link that
NOTE
Modulation Mode QPSK - l This parameter is valid only when AM

of the Full AM 16QAM Enable Status is set to Enabled.
Capacity l This parameter specifies the highest-
32QAM
gain modulation scheme that the AM
64QAM function supports. This parameter is set
128QAM according to the planning information.
256QAM Generally, the value of this parameter is
determined by the bandwidth of the
services that need to be transmitted over
the Hybrid radio and the availability of
the radio link that corresponds to this
modulation scheme.
NOTE
Modulation Mode of the Full AM
Capacity must be higher than Modulation
Mode of the Guarantee AM Capacity.
NOTE
Enable E1 Priority Disabled Disabled l This parameter specifies whether to

Enabled enable the E1 priority function.
l This parameter is valid only when AM
NOTE

Guarantee E1 - - l If AM Enable Status is set to

Capacity Enabled, this parameter needs to be set
according to IF Channel Bandwidth,
Modulation Mode of the Guarantee
AM Capacity, and the actually
transmitted services.
l If AM Enable Status is set to
Disabled, this parameter needs to be set
according to IF Channel Bandwidth,
Manually Specified Modulation
Mode, and the actually transmitted
services.
NOTE
Full E1 Capacity - - l This parameter specifies the number of

transmitted E1 services in Modulation
Mode of the Full AM Capacity.
l This parameter is valid if Enable E1
Priority is set to Enabled.
l E1 service bandwidth in full capacity
mode ≤ Service bandwidth in full
capacity mode - Service bandwidth in
guarantee capacity mode + E1 service
bandwidth in guarantee capacity mode.
In addition, the number of E1 services in
full capacity modulation mode should be
smaller than or equal to the maximum
number of E1 services in full capacity
modulation mode.
l The Full E1 Capacity must be set to the
NOTE

Parameters for Configuring the RF

TX Frequency - - l This parameter indicates or specifies the

(MHz) transmit frequency of the ODU, namely,
the channel central frequency.
less than the sum of the lower TX
between the upper TX frequency limit
supported by the ODU and a half of the
channel spacing.
frequencies of both the ends of a radio
link should be one T/R spacing.
Range of TX - - l This parameter indicates the range of the

Frequency(MHz) transmit frequency of the ODU.
l The Range of Frequency(MHz)
depends on the specifications of the
ODU.
Actual TX - - This parameter indicates the actual transmit

Frequency(MHz) frequency of the ODU.
Actual RX - - This parameter indicates the actual receive


T/R Spacing(MHz) - - l This parameter specifies the spacing

between the transmit frequency and the
receive frequency of an ODU to prevent
interference between them.
l If Station Type of the ODU is TX
high, the TX frequency is one T/R
spacing higher than the receive
frequency. If Station Type of the ODU
is TX low, the TX frequency is one T/R
spacing lower than the receive
frequency.
spacing, set this parameter to 0,
indicating that the T/R spacing supported
by the ODU is used.
set to the same value at both the ends of
a radio link.
Actual T/R - - This parameter indicates the actual T/R

Spacing(MHz) spacing of the ODU.

Parameters for Configuring the Power

TX Power(dBm) - - l This parameter indicates or specifies the

transmit power of the ODU. This
parameter cannot be set to a value that
exceeds the nominal power range of the
ODU.
l This parameter cannot take a value
greater than the preset value of
Maximum Transmit Power(dBm).
be set to the same value at both ends of a
radio link.
Range of TX - - This parameter indicates the range of the

Power(dBm) transmit power of the ODU.
Actual TX Power - - l This parameter indicates the actual

(dBm) transmit power of the ODU.
l If the ATPC function is enabled, the
queried actual transmit power may be
different from the preset value.
Actual RX Power - - This parameter indicates the actual receive

(dBm) power of the ODU.
TX Status Unmute Unmute l This parameter indicates or specifies the

Mute transmit status of the ODU.
l When this parameter is set to Mute, the
signals.
l When this parameter is set to Unmute,
the ODU can normally transmit and
receive microwave signals.
l In normal cases, it is recommended that
you set this parameter to unmute.
Actual TX Status - - This parameter indicates the actual transmit

status of the ODU.

Equipment Information
Frequency(GHz) - - This parameter indicates the frequency band

where the ODU operates.
Equip Type - - l This parameter indicates the equipment

type of the ODU.
l PDH and SDH indicate the transmission
capacity only and are irrelevant to the
type of transmitted service.
Station Type - - l This parameter indicates whether the

ODU is a Tx high station or a Tx low
station.
l The transmit frequency of a Tx high
station is one T/R spacing higher than the
transmit frequency of a Tx low station.
Produce SN - - This parameter indicates the manufacturing

serial number and the manufacturer code of
the ODU.
Transmission - - This parameter indicates the level of the

Power Type output power of the ODU.
Related Tasks
B.5 Multiplex Section Protection Parameters

This topic describes the parameters that are related to multiplex section protection (MSP).
This topic describes the parameters that are used for creating linear MSP groups.
This topic describes the parameters that are related to linear MSP groups.

This topic describes the parameters that are used for creating linear MSP groups.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear
MS from the Function Tree.
2. Click Create.


Protection Type 1+1 Protection 1+1 Protection l This parameter specifies the protection
1:N Protection type of the linear MSP group.
l In the case of 1+1 linear MSP, one
working channel and one protection
channel are required. When the working
channel fails, the service is switched
from the working channel to the
protection channel.
l In the case of 1:N linear MSP, N working
channels and one protection channel are
required. Normal services are
transmitted on the working channels and
extra services are transmitted on the
protection channel. When one working
channel fails, the services are switched
from this working channel to the
protection channel, and the extra
services are interrupted.
l If extra services need to be transmitted
or several working channels are
required, select 1:N Protection.
Switching Mode Single-Ended Single-Ended l This parameter specifies the switching

Switching Switching (1+1 mode of the linear MSP.
Dual-Ended Protection) l In single-ended mode, the switching
Switching Dual-Ended occurs only at one end and the state of
Switching (1:N the other end remains unchanged.
Protection) l In dual-ended mode, the switching
occurs at both ends at the same time.
l If the linear MSP type is set to 1:N
Protection, Switching Mode can be set
to Dual-Ended Switching only.

Revertive Mode Non-Revertive Non-Revertive (1+1 l This parameter specifies the revertive
Revertive Protection) mode of the linear MSP.
Revertive (1:N l When this parameter is set to
Protection) 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
parameter to Revertive.
Protection, Revertive Mode can be set
to Revertive only.
WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
preset WTR time, a revertive switching
occurs.
Revertive Mode is set to Revertive.
default value.
SD Enable Enabled Enabled l This parameter indicates or specifies

Disabled whether the switching at the SD alarm of
the linear MSP is enabled.
the B2_SD alarm is considered as a
switching condition.

Protocol Type New Protocol New Protocol l The new protocol is supported at the
Restructure Protocol early stage, and the mainstream protocol
version is used currently.
l The restructure protocol optimizes the
new protocol and provides better
measures to protect the new protocol,
thus ensuring that the new protocol runs
in a better manner.
l The new protocol is more mature, and
the restructure protocol complies with
the standard. It is recommended that you
use the new protocol.
l You must ensure that the interconnected
NEs run the protocols of the same type.

Select Mapping West Working Unit West Working Unit This parameter specifies the mapping
Direction West Protection direction of the linear MSP.
Unit
Select Mapping - - l This parameter specifies the mapping

Mode board and port in the mapping direction.
l If the protection type is set to 1+1
Protection, only one line port can be
mapped as West Working Unit.
l Only one line port can be mapped as
West Protection Unit.
l The line port mapped as West
Protection Unit and the line port
mapped as West Working Unit should
be configured for different boards if
possible.
Mapped Board - - This parameter indicates the preset slot

mapping relations, including the mapping
direction and the corresponding mapping
mode.
Related Tasks


This topic describes the parameters that are related to linear MSP groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS


Protection Type 1+1 Protection - l This parameter indicates the protection

1:N Protection type of the linear MSP group.
l In the case of 1+1 linear MSP, one
working channel and one protection
channel are required. When the working
channel fails, the service is switched
from the working channel to the
protection channel.
l In the case of 1:N linear MSP, N working
channels and one protection channel are
required. Normal services are
transmitted on the working channels and
extra services are transmitted on the
protection channel. When one working
channel fails, the services are switched
from this working channel to the
protection channel, and the extra
services are interrupted.
l If extra services need to be transmitted
or several working channels are
required, select 1:N Protection.
Switching Mode Single-Ended - l This parameter indicates or specifies the

Switching switching mode of the linear MSP.
Dual-Ended l In single-ended mode, the switching
Switching occurs only at one end and the state of
the other end remains unchanged.
l In dual-ended mode, the switching
occurs at both ends at the same time.
Protection, Switching Mode can be set
to Dual-Ended Switching only.

Revertive Mode Non-Revertive - l This parameter indicates or specifies the

Revertive revertive mode of the linear MSP.
l When this parameter is set to
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.
Protection, Revertive Mode can be set
to Revertive only.

WTR time.
occurs.
default value.
SD Enable Enabled - l This parameter indicates or specifies

Disabled whether the reverse switching function
is enabled.
the B2_SD alarm is considered as a
switching condition.

Protocol Type New Protocol - l The new protocol is supported at the

Restructure Protocol early stage, and the mainstream protocol
version is used currently.
l The restructure protocol optimizes the
new protocol and provides better
measures to protect the new protocol,
thus ensuring that the new protocol runs
in a better manner.
l You must ensure that the interconnected
NEs run the protocols of the same type.
l The new protocol is more mature, and
the restructure protocol complies with
the standard. It is recommended that you
use the new protocol.
Protocol Status - - This parameter indicates the protocol status

of the linear MSP.

Protection Unit - - This parameter indicates that which of the

units, namely, the west protection unit or the
west working unit, is currently in the
protection status.
West Line - - This parameter indicates the west protection

- unit and the west working unit of the linear
MSP.
West Switching - - This parameter indicates the switching

Status status of the line.
Protected Unit - - This parameter indicates the working

channel protected by the current protection
channel.
Remote/Local End - - When Switching Mode is set to Dual-

Indication Ended Switching, the central office end
that issues the switching command is
displayed.
Related Tasks

B.6 SDH/PDH Service Parameters

This topic describes the parameters that are related to SDH/PDH services.
This parameter describes the parameters that are used for creating point-to-point cross-
connections.
B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation
This topic describes the parameters that are used for creating SNCP services.
B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into
SNCP Services
This topic describes the parameters that are used for converting normal services into SNCP
services.
This topic describes the parameters that are used for configuring SDH services (namely,
configuring cross-connections).
This topic describes the parameters that are used for controlling SNCP services.
This section describes the parameters for TU_AIS insertion.

This parameter describes the parameters that are used for creating point-to-point cross-
connections.
Navigation Path
l Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH
Service Configuration from the Function Tree.
l Click Create.
Parameters
Level VC12 VC12 l This parameter specifies the level of the

VC3 service to be created.
VC4 l If the service is an E1 service or a data
service that is bound with VC-12
channels, set this parameter to VC12.
l If the service is a data service that is
bound with VC-3 channels, set this
parameter to VC3.
l If all the services on a VC-4 channel pass
through the NE, set this parameter to
VC4.

Direction Bidirectional Bidirectional l When this parameter is set to

Unidirectional Unidirectional, create only the cross-
connections from the service source to
the service sink.
Bidirectional, create the cross-
connections from the service source to
the service sink and the cross-
connections from the service sink to the
service source.
you set this parameter to Bidirectional.
Source Slot - - This parameter specifies the slot of the

service source.
Source VC4 - - l This parameter specifies the number of

the VC-4 channel where the service
source is located.
l This parameter cannot be set when
Source Slot is set to the slot of the
tributary board.
Source Timeslot - - l This parameter indicates the timeslot

Range(e.g.1,3-6) range of the service source.
l This parameter can be set to a number or
several numbers. When setting this
parameter to several numbers, use the
comma (,) to separate the discrete
numbers, or use the endash (-) to
represent a consecutive number. For
example, the numbers 1, and 3-6 indicate
1, 3, 4, 5, and 6.
Sink Slot - - This parameter specifies the slot of the

service sink.
Sink VC4 - - l This parameter specifies the number of

the VC-4 channel where the service sink
is located.
l This parameter cannot be set when Sink
Slot is set to the slot of the tributary
board.

Sink Timeslot - - l This parameter specifies the timeslot

Range(e.g.1,3-6) range of the service sink.
1, 3, 4, 5, and 6.
E1 Priority High - l This parameter specifies the priority of

Low an E1 service.
None l This parameter is available only if the E1
priority function is enabled for the ports
configured in the cross-connections.
l If E1 Priority is set to High,
transmission of the E1 service is ensured
in any modulation scheme.
l If E1 Priority is set to Low, transmission
of the E1 service is ensured only in full-
capacity modulation scheme
Activate Yes Yes l This parameter specifies whether to

Immediately No immediately activate the configured
service.
l To immediately deliver the configured
SDH service to the NE, set this parameter
to Yes.
Related Tasks
B.6.2 Parameter Description: SDH Service Configuration_SNCP

Service Creation
This topic describes the parameters that are used for creating SNCP services.
Navigation Path
l Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH
l Click Create SNCP Service.


Service Type SNCP SNCP This parameter indicates that the type of the
service to be created is SNCP.

Unidirectional Unidirectional, create only the cross-
connections from the SNCP service
source to the SNCP service sink.
Bidirectional, create the cross-
connections from the SNCP service
source to the service sink and the cross-
connections from the SNCP service sink
to the service source.
Level VC12 VC12 l This parameter specifies the level of the

VC3 SCNP service to be created.
channels, set this parameter to VC12.
bound with VC-3 channels, set this
parameter to VC3.
through the NE, set this parameter to
VC4.
Hold-off Time 0 to 100 0 l This parameter specifies the duration of

(100ms) the hold-off time.
l When a line is faulty, SNCP switching
can be performed on the NE after a delay
of time to prevent the situation where the
NE performs SNCP switching and other
protection switching at the same time.
l If multiple link-based protection
schemes, such as SNCP, 1+1 protection,
and N+1 protection, are available at the
same time, the hold-off time needs to be
set to a duration that is longer than the
switching duration for the multiple link-
based protection schemes.
l If only the SNCP scheme is available, it
is recommended that you set the hold-off
time to 0.

Revertive Mode Non-Revertive Non-Revertive l This parameter specifies whether to

Revertive switch the service to the original working
channel after the fault is rectified.
l If this parameter is set to Revertive, the
service is switched from the protection
channel to the original working channel.
If this parameter is set to Non-
Revertive, the service is not switched
from the protection channel to the
original working channel.
occurs.
default value.

service source.

source is located.
tributary board.

1, 3, 4, 5, and 6.

service sink.


is located.
board.

1, 3, 4, 5, and 6.
Configure SNCP Selected Deselected l After the Configure SNCP Tangent

Tangent Ring Deselected Ring checkbox is selected, you can
quickly configure the SNCP service for
the SNCP ring tangent point.
you do not select this checkbox.
Activate Selected Selected l This parameter specifies whether to

Immediately Deselected immediately activate the configured
SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
Related Tasks
B.6.3 Parameter Description: SDH Service

Configuration_Converting Normal Services Into SNCP Services
This topic describes the parameters that are used for converting normal services into SNCP
services.

Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH
2. If a bidirectional SDH service is created, select this service in Cross-Connection. Right-
click the selected service and choose Expand to Unidirectional from the shortcut menu.
3. Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.

Service Type SNCP SNCP This parameter indicates that the type of the
service to be created is SNCP.
Direction Unidirectional - This parameter indicates the direction of the

SNCP service.
Level VC12 - l This parameter indicates the level of the

VC3 SNCP service.
channels, the parameter value is VC12.
bound with VC-3 channels, the
parameter value is VC3.
through the NE, the parameter value is
VC4.
Hold-off Time 0 to 100 0 l This parameter specifies the duration of

(100ms) the hold-off time.
time to 0.

Revertive Mode Non-Revertive Non-Revertive l This parameter specifies whether to

Revertive switch the service to the original working
channel after the fault is rectified. If this
parameter is set to "Revertive", the
occurs.
default value.

service source.

source is located.
tributary board.

1, 3, 4, 5, and 6.


service sink.

is located.
board.

1, 3, 4, 5, and 6.
Configure SNCP - - After the Configure SNCP Tangent Ring

Tangent Ring checkbox is selected, you can quickly
configure the SNCP service for the SNCP
ring tangent point.
Activate - - l This parameter indicates whether to

Immediately immediately activate the configured
SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
Related Tasks

This topic describes the parameters that are used for configuring SDH services (namely,
configuring cross-connections).
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service

Cross-Connection Parameters

VC3 service.
channels, VC12 is displayed.
bound with VC-3 channels, VC3 is
displayed.
through the NE, VC4 is displayed.
Source Slot - - This parameter indicates the slot of the

service source.
Source Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service source.
Sink Slot - - This parameter indicates the slot of the

source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service sink.
E1 Priority High - l This parameter specifies the priority of

Low an E1 service.
None l This parameter is available only if the E1
priority function is enabled for the ports
configured in the cross-connections.
l If E1 Priority is set to High,
transmission of the E1 service is ensured
in any modulation scheme.
l If E1 Priority is set to Low, transmission
of the E1 service is ensured only in full-
capacity modulation scheme
Activation Status Yes - This parameter indicates whether to activate

No the service.
Bound Group - - The OptiX RTN 950 does not support this
Number parameter.
Lockout Status - - The OptiX RTN 950 does not support this
parameter.
Trail Name - - The OptiX RTN 950 does not support this
parameter.
Schedule No. - - The OptiX RTN 950 does not support this
parameter.

Parameters for Automatically Generated Cross-Connections


VC3 service.
displayed.
Source Slot - - This parameter indicates the slot of the

service source.
Source Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service source.
Sink Slot - - This parameter indicates the slot of the

source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service sink.
Lockout Status - - The OptiX RTN 950 does not support this
parameter.
Trail Name - - The OptiX RTN 950 does not support this
parameter.
Schedule No. - - The OptiX RTN 950 does not support this
parameter.
Related Tasks

This topic describes the parameters that are used for controlling SNCP services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service


Service Type - - This parameter indicates the service

protection type of the protection group.
Source - - This parameter indicates the timeslots where

the working service source and protection
service source of the protection group are
located.
Sink - - This parameter indicates the timeslots where

the working service sink and protection
service sink of the protection group are
located.

VC3 service.
displayed.
Current Status - - This parameter indicates the current

switching mode and switching status of the
services of the protection group.
Revertive Mode Revertive - l This parameter indicates or specifies the

Non-Revertive revertive mode of the service.
l This parameter determines whether to
switch the service from the protection
channel to the original working channel
after the fault is rectified.


WTR time.
occurs.
default value.
Hold-off Time 0 to 100 - l This parameter indicates or specifies the

(100ms) duration of the hold-off time.
time to 0.

Initiation TIM Null l This parameter indicates or specifies the

Condition EXC conditions that trigger the protection
switching of the service.
SD
l If TIM is selected, the SNCP service
UNEQ considers the HP_TIM alarm as an
Null automatic switching condition.
l If EXC is selected, the SNCP service
considers the B3_EXC or BIP_EXC
alarm as an automatic switching
condition.
l If SD is selected, the SNCP service
considers the B3_SD or BIP_SD alarm
as an automatic switching condition.
l If UNEQ is selected, the SNCP service
considers the HP_UNEQ or LP_UNEQ
alarm as an automatic switching
condition.
l It is recommended that you set Initiation
Condition to the same condition for
Working Service and Protection
Service.
l The protection switching conditions in
Initiation Condition are optional values
not included in the default values, and
they are set according to the planning
information.
Trail Status - - This parameter indicates the status of the

working service and protection service of
the protection group.
Service Grouping - - The OptiX RTN 950 does not support this
parameter.
Active Channel - - This parameter indicates whether the

working service or protection service is
currently received by the protection group.
Trail Name - - Displays the trail name.
Related Tasks

This section describes the parameters for TU_AIS insertion.

Navigation Path
In the NE Explorer, select the IFU2/IFX2 board from the Object Tree and choose Alarm >
Triggered Alarm Insertion from the Function Tree.
Table B-1 Parameters on the main interface
Port - - Displays the slot ID of the IFU2/IFX2 board

and the ID of the IF port.
High Channel - - Displays the higher order path number of the

IFU2/IFX2 board.
Low Channel - - Displays the lower order path number of the

IFU2/IFX2 board.
Insert TU_AIS to Enable Disabled If this parameter is set to Enable for an E1

E1_AIS Disabled path and the E1 path detects the E1_AIS
alarm, the TU_AIS alarm is inserted into
this path.
Related Tasks
B.7 Clock Parameters

This topic describes the parameters that are related to clocks.

This topic describes the parameters that are related to the priority table of a clock source.
This topic describes the parameters that are related to a clock subnet.
This topic describes the parameters that are related clock quality.
B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control
This topic describes the parameters that are related to SSM output control.
B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status
This topic describes the parameters that are used for enabling the clock ID function.
B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
This topic describes the parameters that are related to clock source restoration.
B.7.7 Parameter Description: Clock Source Switching_Clock Source Switching
This topic describes the parameters that are related to the switching status of a clock source.

B.7.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions

This section describes the parameters that are related to the switching conditions of clock sources.
B.7.9 Parameter Description: Output Phase-Locked Source of the External Clock Source
This topic describes the parameters of the output phase-locked source of the external clock
source.
This topic describes the parameters that are related to the clock synchronization status.

This topic describes the parameters that are related to the priority table of a clock source.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Clock Source Priority.
2. Click the System Clock Source Priority List tab.
Parameters
Clock Source - - l External clock source

1 indicates the external
clock source at the
CLK or TIME1 port on
the CST or CSH board
in physical slot 7.
External clock source
2 indicates the external
clock source at the
CLK or TIME1 port on
the CST or CSH board
in physical slot 8.
l The internal clock
source is always at the
lowest priority and
indicates that the NE
works in the free-run
mode.
l The clock sources and
the corresponding
clock source priority
levels are determined
according to the clock
synchronization
schemes.

External Clock Source 2Mbit/s 2Mbit/s l This parameter

Mode 2MHz indicates the type of
the external clock
source signal.
according to the
external clock signal.
In normal cases, the
external clock signal is
a 2 Mbit/s signal.
Synchronous Status Byte SA4 to SA8 SA4 l This parameter is valid

only when External
Clock Source Mode is
set to 2Mbit/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 needs
to be set only when the
SSM or extended SSM
is enabled. In normal
cases, the external
clock sources use the
SA4 to transmit the
SSM.
Clock Source Priority - - Displays the priority

Sequence (1 is the sequence of clock sources.
highest) 1 indicates the highest
clock source priority.
Related Tasks

This topic describes the parameters that are related to a clock subnet.
Navigation Path
Clock Subnet Configuration.
2. Click the Clock Subnet tab.

Parameters for Setting a Clock Subnet

Affiliated Subnet 0 to 255 0 l This parameter is used

when the clock subnet
needs to be created on
the NMS.
l The NEs that trace the
same clock source
should be allocated
with the same clock
subnet ID.

Protection Status Start Extended SSM Stop SSM Protocol l The SSM protocol is a
Protocol scheme used for
Start Standard SSM synchronous
Protocol management on an
SDH network and
Stop SSM Protocol indicates that the SSM
is passed by the lower
four bits of the S1 byte
and can be exchanged
between the nodes.
The SSM protocol
ensures that the
equipment
automatically selects
the clock source of the
highest quality and
highest priority, thus
preventing mutual
clock tracing.
l After the standard
SSM protocol is
started, the NE first
performs the
protection switching
on the clock source
quality level
information provided
by the S1 byte. If the
quality level of the
clock source is the
same, the NE then
performs the
priority table. That is,
the NE selects an
unlocked clock source
that is of the highest
quality and highest
priority from all the
current available clock
sources as the clock
source to be
synchronized and
traced by the local
station.
l If the SSM protocol is
stopped, it indicates

that the S1 byte is not

used. The NE selects
and switches a clock
source only according
to the sequence
specified in the
priority table. The
clock source of the
highest priority is used
as the clock source to
be traced.
l After the SSM
protocol is stopped,
each NE performs the
on the clock according
to the preset priority
table of the clock
source only when the
clock source of a
higher priority is lost.
Clock Source - - This parameter indicates

the clock source that is
configured for an NE. In
Clock Source Priority,
you can set whether to add
or delete a clock source.

Clock Source ID (None) (None) l This parameter is valid

1 to 15 only when the
extended SSM
protocol is started.
l Clock source IDs are
allocated for the
following clock
sources only:
– External clock
source
– 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
Related Tasks

This topic describes the parameters that are related clock quality.
Navigation Path
2. Click the Clock Quality tab.

Parameters for Clock Source Quality


the name of the
configured clock source.
In Clock Source
Priority, you can set
whether to add or delete a
clock source.
Configuration Quality Unknown Automatic Extraction This parameter specifies

Synchronization Quality the quality level that is
G.811 Clock Signal configured for the clock
source. This function is
G.812 Transit Clock required only in a special
Signal scenario or in a test.
G.812 Local Clock Signal Generally, this parameter
G.813 SDH Equipment need not be set.
Timing Source (SETS)
Signal
Do Not Use For
Synchronization
Automatic Extraction
Clock Quality - - This parameter indicates

the clock source quality
signal received by the NE.
The NE extracts the clock
source quality signal from
the S1 byte of each clock
source.
Parameters for Manual Setting of 0 Quality Level


the name of the NE.

Manual Setting of 0 Do Not Use For Do Not Use For This parameter specifies
Quality Level Synchronization Synchronization the clock quality whose
G.811 Reference Clock level is manually set to
zero.
Between G.811 Reference
Clock and G.812 Transit l Do Not Use For
Clock Synchronization: the
notification
G.812 Transit Clock information in the
Between G.812 Transit reverse direction of the
Clock and G.812 Local selected
Clock synchronization clock
G.812 Local Clock source to avoid direct
mutual locking of
Between G.812 Local
adjacent NEs.
Clock and synchronous
equipment timing source l G.811 Reference
(SETS) Clock: the clock signal
specified in ITU-T G.
SETS Clock
811.
Between synchronous
l Between G.811
equipment timing source
Reference Clock and
(SETS) and quality
G.812 Transit Clock:
unavailable
lower than the quality
level of the clock
signal specified in
ITU-T G.811 but
higher than the quality
level of the transit
exchange clock signal
812.
l G.812 Transit Clock:
the transit exchange
clock signal specified
in ITU-T G.812.
l Between G.812
Transit Clock and G.
812 Local Clock:
level of the transit
exchange clock signal
812 but higher than the
quality level of the
local exchange clock
signal specified in
ITU-T G.812.
l G.812 Local Clock:
the local exchange


in ITU-T G.812.
l Between G.812 Local
Clock and
synchronous
equipment timing
source (SETS): lower
than the quality level
of the local exchange
in ITU-T G.812 but
level of the clock
signal of the SETS.
l SETS Clock: the clock
signal of the SETS.
l Between synchronous
equipment timing
source (SETS) and
quality unavailable:
level of the clock
signal of the SETS but
level unavailable in the
synchronous timing
source.
Related Tasks
B.7.4 Parameter Description: Clock Subset Setting_SSM Output

Control
This topic describes the parameters that are related to SSM output control.
Navigation Path
2. Click the SSM Output Control tab.

Parameters
Line Port - - l This parameter

indicates the name of
the line clock port.
l Line Port: indicates
the SSM quality
information output
port of the current
available line clock
source and the external
clock source. This
output port can
transmit the quality
information of the
clock source by
outputting the S1 byte
to the downstream NE.
Control Status Enabled Enabled l This parameter is valid

Disabled only when the SSM
protocol or the
extended SSM
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,
Disabled.
Related Tasks
B.7.5 Parameter Description: Clock Subset Setting_Clock ID

Enabling Status
This topic describes the parameters that are used for enabling the clock ID function.

Navigation Path
2. Click the Clock ID Status tab.
Parameters
Line Port - - l This parameter

indicates the name of
the line clock port.
l Line Port: indicates
the SSM quality
information output
port of the current
available line clock
source and the external
clock source. This
output port can
transmit the quality
information of the
clock source by
outputting the S1 byte
to the downstream NE.
Enabled Status Enabled Enabled l This parameter is valid

Disabled only when the
extended SSM
l This parameter
indicates whether the
clock source ID is
output at the line port.
l If the line ports are
connected to the NEs
in the same clock
subnet and if the
extended SSM
protocol is started on
the opposite NE, this
parameter is set to
Enabled. Otherwise,
Disabled.
Related Tasks

B.7.6 Parameter Description: Clock Source Switching_Clock Source

Restoration Parameters
This topic describes the parameters that are related to clock source restoration.
Navigation Path
Clock Source Switching.
2. Click the Clock Source Reversion Parameter tab.
Parameters

the name of the NE.

Higher Priority Clock Auto-Revertive Auto-Revertive l When the quality of a

Source Reversion Mode Non-Revertive higher-priority clock
source degrades, the
NE automatically
switches the clock
source to a lower-
priority clock source.
If this parameter is set
to Auto-Revertive,
the NE automatically
switches the clock
source to the higher-
priority clock source
when this higher-
priority clock source
restores. If this
parameter is set to
Non-Revertive, the
NE does not
automatically switch
the clock source to the
higher-priority clock
source when this
higher-priority clock
source restores.
l Correct setting of
Clock Source
Switching Condition
ensures the reliability
of the clock source
switching. To improve
the clock quality,
select Auto-
Revertive. Otherwise,
to prevent jitter of the
clock, generally, it is
Non-Revertive.

Clock Source WTR 0 to 12 5 l This parameter

Time(min.) specifies the duration
from the time when the
clock source
restoration is detected
to the time when the
clock source switching
is triggered. This
parameter is used to
avoid frequent
switching of the clock
source due to
instability of the clock
source state within a
short time.
only when Higher
Priority Clock
Source Reversion
Mode is set to Auto-
Revertive.
Related Tasks

Switching
This topic describes the parameters that are related to the switching status of a clock source.
Navigation Path
Clock Source Switching.
2. Click the Clock Source Switching tab.
Parameters

the name of the clock
source.
Effective Status Valid - This parameter indicates

Invalid whether the clock source
is valid.

Lock Status Lock - l This parameter

Unlock specifies the locking
status of the clock
source in the priority
table.
l Lock: A clock source
in the priority table is
in the locked state. The
clock source in the
locked state cannot be
switched.
l Unlock: A clock
source in the priority
table is in the unlocked
state. The clock source
in the unlocked state
can be switched.
Switching Source - - This parameter indicates

the clock source to be
traced by the NE after the
switching.
Switching Status Normal - This parameter indicates

Manual Switching the switching status of the
current clock source.
Forced Switching

Switching Conditions
This section describes the parameters that are related to the switching conditions of clock sources.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Clock > Clock Source Switching from the Function Tree.
2. Click the Clock Source Switching Condition tab.
Parameters
NE Name - - Displays the name of the

NE.
Clock Source - - Displays the clock source.

AIS Alarm Generated Yes No l The default value is

No recommended.
set to Yes, it indicates
that clock source
switching occurs if the
clock source reports
the AIS alarm.
set to No, it indicates
that no clock source
the AIS alarm.
B1 BER Threshold- - - The parameter is invalid.

Crossing Generated
RLOS,RLOF,OOF/ Yes Yes This parameter indicates

RLOC Alarms that clock switching
Generated occurs when the clock
source reports the RLOS,
RLOF, OOF, or LOC
alarm.
CV Threshold-Crossing - - The parameter is invalid.

Generated
CV Threshold - - The parameter is invalid.
B2-EXC Alarm Yes No l The default value is

Generated No recommended.
set to Yes, it indicates
that clock source
the B2-EXC alarm.
set to No, it indicates
that no clock source
the B2-EXC alarm.
Related Tasks

B.7.9 Parameter Description: Output Phase-Locked Source of the

External Clock Source
This topic describes the parameters of the output phase-locked source of the external clock
source.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Phase-Locked Source Output by External Clock.
Parameters
2M Phase-Locked External Clock Source 1 - This parameter indicates

Source Number External Clock Source 2 the number of the external
clock source output of the
NE.
External Clock Output 2Mbit/s 2Mbit/s l This parameter

Mode 2MHz specifies the mode of
the output clock.
to be set according to
the requirements of the
interconnected
equipment. Generally,
the output external
clock signal is a 2
Mbit/s signal.
External Clock Output SA4 to SA8 ALL l This parameter is valid

Timeslot ALL only when External
Clock Output Mode
is set to 2Mbit/s.
l This parameter
indicates which bit of
the TS0 in odd frames
of the output clock
signal is used to
transmit the SSM.
to ALL, it indicates
that all the bits of the
TS0 are used to
transmit the SSM.
you use the default
value.

External Source Output Threshold Disabled Threshold Disabled l This parameter

Threshold Not Inferior to G.813 specifies the lowest
SETS Signal quality of the output
clock. If the clock
Not Inferior to G.812 quality is lower than
Local Signal the value of this
Not Inferior to G.812 parameter, it indicates
Transit Clock Signal that the external clock
Not Inferior to G.811 source does not output
Clock Signal any clock signal.
to Threshold
Disabled, it indicates
that the external clock
source always outputs
the clock signal.
you use the default
value.
2M Phase-Locked No Failure Condition No Failure Condition l This parameter

Source Fail Condition AIS specifies the failure
condition of the 2
LOF Mbit/s phase-locked
AIS OR LOF clock source.
you use the default
value.
2M Phase-Locked Shut Down Output Shut Down Output l This parameter is valid
Source Fail Action 2M Output S1 Byte only when 2M Phase-
Unavailable Locked Source Fail
Condition is not set to
Send AIS No Failure
Condition.
l This parameter
specifies the operation
of the 2 Mbit/s phase-
locked loop (PLL)
when the 2 Mbit/s
phase-locked clock
source meets the
failure conditions.
you use the default
value.

Related Tasks

This topic describes the parameters that are related to the clock synchronization status.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Synchronization Status.
Parameters

the name of the NE.
NE Clock Working - - This parameter indicates

Mode the working mode of the
NE clock.
S1 Byte Synchronization - - This parameter indicates

Quality Information the synchronization
quality information of the
S1 byte.
S1 Byte Synchronous - - This parameter indicates

Source the clock synchronization
source of the S1 byte.
Synchronous Source - - This parameter indicates

the synchronization
source.

Data Output Method in Normal Data Output Normal Data Output l When all the reference
Holdover Mode Mode Mode timing signals are lost,
Keep the Latest Data the slave clock
changes to the
holdover mode. At this
time, the slave clock
works based on the
latest frequency
information stored
before the reference
timing signals are lost.
Then, the frequency of
the oscillator drifts
slowly to ensure that
the offset between the
frequency of the slave
clock and the reference
frequency is very
small. As a result, the
impact caused by the
drift is limited within
the specified
requirement.
l Normal Data Output
Mode: The slave clock
works based on the
latest frequency
information stored
timing signals are lost,
and the holdover
duration depends on
the size of the phase-
locked clock register
on the equipment. The
holdover duration can
be up to 24 hours.
l Keep the Latest Data:
The slave clock works
in holdover mode all
the time based on the
latest frequency
information stored
timing signals are lost.
Related Tasks

B.8 RMON Parameters

This topic describes the parameters that are related to RMON performances.

This topic describes the parameters that are related to RMON statistics groups.
B.8.2 Parameter Description: RMON Performance_History Group
This topic describes the parameters that are related to RMON history groups.
B.8.3 Parameter Description: RMON Performance_History Control Group
This topic describes the parameters that are related to RMON history control groups.
This topic describes the parameters that are related to RMON setting.

This topic describes the parameters that are related to RMON statistics groups.
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
2. Click the Statistics Group tab.
Parameters
Object - - This parameter specifies the object to be

monitored.
Sampling Period 5 to 150 5 This parameter specifies the duration of the

monitoring period.
Display Selected Deselected l This parameter specifies the method of

Accumulated Deselected displaying the performance events.
Value l If this parameter is not selected, the
displayed value is an increment
compared to the value that is collected in
last sampling period and stored in the
register.
l If this parameter is selected, the
displayed value is an absolute value that
is currently stored in the register.

Display Mode Graphics List l This parameter specifies the method of

List displaying the performance events.
l If this parameter is set to Graphics, the
number of performance events to be
monitored at each time cannot be more
than 10, and the unit should be the same.
Legend Color - l This parameter indicates the description

Description of different colors.
Display Mode is set to Graphics.
Event - - l This parameter indicates the queried

performance events.
Display Mode is set to List.
Related Tasks
A.14.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
B.8.2 Parameter Description: RMON Performance_History Group

This topic describes the parameters that are related to RMON history groups.
Navigation Path
2. Click the History Group tab.
Parameters
Object - - The parameter indicates the object to be

monitored.
Ended from/to - - This parameter specifies the start time and

end time of the monitoring period.
History Table 30-Second 30-Second This parameter specifies the monitoring

Type 30-Minute period.
Custom Period 1
Custom Period 2

Display Mode Graphics List l This parameter specifies the method of

List displaying the performance events.
l If this parameter is set to Graphics, the
number of performance events to be
monitored at each time cannot be more
than 10, and the unit should be the same.
Legend Color - l This parameter indicates the description

Description of different colors.
Display Mode is set to Graphics.
Event - - l This parameter indicates the queried

performance events.
Display Mode is set to List.
Statistical Item - - This parameter indicates the performance

items to be monitored.
Statistical Value - - This parameter indicates the statistical value

of the monitored performance items.
Time Flag - - This parameter indicates the time point of

each performance event.
B.8.3 Parameter Description: RMON Performance_History Control

Group
This topic describes the parameters that are related to RMON history control groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History
Control Group.
Parameters
30-Second Enabled Disabled This parameter indicates or specifies

Disabled whether to enable the 30-Second
monitoring function.
30-Minute Enabled Enabled This parameter indicates or specifies

Disabled whether to enable the 30-Minute

Custom Period 1 Enabled Disabled This parameter indicates or specifies

Disabled whether to enable Custom Period 1.

Disabled whether to enable Custom Period 2.
Period Length(s) 300 to 43200 900(Custom Period l This parameter indicates or specifies the
(Custom Period 1) 1) monitoring period in Custom Period 1
300 to 86400 86400(Custom and Custom Period 2.
(Custom Period 2) Period 2) l The value must be an integer multiple of
30.
History Register 1 to 50 16 This parameter indicates or specifies the

Count 6(Custom Period 2) quantity of the history registers.
Related Tasks

This topic describes the parameters that are related to RMON setting.
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
l Click the RMON Setting tab.
Object Parameters
Object - - This parameter indicates the object to be

collected.
30-Second Enabled - This parameter indicates or specifies

Disabled whether to enable the 30-Second
NOTE
In the case of Object, 30-Second cannot be set.
30-Minute Enabled Disabled l This parameter indicates or specifies

l In RMON History Control Group of
the NE, if 30-Minute is set to Disabled,
Not Supported is displayed for this
parameter.

Custom Period 1 Enabled - l This parameter indicates or specifies

Disabled whether to enable the monitoring
function based on Custom Period 1.
the NE, if Custom Period 1 is set to
Disabled, Not Supported is displayed
for this parameter.
Custom Period 2 Enabled - l This parameter indicates or specifies

Disabled whether to enable the monitoring
function based on Custom Period 2.
the NE, if Custom Period 2 is set to
Disabled, Not Supported is displayed
for this parameter.
Event Parameters
Event - - This parameter indicates the performance

event to be monitored.
30-Second Enabled Disabled This parameter indicates or specifies

Disabled whether to enable the monitoring function
based on 30-Second.
30-Minute Enabled - This parameter indicates or specifies


based on Custom Period 1Custom Period
1 Monitor.

based on Custom Period 2Custom Period
2 Monitor.
Threshold Detect Report All Report All l This parameter indicates or specifies the
Do Not Detect threshold detection method.
Report Only the l If the number of detected events reaches
Upper Threshold the preset threshold, the events are
reported to the NMS. Otherwise, the
Report Only the events are not reported to the NMS.
Lower Threshold
l If an event does not support this
parameter, Not Supported is displayed.

Upper Threshold - - This parameter indicates or specifies the

upper threshold. If the number of
performance events exceeds the preset
upper threshold, the corresponding
performance events are reported.
Lower Threshold - - This parameter indicates or specifies the

lower threshold. If the number of
performance events is less than the preset
lower threshold, the corresponding
performance events are reported.
Threshold Unit - - This parameter indicates the unit of each

threshold of the performance events.
Related Tasks
A.14.4 Browsing the Performance Data in the History Group of an Ethernet Port
B.9 Parameters for Ethernet Services and Ethernet Features

on the Packet Plane
packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port
parameters, and QoS parameters.
B.9.1 Parameters for Ethernet Services

This topic describes the parameters that are related to Ethernet services.
B.9.2 Parameters for Ethernet Protocols
This topic describes the parameters that are related to the Ethernet protocol.
B.9.3 Parameters for the Ethernet OAM
This topic describes the parameters that are related to the Ethernet operation, administration and
maintenance (OAM).
B.9.4 QoS Parameters
This topic describes the parameters that are related to QoS.
B.9.5 Parameters for the Ports on Ethernet Boards
This section describes the parameters for the Ethernet ports on the packet plane.

This topic describes the parameters that are related to Ethernet services.

This topic describes the interface parameters that are used for creating an Ethernet line (E-Line)
service.

B.9.1.2 Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
This topic describes the parameters that are used for creating VLAN forwarding table items.
This topic describes the parameters that are used for creating an Ethernet local area network (E-
LAN) service.
This topic describes the parameters that are related to E-LAN services.
This topic describes the parameters that are used for creating a QinQ link.

This topic describes the interface parameters that are used for creating an Ethernet line (E-Line)
service.
Navigation Path
2. Click New.

Service ID 1 to 4294967294 - This parameter specifies

the ID of the E-Line
service.
Service Name - - This parameter specifies

the name of the E-Line
service.
Direction UNI-UNI UNI-UNI l This parameter

UNI-NNI specifies the direction
of the E-Line service.
NNI-NNI
according to the

BPDU Not Transparently Not Transparently l This parameter

Transmitted Transmitted specifies the
Transparently transparent
Transmitted transmission ID of the
bridge protocol data
unit (BPDU) packets.
It is used to indicate
whether the E-Line
service transparently
transmits the BPDU
packets.
l If the BPDU packets
are used as the service
packets and
transparently
transmitted to the
opposite end, set this
parameter to
Transparently
Transmitted.
l In other cases, set this
parameter to Not
Transparently
Transmitted.
according to the
MTU(byte) - - This parameter cannot be

set here.
Service Tag Role - - The OptiX RTN 950 does

not support this
parameter.

Source Port - - l This parameter is valid

only when Direction
is set to UNI-UNI or
UNI-NNI.
l Before setting this
parameter, check and
ensure that the
attributes in Ethernet
Interface of the port
are set correctly and
are the same as the
l The value of this
parameter cannot be
the same as the value
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

Source VLANs 1 to 4094 - l This parameter can be

set to null, a number,
or several numbers.
When setting this
parameter to several
numbers, use the
comma (,) to separate
the discrete numbers,
or use the endash (-) to
represent a
consecutive number.
For example, the
numbers 1, and 3-6
indicate 1, 3, 4, 5, and
6.
only when Direction
UNI-NNI.
l The number of
VLANs must be the
same value of Sink
VLANs. Otherwise,
you need to create a
VLAN forwarding
table for swapping
VLAN IDs.
to null, all the services
at the source port are
used as the service
source.
l If this parameter is not
set to null, only the
service that contains
the VLAN ID at the
source port can be used
as the service source.
Bearer Type QinQ Link QinQ Link l Uses the QinQ link to
carry the E-Line
service.
only when Direction
is set to UNI-NNI.

QinQ Link ID - - l Selects the QinQ link

ID.
l A QinQ link ID is
preset in QinQ Link.
only when Direction
is set to UNI-NNI.
Bearer Type 1 QinQ Link QinQ Link l Uses the QinQ link to
carry the E-Line
service.
only when Direction
is set to NNI-NNI.
QinQ Link ID 1 - - l Selects the QinQ link

ID of the first QinQ
link.
only when Direction
is set to NNI-NNI.
l The QinQ link ID is
Bearer Type 2 QinQ Link QinQ Link l Uses the QinQ link to
carry the E-Line
service.
only when Direction
is set to NNI-NNI.
QinQ Link ID 2 - - l Selects the QinQ link

ID of the second QinQ
link.
only when Direction
is set to NNI-NNI.
l The QinQ link ID is

Sink Port - - l This parameter is valid

only when Direction
is set to UNI-UNI.
l Before setting this
parameter, check and
ensure that the
attributes in Ethernet
Interface of the port
are set correctly and
are the same as the
l The value of this
parameter cannot be
the same as the value
of Source Port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

Sink VLANs 1 to 4094 - l This parameter is valid

only when Direction
is set to UNI-UNI.
l This parameter can be
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
l The number of
VLANs must be the
same value of Source
VLANs.
at the sink port are
used as the service
sink.
service that contains
the VLAN ID at the
sink port can be used
as the service sink.
Related Tasks
B.9.1.2 Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet


Service ID 1 to 4294967294 - This parameter indicates

the ID of the E-Line
service.
Service Name - - This parameter indicates

or specifies the name of
the E-Line service.
Source Node - - This parameter indicates

the source node.
Sink Node - - This parameter indicates

the sink node.

not support this
parameter.

set here.

BPDU Not Transparently - l This parameter

Transmitted indicates the
Transparently transparent
Transmitted transmission tag of the
bridge protocol data
unit (BPDU) packets.
This parameter is used
to indicate whether the
Ethernet line
transparently
transmits the BPDU
packets.
are used as the service
packets and
transparently
transmitted to the
opposite end, set this
parameter to
Transparently
Transmitted.
are used as the
protocol packets to
compute the spanning
tree topology of the
network, set this
parameter to Not
Transparently
Transmitted.
Deployment Status - - This parameter indicates

whether E-Line service is
deployed.
Parameters Associated with UNI Ports

Port - - This parameter indicates

the UNI port.

VLANs 1 to 4094 - This parameter indicates

or specifies the VLAN ID
of the UNI port.
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
only when Direction
UNI-NNI in the
process of creating an
E-Line service.
of the UNI work as the
service source or
service sink.
services of the UNI
port whose VLAN IDs
are included in the set
value of this parameter
work as the service
source or service sink.

Parameters Associated with NNI Ports

QinQ Link ID 1 to 4294967295 - l This parameter

indicates the QinQ link
ID of the QinQ link
connected to the NNI
port.
only when Direction
UNI-NNI in the
E-Line service.
Port - - l This parameter

indicates the NNI port.
only when Direction
UNI-NNI in the
E-Line service.
S-VLAN ID - - l This parameter

indicates or specifies
the VLAN ID of the
NNI port.
only when Direction
is set to UNI-NNI or
NNI-NNI in the
E-Line service.
l This parameter is
Parameters for the Port Attributes


the QinQ link ID of the
QinQ link connected to
the port.

Enable Port - - l This parameter

indicates whether to
enable the port.
l This parameter is
preset in General
Attributes of
Ethernet Interface.
Encapsulation Type Null - l This parameter

802.1Q indicates the
encapsulation type of
QinQ the port.
only when Direction
UNI-NNI in the
E-Line service.
to Null, the port
transparently
transmits the received
packets.
to 802.1Q, the port
identifies the packets
that comply with the
IEEE 802.1Q
standard.
to QinQ, the port
identifies the packets
that comply with the
IEEE 802.1 QinQ
standard.
l This parameter is
preset in General
Attributes of
Ethernet Interface.
TAG Tag Aware l This parameter

Access indicates the tag of the
port.
Hybrid
l This parameter is
preset in Layer 2
Attributes of
Ethernet Interface .


This topic describes the parameters that are used for creating VLAN forwarding table items.
Navigation Path
2. Click the VLAN Forwarding Table Item tab.
3. Click New.
Parameters for VLAN Forwarding Table Item

Source Interface Type V-UNI V-UNI This parameter specifies

the network attribute of
the source interface.
Source Interface - - This parameter specifies

the source interface.
Source VLAN ID 1 to 4094 - This parameter specifies

the VLAN ID of the
source service.
Sink Interface Type V-UNI V-UNI This parameter specifies

the network attribute of
the sink interface.
Sink Interface - - This parameter specifies

the sink interface.
Sink VLAN ID 1 to 4094 - This parameter specifies

the VLAN ID of the sink
service.
NOTE
l The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table item is
created. In this case, a service from Source Interface to Sink Interface carries the VLAN ID specified in
Sink VLAN ID when the service is transmitted from Sink Interface.
l The VLAN ID in a VLAN forwarding table item is converted unidirectionally and can be converted from
Source VLAN ID to Sink VLAN ID only. The VLAN ID can be converted bidirectionally only when the
other VLAN forwarding table item is configured reversely.
l In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion of
VLAN IDs.
Related Tasks


This topic describes the parameters that are used for creating an Ethernet local area network (E-
LAN) service.
Navigation Path
2. Click New.

Service ID 1 to 4294967294 - l This parameter

specifies the ID of the
E-LAN service.
l The OptiX RTN 950
supports simultaneous
creation of an E-LAN
service only.

the name of the E-LAN
service.
BPDU - - l This parameter

indicates the
transparent
transmission tag of the
BPDU packets.
l In the case of an E-
LAN service, this
parameter supports
only transparent
transmission of the
BPDU packets and
cannot be set
manually.
l Not Transparently
Transmitted
indicates that the
BPDU packets are
used as the protocol
packets to compute the
spanning tree topology
of the network.

Tag Type C-Awared C-Awared l C-Awared indicates

S-Awared that the packets are
learnt according to C-
Tag-Transparent Tag (the VLAN tag on
the client-side). To
create the 802.1q
bridge, set this
parameter to C-
Awared.
l S-Awared indicates
that the packets are
learnt according to S-
Tag (the VLAN tag at
the carrier service
layer). To create the
802.1ad bridge, set this
parameter to S-
Awared.
l Tag-Transparent
indicates that the
Ethernet packets are
directly and
transparently
transmitted no matter
they contain VLAN
tags or not. To create
the 802.1d bridge, set
this parameter to Tag-
Transparent.
according to the

Self-Learning MAC Enabled Enabled l This parameter

Address Disabled specifies whether to
enable the MAC
address self-learning
function.
l If the MAC self-
learning function of an
Ethernet LAN is
enabled, the Ethernet
LAN learns an MAC
address according to
the original MAC
address in the packet
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
Ethernet LAN is
disabled, a static MAC
address forwarding
table needs to be
configured.
Otherwise, the
Ethernet LAN fails to
forward the services.
MAC Address Learning - - l This parameter

Mode indicates the mode
used to learn an MAC
address.
l When the bridge uses
the SVL mode, all the
VLANs share one
MAC address table. If
the bridge uses the IVL
mode, each VLAN has
an MAC address table.

set here.

not support this
parameter.

Parameters for UNIs


the UNI port.
SVLAN 1 to 4094 - l This parameter

specifies the S-VLAN
ID of the UNI port.
only when Tag Type
is set to S-Awared.
according to the
VLANs/CVLAN 1 to 4094 - l This parameter

specifies the VLAN ID
of the UNI port.
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
of the UNI work as the
service source or
service sink.
services of the UNI
port whose VLAN IDs
are included in the set
work as the service
source or service sink.

Parameters of NNIs

only when Tag Type
is set to S-Awared.
SVLANs - - l This parameter

ID of the NNI port.
only when Tag Type
is set to S-Awared.
Parameters for the Split Horizon Group

Split Horizon Group ID - 1 l This parameter

indicates the ID of the
split horizon group.
l The default split
horizon group ID is 1
and cannot be set
manually.

Split Horizon Group - - l A split horizon group

Member member indicates the
logical port member in
the split horizon
group.
l The port members that
are added to the same
split horizon group
cannot communicate
with each other.
l The OptiX RTN 950
supports only the
division of the split
horizon group
members according to
the Ethernet physical
port.
l If a UNI or NNI logical
port of the 802.1ad
bridge is added to a
split horizon group
member, the physical
port that is mounted
with the logical port is
automatically added to
the split horizon group
member.
Related Tasks

This topic describes the parameters that are related to E-LAN services.
Navigation Path


Service ID 1 to 4294967294 - l This parameter

E-LAN service.
l The supports
simultaneous creation
of an E-LAN service
only.

the name of the E-LAN
service.
BPDU - - l This parameter

indicates the
transparent
transmission tag of the
BPDU packets.
l In the case of an E-
LAN service, this
parameter supports
only transparent
transmission of the
BPDU packets and
cannot be set
manually.
l Not Transparently
Transmitted
indicates that the
BPDU packets are
used as the protocol
packets to compute the
spanning tree topology
of the network.

Tag Type C-Awared C-Awared l C-Awared indicates

S-Awared that the packets are
learnt according to C-
Tag-Transparent Tag (the VLAN tag on
the client-side). To
create the 802.1q
bridge, set this
parameter to C-
Awared.
l S-Awared indicates
learnt according to S-
Tag (the VLAN tag at
the carrier service
layer). To create the
802.1ad bridge, set this
parameter to S-
Awared.
l Tag-Transparent
indicates that the
Ethernet packets are
directly and
transparently
transmitted no matter
they contain VLAN
tags or not. To create
the 802.1d bridge, set
this parameter to Tag-
Transparent.
Self-Learning MAC Enabled Enabled l This parameter

Address indicates whether to
enable the MAC
address self-learning
function.
l If the MAC self-
Ethernet LAN is
enabled, the Ethernet
LAN learns an MAC
address according to
the original MAC
address in the packet
and automatically
refreshes the MAC
address forwarding
table.

MAC Address Learning - - l This parameter

Mode indicates the mode
used to learn an MAC
address.
l When the bridge uses
the SVL mode, all the
VLANs share one
MAC address table. If
the bridge uses the IVL
mode, each VLAN has
an MAC address table.

set here.

not support this
parameter.
Parameters for UNIs


the UNI port.

ID of the UNI port.
only when Tag Type
is set to S-Awared.
according to the

VLANs/CVLAN 1 to 4094 - l This parameter

of the UNI port.
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, the E-LAN
service exclusively
uses the corresponding
UNI physical port.
That is, the entire port
is mounted to the
bridge.
to a non-null value,
only the
corresponding UNI
port whose service
packets contain this
VLAN ID works as the
logical port and is
mounted to the bridge.
Parameters for NNIs


only when Tag Type
is set to S-Awared.

SVLANs - - l This parameter

ID of the UNI port.
only when Tag Type
is set to S-Awared.
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
Parameters for Static MAC Addresses

VLAN ID - 1 l This parameter is

invalid if MAC
Address Learning
Mode is SVL. That is,
the preset static MAC
address entries are
valid for all VLANs.
l If MAC Address
Learning Mode is set
to IVL, the preset
static MAC address
entries are valid for
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the

MAC Address - - l This parameter

the static MAC
address.
l A static MAC address
is an address that is set
manually. It is not
aged automatically
and needs to be deleted
manually.
l Generally, a static
MAC address is used
for the port that
receives but does not
forward Ethernet
service packets or the
port whose MAC
address need not be
aged automatically.
Egress Interface - - l This parameter

specifies the Ethernet
port that corresponds
to the MAC address.
according to the

Parameters for Self-Learning MAC Address

VLAN ID - 1 l This parameter is

invalid if MAC
Address Learning
Mode is SVL. That is,
the preset self-learning
MAC address entries
are valid for all
VLANs.
l If MAC Address
Learning Mode is set
to IVL, the preset self-
learning MAC address
entries are valid for
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the

the self-learning MAC
address. A self-
learning MAC address
is also called a
dynamic MAC
address.
l A self-learning MAC
address is an entry
obtained by a bridge in
SVL or IVL learning
mode. A self-learning
MAC address can be
aged.
Egress Interface - - l This parameter

specifies the Ethernet
port that corresponds
to the MAC address.
according to the

Parameters Associated with MAC Address Learning

Aging Ability Enabled Enabled The OptiX RTN 950

Disabled supports enabling/
disabling of the aging
Aging Time(min) - 5 function and aging time
for the MAC address
table.
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.
Parameters for Disabled MAC Addresses

VLAN ID - 1 This parameter indicates

or specifies the VLAN ID
of the service. A disabled
MAC address is valid for
the VLAN whose VLAN
ID is equal to the preset
VLAN ID.


specifies or indicates
the disabled MAC
address. A disabled
MAC address is also
called a blacklisted
MAC address.
l This parameter is used
for discarding an
entry, also called a
black hole entry,
whose data frame that
contains a specific
destination MAC
address. A disabled
MAC address needs to
be set manually and
cannot be aged.
Parameters for Unknown Frame Processing

Frame Type Unicast 1 This parameter indicates

Multicast the type of the received
unknown frame.
Handing Mode Discard Broadcast Selects the method of

Broadcast processing the unknown
frame. If this parameter is
set to Discard, the
unknown frame is directly
discarded. If this
parameter is set to
Broadcast, the unknown
frame is broadcast at the
forwarding port.

Parameters for the Split Horizon Group

Split Horizon Group ID - 1 l This parameter

split horizon group.
l The default split
horizon group ID is 1
and cannot be set
manually.
Split Horizon Group - - l A split horizon group

Member member indicates the
logical port member in
the split horizon
group.
l The port members that
are added to different
split horizon groups
cannot communicate
with each other.
l The supports only the
division of the split
horizon group
members according to
the Ethernet physical
port.
l If a UNI or NNI logical
port of the 802.1ad
bridge is added to a
split horizon group
member, the physical
port that is mounted
with the logical port is
automatically added to
the split horizon group
member.
Maintenance Association Parameters

Maintenance - - This parameter indicates the maintenance

Domain Name domain of the created maintenance
association.

Maintenance - - l This parameter specifies the name of the

Association Name maintenance association, which is a
domain related to a service. Through
maintenance association division, the
connectivity check (CC) can be
performed on the network that transmits
a service instance.
l This parameter can contain a maximum
of eight bytes.
CC Test Transmit 1s 1s l This parameter specifies the interval for

Period 10s transmitting packets in the CC test.
1m l The CC is performed to check the
availability of the service.
10m
Parameters for the MEP


Domain Name domain of the created MEP.

Association Name association of the created MEP.
Node - - This parameter indicates the MEP node.
VLAN - - This parameter indicates the VLAN ID of

the current service.
MP ID 1 to 2048 1 l This parameter specifies the MEP ID.

l Each MEP needs to be configured with
an MEP ID, which is unique in the
maintenance association. The MEP ID is
required in the OAM operation.
Direction Ingress Ingress l This parameter specifies the direction of

Egress the MEP.
l "Ingress" indicates the direction in
which the packets are transmitted to the
port, and "Egress" indicates the direction
in which the packets are transmitted
from the port.
CC Status Active Active l This parameter specifies whether to

Inactive enable the CC function of the MEP.
l In the case of the tests based on the MP
IDs, CC Status must be set to Active.

Related Tasks
A.12.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service

This topic describes the parameters that are used for creating a QinQ link.
Navigation Path
Service Management > QinQ Link from the Function Tree.
2. Click New.
Parameters for the General Attributes

QinQ Link ID 1 to 4294967295 - This parameter specifies

the ID of the QinQ link.
NOTE
The OptiX RTN 950
supports 1024 QinQ links,
whose IDs must be different
from each other.
Board - - This parameter specifies

the board where the QinQ
link is located.
Port - - This parameter specifies

the port where the QinQ
link is located.
S-Vlan ID 1 to 4094 - l This parameter

(at the network
operator side) for the
QinQ link.
according to the
Related Tasks


This topic describes the parameters that are related to the Ethernet protocol.

This topic describes the parameters that are used for creating ERPS management tasks.
This topic describes the parameters that are used for Ethernet ring protection switching (ERPS)
management.
This topic describes the parameters that are used for creating MSTP port groups.
This topic describes the parameters that are related to MSTP bridges.
This topic describes the parameters that are related to the MSTP CIST.
B.9.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST
This topic describes the parameters that are related to the running information about the MSTP
CIST.
B.9.2.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration
This topic describes the parameters that are used for configuring the IGMP snooping protocol.
B.9.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly
Deleted
This topic describes the parameters that are used for adding a port to be quickly deleted.
B.9.2.10 Parameter Description: IGMP Snooping Configuration_Route Management
This topic describes the parameters that are used for IGMP Snooping protocol route
management.
B.9.2.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation
This topic describes the parameters that are used for adding static router ports.
B.9.2.12 Parameter Description: IGMP Snooping Configuration_Route Member Port
Management
This topic describes the parameters that are used for managing the route member ports of the
IGMP Snooping protocol.
B.9.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group
Member Creation
This topic describes the parameters that are used for adding static multicast groups.
This topic describes the parameters that are used for collecting the data statistics of the IGMP
Snooping protocol.
B.9.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation
This topic describes the parameters that are used for creating a link aggregation group (LAG).
This section describes the parameters for port priorities and system priorities.


This parameter describes the parameters that are used for creating LPT management.
B.9.2.18 Parameter Description: Port Mirroring_Creation
This topic describes the parameters that are used for creating port mirroring tasks.

This topic describes the parameters that are used for creating ERPS management tasks.
Navigation Path
Protection > ERPS Management.
2. Click New.
Parameters
ERPS ID 1 to 8 - l This parameter

specifies the ID of the
Ethernet ring
(ERPS) instance.
l The IDs of ERPS
instances on an NE
must be different from
each other.
East Port - - This parameter specifies

the east port of the ERPS
instance.
West Port - - This parameter specifies

the west port of the ERPS
instance.
RPLOwner Ring Node Yes No l This parameter

Flag No specifies whether the
node on the ring is the
ring protection link
(RPL) owner.
l Only one node on the
ring can be set as the
RPL owner for each
Ethernet ring.

RPL Port - - l This parameter

specifies the RPL port.
l There is only one RPL
port and this RPL port
must be the east or
west port on the RPL
owner node.
Control VLAN 1 to 4094 - l This parameter

of Control VLAN.
l Each node on the
Ethernet ring transmits
the R-APS packets on
the dedicated ring APS
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
isolating the dedicated
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
that are contained in
the service packets or
inband DCN packets.
l The Control VLAN
must be set to the same
value for all the NEs
on an ERPS ring.
Destination Node 01-19-A7-00-00-01 01-19-A7-00-00-01 This parameter indicates

the MAC address of the
destination node. The
default destination MAC
address in the R-APS
packets is always 01-19-
A7-00-00-01.
Related Tasks


This topic describes the parameters that are used for Ethernet ring protection switching (ERPS)
management.
Navigation Path
Parameters
ERPS ID 1 to 8 - This parameter indicates

the ID of the ERPS
instance.
East Port - - This parameter indicates

the east port of the ERPS
instance.
West Port - - This parameter indicates

the west port of the ERPS
instance.
RPL Owner Ring Node Yes - This parameter indicates

Flag No whether a node on the ring
is the ring protection link
(RPL) owner.
RPL Port - - This parameter indicates

the RPL port.

Control VLAN 1 to 4094 - l This parameter

the VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring transmits
the R-APS packets on
the dedicated ring APS
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
isolating the dedicated
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
that are contained in
the service packets or
inband DCN packets.
l The Control VLAN
must be set to the same
value for all the NEs
on an ERPS ring.
Destination Node 01-19-A7-00-00-01 - This parameter indicates

destination node. The
default destination MAC
address in the R-APS
packets is always 01-19-
A7-00-00-01.

Hold-Off Time(ms) 0 to 10000, in step of 100 - l This parameter

the hold-off time of the
ERPS hold-off timer.
l The hold-off timer is
used for negotiating
the protection
switching sequence
when the ERPS
coexists with other
protection schemes so
that the fault can be
rectified in the case of
other protection
switching (such as
LAG protection)
before the ERPS
occurs. When a node
on the ring detects one
or more new faults, it
starts up the hold-off
timer if the preset
hold-off time is set to a
value that is not 0.
During the hold-off
time, the fault is not
reported to trigger an
ERPS. When the hold-
off timer times out, the
node checks the link
status regardless
whether the fault that
triggers the startup of
the timer exists. If the
fault exists, the node
reports it to trigger an
ERPS. This fault can
be the same as or
different from the fault
that triggers the initial
startup of the hold-off
timer.

Guard Time(ms) 10 to 2000, in step of 10 - l This parameter

the guard time of the
ERPS guard timer.
l The nodes on the ring
continuously forward
the R-APS packets to
the Ethernet ring. As a
result, the outdated R-
APS packets may exist
on the ring network.
After a node on the
ring receives the
outdated R-APS
packets, an incorrect
ERPS may occur. The
ERPS guard timer is an
R-APS timer used for
preventing a node on
the ring from receiving
outdated R-APS
packets. When a faulty
node on the ring
detects that the
switching condition is
cleared, the node starts
up the guard timer and
starts to forward the R-
APS (NR) packets.
During this period, the
R-APS packets
received by the node
are discarded. The
received R-APS
packets are forwarded
only after the time of
the guard timer
expires.

WTR Time(min) 5 to 12, in step of 1 - l This parameter

the WTR time of the
WRT timer in the case
of ERPS protection.
l The WTR time refers
to the duration from
the time when the
working channel is
restored to the time
when the switching is
released. When the
working channel is
restored, the WTR
timer of the RPL
owner starts up. In
addition, a signal that
indicates the operation
of the WTR timer is
continuously output in
the timing process.
When the WTR timer
times out and no
switching request of a
higher priority is
received, the signal
indicating the
operation of the WTR
timer is not
transmitted. In
addition, the WTR
release signal is
continuously output.
l The WTR timer is used
to prevent frequent
switching caused by
the unstable working
channel.
Packet Transmit 1 to 10 - This parameter displays or

Interval(s) specifies the interval for
sending R-APS packets
periodically.
Entity Level 0 to 7 - This parameter indicates

or specifies the level of the
maintenance entity.
Last Switching Request - - This parameter indicates

the last switching request.

RB Status - - This parameter indicates

the RB (RPL Blocked)
status of the packets
received by the working
node.
l noRB: The RPL is not
blocked.
l RB : The RPL is
blocked.
DNF Status - - This parameter indicates

the DNF status of the
packets received by the
working node.
l noDNF: The R-APS
packets do not contain
the DNF flag. In this
case, the packets are
forwarded by the node
that detects the fault on
a non-RPL link, and
the node that receives
the packets is
requested to clear the
forwarding address
table.
l DNF: The R-APS
packets contain the
DNF flags. In this
case, the packets are
forwarded by the node
that detects the fault on
an RPL link, and the
node that receives the
packets is informed
not to clear the
forwarding address
table.

Status of State Machine - - This parameter indicates

the status of the state
machine at the working
node.
l Idle: The Ethernet ring
is in normal state. For
example, no node on
the Ethernet ring
detects any faults or
receives the R_APS
(NR, RB) packets.
l Protection: The
Ethernet ring is in
protected state. For
example, a fault on the
node triggers the
ERPS, or a node on the
ring is in the WTR
period after the fault is
rectified.
Node Carried with - - This parameter indicates

Current Packet the MAC address carried
in the R-APS packets
received by the current
node. The MAC address
refers to the MAC address
of the source node that
initiates the switching
request.
Related Tasks

Navigation Path
2. Click the Port Group Parameters tab.
3. Click Create. The Create Port Group dialog box is displayed.


Protocol Type MSTP MSTP This parameter specifies

STP the protocol type.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 950
supports the CIST
MSTP only.
l STP: stands for
Spanning Tree
Protocol.
Enable Protocol Enabled Disabled l This parameter

Disabled specifies whether to
enable the protocol of
the port group or a
member port in the
port group.
l If the STP or MSTP is
enabled, the spanning
tree topology is
automatically re-
configured. As a
result, the services are
interrupted.
Parameters for Application Ports


the board where the
member of port group is
located.
Available Port List - - This parameter indicates

the available port list in
which a port can be added
to the port group.
Selected Port List - - This parameter indicates

the selected ports that can
be added to the port group.
Related Tasks


Navigation Path
2. Click the Port Group Parameters tab.
3. On the main interface, select the port group to be configured.
4. Click Config. The Configure Port Group dialog box is displayed.
Parameters for the Added Port


the board where the
member of port group is
located.
Available Port List - - This parameter indicates

the available port list in
which a port needs to be
added to the port group.
Selected Port List - - This parameter indicates

the selected ports that
need to be added to the
port group.
Related Tasks

This topic describes the parameters that are related to MSTP bridges.
Navigation Path


Port Group ID - - l This parameter

port group.
set to only the port
group ID that is
automatically
allocated.
MST Domain Name - - The OptiX RTN 950 does

not support this
parameter.
Redaction Level - - The OptiX RTN 950 does

not support this
parameter.
Mapping List - - The OptiX RTN 950 does

not support this
parameter.
Bridge Parameters
Port Group ID - - l This parameter

port group.
set to only the port
Group ID that is
automatically
allocated.
MST Domain Max Hop - 20 Specifies the maximum

Count hop count of the MSTP.

Network Diameter 2 to 7 7 l This parameter

specifies the MSTP
network diameter.
l Network Diameter is
related to the link
whose number of
switches is the most
and is indicated by the
number of switches
that are connected to
the link. When you set
Network Diameter
for the switches, the
MSTP automatically
sets Max Age(s),
Hello Time(s), and
Forward Delay(s) to
the more appropriate
values for the
switches.
l If the value of
Network Diameter is
greater, the network is
in a larger scale.
Hello Time(s) 1 to 10 2 l This parameter

specifies the interval
for transmitting the
CBPDU packets
through 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.

Max Age(s) 6 to 40 20 l This parameter

specifies 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
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.
Forward Delay(s) 4 to 30 15 l This parameter

specifies the holdoff
time of a port in the
listening state and in
the learning state.
the longer the delay of
the network state
change. Hence, the
topology changes are
slower and the
recovery in the case of
faults is slower.
Port Parameters

the port in the port group.

Enable Edge Attribute Disabled Disabled l This parameter

Enabled specifies the
management edge
attributes of the port.
l This parameter
specifies whether to
set the port as an edge
port. The edge port
refers to the bridge
port that is connected
to the LAN. In normal
cases, this port does
not receive or transmit
BPDU messages.
set to Enabled only
when the port is
directly connected to
the data
communications
terminal equipment,
such as a computer. In
other cases, it is
use the default value.
Actual Edge Attribute - - This parameter indicates

the actual management
edge attributes of the port.

Point-to-Point Attribute false auto l This parameter

true specifies the point-to-
point attribute of the
auto port.
l false: forced non-
point-to-point link
attribute
l true: forced point-to-
point link attribute
l auto: automatically
detected point-to-
to auto, the bridge
determines Actual
Point-to-Point
Attribute of the port
working mode. If the
actual working mode
is full-duplex, the
actual point-to-point
attribute is true. If the
actual working mode
is half-duplex, Actual
Point-to-Point
Attribute is false.
l Only the designated
port whose Actual
Point-to-Point
Attribute is "True"
can transmit the rapid
state migration request
and response.
you use the default
value.
Actual Point-to-Point - - This parameter indicates

Attribute the actual point-to-point
attribute of the port.

Max Transmit Packet 1 to 255 3 l This parameter

Count specifies the
maximum number of
packets to be
transmitted.
l The maximum number
of packets to be
transmitted by the port
refers to the maximum
number of MSTP
packets that the port
can transmit within 1s.
the planning
information.
Related Tasks

This topic describes the parameters that are related to the MSTP CIST.
Navigation Path
2. Click the CIST&MSTI Parameters tab.

Port Group - - This parameter specifies

the port group.
MSTI ID 0 0 This parameter indicates

the MSTI ID. The value 0
indicates common and
internal spanning tree
(CIST). The OptiX RTN
950 supports only the
MSTP that uses CIST.

Bridge Priority 0 to 61440, in step of 4096 32768 l The most significant

16 bits of the bridge ID
indicates the priority
of the bridge.
l When the value is
smaller, the priority is
higher. As a result, the
bridge is more possible
to be 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.
Port Parameters

Priority 0 to 240, in step of 16 128 l The most significant

eight bits of the port ID
indicate the port
priority.
l When the value is
higher.
Path Cost 1 to 200000000 200000 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.
Related Tasks

B.9.2.7 Parameter Description: MSTP Configuration_Running Information About

the CIST
This topic describes the parameters that are related to the running information about the MSTP
CIST.
Navigation Path
2. Click the CIST Running Information tab.

Port Group ID - - This parameter indicates

the ID of the port group.
Protocol Running Mode MSTP Disabled l This parameter

STP indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 950
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.

Bridge Priority 0 to 61440, in step of 4096 32768 l This parameter

of the bridge.
l The most significant
of the bridge.
l When the value is
root bridge.
value, the bridge
as the root bridge.
Bridge MAC Address - - This parameter indicates

bridge.
Root Bridge MAC - - This parameter indicates

Address the MAC address of the
root bridge.
External Path Cost - 2 The OptiX RTN 950 does

ERPC not support this
parameter.
Domain Root Bridge - 32768 The OptiX RTN 950 does

Priority not support this
parameter.
Domain Root Bridge - - The OptiX RTN 950 does

MAC Address not support this
parameter.
Internal Path Cost IRPC - - The OptiX RTN 950 does

not support this
parameter.

Root Port Priority 0 to 240, in step of 16 128 l This parameter

of the root port.
l The most significant
eight bits of the ID of
the root port indicate
the priority of the root
port.
l When the value is
higher.
Root Port - - This parameter indicates

the root port.
Hello Time(s) - 2 l This parameter

indicates the interval
for transmitting
CBPDU packets
through the bridge.
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.

specifies the
maximum age of the
the longer the
of the CBPDU, which
indicates that the
network diameter is
greater. When the
a timely manner and
thus the network
reduced.


specifies the holdoff
the learning state.
the network state
change. Hence, the
slower and the
faults is slower.
MST Domain Max Hop - - The OptiX RTN 950 does

Count not support this
parameter.
Topology Change Count - - This parameter indicates

the identifier of the
topology change.
Last Topology Change - - This parameter indicates

Time(s) the duration of the last
topology change.
Topology Change Count - - This parameter indicates

the count of the topology
changes.
Port Parameters

Enable Protocol Enabled Disabled This parameter indicates

Disabled whether the protocol of
the port group or a
member of the port group
is enabled.
Port Role - Disabled This parameter indicates

the role of a port.

Port Status Discarding Discarding This parameter indicates

Learning the state of a port.
Forwarding l Discarding: receives
only BPDU packets
l Learning: only
receives or transmits
BPDU packets
l Forwarding: forwards
user traffic, and
transmits/receives
BPDU packets
Priority 0 to 240, in step of 16 128 l The most significant

indicate the port
priority.
l When the value is
higher.
Path Cost 1 to 200000000 200000 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.
Bridge Priority 0 to 61440, in step of 4096 32768 l The most significant

of the bridge.
l When the value is
root bridge.
value, the bridge
as the root bridge.

Bridge MAC Address - - This parameter indicates

bridge.
Designated Port Priority 0 to 240, in step of 16 0 l The most significant

indicate the port
priority.
l When the value is
higher.
Design Port - 0 This parameter indicates

the designated port.
Edge Port Attribute Disabled Disabled l This parameter

Enabled specifies the
management edge
attributes of the port.
l This parameter
specifies whether to
set the port as an edge
port. The edge port
refers to the bridge
port that is connected
to the LAN. In normal
cases, this port does
not receive or transmit
BPDU messages.
set to Enabled only
when the port is
directly connected to
the data
communications
terminal equipment,
such as a computer. In
other cases, it is
Actual Edge Port - Disabled This parameter indicates

Attribute the actual management
edge attributes of the port.

Point to Point false auto l This parameter

true specifies the point-to-
point attribute of the
auto port.
l false: forced non-
point-to-point link
attribute
l true: forced point-to-
l auto: automatically
detected point-to-
to auto, the bridge
determines Actual
Point to Point
Attribute of the port
working mode. If the
actual working mode
is full-duplex, the
actual point-to-point
attribute is true. If the
actual working mode
is half-duplex, Actual
Point to Point
Attribute is false.
l Only the designated
port whose Actual
Point-to-Point
Attribute is "True"
can transmit the rapid
state migration request
and response.
you use the default
value.
Actual Point to Point - - This parameter indicates

the actual point-to-point
attribute of the port.

Max Count of 1 to 255 3 l This parameter

Transmitting Message indicates the
maximum number of
packets to be
transmitted.
l The maximum number
of packets to be
transmitted by the port
refers to the maximum
number of MSTP
packets that the port
can transmit within 1s.
Protocol Running Mode STP - l This parameter

MSTP indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 950
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.
Hello Time(s) 1 to 10 2 l This parameter

indicates the interval
for transmitting the
CBPDU packets
through the bridge.
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.


specifies the
maximum age of the
the longer the
of the CBPDU, which
indicates that the
network diameter is
greater. When the
a timely manner and
thus the network
reduced.

specifies the holding
the learning state.
the network state
change. Hence, the
slower and the
faults is slower.
Remain Hop - - The OptiX RTN 950 does

not support this
parameter.
Related Tasks
B.9.2.8 Parameter Description: IGMP Snooping Configuration_Protocol

Configuration
This topic describes the parameters that are used for configuring the IGMP snooping protocol.

Navigation Path
2. Click the Protocol Configuration tab.

Service ID - - This parameter indicates

the service ID.
Enabled Protocol Enabled Disabled l This parameter

Disabled specifies 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.

Router Port Aging Time 1 to 120 8 l If an entry is not

(min) updated in a certain
period (that is, no
IGMP query packet is
received), this entry is
automatically deleted.
This mechanism is
called aging, and this
period is called aging
time.
to a very large value,
the bridge stores
excessive multicast
entries that are
outdated.
Consequently, the
resources of the
multicast table are
exhausted.
to a very small value,
the bridge may delete
the multicast entry that
is required.
Consequently, the
forwarding efficiency
decreases.

Maximum Times of No 1 to 4 3 l This parameter

Response from Multicast specifies the
Members maximum number of
multicast group
members who do not
respond.
l If the IEEE 802.1q
bridge transmits an
IGMP group query
packet to the multicast
member ports, the
IEEE 802.1q bridge
starts the timer for the
query of the maximum
number of responses.
If no IGMP report
packets are received
within the query time,
the IEEE 802.1q
bridge adds one to the
number of no
responses at the port.
When the number of
no responses exceeds
the preset value of
Maximum Times of
No Response from
Multicast Members,
the IEEE 802.1q
bridge deletes the
additional multicast
members from the
multicast group.
Maximum Number of - - l This parameter

Multicast Groups specifies the
maximum number of
allowable multicast
groups.
l The multicast group
records the mapping
relations between the
ports on the router,
MAC multicast
addresses, and
member ports in the
multicast group.

Maximum Number of - - l This parameter

Multicast Group specifies the
Members maximum number of
allowable multicast
group members.
l A multicast group
member refers to the
host that is added to a
multicast group.
Actual Multicast Count - - This parameter indicates

the number of actually
used multicast groups.
Actual Multicast - - This parameter indicates

Members Count the number of actually
used multicast group
members.
Related Tasks
B.9.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be

Quickly Deleted
This topic describes the parameters that are used for adding a port to be quickly deleted.
Navigation Path
2. Click the Protocol Configuration tab.
3. Click Add.
Parameters for Fast Leave Ports


the service ID.

VLAN ID 1 to 4094 1 l This parameter

specifies the VLAN
where the port to be
quickly deleted is
located.
the planning
information.
Port Type V-UNI V-UNI l This parameter

V-NNI specifies the type of
the port to be quickly
deleted.
the planning
information.

the port to be quickly
deleted.
Related Tasks
B.9.2.10 Parameter Description: IGMP Snooping Configuration_Route

Management
This topic describes the parameters that are used for IGMP Snooping protocol route
management.
Navigation Path
2. Click the Router Port Management tab.
Parameters for Router Port Management

Service ID - - This parameter specifies

the ID of the created E-
LAN service.

VLAN ID - - This parameter indicates

the VLAN ID of the router
port.
Port Type - - This parameter indicates

the type of the router port.

the router port.
Port Status - - This parameter indicates

the status of the router
port.
Port Creating Time - - This parameter indicates

the time when the router
port is created.
Port Remainder Aging - - This parameter indicates

Time(min) the remaining aging time
of the router port.
Related Tasks
B.9.2.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port

Creation
This topic describes the parameters that are used for adding static router ports.
Navigation Path
2.
3. Click the Router Port Management tab.
4. Click New.
Parameters for Router Port Creation


LAN service.
VLAN ID 1 to 4094 1 This parameter indicates

the VLAN ID of the router
port.

Available Port - - This parameter indicates

the available ports.
Selected Port - - This parameter indicates

the specified router port.
Related Tasks
B.9.2.12 Parameter Description: IGMP Snooping Configuration_Route Member

Port Management
This topic describes the parameters that are used for managing the route member ports of the
IGMP Snooping protocol.
Navigation Path
2. Click the Route Member Port Management tab.
Parameters for Multicast Groups Information


LAN service.

the VLAN ID of the
multicast group.
Multicast MAC Address - - This parameter indicates

the multicast MAC
address.
Multicast Groups Type - - This parameter indicates

the type of the multicast
group.
Multicast Group - - This parameter indicates

Creating Time the time when the
multicast group is set up.

Parameters for Multicast Group Members Information


LAN service.

the VLAN ID of the
multicast group member.

the type of the multicast
group member.

the multicast group
member port.
Port Remainder Aging - - This parameter indicates

Times the remaining non-
response times of the
multicast group member
port.
Related Tasks
B.9.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast

Group Member Creation
This topic describes the parameters that are used for adding static multicast groups.
Navigation Path
2. Click the Route Member Port Management tab.
3. Click New.
Parameters for Router Port Creation


LAN service.

VLAN ID 1 to 4094 1 This parameter specifies

the VLAN ID of the
multicast group.
Multicast MAC Address - - This parameter specifies

the multicast MAC
address.

the available interfaces.

the preset port of the
multicast group members.
Related Tasks

This topic describes the parameters that are used for collecting the data statistics of the IGMP
Snooping protocol.
Navigation Path
2. Click the Packet Statistics tab.
Parameters for Routing Member Interface Management


the service ID.

the VLAN ID of the
service.

the port type.

the port.
Packet Statistics Status Clear Clear This parameter indicates

Start or specifies the status of
collecting the packet
Stop statistics.

IGMPv1 Query Packet - - This parameter indicates

Count the number of received
IGMPv1 query packets.


IGMP Leaving Packet - - This parameter displays

Count the number of leaving
packets that are received.
IGMPv1 Member - - This parameter indicates

Report Packet Count the number of received
packets that are reported
by the IGMPv1 members.


Unrecognized or - - This parameter indicates

Unprocessed Packet the number of packets that
Count cannot be recognized or
processed.
Discarded Incorrect - - This parameter indicates

Packet Count the number of discarded
error packets.
Related Tasks
B.9.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG

Creation
This topic describes the parameters that are used for creating a link aggregation group (LAG).

Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
2. Click the Link Aggregation Group Management tab.
3. Click New.

LAG No. - 1 l This parameter

specifies the LAG
number to be set
manually.
only when
Automatically
Assign is not selected.
Automatically Assign Selected Selected l This parameter

Deselected indicates whether
LAG No. is allocated
automatically.
l When Automatically
Assign is selected,
LAG No. cannot be
set.
LAG Name - - This parameter specifies

the LAG name.

LAG Type Static Static l Static: You can create

Manual a LAG. When you add
or delete a member
port to or from the
LAG, the Link
Aggregation Control
Protocol (LACP)
protocol is required. In
a LAG, a port can be in
selected, standby, or
unselected state. The
aggregation
information is
exchanged among
different equipment
through the LACP
protocol to ensure that
the aggregation
information is the
same among all the
nodes.
l Manual: You can
create a LAG. When
you add or delete a
member port, the
LACP protocol is not
required. The port can
be in the up or down
state. The system
determines whether to
aggregate a port
according to its
physical state (UP or
DOWN), working
mode, and rate.
Switch Protocol - - The OptiX RTN 950 does

not support this
parameter.
Switch Mode - - The OptiX RTN 950 does

not support this
parameter.
Link Trace Protocol - - The OptiX RTN 950 does

not support this
parameter.

Revertive Mode Revertive Non-Revertive l This parameter can be

Non-Revertive set only when Load
Sharing is set to Non-
Sharing.
l When a LAG is set to
Revertive, the
services are switched
back to the former
working channel after
this channel is restored
to normal.
l When a LAG is set to
Non-Revertive, the
status of the LAG does
not change after the
former working
channel is restored to
normal. That is, the
services are still
transmitted on the
protection channel.
Load Sharing Sharing Non-Sharing l Sharing: Each member

Non-Sharing link of a LAG
processes traffic at the
same time and shares
the traffic load. The
sharing mode can
increase a bandwidth
utilization for the link.
When the LAG
members change, or
certain links fail, the
system automatically
re-allocates the traffic.
l Non-Sharing: Only
one member link of a
LAG carries traffic,
and the other link is in
the standby state. In
this case, a hot backup
mechanism is
provided. When the
active link of a LAG is
faulty, the system
activates the standby
link, thus preventing
link failure.

Load Sharing Hash Source MAC Source MAC l This parameter is valid
Algorithm Destination MAC only when Load
Sharing of a LAG is
Source and Destination set to Sharing.
MAC
l The load sharing
Source IP computation methods
Destination IP include: MAC address
Source and Destination IP specific allocation
(based on the source
MAC address,
destination MAC
address, and XOR
between source MAC
address and source
MAC address), IP
address specific
allocation (based on
the source IP address,
destination IP address,
and XOR between
source IP address and
source IP address).

System Priority 0 to 65535 32768 l This parameter

of a LAG. The smaller
the value of System
Priority, the higher
the priority.
l When a local LAG
negotiates with an
opposite LAG through
LACP packets, both
LAGs can obtain the
system priorities of
each other. Then, the
LAG of the higher
system priority is
considered as the
comparison result of
both LAGs so that the
aggregation
information is
consistent at both
LAGs. If the priorities
of both LAGs are the
same, the system MAC
addresses are
compared. Then, the
comparison result
based on the LAG with
smaller system MAC
address is considered
as the result of both
LAGs and is used to
ensure that the
aggregation
information is
consistent at both
LAGs.
Port Settings Parameters

Main Board - - l This parameter

specifies the main
board in a LAG.
according to the

Main Port - - l This parameter

specifies the main port
in a LAG.
l After a LAG is created,
you can add Ethernet
services to the main
port only. Services
cannot be added to a
slave port. When Load
Sharing is set to Non-
Sharing, the link
connected to the main
port is used to transmit
the services, and the
link connected to the
slave port is used for
protection.
Board (Available Slave - - l This parameter

Ports) specifies the slave
board in a LAG.
according to the
Port (Available Slave - - l This parameter

Ports) specifies the salve port
in a LAG.
l The slave ports in a
LAG are fixed. Unless
they are manually
modified, the system
does not automatically
add them to or delete
them from the LAG.
Selected Slave Ports - - This parameter indicates

the selected slave ports.
Related Tasks


Navigation Path
2. Click the Port Priority tab.


the port whose priority can
be set.
Port Priority 0 to 65535 32768 l This parameter

indicates the priorities
of the ports in a LAG
as defined in the LACP
protocol. The smaller
the value, the higher
the priority.
l When ports are added
into a LAG, the port of
the highest priority is
preferred for service
transmission.
Related Tasks

This parameter describes the parameters that are used for creating LPT management.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
2. Click New.
Parameters for Convergence Points

Board - - This parameter specifies the board at the

convergence point.

Port - - This parameter specifies the port on the

board of the convergence point.
NOTE
One port can be in an LPT only.
Parameters for Access Points

Board - - This parameter specifies the board at the

access point.
Port - - This parameter specifies the port on the

board of the access point.
NOTE
The access point supports selection of multiple
ports on different boards.
Related Tasks

This topic describes the parameters that are used for creating port mirroring tasks.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Port
Mirroring from the Function Tree.
2. Click New. The Port Mirror Management dialog box is displayed.

Mirror Name - - l This parameter specifies the name of the

mirroring task.
l After the mirroring function of the port
is enabled, you can monitor all the
mirrored ports by analyzing the packets
at the mirroring port only. As a result,
you can easily manage the ports.

Direction Ingress Ingress l This parameter specifies the direction in

Egress which the service to be monitored.
l Ingress indicates that the Listened
Port copies the received packets to the
Mirror Listener Port and sends the
packets out of the Mirror Listener
Port.
l Egress indicates that the Listened Port
copies the transmitted packets to the
Mirror Listener Port and sends the
packets out of the Mirror Listener
Port.
Mirror Listener - - l This parameter specifies the mirroring

Port listener port and the listened port.
l Listened Port indicates the source port
Listened Port - -
of the mirrored packets.
l Mirror Listener Port indicates the port
from which the packets copied from the
Listened Port are sent out.
l Mirror Listener Port: The port where
services are available cannot be selected.
Otherwise, the creation fails.

This topic describes the parameters that are related to the Ethernet operation, administration and
maintenance (OAM).
B.9.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain

Creation
This topic describes the parameters that are used for creating maintenance domains.
B.9.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association
Creation
This topic describes the parameters that are used for creating maintenance associations.
This topic describes the parameters that are used for creating a maintenance association end
point (MEP).
B.9.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation
This topic describes the parameters that are used for creating a remote MEP.
This topic describes the parameters that are used for creating a maintenance association
intermediate point (MIP).
This topic describes the parameters that are used for enabling the LB.


This topic describes the parameters that are used for enabling the LT.
This topic describes the OAM parameters that are related to Ethernet ports.
Monitoring
This topic describes the parameters that are used for monitoring the OAM error frames at the
Ethernet port.
B.9.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance

Domain Creation
This topic describes the parameters that are used for creating maintenance domains.
Navigation Path
3. Choose New > New Maintenance Domain.

Maintenance - default l This parameter specifies the name of the

Domain Name maintenance domain.
l The maintenance domain refers to the
network for the Ethernet OAM.
of eight bytes.

Maintenance 0 4 l This parameter specifies the level of the

Domain Level 1 maintenance domain.
2 l The values 0-2 indicate the carrier level,
the values 3-4 indicate the supplier level,
3 and the values 5-7 indicate the user level.
4 l When the value is set to 0, the
5 maintenance domain is at the lowest
6 level. The values 1-7 indicate that the
level increases in a sequential order.
7
l The OAM packets whose level is higher
than the preset value are transparently
transmitted by the MEPs. The OAM
packets whose level is lower than the
preset value are directly discarded by the
MEPs. The OAM packets whose level is
the same as the preset value are
responded to or terminated by the MEPs
according to the message type.
Related Tasks
B.9.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance

Association Creation
This topic describes the parameters that are used for creating maintenance associations.
Navigation Path
3. Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.


Domain Name domain of the created maintenance
association.

Maintenance - - l This parameter specifies the name of the

Association Name maintenance association, which is a
domain related to a service. Through
maintenance association division, the
connectivity check (CC) can be
performed on the network that transmits
a service instance.
of eight bytes.
Relevant Service - - This parameter specifies the service

instance that is related to the maintenance
association.
CC Test Transmit 1s 1s l This parameter specifies the interval for

Period 10s transmitting packets in the CC.
1m l The CC is performed to check the
availability of the service.
10m
Related Tasks

This topic describes the parameters that are used for creating a maintenance association end
point (MEP).
Navigation Path
3. Select the maintenance association in which an MEP needs to be created. Choose New >
New MEP Point.


Domain Name domain of the created MEP.

Board - - This parameter specifies the board where

the MEP is located.

Port - - This parameter specifies the port where the

MEP is located.
VLAN - - This parameter indicates the VLAN ID of

the current service.
MP ID 1 to 2048 1 l This parameter specifies the MEP ID.

l Each MEP needs to be configured with
an MEP ID, which is unique in the
maintenance association. The MEP ID is
Direction Ingress Ingress l This parameter specifies the direction of

Egress the MEP.
l Ingress indicates the direction in which
the packets are transmitted to the port,
and Egress indicates the direction in
which the packets are transmitted from
the port.
CC Status Active Active l This parameter specifies whether to

Inactive enable the CC function of the MEP.
l In the case of the tests based on the MP
IDs, CC Status must be set to Active.
Related Tasks
B.9.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP

Creation
This topic describes the parameters that are used for creating a remote MEP.
Navigation Path
3. Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point
dialog box is displayed.
4. Click New.



Domain Name domain of the MEP.

Remote 1 to 2048 - l This parameter specifies the ID of the

Maintenance Point remote MEP.
ID(e.g:1,3-6) l If other MEPs may initiate OAM
operations to an MEP in the same MA,
set the other MEPs to be the remote
MEPs.
Related Tasks

This topic describes the parameters that are used for creating a maintenance association
intermediate point (MIP).
Navigation Path
2. Click the MIP Point tab.
3. Select the maintenance domain in which an MIP needs to be created, and then click New.


Domain Name domain of the MIP.
Board - - This parameter specifies the board where

the MIP is located.
Port - - This parameter specifies the port where the

MIP is located.

MP ID 1 to 2048 1 l This parameter specifies the MIP ID.

l Each MIP needs to be configured with an
MIP ID, which is unique in the
maintenance domain. The MIP ID is
NOTE
To create MEPs and MIPs in a service at a
port, ensure that only one MIP can be created
and the level of the MIP must be higher than
the level of the MEP.
Related Tasks

This topic describes the parameters that are used for enabling the LB.
Navigation Path
3. Select the maintenance domain and maintenance association for the LB test.
4. Choose OAM > Start LB.

Destination Selected Deselected This parameter needs to be selected if the

Maintenance Point Deselected LB test is performed on the basis of
ID Destination Maintenance Point IDs.
Destination Selected Selected This parameter needs to be selected if the

Maintenance Point Deselected LB test is performed on the basis of MAC
MAC Address addresses.
Maintenance - - This parameter indicates the name of the

Domain Name maintenance domain for the LB test.

Association Name maintenance association for the LB test.
Source - - l This parameter specifies the source

Maintenance Point maintenance point in the LB test.
ID l Only the MEP can be set to the source
maintenance point.

Destination - - l This parameter specifies the destination

Maintenance Point maintenance point in the LB test.
ID l Only the MEP can be set to the
destination maintenance point.
l Destination Maintenance Point ID can
be set only when MP ID is selected.
Destination - 00-00-00-00-00-00 l This parameter specifies the MAC

Maintenance Point address of the port where the destination
MAC Address maintenance point is located in the LB
test.
l Only the MAC address of the MEP can
be set to the MAC address of the
l Destination Maintenance Point MAC
Address can be set only when Sink
Maintenance Point MAC Address.
Transmitted 1 to 255 3 l This parameter specifies the number of

Packet Count packets transmitted each time in the LB
test.
l When the value is greater, the required
duration is longer.
Transmitted 64 to 1400 64 l This parameter specifies the length of a

Packet Length transmitted LBM packet.
l If the packet length is different, the test
result may be different. In normal cases,
it is recommended that you use the
default value.
Transmitted 0 to 7 7 l This parameter specifies the priority of

Packet Priority transmitting packets.
l 0 indicates the lowest priority, and 7
indicates the highest priority. In normal
cases, this parameter is set to the highest
priority.
Detection Result - - This parameter indicates the relevant

information and result of the LB test.
Related Tasks

This topic describes the parameters that are used for enabling the LT.

Navigation Path
3. Select the maintenance domain and maintenance association for the LT test.
4. Choose OAM > Start LT.
Test Node Parameters

Destination Selected Deselected This parameter needs to be selected if the LT

Maintenance Point Deselected test is performed on the basis of MP IDs.
ID
Destination Selected Selected This parameter needs to be selected if the LT

Maintenance Point Deselected test is performed on the basis of MAC
MAC Address addresses.

Domain Name maintenance domain for the LT test.

Association Name maintenance association for the LT test.
Source - - l This parameter specifies the source

Maintenance Point maintenance point in the LT test.
ID l Only the MEP can be set to the source
maintenance point.
Destination - - l This parameter specifies the destination

ID l Only the MEP can be set to the
l Destination Maintenance Point ID can
be set only when MP ID is selected.
Destination - 00-00-00-00-00-00 l This parameter specifies the MAC

Maintenance Point address of the port where the destination
MAC Address maintenance point is located in the LT
test.
l Only the MAC address of the MEP can
be set to the MAC address of the
l Destination Maintenance Point MAC
Address can be set only when Sink
Maintenance Point MAC Address.

Parameters for the Detection Result

Source - - This parameter indicates the source

ID
Destination - - This parameter indicates the MAC address

Maintenance Point of the port where the destination
ID/MAC maintenance point is located in the LT test.
Response - - This parameter indicates the MAC address

Maintenance Point of the port where the responding
ID/MAC maintenance point is located in the LT test.
Hop Count 1 to 64 - l This parameter indicates the number of

hops from the source maintenance point
to the responding maintenance point or
to the destination maintenance point in
the LT test.
l The number of hops indicates the
adjacent relation between the responding
maintenance point to the source
maintenance point. The number of hops
increases by one when a responding
point occurs on the link from the source
maintenance point to the destination
maintenance point.
Test Result - - This parameter indicates the result of the LT

- test.
Related Tasks

This topic describes the OAM parameters that are related to Ethernet ports.
Navigation Path
2. Click the OAM Parameter tab.


Port - - This parameter indicates the corresponding

port.
Enable OAM Enabled Disabled l This parameter indicates or specifies

Protocol Disabled whether to enable the OAM protocol.
l After the OAM protocol is enabled, the
current Ethernet port starts to use the
preset mode to create the OAM
connection with the opposite end.
OAM Working Active Active l This parameter indicates or specifies the

Mode Passive working mode of the OAM.
l The port whose OAM working mode is
set to Active can initiate the OAM
connection.
l The port whose OAM working mode is
set to Passive can only wait for the
opposite end to send the OAM
connection request.
l The OAM working mode of the
equipment at only one end can be
Passive.
Link Event Enabled Enabled l This parameter indicates or specifies

Notification Disabled whether the local link events can be
notified to the opposite end.
l If the alarms caused by link events can
be reported, that is, if the number of
performance events (for example, error
frame period, error frame, error frame
second, and error frame signal cycle) at
the local end exceeds the preset
threshold, these performance events are
notified to the port at the opposite end
through the link event notification
function.

Remote Side Disabled Disabled l This parameter indicates or specifies

Loopback Enabled whether the port responds to the remote
Response loopback.
l Remote loopback indicates that the local
OAM entity transmits packets to the
remote OAM entity for loopback. The
local OAM entity can locate the fault and
test the link performance through
loopback data analysis.
l If a port does not support remote
loopback response, this port does not
respond to the loopback request from the
remote port regardless of the OAM port
status.
Loopback Status Non-Loopback - This parameter indicates the loopback status

Initiate Loopback at at the local end.
Local NOTE
Loopback Status is valid only after you choose
Respond Loopback OAM > Enable Remote Loopback.
of Remote
OAM Discovery FAULT - This parameter indicates the OAM

Status ACTIVE_SEND_L discovery status at the local end.
OCAL
PASSIVE_WAIT
SEND_LOCAL_R
EMOTE
SEND_LOCAL_R
EMOTE_OK
SEND_ANY
Port Transmit FWD - l This parameter indicates the status of

Status DISCARD transmitting packets at the local end.
l When a port is in the FWD state, the port
forwards the non-OAM packets. When a
port is in the DISCARD state, the port
discards the non-OAM packets.
Port Receive Status FWD - l This parameter indicates the status of

DISCARD receiving packets at the local end.
LB l In the FWD state, the port forwards the
non-OAM packets. In the LB state, the
port loopback the non-OAM packets. In
the DISCARD state, the port discards
the non-OAM packets.

Related Tasks

Monitoring
This topic describes the parameters that are used for monitoring the OAM error frames at the
Ethernet port.
Navigation Path
2. Click the OAM Error Frame Monitor tab.


port.
Error Frame 1000 to 60000, in 1000 This parameter specifies the duration of
Monitor Window step of 100 monitoring error frames.
(ms)
Error Frame 1 to 4294967295, in 1 l This parameter specifies the threshold of

Monitor Threshold step of 1 monitoring error frames.
(frame) l Within the specified value of Error
Frame Monitor Window(ms), if the
number of error frames on the link
exceeds the preset value of Error
Frame Monitor Threshold(frame), an
alarm is reported.
Error Frame 1488 to 892800000, 892800000 This parameter specifies the window of
Period Window in step of 1 monitoring the error frame period.
(frame)

Period Threshold step of 1 monitoring the error frame period.
(frame) l Within the specified value of Error
Frame Period Window(frame), if the
Frame Period Threshold(frame), an
alarm is reported.
Error Frame 10 to 900, in step of 60 This parameter specifies the time window of
Second Window(s) 1 monitoring the error frame second.

Error Frame 10 to 900, in step of 1 l This parameter specifies the threshold of

Second Threshold 1 monitoring error frame seconds.
(s) l If any error frame occurs in one second,
this second is called an errored frame
second. Within the specified value of
Error Frame Second Window(s), if the
Frame Second Threshold(s), an alarm
is reported.
Error Frame 1 to 60, in step of 1 1 This parameter specifies the window of

Signal Periodic monitoring the error frame signal period.
Monitor Window
(Entries)

Signal Periodic step of 1 monitoring the error frame signal period.
Monitor Threshold l Within the specified value of Error
(Entries) Frame Signal Periodic Monitor
Window(Entries), if the number of
error signals exceeds the preset value of
Error Frame Signal Periodic Monitor
Threshold(Entries), an alarm is
reported.
Related Tasks

This topic describes the parameters that are related to QoS.

This topic describes the parameters that are used for managing DiffServ domains.
This parameter describes the parameters that are used for creating DiffServ (DS) domains.
This topic describes the parameters that are used for changing DiffServ (DS) domain applied
ports.
This topic describes the parameters that are related to port policies.
This topic describes the parameters that are used for creating port policies.

This parameter describes the parameters that are used for creating traffic classification.
This topic describes the parameters that are used for creating port shaping management tasks.

This topic describes the parameters that are used for managing DiffServ domains.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS

Mapping Relation ID 1 to 8 1 This parameter indicates

the ID of the mapping
relation between DiffServ
domains.
Mapping Relation Name - Default Map This parameter indicates

the name of the mapping
relation between DiffServ
domains.
NOTE
If one default DiffServ domain exists on the OptiX RTN 950 equipment, Mapping Relation ID is set to 1, and
Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to the domain.
The default DiffServ domain cannot be modified or deleted.
Parameters for Ingress Mapping Relation

CVLAN 0 to 7 - l This parameter

of the C-VLAN of the
ingress packets.
l C-VLAN indicates the
client-side VLAN, and
the value 7 indicates
the highest priority.


of the S-VLAN of the
ingress packets.
l S-VLAN indicates the
server-side VLAN,
and the value 7
indicates the highest
priority.
IP DSCP 0 to 63 - l This parameter

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
l The differentiated
services code point
(DSCP) refers to bits
0-5 of the
differentiated services
(DS) field in the packet
and indicates the
service class and
discarding priority of
the packet.

PHB BE - l This parameter

AF1 indicates the per-hop
behavior (PHB)
AF2 service class of the
AF3 DiffServ domain.
AF4 l The PHB service class
EF refers to the
forwarding behavior
CS6
of the DiffServ node
CS7 on the behavior
aggregate (BA)
operation. The
forwarding behavior
can meet the specific
requirements.
l The PHB service
classes are BE, AF1,
AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, and DSCP
value) contained in the
packets of the DiffServ
domain and the eight
PDB service classes
meet the requirements
of the specified or
default mapping
relation.
NOTE
The AF1 is classified into
three sub service classes,
namely, AF11, AF12, and
AF13, only one of which is
valid. It is the same case
with the AF2, AF3, and
AF4.

Parameters for Egress Mapping Relation


AF1 indicates the PHB
service class of the
AF2 DiffServ domain.
AF4 refers to the
EF forwarding behavior
of the DiffServ node
CS6
on the behavior
CS7 aggregate (BA)
operation. The
forwarding behavior
requirements.
l The PHB service
AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, and DSCP
packets of the DiffServ
PDB service classes
of the specified or
default mapping
relation.
NOTE
AF4.

of the C-VLAN of the
egress packets.


of the S-VLAN of the
egress packets.
server-side VLAN,
and the value 7
priority.

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
l The DSCP refers to
bits 0-5 of the DS field
in the packet and
indicates the service
class and discarding
priority of the packet.


the port that uses the
DiffServ domain.
Packet Type CVLAN CVLAN The packets trusted by the

SVLAN OptiX RTN 950 are the
C_VLAN, S_VLAN and
IP-DSCP IP DSCP packets that
contain the C_VLAN
priority, S_VLAN
priority, or DSCP value.
By default, the untrusted
packets are mapped to the
BE service class for best-
effort forwarding.
NOTE
The E-Line point-to-point
transparent transmission
service supports only the
mapping from DSCP
packets to the PHB service
class.

Related Tasks

This parameter describes the parameters that are used for creating DiffServ (DS) domains.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from
the Function Tree.
2. Click New.

Mapping Relation ID 2 to 8 2 This parameter specifies

the ID of the mapping
relation of a DS domain.
Mapping Relation Name - - This parameter specifies

Packet Type cvlan cvlan l This parameter

svlan specifies the type of
the packet.
ip-dscp
l The packets trusted by
the OptiX RTN 950
are the C_VLAN,
S_VLAN and IP
DSCP packets that
contain the C_VLAN
priority, S_VLAN
priority, or DSCP
value. By default, the
untrusted packets are
mapped to the BE
service class for best-
effort forwarding.
NOTE
mapping from DSCP
class.

NOTE
If one default DS domain exists on the OptiX RTN equipment, Mapping Relation ID is set to 1, Mapping
Relation Name is set to Default Map. If these parameters are not set, all the ports belong to the domain. The
default DS domain cannot be modified and deleted.
Parameters for Ingress Mapping Relation


specifies the C-VLAN
priority of the ingress
packets.

priority of the ingress
packets.
server-side VLAN,
and the value 7
priority.

specifies the DSCP
priority of the IP
addresses of the
ingress packets.
services code point
0-5 of the
and indicates the
service class and
the packet.


service class of the DS
AF2 domain.
AF4 refers to the
of the DS node on the
CS6
behavior aggregate
CS7 (BA) operation. The
forwarding behavior
requirements.
l The PHB service
AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, and DSCP
packets of the DS
PDB service classes
of the specified or
default mapping
relation.
NOTE
AF4.

Parameters for Egress Mapping Relation


service class of the DS
AF2 domain.
AF4 refers to the
of the DS node on the
CS6
behavior aggregate
CS7 (BA) operation. The
forwarding behavior
requirements.
l The PHB service
AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, and DSCP
packets of the DS
PDB service classes
of the specified or
default mapping
relation.
NOTE
AF4.

specifies the C-VLAN
priority of the egress
packets.


priority of the egress
packets.
server-side VLAN,
and the value 7
priority.

specifies the DSCP
priority of the IP
addresses of the egress
packets.
services code point
0-5 of the
and indicates the
service class and
the packet.


the board that uses the
mapping relations
between DS domains.
Available Port - - This parameter displays

the available port list from
which you can select the
port that uses the mapping
relations between DS
domains.
Selected Port - - This parameter displays

the selected port list. The
ports in the list use the
mapping relations
between DS domains.

Related Tasks

This topic describes the parameters that are used for changing DiffServ (DS) domain applied
ports.
Navigation Path
2. Select the DS domain to be changed in the main interface.
3. Click the Apply Port tab.
4. Click Modify.
Parameters for Configuring the Applied Ports

Mapping Relation Name - - This parameter indicates


Packet Type CVLAN CVLAN l This parameter

SVLAN specifies the type of
the packet.
IP-DSCP
l The packets trusted by
the OptiX RTN 950
are the C-VLAN, S-
VLAN and IP-DSCP
packets that contain
the C-VLAN priority,
S-VLAN priority, or
DSCP value. By
default, the untrusted
packets are mapped to
the BE service class
for best-effort
forwarding.
l When the OptiX RTN
950 receives services
and identifies service
types based on VLAN
priorities, the trusted
packets at a UNI ports
carry C-VLAN
priorities, and the
trusted packets at an
NNI port carry S-
VLAN priorities.
When the OptiX RTN
950 receives services
and identifies service
types based on DSCP
values, the trusted
packets at a port carry
IP-DSCP values.
NOTE
mapping from DSCP
class.

the board where the port is
located.

the available port.


the selected port.
The selected port is
applied to the DS domain.
NOTE
If one default DS domain exists on the OptiX RTN 950, Mapping Relation ID is set to 1, and Mapping Relation
Name is set to Default Map. If these parameters are not set, all the ports belong to the domain. The port applied
to the default DS domain cannot be modified.
Related Tasks

This topic describes the parameters that are related to port policies.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Parameters
Policy ID 1 to 36 - l This parameter

indicates the policy ID
of the port.
l The OptiX RTN 950
supports a maximum
number of 36 policies.
Policy Name - - This parameter indicates

or specifies the policy
name of the port.

CoS CS7 - l The BE, AF1, AF2,

CS6 AF3, AF4, EF, CS6,
and CS7 service
EF classes respectively
AF4 map eight queuing
AF3 entities. The OptiX
RTN 950 provides
AF2
different QoS policies
AF1 for the queues at
BE different service
classes.
l CS6-CS7: indicates
the highest service
grade, which is mainly
involved in signaling
transmission.
l EF: indicates fast
forwarding. This
service class is
applicable to the traffic
whose delay is small
and packet loss ratio is
low, for example,
voice and video
services.
l AF1-AF4: indicates
assured forwarding.
This service class is
that requires rate
guarantee but does not
require delay or jitter
limit.
l BE: indicates that the
traffic is forwarded in
best-effort manner
without special
processing.

Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority (SP)
Reloading WRR AF4, AF3, AF2, AF1: scheduling algorithm
WRR is designed for the key
services. One
important
characteristic of the
key services is that
higher priorities are
required to minimize
the response delay in
the case of congestion
events.
l The weighted round
robin (WRR)
scheduling algorithm
divides each port into
multiple output sub-
queues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each sub-
queue has a certain
period of service time.
l The OptiX RTN 950
supports the setting of
the SP+WRR
of the CoS queue
according to the
requirement, and
provides one or more
queues that comply
with the SP algorithm.
Except for the default
value, however, the
value of the WRR
and the value of the SP
cannot be interleaved.
That is, except for the
default value,
Grooming Police
After Reloading can
be changed from SP to
WRR according to the
queue priorities in a
descending order
(CS7-BE).


according to the
Policy Weight(%) 1 to 100 25 l This parameter

specifies the weight of
the policy in the WRR
queue. The weight
indicates the
percentage of the
bandwidth resources
obtained by the WRR
queue.
set only when
Grooming Police
After Reloading is set
to WRR.
according to the
Bandwidth Limit Disabled Disabled l This parameter

Enabled indicates or specifies
whether traffic
shaping is enabled for
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
(kbit/s), CBS (byte),
and PBS (byte) can be
set only when
Bandwidth Limit is
set to Enabled.
according to the
CIR(kbit/s) - - Traffic shaping for an

egress queue uses the
single token bucket two
color marker algorithm.
The value of the CIR must
be equal to the value of the
PIR. In actual traffic
shaping processing, only
the PIR is valid.

PIR(kbit/s) - - l When the buffer queue

is empty, the packets
are processed as
follows: If the rate of a
packet is equal to or
lower than the PIR, it
is directly forwarded;
if the rate of a packet is
higher than the PIR, it
enters the buffer queue
and then is forwarded
at a rate equal to the
PIR.
l When the buffer queue
is not empty, the
packets whose rate
passes the restriction
of the PIR directly
enter the buffer queue
and then are forwarded
PIR.
according to the
CBS(byte) - - l It is recommended that

you set the value of the
CBS equal to the value
of the PIR. In actual
traffic shaping
processing, only the
PBS is valid.
according to the

PBS(byte) - - l When the buffer queue

is empty, certain burst
packets can be
forwarded if the rate of
the packets is equal to
or lower than the PIR
in a certain period. The
maximum traffic of the
burst packets is
determined by the
PBS.
according to the
Related Tasks

This topic describes the parameters that are used for creating port policies.
Navigation Path
2. Click the CoS Queue Configuration tab.
3. Click New. The Create Port Policy dialog box is displayed.
Parameters
Policy ID 1 to 36 - l This parameter

specifies the policy ID
of the port.
l The OptiX RTN 950
supports a maximum
number of 36 policies.

Automatically Assign Selected Deselected This parameter specifies

Deselected whether to automatically
allocate the policy ID of
the port policy. After this
parameter is selected, the
system automatically
allocates the policy ID,
and then the policy ID
cannot be set manually.
Policy Name - - This parameter specifies

the policy name of the
port.

CoS CS7 - l The BE, AF1, AF2,

CS6 AF3, AF4, EF, CS6,
and CS7 service
EF classes respectively
AF4 map eight queuing
AF3 entities. The OptiX
RTN 950 provides
AF2
different QoS policies
AF1 for the queues at
BE different service class.
l CS6-CS7: indicates
the highest service
grade, which is mainly
involved in signaling
transmission.
l EF: indicates fast
forwarding. This
service class is
whose delay is small
and packet loss ratio is
low, for example,
voice and video
services.
l AF1-AF4: indicates
assured forwarding.
This service class is
that requires rate
guarantee but does not
require delay or jitter
limit.
l BE: indicates that the
traffic is forwarded in
best-effort manner
without special
processing.

Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority (SP)
Reloading WRR AF4, AF3, AF2, AF1: scheduling algorithm
WRR is designed for the key
services. One
important
characteristic of the
key services is that
higher priorities are
required to minimize
the response delay in
the case of congestion
events.
l The weighted round
robin (WRR)
divides each port into
multiple output sub-
queues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each sub-
queue has a certain
period of service time.
l The OptiX RTN 950
the SP+WRR
of the CoS queue
according to the
requirement, and
provides one or more
queues that comply
with the SP algorithm.
Except for the default
value, however, the
value of the WRR
and the value of the SP
cannot be interleaved.
That is, except for the
default value,
Grooming Police
After Reloading can
be changed from SP to
WRR according to the
queue priorities in a
descending order
(CS7-BE).


according to the
Policy Weight(%) 1 to 100 25 l This parameter

specifies the weight of
the policy in the WRR
queue. The weight
indicates the
percentage of the
bandwidth resources
obtained by the WRR
queue.
set only when
Grooming Police
After Reloading is set
to WRR.
according to the
Bandwidth Limit Disabled Disabled l This parameter

whether traffic
shaping is enabled for
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the
CIR(kbit/s) - - Traffic shaping for an

single token bucket two
color marker algorithm.
the PIR is valid.

PIR(kbit/s) - - l When the buffer queue

are processed as
PIR.
is not empty, the
packets whose rate
of the PIR directly
PIR.
according to the
CBS(byte) - - l It is recommended that

you set the value of the
CBS equal to the value
of the PIR. In actual
traffic shaping
processing, only the
PBS is valid.
according to the

PBS(byte) - - l When the buffer queue

packets can be
burst packets is
determined by the
PBS.
according to the
Related Tasks

This parameter describes the parameters that are used for creating traffic classification.
Navigation Path
2. Click the Traffic Classification Configuration tab.
3. Click New. The Create Traffic Classification dialog box is displayed.

Traffic Classification ID 1 to 1024 - This parameter specifies

the ID of the traffic
classification.

ACL Action Permit Permit l The access control list

Deny (ACL) determines
whether to forward or
discard the packets
that enter the port
according to the
specified matching
rules.
set to Permit, the ACL
on the ingress side
filters the packets that
enter the port. Only the
packets that match the
specified rules can be
received by the port.
set to Deny, ACL
processing is not
performed for the
packets over the
ingress port.
Ingress Parameters
Logical Relation And And l This parameter

Between Matched Rules specifies the logical
relationship between
the traffic
classification
matching rules.
l The OptiX RTN 950
the logical AND
between multiple
matching rules.

Match Type DSCP Value - l After you click Add or

CVlan ID Delete, complex
traffic classification
CVlan priority can be performed on
SVlan ID the traffic that enters
SVlan priority the ingress port
according to the preset
matching rules.
l In the case a specific
service, complex
traffic classification
can be divided into
basic traffic types
according to the DSCP
value, C_VLAN ID,
C_VLAN priority,
S_VLAN ID, or
S_VLAN priority.
Traffic type is based
on the associated
Ethernet packets.
Therefore, this
parameter is set
according to the packet
type and the planning
information.
Match Value DSCP Value: 0 to 63 - l If the matching value

CVlan ID: 1 to 4094 of the packets is the
same as the preset
CVlan priority: 0 to 7 Match Value, the
SVlan ID: 1 to 4094 packets match the
SVlan priority: 0 to 7 rules of complex
traffic classification.
according to the

CoS - - l This parameter

CS7 specifies the PHB
service class queue
CS6 mapped by the traffic
EF classification packets.
AF4 l If this parameter is set
AF3 to empty (-), the traffic
classification packets
AF2
map the PHB service
AF1 class queue according
BE the mapping relation
specified in the topic
about Diffserv domain
management.
according to the
Bandwidth Limit Disabled Enabled l This parameter

whether the CAR
operation is performed
for the flow in the
ingress direction.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the

CIR(kbit/s) - - l When the rate of the

packets is not more
than the CIR, the
packets are marked
blue and pass the CAR
policing. These
packets are first
forwarded in the case
of network congestion.
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 can
pass the restriction of
the CAR and are
marked yellow. The
processing method of
the packets marked
yellow can be set to
"Pass" or "Remark".
"Remark" indicates
mapped into another
specified queue of a
higher priority (this is
equal to changing the
priority of the packets)
and then forwarded to
the next port. If a
network congestion
event occurs again, the
packets marked
yellow can be
processed according to
the new priority.
according to the

PIR(kbit/s) - - l When the rate of the

the PIR, the packets
that exceed the rate
restriction are marked
red and directly
discarded.
l When the rate of the
the CIR but 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. The
processing method of
the packets marked
yellow can be set to
"Pass" or "Remark".
"Remark" indicates
mapped into another
the next port. If a
network congestion
event occurs again, the
packets marked
yellow can be
processed according to
the new priority.
according to the

CBS(byte) - - l During a certain

period, if the rate of the
packets whose
processing method is
marked "Pass" is not
more than the CIR,
certain burst packets
are allowed and can be
first forwarded in the
case of network
congestion. The
burst packets is
determined by the
CBS.
according to the
PBS(byte) - - l During a certain

period, if the rate of the
packets whose
processing method is
marked "Pass" is more
than the CIR but not
more than the PIR,
certain burst packets
are allowed and
marked yellow. The
burst packets is
determined by the
PBS.
according to the

Coloration Mode Color Blindness Color Blindness l This parameter

specifies the CAR
operation performed
by the equipment on
the packets. The
packets are dyed
according to the result
of the CAR operation.
The dying rule is
determined by the
comparison between
the rate of the packets
and the preset CAR
value.
l The OptiX RTN 950
supports Color
Blindness only.
Packet Color Red - Packets can be dyed in

Yellow three colors: red, yellow,
and green. The packets in
Green red are first discarded.
Handling Mode Discard - l This parameter

Pass specifies the method of
handling the packets.
Remark
l Discard: The packets
are discarded.
l Pass: The packets are
forwarded.
l Remark: The packets
are remarked.
"Remark" indicates
mapped into another
the next port.

Relabeled CoS CS7 - If the handling method is

CS6 set to "Remark", you can
reset the CoS of the
EF packets.
AF4
AF3
AF2
AF1
BE
Egress Parameters
Bandwidth Limit Disabled Enable l This parameter

Enable indicates or specifies
whether the traffic
shaping is performed
in the egress function.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the

CIR(kbit/s) - - l In the case that no

packets exist in the
egress queue: When
the rate of the packets
is not more than the
CIR, these packets
directly enter the
egress queue.
l In the case that certain
egress queue: The
packets whose rate
of the PIR directly
enter the egress queue,
which forwards the
packets to the next port
at the CIR.
according to the

PIR(kbit/s) - - l In the case that no

egress queue: If 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 enter the
egress queue, which
forwards the packets to
the next port at the
CIR. If the rate of the
the PIR, the packets
are directly discarded.
l In the case that certain
egress queue: The
packets whose rate
of the PIR directly
enter the egress queue,
which forwards the
packets to the next port
at the CIR.
according to the
CBS(byte) - - l If the rate of the

packets is not more
than the CIR during a
certain period, the
burst packets are
directly transmitted.
The maximum traffic
of the burst packets is
determined by the
CBS.
according to the

PBS(byte) - - l If the rate of the

the CIR but is not more
than the PIR during a
certain period, the
burst packets enter the
egress queue. The
burst packets is
determined by the
PBS.
according to the
Related Tasks

This topic describes the parameters that are used for creating port shaping management tasks.
Navigation Path
Management > Port Shaping Management from the Function Tree.
2. Click New.
Parameters for Port Shaping Management

Slot No. - - This parameter specifies

the slot ID.

the port.
CIR (kbit/s) - - Traffic shaping for an

CBS (byte) - - single token bucket two
PIR (kbit/s) - - color marker algorithm.
the PIR is valid.

PBS (byte) - - If the traffic shaping

function is enabled, OptiX
RTN 950 processes the
packets in the buffer
queue through the
following methods when
no packets are available in
the queue.
are processed as
PIR.
packets can be
burst packets is
determined by the
PBS.
is not empty, the
packets whose rate
of the PIR directly
PIR.
Related Tasks


This section describes the parameters for the Ethernet ports on the packet plane.

This topic describes the parameters that are related to the basic attributes of an Ethernet interface.
This topic describes the parameters that are related to flow control.
This topic describes the parameters that are related to the Layer 2 attributes.
This topic describes the parameters that are used for configuring the advanced attributes.

This topic describes the parameters that are related to the basic attributes of an Ethernet interface.
Navigation Path
2. Click the General Attributes tab.


the port name.

the port name.
Enable Port Enabled Enabled This parameter indicates

Disabled the working mode of the
port.
Port Mode - - This parameter indicates

the port mode.

Encapsulation Type Null - l This parameter

802.1Q specifies the method of
the port to process the
QinQ received packets.
l If you set this
parameter to Null, the
port transparently
transmits the received
packets.
l If you set this
parameter to 802.1Q,
the port identifies the
packets that comply
with the IEEE 802.1q
standard.
l If you set this
parameter to QinQ,
the port identifies the
packets that comply
with the IEEE 802.1ad
QinQ standard.

Working Mode Auto-Negotiation Auto-Negotiation l The Ethernet ports of

10M Half-Duplex different types support
different working
10M Full-Duplex modes.
100M Half-Duplex l When the equipment
100M Full-Duplex on the opposite side
1000M Full-Duplex works in auto-
negotiation mode, set
the working mode of
the equipment on the
local side to Auto-
Negotiation.
l When the equipment
on the opposite side
works in full-duplex
mode, set the working
mode of the equipment
on the local side to
10M Full-Duplex,
100M Full-Duplex, or
1000M Full-Duplex
depending on the port
rate of the equipment
on the opposite side.
l When the equipment
on the opposite side
works in half-duplex
mode, set the working
mode of the equipment
on the local side to
10M Half-Duplex,
100M Half-Duplex,
or Auto-Negotiation
depending on the port
rate of the equipment
on the opposite side.
l The GE optical
interface supports the
1000M full-duplex
mode only.
Max Frame Length 1518 to 9600 1522 The value of this

(byte) parameter should be
greater than the length of
any frame to be
transported.

Auto-Negotiation Auto-Negotiation 100M Full-Duplex l This parameter

Enable 10M Half-Duplex specifies the auto-
negotiation capability
10M Full-Duplex of the Ethernet port.
100M Half-Duplex l This parameter is valid
100M Full-Duplex only when Working
Mode is set to Auto-
1000M Full-Duplex Negotiation.
Logical Port Attribute Optical Port Optical Port l This parameter

Electrical Port specifies the attribute
of the logical port.
l The SFP on the
EM6F, CSHB and
CSHC board supports
the optical port and
electrical port.
Physical Port Attribute - - This parameter indicates

the attribute of the
physical port.
Related Tasks

This topic describes the parameters that are related to flow control.
Navigation Path
2. Click the Flow Control tab.


the port name.

Non-Autonegotiation Disabled Disabled l This parameter is valid

Flow Control Mode Enabled only when Working
Mode is not set to
Auto-Negotiation.
l The non-
autonegotiation flow
control mode of the
equipment on the local
side must be consistent
with the non-
autonegotiation flow
control mode of the
equipment on the
opposite side
Auto-Negotiation Flow Disabled Disabled l This parameter is valid

Control Mode Enable Symmetric Flow only when Working
Control Mode is set to Auto-
Negotiation.
l The auto-negotiation
flow control mode of
the equipment on the
local side must be
consistent with the
auto-negotiation flow
control mode of the
equipment on the
opposite side
Related Tasks

This topic describes the parameters that are related to the Layer 2 attributes.
Navigation Path
2. Click the Layer 2 Attributes tab.



the port name.
QinQ Type Domain - - l This parameter

specifies the QinQ
type domain.
l When Encapsulation
Type in the General
Attributes tab page is
set to QinQ, you need
to set QinQ Type
Domain. The default
value is 88A8.
l When Encapsulation
Type in the General
Attributes tab page is
set to Null or 802.1Q,
you cannot set QinQ
Type Domain. In this
case, QinQ Type
Domain is displayed
as FFFF and cannot be
changed.
l QinQ Type Domain
should be set to the
same value for all the
ports on the EM6T/
EM6F board.

TAG Tag Aware Tag Aware l This parameter

Access specifies the TAG flag
of a port. For details
Hybrid about the TAG flags
and associated frame-
processing methods,
see Table B-2.
l If all the accessed
services are frames
with the VLAN tag
(tagged frames), this
parameter is set to Tag
Aware.
l If all the accessed
services are frames
without the VLAN tag
(untagged frames),
Access.
l If the accessed
services contain
tagged frames and
untagged frames, this
parameter is set to
Hybrid.
Default VLAN ID 1 to 4094 1 l This parameter is valid

only when TAG is set
to Access or Hybrid.
l For details about the
functions of this
parameter, see Table
B-2.
situations.

VLAN Priority 0 to 7 0 l This parameter is valid

only when TAG is set
to Access or Hybrid.
l For details about the
functions of this
parameter, see Table
B-2.
l When the VLAN
priority is required to
divide streams or to be
used for other
purposes, this
parameter is set
according to the
In normal cases, it is
Table B-2 Methods used by Ethernet interfaces to process data frames

Port Type of Data Processing Method
Frame
Tag Aware Access Hybrid
Ingress UNI Tagged frame The port receives the The port discards The port receives
frame. the frame. the frame.
Untagged frame The port discards the The ports add the The ports add 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 receive frame and receive
the frame. the frame.

Port Type of Data Processing Method

Frame
Egress UNI 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.
Related Tasks

This topic describes the parameters that are used for configuring the advanced attributes.
Navigation Path


the port name.
Port Physical - - This parameter indicates

Parameters the physical parameters of
the port.

MAC Loopback Non-Loopback Non-Loopback l This parameter

Inloop specifies the loopback
state at the MAC layer.
When this parameter is
set to Inloop, the
Ethernet signals
transmitted to the
opposite end are
looped back.
l In normal cases, it is
PHY Loopback Non-Loopback Non-Loopback l This parameter

Inloop specifies the loopback
state at the PHY layer.
When this parameter is
set to Inloop, the
Ethernet physical
signals transmitted to
the opposite end are
looped back.
l In normal cases, it is
MAC Address - - This parameter indicates

port.
Transmitting Rate(kbit/ - - This parameter indicates

s) the rate at which the data
packets are transmitted.
Receiving Rate(kbit/s) - - This parameter indicates

the rate at which the data
packets are received.
Loopback Check - - This parameter specifies

whether to enable loop
detection, which is used to
check whether a loop
exists on the port.
Loopback Port - - This parameter specifies

Shutdown whether to enable the loop
port shutdown function.

Enabling Broadcast Disabled Disabled This parameter specifies

Packet Suppression Enabled whether to limit the traffic
rate of the broadcast
packets according to the
proportion of the
broadcast packets in the
total packets. When the
equipment at the opposite
end may encounter a
broadcast storm, this
parameter is set to
Enabled.
Broadcast Packet 0 to 100 30 When the proportion of

Suppression Threshold the broadcast packets in
the total packets exceeds
the value of this
parameter, the received
broadcast packets are
discarded. The value of
this parameter should be
more than the proportion
of the broadcast packets in
the total packets before
the broadcast storm
occurs. In normal cases,
30% or higher.
Related Tasks
B.10 Parameters for Ethernet Services and Ethernet Features

on the EoPDH Plane
EoPDH plane, including service parameters, protocol parameters, OAM parameters, Ethernet
port parameters, and QoS parameters.

This section describes the parameters for EoPDH-plane Ethernet services.
This section describes the parameters for EoPDH-plane Ethernet protocols.
This section describes the parameters for the Ethernet OAM on the EoPDH plane.


This section describes the parameters for the QoS on the EoPDH plane.
This section describes the parameters for the Ethernet ports on the EoPDH plane.

This section describes the parameters for EoPDH-plane Ethernet services.

This section describes the parameters for creating an Ethernet line service.
B.10.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line
Services
This section describes the parameters associated with QinQ-based Ethernet line services, which
need to be set on the NMS.
This section describes the parameters for Ethernet line services.
B.10.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services
Based on IEEE 802.1d/802.1q Bridge
This section describes the parameters for creating an Ethernet LAN service.
B.10.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based
Ethernet LAN Service
This section describes the parameters associated with IEEE 802.1ad bridge-based Ethernet LAN
services, which need to be set on the NMS.
This section describes the parameters for creating VLAN filtering tables.
This section describes the parameters associated with the aging time of MAC address table
entries, which need to be set on the NMS.

This section describes the parameters for creating an Ethernet line service.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose
Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.
2. Deselect Display QinQ Shared Service.
3. Click New.


Board - - Displays the board name.
Service Type EPL EPL Specify the Ethernet service type to EPL.
Direction Bidirectional Bidirectional l If this parameter is set to

Unidirectional Unidirectional, you only need to create
a service from the service source to the
service sink. That is, there is traffic only
in the direction from the service source
to the sink port.
l If this parameter is set to Bidirectional,
you need to create a service from the
service source to the service sink and a
service from the service sink to the
service source. That is, there is traffic in
the direction from the service source to
the sink port and in the direction from the
service sink to the source port at the same
time.
Source Port - - l Specifies the port of the service source.

l When you create bidirectional Ethernet
services from a PORT to a VCTRUNK,
it is recommended that you set the PORT
to the source port.
Source VLAN(e.g. 1-4095 - l This parameter can be set to null, a

1,3-6) number, or several numbers. When
setting this parameter to several
numbers, use the comma (,) to separate
the discrete numbers, or use the hyphen
(-) to represent consecutive numbers. For
1, 3, 4, 5, and 6.
l The number of VLANs must be the same
as the value of Sink VLAN(e.g. 1,3-6).
l If this parameter is set to null, all the
services at the source port are used as the
service source.
l If this parameter is not set to null, only
the service that carries a specified VLAN
ID at the source port can be used as the
service source.

Sink Port - - l Specifies the port of the service sink.

l This parameter cannot take the same
value as Source Port.
l When you create bidirectional Ethernet
services from a PORT to a VCTRUNK,
it is recommended that you set the
VCTRUNK to the sink port.
Sink VLAN(e.g. 1-4095 - l This parameter can be set to null, a

1,3-6) number, or several numbers. When
setting this parameter to several
numbers, use the comma (,) to separate
the discrete numbers, or use the hyphen
(-) to represent consecutive numbers. For
1, 3, 4, 5, and 6.
l The number of VLANs must be the same
as the value of Source VLAN(e.g.
1,3-6).
l If this parameter is set to null, all the
services at the sink port are used as the
service sink.
l If this parameter is not set to null, only
the service that carries a specified VLAN
ID at the sink port can be used as the
service sink.
Table B-4 Parameters for port attributes

Port - - Displays the ports involved in the Ethernet

service.
Port Type - - Displays the network attribute of the

Ethernet port.
Port Enabled Enabled Disabled l When the source port or the sink port is
Disabled set to a PORT, set Port Enabled to
Enabled.
l This parameter need not be set when the
source port or sink port is a VCTRUNK.

TAG Tag Aware Tag Aware l If all the accessed services are frames
Access with VLAN tags (tagged frames), set this
parameter to Tag Aware.
Hybrid
l If all the accessed services are frames
without VLAN tags (untagged frames),
set this parameter to Access.
l If the accessed services contain tagged
frames and untagged frames, set this
parameter to Hybrid.
Table B-5 Parameters for bound paths

VCTRUNK Port VCTRUNK1- VCTRUNK1 Specifies the VCTRUNK to bind paths.

VCTRUNK16
Level - - Displays the level of the bound VC path.

In the case of the EFP8 board, this parameter
always takes the value of VC12-Xv.
Direction Direction Direction l Specifies the direction of the bound path.

Uplink l Set this parameter to Bidirectional
Downlink unless otherwise specified.
Available - - l Displays the available VC4 paths.

Resources l In the case of the EFP8 board, this
parameter always takes the value of
VC4-1.
Available VC12-1-VC12-63 - Specifies the available timeslots.

Timeslots
Bound Path - - You need to plan and set this parameter

according to the following principles:
l The capacity of the VCTRUNK is
determined by the actual bandwidth
required by the services.
l The EFP8 board supports 16
VCTRUNKs. Each VCTRUNK can
bind a maximum of 16 VC-12 paths and
the total number of bound VC-12 paths
cannot exceed 63.
Number of Bound - - Displays the number of the bound VC path.

Paths

Activation Status - - Displays the activation status of the bound

VC path.
Related Tasks
B.10.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based

Ethernet Line Services
This section describes the parameters associated with QinQ-based Ethernet line services, which
need to be set on the NMS.
Navigation Path
1. In the NE Explorer, select the EFP8 board, and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
2. Select Display QinQ Shared Service.
3. Click New.
Service Type EPL EPL Specifies the service type to EVPL(QinQ).

EVPL(QinQ)

Unidirectional Unidirectional, only the service from
the service source to the service sink is
created. That is, the service source is
forwarded only to the sink port.
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. That is, when
the service source is forwarded to the
sink port, the service sink is forwarded to
the source port.
parameter to Bidirectional.

Operation Type l Add S-VLAN Strip S-VLAN l When used for private line services,
l Transparently QinQ can process VLAN tags in
transmit C- different manners as required.
VLAN l When Service Direction is set to
l Transparently Unidirectional, you can set Operation
transmit S- Type to Strip S-VLAN.
VLAN l Set this parameter according to actual
l Transparently situations.
transmit S-
VLAN and C-
VLAN
l Translate S-
VLAN
l Translate S-
VLAN and
transparently
transmit C-
VLAN
l Strip S-VLAN
Source Port - - l Specifies the port where the service

source resides.
l When creating a bidirectional Ethernet
service from a PORT to a VCTRUNK, it
is recommended that you use the PORT
as the source port.
Source C-VLAN 1-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 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 value range of this parameter work as
the service source.

Source S-VLAN 1-4095 - l This parameter must be set to a

numerical value.
l Only the service of the source port whose
S-VLAN ID is equal to the value of this
parameter work as the service source.
Sink Port - - l Specifies the port where the service sink

resides.
l This parameter must be set to be a value
different from Source Port.
l When creating a bidirectional Ethernet
service from a PORT to a VCTRUNK, it
is recommended that you use the
VCTRUNK as the sink port.
Sink C-VLAN(e.g. 1-4095 - l You can set this parameter to null, a

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 VLANs set in this
parameter should be the same as the
number of VLANs set in Source C-
VLAN(e.g. 1, 3-6).
l When you set this parameter to null, all
the services of the sink port work as the
service sink.
l When you set this parameter to a non-
null value, only the services of the sink
port whose VLAN IDs are included in
the value range of this parameter work as
the service sink.
Sink S-VLAN 1-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 AUTO Displays the C-VLAN priority.
S-VLAN Priority AUTO AUTO Specifies the S-VLAN priority. The bigger
Priority 0 to Priority the value, the higher the priority.
7

Table B-7 Parameters of port attributes
Port - - Displays the ports that are configured to

transmit the service.

Ethernet port.
Port Enabled Enabled - l When the source port or the sink port is
Disabled set to a PORT, set Port Enabled to
Enabled.
l This parameter need not be set when the
source port or sink port is a VCTRUNK.
TAG - - This parameter is invalid for QinQ line

services.

VCTRUNK16



VC4-1.

Timeslots

cannot exceed 63.


Paths

VC path.
Related Tasks

This section describes the parameters for Ethernet line services.
Navigation Path
In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration >
Table B-9 Parameters on the main interface (Display QinQ Shared Service is not selected)
Service Type - - Displays the service type.
Service Direction - - Displays the service direction.
Source Port - - Displays the port of the service source.
Source VLAN - - Displays the VLAN ID of the service source.
Sink Port - - Displays the port of the service sink.
Sink VLAN - - Displays the VLAN ID of the service sink.
Activation Status - - Displays whether to activate the service.
Table B-10 Parameters on the main interface (Display QinQ Shared Service is selected)
Port Type - - Displays the service type.

Source Port - - Displays the port of the service source.
Source C-VLAN - - Displays the VLAN ID of the service source.
Source S-VLAN - - l Displays the S-VLAN ID of the service

source.
l This parameter can be set only for the
QinQ-based EVPL service.
Sink Port - - Displays the port of the service sink.
Sink C-VLAN - - Displays the VLAN ID of the service sink.
Sink S-VLAN - - l Displays the S-VLAN ID of the service

sink.
C-VLAN Priority - - l Displays the priority of the C-VLAN.

S-VLAN Priority - - l Displays the priority of the S-VLAN.

Activation Status - - Displays whether to activate the service.
Table B-11 Parameters for port attributes

Port - - Displays the port name.

Ethernet port.
Port Enable - - When the source port or sink port is a PORT,

this parameter indicates whether the port is
enabled.
TAG - - Displays the tag attribute of the Ethernet

port.


VCTRUNK Port - - Displays the VCTRUNK that binds VC

paths.
Level - - Displays the level of the bound VC paths.
Service Direction - - Displays the direction of the bound VC

paths.
Bound Path - - Displays the serial numbers of the bound VC

paths.
Number of Bound - - Displays the number of the bound VC paths.

Paths
Activation Status - - Displays whether the bound VC paths are

activated.
Related Tasks
B.10.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN

Services Based on IEEE 802.1d/802.1q Bridge
Navigation Path
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
2. Click New.

Board - - Displays the board that is configured with a

bridge.
VB name - - Describes the bridge. It is recommended that

you set this parameter to a character string
that indicates the function of the bridge.

Bridge Type 802.1q 802.1q l If this parameter is set to 802.1q, an

802.1d IEEE 802.1q bridge is created.
802.1ad l If this parameter is set to 802.1d, an
IEEE 802.1d bridge is created.
Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode, all
Mode Filter Enable Filter Enable the VLANs share one MAC address
(supported by the (supported by the table. When the bridge uses the IVL
IEEE 802.1q IEEE 802.1q mode, each VLAN has an MAC address
bridge and IEEE bridge and the table.
802.1ad bridge, IEEE 802.1ad l When the filtering function is enabled at
unsupported by bridge) the ingress port, the ingress port checks
the IEEE 802.1d l SVL/Ingress the VLAN tags of all incoming packets.
bridge) Filter Disable If the VLAN ID contained in the VLAN
l SVL/Ingress (supported by the tag of a packet is not included in the
Filter Disable IEEE 802.1d VLAN filtering table, the packet is
(supported by the bridge and the discarded. When the filtering function is
IEEE 802.1d IEEE 802.1ad disabled at the ingress port, the ingress
bridge and IEEE bridge) port does not check any VLAN tag of the
802.1ad bridge, incoming packets.
unsupported by
the IEEE 802.1q
bridge)
Bridge Learning - - Displays the learning mode of the bridge.

Mode
Ingress Filter - - Displays whether the filtering function is

enabled at the ingress port.
MAC Address Self- - - Displays whether the MAC address self-

learning learning of the bridge is enabled.
Table B-14 Parameters for mounting services

VB Port - - Displays the ID of the logical port on the

bridge.
Mount Port - - Displays or specifies which physical port or

VCTRUNK on the Ethernet switch board is
Port Type - - Displays the network attribute of the port

Port Enabled Disabled - Displays or specifies whether the port

Enabled mounted to the bridge is enabled.

TAG Access Tag Aware Displays or specifies the tag attribute of the
Tag Aware port mounted to the bridge.
Hybrid
Default VLAN ID - - Displays or specifies the default VLAN ID

of the port mounted to the bridge.
This parameter is valid only when you set
the tag attribute of the port to Access or
Hybrid.
Working Mode Auto-Negotiation Auto-Negotiation Displays or specifies the working mode of

10M Half-Duplex the port mounted to the bridge.
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
Active - - Displays whether to activate the service.
Service Direction - - Displays the direction of the service.
C-VLAN - - The IEEE 802.1d/802.1q bridge does not

support this parameter.
S-VLAN - - The IEEE 802.1d/802.1q bridge does not

S-VLAN Priority - - The IEEE 802.1d/802.1q bridge does not

C-VLAN Priority - - The IEEE 802.1d/802.1q bridge does not

Table B-15 Parameters for mounting configuration

Available Mounted - - Displays which physical port or VCTRUNK

Ports on the Ethernet switch board can be mounted
to the bridge.
Selected Mounted - - Displays which physical port or VCTRUNK

Ports on the Ethernet switch board is mounted to
the bridge.



VCTRUNK16



VC4-1.

Timeslots

cannot exceed 63.

Paths

VC path.
Related Tasks
B.10.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad

Bridge-Based Ethernet LAN Service
This section describes the parameters associated with IEEE 802.1ad bridge-based Ethernet LAN
services, which need to be set on the NMS.

Navigation Path
1. In the NE Explorer, select the EFP8 board, and then choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
2. Click New.
Board - - Displays the board where the bridge is

configured.
VB Name - - This parameter is a string that describes the

bridge. It is recommended that you set this
parameter to a character string that contains
the information about the detailed
application of the bridge.
Bridge Type 802.1q 802.1q When this parameter is set to 802.1ad,

802.1d create the IEEE 802.1ad bridge.
802.1ad
Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode, all
Mode Filter Enable Filter Enable the VLANs share one MAC address
(supported by the (supported by the table. When the bridge uses the IVL
802.1q bridge 802.1q bridge mode, all the VLANs correspond to their
and 802.1ad and the 802.1ad respective MAC address tables.
bridge, bridge) l If the ingress filter is enabled, the VLAN
unsupported by l SVL/Ingress tag is checked at the ingress port. If the
the 802.1d Filter Disable VLAN ID does not equal the VLAN ID
bridge) (supported by the of the port defined in the VLAN filtering
l SVL/Ingress 802.1d bridge table, the packet is discarded. If the
Filter Disable and the 802.1ad ingress filter is disabled, the preceding
(supported by the bridge) described check is not conducted.
802.1d bridge
and 802.1ad
bridge,
unsupported by
the 802.1q
bridge)
Bridge Learning - - Displays the bridge learning mode.

Mode
Ingress Filter - - Displays whether the ingress filter function

is enabled.
MAC Address Self- - - Displays whether the MAC address self-

learning learning function of the bridge is enabled.

Table B-18 Parameters of service mounting

VB Port - - Displays the ID of the logical port of the

bridge.
Mount Port - - Displays or specifies the external port or

VCTRUNK on the Ethernet switching
board that is connected to the bridge.

external port/VCTRUNK connected to the
bridge.
Port Enabled Disabled - Displays or specifies whether the external

Enabled port connected to the bridge is enabled.
TAG - - This parameter is invalid in the case of

Ethernet LAN services based on 802.1ad
bridge.
Default VLAN ID - - Displays or specifies the default VLAN ID.

This parameter is valid only when TAG is
set to Access or Hybrid.
Working Mode Auto-Negotiation Auto-Negotiation Displays or specifies the working mode of

10M Half-Duplex the external port.
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
Activate - - Displays whether the service is activated.
C-VLAN - - Displays or specifies the C-VLAN ID that

the data frames carry.
Is valid only when the bridge is an IEEE
802.1ad bridge and Operation Type is set
to Add S-VLAN Base for Port and C-
VLAN.
Specifies the mapping relationship between
the C-VLAN ID carried by the data frames
and the S-VLAN ID to be added.

S-VLAN - - Displays or specifies the S-VLAN ID that

the data frames carry.
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 ID.
VLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify the
mapping relationship between the S-
VLAN ID to be added and the C-VLAN
ID carried by the data frames that enter
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 ID
to be carried by the data frames that enter
S-VLAN Priority - - Displays or specifies the S-VLAN priority.
C-VLAN Priority - - Displays or specifies the C-VLAN priority.
Table B-19 Parameters of service mounting

Operation Type Add S-VLAN base Add S-VLAN base For the meaning of each operation type, see
for port for port Application of the QinQ Technology in
Add S-VLAN base 802.1ad Bridge Services in the Feature
for Port and C- Description.
VLAN
Mount Port
Mount Port and base
for Port and S-
VLAN
VB Port - - Specifies the ID of the logical port of the

bridge.
Mount Port - - Selects the external port or VCTRUNK on

the Ethernet switching board that is
connected to the bridge.
Port Type - - Displays the port type.

C-VLAN 1-4095 - Is valid only when Operation Type is set to

Add S-VLAN Base for Port and C-
VLAN.
Specifies the mapping relationship between
the C-VLAN ID carried by the data frames
and the S-VLAN ID to be added.
S-VLAN 1-4095 - l When Operation Type is set to Add S-

specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN ID.
mapping relationship between the S-
VLAN ID to be added and the C-VLAN
ID carried by the data frames that enter
this parameter specifies the S-VLAN ID
S-VLAN Priority AUTO AUTO Specifies the S-VLAN priority.

Priority 0 to Priority
7
C-VLAN Priority AUTO AUTO Specifies the C-VLAN priority.


VCTRUNK16




VC4-1.

Timeslots

cannot exceed 63.

Paths

VC path.
Related Tasks

Navigation Path
Board - - Displays the board that is configured with a

bridge.
VB ID - - Displays the ID of the bridge.

VB Name - - This parameter is a character string that

describes the bridge. It is recommended that
you set this character string to a value that
indicates the specific purpose of the bridge.
Bridge Type - - Displays the type of the bridge.
Bridge Switch - - Displays the switching mode of the bridge.

Mode
Bridge Learning - - Displays the learning mode of the bridge.

Mode
Ingress Filter - - Displays whether the filtering function is

enabled at the ingress port.
MAC Address self- - - Displays whether the MAC address self-

Learning learning of the bridge is enabled.
Active - - Displays whether to activate the service.
Table B-22 Parameters for mounting services


bridge.
Mount Port - - Displays or specifies which physical port or

VCTRUNK on the Ethernet switch board is
Port Type - - Displays the network attribute of the port

Port Enable - - Displays or specifies whether the port

mounted to the bridge is enabled.
Hub/Spoke Hub Hub Displays or specifies the Hub/Spoke

Spoke attribute of the port mounted to the bridge.
l Hub ports can mutually access each
other.
l Hub ports and Spoke ports can mutually
access each other.
l Spoke ports cannot mutually access each
other.

TAG - - Displays or specifies the TAG attribute of

the mounted port in the case of Ethernet
LAN services based on 802.1d bridge or
802.1q bridge.
This parameter is invalid in the case of
Ethernet LAN services based on 802.1ad
bridge.
Default VLAN ID - - Displays or specifies the default VLAN ID

of the port mounted to the bridge.
This parameter is valid only when you set
the tag attribute of the port to Access or
Hybrid.
Working Mode - - Displays or specifies the working mode of

the port mounted to the bridge.
Service Direction - - Displays the direction of the service.
C-VLAN - - Displays or specifies the C-VLAN ID

carried by the data frame.
This parameter is valid only when the bridge
is an IEEE 802.1ad bridge and Operation
Type is 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 - - Displays or specifies the S-VLAN ID

carried by the data frame.
specifies the S-VLAN to be added to the
data frames that enter the IEEE 802.1ad
bridge.
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.
this parameter specifies the S-VLAN tag
S-VLAN Priority - - Displays the priority of the S-VLAN.
C-VLAN Priority - - Displays the priority of the C-VLAN.
Table B-23 Parameters for VLAN filtering table
VLAN ID - - Displays the VLAN ID that needs to be

filtered in forwarding.

bridge.
Forwarding - - Displays the actually specified forwarding

Physical Port port.
l Selected forwarding ports can send
packets only among themselves.
l Selected forwarding ports can only
forward the packet that carries the
VLAN ID tag. These ports discard the
packet that carries other VLAN tags.
l The broadcast packets transmitted by
any of Selected forwarding ports can
be forwarded only among Selected
forwarding ports.

Activation Status - - Displays whether the VLAN ID entry is

valid.
Table B-24 Parameters for VLAN unicast

VLAN ID - - l This parameter is invalid for the 802.1d

bridge and the 802.1ad bridge that adopt
the SVL learning mode. The entry
applies to all VLANs.
l In the case of the 802.1d bridge and the
802.1ad bridge that adopt the SVL
learning mode, the entry applies to only
the VLAN with the ID specified by this
parameter.
l Set this parameter according to the
MAC Address - - l Displays or specifies the static MAC

address.
l A static MAC address is an address that
is set manually. It does not age
automatically and needs to be deleted
manually.
l Generally, a static MAC address is used
for the port that receives but does not
forward Ethernet service packets or the
port whose MAC address need not age
automatically.

bridge.
Physical Port - - l Specifies the Ethernet port that

corresponds to the MAC address.
Aging Status - - Displays the aging status of the entries.
Table B-25 Parameters for disabling MAC addresses

VB - - Displays the ID and name of the bridge.

VLAN ID(e.g. - - Displays or specifies the VLAN ID of the

1,3-6) service. A disabled MAC address is valid for
the VLAN with the ID as specified by this
parameter.
MAC Address - - l Displays or specifies the disabled MAC

address. A disabled MAC address is also
called a blacklisted MAC address.
l The data frame that contains a disabled
destination MAC address is discarded. A
disabled MAC address needs to be set
manually and does not age.

VCTRUNK Port - - Displays the VCTRUNK to bind VC paths.
Level - - Displays the level of the bound VC paths.
Service Direction - - Displays the direction of the bound VC

paths.
Bound Path - - Displays the bound paths.
Number of Bound - - Displays the number of bound paths.

Paths
Table B-27 Parameters for self-learned MAC addresses

MAC Address - - l Displays or specifies the self-learned

MAC address. A self-learned MAC
address is also called a dynamic MAC
address.
l The entries of self-learned MAC
addresses are obtained when the bridge
uses the SVL or IVL learning mode. A
self-learned MAC address ages.

bridge.

VLAN ID - - l If the bridge uses the SVL learning

mode, this parameter is invalid. That is,
the preset self-learned MAC address
entries are valid for all VLANs.
l If the bridge uses the IVL learning mode,
the preset self-learned MAC address
entries are valid only for the VLAN with
the ID specified by this parameter.
Table B-28 Parameters for VLAN MAC address table capacity

VLAN ID - - Displays the VLAN ID specified for

querying the self-learned MAC addresses.
Actual MAC - - Displays how many MAC addresses are

Address Table actually self-learned in the query condition
Capacity of a specific VLAN ID.
Table B-29 Parameters for VB port MAC address table capacity


bridge. The ID is specified for querying the
self-learned MAC addresses.
Actual MAC - - Displays how many MAC addresses are

Address Table actually self-learned in the query condition
Capacity of a specific VB port.
Related Tasks

This section describes the parameters for creating VLAN filtering tables.

Navigation Path
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
2. Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
NOTE
In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the VB must
be IVL.
3. Click New.
VB - - Displays the bridge whose VLAN filtering

table is to be created.
VLAN ID(e.g. 1-4095 1 Specifies the VLAN IDs in the VLAN

1,3-6) filtering table.
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.
Available - - Displays the ports mounted to the bridge.

forwarding ports
Selected - - Displays the selected forwarding ports.

forwarding ports l The selected forwarding ports can send
packets only among themselves.
l The selected forwarding ports can only
forward 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 carries the
VLAN ID(e.g.1,3-6) tag can be
forwarded only among the selected
forwarding ports.
Related Tasks


This section describes the parameters associated with the aging time of MAC address table
entries, which need to be set on the NMS.
Navigation Path
In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching
Management > Aging Time from the Function Tree.

Board - - Displays the Ethernet board.
MAC Address l 1 to 120 Min 5 Min l If one entry is not updated in a certain
Aging Time l 1 to 120 Hour period, that is, if no new packet from this
MAC address is received to enable the
l 1 to 120 Day re-learning of this MAC address, this
entry is deleted automatically. This
mechanism is called aging, and this
period is called the aging time.
l If you set this parameter 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 you set this parameter to a very small
value, the bridge may delete the MAC
address table entry that is required,
which reduces the forwarding
efficiency.
l It is recommended that this parameter
takes the default value.
Related Tasks

This section describes the parameters for EoPDH-plane Ethernet protocols.

This section describes the parameters for the types of spanning tree protocols and for enabling
the spanning tree protocols.

This section describes the parameters for the spanning tree protocol.
This section describes the parameters associated with the spanning tree protocol, which need to
be set on the NMS.
This section describes the parameters associated with the type and enabled status of the spanning
tree protocol, which need to be set on the NMS.
This section describes the parameters associated with the point-to-point attribute of the spanning
This section describes the parameters for enabling the IGMP snooping protocol.
B.10.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table
Entries
This section describes the parameters for creating static multicast table entries.
B.10.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table
Entries
This section describes the parameters for the aging time of multicast table entries.
This topic describes the parameters for creating a link aggregation group (LAG).
B.10.2.12 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT
This section describes the parameters for creating point-to-point service LPT.
B.10.2.13 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service
LPT
This section describes the parameters for creating point-to-multipoint service LPT.
This section describes the parameters for creating port mirroring tasks.

This section describes the parameters for the types of spanning tree protocols and for enabling
the spanning tree protocols.
Navigation Path
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
2. Click the Protocol Enabled tab.

VB - - Displays the created bridge.
Protocol Enabled Enabled Disabled l Indicates whether to enable the spanning

Disabled tree protocol.
l Try to avoid Layer 2 service loopbacks
in the service networking. If no loop
occurs, you need not start the STP/
RSTP.
l If the loop is already formed in the
service networking, you must start the
STP or RSTP.
Protocol Type STP RSTP l This parameter is valid only when

RSTP Protocol Enabled is Enabled.
l The protocol type should be set
according to the requirement of the
interconnected Ethernet equipment. The
default value is recommended unless
otherwise specified.
Related Tasks

This section describes the parameters for the spanning tree protocol.
Navigation Path
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.

Priority 0-61440 32768 l The most significant 16 bits of the bridge

ID indicate the priority of the bridge.
l When the value is smaller, the priority is
higher. As a result, the bridge is more
likely to be selected as the root bridge.
l If the priorities of all the bridges on the
STP network take the same value, the
bridge whose MAC address is the
smallest is selected as the root bridge.
MAC Address - - Displays the MAC address of a bridge.
Max Age(s) 6-40 20 l 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
packet, and the greater the network
diameter. When the value of this
parameter is greater, however, the link
fault detection of the bridge is slower and
thus the network adaptability is reduced.
Hello Time(s) 1-10 2 l Indicates the interval for transmitting

CBPDU packets through the bridge.
l The greater the value of this parameter,
the less the network resources that are
occupied by the spanning tree. As the
value of this parameter increases,
however, the topology stability
decreases.
Forward Delay(s) 4-30 15 l 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 of the network state change.
Therefore, the topology changes are
slower and recovery in the case of faults
is slower.
TxHoldCout(per 1-10 6 Indicates how many times the port transmits

second) CBPDU packets in every second.
Related Tasks


This section describes the parameters associated with the spanning tree protocol, which need to
be set on the NMS.
Navigation Path
1. In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
2. Click the Port Parameters tab.

Port - - Displays the created bridge.
Priority 0-240 128 l The most significant eight bits of the port
ID indicate the port priority.
l The smaller the value of this parameter,
the higher the priority.
Port Path Cost 1-200000000 - l Indicates the status of the network to

which the port is connected.
l In the case of the bridges on both ends of
the path, set this parameter to the same
value.
Status - - Displays the state of a port.
Admin Edge Enabled Disabled l Is valid only when the RSTP is used.
Attribute Disabled l Specifies 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 Set this parameter to Enabled only when
the Ethernet port on the Ethernet board
is directly connected to the data
communication terminal equipment,
such as a computer. In other cases, it is
recommended that this parameter takes
the default value.

Protocol Enabled Enabled Enabled l Specifies whether the STP or RSTP is

Disabled enabled for the port.
l When this parameter is set to Disabled,
the port does not process or transmit the
BPDU.
Auto Edge Enabled Disabled l Is valid only when Admin Edge

Detection Disabled Attribute is set to Enabled.
if the bridge detects that this port is
connected to the port of another bridge,
the RSTP considers this port as a non-
edge port.
l When Admin Edge Attribute is set to
Enabled, set this parameter to
Enabled. In other cases, it is
recommended that this parameter takes
the default value.
Related Tasks

Navigation Path
2. Click the Bridge Running Information tab.
Priority - - Displays the priority of the bridge. The most

significant 16 bits of the bridge ID indicate
the priority of the bridge.

MAC Address - - Displays the MAC address of the bridge.
Designed Root - - Displays the priority of the specified bridge.

Bridge Priority
Designed Root - - Displays the MAC address of the specified

Bridge MAC bridge.
Address
Root Path Cost - - Displays the root path cost. The root path
cost is the path cost of the root port and is
used for calculating the network topology.
Root Port - - Displays the root port of the spanning tree

protocol.
Max Age(s) - - Displays the maximum age of the CBPDU

packet that is recorded by the port.
Hello Time(s) - - Displays the interval for transmitting the

CBPDU packets through the bridge.
Forward Delay(s) - - Displays the holding time of a port in

listening state and in learning state.
HoldCout - - Displays the number of times that each port

transmits CBPDU packets per second.
Related Tasks

Navigation Path
2. Click the Port Running Information tab.
Port - - Displays the logical port of the bridge.

Port ID - - Displays the port ID.
Port Status - - Displays the port status.
Port Path Cost - - Displays the port path cost.
Designated Port D - - Displays the ID of the specified port.
Designated Root - - Displays the priority of the specified root

Bridge Priority bridge.
Designated Root - - Displays the MAC address of the specified

Bridge MAC root bridge.
Address
Designated Path - - Displays the specified path cost.

Cost
Designated Bridge - - Displays the priority of the specified bridge.

Priority
Designated Bridge - - Displays the MAC address of the specified

MAC Address bridge.
Topology - - Displays the enabled status of topology

Detection detection.
Edge Port Status - - Displays the enabled status of the edge port.
Running Time(s) - - Displays the duration when the topology

remains unchanged.
Related Tasks

This section describes the parameters associated with the point-to-point attribute of the spanning
Navigation Path
2. Click the Point to Point Attribute tab.


Port - - Displays the internal and external ports on

the Ethernet board.
Point-to-point Adaptive Adaptive connection l This parameter is valid only when the
Attribute connection RSTP is used.
Link connection l If this parameter is set to Adaptive
Shared 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 port works in full-duplex
mode, the actual point-to-point attribute
of the port is True. If the port works in
half-duplex mode, the actual point-to-
point attribute of the port is False.
l If you set this parameter to Link
connection, the actual point-to-point
attribute of the port is True.
l If you set this parameter to Shared
media, the actual point-to-point attribute
of the port is False.
l Only the port whose actual point to point
attribute is True can transmit the fast
transition request and response
messages.
Related Tasks

This section describes the parameters for enabling the IGMP snooping protocol.
Navigation Path
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the
Function Tree.
2. Click the Enable IGMP Snooping Protocol tab.


VB - - Displays the ID of the bridge.
Protocol Enable Enabled Disabled l Specifies whether to enable the IGMP

Disabled snooping protocol.
l If the IGMP multicast router exists on
the interconnected Ethernet network,
enable the IGMP snooping protocol
according to the requirements of the
router.
The Discarded Tag Enabled Enabled l This parameter specifies the method of
of the Packet Disabled the port to process unknown multicast
Excluded in the packets. When the IEEE 802.1q or
Multicast Group 802.1ad bridge receives the multicast
packets whose multicast addresses are
not included in the multicast table, these
packets are considered as unknown
packets.
Protocol Enable is Enabled.
l If this parameter is set to Enabled,
unknown multicast packets are
discarded.
l If this parameter is set to Disabled,
unknown multicast packets are
broadcast in the VLAN.
l Set this parameter as required by the
IGMP multicast server.
Related Tasks
B.10.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static

Multicast Table Entries
This section describes the parameters for creating static multicast table entries.
Navigation Path
Function Tree.
2. Click the Static Multicast Table tab.

3. Click New.

VB ID - - Displays the ID of the created bridge.
VLAN ID - - Specifies the VLAN ID of the static

multicast table entry.
MAC Address - - l Specifies the MAC address in the static

multicast table.
Multicast Port - - l Specifies the port as an entry in the static

multicast table.
l An entry in the static multicast table does
not age.
Related Tasks
B.10.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast

Table Entries
This section describes the parameters for the aging time of multicast table entries.
Navigation Path
Function Tree.
2. Click the Multicast Aging Time tab.


Multicast Aging 1-120 8 l Specifies the aging time for multicast

Time(Min) table entries. When a dynamic multicast
table entry is not updated in a certain
period (that is, no IGMP request from
this multicast address is received), 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 great
value, the bridge stores excessive
multicast table entries that are no longer
needed, 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 entry that is needed,
which reduces the forwarding
efficiency.
l The default value is recommended.
Related Tasks

This topic describes the parameters for creating a link aggregation group (LAG).
Navigation Path
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
2. Click the Link Aggregation Group Management tab.
3. Click New.
Attribute Parameters
LAG No 1-12 1 Specifies the LAG number.
LAG Name - - Specifies the LAG name.

LAG Type Static Static l Static: A static LAG is created by the

Manual user. To add or delete a member port, you
need to run the Link Aggregation
Control Protocol (LACP) protocol. In a
static LAG, a port can be in selected,
standby, or unselected state. By running
the LACP protocol, devices exchange
aggregation information so that they
share the same aggregation information.
l Manual: A manual LAG is created by the
user. When you add or delete a member
port, you need not run the LACP
protocol. In a manual LAG, a port can be
in the UP or DOWN state. The system
determines whether to aggregate a port
according to its physical state (UP or
DOWN), working mode, and rate.
Load Sharing Sharing Sharing l Sharing: In a sharing LAG, all member

Non-Sharing ports always share the traffic load. The
sharing mode can improve bandwidth
utilization on a link. When the member
ports are changed or some member ports
fail, the traffic load of each member port
is automatically re-allocated.
l Non-Sharing: In a non-sharing LAG,
only one member port carries the traffic
load and the other member ports are in
Standby state. Actually, a non-sharing
LAG works in hot-standby mode. When
the active port fails, the system selects a
standby port to substitute for the failed
port, thus preventing a link failure.
Sharing Mode IP Sharing Mode IP Sharing Mode You can set this parameter only when Load
MAC Sharing Mode Sharing is Sharing.
Revertive Mode Revertive Revertive l You can set this parameter only when
Non-Revertive Load Sharing is Non-Sharing.
l If this parameter is set to Revertive,
services are automatically switched back
to the working path after the working
path recovers.
l If this parameter is set to Non-
Revertive, services are still transmitted
in the protection path after the working
path recovers and the LAG remains the
same.

Port Setting Parameters

Main Port - - l Specifies the main port in a LAG.

l After a LAG is created, you can add
Ethernet services to the main port only.
That is, services cannot be added to a
slave port.
l When Load Sharing is set to Non-
Sharing, the link connected to the main
port is the working path and the links
connected to the slave ports are
protection paths.
Available Slave - - l Specifies the salve port in a LAG.

Ports l After a LAG is created, you need to
perform manual operations to add or
delete a slave port.
Selected Slave - - Displays the selected slave ports.

Ports
Related Tasks

Navigation Path
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
2. Click the Link Aggregation Parameters tab.

Port Priority 0-65535 32768 l This parameter is valid only when LAG
Type of a LAG is set to Static.
l This parameter indicates the priorities of
the ports in a LAG as defined in the
LACP protocol. The smaller the value,
the higher the priority.

Parameters for the system settings

System Priority 0-65535 32768 l This parameter is valid only when LAG
Type of a LAG is set to Static.
l This parameter indicates the priority of a
LAG. The smaller the value, the higher
the priority.
l When the local LAG and the opposite
LAG negotiate through LACP packets,
one can obtain the system priority of the
other. The LAG with the higher system
priority is considered as the comparison
result. Then, the aggregation
information is consistent at both ends. If
the local LAG and the opposite LAG
have the same system priority, the MAC
addresses are compared. The LAG with
a lower MAC address is considered as
the comparison result. Then, the
aggregation information is consistent at
both ends.
System MAC - - Displays the MAC address of the system.

Address
Related Tasks
B.10.2.12 Parameter Description: LPT Management_Creation of Point-to-Point

Service LPT
This section describes the parameters for creating point-to-point service LPT.
Navigation Path
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click Query.

VCTRUNK Port - - Displays the VCTRUNK used by the

Ethernet service.

Direction - - l Displays the direction of the Ethernet

service at the port.
l The service direction is set to positive
when the source port is a PORT and the
sink port is a VCTRUNK; the service
direction is set to reverse when the
source port is a VCTRUNK and the sink
port is a PORT.
LPT Yes No Specifies whether to enable the LPT.

No
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l Specifies the bearer mode of the LPT
Ethernet packets.
GFP-CSF l The default value is recommended.
PORT-Type Port 0-10000 0 l When the link on which Ethernet

Hold-Off Time(ms) services are transmitted is configured
with other protection schemes, you need
to set the hold-off time of LPT. This
enables the NE to notify the equipment
at both ends of a transmission network of
the fault on the transmission link only
when the other protection schemes fail.
l This parameter is valid only in the
positive direction of LPT.
VCTRUNK Port 0-10000 0 l When the link on which Ethernet

Hold-Off Time(ms) services are transmitted is configured
with other protection schemes, you need
to set the hold-off time of LPT. This
enables the NE to notify the equipment
at both ends of a transmission network of
the fault on the transmission link only
when the other protection schemes fail.
l This parameter is valid only in the
reverse direction of LPT.
Related Tasks
B.10.2.13 Parameter Description: LPT Management_Creation of Point-to-

Multipoint Service LPT
This section describes the parameters for creating point-to-multipoint service LPT.

Navigation Path
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click PtoMP LPT. Then, the LPT Management dialog box appears.
3. Click New.
Parameters for Convergence Points

Port - - Specifies the port of the convergence point.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when the
Ethernet selected port is a VCTRUNK.
Port Hold-Off 0-10000 0 When the link on which Ethernet services

Time(ms) are transmitted is configured with other
protection schemes, you need to set the
hold-off time of LPT. This enables the NE
to notify the equipment at both ends of a
transmission network of the fault on the
transmission link only when the other
protection schemes fail.
Parameters for Access Points

Port - - Specifies the port at the access node.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when the
Ethernet selected port is a VCTRUNK.
Related Tasks

This section describes the parameters for creating port mirroring tasks.

Navigation Path
Configuration > Ethernet Interface Management > Port Mirroring from the Function
Tree.
2. Click New.

Mirror Listener - - l After the mirroring function of the port

Port is configured, you can monitor all the
mirrored ports by analyzing the packets
at the mirroring port only. As a result,
you can easily manage the ports.
l Mirror Listener Port indicates the port
that sends the packets copied from
Uplink Listened Port and Downlink
Listened Port.
l Mirror Listener Port cannot be set to a
port that carries any service.
Uplink Listener - - l Uplink Listener Port and Downlink

Port Listener Port indicate the ports that
copy packets for Mirror Listener Port.
Downlink Listener - -
l Uplink Listener Port can be a PORT or
Port
a VCTRUNK. As a PORT, the port
copies the packets that it receives; as a
VCTRUNK, the port copies the packets
that it transmits. Mirror Listener Port
sends the packets copied from Uplink
Listener Port.
l Downlink Listener Port can be a PORT
or a VCTRUNK. As a PORT, the port
copies the packets that it transmits; as a
VCTRUNK, the port copies the packets
that it receives. Mirror Listener Port
sends the packets copied from Downlink
Listener Port.
NOTE
The transmit direction and receive direction
mentioned in this section are related to the local
NE.

This section describes the parameters for the Ethernet OAM on the EoPDH plane.


This topic describes the parameters for creating maintenance domains (MDs).
This section describes the parameters for creating maintenance associations (MAs).
This section describes the parameters for creating a maintenance point (MP).
This section describes the parameters for enabling the LB.
This topic describes the parameters for enabling the LT.
This section describes the OAM parameters that are related to Ethernet ports.
This section describes the parameters for monitoring the OAM error frames at the Ethernet port.
This section describes the parameters for monitoring the OAM errored frames at the Ethernet
port.

This topic describes the parameters for creating maintenance domains (MDs).
Navigation Path
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MD from the drop-down list.

Maintenance Domain For example: MD1 - Specifies the name of the

Name MD.

Maintenance Domain Consumer High(7) Operator Low(0) Specifies the level of the
Level Consumer Middle(6) MD. The greater the value,
the higher the level.
Consumer Low(5)
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
Related Tasks

This section describes the parameters for creating maintenance associations (MAs).
Navigation Path
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MA from the drop-down list.
Maintenance Domain For example: MD1 - Displays the MD in which

Name an MA is to be created.
Maintenance For example: MA1 - This parameter specifies

Association Name the name of the MA,
which is a service-related
domain. By creating MAs,
the connectivity check
(CC) can be performed on
the network that transmits
a particular service
instance.

Related Tasks

This section describes the parameters for creating a maintenance point (MP).
Navigation Path
Tree.
2. Click New.
Maintenance - NULL Specifies the maintenance domain (MD) of

Domain Name the MP.
NOTE
An MD is not required for a common MP. For
the creation of a common MP, select NULL.
Maintenance - NULL Specifies the maintenance association (MA)

Association Name of the MP.
NOTE
An MA is not required for a common MP. For
the creation of a common MP, select NULL.
Node - - Specifies the port where you want to create

an MP.
VLAN ID - - l Configures the ID of the VLAN to which

the service of the MP belongs. The
information is contained in the OAM
data packet. The MPs with the same
VLAN ID in an MD can communicate
with each other.
l This parameter can be null in the case of
PORT services, but need to be set in the
case of PORT+VLAN services.
MP ID Standard MP: 00-00-0000 Uniquely identifies an MP. From the highest

00-00-0000 to FF- to the lowest, the first byte indicates the
FF-1FFF network number, the second byte indicates
Common MP: the number of the node in the local network,
00-00-0000 to FF- and the third and forth bytes indicate the ID
FF-FF00 of the MP on the network node. The MP ID
must be unique in the entire network.

Type MEP MEP Specifies the MP type defined in IEEE

MIP 802.1ag. An MP can be a maintenance
association end point (MEP) or a
maintenance association intermediate point
(MIP).
Direction Ingress Ingress l Specifies the direction of the MEP.

Egress l Set this parameter to Ingress if the OAM
data initiated by the MEP travels through
the Ethernet switching unit on the local
NE. Otherwise, set this parameter to
Egress.
Parameters for Advanced Attributes
Table B-41 Parameters for advanced attributes

Level Consumer High(7) Provider High(4) Specifies the level of a common MP. The
Consumer Middle greater the value, the higher the level.
(6) NOTE
This parameter is valid only for a common MP
Consumer Low(5) (NULL).
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
CC Status Active Inactive Specifies whether to enable the connectivity

Inactive check (CC) function at an MP.
LB Timeout(ms) 3000 to 60000, in 5000 l Specifies the timeout duration of an LB

step of 100 test.
l This parameter can be set only for an
MEP.
LT Timeout(ms) 3000 to 60000, in 5000 l Specifies the timeout duration of an LT

step of 100 test.
MEP.

CCM Sending Standard MP: Standard MP Specifies the interval for sending the CCM
Period(ms) 1000 1000 packet at the MP where the CC test is
performed.
10000 Common MP:
l If this parameter takes a very small
6000 5000 value, service bandwidth decreases
600000 significantly.
Common MP: l If this parameter takes a very great value,
1000 to 60000, in the CC test will become less capable in
step of 100 detecting service interruptions. The
default value is recommended.
MEP.
Related Tasks

This section describes the parameters for enabling the LB.
Navigation Path
Tree.
2. Select the node that requires an LB test, click OAM Operation, and select Start LB.

LB Source MP ID - - Specifies the ID of the

source maintenance point
in the LB test.
LB Sink MP ID - - Specifies the ID of the sink

maintenance point in the
LB test.
Test Result - - Indicates the result of one

LB test.

Test based on the MAC Selected Not selected Select this parameter for
Address Not selected an LB test based on MAC
addresses.
NOTE
This parameter is valid only
for a standard MP.
LB Sink MP MAC Specifies the MAC

Address address of the sink
maintenance point in the
LB test. This parameter is
valid only in the case of
Test based on the MAC
Address.
Related Tasks

This topic describes the parameters for enabling the LT.
Navigation Path
Tree.
2. Select the node that requires an LT test, click OAM Operation, and select Start LT.
LT Source MP ID - - Specifies the source MP in

the LT test.
LT Sink MP ID - - Specifies the sink MP in

the LT test.
Responding MP ID - - Displays the MP that

responds to the test.
Responding MP Type - - Displays the type of the

MP that responds to the
test.

Hop Count - - Displays the count of hops

between the source MP
and the responding MP.
That is, the number of
responding MPs from the
source MP to a certain
responding MP in an LT
test.
Test Result - - Indicates the result of one

LT test.
Related Tasks

This section describes the OAM parameters that are related to Ethernet ports.
Navigation Path
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
2. Click the OAM Parameter tab.

PORT - - Displays the name of the

external Ethernet port.
Enable OAM Protocol Enabled Disabled Specifies whether the

Disabled point-to-point OAM
protocol (IEEE 802.3ah
protocol) is enabled.
After the OAM protocol is
enabled, the current
Ethernet port starts to use
the preset mode to set up
an OAM connection with
the opposite end.

OAM Working Mode Active Active The negotiation mode of

Passive IEEE 802.3ah includes
active and passive modes.
If this parameter is set to
Active, the port can
initiate an OAM
connection. If this
parameter is set to
Passive, the port can only
respond to the OAM
connection requests from
the opposite end.
Remote Alarm Support Enabled Enabled Specifies whether the

for Link Event Disabled detected link event is
notified to the opposite
end (for example, error
frame periods, error
frames, and error frame
seconds).
Max OAM Packet - - Displays the maximum

Length(byte) length of the OAM
packets.
This parameter takes the
same value as the Max
Frame Length of the
external port.
Loopback Status - - Displays the loopback

status.
Related Tasks

This section describes the parameters for monitoring the OAM error frames at the Ethernet port.
Navigation Path
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
2. Click the OAM Error Frame Monitor tab.


PORT For example: - Displays the name of the external Ethernet

PORT1 port.
Error Frame 1000 to 60000, in 1000 In the specified Error Frame Monitor
Monitor(ms) step of 100 Window (ms), if the number of error frames
exceeds the specified Error Frame
Monitor Threshold (Entries) due to the
link degradation, the link event alarm is
reported.
Error Frame 1 to 4294967295, in 2 Specifies the threshold of monitoring error

Monitor Threshold step of 1 frames.
(Entries)
Error Frame 14880 to 8928000, 148800 Within the specified value of Error Frame
period Window in step of 1 Period Window (frame), if the number of
(frame) error frames on the link exceeds the preset
value of Error Frame Period Threshold
(frame), an alarm is reported.
Error Frame 1 to 892800000, in 2 Specifies the threshold of monitoring the

period Threshold step of 1 error frame period.
(frame)
Error Frame 10 to 900, in step of 60 If any error frame occurs in one second, this
Second Window(s) 1 second is called an error frame second.
Within the specified value of Error Frame
Second Window(s), if the number of error
frames on the link exceeds the preset value
of Error Frame Second Threshold (s), an
alarm is reported.
Error Frame 1 to 900, in step of 1 2 Specifies the threshold of monitoring error

Second Threshold frame seconds.
(s)
Related Tasks

This section describes the parameters for monitoring the OAM errored frames at the Ethernet
port.

Navigation Path
1. In the NE Explorer, select the EFP8 board and choose Configuration > Ethernet
Maintenance > Ethernet Port OAM from the Function Tree.
2. Click the Remote OAM parameter tab.

Field Value Range Default Value Description
Port - - Displays the name of the

remote Ethernet port.
Remote OAM Working - - Displays the working

Mode mode of the remote
Ethernet port.
Remote Alarm Support - - Displays whether the

for Link Event remote Ethernet port can
notify link events to the
local port.
Remote Side Loopback - - Displays how the remote

Response Ethernet port responds to a
loopback.
Unidirectional - - Displays whether the

Operation remote Ethernet port
supports unidirectional
operations.
Max.OAM Packet - - Displays the maximum

Length (byte) OAM packet size
supported by the remote
Ethernet port.
Related Tasks

This section describes the parameters for the QoS on the EoPDH plane.

This parameter describes the parameters for creating flows.
This section describes the parameters for creating CAR.
This section describes the parameters for creating CoS.


This section describes the parameters for creating CAR/CoS.
B.10.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues
This section describes the parameters for shaping management of egress queues.

This parameter describes the parameters for creating flows.
Navigation Path
2. Click the Flow Configuration tab.
3. Click New.


Flow Type Port Flow Port Flow l Port flow: The packets from a certain
Port+VLAN Flow port are classified as a type of flow. The
Ethernet service associated with this
Port+SVLAN Flow flow type is the line service or Layer 2
Port+CVLAN switching service that uses this port as
+SVLAN Flow the service source.
Port+VLAN l Port+VLAN flow: The packets that are
+Priority Flow 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 EVPL service (based on
VLAN) or EVPLAN service (based on
802.1q bridge) that uses this PORT
+VLAN as the service source.
l 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
802.1ad bridge) that uses this PORT
+SVLAN as the service source.
l Port+CVLAN+SVLAN flow: The
packets that are received from or
transmitted to 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
802.1ad bridge) that uses this PORT
+CVLAN+SVLAN as the service
source.
l Port+VLAN+Priority flow: The packets
that are from a certain port and have a
specified VLAN ID and a specified
VLAN priority are classified as a type of
flow. The associated Ethernet service of
this flow type is the line service that uses
this Port+VLAN+Priority as the service
source.

Port PORT1-PORT9, PORT1 l When the associated service is the line

VCTRUNK1- service, set this parameter to the source
VCTRUNK16 port or sink port of the associated
Ethernet service.
l When the associated service is the Layer
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 or Port
+VLAN+Priority 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+CVLAN+SVLAN
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
Port+SVLAN+CVLAN Flow.
l Set this parameter to the source S-VLAN
of the associated Ethernet service.
Priority - - l This parameter is valid only when Flow

Type is PORT+VLAN+Priority Flow.
l This parameter indicates the VLAN
priority of the flow-associated Ethernet
services.
Related Tasks

This section describes the parameters for creating CAR.
Navigation Path
1. In the NE Explorer, select the EFP8 board, and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
2. Click the CAR Configuration.
3. Click New.


CAR ID 1-512 1 This parameter identifies a CAR operation,

and is used to bind a flow to an associated
CAR operation.
Enabled/Disabled Enabled Disabled Indicates whether to enable the CAR

Disabled operation performed on the flow bound to
the CAR.
Committed 0-100032 0 l Indicates the CIR. When the rate of a

information Rate Step: 64 packet is not more than the CIR, this
(kbit/s) packet passes the restriction of the CAR
and is forwarded first even in the case of
network congestion.
l The value of this parameter should not
be more than the PIR.
Committed Burst 0-1024 0 Indicates the CBS. When the rate of a packet
Size(kbyte) that passes the restriction of the CAR is not
more than the CIR in a certain period, some
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 0-100032 0 l Indicates the PIR. When the rate of a

Rate(kbit/s) Step: 64 packet is more than the PIR, the packet
that exceeds the rate restriction is
directly discarded. When the rate of
packets is more than the CIR but is lower
than or equal to the PIR, these packets
whose rate exceeds the CIR can pass the
restriction of the CAR and are marked
yellow, and these packets are discarded
first in the case of network congestion.
be more than the port bandwidth.

Maximum Burst 0-1024 0 Indicates the MBS. When the rate of the
Size(kbyte) packet that passes the restriction of the CAR
is more than the CIR but is not more than
the PIR, some 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
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.
Related Tasks

This section describes the parameters for creating CoS.
Navigation Path
2. Click the CoS Configuration tab.
3. Click New.

CoS ID 1-64 1 This parameter identifies a CoS operation,

and is used to bind a flow to an associated
CoS operation.

CoS Type simple simple l If the CoS type of a flow is set to simple,
VLAN Priority all the packets in this flow are directly
scheduled to a specified egress queue.
IPTOS
l If the CoS type of a flow is set to VLAN
DSCP priority, the packets in this flow are
scheduled to specified egress queues
according to the user priorities specified
in the VLAN tags of these packets.
l If the CoS type of a flow is set to DSCP,
the packets in this flow are scheduled to
specified egress queues according to
differentiated services code point
(DSCP) in the IPv6 tags of these packets.
l If the CoS type of a flow is set to IP TOS,
the packets in this flow are scheduled to
specified egress queues according to the
TOS values carried in the IPv4 packets.
This CoS type is applicable to IPv4
packets.
CoS parameter - - Displays the CoS parameters corresponding

to different CoS types.
CoS Priority 0-7 - This parameter determines to which egress

queue a packet is schedule.
l Each Ethernet port on the EFP8 board
supports eight egress port queues.
Queues 1-8 respectively correspond to
the CoS priorities from 0 to 7.
l Queue 8, with the CoS priority of 7, is as
SP queue. Queues 1-7, with the CoS
priorities 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). On the EFP8
board, the weighted proportion of these
WRR queues cannot be changed.
l If the traffic shaping feature of some
queues is enabled, bandwidth is
allocated first to the queues whose traffic
shaping feature is enabled based on the
CIR. The remaining bandwidth is
allocated to the eight queues by using the
SP+WRR algorithm.
Related Tasks


This section describes the parameters for creating CAR/CoS.
Navigation Path
1. In the NE Explorer, select the required Ethernet switching board, and then choose
2. Click the Flow Configuration tab.
Flow Type - - Displays the type of a flow.
VB ID - - Displays the ID of the bridge.
Port - - Displays the port where a flow is to be

created.
C-VLAN - - l Displays the C-VLAN.

l This parameter is valid is Flow Type is
Port+VLAN Flow, Port+CVLAN
+SVLAN Flow, or Port+VLAN
+Priority Flow.
S-VLAN - - l Displays the S-VLAN.

l This parameter is valid when Flow
Type is Port+SVLAN Flow or Port
+CVLAN+SVLAN Flow.
Priority - - l Displays the priority of the flow.

l This parameter is valid when Flow
Type is Port+VLAN+Priority Flow.
Bound CAR - None 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 - None Indicates the CoS ID that corresponds to a

CoS operation.
Related Tasks

B.10.4.5 Parameter Description: QoS Management_Shaping Management of Egress

Queues
This section describes the parameters for shaping management of egress queues.
Navigation Path
QoS Management > Port Shaping Management from the Function Tree.
Port Queue - - Displays the queue name.
Status Enabled Disabled Indicates whether to enable the traffic

Disabled shaping feature of an egress queue.
CIR(kbit/s) 0-100032 0 l When the rate of a packet is not more

Step: 64 than the CIR, this packet directly enters
the egress queue.
be more than the PIR.
DCBS(kbyte) - 0 Displays the excess burst size.
PIR(kbit/s) 0-100032 0 l When the rate of a packet is more than

Step: 64 the PIR, the packet that exceeds the rate
restriction is directly discarded. When
the rate of packets is more than the CIR
but not more than the PIR, the packets
that exceed the restriction of the CIR
enter the buffer of the CIR. When the
buffer overflows, the packets are marked
yellow and enter the egress queue, which
enables the packets to be discarded first
in the case of queue congestion.
be more than the port bandwidth.
DMBS(kbyte) - 0 Displays the maximum excess burst size.
Related Tasks


This section describes the parameters for the Ethernet ports on the EoPDH plane.

This section describes the parameters for Ethernet external ports.
This section describes the parameters for Ethernet internal ports.
This section describes the parameters for setting the type field of QinQ frames.

This section describes the parameters for Ethernet external ports.
Navigation Path
1. In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
2. Select External Port.
Table B-52 Parameters for the basic attributes

Port - - Displays the name of the external port.
Name - - Displays or specifies the name of the

external port.
Enabled/Disabled Enabled Disabled l If the port gains access to services, set

Disabled this parameter to Enabled. Otherwise,
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.
This parameter is invalid for PORT9.

Working Mode Auto-Negotiation Auto-Negotiation l Different types of Ethernet ports support

10M Half-Duplex different working modes.
10M Full-Duplex l If the opposite port works in auto-
negotiation mode, set this parameter to
100M Half-Duplex Auto-Negotiation.
100M Full-Duplex l If the opposite port works in full-duplex
mode, set this parameter to 10M Full-
Duplex or 100M Full-Duplex,
depending on the rate of the opposite
port.
l If the opposite port works in half-duplex
mode, set this parameter to 10M Half-
Duplex or 100M Half-Duplex,
depending on the rate of the opposite
port, or set this parameter to Auto-
Negotiation.
Max Frame 1518-2000 1522 l Set this parameter to a value greater than
Length the maximum length of all the data
frames to be transmitted.
l The default value is recommended if the
jumbo frame is not considered and the
data frames contain only one layer of
VLAN tags or even no tags. The value of
1526 or greater is recommended if the
data frames contain two layers of tags,
such as QinQ.
Port Physical - - Displays the actual working status of a

Parameters PORT.
MAC Loopback Non-Loopback Non-Loopback l A MAC loopback is to loop back the

Loopback Ethernet frames transmitted to the
opposite port.
l Use the default value unless otherwise
specified.
PHY Loopback Non-Loopback Non-Loopback l A PHY loopback is to loop back the

Loopback Ethernet physical signals transmitted to
the opposite port.
l Use the default value unless otherwise
specified.

Table B-53 Parameters for flow control

Non- Disabled Disabled l This parameter is valid only when

Autonegotiation Enable Symmetric Working Mode is not set to Auto-
Flow Control Flow Control Mode Negotiation.
Mode l If this parameter is set to Enable
Send Only
Symmetric Flow Control Mode, the
Receive Only port can send PAUSE frames and
process the received PAUSE frames.
l If this parameter is set to Send Only, the
port can send PAUSE frames in the case
of congestion but cannot process the
l If this parameter is set to Receive Only,
the port can process the received PAUSE
frames but cannot send PAUSE frames
in the case of congestion.
l Set this parameter to the same as the non-
autonegotiation flow control mode of the
opposite port.
Autonegotiation Disabled Disabled l This parameter is valid only when

Flow Control Enable Working Mode is Auto-Negotiation.
Mode Dissymmetric Flow l If this parameter is set to Enable
Control Symmetric Control, the port can send
Enable Symmetric PAUSE frames and process the received
Control PAUSE frames.
Enable Symmetric/ l If this parameter is set to Enable
Dissymmetric Flow Dissymmetric Flow Control, the port
Control can send PAUSE frames in the case of
congestion but cannot process the
l If this parameter is set to Enable
Symmetric/Dissymmetric Flow
Control, the port can function as
follows:
– Sends and processes PAUSE frames.
– Sends but does not process PAUSE
frames.
– Processes but does not send PAUSE
frames.
autonegotiation flow control mode of the
opposite port.

Table B-54 Parameters for the tag attributes

TAG Tag Aware Tag Aware l With different tag attributes, the port
Access processes frames in different modes. For
details, see Table B-57.
Hybrid
l Set this parameter to Tag Aware if the
port processes the frames with VLAN
tags (or tagged frames).
l Set this parameter to Access if the port
processes the frames without VLAN tags
(or untagged frames).
l Set this parameter to Hybrid if the port
processes the tagged frames and
untagged frames.
Default VLAN ID 1-4095 1 l This parameter is valid only when

TAG is set to Access or Hybrid.
l For the usage of this parameter, see
Table B-57.
VLAN Priority 0-7 0 l This parameter is valid only when

Table B-57.
l When the VLAN priority is required for
traffic classification or other purposes,
set this parameter as required. Use the
default value unless otherwise specified.
Entry Detection Enabled Enabled l Indicates whether to check the incoming

Disabled packets according to the tag attribute.
Table B-55 Parameters for the network attributes


Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Aware or S-
Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter takes
the default value.
Table B-56 Parameters for the advanced attributes

Enabling Disabled Disabled This parameter specifies whether to restrict

Broadcast Packet Enabled the traffic of broadcast packets according to
Suppression the proportion of the broadcast packets to
the total packets. Set this parameter to
Enabled when a broadcast storm may occur
at the opposite port.
Broadcast Packet 10%-100% 30% When the proportion of the received

Suppression broadcast packets to the total packets
Threshold crosses the threshold, the port discards the
received broadcast packets. Set this
parameter to a value greater than the
proportion when no broadcast storm occurs.
The value of 30% or greater is
recommended.
Traffic Threshold 0-100 (PORT1- 100 (PORT1- Specifies the traffic threshold of the port.
(Mbps) PORT8) PORT8) You can specify the traffic monitoring
0-1000 (PORT9) 1000 (PORT9) period by setting Port Traffic Threshold
Time Window(Min).

Port Traffic 0-30 0 Specifies the traffic monitoring period.

Threshold Time l If Port Traffic Threshold Time
Window(Min) Window(Min) is set to 0, an associated
alarm is reported at the moment when the
traffic received at the port crosses the
value of Traffic Threshold(Mbps).
l If the Port Traffic Threshold Time
Window(Min) is set to a value other
than 0, an associated alarm is reported
only when the traffic received at the port
always crosses the value of Traffic
Threshold(Mbps) in the monitoring
period.
Table B-57 Methods used by ports to process data frames

Direction Type of Data Processing Method
Frame
Tag aware Access Hybrid
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.
Untagged frame Discards the frame. The port receives the The port receives the
frame after adding to frame after adding to
the frame the VLAN the frame the VLAN
tag that contains tag that contains
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the frame. The port strips the l If the VLAN ID
VLAN tag from the in the frame is
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.

Related Tasks

This section describes the parameters for Ethernet internal ports.
Navigation Path
1. In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
2. Select Internal Port.
Table B-58 Parameters for the tag attributes
Port - - Displays the name of the internal port.
TAG Tag Aware Tag Aware l With different tag attributes, the port
Access processes frames in different modes. For
details, see Table B-63.
Hybrid
l Set this parameter to Tag Aware if the
port processes the frames with VLAN
tags (or tagged frames).
l Set this parameter to Access if the port
processes the frames without VLAN tags
(or untagged frames).
l Set this parameter to Hybrid if the port
processes the tagged frames and
untagged frames.
Default VLAN ID 1-4095 1 l This parameter is valid only when

Table B-63.
VLAN Priority 0-7 0 l This parameter is valid only when

l For the usage of this parameter, refer to
Table B-63.
l When the VLAN priority is required for
traffic classification or other purposes,
set this parameter as required. The
default value is recommended unless
otherwise specified.

Entry Detection Enabled Enabled l Indicates whether to check the incoming

Disabled packets according to the tag attribute.
Table B-59 Parameters for encapsulation or mapping

Mapping Protocol GFP GFP The default value is recommended.

The EFP8 board supports GFP only.
Scramble Scrambling Mode Scrambling Mode l Indicates the scrambling polynomial

[X43+1] [X43+1] used by the mapping protocol.
Unscrambled l The default value is recommended.
Set Inverse Value - - This parameter is invalid for the EFP8

for CRC board.
Check Field FCS32 FCS32 l When the Ethernet board uses the GFP
Length No mapping protocol, set this parameter to
FCS32 or No.
l When you set this parameter to FCS32,
a 32-bit FCS is used.
FCS Calculated Big endian Big endian l When you set this parameter to Big
Little endian endian, the least significant byte of the
FCS is placed first and the most
significant byte is placed last.
l When you set this parameter to Little
endian, the most significant byte of the
FCS is placed first and the least
significant byte is placed last.
Extension Header No No Indicates whether the GFP payload header

Option contains the extension header and eHEC.
Table B-60 Parameters for the network attributes


Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Aware or S-
Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter takes
the default value.
Table B-61 Parameters for the LCAS

Enabling LCAS Disabled Disabled l Indicates whether to enable the LCAS

Enabled function.
l The LCAS can dynamically adjust the
number of virtual containers for
mapping required services to meet the
bandwidth needs of the applications. As
a result, the bandwidth utilization is
improved.
LCAS Mode Huawei Mode Huawei Mode l Indicates the sequence in which the
Standard Mode LCAS sink sends the MST control
packet and Rs-Ack control packet.
l When you set this parameter to Huawei
Mode, the LCAS sink first sends the Rs-
Ack and then sends the MST.
l When you set this parameter to
Standard Mode, the LCAS sink first
sends the MST and then sends the Rs-
Ack.
l If the equipment at the opposite end is
the third-party equipment and does not
support the Huawei mode, set this
parameter to Standard Mode.
Otherwise, set this parameter to Huawei
Mode.

Hold Off Time(ms) An integer ranging 2000 l When a member link is faulty, the LCAS
from 0, 2000 to performs switching after a delay of time
10000, in the to prevent the situation where an NE
increments of 100 simultaneously performs a protection
switching such as SNCP and performs an
LCAS switching. This parameter
specifies the duration of the delay.
WTR(s) 0-720 300 l When the time after a member link is

restored to normal reaches the specified
value of this parameter, the VCG uses
the restored member link.
TSD Disabled Disabled l Indicates whether the TSD is used as a

Enabled 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.
Minimum Number 2-256 16 l Specifies the minimum number of

of Members in the members in the transmit direction. After
Transmit Direction the LCAS is enabled, the LCAS_PLCT
alarm is reported when the number of
effective members in the transmit
direction becomes lower than the
minimum number specified by this
parameter.
Minimum Number 2-256 16 l Specifies the minimum number of

of Members in the members in the receive direction. After
Receive Direction the LCAS is enabled, the LCAS_PLCT
alarm is reported when the number of
effective members in the receive
direction becomes lower than the
minimum number specified by this
parameter.



VCTRUNK16



VC4-1.

Timeslots

cannot exceed 63.

Paths

VC path.
Table B-63 Methods used by ports to process data frames

Frame
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.


Frame
Untagged frame Discards the frame. The port receives the The port receives the
frame after adding to frame after adding to
the frame the VLAN the frame the VLAN
tag that contains tag that contains
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the frame. The port strips the l If the VLAN ID
VLAN tag from the in the frame is
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.
Related Tasks

This section describes the parameters for setting the type field of QinQ frames.
Navigation Path
Advance Attribute > QinQ Type Area Settings from the Function Tree.

Board - - Displays the Ethernet board on which the

type field of QinQ frames needs to be set.
If the Ethernet board is the EFP8 board, this
parameters always takes the value of EFP8.
QinQ Type Area 81 00 8100 Specifies the type field of QinQ frames. Set
(Hexadecimal) 88 A8 this parameter according to the type field of
the accessed QinQ frames.
91 00
0600 to FFFF
Related Tasks
B.11 Parameters for the Orderwire and Auxiliary Interfaces

This topic describes the parameters that are related to the orderwire and auxiliary interfaces.

This topic describes the parameters that are used for general orderwire features.
This topic describes the parameters that are used for advanced orderwire features.
This topic describes the parameters that are used for F1 data ports.
This topic describes the parameters that are used for broadcast data ports.
This topic describes the parameters that are used for environment monitoring interfaces.

This topic describes the parameters that are used for general orderwire features.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Orderwire from the Function Tree.
2. Click the General tab.

Parameters
Call Waiting Time 1 to 9 9 l This parameter indicates the waiting

(s) time after the local station dials the
number. If the calling station does not
receive the response message from the
called station within the call waiting
time, it automatically removes the
communication connection.
l If less than 30 nodes exist in the
orderwire subnet, it is recommended that
you set this parameter to five seconds. If
more than 30 nodes exist in the orderwire
subnet, it is recommended that you set
this parameter to nine seconds.
l The call waiting time should be set to the
same for all the NEs.
Dialling Mode Pulse Dual-Tone This parameter indicates the dialling mode
Dual-Tone Frequency of the orderwire phone.
Frequency
Conference Call - 888 l This parameter indicates the telephone

number of the network-wide orderwire
conference call.
l When an OptiX RTN 950 dials the
telephone number 888, the orderwire
phones of all the NEs on the orderwire
subnet ring. When an OptiX RTN 950
receives the call, the orderwire phones
on the other NEs do not ring. In this case,
the orderwire point-to-multipoint group
call changes to a point-to-point call
between two NEs.
l The telephone number of the orderwire
conference call should be the same for
all the nodes on the same subnet.
l The telephone number of the orderwire
conference call must have the same
length as the telephone number of the
orderwire phone (phone 1) at the local
site.

Phone 1 100 to 99999999 101 l This parameter specifies the orderwire

phone number of the local station. An
addressing call refers to a point-to-point
call.
l The length of the orderwire phone
number of each NE should be the same.
It is recommended that you set the phone
number to a three-digit number.
l The orderwire phone number of each NE
should be unique. It is recommended that
the phone numbers are allocated from
101 for the NEs in a sequential order
according to the NE IDs.
l The orderwire phone number cannot be
set to the group call number 888 and
cannot start with 888.
Available - - This parameter indicates the available port

Orderwire Port for the orderwire phone.
Selected - - This parameter indicates the selected port

Orderwire Port for the orderwire phone.
Related Tasks

This topic describes the parameters that are used for advanced orderwire features.
Navigation Path
2. Click the Advanced tab.

Parameters for Bytes Occupied by Orderwire Phones

Orderwire E1 E1 l This parameter specifies the overhead

Occupied Bytes E2 byte that is used to transmit the orderwire
signals.
l Regardless the parameter value, the
radio link always uses a customized
overhead byte to transmit the orderwire
signals. Hence, this parameter should be
set according to the occupied SDH
overhead bytes in the ordinary SDH.
Related Tasks

This topic describes the parameters that are used for F1 data ports.
Navigation Path
2. Click the F1 Data Port tab.
Parameters
Available Data - - l This parameter indicates the available F1

Path data channel.
l Two data channels should be selected for
the configuration.
Number - - This parameter indicates the number of the

F1 data port.
Data Channel 1 - - l If an SDH optical or electrical line port

is selected, this parameter corresponds to
the F1 byte in the SDH frame at the line
port.
l If an IF port is selected, this parameter
corresponds to the customized F1 byte in
the microwave frame at the IF port.
l If F1 is selected, this parameter
corresponds to the F1/S1 interface on the
AUX board. The F1/S1 interface

Data Channel 2 complies with ITU-T G.703 and

operates at the rate of 64 kbit/s.
Related Tasks

This topic describes the parameters that are used for broadcast data ports.
Navigation Path
2. Click the Broadcast Data Port tab.
Parameters for Broadcast Data Ports

Overhead Byte SERIAL1 to SERIAL1 l In the case of an SDH optical/electrical

SERIAL4 line, the preset overhead byte is used to
transmit the asynchronous data services.
l In the case of a radio link, a customized
serial overhead byte in the microwave
frame is used to transmit the
asynchronous data services.
Broadcast Data - No Data l When this parameter is set to the

Source SERIAL1, the F1/S1 interface on the
corresponding AUX board is used.
l When this parameter is set to the SDH
optical/electrical line port, the value of
Overhead Byte of this port is used.
l When this parameter is set to the IF port,
the customized Serial byte in the
microwave frame of this port is used.

Available - - This parameter indicates the available

Broadcast Data broadcast data sink.
Sink
Selected Broadcast - - l When this parameter is set to the

Data Sink SERIAL1, the F1/S1 interface on the
corresponding AUX board is used.
l When this parameter is set to the SDH
optical/electrical line port, the value of
Overhead Byte of this port is used.
l When this parameter is set to the IF port,
the customized Serial byte in the
microwave frame of this port is used.
Related Tasks

This topic describes the parameters that are used for environment monitoring interfaces.
Navigation Path
Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the Function
Tree.
Parameters for the Basic Attributes

Operation Object - - This parameter indicates the operation

object.
Relay Control Auto Control Auto Control l Auto Control: If an alarm is reported, the
Mode Manual Control alarming relay is started up
automatically. Otherwise, the alarming
relay is shut down.
l Manual Control: Relay Status in Major
Alarm(K0) and Relay Status in
Critical Alarm(K1) need to be set.

Relay Status in Disabled Disabled l This parameter indicates that the status
Major Alarm(K0) Enabled of the relay is set manually for major
alarms.
l Enable: The relay is set to the "0N" status
for major alarms.
l Disabled: The relay is set to the "OFF"
status for major alarms.
l This parameter is valid only when Relay
Control Mode is set to Manual
Control.
Relay Status in Disabled Disabled l This parameter indicates that the status
Critical Alarm(K1) Enabled of the relay is set manually for critical
alarms.
l Enable: The relay is set to the enabled
status for critical alarms.
l Disabled: The relay is set to the disabled
status for critical alarms.
l This parameter is valid only when Relay
Control Mode is set to Manual
Control.
Parameters for the Input Relay


object.
Path Name - - This parameter indicates or specifies the

name of the channel.
Using Status Unused Unused This parameter specifies whether the alarm
Used interface of the input relay is used.
Alarm Mode Relay Turns Off/ Relay Turns Off/ l If this parameter is set to Relay Turns
High Level High Level Off/High Level, an alarm is generated
Relay Turns On/ when the relay is turned off.
Low Level l If this parameter is set to Relay Turns
On/Low Level, an alarm is generated
when the relay is turned on.
l This parameter is valid only when Using
Status is set to Used.

Alarm Severity Critical Alarm Critical Alarm This parameter specifies the severity of the
Major Alarm alarm that is generated at the input relay.
Minor Alarm
Warning Alarm
Parameters for the Output Relay


object.
Path Name - - This parameter indicates or specifies the

name of the output channel.
Use or Not Unused Unused This parameter specifies whether the alarm
Used interface of the output relay is used.
Parameters for the Temperature Attributes


object.
Monitor Status - - This parameter indicates whether the

temperature attribute is monitored.
Temperature - - This parameter indicates the upper

Upper Threshold temperature threshold of the board. When
(Deg.C) the actual temperature is higher than the
preset value, an alarm is generated.
Temperature - - This parameter indicates the lower

Lower Threshold temperature threshold of the board. When
(Deg.C) the actual temperature is lower than the
preset value, an alarm is generated.

Parameters for the Alarm Relay

Alarm Severity Critical Alarm Critical Alarm This parameter indicates the severity of the
Major Alarm Major Alarm alarm.
Minor Alarm Minor Alarm
Warning Alarm Warning Alarm
Alarm Output CSK-1 CSK-1 This parameter specifies the channel of the
Channel CSK-2 output alarm relay.
CSK-3
CSK-4
Related Tasks
B.12 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces.

This topic describes the parameters that are related to IF attributes.
This topic describes the parameters that are related to the ATPC attributes.
This topic describes the parameters that are used for configuring the Hybrid/AM function.
B.12.4 Parameter Description: Hybrid_AM Configuration_Advanced Attributes
This section describes the parameters that are used for configuring the advanced attributes.
This topic describes the parameters that are related to ATPC adjustment records.
B.12.6 Parameter Description: PRBS Test
This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS)
test.
B.12.7 Parameter Description: ODU Interface_Radio Frequency Attribute
This topic describes the parameters that are related to radio frequency attributes of an ODU.
This topic describes the parameters that are used for configuring the power attributes of the
ODU.
B.12.9 Parameter Description: ODU Interface_Equipment Information
This topic describes the parameters that are used for configuring the equipment information of
the ODU.
B.12.10 Parameter Description: ODU Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes of the
ODU.
This topic describes the parameters that are related to the SDH interfaces.
B.12.12 Parameter Description: Automatic Laser Shutdown
This topic describes the parameters that are related to the automatic laser shutdown (ALS)
function.
This topic describes the parameters that are related to the PDH interfaces.
B.12.14 Parameter Description: Microwave Interface_Basic Attributes
This topic describes the parameters that are related to the basic attributes of microwave
interfaces.
B.12.15 Parameter Description: Microwave Interface_Layer 2 Attributes
This topic describes the parameters that are related to the Layer 2 attributes of microwave
interfaces.
B.12.16 Parameter Description: Microwave Interface_Advanced Attributes
This topic describes the parameters that are related to the advanced attributes of microwave
interfaces.

This topic describes the parameters that are related to IF attributes.
Navigation Path
l Click the IF Attributes tab.
Parameters

IF interface.
Radio Link ID 1 to 4094 1 l This parameter indicates or specifies the

ID of a radio link. As the identifier of a
radio link, this parameter is used to
prevent incorrect connections of radio
links between sites.
l Each radio link of an NE should have a
unique link ID, and the link IDs at both
ends of a radio link should be the same.

Received Radio - - l This parameter indicates the received ID

Link ID of the radio link.
ID does not match the preset value of
Radio Link ID at the local end, the local
end inserts the AIS signal to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the link
IDs do not match.
IF Port Loopback Non-Loopback Non-Loopback l This parameter indicates or specifies the

Inloop loopback status of the IF interface.
Outloop l Non-Loopback indicates that the
loopback is cancelled or not performed.
l Inloop indicates that the IF signals
transmitted to the opposite end are
looped back.
l Outloop indicates that the received SDH
signals are looped back.
l Generally, this parameter is used to
locate the faults that occur at each IF
interface. The IF loopback is used for
diagnosis. If this function is enabled, the
services at the related ports are affected.
In normal cases, this parameter is set to
Non-Loopback.
2M Wayside Disabled Disabled l This parameter indicates or specifies

Enable Statusa Enabled whether the radio link transmits the
wayside E1 service.
l The wayside E1 service can be supported
by the IF1 board in the
7,STM-1,28MHz,128QAM,
8,E3,28MHz,QPSK, or 9,E3,14MHz,
16QAM mode.
2M Wayside Input - - l This parameter indicates or specifies the

Boarda slot in which the 2M wayside service is
accessed.
l This parameter can be set only when 2M
Wayside Enable Status is set to
Enabled.
l The wayside E1 service can be supported
by the IF1 board in the
7,STM-1,28MHz,128QAM,
8,E3,28MHz,QPSK, or 9,E3,14MHz,
16QAM mode.

350 MHz Stop Stop l This parameter indicates or specifies the

Consecutive Wave Start status of transmitting the 350 MHz
Status carrier signals at the IF interface.
l This parameter can be set to Start in the
commissioning process only. In normal
cases, this parameter is set to Stop.
Otherwise, the services are interrupted.
XPIC Enabledb Enabled Enabled l This parameter indicates or specifies

Disabled whether the XPIC function of the IFX2
board is enabled.
l If the IFX2 board does not perform the
XPIC function, this parameter should be
set to Disabled. In this case, the XPIC
cable is required to perform self-loop for
the XPIC port on the IFX2 board.
Enable IEEE-1588 Enabled Disabled If the OptiX RTN 950 is interconnected with
Timeslotc Disabled the packet radio equipment, this parameter
should be set to Enabled. Otherwise, this
parameter should be set to Disabled.
NOTE
l a. The IFU2 and IFX2 boards do not support the 2M wayside service.
l b. The IFU2 and IF1 boards do not support the XPIC function.
l c. The IF1 board does not support the IEEE-1588 timeslot function.
Related Tasks

This topic describes the parameters that are related to the ATPC attributes.
Navigation Path
l Click the ATPC Attributes tab.
Parameters

IF interface.

ATPC Enable Disabled Disabled l This parameter specifies whether the

Status Enabled ATPC function is enabled.
l When this parameter is set to Enabled
and if the RSL at the receive end is 2 dB
higher or lower than the central value
between the ATPC upper threshold and
the ATPC lower threshold at the receive
end, the receiver notifies the transmitter
to decrease or increase the transmit
power until the RSL is within the range
that is 2 dB higher or lower than the
central value between the ATPC upper
threshold and the ATPC lower threshold.
attributes.
ATPC Upper -75.0 to -20.0 -45.0 l Set the central value between the ATPC
threshold to a value for the expected
ATPC Lower -35.0 to -90.0 -70.0 receive power.
Threshold(dBm)
Lower Threshold(dBm) to the
and the ATPC lower threshold and 10
dB.
l You can set the ATPC upper threshold
only when ATPC Automatic
Threshold(dBm) is set to Disabled.

ATPC Automatic Enabled Disabled l This parameter specifies whether the

Threshold Enable Disabled ATPC automatic threshold function is
Status enabled.
l If this parameter is set to Enabled, the
link.
l If this parameter is set to Disabled, you
need to manually set ATPC Upper
Threshold(dBm) and ATPC Lower
Threshold(dBm).
ATPC Upper - - l This parameter indicates that the

Automatic equipment automatically uses the preset
Threshold(dBm) ATPC upper and lower thresholds.
l This parameter is valid only when ATPC
ATPC Lower - -
Automatic Threshold Enable Status is
Automatic
set to Enabled.
Threshold(dBm)
Related Tasks

This topic describes the parameters that are used for configuring the Hybrid/AM function.
Navigation Path
l In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose
l Click the Hybrid/AM Configuration tab.
Parameters

IF port.
IF Channel 7M - IF Channel Bandwidth indicates the

Bandwidth 14M channel spacing of the corresponding radio
link. This parameter is set according to the
28M planning information.
56M

AM Enable Status Disable Disable l When this parameter is set to Disable, the
Enable radio link uses only the specified
Modulation Mode.
l When this parameter is set to Enable, the
radio link uses the corresponding
channel conditions.
Hence, the Hybrid radio can ensure the
reliable transmission of the E1 services and
provide bandwidth adaptively for the
Ethernet services when the AM function is
enabled.
Modulation Mode QPSK QPSK This parameter specifies the lowest-gain

of the Guarantee 16QAM modulation scheme that the AM function
AM Capacity supports. This parameter is set according to
128QAM service transmission bandwidth that the
Hybrid radio must ensure and the
256QAM availability of the radio link that corresponds
to this modulation scheme.
Enable Status is set to Enable.

of the Full AM 16QAM modulation scheme that the AM function
Capacity supports. This parameter is set according to
256QAM availability of the radio link that corresponds
to this modulation scheme.
NOTE
Manually QPSK QPSK This parameter specifies the modulation

Specified 16QAM scheme that the radio link uses for signal
Modulation Mode transmission.
32QAM
64QAM Enable Status is set to Disable.
128QAM
256QAM

Enable E1 Priority Disable Disable l This parameter specifies whether to

Enable enable the E1 priority function.
l This parameter is valid only when AM
Guarantee E1 - - l When AM Enable Status is set to

Capacity Enable, this parameter depends on IF
Channel Bandwidth and Modulation
Mode of the Guarantee AM Capacity
and is not configurable.
l When AM Enable Status is set to
Disable, this parameter depends on IF
Channel Bandwidth and Manually
Specified Modulation Mode and is not
configurable.
Full E1 Capacity - - l This parameter specifies the number of

transmitted E1 services in Modulation
Mode of the Full AM Capacity.
l This parameter is valid if Enable E1
Priority is set to Enable.
l If the E1 priority function is enabled, the
maximum number of allowed E1
services in the current mode = Min
([Bandwidth of the air interface in the
current mode - (Bandwidth for the
assured capacity - Assured E1 capacity x
2M)]/2M, E1NUM in the highest-gain
modulation mode).
l The Full E1 Capacity must be set to the
Transmit-End - - Displays the modulation mode at the

Modulation Mode transmit mode.
Receive-End - - Displays the modulation mode at the receive

Modulation Mode mode.
Guarantee AM - - Displays the guarantee AM service capacity.

Service Capacity
(Mbit/s)
Full AM Service - - Displays the full AM service capacity.

Capacity(Mbit/s)
Transmitted AM - - Displays the transmitted AM service

Service Capacity capacity.
(Mbit/s)

Received AM - - Displays the received AM service capacity.

Service Capacity
(Mbit/s)
Related Tasks
B.12.4 Parameter Description: Hybrid_AM

Configuration_Advanced Attributes
This section describes the parameters that are used for configuring the advanced attributes.
Navigation Path
l In the NE Explorer, select the Hybrid IF board, and then choose Configuration > Hybrid/
AM Configuration from the Function Tree.
l Click the Advanced Attributes tab.
Parameters
Modulation Mode - - Displays the modulation schemes.
E1 Capacity - - l You can specify the number of E1s that

can be transmitted in intermediate
modulation scheme, by setting the
advanced attributes correspondingly.
l Generally, it is recommended that this
parameter takes the default value. To
ensure that a specific number of E1s can
be transmitted in intermediate
modulation scheme, adjust the E1
capacity in each modulation scheme
according to the network planning
information.
l If the E1 priority function is enabled, the
maximum number of allowed E1
services in the current mode = Min
{[Bandwidth of the air interface in the
current mode - (Bandwidth for the
assured capacity - Assured E1 number x
2Mbps)]/2Mbps, E1 number in the
highest-gain modulation mode}.

Data Service - - Displays the data service bandwidth.

Bandwidth(Mbit/
s)
Related Tasks

This topic describes the parameters that are related to ATPC adjustment records.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ATPC Adjustment Records from the Function Tree.
Parameters
Port - - This parameter indicates the port for the

ATPC adjustment.
Event NO. - - This parameter indicates the number of the

ATPC adjustment event.
Adjustment Time - - This parameter indicates the time of the

ATPC adjustment.
Adjustment - - This parameter indicates the direction of the

Direction adjustment at the port.
Switchover - - This parameter indicates the switching

operation at the port.
Transmitted - - This parameter indicates the transmitted

Power(dBm) power of the port to be switched.
Received Power - - This parameter indicates the received power

(dBm) of the port to be switched.
Related Tasks
B.12.6 Parameter Description: PRBS Test

This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS)
test.

Navigation Path
Configuration > PRBS Test from the Function Tree.
Parameters
Port - - This parameter indicates the port for the

PRBS test.
Direction Cross Cross l This parameter indicates or specifies the

Tributary direction of the PRBS test.
l In the tributary direction, the PRBS test
is performed to check the connectivity of
the cable from the tributary board to the
DDF.
l In the cross-connect direction, the PRBS
test is performed to check the processing
of the service from the tributary board to
the NE at the remote end.
Duration 1 to 255 1 This parameter indicates or specifies the

duration of the PRBS test.
Measured Time s s This parameter indicates or specifies the

10min time unit used for the PRBS test.
h
Start Time - - This parameter indicates the start time of the

PRBS test.
Progress - - This parameter indicates the progress

percentage of the PRBS test.
Total PRBS - - This parameter indicates the number of bit

errors that occur in the PRBS test.
Accumulating Selected Deselected This parameter specifies whether to display

Mode Deselected the values in accumulative mode. If
Accumulating Mode is selected, it
indicates that the values are displayed in
accumulative mode.
B.12.7 Parameter Description: ODU Interface_Radio Frequency

Attribute
This topic describes the parameters that are related to radio frequency attributes of an ODU.

Navigation Path
l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
l Click the Radio Frequency Attributes tab.
Parameters
Board - - This parameter indicates the corresponding

ODU.
Transmit - - l This parameter indicates or specifies the

Frequency(MHz) transmit frequency of the ODU, namely,
the central frequency of the channel.
less than the sum of the minimum
transmit frequency supported by the
ODU and a half of the channel spacing,
and must not be more than the difference
between the maximum transmit
frequency supported by the ODU and a
half of the channel spacing.
frequencies at both ends of a radio link
should be one T/R spacing.

T/R Spacing(MHz) - - l This parameter indicates or specifies the

spacing between the transmit frequency
and receive frequency of the ODU to
prevent mutual interference of the
transmitter and receiver.
l If the ODU is a Tx high station, the
transmit frequency is one T/R spacing
higher than the receive frequency. If the
ODU is a Tx low station, the transmit
frequency is one T/R spacing lower than
the receive frequency.
spacing, this parameter is set to 0,
indicating that the T/R spacing supported
by the ODU is used.
radio link.
Actual Transmit - - This parameter indicates the actual transmit

Actual Receive - - This parameter indicates the actual receive

Actual T/R - - This parameter indicates the actual T/R

Spacing(MHz) spacing of the ODU.
The Range of - - This parameter indicates the working range

frequency Point of the frequency of the ODU.
(MHz)
Related Tasks

This topic describes the parameters that are used for configuring the power attributes of the
ODU.
Navigation Path

l Click the Power Attributes tab.
Parameters

ODU.

modulation module.
exceed this value.
Transmit Power - - l This parameter specifies the transmit

(dBm) power of the ODU. This parameter
cannot be set to a value that exceeds the
nominal power rang of the ODU or a
value that exceeds Maximum Transmit
Power(dBm).
be set to the same value at both ends of a
radio link.

Power to Be -90.0 to -20.0 -10.0 l This parameter is used to set the expected
Received(dBm) receive power of the ODU and is mainly
used in the antenna alignment stage.
After this parameter is set, the NE
exceeds the range of receive power ±3
TX High - - l If the value of the actual transmit power

Threshold(dBm) of the ODU is greater than the preset
value of TX High Threshold(dBm), the
system separately records the duration
when the value of the actual transmit
power of the ODU is greater than the
preset value of TX High Threshold
(dBm) and the duration when the value
of the actual transmit power of the ODU
is greater than the preset value of TX
Low Threshold(dBm) in the
performance events.
l If the value of the actual transmit power
of the ODU is greater than the preset
value of TX Low Threshold(dBm) and
is lower than the preset value of TX High
Threshold(dBm), the system records
the duration when the value of the actual
transmit power of the ODU is greater
than the preset value of TX Low
Threshold(dBm) in the performance
events.

TX Low Threshold - - l If the value of the actual transmit power

(dBm) of the ODU is lower than the preset value
of TX Low Threshold(dBm), the
system does not record it.
l TX High Threshold(dBm) and TX
Low Threshold(dBm) are valid only
when the ATPC function is enabled.
RX High - - l If the value of the actual receive power

Threshold(dBm) of the ODU is lower than the preset value
of RX Low Threshold(dBm), the
system records the duration when the
value of the actual receive power of the
ODU is lower than the preset value of
RX Low Threshold(dBm) and duration
when the value of the actual transmit
power of the ODU is lower than the
preset value of RX High Threshold
(dBm)in the performance events.
l If the value of the actual receive power
value of RX Low Threshold(dBm) and
is lower than the preset value of RX High
Threshold(dBm), the system records
the duration when the value of the actual
receive power of the ODU is Lower than
the preset value of RX High Threshold
(dBm) in the performance events.
l If the value of the actual receive power

RX Low Threshold - - value of RX High Threshold(dBm), the

(dBm) system does not record it.
Actual Transmit - - l This parameter indicates the actual

Power(dBm) transmit power of the ODU.
l If the ATPC function is enabled, the
queried actual transmit power may be
different from the preset value.
Actual Receive - - This parameter indicates the actual receive

Power(dBm) power of the ODU.
Actual range of - - This parameter indicates the range of the

Power(dBm) actual transmit power of the ODU.

Related Tasks
B.12.9 Parameter Description: ODU Interface_Equipment

Information
This topic describes the parameters that are used for configuring the equipment information of
the ODU.

Navigation Path
Configuration > ODU Interface from the Function Tree.
l Click the Equipment Information tab.
Parameters

ODU.
Frequency(GHz) - - This parameter indicates the frequency band

where the ODU operates.
Equipment Type - - l This parameter indicates the equipment

type of the ODU.
l PDH and SDH indicate the transmission
capacity only and are irrelevant to the
type of transmitted service.
T/R Spacing(MHz) - - This parameter indicates the T/R spacing of

the ODU.
Intermediate - - This parameter indicates the IF frequency

Frequency bandwidth of the ODU.
Bandwidth (MHz)
IF Bandwidth - - Displays the IF bandwidth type.

Type
Station Type - - l This parameter indicates whether the

ODU is a Tx high station or a Tx low
station.
l The transmit frequency of a Tx high
station is one T/R spacing higher than the
transmit frequency of a Tx low station.

Produce Time - - This parameter indicates the manufacturing

time of the ODU.
Produce SN - - This parameter indicates the manufacturing

serial number and the manufacturer code of
the ODU.
Related Tasks

B.12.10 Parameter Description: ODU Interface_Advanced

Attributes
This topic describes the parameters that are used for configuring the advanced attributes of the
ODU.
Navigation Path
l Click the Advanced Attributes tab.
Parameters

ODU.
RF Loopback Non-Loopback Non-Loopback l This parameter indicates or specifies the

Inloop loopback status of the RF interface of the
ODU.
l Non-Loopback indicates that the
loopback is canceled or not performed.
l Inloop indicates that the RF signals
looped back.
l This function is used for fault locating
for the RF interfaces. The RF
Loopback function is used for diagnosis
and may affect the services that are
transmitted over the interfaces. Hence,
exercise precaution before starting this
function.
Non-Loopback.
Configure unmute unmute l This parameter indicates or specifies the

Transmission mute transmit status of the ODU.
Status l If this parameter is set to mute, the
signals.
l If this parameter is set to unmute, the
ODU can normally transmit and receive
microwave signals.
unmute.

Actual - - This parameter indicates the actual transmit

Transmission status of the ODU.
Status
Factory - - This parameter indicates the manufacturer

Information information about the ODU.
Related Tasks

This topic describes the parameters that are related to the SDH interfaces.
Navigation Path
Configuration > SDH Interface from the Function Tree.
l Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Parameters

SDH interface.
Optical Interface - - This parameter indicates or specifies the

Namea name of the optical interface.
Laser Switcha Open Open l This parameter indicates or specifies the

Close on/off state of the laser.
l This parameter is set for SDH optical
interfaces only.
Open.

Optical(Electrical) Non-Loopback Non-Loopback l This parameter indicates or specifies the

Interface Inloop loopback status on the SDH interface.
Loopbacka l Non-Loopback indicates that the
Outloop
l Inloop indicates that the SDH signals
looped back.
for the SDH interfaces. The Optical
(Electrical) Interface Loopback
function is used for diagnosis and may
affect the services that are transmitted
over the interfaces. Hence, exercise
precaution before starting this function.
Non-Loopback.
VC4 Loopbackb Non-Loopback Non-Loopback l This parameter indicates or specifies the

Inloop loopback status in the VC-4 path.
l Inloop indicates that the VC-4 signals
looped back.
l Outloop indicates that the received
VC-4 signals are looped back.
for the VC-4 paths. The VC4
Loopback function is used for diagnosis
and may affect the services that are
transmitted over the interfaces. Hence,
exercise precaution before starting this
function.
Non-Loopback.
NOTE
l a: Indicates the parameters that are supported when Port is selected from the list box.
l b: Indicates the parameters that are supported when VC4 Channel is selected from the list box.
Related Tasks

B.12.12 Parameter Description: Automatic Laser Shutdown

This topic describes the parameters that are related to the automatic laser shutdown (ALS)
function.
Navigation Path
Configuration > Automatic Laser Shutdown from the Function Tree.
Parameters
Optical Interface - - This parameter indicates the corresponding

optical interface.
Automatic Disabled Disabled l This parameter indicates or specifies

Shutdown Enabled whether the Automatic Laser
Shutdown function is enabled or
disabled for the laser.
l The ALS function allows the laser to shut
down automatically when an optical port
does not carry services, an optical fiber
is broken, or no optical signal is received.
l You can set On Period(ms), Off Period
(ms), and Continuously On-test Period
(ms) only when this parameter is set to
Enabled.
On Period(ms) 1000 to 3000 2000 This parameter indicates or specifies the

period when a shutdown laser automatically
starts up and tests whether the optical fiber
is normal.
Off Period(ms) 2000 to 300000 60000 This parameter indicates or specifies the
period when the laser does not work (with
the ALS function being enabled).
Continuously On- 2000 to 300000 90000 This parameter indicates or specifies the
test Period(ms) period when a shutdown laser is manually
started up and tests whether the optical fiber
is normal.

This topic describes the parameters that are related to the PDH interfaces.

Navigation Path
Configuration > PDH Interface from the Function Tree.
l Select By Board/Port(Channel).
l Select Port from the list box.
Parameters

port.
Port Name - - This parameter indicates or specifies the

name of the port.
Tributary Non-Loopback Non-Loopback l This parameter indicates or specifies the

Loopback Inloop loopback status in the associated path of
the tributary unit.
Outloop
l Inloop indicates that the PDH signals
looped back.
l Outloop indicates that the received PDH
for the paths of the tributary unit. The
Tributary Loopback function is used
for diagnosis and may affect the services
that are transmitted over the interfaces.
Hence, exercise precaution before
starting this function.
Non-Loopback.
Port Impedance - - This parameter indicates the impedance of a

path, which depends on the tributary unit.

Service Load Load Load l This parameter indicates or specifies the

Indication Non-Loaded service loading status in a specific path.
l When this parameter is set to Load, the
board detects whether alarms exist in the
path.
Loaded, the board does not detect
whether there are alarms in the path.
l If a path does not carry any services, you
can set this parameter to Non-Loaded
for the path to mask all the alarms. If a
path carries services, you need to set this
parameter to Load for the path.
Retiming Mode Normal Normal l This parameter indicates or specifies the

Retiming Mode of retiming mode of a specific path.
Tributary Clock l By using the retiming function, the
Retiming Mode of retiming reference signal from the SDH
Cross-Connect network and the service data signal are
Clock combined and then sent to the client
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 the
retiming function is used with the
clock of the upstream tributary unit
traced., 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,
should be used to provide reference
clock signals for the equipment.
l If the retiming function is required, it is
recommended that you set this parameter
to Retiming Mode of Cross-connect
Clock.

Port Service Type - - This parameter indicates the type of services

that are processed in a path. It depends on
the services that are transmitted in a path.
Related Tasks
B.12.14 Parameter Description: Microwave Interface_Basic

Attributes
This topic describes the parameters that are related to the basic attributes of microwave
interfaces.
Navigation Path
2. Click the Basic Attributes tab.
Parameters

IF port.
Name - - This parameter indicates or specifies the

customized port name.
Port Mode Layer 2 Layer 2 This parameter indicates the working mode
of the Ethernet name.
Encapsulation Null 802.1Q l This parameter specifies the method of

Type 802.1Q the port to process the received packets.
QinQ l If this parameter is set to Null, the port
transparently transmits the received
packets.
l If this parameter is set to 802.1Q, the port
identifies the packets that comply with
the IEEE 802.1Q standard.
l If this parameter is set to QinQ, the port
identifies the packets that comply with
the IEEE 802.1 QinQ standard.
Related Tasks

B.12.15 Parameter Description: Microwave Interface_Layer 2

Attributes
This topic describes the parameters that are related to the Layer 2 attributes of microwave
interfaces.
Navigation Path
2. Click the Layer 2 Attributes tab.
Parameters for Layer 2 Attributes


IF port.
QinQ Type - - l This parameter specifies the QinQ type

Domain domain.
l This parameter can be set only when
Encapsulation Type in General
Attributes is set to QinQ.
Tag Tag Aware Tag Aware l This parameter specifies the TAG flag of
Access a port. For details about the TAG flags
and associated frame-processing
Hybrid methods, see Table B-65.
that contain the VLAN tag (tagged
frames), set this parameter to "Tag
Aware".
that do not contain the VLAN tag
(untagged frames), set this parameter to
"Access".
l If the accessed services contain tagged
frames and untagged frames, set this
parameter to "Hybrid".
Default VLAN ID 1 to 4094 1 l This parameter is valid only when

l For details about the functions of this
parameter, see Table B-65.
to the actual situations.

VLAN Priority 0 0 l This parameter is valid only when

1 TAG is set to Access or Hybrid.
l For details about the functions of this
2
parameter, see Table B-65.
3
l When the VLAN priority is required to
4 divide streams or to be used for other
5 purposes, this parameter needs to be set
according to the planning information. In
6 normal cases, it is recommended that you
7 use the default value.
Table B-65 Data frame processing

Status Type of Data Processing Method
Frame
Ingress Port Tagged frame The port receives the The port discards The port receives
frame. the frame. the frame.
Untagged frame The port discards the The port receives The port receives
frame. the frame after the the frame after the
VLAN tag that VLAN tag that
corresponds to corresponds to
"Default VLAN ID" "Default VLAN ID"
and "VLAN and "VLAN
Priority" is added to Priority" is added to
the frame. the frame.
Egress Port 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.

Related Tasks
B.12.16 Parameter Description: Microwave Interface_Advanced

Attributes
This topic describes the parameters that are related to the advanced attributes of microwave
interfaces.
Navigation Path
Parameters for Advanced Attributes


IF port.
Radio Link ID 1 to 4094 1 l This parameter specifies the ID of the

radio link. As the identifier of a radio
link, this parameter is used to prevent
incorrect connections of radio links
between sites.
l The ID of each radio link of an NE must
be unique, and the link IDs at both ends
of a radio link must be the same.
Received Radio - - l This parameter indicates the received ID

Link ID of the radio link.
ID does not match with the preset value
of Radio Link ID at the local end, the
local end inserts the AIS signal to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the link
IDs do not match.

IF Port Loopback Non-Loopback Non-Loopback l This parameter indicates or specifies the

Inloop loopback status of the IF interface.
l Inloop indicates that the IF signals
looped back.
l Generally, this parameter is used to
locate the faults that occur at each IF
interface. The IF loopback is used for
diagnosis. If this function is enabled, the
services at the related ports are affected.
In normal cases, this parameter is set to
Non-Loopback.
Composite Port Non-Loopback Non-Loopback l This parameter indicates or specifies the

Loopback Inloop loopback status on the composite
interface.
Outloop
l Inloop indicates that the composite
signals transmitted to the opposite end
are looped back.
l Outloop indicates that the received
composite signals are looped back.
Non-Loopback.
Error Frame Enabled Enabled l This parameter indicates or specifies

Discard Enabled Disabled whether to discard the Ethernet frame
when a CRC error occurs in an Ethernet
frame.
l If the Ethernet service transmitted on the
IF_ETH port is a voice service or a video
service, you can set this parameter to
Disabled.
l The IF1 board does not support this
parameter.
MAC Address - - l This parameter indicates the MAC

address of the port.
parameter.

Transmitting Rate - - l This parameter indicates the transmit

(Kbit/s) rate of the local port.
parameter.
Receiving Rate - - l This parameter indicates the receive rate

(Kbit/s) of the local port.
parameter.
MAC Loopback Non-Loopback Non-Loopback l This parameter specifies the loopback

Inloop state at the MAC layer. When this
parameter is set to Inloop, the Ethernet
signals transmitted to the opposite end
are looped back.
you use the default value.
parameter.
PHY Loopback Non-Loopback Non-Loopback The IF port on the OptiX RTN 950 does not
support the setting of this parameter.
Related Tasks
B.13 Parameters for Overhead

This topic describes the parameters that are related to overhead.

This topic describes the parameters that are related to the regenerator section overheads
(RSOHs).
This topic describes the parameters that are related to the VC-4 path overheads (POHs).

This topic describes the parameters that are related to the regenerator section overheads
(RSOHs).

Navigation Path
1. Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
2. Choose Display in Text Format or Display in Hexadecimal.
Parameters for Setting the Display Format

Display in Text Selected Selected This parameter specifies the display in the
Format Deselected text format.
Display in Selected Deselected This parameter specifies the display in the

Hexadecimal Deselected hexadecimal format.

Object - - This parameter indicates the object to be set.
J0 to be Sent - [16 Bytes]HuaWei If the NE at the opposite end reports the

([Mode]Content) SBS J0_MM alarm, this parameter is set
according to the J0 byte to be received at the
opposite end.
J0 to be Received - [Disabled] l This parameter specifies the J0 byte to be

([Mode]Content) received.
l If this parameter is set to [Disabled], the
board does not monitor the received J0
byte.
default value.
J0 Received - - This parameter indicates the J0 byte that is

([Mode]Content) actually received.
Related Tasks


Navigation Path
1. Select SDH interface board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > VC4 Path Overhead from the Function Tree.


Parameters for the Trace Byte J1


([Mode]Content) SBS LP_TIM or LP_TIM_VC3 alarm, this
parameter is set according to the J1 byte to
be received at the opposite end.
J1 to be Received - [Disabled] l If this parameter is set to [Disabled], the

([Mode]Content) board does not monitor the received J1
byte.
default value.
J1 Received - - This parameter displays the J1 byte that is

([Mode]Content) actually received.
Parameters for the Signal Flag C2

C2 to be Sent - (0x00)Unequipped If the NE at the opposite end reports the

HP_SLM alarm, this parameter is set
according to the C2 byte to be received at the
opposite end.

C2 to be Received - (0x00)Unequipped If the NE at the local end reports the

HP_SLM alarm, this parameter is set
according to the C2 byte to be sent at the
opposite end.
C2 Received - - This parameter displays the C2 byte that is

actually received.
Parameters for Overhead Termination

VC4 Overhead Termination Auto l If this parameter is set to Pass-

Termination Pass-Through Through, the NE forwards the original
overhead after monitoring the VC-4 path
Auto overhead regardless of the C2 byte.
l If this parameter is set to Termination,
the NE generates the new VC-4 path
overhead according to the board setting
after monitoring the VC-4 path overhead
regardless of the C2 byte.
l If this parameter is set to Auto, the VC-4
path overhead in the VC-4 pass-through
service is passed through, and the VC-4
path overhead in the VC-12 service is
terminated.
default value.
Related Tasks

Navigation Path
Configuration > Overhead Management > VC12 Path Overhead from the Function
Tree.



Parameters for the Trace Byte


SBS HP_TIM alarm, this parameter is set
according to the J2 byte to be received by
the NE at the opposite end.
J2 to be Received - [Disabled] l If this parameter is set to [Disabled], the

board does not monitor the received J2
byte.
default value.
J2 Received - - This parameter displays the J2 byte that is

actually received.
Parameters for the Signal Flag

Signal Label - - If the NE at the opposite end reports the

(L1,L2,L3 of V5) to LP_SLM or LP_SLM_VC3 alarm, this
be Sent parameter is set according to the V5 byte to
be received at the opposite end.
Signal Label - - If the NE at the local end reports the

(L1,L2,L3 of V5) to LP_SLM or LP_SLM_VC3 alarm, this
be Received parameter is set according to the V5 byte to
be sent at the opposite end.
Signal Label - - This parameter displays the V5 byte that is

(L1,L2,L3 of V5) actually received.
Received

Related Tasks

Configuration Guide (U2000) C Glossary
C Glossary
Terms are listed in an alphabetical order.
C.1 0-9
This section provides the terms starting with numbers.
C.2 A-E
This section provides the terms starting with letters A to E.
C.3 F-J
This section provides the terms starting with letters F to J.
C.4 K-O
This section provides the terms starting with letters K to O.
C.5 P-T
This section provides the terms starting with letters P to T.
C.6 U-Z
This section provides the terms starting with letters U to Z.
Issue 01 (2010-09-25) Huawei Proprietary and Confidential C-1

C Glossary Configuration Guide (U2000)
C.1 0-9
This section provides the terms starting with numbers.
1+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection
SNC/trail and a permanent bridge. At the source end, the normal traffic signal is
permanently bridged to both the working and protection SNC/trail. At the sink end, the
normal traffic signal is selected from the better of the two SNCs/trails. Due to the
permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic
signal to be provided.
1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)
802.1Q in 802.1Q 802.1Q in 802.1Q (QinQ) is a VLAN feature that allows the equipment to add a VLAN
tag to a tagged frame.The implementation of QinQ is to add a public VLAN tag to a
frame with a private VLAN tag, making the frame encapsulated with two layers of VLAN
tags. The frame is forwarded over the service provider's backbone network based on the
public VLAN tag. By this, a layer 2 VPN tunnel is provided to customers.The QinQ
feature enables the transmission of the private VLANs to the peer end transparently.
C.2 A-E
This section provides the terms starting with letters A to E.
ACAP See adjacent channel alternate polarization

adaptive modulation A technology that is used to automatically adjust the modulation mode according to the
channel quality. When the channel quality is favorable, the equipment adopts a high-
efficiency modulation mode to improve the transmission efficiency and the spectrum
utilization of the system. When the channel quality is degraded, the equipment adopts
the low-efficiency modulation mode to improve the anti-interference capability of the
link that carries high-priority services.
ADC See Analog to Digital Converter
add/drop multiplexer Add/Drop Multiplexing. Network elements that provide access to all or some subset of
the constituent signals contained within an STM-N signal. The constituent signals are
added to (inserted), and/or dropped from (extracted) the STM-N signal as it passed
through the ADM.
Address Resolution Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses to
Protocol MAC addresses. It allows hosts and routers to determine the link layer addresses through
ARP requests and ARP responses. The address resolution is a process in which the host
converts the target IP address into a target MAC address before transmitting a frame.
The basic function of the ARP is to query the MAC address of the target equipment
through its IP address.
adjacent channel A channel configuration method, which uses two adjacent channels (a horizontal
alternate polarization polarization wave and a vertical polarization wave) to transmit two signals.
ADM See add/drop multiplexer
C-2 Huawei Proprietary and Confidential Issue 01 (2010-09-25)

Administrative Unit The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and an AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
AGC See Automatic Gain Control
AM See adaptive modulation
Analog to Digital An electronic circuit that converts continuous signals to discrete digital numbers. The
Converter reverse operation is performed by a digital-to-analog converter (DAC).
APS See Automatic Protection Switching
ARP See Address Resolution Protocol
ASK amplitude shift keying
ATPC See automatic transmit power control
AU See Administrative Unit
Automatic Gain A process or means by which gain is automatically adjusted in a specified manner as a
Control function of a specified parameter, such as received signal level.
Automatic Protection Automatic Protection Switching (APS) is the capability of a transmission system to
Switching detect a failure on a working facility and to switch to a standby facility to recover the
traffic.
automatic transmit A method of adjusting the transmit power based on fading of the transmit signal detected
power control at the receiver
B
Base Station Controller A logical entity that connects the BTS with the MSC in a GSM network. It interworks
with the BTS through the Abis interface, the MSC through the A interface. It provides
the following functions: Radio resource management, Base station management, Power
control, Handover control, and Traffic measurement. One BSC controls and manages
one or more BTSs in an actual network.
BER See Bit Error Rate
BIOS Basic Input Output System
BIP Bit-Interleaved Parity
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
Bit Error Rate Bit error rate. Ratio of received bits that contain errors. BER is an important index used
to measure the communications quality of a network.
BPDU See Bridge Protocol Data Unit
Bridge Protocol Data The data messages that are exchanged across the switches within an extended LAN that
Unit uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
BSC See Base Station Controller

C
C-VLAN Customer VLAN
CAR See committed access rate
CBS See Committed Burst Size
CCDP See Co-Channel Dual Polarization
Central Processing The CPU is the brains of the computer. Sometimes referred to simply as the processor
Unit or central processor, the CPU is where most calculations take place.
CF See compact flash
CGMP Cisco Group Management Protocol
CIR See Committed Information Rate
CIST See Common and Internal Spanning Tree
Class of Service A class object that stores the priority mapping rules. When network congestion occurs,
the class of service (CoS) first processes services by different priority levels from high
to low. If the bandwidth is insufficient to support all services, the CoS dumps the services
of low priority.
Co-Channel Dual A channel configuration method, which uses a horizontal polarization wave and a vertical
Polarization polarization wave to transmit two signals. The Co-Channel Dual Polarization is twice
the transmission capacity of the single polarization.
committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into QoS (Quality of Service) groups, and by which the input or output transmission rate
can be defined.
Committed Burst Size committed burst size. A parameter used to define the capacity of token bucket C, that is,
the maximum burst IP packet size when the information is transferred at the committed
information rate. This parameter must be larger than 0. It is recommended that this
parameter should be not less than the maximum length of the IP packet that might be
forwarded.
Committed The rate at which a frame relay network agrees to transfer information in normal
Information Rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to
the leaky bucket.
Common and Internal Common and Internal Spanning Tree. The single Spanning Tree calculated by STP and
Spanning Tree RSTP together with the logical continuation of that connectivity through MST Bridges
and regions, calculatedby MSTP to ensure that all LANs in the Bridged Local Area
Network are simply and fully connected.
compact flash Compact flash (CF) was originally developed as a type of data storage device used in
portable electronic devices. For storage, CompactFlash typically uses flash memory in
a standardized enclosure.
CoS See Class of Service
CPU See Central Processing Unit
CRC See Cyclic Redundancy Check

cross polarization A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate
interference the cross-connect interference between two polarization waves in the CCDP.
cancellation
Cyclic Redundancy A procedure used in checking for errors in data transmission. CRC error checking uses
Check a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
Data Communication A communication network used in a TMN or between TMNs to support the Data
Network Communication Function (DCF).
Data Communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
Channel transmit information on operation, management, maintenance and provision (OAM&P)
between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the
192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12
is referred to as the 576 kbit/s DCC-M channel.
DC See Direct Current
DC-C See DC-Return Common (with Ground)
DC-I See DC-Return Isolate (with Ground)
DC-Return Common A power system, in which the BGND of the DC return conductor is short-circuited with
(with Ground) the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-Return Isolate A power system, in which the BGND of the DC return conductor is short-circuited with
(with Ground) the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See Data Communications Channel
DCN See Data Communication Network
Differentiated Services Differentiated Services CodePoint. A marker in the header of each IP packet using bits
Code Point 0-6 in the DS field. Routers provide differentiated classes of services to various service
streams/flows based on this marker. In other words, routers select corresponding PHB
according to the DSCP value.
digital modulation A digital modulation controls the changes in amplitude, phase, and frequency of the
carrier based on the changes in the baseband digital signal. In this manner, the
information can be transmitted by the carrier.
Direct Current Electrical current whose direction of flow does not reverse. The current may stop or
change amplitude, but it always flows in the same direction.
Distance Vector Distance Vector Multicast Routing Protocol. The DVMRP protocol is an Internet
Multicast Routing gateway protocol mainly based on the RIP. The protocol implements a typical dense
Protocol mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing
datagrams with its neighbors.
DSCP See Differentiated Services Code Point

dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio waves
orthogonally polarized.
DVMRP See Distance Vector Multicast Routing Protocol
E
E-LAN Ethernet-LAN
ECC See Embedded Control Channel
Electro Magnetic Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
Interference limits the effective performance of electronics/electrical equipment.
electromagnetic Electromagnetic compatibility is the condition which prevails when telecommunications
compatibility equipment is performing its individually designed function in a common electromagnetic
environment without causing or suffering unacceptable degradation due to unintentional
electromagnetic interference to or from other equipment in the same environment.
[NTIA]
Embedded Control An ECC provides a logical operations channel between SDH NEs, utilizing a data
Channel communications channel (DCC) as its physical layer.
EMC See electromagnetic compatibility
EMI See Electro Magnetic Interference
EPL See Ethernet Private Line
EPLAN See ethernet private lan service
equalization A method of avoiding selective fading of frequencies. Equalization can compensate for
the changes of amplitude frequency caused by frequency selective fading.
ERPS See ethernet ring protection switching
ES-IS End System to Intermediate System
ethernet private lan An Ethernet service type, which carries Ethernet characteristic information over a
service dedocated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or
MPLS server layer networks.
Ethernet Private Line A point-to-point interconnection between two UNIs without SDH bandwidth sharing.
Transport bandwidth is never shared between different customers.
ethernet ring protection switching mechanisms for ETH layer Ethernet ring topologies.
ethernet virtual private An Ethernet service type, which carries Ethernet characteristic information over a shared
lan service bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
ethernet virtual private An Ethernet service type, which carries Ethernet characteristic information over shared
line service bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
ETSI See European Telecommunications Standards Institute
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute

EVPL See ethernet virtual private line service

EVPLAN See ethernet virtual private lan service
C.3 F-J
This section provides the terms starting with letters F to J.
F
Fast Ethernet A type of Ethernet with a maximum transmission rate of 100 Mbit/s. It complies with
the IEEE 802.3u standard and extends the traditional media-sharing Ethernet standard.
fast link pulse The likn pulse that is used to encode information during automatic negotiation.
FCS Frame Check Sequence
FD See frequency diversity
FE See Fast Ethernet
FEC See Forward Error Correction
Field Programmable A type of semi-customized circuit used in the Application Specific Integrated Circuit
Gate Array (ASIC) field. It is developed on the basis of the programmable components, such as the
PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also
overcomes the disadvantage of the original programmable components in terms of the
limited number of gate arraies.
FIFO See First in First out
File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computers
on the Internet. Both computers must support their respective FTP roles: one must be an
FTP client and the other an FTP server.
First in First out A stack management mechanism. The first saved data is first read and invoked.
FLP See fast link pulse
Forward Error A bit error correction technology that adds the correction information to the payload at
Correction the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
FPGA See Field Programmable Gate Array
frequency diversity A diversity scheme that enables two or more microwave frequencies with a certain
frequency interval are used to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading.
FTP See File Transfer Protocol
G
gateway network A network element that is used for communication between the NE application layer and
element the NM application layer
GE See Gigabit Ethernet

Generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This is
to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
GFP Generic Framing Procedure
Gigabit Ethernet GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.It
runs at 1000Mbit/s. Gigabit Ethernet uses a private medium, and it does not support
coaxial cables or other cables. It also supports the channels in the bandwidth mode. If
Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge
(switch) or a router as the center, it gives full play to the performance and the bandwidth.
In the network structure, Gigabit Ethernet uses full duplex links that are private, causing
the length of the links to be sufficient for backbone applications in a building and campus.
GNE See gateway network element
Graphical User A visual computer enviroment that represents programs, files, and options with graphical
Interface images, such as icons, menus, and dialog boxes, on the screen.
GTS See Generic traffic shaping
GUI See Graphical User Interface
HDB3 High Density Bipolar Code 3

HDLC See High level Data Link Control procedure
High level Data Link A data link protocol from ISO for point-to-point communications over serial links.
Control procedure Derived from IBM's SDLC protocol, HDLC has been the basis for numerous protocols
including X.25, ISDN, T1, SS7, GSM, CDPD, PPP and others. Various subsets of HDLC
have been developed under the name of Link Access Procedure (LAP).
hot standby A mechanism of ensuring device running security. The environment variables and
storage information of each running device are synchronized to the standby device. When
the faults occur on the running device, the standby device can take over the services in
the faulty device in automatic or manual way to ensure the normal running of the entire
system.
HSM Hitless Switch Mode
hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports
the AM function.
ICMP See Internet Control Messages Protocol

IDU See indoor unit
IEC See International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers
IETF The Internet Engineering Task Force
IF See intermediate frequency
IGMP See Internet Group Management Protocol

IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol manages
and controls the multicast group by listening to and analyze the Internet Group
Management Protocol (IGMP) packet between hosts and layer 3 devices. In this manner,
the spread of the multicast data on layer 2 network can be prevented efficiently.
indoor unit The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and IF processing for services.
Institute of Electrical A society of engineering and electronics professionals based in the United States but
and Electronics boasting membership from numerous other countries. The IEEE focuses on electrical,
Engineers electronics, computer engineering, and science-related matters.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
signal.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
signal.
Intermediate System to A protocol used by network devices (routers) .IS-IS is a kind of Interior Gateway Protocol
Intermediate System (IGP), used within the ASs. It is a link status protocol using Shortest Path First (SPF)
algorithm to calculate the route.
International The International Electrotechnical Commission (IEC) is an international and non-
Electrotechnical governmental standards organization dealing with electrical and electronical standards.
Commission
International ISO (International Organization for Standardization) is the world's largest developer and
Organization for publisher of International Standards.
Standardization
Internet Control ICMP belongs to the TCP/IP protocol suite. It is used to send error and control messages
Messages Protocol during the transmission of IP-type data packets.
Internet Group The protocol for managing the membership of Internet Protocol multicast groups among
Management Protocol the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish
and maintain multicast group memberships.
Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sent
across an internet and provides the basis for connectionless, best-effort packet delivery
service. IP includes the ICMP control and error message protocol as an integral part. The
entire protocol suite is often referred to as TCP/IP because TCP and IP are the two
fundamental protocols. IP is standardized in RFC 791.
Internet Protocol A update version of IPv4. It is also called IP Next Generation (IPng). The specifications
Version 6 and standardizations provided by it are consistent with the Internet Engineering Task
Force (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of the
Internet Protocol, designed as the successor to IPv4. The specifications and
standardizations provided by it are consistent with the Internet Engineering Task Force
(IETF).The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
IP See Internet Protocol
IPv6 See Internet Protocol Version 6
IS-IS See Intermediate System to Intermediate System
ISO See International Organization for Standardization
ITU-T International Telecommunication Union - Telecommunication Standardization Sector

IVL Independence VLAN learning
C.4 K-O
This section provides the terms starting with letters K to O.
L
LAG See link aggregation group
LAN See Local Area Network
LAPD Link Access Procedure on the D channel
LAPS Link Access Procedure-SDH
layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmits
and distributes packet data based on the MAC address. Since the MAC address is the
second layer of the OSI model, this data forwarding method is called layer 2 switch.
LB See Loopback
LCAS See Link Capacity Adjustment Scheme
LDPC Low-Density Parity Check code
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC clientcan treat the link aggregation group as if it were
a single link.
Link Capacity The Link Capacity Adjustment Scheme (LCAS) is designed to allow the dynamic
Adjustment Scheme provisioning of bandwidth, using VCAT, to meet customer requirements.
LMSP Linear Multiplex Section Protection
Local Area Network A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
Loopback A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors.
LPT Link State Path Through
M
MA See Maintenance Association
MAC See Medium Access Control
MADM Multi Add-Drop Multiplexer
Maintenance That portion of a Service Instance, preferably all of it or as much as possible, the
Association connectivity of which is maintained by CFM. It is also a full mesh of Maintenance
Entities.

Maintenance Domain The Maintenance Domain (MD) refers to the network or the part of the network for which
connectivity is managed by CFM. The devices in an MD are managed by a single ISP.
Maintenance Point Maintenance Point (MP) is one of either a MEP or a MIP.
Management A type of database used for managing the devices in a communications network. It
Information Base comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
Maximum Transfer The MTU (Maximum Transmission Unit) is the size of the largest datagram that can be
Unit sent over a network.
MBS Maximum Burst Size
MD See Maintenance Domain
MDI See Medium Dependent Interface
Mean Time To Repair The average time that a device will take to recover from a failure.
Medium Access A general reference to the low-level hardware protocols used to access a particular
Control network. The term MAC address is often used as a synonym for physical addresses.
Medium Dependent The electrical and mechanical interface between the equipment and the media
Interface transmission.
MEP Maintenance End Point
MIB See Management Information Base
MP See Maintenance Point
MSP See multiplex section protection
MSTP See Multiple Spanning Tree Protocol
MTBF Mean Time Between Failure
MTTR See Mean Time To Repair
MTU See Maximum Transfer Unit
Multiple Spanning Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an
Tree Protocol algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed
as a tree network. In this case, the proliferation and endless cycling of packets is avoided
in the loop network.The protocol that introduces the mapping between VLANs and
multiple spanning trees. This solves the problem that data cannot be normally forwarded
in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.
multiplex section A function, which is performed to provide capability for switching a signal between and
protection including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
N
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
NE See Network Element
Network Element A network element (NE) contains both the hardware and the software running on it. One
NE is at least equipped with one system control board which manages and monitors the
entire network element. The NE software runs on the system control board.

network management The network management system in charge of the operation, administration, and
system maintenance of a network.
Network Service Access A network address defined by ISO, through which entities on the network layer can
Point access OSI network services.
NLP Normal Link Pulse
NMS See network management system
NNI Network-to-Network Interface or Network Node Interface
non-gateway network A network element whose communication with the NM application layer must be
element transferred by the gateway network element application layer.
non-GNE See non-gateway network element
NSAP See Network Service Access Point
O
OAM Operations, Administration and Maintenance
ODU See outdoor unit
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
First algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed of the network topology which is identical on all routers
in the area.
Open Systems A standard or "reference model" (officially defined by the International Organization of
Interconnection Standards (ISO)) for how messages should be transmitted between any two points in a
telecommunication network. The reference model defines seven layers of functions that
take place at each end of a communication.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
OSI See Open Systems Interconnection
OSPF See Open Shortest Path First
outdoor unit The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for RF signals.
C.5 P-T
This section provides the terms starting with letters P to T.
P
PDH See Plesiochronous Digital Hierarchy
Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should be
not less than the committed information rate.
PIM-DM Protocol Independent Multicast-Dense Mode
PIM-SM See Protocol Independent Multicast-Sparse Mode

PIR See Peak Information Rate

Plesiochronous Digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
Hierarchy rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates
data packets on the network layer. It is located in layer 2 of the IP protocol stack.
polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
PPP See Point-to-Point Protocol
PRBS Pseudo-Random Binary Sequence
Protocol Independent A protocol for efficiently routing to multicast groups that may span wide-area (and inter-
Multicast-Sparse Mode domain) internets. This protocol is named protocol independent because it is not
dependent on any particular unicast routing protocol for topology discovery, and sparse-
mode because it is suitable for groups where a very low percentage of the nodes (and
their routers) will subscribe to the multicast session. Unlike earlier dense-mode multicast
routing protocols such as DVMRP and PIM-DM which flooded packets everywhere and
then pruned off branches where there were no receivers, PIM-SM explicitly constructs
a tree from each sender to the receivers in the multicast group. Multicast packets from
the sender then follow this tree.
Q
QoS See Quality of Service
QPSK See Quadrature Phase Shift Keying
Quadrature Phase Shift Quadrature Phase Shift Keying (QPSK) is a modulation method of data transmission
Keying through the conversion or modulation and the phase determination of the reference
signals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK uses
four dots in the star diagram. The four dots are evenly distributed on a circle. On these
phases, each QPSK character can perform two-bit coding and display the codes in Gray
code on graph with the minimum BER.
Quality of Service Quality of Service, which determines the satisfaction of a subscriber for a service. QoS
is influenced by the following factors applicable to all services: service operability,
service accessibility, service maintainability, and service integrity.
R
Radio Freqency A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
Radio Network A device used in the RNS to control the usage and integrity of radio resources.
Controller

Rapid Spanning Tree An evolution of the Spanning Tree Protocol, providing for faster spanning tree
Protocol convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Received signal level The signal level at a receiver input terminal.
Received Signal The received wide band power, including thermal noise and noise generated in the
Strength Indicator receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
RF See Radio Freqency
RFC Request For Comment
RIP See Routing Information Protocol
RMON Remote Monitoring
RNC See Radio Network Controller
Routing Information Routing Information Protocol: A simple routing protocol that is part of the TCP/IP
Protocol protocol suite. It determines a route based on the smallest hop count between source and
destination. RIP is a distance vector protocol that routinely broadcasts routing
information to its neighboring routers and is known to waste bandwidth.
RS Reed-Solomon encoding
RSL Received Signal Level
RSSI See Received Signal Strength Indicator
RSTP See Rapid Spanning Tree Protocol
RTN Radio Transmission Node
S
SD See space diversity
SDH See Synchronous Digital Hierarchy
SFP See Small Form-Factor Pluggable
Signal Noise Ratio The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to the
amplitude of noise signals at a given point in time. SNR is expressed as 10 times the
logarithm of the power ratio and is usually expressed in dB (Decibel).
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Small Form-Factor A specification for a new generation of optical modular transceivers.
Pluggable
SNC See SubNetwork Connection
SNCP See SubNetwork Connection Protection
SNMP See Simple Network Management Protocol

SNR See Signal Noise Ratio

SP Strict Priority
space diversity A diversity scheme that enables two or more antennas separated by a specific distance
to transmit/receive the same signal and selection is then performed between the two
signals to ease the impact of fading. Currently, only receive SD is used.
Spanning Tree Protocol Spanning Tree Protocol. STP is a protocol that is used in the LAN to remove the loop.
STP applies to the redundant network to block some undesirable redundant paths through
certain algorithms and prune a loop network into a loop-free tree network.
SSM See Synchronization Status Message
STM See synchronous transport module
STM-1 SDH Transport Module -1
STM-1e STM-1 Electrical Interface
STM-1o STM-1 Optical Interface
STM-N SDH Transport Module -N
STP See Spanning Tree Protocol
sub-network Sub-network is the logical entity in the transmission network and comprises a group of
network management objects. The network that consists of a group of interconnected or
correlated NEs, according to different functions. For example, protection subnet, clock
subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a
sub-network is used to contain the equipments which are located in adjacent regions and
closely related with one another, and it is indicated with a sub-network icon on a
topological view. The U2000 supports multilevels of sub-networks. A sub-network
planning can better the organization of a network view. On the one hand, the view space
can be saved, on the other hand, it helps the network management personnel focus on
the equipments under their management.
SubNetwork A "transport entity" that transfers information across a subnetwork, it is formed by the
Connection association of "ports" on the boundary of the subnetwork.
SubNetwork A working subnetwork connection is replaced by a protection subnetwork connection if
Connection Protection the working subnetwork connection fails, or if its performance falls below a required
level.
SVL Shared VLAN Learning
Synchronization Status A message that is used to transmit the quality levels of timing signals on the synchronous
Message timing link. Through this message, the node clocks of the SDH network and the
synchronization network can acquire upper stream clock information, and the two
perform operations on the corresponding clocks, such as tracing, switchover, or
converting hold), and then forward the synchronization information of this node to down
stream.
Synchronous Digital SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines
Hierarchy the transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is only used only for signals. SDH is
suitable for the fiber communication system with high speed and a large capacity since
it uses synchronous multiplexing and flexible mapping structure.

synchronous transport An STM is the information structure used to support section layer connections in the
module SDH. It consists of information payload and Section Overhead (SOH) information fields
organized in a block frame structure which repeats every 125 . The information is suitably
conditioned for serial transmission on the selected media at a rate which is synchronized
to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher
capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities
for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.
T
TCI Tag Control Information
TCP See Transmission Control Protocol
TDM See Time Division Multiplexing
Telecommunication The Telecommunications Management Network is a protocol model defined by ITU-T
Management Network for managing open systems in a communications network.An architecture for
management, including planning, provisioning, installation, maintenance, operation and
administration of telecommunications equipment, networks and services.
Time Division It is a multiplexing technology. TDM divides the sampling cycle of a channel into time
Multiplexing slots (TSn, n=0, 1, 2, 3...), and the sampling value codes of multiple signals engross time
slots in a certain order, forming multiple multiplexing digital signals to be transmitted
over one channel.
TMN See Telecommunication Management Network
trail A type of transport entity, mainly engaged in transferring signals from the input of the
trail source to the output of the trail sink, and monitoring the integrality of the transferred
signals.
TransmissionControl The protocol within TCP/IP that governs the breakup of data messages into packets to
Protocol be sent via IP (Internet Protocol), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
TU Tributary Unit
C.6 U-Z
This section provides the terms starting with letters U to Z.
U
UDP See User Datagram Protocol
UNI See User Network Interface

User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagrams. UDP provides application programs with the unreliable
connectionless packet delivery service. Thus, UDP messages can be lost, duplicated,
delayed, or delivered out of order.UDP is used to try to transmit the data packet, that is,
the destination device does not actively confirm whether the correct data packet is
received.
User Network Interface A type of ATM Forum specification that defines an interoperability standard for the
interface between ATM-based products (a router or an ATM switch) located in a private
network and the ATM switches located within the public carrier networks. Also used to
describe similar connections in Frame Relay networks.
V
VC See Virtual Container
VC-12 Virtual Container -12
VCG See virtual concatenation group
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board
virtual concatenation A group of co-located member trail termination functions that are connected to the same
group virtual concatenation link
Virtual Container A Virtual Container is the information structure used to support path layer connections
in the SDH. It consists of information payload and path Overhead (POH) information
fields organized in a block frame structure which repeats every 125 or 500 μs.
Virtual Local Area A logical grouping of two or more nodes which are not necessarily on the same physical
Network network segment but which share the same IP network number. This is often associated
with switched Ethernet.
Virtual Private The extension of a private network that encompasses encapsulated, encrypted, and
Network authenticated links across shared or public networks. VPN connections can provide
remote access and routed connections to private networks over the Internet.
VLAN See Virtual Local Area Network
Voice over IP An IP telephony term for a set of facilities used to manage the delivery of voice
information over the Internet. VoIP involves sending voice information in a digital form
in discrete packets rather than by using the traditional circuit-committed protocols of the
public switched telephone network (PSTN).
VoIP See Voice over IP
VPN See Virtual Private Network
W
Wait to Restore Time A period of time that must elapse before a - from a fault recovered - trail/connection can
be used again to transport the normal traffic signal and/or to select the normal traffic
signal from.

WAN See Wide Area Network

Web LCT The local maintenance terminal of a transport network, which is located on the NE
management layer of the transport network
Wide Area Network A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
WRR Weighted Round Robin
WTR See Wait to Restore Time
X
XPD Cross-Polarization Discrimination
XPIC See cross polarization interference cancellation


RTN 950 Configuration Guide (U2000) - (V100R002C01 - 01)

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

RTN 950 Configuration Guide (U2000) - (V100R002C01 - 01)

Uploaded by

Copyright:

Available Formats

OptiX RTN 950 Radio Transmission System

Configuration Guide (U2000)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2010-09-25) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 950 V100R002C01

iManager U2000 V100R002C01

The intended audience of this document are:

l Installation and commissioning engineer

Indicates a hazard with a high level of risk,

Indicates a hazard with a medium or low level

Issue 01 (2010-09-25) Huawei Proprietary and Confidential iii

Indicates a potentially hazardous situation,

Indicates a tip that may help you solve a

Provides additional information to emphasize

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

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

iv Huawei Proprietary and Confidential Issue 01 (2010-09-25)

{ 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 ">"

Updates in Issue 01 (2010-09-25) Based on Product Version V100R002C01

Issue 01 (2010-09-25) Huawei Proprietary and Confidential v

About This Document...................................................................................................................iii

2 Configuring the Network Topology.......................................................................................2-1

3 Configuring Radio Links..........................................................................................................3-1

Issue 01 (2010-09-25) Huawei Proprietary and Confidential vii

3.3.2 Service Planning...................................................................................................................................3-16

4 Configuring TDM Services......................................................................................................4-1

5 Configuring Packet-Based Ethernet Services.......................................................................5-1

viii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

5.1.4 Ethernet Service Types Based on the Packet Plane............................................................................... 5-6

Issue 01 (2010-09-25) Huawei Proprietary and Confidential ix

5.4.2.3 Service Planning (Ethernet Services)................................................................................................5-91

x Huawei Proprietary and Confidential Issue 01 (2010-09-25)

5.7.3.1 Configuration Process (Ethernet Ports)...........................................................................................5-187

6 Configuring EoPDH-Based Ethernet Services.....................................................................6-1

Issue 01 (2010-09-25) Huawei Proprietary and Confidential xi

6.1.5.5 EVPLAN Services Based on the 802.1q Bridge...............................................................................6-11

xii Huawei Proprietary and Confidential Issue 01 (2010-09-25)

6.4.3.7 Configuration Process (Cross-Connections) ....................................................................................6-97

7 Configuring the Clock...............................................................................................................7-1

8 Configuring Auxiliary Ports and Functions..........................................................................8-1

Issue 01 (2010-09-25) Huawei Proprietary and Confidential xiii

8.4.3 Configuration Process..........................................................................................................................8-15

9 Adding and Modifying Configuration Data........................................................................9-1

xiv Huawei Proprietary and Confidential Issue 01 (2010-09-25)

A.6.4 Configuring DCC Transparent Transmission.....................................................................................A-27

Issue 01 (2010-09-25) Huawei Proprietary and Confidential xv

A.10.1 Creating the Cross-Connections of Point-to-Point Services............................................................A-59

xvi Huawei Proprietary and Confidential Issue 01 (2010-09-25)

A.12.4.3 Configuring the Aging Parameters of a MAC Address Table.......................................................A-98

Issue 01 (2010-09-25) Huawei Proprietary and Confidential xvii