RTN 380 V100R001C00 Commissioning and Configuration Guide 03 PDF

OptiX RTN 380 Radio Transmission System
V100R001C00
Commissioning and Configuration

Guide
Issue 03
Date 2013-04-25
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Copyright © Huawei Technologies Co., Ltd.
Commissioning and Configuration Guide About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX RTN 380 V100R001C00
iManager U2000 V100R008C00
Intended Audience
This document describes how to commission OptiX RTN 380, including preparations, site
commissioning, system commissioning, and network-wide service data configuration.
This document is intended for:
l Installation and commissioning engineers

l Data configuration engineers
l System maintenance engineers
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 03 (2013-04-25) Huawei Proprietary and Confidential ii

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.
Issue 03 (2013-04-25) Huawei Proprietary and Confidential iii

{ 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
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 03 (2013-04-25)
This issue is the third release for the product version V100R001C00.
Change Description
- Fixed the known bugs.
Issue 02 (2013-03-30)
This issue is the second release for the product version V100R001C00.
Change Description
- Fixed the known bugs.
8.6 Configuring Native Ethernet Services Added end-to-end configuration examples.
Issue 03 (2013-04-25) Huawei Proprietary and Confidential iv

Issue 01 (2013-01-20)
This issue is the first release for the product version V100R001C00.
Issue 03 (2013-04-25) Huawei Proprietary and Confidential v

Commissioning and Configuration Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Safety Precautions.........................................................................................................................1
1.1 General Safety Precautions.................................................................................................................................2
1.2 Warning and Safety Symbols.............................................................................................................................3
1.3 Electrical Safety..................................................................................................................................................4
1.4 Environment of Flammable Gas.........................................................................................................................5
1.5 Storage Batteries.................................................................................................................................................6
1.6 Radiation.............................................................................................................................................................7
1.6.1 Safe Usage of Optical Fibers.....................................................................................................................8
1.6.2 Electromagnetic Exposure.........................................................................................................................8
1.6.3 Forbidden Areas........................................................................................................................................8
1.6.4 Laser..........................................................................................................................................................9
1.6.5 Microwave...............................................................................................................................................10
1.7 Working at Heights...........................................................................................................................................10
1.7.1 Hoisting Heavy Objects...........................................................................................................................10
1.7.2 Using Ladders..........................................................................................................................................11
1.8 Mechanical Safety............................................................................................................................................13
1.9 Other Precautions.............................................................................................................................................14
2 Commissioning Preparations....................................................................................................16
2.1 Preparing Documents and Tools.......................................................................................................................17
2.2 Preparing the Certification File for NE Access from a USB Flash Drive........................................................18
2.3 Preparing a USB Flash Drive...........................................................................................................................19
2.4 Determining the Commissioning Method........................................................................................................20
2.5 Checking Commissioning Conditions..............................................................................................................21
2.5.1 Checking Site Commissioning Conditions..............................................................................................21
2.5.2 Checking System Commissioning Conditions........................................................................................21
3 Commissioning Process.............................................................................................................22
3.1 Site Commissioning Process (Without 1+1 Protection)...................................................................................23
3.2 Site Commissioning Procedure (with 1+1 Protection).....................................................................................24
3.3 System Commissioning Process.......................................................................................................................29
4 Site Commissioning (Using a USB Flash Drive to Configure Data).................................31

4.1 Powering On OptiX RTN 380..........................................................................................................................33
Issue 03 (2013-04-25) Huawei Proprietary and Confidential vi

4.1.1 Powering on OptiX RTN 380 (with an Outdoor PI)...............................................................................33

4.1.2 Powering on OptiX RTN 380 (with an Indoor PI)..................................................................................35
4.1.3 Powering on OptiX RTN 380 (with a DC Power Supply)......................................................................39
4.1.4 Powering on OptiX RTN 380 (with an Ethernet Board).........................................................................41
4.2 Loading Commissioning Data Using a USB Flash Drive................................................................................44
4.3 Connecting the Web LCT to the Equipment....................................................................................................46
4.4 Creating NEs Using the Search Method...........................................................................................................49
4.5 Synchronizing NE Time...................................................................................................................................50
4.6 Checking Alarms..............................................................................................................................................51
4.7 Aligning Antennas............................................................................................................................................52
4.7.1 Main Lobe and Side Lobes......................................................................................................................52
4.7.2 Aligning Single-Polarized Antennas.......................................................................................................55
4.8 Checking the Microwave Link Status and Receive Power...............................................................................57
5 Site Commissioning (Using the Web LCT to Configure Data)..........................................59

5.1 Powering On OptiX RTN 380..........................................................................................................................60
5.1.1 Powering on OptiX RTN 380 (with an Outdoor PI)...............................................................................60
5.1.2 Powering on OptiX RTN 380 (with an Indoor PI)..................................................................................62
5.1.3 Powering on OptiX RTN 380 (with a DC Power Supply)......................................................................66
5.1.4 Powering on OptiX RTN 380 (with an Ethernet Board).........................................................................68
5.2 Connecting the Web LCT to the Equipment....................................................................................................71
5.3 Creating NEs Using the Search Method...........................................................................................................73
5.4 Configuring Site Commissioning Data.............................................................................................................75
5.4.1 Changing an NE ID.................................................................................................................................75
5.4.2 Setting NE Communication Parameters..................................................................................................76
5.4.3 Changing an NE Name............................................................................................................................77
5.4.4 Setting the VLAN ID and Bandwidth for an Inband DCN.....................................................................78
5.4.5 Setting OSPF Protocol Parameters..........................................................................................................79
5.4.6 Creating a LAG.......................................................................................................................................80
5.4.7 Creating a Microwave 1+1 Protection Group..........................................................................................83
5.4.8 Configuring a Single Hop of Microwave Link........................................................................................84
5.4.9 Synchronizing NE Time..........................................................................................................................86
5.5 Checking Alarms..............................................................................................................................................87
5.6 Aligning Antennas............................................................................................................................................88
5.6.1 Main Lobe and Side Lobes......................................................................................................................88
5.6.2 Aligning Single-Polarized Antennas.......................................................................................................91
5.7 Checking the Microwave Link Status and Receive Power...............................................................................93
6 System Commissioning..............................................................................................................95
6.1 Configuring Network-wide Service Data.........................................................................................................96
6.2 Testing Ethernet Services.................................................................................................................................96
6.2.1 Testing Ethernet Services Configured on a Per NE Basis.......................................................................96
6.2.2 Testing Ethernet Services Configured in End-to-End Mode...................................................................97
6.3 Testing AMAC Shifting...................................................................................................................................99
Issue 03 (2013-04-25) Huawei Proprietary and Confidential vii

6.4 Testing Protection Switching..........................................................................................................................100

6.4.1 Testing ERPS Switching.......................................................................................................................100
6.4.2 Testing 1+1 Protection Switching.........................................................................................................103
6.5 Checking the Clock Status..............................................................................................................................105
6.6 Testing the Fade Margin over a Microwave Link..........................................................................................106
6.7 Testing Ethernet Service Performance...........................................................................................................108
6.7.1 Testing the Latency, Throughput, and Packet Loss Ratio.....................................................................108
6.7.2 Testing the Long-term Packet Loss Ratio.............................................................................................110
7 Handling of Common Faults During Site Deployment....................................................114

7.1 When a USB Flash Drive Is Used for Loading Commissioning Data, Some Commands Fail to Be Loaded
..............................................................................................................................................................................115
7.2 The Receive Power Does not Meet the Design Requirements.......................................................................115
8 Configuring Networkwide Service Data..............................................................................117

8.1 Configuration Preparations.............................................................................................................................118
8.1.1 Preparing Documents and Tools............................................................................................................118
8.1.2 Checking Configuration Conditions......................................................................................................118
8.2 General Configuration Process.......................................................................................................................118
8.3 Common Network Scenarios of Configuration Examples.............................................................................120
8.3.1 Overview...............................................................................................................................................120
8.3.2 Microwave Chain Network...................................................................................................................121
8.3.3 Microwave Ring Network.....................................................................................................................122
8.3.4 Hybrid Network Consisting of Radio Equipment and Optical Fibers...................................................123
8.3.5 Large-capacity Microwave Backhaul Network Configured with 1+1 Protection.................................124
8.4 Configuring the Network Topology...............................................................................................................125
8.4.1 Basic Concepts......................................................................................................................................125
8.4.1.1 DCN..............................................................................................................................................125
8.4.1.2 Access Control..............................................................................................................................126
8.4.1.3 GNE and Non-GNE......................................................................................................................128
8.4.1.4 NE ID and NE IP Address............................................................................................................129
8.4.1.5 Fiber/Cable Types.........................................................................................................................129
8.4.1.6 Subnet...........................................................................................................................................130
8.4.2 Configuration Process (Network Topology).........................................................................................130
8.4.3 Configuration Example (Microwave Chain Network)..........................................................................137
8.4.3.1 Networking Diagram....................................................................................................................137
8.4.3.2 Service Planning...........................................................................................................................138
8.4.3.3 Configuration Procedure...............................................................................................................139
8.4.4 Configuration Example (Microwave Ring Network)............................................................................141
8.5 Configuring Microwave Links.......................................................................................................................146
8.5.1 Basic Concepts......................................................................................................................................146
Issue 03 (2013-04-25) Huawei Proprietary and Confidential viii

8.5.1.1 AM and AMAC............................................................................................................................146

8.5.1.2 RF Configuration Modes..............................................................................................................149
8.5.1.3 E-LAG..........................................................................................................................................151
8.5.1.4 Hop Management.........................................................................................................................153
8.5.2 Configuration Process (Microwave Links)............................................................................................154
8.5.3 Configuration Example (Microwave Links on a Chain Network)........................................................159
8.5.4 Configuration Example (Microwave Links on a Ring Network)..........................................................163
8.5.5 Configuration Example (Large-Capacity Backhaul Microwave Links with 1+1 Protection)...............168
8.6 Configuring Native Ethernet Services ...........................................................................................................174
8.6.1 Basic Concepts......................................................................................................................................175
8.6.1.1 Auto-negotiation...........................................................................................................................175
8.6.1.2 Flow Control Function..................................................................................................................175
8.6.1.3 Port Description............................................................................................................................177
8.6.1.4 MAC Address Table Management...............................................................................................177
8.6.1.5 VLAN Forwarding Tables for E-Line Services............................................................................178
8.6.1.6 Split Horizon Groups....................................................................................................................179
8.6.1.7 Protection for Native Ethernet Services.......................................................................................180
8.6.2 Native Ethernet Service Types..............................................................................................................182
8.6.2.1 Transparently Transmitted Point-to-Point E-Line Service...........................................................182
8.6.2.2 VLAN-based E-Line Service........................................................................................................183
8.6.2.3 QinQ-Based E-Line Services........................................................................................................185
8.6.2.4 IEEE 802.1D Bridge-based E-LAN Services...............................................................................187
8.6.2.5 IEEE 802.1Q Bridge-based E-LAN Services...............................................................................188
8.6.3 Typical Mobile Bearer Network Topologies for Ethernet Services......................................................189
8.6.3.1 Networking of VLAN-based E-Line Services..............................................................................189
8.6.3.2 Networking of IEEE 802.1D Bridge-based E-LAN Services......................................................190
8.6.3.3 Networking of IEEE 802.1Q Bridge-based E-LAN Services......................................................191
8.6.3.4 Comparison Between the Three Networking Modes...................................................................192
8.6.4 Configuration Process............................................................................................................................195
8.6.4.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point E-Line Services).....196
8.6.4.2 End-to-End Configuration Process (Transparently Transmitted Point-to-Point E-Line Services)
..................................................................................................................................................................202
8.6.4.3 Per-NE Configuration Process (VLAN-based E-Line Services)..................................................207
8.6.4.4 End-to-End Configuration Process (VLAN-based E-Line Services)...........................................215
Issue 03 (2013-04-25) Huawei Proprietary and Confidential ix

8.6.4.5 Per-NE Configuration Process (QinQ-based E-Line Services)....................................................220

8.6.4.6 End-to-End Configuration Process (QinQ-based E-Line Services).............................................227
8.6.4.7 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)...........................232
8.6.4.8 End-to-End Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)....................241
8.6.4.9 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)...........................244
8.6.4.10 End-to-End Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)..................253
8.6.5 Configuration Example (Transparently Transmitted Point-to-Point E-Line Services).........................258
8.6.5.2 Service Planning (Port Information).............................................................................................259
8.6.5.3 Service Planning (Ethernet Protection)........................................................................................260
8.6.5.4 Service Planning (Ethernet Services)...........................................................................................260
8.6.5.5 Service Planning (QoS)................................................................................................................261
8.6.5.6 Procedure of Configuration on a Per-NE Basis (Ethernet Protection).........................................263
8.6.5.7 Procedure of Configuration on a Per-NE Basis (Service Information)........................................264
8.6.5.8 Procedure of Configuration on a Per-NE Basis (QoS).................................................................265
8.6.5.9 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification).........................268
8.6.5.10 End-to-End Configuration Procedure (Ethernet Protection)......................................................269
8.6.5.11 End-to-End Configuration Procedure (Service Information).....................................................270
8.6.5.12 End-to-End Configuration Procedure (QoS)..............................................................................271
8.6.5.13 End-to-End Configuration Procedure (Verifying Ethernet Service Configurations).................274
8.6.6 Configuration Example (VLAN-based E-Line Services)......................................................................275
8.6.6.9 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification).........................288
8.6.7 Configuration Example (QinQ-based E-Line Services)........................................................................296
8.6.7.2 Service Planning (Ethernet Ports).................................................................................................297
8.6.7.7 Procedure of Configuration on a Per-NE Basis (NNI Ports)........................................................302
Issue 03 (2013-04-25) Huawei Proprietary and Confidential x


8.6.7.10 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification).......................307
8.6.7.12 End-to-End Configuration Procedure (UNI and NNI Ports)......................................................309
8.6.8 Configuration Example (IEEE 802.1D Bridge-based E-LAN Service)................................................315
8.6.8.2 Service Planning (Ethernet Ports).................................................................................................317
8.6.8.6 Per-NE Configuration Procedure (Ethernet Protection)...............................................................323
8.6.8.7 Per-NE Configuration Procedure (Service Information)..............................................................324
8.6.8.8 Per-NE Configuration Procedure (Ethernet Ports).......................................................................326
8.6.8.9 Per-NE Configuration Procedure (QoS).......................................................................................327
8.6.8.10 Per-NE Configuration Procedure (Ethernet Service Verification).............................................329
8.6.9 Configuration Example (IEEE 802.1q Bridge-based E-LAN Services)...............................................339
8.6.9.8 Procedure of Configuration on a Per-NE Basis (Port Information).............................................345
8.6.9.10 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification).......................349
8.7 Configuring Clocks.........................................................................................................................................351
8.7.1 Basic Concepts......................................................................................................................................351
8.7.1.1 Clock Source.................................................................................................................................351
8.7.1.2 Clock Protection Modes...............................................................................................................351
8.7.1.3 Clock Synchronization Policy......................................................................................................357
8.7.2 Configuration Process (Configuring a Clock).......................................................................................360
8.7.3 Configuration Example (Clock on a Microwave Chain Network)........................................................362
Issue 03 (2013-04-25) Huawei Proprietary and Confidential xi


8.7.4 Configuration Example (Clock on a Microwave Ring Network)..........................................................364
8.8 Adding and Modifying Configuration Data...................................................................................................367
8.8.1 Common Task Collection (Network Topology)....................................................................................367
8.8.2 Common Task Collection (Microwave Links)......................................................................................368
8.8.3 Common Task Collection (Ethernet Services)......................................................................................370
A Task Collection.........................................................................................................................373
A.1 U2000 Quick Start.........................................................................................................................................374
A.1.1 Logging In to a U2000 Client...............................................................................................................374
A.1.2 Shutting Down a U2000 Client.............................................................................................................374
A.1.3 Using the Help......................................................................................................................................375
A.1.4 Navigating to Common Views.............................................................................................................376
A.1.4.1 Navigating to Main Topology.....................................................................................................376
A.1.4.2 Navigating to NE Explorer..........................................................................................................377
A.1.4.3 Navigating to the NE Panel.........................................................................................................378
A.2 Web LCT Quick Start....................................................................................................................................379
A.2.1 Connecting the Web LCT to the Equipment........................................................................................379
A.2.2 Using the Help......................................................................................................................................382
A.2.3 Navigating to NE Explorer...................................................................................................................383
A.3 Network Management...................................................................................................................................384
A.3.1 Managing NEs......................................................................................................................................384
A.3.1.1 Creating an NE by Using the Search Method..............................................................................384
A.3.1.2 Creating an NE Manually............................................................................................................386
A.3.1.3 Logging In to an NE....................................................................................................................387
A.3.1.4 Changing an NE ID.....................................................................................................................388
A.3.1.5 Changing an NE Name................................................................................................................389
A.3.1.6 Synchronizing the NE Time........................................................................................................390
A.3.1.7 Localizing the NE Time...............................................................................................................392
A.3.1.8 Configuring a Standard NTP Key................................................................................................393
A.3.2 Configuring NE Data............................................................................................................................394
A.3.2.1 Uploading NE Data......................................................................................................................394
A.3.2.2 Synchronizing NE Data...............................................................................................................396
A.3.3 Setting the Performance Monitoring Status for an NE.........................................................................396
A.3.4 Creating a Fiber/Cable..........................................................................................................................397
A.3.4.1 Creating a Fiber/Cable by Using the Search Method..................................................................397
A.3.4.2 Creating a Fiber/Cable Manually.................................................................................................398
A.3.4.3 Creating an Extended ECC Connection......................................................................................400
A.3.4.4 Creating a Back-to-back Radio Connection................................................................................401
A.3.5 Managing Subnets................................................................................................................................402
Issue 03 (2013-04-25) Huawei Proprietary and Confidential xii

A.3.5.1 Creating a Subnet.........................................................................................................................402

A.3.5.2 Copying a Topology Object.........................................................................................................402
A.3.5.3 Moving a Topology Object..........................................................................................................403
A.3.6 Managing Communication...................................................................................................................404
A.3.6.1 Setting NE Communication Parameters......................................................................................404
A.3.6.2 Configuring DCCs.......................................................................................................................405
A.3.6.3 Setting the VLAN ID and Bandwidth for an Inband DCN.........................................................406
A.3.6.4 Configuring the Priorities of Inband DCN Packets.....................................................................407
A.3.6.5 Setting a Port for an Inband DCN................................................................................................408
A.3.6.6 Configuring Access Control........................................................................................................409
A.3.6.7 Configuring Extended ECCs.......................................................................................................410
A.3.6.8 Creating a Static IP Route............................................................................................................412
A.3.6.9 Setting OSPF Protocol Parameters..............................................................................................413
A.3.6.10 Creating an OSPF Area.............................................................................................................414
A.3.6.11 Configuring the Network Information of an ABR....................................................................415
A.3.6.12 Creating a Manual Route Aggregation Group...........................................................................417
A.3.6.13 Configuring Port IP Addresses for an ABR..............................................................................418
A.3.6.14 Configuring the OSPF Authentication Type.............................................................................420
A.3.6.15 Enabling the Proxy ARP............................................................................................................421
A.3.6.16 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used..........................422
A.3.6.17 Querying ECC Routes...............................................................................................................423
A.3.6.18 Querying IP Routes....................................................................................................................424
A.3.6.19 Verifying Connectivity of an ECC Network.............................................................................425
A.3.6.20 Verifying Connectivity of an IP DCN Network........................................................................426
A.3.6.21 Setting SNMP Communication Parameters...............................................................................427
A.3.6.22 Configuring the Active and Standby Gateway NEs..................................................................429
A.3.7 Configuring the NMS Port on an NE...................................................................................................430
A.4 Security Management....................................................................................................................................431
A.4.1 Configuring an NE User.......................................................................................................................431
A.4.1.1 Creating an NE User....................................................................................................................431
A.4.1.2 Changing the Password of an NE User........................................................................................432
A.4.1.3 Setting the Warning Screen Parameters.......................................................................................433
A.4.1.4 Switching NE Users.....................................................................................................................434
A.4.2 Enabling/Disabling USB Flash Drive Access......................................................................................435
A.4.3 Configuring Web LCT Access to an NE..............................................................................................436
A.4.4 Configuring an Access Control List for an NE....................................................................................437
A.4.4.1 Creating Basic ACL Rules...........................................................................................................437
A.4.4.2 Creating Advanced ACL Rules...................................................................................................438
A.4.5 Querying NE Operation Logs...............................................................................................................439
A.4.6 Querying NE Security Logs..................................................................................................................440
A.4.7 Configuring Syslog...............................................................................................................................441
A.4.7.1 Enabling the Syslog Service........................................................................................................441
Issue 03 (2013-04-25) Huawei Proprietary and Confidential xiii

A.4.7.2 Setting Types and Severities of Logs to Be Sent to Syslog Servers............................................441

A.4.7.3 Configuring Syslog Servers.........................................................................................................442
A.4.7.4 Configuring Gateway NEs for Communication Between NEs and Syslog Servers....................443
A.4.8 Configuring File Transfer Protocols.....................................................................................................444
A.4.9 Configuring SSL Protocol Communication..........................................................................................445
A.4.9.1 Configuring SSL Protocol Communication Between a U2000 Server and Its Clients...............445
A.4.9.2 Configuring the Connection Mode Between the U2000 and Its Gateway NE............................446
A.4.10 Configuring RADIUS Authentication................................................................................................447
A.4.10.1 Enabling/Disabling the RADIUS Authentication Function......................................................448
A.4.10.2 Creating a RADIUS Server or a RADIUS Proxy Server..........................................................448
A.4.10.3 Configuring RADIUS Server Parameters..................................................................................450
A.5 Managing Microwave Links..........................................................................................................................452
A.5.1 Configuring a Single Hop of Microwave Link.....................................................................................452
A.5.2 Browsing the Performance of a Hop of Microwave Link....................................................................454
A.5.3 Creating a Microwave 1+1 Protection Group.......................................................................................455
A.5.4 Microwave 1+1 Protection Switching..................................................................................................457
A.5.5 Querying the Microwave 1+1 Protection Status...................................................................................458
A.5.6 Configuring Ethernet Frame Header Compression..............................................................................459
A.5.7 Setting the Maximum Transmit Power and the Power Thresholds......................................................460
A.5.8 Querying the AM Status.......................................................................................................................461
A.5.9 Querying ATPC Adjustment Records..................................................................................................462
A.5.10 Querying Historical Transmit Power and Receive Power..................................................................463
A.5.11 Querying the SNR Value of a Microwave Link.................................................................................464
A.6 Managing Ports..............................................................................................................................................465
A.6.1 Setting Parameters for an Ethernet Port................................................................................................465
A.6.1.1 Setting the Basic Attributes for an Ethernet Port.........................................................................465
A.6.1.2 Configuring the Traffic Control Function for an Ethernet Port...................................................466
A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port.....................................................................467
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port.................................................................468
A.6.2 Setting Parameters for a Microwave Port.............................................................................................469
A.6.2.1 Setting Basic Attributes for a Microwave Port............................................................................469
A.6.2.2 Setting Layer 2 Attributes for a Microwave Port........................................................................470
A.6.2.3 Setting Advanced Attributes for a Microwave Port....................................................................472
A.7 Managing Ethernet Services and Features.....................................................................................................473
A.7.1 Managing ERPS....................................................................................................................................473
A.7.1.1 Creating an ERP Instance............................................................................................................473
A.7.1.2 Setting ERPS Protocol Parameters..............................................................................................474
A.7.1.3 Querying the ERPS Status...........................................................................................................475
A.7.2 Managing LAGs...................................................................................................................................476
A.7.2.1 Creating a LAG............................................................................................................................476
A.7.2.2 Setting Parameters for a LAG......................................................................................................479
A.7.2.3 Querying the Protocol Information About a LAG.......................................................................480
Issue 03 (2013-04-25) Huawei Proprietary and Confidential xiv

A.7.3 Configuring Ethernet Services..............................................................................................................481

A.7.3.1 Creating a Point-to-Point Transparently Transmitted E-Line Service.........................................481
A.7.3.2 Creating a VLAN-based E-Line Service.....................................................................................482
A.7.3.3 Creating a QinQ-based E-Line Service.......................................................................................483
A.7.3.4 Creating an E-Line Service for Transmitting Layer 2 Protocol Packets.....................................485
A.7.3.5 Creating VLAN Forwarding Table Entries.................................................................................486
A.7.3.6 Creating an IEEE 802.1D Bridge-based E-LAN Service............................................................487
A.7.3.7 Creating an IEEE 802.1Q Bridge-based E-LAN Service............................................................488
A.7.3.8 Creating an E-LAN Service for Transmitting Layer 2 Protocol Packets....................................489
A.7.3.9 Configuring a Split Horizon Group.............................................................................................490
A.7.3.10 Changing Logical Ports Mounted to a Bridge...........................................................................491
A.7.3.11 Configuring a QinQ Link...........................................................................................................492
A.7.3.12 Configuring an E-Line Service Carried by a QinQ Link from a UNI to an NNI......................493
A.7.3.13 Deleting an E-Line Service........................................................................................................494
A.7.3.14 Deleting an E-LAN Service.......................................................................................................495
A.7.4 Managing MAC Address Tables..........................................................................................................496
A.7.4.1 Creating a Static MAC Address Entry.........................................................................................496
A.7.4.2 Creating a Blacklist MAC Address Entry...................................................................................497
A.7.4.3 Managing a Dynamic MAC Address Table................................................................................498
A.7.5 Setting the Mode for Processing an Unknown Frame of an E-LAN Service.......................................499
A.7.6 Managing QoS......................................................................................................................................500
A.7.6.1 Modifying the Mapping for a DS Domain..................................................................................500
A.7.6.2 Changing the Packet Type Trusted by a Port..............................................................................502
A.7.6.3 Configuring CAR for a Port or Creating Traffic Classification..................................................503
A.7.6.4 Configuring Port Shaping............................................................................................................505
A.7.6.5 Setting Egress Queue Scheduling Policies..................................................................................506
A.7.6.6 Setting Traffic Shaping for Egress Queues.................................................................................507
A.7.6.7 Setting the Congestion Management Mode for Egress Queues..................................................508
A.7.7 Using Ethernet Service OAM...............................................................................................................509
A.7.7.1 Creating an MD...........................................................................................................................509
A.7.7.2 Creating an MA...........................................................................................................................510
A.7.7.3 Creating an MEP..........................................................................................................................511
A.7.7.4 Creating a Remote MEP in an MA..............................................................................................512
A.7.7.5 Creating an MIP...........................................................................................................................513
A.7.7.6 Performing a CC Test..................................................................................................................514
A.7.7.7 Performing an LB Test................................................................................................................515
A.7.7.8 Performing an LT Test.................................................................................................................517
A.7.7.9 Activating the AIS.......................................................................................................................518
A.7.7.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services......................519
A.7.7.11 Performing E-LAN Service Loopback Detection......................................................................520
A.7.7.12 Reactivating an E-LAN Service................................................................................................521
A.7.8 Using Ethernet Port OAM....................................................................................................................522
Issue 03 (2013-04-25) Huawei Proprietary and Confidential xv

A.7.8.1 Enabling OAM Auto-discovery...................................................................................................522

A.7.8.2 Enabling the Link Event Notification..........................................................................................523
A.7.8.3 Changing the OAM Errored Frame Monitoring Threshold.........................................................524
A.7.8.4 Performing a Remote Loopback..................................................................................................526
A.7.8.5 Enabling Self-loop Detection......................................................................................................527
A.7.9 Configuring LPT...................................................................................................................................528
A.8 Managing Clocks...........................................................................................................................................529
A.8.1 Managing Clocks at the Physical Layer...............................................................................................529
A.8.1.1 Configuring Clock Sources..........................................................................................................529
A.8.1.2 Configuring Protection for Clock Sources..................................................................................530
A.8.1.3 Customizing the Clock Quality...................................................................................................531
A.8.1.4 Enabling/Disabling SSM Transmission.......................................................................................532
A.8.1.5 Enabling/Disabling the Output of Clock Source IDs..................................................................533
A.8.1.6 Modifying Clock Source Reversion Parameters..........................................................................534
A.8.1.7 Querying the Clock Synchronization Status................................................................................535
A.9 Using RMON.................................................................................................................................................536
A.9.1 Browsing Current Performance Events of Ethernet.............................................................................536
A.9.2 Setting the Ethernet Performance Threshold-Crossing Parameter.......................................................537
A.9.3 Configuring the Parameters for Ethernet Historical Performance Monitoring.....................................538
A.9.4 Browsing Ethernet Historical Performance Data..................................................................................539
A.10 Configuring a Native Ethernet Service (in End-to-End Mode)...................................................................540
A.10.1 Searching for Native Ethernet Services..............................................................................................540
A.10.2 Creating a Point-to-Point Transparently Transmitted E-Line Service................................................541
A.10.3 Creating a VLAN-based E-Line Service............................................................................................542
A.10.4 Creating a QinQ-based E-Line Service..............................................................................................543
A.10.5 Creating an IEEE 802.1D Bridge-based E-LAN Service...................................................................545
A.10.6 Creating an IEEE 802.1Q Bridge-based E-LAN Service...................................................................547
A.10.7 Verifying a Native Ethernet Service...................................................................................................549
A.10.8 Managing Native Ethernet Services...................................................................................................551
A.10.9 Managing Discrete Native Ethernet Services ....................................................................................552
A.10.10 Adjusting an E-LAN Service Network.............................................................................................553
A.11 Verifying Services and Features..................................................................................................................554
A.11.1 Testing Ethernet Services...................................................................................................................554
A.11.1.1 Testing Ethernet Services Configured on a Per NE Basis.........................................................554
A.11.1.2 Testing Ethernet Services Configured in End-to-End Mode.....................................................556
A.11.2 Testing AMAC Shifting.....................................................................................................................557
A.11.3 Testing Protection Switching..............................................................................................................558
A.11.3.1 Testing ERPS Switching............................................................................................................558
A.11.3.2 Testing 1+1 Protection Switching.............................................................................................561
B Glossary......................................................................................................................................564
Issue 03 (2013-04-25) Huawei Proprietary and Confidential xvi

Commissioning and Configuration Guide 1 Safety Precautions
1 Safety Precautions
About This Chapter
This topic describes the safety precautions that you must follow when installing, operating, and
maintaining Huawei devices.
1.1 General Safety Precautions

This topic describes essential safety precautions that instruct you in the selection of measuring
and testing instruments when you install, operate, and maintain Huawei devices.
1.2 Warning and Safety Symbols
Before using the equipment, note the following warning and safety symbols on the equipment.
1.3 Electrical Safety
This topic describes safety precautions for high voltage, lightning strikes, high leakage current,
power cables, fuses, and ESD.
1.4 Environment of Flammable Gas
This topic describes safety precautions for the operating environment of a device.
1.5 Storage Batteries
This topic describes safety precautions for operations of storage batteries.
1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
1.7 Working at Heights
This topic describes safety precautions for working at heights.
1.8 Mechanical Safety
This topic describes safety precautions for drilling holes, handling sharp objects, operating fans,
and carrying heavy objects.
1.9 Other Precautions
This topic describes safety precautions for removing and inserting boards, binding signal cables,
and routing cables.
Issue 03 (2013-04-25) Huawei Proprietary and Confidential 1

1.1 General Safety Precautions

This topic describes essential safety precautions that instruct you in the selection of measuring
and testing instruments when you install, operate, and maintain Huawei devices.
All Safety Precautions

To ensure the safety of humans and a device, follow the marks on the device and all the safety
precautions in this document when installing, operating, and maintaining a device.
The "CAUTION", "WARNING", and "DANGER" marks in this document do not cover all the
safety precautions that must be followed. They are supplements to the safety precautions.
Local Laws and Regulations

When operating a device, always comply with the local laws and regulations. The safety
precautions provided in the documents are in addition/supplementary to the local laws and
regulations.
Basic Installation Requirements

The installation and maintenance personnel of Huawei devices must receive strict training and
be familiar with the proper operation methods and safety precautions before any operation.
l Only trained and qualified personnel are permitted to install, operate, and maintain a device.
l Only certified professionals are permitted to remove the safety facilities, and to troubleshoot
and maintain the device.
l Only the personnel authenticated or authorized by Huawei are permitted to replace or
change the device or parts of the device (including software).
l The operating personnel must immediately report the faults or errors that may cause safety
problems to the person in charge.
Grounding Requirements
The grounding requirements are applicable to the device that needs to be grounded.
l When installing the device, always connect the grounding facilities first. When removing
the device, always disconnect the grounding facilities last.
l Ensure that the grounding conductor is intact.
l Do not operate the device in the absence of a suitably installed grounding conductor.
l The device must be connected to the protection ground (PGND) permanently. Before
operating the device, check the electrical connections of the device, and ensure that the
device is properly grounded.
Human Safety
l When there is a risk of a lightning strike, do not operate the fixed terminal or touch the
cables.
l When there is risk of a lightning strike, unplug the AC power connector. Do not use the
fixed terminal or touch the terminal or antenna connector.

NOTE
The preceding requirements apply to wireless fixed station terminals.
l To avoid electric shocks, do not connect safety extra-low voltage (SELV) circuits to
telephone-network voltage (TNV) circuits.
l Do not look into optical ports without eye protection. Otherwise, human eyes may be hurt
by laser beams.
l Before operating the device, wear an ESD protective coat, ESD gloves, and an ESD wrist
strap. In addition, you need to get off the conductive objects, such as jewelry and watches,
to prevent electric shock and burn.
l In case of fire, escape from the building or site where the device is located and press the
fire alarm bell or dial the telephone number for fire alarms. Do not enter the burning building
again in any situation.
Device Safety
l Before any operation, install the device firmly on the ground or other rigid objects, such as
on a wall or in a rack.
l When the system is working, ensure that the ventilation hole is not blocked.
l When installing the front panel, use a tool to tighten the screws firmly, if required.
l After installing the device, clean up the packing materials.
1.2 Warning and Safety Symbols

Before using the equipment, note the following warning and safety symbols on the equipment.
Table 1-1 lists the warning and safety symbols of the OptiX RTN 380 and their meanings.
Table 1-1 Warning and safety symbols of the OptiX RTN 380
Label Label Name Description
ESD protection label Indicates that the equipment is

sensitive to static electricity.
Radiation warning label Indicates that the equipment

generates electromagnetic
radiation.
High temperature warning label Indicates that the equipment

surface temperature may exceed
70°C when the ambient
temperature is higher than 55°C.
Wear protective gloves to handle
the equipment.
Grounding label Indicates the grounding position

of a chassis.

1.3 Electrical Safety

This topic describes safety precautions for high voltage, lightning strikes, high leakage current,
power cables, fuses, and ESD.
High Voltage
DANGER
l A high-voltage power supply provides power for device operations. Direct human contact
with the high voltage power supply or human contact through damp objects can be fatal.
l Unspecified or unauthorized high voltage operations could result in fire or electric shock, or
both.
Thunderstorm
The requirements apply only to wireless base stations or devices with antennas and feeders.
DANGER
Do not perform operations on high voltage, AC power, towers, or backstays in stormy weather
conditions.
High Leakage Current
WARNING
Before powering on a device, ground the device. Otherwise, the safety of humans and the device
cannot be ensured.
If a high leakage current mark is labeled near the power connector of the device, you must
connect the PGND terminal on the shell to the ground before connecting the device to an A/C
input power supply. This is to prevent the electric shock caused by leakage current of the device.

Power Cables
DANGER
Do not install or remove the power cable with a live line. Transient contact between the core of
the power cable and the conductor may generate electric arc or spark, which may cause fire or
eye injury.
l Before installing or removing power cables, you must power off the device.
l Before connecting a power cable, you must ensure that the label on the power cable is
correct.
Device with Power On
DANGER
Installing or removing a device is prohibited if the device is on.
DANGER
Do not install or remove the power cables of the equipment when it is powered on.
Short Circuits
When installing and maintaining devices, place and use the associated tools and instruments in
accordance with regulations to avoid short-circuits caused by metal objects.
Fuse
WARNING
If the fuse on a device blows, replace the fuse with a fuse of the same type and specifications to
ensure safe operation of the device.
1.4 Environment of Flammable Gas

This topic describes safety precautions for the operating environment of a device.

DANGER
Do not place or operate devices in an environment of flammable or explosive air or gas.
Operating an electronic device in an environment of flammable gas causes a severe hazard.
1.5 Storage Batteries

This topic describes safety precautions for operations of storage batteries.
DANGER
Before operating a storage battery, you must read the safety precautions carefully and be familiar
with the method of connecting a storage battery.
l Incorrect operations of storage batteries cause hazards. During operation, prevent any short-
circuit, and prevent the electrolyte from overflowing or leakage.
l If the electrolyte overflows, it causes potential hazards to the device. The electrolyte may
corrode metal parts and the circuit boards, and ultimately damage the circuit boards.
l A storage battery contains a great deal of energy. Misoperations may cause a short-circuit,
which leads to human injuries.
Basic Precautions
To ensure safety, note the following points before installing or maintaining the storage battery:
l Use special insulation tools.
l Wear an eye protector and take effective protection measures.
l Wear rubber gloves and a protection coat to prevent the hazard caused by the overflowing
electrolyte.
l When handling the storage battery, ensure that its electrodes are upward. Leaning or
reversing the storage battery is prohibited.
l Before installing or maintaining the storage battery, ensure that the storage battery is
disconnected from the power supply that charges the storage battery.
Short-Circuit
DANGER
A battery short-circuit may cause human injuries. Although the voltage of an ordinary battery
is low, the instantaneous high current caused by a short-circuit emits a great deal of energy.
Avoid any short-circuit of batteries caused by metal objects. If possible, disconnect the working
battery before performing other operations.

Hazardous Gas
CAUTION
Do not use any unsealed lead-acid storage battery. Lay a storage battery horizontally and fix it
properly to prevent the battery from emitting flammable gas, which may cause fire or device
erosion.
Working lead-acid storage batteries emit flammable gas. Therefore, ventilation and fireproofing
measures must be taken at the sites where lead-acid storage batteries are placed.
Battery Temperature
CAUTION
If a battery overheats, the battery may be deformed or damaged, and the electrolyte may
overflow.
When the temperature of the battery is higher than 60°C, you need to check whether the
electrolyte overflows. If the electrolyte overflows, take appropriate measures immediately.
Battery Leakage
CAUTION
In the event of acid overflow or spillage, neutralize the acid and clean it up appropriately.
When handling a leaky battery, protect against the possible damage caused by the acid. When
you find the electrolyte leaks, you can use the following substances to counteract and absorb the
leaking electrolyte:
l Sodium bicarbonate (NaHCO3)
l Sodium carbonate (Na2CO3)
In the event of acid overflow or spillage, neutralize the acid and clean it up as recommended by
the battery manufacturer and any local regulations for acid disposal.
If a person contacts battery electrolyte, clean the skin that contacts the battery electrolyte
immediately by using water. In case of a severe situation, the person must be sent to a hospital
immediately.
1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.

1.6.1 Safe Usage of Optical Fibers

The laser beam can cause damage to your eyes. Hence, you must exercise caution when using
optical fibers.
DANGER
When installing or maintaining optical fibers, avoid direct eye exposure to the laser beams
launched from the optical interface or fiber connectors. The laser beam can cause damage to
your eyes.
Cleaning Fiber Connectors and Optical Interfaces
CAUTION
If fiber connectors or flanges are contaminated, optical power commissioning is seriously
affected. Therefore, the two endfaces and flange of every external fiber must be cleaned before
the fiber is led into the equipment through the optical distribution frame (ODF) for being inserted
into an optical interface on the equipment.
The fiber connectors and optical interfaces of the lasers must be cleaned with the following
special cleaning tools and materials:
l Special cleaning solvent: It is preferred to use isoamylol. Propyl alcohol, however, can also
be used. It is prohibited that you use alcohol and formalin.
l Non-woven lens tissue
l Special compressed gas
l Cotton stick (medical cotton or long fiber cotton)
l Special cleaning roll, used with the recommended cleaning solvent
l Special magnifier for fiber connectors
1.6.2 Electromagnetic Exposure

This topic describes safety precautions for electromagnetic exposure.
If multiple transmit antennas are installed on a tower or backstay, keep away from the transmit
directions of the antennas when you install or maintain an antenna locally.
CAUTION
Ensure that all personnel are beyond the transmit direction of a working antenna.
1.6.3 Forbidden Areas

The topic describes requirements for a forbidden area.

l Before entering an area where the electromagnetic radiation is beyond the specified range,
the associated personnel must shut down the electromagnetic radiator or stay at least 10
meters away from the electromagnetic radiator, if in the transmit direction.
l A physical barrier and an eye-catching warning flag should be available in each forbidden
area.
1.6.4 Laser
This topic describes safety precautions for lasers.
WARNING
When handling optical fibers, do not stand close to, or look into the optical fiber outlet directly
without eye protection.
Laser transceivers are used in the optical transmission system and associated test tools. The laser
transmitted through the bare optical fiber produces a small beam of light, and therefore it has
very high power density and is invisible to human eyes. When a beam of light enters eyes, the
eyes may be damaged.
In normal cases, viewing an un-terminated optical fiber or a damaged optical fiber without eye
protection at a distance greater than 150 mm does not cause eye injury. Eye injury may occur,
however, if an optical tool such as a microscope, magnifying glass, or eye loupe is used to view
an un-terminated optical fiber.
Safety Instructions Regarding Lasers

To avoid laser radiation, obey the following instructions:
l All operations should be performed by authorized personnel who have completed the
required training courses.
l Wear a pair of eye-protective glasses when you are handling lasers or fibers.
l Ensure that the optical source is switched off before disconnecting optical fiber connectors.
l Do not look into the end of an exposed fiber or an open connector when you are not sure
whether the optical source is switched off.
l Use an optical power meter to measure the optical power and ensure that the optical source
is switched off.
l Before opening the front door of an optical transmission device, ensure that you are not
exposed to laser radiation.
l Do not use an optical tool such as a microscope, a magnifying glass, or an eye loupe to
view the optical connector or fiber that is transmitting optical signals.
Instructions Regarding Fiber Handling

Read and abide by the following instructions before handling fibers:
l Only trained personnel are permitted to cut and splice fibers.
l Before cutting or splicing a fiber, ensure that the fiber is disconnected from the optical
source. After disconnecting the fiber, cap to the fiber connectors.

1.6.5 Microwave
When installing and maintaining the equipment of Huawei, follow the safety precautions of
microwave to ensure the safety of the human body and the equipment.
WARNING
Strong radio frequency can harm the human body.
When installing or maintaining an aerial on the tower or mast that is installed with multiple
aerials, switch off the transmitter in advance.
1.7 Working at Heights

This topic describes safety precautions for working at heights.
WARNING
When working at heights, be cautious to prevent objects from falling down.
The requirements for working at heights are as follows:
l The personnel who work at heights must be trained.

l Carry and handle the operating machines and tools with caution to prevent them from falling
down.
l Safety measures, such as wearing a helmet and a safety belt, must be taken.
l Wear cold-proof clothes when working at heights in cold areas.
l Check all lifting appliances thoroughly before starting the work, and ensure that they are
intact.
1.7.1 Hoisting Heavy Objects

This topic describes the safety precautions for hoisting heavy objects that you must follow when
installing, operating, and maintaining Huawei devices.
WARNING
When heavy objects are being hoisted, do not walk below the cantilever or hoisted objects.
l Only trained and qualified personnel can perform hoisting operations.

l Before hoisting heavy objects, check that the hoisting tools are complete and in good
condition.

l Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object or
wall with good weight-bearing capacity.
l Issue orders with short and explicit words to ensure correct operations.
l Ensure that the angle between the two cables is less than or equal to 90 degrees during the
lifting, as shown in Figure 1-1.
Figure 1-1 Hoisting heavy objects
1.7.2 Using Ladders

This topic describes safety precautions for using ladders.
Checking Ladders
l Before using a ladder, check whether the ladder is damaged. After checking that the ladder
is in good condition, you can use the ladder.
l Before using a ladder, you should know the maximum weight capacity of the ladder. Avoid
overweighing the ladder.
Placing Ladders
The proper slant angle of the ladder is 75 degrees. You can measure the slant angle of the ladder
with an angle square or your arms, as shown in Figure 1-2. When using a ladder, to prevent the

ladder from sliding, ensure that the wider feet of the ladder are downward, or take protection
measures for the ladder feet. Ensure that the ladder is placed securely.
Figure 1-2 Slanting a ladder
Climbing Up a Ladder
When climbing up a ladder, pay attention to the following points:
l Ensure that the center of gravity of your body does not deviate from the edges of the two
long sides.
l Before operations, ensure that your body is stable to reduce risks.
l Do not climb higher than the fourth rung of the ladder (counted from up to down).
If you want to climb up a roof, ensure that the ladder top is at least one meter higher than the
roof, as shown in Figure 1-3.
Figure 1-3 Ladder top being one meter higher than the roof

1.8 Mechanical Safety

This topic describes safety precautions for drilling holes, handling sharp objects, operating fans,
and carrying heavy objects.
Drilling Holes
WARNING
Do not drill holes on the cabinet without prior permission. Drilling holes without complying
with the requirements affects the electromagnetic shielding performance of the cabinet and
damages the cables inside the cabinet. In addition, if the scraps caused by drilling enter the
cabinet, the printed circuit boards (PCBs) may be short-circuited.
l Before drilling a hole on the cabinet, remove the cables inside the cabinet.
l Wear an eye protector when drilling holes. This is to prevent eyes from being injured by
the splashing metal scraps.
l Wear protection gloves when drilling holes.
l Take measures to prevent the metallic scraps from falling into the cabinet. After the drilling,
clean up the metallic scraps.
Sharp Objects
WARNING
Wear protection gloves when carrying the device. This is to prevent hands from being injured
by the sharp edges of the device.
Fans
l When replacing parts, place the objects such as the parts, screws, and tools properly. This
is to prevent them from falling into the operating fans, which damages the fans or device.
l When replacing the parts near fans, keep your fingers or boards from touching operating
fans before the fans are powered off and stop running. Otherwise, the hands or the boards
are damaged.
Carrying Heavy Objects

Wear protection gloves when carrying heavy objects. This is to prevent hands from being hurt.

WARNING
l The carrier must be prepared for load bearing before carrying heavy objects. This is to prevent
the carrier from being strained or pressed by the heavy objects.
l When you pull a chassis out of the cabinet, pay attention to the unstable or heavy objects on
the cabinet. This is to prevent the heavy objects on the cabinet top from falling down, which
may hurt you.
l Generally, two persons are needed to carry a chassis. It is prohibited that only one person
carries a heavy chassis. When carrying a chassis, the carriers should stretch their backs and
move stably to avoid being strained.
l When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not hold
the handles of the modules installed in the chassis, such as the power modules, fan modules,
and boards.
1.9 Other Precautions

This topic describes safety precautions for removing and inserting boards, binding signal cables,
and routing cables.
Removing and Inserting a Board
CAUTION
When inserting a board, wear an ESD wrist strap or ESD gloves, and handle the board gently to
avoid distorting pins on the backplane.
l Slide the board along the guide rails.

l Do not contact one board with another to avoid short-circuits or damage.
l When holding a board in hand, do not touch the board circuits, components, connectors,
or connection slots of the board to prevent damage caused by ESD of the human body to
the electrostatic-sensitive components.
Binding Signal Cables
CAUTION
Bind the signal cables separately from the high-current or high-voltage cables.
Routing Cables
In the case of extremely low temperature, heavy shock or vibration may damage the plastic skin
of the cables. To ensure the construction safety, comply with the following requirements:

l When installing cables, ensure that the environment temperature is above 0°C.
l If the cables are stored in a place where the ambient temperature is below 0°C, transfer
them to a place at room temperature and store the cables for more than 24 hours before
installation.
l Handle the cables gently, especially in a low-temperature environment. Do not perform
any improper operations, for example, pushing the cables down directly from a truck.
High Temperature
WARNING
If the ambient temperature exceeds 55°C, the temperature of the front panel surface marked the
flag may exceed 70°C. When touching the front panel of the board in such an environment,
you must wear the protection gloves.

Commissioning and Configuration Guide 2 Commissioning Preparations
2 Commissioning Preparations
About This Chapter
This chapter describes the preparations that must be made prior to commissioning equipment.
The preparation process is as follows:
2.1 Preparing Documents and Tools
This section lists the documents and tools to be obtained prior to equipment commissioning.
2.2 Preparing the Certification File for NE Access from a USB Flash Drive
This section describes how to prepare an RTN.CER file used for authentication of NE access
from a USB flash drive. The file allows you to perform site commissioning, database backup/
restoration, and software upgrades using a USB flash drive.
2.3 Preparing a USB Flash Drive
Prepare a USB flash drive if it is required for commissioning.
2.4 Determining the Commissioning Method
According to the scale of a microwave transmission network, commissioning engineers can use
the network commissioning method.
2.5 Checking Commissioning Conditions
Ensure that the equipment meets the requirements for site commissioning or system
commissioning prior to performing any commissioning tasks.

2.1 Preparing Documents and Tools

This section lists the documents and tools to be obtained prior to equipment commissioning.
Documents
Obtain the following documents before equipment commissioning:
l Engineering design documents, including:
– Network Plan
– Engineering Design
l Commissioning guide, including:
– OptiX RTN 380 Microwave Transmission System Commissioning and Configuration
Guide
Tools
Prepare the tools listed in Table 2-1 before equipment commissioning.
Table 2-1 Tools

Tool Application Scenario
Adjustable wrench, screwdriver, telescope, Aligning antennas

interphone, hex key (delivered with
antennas), multimeter, north-stabilized
indicator, and received signal strength
indicator (RSSI) test cable (delivered with
OptiX RTN 380)
A laptop with the Web LCT installed l Configuring site commissioning data
l Checking the microwave link status and
receive power
l Testing adaptive modulation (AM)
shifting
l Checking alarms
Network management system (NMS) server Performing system commissioning items
NOTE
For details about the requirements and methods for installing the Web LCT, see the iManager U2000 Web
LCT User Guide.

2.2 Preparing the Certification File for NE Access from a

USB Flash Drive
This section describes how to prepare an RTN.CER file used for authentication of NE access
from a USB flash drive. The file allows you to perform site commissioning, database backup/
restoration, and software upgrades using a USB flash drive.
Prerequisites
The NMS is available.
Tools, Equipment, and Materials

U2000
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Access D:\oss\client\client\tools\usbtool (an example) where the USB file generation tool is
stored.
NOTE
On the Web LCT, the USB file generation tool in stored D:\WebLCT\weblct\tools\usbtool (an example).
Step 2 Run startup_usbTool.bat.
The USB File Generation Tool dialog box is displayed.

Step 3 Enter the NE use name, enter and confirm the password, and click Generate File.

Step 4 Click OK in the displayed confirmation dialog box.
Step 5 Access D:\oss\client\client\tools\usbtool\output (an example) where the RTN.CER file is

stored, and copy the file to the root directory of the USB flash drive.
NOTE
l On the Web LCT, the RTN.CER file is stored in D:\WebLCT\weblct\tools\usbtool\output (an example).
l Save the RTN.CER file before closing USB file generation tool. Otherwise, the file will be automatically
deleted when you close the tool.
----End
2.3 Preparing a USB Flash Drive

Prepare a USB flash drive if it is required for commissioning.
USB Flash Drive Model

The USB flash drive model recommended for OptiX RTN 380 is Locitech U208 (4 GB). If a
USB flash drive of another model or capacity is required, contact the local Huawei office for
confirmation. Not all USB flash drives are supported by OptiX RTN 380.
Content and Storage Paths on the USB Flash Drive

Data Storage Directory
NE software \pkg
Patch \patch
License software \license
Script \script

Data Storage Directory
USB authentication certificate Root directory

NOTE
The RTN.CER file stores the administrator
accounts and passwords. The passwords are
encrypted in MD5/SHA256 format. This file is
generated using a special-purpose tool.
2.4 Determining the Commissioning Method

According to the scale of a microwave transmission network, commissioning engineers can use
the network commissioning method.
NOTE
In the following instructions for both types of commissioning methods, site commissioning and system
commissioning are defined as follows:
l Site commissioning refers to the commissioning of one microwave link hop and the sites at both ends of the
hop. Site commissioning is carried out with commissioning tools connected to the NE at a single site.
l System commissioning refers to the commissioning and configuring of all NEs on a network. System
commissioning is carried out with commissioning tools connected to a gateway NE.
Single-Hop Commissioning
Single-hop commissioning is preferred for small-scale microwave transmission networks (for
example, a network with only one or two microwave link hops). By performing single-hop
commissioning, you can complete all site and system commissioning tasks at one time. The
major steps are outlined as follows:
1. On both ends of a microwave link,power on the equipment.

2. Load commissioning data using a USB flash drive or configure commissioning data
using the Web LCT.
3. Use the Web LCT to complete the site commissioning items.
4. Use the Web LCT to complete the system commissioning items.
Network Commissioning
Network commissioning is usually carried out for large-scale microwave transmission networks.
The major steps are outlined as follows:
1. On both ends of a microwave link, power on the equipment.

2. Load commissioning data using a USB flash drive or configure commissioning data
using the Web LCT.
3. Use the Web LCT to complete the site commissioning items.
4. Use the U2000 to complete the system commissioning items at the site where services
converge.

2.5 Checking Commissioning Conditions

Ensure that the equipment meets the requirements for site commissioning or system
commissioning prior to performing any commissioning tasks.
2.5.1 Checking Site Commissioning Conditions

Before performing site commissioning, ensure that the equipment and weather conditions meet
the requirements for site commissioning.
The requirements are listed as follows:
l Hardware installation has been completed and has passed the installation check.
l Power is available for the equipment.
l Service signal cables have been properly routed.
l Onsite conditions meet the requirements for antennas to work at their given heights, and
the commissioning personnel are trained to work at these heights.
l There are no adverse weather conditions (such as strong wind, rain, snow, or fog) that could
hinder or affect commissioning.
2.5.2 Checking System Commissioning Conditions

Before performing system commissioning, ensure that the equipment and weather meet the
requirements for system commissioning.
The requirements are listed as follows:
l Site commissioning at both ends of a microwave link has been completed.
l Data communication network (DCN) communication on the microwave transmission
network is normal.
l There are no adverse weather conditions (such as strong wind, rain, snow, or fog) that could
hinder or affect commissioning.

Commissioning and Configuration Guide 3 Commissioning Process
3 Commissioning Process
About This Chapter
Based on the objects to be commissioned, commissioning involves two stages: site

commissioning and system commissioning.
3.1 Site Commissioning Process (Without 1+1 Protection)

Site commissioning refers to the commissioning of one microwave link hop and the sites at both
ends of the hop. Site commissioning ensures that the sites and the microwave link between the
sites work properly. Site commissioning is a preparation for system commissioning.
3.2 Site Commissioning Procedure (with 1+1 Protection)
For sites configured with 1+1 protection, the commissioning procedure is different.
3.3 System Commissioning Process
System commissioning refers to the commissioning of an entire microwave transmission
network. System commissioning ensures that various services are transmitted properly and
protection is implemented across the network.

3.1 Site Commissioning Process (Without 1+1 Protection)

Site commissioning refers to the commissioning of one microwave link hop and the sites at both
ends of the hop. Site commissioning ensures that the sites and the microwave link between the
sites work properly. Site commissioning is a preparation for system commissioning.
You can use the following tools to configure site without 1+1 protection commissioning data
for OptiX RTN 380:
l USB flash drive
l Web LCT
Site Commissioning Items (Using a USB Flash Drive to Configure Data)

Engineers can configure site commissioning data using a USB flash drive onsite if they:
l Are familiar with the microwave link plan for the target sites.
l Have a USB flash drive that contains the NE commissioning data.
l Have a laptop on which the Web LCT is installed.
Table 3-1 Configuring site commissioning data using a USB flash drive
Commissioning Item Remarks
Powering on the Equipment Required.
Loading Commissioning Data Using a USB Flash Drive Required.
Connecting the Web LCT to the Equipment Required.
Creating NEs Using the Search Method Required.
Synchronizing NE Time Required.
Checking Alarms Required.
Aligning Antennasa Aligning Single-Polarized Required when radio services

Antennas are transmitted by single-
polarized antennas.
Checking the Microwave Link Status and Receive Power Required.
NOTE
a: Before aligning antennas, power on the equipment and configure site commissioning data at both ends
of the microwave link.
Site Commissioning Items (Using the Web LCT to Configure Data)

Engineers can configure site commissioning data using the Web LCT onsite if they:
l Are familiar with how to configure microwave link data on OptiX RTN 380.
l Are familiar with the microwave link plan for the target sites.

l Have a laptop on which the Web LCT is installed.
Powering on the Equipment Required.
Connecting the Web LCT to the Equipment Required.
Creating NEs Using the Search Method Required.
Configuring Site Changing an NE ID Required.

Commissioning Data
Configuring NE Required.
Communications
Parameters
Changing an NE Name Required.
Setting the VLAN ID and Optional.

Bandwidth for an Inband
DCN
Setting OSPF Protocol Required.

Parameters
Configuring Data for a Hop Required.

of Microwave Link
Synchronizing the NE Time Required.
Checking Alarms Required.
Aligning Antennas Aligning Single-Polarized Required when radio services

Antennas are transmitted by single-
polarized antennas.
Checking the Microwave Link Status and the Receive Required.

Power
NOTE
Before aligning antennas, power on the equipment and configure site commissioning data at both ends of
the microwave link.
3.2 Site Commissioning Procedure (with 1+1 Protection)

For sites configured with 1+1 protection, the commissioning procedure is different.
NOTE
Sites configured with 1+1 protection only support configuration of commissioning data using the Web LCT,
and do not support configuration of commissioning data using a USB flash drive.
Site Commissioning Items (Configuring Commissioning Data Using the Web LCT)
Commissioning engineers can configure commissioning data using the Web LCT on site when:

l The commissioning engineers are familiar with the microwave link data plan for target
sites.
l The commissioning engineers have a laptop on which the Web LCT has been installed.
l The 1+1 cascade optical fibers between COMBO ports on the active and standby OptiX
RTN 380s have been connected.
l The outdoor optical fibers between GE ports on peer OptiX RTN 380s have been connected.
Site commissioning can be performed according to Figure 3-1 or Figure 3-2 depending on the
number of data configuration engineers responsible for configuring 1+1 protection at both sites.
NOTE
l Antenna alignment engineers align antennas, activate radio links, and turn over the subsequent
commissioning to the data configuration engineers responsible for configuring 1+1 protection.
l The data configuration engineers responsible for configuring 1+1 protection completes the configuration of
1+1 protection.
l An engineer familiar with site commissioning can align antennas and configure 1+1 protection on himself/
herself.
Figure 3-1 Coordinately configuring 1+1 protection for sites at both ends
Near-end site Far-end site
Main Main
LAG LAG
LAG LAG
Web LCT Antenna Antenna Web LCT
LAG LAG
Standby Standby
E-LAG E-LAG
Antenna alignment Data configuration Antenna alignment Data configuration engineer

engineer engineer responsible for engineer responsible for configuring
configuring 1+1 protection 1+1 protection
Active NE Standby NE Active NE Standby NE
1 1
Power on the Power on the
equipment. equipment.
2
2 Configure site
Configure site
commissioning commissioning
Change an NE ID. data. Change an NE ID. data.
3 3
Configure NE Configure NE
Check alarms. communication Check alarms.
communication
parameters. parameters.
Change an NE
Change an NE name. 4 4
name.
Align antennas Align antennas
Configure the VLAN ID Configure the VLAN
and bandwidth for ID and bandwidth for
inband DCN. 5 inband DCN. 5
Check the status Check the status
Configure OSPF and receive power Configure OSPF and receive power
parameters. of the active parameters. of the active
microwave link. microwave link.
Configure a hop of Configure a hop of
microwave link. 6 microwave link. 6
equipment. Synchronize NE equipment.
Synchronize NE time.
time.
7 7
Configure site Configure site
commissioning Change an NE ID. commissioning Change an NE ID.
parameters. data.
8 8 Configure NE Configure NE
Deleting an E-LAN Deleting an E-LAN 8 8 communication
communication data. Deleting an E-LAN Deleting an E-LAN
Service or Deleting Service or Deleting parameters.
Service or Deleting Service or Deleting
an E-Line Service an E-Line Service
Change an NE an E-Line Service an E-Line Service Change an NE
name. name.
If an optical splitter is used 9.1
10.1 Configure a If an optical splitter is
to form 1+1 protection, this Configure a LAG for 9.1 Configure the VLAN ID
LAG for 1+1 Configure the VLAN used to form 1+1 10.1 Configure a
step does not need to be 1+1 protection. Configure a LAG and bandwidth for
protection. ID and bandwidth for protection, this step does LAG for 1+1
performed. for 1+1 protection. inband DCN.
inband DCN. not need to be performed. protection.
9.2 10.2 Configure OSPF Configure OSPF
Configure a 1+1 Configure a 1+1 parameters. 9.2 10.2 parameters.
protection group. protection group. Configure a 1+1 Configure a 1+1
protection group. protection group.
Configure a hop of Configure a hop of
11 11 microwave link. microwave link.
11 11
Check alarms. Check alarms.
Synchronize NE Check alarms. Check alarms. Synchronize NE
time. time.
12
Required 12
Check the status and
receive power of the Check the status
Optional microwave links. and receive power
of the microwave
No operation links.

For sites at both ends of a link, perform the following simultaneously:

1. Power on the active OptiX RTN 380s according to Powering on the Equipment and keep
the standby OptiX RTN 380s in the off status.
2. Configure commissioning data for the active OptiX RTN 380s according to Configuring
Site Commissioning Data. At this time, do not configure the microwave 1+1 protection
group (or the link aggregation group used for 1+1 protection if the protection involves
OptiX RTN 900).
3. Check alarms on the active OptiX RTN 380s according to Checking Alarms.
4. Align single-polarized antennas according to Aligning Single-Polarized Antennas to
activate microwave links between the active OptiX RTN 380s.
5. Check the status and receive power of the microwave link between the active OptiX RTN
380s according to Checking the Microwave Link Status and Receive Power.
6. Power on the standby OptiX RTN 380s according to Powering on the Equipment.
7. Perform A.7.3.14 Deleting an E-LAN Service or A.7.3.13 Deleting an E-Line Service
for the active/standby OptiX RTN 380.
NOTE
By default, an OptiX RTN 380 creates a bridge-based E-LAN service. All ports of the OptiX RTN 380
are mounted to the bridge. The Ethernet ports that do not participate in 1+1 protection will result in a 1+1
protection configuration failure. Therefore, you must delete this E-LAN service.
8. Configure commissioning data for the standby NE and data for active and standby
microwave 1+1 protection groups (and the link aggregation group used for 1+1
protection if the protection involves OptiX RTN 900).
9. Check alarms on the active and standby OptiX RTN 380s according to Checking
Alarms.
10. Check the status and receive power of microwave links according to Checking the
Microwave Link Status and Receive Power.

Figure 3-2 Independently configuring 1+1 protection for the near-end site
Near-end site Far-end site
Main Main
LAG LAG
LAG LAG
Web LCT Antenna Antenna Web LCT
LAG LAG
Standby Standby
E-LAG E-LAG
Antenna alignment Antenna alignment

engineer engineer
Active NE Standby NE Active NE Standby NE
1 1
equipment. equipment.
2 2
Change an NE ID. Configure site Change an NE ID. Configure site
commissioning commissioning
Configure NE data. Configure NE data.
communication communication
3 3
parameters. parameters.
Check alarms. Check alarms.
Change an NE Change an NE
name. name.
Configure the VLAN ID 4 4

Configure the VLAN
and bandwidth for Align antennas Align antennas
ID and bandwidth for
inband DCN.
inband DCN.
Configure OSPF Configure OSPF 5
5
parameters. parameters. Check the status
Check the status
and receive power
and receive power
Configure a hop of of the active
of the active Configure a hop of
Synchronize NE Synchronize NE 6
time. Power on the
time.
equipment.
7 7
Deleting an E-LAN Deleting an E-LAN
The data configuration
engineers responsible for
configuring 1+1 protection
configure the following for sites If an optical splitter is used
8.1 9.1
at both ends using DCN at the to form 1+1 protection, this Configure a
Configure a LAG
near end. step does not need to be LAG for 1+1
for 1+1 protection.
performed. protection.
8.2 9.2
Configure a 1+1 Configure a 1+1
protection group. protection group.
10
Lock the 1+1
protection group of
the active devices to
the active unit.
11 11
Deleting an E-LAN Deleting an E-LAN
If an optical splitter is used 12.1 13.1

to form 1+1 protection, this Configure a LAG Configure a LAG
step does not need to be for 1+1 protection. for 1+1 protection.
performed.
12.2 13.2
Configure a 1+1 Configure a 1+1
protection group. protection group. Change an NE ID.
Change an NE ID.
14 Lock the 1+1 Configure NE
protection group of the Configure NE communication
active devices to the communication parameters.
active unit. parameters.
15 Change an NE
Configure site name.
Change an NE
commissioning
name.
data.
Configure the VLAN
Configure the VLAN ID and bandwidth for
16 inband DCN.
Configure site ID and bandwidth for
commissioning inband DCN. Configure OSPF
data. parameters.
Configure OSPF
17 17 parameters. 17 17
Check alarms. Check alarms. Check alarms. Check alarms. Configure a hop of
Configure a hop of microwave link.
18 microwave link. 18
Check the status Synchronize NE
Check the status
Synchronize NE and receive power time.
and receive power
of the microwave time. of the microwave
links. links.
Required
19 19
Optional Clear forced Clear forced
switchover switchover
No operation command.
command.
1. Power on the active OptiX RTN 380s at both ends according to Powering on the
Equipment and keep the standby OptiX RTN 380s in the off status.
2. Configure commissioning data for the active OptiX RTN 380s at both ends according to
Configuring Site Commissioning Data. At this time, do not configure the microwave 1
+1 protection group (or the link aggregation group used for 1+1 protection if the protection
involves OptiX RTN 900).
3. Check alarms on the active OptiX RTN 380s at both ends according to Checking
Alarms.

4. Align single-polarized antennas according to Aligning Single-Polarized Antennas to

activate microwave links between the active OptiX RTN 380s.
5. Check the status and receive power of the microwave link between the active OptiX RTN
380s according to Checking the Microwave Link Status and Receive Power.
6. Power on the standby OptiX RTN 380 on the far end according to Powering on the
Equipment.
for active/standby equipment on the far end.
NOTE
8. Configure microwave 1+1 protection group data for the active and standby NEs on the
far end (and the link aggregation group used for 1+1 protection if the protection involves
OptiX RTN 900).
9. Forcibly switch the 1+1 protection group of active NEs to the active unit according to A.
5.4 Microwave 1+1 Protection Switching.
for active/standby equipment on the near end.
NOTE
11. Configure microwave 1+1 protection group data for the active and standby NEs on the
near end (and the link aggregation group used for 1+1 protection if the protection involves
OptiX RTN 900).
12. Forcibly switch the 1+1 protection group of active NEs to work at the active unit according
to A.5.4 Microwave 1+1 Protection Switching.

13. Configure commissioning data for the standby OptiX RTN 380 at the far end according to
Configuring Site Commissioning Data.
14. Configure commissioning data for the standby OptiX RTN 380 at the near end according
to Configuring Site Commissioning Data.
15. Check alarms on the active and standby OptiX RTN 380s according to Checking
Alarms.
16. Check the status and receive power of microwave links according to Checking the
Microwave Link Status and Receive Power.
17. Clear forced switchover commands for the main OptiX RTN 380s at the near end and the
far end according to A.5.4 Microwave 1+1 Protection Switching.
3.3 System Commissioning Process

System commissioning refers to the commissioning of an entire microwave transmission
network. System commissioning ensures that various services are transmitted properly and
protection is implemented across the network.
Table 3-2 System commissioning items
6.1 Configuring Network-wide Service Data Required.
6.2 Testing Ethernet 6.2.1 Testing Ethernet Required when Ethernet

Services Services Configured on a services are configured on a
Per NE Basis per NE basis.

6.2.2 Testing Ethernet Required when Ethernet

Services Configured in services are configured in
End-to-End Mode end-to-end mode.
6.3 Testing AMAC Shifting Required.
6.4 Testing Protection Testing ERPS Switching Required.

Switching
6.4.2 Testing 1+1 Required when a microwave
Protection Switching link with 1+1 protection is
configured.
6.5 Checking the Clock Status Required.
6.6 Testing the Fade Margin over a Microwave Link Optional.
6.7 Testing Ethernet 6.7.1 Testing the Latency, Required.

Service Performance Throughput, and Packet
Loss Ratio
6.7.2 Testing the Long-term Required.

Packet Loss Ratio

OptiX RTN 380 Radio Transmission System 4 Site Commissioning (Using a USB Flash Drive to
Commissioning and Configuration Guide Configure Data)
4 Site Commissioning (Using a USB Flash

Drive to Configure Data)
About This Chapter
Site commissioning using a USB flash drive is highly efficient. Prior to site commissioning using
this method, ensure that configuration data stored in the USB flash drive is correct.
The commissioning process is as follows:
4.1 Powering On OptiX RTN 380
Power can be supplied to the OptiX RTN 380 in three modes. You can verify whether the
hardware system and power system are functional by observing the equipment power-on process.
4.2 Loading Commissioning Data Using a USB Flash Drive
While commissioning data is being loaded to an NE using a USB flash drive, NE software is
also upgraded simultaneously.
4.3 Connecting the Web LCT to the Equipment
Properly connecting the Web LCT to the equipment is a prerequisite for configuring
commissioning data for the equipment.
4.4 Creating NEs Using the Search Method
The search method is generally used to create an NE during site commissioning.
4.5 Synchronizing NE Time
Adjust the NE time so that it is synchronized with the time on the Web LCT. This ensures that
the NE accurately records the time when an alarm, a performance event, or an abnormal event
occurs.
4.6 Checking Alarms
Checking alarms generated by equipment helps you to determine whether the equipment is
functioning properly.
4.7 Aligning Antennas
Antenna alignment is the most important activity in site commissioning, as antenna alignment
has a direct effect on microwave link performance.
4.8 Checking the Microwave Link Status and Receive Power

After antenna alignment, check whether the status of a microwave link is normal and whether
the receive power meets requirements.


Context
NOTE
l Power on the equipment within 24 hours of unpacking.

l During maintenance, the power-off time of the equipment cannot be longer than 24 hours.
4.1.1 Powering on OptiX RTN 380 (with an Outdoor PI)

This section describes how to power on OptiX RTN 380 with an outdoor PI. You can verify
whether the OptiX RTN 380 and outdoor PI are functional by observing the equipment power-
on process.
Prerequisites
l The power supply is available. The voltage, polarity, and fuse capacity of the power supply
are correct.
l The power supply (for example, the cabinet power distribution box) is switched off.
l Power cable connections are correct. The polarity is not reversed.
Context
Table 4-1 lists the fuse capacity recommended for OptiX RTN 380.
Table 4-1 Fuse capacity

Chassis Recommended Fuse Capacity
OptiX RTN 380 6A
NOTE
The fuse capacity ranges from 6 A to 12 A in practice.

Precaution
CAUTION
l If the output power voltage of the power supply does not meet test requirements, do not
switch on the power supply and propose corresponding rectification suggestions.
l If any power cable connection is incorrect, rectify the connection before power-on.
Otherwise, the circuit breaker on the power distribution box will be disconnected and even
the power cable may be burnt.
Procedure
Step 1 Connect to the power supply.
OptiX RTN 380
P&E
P&E MGMT
PI (+)(-)
Power supply device
(+)
(-)

Step 2 Verify that the P&E cable and PI power cable are correctly connected. Connect the PI to the
power supply and observe the PI indicators.
Normally, the DC IN and P&E OUT indicators on the PI should be steady green.
NOTE
l If the DC IN indicator is steady green but the P&E OUT indicator blinks green, check whether the P&E
cable or OptiX RTN 380 is short-circuited.
l If the DC IN indicator is steady green and the P&E OUT indicator is off, check whether the P&E cable or
PI is faulty.
Step 3 Observe the system indicator on OptiX RTN 380 to check whether the NE is successfully
powered on.
System indicator
USB/RSSI/NMS
Normally, the system indicator in the USB/RSSI/NMS port on the OptiX RTN 380 should be
steady green.
NOTE
If the system indicator is steady red, check whether the P&E cable or OptiX RTN 380 is faulty.
----End
4.1.2 Powering on OptiX RTN 380 (with an Indoor PI)

This section describes how to power on OptiX RTN 380 with an indoor PI. You can verify
whether the OptiX RTN 380 and indoor PI are functional by observing the equipment power-
on process.

Prerequisites
are correct.
Context

OptiX RTN 380 6A
NOTE
Precaution
CAUTION
Procedure

OptiX RTN 380
P&E
MGMT P&E
PI

Power supply equipment
Blue: -48 V (-)
Black: 0 V ground cable (+)
NOTE
PI is faulty.
powered on.
System indicator
USB/RSSI/NMS
steady green.
NOTE
----End

4.1.3 Powering on OptiX RTN 380 (with a DC Power Supply)

This section describes how to power on OptiX RTN 380 directly with a DC power supply. You
can verify whether the OptiX RTN 380 and DC power system are functional by observing the
equipment power-on process.
Prerequisites
are correct.
Context
OptiX RTN 380 6A
NOTE
Select the fuse capacity according to the DC cable length.
l Select the fuse capacity from 6 A to 12 A if the DC cable length is smaller than 150 m.
l Select the fuse capacity from 6 A to 10 A if he DC cable length ranges from 150 m to 200 m (excluding 200
m).
l Select the fuse capacity 6 A if the DC cable length ranges from 200 m to 300 m.
Precaution
CAUTION
Procedure

OptiX RTN 380
PWR
Step 2 Verify that the DC power cable is correctly connected, switch on the power supply, and view
the system indicator on the OptiX RTN 380 to check whether the NE is successfully powered
on.

System indicator
PWR
Front view
Negative Positive USB/RSSI/NMS
Brown: 0 V ground cable

(+)
(-)
Blue: -48 V
steady green.
NOTE
l If the system indicator is off, check whether the output power voltage and polarity. If the output power
voltage or polarity is incorrect, locate the fault.
l If the system indicator is on red, check whether the OptiX RTN 380 is faulty.
----End
4.1.4 Powering on OptiX RTN 380 (with an Ethernet Board)

This section describes how to power on OptiX RTN 380 through an Ethernet board. You can
verify whether the OptiX RTN 380 and Ethernet board power supply are functional by observing
the equipment power-on process.
Prerequisites
l RTN 900 equipment and its EG4P board have been working normally.

Web LCT

Precaution
CAUTION
Procedure
OptiX RTN 380
P&E
P&E
NMS/COM
3/P1
EG4P
OptiX RTN 950
Interconnection with the OptiX RTN 900

Step 2 Power on the OptiX RTN 900, observe the P&E port indicator (P1 or P2) on the EG4P board
that is connected to the OptiX RTN 380 to check whether the OptiX RTN 380 is successfully
powered on.
System indicator
P&E
USB/RSSI/NMS
NMS/COM
RTN 950
EG4P
EG4P
STAT
STAT
SRV
L/A1
L/A2
L/A3
L/A4
L/A4
SRV
L/A1
L/A2
L/A3
P1
P2
P1
OUT1/IN1 OUT2/IN2 1 2 3/P1 4/P1 P2 OUT1/IN1
OUT2/IN2
1 2 3/P1 4/P1
EG4P
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
OUT1/IN1 1 2 3/P1 4/P1

OUT2/IN2
Power over
L/A3
L/A4
P1
P2
Ethernet indicators
EG4P
3/P1 4/P2
The 3/P1 and 4/P2 ports on the EG4P board provide the Ethernet over power function. In this
example, the 3/P1 port is used. Normally, the L/A3 indicator on the EG4P board of the OptiX
RTN 900 should be on green or blink yellow and the P1 indicator on the EG4P board should be
on green. Normally, the system indicator in the USB/RSSI/NMS port on the OptiX RTN
380should be steady green.
If... Then...
The P1 indicator on the EG4P board is off Perform Step 3 to check whether the power
over Ethernet function is enabled on the EG4P
board.
The L/A3 indicator on the EG4P board is off Check whether the P&E cable or OptiX RTN
900 is faulty.
The system indicator on the OptiX RTN Check whether the P&E cable or OptiX RTN
380 is on red 380 is faulty.
Step 3 Connect the Web LCT to the OptiX RTN 900, enable the power over Ethernet function for the
port on the EG4P board that is connected to the OptiX RTN 380 by using the Web LCT.
1. In NE Explorer, select the desired NE from the object tree and choose Configuration >
Interface Management > Ethernet Interface from Function Tree.
2. Click the Advanced Attributes tab.

3. Set PoE to Enabled for the port on the EG4P board that is connected to the OptiX RTN
380.
4. Click Apply.
----End
4.2 Loading Commissioning Data Using a USB Flash Drive

While commissioning data is being loaded to an NE using a USB flash drive, NE software is
also upgraded simultaneously.
Prerequisites
l The NE has been powered on.
l Commissioning data has been loaded onto a USB flash drive.
l The authentication certificate on the USB flash drive is correct.

USB flash drive
Procedure
Step 1 Remove the metal protector from the USB/RSSI/NMS port.
Step 2 Insert the USB flash drive into the USB port.
USB/RSSI/NMS (bottom view)
USB System
indicator indicator
USB
interface
USB/RSSI/NMS
Step 3 Observe the USB indicator to check the data loading status.

Status of the USB Data Loading Status Operation

Indicator
The USB indicator blinks The loading of Remove the USB flash drive.
green, goes off, blinks green, commissioning data is
and turns steady green. complete.
NOTE
l Do not remove the USB
flash drive while the USB
indicator is blinking green.
If the USB flash drive is
removed, the data loading
will be interrupted.
l When data is being loaded
from the USB flash drive,
the USB indicator blinks
green for the first time.
After the data loading is
complete, the NE
automatically resets, which
takes 2 minutes to 3
minutes, and the USB
indicator goes off. After the
reset is complete, the USB
indicator blinks green
again. Finally, the USB
indicator and the system
indicator on the NE are both
steady green, indicating
that the data loading is
successful.
l If only the script files are
loaded using the USB flash
drive, the USB indicator
blinks green for 1 second to
2 seconds and then the NE
resets automatically. In this
case, you may fail to notice
that the USB indicator has
blinked green because the
blinking duration is too
short.
l If the script files and
software package are
loaded using the USB flash
drive, the loading process
may last more than 10
minutes.
The USB indicator turns off The USB flash drive is faulty l Copy the commissioning
after the USB flash drive is and has failed to go online. data to another USB flash
inserted. NOTE drive.
Another possible cause is that l Repeat Step 2 to load the
the USB flash drive is not
data to the NE.
properly inserted.

Status of the USB Data Loading Status Operation

Indicator
The USB indicator blinks An incorrect model of USB l Copy the commissioning
red. flash drive has been inserted, data to another USB flash
or an error has occurred when drive of the correct
the NE attempted to read/ model.
write the USB flash drive. l Repeat Step 2 to load the
NOTE data to the NE.
2.3 Preparing a USB Flash
Drive provides the model of
USB flash drive supported by
OptiX RTN 380.
The USB indicator is steady The loaded data is incorrect. Handle the fault by following
red. instructions in 7.1 When a
USB Flash Drive Is Used
for Loading
Commissioning Data, Some
Commands Fail to Be
Loaded.
----End

Prerequisites
OptiX RTN 380s have been powered on.
NOTE
When a USB flash drive is used for data configuration, connect the Web LCT to only one end of the microwave
link.

Web LCT
Procedure
Step 1 Start the laptop and log in to the operating system.
Step 2 Set the IP address of the laptop.
The IP address must meet the following requirements:
l The IP address is in the same network segment (the default network segment is 129.9.0.0)
as the NE IP address, but is different from the NE IP address.

l The subnet mask is the same as that for the NE IP address (the default subnet mask is
255.255.0.0).
l The default gateway IP address is blank.
Step 3 Connect the Web LCT to an OptiX RTN 380 in an appropriate way based on the site
configuration. For details, see Figure 4-1.
CAUTION
Ensure that each fiber/cable is properly connected to the correct port. Otherwise, the equipment
or the tool may be damaged.
Figure 4-1 Ways for connecting the Web LCT to an OptiX RTN 380
P&E P&E
P&E USB/RSSI/NMS
NMS/COM
MGMT P&E
4/P2
NMS
Fiber
To NodeB
MGMT
P&E
EG4P
A network consisting of only the A network consisting of both the A network consisting of only the
OptiX RTN 380s (using PI) OptiX RTN380s and the OptiX RTN 900s OptiX RTN 380s
NOTE
l If a site has several cascaded OptiX RTN 380s, connect the laptop to only one of the OptiX RTN 380s.
l Use either a crossover cable or a straight-through cable to connect the laptop to the OptiX RTN 380. For
the wire sequences of crossover cables and straight-through cables, see Cable in the OptiX RTN 380
Microwave Transmission System Product Description.
After the Web LCT and the OptiX RTN 380 are properly connected, the indicator at the Ethernet
port of the laptop is steady green. A message is displayed indicating that the network has
established a local connection if the operating system has been configured to do so. If the
operating system displays a message indicating an IP address conflict, change the IP address of
the laptop.
Step 4 On the desktop, double-click the Start Web LCT icon.
The system displays the USER LOGIN window of the Web LCT.

Step 5 Set User Name, Password, and Verification Code, and click Login.
l User Name: admin
l Password: Changeme_123
NOTE
At the first login to the Web LCT, change the password as prompted.
If the entered user name and password are correct, the NE List page is displayed.
----End
Follow-up Procedure
l If a site has only OptiX RTN 380s and no PI is configured, remove the P&E cable from
the OptiX RTN 380 after the commissioning is complete.
l If you cannot access the USER LOGIN window or the NE List page, configure the Internet
Explorer using the following method:


Prerequisites
l The Web LCT is communicating properly with NEs.
l The NE user has Operation Level rights or higher.

Web LCT
Context
The following procedure:
l Searches for NEs using the NE Search method if the NEs are connected directly to the
Web LCT using Ethernet cables.
l Searches for NEs using the IP auto discovery method if the site has multiple NEs.
Procedure
Step 1 Search for NEs using the NE Search method if the NEs are connected directly to the Web LCT
using Ethernet cables.

Step 2 Search for NEs using the IP auto discovery method if the site has multiple NEs.
----End
4.5 Synchronizing NE Time

occurs.
Prerequisites
l The basic data of all NEs on the network has been configured.
l Time settings on the Web LCT are correct.
l You must be an NM user with NE operator authority or higher.

Web LCT

Context
The following procedure synchronizes the NE time with the Web LCT time.
Procedure
Step 1 Synchronize the NE time with the Web LCT time.
----End
4.6 Checking Alarms

Prerequisites
l The Web LCT has been connected to the equipment.
l Basic data has been configured for the equipment.

Web LCT
Context
The following procedure checks the alarms on an NE.
Procedure
Step 1 Check alarms.

----End

4.7.1 Main Lobe and Side Lobes

Before aligning antennas, engineers must be familiar with the following concepts regarding the
main lobe and side lobes.
Definition
The electric field strength of the radiated power of an antenna varies in space. The differences
of the power distribution can be shown in an azimuth diagram. Generally, there are two azimuth
diagrams illustrating the horizontal and vertical sections. These are the horizontal azimuth
diagram and vertical azimuth diagram. Figure 4-2 is a vertical azimuth diagram showing many
lobes. The lobe with the strongest radiated power is the main lobe, while the others are side
lobes. The first side lobe can be used for aligning the antenna.
Figure 4-2 Main lobe and side lobes
Main lobe
First side lobe
Second side lobe
Locating of the Main Lobe

Antenna alignment aligns the main lobe of the local antenna with the main lobe of the opposite
antenna, to achieve the maximum received signal strength at the opposite antenna.

The main lobe width of a microwave antenna is narrow, specifically, between 0.6° and 3.7°. For
instance, in the case of a 1.2 m antenna at a working frequency of 23 GHz, the azimuth is only
0.9° when the signal level drops from the signal peak to zero. Once a signal is detected, very
small alignment adjustments are required to locate the main lobe.
Antenna movement across the main lobe results in a rapid rise and drop in the signal level.
Whether the main lobe is aligned properly can be verified by comparing the received signal
peaks. Typically, the main lobe signal peak is 20-25 dB higher than the first side lobe signal
peak.
Figure 4-3 shows the head-on view of a free-space model for radio propagation with concentric
rings of side lobe peaks and troughs radiating outward from the main lobe.
Figure 4-3 Horizontal section and front view of the antenna

180o
90o
0o
Center of the main lobe

Outer edge of the main lobe, 3 to
10 dB lower than the main lobe
180o
Trough between the main lobe
and the first side lobe, 30 dB
lower than the main lobe
First side lobe, 20-25 dB
90o lower than the main lobe
Trough between the first side lobe
and the second side lobe, 30 dB or
more lower than the main lobe
0o Second side lobe, where
signals are very weak
a Horizontal section b Head-on
of the antenna view
Tracking Path
Side lobe signal readings are sometimes mistaken for main lobe readings when signals are
tracked on different elevations (or azimuths). Figure 4-4 shows a horizontal radio propagation
model of an antenna, and signal levels at three different elevation positions (1-7 represent the
measured signal level values of the received signal strength indicator [RSSI] port of the OptiX
RTN 380).

Figure 4-4 Three tracking paths

Head-on view of tracking paths for
different elevations Signal level for each path
6 7
C C'
C 6 7 C' 5
4
4 5
B B'
B B'
1 2 3
A A'
2
1 3
A A'
l Line AA' indicates that the main lobe of the antenna is almost aligned properly. The main
lobe is at point 2, and the first side lobes are at points 1 and 3. Slightly adjust the azimuth
of the antenna at point 2 until the peak signal appears.
l Line BB' indicates that the elevation of the antenna slightly deviates from the main lobe.
The signal peaks appear at points 4 and 5. The signal peak at point 4 is higher than the
signal peak at point 5 because of the antenna characteristics. As a result, point 4 may be
mistaken for the peak point of the main lobe signal. The correct method is to set the azimuth
of the antenna to the middle position between the two signal peaks. Then, adjust the
elevation of the antenna until the three signal peaks of line AA' appear. Slightly adjust the
elevation and azimuth of the antenna at point 2 until the peak signal appears.
l Line CC' indicates that the elevation of the antenna completely deviates from the main lobe
and is almost aligned with the first side lobe. The signal peak of the first side lobe at point
6 and the signal peak of the first side lobe at point 7 appear as one signal peak. As a result,
points 6 and 7 may be mistaken for the peak point of the main lobe signal. The correct
method is to set the azimuth of the antenna to the middle of points 6 and 7. Then, adjust
the elevation of the antenna until the three signal peaks of line AA' appear. Slightly adjust
the elevation and azimuth of the antenna at point 2 until the peak signal appears.
When the side lobe peak on one side is higher than the side lobe peak at the other side, as shown
in Figure 4-5, a common error is moving the antenna from left to right along line DD', or top
to bottom along line EE'. As a result, point 1 may be mistaken for the peak point of the main
lobe signal. The correct method is to adjust the elevation in the middle of points 1 and 2 or the
azimuth in the middle of points 1 and 3. Several adjustments are required to ensure that the three
signal peaks of line AA' can appear. Slightly adjust the elevation and azimuth of the antenna at
point 2 as shown in Figure 4-4 until the peak signal appears.
Figure 4-5 Aligning the antenna with the first side lobe
E
1
2
D D'
1 2
D D'
1
3
3
E E'
E'

4.7.2 Aligning Single-Polarized Antennas

When aligning single-polarized antennas, align the main lobes by adjusting the azimuth and
elevation of the antennas at both ends.
Prerequisites
l The preceding site commissioning items have been completed at both ends of a microwave
link.
l The weather conditions at both ends are suitable for outdoor operations, and there is no
threat of rain, snow, fog or other unfavorable conditions that could interfere with the
procedure.
l A properly calibrated multimeter is available.
l The automatic transmit power control (ATPC) function has been disabled (this function is
disabled by default).
l The adaptive modulation (AM) function has been disabled (this function is disabled by
default).

l Adjustable wrench
l Interphone
l Hex key (delivered with antennas)
l North-stabilized indicator
l Telescope
l Multimeter
l Received signal strength indicator (RSSI) test cables (delivered with OptiX RTN 380)
CAUTION
You can change the azimuth and elevation of the antennas by adjusting the nuts or screws. For
details, see the antenna installation guide. Steps provided in this section are for reference only.
Procedure
Step 1 Calculate the voltage value (VBNC) for the RSSI port corresponding to the planned received
signal level (RSL) based on the RSSI and RSL curves.
NOTE
The curve diagram for VBNC and RSL is delivered along with the OptiX RTN 380.
Step 2 Determine the azimuth of the antenna at the local end based on the installation position and
height of the antenna. Then, adjust the elevation of the antenna to the horizontal position.

NOTE
For a special microwave link (for example, a microwave link with one end on a mountain top and the other end
at the foot of the mountain), the inclination between the link and the horizontal line is greater than the half-power
angle of the antenna. Slightly adjust the elevation of the antenna so the main lobes are aligned vertically.
Step 3 Connect a multimeter to the RSSI port on the OptiX RTN 380 at the local end using an RSSI
test fiber and test the voltage value VBNC. Turn the multimeter to the DC power level with the
voltage value 20 V.
TIP
It is recommended that you fix the multimeter to the tower with adhesive tape at your plain view, so that
you can observe the RSSI voltage value while aligning antennas.
Figure 4-6 Testing the RSSI voltage using a multimeter
USB/RSSI/NMS
USB RSSI
Step 4 Adjust the azimuth and elevation of the antenna as follows:

1. Keep the remote antenna fixed.
2. Loosen the antenna brackets, rotate the antenna horizontally within a large range, and
observe the value of VBNC on the multimeter. When the value is not 0, secure the antenna
brackets.
3. Loosen the fine adjustment bolts, rotate the antenna horizontally, and observe the peak
values of VBNC on the multimeter.
Normally, three signal peaks are tracked, as shown in Figure 4-7.
Figure 4-7 Signal peaks

2
1 3

CAUTION
If the number of tracked signal peaks is fewer than three, even after a wide rotation and
careful observation of the multimeter, refer to 4.7.1 Main Lobe and Side Lobes for help
with handling the exception.
4. Adjust the antenna azimuth until the signal strength reaches position 2 shown in Figure
4-7. When the signal strength is at position 2, the value of VBNC is the peak value.
5. Slightly adjust the elevation and azimuth at point 2 until VBNC reaches the peak value within
the tracked range.
6. Secure the antenna at the local end.
NOTE
When securing the antenna, ensure that VBNC remains at the peak value.
Step 5 Repeat Step 2 to Step 4 to adjust the antenna at the remote end. When VBNC reaches the peak
value, secure the antenna at the remote end.
Step 6 Repeat Step 2 to Step 4 for two to four times. When VBNC at the local end and VBNC at the
remote end reach the peak value, secure the antennas at both ends.
NOTE
l Perform slight adjustments in this step.

l After the adjustments are complete and antennas at both ends are secured, the VBNC value must reach or
exceed the VBNC value obtained in Step 1.
----End

Prerequisites
l Antennas have been aligned.
l The basic data of NEs on the entire network has been configured.
l You must be an NM user with NE maintainer authority or higher.

Web LCT
Context
The following procedure checks the microwave link status and receive power.
Procedure
Step 1 Check the microwave link status and receive power.

NOTE
If the receive power does not meet design requirements, handle the fault by following instructions in 7.2
The Receive Power Does not Meet the Design Requirements.
----End

OptiX RTN 380 Radio Transmission System 5 Site Commissioning (Using the Web LCT to Configure
Commissioning and Configuration Guide Data)
5 Site Commissioning (Using the Web LCT to

Configure Data)
About This Chapter
Site commissioning using the Web LCT requires that commissioning engineers be capable of
configuring NE data.
The commissioning process is as follows:
5.4 Configuring Site Commissioning Data
During site commissioning, you do not need to configure Ethernet service data. By default, the
NE creates an IEEE 802.1D bridge-based Ethernet local area network (E-LAN) service for
transmitting Ethernet services.
5.5 Checking Alarms


Context
NOTE
l Power on the equipment within 24 hours of unpacking.

l During maintenance, the power-off time of the equipment cannot be longer than 24 hours.
5.1.1 Powering on OptiX RTN 380 (with an Outdoor PI)

This section describes how to power on OptiX RTN 380 with an outdoor PI. You can verify
whether the OptiX RTN 380 and outdoor PI are functional by observing the equipment power-
on process.
Prerequisites
are correct.
Context

OptiX RTN 380 6A
NOTE

Precaution
CAUTION
Procedure
OptiX RTN 380
P&E
P&E MGMT
PI (+)(-)
Power supply device
(+)
(-)

NOTE
PI is faulty.
powered on.
System indicator
USB/RSSI/NMS
steady green.
NOTE
----End
5.1.2 Powering on OptiX RTN 380 (with an Indoor PI)

This section describes how to power on OptiX RTN 380 with an indoor PI. You can verify
whether the OptiX RTN 380 and indoor PI are functional by observing the equipment power-
on process.

Prerequisites
are correct.
Context

OptiX RTN 380 6A
NOTE
Precaution
CAUTION
Procedure

OptiX RTN 380
P&E
MGMT P&E
PI

Blue: -48 V (-)
Black: 0 V ground cable (+)
NOTE
PI is faulty.
powered on.
System indicator
USB/RSSI/NMS
steady green.
NOTE
----End

5.1.3 Powering on OptiX RTN 380 (with a DC Power Supply)

This section describes how to power on OptiX RTN 380 directly with a DC power supply. You
can verify whether the OptiX RTN 380 and DC power system are functional by observing the
equipment power-on process.
Prerequisites
are correct.
Context
OptiX RTN 380 6A
NOTE
Select the fuse capacity according to the DC cable length.
l Select the fuse capacity from 6 A to 12 A if the DC cable length is smaller than 150 m.
l Select the fuse capacity from 6 A to 10 A if he DC cable length ranges from 150 m to 200 m (excluding 200
m).
l Select the fuse capacity 6 A if the DC cable length ranges from 200 m to 300 m.
Precaution
CAUTION
Procedure

OptiX RTN 380
PWR
Step 2 Verify that the DC power cable is correctly connected, switch on the power supply, and view
the system indicator on the OptiX RTN 380 to check whether the NE is successfully powered
on.

System indicator
PWR
Front view
Negative Positive USB/RSSI/NMS
Brown: 0 V ground cable

(+)
(-)
Blue: -48 V
steady green.
NOTE
l If the system indicator is off, check whether the output power voltage and polarity. If the output power
voltage or polarity is incorrect, locate the fault.
l If the system indicator is on red, check whether the OptiX RTN 380 is faulty.
----End
5.1.4 Powering on OptiX RTN 380 (with an Ethernet Board)

This section describes how to power on OptiX RTN 380 through an Ethernet board. You can
verify whether the OptiX RTN 380 and Ethernet board power supply are functional by observing
the equipment power-on process.
Prerequisites
l RTN 900 equipment and its EG4P board have been working normally.

Web LCT

Precaution
CAUTION
Procedure
OptiX RTN 380
P&E
P&E
NMS/COM
3/P1
EG4P
OptiX RTN 950
Interconnection with the OptiX RTN 900

Step 2 Power on the OptiX RTN 900, observe the P&E port indicator (P1 or P2) on the EG4P board
that is connected to the OptiX RTN 380 to check whether the OptiX RTN 380 is successfully
powered on.
System indicator
P&E
USB/RSSI/NMS
NMS/COM
RTN 950
EG4P
EG4P
STAT
STAT
SRV
L/A1
L/A2
L/A3
L/A4
L/A4
SRV
L/A1
L/A2
L/A3
P1
P2
P1
OUT1/IN1 OUT2/IN2 1 2 3/P1 4/P1 P2 OUT1/IN1
OUT2/IN2
1 2 3/P1 4/P1
EG4P
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
OUT1/IN1 1 2 3/P1 4/P1

OUT2/IN2
Power over
L/A3
L/A4
P1
P2
Ethernet indicators
EG4P
3/P1 4/P2
The 3/P1 and 4/P2 ports on the EG4P board provide the Ethernet over power function. In this
example, the 3/P1 port is used. Normally, the L/A3 indicator on the EG4P board of the OptiX
RTN 900 should be on green or blink yellow and the P1 indicator on the EG4P board should be
on green. Normally, the system indicator in the USB/RSSI/NMS port on the OptiX RTN
380should be steady green.
If... Then...
The P1 indicator on the EG4P board is off Perform Step 3 to check whether the power
over Ethernet function is enabled on the EG4P
board.
The L/A3 indicator on the EG4P board is off Check whether the P&E cable or OptiX RTN
900 is faulty.
The system indicator on the OptiX RTN Check whether the P&E cable or OptiX RTN
380 is on red 380 is faulty.
Step 3 Connect the Web LCT to the OptiX RTN 900, enable the power over Ethernet function for the
port on the EG4P board that is connected to the OptiX RTN 380 by using the Web LCT.
1. In NE Explorer, select the desired NE from the object tree and choose Configuration >
Interface Management > Ethernet Interface from Function Tree.
2. Click the Advanced Attributes tab.

3. Set PoE to Enabled for the port on the EG4P board that is connected to the OptiX RTN
380.
4. Click Apply.
----End

Prerequisites
NOTE
link.

Web LCT
Procedure
255.255.0.0).
configuration. For details, see Figure 5-1.
CAUTION

Figure 5-1 Ways for connecting the Web LCT to an OptiX RTN 380
P&E P&E
P&E USB/RSSI/NMS
NMS/COM
MGMT P&E
4/P2
NMS
Fiber
To NodeB
MGMT
P&E
EG4P
NOTE
the laptop.


l User Name: admin

NOTE
----End
Follow-up Procedure

Prerequisites
l The Web LCT is communicating properly with NEs.

l The NE user has Operation Level rights or higher.

Web LCT
Context
l Searches for NEs using the NE Search method if the NEs are connected directly to the
Web LCT using Ethernet cables.
l Searches for NEs using the IP auto discovery method if the site has multiple NEs.
Procedure
Step 1 Search for NEs using the NE Search method if the NEs are connected directly to the Web LCT
using Ethernet cables.
Step 2 Search for NEs using the IP auto discovery method if the site has multiple NEs.
----End

5.4 Configuring Site Commissioning Data

During site commissioning, you do not need to configure Ethernet service data. By default, the
NE creates an IEEE 802.1D bridge-based Ethernet local area network (E-LAN) service for
transmitting Ethernet services.
5.4.1 Changing an NE ID
Change the NE ID according to the engineering plan to ensure that each NE ID is unique. This
task does not interrupt services.
Prerequisites
You must be an NM user with NE operator authority or higher.

U2000
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The following procedure changes an NE ID to the planned value listed in the following table.
Parameter Value
New ID 320
After changing the NE ID, you need to restart the NE.
Procedure
Step 1

----End
5.4.2 Setting NE Communication Parameters

NE communication parameters include the NE IP address, gateway IP address, and subnet mask.
Prerequisites

U2000
NOTE
Precautions
If multiple parameters need to be set, click Apply after setting each parameter.
Context
The following procedure sets the IP address and subnet mask of an NE to the planned values
listed in the following table.
Parameter Value
IP Address 129.9.0.1
Subnet Mask 255.255.0.0
Procedure
Step 1

----End
5.4.3 Changing an NE Name

For easier identification of an NE in Main Topology, name the NE according to its geographical
location or the device to which it is connected.
Prerequisites

U2000
NOTE
Context
The following procedure changes an NE name to the planned value listed in the following table.
Parameter Value
Name Site2-1
Procedure
Step 1

----End
5.4.4 Setting the VLAN ID and Bandwidth for an Inband DCN

The VLAN ID used by an inband data communication network (DCN) must be different from
the VLAN ID used by services. The bandwidth of an inband DCN must meet the requirements
of the transmission network for managing messages.
Prerequisites
You must be an NM user with NE administrator authority or higher.

U2000
NOTE
Context
The following procedure sets the VLAN ID and bandwidth to the planned values listed in the
following table for an inband DCN.
Parameter Value
VLAN ID 4092
Bandwidth(Kbit/s) 512Kbit/s
Procedure
Step 1

----End
5.4.5 Setting OSPF Protocol Parameters

When the OptiX RTN equipment is interconnected with third-party equipment, routing protocol
interaction works properly after you set Open Shortest Path First (OSPF) protocol parameters
of the OptiX RTN equipment based on related requirements of the third-party equipment.
Prerequisites

U2000
NOTE
Context
The following procedure configures OSPF parameters according to the planned parameter values
Parameter Value
Area 0.0.0.1
OSPF Status Enabled
Static route Enabled
LAN Interface Disabled

Procedure
Step 1
----End
5.4.6 Creating a LAG

If the bandwidth or availability of the Ethernet link between two NEs needs to be improved,
create a link aggregation group (LAG).
Prerequisites

U2000
NOTE
Context
l Creates a non-load sharing LAG to protect the Ethernet link from a UNI-side equipment
to an NE, according to the planned parameter values listed in the following table.
Parameter NE
LAG No. Assign Automatically
LAG Name LAG_01
LAG Type Static (default value)
Load Sharing Non-Sharing
LAG Priority 32768 (default value)

Parameter NE
Packet Receive Timeout Period Long period
Main Ports 1-SHUF3-3 (GE2)
Standby Ports 1-SHUF3-2 (GE1)
l Creates a load-sharing LAG to increase the Ethernet bandwidth for a link between air
interfaces, according to the planned parameter values listed in the following table.
Parameter NE
LAG Name LAG_02
Load Sharing Sharing
LAG Min Active Link Threshold 1
Main Ports 1-SHUF3-1 (IF)
Switch LAG upon Air Interface SD Enabled
l Create a LAG for configuring 1+1 protection according to the planned parameter values
Parameter NE
LAG No. Assign Automatically (default value).
LAG type Static (default value)
Load sharing type Non-load sharing (default value)
LAG priority 32768 (default value)
Main port 1-SHUF3-2 (GE1)
Procedure
Step 1 Create a non-load sharing LAG.

Step 2 Create a load-sharing LAG.
Step 3 Create a LAG for configuring 1+1 protection with NE-level protection.
----End

5.4.7 Creating a Microwave 1+1 Protection Group

If microwave links are configured with 1+1 hot standby (HSB) protection, you need to create a
corresponding microwave 1+1 protection group.
Prerequisites
l If no optical splitter is used when 1+1 HSB is configured, E-LAG needs to be configured.
l The COMBO ports on the active and standby OptiX RTN 380s are connected using an
optical fiber.

U2000
Context
The following procedure
l creates a microwave 1+1 protection group in LAG Mode according to planned values
provided in the following table.
Parameter Value
Service Protection Type LAG Mode
Reversion Mode Revertive
WTR Time (s) 600 (default value)
Enable Reverse Switching Enable
Working/Protection Unit Type Working Unit
Service Port 1-SHUF3-2(GE1)
l creates a microwave 1+1 protection group in Split Mode according to planned values
Parameter Value

Procedure
Step 1 Create a microwave 1+1 protection group in LAG Mode.
Step 2 Create a microwave 1+1 protection group in Split Mode.
----End
5.4.8 Configuring a Single Hop of Microwave Link

By performing this task, you can set the basic attributes for the local NE and the peer NE on a
single hop of microwave link.
Prerequisites
l The sites at the two ends of a microwave link hop are communicating properly.

U2000

NOTE
Precautions
The following parameters of the NEs on a hop of microwave link are automatically synchronized:
Link ID, IF Channel Bandwidth, , AMAC, Guaranteed AMAC Capacity, Full AMAC
Capacity, Modulation Mode, T/R Spacing(MHz), and ATPC. That is, if one of the preceding
parameters is modified on an NE, the modification is automatically duplicated on the peer NE.
Context
The following procedure configures basic information for the hop of microwave link shown in
the following figure by configuring NE1.
The planned parameter values are listed in the following table.
Parameter Link
NE ID 9-38412(Local Radio Terminal)

9-20038(Opposite Radio Terminal)
Link ID 2
IF Channel Bandwidth 250MHz
AMAC Disabled
Modulation Mode 16QAM
TX Frequency(MHz) 73500
T/R Spacing (MHz) 10000
ATPC Disabled
TX power (dBm) 10
Power to Be Frequency(dBm) -40
TX Status unmute
Antenna Polarization Direction V
Procedure
Step 1

----End
5.4.9 Synchronizing NE Time

occurs.
Prerequisites
l The basic data of all NEs on the network has been configured.
l Time settings on the Web LCT are correct.

Web LCT
Context
The following procedure synchronizes the NE time with the Web LCT time.
Procedure
Step 1 Synchronize the NE time with the Web LCT time.

----End
5.5 Checking Alarms

Prerequisites
l The Web LCT has been connected to the equipment.
l Basic data has been configured for the equipment.

Web LCT
Context
The following procedure checks the alarms on an NE.
Procedure
Step 1 Check alarms.

----End

5.6.1 Main Lobe and Side Lobes

Before aligning antennas, engineers must be familiar with the following concepts regarding the
main lobe and side lobes.
Definition
The electric field strength of the radiated power of an antenna varies in space. The differences
of the power distribution can be shown in an azimuth diagram. Generally, there are two azimuth
diagrams illustrating the horizontal and vertical sections. These are the horizontal azimuth
diagram and vertical azimuth diagram. Figure 5-2 is a vertical azimuth diagram showing many
lobes. The lobe with the strongest radiated power is the main lobe, while the others are side
lobes. The first side lobe can be used for aligning the antenna.
Figure 5-2 Main lobe and side lobes
Main lobe
First side lobe
Second side lobe
Locating of the Main Lobe

Antenna alignment aligns the main lobe of the local antenna with the main lobe of the opposite
antenna, to achieve the maximum received signal strength at the opposite antenna.

The main lobe width of a microwave antenna is narrow, specifically, between 0.6° and 3.7°. For
instance, in the case of a 1.2 m antenna at a working frequency of 23 GHz, the azimuth is only
0.9° when the signal level drops from the signal peak to zero. Once a signal is detected, very
small alignment adjustments are required to locate the main lobe.
Antenna movement across the main lobe results in a rapid rise and drop in the signal level.
Whether the main lobe is aligned properly can be verified by comparing the received signal
peaks. Typically, the main lobe signal peak is 20-25 dB higher than the first side lobe signal
peak.
Figure 5-3 shows the head-on view of a free-space model for radio propagation with concentric
rings of side lobe peaks and troughs radiating outward from the main lobe.
Figure 5-3 Horizontal section and front view of the antenna

180o
90o
0o
Center of the main lobe

Outer edge of the main lobe, 3 to
10 dB lower than the main lobe
180o
Trough between the main lobe
and the first side lobe, 30 dB
lower than the main lobe
First side lobe, 20-25 dB
90o lower than the main lobe
Trough between the first side lobe
and the second side lobe, 30 dB or
more lower than the main lobe
0o Second side lobe, where
signals are very weak
a Horizontal section b Head-on
of the antenna view
Tracking Path
Side lobe signal readings are sometimes mistaken for main lobe readings when signals are
tracked on different elevations (or azimuths). Figure 5-4 shows a horizontal radio propagation
model of an antenna, and signal levels at three different elevation positions (1-7 represent the
measured signal level values of the received signal strength indicator [RSSI] port of the OptiX
RTN 380).

Figure 5-4 Three tracking paths

Head-on view of tracking paths for
different elevations Signal level for each path
6 7
C C'
C 6 7 C' 5
4
4 5
B B'
B B'
1 2 3
A A'
2
1 3
A A'
l Line AA' indicates that the main lobe of the antenna is almost aligned properly. The main
lobe is at point 2, and the first side lobes are at points 1 and 3. Slightly adjust the azimuth
of the antenna at point 2 until the peak signal appears.
l Line BB' indicates that the elevation of the antenna slightly deviates from the main lobe.
The signal peaks appear at points 4 and 5. The signal peak at point 4 is higher than the
signal peak at point 5 because of the antenna characteristics. As a result, point 4 may be
mistaken for the peak point of the main lobe signal. The correct method is to set the azimuth
of the antenna to the middle position between the two signal peaks. Then, adjust the
elevation of the antenna until the three signal peaks of line AA' appear. Slightly adjust the
elevation and azimuth of the antenna at point 2 until the peak signal appears.
l Line CC' indicates that the elevation of the antenna completely deviates from the main lobe
and is almost aligned with the first side lobe. The signal peak of the first side lobe at point
6 and the signal peak of the first side lobe at point 7 appear as one signal peak. As a result,
points 6 and 7 may be mistaken for the peak point of the main lobe signal. The correct
method is to set the azimuth of the antenna to the middle of points 6 and 7. Then, adjust
the elevation of the antenna until the three signal peaks of line AA' appear. Slightly adjust
the elevation and azimuth of the antenna at point 2 until the peak signal appears.
When the side lobe peak on one side is higher than the side lobe peak at the other side, as shown
in Figure 5-5, a common error is moving the antenna from left to right along line DD', or top
to bottom along line EE'. As a result, point 1 may be mistaken for the peak point of the main
lobe signal. The correct method is to adjust the elevation in the middle of points 1 and 2 or the
azimuth in the middle of points 1 and 3. Several adjustments are required to ensure that the three
signal peaks of line AA' can appear. Slightly adjust the elevation and azimuth of the antenna at
point 2 as shown in Figure 5-4 until the peak signal appears.
Figure 5-5 Aligning the antenna with the first side lobe
E
1
2
D D'
1 2
D D'
1
3
3
E E'
E'

5.6.2 Aligning Single-Polarized Antennas

When aligning single-polarized antennas, align the main lobes by adjusting the azimuth and
elevation of the antennas at both ends.
Prerequisites
l The preceding site commissioning items have been completed at both ends of a microwave
link.
l The weather conditions at both ends are suitable for outdoor operations, and there is no
threat of rain, snow, fog or other unfavorable conditions that could interfere with the
procedure.
l A properly calibrated multimeter is available.
l The automatic transmit power control (ATPC) function has been disabled (this function is
disabled by default).
l The adaptive modulation (AM) function has been disabled (this function is disabled by
default).

l Adjustable wrench
l Interphone
l Hex key (delivered with antennas)
l North-stabilized indicator
l Telescope
l Multimeter
l Received signal strength indicator (RSSI) test cables (delivered with OptiX RTN 380)
CAUTION
You can change the azimuth and elevation of the antennas by adjusting the nuts or screws. For
details, see the antenna installation guide. Steps provided in this section are for reference only.
Procedure
Step 1 Calculate the voltage value (VBNC) for the RSSI port corresponding to the planned received
signal level (RSL) based on the RSSI and RSL curves.
NOTE
The curve diagram for VBNC and RSL is delivered along with the OptiX RTN 380.
Step 2 Determine the azimuth of the antenna at the local end based on the installation position and
height of the antenna. Then, adjust the elevation of the antenna to the horizontal position.

NOTE
For a special microwave link (for example, a microwave link with one end on a mountain top and the other end
at the foot of the mountain), the inclination between the link and the horizontal line is greater than the half-power
angle of the antenna. Slightly adjust the elevation of the antenna so the main lobes are aligned vertically.
Step 3 Connect a multimeter to the RSSI port on the OptiX RTN 380 at the local end using an RSSI
test fiber and test the voltage value VBNC. Turn the multimeter to the DC power level with the
voltage value 20 V.
TIP
It is recommended that you fix the multimeter to the tower with adhesive tape at your plain view, so that
you can observe the RSSI voltage value while aligning antennas.
Figure 5-6 Testing the RSSI voltage using a multimeter
USB/RSSI/NMS
USB RSSI
Step 4 Adjust the azimuth and elevation of the antenna as follows:

1. Keep the remote antenna fixed.
2. Loosen the antenna brackets, rotate the antenna horizontally within a large range, and
observe the value of VBNC on the multimeter. When the value is not 0, secure the antenna
brackets.
3. Loosen the fine adjustment bolts, rotate the antenna horizontally, and observe the peak
values of VBNC on the multimeter.
Normally, three signal peaks are tracked, as shown in Figure 5-7.
Figure 5-7 Signal peaks

2
1 3

CAUTION
If the number of tracked signal peaks is fewer than three, even after a wide rotation and
careful observation of the multimeter, refer to 4.7.1 Main Lobe and Side Lobes for help
with handling the exception.
4. Adjust the antenna azimuth until the signal strength reaches position 2 shown in Figure
5-7. When the signal strength is at position 2, the value of VBNC is the peak value.
5. Slightly adjust the elevation and azimuth at point 2 until VBNC reaches the peak value within
the tracked range.
6. Secure the antenna at the local end.
NOTE
When securing the antenna, ensure that VBNC remains at the peak value.
Step 5 Repeat Step 2 to Step 4 to adjust the antenna at the remote end. When VBNC reaches the peak
value, secure the antenna at the remote end.
Step 6 Repeat Step 2 to Step 4 for two to four times. When VBNC at the local end and VBNC at the
remote end reach the peak value, secure the antennas at both ends.
NOTE
l Perform slight adjustments in this step.

l After the adjustments are complete and antennas at both ends are secured, the VBNC value must reach or
exceed the VBNC value obtained in Step 1.
----End

Prerequisites
l The basic data of NEs on the entire network has been configured.

Web LCT
Context
The following procedure checks the microwave link status and receive power.
Procedure
Step 1 Check the microwave link status and receive power.

NOTE
If the receive power does not meet design requirements, handle the fault by following instructions in 7.2
The Receive Power Does not Meet the Design Requirements.
----End

Commissioning and Configuration Guide 6 System Commissioning
6 System Commissioning
About This Chapter
This chapter describes the specific commissioning procedures for all system commissioning
items.
6.1 Configuring Network-wide Service Data
After site commissioning is performed for each hop of microwave link, embedded control
channel (ECC) communication between NEs is normal. Then, you can connect the U2000 to an
NE and configure network-wide service data.
6.2 Testing Ethernet Services
By testing Ethernet services, you can check whether the Ethernet services are available over
microwave links. Ethernet services can be tested using the ETH OAM function, and no dedicated
tester is required.
6.3 Testing AMAC Shifting
By simulating the signal-to-noise ratio (SNR) of received signals, you can determine whether
to trigger AMAC shifting on OptiX RTN 380.
6.4 Testing Protection Switching
If services on a microwave network are protected, you need to test typical protection schemes
to verify the protection switching function.
6.5 Checking the Clock Status
Checking the clock status for all NEs on a microwave transmission network ensures that the NE
clocks are synchronized.
6.6 Testing the Fade Margin over a Microwave Link
The fade margin over a microwave link can be evaluated by measuring the mean square errors
(MSEs) at different received signal levels (RSLs).
6.7 Testing Ethernet Service Performance
This section describes how to test Ethernet service performance using the NE-inherent test
functions.

6.1 Configuring Network-wide Service Data

After site commissioning is performed for each hop of microwave link, embedded control
channel (ECC) communication between NEs is normal. Then, you can connect the U2000 to an
NE and configure network-wide service data.
Context
NOTE
For details about how to configure network-wide service data, see 8 Configuring Networkwide Service
Data.
6.2 Testing Ethernet Services

tester is required.
6.2.1 Testing Ethernet Services Configured on a Per NE Basis

To test Ethernet services configured on a per NE basis, you must create ETH OAM manually.
Prerequisites
Ethernet services have been configured.
NOTE
If the Ethernet services to be tested are low-priority services, it is recommended that you perform the test when
weather conditions are favorable and the microwave link works in the highest-order modulation scheme.

U2000
Test Connection Diagram

The following procedure uses the Ethernet services from GE 1 on NE 1 to GE 1 on NE 2 as an
example, as shown in Figure 6-1.
Figure 6-1 Connection diagram for testing Ethernet services
Microwave transmission network

NE 1 NE 2
GE 1 GE 1
NodeB
VLAN ID = 100 VLAN ID = 100
RNC

Procedure
Step 1 Test the Ethernet services between NE1 and NE2.
l If the value of LossRate in Result is 0, the test is successful.

l If the value of LossRate in Result is not 0, handle the problem based on the procedures in
the following table.
Cause Handling Procedure
Connecting to the peer end fails within the Check whether services are interrupted.
specified period.
Packets are lost. Check whether the service traffic is higher

than the transmission bandwidth.
Check the link for bit errors.
----End
6.2.2 Testing Ethernet Services Configured in End-to-End Mode

The ETH OAM that is automatically created by services can be used to test Ethernet services
configured in end-to-end mode.
Prerequisites
NOTE

U2000

NOTE
The Web LCT does not support this operation.

example, as shown in Figure 6-2.
Figure 6-2 Connection diagram for testing Ethernet services

NE 1 NE 2
GE 1 GE 1
NodeB
RNC

1. Verifies Ethernet line (E-Line) services transmitted in Native Ethernet mode.
2. Verifies Ethernet local area network (E-LAN) services transmitted in Native Ethernet
mode.
Procedure
Step 1 Verify E-Line services transmitted in Native Ethernet mode.
Step 2 Verify E-LAN services transmitted in Native Ethernet mode.

----End
6.3 Testing AMAC Shifting

Prerequisites
l The adaptive modulation (AMAC) function has been enabled for the microwave link to be
tested.
l Weather conditions are favorable.

Web LCT
NOTE
The U2000 does not support this operation.
Context
The following procedure tests the AMAC shifting function on an NE.
Procedure
Step 1 Set the AMAC attributes.

Step 2 Test one-click AMAC shifting.
----End
6.4 Testing Protection Switching

6.4.1 Testing ERPS Switching

You can verify the Ethernet ring protection switching (ERPS) function by checking the port
status of the ERPS protection group before and after switching.
Prerequisites
l ERPS has been configured for OptiX RTN 380s on a ring network.
l Ethernet links on the ring network are connected correctly.


U2000
NOTE
Context
The following procedure queries the port status change on the ring protection link (RPL) owner
node in an ERPS protection group before and after switching to check whether the ERPS function
is running properly.

In Figure 6-3, the Ethernet services between NE 1 and NE 6 are protected by ERPS, and NE 1
is the RPL owner node.
Figure 6-3 Configuration for testing ERPS

NE 4 NE 3
E: IF E: GE (GE2)
W: GE (GE2) W: IF
NE 5 NE 2
E: GE (GE2) E: IF
W: IF W: GE (GE2)
NE 6 NE 1
E: IF E: GE (GE2)
W: GE (GE2) NE 7 NE 8
E: GE (GE2) E: IF W: IF
W: IF W: GE (GE2) RPL owner
Ethernet cable
Ethernet service direction
Blocked port
Procedure
Step 1 Before switching, query the status of the ERPS protection group that is configured on NE 1.

Step 2 Test the availability of the Ethernet services. For details, see 6.2.1 Testing Ethernet Services
Configured on a Per NE Basis.
The value of LossRate in Detection Result should be 0.
Step 3 Set TX Status to mute for NE 6.
Step 4 After switching, query the status of the ERPS protection group that is configured on NE 1.

Step 6 Set TX Status to unmute for NE 6.
----End
6.4.2 Testing 1+1 Protection Switching

You can verify the 1+1 protection functions by checking the changes of the main and standby
devices before and after switching.
Prerequisites
l Antenna alignment has been completed.
l Ethernet services and 1+1 protection have been configured.
l Static link aggregation groups (LAGs) have been configured for third-party devices,when
the devices are connected without optical splitters.

U2000

Figure 6-4 Test connection diagram
When the optical splitters are not used ,the basic configurations are as follows:
l Main OptiX RTN 380s: NE 11 and NE 12
l Standby OptiX RTN 380s: NE 21 and NE 22
LAG NE 11 NE 12 LAG
LAG LAG
COMBO COMBO
Antenna Antenna
NE 21 NE 22
LAG LAG
E-LAG E-LAG
OptiX RTN 900 Microwave link
Ethernet link Optical fiber
The Ethernet services protected by 1+1 hot standby (HSB) between NE 11 and NE 12 shown in
Figure 6-4 are tested.
The same testing way can be used for the topology with optical splitters.
Procedure
Step 1 Configure Reversion Mode for the 1+1 HSB protection group on NE 11.
1. In NE Explorer, choose NE 11 from the object tree and choose Configuration > IF 1+1
Protection from Function Tree.
2. In Protection Group, select the desired protection group and set Reversion Mode to Non-
Revertive.
3. Click Apply.
4. Click Close.
Step 2 Query the protection group status on NE 11 before switching.

2. In Protection Group, select the desired protection group and click Query.
3. Ensure that Active NE of Device in Protection Group is NE 11.
Step 3 Test availability of the tested Ethernet services before switching. For details, see 6.2 Testing
Ethernet Services. The value of LossRate in Test Result should be 0.
Step 4 Cold reset NE 11.

1. Optional: Double-click the subnet to which NE 11 belongs.

2. Double-click NE 11 in Main Topology.

The NE panel is displayed.
3. Select the SHUF3 board, right-click, and choose Cold Reset from the shortcut menu.
The Warning dialog box is displayed.
4. Click OK.
Step 5 After NE 11 is cold reset (which takes about 3 minutes), query the protection group status on
NE 11.
Step 6 Test availability of the tested Ethernet services after switching. For details, see 6.2 Testing
Ethernet Services. The value of LossRate in Test Result should be 0, indicating that the 1+1
protection switching is successful.
Step 7 Restore Reversion Mode to the original value.
----End
6.5 Checking the Clock Status

Checking the clock status for all NEs on a microwave transmission network ensures that the NE
clocks are synchronized.
Prerequisites
l Clock configuration has been completed.
l The links that transmit clock signals are functioning properly.

U2000
NOTE
Context
The following procedure checks the clock status of NEs on a network.
Procedure
Step 1 Check the clock status of an NE.

Step 2 Repeat Step 1 to check the clock status of the other NEs on the network.
----End
6.6 Testing the Fade Margin over a Microwave Link

The fade margin over a microwave link can be evaluated by measuring the mean square errors
(MSEs) at different received signal levels (RSLs).
Prerequisites
l Antennas have been aligned, and the RSLs at both ends of the microwave link meet
requirements.
l The configured transmit power is the same as the actual transmit power.

U2000
NOTE
Context
The procedure for testing the fade margin is as follows:
l Test the mapping between RSLs and MSEs at multiple sites.
l Calculate the RSL corresponding to the MSE demodulation threshold to determine the
receiver sensitivity.
l Subtract the receiver sensitivity from the current RSL to obtain the fade margin.
The following procedure tests the fade margin over a microwave link.

Precautions
1. When the fade margin is being tested, all the services carried on the microwave link may
be interrupted.
2. For microwave links configured with 1+1 protection, forcibly switch services to the main
link before testing the main link. Forcibly switch services to the standby link before testing
the standby link.
Procedure
Step 1 Disable the adaptive modulation (AM) and automatic transmit power control (ATPC) functions
on the microwave link between two sites.
Step 2 Test the fade margin over the microwave link.
Step 3 Enable the AM and ATPC functions for the microwave link base on Step 1.
NOTE
Restore Modulation Mode of the Guaranteed AM Capacity and Modulation Mode of the Full AM
Capacity to their initial values when enabling the AM function.
----End

6.7 Testing Ethernet Service Performance

This section describes how to test Ethernet service performance using the NE-inherent test
functions.
6.7.1 Testing the Latency, Throughput, and Packet Loss Ratio

This section describes how to test the latency, throughput, and packet loss ratio of VLAN-based
Ethernet line (E-Line) services with different frame lengths.
Prerequisites
l The source and sink NEs of the Ethernet services have been configured with VLAN-based
E-Line services.

U2000
Context
CAUTION
l The source and sink ports (test ports) of the tested Ethernet services must be Ethernet ports.
During the test, all Ethernet services over the test ports are interrupted.
l If the tested Ethernet services contain quality of service (QoS), OAM, link aggregation group
(LAG), inband data communication network (DCN), or other protocol data, the test results
may be inaccurate. It is recommended that you disable the functions before performing the
test.
l If the source port of the tested services carries other services, the test results may be
inaccurate. It is recommended that you disable the other services at the source port before
performing the test.

The Ethernet services between PORT 2 on NE(9–2396) and PORT 2 on NE(9–2398) shown in
Figure 6-5 are tested. Both NE(9–2396) and NE(9–2398) are configured with VLAN-based E-
Line services.

NE(9-2396) NE(9-2398)
PORT 2 PORT 2
NodeB VLAN ID = 100 VLAN ID = 100

Microwave network
RNC
The Ethernet services between NE(9–2396) and NE(9–2398) carry the VLAN ID 100.
Procedure
Step 1 Configure the TAG attributes for the test ports.
Step 2 Configure a sink NE for the test.

Step 3 Configure a source NE for the test and initiate the test.
NOTE
l The test results may deviate from the actual values, as compared with the results of a test performed using
a meter. When the bandwidth of tested services is less than 70 Mbit/s, the deviation of the packet loss ratio
is less than 1%. When the bandwidth of tested services is higher than or equal to 70 Mbit/s, the deviation of
the packet loss ratio is less than 0.2%. If the packet loss ratio is not 0 and its deviation is within these ranges,
perform the test multiple times. If the results of the multiple tests show that a few packets are lost and the
packet loss ratio of services with long frames is higher than that of services with short frames, you can
consider that no packet is lost.
l The throughput test result of services with long frames deviates from the actual result by less than 5%.
l The latency result and packet loss ratio result are the results of bidirectional services.
----End
6.7.2 Testing the Long-term Packet Loss Ratio

This section describes how to test the long-term packet loss ratio of VLAN-based Ethernet line
(E-Line) services with different frame lengths.
Prerequisites
l The source and sink NEs of the Ethernet services have been configured with VLAN-based
E-Line services.

U2000

Context
CAUTION
l During the Ethernet service test, all Ethernet services over the test ports are interrupted.
l If the tested Ethernet services contain quality of service (QoS), OAM, link aggregation group
(LAG), inband data communication network (DCN), or other protocol data, the test results
may be inaccurate. It is recommended that you disable the functions before performing the
test.
l If the source port of the tested services carries other services, the test results may be
inaccurate. It is recommended that you disable the other services at the source port before
performing the test.

The Ethernet services between PORT 2 on NE(9–2396) and PORT 2 on NE(9–2398) shown in
Figure 6-6 are tested. Both NE(9–2396) and NE(9–2398) are configured with VLAN-based E-
Line services.
NE(9-2396) NE(9-2398)
PORT 2 PORT 2
NodeB VLAN ID = 100 VLAN ID = 100

Microwave network
RNC
The Ethernet services between NE(9–2396) and NE(9–2398) carry the VLAN ID 100.
Procedure
Step 1 Configure the TAG attributes for the test ports.

Step 2 Configure a sink NE for the test.
Step 3 Configure a source NE for the test and initiate the test.

NOTE
The test results may deviate from the actual values. When the number of received packets and that of sent packets
are different and the difference is less than a millionth, you can consider that no packet is lost.
----End

Commissioning and Configuration Guide 7 Handling of Common Faults During Site Deployment
7 Handling of Common Faults During Site

Deployment
About This Chapter
This chapter describes how to handle common faults during site deployment.
7.1 When a USB Flash Drive Is Used for Loading Commissioning Data, Some Commands Fail
to Be Loaded
This section describes how to handle a command loading failure that occurs when a USB flash
drive is used for loading commissioning data.
7.2 The Receive Power Does not Meet the Design Requirements
This section describes how to handle the fault of receive power failing to meet the design
requirements.

7.1 When a USB Flash Drive Is Used for Loading

Commissioning Data, Some Commands Fail to Be Loaded
This section describes how to handle a command loading failure that occurs when a USB flash
drive is used for loading commissioning data.
Fault Symptom
When a USB flash drive is used for loading commissioning data, the indicator on the USB flash
drive is steady red after the loading is complete.
Cause Analysis
Steady red indicates that some commands fail to be loaded. You can locate these commands in
NE operation logs.
Procedure
Step 1 Browse NE operation logs. For details, see A.4.5 Querying NE Operation Logs.
Step 2 Record Operation Object in the logs with Result being Operation Failed, and send the
recorded information to the engineers responsible for generating data scripts.
NOTE
If commissioning engineers are able to configure NE data on the Web LCT, they can re-configure data related
to the failed commands based on the logs using the Web LCT.
Step 3 After correct scripts are generated, arrange personnel to load the commissioning data using a
USB flash drive. For details, see 4.2 Loading Commissioning Data Using a USB Flash
Drive.
----End
7.2 The Receive Power Does not Meet the Design

Requirements
This section describes how to handle the fault of receive power failing to meet the design
requirements.
Fault Symptom
No hardware alarm is reported on an NE. However, the receive power is at least 3 dB less than
the designed receive power, and the microwave link reports an MW_LOF alarm.
Cause Analysis
No hardware alarm is reported, so the equipment is running normally. Diagnose the fault from
the following aspects:
l NE configurations

l Link transmission conditions and network plan

l Hardware installation and antenna alignment
Procedure
Step 1 Check NE configurations by browsing the configuration data of the microwave link according
to A.5.1 Configuring a Single Hop of Microwave Link.
l Verify that the actual transmit and receive frequencies at both ends of the link match and
meet the network plan requirements.
l Verify that the channel bandwidths and modulation schemes at both ends of the link are the
same and meet the network plan requirements.
l Verify that the transmit power at both ends of the link meets the network plan requirements.
l Verify that the adaptive modulation (AM) and automatic transmit power control (ATPC)
functions are disabled during antenna alignment.
Step 2 Check the link transmission conditions and network plan.
l Verify that antennas are aligned under favorable weather conditions, free from the impact of
rainfall, snow, or fog.
l Verify the line of sight (LOS) on the microwave link based on a map and observation.
l Verify that the antenna positions and directions meet the network plan requirements by using
a compass.
l Verify that the height difference between the antennas is within the adjustment range and
that the network design parameters are correct by consulting network planning engineers.
Step 3 Check hardware installation and antenna alignment.
l Verify that the polarization directions of the antennas meet the network plan requirements.
When an OptiX RTN 380 or hybrid coupler is being installed, the polarization directions of
feed ports are the same.
l Verify that the main lobes of the antennas are aligned.
----End

Commissioning and Configuration Guide 8 Configuring Networkwide Service Data
8 Configuring Networkwide Service Data
About This Chapter
This document uses configuration examples to describe the flow and procedure for configuring
the equipment. With this document, you can get familiar with the data configuration methods
and complete various configuration tasks in actual application.
8.1 Configuration Preparations

Before configuring the NE data, you must make the required preparations.
8.2 General Configuration Process
Select a proper configuration process based on the actual configuration scenarios.
8.3 Common Network Scenarios of Configuration Examples
This section provides the four network scenarios on which initial configuration examples are
based. The initial configuration examples cover all operations in general configuration process.
8.4 Configuring the Network Topology
You can manage a transport network by using the U2000 only after configuring the network
topology.
8.5 Configuring Microwave Links
Before configuring services on a microwave link, you need to configure the microwave link.
8.6 Configuring Native Ethernet Services
Native Ethernet services include Native Ethernet line (E-Line) services and Native Ethernet local
area network (E-LAN) services.
8.7 Configuring Clocks
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.
8.8 Adding and Modifying Configuration Data
During the equipment commissioning and operating phases, you need to add or modify certain
configuration data according to the actual requirements.

8.1 Configuration Preparations

Before configuring the NE data, you must make the required preparations.
8.1.1 Preparing Documents and Tools

Related documents and tools must be available to ensure the proper configuration of data.
Documents
l Network planning documents
l OptiX RTN 380 Radio Transmission System Commissioning and 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 requirements and methods for installing U2000 software and hardware, see the documents that accompany
the U2000.
8.1.2 Checking Configuration Conditions

Before beginning the configuration process, confirm that local conditions meet requirements.
Context
Ensure that the following requirements are met:
l All the NEs on the network must be powered on properly.

l Data communication network (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 network operator rights or higher.
8.2 General Configuration Process

Select a proper configuration process based on the actual configuration scenarios.
Initial Configuration
Initial configuration of a microwave network refers to initial configuration of network-wide
service data using the network management system (NMS) after site commissioning is complete.
Figure 8-1 shows the configuration flowchart.

Figure 8-1 Flowchart for initial configuration
Required Start
Optional
Configure the network
topology.
Configure microwave
links.
Configure Native
Ethernet services.
Configure the clock.
End
The steps in the configuration flowchart are described in Table 8-1.
Table 8-1 Initial configuration

Operation Remarks
8.4 Configuring the Network Required.

Topology
8.5 Configuring Microwave Links Required.
8.6 Configuring Native Ethernet Required.

Services
8.7 Configuring Clocks Required.
NOTE
The configuration sequence provided in Table 8-1 is for reference only and needs to be adjusted based on actual
scenarios. For detailed configuration methods based on local scenarios, see the configuration examples
corresponding to 8.3 Common Network Scenarios of Configuration Examples.
Network Adjustment
Network adjustment involves adding and adjusting configuration data during the equipment
commissioning and operation phases. You can determine a task collection based on the actual

network adjustment requirements and then find the corresponding configuration operations from
the task collection.
Table 8-2 Network adjustment

Common Task Collection Description
8.8.1 Common Task Collection Lists configuration operations associated with NE

(Network Topology) attributes, including changing the ID and IP address
of an NE.
8.8.2 Common Task Collection Lists configuration operations associated with

(Microwave Links) microwave links, including changing the basic
attributes and radio frequency (RF) attributes of
microwave links.
8.8.3 Common Task Collection Lists configuration operations associated with

(Ethernet Services) Ethernet services, including configuring or
modifying Ethernet port parameters and creating link
aggregation groups (LAGs).
8.3 Common Network Scenarios of Configuration Examples

This section provides the four network scenarios on which initial configuration examples are
based. The initial configuration examples cover all operations in general configuration process.
8.3.1 Overview
This section describes the relationship between networking and configuration process.
l The entire configuration process on a chain network and ring network, covering the
configuration of network topology, microwave links, Ethernet services, and clock, is
demonstrated.
l Because the structure of a large-capacity microwave backhaul network configured with 1
+1 protection and that of a hybrid network consisting of radio equipment and optical fibers
are simple, only the examples of key and complicated configurations are provided.
l In Table 8-3, √ indicates that a configuration example is provided and - indicates that no
configuration example is provided.

Table 8-3 Configuration examples for different networks

Operation Microwave Microwave Hybrid Large-
Chain Ring Network Capacity
Network Network Consisting Microwave
of Radio Backhaul
Equipment Network
and Optical Configured
Fibers with 1+1
Protection
Configure the network √ √ - -

topology
Configure microwave √ √ - √
links
Configur Transparently - - √ -
e Native transmitted
Ethernet point-to-point
services E-Line
service
VLAN-based √ - - -
E-Line
service
QinQ-based - - - √
E-Line
service
IEEE 802.1D - √ - -
bridge-based
E-LAN
service
IEEE 802.1Q √ - - -
bridge-based
E-LAN
service
Configur Clock on a √ - - -
e the microwave
clock chain
network
Clock on a - √ - -
microwave
ring network
8.3.2 Microwave Chain Network

This section describes a microwave chain network consisting of multiple OptiX RTN 380
equipment and OptiX RTN 900 equipment.

Figure 8-2 shows the topology of the network. Ethernet services are received on NE21 and
NE23 and are transmitted to the local backhaul network through NE24 and NE99.
Figure 8-2 Networking diagram for a microwave chain network

NMS
RNC
LAN
switch
Regional
Backhaul
Network
P&E GE GE
P&E
NodeB 1 P&E NE99

NE21 NE22 NE23 NE24
RAN 1
OptiX RTN 900 Radio link Ethernet link
NOTE
NE99 is an OptiX RTN 900 NE and it receives services from NE24 through the P&E port of the EG4P
board. This manual does not introduce the detailed configurations of NE99.
8.3.3 Microwave Ring Network

This section describes a microwave ring network consisting of six OptiX RTN 380 devices
located at three sites.
Figure 8-3 shows the topology of the network. Ethernet services are received on NE36 and
NE33 and are transmitted to the local backhaul network through NE35.

Figure 8-3 Networking diagram for a microwave ring network
NMS
NodeB 1
P&E
LAN switch
GE GE
NE31 NE36
P&E Regional
Backhaul
Network
RNC
GE GE NE35
NE32
GE GE
P&E
NodeB 2 NE33 NE34
Radio link Ethernet link
8.3.4 Hybrid Network Consisting of Radio Equipment and Optical

Fibers
This section describes a hybrid network consisting of radio equipment and optical fibers. In this
network, a hop of large-capacity OptiX RTN 380 equipment replace optical fibers to form a ring
network with OptiX optical transmission equipment.
As shown in Figure 8-4, OptiX RTN 380s can provide high-bandwidth microwave links for
transmitting Ethernet services on a metro optical Ethernet in areas where optical fibers are
difficult to lay out.

Figure 8-4 Networking diagram of a hybrid ring network consisting of radio equipment and
optical fibers
NMS
LAN
switch
LAG LAG
Backbone
NE33 NE34 Network
NE91 NE92
NE93 NE94
Optical
Radio link Ethernet link transmisson
equipment
8.3.5 Large-capacity Microwave Backhaul Network Configured

with 1+1 Protection
This section describes a large-capacity microwave backhaul network consisting of four OptiX
RTN 380 devices and OptiX RTN 900 equipment. The equipment forms 1+1 protection.
As shown in Figure 8-5, the OptiX RTN 380 can provide large-capacity backhaul links for
convergence nodes. In addition, it can form 1+1 protection with an OptiX RTN 900 NE to protect
services on the backhaul links.

Figure 8-5 Networking diagram of a large-capacity microwave backhaul network configured

with 1+1 protection
RNC 1
RAN 1
NE11 NE13
P&E P&E
GE GE
COMBO COMBO
COMBO COMBO
GE GE
RAN 2 P&E P&E

NE14 RNC 2
NE12
NOTE
On this network, LAGs configured for the OptiX RTN 900 equipment or switches work together with the OptiX
RTN 380 equipment to implement 1+1 protection. If optical splitters are used to achieve 1+1 protection, see
Networking Diagram in Feature Description for details.
8.4 Configuring the Network Topology

You can manage a transport network by using the U2000 only after configuring the network
topology.
8.4.1 Basic Concepts

Before configuring the network topology, familiarize yourself with the basic concepts.
8.4.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. 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. OptiX RTN 380 supports the HWECC, IP DCN, and L2 DCN solutions.
By default, the IP DCN solution is used.
IP DCN is a DCN solution provided by Huawei. In this solution, network management system
(NMS) messages are encapsulated in the standard IP protocol stack and transmitted over DCN
channels between NEs so that the NMS can manage these NEs.
Figure 8-6 shows how NMS messages are transmitted using the IP DCN solution.

Figure 8-6 Application of the IP DCN solution
3rd-party Msg
3rd-party Msg OptiX Msg
IP stack
IP stack OptiX Msg IP stack
NM-ETH
NM-ETH IP stack DCC Third-party
DCC equipment
Third-party
NMS
External DCN
OptiX Msg
IP stack
OptiX Msg Inband DCN
IP stack OptiX Msg
NM-ETH IP stack
NMS Inband DCN
OptiX Msg
IP stack OptiX Msg
Inband DCN IP stack
Inband DCN
Ethernet link Microwave link
As shown in the preceding figure, different vendors' NMS messages encapsulated in the IP
protocol stack can be transmitted over the following DCN channels:
l DCCs in microwave links
l Ethernet service channels in radio or GE links
l Ethernet NMS ports
8.4.1.2 Access Control

The access control function enables an OptiX RTN 380 to connect to a network management
system (NMS) through its GE port.
Connecting to an NMS Through a Third-Party Service Network

Figure 8-7 illustrates a typical scenario in which an OptiX RTN 380 connects to an NMS through
a third-party service network. When transmitting Ethernet services, the packet switched network
(PSN) also transmits data communication network (DCN) packets between the NMS and the
gateway NE. In this instance, the access control function can be enabled on the GE port of the
gateway NE.

Figure 8-7 Access control (OptiX RTN 380 connecting to an NMS through a third-party service
network)
NMS
DCN packets
LAN switch
PSN
GE port
Access control
enabled
Router
Ethernet services
After you enable the access control function on the GE port:

l The GE port functions as an NMS port on the gateway NE.
l You can specify the IP address of the GE port according to the requirements of the PSN.
This IP address cannot be on the same segment as the IP address of the local NE.
l The DCN packets transmitted/received at the GE port carry a VLAN ID used for inband
DCN. Before a DCN packet arrives at the NMS, its VLAN ID needs to be stripped off by
an NE such as the LAN switch in Figure 8-7.
l The NMS can communicate with the gateway NE based on the IP address of the GE port
on which the access control function is enabled.
Connecting to a Web LCT Through a GE Port

Figure 8-8 illustrates a typical scenario in which an OptiX RTN 380 connects to a Web LCT
through its GE port. Generally, a Web LCT is used for OptiX RTN 380 onsite maintenance. At
sites that do not have power injectors (PIs) installed, maintenance personnel must climb towers
to connect OptiX RTN 380s to Web LCTs. To avoid climbing towers, maintenance personnel
can instead disconnect the Ethernet service cable between an OptiX RTN 380 and a NodeB,
connect the Ethernet service cable to a Web LCT, and then enable access control on the GE port
on the OptiX RTN 380.

Figure 8-8 Access control (OptiX RTN 380 connecting to a Web LCT through its GE port)
NodeB 1
GE port
Access control
enabled
Web LCT
GE port
NOTE
l An OptiX RTN 380 can connect to a Web LCT through its GE port only if its GE port functions as an
electrical port.
l A VLAN ID can be added to and stripped from DCN packets only after you install a drive and specify
the VLAN ID on the computer on which the Web LCT is installed.
8.4.1.3 GNE and Non-GNE

A gateway NE (GNE) refers to an NE whose application layer communicates directly with the
network management system (NMS) application layer. A non-GNE refers to an NE whose
application layer communicates with the NMS application layer by forwarding data through the
GNE application layer.
GNE
Generally, a GNE is connected to the NMS through a local area network (LAN) or through a
wide area network (WAN). Its application layer can directly communicate with the NMS
application layer. One set of NMS needs to be connected to one or more GNEs.
Embedded control channel (ECC) communication between the GNEs may create an oversized
data communication network (DCN). To prevent this, disable extended ECC for the GNEs.
Non-GNE
A non-GNE communicates with the GNE through the DCN channels between NEs.

8.4.1.4 NE ID and NE IP Address

An NE on the DCN is identified by its ID and IP address.
NE ID
At the application layer of each DCN solution, an OptiX NE uses its NE ID as the NE address.
Therefore, each NE must have a unique NE ID on the DCN and all the NE IDs must be planned
in a unified manner.
The NE ID has 24 bits. The most significant eight bits represent the subnet ID (or the extended
ID) and the least significant 16 bits represent the basic ID. For example, if an NE ID is 0x090001,
the subnet ID is 9 and the basic ID is 1.
NE IP Address
An NE uses an IP address as its unique identifier during TCP/IP communication.
In the HWECC solution, the IP addresses of the NEs on the DCN are used in the following
scenarios:
l A gateway NE (GNE) communicates with the U2000 over TCP/IP. The IP address of the
GNE must be planned as required by the external DCN.
l Different NEs communicate with each other over extended embedded control channels
(ECCs). In this scenario, NE IP addresses must be on the same network segment. By default,
NE IP addresses are on the 129.9.0.0 network segment.
In the DCN solution (for example, IP DCN) where network management messages are
transmitted over TCP/IP, an NE IP address is used as the NE address at the network layer.
Therefore, each NE IP address on the DCN must be unique and all these NE IP addresses must
be planned in a unified manner.
By default (which indicates that an NE IP address is never manually changed), this NE IP address
is automatically changed to 0x81000000 + ID if the NE ID is changed. For example, if an NE
IP address is never manually changed, this NE IP address is automatically changed to 129.9.0.1
when the NE ID is changed to 0x090001. Once an NE IP address is manually changed, the
interlocking relationship between the NE ID and NE IP address no longer takes effect.
8.4.1.5 Fiber/Cable Types

You can obtain the clear fiber/cable connection relationship between NEs by using the fiber
management function of the U2000. You can also use the U2000 to manage fibers and cables,
including Ethernet fibers/cables, microwave links, extended ECC cables, and back-to-back radio
connections.
l Ethernet fibers/cables
Ethernet fibers/cables refer to the Ethernet fiber/cable connections between Ethernet
optical/electrical ports on different sets of equipment.
l Microwave links
Microwave links refer to the radio connections between different sets of radio equipment.
That is, the microwave links indicate the connection relationship 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 relationship between the NEs.
l Back-to-back radio connections
Back-to-back radio connections refer to the NE cascading relationship. That is, the back-
to-back radio connections indicate the connection relationship between the NEs.
NOTE
Fibers and cables are topological objects on the U2000. Therefore, operations on the fibers or cables do not
affect the normal running of the NEs.
8.4.1.6 Subnet
NEs in the same domain or with similar attributes can be allocated to the same subnet. In this
manner, they can be displayed and managed as a whole on the U2000, which facilitates NE
management.
Subnets are topological objects on the U2000, but do not physically exist on networks. Therefore,
operations on subnets do not affect the normal running of NEs. Subnets simplify the main
topology on the U2000.
8.4.2 Configuration Process (Network Topology)

This section describes the processes of configuring the four topological objects: NEs, boards,
fibers/cables, and subnets.
Figure 8-9 shows the flowchart for configuring the network topology.

Figure 8-9 Flowchart for configuring the network topology
Required Start
Optional
Create an NE.
Set NE attributes.
Set the DCN channel.
Synchronize the NE time.
Set the NE performance

monitoring status.
Create fibers/cables and

subnets.
End
NOTE
When the Web LCT is used for configuration, there is no need to create fibers/cables and subnets.
The steps in the configuration flowchart are described as follows:

Creating NEs
Table 8-4 Process of creating NEs

Step Operation Remarks
1 Creating NEs A.3.1.1 It is recommended that you perform this

on the U2000 Creating an operation to add one or more NEs to a large
NE by Using existing network on the U2000.
the Search To achieve Secure Sockets Layer (SSL)
Method communication between the network
management system NMS and the gateway
NE, Connection Mode needs to be set to
Security SSL.
A.3.1.2 It is recommended that you perform this

Creating an operation to create NEs on the U2000 in other
NE Manually cases. The following parameters need to be
set:
l Set Search Mode to Search for NE.
l Search Domain: When the IP address of
the gateway NE (GNE) is known, it is
recommended that you set 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 Create NE after search, and
Upload after create. By default, NE
User is root and Password is password.
l Connection Mode: This parameter
specifies the connection mode between
the NMS and the gateway NE. For SSL
connection, set this parameter to Security
SSL.
2 A.3.2.1 Uploading NE Data If you select Upload after create during A.

3.1.2 Creating an NE Manually, skip this
operation.
NOTE
The NE creation steps on the Web LCT are different from those on the U2000. When the Web LCT is used:
1. Skip A.3.2.1 Uploading NE Data.
2. If an NE is not logged in after being created, perform A.3.1.3 Logging In to an NE.

Configuring NE Attributes
Table 8-5 Process of configuring NE attributes

1 A.3.1.4 Required. Set parameters as follows:

Changing l Change New ID to be the NE ID specified during the data
an NE ID communication network (DCN) planning.
l If the extended NE ID is required, change New Extended
ID.
2 A.3.1.5 Optional.
Changing
an NE
Name
Configuring DCCs
Table 8-6 Process of configuring DCCs


Setting NE l In the case of the GNE, set IP and Subnet Mask according
Communica to the planning of the external DCN.
tion
Parameters l In the case of the GNE, set Gateway IP if the external
DCN requires.
l Generally, it is recommended that you set Connection
Mode to Common + Security SSL. If you need to set the
gateway NE to allow for NMS access only in SSL
connection mode, set Connection Mode to Security
SSL.
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.
2 A.3.6.2 Disable related DCCs when using inband DCN channels.

Configuring
DCCs

3 A.3.6.7 Disable the automatic extended embedded control channel

Configuring (ECC) function for NEs that communicate with the NMS
Extended through NMS ports.
ECCs
4 A.3.6.3 Required if the OptiX RTN 380 equipment uses the inband
Setting the DCN solution and if the VLAN ID and bandwidth planned
VLAN ID for this inband DCN do not assume their default values (the
and default VLAN ID is 4094 and the default bandwidth is 512
Bandwidth kbit/s).
for an
Inband
DCN

Setting a l If inband DCN channels use the HWECC protocol, set
Port for an Protocol Type to HWECC. If inband DCN channels use
Inband the IP protocol, set Protocol Type to IP. If inband DCN
DCN channels use the L2 DCN protocol, set Protocol Type to
L2DCN.
l It is recommended that you set Enabled Status to
Disabled for the ports connected to customers' equipment.
6 A.3.6.9 Optional. When a network consists of only OptiX RTN 380

Setting NEs and uses a single Open Shortest Path First (OSPF) area,
OSPF it is recommended that you retain the default values for the
Protocol parameters.
Parameters
7 A.3.6.6 Optional.
Configuring When a gateway NE is connected to the NMS through a third-
Access party network, enable the access control function for the
Control Ethernet port connected to the third-party network on the
gateway NE. In addition, set IP address and Subnet mask
for the port according to the network plan.
NOTE
The preceding DCN configuration process applies to a typical IP DCN solution configuration in a single OSPF
area. For the configuration process for an IP DCN solution containing special requirements or for another DCN
solution, see related descriptions in the Feature Description.

Synchronizing NE Time
Table 8-7 Process of synchronizing NE time
1 Synchroni A.3.1.6 Required.

zing the Synchron l To synchronize the NEs with the NMS 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 NMS 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 Network Time
Protocol (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 Flag 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 Flag 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
Flag 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.3.1.7 Required if daylight saving time (DST) is used at the

Localizin local area.
g the NE Set the parameters according to the planning of DST
Time at the local area.

A.3.1.8 Required if the standard NTP authentication is used

Configuri to synchronize the NEs with the NTP server.
ng a Set the parameters according to the identification
Standard authentication of the NTP.
NTP Key
NOTE
When the Web LCT is used, skip this operation because
this operation is included in A.3.1.6 Synchronizing the
NE Time.
Setting the Performance Monitoring Status
Table 8-8 Process of setting the performance monitoring status
1 A.3.3 If the 15-minute and 24-hour performance monitoring

Setting the functions are set to Disabled, enable these performance
Performanc monitoring functions.
e
Monitoring
Status for
an NE
Creating Fibers/Cables and Subnets
Table 8-9 Process of creating fibers/cables and subnets
1 Creating A.3.4.1 It is recommended that you perform this operation

fibers/ Creating to create fibers/cables.
cables a Fiber/
Cable by
Using the
Search
Method
A.3.4.2 It is recommended that you perform this operation

Creating to create fibers/cables that cannot be created using
a Fiber/ the search method (for example, when the fiber/
Cable cable has not been connected).
Manually
2 A.3.4.4 Creating a Optional when there are cascading NEs on the

Back-to-back Radio network.
Connection

3 Configuri A.3.5.1 Optional.

ng the Creating
subnet a Subnet
A.3.5.2 Optional.
Copying a
Topology
Object
A.3.5.3 Optional.
Moving a
Topology
Object
8.4.3 Configuration Example (Microwave Chain Network)

This section uses a microwave chain network as an example to describe how to configure the
network topology according to the network plan.
8.4.3.1 Networking Diagram

This section describes the networking of NEs.
Figure 8-10 shows a microwave chain network configured according to the following
requirements:
l The microwave link traverses both OptiX RTN 380 equipment and OptiX RTN 900
equipment, which are managed by the U2000.
l The local backhaul network is a third-party network and cannot be managed together with
the OptiX RTN equipment. NE99 is configured as the gateway NE, and it communicates
with U2000s using the access control function.
l The NEs use the D1 to D3 bytes in microwave links or partial Ethernet bandwidth in GE
links for data communication network (DCN) communication that is implemented using
IP.


NMS
RNC
LAN
switch
Regional
Backhaul
Network
P&E GE GE
P&E
NodeB 1 P&E NE99

NE21 NE22 NE23 NE24
RAN 1
NOTE
l On the NMS, the logical port of a microwave port is 1-SHUF3-1(IF).

l On the NMS, the logical port of a P&E port is 1-SHUF3-2(GE1).
l On the NMS, the logical port of a COMBO port that functions as an optical GE port is 1-SHUF3-3
(GE2).
l On the NMS, the logical port of a COMBO port that functions as a 1+1 concatenation port is 1-
SHUF3-3. This port is valid only when DCN is being configured.
l On the NMS, the logical port of a GE port is 1-SHUF3-4(GE3).
8.4.3.2 Service Planning

This section describes the parameters required for configuring a microwave chain network.
l Use the IP DCN solution.

l To prevent impact on NodeBs, disable the inband DCN function for the ports that receive/
transmit services from/to NodeBs on all NEs.
l Plan the management VLAN ID and bandwidth of the inband DCN for each NE as follows:
– Retain the default value 4094 for the management VLAN ID. The management VLAN
ID must be different from the VLAN ID carried by service packets.
– Retain the default value 512 kbit/s for the inband DCN bandwidth.
l Retain the default values for OSPF protocol parameters.

l Synchronize the NE time with the NMS server at an interval of one day. The daylight saving
time (DST) scheme is not used at the local area.
l Enable the 15-minute and 24-hour performance monitoring functions for all NEs.
l Do not configure subnets.
l Allocate IDs and IP addresses to NEs according to the DCN plan. For details, see Figure
8-11.
Figure 8-11 Allocated IDs and IP addresses (microwave chain network)

NMS
LAN switch
10.0.0.100
Regional
Backhaul
Network
9-21 9-22 9-23 9-24 9-99

129.9.0.21 129.9.0.22 129.9.0.23 129.9.0.24 129.9.0.99
0.0.0.0 RNC
0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
NE21 NE22 NE23 NE24 NE99
Extended ID-Basic ID
IP address
Radio link Ethernet link Gateway
NOTE
l The subnet mask for the IP address of each NE takes the same value 255.255.0.0.
l The access control function is enabled for the Ethernet port (IP address: 10.0.0.99) of NE99.
l The IP address allocated to each NE interlocks with the NE ID. Therefore, if the IP address of an NE
has not been changed manually, the NE automatically changes the IP address to the planned value
after the NE ID is changed.
l NE99 is an OptiX RTN 900 NE and therefore its configuration is not detailed in this example.
8.4.3.3 Configuration Procedure

This section describes the procedure for configuring a microwave chain network.
Precautions
If the NE ID and the values of NE communication parameters are changed during per-NE
commissioning, skip the operations.
Procedure
Step 1 Create NEs manually. For details, see A.3.1.2 Creating an NE Manually.
This table provides parameter values for manually creating NEs.

Parameter Value
Search Domain IP Address 129.9.255.255
Search User root
Search for NE Create NE after search Selected
Upload after create Selected
NE User root
Password password
NOTE
In this example, it is assumed that the IP address of the gateway NE has not been changed manually and is
unknown. Therefore, you need to search for NEs by using the 129.9.255.255 network segment as the search
domain. If the IP address of the gateway NE is known, it is recommended that you use the IP address of the
gateway NE as the search domain.
Normally, the icons of NE21 to NE24 should be displayed on Main Topology and all the NE
data should be uploaded successfully.
Step 2 Change NE IDs. For details, see A.3.1.4 Changing an NE ID.
This table provides parameter values for NE21 to NE24.
Parameter Value
NE21 NE22 NE23 NE24
New ID 21 22 23 24
New Extended 9 (default) 9 (default) 9 (default) 9 (default)

ID
Step 3 Configure NE communication parameters. For details, see A.3.6.1 Setting NE Communication
Parameters.
Parameter Value
NE21 NE22 NE23 NE24
IP 129.9.0.21 129.9.0.22 129.9.0.23 129.9.0.24
Gateway IP 0.0.0.0 (default) 0.0.0.0 (default) 0.0.0.0 (default) 0.0.0.0 (default)
Subnet Mask 255.255.0.0 255.255.0.0 255.255.0.0 255.255.0.0

(default) (default) (default) (default)
Extended ID 9 9 9 9

Parameter Value
NE21 NE22 NE23 NE24
Connection Common Common Common Common

Mode +Security SSL +Security SSL +Security SSL +Security SSL
Step 4 Configure inband DCN ports. For details, see A.3.6.5 Setting a Port for an Inband DCN.
This table provides parameter values for NE21 and NE23.
Parameter Value
1-SHUF3-2 Other ports
Enabled/Disabled Disabled Enabled (default value)
Step 5 Synchronize NE time. For details, see A.3.1.6 Synchronizing the NE Time.
Parameter Value
All the ports on all the NEs
Synchronous Mode Network management
Period (days) 1
Step 6 Create fibers using the search method. For details, see A.3.4.1 Creating a Fiber/Cable by Using
the Search Method.
Normally, all the microwave links and Ethernet cables are created successfully on Main
Topology.
Step 7 Create back-to-back microwave connections. For details, see A.3.4.4 Creating a Back-to-back
Radio Connection.
This table provides parameter values for creating back-to-back microwave connections.
Parameter Value
Source NE NE22
Sink NE NE23
----End
8.4.4 Configuration Example (Microwave Ring Network)

This section uses a microwave ring network as an example to describe how to configure the
network topology according to the network plan.


Figure 8-12 shows a microwave ring network configured according to the following
requirements:
l The network contains six OptiX RTN 380 NEs located at three sites. The NEs are managed
by the U2000.
l The local backhaul network is a third-party network and cannot be managed together with
the OptiX RTN equipment. Therefore, NE35 is configured as the gateway NE and it
communicates with the U2000 using the access control function.
l The NEs use the D1 to D3 bytes in microwave links or partial Ethernet bandwidth in GE
links for data communication network (DCN) communication that is implemented using
IP.
Figure 8-12 Networking diagram for a microwave ring network
NMS
NodeB 1
P&E
LAN switch
GE GE
NE31 NE36
P&E Regional
Backhaul
Network
RNC
GE GE NE35
NE32
GE GE
P&E
NodeB 2 NE33 NE34
NOTE

l On the NMS, the logical port of a COMBO port that functions as an optical GE port is 1-SHUF3-3
(GE2).
l On the NMS, the logical port of a COMBO port that functions as a 1+1 concatenation port is 1-
SHUF3-3. This port is valid only when DCN is being configured.


This section describes the parameters required for configuring a microwave ring network.
l Use the IP DCN solution.

l To prevent impact on NodeBs, disable the inband DCN function for the ports that receive/
transmit services from/to NodeBs on all NEs.
l Plan the management VLAN ID and bandwidth of the inband DCN for each NE as follows:
– Retain the default value 4094 for the management VLAN ID. The management VLAN
ID must be different from the VLAN ID carried by service packets.
– Retain the default value 512 kbit/s for the inband DCN bandwidth.
l Retain the default values for OSPF protocol parameters.
l Synchronize the NE time with the NMS server at an interval of one day. The daylight saving
time (DST) scheme is not used at the local area.
l Enable the 15-minute and 24-hour performance monitoring functions for all NEs.
l Do not configure subnets.
l Allocate IDs and IP addresses to NEs according to the DCN plan. For details, see Figure
8-13.
Figure 8-13 Allocated IDs and IP addresses (microwave ring network)

NMS
NE31 NE36
9-31 9-36 LAN switch
129.9.0.31 129.9.0.36 10.0.0.100
0.0.0.0 0.0.0.0
9-32 9-35
129.9.0.32 129.9.0.35 Regional Backhaul
0.0.0.0 0.0.0.0 Network
NE32 NE35
RNC
9-33 9-34
129.9.0.33 129.9.0.34
0.0.0.0 0.0.0.0
NE33 NE34
Extended ID-Basic ID
IP address
Radio link Ethernet link Gateway
NOTE
l The subnet mask for the IP address of each NE takes the same value 255.255.0.0.
l The access control function is enabled for the P&E port (IP address: 10.0.0.35) of NE35.
l The IP address allocated to each NE interlocks with the NE ID. Therefore, if the IP address of an NE
has not been changed manually, the NE automatically changes the IP address to the planned value
after the NE ID is changed.


This section describes the procedure for configuring a microwave ring network.
Precautions
If the NE ID and the values of NE communication parameters are changed during per-NE
commissioning, skip the operations.
Procedure
Step 1 Create NEs manually. For details, see A.3.1.2 Creating an NE Manually.
Parameter Value
Search Domain IP Address 129.9.255.255
Search User root
Search for NE Create an NE after it is Selected

found.
Upload after create Selected
NE User root
Password password
NOTE
In this example, it is assumed that the IP address of the gateway NE has not been changed manually and is
unknown. The NEs are searched for by using the 129.9.255.255 network segment as the search domain. If the
IP address of the gateway NE is known, it is recommended that you use the IP address of the gateway NE as
the search domain.
Normally, the icons of NE31 to NE36 should be displayed on Main Topology and all the NE
data should be uploaded successfully.
Step 2 Change NE IDs. For details, see A.3.1.4 Changing an NE ID.
Paramete Value
r
NE31 NE32 NE33 NE34 NE35 NE36
New ID 31 32 33 34 35 36
New 9 (default 9 (default 9 (default 9 (default 9 (default 9 (default

Extended value) value) value) value) value) value)
ID
Step 3 Configure NE communication parameters. For details, see A.3.6.1 Setting NE Communication
Parameters.

Paramete Value
r
IP 129.9.0.31 129.9.0.32 129.9.0.33 129.9.0.34 129.9.0.35 129.9.0.36
Gateway 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0

IP (default (default (default (default (default (default
value) value) value) value) value) value)
Subnet 255.255.0. 255.255.0. 255.255.0. 255.255.0. 255.255.0. 255.255.0.

Mask 0 (default 0 (default 0 (default 0 (default 0 (default 0 (default
Extended 9 9 9 9 9 9
ID
Connectio Common Common Common Common Common Common

n Mode +Security +Security +Security +Security +Security +Security
SSL SSL SSL SSL SSL SSL
Step 4 Configure access control. For details, see A.3.6.6 Configuring Access Control.
This table provides parameter values for NE35.
Parameter Value
1-SHUF3-2
Enabled/Disabled Enabled
IP 10.0.0.35
Step 5 Configure inband DCN ports. For details, see A.3.6.5 Setting a Port for an Inband DCN.
This table provides parameters of NE33 and NE36.
Parameter Value
1-SHUF3-2 Other Ports
Enabled/Disabled Disabled Enabled (default value)
Step 6 Synchronize NE time. For details, see A.3.1.6 Synchronizing the NE Time.

Parameter Value
All the ports on all the NEs
Synchronous Mode NMS
Period (days) 1
Step 7 Create fibers using the search method. For details, see A.3.4.1 Creating a Fiber/Cable by Using
the Search Method.
Normally, all the microwave links and Ethernet cables are created successfully on Main
Topology.
Step 8 Create back-to-back microwave connections. For details, see A.3.4.4 Creating a Back-to-back
Radio Connection.
This table provides parameter values for creating back-to-back microwave connections.
Parameter Value
Connection 1 Connection 2 Connection 3
Source NE NE31 NE32 NE34
Sink NE NE36 NE33 NE35
----End
8.5 Configuring Microwave Links

Before configuring services on a microwave link, you need to configure the microwave link.

Before configuring a microwave link, familiarize yourself with the basic concepts.
8.5.1.1 AM and AMAC

Adaptive modulation (AM) technology automatically adjusts the modulation scheme based on
channel quality. Adaptive modulation and adaptive channel spacing (AMAC) is the
enhancement of AM. AMAC can not only adjust the modulation scheme automatically but also
adjust the channel spacing automatically.
AM
When AM technology is enabled and the same channel spacing is used, the radio service
bandwidth varies according to the modulation scheme. The higher the modulation efficiency,
the higher the bandwidth of the transmitted services. With quality of service (QoS) technology,
packet services are groomed to queues with different priorities. Services in different queues are
then transmitted to the microwave port after the queue-scheduling algorithm has been run. Under
all channel conditions, the service capacity varies according to the modulation scheme.

l When conditions for channel quality are favorable good (such as on sunny days), the
equipment uses a higher-order modulation scheme to transmit more user services. This
improves transmission efficiency and spectrum utilization of the system.
l When conditions for channel quality are unfavorable (such as on stormy or foggy days),
the equipment uses a lower-order modulation scheme to ensure that higher-priority services
are transmitted first. If some lower-priority queues become congested due to a lack of
available bandwidth, some or all interfaces in these queues are discarded. This method
improves the anti-interference capabilities of a microwave link and ensures link availability
for high-priority services.
Figure 8-14 shows step-by-step AM shifting caused by weather changes and the impact of the
shifting on service throughput and reliability.
Figure 8-14 Adaptive modulation
64 32 16 32 64
QAM QAM 16 QAM QAM QAM
QAM QPSK
QPSK
Strong QPSK
Receive Signal Availability
64 QAM 99.96%
32 QAM 99.99%
16 QAM Low-priority Low-priority 99.995%

service service
QPSK 99.998%
QPSK strong 99.999%

High-priority service
Time
The AM technology used by the OptiX RTN 380 has the following features:
l Uses QPSK Strong, QPSK, 16QAM, 32QAM, 64QAM modulation schemes. Compared
with QPSK, QPSK Strong, using different parameters in forward error correction (FEC)
coding, has stronger error correction capability, and therefore has better receiver sensitivity.
It has, however, less air interface bandwidth.

l Can configure both the lowest-order modulation scheme (also called reference scheme or
modulation scheme of guaranteed AM capacity) and the highest-order modulation scheme
(also called nominal scheme or modulation scheme of full AM capacity).
l Can switch modulation schemes without changing the transmit frequency, receive
frequency, or channel spacing.
l Switches modulation schemes step-by-step.
l Features hitless shifting. When the modulation scheme is downshifted, low-priority
services are discarded while high-priority services are not affected. Shifting is successful
even when 100 dB/s channel fading occurs.
AMAC
AMAC is the enhancement of AM. If the lowest-order modulation scheme is set to QPSK Strong,
the AM function downshifts the modulation scheme to QPSK Strong when channel quality
deteriorates. Then, the AC function downshifts the channel spacing. The equipment uses the
available bandwidth to transmit high-priority services, reducing the impact of channel quality
deterioration on service signals.
Figure 8-15 shows the step-by-step shifting of the modulation scheme and channel spacing
caused by weather changes and the impact of the shifting on service throughput and reliability.
Figure 8-15 AMAC diagram
64 64
QAM 32 32 QAM
16 QPSK QPSK QPSK 16 QAM
QAM QAM QPSK QPSK QAM
Strong Strong Strong
@500M @500M
@250M
Receive Signal Availability
64 QAM 99.92%
32 QAM 99.96%
16 QAM 99.99%
Low-priority Low-priority
service service
QPSK 99.998%
QPSk Strong High-priority 99.999%

service
Time

l Channel spacing shifting is supported only when the modulation scheme downshifts to the
lowest-order modulation scheme QPSK Strong.
l When conditions for channel quality are unfavorable (such as on stormy or foggy days),
the equipment downshifts the channel spacing, which reduces the impact of channel quality
deterioration on service signals.
l AMAC features hitless shifting. When the channel spacing is downshifted, low-priority
services are discarded while high-priority services are not affected. Shifting is successful
even when 100 dB/s channel fading occurs.
8.5.1.2 RF Configuration Modes

OptiX RTN 380 supports three basic RF configurations: 1+0 non-protection configuration, 2+0
non-protection configuration, and 1+1 protection configuration.
1+0 Non-Protection Configuration

The 1+0 non-protection configuration indicates that the microwave link has one working channel
and no protection channel.
Figure 8-16 Typical configuration of 1+0 non-protection
NE1 NE2
2+0 Non-Protection Configuration

The 2+0 non-protection configuration indicates that the microwave link has two working
channels and no protection channel.
Figure 8-17 Typical configuration of 2+0 non-protection
RNC
RAN
NE1 NE3
NE2 NE4

1+1 HSB Protection Configuration

1+1 HSB protection is implemented based on the 1+1 hot backup of OptiX RTN 380s at both
ends of each microwave link hop.
Figure 8-18 Configuration of a 1+1 HSB group (for protecting 1xGE services without any
optical splitter used)
RNC
RAN
LAG LAG NE1 NE3 LAG LAG
COMBO COMBO
COMBO COMBO
LAG NE2 NE4 LAG
Figure 8-19 Configuration of a 1+1 HSB group (for protecting 2xGE services without any
optical splitter used)
RNC 1
RAN 1
LAG1 LAG1 NE1 NE3 LAG1 LAG1

P&E P&E
GE GE
LAG2COMBO LAG2
COMBO
LAG2 LAG2
COMBO COMBO
LAG2 LAG2
GE GE
RAN 2 P&E P&E

LAG1 NE2 NE4 LAG1 RNC 2

Figure 8-20 Configuration of a 1+1 HSB group (for protecting 1xGE services with an optical
splitter used)
RNC
RAN
NE1 NE3
GE
GE
COMBO COMBO
COMBO COMBO
GE GE
NE2 NE4
OptiX RTN 900 Radio link Ethernet link Optical splitter
8.5.1.3 E-LAG
When switching occurs on the NEs in a 1+1 HSB, an enhanced link aggregation group (E-LAG)
is required to implement switching for active and standby GE access links (HSB is short for hot
standby).
Introduction
E-LAG is a mechanism that implements multi-chassis link aggregation using the Link
Aggregation Control Protocol (LACP). It enhances Ethernet link reliability from the port level
to the equipment level.
As shown in Figure 8-21, two OptiX RTN 380s form a 1+1 HSB. A static link aggregation
group (LAG) that has only the master port is configured on each of the OptiX RTN 380s. The
master and slave OptiX RTN 380s exchange 1+1 HSB protection protocol packets so that the
LAGs on them form a multi-chassis E-LAG. A static, non-load sharing, and non-revertive LAG
must be configured on the IDU (or UNI equipment) connected to the OptiX RTN 380s. This
LAG works with the 1+1 HSB to implement switching for the active and standby GE access
links.

Figure 8-21 E-LAG application
LAG LAG
LAG LAG
GE GE
Cascade Cascade
cable cable
IDU IDU
GE Antenna Antenna GE
LAG LAG
E-LAG E-LAG
Principles
NOTE
This section describes the E-LAG implementation at the transmit end shown in Figure 8-21. The E-LAG
implementation at the receive end is similar.
1. Before E-LAG switching

NE 1 is the master NE in the 1+1 HSB. In normal cases, the 1+1 HSB protection protocol
sets the highest LAG system priority on NE 1 and a lower LAG system priority on NE 2.
Manually set the LAG system priority on the IDU to be much lower than the LAG system
priorities set on NE 1 and NE 2 (it is recommended that the value of the LAG system priority
on the IDU be greater than 1000). According to the LACP negotiation results, the link
between NE 1 and the IDU is in the Selected state, and the link between NE 2 and the IDU
is in the Unselected state. As a result, the IDU transmits services only to NE 1.
Figure 8-22 Before E-LAG switching

NE1
Master
Ethernet
service
Master port
LAG 1
GE
Protection
protocol
packets
Ethernet
GE LAG 2
service
Slave port
IDU LAG 3
Antenna
E-LAG
NE 2
Slave
LAG of the highest
system priority

2. E-LAG switching
When switching occurs on NE 1 and NE 2, they exchange the LAG system priorities, and
the 1+1 HSB protection protocol sets the highest LAG system priority on NE 2. According
to the LACP renegotiation results, the link between NE 1 and the IDU is in the Unselected
state, and the link between NE 2 and the IDU is in the Selected state. As a result, the IDU
transmits services only to NE 2.
Figure 8-23 E-LAG switching

NE 1
Master
Master port
GE LAG 1
Protection
protocol
packets
Ethernet
GE LAG 2
service
Slave port
IDU LAG 3
Antenna
Ethernet
service
E-LAG
NE 2
Slave
LAG of the highest
system priority
Feature Dependencies and Limitations

l The ports at both ends of each GE access link must have the same ID and type (optical port
or electrical port). The ports must work in auto-negotiation mode.
l The IDU (or UNI equipment) connected to NE 1 and NE 2 must be configured with a static,
non-load sharing, and non-revertive LAG. It is recommended that the value of the LAG
system priority on the IDU be greater than 1000.
8.5.1.4 Hop Management

The U2000 supports the hop management function, which allows for the simultaneous
modification of the NEs at the two ends of a hop.
Hop management applies to microwave links using the 1+0 non-protection configuration. If a
microwave link is not working correctly, the basic information about the peer NE is not
displayed.
The following parameters on the local and peer NEs on a microwave link hop are automatically
correlated: Link ID, IF Channel Bandwidth, AM, Modulation Mode of the Guaranteed AM
Capacity, Modulation Mode of the Full AM, and T/R Spacing (MHz). If any of the preceding

parameters is modified on one NE, the corresponding parameter is automatically modified on

the peer NE.
The following figure shows the window for configuring the hop management function.
8.5.2 Configuration Process (Microwave Links)

This section describes the processes of configuring the hop management function, power, and
other parameters for a microwave link.
Figure 8-24 shows the flowchart for configuring microwave links.

Figure 8-24 Flowchart for configuring microwave links
Required Start
Optional
Create a microwave 1+1
protection group.
Configure a hop of microwave link.
Configure Ethernet frame header

compression.
Set the maximum transmit power

and the power thresholds.
Create a microwave link after it is

found.
End
The steps in the flowchart are described as follows:

Configuring Microwave Links
Table 8-10 Process of configuring microwave links

1 Creating a A.7.3.14 Deleting an Required. Ensure that only the

microwav E-LAN Service or A. microwave port and the Ethernet port
e 1+1 7.3.13 Deleting an E- that participates in 1+1 protection are
protection Line Service configured with services. If you
group configure services on other Ethernet
ports, 1+1 protection configuration will
fail.
NOTE
By default, an OptiX RTN 380 creates a
bridge-based E-LAN service. All ports of
the OptiX RTN 380 are mounted to the
bridge. The Ethernet ports that do not
participate in 1+1 protection will result in a
1+1 protection configuration failure.
Therefore, you must delete this E-LAN
service.
A.7.2.1 Creating a This step is ignored when an optical

LAG splitter is used and is required when no
optical splitter is used.
Configure a LAG on each of the main
OptiX RTN 380s and each of the
standby OptiX RTN 380s. The LAG has
only one member port that receives and
transmits Ethernet services.
Set parameters as follows:
l Set LAG Type to Static.
l Set Reversion Mode to Non-
Revertive.
l Set Load Balancing to Non-
Sharing.
l Set Master Port to the port that
receives and transmits Ethernet
services. Do not set Standby
Ports.

A.5.3 Creating a Required. Set parameters as follows:

Microwave 1+1 l In the scenario where optical
Protection Group splitters are used, set Service
Protection Mode to Split Mode. In
the scenario where no optical
splitters are used, set Service
Protection Mode to LAG Mode.
l Set Working Mode to HSB.
l Set Working/Protection Unit
Type to Working Unit for the main
OptiX RTN 380 and Protection
Unit for the standby OptiX RTN
380.
l It is recommended that you set
Reversion Mode to the default
value Revertive Mode.
l WTR Time(s) is available only
when Reversion Mode is set to
Revertive Mode.
l It is recommended that you set
Enable Reverse Switching to
Enable.
l Set Service port to the Ethernet port
that receives/transmits services.
l Set Working Mode, Reversion
Mode, WTR Time(s), and Enable
Reverse Switching to the same
values for the OptiX RTN 380s at
both ends of the hop of microwave
link.
NOTE
If 1+1 protection configuration fails, check
that:
l Working Mode is set to the default
value Auto-Negotiation for Service
port on the main and standby OptiX
RTN 380s.
l Ethernet services are configured only
on Service port that participates in 1+1
protection.
l The COMBO ports that function as 1+1
cascade ports cannot be configured with
any Ethernet services.
l The COMBO ports on the main and
standby OptiX RTN 380s are properly
connected using an optical fiber.

2 A.5.1 Configuring a Single Hop of Required. Set parameters as follows:

Microwave Link l Link ID, IF Channel Bandwidth,
AMAC Status, Guaranteed
AMAC Capacity, Full AMAC
Capacity, and T/R Spacing
(MHz) of the local NE and the peer
NE on a hop of microwave link are
automatically correlated. If any of
the preceding parameters is
modified on one NE, the parameter
on the peer NE is automatically
modified accordingly.
l Set Link ID, TX Frequency
(MHz), TX Power (dBm), and T/R
Spacing (MHz) according to the
network plan.
l Set Transmit Status to unmute for
the main and standby microwave
links.
l Set Power to Be Received(dBm) to
the received signal level specified in
the network plan. The antenna non-
alignment indication function is
enabled only after this parameter is
set. When the antenna misalignment
indicating function is enabled, if the
actual receive power is 3 dB lower
than the power expected to be
received, the RADIO_RSL_BE-
YONDTH alarm is reported. After
the antennas are aligned for
consecutive 30 minutes, the NE
automatically disables the antenna
non-alignment indication function.
NOTE
l All parameters on the main and standby
NEs in a 1+1 hot standby (HSB)
protection group must be set
consistently.
l Data on the two main NEs at the ends
of a hop of microwave link must
correspond with each other. So does the
data on the standby NEs.
3 A.5.6 Configuring Ethernet Frame Required if Ethernet frame header

Header Compression compression is enabled.
Set related parameters according to the
network plan.

4 A.5.7 Setting the Maximum Optional.

Transmit Power and the Power Set Maximum Transmit Power
Thresholds according to the network plan when the
automatic transmit power control
(ATPC) function is enabled. If you want
to calculate how long the transmit/
receive power remains within the
maximum and minimum power
thresholds, you can set the power
thresholds.
NOTE
Configurations on the main and standby
NEs in a 1+1 protection group must be the
same.
5 A.3.4.1 Creating a Fiber/Cable by In normal cases, Main Topology

Using the Search Method displays the previously created
microwave links.
8.5.3 Configuration Example (Microwave Links on a Chain

Network)
This section uses microwave links on a chain network as examples to describe how to configure
microwave links according to the network plan.

Configure the microwave links on the chain network according to 8.4.3 Configuration Example
(Microwave Chain Network) and the following requirements:
l Enable AMAC for all microwave links, because they carry Ethernet services.
l Table 8-11 provides the requirements on the services from NodeB 1 and RAN 1.
Table 8-11 Capacity of services from NodeB 1 and RAN 1
Service Capacity NodeB 1 RAN 1
Capacity of high-priority 40 100

Ethernet services (Mbit/s)
Capacity of low-priority 60 600


NOTE
High-priority services are services that require transmission guarantees. High-priority services must not
be discarded in modulation scheme shifts. Low-priority services are services that do not require
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts. The
common service priorities are provided in Table 8-12.
Table 8-12 Common service priorities
Service Type Priority
Voice, signaling, and OM Ethernet High

services
Streaming media, background, and Low

interactive Ethernet services, for example,
Internet services
Figure 8-25 Networking diagram for microwave links on a chain network

NMS
RNC
LAN switch
201 202
81125M 81375M Regional
71125M 71375M Backhaul Network
250M 250M
1+0 1+0
V-polarization H-polarization
Tx low Tx high Tx high Tx low
P&E GE GE
P&E
NodeB 1 P&E NE99

NE21 NE22 NE23 NE24
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
RAN 1 Channel spacing
RF configuarion
Polarization

This section describes the parameters required for configuring microwave links on a chain
network.

Basic information about microwave links

Obtain basic information about microwave links based on the spectrum allocation on a
microwave network and the required microwave transmission capacity, as listed in Table
8-13.
Table 8-13 Basic information about microwave links

Parameter Link (NE21–NE22) Link (NE23–NE24)
Link ID 201 202
TX High Site NE22 NE23
TX Low Site NE21 NE24
TX frequency at the TX 81125 81375

high site (MHz)
TX frequency at the TX low 71125 71375

site (MHz)
T/R Spacing (MHz) 10000 10000
Radio Working Mode 250 250
RF Configuration Mode 1+0 1+0
Polarization Direction V (vertical polarization) H (horizontal polarization)
AMAC Attribute Information

Compute AMAC attribute information based on Ethernet service capacity and availability
requirements, as listed in Table 8-14.
Table 8-14 AMAC attribute information

AMAC Status Enabled Enabled
Guaranteed AMAC QPSK Strong QPSK Strong

Capacity
Full AMAC Capacity 16QAM 64QAM
NOTE
The microwave capacity and the AMAC function are under license control.

Power and ATPC Information

Obtain information about the microwave link power and automatic transmit power control
(ATPC) by using microwave network planning software such as Pathloss, as listed in Table
8-15.
Table 8-15 Power and ATPC information
TX Power (dBm) 10 (NE21) 8 (NE23)

10 (NE22) 8 (NE24)
RX Power (dBm) -43 (NE21) -48 (NE23)

-43 (NE22) -48 (NE24)
ATPC Disabled Disabled
NOTE
l The transmit power and receive power are calculated in AMAC guaranteed capacity mode.
l In this example, ATPC is disabled.

This section describes the procedure for configuring microwave links on a microwave chain
network.
Procedure
Step 1 Manage a hop of microwave link. For details, see A.5.1 Configuring a Single Hop of
Microwave Link.
l Basic parameters
Parameter Value
Link (NE21–NE22) Link (NE23–NE24)
Link ID 201 202
l IF parameters
Parameter Value
IF Channel Bandwidth 250M 250M

Parameter Value
Guaranteed AMAC QPSK Strong QPSK Strong

Capacity
l RF parameters
Parameter Value
TX Frequency (MHz) 71125 (NE21) 82375 (NE23)

81125 (NE22) 72375 (NE24)
APTC Disabled Disabled
TX Power (dBm) 10 8
Power to Be Received -43 -48

(dBm)
TX Status unmute unmute
Polarization direction V H
----End
8.5.4 Configuration Example (Microwave Links on a Ring Network)

This section uses microwave links on a ring network as examples to describe how to configure
microwave links according to the network plan.

Configure the ring network according to 8.4.4 Configuration Example (Microwave Ring
Network) and the following requirements:
l Enable AMAC for all microwave links, because they carry Ethernet services.
l The service capacity of each NodeB is provided in Table 8-16.

Table 8-16 Service capacity of each NodeB

Service Capacity NodeB 1 NodeB 2
NOTE


services

Internet services

Figure 8-26 Networking diagram for microwave links on a ring network
NMS
NodeB 1
301
81125M Tx low Tx low 303 LAN
71125M 81625M switch
250M 71625M
1+0 250M
V-polarization 1+0
V-polarization
NE31 NE36
Tx high Tx high Regional
Backhaul
Network
RNC
NE32 NE35
Tx high Tx low
NodeB 2 NE33 NE34

302
81375M
71375M Link ID
250M Tx high station Tx Freq.
1+0 Tx low station Tx Freq.
H-polarization Channel spacing
RF configuarion
Polarization

This section describes the parameters required for configuring microwave links on a ring
network.
Basic Information About Microwave Links

8-18.
Parameter Link (NE31–NE32) Link (NE33–NE34) Link (NE35–NE36)
Link ID 301 302 303
TX High Site NE32 NE33 NE35
TX Low Site NE31 NE34 NE36
TX frequency at the 81125 81375 81625

TX high site (MHz)

TX frequency at the 71125 71375 71625

TX low site (MHz)
T/R Spacing (MHz) 10000 10000 10000
Radio Working 250 250 250

Mode
RF Configuration 1+0 1+0 1+0

Mode
Polarization V (vertically H (horizontally V (vertically

Direction polarized) polarized) polarized)

AMAC Status Enabled Enabled Enabled
Guaranteed AMAC QPSK Strong QPSK Strong QPSK Strong

Capacity
Full AMAC 16QAM 16QAM 16QAM

Capacity
NOTE

8-20.
TX Power (dBm) 10 (NE31) 10 (NE33) 11 (NE35)

10 (NE32) 10 (NE34) 11 (NE36)

RX Power (dBm) -46 (NE31) -45 (NE33) -43 (NE35)

-46 (NE32) -45 (NE34) -43 (NE36)
ATPC Disabled Disabled Disabled
NOTE

This section describes the procedure for configuring microwave links on a microwave ring
network.
Procedure
Microwave Link.
l This table provides parameter values for NE31 to NE36.
– Basic parameters
Parameter Value
Link (NE31– Link (NE33– Link (NE35–

NE32) NE34) NE36)
Link ID 301 302 303
– IF parameters
Parameter Value

NE32) NE34) NE36)
IF Channel 250M 250M 250M

Bandwidth
AMAC Status Enabled Enabled Enabled
Guaranteed QPSK Strong QPSK Strong QPSK Strong

AMAC Capacity
Full AMAC 16QAM 16QAM 16QAM

Capacity
– RF parameters

Parameter Value

NE32) NE34) NE36)
TX Frequency 71125 (NE31) 81375 (NE33) 81625 (NE35)

(MHz) 81125 (NE32) 71375 (NE34) 71625 (NE36)
T/R Spacing 10000 10000 10000

(MHz)
APTC Disabled Disabled Disabled
TX Power (dBm) 10 10 11
Power to Be -46 -45 -43

Received (dBm)
TX Status unmute unmute unmute
Polarization V H V
direction
----End
8.5.5 Configuration Example (Large-Capacity Backhaul Microwave

Links with 1+1 Protection)
This section uses a large-capacity backhaul microwave link as an example to describe how to
configure microwave links according to the network plan.

NOTE
On this network, LAGs configured for the OptiX RTN 900 equipment or switches work together with the OptiX
RTN 380 equipment to implement 1+1 protection. If optical splitters are used to achieve 1+1 protection, see
Networking Diagram in Feature Description for details.
Figure 8-27 shows a hop of important microwave link. Two OptiX RTN 380 devices are
cascaded at each site for receiving two channels of GE services (from RAN 1 and RAN 2) from
the OptiX RTN 900 convergence node. 1+1 HSB protection is configured to guarantee reliable
transmission of the GE services.
l Enable AMAC for the microwave links.
l Table 8-21 provides the requirements on the services from the RAN 1 and RAN 2.

Table 8-21 Capacity of services from RAN 1 and RAN 2

Service Capacity RAN 1 RAN 2


NOTE


services

Internet services
Figure 8-27 Networking diagram for 1+1 HSB protection
RNC 1
RAN 1
101
81125M
71125M
LAG1 LAG1 NE11 250M NE13 LAG1 LAG1
P&E 1+1 P&E
V-polarization
GE GE
Tx high Tx low
LAG2COMBO LAG2
COMBO
LAG2 LAG2
COMBO COMBO
LAG2 LAG2
GE GE
RAN 2 P&E P&E

Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Channel spacing
OptiX RTN 900 Radio link Ethernet link RF configuarion
Polarization


This section describes the parameters required for configuring large-capacity backhaul
microwave links with 1+1 protection.
Basic Information About Microwave Links

8-23.

Link ID 101
TX High Site NE11 NE12
TX Low Site NE13 NE14
TX frequency at the TX 81125

high site (MHz)
TX frequency at the TX low 71125

site (MHz)
Radio Working Mode 250
RF Configuration Mode 1+1
Polarization Direction V (vertical polarization)


Guaranteed AMAC QPSK QPSK

Capacity
NOTE


8-25.
TX Power (dBm) 8 8
RX Power (dBm) -46 -46
ATPC Disabled Disabled
NOTE
1+1 HSB Protection Information

On the OptiX RTN 380, in order to implement 1+1 HSB protection, configure a static, non-load
sharing, and non-revertive LAG for each involved Ethernet port. Each LAG contains only one
member port.
Table 8-26 and Table 8-27 provide the LAG configurations and 1+1 HSB configurations of
NE11, NE12, NE13, and NE14.
NOTE

l On the NMS, the logical port of a COMBO port that functions as an optical GE port is 1-SHUF3-3(GE2).
l On the NMS, the logical port of a COMBO port that functions as a 1+1 concatenation port is 1-SHUF3-3.
This port is valid only when DCN is being configured.
Table 8-26 LAG configuration information
Parameter Value (NE11/NE12/NE13/NE14)
LAG1 LAG2
LAG Name LAG1 LAG2
LAG Type Static Static
Revertive Mode Non-Revertive Non-Revertive
Load Balancing Non-Sharing Non-Sharing
System Priority 32768 32768

LAG1 LAG2
Master Board 1-SHUF3 1-SHUF3
Main Port 1-SHUF3-2(GE1) 1-SHUF3-4(GE3)
Table 8-27 1+1 HSB configuration information

Parameter Main NEs (NE11 and Standby NEs (NE12 and
NE13) NE14)
Service Protection Mode LAG Mode LAG Mode
Working Mode HSB HSB
Revertive Mode Revertive Mode Revertive Mode
WTR Time(s) 600 600
Enable Reverse Switching Enable Enable
Working/Protection Unit Work Unit Protection Unit

Type
IF Port 1-SHUF3-1(IF) 1-SHUF3-1(IF)
Service Port 1-SHUF3-2(GE1) 1-SHUF3-2(GE1)

1-SHUF3-4(GE3) 1-SHUF3-4(GE3)
NOTE
LAG1 and LAG2 need to be configured for the OptiX RTN 900 NE interconnected with the OptiX RTN 380
to implement 1+1 HSB protection. The configurations on the OptiX RTN 900 NE are not provided here.
l Create static, non-load sharing, and non-revertive LAGs for it. The priority values are recommended to be
larger than 1000 for the LAGs.
l Only ports of the same type (electrical or optical) can be added in to a LAG, and Working Mode must be
set to Auto-Negotiation for the ports.

This section describes the procedure for configuring large-capacity backhaul microwave links
with 1+1 protection.
Procedure
Microwave Link.
l Basic parameters

Parameter Value
Link ID 101 101
l IF parameters
Parameter Value
IF Channel Bandwidth 250M 250M
Guaranteed AMAC QPSK QPSK

Capacity
l RF parameters
Parameter Value
TX Frequency (MHz) 81125 (NE11) 81125 (NE12)

71125 (NE13) 71125 (NE14)
APTC Disabled Disabled
TX Power (dBm) 8 8
Power to Be Received -46 -46

(dBm)
TX Status unmute unmute
Polarization direction V V
Step 2 Delete the default E-LAN service. For details, see A.7.3.10 Changing Logical Ports Mounted
to a Bridge.
NOTE
By default, an OptiX RTN 380 NE is configured with a bridge-based E-LAN service which is mounted to all
ports. In this example, the COMBO port functions as a 1+1 cascade port cannot carry Ethernet services. If it
carries Ethernet services, 1+1 protection cannot be created. Therefore, delete the E-LAN service before
configuring E-LAN or E-Line services according to the service plan.
Step 3 Create LAGs. For details, see A.7.2.1 Creating a LAG.
This table provides the LAG configuration information for NE11, NE12, NE13, and NE14.

Table 8-28 LAG configuration information
LAG1 LAG2
LAG Name LAG1 LAG2
Revertive Mode Non-Revertive Non-Revertive
Load Balancing Non-Sharing Non-Sharing
Master Board 1-SHUF3 1-SHUF3
Step 4 Create microwave 1+1 protection groups. For details, see A.5.3 Creating a Microwave 1+1
Protection Group.
This table provides the 1+1 HSB configuration information for NE11, NE12, NE13, and NE14.
Table 8-29 1+1 HSB configuration information
Parameter Main NEs (NE11 and Standby NEs (NE12 and

NE13) NE14)
Service Protection Mode LAG Mode LAG Mode
Working Mode HSB HSB
Revertive Mode Revertive Mode Revertive Mode
WTR Time(s) 600 600
Enable Reverse Switching Enable Enable
Working/Protection Unit Work Unit Protection Unit

Type
IF Port 1-SHUF3-1(IF) 1-SHUF3-1(IF)
Service Port 1-SHUF3-2(GE1) 1-SHUF3-2(GE1)

----End
8.6 Configuring Native Ethernet Services

Native Ethernet services include Native Ethernet line (E-Line) services and Native Ethernet local
area network (E-LAN) services.


Before configuring Native Ethernet services, familiarize yourself with the basic concepts.
8.6.1.1 Auto-negotiation
The auto-negotiation function allows network equipment to send information about its supported
working mode to the opposite end and to receive corresponding information back.
Auto-negotiation Function of GE Electrical Ports

GE electrical ports on OptiX RTN 380 support four working modes: 10M full-duplex, 100M
full-duplex, 1000M full-duplex, and auto-negotiation. Table 8-30 lists auto-negotiation rules
for GE electrical ports.
Table 8-30 Auto-negotiation rules for GE electrical ports (when the local GE electrical port
works in 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
10M half-duplex 10M half-duplex
10M full-duplex 10M half-duplex
100M half-duplex 100M half-duplex
100M full-duplex 100M half-duplex
1000M full-duplex 1000M full-duplex
NOTE
As provided in Table 8-30, when the opposite GE electrical port works in 10M full-duplex or 100M full-duplex
mode, auto-negotiation does not necessarily achieve full matching between the two ends. As a result, some
packets are lost. Therefore, when the opposite GE electrical port works in 10M full-duplex or 100M full-duplex
mode, 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 flow control.
Auto-negotiation Function of GE Optical Ports

GE optical ports support only the 1000M full-duplex working mode. Auto-negotiation of GE
optical ports is used only for negotiating flow control.
8.6.1.2 Flow Control Function

When equipment fails to handle the traffic received at the port due to poor data processing/
transferring capability, the line becomes congested. This also causes buffer overflow and

therefore some packets are discarded. To reduce the number of packets to be discarded, take
appropriate flow control measures.
Half-duplex Ethernet uses a back-pressure mechanism to control flow. Full-duplex Ethernet uses
PAUSE frames to control flow. Currently, half-duplex Ethernet is not widely applied; therefore,
the flow control function is currently implemented for full-duplex Ethernet.
The flow control function on the equipment is classified into two types: auto-negotiation flow
control and non-auto-negotiation flow control.
Auto-negotiation Flow Control

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

The port can transmit PAUSE frames in case of congestion but cannot process received
PAUSE frames.
l Symmetric PAUSE
The port can transmit PAUSE frames and process 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 received PAUSE frames.
– Processes received PAUSE frames but cannot transmit PAUSE frames.
l Disabled
The port does not transmit or process PAUSE frames.
NOTE
OptiX RTN 380 supports only two auto-negotiation flow control modes: Disabled and Symmetric Pause, which
correspond to Disabled and Enable Symmetric Flow Control on the network management system (NMS)
respectively.
Non-auto-negotiation Flow Control

When an Ethernet port works in a fixed working mode, use non-auto-negotiation flow control.
The non-auto-negotiation flow control modes include the following:
l Send only
The port can transmit PAUSE frames in case of congestion but cannot process received
PAUSE frames.
l Receive only
The port can process received PAUSE frames but cannot transmit PAUSE frames in 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
OptiX RTN 380 supports only two auto-negotiation flow control modes: Disabled and Symmetric Pause, which
correspond to Disabled and Enable Symmetric Flow Control on the NMS respectively.
8.6.1.3 Port Description

OptiX RTN 380 provides three GE ports.
Figure 8-28 shows the physical Ethernet ports on the OptiX RTN 380. Table 8-31 provides the
logical ports and functions of the physical Ethernet ports.
Figure 8-28 Ports on the OptiX RTN 380
GE COMBO
P&E
Table 8-31 Description of ports on the OptiX RTN 380

Physical Logical Port Description
Port
P&E 1-SHUF3-2 A P&E port can function as an electrical GE port.

(GE1)
COMBO 1-SHUF3-3 l When 1+1 HSB protection has not been configured for OptiX RTN 380,
(GE2) the COMBO port functions as an optical GE port to transmit/receive
Ethernet services.
l When 1+1 protection has been configured for OptiX RTN 380, the
COMBO port functions a cascade port in a 1+1 protection group and is
used to cascade two OptiX RTN 380s.
GE 1-SHUF3-4 A GE port with an SFP module can function as an optical GE port.

(GE3)
8.6.1.4 MAC Address Table Management

Entries in a MAC address table show the mapping between MAC addresses and ports. Entries
can be classified into dynamic entries, static entries, and blacklist entries.

Table 8-32 Entries in a MAC address table

Entry Description
Dynamic entry A dynamic entry is learned by a bridge in SVL or IVL mode. A

dynamic entry will be aged out. It is lost after the Ethernet processing
unit is cold reset.
Static entry A static entry is manually added by a network administrator to the

MAC address table on the network management system (NMS).
Generally, a static entry is configured for a port connected to a device
that has a known MAC address and that carries constant and heavy
traffic. A static entry will not be aged out. It is not lost after the
Ethernet processing unit is reset.
Blacklist entry A blacklist entry is also called a MAC disabled entry or a black hole
entry. It is configured by a network administrator. An Ethernet frame
whose source or destination MAC address is specified in a blacklist
entry is discarded. A blacklist entry will not be aged out. It is not
lost after the Ethernet processing unit is reset.
NOTE
If no new packet is received from a MAC address within a specified period of time, the corresponding
entry is automatically deleted. This mechanism is called aging and the specified period of time is called
aging time.
8.6.1.5 VLAN Forwarding Tables for E-Line Services

Generally, the VLAN ID carried by a VLAN-based Ethernet line (E-Line) service does not need
to be changed. If it is necessary to change a VLAN ID, you must configure a VLAN forwarding
table.
If VLAN ID change is required for a VLAN-based E-Line service, you must specify the source
VLAN ID and sink VLAN ID, as shown in the E-Line service information table in Figure
8-29. In addition, you must configure a VLAN forwarding table to allow VLAN switching
between the source and the sink.
In Figure 8-29, service 1 from NodeB 1 and service 2 from NodeB 2 are transmitted through
NE 3 to the radio network controller (RNC). Services 1 and 2 have the same VLAN ID of 100.
To prevent a VLAN ID conflict on NE 3, you can configure a VLAN forwarding table on NE
2 so that the VLAN ID of service 2 changes from 100 to 200 on NE 2.

Figure 8-29 Application of the VLAN forwarding table for an E-Line service (on NE 2)
Service 1 NE 1
Service 1 VLAN ID: 100
VLAN ID: 100 E-Line Port 1
Port 2 Service 1
Service 2 NE 3 VLAN ID: 100
VLAN ID: 200 NodeB 1
E-Line
Port 1 Port 2 Transmission
Port 3 network
E-Line
RNC NE 2
E-Line Port 1
Port 2
Service 2
Service 2 NodeB 2 VLAN ID: 100
VLAN ID: 200
VLAN forwarding table

Source Source Sink
Sink Port
Port VLAN ID VLAN ID
Port 1 100 Port 2 200
Port 2 200 Port 1 100
E-Line service information table

Source Source Sink
Sink Port
Port VLAN ID VLAN ID
Port 1 100 Port 2 200
8.6.1.6 Split Horizon Groups

To separate services that converge and to prevent broadcast storms resulting from service loops,
configure a split horizon group for Ethernet local area network (E-LAN) services at specified
nodes. The logical ports within the same split horizon group cannot forward packets to each
other.
Figure 8-30 shows a typical application of a split horizon group. Each NE on the network is
configured with E-LAN services, and the microwave port and two GE ports on each NE are
configured as bridge-mounted logical ports. If a split horizon group is not configured on NE1,
its microwave port and the GE port connected to NE4 forward packets to each other, causing a
service loop and a broadcast storm. If a split horizon group is configured on NE1 and if its
microwave port and the GE port connected to NE4 are configured as members of the split horizon
group, the two ports do not forward packets to each other.

Figure 8-30 Split horizon group
NE 2 NE 1
NodeB 1 RNC
Split
horizon
group
NE 3 NE 4
NodeB 2 NodeB 3
Microwave link Ethernet link
NOTE
l Ethernet ring protection switching (ERPS) prevents service loops on ring networks. If ERPS has already
been enabled for a ring network, do not configure a split horizon group because it may affect ERPS
functionality.
l OptiX RTN 380 allows only physical ports to be configured into a split horizon group.Therefore, the logical
ports mapped from a physical port are added to the split horizon group automatically.
8.6.1.7 Protection for Native Ethernet Services

OptiX RTN 380 supports two protection modes for Native Ethernet services: Ethernet ring
protection switching (ERPS) and link aggregation group (LAG).
ERPS
ERPS is applicable to ring physical networks and can provide protection for the Ethernet local
area network (E-LAN) services between all the ring network nodes. 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. When a link fails or an NE becomes faulty, the RPL node unblocks its RPL port so
that services can be switched from the faulty point to the RPL port for transmission. In this
manner, protection for the ring network is achieved.
The Ethernet ring network shown in Figure 8-31 is configured with ERPS. Normally, NE1
blocks its GE port connected to NE2 to prevent a loop. When links between NE4 and NE5 are
faulty, NE1 unblocks its GE port. Services between NE4 and NE5 are switched to the route NE4-
NE3-NE2-NE1-NE8-NE7-NE6-NE5.

Figure 8-31 Implementation of ERPS

NE4 NE3
NE5 NE2
NodeB
RNC
NodeB
NE6
NE1
NE7 NE8
NodeB NodeB
Protection switching
NE4 NE3
Failure
NE5 NE2
NodeB
RNC NodeB
NE1
NE6
NE7 NE8
NodeB NodeB
Ethernet cable
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 8-32, the LAG feature provides the following functions:
l Increased link capacity

The LAG feature provides users with a cost-effective method for increasing link bandwidth.
Users obtain data links with higher bandwidths by combining multiple physical links into

one logical link without having to upgrade existing equipment. The bandwidth of the logical
link is equal to the sum of the bandwidths of the physical links. The aggregation module
distributes traffic to different members by using a load balancing algorithm, achieving load
balancing at the link level.
l Improved link availability
The links in a LAG provide backup for one another dynamically. When a link fails, another
link in the LAG quickly takes over.
Figure 8-32 LAG

2.5Gbit/s
LAG LAG
3xGE 3xGE
IDU/Switch IDU/Switch
8.6.2 Native Ethernet Service Types

Native Ethernet services are classified into four types.
8.6.2.1 Transparently Transmitted Point-to-Point E-Line Service

The transparently transmitted point-to-point Ethernet line (E-Line) service is 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 8-33 describes the transparently transmitted point-to-point E-Line service model.
Table 8-33 Transparently transmitted point-to-point E-Line service model

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

PORT (sink) Null (sink) transparently
transmits all the
received Ethernet
frames to the sink
port.

Service Model Traffic Flow Service Direction Encapsulation Description

Type
Model 2 PORT (source) UNI-UNI 802.1Q (source) The source port

NOTE PORT (sink) 802.1Q (sink) processes the
In service model 2, incoming Ethernet
ports process the frames based on its
received Ethernet TAG attribute, and
frames according to
then sends the
their TAG attributes.
Therefore, service processed Ethernet
model 2 is not a real frames to the sink
transparent port. The sink port
transmission model processes the
and is not Ethernet frames
recommended.
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.
Typical Application
Figure 8-33 shows the typical application of service model 1.
Figure 8-33 Typical application of service model 1

NE 1 NE 2
Port 1 E-Line Port 2 Port 2 E-Line Port 1

Service 1 Transmission Service 1
network
In model 1, Ethernet service 1 is transmitted to NE1 through port 1, regardless of whether the
Ethernet service carries an unknown VLAN ID or no VLAN ID. Port 1 transparently transmits
Ethernet service 1 to port 2. Port 2 transmits Ethernet service 1 to NE2. Service processing on
NE2 is the same as that on NE1.
In model 2, Ethernet service 1 is transmitted to NE1 through port 1, regardless of whether the
Ethernet service carries an unknown VLAN ID or no VLAN ID. Port 1 and Port 2 process the
incoming packets based on their own TAG attributes. Then, Port 2 sends Ethernet service 1 to
NE2. Service processing on NE2 is the same as that on NE1.
8.6.2.2 VLAN-based E-Line Service

You can use VLANs to separate Ethernet line (E-Line) services, which allows the E-Line
services to share one physical transmission channel. E-Line services separated in this manner
are called VLAN-based E-Line services.
Service Model
Table 8-34 provides information about the VLAN-based E-Line service model.

Table 8-34 VLAN-based E-Line service model

Service Type Service Flow Service Direction Encapsulation Service
Type at a Port Description
VLAN-based E- PORT+VLAN UNI-UNI (UNI IEEE 802.1Q The source port

Line service (source) stands for user-to- (source) processes incoming
PORT+VLAN network interface.) IEEE 802.1Q (sink) Ethernet frames
(sink) based on its tag
attribute, and then
sends Ethernet
frames containing a
specific VLAN ID
to the sink port. The
sink port processes
the Ethernet frames
based on its tag
attribute, and then
transmits the
processed Ethernet
frames.
Typical Application
Figure 8-34 shows a typical application of the VLAN-based E-Line service model. Services 1,
2, 3, and 4 from four NodeBs converge through a transmission network to a radio network
controller (RNC).
l Services 1, 2, 3, and 4 carry different VLAN IDs.
l On NE 1, services 1 and 2 are received at port 2 and port 3, respectively, and forwarded
through port 1. They share the same channel but are isolated by VLANs.
l On NE 2, services 3 and 4 are received at port 2 and port 3, respectively, and forwarded
through port 1. They share the same channel but are isolated by VLANs.
l On NE 3, services 1 and 2 are received at port 2, services 3 and 4 are received at port 3,
and all four services are forwarded through port 1. All the services share the same channel
but are isolated by VLANs.
l Ports 2 and 3 on NE 1, NE 2, and NE 3 process incoming Ethernet frames based on their
tag attributes and transmit the Ethernet frames to port 1. Port 1 processes outgoing Ethernet
frames based on its tag attribute. Because the services have different VLAN IDs, they can
share ports 1 on NE 1, NE 2, and NE 3.

Figure 8-34 VLAN-based E-Line service model
Service 1
VLAN ID: 100 Service 1
VLAN ID: 100 NE 1 Service 1
Service 2 Port 2
Service 2 VLAN ID: 100
VLAN ID: 200 NodeB 1
Service 3 VLAN ID: 200 E-Line
VLAN ID: 300 Port 1
Service 4 Port 3
NE 3 E-Line
VLAN ID: 400 Service 2
E-Line VLAN ID: 200
Port 1 Port 2 NodeB 2
Transmission
Port 3 network
E-Line
RNC
Port 2
E-Line Service 3
Port 1 NodeB 3 VLAN ID: 300
Port 3
Service 3 E-Line
VLAN ID: 300
Service 4 NE 2 Service 4
VLAN ID: 400 VLAN ID: 400
NodeB 4
8.6.2.3 QinQ-Based E-Line Services

S-VLAN tags can be used to separate several E-Line services so that these services share one
physical channel for transmission. Therefore, S—VLAN tags can separate more services than
C-VLAN tags.These services are called QinQ-based E-Line services.
Service Model
Table 8-35 shows the QinQ-based E-Line service models.
Table 8-35 QinQ-based E-Line service models

Service Service Flow Service Port Encapsulation Service Description
Model Direction Mode
Model 1 PORT (source) UNI-NNI 802.1Q (source)a The source port only receives
QinQ link (sink) the Ethernet frames that carry
QinQ (sink)
C-VLAN tags. After
receiving the Ethernet
frames, it adds the S-VLAN
tag that corresponds to the
QinQ link to the Ethernet
frames and then transmits the
Ethernet frames to the sink
port to which the QinQ link is
connected.

Service Service Flow Service Port Encapsulation Service Description

Model Direction Mode
Model 2 PORT+C-VLAN UNI-NNI 802.1Q (source)a The source port adds the S-
(source) VLAN tag that corresponds
QinQ (sink)
QinQ link (sink) to the QinQ link to all the
Ethernet frames that carry
specific C-VLAN tags and
then transmits the Ethernet
frames to the sink port to
which the QinQ link is
connected.
NOTE
a: Set Tag to Tag Aware.
Typical Application
Service 1 and service 2 carry different unknown C-VLAN tags. Service 1 is transmitted to NE1
through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag
to service 1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then
transmitted to port 3. Port 3 transmits service 1 and service 2 to NE2.
NE2 processes service 1 and service 2 in the same manner as NE1.

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
Service 2 e E-Lin Service 2
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 transmitted to NE1 through
port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag to service
1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then transmitted
to port 3. Port 3 transmits service 1 and service 2 to NE2.

NE2 processes service 1 and service 2 in the same manner as NE1.

Strip S-VLAN Label Add S-VLAN Label
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: 100 Network VLAN ID: 100
Service 2 e E-Lin Service 2
VLAN ID: 200 E-Lin e
Port 2 Port 2 VLAN ID: 200
Add S-VLAN Label Strip S-VLAN Label
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)
8.6.2.4 IEEE 802.1D Bridge-based E-LAN Services

Ethernet local area network (E-LAN) services that are forwarded based only on the MAC address
table are called IEEE 802.1D bridge-based E-LAN services.
Service Model
Table 8-36 shows the IEEE 802.1D bridge-based E-LAN service model.
Table 8-36 IEEE 802.1D bridge-based E-LAN service model

Service Type Tag Type Encapsulation Logical Port Learning Switching
Type at a Port Type Mode Sub-domain
IEEE 802.1D Tag- Null PORT SVL None

bridge-based E- Transparent
LAN service
Typical Application
Figure 8-37 shows a typical application of the IEEE 802.1D bridge-based E-LAN service model.
Services from NodeB 1 and NodeB 2 converge at NE1 and then are transmitted to the radio
network controller (RNC). The services do not need to be separated; therefore, an IEEE 802.1D
bridge is used at NE1 to schedule services.

Figure 8-37 IEEE 802.1D bridge-based E-LAN service model

NE 2
Port 2 Port 1
NodeB 1
802.1D
NE 1 bridge
Port 1
Port 2
Transmission network
Port 3
RNC NE 3
802.1D
bridge Port 1
Port 2
NodeB 2
802.1D
bridge
8.6.2.5 IEEE 802.1Q Bridge-based E-LAN Services

You can use VLANs to separate Ethernet local area network (E-LAN) services and divide an
IEEE 802.1Q bridge into multiple independent switching sub-domains. E-LAN services
separated in this manner are called IEEE 802.1Q bridge-based E-LAN services.
Service Model
Table 8-37 provides information about the IEEE 802.1Q bridge-based E-LAN service model.
Table 8-37 IEEE 802.1Q bridge-based E-LAN service model
Service Type Tag Type Encapsulation Logical Port Learning Switching

Type at a Port Type Mode Sub-domain
IEEE 802.1Q C-Aware IEEE 802.1Q PORT+VLAN Independent A bridge divided

bridge-based E- VLAN learning into switching
LAN service (IVL) sub-domains by
VLAN
Typical Application
Figure 8-38 shows a typical application of the IEEE 802.1Q bridge-based E-LAN service model.
Services 1, 2, 3, and 4 from four NodeBs converge through a transmission network to a radio
network controller (RNC).
l Services 1 and 2 have the same VLAN ID of 100, and services 3 and 4 have the same VLAN
ID of 200.
l Because the VLAN ID of services 1 and 2 is different from that of services 3 and 4, IEEE
802.1Q bridges are configured: one each for NE 1, NE 2, and NE 3. The bridges are divided
into switching sub-domains by VLAN for service isolation over each bridge.

Figure 8-38 IEEE 802.1Q bridge-based E-LAN service model
NE 2 VLAN 100
Service 1
Port 2 VLAN ID: 100
NodeB 1
Service 1, 2
Port 1
VLAN ID: 100
Service 3, 4 Port 3
NE 1 Port 2 Service 2
VLAN ID: 200 VLAN 100
Domain 1 VLAN ID: 100
(VLAN ID: 100) 802.1Q bridge NodeB 2
Port 1
VLAN 200 Transmission network
RNC Port 3 NE
NE 3 VLAN 200 Service 3
2 Port 2 VLAN ID: 200
NodeB 3
802.1Q bridge Port 1
Domain 2
(VLAN ID: 200) Port 3
Service 4
VLAN ID: 200
802.1Q bridge NodeB 4
8.6.3 Typical Mobile Bearer Network Topologies for Ethernet

Services
Ethernet services are typically transmitted in three mobile bearer network topologies.
8.6.3.1 Networking of VLAN-based E-Line Services

VLANs can be used to separate Ethernet line (E-Line) services. With the VLAN technology,
multiple E-Line services can share one physical channel.
On the mobile bearer network shown in Figure 8-39, the VLAN IDs carried by received NodeB
services are planned in a unified manner and are unique globally. The NodeB services share the
Ethernet service bandwidth on the network (NE1 to NE8) and are isolated from each other by
means of VLAN IDs. The NodeB services are aggregated at NE1 and then transmitted through
the local backhaul network to the RNC. Therefore, in this example, services on the microwave
network of the mobile bearer network are configured as VLAN-based E-Line services.

Figure 8-39 Networking diagram of VLAN-based E-Line services
NodeB 1 NE3
NE7 NE4
VLAN 1
NE1
Local backhaul
network
NodeB 2 Transmission network
VLAN 2
GE
NE8
NE2
NE6 NE5 RNC

NodeB 3
VLAN 3
8.6.3.2 Networking of IEEE 802.1D Bridge-based E-LAN Services

In the case of IEEE 802.1D bridge-based Ethernet local area network (E-LAN) service
networking, data is forwarded based on MAC addresses instead of VLAN IDs.
As shown in Figure 8-40, the mobile bearer network does not need to sense whether the received
NodeB services carry any VLAN IDs. Services from each NodeB are aggregated at NE1 and
then transmitted through the local backhaul network to the radio network controller (RNC).
Therefore, in this example, the services on the radio equipment (NE1 to NE8) of the mobile
bearer network are configured as IEEE 802.1D bridge-based E-LAN services. The microwave
network checks the destination ports in the MAC address table according to the destination MAC
addresses carried by the NodeB services and then forwards NodeB services to the ports.
NOTE
Because IEEE 802.1D bridge-based packets are forwarded based only on MAC addresses, the packets are
broadcast to all ports mounted to the bridge. Ports that do not require communication with one another can be
allocated to a split horizon group so that the ports are isolated from each other.

Figure 8-40 Networking diagram (IEEE 802.1D bridge-based E-LAN services)
NodeB 1 NE3
NE7 NE4
VLAN 1
NE1
Local backhaul
network
NodeB 2 Transmission network
VLAN 2
GE
NE8
NE2
NE6 NE5 RNC

NodeB 3
VLAN 3
Split horizon group Microwave link Ethernet link
8.6.3.3 Networking of IEEE 802.1Q Bridge-based E-LAN Services

In the case of IEEE 802.1Q bridge-based Ethernet local area network (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 bearer network shown in Figure 8-41, the VLAN IDs carried by received NodeB
services are planned in a unified manner and are unique within each domain. NodeB services in
different domains are isolated from each other by means of VLAN IDs and NodeBs in the same
domain can not communicate with each other. The NodeB services are aggregated at NE1 and
then transmitted through the local backhaul network to the radio network controller (RNC).
Therefore, in this example, the services on the radio equipment of the mobile bearer network
are configured as IEEE 802.1Q bridge-based E-LAN services. The microwave network checks
the destination ports in the MAC address table according to the destination MAC addresses and
VLAN IDs carried by the NodeB services and then forwards NodeB 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 do not require communication with one another by adding the ports into a split horizon group.

Figure 8-41 Networking diagram for IEEE 802.1Q bridge-based E-LAN services
NE7
NE4
NodeB 1
VLAN 1
NE1
Domain 1
VLAN 1 NE4 NE3
Local backhaul
NodeB 2 network
VLAN 1
Domain 2
VLAN 2
GE
NodeB 3 NE2
VLAN 2
NE6 NE5
RNC
NE8
Split horizon group Microwave link Ethernet link
8.6.3.4 Comparison Between the Three Networking Modes

The three networking modes differ from each other.
Table 8-38 compares the three networking modes.

Table 8-38 Comparison between the three networking modes

Networkin Application Scenario Service Service Configurati Network
g Mode Stabilit Security on Scalability
Applicable Applicable y Complexity
Network VLAN ID
Size Allocation
Networking This l The VLAN IDs High l Very l Services l The

of VLAN- networking carried by high with a network is
based mode is received base l Servic certain difficult
Ethernet line applicable to transceiver es VLAN ID to expand.
(E-Line) all network station (BTS) from are l To add the
services sizes. services are differe transmitte new
planned in a nt d over a VLAN ID
unified manner BTSs fixed after a
and are unique are service BTS is
globally. isolate trail. added,
l BTS services d from l The OAM you must
share Ethernet each capability change
service other. is strong the E-
bandwidths and and only Line
are isolated by point-to- configurat
means of VLAN point ions on all
IDs. configurat the NEs
ion is that the
supported. new
service
path
traverses.


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

of IEEE recommended does not need to l The trail is set network is
802.1D that the sense whether service up by easy to
bridge-based network the received BTS packet means of expand.
Ethernet local contain less services carry s can MAC l After a
area network than 50 BTSs. any VLAN IDs. be address BTS is
(E-LAN) l Services do not broadc self- added,
services need to be ast on learning, you do not
isolated between the and is need to
different ports entire variable. change
connected to the networ l Point-to- the
same bridge.a k. multipoint configurat
configurat ions of
ion is other NEs
supported. on the
The OAM network.
capability Instead,
is you only
relatively need to
weak. change
the
mounted
ports on
the NE
connected
to the base
station.


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

of IEEE networking carried by l The trails are network is
802.1Q mode is received BTS service learned easy to
bridge-based applicable to services are packet based on expand.
E-LAN all network planned in a s are MAC l After a
services sizes, unified manner broadc addresses BTS is
especially to a and are unique ast and added in a
network that is within each within VLAN domain,
divided into domain. each IDs and you do not
several l The BTS domai are not need to
domains. services from n and fixed. change
different are l Point-to- the
domains are isolate multipoint configurat
isolated from d configurat ions of the
each other by betwee ion is other NEs
means of VLAN n supported. in the
IDs. differe The OAM domain or
l BTS services nt capability the
within a domain domai is configurat
do not need to be ns. relatively ions of
isolated from weak. NEs in the
other
each other.a
domains.
Instead,
you only
need to
change
the
mounted
ports and
VLAN
IDs on the
NE
connected
to the base
station.
NOTE
a: To block communication between certain ports connected to a bridge, you must add the ports into a split
horizon group.
8.6.4 Configuration Process

The service configuration process differs according to the specific service type.

8.6.4.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point E-

Line Services)
This section describes the processes of configuring the service information, port information,
protection information, and quality of service (QoS) information of a transparently transmitted
point-to-point Ethernet service (E-Line) and the process of verifying the service configurations.
Flowchart
Figure 8-42 shows the flowchart for configuring transparently transmitted point-to-point E-Line
services.
Figure 8-42 Flowchart for configuring transparently transmitted point-to-point E-Line services
Required Start
Optional
Configure a LAG.
Configure E-Line
services.
Set port attributes.
Configure QoS.
Verify Ethernet
services.
End

Configuring LAG for Ethernet ports
Table 8-39 Process of configuring LAG for Ethernet ports

1 A.7.2.1 When the Ethernet link between an OptiX RTN 380 NE and
Creating a UNI-side equipment requires higher bandwidth or active/
LAG standby protection. Set parameters as follows:
l Set LAG Type to the same value on the NE and on the
UNI-side equipment. The recommended value is Static.
l Set Load Sharing to the same value on the NE and on the
UNI-side equipment. Set Load Sharing to Sharing if the
Ethernet link requires higher bandwidth, or Non-
Sharing if the Ethernet link does not require higher
bandwidth.
l Load Sharing Hash Algorithm takes the default value of
Automatic. This parameter is valid only to load-sharing
LAGs.
l Set Reversion Mode to the same value as that for the
opposite equipment. The recommended value is
Revertive. This parameter is valid only to non-load
sharing LAGs.
l Set WTR Time(min) to the same value on the NE and on
the UNI-side equipment. It is recommended that this
parameter take its default value. This parameter is valid
only to revertive LAGs.
l Set the main and slave ports according to the network plan.
It is recommended that you set the main and slave ports of
the LAG at both ends consistently.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring Transparently Transmitted Point-to-Point E-Line Services
Table 8-40 Process of configuring transparently transmitted point-to-point E-Line services

1 A.7.3.14 Required when an NE is being initially configured.

Deleting an NOTE
E-LAN Because an OptiX RTN 380 carries IEEE 802.1D bridge-based
Service Ethernet local area network (E-LAN) services by default, you need
to delete the default services manually before you configure
transparently transmitted point-to-point E-Line services on it.

2 A.7.3.1 Required.
Creating a Set the service parameters as follows:
Point-to- l Set Source and Sink according to the network plan.
Point
Transparen l Leave VLAN ID empty for both the source and sink.
tly Set parameters for the source and sink ports as follows:
Transmitte l Set Port Enable to Enabled.
d E-Line
Service l Set Encapsulation Type to Null.
l When the port is an Ethernet port connected to the UNI-
side equipment, set Working Mode to the same value on
the NE and on the UNI-side equipment. Normally, this
parameter is set to Auto-Negotiation on the UNI-side
equipment. If the port is an Ethernet port used for internal
connection, it is recommended that you set Working
Mode to Auto-Negotiation for related ports.
Setting Port Attributes
Table 8-41 Process of setting port attributes

1 Setting A.6.1.1 Optional.

parameter Setting Set Max Frame Length (byte) to the length of the
s for an the Basic longest frame that the port may receive. It is
Ethernet Attribute recommended that this parameter take the default
port s for an value of 9600.
Ethernet
Port
A.6.1.2 Required when the flow control function is enabled

Configuri on the external equipment to which the Ethernet port
ng the is connected. Set parameters as follows:
Traffic l When the external equipment uses the non-auto-
Control negotiation flow control function, set Non-
Function Autonegotiation Flow Control Mode to
for an Enable Symmetric Flow Control.
Ethernet
Port l When the external equipment uses the auto-
negotiation flow control function, set
Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.

A.6.1.4 Optional.
Setting
the
Advanced
Attribute
s for an
Ethernet
Port
2 Setting A.6.2.1 Optional.

parameter Setting
s for a Basic
microwav Attribute
e port s for a
Microwav
e Port
A.6.2.3 Optional.
Setting
Advanced
Attribute
s for a
Microwav
e Port
NOTE
Because the Web LCT does not provide a window specifically for configuring microwave ports, configure
microwave port parameters in the window for configuring Ethernet port parameters.
Configuring QoS
Table 8-42 Process of configuring QoS

1 A.7.6.1 Required if the default mappings for the Differentiated

Modifying Services (DS) domain are inapplicable.
the Set related parameters according to the network plan.
Mapping
for a DS
Domain
2 A.7.6.2 Required if the priority type of an Ethernet service is not

Changing CVLAN, which is the default packet type trusted by the
the Packet DiffServ domain.
Type Set the parameters according to the network plan.
Trusted by a
Port

3 Creating Required if a per-hop behavior (PHB) needs to be specified

Flows and for the incoming flow that carries a certain VLAN ID.
Specifying
PHBs for
the Flows
4 Creating Required if the traffic that enters a port needs to be limited.

CAR Set parameters according to the network plan.
5 A.7.6.5 Required if a port is required to schedule traffic according to

Setting a certain queue scheduling policy in the case of traffic
Egress congestion. The default queue scheduling mode is SP+WRR
Queue (SP is short for strict priority and WRR for weighted round
Scheduling robin). AF1 to AF4 queues are WRR queues (allocated the
Policies same weight) and the other queues are SP queues.
Set the parameters according to the network plan.
6 A.7.6.6 Required if the bandwidth for egress port queues needs to be

Setting restricted.
Traffic Set the parameters according to the network plan.
Shaping for
Egress
Queues
7 A.7.6.7 Required if a certain congestion management mode is

Setting the required for queues at an egress port. The default mode is tail
Congestion drop.
Manageme Set the parameters according to the network plan.
nt Mode for
Egress
Queues
8 A.7.6.4 Required if you need to limit the egress bandwidth that an

Configuring Ethernet service occupies.
Port Set related parameters according to the network plan.
Shaping

Verifying Ethernet Service Configurations
Table 8-43 Process of verifying Ethernet service configurations

1 A.7.7.1 Required for the NEs where the two Ethernet ports involved
Creating an in the service test are located. Set parameters as follows:
MD l Set Maintenance Domain Name and Maintenance
Domain Level to the same values for the NEs.
l For an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance
Domain Level takes its default value of 4. For an Ethernet
service between two internal NEs on the transport
network, set Maintenance Domain Level to a value
smaller than 4. For 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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit
Period to 1s.
MEP l Set Maintenance Association Name to the value of
Maintenance Association Name that is set in the
preceding step.
l Set Port to the Ethernet ports that are involved in the
service test.
l Set MEP ID to different values for maintenance
association end points (MEPs) in the same maintenance
domain (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 Set CC Status to Active, as the MEP ID is used to identify
the MEP during the loopback (LB) test.

4 A.7.7.4 Required for the NE where the Ethernet ports involved in the
Creating a OAM operation are located. Set parameters as follows:
Remote l Set Maintenance Domain Name to the value of
MEP in an Maintenance Domain Name that is set in the preceding
MA step.
l Set Maintenance Association Name to the value of
preceding step.
l To ensure that an MEP can respond to the OAM operations
initiated by the other MEPs in the same maintenance
association (MA), you need to set the other MEPs as the
remote MEPs.
NOTE
When two MEPs are on the same NE, you do not need to configure
remote MEPs.
5 A.7.7.7 Required.
Performing The LB test result should show that no packet loss occurs.
an LB Test
8.6.4.2 End-to-End Configuration Process (Transparently Transmitted Point-to-

Point E-Line Services)
protection information, and quality of service (QoS) information for a transparently transmitted
point-to-point Ethernet line (E-Line) service in end-to-end mode and the process of verifying
the service configurations.
NOTE
Ethernet service configuration on microwave links in a 1+1 protection group or an air-interface LAG is
complex. Therefore, it is recommended that you configure Ethernet services on these microwave links on
per-NE basis, or configure Ethernet services on the main NE in end-to-end mode but on the standby NE
on per-NE basis.
Flowchart
Figure 8-43 shows the flowchart for configuring transparently transmitted point-to-point E-Line
services.

Figure 8-43 Flowchart for configuring transparently transmitted point-to-point E-Line services
Required Start
Optional
Configure a LAG.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End

1 Setting A.6.1.1 Required.

Parameter Setting l Set Port Mode to Layer 2 and set
s for an the Basic Encapsulation Type to Null.
Ethernet Attribute
Port s for an l Set Max Frame Length (byte) to the length of
Ethernet the longest frame that the port may receive. It is
Port recommended that this parameter take the default
value of 9600.


Ethernet
A.6.1.4 Optional.
Setting
the
Advanced
Attribute
s for an
Ethernet
Port
2 Setting A.6.2.1 Required.

Parameter Setting Set Port Mode to Layer 2 and set Encapsulation
s for a Basic Type to Null.
Microwav Attribute
e Port s for a
Microwav
e Port
A.6.2.3 Optional.
Setting
Advanced
Attribute
s for a
Microwav
e Port


bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring Transparently Transmitted Point-to-Point E-Line Services
Table 8-46 Process of configuring transparently transmitted point-to-point E-Line services


Deleting an NOTE
to delete the default services manually before you configure
transparently transmitted point-to-point E-Line services on it.

2 A.3.4.1 Perform this task to create microwave links or Ethernet fibers/

Creating a cables for service paths if they have not been created on Main
Fiber/Cable Topology of the U2000.
by Using the Set Automatically Allocate Address to No when creating
Search Ethernet fiber/cable.
Method
3 A.10.2 Required.
Creating a Set related parameters according to the service planning
Point-to- information and parameter planning information.
Point
Transparen
tly
Transmitte
d E-Line
Service
Configuring QoS


Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows




Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues

Shaping

1 A.10.7 Required.
Verifying a The loopback (LB) test result should show that no packet loss
Native occurs.
Ethernet
Service
8.6.4.3 Per-NE Configuration Process (VLAN-based E-Line Services)

protection information, and quality of service (QoS) information for a VLAN-based Ethernet
line (E-Line) service and the process of verifying the service configurations.

Flowchart
Figure 8-44 shows the flowchart for configuring VLAN-based E-Line services.
Figure 8-44 Flowchart for configuring VLAN-based E-Line services
Required Start
Optional
Configure a LAG.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End


bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring VLAN-based E-Line Services
Table 8-50 Process of configuring VLAN-based E-Line services


Deleting an NOTE
to delete the default services manually before you configure VLAN-
based E-Line services on it.

2 A.7.3.2 Required.
Creating a Set the service parameters as follows:
VLAN- l Set Source and Sink according to the network plan.
based E-
Line Service l Set VLAN ID for the source and sink according to the
network plan.
Set parameters for the source and sink ports as follows:
l Set Port Enable to Enabled.
l Set Encapsulation Type to 802.1Q.
l Set Tag according to the following principles:
– If all the accessed services carry VLAN tags (tagged
frames), set Tag to Tag Aware.
– If none of the accessed services carries VLAN tags
(untagged frames), set Tag to Access, and set Default
VLAN ID and VLAN Priority according to the
network plan.
– When the accessed services contain tagged frames and
untagged frames, set Tag to Hybrid, and set Default
network plan.
3 A.7.3.4 Required when Layer 2 protocol packets need to be

Creating an transparently transmitted.
E-Line
Service for
Transmittin
g Layer 2
Protocol
Packets
4 A.7.3.5 Required when the VLAN tags of the Ethernet service need
Creating to be switched at the source and sink.
VLAN The parameters need to be set according to the network plan.
Forwarding
NOTE
Table The corresponding VLAN forwarding table items need to be
Entries configured for the source port and sink port.


1 Setting the A.6.1.1 Optional.

s of the Basic longest frame that the port may receive. It is
ports s for an value of 9600.
Ethernet
Port

Ethernet
A.6.1.4 Optional.
Setting
the
Advanced
Attribute
s for an
Ethernet
Port
2 Setting the A.5.6 Optional.

parameter Configuri
s of ng
microwav Ethernet
e ports Frame
Header
Compress
ion
A.6.2.2 Optional.
Setting
Layer 2
Attribute
s for a
Microwav
e Port

A.6.2.3 Optional.
Setting
Advanced
Attribute
s for a
Microwav
e Port
NOTE
Configuring QoS


Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows




Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues

Shaping


step.
for the NEs.
Period to 1s.
preceding step.
service test.
domain (MD).
MA step.
preceding step.
remote MEPs.
NOTE
remote MEPs.
5 A.7.7.7 Required.
an LB Test

8.6.4.4 End-to-End Configuration Process (VLAN-based E-Line Services)

line (E-Line) service in end-to-end mode and the process of verifying the service configurations.
NOTE
on per-NE basis.
Flowchart
Figure 8-45 shows the flowchart for configuring VLAN-based E-Line services.
Figure 8-45 Flowchart for configuring VLAN-based E-Line services
Required Start
Optional
Configure a LAG.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End


1 Setting the A.6.1.1 Required.

parameter Setting l Set Port Mode to Layer 2 and set
s of the Basic Encapsulation Type to 802.1Q.
Ethernet Attribute
ports s for an l Set Max Frame Length (byte) to the length of
Ethernet the longest frame that the port may receive. It is
Port recommended that this parameter take the default
value of 9600.

Ethernet
A.6.1.3 Required. Set parameters as follows:

Setting l If all the accessed services carry VLAN tags
the Layer (tagged frames), set Tag to Tag Aware.
2
Attribute l If none of the accessed services carries VLAN
s for an tags (untagged frames), set Tag to Access, and
Ethernet set Default VLAN ID and VLAN Priority
Port according to the network plan.
l When the accessed services contain tagged
frames and untagged frames, set Tag to
Hybrid, and set Default VLAN ID and VLAN
Priority according to the network plan.
A.6.1.4 Optional.
Setting
the
Advanced
Attribute
s for an
Ethernet
Port

2 Setting the A.5.6 Required.

parameter Configuri Set Port Mode to Layer 2 and set Encapsulation
s of ng Type to 802.1Q.
microwav Ethernet
e ports Frame
Header
Compress
ion
A.6.2.2 Required. Set parameters as follows:

Setting l If all the accessed services carry VLAN tags
Layer 2 (tagged frames), set Tag to Tag Aware.
Attribute
s for a l If none of the accessed services carries VLAN
Microwav tags (untagged frames), set Tag to Access, and
e Port set Default VLAN ID and VLAN Priority
according to the network plan.
l When the accessed services contain tagged
frames and untagged frames, set Tag to
Hybrid, and set Default VLAN ID and VLAN
Priority according to the network plan.
A.6.2.3 Optional.
Setting
Advanced
Attribute
s for a
Microwav
e Port


bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring VLAN-based E-Line Services
Table 8-56 Process of configuring VLAN-based E-Line services


Deleting an NOTE
to delete the default services manually before you configure VLAN-
based E-Line services on it.


Method
3 A.10.3 Required.
VLAN- information and parameter planning information.
based E-
Line Service
4 A.7.3.4 Required when Layer 2 protocol packets need to be

Creating an transparently transmitted.
E-Line
Service for
Transmittin
g Layer 2
Protocol
Packets
Configuring QoS


Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows




Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues

Shaping

1 A.10.7 Required.
Native occurs.
Ethernet
Service
8.6.4.5 Per-NE Configuration Process (QinQ-based E-Line Services)

Configuring QinQ-based E-Line services includes configuring service information, NNI port
information, protection information, and QoS information, and verifying service configurations.
Flowchart
Figure 8-46 shows the flowchart for configuring QinQ-based E-Line services.

Figure 8-46 Flowchart for configuring QinQ-based E-Line services
Required Start
Optional
Configure a LAG.
Configure NNI port

attributes.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End
The steps in the flowchart are described as follows.


bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Setting NNI Port Attributes
Table 8-60 Setting NNI port attributes

1 A.7.3.14 Deleting an E- Required when an NE is being initially configured.

LAN Service NOTE
By default, an OptiX RTN 380 is configured with an IEEE
802.1D bridge-based E-LAN service, which is mounted to
the Ethernet ports and microwave port on the OptiX RTN
380 NE. Before configuring NNI port attributes, delete the
service. If you do not delete the service, Encapsulation
Type cannot be configured for the port.

2 Configuri A.6.1.1 Required when an Ethernet port is selected as the

ng NNI Setting NNI port. Set Encapsulation Type to QinQ.
port the Basic
(Ethernet Attribute
port) s for an
parameter Ethernet
s Port
A.6.1.3 Optional. Set QinQ Type Domain according to the

Setting network plan. The default value is 88A8.
the Layer
2
Attribute
s for an
Ethernet
Port
3 Configuri A.6.2.1 Required when the microwave port is selected as the

ng NNI Setting NNI port. Set Encapsulation Type to QinQ.
port Basic
(microwav Attribute
e port) s for a
parameter Microwav
s e Port

Advanced
Attribute
s for a
Microwav
e Port

Configuring QinQ-based E-Line Services
Table 8-61 Configuring QinQ-based E-Line services

1 A.7.3.3 Required.
Creating a Set service parameters as follows:
QinQ-based
E-Line l Set Direction to UNI-NNI.
Service l Set Source to the Ethernet port that will function as the
UNI port according to the network plan.
l Set Sink to Create QinQ Link.
– For a microwave port, only when Encapsulation
Type is set to QinQ, the port can function as an NNI
port.
– Set SVLAN ID according to the network plan.
l Set Encapsulation Type to QinQ for the NNI port.
l Set Encapsulation Type to 802.1Q for the UNI port.
Working Mode must be set consistently for the UNI port
and the interconnected port of the UNI-side equipment.
Usually, the interconnected port of the UNI-side
equipment works in auto-negotiation mode.
l Set Tag as follows:
network planning information.
– When the accessed services contain tagged frames and
untagged frames, set Tag to Hybrid, and set Default
network planning information.

Configuring QoS


Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows



Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues


Shaping

step.
for the NEs.
Period to 1s.

preceding step.
service test.
domain (MD).
MA step.
preceding step.
remote MEPs.
NOTE
remote MEPs.
5 A.7.7.7 Required.
an LB Test
8.6.4.6 End-to-End Configuration Process (QinQ-based E-Line Services)

line (E-Line) service in end-to-end mode and the process of verifying the service configurations.
NOTE
on per-NE basis.

Flowchart
Figure 8-47 shows the flowchart for configuring QinQ-based E-Line services.
Figure 8-47 Flowchart for configuring QinQ-based E-Line services
Required Start
Optional
Configure a LAG.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End
1 A.7.3.14 Deleting an E- Required when an NE is being initially configured.

LAN Service NOTE
By default, an OptiX RTN 380 is configured with an IEEE
802.1D bridge-based E-LAN service, which is mounted to
the Ethernet ports and microwave port on the OptiX RTN
380 NE. Before configuring NNI port attributes, delete the
service. If you do not delete the service, Encapsulation
Type cannot be configured for the port.

2 Setting the A.6.1.1 Required.

parameter Setting l Set Port Mode to Layer 2.
s of the Basic
Ethernet Attribute l To enable Ethernet ports to function as UNI
ports s for an ports, set Encapsulation Type to 802.1Q. To
Ethernet enable Ethernet ports to function as NNI ports,
Port set Encapsulation Type to QinQ.
l Set Max Frame Length (byte) to the length of
the longest frame that the port may receive. It is
recommended that this parameter take the default
value of 9600.

the Layer
2
Attribute
s for an
Ethernet
Port
3 Setting the A.5.6 Required.

parameter Configuri To enable microwave ports to function as NNI ports,
s of ng set Port Mode to Layer 2 and Encapsulation
microwav Ethernet Type to QinQ.
e ports Frame
Header
Compress
ion

Layer 2
Attribute
s for a
Microwav
e Port

bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring QinQ-based E-Line Services
Table 8-66 Process of configuring QinQ-based E-Line services

Method

2 A.10.4 Required.
QinQ-based information and parameter planning information.
E-Line
Service
Configuring QoS

Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows



Setting restricted.
Shaping for
Egress
Queues


Congestion drop.
nt Mode for
Egress
Queues

Shaping

1 A.10.7 Required.
Native occurs.
Ethernet
Service
8.6.4.7 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)

protection information, and quality of service (QoS) information for an IEEE 802.1D bridge-
based Ethernet local area network (E-LAN) service and the process of verifying the service
configurations.
Flowchart
Figure 8-48 shows the flowchart for configuring IEEE 802.1D bridge-based E-LAN services.

Figure 8-48 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services
Required Start
Optional
Configure a LAG.
Configure ERPS
protection.
Configure E-LAN
service.
Configure QoS.
Verify Ethernet
services.
End


bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG

Configuring ERPS Protection
Table 8-70 Process of configuring ERPS protection

1 A.7.1.1 Creating an ERP Required when an Ethernet

Instance ring needs to be protected and
service loops need to be
avoided on the Ethernet ring.
Perform the configuration
based on the service plan and
the parameter planning
principles in the operation.
2 A.7.1.2 Setting ERPS Required if the values of the

Protocol Parameters default parameters of the
Ethernet ring protection
switching (ERPS) timers
need to be changed.
Set Hold-Off Time(ms),
Guard Time(ms), WTR
Time(mm:ss), and Packet
Transmit Interval(s)
according to the actual
requirements. Set these
parameters to the same
values for all the NEs on the
network.

Configuring IEEE 802.1D Bridge-based E-LAN Services
Table 8-71 Process of configuring IEEE 802.1D bridge-based E-LAN services
1 A.7.3.6 Creating an IEEE Optional.

802.1D Bridge-based E- Set the service parameters as follows:
LAN Service l Set Source and Sink according to the network
plan.
l Leave VLAN ID empty for both the source and
sink.
l Set Tag Type to Tag-Transparent.
l Set Self-Learning MAC Address to Enabled
l Set Encapsulation Type to Null.
l When the port is an Ethernet port connected to the
UNI-side equipment, set Working Mode to the
same value on the NE and on the UNI-side
equipment. Normally, this parameter is set to
Auto-Negotiation on the UNI-side equipment. If
the port is an Ethernet port used for internal
connection, it is recommended that you set
Working Mode to Auto-Negotiation for related
ports.
l To disable packet forwarding between certain E-
LAN service ports, configure the ports as Split
Horizon Group Members on the Config Split
Horizon Group window.
NOTE
IEEE 802.1D bridge-based services are configured for the
OptiX RTN 380 by default. This step is required only when
IEEE 802.1D bridge-based services need to be reconfigured
for the OptiX RTN 380.
2 A.7.3.10 Changing Optional.

Logical Ports Mounted to NOTE
a Bridge Perform this operation when you need to change the type of
a logical port mounted to a bridge, because an OptiX RTN
380 carries IEEE 802.1D bridge-based services by default.
3 Mana A.7.4.2 Creating Required when usage of E-LAN services needs to be

ging a Blacklist MAC disabled on certain MAC address host.
the Address Entry Set the parameters according to the network plan.
MAC
addres A.7.4.1 Creating Required if you need to set certain MAC address
s table a Static MAC entries not to age.
Address Entry Set the parameters according to the network planning
information.

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

Managing a if the default aging time (five minutes) needs to be
Dynamic MAC changed.
Address Table Set the parameters according to the network plan.
4 A.7.5 Setting the Mode Optional. By default, the processing mode for
for Processing an unknown frames is flood.
Unknown Frame of an E-
LAN Service
NOTE

Ethernet
Port

Ethernet
A.6.1.4 Required when you need to enable the port self-loop

Setting test and automatic loopback shutdown functions or
the to enable the broadcast packet suppression function.
Advanced Set Loopback check, Loopback port shutdown,
Attribute Enabling broadcast packet suppression, and
s for an Broadcast packet suppression threshold as
Ethernet desired.
Port


parameter Setting
s of Basic
microwav Attribute
e ports s for a
Microwav
e Port

Advanced to enable the broadcast packet suppression function.
Attribute Set Loopback check, Loopback port Block,
s for a Broadcast packet suppression, and Broadcast
Microwav packet suppression threshold as desired.
e Port
NOTE
Configuring QoS


Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows




Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues

Shaping

step.
for the NEs.
Period to 1s.
preceding step.
service test.
domain (MD).
MA step.
preceding step.
remote MEPs.
NOTE
remote MEPs.
5 A.7.7.7 Required.
an LB Test

8.6.4.8 End-to-End Configuration Process (IEEE 802.1D Bridge-based E-LAN

Services)
protection information, and quality of service (QoS) information for an IEEE 802.1D bridge-
based Ethernet local area network (E-LAN) service in end-to-end mode and the process of
verifying the service configurations.
NOTE
on per-NE basis.
Flowchart
Figure 8-49 shows the flowchart for configuring IEEE 802.1D bridge-based E-LAN services.
Figure 8-49 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services
Required Start
Optional
Configure a LAG.
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
End

bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring IEEE 802.1D Bridge-based E-LAN Services
Table 8-76 Process of configuring IEEE 802.1D bridge-based E-LAN services
1 A.3.4.1 Creating a Fiber/ Perform this task to create microwave links or

Cable by Using the Ethernet fibers/cables for service paths if they have not
Search Method been created on Main Topology of the U2000.
Set Automatically Allocate Address to No when
creating Ethernet fiber/cable.

2 A.10.5 Creating an IEEE Optional.

802.1D Bridge-based E- Set related parameters according to the service
LAN Service planning information and parameter planning
information.
3 A.7.3.10 Changing Optional.

Logical Ports Mounted to NOTE
a Bridge Perform this operation when you need to change the type of
a logical port mounted to a bridge, because an OptiX RTN
380 carries IEEE 802.1D bridge-based services by default.
Configuring QoS


Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows




Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues

Shaping

1 A.10.7 Required.
Native occurs.
Ethernet
Service
8.6.4.9 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)

protection information, and quality of service (QoS) information for an IEEE 802.1Q bridge-
based Ethernet local area network (E-LAN) service and the process of verifying the service
configurations.
Flowchart
Figure 8-50 shows the flowchart for configuring IEEE 802.1Q bridge-based E-LAN services.

Figure 8-50 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services
Required Start
Optional
Configure a LAG.
Configure ERPS
protection.
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
End


bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring ERPS Protection
Table 8-80 Process of configuring ERPS protection

1 A.7.1.1 Creating an ERP Required when an Ethernet

Instance ring needs to be protected and
service loops need to be
avoided on the Ethernet ring.

2 A.7.1.2 Setting ERPS Required if the values of the

Protocol Parameters default parameters of the
Ethernet ring protection
switching (ERPS) timers
need to be changed.
Set Hold-Off Time(ms),
Guard Time(ms), WTR
Time(mm:ss), and Packet
Transmit Interval(s)
according to the actual
requirements. Set these
parameters to the same
values for all the NEs on the
network.
Configuring IEEE 802.1Q Bridge-based E-LAN Services
Table 8-81 Process of configuring IEEE 802.1Q bridge-based E-LAN services

1 A.7.3.14 Deleting Required when an NE is being initially configured.

an E-LAN Service NOTE
Delete the IEEE 802.1D bridge-based E-LAN services that are
configured for an OptiX RTN 380 by default before configuring
IEEE 802.1Q bridge-based E-LAN services.

2 A.7.3.7 Creating an Required.

IEEE 802.1Q Set the service parameters as follows:
Bridge-based E- l Set Source and Sink according to the network plan.
LAN Service
l Set VLAN ID for the source and sink according to the
network plan.
l Set Tag Type to C-Aware.
l Set Self-Learning MAC Address to Enabled according
to the network plan.
l Set Encapsulation Type to 802.1Q.
l To disable packet forwarding between certain E-LAN
service ports, configure the ports as Split Horizon
Group Members on the Config Split Horizon Group
window.
l Set Tag according to the following principles:
network plan.
– When the accessed services contain tagged frames
and untagged frames, set Tag to Hybrid, and set
Default VLAN ID and VLAN Priority according to
the network plan.
3 A.7.3.8 Creating an Required when Layer 2 protocol packets need to be

E-LAN Service for transparently transmitted.
Transmitting
Layer 2 Protocol
Packets
4 Mana A.7.4.2 Required when usage of E-LAN services needs to be

ging Creating a disabled on certain MAC address host.
the Blacklist Set the parameters according to the network plan.
MAC MAC
addres Address
s table Entry

A.7.4.1 Required if you need to set certain MAC address entries not
Creating a to age.
Static Set the parameters according to the network plan.
MAC
Address
Entry
A.7.4.3 Required if the aging function needs to be disabled or if the

Managing default aging time (five minutes) needs to be changed.
a Dynamic Set the parameters according to the network plan.
MAC
Address
Table
5 A.7.5 Setting the Optional. By default, the processing mode for unknown
Mode for frames is flood.
Processing an
Unknown Frame of
an E-LAN Service


Ethernet
Port

Ethernet


the to enable the broadcast packet suppression function.
Advanced Set Loopback check, Loopback port Block,
Attribute Broadcast packet suppression, and Broadcast
s for an packet suppression threshold as desired.
Ethernet
Port

parameter Setting
s of Basic
microwav Attribute
e ports s for a
Microwav
e Port
A.6.2.2 Optional.
Setting
Layer 2
Attribute
s for a
Microwav
e Port

Advanced to enable the broadcast packet suppression function.
Attribute Set Loopback check, Loopback port Block,
s for a Broadcast packet suppression, and Broadcast
Microwav packet suppression threshold as desired.
e Port
NOTE
Configuring QoS

Mapping
for a DS
Domain


Trusted by a
Port

Specifying
PHBs for
the Flows



Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues

Shaping


step.
for the NEs.
Period to 1s.
preceding step.
service test.
domain (MD).

MA step.
preceding step.
remote MEPs.
NOTE
remote MEPs.
5 A.7.7.7 Required.
an LB Test
8.6.4.10 End-to-End Configuration Process (IEEE 802.1Q Bridge-based E-LAN

Services)
protection information, and quality of service (QoS) information for an IEEE 802.1Q bridge-
based Ethernet local area network (E-LAN) service in end-to-end mode and the process of
verifying the service configurations.
NOTE
on per-NE basis.
Flowchart
Figure 8-51 shows the flowchart for configuring IEEE 802.1Q bridge-based E-LAN services.

Figure 8-51 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services
Required Start
Optional
Configure a LAG.
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
End


bandwidth.
LAGs.
sharing LAGs.
2 A.7.2.2 Optional.
Setting
Parameters
for a LAG
Configuring IEEE 802.1Q Bridge-based E-LAN Services
Table 8-86 Process of configuring IEEE 802.1Q bridge-based E-LAN services


Deleting an NOTE
E-LAN Delete the IEEE 802.1D bridge-based E-LAN services that are configured
Service for an OptiX RTN 380 by default before configuring IEEE 802.1Q bridge-
based E-LAN services.

2 A.3.4.1 Required if microwave links or Ethernet fibers/cables have not

Creating a been created for service paths on Main Topology of the U2000.
Fiber/Cable Set Automatically Allocate Address to No when creating
by Using the Ethernet fiber/cable.
Search
Method
3 A.10.6 Required.
Creating an Set related parameters according to the service planning
IEEE 802.1Q information and parameter planning information.
Bridge-based
E-LAN
Service
4 A.7.3.8 Required when Layer 2 protocol packets need to be transparently

Creating an transmitted.
E-LAN
Service for
Transmitting
Layer 2
Protocol
Packets
Configuring QoS


Mapping
for a DS
Domain

Trusted by a
Port

Specifying
PHBs for
the Flows




Setting restricted.
Shaping for
Egress
Queues

Congestion drop.
nt Mode for
Egress
Queues

Shaping

1 A.10.7 Required.
Native occurs.
Ethernet
Service

8.6.5 Configuration Example (Transparently Transmitted Point-to-

Point E-Line Services)
This section uses a transparently transmitted point-to-point E-Line service as an example to
describe how to configure Ethernet services according to the network plan.

As shown in Figure 8-52, a hop of large-capacity OptiX RTN 380 equipment replace optical
fibers to form a ring network with OptiX optical transmission equipment. Configure Ethernet
services according to the following requirements:
Table 8-89 Service requirements

Requirement Description Requirement Satisfaction
Servic The Ethernet service capacity l The OptiX RTN 380 provides three GE ports
e on a ring network does not (two optical ports and one electrical port) for
access exceed 2 Gbit/s. Microwave receiving Ethernet services, configuring a link
capaci links need to transparently aggregation group (LAG), and configuring
ty transmit Ethernet services. transparently transmitted point-to-point E-
Line services.
Servic Links between the OptiX optical
l NE91 and NE93 each provides three GE ports
e transmission equipment and the
(two optical ports and one electrical port) that
protec OptiX RTN 380 equipment
work in auto-negotiation mode. A load-
tion need protection.
sharing LAG is configured for the ports, with
the electrical GE ports as the main ports.
QoS The priorities of Ethernet Configure DiffServ and perform service

services transmitted over a scheduling and forwarding based on DSCP
microwave network are values.
identified by DSCP values. All
the NEs on the microwave
network have the same mapping
between PHBs and DSCP
values for Ethernet services.

Figure 8-52 Networking diagram for transparently transmitted point-to-point E-Line services
NMS
LAN
switch
LAG LAG
Backbone
NE33 NE34 Network
NE91 NE92
NE93 NE94
Optical
Radio link Ethernet link transmisson
equipment
8.6.5.2 Service Planning (Port Information)

This section describes the parameters for configuring Ethernet ports.
Ethernet Port Information

Table 8-90 provides information about Ethernet ports carrying services on NE33 and NE34.
NOTE

Table 8-90 Ethernet port information

Parameter Value (NE33 and NE34)
1-SHUF3-2(GE1) 1-SHUF3-3(GE2) 1-SHUF3-4(GE3)
Encapsulation Type Null Null Null
Working Mode Auto-Negotiation Auto-Negotiation Auto-Negotiation
Flow Control Disabled Disabled Disabled

NOTE
l The three GE ports of the optical transmission equipment interconnected with the OptiX RTN 380 work in
auto-negotiation mode. Therefore, the three GE ports on the OptiX RTN 380 for receiving services need to
work in auto-negotiation mode. If the peer Ethernet ports work in 1000M full-duplex mode, the local Ethernet
ports also need to work in 1000M full-duplex mode.
l Generally, the flow control function is enabled only when an NE or the peer equipment is inadequate for
QoS processing. The plan for flow control must be the same for the equipment at both ends.
Microwave Port Information

Table 8-91 provides information about microwave ports carrying services on NE33 and NE34.
Table 8-91 Microwave port information
Parameter Value (NE33 and NE34)
1-SHUF3-1(IF)
Encapsulation Type Null
8.6.5.3 Service Planning (Ethernet Protection)

This section describes the parameters required for configuring Ethernet protection.
Because the transmitted service capacity exceeds the bandwidth of a single GE link, configure
a static load-sharing LAG. Configure a corresponding LAG for NE91 and NE92.
Table 8-92 Ethernet LAG
Parameter NE33 NE34
LAG Name LAG1 LAG1
Load Sharing Sharing Sharing
Standby Port 1-SHUF3-3(GE2) 1-SHUF3-3(GE2)

8.6.5.4 Service Planning (Ethernet Services)

This section describes the parameters required for configuring Ethernet services.
Table 8-93 provides the detailed service plan.

Table 8-93 Information about a transparently transmitted point-to-point E-Line service

Parameter NE33 NE34
Service ID 1 1
Service Name Ring_ELine Ring_ELine
L2 Protocol Control Not Transparent Not Transparent
Source Port 1-SHUF3-2(GE1) 1-SHUF3-2(GE1)
Source C-VLANs Blank Blank
Sink Port 1-SHUF3-1(IF) 1-SHUF3-1(IF)
Sink C-VLANs Blank Blank
NOTE
In this example, Ethernet services are shared by member ports in the LAG. Therefore, services only need to be
configured for the main port 1-SHUF3-2(GE1) in the LAG.
8.6.5.5 Service Planning (QoS)

This section describes the parameters required for configuring QoS.
DiffServ
DiffServ (DS) is the basis for QoS. It is recommended that a VLAN priority or differentiated
services code point (DSCP) value be allocated to a base station service based on the service type.
The transport network creates the corresponding DS domain according to the allocated VLAN
priority or DSCP value. All ports involved in the service must use the same DS configuration.
In this example, services from the base stations are allocated DSCP values based on service
types, and the OptiX RTN 380s allocate per-hop behaviors (PHBs) according to the DSCP
values. For details, see Table 8-94.
Table 8-94 PHBs and Service types

PHB DSCP Service Type
CS7 56 -
CS6 48 -
EF 40 Real-time voice services

(R99 conversational and R99
streaming services) and
signaling
AF41 36 -
AF42 34 -
AF43 32 -

AF31 28 O&M and high-priority real-

time HSDPA services (O&M
and HSPA streaming
services)
AF32 26 -
AF33 24 Low-priority real-time

HSDPA service (HSPA
streaming service)
AF21 20 High-priority non-real-time

R99 services (R99 interactive
and R99 background
services)
AF22 18 -
AF23 16 Low-priority non-real-time

and R99 background
services)
AF11 12 -
AF12 10 -
AF13 8 -
BE 0 HSDPA data services (HSPA

interactive and background
services)
NOTE
l CS7 or CS6 is not recommended, because CS7 or CS6 may be used to transmit Ethernet protocol packets
or inband data communication network (DCN) packets.
l The trusted packet type is not the C-VLAN priority but the DSCP value. Therefore, the trusted packet type
needs to be changed for service-associated Ethernet ports in the default DS domain.
Queue Scheduling Policy and Congestion Management Mode

Table 8-95 and Table 8-96 list the queue scheduling policies and congestion management modes
for services of various priorities on microwave ports and Ethernet ports in this example.
Table 8-95 Queue scheduling policies
PHB Queue Scheduling Policy
CS7 Strict priority (SP)
CS6 SP

EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
Table 8-96 Congestion management modes
PHB Congestion Management Mode
CS7 Tail drop
CS6 Tail drop
EF Tail drop
AF4 Tail drop
AF3 Tail drop
AF2 Tail drop
AF1 Tail drop
BE Tail drop
CAR
Generally, a microwave backhaul network does not require committed access rate (CAR)
because 2G/3G base stations and BSCs/RNCs have their own traffic control policies (BSC is
short for base station controller, and RNC for radio network controller).
Shaping
If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth for
aggregation services, you can enable port shaping at the edge node to limit the Ethernet service
traffic sent to the convergence node. This prevents congestion at the convergence node.
In this example, you do not need to enable port shaping.
8.6.5.6 Procedure of Configuration on a Per-NE Basis (Ethernet Protection)

This section describes the procedure for configuring Ethernet protection.

Procedure
Step 1 Create a LAG. For details, see A.7.2.1 Creating a LAG.
This table provides parameter values of the LAG on NE33 and NE34.

Parameter NE33 NE34
LAG Name LAG1 LAG1

----End
8.6.5.7 Procedure of Configuration on a Per-NE Basis (Service Information)

This section describes the procedure for configuring service information.
Procedure
Step 1 Delete E-LAN services. For details, see A.7.3.14 Deleting an E-LAN Service.
Step 2 Create transparently transmitted point-to-point E-Line services. For details, see A.7.3.1
Creating a Point-to-Point Transparently Transmitted E-Line Service.
Table 8-98 Information about a transparently transmitted point-to-point E-Line service

Parameter NE33 NE34
Service ID 1 1
Service Name Ring_ELine Ring_ELine
L2 Protocol Control Not Transparent Not Transparent
Source C-VLANs Blank Blank
Sink C-VLANs Blank Blank

Port NE33 NE34
1-SHUF3-2 1-SHUF3-1 1-SHUF3-2 1-SHUF3-1

(GE1) (IF) (GE1) (IF)
Port Enable Enabled - Enabled -
VLAN ID (e.g. - - - -
1,3-5)
Working Mode Auto- - Auto- -

Negotiation Negotiation
Encapsulation Null Null Null Null

Type
Tag - - - -
----End
8.6.5.8 Procedure of Configuration on a Per-NE Basis (QoS)

This section describes the procedure for configuring quality of service (QoS).
Procedure
Step 1 Modify the mapping for a DS domain. For details, see A.7.6.1 Modifying the Mapping for a
DS Domain.
This table provides parameter values on the Ingress tab page.
CVLAN IP DSCP PHB

SVLAN
MPLS EXP
Retain the default values for 0 BE

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33

CVLAN IP DSCP PHB

SVLAN
MPLS EXP
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
This table provides parameter values on the Egress tab page.
CVLAN IP DSCP PHB

SVLAN

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
Step 2 Change the ports applied to a DS domain and their trusted packet types. For details, see A.7.6.2
Changing the Packet Type Trusted by a Port.

NE Port Packet Type
NE33 1-SHUF3-2(GE1) ip-dscp

1-SHUF3-3(GE2)
1-SHUF3-4(GE3)
1-SHUF3-1(IF)

1-SHUF3-3(GE2)
1-SHUF3-4(GE3)
1-SHUF3-1(IF)
NOTE
The desired trusted packet type of the port is not the C-VLAN priority but DSCP value. Therefore, the trusted
packet type needs to be modified for service-associated Ethernet ports in the default DS domain.
Step 3 Set egress queue scheduling policies. For details, see A.7.6.5 Setting Egress Queue Scheduling
Policies.
This table provides parameter values for scheduling priorities of microwave ports and Ethernet
ports.
PHB Service Class Queue Scheduling Mode
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
Step 4 Set egress queue congestion management modes. For details, see A.7.6.7 Setting the
Congestion Management Mode for Egress Queues.
This table provides parameter values for congestion management modes of microwave ports
and Ethernet ports.
PHB Service Class Congestion Management
CS7 Tail Drop Threshold

EF Tail Drop Threshold
AF4 Tail Drop Threshold
BE Tail Drop Threshold
----End
8.6.5.9 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification)

This section describes the procedure for verifying Ethernet service configurations.
Procedure
Step 1 Create a maintenance domain (MD). For details, see A.7.7.1 Creating an MD.
This table provides parameter values for creating an MD.
Parameter Value
NE33 NE34
Maintenance Domain InterNE InterNE

Name
Maintenance Domain 4 4
Level
Step 2 Create a maintenance association (MA). For details, see A.7.7.2 Creating an MA.
This table provides parameter values for creating an MA.
Parameter Value
NE33 NE34

Name
Maintenance Association Ring_ELine Ring_ELine

Name
Relevant Service 1-Ring_ELine 1-Ring_ELine
CC Test Transmit Period 1s 1s

Step 3 Create a maintenance end point (MEP). For details, see A.7.7.3 Creating an MEP.
This table provides parameter values for creating an MEP.
Parameter Value
NE33 NE34

Name

Name
Board 1-SHUF3 1-SHUF3
Port 1-SHUF3-2 1-SHUF3-2
VLAN – –
MEP ID 101 102
Direction Ingress Ingress
CC Status Active Active
Step 4 Create a remote MEP in an MA. For details, see A.7.7.4 Creating a Remote MEP in an MA.
This table provides parameter values for creating a remote MEP in an MA.
Parameter Value
NE33 NE34
Maintenance Domain EdgeNE EdgeNE

Name

Name
Remote Maintenance Point 102 101

ID(e.g:1,3-6)
Step 5 Perform an LB test. For details, see A.7.7.7 Performing an LB Test.
Perform an LB test by considering the MEP whose MEP ID is 101 as the source MEP and the
MEP whose MEP ID is 102 as the sink MEP.
There should be no packet loss during the tests.
----End
8.6.5.10 End-to-End Configuration Procedure (Ethernet Protection)


Procedure
Step 1 Create a LAG. For details, see A.7.2.1 Creating a LAG.
This table provides parameter values of the LAG on NE33 and NE34.

Parameter NE33 NE34
LAG Name LAG1 LAG1

----End
8.6.5.11 End-to-End Configuration Procedure (Service Information)

This section describes the procedure for configuring Ethernet service information.
Procedure
Step 1 Delete Ethernet local area network (E-LAN) services. For details, see A.7.3.14 Deleting an E-
LAN Service.
Step 2 Create Ethernet line (E-Line) services transmitted in Native Ethernet mode. For details, see A.
10.3 Creating a VLAN-based E-Line Service.
1. Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
2. Set the basic attributes for the E-Line service.

3. Configure the source and sink of the E-Line service.

a. Double-click the source NE (NE33) in the Physical Topology tab page.
b. Select 1-SHUF3-2(GE1), set C-VLAN to blank and set S-VLAN to blank.
c. Click OK.
d. Double-click the sink NE (NE34) in the Physical Topology tab page.
e. Select 1-SHUF3-2(GE1), set C-VLAN to blank and set S-VLAN to blank.
f. Click OK.
4. Click Calculate Route.

5. Check the service path information.
6. Select Deploy and ETH OAM CC.
7. Click OK.
----End
8.6.5.12 End-to-End Configuration Procedure (QoS)

Procedure
DS Domain.
CVLAN IP DSCP PHB

SVLAN
MPLS EXP

all the parameters.
12 AF11
10 AF12

CVLAN IP DSCP PHB

SVLAN
MPLS EXP
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
CVLAN IP DSCP PHB

SVLAN

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41

CVLAN IP DSCP PHB

SVLAN
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
NE Port Packet Type

1-SHUF3-3(GE2)
1-SHUF3-4(GE3)
1-SHUF3-1(IF)

1-SHUF3-3(GE2)
1-SHUF3-4(GE3)
1-SHUF3-1(IF)
NOTE
Policies.
ports.
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP

AF1 SP
BE SP
and Ethernet ports.
----End
8.6.5.13 End-to-End Configuration Procedure (Verifying Ethernet Service

Configurations)
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the main
menu.
Step 2 In the Set Filter Criteria dialog box, set filter conditions and click Filter.
The Native Ethernet services that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet service, and choose Ethernet OAM > LB Test from
the shortcut menu.

Step 4 In the LB Test dialog box, select the desired service trail.
NOTE
l An LB test checks whether a service is bidirectional available. For a bidirectional service, select the
NE at either end to initiate an LB test.
l If Ethernet services are in different VLANs, the U2000 automatically selects the service in a VLAN
for an LB test.
l One NE cannot be involved in multiple LB tests simultaneously.
Step 5 Optional: Choose Config LB Parameter from the shortcut menu. Set Sent Packets, Sent
Packets Length, and Sent Packets Priority. Then, click OK.
Step 6 Click Run.
Step 7 Click the LB Testing Information and LB Statistics Information tabs, and determine whether
the service is available based on the displayed information.
Normally, Test Results indicates Test Succeeded.
----End
8.6.6 Configuration Example (VLAN-based E-Line Services)

This section uses a VLAN-based E-Line service as an example to describe how to configure
Ethernet services according to the service plan.


The section describes the networking of NEs.
Configure Ethernet services according to 8.5.3 Configuration Example (Microwave Links on
a Chain Network) and the following requirements.

Servic Configure a port working in The OptiX RTN 380 provides an electrical P&E
e auto-negotiation mode for port for receiving services.
access receiving a channel of electrical
capaci GE signals from NodeB 1.
ty Configure a port working in
auto-negotiation mode for
receiving a channel of electrical
GE signals from RAN 1.
Servic No -
e
protec
tion
Servic Separate services from NodeB 1 Configure VLAN-based E-Line services on

e and RAN 1 from each other NE21, NE22, NE23, and NE24.
separa using VLAN IDs: NOTE
tion l VLAN ID of NodeB 1: 100 You can also configure IEEE 802.1Q bridge-based E-
LAN services on NE23. For details, see 8.6.9
l VLAN ID of RAN 1: 200 Configuration Example (IEEE 802.1q Bridge-based
E-LAN Services).


Figure 8-53 Networking diagram for VLAN-based E-Line services

NMS
RNC
LAN
switch
Regional
Backhaul
Network
P&E GE GE
P&E
NodeB 1 P&E NE99

VLAN 100 NE21 NE22 NE23 NE24
RAN1
VLAN 200


Table 8-101 provides the information about the Ethernet ports that transmit/receive Ethernet
services.
NOTE


Parameter NE21 NE22 NE23 NE24
1-SHUF3-2 1-SHUF3-4 1-SHUF3-2 1-SHUF3-4 1-SHUF3-2

(GE1) (GE3) (GE1) (GE3) (GE1)
Encapsulatio 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

n Type
Working Auto- Auto- Auto- Auto- Auto-

Mode Negotiation Negotiation Negotiation Negotiation Negotiation
Flow Control Disabled Disabled Disabled Disabled Disabled
Tag Type Tag Aware Tag Aware Tag Aware Tag Aware Tag Aware
NOTE
l In this example, the GE ports on the NodeB and RAN connected to the OptiX RTN 380 work in auto-
negotiation mode. Therefore, the peer GE ports on the OptiX RTN 380 must also work in auto-negotiation
mode. If the peer Ethernet ports work in another mode, the local Ethernet ports must work in the same mode.
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag-aware.

Table 8-102 provides the information about the microwave ports that transmit/receive services.
Parameter NE21/NE22/NE23/NE24
1-SHUF3-1(IF)
Encapsulation Type 802.1Q
Tag Type Tag Aware

In this example, Ethernet protection is not used.

Figure 8-54 provides the planning information of the end-to-end Ethernet services between NEs.

Figure 8-54 Information about VLAN-based E-Line services

Links: NE24-NE23-NE22-NE21
NE24 NE23 NE22 NE21

IF IF GE2 GE2 IF IF
C:200
RNC -RAN 1
GE1(C:200) GE1(C:200)
C:100 C:100 C:100
RNC - NodeB 1
GE1(C:100) GE1(C:100)
C: C-VLAN
Pass through
Add/Drop
Table 8-103 provides the planning information of the per-NE services on each NE.
Table 8-103 Information about VLAN-based E-Line services

Parameter NE24 NE23 NE22 NE21
NE23 to NE22 to RAN 1 to NE21 to NodeB 1 to

NE99 NE24 NE24 NE23 NE22
Service ID 1 1 2 1 1
Service NE23toNE9 NE22toNE2 RAN1toNE2 NE21toNE2 NodeB1toN

Name 9_Vline 4_Vline 4_Vline 3_Vline E22_Vline
L2 Protocol Not Not Not Not Not

Control Transparent Transparent Transparent Transparent Transparent
Source Port 1-SHUF3-1 1-SHUF3-4 1-SHUF3-2 1-SHUF3-1 1-SHUF3-2

(IF) (GE3) (GE1) (IF) (GE1)
Source C- 100, 200 100 200 100 100

VLANs
Sink Port 1-SHUF3-2 1-SHUF3-1 1-SHUF3-1 1-SHUF3-4 1-SHUF3-1

(GE1) (IF) (IF) (GE3) (IF)
Sink C- 100, 200 100 200 100 100

VLANs

DiffServ

CS7 56 -
CS6 48 -

signaling
AF41 36 -
AF42 34 -
AF43 32 -

and HSPA streaming
services)
AF32 26 -

HSDPA service (HSPA
streaming service)

and R99 background
services)
AF22 18 -

and R99 background
services)
AF11 12 -
AF12 10 -
AF13 8 -

services)

NOTE

Table 8-105 and Table 8-106 list the queue scheduling policies and congestion management
modes for services of various priorities on microwave ports and Ethernet ports in this example.
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
CS7 Tail drop
CS6 Tail drop
EF Tail drop
AF4 Tail drop
AF3 Tail drop
AF2 Tail drop
AF1 Tail drop
BE Tail drop

CAR
Shaping


Procedure
Step 2 Create transparently transmitted point-to-point E-Line services. For details, see A.7.3.1
Creating a Point-to-Point Transparently Transmitted E-Line Service.
l Parameters of NE21
This table provides parameter values for the E-Line services on NE21.
Parameter NE21
NodeB 1 to NE22
Service ID 1
Service Name NodeB1toNE22_Vline
Direction UNI-UNI
Source Port 1-SHUF3-2(GE1)
Sink Port 1-SHUF3-1(IF)
This table provides parameter values for the related ports on NE21.
Parameter NE21
1-SHUF3-2(GE1) 1-SHUF3-1(IF)
Port Enable Enabled -

Parameter NE21
VLAN ID 100 100
Working Mode Auto-Negotiation -
Encapsulation Type 802.1Q 802.1Q
Tag Tag Aware Tag Aware
Parameter NE22
NE21 to NE23
Service ID 1
Service Name NE21toNE23_Vline
Direction UNI-UNI
Source Port 1-SHUF3-1(IF)
Sink Port 1-SHUF3-4(GE3)
Parameter NE22
VLAN ID 100 100
Parameter NE23
NE22 to NE24 RAN 1 to NE24
Service ID 1 2

Parameter NE23
NE22 to NE24 RAN 1 to NE24
Service Name NE22toNE24_Vline RAN1toNE24_Vline
Direction UNI-UNI UNI-UNI
Parameter NE23
1-SHUF3-2(GE1) 1-SHUF3-4(GE3) 1-SHUF3-1(IF)
Port Enable Enabled Enabled -
VLAN ID 200 100 100, 200
Working Mode Auto-Negotiation Auto-Negotiation -
Encapsulation 802.1Q 802.1Q 802.1Q

Type
Tag Tag Aware Tag Aware Tag Aware
Parameter NE24
NE23 to NE99
Service ID 1
Service Name NE23toNE99_Vline
Direction UNI-UNI
Source Port 1-SHUF3-1(IF)
Sink Port 1-SHUF3-2(GE1)
Parameter NE24

Parameter NE24
VLAN ID 100, 200 100, 200
----End

Procedure
DS Domain.
CVLAN IP DSCP PHB

SVLAN
MPLS EXP

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF

CVLAN IP DSCP PHB

SVLAN
MPLS EXP
48 CS6
56 CS7
CVLAN IP DSCP PHB

SVLAN

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
NE Port Packet Type

1-SHUF3-1(IF)

NE Port Packet Type

1-SHUF3-1(IF)

1-SHUF3-4(GE3)
1-SHUF3-1(IF)

1-SHUF3-1(IF)
NOTE
Policies.
ports.
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
and Ethernet ports.

----End
8.6.6.9 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification)

Procedure
Parameter Value
NE21 NE23 NE24
Maintenance EdgeNE EdgeNE EdgeNE

Domain Name
Maintenance 4 4 4
Domain Level
Parameter Value
NE21 NE23 NE24
Maintenance EdgeNE EdgeNE EdgeNE EdgeNE

Domain Name
Maintenance NodeB1_Vline RAN1_Vline NodeB1_Vline RAN1_Vline

Association
Name
Relevant 1- 1- 1- 1-
Service NodeB1toNE22 RAN1toNE24_ NE23toNE99_ NE23toNE99_
_Vline Vline Vline Vline

Parameter Value
NE21 NE23 NE24
CC Test 1s 1s 1s 1s
Transmit
Period
Parameter Value
NE21 NE23 NE24

Domain Name

Association
Name
Board 1-SHUF3 1-SHUF3 1-SHUF3 1-SHUF3
Port 1-SHUF3-2 1-SHUF3-2 1-SHUF3-2 1-SHUF3-2
VLAN 100 200 100 200
MEP ID 101 201 102 202
Direction Ingress Ingress Ingress Ingress
CC Status Active Active Active Active
Parameter Value
NE21 NE23 NE24

Domain Name

Association
Name
Remote 102 202 101 201

Maintenance
Point ID(e.g:
1,3-6)

Step 5 Perform LB tests. For details, see A.7.7.7 Performing an LB Test.

----End


Context
This section describes the procedure for configuring Ethernet services between NodeB 1 and
the RNC. The procedure for configuring Ethernet services between RAN 1 and the RNC is
similar.
Procedure
LAN Service.
Step 2 Create optical fibers manually. For details, see A.3.4.1 Creating a Fiber/Cable by Using the
Search Method.
This table provides parameter values for creating optical fibers manually.
Parameter Value
GE Optical Fiber between NE22 and

NE23
Fiber/Cable Type Fiber
Source NE NE22
Source Board 1-SHUF3-4(GE3)
Source Port 4
Sink NE NE23
Sink Board 1-SHUF3-4(GE3)
Sink Port 4
Automatically Allocate IP Address No

NOTE
This example is based on the hypothesis that the microwave links have been created during microwave link
configuration.
10.3 Creating a VLAN-based E-Line Service.

b. Select 1-SHUF3-2(GE1), set C-VLAN to 100 and set S-VLAN to blank.
c. Click OK.
e. Select 1-SHUF3-2(GE1), set C-VLAN to 100 and set S-VLAN to blank.
f. Click OK.

5. Check the service path information. Set Out C-VLAN and In C-VLAN for each node on
the service path.
7. Click OK.
----End


Procedure
DS Domain.
CVLAN IP DSCP PHB

SVLAN
MPLS EXP

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
CVLAN IP DSCP PHB

SVLAN

all the parameters.
12 AF11

CVLAN IP DSCP PHB

SVLAN
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
NE Port Packet Type

1-SHUF3-1(IF)

1-SHUF3-1(IF)

1-SHUF3-4(GE3)
1-SHUF3-1(IF)

1-SHUF3-1(IF)
NOTE

Policies.
ports.
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
and Ethernet ports.
----End

Configurations)

Context
This section describes the procedure for verifying Ethernet services between NodeB 1 and the
RNC. The procedure for verifying Ethernet services between RAN 1 and the RNC is similar.
Procedure
menu.
the shortcut menu.
NOTE
for an LB test.
Step 6 Click Run.


----End
8.6.7 Configuration Example (QinQ-based E-Line Services)

This section uses a QinQ-based E-Line service as an example to describe how to configure
Ethernet services according to the service plan.

Configure Ethernet services according to 8.5.5 Configuration Example (Large-Capacity

Backhaul Microwave Links with 1+1 Protection) and the following requirements.
Servic Use the microwave links l Cascade two OptiX RTN 380 NEs at a site to
e configured with 1+1 HSB provide two electrical P&E ports and two
access protection between OptiX RTN optical GE ports for receiving services.
capaci 380 NEs to: l Configure LAGs for the OptiX RTN 900 NEs
ty l Transparently transmit to implement 1+1 HSB protection with the
services from RAN 1 to OptiX RTN 380 NEs.
RNC 1 point-to-point.
l Transparently transmit
services from RAN 2 to
RNC 2 point-to-point.
Servic Configure end-to-end

e protection for two channels of
protec GE services.
tion

Servic The VLAN ID plan for RAN 1 Configure QinQ services to separate services on
e and RAN 2 is unknown yet. microwave links using SVLAN.
separa
tion

Figure 8-55 Networking diagram for QinQ-based E-Line services
RNC 1
RAN 1
LAG1 LAG1 NE11 NE13 LAG1 LAG1

P&E P&E
GE GE
LAG2 COMBO COMBO LAG2
LAG2 LAG2
COMBO COMBO
LAG2 LAG2
GE GE
RAN 2 P&E P&E

8.6.7.2 Service Planning (Ethernet Ports)


services.

NOTE


Working Mode Auto-Negotiation Auto-Negotiation
Flow Control Disabled Disabled
NOTE
l In this example, the GE ports on the OptiX RTN 900 connected to the OptiX RTN 380 work in auto-
mode. If the peer Ethernet ports work in 1000M full-duplex mode, the local Ethernet ports also need to work
in 1000M full-duplex mode.


1-SHUF3-1(IF)
Encapsulation Type QinQ
QinQ Type Domain 88A8

In this example, LAGs need to be configured for OptiX RTN 900 to implement 1+1 HSB
protection for two channels of received GE services, together with OptiX RTN 380.
1+1 HSB Protection Information for the OptiX RTN 380

See Configuration Example (Large-Capacity Backhaul Microwave Links with 1+1
Protection) for the configurations of 1+1 HSB protection on the OptiX RTN 380.

LAG Information on the OptiX RTN 900

Configure the OptiX RTN 900 interconnected with the OptiX RTN 380 as follows:
l Create static, non-load sharing, and non-revertive LAGs for it. The priority values are
recommended to be larger than 1000 for the LAGs.
l Add ports of the same type (electrical or optical) into a LAG, and set Working Mode to
Auto-Negotiation for the ports.

Figure 8-56 provides the service plan for the main link (NE11–NE13). Service plan for the
standby link (NE12–NE14) is the same.
Figure 8-56 Information about the QinQ-based E-Line Services
Link: NE11-NE13
NE11 NE13
P&E IF IF P&E
SVLAN:100
RAN1-NodeB 1
GE IF IF GE
SVLAN:200
RAN2-NodeB 2
Add/Drop
NOTE
The following Ethernet services need to be created on the OptiX RTN 900. This manual does not provide the
details about the configuration process.
l Transparently transmitted point-to-point services from the access port of RAN 1 to LAG1
l Transparently transmitted point-to-point services from the access port of RAN 2 to LAG2
Table 8-110 provides the detailed service plan.
Table 8-110 Information about the QinQ-based E-Line services

RAN 1 to NodeB 1 RAN 2 to NodeB 2
Service ID 1 2
Service Name RAN1toNodeB1_Qline RAN2toNodeB2_Qline

Direction UNI-NNI UNI-NNI
Source C-VLANs - -
Source QinQ link - -
Sink QinQ link ID: 1 ID: 2

Port: 1-SHUF3-1(IF) Port: 1-SHUF3-1(IF)
SVLAN: 100 SVLAN: 200

DiffServ
CS7 56 -
CS6 48 -

signaling
AF41 36 -
AF42 34 -
AF43 32 -

and HSPA streaming
services)

AF32 26 -

HSDPA service (HSPA
streaming service)

and R99 background
services)
AF22 18 -

and R99 background
services)
AF11 12 -
AF12 10 -
AF13 8 -

services)
NOTE

CS6 SP
EF SP
AF4 SP
AF3 SP

AF2 SP
AF1 SP
BE SP

CS7 Tail drop
CS6 Tail drop
EF Tail drop
AF4 Tail drop
AF3 Tail drop
AF2 Tail drop
AF1 Tail drop
BE Tail drop
CAR
Shaping

In this example, LAGs need to be configured for the OptiX RTN 900 to implement 1+1 HSB
protection for two channels of received GE services, together with OptiX RTN 380. For details,
see the OptiX RTN 900 Configuration Guide.
8.6.7.7 Procedure of Configuration on a Per-NE Basis (NNI Ports)

In this example, the NNI port information needs to be configured prior to QinQ-based E-Line
services.

Procedure
Step 1 Configure the basic attributes for the NNI ports. For details, see A.6.2.1 Setting Basic Attributes
for a Microwave Port.
This table provides values for basic parameters of the NNI ports.
1-SHUF3-1(IF)
Step 2 Configure Layer 2 parameters for the NNI ports. For details, see A.6.2.2 Setting Layer 2
Attributes for a Microwave Port.
This table describes values for Layer 2 parameters of the NNI ports.
1-SHUF3-1(IF)
----End

Procedure
Step 1 Create transparently transmitted point-to-point services. For details, see A.7.3.3 Creating a
QinQ-based E-Line Service.
This table provides parameter values for NE11, NE12, NE13, and NE14.
Table 8-114 Information about the QinQ-based E-Line services
Service ID 1 2
Service Name RAN1toNodeB1_Qline RAN2toNodeB2_Qline
Direction UNI-NNI UNI-NNI
Source C-VLANs - -
Source QinQ link - -

Sink QinQ link ID: 1 ID: 2

Port: 1-SHUF3-1(IF) Port: 1-SHUF3-1(IF)
SVLAN: 100 SVLAN: 200
This table provides parameter values for ports on NE11, NE12, NE13, and NE14.
1-SHUF3-2(GE1) 1-SHUF3-4(GE3) 1-SHUF3-1(IF)
VLAN ID - - -
Encapsulation 802.1Q 802.1Q QinQ

Type
Tag - - -
----End

Procedure
DS Domain.
CVLAN IP DSCP PHB

SVLAN
MPLS EXP

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21

CVLAN IP DSCP PHB

SVLAN
MPLS EXP
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
CVLAN IP DSCP PHB

SVLAN

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43

CVLAN IP DSCP PHB

SVLAN
40 EF
48 CS6
56 CS7
NE Port Packet Type
NE11/NE12/NE13/NE14 1-SHUF3-2(GE1) ip-dscp

1-SHUF3-4(GE3)
1-SHUF3-1(IF)
NOTE
Policies.
ports.
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
and Ethernet ports.

----End
8.6.7.10 Procedure of Configuration on a Per-NE Basis (Ethernet Service

Verification)
Context
NOTE
In this example, only the connectivity of the main link (NE11–NE13) needs to be verified normally. After
services are switched to the standby link (NE12–NE14), connectivity of the standby link needs to be verified.
Procedure
Parameter Value
Maintenance Domain Name EdgeNE
Maintenance Domain Level 4
Parameter Value
RAN 1–NodeB 1 RAN 2–NodeB 2

Name

Parameter Value
RAN 1–NodeB 1 RAN 2–NodeB 2
Maintenance Association RAN1_Qline RAN2_Qline

Name
Relevant Service 1-RAN1toNodeB1_Qline 2-RAN2toNodeB2_Qline
CC Test Transmit Period 1s 1s
Parameter Value
NE11 NE13

Domain Name
Maintenance RAN1_Qline RAN2_Qline RAN1_Qline RAN2_Qline

Association
Name
VLAN 100 200 100 200
MEP ID 101 201 102 202
Parameter Value
NE11 NE13

Domain Name
Maintenance RAN1_Qline RAN2_Qline RAN1_Qline RAN2_Qline

Association
Name

Parameter Value
NE11 NE13
Remote 102 202 101 201

Maintenance
Point ID(e.g:
1,3-6)
Perform an LB test for services between RAN 1 to NodeB 1 by considering the MEP whose
MEP ID is 101 as the source MEP and the MEP whose MEP ID is 102 as the sink MEP.
Perform an LB test for services between RAN 2 to NodeB 2 by considering the MEP whose
MEP ID is 201 as the source MEP and the MEP whose MEP ID is 202 as the sink MEP.
----End

In this example, LAGs need to be configured for the OptiX RTN 900 to implement 1+1 HSB
protection for two channels of received GE services, together with OptiX RTN 380. For details,
see the OptiX RTN 900 Configuration Guide.
8.6.7.12 End-to-End Configuration Procedure (UNI and NNI Ports)

In this example, the NNI port information needs to be configured prior to QinQ-based E-Line
services.
Procedure
Step 1 Configure the basic attributes for the UNI ports. For details, see A.6.1.1 Setting the Basic
Attributes for an Ethernet Port.
This table provides values for basic parameters of the UNI ports.
Step 2 Configure the basic attributes for the NNI ports. For details, see A.6.2.1 Setting Basic Attributes
for a Microwave Port.
This table provides values for basic parameters of the NNI ports.

1-SHUF3-1(IF)
Step 3 Configure Layer 2 parameters for the NNI ports. For details, see A.6.2.2 Setting Layer 2
Attributes for a Microwave Port.
This table describes values for Layer 2 parameters of the NNI ports.
1-SHUF3-1(IF)
----End

Context
This section describes the procedure for configuring Ethernet services between RAN 1 and the
RNC. The procedure for configuring Ethernet services between RAN 2 and the RNC is similar.
Procedure
LAN Service.
10.4 Creating a QinQ-based E-Line Service.


b. Select 1-SHUF3-2(GE1), set C-VLAN to blank and set S-VLAN to blank.
c. Click OK.
e. Select 1-SHUF3-2(GE1), set C-VLAN to blank and set S-VLAN to blank.
f. Click OK.

5. Check the service path information. Set Out S-VLAN and In S-VLAN for each node on
the service path.
7. Click OK.
----End

Procedure
DS Domain.
CVLAN IP DSCP PHB

SVLAN
MPLS EXP

all the parameters.
12 AF11

CVLAN IP DSCP PHB

SVLAN
MPLS EXP
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
CVLAN IP DSCP PHB

SVLAN

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33

CVLAN IP DSCP PHB

SVLAN
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
NE Port Packet Type
NE11/NE12/NE13/NE14 1-SHUF3-2(GE1) ip-dscp

1-SHUF3-4(GE3)
1-SHUF3-1(IF)
NOTE
Policies.
ports.
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP

and Ethernet ports.
----End

Configurations)
Context
This section describes the procedure for verifying Ethernet services between RAN 1 and the
RNC. The procedure for verifying Ethernet services between RAN 2 and the RNC is similar.
Procedure
menu.
the shortcut menu.

NOTE
for an LB test.
Step 6 Click Run.
----End
8.6.8 Configuration Example (IEEE 802.1D Bridge-based E-LAN

Service)
This section provides an example of how to configure IEEE 802.1D bridge-based Ethernet local
area network (E-LAN) services according to the network plan.


a Ring Network) and the following requirements.

Servic NodeB 1 and NodeB 2 provide l Configure IEEE 802.1D bridge-based

e GE ports that work in auto- Ethernet local area network (E-LAN)
access negotiation mode. services.
capaci l Configure loop detection and the broadcast
ty packet suppression functions.
Servic l Configure protection for l Configure Ethernet ring protection switching
e Ethernet services on ring (ERPS).
protec networks.
tion l The network must provide
the service loop detection
function and the broadcast
packet suppression function.
Servic Ethernet services from NodeB 1

e and NodeB 2 need to be
separa transparently transmitted.
tion
Qualit The priorities of Ethernet Configure DiffServ and perform service

y of services transmitted over a scheduling and forwarding based on DSCP
servic microwave network are values.
e identified by DSCP values. All
(QoS) the NEs on the microwave

Figure 8-57 Networking diagram for IEEE 802.1D bridge-based E-LAN services
NMS
NodeB 1
P&E
LAN switch
GE GE
NE31 NE36
802.1D bridge 802.1D bridge
P&E Local backhaul
network
RNC
GE GE NE35
NE32
GE GE
P&E
NodeB 2
NE33 NE34
8.6.8.2 Service Planning (Ethernet Ports)

This section describes the parameters required for configuring Ethernet ports and microwave
ports.

services.
NOTE


Parameter Encapsulati Working Flow Broadcast Broadcast

on Type Mode Control Packet Packet
Suppressio Suppressio
n n Threshold
NE31 1-SHUF3-4 Null Auto- Disabled Enabled 30

(GE3) Negotiation

(GE3) Negotiation

(GE1) Negotiation
1-SHUF3-4 Null Auto- Disabled Enabled 30

(GE3) Negotiation

(GE3) Negotiation

(GE1) Negotiation

(GE3) Negotiation

(GE1) Negotiation

(GE3) Negotiation
NOTE
l In this example, the GE ports on all the NodeBs work in auto-negotiation mode. Therefore, the peer GE port
of each NE that receives services must work in auto-negotiation mode. If the peer Ethernet port works in
another mode, the local Ethernet port must be set to the same mode. The working modes of the Ethernet
ports inside the network are planned as auto-negotiation.
l In this example, the loopback port shutdown function is disabled for the Ethernet ports.

Parameter Encapsulation Broadcast Broadcast

Type Packet Packet
Suppression Suppression
Threshold
NE31 1-SHUF3-1(IF) Null Enabled 30

Parameter Encapsulation Broadcast Broadcast

Type Packet Packet
Threshold

This section describes the parameters required for configuring Ethernet protection.
Information About ERP Instances

Table 8-118 provides the planning information about Ethernet ring protection (ERP) instances.
Table 8-118 Information about ERP instances

Item NE31 NE32 NE33 NE34 NE35 NE36
ERPS ID 1 1 1 1 1 1
East Port 1- 1- 1- 1- 1- 1-
SHUF3-1 SHUF3-4 SHUF3-1 SHUF3-4 SHUF3-1 SHUF3-4
(IF) (GE3) (IF) (GE3) (IF) (GE3)
West Port 1- 1- 1- 1- 1- 1-
(GE3) (IF) (GE3) (IF) (GE3) (IF)
RPL No Yes No No No No
Owner
Ring Node
Flag
RPL Port - 1- - - - -
SHUF3-4
(GE3)
Control 4093 4093 4093 4093 4093 4093

VLAN
Packet 5s (default 5s (default 5s (default 5s (default 5s (default 5s (default

Transmit value) value) value) value) value) value)
Interval(s)

Item NE31 NE32 NE33 NE34 NE35 NE36
Entity 4 (default 4 (default 4 (default 4 (default 4 (default 4 (default

Level value) value) value) value) value) value)
WTR - 5 minutes - - - -
Time (default
value)
Guard 500 ms 500 ms 500 ms 500 ms 500 ms 500 ms

Time (ms) (default (default (default (default (default (default
Hold-Off 0s (default 0s (default 0s (default 0s (default 0s (default 0s (default

Time (ms) value) value) value) value) value) value)
NOTE
l In this example, all the services are aggregated on NE35. Therefore, the NE that is farthest from NE35 needs
to function as the RPL owner. In this manner, when the ring network is normal, the traffic carried on each
link is relatively even.
l The control VLAN ID must be unique. It is recommended that the control VLAN ID take the value 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally take their
default values.

Table 8-119 provides the planning information about an IEEE 802.1D bridge-based Ethernet
service.
Table 8-119 Information About an IEEE 802.1D bridge-based E-LAN service
Paramete NE31 NE32 NE33 NE34 NE35 NE36

r
Service ID 1 1 1 1 1 1
Service Dlan Dlan Dlan Dlan Dlan Dlan

Name
Tag Type Tag- Tag- Tag- Tag- Tag- Tag-

Transpare Transpare Transpare Transpare Transpare Transpare
nt nt nt nt nt nt
MAC Enabled Enabled Enabled Enabled Enabled Enabled

Address
Learning
MAC SVL SVL SVL SVL SVL SVL

Address
Learning
Mode

Paramete NE31 NE32 NE33 NE34 NE35 NE36

r
Mounted 1- 1- 1- 1- 1- 1-
UNI port SHUF3-4 SHUF3-4 SHUF3-2 SHUF3-4 SHUF3-2 SHUF3-2
(GE3) (GE3) (GE1) (GE3) (GE1) (GE1)
1- 1- 1- 1- 1- 1-
(IF) (IF) (GE3) (IF) (GE3) (GE3)
1- 1- 1-
SHUF3-1 SHUF3-1 SHUF3-1
(IF) (IF) (IF)

This section describes the parameters required for configuring quality of service (QoS).
DiffServ
CS7 56 -
CS6 48 -

signaling
AF41 36 -
AF42 34 -
AF43 32 -

and HSPA streaming
services)

AF32 26 -

HSDPA service (HSPA
streaming service)

and R99 background
services)
AF22 18 -

and R99 background
services)
AF11 12 -
AF12 10 -
AF13 8 -

services)
NOTE

CS6 SP
EF SP
AF4 SP
AF3 SP

AF2 SP
AF1 SP
BE SP
CS7 Tail drop
CS6 Tail drop
EF Tail drop
AF4 Tail drop
AF3 Tail drop
AF2 Tail drop
AF1 Tail drop
BE Tail drop
CAR
Shaping
8.6.8.6 Per-NE Configuration Procedure (Ethernet Protection)

Procedure
Step 1 Create an Ethernet ring protection switching (ERP) instance. For details, see A.7.1.1 Creating
an ERP Instance.
This table provides parameter values for creating an ERP instance.

Paramete Value
r
ERPS ID 1 1 1 1 1 1
East Port 1- 1- 1- 1- 1- 1-
West Port 1- 1- 1- 1- 1- 1-
RPL No Yes No No No No
Owner
Ring
Node Flag
RPL Port - 1- - - - -
SHUF3-4
Control 4093 4093 4093 4093 4093 4093

VLAN
----End
8.6.8.7 Per-NE Configuration Procedure (Service Information)

Procedure
Step 1 Configure Ethernet local area network (E-LAN) services based on the IEEE 802.1D bridge. For
details, see A.7.3.6 Creating an IEEE 802.1D Bridge-based E-LAN Service.
l Parameters of NE31, NE32, and NE34
This table lists the ports to be selected.
Port
1-SHUF3-4
1-SHUF3-1
This table provides service parameter values.
Parameter Value
Service ID 1
Service Name Dlan
Direction Tag-Transparent

Parameter Value
L2 Protocol Control Not Transparent
MAC Address Learning Enabled
This table provides port parameter values
Parameter 1-SHUF3-4 1-SHUF3-1
VLAN ID (e.g. 1,3-5) Blank Blank
Encapsulation Type Null Null
Tag - -
l Parameters of NE33, NE35, and NE36

This table lists the ports to be selected.
Port
1-SHUF3-2
1-SHUF3-4
1-SHUF3-1
This table provides service parameter values.
Parameter Value
Service ID 1
Service Name Dlan
Direction Tag-Transparent
This table provides port parameter values
Parameter 1-SHUF3-2 1-SHUF3-4 1-SHUF3-1

Parameter 1-SHUF3-2 1-SHUF3-4 1-SHUF3-1
VLAN ID (e.g. Blank Blank Blank

1,3-5)
Encapsulation Null Null Null

Type
Tag - - -
----End
8.6.8.8 Per-NE Configuration Procedure (Ethernet Ports)

This section describes the procedure for configuring Ethernet ports and microwave ports.
Procedure
Step 1 Configure the advanced attributes of Ethernet ports. For details, see A.6.1.4 Setting the
Advanced Attributes for an Ethernet Port.
This table provides parameter values for Ethernet ports.
Parameter Loopback Broadcast Broadcast

Check Packet Packet
Threshold
NE31 1-SHUF3-4 Enabled Enabled 30
1-SHUF3-4 Enabled Enabled 30
This table provides parameter values for microwave ports.

Parameter Broadcast Packet Broadcast Packet

Threshold
NE31 1-SHUF3-1 Enabled 30
----End
8.6.8.9 Per-NE Configuration Procedure (QoS)

Procedure
Step 1 Modify the mapping for a Differentiated Services (DS) domain. For details, see A.7.6.1
Modifying the Mapping for a DS Domain.
CVLAN MPLS EXP IP DSCP PHB
Default value Default value 0 BE
12 AF11
8 AF13
20 AF21
16 AF23
28 AF31
24 AF33
36 AF41
32 AF43
40 EF
48 CS6
56 CS7

12 AF11
8 AF13
20 AF21
16 AF23
28 AF31
24 AF33
36 AF41
32 AF43
40 EF
48 CS6
56 CS7
Step 2 Modify the ports in the DS domain and their trusted packet types. For details, see A.7.6.2
This table provides parameter values for NE33, NE35, and NE36.
Parameter Packet Type
GE1 ip-dscp
GE3
IF
GE3 ip-dscp
IF
NOTE
packet type needs to be changed for service-associated Ethernet ports in the default DS domain.
Policies.

ports.
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
and Ethernet ports.
----End
8.6.8.10 Per-NE Configuration Procedure (Ethernet Service Verification)

Procedure
Step 1 Create maintenance domains (MDs). For details, see A.7.7.1 Creating an MD.
This table provides parameter values for creating MDs.

Parameter Value
NE33 NE35 NE36

Domain Name
Maintenance 4 4 4
Domain Level
This table provides parameter values for creating MAs.
Parameter Value
NE33 NE35 NE36

Domain Name
Maintenance Dlan Dlan Dlan

Association Name
Relevant Service 1-Dlan 1-Dlan 1-Dlan
CC Test Transmit 1s 1s 1s
Period
Step 3 Create maintenance association end points (MEPs). For details, see A.7.7.3 Creating an
MEP.
This table provides parameter values for creating MEPs
Parameter Value
NE33 NE35 NE36

Domain Name
Maintenance Dlan Dlan Dlan

Association Name
Board 1-SHUF3 1-SHUF3 1-SHUF3
Port GE1 GE1 GE1
VLAN - - -
MEP ID 103 105 106
Direction Ingress Ingress Ingress
CC Status Active Active Active

Step 4 Specify remote MEPs. For details, see A.7.7.4 Creating a Remote MEP in an MA.
l This table provides parameter values for creating remote MEPs for NE35.
Parameter Value

Name
Maintenance Association Dlan Dlan

Name
MP ID 103 106
l This table provides parameter values for creating a remote MEP for NE33.
Parameter Value
Maintenance Association Name Dlan
MP ID 105
l This table provides parameter values for creating a remote MEP for NE36.
Parameter Value
Maintenance Association Name Dlan
MP ID 105
Step 5 Perform loopback (LB) tests. For details, see A.7.7.7 Performing an LB Test.
Perform the LB test by considering the MEP whose MEP ID is 105 as the source MEP and the
Perform the LB test by considering the MEP whose MEP ID is 105 as the source MEP and the
----End

Procedure
Step 1 Create optical fibers manually. For details, see A.3.4.1 Creating a Fiber/Cable by Using the
Search Method.

This table provides parameter values for creating optical fibers manually.
Parameter Value
GE Optical Fiber GE Optical Fiber GE Optical Fiber

between NE31 and between NE32 and between NE34 and
NE36 NE33 NE35
Fiber/Cable Type Fiber Fiber Fiber
Source NE NE31 NE32 NE34
Source Board 1-SHUF3 1-SHUF3 1-SHUF3
Source Port 4 4 4
Sink NE NE36 NE33 NE35
Sink Board 1-SHUF3 1-SHUF3 1-SHUF3
Sink Port 4 4 4
Automatically No No No
Allocate IP Address
NOTE
This example is based on the hypothesis that the microwave links have been created during microwave link
configuration.
Step 2 Create Ethernet local area network (E-LAN) services transmitted in Native Ethernet mode. For
details, see A.10.5 Creating an IEEE 802.1D Bridge-based E-LAN Service.
1. Choose ServiceNative Ethernet ServiceCreate E-LAN Service from the Main Menu.
2. Set the general attributes for E-LAN services.
3. Configure bridge-mounted ports for E-LAN services.

a. Double-click NE35 in the Physical Topology tab page.
b. Set Tag Type to Tag-Transparent.
c. Under Available Interface, select 1-SHUF3-2(GE1), 1-SHUF3-4(GE3), and 1-
SHUF3-1(IF), and click .

d. Click OK.
4. Repeat Step 2.3 to configure bridge-mounted ports on NE32, NE33, NE34, and NE36 based
on 8.6.8.4 Service Planning (Ethernet Services).
5. Set the general attributes for the bridge-mounted ports.
a. Click .
b. Click the Interface Information tab.
c. Set the general attributes for the bridge-mounted ports.
NE Interface Enable Port Working Mode Max Frame

Length (byte)
NE31 1-SHUF3-4(GE3) Enabled Auto-Negotiation 9600
1-SHUF3-1(IF) - - -
1-SHUF3-1(IF) - - -
1-SHUF3-4(GE3) Enabled Auto-Negotiation 9600
1-SHUF3-1(IF) - - -
1-SHUF3-1(IF) - - -
1-SHUF3-1(IF) - - -
1-SHUF3-1(IF) - - -
6. Set the advanced attributes for the bridge-mounted ports.
a. Click .
b. Click the Interface Information tab.
c. Select the desired bridge-mounted ports.
d. Click .
e. Click the Advanced Attributes tab and set the advanced attributes for the ports.

NE Port Loopback Check Broadcast Packet Broadcast Packet

Threshold
NE31 1-SHUF3-4(GE3) Enabled Enabled 30
1-SHUF3-1(IF) Enabled Enabled 30
1-SHUF3-4(GE3) Enabled Enabled 30
7. Configure Ethernet Ring Protection Switching (ERPS).
a. Click .
b. Click the ERPS tab. Then, click Add.
c. Based on 8.6.8.3 Service Planning (Ethernet Protection), Set the parameters for the
ERPS protection instance.
d. Click OK.
e. Set the parameters for the ERPS protocol.

9. Click Configure. In the Configure Ethernet OAM dialog box, configure Ethernet
operation, administration and maintenance (ETH OAM) port information.

10. Click OK.
----End

Procedure
Step 1 Modify the mapping for a Differentiated Services (DS) domain. For details, see A.7.6.1
Modifying the Mapping for a DS Domain.
12 AF11
8 AF13
20 AF21
16 AF23
28 AF31
24 AF33
36 AF41
32 AF43
40 EF
48 CS6
56 CS7
12 AF11
8 AF13
20 AF21
16 AF23
28 AF31

24 AF33
36 AF41
32 AF43
40 EF
48 CS6
56 CS7
Step 2 Modify the ports in the DS domain and their trusted packet types. For details, see A.7.6.2
GE1 ip-dscp
GE3
IF
GE3 ip-dscp
IF
NOTE
packet type needs to be changed for service-associated Ethernet ports in the default DS domain.
Policies.
ports.
CS7 SP
CS6 SP
EF SP

AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
and Ethernet ports.
----End

Configurations)
Procedure
menu.
the shortcut menu.

NOTE
for an LB test.
Step 6 Click Run.


Step 8 Repeat steps Step 3 to Step 7 to verify the Ethernet services transmitted from the radio network
controller (RNC) to NodeB 1.
----End
8.6.9 Configuration Example (IEEE 802.1q Bridge-based E-LAN

Services)
This section uses an IEEE 802.1q bridge-based E-LAN service as an example to describe how
to configure Ethernet services according to the service plan.


a Chain Network) and the following requirements.
Servic Configure a port working in The OptiX RTN 380 provides an electrical P&E
e auto-negotiation mode for port for receiving services.
access receiving a channel of electrical
capaci GE signals from NodeB 1.
ty Configure a port working in
auto-negotiation mode for
receiving a channel of electrical
GE signals from RAN 1.
Servic No -
e
protec
tion
Servic Separate services from NodeB 1 l Configure VLAN-based E-Line services for
e and RAN 1 from each other NE21, NE22, and NE24.
separa using VLAN IDs: l Configure IEEE 802.1q bridge-based E-LAN
tion l VLAN ID of NodeB 1: 100 services for NE23.
l VLAN ID of RAN 1: 200


NOTE
For details about how to plan and configure VLAN-based E-Line services for NE21, NE22, and NE24, see 8.6.6
Configuration Example (VLAN-based E-Line Services). We will illustrate how to plan and configure IEEE
802.1q bridge-based E-LAN services for NE23.
Figure 8-58 Networking diagram for IEEE 802.1q bridge-based E-LAN services
NMS
RNC
LAN
switch
Regional
Backhaul
Network
P&E GE GE
P&E
NodeB 1 P&E NE99

VLAN 100 NE21 NE22 NE23 NE24
RAN1
VLAN 200


Table 8-124 provides the information about the Ethernet ports on NE23.
NOTE



Parameter 1-SHUF3-2(GE1) 1-SHUF3-4(GE3)
Flow Control Disabled Disabled
Tag Type Tag Aware Tag Aware
NOTE
l In this example, the GE ports on the NodeB 1 and RAN 1 connected to the OptiX RTN 380 work in auto-
mode. If the peer Ethernet ports work in another mode, the local Ethernet ports must work in the same mode.
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag-aware.

Table 8-125 provides the information about the microwave port on NE23.

Parameter 1-SHUF3-1(IF)
Tag Type Tag Aware


Configure IEEE 802.1q bridge-based E-LAN services for NE23 according to Table 8-126.
Table 8-126 Information about IEEE 802.1q bridge-based E-LAN services

Item NE23
Service ID 1
Service Name Qlan
Tag C-Aware

Item NE23
MAC Address Learning Mode IVL
Mounted UNI port 1-SHUF3-2(GE1) (VLAN ID: 200)

1-SHUF3-4(GE3) (VLAN ID: 100)
1-SHUF3-1(IF) (VLAN ID: 100, 200)

DiffServ
CS7 56 -
CS6 48 -

signaling
AF41 36 -
AF42 34 -
AF43 32 -

and HSPA streaming
services)
AF32 26 -


HSDPA service (HSPA
streaming service)

and R99 background
services)
AF22 18 -

and R99 background
services)
AF11 12 -
AF12 10 -
AF13 8 -

services)
NOTE

CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP

AF1 SP
BE SP
CS7 Tail drop
CS6 Tail drop
EF Tail drop
AF4 Tail drop
AF3 Tail drop
AF2 Tail drop
AF1 Tail drop
BE Tail drop
CAR
Shaping


Procedure

Step 2 Create an IEEE 802.1q bridge-based E-LAN service. For details, see A.7.3.7 Creating an IEEE
802.1Q Bridge-based E-LAN Service.
This table provides parameter values for mounted ports of NE23.
Port
1-SHUF3-2(GE1)
1-SHUF3-4(GE3)
1-SHUF3-1(IF)
This table provides parameter values for the bridge-based service.
Parameter Value
Service ID 1
Service Name Qlan
Tag C-Aware
This table provides parameter values for related ports.
Parameter 1-SHUF3-2(GE1) 1-SHUF3-4(GE3) 1-SHUF3-1(IF)
VLAN ID 200 100 100,200
Encapsulation 802.1Q 802.1Q 802.1Q

Type
Tag Tag Aware Tag Aware Tag Aware
----End
8.6.9.8 Procedure of Configuration on a Per-NE Basis (Port Information)

This section describes the procedure for configuring Ethernet ports and microwave ports.
Procedure
Step 1 Configure the advanced attributes of Ethernet ports. For details, see A.6.1.4 Setting the
Advanced Attributes for an Ethernet Port.

This table provides parameter values for Ethernet ports.
Parameter Loopback Broadcast Broadcast

Check Packet Packet
Threshold

(GE1)
1-SHUF3-4
NE32 (GE3)
This table provides parameter values for microwave ports.
Parameter Broadcast Packet Broadcast Packet

Threshold
NE32 1-SHUF3-1(IF) Enabled 30
----End

Procedure
DS Domain.
CVLAN IP DSCP PHB

SVLAN
MPLS EXP

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23

CVLAN IP DSCP PHB

SVLAN
MPLS EXP
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6
56 CS7
CVLAN IP DSCP PHB

SVLAN

all the parameters.
12 AF11
10 AF12
8 AF13
20 AF21
18 AF22
16 AF23
28 AF31
26 AF32
24 AF33
36 AF41
34 AF42
32 AF43
40 EF
48 CS6

CVLAN IP DSCP PHB

SVLAN
56 CS7
NE Port Packet Type

1-SHUF3-4(GE3)
1-SHUF3-1(IF)
NOTE
Policies.
ports.
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP
and Ethernet ports.

----End
8.6.9.10 Procedure of Configuration on a Per-NE Basis (Ethernet Service

Verification)
Procedure
Parameter Value
NE21 NE23 NE24

Domain Name
Maintenance 4 4 4
Domain Level
Parameter Value
NE21 NE23 NE24

Domain Name

Association
Name

Parameter Value
NE21 NE23 NE24
Relevant 1- 1- 1- 1-
Service NodeB1toNE22 RAN1toNE24_ NE23toNE99_ NE23toNE99_
_Vline Vline Vline Vline
CC Test 1s 1s 1s 1s
Transmit
Period
Parameter Value
NE21 NE23 NE24

Domain Name

Association
Name
VLAN 100 200 100 200
MEP ID 101 201 102 202
Parameter Value
NE21 NE23 NE24

Domain Name

Association
Name

Parameter Value
NE21 NE23 NE24
Remote 102 202 101 201

Maintenance
Point ID(e.g:
1,3-6)

----End
8.7 Configuring Clocks

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.

Before configuring clocks, familiarize yourself with the basic concepts.
8.7.1.1 Clock Source

A clock source is used to synchronize the components of an NE or upstream and downstream
NEs, and to provide stable and accurate operating frequency for the functional modules and
chips of an NE. With the clock source, services can be transmitted correctly and in strict order.
OptiX RTN 380 supports the following clock sources:
l Radio clock source: a clock source that is extracted from a received radio signal stream.
l Ethernet clock source: a clock source that is extracted from a received synchronous Ethernet
signal stream.
l Internal clock source: a clock source that is generated through the free-run oscillation of
an NE built-in clock. The internal clock source has the lowest priority.
8.7.1.2 Clock Protection Modes

The OptiX RTN 380 supports clock source protection based on priorities, synchronization status
message (SSM) protection, and extended SSM protection.
Clock Source Protection Based on Priorities

Clock source protection is provided based on the priorities specified in the clock source priority
list. When a higher priority clock source fails, a lower priority clock source is used. Only clock

sources added to the clock source priority list can be selected. The internal clock source is the
clock source with the lowest priority.
As shown in Figure 8-59, a link aggregation group (LAG) protects the services between NE11
and the RNC. NE11 traces the clock of the RNC through synchronous Ethernet. Ports GE1 and
GE2 on NE11 need to be added to the clock source priority list so that NE1 can obtain reference
clock from GE2 when GE1 fails.
Figure 8-59 Clock source protection based on priorities
NE11
NE21 GE1
Radio GE2
Internal Internal
RNC
GE1
Radio link
GE2
NE NAME
Cable Clock synchronization
Clock priority 1
Clock priority 2
Radio link
Internal clock
SSM Protection
SSM protection enhances clock source protection based on priorities and triggers clock switching
based on the clock source quality level. Table 8-130 provides details on SSM protection.
Table 8-130 SSM protection

Item Description
Definition SSM protection refers to the clock protection in compliance with the SSM
protocol specified in ITU-T G.781. The SSM protocol defines the levels and
states of clock signals.
Channel The OptiX RTN 380 supports SSM protection on Ethernet links and radio
links.
l On radio links, SSM messages are transmitted through specific overhead
bytes.
l On GE ports, SSM messages are transmitted through specific protocol
control packets.

Item Description
Function SSM messages can be identified for:

l Selecting the high-quality clock source as the reference clock
l Preventing a timing loop between two clock devices
Handling Once SSM protection is enabled on an NE, automatic protection switching

process 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 as the synchronization source.
l The NE broadcasts the quality information of the synchronization clock
source to its downstream NE, and also notifies its upstream NE that its
own clock source cannot be used for synchronization.
Application The SSM protocol can be applied to a ring network with one external
scenario reference source or a chain network with two external reference sources.
When the SSM protocol is applied to a ring network, the node where the
reference clock is injected cannot select any clock sources on the ring. The
other nodes can select the east or west clock source on the ring.
Figure 8-60 is a microwave ring where the SSM protection is enabled.
When the network operates normally, the NEs on the ring select the clock source as follows:
1. NE11 selects the external clock source as the synchronous source and sends the clock
quality message "G.812" to NE12 and NE13.
2. NE12, NE13, NE21, NE22, NE31, and NE32 select the upstream clock source from their
own clock source priority lists.
3. In addition, each NE sends a Don't Use for Sync. (DUS) message to the upstream direction.
4. Although NE22 and NE31 detect usable clock sources from the radio link, they decide not
to switch clock sources because the priorities of the protection clock sources are the same
as the working clock sources.
When the microwave links between NE12 and NE21 become faulty, the NEs on the ring select
the clock source as follows:
1. NE12, NE13, NE32, and NE31 use the current clock sources.
2. NE21 loses the west clock source and finds the DUS message in the east direction.
Therefore, NE21 selects the internal clock and sends a G.812 clock quality message to the
downstream.
3. NE22 finds that the west clock source is the internal clock, inferior to the east clock source
of G.812. Therefore, NE22 selects the east clock source. In addition, NE22 sends a DUS
message to the east link and sends a G.812 clock quality message to the west link.
4. NE21 receives the G.812 clock quality message from NE22, selects the east clock source,
and sends a DUS message to the east link, after which clock switching is completed on the
ring.

NOTE
SSM protection does not provide a complete solution to the timing loop. Do not configure the clock sources that
may form a loop. For example, you should not add the west and east clock sources to the clock source priority
list on NE11.
Figure 8-60 SSM protection
NE11 BITS
Radio link Radio Network
Internal
NE12 NE13
W: GE E: GE
E: Radio W: Radio
Internal Internal
E W
W E
NE21 W E NE32
W: Radio E: Radio
E: GE W: GE
Internal Internal
E W
W E
NE22 NE31
W: GE E: GE
E: Radio E W W: Radio
Internal Internal
Clock synchronization Radio link NE NAME

Clock priority 1
E East Clock priority 2
Cable
Internal clock
W West
Extended SSM Protection

Extended SSM protection uses clock source markers to perform SSM protection. Table 8-131
provides details on extended SSM protection.

Table 8-131 Extended SSM protection

Item Description
Definition Extended SSM protection refers to clock protection in compliance with

Huawei-defined extended SSM protocol that introduces clock IDs into the
SSM protocol. Clock IDs are transmitted with SSM messages and are used
in automatic clock switching.
The clock ID takes a value from 0 to 15. 0 being the default value indicates
an invalid clock ID. After the extended SSM protocol is enabled, the NE
does not select clock source 0 as the current clock source.
Channel Extended SSM protection is always applied with SSM protection. The OptiX
RTN 380 supports extended SSM protection and SSM protection on Ethernet
and microwave links.
l On microwave links, SSM messages and extended SSM messages are
transmitted through specific overhead bytes.
l On GE ports, SSM messages and extended SSM messages are
transmitted through specific protocol control packets.
Function Extended SSM messages prevent timing loops because clock devices can
determine whether clock references come from their own input.
Handling After extended SSM protection is enabled on an NE, automatic clock

process switching conforms to the following rules:
l According to the clock source priority list, the NE selects the clock source
of the best quality as its synchronization source.
l If the clock ID of a certain clock source indicates that the clock source
is from the NE itself, that source is not processed.
l If multiple clock sources are of equally high quality, the NE selects the
one of the highest priority as the synchronization source.
l The NE broadcasts the quality information and the clock ID of the
synchronization clock source to its downstream NE, and also notifies its
upstream NE that its own clock source cannot be used for
synchronization.

Item Description
Application Extended SSM protocol applies to complex clock synchronization networks,

scenario such as networks with multiple clock references, tangent rings, intersecting
rings, and mesh networks.
Clock IDs are allocated as follows:
l When 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 any node intersecting a ring or chain with a ring, the internal clock
sources should have a clock ID.
l At any node intersecting a ring or chain with a ring, clock sources that
are accessed within the ring should have a clock ID.
l Clock sources other than the preceding types should always have their
clock ID set to the default value 0.
l Clock IDs are used for timing reference only. They do not indicate any
priority difference.
Figure 8-61 is a microwave ring with extended SSM protection enabled.

On the ring, the following clock sources require a clock ID:
l P&E interface clock on NE11
l P&E interface clock on NE42
l Internal clock source on NE11
l Internal clock source on NE42

Figure 8-61 Extended SSM protection
Master BITS
NE11
NE12
P&E
W: GE
W: Radio 1
E: Radio
P&E E: GE
Internal
Internal
E NE32
NE21 W
E: Radio
W: Radio W: GE
W E
E: GE
Internal
Internal W E
E W
W E
NE22 NE31
W: GE W E: GE
E
E: Radio W: Radio
Internal W E Internal
NE41 NE42
EW
W: Radio W: GE
P&E
E: GE E: Radio
Internal P&E
Internal
Slave BITS
Clock synchronization Radio link

NE NAME
E East Clock priority 1
Cabel/fiber Clock priority 2
W west Internal clock
NOTE
l The extended SSM protection provides a complete solution to the timing loop. Therefore, 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.
8.7.1.3 Clock Synchronization Policy

Plan an appropriate clock synchronization policy based on the network topology.

Clock Synchronization Policy for a Chain Network

For a chain network consisting of microwave links, plan the clock synchronization policy
according to the following principles:
l If an Ethernet clock source is input into the master (source) node, configure this clock
source for this node.
l For the other nodes, configure the clock sources from their upper-level microwave links.
l If a node has multiple upper-level microwave links , configure one radio clock source for
each microwave link and allocate priorities to these radio clock sources based on the
microwave link status.
l Do not configure synchronization status message (SSM) or extended SSM protection.
Figure 8-62 shows the clock synchronization policy for a chain network.
l An Ethernet clock source is input into the master node NE1. The clock source priorities for
NE1 in descending order are: GE1 (the Ethernet clock source) > internal clock source.
l NE2 is the downstream NE of NE1. Therefore, the clock source priorities for NE2 in
descending order are: IF > internal clock source.
l NE3 and NE2 are cascaded. Therefore, the clock source priorities for NE3 in descending
order are: GE2 > internal clock source.
l NE4 is the downstream NE of NE3. Therefore, the clock source priorities for NE4 in
descending order are: IF > internal clock source.
l Do not configure SSM or extended SSM protection.
Figure 8-62 Clock synchronization policy for a chain network
GE
NE4
BITS NE1 NE2 NE3 IF/
Internal
GE1/ IF/ GE2/
Internal Internal Internal
Clock Microwave link Ethernet link
Clock Synchronization Policy for a Ring Network

For a ring network consisting of microwave links, plan the clock synchronization policy
according to the following principles:
Divide the ring into two chains and configure the clock synchronization policy separately on
each chain.

Figure 8-63 shows the clock synchronization policy for a ring network.
l Enable the SSM function for all nodes on the ring.

l An Ethernet clock source is input into the master node NE1. The clock source priorities for
NE1 in descending order are: GE1 (the Ethernet clock source) > internal clock source.
l NE2 traces the clock of NE1. Therefore, the clock source priorities for NE2 in descending
order are: IF > GE2 > internal clock source.
order are: GE2 > IF > internal clock source.
order are: IF > GE2 > internal clock source.
Figure 8-63 Clock synchronization policy for a ring network
BITS
GE2/
IF/
GE1/ GE Internal
Internal
NE1 NE6
IF/
IF/
GE2/
GE2/ NE2 NE5
Internal
Internal
NE3 NE4
GE2/ GE2/
IF/ IF/
Internal Internal
Clock Microwave link Ethernet link

Precautions of Planning a Clock Synchronization Policy

Take the following precautions when planning a clock synchronization policy.
The number of NEs on a long clock chain must not be more than 20. A number less 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.
Clock Synchronization Policy for Base Stations

The clock synchronization policy is as follows when a microwave transmission network
transmits clock synchronization signals to a base station.
If the base station is connected to the network through Ethernet ports, timing reference signals
are transmitted to the base station through the Ethernet ports.
If the base station is connected to the network through Ethernet ports only and does not support
the synchronous Ethernet function, you can provide timing reference signals to the base station
through an external clock port. OptiX RTN 380 does not support external clock ports.
8.7.2 Configuration Process (Configuring a Clock)

This section describes the process of configuring the clock source, clock protection, and output
clock.
Figure 8-64 shows the flowchart for configuring a clock.
Figure 8-64 Flowchart for configuring a clock
Required Start
Optional
Configure the clock
source.
Configure SSM or
extended SSM protection.
Query the clock

synchronization status.
End

Table 8-132 Process of configuring the clock

1 A.8.1.1 Configuring Clock Required. Set parameters as follows:

Sources Set Clock Source according to clock source
planning information.
2 Configu A.8.1.2 Required when the SSM or extended SSM

ring the Configuring protection is used. Set parameters as follows:
Synchro Protection for l Set Protection Status according to the used
nization Clock Sources protocol type.
Status
Messag l If the clock uses the extended SSM
e (SSM) protection, set Clock Source ID for the
or following clock sources:
extende – Internal clock source of the NE that
d SSM connects the intersecting ring and chain or
protecti connects the intersecting rings
on – 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.8.1.4 Required when the SSM or extended SSM

Enabling/ protection is used.
Disabling SSM When a line port is connected to the NE on the
Transmission same clock subnet, set Control Status to
Enabled. In other cases, set Control Status to
Disabled.
A.8.1.5 Required when the extended SSM protection is

Enabling/ used.
Disabling the When a line port is connected to the NE on the
Output of same clock subnet, set Output Clock ID to
Clock Source Enabled.
IDs
A.8.1.3 Optional.
Customizing
the Clock
Quality
3 A.8.1.7 Querying the Optional.

Clock Synchronization
Status

8.7.3 Configuration Example (Clock on a Microwave Chain

Network)
This section uses the clock on a microwave chain network as an example to describe how to
configure the clock according to the network plan.

Configure the clock for the network shown in Figure 8-65 according to 8.5.3 Configuration
Example (Microwave Links on a Chain Network) and the following requirements:
l Synchronize the microwave chain network with the clock of the RNC.
l Provide clock signals to NodeB 1 and RAN 1 through GE ports.

NMS
RNC
LAN
switch
Regional
Backhaul
Network
P&E GE GE
P&E
NodeB 1 P&E NE99

NE21 NE22 NE23 NE24
RAN 1

This section describes the parameters required for configuring clock on a microwave chain
network.

Clock Source Information

Obtain the clock source information shown in Figure 8-66 according to 8.7.1.3 Clock
Synchronization Policy.

NMS
RNC
LAN switch
Regional Backhaul
Network
GE GE
P&E
P&E NE99
NE21 NE22 NE23 NE24
Master Clock
Clock Protection
Configure clock priority protection for microwave links on the chain network.

In this example, the microwave transmission network is synchronized with the RNC through
GE ports, and transmits timing reference signals to NodeB 1 and RAN 1 through the GE ports.

This section describes the procedure for configuring clock on a microwave chain network.
Procedure
Step 1 Configure the clock source. For details, see A.8.1.1 Configuring Clock Sources.

This table provides parameter values for configuring the clock source.
Parameter Value
NE21 NE22 NE23 NE24
Clock Source 1-SHUF3-1 1-SHUF3-4 1-SHUF3-1 1-SHUF3-2

Internal Clock Internal Clock Internal Clock Internal Clock
Source Source Source Source
Step 2 Configure clock source protection. For details, see A.8.1.2 Configuring Protection for Clock
Sources.
Parameter Value
Start Standard SSM Protocol Selected
NOTE
The other parameters take their default values.
Step 3 Query the clock synchronization status. For details, see A.8.1.7 Querying the Clock
Synchronization Status.
NE Clock Mode must be Tracing Mode for all NEs.
----End
8.7.4 Configuration Example (Clock on a Microwave Ring Network)

This section provides an example of how to configure the clock on a microwave ring network

Based on 8.5.4 Configuration Example (Microwave Links on a Ring Network), configure
clocks according to the following requirements. Figure 8-67 shows the networking diagram.
l The microwave ring network is directly synchronized with the clock of the radio network
controller (RNC).
l Clock synchronization signals are transmitted to each NodeB through a GE port.

Figure 8-67 Networking diagram (clocks on a microwave ring network)
NMS
NodeB 1 GE
LAN switch
GE
NE31 NE36
GE Local backhaul
network
RNC
NE35
NE32
GE GE
GE
NodeB 2
NE33 NE34

This section describes the parameters required for configuring clocks on a microwave ring
network.
Clock Source Information

Based on 8.7.1.3 Clock Synchronization Policy, you can obtain the clock source information
as shown in Figure 8-68.

Figure 8-68 Networking diagram (clocks on a microwave ring network)

NMS
GE3/ IF/
IF/ GE3/
Internal Internal
LAN switch
GE
NE31 NE36
GE Local backhaul
IF/
GE3/ network
Internal GE1/
RNC
Internal
NE35
NE32
GE GE
GE3/ GE3/
IF/ NE33 NE34 IF/
Internal Internal
Master clock Microwave link Ethernet link
Clock Protection
The standard Synchronization Status Message (SSM) protocol is enabled for all NEs on the ring
network.

In this example, the microwave transmission network is synchronized with the radio network
controller (RNC) through GE ports, and transmits timing reference signals to the base station
through the GE ports.

This section describes the procedure for configuring clocks.
Procedure
Step 1 Configure the clock sources. For details, see A.8.1.1 Configuring Clock Sources.
This table provides parameter values for configuring clock sources.

Paramete Value
r
Clock 1- 1- 1- 1- 1- 1-
Source SHUF3-4 SHUF3-1 SHUF3-4 SHUF3-4 SHUF3-2 SHUF3-1
1- 1- 1- 1- Internal 1-
SHUF3-1 SHUF3-4 SHUF3-1 SHUF3-1 Clock SHUF3-4
Internal Internal Internal Internal Source Internal
Clock Clock Clock Clock Clock
Source Source Source Source Source
Step 2 Configure protection for the clock sources. For details, see A.8.1.2 Configuring Protection for
Clock Sources.
Parameter Value
Start Standard SSM Protocol Selected
NOTE
The other parameters take their default values.
Step 3 Query the clock synchronization status. For details, see A.8.1.7 Querying the Clock
Synchronization Status.
NE Clock Mode must be Tracing Mode for all NEs.
----End
8.8 Adding and Modifying Configuration Data

During the equipment commissioning and operating phases, you need to add or modify certain
configuration data according to the actual requirements.
8.8.1 Common Task Collection (Network Topology)

Common tasks associated with the network topology include common configuration tasks
associated with NE attributes.

Table 8-133 Common task collection (NE attributes)

Task Application Configuration Description
Scenario Operation
Creating NEs When using the A.3.1.2 Creating an NE l Generally, NEs

network management Manually or A.3.1.1 are created by
system (NMS) to Creating an NE by searching for the
perform centralized Using the Search NE on the NMS.
management of NEs, Method l The manual NE
create the icons of the creation method
NEs to be managed at is applicable only
corresponding when several NEs
positions on Main need to be created
Topology. on a large
microwave
transmission
network.
Changing an You must change an A.3.1.4 Changing an -

NE ID NE ID, if it does not NE ID
meet the network
planning requirements
(for example, if the NE
ID is the same as
another NE ID).
Changing the You must change the A.3.6.1 Setting NE -

IP address of an IP address of the Communication
NE gateway NE if changes Parameters
occur in the external
data communication
network (DCN)
between the NMS
server and the gateway
NE.
Synchronizing You can configure the A.3.1.6 Synchronizing To ensure that the NE
the NE time NE time to be the NE Time time is synchronized
automatically and correctly, the time
periodically and time domain of
synchronized. You can the NMS server must
also manually be set correctly.
synchronize the NE
time if the NE time is
lost due to NE faults.
8.8.2 Common Task Collection (Microwave Links)

This section describes the common configuration tasks associated with microwave links.

CAUTION
When you add or modify the configurations of a microwave link, you must first modify the
configurations of the NE that is located far from the network management system (NMS) server
and then modify the configurations of the NE that is located near to the NMS server.
NOTE
An MW_CFG_MISMATCH alarm is reported if the adaptive modulation (AM) status (enabled/disabled),

or parameters related to modulation schemes are set inconsistently at the two ends of a microwave link.
Clear the alarm as soon as possible because it may cause ineffective service configurations or service
interruptions.
Table 8-134 Common task collection (microwave links)

Scenario Operation
Configuring The ATPC function A.5.1 Configuring a To enable the ATPC

the automatic must be enabled for the Single Hop of function, set ATPC
transmit power microwave link or the Microwave Link Enable Status to
control values of ATPC Enabled and change
(ATPC) parameters must be other ATPC
function changed. parameter values
according to the
planning
information.
Changing the You can change the In RF, change TX

transmit power transmit power if the Power (dBm) or
fading margin is parameter values
insufficient but the associated with
transmit power can still power.
be increased.


Scenario Operation
Changing the When the original l Before using the

modulation modulation scheme new modulation
scheme of a does not meet the scheme, contact
microwave link service requirements, the network
you must use another planning
modulation scheme. department to
confirm that the
Hybrid
microwave 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
microwave link.
8.8.3 Common Task Collection (Ethernet Services)

This section describes the common configuration tasks associated with Native Ethernet services.
Table 8-135 Common task collection (Ethernet services)

Task Application Configuration Operation Remarks
Scenario
Creating an An Ethernet service A.7.3 Configuring Ethernet -

Ethernet must be created Services
service according to the service
plan.
Setting or If the service A.6.1 Setting Parameters for -

modifying the requirements or an Ethernet Port
parameters of configurations at the
Ethernet ports opposite end change,
the parameters of an
Ethernet port must be
changed.


Scenario
Deleting an Perform this operation A.7.3.13 Deleting an E-Line -

Ethernet if you want to delete the Service or A.7.3.14 Deleting
service Ethernet services that an E-LAN Service
will no longer be used
to release the occupied
resources.
Creating a l Perform this A.7.2.1 Creating a LAG l When

link operation when the creating a
aggregation available bandwidth LAG, set
group (LAG) is insufficient and the port that
you want to create a already
LAG to increase the carries
bandwidth. services to
l Perform this be the main
operation if you port.
want to improve l This
link reliability. operation
causes
transient
service
interruption
s.
Changing Perform this operation A.7.3.10 Changing Logical You must add
logical ports when the E-LAN Ports Mounted to a Bridge or delete the
mounted to an service requirements logical ports
Ethernet local change and the logical connected to
area network ports connected to the the E-LAN, or
(E-LAN) E-LAN must be modify
changed. attributes
associated with
the logical ports
connected to
the E-LAN
according to the
actual network
plan.


Scenario
Managing the l Create MAC A.7.4 Managing MAC -

MAC address address blacklist Address Tables
table entries when you
want to prevent
certain MAC
address hosts from
using E-LAN
services.
l Create static MAC
address entries
when you want to
prevent certain
MAC address
entries from being
aged.
l Set the aging
parameters of
corresponding
MAC addresses
when you want to
disable the aging
function or modify
the default aging
time (5 minutes).
Adjusting the Perform this operation A.7.6 Managing QoS Change the
quality of when the service values of QoS
service (QoS) requirements change parameters to
and the QoS must be adjust the QoS.
adjusted.

Commissioning and Configuration Guide A Task Collection
A Task Collection
This document describes tasks related to OptiX RTN 380.

A.1 U2000 Quick Start
This chapter describes basic operations on the U2000 client.
A.2 Web LCT Quick Start
This chapter describes basic operations on the Web LCT client.
A.3 Network Management
Network management involves topology management, communication management, and
security management.
A.4 Security Management
Security management is an important part of network management.
A.5 Managing Microwave Links
Before you configure a microwave link between two microwave sites, configure information
about the microwave link.
A.6 Managing Ports
Setting port parameters correctly is the basis for configuring ports to carry services.
A.7 Managing Ethernet Services and Features
Configurations of Ethernet services and features on the packet plane include Ethernet port,
protection, service, protocol, and OAM configurations.
A.8 Managing Clocks
To ensure clock synchronization between transmission nodes on a transport network, you need
to manage the NE clocks.
A.9 Using RMON
Remote network monitoring (RMON) monitors the data traffic on a network segment or an entire
network. Currently, RMON is one of the most widely used network management standards.
A.10 Configuring a Native Ethernet Service (in End-to-End Mode)
The U2000 allows Native Ethernet services to be configured in an end-to-end mode.
A.11 Verifying Services and Features
This chapter describes how to verify service and feature configurations.

A.1 U2000 Quick Start

This chapter describes basic operations on the U2000 client.
A.1.1 Logging In to a U2000 Client

The U2000 uses the client/server architecture and allows multiple clients. You can log in to the
U2000 server from a U2000 client to manage OptiX RTN NEs.
Prerequisites
l The U2000 system has been started on the U2000 server.
l The IP address of the U2000 client is in the access control list (ACL) configured in the
U2000 system.
l The U2000 client is communicating with the U2000 server properly.
Tools, Meter, and Materials

U2000
NOTE
Context
The following procedure helps you log in to the U2000 client.
Procedure
Step 1
----End
A.1.2 Shutting Down a U2000 Client

Shut down a U2000 client when it will not to be used.

Prerequisites

U2000
NOTE
Context
The following procedure shuts down a U2000 client.
Procedure
Step 1
----End
A.1.3 Using the Help

The Help provides help information about the U2000.
Prerequisites

U2000
NOTE
Context
The following procedure helps you use the iManager U2000 Help.

Procedure
Step 1
----End
A.1.4 Navigating to Common Views

This section describes how to navigate to the common views of the U2000 and the functions of
the views.
A.1.4.1 Navigating to Main Topology

The U2000 provides the Main Topology view for network topology management.
Prerequisites

U2000
NOTE
Context
The following procedure navigates to Main Topology.
Procedure
Step 1

----End
A.1.4.2 Navigating to NE Explorer

The U2000 provides the NE Explorer view for equipment management. The NE Explorer view
consists of the function tree pane, object tree pane, and configuration pane.
Prerequisites

U2000
NOTE
Context
The following procedure navigates to NE Explorer.
Procedure
Step 1

----End
A.1.4.3 Navigating to the NE Panel

NE Panel displays the boards configured on an NE. Different colors represent different board
status.
Prerequisites

U2000
NOTE
Context
The following procedure navigates to NE Panel.
Procedure
Step 1

----End
A.2 Web LCT Quick Start

This chapter describes basic operations on the Web LCT client.
A.2.1 Connecting the Web LCT to the Equipment

Prerequisites
NOTE
link.

Web LCT
Procedure
255.255.0.0).

configuration. For details, see Figure A-1.
CAUTION
Figure A-1 Ways for connecting the Web LCT to an OptiX RTN 380
P&E P&E
P&E USB/RSSI/NMS
NMS/COM
MGMT P&E
4/P2
NMS
Fiber
To NodeB
MGMT
P&E
EG4P
NOTE
the laptop.

l User Name: admin
NOTE
----End
Follow-up Procedure

A.2.2 Using the Help

The Help provides help information about the Web LCT.
Prerequisites

Web LCT
NOTE
Context
The following procedure obtains help information related to the Web LCT.
Procedure
Step 1

----End
A.2.3 Navigating to NE Explorer

The U2000 provides the NE Explorer view for equipment management. The NE Explorer view
consists of the function tree pane, object tree pane, and configuration pane.
Prerequisites

Web LCT
NOTE
Context
The following procedure helps you navigates to NE Explorer by clicking NE Explorer.
Procedure
Step 1

----End
A.3 Network Management

Network management involves topology management, communication management, and
security management.
A.3.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the network management
system (NMS).
A.3.1.1 Creating an NE 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 network segment of the gateway NE IP address, 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 search method creates NEs faster and more reliably.
Prerequisites
l The network management system (NMS) is communicating with NEs properly.

U2000
NOTE
This task can also be performed on the Web LCT, but the steps are different from those on the U2000.
Context
l Creates an NE by using the search method.

l Creates an NE by using the NE Search method (only on the Web LCT) if the NE is the
gateway NE and belongs to the same network segment as the NMS server.
Procedure
Step 1 Create an NE by using the search method.
Step 2 Create an NE by using the NE Search method (only on Web LCT).

----End
A.3.1.2 Creating an NE Manually

If you create NEs manually, you can create them one by one instead of in batches.
Prerequisites
l The network management system (NMS) is properly communicating with the NE to be
created.
l If the NE to be created is a non-gateway NE, the corresponding gateway NE has been
created.

U2000
NOTE
Context
The following procedure creates NE(9-16947) manually.
Procedure
Step 1

----End
A.3.1.3 Logging In to an NE
After an NE is created, log in to the NE before you can manage it.
Prerequisites
l The NE to be managed has been created in NE List.

Web LCT
NOTE
Context
The following procedure helps you log in to an NE.
Procedure
Step 1

----End
A.3.1.4 Changing an NE ID
Change the NE ID according to the engineering plan to ensure that each NE ID is unique. This
task does not interrupt services.
Prerequisites

U2000
NOTE
Context
The following procedure changes an NE ID to the planned value listed in the following table.
Parameter Value
New ID 320
After changing the NE ID, you need to restart the NE.
Procedure
Step 1

----End
A.3.1.5 Changing an NE Name

For easier identification of an NE in Main Topology, name the NE according to its geographical
location or the device to which it is connected.
Prerequisites

U2000
NOTE
Context
The following procedure changes an NE name to the planned value listed in the following table.
Parameter Value
Name Site2-1
Procedure
Step 1

----End
A.3.1.6 Synchronizing the NE Time

By configuring the NE time to be synchronous with the time on the network management system
(NMS) or standard Network Time Protocol (NTP) server, you can record the exact time when
an alarm and abnormal event occurs.
Prerequisites
l The time zone and time have been set correctly on the PC or server running the NMS
software.
l The time on the NTP server has been set correctly. The NTP protocol is running normally.

U2000
NOTE
Context
l Synchronizes the NE time with the NMS time according to the planned parameter values
listed in the following table
Table A-1 Parameters for NE time synchronization

Parameter Value
Synchronous Mode NM
l Synchronizes the NE time with the NTP server time according to the planned parameter
values listed in the following tables.

Table A-2 Parameters for NE time synchronization

Parameter Value
Synchronous Mode Standard NTP
Standard NTP Authentication Disabled
Table A-3 Parameters for the standard NTP server

Parameter Value
Standard NTP Server Flag NE ID
Standard NTP Server 9-16
Standard NTP Server Key 0
Procedure
Step 1 Synchronize the NE time with the NMS time.
Step 2 Synchronize the NE time with the NTP server time.

----End
A.3.1.7 Localizing the NE Time

If daylight saving time (DST) is used in the area where an NE is located, localize the NE time
to synchronize it with the local time.
Prerequisites

U2000
NOTE
Context
The following procedure synchronizes the NE time with the local time according to the planned
parameter values listed in the following table.
Parameter Value
Time Zone (U2000) (UTC+01:00)-Central European Time

(Europe/Berlin)
Time Zone (Web LCT) (GMT+08:00)-China Standard Time(PRC)
DST Selected
Start Rule Week
End Rule Week

Procedure
Step 1 Localize the NE time (U2000).
Step 2 Localize the NE time (Web LCT).
----End
A.3.1.8 Configuring a Standard NTP Key
Prerequisites
l Synchronous Mode is set to Standard NTP, and Standard NTP Authentication is set
to Enabled.
l The Network Time Protocol (NTP) is running properly. The NTP identity authentication
has been enabled on the NTP server.

U2000

NOTE
Context
The following procedure configures a standard NTP key according to the planned parameter
values listed in the following table.
Parameter Value
Key ID 123
Password test1234
Trusted Yes
Procedure
Step 1
----End
A.3.2 Configuring NE Data

After an NE is created, configure NE data so that the network management system (NMS) can
manage this NE.
A.3.2.1 Uploading NE Data

Uploading NE data is commonly used for configuring NE data. By performing this task, you
can upload NE data, such as configuration, alarm, and performance data, to the network
management system (NMS).
Prerequisites
l You have logged in to the NE.


U2000
NOTE
Context
l Uploads NE data when the NE has not been configured.
l Uploads NE data when the NE has been configured.
Procedure
Step 1 Upload NE data when the NE has not been configured.
Step 2 Upload NE data when the NE has been configured.
----End

A.3.2.2 Synchronizing NE Data

Synchronizing NE data is uploading the NE-side data that is different from the NMS-side data,
including conflicting data and absent data, to the network management system (NMS).
Prerequisites
l An NE has been created.
l The NE is in unsynchronized state.
NOTE
An NE in unsynchronized state is marked with .

U2000
NOTE
Context
The following procedure synchronizes NE data.
Procedure
Step 1
----End
A.3.3 Setting the Performance Monitoring Status for an NE

By performing this task, you can manually enable or disable performance monitoring for NEs,
or set the performance monitoring period.
Prerequisites


U2000
NOTE
Context
The following procedure enables the 15-minute performance monitoring function and the 24-
hour performance monitoring function for an NE.
Procedure
Step 1
----End
A.3.4 Creating a Fiber/Cable

To implement end-to-end service management on the network management system (NMS), you
must create fibers or cables first.
A.3.4.1 Creating a Fiber/Cable by Using the Search Method

The network management system (NMS) can find the fibers connected to a specified microwave
port or Ethernet port by using the search method. This method is the most common method for
creating microwave links.
Prerequisites

U2000

NOTE
Context
The following procedure creates a microwave link or an Ethernet link on the RTN subnet using
the search method.
Procedure
Step 1 Create a microwave link on the RTN subnet using the search method.
Step 2 Create an Ethernet link on the RTN subnet using the search method.
----End
A.3.4.2 Creating a Fiber/Cable Manually

You can create a fiber by specifying the ports connected by the fiber. This method can be used
to create both microwave links and Ethernet links.

Prerequisites

U2000
NOTE
Context
The following procedure creates a fiber manually according to the planned parameter values
Parameter Value
Fiber/Cable Type Radio Link
Name l-1
Source NE NE16938
Source NE Subrack-Slot-Board Type-Port 1-SHUF3-1(IF)
Sink NE NE(129–16937)
Sink NE Subrack-Slot-Board Type-Port 1-SHUF3-1(IF)
Automatically Allocate IP Address No
Procedure
Step 1
----End

A.3.4.3 Creating an Extended ECC Connection

Extended embedded control channel (ECC) connections indicate that inter-NE data
communication network (DCN) communication is implemented using cascaded network
management system (NMS) ports.
Prerequisites

U2000
NOTE
Context
The following procedure creates an extended ECC connection according to the planned
Parameter Value
Name Extended ECC-1
Source NE NE16938
Sink NE NE(129–16937)
Procedure
Step 1
----End

A.3.4.4 Creating a Back-to-back Radio Connection

Back-to-back radio connections indicate the stacking of multiple OptiX RTN NEs at the same
site.
Prerequisites

U2000
NOTE
Context
The following procedure creates a back-to-back radio connection according to the planned
Parameter Value
Name b-1
Source NE NE(9–16943)
Sink NE NE16938
Procedure
Step 1
----End

A.3.5 Managing Subnets

To facilitate NE management, you can allocate the NEs that are in the same domain or that have
similar attributes to the same subnet.
A.3.5.1 Creating a Subnet

In Main Topology, you can create a subnet object and allocate an NE to this subnet.
Prerequisites

U2000
NOTE
Context
The following procedure creates a subnet named RTN.
Procedure
Step 1
----End
A.3.5.2 Copying a Topology Object

In the current topology, you can copy topology objects from one subnet to another subnet.
Prerequisites


U2000
NOTE
Context
The following procedure copies NE16938 to the RTN subnet.
Procedure
Step 1
----End
A.3.5.3 Moving a Topology Object

In the current topology, you can move topology objects from one subnet to another subnet.
Prerequisites

U2000
NOTE
Context
The following procedure moves NE16938 to the RTN subnet.

Procedure
Step 1
----End
A.3.6 Managing Communication

To manage NEs using the network management system (NMS), ensure that the data
communication network (DCN) communication between the NEs and NMS is normal.
A.3.6.1 Setting NE Communication Parameters

NE communication parameters include the NE IP address, gateway IP address, and subnet mask.
Prerequisites

U2000
NOTE
Precautions
If multiple parameters need to be set, click Apply after setting each parameter.
Context
The following procedure sets the IP address and subnet mask of an NE to the planned values
Parameter Value

Parameter Value
Procedure
Step 1
----End
A.3.6.2 Configuring DCCs

To meet the requirements for managing a complex network, you must set the channel type,
protocol type, and status of data communications channels (DCCs) according to the network
plan.
Prerequisites

U2000
NOTE
Context
The following procedure changes the DCC protocol to Huawei embedded control channel
(HWECC).
Parameter Value
Enabled/Disabled Enabled (default value)

Parameter Value
Protocol Type HWECC
Procedure
Step 1
----End
A.3.6.3 Setting the VLAN ID and Bandwidth for an Inband DCN

The VLAN ID used by an inband data communication network (DCN) must be different from
the VLAN ID used by services. The bandwidth of an inband DCN must meet the requirements
of the transmission network for managing messages.
Prerequisites

U2000
NOTE
Context
The following procedure sets the VLAN ID and bandwidth to the planned values listed in the
following table for an inband DCN.
Parameter Value
VLAN ID 4092

Parameter Value
Bandwidth(Kbit/s) 512Kbit/s
Procedure
Step 1
----End
A.3.6.4 Configuring the Priorities of Inband DCN Packets

By performing this task, you can set the VLAN priorities and differentiated services code point
(DSCP) values carried by inband data communication network (DCN) packets.
Prerequisites

U2000
NOTE
Context
The following procedure sets the VLAN priority and DSCP value carried by inband DCN packets
to the planned values listed in the following table.
Packet Type Priority
VLAN EF
DSCP BE (default value)

Procedure
Step 1
----End
A.3.6.5 Setting a Port for an Inband DCN

By performing this task, you can set the inband data communication network (DCN) status and
inband DCN protocol stack type for an inband DCN port.
Prerequisites

U2000
NOTE
Context
l Sets the inband DCN protocol stack to the Huawei embedded control channel (HWECC)
protocol stack for three Ethernet ports.
Parameter GE1 GE2 GE3
Enabled Status Enabled (default Enabled (default Enabled (default

value) value) value)
Protocol Type HWECC HWECC HWECC

l Disables the inband DCN function of a microwave port.

Parameter IF
Enabled Status Disabled
Procedure
Step 1 Change the inband DCN protocol stack for an Ethernet port.
Step 2 Change the inband DCN status for a microwave port.
----End
A.3.6.6 Configuring Access Control

When an NE is connected to the network management system (NMS) using an Ethernet service
port, you must configure access control.
Prerequisites


U2000
NOTE
Context
The following procedure configures the access control function for the port GE1 according to
the planned parameter values listed in the following table.
Parameter Value
Enabled Status Enabled (default value)
Procedure
Step 1
----End
A.3.6.7 Configuring Extended ECCs

Two extended embedded control channel (ECC) modes are available: auto and manual.
Prerequisites
Tools, Instruments and Materials

U2000

NOTE
Precautions
The default extended ECC mode is Auto mode.
Context
l Disables the extended ECC function in auto mode.

l Enables the manual extended ECC function and configures an NE as the server, according
to the planned parameter values listed in the following table.
Parameter Value
Port 1602
l Enables the manual extended ECC function and configures an NE as the client, according
Parameter Value
Opposite IP 129.9.0.1
Port 1602
Procedure
Step 1 Disable the extended ECC function in auto mode.
Step 2 Enable the manual extended ECC function and configure an NE as the server.

Step 3 Enable the manual extended ECC function and configure an NE as the client.
----End
A.3.6.8 Creating a Static IP Route

When dynamic routes fail to meet planning requirements, you must create static IP routes
manually.
Prerequisites

U2000
NOTE

Context
The following procedure creates a static IP route according to the planned parameter values
Parameter Value
Destination Address 129.9.0.7
Subnet Mask 255.255.255.255
Gateway 129.0.0.1
Procedure
Step 1
----End
A.3.6.9 Setting OSPF Protocol Parameters

When the OptiX RTN equipment is interconnected with third-party equipment, routing protocol
interaction works properly after you set Open Shortest Path First (OSPF) protocol parameters
of the OptiX RTN equipment based on related requirements of the third-party equipment.
Prerequisites

U2000
NOTE

Context
The following procedure configures OSPF parameters according to the planned parameter values
Parameter Value
Area 0.0.0.1
OSPF Status Enabled
Static route Enabled
LAN Interface Disabled
Procedure
Step 1
----End
A.3.6.10 Creating an OSPF Area

If an NE functions as an area border router (ABR), you must create the non-backbone area to
which the ABR belongs.
Prerequisites

U2000
NOTE

Context
The following procedure creates an Open Shortest Path First (OSPF) area according to the
planned parameter values listed in the following table.
Parameter Value
ID 0.0.0.1
Authentication Type none
Automatic Route Aggregation Enabled
Stub Type NON-STUB
Procedure
Step 1
----End
A.3.6.11 Configuring the Network Information of an ABR

By performing this task, you can add or modify the network information of an area border router
(ABR).
Prerequisites

U2000

NOTE
Context
l Modifies the network information about the backbone Open Shortest Path First (OSPF)
area according to the planned parameter values listed in the following table.
Parameter Value
l Adds the network information about a non-backbone OSPF area according to the planned
Parameter Value
Procedure
Step 1 Modify the network information about the backbone OSPF area.
Step 2 Add the network information about a non-backbone OSPF area.

----End
A.3.6.12 Creating a Manual Route Aggregation Group

An NE supports a maximum of eight manual route aggregation groups.
Prerequisites

U2000
NOTE
Context
The following procedure creates a manual route aggregation group according to the planned
Parameter Value
Procedure
Step 1

----End
A.3.6.13 Configuring Port IP Addresses for an ABR

If a port on an area border router (ABR) does not belong to the backbone area, you must configure
an IP address for this port.
Prerequisites

U2000
NOTE
Context
l Sets a port IP address for the data communications channel (DCC) at a microwave port.
Parameter Value
Protocol Type IP (default value)
l Sets a port IP address for the inband data communication network (DCN) channel at the
Ethernet port GE1.

Parameter Value
Protocol Type IP (default value)
Procedure
Step 1 Set a port IP address for the DCC channel at a microwave port.
Step 2 Set a port IP address for the inband DCN channel at the Ethernet port GE1.
----End

A.3.6.14 Configuring the OSPF Authentication Type

By performing this task, you can configure the authentication type for an OSPF area and also
configure authentication passwords for different port types when different authentication types
are used.
Prerequisites

U2000
NOTE
Context
l Changes the authentication type for area 0.0.0.1.
Table A-4 Authentication Type

Parameter Value
Authentication Type MD5
l Sets the passwords used for a data communication network (DCN) port when different
Open Shortest Path First (OSPF) authentication types are used.
Table A-5 Authentication Password

Port Type Authentication Authentication MD5 Key
Type Password
LAN MD5 abc123 16
DCC none (default value) - -
Procedure
Step 1 Change the authentication type for an area.

Step 2 Set the passwords used for a DCN port when different OSPF authentication types are used.
----End
A.3.6.15 Enabling the Proxy ARP

The proxy Address Resolution Protocol (ARP) enables NEs in the same network segment but
different domains to communicate with one another.
Prerequisites

U2000
NOTE

Context
The following procedure enables the proxy ARP function for NE1 (gateway NE) shown in the
following figure. By performing this operation, the network management system (NMS) gains
direct access to NE2.
ARP proxy enabled
NE 1 NE 2
Third-party NMS
129.9.0.100 129.9.0.2
129.9.0.1
Ethernet link Radio link
Procedure
Step 1
----End
A.3.6.16 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used
The RSTP protocol improves stability of an L2 DCN.
Prerequisites

U2000

NOTE
Context
The following procedure enables the RSTP protocol when the L2 DCN solution is used.
Procedure
Step 1
----End
A.3.6.17 Querying ECC Routes

By querying embedded control channel (ECC) routes, you can check whether the HWECC
solution is correctly configured and whether NEs properly communicate with one another.
Prerequisites

U2000
NOTE
Context
The following procedure checks whether the NE ECC routes and parameters are properly
planned.
Procedure
Step 1

----End
A.3.6.18 Querying IP Routes

By querying IP routes, you can check whether the IP data communication network (DCN)
solution and inband DCN solution are configured correctly and whether NEs properly
communicate with one another.
Prerequisites

U2000
NOTE
Context
The following procedure checks whether the NE IP routes and parameters are properly planned.
Procedure
Step 1

----End
A.3.6.19 Verifying Connectivity of an ECC Network

You can use the ping or traceroute function to verify the data communication network (DCN)
connectivity between two NEs on an embedded control channel (ECC) network.
Prerequisites

U2000
NOTE
Context
l Checks the DCN connectivity between two NEs on an ECC network by using the ping
function.
l Checks the DCN connectivity between two NEs on an ECC network by using the traceroute
function.
Procedure
Step 1 Check the DCN connectivity by using the ping function.

Step 2 Check the DCN connectivity by using the traceroute function.
----End
A.3.6.20 Verifying Connectivity of an IP DCN Network

You can use the ping or traceroute function to verify the data communication network (DCN)
connectivity between two NEs on an IP DCN network.
Prerequisites

U2000
NOTE
Context

l Checks the DCN connectivity between two NEs on an IP DCN network by using the ping
function.
l Checks the DCN connectivity between two NEs on an IP DCN network by using the
traceroute function.
Procedure
Step 1 Check the DCN connectivity by using the ping function.
Step 2 Check the DCN connectivity by using the traceroute function.
----End
A.3.6.21 Setting SNMP Communication Parameters

By performing this task, you can configure the Simple Network Management Protocol (SNMP)
parameters for an NE that functions as an SNMP agent. This SNMP agent uses these parameters
to communicate with the SNMP server.
Prerequisites


U2000
NOTE
Precautions
The SNMP version, read/write permissions, and community name planned for an OptiX RTN
380 must be the same as those for the SNMP server.
Context
The following procedure configures the SNMP server to directly query alarms and performance
events on all NEs.
NE 1 NE 8
NE 2
NE 7
IP DCN
NE 3
External DCN
NE 6 (GNE)
NE 4 NE 5 SNMP server
IP address: 10.10.10.3
Based on the SNMP server information, the SNMP parameters planned for all NEs are listed in
Table A-6 SNMP plan
Parameter All NEs
IP address of the SNMP server 10.10.10.3
Read/Write permissions Reading and writing
Read community name Read_01
Write community name Write_01
Trap version SNMP V2C
Report MW performance Trap Report
Report IP performance Trap Report
Report Alarm Trap Report
Port 162

Procedure
Step 1
----End
A.3.6.22 Configuring the Active and Standby Gateway NEs

By performing this task, you can configure the active and standby gateway NEs on a data
communication network (DCN) to improve network reliability.
Prerequisites

U2000
NOTE
Context
The following procedure configures the standby gateway NE for NE(129-16937) according to
the planned parameter value listed in the following table.
Parameter Value
Standby gateway NE NE16938
Procedure
Step 1

----End
A.3.7 Configuring the NMS Port on an NE

By default, an NE can connect to the network management system (NMS) or another NE through
its NMS port. The NMS port works in auto-negotiation mode.
Prerequisites

U2000
NOTE
Precautions
l It is recommended that the Web LCT access an NE through an Ethernet port
l If you need to initialize an NE or download software by using the LCT, the LCT must
access the NE through an Ethernet port.
Context
The following procedure sets the working mode for an Ethernet port according to the planned
Parameter Value
Work Mode 100M Full-Duplex
Enable Ethernet Access Enabled

Procedure
Step 1
----End
A.4 Security Management

Security management is an important part of network management.
A.4.1 Configuring an NE User

NE users refer to the users who log in to and operate NEs. Different types of NE users are
assigned different rights to log in to and manage NEs.
A.4.1.1 Creating an NE User

NE users are divided into five levels in ascending order of operation rights: monitor level,
operation level, maintenance level, system level, and debug level. Different levels of NE users
can be created as required.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l You must be an NM user with a higher level than the user to be created.

U2000
NOTE
Precautions
l The default NE user is at the monitor level.

l For security of NE data, it is recommended to assign operations rights to NE users based

on their responsibilities.
Context
The following procedure creates an NE user according to the planned parameter values listed in
Parameter Value
NE User user1
User Level Monitor Level (default value)
Procedure
Step 1
----End
A.4.1.2 Changing the Password of an NE User

Periodically changing the password of an NE user ensures the NE security.
Prerequisites
l An NE user has been created.
l You must be an NM user with a higher level than the user whose password is to be changed.

U2000
NOTE

Precautions
Periodically change the password of an NE user to ensure NE security.
Context
The following steps change the password of user1.
Procedure
Step 1
----End
A.4.1.3 Setting the Warning Screen Parameters

By performing this task, you can enable the warning screen function. With this function enabled,
the network management system (NMS) displays some information to a user when the user logs
in to an NE. The displayed information can be defined by carriers.
Prerequisites
You must be an NM user with NE maintainer authority or higher.

U2000
NOTE
Context
The following procedure enables the warning screen function. After you log in to an NE, the
NMS displays the message "The NE is online."

Procedure
Step 1
----End
A.4.1.4 Switching NE Users

By performing this task, you can switch an NE user to a higher-level NE user when the operations
on the network management system (NMS) are beyond the operation rights of the NE user.
Prerequisites
l An NE user has been created.

U2000
NOTE
Precautions
An NE user cannot log in to and manage an NE from different servers at the same time. If an
NE user logs in to an NE from two servers at different time, the first logged-in user is forcibly
logged out.
Context
The following procedure switches an NE user according to the planned parameter value listed
in the following table.
Parameter Value
NE user to be switched user1

Procedure
Step 1
----End
A.4.2 Enabling/Disabling USB Flash Drive Access

By default, a USB flash drive can access an NE. You can perform this task to disable or enable
the access according to actual requirements.
Prerequisites

U2000
NOTE
Context
The following procedure disables USB flash drive access.
Procedure
Step 1

----End
A.4.3 Configuring Web LCT Access to an NE

When an NE is managed by the network management system (NMS), the Web LCT can access
this NE by default.
Prerequisites

U2000
NOTE
Precautions
l If the Web 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 Web LCT according to LCT Access Control
Switch.
l If the Web LCT requests to log in to an NE to which the NMS has not logged in, the NE
permits the login of the Web LCT regardless of LCT Access Control Switch. After the
Web LCT logs in, the NMS can also log in to the NE. After the NMS user logs in to the
NE successfully, the logged-in Web LCT user is not affected even if LCT Access Control
Switch is set to Disable Access.
Context
The following procedure disables Web LCT access.
Procedure
Step 1

----End
A.4.4 Configuring an Access Control List for an NE

This chapter describes how to configure an access control list (ACL) for an NE to filter IP packets
attempting to access the NE.
A.4.4.1 Creating Basic ACL Rules

This section describes how to create basic access control list (ACL) rules for an NE. Based on
the basic ACL rules, IP packets attempting to access the NE can be filtered by source address.
Prerequisites

U2000
NOTE
Context
The following procedure sets a basic ACL rule which allows IP packets with the source IP
addresses in the network segment 129.9.0.0/16 to traverse the NE.
Procedure
Step 1

----End
A.4.4.2 Creating Advanced ACL Rules

This section describes how to create advanced access control list (ACL) rules for an NE. Based
on the advanced ACL rules, IP packets attempting to access the NE can be filtered by source/
sink address, source/sink port, and protocol type.
Prerequisites

U2000
NOTE
Context
The following procedure sets an ACL rule which forbids TCP packets with the sink port number
23 to traverse the NE.
Procedure
Step 1

----End
A.4.5 Querying NE Operation Logs

This section describes how to query operation logs of an NE.
Prerequisites

U2000
NOTE
Context
The followings steps allow you to browse the operation logs of user szhw.
Procedure
Step 1

----End
A.4.6 Querying NE Security Logs

This section describes how to query NE security logs.
Prerequisites
You must be an NM user with NE monitor authority or higher.

U2000
NOTE
Procedure
Step 1
----End

A.4.7 Configuring Syslog

This chapter describes how to configure Syslog if Syslog servers are used to collect logs of all
NEs on a network.
A.4.7.1 Enabling the Syslog Service

This section describes how to enable the Syslog service if an NE is required to forward its logs
to Syslog servers.
Prerequisites

U2000
NOTE
Context
The following procedure enables Syslog services for an NE.
Procedure
Step 1
----End
A.4.7.2 Setting Types and Severities of Logs to Be Sent to Syslog Servers

This section describes how to set types and severities of logs to be sent to Syslog servers.

Prerequisites

U2000
NOTE
Context
The following procedure adds a type of logs to be transferred to the Syslog server. The following
table provides the log type and severity.
Parameters Value
Log Type security/authorization messages
Log Severity Debug
NOTE
By default, the NE forwards security/authentication messages of all severities to the Syslog server.
Procedure
Step 1
----End
A.4.7.3 Configuring Syslog Servers

This section describes how to set Syslog server-related parameters on NEs that transmit logs to
Syslog servers.

Prerequisites

U2000
NOTE
Context
The following procedure configures a Syslog server. The following table provides information
about logs received by the server.
Parameters Value
IP Address 129.9.100.200
Send Mode UDP
Port 514
Procedure
Step 1
----End
A.4.7.4 Configuring Gateway NEs for Communication Between NEs and Syslog
Servers
If no IP routes are available between an NE and its Syslog servers, configure a gateway NE to
forward the NE's logs to the Syslog servers. Ensure that IP routes are available between the
gateway NE and the Syslog servers, and the data communication network (DCN) communication
between the NE and the gateway NE is normal.

Prerequisites

U2000
NOTE
Context
The following procedure sets NE(9-16938) as the gateway NE for forwarding logs to the Syslog
server.
Procedure
Step 1
----End
A.4.8 Configuring File Transfer Protocols

This section describes how to configure file transfer protocols that are used when the network
management system (NMS) loads software to NEs. The File Transfer Protocol (FTP) or Secure
File Transfer Protocol (SFTP) is used by default when the NMS loads software to NEs.
Prerequisites
You must be an NM user with NE maintainer authority or higher.

U2000
NOTE

Context
The following procedure prevents the NMS from loading software to NE(9-16838) using the
FTP.
Procedure
Step 1
----End
A.4.9 Configuring SSL Protocol Communication

The security socket layer (SSL) protocol provides encrypted and reliable communication
between entities, improving the network management security.
A.4.9.1 Configuring SSL Protocol Communication Between a U2000 Server and Its
Clients
Secure Sockets Layer (SSL) protocol communication between a U2000 server and its clients is
supported only after corresponding configurations are performed on the U2000 server and
clients.
Prerequisites
The connection mode of the U2000 server is set to SSL.

U2000
NOTE

Precautions
l Two connection modes are supported, which are Common and Security(SSL). You can
query the connection mode on the U2000 server by running a query command.
l The default connection mode is Common.
NOTE
l When the U2000 server and its client are deployed on the same host and the U2000 server uses the
SSL connection mode, the client can log in to the server by using the common or SSL connection
mode. When the U2000 server and its client are deployed on the same host and the U2000 server uses
the common connection mode, the client can log in to the server only by using the common connection
mode.
l When the U2000 server and its client are deployed on different hosts, the client can log in to the U2000
server only by using the same connection mode as the U2000 server.
Context
The following procedure sets the connection mode to Security (SSL) for a client.
Procedure
Step 1
----End
A.4.9.2 Configuring the Connection Mode Between the U2000 and Its Gateway NE
Two connection modes are supported between the U2000 and its gateway NE: common
connection mode and Secure Sockets Layer (SSL) connection mode.
Prerequisites
l SSL licenses have been deployed on the gateway NE and the U2000 according to the SSL
loading guide.

U2000

NOTE
Context
The following procedure configures NE(129–16937), the gateway NE, to communicate with the
U2000 by using only the SSL protocol.
Procedure
Step 1 Configure the connection mode of the U2000.
Step 2 Configure the connection mode of the gateway NE.
----End
A.4.10 Configuring RADIUS Authentication

The Remote Authentication Dial In User Service (RADIUS) authentication function allows a
RADIUS server to implement centralized management over all users that log in to an NE.

A.4.10.1 Enabling/Disabling the RADIUS Authentication Function

An NE can use the Remote Authentication Dial In User Service (RADIUS) authentication
function only after the RADIUS client function is enabled on the NE. An NE can function as a
proxy server only after the proxy server function is enabled on the NE.
Prerequisites

U2000
NOTE
Context
The following procedure configures the local NE as the gateway NE, enables the RADIUS
authentication function, and configures the local NE as the proxy server.
Procedure
Step 1
----End
A.4.10.2 Creating a RADIUS Server or a RADIUS Proxy Server

A Remote Authentication Dial In User Service (RADIUS) server needs to be configured if an
NE uses RADIUS authentication in network access server (NAS) mode or functions as a proxy
server. A RADIUS proxy server needs to be configured if an NE uses RADIUS authentication
in proxy NAS mode.

Prerequisites
l The RADIUS authentication function has been enabled for an NE.

U2000
NOTE
Context
l Configures the RADIUS server according to the planned parameter values listed in the
following table, when the NE performs security authentication in NAS mode or functions
as a proxy server.
Parameter Value
Function Authentication
Server Type Radius Server
Server ID IP Address: 10.10.10.1
l Configures the proxy server according to the planned parameter values listed in the
following table, when the NE performs security authentication in proxy NAS mode.
Parameter Value
Server Type Proxy Server
Server ID NE ID: NE(129–16937)
Procedure
Step 1 Configure information about the RADIUS server.

Step 2 Configure information about the RADIUS proxy server.
----End
A.4.10.3 Configuring RADIUS Server Parameters

This section describes how to configure Remote Authentication Dial In User Service (RADIUS)
server parameters.
Prerequisites
l The RADIUS server or RADIUS proxy server has been configured for an NE.
l The RADIUS authentication function has been enabled for the NE.

U2000
NOTE

Context
l Configures RADIUS server parameters according to the planned parameter values listed
in the following table, when the NE performs security authentication in network access
server (NAS) mode.
Parameter Value
Server Type Radius Server
Server ID IP Address: 10.10.10.1
Server Status Active
Shared Key Abcd1234
Interval of Packet Transmission 5 (default)
Packet Retransmission Attempts 3 (default)
l Configures RADIUS server parameters according to the planned parameter values listed
in the following table, when the NE performs security authentication in proxy NAS mode.
Parameter Value
Server Type Proxy Server
Server ID NE ID: NE(9–2327)
Server Status Active
Interval of Packet Transmission 5 (default)
Packet Retransmission Attempts 3 (default)
Procedure
Step 1 Configure RADIUS server parameters when the NE performs security authentication in NAS
mode.

Step 2 Configure RADIUS server parameters when the NE performs security authentication in proxy
NAS mode.
----End
A.5 Managing Microwave Links

Before you configure a microwave link between two microwave sites, configure information
about the microwave link.
A.5.1 Configuring a Single Hop of Microwave Link

By performing this task, you can set the basic attributes for the local NE and the peer NE on a
single hop of microwave link.
Prerequisites
l The sites at the two ends of a microwave link hop are communicating properly.


U2000
NOTE
Precautions
The following parameters of the NEs on a hop of microwave link are automatically synchronized:
Link ID, IF Channel Bandwidth, , AMAC, Guaranteed AMAC Capacity, Full AMAC
Capacity, Modulation Mode, T/R Spacing(MHz), and ATPC. That is, if one of the preceding
parameters is modified on an NE, the modification is automatically duplicated on the peer NE.
Context
The following procedure configures basic information for the hop of microwave link shown in
the following figure by configuring NE1.
The planned parameter values are listed in the following table.
Parameter Link
NE ID 9-38412(Local Radio Terminal)

9-20038(Opposite Radio Terminal)
Link ID 2
IF Channel Bandwidth 250MHz
AMAC Disabled
Modulation Mode 16QAM
TX Frequency(MHz) 73500
ATPC Disabled
TX power (dBm) 10
Power to Be Frequency(dBm) -40
TX Status unmute
Antenna Polarization Direction V
Procedure
Step 1

----End
A.5.2 Browsing the Performance of a Hop of Microwave Link

This section describes how to query performance information about a microwave link hop.
Prerequisites

U2000
NOTE
Context
The following procedure queries performance information about a microwave link hop.
Procedure
Step 1 Browsing the Performance of a Hop of Microwave Link (U2000)

Step 2 Browsing the Performance of a Hop of Microwave Link (Web LCT)
----End
A.5.3 Creating a Microwave 1+1 Protection Group

If microwave links are configured with 1+1 hot standby (HSB) protection, you need to create a
corresponding microwave 1+1 protection group.
Prerequisites
l If no optical splitter is used when 1+1 HSB is configured, E-LAG needs to be configured.
l The COMBO ports on the active and standby OptiX RTN 380s are connected using an
optical fiber.

U2000

Context
The following procedure
l creates a microwave 1+1 protection group in LAG Mode according to planned values
Parameter Value
l creates a microwave 1+1 protection group in Split Mode according to planned values
Parameter Value
Procedure
Step 1 Create a microwave 1+1 protection group in LAG Mode.

Step 2 Create a microwave 1+1 protection group in Split Mode.
----End
A.5.4 Microwave 1+1 Protection Switching

You can perform external switching on the microwave 1+1 protection by performing microwave
1+1 protection switching.
Prerequisites
l Microwave 1+1 protection has been configured.

U2000
NOTE

Context
The following procedure performs external switching on a microwave 1+1 protection group
according to the planned parameter values listed in the following table.
Parameter Value
Working Mode HSB
Unit Working Board
Switching Conditions Force Switching to Protection Port
Procedure
Step 1
----End
A.5.5 Querying the Microwave 1+1 Protection Status

You can learn about the current information about the microwave 1+1 protection by querying
the microwave 1+1 protection status.
Prerequisites
l Microwave 1+1 protection has been configured.

U2000
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.

Context
The following procedure queries the status information about a 1+1 space diversity (HSB)
protection group.
Procedure
Step 1
----End
A.5.6 Configuring Ethernet Frame Header Compression

You can configure the Ethernet header compression function by setting microwave port
parameters.
Prerequisites

U2000
NOTE
Context
The following procedure configures a microwave port according to the planned parameter values
Parameter Value
1-SHUF3-1 (IF)
Speed Transmission at L2 Enabled

Parameter Value
1-SHUF3-1 (IF)
Speed Transmission at L3 Enabled
NOTE
If the Ethernet header compression function is enabled, set the preceding two parameters to Enabled to compress
Layer 2 headers and IP headers.
Procedure
Step 1
----End
A.5.7 Setting the Maximum Transmit Power and the Power

Thresholds
This section describes how to set the maximum transmit power and the power thresholds.
Prerequisites

U2000
Context
The following procedure sets the maximum transmit power to the planned value listed in the
following table for an NE.
NOTE
The method for setting power thresholds is the same as that for setting the maximum transmit power.

Parameter Value
Maximum Transmit Power 10 dBm
Procedure
Step 1
----End
A.5.8 Querying the AM Status

This section describes how to query the adaptive modulation (AM) scheme changes and the
Ethernet bandwidth in the current modulation scheme.
Prerequisites

U2000
Context
The following procedure queries the AM scheme and the Ethernet bandwidth in the current
modulation scheme.
Procedure
Step 1

----End
A.5.9 Querying ATPC Adjustment Records

This section describes how to query automatic transmit power control (ATPC) adjustment
records.
Prerequisites

U2000
NOTE
Context
The following procedure queries ATPC adjustment records.
Procedure
Step 1

----End
A.5.10 Querying Historical Transmit Power and Receive Power

This section describes how to query the change trend of historical transmit power and receive
power, which serves as a reference for microwave link troubleshooting.
Prerequisites

U2000
NOTE
Context
The following procedure queries the change trend of historical transmit power and receive
power.
Procedure
Step 1

----End
A.5.11 Querying the SNR Value of a Microwave Link

This section describes how to query the change trend of the signal-to-noise ratio (SNR) value
of a microwave link, which serves as a reference for troubleshooting microwave link faults.
Prerequisites

U2000
NOTE
Context
The following procedure queries the change trend of the SNR value of a microwave link.
Procedure
Step 1

----End
A.6 Managing Ports

Setting port parameters correctly is the basis for configuring ports to carry services.
A.6.1 Setting Parameters for an Ethernet Port

Ethernet port parameters include basic attributes, traffic control, Layer 2 attributes, and advanced
attributes.
A.6.1.1 Setting the Basic Attributes for an Ethernet Port

The basic attributes of an Ethernet port define physical-layer information, such as the port mode,
encapsulation type, and maximum frame length.
Prerequisites

U2000
NOTE
The procedures performed on the Web LCT and U2000 are the same. In addition, the procedure performed on
the Web LCT can configure basic attributes for microwave ports.
Context
The following procedure configures the basic attributes for the port GE1 according to the planned

Parameter Value
1-SHUF3-2 (GE1)
Working Mode 100M Full-Duplex
Procedure
Step 1
----End
A.6.1.2 Configuring the Traffic Control Function for an Ethernet Port

After the traffic control function is enabled, an Ethernet port sends a pause frame to instruct the
peer end to stop sending Ethernet packets for a specific period of time if congestion occurs on
the link. Then the link congestion is eliminated.
Prerequisites

U2000
NOTE
Context
The following procedure configures the access control function for the port GE1 according to

Parameter Value
1-SHUF3-2 (GE1)
Auto-Negotiation Flow Control Mode Enable Symmetric Flow Control
Non-Autonegotiation Flow Control Mode Disabled
NOTE
Enable the flow control function for ports connected to external equipment only when the external equipment
uses the flow control function. Normally, the function is not required.
Procedure
Step 1
----End
A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port

Layer 2 attributes of Ethernet ports define tag attributes.
Prerequisites
l Encapsulation Type is set to 802.1Q for an Ethernet port.

U2000
NOTE
the Web LCT can configure Layer 2 attributes for microwave ports.

Context
The following procedure configures the Layer 2 attributes for the port GE1 according to the
Parameter Value
1-SHUF3-2 (GE1)
Tag Access
Default VLAN ID 100
VLAN Priority 0
NOTE
All tag attributes, except for the VLAN priority, can be configured during service configuration.
Procedure
Step 1
----End
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port

You can configure MAC/PHY layer loopbacks, check the port rates, and configure loopback
detection and broadcast packet suppression functions by setting related Ethernet advanced
attributes.
Prerequisites

U2000

NOTE
the Web LCT can configure advanced attributes for microwave ports.
Context
The following procedure configures the advanced attributes for the port GE1 according to the
Parameter Value
1-SHUF3-2 (GE1)
Broadcast Packet Suppression Enabled
Broadcast Packet Suppression Threshold 30%
NOTE
If the port is mounted with Ethernet local area network (E-LAN) services, enable the broadcast packet
suppression function for the port to suppress excessive packets in case of broadcast storms to E-LAN services.
It is recommended that you set the broadcast packet suppression threshold to the default value 30%.
Procedure
Step 1
----End
A.6.2 Setting Parameters for a Microwave Port

The process of setting the basic attributes, Layer 2 attributes, and advanced attributes for a
microwave port is similar to that for an Ethernet port.
A.6.2.1 Setting Basic Attributes for a Microwave Port

The general attributes of microwave ports define the physical-layer information, such as the port
mode and encapsulation type.

Prerequisites

U2000
NOTE
A.6.1.1 Setting the Basic Attributes for an Ethernet Port shows how to set the basic attributes for a microwave
port on the Web LCT. The procedures in A.6.1.1 Setting the Basic Attributes for an Ethernet Port performed
on the Web LCT and U2000 are the same. In addition, the procedure performed on the Web LCT can configure
basic attributes for microwave ports.
Context
The following procedure configures the basic attributes for a microwave port according to the
Parameters Value
1-SHUF3-1 (IF)
Procedure
Step 1
----End
A.6.2.2 Setting Layer 2 Attributes for a Microwave Port

The Layer 2 attributes of microwave ports define tag attributes.

Prerequisites
l Encapsulation Type is set to 802.1Q for a microwave port.

U2000
NOTE
A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port shows how to set the Layer 2 attributes for a
microwave port on the Web LCT. The procedures in A.6.1.3 Setting the Layer 2 Attributes for an Ethernet
Port performed on the Web LCT and U2000 are the same. In addition, the procedure performed on the Web
LCT can configure Layer 2 attributes for microwave ports.
Context
The following procedure configures the Layer 2 attributes for a microwave port according to
Parameters Value
1-SHUF3-1 (IF)
Tag Access
Default VLAN ID 100
VLAN Priority 0
NOTE
When services are configured on a per-NE basis, all tag attributes, except for the VLAN priorities, can be
configured during service configuration.
Procedure
Step 1

----End
A.6.2.3 Setting Advanced Attributes for a Microwave Port

The advanced attributes of microwave ports are for querying the port traffic rate, configuring
loop detection, and configuring broadcast packet suppression.
Prerequisites

U2000
NOTE
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port shows how to set the advanced attributes for
a microwave port on the Web LCT. The procedures in A.6.1.4 Setting the Advanced Attributes for an
Ethernet Port performed on the Web LCT and U2000 are the same. In addition, the procedure performed on
the Web LCT can configure advanced attributes for microwave ports.
Context
The following procedure configures the advanced attributes for a microwave port according to
Parameters Value
1-SHUF3-1 (IF)
Broadcast Packet Suppression Enabled
Broadcast Packet Suppression Threshold 30%

NOTE
If the port is mounted with Ethernet local area network (E-LAN) services, enable the broadcast packet
suppression function for the port to suppress excessive broadcast packets in an E-LAN service broadcast storm.
It is recommended that you set the broadcast packet suppression threshold to the default value 30%.
Procedure
Step 1
----End
A.7 Managing Ethernet Services and Features

Configurations of Ethernet services and features on the packet plane include Ethernet port,
protection, service, protocol, and OAM configurations.
A.7.1 Managing ERPS

For an FE/GE ring network or a hybrid network, Ethernet ring protection switching (ERPS) can
be configured to protect Ethernet services.
A.7.1.1 Creating an ERP Instance

Ethernet ring protection switching (ERPS) is configured by creating ERP instances.
Prerequisites

U2000
NOTE

Context
The following procedure creates an ERP instance according to the planned parameter values
Parameter Value
ERPS ID 1
East Port 1-SHUF3-1(IF)
West Port 1-SHUF3-2(GE1)
RPL Owner Ring Node Flag Yes
RPL Port 1-SHUF3-1(IF)
Control VLAN 100
Procedure
Step 1
----End
A.7.1.2 Setting ERPS Protocol Parameters

The Ethernet ring protection switching (ERPS) protocol parameters to be set include the hold-
off time, wait to restore (WTR) time, and guard time.
Prerequisites
l An Ethernet ring protection (ERP) instance has been created.

U2000

NOTE
Context
The following procedure configures ERPS protocol parameters according to the planned
Parameter Value
WTR Time (min) 10
Set the parameters according to the network plan. Default values are recommended.
Procedure
Step 1
----End
A.7.1.3 Querying the ERPS Status

By performing this task, you can query the Ethernet ring protection switching (ERPS) status.
Prerequisites

U2000
NOTE

Context
The following procedure queries the ERPS status.
Procedure
Step 1
----End
A.7.2 Managing LAGs

Link aggregation allows one or multiple links that are connected to the same equipment to be
aggregated to form a link aggregation group (LAG). For MAC users, a LAG works as a single
link. In this manner, the link bandwidth and availability are improved.
A.7.2.1 Creating a LAG

If the bandwidth or availability of the Ethernet link between two NEs needs to be improved,
create a link aggregation group (LAG).
Prerequisites

U2000
NOTE
Context
l Creates a non-load sharing LAG to protect the Ethernet link from a UNI-side equipment
to an NE, according to the planned parameter values listed in the following table.

Parameter NE
LAG Name LAG_01
Load Sharing Non-Sharing
Main Ports 1-SHUF3-3 (GE2)
l Creates a load-sharing LAG to increase the Ethernet bandwidth for a link between air
interfaces, according to the planned parameter values listed in the following table.
Parameter NE
LAG Name LAG_02
Load Sharing Sharing
LAG Min Active Link Threshold 1
Main Ports 1-SHUF3-1 (IF)
Switch LAG upon Air Interface SD Enabled
l Create a LAG for configuring 1+1 protection according to the planned parameter values
Parameter NE
LAG No. Assign Automatically (default value).
LAG type Static (default value)
Load sharing type Non-load sharing (default value)
LAG priority 32768 (default value)
Main port 1-SHUF3-2 (GE1)

Procedure
Step 1 Create a non-load sharing LAG.
Step 2 Create a load-sharing LAG.
Step 3 Create a LAG for configuring 1+1 protection with NE-level protection.

----End
A.7.2.2 Setting Parameters for a LAG

Link aggregation group (LAG) parameters include port priority and load-sharing algorithm.
Prerequisites

U2000
NOTE
Context
The following procedure sets LAG parameters according to the planned parameter values listed
Parameter Value
Port Priority 32768 (default value)
System Load Sharing Hash Algorithm Source and Destination MACs
Procedure
Step 1

----End
A.7.2.3 Querying the Protocol Information About a LAG

By performing this task, you can learn about the running information of the Link Aggregation
Control Protocol (LACP) used for a link aggregation group (LAG).
Prerequisites
l A LAG has been created.

U2000
NOTE
Context
The following procedure queries the LACP information about a LAG.
Procedure
Step 1

----End
A.7.3 Configuring Ethernet Services

Ethernet services are classified into two types: Ethernet line (E-Line) service and Ethernet local
area network (E-LAN) service.
A.7.3.1 Creating a Point-to-Point Transparently Transmitted E-Line Service

By creating point-to-point transparently transmitted Ethernet line (E-Line) services, you can
transparently transmit all packets received at the source to the sink.
Prerequisites
l The service to be created does not conflict with existing services.

U2000
NOTE
Precautions
In point-to-point transparently transmitted E-Line services, Layer 2 protocol packets are
transmitted as common services. Therefore, Layer 2 protocol packets cannot be transmitted first
in the case of link congestion.
Context
The following procedure creates the point-to-point transparently transmitted E-Line service
shown in the following figure.

GE1
(Auto-Negotiation)
E-Line
IF
GE2
Procedure
Step 1
----End
A.7.3.2 Creating a VLAN-based E-Line Service

By creating VLAN-based Ethernet line (E-Line) services, you can transmit service packets from
the source to a sink based on the VLAN IDs carried by the packets. Layer 2 protocol packets
cannot be transmitted as VLAN-based E-Line services.
Prerequisites

U2000
NOTE

Precautions
Layer 2 protocol packets cannot be transmitted as VLAN-based E-Line services. See A.7.3.4
Creating an E-Line Service for Transmitting Layer 2 Protocol Packets to perform necessary
operations if Layer 2 protocol packets need to be transparently transmitted.
Context
The following procedure creates the VLAN-based E-Line service shown in the following figure.
GE1
(Auto-Negotiation)
VLAN ID=100 E-Line
IF
VLAN ID=100
GE2
Procedure
Step 1
----End
A.7.3.3 Creating a QinQ-based E-Line Service

QinQ-based E-Line services add or strip SVLAN IDs to/from service packets on source ports
based on QinQ operation types, and forward the packets to the corresponding sink ports. Layer
2 protocol packets cannot be transmitted as QinQ-based E-Line services.
Prerequisites


U2000
NOTE
Precautions
Layer 2 protocol packets cannot be transmitted as QinQ-based E-Line services. See A.7.3.4
Creating an E-Line Service for Transmitting Layer 2 Protocol Packets to perform necessary
operations if Layer 2 protocol packets need to be transparently transmitted.
Context
The following procedure creates the QinQ-based E-Line service shown in the following figure.
GE1
(Auto-Negotiation)
Unknown VLAN ID E-Line
IF
SVLAN ID=100
GE2
Procedure
Step 1
----End

A.7.3.4 Creating an E-Line Service for Transmitting Layer 2 Protocol Packets

An Ethernet line (E-Line) service can be created for transmitting Layer 2 protocol packets from
the source to the sink as packets with a per-hop behavior (PHB) of CS7.
Prerequisites

U2000
NOTE
Context
The following procedure creates the E-Line service shown in the following figure for
transmitting Link Aggregation Control Protocol (LACP) packets.
GE1
LACP packet E-Line

IF
LACP packet
GE2
Procedure
Step 1
----End

A.7.3.5 Creating VLAN Forwarding Table Entries

VLAN forwarding table entries enable VLAN ID switching at the source or sink end of an
Ethernet line (E-Line) service.
Prerequisites
l An E-Line service has been configured.

U2000
NOTE
Context
The following procedure configures a VLAN forwarding table to implement VLAN switching
for an E-Line service.
GE1
VLAN ID=100 E-Line
IF
VLAN ID=200
GE2
E-Line Service Information Table

Source Source Sink Sink
Interface VLAN ID Interface VLAN ID
GE1 100 IF 200
VLAN Forwarding Table

Source Source Sink Sink
Interface VLAN ID Interface VLAN ID
GE1 100 IF 200
IF 200 GE1 100
NOTE
A VLAN forwarding table entry implements only unidirectional VLAN switching. For bidirectional VLAN
switching, you must configure two VLAN forwarding table entries.
Procedure
Step 1

----End
A.7.3.6 Creating an IEEE 802.1D Bridge-based E-LAN Service

An IEEE 802.1D bridge is a transparent bridge and functions as a switching domain.
Prerequisites

U2000
NOTE
Precautions
l In IEEE 802.1D bridge-based Ethernet local area network (E-LAN) services, Layer 2
protocol packets are transmitted as common services. Therefore, Layer 2 protocol packets
cannot be transmitted first in the case of link congestion.
l By default, the NE carries an IEEE 802.1D bridge-based E-LAN service that is mounted
to all the ports of the NE.
Context
The following procedure creates the IEEE 802.1D bridge-based E-LAN service shown in the
following figure.
GE1
(Auto-Negotiation)
IF
GE2
(Auto-Negotiation)
Bridge

Procedure
Step 1
----End
A.7.3.7 Creating an IEEE 802.1Q Bridge-based E-LAN Service

An IEEE 802.1Q bridge is a virtual bridge (VB), which can be divided by VLANs into several
switching domains.
Prerequisites

U2000
NOTE
Precautions
IEEE 802.1Q bridge-based Ethernet local area network (E-LAN) services can be configured to
transparently transmit Layer 2 protocol packets as packets with a per-hop behavior (PHB) of
CS7.
Context
The following procedure creates the IEEE 802.1Q bridge-based E-LAN service shown in the
following figure.

GE1
(Auto-Negotiation)
VLAN ID=100
IF
GE2 VLAN ID=100,200
(Auto-Negotiation)
VLAN ID=200
Bridge
Procedure
Step 1
----End
A.7.3.8 Creating an E-LAN Service for Transmitting Layer 2 Protocol Packets

An Ethernet local area network (E-LAN) service can be created for transmitting Layer 2 protocol
packets from the source to the sink as packets with a per-hop behavior (PHB) of CS7.
Prerequisites
l An IEEE 802.1Q bridge-based E-LAN service has been created.

U2000
NOTE
Context
The following procedure creates an E-LAN service for transmitting Link Aggregation Control
Protocol (LACP) packets shown in the following figure.

GE1
LACP packet E-LAN

IF
LACP packet
GE2
NOTE
The port used to transmit the E-LAN service carrying LACP packets must be the same as the port that is used
to transmit the IEEE 802.1Q bridge-based E-LAN service.
Procedure
Step 1
----End
A.7.3.9 Configuring a Split Horizon Group

Ports mounted to the same split horizon group cannot forward packets to one another.
Prerequisites
l Ethernet local area network (E-LAN) services have been configured.

U2000
NOTE

Context
The following procedure creates a split horizon group for the E-LAN services shown in the
following figure, so that the ports GE1 and GE2 cannot forward packets to each other.
GE1
(Auto-Negotiation)
IF
GE2
(Auto-Negotiation)
Bridge
Split horizon group
Procedure
Step 1
----End
A.7.3.10 Changing Logical Ports Mounted to a Bridge

This section describes how to change the logical ports mounted to a bridge and how to modify
the attributes of the ports.
Prerequisites

U2000

NOTE
Context
The following procedure deletes the port GE2 to which the E-LAN services are mounted and
removes VLAN 200 from the VLAN list of the microwave port.
Procedure
Step 1
----End
A.7.3.11 Configuring a QinQ Link

QinQ link configuration is the prerequisite for configuring a QinQ-based Ethernet line (E-Line)
service.
Prerequisites
l On associated ports, the Encapsulation Type is set to QinQ.

U2000
NOTE
Context
The following procedure configures a QinQ link according to the planned parameter values listed

Parameter Value
QinQ Link ID 1
Port 2(PORT-2)
S-VLAN ID 100
Procedure
Step 1
----End
A.7.3.12 Configuring an E-Line Service Carried by a QinQ Link from a UNI to an

NNI
This section describes how to configure an Ethernet line (E-Line) service carried by a QinQ link
from a user-to-network interface (UNI) to a network-to-network interface (NNI).
Prerequisites
l Ethernet boards have been added on the NE Panel.
l For UNI and NNI ports that carry services, Port Mode has been set to Layer 2. For NNI
ports, Encapsulation Type has been set to QinQ.

U2000
Context
The following procedure configures an E-Line service carried by a QinQ link from a UNI to an
NNI, according to the planned parameter values listed in the following table.

Parameter Value
Service ID 1
Service Name E-LINE
Direction UNI-NNI
Source 1-SHUF3-3 (GE2)
Sink QinQ Link-1
VLAN ID (Sink) 100
Procedure
Step 1
----End
A.7.3.13 Deleting an E-Line Service

When an Ethernet line (E-Line) service is not used, you need to delete the service to release
Ethernet resources.
Prerequisites
l An E-Line service has been configured.

U2000
NOTE

Context
The following procedure deletes the E-Line service whose ID is 1.
Procedure
Step 1
----End
A.7.3.14 Deleting an E-LAN Service

When an Ethernet local area network (E-LAN) service is not used, you need to delete the service
to release Ethernet resources.
Prerequisites
l An E-LAN service has been configured.

U2000
NOTE
Context
The following procedure deletes the E-LAN service whose ID is 1.
Procedure
Step 1

----End
A.7.4 Managing MAC Address Tables

A MAC address table is the core of an Ethernet local area network (E-LAN) service. OptiX RTN
380 provides various functions for managing MAC address tables.
A.7.4.1 Creating a Static MAC Address Entry

By creating static MAC address entries, you can ensure that hosts with specific MAC addresses
are not affected after the MAC addresses are aged out. In addition, static MAC address entries
ensure that Ethernet local area network (E-LAN) services are applicable to hosts that receive
but not transmit packets.
Prerequisites
l E-LAN services have been configured.

U2000
NOTE
Context
The following procedure adds the MAC address listed in the following table into the static MAC
address table for an E-LAN service.
Parameter Value
VLAN ID 100
MAC Address 00–09–09–09–58–01

Parameter Value
Egress Interface GE1
Procedure
Step 1
----End
A.7.4.2 Creating a Blacklist MAC Address Entry

This section describes how to prevent NEs with specific MAC addresses from receiving/
transmitting Ethernet local area network (E-LAN) services by creating blacklist MAC address
entries.
Prerequisites

U2000
NOTE
Context
The following procedure blacklists the MAC address listed in the following table for an E-LAN
service.

Parameter Value
VLAN ID 100
MAC Address 00–08–09–09–57–07
Procedure
Step 1
----End
A.7.4.3 Managing a Dynamic MAC Address Table

By performing this task, you can set aging parameters, or query or clear entries in a dynamic
MAC address table.
Prerequisites

U2000
NOTE
Context
The following procedure sets the aging time to 10 minutes for a dynamic MAC address entry.

Procedure
Step 1
----End
A.7.5 Setting the Mode for Processing an Unknown Frame of an E-

LAN Service
An unknown frame refers to either a unicast frame whose destination MAC address is not in the
MAC address table or a multicast frame whose MAC address is not in a multicast group. By
default, an NE broadcast an unknown frame. By performing this task, you can change the
processing mode to discarding.
Prerequisites

U2000
NOTE
Context
The following procedure changes the processing mode for unknown frames to Discarding.
NOTE
In practice, it is recommended that you do not change the processing mode for unknown frames.
Procedure
Step 1

----End
A.7.6 Managing QoS

By managing QoS, you can provide different service levels for different service types.
A.7.6.1 Modifying the Mapping for a DS Domain

This section describes how to modify the mapping between packet priorities and per-hop
behaviors (PHBs) in the ingress or egress direction of a Differentiated Services (DS) domain.
Prerequisites

U2000
NOTE
Context
The following procedure changes the mapping for a DS domain according to the planned
parameter values listed in the following tables.
The following table provides the values of the parameters on the Ingress tab page.
CVLAN/SVLAN MPLS EXP IP DSCP PHB
12 AF11
8 AF13
20 AF21

16 AF23
28 AF31
24 AF33
36 AF41
32 AF43
40 EF
48 CS6
56 CS7
The following table provides the values of the parameters on the Egress tab page.
12 AF11
8 AF13
20 AF21
16 AF23
28 AF31
24 AF33
36 AF41
32 AF43
40 EF
48 CS6
56 CS7
Procedure
Step 1

----End
A.7.6.2 Changing the Packet Type Trusted by a Port

This section describes how to set the packet type trusted by a port.
Prerequisites

U2000
NOTE
Context
The following procedure changes the packet types trusted by the Ethernet ports and microwave
port to the planned value listed in the following table.
GE1 ip-dscp
GE2
IF
Procedure
Step 1

----End
A.7.6.3 Configuring CAR for a Port or Creating Traffic Classification

By performing this task, you can configure committed access rate (CAR) for a port or map a
flow that complies with traffic classification matching rules to a specified priority queue.
Prerequisites

U2000
NOTE
Context
NOTE
l The two operations that you can perform are mutually exclusive for a port.
l If Match Value is set to 0, this task enables you to configure CAR for a port. If Match Value is set to
a non-zero value, this task enables you to map a flow that complies with traffic classification matching
rules to a specified priority queue.

l Configures CAR for a port.
Parameter Value
Traffic Classification ID 1
Port 1-SHUF3-4(GE3)
Match Type CVLAN ID
Match Value 0

Parameter Value
CoS AF1
Bandwidth Limit Enable
CIR(Kbit/s) 102400
PIR(Kbit/s) 204800
CBS(byte) 128000
PBS(byte) 256000
Yellow packet processing mode Pass
l Maps a flow that complies with traffic classification matching rules to a specified priority
queue.
Parameter Value
Traffic Classification ID 2
Port 1-SHUF3-3(GE2)
Match Type CVLAN ID
Match Value 100
CoS AF1
Procedure
Step 1 Configure CAR for a port.
Step 2 Map a flow that complies with traffic classification matching rules to a specified priority queue.

----End
A.7.6.4 Configuring Port Shaping

This section describes how to configure traffic shaping for an egress port.
Prerequisites

U2000
NOTE
Context
The following procedure configures port shaping for the Ethernet port GE1 according to the
Parameter Value
Bandwidth Limit Enabled
PIR (kbit/s) 512
PBS (kbit/s) 512
Procedure
Step 1

----End
A.7.6.5 Setting Egress Queue Scheduling Policies

This section describes how to set queue scheduling policies for an egress port.
Prerequisites

U2000
NOTE
Context
The following procedure configures queue scheduling policies for a microwave port according
Parameter Grooming Policy After Reloading
CS7 SP (default value)
CS6 SP (default value)
EF SP (default value)
AF4 SP
AF3 SP
AF2 SP
AF1 SP
BE SP (default value)

Procedure
Step 1
----End
A.7.6.6 Setting Traffic Shaping for Egress Queues

This section describes how to set traffic shaping for an egress queue.
Prerequisites

U2000
NOTE
Context
The following procedure sets traffic shaping for an egress queue (AF4) at a microwave port
Parameter Value
Bandwidth Limit Enabled
PIR (kbit/s) 512
PBS (kbit/s) 512
Procedure
Step 1

----End
A.7.6.7 Setting the Congestion Management Mode for Egress Queues

This section describes how to set the congestion management mode for an egress queue.
Prerequisites

U2000
NOTE
Context
The following procedure sets the congestion management mode for an egress queue at a
microwave port according to the planned parameter values listed in the following table.
Paramete Congesti WRED Configuration

r on
Manage ID Name Upper Lower Discard
ment Threshol Threshol Ratio (%)
Mode d (Bytes) d (Bytes)
CS7 Tail drop - - - - -

CS6 (default)
EF
AF4
AF2
AF1
BE

Paramete Congesti WRED Configuration

r on
Manage ID Name Upper Lower Discard
ment Threshol Threshol Ratio (%)
Mode d (Bytes) d (Bytes)
AF3 WRED Auto- WRED1 64 (green) 42 (green) 100

assign 42 (red) 21 (red) (default
value)
Procedure
Step 1
----End
A.7.7 Using Ethernet Service OAM

By using Ethernet service OAM, you can maintain Ethernet services in an end-to-end manner.
A.7.7.1 Creating an MD
A maintenance domain (MD) defines the Ethernet OAM range and level. MDs of different ranges
and levels can provide users with differentiated OAM services.
Prerequisites

U2000
NOTE

Context
The following procedure creates a maintenance domain according to the planned parameter
Parameter Value
Maintenance Domain Name MD1
Maintenance Domain Level 4
Procedure
Step 1
----End
A.7.7.2 Creating an MA
A maintenance domain (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.
Prerequisites
l An MD has been created.
l An Ethernet service has been created.

U2000
NOTE

Context
The following procedure creates an MA according to the planned parameter values listed in the
following table.
Parameter Value
Maintenance Domain Name default
Maintenance Association Name MA1
Relevant Service auto_configuration
CC Test Transmit Period 1s
Procedure
Step 1
----End
A.7.7.3 Creating an MEP

Maintenance association end points (MEPs) initiate or terminate Ethernet OAM packets. After
creating MEPs, you can check the Ethernet link between MEPs in the same maintenance
association (MA) by performing OAM operations.
Prerequisites
l An MA has been created.

U2000

NOTE
Context
The following procedure creates an MEP for the Ethernet port GE1 according to the planned
Parameter Value
Port 1-SHUF3-2(GE1)
VLAN 100
MP ID 1
Direction Ingress
CC Status Active
Procedure
Step 1
----End
A.7.7.4 Creating a Remote MEP in an MA

To ensure that a maintenance association end point (MEP) can respond to the OAM operations
initiated by the other MEPs in the same maintenance association (MA), you must configure the
other MEPs to be the remote MEPs of this MEP.

Prerequisites
l An MA has been created.

U2000
NOTE
Context
The following procedure creates a remote MEP according to the planned parameter values listed
Parameter Value
Remote Maintenance Point ID 2
Procedure
Step 1
----End
A.7.7.5 Creating an MIP

Maintenance association intermediate points (MIPs) can respond to specific OAM packets. By
creating MIPs, you can divide the Ethernet link between two MEPs in the same maintenance
association (MA) into several segments, therefore facilitating the Ethernet link checking.

Prerequisites
l A maintenance domain (MD) has been created.

U2000
NOTE
Context
The following procedure creates an MIP for the Ethernet port GE2 according to the planned
Parameter Value
Port 1-SHUF3-3(GE2)
MP ID 1
Procedure
Step 1
----End
A.7.7.6 Performing a CC Test

A continuity check (CC) test checks the status of a unidirectional link automatically and
periodically. If a CC test started at the source end finds that the link is faulty, the sink reports
the corresponding alarm.

Prerequisites
l The source and sink maintenance association end points (MEPs) in the same maintenance
associations have been created.
l The remote MEPs have been created.

U2000
NOTE
Precautions
l Only an MEP can start a CC test and function as the receive or respond end in the test.
l During a 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. If the sink MEP fails to receive the CCM packets
from the source MEP within the specified period (3.5 times the transmission interval), it
reports an alarm automatically.
l A CC test does not affect services.
Context
The following procedure performs a CC test.
Procedure
Step 1
----End
A.7.7.7 Performing an LB Test

A loopback (LB) test enables you to check the bidirectional connectivity between the source
and sink maintenance association end points (MEPs) in the same maintenance association (MA).

Prerequisites
l The source and sink MEPs in the same maintenance associations have been created.
l The continuity check (CC) function has been enabled.

U2000
NOTE
Precautions
l Only an MEP can initiate an LB test and function as the receive end in the test.
l During an LB test, the source MEP constructs and transmits loopback message (LBM)
frames and starts the timer. If the sink MEP receives the LBM frames, it sends loopback
reply (LBR) frames back to the source MEP. This indicates that the loopback is successful.
If the source MEP timer expires, the loopback has failed.
l An LB test does not affect services.
Context
The following procedure enables an LB test according to the planned parameter values listed in
Parameter Value
Source Maintenance ID 2
Destination Maintenance ID 1
Procedure
Step 1

----End
A.7.7.8 Performing an LT Test

Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate
faults. A faulty network segment can be located based on maintenance association intermediate
points (MIPs) through only one test.
Prerequisites
association (MA) have been created.
l The continuity check (CC) function has been enabled.

U2000
NOTE
Precautions
l Only an MEP can initiate an LT test and work as the receive end in the test.
l During an LT test, the source MEP constructs and transmits link trace message (LTM)
frames and starts the timer. All the MPs that receive the LTM frames respond with link
trace reply (LTR) frames. According to the LTR frames, you can determine all the MIPs
long the path from the source MEP to the sink MEP.
l An LT test does not affect services.
Context
The following procedure enables an LT test according to the planned parameter values listed in

Parameter Value
Source Maintenance ID 2
Destination Maintenance ID 1
Procedure
Step 1
----End
A.7.7.9 Activating the AIS

After a fault is detected by a maintenance point (MP) on which the alarm indication signal (AIS)
function is activated, the MP sends an AIS packet to inform a higher-level MP of the fault
information.
Prerequisites
domain (MD) have been created.

U2000
NOTE

Context
The following procedure activates the AIS function.
Procedure
Step 1
----End
A.7.7.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet

Services
The ETH OAM function allows you to monitor packet loss ratio, delay, or delay variation of
Ethernet services without any impact on the Ethernet services.
Prerequisites
l Native Ethernet line (E-Line) services that are transmitted based on ports and VLAN IDs
have been created.
l The source and sink maintenance end points (MEPs) in the same maintenance domain (MD)
have been created.

U2000
NOTE
Precautions
OptiX RTN 380 uses the remote network monitoring (RMON) function to collect statistics about
packet loss ratio, delay, or delay variation of Ethernet services.

Context
l Monitors the real-time performance statistics of Ethernet ports.
l Monitors the 30-minute historical performance statistics of Ethernet ports.
Procedure
Step 1 Monitor the current packet loss ratio, delay, or delay variation.
Step 2 Monitor the historical packet loss ratio, delay, or delay variation.
----End
A.7.7.11 Performing E-LAN Service Loopback Detection

This section describes how to configure automatic detection of Ethernet local area network (E-
LAN) service loopbacks and automatic service disabling.
Prerequisites

l E-LAN services have been created.

U2000
Context
l Creation of MEPs is not a prerequisite for service loopback detection.
NOTE
During an E-LAN service loopback test, if a node on the network to which the test port is connected reports a
loopback packet threshold-crossing event, there is an E-LAN service loop on this node.
The following procedure performs E-LAN service loopback detection and disables services
automatically in the case of an E-LAN service loopback.
Parameter Value
VLAN/CVLAN NULL
Packet Timeout Period(s) 3
Disable Service When Loopback Is Detected Yes
Procedure
Step 1
----End
A.7.7.12 Reactivating an E-LAN Service

This section describes how to reactivate Ethernet local area network (E-LAN) services that are
deactivated during a service loopback detection process.

Prerequisites
l An E-LAN service port has been disabled due to a service loopback.

U2000
Context
The following procedure reactivates an E-LAN service.
Procedure
Step 1
----End
A.7.8 Using Ethernet Port OAM

By using Ethernet port OAM, you can maintain point-to-point Ethernet links.
A.7.8.1 Enabling OAM Auto-discovery

IEEE 802.3ah OAM is implemented based on OAM auto-discovery. After the OAM auto-
discovery operation is successful, the equipment automatically monitors the fault and
performance of the link.
Prerequisites

U2000

NOTE
Precautions
OAM auto-discovery is implemented based on the auto-negotiation between the local equipment
and the peer equipment. If the negotiation fails, the local equipment reports an alarm. After OAM
auto-discovery is successfully completed, the link performance is monitored according to the
errored frame threshold. You can set the errored frame threshold on the network management
system (NMS).
Context
The following procedure enables the OAM auto-discovery function according to the planned
Parameter Value
Port 1-SHUF3-1(IF-1)
OAM Working Mode Active (default value)
Enable OAM Protocol Enabled
Procedure
Step 1
----End
A.7.8.2 Enabling the Link Event Notification

After the link event notification is enabled on the local equipment, the peer equipment is
informed if OAM detects a link fault or a link performance event.

Prerequisites
l The OAM auto-discovery operation has been performed successfully on the equipment at
both ends.

U2000
NOTE
Context
The following procedure enables the link event notification function for a microwave port.
Procedure
Step 1
----End
A.7.8.3 Changing the OAM Errored Frame Monitoring Threshold

Set the OAM errored frame monitoring threshold, so OAM checks link performance based on
this threshold. Generally, the default value is used. You can change the value based on link
conditions.
Prerequisites
l The IEEE 802.3ah OAM function has been enabled on the peer equipment. The OAM auto-
discovery operation has been performed successfully on the equipment at both ends.

U2000

NOTE
Precautions
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 peer equipment
of the link event. If the remote alarm for the link event is also supported at the peer end, the peer
equipment can inform the local equipment of the link event it has detected. Then, the
corresponding alarm is reported at the local end.
Context
The following procedure modifies Error Frame Period Window of the port GE1 to the planned
value listed in the following table.
Parameter Value
Error Frame Monitor Window(ms) 1000 (default value)
Error Frame Monitor Threshold(frames) 1 (default value)
Error Frame Period Window(frame) 8928000
Error Frame Period Threshold(frames) 1 (default value)
Error Frame Second Window(s) 60 (default value)
Error Frame Second Threshold(s) 1 (default value)
Procedure
Step 1
----End

A.7.8.4 Performing a 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 peer end to return the data.
Prerequisites
l The OAM auto-discovery operation has been performed successfully at both ends of the
link.
l OAM Working Mode is set to Active on the equipment that has initiated the loopback.
l The equipment that responds to the loopback supports the remote loopback.

U2000
NOTE
Precautions
l If a port is capable of responding to loopbacks, it enters the loopback responding state and
reports a loopback responding alarm after receiving the command of enabling the remote
loopback function sent from the peer OAM port. The equipment that initiates the loopback
enters the loopback initiation state and reports a loopback initiation alarm.
l Generally, after the remote loopback function is enabled, service packets, except for
OAMPDU packets and data communication network (DCN) packets, are looped back at
the peer end.
l After using the remote loopback function to locate a fault and test link performance, you
must disable the remote loopback function at the end where the loopback is initiated, and
then restore services. The alarm is automatically cleared.
Context
The following procedure performs a remote loopback on a microwave port.
Procedure
Step 1

----End
A.7.8.5 Enabling Self-loop Detection

After enabling 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.
Prerequisites
l All the external physical ports have been enabled.

U2000
NOTE
Context
The following procedure enables the self-loop detection function for the Ethernet port GE1.
Procedure
Step 1

----End
A.7.9 Configuring LPT

After link-state pass through (LPT) is configured, Ethernet ports correlated with microwave
links can be disabled automatically in the case of a microwave link fault. OptiX RTN 380
supports simplified LPT.
Prerequisites

U2000
Context
The following procedure configures LPT according to the planned parameter values listed in the
following table.
Parameter Value
Convergence Port 1-SHUF3-1 (IF)
Access Port 1-SHUF3-2 (GE1)
Procedure
Step 1

----End
A.8 Managing Clocks

To ensure clock synchronization between transmission nodes on a transport network, you need
to manage the NE clocks.
A.8.1 Managing Clocks at the Physical Layer

This section describes how to synchronize clock signals by transmitting reference clock signals
at the physical layer.
A.8.1.1 Configuring Clock Sources

This section describes how to configure clock sources according to the planned clock
synchronization scheme so that all the NEs on the network trace the same clock.
Prerequisites

U2000
NOTE
Context
The following procedure configures a microwave port and the port as clock sources. The priority
of the clock source at the microwave port is higher than that at the port .

Procedure
Step 1
----End
A.8.1.2 Configuring Protection for Clock Sources

This section describes how to configure protection for clock sources. For a simple network (such
as a chain network), protection for the clock sources is not required or the clock sources are
protected according to the clock source priority table. For a complex network (such as a ring
network, a ring with chain network, or a network consisting of intersectant rings), clock sources
need to be protected by using the standard Synchronization Status Message (SSM) protocol or
the extended SSM protocol.
Prerequisites
l Clock sources have been configured.

U2000
NOTE
Context
l Enables the standard SSM protocol.

l Enables the extended SSM protocol and sets the IDs of the clock source GE1 and the internal
clock source to 1 and 2 respectively.

NOTE
l It is recommended that you enable the standard SSM protocol for a simple ring network and enable the
extended SSM protocol for a complex network (for example, a network consisting of intersectant rings,
which may provide the network with multiple clock sources).
l If the extended SSM protocol is enabled, set IDs for the following clock sources:
l Reference clock sources for a ring network
l Local clock source of an NE that traces a clock source outside the ring network
Each clock source ID must be unique and is unrelated to priorities.
Procedure
Step 1 Enable the standard SSM protocol.
Step 2 Enable the extended SSM protocol.
----End
A.8.1.3 Customizing the Clock Quality

By default, an NE determines the quality of a clock based on the clock quality information
extracted from the clock source. If the clock quality is 0 (indicating that the synchronization

quality is unknown), the clock source is unavailable. If required, you can customize the clock
quality of all clock sources and the clock quality level of the clock source whose clock quality
is 0.
Prerequisites
l Clock sources have been configured.

U2000
NOTE
Context
The following procedure sets the clock quality of the clock source at the port PORT-2 to G.811.
NOTE
If an NE cannot extract the clock quality of a clock source for a ring network (for example, if an NE provides
a synchronous Ethernet clock source for the ring network but cannot transmit the clock quality information
through SSMs), define the clock quality manually.
Procedure
Step 1
----End
A.8.1.4 Enabling/Disabling SSM Transmission

After the standard Synchronization Status Message (SSM) protocol or the extended SSM
protocol is enabled for an NE, the NE sends SSMs to the other NEs in the same clock subnet
through all microwave links or Ethernet links. To prevent interference between two different
clock subnets, the NE must be disabled from sending SSMs to links connected to another clock
subnet.

Prerequisites

U2000
NOTE
Context
The following procedure disables the port PORT-2 from transmitting SSMs.
NOTE
For a port connected to another clock subnet on which the SSM protocol is enabled, disable the port from
transmitting SSMs.
Procedure
Step 1
----End
A.8.1.5 Enabling/Disabling the Output of Clock Source IDs

After the extended Synchronization Status Message (SSM) protocol is enabled for an NE, the
NE sends clock source IDs to the other NEs through all microwave links or Ethernet links. To
avoid interference between two different clock subnets, the NE needs to be disabled from sending
clock source IDs to links connected to another clock subnet.
Prerequisites


U2000
NOTE
Context
The following procedure disables the port PORT-2 from transmitting clock source IDs.
NOTE
For a port connected to another clock subnet on which the extended SSM protocol is enabled, disable the port
from transmitting clock source IDs.
Procedure
Step 1
----End
A.8.1.6 Modifying Clock Source Reversion Parameters

You can change the default values of certain clock source reversion parameters if required.
Prerequisites

U2000
NOTE

Context
The following procedure sets the clock reversion mode of a high-priority clock source to non-
revertive.
NOTE
Normally, all clock source reversion parameters take their default values. If strict concordance between the clock
trail and the service route is required, you can change the parameter values according to the reversion mode and
wait to restore (WTR) time configured for service protection.
Procedure
Step 1
----End
A.8.1.7 Querying the Clock Synchronization Status

By performing this task, you can query the clock synchronization status of an NE.
Prerequisites

U2000
NOTE
Procedure
Step 1

----End
A.9 Using RMON

Remote network monitoring (RMON) monitors the data traffic on a network segment or an entire
network. Currently, RMON is one of the most widely used network management standards.
A.9.1 Browsing Current Performance Events of Ethernet

After you configure a remote network monitoring (RMON) statistics group for a port, you can
browse the real-time statistical performance data of the port.
Prerequisites

U2000
NOTE
Context
The following procedure allows you to browse the real-time Unicast Packets Received
(packets/s) and Unicast Packets Transmitted(packets/s) of GE port.
Procedure
Step 1

----End
A.9.2 Setting the Ethernet Performance Threshold-Crossing

Parameter
After you configure a remote network monitoring (RMON) alarm group for a port, you can
monitor whether the performance value of the port crosses the configured thresholds in the long
term.
Prerequisites

U2000
NOTE
Context
The following procedure enables the threshold-crossing monitoring function for RXPKT64
Parameter Value
30-Second Enabled
30-Minute Enabled
Custom Period 1 Enabled

Procedure
Step 1
----End
A.9.3 Configuring the Parameters for Ethernet Historical

Performance Monitoring
When configuring a historical control group for an Ethernet port, you can configure how the
historical performance data of the port is monitored. The Ethernet board monitors the historical
performance data of each port at the default sampling interval of 30 minutes. A maximum of 50
historical performance entries can be saved.
Prerequisites

U2000
NOTE
Context
The following procedure enables the monitoring of Custom Period 1 for undersized packets
Parameter Value
Period Length(s) 900
History Register Count 16

Procedure
Step 1
----End
A.9.4 Browsing Ethernet Historical Performance Data

After you configure a remote network monitoring (RMON) historical group for a port, you can
browse the historical performance data of the port.
Prerequisites
l The task in A.9.3 Configuring the Parameters for Ethernet Historical Performance
Monitoring has been completed.

U2000
NOTE
Context
The following procedure allows you to browse the 30-second historical performance count
statistics at port GE1.
Procedure
Step 1

----End
A.10 Configuring a Native Ethernet Service (in End-to-End

Mode)
The U2000 allows Native Ethernet services to be configured in an end-to-end mode.
A.10.1 Searching for Native Ethernet Services

This section describes how to synchronize Native Ethernet services from the NE layer of the
network management system (NMS) to the network layer of the NMS.
Prerequisites
l Native Ethernet service data has been correctly configured for the NE.
l Data is synchronous between the NE and NMS.

U2000
NOTE
Precautions
This task synchronizes Native Ethernet services that have not yet been synchronized to the
network layer topology of the NMS. For Native Ethernet services that have been synchronized
to the network layer topology of the NMS, skip this task and manage the services by referring
to A.10.8 Managing Native Ethernet Services.

Context
The procedure described in this section synchronizes the Native Ethernet line (E-Line) and
Native Ethernet local area network (E-LAN) services of a specified search area to the network
layer of the NMS.
Procedure
Step 1
----End
A.10.2 Creating a Point-to-Point Transparently Transmitted E-Line

Service
This section describes how to create a point-to-point transparently transmitted Ethernet line (E-
Line) service in end-to-end mode.
Prerequisites
l Port attributes have been configured for each board on an NE.
l Fiber connections for Ethernet links between NEs have been created on Main Topology.
l Data is synchronous between the NE and network management system (NMS).

U2000
NOTE
Context
The procedure described in this section creates a point-to-point transparently transmitted E-Line
service according to the planned parameter values listed in the following table.

Parameter Value
Service Name E-Line-001
BPDU Private Service No
Customer Customer1
Source port 1-SHUF3-2(PORT-2)
Sink NE NE(9–22142)
Sink port 1-SHUF3-2(PORT-2)
Procedure
Step 1
----End
A.10.3 Creating a VLAN-based E-Line Service

This section describes how to create a VLAN-based Ethernet line (E-Line) service in end-to-
end mode.
Prerequisites

U2000

NOTE
Context
The procedure described in this section creates a VLAN-based E-Line service according to the
Parameter Value
Customer Customer1
C-VLAN of the source port 100
C-VLAN of the sink port 100
Procedure
Step 1
----End
A.10.4 Creating a QinQ-based E-Line Service

This section describes how to create a QinQ-based Ethernet line (E-Line) service in end-to-end
mode.

Prerequisites

U2000
NOTE
Context
The procedure described in this section creates a VLAN-based E-Line service according to the
Parameter Value
Customer Customer1
C-VLAN of the source port 100
S-VLAN of the source port 100
C-VLAN of the sink port 100
S-VLAN of the sink port 100
Procedure
Step 1

----End
A.10.5 Creating an IEEE 802.1D Bridge-based E-LAN Service

This section describes how to create an IEEE 802.1D bridge-based Ethernet local area network
(E-LAN) service in end-to-end mode.
Prerequisites
l Port attributes have been correctly configured for each board on an NE.

U2000
NOTE
Context
The procedure described in this section creates an IEEE 802.1D bridge-based E-LAN service
Table A-7 Basic parameters for an IEEE 802.1D bridge-based E-LAN service
Parameter Value
Service Type E-LAN
Service Name E-LAN-00001
Customer customer_01
Tag Type Tag-Transparent

Table A-8 Information about ports mounted to network bridges

Par Value
am
eter NE(200-121) NE(200-19) NE(200-124) NE(200-20)
1- 1- 1- 1- 1- 1- 1- 1- 1- 1- 1- 1-
SH SH SH SH SH SH SH SH SH SH SH SH
UF3 UF3 UF3 UF3 UF3 UF3 UF3 UF3 UF3 UF3 UF3 UF3
-1 -2 -3 -1 -2 -3 -1 -2 -3 -1 -2 -3
(IF (PO (PO (IF (PO (PO (IF (PO (PO (IF (PO (PO
E-1) RT- RT- E-1) RT- RT- E-1) RT- RT- E-1) RT- RT-
2) 3) 2) 3) 2) 3) 2) 3)
Ena - Ena Ena - Ena Ena - Ena Ena - Ena Ena

ble bled bled bled bled bled bled bled bled
Port
Wor - Aut Aut - Aut Aut - Aut Aut - Aut Aut

king o- o- o- o- o- o- o- o-
Mo Neg Neg Neg Neg Neg Neg Neg Neg
de otiat otiat otiat otiat otiat otiat otiat otiat
ion ion ion ion ion ion ion ion
Loo Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena
pba bled bled bled bled bled bled bled bled bled bled bled bled
ck
Che
ck
Bro Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena
adca bled bled bled bled bled bled bled bled bled bled bled bled
st
Pac
ket
Sup
pres
sion
Bro 30 30 30 30 30 30 30 30 30 30 30 30
adca
st
Pac
ket
Sup
pres
sion
Thr
esho
ld
(%)

Procedure
Step 1
----End
A.10.6 Creating an IEEE 802.1Q Bridge-based E-LAN Service

This section describes how to create an IEEE 802.1Q bridge-based Ethernet local area network
(E-LAN) service in end-to-end mode.
Prerequisites
l Port attributes have been correctly configured for each board on an NE.

U2000
NOTE
Context
The procedure described in this section creates an IEEE 802.1Q bridge-based E-LAN service
Table A-9 Basic parameters for an IEEE 802.1Q bridge-based E-LAN service
Parameter Value
Service Type E-LAN
Service Name E-LAN-00001

Parameter Value
Customer customer_02
Tag Type C-Aware
Table A-10 Information about ports mounted to network bridges

Par Value
am
eter NE(200-121) NE(200-19) NE(200-124) NE(200-20)
1- 1- 1- 1- 1- 1- 1- 1- 1- 1- 1- 1-
-1 -2 -3 -1 -2 -3 -1 -2 -3 -1 -2 -3
2) 3) 2) 3) 2) 3) 2) 3)
Ena - Ena Ena - Ena Ena - Ena Ena - Ena Ena

ble bled bled bled bled bled bled bled bled
Port
Wor - Aut Aut - Aut Aut - Aut Aut - Aut Aut

king o- o- o- o- o- o- o- o-
Mo Neg Neg Neg Neg Neg Neg Neg Neg
de otiat otiat otiat otiat otiat otiat otiat otiat
ion ion ion ion ion ion ion ion
Loo Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena
pba bled bled bled bled bled bled bled bled bled bled bled bled
ck
Che
ck
Bro Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena Ena
adca bled bled bled bled bled bled bled bled bled bled bled bled
st
Pac
ket
Sup
pres
sion

Par Value
am
eter NE(200-121) NE(200-19) NE(200-124) NE(200-20)
1- 1- 1- 1- 1- 1- 1- 1- 1- 1- 1- 1-
-1 -2 -3 -1 -2 -3 -1 -2 -3 -1 -2 -3
2) 3) 2) 3) 2) 3) 2) 3)
Bro 30 30 30 30 30 30 30 30 30 30 30 30
adca
st
Pac
ket
Sup
pres
sion
Thr
esho
ld
(%)
Procedure
Step 1
----End
A.10.7 Verifying a Native Ethernet Service

This section describes how to use ETH OAM to verify the connectivity of Native Ethernet
services.

Prerequisites
l Native Ethernet services are configured in end-to-end mode and ETH OAM CC has been
enabled.

U2000
NOTE
Context
The procedure described in this section aims to:
1. Verify Ethernet line (E-Line) services transmitted in Native Ethernet mode.
2. Verify Ethernet local area network (E-LAN) services transmitted in Native Ethernet mode.
Procedure
Step 1 Verify Ethernet line (E-Line) services transmitted in Native Ethernet mode.
Step 2 Verify Ethernet local area network (E-LAN) services transmitted in Native Ethernet mode.

----End
A.10.8 Managing Native Ethernet Services

This section describes how to manage a Native Ethernet service, such as deploying and deleting
a Native Ethernet service and querying information about the service.
Prerequisites

U2000
NOTE
Context
The procedure described in this section enables you to manage a Native Ethernet service.
Procedure
Step 1

----End
A.10.9 Managing Discrete Native Ethernet Services

This section describes how to manage discrete Native Ethernet services. Such services cannot
become network-layer services and exist only on isolated NEs.
Prerequisites

U2000
NOTE
Context
The procedure described in this section enables you to manage discrete Native Ethernet services.
Procedure
Step 1

----End
A.10.10 Adjusting an E-LAN Service Network

This section describes how to adjust an Ethernet local area network (E-LAN) service network
after E-LAN services are configured in end-to-end mode.
Prerequisites

U2000
NOTE
Context
The procedure described in this section adjusts an E-LAN service network.
Procedure
Step 1

----End
A.11 Verifying Services and Features

This chapter describes how to verify service and feature configurations.
A.11.1 Testing Ethernet Services

tester is required.
A.11.1.1 Testing Ethernet Services Configured on a Per NE Basis

To test Ethernet services configured on a per NE basis, you must create ETH OAM manually.
Prerequisites
NOTE

U2000

example, as shown in Figure A-2.

Figure A-2 Connection diagram for testing Ethernet services

NE 1 NE 2
GE 1 GE 1
NodeB
RNC
Procedure
Step 1 Test the Ethernet services between NE1 and NE2.
l If the value of LossRate in Result is 0, the test is successful.

l If the value of LossRate in Result is not 0, handle the problem based on the procedures in
Cause Handling Procedure
Connecting to the peer end fails within the Check whether services are interrupted.
specified period.
Packets are lost. Check whether the service traffic is higher

than the transmission bandwidth.
Check the link for bit errors.
----End

A.11.1.2 Testing Ethernet Services Configured in End-to-End Mode

The ETH OAM that is automatically created by services can be used to test Ethernet services
configured in end-to-end mode.
Prerequisites
NOTE

U2000
NOTE

example, as shown in Figure A-3.
Figure A-3 Connection diagram for testing Ethernet services

NE 1 NE 2
GE 1 GE 1
NodeB
RNC

1. Verifies Ethernet line (E-Line) services transmitted in Native Ethernet mode.
2. Verifies Ethernet local area network (E-LAN) services transmitted in Native Ethernet
mode.
Procedure
Step 1 Verify E-Line services transmitted in Native Ethernet mode.

Step 2 Verify E-LAN services transmitted in Native Ethernet mode.
----End
A.11.2 Testing AMAC Shifting

Prerequisites
l The adaptive modulation (AMAC) function has been enabled for the microwave link to be
tested.

Web LCT
NOTE

Context
The following procedure tests the AMAC shifting function on an NE.
Procedure
Step 1 Set the AMAC attributes.
Step 2 Test one-click AMAC shifting.
----End
A.11.3 Testing Protection Switching

A.11.3.1 Testing ERPS Switching

You can verify the Ethernet ring protection switching (ERPS) function by checking the port
status of the ERPS protection group before and after switching.

Prerequisites
l ERPS has been configured for OptiX RTN 380s on a ring network.
l Ethernet links on the ring network are connected correctly.

U2000
NOTE
Context
The following procedure queries the port status change on the ring protection link (RPL) owner
node in an ERPS protection group before and after switching to check whether the ERPS function
is running properly.

In Figure A-4, the Ethernet services between NE 1 and NE 6 are protected by ERPS, and NE 1
is the RPL owner node.
Figure A-4 Configuration for testing ERPS

NE 4 NE 3
E: IF E: GE (GE2)
W: GE (GE2) W: IF
NE 5 NE 2
E: GE (GE2) E: IF
W: IF W: GE (GE2)
NE 6 NE 1
E: IF E: GE (GE2)
W: GE (GE2) NE 7 NE 8
E: GE (GE2) E: IF W: IF
W: IF W: GE (GE2) RPL owner
Ethernet cable
Blocked port

Procedure
Step 1 Before switching, query the status of the ERPS protection group that is configured on NE 1.
Step 3 Set TX Status to mute for NE 6.
Step 4 After switching, query the status of the ERPS protection group that is configured on NE 1.

Step 6 Set TX Status to unmute for NE 6.
----End
A.11.3.2 Testing 1+1 Protection Switching

You can verify the 1+1 protection functions by checking the changes of the main and standby
devices before and after switching.
Prerequisites
l Ethernet services and 1+1 protection have been configured.
l Static link aggregation groups (LAGs) have been configured for third-party devices,when
the devices are connected without optical splitters.

U2000

Figure A-5 Test connection diagram
When the optical splitters are not used ,the basic configurations are as follows:
l Main OptiX RTN 380s: NE 11 and NE 12
l Standby OptiX RTN 380s: NE 21 and NE 22
LAG NE 11 NE 12 LAG
LAG LAG
COMBO COMBO
Antenna Antenna
NE 21 NE 22
LAG LAG
E-LAG E-LAG
OptiX RTN 900 Microwave link
Ethernet link Optical fiber
The Ethernet services protected by 1+1 hot standby (HSB) between NE 11 and NE 12 shown in
Figure A-5 are tested.
The same testing way can be used for the topology with optical splitters.
Procedure
Step 1 Configure Reversion Mode for the 1+1 HSB protection group on NE 11.
2. In Protection Group, select the desired protection group and set Reversion Mode to Non-
Revertive.
3. Click Apply.
4. Click Close.
Step 2 Query the protection group status on NE 11 before switching.

Step 3 Test availability of the tested Ethernet services before switching. For details, see 6.2 Testing
Ethernet Services. The value of LossRate in Test Result should be 0.
Step 4 Cold reset NE 11.

1. Optional: Double-click the subnet to which NE 11 belongs.

2. Double-click NE 11 in Main Topology.

The NE panel is displayed.
3. Select the SHUF3 board, right-click, and choose Cold Reset from the shortcut menu.
The Warning dialog box is displayed.
4. Click OK.
Step 5 After NE 11 is cold reset (which takes about 3 minutes), query the protection group status on
NE 11.
Step 6 Test availability of the tested Ethernet services after switching. For details, see 6.2 Testing
Ethernet Services. The value of LossRate in Test Result should be 0, indicating that the 1+1
protection switching is successful.
Step 7 Restore Reversion Mode to the original value.
----End

Commissioning and Configuration Guide B Glossary
B Glossary
Numerics
3G See 3rd Generation.
3rd Generation (3G) The third generation of digital wireless technology, as defined by the International
Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to
19.2 kbit/s offered by second generation technology.
A
ABR See area border router.
ACAP See adjacent channel alternate polarization.
ACL See access control list.
AF See assured forwarding.
AIS alarm indication signal
AM See adaptive modulation.
ARP See Address Resolution Protocol.
ASBR See autonomous system boundary router.
ATPC See automatic transmit power control.
Address Resolution An Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and
Protocol (ARP) routers to determine the link layer addresses through ARP requests and ARP responses.
access control list A list of entities, together with their access rights, which are authorized to have access
(ACL) to a resource.
adaptive modulation A technology that is used to automatically adjust the modulation mode according to the
(AM) channel quality. When the channel quality is favorable, the equipment uses a high-
efficiency modulation mode to improve the transmission efficiency and the spectrum
utilization of the system. When the channel quality is degraded, the equipment uses the
low-efficiency modulation mode to improve the anti-interference capability of the link
that carries high-priority services.

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.
(ACAP)
air interface The interface between the cellular phone set or wireless modem (usually portable or
mobile) and the active base station.
alarm suppression An alarm management method. Alarms that are set to be suppressed are not reported
from NEs any more.
area border router A router that can belong to more than two areas of which one area must be a backbone
(ABR) area.
assured forwarding One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.
(AF) It is suitable for certain key data services that require assured bandwidth and short delay.
For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that
exceeds the bandwidth limit, AF degrades the service class and continues to forward the
traffic instead of discarding the packets.
automatic transmit A method of adjusting the transmit power based on fading of the transmit signal detected
power control (ATPC) at the receiver
autonomous system A router that exchanges routing information with other ASs.
boundary router
(ASBR)
B
BE See best effort.
BIOS See basic input/output system.
backup A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
baseband A form of modulation in which the information is applied directly onto the physical
transmission medium.
basic input/output A firmware stored in the computer mainboard. It contains basic input/output control
system (BIOS) programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
best effort (BE) A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of the
network and routers. The amount of resource that a diagram can use depends of the time
it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss
ratio, and high reliability.
blacklist A method of filtering packets based on their source IP addresses. Compared with ACL,
the match condition for the black list is much simpler. Therefore, the black list can filter
packets at a higher speed and can effectively screen the packet sent from the specific IP
address.

bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ from repeaters because bridges store
and forward complete packets, while repeaters forward all electrical signals. Bridges
differ from routers because bridges use physical addresses, while routers use IP
addresses.
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
burst A process of forming data into a block of the proper size, uninterruptedly sending the
block in a fast operation, waiting for a long time, and preparing for the next fast sending.
C
CC See continuity check.
CCDP See co-channel dual polarization.
CSES consecutive severely errored second
CSMA/CD See carrier sense multiple access with collision detection.
carrier sense multiple Carrier sense multiple access with collision detection (CSMA/CD) is a computer
access with collision networking access method in which:
detection (CSMA/CD)
l A carrier sensing scheme is used.
l A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
chain network One type of network that all network nodes are connected one after one to be in series.
channel spacing The center-to-center difference in frequency or wavelength between adjacent channels
in a WDM device.
co-channel dual A channel configuration method, which uses a horizontal polarization wave and a vertical
polarization (CCDP) polarization wave to transmit two signals. The Co-Channel Dual Polarization has twice
the transmission capacity of the single polarization.
congestion A flow control measure to solve the problem of network resource competition. When
management the network congestion occurs, it places packets into the queue for buffer and determines
the packet forwarding order.
continuity check (CC) Ethernet CFM can detect the connectivity between MEPs. The detection is achieved after
MEPs transmit Continuity Check Messages (CCMs) periodically.
D
DCC See data communications channel.
DCN See data communication network.
DD database description
DM See delay measurement.
DRDB dynamic random database
DS data service
DSCP differentiated services code point

data communication A communication network used in a TMN or between TMNs to support the data
network (DCN) communication function.
data communications The data channel that uses the D1–D12 bytes in the overhead of an STM-N signal to
channel (DCC) transmit information about operation, management, maintenance and provision
(OAM&P) between NEs. The DCC channels that are composed of bytes D1–D3 are
referred to as the 192 kbit/s DCC-R channel. The other DCC channels that are composed
of bytes D4–D12 are referred to as the 576 kbit/s DCC-M channel.
delay measurement The time elapsed since the start of transmission of the first bit of the frame by a source
(DM) node until the reception of the last bit of the loopbacked frame by the same source node,
when the loopback is performed at the frame's destination node.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves
orthogonally polarized.
E
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
E1 An European standard for high-speed data transmission at 2.048 Mbit/s. It provides
thirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32
timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization, and
timeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use as speech
channels. Each timeslot sends or receives an 8-bit data per second. Each frame sends or
receives 256-bit data per second. 8000 frames will be sent or received per second.
Therefore the line data rate is 2.048 Mbit/s.
ECC See embedded control channel.
EF See expedited forwarding.
EMC See electromagnetic compatibility.
ERPS Ethernet ring protection switching
ES errored second
ESD electrostatic discharge
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet local area A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
network (E-LAN) virtual connection).
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute
(ETSI)
electromagnetic A condition which prevails when telecommunications equipment is performing its
compatibility (EMC) 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.

embedded control A logical channel that uses a data communications channel (DCC) as its physical layer,
channel (ECC) to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
(EF) demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF
traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP
value of EF PHB is "101110".
extended ID The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The physical ID of an NE is comprised of the NE ID and extended
ID.
extended NE ID The serial number of a subnetwork where an NE resides, which is usually used to
distinguish different network segments. An extended ID and an ID form the physical ID
of an NE.
F
FE See fast Ethernet.
FEC See forward error correction.
FIFO See first in first out.
FPGA See field programmable gate array.
FTP File Transfer Protocol
fast Ethernet (FE) Any network that supports transmission rate of 100 Mbit/s. The Fast Ethernet is 10 times
faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so
on. Fast Ethernet is extended based on the IEEE802.3 standard, and it uses the following
three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),
100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical
fibers).
field programmable A type of semi-customized circuit used in the application specific integrated circuit
gate array (FPGA) (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 arrays.
first in first out (FIFO) A stack management mechanism. The first saved data is first read and invoked.
flooding A type of incident, such as insertion of a large volume of data, that results in denial of
service.
forward error A bit error correction technology that adds the correction information to the payload at
correction (FEC) the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
G
GE See gigabit Ethernet.
GNE See gateway network element.
gateway A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.

gateway network A network element that is used for communication between the NE application layer and
element (GNE) the NM application layer.
gigabit Ethernet (GE) A collection of technologies for transmitting Ethernet frames at a rate of a gigabit per
second, as defined by the IEEE 802.3z standard. GE is compatible with 10 Mbit/s and
100 Mbit/s Ethernet. It runs at 1000 Mbit/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.
H
HSDPA See High Speed Downlink Packet Access.
HUAWEI Electronic The software used to view, search for, and upgrade electronic documentation of Huawei
Document Explorer products. HedEx, pronounced as [hediks], has two editions, HedEx Lite and HedEx
(HedEx) Server.
HedEx See HUAWEI Electronic Document Explorer.
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement
Packet Access for asymmetric uplink and downlink transmission of data services. It enables the
(HSDPA) maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
I
ICMP See Internet Control Message Protocol.
IDU See indoor unit.
IEEE See Institute of Electrical and Electronics Engineers.
IETF See Internet Engineering Task Force.
IP Internet Protocol
IP address A 32-bit (4-byte) binary digit that uniquely identifies a host (computer) connected to the
Internet for communication with other hosts in the Internet by transferring packets. An
IP address is expressed in dotted decimal notation, consisting of decimal values of its 4
bytes, separated by periods (.), for example, 127.0.0.1. The first three bytes of an IP
address identify the network to which the host is connected, and the last byte identifies
the host itself.
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
ISO International Organization for Standardization
ITU See International Telecommunication Union.
ITU-T See International Telecommunication Union-Telecommunication Standardization
Sector.

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 (IEEE) electronics, computer engineering, and science-related matters.
International A United Nations agency, one of the most important and influential recommendation
Telecommunication bodies, responsible for recommending standards for telecommunication (ITU-T) and
Union (ITU) radio networks (ITU-R).
International An international body that develops worldwide standards for telecommunications
Telecommunication technologies. These standards are grouped together in series which are prefixed with a
Union- letter indicating the general subject and a number specifying the particular standard. For
Telecommunication example, X.25 comes from the "X" series which deals with data networks and open
Standardization Sector system communications and number "25" deals with packet switched networks.
(ITU-T)
Internet Control A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and
Message Protocol other information relevant to IP packet processing. For example, it can let the IP software
(ICMP) on one machine inform another machine about an unreachable destination. See also
communications protocol, IP, ISO/OSI reference model, packet (definition 1).
Internet Engineering A worldwide organization of individuals interested in networking and the Internet.
Task Force (IETF) Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with
studying technical problems facing the Internet and proposing solutions to the Internet
Architecture Board (IAB). The work of the IETF is carried out by various working groups
that concentrate on specific topics such as routing and security. The IETF is the publisher
of the specifications that led to the TCP/IP protocol standard.
Internet Protocol The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
version 4 (IPv4) assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers together
are used for routing, and the host number is used to address an individual host within the
network or subnetwork.
Internet Protocol An update version of IPv4, which is designed by the Internet Engineering Task Force
version 6 (IPv6) (IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
J
jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
L
L2VPN Layer 2 virtual private network
LACP See Link Aggregation Control Protocol.
LAG See link aggregation group.
LAN See local area network.

LB See loopback.
LBM See loopback message.
LBR See loopback reply.
LCT local craft terminal
LM See loss measurement.
LOS See loss of signal.
LSA link-state advertisement
LSDB link state database
LT linktrace
LTM See linktrace message.
LTR See linktrace reply.
Layer 2 switching A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch
transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switching.
Link Aggregation A dynamic link aggregation protocol that improves the transmission speed and
Control Protocol reliability. The two ends of the link send LACP packets to inform each other of their
(LACP) parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
(LAG) aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
linktrace message The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP.
(LTM) LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.
linktrace reply (LTR) For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called LTR. LTR also includes the TTL that equals the result of the TTL of LTM minus
1.
local area network A network formed by the computers and workstations within the coverage of a few square
(LAN) 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 (LB) A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loopback message The loopback packet sent by the node that supports 802.2ag MAC Ping to the destination
(LBM) node. LBM message carries its own sending time.
loopback reply (LBR) A response message involved in the 802.2ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the LBM.
The LBR carries the sending time of LBM, the receiving time of LBM and the sending
time of LBR.

loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frames
where the counters maintain a count of transmitted and received data frames between a
pair of MEPs.
loss of signal (LOS) No transitions occurring in the received signal.
M
MA maintenance association
MAC See Media Access Control.
MAC address A link layer address or physical address. It is six bytes long.
MD See maintenance domain.
MDI medium dependent interface
ME maintenance entity
MEP maintenance end point
MIB See management information base.
MIP maintenance intermediate point
MP maintenance point
MPLS See Multiprotocol Label Switching.
MSTP See Multiple Spanning Tree Protocol.
MTBF See mean time between failures.
MTTR See mean time to repair.
MTU See maximum transmission unit.
Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of the
(MAC) data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
Tree Protocol (MSTP) 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.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different link
Switching (MPLS) layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.

maintenance domain The network or the part of the network for which connectivity is managed by connectivity
(MD) fault management (CFM). The devices in a maintenance domain are managed by a single
Internet service provider (ISP).
management A type of database used for managing the devices in a communications network. It
information base (MIB) comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies,
unit (MTU) depending on the network—576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
mean time between The average time between consecutive failures of a piece of equipment. It is a measure
failures (MTBF) of the reliability of the system.
mean time to repair The average time that a device will take to recover from a failure.
(MTTR)
microwave The portion of the electromagnetic spectrum with much longer wavelengths than infrared
radiation, typically above about 1 mm.
multicast A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
N
NAS network access server
NE network element
NE Explorer The main operation interface, of the network management system, which is used to
manage the telecommunication equipment. In the NE Explorer, the user can query,
manage and maintain the NE, boards, and ports on a per-NE basis.
NTP Network Time Protocol
network segment A part of an Ethernet or other network, on which all message traffic is common to all
nodes, that is, it is broadcast from one node on the segment and received by all others.
network storm A phenomenon that occurs during data communication. To be specific, mass broadcast
packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by network
connection or configuration problems.
O
OAM See operation, administration and maintenance.
ODF optical distribution frame
ODU See outdoor unit.
OSI See open systems interconnection.

OSPF See Open Shortest Path First.

Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
First (OSPF) algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed with the network topology which is identical on all
routers in the area.
open systems A framework of ISO standards for communication between different systems made by
interconnection (OSI) different vendors, in which the communications process is organized into seven different
categories that are placed in a layered sequence based on their relationship to the user.
Each layer uses the layer immediately below it and provides a service to the layer above.
Layers 7 through 4 deal with end-to-end communication between the message source
and destination, and layers 3 through 1 deal with network functions.
operation, A group of network support functions that monitor and sustain segment operation,
administration and support activities that are concerned with, but not limited to, failure detection,
maintenance (OAM) notification, location, and repairs that are intended to eliminate faults and keep a segment
in an operational state, and support activities required to provide the services of a
subscriber access network to users/subscribers.
outdoor unit (ODU) The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for radio frequency (RF) signals.
P
P2P See point-to-point service.
PBS See peak burst size.
PDU protocol data unit
PHB See per-hop behavior.
PLL See phase-locked loop.
PPP Point-to-Point Protocol
PPPoE Point-to-Point Protocol over Ethernet
PRBS See pseudo random binary sequence.
PSN See packet switched network.
PTP Precision Time Protocol
packet loss The discarding of data packets in a network when a device is overloaded and cannot
accept any incoming data at a given moment.
packet switched A telecommunications network that works in packet switching mode.
network (PSN)
peak burst size (PBS) A parameter that is used to define the capacity of token bucket P, that is, the maximum
burst IP packet size when the information is transferred at the peak information rate. This
parameter must be larger than 0. It is recommended that PBS should be not less than the
maximum length of the IP packet that might be forwarded. See also CIR, CBS, and PIR.
per-hop behavior IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
(PHB) behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).

phase-locked loop A circuit that consists essentially of a phase detector which compares the frequency of
(PLL) a voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency generator; the output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
physical layer Layer 1 in the Open System Interconnection (OSI) architecture; the layer that provides
services to transmit bits or groups of bits over a transmission link between open systems
and which entails electrical, mechanical and handshaking.
point-to-point service A service between two terminal users. In P2P services, senders and recipients are
(P2P) terminal users.
polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
policy A set of rules that are applied when the conditions for triggering an event are met.
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the
sequence (PRBS) values of any of the other elements, similar to real random sequences.
Q
QPSK See quadrature phase shift keying.
QoS See quality of service.
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying (QPSK) the phase determination of the reference signals (carrier). It is also called the fourth period
or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are
evenly distributed on a circle. On these phases, each QPSK character can perform two-
bit coding and display the codes in Gray code on graph with the minimum BER.
quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS See Remote Authentication Dial-In User Service.
RADIUS An authentication mode in which the BRAS sends the user name and the password to
authentication the RADIUS server by using the RADIUS protocol. The RADIUS server authenticates
the user, and then returns the result to the BRAS.
RDI remote defect indication
RED See random early detection.
RF See radio frequency.
RFC See Request For Comments.

RMON remote network monitoring

RNC See radio network controller.
RSL See received signal level.
RSSI See received signal strength indicator.
RTN radio transmission node
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial-In User Service access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
(RADIUS) transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
Request For Comments A document in which a standard, a protocol, or other information pertaining to the
(RFC) operation of the Internet is published. The RFC is actually issued, under the control of
the IAB, after discussion and serves as the standard. RFCs can be obtained from sources
such as InterNIC.
radio frequency (RF) A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
radio network A piece of equipment in the RNS which is in charge of controlling the use and the integrity
controller (RNC) of the radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
(RED) to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulting from traditional tail drop can be prevented.
received signal level The signal level at a receiver input terminal.
(RSL)
received signal strength The received wide band power, including thermal noise and noise generated in the
indicator (RSSI) receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
receiver sensitivity The minimum acceptable value of average received power at point R to achieve a 1 x
10-12 BER (The FEC is open).
route The path that network traffic takes from its source to its destination. In a TCP/IP network,
each IP packet is routed independently. Routes can change dynamically.
routing table A mapping table that stores the relationship between the original address, destination
address, SMS protocol type, and account. The SMSC delivers an SMS message to the
designated account according to the information in the routing table.
S
SD See signal degrade.
SF See signal fail.
SFP small form-factor pluggable
SNMP See Simple Network Management Protocol.
SNR See signal-to-noise ratio.

SPF shortest path first

SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
Secure Sockets Layer A security protocol that works at a socket level. This layer exists between the TCP layer
(SSL) and the application layer to encrypt/decode data and authenticate concerned entities.
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
(SNMP) transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Message (SSM) Nodes on an SDH network and a synchronization network acquire upstream clock
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.
service flow An MAC-layer-based unidirectional transmission service. It is used to transmit data
packets, and is characterized by a set of QoS parameters, such as latency, jitter, and
throughput.
shaping A process of delaying packets within a traffic stream to cause it to conform to specific
defined traffic profile.
signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded defect
condition is active.
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
(SNR) given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB (Decibel).
single-polarized An antenna intended to radiate or receive radio waves with only one specified
antenna polarization.
subnet mask The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the device and is matched
with the IP address.
T
TCP/IP Transmission Control Protocol/Internet Protocol
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
Time Division- A 3G mobile communications standard found in UMTS mobile telecommunications
Synchronous Code networks in China as an alternative to W-CDMA. TD-SCDMA integrates technologies
Division Multiple of CDMA, TDMA, and FDMA, and makes use of technologies including intelligent
Access (TD-SCDMA) antenna, joint detection, low chip rate (LCR), and adaptive power control. With the
flexibility of service processing, a TD-SCDMA network can connect to other networks
through the RNC.

tail drop A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
tolerance Permissible degree of variation from a pre-set standard.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the entire
network. In this way, different traffic packets can be treated differently.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in the
scenario that the traffic matches network resources provided by the lower layer devices,
avoiding packet loss and congestion.
U
UAS unavailable second
UAT See unavailable time event.
UDP See User Datagram Protocol.
UNI See user-to-network interface.
User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol (UDP) datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagram. UDP provides application programs with the unreliable
connectionless packet delivery service. There is a possibility that UDP messages will be
lost, duplicated, delayed, or delivered out of order. The destination device does not
confirm whether a data packet is received.
unavailable time event An event that is reported when the monitored object generates 10 consecutive severely
(UAT) errored seconds (SES) and the SESs begin to be included in the unavailable time. The
event will end when the bit error ratio per second is better than 10-3 within 10 consecutive
seconds.
unicast The process of sending data from a source to a single recipient.
user-to-network The interface between user equipment and private or public network equipment (for
interface (UNI) example, ATM switches).
V
VB virtual bridge
VLAN virtual local area network
VM virtual memory
W
WAN See wide area network.
WEEE waste electrical and electronic equipment
WRED See weighted random early detection.
WRR weighted round robin
WTR See wait to restore.

Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
detection (WRED) synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
wide area network A network composed of computers which are far away from each other which are
(WAN) physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
window General method for speech preprocessing, like Haming window.


RTN 380 V100R001C00 Commissioning and Configuration Guide 03 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RTN 380 V100R001C00 Commissioning and Configuration Guide 03 PDF

Uploaded by

Copyright:

Available Formats

OptiX RTN 380 Radio Transmission System

Commissioning and Configuration

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2013-04-25) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 380 V100R001C00

iManager U2000 V100R008C00

This document is intended for:

l Installation and commissioning engineers

Indicates a hazard with a high level of risk,

Indicates a hazard with a medium or low level

Issue 03 (2013-04-25) Huawei Proprietary and Confidential ii

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

Issue 03 (2013-04-25) Huawei Proprietary and Confidential iii

{ 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 ">"

- Fixed the known bugs.

- Fixed the known bugs.

8.6 Configuring Native Ethernet Services Added end-to-end configuration examples.

Issue 03 (2013-04-25) Huawei Proprietary and Confidential iv

Issue 03 (2013-04-25) Huawei Proprietary and Confidential v

About This Document.....................................................................................................................ii

4 Site Commissioning (Using a USB Flash Drive to Configure Data).................................31

Issue 03 (2013-04-25) Huawei Proprietary and Confidential vi

4.1.1 Powering on OptiX RTN 380 (with an Outdoor PI)...............................................................................33

5 Site Commissioning (Using the Web LCT to Configure Data)..........................................59

Issue 03 (2013-04-25) Huawei Proprietary and Confidential vii

6.4 Testing Protection Switching..........................................................................................................................100

7 Handling of Common Faults During Site Deployment....................................................114

8 Configuring Networkwide Service Data..............................................................................117

Issue 03 (2013-04-25) Huawei Proprietary and Confidential viii

8.5.1.1 AM and AMAC............................................................................................................................146

Issue 03 (2013-04-25) Huawei Proprietary and Confidential ix

8.6.4.5 Per-NE Configuration Process (QinQ-based E-Line Services)....................................................220

Issue 03 (2013-04-25) Huawei Proprietary and Confidential x

8.6.7.8 Procedure of Configuration on a Per-NE Basis (Service Information)........................................303

Issue 03 (2013-04-25) Huawei Proprietary and Confidential xi

8.7.3.3 Configuration Procedure...............................................................................................................363

Issue 03 (2013-04-25) Huawei Proprietary and Confidential xii

A.3.5.1 Creating a Subnet.........................................................................................................................402

Issue 03 (2013-04-25) Huawei Proprietary and Confidential xiii

A.4.7.2 Setting Types and Severities of Logs to Be Sent to Syslog Servers............................................441

Issue 03 (2013-04-25) Huawei Proprietary and Confidential xiv

A.7.3 Configuring Ethernet Services..............................................................................................................481

Issue 03 (2013-04-25) Huawei Proprietary and Confidential xv

A.7.8.1 Enabling OAM Auto-discovery...................................................................................................522

Issue 03 (2013-04-25) Huawei Proprietary and Confidential xvi

About This Chapter