RTN 320 V100R007C00 Commissioning and Configuration Guide 02

OptiX RTN 320 Radio Transmission System
V100R007C00
Commissioning and Configuration

Guide
Issue 02
Date 2016-11-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. 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 02 (2016-11-30) 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 320 V100R007C00
iManager U2000–T V200R016C50
iManager U2000–M V200R016C00
Intended Audience
This document describes how to commission OptiX RTN 320, 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 an imminently hazardous situation

which, if not avoided, will result in death or
serious injury.
Indicates a potentially hazardous situation

which, if not avoided, could result in death
or serious injury.
Issue 02 (2016-11-30) Huawei Proprietary and Confidential ii

Symbol Description

which, if not avoided, may result in minor
or moderate injury.

which, if not avoided, could result in
equipment damage, data loss, performance
deterioration, or unanticipated results.
NOTICE is used to address practices not
related to personal injury.
Calls attention to important information,

best practices and tips.
NOTE is used to address information not
related to personal injury, equipment
damage, and environment deterioration.
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.
Issue 02 (2016-11-30) Huawei Proprietary and Confidential iii

{ x | y | ... } Optional items are grouped in braces and separated by

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

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

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

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

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

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Updates in Issue 02 (2016-11-30) Based on Product Version V100R007C00

This document is the second release of the V100R007C00 version.
Change Description
— Fixed the known bugs.
Updates in Issue 01 (2016-04-30) Based on Product Version V100R007C00

This issue is the first release for the product version V100R007C00.
Issue 02 (2016-11-30) Huawei Proprietary and Confidential iv

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.........................................................................................................................................................................8
1.6.1 Safe Usage of Optical Fibers....................................................................................................................................... 8
1.6.2 Electromagnetic Exposure........................................................................................................................................... 9
1.6.3 Forbidden Areas.......................................................................................................................................................... 9
1.6.4 Laser............................................................................................................................................................................ 9
1.6.5 Microwave................................................................................................................................................................. 10
1.7 Working at Heights....................................................................................................................................................... 10
1.7.1 Hoisting Heavy Objects............................................................................................................................................. 11
1.7.2 Using Ladders............................................................................................................................................................12
1.8 Mechanical Safety........................................................................................................................................................ 14
1.9 Other Precautions......................................................................................................................................................... 15
2 Commissioning Preparations.................................................................................................... 17
2.1 Preparing Documents and Tools...................................................................................................................................18
2.2 Preparing Files for Authentication Using a USB Flash Drive and Hardening Security of Files on the USB Flash
Drive................................................................................................................................................................................... 19
2.3 Determining the Commissioning Method.................................................................................................................... 24
2.4 Checking Commissioning Conditions.......................................................................................................................... 25
2.4.1 Checking Site Commissioning Conditions................................................................................................................25
2.4.2 Checking System Commissioning Conditions.......................................................................................................... 25
3 Commissioning Process............................................................................................................. 27
3.1 Site Commissioning Process (Universal)..................................................................................................................... 28
3.2 Site Commissioning Procedure (with Cascade 1+1 Protection)...................................................................................29
3.3 Site Commissioning Procedure (XPIC Links with 1+1 Protection).............................................................................34
3.4 Site Commissioning Process (MIMO)......................................................................................................................... 38
3.5 System Commissioning Process................................................................................................................................... 42
Issue 02 (2016-11-30) Huawei Proprietary and Confidential v

4 Site Commissioning (Using a USB Flash Drive to Configure Data)................................. 44

4.1 Powering On OptiX RTN 320...................................................................................................................................... 45
4.1.1 Powering on OptiX RTN 320 (with a PI).................................................................................................................. 45
4.1.2 Powering on OptiX RTN 320 (with a DC Power Supply).........................................................................................48
4.2 Loading Commissioning Data Using a USB Flash Drive............................................................................................ 49
4.3 Using the Web LCT to Complete Subsequent Commissioning Items..........................................................................51
5 Site Commissioning (Using the Web LCT to Configure Data).......................................... 53

5.1 Powering On OptiX RTN 320...................................................................................................................................... 55
5.1.1 Powering on OptiX RTN 320 (with a DC Power Supply).........................................................................................55
5.1.2 Powering on OptiX RTN 320 (with a PI).................................................................................................................. 57
5.2 Connecting the Web LCT to the Equipment.................................................................................................................60
5.3 Creating NEs Using the Search Method.......................................................................................................................64
5.4 Delivering a Commissioning Data Script to an NE Using the Web LCT.................................................................... 66
5.5 Configuring Site Commissioning Data.........................................................................................................................67
5.5.1 Changing an NE ID................................................................................................................................................... 68
5.5.2 Changing an NE Name.............................................................................................................................................. 69
5.5.3 Setting the VLAN ID and Bandwidth for an Inband DCN....................................................................................... 69
5.5.4 Releasing the QoS Policy Bound to an Interface...................................................................................................... 70
5.5.5 Creating a LAG......................................................................................................................................................... 71
5.5.6 Configuring a Single Hop of Microwave Link..........................................................................................................72
5.5.7 Synchronizing Data on Active and Standby NEs in a 1+1 Protection Group........................................................... 74
5.5.8 Testing the XPI Value................................................................................................................................................ 74
5.6 Checking Alarms.......................................................................................................................................................... 75
5.7 Aligning Antennas........................................................................................................................................................ 76
5.7.1 Main Lobe and Side Lobes........................................................................................................................................ 77
5.7.2 Aligning Single-Polarized Antennas......................................................................................................................... 79
5.7.3 Aligning Dual-Polarized Antennas (XPIC Links).....................................................................................................83
5.7.4 Aligning Dual-Polarized Antennas (Inter-NE MIMO)..............................................................................................86
5.8 Checking the Microwave Link Status and Receive Power...........................................................................................88
5.9 Configuring MIMO Links............................................................................................................................................ 89
6 System Commissioning..............................................................................................................91
6.1 Configuring Network-wide Service Data..................................................................................................................... 92
6.2 Testing Ethernet Services............................................................................................................................................. 92
6.2.1 Testing Ethernet Services Configured on a Per NE Basis......................................................................................... 92
6.2.2 Testing Ethernet Services Configured in End-to-End Mode..................................................................................... 95
6.3 Testing AM Shifting..................................................................................................................................................... 97
6.4 Testing ATPC................................................................................................................................................................98
6.5 Testing Protection Switching........................................................................................................................................99
6.5.1 Testing ERPS Switching............................................................................................................................................99
6.5.2 Testing 1+1 Protection Switching (Intra-equipment 1+1 Protection)..................................................................... 102
6.5.3 Testing 1+1 Protection Switching (Cascade 1+1 Protection).................................................................................. 103
6.5.4 Testing MPLS APS Protection Switching............................................................................................................... 105
Issue 02 (2016-11-30) Huawei Proprietary and Confidential vi

6.6 Checking the Clock Status..........................................................................................................................................108

6.7 Testing the Fade Margin over a Microwave Link.......................................................................................................109
6.8 Testing Ethernet Service Performance........................................................................................................................111
6.8.1 Testing Ethernet Service Performance (Based on RFC 2544).................................................................................111
6.8.2 Testing the Latency, Throughput, and Packet Loss Ratio........................................................................................113
6.8.3 Testing the Long-term Packet Loss Ratio................................................................................................................117
7 Handling of Common Faults During Site Deployment.................................................... 121

7.1 Handling a Fault in Commissioning Script Loading Using a USB Flash Drive........................................................ 122
7.2 Handling the Failure of the Receive Power to Meet the Design Requirements......................................................... 123
8 Configuring Networkwide Service Data.............................................................................. 124

8.1 Configuration Preparations.........................................................................................................................................125
8.1.1 Preparing Documents and Tools..............................................................................................................................125
8.1.2 Checking Configuration Conditions........................................................................................................................ 125
8.1.3 U2000 Quick Start................................................................................................................................................... 125
8.1.3.1 Logging In to a U2000 Client...............................................................................................................................126
8.1.3.2 Shutting Down a U2000 Client............................................................................................................................ 126
8.1.3.3 Using the Help...................................................................................................................................................... 127
8.1.3.4 Navigating to Common Views..............................................................................................................................128
8.1.3.4.1 Navigating to Main Topology............................................................................................................................128
8.1.3.4.2 Navigating to NE Explorer................................................................................................................................ 129
8.1.3.4.3 Navigating to the NE Panel............................................................................................................................... 130
8.2 General Configuration Process................................................................................................................................... 130
8.3 Common Network Scenarios of Configuration Examples......................................................................................... 132
8.3.1 Overview................................................................................................................................................................. 132
8.3.2 Microwave Chain Network..................................................................................................................................... 133
8.3.3 Microwave Ring Network....................................................................................................................................... 134
8.3.4 PTP Large Capacity Microwave Transmission Scenario........................................................................................ 135
8.3.5 Microwave 1+1 Protection Scenario....................................................................................................................... 136
8.3.6 NE Cascading Transmission Scenario.....................................................................................................................136
8.4 Configuring the Network Topology............................................................................................................................137
8.4.1 Basic Concepts........................................................................................................................................................ 137
8.4.1.1 Introduction to DCN............................................................................................................................................. 138
8.4.1.2 IP DCN................................................................................................................................................................. 142
8.4.1.3 Fiber/Cable Types.................................................................................................................................................147
8.4.1.4 Logical Boards......................................................................................................................................................147
8.4.2 Configuration Process (Network Topology)............................................................................................................147
8.4.3 Configuration Example (Network Topology)..........................................................................................................150
8.4.3.1 Networking Diagram............................................................................................................................................ 150
8.4.3.2 Configuration Procedure.......................................................................................................................................151
8.5 Configuring Microwave Links................................................................................................................................... 156
8.5.1 Configuration Process (Microwave Links)..............................................................................................................156
8.5.2 Configuration Example (Microwave Links on a Chain Network).......................................................................... 161
Issue 02 (2016-11-30) Huawei Proprietary and Confidential vii


8.5.3 Configuration Example (Microwave Links with 1+1 Protection)...........................................................................164
8.5.4 Configuration Example ( XPIC Microwave links with PLA protection)................................................................ 167
8.5.5 Configuration Example (4 x 4 MIMO Microwave Links)...................................................................................... 170
8.5.6 Configuration Example (XPIC Links with 1+1 Protection)....................................................................................172
8.5.7 Configuration Example (Cascade EPLA)................................................................................................................178
8.6 Configuring Ethernet Services ...................................................................................................................................181
8.6.1 Ethernet Service Ports............................................................................................................................................. 182
8.6.2 Ethernet Service Types............................................................................................................................................ 183
8.6.2.1 Transparently Transmitted Point-to-Point E-Line Service................................................................................... 184
8.6.2.2 VLAN-based E-Line Service................................................................................................................................185
8.6.2.3 QinQ-Based E-Line Services................................................................................................................................187
8.6.2.4 IEEE 802.1D Bridge-based E-LAN Services.......................................................................................................190
8.6.2.5 IEEE 802.1Q Bridge-based E-LAN Services.......................................................................................................191
8.6.2.6 802.1ad Bridge-based E-LAN Services................................................................................................................192
8.6.3 Configuration Process..............................................................................................................................................194
8.6.3.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point E-Line Services)............................. 195
8.6.3.2 End-to-End Configuration Process (Transparently Transmitted Point-to-Point E-Line Service)........................ 198
8.6.3.3 Per-NE Configuration Process (VLAN-based E-Line Services)..........................................................................200
8.6.3.4 End-to-End Configuration Process (VLAN-based E-Line Service).....................................................................203
8.6.3.5 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)...................................................205
8.6.3.6 End-to-End Configuration Process (IEEE 802.1D Bridge-Based E-LAN Service).............................................208
8.6.3.7 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)...................................................210
8.6.3.8 End-to-End Configuration Process (IEEE 802.1Q Bridge-based E-LAN Service)............................................. 213
8.6.4 Configuration Example (Transparently Transmitted Point-to-Point E-Line Services)........................................... 216
8.6.4.2 Procedure of Configuration on a Per-NE Basis (Service Information)................................................................ 217
8.6.4.3 Procedure of Configuration on a Per-NE Basis (QoS)......................................................................................... 218
8.6.4.4 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification)..................................................221
8.6.4.5 End-to-End Configuration Procedure (Configuring Service Information)...........................................................224
8.6.4.6 End-to-End Configuration Procedure (QoS)........................................................................................................ 225
Issue 02 (2016-11-30) Huawei Proprietary and Confidential viii

8.6.4.7 End-to-End Configuration Procedure (Verifying Service Configurations).......................................................... 227

8.6.5 Configuration Example (VLAN-based E-Line Services)........................................................................................228
8.6.5.5 End-to-End Configuration Procedure (Configuring Service Information)...........................................................237
8.6.6 Configuration Example (IEEE 802.1D Bridge-based E-LAN Service).................................................................. 242
8.6.6.2 Per-NE Configuration Procedure (Ethernet Protection)....................................................................................... 244
8.6.6.3 Per-NE Configuration Procedure (Service Information)...................................................................................... 245
8.6.6.4 Per-NE Configuration Procedure (QoS)............................................................................................................... 246
8.6.6.5 Per-NE Configuration Procedure (Ethernet Service Verification)........................................................................248
8.6.6.6 End-to-EndConfiguration Procedure (Ethernet Protection)................................................................................. 251
8.6.6.7 End-to-End Configuration Procedure (Service Information)............................................................................... 252
8.6.6.9 End-to-End Configuration Procedure (Ethernet Service Verification).................................................................255
8.6.7 Configuration Example (IEEE 802.1Q Bridge-based E-LAN Services).................................................................256
8.6.7.5 End-to-End Configuration Procedure (Service Information)............................................................................... 265
8.7 Configuring Clocks.....................................................................................................................................................270
8.7.1 Configuration Process (Configuring a Clock)......................................................................................................... 270
8.7.2 Configuration Example (Clock on a Microwave Chain Network)..........................................................................271
8.7.3 Configuration Example (Clock on a Microwave Ring Network)............................................................................275
8.7.4 Configuration Example (Clock on an NE Cascading Transmission Network)....................................................... 279
8.8 Common Service Configuration Operations.............................................................................................................. 282
8.8.1 Configuring the Network Topology.........................................................................................................................282
8.8.1.1 Creating an NE by Using the Search Method.......................................................................................................283
8.8.1.2 Creating an NE Manually..................................................................................................................................... 284
Issue 02 (2016-11-30) Huawei Proprietary and Confidential ix

8.8.1.3 Configuring Logical Interfaces.............................................................................................................................285

8.8.1.4 Changing an NE ID.............................................................................................................................................. 286
8.8.1.5 Changing an NE Name......................................................................................................................................... 287
8.8.1.6 Setting the VLAN ID and Bandwidth for an Inband DCN.................................................................................. 288
8.8.1.7 Configuring Access Control................................................................................................................................. 289
8.8.1.8 Creating a Fiber/Cable by Using the Search Method........................................................................................... 290
8.8.1.9 Creating a Fiber/Cable Manually......................................................................................................................... 291
8.8.2 Configuring Microwave Links................................................................................................................................ 292
8.8.2.1 Creating a Microwave 1+1 Protection Group.......................................................................................................293
8.8.2.2 Managing a Hop of Microwave Link................................................................................................................... 295
8.8.2.3 Synchronizing Data Between Main and Standby NEs (1+1)............................................................................... 297
8.8.2.4 Creating a PLA\EPLA Group...............................................................................................................................297
8.8.3 Configuring Ethernet Services on a Per-NE Basis.................................................................................................. 299
8.8.3.1 Creating a LAG.................................................................................................................................................... 300
8.8.3.2 Creating an ERPS Instance...................................................................................................................................303
8.8.3.3 Setting Protocol Parameters for an ERPS Instance.............................................................................................. 304
8.8.3.4 Creating a Point-to-Point Transparently Transmitted E-Line Service..................................................................304
8.8.3.5 Creating a VLAN-based E-Line Service.............................................................................................................. 306
8.8.3.6 Creating an IEEE 802.1D Bridge-based E-LAN Service.....................................................................................307
8.8.3.7 Creating an IEEE 802.1Q Bridge-based E-LAN Service.....................................................................................308
8.8.3.8 Changing Logical Ports Mounted to a Bridge...................................................................................................... 309
8.8.3.9 Deleting an E-Line Service...................................................................................................................................310
8.8.3.10 Deleting an E-LAN Service................................................................................................................................311
8.8.3.11 Modifying the Mapping for a DS Domain..........................................................................................................312
8.8.3.12 Changing the Packet Type Trusted by a Port......................................................................................................313
8.8.3.13 Enabling/Disabling DSCP Demapping at an Egress Port.................................................................................. 314
8.8.3.14 Setting Egress Queue Scheduling Policies......................................................................................................... 315
8.8.3.15 Releasing the QoS Policy Bound to an Interface............................................................................................... 316
8.8.3.16 Restoring an Ethernet Port Configured as an NMS Port to a Service Port........................................................ 317
8.8.4 Configuring Ethernet Services (in End-to-End Mode)............................................................................................318
8.8.4.1 Searching for Native Ethernet Services................................................................................................................318
8.8.4.2 Creating a Transparently Transmitted Point-to-Point E-Line Service..................................................................319
8.8.4.3 Creating a VLAN-based E-Line Service.............................................................................................................. 320
8.8.4.4 Creating an IEEE 802.1D Bridge-based E-LAN Service.....................................................................................322
8.8.4.5 Creating an IEEE 802.1Q Bridge-based E-LAN Service.....................................................................................323
8.8.5 Configuring Clocks..................................................................................................................................................324
8.8.5.1 Configuring the System Clock Source................................................................................................................. 325
8.8.5.2 Configuring Protection for Clock Sources........................................................................................................... 325
8.8.5.3 Configuring a Clock Source Group...................................................................................................................... 327
Issue 02 (2016-11-30) Huawei Proprietary and Confidential x

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 02 (2016-11-30) 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 320 and their meanings.
Table 1-1 Warning and safety symbols of the OptiX RTN 320
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
CAUTION
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
CAUTION
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
NOTICE
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
NOTICE
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
NOTICE
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.
1.6.2 Electromagnetic Exposure
This topic describes safety precautions for electromagnetic exposure.
1.6.3 Forbidden Areas
The topic describes requirements for a forbidden area.
1.6.4 Laser
This topic describes safety precautions for lasers.
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.
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
NOTICE
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.
NOTICE
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.
CAUTION
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.
CAUTION
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.
CAUTION
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.
1.7.2 Using Ladders
This topic describes safety precautions for using ladders.
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.
CAUTION
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
CAUTION
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
CAUTION
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.

CAUTION
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
NOTICE
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
NOTICE
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
CAUTION
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 Files for Authentication Using a USB Flash Drive and Hardening Security of
Files on the USB Flash Drive
This section describes how to prepare files for authentication using a USB flash drive and
how to harden security of files on the USB flash drive. The files allow you to perform site
commissioning, database backup/restoration, and software upgrades using a USB flash drive.
2.3 Determining the Commissioning Method
According to the scale of a microwave transmission network, commissioning engineers can
use the single-hop commissioning method or system commissioning method.
2.4 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 320 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 (By default, the
RSSI cable is not delivered. It must be
locally purchased), special spanner for the
orthogonal mode transducer (OMT)
(delivered with the OMT)
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 Files for Authentication Using a USB Flash

Drive and Hardening Security of Files on the USB Flash
Drive
This section describes how to prepare files for authentication using a USB flash drive and
how to harden security of files on the USB flash drive. The files allow you to perform site
commissioning, database backup/restoration, and software upgrades using a USB flash drive.
Prerequisites
The NMS is available.
Tools, Instruments, and Materials

USB file generation tool, USB flash drive
For OptiX RTN 320, the recommended USB flash drive model is Netac U208 (4G). If a USB
flash drive of another model or capacity is required, contact the local Huawei representative
office for confirmation. Some USB flash drives may not be compatible with OptiX RTN 300
products.
NOTE
The following procedure describes how to restoring a software package and configuration scripts from a USB
flash drive. The procedure of restoring a patch package and a database from a USB flash drive is similar. The
only difference is that a patch subdirectory and a db subdirectory need to be created and the patch package
and database files on the NMS need to be copied in the patch subdirectory and the db subdirectory
respectively, but the pkg or script directory does not need to be created.
Procedure
Step 1 Create a new folder usbfile on the computer and copy all files required for the USB flash
drive to the folder.
Table 2-2 Main data storage locations
Data Storage Location
NE software \pkg
NOTE
Data needs to be put in the \pkg path only if the NE software needs to be updated.
In other cases, the directory should be empty.
Patch software \patch
Scripts \script

Data Storage Location
Database \db
NOTE
The folder names can be customized by users. In this section, usbfile is used as an example.
Step 2 Open the directory for storing the USB file generation tool, and run startup_usbTool.bat.
NOTE
l On the U2000, the tool is stored in D:\oss\client\client\tools\usbtool.

