RTN 320&320F Commissioning and Configuration Guide (V100R021C10 - 02) (PDF) - en

OptiX RTN 320&320F Radio Transmission System
V100R021C10
Commissioning and Configuration

Guide
Issue 02
Date 2022-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. 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: https://www.huawei.com
Email: support@huawei.com
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. i

Commissioning and Configuration Guide About This Document
About This Document
Product Versions
The following table lists the product versions related to this document.
Product Name Product Version
OptiX RTN 320/320F V100R021C10
iMaster NCE V100R021C10
NOTE
For products of V100R019C00 or a later version, use the iMaster NCE/Web LCT. The Web
LCT is running the same software version as the iMaster NCE.
Intended Audience
This document describes how to commission OptiX RTN 320/320F, including
preparations, site commissioning, system commissioning, and network-wide
service data configuration.
This document is intended for:
● Installation and commissioning engineers

● Data configuration engineers
● System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. ii

Symbol Description
Indicates a hazard with a medium level of risk which, if not

avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not

avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation 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.
Command Conventions
The command conventions that may be found in this document are defined as
follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are

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

vertical bars. One item can be 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.
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. iii

Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog

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

the ">" signs. For example, choose File > Create >
Folder.
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Product Version V100R021C10 - Issue 02 (2022-09-30)

This is the second release for V100R021C10.
This issue includes the following changes.
Topic Description
- Fixed the known bugs.
Product Version V100R021C10 - Issue 01 (2022-06-30)

This is the first release for V100R021C10.
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. 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................................................................................................................................................. 8
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................................................................................................................................................... 10
1.7.2 Using Ladders..................................................................................................................................................................... 11
1.8 Mechanical Safety.................................................................................................................................................................13
1.9 Other Precautions................................................................................................................................................................. 14
2 Commissioning Preparations.............................................................................................. 16
2.1 Preparing Documents and Tools......................................................................................................................................16
2.2 Determining the Commissioning Method.................................................................................................................... 17
2.3 Checking Commissioning Conditions............................................................................................................................. 18
2.3.1 Checking Site Commissioning Conditions................................................................................................................. 18
2.3.2 Checking System Commissioning Conditions.......................................................................................................... 18
3 Commissioning Process........................................................................................................ 20
3.1 Site Commissioning Process (General).......................................................................................................................... 20
3.2 Site Commissioning Process (with Cascade 1+1 Protection)................................................................................. 22
3.3 Site Commissioning Process (XPIC Links with 1+1 Protection).............................................................................26
3.4 Site Commissioning Process (MIMO)............................................................................................................................ 31
3.5 System Commissioning Process....................................................................................................................................... 35
4 Site Commissioning (Configuring Commissioning Data Using the Web LCT)....... 37

4.1 Powering On the Device..................................................................................................................................................... 38
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. v

4.1.1 Powering On the Device (DC Power Supply)...........................................................................................................38

4.1.2 Powering On the Device (PI Power Supply).............................................................................................................40
4.2 Accessing the Web LCT....................................................................................................................................................... 44
4.3 Creating NEs Using the Search Method........................................................................................................................49
4.4 Delivering a Commissioning Data Script Using the Web LCT............................................................................... 54
4.5 Configuring Commissioning Data................................................................................................................................... 55
4.5.1 Changing the NE ID.......................................................................................................................................................... 55
4.5.2 Changing the NE Name.................................................................................................................................................. 56
4.5.3 Configuring the VLAN ID and Bandwidth for an Inband DCN.......................................................................... 57
4.5.4 Unbinding QoS Policies for Ports................................................................................................................................. 58
4.5.5 Creating a Link Aggregation Group............................................................................................................................ 59
4.5.6 Configuring a Hop of Microwave Link....................................................................................................................... 61
4.5.7 Synchronizing Data on Main and Standby NEs in a 1+1 Protection Group..................................................63
4.5.8 Testing the XPI Value....................................................................................................................................................... 64
4.6 Checking Alarms................................................................................................................................................................... 65
4.7 Aligning Antennas................................................................................................................................................................ 66
4.7.1 Main Lobe and Side Lobes............................................................................................................................................. 66
4.7.2 Aligning Single-Polarized Antennas............................................................................................................................ 69
4.7.3 Aligning Dual-Polarized Antennas (XPIC Links)..................................................................................................... 73
4.7.4 Aligning Dual-Polarized Antennas (Inter-NE MIMO)........................................................................................... 76
4.8 Checking the Microwave Link Status and Receive Power.......................................................................................79
4.9 Configuring MIMO Links (Inter-NE)............................................................................................................................... 80
4.10 Configuring FO Maintenance Through the BBU......................................................................................................81
4.11 Connecting to the FO Device Through the BBU Service Port............................................................................. 83
5 System Commissioning........................................................................................................ 85
5.1 Configuring Network-wide Service Data...................................................................................................................... 86
5.2 Testing Ethernet Services................................................................................................................................................... 86
5.2.1 Testing Ethernet Services Configured on a Per-NE Basis..................................................................................... 86
5.3 Testing AM Shifting.............................................................................................................................................................. 90
5.4 Testing ATPC........................................................................................................................................................................... 91
5.5 Testing Protection Switching............................................................................................................................................. 92
5.5.1 Testing ERPS........................................................................................................................................................................ 92
5.5.2 Testing 1+1 Protection Switching (Intra-equipment 1+1 Protection)............................................................. 95
5.5.3 Testing 1+1 Protection Switching (Cascade 1+1 Protection)............................................................................. 97
5.5.4 Testing MPLS APS Protection Switching.................................................................................................................... 99
5.6 Checking the Clock Status............................................................................................................................................... 102
5.7 Testing the Fade Margin over a Microwave Link.................................................................................................... 104
5.8 Testing Ethernet Service Performance........................................................................................................................ 106
5.8.1 Testing Ethernet Service Performance (Based on RFC 2544).......................................................................... 106
5.8.2 Testing E-Line Service Performance (Based on OAM)....................................................................................... 111
5.8.3 Testing the Long-term Packet Loss Ratio............................................................................................................... 114
6 Handling Common Faults During Site Deployment................................................... 119
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. vi

6.1 Handling the Fault of the Receive Power Failing to Meet the Design Requirements................................ 119
7 Configuring Network-wide Service Data.......................................................................121

7.1 Configuration Preparations............................................................................................................................................. 121
7.1.1 Preparing Documents and Tools................................................................................................................................ 122
7.1.2 Checking Configuration Conditions.......................................................................................................................... 122
7.1.3 NCE Quick Start............................................................................................................................................................... 122
7.1.3.1 Logging In to the NCE Client................................................................................................................................... 123
7.1.3.2 Logging Out of the NCE Client............................................................................................................................... 124
7.1.3.3 Using Online Help....................................................................................................................................................... 124
7.1.3.4 Navigating to Common Views................................................................................................................................ 125
7.1.3.4.1 Navigating to the Main Topology...................................................................................................................... 125
7.1.3.4.2 Navigating to the NE Explorer.............................................................................................................................126
7.1.3.4.3 Navigating to the NE Panel.................................................................................................................................. 127
7.2 General Configuration Process.......................................................................................................................................127
7.3 Common Network Scenarios of Configuration Examples.................................................................................... 129
7.3.1 Overview............................................................................................................................................................................ 129
7.3.2 Microwave Chain Network.......................................................................................................................................... 130
7.3.3 Microwave Ring Network............................................................................................................................................. 131
7.3.4 PTP Large Capacity Microwave Transmission Scenario..................................................................................... 132
7.3.5 Microwave 1+1 Protection Scenario......................................................................................................................... 133
7.3.6 NE Cascading Transmission Scenario....................................................................................................................... 133
7.4 Configuring the Network Topology..............................................................................................................................134
7.4.1 Basic Concepts..................................................................................................................................................................134
7.4.1.1 Introduction to the DCN........................................................................................................................................... 135
7.4.1.2 IP DCN............................................................................................................................................................................. 140
7.4.1.3 Fiber/Cable Types........................................................................................................................................................ 144
7.4.1.4 Logical Boards............................................................................................................................................................... 145
7.4.2 Configuration Process (Network Topology)...........................................................................................................145
7.4.3 Configuration Example (Network Topology)........................................................................................................ 148
7.4.3.1 Networking Diagram.................................................................................................................................................. 148
7.4.3.2 Configuration Procedure........................................................................................................................................... 150
7.5 Configuring Microwave Links......................................................................................................................................... 156
7.5.1 Configuration Process (Microwave Links).............................................................................................................. 156
7.5.2 Configuration Example (Microwave Links on a Chain Network)...................................................................161
7.5.3 Configuration Example (Microwave Links with 1+1 Protection)....................................................................164
7.5.4 Configuration Example ( XPIC Microwave links with PLA protection)......................................................... 168
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. vii

7.5.5 Configuration Example (XPIC Links with 1+1 Protection)................................................................................ 171

7.5.6 Configuration Example (Cascade EPLA)................................................................................................................. 178
7.5.7 Configuration Example (4 x 4 MIMO Microwave Links)................................................................................... 183
7.6 Configuring Ethernet Services .......................................................................................................................................185
7.6.1 Ethernet Service Ports................................................................................................................................................... 185
7.6.2 Ethernet Service Types.................................................................................................................................................. 188
7.6.2.1 Transparently Transmitted Point-to-Point E-Line Service.............................................................................. 188
7.6.2.2 VLAN-based E-Line Service...................................................................................................................................... 189
7.6.2.3 QinQ-Based E-Line Services..................................................................................................................................... 191
7.6.2.4 IEEE 802.1D Bridge-based E-LAN Services.......................................................................................................... 195
7.6.2.5 IEEE 802.1Q Bridge-based E-LAN Services......................................................................................................... 195
7.6.2.6 802.1ad Bridge-based E-LAN Services.................................................................................................................. 197
7.6.3 Configuration Process.................................................................................................................................................... 198
7.6.3.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point E-Line Services)..............199
7.6.3.2 Per-NE Configuration Process (VLAN-based E-Line Services)......................................................................201
7.6.3.3 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)........................................... 202
7.6.3.4 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)...........................................204
7.6.4 Configuration Example (Transparently Transmitted Point-to-Point E-Line Services)..............................206
7.6.4.2 Procedure of Configuration on a Per-NE Basis (Service Information)...................................................... 207
7.6.4.3 Per-NE Configuration Process (Configuring QoS)............................................................................................ 208
7.6.4.4 Procedure of Configuration on a Per-NE Basis (Ethernet Service Verification)..................................... 212
7.6.5 Configuration Example (VLAN-based E-Line Services)......................................................................................215
7.6.6 Configuration Example (IEEE 802.1D Bridge-based E-LAN Service)............................................................. 224
7.6.6.2 Per-NE Configuration Procedure (Ethernet Protection)................................................................................. 225
7.6.6.3 Per-NE Configuration Procedure (Service Information)................................................................................. 226
7.6.6.5 Per-NE Configuration Procedure (Ethernet Service Verification)................................................................232
7.6.7 Configuration Example (IEEE 802.1Q Bridge-based E-LAN Services)...........................................................235
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. viii


7.7 Configuring Clocks............................................................................................................................................................. 247
7.7.1 Configuration Process (Configuring a Clock)........................................................................................................ 247
7.7.2 Configuration Example (Clock on a Microwave Chain Network).................................................................. 248
7.7.3 Configuration Example (Clock on a Microwave Ring Network).....................................................................251
7.7.4 Configuration Example (Clock on an NE Cascading Transmission Network)............................................ 254
7.8 Common Service Configuration Operations............................................................................................................. 256
7.8.1 Configuring the Network Topology.......................................................................................................................... 257
7.8.1.1 Connecting to an NE (Using the USB Port)........................................................................................................257
7.8.1.2 Creating NEs by Using the Search Method (NCE)........................................................................................... 257
7.8.1.3 Creating NEs by Using the Search Method (Web LCT).................................................................................. 260
7.8.1.4 Creating NEs by Using the Manual Method (NCE)......................................................................................... 262
7.8.1.5 Creating NEs by Using the Manual Method (Web LCT)................................................................................ 263
7.8.1.6 Configuring Logical Interfaces................................................................................................................................ 264
7.8.1.7 Changing NE IDs.......................................................................................................................................................... 267
7.8.1.8 Changing the NE Name............................................................................................................................................ 268
7.8.1.9 Setting the VLAN ID and Bandwidth for an Inband DCN............................................................................. 268
7.8.1.10 Configuring Access Control.................................................................................................................................... 269
7.8.1.11 Creating a Fiber/Cable by Using the Search Method................................................................................... 271
7.8.1.12 Creating a Fiber/Cable Manually......................................................................................................................... 272
7.8.2 Configuring Microwave Links......................................................................................................................................273
7.8.2.1 Creating a Microwave 1+1 Protection Group.....................................................................................................273
7.8.2.2 Managing a Hop of Microwave Link.................................................................................................................... 276
7.8.2.3 Synchronizing Data Between Main and Standby NEs (1+1)........................................................................ 278
7.8.2.4 Creating a PLA\EPLA Group..................................................................................................................................... 279
7.8.2.5 Creating an EPLA Group for NE-level Protection in LAG Mode.................................................................. 282
7.8.2.6 Creating an EPLA Group for NE-level Protection in Optical Splitter Mode.............................................284
7.8.2.7 Configuring AES Radio Interface Encryption......................................................................................................286
7.8.3 Configuring Ethernet Services on a Per-NE Basis................................................................................................ 287
7.8.3.1 Creating a LAG............................................................................................................................................................. 287
7.8.3.2 Creating an ERPS Instance....................................................................................................................................... 290
7.8.3.3 Setting Protocol Parameters for an ERPS Instance.......................................................................................... 291
7.8.3.4 Creating a Point-to-Point Transparently Transmitted E-Line Service.........................................................291
7.8.3.5 Creating a VLAN-based E-Line Service................................................................................................................ 293
7.8.3.6 Creating an IEEE 802.1D Bridge-based E-LAN Service................................................................................... 294
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. ix

7.8.3.7 Creating an IEEE 802.1Q Bridge-based E-LAN Service................................................................................... 295

7.8.3.8 Changing Logical Ports Mounted to a Bridge................................................................................................... 296
7.8.3.9 Deleting an E-Line Service........................................................................................................................................297
7.8.3.10 Deleting an E-LAN Service..................................................................................................................................... 298
7.8.3.11 Creating a DS Domain............................................................................................................................................. 299
7.8.3.12 Modifying the Mapping Relationship of the DiffServ Domain..................................................................302
7.8.3.13 Modifying the Ports Applied to a DiffServ Domain and Packet Types Trusted by Ports..................303
7.8.3.14 Enabling/Disabling DSCP Demapping at Egress Ports................................................................................. 305
7.8.3.15 Enabling/Disabling Outbound Demapping at the Egress Port of a DiffServ Domain.......................306
7.8.3.16 Creating a WRR Policy............................................................................................................................................. 307
7.8.3.17 Creating a Port WRED Policy................................................................................................................................ 308
7.8.3.18 Modifying the Port Policy....................................................................................................................................... 309
7.8.3.19 Creating a Port Policy.............................................................................................................................................. 310
7.8.3.20 Creating Traffic.......................................................................................................................................................... 311
7.8.3.21 Setting the Port That Uses the Port Policy....................................................................................................... 312
7.8.3.22 Setting Egress Queue Scheduling Policies........................................................................................................ 313
7.8.3.23 Creating a DS Domain Profile...............................................................................................................................314
7.8.3.24 Creating a Port WRED Policy Profile.................................................................................................................. 316
7.8.3.25 Creating a WRR Policy Profile............................................................................................................................... 317
7.8.3.26 Creating a Port Policy Profile................................................................................................................................ 319
7.8.3.27 Downloading a QoS Policy Profile to an NE or Port.....................................................................................320
7.8.3.28 Releasing the QoS Policy Bound to an Interface........................................................................................... 322
7.8.3.29 Restoring an Ethernet Port Configured as an NMS Port to a Service Port........................................... 323
7.8.4 Configuring Clocks.......................................................................................................................................................... 324
7.8.4.1 Configuring the System Clock Source.................................................................................................................. 324
7.8.4.2 Configuring Protection for Clock Sources........................................................................................................... 325
7.8.4.3 Configuring a Clock Source Group........................................................................................................................ 326
Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. x

Commissioning and Configuration Guide 1 Safety Precautions
1 Safety Precautions
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 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. 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.
● Only trained and qualified personnel are permitted to install, operate, and
maintain a device.
● Only certified professionals are permitted to remove the safety facilities, and
to troubleshoot and maintain the device.
● Only the personnel authenticated or authorized by Huawei are permitted to
replace or change the device or parts of the device (including software).
● 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.
● When installing the device, always connect the grounding facilities first. When
removing the device, always disconnect the grounding facilities last.
● Ensure that the grounding conductor is intact.
● Do not operate the device in the absence of a suitably installed grounding
conductor.
● 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
● When there is a risk of a lightning strike, do not operate the fixed terminal or
touch the cables.
● 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.
● To avoid electric shocks, do not connect safety extra-low voltage (SELV)
circuits to telephone-network voltage (TNV) circuits.
● Do not look into optical ports without eye protection. Otherwise, human eyes
may be hurt by laser beams.
● 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.
● 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
● Before any operation, install the device firmly on the ground or other rigid
objects, such as on a wall or in a rack.
● When the system is working, ensure that the ventilation hole is not blocked.
● When installing the front panel, use a tool to tighten the screws firmly, if
required.
● 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/320F and
their meanings.
Table 1-1 Warning and safety symbols of the OptiX RTN 320/320F
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.

Label Label Name Description
High temperature warning Indicates that the equipment

label 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
● 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.
● 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.
● Before installing or removing power cables, you must power off the device.
● 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.
● Incorrect operations of storage batteries cause hazards. During operation,

prevent any short-circuit, and prevent the electrolyte from overflowing or
leakage.
● 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.
● 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:
● Use special insulation tools.
● Wear an eye protector and take effective protection measures.
● Wear rubber gloves and a protection coat to prevent the hazard caused by
the overflowing electrolyte.
● When handling the storage battery, ensure that its electrodes are upward.
Leaning or reversing the storage battery is prohibited.
● 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:
● Sodium bicarbonate (NaHCO3)

● Sodium carbonate (Na2CO3)
In the event of acid overflow or spillage, neutralize the acid and clean it up as
recommended by the battery manufacturer and any local regulations for acid
disposal.
If a person contacts battery electrolyte, clean the skin that contacts the battery
electrolyte immediately by using water. In case of a severe situation, the person
must be sent to a hospital immediately.

1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
1.6.1 Safe Usage of Optical Fibers

The laser beam can cause damage to your eyes. Hence, you must exercise caution
when using optical fibers.
DANGER
When installing or maintaining optical fibers, avoid direct eye exposure to the
laser beams launched from the optical interface or fiber connectors. The laser
beam can cause damage to your eyes.
Cleaning Fiber Connectors and Optical Interfaces
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:
● 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.
● Non-woven lens tissue
● Special compressed gas
● Cotton stick (medical cotton or long fiber cotton)
● Special cleaning roll, used with the recommended cleaning solvent
● 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.
● 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.
● 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:
● All operations should be performed by authorized personnel who have

completed the required training courses.
● Wear a pair of eye-protective glasses when you are handling lasers or fibers.
● Ensure that the optical source is switched off before disconnecting optical
fiber connectors.
● 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.
● Use an optical power meter to measure the optical power and ensure that the
optical source is switched off.
● Before opening the front door of an optical transmission device, ensure that
you are not exposed to laser radiation.

● 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:
● Only trained personnel are permitted to cut and splice fibers.

● 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:
● The personnel who work at heights must be trained.

● Carry and handle the operating machines and tools with caution to prevent
them from falling down.
● Safety measures, such as wearing a helmet and a safety belt, must be taken.
● Wear cold-proof clothes when working at heights in cold areas.
● 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.

CAUTION
When heavy objects are being hoisted, do not walk below the cantilever or hoisted
objects.
● Only trained and qualified personnel can perform hoisting operations.

● Before hoisting heavy objects, check that the hoisting tools are complete and
in good condition.
● Before hoisting heavy objects, ensure that the hoisting tools are fixed to a
secure object or wall with good weight-bearing capacity.
● Issue orders with short and explicit words to ensure correct operations.
● 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
● Before using a ladder, check whether the ladder is damaged. After checking
that the ladder is in good condition, you can use the ladder.
● 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:
● Ensure that the center of gravity of your body does not deviate from the
edges of the two long sides.
● Before operations, ensure that your body is stable to reduce risks.
● 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.
● Before drilling a hole on the cabinet, remove the cables inside the cabinet.
● Wear an eye protector when drilling holes. This is to prevent eyes from being
injured by the splashing metal scraps.
● Wear protection gloves when drilling holes.
● 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
● 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.
● 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
● 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.
● 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.
● 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.
● 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.
● Slide the board along the guide rails.

● Do not contact one board with another to avoid short-circuits or damage.
● 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:
● When installing cables, ensure that the environment temperature is above
0°C.
● 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.
● 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
This chapter describes the preparations required prior to equipment

commissioning.
The preparation process is as follows:

2.1 Preparing Documents and Tools
To ensure that the equipment commissioning goes smoothly, you need to prepare
the related documents and tools in advance.
2.2 Determining the Commissioning Method
According to the scale of a microwave network, commissioning engineers can
adopt the single-hop commissioning method or system commissioning method.
2.3 Checking Commissioning Conditions
Ensure that the equipment meets the requirements for commissioning before
performing site commissioning or system commissioning.
2.1 Preparing Documents and Tools

To ensure that the equipment commissioning goes smoothly, you need to prepare
the related documents and tools in advance.
Documents
Prepare the following documents before equipment commissioning:
● Engineering design documents, including:

– XX Network Planning
– XX Engineering Design
● Commissioning guides, including:
– OptiX RTN 320/320F Radio Transmission System Commissioning and
Configuration Guide
Tools
Table 2-1 lists the tools required for commissioning.

Table 2-1 Tools

Tool Application Scenario
Adjustable wrench, screwdriver, Aligning antennas

telescope, interphone, hex key
(delivered with antennas), multimeter,
north-stabilized indicator, special
spanner for the OMT (delivered with
the OMT), and RSSI test cable (By
default, the RSSI test cable is not
delivered and needs to be purchased
locally.)
Laptop on which the Web LCT is ● Configuring site commissioning

installed data
● Checking the microwave link status
and receive power
● Testing AM switching
● Checking alarms
PC on which the NCE is installed Performing centralized commissioning

on the NCE
NOTE
For details about the requirements and methods for installing the Web LCT hardware and
software, see the Web LCT User Guide.
2.2 Determining the Commissioning Method

According to the scale of a microwave network, commissioning engineers can
adopt the single-hop commissioning method or system commissioning method.
Context
NOTE
Site commissioning and system commissioning are defined as follows:

● 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 on a network.
● System commissioning refers to the configuration of commissioning data for each site.
System commissioning is carried out with commissioning tools connected to a gateway NE
to communicate with all NEs on a network.
Single-Hop Commissioning
Single-hop commissioning is applicable to small-scale microwave 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
items at a time. The commissioning procedure is as follows:

1. Power on the devices of the sites at both ends of a microwave link.

2. Configure commissioning data using the Web LCT.
3. Complete the remaining site commissioning items using the Web LCT.
4. Complete the system commissioning items using the Web LCT.
System Commissioning
System commissioning is applicable to large-scale microwave networks to improve
engineering efficiency. The procedure is as follows:
1. Power on the device.

2. Configure commissioning data using the Web LCT.
3. Complete the remaining site commissioning items using the Web LCT.
4. Complete the system commissioning items using the NCE at a central site
where services are aggregated.
2.3 Checking Commissioning Conditions

Ensure that the equipment meets the requirements for commissioning before
performing site commissioning or system commissioning.
2.3.1 Checking Site Commissioning Conditions

Before site commissioning, you need to check the site and weather conditions.
Context
The site commissioning conditions are as follows:
● Equipment hardware has been installed and passed the installation check.
● Power is available to the equipment.
● Service signal cables that are connected to other equipment have been
properly routed.
● The onsite conditions and antenna commissioning personnel meet the
requirements for working at heights.
● The weather is fine, without gale, rain, snow, or fog.
2.3.2 Checking System Commissioning Conditions

Before system commissioning, you need to check the site and weather conditions.
Context
The system commissioning conditions are as follows:
● Site commissioning is completed for microwave equipment at both ends of

the microwave link.
● DCN communication on the microwave network is normal.

● During the commissioning, the weather is fine, without gale, rain, snow, or
fog.

Commissioning and Configuration Guide 3 Commissioning Process
3 Commissioning Process
Based on the objects to be commissioned, commissioning involves two phases: site

commissioning and system commissioning.
3.1 Site Commissioning Process (General)

Site commissioning refers to the commissioning of one microwave link hop and
the sites at both ends of the hop. Site commissioning ensures that the sites and
the microwave link between the sites work properly, which prepares for system
commissioning.
3.2 Site Commissioning Process (with Cascade 1+1 Protection)
For sites configured with cascade 1+1 protection, the commissioning process is
different. Unless otherwise specified, 1+1 protection mentioned in the following
refers to cascade 1+1 protection.
3.3 Site Commissioning Process (XPIC Links with 1+1 Protection)
Commissioning of an XPIC site configured with 1+1 protection links requires an
additional operation of aligning polarized antennas based on cascade 1+1
protection links.
3.4 Site Commissioning Process (MIMO)
The RTN 320 supports intra-NE 2x2 MIMO sites, inter-NE 2x2 MIMO sites, and 4x4
MIMO sites. 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 various protection functions are implemented across the
microwave network.
3.1 Site Commissioning Process (General)

Site commissioning refers to the commissioning of one microwave link hop and
the sites at both ends of the hop. Site commissioning ensures that the sites and
the microwave link between the sites work properly, which prepares for system
commissioning.

Commissioning Method
For the OptiX RTN 320/320F, you can use the following tools to configure the
commissioning data of the site with cascade 1+1 protection:
● Web LCT
● Mobile phone connected to the equipment using a USB cable
NOTE
If a mobile phone is used for commissioning, connect it to the equipment by referring

to 7.8.1.1 Connecting to an NE (Using the USB Port).
Site Commissioning Items (Configuring Commissioning Data Using the Web

LCT)
Commissioning engineers can configure site commissioning data using the Web
LCT onsite when they are:
● Capable of configuring microwave link data for the OptiX RTN 320/320F.
● Aware of the microwave link planning data for the site.
● Equipped with a laptop on which the Web LCT is installed.
Commissioning Item Description
Powering on the Device Mandatory
Accessing the Web LCT Mandatory
Creating NEs Using the Search Method Mandatory
Configuring Commissioning Data Using the Web Mandatory

LCT or Delivering a Commissioning Data Script
Using the Web LCT
Checking Alarms Mandatory
Aligning Antennasa Aligning Single- Mandatory when a

Polarized Antennas single-polarized antenna
on a microwave link is
used for transmission
Aligning Dual-Polarized Mandatory when a dual-

Antennas polarized antenna on a
microwave link is used
for transmission
Checking the Microwave Link Status and Receive Mandatory

Power
NOTE
a: Before aligning antennas, power on the device and configure site commissioning data at
both ends of the microwave link.

3.2 Site Commissioning Process (with Cascade 1+1

Protection)
For sites configured with cascade 1+1 protection, the commissioning process 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 delivery of the commissioning data script using the Web LCT.
For the OptiX RTN 320/320F, you can use the following tools to configure the
commissioning data of the site with cascade 1+1 protection:
● Web LCT
NOTE


LCT)
Commissioning engineers can configure commissioning data using the Web LCT
onsite when they are:
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
● Antenna alignment engineers align antennas, activate microwave links, and turn over the
subsequent commissioning to the data configuration engineers responsible for configuring
1+1 protection.
● The data configuration engineers responsible for configuring 1+1 protection completes the
configuration of 1+1 protection data.
● An engineer familiar with site commissioning can also serve as the preceding two roles.

Figure 3-1 Coordinately configuring 1+1 protection data for sites at both ends
For sites at both ends of a link, perform the following operations simultaneously:
1. Power on the main device by referring to 4.1 Powering On the Device and
keep the standby device in the off status.
2. Configure commissioning data for the main device by referring to 4.5
Configuring Commissioning Data. At this time, do not configure a
microwave 1+1 protection group (or link aggregation group for 1+1
protection if the protection involves LAG).
3. Check alarms on the main device by referring to 4.6 Checking Alarms.
4. Activate microwave links of the main device by referring to 4.7 Aligning
Antennas.
5. Check the status and receive power of the main microwave link by referring to
4.8 Checking the Microwave Link Status and Receive Power.
6. Power on the standby device by referring to 4.1 Powering On the Device.
7. Configure commissioning data for the standby device.

8. Configure microwave 1+1 protection group data for the main device (and a
LAG for 1+1 protection if the protection involves LAG).
9. Synchronize the data on main and standby NEs in a 1+1 protection group.
10. Check alarms on the main and standby devices by referring to 4.6 Checking
Alarms.
11. Check the microwave link status and receive power.
Figure 3-2 Independently configuring 1+1 protection data for the local site
1. Power on the main devices at both ends by referring to 4.1 Powering On the
Device and keep the standby devices in the off status.
2. Configure commissioning data for the main devices at both ends by referring
to 4.5 Configuring Commissioning Data. At this time, do not configure a

3. Check alarms on the main devices at both ends by referring to 4.6 Checking
Alarms.
4. Activate microwave links of the main device by referring to 4.7 Aligning
Antennas.
6. Power on the remote standby device by referring to 4.1 Powering On the
Device.
7. Configure commissioning data for the remote standby device by referring to
4.5 Configuring Commissioning Data. At this time, do not configure a
8. Configure microwave 1+1 protection group data for the main device at the
remote site (and a LAG for 1+1 protection if the protection involves LAG).
9. Synchronize the data on main and standby NEs in a 1+1 protection group
for the remote site.
10. Force the 1+1 protection group of the main device to work in the main unit by
referring to Microwave 1+1 Protection Switching.
11. Power on the local standby device by referring to 4.1 Powering On the
Device.
12. Configure commissioning data for the local standby device by referring to 4.5
local site (and a LAG for 1+1 protection if the protection involves LAG).
for the local site.

16. Check alarms on the main and standby devices at both ends by referring to
4.6 Checking Alarms.
17. Check the microwave link status and receive power by referring to 4.8
Checking the Microwave Link Status and Receive Power.
18. Clear the forced switching commands for the main devices at the local and
remote ends by referring to Microwave 1+1 Protection Switching.
3.3 Site Commissioning Process (XPIC Links with 1+1

Protection)
Commissioning of an XPIC site configured with 1+1 protection links requires an
additional operation of aligning polarized antennas based on cascade 1+1
protection links.
For the OptiX RTN 320/320F, you can use the following tools to configure
commissioning data for an XPIC site configured with 1+1 protection links:
● Web LCT
NOTE



LCT)
Commissioning engineers can configure commissioning data using the Web LCT
onsite when they are:
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
● Antenna alignment engineers align antennas, activate microwave links, and turn over the
subsequent commissioning to the data configuration engineers responsible for configuring
1+1 protection.
● The data configuration engineers responsible for configuring 1+1 protection completes the
configuration of 1+1 protection data.
● An engineer familiar with site commissioning can also serve as the preceding two roles.
NOTE
The integrated RTN 320 is used as an example to describe the procedure.

Figure 3-3 Coordinately configuring 1+1 protection data for sites at both ends
For sites at both ends of a link, perform the following operations simultaneously:
1. Power on the main device by referring to 4.1 Powering On the Device and
keep the standby device in the off status.
2. Configure commissioning data for the main device by referring to 4.5
3. Check alarms on the main device by referring to 4.6 Checking Alarms.
4. Activate microwave links of the main device by referring to 4.7.3 Aligning
Dual-Polarized Antennas (XPIC Links).
6. Power on the standby device by referring to 4.1 Powering On the Device.

7. Configure commissioning data for the standby device.

8. Configure microwave 1+1 protection group data for the main device (and a
LAG for 1+1 protection if the protection involves LAG).
9. Synchronize the data on main and standby NEs in a 1+1 protection group.
10. Check alarms on the main and standby devices by referring to 4.6 Checking
Alarms.
11. Check the microwave link status and receive power.
Figure 3-4 Independently configuring 1+1 protection data for the local site
1. Power on the main devices at both ends by referring to 4.1 Powering On the
Device and keep the standby devices in the off status.

2. Configure commissioning data for the main devices at both ends by referring
to 4.5 Configuring Commissioning Data. At this time, do not configure a
3. Check alarms on the main devices at both ends by referring to 4.6 Checking
Alarms.
4. Activate microwave links of the main device by referring to 4.7.3 Aligning
Dual-Polarized Antennas (XPIC Links).
6. Power on the remote standby device by referring to 4.1 Powering On the
Device.
7. Configure commissioning data for the remote standby device by referring to
4.5 Configuring Commissioning Data. At this time, do not configure a
remote site (and a LAG for 1+1 protection if the protection involves LAG).
for the remote site.
11. Power on the local standby device by referring to 4.1 Powering On the
Device.
12. Configure commissioning data for the local standby device by referring to 4.5
local site (and a LAG for 1+1 protection if the protection involves LAG).
for the local site.

16. Check alarms on the main and standby devices at both ends by referring to
4.6 Checking Alarms.
17. Check the microwave link status and receive power by referring to 4.8
Checking the Microwave Link Status and Receive Power.
18. Clear the forced switching commands for the main devices at the local and
remote ends by referring to Microwave 1+1 Protection Switching.
3.4 Site Commissioning Process (MIMO)

The RTN 320 supports intra-NE 2x2 MIMO sites, inter-NE 2x2 MIMO sites, and 4x4
MIMO sites. The commissioning process for MIMO links is different from that for
common links.
NOTE
If a mobile phone is used for commissioning, connect it to the equipment by referring to

7.8.1.1 Connecting to an NE (Using the USB Port).
NOTE
The RTN 320F of the current version does not support MIMO.
2X2 MIMO Commissioning

NOTE
Inter-NE 2x2 MIMO will usually be expanded to 4x4 MIMO. The commissioning processes
for inter-NE 2x2 MIMO and 4x4 MIMO are the same. After the commissioning is complete,
use purchased filter planes to seal idle polarization ports.

Figure 3-5 Flowchart for 2x2 MIMO commissioning
Table 3-1 2x2 MIMO commissioning
Procedure Operation Description
1 Powering on the device Mandatory
2 Configuring Mandatory
commissioning data NOTE
● Do not enable XPIC
when configuring
microwave link data.
● Configure each
microwave link in the
MIMO work group.

3 Checking alarms Mandatory
4 Aligning single- Mandatory

polarized antennas
5 Configuring MIMO Mandatory

links
6 Checking the Mandatory

microwave link status
and receive power

Inter-NE 4x4 MIMO Commissioning
Figure 3-6 Flowchart for inter-NE 4x4 MIMO commissioning
Table 3-2 Inter-NE 4x4 MIMO commissioning

1 Powering on the device Mandatory

2 Configuring Mandatory
commissioning data NOTE
● Do not enable XPIC
when configuring
microwave link data.
● Configure each
microwave link in the
MIMO work group.
3 Checking alarms Mandatory
4 Aligning dual-polarized Mandatory

antennas
5 Configuring MIMO Mandatory

links
6 Checking the Mandatory

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 various protection functions are implemented across the
microwave network.
Table 3-3 System commissioning items of the RTN 320F

5.1 Configuring Network-wide Service Data Mandatory
5.2 Testing Ethernet 5.2.1 Testing Ethernet Mandatory when

Services Services Configured on Ethernet services are
a Per-NE Basis configured
5.3 Testing AM Shifting Mandatory
5.4 Testing ATPC Mandatory
5.5 Testing Protection 5.5.1 Testing ERPS Mandatory

Switching
5.5.2 Testing 1+1 Mandatory when a
Protection Switching microwave link with 1+1
(Intra-equipment 1+1 protection is configured
Protection)

5.5.3 Testing 1+1

Protection Switching
(Cascade 1+1
Protection)
5.6 Checking the Clock Status Mandatory
5.7 Testing the Fade Margin over a Microwave Optional

Link
Table 3-4 System commissioning items of the RTN 320

5.1 Configuring Network-wide Service Data Mandatory
5.2 Testing Ethernet 5.2.1 Testing Ethernet Mandatory when

Services Services Configured on Ethernet services are
a Per-NE Basis configured
5.3 Testing AM Shifting Mandatory
5.4 Testing ATPC Mandatory
5.5 Testing Protection 5.5.1 Testing ERPS Mandatory

Switching
5.5.2 Testing 1+1 Mandatory when a
Protection Switching microwave link with 1+1
(Intra-equipment 1+1 protection is configured
Protection)
5.5.3 Testing 1+1

(Cascade 1+1
Protection)
5.5.4 Testing MPLS APS Mandatory

5.6 Checking the Clock Status Mandatory
5.7 Testing the Fade Margin over a Microwave Optional

Link
5.8 Testing Ethernet 5.8.2 Testing E-Line Mandatory

Service Performance Service Performance
(Based on OAM)
5.8.3 Testing the Long- Mandatory

term Packet Loss Ratio

OptiX RTN 320&320F Radio Transmission System 4 Site Commissioning (Configuring Commissioning
Commissioning and Configuration Guide Data Using the Web LCT)
4
Site Commissioning (Configuring
Commissioning Data Using the Web LCT)
This commissioning mode requires commissioning engineers to be capable of

configuring NE data.
4.1 Powering On the Device

By observing the process of powering on the device, you can check whether the
hardware system and power system of the device are normal.
4.2 Accessing the Web LCT
Properly accessing the Web LCT is a prerequisite for subsequent data
configuration.
4.3 Creating NEs Using the Search Method
The search method is generally used to create NEs during site commissioning.
4.4 Delivering a Commissioning Data Script Using the Web LCT
If the commissioning data script of a site is available, you can use the Web LCT to
deliver the script to the NE without configuring data onsite.
4.5 Configuring Commissioning Data
This section describes how to configure site commissioning data for an NE when
you perform site commissioning using the Web LCT.
4.6 Checking Alarms
By checking the current alarms of the equipment, you can determine whether the
equipment can work normally.
4.7 Aligning Antennas
Antenna alignment is the most important activity for site commissioning. Its result
has a direct effect on the performance of microwave links.
4.8 Checking the Microwave Link Status and Receive Power
After antenna alignment, check whether the status of a microwave link is normal
and whether the receive power meets requirements.
4.9 Configuring MIMO Links (Inter-NE)
After aligning antennas, you need to configure MIMO links.
4.10 Configuring FO Maintenance Through the BBU

4.11 Connecting to the FO Device Through the BBU Service Port
4.1 Powering On the Device

By observing the process of powering on the device, you can check whether the
hardware system and power system of the device are normal.
Context
NOTE
● Power on the device within 24 hours after unpacking it.

● During maintenance, the power-off time of the device cannot exceed 24 hours.
4.1.1 Powering On the Device (DC Power Supply)

Through the DC power supply, you can observe the process of powering on the
device to check whether the hardware system of the device and the DC power
supply system are normal.
Prerequisites
● The hardware installation of the device is complete and the installation check
is passed.
● The power supply is available. Before connecting the power cable, check the
voltage and polarity of the power supply and the capacity of the fuse.
● The power switch of the power supply (such as the power distribution box of
the cabinet) is turned off.
● The power cable is properly connected, and the positive and negative poles
are not reversely connected.
● Only the RTN 320F (DC option) supports DC power supply.
Context
Table 4-1 lists the fuse capacity recommended for the OptiX RTN 320/320F.
Table 4-1 Fuse capacity

Chassis Recommended Fuse Capacity
RTN 320/RTN 320F (DC option) ● Integrated RTN 320: 12 A

● OAU 2A: 10 A
● OAU 2F: 7 A

Precautions
NOTICE
● If the output voltage of the power supply device does not meet the test
requirements, do not power on the device before providing rectification
suggestions.
● If the power cable is reversely connected, rectify the connection before power-
on. Otherwise, the circuit breaker of the power distribution box is disconnected
and the power cable may be burnt.
Procedure
Step 1 Connect the power supply. Check and ensure that the DC power cable is correctly
connected.
Figure 4-1 Connection diagram for the RTN 320

Figure 4-2 Connection diagram of the RTN 320F (OAU 2F)
Step 2 Check and ensure that the power cable is correctly connected. Power on the OAU
and observe the system indicators of the OptiX RTN 320/320F to ensure that the
power-on is normal.
Normally, the system indicator should be steady green.
NOTE
● If the system indicator is off, check the output voltage and polarity of the power supply
to locate the power supply fault.
● If the system indicator is red, check whether the OptiX RTN 320/320F is faulty.
----End
4.1.2 Powering On the Device (PI Power Supply)

Through the PI power supply, you can observe the process of powering on the
device to check whether the hardware system of the device and the PI power
supply system are normal.
Prerequisites
NOTE
This section uses the PI-DC B20 as an example to describe how to power on the integrated
RTN 320. For details about other types of PIs, see the corresponding product description
and installation guide.

● The hardware installation of the device is complete and the installation check
is passed.
● The power supply is available. Before connecting the power cable, check the
voltage and polarity of the power supply and the capacity of the fuse.
● The power switch of the power supply (such as the power distribution box of
the cabinet) is turned off.
● The power cable is properly connected, and the positive and negative poles
are not reversely connected.
● The RTN 320F (P&E option) supports PI power supply.
Context
Table 4-2 lists the fuse capacity recommended for the RTN 320.
Table 4-2 Fuse capacity

Chassis Recommended Fuse Capacity
Integrated RTN 320 10 A
RTN 320F (P&E option) OAU 2F: 7 A
Precautions
NOTICE
● If the output voltage of the power supply device does not meet the test
requirements, do not power on the device before providing rectification
suggestions.
● If the power cable is reversely connected, rectify the connection before power-
on. Otherwise, the circuit breaker of the power distribution box is disconnected
and the power cable may be burnt.
Procedure
Step 1 Power on the device.
The method of connecting the (P&E/GE1) port on the RTN 320F to the (P&E1)
port on the PI is the same as that of connecting the (P&E1/GE1) port on the
integrated RTN 320. This step uses the integrated RTN 320 as an example.

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 panel should be steady
green.
NOTE
● If the DC IN indicator is steady green but the P&E OUT indicator blinks green, check whether
the outdoor network cable or RTN 320 is short-circuited.
● 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 the RTN 320 to check whether the device is
successfully powered on.
Normally, the system indicator should be steady green.

NOTE
If the system indicator is red, check whether the microwave link and outdoor network cable
are normal and whether the RTN 320 is faulty.
----End

4.2 Accessing the Web LCT

Properly accessing the Web LCT is a prerequisite for subsequent data
configuration.
Prerequisites
● The OptiX RTN 320/320F has been powered on.
● The WLAN module is working properly.
Tools, Instruments, and Materials