l On the Web LCT, the tool is stored in D:\WebLCT\weblct\tools\usbtool.
The USB File Generation Tool dialog box is displayed.

Step 3 Generate an authentication file RTN.CER.
1. Input the user name and password for the target NE.
NOTE
For a new NE, input the default user name and password.
– Default user name: szhw
– Default password: Changeme_123
2. Set Encryption Type to PBKDF2.

NOTE
– At the same time, set SSL Certificate and Certificate File Path. There are two types of SSL
certificates: Default and Custom.
n Set the parameter to Default if you want to use the default certificate on the U2000. Set the
parameter to Custom if you want to use your own certificate.
n Two types of customized certificates are supported: *.crt and *.p12. A *.p12 certificate has
been encrypted, so a key is required. Select Generate USB authentication certificates when
preparing a customized certificate so that a USB flash drive supports the generated
customized certificate.
n Both *.crt and *.p12 certificates must be synchronized with the target NE. For details, see the
U2000 Administrator Guide.
3. Click Generate File.

4. Click OK in the displayed confirmation dialog box.
5. Open the directory storing the RTN.CER file and copy the file to the root directory of the
usbfile folder.
NOTE
– On the U2000, the file is stored in D:\oss\client\client\tools\usbtool\output (an example).

– On the Web LCT, the file is stored in D:\WebLCT\weblct\tools\usbtool\output (an example).
– Save the RTN.CER file before closing the USB file generation tool. Otherwise, the file will be
automatically deleted when you close the tool.
Step 4 Harden security of files in the usbfile directory.

NOTE
The default USB mode of an NE is the incompatible mode.

1. On the USB File Generation Tool page, click the Harden Security tab and a dialog box
is displayed.
2. Click Add, and select the usbfile directory to add all files under the directory to the file
list.

3. Optional: Right-click one or more files and set the encryption status.
NOTE
If the USB mode of an NE is the incompatible mode, set the encryption status of some files, for
example, the software package, to Disable to speed up the loading of files from the USB flash drive to
the target NE. However, it is recommended to encrypt all files.
4. Click Harden.
5. Click Yes in the strategy file generation dialog box displayed.
6. Record the file output path shown in the following dialog box. Click OK.

7. Check files and the contents structure in the output path and copy all contents and files to
the root directory on the USB flash drive.
NOTE
Files in the file output path must be copied to the USB flash drive as soon as possible, because all files
in the paths will be automatically deleted when the USB file generation tool is closed.
Files and contents structure on the USB flash drive:
Step 5 Click Close.
----End
2.3 Determining the Commissioning Method

According to the scale of a microwave transmission network, commissioning engineers can
use the single-hop commissioning method or system commissioning method.
Context
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.

System Commissioning
System commissioning is usually carried out for large-scale microwave transmission
networks. The major steps are outlined as follows:
1. 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.4 Checking Commissioning Conditions

Ensure that the equipment meets the requirements for site commissioning or system
commissioning prior to performing any commissioning tasks.
2.4.1 Checking Site Commissioning Conditions
Before performing site commissioning, ensure that the site and weather conditions meet the
requirements for site commissioning.
2.4.2 Checking System Commissioning Conditions
Before performing system commissioning, ensure that the equipment and weather meet the
requirements for system commissioning.
2.4.1 Checking Site Commissioning Conditions

Before performing site commissioning, ensure that the site and weather conditions meet the
requirements for site commissioning.
Context
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.4.2 Checking System Commissioning Conditions

Before performing system commissioning, ensure that the equipment and weather meet the
requirements for system commissioning.
Context
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 (Universal)

Site commissioning refers to the commissioning of one radio link hop and the sites at both
ends of the hop. Site commissioning ensures that the sites and the radio link between the sites
work properly. Site commissioning is a preparation for system commissioning.
3.2 Site Commissioning Procedure (with Cascade 1+1 Protection)
For sites configured with cascade 1+1 protection, the commissioning procedure is different.
Unless otherwise specified, 1+1 protection mentioned in the following refers to cascade 1+1
protection.
3.3 Site Commissioning Procedure (XPIC Links with 1+1 Protection)
For a site configured with XPIC links with 1+1 protection, commissioning the site requires
the operation of aligning polarized antennas in addition to the commissioning of cascade 1+1
links.
3.4 Site Commissioning Process (MIMO)
The RTN 320 supports intra-NE 2x2 multiple-input multiple-output (MIMO) links, inter-NE
2x2 MIMO links, and inter-NE 4x4 MIMO links. The commissioning process for MIMO
links is different from that for common links.
3.5 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 (Universal)

Site commissioning refers to the commissioning of one radio link hop and the sites at both
ends of the hop. Site commissioning ensures that the sites and the radio link between the sites
work properly. Site commissioning is a preparation for system commissioning.
You can use the following tools to configure site commissioning data for OptiX RTN 320:
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 radio 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.
Checking Alarms Required.
Aligning Antennasa Aligning Single-Polarized Required when radio

Antennas services are transmitted by
single-polarized antennas.
Aligning Dual-Polarized Required when radio

dual-polarized antennas.
Checking the Radio 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 radio 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 radio link data on OptiX RTN 320.

l Are familiar with the radio 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 Commissioning Data or Delivering a Required.

Commissioning Data Script to an NE Using the Web
LCT
Checking Alarms Required.
Aligning Antennasb Aligning Single-Polarized Required when radio

single-polarized antennas.
Aligning Dual-Polarized Required when radio

dual-polarized antennas.
Checking the Radio Link Status and Receive Power Required.
NOTE
b: Before aligning antennas, power on the equipment and configure site commissioning data at both ends
of the radio link.
3.2 Site Commissioning Procedure (with Cascade 1+1

Protection)
For sites configured with cascade 1+1 protection, the commissioning procedure is different.
Unless otherwise specified, 1+1 protection mentioned in the following refers to cascade 1+1
protection.
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 or delivery of
commissioning data scripts using the Web LCT.
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.
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 Change an NE ID. commissioning
Change an NE ID. data. data.
3 Configure NE 3
Configure NE communication
Check alarms. Check alarms.
communication parameters.
parameters.
Change an NE name.
Change an NE name. 4 4
Align antennas Realesing the QoS Align antennas
Realesing the QoS policy bound to the
policy bound to the COMBO port
5 5
COMBO port
Check the status Delete logical Check the status
Delete logical and receive power COMBO port and receive power
COMBO port of the active of the active
microwave link. Configure the VLAN ID microwave link.
Configure the VLAN ID and bandwidth for
and bandwidth for 6 inband DCN. 6
inband DCN. Power on the Power on the
equipment. Configure a hop of equipment.
Configure a hop of microwave link.
microwave link. 7 7
Configure site Configure site
commissioning commissioning Change an NE ID.
parameters. Change an NE ID. data.
Configure NE Configure NE
communication communication
parameters. parameters.
If an optical splitter is used 8.1 Change an NE name. Change an NE name.

to form 1+1 protection, this If an optical splitter is
Configure a LAG for
step does not need to be used to form 1+1 8.1 Configure a LAG
1+1 protection. Realesing the QoS Realesing the QoS
performed. protection, this step does
policy bound to the for 1+1 protection. policy bound to the
not need to be performed.
COMBO port COMBO port
8.2
Configure a 1+1
Delete logical 8.2 Configure a 1+1 Delete logical
protection group.
COMBO port protection group. COMBO port
10
Synchronizing Data on Configure the VLAN ID Configure the VLAN ID
Active and Standby NEs in a and bandwidth for 10 and bandwidth for
Synchronizing Data on
1+1 Protection Group inband DCN. inband DCN.
Active and Standby NEs in a
1+1 Protection Group
11
11
Required Check alarms. Check alarms. 11
11
Check alarms. Check alarms.
Optional
10
No operation
Check the status and 10
receive power of the
Check the status and
microwave links.
receive power of the
microwave links.
For sites at both ends of a link, perform the following simultaneously:

1. Power on the active equipment according to Powering on the Equipment and keep the
standby equipment in the off status.
2. Configure commissioning data for the active equipment according to Configuring Site
Commissioning Data. At this time, do not configure the IF 1+1 protection group (or the
link aggregation group used for 1+1 protection if the protection involves LAG).
3. Check alarms on the active equipment according to Checking Alarms.
4. Align single-polarized antennas according to Aligning Antennas to activate microwave
links between the active equipment.
5. Check the status and receive power of the microwave link between the active equipment
according to Checking the Microwave Link Status and Receive Power.
6. Power on the standby equipment according to Powering on the Equipment.
7. Configuring Commissioning Data for the standby NE.
8. Configure IF 1+1 protection group data for active NE. (and the link aggregation
group used for 1+1 protection if the protection involves LAG).
9. 5.5.7 Synchronizing Data on Active and Standby NEs in a 1+1 Protection Group.
10. Check alarms on the active and standby equipment according to Checking Alarms.
11. 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
Power on the Power on the
Change an NE ID. Change an NE ID.
equipment. equipment.
Configure NE 2 2
Configure site Configure NE
communication Configure site
commissioning communication
parameters. commissioning
data. parameters.
data.
Change an NE 3 Change an NE 3
name. Check alarms. name. Check alarms.
Configure the VLAN ID Configure the VLAN ID

and bandwidth for 4 and bandwidth for 4
inband DCN. Align antennas inband DCN. Align antennas
Configure a hop of Configure a hop of

microwave link. 5
5 microwave link.
Check the status
Check the status
and receive power
and receive power
of the active
of the active
microwave link.
microwave link.
6
Power on the
equipment.
7
Configure site
commissioning Change an NE ID.
data.
Configure NE
If an optical splitter is used communication
8.1
to form 1+1 protection, this Configure a LAG parameters.
step does not need to be for 1+1 protection.
performed.
Change an NE
8.2 name.
Configure a 1+1
protection group. Configure the VLAN
The data configuration ID and bandwidth for
engineers responsible for 9 inband DCN.
configuring 1+1 protection Synchronizing Data on
configure the following for sites Active and Standby NEs in a
at both ends using DCN at the 1+1 Protection Group
Change an NE ID.
near end.
10 Lock the 1+1 protection
Configure NE group of the active devices
communication to the active unit.
parameters.
11
Power on the
equipment. Change an NE
name.
12
Configure site
commissioning Configure the VLAN ID
data. and bandwidth for
inband DCN.
If an optical splitter is used 13.1
to form 1+1 protection, this Configure a LAG
step does not need to be for 1+1 protection.
performed.
13.2
Configure a 1+1
protection group.
14
Synchronizing Data on
Active and Standby NEs in a
1+1 Protection Group
15 Lock the 1+1 protection

group of the active devices
to the active unit.
16 16 16
16
Check alarms. Check alarms. Check alarms. Check alarms.
17 17
Required Check the status and receive Check the status and receive
power of the microwave links. power of the microwave links.
Optional
18 18
No operation Clear forced switchover Clear forced switchover
command. command.
1. Power on the active equipment at both ends according to Powering on the Equipment
and keep the standby equipment in the off status.
2. Configure commissioning data for the active equipment at both ends according to
Configuring Site Commissioning Data. At this time, do not configure the IF 1+1
protection group (or the link aggregation group used for 1+1 protection if the protection
involves LAG).
3. Check alarms on the active equipment at both ends according to Checking Alarms.
4. Align single-polarized antennas according to Aligning Antennas to activate microwave
links between the active equipment.