Web LCT (Windows 7 or later)
Context
This section describes how to connect the RTN 320 to the Web LCT through
WLAN. If the WLAN module does not work properly, you are advised to connect
the RTN 320 to the Web LCT through the NMS/GE2(e) port in the maintenance
compartment. Generally, you are not advised to connect the equipment to the
Web LCT through the NMS port at the side of the maintenance compartment. The
IP address of the network port on a computer on which the Web LCT is installed
must be in the same network segment as the NE IP address and must be different
from the NE IP address.
This section describes how to connect the RTN 320F to the Web LCT through
WLAN. If the WLAN module does not work properly, you are advised to connect
the RTN 320F to the Web LCT through the NMS port. If the equipment is
connected to the Web LCT through the NMS port, the IP address of the network
port on a computer on which the Web LCT is installed must be in the same
network segment as the NE IP address and must be different from the NE IP
address.
Figure 4-3 Connecting the OptiX RTN 320/320F to the Web LCT
Connection diagram for the RTN 320

Connection diagram for the RTN 320F

NOTE
● If a site has several cascaded OptiX RTN 320/320Fs, connect the laptop to only one of
the OptiX RTN 320/320Fs. Other OptiX RTN 320/320Fs can be connected through the
internal DCN.
● Use either a crossover cable or a straight-through cable to connect the equipment to
the laptop. For the wire sequences of crossover cables and straight-through cables, see
Outdoor Network Cables in the Product Description.
Procedure
Step 1 Start the laptop and log in to the operating system.
Step 2 Start WLAN connection on the laptop.
Step 3 Manually configure the static IP address on the laptop. Ensure that this IP address
in the same network segment with the fixed NE IP address (192.168.1.1/24).
Step 4 Select the SSID of the NE to be connected, and enter the password to establish a
WLAN connection.
● The default SSID is FMn-The last six digits of a MAC address in hexadecimal
format-NE ID.
● The default password is Modify_123.


NOTE
● If the tool does not find the SSID of the NE, perform the following operations:
– Check whether there is a block between the laptop and the equipment.
– Check whether the distance between the laptop and equipment is longer than the
WLAN transmission distance. (The typical transmission distance between the
WLAN module and laptop is 30 m. An external WLAN network adapter can be
installed on the laptop to extend the typical transmission distance to 70 m.)
– If the distance between the laptop and equipment is within the 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 the connection fails, check whether:
– The connection password is correct.
– The IP address is automatically allocated.
– Another device is connected to the NE through WLAN. Only one device can access
an NE through WLAN at a time. If the access device needs to be switched, you are
advised to disconnect the first device before connecting the second one. The
method of disconnecting an NE is similar to that of connecting an NE.
If the connection is successful, the indicator at the network port on 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 5 After the WLAN connection is set up successfully, double-click the Start Web LCT
icon on the desktop.
The Initialize Web LCT Password window for the Web LCT is displayed through
the Internet Explorer.
Step 6 Specify User Name and Password, and click Confirm.
NOTE
● User name: admin

● At the first login to the Web LCT, set the password as prompted.
● After the password is changed, you need to log in again.

----End
Follow-up Procedure
If you cannot access the login page or the NE list page, configure the Internet
Explorer using the following method.
4.3 Creating NEs Using the Search Method

The search method is generally used to create NEs during site commissioning.
Prerequisites
● The NMS communicates with NEs properly.

● You are an NE user with operation level permissions or higher. You are an
NMS user with NE operator permissions or higher.
● If the NE connection mode is SSL (default) or Normal+SSL, and NEs connect
to the Web LCT through a WLAN, NEs are accessed using the SSL protocol. If
the NEs connect to the Web LCT through Ethernet, you are also advised to
use the SSL protocol.
● 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 opt/oss/NCE/etc/ssl/nemanager/default directory on the NCE
to the WebLCT\conf directory on the Web LCT. Rename default to
certificate. Note that the installation directory on the Web LCT cannot
contain Chinese characters, spaces, or special characters.
– Restart the Web LCT.

Web LCT
Context
The following procedure:
● Searches for NEs using the Search by user port method if the commissioning
NEs are connected directly to the Web LCT through a WLAN.
● Searches for NEs using the NE Search method if the commissioning NEs are
connected directly to the Web LCT through Ethernet cables.
● Searches for NEs using the IP auto discovery method if the site has multiple
NEs, and the NEs are connected directly to the Web LCT through a LAN.
NOTE
● User name for NE login: root

● Default password for NE login: Changeme_123
● You must change the password at your first login with the default one.
Procedure
Step 1 Search for NEs using the Search by user port method if the commissioning NEs
are connected directly to the Web LCT through a WLAN.
1. Search for NEs.

2. Add an NE.
3. Log in to an NE.
NOTE
For NEs of V100R020C10 and later versions, change the initial password as prompted
when logging in to the Web LCT, and keep the new password properly.

Step 2 Search for NEs using the NE Search method if the commissioning NEs are
connected directly to the Web LCT through Ethernet cables.
NOTE
For NEs of V100R020C10 and later versions, change the initial password as prompted when
logging in to the Web LCT, and keep the new password properly.

Step 3 Search for NEs using the IP auto discovery method if the site has multiple NEs.
1. Search for NEs.
2. Add an NE.

3. Log in to an NE.
NOTE
For NEs of V100R020C10 and later versions, change the initial password as prompted
when logging in to the Web LCT, and keep the new password properly.
----End
4.4 Delivering a Commissioning Data Script Using the

Web LCT
If the commissioning data script of a site is available, you can use the Web LCT to
deliver the script to the NE without configuring data onsite.

Prerequisites
● The equipment has been connected to the Web LCT.
● The commissioning data script for the site has been prepared.

Web LCT
Procedure
Step 1 Deliver a commissioning data script.
NOTE
By default, the user name is root and the password is Changeme_123.
----End
4.5 Configuring Commissioning Data

This section describes how to configure site commissioning data for an NE when
you perform site commissioning using the Web LCT.
4.5.1 Changing the NE ID

This section describes how to change NE IDs based on the engineering plan to
ensure that NE IDs are unique. The change does not affect services.
Prerequisites
You are an NMS user with NE maintainer permissions 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 Changing the NE ID.
----End
4.5.2 Changing the NE Name

To better identify an NE in the main topology, name the NE according to the
geographical location of the NE or the equipment connected to the NE.
Prerequisites
You are an NMS user with NE operator permissions or higher.

Web LCT

Context
following table.
Parameter Value
Name Site2-1
Procedure
Step 1 Change the NE name.
----End
4.5.3 Configuring the VLAN ID and Bandwidth for an Inband

DCN
The VLAN ID used by the inband DCN must be different from the VLAN ID used
by services. The bandwidth used by the inband DCN must meet the requirement
for transmitting network management messages.
Prerequisites

Web LCT
Context
The following procedure sets the VLAN ID and bandwidth for an inband DCN to
the planned values listed in the following table.

Parameter Value
Ethernet Board VLANID 4092
Bandwidth(Kbit/s) 1000
Procedure
Step 1 Configure the VLAN ID and bandwidth for an Inband DCN.
It is recommended the default value of Ethernet Board VLANID be used. The
value of Ethernet Board VLANID for each NE must be different from the VLAN ID
of Ethernet services. This parameter specifies the VLAN ID for all inband DCN
channels on an NE. The priority of this VLAN ID is lower than the VLAN ID of the
inband DCN channel over a specific port.
Generally, Bandwidth(Kbit/s) is set to 512 by default. When an NE is located on
an aggregation-layer link, you can set Bandwidth(Kbit/s) to 2 Mbit/s.
Generally, IF Port Bandwidth(Kbit/s) is set to 512 by default. When an NE is
located on an aggregation-layer link, you can set IF Port Bandwidth(Kbit/s) to 1
Mbit/s.
----End
4.5.4 Unbinding QoS Policies for Ports

This section describes how to unbind QoS policies for ports.
Prerequisites

NCE

NOTE
This operation can also be performed on the Web LCT, and the procedure is the same as that on
the NCE.
Context
The following procedure unbinds the QoS policy for the specified port.
NOTE
The RTN 320F is used as an example to describe the procedure.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > QoS Management > Diffserv Domain Management.
Step 2 Enter the Application Object tab page.
Step 3 Unbind the QoS policies for the ports.
----End
4.5.5 Creating a Link Aggregation Group

LAG is short for link aggregation group. If an E-LAG-based EPLA or 1+1 protection
link needs to be created for an NE, configure the E-LAG for access ports.
Prerequisites


Web LCT
Context
The following procedure shows how to create a LAG for an NE to configure 1+1
protection. The following table lists the planned parameters.
Parameter NE
LAG No. Select Assign Automatically (default

value).
LAG Name LAG_01
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 10GE
Procedure
Step 1 Create a LAG.
NOTE

----End
4.5.6 Configuring a Hop of Microwave Link

This section describes how to configure the basic information about a hop of
microwave link on the NE at one end of the link.
Prerequisites
● You are an NMS user with NE operator permissions or higher.
● The two ends of the microwave link can communicate properly.

NCE

NOTE
the NCE.
Context
The following procedure shows how to configure a hop of microwave link.
The planned parameter values are listed in the following table.
Table 4-3 Data planned for the RTN 320F
Parameter Value
Protection 1+0
XPIC Enabled
● Polarization - V: IF2
● Polarization - H: IF1
Link ID - V Polarization - V: 1
Link ID - H Polarization - H: 2
IF Channel Bandwidth 28MHz
AM Status Enabled
Guaranteed Capacity QPSK

Modulation
Full Capacity Modulation 64QAM
TX Frequency(MHz) 25557.000
T/R Spacing(MHz) 1200.000
ATPC Disabled
TX Power(dBm) 11.0
Power to Be -20.0
Received(dBm)
Procedure
Step 1 In the NE Explorer, select the NE from the object tree and choose Configuration >
Microwave Link Configuration.
Step 2 Set related parameters as planned.

NOTE
The RTN 320F is used as an example to describe the configuration process.

----End
4.5.7 Synchronizing Data on Main and Standby NEs in a 1+1

Protection Group
This section describes how to synchronize data of a main NE to its standby NE.
Prerequisites
● An inter-equipment 1+1 protection group has been created.
● The two GE ports connected through a cascading cable must be the same. For
example, both ends use COMBO ports.
● Configuration synchronization can be performed only on the working main
NE.

NCE

NOTE
the NCE.
Context
The following procedure shows how to synchronize data between the main and
standby NEs in a 1+1 protection group.
Procedure
Step 1 Synchronize the data on main and standby NEs in a 1+1 protection group.
----End
4.5.8 Testing the XPI Value

During antenna alignment, you need to test the XPI value range to check whether
the polarization direction of the antenna is aligned.
Prerequisites
● The RTN 320F of the current version does not support MIMO.
● You are an NMS user with NE maintainer permissions or higher.
● All ports are configured with IF parameters as planned.

Web LCT
Context
The following procedure shows how to test the XPI value based on the parameter
values listed in the following table.
Parameter Value Value Range
Opposite NE ID 40802 1~49151

Parameter Value Value Range
Opposite NE Ex-ID 9 1~254
Opposite NE Slot ID 1 1~100
Procedure
Step 1 Test the XPI value.
After the test is complete, check whether the value of XPI(dB) ranges from 19 to
26. If yes, the polarization directions of antennas at both ends of the NE are
aligned. If no, re-align the polarization directions of antennas at both ends until
the XPI value falls within the range of 19 to 26.
----End
4.6 Checking Alarms

By checking the current alarms of the equipment, you can determine whether the
equipment can work normally.
Prerequisites
● The equipment has been connected to the Web LCT.
● Basic NE data has been configured.

Web LCT
Context
The following procedure shows how to check alarms.

Procedure
Step 1 In the NE Explorer, select the NE from the object tree and click in the toolbar.
Step 2 Click Browse Current Alarms.
Step 3 Browse the displayed alarm information.
Check whether there are any alarms, especially the following alarms:
● POWER_ALM
● HARD_BAD
● NESF_LOST
● TEMP_ALARM
● XPIC_LOS
● NB_UNREACHABLE
For details about the preceding alarms and about how to handle them, see the
OptiX RTN 320/320FMicrowave Transmission System Maintenance Guide.
----End
4.7 Aligning Antennas

Antenna alignment is the most important activity for site commissioning. Its result
has a direct effect on the performance of microwave links.
4.7.1 Main Lobe and Side Lobes

Before aligning antennas, you need to master the knowledge about the main lobe
and side lobes of antennas.
Definitions of the Main Lobe and Side Lobes

The strength of the electric field radiated by an antenna varies at different points
in space, which can be shown through an antenna pattern. Generally, the
horizontal pattern is used for the horizontal plane and the vertical pattern for the
vertical plane. Figure 4-4 shows a vertical pattern. There are many lobes in the
pattern. The lobe with the largest radiation direction is called the main lobe, and
other lobes are called side lobes. The first side lobe can affect the antenna
alignment.
Figure 4-4 Main lobe and side lobes

Locating the Main Lobe

Antenna alignment is to align the main lobes of antennas at both ends to
maximize the strength of signals received from the peer antenna.
The main lobe width of the microwave antenna is narrow, usually ranging from
0.6° and 3.7°. For instance, for a 1.2 m antenna at an operating frequency of 23
GHz, the azimuth is only 0.9° when the signal level drops from the peak to zero.
Therefore, you only need to slightly adjust the antenna once signals are detected.
When the main lobe is scanned during antenna alignment, the signal level
changes rapidly. By comparing the received signal peak, you can determine
whether the main lobe is aligned. Generally, the signal peak of the main lobe is 20
to 25 dB higher than that of the first side lobe.
Figure 4-5 shows the antenna propagation model in free space. The side lobes
radiate outward with the main lobe as their center.
Figure 4-5 Horizontal view and front view of the antenna
Scanning Path
When signals are scanned at different elevations (azimuths), the scanned side
lobe signals are sometimes mistaken for main lobe signals. Figure 4-6 shows the
radiation model in the horizontal direction of the antenna. The antenna signal
levels scanned at three different elevations are as follows (values 1 to 7 indicate
the signal levels tested on the RSSI port of the RTN 380AXH).

Figure 4-6 Three scanning paths
● Line AA' indicates that the antenna is almost aligned in the vertical direction
and the elevation does not need to be adjusted. The signal peak of the main
lobe occurs at point 2, and that of the first side lobe occurs at points 1 and 3.
In this case, you only need to slightly adjust the azimuth of the antenna at
point 2 until the signal reaches its peak.
● Line BB' indicates that the elevation of the antenna slightly deviates from the
main lobe. The signal peak occurs at points 4 and 5. The signal peak at point
4 is higher than that 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 adjust the azimuth of the antenna to the middle
position between the two signal peaks. Then, adjust the elevation of the
antenna until three signal peaks in line AA' appear. Slightly adjust the
antenna at point 2 until the signal peak appears.
● 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 peaks
of the first side lobe at points 6 and 7 appear as one signal peak. As a result,
this point may be mistaken for the peak point of the main lobe signal. The
correct method is to adjust the azimuth of the antenna to the middle position
between points 6 and 7. Then, adjust the elevation of the antenna until three
signal peaks in line AA' appear. Slightly adjust the antenna at point 2 until the
signal peak appears.
If the peak of the side lobe signal on one side is obviously higher than that on the
other side, as shown in Figure 4-7, a common error is adjusting the azimuth
leftwards or rightwards along line DD' or adjusting the elevation along line EE'. As
a result, point 1 is mistaken for the peak point of the main lobe signal. The correct
method is to adjust the elevation to the middle position between points 1 and 2
or the azimuth to the middle position between points 1 and 3. Then, repeatedly
adjust the antenna until three signal peaks of line AA' appear. Slightly adjust the
antenna at point 2 as shown in Figure 4-6 until the signal peak appears.

Figure 4-7 Aligning the antenna with the first side lobe
4.7.2 Aligning Single-Polarized Antennas

When aligning single-polarized antennas, you need to adjust the azimuth and
elevation of antennas at both ends to ensure that the main lobes of the antenna
signals are aligned.
Prerequisites
● Antennas are installed according to the network plan.
the microwave link.
● During the commissioning, the weather at both sites is suitable and there is
no threat of rain, snow, or fog.
● The multimeter is calibrated.
● The ATPC function is disabled (this function is disabled on the NE by default).
● The AM function is disabled (this function is disabled on the NE by default).
NOTE
When commissioning the 2x2 MIMO antennas of a single RTN 320, you need to commission
each link separately. That is, mute a link when commissioning the other. Otherwise, interference
may be caused on signal receiving, affecting antenna alignment accuracy.

● Adjustable wrench
● Interphone
● Hex key (delivered with the antenna)
● North-stabilized indicator
● Telescope
● Multimeter

● RSSI test cable (By default, the RSSI test cable is not delivered and needs to
be purchased locally.)
NOTICE
You can adjust the azimuth and elevation of the antenna by adjusting nuts or
screws. For details, see the antenna installation guide. The procedure provided in
this section is for reference only.
The procedure is applicable to the separated RTN 320 and RTN 320F. The
procedure for the integrated RTN 320 is similar. The port for measuring the RSSI is
on the RTN 380AXH.
Figure 4-8 Testing the RSSI voltage using a multimeter (separated RTN 320 and
RTN 320F)

Figure 4-9 Testing the RSSI voltage using a multimeter (integrated OptiX RTN
320)
Procedure
Step 1 Read the voltage (VBNC) of the RSSI port corresponding to the designed receive
power based on the RSSI-RSL curve.
NOTE
The RSSI-RSL curve diagram of the RTN 380AXH is placed in the RTN 380AXH carton.
Step 2 Determine the azimuth of the antenna according to the installation position and
height. Then, adjust the elevation of the antenna to the horizontal position.
NOTE
For some special links, such as the microwave link from the mountain top to the mountain
foot, if the angle between the microwave link and the horizontal plane exceeds the half-
power angle of the antenna, you can slightly adjust the elevation of the antenna to ensure
that the main lobe of the antenna is aligned in the vertical direction.
Step 3 Set the multimeter to the 20 V DC scale, connect the multimeter to the RSSI port
on the local RTN 380AXH through an RSSI test cable, and measure the voltage
(VBNC) of the port.
NOTE
You can use adhesive tapes to fix the multimeter at a position suitable for observation on
the tower so that you can observe the RSSI while adjusting the antenna.
Figure 4-10 Testing the RSSI voltage using a multimeter
RTN 320

RTN 320F
Step 4 Preliminarily adjust the azimuth and elevation of the antenna as follows:
1. Keep the remote antenna fixed.
2. Loosen the azimuth adjustment nut, observe the VBNC measured by the
multimeter, and rotate the antenna within a large range in the horizontal
direction. When the VBNC is not zero, tighten the azimuth adjustment nut.
3. Use the horizontal fine-adjustment nut to rotate the antenna within the
allowed range and record the peak of VBNC measured by the multimeter.
In normal cases, three signal peaks should be scanned, as shown in Figure
4-11.

Figure 4-11 Signal peaks
NOTICE
If other peaks appear when the rotation range is large enough and you have
carefully observed the multimeter, handle the exception according to the
methods described in 4.7.1 Main Lobe and Side Lobes.
4. Adjust the azimuth fine-adjustment nut to ensure that the azimuth of the
antenna reaches the peak at point 2 (the position with the maximum value of
VBNC), as shown in Figure 4-11.
5. Slightly adjust the elevation using the fine-adjustment nut until VBNC reaches
the peak within the scanned range.
6. Fix the local antenna.
NOTE
When you tighten the antenna, ensure that VBNC remains at the maximum value.
Step 5 Adjust the remote antenna by following Step 2 to Step 4. When the remote VBNC
reaches the maximum value, fix the remote antenna.
Step 6 Repeat Step 2 to Step 4 twice to four times until VBNC at both ends reaches the
maximum value, and fix the antennas at both ends.
NOTE
● In preceding steps, only fine adjustment is required.

● After several adjustments, the VBNC of antennas fixed at both ends must reach or exceed the
VBNC value obtained in Step 1.
----End
4.7.3 Aligning Dual-Polarized Antennas (XPIC Links)

When aligning dual-polarized antennas, you need to align the main lobes by
adjusting the azimuth and elevation of the antennas at both ends. You also need
to adjust the feeds of the antennas so that the cross-polarization discrimination
(XPD) meets the specified requirements.
Prerequisites
the microwave link.



● Interphone
● Telescope
● Multimeter
● RSSI test cable (By default, the RSSI cable is not delivered and needs to be
purchased locally.)
● Special spanner for the orthogonal mode transducer (OMT) (delivered with
the OMT)
Context
NOTE
In this procedure, the OptiX RTN 320/320F at each end is installed as follows: The RTN 320 is
installed in a split manner, and the RTN 320F is installed in a separated manner. Adjust the
OMT feed instead of antenna feed if the OptiX RTN 320/320F at each end is installed as follows:
The RTN 320 is directly installed on the OMT, and the integrated RTN 320F is installed on the
OMT.
Procedure
Step 1 At both ends of the site, power off the vertically polarized ODUs and power on the
horizontally polarized ODUs. Ensure that antennas at both ends transmit
horizontally polarized signals.
Step 2 Adjust the azimuth and elevation of antennas at both ends by referring to 4.7.2
Aligning Single-Polarized Antennas, and ensure that the main lobes of
horizontally polarized signals are aligned.
Step 3 Calculate the RSL (P1) of the horizontally polarized signals at the local end.
1. Use a multimeter to test the signal level of the RSSI port on the horizontally
polarized ODU.
2. Calculate the RSL (P1) of the horizontally polarized signals based on the
curve diagram in the ODU carton.
Step 4 Adjust the antenna feed at the local end, and ensure that the RSL of the vertically
polarized signals reaches the minimum value (P2).
1. Power on the vertically polarized ODU at the local end.
2. Move the multimeter to the RSSI port of the vertically polarized ODU to test
the level.