6. Power on the standby equipment on the far end according to Powering on the
Equipment.
7. Configure commissioning data for the active equipment at far end according to
involves LAG).
8. Configure IF 1+1 protection group data for the active NE on the far end (and the link
aggregation group used for 1+1 protection if the protection involves LAG).
9. 5.5.7 Synchronizing Data on Active and Standby NEs in a 1+1 Protection Group on
the far end.
10. Forcibly switch the 1+1 protection group of active NEs to the active unit according to
Microwave 1+1 Protection Switching.
11. Power on the standby equipment on the near end according to Powering on the
Equipment.
12. Configure commissioning data for the active equipment at near end according to
involves LAG).
13. Configure IF 1+1 protection group data for the active NE on the near end (and the
the near end.
15. Forcibly switch the 1+1 protection group of active NEs to work at the active unit
according to Microwave 1+1 Protection Switching.

18. Clear forced switchover commands for the main equipment at the near end and the far
end according to Microwave 1+1 Protection Switching
3.3 Site Commissioning Procedure (XPIC Links with 1+1

Protection)
For a site configured with XPIC links with 1+1 protection, commissioning the site requires
the operation of aligning polarized antennas in addition to the commissioning of cascade 1+1
links.
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.
Site commissioning can be performed according to Figure 3-3 or Figure 3-4 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-3 Coordinately configuring 1+1 protection for sites at both ends
For sites at both ends of a link, perform the following simultaneously:
1. Power on the active equipment according to Powering on the Equipment and keep the
standby equipment in the off status.
2. Configure commissioning data for the active equipment according to Configuring Site
Commissioning Data. At this time, do not configure the IF 1+1 protection group (or the
3. Check alarms on the active equipment according to Checking Alarms.
4. Align Dual-Polarized antennas according to Aligning Dual-Polarized Antennas (XPIC
link) to activate microwave links between the active equipment.
6. Power on the standby equipment according to Powering on the Equipment.
7. Configuring Commissioning Data for the standby NE.

8. Configure IF 1+1 protection group data for active NE. (and the link aggregation
group used for 1+1 protection if the protection involves LAG).
9. 5.5.7 Synchronizing Data on Active and Standby NEs in a 1+1 Protection Group.
Figure 3-4 Independently configuring 1+1 protection for the near-end site
1. Power on the active equipment at both ends according to Powering on the Equipment
and keep the standby equipment in the off status.
2. Configure commissioning data for the active equipment at both ends according to

involves LAG).
3. Check alarms on the active equipment at both ends according to Checking Alarms.
4. Align Dual-Polarized antennas according to Aligning Dual-Polarized Antennas (XPIC
link) to activate microwave links between the active equipment.
6. Power on the standby equipment on the far end according to Powering on the
Equipment.
7. Configure commissioning data for the active equipment at far end according to
involves LAG).
8. Configure IF 1+1 protection group data for the active NE on the far end (and the link
aggregation group used for 1+1 protection if the protection involves LAG).
the far end.
10. Forcibly switch the 1+1 protection group of active NEs to the active unit according to
Microwave 1+1 Protection Switching.
11. Power on the standby equipment on the near end according to Powering on the
Equipment.
12. Configure commissioning data for the active equipment at near end according to
involves LAG).
13. Configure IF 1+1 protection group data for the active NE on the near end (and the
the near end.
15. Forcibly switch the 1+1 protection group of active NEs to work at the active unit
according to Microwave 1+1 Protection Switching.

18. Clear forced switchover commands for the main equipment at the near end and the far
end according to Microwave 1+1 Protection Switching
3.4 Site Commissioning Process (MIMO)

The RTN 320 supports intra-NE 2x2 multiple-input multiple-output (MIMO) links, inter-NE
2x2 MIMO links, and inter-NE 4x4 MIMO links. The commissioning process for MIMO
links is different from that for common links.

Commissioning Process for Intra-NE 2x2 MIMO
Figure 3-5 Flowchart for intra-NE 2x2 MIMO commissioning
Table 3-2 Commissioning process for intra-NE 2x2 MIMO

Step Operation Remarks
1 4.1 Powering On OptiX Required

RTN 320

2 5.5 Configuring Site Required

Commissioning Data NOTE
l Do not enable XPIC when
configuring microwave
link data.
l Configure each microwave
link in the MIMO work
group.
3 5.6 Checking Alarms Required
4 5.7.2 Aligning Single- Required

Polarized Antennas
5 5.9 Configuring MIMO Required

Links
6 5.8 Checking the Required

Microwave Link Status
and Receive Power
NOTE
Inter-NE 2x2 MIMO links will commonly be expanded to 4x4 MIMO links. The commissioning
processes for inter-NE 2x2 and 4x4 MIMO links are the same. After commissioning inter-NE 2x2
MIMO links, use purchased short-circuiting plates to seal idle polarization ports.

Commissioning Process for Inter-NE 4x4 MIMO
Figure 3-6 Flowchart for inter-NE 4x4 MIMO commissioning
Table 3-3 Commissioning process for inter-NE 4x4 MIMO
1 4.1 Powering On OptiX Required

RTN 320

2 5.5 Configuring Site Required

Commissioning Data NOTE
l Do not enable XPIC when
configuring microwave
link data.
l Configure each microwave
link in the MIMO work
group.
3 5.6 Checking Alarms Required
4 5.7.4 Aligning Dual- Required

Polarized Antennas (Inter-
NE MIMO)
5 5.9 Configuring MIMO Required

Links
6 5.8 Checking the Required

Microwave Link Status
and Receive Power
3.5 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-4 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 AM Shifting Required.
6.4 Testing ATPC Required.
6.5 Testing Protection 6.5.1 Testing ERPS Required.

Switching Switching

6.5.2 Testing 1+1 Required when a microwave

Protection Switching link with 1+1 protection is
(Intra-equipment 1+1 configured.
Protection)
6.5.3 Testing 1+1

Protection Switching
(Cascade 1+1 Protection)
6.5.4 Testing MPLS APS Required.

Protection Switching
6.6 Checking the Clock Status Required.
6.7 Testing the Fade Margin over a Microwave Link Optional.
6.8 Testing Ethernet 6.8.2 Testing the Latency, Required.

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

term Packet Loss Ratio

OptiX RTN 320 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.
Context
The commissioning process is as follows:
4.1 Powering On OptiX RTN 320
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
When you load commissioning data from a USB flash drive to an NE, the NE software is
upgraded simultaneously.
4.3 Using the Web LCT to Complete Subsequent Commissioning Items
The specific commissioning steps are the same as those in the scenario where the entire
commissioning process is performed using the Web LCT.


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 320 (with a PI)

This section describes how to power on OptiX RTN 320 with an indoor PI. You can verify
whether the OptiX RTN 320 and indoor PI are functional by observing the equipment power-
on process.
4.1.2 Powering on OptiX RTN 320 (with a DC Power Supply)
This section describes how to power on OptiX RTN 320 directly with a DC power supply.
You can verify whether the OptiX RTN 320 and DC power system are functional by
observing the equipment power-on process.

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 320.
Table 4-1 Fuse capacity

Chassis Recommended Fuse Capacity
OptiX RTN 320 10 A

Precaution
NOTICE
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.
Step 2 Verify that the outdoor network 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
outdoor network cable or OptiX RTN 320 is short-circuited.
l If the DC IN indicator is steady green and the P&E OUT indicator is off, check whether the outdoor
network cable or PI is faulty.
Step 3 Observe the system indicator on OptiX RTN 320 to check whether the NE is successfully
powered on.
Normally, the system indicator on the OptiX RTN 320 should be steady green.
NOTE
If the system indicator is steady red, check whether the microwave link, the outdoor network cable or
OptiX RTN 320 is faulty.
----End


Prerequisites
supply are correct.
Context

Split OptiX RTN 320 12 A
Integrated OptiX RTN 320 10 A
Precaution
NOTICE
Procedure
Step 1 Connect to the power supply and verify that the DC power cable is correctly connected.

Step 2 Switch on the power supply and view the system indicator on the OAU to check whether the
NE is successfully powered on.
Normally, the system indicator in the USB/NMS port on the OptiX RTN 320 should be 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 320 is faulty.
----End
4.2 Loading Commissioning Data Using a USB Flash

Drive
When you load commissioning data from a USB flash drive to an NE, the NE software is
upgraded simultaneously.
Prerequisites
l The equipment has been powered on and is running properly. (If the equipment is
powered on for the first time or if the equipment is powered off and then powered on
again, wait 3 minutes before you load commissioning data using a USB flash drive.)

l Commissioning data has been loaded to a USB flash drive.

l The certificate file on the USB flash drive is correct.
Tools, Equipment, and Materials

USB flash drive
Procedure
Step 1 Power on the equipment and open the USB maintenance compartment.
Step 2 Insert the USB flash drive into the USB port. Remove the WLAN module if it has been
inserted into the USB port.
Step 3 Check the data loading status by observing the USB indicator.
USB Indicator Status Data Loading Status Follow-up Operation
The indicator blinks green, Loading data is successful. Remove the USB flash
turns off, blinks green again, NOTE drive, connect the WLAN
and turns steady green. l When the indicator is
module to the USB port, and
blinking green, do not close the maintenance
remove the USB flash compartment.
drive. Otherwise, the data
loading is interrupted.
l If both script files and
software package are
loaded using the USB
flash drive, the loading
may take more than 10
minutes.

USB Indicator Status Data Loading Status Follow-up Operation
The indicator turns off after The USB flash drive is l Copy the commissioning
the USB flash drive is faulty and fails to go online. data to another qualified
inserted into the USB port. NOTE USB flash drive.
Another possible cause is that l Perform Step 2 again to
the USB flash drive is not
load the commissioning
properly inserted.
data.
The USB indicator blinks The model of the USB flash l Copy the commissioning
red. drive is incorrect, or an error data to another USB
occurs when the NE flash drive.
attempts to read/write the l Perform Step 2 again to
USB flash drive. load the commissioning
NOTE data.
For the USB flash drive
models supported by OptiX
RTN 320, see 2.2 Preparing
Files for Authentication
Using a USB Flash Drive and
Hardening Security of Files
on the USB Flash Drive.
The indicator is steady red. The loaded data is Handle the fault by
abnormal. following instructions in 7.1
Handling a Fault in
Commissioning Script
Loading Using a USB
Flash Drive.
----End
4.3 Using the Web LCT to Complete Subsequent

Commissioning Items
The specific commissioning steps are the same as those in the scenario where the entire
commissioning process is performed using the Web LCT.
Prerequisites
l The OptiX RTN 320 has been powered on.
l Commissioning data has been downloaded from a USB flash disk to the NE.

Web LCT
Procedure
Step 1 At one end of the radio link, connect the Web LCT to the equipment.

Step 2 5.6 Checking Alarms.
Step 3 5.7 Aligning Antennas.
Step 4 5.8 Checking the Microwave Link Status and Receive Power.
----End

OptiX RTN 320 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.
Context
The commissioning process is as follows:
5.2 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.
5.3 Creating NEs Using the Search Method
The search method is generally used to create an NE during site commissioning.
5.4 Delivering a Commissioning Data Script to an NE Using the Web LCT
This section describes how to deliver a commissioning data script to an NE using the Web
LCT. The function is available when a site commissioning data script has been prepared. With
this function, onsite configuration is not required.
5.5 Configuring Site Commissioning Data
This section describes how to configure site commissioning data when using the Web LCT to
perform site commissioning.
5.6 Checking Alarms
Checking alarms generated by equipment helps you to determine whether the equipment is
functioning properly.
5.7 Aligning Antennas
Antenna alignment is the most important activity in site commissioning, as antenna alignment
has a direct effect on microwave link performance.

5.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.
5.9 Configuring MIMO Links
MIMO links are configured after antennas have been aligned.


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.

on process.

Prerequisites
supply are correct.
Context
Split OptiX RTN 320 12 A
Integrated OptiX RTN 320 10 A

Precaution
NOTICE
Procedure
Step 1 Connect to the power supply and verify that the DC power cable is correctly connected.
Step 2 Switch on the power supply and view the system indicator on the OAU to check whether the
NE is successfully powered on.
Normally, the system indicator in the USB/NMS port on the OptiX RTN 320 should be 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 320 is faulty.
----End

on process.
Prerequisites
supply are correct.
Context
OptiX RTN 320 10 A
Precaution
NOTICE
Procedure
Step 1 Connect to the power supply.

Step 2 Verify that the outdoor network 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
outdoor network cable or OptiX RTN 320 is short-circuited.
l If the DC IN indicator is steady green and the P&E OUT indicator is off, check whether the outdoor
network cable or PI is faulty.
Step 3 Observe the system indicator on OptiX RTN 320 to check whether the NE is successfully
powered on.
Normally, the system indicator on the OptiX RTN 320 should be steady green.
NOTE
If the system indicator is steady red, check whether the microwave link, the outdoor network cable or
OptiX RTN 320 is faulty.
----End

5.2 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.
Prerequisites
l OptiX RTN 320s have been powered on.
l The WLAN module is normal.
NOTE
After you load commissioning data using a USB flash drive and establish the DCN, you need to connect the
Web LCT to only one end of a microwave link hop. Then, the entire microwave link hop can be
commissioned.

Web LCT (Win7 operating system)
Background Information
This section describes how to connect the OptiX RTN 320 to the Web LCT through WLAN.
If the WLAN module is not working properly, it is recommended that you connect the OptiX
RTN 320 to the Web LCT through the NMS/GE2(e) port within the maintenance
compartment. In normal cases, it is not recommended that you connect the OptiX RTN 320 to
the Web LCT through the NMS port at the side of the maintenance compartment. The IP
address of the Ethernet ports on the computer that houses the Web LCT must be in the same
network segment as the NE IP address. The two IP addresses must be different.

Figure 5-1 Ways for connecting the Web LCT to an OptiX RTN 320
NOTE
l If a site has several cascaded OptiX RTN 320s, connect the laptop to only one of the OptiX RTN 320s.
Other OptiX RTN 320s can be connected through the internal DCN.
l Use either a crossover cable or a straight-through cable to connect the laptop to the OptiX RTN 320. For
the wire sequences of crossover cables and straight-through cables, see Cable in the OptiX RTN 320
Microwave Transmission System Product Description.
Procedure
Step 1 Start the laptop and log in to the operating system.
Step 2 Use the Wi-Fi Connection tool delivered with the Web LCT to set up a Wi-Fi connection
between the laptop and NE.
1. Access the Wi-Fi Connection tool directory (such as WebLCT\weblct\tools\wificonn)
and run WifiConnection.exe.
2. Select the SSID of the NE to set up a WLAN connection.
– The default SSID is FMn-The last six digits of a MAC address in hexadecimal
format-NE ID.
– Default password: Modify_123.

Right-click it.
1
After the connection is set up, the

connection status of the related NE
becomes "Connected".

NOTE
– If the WLAN Connection tool does not find the SSID of the NE, perform the following
operations:
n Check whether there is a block between the laptop and the NE.
n Check whether the distance between the laptop and NE is longer than the typical WLAN
transmission distance. (The typical transmission distance between the WLAN module
and laptop is 30m. An external WLAN network adapter can be installed on the laptop to
extend the typical transmission distance to 70 m.)
n If the distance between the laptop and NE is shorter than the typical WLAN transmission
distance, view the status of the WLAN indicator in the maintenance compartment. If the
WLAN indicator is red (indicating the abnormal state), replace the WLAN module or
connect the laptop to the NMS port in the maintenance compartment to check the
WLAN configuration.
– Generally, it takes about 20s to set up connection through WLAN, please be patient.
– If a WLAN connection fails to be set up, check whether:
n The connection password is correct.
n The IP address is automatically allocated.
n Another laptop is connected to the NE though WLAN. Only one device can access an
NE through WLAN at a time. If another device needs to access the NE, it is
recommended that you use the WLAN Connection tool to disconnect the first device and
then access the second device. The disconnection method is similar to the connection
method.
After the Web LCT and the OptiX RTN 320 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.
Step 3 After the WLAN connection is set up successfully, double-click the Start Web LCT icon on
the desktop.
The system displays the USER LOGIN window of the Web LCT.
Step 4 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
If you cannot access the USER LOGIN window or the NE List page, configure the Internet
Explorer using the following method:
5.3 Creating NEs Using the Search Method

The search method is generally used to create an NE during site commissioning.
Prerequisites
l The Web LCT is communicating properly with NEs.
l You must be an NM user with NE operator authority or higher.
l If the NE connection mode is SSL or Normal+SSL (default), and NEs connect to the
Web LCT through WLAN, NEs are accessed using the SSL protocol. If the NEs connect
to the Web LCT through an Ethernet cable, it is also recommended to use the SSL
protocol.
l Follow the following steps to replace the SSL certificate if it is not matched.

– Delete the WebLCT\conf\certificate directory on the Web LCT.

– Copy the server\etc\ssl\nemanager\default directory on the U2000 to the path
WebLCT\conf on the Web LCT. Rename default to certificate. Note that the
installation path on the Web LCT should not contain Chinese characters, spaces, or
special characters.
– Restart the Web LCT.

Web LCT
Context
The following procedure:
l Searches for NEs using the Search by user port method if the NEs are connected
directly to the Web LCT using WLAN.
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, and
are connected directly to the Web LCT using LAN.
NOTE
The default user name for NE login: lct.

The default password for NE login: Changeme_123.
Procedure
Step 1 Search for NEs using the Search by user port method if the NEs are connected directly to the
Web LCT using WLAN.
Step 2 Search for NEs using the NE Search method if the NEs are connected directly to the Web
LCT using Ethernet cables.

Step 3 Search for NEs using the IP auto discovery method if the site has multiple NEs.
----End
5.4 Delivering a Commissioning Data Script to an NE

Using the Web LCT
This section describes how to deliver a commissioning data script to an NE using the Web
LCT. The function is available when a site commissioning data script has been prepared. With
this function, onsite configuration is not required.
Prerequisites
l The equipment has been connected to the Web LCT.
l The commissioning data script for the site has been prepared.

Web LCT

Procedure
Step 1 Deliver a commissioning data script.
NOTE
By default, "User Name" is "szhw" and "Password" is "Changeme_123".
----End
5.5 Configuring Site Commissioning Data

This section describes how to configure site commissioning data when using the Web LCT to
perform site commissioning.
5.5.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.
5.5.2 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.
5.5.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.
5.5.4 Releasing the QoS Policy Bound to an Interface
This operation releases the QoS policy bound to a port.
5.5.5 Creating a LAG
If links must be configured with EPLA/1+1 protection based on E-LAG, the access ports must
be added into an E-LAG.
5.5.6 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.
5.5.7 Synchronizing Data on Active and Standby NEs in a 1+1 Protection Group
This section describes how to synchronize data of an active NE to its standby NE.

5.5.8 Testing the XPI Value

When aligning polarization directions of antennas, test the XPI value to determine whether
the polarization directions are correctly aligned.
5.5.1 Changing an NE ID
Prerequisites
You must be an NM user with NE maintainer authority or higher.

Web LCT
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 log in to the NE again.
Procedure
Step 1
----End

5.5.2 Changing an NE Name

Prerequisites
You must be an NM user with NE operator authority or higher.

Web LCT
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.5.3 Setting the VLAN ID and Bandwidth for an Inband DCN


Prerequisites

Web LCT
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) 1000Kbit/s
Procedure
Step 1
----End
5.5.4 Releasing the QoS Policy Bound to an Interface

Prerequisites

U2000

NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The following steps release the QoS policy bound to a COMBO port.
Procedure
Step 1
----End
5.5.5 Creating a LAG

If links must be configured with EPLA/1+1 protection based on E-LAG, the access ports must
be added into an E-LAG.
Prerequisites

Web LCT
Context
l Create a LAG for configuring 1+1 protection according to the planned parameter values
listed in the following table.
Parameter NE
LAG No. Assign Automatically (default value).
LAG Name LAG_02

Parameter NE
LAG type Static (default value)
Revertive Non-Revertive
Load sharing type Non-load sharing (default value)
LAG priority for the main NE 32768 (default value)
Main port GE1
Main port GE(e)
Procedure
Step 1
----End
5.5.6 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

Context
The following procedure configures basic information for the hop of microwave link.
The planned parameter values are listed in the following table.
Parameter Link
Protection 1+0
XPIC Enabled
l Polarization V: IF2
l Polarization H: IF1
Link ID l Polarization V: 1
l Polarization H: 2
Channel Space 28MHz
AM Status Enabled
Guaranteed Capacity Modulation Mode QPSK
Full Capacity Modulation Mode 64QAM
TX Frequency (MHz) 11060.0
T/R Spacing (MHz) 1200
ATPC Disabled
TX power (dBm) 11
Power to be Received(dBm) -20
Procedure
Step 1
----End

5.5.7 Synchronizing Data on Active and Standby NEs in a 1+1

Protection Group
This section describes how to synchronize data of an active NE to its standby NE.
Prerequisites
l An inter-equipment 1+1 protection group has been created.
l The active and standby NEs are cascaded through ports of the same type, for example,
COMBO ports.
l This operation is performed on the active NE.

U2000
NOTE
The following steps synchronize data from an active NE to its standby NE.
Procedure
Step 1
----End
5.5.8 Testing the XPI Value

When aligning polarization directions of antennas, test the XPI value to determine whether
the polarization directions are correctly aligned.

Prerequisites
l You must be an NM user with NE maintainer authority or higher.
l All ports are configured with intermediate frequency (IF) parameters specified in the
network planning.

Web LCT
Context
The following procedure tests the XPI value based on the parameter values listed in the
following table.
Parameter Value
Opposite NE ID 40802
Opposite NE Ex-ID 9
Opposite NE Slot ID 1
Procedure
Step 1
----End
5.6 Checking Alarms

Checking alarms generated by equipment helps you to determine whether the equipment is
functioning properly.

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.7 Aligning Antennas

Antenna alignment is the most important activity in site commissioning, as antenna alignment
has a direct effect on microwave link performance.
5.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.
5.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.
5.7.3 Aligning Dual-Polarized Antennas (XPIC Links)
When aligning dual-polarized antennas, align the main lobes by adjusting the azimuth and
elevation of the antennas at both ends. Engineers also need to adjust the feed booms of the
antennas so that cross-polarization discrimination (XPD) meets requirements.
5.7.4 Aligning Dual-Polarized Antennas (Inter-NE MIMO)

elevation of the antennas at both ends. Engineers also need to adjust the antenna feeds so that
cross-polar isolation (XPI) meets requirements.
5.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 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 320).
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
B 4 5 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.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 antennas have been installed according to the network plan.
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).
NOTE
When aligning antennas at intra-NE 2x2 multiple-input multiple-output (MIMO) sites, commission each link
separately. That is, disable a link when commissioning the other. Otherwise, interference may be caused on
received signals, affecting antenna alignment.

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 (By default, the RSSI cable is not
delivered. It must be locally purchased.)
NOTICE
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.
The procedure describes in this section is the procedure for aligning single-polarized antennas
for the split OptiX RTN 320. For the integrated OptiX RTN 320, the procedure is similar. The
RSSI port is on the OptiX RTN 320.

Figure 5-6 Testing the RSSI voltage using a multimeter (split OptiX RTN 320)
Figure 5-7 Testing the RSSI voltage using a multimeter (integrated OptiX RTN 320)
TNC type (female)
Test pin TNC type (female)
Test pin
TNC type (Male)
TNC type (Male)

RTN 320
XMC-3 ODU

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 320.
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 320 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.
NOTE
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-8 Testing the RSSI voltage using a multimeter
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-9.

Figure 5-9 Signal peaks

2
1 3
NOTICE
If the number of tracked signal peaks is fewer than three, even after a wide rotation and
careful observation of the multimeter, refer to 5.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-9. 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
5.7.3 Aligning Dual-Polarized Antennas (XPIC Links)

elevation of the antennas at both ends. Engineers also need to adjust the feed booms of the
antennas so that cross-polarization discrimination (XPD) meets requirements.
Prerequisites
l The site commissioning of the radio equipment at both ends of the radio link is complete.
l The weather at both stations is suitable for outdoor operations and there is no threat of
rain, snow, or fog
l On-site conditions meet the requirements for the antennas to operate at a high altitude
and the personnel commissioning the antennas are trained to work at high altitudes.
l The Multimeter is calibrated.

l The ATPC function is disabled (its default status on the NE is Disabled).

l The AM function is disabled (its default status on the NE is Disabled).

l Adjustable wrench
l Interphone
l Telescope
l Multimeter
delivered. It must be locally purchased)
l Special spanner for the orthogonal mode transducer (OMT) (delivered with the OMT)
Context
NOTE
The following procedure assumes that the RTN 320s at both ends are installed separately from antennas. If
the RTN 320s at both ends need to be connected directly to an OMT, the OMT should be adjusted instead of
the antenna feed boom.
Procedure
Step 1 Power off the vertically polarized ODUs and power on the horizontally polarized ODUs at
both ends of the microwave link. Ensure that the antennas at both ends are transmitting
horizontally polarized signals.
Step 2 Adjust the azimuth angle and elevation angle of the antennas at both ends by referring to 5.7.2
Aligning Single-Polarized Antennas, and ensure that the main lobes of the horizontally
polarized signals are aligned.
Step 3 Measure the received signal level (RSL) of the horizontally polarized signals, that is, P1, at
the local end.
1. Use a multimeter to measure the RSL at the RSSI port of the horizontally polarized
ODU.
2. Calculate the RSL of the horizontally polarized signals, that is, P1, by referring to the
curve diagram delivered with the ODU.
Step 4 Adjust the feed boom at the local end, and ensure that the RSL of the vertically polarized
signals reaches the lower threshold (P2).
1. Power on the vertically polarized ODU at the local end.
2. Use a multimeter to measure the RSL at the RSSI port of the vertically polarized ODU.
3. Calculate the RSL (P2) of the vertically polarized signals by referring to the curve
diagram in the RTN 320 box.
4. Calculate the XPD1 (XPD1 = P1 - P2).
If... Then...
The calculated XPD1 is less than 24 dB Go to the next step.

If... Then...
The calculated XPD1 is greater than or equal to 24 dB Go to Step 5.
5. Release the feed boom holder slightly, and turn the feed boom slightly until the RSL
reaches the lower threshold and the calculated XPD1 is greater than or equal to 24 dB.
Step 5 Record the angle (D1) of the current feed boom.
Step 6 At both ends of the microwave link, power off the horizontally polarized ODUs and power on
the vertically polarized ODUs. Ensure that the antennas at both ends are transmitting
vertically polarized signals.
Step 7 Measure the RSL (P3) of the vertically polarized signals at the local end by referring to Step
3.
Step 8 Adjust the feed boom at the local end, and ensure that the RSL of the horizontally polarized
signals reaches the lower threshold (P4).
1. Power on the horizontally polarized ODU at the local end.
2. Use a multimeter to measure the RSL at the RSSI port of the horizontally polarized
ODU.
3. Calculate the RSL (P4) of the horizontally polarized signals by referring to the curve
diagram delivered with the ODU.
4. Calculate the XPD2 (XPD2 = P3 - P4).
If... Then...
The calculated XPD2 is less than 24 dB Go to the next step.
The calculated XPD2 is greater than or equal to 24 dB Go to Step 9.
5. Release the feed boom holder slightly, and turn the feed boom slightly until the RSL
reaches the lower threshold and the calculated XPD2 is greater than or equal to 24 dB.
Step 9 Record the angle (D2) of the current feed boom.
Step 10 Adjust the feed boom slightly (ranging from D1 to D2), and ensure that XPD1 and XPD2 are
greater than or equal to 24 dB.

NOTE
If D1 and D2 are the same, you do not need to adjust the feed boom.
Step 11 Tighten all the screws on the antennas.

NOTE
Use the multimeter to measure the RSL at the RSSI port again to ensure that no movement occurred during
the screw tightening process.
----End
Related Information
In practice, you can align vertically polarized antennas first. If XPD can meet requirements
after the vertically polarized antennas are aligned, you do not need to align horizontally
polarized antennas. Otherwise, you need to go on to align the horizontally polarized antennas.
5.7.4 Aligning Dual-Polarized Antennas (Inter-NE MIMO)

elevation of the antennas at both ends. Engineers also need to adjust the antenna feeds so that
cross-polar isolation (XPI) meets requirements.
Prerequisites
l The antennas have been installed according to the network plan.
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 Telescope
l Multimeter
delivered. It must be locally purchased)
l Special spanner for the orthogonal mode transducer (OMT) (delivered with the OMT)

Context
Figure 5-10 Dual-polarized antennas for inter-NE MIMO
NOTICE
After changing the frequency, align antennas again to ensure that the XPI is in a range of 19
dB to 26 dB.
Ensure that the poles where two antennas are installed at a MIMO site are in parallel.
Otherwise, the XPI cannot be adjusted to a range of 19 dB to 26 dB.
Procedure
Step 1 Align the physical antennas.
1. Unmute ODU port 1 and mute the other ODUs. Adjust antennas A and B until they are
properly aligned.
2. Align antennas C and D in the same way.
Step 2 Align the polarization directions.

1. Tighten the screws for adjusting the azimuth and elevation of antennas A and B.
2. Unmute all ODUs and use the Web LCT to calculate XPI values of ODU port 3 and
ODU port 4. Adjust the feed of antenna A until the XPI values are within the range of 20
dB to 26 dB.
3. Use the Web LCT to calculate XPI values of ODU port 1 and ODU port 2. Adjust the
feed of antenna B until the XPI values are within the range of 20 dB to 26 dB.
4. Use the Web LCT to check whether the XPI values of ODU port 3 and ODU port 4 are
still within the range of 20 dB to 26 dB. If yes, go to the next sub-step. If no, re-adjust
the feed of antenna A until the XPI values are within the range of 20 dB to 26 dB. Use
the Web LCT to check whether the XPI values of ODU port 1 and ODU port 2 are still
within the range of 20 dB to 26 dB. If yes, go to the next sub-step. If no, re-adjust the
feed of antenna B until the XPI values are within the range of 20 dB to 26 dB. Check the
XPI values of ODU port 1, ODU port 2, ODU port 3, and ODU port 4 for multiple times