3. Calculate the RSL (P2) of the vertically polarized signals corresponding to the
minimum value according to the curve diagram in the ODU carton.
4. Calculate the XPD1 (XPD1 = P1 – P2).
If... Then...
The calculated XPD1 (XPD1 = P1 – Go to the next step.

P2) is less than 24 dB
The calculated XPD1 (XPD1 = P1 – Go to Step 5.

P2) is not less than 24 dB
NOTE
– The link XPD is obtained through a rollback from the antenna XPD by 6 dB.
– In actual commissioning, the XPD value is usually greater than 24 dB. Try to adjust
the XPD value to the maximum value to ensure that links work in the optimal
state.
5. Release the holder of the antenna feed to some extent, slightly rotate the
feed in a small range, and continuously monitor the level reading until the
test value is the minimum value and the XPD1 is greater than or equal to 24
dB.
Step 5 Record the angle (D1) of the feed.
Step 6 At both ends of the site, power off the horizontally polarized ODUs and power on
the vertically polarized ODUs. Ensure that antennas at both ends transmit
vertically polarized signals.
Step 7 Calculate the RSL (P3) of the vertically polarized signals of the local antenna by
referring to Step 3.
Step 8 Adjust the antenna feed at the local end, and ensure that the RSL of the
horizontally polarized signals reaches the minimum value (P4).
1. Power on the horizontally polarized ODU at the local end.
2. Move the multimeter to the RSSI port of the horizontally polarized ODU to
test the level.
3. Calculate the RSL (P4) of the horizontally polarized signals corresponding to
the minimum value based on the curve diagram in the ODU carton.
4. Calculate the XPD2 (XPD2 = P3 – P4).
If... Then...
The calculated XPD2 (XPD2 = P3 – Go to the next step.

P4) is less than 24 dB
The calculated XPD2 (XPD2 = P3 – Go to Step 9.

P4) is not less than 24 dB

5. Release the holder of the antenna feed to some extent, slightly rotate the
feed in a small range, and continuously monitor the level reading until the
test value is the minimum value and the XPD2 is greater than or equal to 24
dB.
Step 9 Record the angle (D2) of the feed.
Step 10 Slightly rotate the feed to determine a proper feed angle from D1 to D2 so that
XPD1 and XPD2 are still greater than or equal to 24 dB.
NOTE
If D1 and D2 are the same, you do not need to adjust the antenna feed.
Step 11 Tighten all the screws on the antennas at both ends.

NOTE
Use the multimeter to check whether the RSL of the RSSI port is the same as that before the
screws are tightened. This prevents antenna alignment deviation during screw tightening.
----End
Related Information
In practice, you can align dual-polarized antennas by mainly measuring the
vertically polarized signals.
4.7.4 Aligning Dual-Polarized Antennas (Inter-NE MIMO)

When aligning dual-polarized antennas, you need to align the main lobes by
adjusting the azimuth and elevation of the antennas at both ends. You also need
to adjust the feeds of the antennas so that the cross-polar isolation (XPI) meets
the specified requirements.

Prerequisites
● The RTN 320F of the current version does not support MIMO.
● Antennas are installed according to the network plan.
the microwave link.
Tools and Materials

● Interphone
● Telescope
● Multimeter
● RSSI test cable (By default, the RSSI cable is not delivered and needs to be
purchased locally.)
● Special spanner for the OMT (delivered with the OMT)
Context
Figure 4-12 Dual-polarized antennas (inter-NE MIMO)

NOTE
After changing the frequency, align the antennas again to ensure that the XPI value ranges
from 19 dB to 26 dB.
In the case of installation at a MIMO site, ensure that poles where the two antennas are
installed are in parallel. Otherwise, the XPI cannot be adjusted to a value ranging from 19
dB to 26 dB.
Procedure
Step 1 Align the antennas physically.
1. Turn on 1#ODU and 2#ODU, mute other ODUs, and adjust antennas A and B
until the antennas are aligned.
2. Use the same method to align antennas C and D.
Step 2 Align the polarization directions of antennas.
1. Tighten the screws for adjusting the azimuth and elevation of antennas A and
B.
2. Turn on all ODUs, use the Web LCT to calculate the XPI values of the ports on
2#ODU and 4#ODU, and adjust the feed pressing block of antenna A to
ensure that the XPI values of the ports range from 19 dB to 26 dB.
3. When the XPI values of the ports on 2#ODU and 4#ODU range from 19 dB to
26 dB, use the Web LCT to calculate the XPI values of the ports on 1#ODU
and 3#ODU. Then, adjust the feed pressing block of antenna B to ensure that
the XPI values of the ports range from 19 dB to 26 dB.
4. When the XPI values of ports on 1#ODU and 3#ODU range from 19 dB to 26
dB, use the Web LCT to calculate the XPI values of ports on 2#ODU and
4#ODU. Then, check whether the XPI values of ports on 2#ODU and 4#ODU
range from 19 dB to 26 dB. If not, adjust the feed pressing block of antenna A
again to ensure that the XPI values of the ports on 2#ODU and 4#ODU range
from 19 dB to 26 dB. Then, calculate the XPI values of the ports on 1#ODU
and 3#ODU again to check whether the values range from 19 dB to 26 dB. If
not, adjust the feed pressing block of antenna B again to ensure that the XPI
values of ports on 1#ODU and 3#ODU range from 19 dB to 26 dB.
Repeatedly check the XPI values of ports on 1#ODU, 2#ODU, 3#ODU, and
4#ODU, and adjust the feed pressing block of antenna A or B. Ensure that the
XPI values of ports on 1#ODU, 2#ODU, 3#ODU, and 4#ODU range from 19
dB to 26 dB.
5. After confirming that the XPI values of ports on 1#ODU, 2#ODU, 3#ODU, and
4#ODU meet the requirements, lock the polarization directions of antennas A
and B.
6. Adjust the polarization directions of antennas C and D in the way described in
Step 2.1 to Step 2.5.
----End

4.8 Checking the Microwave Link Status and Receive

Power
After antenna alignment, check whether the status of a microwave link is normal
and whether the receive power meets requirements.
Prerequisites
● The antennas have been aligned.
● Basic data has been configured for all NEs on the network.

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 6.1 Handling the Fault of the Receive Power Failing to Meet the Design
Requirements.
----End

4.9 Configuring MIMO Links (Inter-NE)

After aligning antennas, you need to configure MIMO links.
Prerequisites
● The RTN 320F does not support MIMO.
● Basic data has been configured for all NEs on the network.

Web LCT
Context
The following procedure configures a 4x4 MIMO link.
The planned parameter values are listed in the following table.
Parameter Value
IF Channel Bandwidth(MHz) 56MHz
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
T/R Spacing(MHz) 266.000
TX Status unmute
NOTE
The configuration example shows the configuration of 4x4 MIMO links. For the
configuration of 2x2 MIMO links, you only need to set the MIMO Type in the configuration
example to 2x2 MIMO.
Procedure
Step 1 Configure MIMO Links.

----End
4.10 Configuring FO Maintenance Through the BBU

The FO device can be maintained under the tower through the service port of the
BBU only after the port enablement status, port IP address, subnet mask, and
gateway IP address are configured for the microwave device.
Prerequisites

NCE
NOTE
the NCE.
Context
Configure the information of port ETH LOCALIF2 on the FO device as follows.
Parameter Microwave BBU PC
Port Name 1-MXXI4-3(GE(e)) FE/GE0 FE/GE0 NIC
Enabled Status Enabled - - -
IP Address 192.168.15.13 192.168.15 192.168.2. 192.168.2.2

.16 1

Parameter Microwave BBU PC
Subnet Mask 255.255.255.0 255.255.25 255.255.2 255.255.255.0

5.0 55.0
Gateway IP 192.168.15.16 - - 192.168.2.1
Figure 4-13 Networking diagram for configuring FO maintenance through the

BBU
NOTE
All UMPT panels support FO maintenance through the BBU. The preceding figure uses the
UMPTe panel as an example.
Procedure
1. Configure the information of port ETH LOCALIF2 on the FO device.
2. Configure the BBU.

a. Create a VRF on the BBU side.
ADD VRF: VRFIDX=7;
b. Set the IP address of the port on the BBU that is directly connected to the
FO device to the gateway IP address of port ETH LOCALIF2 on the FO
device, for example, 192.168.15.16.
ADD ETHPORT: SN=6, SBT=BASE_BOARD, PORTID=2, PA=COPPER,SPEED=AUTO,DUPLEX=AUTO;
ADD INTERFACE: ITFID=1, ITFTYPE=VLAN, VLANID=4094, VRFIDX=7;
ADD IPADDR4: ITFID=1, VRFIDX=7,IP="192.168.15.16", MASK="255.255.255.0";
c. Set the IP address of the electrical port on the BBU that is connected to
the Web LCT to 192.168.2.1.
ADD ETHPORT:SN=6, SBT=BASE_BOARD, PN=0, PORTID=0, PA=COPPER, SPEED=AUTO,
DUPLEX=AUTO;

ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, VRFIDX=7,PT=ETH, PORTID=0,

ARPPROXY=ENABLE;
ADD IPADDR4: ITFID=0, VRFIDX=7,IP="192.168.2.1", MASK="255.255.255.0";
d. Set the forwarding mode to route.
SET GTRANSPARA: FORWARDMODE=ROUTE
3. Set the IP address of the laptop installed with the Web LCT to be in the same
network segment as the IP address of the electrical port on the BBU (for
example, 192.168.2.2), and set the gateway IP address to the IP address of
the electrical port on the BBU (for example, 192.168.2.1).
4.11 Connecting to the FO Device Through the BBU

Service Port
This section describes how to connect to the FO device through the BBU service
port under a tower. After the FO device is connected, you can commission,
configure, and maintain the FO device.
Prerequisites
● Operations in 4.10 Configuring FO Maintenance Through the BBU have
been performed on the FO device and service interworking can be
implemented between the FO device and the BBU.

Web LCT
Procedure
1. Connect the Web LCT to the laptop. For details, see 4.2 Accessing the Web
LCT.
2. Connect to the FO device.
a. Add the FO device to the Web LCT by using the IP address of port ETH
LOCALIF2 on the FO device.

b. Log in to the FO device.

NOTE
● User name for NE login: root

● Default password for NE login: Changeme_123
● You must change the password at your first login with the default one.

Commissioning and Configuration Guide 5 System Commissioning
5 System Commissioning
This chapter describes the specific commissioning procedures for all system
commissioning items.
5.1 Configuring Network-wide Service Data

After site commissioning is performed for each hop of microwave link on the
microwave network, the DCN communication between NEs carried by microwave
links becomes normal. In this case, an NE can be accessed using the NCE to
configure the network-wide service data.
5.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 Ethernet tester is required.
5.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/320F.
5.4 Testing ATPC
OptiX RTN 320/320F supports the ATPC meter-free test.
5.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.
5.6 Checking the Clock Status
Checking the clock status for all NEs on a microwave transmission network
ensures that the NE clocks are synchronized.
5.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).
5.8 Testing Ethernet Service Performance
This section describes how to test Ethernet service performance using the NE-
inherent test functions.

5.1 Configuring Network-wide Service Data

After site commissioning is performed for each hop of microwave link on the
microwave network, the DCN communication between NEs carried by microwave
links becomes normal. In this case, an NE can be accessed using the NCE to
configure the network-wide service data.
Context
NOTE
For details about how to configure network-wide service data, see 7 Configuring Network-
wide Service Data.
5.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 Ethernet tester is required.
5.2.1 Testing Ethernet Services Configured on a Per-NE Basis

To test Ethernet services configured on a per-NE basis, you need to manually
create the ETH OAM.
Prerequisites
Ethernet services have been configured.
NOTE
You are advised to test low-priority Ethernet services in good weather conditions where full
capacity AM scheme is used.

NCE
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 5-1.

Figure 5-1 Networking diagram
Procedure
Step 1 Create an MD.
Step 2 Create an MA.

Step 3 Create an MEP.
Step 4 Create a remote MEP.

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.
● If the value of LossRate in Result is 0, the test is successful.

● 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 Check whether services are

within the specified period. interrupted.
Packets are lost. Check whether the service traffic is

higher than the transmission
bandwidth.
Check the link for bit errors.
----End

5.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/320F.
Prerequisites
● The adaptive modulation (AM) function has been enabled for the microwave
link to be tested.
● Weather conditions are favorable.

Web LCT
NOTE
The NCE does not support this operation.
Context
The following procedure tests the AM switching function on an NE.
Procedure
Step 1 Test one-click AM switching.
NOTE
----End

5.4 Testing ATPC

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

NCE
NOTE
the NCE.
Context
The following procedure tests the ATPC function on an NE.
Procedure
Step 1 In the NE Explorer, select the NE and choose Diagnosis&&Maintenance > ATPC
Meter-free Test from the function tree.
Step 2 Test ATPC.
NOTE

----End
5.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.
5.5.1 Testing ERPS

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
● ERPS has been configured for OptiX RTN 320/320Fs on a ring network.
● Ethernet links on the ring network are connected correctly.

NCE
NOTE
the NCE.
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 5-2, the Ethernet services from NE 1 to NE 4 are protected by ERPS, and
NE 2 is the RPL owner node.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet
Protection > ERPS Management from the function tree.
Step 2 Query the working status of the protection group on NE 2 before the switching.
State Machine Status should be Idle. East Port Status should be Block. West
Port Status should be Unblock.

Step 3 Test the availability of the Ethernet service. For details, see 5.2.1 Testing Ethernet
Services Configured on a Per-NE Basis.
The value of LossRate in Detection Result should be 0.
Step 4 Set TX Status to Mute for the IF2 port on NE 4.
1. In the NE Explorer, select the NE and choose Configuration > Microwave
Link Configuration from the function tree.
2. Set TX Status of the NE to Mute.

Step 5 Refer to step 1 and step 2 to query the working status of the protection group on
NE 2 after the switching.
Step 6 Test the availability of the Ethernet service. For details, see 5.2.1 Testing Ethernet
Services Configured on a Per-NE Basis.
The value of LossRate in Detection Result should be 0.
Step 7 Refer to step 4 to set TX Status of the IF2 port on NE 4 to Unmute.
----End
5.5.2 Testing 1+1 Protection Switching (Intra-equipment 1+1

Protection)
You can verify the 1+1 protection functions by checking the changes of the main
and standby working boards in the 1+1 protection group before and after
switching.
Prerequisites
● Ethernet services and 1+1 protection have been configured.

NCE


The basic configurations are as follows:
● Main IF port: IF1
● Standby IF port: IF2
NOTE
The following test procedure is applicable to all types of the 1+1 protection. The 1+1 HSB is
used as an example.
In the following procedure, Ethernet services protected by 1+1 hot standby (HSB)
from NE 11 to NE 12 is taken as an example.
Procedure
Step 1 In the NE Explorer, select the NE from the object tree and choose Diagnosis &
Maintenance > One-Touch Test from the function tree.
Step 2 In Optional Acceptance Items, select HSB switching test
Operation diagram for the RTN 320
Operation diagram for the RTN 320F

Step 3 Select the desired protection group from Available Protection Groups.
Operation diagram for the RTN 320
Operation diagram for the RTN 320F
Step 4 Click Start.

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

Protection)
You can verify the 1+1 protection function by checking the changes of the main
and standby devices in the 1+1 protection group before and after switching.
Prerequisites
● Ethernet services and 1+1 protection have been configured.
● Static link aggregation groups (LAGs) have been configured for third-party
devices when the devices are connected without optical splitters.


NCE

When the optical splitters are not used, the basic configurations are as follows:
● Main OptiX RTN 320/320Fs: NE 11 and NE 12
● Standby OptiX RTN 320/320Fs: NE 21 and NE 22
NOTE
The following test procedure is applicable to all types of the 1+1 protection. The 1+1 HSB is
used as an example.
In the following procedure, Ethernet services protected by 1+1 hot standby (HSB)
from NE 11 to NE 12 is taken as an example.
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 the NE Explorer, select NE 11 from the object tree and choose
Configuration > IF 1+1 Protection > Cascade 1+1 Protection from the
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 working status of the protection group on NE 11 before the switching.
Configuration > IF 1+1 Protection > Cascade 1+1 Protection from the
function tree.
2. In Protection Group, select the desired protection group and click Query.
3. Ensure that the device NE in Protection Group is an active NE NE 11.
Step 3 Verify the availability of the Ethernet service before switching. For details, see 5.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 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.
1. In the NE Explorer, select the NE 11 from the object tree and choose
Configuration > IF 1+1 Protection from the function tree.
2. In Protection Group, select the desired protection group and click Query.
3. Ensure that the device NE in Protection Group is a standby NE NE 21.
Step 6 Verify the availability of the Ethernet service after switching. For details, see 5.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 set in Step 1 to the original value.
----End
5.5.4 Testing MPLS APS Protection Switching

You can verify the MPLS APS protection switching function by checking the change
of the MPLS tunnel in an MPLS APS protection group before and after the
switching.
Prerequisites
● The MPLS tunnel protection group must be created properly.
NOTE
The RTN 320F does not support MPLS.

NCE

NOTE
the NCE.
Context
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 two ends negotiates through the
APS protocol. Then, the transmit end transmits the services over the protection
tunnel and the receive end receives the services from the protection tunnel. In this
manner, the services are switched.

Figure 5-5 shows the connection diagram for testing MPLS APS protection
switching.
Figure 5-5 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 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 forcibly.
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 tunnel 1:1 protection groups on NE A and
NE B after the switching.

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
● If Forced Switching is performed at the previous step, the state of the tunnel protection
group should be Forced Switching.
● If Manual Switching to Protection is performed at the previous step, the state of the
tunnel protection group should be Manual (Working to Protection) Switching.
Step 4 Restore the services on NE A and NE B to the working tunnel.

switching.
3. Right-click the tested protection group and then choose Clear from the
shortcut menu.
4. Click OK.
The Operation Result dialog box is displayed.
5. Click Close.
6. Click Query.
Services are restored to the working tunnel.
----End
5.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
● Clock configuration has been completed.
● The links that transmit clock signals are functioning properly.

NCE
NOTE
the NCE.
Context
The following procedure checks the clock status of NEs on a network.
Procedure
Step 1 In the NE Explorer, select NE A and choose Configuration > Clock > Physical
Clock > Physical > Clock Subnet Configuration from the function tree.
Step 2 Check the clock status.
If the clock of an NE is used as the master clock for the microwave network, this
clock must be in free-run mode and the clocks of other NEs must be in tracing
mode. If a service clock or an external clock is used as the master clock for the
microwave network, the clocks of all the NEs must be in tracing mode.

Step 3 Repeat step 1 and step 2 to check the clock status of the other NEs on the
network.
----End
5.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
● Antennas have been aligned, and the RSLs at both ends of the microwave link
meet requirements.
● TX Power configured for the OptiX RTN 320/320F is the same as the actual
transmit power.

NCE
NOTE
the NCE.
Context
The procedure for testing the fade margin is as follows:
● Test the mapping between RSLs and MSEs at multiple sites.
● Calculate the RSL corresponding to the MSE demodulation threshold to
determine the receiver sensitivity.
● 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. A test on the main link in 1+1 protection configuration requires signals
transmitted on main channels at both ends. To test the standby microwave
link, you need to forcibly switch services to the standby channel at both ends
of the link before performing the test.
3. For an XPIC link, you need to test the channels in the horizontal and vertical
polarization directions synonymously. Therefore, the fading margins of the
two OptiX RTN 320/320Fs are reported at the same time.

Procedure
Step 1 Disable adaptive modulation (AM) and automatic transmit power control (ATPC)
functions on the microwave link between two sites.
1. In the NE Explorer, select the NE from the object tree and choose
Configuration > Microwave Link Configuration from the function tree.
2. Disable AM ATPC functions on the microwave link between two sites.
3. Click Apply.
Step 2 Test the fade margin over the microwave link.
Diagnosis&Maintenance > Fade Margin from the function tree.
2. Test the fade margin over the microwave link.
NOTE

Step 3 Enable AM and ATPC functions on the microwave link by referring to 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
5.8 Testing Ethernet Service Performance

This section describes how to test Ethernet service performance using the NE-
inherent test functions.
Context
NOTE
The RTN 320F supports this function.
5.8.1 Testing Ethernet Service Performance (Based on RFC

2544)
This section describes how to use the RFC 2544-compliant function to test packet
loss, delay, and throughput for Ethernet services
Prerequisites
● Ethernet services have been configured.

NCE

Context
NOTICE
● Performance tests for E-Line services, E-LAN services, and hybrid E-Line and E-
LAN services are supported.
● Do not modify data configuration during the test.
● During the test, if the network-side port for Ethernet services is configured in a
LAG group and the LAG group works in load sharing mode, only the data of a
single link is returned.
● The ports at both ends for testing Ethernet services must be Ethernet ports.
● During the test, only the tested Ethernet services over the test ports are
interrupted in normal cases.
● Large test traffic may affect the traffic of other services and even cause packet
loss of other services.
● An NE cannot function as both the initiator and reflector.

The following test procedure takes the Ethernet service between port 1 on NE A
and port 2 on NE B as an example, as shown in Figure 5-6. The Ethernet services
configured on NE A and NE B are E-LAN services.
NOTE
To test E-LAN services based on RFC 2544, the initiator sends test packets or delay packets
with specified traffic, and the reflector loops back the packets based on packet filtering
conditions (such as VLAN IDs and MAC addresses). The initiator calculates network
performance indicators by collecting statistics on the number of sent and received packets
or information of delay packets.

Procedure
Step 1 Choose Maintenance > Test and Diagnose > Instrument-Free Measurement >
Perform RFC 2544 Test from the main menu.
The Create Test Instance dialog box is displayed.
Step 2 Choose General > Display Advanced Parameters. Configure general test
information.
Parameters are described as follows:
1. Throughput test
– Test Rate (Mbit/s): indicates the upper limit of the rate at which the
device sends test packets. Its value range is 1 Mbit/s to 10000 Mbit/s.
NOTE
▪ After the transmission rate upper threshold is specified (lower threshold is fixed to
1 kbit/s), the NE performs a test with the upper threshold and the lower
thresholds respectively. The NE checks for packet loss during the tests at the upper
threshold and lower threshold rates, and uses a dichotomy to calculate a new
transmission rate based on the packet loss condition. Repeat this step until a
maximum transmission rate that meets the requirements for the bandwidth
precision and packet loss precision is found as the throughput.
▪ If the specified test rate is lower than the actual bandwidth, the throughput in the
test result is equal to the specified test rate when the test is successful. Therefore,
you are advised to set the test rate to a value higher than the actual physical
bandwidth.
▪ If the specified test rate is lower than the port rate:

○ When the UNI is not configured in a LAG, the test rate must be less than or
equal to the physical bandwidth of the interface (depending on the GE/FE
type of the interface. The test rate is considered as 1 Gbit/s for an IF port).
– Test Duration (s): indicates the maximum test duration for a specific
packet length. Its value ranges from 10s to 172800s.

NOTE
▪ The test duration must be longer than twice the test interval.
▪ If the throughput is calculated out within a test duration, the test for the specific
packet length ends. If the throughput fails to be calculated out within a test
duration, the test for the specific packet length fails and a timeout error is
returned.
– Packet Loss Ratio: indicates the packet loss precision. After performing a
test at a specified rate, the NE checks whether packet loss occurs
according to this parameter value.
– Test Precision (kbit/s): indicates the throughput test precision. The
higher the precision, the longer the test duration.
– Packet Transmission Interval (s): indicates the packet transmission
duration in a throughput test. Its value ranges from 1s to 60s.
NOTE
This parameter setting is related to the test duration. The longer the packet
transmission duration, the longer the total test duration. It is advisable to set it to its
maximum value 60s.
2. Packet loss ratio test
– Test Rate: indicates the upper limit of the rate at which the device sends
test packets. Its value range is 1 Mbit/s to 10000 Mbit/s.
– Test Duration: indicates the maximum test duration for a specific packet
length. Its value ranges from 10s to 172800s.
3. Delay test
– Test Rate: indicates the upper limit of the rate at which the device sends
test packets. Its value range is 1 Mbit/s to 10000 Mbit/s.
– Test Duration: indicates the maximum test duration for a specific packet
length. Its value ranges from 10s to 172800s.
NOTE
The test duration must be longer than twice the test interval.
– Packet Transmission Interval: indicates the delay packet transmission
interval in a delay test.
4. Packet Size (bytes): One to seven packet lengths can be set; that is, delay
tests can be performed for a maximum of seven packet lengths at the same
time.
Step 3 Select Initiator and configure the initiator information.


● Initiator: indicates the UNI test port at the initiator end.
● Destination MAC Address: Indicates the destination MAC address carried in
packets initiatively sent by the NE (for example, 00-00-00-00-00-01 or
00-00-00-00-00-02). The reflector end reflects packets according to the
destination MAC address. The MAC address configuration at the initiator end
must be consistent with that at the reflector end.
● For L2 services, Destination MAC Address needs to be configured and
Destination IP Address does not need to be configured. In addition, MAC
addresses must be unicast MAC addresses.
● VLAN ID: indicates the VLAN ID of the E-LAN service.
● 802.1p Priority: indicates the VLAN priority carried in the packets initiatively
sent by the device.
Step 4 Select Reflector and configure the reflector information.

● Reflector: Indicates the reflector UNI test port.

● Reflector MAC Address: indicates the MAC address based on which the
reflector reflects packets. The MAC address configuration at the initiator end
must be consistent with that at the reflector end.
● For L2 services, Destination MAC Address needs to be configured and
Destination IP Address does not need to be configured. In addition, MAC
addresses must be unicast MAC addresses.
● VLAN ID: indicates the VLAN ID of the E-LAN service.
Step 5 After the configuration is complete, click OK.
Step 6 Click Start to start the instrument-free test.
Step 7 After the test is complete, click Export Report to export the test reports.
----End
5.8.2 Testing E-Line Service Performance (Based on OAM)

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
● The Ethernet services for NEs at both ends must be VLAN-based E-Line
services, that is, port+VLAN<->port+VLAN E-Line services.

NCE
Context
NOTICE
● The ports at both ends for testing Ethernet services must be Ethernet ports.
During the test, all Ethernet services over the test ports are interrupted.
● 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. You are advised to cancel these configurations when testing
services.
● If the source port of the tested services carries other services, the test results
may be inaccurate. You are advised to disconnect other services when testing
services.
● V100R006C00 and later versions support intra-equipment LAG/PLA/EPLA/1+1
protection groups. Cascading protection is not supported.
● 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.


NE 2 as an example, as shown in Figure 5-7. The Ethernet services configured on
NE 1 and NE 2 are VLAN-based E-Line services.
The Ethernet service between NE 1 and NE 2 has the VLAN ID of 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 ends cannot be successfully created.
Procedure
Step 1 Disable the inband DCN of the test ports on NE 1 and NE 2.
Take NE 1 as an example.
Communication > DCN Management from the function tree.
2. Click the Port Settings tab.
3. Select FE/GE and set parameters for the ports that need to use inband DCN.
4. Click Apply.
Step 2 Disable the access control of the test ports on NE 1 and NE 2.
2. Click the Access Control tab.
3. Disable the access control function for the DCN port.

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

Configuration > Interface Management > Ethernet Interface from the
function tree.
2. Click the Layer 2 Attributes tab.
3. Change the value of Tag to Access for Ethernet ports. Set Default VLAN ID
to the VLAN ID of the E-Line service to be verified. In this example, set
Default VLAN ID to 100.
Step 4 Configure a sink end for the test.

1. In the NE Explorer, select NE 2 from the object tree and choose Diagnosis &
Maintenance > Data Service Performance Test from the function tree.
2. Select the Ethernet service to be tested, enter Test Name, and set Test As to
Sink.
3. In this example, the service port is on the sink node, so set Sink Status to
Enabled.
NOTE
If Ethernet port is on the source node, Source Status should be set to Enabled.
4. Click Apply.
Step 5 Configure a source end for the test and initiate the test.
Diagnosis&Maintenance > Data Service Performance Test from the
function tree.
2. Select the Ethernet service to be tested, specify Test Name as that on NE 2,
set Tested As to Source.

3. In this example, the service port is on the source node, so set Source Status
to Enabled.
NOTE
If Ethernet port is on the sink node, Sink Status should be set to Enabled.
4. Click Apply.
5. Click Start.
NOTE
Only the source NE 1 can initiate the test, and the sink NE 2 cannot initiate the test.
6. Click OK.
The system starts the test and displays the test progress and test result.
NOTE
The system tests the following parameters:

– Throughput, Latency, Packet Loss Ratio when Frame Length(Bytes) is 64, 128, 256,
512, 1024, 1280, and 1518
– Latency and Packet Loss Ratio when Throughput Percentage(%) is 80, 90, and 100
7. Optional: After the progress bar indicates that the test is 100% complete,
click Export Report.
Data Service Performance Test Report is displayed.
NOTE
– Compared with an instrument-based test, the test result of this operation may be
inaccurate. When the bandwidth of the tested service is lower than 70 Mbit/s, the
tested error rate of the packet loss ratio is less than 1%. When the bandwidth of the
tested service is greater than or equal to 70 Mbit/s, the tested error rate of the packet
loss ratio is less than 0.2%. If the tested packet loss ratio is not 0 and is within the
preceding error ranges, perform the test several times. If the test results show that few
packets are lost and the packet loss ratio of services with long frames is higher than
that of services with short frames, we consider that no packet is lost for the tested
service.
– Compared with the throughput in practice, the throughput in test results of long-frame
services has an error rate lower than 5%.
– The latency result and packet loss ratio result are the results of bidirectional services.
----End
5.8.3 Testing the Long-term Packet Loss Ratio

This section describes how to test the long-term packet loss ratio of VLAN-based
E-Line services with different frame lengths.
Prerequisites
● The Ethernet services for NEs at both ends must be VLAN-based E-Line
services, that is, port+VLAN<->port+VLAN E-Line services.


NCE
Context
NOTICE
● Do not modify data configuration during the test.

● During the Ethernet service test, all Ethernet services over the test ports are
interrupted.
● 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. You are advised to cancel these configurations when testing
services.
● If the source port of the tested services carries other services, the test results
may be inaccurate. You are advised to disconnect other services when testing
services.
● V100R006C00 and later versions support intra-equipment LAG/PLA/EPLA/1+1
protection groups. Cascading protection is not supported.
● 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.

NE 2 as an example, as shown in Figure 5-8. The Ethernet services configured on
NE 1 and NE 2 are VLAN-based E-Line services.
The Ethernet service between NE 1 and NE 2 has the VLAN ID of 100.
Procedure
Step 1 Disable the inband DCN of the test ports on NE 1 and NE 2.

2. Click the Port Settings tab.
3. Select FE/GE and set parameters for the ports that need to use inband DCN.
4. Click Apply.
Step 2 Disable the access control of the test ports on NE 1 and NE 2.
2. Click the Access Control tab.
3. Disable the access control function for the DCN port.
NOTICE
This operation may cause DCN interruption.
Step 3 Configure the TAG attributes for the test ports.
Configuration > Interface Management > Ethernet Interface from the
function tree.
2. Click the Layer 2 Attributes tab.
3. Change the value of Tag to Access for Ethernet ports. Set Default VLAN ID
to the VLAN ID of the E-Line service to be verified. In this example, set
Default VLAN ID to 100.
Step 4 Configure a sink end for the test.

1. In the NE Explorer, select NE 2 from the object tree and choose Diagnosis &
Maintenance > Data Service Performance Test from the function tree.
2. Select the Ethernet service to be tested, enter Test Name, and set Test As to
Sink.
3. In this example, the service port is on the sink node, so set Sink Status to
Enabled.
NOTE
If Ethernet port is on the source node, Source Status should be set to Enabled.
4. Click Apply.
Step 5 Configure a source end for the test and initiate the test.
Diagnosis&Maintenance > Data Service Performance Test from the
function tree.
2. Select the Ethernet service to be tested, specify Test Name as that on NE 2,
set Tested As to Source.
3. In this example, the service port is on the source node, so set Source Status
to Enabled.
NOTE
If Ethernet port is on the sink node, Sink Status should be set to Enabled.
4. Click the Long-term Packet Loss Ratio tab.
5. Configure test parameters.
– Set Frame Length(Bytes) to 64.

– Set Throughput Percentage(%) to 80.
NOTE
To test the long-term packet loss ratio when the throughput percentage is 90%, set
Throughput Percentage(%) to 90. To test the long-term packet loss rate at a specific
traffic volume, configure a flow whose C-VLAN ID is 100 in the port policy for the service
port and configure the specific CAR for the flow. In this case, set Throughput
Percentage(%) to 100.
6. Click Start Long-term Test.
The system starts the test and displays the test progress and test result.
NOTE
– Only the source NE 1 can initiate the test, and the sink NE 2 cannot initiate the test.
– After the test time lasts for 24 hours (commonly used test time), click Stop Long-term
Test and check the test result.

7. Optional: After the progress bar indicates that the test is 100% complete,
click Export Report.
Data Service Performance Test Report is displayed.
NOTE
Tests may have an error rate in the results. When the number of received packets is
different from the number of transmitted packets (with the error rate less than a
millionth), you can conclude that no packet loss occurs for the tested service.
Step 6 Repeat Step 5.5 to Step 5.7 to test the long-term packet loss ratio when the
following parameters are set.
Set the value of Frame Length(Bytes) to 64, 128, 256, 512, 1024, 1280, and
1518 respectively.
Step 7 After the test is complete (that is, the test progress is 100%), set the enabling
status of the node corresponding to the test port to Disabled.
----End

Commissioning and Configuration Guide 6 Handling Common Faults During Site Deployment
6 Handling Common Faults During Site

Deployment
This chapter describes how to handle common faults during site deployment.
6.1 Handling the Fault of the Receive Power Failing to Meet the Design
Requirements
This section describes how to handle the fault of the receive power failing to meet
the design requirements.
6.1 Handling the Fault of the Receive Power Failing to

Meet the Design Requirements
This section describes how to handle the fault of the receive power failing to meet
the design requirements.
Fault Symptom
No hardware alarm is reported on the equipment, but the receive power does not
meet the design requirements (the difference between the receive power and the
designed value is greater than 3 dB), or even the MW_LOF alarm is reported on
the microwave link.
Fault Analysis
No hardware alarm is reported, so the equipment is running normally. Diagnose
the fault from the following aspects:
● NE configurations
● Link transmission conditions and network plan
● Hardware installation and antenna alignment
Procedure
Step 1 Check the link transmission conditions and network plan.

Commissioning and Configuration Guide 6 Handling Common Faults During Site Deployment
● Verify that antennas are aligned under favorable weather conditions, free
from the impact of rainfall, snow, or fog.
● 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 7 Configuring Network-wide Service Data
7 Configuring Network-wide Service Data
This document describes the process and procedure for configuring the equipment
using configuration examples and provides the data configuration methods for
you to complete various configuration tasks in actual applications.
NOTE
This document describes the service configuration on the NCE.
7.1 Configuration Preparations

Before configuring the NE data, you must make the required preparations.
7.2 General Configuration Process
Select a proper configuration process based on the actual configuration scenarios.
7.3 Common Network Scenarios of Configuration Examples
This section provides the initial configuration examples which are based on six
network scenarios and cover all operations in the general configuration process.
7.4 Configuring the Network Topology
You can manage a transport network by using the NCE only after configuring the
network topology.
7.5 Configuring Microwave Links
Before configuring services on a microwave link, you need to configure the
microwave link.
7.6 Configuring Ethernet Services
Ethernet services include Native Ethernet line (E-Line) services and Native
Ethernet local area network (E-LAN) services.
7.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.
7.8 Common Service Configuration Operations
This section provides hyperlinks to common service configuration operations.
7.1 Configuration Preparations

Before configuring the NE data, you must make the required preparations.

Prerequisites
NOTE
This document describes how to configure the integrated RTN 320, split RTN 320 OAU 2A,
and RTN 320F OAU 2F. The split RTN 320 OAU 2A is used as an example to describe the
configuration process. The configuration process for the integrated RTN 320 is similar to
that for the RTN 320F OAU 2F. If there are configuration differences among the integrated
RTN320, split RTN 320 OAU 2A, and RTN 320F OAU 2F, they will be described separately.
7.1.1 Preparing Documents and Tools

Related documents and tools must be available to ensure the proper configuration
of data.
Documents
● Network planning documents
● OptiX RTN 320/320F Radio Transmission System Commissioning and
Configuration Guide
Tools
● A computer where the NCE server software is installed
● A computer where the NCE client software is installed
NOTE
For requirements and methods for installing NCE software and hardware, see the documents
that accompany the NCE.
7.1.2 Checking Configuration Conditions

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

● Data communication network (DCN) communication between the gateway
NE and the non-gateway NEs must be normal.
● The network communication between the NCE server and the gateway NE
must be normal.
● The NCE client can log in to the NCE server and has network operator rights
or higher.
● The gateway NE must log in to the NCE client.
7.1.3 NCE Quick Start

The NCE quick start guide helps to learn about basic operations on the NCE client.

7.1.3.1 Logging In to the NCE Client

The NCE uses the client/server architecture and allows multiple clients. You can
log in to the NCE client with a PC.
Prerequisites
● The local PC is connected properly to the NCE server, and the NCE server is
running properly.
● You have obtained the account and password for login.

PC
● The operating system of your PC and web browser must meet the following
requirements.
Table 7-1 O&M-plane configuration requirements
Item Basic Configuration Requirement
Memory 4 GB or larger
Hard disk Free hard disk: 8 GB or larger
Operating ● Windows 7 (32-bit or 64-bit)

system ● Windows 10 (32-bit or 64-bit)
Web browser ● Internet Explorer 11 or later (32-bit or 64-bit)

● Google Chrome 50 or later (32-bit or 64-bit)
● Firefox 40 or later (32-bit or 64-bit)
● Edge 20 or later (64-bit)
Resolution 1366 x 768 or higher (recommended: 1920 x 1080)
● On the NCE O&M plane, the default user admin serves as the system
administrator who can manage all resources and has all operation
permissions. The initial password of the user is Changeme_123. If you enter
incorrect passwords for user admin for five consecutive times within 10
minutes, the login IP address will be locked for 10 minutes.
● If three accounts using a login IP address are locked within 10 minutes, this IP
address will be locked for 30 minutes.
● If the login using an IP address meets the IP address lockout conditions
specified on the Account Policy page, this IP address will be locked.
● If the login using a local account meets the account lockout conditions
specified on the Account Policy page, this account will be locked for 30
minutes by default.
● You can wait until the account is unlocked or contact the security
administrator to unlock the account and then log in to the system again.

Procedure
Step 1 Enter https://IP address of the O&M plane:Port number in the address box of the
web browser, and press Enter.
NOTE
● The IP address of the O&M plane is the client login IP address configured on the
Common_Service node. If the Common_Service node is deployed in a cluster, this IP
address is the floating IP address of the Common_Service node cluster. If the
Common_Service node is a single instance, this IP address is the client login IP address
of the Common_Service node.
● The port number is that of the system server and its default value is 31943.
Step 2 In the Login dialog box, fill in Username and Password.

NOTE
You need to change the initial password on your first login. If you forget the password for
user admin, you can reset the password only by reinstalling the system.
Step 3 Click Log In.
----End
7.1.3.2 Logging Out of the NCE Client

You need to log out of the NCE client after you are done using it.
Prerequisites
You are an NE user with Operation Level permissions or higher.You are an NMS
user with NE operator permissions or higher.

PC
Procedure
Step 1 In the upper right corner of the window, click the username and choose Log Out.
NOTE
● If Auto-logout if no activity within is configured, the user session is automatically

logged out if no operation is performed within the period specified by this parameter.
● If the web browser is forcibly closed, the session will not be logged out immediately but
30 minutes later. Therefore, do not forcibly close the web browser.
● Sessions are forcibly logged out under attacks.
----End
7.1.3.3 Using Online Help

Online Help provides help information about the NCE.

Prerequisites
Tools, Equipment, and Materials

NCE
NOTE
The Web LCT does not support this operation.
Procedure
Step 1 Click in the upper right corner of the NCE window.
----End
7.1.3.4 Navigating to Common Views

This section describes how to navigate to the main interfaces of the NCE and the
functions of these interfaces.
7.1.3.4.1 Navigating to the Main Topology

On the NCE, you can manage the network topology in the main topology view.
Prerequisites

NCE
NOTE
Procedure
Step 1 In the NCE window, click Network Management.
The main topology view is displayed.
Step 2 Optional: Click on the left in the main topology view.

The subnet and NE information in the current network topology is displayed on

the left in the main topology view.
----End
7.1.3.4.2 Navigating to the NE Explorer

The NE Explorer provides the main GUI for device management on the NCE. In the
NE Explorer view, there is the function tree, object tree, and configuration pane.
Prerequisites

NCE
Procedure
Step 1 Optional: On the Physical Topology page, double-click the subnet where the
target NE is located. In the topology view, select the NE icon.
NOTE
You can also select the target NE using either of the following methods:
● Click on the left in the main topology view and select the target NE from the
displayed subnet and NE information. An NE information drop-down list is displayed on
the right.
● In the search box in the upper right corner of the main topology view, enter the key
information about the target NE and click the target NE in the search result list.
Step 2 Click Show information panel in the search box in the upper right corner. Select
NE Explorer from the drop-down list.

The NE Explorer view is displayed.
----End
7.1.3.4.3 Navigating to the NE Panel

NE Panel displays the boards configured on the NE. Different colors of the boards
represent different board states.
Prerequisites

NCE
NOTE
Procedure
Step 1 Optional: In Main Topology, double-click the subnet to which the NE belongs.
Step 2 Double-click the icon of the desired NE in Main Topology.In NE List, double-click
the NE to which you are logged in.
NE Panel is displayed.
NOTE
● To quickly navigate to the NE Explorer view, click .
● To quickly synchronize the NE time, click .
----End
7.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 7-1 shows the configuration flowchart.

Figure 7-1 Flowchart for initial configuration
The steps in the configuration flowchart are described in Table 7-2.
Table 7-2 Initial configuration
Operation Remarks
7.4 Configuring the Network Required.

Topology
7.5 Configuring Microwave Required.

Links
7.6 Configuring Ethernet Required.

Services
7.7 Configuring Clocks Required.
NOTE
The configuration sequence provided in Table 7-2 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 7.3 Common Network Scenarios of Configuration
Examples.
To prevent service interruption, first configure the clock and then configure services when
configuring MIMO links on the RTN 320.

7.3 Common Network Scenarios of Configuration

Examples
This section provides the initial configuration examples which are based on six
network scenarios and cover all operations in the general configuration process.
7.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 7-3 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
Transmi Scenari ssion
ssion o Scenari
Scenari o
o
Configure the √ - - - - -
network
topology
Configure √ - √ √ √ √
microwave links
Confi Transpa - - √ - - -
gure rently
Nativ transmit
e ted
Ether point-
net to-point
servi E-Line
ces service
VLAN- √ - - - - -
based
E-Line
service

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
Transmi Scenari ssion
ssion o Scenari
Scenari o
o
IEEE - √ - - - -
802.1D
bridge-
based
E-LAN
service
IEEE √ - - - - -
802.1Q
bridge-
based
E-LAN
service
Confi Clock √ - - - - -
gure on a
the microw
clock ave
chain
network
Clock - √ - - - -
on a
microw
ave ring
network
7.3.2 Microwave Chain Network