and ensure that their XPI values are within the range of 20 dB to 26 dB by adjusting the
feeds of corresponding antennas.
5. Tighten the screws for adjusting the polarization directions of antennas A and B.
6. Align the polarization directions of antennas C and D in a similar way described in sub-
steps a to e.
----End
5.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.
Prerequisites
l Antennas have been aligned.
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
Handling the Failure of the Receive Power to Meet the Design Requirements.
----End

5.9 Configuring MIMO Links

MIMO links are configured after antennas have been aligned.
Prerequisites

Web LCT
Context
The following procedure configures a 4x4 MIMO link.
The following table lists the parameter values.
Parameter Value
IF Channel Bandwidth (MHz) 56 MHz
AM Status Enabled
Guaranteed Capacity Modulation QPSK
Full Capacity Modulation 256QAM
ATPC Enable Status Disabled
Maximum Transmit Power (dBm) 18.0
TX Power (dBm) 15.0
TX Frequency (MHz) 13087.000
T/R Spacing (MHz) 266.000
TX Status unmute
NOTE
The configuration example illustrates how to configure 4x4 MIMO links. You can configure 2x2 MIMO
links in the similar way. The only difference lies in that you need to set MIMO Type to 2*2 MIMO
(Not Cascaded).
Procedure
Step 1

----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, data communication
network (DCN) 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 AM Shifting
By simulating the signal-to-noise ratio (SNR) of received signals, you can determine whether
to trigger AM shifting on OptiX RTN 320.
6.4 Testing ATPC
OptiX RTN 320 supports the ATPC meter-free test.
6.5 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.6 Checking the Clock Status
Checking the clock status for all NEs on a microwave transmission network ensures that the
NE clocks are synchronized.
6.7 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.8 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, data communication
network (DCN) 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

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.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.
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.
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 GE1 on NE 1 to GE1 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 Create an MD.
Step 2 Create an MA.

Step 3 Create an MEP.
Step 4 Create a remote MEP.
Step 5 Perform an LB test.

Perform an LB test by considering the MEP whose ID is 1 as the source MEP and the MEP
whose ID is 2 as the sink MEP.

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 Check whether services are interrupted.
the 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
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
NOTE
The Web LCT does not support this operation.


The following procedure uses the Ethernet services from GE 1 port on NE 1 to GE 1 port on
NE 2 as an example, as shown in Figure 6-2.
Figure 6-2 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

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 AM Shifting

By simulating the signal-to-noise ratio (SNR) of received signals, you can determine whether
to trigger AM shifting on OptiX RTN 320.
Prerequisites
l The adaptive modulation (AM) 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 AM shifting function on an NE.
Procedure
Step 1 Testing One-Touch AM Switching.

----End
6.4 Testing ATPC

OptiX RTN 320 supports the ATPC meter-free test.
Prerequisites
l The ATPC function has been enabled for the microwave link to be tested, and the link is
normal.

U2000
NOTE
Context
The following procedure tests the ATPC function on a microwave link.
Procedure
Step 1

----End
6.5 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.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.
6.5.2 Testing 1+1 Protection Switching (Intra-equipment 1+1 Protection)
You can check the change of active and standby IF ports in a 1+1 protection group before and
after switching to check whether the 1+1 protection functions normally.
6.5.3 Testing 1+1 Protection Switching (Cascade 1+1 Protection)
You can verify the 1+1 protection functions by checking the changes of the main and standby
devices before and after switching.
6.5.4 Testing MPLS APS Protection Switching
By checking the change in the status of MPLS tunnels before and after the MPLS APS
switching, you can verify whether the MPLS APS protection function is normal.
6.5.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 320s 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 4 are protected by ERPS, and NE
2 is the RPL owner node.
Figure 6-3 Configuration for testing ERPS
Procedure
Step 1 Before switching, query the status of the ERPS protection group that is configured on NE 2.

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 IF2 port of NE4.
Step 4 After switching, query the status of the ERPS protection group that is configured on NE 2.

Step 5 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 6 Set TX Status to unmute for IF2 port of NE4.
----End
6.5.2 Testing 1+1 Protection Switching (Intra-equipment 1+1

Protection)
You can check the change of active and standby IF ports in a 1+1 protection group before and
after switching to check whether the 1+1 protection functions normally.
Prerequisites
l Antenna alignment has been completed.
l Ethernet services and 1+1 protection have been configured.

U2000

The basic configurations are as follows:
l Active IF port: IF1
l Standby IF port: IF2
NOTE
The following configuration steps adopt all the 1+1 protection, and take the 1+1 HSB as an example.

Figure 6-4 Test connection diagram
The Ethernet services protected by 1+1 hot standby (HSB) between NE 11 and NE 12 are
tested.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer. Choose Diagnosis & Maintenance >
One-Touch Test from the Function Tree.
Step 2 In Optional Acceptance Items, select HSB switching test
Step 3 Select the desired protection group from Available Protection Groups.
Step 4 Click Start.

After the test is complete, an HSB switching test report is displayed.
----End
6.5.3 Testing 1+1 Protection Switching (Cascade 1+1 Protection)

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

When the optical splitters are not used, the basic configurations are as follows:
l Main OptiX RTN 320s: NE 11 and NE 12
l Standby OptiX RTN 320s: NE 21 and NE 22
NOTE
The following configuration steps adopts all the 1+1 protection, and take the 1+1 HSB as an example.
The Ethernet services protected by 1+1 hot standby (HSB) between NE 11 and NE 12 shown
in Figure 6-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.
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 DMC4 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.
2. In Protection Group, select the desired protection group and click Query.
3. Ensure that Active NE of Device in Protection Group is NE 21.
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.4 Testing MPLS APS Protection Switching

By checking the change in the status of MPLS tunnels before and after the MPLS APS
switching, you can verify whether the MPLS APS protection function is normal.
Prerequisites
l The MPLS tunnel protection group must be created properly.

U2000
NOTE

1:1 protection
In normal situations, services are transmitted in the working tunnel. That is, services are
transmitted and received in a different tunnel respectively. When the working tunnel is faulty,
the equipment at the transmit end transmits services through the protection tunnel, and the
equipment at the receive end receive services through the protection tunnel after a negotiation
through the APS protocol. Therefore, service switching is realized.

Figure 6-6 shows the connection diagram for testing MPLS APS protection switching. NE A
and NE B are the OptiX RTN 320 NEs.
Figure 6-6 Connection diagram for testing the MPLS APS protection
Procedure
Step 1 Query the switching status of the current MPLS tunnel 1:1 protection group on NE A and NE
B.
1. In the NE Explorer, select NE A and then choose Configuration > APS Protection
Management from the Function Tree.
2. Click the Tunnel APS Management tab, right-click the tested protection group, and
then choose Query Switching Status from the shortcut menu, to check the MPLS
protection group configured on the NE.

3. Choose the protection group for switching, and check its switching status. In normal
situations, the switching status should be Normal, and Tunnel Status for both the
working and protection tunnels should be Available.
NOTE
If Tunnel Status for the working or protection tunnel is not Available, rectify tunnel-related faults.
Step 2 Switch the services to the protection tunnel manually and forcedly.
2. Click the Tunnel APS Management tab and choose the protection group for switching.
3. Right-click the tested protection group, and then choose Forced Switching from the
shortcut menu.
The Confirm dialog box is displayed.
4. Click OK.
The Operation Result dialog box is displayed.
5. Click Close.
Step 3 Query the switching status of the MPLS 1:1 protection groups on NE A and NE B after the
switching.

3. Right-click the tested protection group and then choose Query Switching Status from
the shortcut menu, to check Switching Status of the tunnel protection group.
In normal situations, the switching status should be Forced Switching.
4. Query Active Tunnel of the tunnel protection group.
In normal situation, Working should be Standby, and Protection should be Active.
NOTE
l If Forced Switching is performed at the previous step, the state of the protection group should be
Forced Switching.
l If Manual Switching to Protection is performed at the previous step, the state of the protection
group should be Manual (Working to Protection) Switching.
Step 4 Restore the services on NE A and NE B to the working tunnel.

3. Right-click the tested protection group and then choose Clear from the shortcut menu.
The Confirm dialog box is displayed.
4. Click OK.
The Operation Result dialog box is displayed.
5. Click Close.
6. Click Query.
Services is restored to the working tunnel.
----End
6.6 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.7 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.
3. For an XPIC group, the channels in the two polarization directions (H and V) are tested.
Therefore, the fading margins of the two OptiX RTN 320s are reported at the same time.
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.8 Testing Ethernet Service Performance

This section describes how to test Ethernet service performance using the NE-inherent test
functions.
6.8.1 Testing Ethernet Service Performance (Based on RFC 2544)
This section describes how to use RFC 2544-compliant functions to test the packet loss ratio,
delay, and throughput for Ethernet services.
6.8.2 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.
6.8.3 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.
6.8.1 Testing Ethernet Service Performance (Based on RFC 2544)

This section describes how to use RFC 2544-compliant functions to test the packet loss ratio,
delay, and throughput for Ethernet services.
Prerequisites
l The antennas have been aligned.
l Ethernet services have been configured.

U2000

NOTE
The OptiX RTN 380 that uses SHUF3 boards does not support services.
Context
NOTICE
l Performance tests for E-Line services, E-LAN services, and a mixture of E-Line and E-
LAN services are supported.
l During the test, do not modify any configuration.
l The ports at the ends of the Ethernet service to be tested must be Ethernet ports.
l During the test, only the tested Ethernet services at the tested port are interrupted in
normal cases.
l Large test traffic may affect other services and even cause packet loss of other services.
l An NE cannot function as an initiator and a reflector at the same time.
Connection Diagram for the Test

The test procedure takes the Ethernet service between NE A (PORT1) and NE B
(PORT2)Figure 6-7, as shown in , as an example. Ethernet services on NE A and NE B are E-
LAN.
NOTE
In an RFC 2544-compliant test on E-LAN services, the test initiator sends test packets or delay packets
at a specific traffic volume. The reflector end returns the packets based on the specific filter criteria (for
example, by VLAN and MAC address). The initiator end computes the network performance based on
the number of locally transmitted and received packets or timestamp information about delay packets.

Procedure
Step 1
----End
6.8.2 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
NOTICE
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), 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.
l For V100R006C00 and later versions, the tests are supported for intra-NE LAG/PLA/
EPLA-enabled microwave links, but are not supported for cascaded microwave links.
l Meter-free test results may be inaccurate if a warm/cold reset occurs during a test. In case
of a warm/cold reset, you need to initiate a second test.

The Ethernet services between GE1 on NE1 and GE on NE2 shown in Figure 6-8 are tested.
Both NE1 and NE2 are configured with VLAN-based E-Line services.
The Ethernet services between NE1 and NE2 carry the VLAN ID 100.
NOTE
The VLAN ID of the E-Line service to be tested must be the same as the default VLAN ID of the test port.
Otherwise, the source and sink NEs cannot be successfully created.
Procedure
Step 1 Disable the inband DCN of the test ports.
NE1 is used as an example:

Step 2 Disable the access control of the test ports.

NOTICE
This operation may cause DCN interruption.
Step 3 Configure the TAG attributes for the test ports.


Step 4 Configure a sink NE for the test.
Step 5 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.8.3 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
NOTICE
l Do not modify data configuration during the test.
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), 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.
l For V100R006C00 and later versions, the tests are supported for intra-NE LAGPLA/
EPLA-enabled microwave links, but are not supported for cascaded microwave links.
l Meter-free test results may be inaccurate if a warm/cold reset occurs during a test. In case
of a warm/cold reset, you need to initiate a second test.

The Ethernet services between GE1 on NE1 and GE1 on NE2 shown in Figure 6-9 are tested.
Both NE1 and NE2 are configured with VLAN-based E-Line services.

The Ethernet services between NE1 and NE2 carry the VLAN ID 100.
Procedure
Step 1 Disable the inband DCN of the test ports.
Step 2 Configure the TAG attributes for the test ports.


Step 3 Configure a sink NE for the test.
Step 4 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 Handling a Fault in Commissioning Script Loading Using a USB Flash Drive
This section describes how to handle the fault that occurs when some commands fail to be
loaded during the commissioning script loading using a USB flash drive.
7.2 Handling the Failure of the Receive Power to Meet the Design Requirements
This section describes how to handle the fault of receive power failing to meet the design
requirements.

7.1 Handling a Fault in Commissioning Script Loading

Using a USB Flash Drive
This section describes how to handle the fault that occurs when some commands fail to be
loaded during the commissioning script loading using a USB flash drive.
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 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 Handling the Failure of the Receive Power to 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 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.
Step 2 Check hardware installation and antenna alignment.
----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.
NOTE
This document describes the service configuration on the U2000-T.
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 initial configuration examples which are based on five network
scenarios and cover all operations in the 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 Ethernet Services
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 Common Service Configuration Operations
This section provides hyperlinks to common service configuration operations.

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.
8.1.2 Checking Configuration Conditions
Before beginning the configuration process, confirm that local conditions meet requirements.
8.1.3 U2000 Quick Start
This chapter describes basic operations on the U2000 client.
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 320 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.
l The gateway NE must log in to the computer where the U2000 software is installed.
8.1.3 U2000 Quick Start

This chapter describes basic operations on the U2000 client.
8.1.3.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.
8.1.3.2 Shutting Down a U2000 Client
Shut down a U2000 client when it will not to be used.
8.1.3.3 Using the Help
The Help provides help information about the U2000.
8.1.3.4 Navigating to Common Views
This section describes how to navigate to the common views of the U2000 and the functions
of the views.
8.1.3.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.

U2000
Procedure
Step 1
----End
8.1.3.2 Shutting Down a U2000 Client

Shut down a U2000 client when it will not to be used.

Prerequisites

U2000
Procedure
Step 1
----End
8.1.3.3 Using the Help

The Help provides help information about the U2000.
Prerequisites

U2000
Procedure
Step 1

----End
8.1.3.4 Navigating to Common Views

This section describes how to navigate to the common views of the U2000 and the functions
of the views.
8.1.3.4.1 Navigating to Main Topology
The U2000 provides the Main Topology view for network topology management.
8.1.3.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.
8.1.3.4.3 Navigating to the NE Panel
NE Panel displays the boards configured on an NE. Different colors represent different board
status.
8.1.3.4.1 Navigating to Main Topology

The U2000 provides the Main Topology view for network topology management.
Prerequisites

U2000
Procedure
Step 1

----End
8.1.3.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
Procedure
Step 1
----End

8.1.3.4.3 Navigating to the NE Panel

NE Panel displays the boards configured on an NE. Different colors represent different board
status.
Prerequisites

U2000
Context
The following procedure navigates to NE Panel.
Procedure
Step 1
----End
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 Ethernet Services Required.
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.
To prevent service interruption, first configure the clock and then configure services when configuring MIMO
links.

8.3 Common Network Scenarios of Configuration

Examples
This section provides the initial configuration examples which are based on five network
scenarios and cover all operations in the general configuration process.
8.3.1 Overview
This section provides the relationships between configuration examples and various networks.
8.3.2 Microwave Chain Network
A microwave chain network consists of three sites and three OptiX RTN 320s.
8.3.3 Microwave Ring Network
This section describes a microwave ring network consisting of four OptiX RTN 320 devices
located at four sites.
8.3.4 PTP Large Capacity Microwave Transmission Scenario
In this scenario, XPIC links with PLA or EPLA transparently transmit point-to-point Ethernet
services.
8.3.5 Microwave 1+1 Protection Scenario
In this scenario, two OptiX RTN 320s form a hop of 1+1 protection links.
8.3.6 NE Cascading Transmission Scenario
NE cascading transmission scenarios include the XPIC with 1+1 protection scenario and
cascade EPLA scenario.
8.3.1 Overview
This section provides the relationships between configuration examples and various networks.
NOTE
See the table below, √ indicates that a configuration example is provided and - indicates that no
configuration example is provided.
Table 8-2 Configuration examples for different networks

Operation Microw Microw PTP Microw XPIC Cascade
ave ave Large ave 1+1 with EPLA
Chain Ring Capacit Protecti 1+1 Scenari
Networ Networ y on Protecti o
k k Microw Transmi on
ave ssion Transmi
Transm Scenari ssion
ission o Scenari
Scenari o
o
Configure the √ - - - - -
network topology
Configure √ - √ √ √ √
microwave links

Operation Microw Microw PTP Microw XPIC Cascade

ave ave Large ave 1+1 with EPLA
Chain Ring Capacit Protecti 1+1 Scenari
Networ Networ y on Protecti o
k k Microw Transmi on
ave ssion Transmi
Transm Scenari ssion
ission o Scenari
Scenari o
o
Confi Transpar - - √ - - -
gure ently
Nativ transmitt
e ed point-
Ether to-point
net E-Line
servic service
es
VLAN- √ - - - - -
based E-
Line
service
IEEE - √ - - - -
802.1D
bridge-
based E-
LAN
service
IEEE √ - - - - -
802.1Q
bridge-
based E-
LAN
service
Confi Clock on √ - - - - -
gure a
the microwa
clock ve chain
network
Clock on - √ - - - -
a
microwa
ve ring
network
8.3.2 Microwave Chain Network

A microwave chain network consists of three sites and three OptiX RTN 320s.

Figure 8-2 shows the topology of the network. Ethernet services are received on NE2 and
NE3 and are transmitted to the local backhaul network through NE1.
Figure 8-2 Networking diagram for a microwave chain network
8.3.3 Microwave Ring Network

This section describes a microwave ring network consisting of four OptiX RTN 320 devices
located at four sites.
Figure 8-3 shows the topology of the network. Ethernet services are received on NE1 and
NE3 and are transmitted to the local backhaul network through NE2.

Figure 8-3 Networking diagram for a microwave ring network
8.3.4 PTP Large Capacity Microwave Transmission Scenario

In this scenario, XPIC links with PLA or EPLA transparently transmit point-to-point Ethernet
services.
Figure 8-4 shows the networking topology. On the chain network, NE1 is directly connected
to the Ethernet network, and services are sent to the RNC through NE2.
Figure 8-4 PTP large capacity microwave transmission network topology

NOTE
Large-capacity microwave links can be provided in the multiple-input multiple-output (MIMO)
scenario. For details about how to configure the MIMO scenario, see the Feature Configuration.
8.3.5 Microwave 1+1 Protection Scenario

In this scenario, two OptiX RTN 320s form a hop of 1+1 protection links.
As shown in Figure 8-5, the OptiX RTN 320 can provide 1+1 protection for backhaul links,
improving the reliability of aggregation sites.
Figure 8-5 Network topology in the microwave 1+1 protection scenario
8.3.6 NE Cascading Transmission Scenario

NE cascading transmission scenarios include the XPIC with 1+1 protection scenario and
cascade EPLA scenario.
Figure 8-6 shows the topology of the network. Both the master and slave OptiX RTN 320s
are used for service access. Inter-NE E-LAG is configured. This configuration mode provides
protection for microwave links, equipment, and access links.
Figure 8-6 Network topology in the NE cascading transmission scenario

NOTE
Connections in the XPIC with 1+1 protection scenario are the same as those in the cascade EPLA scenario.
Figure 8-7 4 x 4 MIMO scenario

RNC 1
NE1 NE3
RAN 1 LAG1 LAG1 V1 LAG1 LAG1
GE1(e) V1 1:V1 2:V1 GE1(e)
3:H1 4:H1 H1
H1
COMBO COMBO
COMBO 5:V2 6:V2 COMBO
RAN 2 V2 8:H2 V2
7:H2
GE2(e) H2 H2 GE2(e) LAG1 RNC 2

LAG1 NE2(Protection) NE4
Radio link Ethernet link
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.2 Configuration Process (Network Topology)
This section provides the process for configuring NEs, DCNs, and fibers/cables.
8.4.3 Configuration Example (Network Topology)
In this example, the default DCN solution (IP DCN solution) provided by the RTN 300 is
used.
8.4.1 Basic Concepts

Before configuring the network topology, familiarize yourself with the basic concepts.
8.4.1.1 Introduction to DCN

Through the data communication network (DCN), the NMS communicates with transmission
NEs to manage and maintain them.
8.4.1.2 IP DCN
This section describes the basic knowledge about IP DCN.
8.4.1.3 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.
8.4.1.4 Logical Boards
An integrated OptiX RTN 320 has two logical boards: DMC5 and ODU. The slot IDs for the
two logical boards are 1 and 51, respectively. A split OptiX RTN 320 has three logical boards:

DMC4 and two ODUs. The slot IDs for the three logical boards are 1, 51, and 52,
respectively.
8.4.1.1 Introduction to DCN

Through the data communication network (DCN), the NMS communicates with transmission
NEs to manage and maintain them.
DCN Composition
The DCN contains two types of node: NMS and NE. The DCN between the NMS and NEs is
called external DCN. The DCN among NEs is called internal DCN. The external DCN
consists of data communication devices, such as Ethernet switches and routers. The internal
DCN consists of NEs that are connected using DCN channels. Unless otherwise specified, the
DCN mentioned in this document refers to internal DCN.
DCN Channel
DCN channels fall into two types: outband DCN channel and inband DCN channel.
l Oubtband DCN channels do not occupy any service bandwidth. The RTN 300 supports
two types of outband DCN channel:
– D1 to D3 bytes in microwave frames
– Channels over NMS ports

l Inband DCN channels occupy some service bandwidth. The RTN 300 supports two types
of inband DCN channel:
– Some Ethernet service bandwidth of microwave links
– Some Ethernet service bandwidth of Ethernet links
NOTE
When inter-equipment 1+1 HSB or cascade EPLA is configured, the cascaded NEs use the inband DCN
to communicate.
DCN Solutions
The RTN 300 provides the following DCN solutions:
l IP DCN solution
In the IP DCN solution, network management messages are encapsulated into IP packets.
NEs forward the IP packets based on the IP addresses contained in them. This solution

supports a maximum of 400 NEs and ensures high network stability. This solution is the
default and preferred solution.
l L2 DCN solution
In the L2 DCN solution, network management messages are encapsulated into IP
packets, which are carried by Ethernet frames. NEs forward the Ethernet frames based
on the MAC addresses contained in them. This solution supports a maximum of 30 NEs.
However, this solution has the risk of broadcast packet flooding and provides poor
network stability.
The RTN 300 also supports the HWECC solution, which is eliminated gradually.

NE Types on the DCN

Two types of NE are available on the DCN: gateway NE and non-gateway NE.
Gateway NE: The application layer of the NMS directly communicates with the application
layer of a gateway NE. Generally, an NE at the boundary between the internal DCN and
external DCN is a gateway NE. An NE located inside a DCN can also function as a gateway
NE. The NEs between the NMS and the gateway NE inside a DCN forward DCN packets at
L2 or L3.
Non-gateway NE: The application layer of the NMS communications with the application
layer of a non-gateway NE through the application layer of a gateway NE. The NEs between
the gateway NE and non-gateway NE forward DCN packets at L2 or L3.
DCN Flags
An NE on the DCN must be configured with two DCN flags: NE ID and NE IP address.

An NE ID is used for application layer communication. An NE ID contains three bytes among

which the most significant byte represents the extended ID and the other two bytes represent
the basic ID. For example, if the extended ID is 9 and the basic ID is 1, the NE ID is
represented as 9-1.
An NE IP address is used for IP communication. By default, the NE IP address and NE ID of

an NE are associated. Specifically, the last three bytes of the NE IP address correspond to the
three bytes of the NE ID. For example, if an NE ID is changed to 9-1, the corresponding NE
IP address automatically changes to 129.9.0.1.
When an NE IP address is changed manually, the association relationship between the NE ID
and NE IP address becomes ineffective.
8.4.1.2 IP DCN
This section describes the basic knowledge about IP DCN.

Application of the IP DCN Solution

Huawei's IP DCN solution allows an NMS to manage NEs by encapsulating NMS messages
in the IP protocol stack and transmitting them over DCN channels between the NEs. This
solution is preferred if a network has only RTN 300s or a combination of RTN 300s and third-
party equipment supporting the IP protocol stack.
IP DCN Protocol Stack

To implement IP DCN, all NEs on the DCN must support the IP protocol stack. IP DCN uses
the standard TCP/IP protocol stack architecture.

l Layer 1 of the protocol stack is the physical layer, which provides data transmission
channels for data terminal equipment. The RTN 300 provides the following DCN
channels:
– NMS port: all the bandwidth at the NMS port
– DCC channel: three Huawei-defined DCC bytes in a microwave frame at a
microwave port
– Inband DCN: a portion of Ethernet service bandwidth at an Ethernet or a
microwave port
l Layer 2 is the data link layer, which provides reliable data transmission to the physical
link layer. DCCs and inband DCNs use the PPP protocol to set up data links. Therefore,
IP addresses of adjacent NEs do not need to be in the same IP network segment.
l Layer 3 is the network layer, which specifies the network layer address for a network
entity and provides forwarding and addressing functions. NEs implement network layer
functions using the IP protocol. The routes used for IP forwarding can be direct routes
discovered by link layer protocols, manually configured static routes, or dynamic routes
generated by the OSPF protocol. The RTN 300 provides various OSPF features; for
details, see Specifications.
l Layer 4 is the transport layer, which provides end-to-end communication services for the
upper layer. NEs support the TCP/UDP protocol.
Forwarding DCN Packets Based on the IP Protocol Stack

In IP DCN, the packets are forwarded in either gateway access mode or direct access mode.
In gateway access mode, the packets are forwarded as follows:
1. The NMS forwards application layer packets to the gateway NE through the TCP
connection.
2. The gateway NE extracts the packets from the TCP/IP protocol stack and delivers them
to the application layer.
3. The application layer of the gateway NE queries the NE ID carried by the packets. If the
NE ID is not the gateway NE's ID, the gateway NE queries the core routing table of the
application layer by the destination NE address to obtain the route to the destination NE
and the communication protocol stack of the transit NE. Because the transit NE uses the
IP protocol stack, the gateway NE transfers the packets to the transit NE through the IP
protocol stack.
4. The network layer of the transit NE queries the destination IP address of the packets. If
the address is not the transit NE's address, the transit NE queries the IP routing table to
obtain the route to the destination NE and then transfers the packets.
5. The network layer of the destination NE passes the packets to its application layer
through the transport layer only if the destination IP address of the packets is the same as
the IP address of the destination NE. The application layer then processes the packets.

In direct access mode, the packets are transferred in a different way.

The original gateway NE acts as an ordinary transit NE, and packets are transferred at the
network layer.

Traversing the L2 Network

In actual networking, the RTN 300 is often connects to a third-party L2 network. In this
scenario, IP DCN packets have to traverse the L2 network based on the access control
function at RTN 300's Ethernet ports.
A third-party L2 network may be located between the NMS and a network consisting of
OptiX RTN 300s or between two networks consisting of OptiX RTN 300s.
When the third-party L2 network is located between the NMS and the network comprised of
RTN 300s, the L2 network transmits Ethernet services and DCN packets between the NMS
and the gateway NE. In this example, the NMS uses the LAN switch to remove the VLAN ID
carried by NMS messages and the access control function is enabled on the Ethernet port of
the gateway NE. After the access control function is enabled:
l The Ethernet port functions as an Ethernet NMS port on the gateway NE.
l The IP address of the Ethernet port must be in the same network segment as that of the
NMS IP address and in a network segment different from that of NE IP addresses.
l The NMS communicates with the gateway NE based on the IP address of the Ethernet
port.
When the third-party L2 network is located between two networks comprised of RTN 300s,
NMS messages are encapsulated as L2 services for transmission. In this example, the access
control function is enabled on the Ethernet ports of the two networks for connecting to the
third-party L2 network and their IP addresses are in the same network segment.
The third-party L2 network creates a dedicated L2VPN service for the DCN packets carrying
a specific inband DCN VLAN ID.

8.4.1.3 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.
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.
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.4 Logical Boards

An integrated OptiX RTN 320 has two logical boards: DMC5 and ODU. The slot IDs for the
two logical boards are 1 and 51, respectively. A split OptiX RTN 320 has three logical boards:
DMC4 and two ODUs. The slot IDs for the three logical boards are 1, 51, and 52,
respectively.
NOTE
For a split OptiX RTN 320, the ODU is virtualized as a module of the DMC4 board. Alarms about the ODU
are reported by the DMC4 board. You can query the type (split or integrated) of an OptiX RTN 320 on the
U2000 by querying the subrack type of the NE.
8.4.2 Configuration Process (Network Topology)

This section provides the process for configuring NEs, DCNs, and fibers/cables.
Figure 8-8 shows the flowchart for configuring the network topology.

Figure 8-8 Flowchart for configuring the network topology
Required Start
Optional
Create an NE.
Set NE attributes.
Set the DCN .
Create fibers/cables.
End
NOTE
When the Web LCT is used for configuration, there is no need to create fibers/cables.
The steps in the configuration flowchart are described as follows:
Creating NEs
Table 8-3 Process of creating NEs

1 Creating NEs 8.8.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
Method
8.8.1.2 It is recommended that you perform this

Creating an operation to create NEs on the U2000 in
NE Manually other cases.

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

1 8.8.1.4 Required.
Changing an
NE ID
2 8.8.1.5 Optional.
Changing an
NE Name
Configuring DCN
Table 8-5 Process of configuring DCN

1 8.8.1.6 Setting the Required.

VLAN ID and If the VLAN ID and bandwidth planned for this
Bandwidth for an inband DCN do not assume their default values
Inband DCN (the default VLAN ID is 4094 and the default
bandwidth is 512 kbit/s).
2 8.8.1.7 Configuring Optional.

Access Control By default, access control is enabled for Ethernet
interfaces. Perform this step if you want to
modify the IP address or disable the function.
Creating Fibers/Cables
Table 8-6 Process of creating fibers/cables

1 Creating 8.8.1.8 It is recommended that you perform this operation

fibers/ Creating to create fibers/cables.
cables a Fiber/
Cable by
Using the
Search
Method

8.8.1.9 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
8.4.3 Configuration Example (Network Topology)

In this example, the default DCN solution (IP DCN solution) provided by the RTN 300 is
used.
8.4.3.1 Networking Diagram

This section describes the networking of NEs.
8.4.3.2 Configuration Procedure
This section describes the procedure for configuring a microwave chain network.

Figure 8-9 shows a microwave chain network configured according to the following
requirements:
l A microwave chain network consists of three sites and three OptiX RTN 320s, 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. NE1 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.

NOTE
l For the integrated OptiX RTN 320:

l On the NMS, the logical port of an IF1 port is 1-DMC5-1(IF1).
l On the NMS, the logical port of a GE1(e) electrical interface is 1-DMC5-3(GE1(e)).
l On the NMS, the logical port of an NMS/GE2(e) electrical interface is 1-DMC5-4(NMS/GE2(e)).
l On the NMS, the logical port of a GE3(o) optical interface is 1-DMC5-5(GE3(o)).
l On the NMS, the logical port of a COMBO port is 1-DMC5-6(COMBO).
l On the NMS, the logical port of a P&E port is 1-DMC5-7(P&E).
l For the split OptiX RTN 320:
The split OptiX RTN 320 is used as an example to describe the configuration. For the integrated OptiX RTN
320, the configuration is similar.


Data Preparation
Item Value in This Example Planning Principle
DCN l Use the IP DCN l The default IP DCN

solution. solution is
l Change the VLAN IDs recommended.
of all inband DCN l The VLAN ID of inband
channels to 4094 DCN channels must be
(default) and the different from service
bandwidth to 512 kbit/s VLAN IDs.
(default).
NE ID and NE IP address See the following figure. l Each NE must have a

unique NE ID and IP
address.
l If access control is
enabled for the port
connected to the NMS, it
is recommended to
maintain the correlation
between NE IP addresses
and NE IDs (by not
manually modifying NE
IP addresses). Modifying
an NE ID does not affect
the correlation between
the NE ID and the
corresponding IP address
of a non-gateway NE. If
the IP address of a non-
gateway NE is not
changed manually, the
NE automatically
changes the IP address to
be the planned value
after the NE ID is
changed. (For example,
it the NE ID is NE9-22,
the NE IP address is
automatically changed to
129.9.0.22.)
Gateway NE NE1 -

Access Control Access control is enabled on If access control is enabled

the GE(e) port (IP address: on the Ethernet port of the
10.0.0.1) of NE1. Access gateway NE, ensure that the
control is enabled for other IP address of this Ethernet
interfaces by default and the port is in the same network
setting is not modified. segment as the IP address of
the NMS but in a different
network segment from the
IP address of the gateway
NE.
Figure 8-10 Allocated IDs and IP addresses
Precautions
NOTE
If the NE ID and NE name are changed during commissioning on a per-NE basis, skip the operations.
Procedure
Step 1 Creating an NE by Using the Search Method.

NOTE
In this example, the IP address of the GE(e) interface of the gateway NE has been modified to the
planned value during NE commissioning.
Normally, the icons of NE1 to NE3 should be displayed on the main topology and all the NE
data should be uploaded successfully.
Step 2 Change an NE ID.
NE1 is used as an example.
Step 3 Change an NE Name.


Step 4 Configuring Access Control.
Step 5 Create a microwave link on the RTN subnet using the search method.
The microwave link between NE1 and NE2 is used as an example.
----End

8.5 Configuring Microwave Links

Before configuring services on a microwave link, you need to configure the microwave link.
8.5.1 Configuration Process (Microwave Links)
The core operation of configuring microwave links is managing a hop of microwave link.
8.5.2 Configuration Example (Microwave Links on a Chain Network)
This section describes how to configure 1+0 microwave links.
8.5.3 Configuration Example (Microwave Links with 1+1 Protection)
This section describes how to configure a microwave link hop configured with 1+1 HSB
protection.
8.5.4 Configuration Example ( XPIC Microwave links with PLA protection)
This section describes how to configure an XPIC microwave link configured with PLA
protection.
8.5.5 Configuration Example (4 x 4 MIMO Microwave Links)
This section describes how to configure 4 x 4 MIMO microwave links configured with a hop
of EPLA protection.
8.5.6 Configuration Example (XPIC Links with 1+1 Protection)
This section describes how to configure a hop of XPIC links with 1+1 protection.
8.5.7 Configuration Example (Cascade EPLA)
This section describes how to configure a hop of 4+0 EPLA links.
8.5.1 Configuration Process (Microwave Links)

The core operation of configuring microwave links is managing a hop of microwave link.
Configuring Microwave Links on Non-cascaded NEs

Figure 8-11 shows the flowchart for configuring microwave links.
Figure 8-11 Flowchart for configuring microwave links

Microwave links
Microwave Links with 1+1 XPIC microwave links with PLA or
with XPIC or
Protection intra-equipment EPLA protection
1+0 protection
Start Start Start
Release the QoS policy Configure a hop of Release the QoS policy
Required bound to a standby IF port microwave link. bound to a slave IF port
Optional
Create a microwave 1+1 Create a microwave link Configure a hop of
protection group after it is found. microwave link.
Configure a hop of End Create a PLA or intra-

microwave link. equipment EPLA protection
group
Create a microwave link

after it is found. Create a microwave link
after it is found.
End
End

NOTE
The preceding flowcharts provide basic processes of configuring microwave links.
Table 8-7 Process of configuring microwave links with 1+1 HSB\FD\SD protection
Operation Remarks
8.8.3.15 Releasing the QoS Policy Bound Required.

to an Interface
8.8.2.1 Creating a Microwave 1+1 Required.

Protection Group
8.8.2.2 Managing a Hop of Microwave Required.

Link
8.8.1.8 Creating a Fiber/Cable by Using In normal cases, Main Topology displays the
the Search Method previously created microwave links.
Table 8-8 Process of configuring microwave links with 1+0 or XPIC protection
Operation Remarks

Link
Table 8-9 Process of configuring XPIC links with PLA or intra-equipment EPLA
Operation Remarks

to an Interface

Link
8.8.2.4 Creating a PLA\EPLA Group Required.
Configuring Microwave Links on Cascaded NEs

Figure 8-12 shows the flowchart for configuring microwave links on cascaded NEs.

Figure 8-12 Flowchart for configuring microwave links

Microwave XPIC Links Microwave Links in a
with 1+1 Protection cascade EPLA group
Required Start Start
Optional
Release the QoS policy Release the QoS policy
bound to a standby IF port bound to a slave IF port
Configure a hop of Configure cascade EPLA

microwave link. group
Create a microwave 1+1

protection group. Configure a hop of
microwave link.
Synchronizing Data Between Create a microwave link

Main and Standby NEs after it is found.
Create a microwave link End

after it is found.
End
NOTE
The preceding flowcharts provide basic processes of configuring microwave links.
Table 8-10 Process of configuring XPIC links with 1+1 HSB protection
Operation Remarks
Releasing the QoS Policy Bound to a Required.

standby IF port
8.8.2.2 Managing a Hop of Required. Only the main NE needs to be

Microwave Link configured with a microwave link.
8.8.2.1 Creating a Microwave 1+1 Required.

Protection Group NOTE
Ensure that the 1+1 cascading port is not configured
with services. Otherwise, 1+1 protection configuration
will fail.

Operation Remarks
8.8.2.3 Synchronizing Data Between Configuration data is synchronized between the

Main and Standby NEs (1+1) main and standby NEs.
8.8.1.8 Creating a Fiber/Cable by In normal cases, Main Topology displays the

Using the Search Method previously created microwave links.
Table 8-11 Process of configuring microwave links in a cascade EPLA group

Operation Remarks
Releasing the QoS Policy bound to a Required.

slave IF port
Creating a 8.8.3.1 Creating a Required. Ensure that the EPLA cascade ports
microwave LAG are not configured with services. Otherwise,
EPLA PLA protection configuration will fail.
protection
group Required when configuring EPLA in LAG
mode.
Configure a LAG on each of the main OptiX
RTN 320s and each of the standby OptiX RTN
320s. The LAG has only one member port that
receives and transmits Ethernet services.
NOTE
Ensure that the EPLA cascading port is not configured
with services. Otherwise, EPLA protection
configuration will fail.
8.8.2.4 Creating a PLA Required.

\EPLA Group
8.8.2.2 Managing a Hop of Required.

Microwave Link
8.8.1.8 Creating a Fiber/Cable by In normal cases, Main Topology displays the

Using the Search Method previously created microwave links.
4x4 MIMO Microwave Link Configuration Mode

Figure 8-13 shows the procedure for configuring microwave links.

Figure 8-13 Procedure for configuring microwave links
Microwave Links in
4*4 MIMO
Required Start
Optional
Release the QoS policy
bound to a slave IF port
Configure a hop of
microwave link.
Create a microwave link

after it is found.
End
Table 8-12 Procedure for configuring 4 x 4 MIMO microwave links

Operation Remarks

to an Interface

Link
8.8.1.8 Creating a Fiber/Cable by Using In normal cases, Main Topology displays

the Search Method the previously created microwave links.

8.5.2 Configuration Example (Microwave Links on a Chain

Network)
This section describes how to configure 1+0 microwave links.

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

Configure the microwave links on the chain network according to the following requirements:
l Enable AM for all microwave links, because they carry Ethernet services.
l Table 8-13 provides the requirements on the services from NodeB 1 and RAN 1.
Table 8-13 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-14.
Table 8-14 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-14 Networking diagram for microwave links on a chain network
NOTE


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

Data Preparation
Figure 8-15 Microwave link configurations on a chain network
Context
NOTE
l The following procedure takes configuring the link between NE2 and NE3 as an example.
Configuring the link between NE1 and NE2 is similar.
l The following procedure configures basic information for the hop of microwave link shown in the
following figure by configuring NE3.
Procedure
Step 1

----End
8.5.3 Configuration Example (Microwave Links with 1+1

Protection)
This section describes how to configure a microwave link hop configured with 1+1 HSB
protection.

This section describes the procedure for configuring large-capacity backhaul microwave links
with 1+1 protection.

Figure 8-16 shows a hop of important microwave link. Two OptiX RTN 320 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 AM for the microwave links.
l Table 8-15 provides the requirements on the services from the RAN 1 and RAN 2.
Table 8-15 Capacity of services from RAN 1 and RAN 2

Service Capacity RAN 1 RAN 2



NOTE


services

Figure 8-16 Networking diagram for 1+1 HSB protection

NOTE


Data Preparation
Figure 8-17 Data Planning

Table 8-17 1+1 HSB plan

Item Value in This Example
Revertive Mode Revertive Mode (default value)
WTR Time 600s (default value)
Enable Reverse Switching Enabled (default value)
Working Board IF1
Protection Board IF2
NOTE
The following procedure takes configuring NE1 as an example.
Procedure
Step 1 Refer to 8.8.3.15 Releasing the QoS Policy Bound to an Interface, releasing the QoS Policy
bound to the standby IF port.
Step 2 Configure a microwave link hop configured with 1+1 HSB protection.
NOTE
The following procedure configures basic information for the hop of microwave link shown in the
----End
8.5.4 Configuration Example ( XPIC Microwave links with PLA

protection)
This section describes how to configure an XPIC microwave link configured with PLA
protection.


This section describes the procedure for configuration.

As shown in Figure 8-18, configure the microwave links according to the following
requirements.
l To increase the bandwidth for transmitting services from NodeB, enable the cross
polarization interference cancellation (XPIC) function for the microwave links between
NE1 and NE2.
l To balance the Ethernet bandwidth utilization on links, the Ethernet service transmission
channels in the two microwave links need to be bound as a single transmission channel
(namely, a PLA group).
Figure 8-18 Networking of XPIC links with PLA protection

NOTE


This section describes the procedure for configuration.
Data Preparation
NOTE

Procedure
bound to the slave interface.
Step 2 Configure a hop of microwave link.
take NE1 for example:
Step 3 Create a PLA protection group.