A microwave chain network consists of three sites and three OptiX RTN 320/320Fs.
Figure 7-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 7-2 Networking diagram for a microwave chain network
7.3.3 Microwave Ring Network

This section describes a microwave ring network consisting of four OptiX RTN
320/320F devices located at four sites.
Figure 7-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 7-3 Networking diagram for a microwave ring network
7.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 7-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 7-4 PTP large capacity microwave transmission network topology

7.3.5 Microwave 1+1 Protection Scenario

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

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

RTN 320 networking scenario
RTN 320F networking scenario

NOTE
Connections in the XPIC with 1+1 protection scenario are the same as those in the cascade EPLA
scenario.
Figure 7-7 4 x 4 MIMO scenario
NOTE
The RTN 320F does not support MIMO.
7.4 Configuring the Network Topology

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

Before configuring the network topology, familiarize yourself with the basic
concepts.

7.4.1.1 Introduction to the DCN

The network management system (NMS) communicates with a transmission
network element (NE) through the DCN to manage and maintain the NE.
Composition of the DCN

The DCN contains two types of nodes: NMS and NE. The DCN between the NMS
and NEs is called an external DCN. The DCN among NEs is called an 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 described in this document
refers to the internal DCN.
DCN Channel
DCN channels fall into two types: outband DCN channel and inband DCN channel.
● Outband DCN channels do not occupy any service bandwidth. The RTN 300
supports two types of outband DCN channels:
– D1 to D3 bytes in a microwave frame
– NMS port

● Inband DCN channels occupy partial service bandwidth. The RTN 300
supports two types of inband DCN channels:
– Partial Ethernet service bandwidth of a microwave link
– Partial Ethernet service bandwidth of an Ethernet link
NOTE
When inter-equipment 1+1 HSB or cascading EPLA is configured, inband DCN is used for
communication between two cascaded NEs.
DCN Solutions
The RTN 300 provides two DCN solutions:
● IP DCN solution
In the IP DCN solution, network management messages are encapsulated into
IP packets. NEs forward the packets based on the IP addresses contained in

them. This solution supports a maximum of 200 NEs and ensures high
network stability. This solution is the default and preferred solution.
● 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 packets
based on the MAC addresses contained in the Ethernet frames. This solution
supports a maximum of 120 NEs. However, it has a risk of broadcast packet
flooding and provides low network stability.
The RTN 300 also supports the HWECC solution, which is eliminated gradually.

NE Types on the DCN

There are two types of NEs on the DCN: gateway NE (GNE) and non-gateway NE
(non-GNE).
Gateway NE: The application layer of the NMS directly communicates with the
application layer of the gateway NE. Generally, an NE at the boundary between
the internal DCN and the 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 the non-gateway NE through the application layer of a
gateway NE. The NEs between the gateway NE and the non-gateway NE forward
DCN packets at L2 or L3.

DCN IDs
An NE on the DCN must be configured with two DCN IDs: NE ID and NE IP
address.
The NE ID is used for application layer communication. It 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.
The NE IP address is used for IP communication. By default, the NE IP address and

NE ID 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 10.9.0.1.
When an NE IP address is changed manually, the association relationship between
the NE ID and the NE IP address becomes ineffective.

7.4.1.2 IP DCN
This section describes the basic knowledge about IP DCN.
Application of the IP DCN Solution

IP DCN is a DCN solution provided by Huawei. In this solution, network
management messages are encapsulated in the standard IP protocol stack and
transmitted over DCN channels between NEs so that the network management
system (NMS) can manage these NEs. IP DCN is a preferred solution when a
network consists of only the RTN 300 or of the RTN 300 and third-party
equipment that supports 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.
● 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 is used for transmitting
DCN data.
– DCC channel: Three self-defined DCC bytes in a microwave frame are
used for transmitting DCN data at a microwave port.
– Inband DCN channel: A part of Ethernet service bandwidth is used as the
DCN channel at the Ethernet or microwave port.
● Layer 2 is the data link layer, which provides reliable data transmission to the
physical link layer. DCC and inband DCN channels 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.
● Layer 3 is the network layer, which implements 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.
● 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 transferred as follows:

1. The NMS forwards the application layer packets to the gateway NE through
the TCP connection between the NMS and the gateway NE.
2. The gateway NE extracts packets from the TCP/IP protocol stack and reports
the packets to the application layer.
3. If the ID of the destination NE is not that of the local NE, the gateway NE
queries the core routing table of the application layer to obtain the
corresponding route 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. After receiving the packet that encapsulates the message, the network layer
of the transit NE queries the destination IP address of the packet. If the IP
address is not the IP address of the local NE, the transit NE queries the IP
routing table according to the destination IP address to obtain the
corresponding route and then transfers the packet.
5. After receiving the packet, the network layer of the destination NE reports the
packet to the application layer through the transport layer because the
destination IP address of the packet is the IP address of the local NE. The
application layer processes the packets sent from the NMS.
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 often connects to a third-party L2 network. In
this case, IP DCN packets have to traverse the L2 network based on the access
control function at the Ethernet service port.
A third-party L2 network may be located between the NMS and a network
consisting of RTN 300s or between two networks consisting of RTN 300s.
When the third-party L2 network is located between the NMS and the network
consisting of RTN 300s, the L2 network transmits Ethernet services and DCN
packets between the NMS and the gateway NE. In this case, 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 service port of the gateway NE. After
the access control function is enabled:
● The Ethernet port functions as an Ethernet NMS port on the gateway NE.
● The IP address of the Ethernet port must be in the same network segment as
that of the NMS but in a different network segment from that of the NE.
● 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 consisting of

RTN 300s, NMS messages are encapsulated as L2 services for transmission. In this
case, 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 an additional L2VPN service for the DCN
packets carrying inband DCN VLAN.
7.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 NCE. You can also use the NCE to manage
fibers and cables, including Ethernet fibers/cables, microwave links.
● Ethernet fibers/cables
Ethernet fibers/cables refer to the Ethernet fiber/cable connections between
Ethernet optical/electrical ports on different sets of equipment.

● 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 NCE. Therefore, operations on the fibers or
cables do not affect the normal running of the NEs.
7.4.1.4 Logical Boards

Introduction to the Logical Boards of OptiX RTN 320/320F.
● An integrated RTN 320 has two logical boards: DMC5 and ODU. The slot IDs
for the two logical boards are 1 and 51, respectively.
● A split RTN 320 has three logical boards: DMC4 and two ODUs. The slot IDs
for the three logical boards are 1, 51, and 52, respectively.
● The RTN 320F OAU 2F has three logical boards: one DMD4 and two ODUs,
which are inserted in slots 1, 51, and 52 respectively.
NOTE
For a split 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 RTN
320 on the NCE by querying the subrack type of the NE.
7.4.2 Configuration Process (Network Topology)

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

Figure 7-8 Flowchart for configuring the network topology
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 7-4 Process of creating NEs
Step Operation Remarks
1 Creating NEs Creating an It is recommended that you perform

on the NCE NE by Using this operation to add one or more NEs
the Search to a large existing network on the
Method(Web NCE.
LCT)
Creating an It is recommended that you perform

NE this operation to create NEs on the
Manually(We NCE in other cases.
bLCT)

Configuring NE Attributes
Table 7-5 Process of configuring NE attributes
1 7.8.1.7 Required.
Changing NE
IDs
2 7.8.1.8 Optional.
Changing
the NE
Name
Configuring DCN
Table 7-6 Process of configuring DCN
1 7.8.1.9 Setting the Required.

VLAN ID and If the VLAN ID and bandwidth planned for
Bandwidth for an this inband DCN do not assume their
Inband DCN default values (the default VLAN ID is
4094 and the default bandwidth is 1024
kbit/s).
2 7.8.1.10 Optional.
Configuring Access By default, access control is enabled for
Control Ethernet interfaces. Perform this step if you
want to modify the IP address or disable
the function.
Creating Fibers/Cables
Table 7-7 Process of creating fibers/cables
1 Creating 7.8.1.11 It is recommended that you perform this

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

7.8.1.12 It is recommended that you perform this

Creating operation to create fibers/cables that cannot
a Fiber/ be created using the search method (for
Cable example, when the fiber/cable has not been
Manuall connected).
y
7.4.3 Configuration Example (Network Topology)

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

This section describes the networking of NEs.
Figure 7-9 shows a microwave chain network configured according to the
● A microwave chain network consists of two sites and three OptiX RTN
320/320Fs, which are managed by the NCE.
● 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 NCEs using the access control function.
● 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
● For the RTN 320F:

● On the NMS, the logical port of an IF1 port is 1-DMD4-1(IF1).
● On the NMS, the logical port of a GE1 port is 1-DMD4-3(GE1).
● On the NMS, the logical port of a 10GE1 port is 1-DMD4-5(10GE1).
● On the NMS, the logical port of a 10GE2 optical port is 1-DMD4-6(10GE2).
● For the integrated RTN 320:
● On the NMS, the logical port of an IF1 port is 1-DMC5-1(IF1).
● On the NMS, the logical port of a GE1(e) electrical port is 1-DMC5-3(GE1(e)).
● On the NMS, the logical port of an NMS/GE2(e) electrical port is 1-DMC5-4(NMS/
GE2(e)).
● On the NMS, the logical port of a GE3(o) optical port is 1-DMC5-5(GE3(o)).
● On the NMS, the logical port of a COMBO port is 1-DMC5-6(COMBO).
● On the NMS, the logical port of a P&E port is 1-DMC5-7(P&E).
● For the split RTN 320:
GE2(e)).
7.4.3.2 Configuration Procedure

This section describes the procedure for configuring a microwave chain network.
Data Preparation
Item Value in This Example Planning Principle
DCN ● Use the IP DCN ● The default IP DCN

solution. solution is
● Change the VLAN IDs recommended.
of all inband DCN ● The VLAN ID of
channels to 4094 inband DCN channels
(default) and the must be different
bandwidth to 512 from service VLAN
kbit/s (default). IDs.

NE ID and NE IP address See the following figure. ● Each NE must have a

unique NE ID and IP
address.
● 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.
Gateway NE NE1 -
Access Control Access control is enabled If access control is

on the GE port (IP enabled on the Ethernet
address: 10.0.0.1) of NE1. port of the gateway NE,
Access control is enabled ensure that the IP
for other interfaces by address of this Ethernet
default and the setting is port is in the same
not modified. network segment as the
IP address of the NMS
but in a different
network segment from
the IP address of the
gateway NE.

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

7.5 Configuring Microwave Links

Before configuring services on a microwave link, you need to configure the
microwave link.
7.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 7-11 shows the flowchart for configuring microwave links.
Figure 7-11 Flowchart for configuring microwave links
NOTE
The preceding flowcharts provide basic processes of configuring microwave links.
Table 7-8 Process of configuring microwave links with 1+1 HSB\FD\SD protection
Operation Remarks
7.8.3.28 Releasing the QoS Policy Required.

Bound to an Interface
7.8.2.1 Creating a Microwave 1+1 Required.

Protection Group

Operation Remarks
7.8.2.2 Managing a Hop of Required.

Microwave Link
7.8.1.11 Creating a Fiber/Cable by In normal cases, Main Topology

Using the Search Method displays the previously created
microwave links.
Table 7-9 Process of configuring microwave links with 1+0 or XPIC protection
Operation Remarks

Microwave Link

microwave links.
Table 7-10 Process of configuring XPIC links with PLA or intra-equipment EPLA
Operation Remarks


Microwave Link
7.8.2.4 Creating a PLA\EPLA Group Required.

microwave links.
Configuring Microwave Links on Cascaded NEs

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

Figure 7-12 Flowchart for configuring microwave links
NOTE
The preceding flowcharts provide basic processes of configuring microwave links.
Table 7-11 Process of configuring XPIC links with 1+1 HSB protection
Operation Remarks
Releasing the QoS Policy Bound Required.

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

Microwave Link configured with a microwave link.
7.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
7.8.2.3 Synchronizing Data Configuration data is synchronized

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

by Using the Search Method the previously created microwave links.
Table 7-12 Process of configuring microwave links in a cascade EPLA group

Operation Remarks
Releasing the QoS Policy bound Required.

to a slave IF port
Creating a 7.8.3.1 Creating a Required. Ensure that the EPLA cascade

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

PLA\EPLA Group

Microwave Link
7.8.1.11 Creating a Fiber/Cable In normal cases, Main Topology displays

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

NOTE
Figure 7-13 shows the procedure for configuring microwave links.

Figure 7-13 Procedure for configuring microwave links
Table 7-13 Procedure for configuring 4 x 4 MIMO microwave links

Operation Remarks


Microwave Link

microwave links.

7.5.2 Configuration Example (Microwave Links on a Chain

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

Configure the microwave links on the chain network according to the following
requirements:
● Enable AM for all microwave links, because they carry Ethernet services.
● Table 7-14 provides the requirements on the services from NodeB 1 and RAN
1.
Table 7-14 Capacity of services from NodeB 1 and RAN 1

Service Capacity NodeB 1 RAN 1
Capacity of high- 40 100

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

Ethernet services
(Mbit/s)
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 7-15.
Table 7-15 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 7-14 Networking diagram for microwave links on a chain network

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

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

NOTE
The name of the RTN 320F on the NCE is displayed as RTN 320. The following uses the
DMD4 as an example to describe the configuration procedure. The procedure for
configuring the RTN 320 is similar to that for configuring the RTN 320F.
----End
7.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.

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

Table 7-16 Capacity of services from RAN 1 and RAN 2

Service Capacity RAN 1 RAN 2

priority Ethernet
services (Mbit/s)

Ethernet services
(Mbit/s)
NOTE



services

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

NOTE

GE2(e)).
GE2(e)).

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

Data Preparation
Figure 7-17 Data Planning
Table 7-18 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 7.8.3.28 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 following figure by configuring NE1.
NOTE
The RTN 320F is displayed as the RTN 320 on the NMS. The RTN 320 using DMC4 boards is
used as an example to describe how to configure the RTN 320. The procedure for configuring
the RTN 320F is the same as that for configuring the RTN 320.
----End
7.5.4 Configuration Example ( XPIC Microwave links with PLA

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

As shown in Figure 7-18, configure the microwave links according to the following
requirements.
● 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.
● 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 7-18 Networking of XPIC links with PLA protection
NOTE

GE2(e)).
GE2(e)).

This section describes the procedure for configuration.

Data Preparation
NOTE
Procedure
QoS Policy bound to the slave interface.
Step 2 Configure a hop of microwave link.
NOTE
take NE1 for example:

Step 3 Create a PLA protection group.

NOTE
take NE1 for example:
----End
7.5.5 Configuration Example (XPIC Links with 1+1 Protection)

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


Figure 7-20 shows a hop of important microwave link. Two OptiX RTN 320/320F
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.
RAN 2.


priority Ethernet
services (Mbit/s)

Ethernet services
(Mbit/s)
NOTE



services

Figure 7-20 Network topology of XPIC links with 1+1 protection

RTN 320 networking diagram

RTN 320F networking diagram

NOTE

GE2(e)).
GE2(e)).

Data Preparation

Parameters for configuring the RTN 320

Parameters for configuring the RTN 320F
Table 7-21 LAG plan

Item Value in This Planning Principle
Example
Static (default Configure the same aggregation type at both ends. Static
LAG type value) aggregation is recommended.
Load sharing Non-Sharing Configure the same load sharing mode at both ends.
mode (default value) Configure a load non-sharing LAG to provide protection.
System priority 32768 (default The default value is recommended. The system priority
value) can be set only in static aggregation.


Example
Master ports ● LAG1: GE1 It is recommended that you set the main ports
● LAG2: GE2 consistently for the equipment at both ends.
Table 7-22 1+1 HSB plan

Example
Service Protection LAG (default -

Type value)
Revertive Mode Revertive Mode In 1+1 HSB protection, you can initiate configuration
(default value) 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 Enabled (default -

Switching value)
IF Port IF1 and IF2 -
Service Port GE1 and GE2 -
cascade Port ● RTN 320: -

Combo
● RTN 320F:
10GE1
NOTE
Procedure
QoS Policy bound to the standby IF interface.
Step 2 Manage a hop of microwave link.
NOTE
The following procedure configures basic information for the hop of microwave link shown
in the following figure by configuring NE1.

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
7.5.6 Configuration Example (Cascade EPLA)

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

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

RAN 2.



priority Ethernet
services (Mbit/s)

Ethernet services
(Mbit/s)
NOTE



services

Figure 7-22 Network topology of a cascade EPLA group with XPIC enabled
RTN 320 networking diagram
RTN 320F networking diagram


Data Preparation

Parameters for configuring the RTN 320

Parameters for configuring the RTN 320F

NOTE
Procedure
QoS Policy bound to the slave interface.
Step 3 Create a cascading EPLA group.

For the master NE, take NE1 for example:
NOTE
The master and slave NEs are cascaded through 2.5GE optical ports for the RTN 320.
The master and slave NEs are cascaded through GE/2.5GE/10GE optical ports for the RTN
320F.

For the slave NE, take NE2 for example:
NOTE
Service ports on the master and slave NEs selected for a PLA group must have the same.
The selected cascade ports on the master and slave NEs must have the same name.
----End
7.5.7 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.
NOTE


Figure 7-24 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 7-24 4 x 4 MIMO networking

This section describes the procedure for configuring a microwave chain network.
Prerequisites
● The basic data of NEs on the entire network has been configured.
Data Preparation
Figure 7-25 4x4 MIMO link configuration parameters

Procedure
Step 1 Configure 4 x 4 MIMO microwave links.
----End
7.6 Configuring Ethernet Services

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

The split RTN 320 provides four GE ports. The integrated RTN 320 provides five GE
ports. The RTN 320F provides two GE ports and two 10GE ports.
Figure 7-26 shows the physical Ethernet ports on the OptiX RTN 320/320F. Table
7-25 and Table 7-26 provides the logical ports and functions of physical Ethernet
ports.
Figure 7-26 Port diagram

Port diagram of the RTN 320

Port diagram of the RTN 320F
Table 7-25 Description of Ethernet ports on the RTN 320

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

RTN
320/320F:
1-DMC4-3,
(GE1
electrical)
● Integrated
OptiX RTN
320/320F:
1-DMC5-3
(GE1
electrical)
NMS/ ● Split OptiX An NMS port or a GE electrical port

GE2(e) RTN
320/320F:
1-DMC4-4
(NMS/GE2
electrical)
● Integrated
OptiX RTN
320/320F:
1-DMC5-4
(NMS/GE2
electrical)


Port
GE3(o) ● Split OptiX A GE optical port (SFP module)

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

RTN
320/320F:
1-DMC4-6
(COMBO)
● Integrated
OptiX RTN
320/320F:
1-DMC5-6
(COMBO)
P&E Integrated The P&E port on an integrated OptiX RTN 320/320F can function
OptiX RTN as a GE electrical port.
320/320F: 1-
DMC5-7 (P&E)
Table 7-26 Description of Ethernet ports on the RTN 320F

Port
GE1 1-DMD4-3(GE1) A GE electrical port
GE2 1-DMD4-4(GE2) A GE electrical port
10GE1 1-DMD4-5(10GE1) A 10GE optical port (SFP module)
10GE2 1-DMD4-6(10GE2) A 10GE optical port (SFP module)
NOTE
● The split RTN 320 provides two IF ports, which correspond to two logical ports: 1-DMC4-1
(IF1) and 1-DMC4-2 (IF2).
● The integrated RTN 320 provides two IF ports, which correspond to two logical ports: 1-
DMC5-1 (IF1) and 1-DMC5-2 (IF2).

7.6.2 Ethernet Service Types

Native Ethernet services are classified into six types.
7.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 7-27 describes the transparently transmitted point-to-point E-Line service
model.
Table 7-27 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.
Model 2 PORT (source) UNI-UNI 802.1Q/QINQ The source port

NOTE PORT (sink) (source) processes the
In service model 802.1Q/QINQ incoming
2, ports process
(sink) Ethernet frames
Ethernet frames based on their
based on their Tag
TAG attribute or
attribute or QinQ-
class domain. QinQ-class
Therefore, service domain, and then
model 2 is not a sends the
real transparent processed
transmission Ethernet frames
model and is not
to the sink port.
recommended.
The sink port
processes the
Ethernet frames
based on its TAG
attribute, and
then exports the
processed
Ethernet frames.

Typical Application
Figure 7-27 shows the typical application of transparently transmitted point-to-
point E-Line service model.
Figure 7-27 Typical application of Transparently transmitted point-to-point E-Line

service model
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.
7.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 7-28 provides information about the VLAN-based E-Line service model.

Table 7-28 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- (source) processes
PORT+VLAN to-network IEEE 802.1Q incoming
(sink) interface.) (sink) Ethernet frames
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 7-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).
● Services 1, 2, 3, and 4 carry different VLAN IDs.
● 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.
● 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.
● 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.
● 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 7-28 VLAN-based E-Line service model
7.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 7-29 shows the QinQ-based E-Line service models.
Table 7-29 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
QinQ link (sink) QinQ (sink) S-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

QinQ link (sink) QinQ (sink) processes 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

list (source) QinQ (sink) processes Ethernet
QinQ link (sink) frames according 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 PORT+S-VLAN UNI-UNI QinQ (source) The source port

4(1) list (source) QinQ (sink) transmits the Ethernet
PORT+S-VLAN frames that carry a
list (sink) specific S-VLAN tag
(corresponding to the
source QinQ) to the sink
port to which the sink
QinQ is connected.
Model QinQ link NNI-NNI QinQ (source) The source port

4(2) (source) QinQ (sink) transmits the Ethernet
QinQ link (sink) frames that 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 7-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 7-29 Typical application of service model 1

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.


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.

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.

7.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 7-30 shows the IEEE 802.1D bridge-based E-LAN service model.
Table 7-30 IEEE 802.1D bridge-based E-LAN service model
Service Type Tag Type Encapsulatio Logical Port Learning Switching