take NE1 for example:
----End
8.5.5 Configuration Example (4 x 4 MIMO Microwave Links)

This section describes how to configure 4 x 4 MIMO microwave links configured with a hop
of EPLA protection.


Figure 8-20 shows a hop of backbone microwave link. Two OptiX RTN 320 devices are
cascaded at the same site to backhaul two channels of GE Ethernet services for the
aggregation site where the OptiX RTN 900 is deployed. To increase bandwidth and reliability,
microwave links are configured in 4 x 4 MIMO mode.
Figure 8-20 4 x 4 MIMO networking

RNC 1
NE1 NE3
GE1(e) V1 1:V1 2:V1 GE1(e)
3:H1 4:H1 H1
H1
COMBO COMBO
RAN 2 V2 8:H2 V2
7:H2


Prerequisites

Data Preparation
Figure 8-21 4x4 MIMO link configuration parameters

IF Channel Bandwidth(MHz) 56MHz
AM Status
Guaranteed Capacity Enabled
Modulation QPSK
Full Capacity Modulation 256QAM
ATPC Enable Status Disabled
Maximum Transmit 18.0
Power(dBm) 15.0
TX Power(dBm) 13087.000
TX Frequency(MHz)
T/R Spacing(MHz) 266.000
TX Status unmute
RNC 1
NE1 NE3
GE1(e) V1 1:V1 2:V1 GE1(e)
3:H1 4:H1 H1
H1
COMBO COMBO
RAN 2 V2 8:H2 V2
7:H2

Procedure
Step 1
----End
8.5.6 Configuration Example (XPIC Links with 1+1 Protection)

This section describes how to configure a hop of XPIC links with 1+1 protection.



Figure 8-22 shows a hop of important microwave link. Two OptiX RTN 320 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.



NOTE


services


Figure 8-22 Network topology of XPIC links with 1+1 protection
NOTE



Data Preparation
Table 8-20 LAG plan

Static (default value) Configure the same aggregation

type at both ends. Static
LAG type aggregation is recommended.
Load sharing mode Non-Sharing (default value) Configure the same load sharing
mode at both ends. Configure a
load non-sharing LAG to provide
protection.
System priority 32768 (default value) The default value is recommended.

The system priority can be set only
in static aggregation.
Master ports l LAG1: GE1(e) It is recommended that you set the

l LAG2: GE2(e) main ports consistently for the
equipment at both ends.
Table 8-21 1+1 HSB plan

Service Protection Type LAG (default value) –

Revertive Mode Revertive Mode (default value) In 1+1 HSB protection, you can
initiate configuration
synchronization only on a main NE
in the working state. To ensure that
the working NE is the main NE,
"Revertive Mode" is recommended
here.
WTR Time 600s (default value) –
Enable Reverse Switching Enabled (default value) –
IF Port IF1 and IF2 –
Service Port GE1(e) and GE2(e) –
cascade Port Combo –
NOTE
Procedure
bound to the standby IF interface.
Step 2 Manage a hop of microwave link.

NOTE
Step 3 Configure a LAG for each Ethernet service access port on the main and standby NEs. This
step explains how to configure LAG1 on NE1 and NE3.

Step 4 Create a microwave 1+1 protection group on the main and standby NEs.
Step 5 Synchronize data between the main and standby NEs in the 1+1 protection group.
----End

8.5.7 Configuration Example (Cascade EPLA)

This section describes how to configure a hop of 4+0 EPLA links.


Figure 8-24 shows a hop of backbone microwave link. To improve the bandwidth and
reliability of microwave links for Ethernet service transmission, two OptiX RTN 320s at a site
can be enabled with XPIC and cascaded to form a 4+0 EPLA group.



NOTE

services


Figure 8-24 Network topology of a cascade EPLA group with XPIC enabled
NOTE



Data Preparation
38500M
Tx high station Tx Freq. 37300M
Tx low station Tx Freq.
Channel spacing 28M
Guaranteed AM Capacity QPSK
Full AM Capacity 64QAM
TX Power 10
Power to Be Received -20
RNC 1
RAN 1 NE1 NE3
GE1(e) H H GE1(e)
V V
GE2(e) GE2(e)
COMBO
COMBO
COMBO COMBO
RAN 2 XPIC&EPLA
H H RNC 2
V V
NE2 NE4
NOTE
Procedure
bound to the slave interface.
Step 2 Manage a hop of microwave link.
NOTE

Step 3 Create a cascading EPLA group.

Take NE1 for example:
----End
8.6 Configuring Ethernet Services

Ethernet services include Native Ethernet line (E-Line) services and Native Ethernet local
area network (E-LAN) services.
8.6.1 Ethernet Service Ports
Split OptiX RTN 320 provides 4 GE ports. Integrated OptiX RTN 320 provides 5 GE ports.
8.6.2 Ethernet Service Types
Native Ethernet services are classified into six types.
8.6.3 Configuration Process
The service configuration process differs according to the specific service type.
8.6.4 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.

8.6.5 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.
8.6.6 Configuration Example (IEEE 802.1D Bridge-based E-LAN Service)
This section provides an example of how to configure an IEEE 802.1D bridge-based E-LAN
service according to the plan.
8.6.7 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.
8.6.1 Ethernet Service Ports

Split OptiX RTN 320 provides 4 GE ports. Integrated OptiX RTN 320 provides 5 GE ports.
Figure 8-26 shows the physical Ethernet ports on the OptiX RTN 320. Table 8-24 provides
the logical ports and functions of physical Ethernet ports.
Figure 8-26 Ethernet ports on the OptiX RTN 320
Table 8-24 Description of Ethernet ports on the OptiX RTN 320

Physical Logical Port Description
Port
GE1(e) l Split OptiX A GE electrical port

RTN 320: 1-
DMC4-3,
(GE1
electrical)
l Integrated
OptiX RTN
320: 1-
DMC5-3
(GE1
electrical)

Physical Logical Port Description

Port
NMS/GE2(e) l Split OptiX An NMS port or a GE electrical port

RTN 320: 1-
DMC4-4
(NMS/GE2
electrical)
l Integrated
OptiX RTN
320: 1-
DMC5-4
(NMS/GE2
electrical)
GE3(o) l Split OptiX A GE optical port (SFP module)

RTN 320: 1-
DMC4-5
(GE3 optical)
l Integrated
OptiX RTN
320: 1-
DMC5-5
(GE3 optical)
COMBO l Split OptiX A GE optical port (SFP module)

RTN 320: 1-
DMC4-6
(COMBO)
l Integrated
OptiX RTN
320: 1-
DMC5-6
(COMBO)
P&E Integrated OptiX The P&E on an integrated OptiX RTN 320 can function as a GE electrical
RTN 320: 1- port.
DMC5-7 (P&E)
NOTE
l Split OptiX RTN 320 provides two IF ports, which correspond to two logical ports: 1-DMC4-1 (IF1) and
1-DMC4-2 (IF2), and two reserved MIMO ports.
l Integrated OptiX RTN 320 provides two IF ports, which correspond to two logical ports: 1-DMC5-1 (IF1)
and 1-DMC5-2 (IF2), and two reserved MIMO ports.
8.6.2 Ethernet Service Types

Native Ethernet services are classified into six 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.
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.
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.
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.
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.
8.6.2.6 802.1ad Bridge-based E-LAN Services
S-VLANs can be used to divide a bridge into sub-switching domains. Services from different
users are separated when they are transmitted in different sub-switching domains. These
services are called 802.1ad bridge-based E-LAN services.
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-25 describes the transparently transmitted point-to-point E-Line service model.
Table 8-25 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/QINQ The source port

NOTE PORT (sink) (source) processes the
In service model 2, 802.1Q/QINQ incoming Ethernet
ports process
(sink) frames based on
Ethernet frames their TAG attribute
based on their Tag
or QinQ-class
attribute or QinQ-
class domain. domain, and then
Therefore, service sends the processed
model 2 is not a real Ethernet frames to
transparent the sink port. The
transmission model sink port processes
and is not
the Ethernet frames
recommended.
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.
Typical Application
Figure 8-27 shows the typical application of transparently transmitted point-to-point E-Line
service model.
Figure 8-27 Typical application of Transparently transmitted point-to-point E-Line service

model
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 or QinQ-class domain. 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-26 provides information about the VLAN-based E-Line service model.
Table 8-26 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-28 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-28 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-27 shows the QinQ-based E-Line service models.
Table 8-27 QinQ-based E-Line service models

Service Service Flow Service Port Encapsulation Service Description
Model Direction Mode
Model 1 PORT (source) UNI-NNI Null (source) The source port adds the S-
QinQ link (sink) QinQ (sink) VLAN tag that corresponds
to the QinQ link to all the
received 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 (source) UNI-NNI 802.1Q (source) The source port processes
QinQ link (sink) QinQ (sink) Ethernet frames according
to the Tag attribute. It adds
the S-VLAN tag that
corresponds to the QinQ
link to all the Ethernet
frames, and then transmits
the Ethernet frames to the
sink port where the QinQ
link configured.
Model 3 PORT+C-VLAN UNI-NNI 802.1Q (source) The source port processes

list (source) QinQ (sink) Ethernet frames according
QinQ link (sink) to the Tag attribute. It adds
the S-VLAN tag that
corresponds to the C-VLAN
to all the Ethernet frames,
and then transmits the
Ethernet frames to the sink
port where the QinQ link
configured.
Model 4(1) PORT+S-VLAN UNI-UNI QinQ (source) The source port transmits
list (source) QinQ (sink) the Ethernet frames that
PORT+S-VLAN carry a specific S-VLAN tag
list (sink) (corresponding to the source
QinQ) to the sink port to
which the sink QinQ is
connected.
Model 4(2) QinQ link NNI-NNI QinQ (source) The source port transmits
(source) QinQ (sink) the Ethernet frames that
QinQ link (sink) carry a specific S-VLAN tag
(corresponding to the source
QinQ link) to the sink port
to which the sink QinQ link
is connected. If the source
and sink QinQ links have
different S-VLAN tags, S-
VLAN tag swapping occurs.
Typical Application
Figure 8-29 shows the typical application of service model 1.
Service 1 and service 2 contain tagged frames and untagged frames. 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.
Figure 8-29 Typical application of service model 1

NE 1 NE 2
Port 1 Port 1
E-Line Transmission E-Line
Service 1 Port 3 Port 3 Service 1
Network
Service 2 e E-Lin Service 2
E-Lin e
Port 2 Port 2
Strip S-VLAN Label Add S-VLAN Label Add S-VLAN Label Strip S-VLAN Label
Data( 1) S-VLAN(300) Data(1) S-VLAN(300) Data(1) Data(1)
Data(2) S-VLAN(400) Data(2) S-VLAN(400) Data(2) Data(2)
Service 1 and service 2 carry different unknown C-VLAN tags. Service 1 is 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.

Strip S-VLAN Label Add S-VLAN Label
C-VLAN Data( 1) S-VLAN(300) C-VLAN Data(1)
C-VLAN Data(2) S-VLAN(400) C-VLAN Data(2)
NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
Port 3 Transmission Port 3 E-Line Service 1
Unknown CVLAN Network Unknown CVLAN
Unknown CVLAN E-Lin e Unknown CVLAN
Port 2 Port 2
Add S-VLAN Label Strip S-VLAN Label
S-VLAN(300) C-VLAN Data(1) C-VLAN Data( 1)
S-VLAN(400) C-VLAN Data(2) C-VLAN Data(2)
Service 1 and service 2 carry different C-VLAN tags. Service 1 is 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.


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
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)

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

Switching S-VLAN Label
S-VLAN(100) Data( 1) S-VLAN(300) Data(1)
S-VLAN(100) Data(2) S-VLAN(400) Data(2)
NE 1 NE 2
Port 1 Port 1
E-Line
Service 1
Port 3 Transmission Port 3 E-Line Service 1
S-VLAN ID: 100 Network S-VLAN ID: 100
S-VLAN ID: 100 Port 2 E-Lin e
Port 2 S-VLAN ID: 100
Switching S-VLAN Label
S-VLAN(300) Data( 1) S-VLAN(100) Data(1)
S-VLAN(400) Data(2) S-VLAN(100) 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-28 shows the IEEE 802.1D bridge-based E-LAN service model.

Table 8-28 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-Transparent Null PORT SVL None

bridge-based E-
LAN service
Typical Application
Figure 8-33 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-33 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-29 provides information about the IEEE 802.1Q bridge-based E-LAN service model.

Table 8-29 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

bridge-based E- VLAN learning divided into
LAN service (IVL) switching sub-
domains by
VLAN
NOTE
The maximum number of VLANs supported by the configured for all the Ethernet services is fixed to 1024. If
more than 1024 VLANs are bound to a V-UNI, the logical type of the V-UNI must be PORT, and a VLAN
filtering table must be created to restrict E–LAN services transmitted from the V-UNI.
Typical Application
Figure 8-34 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-34 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 VLAN 100 Port 2 Service 2
VLAN ID: 200 VLAN ID: 100
Domain 1
(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.2.6 802.1ad Bridge-based E-LAN Services

S-VLANs can be used to divide a bridge into sub-switching domains. Services from different
users are separated when they are transmitted in different sub-switching domains. These
services are called 802.1ad bridge-based E-LAN services.

Service Model
Table 8-30 shows the 802.1ad bridge-based E-LAN service model.
Table 8-30 802.1ad bridge-based E-LAN service model

Service Model TAG Learning Sub-switching Logical Port Encapsulation
Attribute Mode Domain Type Mode at a
Port
802.1ad bridge- S-Aware IVL A bridge is PORT (UNI Null or 802.1Q

based E-LAN divided into port)
service sub-switching
domains based PORT+C- 802.1Q
on S-VLAN VLAN list
tags. (UNI port)
PORT+S- QinQ
VLAN list
(NNI port)
NOTE
The maximum number of VLANs supported by the configured for all the Ethernet services is fixed to 1024. If
more than 1024 VLANs are bound to a V-UNI, the logical type of the V-UNI must be PORT, and a VLAN
filtering table must be created to restrict E–LAN services transmitted from the V-UNI.
Typical Application
Figure 8-35 shows the typical application of the 802.1ad bridge-based E-LAN service model.
NE2 and N3 receive services G and H and send them to the convergence node NE1. Services
G and H carry a same C-VLAN tag, so S-VLAN tags are added for differentiating and
separating these services.

Figure 8-35 Typical application of the 802.1ad bridge-based E-LAN service model
NE 2
Add S-VLAN tag Strip S-VLAN tag
S-VLAN(300) C-VLAN(100) Data(G) C-VLAN(100) Data( G)
S-VLAN(400) C-VLAN(100) Data(H) C-VLAN(100) Data(H)
NE 2
SVLAN 300
Port 1
User G2
CVLAN 100
Port 3
SVLAN 400
NE 1 Port 2
Transmission User H2
SVLAN 300 Network CVLAN 100
Port 1 Port 3
User G1 802.1ad
CVLAN 100 bridge
SVLAN 400
NE 3
Port 2
User H1
CVLAN 100 Port 4 SVLAN 300
Transmission
Port 1
802.1ad Network
User G3
bridge CVLAN 100
SVLAN 400
Port 3 Port 2
NE 1 User H3
CVLAN 100
Strip S-VLAN tag Add S-VLAN tag
802.1ad
C-VLAN(100) Data( G) S-VLAN(300) C-VLAN(100) Data(G)
bridge
C-VLAN(100) Data(H) S-VLAN(400) C-VLAN(100) Data(H)
NE 3
Add S-VLAN tag Strip S-VLAN tag
S-VLAN(300) C-VLAN(100) Data(G) C-VLAN(100) Data( G)
S-VLAN(400) C-VLAN(100) Data(H) C-VLAN(100) Data(H)
NOTE
You can also configure 8.6.2.3 QinQ-Based E-Line Services on NE2 and NE3 for service access.
8.6.3 Configuration Process

The service configuration process differs according to the specific service type.
8.6.3.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point E-Line

Services)
This section describes the processes of configuring the service 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.
8.6.3.2 End-to-End Configuration Process (Transparently Transmitted Point-to-Point E-Line
Service)
This section describes the process of configuring a transparently transmitted point-to-point E-
Line service in an end-to-end manner. The process includes configuring E-Line service
information and QoS and verifying service configurations.
8.6.3.3 Per-NE Configuration Process (VLAN-based E-Line Services)

service (QoS) information for a VLAN-based Ethernet line (E-Line) service and the process
of verifying the service configurations.
8.6.3.4 End-to-End Configuration Process (VLAN-based E-Line Service)
This section describes the process of configuring a VLAN-based E-Line service in an end-to-
end manner. The process includes configuring E-Line service information and QoS and
verifying service configurations.
8.6.3.5 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)
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.
8.6.3.6 End-to-End Configuration Process (IEEE 802.1D Bridge-Based E-LAN Service)
This section describes the process of configuring an IEEE 802.1D bridge-based E-LAN
service in an end-to-end manner. The process includes configuring E-LAN service
8.6.3.7 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)
service (QoS) information for an IEEE 802.1Q bridge-based Ethernet local area network (E-
8.6.3.8 End-to-End Configuration Process (IEEE 802.1Q Bridge-based E-LAN Service)
This section describes the process of configuring an IEEE 802.1Q bridge-based E-LAN
8.6.3.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point

E-Line Services)
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-36 shows the flowchart for configuring transparently transmitted point-to-point E-
Line services.

Figure 8-36 Flowchart for configuring transparently transmitted point-to-point E-Line

services
Required Start
Optional
Configure LAGs.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
Synchronize 1+1
configurations.
End
Configuring LAGs
Table 8-31 Process of configuring LAGs

Operation Remarks
8.8.3.1 Creating a LAG Required when Ethernet ports need to use LAGs.

Configuring Transparently Transmitted Point-to-Point E-Line Services
Table 8-32 Process of configuring transparently transmitted point-to-point E-Line services

Operation Remarks
8.8.3.4 Creating a Point-to- Required.

Point Transparently
Transmitted E-Line
Service
Configuring QoS
Table 8-33 Process of configuring QoS

Operation Remarks
8.8.3.11 Modifying the Required if the default mappings for the Differentiated
Mapping for a DS Domain Services (DS) domain are inapplicable.
8.8.3.12 Changing the Required if the priority type of an Ethernet service is not
Packet Type Trusted by a CVLAN, which is the default packet type trusted by the
Port DiffServ domain.
8.8.3.13 Enabling/ If DSCP-based DiffServ is enabled and if you do not want

Disabling DSCP the DSCP values to be changed by demapping at egress
Demapping at an Egress ports, you can disable DSCP demapping.
Port
8.8.3.14 Setting Egress Required if a port is required to schedule traffic according

Queue Scheduling Policies to a certain queue scheduling policy in the case of traffic
congestion. The default queue scheduling mode is SP
+WRR (SP is short for strict priority and WRR for weighted
round robin). AF1 to AF4 queues are WRR queues
(allocated the same weight) and the other queues are SP
queues.
Verifying Ethernet Service Configurations
Table 8-34 Process of verifying Ethernet service configurations

Operation Remarks
Testing Ethernet Services The connectivity of Ethernet services is verified using an

Configured on a Per NE Ethernet OAM test.
Basis

Synchronizing 1+1 Configurations
Table 8-35 Process of synchronizing 1+1 configurations

Operation Remarks
8.8.2.3 Synchronizing Data Optional. When links in a cascade 1+1 protection group
Between Main and carry Ethernet services, perform this operation to
Standby NEs (1+1) synchronize service configurations on the active NE to the
standby NE.
8.6.3.2 End-to-End Configuration Process (Transparently Transmitted Point-to-

Point E-Line Service)
This section describes the process of configuring a transparently transmitted point-to-point E-
Line service in an end-to-end manner. The process includes configuring E-Line service
Flowchart
Figure 8-37 shows the flowchart for configuring a transparently transmitted point-to-point E-
Line service.
Figure 8-37 Flowchart for configuring a transparently transmitted point-to-point E-Line

service
Required Start
Optional
Configure LAGs.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
Synchronize 1+1
configurations.
End

The operations in the configuration flowchart are described as follows.
Configuring LAGs

Operation Remarks
Configuring a Transparently Transmitted Point-to-Point E-Line Service
Table 8-37 Process of configuring a transparently transmitted point-to-point E-Line service

Operation Remarks
8.8.1.8 Creating a Fiber/Cable Optical. Perform this operation to create microwave

by Using the Search Method links or Ethernet fibers/cables for the service path if
they have not been created on the topology of the
U2000.
8.8.4.2 Creating a Required.

Transparently Transmitted
Point-to-Point E-Line Service
Configuring QoS

Operation Remarks

Port

Operation Remarks

queues.
Verifying Service Configurations
Table 8-39 Process of verifying the service configurations
Operation Remarks
8.6.4.7 End-to- Perform an Ethernet OAM test to verify the connectivity of the Ethernet
End service.
Configuration
Procedure
(Verifying
Service
Configurations
)
Operation Remarks
standby NE.
8.6.3.3 Per-NE Configuration Process (VLAN-based E-Line Services)

service (QoS) information for a VLAN-based Ethernet line (E-Line) service and the process
of verifying the service configurations.
Flowchart
Figure 8-38 shows the flowchart for configuring VLAN-based E-Line services.

Figure 8-38 Flowchart for configuring VLAN-based E-Line services
Required Start
Optional
Configure LAGs.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
Synchronize 1+1
configurations.
End
Configuring LAGs

Operation Remarks
Configuring VLAN-based E-Line Services
Table 8-42 Process of configuring VLAN-based E-Line services

Operation Remarks
8.8.3.5 Creating a VLAN- Required.

based E-Line Service

Configuring QoS

Operation Remarks

Port

queues.

Operation Remarks

Basis

Operation Remarks
standby NE.

8.6.3.4 End-to-End Configuration Process (VLAN-based E-Line Service)

This section describes the process of configuring a VLAN-based E-Line service in an end-to-
end manner. The process includes configuring E-Line service information and QoS and
verifying service configurations.
Flowchart
Figure 8-39 shows the flowchart for configuring a VLAN-based E-Line service.
Figure 8-39 Flowchart for configuring a VLAN-based E-Line service
Required Start
Optional
Configure LAGs.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
Synchronize 1+1
configurations.
End
Configuring LAGs

Operation Remarks

Configuring a VLAN-based E-Line Service
Table 8-47 Process of configuring a VLAN-based E-Line service

Operation Remarks
8.8.1.8 Creating a Fiber/Cable Perform this operation to create microwave links or

by Using the Search Method Ethernet fibers/cables for the service path if they have
not been created on the topology of the U2000.
8.8.4.3 Creating a VLAN-based Required.

E-Line Service
Configuring QoS

Operation Remarks

Port

queues.


Operation Remarks
End service.
Configuration
Procedure
(Verifying
Service
Configurations
)

Operation Remarks
standby NE.
8.6.3.5 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)

service (QoS) information for an IEEE 802.1D bridge-based Ethernet local area network (E-
Flowchart
Figure 8-40 shows the flowchart for configuring IEEE 802.1D bridge-based E-LAN services.

Figure 8-40 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services
Required
Start
Optional
Configure Ethernet Protection
Configure E-LAN services.
Configure QoS.
Verify Ethernet services.
Synchronize 1+1
configurations.
End
NOTE
The flowchart provides the basic process of configuring E-LAN services. In addition, configuring
MSTP, split horizon groups, and MAC address entries may be required. For details about these
operations, see the Feature Configuration Guide
Configuring Ethernet Protection
Table 8-51 Process of configuring ethernet protection

Operation Remarks
8.8.3.2 Creating an ERPS Required.

Instance

Configuring IEEE 802.1D Bridge-based E-LAN Services
Table 8-52 Process of configuring IEEE 802.1D bridge-based E-LAN services

Operation Remarks
8.8.3.6 Creating an IEEE Required.

802.1D Bridge-based E-
LAN Service
Configuring QoS

Operation Remarks

Port

queues.

Operation Remarks

Basis


Operation Remarks
standby NE.
8.6.3.6 End-to-End Configuration Process (IEEE 802.1D Bridge-Based E-LAN

Service)
This section describes the process of configuring an IEEE 802.1D bridge-based E-LAN
Flowchart
Figure 8-41 shows the flowchart for configuring an IEEE 802.1D bridge-based E-LAN
service.
Figure 8-41 Flowchart for configuring an IEEE 802.1D bridge-based E-LAN service
Required
Start
Optional
Configure Ethernet Protection
Configure E-LAN services.
Configure QoS.
Verify Ethernet services.
Synchronize 1+1
configurations.
End

Operation Remarks
8.8.3.1 Required when Ethernet ports need to use LAGs.

Creating a
LAG
8.8.3.2 Required when Ethernet services need to use ERPS.

Creating an
ERPS Instance
Configuring an IEEE 802.1D Bridge-based E-LAN Service
Table 8-57 Process of configuring an IEEE 802.1D bridge-based E-LAN service
Operation Remarks
8.8.1.8 Creating a Fiber/Cable Perform this operation to create microwave links or

by Using the Search Method Ethernet fibers/cables for the service path if they have
not been created on the topology of the U2000.

802.1D Bridge-based E-LAN
Service
Configuring QoS
Operation Remarks

Port

Operation Remarks

queues.
Operation Remarks
End service.
Configuration
Procedure
(Ethernet
Service
Verification)
Operation Remarks
standby NE.
8.6.3.7 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)

service (QoS) information for an IEEE 802.1Q bridge-based Ethernet local area network (E-
Flowchart
Figure 8-42 shows the flowchart for configuring IEEE 802.1Q bridge-based E-LAN services.

Figure 8-42 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services
Required
Start
Optional
Configure Ethernet
Protection
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
Synchronize 1+1
configurations.
End
NOTE

Operation Remarks
8.8.3.2 Creating an ERPS Required.

Instance

Configuring IEEE 802.1Q Bridge-based E-LAN Services
Table 8-62 Process of configuring IEEE 802.1Q bridge-based E-LAN services

Operation Remarks

802.1Q Bridge-based E-
LAN Service
Configuring QoS

Operation Remarks

Port

queues.

Operation Remarks

Basis


Operation Remarks
standby NE.
8.6.3.8 End-to-End Configuration Process (IEEE 802.1Q Bridge-based E-LAN

Service)
This section describes the process of configuring an IEEE 802.1Q bridge-based E-LAN
Flowchart
Figure 8-43 shows the flowchart for configuring an IEEE 802.1Q bridge-based E-LAN
service.
Figure 8-43 Flowchart for configuring an IEEE 802.1Q bridge-based E-LAN service
Required
Start
Optional
Configure Ethernet
Protection
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
Synchronize 1+1
configurations.
End

NOTE
Operation Remarks
8.8.3.1 Required when Ethernet ports need to use LAGs.

Creating a
LAG
8.8.3.2 Required when Ethernet services need to use ERPS.

Creating an
ERPS Instance
Configuring an IEEE 802.1Q Bridge-based E-LAN Service
Table 8-67 Process of configuring an IEEE 802.1Q bridge-based E-LAN service
Operation Remarks
8.8.1.8 Perform this operation to create microwave links or Ethernet fibers/

Creating a cables for the service path if they have not been created on the topology
Fiber/Cable by of the U2000.
Using the
Search Method
8.8.4.5 Required.
Creating an Set parameters according to the service plan and parameter plan.
IEEE 802.1Q
Bridge-based
E-LAN Service
Configuring QoS
Operation Remarks

Operation Remarks

Port

queues.

Operation Remarks
End service.
Configuration
Procedure
(Verifying
Service
Configurations
)

Operation Remarks
standby NE.

8.6.4 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.

8.6.4.2 Procedure of Configuration on a Per-NE Basis (Service Information)
This section describes the procedure for configuring service information.
8.6.4.3 Procedure of Configuration on a Per-NE Basis (QoS)
This section describes the procedure for configuring quality of service (QoS).
8.6.4.4 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification)
This section describes the procedure for verifying Ethernet service configurations.
8.6.4.5 End-to-End Configuration Procedure (Configuring Service Information)
This section describes the procedure for configuring Ethernet service information.
8.6.4.6 End-to-End Configuration Procedure (QoS)
8.6.4.7 End-to-End Configuration Procedure (Verifying Service Configurations)
This section describes how to verify Ethernet service configurations.

As Figure 8-44 illustrates, NE1 is a terminal station of a backhaul network. The service
requirements are as follows:
l NE2 must transparently transmit the Ethernet services from the NodeB to NE1 in point-
to-point manner.
l The priorities of Ethernet services transmitted over a microwave network are 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-44 Networking diagram for transparently transmitted point-to-point E-Line services

NOTE
In this example, it is assumed that XPIC and PLA have been configured for the microwave links, and only
Ethernet services need to be configured between NE1 and NE2.
NOTE


Data Preparation
Procedure
Step 1 Create a Point-to-Point Transparently Transmitted E-Line Service.

----End

Data Preparation
Mapping between DSCP See the following figure. l DiffServ configuration

values, PHBs, and queue should be the same for
scheduling modes each service port.
l If the type of packets
trusted by service ports is
DSCP, enabling DSCP
demapping function for
egress ports of a DS
domain is not required,
as the DSCP demapping
function may change
DSCP values.

Procedure
Step 1 Modify the mapping for a DS domain.
Step 2 Change the packet type trusted by a port.


Step 3 Disable DSCP demapping at an egress port.

Step 4 Set egress queue scheduling policies.


----End
8.6.4.4 Procedure of Configuration on a Per-NE Basis (Ethernet Service

Verification)
Data Preparation
NOTE
This section describes how to test the connectivity of the Ethernet service over the microwave link between
NE1 and NE2.
Procedure


Step 5 LB test.
Perform an LB test by considering the MP whose ID is 1 as the source MP and the MP whose
ID is 2 as the sink MP.


----End


Data Preparation
Data Value in This Example Planning Guidelines
Service information l Service name: l Set names for E-Line

NE1toNE2 services according to the
l Source: NE1 (GE1(e)) network plan.
l Sink: NE2 (GE1(e)) l Leave the VLAN IDs
empty for the source and
sink NEs of transparently
transmitted point-to-
point E-Line services.
Port information Retain the default settings l Enable ports.

for all ports. l Set Encapsulation Type
to null.
l It is recommended that
you set Working Mode
to Autonegotiation.
Prerequisites
Ethernet fibers/cables and microwave links have been searched out in the operation of 8.4
Configuring the Network Topology.
Procedure
Step 1 Create a transparently transmitted point-to-point E-Line service.
----End


Data Preparation

DSCP, enabling DSCP
function may change
DSCP values.
Procedure





----End

Context
In this example, ETH OAM is configured during the service information configuration.
Therefore, you can perform an LB test to verify service configurations.
Procedure
Step 1 Verify Ethernet service configurations.
The service NE1toNE2 is used as an example.
----End

8.6.5 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.3.2 Microwave Chain Network and the following
requirements.
Table 8-71 Service requirements
Requirement Description Requirement Satisfaction
Servic Configure a port working in NE 2 and NE 3 provide an electrical P&E port

e auto-negotiation mode for for receiving services.
access receiving a channel of
capaci electrical GE signals from
ty NodeB 1.
Servic No -
e
protec
tion
Servic Separate services from NodeB Configure VLAN-based E-Line services on

e 1 and RAN 1 from each other NE1, NE2, and NE3.
separa using VLAN IDs:
tion l VLAN ID of NodeB 1: 100
l VLAN ID of RAN 1: 200

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-45 Networking diagram for VLAN-based E-Line services

NOTE


Data Preparation

Procedure
Step 1 Create a VLAN-based E-Line Service.
----End

Data Preparation

DSCP, enabling DSCP
function may change
DSCP values.

Procedure





----End

Verification)
Data Preparation
NOTE
NE1 and NE2.
Procedure


Step 5 LB test.


----End


Context
This section describes the procedure for configuring an Ethernet service between NodeB 1
and the RNC in end-to-end mode. The procedure for configuring an Ethernet service between
RAN 1 and the RNC is similar.
Data Preparation
Data Value in This Example Planning Guidelines
Service information Service information l Set names for

configured on NodeB 1: networkwide E-Line
l Service name: services according to the
NE1toNE4 network plan.
l Source: NE1 (GE1(e)) l Set the same VLAN ID
for the source and sink
l Sink: NE4 (GE1(e)) NEs.
l VLAN ID: 100
Service information
configured on RAN 1:
l Service name:
NE1toNE2
l Source: NE1 (GE1(e))
l Sink: NE2 (GE1(e))
l VLAN ID: 200
Port information l Encapsulation Type: l Enable ports.

802.1Q l For a port that carries
l Working Mode: VLAN-based E-Line
Autonegotiation services, set
Encapsulation Type to
802.1Q.
l It is recommended that
you set Working Mode
to Autonegotiation.
Prerequisites
Procedure
Step 1 Create a VLAN-based E-Line service.
The RAN 1 service is used as an example.

----End

Data Preparation

DSCP, enabling DSCP
function may change
DSCP values.

Procedure





----End

Context
Procedure
Step 1 Verify Ethernet service configurations.
----End

8.6.6 Configuration Example (IEEE 802.1D Bridge-based E-LAN

Service)
This section provides an example of how to configure an IEEE 802.1D bridge-based E-LAN
service according to the plan.

8.6.6.2 Per-NE Configuration Procedure (Ethernet Protection)
This section describes the procedure for configuring Ethernet protection.
8.6.6.3 Per-NE Configuration Procedure (Service Information)
8.6.6.4 Per-NE Configuration Procedure (QoS)
8.6.6.5 Per-NE Configuration Procedure (Ethernet Service Verification)
8.6.6.6 End-to-EndConfiguration Procedure (Ethernet Protection)
8.6.6.7 End-to-End Configuration Procedure (Service Information)
8.6.6.9 End-to-End Configuration Procedure (Ethernet Service Verification)

Configure Ethernet services according to 8.3.3 Microwave Ring Network and the following
requirements.
Servic Support the backhaul of one l Configure IEEE 802.1D bridge-based

e GE electrical signal from Ethernet local area network (E-LAN)
access NodeB 1 and NodeB 2 services.
capaci respectively. The port mode is l Configure Ethernet ring protection switching
ty auto-negotiation. (ERPS).
Servic Configure protection for
e Ethernet services on ring
protec networks.
tion

Servic Ethernet services from NodeB

e 1 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
services.
Figure 8-46 Networking diagram for IEEE 802.1D bridge-based E-LAN services

NOTE

8.6.6.2 Per-NE Configuration Procedure (Ethernet Protection)

Data Preparation
Procedure
Step 1

----End
8.6.6.3 Per-NE Configuration Procedure (Service Information)

Data Preparation
Procedure
Step 1 Creating an IEEE 802.1d Bridge-based E-LAN Service.

----End
8.6.6.4 Per-NE Configuration Procedure (QoS)

Data Preparation

Procedure




----End
8.6.6.5 Per-NE Configuration Procedure (Ethernet Service Verification)

Data Preparation
NOTE
NE1 and NE2.

Procedure

Step 5 LB test.



----End
8.6.6.6 End-to-EndConfiguration Procedure (Ethernet Protection)

Data Preparation
Procedure
Step 1

----End

Data Preparation
Procedure
Step 1 Creating an IEEE 802.1d Bridge-based E-Line Service.

----End

Data Preparation

Procedure



----End
8.6.6.9 End-to-End Configuration Procedure (Ethernet Service Verification)

Context
Procedure
Step 1 Verify the Ethernet service configuration.

----End
8.6.7 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.


Configure Ethernet services according to 8.3.2 Microwave Chain Network and the following
requirements.


Servic Configure a port working in The NE2 and NE3 provides an electrical P&E
e auto-negotiation mode for port for receiving services.
access receiving a channel of
capaci electrical GE signals from
ty NodeB 1.
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 Configure IEEE 802.1Q bridge-based E-LAN
e 1 and RAN 1 from each other services for NE1, NE2, and NE3.
separa using VLAN IDs:
tion l VLAN ID of NodeB 1: 100
l VLAN ID of RAN 1: 200
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
services.

Figure 8-47 Networking diagram for IEEE 802.1q bridge-based E-LAN services
NOTE



Data Preparation
Procedure
Step 1 Creating an IEEE 802.1Q Bridge-based E-LAN Service.
----End


Data Preparation

DSCP, enabling DSCP
function may change
DSCP values.
Procedure





----End

Verification)
Data Preparation
NOTE
NE1 and NE2.
Procedure


Step 5 LB test.


----End


Data Preparation
Prerequisites
Procedure
Step 1 Create an IEEE 802.1Q bridge-based E-LAN service.

----End

Data Preparation

DSCP, enabling DSCP
function may change
DSCP values.

Procedure





----End

Context
Procedure
Step 1 Verify service configurations.
----End

8.7 Configuring Clocks

8.7.1 Configuration Process (Configuring a Clock)
This section describes the process of configuring the clock source, clock protection, and
output clock.
8.7.2 Configuration Example (Clock on a Microwave Chain Network)
This section describes how to configure clocks on a microwave chain network.
8.7.3 Configuration Example (Clock on a Microwave Ring Network)
This section describes how to configure clocks on a microwave ring network.
8.7.4 Configuration Example (Clock on an NE Cascading Transmission Network)
This section describes how to configure clocks on an NE cascading transmission network.
8.7.1 Configuration Process (Configuring a Clock)

This section describes the process of configuring the clock source, clock protection, and
output clock.
Figure 8-48 shows the flowchart for configuring a clock.
Figure 8-48 Flowchart for configuring a clock
Required Start
Optional
Configure clock sources.
Configure standard SSM or

extended SSM protection.
Configure a clock source

group.
Query the clock

synchronization status.
End

Table 8-74 Process of configuring the clock
Step Operatio Remarks

n
1 8.8.5.1 Required. Set parameters as follows:

Configuri Set Clock Source according to clock source planning
ng the information.
System
Clock
Source
2 8.8.5.2 Required when the SSM or extended SSM protection is

Configuri used. Set parameters as follows:
ng l Set Protection Status according to the used protocol
Protection type.
for Clock
Sources l If the clock uses the extended SSM protection, set Clock
Source ID for the following clock sources:
– Internal clock source of the NE that connects the
intersecting ring and chain or connects the
intersecting rings
– Line clock source that is accessed to the ring through
the NE that connects the intersecting ring and chain or
connects the intersecting rings and is configured with
the line clock source on the ring
The values of Clock Source ID for these clock sources
should be different.
3 8.8.5.3 Optional.
Configuri
ng a
Clock
Source
Group
4 6.6 Optional.
Checking
the Clock
Status
8.7.2 Configuration Example (Clock on a Microwave Chain

Network)
This section describes how to configure clocks on a microwave chain network.

This section describes the procedure for configuring clock on a microwave chain network.


Configure the clock for the network shown in Figure 8-49 according to 8.5.2 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(e) ports.

NOTE


Data Preparation
Item Value in This Example Planning Principles
Clock source information See the following figure. You need to configure an
Ethernet clock source for
each link.
Clock protection Not in use. In this example, a chain

network is set up. Therefore,
only priority-based clock
source protection is used
and the standard SSM or
extended SSM protection is
not used.

NOTE
The following procedure takes configuring clocks on NE1 as an example. Configuring clocks on other
NEs is similar.
Procedure
Step 1 Configure the clock source.
Step 2 Query the clock synchronization status.
NE Clock Mode must be Tracing Mode for all NEs.

----End
8.7.3 Configuration Example (Clock on a Microwave Ring

Network)
This section describes how to configure clocks on a microwave ring network.

This section describes the procedure for configuring clocks.

Configure clocks according to the following requirements. Figure 8-51 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 the GE1(e) port.

Figure 8-51 Networking diagram (clocks on a microwave ring network)
NOTE


This section describes the procedure for configuring clocks.

Data Preparation
Clock source information See the following figure. –
Clock protection Standard SSM In this example, a ring

network is set up. Therefore,
the standard SSM or
extended SSM protection is
used.
NOTE
The following procedure takes configuring clocks on NE1 as an example. Configuring clocks on other
NEs is similar.
Procedure
Step 1 Configure the clock sources.

Step 2 Configure protection for the clock sources.

----End

8.7.4 Configuration Example (Clock on an NE Cascading

Transmission Network)
This section describes how to configure clocks on an NE cascading transmission network.

Configure clocks according to the following requirements. Figure 8-53 shows the networking
diagram.
l Synchronize an NE cascading network with the clock of the RNC.
l Provide clock signals to NodeB and RAN through GE(e) ports.
Figure 8-53 Networking diagram for an NE cascading transmission network
NE1
RAN 1 LAG1 LAG1
GE1(e) V1 1:V1 2:V1
3:H1 4:H1
H1
COMBO
COMBO 5:V2 6:V2
RAN 2 V2 8:H2
7:H2
GE2(e) H2
LAG1 NE2(Protection)
Radio link Ethernet lin

NOTE


Data Preparation
Clock source information See the following figure. You need to configure an
Ethernet clock source for
each link.
Clock protection Not in use. This network is an NE

cascading transmission
network. Only clock source
priority protection is
enabled, and SSM and
extended SSM are not
enabled.

Clock Priority Clock Priority

IF1 GE1(e)
RNC
Internal Internal
NE1 NE3
GE1(e) V1 1:V1 2:V1 GE1(e)
3:H1 4:H1 H1
H1
COMBO COMBO

RAN 2 V2 V2
7:H2 8:H2
GE2(e) H2 H2 GE2(e) LAG1