n Type at a Type Mode Sub-domain
Port
IEEE 802.1D Tag- Null PORT SVL None

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

Service Type Tag Type Encapsulatio Logical Port Learning Switching
n Type at a Type Mode Sub-domain
Port
IEEE 802.1Q C-Aware IEEE 802.1Q PORT+VLAN Independent A bridge

bridge-based VLAN learning divided into
E-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 7-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).
● Services 1 and 2 have the same VLAN ID of 100, and services 3 and 4 have
the same VLAN ID of 200.
● 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 7-34 IEEE 802.1Q bridge-based E-LAN service model
7.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 7-32 shows the 802.1ad bridge-based E-LAN service model.
Table 7-32 802.1ad bridge-based E-LAN service model

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

bridge-based divided into port) 802.1Q
E-LAN service sub-switching
domains PORT+C- 802.1Q
based on S- VLAN list
VLAN 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 7-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 7-35 Typical application of the 802.1ad bridge-based E-LAN service model
NOTE
You can also configure 7.6.2.3 QinQ-Based E-Line Services on NE2 and NE3 for service
access.
7.6.3 Configuration Process

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

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

Line services
Configuring LAGs
Table 7-33 Process of configuring LAGs

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

Configuring Transparently Transmitted Point-to-Point E-Line Services
Table 7-34 Process of configuring transparently transmitted point-to-point E-Line

services
Operation Remarks

Point-to-Point
Transparently
Transmitted E-Line
Service
Configuring QoS
Table 7-35 Process of configuring QoS

Operation Remarks
7.8.3.12 Modifying the Required if the default mappings for the

Mapping Relationship Differentiated Services (DS) domain are inapplicable.
of the DiffServ Domain
7.8.3.13 Modifying the Required when the default weighted round robin
Ports Applied to a (WRR) policies do not meet the requirements.
DiffServ Domain and
Packet Types Trusted by
Ports
7.8.3.16 Creating a Required if the priority type of an Ethernet service is

WRR Policy not CVLAN, which is the default packet type trusted
by the DiffServ domain.
7.8.3.18 Modifying the Required when the queues at a port need to be

Port Policy configured with the scheduling algorithm, queue
shaping, and drop algorithm.
7.8.3.20 Creating Traffic Required when a flow at a port requires access

control list (ACL), class of service (CoS), committed
access rate (CAR), or shaping operations.
7.8.3.21 Setting the Required when you need to apply created port
Port That Uses the Port policies to ports.
Policy

Verifying Ethernet Service Configurations
Table 7-36 Process of verifying Ethernet service configurations

Operation Remarks
Testing Ethernet Services The connectivity of Ethernet services is

Configured on a Per NE Basis verified using an Ethernet OAM test.
Synchronizing 1+1 Configurations
Table 7-37 Process of synchronizing 1+1 configurations

Operation Remarks
7.8.2.3 Synchronizing Optional. When links in a cascade 1+1 protection

Data Between Main group carry Ethernet services, perform this operation
and Standby NEs (1+1) to synchronize service configurations on the active
NE to the standby NE.
7.6.3.2 Per-NE Configuration Process (VLAN-based E-Line Services)

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

Configuring LAGs
Table 7-38 Process of configuring LAGs

Operation Remarks
Configuring VLAN-based E-Line Services
Table 7-39 Process of configuring VLAN-based E-Line services

Operation Remarks

VLAN-based E-Line
Service

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

Services Configured on an Ethernet OAM test.
a Per NE Basis

Operation Remarks

7.6.3.3 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN

Services)
quality of service (QoS) information for an IEEE 802.1D bridge-based Ethernet

local area network (E-LAN) service and the process of verifying the service
configurations.
Flowchart
Figure 7-38 shows the flowchart for configuring IEEE 802.1D bridge-based E-LAN
services.
Figure 7-38 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services
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 7-42 Process of configuring ethernet protection
Operation Remarks
7.8.3.2 Creating an Required.

ERPS Instance

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

Operation Remarks
7.8.3.6 Creating an IEEE Required.

802.1D Bridge-based E-
LAN Service

Operation Remarks

a Per NE Basis

Operation Remarks

7.6.3.4 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN

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

Figure 7-39 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services
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 7-46 Process of configuring ethernet protection

Operation Remarks
7.8.3.2 Creating an Required.

ERPS Instance

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

Operation Remarks
7.8.3.7 Creating an IEEE Required.

802.1Q Bridge-based E-
LAN Service

Operation Remarks

a Per NE Basis

Operation Remarks

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

As Figure 7-40 illustrates, NE1 is a terminal station of a backhaul network. The
service requirements are as follows:
● NE2 must transparently transmit the Ethernet services from the NodeB to NE1
in point-to-point manner.

● 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 7-40 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.
7.6.4.2 Procedure of Configuration on a Per-NE Basis (Service Information)

This section describes the procedure for configuring service information.
Data Preparation
Procedure
Step 1 Create a Point-to-Point Transparently Transmitted E-Line Service.

NOTE
For point-to-point transparently transmitted services, parameter "L2 Protocol Control" takes
the fixed value Not Transparent.
For an E-Line service transparently transmitting LACP packets from other equipment, set
parameter "L2 Protocol Control" to LACP Packet Transparent.
For an E-Line service transparently transmitting BPDU packets from other equipment, set
parameter "L2 Protocol Control" to BPDU Packet Transparent.
----End
7.6.4.3 Per-NE Configuration Process (Configuring QoS)

This section describes the process of configuring QoS on a per-NE basis.
Data Preparation
Mapping between DSCP See the following figure. ● DiffServ configuration

values, PHBs, and queue should be the same
scheduling modes for each service port.
● 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 ports that use a DS domain and their trusted packet types.
Delete a port that uses the DS domain.

Add a port that uses the DS domain.
Modify the packet type trusted by the port.

Step 3 Create a WRR policy.
Step 4 Create a port policy.
Step 5 Create traffic.
Step 6 Set the port that uses the port policy.

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

Verification)
This section describes the procedure for verifying Ethernet service configurations.
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.




bandwidth.

----End
7.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 7.3.2 Microwave Chain Network and
the following requirements.
Table 7-50 Service requirements

Requirement Description Requirement Satisfaction
Servi Configure a port working in NE 2 and NE 3 provide an electrical P&E

ce auto-negotiation mode for port for receiving services.
acces receiving a channel of
s electrical GE signals from
capac NodeB 1.
ity
Servi No -
ce
prote
ction
Servi Separate services from Configure VLAN-based E-Line services on

ce NodeB 1 and RAN 1 from NE1, NE2, and NE3.
separ each other using VLAN IDs:
ation ● VLAN ID of NodeB 1:
100
● 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 7-41 Networking diagram for VLAN-based E-Line services


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


Data Preparation

trusted by service
ports is DSCP,
enabling DSCP
demapping function
DS domain is not
demapping function
may change DSCP
values.
Procedure



----End

Verification)
Data Preparation
NOTE
Procedure


Step 5 LB test.




bandwidth.

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

Configure Ethernet services according to 7.3.3 Microwave Ring Network and the
following requirements.

Servi Backhaul one GE electrical ● Configure IEEE 802.1D bridge-based

ce signal from NodeB 1 and Ethernet local area network (E-LAN)
acces NodeB 2 separately. The services.
s port mode is auto- ● Configure Ethernet ring protection
capac negotiation. switching (ERPS).
ity
Servi Configure protection for

ce Ethernet services on ring
prote networks.
ction
Servi Transparently transmit

ce Ethernet services from
separ NodeB 1 and NodeB 2.
ation
Quali The priorities of Ethernet Configure DiffServ and perform service

ty of services transmitted over a scheduling and forwarding based on DSCP
servic microwave network are values.
e identified by DSCP values.
(QoS All the NEs on the
) microwave network have
the same mapping

Figure 7-42 Networking diagram for IEEE 802.1D bridge-based E-LAN services
7.6.6.2 Per-NE Configuration Procedure (Ethernet Protection)

This section describes the procedure for configuring Ethernet protection.

Data Preparation
Procedure
Step 1 Configuration ethernet protection.
----End
7.6.6.3 Per-NE Configuration Procedure (Service Information)


Data Preparation
Procedure
Step 1 Creating an IEEE 802.1d Bridge-based E-LAN Service.
Configure Ethernet interfaces and microwave interfaces.

Configure E-LAN services.
----End


Data Preparation
Procedure

Delete a port that uses the DS domain.
Add a port that uses the DS domain.
Modify the packet type trusted by the port.


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

Data Preparation
NOTE
Procedure


Step 5 LB test.




bandwidth.

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

The section describes the networking of NEs.
Configure Ethernet services according to 7.3.2 Microwave Chain Network and
the following requirements.

Servi Configure a port working in The NE2 and NE3 provides an electrical
ce auto-negotiation mode for P&E port for receiving services.
acces receiving a channel of
s electrical GE signals from
capac NodeB 1.
ity Configure a port working in
auto-negotiation mode for
receiving a channel of
electrical GE signals from
RAN 1.
Servi No -
ce
prote
ction
Servi Separate services from Configure IEEE 802.1Q bridge-based E-

ce NodeB 1 and RAN 1 from LAN services for NE1, NE2, and NE3.
separ each other using VLAN IDs:
ation ● VLAN ID of NodeB 1:
100
● 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
Figure 7-43 Networking diagram for IEEE 802.1q bridge-based E-LAN services


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

Configure microwave interfaces.

Configure E-LAN services.

----End

Data Preparation

trusted by service
ports is DSCP,
enabling DSCP
demapping function
DS domain is not
demapping function
may change DSCP
values.

Procedure



----End

Verification)
Data Preparation
NOTE
Procedure


Step 5 LB test.




bandwidth.

----End
7.7 Configuring Clocks

7.7.1 Configuration Process (Configuring a Clock)

This section describes the process of configuring the clock source, clock protection,
and output clock.
Figure 7-44 shows the flowchart for configuring a clock.
Figure 7-44 Flowchart for configuring a clock

Table 7-53 Process of configuring the clock
1 7.8.4.1 Configuring the Required. Set parameters as follows:

System Clock Source Set Clock Source according to clock
source planning information.
2 7.8.4.2 Configuring Required when the SSM or extended

Protection for Clock SSM protection is used. Set
Sources parameters as follows:
● Set Protection Status according to
the used protocol type.
● 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 7.8.4.3 Configuring a Optional.

Clock Source Group
4 5.6 Checking the Clock Optional.

Status
7.7.2 Configuration Example (Clock on a Microwave Chain

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

Configure the clock for the network shown in Figure 7-45 according to 7.5.2
Configuration Example (Microwave Links on a Chain Network) and the

● Synchronize the microwave chain network with the clock of the RNC.
● Provide clock signals to NodeB 1 and RAN 1 through GE1 ports.

This section describes the procedure for configuring clock on a microwave chain
network.
Data Preparation
Item Value in This Example Planning Principles
Clock See the following figure. You need to configure an

source Ethernet clock source for each
informati link.
on
Clock Not in use. In this example, a chain network

protectio is set up. Therefore, only priority-
n 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
7.7.3 Configuration Example (Clock on a Microwave Ring

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

Configure clocks according to the following requirements. Figure 7-47 shows the
networking diagram.
● The microwave ring network is directly synchronized with the clock of the
radio network controller (RNC).
● Clock synchronization signals are transmitted to each NodeB through the GE1
port.

Figure 7-47 Networking diagram (clocks on a microwave ring network)

This section describes the procedure for configuring clocks.
Data Preparation
Clock See the following figure. -

source
informati
on
Clock Standard SSM In this example, a ring network

protectio is set up. Therefore, the standard
n 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
7.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 7-49 shows the
networking diagram.
● Synchronize an NE cascading network with the clock of the RNC.
● Provide clock signals to NodeB and RAN through GE(e) ports.

Figure 7-49 Networking diagram for an NE cascading transmission network

This section describes the procedure for configuring clock on a microwave chain
network.
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.

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
7.8 Common Service Configuration Operations

This section provides hyperlinks to common service configuration operations.

NOTE
This document describes how to configure the integrated RTN 320, split RTN 320 OAU 2A,
and RTN 320F OAU 2F. The split RTN 320 OAU 2A is used as an example to describe the
configuration process. The configuration process for the integrated RTN 320 is similar to
that for the RTN 320F OAU 2F. If there are differences among the integrated RTN 320, split
RTN 320 OAU 2A, and RTN 320F OAU 2F, they will be described separately.
7.8.1 Configuring the Network Topology

This section provides hyperlinks to common operations of network topology
configuration.
7.8.1.1 Connecting to an NE (Using the USB Port)

Proper USB connection to a mobile phone is a prerequisite for data configuration
from the mobile phone.

A mobile phone with MDT installed.
Procedure
1. Power on the OptiX RTN 380H by referring to 4.1 Powering On the Device.
2. Use a USB cable to connect the USB port on the OptiX RTN 320/320F to the
mobile phone.
3. Configure commissioning data on the mobile phone. For details, see
Microwave Deployment Tools.
7.8.1.2 Creating NEs by Using the Search Method (NCE)

The NCE can find all NEs that communicate with a specific gateway NE by using
the IP address of the gateway NE, the IP address range of the gateway NE, or the
NSAP addresses. In addition, the NCE can create the NEs that are found in
batches. Compared with the method of manually creating NEs, this method is
faster and more reliable.
Prerequisites
● The NMS must have proper communication with NEs.

NCE
Procedure
Step 1 Choose Topology > Discovery > NE from the main menu.
Step 2 Select Transport NE Search tab.

Step 3 Select Search Mode.

NOTE
● If the NCE server and the gateway NE are in the same network segment, it is recommended
that you set Search Mode to IP auto discovery.
● In other scenarios, it is recommended that you set Search Mode to Search for NE.
If... Then...
Search Mode is set to Search for NE Perform Step 4 to Step 7.
Search Mode is set to IP auto discovery Perform Step 8 to Step 10.
Step 4 If Search Mode is set to Search for NE, you need to add a search domain.
1. Click Add, and then the Input Search Domain dialog box is displayed.
2. Select an address type and enter the search address.
NOTE
– When Address Type is set to IP Address of GNE or IP Address Range of GNE, and the
NCE server and gateway NE are not in the same network segment, ensure that the IP
routes of the network segments to which the NCE server and gateway NE belong are
configured on the NCE and related routers.
– The factory default user name is root, and its corresponding password is
Changeme_123. If you have changed the password, log in to the NE using the correct
password.
3. Click OK.

Step 5 Repeat Step 4 to add several search domains.
Step 6 In the Search for NE dialog box, perform the operations described in the Note
part.
NOTE
● If Create NE after search is selected, you need to specify NE User and Password.
● You can select either Create NE after search or Upload after Create or both Create NE
after search and Upload after Create. In this manner, after the NE searching is complete,
the system automatically creates an NE and uploads the NE.
Step 7 Click Next, and then the Transport NE Search dialog box is displayed.
After the search is complete, all the NEs that are found are displayed in the Result
list.
Step 8 If Search Mode is set to IP auto discovery, enter NE User and Password.
NOTE
The factory default user name is root, and its corresponding password is Changeme_123. If
you have changed the password, log in to the NE using the correct password.
Step 9 Click Next to navigate to the search interface.
Step 10 After the NE to be created is displayed in Result, click Stop. In the dialog box that
is displayed, click Yes.
Step 11 Create NEs.

1. Select an NE that is not created from the Result list.
2. Optional: Select the GNE ID of the NE.
3. Click Create.
The Create dialog box is displayed.
4. Specify User Name and Password.
5. Click OK.
The icon of the created NE is displayed in the Main Topology.

Step 12 Optional: Repeat Step 11 to create other NEs that are not created.
----End
7.8.1.3 Creating NEs by Using the Search Method (Web LCT)

The Web LCT can find all NEs that communicate with a specific gateway NE by
using the IP address of the gateway NE, the IP address range of the gateway NE,
or the NSAP addresses. In addition, the Web LCT can create the NEs that are
found in batches. Compared with the method of manually creating NEs, this
method is faster and more reliable.
Prerequisites
● The NMS must have proper communication with NEs.

Web LCT
Procedure
Step 1 Click NE Search in NE List and select a desired search type.
If... Then...
All NEs are directly connected to the NMS server Perform Step 2 to Step 5.
through Ethernet cables
Not all NEs are directly connected to the NMS Perform Step 6 to Step 11.
server through Ethernet cables
Step 2 Select NE Search.

The Search NE dialog box is displayed.
NOTE
The default user name is root, and its corresponding password is Changeme_123.

Step 3 Set Local IP Address based on the network planning information.

NOTE
Local IP Address indicates the IP address of an Ethernet port on the NMS server. There may be
multiple Local IP Address values because an NMS server may have multiple network adapters.
Step 4 Set NE IP Address based on the network planning information.

NOTE
NE IP Address indicates the IP addresses of all NEs (searched out by the system automatically)
that are connected to the NMS server directly through Ethernet cables.
Step 5 Click OK.

NOTE
When NE Search is selected, the system can directly log in to NEs. You do not need to enter
the user name and password.
Step 6 Select Advanced Search.

The Search NE dialog box is displayed.
Step 7 Optional: If you select IP auto discovery, then:

1. Click Search.
2. After the Web LCT finds the NEs to be managed, click End Search.
NOTE
In the IP auto discovery mode, the Web LCT searches for the gateway NE and non-gateway NEs
that are managed by the gateway NE in the network segment where the server resides.
Step 8 Optional: If you select Search NE, then:

1. Click Manage Domain.
The Manage Domain Search dialog box is displayed.
2. Optional: Click Add to add a network segment. Then, set Domain Type and
Domain Address.
3. Optional: Select an existing network segment and click Modify to modify the
network segment.
4. Optional: Select an existing network segment and click Delete to delete the
network segment.
5. Click Search.
6. After the WebLCT finds the NEs, click End Search.
NOTE
During initial configuration, Manage Domain takes the default value of 129.9.255.255.
After the IP address of the gateway NE is changed, the value of Manage Domain also
needs to be changed. The default network segment cannot be modified or deleted.

Step 9 Select the NE that needs to be added and click Add NE.
A dialog box is displayed, indicating that the NE is added successfully.
Step 10 Click OK.
A new NE has been added to the NE list.
Step 11 Click Cancel.
----End
7.8.1.4 Creating NEs by Using the Manual Method (NCE)

You can only create NEs one by one by using the manual method. The manual
method, unlike the search method, does not allow creating NEs in batches.
Prerequisites
● The NMS must have proper communication with the NE to be created.
● If the NE to be created is a non-gateway NE, the gateway NE to which the NE
to be created belongs must be created.

NCE
Procedure
Step 1 In the main topology view, right-click and choose New > NE from the shortcut
menu.
The Create NE dialog box is displayed.
Step 2 Choose RTN Series from the object tree and select a product name.
Step 3 Enter the following information: ID, Extended ID, Name, and Remarks.
Step 4 Set Gateway Type for the NE.
If... Then...
The Gateway Type parameter is set to Proceed to the next step.

Gateway
The Gateway Type parameter is set to Select the gateway to which the NE
Non-Gateway belongs, and go to Step 6.
Step 5 Specify the protocol and IP address that the NE uses.

Protocol parameter is set to IP. Enter the IP Address of the NE.
NOTE
Security SSL is recommended for communication.
Step 6 Specify NE User and Password.
The default user name is root and the default password is Changeme_123.
Step 7 Click OK.
Step 8 Click the Main Topology.

The icon of the NE is displayed at the cursor position.
----End
7.8.1.5 Creating NEs by Using the Manual Method (Web LCT)

You can only create NEs one by one by using the manual method. The manual
method, unlike the search method, does not allow creating NEs in batches.
Prerequisites
● If the NE to be created is a non-gateway NE, the gateway NE to which the NE
to be created belongs must be created.


Web LCT
Procedure
Step 1 In NE List, click Add NE. Then, select Europe.
Step 2 Set the NE parameters.
NOTE
Set the parameters according to the network plan.

● The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.
● ID indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique
on the networks that are managed by the same NMS.
● Do not change the Extended ID when the number of actual NEs does not exceed the range
permitted by the basic NE ID.
● The default user name is root, and its corresponding password is Changeme_123.
NOTE
● SSL is recommended for communication with NEs. Set the port number to 5432 and perform
the following steps to replace the SSL certificate:
1. a. Delete the WebLCT\conf\certificate directory on the Web LCT.
2. Copy the opt/oss/NCE/etc/ssl/nemanager/default directory on the NCE 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.
3. c. Restart the Web LCT.
● Install the SSL certificate to the NE using the NCE. For details, see the Security Configuration
Maintenance & Hardening.
Step 3 Click OK.

A new NE is already added to the NE list.
----End
7.8.1.6 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
● Before deleting the logical interface, delete services on the interface and the
QoS policy bound to the interface. 7.8.3.28 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 Configuring logical interfaces.

----End

7.8.1.7 Changing NE IDs

This section describes how to change NE IDs based on the engineering plan to
ensure that NE IDs are unique. The change does not affect services.
Prerequisites

NCE
NOTE
The Web LCT also supports this operation and the steps are the same as those on the NCE.
Context
The following procedure changes NE IDs to the planned values listed in the
following table.
Parameter Value
New ID 1
New Extended ID 9
After changing NE IDs, you need to log in to the NE again.
Procedure
Step 1 Change NE IDs.
----End

7.8.1.8 Changing the NE Name

To better identify an NE in the main topology, name the NE according to the
geographical location of the NE or the equipment connected to the NE.
Prerequisites

NCE
NOTE
Context
following table.
Parameter Value
Name NE1
Procedure
Step 1 Change the NE name.
----End
7.8.1.9 Setting the VLAN ID and Bandwidth for an Inband DCN

The VLAN ID used by the inband DCN must be different from the VLAN ID used
by services. The bandwidth used by the inband DCN must meet the requirement
for transmitting network management messages.

Prerequisites

NCE
NOTE
Context
The following procedure sets the VLAN ID and bandwidth for an inband DCN to
the planned values listed in the following table.
Parameter Value
Ethernet Board VLAN ID 4094
Bandwidth (kbit/s) 512
Procedure
Step 1 Set the VLAN ID and bandwidth for an inband DCN.
----End
7.8.1.10 Configuring Access Control

In the event of access to the NMS through an Ethernet service port, you need to
configure access control.
Prerequisites


NCE
NOTE
Precautions
NOTE
● The default IP address of the access control port cannot be used to access a public network
(such as the Internet).
● The default IP address is temporary and is only for auto deployment of the management
DCN. You need to change the IP address in time.
Context
The following procedure configures the access control function for the port GE1
according to the planned 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 Configure access control.
----End

7.8.1.11 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

NCE
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
7.8.1.12 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

NCE
NOTE
Context
The following procedure creates a fiber manually according to the planned
parameter values listed in the following table.
Parameter Value
Fiber/Cable Type Radio Link
Name l-2
Source NE NE(9-40775)
Source NE Subrack-Slot-Board Type- ● RTN 320: 1-DMC4-1(IF)

Port ● RTN 320F: 1-DMD4-1(IF)
Sink NE NE(9-40776)

Parameter Value
Sink NE Subrack-Slot-Board Type-Port ● RTN 320: 1-DMC4-1(IF)

● RTN 320F: 1-DMD4-1(IF)
Automatically Allocate IP Address No
Procedure
Step 1 Create a fiber/cable manually.
----End
7.8.2 Configuring Microwave Links

This section provides videos to common operations of microwave link
configuration.
7.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
● For 1+1 protection in LAG mode, you must configure E-LAG first.
● The GE ports connected by a cascade port must be configured with the same
port type. For example, both are configured with "COMBO".
NOTE
The RTN 320F uses 10GE ports for cascading.


NCE
NOTE
Context
The following procedure creates a microwave 1+1 protection group according to
planned values provided in the following table.
NOTE
The OAU 2F is used as an example to describe the procedure.

● Create an intra-equipment microwave 1+1 protection group according to
values provided in the following table.
Parameter Value
Reversion Mode Revertive Mode
WTR Time (s) 600 (default value)
Enable Reverse Switching Enable
Working Port IF1
Protection Port IF2
● Create a microwave 1+1 protection group in LAG Mode according to planned

Parameter Value
Service Protection Type LAG Mode
Working/Protection Unit Type Working Unit
IF Port IF1 and IF2
Service Port GE1(e) and GE2(e)
cascade Port 10GE1(o)
● Create a microwave 1+1 protection group in Split Mode according to planned


Parameter Value
Service Protection Type Optical Splitter Mode
Working/Protection Unit Type Working Unit
IF Port IF1
Service Port 10GE1(o) and 10GE2(o)
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
7.8.2.2 Managing a Hop of Microwave Link

This task helps you manage microwave links by hop.

Prerequisites
● The NEs at the two ends of a microwave link hop are communicating
properly.

NCE
NOTE
Background Information
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 28MHz
AM Enabled
Guaranteed AM Capacity QPSK/45Mbit/s
Full AM Capacity 64QAM/147Mbit/s
T/R Spacing(MHz) 644
ATPC Disabled
TX power (dBm) 11
Power to Be Frequency(dBm) -10
TX Status unmute
Procedure

----End
7.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
● The GE ports connected by a cascade port must be configured with the same
port type. For example, both are configured with "COMBO".
● You can initiate configuration synchronization only on a main NE in the
working state.
● If both NEs are in the working or protection state, you cannot initiate
configuration synchronization.

NCE
NOTE
Procedure
Step 1 Synchronize data between main and standby NEs (1+1).

----End
7.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
● No Ethernet service has been configured on the slave NE if a PLA EPLA group
without NE-level protection will be created.
● The cascade ports on the two NEs to be configured as the master and slave
NEs in a PLA EPLA group are configured with no Ethernet service.

NCE
Context
NOTE
The RTN 320 is used as an example to describe the procedure.

● Create a PLA group according to the planned parameter values listed in the
following table.
Parameter Value
Master Port IF2
Slave Port IF2
● 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
Available Service Ports GE1, GE2
Available Adjacent Members COMBO-1, COMBO-2
Procedure
Step 1 Create a PLA group.
Step 2 Create a cascading EPLA group.

For the master NE:
NOTE
● The master and slave NEs are cascaded through 2.5GE optical ports for the RTN 320.
● The master and slave NEs are cascaded through GE/2.5GE/10GE optical ports for the
RTN 320F.

For the slave NE:
NOTE
● Service ports on the master and slave NEs selected for an EPLA group must have the
same.
● The selected cascade ports on the master and slave NEs must have the same name.
----End

7.8.2.5 Creating an EPLA Group for NE-level Protection in LAG Mode

When physical link aggregation (EPLA) is required to improve Ethernet service
bandwidth or reliability on microwave links, you need to create an EPLA group.
Prerequisites
● No Ethernet service has been configured on the slave NE if an EPLA group
NEs in an EPLA group are configured with no Ethernet service.

NCE
Context
Create a cascade EPLA group in LAG mode according to the planned parameter
values listed in the following table.
Parameter Value
Protection Type NE-level LAG protection
NE Role Master
IF Port IF
Available Service Ports 10GE1(o)

NOTE
Configure service ports based on the
network plan.
Available Local Members 6(10GE2(o))-1, 6(10GE2(o))-2
Available Adjacent Members 6(10GE2(o))-1, 6(10GE2(o))-2
Procedure
Step 1 Create a non-load sharing LAG.

Step 2 Create a cascade EPLA group in LAG mode.

For the master NE:
NOTE
RTN 320F.
For the slave NE:
NOTE
same.

----End
7.8.2.6 Creating an EPLA Group for NE-level Protection in Optical Splitter

Mode
When physical link aggregation (EPLA) is required to improve Ethernet service
bandwidth or reliability on microwave links, you need to create an EPLA group.
Prerequisites
● No Ethernet service has been configured on the slave NE if an EPLA group
NEs in an EPLA group are configured with no Ethernet service.

NCE
Context
Create a cascade EPLA group in optical splitter mode according to the planned
Parameter Value
Protection Type NE-level Split protection
NE Role Master
IF Port IF1

Parameter Value
Available Service Ports 10GE1(o)

NOTE
Configure service ports based on the
network plan.
Available Local Members 6(10GE2(o))-1, 6(10GE2(o))-2
Available Adjacent Members 6(10GE2(o))-1, 6(10GE2(o))-2
Procedure
Step 1 Create a cascade EPLA group in optical splitter mode.
For the master NE:
NOTE
RTN 320F.
For the slave NE:
NOTE
same.

----End
7.8.2.7 Configuring AES Radio Interface Encryption

This section describes how to enable AES air interface encryption on OptiX RTN
320/320F and configure related parameters.
NOTE
Only the RTN 320F supports the AES air interface encryption function.
Prerequisites

NCE
Context
The following steps describe how to configure AES radio interface encryption
according to the planned values in the following table.
Parameter Value
Encryption Status Enabled
Key Negotiation Interval 7 days

Procedure
1. Configuring AES radio interface encryption.
7.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.
7.8.3.1 Creating a LAG

If link aggregation is required to improve the bandwidth and availability of
Ethernet links between two NEs, a LAG needs to be created.
Prerequisites

NCE
NOTE
Context
● Creates a load non-sharing LAG to protect the Ethernet link from the client
equipment to an NE. The following table lists the planned parameters.
Parameter Value
LAG No. Assign automatically
LAG Name LAG1
LAG Type Static (default value)

Parameter Value
Load Sharing Non-Sharing
LAG Priority 32768 (default value)
Packet Receive Timeout Period Long period
Master Port GE1
Standby Port GE2
● Creates a load sharing LAG to increase Ethernet bandwidth of Ethernet links.

The following table lists the planned parameters.
Parameter Value
LAG No. Assign automatically
LAG Name LAG1
Load Sharing Sharing
Packet Receive Timeout Period Long period
LAG Min. Active Links 2
Master Port GE1
Standby Port GE2
● Creates a LAG for NEs to configure 1+1 protection. The following table lists
the planned parameters.
Parameter Value
LAG No. Assign automatically (default

value)
Load Sharing Non-Sharing (default value)
Master Port GE1
Procedure
Step 1 Create a non-load sharing LAG.

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

7.8.3.2 Creating an ERPS Instance

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

NCE
NOTE
Context
The following procedure creates an ERPS instance according to the planned
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 Create an ERPS instance.
----End

7.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
● Ethernet boards and IF boards have been added to the NE Panel.

NCE
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.
● For multi-ring networks, Compatible_Version for all ring nodes must be ver2.
● 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 Set protocol parameters for an ERPS instance.
----End
7.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
● The service to be created does not conflict with existing services.

NCE
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 Create a point-to-point transparently transmitted E-Line service.
----End

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

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

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

NCE
NOTE
Precautions
● 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.
● 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 Create an IEEE 802.1d bridge-based E-LAN service.

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

NCE
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 Create an IEEE 802.1q bridge-based E-LAN service.
----End
7.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
● Ethernet local area network (E-LAN) services have been configured.

NCE
NOTE
Context
The following steps remove port IF1, from the ports mounted with E-LAN services.
Procedure
Step 1 Change logical ports mounted to a bridge.

----End
7.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
● An E-Line service has been configured.

NCE
NOTE
Context
The following procedure deletes the E-Line service whose ID is 1.
Procedure
Step 1 Delete an E-Line service.

----End
7.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
● An E-LAN service has been configured.

NCE
NOTE
Context
The following procedure deletes the E-LAN service whose ID is 1.
Procedure
Step 1 Delete an E-LAN service.

----End
7.8.3.11 Creating a DS Domain

By creating a DS domain, you can create the mappings relationship of a new DS
domain and configure the ports that use this mapping relationship.
Prerequisites
● On the NE Panel, you have added the board where the Ethernet port resides.

NCE
NOTE
Context
The following procedure creates a DS domain according to the planned values
listed in the following table.
Parameter Value
Mapping Relation ID 2
Mapping Relation Name Diffserv
Inbound Mapping Relationship Default values
Outbound Mapping Relationship Default values
Available Port (COMBO)

NOTE
The P&E interface is be used as an example
for RTN 320F.

Parameter Value
Packet Type cvlan
Enable Outbound Mapping Enable
Procedure
Step 1 Enter the Diffeserv Domain Management page, click NEW, the Create DS
Mapping RelationCreate DS Domain dialog box is displayed.
Step 2 Configure the mapping relationships between the priorities of ingress packets and
PHB service classes.

Step 3 Configure the mapping relationships between the priorities of egress packets and
PHB service classes.
Step 4 Set parameters of application port.

----End
7.8.3.12 Modifying the Mapping Relationship of the DiffServ Domain

This section describes how to modify the mapping relationship between packet
priorities and PHB service classes in the ingress or egress direction of a DiffServ
domain.
Prerequisites

NCE
NOTE
Context
OptiX RTN 320/320F has a default DiffServ domain whose Mapping Relation ID
is 1 and Mapping Relation Name is Default map. The default DiffServ domain
can be modified but cannot be deleted. Other DiffServ domains can be deleted or
modified.
The following procedure modifies the mapping relationship of the DiffServ domain
according to the planned values listed in the following table.

The following table describes parameters on the Inbound Mapping Relationship

tab.
C-VLAN 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
48-55 CS6
56-63 CS7
Procedure
Step 1 Modify the mapping relationship of the DiffServ domain.
----End
7.8.3.13 Modifying the Ports Applied to a DiffServ Domain and Packet Types
Trusted by Ports
This section describes how to modify the packet type trusted by ports on a NE.
Prerequisites

NCE

NOTE
Context
The following procedure modifies the packet types trusted by the microwave ports
to the planned value listed in the following table.
Parameter Packet Type
IF cvlan
Procedure
Step 1 Delete a port that uses the DiffServ domain.
Step 2 Add a port that uses the DiffServ domain.
Step 3 Change the packet type trusted by the port.

----End
7.8.3.14 Enabling/Disabling DSCP Demapping at Egress Ports

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

NCE
NOTE
Context
The following procedure sets Egress DSCP Mapping Status to Enabled.
Procedure
Step 1 Set Egress DSCP Mapping Status to Enabled.

----End
7.8.3.15 Enabling/Disabling Outbound Demapping at the Egress Port of a

DiffServ Domain
You can disable Outbound demapping at an egress port on an RTN NE to forbid
the NE modifying packet priorities.
Prerequisites

NCE
Context
The following procedure sets the enable status of outbound demapping at the
Egress port of a DS domain according to the planned value listed in the following
table.
Parameter value
GE Disable
Procedure
Step 1 Disabling Outbound Demapping at the Egress Port of a DiffServ Domain.

----End
7.8.3.16 Creating a WRR Policy

This section describes how to create a WRR policy.
Prerequisites

NCE
NOTE
Context
The following procedure creates a WRR policy according to the planned values
Parameter Value
Policy ID Assigned automatically
Policy Name WRR
CS7 Scheduling Weight 0
CS6 Scheduling Weight 0
EF Scheduling Weight 0
AF4 Scheduling Weight 25

Parameter Value
BE Scheduling Weight 0
Procedure
Step 1 Creating a WRR policy.
----End
7.8.3.17 Creating a Port WRED Policy

This section describes how to create a port WRED policy (WRED stands for
weighted random early detection).
Prerequisites

NCE
NOTE
Context
The following procedure creates a WRED policy according to the planned values

Parameter Value
Policy ID 2
Policy Name WRED
Lower Drop Threshold(256 bytes) 32, 32, 400
Upper Drop Threshold(256 bytes) 64, 64, 460
Drop Probability(%) 100, 100, 1
Procedure
Step 1 Creating a port WRED policy.
----End
7.8.3.18 Modifying the Port Policy

This section describes how to change the parameter values of a created port
policy.
Prerequisites
● The port policy must be created.

NCE
NOTE

Context
The following procedure modifies a port policy according to the planned values
Parameter Value
Bandwidth Limitation Enabled
Port WRED Policy 1-default port wred
Procedure
Step 1 Modifying the port policy.
----End
7.8.3.19 Creating a Port Policy

This section describes how to create port policies, including scheduling, shaping,
packet dropping, and WRR policies for egress queues.
Prerequisites
● The board of the Ethernet ports must be added onNE Panel.

NCE
NOTE
Context
The following procedure creates a port policy according to the planned values

Parameter Value
Policy ID 6
Policy Name Policy
WRR Scheduling Policy 1-WRR Default Scheduling
Enable Bandwidth Restriction Enabled
Port WRED Policy 1-default port WRED
Procedure
Step 1 Creating a port policy.
----End
7.8.3.20 Creating Traffic

By creating traffic, you can configure ACL, CoS, CAR and shaping for a specified
traffic stream on a specified port.
Prerequisites
● The Ethernet board must be added on the NE Panel.

NCE
NOTE

Context
The following procedure creates traffic.
Procedure
Step 1 Creating traffic.
----End
7.8.3.21 Setting the Port That Uses the Port Policy

This section describes how to set the port that uses the port policy.
Prerequisites
● The Ethernet board must be added on the NE Panel.

NCE
NOTE
Context
The following procedure sets the port that uses the port policy.
Procedure
Step 1 Setting the port that uses the port policy.

----End
7.8.3.22 Setting Egress Queue Scheduling Policies

This section describes how to set queue scheduling policies for an egress port.
Prerequisites

NCE
NOTE
Context
The following procedure sets 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)
AF1 WRR(weight=25)
BE WRR(weight=25)

Procedure
Step 1 Set egress queue scheduling policies.
----End
7.8.3.23 Creating a DS Domain Profile

A global DS domain profile can be created and applied to multiple NEs or ports on
a network.
Prerequisites

NCE
NOTE
Context
The following procedure creates a DS domain profile.
Parameter Value
Policy Name DIS
IP DSCP 8-15
16-23
24-31
32-39
40-47

Parameter Value
48-55
56-63
Procedure
Step 1 Enter the DS Proflie page.
Step 2 Set Inbound Mapping Relationship.
Step 3 Set Outbound Mapping Relationship.

----End
7.8.3.24 Creating a Port WRED Policy Profile

A global port WRED policy profile can be created and applied to multiple NEs or
ports on a network.
Prerequisites

NCE
NOTE
Context
The following procedure creates a port WRED policy profile.
Procedure
Step 1 Enter the Port WRED Proflie page.

Step 2 Create a port WRED policy profile.
----End
7.8.3.25 Creating a WRR Policy Profile

A WRR policy profile can be created and applied to multiple NEs or ports on a
network.
Prerequisites

NCE
NOTE
Context
The following procedure creates a WRR policy profile.

Parameter Value
Profile Name WRR
CS7 Scheduling Weight (0-100) 0
CS6 Scheduling Weight(0-100) 0
EFScheduling Weight(0-100) 0
AF4 Scheduling Weight(0-100) 25
BE Scheduling Weight(0-100) 0
Procedure
Step 1 Enter the WRR Scheduling Proflie page.
Step 2 Set WRR policy profile parameters.

----End
7.8.3.26 Creating a Port Policy Profile

A global port policy profile can be created and applied to multiple NEs or ports on
a network.
Prerequisites

NCE
NOTE
Context
The following procedure creates a port policy profile.
Parameter Value
Profile Name port
WFQ Scheduling Policy WFQ Default Scheduling
Bandwidth Limitation Enabled
CIR(kbit/s) 64
PIR(kbit/s) 64
CBS(bytes) 64
PBS(bytes) 64
Port WRED Policy Default port WRED

Procedure
Step 1 Enter the Port Proflie page.
Step 2 Create a port policy profile.
----End
7.8.3.27 Downloading a QoS Policy Profile to an NE or Port

You can apply various QoS policies to specified NEs or ports.
Prerequisites
● A policy profile has been created.

NCE
NOTE

Context
The following procedure downloads a DS domain profile to an NE or port.
NOTE
This topic describes how to download a DS domain profile to an NE or port. The method of
downloading other profiles is similar.
Procedure
Step 1 Enter the create profile page.
Step 2 Download profile to NE.
Step 3 Download profile to port.

NOTE
Before download the profile to a port, you need to download the profile to the NE where
the port is located.

----End
7.8.3.28 Releasing the QoS Policy Bound to an Interface

This operation releases the QoS policy bound to a port.
Prerequisites

NCE
NOTE
Context
The following steps release the QoS policy bound to a specified port.
NOTE
Procedure
Step 1 Releasing the QoS policy bound to an interface.
NOTE
On the NMS, the RTN 320F is displayed as the RTN 320.

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

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

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

----End
7.8.4 Configuring Clocks

7.8.4.1 Configuring the System Clock Source

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

NCE
NOTE
Context
The following steps configure GE1 interface as the clock source with the highest
priority.
Procedure
Step 1 Configuring the system clock source.

----End
7.8.4.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
● Clock sources have been configured.

NCE
NOTE
Context
● Enables the standard SSM protocol.
● Enables the extended SSM protocol and sets the IDs of the GE1(e) and the
internal clock source to 1 and 2 respectively.

NOTE
● 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).
● If the extended SSM protocol is enabled, set IDs for the following clock sources:
● Reference clock sources for a ring network
● 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
7.8.4.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
● Clock sources have been configured.

NCE

NOTE
Context
The following steps configure two clock sources as a group.
Procedure
Step 1 Configuring a clock source group.
----End

RTN 320&320F Commissioning and Configuration Guide (V100R021C10 - 02) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RTN 320&320F Commissioning and Configuration Guide (V100R021C10 - 02) (PDF) - en

Uploaded by

Copyright:

Available Formats

OptiX RTN 320&320F Radio Transmission System

Commissioning and Configuration

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Product Name Product Version

OptiX RTN 320/320F V100R021C10

iMaster NCE V100R021C10

This document is intended for:

● Installation and commissioning engineers

Indicates a hazard with a high level of risk which, if not

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. ii

Indicates a hazard with a medium level of risk which, if not

Indicates a hazard with a low level of risk which, if not

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices, and

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are

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

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

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

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

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. iii

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

> Multi-level menus are in boldface and separated by

Product Version V100R021C10 - Issue 02 (2022-09-30)

- Fixed the known bugs.

Product Version V100R021C10 - Issue 01 (2022-06-30)

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. iv

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

4 Site Commissioning (Configuring Commissioning Data Using the Web LCT)....... 37

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. v

4.1.1 Powering On the Device (DC Power Supply)...........................................................................................................38

6 Handling Common Faults During Site Deployment................................................... 119

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. vi

7 Configuring Network-wide Service Data.......................................................................121

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. vii

7.5.5 Configuration Example (XPIC Links with 1+1 Protection)................................................................................ 171

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. viii

7.6.7.3 Per-NE Configuration Process (Configuring QoS)............................................................................................ 240

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. ix

7.8.3.7 Creating an IEEE 802.1Q Bridge-based E-LAN Service................................................................................... 295

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. x

1.1 General Safety Precautions

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. 1

1.1 General Safety Precautions

All Safety Precautions

Local Laws and Regulations

Basic Installation Requirements

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. 2

1.2 Warning and Safety Symbols

Label Label Name Description

ESD protection label Indicates that the equipment

Radiation warning label Indicates that the equipment

Issue 02 (2022-09-30) Copyright © Huawei Technologies Co., Ltd. 3

Label Label Name Description

High temperature warning Indicates that the equipment

Grounding label Indicates the grounding

1.3 Electrical Safety

● A high-voltage power supply provides power for device operations. Direct