LAG1 NE2 NE4
Clock Priority
Clock Priority
IF2
GE2(e)
Internal
Internal
NOTE
The following procedure takes configuring clocks on NE3 as an example. Configuring clocks on other NEs is
similar.
Procedure
Step 1 Configure the clock source.


----End
8.8 Common Service Configuration Operations

This section provides hyperlinks to common service configuration operations.
8.8.1 Configuring the Network Topology

This section provides hyperlinks to common operations of network topology configuration.
8.8.2 Configuring Microwave Links
This section provides videos to common operations of microwave link configuration.
8.8.3 Configuring Ethernet Services on a Per-NE Basis
This section provides hyperlinks to common operations of configuring Ethernet services on a
per-NE basis.
8.8.4 Configuring Ethernet Services (in End-to-End Mode)
This section provides hyperlinks to common operations of configuring Ethernet services in an
end-to-end mode.
8.8.5 Configuring Clocks
8.8.1 Configuring the Network Topology

This section provides hyperlinks to common operations of network topology configuration.
8.8.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.
8.8.1.2 Creating an NE Manually
If you create NEs manually, you can create them one by one instead of in batches.

8.8.1.3 Configuring Logical Interfaces

If the optical port does not have an Ethernet SFP module or functions as a cascade port, delete
the logical interface.
8.8.1.4 Changing an NE ID
8.8.1.5 Changing an NE Name
8.8.1.6 Setting the VLAN ID and Bandwidth for an Inband DCN
8.8.1.7 Configuring Access Control
When an NE is connected to the network management system (NMS) using an Ethernet
service port, you must configure access control.
8.8.1.8 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.
8.8.1.9 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.
8.8.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 (U2000).
Step 2 Create an NE by using the NE Search method (Web LCT).
----End
8.8.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
NOTE
If new NEs are created manually on the Web LCT:

l SSL is recommended for communication with NEs. Set the port number to 5432 and perform the
following steps to replace the SSL certificate:
l Delete the WebLCT\conf\certificate directory on the Web LCT.
l Copy the server\etc\ssl\nemanager\default directory on the U2000 to the path WebLCT\conf on the
Web LCT. Rename default to certificate. Note that the installation path on the Web LCT should not
contain Chinese characters, spaces, or special characters.
l Restart the Web LCT.
l Install the SSL certificate to the NE using the U2000. For details, see the Security Configuration
Maintenance & Hardening.
Context
The following procedure creates NE1 manually.
Procedure
Step 1 Creating an NE manually
----End
8.8.1.3 Configuring Logical Interfaces

If the optical port does not have an Ethernet SFP module or functions as a cascade port, delete
the logical interface.
Prerequisites
l The U2000 communicates properly with the NE to be created.
l Before deleting the logical interface, delete services on the interface and the QoS policy
bound to the interface. 8.8.3.15 Releasing the QoS Policy Bound to an Interface
describes how to delete the QoS policy bound to an interface.

Context
The following steps delete the logical interface of a COMBO port.
Procedure
Step 1
----End
8.8.1.4 Changing an NE ID
Prerequisites
You must be an NM user with NE maintainer authority or higher.

U2000
NOTE
Context
The following procedure changes an NE ID to the planned value listed in the following table.
Parameter Value
New ID 1
New Extended ID 9
After changing the NE ID, you need to relog in to the NE.

Procedure
Step 1 Changing an NE ID
----End
8.8.1.5 Changing an NE Name

Prerequisites

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

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

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 4094
Bandwidth(Kbit/s) 512Kbit/s
Procedure
Step 1 Setting the VLAN ID and Bandwidth for an Inband DCN

----End
8.8.1.7 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
Precautions
NOTE
l Do not use the default IP address of an access control interface to access the public network (for example,
Internet).
l The default IP address is a temporary address and is only used for the DCN plug-and-play of the NE.
Users must modify the default IP address in a timely manner.
Context
The following procedure configures the access control function for the port GE1(e) according
to the planned parameter values listed in the following table.
Parameter Value
Enabled Status Enabled (default value)
IP Address 10.0.0.1
Subnet Mask 255.255.0.0

Procedure
Step 1 Configuring Access Control
----End
8.8.1.8 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
8.8.1.9 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-2
Source NE NE(9-40775)
Source NE Subrack-Slot-Board Type-Port 1-DMC4-1(IF)
Sink NE NE(9-40776)
Sink NE Subrack-Slot-Board Type-Port 1-DMC4-1(IF)
Automatically Allocate IP Address No
Procedure
Step 1
----End
8.8.2 Configuring Microwave Links

This section provides videos to common operations of microwave link configuration.
8.8.2.1 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.
8.8.2.2 Managing a Hop of Microwave Link
This task helps you manage microwave links by hop.
8.8.2.3 Synchronizing Data Between Main and Standby NEs (1+1)

This section describes how to synchronize data between the main and standby NEs in a 1+1
HSB protection group.
8.8.2.4 Creating a PLA\EPLA Group
When physical link aggregation (PLA\EPLA) is required to improve Ethernet service
bandwidth or reliability on microwave links, you need to create a PLA\EPLA group.
8.8.2.1 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 For 1+1 protection in LAG mode, you must configure E-LAG first.
l The GE ports connected by a cascade port must be configured with the same port type.
For example, both are configured with "COMBO".

U2000
NOTE
Context
The following procedure creates a microwave 1+1 protection group according to planned
values provided in the following table.
l Create an intra-equipment microwave 1+1 protection group according to values provided

Parameter Value
Reversion Mode Revertive Mode
WTR Time (s) 600 (default value)
Enable Reverse Switching Enable
Working Port IF1
Protection Port IF2
l Create 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

Parameter Value
Working/Protection Unit Type Working Unit
IF Port IF1 and IF2
Service Port GE1(e) and GE2(e)
cascade Port COMBO
l Create a microwave 1+1 protection group in Split Mode according to planned values
provided in the following table.
Parameter Value
Service Protection Type Optical Splitter Mode
Working/Protection Unit Type Working Unit
IF Port IF1
Service Port GE3(o) and COMBO
cascade Port GE1(e)
Procedure
Step 1 Create an intra-equipment microwave 1+1 protection group

Step 2 Create a microwave 1+1 protection group in LAG Mode.
Step 3 Create a microwave 1+1 protection group in Split Mode.
----End
8.8.2.2 Managing a Hop of Microwave Link

This task helps you manage microwave links by hop.
Prerequisites
l The NEs at the two ends of a microwave link hop are communicating properly.

U2000
NOTE

Precautions
The following procedure configures basic information for the hop of microwave link shown in
the following figure by configuring NE1.
Parameter Link
Link ID 1
IF Channel Bandwidth 56MHz
AM Enabled
Guaranteed AM Capacity 32QAM/204Mbit/s
Full AM Capacity 256QAM/350Mbit/s
TX Frequency(MHz) 14551.0
T/R Spacing(MHz) 644
ATPC Disabled
TX power (dBm) 10
Power to Be Frequency(dBm) -10
TX Status unmute
Procedure
Step 1
----End

8.8.2.3 Synchronizing Data Between Main and Standby NEs (1+1)

This section describes how to synchronize data between the main and standby NEs in a 1+1
HSB protection group.
Prerequisites
l The GE ports connected by a cascade port must be configured with the same port type.
For example, both are configured with "COMBO".
l You can initiate configuration synchronization only on a main NE in the working state.
l If both NEs are in the working or protection state, you cannot initiate configuration
synchronization.

U2000
NOTE
Procedure
Step 1
----End
8.8.2.4 Creating a PLA\EPLA Group

When physical link aggregation (PLA\EPLA) is required to improve Ethernet service
bandwidth or reliability on microwave links, you need to create a PLA\EPLA group.
Prerequisites
l No Ethernet service has been configured on the slave NE if a EPLA group without NE-
level protection will be created.

l The cascade ports on the two NEs to be configured as the master and slave NEs in a
EPLA group are configured with no Ethernet service.

U2000
Context
l Create a PLA group according to the planned parameter values listed in the following
table.
Parameter Value
Master Port IF1
Slave Port IF2
l Create a cascading EPLA group according to the planned parameter values listed in the
following table
Parameter Value
Protection Type No NE-level protection
NE Role Master
IF Port IF
Service Port GE1(e), GE2(e)
Cascade Port COMBO-1, COMBO-2
Procedure
Step 1 Create a PLA group.

Step 2 Create a cascading EPLA group.
----End
8.8.3 Configuring Ethernet Services on a Per-NE Basis

This section provides hyperlinks to common operations of configuring Ethernet services on a
per-NE basis.
8.8.3.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).
8.8.3.2 Creating an ERPS Instance
Ethernet ring protection switching (ERPS) is configured by creating ERPS instances.
8.8.3.3 Setting Protocol Parameters for an ERPS Instance
Protocol parameters set for an ERPS instance take effect only to the ERPS instance.
8.8.3.4 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.
8.8.3.5 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.
8.8.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.
8.8.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.
8.8.3.8 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.
8.8.3.9 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.

8.8.3.10 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.
8.8.3.11 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.
8.8.3.12 Changing the Packet Type Trusted by a Port
This section describes how to set the packet type trusted by a port.
8.8.3.13 Enabling/Disabling DSCP Demapping at an Egress Port
If DSCP-based Diffserv is enabled and if you do not want the DSCP values to be changed by
demapping at egress ports, you can disable DSCP demapping.
8.8.3.14 Setting Egress Queue Scheduling Policies
This section describes how to set queue scheduling policies for an egress port.
8.8.3.15 Releasing the QoS Policy Bound to an Interface
8.8.3.16 Restoring an Ethernet Port Configured as an NMS Port to a Service Port
By default, the GE2(e) port is configured as an NMS port. Before configuring services on the
GE2(e) port, restore it to a service port.
8.8.3.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 Create 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 LAG1
LAG Type Static (default value)
Load Sharing Non-Sharing

Parameter NE
LAG Priority 32768 (default value)
Packet Receive Timeout Period Long period
Main Ports GE1(e)
Standby Ports GE2(e)
l Create a load sharing LAG to increase Ethernet bandwidth of Ethernet links, according
to the planned parameter values listed in the following table.
Parameter NE
LAG No. Assign Automatically
LAG Name LAG1
LAG Type Static (default value)
Load Sharing Sharing
LAG Priority 32768 (default value)
Packet Receive Timeout Period Long period
LAG Min Active Link Threshold 2
Main Ports GE1(e)
Standby Ports GE2(e)
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 GE1(e)
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.
----End

8.8.3.2 Creating an ERPS Instance

Ethernet ring protection switching (ERPS) is configured by creating ERPS instances.
Prerequisites

U2000
NOTE
Context
The following procedure creates an ERPS instance according to the planned parameter values
Parameter Value
ERPS ID 1
East Port IF2
West Port IF1
RPL Owner Ring Node Flag RPL Port
RPL Port IF2
Control VLAN 4093
Procedure
Step 1
----End

8.8.3.3 Setting Protocol Parameters for an ERPS Instance

Protocol parameters set for an ERPS instance take effect only to the ERPS instance.
Prerequisites
l Ethernet boards and IF boards have been added to the NE Panel.

U2000
NOTE
NOTE
In this task, you can set Compatible_Version, Virtual Channel Status, Virtual Channel VLANs, and
Major ERPS Ring ID, and query or modify other ERPS instance protocol parameters.
l For multi-ring networks, Compatible_Version for all ring nodes must be ver2.
l Only the sub-ring node on an interconnection node supports Major ERPS Ring ID, which associates the
sub-ring with the major ring.
Procedure
Step 1
----End
8.8.3.4 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.
Procedure
Step 1
----End


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.
Prerequisites

U2000
NOTE
Context
The following procedure creates the VLAN-based E-Line service shown in the following
figure.
Procedure
Step 1
----End


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.
Procedure
Step 1

----End

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.

Procedure
Step 1
----End
8.8.3.8 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
l Ethernet local area network (E-LAN) services have been configured.

U2000
NOTE
Context
The following steps remove port IF1, from the ports mounted with E-LAN services.
Procedure
Step 1

----End
8.8.3.9 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
8.8.3.10 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
8.8.3.11 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 MPLS EXP IP DSCP PHB
Default value Default value 0-7 BE
8-15 AF11
16-23 AF21
24-31 AF31
32-39 AF41
40-47 EF

CVLAN MPLS EXP IP DSCP PHB
48-55 CS6
56-63 CS7
Procedure
Step 1
----End
8.8.3.12 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.
Parameter Packet Type
IF1 ip-dscp

Parameter Packet Type
IF2
GE1(e)
GE2(e)
GE3(o)
COMBO
Procedure
Step 1
----End
8.8.3.13 Enabling/Disabling DSCP Demapping at an Egress Port

If DSCP-based Diffserv is enabled and if you do not want the DSCP values to be changed by
demapping at egress ports, you can disable DSCP demapping.
Prerequisites

U2000
NOTE
Context
The following procedure sets Egress DSCP Mapping Status to Disabled.

Procedure
Step 1
----End
8.8.3.14 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 to the planned parameter values listed in the following table.
Parameter Grooming Policy After Reloading
CS7 SP
CS6 SP
EF SP
AF4 SP
AF3 WRR(weight=25)
AF2 WRR(weight=25)

Parameter Grooming Policy After Reloading
AF1 WRR(weight=25)
BE WRR(weight=25)
Procedure
Step 1
----End
8.8.3.15 Releasing the QoS Policy Bound to an Interface

Prerequisites

U2000
NOTE
Context
The following steps release the QoS policy bound to a COMBO port.
Procedure
Step 1

----End
8.8.3.16 Restoring an Ethernet Port Configured as an NMS Port to a Service Port

By default, the GE2(e) port is configured as an NMS port. Before configuring services on the
GE2(e) port, restore it to a service port.
Prerequisites

U2000
NOTE
Context
The following steps restore the GE2(e) port configured as an NMS port to a service port.
Procedure
Step 1

----End
8.8.4 Configuring Ethernet Services (in End-to-End Mode)

This section provides hyperlinks to common operations of configuring Ethernet services in an
end-to-end mode.
8.8.4.1 Searching for Native Ethernet Services

By searching for native Ethernet services, you can synchronize the configured native Ethernet
service data from the NE layer of the NMS to the network layer.
8.8.4.2 Creating a Transparently Transmitted Point-to-Point E-Line Service
This section describes how to configure a transparently transmitted point-to-point E-Line
service in an end-to-end manner.
This section describes how to create a VLAN-based E-Line service in an end-to-end manner.
This section describes how to configure an IEEE 802.1D bridge-based E-LAN service in an
end-to-end manner.
This section describes how to configure an IEEE 802.1Q bridge-based E-LAN service in an
end-to-end manner.
8.8.4.1 Searching for Native Ethernet Services

By searching for native Ethernet services, you can synchronize the configured native Ethernet
service data from the NE layer of the NMS to the network layer.
Prerequisites
l Native Ethernet services have been correctly configured.
l Configuration data on the NMS is the same as that on NEs.


U2000
NOTE
Precautions
l Verify that cables have been created between the NEs on the topology.
l This task searches for native Ethernet services that have been correctly configured but
for which no topologies have been created at the network layer of the NMS. For native
Ethernet services for which topologies have been created at the network layer of the
NMS, skip this task.
Context
The following procedure synchronizes the native E-LAN services in a specified area to the
network layer of the NMS.
Procedure
Step 1
----End
8.8.4.2 Creating a Transparently Transmitted Point-to-Point E-Line Service

This section describes how to configure a transparently transmitted point-to-point E-Line
service in an end-to-end manner.
Prerequisites
l Fiber/Cable connections have been created between NEs in the main topology.


U2000
NOTE
Context
The following procedure creates a transparently transmitted point-to-point E-Line service
according to the planned parameter values listed in the following table.
Parameter Value
Service name NE1toNE2
Source NE NE1
Source port GE1(e)
Sink NE NE2
Sink port GE1(e)
Procedure
Step 1
----End

This section describes how to create a VLAN-based E-Line service in an end-to-end manner.

Prerequisites

U2000
NOTE
Context
The following procedure creates a VLAN-based E-Line service according to the planned
parameter values listed in the following table.
Parameter Value
Service name NE1toNE2
Source NE NE1
Source port GE1(e)
Source C-VLAN 200
Sink NE NE2
Sink port GE1(e)
Sink C-VLAN 200
Procedure
Step 1

----End

This section describes how to configure an IEEE 802.1D bridge-based E-LAN service in an
end-to-end manner.
Prerequisites

U2000
NOTE
Context
The following procedure creates an IEEE 802.1D bridge-based E-LAN service according to
the planned parameter values listed in the following tables.
Table 8-75 Basic information
Parameter Value
Service Type E-LAN
Service Name E-LAN

Table 8-76 Information about mounted ports
Parameter NE1 NE2 NE3 NE4
Ports mounted GE1(e) IF1 GE1(e) IF1

to a bridge IF1 IF2 IF1 IF2
IF2 IF2
Procedure
Step 1
----End

This section describes how to configure an IEEE 802.1Q bridge-based E-LAN service in an
end-to-end manner.
Prerequisites

U2000
NOTE

Context
The following procedure creates an IEEE 802.1Q bridge-based E-LAN service according to
the planned parameter values listed in the following tables.
Table 8-77 Service information

Parameter NE1 NE2 NE3
Ports mounted to a GE1(e) (VLAN ID: IF2 (VLAN ID: GE1(e) (VLAN ID:
bridge 100,200) 100,200) 100)
IF1 (VLAN ID: IF1 (VLAN ID:100) IF1 (VLAN ID:100)
100,200) GE1(e) (VLAN ID:
200)
Procedure
Step 1
----End
8.8.5 Configuring Clocks

8.8.5.1 Configuring the System Clock Source
This task helps you to change the default clock source of OptiX RTN 320.
8.8.5.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.

8.8.5.3 Configuring a Clock Source Group

If multiple links between two NEs form a ring, clock source groups must be configured on the
two NEs to prevent clock loops.
8.8.5.1 Configuring the System Clock Source

This task helps you to change the default clock source of OptiX RTN 320.
Prerequisites

U2000
NOTE
Context
The following steps configure interface as the clock source with the highest priority.
Procedure
Step 1 Configuring the system clock source.
----End
8.8.5.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 GE1(e) 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
8.8.5.3 Configuring a Clock Source Group

If multiple links between two NEs form a ring, clock source groups must be configured on the
two NEs to prevent clock loops.
Prerequisites
l Clock sources have been configured.
l Standard SSM protocol have been configured.

U2000
NOTE
Context
The following steps configure two clock sources as a group.
Procedure
Step 1

----End


RTN 320 V100R007C00 Commissioning and Configuration Guide 02

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RTN 320 V100R007C00 Commissioning and Configuration Guide 02

Transféré par

Droits d'auteur :

Formats disponibles

OptiX RTN 320 Radio Transmission System

Commissioning and Configuration

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2016-11-30) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 320 V100R007C00

iManager U2000–T V200R016C50

iManager U2000–M V200R016C00

This document is intended for:

l Installation and commissioning engineers

Indicates an imminently hazardous situation

Indicates a potentially hazardous situation

Issue 02 (2016-11-30) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Calls attention to important information,

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.

Issue 02 (2016-11-30) 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

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Updates in Issue 02 (2016-11-30) Based on Product Version V100R007C00

— Fixed the known bugs.

Updates in Issue 01 (2016-04-30) Based on Product Version V100R007C00

Issue 02 (2016-11-30) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

Issue 02 (2016-11-30) Huawei Proprietary and Confidential v

4 Site Commissioning (Using a USB Flash Drive to Configure Data)................................. 44

5 Site Commissioning (Using the Web LCT to Configure Data).......................................... 53

Issue 02 (2016-11-30) Huawei Proprietary and Confidential vi

6.6 Checking the Clock Status..........................................................................................................................................108

7 Handling of Common Faults During Site Deployment.................................................... 121

8 Configuring Networkwide Service Data.............................................................................. 124

Issue 02 (2016-11-30) Huawei Proprietary and Confidential vii

8.5.2.1 Networking Diagram............................................................................................................................................ 161

Issue 02 (2016-11-30) Huawei Proprietary and Confidential viii

8.6.4.7 End-to-End Configuration Procedure (Verifying Service Configurations).......................................................... 227

Issue 02 (2016-11-30) Huawei Proprietary and Confidential ix

8.8.1.3 Configuring Logical Interfaces.............................................................................................................................285

Issue 02 (2016-11-30) Huawei Proprietary and Confidential x

About This Chapter

1.1 General Safety Precautions

Issue 02 (2016-11-30) Huawei Proprietary and Confidential 1

1.1 General Safety Precautions

All Safety Precautions

Local Laws and Regulations

Basic Installation Requirements

Issue 02 (2016-11-30) Huawei Proprietary and Confidential 2

1.2 Warning and Safety Symbols

ESD protection label Indicates that the equipment is

Radiation warning label Indicates that the equipment

High temperature warning label Indicates that the equipment

Grounding label Indicates the grounding position