RTN 310 V100R001C01 Commissioning and Configuration Guide 02 PDF

OptiX RTN 310 Radio Transmission System
V100R001C01
Commissioning and Configuration

Guide
Issue
02
Date
2012-12-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2012-12-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

Commissioning and Configuration Guide
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX RTN 310
V100R001C01
iManager U2000
V100R008C00
Intended Audience
This document describes how to commission OptiX RTN 310, including preparations, site
commissioning, system commissioning, and network-wide service data configuration.
This document is intended for:
l
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
Alerts you to a high risk hazard that could, if
not avoided, result in serious injury or death.
Alerts you to a medium or low risk hazard that
could, if not avoided, result in moderate or
minor injury.
Issue 02 (2012-12-30)

ii

About This Document
Symbol
Description
Alerts you to a potentially hazardous situation
that could, if not avoided, result in equipment
damage, data loss, performance deterioration,
or unanticipated results.
Provides a tip that may help you solve a
problem or save time.
Provides additional information to emphasize
or supplement important points in the main
text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Issue 02 (2012-12-30)
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

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

vertical bars. One item is selected or no item is selected.

iii

About This Document
Convention
Description
{ x | y | ... }*
Optional items are grouped in braces and separated by

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

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

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

signs. For example, choose File > Create > Folder.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 02 (2012-12-30)
This issue is the second release for the product version V100R001C01.
Change
Description
8.7 Configuring Native Ethernet Services
Added end-to-end configuration examples.
Issue 01 (2012-10-30)
This issue is the first release for the product version V100R001C01.
Issue 02 (2012-12-30)

iv

Contents
Contents
About This Document.....................................................................................................................ii
1 Safety Precautions.........................................................................................................................1
1.1 General Safety Precautions.................................................................................................................................2
1.2 Warning and Safety Symbols.............................................................................................................................3
1.3 Electrical Safety..................................................................................................................................................4
1.4 Environment of Flammable Gas.........................................................................................................................5
1.5 Storage Batteries.................................................................................................................................................6
1.6 Radiation.............................................................................................................................................................7
1.6.1 Safe Usage of Optical Fibers.....................................................................................................................8
1.6.2 Electromagnetic Exposure.........................................................................................................................8
1.6.3 Forbidden Areas........................................................................................................................................8
1.6.4 Laser..........................................................................................................................................................9
1.6.5 Microwave...............................................................................................................................................10
1.7 Working at Heights...........................................................................................................................................10
1.7.1 Hoisting Heavy Objects...........................................................................................................................10
1.7.2 Using Ladders..........................................................................................................................................11
1.8 Mechanical Safety............................................................................................................................................13
1.9 Other Precautions.............................................................................................................................................14
2 Commissioning Preparations....................................................................................................16
2.1 Preparing Documents and Tools.......................................................................................................................17
2.2 Preparing a USB Flash Drive...........................................................................................................................18
2.3 Determining the Commissioning Method........................................................................................................18
2.4 Checking Commissioning Conditions..............................................................................................................19
2.4.1 Checking Site Commissioning Conditions..............................................................................................19
2.4.2 Checking System Commissioning Conditions........................................................................................19
3 Commissioning Process.............................................................................................................20
3.1 Site Commissioning Process............................................................................................................................21
3.2 System Commissioning Process.......................................................................................................................23
4 Site Commissioning (Using a USB Flash Drive to Configure Data).................................25

4.1 Powering on the Equipment.............................................................................................................................27
4.2 Loading Commissioning Data Using a USB Flash Drive................................................................................31
4.3 Connecting the Web LCT to the Equipment....................................................................................................34
Issue 02 (2012-12-30)


Contents
4.4 Creating NEs Using the Search Method...........................................................................................................37

4.5 Synchronizing NE Time...................................................................................................................................38
4.6 Checking Alarms..............................................................................................................................................39
4.7 Aligning Antennas............................................................................................................................................40
4.7.1 Main Lobe and Side Lobes......................................................................................................................40
4.7.2 Aligning Single-Polarized Antennas.......................................................................................................43
4.7.3 Aligning Dual-Polarized Antennas..........................................................................................................46
4.8 Checking the Microwave Link Status and Receive Power...............................................................................52
5 Site Commissioning (Using the Web LCT to Configure Data)..........................................54

5.4 Configuring Site Commissioning Data.............................................................................................................63
5.4.1 Changing an NE ID.................................................................................................................................66
5.4.2 Setting NE Communication Parameters..................................................................................................66
5.4.3 Changing an NE Name............................................................................................................................67
5.4.4 Setting the VLAN ID and Bandwidth for an Inband DCN.....................................................................68
5.4.5 Setting OSPF Protocol Parameters..........................................................................................................69
5.4.6 Creating a LAG.......................................................................................................................................70
5.4.7 Creating a Microwave 1+1 Protection Group..........................................................................................73
5.4.8 Creating a PLA Group.............................................................................................................................74
5.4.9 Configuring a Single Hop of Microwave Link........................................................................................75
5.4.10 Synchronizing NE Time........................................................................................................................77
5.5 Checking Alarms..............................................................................................................................................78
6 System Commissioning..............................................................................................................93
6.1 Configuring Network-wide Service Data.........................................................................................................94
6.2 Testing Ethernet Services.................................................................................................................................94
6.2.1 Testing Ethernet Services Configured on a Per NE Basis.......................................................................94
6.2.2 Testing Ethernet Services Configured in End-to-End Mode...................................................................95
6.3 Testing AM Shifting.........................................................................................................................................97
6.4 Testing Protection Switching............................................................................................................................98
6.4.1 Testing ERPS Switching.........................................................................................................................98
6.4.2 Testing 1+1 Protection Switching.........................................................................................................101
6.4.3 Testing PLA Protection Switching........................................................................................................103
6.5 Checking the Clock Status..............................................................................................................................105
6.6 Testing the Fade Margin over a Microwave Link..........................................................................................105
6.7 Testing Ethernet Service Performance...........................................................................................................107
Issue 02 (2012-12-30)

vi

Contents
6.7.1 Testing the Latency, Throughput, and Packet Loss Ratio.....................................................................107

6.7.2 Testing the Long-term Packet Loss Ratio.............................................................................................110
7 Handling of Common Faults During Site Deployment....................................................113

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

8.1 Configuration Preparations.............................................................................................................................118
8.1.1 Preparing Documents and Tools............................................................................................................118
8.1.2 Checking Configuration Conditions......................................................................................................118
8.2 U2000 Quick Start..........................................................................................................................................118
8.3 General Configuration Process.......................................................................................................................118
8.4 Common Configuration Scenarios of Microwave Transmission Networks...................................................120
8.4.1 Microwave Chain Network...................................................................................................................120
8.4.2 Microwave Ring Network.....................................................................................................................122
8.5 Configuring the Network Topology...............................................................................................................123
8.5.1 Basic Concepts......................................................................................................................................123
8.5.1.1 DCN..............................................................................................................................................123
8.5.1.2 Access Control..............................................................................................................................124
8.5.1.3 GNE and Non-GNE......................................................................................................................126
8.5.1.4 NE ID and NE IP Address............................................................................................................127
8.5.1.5 Fiber/Cable Types.........................................................................................................................127
8.5.1.6 Subnet...........................................................................................................................................128
8.5.2 Configuration Process (Network Topology).........................................................................................128
8.5.3 Configuration Example (Microwave Chain Network Topology)..........................................................135
8.5.3.1 Networking Diagram....................................................................................................................135
8.5.3.2 Service Planning...........................................................................................................................136
8.5.3.3 Configuration Procedure...............................................................................................................138
8.5.4 Configuration Example (Microwave Ring Network Topology)...........................................................140
8.6 Configuring Microwave Links.......................................................................................................................145
8.6.1 Basic Concepts......................................................................................................................................145
8.6.1.1 Adaptive Modulation....................................................................................................................145
8.6.1.2 CCDP and XPIC...........................................................................................................................147
8.6.1.3 RF Configuration Modes..............................................................................................................148
8.6.1.4 PLA...............................................................................................................................................151
8.6.1.5 E-LAG..........................................................................................................................................152
8.6.1.6 Hop Management.........................................................................................................................154
8.6.2 Configuration Process (Microwave Links)............................................................................................155
8.6.3 Configuration Example (Microwave Links on a Microwave Chain Network).....................................162
Issue 02 (2012-12-30)

vii

Contents

8.6.4 Configuration Example (Microwave Links on a Microwave Ring Network).......................................171
8.7 Configuring Native Ethernet Services ...........................................................................................................176
8.7.1 Basic Concepts......................................................................................................................................176
8.7.1.1 Auto-negotiation...........................................................................................................................176
8.7.1.2 Flow Control Function..................................................................................................................177
8.7.1.3 Ethernet Port Description.............................................................................................................178
8.7.1.4 MAC Address Table Management...............................................................................................179
8.7.1.5 VLAN Forwarding Tables for E-Line Services............................................................................180
8.7.1.6 Split Horizon Groups....................................................................................................................181
8.7.1.7 Protection for Native Ethernet Services.......................................................................................181
8.7.2 Native Ethernet Service Types..............................................................................................................183
8.7.2.1 Transparently Transmitted Point-to-Point E-Line Service...........................................................183
8.7.2.2 VLAN-based E-Line Service........................................................................................................185
8.7.2.3 IEEE 802.1D Bridge-based E-LAN Services...............................................................................186
8.7.2.4 IEEE 802.1Q Bridge-based E-LAN Services...............................................................................187
8.7.3 Typical Mobile Bearer Network Topologies for Ethernet Services......................................................188
8.7.3.1 Networking of VLAN-based E-Line Services..............................................................................188
8.7.3.2 Networking of IEEE 802.1D Bridge-based E-LAN Services......................................................189
8.7.3.3 Networking of IEEE 802.1Q Bridge-based E-LAN Services......................................................190
8.7.3.4 Comparison Between the Three Networking Modes...................................................................191
8.7.4 Configuration Process............................................................................................................................194
8.7.4.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point E-Line Services)
..................................................................................................................................................................195
8.7.4.2 End-to-End Configuration Process (Transparently Transmitted Point-to-Point E-Line Services)
..................................................................................................................................................................201
8.7.4.3 Per-NE Configuration Process (VLAN-based E-Line Services)..................................................205
8.7.4.4 End-to-End Configuration Process (VLAN-based E-Line Services)...........................................213
8.7.4.5 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)...........................218
8.7.4.6 End-to-End Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)....................227
8.7.4.7 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)...........................231
8.7.4.8 End-to-End Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)....................240
8.7.5 Configuration Example (Transparently Transmitted Point-to-Point E-Line Services).........................245
8.7.5.2 Service Planning (Port Information).............................................................................................246
8.7.5.3 Service Planning (Ethernet Protection)........................................................................................246
8.7.5.4 Service Planning (Ethernet Services)...........................................................................................247
8.7.5.5 Service Planning (QoS)................................................................................................................247
Issue 02 (2012-12-30)

viii

Contents
8.7.5.6 Per-NE Configuration Procedure (Ethernet Protection)...............................................................250

8.7.5.7 Per-NE Configuration Procedure (Ethernet Ports).......................................................................250
8.7.5.8 Per-NE Configuration Procedure (QoS).......................................................................................250
8.7.5.9 Per-NE Configuration Procedure (Ethernet Service Verification)...............................................253
8.7.5.10 End-to-End Configuration Procedure.........................................................................................254
8.7.6 Configuration Example (VLAN-based E-Line Service).......................................................................254
8.7.6.2 Service Planning (Ethernet Ports).................................................................................................256
8.7.6.7 Per-NE Configuration Procedure (Service Information)..............................................................262
8.7.6.10 End-to-End Configuration Procedure (Ethernet Protection)......................................................272
8.7.6.11 End-to-End Configuration Procedure (Service Information).....................................................272
8.7.6.12 End-to-End Configuration Procedure (QoS)..............................................................................274
8.7.6.13 End-to-End Configuration Procedure (Ethernet Service Verification)......................................277
8.7.7 Configuration Example (IEEE 802.1D Bridge-based E-LAN Service)................................................278
8.7.7.10 Per-NE Configuration Procedure (Ethernet Service Verification).............................................292
8.7.7.13 End-to-End Configuration Procedure (Verifying Ethernet Service Configurations).................300
8.7.8 Configuration Example (IEEE 802.1Q Bridge-based E-LAN Service)................................................302
Issue 02 (2012-12-30)

ix

Contents

8.8 Configuring Clocks.........................................................................................................................................327
8.8.1 Basic Concepts......................................................................................................................................327
8.8.1.1 Clock Source.................................................................................................................................327
8.8.1.2 Clock Protection Modes...............................................................................................................328
8.8.1.3 Clock Synchronization Policy......................................................................................................333
8.8.2 Configuration Process (Configuring a Clock).......................................................................................337
8.8.3 Configuration Example (Clock on a Microwave Chain Network)........................................................339
8.8.4 Configuration Example (Clock on a Microwave Ring Network)..........................................................342
8.9 Adding and Modifying Configuration Data...................................................................................................345
8.9.1 Common Task Collection (Network Topology)....................................................................................345
8.9.2 Common Task Collection (Microwave Links)......................................................................................346
8.9.3 Common Task Collection (Ethernet Services)......................................................................................348
A Task Collection.........................................................................................................................351
A.1 U2000 Quick Start.........................................................................................................................................352
A.1.1 Logging In to a U2000 Client...............................................................................................................352
A.1.2 Shutting Down a U2000 Client.............................................................................................................352
A.1.3 Using the Help......................................................................................................................................353
A.1.4 Navigating to Common Views.............................................................................................................354
A.1.4.1 Navigating to Main Topology.....................................................................................................354
A.1.4.2 Navigating to NE Explorer..........................................................................................................355
A.1.4.3 Navigating to the NE Panel.........................................................................................................356
A.2 Web LCT Quick Start....................................................................................................................................357
A.2.1 Connecting the Web LCT to the Equipment........................................................................................357
A.2.2 Using the Help......................................................................................................................................360
A.2.3 Navigating to NE Explorer...................................................................................................................361
A.3 Network Management...................................................................................................................................362
A.3.1 Managing NEs......................................................................................................................................362
A.3.1.1 Creating an NE by Using the Search Method..............................................................................362
A.3.1.2 Creating an NE Manually............................................................................................................364
A.3.1.3 Logging In to an NE....................................................................................................................365
Issue 02 (2012-12-30)


Contents
A.3.1.4 Changing an NE ID.....................................................................................................................366

A.3.1.5 Changing an NE Name................................................................................................................367
A.3.1.6 Synchronizing the NE Time........................................................................................................368
A.3.1.7 Localizing the NE Time...............................................................................................................370
A.3.1.8 Configuring a Standard NTP Key................................................................................................371
A.3.2 Configuring NE Data............................................................................................................................372
A.3.2.1 Uploading NE Data......................................................................................................................373
A.3.2.2 Synchronizing NE Data...............................................................................................................374
A.3.3 Setting the Performance Monitoring Status for an NE.........................................................................375
A.3.4 Creating a Fiber/Cable..........................................................................................................................376
A.3.4.1 Creating a Fiber/Cable by Using the Search Method..................................................................376
A.3.4.2 Creating a Fiber/Cable Manually.................................................................................................377
A.3.4.3 Creating an Extended ECC Connection......................................................................................378
A.3.4.4 Creating a Back-to-back Radio Connection................................................................................379
A.3.5 Managing Subnets................................................................................................................................380
A.3.5.1 Creating a Subnet.........................................................................................................................380
A.3.5.2 Copying a Topology Object.........................................................................................................381
A.3.5.3 Moving a Topology Object..........................................................................................................382
A.3.6 Managing Communication...................................................................................................................383
A.3.6.1 Setting NE Communication Parameters......................................................................................383
A.3.6.2 Configuring DCCs.......................................................................................................................384
A.3.6.3 Setting the VLAN ID and Bandwidth for an Inband DCN.........................................................385
A.3.6.4 Configuring the Priorities of Inband DCN Packets.....................................................................386
A.3.6.5 Setting a Port for an Inband DCN................................................................................................387
A.3.6.6 Configuring Access Control........................................................................................................389
A.3.6.7 Configuring Extended ECCs.......................................................................................................390
A.3.6.8 Creating a Static IP Route............................................................................................................392
A.3.6.9 Setting OSPF Protocol Parameters..............................................................................................393
A.3.6.10 Creating an OSPF Area.............................................................................................................394
A.3.6.11 Configuring the Network Information of an ABR....................................................................395
A.3.6.12 Creating a Manual Route Aggregation Group...........................................................................397
A.3.6.13 Configuring Port IP Addresses for an ABR..............................................................................398
A.3.6.14 Configuring the OSPF Authentication Type.............................................................................399
A.3.6.15 Enabling the Proxy ARP............................................................................................................401
A.3.6.16 Querying ECC Routes...............................................................................................................402
A.3.6.17 Querying IP Routes....................................................................................................................403
A.3.6.18 Verifying Connectivity of an ECC Network.............................................................................404
A.3.6.19 Verifying Connectivity of an IP DCN Network........................................................................405
A.3.6.20 Setting SNMP Communication Parameters...............................................................................407
A.3.6.21 Configuring the Active and Standby Gateway NEs..................................................................408
A.3.7 Configuring the NMS Port on an NE...................................................................................................409
A.4 Security Management....................................................................................................................................410
Issue 02 (2012-12-30)

xi

Contents
A.4.1 Configuring an NE User.......................................................................................................................410

A.4.1.1 Creating an NE User....................................................................................................................410
A.4.1.2 Changing the Password of an NE User........................................................................................412
A.4.1.3 Setting the Warning Screen Parameters.......................................................................................412
A.4.1.4 Switching NE Users.....................................................................................................................413
A.4.2 Configuring Web LCT Access to an NE..............................................................................................414
A.4.3 Configuring an Access Control List for an NE....................................................................................415
A.4.3.1 Creating Basic ACL Rules...........................................................................................................415
A.4.3.2 Creating Advanced ACL Rules...................................................................................................416
A.4.4 Querying NE Operation Logs...............................................................................................................417
A.4.5 Querying Operation Logs Sent to Syslog Servers................................................................................418
A.4.6 Configuring Syslog...............................................................................................................................419
A.4.6.1 Enabling the Syslog Service........................................................................................................419
A.4.6.2 Setting Types and Severities of Logs to Be Sent to Syslog Servers............................................419
A.4.6.3 Configuring Syslog Servers.........................................................................................................420
A.4.6.4 Configuring Gateway NEs for Communication Between NEs and Syslog Servers....................421
A.4.7 Configuring File Transfer Protocols.....................................................................................................422
A.4.8 Configuring SSL Protocol Communication..........................................................................................423
A.4.8.1 Configuring SSL Protocol Communication Between a U2000 Server and Its Clients...............423
A.4.8.2 Configuring the Connection Mode Between the U2000 and Its Gateway NE............................424
A.4.9 Configuring RADIUS Authentication..................................................................................................425
A.4.9.1 Enabling/Disabling the RADIUS Authentication Function........................................................426
A.4.9.2 Creating a RADIUS Server or a RADIUS Proxy Server............................................................426
A.4.9.3 Configuring RADIUS Server Parameters....................................................................................428
A.5 Managing Microwave Links..........................................................................................................................430
A.5.1 Configuring a Single Hop of Microwave Link.....................................................................................430
A.5.2 Browsing the Performance of a Hop of Microwave Link....................................................................432
A.5.3 Creating a Microwave 1+1 Protection Group.......................................................................................433
A.5.4 Microwave 1+1 Protection Switching..................................................................................................435
A.5.5 Querying the Microwave 1+1 Protection Status...................................................................................436
A.5.6 Creating a PLA Group..........................................................................................................................436
A.5.7 Querying the Status of a PLA Group....................................................................................................438
A.5.8 Configuring Ethernet Frame Header Compression and Errored Frame Discarding Over Air Interfaces
........................................................................................................................................................................438
A.5.9 Enabling the Notification of Radio Bandwidth....................................................................................439
A.5.10 Setting the Maximum Transmit Power and the Power Thresholds....................................................440
A.5.11 Querying the AM Status.....................................................................................................................441
A.5.12 Querying ATPC Adjustment Records................................................................................................442
A.5.13 Querying Historical Transmit Power and Receive Power..................................................................443
A.5.14 Querying the SNR Value of a Microwave Link.................................................................................444
A.6 Managing Ports..............................................................................................................................................445
A.6.1 Setting Parameters for an Ethernet Port................................................................................................445
A.6.1.1 Setting the Basic Attributes for an Ethernet Port.........................................................................445
Issue 02 (2012-12-30)

xii

Contents
A.6.1.2 Configuring the Traffic Control Function for an Ethernet Port...................................................446

A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port.....................................................................447
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port.................................................................449
A.6.1.5 Querying the Running Status of a Microwave Port.....................................................................450
A.6.2 Setting Parameters for a Microwave Port.............................................................................................451
A.6.2.1 Setting Basic Attributes for a Microwave Port............................................................................451
A.6.2.2 Setting Layer 2 Attributes for a Microwave Port........................................................................452
A.6.2.3 Setting Advanced Attributes for a Microwave Port....................................................................453
A.6.2.4 Querying the Running Status of an Ethernet Port.......................................................................454
A.7 Managing Ethernet Services and Features.....................................................................................................455
A.7.1 Managing ERPS....................................................................................................................................455
A.7.1.1 Creating an ERP Instance............................................................................................................455
A.7.1.2 Setting ERPS Protocol Parameters..............................................................................................457
A.7.1.3 Querying the ERPS Status...........................................................................................................458
A.7.2 Managing LAGs...................................................................................................................................458
A.7.2.1 Creating a LAG............................................................................................................................458
A.7.2.2 Setting Parameters for a LAG......................................................................................................461
A.7.2.3 Querying the Protocol Information About a LAG.......................................................................462
A.7.3 Configuring Ethernet Services..............................................................................................................463
A.7.3.1 Creating a Point-to-Point Transparently Transmitted E-Line Service.........................................463
A.7.3.2 Creating a VLAN-based E-Line Service.....................................................................................464
A.7.3.3 Creating an E-Line Service for Transmitting Layer 2 Protocol Packets.....................................465
A.7.3.4 Creating VLAN Forwarding Table Entries.................................................................................467
A.7.3.5 Creating an IEEE 802.1D Bridge-based E-LAN Service............................................................468
A.7.3.6 Creating an IEEE 802.1Q Bridge-based E-LAN Service............................................................469
A.7.3.7 Creating an E-LAN Service for Transmitting Layer 2 Protocol Packets....................................470
A.7.3.8 Configuring a Split Horizon Group.............................................................................................472
A.7.3.9 Changing Logical Ports Mounted to a Bridge.............................................................................473
A.7.3.10 Deleting an E-Line Service........................................................................................................473
A.7.3.11 Deleting an E-LAN Service.......................................................................................................474
A.7.4 Managing MAC Address Tables..........................................................................................................475
A.7.4.1 Creating a Static MAC Address Entry.........................................................................................475
A.7.4.2 Creating a Blacklist MAC Address Entry...................................................................................476
A.7.4.3 Managing a Dynamic MAC Address Table................................................................................477
A.7.5 Setting the Mode for Processing an Unknown Frame of an E-LAN Service.......................................478
A.7.6 Managing QoS......................................................................................................................................479
A.7.6.1 Modifying the Mapping for a DS Domain..................................................................................479
A.7.6.2 Changing the Packet Type Trusted by a Port..............................................................................481
A.7.6.3 Configuring Port Shaping............................................................................................................482
A.7.6.4 Setting Egress Queue Scheduling Policies..................................................................................483
A.7.6.5 Setting Traffic Shaping for Egress Queues.................................................................................484
A.7.6.6 Setting the Congestion Management Mode for Egress Queues..................................................485
Issue 02 (2012-12-30)

xiii

Contents
A.7.7 Using Ethernet Service OAM...............................................................................................................487

A.7.7.1 Creating an MD...........................................................................................................................487
A.7.7.2 Creating an MA...........................................................................................................................488
A.7.7.3 Creating an MEP..........................................................................................................................489
A.7.7.4 Creating a Remote MEP in an MA..............................................................................................490
A.7.7.5 Creating an MIP...........................................................................................................................491
A.7.7.6 Performing a CC Test..................................................................................................................492
A.7.7.7 Performing an LB Test................................................................................................................493
A.7.7.8 Performing an LT Test.................................................................................................................495
A.7.7.9 Activating the AIS.......................................................................................................................496
A.7.7.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services......................497
A.7.7.11 Performing E-LAN Service Loopback Detection......................................................................499
A.7.7.12 Reactivating an E-LAN Service................................................................................................500
A.7.8 Using Ethernet Port OAM....................................................................................................................501
A.7.8.1 Enabling OAM Auto-discovery...................................................................................................501
A.7.8.2 Enabling the Link Event Notification..........................................................................................502
A.7.8.3 Changing the OAM Errored Frame Monitoring Threshold.........................................................503
A.7.8.4 Performing a Remote Loopback..................................................................................................504
A.7.8.5 Enabling Self-loop Detection......................................................................................................506
A.7.9 Configuring LPT...................................................................................................................................507
A.8 Managing Clocks...........................................................................................................................................508
A.8.1 Managing Clocks at the Physical Layer...............................................................................................508
A.8.1.1 Changing the Clock Control Mode..............................................................................................508
A.8.1.2 Configuring Clock Sources..........................................................................................................509
A.8.1.3 Configuring Protection for Clock Sources..................................................................................510
A.8.1.4 Customizing the Clock Quality...................................................................................................512
A.8.1.5 Enabling/Disabling SSM Transmission.......................................................................................513
A.8.1.6 Enabling/Disabling the Output of Clock Source IDs..................................................................514
A.8.1.7 Modifying Clock Source Reversion Parameters..........................................................................514
A.8.1.8 Querying the Clock Synchronization Status................................................................................515
A.8.2 Managing the IEEE 1588v2 Clock.......................................................................................................516
A.8.2.1 Enabling/Disabling the IEEE-1588 Timeslot for a Microwave Port...........................................516
A.8.2.2 Querying or Modifying the PTP System Time............................................................................517
A.8.2.3 Setting the PTP NE Attributes.....................................................................................................518
A.8.2.4 Creating a PTP Clock Port...........................................................................................................519
A.8.2.5 Setting PTP Clock Port Attributes...............................................................................................520
A.8.2.6 Setting Parameters for IEEE 1588v2 Clock Packets...................................................................522
A.8.2.7 Configuring the Delay Offset for Asymmetric Transmission Between NEs...............................524
A.8.2.8 Configuring the Cascade Fiber Length for a 1+1 Protection Group...........................................525
A.8.2.9 Configuring a PTP Clock Subnet................................................................................................526
A.8.2.10 Modifying the BMC Algorithm Parameters for an NE Clock...................................................527
A.9 Using RMON.................................................................................................................................................528
Issue 02 (2012-12-30)

xiv

Contents
A.9.1 Browsing Current Performance Events of Ethernet.............................................................................528

A.9.2 Setting the Ethernet Performance Threshold-Crossing Parameter.......................................................529
A.9.3 Configuring the Parameters for Ethernet Historical Performance Monitoring.....................................530
A.9.4 Browsing Ethernet Historical Performance Data..................................................................................531
A.10 Configuring a Native Ethernet Service (in End-to-End Mode)...................................................................532
A.10.1 Searching for Native Ethernet Services..............................................................................................532
A.10.2 Creating a Point-to-Point Transparently Transmitted E-Line Service................................................533
A.10.3 Creating a VLAN-based E-Line Service............................................................................................534
A.10.4 Creating an IEEE 802.1D Bridge-based E-LAN Service...................................................................535
A.10.5 Creating an IEEE 802.1Q Bridge-based E-LAN Service...................................................................537
A.10.6 Verifying a Native Ethernet Service...................................................................................................539
A.10.7 Managing Native Ethernet Services...................................................................................................541
A.10.8 Managing Discrete Native Ethernet Services ....................................................................................542
A.10.9 Adjusting an E-LAN Service Network...............................................................................................543
A.11 Verifying Services and Features..................................................................................................................544
A.11.1 Testing Ethernet Services...................................................................................................................544
A.11.1.1 Testing Ethernet Services Configured on a Per NE Basis.........................................................544
A.11.1.2 Testing Ethernet Services Configured in End-to-End Mode.....................................................546
A.11.2 Testing AM Shifting...........................................................................................................................547
A.11.3 Testing Protection Switching..............................................................................................................548
A.11.3.1 Testing ERPS Switching............................................................................................................548
A.11.3.2 Testing 1+1 Protection Switching.............................................................................................551
A.11.3.3 Testing PLA Protection Switching............................................................................................553
B Parameters Description............................................................................................................556
B.1 Parameters for Network Management...........................................................................................................557
B.1.1 Parameters for NE Management...........................................................................................................557
B.1.1.1 Parameter Description: NE Searching.........................................................................................557
B.1.1.2 Parameter Description: NE Creation...........................................................................................560
B.1.1.3 Parameter Description: NE Time Synchronization (U2000).......................................................562
B.1.1.4 Parameter Description: Standard NTP Key Management...........................................................565
B.1.1.5 Parameter Description: Localization Management of the NE Time............................................566
B.1.2 Parameters for Communications Management.....................................................................................567
B.1.2.1 Parameter Description: NE Communication Parameter Setting..................................................567
B.1.2.2 Parameter Description: ECC Management_Ethernet Port Extended ECC..................................569
B.1.2.3 Parameter Description: NE ECC Link Management...................................................................570
B.1.2.4 Parameter Description: ECC Link Management_Availability Test............................................571
B.1.2.5 Parameter Description: Access Control.......................................................................................572
B.1.2.6 Parameter Description: DCC Management_DCC Rate Configuration........................................574
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management........................575
B.1.2.8 Parameter Description: IP Protocol Stack Management_Availability Test.................................576
B.1.2.9 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings...................577
B.1.2.10 Parameter Description: IP Protocol Stack_Proxy ARP.............................................................582
Issue 02 (2012-12-30)

xv

Contents
B.1.2.11 Parameter Description: Management of Multiple OSPF Areas.................................................583

B.1.2.12 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas..............584
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be Manually
Aggregated................................................................................................................................................586
B.1.2.14 Parameter Description: Port OSPF Setting................................................................................586
B.1.2.15 Parameter Description: DCN Management_Bandwidth Management......................................586
B.1.2.16 Parameter Description: DCN Management_Port Setting..........................................................587
B.1.2.17 Parameter Description: DCN Management_Access Control.....................................................588
B.1.2.18 Parameter Description: DCN Management_Packet Control.....................................................589
B.1.2.19 Parameter Description: SNMP Communications Parameters Setting.......................................590
B.1.3 Parameters for RADIUS.......................................................................................................................590
B.1.3.1 Parameter Description: RADIUS Configuration_Creation.........................................................591
B.1.3.2 Parameter Description: Enabling/Disabling the RADIUS Function...........................................592
B.2 Radio Link Parameters...................................................................................................................................592
B.2.1 Parameter Description: IF 1+1 Protection Group.................................................................................592
B.2.2 Parameter Description: PLA Group Creation.......................................................................................596
B.2.3 Parameters Description: Radio Link Configuration.............................................................................597
B.3 Parameters for Board Interfaces.....................................................................................................................603
B.3.1 Parameters for the Ports on Ethernet Boards........................................................................................603
B.3.1.1 Parameter Description: Ethernet Interface_Basic Attributes.......................................................603
B.3.1.2 Parameter Description: Ethernet Interface_Flow Control...........................................................606
B.3.1.3 Parameter Description: Ethernet Interface_Layer 2 Attributes....................................................608
B.3.1.4 Parameter Description: Ethernet Interface_Advanced Attributes................................................610
B.3.2 Microwave Interface Parameters..........................................................................................................613
B.3.2.1 Parameter Description: Microwave Interface_Basic Attributes..................................................613
B.3.2.2 Parameter Description: Microwave Interface_Layer 2 Attributes...............................................614
B.3.2.3 Parameter Description: Microwave Interface_Advanced Attributes...........................................615
B.4 Parameters for Ethernet Services and Ethernet Features...............................................................................617
B.4.1 Parameters for Ethernet Services..........................................................................................................617
B.4.1.1 Parameter Description: E-Line Service........................................................................................617
B.4.1.2 Parameter Description: E-LAN Service.......................................................................................622
B.4.2 Parameters for Ethernet Protocols........................................................................................................633
B.4.2.1 Parameter Description: ERPS Management................................................................................633
B.4.2.2 Parameter Description: Ethernet Link Aggregation Management...............................................639
B.4.2.3 Parameter Description: Ethernet Link Aggregation_Link Aggregation......................................646
B.4.2.4 Parameter Description: Simplified LPT Creation........................................................................647
B.4.3 Parameters for the Ethernet OAM........................................................................................................648
B.4.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation
..................................................................................................................................................................648
B.4.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation
..................................................................................................................................................................649
B.4.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation............................650
B.4.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation..............651
Issue 02 (2012-12-30)

xvi

Contents
B.4.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation.............................652

B.4.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling..............................653
B.4.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling...............................654
B.4.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback Detection............655
B.4.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter..............................656
B.4.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
..................................................................................................................................................................658
B.4.4 Parameter Description: QoS Management............................................................................................660
B.5 RMON Parameters.........................................................................................................................................668
B.5.1 Parameter Description: RMON Performance_Statistics Group............................................................668
B.5.2 Parameter Description: RMON Performance_History Group..............................................................669
B.5.3 Parameter Description: RMON Performance_RMON Setting.............................................................670
B.6 Clock Parameters...........................................................................................................................................671
B.6.1 Physical-Layer Clock Parameters.........................................................................................................671
B.6.1.1 Parameter Description: Clock Synchronization Status................................................................672
B.6.1.2 Parameter Description: Clock Source Priority Table...................................................................673
B.6.1.3 Parameter Description: Clock Source Switching_Clock Source Switching................................674
B.6.1.4 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters...........675
B.6.1.5 Parameter Description: Clock Subnet Setting_Clock Subnet......................................................677
B.6.1.6 Parameter Description: Clock Subnet Setting_Clock Quality.....................................................680
B.6.1.7 Parameter Description: Clock Subset Setting_SSM Output Control...........................................683
B.6.1.8 Parameter Description: Clock Subset Setting_Clock ID Enabling Status...................................684
B.7 PTP Clock Parameters...................................................................................................................................685
B.7.1 Parameter Description: Clock Synchronization Attribute....................................................................685
B.7.2 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet................................................696
B.7.3 Parameter Description: Setting of a PTP Clock Subnet_Port_BMC....................................................696
C Glossary......................................................................................................................................699
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
Issue 02 (2012-12-30)

xvii

Contents
1.5 Storage Batteries.................................................................................................................................................6

1.6 Radiation.............................................................................................................................................................7
1.6.1 Safe Usage of Optical Fibers.....................................................................................................................8
1.6.2 Electromagnetic Exposure.........................................................................................................................8
1.6.3 Forbidden Areas........................................................................................................................................8
1.6.4 Laser..........................................................................................................................................................9
1.6.5 Microwave...............................................................................................................................................10
1.7 Working at Heights...........................................................................................................................................10
1.7.1 Hoisting Heavy Objects...........................................................................................................................10
1.7.2 Using Ladders..........................................................................................................................................11
1.8 Mechanical Safety............................................................................................................................................13
1.9 Other Precautions.............................................................................................................................................14
2 Commissioning Preparations....................................................................................................16
2.1 Preparing Documents and Tools.......................................................................................................................17
2.2 Preparing a USB Flash Drive...........................................................................................................................18
2.3 Determining the Commissioning Method........................................................................................................18
2.4 Checking Commissioning Conditions..............................................................................................................19
2.4.1 Checking Site Commissioning Conditions..............................................................................................19
2.4.2 Checking System Commissioning Conditions........................................................................................19
3 Commissioning Process.............................................................................................................20
3.1 Site Commissioning Process............................................................................................................................21
3.2 System Commissioning Process.......................................................................................................................23
4 Site Commissioning (Using a USB Flash Drive to Configure Data).................................25

4.2 Loading Commissioning Data Using a USB Flash Drive................................................................................31
4.5 Synchronizing NE Time...................................................................................................................................38
4.6 Checking Alarms..............................................................................................................................................39
5 Site Commissioning (Using the Web LCT to Configure Data)..........................................54

5.4 Configuring Site Commissioning Data.............................................................................................................63
5.4.1 Changing an NE ID.................................................................................................................................66
5.4.2 Setting NE Communication Parameters..................................................................................................66
Issue 02 (2012-12-30)

xviii

Contents
5.4.3 Changing an NE Name............................................................................................................................67

5.4.4 Setting the VLAN ID and Bandwidth for an Inband DCN.....................................................................68
5.4.5 Setting OSPF Protocol Parameters..........................................................................................................69
5.4.6 Creating a LAG.......................................................................................................................................70
5.4.7 Creating a Microwave 1+1 Protection Group..........................................................................................73
5.4.8 Creating a PLA Group.............................................................................................................................74
5.4.9 Configuring a Single Hop of Microwave Link........................................................................................75
5.4.10 Synchronizing NE Time........................................................................................................................77
5.5 Checking Alarms..............................................................................................................................................78
6 System Commissioning..............................................................................................................93
6.1 Configuring Network-wide Service Data.........................................................................................................94
6.2 Testing Ethernet Services.................................................................................................................................94
6.2.1 Testing Ethernet Services Configured on a Per NE Basis.......................................................................94
6.2.2 Testing Ethernet Services Configured in End-to-End Mode...................................................................95
6.3 Testing AM Shifting.........................................................................................................................................97
6.4 Testing Protection Switching............................................................................................................................98
6.4.1 Testing ERPS Switching.........................................................................................................................98
6.4.2 Testing 1+1 Protection Switching.........................................................................................................101
6.4.3 Testing PLA Protection Switching........................................................................................................103
6.5 Checking the Clock Status..............................................................................................................................105
6.6 Testing the Fade Margin over a Microwave Link..........................................................................................105
6.7 Testing Ethernet Service Performance...........................................................................................................107
6.7.1 Testing the Latency, Throughput, and Packet Loss Ratio.....................................................................107
6.7.2 Testing the Long-term Packet Loss Ratio.............................................................................................110
7 Handling of Common Faults During Site Deployment....................................................113

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

8.1 Configuration Preparations.............................................................................................................................118
8.1.1 Preparing Documents and Tools............................................................................................................118
8.1.2 Checking Configuration Conditions......................................................................................................118
8.2 U2000 Quick Start..........................................................................................................................................118
8.3 General Configuration Process.......................................................................................................................118
8.4 Common Configuration Scenarios of Microwave Transmission Networks...................................................120
8.4.1 Microwave Chain Network...................................................................................................................120
8.4.2 Microwave Ring Network.....................................................................................................................122
Issue 02 (2012-12-30)

xix

Contents
8.5 Configuring the Network Topology...............................................................................................................123

8.5.1 Basic Concepts......................................................................................................................................123
8.5.1.1 DCN..............................................................................................................................................123
8.5.1.2 Access Control..............................................................................................................................124
8.5.1.3 GNE and Non-GNE......................................................................................................................126
8.5.1.4 NE ID and NE IP Address............................................................................................................127
8.5.1.5 Fiber/Cable Types.........................................................................................................................127
8.5.1.6 Subnet...........................................................................................................................................128
8.5.2 Configuration Process (Network Topology).........................................................................................128
8.5.3 Configuration Example (Microwave Chain Network Topology)..........................................................135
8.5.4 Configuration Example (Microwave Ring Network Topology)...........................................................140
8.6 Configuring Microwave Links.......................................................................................................................145
8.6.1 Basic Concepts......................................................................................................................................145
8.6.1.1 Adaptive Modulation....................................................................................................................145
8.6.1.2 CCDP and XPIC...........................................................................................................................147
8.6.1.3 RF Configuration Modes..............................................................................................................148
8.6.1.4 PLA...............................................................................................................................................151
8.6.1.5 E-LAG..........................................................................................................................................152
8.6.1.6 Hop Management.........................................................................................................................154
8.6.2 Configuration Process (Microwave Links)............................................................................................155
8.6.3 Configuration Example (Microwave Links on a Microwave Chain Network).....................................162
8.6.4 Configuration Example (Microwave Links on a Microwave Ring Network).......................................171
8.7 Configuring Native Ethernet Services ...........................................................................................................176
8.7.1 Basic Concepts......................................................................................................................................176
8.7.1.1 Auto-negotiation...........................................................................................................................176
8.7.1.2 Flow Control Function..................................................................................................................177
8.7.1.3 Ethernet Port Description.............................................................................................................178
8.7.1.4 MAC Address Table Management...............................................................................................179
8.7.1.5 VLAN Forwarding Tables for E-Line Services............................................................................180
8.7.1.6 Split Horizon Groups....................................................................................................................181
Issue 02 (2012-12-30)

xx

Contents
8.7.1.7 Protection for Native Ethernet Services.......................................................................................181

8.7.2 Native Ethernet Service Types..............................................................................................................183
8.7.2.1 Transparently Transmitted Point-to-Point E-Line Service...........................................................183
8.7.2.2 VLAN-based E-Line Service........................................................................................................185
8.7.2.3 IEEE 802.1D Bridge-based E-LAN Services...............................................................................186
8.7.2.4 IEEE 802.1Q Bridge-based E-LAN Services...............................................................................187
8.7.3 Typical Mobile Bearer Network Topologies for Ethernet Services......................................................188
8.7.3.1 Networking of VLAN-based E-Line Services..............................................................................188
8.7.3.2 Networking of IEEE 802.1D Bridge-based E-LAN Services......................................................189
8.7.3.3 Networking of IEEE 802.1Q Bridge-based E-LAN Services......................................................190
8.7.3.4 Comparison Between the Three Networking Modes...................................................................191
8.7.4 Configuration Process............................................................................................................................194
8.7.4.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point E-Line Services)
..................................................................................................................................................................195
8.7.4.2 End-to-End Configuration Process (Transparently Transmitted Point-to-Point E-Line Services)
..................................................................................................................................................................201
8.7.4.3 Per-NE Configuration Process (VLAN-based E-Line Services)..................................................205
8.7.4.4 End-to-End Configuration Process (VLAN-based E-Line Services)...........................................213
8.7.4.5 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)...........................218
8.7.4.6 End-to-End Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)....................227
8.7.4.7 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)...........................231
8.7.4.8 End-to-End Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)....................240
8.7.5 Configuration Example (Transparently Transmitted Point-to-Point E-Line Services).........................245
8.7.5.2 Service Planning (Port Information).............................................................................................246
8.7.5.10 End-to-End Configuration Procedure.........................................................................................254
8.7.6 Configuration Example (VLAN-based E-Line Service).......................................................................254
Issue 02 (2012-12-30)

xxi

Contents

8.7.6.13 End-to-End Configuration Procedure (Ethernet Service Verification)......................................277
8.7.7 Configuration Example (IEEE 802.1D Bridge-based E-LAN Service)................................................278
8.7.8 Configuration Example (IEEE 802.1Q Bridge-based E-LAN Service)................................................302
8.8 Configuring Clocks.........................................................................................................................................327
8.8.1 Basic Concepts......................................................................................................................................327
8.8.1.1 Clock Source.................................................................................................................................327
8.8.1.2 Clock Protection Modes...............................................................................................................328
8.8.1.3 Clock Synchronization Policy......................................................................................................333
8.8.2 Configuration Process (Configuring a Clock).......................................................................................337
8.8.3 Configuration Example (Clock on a Microwave Chain Network)........................................................339
Issue 02 (2012-12-30)

xxii

Contents

8.8.4 Configuration Example (Clock on a Microwave Ring Network)..........................................................342
8.9 Adding and Modifying Configuration Data...................................................................................................345
8.9.1 Common Task Collection (Network Topology)....................................................................................345
8.9.2 Common Task Collection (Microwave Links)......................................................................................346
8.9.3 Common Task Collection (Ethernet Services)......................................................................................348
A Task Collection.........................................................................................................................351
A.1 U2000 Quick Start.........................................................................................................................................352
A.1.1 Logging In to a U2000 Client...............................................................................................................352
A.1.2 Shutting Down a U2000 Client.............................................................................................................352
A.1.3 Using the Help......................................................................................................................................353
A.1.4 Navigating to Common Views.............................................................................................................354
A.1.4.1 Navigating to Main Topology.....................................................................................................354
A.1.4.2 Navigating to NE Explorer..........................................................................................................355
A.1.4.3 Navigating to the NE Panel.........................................................................................................356
A.2 Web LCT Quick Start....................................................................................................................................357
A.2.1 Connecting the Web LCT to the Equipment........................................................................................357
A.2.2 Using the Help......................................................................................................................................360
A.2.3 Navigating to NE Explorer...................................................................................................................361
A.3 Network Management...................................................................................................................................362
A.3.1 Managing NEs......................................................................................................................................362
A.3.1.1 Creating an NE by Using the Search Method..............................................................................362
A.3.1.2 Creating an NE Manually............................................................................................................364
A.3.1.3 Logging In to an NE....................................................................................................................365
A.3.1.4 Changing an NE ID.....................................................................................................................366
A.3.1.5 Changing an NE Name................................................................................................................367
A.3.1.6 Synchronizing the NE Time........................................................................................................368
A.3.1.7 Localizing the NE Time...............................................................................................................370
A.3.1.8 Configuring a Standard NTP Key................................................................................................371
A.3.2 Configuring NE Data............................................................................................................................372
A.3.2.1 Uploading NE Data......................................................................................................................373
A.3.2.2 Synchronizing NE Data...............................................................................................................374
A.3.3 Setting the Performance Monitoring Status for an NE.........................................................................375
A.3.4 Creating a Fiber/Cable..........................................................................................................................376
A.3.4.1 Creating a Fiber/Cable by Using the Search Method..................................................................376
A.3.4.2 Creating a Fiber/Cable Manually.................................................................................................377
A.3.4.3 Creating an Extended ECC Connection......................................................................................378
A.3.4.4 Creating a Back-to-back Radio Connection................................................................................379
A.3.5 Managing Subnets................................................................................................................................380
Issue 02 (2012-12-30)

xxiii

Contents
A.3.5.1 Creating a Subnet.........................................................................................................................380

A.3.5.2 Copying a Topology Object.........................................................................................................381
A.3.5.3 Moving a Topology Object..........................................................................................................382
A.3.6 Managing Communication...................................................................................................................383
A.3.6.1 Setting NE Communication Parameters......................................................................................383
A.3.6.2 Configuring DCCs.......................................................................................................................384
A.3.6.3 Setting the VLAN ID and Bandwidth for an Inband DCN.........................................................385
A.3.6.4 Configuring the Priorities of Inband DCN Packets.....................................................................386
A.3.6.5 Setting a Port for an Inband DCN................................................................................................387
A.3.6.6 Configuring Access Control........................................................................................................389
A.3.6.7 Configuring Extended ECCs.......................................................................................................390
A.3.6.8 Creating a Static IP Route............................................................................................................392
A.3.6.9 Setting OSPF Protocol Parameters..............................................................................................393
A.3.6.10 Creating an OSPF Area.............................................................................................................394
A.3.6.11 Configuring the Network Information of an ABR....................................................................395
A.3.6.12 Creating a Manual Route Aggregation Group...........................................................................397
A.3.6.13 Configuring Port IP Addresses for an ABR..............................................................................398
A.3.6.14 Configuring the OSPF Authentication Type.............................................................................399
A.3.6.15 Enabling the Proxy ARP............................................................................................................401
A.3.6.16 Querying ECC Routes...............................................................................................................402
A.3.6.17 Querying IP Routes....................................................................................................................403
A.3.6.18 Verifying Connectivity of an ECC Network.............................................................................404
A.3.6.19 Verifying Connectivity of an IP DCN Network........................................................................405
A.3.6.20 Setting SNMP Communication Parameters...............................................................................407
A.3.6.21 Configuring the Active and Standby Gateway NEs..................................................................408
A.3.7 Configuring the NMS Port on an NE...................................................................................................409
A.4 Security Management....................................................................................................................................410
A.4.1 Configuring an NE User.......................................................................................................................410
A.4.1.1 Creating an NE User....................................................................................................................410
A.4.1.2 Changing the Password of an NE User........................................................................................412
A.4.1.3 Setting the Warning Screen Parameters.......................................................................................412
A.4.1.4 Switching NE Users.....................................................................................................................413
A.4.2 Configuring Web LCT Access to an NE..............................................................................................414
A.4.3 Configuring an Access Control List for an NE....................................................................................415
A.4.3.1 Creating Basic ACL Rules...........................................................................................................415
A.4.3.2 Creating Advanced ACL Rules...................................................................................................416
A.4.4 Querying NE Operation Logs...............................................................................................................417
A.4.5 Querying Operation Logs Sent to Syslog Servers................................................................................418
A.4.6 Configuring Syslog...............................................................................................................................419
A.4.6.1 Enabling the Syslog Service........................................................................................................419
A.4.6.2 Setting Types and Severities of Logs to Be Sent to Syslog Servers............................................419
A.4.6.3 Configuring Syslog Servers.........................................................................................................420
Issue 02 (2012-12-30)

xxiv

Contents
A.4.6.4 Configuring Gateway NEs for Communication Between NEs and Syslog Servers....................421
A.4.7 Configuring File Transfer Protocols.....................................................................................................422
A.4.8 Configuring SSL Protocol Communication..........................................................................................423
A.4.8.1 Configuring SSL Protocol Communication Between a U2000 Server and Its Clients...............423
A.4.8.2 Configuring the Connection Mode Between the U2000 and Its Gateway NE............................424
A.4.9 Configuring RADIUS Authentication..................................................................................................425
A.4.9.1 Enabling/Disabling the RADIUS Authentication Function........................................................426
A.4.9.2 Creating a RADIUS Server or a RADIUS Proxy Server............................................................426
A.4.9.3 Configuring RADIUS Server Parameters....................................................................................428
A.5 Managing Microwave Links..........................................................................................................................430
A.5.1 Configuring a Single Hop of Microwave Link.....................................................................................430
A.5.2 Browsing the Performance of a Hop of Microwave Link....................................................................432
A.5.3 Creating a Microwave 1+1 Protection Group.......................................................................................433
A.5.4 Microwave 1+1 Protection Switching..................................................................................................435
A.5.5 Querying the Microwave 1+1 Protection Status...................................................................................436
A.5.6 Creating a PLA Group..........................................................................................................................436
A.5.7 Querying the Status of a PLA Group....................................................................................................438
A.5.8 Configuring Ethernet Frame Header Compression and Errored Frame Discarding Over Air Interfaces
........................................................................................................................................................................438
A.5.9 Enabling the Notification of Radio Bandwidth....................................................................................439
A.5.10 Setting the Maximum Transmit Power and the Power Thresholds....................................................440
A.5.11 Querying the AM Status.....................................................................................................................441
A.5.12 Querying ATPC Adjustment Records................................................................................................442
A.5.13 Querying Historical Transmit Power and Receive Power..................................................................443
A.5.14 Querying the SNR Value of a Microwave Link.................................................................................444
A.6 Managing Ports..............................................................................................................................................445
A.6.1 Setting Parameters for an Ethernet Port................................................................................................445
A.6.1.1 Setting the Basic Attributes for an Ethernet Port.........................................................................445
A.6.1.2 Configuring the Traffic Control Function for an Ethernet Port...................................................446
A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port.....................................................................447
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port.................................................................449
A.6.1.5 Querying the Running Status of a Microwave Port.....................................................................450
A.6.2 Setting Parameters for a Microwave Port.............................................................................................451
A.6.2.1 Setting Basic Attributes for a Microwave Port............................................................................451
A.6.2.2 Setting Layer 2 Attributes for a Microwave Port........................................................................452
A.6.2.3 Setting Advanced Attributes for a Microwave Port....................................................................453
A.6.2.4 Querying the Running Status of an Ethernet Port.......................................................................454
A.7 Managing Ethernet Services and Features.....................................................................................................455
A.7.1 Managing ERPS....................................................................................................................................455
A.7.1.1 Creating an ERP Instance............................................................................................................455
A.7.1.2 Setting ERPS Protocol Parameters..............................................................................................457
A.7.1.3 Querying the ERPS Status...........................................................................................................458
A.7.2 Managing LAGs...................................................................................................................................458
Issue 02 (2012-12-30)

xxv

Contents
A.7.2.1 Creating a LAG............................................................................................................................458

A.7.2.2 Setting Parameters for a LAG......................................................................................................461
A.7.2.3 Querying the Protocol Information About a LAG.......................................................................462
A.7.3 Configuring Ethernet Services..............................................................................................................463
A.7.3.1 Creating a Point-to-Point Transparently Transmitted E-Line Service.........................................463
A.7.3.2 Creating a VLAN-based E-Line Service.....................................................................................464
A.7.3.3 Creating an E-Line Service for Transmitting Layer 2 Protocol Packets.....................................465
A.7.3.4 Creating VLAN Forwarding Table Entries.................................................................................467
A.7.3.5 Creating an IEEE 802.1D Bridge-based E-LAN Service............................................................468
A.7.3.6 Creating an IEEE 802.1Q Bridge-based E-LAN Service............................................................469
A.7.3.7 Creating an E-LAN Service for Transmitting Layer 2 Protocol Packets....................................470
A.7.3.8 Configuring a Split Horizon Group.............................................................................................472
A.7.3.9 Changing Logical Ports Mounted to a Bridge.............................................................................473
A.7.3.10 Deleting an E-Line Service........................................................................................................473
A.7.3.11 Deleting an E-LAN Service.......................................................................................................474
A.7.4 Managing MAC Address Tables..........................................................................................................475
A.7.4.1 Creating a Static MAC Address Entry.........................................................................................475
A.7.4.2 Creating a Blacklist MAC Address Entry...................................................................................476
A.7.4.3 Managing a Dynamic MAC Address Table................................................................................477
A.7.5 Setting the Mode for Processing an Unknown Frame of an E-LAN Service.......................................478
A.7.6 Managing QoS......................................................................................................................................479
A.7.6.1 Modifying the Mapping for a DS Domain..................................................................................479
A.7.6.2 Changing the Packet Type Trusted by a Port..............................................................................481
A.7.6.3 Configuring Port Shaping............................................................................................................482
A.7.6.4 Setting Egress Queue Scheduling Policies..................................................................................483
A.7.6.5 Setting Traffic Shaping for Egress Queues.................................................................................484
A.7.6.6 Setting the Congestion Management Mode for Egress Queues..................................................485
A.7.7 Using Ethernet Service OAM...............................................................................................................487
A.7.7.1 Creating an MD...........................................................................................................................487
A.7.7.2 Creating an MA...........................................................................................................................488
A.7.7.3 Creating an MEP..........................................................................................................................489
A.7.7.4 Creating a Remote MEP in an MA..............................................................................................490
A.7.7.5 Creating an MIP...........................................................................................................................491
A.7.7.6 Performing a CC Test..................................................................................................................492
A.7.7.7 Performing an LB Test................................................................................................................493
A.7.7.8 Performing an LT Test.................................................................................................................495
A.7.7.9 Activating the AIS.......................................................................................................................496
A.7.7.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services......................497
A.7.7.11 Performing E-LAN Service Loopback Detection......................................................................499
A.7.7.12 Reactivating an E-LAN Service................................................................................................500
A.7.8 Using Ethernet Port OAM....................................................................................................................501
A.7.8.1 Enabling OAM Auto-discovery...................................................................................................501
Issue 02 (2012-12-30)

xxvi

Contents
A.7.8.2 Enabling the Link Event Notification..........................................................................................502

A.7.8.3 Changing the OAM Errored Frame Monitoring Threshold.........................................................503
A.7.8.4 Performing a Remote Loopback..................................................................................................504
A.7.8.5 Enabling Self-loop Detection......................................................................................................506
A.7.9 Configuring LPT...................................................................................................................................507
A.8 Managing Clocks...........................................................................................................................................508
A.8.1 Managing Clocks at the Physical Layer...............................................................................................508
A.8.1.1 Changing the Clock Control Mode..............................................................................................508
A.8.1.2 Configuring Clock Sources..........................................................................................................509
A.8.1.3 Configuring Protection for Clock Sources..................................................................................510
A.8.1.4 Customizing the Clock Quality...................................................................................................512
A.8.1.5 Enabling/Disabling SSM Transmission.......................................................................................513
A.8.1.6 Enabling/Disabling the Output of Clock Source IDs..................................................................514
A.8.1.7 Modifying Clock Source Reversion Parameters..........................................................................514
A.8.1.8 Querying the Clock Synchronization Status................................................................................515
A.8.2 Managing the IEEE 1588v2 Clock.......................................................................................................516
A.8.2.1 Enabling/Disabling the IEEE-1588 Timeslot for a Microwave Port...........................................516
A.8.2.2 Querying or Modifying the PTP System Time............................................................................517
A.8.2.3 Setting the PTP NE Attributes.....................................................................................................518
A.8.2.4 Creating a PTP Clock Port...........................................................................................................519
A.8.2.5 Setting PTP Clock Port Attributes...............................................................................................520
A.8.2.6 Setting Parameters for IEEE 1588v2 Clock Packets...................................................................522
A.8.2.7 Configuring the Delay Offset for Asymmetric Transmission Between NEs...............................524
A.8.2.8 Configuring the Cascade Fiber Length for a 1+1 Protection Group...........................................525
A.8.2.9 Configuring a PTP Clock Subnet................................................................................................526
A.8.2.10 Modifying the BMC Algorithm Parameters for an NE Clock...................................................527
A.9 Using RMON.................................................................................................................................................528
A.9.1 Browsing Current Performance Events of Ethernet.............................................................................528
A.9.2 Setting the Ethernet Performance Threshold-Crossing Parameter.......................................................529
A.9.3 Configuring the Parameters for Ethernet Historical Performance Monitoring.....................................530
A.9.4 Browsing Ethernet Historical Performance Data..................................................................................531
A.10 Configuring a Native Ethernet Service (in End-to-End Mode)...................................................................532
A.10.1 Searching for Native Ethernet Services..............................................................................................532
A.10.2 Creating a Point-to-Point Transparently Transmitted E-Line Service................................................533
A.10.3 Creating a VLAN-based E-Line Service............................................................................................534
A.10.4 Creating an IEEE 802.1D Bridge-based E-LAN Service...................................................................535
A.10.5 Creating an IEEE 802.1Q Bridge-based E-LAN Service...................................................................537
A.10.6 Verifying a Native Ethernet Service...................................................................................................539
A.10.7 Managing Native Ethernet Services...................................................................................................541
A.10.8 Managing Discrete Native Ethernet Services ....................................................................................542
A.10.9 Adjusting an E-LAN Service Network...............................................................................................543
A.11 Verifying Services and Features..................................................................................................................544
Issue 02 (2012-12-30)

xxvii

Contents
A.11.1 Testing Ethernet Services...................................................................................................................544

A.11.1.1 Testing Ethernet Services Configured on a Per NE Basis.........................................................544
A.11.1.2 Testing Ethernet Services Configured in End-to-End Mode.....................................................546
A.11.2 Testing AM Shifting...........................................................................................................................547
A.11.3 Testing Protection Switching..............................................................................................................548
A.11.3.1 Testing ERPS Switching............................................................................................................548
A.11.3.2 Testing 1+1 Protection Switching.............................................................................................551
A.11.3.3 Testing PLA Protection Switching............................................................................................553
B Parameters Description............................................................................................................556
B.1 Parameters for Network Management...........................................................................................................557
B.1.1 Parameters for NE Management...........................................................................................................557
B.1.1.1 Parameter Description: NE Searching.........................................................................................557
B.1.1.2 Parameter Description: NE Creation...........................................................................................560
B.1.1.3 Parameter Description: NE Time Synchronization (U2000).......................................................562
B.1.1.4 Parameter Description: Standard NTP Key Management...........................................................565
B.1.1.5 Parameter Description: Localization Management of the NE Time............................................566
B.1.2 Parameters for Communications Management.....................................................................................567
B.1.2.1 Parameter Description: NE Communication Parameter Setting..................................................567
B.1.2.2 Parameter Description: ECC Management_Ethernet Port Extended ECC..................................569
B.1.2.3 Parameter Description: NE ECC Link Management...................................................................570
B.1.2.4 Parameter Description: ECC Link Management_Availability Test............................................571
B.1.2.5 Parameter Description: Access Control.......................................................................................572
B.1.2.6 Parameter Description: DCC Management_DCC Rate Configuration........................................574
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management........................575
B.1.2.8 Parameter Description: IP Protocol Stack Management_Availability Test.................................576
B.1.2.9 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings...................577
B.1.2.10 Parameter Description: IP Protocol Stack_Proxy ARP.............................................................582
B.1.2.11 Parameter Description: Management of Multiple OSPF Areas.................................................583
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas..............584
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be Manually
Aggregated................................................................................................................................................586
B.1.2.14 Parameter Description: Port OSPF Setting................................................................................586
B.1.2.15 Parameter Description: DCN Management_Bandwidth Management......................................586
B.1.2.16 Parameter Description: DCN Management_Port Setting..........................................................587
B.1.2.17 Parameter Description: DCN Management_Access Control.....................................................588
B.1.2.18 Parameter Description: DCN Management_Packet Control.....................................................589
B.1.2.19 Parameter Description: SNMP Communications Parameters Setting.......................................590
B.1.3 Parameters for RADIUS.......................................................................................................................590
B.1.3.1 Parameter Description: RADIUS Configuration_Creation.........................................................591
B.1.3.2 Parameter Description: Enabling/Disabling the RADIUS Function...........................................592
B.2 Radio Link Parameters...................................................................................................................................592
B.2.1 Parameter Description: IF 1+1 Protection Group.................................................................................592
Issue 02 (2012-12-30)

xxviii

Contents
B.2.2 Parameter Description: PLA Group Creation.......................................................................................596

B.2.3 Parameters Description: Radio Link Configuration.............................................................................597
B.3 Parameters for Board Interfaces.....................................................................................................................603
B.3.1 Parameters for the Ports on Ethernet Boards........................................................................................603
B.3.1.1 Parameter Description: Ethernet Interface_Basic Attributes.......................................................603
B.3.1.2 Parameter Description: Ethernet Interface_Flow Control...........................................................606
B.3.1.3 Parameter Description: Ethernet Interface_Layer 2 Attributes....................................................608
B.3.1.4 Parameter Description: Ethernet Interface_Advanced Attributes................................................610
B.3.2 Microwave Interface Parameters..........................................................................................................613
B.3.2.1 Parameter Description: Microwave Interface_Basic Attributes..................................................613
B.3.2.2 Parameter Description: Microwave Interface_Layer 2 Attributes...............................................614
B.3.2.3 Parameter Description: Microwave Interface_Advanced Attributes...........................................615
B.4 Parameters for Ethernet Services and Ethernet Features...............................................................................617
B.4.1 Parameters for Ethernet Services..........................................................................................................617
B.4.1.1 Parameter Description: E-Line Service........................................................................................617
B.4.1.2 Parameter Description: E-LAN Service.......................................................................................622
B.4.2 Parameters for Ethernet Protocols........................................................................................................633
B.4.2.1 Parameter Description: ERPS Management................................................................................633
B.4.2.2 Parameter Description: Ethernet Link Aggregation Management...............................................639
B.4.2.3 Parameter Description: Ethernet Link Aggregation_Link Aggregation......................................646
B.4.2.4 Parameter Description: Simplified LPT Creation........................................................................647
B.4.3 Parameters for the Ethernet OAM........................................................................................................648
B.4.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation
..................................................................................................................................................................648
B.4.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation
..................................................................................................................................................................649
B.4.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation............................650
B.4.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation..............651
B.4.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation.............................652
B.4.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling..............................653
B.4.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling...............................654
B.4.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback Detection............655
B.4.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter..............................656
B.4.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
..................................................................................................................................................................658
B.4.4 Parameter Description: QoS Management............................................................................................660
B.5 RMON Parameters.........................................................................................................................................668
B.5.1 Parameter Description: RMON Performance_Statistics Group............................................................668
B.5.2 Parameter Description: RMON Performance_History Group..............................................................669
B.5.3 Parameter Description: RMON Performance_RMON Setting.............................................................670
B.6 Clock Parameters...........................................................................................................................................671
B.6.1 Physical-Layer Clock Parameters.........................................................................................................671
B.6.1.1 Parameter Description: Clock Synchronization Status................................................................672
Issue 02 (2012-12-30)

xxix

Contents
B.6.1.2 Parameter Description: Clock Source Priority Table...................................................................673

B.6.1.3 Parameter Description: Clock Source Switching_Clock Source Switching................................674
B.6.1.4 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters...........675
B.6.1.5 Parameter Description: Clock Subnet Setting_Clock Subnet......................................................677
B.6.1.6 Parameter Description: Clock Subnet Setting_Clock Quality.....................................................680
B.6.1.7 Parameter Description: Clock Subset Setting_SSM Output Control...........................................683
B.6.1.8 Parameter Description: Clock Subset Setting_Clock ID Enabling Status...................................684
B.7 PTP Clock Parameters...................................................................................................................................685
B.7.1 Parameter Description: Clock Synchronization Attribute....................................................................685
B.7.2 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet................................................696
B.7.3 Parameter Description: Setting of a PTP Clock Subnet_Port_BMC....................................................696
C Glossary......................................................................................................................................699
Issue 02 (2012-12-30)

xxx

Figures
Figures
Figure 1-1 Hoisting heavy objects.........................................................................................................................11
Figure 1-2 Slanting a ladder..................................................................................................................................12
Figure 1-3 Ladder top being one meter higher than the roof.................................................................................12
Figure 4-1 Ways for connecting the Web LCT to an OptiX RTN 310.................................................................35
Figure 4-2 Main lobe and side lobes......................................................................................................................40
Figure 4-3 Horizontal section and front view of the antenna................................................................................41
Figure 4-4 Three tracking paths.............................................................................................................................42
Figure 4-5 Aligning the antenna with the first side lobe.......................................................................................42
Figure 4-6 Testing the RSSI voltage using a multimeter......................................................................................44
Figure 4-7 Signal peaks.........................................................................................................................................45
Figure 5-1 Ways for connecting the Web LCT to an OptiX RTN 310.................................................................60
Figure 5-2 Configuration flowchart.......................................................................................................................64
Figure 5-3 Main lobe and side lobes......................................................................................................................79
Figure 5-4 Horizontal section and front view of the antenna................................................................................80
Figure 5-5 Three tracking paths.............................................................................................................................81
Figure 5-6 Aligning the antenna with the first side lobe.......................................................................................81
Figure 5-7 Testing the RSSI voltage using a multimeter......................................................................................83
Figure 5-8 Signal peaks.........................................................................................................................................84
Figure 6-1 Connection diagram for testing Ethernet services...............................................................................94
Figure 6-2 Connection diagram for testing Ethernet services...............................................................................96
Figure 6-3 Configuration for testing ERPS...........................................................................................................99
Figure 6-4 Test connection diagram....................................................................................................................102
Figure 8-1 Flowchart for initial configuration.....................................................................................................119
Figure 8-2 Networking diagram of a microwave chain network.........................................................................121
Figure 8-3 Networking diagram of a microwave ring network...........................................................................122
Figure 8-4 Application of the IP DCN solution...................................................................................................124
Figure 8-5 Access control (OptiX RTN 310 connecting to an NMS through a third-party service network)
..............................................................................................................................................................................125
Figure 8-6 Access control (OptiX RTN 310 connecting to a Web LCT through its GE port)............................126
Figure 8-7 Flowchart for configuring the network topology...............................................................................129
Figure 8-8 Networking diagram (microwave chain network topology)..............................................................136
Issue 02 (2012-12-30)

xxxi

Figures
Figure 8-9 Allocated IDs and IP addresses (microwave chain network)............................................................137

Figure 8-10 Networking diagram (microwave ring network topology)..............................................................141
Figure 8-11 Allocated IDs and IP addresses (microwave ring network).............................................................142
Figure 8-12 Adaptive modulation........................................................................................................................146
Figure 8-13 Single-polarized transmission..........................................................................................................147
Figure 8-14 CCDP transmission..........................................................................................................................147
Figure 8-15 Typical configuration of 1+0 non-protection...................................................................................148
Figure 8-16 Typical configuration of 1+1 HSB protection.................................................................................149
Figure 8-17 Typical configuration of 1+1 FD protection....................................................................................149
Figure 8-18 Typical configuration of 1+1 SD protection....................................................................................150
Figure 8-19 Typical configuration of 2+0 non-protection (with PLA configured with NE-level protection)
..............................................................................................................................................................................150
Figure 8-20 Typical configuration of the XPIC..................................................................................................151
Figure 8-21 PLA..................................................................................................................................................151
Figure 8-22 E-LAG application...........................................................................................................................152
Figure 8-23 Before E-LAG switching.................................................................................................................153
Figure 8-24 E-LAG switching.............................................................................................................................154
Figure 8-25 Flowchart for configuring microwave links.....................................................................................156
Figure 8-26 Networking diagram (microwave links on a microwave chain network)........................................164
Figure 8-27 Networking diagram (microwave links on a microwave ring network)..........................................172
Figure 8-28 Ethernet ports on an OptiX RTN 310..............................................................................................178
Figure 8-29 Application of the VLAN forwarding table for an E-Line service (on NE 2).................................180
Figure 8-30 Split horizon group..........................................................................................................................181
Figure 8-31 Implementation of ERPS.................................................................................................................182
Figure 8-32 LAG.................................................................................................................................................183
Figure 8-33 Typical application of service model 1............................................................................................184
Figure 8-34 VLAN-based E-Line service model.................................................................................................186
Figure 8-35 IEEE 802.1D bridge-based E-LAN service model..........................................................................187
Figure 8-36 IEEE 802.1Q bridge-based E-LAN service model..........................................................................188
Figure 8-37 Networking diagram of VLAN-based E-Line services....................................................................189
Figure 8-38 Networking diagram (IEEE 802.1D bridge-based E-LAN services)...............................................190
Figure 8-39 Networking diagram of IEEE 802.1Q bridge-based E-LAN services.............................................191
Figure 8-40 Flowchart for configuring transparently transmitted point-to-point E-Line services......................195
Figure 8-41 Flowchart for configuring transparently transmitted point-to-point E-Line services......................201
Figure 8-42 Flowchart for configuring VLAN-based E-Line services................................................................206
Figure 8-43 Flowchart for configuring VLAN-based E-Line services................................................................213
Figure 8-44 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services.........................................219
Figure 8-45 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services.........................................227
Figure 8-46 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services.........................................232
Figure 8-47 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services.........................................241
Figure 8-48 Networking diagram (transparently transmitted point-to-point E-Line services)............................245
Figure 8-49 Networking diagram (VLAN-based E-Line services).....................................................................255
Figure 8-50 Information about VLAN-based E-Line services............................................................................258
Issue 02 (2012-12-30)

xxxii

Figures
Figure 8-51 Networking diagram (IEEE 802.1D bridge-based E-LAN services)...............................................279

Figure 8-52 Networking diagram (IEEE 802.1Q bridge-based E-LAN services)...............................................303
Figure 8-53 Clock source protection based on priorities.....................................................................................328
Figure 8-54 SSM protection................................................................................................................................330
Figure 8-55 Extended SSM protection................................................................................................................333
Figure 8-56 Clock synchronization policy for a chain network..........................................................................334
Figure 8-57 Clock synchronization policy for a ring network.............................................................................336
Figure 8-58 Flowchart for configuring a clock....................................................................................................337
Figure 8-59 Networking diagram (clocks on a microwave chain network)........................................................340
Figure 8-60 Networking diagram (clocks on a microwave chain network)........................................................341
Figure 8-61 Networking diagram (clocks on a microwave ring network)..........................................................343
Figure 8-62 Networking diagram (clocks on a microwave ring network)..........................................................344
Figure A-1 Ways for connecting the Web LCT to an OptiX RTN 310...............................................................358
Figure A-2 Connection diagram for testing Ethernet services............................................................................545
Figure A-3 Connection diagram for testing Ethernet services............................................................................546
Figure A-4 Configuration for testing ERPS........................................................................................................549
Figure A-5 Test connection diagram...................................................................................................................552
Figure A-6 Test connection diagram...................................................................................................................554
Issue 02 (2012-12-30)

xxxiii

Tables
Tables
Table 1-1 Warning and safety symbols of the OptiX RTN 310..............................................................................3
Table 2-1 Tools......................................................................................................................................................17
Table 3-1 Configuring site commissioning data using a USB flash drive.............................................................21
Table 3-2 System commissioning items................................................................................................................23
Table 4-1 Fuse capacity.........................................................................................................................................27
Table 5-1 Fuse capacity.........................................................................................................................................55
Table 5-2 Configuration procedure........................................................................................................................65
Table 8-1 Initial configuration.............................................................................................................................119
Table 8-2 Network adjustment.............................................................................................................................120
Table 8-3 Configuration examples.......................................................................................................................121
Table 8-4 Configuration examples.......................................................................................................................123
Table 8-5 Process of creating NEs.......................................................................................................................130
Table 8-6 Process of configuring NE attributes...................................................................................................131
Table 8-7 Process of configuring DCCs..............................................................................................................131
Table 8-8 Process of synchronizing NE time......................................................................................................133
Table 8-9 Process of setting the performance monitoring status.........................................................................134
Table 8-10 Process of creating fibers/cables and subnets....................................................................................134
Table 8-11 Process of configuring microwave links...........................................................................................157
Table 8-12 Service capacity transmitted by each NodeB....................................................................................163
Table 8-13 Common service priorities................................................................................................................163
Table 8-14 Basic information about microwave links.........................................................................................164
Table 8-15 AM attribute information..................................................................................................................165
Table 8-16 Power and ATPC information...........................................................................................................166
Table 8-17 Configuration information about XPIC groups.................................................................................166
Table 8-18 Configuration information about PLA groups..................................................................................167
Table 8-19 Service capacity transmitted by each NodeB....................................................................................171
Table 8-20 Common service priorities................................................................................................................172
Table 8-21 Basic information about microwave links.........................................................................................173
Table 8-22 AM attribute information..................................................................................................................173
Table 8-23 Power and ATPC information...........................................................................................................174
Table 8-24 Auto-negotiation rules for GE electrical ports (when the local GE electrical port works in autonegotiation mode).................................................................................................................................................176
Table 8-25 Mapping between physical ports and logical ports for an OptiX RTN 310......................................178
Table 8-26 Entries in a MAC address table.........................................................................................................179
Issue 02 (2012-12-30)

xxxiv

Tables
Table 8-27 Transparently transmitted point-to-point E-Line service model.......................................................184

Table 8-28 VLAN-based E-Line service model..................................................................................................185
Table 8-29 IEEE 802.1D bridge-based E-LAN service model............................................................................186
Table 8-30 IEEE 802.1Q bridge-based E-LAN service model............................................................................187
Table 8-31 Comparison between the three networking modes............................................................................192
Table 8-32 Process of configuring LAG for Ethernet ports................................................................................196
Table 8-33 Process of configuring transparently transmitted point-to-point E-Line services.............................196
Table 8-34 Process of setting port attributes........................................................................................................197
Table 8-35 Process of configuring QoS...............................................................................................................198
Table 8-36 Process of verifying Ethernet service configurations........................................................................199
Table 8-39 Process of configuring transparently transmitted point-to-point E-Line services.............................203
Table 8-43 Process of configuring VLAN-based E-Line services......................................................................207
Table 8-49 Process of configuring VLAN-based E-Line services......................................................................216
Table 8-53 Process of configuring ERPS protection...........................................................................................221
Table 8-54 Process of configuring IEEE 802.1D bridge-based E-LAN services................................................222
Table 8-60 Process of configuring IEEE 802.1D bridge-based E-LAN services................................................229
Table 8-65 Process of configuring IEEE 802.1Q bridge-based E-LAN services................................................234
Issue 02 (2012-12-30)

xxxv

Tables

Table 8-71 Process of configuring IEEE 802.1Q bridge-based E-LAN services................................................243
Table 8-74 Ethernet port information..................................................................................................................246
Table 8-75 Microwave port information..............................................................................................................246
Table 8-76 Information about a transparently transmitted point-to-point E-Line service...................................247
Table 8-77 PHBs and service types.....................................................................................................................247
Table 8-78 Queue scheduling policies.................................................................................................................248
Table 8-79 Congestion management mode..........................................................................................................249
Table 8-80 Information about Ethernet ports on XPIC links...............................................................................256
Table 8-81 Information about Ethernet ports on non-XPIC links.......................................................................256
Table 8-82 Information about microwave ports on XPIC links..........................................................................257
Table 8-83 Information about microwave ports on non-XPIC links...................................................................257
Table 8-84 Information about VLAN-based E-Line services on XPIC links......................................................258
Table 8-85 Information about VLAN-based E-Line services on non-XPIC links..............................................259
Table 8-89 Ethernet port information..................................................................................................................280
Table 8-90 Microwave port information..............................................................................................................281
Table 8-91 Information about ERP instances......................................................................................................281
Table 8-92 Information About an IEEE 802.1D bridge-based E-LAN service...................................................282
Table 8-96 Information about Ethernet ports on XPIC links...............................................................................304
Table 8-97 Information about Ethernet ports on non-XPIC links.......................................................................304
Table 8-98 Information about microwave ports on XPIC links..........................................................................305
Table 8-99 Information about microwave ports on non-XPIC links...................................................................306
Table 8-100 Information about IEEE 802.1Q bridge-based E-LAN services on XPIC links.............................306
Table 8-101 Information about IEEE 802.1Q bridge-based E-LAN services on non-XPIC links......................307
Table 8-102 PHBs and service types...................................................................................................................308
Table 8-103 Queue scheduling policies...............................................................................................................309
Table 8-104 Congestion management mode........................................................................................................309
Table 8-105 SSM protection................................................................................................................................329
Table 8-106 Extended SSM protection................................................................................................................331
Table 8-107 Process of configuring the clock.....................................................................................................337
Table 8-108 XPIC links.......................................................................................................................................342
Table 8-109 Non-XPIC links...............................................................................................................................342
Table 8-110 Common task collection (NE attributes).........................................................................................346
Issue 02 (2012-12-30)

xxxvi

Tables
Table 8-111 Common task collection (microwave links)....................................................................................347

Table 8-112 Common task collection (Ethernet services)...................................................................................348
Table A-1 Parameters for NE time synchronization............................................................................................368
Table A-2 Parameters for NE time synchronization............................................................................................369
Table A-3 Parameters for the standard NTP server.............................................................................................369
Table A-4 Authentication Type...........................................................................................................................400
Table A-5 Authentication Password....................................................................................................................400
Table A-6 SNMP plan.........................................................................................................................................407
Table A-7 Basic parameters for an IEEE 802.1D bridge-based E-LAN service.................................................536
Table A-8 Information about ports mounted to network bridges........................................................................536
Table A-9 Basic parameters for an IEEE 802.1Q bridge-based E-LAN service.................................................538
Table A-10 Information about ports mounted to network bridges......................................................................538
Table B-1 Methods used by Ethernet interfaces to process data frames.............................................................609
Table B-2 Data frame processing........................................................................................................................615
Issue 02 (2012-12-30)

xxxvii

1 Safety Precautions
Safety Precautions
About This Chapter

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


1.1 General Safety Precautions

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

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

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

The installation and maintenance personnel of Huawei devices must receive strict training and
be familiar with the proper operation methods and safety precautions before any operation.
l
Only trained and qualified personnel are permitted to install, operate, and maintain a device.
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.
l
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
l
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.
Issue 02 (2012-12-30)


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.
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.
Device Safety
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 310 and their meanings.
Table 1-1 Warning and safety symbols of the OptiX RTN 310
Label
Issue 02 (2012-12-30)
Label Name
Description
ESD protection label
Indicates that the equipment is

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

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

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

of a chassis.


1.3 Electrical Safety

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


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

This topic describes safety precautions for the operating environment of a device.
Issue 02 (2012-12-30)


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

This topic describes safety precautions for operations of storage batteries.
DANGER
Before operating a storage battery, you must read the safety precautions carefully and be familiar
with the method of connecting a storage battery.
l
Incorrect operations of storage batteries cause hazards. During operation, prevent any shortcircuit, 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:
l
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.
Issue 02 (2012-12-30)


Hazardous Gas
CAUTION
Do not use any unsealed lead-acid storage battery. Lay a storage battery horizontally and fix it
properly to prevent the battery from emitting flammable gas, which may cause fire or device
erosion.
Working lead-acid storage batteries emit flammable gas. Therefore, ventilation and fireproofing
measures must be taken at the sites where lead-acid storage batteries are placed.
Battery Temperature
CAUTION
If a battery overheats, the battery may be deformed or damaged, and the electrolyte may
overflow.
When the temperature of the battery is higher than 60C, you need to check whether the
electrolyte overflows. If the electrolyte overflows, take appropriate measures immediately.
Battery Leakage
CAUTION
In the event of acid overflow or spillage, neutralize the acid and clean it up appropriately.
When handling a leaky battery, protect against the possible damage caused by the acid. When
you find the electrolyte leaks, you can use the following substances to counteract and absorb the
leaking electrolyte:
l
Sodium bicarbonate (NaHCO3)
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.
Issue 02 (2012-12-30)


1.6.1 Safe Usage of Optical Fibers

The laser beam can cause damage to your eyes. Hence, you must exercise caution when using
optical fibers.
DANGER
When installing or maintaining optical fibers, avoid direct eye exposure to the laser beams
launched from the optical interface or fiber connectors. The laser beam can cause damage to
your eyes.
Cleaning Fiber Connectors and Optical Interfaces
CAUTION
If fiber connectors or flanges are contaminated, optical power commissioning is seriously
affected. Therefore, the two endfaces and flange of every external fiber must be cleaned before
the fiber is led into the equipment through the optical distribution frame (ODF) for being inserted
into an optical interface on the equipment.
The fiber connectors and optical interfaces of the lasers must be cleaned with the following
special cleaning tools and materials:
l
Special cleaning solvent: It is preferred to use isoamylol. Propyl alcohol, however, can also
be used. It is prohibited that you use alcohol and formalin.
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.
CAUTION
Ensure that all personnel are beyond the transmit direction of a working antenna.
1.6.3 Forbidden Areas

The topic describes requirements for a forbidden area.
Issue 02 (2012-12-30)


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.
WARNING
When handling optical fibers, do not stand close to, or look into the optical fiber outlet directly
without eye protection.
Laser transceivers are used in the optical transmission system and associated test tools. The laser
transmitted through the bare optical fiber produces a small beam of light, and therefore it has
very high power density and is invisible to human eyes. When a beam of light enters eyes, the
eyes may be damaged.
In normal cases, viewing an un-terminated optical fiber or a damaged optical fiber without eye
protection at a distance greater than 150 mm does not cause eye injury. Eye injury may occur,
however, if an optical tool such as a microscope, magnifying glass, or eye loupe is used to view
an un-terminated optical fiber.
Safety Instructions Regarding Lasers

To avoid laser radiation, obey the following instructions:
l
All operations should be performed by authorized personnel who have completed the
required training courses.
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:
l
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.
Issue 02 (2012-12-30)


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

This topic describes safety precautions for working at heights.
WARNING
When working at heights, be cautious to prevent objects from falling down.
The requirements for working at heights are as follows:
l
The personnel who work at heights must be trained.
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.
WARNING
When heavy objects are being hoisted, do not walk below the cantilever or hoisted objects.
l
Only trained and qualified personnel can perform hoisting operations.
Before hoisting heavy objects, check that the hoisting tools are complete and in good
condition.
Issue 02 (2012-12-30)

10

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
l
Before using a ladder, check whether the ladder is damaged. After checking that the ladder
is in good condition, you can use the ladder.
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
Issue 02 (2012-12-30)

11

ladder from sliding, ensure that the wider feet of the ladder are downward, or take protection
measures for the ladder feet. Ensure that the ladder is placed securely.
Figure 1-2 Slanting a ladder
Climbing Up a Ladder
When climbing up a ladder, pay attention to the following points:
l
Ensure that the center of gravity of your body does not deviate from the edges of the two
long sides.
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
Issue 02 (2012-12-30)

12

1.8 Mechanical Safety

This topic describes safety precautions for drilling holes, handling sharp objects, operating fans,
and carrying heavy objects.
Drilling Holes
WARNING
Do not drill holes on the cabinet without prior permission. Drilling holes without complying
with the requirements affects the electromagnetic shielding performance of the cabinet and
damages the cables inside the cabinet. In addition, if the scraps caused by drilling enter the
cabinet, the printed circuit boards (PCBs) may be short-circuited.
l
Before drilling a hole on the cabinet, remove the cables inside the cabinet.
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
WARNING
Wear protection gloves when carrying the device. This is to prevent hands from being injured
by the sharp edges of the device.
Fans
l
When replacing parts, place the objects such as the parts, screws, and tools properly. This
is to prevent them from falling into the operating fans, which damages the fans or device.
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.
Issue 02 (2012-12-30)

13

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

This topic describes safety precautions for removing and inserting boards, binding signal cables,
and routing cables.
Removing and Inserting a Board
CAUTION
When inserting a board, wear an ESD wrist strap or ESD gloves, and handle the board gently to
avoid distorting pins on the backplane.
l
Slide the board along the guide rails.
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
CAUTION
Bind the signal cables separately from the high-current or high-voltage cables.
Routing Cables
In the case of extremely low temperature, heavy shock or vibration may damage the plastic skin
of the cables. To ensure the construction safety, comply with the following requirements:
Issue 02 (2012-12-30)

14

When installing cables, ensure that the environment temperature is above 0C.
If the cables are stored in a place where the ambient temperature is below 0C, 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
WARNING
If the ambient temperature exceeds 55C, the temperature of the front panel surface marked the
flag may exceed 70C. When touching the front panel of the board in such an environment,
you must wear the protection gloves.
Issue 02 (2012-12-30)

15

2 Commissioning Preparations
Commissioning Preparations
About This Chapter

This chapter describes the preparations that must be made prior to commissioning equipment.
The preparation process is as follows:
2.1 Preparing Documents and Tools
This section lists the documents and tools to be obtained prior to equipment commissioning.
2.2 Preparing a USB Flash Drive
Prepare a USB flash drive if it is required for commissioning.
2.3 Determining the Commissioning Method
According to the scale of a microwave transmission network, commissioning engineers can use
the network commissioning method.
2.4 Checking Commissioning Conditions
Ensure that the equipment meets the requirements for site commissioning or system
commissioning prior to performing any commissioning tasks.
Issue 02 (2012-12-30)

16

2.1 Preparing Documents and Tools

This section lists the documents and tools to be obtained prior to equipment commissioning.
Documents
Obtain the following documents before equipment commissioning:
l
Engineering design documents, including:

Network Plan
Engineering Design
Commissioning guide, including:

OptiX RTN 310 Microwave Transmission System Commissioning and Configuration
Guide
Tools
Prepare the tools listed in Table 2-1 before equipment commissioning.
Table 2-1 Tools
Tool
Application Scenario
Adjustable wrench, screwdriver, telescope,

interphone, hex key (delivered with
antennas), multimeter, north-stabilized
indicator, and received signal strength
indicator (RSSI) test cable (delivered with
OptiX RTN 310), special spanner for the
orthogonal mode transducer (OMT)
(delivered with the OMT)
Aligning antennas
A laptop with the Web LCT installed
l Configuring site commissioning data

l Checking the microwave link status and
receive power
l Testing adaptive modulation (AM)
shifting
l Checking alarms
Network management system (NMS) server
Performing system commissioning items
NOTE
For details about the requirements and methods for installing the Web LCT, see the iManager U2000 Web
LCT User Guide.
Issue 02 (2012-12-30)

17

2.2 Preparing a USB Flash Drive

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

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

Data
Storage Directory
NE software
\pkg
Patch
\patch
License software
\license
Script
\script
USB authentication certificate
Root directory
NOTE
The RTN.CER file stores the administrator
accounts and passwords. The passwords are
encrypted in MD5 format. This file is generated
using a special-purpose tool.
2.3 Determining the Commissioning Method

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

18

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

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

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

Before performing system commissioning, ensure that the equipment and weather meet the
requirements for system commissioning.
The requirements are listed as follows:
l
Site commissioning at both ends of a microwave link has been completed.
Data communication network (DCN) communication on the microwave transmission

network is normal.
There are no adverse weather conditions (such as strong wind, rain, snow, or fog) that could
hinder or affect commissioning.
Issue 02 (2012-12-30)

19

3 Commissioning Process
Commissioning Process
About This Chapter

Based on the objects to be commissioned, commissioning involves two stages: site
commissioning and system commissioning.
3.1 Site Commissioning Process
Site commissioning refers to the commissioning of one microwave link hop and the sites at both
ends of the hop. Site commissioning ensures that the sites and the microwave link between the
sites work properly. Site commissioning is a preparation for system commissioning.
3.2 System Commissioning Process
System commissioning refers to the commissioning of an entire microwave transmission
network. System commissioning ensures that various services are transmitted properly and
protection is implemented across the network.
Issue 02 (2012-12-30)

20

3.1 Site Commissioning Process

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

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

are transmitted by singlepolarized antennas.
Aligning Dual-Polarized
Antennas

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

Engineers can configure site commissioning data using the Web LCT onsite if they:
Issue 02 (2012-12-30)

21

Are familiar with how to configure microwave link data on OptiX RTN 310.
Are familiar with the microwave link plan for the target sites.
Have a laptop on which the Web LCT is installed.
Commissioning Item
Remarks
Powering on the Equipment
Required.
Connecting the Web LCT to the Equipment
Required.
Creating NEs Using the Search Method
Required.
Configuring Site
Commissioning Data
Changing an NE ID
Required.
Configuring NE
Communications
Parameters
Required.
Changing an NE Name
Optional.
Setting the VLAN ID and

Bandwidth for an Inband
DCN
Required.
Setting OSPF Protocol

Parameters
Optional.
Configuring a link
aggregation group (LAG)
Required when configuring

physical link aggregation
(PLA) or 1+1 HSB/FD/SD
with NE-level protection
(HSB is short for hot standby,
FD for frequency diversity,
and SD for space diversity).
Configuring an IF 1+1
Protection Group
Required when configuring a

microwave link with 1+1
protection.
Configuring a PLA Group
Required when configuring a

microwave link with PLA
protection.
Configuring Data for a Hop

of Microwave Link
Required.
Synchronizing the NE Time
Required.
Checking Alarms
Aligning Antennas*
Issue 02 (2012-12-30)
Required.
Aligning Single-Polarized
Antennas

are transmitted by singlepolarized antennas.
Aligning Dual-Polarized
Antennas

are transmitted by dualpolarized antennas.

22

Commissioning Item
Remarks
Checking the Microwave Link Status and Receive Power
Required.
NOTE
*: Before aligning antennas, power on the equipment and configure site commissioning data at both ends
of the microwave link.
3.2 System Commissioning Process

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

Services
6.2.1 Testing Ethernet

Services Configured on a
Per NE Basis
Required when Ethernet

services are configured on a
per NE basis.
6.2.2 Testing Ethernet

Services Configured in
End-to-End Mode
Required when Ethernet

services are configured in
end-to-end mode.
6.3 Testing AM Shifting

6.4 Testing Protection
Switching
Issue 02 (2012-12-30)
Required.
Testing Ethernet Ring
Protection Switching
(ERPS)
Required.
6.4.2 Testing 1+1

Required when a microwave

link with 1+1 protection is
configured.
6.4.3 Testing PLA

Required when a microwave

link with physical link
aggregation (PLA)
protection is configured.
6.5 Checking the Clock Status
Required.
6.6 Testing the Fade Margin over a Microwave Link
Optional.
6.7 Testing Ethernet

Service Performance
Required.
6.7.1 Testing the Latency,

Throughput, and Packet
Loss Ratio

23

Commissioning Item
Remarks
6.7.2 Testing the Long-term
Packet Loss Ratio
Issue 02 (2012-12-30)

Required.
24

4 Site Commissioning (Using a USB Flash Drive to

Configure Data)
Site Commissioning (Using a USB Flash

Drive to Configure Data)
About This Chapter

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

25


Configure Data)
After antenna alignment, check whether the status of a microwave link is normal and whether
the receive power meets requirements.
Issue 02 (2012-12-30)

26


Configure Data)

Prerequisites
l
A suitable power supply is available. The voltage, polarity, and fuse capacity of the power
supply have been checked.
The power supply (for example, the cabinet power distribution box) is switched off.
Power cables are connected correctly.
Tools, Equipment, and Materials

Web LCT
Context
Table 4-1 lists the fuse capacity recommended for OptiX RTN 310.
Table 4-1 Fuse capacity
Chassis
Recommended Fuse Capacity
OptiX RTN 310
6 A to 12 A
Precautions
CAUTION
l If the output voltage of the power supply does not meet test requirements, do not switch on
the power supply and propose rectification suggestions.
l If power cables are connected to the OptiX RTN 310 incorrectly, reconnect the power cables
before switch on the power supply. Otherwise, the circuit breakers in the power distribution
box will be switched off and the power cables will be damaged.
Procedure
Step 1 Select the desired procedure to switch on the power supply based on the actual scenario.
Issue 02 (2012-12-30)

27


Configure Data)
2
PWR
P&E
MGMT
P&E
P&E
NMS/COM
P&E
3/P1
EG4P
Power over Ethernet is used.
A DC power supply is used.
Interconnected with OptiX RTN 900
If...
Then...
Power over Ethernet is used
Perform Step 2 and Step 3.
A DC power supply is used
Perform Step 4.
OptiX RTN 310 is interconnected with OptiX

RTN 900
Perform Step 5 to Step 7.
Step 2 Verify that the P&E cable and power injector (PI) power cable are correctly connected. Switch
on the power supply and observe the PI indicators.
Power supply equipment

Blue: -48 V
Black: 0 V ground cable
(-)
(+)
Normally, the DC IN and P&E OUT indicators on the PI are steady green.
Issue 02 (2012-12-30)

28


Configure Data)
NOTE
l If the DC IN indicator is steady green but the P&E OUT indicator blinks green, check whether the P&E
cable or OptiX RTN 310 is short-circuited.
l If the DC IN indicator is steady green but the P&E OUT indicator is off, check whether the P&E cable or
PI is faulty.
Step 3 Observe the system indicator on the OptiX RTN 310 to check whether the equipment is
successfully powered on.
System indicator
USB/RSSI/NMS
Normally, the system indicator in the USB/RSSI/NMS port on the OptiX RTN 310 is steady
green.
NOTE
If the system indicator is steady red, check whether the P&E cable or OptiX RTN 310 is faulty.
Step 4 Verify that the DC power cable is correctly connected and switch on the power supply. Observe
the system indicator on the OptiX RTN 310 to check whether the equipment is successfully
powered on.
Issue 02 (2012-12-30)

29


Configure Data)
System indicator
PWR
Front view
Positive
Negative
USB/RSSI/NMS

Brown: 0 V ground cable
Blue: -48 V
(+)
(-)
green.
NOTE
l If the system indicator is off, check the output voltage and polarity of the power supply. If the output
voltage or polarity is incorrect, locate the fault.
l If the system indicator is steady red, check whether the OptiX RTN 310 is faulty.
Step 5 Power on the OptiX RTN 900, observe the 3/P1 or 4/P2 indicator on the EG4P board on the
OptiX RTN 900 that is connected to the P&E port on the OptiX RTN 310.
If...
Then...
The 3/P1 or 4/P2 indicator on the EG4P board is off
Go to the next step.
The 3/P1 or 4/P2 indicator on the EG4P board is on
Perform Step 7.
Step 6 Connect the Web LCT to the OptiX RTN 900. Enable the power over Ethernet function for the
port on the EG4P board that is connected to the OptiX RTN 310 by using the Web LCT.
1.
In NE Explorer, choose the desired NE from the object tree and choose Configuration >
Interface Management > Ethernet Interface from Function Tree.
2.
Click the Advanced Attributes tab.
3.
Set PoE to Enabled for the port on the EG4P board that is connected to the OptiX RTN
310.
4.
Click Apply.
Step 7 Verify that the P&E cable is correctly connected, and observe the system indicator on the OptiX
RTN 310 to check whether the equipment is successfully powered on.
Issue 02 (2012-12-30)

30


Configure Data)
System indicator
P&E
USB/RSSI/NMS
NMS/COM
3/P1
4/P1
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
EG4P
OUT1/IN1
EG4P
OUT2/IN2
3/P1
4/P1
OUT2/IN2
3/P1
4/P1
L/A4
P1
P2
L/A3
OUT1/IN1
Power over
Ethernet indicators
OUT2/IN2
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
EG4P
RTN 950
OUT1/IN1
EG4P
3/P1
4/P2
The 3/P1 and 4/P2 ports on the EG4P board provide power over Ethernet capabilities. The 3/P1
port is used in this example. Normally, the L/A3 indicator on the EG4P board of the OptiX RTN
900 is steady green or blinks yellow, and the 3/P1 indicator on the EG4P board and the system
indicator in the USB/RSSI/NMS port on the OptiX RTN 310 are steady green.
NOTE
l If the L/A3 indicator on the EG4P board of the OptiX RTN 900 is off, check whether the P&E cable
or OptiX RTN 900 is faulty.
l If the 3/P1 indicator on the EG4P board of the OptiX RTN 900 is off, check whether the power over
Ethernet function is enabled.
l If the system indicator on the OptiX RTN 310 is steady red, check whether the P&E cable or OptiX
RTN 310 is faulty.
----End
4.2 Loading Commissioning Data Using a USB Flash Drive

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

31


Configure Data)

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

32


Configure Data)
Status of the USB

Indicator
Data Loading Status
Operation
The USB indicator blinks

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

after the USB flash drive is
inserted.
Issue 02 (2012-12-30)
The USB flash drive is faulty

and has failed to go online.
NOTE
Another possible cause is that
the USB flash drive is not
properly inserted.

l Copy the commissioning

data to another USB flash
drive.
l Repeat Step 2 to load the
data to the NE.
33


Configure Data)
Status of the USB

Indicator
Data Loading Status
Operation
The USB indicator blinks

red.
An incorrect model of USB

flash drive has been inserted,
or an error has occurred when
the NE attempted to read/
write the USB flash drive.
l Copy the commissioning

data to another USB flash
drive of the correct
model.
NOTE
2.2 Preparing a USB Flash
Drive provides the model of
USB flash drive supported by
OptiX RTN 310.
The USB indicator is steady

red.
The loaded data is incorrect.
l Repeat Step 2 to load the

data to the NE.
Handle the fault by following

instructions in 7.1 When a
USB Flash Drive Is Used
for Loading
Commissioning Data, Some
Commands Fail to Be
Loaded.
----End

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

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

34


Configure Data)
l The subnet mask is the same as that for the NE IP address (the default subnet mask is
255.255.0.0).
l The default gateway IP address is blank.
Step 3 Connect the Web LCT to an OptiX RTN 310 in an appropriate way based on the site
configuration. For details, see Figure 4-1.
CAUTION
Ensure that each fiber/cable is properly connected to the correct port. Otherwise, the equipment
or the tool may be damaged.
Figure 4-1 Ways for connecting the Web LCT to an OptiX RTN 310
P&E
MGMT
P&E
P&E
USB/RSSI/NMS
NMS/COM
P&E
4/P2
NMS
Fiber
To NodeB
MGMT
P&E
EG4P
A network consisting of only OptiX RTN 310s

(using the PI)
A network consisting of both OptiX RTN 310s and

OptiX RTN 900s
A network consisting of only

OptiX RTN 310s
NOTE
l If a site has several cascaded OptiX RTN 310s, connect the laptop to only one of the OptiX RTN 310s.
l Use either a crossover cable or a straight-through cable to connect the laptop to the OptiX RTN 310. For
the wire sequences of crossover cables and straight-through cables, see Cable in the OptiX RTN 310
Microwave Transmission System Product Description.
After the Web LCT and the OptiX RTN 310 are properly connected, the indicator at the Ethernet
port of the laptop is steady green. A message is displayed indicating that the network has
established a local connection if the operating system has been configured to do so. If the
operating system displays a message indicating an IP address conflict, change the IP address of
the laptop.
Step 4 On the desktop, double-click the Start Web LCT icon.
The system displays the USER LOGIN window of the Web LCT.
Issue 02 (2012-12-30)

35


Configure Data)
Step 5 Set User Name, Password, and Verification Code, and click Login.
l User Name: admin
l Password: Changeme_123
If the entered user name and password are correct, the NE List page is displayed.
----End
Follow-up Procedure
l
If a site has only OptiX RTN 310s and no PI is configured, remove the P&E cable from
the OptiX RTN 310 after the commissioning is complete.
If you cannot access the USER LOGIN window or the NE List page, configure the Internet
Explorer using the following method:
Issue 02 (2012-12-30)

36


Configure Data)

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

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

37


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

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

Web LCT
Issue 02 (2012-12-30)

38


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

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

Web LCT
Context
The following procedure checks the alarms on an NE.
Procedure
Step 1 Check alarms.
Issue 02 (2012-12-30)

39


Configure Data)
----End

4.7.1 Main Lobe and Side Lobes

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

Antenna alignment aligns the main lobe of the local antenna with the main lobe of the opposite
antenna, to achieve the maximum received signal strength at the opposite antenna.
Issue 02 (2012-12-30)

40


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

Outer edge of the main lobe, 3 to
10 dB lower than the main lobe
Trough between the main lobe
and the first side lobe, 30 dB
lower than the main lobe
First side lobe, 20-25 dB
180o
90o
0o
a Horizontal section
of the antenna
b Head-on
view
Trough between the first side lobe

and the second side lobe, 30 dB or
more lower than the main lobe
Second side lobe, where
signals are very weak
Tracking Path
Side lobe signal readings are sometimes mistaken for main lobe readings when signals are
tracked on different elevations (or azimuths). Figure 4-4 shows a horizontal radio propagation
model of an antenna, and signal levels at three different elevation positions (1-7 represent the
measured signal level values of the received signal strength indicator [RSSI] port of the OptiX
RTN 310).
Issue 02 (2012-12-30)

41


Configure Data)
Figure 4-4 Three tracking paths

Head-on view of tracking paths for
different elevations
Signal level for each path

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

42


Configure Data)
4.7.2 Aligning Single-Polarized Antennas

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

l
Adjustable wrench
Interphone
Hex key (delivered with antennas)
North-stabilized indicator
Telescope
Multimeter
Received signal strength indicator (RSSI) test cables (delivered with OptiX RTN 310)
CAUTION
You can change the azimuth and elevation of the antennas by adjusting the nuts or screws. For
details, see the antenna installation guide. Steps provided in this section are for reference only.
Precautions
l
If the microwave link needs to be configured with 1+1 protection, configure 1+1 protection
after antenna alignment.
If the microwave link is configured with 1+1 protection and only one antenna is used at
each end, power off the standby OptiX RTN 310s at both ends before aligning the antennas.
After the antennas are aligned, power on the standby OptiX RTN 310s.
If the microwave link is configured with 1+1 space diversity (SD) protection, align the
antennas in the following sequence:
Issue 02 (2012-12-30)

43


Configure Data)
1.
Power on the main OptiX RTN 310s at both ends. Ensure that they are always powered
on during the alignment process.
2.
Power off the standby OptiX RTN 310s and align the main antennas at both ends.
3.
Power on the standby OptiX RTN 310 at the local end. Retain the position of the main
antenna at the remote end, and adjust the diversity antenna at the local end.
4.
Power on the standby OptiX RTN 310 at the remote end. Retain the position of the
main antenna at the local end, and adjust the diversity antenna at the remote end.
If the microwave link is configured with 1+1 frequency diversity (FD) protection and two
antennas are used at each end, align the antennas in the following sequence:
1.
Power on the main OptiX RTN 310s, power off the standby OptiX RTN 310s, and
align the main antennas at both ends.
2.
Power off the main OptiX RTN 310s, power on the standby OptiX RTN 310s, and
align the diversity antennas at both ends.
Procedure
Step 1 Calculate the voltage value (VBNC) for the RSSI port corresponding to the planned received
signal level (RSL) based on the RSSI and RSL curves.
NOTE
The curve diagram for VBNC and RSL is delivered along with the OptiX RTN 310.
Step 2 Determine the azimuth of the antenna at the local end based on the installation position and
height of the antenna. Then, adjust the elevation of the antenna to the horizontal position.
NOTE
For a special microwave link (for example, a microwave link with one end on a mountain top and the other end
at the foot of the mountain), the inclination between the link and the horizontal line is greater than the half-power
angle of the antenna. Slightly adjust the elevation of the antenna so the main lobes are aligned vertically.
Step 3 Connect a multimeter to the RSSI port on the OptiX RTN 310 at the local end using an RSSI
test fiber and test the voltage value VBNC. Turn the multimeter to the DC power level with the
voltage value 20 V.
TIP
It is recommended that you fix the multimeter to the tower with adhesive tape at your plain view, so that
you can observe the RSSI voltage value while aligning antennas.
Figure 4-6 Testing the RSSI voltage using a multimeter
USB/RSSI/NMS
USB RSSI
Issue 02 (2012-12-30)

44


Configure Data)
Step 4 Adjust the azimuth and elevation of the antenna as follows:

1.
Keep the remote antenna fixed.
2.
Loosen the antenna brackets, rotate the antenna horizontally within a large range, and
observe the value of VBNC on the multimeter. When the value is not 0, secure the antenna
brackets.
3.
Loosen the fine adjustment bolts, rotate the antenna horizontally, and observe the peak
values of VBNC on the multimeter.
Normally, three signal peaks are tracked, as shown in Figure 4-7.
Figure 4-7 Signal peaks
2
1
CAUTION
If the number of tracked signal peaks is fewer than three, even after a wide rotation and
careful observation of the multimeter, refer to 4.7.1 Main Lobe and Side Lobes for help
with handling the exception.
4.
Adjust the antenna azimuth until the signal strength reaches position 2 shown in Figure
4-7. When the signal strength is at position 2, the value of VBNC is the peak value.
5.
Slightly adjust the elevation and azimuth at point 2 until VBNC reaches the peak value within
the tracked range.
6.
Secure the antenna at the local end.

NOTE
When securing the antenna, ensure that VBNC remains at the peak value.
Step 5 Repeat Step 2 to Step 4 to adjust the antenna at the remote end. When VBNC reaches the peak
value, secure the antenna at the remote end.
Step 6 Repeat Step 2 to Step 4 for two to four times. When VBNC at the local end and VBNC at the
remote end reach the peak value, secure the antennas at both ends.
NOTE
l Perform slight adjustments in this step.

l After the adjustments are complete and antennas at both ends are secured, the VBNC value must reach or
exceed the VBNC value obtained in Step 1.
----End
Issue 02 (2012-12-30)

45


Configure Data)
4.7.3 Aligning Dual-Polarized Antennas

When aligning dual-polarized antennas, align the main lobes by adjusting the azimuth and
elevation of the antennas at both ends. Engineers also need to adjust the feed booms of the
antennas so that cross-polarization discrimination (XPD) meets requirements.
Prerequisites
l
link.
procedure.
default).

l
Adjustable wrench
Interphone
Telescope
Multimeter
Received signal strength indicator (RSSI) test cables (delivered with )
Special spanner for the orthogonal mode transducer (OMT) (delivered with the OMT)
Context
NOTE
The following procedure assumes that the s at both ends are installed separately from antennas. If the s at both
ends need to be connected directly to an OMT, the OMT should be adjusted instead of the antenna feed boom.
Procedure
Step 1 Power off the vertically polarized s and power on the horizontally polarized s at both ends of
the microwave link. Ensure that the antennas at both ends are transmitting horizontally polarized
signals.
Issue 02 (2012-12-30)

46


Configure Data)
Vertically polarized RTN 310
Horizontally polarized RTN 310

Switch off
Power
supply
Step 2 Adjust the azimuth angle and elevation angle of the antennas at both ends by referring to 4.7.2
Aligning Single-Polarized Antennas, and ensure that the main lobes of the horizontally
polarized signals are aligned.
Step 3 Measure the received signal level (RSL) of the horizontally polarized signals, that is, P1, at the
local end.
1.
Issue 02 (2012-12-30)
Use a multimeter to measure the RSL at the RSSI port of the horizontally polarized .

47


Configure Data)
3.62
2.
Calculate the RSL of the horizontally polarized signals, that is, P1, by referring to the curve
diagram delivered with the .
Step 4 Adjust the feed boom at the local end, and ensure that the RSL of the vertically polarized signals
reaches the lower threshold (P2).
1.
Power on the vertically polarized at the local end.
2.
Use a multimeter to measure the RSL at the RSSI port of the vertically polarized .
Issue 02 (2012-12-30)

48


Configure Data)
3.62
3.
Calculate the RSL (P2) of the vertically polarized signals by referring to the curve diagram
in the box.
4.
Calculate the XPD1 (XPD1 = P1 - P2).
5.
If...
Then...
The calculated XPD1 is less than 30 dB
The calculated XPD1 is greater than or equal to 30 dB
Go to Step 5.
Release the feed boom holder slightly, and turn the feed boom slightly until the RSL reaches
the lower threshold and the calculated XPD1 is greater than or equal to 30 dB.
Step 5 Record the angle (D1) of the current feed boom.

Step 6 At both ends of the microwave link, power off the horizontally polarized s and power on the
vertically polarized s. Ensure that the antennas at both ends are transmitting vertically polarized
signals.
Issue 02 (2012-12-30)

49


Configure Data)
Power
supply
Switch off
Step 7 Measure the RSL (P3) of the vertically polarized signals at the local end by referring to Step
3.
Step 8 Adjust the feed boom at the local end, and ensure that the RSL of the horizontally polarized
signals reaches the lower threshold (P4).
1.
Power on the horizontally polarized at the local end.
2.
Issue 02 (2012-12-30)

50


Configure Data)
3.62
3.
Calculate the RSL (P4) of the horizontally polarized signals by referring to the curve
4.
5.
If...
Then...
Go to Step 9.
Release the feed boom holder slightly, and turn the feed boom slightly until the RLS reaches

Step 10 Adjust the feed boom slightly (ranging from D1 to D2), and ensure that XPD1 and XPD2 are
greater than or equal to 30 dB.
Issue 02 (2012-12-30)

51


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

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

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

Web LCT
Context
The following procedure checks the microwave link status and receive power.
Issue 02 (2012-12-30)

52


Configure Data)
Procedure
Step 1 Check the microwave link status and receive power.
NOTE
If the receive power does not meet design requirements, handle the fault by following instructions in 7.2
The Receive Power Does not Meet the Design Requirements.
----End
Issue 02 (2012-12-30)

53

5 Site Commissioning (Using the Web LCT to Configure

Data)
Site Commissioning (Using the Web LCT to

Configure Data)
About This Chapter

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

54


Data)

Prerequisites
l
A suitable power supply is available. The voltage, polarity, and fuse capacity of the power
supply have been checked.
The power supply (for example, the cabinet power distribution box) is switched off.
Power cables are connected correctly.

Web LCT
Context
Table 5-1 lists the fuse capacity recommended for OptiX RTN 310.
Table 5-1 Fuse capacity
Chassis
Recommended Fuse Capacity
OptiX RTN 310
6 A to 12 A
Precautions
CAUTION
l If the output voltage of the power supply does not meet test requirements, do not switch on
the power supply and propose rectification suggestions.
l If power cables are connected to the OptiX RTN 310 incorrectly, reconnect the power cables
before switch on the power supply. Otherwise, the circuit breakers in the power distribution
box will be switched off and the power cables will be damaged.
Procedure
Step 1 Select the desired procedure to switch on the power supply based on the actual scenario.
Issue 02 (2012-12-30)

55


Data)
2
PWR
P&E
MGMT
P&E
P&E
NMS/COM
P&E
3/P1
EG4P
Power over Ethernet is used.
A DC power supply is used.
Interconnected with OptiX RTN 900
If...
Then...
Power over Ethernet is used
Perform Step 2 and Step 3.
A DC power supply is used
Perform Step 4.
OptiX RTN 310 is interconnected with OptiX

RTN 900
Perform Step 5 to Step 7.
Step 2 Verify that the P&E cable and power injector (PI) power cable are correctly connected. Switch
on the power supply and observe the PI indicators.

Blue: -48 V
Black: 0 V ground cable
(-)
(+)
Normally, the DC IN and P&E OUT indicators on the PI are steady green.
Issue 02 (2012-12-30)

56


Data)
NOTE
l If the DC IN indicator is steady green but the P&E OUT indicator blinks green, check whether the P&E
cable or OptiX RTN 310 is short-circuited.
l If the DC IN indicator is steady green but the P&E OUT indicator is off, check whether the P&E cable or
PI is faulty.
Step 3 Observe the system indicator on the OptiX RTN 310 to check whether the equipment is
successfully powered on.
System indicator
USB/RSSI/NMS
green.
NOTE
If the system indicator is steady red, check whether the P&E cable or OptiX RTN 310 is faulty.
Step 4 Verify that the DC power cable is correctly connected and switch on the power supply. Observe
the system indicator on the OptiX RTN 310 to check whether the equipment is successfully
powered on.
Issue 02 (2012-12-30)

57


Data)
System indicator
PWR
Front view
Positive
Negative
USB/RSSI/NMS

Brown: 0 V ground cable
Blue: -48 V
(+)
(-)
green.
NOTE
l If the system indicator is off, check the output voltage and polarity of the power supply. If the output
voltage or polarity is incorrect, locate the fault.
l If the system indicator is steady red, check whether the OptiX RTN 310 is faulty.
Step 5 Power on the OptiX RTN 900, observe the 3/P1 or 4/P2 indicator on the EG4P board on the
OptiX RTN 900 that is connected to the P&E port on the OptiX RTN 310.
If...
Then...
The 3/P1 or 4/P2 indicator on the EG4P board is off
The 3/P1 or 4/P2 indicator on the EG4P board is on
Perform Step 7.
Step 6 Connect the Web LCT to the OptiX RTN 900. Enable the power over Ethernet function for the
port on the EG4P board that is connected to the OptiX RTN 310 by using the Web LCT.
1.
In NE Explorer, choose the desired NE from the object tree and choose Configuration >
Interface Management > Ethernet Interface from Function Tree.
2.
Click the Advanced Attributes tab.
3.
Set PoE to Enabled for the port on the EG4P board that is connected to the OptiX RTN
310.
4.
Click Apply.
Step 7 Verify that the P&E cable is correctly connected, and observe the system indicator on the OptiX
RTN 310 to check whether the equipment is successfully powered on.
Issue 02 (2012-12-30)

58


Data)
System indicator
P&E
USB/RSSI/NMS
NMS/COM
3/P1
4/P1
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
EG4P
OUT1/IN1
EG4P
OUT2/IN2
3/P1
4/P1
OUT2/IN2
3/P1
4/P1
L/A4
P1
P2
L/A3
OUT1/IN1
Power over
Ethernet indicators
OUT2/IN2
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
STAT
SRV
L/A1
L/A2
L/A3
L/A4
P1
P2
EG4P
RTN 950
OUT1/IN1
EG4P
3/P1
4/P2
The 3/P1 and 4/P2 ports on the EG4P board provide power over Ethernet capabilities. The 3/P1
port is used in this example. Normally, the L/A3 indicator on the EG4P board of the OptiX RTN
900 is steady green or blinks yellow, and the 3/P1 indicator on the EG4P board and the system
indicator in the USB/RSSI/NMS port on the OptiX RTN 310 are steady green.
NOTE
l If the L/A3 indicator on the EG4P board of the OptiX RTN 900 is off, check whether the P&E cable
or OptiX RTN 900 is faulty.
l If the 3/P1 indicator on the EG4P board of the OptiX RTN 900 is off, check whether the power over
Ethernet function is enabled.
l If the system indicator on the OptiX RTN 310 is steady red, check whether the P&E cable or OptiX
RTN 310 is faulty.
----End

Prerequisites
NOTE
link.
Issue 02 (2012-12-30)

59


Data)

Web LCT
Procedure
255.255.0.0).
configuration. For details, see Figure 5-1.
CAUTION
Figure 5-1 Ways for connecting the Web LCT to an OptiX RTN 310
P&E
MGMT
P&E
P&E
USB/RSSI/NMS
NMS/COM
P&E
4/P2
NMS
Fiber
To NodeB
MGMT
P&E
EG4P
Issue 02 (2012-12-30)

(using the PI)

OptiX RTN 900s

OptiX RTN 310s

60


Data)
NOTE
the laptop.
l User Name: admin
----End
Issue 02 (2012-12-30)

61


Data)
Follow-up Procedure
l

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

Web LCT
Context
l
Searches for NEs using the NE Search method if the NEs are connected directly to the
Web LCT using Ethernet cables.
Searches for NEs using the IP auto discovery method if the site has multiple NEs.
Procedure
Step 1 Search for NEs using the NE Search method if the NEs are connected directly to the Web LCT
using Ethernet cables.
Issue 02 (2012-12-30)

62


Data)
Step 2 Search for NEs using the IP auto discovery method if the site has multiple NEs.
----End
5.4 Configuring Site Commissioning Data

During site commissioning, you do not need to configure Ethernet service data. By default, the
NE creates an IEEE 802.1D bridge-based Ethernet local area network (E-LAN) service for
transmitting Ethernet services.
Flowchart
Figure 5-2 shows the flowchart for configuring site commissioning data.
Issue 02 (2012-12-30)

63


Data)
Figure 5-2 Configuration flowchart
Start
Change the NE ID.
Set NE communication
parameters.
Change the NE name.
Set the VLAN ID and

bandwidth for an inband DCN.
Configure OSPF parameters.
Configuring a LAG.
Configuring a microwave 1+1

protection group.
Configuring a PLA group
Configure data for a hop of

microwave link.
Required
Synchronize the NE time.
Optional
End
Issue 02 (2012-12-30)

64


Data)
Process
Table 5-2 Configuration procedure
Step
Operation
Remarks
Changing an NE ID
Required. Set parameters as follows:

l Set New ID according to the DCN plan.
l If a specific extended NE ID is required,
change New Extended ID to the
required one.
Configuring NE
Communications Parameters
Required if special requirements are

imposed on the IP address of the NE.
Configure the IP address and subnet mask
for the NE as required.
NOTE
If the IP address of an NE has not been changed
manually, the IP address changes with the NE
ID and is always 0x81000000 + NE ID.
Issue 02 (2012-12-30)
Changing an NE Name
Optional.
Setting the VLAN ID and

Bandwidth for an Inband
DCN
Required.
Setting OSPF Protocol

Parameters
Optional.
Configuring a link
aggregation group (LAG)
Required when configuring physical link

aggregation (PLA) or 1+1 HSB/FD/SD
with NE-level protection (HSB is short for
hot standby, FD for frequency diversity,
and SD for space diversity).
Configuring a Microwave 1+1

Protection Group
Required when configuring a microwave

link with 1+1 protection.
Configuring a PLA Group
Required when configuring a microwave

link with PLA protection.
Configuring Data for a Hop of

Radio Link
Required.
10
Synchronizing the NE Time
Required. This operation synchronizes NE

time with the time on the computer that
runs the Web LCT.

65


Data)
5.4.1 Changing an NE ID
Change the NE ID according to the engineering plan to ensure that each NE ID is unique. This
task does not interrupt services.
Prerequisites
You must be an NM user with NE operator rights or higher.

U2000
NOTE
The Web LCT also supports this task. The steps are the same as those on the U2000.
Context
The following procedure changes an NE ID to the planned value listed in the following table.
Parameter
Value
New ID
320
Procedure
Step 1
----End
5.4.2 Setting NE Communication Parameters

NE communication parameters include the NE IP address, gateway IP address, and subnet mask.
Prerequisites
Issue 02 (2012-12-30)

66


Data)

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

For easier identification of an NE in Main Topology, name the NE according to its geographical
location or the device to which it is connected.
Prerequisites
Issue 02 (2012-12-30)

67


Data)

U2000
NOTE
Context
The following procedure changes an NE name to the planned value listed in the following table.
Parameter
Value
Name
Site2-1
Procedure
Step 1
----End
5.4.4 Setting the VLAN ID and Bandwidth for an Inband DCN

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

U2000
NOTE
Issue 02 (2012-12-30)

68


Data)
Context
The following procedure sets the VLAN ID and bandwidth to the planned values listed in the
following table for an inband DCN.
Parameter
Value
VLAN ID
4092
Bandwidth(Kbit/s)
1000bit/s
Procedure
Step 1
----End
5.4.5 Setting OSPF Protocol Parameters

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

U2000
NOTE
Context
The following procedure configures OSPF parameters according to the planned parameter values
Issue 02 (2012-12-30)

69


Data)
Parameter
Value
Area
0.0.0.1
OSPF Status
Enabled
Static route
Enabled
LAN Interface
Disabled
Procedure
Step 1
----End
5.4.6 Creating a LAG

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

U2000
NOTE
Context
l
Issue 02 (2012-12-30)
Creates a non-load sharing LAG to protect the Ethernet link from a UNI-side equipment
to an NE, according to the planned parameter values listed in the following table.
70

Issue 02 (2012-12-30)

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

71


Data)
Parameter
NE
Main port
1-SHXA2-2 (GE1)
Procedure
Step 1 Create a non-load sharing LAG.
Step 2 Create a load-sharing LAG.
Step 3 Create a LAG for configuring 1+1 or PLA protection with NE-level protection.
Issue 02 (2012-12-30)

72


Data)
----End
5.4.7 Creating a Microwave 1+1 Protection Group

If microwave links are configured with 1+1 hot standby (HSB), frequency diversity (FD), or
space diversity (SD) protection, you need to create a corresponding microwave 1+1 protection
group.
Prerequisites
l
An enhanced link aggregation group (E-LAG) has been configured.
1+1 protection cannot coexist with cross polarization interference cancellation (XPIC) or
physical link aggregation (PLA).
The Ethernet ports on the active and standby OptiX RTN 310s must both be P&E electrical
ports or GE optical ports, and work in Auto-negotiation mode. A static and non-load
sharing link aggregation group (LAG) has been created on each of the active and standby
OptiX RTN 310s. The LAG has only one member port, which is an Ethernet port.
Ethernet services are received/transmitted through either the GE optical port or the P&E
electrical port of an OptiX RTN 310. If Ethernet services are received/transmitted through
both ports, 1+1 protection cannot be successfully configured.
The COMBO ports on the active and standby OptiX RTN 310s are connected using an
optical fiber.
Logical Port Attribute has been set to Electrical Port if the Ethernet port in the 1+1
protection group is a P&E electrical port.

U2000
Context
The following procedure creates a microwave 1+1 protection group according to the planned
parameter values listed in the following table.
Issue 02 (2012-12-30)

73


Data)
Parameter
Value
Working Mode
HSB
Reversion Mode
Revertive
WTR Time (s)
600 (default value)
Enable Reverse Switching
Enable
Working/Protection Unit Type
Working Unit
Service Port
1-SHXA2-2(GE1)
Procedure
Step 1
----End
5.4.8 Creating a PLA Group

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

U2000
Issue 02 (2012-12-30)

74


Data)
Context
The following procedure creates a PLA group according to the planned parameter values listed
in the following table.
Parameter
Value
Protection Type
NE-level LAG protection
NE Role
Slave
IF Port
1-SHXA2-1 (IF)
Service Port
1-SHXA2-2 (GE1)
Cascade Port
1-SHXA2-3 (GE2)
Procedure
Step 1
----End
5.4.9 Configuring a Single Hop of Microwave Link

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

U2000
Issue 02 (2012-12-30)

75


Data)
NOTE
Precautions
The following parameters of the NEs on a hop of microwave link are automatically synchronized:
Link ID, IF Channel Bandwidth, XPIC, AM, Modulation Mode of the Guaranteed AM
Capacity, Modulation Mode of the Full AM Capacity, Modulation Mode, T/R Spacing
(MHz), and ATPC. That is, if one of the preceding parameters is modified on an NE, the
modification is automatically duplicated on the peer NE.
Context
The following procedure configures basic information for the hop of microwave link shown in
the following figure by configuring NE1. The hop of microwave link is a member of a cross
polarization interference cancellation (XPIC) group.
NE3
NE1
V-polarization
GE
GE
COMBO
COMBO
COMBO
COMBO
H-polarization
GE
NE2
GE
NE4
The planned parameter values are listed in the following table.
Issue 02 (2012-12-30)
Parameter
Link 1
Link 2
NE ID
9-2327(Local Radio
Terminal)
9-2322(Local Radio
Terminal)
9-2328(Opposite Radio
Terminal)
Terminal)
Link ID
TX frequency at the TX high

site (MHz)
14920 (NE1)
14920 (NE2)
TX frequency at the TX low

site (MHz)
14500 (NE3)
14500 (NE4)
RF configuration mode
XPIC
XPIC
Polarization direction
V (vertical polarization)
H (horizontal polarization)
Radio working mode
28 MHz
28 MHz
AM
Disabled
Disabled
Modulation Mode
16QAM
16QAM

76


Data)
Parameter
Link 1
Link 2
T/R Spacing (MHz)
420
420
ATPC
Disabled
Disabled
TX power (dBm)
22
22
RX power (dBm)
-26
-26
Procedure
Step 1
----End
5.4.10 Synchronizing NE Time

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

Web LCT
Context
The following procedure synchronizes the NE time with the Web LCT time.
Issue 02 (2012-12-30)

77


Data)
Procedure
Step 1 Synchronize the NE time with the Web LCT time.
----End
5.5 Checking Alarms

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

Web LCT
Context
The following procedure checks the alarms on an NE.
Procedure
Step 1 Check alarms.
Issue 02 (2012-12-30)

78


Data)
----End

5.6.1 Main Lobe and Side Lobes

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

Antenna alignment aligns the main lobe of the local antenna with the main lobe of the opposite
antenna, to achieve the maximum received signal strength at the opposite antenna.
Issue 02 (2012-12-30)

79


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

Outer edge of the main lobe, 3 to
10 dB lower than the main lobe
Trough between the main lobe
and the first side lobe, 30 dB
First side lobe, 20-25 dB
180o
90o
0o
a Horizontal section
of the antenna
b Head-on
view
Trough between the first side lobe

and the second side lobe, 30 dB or
more lower than the main lobe
Second side lobe, where
signals are very weak
Tracking Path
Side lobe signal readings are sometimes mistaken for main lobe readings when signals are
tracked on different elevations (or azimuths). Figure 5-5 shows a horizontal radio propagation
model of an antenna, and signal levels at three different elevation positions (1-7 represent the
measured signal level values of the received signal strength indicator [RSSI] port of the OptiX
RTN 310).
Issue 02 (2012-12-30)

80


Data)
Figure 5-5 Three tracking paths

Head-on view of tracking paths for
different elevations
Signal level for each path

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

81


Data)
5.6.2 Aligning Single-Polarized Antennas

When aligning single-polarized antennas, align the main lobes by adjusting the azimuth and
elevation of the antennas at both ends.
Prerequisites
l
link.
procedure.
default).

l
Adjustable wrench
Interphone
Telescope
Multimeter
Received signal strength indicator (RSSI) test cables (delivered with OptiX RTN 310)
CAUTION
You can change the azimuth and elevation of the antennas by adjusting the nuts or screws. For
details, see the antenna installation guide. Steps provided in this section are for reference only.
Precautions
l
If the microwave link needs to be configured with 1+1 protection, configure 1+1 protection
after antenna alignment.
If the microwave link is configured with 1+1 protection and only one antenna is used at
each end, power off the standby OptiX RTN 310s at both ends before aligning the antennas.
After the antennas are aligned, power on the standby OptiX RTN 310s.
If the microwave link is configured with 1+1 space diversity (SD) protection, align the
antennas in the following sequence:
Issue 02 (2012-12-30)

82


Data)
1.
Power on the main OptiX RTN 310s at both ends. Ensure that they are always powered
on during the alignment process.
2.
Power off the standby OptiX RTN 310s and align the main antennas at both ends.
3.
Power on the standby OptiX RTN 310 at the local end. Retain the position of the main
antenna at the remote end, and adjust the diversity antenna at the local end.
4.
Power on the standby OptiX RTN 310 at the remote end. Retain the position of the
main antenna at the local end, and adjust the diversity antenna at the remote end.
If the microwave link is configured with 1+1 frequency diversity (FD) protection and two
antennas are used at each end, align the antennas in the following sequence:
1.
Power on the main OptiX RTN 310s, power off the standby OptiX RTN 310s, and
align the main antennas at both ends.
2.
Power off the main OptiX RTN 310s, power on the standby OptiX RTN 310s, and
align the diversity antennas at both ends.
Procedure
Step 1 Calculate the voltage value (VBNC) for the RSSI port corresponding to the planned received
signal level (RSL) based on the RSSI and RSL curves.
NOTE
The curve diagram for VBNC and RSL is delivered along with the OptiX RTN 310.
Step 2 Determine the azimuth of the antenna at the local end based on the installation position and
height of the antenna. Then, adjust the elevation of the antenna to the horizontal position.
NOTE
For a special microwave link (for example, a microwave link with one end on a mountain top and the other end
at the foot of the mountain), the inclination between the link and the horizontal line is greater than the half-power
angle of the antenna. Slightly adjust the elevation of the antenna so the main lobes are aligned vertically.
Step 3 Connect a multimeter to the RSSI port on the OptiX RTN 310 at the local end using an RSSI
test fiber and test the voltage value VBNC. Turn the multimeter to the DC power level with the
voltage value 20 V.
TIP
It is recommended that you fix the multimeter to the tower with adhesive tape at your plain view, so that
you can observe the RSSI voltage value while aligning antennas.
Figure 5-7 Testing the RSSI voltage using a multimeter
USB/RSSI/NMS
USB RSSI
Issue 02 (2012-12-30)

83


Data)
Step 4 Adjust the azimuth and elevation of the antenna as follows:

1.
Keep the remote antenna fixed.
2.
Loosen the antenna brackets, rotate the antenna horizontally within a large range, and
observe the value of VBNC on the multimeter. When the value is not 0, secure the antenna
brackets.
3.
Loosen the fine adjustment bolts, rotate the antenna horizontally, and observe the peak
values of VBNC on the multimeter.
Normally, three signal peaks are tracked, as shown in Figure 5-8.
Figure 5-8 Signal peaks
2
1
CAUTION
If the number of tracked signal peaks is fewer than three, even after a wide rotation and
careful observation of the multimeter, refer to 4.7.1 Main Lobe and Side Lobes for help
with handling the exception.
4.
Adjust the antenna azimuth until the signal strength reaches position 2 shown in Figure
5-8. When the signal strength is at position 2, the value of VBNC is the peak value.
5.
Slightly adjust the elevation and azimuth at point 2 until VBNC reaches the peak value within
the tracked range.
6.
Secure the antenna at the local end.

NOTE
When securing the antenna, ensure that VBNC remains at the peak value.
Step 5 Repeat Step 2 to Step 4 to adjust the antenna at the remote end. When VBNC reaches the peak
value, secure the antenna at the remote end.
Step 6 Repeat Step 2 to Step 4 for two to four times. When VBNC at the local end and VBNC at the
remote end reach the peak value, secure the antennas at both ends.
NOTE
l Perform slight adjustments in this step.

l After the adjustments are complete and antennas at both ends are secured, the VBNC value must reach or
exceed the VBNC value obtained in Step 1.
----End
Issue 02 (2012-12-30)

84


Data)
5.6.3 Aligning Dual-Polarized Antennas

When aligning dual-polarized antennas, align the main lobes by adjusting the azimuth and
elevation of the antennas at both ends. Engineers also need to adjust the feed booms of the
antennas so that cross-polarization discrimination (XPD) meets requirements.
Prerequisites
l
link.
procedure.
default).

l
Adjustable wrench
Interphone
Telescope
Multimeter
Received signal strength indicator (RSSI) test cables (delivered with )
Special spanner for the orthogonal mode transducer (OMT) (delivered with the OMT)
Context
NOTE
The following procedure assumes that the s at both ends are installed separately from antennas. If the s at both
ends need to be connected directly to an OMT, the OMT should be adjusted instead of the antenna feed boom.
Procedure
Step 1 Power off the vertically polarized s and power on the horizontally polarized s at both ends of
the microwave link. Ensure that the antennas at both ends are transmitting horizontally polarized
signals.
Issue 02 (2012-12-30)

85


Data)

Switch off
Power
supply
Step 2 Adjust the azimuth angle and elevation angle of the antennas at both ends by referring to 4.7.2
Aligning Single-Polarized Antennas, and ensure that the main lobes of the horizontally
polarized signals are aligned.
Step 3 Measure the received signal level (RSL) of the horizontally polarized signals, that is, P1, at the
local end.
1.
Issue 02 (2012-12-30)

86


Data)
3.62
2.
Calculate the RSL of the horizontally polarized signals, that is, P1, by referring to the curve
Step 4 Adjust the feed boom at the local end, and ensure that the RSL of the vertically polarized signals
reaches the lower threshold (P2).
1.
Power on the vertically polarized at the local end.
2.
Use a multimeter to measure the RSL at the RSSI port of the vertically polarized .
Issue 02 (2012-12-30)

87


Data)
3.62
3.
Calculate the RSL (P2) of the vertically polarized signals by referring to the curve diagram
in the box.
4.
5.
If...
Then...
Go to Step 5.
Release the feed boom holder slightly, and turn the feed boom slightly until the RSL reaches

Step 6 At both ends of the microwave link, power off the horizontally polarized s and power on the
vertically polarized s. Ensure that the antennas at both ends are transmitting vertically polarized
signals.
Issue 02 (2012-12-30)

88


Data)
Power
supply
Switch off
Step 7 Measure the RSL (P3) of the vertically polarized signals at the local end by referring to Step
3.
Step 8 Adjust the feed boom at the local end, and ensure that the RSL of the horizontally polarized
signals reaches the lower threshold (P4).
1.
Power on the horizontally polarized at the local end.
2.
Issue 02 (2012-12-30)

89


Data)
3.62
3.
Calculate the RSL (P4) of the horizontally polarized signals by referring to the curve
4.
5.
If...
Then...
Go to Step 9.
Release the feed boom holder slightly, and turn the feed boom slightly until the RLS reaches

Step 10 Adjust the feed boom slightly (ranging from D1 to D2), and ensure that XPD1 and XPD2 are
greater than or equal to 30 dB.
Issue 02 (2012-12-30)

90


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

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

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

Web LCT
Context
The following procedure checks the microwave link status and receive power.
Issue 02 (2012-12-30)

91


Data)
Procedure
Step 1 Check the microwave link status and receive power.
NOTE
If the receive power does not meet design requirements, handle the fault by following instructions in 7.2
The Receive Power Does not Meet the Design Requirements.
----End
Issue 02 (2012-12-30)

92

6 System Commissioning
System Commissioning
About This Chapter

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

93


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

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

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

U2000
Test Connection Diagram

The following procedure uses the Ethernet services from GE 1 on NE 1 to GE 1 on NE 2 as an
example, as shown in Figure 6-1.
Figure 6-1 Connection diagram for testing Ethernet services
NE 1
Microwave transmission network
GE 1
NE 2
GE 1
NodeB
VLAN ID = 100
VLAN ID = 100
RNC
Issue 02 (2012-12-30)

94

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

l If the value of LossRate in Result is not 0, handle the problem based on the procedures in
the following table.
Cause
Handling Procedure
Connecting to the peer end fails within the

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

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

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

U2000
Issue 02 (2012-12-30)

95

NOTE
The Web LCT does not support this operation.

example, as shown in Figure 6-2.
Figure 6-2 Connection diagram for testing Ethernet services
NE 1
GE 1
NE 2
GE 1
NodeB
VLAN ID = 100
VLAN ID = 100
RNC

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

Issue 02 (2012-12-30)

96

----End

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

Web LCT
NOTE
The U2000 does not support this operation.
Context
The following procedure tests the AM shifting function on an NE.
Procedure
Step 1 Set the AM attributes.
Issue 02 (2012-12-30)

97

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

6.4.1 Testing ERPS Switching

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

98


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

In Figure 6-3, the Ethernet services between NE 1 and NE 6 are protected by ERPS, and NE 1
is the RPL owner node.
Figure 6-3 Configuration for testing ERPS
NE 4
E: IF
W: GE (GE2)
NE 3
E: GE (GE2)
W: IF
NE 5
E: GE (GE2)
W: IF
NE 6
E: IF
W: GE (GE2)
NE 2
E: IF
W: GE (GE2)
NE 7
E: GE (GE2)
W: IF
NE 8
E: IF
W: GE (GE2)
NE 1
E: GE (GE2)
W: IF
RPL owner
Ethernet cable
Ethernet service direction
Blocked port
Procedure
Step 1 Before switching, query the status of the ERPS protection group that is configured on NE 1.
Issue 02 (2012-12-30)

99

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

100

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

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

U2000
Issue 02 (2012-12-30)

101


Figure 6-4 Test connection diagram
The basic configurations are as follows:
l
Main OptiX RTN 310s: NE 11 and NE 12
Standby OptiX RTN 310s: NE 21 and NE 22

LAG
NE 11
NE 12
LAG
LAG
LAG
COMBO
COMBO
Antenna
NE 21
Antenna
NE 22
LAG
LAG
E-LAG
E-LAG
OptiX RTN 900
Ethernet link
Microwave link
Optical fiber
The Ethernet services protected by 1+1 hot standby (HSB) between NE 11 and NE 12 shown in
Figure 6-4 are tested.
Procedure
Step 1 Configure Reversion Mode for the 1+1 HSB protection group on NE 11.
1.
In NE Explorer, choose NE 11 from the object tree and choose Configuration > IF 1+1
Protection from Function Tree.
2.
In Protection Group, select the desired protection group and set Reversion Mode to NonRevertive.
3.
Click Apply.
4.
Click Close.
Step 2 Query the protection group status on NE 11 before switching.

1.
2.
In Protection Group, select the desired protection group and click Query.
3.
Ensure that Active NE of Device in Protection Group is NE 11.
Step 3 Test availability of the tested Ethernet services before switching. For details, see A.11.1 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.
Issue 02 (2012-12-30)

102

3.
Select the SHXA2 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.
2.
3.
Step 6 Test availability of the tested Ethernet services after switching. For details, see A.11.1 Testing
Ethernet Services. The value of LossRate in Test Result should be 0, indicating that the 1+1
protection switching is successful.
Step 7 Restore Reversion Mode to the original value.
----End
6.4.3 Testing PLA Protection Switching

You can verify the physical link aggregation (PLA) function by checking the changes of devices
and links in a PLA group before and after switching.
Prerequisites
l
PLA protection has been configured.
Enhanced link aggregation groups (E-LAGs) have been configured for OptiX RTN 310s,
and static LAGs have been configured for third-party devices.

U2000
Issue 02 (2012-12-30)

103


LAG
NE 11
NE 12
LAG
LAG
LAG
COMBO
COMBO
Antenna
NE 21
Antenna
NE 22
LAG
LAG
E-LAG
E-LAG
Microwave link
OptiX RTN 900

Ethernet link
Optical fiber
As shown in the preceding figure, the basic configurations are as follows:

l
NE 11 and NE 12 form a hop of microwave link.
The PLA configuration with E-LAG is used as an example.
Procedure
Step 1 Test the availability of the tested Ethernet services before switching. For details, see A.11.1
Testing Ethernet Services. The value of LossRate in Test Result should be 0.
1.
In NE Explorer, choose NE 11 from the object tree and choose Configuration >
Microwave Link Configuration from Function Tree.
2.
In RF, set TX Status to mute.
3.
Click Apply.
Step 3 Test the availability of the tested Ethernet services after switching. For details, see A.11.1
Testing Ethernet Services. The value of LossRate in Test Result should be 0, indicating that
the PLA protection switching is successful.
1.
2.
In RF, set TX Status to unmute.
3.
Click Apply.
----End
Issue 02 (2012-12-30)

104


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

U2000
NOTE
Context
The following procedure checks the clock status of NEs on a network.
Procedure
Step 1 Check the clock status of an NE.
Step 2 Repeat Step 1 to check the clock status of the other NEs on the network.
----End

The fade margin over a microwave link can be evaluated by measuring the mean square errors
(MSEs) at different received signal levels (RSLs).
Issue 02 (2012-12-30)

105

Prerequisites
l
Antennas have been aligned, and the RSLs at both ends of the microwave link and the crosspolarization discrimination (XPD) meet requirements.
The configured transmit power is the same as the actual transmit power.
Context
The procedure for testing the fade margin is as follows:
l
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.

U2000
NOTE
Context
The following procedure tests the fade margin over a microwave link.
Precautions
1.
When the fade margin is being tested, all the services carried on the microwave link may
be interrupted.
2.
For microwave links configured with 1+1 protection, lock the standby link before testing
the main link. Forcibly switch services to the standby link before testing it. The main and
standby links are tested simultaneously. Therefore, the fade margins of the main and
standby OptiX RTN 310s are reported at the same time.
3.
For cross polarization interference cancellation (XPIC) links, the links in the vertical
polarization direction and horizontal polarization direction are tested simultaneously.
Therefore, the fade margins of the main and standby OptiX RTN 310s are reported at the
same time.
Procedure
Step 1 Disable the adaptive modulation (AM) and automatic transmit power control (ATPC) functions
on the microwave link between two sites.
Issue 02 (2012-12-30)

106

Step 2 Test the fade margin over the microwave link.
Step 3 Enable the AM and ATPC functions for the microwave link base on Step 1.
NOTE
Restore Modulation Mode of the Guaranteed AM Capacity and Modulation Mode of the Full AM
Capacity to their initial values when enabling the AM function.
----End
6.7 Testing Ethernet Service Performance

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

This section describes how to test the latency, throughput, and packet loss ratio of VLAN-based
Ethernet line (E-Line) services with different frame lengths.
Issue 02 (2012-12-30)

107

Prerequisites
l
The source and sink NEs of the Ethernet services have been configured with VLAN-based
E-Line services.

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

The Ethernet services between PORT 2 on NE(92396) and PORT 2 on NE(92398) shown in
Figure 6-6 are tested. Both NE(92396) and NE(92398) are configured with VLAN-based ELine services.
PORT 2
NodeB
NE(9-2396)
NE(9-2398)
VLAN ID = 100
PORT 2
VLAN ID = 100
Microwave network
RNC
The Ethernet services between NE(92396) and NE(92398) carry the VLAN ID 100.
Procedure
Step 1 Configure the TAG attributes for the test ports.
Issue 02 (2012-12-30)

108

Step 2 Configure a sink NE for the test.
Step 3 Configure a source NE for the test and initiate the test.
Issue 02 (2012-12-30)

109

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

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

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

The Ethernet services between PORT 2 on NE(92396) and PORT 2 on NE(92398) shown in
Figure 6-7 are tested. Both NE(92396) and NE(92398) are configured with VLAN-based ELine services.
Issue 02 (2012-12-30)

110

PORT 2
NodeB
NE(9-2396)
NE(9-2398)
VLAN ID = 100
PORT 2
VLAN ID = 100
Microwave network
RNC
The Ethernet services between NE(92396) and NE(92398) carry the VLAN ID 100.
Procedure
Step 1 Configure the TAG attributes for the test ports.
Step 2 Configure a sink NE for the test.
Issue 02 (2012-12-30)

111

Step 3 Configure a source NE for the test and initiate the test.
NOTE
The test results may deviate from the actual values. When the number of received packets and that of sent packets
are different and the difference is less than a millionth, you can consider that no packet is lost.
----End
Issue 02 (2012-12-30)

112

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

Deployment
About This Chapter

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

113

7.1 When a USB Flash Drive Is Used for Loading

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

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

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

115

8 Configuring Networkwide Service Data
Configuring Networkwide Service Data
About This Chapter

This document uses configuration examples to describe the flow and procedure for configuring
the equipment. With this document, you can get familiar with the data configuration methods
and complete various configuration tasks in actual application.
8.1 Configuration Preparations
Before configuring the NE data, you must make the required preparations.
8.2 U2000 Quick Start
U2000 Quick Start describes basic operations on the U2000 client.
8.3 General Configuration Process
Select a proper configuration process based on the actual configuration scenarios.
8.4 Common Configuration Scenarios of Microwave Transmission Networks
This section describes two initial configuration scenarios: configuration on a microwave chain
network and configuration on a microwave ring network. To simply the description of
configuration examples of OptiX RTN 310, all initial configuration examples in this document
are based on the microwave chain network or the microwave ring network.
8.5 Configuring the Network Topology
You can manage a transport network by using the U2000 only after configuring the network
topology.
8.6 Configuring Microwave Links
Before configuring services on a microwave link, you need to configure the microwave link.
Native Ethernet services include Native Ethernet line (E-Line) services and Native Ethernet local
area network (E-LAN) services.
8.8 Configuring Clocks
To ensure that clocks of all the nodes on the transmission network are synchronized, configure
the clocks for these nodes according to a unified clock synchronization policy.
8.9 Adding and Modifying Configuration Data
Issue 02 (2012-12-30)

116

During the equipment commissioning and operating phases, you need to add or modify certain
configuration data according to the actual requirements.
Issue 02 (2012-12-30)

117

8.1 Configuration Preparations

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

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

Before beginning the configuration process, confirm that local conditions meet requirements.
Context
Ensure that the following requirements are met:
l
l
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 U2000 server and the gateway NE must be
normal.
The U2000 client can log in to the U2000 server and has network operator rights or higher.
8.2 U2000 Quick Start

U2000 Quick Start describes basic operations on the U2000 client.
8.3 General Configuration Process

Select a proper configuration process based on the actual configuration scenarios.
Issue 02 (2012-12-30)

118

Initial Configuration
Initial configuration of a microwave network refers to initial configuration of network-wide
service data using the network management system (NMS) after site commissioning is complete.
Figure 8-1 shows the configuration flowchart.
Figure 8-1 Flowchart for initial configuration
Start
Required
Optional
Configure the network

topology.
Configure microwave
links.
Configure Native
Ethernet services.
Configure the clock.
End
The steps in the configuration flowchart are described in Table 8-1.

Table 8-1 Initial configuration
Issue 02 (2012-12-30)
Operation
Remarks
8.5 Configuring the Network

Topology
Required.
Required.
8.7 Configuring Native Ethernet

Services
Required.
Required.

119

NOTE
The configuration sequence provided in Table 8-1 is for reference only and needs to be adjusted based on actual
scenarios. For detailed configuration methods based on local scenarios, see the configuration examples
corresponding to 8.4.1 Microwave Chain Network or 8.4.2 Microwave Ring Network.
Network Adjustment
Network adjustment involves adding and adjusting configuration data during the equipment
commissioning and operation phases. You can determine a task collection based on the actual
network adjustment requirements and then find the corresponding configuration operations from
the task collection.
Table 8-2 Network adjustment
Common Task Collection
Description
8.9.1 Common Task Collection

(Network Topology)
Lists configuration operations associated with NE

attributes, including changing the ID and IP address
of an NE.

(Microwave Links)
Lists configuration operations associated with

microwave links, including changing the basic
attributes and radio frequency (RF) attributes of
microwave links.

(Ethernet Services)
Lists configuration operations associated with

Ethernet services, including configuring or
modifying Ethernet port parameters and creating link
aggregation groups (LAGs).
8.4 Common Configuration Scenarios of Microwave

Transmission Networks
This section describes two initial configuration scenarios: configuration on a microwave chain
network and configuration on a microwave ring network. To simply the description of
configuration examples of OptiX RTN 310, all initial configuration examples in this document
are based on the microwave chain network or the microwave ring network.
8.4.1 Microwave Chain Network

Configuration examples are based on a microwave chain network that consists of OptiX RTN
310s and OptiX RTN 900s.
Network Topology
Figure 8-2 shows the networking diagram of the microwave chain network. On the network,
NE11, NE21, and NE23 receive Ethernet services, and NE99_1 and NE99_2 receive services
from the local backhaul network.
Issue 02 (2012-12-30)

120

Figure 8-2 Networking diagram of a microwave chain network

NMS
LAN switch
NE11
P&E
P&E
GE
NodeB 1
NE99_1
NE13
V-polarization
GE
Local backhaul
network
COMBO
COMBO
COMBO
XPIC&PLA
COMBO
GE
GE
RNC
P&E
NE12
H-polarization
NE14
P&E
GE
P&E
GE
P&E
NodeB 2
NE21
NE22
NE24
NE99_2
NE23
NodeB 3
OptiX RTN 900
Microwave link
Ethernet link
XPIC cable
NOTE
l NE99_1 and NE99_2 are OptiX RTN 900 NEs and they receive services from NE13 and NE24 through
the P&E ports on the EG4P boards. Configurations of NE99_1 and NE99_2 are not described in this
example.
l In the scenarios described in this section, 1+1 HSB/FD/SD protection is not configured. For details
about the configuration process, see Feature Description.
Configuration Examples
Table 8-3 provides examples for configuration on the microwave chain network.
Table 8-3 Configuration examples
Issue 02 (2012-12-30)
Step
Operation
Configuration Example
Configuring
the network
topology
8.5.3 Configuration Example (Microwave Chain

Network Topology)

121

Step
Operation
Configuring
microwave
links
8.6.3 Configuration Example (Microwave Links on a

Microwave Chain Network)
Configuring
Native Ethernet
services
8.7.5 Configuration Example (Transparently

Transmitted Point-to-Point E-Line Services)
8.7.6 Configuration Example (VLAN-based E-Line
Service)
8.7.8 Configuration Example (IEEE 802.1Q Bridgebased E-LAN Service)
Configuring
clocks
8.8.3 Configuration Example (Clock on a Microwave

Chain Network)
8.4.2 Microwave Ring Network

Configuration examples are based on a microwave ring network that contains six OptiX RTN
310 NEs on three sites.
Network Topology
Figure 8-3 shows the networking diagram of the microwave ring network. On the network,
NE36 and NE33 receive Ethernet services, and NE35 receives services from the local backhaul
network.
Figure 8-3 Networking diagram of a microwave ring network
NMS
NodeB 1
P&E
GE
NE31
LAN switch
GE
NE36
P&E
Local backhaul
network
RNC
GE
GE NE35
NE32
GE
GE
P&E
NodeB 2
NE33
Microwave link
Issue 02 (2012-12-30)
NE34
Ethernet link

122

Configuration Examples
Table 8-4 provides examples for configuration on the microwave ring network.
Table 8-4 Configuration examples
Step
Operation
Configuring the network

topology
8.5.4 Configuration Example (Microwave

Ring Network Topology)
Configuring microwave links
8.6.4 Configuration Example (Microwave

Links on a Microwave Ring Network)
Configuring Native Ethernet

services
8.7.7 Configuration Example (IEEE

802.1D Bridge-based E-LAN Service)
Configuring clocks
8.8.4 Configuration Example (Clock on a

Microwave Ring Network)
8.5 Configuring the Network Topology

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

Before configuring the network topology, familiarize yourself with the basic concepts.
8.5.1.1 DCN
To manage and maintain an NE, the U2000 needs to communicate with the NE through the data
communication network (DCN).
On a DCN, the U2000 and all the NEs are considered as nodes. The DCN between the U2000
and all the NEs is considered as the external DCN, and the DCN between the NEs is considered
as the internal DCN. OptiX RTN 310 supports the HWECC and IP DCN solutions. By default,
the IP DCN solution is used.
IP DCN is a DCN solution provided by Huawei. In this solution, network management system
(NMS) messages are encapsulated in the standard IP protocol stack and transmitted over DCN
channels between NEs so that the NMS can manage these NEs.
Figure 8-4 shows how NMS messages are transmitted using the IP DCN solution.
Issue 02 (2012-12-30)

123

Figure 8-4 Application of the IP DCN solution

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

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

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

124

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

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

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

125

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

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

126

8.5.1.4 NE ID and NE IP Address

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

You can obtain the clear fiber/cable connection relationship between NEs by using the fiber
management function of the U2000. You can also use the U2000 to manage fibers and cables,
including Ethernet fibers/cables, microwave links, extended ECC cables, and back-to-back radio
connections.
l
Ethernet fibers/cables
Ethernet fibers/cables refer to the Ethernet fiber/cable connections between Ethernet
optical/electrical ports on different sets of equipment.
Microwave links
Microwave links refer to the radio connections between different sets of radio equipment.
That is, the microwave links indicate the connection relationship between different IF ports.
l
Issue 02 (2012-12-30)
Extended ECC cables

127

Extended ECC cables refer to the extended ECC channels between the NEs. That is, the
extended ECC cables indicate the connection relationship between the NEs.
l
Back-to-back radio connections

Back-to-back radio connections refer to the NE cascading relationship. That is, the backto-back radio connections indicate the connection relationship between the NEs.
NOTE
Fibers and cables are topological objects on the U2000. Therefore, operations on the fibers or cables do not
affect the normal running of the NEs.
8.5.1.6 Subnet
NEs in the same domain or with similar attributes can be allocated to the same subnet. In this
manner, they can be displayed and managed as a whole on the U2000, which facilitates NE
management.
Subnets are topological objects on the U2000, but do not physically exist on networks. Therefore,
operations on subnets do not affect the normal running of NEs. Subnets simplify the main
topology on the U2000.
8.5.2 Configuration Process (Network Topology)

This section describes the processes of configuring the four topological objects: NEs, boards,
fibers/cables, and subnets.
Figure 8-7 shows the flowchart for configuring the network topology.
Issue 02 (2012-12-30)

128

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

monitoring status.
Create fibers/cables and
subnets.
End
NOTE
When the Web LCT is used for configuration, there is no need to create fibers/cables and subnets.
The steps in the configuration flowchart are described as follows:
Issue 02 (2012-12-30)

129

Creating NEs
Table 8-5 Process of creating NEs
Step
Operation
Creating NEs
on the U2000
Remarks
A.3.1.1
Creating an
NE by Using
the Search
Method
It is recommended that you perform this

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

operation to create NEs on the U2000 in other
cases. The following parameters need to be
set:
l Set Search Mode to Search for NE.
l Search Domain: When the IP address of
the gateway NE (GNE) is known, it is
recommended that you set the IP address
range of the GNE as the search domain.
In the case of initial configuration, it is
recommended that you set the
129.9.255.255 network segment as the
search domain.
l Search for NE: It is recommended that
you select Create NE after search, and
Upload after create. By default, NE
User is root and Password is password.
l Connection Mode: This parameter
specifies the connection mode between
the NMS and the gateway NE. For SSL
connection, set this parameter to Security
SSL.
A.3.2.1 Uploading NE Data
If you select Upload after create during A.

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

130

Configuring NE Attributes
Table 8-6 Process of configuring NE attributes
Step
Operation
Remarks
A.3.1.4
Changing
an NE ID

l Change New ID to be the NE ID specified during the data
communication network (DCN) planning.
l If the extended NE ID is required, change New Extended
ID.
A.3.1.5
Changing
an NE
Name
Optional.
Configuring DCCs
Table 8-7 Process of configuring DCCs
Step
Operation
Remarks
A.3.6.1
Setting NE
Communica
tion
Parameters

l In the case of the GNE, set IP and Subnet Mask according
to the planning of the external DCN.
l In the case of the GNE, set Gateway IP if the external
DCN requires.
l Generally, it is recommended that you set Connection
Mode to Common + Security SSL. If you need to set the
gateway NE to allow for NMS access only in SSL
connection mode, set Connection Mode to Security
SSL.
l In the case of non-GNEs, it is recommended that you set
IP Address to 0x81000000 + NE ID. That is, if the NE ID
is 0x090001, set IP Address to 129.9.0.1. Set Subnet
Mask to 255.255.0.0.
NOTE
If the IP address of an NE is not changed manually, the IP address
changes according to the NE ID and is always 0x81000000 + NE ID.
In this case, the IP address of a non-GNE does not need to be changed
manually.
Issue 02 (2012-12-30)
A.3.6.2
Configuring
DCCs
Disable related DCCs when using inband DCN channels.

131

Step
Operation
Remarks
A.3.6.7
Configuring
Extended
ECCs
Disable the automatic extended embedded control channel

(ECC) function for NEs that communicate with the NMS
through NMS ports.
A.3.6.3
Setting the
VLAN ID
and
Bandwidth
for an
Inband
DCN
Required if the OptiX RTN 310 equipment uses the inband

DCN solution and if the VLAN ID and bandwidth planned
for this inband DCN do not assume their default values (the
default VLAN ID is 4094 and the default bandwidth is 512
kbit/s).
A.3.6.5
Setting a
Port for an
Inband
DCN
A.3.6.9
Setting
OSPF
Protocol
Parameters
Optional. When a network consists of only OptiX RTN 310

NEs and uses a single Open Shortest Path First (OSPF) area,
it is recommended that you retain the default values for the
parameters.
A.3.6.6
Configuring
Access
Control
Optional.
l If inband DCN channels use the HWECC protocol, set

Protocol Type to HWECC. If inband DCN channels use
the IP protocol, set Protocol Type to IP.
l It is recommended that you set Enabled Status to
Disabled for the ports connected to customers' equipment.
When a gateway NE is connected to the NMS through a thirdparty network, enable the access control function for the
Ethernet port connected to the third-party network on the
gateway NE. In addition, set IP address and Subnet mask
for the port according to the network plan.
NOTE
The preceding DCN configuration process applies to a typical IP DCN solution configuration in a single OSPF
area. For the configuration process for an IP DCN solution containing special requirements or for another DCN
solution, see related descriptions in the Feature Description.
Issue 02 (2012-12-30)

132

Synchronizing NE Time
Table 8-8 Process of synchronizing NE time
Step
Operation
Synchroni
zing the
NE time
Remarks
A.3.1.6
Synchron
izing the
NE Time
Required.
l To synchronize the NEs with the NMS server, set
the relevant parameters as follows:
Set Synchronous Mode to NM.
Right-click and choose the operation from the
shortcut menu to ensure that the NE are
synchronized with the NMS time
immediately.
Set the synchronization parameters according
to the requirements. It is recommended that
the parameters adopt the default values.
l To synchronize the NEs with the Network Time
Protocol (NTP) server, set the relevant
parameters as follows:
Set Synchronous Mode to Standard NTP.
Set Standard NTP Authentication
according to the requirements for the NTP
server.
It is recommended that you set the upper level
NTP server that the NEs trace as follows:
In the case of the GNE, set the external
NTP server to the upper level NTP server.
Set Standard NTP Server Flag to IP and
set Standard NTP Server to the IP
address of the external NTP server.
In the case of a non-GNE, set the GNE to
the upper level NTP server. If the nonGNE needs to communicate with the GNE
through the HWECC protocol, set
Standard NTP Server Flag to NE ID and
set Standard NTP Server to the NE ID
of the GNE. If the non-GNE needs to
communicate with the GNE through the
IP protocol, set Standard NTP Server
Flag to IP and set Standard NTP
Server to the IP address of the GNE.
Set Standard NTP Server Key according
to the requirements for the NTP server.
A.3.1.7
Localizin
g the NE
Time
Issue 02 (2012-12-30)
Required if daylight saving time (DST) is used at the

local area.
Set the parameters according to the planning of DST
at the local area.

133

Step
Operation
Remarks
A.3.1.8
Configuri
ng a
Standard
NTP Key
Required if the standard NTP authentication is used

to synchronize the NEs with the NTP server.
Set the parameters according to the identification
authentication of the NTP.
NOTE
When the Web LCT is used, skip this operation because
this operation is included in A.3.1.6 Synchronizing the
NE Time.
Setting the Performance Monitoring Status

Table 8-9 Process of setting the performance monitoring status
Step
Operation
Remarks
A.3.3
Setting the
Performanc
e
Monitoring
Status for
an NE
If the 15-minute and 24-hour performance monitoring

functions are set to Disabled, enable these performance
monitoring functions.
Creating Fibers/Cables and Subnets

Table 8-10 Process of creating fibers/cables and subnets
Step
Operation
Creating
fibers/
cables
Issue 02 (2012-12-30)
Remarks
A.3.4.1
Creating
a Fiber/
Cable by
Using the
Search
Method
It is recommended that you perform this operation

to create fibers/cables.
A.3.4.2
Creating
a Fiber/
Cable
Manually
It is recommended that you perform this operation

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

network.

134

Step
Operation
Configuri
ng the
subnet
Remarks
A.3.5.1
Creating
a Subnet
Optional.
A.3.5.2
Copying a
Topology
Object
Optional.
A.3.5.3
Moving a
Topology
Object
Optional.
8.5.3 Configuration Example (Microwave Chain Network

Topology)
This section provides an example of how to configure a microwave chain network topology
according to the network plan.
8.5.3.1 Networking Diagram

This section describes the networking of NEs.
Figure 8-8 shows a microwave chain network configured according to the following
requirements:
l
The U2000 manages the microwave links on the network that consists of OptiX RTN
310s and OptiX RTN 900s.
The local backhaul network is a third-party network and cannot be managed together with
the OptiX RTN equipment. Therefore, NE99_1 and NE99_2 are set to be the gateway NEs
and they communicate with the U2000 using the access control function.
The NEs use the D1 to D3 bytes in microwave links or use part of the Ethernet bandwidth
in GE links for internal data communication network (DCN) communication which is
implemented using the IP protocol.
Issue 02 (2012-12-30)

135

Figure 8-8 Networking diagram (microwave chain network topology)

NMS
LAN switch
NE11
P&E
P&E
GE
NodeB 1
NE99_1
NE13
V-polarization
GE
Local backhaul
network
COMBO
COMBO
COMBO
XPIC&PLA
COMBO
GE
GE
RNC
P&E
NE12
H-polarization
NE14
P&E
GE
P&E
GE
P&E
NodeB 2
NE21
NE22
NE99_2
NE24
NE23
NodeB 3
OptiX RTN 900
Microwave link
Ethernet link
XPIC cable
NOTE
On the NMS, the logical port of a microwave port is 1-SHXA2-1(IF).
On the NMS, the logical port of a COMBO port that functions as an optical GE port is 1-SHXA2-2
(GE1).
On the NMS, the logical port of a P&E port is 1-SHXA2-2(GE1), when the COMBO port does not
function as an optical GE port.
On the NMS, the logical port of a GE port is 1-SHXA2-3(GE2).
On the NMS, the logical port of a COMBO port that functions as a 1+1 concatenation port is 1SHXA2-4. This port is valid only when DCN is being configured.
8.5.3.2 Service Planning

This section describes the parameters required for configuring a microwave chain network
topology.
l
This example uses the IP data communication network (DCN) solution.
To prevent adverse impact on base stations, the inband DCN function for service ports that
receive services from base stations must be disabled on all NEs.
The management VLAN ID and bandwidth of inband DCN are planned for each NE.
Issue 02 (2012-12-30)

136

The management VLAN ID takes the default value 4094, which is unique on the
network.
The inband DCN bandwidth takes the default value 512 kbit/s.
l
Figure 8-9 shows the ID and IP address that are allocated to each NE according to the DCN
plan.
Figure 8-9 Allocated IDs and IP addresses (microwave chain network)

NMS
LAN switch
NE11
9-11
129.9.0.11
0.0.0.0
NE13
9-13
129.9.0.13
0.0.0.0
9-12
129.9.0.12
0.0.0.0
NE12
9-14
129.9.0.14
0.0.0.0
NE14
9-21
129.9.0.21
0.0.0.0
NE21
9-22
129.9.0.22
0.0.0.0
NE22
Microwave link
Ethernet link
NE99_1
10.0.0.100
9-91
129.9.0.91
0.0.0.0
Local backhaul
network
RNC
9-24
129.9.0.24
0.0.0.0
9-23
129.9.0.23
0.0.0.0
NE24
9-92
129.9.0.92
0.0.0.0
NE99_2
NE23
XPIC cable
Extended ID-Basic ID
IP address
Gateway
NOTE
l The subnet mask for each NE IP address takes the same value 255.255.0.0.
l The access control function is enabled for the Ethernet port (IP address: 10.0.0.91) on NE99_1 and
the Ethernet port (IP address: 10.0.0.92) on NE99_2.
l The IP address allocated to each NE interlocks with the NE ID. Therefore, if the IP address of an NE
has not been changed manually, the NE automatically changes the IP address to the planned value
after the NE ID is changed.
l NE99_1 and NE99_2 are OptiX RTN 900 NEs, and therefore their configurations are not detailed in
this example.
The Open Shortest Path First (OSPF) protocol parameters take their default values.
In this example, the policy of synchronizing the NE with the network management system
(NMS) server is used. The automatic synchronization period is one day. Daylight saving
time (DST) is not used in the local area.
The 15-minute and 24-hour performance monitoring functions are enabled for all NEs.
In this configuration example, no subnet needs to be configured.
Issue 02 (2012-12-30)

137

8.5.3.3 Configuration Procedure

This section describes the procedure for configuring the network topology.
Precautions
If the NE ID and the NE communication parameter values were changed and the logical boards
were configured during the NE commissioning, skip these operations.
Procedure
Step 1 Create NEs manually. For details, see A.3.1.2 Creating an NE Manually.
This table provides parameter values for creating an NE manually.
Parameter
Value
Search Domain
Search for NE
IP Address
129.9.255.255
Search User
root
Create NE after search
Selected
Upload after create
Selected
NE User
root
Password
password
NOTE
The configuration example assumes that the IP address of the gateway NE has not been changed manually and
is unknown. The NEs are searched for by using the 129.9.255.255 network segment as the search domain. If the
IP address of the gateway NE is known, it is recommended that you use the IP address of the gateway NE as
the search domain.
The icons of NE11 to NE14 and NE21 to NE24 should be displayed on Main Topology and all
the NE data should be uploaded successfully.
Step 2 Change the NE IDs. For details, see A.3.1.4 Changing an NE ID.
This table provides parameter values for NE11 to NE14.
Parameter
Value
NE11
NE12
NE13
NE14
New ID
11
12
13
14
New Extended
ID
9 (default value)
9 (default value)
9 (default value)
9 (default value)

Issue 02 (2012-12-30)

138

Parameter
Value
NE21
NE22
NE23
NE24
New ID
21
22
23
24
New Extended
ID
9 (default value)
9 (default value)
9 (default value)
9 (default value)
Step 3 Set communication parameters for the NEs. For details, see A.3.6.1 Setting NE
Communication Parameters.
Parameter
Value
NE11
NE12
NE13
NE14
IP
129.9.0.11
129.9.0.12
129.9.0.13
129.9.0.14
Gateway IP
0.0.0.0 (default
value)
0.0.0.0 (default
value)
0.0.0.0 (default
value)
0.0.0.0 (default
value)
Subnet Mask
255.255.0.0
(default value)
255.255.0.0
(default value)
255.255.0.0
(default value)
255.255.0.0
(default value)
Extended ID
Connection
Mode
Common
+Security SSL
Common
+Security SSL
Common
+Security SSL
Common
+Security SSL

Parameter
Value
NE21
NE22
NE23
NE24
IP
129.9.0.21
129.9.0.22
129.9.0.23
129.9.0.24
Gateway IP
0.0.0.0 (default
value)
0.0.0.0 (default
value)
0.0.0.0 (default
value)
0.0.0.0 (default
value)
Subnet Mask
255.255.0.0
(default value)
255.255.0.0
(default value)
255.255.0.0
(default value)
255.255.0.0
(default value)
Extended ID
Connection
Mode
Common
+Security SSL
Common
+Security SSL
Common
+Security SSL
Common
+Security SSL
Step 4 Configure ports for the inband data communication network (DCN). For details, see A.3.6.5
Setting a Port for an Inband DCN.
This table provides parameter values for NE11, NE21, and NE23.
Issue 02 (2012-12-30)

139

Parameter
Value
Enabled/Disabled
1-SHXA2-2
Other Ports
Disabled
Enabled (default value)
Step 5 Synchronize the NE time. For details, see A.3.1.6 Synchronizing the NE Time.
This table provides parameter values for synchronizing the NE time.
Parameter
Value
All the Ports on All the NEs
Synchronous Mode
NM
Period (days)
Step 6 Create fibers/cables by using the search method. For details, see A.3.4.1 Creating a Fiber/Cable
by Using the Search Method.
Normally, all the microwave link and Ethernet fibers/cables are created successfully on Main
Topology.
Step 7 Create a back-to-back radio connection. For details, see A.3.4.4 Creating a Back-to-back
Radio Connection.
This table provides parameter values for creating a back-to-back radio connection.
Parameter
Value
Source NE
NE22
Sink NE
NE23
----End
8.5.4 Configuration Example (Microwave Ring Network Topology)

This section provides an example of how to configure a microwave ring network topology

Figure 8-10 shows the network topology of a microwave ring network configured according to
the following requirements:
l
Issue 02 (2012-12-30)
The network contains six OptiX RTN 310 NEs located at three sites. The NEs are managed
by the U2000.
140

The local backhaul network is a third-party network and cannot be managed together with
the OptiX RTN equipment. Therefore, NE35 is configured as the gateway NE and it
communicates with the U2000 using the access control function.
The NEs use the D1 to D3 bytes in microwave links or use part of the Ethernet bandwidth
in GE links for internal data communication network (DCN) communication which is
implemented using the IP protocol.
Figure 8-10 Networking diagram (microwave ring network topology)
NMS
NodeB 1
P&E
GE
NE31
LAN switch
GE
NE36
P&E
Local backhaul
network
RNC
GE
GE NE35
NE32
GE
GE
P&E
NodeB 2
NE33
Microwave link
NE34
Ethernet link
NOTE
(GE1).

This section describes the parameters required for configuring a microwave ring network
topology.
l
Issue 02 (2012-12-30)
This example uses the IP data communication network (DCN) solution.

141

To prevent adverse impact on base stations, the inband DCN function for service ports that
receive services from base stations must be disabled on all NEs.
The management VLAN ID and bandwidth of inband DCN are planned for each NE.
The management VLAN ID takes the default value 4094, which is unique on the
network.
The inband DCN bandwidth takes the default value 512 kbit/s.
Figure 8-11 shows the ID and IP address that are allocated to each NE according to the
DCN plan.
Figure 8-11 Allocated IDs and IP addresses (microwave ring network)

NMS
NE31
9-31
129.9.0.31
0.0.0.0
NE36
LAN switch
9-36
129.9.0.36
0.0.0.0
9-32
129.9.0.32
0.0.0.0
10.0.0.100
9-35
129.9.0.35
0.0.0.0
NE32
Local backhaul
network
NE35
9-33
129.9.0.33
0.0.0.0
9-34
129.9.0.34
0.0.0.0
NE33
NE34
Microwave link
Ethernet link
RNC
Extended ID-Basic ID
IP address
Gateway
NOTE
l The subnet mask for each NE IP address takes the same value 255.255.0.0.
l The access control function for port GE1 (IP address: 10.0.0.35) of NE35 is enabled.
l The IP address allocated to each NE interlocks with the NE ID. Therefore, if the IP address of an NE
has not been changed manually, the NE automatically changes the IP address to the planned value
after the NE ID is changed.
The Open Shortest Path First (OSPF) protocol parameters take their default values.
In this example, the policy of synchronizing the NE with the network management system
(NMS) server is used. The automatic synchronization period is one day. Daylight saving
time (DST) is not used in the local area.
The 15-minute and 24-hour performance monitoring functions are enabled for all NEs.
In this configuration example, no subnet needs to be configured.

This section describes the procedure for configuring a microwave ring network topology.
Issue 02 (2012-12-30)

142

Precautions
If the NE ID and the NE communication parameter values were changed and the logical boards
were configured during the NE commissioning, skip these operations.
Procedure
Step 1 Create NEs manually. For details, see A.3.1.2 Creating an NE Manually.
This table provides parameter values for creating an NE.
Parameter
Value
Search Domain
Search for NE
IP Address
129.9.255.255
Search User
root
Create an NE after it is
found.
Selected
Upload after create
Selected
NE User
root
Password
password
NOTE
In this configuration example, it is assumed that the IP address of the gateway NE has not been changed manually
and is unknown. The NEs are searched for by using the 129.9.255.255 network segment as the search domain.
If the IP address of the gateway NE is known, it is recommended that you use the IP address of the gateway NE
as the search domain.
Normally, the icons of NE31 to NE36 are displayed on Main Topology and all the NE data are
uploaded successfully.
Step 2 Change the NE IDs. For details, see A.3.1.4 Changing an NE ID.
This table provides parameter values for changing the NE IDs.
Paramete
r
Value
NE31
NE32
NE33
NE34
NE35
NE36
New ID
31
32
33
34
35
36
New
Extended
ID
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
Step 3 Set communication parameters for the NEs. For details, see A.3.6.1 Setting NE
Communication Parameters.
This table provides communication parameter values.
Issue 02 (2012-12-30)

143

Paramete
r
Value
NE31
NE32
NE33
NE34
NE35
NE36
IP
129.9.0.31
129.9.0.32
129.9.0.33
129.9.0.34
129.9.0.35
129.9.0.36
Gateway
IP
0.0.0.0
(default
value)
0.0.0.0
(default
value)
0.0.0.0
(default
value)
0.0.0.0
(default
value)
0.0.0.0
(default
value)
0.0.0.0
(default
value)
Subnet
Mask
255.255.0.
0 (default
value)
255.255.0.
0 (default
value)
255.255.0.
0 (default
value)
255.255.0.
0 (default
value)
255.255.0.
0 (default
value)
255.255.0.
0 (default
value)
Extended
ID
Connectio
n Mode
Common
+Security
SSL
Common
+Security
SSL
Common
+Security
SSL
Common
+Security
SSL
Common
+Security
SSL
Common
+Security
SSL
Step 4 Configure access control. For details, see A.3.6.6 Configuring Access Control.
This table provides parameter values for configuring access control for NE35.
Parameter
Value
1-SHXA2-2
Enabled/Disabled
Enabled
IP
10.0.0.35
Subnet Mask
255.255.0.0
Step 5 Configure ports for the inband data communication network (DCN). For details, see A.3.6.5
Setting a Port for an Inband DCN.
This table provides parameter values for NE33 and NE36.
Parameter
Value
Enabled/Disabled
1-SHXA2-2
Other Ports
Disabled
Step 6 Synchronize the NE time. For details, see A.3.1.6 Synchronizing the NE Time.
This table provides parameter values for synchronizing the NE time.
Issue 02 (2012-12-30)

144

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

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

Before configuring a microwave link, familiarize yourself with the basic concepts.
8.6.1.1 Adaptive Modulation

Adaptive modulation (AM) technology automatically adjusts the modulation scheme based on
channel quality.
When AM technology is enabled and the same channel spacing is used, the available radio
service bandwidth varies according to the modulation scheme: the higher the modulation
efficiency, the higher the bandwidth of the transmitted services. With quality of service (QoS)
technology, packet services are groomed to queues with different priorities. Services in different
queues are then transmitted to the microwave port after the queue-scheduling algorithm has been
run. The service capacity varies according to the modulation scheme regardless of channel
conditions.
Issue 02 (2012-12-30)

145

When channel conditions are favorable (such as on sunny days), the equipment uses a
higher-order modulation scheme to transmit more user services. This improves
transmission efficiency and spectrum utilization of the system.
When channel conditions are unfavorable (such as on stormy or foggy days), the equipment
uses a lower-order modulation scheme to ensure that higher-priority services are
transmitted first. If some lower-priority queues become congested due to a lack of available
bandwidth, some or all interfaces in these queues are discarded. This method improves the
anti-interference capabilities of a microwave link and ensures link availability for highpriority services.
Figure 8-12 shows how the modulation scheme shifts step by step according to weather changes
and how modulation schemes affect service throughput and reliability. In this example, the
modulation scheme of guaranteed AM capacity is QPSK Strong and the modulation scheme of
full AM capacity is 256QAM.
Figure 8-12 Adaptive modulation
256
QAM
128
64
32
QAM QAM
QAM
16
16
32
16
16 QAM
QAM
QAM
QPSK
QAM Strong
Strong QAM
QPSK
QPSK
Strong
128
64
QAM QAM
RSL
Availability
99.5%
256 QAM
128 QAM
99.9%
64 QAM
99.92%
32 QAM
99.96%
16 QAM
16 QAM strong
256
QAM
Low-priority
service
Low-priority
service
99.99%
99.995%
99.998%
QPSK
99.999%
QPSK strong
High-priority service
Time
The AM technology used by OptiX RTN 310 has the following features:
l
Issue 02 (2012-12-30)
Uses QPSK Strong, QPSK, 16QAM Strong, 16QAM, 32QAM, 64QAM, 128QAM,
256QAM, 512QAM, 512QAM Light, 1024QAM, 1024QAM Light, and 2048QAM
modulation schemes. Compared with QPSK/16QAM, QPSK Strong/16QAM Strong, using
different parameters in forward error correction (FEC) coding, has stronger error correction
146

capability, and therefore has better receiver sensitivity. It has, however, less air interface
bandwidth. Compared with 512QAM/1024QAM, 512QAM Light/1024QAM Light, using
different parameters in forward error correction (FEC) coding, has weaker error correction
capability, and therefore has worse receiver sensitivity. It has, however, higher air interface
bandwidth.
l
Can configure both the lowest-order modulation scheme (also called reference scheme or
modulation scheme of guaranteed AM capacity) and the highest-order modulation scheme
(also called nominal scheme or modulation scheme of full AM capacity).
Can switch modulation schemes without changing the transmit frequency, receive
frequency, or channel spacing.
Switches modulation schemes step-by-step.
Features hitless switching. When the modulation scheme is downshifted, high-priority

services are not affected while low-priority services are discarded. Switching is successful
even when 100 dB/s channel fast fading occurs.
8.6.1.2 CCDP and XPIC

Co-channel dual polarization (CCDP) and cross polarization interference cancellation (XPIC)
have been developed based on the characteristics of microwave polarization. CCDP doubles
transmission capacity by transmitting two channels of signals over two orthogonally polarized
waves, and XPIC eliminates interference between the two waves.
Microwave transmission can be classified as single-polarized transmission and CCDP
transmission.
l
In single-polarized transmission, one channel of signals is transmitted over a horizontally

or vertically polarized wave. See Figure 8-13.
In CCDP transmission, two channels of signals of the same frequency are transmitted over
the horizontally polarized wave and the vertically polarized wave on a channel. See Figure
8-14.
The capacity of CCDP transmission is twice that of single-polarized transmission.

Figure 8-13 Single-polarized transmission
Figure 8-14 CCDP transmission
Issue 02 (2012-12-30)

147

If conditions were perfect, there would be no interference between the two channels of signals,
and the receiver could easily recover the original signals. In reality, however, there is always
interference caused by antenna cross-polarization discrimination (XPD) and channel
deterioration. XPIC eliminates this interference and enables a receiver to recover the original
signals.
8.6.1.3 RF Configuration Modes

OptiX RTN 310 supports four basic radio frequency (RF) configurations: 1+0 non-protection
configuration, 1+1 protection configuration, 2+0 non-protection configuration, and cross
polarization interference cancellation (XPIC) configuration.
1+0 Non-Protection Configuration

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

The 1+1 protection configuration indicates that the microwave link has one working channel
and one protection channel.
The 1+1 protection configuration is classified into 1+1 hot standby (HSB), 1+1 frequency
diversity (FD), and 1+1 space diversity (SD).
l
Issue 02 (2012-12-30)
1+1 HSB provides 1+1 hot standby protection for the OptiX RTN 310 at the two ends of
a microwave link hop.

148

Figure 8-16 Typical configuration of 1+1 HSB protection

RNC
RAN
LAG
LAG
NE1
LAG
COMBO
COMBO
COMBO
COMBO
LAG
NE4
NE2
OptiX RTN 900
NE3
Radio link
LAG
LAG
Ethernet link
1+1 FD uses two channels with a frequency spacing in between to receive and transmit the
same services. The receive end selects the channel with better quality service signals. With
1+1 FD protection, the impact of signal transmission fading is reduced.
The 1+1 FD protection also supports the 1+1 HSB protection.
Figure 8-17 Typical configuration of 1+1 FD protection

RNC
RAN
LAG
LAG
LAG
NE1
Issue 02 (2012-12-30)
LAG
COMBO
COMBO
COMBO
COMBO
NE4
NE2
OptiX RTN 900
NE3
Radio link
LAG
LAG
Ethernet link
1+1 SD uses two antennas at different heights to receive the same services. The receive
end selects the channel with better quality service signals. With 1+1 SD protection, the
impact of signal transmission fading is reduced.
149

The 1+1 SD protection also supports the 1+1 HSB protection.

Figure 8-18 Typical configuration of 1+1 SD protection
RNC
RAN
LAG
LAG
LAG
NE1
NE3
LAG
COMBO
COMBO
COMBO
COMBO
NE4
NE2
OptiX RTN 900
Radio link
LAG
LAG
Ethernet link
2+0 Non-Protection Configuration

The 2+0 non-protection configuration indicates that the microwave link has two working
channels and no protection channel.
Figure 8-19 Typical configuration of 2+0 non-protection (with PLA configured with NE-level
protection)
RNC
RAN
LAG
NE3 LAG
LAG NE1
GE
GE
GE
GE
LAG NE2
OptiX RTN 900
Issue 02 (2012-12-30)
NE4
Radio link

LAG
LAG
Ethernet link
150

NOTE
PLA protection is often configured for NEs in a 2+0 non-protection group.
XPIC Configuration
The XPIC adopts both the horizontally polarized wave and the vertically polarized wave over
one channel to transmit two channels of signals. Therefore, the microwave link capacity in XPIC
configuration is double the microwave link capacity in 1+0 configuration.
Figure 8-20 Typical configuration of the XPIC
V-polarization
COMBO
COMBO
COMBO
COMBO
Antenna
Antenna
H-polarization
8.6.1.4 PLA
Physical Link Aggregation (PLA) aggregates all Ethernet bandwidth across several microwave
links between two NEs into a logical path to achieve higher Ethernet bandwidth.
Different from air-interface link aggregation group (LAG), PLA dynamically allocates Ethernet
traffic, based on the Ethernet service bandwidth over each member microwave link, to achieve
load sharing between member microwave links. PLA can use the load sharing mode regardless
of whether member microwave links use the same Ethernet frame type or length or provide the
same Ethernet bandwidth. PLA ensures equivalent Ethernet bandwidth utilization between
member microwave links even when the Ethernet bandwidth on each member link changes.
Figure 8-21 PLA
Microwave link 1
Ethernet
channel
GE
PLA
GE
Ethernet
channel
Microwave link 2
Issue 02 (2012-12-30)

151

OptiX RTN 310 supports two configuration modes: PLA with NE-level protection and PLA
without NE-level protection. The protection scopes of the two configuration modes are different.
l
PLA without NE-level protection protects microwave links, but not radio equipment.
In PLA with NE-level protection, LAG is configured for the service source and equipment
protection is configured for access equipment. Both microwave links and access equipment
are protected. This configuration requires the service source (an IDU or UNI equipment)
to provide two access ports and to support a static LAG. The LAG of the service source
and the equipment protection on the OptiX RTN 310 equipment cooperate to implement
protection switching for both equipment and Ethernet access links.
8.6.1.5 E-LAG
When switching occurs on the NEs in a 1+1 HSB/SD/FD or physical link aggregation (PLA)
group, an enhanced link aggregation group (E-LAG) is required to implement switching for
active and standby GE access links (HSB is short for hot standby, SD for space diversity, and
FD for frequency diversity).
Introduction
E-LAG is a mechanism that implements multi-chassis link aggregation using the Link
Aggregation Control Protocol (LACP). It enhances Ethernet link reliability from the port level
to the equipment level.
As shown in Figure 8-22, two OptiX RTN 310s form a 1+1 HSB/FD/SD or PLA group. A static
link aggregation group (LAG) that has only the master port is configured on each of the OptiX
RTN 310s. The master and slave OptiX RTN 310s exchange 1+1 HSB/FD/SD or PLA protection
protocol packets so that the LAGs on them form a multi-chassis E-LAG. A static, non-load
sharing, and non-revertive LAG must be configured on the IDU (or UNI equipment) connected
to the OptiX RTN 310s. This LAG works with the 1+1 HSB/FD/SD or PLA group to implement
switching for the active and standby GE access links.
Figure 8-22 E-LAG application
LAG
LAG
LAG
GE
GE
Cascade
cable
IDU
GE
LAG
Cascade
cable
Antenna
GE
Antenna
LAG
E-LAG
IDU
LAG
E-LAG
Principles
NOTE
This section describes the E-LAG implementation at the transmit end shown in Figure 8-22. The E-LAG
implementation at the receive end is similar.
Issue 02 (2012-12-30)

152

1.
Before E-LAG switching

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

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

system priority
2.
E-LAG switching
When switching occurs on NE 1 and NE 2, they exchange the LAG system priorities, and
the 1+1 HSB/FD/SD or PLA protection protocol sets the highest LAG system priority on
NE 2. According to the LACP renegotiation results, the link between NE 1 and the IDU is
in the Unselected state, and the link between NE 2 and the IDU is in the Selected state. As
a result, the IDU transmits services only to NE 2.
Issue 02 (2012-12-30)

153

Figure 8-24 E-LAG switching

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

system priority
Feature Dependencies and Limitations

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

The U2000 supports the hop management function, which allows for the simultaneous
modification of the NEs at the two ends of a hop.
Hop management applies to microwave links using either the 1+0 non-protection configuration
or the cross polarization interference cancellation (XPIC) configuration. If a microwave link is
not working correctly, the basic information about the peer NE is not displayed.
The following parameters on the local and peer NEs on a microwave link hop are automatically
correlated: Link ID, IF Channel Bandwidth, AM, Modulation Mode of the Guaranteed AM
Capacity, Modulation Mode of the Full AM, and T/R Spacing (MHz). If any of the preceding
parameters is modified on one NE, the corresponding parameter is automatically modified on
the peer NE.
The following figure shows the window for configuring the hop management function.
Issue 02 (2012-12-30)

154

8.6.2 Configuration Process (Microwave Links)

This section describes the processes of configuring the hop management function, power,
IEEE-1588 timeslot status (enabled or disabled), and other parameters for a microwave link.
Figure 8-25 shows the flowchart for configuring microwave links.
Issue 02 (2012-12-30)

155

Figure 8-25 Flowchart for configuring microwave links

Required
Start
Optional
Create a microwave 1+1 protection group.
Create a PLA group.
Configure a hop of microwave link.
Configure Ethernet frame header

compression and errored frame discarding
over air interfaces.
Set the maximum transmit power and the

power thresholds.
Enable/Disable IEEE-1588 timeslots.
Create a microwave link after it is found.
End
The steps in the flowchart are described as follows:
Issue 02 (2012-12-30)

156

Configuring Microwave Links

Table 8-11 Process of configuring microwave links
Step
Operation
Creating a
microwave
1+1
protection
group
Remarks
Deleting the
Ethernet
port that
does not
participate in
1+1
protection
from the
bridge of the
E-LAN
service or
deleting the
E-Line
service on the
Ethernet
port that
does not
participate in
1+1
protection
Required when 1+1 protection is required for

microwave links.
A.7.2.1
Creating a
LAG
Required when 1+1 protection is required for

microwave links.
Required. Do not configure Ethernet services

on the Ethernet port that does not participate
in 1+1 protection. If you configure Ethernet
services on the Ethernet port, 1+1 protection
configuration will fail.
NOTE
By default, an OptiX RTN 310 creates a bridgebased E-LAN service. All ports of the OptiX RTN
310 are mounted to the bridge. Therefore, you must
delete the Ethernet port that does not participate in
1+1 protection from the bridge. If an E-Line service
has been configured on the Ethernet port that does
not participate in 1+1 protection, delete the E-Line
service.
Required. Configure a LAG on each of the

main OptiX RTN 310s and each of the standby
OptiX RTN 310s. The LAG has only one
member port that receives and transmits
Ethernet services.
Set parameters as follows:
l Set LAG Type to Static.
l Set Reversion Mode to Non-Revertive.
l Set Load Balancing to Non-Sharing.
l Set Master Port to the port that receives
and transmits Ethernet services. Do not set
Standby Ports.
Issue 02 (2012-12-30)

157

Step
Operation
Remarks
Creating a
Microwave 1
+1 Protection
Group
Optional. Set parameters as follows:

l Set Working Mode according to the
network plan.
l Set Working/Protection Unit Type to
Working Unit for the main OptiX RTN
310 and Protection Unit for the standby
OptiX RTN 310.
l It is recommended that you set Reversion
Mode to the default value Revertive
Mode.
l WTR Time(s) is available only when
Reversion Mode is set to Revertive
Mode.
l It is recommended that you set Enable
Reverse Switching to Disabled, and then
to Enabled after the 1+1 protection status
is stable.
l Set Service port to the same value as
Master Port that you set during link
aggregation group (LAG) creation.
l Set Working Mode, Reversion Mode,
WTR Time(s), and Enable Reverse
Switching to the same values for the OptiX
RTN 310s at both ends of the hop of
microwave link.
NOTE
If 1+1 protection configuration fails, check that:
l Working Mode is set to the default value AutoNegotiation for Service port on the main and
standby OptiX RTN 310s.
l Logical Port Attribute of the P&E electrical
port (1-SHXA2-2) takes the default value
Electrical Port.
l Ethernet services are configured only on
Service port involved in 1+1 protection.
l No feature that conflicts with 1+1 protection,
such as cross polarization interference
cancellation (XPIC) or physical link
aggregation (PLA), is configured.
l The COMBO ports on the main and standby
OptiX RTN 310s are properly connected using
an optical fiber.
Issue 02 (2012-12-30)

158

Step
Operation
Creating a
PLA group
Remarks
Deleting the
Ethernet
port that
does not
participate in
1+1
protection
from the
bridge of the
E-LAN
service or
deleting the
E-Line
service on the
Ethernet
port that
does not
participate in
1+1
protection
Required.
A.7.2.1
Creating a
LAG
Required when a microwave link requires

PLA with NE-level protection. Set parameters
as follows:
Delete Ethernet services on the cascade ports

between the master and slave NEs before
configuring PLA, because Ethernet services
are not allowed on the ports during PLA
configuration.
l Set LAG Type to Static.

l Set Reversion Mode to Non-Revertive.
l Set Load Balancing to Non-Sharing.
l Set Master Port to the port that receives
and transmits Ethernet services. Do not set
Standby Ports.
Issue 02 (2012-12-30)

159

Step
Operation
Remarks
Creating a
PLA Group
Required when a microwave link requires

PLA. Set parameters as follows:
l If NE-level protection is required, set
Protection Type to NE-level LAG
protection. Set Service Port to the same
port ID for the master and slave NEs, and
ensure that the ports are both GE electrical
ports or GE optical ports. Set Working
Mode to Auto-Negotiation.
l If NE-level protection is not required, set
Protection Type to No NE-level
protection, and set Service Port only for
the master NE.
l Set NE Role to Active and Standby for the
master and slave NEs respectively.
l Set Cascade Port to the same port ID for
the master and slave NEs, and ensure that
the ports are both GE electrical ports or GE
optical ports.
Issue 02 (2012-12-30)

160

Step
Operation
Remarks
A.5.1 Configuring a Single

Hop of Microwave Link

l Link ID, IF Channel Bandwidth, AM,
Modulation Mode of the Guaranteed
AM Capacity, Modulation Mode of the
Full AM, and T/R Spacing (MHz) of the
local NE and the peer NE on a hop of
microwave link are automatically
correlated. If any of the preceding
parameters is modified on one NE, the
parameter on the peer NE is automatically
modified accordingly.
l Set Link ID, TX Frequency (MHz), TX
Power (dBm), and T/R Spacing (MHz)
l Set the transmit status to unmute.
l Set Power to Be Received(dBm) to the
received signal level specified in the
network plan. The antenna non-alignment
indication function is enabled only after
this parameter is set. When the antenna
misalignment indicating function is
enabled, if the actual receive power is 3 dB
lower than the power expected to be
received, the RADIO_RSL_BEYONDTH
alarm is reported. After the antennas are
aligned for consecutive 30 minutes, the NE
automatically disables the antenna nonalignment indication function.
NOTE
l All parameters on the main and standby NEs in
a 1+1 HSB or space diversity (SD) protection
group must be set consistently.
l IF parameters on the main and standby NEs in
a 1+1 frequency (FD) protection group must be
set consistently. The radio frequency (RF)
parameters can be set differently.
l Data on the two main NEs at the ends of a hop
of microwave link must correspond with each
other. So does the data on the standby NEs.
Configuring Ethernet
frame header compression
and errored frame
discarding over air
interfaces
Required when the Ethernet frame header

compression function is enabled for air
interfaces or errored Ethernet frames are
configured not to be discarded.
Set the parameters according to the service
plan.
NOTE
Configurations on the main and standby NEs in a
PLA/1+1 protection group must be the same.
Issue 02 (2012-12-30)

161

Step
Operation
Remarks
A.5.10 Setting the

Maximum Transmit Power
and the Power Thresholds
Optional.
Set Maximum Transmit Power according to
the network plan when the ATPC function is
enabled. If you want to calculate how long the
transmit/receive power remains within the
maximum and minimum power thresholds,
you can set the power thresholds.
NOTE
Configurations on the main and standby NEs in a 1
+1 protection group must be the same.
A.8.2.1 Enabling/Disabling
the IEEE-1588 Timeslot for
a Microwave Port
Required when the microwave port transmits

IEEE 1588v2 packets.
Set Enable IEEE-1588 Timeslot to
Enabled.
NOTE
Configurations on the main and standby NEs in a
PLA/1+1 protection group must be the same.
A.3.4.1 Creating a Fiber/

Cable by Using the Search
Method
In normal cases, Main Topology displays the

previously created microwave links.
NOTE
l The preceding parameters need to be set separately but set to the same values for the microwave links in the
vertical and horizontal polarization directions.
l The MW_CFG_MISMATCH alarm is reported if the adaptive modulation (AM) status (enabled or disabled),
1588 timeslot status (enabled or disabled), or modulation scheme is set inconsistently at the two ends of a
microwave link. This alarm should be cleared immediately. Otherwise, services may be configured
unsuccessfully or interrupted.
8.6.3 Configuration Example (Microwave Links on a Microwave

Chain Network)
This section provides an example of how to configure microwave links on a microwave chain
network according to the network plan.

Based on 8.5.3 Configuration Example (Microwave Chain Network Topology), configure
the microwave links on a microwave chain network according to the following requirements.
Figure 8-26 shows the networking diagram.
l
Issue 02 (2012-12-30)
To increase the bandwidth for transmitting services from NodeB, enable the cross
polarization interference cancellation (XPIC) function for the microwave links between
NE11 and NE13 and between NE12 and NE14.
162

To balance the Ethernet bandwidth utilization on links, configure PLA for the microwave
links between NE11 and NE13 and for those between NE12 and NE14. The PLA for NE11
and NE12 does not need to provide NE-level protection whereas the PLA for NE13 and
NE14 does.
Enable adaptive modulation (AM) for all microwave links except for the links configured
with the XPIC function. All microwave links carry Ethernet services.
The service capacity transmitted by each NodeB is provided in Table 8-12.

Table 8-12 Service capacity transmitted by each NodeB
Service Capacity
NodeB 1
NodeB 2
NodeB 3
Capacity of highpriority Ethernet

services (Mbit/s)
90
15
24
Capacity of lowpriority Ethernet

services (Mbit/s)
NOTE
High-priority services require transmission guarantees and must not be discarded in modulation scheme
shifts. Low-priority services do not require transmission guarantees and can be discarded in modulation
scheme shifts. Common service priorities are provided in Table 8-13.
Table 8-13 Common service priorities
Issue 02 (2012-12-30)
Service Type
Priority
Voice, signaling, and O&M Ethernet

services
High
Streaming media, background, and

interactive Ethernet services, for example,
Internet services
Low

163

Figure 8-26 Networking diagram (microwave links on a microwave chain network)

NMS
101
14930 MHz
14510 MHz
28 MHz
1+0
V-polarization
NE11
P&E
GE
NodeB 1
TX high site
LAN switch
NE13
P&E
GE
TX low site
COMBO
COMBO
COMBO
COMBO
TX high site TX low site

GE
NE12
102
14930 MHz
14510 MHz
28 MHz
1+0
H-polarization
TX low site
Local backhaul
network
NE99_1
GE
P&E
RNC
NE14
TX high site
TX low site
TX high site
NE99_2
NE24
NodeB 2
NE21
NE22
201
14947 MHz
14527 MHz
7 MHz
1+0
V-polarization
OptiX RTN 900
NE23
202
14952 MHz
14532 MHz
14 MHz
1+0
H-polarization
Link ID
TX frequency at a TX high site
TX frequency at a TX low site
Channel spacing
RF configuration
Polarization
NodeB 3
Microwave link
Ethernet link
XPIC cable

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

You can obtain basic information about microwave links based on the spectrum allocation on
the microwave network and the required radio transmission capacity, as listed in Table 8-14.
Table 8-14 Basic information about microwave links
Issue 02 (2012-12-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Link ID
101
102
201
202
TX high site
NE11
NE12
NE21
NE23
TX low site
NE13
NE14
NE22
NE24

164

Parameter
Link 1
Link 2
Link 3
Link 4
TX frequency
at the TX high
site (MHz)
14930
14930
14947
14952
TX frequency
at the TX low
site (MHz)
14510
14510
14527
14532
T/R Spacing
(MHz)
420
420
420
420
Radio working
mode
28
28
14
RF
configuration
mode
XPIC
XPIC
1+0
1+0
Polarization
direction
V (vertical
polarization)
H (horizontal
polarization)
V (vertical
polarization)
H (horizontal
polarization)
AM Attribute Information
You can compute adaptive modulation (AM) attribute information based on Ethernet service
capacity and availability requirements, as listed in Table 8-15.
Table 8-15 AM attribute information
Parameter
Link 1
Link 2
Link 3
Link 4
AM
Disabled
Disabled
Enabled
Enabled
Modulation
Mode of the
Guaranteed
AM Capacity
QPSK Strong
QPSK Strong
Modulation
Mode of the
Full AM
32QAM
64QAM
Modulation
Mode
128QAM
128QAM
NOTE
Both the radio capacity and the AM function require a corresponding license file.
Issue 02 (2012-12-30)

165

Power and ATPC Information

You can obtain information about the microwave link power and automatic transmit power
control (ATPC) by using microwave network planning software such as Pathloss, as listed in
Table 8-16.
Table 8-16 Power and ATPC information
Parameter
Link 1
Link 2
Link 3
Link 4
TX power
(dBm)
16 (NE11)
16 (NE12)
16.5 (NE21)
20 (NE23)
16 (NE13)
16 (NE14)
16.5 (NE22)
20 (NE24)
RX power
(dBm)
-46 (NE11)
-46 (NE12)
-43 (NE21)
-48 (NE23)
-46 (NE13)
-46 (NE14)
-43 (NE22)
-48 (NE24)
ATPC
Disabled
Disabled
Disabled
Disabled
ATPC upper
threshold
(dBm)
ATPC lower
threshold
(dBm)
NOTE
l The transmit power and receive power are calculated in the modulation scheme of guaranteed AM capacity.
l In this example, the ATPC function is disabled.
Configuration Information About XPIC Groups

Table 8-17 lists the cross polarization interference cancellation (XPIC) configuration
information for NE11, NE12, NE13, and NE14.
Table 8-17 Configuration information about XPIC groups
Parameter
H (horizontal
polarization)
XPIC group
NE11
NE12
NE13
NE14
Configuration Information About PLA Groups

Table 8-18 lists the physical link aggregation (PLA) configuration information for NE11, NE12,
NE13, and NE14.
Issue 02 (2012-12-30)

166

Table 8-18 Configuration information about PLA groups

Parameter
NE11
NE12
NE13
NE14
PLA ID
1 (default value)
1 (default value)
1 (default value)
1 (default value)
IF Port
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
Service Port
1-SHXA2-2
(GE1)
1-SHXA2-2
(GE1)
1-SHXA2-2
(GE1)
Cascade Port
1-SHXA2-3
(GE2)
1-SHXA2-3
(GE2)
1-SHXA2-3
(GE2)
1-SHXA2-3
(GE2)
NE Role
Active
Standby
Active
Standby
Protection
Type
No NE-level
protection
No NE-level
protection
NE-level LGA
protection
NE-level LGA
protection
Minimum
Active Link
1 (default value)
1 (default value)
1 (default value)
1 (default value)
LAG NO
Assign
automatically
Assign
automatically
LAG Name
LAG_01
LAG_01
LAG Type
Static
Static
Load
Balancing
Non-Sharing
Non-Sharing
Reversion
Mode
Non-Revertive
Non-Revertive
System
Priority
32768
32768

This section describes the procedure for configuring microwave links on a microwave chain
network.
Procedure
Step 1 Delete the Ethernet port that does not participate in 1+1 protection from the bridge of the
Ethernet local area network (E-LAN) service, or delete the Ethernet line (E-Line) service
on the Ethernet port that does not participate in 1+1 protection.
Step 2 Create a link aggregation group (LAG).
Issue 02 (2012-12-30)

167

Parameter
Value
NE13
NE14
LAG NO
Select Assign
automatically.
Select Assign
automatically.
LAG Name
LAG_01
LAG_01
LAG Type
Static
Static
Load Balancing
Non-Sharing
Non-Sharing
Reversion Mode
Non-Revertive
Non-Revertive
System Priority
32768
32768
Main Port
1-SHXA2
1-SHXA2
Standby Port
Step 3 Create a physical link aggregation (PLA) group.

Parameter
NE11
NE12
NE13
NE14
PLA ID
1 (default value)
1 (default value)
1 (default value)
1 (default value)
IF Port
1-SHXA2-1
1-SHXA2-1
1-SHXA2-1
1-SHXA2-1
Service Port
1-SHXA2-2
1-SHXA2-2
1-SHXA2-2
1-SHXA2-2
Cascade Port
1-SHXA2-3
1-SHXA2-3
1-SHXA2-3
1-SHXA2-3
NE Role
Active
Standby
Active
Standby
Protection
Type
No NE-level
protection
No NE-level
protection
NE-level LGA
protection
NE-level LGA
protection
Minimum
Active Link
1 (default value)
1 (default value)
1 (default value)
1 (default value)
Step 4 Configure microwave links. For details, see A.5.1 Configuring a Single Hop of Microwave
Link.
l This table provides parameter values for NE11 to NE14.
Basic parameters
Parameter
Issue 02 (2012-12-30)
Value
NE11
NE12
NE13
NE14
XPIC
Enabled
Enabled
Enabled
Enabled
Link ID-V
101
101

168

Parameter
Value
NE11
NE12
NE13
NE14
102
102
NE11
NE12
NE13
NE14
IF Channel
Bandwidth
28M
28M
28M
28M
AM
Disabled
Disabled
Disabled
Disabled
Modulation
Mode
128QAM
128QAM
128QAM
128QAM
NE11
NE12
NE13
NE14
TX
Frequency
(MHz)
14930
14930
14510
14510
T/R Spacing
(MHz)
420
420
420
420
APTC
Disabled
Disabled
Disabled
Disabled
ATPC Upper
Threshold
(dBm)
ATPC Lower
Threshold
(dBm)
TX Power
(dBm)
16
16
16
16
Power to Be
Received
(dBm)
-46
-46
-46
-46
TX Status
unmute
unmute
unmute
unmute
Link ID-H
IF parameters
Parameter
Value
Radio frequency (RF) parameters

Parameter
Value

Basic parameters
Issue 02 (2012-12-30)

169

Parameter
Value
NE21
NE22
NE23
NE24
Link ID
201
201
202
202
XPIC
Disabled
Disabled
Disabled
Disabled
NE21
NE22
NE23
NE24
IF Channel
Bandwidth
7M
7M
14M
14M
AM
Enabled
Enabled
Enabled
Enabled
Modulation
Mode of the
Guaranteed
AM Capacity
QPSK Strong
QPSK Strong
QPSK Strong
QPSK Strong
Modulation
Mode of the
Full AM
32QAM
32QAM
64QAM
64QAM
NE21
NE22
NE23
NE24
TX
Frequency
(MHz)
14947
14527
14952
14532
T/R Spacing
(MHz)
420
420
420
420
APTC
Disabled
Disabled
Disabled
Disabled
ATPC Upper
Threshold
(dBm)
ATPC Lower
Threshold
(dBm)
TX Power
(dBm)
16.5
16.5
20
20
IF parameters
Parameter
Value
RF parameters
Parameter
Issue 02 (2012-12-30)
Value

170

Parameter
Value
NE21
NE22
NE23
NE24
Power to Be
Received
(dBm)
-43
-43
-48
-48
TX Status
unmute
unmute
unmute
unmute
----End
8.6.4 Configuration Example (Microwave Links on a Microwave

Ring Network)
This section provides an example of how to configure microwave links on a microwave ring
network according to the network plan.

Based on 8.5.4 Configuration Example (Microwave Ring Network Topology), configure the
radio ring links according to the following requirements. Figure 8-27 shows the networking
diagram.
l
Enable adaptive modulation (AM) for all microwave links, because all microwave links
carry Ethernet services.
The service capacity transmitted by each NodeB is provided in Table 8-19.

Table 8-19 Service capacity transmitted by each NodeB
Service Capacity
NodeB 1
NodeB 2
Capacity of high-priority
Ethernet services (Mbit/s)
10
Capacity of low-priority
Ethernet services (Mbit/s)
20
15
NOTE
High-priority services require transmission guarantees and must not be discarded in modulation scheme
shifts. Low-priority services do not require transmission guarantees and can be discarded in modulation
scheme shifts. Common service priorities are provided in Table 8-20.
Issue 02 (2012-12-30)

171

Table 8-20 Common service priorities

Service Type
Priority
Voice, signaling, and O&M Ethernet

services
High
Streaming media, background, and

interactive Ethernet services, for example,
Internet services
Low
Figure 8-27 Networking diagram (microwave links on a microwave ring network)
NMS
NodeB 1
301
14930 MHz
14510 MHz
14 MHz
1+0
V-polarization
303
14967 MHz
14547 MHz
14 MHz
1+0
V-polarization
NE31
LAN switch
NE36
Local backhaul
network
RNC
NE35
NE32
NodeB 2
NE33
NE34
302
14950 MHz
14530 MHz
14 MHz
1+0
H-polarization
Microwave link
Link ID
TX frequency at a TX high site
TX frequency at a TX low site
Channel spacing
RF configuration
Polarization
Ethernet link

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

You can obtain basic information about microwave links based on the spectrum allocation on
the microwave network and the required radio transmission capacity, as listed in Table 8-21.
Issue 02 (2012-12-30)

172

Table 8-21 Basic information about microwave links

Parameter
Link 1
Link 2
Link 3
Link ID
301
302
303
TX high site
NE31
NE33
NE35
TX low site
NE32
NE34
NE36
TX frequency at the
TX high site (MHz)
14930
14950
14967
TX frequency at the
TX low site (MHz)
14510
14530
14547
T/R Spacing (MHz)
420
420
420
Radio working
mode
14
14
14
RF configuration
mode
1+0
1+0
1+0
Polarization
direction
V (vertical
polarization)
H (horizontal
polarization)
V (vertical
polarization)
AM Attribute Information
You can compute adaptive modulation (AM) attribute information based on Ethernet service
capacity and availability requirements, as listed in Table 8-22.
Table 8-22 AM attribute information
Parameter
Link 1
Link 2
Link 3
AM
Enabled
Enabled
Enabled
Modulation Mode
of the Guaranteed
AM Capacity
16QAM
16QAM
16QAM
Modulation Mode
of the Full AM
128QAM
128QAM
128QAM
NOTE
Both the radio capacity and the AM function require a corresponding license file.
Power and ATPC Information

You can obtain information about the microwave link power and automatic transmit power
control (ATPC) by using microwave network planning software such as Pathloss, as listed in
Table 8-23.
Issue 02 (2012-12-30)

173

Table 8-23 Power and ATPC information

Parameter
Link 1
Link 2
Link 3
TX power (dBm)
16 (NE31)
16 (NE33)
16.5 (NE35)
16 (NE32)
16 (NE34)
16.5 (NE36)
-46 (NE31)
-45 (NE33)
-43 (NE35)
-46 (NE32)
-45 (NE34)
-43 (NE36)
ATPC
Disabled
Disabled
Disabled
ATPC upper
threshold (dBm)
ATPC lower
threshold (dBm)
RX power (dBm)
NOTE
l The transmit power and receive power are calculated in the modulation scheme of guaranteed AM capacity.
l In this example, the ATPC function is disabled.

This section describes the procedure for configuring microwave links on a microwave ring
network.
Procedure
Step 1 Configure microwave links. For details, see A.5.1 Configuring a Single Hop of Microwave
Link.
Basic parameters
Paramet
er
Value
NE31
NE32
NE33
NE34
NE35
NE36
Link ID
301
301
302
302
303
303
XPIC
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
IF parameters
Issue 02 (2012-12-30)

174

Paramet
er
Value
NE31
NE32
NE33
NE34
NE35
NE36
IF
Channel
Bandwid
th
14M
14M
14M
14M
14M
14M
AM
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Modulati
on Mode
of the
Guarant
eed AM
Capacity
16QAM
16QAM
16QAM
16QAM
16QAM
16QAM
Modulati
on Mode
of the
Full AM
128QAM
128QAM
128QAM
128QAM
128QAM
128QAM
Radio frequency (RF) parameters
Issue 02 (2012-12-30)
Paramet
er
Value
NE31
NE32
NE33
NE34
NE35
NE36
TX
Frequen
cy (MHz)
14930
14510
14950
14530
14967
14547
T/R
Spacing
(MHz)
420
420
420
420
420
420
APTC
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
ATPC
Upper
Threshol
d (dBm)
ATPC
Lower
Threshol
d (dBm)
TX
Power
(dBm)
16
16
16
16
16.5
16.5

175

Paramet
er
Value
NE31
NE32
NE33
NE34
NE35
NE36
Power to
Be
Received
(dBm)
-46
-46
-45
-45
-43
-43
TX
Status
unmute
unmute
unmute
unmute
unmute
unmute
----End

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

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

GE electrical ports on OptiX RTN 310 support four working modes: 10M full-duplex, 100M
full-duplex, 1000M full-duplex, and auto-negotiation. Table 8-24 lists auto-negotiation rules
for GE electrical ports.
Table 8-24 Auto-negotiation rules for GE electrical ports (when the local GE electrical port
works in auto-negotiation mode)
Issue 02 (2012-12-30)
Working Mode of the Opposite GE

Electrical Port
Auto-negotiation Result
Auto-negotiation (GE electrical port)
1000M full-duplex
Auto-negotiation (FE electrical port)
100M full-duplex
10M half-duplex
10M half-duplex
10M full-duplex
10M half-duplex
100M half-duplex
100M half-duplex
100M full-duplex
100M half-duplex
1000M full-duplex
1000M full-duplex

176

NOTE
As provided in Table 8-24, when the opposite GE electrical port works in 10M full-duplex or 100M full-duplex
mode, auto-negotiation does not necessarily achieve full matching between the two ends. As a result, some
packets are lost. Therefore, when the opposite GE electrical port works in 10M full-duplex or 100M full-duplex
mode, set the working mode of the local GE electrical port to 10M full-duplex or 100M full-duplex.
When the GE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate flow control.
Auto-negotiation Function of GE Optical Ports

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

When equipment fails to handle the traffic received at the port due to poor data processing/
transferring capability, the line becomes congested. This also causes buffer overflow and
therefore some packets are discarded. To reduce the number of packets to be discarded, take
appropriate flow control measures.
Half-duplex Ethernet uses a back-pressure mechanism to control flow. Full-duplex Ethernet uses
PAUSE frames to control flow. Currently, half-duplex Ethernet is not widely applied; therefore,
the flow control function is currently implemented for full-duplex Ethernet.
The flow control function on the equipment is classified into two types: auto-negotiation flow
control and non-auto-negotiation flow control.
Auto-negotiation Flow Control

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

The port can transmit PAUSE frames in case of congestion but cannot process received
PAUSE frames.
Symmetric PAUSE
The port can transmit PAUSE frames and process received PAUSE frames.
Both asymmetric and symmetric PAUSE

The port has the following capabilities:
Transmits and processes PAUSE frames.
Transmits PAUSE frames but cannot process received PAUSE frames.
Processes received PAUSE frames but cannot transmit PAUSE frames.
Disabled
The port does not transmit or process PAUSE frames.
NOTE
OptiX RTN 310 supports only two auto-negotiation flow control modes: Disabled and Symmetric Pause, which
correspond to Disabled and Enable Symmetric Flow Control on the network management system (NMS)
respectively.
Issue 02 (2012-12-30)

177

Non-auto-negotiation Flow Control

When an Ethernet port works in a fixed working mode, use non-auto-negotiation flow control.
The non-auto-negotiation flow control modes include the following:
l
Send only
The port can transmit PAUSE frames in case of congestion but cannot process received
PAUSE frames.
Receive only
The port can process received PAUSE frames but cannot transmit PAUSE frames in case
of congestion.
Symmetric
The port can transmit PAUSE frames and can also process received PAUSE frames.
Disabled
The port does not transmit or process PAUSE frames.
NOTE
OptiX RTN 310 supports only two auto-negotiation flow control modes: Disabled and Symmetric Pause, which
correspond to Disabled and Enable Symmetric Flow Control on the NMS respectively.
8.7.1.3 Ethernet Port Description

An OptiX RTN 310 provides two GE service ports for transmitting radio services carried by the
Native Ethernet.
Figure 8-28 shows the physical Ethernet ports on an OptiX RTN 310.
Figure 8-28 Ethernet ports on an OptiX RTN 310
GE
COMBO
P&E
Table 8-25 lists the logical ports corresponding to the physical Ethernet ports of an OptiX RTN
310 on the network management system (NMS).
Table 8-25 Mapping between physical ports and logical ports for an OptiX RTN 310
Physical Port
Logical Port
Description
COMBO (when used as an Ethernet

optical port)
1-SHXA2-2(GE1)
l A GE1 port can be a COMBO

port or a P&E port.
Issue 02 (2012-12-30)

178

Physical Port
Logical Port
Description
l When a COMBO port functions
as a GE optical port, it can
function as a GE1 port to receive
Ethernet services.
l A COMBO port can also
function as a cross polarization
interference cancellation (XPIC)
port to receive XPIC signals or a
1+1 cascade port to receive 1+1
cascade signals. A COMBO port
can be used as only one type of
port at a time.
l A P&E port can function as a GE
electrical port.
l When a P&E port functions as a
GE electrical port and a COMBO
port functions as a GE optical
port, the two ports share the same
service channel which can
transmit Ethernet services to
only one port at a time. By
default, services are transmitted
to the GE electrical port.
P&E
GE
1-SHXA2-3 (GE2)
A GE port with a small form-factor

pluggable (SFP) module can
function as a GE optical port.
8.7.1.4 MAC Address Table Management

Entries in a MAC address table show the mapping between MAC addresses and ports. Entries
can be classified into dynamic entries, static entries, and blacklist entries.
Table 8-26 Entries in a MAC address table
Issue 02 (2012-12-30)
Entry
Description
Dynamic entry
A dynamic entry is learned by a bridge in SVL or IVL mode. A

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

MAC address table on the network management system (NMS).
Generally, a static entry is configured for a port connected to a device
that has a known MAC address and that carries constant and heavy
traffic. A static entry will not be aged out. It is not lost after the
Ethernet processing unit is reset.

179

Entry
Description
Blacklist entry
A blacklist entry is also called a MAC disabled entry or a black hole

entry. It is configured by a network administrator. An Ethernet frame
whose source or destination MAC address is specified in a blacklist
entry is discarded. A blacklist entry will not be aged out. It is not
lost after the Ethernet processing unit is reset.
NOTE
If no new packet is received from a MAC address within a specified period of time, the corresponding
entry is automatically deleted. This mechanism is called aging and the specified period of time is called
aging time.
8.7.1.5 VLAN Forwarding Tables for E-Line Services

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

Source
Port
Port 1
Source
VLAN ID
100
Port 2
200
Port 2
Sink
VLAN ID
200
Port 1
100
Sink Port
E-Line service information table
Issue 02 (2012-12-30)
Source
Port
Source
VLAN ID
Sink Port
Sink
VLAN ID
Port 1
100
Port 2
200

180

8.7.1.6 Split Horizon Groups

To separate services that converge and to prevent broadcast storms resulting from service loops,
configure a split horizon group for Ethernet local area network (E-LAN) services at specified
nodes. The logical ports within the same split horizon group cannot forward packets to each
other.
Figure 8-30 shows a typical application of a split horizon group. Each NE on the network is
configured with E-LAN services, and the microwave port and two GE ports on each NE are
configured as bridge-mounted logical ports. If a split horizon group is not configured on NE1,
its microwave port and the GE port connected to NE4 forward packets to each other, causing a
service loop and a broadcast storm. If a split horizon group is configured on NE1 and if its
microwave port and the GE port connected to NE4 are configured as members of the split horizon
group, the two ports do not forward packets to each other.
Figure 8-30 Split horizon group
NE 2
NE 1
RNC
NodeB 1
Split
horizon
group
NE 3
NE 4
NodeB 3
NodeB 2
Microwave link
Ethernet link
NOTE
l Ethernet ring protection switching (ERPS) prevents service loops on ring networks. If ERPS has already
been enabled for a ring network, do not configure a split horizon group because it may affect ERPS
functionality.
l OptiX RTN 310 allows only physical ports to be configured into a split horizon group. If a physical port is
mapped into several logical ports and one of those logical ports is a member of a split horizon group, the
other logical ports are added to the split horizon group automatically.
8.7.1.7 Protection for Native Ethernet Services

OptiX RTN 310 supports two protection modes for Native Ethernet services: Ethernet ring
protection switching (ERPS) and link aggregation group (LAG).
Issue 02 (2012-12-30)

181

ERPS
ERPS is applicable to ring physical networks and can provide protection for the Ethernet local
area network (E-LAN) services between all the ring network nodes. Generally, when a ring
network is configured with ERPS, the RPL node blocks the RPL port on one side so that all the
services are transmitted through the ports on the other side. In this manner, service loops are
prevented. When a link fails or an NE becomes faulty, the RPL node unblocks its RPL port so
that services can be switched from the faulty point to the RPL port for transmission. In this
manner, protection for the ring network is achieved.
The Ethernet ring network shown in Figure 8-31 is configured with ERPS. Normally, NE1
blocks its GE port connected to NE2 to prevent a loop. When links between NE4 and NE5 are
faulty, NE1 unblocks its GE port. Services between NE4 and NE5 are switched to the route NE4NE3-NE2-NE1-NE8-NE7-NE6-NE5.
Figure 8-31 Implementation of ERPS
NE4
NE3
NE2
NE5
NodeB
RNC
NodeB
NE6
NE1
NE8
NE7
NodeB
NodeB
Protection switching
NE4
NE3
Failure
NE5
NE2
NodeB
RNC
NodeB
NE1
NE6
NE7
Ethernet cable
NE8
NodeB
NodeB

Blocked port
Issue 02 (2012-12-30)

182

LAG
Link aggregation allows multiple links that are attached to the same equipment to be aggregated
to form a link aggregation group (LAG) so that the bandwidths and availability of the links
increase. The aggregated links can be considered as a single logical link.
As shown in Figure 8-32, the LAG feature provides the following functions:
l
Increased link capacity

The LAG feature provides users with a cost-effective method for increasing link bandwidth.
Users obtain data links with higher bandwidths by combining multiple physical links into
one logical link without having to upgrade existing equipment. The bandwidth of the logical
link is equal to the sum of the bandwidths of the physical links. The aggregation module
distributes traffic to different members by using a load balancing algorithm, achieving load
balancing at the link level.
Improved link availability

The links in a LAG provide backup for one another dynamically. When a link fails, another
link in the LAG quickly takes over.
Figure 8-32 LAG

Link 1
Link 2
Ethernet packet
Ethernet packet
Link aggregation group
8.7.2 Native Ethernet Service Types

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

The transparently transmitted point-to-point Ethernet line (E-Line) service is the basic E-Line
model. Point-to-point transmission does not involve service bandwidth sharing, service
isolation, or service distinguishing. Instead, Ethernet services are transparently transmitted
between two service access points.
Service Model
Table 8-27 describes the transparently transmitted point-to-point E-Line service model.
Issue 02 (2012-12-30)

183

Table 8-27 Transparently transmitted point-to-point E-Line service model

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

transparently
transmits all the
received Ethernet
frames to the sink
port.
PORT (sink)
Null (sink)
Model 2
PORT (source)
NOTE
In service model 2,
ports process the
received Ethernet
frames according to
their TAG attributes.
Therefore, service
model 2 is not a real
transparent
transmission model
and is not
recommended.
PORT (sink)
UNI-UNI
802.1Q (source)
802.1Q (sink)
The source port

processes the
incoming Ethernet
frames based on its
TAG attribute, and
then sends the
processed Ethernet
frames to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.
Typical Application
Figure 8-33 shows the typical application of service model 1.
Figure 8-33 Typical application of service model 1
NE 1
Service 1
Port 1
E-Line
NE 2
Port 2
Transmission
network
Port 2
E-Line
Port 1
Service 1
In model 1, Ethernet service 1 is transmitted to NE1 through port 1, regardless of whether the
Ethernet service carries an unknown VLAN ID or no VLAN ID. Port 1 transparently transmits
Ethernet service 1 to port 2. Port 2 transmits Ethernet service 1 to NE2. Service processing on
NE2 is the same as that on NE1.
In model 2, Ethernet service 1 is transmitted to NE1 through port 1, regardless of whether the
Ethernet service carries an unknown VLAN ID or no VLAN ID. Port 1 and Port 2 process the
incoming packets based on their own TAG attributes. Then, Port 2 sends Ethernet service 1 to
NE2. Service processing on NE2 is the same as that on NE1.
Issue 02 (2012-12-30)

184

8.7.2.2 VLAN-based E-Line Service

You can use VLANs to separate Ethernet line (E-Line) services, which allows the E-Line
services to share one physical transmission channel. E-Line services separated in this manner
are called VLAN-based E-Line services.
Service Model
Table 8-28 provides information about the VLAN-based E-Line service model.
Table 8-28 VLAN-based E-Line service model
Service Type
Service Flow
Service Direction
Encapsulation
Type at a Port
Service
Description
VLAN-based ELine service
PORT+VLAN
(source)
UNI-UNI (UNI
stands for user-tonetwork interface.)
IEEE 802.1Q
(source)
The source port

processes incoming
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.
PORT+VLAN
(sink)
IEEE 802.1Q (sink)
Typical Application
Figure 8-34 shows a typical application of the VLAN-based E-Line service model. Services 1,
2, 3, and 4 from four NodeBs converge through a transmission network to a radio network
controller (RNC).
l
Services 1, 2, 3, and 4 carry different VLAN IDs.
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.
Issue 02 (2012-12-30)

185

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

Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Service 3
VLAN ID: 300
Service 4
VLAN ID: 400
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Port 1
NE 3
Port 1
E-Line
E-Line
RNC
NE 1
E-Line
E-Line
Port 2
Port 3
Port 2
Port 1
Service 3
VLAN ID: 300
Service 4
VLAN ID: 400
E-Line
NodeB 1
Port 3
Service 2
VLAN ID: 200
NodeB 2
Transmission
network
E-Line
Service 1
VLAN ID: 100
Port 2
Port 3
Service 3
NodeB 3 VLAN ID: 300
NE 2
Service 4
VLAN ID: 400
NodeB 4
8.7.2.3 IEEE 802.1D Bridge-based E-LAN Services

Ethernet local area network (E-LAN) services that are forwarded based only on the MAC address
table are called IEEE 802.1D bridge-based E-LAN services.
Service Model
Table 8-29 shows the IEEE 802.1D bridge-based E-LAN service model.
Table 8-29 IEEE 802.1D bridge-based E-LAN service model
Service Type
Tag Type
Encapsulation
Type at a Port
Logical Port
Type
Learning
Mode
Switching
Sub-domain
IEEE 802.1D
bridge-based ELAN service
TagTransparent
Null
PORT
SVL
None
Typical Application
Figure 8-35 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.
Issue 02 (2012-12-30)

186

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

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

You can use VLANs to separate Ethernet local area network (E-LAN) services and divide an
IEEE 802.1Q bridge into multiple independent switching sub-domains. E-LAN services
separated in this manner are called IEEE 802.1Q bridge-based E-LAN services.
Service Model
Table 8-30 provides information about the IEEE 802.1Q bridge-based E-LAN service model.
Table 8-30 IEEE 802.1Q bridge-based E-LAN service model
Service Type
Tag Type
Encapsulation
Type at a Port
Logical Port
Type
Learning
Mode
Switching
Sub-domain
IEEE 802.1Q
bridge-based ELAN service
C-Aware
IEEE 802.1Q
PORT+VLAN
Independent
VLAN learning
(IVL)
A bridge divided
into switching
sub-domains by
VLAN
Typical Application
Figure 8-36 shows a typical application of the IEEE 802.1Q bridge-based E-LAN service model.
Services 1, 2, 3, and 4 from four NodeBs converge through a transmission network to a radio
network controller (RNC).
l
Services 1 and 2 have the same VLAN ID of 100, and services 3 and 4 have the same VLAN
ID of 200.
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.
Issue 02 (2012-12-30)

187

Figure 8-36 IEEE 802.1Q bridge-based E-LAN service model

NE 2
Port 1
Service 1
VLAN ID: 100
Port 2
NodeB 1
Service 1, 2
VLAN ID: 100
Service 3, 4
VLAN ID: 200
VLAN 100
Port 1
NE 1
VLAN 100
VLAN 200
Port 3
RNC
802.1Q bridge
Port 3
Port 2
Domain 1
(VLAN ID: 100)
802.1Q bridge
NE
NE 3 VLAN 200
2
Port 2
Port 1
Domain 2
(VLAN ID: 200)
Service 2
VLAN ID: 100
NodeB 2
NodeB 3
Service 3
VLAN ID: 200
Port 3
802.1Q bridge
NodeB 4
Service 4
VLAN ID: 200
8.7.3 Typical Mobile Bearer Network Topologies for Ethernet

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

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

188

Figure 8-37 Networking diagram of VLAN-based E-Line services
NodeB 1
VLAN 1
NE3
NE4
NE7
NE1
Local backhaul
network
NodeB 2
VLAN 2
GE
NE8
NE2
NodeB 3
VLAN 3
NE6
Microwave link
RNC
NE5
Ethernet link
8.7.3.2 Networking of IEEE 802.1D Bridge-based E-LAN Services

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

189

Figure 8-38 Networking diagram (IEEE 802.1D bridge-based E-LAN services)
NodeB 1
VLAN 1
NE3
NE4
NE7
NE1
Local backhaul
network
NodeB 2
VLAN 2
GE
NE8
NodeB 3
VLAN 3
NE2
NE6
Split horizon group
RNC
NE5
Microwave link
Ethernet link
8.7.3.3 Networking of IEEE 802.1Q Bridge-based E-LAN Services

In the case of IEEE 802.1Q bridge-based Ethernet local area network (E-LAN) service
networking, services are isolated by means of VLAN IDs. That is, the IEEE 802.1Q bridge is
divided into multiple sub-switching domains, which are isolated from each other.
On the mobile bearer network shown in Figure 8-39, the VLAN IDs carried by received NodeB
services are planned in a unified manner and are unique within each domain. NodeB services in
different domains are isolated from each other by means of VLAN IDs and NodeBs in the same
domain can communicate with each other. The NodeB services are aggregated at NE1 and then
transmitted through the local backhaul network to the radio network controller (RNC).
Therefore, in this example, the services on the radio equipment of the mobile bearer network
are configured as IEEE 802.1Q bridge-based E-LAN services. The microwave network checks
the destination ports in the MAC address table according to the destination MAC addresses and
VLAN IDs carried by the NodeB services and then forwards NodeB services to the ports.
NOTE
IEEE 802.1Q bridge-based E-LAN service packets can be broadcast within each domain. Therefore, isolate the
ports that do not require communication with one another by adding the ports into a split horizon group.
Issue 02 (2012-12-30)

190

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

The three networking modes differ from each other.
Table 8-31 compares the three networking modes.
Issue 02 (2012-12-30)

191

Table 8-31 Comparison between the three networking modes

Networkin
g Mode
Applicable
Network
Size
Applicable
VLAN ID
Allocation
Networking
of VLANbased
Ethernet line
(E-Line)
services
This
networking
mode is
applicable to
all network
sizes.
l The VLAN IDs

carried by
received base
transceiver
station (BTS)
services are
planned in a
unified manner
and are unique
globally.
l BTS services
share Ethernet
service
bandwidths and
are isolated by
means of VLAN
IDs.
Issue 02 (2012-12-30)
Service
Stabilit
y
Service
Security
Configurati
on
Complexity
Network
Scalability
High
l Very
high
l Services
with a
certain
VLAN ID
are
transmitte
d over a
fixed
service
trail.
l The
network is
difficult
to expand.
l Servic
es
from
differe
nt
BTSs
are
isolate
d from
each
other.

l The OAM
capability
is strong
and only
point-topoint
configurat
ion is
supported.
l To add the
new
VLAN ID
after a
BTS is
added,
you must
change
the ELine
configurat
ions on all
the NEs
that the
new
service
path
traverses.
192

Networkin
g Mode
Applicable
Network
Size
Applicable
VLAN ID
Allocation
Networking
of IEEE
802.1D
bridge-based
Ethernet local
area network
(E-LAN)
services
It is
recommended
that the
network
contain less
than 50 BTSs.
l The network
does not need to
sense whether
the received BTS
services carry
any VLAN IDs.
Issue 02 (2012-12-30)
l Services do not
need to be
isolated between
different ports
connected to the
same bridge.a
Service
Stabilit
y
Service
Security
Configurati
on
Complexity
Network
Scalability
Medium
l Low
l A service
trail is set
up by
means of
MAC
address
selflearning,
and is
variable.
l The
network is
easy to
expand.
l The
service
packet
s can
be
broadc
ast on
the
entire
networ
k.

l Point-tomultipoint
configurat
ion is
supported.
The OAM
capability
is
relatively
weak.
l After a
BTS is
added,
you do not
need to
change
the
configurat
ions of
other NEs
on the
network.
Instead,
you only
need to
change
the
mounted
ports on
the NE
connected
to the base
station.
193

Networkin
g Mode
Applicable
Network
Size
Applicable
VLAN ID
Allocation
Networking
of IEEE
802.1Q
bridge-based
E-LAN
services
This
networking
mode is
applicable to
all network
sizes,
especially to a
network that is
divided into
several
domains.
l The VLAN IDs

carried by
received BTS
services are
planned in a
unified manner
and are unique
within each
domain.
l The BTS
services from
different
domains are
isolated from
each other by
means of VLAN
IDs.
l BTS services
within a domain
do not need to be
isolated from
each other.a
Service
Stabilit
y
Service
Security
Configurati
on
Complexity
Network
Scalability
Medium
l High
l Service
trails are
learned
based on
MAC
addresses
and
VLAN
IDs and
are not
fixed.
l The
network is
easy to
expand.
l The
service
packet
s are
broadc
ast
within
each
domai
n and
are
isolate
d
betwee
n
differe
nt
domai
ns.
l Point-tomultipoint
configurat
ion is
supported.
The OAM
capability
is
relatively
weak.
l After a
BTS is
added in a
domain,
you do not
need to
change
the
configurat
ions of the
other NEs
in the
domain or
the
configurat
ions of
NEs in the
other
domains.
Instead,
you only
need to
change
the
mounted
ports and
VLAN
IDs on the
NE
connected
to the base
station.
NOTE
a: To block communication between certain ports connected to a bridge, you must add the ports into a split
horizon group.
8.7.4 Configuration Process

The service configuration process differs according to the specific service type.
Issue 02 (2012-12-30)

194

8.7.4.1 Per-NE Configuration Process (Transparently Transmitted Point-to-Point ELine Services)

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

195

Configuring LAG for Ethernet Ports

Table 8-32 Process of configuring LAG for Ethernet ports
Step
Operation
Remarks
A.7.2.1
Creating a
LAG
When the Ethernet link between an OptiX RTN 310 NE and

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

Table 8-33 Process of configuring transparently transmitted point-to-point E-Line services
Issue 02 (2012-12-30)
Step
Operation
Remarks
A.7.3.11
Deleting an
E-LAN
Service
Required when an NE is being initially configured.

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

196

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

Table 8-34 Process of setting port attributes
Issue 02 (2012-12-30)
Step
Operation
Setting
parameter
s for an
Ethernet
port
Remarks
A.6.1.1
Setting
the Basic
Attribute
s for an
Ethernet
Port
Optional.
Set Max Frame Length (byte) to the length of the
longest frame that the port may receive. It is
recommended that this parameter take the default
value of 9600.
A.6.1.2
Configuri
ng the
Traffic
Control
Function
for an
Ethernet
Port
Required when the flow control function is enabled

on the external equipment to which the Ethernet port
is connected. Set parameters as follows:
l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
l When the external equipment uses the autonegotiation flow control function, set
Autonegotiation Flow Control Mode to

197

Step
Operation
Setting
parameter
s for a
microwav
e port
Remarks
A.6.1.4
Setting
the
Advanced
Attribute
s for an
Ethernet
Port
Optional.
A.6.2.1
Setting
Basic
Attribute
s for a
Microwav
e Port
Optional.
A.6.2.3
Setting
Advanced
Attribute
s for a
Microwav
e Port
Optional.
NOTE
Because the Web LCT does not provide a window specifically for configuring microwave ports, configure
microwave port parameters in the window for configuring Ethernet port parameters.
Configuring QoS
Table 8-35 Process of configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain
Required if the default mappings for the Differentiated

Services (DS) domain are inapplicable.
A.7.6.2
Changing
the Packet
Type
Trusted by a
Port
Required if the priority type of an Ethernet service is not

CVLAN, which is the default packet type trusted by the
DiffServ domain.
Issue 02 (2012-12-30)
Set related parameters according to the network plan.
Set the parameters according to the network plan.

198

Step
Operation
Remarks
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies
Required if a port is required to schedule traffic according to

a certain queue scheduling policy in the case of traffic
congestion. The default queue scheduling mode is SP+WRR
(SP is short for strict priority and WRR for weighted round
robin). AF1 to AF4 queues are WRR queues (allocated the
same weight) and the other queues are SP queues.
A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues
Required if the bandwidth for egress port queues needs to be

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues
Required if a certain congestion management mode is

required for queues at an egress port. The default mode is tail
drop.
A.7.6.3
Configuring
Port
Shaping
Required if you need to limit the egress bandwidth that an

Ethernet service occupies.
Verifying Ethernet Service Configurations

Table 8-36 Process of verifying Ethernet service configurations
Step
Operation
Remarks
A.7.7.1
Creating an
MD
Required for the NEs where the two Ethernet ports involved
in the service test are located. Set parameters as follows:
l Set Maintenance Domain Name and Maintenance
Domain Level to the same values for the NEs.
l For an Ethernet service between two edge nodes on the
transport network, it is recommended that Maintenance
Domain Level takes its default value of 4. For an Ethernet
service between two internal NEs on the transport
network, set Maintenance Domain Level to a value
smaller than 4. For an Ethernet service between two
Ethernet ports on the same NE, set Maintenance Domain
Level to a value smaller than the value that is set in the
test of an Ethernet service between two internal NEs on
the transport network.
Issue 02 (2012-12-30)

199

Step
Operation
Remarks
A.7.7.2
Creating an
MA
l Set Maintenance Domain Name to the value of
Maintenance Domain Name that is set in the preceding
step.
l Set Maintenance Association Name to the same value
for the NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit
Period to 1s.
A.7.7.3
Creating an
MEP
l Set Maintenance Association Name to the value of
Maintenance Association Name that is set in the
preceding step.
l Set Port to the Ethernet ports that are involved in the
service test.
l Set MP ID to different values for maintenance association
end points (MEPs) in the same maintenance domain (MD).
l If the OAM information initiated by the MEP travels
through the packet switching unit on the local NE, set
Direction of the MEP to Ingress. Otherwise, set
Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify
the MEP during the loopback (LB) test.
A.7.7.4
Creating a
Remote
MEP in an
MA
Required for the NE where the Ethernet ports involved in the

OAM operation are located. Set parameters as follows:
step.
preceding step.
l To ensure that an MEP can respond to the OAM operations
initiated by the other MEPs in the same maintenance
association (MA), you need to set the other MEPs as the
remote MEPs.
NOTE
When two MEPs are on the same NE, you do not need to configure
remote MEPs.
Issue 02 (2012-12-30)
A.7.7.7
Performing
an LB Test
Required.
The LB test result should show that no packet loss occurs.

200

8.7.4.2 End-to-End Configuration Process (Transparently Transmitted Point-toPoint E-Line Services)

protection information, and quality of service (QoS) information for a transparently transmitted
point-to-point Ethernet line (E-Line) service in end-to-end mode and the process of verifying
the service configurations.
Flowchart
Figure 8-41 shows the flowchart for configuring transparently transmitted point-to-point E-Line
services.
Figure 8-41 Flowchart for configuring transparently transmitted point-to-point E-Line services
Required
Start
Optional
Configure a LAG.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End
Issue 02 (2012-12-30)

201


Step
Operation
Setting
Parameter
s for an
Ethernet
Port
Issue 02 (2012-12-30)
Setting
Parameter
s for a
Microwav
e Port
Remarks
A.6.1.1
Setting
the Basic
Attribute
s for an
Ethernet
Port
Required.
A.6.1.2
Configuri
ng the
Traffic
Control
Function
for an
Ethernet
Port

A.6.1.4
Setting
the
Advanced
Attribute
s for an
Ethernet
Port
Optional.
A.6.2.1
Setting
Basic
Attribute
s for a
Microwav
e Port
Required.
Set Port Mode to Layer 2 and set Encapsulation
Type to Null.
A.6.2.3
Setting
Advanced
Attribute
s for a
Microwav
e Port
Optional.
l Set Port Mode to Layer 2 and set

Encapsulation Type to Null.
l Set Max Frame Length (byte) to the length of
the longest frame that the port may receive. It is
value of 9600.

202


Step
Operation
Remarks
A.7.2.1
Creating a
LAG

bandwidth.
LAGs.
sharing LAGs.
A.7.2.2
Setting
Parameters
for a LAG
Optional.
Configuring Transparently Transmitted Point-to-Point E-Line Services

Table 8-39 Process of configuring transparently transmitted point-to-point E-Line services
Issue 02 (2012-12-30)
Step
Operation
Remarks
A.7.3.11
Deleting an
E-LAN
Service

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

203

Step
Operation
Remarks
A.3.4.1
Creating a
Fiber/Cable
by Using the
Search
Method
Perform this task to create microwave links or Ethernet fibers/

cables for service paths if they have not been created on Main
Topology of the U2000.
Set Automatically Allocate Address to No when creating
Ethernet fiber/cable.
A.10.2
Creating a
Point-toPoint
Transparen
tly
Transmitte
d E-Line
Service
Required.
Set related parameters according to the service planning
information and parameter planning information.
Configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain

A.7.6.2
Changing
the Packet
Type
Trusted by a
Port

DiffServ domain.
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies

Issue 02 (2012-12-30)

204

Step
Operation
Remarks
A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues

drop.
A.7.6.3
Configuring
Port
Shaping


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

protection information, and quality of service (QoS) information for a VLAN-based Ethernet
line (E-Line) service and the process of verifying the service configurations.
Flowchart
Figure 8-42 shows the flowchart for configuring VLAN-based E-Line services.
Issue 02 (2012-12-30)

205

Figure 8-42 Flowchart for configuring VLAN-based E-Line services
Required
Start
Optional
Configure a LAG.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End
Issue 02 (2012-12-30)

206


Step
Operation
Remarks
A.7.2.1
Creating a
LAG

bandwidth.
LAGs.
sharing LAGs.
A.7.2.2
Setting
Parameters
for a LAG
Optional.
Configuring VLAN-based E-Line Services

Table 8-43 Process of configuring VLAN-based E-Line services
Issue 02 (2012-12-30)
Step
Operation
Remarks
A.7.3.11
Deleting an
E-LAN
Service

NOTE
to delete the default services manually before you configure VLANbased E-Line services on it.

207

Step
Operation
Remarks
A.7.3.2
Creating a
VLANbased ELine Service
Required.
l Set VLAN ID for the source and sink according to the
network plan.
l Set Encapsulation Type to 802.1Q.
l Set Tag according to the following principles:
If all the accessed services carry VLAN tags (tagged
frames), set Tag to Tag Aware.
If none of the accessed services carries VLAN tags
(untagged frames), set Tag to Access, and set Default
VLAN ID and VLAN Priority according to the
network plan.
When the accessed services contain tagged frames and
untagged frames, set Tag to Hybrid, and set Default
network plan.
NOTE
If PLA without NE-level protection has been configured, Ethernet
services do not need to be configured for the standby NE. If 1+1
protection or PLA with NE-level protection has been configured,
configure Ethernet services for the main and standby NEs
consistently.
Issue 02 (2012-12-30)
A.7.3.3
Creating an
E-Line
Service for
Transmittin
g Layer 2
Protocol
Packets
Required when Layer 2 protocol packets need to be

transparently transmitted.
A.7.3.4
Creating
VLAN
Forwarding
Table
Entries
Required when the VLAN tags of the Ethernet service need

to be switched at the source and sink.
The parameters need to be set according to the network plan.
NOTE
The corresponding VLAN forwarding table items need to be
configured for the source port and sink port.

208


Step
Operation
Setting the
parameter
s of
Ethernet
ports
Issue 02 (2012-12-30)
Setting the
parameter
s of
microwav
e ports
Remarks
A.6.1.1
Setting
the Basic
Attribute
s for an
Ethernet
Port
Optional.
value of 9600.
A.6.1.2
Configuri
ng the
Traffic
Control
Function
for an
Ethernet
Port

A.6.1.4
Setting
the
Advanced
Attribute
s for an
Ethernet
Port
Optional.
A.5.8
Configuri
ng
Ethernet
Frame
Header
Compress
ion and
Errored
Frame
Discardin
g Over
Air
Interfaces
Optional.

209

Step
Operation
Remarks
A.6.2.2
Setting
Layer 2
Attribute
s for a
Microwav
e Port
Optional.
A.6.2.3
Setting
Advanced
Attribute
s for a
Microwav
e Port
Optional.
NOTE
Configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain

A.7.6.2
Changing
the Packet
Type
Trusted by a
Port

DiffServ domain.
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies

Issue 02 (2012-12-30)

210

Step
Operation
Remarks
A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues

drop.
A.7.6.3
Configuring
Port
Shaping


Step
Operation
Remarks
A.7.7.1
Creating an
MD
Issue 02 (2012-12-30)

211

Step
Operation
Remarks
A.7.7.2
Creating an
MA
step.
for the NEs.
Period to 1s.
A.7.7.3
Creating an
MEP
preceding step.
service test.
A.7.7.4
Creating a
Remote
MEP in an
MA

step.
preceding step.
remote MEPs.
NOTE
remote MEPs.
Issue 02 (2012-12-30)
A.7.7.7
Performing
an LB Test
Required.

212

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

protection information, and quality of service (QoS) information for a VLAN-based Ethernet
line (E-Line) service in end-to-end mode and the process of verifying the service configurations.
Flowchart
Figure 8-43 shows the flowchart for configuring VLAN-based E-Line services.
Figure 8-43 Flowchart for configuring VLAN-based E-Line services
Required
Start
Optional
Configure a LAG.
Configure E-Line
services.
Configure QoS.
Verify Ethernet
services.
End
Issue 02 (2012-12-30)

213


Step
Operation
Setting the
parameter
s of
Ethernet
ports
Remarks
A.6.1.1
Setting
the Basic
Attribute
s for an
Ethernet
Port
Required.
A.6.1.2
Configuri
ng the
Traffic
Control
Function
for an
Ethernet
Port

A.6.1.3
Setting
the Layer
2
Attribute
s for an
Ethernet
Port
l Set Port Mode to Layer 2 and set

Encapsulation Type to 802.1Q.
l Set Max Frame Length (byte) to the length of
the longest frame that the port may receive. It is
value of 9600.
l If all the accessed services carry VLAN tags

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

214

Step
Operation
Setting the
parameter
s of
microwav
e ports
Remarks
A.5.8
Configuri
ng
Ethernet
Frame
Header
Compress
ion and
Errored
Frame
Discardin
g Over
Air
Interfaces
Required.
Set Port Mode to Layer 2 and set Encapsulation
Type to 802.1Q.
A.6.2.2
Setting
Layer 2
Attribute
s for a
Microwav
e Port

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

215


Step
Operation
Remarks
A.7.2.1
Creating a
LAG

bandwidth.
LAGs.
sharing LAGs.
A.7.2.2
Setting
Parameters
for a LAG
Optional.
Configuring VLAN-based E-Line Services

Table 8-49 Process of configuring VLAN-based E-Line services
Issue 02 (2012-12-30)
Step
Operation
Remarks
A.7.3.11
Deleting an
E-LAN
Service

NOTE
to delete the default services manually before you configure VLANbased E-Line services on it.

216

Step
Operation
Remarks
A.3.4.1
Creating a
Fiber/Cable
by Using the
Search
Method
Perform this task to create microwave links or Ethernet fibers/

cables for service paths if they have not been created on Main
Topology of the U2000.
A.10.3
Creating a
VLANbased ELine Service
Required.
A.7.3.3
Creating an
E-Line
Service for
Transmittin
g Layer 2
Protocol
Packets

A.7.3.4
Creating
VLAN
Forwarding
Table
Entries
Required when the VLAN tags of the Ethernet service need

to be switched at the source and sink.

The parameters need to be set according to the network plan.

NOTE
The corresponding VLAN forwarding table items need to be
configured for the source port and sink port.
Configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain

A.7.6.2
Changing
the Packet
Type
Trusted by a
Port

DiffServ domain.
Issue 02 (2012-12-30)

217

Step
Operation
Remarks
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies

A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues

drop.
A.7.6.3
Configuring
Port
Shaping


Step
Operation
Remarks
A.10.6
Verifying a
Native
Ethernet
Service
Required.
occurs.
8.7.4.5 Per-NE Configuration Process (IEEE 802.1D Bridge-based E-LAN Services)

protection information, and quality of service (QoS) information for an IEEE 802.1D bridgebased Ethernet local area network (E-LAN) service and the process of verifying the service
configurations.
Issue 02 (2012-12-30)

218

Flowchart
Figure 8-44 shows the flowchart for configuring IEEE 802.1D bridge-based E-LAN services.
Figure 8-44 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services
Required
Start
Optional
Configure a LAG.
Configure ERPS
protection.
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
End
Issue 02 (2012-12-30)

219


Step
Operation
Remarks
A.7.2.1
Creating a
LAG

bandwidth.
LAGs.
sharing LAGs.
Issue 02 (2012-12-30)
A.7.2.2
Setting
Parameters
for a LAG
Optional.

220

Configuring ERPS Protection

Table 8-53 Process of configuring ERPS protection
Step
Operation
Remarks
A.7.1.1 Creating an ERP

Instance
Required when an Ethernet

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

Protocol Parameters
Required if the values of the

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

221

Configuring IEEE 802.1D Bridge-based E-LAN Services

Table 8-54 Process of configuring IEEE 802.1D bridge-based E-LAN services
Step
Operation
Remarks
A.7.3.5 Creating an IEEE

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

Ports Mounted to a
Bridge
Optional.
Mana
ging
the
MAC
addres
s table
A.7.4.2 Creating
a Blacklist MAC
Address Entry
Required when usage of E-LAN services needs to be

disabled on certain MAC address host.
A.7.4.1 Creating
a Static MAC
Address Entry
Required if you need to set certain MAC address

entries not to age.
NOTE
Perform this operation when you need to change the type of
a logical port mounted to a bridge, because an OptiX RTN
310 carries IEEE 802.1D bridge-based services by default.
Set the parameters according to the network planning

information.

222

Step
Operation
Remarks
A.7.4.3
Managing a
Dynamic MAC
Address Table
4
A.7.5 Setting the Mode

for Processing an
Unknown Frame of an ELAN Service
Required if the aging function needs to be disabled or

if the default aging time (five minutes) needs to be
changed.
Optional. By default, the processing mode for
unknown frames is flood.
NOTE

Issue 02 (2012-12-30)
Step
Operation
Setting the
parameter
s of
Ethernet
ports
Remarks
A.6.1.1
Setting
the Basic
Attribute
s for an
Ethernet
Port
Optional.
value of 9600.
A.6.1.2
Configuri
ng the
Traffic
Control
Function
for an
Ethernet
Port

A.6.1.4
Setting
the
Advanced
Attribute
s for an
Ethernet
Port
Required when you need to enable the port self-loop

test and automatic loopback shutdown functions or
to enable the broadcast packet suppression function.
Set Loopback check, Loopback port shutdown,

Enabling broadcast packet suppression, and
Broadcast packet suppression threshold as
desired.

223

Step
Operation
Setting the
parameter
s of
microwav
e ports
Remarks
A.6.2.1
Setting
Basic
Attribute
s for a
Microwav
e Port
Optional.
A.6.2.3
Setting
Advanced
Attribute
s for a
Microwav
e Port

desired.
NOTE
Configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain

A.7.6.2
Changing
the Packet
Type
Trusted by a
Port

DiffServ domain.
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies

Issue 02 (2012-12-30)

224

Step
Operation
Remarks
A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues

drop.
A.7.6.3
Configuring
Port
Shaping


Step
Operation
Remarks
A.7.7.1
Creating an
MD
Issue 02 (2012-12-30)

225

Step
Operation
Remarks
A.7.7.2
Creating an
MA
step.
for the NEs.
Period to 1s.
A.7.7.3
Creating an
MEP
preceding step.
service test.
A.7.7.4
Creating a
Remote
MEP in an
MA

step.
preceding step.
remote MEPs.
NOTE
remote MEPs.
Issue 02 (2012-12-30)
A.7.7.7
Performing
an LB Test
Required.

226

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

Services)
protection information, and quality of service (QoS) information for an IEEE 802.1D bridgebased Ethernet local area network (E-LAN) service in end-to-end mode and the process of
verifying the service configurations.
Flowchart
Figure 8-45 shows the flowchart for configuring IEEE 802.1D bridge-based E-LAN services.
Figure 8-45 Flowchart for configuring IEEE 802.1D bridge-based E-LAN services
Required
Start
Optional
Configure a LAG.
Configure ERPS
protection.
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
End
Issue 02 (2012-12-30)

227


Step
Operation
Remarks
A.7.2.1
Creating a
LAG

bandwidth.
LAGs.
sharing LAGs.
Issue 02 (2012-12-30)
A.7.2.2
Setting
Parameters
for a LAG
Optional.

228


Step
Operation
Remarks

Instance

Perform the configuration
based on the service plan and
the parameter planning
principles in the operation.

Protocol Parameters

need to be changed.
Guard Time(ms), WTR
network.
Configuring IEEE 802.1D Bridge-based E-LAN Services

Table 8-60 Process of configuring IEEE 802.1D bridge-based E-LAN services
Issue 02 (2012-12-30)
Step
Operation
Remarks
A.3.4.1 Creating a Fiber/

Cable by Using the
Search Method
Perform this task to create microwave links or

Ethernet fibers/cables for service paths if they have not
been created on Main Topology of the U2000.
Set Automatically Allocate Address to No when
creating Ethernet fiber/cable.
A.10.4 Creating an IEEE

802.1D Bridge-based ELAN Service
Optional.
Set related parameters according to the service
planning information and parameter planning
information.

229

Step
Operation
Remarks

Ports Mounted to a
Bridge
Optional.
NOTE
Perform this operation when you need to change the type of
a logical port mounted to a bridge, because an OptiX RTN
310 carries IEEE 802.1D bridge-based services by default.
Configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain

A.7.6.2
Changing
the Packet
Type
Trusted by a
Port

DiffServ domain.
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies


4
Issue 02 (2012-12-30)
A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues

drop.

230

Step
Operation
Remarks
A.7.6.3
Configuring
Port
Shaping


Step
Operation
Remarks
A.10.6
Verifying a
Native
Ethernet
Service
Required.
occurs.
8.7.4.7 Per-NE Configuration Process (IEEE 802.1Q Bridge-based E-LAN Services)

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

231

Figure 8-46 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services
Required
Start
Optional
Configure a LAG.
Configure ERPS
protection.
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
End
Issue 02 (2012-12-30)

232


Step
Operation
Remarks
A.7.2.1
Creating a
LAG

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

Issue 02 (2012-12-30)
Step
Operation
Remarks

Instance


233

Step
Operation
Remarks

Protocol Parameters

need to be changed.
Guard Time(ms), WTR
network.
Configuring IEEE 802.1Q Bridge-based E-LAN Services

Table 8-65 Process of configuring IEEE 802.1Q bridge-based E-LAN services
Issue 02 (2012-12-30)
Step
Operation
Remarks
A.7.3.11 Deleting
an E-LAN Service

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

234

Step
Operation
Remarks
A.7.3.6 Creating an
IEEE 802.1Q
Bridge-based ELAN Service
Required.
l Set VLAN ID for the source and sink according to the
network plan.
l Set Tag Type to C-Aware.
l Set Self-Learning MAC Address to Enabled according
to the network plan.
l Set Encapsulation Type to 802.1Q.
l To disable packet forwarding between certain E-LAN
service ports, configure the ports as Split Horizon
Group Members on the Config Split Horizon Group
window.
l Set Tag according to the following principles:
If all the accessed services carry VLAN tags (tagged
frames), set Tag to Tag Aware.
If none of the accessed services carries VLAN tags
(untagged frames), set Tag to Access, and set Default
network plan.
When the accessed services contain tagged frames
and untagged frames, set Tag to Hybrid, and set
Default VLAN ID and VLAN Priority according to
the network plan.
NOTE
If PLA without NE-level protection has been configured, Ethernet
services do not need to be configured for the standby NE. If 1+1
protection or PLA with NE-level protection has been configured,
configure Ethernet services for the main and standby NEs
consistently.
Issue 02 (2012-12-30)
A.7.3.7 Creating an
E-LAN Service for
Transmitting
Layer 2 Protocol
Packets


235

Step
Operation
Remarks
Mana
ging
the
MAC
addres
s table
A.7.4.2
Creating a
Blacklist
MAC
Address
Entry
Required when usage of E-LAN services needs to be

disabled on certain MAC address host.
A.7.4.1
Creating a
Static
MAC
Address
Entry
Required if you need to set certain MAC address entries not

to age.
A.7.4.3
Managing
a Dynamic
MAC
Address
Table
Required if the aging function needs to be disabled or if the

default aging time (five minutes) needs to be changed.
A.7.5 Setting the

Mode for
Processing an
Unknown Frame of
an E-LAN Service
Optional. By default, the processing mode for unknown

frames is flood.

Issue 02 (2012-12-30)
Step
Operation
Setting the
parameter
s of
Ethernet
ports
Remarks
A.6.1.1
Setting
the Basic
Attribute
s for an
Ethernet
Port
Optional.
value of 9600.

236

Step
Operation
Setting the
parameter
s of
microwav
e ports
Remarks
A.6.1.2
Configuri
ng the
Traffic
Control
Function
for an
Ethernet
Port

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

A.6.2.1
Setting
Basic
Attribute
s for a
Microwav
e Port
Optional.
A.6.2.2
Setting
Layer 2
Attribute
s for a
Microwav
e Port
Optional.
A.6.2.3
Setting
Advanced
Attribute
s for a
Microwav
e Port


desired.

desired.
NOTE
Issue 02 (2012-12-30)

237

Configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain

A.7.6.2
Changing
the Packet
Type
Trusted by a
Port

DiffServ domain.
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies


4
Issue 02 (2012-12-30)
A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues

drop.
A.7.6.3
Configuring
Port
Shaping


238


Step
Operation
Remarks
A.7.7.1
Creating an
MD
A.7.7.2
Creating an
MA
step.
for the NEs.
Period to 1s.
A.7.7.3
Creating an
MEP
preceding step.
service test.
Issue 02 (2012-12-30)

239

Step
Operation
Remarks
A.7.7.4
Creating a
Remote
MEP in an
MA

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

Services)
protection information, and quality of service (QoS) information for an IEEE 802.1Q bridgebased Ethernet local area network (E-LAN) service in end-to-end mode and the process of
verifying the service configurations.
Flowchart
Figure 8-47 shows the flowchart for configuring IEEE 802.1Q bridge-based E-LAN services.
Issue 02 (2012-12-30)

240

Figure 8-47 Flowchart for configuring IEEE 802.1Q bridge-based E-LAN services
Required
Start
Optional
Configure a LAG.
Configure ERPS
protection.
Configure E-LAN
services.
Configure QoS.
Verify Ethernet
services.
End
Issue 02 (2012-12-30)

241


Step
Operation
Remarks
A.7.2.1
Creating a
LAG

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

Issue 02 (2012-12-30)
Step
Operation
Remarks

Instance


242

Step
Operation
Remarks

Protocol Parameters

need to be changed.
Guard Time(ms), WTR
network.
Configuring IEEE 802.1Q Bridge-based E-LAN Services

Table 8-71 Process of configuring IEEE 802.1Q bridge-based E-LAN services
Step
Operation
Remarks
A.7.3.11
Deleting an
E-LAN
Service
A.3.4.1
Creating a
Fiber/Cable
by Using the
Search
Method
Required if microwave links or Ethernet fibers/cables have not

been created for service paths on Main Topology of the U2000.
A.10.5
Creating an
IEEE 802.1Q
Bridge-based
E-LAN
Service
Required.
A.7.3.7
Creating an
E-LAN
Service for
Transmitting
Layer 2
Protocol
Packets
Required when Layer 2 protocol packets need to be transparently

transmitted.
Issue 02 (2012-12-30)
NOTE
Delete the IEEE 802.1D bridge-based E-LAN services that are configured
for an OptiX RTN 310 by default before configuring IEEE 802.1Q bridgebased E-LAN services.


243

Configuring QoS
Step
Operation
Remarks
A.7.6.1
Modifying
the
Mapping
for a DS
Domain

A.7.6.2
Changing
the Packet
Type
Trusted by a
Port

DiffServ domain.
A.7.6.4
Setting
Egress
Queue
Scheduling
Policies


4
Issue 02 (2012-12-30)
A.7.6.5
Setting
Traffic
Shaping for
Egress
Queues

restricted.
A.7.6.6
Setting the
Congestion
Manageme
nt Mode for
Egress
Queues

drop.
A.7.6.3
Configuring
Port
Shaping


244


Step
Operation
Remarks
A.10.6
Verifying a
Native
Ethernet
Service
Required.
occurs.
8.7.5 Configuration Example (Transparently Transmitted Point-toPoint E-Line Services)

This section provides an example of how to configure transparently transmitted point-to-point
Ethernet line (E-Line) services according to the network plan.

As Figure 8-48 illustrates, NE1 is a terminal station of a backhaul network. The service
requirements are as follows:
l
NE1 must transparently transmit the Ethernet services from the NodeB to NE2 in point-topoint manner.
NodeB uses differentiated services code point (DSCP) flags to identify the priorities of the
Ethernet services.
To meet the preceding requirements, transparently transmitted point-to-point E-line services are
configured, and a quality of service (QoS) policy is applied to the services.
Figure 8-48 Networking diagram (transparently transmitted point-to-point E-Line services)
Transparently
transmitted E-line
service
Backhaul network
P&E
NodeB
NE1
Microwave link
Issue 02 (2012-12-30)
NE2
RNC
Ethernet link

245

NOTE
l A P&E port can function as a GE electrical port and its logical port is 1-SHXA2-2(GE1) on the network
management system (NMS).
l The logical port for a microwave port on the NMS is 1-SHXA2-1(IF-1).
8.7.5.2 Service Planning (Port Information)

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

Table 8-74 provides the information about the Ethernet ports that transmit/receive Ethernet
services.
Table 8-74 Ethernet port information
Parameter
1-SHXA2-2(GE1)
Encapsulation Type
Null
Working Mode
Auto-Negotiation
Flow Control
Disabled
NOTE
l In this example, the GE port on the NodeB works in auto-negotiation mode. Therefore, the peer GE port on
NE1 must also work in auto-negotiation mode. If the peer Ethernet port works in another mode, the local
Ethernet port must be set to the same mode. The working modes of the Ethernet ports inside the network
are planned as auto-negotiation.
l Generally, the flow control function is enabled only when an NE or the peer equipment is inadequate for
quality of service (QoS) processing. The planning information of flow control must be the same for the
equipment at both ends.
Microwave Port Information

Table 8-75 provides the information about the microwave ports that transmit/receive services.
Table 8-75 Microwave port information
Parameter
1-SHXA2-1(IF)
Encapsulation Type
Null
8.7.5.3 Service Planning (Ethernet Protection)

In this example, Ethernet protection is not used.
Issue 02 (2012-12-30)

246

8.7.5.4 Service Planning (Ethernet Services)

This section describes the parameters required for configuring Ethernet services.
Table 8-76 provides the planning information about an Ethernet service.
Table 8-76 Information about a transparently transmitted point-to-point E-Line service
Parameters
NE1
Service ID
Service Name
NodeBtoNE2_Tline
L2 Protocol Control
Not transparently transmitted
Source Port
1-SHXA2-2(GE1)
Source C-VLANs
Blank
Sink Port
1-SHXA2-1(IF)
Sink C-VLANs
Blank
8.7.5.5 Service Planning (QoS)

This section describes the parameters required for configuring quality of service (QoS).
Diffserv
DiffServ (DS) is the basis for QoS. It is recommended that a VLAN priority or differentiated
services code point (DSCP) value be allocated to a base station service based on the service type.
The transport network creates the corresponding DS domain according to the allocated VLAN
priority or DSCP value. All ports involved in the service must use the same DS configuration.
In this example, services from the base stations are allocated DSCP values based on service
types, and the OptiX RTN 310s allocate per-hop behaviors (PHBs) according to the DSCP
values. For details, see Table 8-77.
Table 8-77 PHBs and service types
Issue 02 (2012-12-30)
PHB
DSCP
Service Type
CS7
56
CS6
48
EF
40
Real-time voice services

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

247

PHB
DSCP
Service Type
AF31
28
O&M and high-priority realtime HSDPA services (O&M

and HSPA streaming
services)
AF33
24
Low-priority real-time
HSDPA service (HSPA
streaming service)
AF21
20
High-priority non-real-time
R99 services (R99 interactive
and R99 background
services)
AF23
16
Low-priority non-real-time
and R99 background
services)
AF11
12
AF13
BE
HSDPA data services (HSPA

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

Because the transmission rate of an Ethernet port is much higher than the volume of traffic,
congestion never occurs at an Ethernet port. Therefore, queue scheduling policy and congestion
management mode need to be planned only for microwave ports. Retain the default queue
scheduling policy and congestion management mode for an Ethernet port.
Table 8-78 and Table 8-79 list the queue scheduling policies and congestion management modes
for services of various priorities on microwave ports in this example.
Table 8-78 Queue scheduling policies
Issue 02 (2012-12-30)
PHB
Queue Scheduling Policy
CS7
SP
CS6
SP
248

PHB
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Table 8-79 Congestion management mode

PHB
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64 (green)
42 (green)
100
AF4
Tail drop
AF3
WRED
64 (green)
42 (green)
100
42 (red)
21 (red)
64 (green)
42 (green)
42 (red)
21 (red)
AF2
WRED
100
AF1
Tail drop
BE
WRED
64 (green)
42 (green)
100
Service Flow Shaping

Generally, a microwave backhaul network does not perform shaping for service flows because
2G/3G base stations and RNCs have their own traffic control policies (BSC is short for base
station controller, and RNC for radio network controller).
Port Shaping
If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth for
aggregation services, you can enable port shaping at the edge node to limit the Ethernet service
traffic sent to the convergence node. This prevents congestion at the convergence node.
In this example, you do not need to enable port shaping.
Issue 02 (2012-12-30)

249

8.7.5.6 Per-NE Configuration Procedure (Ethernet Protection)

8.7.5.7 Per-NE Configuration Procedure (Ethernet Ports)

This section describes the procedure for configuring service information.
Procedure
Step 1 Delete Ethernet local area network (E-LAN) services. For details, see A.7.3.11 Deleting an ELAN Service.
Step 2 Create a transparently transmitted point-to-point Ethernet line (E-Line) service. For details, see
A.7.3.1 Creating a Point-to-Point Transparently Transmitted E-Line Service.
This table provides service parameter values.
Parameter
Value
Service ID
Service Name
NodeBtoNE2_Tline
Direction
UNI-UNI
L2 Protocol Control
Not Transparent
Source
1-SHXA2-2
Sink
1-SHXA2-1
This table provides port parameter values

Port
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
VLAN ID (e.g. 1,3-5)
Blank
Blank
Working Mode
Auto-Negotiation
Encapsulation Type
Null
Null
Tag
----End
8.7.5.8 Per-NE Configuration Procedure (QoS)

This section describes the procedure for configuring quality of service (QoS).
Issue 02 (2012-12-30)

250

Procedure
Step 1 Modify the mapping for a Differentiated Services (DS) domain. For details, see A.7.6.1
Modifying the Mapping for a DS Domain.
TThis table provides parameter values on the Ingress tab page.
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
This table provides parameter values on the Egress tab page.
Issue 02 (2012-12-30)
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6

251

CVLAN
MPLS EXP
IP DSCP
PHB
56
CS7
Step 2 Change the packet type trusted by ports. For details, see A.7.6.2 Changing the Packet Type
Trusted by a Port.
Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-1
NOTE
The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet type
Step 3 Set egress queue scheduling policies. For details, see A.7.6.4 Setting Egress Queue Scheduling
Policies.
This table provides relayed parameters on microwave ports.
Parameter
Grooming Police After Reloading
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Step 4 Set the congestion management mode for egress queues. For details, see A.7.6.6 Setting the
Congestion Management Mode for Egress Queues.
This table provides relayed parameters on microwave ports.
Parameter
CS7
Issue 02 (2012-12-30)
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
Tail drop

252

Parameter
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS6
Tail drop
EF
WRED
64(Green)
42 (Green)
100
AF4
Tail drop
AF3
WRED
64(Green)
42 (Green)
100
42 (Red)
21 (Red)
64(Green)
42 (Green)
42 (Red)
21 (Red)
AF2
WRED
100
AF1
Tail drop
BE
WRED
64(Green)
42 (Green)
100
----End
8.7.5.9 Per-NE Configuration Procedure (Ethernet Service Verification)

This section describes the procedure for verifying Ethernet service configurations.
Procedure
Step 1 Create a maintenance domain (MD). For details, see A.7.7.1 Creating an MD.
This table provides parameter values for creating an MD.
Parameter
Value
NE1
Maintenance Domain Name
InterNE
Maintenance Domain Level
Step 2 Create a maintenance association (MA). For details, see A.7.7.2 Creating an MA.
This table provides parameter values for creating an MA.
Parameter
Value
NE1
Issue 02 (2012-12-30)
InterNE
Maintenance Association Name
NodeB_Tline

253

Parameter
Value
NE1
Relevant Service
1-NodeBtoNE2_Tline
CC Test Transmit Period
1s
Step 3 Create maintenance association end points (MEPs). For details, see A.7.7.3 Creating an
MEP.
This table provides parameter values for creating MEPs.
Parameter
Value
NE1
Maintenance Domain
Name
InterNE
InterNE
Maintenance Association
Name
NodeB_Tline
NodeB_Tline
Board
1-SHXA2
1-SHXA2
Port
1-SHXA2-2
1-SHXA2-1
VLAN
MP ID
101
102
Direction
Ingress
Ingress
CC Status
Active
Active
Step 4 Perform a loopback (LB) test to verify Ethernet service configurations. For details, see A.7.7.7
Performing an LB Test.
Perform the LB test by considering the MEP whose MEP ID is 101 as the source MEP and the
MEP whose MEP ID is 102 as the sink MEP.
There should be no packet loss during the test.
----End
8.7.5.10 End-to-End Configuration Procedure

In this configuration example, service configuration is performed only on a single NE. Therefore,
end-to-end service configuration is not involved.
8.7.6 Configuration Example (VLAN-based E-Line Service)

This section provides an example of how to configure VLAN-based E-line services according
Issue 02 (2012-12-30)

254


Based on 8.6.3 Configuration Example (Microwave Links on a Microwave Chain
Network), configure Ethernet services according to the following requirements:
l
Each of NodeB 1, NodeB 2, and NodeB 3 provides a 1000 Mbit/s GE port in autonegotiation mode.
VLAN IDs of Ethernet services transmitted by NodeB 1, NodeB 2, and NodeB 3 are 100,
200, and 300 respectively.
NodeB 1, NodeB 2, and NodeB 3 use DSCP flags to identify the priorities of Ethernet
services.
To meet the preceding requirements, VLAN-based Ethernet line (E-Line) services are
configured for service transmission on each NE. In addition, corresponding quality of service
(QoS) processing is configured.
Figure 8-49 Networking diagram (VLAN-based E-Line services)
NMS
LAN switch
NE11
P&E
NE99_1
NE13
V-polarization
P&E
GE
NodeB 1
VLAN 100
GE
COMBO
COMBO
COMBO
COMBO
GE
GE
Local backhaul
network
RNC
P&E
NE12
H-polarization
NE14
P&E
GE
P&E
NodeB 2
VLAN 200
GE
P&E
NE21
NE22
NE24
NE99_2
NE23
NodeB 3
VLAN 300
OptiX RTN 900
Issue 02 (2012-12-30)
Microwave link
Ethernet link

XPIC cable
255

NOTE
(GE1).
8.7.6.2 Service Planning (Ethernet Ports)

ports.

Table 8-80 and Table 8-81 provide the information about the Ethernet ports that transmit/receive
Ethernet services.
Table 8-80 Information about Ethernet ports on XPIC links
Parame
ter
NE11
NE12
NE13
NE14
1SHXA2
-2(GE1)
1SHXA2
-3(GE2)
1SHXA2
-3(GE2)
1SHXA2
-2(GE1)
1SHXA2
-3(GE2)
1SHXA2
-2(GE1)
1SHXA2
-3(GE2)
Encapsul
ation
Type
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q
Working
Mode
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
Flow
Control
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Tag
Type
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Table 8-81 Information about Ethernet ports on non-XPIC links

Parameter
Encapsulatio
n Type
Issue 02 (2012-12-30)
NE21
NE22
NE23
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q

NE24
256

Parameter
NE21
NE22
NE23
NE24
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
Working
Mode
AutoNegotiation
AutoNegotiation
AutoNegotiation
AutoNegotiation
AutoNegotiation
Flow Control
Disabled
Disabled
Disabled
Disabled
Disabled
Tag Type
Tag Aware
Tag Aware
Tag Aware
Tag Aware
Tag Aware
NOTE
l In this example, the GE ports on all the NodeBs work in auto-negotiation mode. Therefore, the peer GE port
of each NE that receives services must work in auto-negotiation mode. 1-SHXA2-1(IF) the peer Ethernet
port works in another mode, the local Ethernet port must be set to the same mode. The working modes of
the Ethernet ports inside the network are planned as auto-negotiation.
l In this example, all the services carry VLAN IDs. Therefore, the TAG attributes of all the ports are Tag
Aware.

Table 8-82 and Table 8-83 provides the information about the microwave ports that transmit/
receive services.
Table 8-82 Information about microwave ports on XPIC links
Parameter
NE11
NE12
NE13
NE14
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
Encapsulation
Type
802.1Q
802.1Q
802.1Q
802.1Q
Tag Type
Tag Aware
Tag Aware
Tag Aware
Tag Aware
Table 8-83 Information about microwave ports on non-XPIC links

Parameter
Issue 02 (2012-12-30)
NE21
NE22
NE23
NE24
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
Encapsulation
Type
802.1Q
802.1Q
802.1Q
802.1Q
Tag Type
Tag Aware
Tag Aware
Tag Aware
Tag Aware

257


This section describes the parameters required for configuring Ethernet protection.
In this example, it is assumed that PLA has been configured during microwave link
configuration. Therefore, Ethernet protection is not required.

Figure 8-50 provides the planning information of the VLAN-based Ethernet line (E-Line)
services between NEs.
Figure 8-50 Information about VLAN-based E-Line services
Links-1: NE13-NE11V-polarization
NE13
NE11
IF
RNC - NodeB 1
IF
C:100V
GE1(C:100)
GE1(C:100)
Links-2: NE24-NE23-NE22-NE21
RNC - NodeB 3
RNC - NodeB 2
NE24
NE23
IF
IF GE2
NE22
GE2 IF
NE21
IF
C:300
GE1(C:300)
GE1(C:300)
C:200
C:200
C:200
GE1(C:200)
GE1(C:200)
C: C-VLAN
Pass through
Add/Drop
Foward
Table 8-84 and Table 8-85 provide detailed planning information about services on each NE.
Table 8-84 Information about VLAN-based E-Line services on XPIC links
Parameter
Issue 02 (2012-12-30)
NE13
NE11
NE14
NE11 to the RNC
NodeB 1 to NE13
NE11 to the RNC
Service ID
Service name
NE11toRNC_Vline
NodeB1toNE13_Vli
ne
NE11toRNC_Vline

258

Parameter
NE13
NE11
NE14
NE11 to the RNC
NodeB 1 to NE13
NE11 to the RNC
L2 protocol control
Not transparently
transmitted
Not transparently
transmitted
Not transparently
transmitted
Source port
1-SHXA2-1(IF)
1-SHXA2-2(GE1)
1-SHXA2-1(IF)
Source C-VLAN IDs
100
100
100
Sink port
1-SHXA2-2(GE1)
1-SHXA2-1(IF)
1-SHXA2-2(GE1)
Sink C-VLAN IDs
100
100
100
Table 8-85 Information about VLAN-based E-Line services on non-XPIC links

Parameter
NE24
NE23
NE22
NE21
NE23 to
NE99
NE22 to
NE24
NodeB 3 to
NE24
NE21 to
NE23
NodeB 2 to
NE22
Service ID
Service
name
NE23toNE9
9_Vline
NE22toNE2
4_Vline
NodeB3toN
E24_Vline
NE21toNE2
3_Vline
NodeB2toN
E22_Vline
L2 protocol
control
Not
transparently
transmitted
Not
transparently
transmitted
Not
transparently
transmitted
Not
transparently
transmitted
Not
transparently
transmitted
Source port
1-SHXA2-1
(IF)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
1-SHXA2-1
(IF)
1-SHXA2-2
(GE1)
Source CVLAN IDs
300,200
300,200
300
200
200
Sink port
1-SHXA2-2
(GE1)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-3
(GE2)
1-SHXA2-1
(IF)
Sink CVLAN IDs
300,200
300,200
300
200
200

Diffserv
Issue 02 (2012-12-30)

259

PHB
DSCP
Service Type
CS7
56
CS6
48
EF
40

signaling
AF41
36
AF43
32
AF31
28

and HSPA streaming
services)
AF33
24
HSDPA service (HSPA
streaming service)
AF21
20
and R99 background
services)
AF23
16
and R99 background
services)
AF11
12
AF13
BE

services)
NOTE
Issue 02 (2012-12-30)

260


PHB
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP

PHB
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64 (green)
42 (green)
100
AF4
Tail drop
AF3
WRED
64 (green)
42 (green)
100
42 (red)
21 (red)
64 (green)
42 (green)
42 (red)
21 (red)
AF2
Issue 02 (2012-12-30)
WRED
100
AF1
Tail drop
BE
WRED
64 (green)
42 (green)
100

261


Port Shaping

8.7.6.7 Per-NE Configuration Procedure (Service Information)

Procedure
Step 2 Create a VLAN-based Ethernet line (E-Line) service. For details, see A.7.3.2 Creating a VLANbased E-Line Service.
l Cross polarization interference cancellation (XPIC) links
Parameters of NE11 and NE13
Parameter
NE13
NE11
NE11 to RNC
NodeB 1 to NE13
Service ID
Service Name
NE11toRNC_Vline
NodeB1toNE13_Vline
Direction
UNI-UNI
UNI-UNI
Source
1-SHXA2-1
1-SHXA2-2
Sink
1-SHXA2-2
1-SHXA2-1
Issue 02 (2012-12-30)

262

Parameter
NE13
NE11
1-SHXA2-2
1-SHXA2-1
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
Enabled
VLAN ID
(e.g. 1,3-5)
100
100
100
100
Working
Mode
AutoNegotiation
AutoNegotiation
Encapsulatio
n Type
802.1Q
802.1Q
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
Tag Aware
Tag Aware
Parameters of NE14
Parameter
NE14
NE11 to RNC
Service ID
Service Name
NE11toRNC_Vline
Direction
UNI-UNI
Source
1-SHXA2-1
Sink
1-SHXA2-2

Parameter
NE14
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
100
100
Working Mode
Auto-Negotiation
Encapsulation Type
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
l Non-XPIC links
Parameters of NE21
Issue 02 (2012-12-30)

263

Parameter
NE21
NodeB 2 to NE22
Service ID
Service Name
NodeB2toNE22_Vline
Direction
UNI-UNI
Source
1-SHXA2-2
Sink
1-SHXA2-1

Parameter
NE21
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
200
200
Working Mode
Auto-Negotiation
Encapsulation Type
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
Parameters of NE22
Parameter
NE22
NE21 to NE23
Service ID
Service Name
NE21toNE23_Vline
Direction
UNI-UNI
Source
1-SHXA2-1
Sink
1-SHXA2-3
Issue 02 (2012-12-30)

264

Parameter
NE22
1-SHXA2-3
1-SHXA2-1
Port Enable
Enabled
200
200
Working Mode
Auto-Negotiation
Encapsulation Type
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
Parameters of NE23
Parameter
NE23
NE22 to NE24
NodeB 3 to NE24
Service ID
Service Name
NE22toNE24_Vline
NodeB3toNE24_Vline
Direction
UNI-UNI
UNI-UNI
Source
1-SHXA2-3
1-SHXA2-2
Sink
1-SHXA2-1
1-SHXA2-1

Parameter
NE23
1-SHXA2-3
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
Enabled
VLAN ID (e.g.
1,3-5)
200
300
300,200
Working Mode
Auto-Negotiation
Auto-Negotiation
Encapsulation
Type
802.1Q
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
Tag Aware
Parameters of NE24
Issue 02 (2012-12-30)

265

Parameter
NE24
NE23 to NE99
Service ID
Service Name
NE23toNE99_Vline
Direction
UNI-UNI
Source
1-SHXA2-1
Sink
1-SHXA2-2

Parameter
NE24
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
300,200
300,200
Working Mode
Auto-Negotiation
Encapsulation Type
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
----End

Procedure
This table provides parameter values on the Ingress tab page.
Issue 02 (2012-12-30)
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23

266

CVLAN
MPLS EXP
IP DSCP
PHB
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7

CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Step 2 Change the ports applied to the DS domain and their trusted packet types. For details, see A.
7.6.2 Changing the Packet Type Trusted by a Port.
This table provides parameter values for NE11, NE13, NE14, and NE23.
Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-3
1-SHXA2-1
Issue 02 (2012-12-30)

267

This table provides parameter values for NE22.

Parameter
Packet Type
1-SHXA2-3
ip-dscp
1-SHXA2-1

Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-1
NOTE
The desired trusted packet type of the port is not the C-VLAN priority but DSCP value. Therefore, the trusted
packet type needs to be changed for service-associated Ethernet ports in the default DS domain.
Policies.
This table provides parameter values for microwave ports on NE11 to NE14 and NE21 to NE24.
Parameter
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Issue 02 (2012-12-30)

268

Parameter
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64(Green)
42 (Green)
100
AF4
Tail drop
AF3
WRED
64(Green)
42 (Green)
100
42 (Red)
21 (Red)
64(Green)
42 (Green)
42 (Red)
21 (Red)
AF2
WRED
100
AF1
Tail drop
BE
WRED
64(Green)
42 (Green)
100
----End

Procedure
Step 1 Create maintenance domains (MDs) for NE11, NE13, NE21, NE23, and NE24. For details, see
A.7.7.1 Creating an MD.
This table provides parameter values for creating MDs for NE11, NE13, NE21, NE23, and NE24.
Parameter
Value
NE11
NE13
NE21
NE23
NE24
Maintenanc
e Domain
Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenanc
e Domain
Level
Step 2 Create maintenance associations (MAs) for NE11, NE13, NE21, NE23, and NE24. For details,
see A.7.7.2 Creating an MA.
l This table provides parameter values for creating MAs for NE11 and NE13.
Issue 02 (2012-12-30)

269

Parameter
Value
NE11
NE13
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
NodeB1_Vline
NodeB1_Vline
Relevant Service
1-NodeB1toNE13_Vline
1-NE11toRNC_Vline
1s
1s
l This table provides parameter values for creating MAs for NE21, NE23, and NE24.
Parameter
Value
NE21
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
NodeB2_Vline
NodeB3_Vline
NodeB2_Vline
NodeB3_Vline
Relevant
Service
1NodeB2toNE2
2_Vline
1NodeB3toNE2
4_Vline
NE23toNE99_
Vline
NE23toNE99_
Vline
CC Test
Transmit
Period
1s
1s
1s
1s
MEP.
l This table provides parameter values for creating MEPs for NE11 and NE13.
Parameter
Issue 02 (2012-12-30)
Value
NE11
NE13
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
NodeB1_Vline
NodeB1_Vline
Board
1-SHXA2
1-SHXA2
Port
1-SHXA2-2
1-SHXA2-2
VLAN
100
100

270

Parameter
Value
NE11
NE13
MP ID
101
102
Direction
Ingress
Ingress
CC Status
Active
Active
l This table provides parameter values for creating MEPs for NE21, NE23, and NE24.
Parameter
Value
NE21
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
NodeB2_Vline
NodeB3_Vline
NodeB2_Vline
NodeB3_Vline
Board
1-SHXA2
1-SHXA2
1-SHXA2
1-SHXA2
Port
1-SHXA2-2
1-SHXA2-2
1-SHXA2-2
1-SHXA2-2
VLAN
200
300
200
300
MP ID
201
301
202
302
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Step 4 Specify remote MEPs. For details, see A.7.7.4 Creating a Remote MEP in an MA.
l This table provides parameter values for creating remote MEPs for NE11 and NE13.
Parameter
Value
NE11
NE13
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
NodeB1_Vline
NodeB1_Vline
MP ID
102
101
l This table provides parameter values for creating remote MEPs for NE21, NE23, and NE24.
Issue 02 (2012-12-30)

271

Parameter
Value
NE21
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
NodeB2_Vline
NodeB3_Vline
NodeB2_Vline
NodeB3_Vline
Remote
Maintenance
Point ID(e.g:
1,3-6)
202
302
201
301
Step 5 Perform loopback (LB) tests. For details, see A.7.7.7 Performing an LB Test.
There should be no packet loss during the tests.
----End
8.7.6.10 End-to-End Configuration Procedure (Ethernet Protection)

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

Context
NOTE
It is recommended that you configure microwave links for which the cross polarization interference cancellation
(XPIC) function is enabled on a per NE basis, because Ethernet services on the links are transparently transmitted
using Layer 2 protocols. This configuration example is for configuring Ethernet services on non-XPIC links.
Procedure
Step 2 Create optical fibers manually. For details, see A.3.4.1 Creating a Fiber/Cable by Using the
Search Method.
This table provides parameter values for creating optical fibers manually.
Issue 02 (2012-12-30)

272

Parameter
Value
GE Optical Fiber between NE23 and
NE22
Fiber/Cable Type
Fiber
Source NE
NE23
Source Board
GE2
Source Port
Sink NE
NE22
Sink Board
GE2
Sink Port
Automatically Allocate IP Address
No
NOTE
This example is based on the hypothesis that the microwave links have been created during microwave link
configuration.
Step 3 Create Ethernet line (E-Line) services transmitted in Native Ethernet mode. For details, see A.
10.3 Creating a VLAN-based E-Line Service.
1.
Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
2.
Set the basic attributes for the E-Line service.
3.
Configure the source and sink of the E-Line service.

a.
Double-click the source NE (NE24) in the Physical Topology tab page.
b.
Select GE1, set C-VLAN to 200 and set S-VLAN to blank.
c.
Click OK.
d.
Double-click the sink NE (NE23) in the Physical Topology tab page.
e.
Select GE1, set C-VLAN to 200 and set S-VLAN to blank.
f.
Click OK.
4.
Click Calculate Route.
5.
Check the service path and VLAN information.
Issue 02 (2012-12-30)

273

6.
Select Deploy and ETH OAM CC.
7.
Click OK.
8.
Repeat Step 3.1 to Step 3.7 and configure the Ethernet services from the radio network
controller (RNC) to NodeB 2 according to the planned values in 8.7.6.4 Service Planning
(Ethernet Services).
----End
8.7.6.12 End-to-End Configuration Procedure (QoS)

Procedure
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Issue 02 (2012-12-30)

274

CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Step 2 Change the ports applied to the DS domain and their trusted packet types. For details, see A.
7.6.2 Changing the Packet Type Trusted by a Port.
Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-3
1-SHXA2-1

Parameter
Packet Type
1-SHXA2-3
ip-dscp
1-SHXA2-1

Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-1
Issue 02 (2012-12-30)

275

NOTE
Policies.
Parameter
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Parameter
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64(Green)
42 (Green)
100
AF4
Tail drop
AF3
WRED
64(Green)
42 (Green)
100
42 (Red)
21 (Red)
64(Green)
42 (Green)
42 (Red)
21 (Red)
AF2
WRED
100
AF1
Tail drop
BE
WRED
64(Green)
42 (Green)
100
----End
Issue 02 (2012-12-30)

276

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

Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the main
menu.
Step 2 In the Set Filter Criteria dialog box, set filter conditions and click Filter.
The Native Ethernet services that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet service, and choose Ethernet OAM > LB Test from
the shortcut menu.
Step 4 In the LB Test dialog box, select the desired service trail.
NOTE
l An LB test checks whether a service is bidirectional available. For a bidirectional service, select the
NE at either end to initiate an LB test.
l If Ethernet services are in different VLANs, the U2000 automatically selects the service in a VLAN
for an LB test.
l One NE cannot be involved in multiple LB tests simultaneously.
Step 5 Optional: Choose Config LB Parameter from the shortcut menu. Set Sent Packets, Sent
Packets Length, and Sent Packets Priority. Then, click OK.
Step 6 Click Run.

Step 7 Click the LB Testing Information and LB Statistics Information tabs, and determine whether
the service is available based on the displayed information.
Normally, Test Results indicates Test Succeeded.
Issue 02 (2012-12-30)

277

Step 8 Repeat steps Step 3 to Step 7 to verify the Ethernet services transmitted from the radio network
controller (RNC) to NodeB 2.
----End
8.7.7 Configuration Example (IEEE 802.1D Bridge-based E-LAN

Service)
This section provides an example of how to configure IEEE 802.1D bridge-based Ethernet local
area network (E-LAN) services according to the network plan.

Based on 8.6.4 Configuration Example (Microwave Links on a Microwave Ring
Network), configure Ethernet services according to the actual requirements.
l
Each of NodeB 1 and NodeB 2 provides a 1000 Mbit/s GE port in auto-negotiation mode.
Ethernet services on a ring network need to be protected.
Services from base stations need to be transparently transmitted.
NodeB 1 and NodeB 2 use DSCP flags to identify the priorities of the Ethernet services.
The network must provide the service loop detection function and the broadcast packet
suppression function.
To meet the preceding requirements, IEEE 802.1D bridge-based E-LAN services are configured
to transmit services from base stations. In addition, the following functions are configured for
the services: service loop test, broadcast packet suppression, ERPS protection, and QoS
processing. See Figure 8-51.
Issue 02 (2012-12-30)

278

Figure 8-51 Networking diagram (IEEE 802.1D bridge-based E-LAN services)
NMS
NodeB 1
P&E
GE
NE31
802.1D bridge
LAN switch
GE
NE36
802.1D bridge
P&E
Local backhaul
network
RNC
GE
GE NE35
NE32
802.1D bridge
802.1D bridge
GE
GE
P&E
NodeB 2
NE33
802.1D bridge
Microwave link
NE34
802.1D bridge
Ethernet link
NOTE
(GE1).

ports.

Table 8-89 provides the information about the Ethernet ports that transmit/receive Ethernet
services.
Issue 02 (2012-12-30)

279

NOTE
On the NMS, the logical port of a COMBO port that functions as an optical GE port is 1-SHXA2-2(GE1).
On the NMS, the logical port of a P&E port is 1-SHXA2-2(GE1), when the COMBO port does not function
as an optical GE port.
On the NMS, the logical port of a COMBO port that functions as a 1+1 concatenation port is 1-SHXA2-4.
This port is valid only when DCN is being configured.
Table 8-89 Ethernet port information

Parameter
Encapsulati
on Type
Working
Mode
Flow
Control
Broadcast
Packet
Suppressio
n
Broadcast
Packet
Suppressio
n Threshold
NE31
1-SHXA2-3
(GE2)
Null
AutoNegotiation
Disabled
Enabled
30
NE32
1-SHXA2-3
(GE2)
Null
AutoNegotiation
Disabled
Enabled
30
NE33
1-SHXA2-2
(GE1)
Null
AutoNegotiation
Disabled
Enabled
30
1-SHXA2-3
(GE2)
Null
AutoNegotiation
Disabled
Enabled
30
NE34
1-SHXA2-3
(GE2)
Null
AutoNegotiation
Disabled
Enabled
30
NE35
1-SHXA2-2
(GE1)
Null
AutoNegotiation
Disabled
Enabled
30
1-SHXA2-3
(GE2)
Null
AutoNegotiation
Disabled
Enabled
30
1-SHXA2-2
(GE1)
Null
AutoNegotiation
Disabled
Enabled
30
1-SHXA2-3
(GE2)
Null
AutoNegotiation
Disabled
Enabled
30
NE36
NOTE
of each NE that receives services must work in auto-negotiation mode. 1-SHXA2-1(IF-1) the peer Ethernet
l In this example, the loopback port shutdown function is disabled for the Ethernet ports.

Table 8-90 provides the information about the microwave ports that transmit/receive services.
Issue 02 (2012-12-30)

280

Table 8-90 Microwave port information

Parameter
Encapsulation
Type
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
NE31
1-SHXA2-1
(IF-1)
Null
Enabled
30
NE32
1-SHXA2-1
(IF-1)
Null
Enabled
30
NE33
1-SHXA2-1
(IF-1)
Null
Enabled
30
NE34
1-SHXA2-1
(IF-1)
Null
Enabled
30
NE35
1-SHXA2-1
(IF-1)
Null
Enabled
30
NE36
1-SHXA2-1
(IF-1)
Null
Enabled
30

Information About ERP Instances

Table 8-91 provides the planning information about Ethernet ring protection (ERP) instances.
Table 8-91 Information about ERP instances
Issue 02 (2012-12-30)
Item
NE31
NE32
NE33
NE34
NE35
NE36
ERPS ID
East Port
1SHXA2-1
(IF-1)
1SHXA2-3
(GE2)
1SHXA2-1
(IF-1)
1SHXA2-3
(GE2)
1SHXA2-1
(IF-1)
1SHXA2-3
(GE2)
West Port
1SHXA2-3
(GE2)
1SHXA2-1
(IF-1)
1SHXA2-3
(GE2)
1SHXA2-1
(IF-1)
1SHXA2-3
(GE2)
1SHXA2-1
(IF-1)
RPL
Owner
Ring Node
Flag
No
Yes
No
No
No
No

281

Item
NE31
NE32
NE33
NE34
NE35
NE36
RPL Port
1SHXA2-3
(GE2)
Control
VLAN
4093
4093
4093
4093
4093
4093
Packet
Transmit
Interval(s)
5s (default
value)
5s (default
value)
5s (default
value)
5s (default
value)
5s (default
value)
5s (default
value)
Entity
Level
4 (default
value)
4 (default
value)
4 (default
value)
4 (default
value)
4 (default
value)
4 (default
value)
WTR
Time
5 minutes
(default
value)
Guard
Time (ms)
500 ms
(default
value)
500 ms
(default
value)
500 ms
(default
value)
500 ms
(default
value)
500 ms
(default
value)
500 ms
(default
value)
Hold-Off
Time (ms)
0s (default
value)
0s (default
value)
0s (default
value)
0s (default
value)
0s (default
value)
0s (default
value)
NOTE
l In this example, all the services are aggregated on NE35. Therefore, the NE that is farthest from NE35 needs
to function as the RPL owner. In this manner, when the ring network is normal, the traffic carried on each
link is relatively even.
l The control VLAN ID must be unique. It is recommended that the control VLAN ID take the value 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally take their
default values.

Table 8-92 provides the planning information about an IEEE 802.1D bridge-based Ethernet
service.
Table 8-92 Information About an IEEE 802.1D bridge-based E-LAN service
Issue 02 (2012-12-30)
Paramete
r
NE31
NE32
NE33
NE34
NE35
NE36
Service ID
Service
Name
Dlan
Dlan
Dlan
Dlan
Dlan
Dlan

282

Paramete
r
NE31
NE32
NE33
NE34
NE35
NE36
Tag Type
TagTranspare
nt
TagTranspare
nt
TagTranspare
nt
TagTranspare
nt
TagTranspare
nt
TagTranspare
nt
MAC
Address
Learning
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
MAC
Address
Learning
Mode
SVL
SVL
SVL
SVL
SVL
SVL
Mounted
UNI port
1SHXA2-3
(GE2)
1SHXA2-3
(GE2)
1SHXA2-2
(GE1)
1SHXA2-3
(GE2)
1SHXA2-2
(GE1)
1SHXA2-2
(GE1)
1SHXA2-1
(IF-1)
1SHXA2-1
(IF-1)
1SHXA2-3
(GE2)
1SHXA2-1
(IF-1)
1SHXA2-3
(GE2)
1SHXA2-3
(GE2)
1SHXA2-1
(IF-1)
1SHXA2-1
(IF-1)
1SHXA2-1
(IF-1)

Diffserv
Issue 02 (2012-12-30)
PHB
DSCP
Service Type
CS7
56
CS6
48

283

PHB
DSCP
Service Type
EF
40

signaling
AF41
36
AF43
32
AF31
28

and HSPA streaming
services)
AF33
24
HSDPA service (HSPA
streaming service)
AF21
20
and R99 background
services)
AF23
16
and R99 background
services)
AF11
12
AF13
BE

services)
NOTE

Issue 02 (2012-12-30)

284


PHB
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP

PHB
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64 (green)
42 (green)
100
AF4
Tail drop
AF3
WRED
64 (green)
42 (green)
100
42 (red)
21 (red)
64 (green)
42 (green)
42 (red)
21 (red)
AF2
WRED
100
AF1
Tail drop
BE
WRED
64 (green)
42 (green)
100

Issue 02 (2012-12-30)

285

Port Shaping

This section describes the procedure for configuring Ethernet protection.
Procedure
Step 1 Create an Ethernet ring protection switching (ERP) instance. For details, see A.7.1.1 Creating
an ERP Instance.
This table provides parameter values for creating an ERP instance.
Paramete
r
Value
NE31
NE32
NE33
NE34
NE35
NE36
ERPS ID
East Port
1SHXA2-1
1SHXA2-3
1SHXA2-1
1SHXA2-3
1SHXA2-1
1SHXA2-3
West Port
1SHXA2-3
1SHXA2-1
1SHXA2-3
1SHXA2-1
1SHXA2-3
1SHXA2-1
RPL
Owner
Ring
Node Flag
No
Yes
No
No
No
No
RPL Port
1SHXA2-3
Control
VLAN
4093
4093
4093
4093
4093
4093
----End

Procedure
Step 1 Configure Ethernet local area network (E-LAN) services based on the IEEE 802.1D bridge. For
details, see A.7.3.5 Creating an IEEE 802.1D Bridge-based E-LAN Service.
l Parameters of NE31, NE32, and NE34
This table lists the ports to be selected.
Issue 02 (2012-12-30)

286

Port
1-SHXA2-3
1-SHXA2-1

Parameter
Value
Service ID
Service Name
Dlan
Direction
Tag-Transparent
L2 Protocol Control
Not Transparent
MAC Address Learning
Enabled

Parameter
1-SHXA2-3
1-SHXA2-1
Port Enable
Enabled
Blank
Blank
Working Mode
Auto-Negotiation
Encapsulation Type
Null
Null
Tag
l Parameters of NE33, NE35, and NE36

This table lists the ports to be selected.
Port
1-SHXA2-2
1-SHXA2-3
1-SHXA2-1
Issue 02 (2012-12-30)
Parameter
Value
Service ID
1
287

Parameter
Value
Service Name
Dlan
Direction
Tag-Transparent
L2 Protocol Control
Not Transparent
Enabled

Parameter
1-SHXA2-2
1-SHXA2-3
1-SHXA2-1
Port Enable
Enabled
Enabled
VLAN ID (e.g.
1,3-5)
Blank
Blank
Blank
Working Mode
Auto-Negotiation
Auto-Negotiation
Encapsulation
Type
Null
Null
Null
Tag
----End

This section describes the procedure for configuring Ethernet ports and microwave ports.
Procedure
Step 1 Configure the advanced attributes of Ethernet ports. For details, see A.6.1.4 Setting the
Advanced Attributes for an Ethernet Port.
This table provides parameter values for Ethernet ports.
Parameter
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
NE31
1-SHXA2-3
Enabled
Enabled
30
NE32
1-SHXA2-3
Enabled
Enabled
30
NE33
1-SHXA2-2
Enabled
Enabled
30
1-SHXA2-3
Enabled
Enabled
30
1-SHXA2-3
Enabled
Enabled
30
NE34
Issue 02 (2012-12-30)
Loopback
Check

288

Parameter
NE35
NE36
Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
1-SHXA2-2
Enabled
Enabled
30
1-SHXA2-3
Enabled
Enabled
30
1-SHXA2-2
Enabled
Enabled
30
1-SHXA2-3
Enabled
Enabled
30
This table provides parameter values for microwave ports.

Parameter
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
NE31
1-SHXA2-1
Enabled
30
NE32
1-SHXA2-1
Enabled
30
NE33
1-SHXA2-1
Enabled
30
NE34
1-SHXA2-1
Enabled
30
NE35
1-SHXA2-1
Enabled
30
NE36
1-SHXA2-1
Enabled
30
----End

Procedure
Issue 02 (2012-12-30)
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21

289

CVLAN
MPLS EXP
IP DSCP
PHB
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7

CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Step 2 Modify the ports in the DS domain and their trusted packet types. For details, see A.7.6.2
Changing the Packet Type Trusted by a Port.
Parameter
Packet Type
GE1
ip-dscp
GE2
IF
Issue 02 (2012-12-30)

290

Parameter
Packet Type
GE2
ip-dscp
IF
NOTE
Step 3 Set scheduling policies for egress queues. For details, see A.7.6.4 Setting Egress Queue
Scheduling Policies.
This table provides parameter values for microwave ports on NE31 to NE36.
Parameter
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Parameter
Issue 02 (2012-12-30)
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64(Green)
42 (Green)
100
AF4
Tail drop

291

Parameter
AF3
AF2
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
WRED
64(Green)
42 (Green)
100
42 (Red)
21 (Red)
64(Green)
42 (Green)
42 (Red)
21 (Red)
WRED
100
AF1
Tail drop
BE
WRED
64(Green)
42 (Green)
100
----End

Procedure
Step 1 Create maintenance domains (MDs). For details, see A.7.7.1 Creating an MD.
This table provides parameter values for creating MDs.
Parameter
Value
NE33
NE35
NE36
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 Create a maintenance association (MA). For details, see A.7.7.2 Creating an MA.
This table provides parameter values for creating MAs.
Parameter
Issue 02 (2012-12-30)
Value
NE33
NE35
NE36
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
Dlan
Dlan
Dlan
Relevant Service
1-Dlan
1-Dlan
1-Dlan

292

Parameter
Value
CC Test Transmit
Period
NE33
NE35
NE36
1s
1s
1s
MEP.
This table provides parameter values for creating MEPs
Parameter
Value
NE33
NE35
NE36
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
Dlan
Dlan
Dlan
Board
1-SHXA2
1-SHXA2
1-SHXA2
Port
GE1
GE1
GE1
VLAN
MP ID
103
105
106
Direction
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
l This table provides parameter values for creating remote MEPs for NE35.
Parameter
Value
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
Dlan
Dlan
MP ID
103
106
l This table provides parameter values for creating a remote MEP for NE33.
Issue 02 (2012-12-30)
Parameter
Value
EdgeNE
Dlan

293

Parameter
Value
MP ID
105
l This table provides parameter values for creating a remote MEP for NE36.
Parameter
Value
EdgeNE
Dlan
MP ID
105
----End

Procedure
Step 1 Create optical fibers manually. For details, see A.3.4.1 Creating a Fiber/Cable by Using the
Search Method.
This table provides parameter values for creating optical fibers manually.
Parameter
Issue 02 (2012-12-30)
Value
GE Optical Fiber
between NE31 and
NE36
GE Optical Fiber
between NE32 and
NE33
GE Optical Fiber
between NE34 and
NE35
Fiber/Cable Type
Fiber
Fiber
Fiber
Source NE
NE31
NE32
NE34
Source Board
GE2
GE2
GE2
Source Port
Sink NE
NE36
NE33
NE35
Sink Board
GE2
GE2
GE2

294

Parameter
Value
GE Optical Fiber
between NE31 and
NE36
GE Optical Fiber
between NE32 and
NE33
GE Optical Fiber
between NE34 and
NE35
Sink Port
Automatically
Allocate IP Address
No
No
No
NOTE
This example is based on the hypothesis that the microwave links have been created during microwave link
configuration.
Step 2 Create Ethernet local area network (E-LAN) services transmitted in Native Ethernet mode. For
details, see A.10.4 Creating an IEEE 802.1D Bridge-based E-LAN Service.
1.
Choose ServiceNative Ethernet ServiceCreate E-LAN Service from the Main Menu.
2.
Set the general attributes for E-LAN services.
3.
Configure bridge-mounted ports for E-LAN services.

a.
Double-click NE35 in the Physical Topology tab page.
b.
Set Tag Type to Tag-Transparent.
c.
Under Available Interface, select GE1, GE2, and IF, and click
d.
Click OK.
4.
Repeat Step 2.3 to configure bridge-mounted ports on NE32, NE33, NE34, and NE36 based
on 8.7.7.4 Service Planning (Ethernet Services).
5.
Set the general attributes for the bridge-mounted ports.

a.
Click
b.
Click the Interface Information tab.
c.
NE
Interface
Enable Port
Working Mode
Max Frame
Length (byte)
NE31
GE2
Enabled
Auto-Negotiation
9600
Issue 02 (2012-12-30)

295

NE
NE32
NE33
NE34
NE35
NE36
Interface
Enable Port
Working Mode
Max Frame
Length (byte)
IF
GE2
Enabled
Auto-Negotiation
9600
IF
GE1
Enabled
Auto-Negotiation
9600
GE2
Enabled
Auto-Negotiation
9600
IF
GE2
Enabled
Auto-Negotiation
9600
IF
GE1
Enabled
Auto-Negotiation
9600
GE2
Enabled
Auto-Negotiation
9600
IF
GE1
Enabled
Auto-Negotiation
9600
GE2
Enabled
Auto-Negotiation
9600
IF
6.
Set the advanced attributes for the bridge-mounted ports.

a.
Click
b.
c.
Select the desired bridge-mounted ports.
d.
Click
e.
Click the Advanced Attributes tab and set the advanced attributes for the ports.
NE
Port
Loopback Check
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
NE31
GE2
Enabled
Enabled
30
IF
Enabled
Enabled
30
GE2
Enabled
Enabled
30
IF
Enabled
Enabled
30
GE1
Enabled
Enabled
30
GE2
Enabled
Enabled
30
NE32
NE33
Issue 02 (2012-12-30)

296

NE
NE34
NE35
NE36
Port
Loopback Check
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
IF
Enabled
Enabled
30
GE2
Enabled
Enabled
30
IF
Enabled
Enabled
30
GE1
Enabled
Enabled
30
GE2
Enabled
Enabled
30
IF
Enabled
Enabled
30
GE1
Enabled
Enabled
30
GE2
Enabled
Enabled
30
IF
Enabled
Enabled
30
7.
Configure Ethernet Ring Protection Switching (ERPS).

a.
Click
b.
Click the ERPS tab. Then, click Add.
c.
Set the parameters for the ERPS protection instance.
d.
Click OK.
e.
Set the parameters for the ERPS protocol.
8.
9.
Click Configure. In the Configure Ethernet OAM dialog box, configure Ethernet
operation, administration and maintenance (ETH OAM) port information.
Issue 02 (2012-12-30)

297

10. Click OK.

----End

Procedure
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Issue 02 (2012-12-30)
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13

298

CVLAN
MPLS EXP
IP DSCP
PHB
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Step 2 Modify the ports in the DS domain and their trusted packet types. For details, see A.7.6.2
Changing the Packet Type Trusted by a Port.
Parameter
Packet Type
GE1
ip-dscp
GE2
IF
Parameter
Packet Type
GE2
ip-dscp
IF
NOTE
Issue 02 (2012-12-30)
Parameter
CS7
SP
299

Parameter
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Parameter
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64(Green)
42 (Green)
100
AF4
Tail drop
AF3
WRED
64(Green)
42 (Green)
100
42 (Red)
21 (Red)
64(Green)
42 (Green)
42 (Red)
21 (Red)
AF2
WRED
100
AF1
Tail drop
BE
WRED
64(Green)
42 (Green)
100
----End
8.7.7.13 End-to-End Configuration Procedure (Verifying Ethernet Service

Configurations)
Issue 02 (2012-12-30)

300

Procedure
menu.
the shortcut menu.
NOTE
for an LB test.
Step 6 Click Run.

Issue 02 (2012-12-30)

301

----End
8.7.8 Configuration Example (IEEE 802.1Q Bridge-based E-LAN

Service)
This section provides an example of how to configure IEEE 802.1Q bridge-based Ethernet local
area network (E-LAN) services according to the network plan.

Network), configure Ethernet services according to the following requirements:
l
Each of NodeB 1, NodeB 2, and NodeB 3 provides a 1000 Mbit/s GE port in autonegotiation mode.
NodeB 1 belongs to area 1; NodeB 2 and NodeB 3 belong to area 2. The base stations in
an area have the same VLAN ID and data from different areas is isolated from each other
by using VLAN IDs.
NodeB 1, NodeB 2, and NodeB 3 use DSCP flags to identify the priorities of Ethernet
services.
The network must provide the service loop detection function and the broadcast packet
suppression function.
To meet the preceding requirements, IEEE 802.1Q bridge-based Ethernet local area network (ELAN) services are configured for service transmission on each NE. In addition, the following
functions are configured for the services: service loop test, broadcast packet suppression, and
quality of service (QoS) processing.
Issue 02 (2012-12-30)

302

Figure 8-52 Networking diagram (IEEE 802.1Q bridge-based E-LAN services)

NMS
LAN switch
NE11
P&E
NodeB 1
VALN 100
NE13
V-polarization
NE99_1
P&E
GE
COMBO
GE
COMBO
COMBO
COMBO
GE
P&E
Local backhaul
network
Domain 1
GE
NE12
H-polarization
RNC
NE14
P&E
GE
P&E
GE
P&E
NE21
NE22
NodeB 2
VLAN 200
NE24
NE99_2
NE23
Domain 2
NodeB 3
VLAN 200
OptiX RTN 900
Microwave link
Ethernet link
XPIC cable
NOTE
(GE1).

ports.

Table 8-96 and Table 8-97 provide the information about the Ethernet ports that transmit/receive
Ethernet services.
Issue 02 (2012-12-30)

303

Table 8-96 Information about Ethernet ports on XPIC links

Parame
ter
NE11
NE12
NE13
NE14
1SHXA2
-2(GE1)
1SHXA2
-3(GE2)
1SHXA2
-3(GE2)
1SHXA2
-2(GE1)
1SHXA2
-3(GE2)
1SHXA2
-2(GE1)
1SHXA2
-3(GE2)
Encapsul
ation
Type
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q
Working
Mode
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
AutoNegotiat
ion
Flow
Control
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Tag
Type
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Tag
Aware
Broadca
st Packet
Suppress
ion
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Broadca
st Packet
Suppress
ion
Threshol
d
30
30
30
30
30
30
30
Table 8-97 Information about Ethernet ports on non-XPIC links

Parameter
Issue 02 (2012-12-30)
NE21
NE22
NE23
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
Encapsulatio
n Type
802.1Q
802.1Q
802.1Q
802.1Q
802.1Q
Working
Mode
AutoNegotiation
AutoNegotiation
AutoNegotiation
AutoNegotiation
AutoNegotiation
Flow Control
Disabled
Disabled
Disabled
Disabled
Disabled
Tag Type
Tag Aware
Tag Aware
Tag Aware
Tag Aware
Tag Aware
Broadcast
Packet
Suppression
Enabled
Enabled
Enabled
Enabled
Enabled

NE24
304

Parameter
Broadcast
Packet
Suppression
Threshold
NE21
NE22
NE23
NE24
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
1-SHXA2-3
(GE2)
1-SHXA2-2
(GE1)
30
30
30
30
30
NOTE
of each NE that receives services must work in auto-negotiation mode. 1-SHXA2-1(IF) the peer Ethernet
l In this example, all the services carry VLAN IDs. Therefore, the TAG attributes of all the ports are Tag
Aware.

Table 8-98 and Table 8-99 provide the information about the microwave ports that transmit/
receive services.
Table 8-98 Information about microwave ports on XPIC links
Parameter
Issue 02 (2012-12-30)
NE11
NE12
NE13
NE14
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
Encapsulation
Type
802.1Q
802.1Q
802.1Q
802.1Q
Tag Type
Tag Aware
Tag Aware
Tag Aware
Tag Aware
Broadcast
Packet
Suppression
Enabled
Enabled
Enabled
Enabled
Broadcast
Packet
Suppression
Threshold
30
30
30
30

305

Table 8-99 Information about microwave ports on non-XPIC links

Parameter
NE21
NE22
NE23
NE24
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
1-SHXA2-1
(IF)
Encapsulation
Type
802.1Q
802.1Q
802.1Q
802.1Q
Tag Type
Tag Aware
Tag Aware
Tag Aware
Tag Aware
Broadcast
Packet
Suppression
Enabled
Enabled
Enabled
Enabled
Broadcast
Packet
Suppression
Threshold
30
30
30
30

In this example, it is assumed that PLA has been configured during microwave link
configuration. Therefore, Ethernet protection is not required.

Table 8-100 and Table 8-101 provide the service planning information.
Table 8-100 Information about IEEE 802.1Q bridge-based E-LAN services on XPIC links
Issue 02 (2012-12-30)
Parameter
NE11
NE13
NE14
Service ID
Auto Assigned
Auto Assigned
Auto Assigned
Service Name
Qlan
Qlan
Qlan
Tag Type
C-Aware
C-Aware
C-Aware
MAC Address
Learning
Enabled
Enabled
Enabled
MAC Address
Learning Mode
IVL
IVL
IVL
L2 Protocol Control
Not Transparent
Not Transparent
Not Transparent

306

Parameter
NE11
NE13
NE14
Mounted UNI port
1-SHXA2-1(IF)
(VLAN ID: 100)
1-SHXA2-1(IF)
(VLAN ID: 100)
1-SHXA2-1(IF)
(VLAN ID: 100)
1-SHXA2-2(GE1)
(VLAN ID: 100)
1-SHXA2-2(GE1)
(VLAN ID: 100)
1-SHXA2-2(GE1)
(VLAN ID: 100)
Table 8-101 Information about IEEE 802.1Q bridge-based E-LAN services on non-XPIC links
Parameter
NE21
NE22
NE23
NE24
Service ID
Auto Assigned
Auto Assigned
Auto Assigned
Auto Assigned
Service Name
Qlan
Qlan
Qlan
Qlan
Tag Type
C-Aware
C-Aware
C-Aware
C-Aware
MAC Address
Learning
Enabled
Enabled
Enabled
Enabled
MAC Address
Learning Mode
IVL
IVL
IVL
IVL
L2 Protocol
Control
Not Transparent
Not Transparent
Not Transparent
Not Transparent
Mounted UNI
port
1-SHXA2-1(IF)
(VLAN ID:
200)
1-SHXA2-1(IF)
(VLAN ID:
200)
1-SHXA2-1(IF)
(VLAN ID:
200)
1-SHXA2-1(IF)
(VLAN ID:
200)
1-SHXA2-2
(GE1) (VLAN
ID: 200)
1-SHXA2-3
(GE2) (VLAN
ID: 200)
1-SHXA2-2
(GE1) (VLAN
ID: 200)
1-SHXA2-2
(GE1) (VLAN
ID: 200)
1-SHXA2-3
(GE2) (VLAN
ID: 200)
NOTE
In this example, the split horizon group is not used.

Diffserv
Issue 02 (2012-12-30)

307

PHB
DSCP
Service Type
CS7
56
CS6
48
EF
40

signaling
AF41
36
AF43
32
AF31
28

and HSPA streaming
services)
AF33
24
HSDPA service (HSPA
streaming service)
AF21
20
and R99 background
services)
AF23
16
and R99 background
services)
AF11
12
AF13
BE

services)
NOTE
Issue 02 (2012-12-30)

308


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

PHB
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64 (green)
42 (green)
100
AF4
Tail drop
AF3
WRED
64 (green)
42 (green)
100
42 (red)
21 (red)
64 (green)
42 (green)
42 (red)
21 (red)
AF2
Issue 02 (2012-12-30)
WRED
100
AF1
Tail drop
BE
WRED
64 (green)
42 (green)
100

309


Port Shaping


Procedure
Step 2 Create IEEE 802.1Q bridge-based E-LAN services. For details, see A.7.3.6 Creating an IEEE
802.1Q Bridge-based E-LAN Service.
Parameters of NE11, NE13 and NE14
This table provides parameter values for mounted ports.
Port
1-SHXA2-2
1-SHXA2-1
Issue 02 (2012-12-30)
Parameter
Value
Service ID
Service Name
Qlan
Direction
C-Aware
L2 Protocol Control
Not Transparent
Enabled

310


Parameter
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
100
100
Working Mode
Auto-Negotiation
Encapsulation Type
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
l Non-XPIC links
Parameters of NE21 and NE24
Port
1-SHXA2-2
1-SHXA2-1

Parameter
Value
Service ID
Service Name
Qlan
Direction
C-Aware
L2 Protocol Control
Not Transparent
Enabled
Issue 02 (2012-12-30)
Parameter
1-SHXA2-2
1-SHXA2-1
Port Enable
Enabled
200
200
Working Mode
Auto-Negotiation
Encapsulation Type
802.1Q
802.1Q

311

Parameter
1-SHXA2-2
1-SHXA2-1
Tag
Tag Aware
Tag Aware
Parameters of NE22
Port
1-SHXA2-3
1-SHXA2-1

Parameter
Value
Service ID
Service Name
Qlan
Direction
C-Aware
L2 Protocol Control
Not Transparent
Enabled

Parameter
1-SHXA2-3
1-SHXA2-1
Port Enable
Enabled
200
200
Working Mode
Auto-Negotiation
Encapsulation Type
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
Parameters of NE23
Port
1-SHXA2-2
1-SHXA2-3
1-SHXA2-1
Issue 02 (2012-12-30)

312


Parameter
Value
Service ID
Service Name
Qlan
Direction
C-Aware
L2 Protocol
Control
Not Transparent
MAC Address
Learning
Enabled

Parameter
1-SHXA2-2
1-SHXA2-3
1-SHXA2-1
Port Enable
Enabled
Enabled
VLAN ID (e.g.
1,3-5)
200
200
200
Working Mode
Auto-Negotiation
Auto-Negotiation
Encapsulation
Type
802.1Q
802.1Q
802.1Q
Tag
Tag Aware
Tag Aware
Tag Aware
----End

This section describes the procedure for configuring Ethernet ports and microwave ports.
Procedure
Step 1 Configure the advanced attributes of Ethernet ports. For details, see A.6.1.4 Setting the
Advanced Attributes for an Ethernet Port.
This table provides parameter values for Ethernet ports.
Parameter
NE11
Issue 02 (2012-12-30)
1-SHXA2-2
Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
Enabled
Enabled
30

313

Parameter
NE13
Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
1-SHXA2-3
Enabled
Enabled
30
1-SHXA2-2
Enabled
Enabled
30
1-SHXA2-3
Enabled
Enabled
30
Loopback
Check
Broadcast
Packet
Suppression
Broadcast
Packet
Suppression
Threshold
l Non-XPIC links
Parameter
NE21
1-SHXA2-2
Enabled
Enabled
30
NE22
1-SHXA2-3
Enabled
Enabled
30
NE23
1-SHXA2-2
Enabled
Enabled
30
1-SHXA2-3
Enabled
Enabled
30
1-SHXA2-2
Enabled
Enabled
30
NE24
This table provides parameter values for microwave ports.

l XPIC links
Parameter
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
NE11
1-SHXA2-1
Enabled
30
NE13
1-SHXA2-1
Enabled
30
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
l Non-XPIC links
Parameter
Issue 02 (2012-12-30)
NE21
1-SHXA2-1
Enabled
30
NE22
1-SHXA2-1
Enabled
30
NE23
1-SHXA2-1
Enabled
30
NE24
1-SHXA2-1
Enabled
30

314

----End

Procedure
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Issue 02 (2012-12-30)
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31

315

CVLAN
MPLS EXP
IP DSCP
PHB
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Step 2 Modify the ports and their trusted packet types. For details, see A.7.6.2 Changing the Packet
Type Trusted by a Port.
Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-3
1-SHXA2-1

Parameter
Packet Type
1-SHXA2-3
ip-dscp
1-SHXA2-1

Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-1
NOTE
Issue 02 (2012-12-30)

316

Parameter
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Parameter
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64(Green)
42 (Green)
100
AF4
Tail drop
AF3
WRED
64(Green)
42 (Green)
100
42 (Red)
21 (Red)
64(Green)
42 (Green)
42 (Red)
21 (Red)
AF2
WRED
100
AF1
Tail drop
BE
WRED
64(Green)
42 (Green)
100
----End

Issue 02 (2012-12-30)

317

Procedure
Step 1 Create maintenance domains (MDs) for NE11, NE13, NE21, NE23, and NE24. For details, see
A.7.7.1 Creating an MD.
This table provides parameter values for creating maintenance domains (MDs) for NE11, NE13,
NE21, NE23, and NE24.
Parameter
Value
NE11
NE13
NE21
NE23
NE24
Maintenanc
e Domain
Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenanc
e Domain
Level
Step 2 Create maintenance associations (MAs) for NE11, NE13, NE21, NE23, and NE24. For details,
see A.7.7.2 Creating an MA.
l This table provides parameter values for creating MAs for NE11 and NE13.
Parameter
Value
NE11
NE13
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
NodeB1_Qlan
NodeB1_Qlan
Relevant Service
1-Qlan
1-Qlan
1s
1s
l This table provides parameter values for creating MAs for NE21, NE23, and NE24.
Parameter
Issue 02 (2012-12-30)
Value
NE21
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
NodeB2_Qlan
NodeB3_Qlan
NodeB2_Qlan
NodeB3_Qlan
Relevant
Service
1-Qlan
1-Qlan
1-Qlan
1-Qlan

318

Parameter
CC Test
Transmit
Period
Value
NE21
NE23
NE24
1s
1s
1s
1s
MEP.
l This table provides parameter values for creating MEPs for NE11 and NE13.
Parameter
Value
NE11
NE13
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
NodeB1_Qlan
NodeB1_Qlan
Board
1-SHXA2
1-SHXA2
Port
1-SHXA2-2
1-SHXA2-2
VLAN
100
100
MP ID
101
102
Direction
Ingress
Ingress
CC Status
Active
Active
l This table provides parameter values for creating MEPs for NE21, NE23, and NE24.
Parameter
Issue 02 (2012-12-30)
Value
NE21
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
NodeB2_Qlan
NodeB3_Qlan
NodeB2_Qlan
NodeB3_Qlan
Board
1-SHXA2
1-SHXA2
1-SHXA2
1-SHXA2
Port
1-SHXA2-2
1-SHXA2-2
1-SHXA2-2
1-SHXA2-2
VLAN
200
200
200
200
MP ID
201
202
202
204
Direction
Ingress
Ingress
Ingress
Ingress

319

Parameter
CC Status
Value
NE21
NE23
NE24
Active
Active
Active
Active
l This table provides parameter values for creating remote MEPs for NE11 and NE13.
Parameter
Value
NE11
NE13
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
NodeB1_Qlan
NodeB1_Qlan
MP ID
102
101
l This table provides parameter values for creating remote MEPs for NE21, NE23, and NE24.
Parameter
Value
NE21
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
NodeB2_Qlan
NodeB3_Qlan
NodeB2_Qlan
NodeB3_Qlan
MP ID
202
204
201
202
----End
8.7.8.11 End-to-End Configuration Procedure (Ethernet Protection)

Issue 02 (2012-12-30)

320


Context
NOTE
It is recommended that you configure microwave links for which the cross polarization interference cancellation
(XPIC) function is enabled on a per NE basis, because Ethernet services on the links are transparently transmitted
using Layer 2 protocols. This configuration example is for configuring Ethernet services on non-XPIC links.
Procedure
Step 2 Create E-LAN services transmitted in Native Ethernet mode.
1.
Choose ServiceNative Ethernet ServiceCreate E-LAN Service from the Main Menu.
2.
Set the general attributes for E-LAN services.
3.
Configure bridge-mounted ports for E-LAN services.

a.
Double-click NE24 in the Physical Topology tab page.
b.
Set Tag Type to C-Aware.
c.
Under Available Interface, select GE1 and IF, and click
d.
Under Selected Interface, set C-VLAN and Encapsulation Type based on 8.7.8.4
Service Planning (Ethernet Services).
e.
Click OK.
4.
Repeat Step 2.3 to configure bridge-mounted ports on NE21, NE22 and NE23 based on
8.7.8.4 Service Planning (Ethernet Services).
5.
Issue 02 (2012-12-30)
a.
Click
b.
c.

321

NE
Interface
Enable Port
Working Mode
Max Frame
Length (byte)
NE21
GE1
Enabled
Auto-Negotiation
9600
IF
GE1
Enabled
Auto-Negotiation
9600
GE2
Enabled
Auto-Negotiation
9600
IF
GE2
Enabled
Auto-Negotiation
9600
IF
GE1
Enabled
Auto-Negotiation
9600
IF
NE22
NE23
NE24
6.
Set the advanced attributes for the bridge-mounted ports.

a.
Click
b.
c.
Select the desired bridge-mounted ports.
d.
Click
e.
Click the Advanced Attributes tab and set the advanced attributes for the ports.
NE
Port
Loopback Check
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
NE21
GE1
Enabled
Enabled
30
IF
Enabled
Enabled
30
GE1
Enabled
Enabled
30
GE2
Enabled
Enabled
30
IF
Enabled
Enabled
30
GE2
Enabled
Enabled
30
IF
Enabled
Enabled
30
GE1
Enabled
Enabled
30
IF
Enabled
Enabled
30
NE22
NE23
NE24
7.
Issue 02 (2012-12-30)

322

8.
Click Configure. In the Configure Ethernet OAM dialog box, configure Ethernet
operation, administration and maintenance (ETH OAM) port information.
9.
Click OK.
----End

Procedure
Issue 02 (2012-12-30)
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6

323

CVLAN
MPLS EXP
IP DSCP
PHB
56
CS7

CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
Step 2 Modify the ports and their trusted packet types. For details, see A.7.6.2 Changing the Packet
Type Trusted by a Port.
Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-3
1-SHXA2-1

Parameter
Packet Type
1-SHXA2-3
ip-dscp
1-SHXA2-1
Issue 02 (2012-12-30)

324


Parameter
Packet Type
1-SHXA2-2
ip-dscp
1-SHXA2-1
NOTE
Parameter
CS7
SP
CS6
SP
EF
SP
AF4
SP
AF3
SP
AF2
SP
AF1
SP
BE
SP
Parameter
Issue 02 (2012-12-30)
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
CS7
Tail drop
CS6
Tail drop
EF
WRED
64(Green)
42 (Green)
100
AF4
Tail drop

325

Parameter
AF3
AF2
Congestion
Management
Mode
WRED Configuration
Upper
Threshold
(bytes)
Lower
Threshold
(bytes)
Discard Ratio
(%)
WRED
64(Green)
42 (Green)
100
42 (Red)
21 (Red)
64(Green)
42 (Green)
42 (Red)
21 (Red)
WRED
100
AF1
Tail drop
BE
WRED
64(Green)
42 (Green)
100
----End
8.7.8.14 End-to-End Configuration Procedure (Verifying Ethernet Service

Configurations)
Procedure
menu.
the shortcut menu.
NOTE
for an LB test.
Issue 02 (2012-12-30)

326

Step 6 Click Run.

----End

To ensure that clocks of all the nodes on the transmission network are synchronized, configure
the clocks for these nodes according to a unified clock synchronization policy.

Before configuring clocks, familiarize yourself with the basic concepts.
8.8.1.1 Clock Source

A clock source is used to synchronize the components of an NE or upstream and downstream
NEs, and to provide stable and accurate operating frequency for the functional modules and
chips of an NE. With the clock source, services can be transmitted correctly and in strict order.
Issue 02 (2012-12-30)

327

OptiX RTN 310 supports the following clock sources:

l
Radio clock source: a clock source that is extracted from a received radio signal stream.
Ethernet clock source: a clock source that is extracted from a received synchronous Ethernet
signal stream.
Internal clock source: a clock source that is generated through the free-run oscillation of
an NE built-in clock. The internal clock source has the lowest priority.
8.8.1.2 Clock Protection Modes

The OptiX RTN 310 supports clock source protection based on priorities, synchronization status
message (SSM) protection, and extended SSM protection.
Clock Source Protection Based on Priorities

Clock source protection is provided based on the priorities specified in the clock source priority
list. When a higher priority clock source fails, a lower priority clock source is used. Only clock
sources added to the clock source priority list can be selected. The internal clock source is the
clock source with the lowest priority.
As shown in Figure 8-53, a link aggregation group (LAG) protects the services between NE11
and the RNC. NE11 traces the clock of the RNC through synchronous Ethernet. Ports GE1 and
GE2 on NE11 need to be added to the clock source priority list so that NE1 can obtain reference
clock from GE2 when GE1 fails.
Figure 8-53 Clock source protection based on priorities
NE11
GE1
GE2
Internal
NE21
Radio
Internal
RNC
GE1
Radio link
Cable
GE2
Clock synchronization
Radio link
NE NAME
Clock priority 1
Clock priority 2
Internal clock
SSM Protection
SSM protection enhances clock source protection based on priorities and triggers clock switching
based on the clock source quality level. Table 8-105 provides details on SSM protection.
Issue 02 (2012-12-30)

328

Table 8-105 SSM protection

Item
Description
Definition
SSM protection refers to the clock protection in compliance with the SSM
protocol specified in ITU-T G.781. The SSM protocol defines the levels and
states of clock signals.
Channel
The OptiX RTN 310 supports SSM protection on Ethernet links and radio
links.
l On radio links, SSM messages are transmitted through specific overhead
bytes.
l On GE ports, SSM messages are transmitted through specific protocol
control packets.
Function
SSM messages can be identified for:

l Selecting the high-quality clock source as the reference clock
l Preventing a timing loop between two clock devices
Handling
process
Once SSM protection is enabled on an NE, automatic protection switching

of clock sources conforms to the following rules:
l According to the clock source priority list, the NE selects the clock source
of the best quality as the synchronization source.
l If multiple clock sources have the best quality, the NE selects the one of
the highest priority as the synchronization source.
l The NE broadcasts the quality information of the synchronization clock
source to its downstream NE, and also notifies its upstream NE that its
own clock source cannot be used for synchronization.
Application
scenario
The SSM protocol can be applied to a ring network with one external
reference source or a chain network with two external reference sources.
When the SSM protocol is applied to a ring network, the node where the
reference clock is injected cannot select any clock sources on the ring. The
other nodes can select the east or west clock source on the ring.
Figure 8-54 is a microwave ring where the SSM protection is enabled.

When the network operates normally, the NEs on the ring select the clock source as follows:
1.
NE11 selects the external clock source as the synchronous source and sends the clock
quality message "G.812" to NE12 and NE13.
2.
NE12, NE13, NE21, NE22, NE31, and NE32 select the upstream clock source from their
own clock source priority lists.
3.
In addition, each NE sends a Don't Use for Sync. (DUS) message to the upstream direction.
4.
Although NE22 and NE31 detect usable clock sources from the radio link, they decide not
to switch clock sources because the priorities of the protection clock sources are the same
as the working clock sources.
When the microwave links between NE12 and NE21 become faulty, the NEs on the ring select
the clock source as follows:
Issue 02 (2012-12-30)

329

1.
NE12, NE13, NE32, and NE31 use the current clock sources.
2.
NE21 loses the west clock source and finds the DUS message in the east direction.
Therefore, NE21 selects the internal clock and sends a G.812 clock quality message to the
downstream.
3.
NE22 finds that the west clock source is the internal clock, inferior to the east clock source
of G.812. Therefore, NE22 selects the east clock source. In addition, NE22 sends a DUS
message to the east link and sends a G.812 clock quality message to the west link.
4.
NE21 receives the G.812 clock quality message from NE22, selects the east clock source,
and sends a DUS message to the east link, after which clock switching is completed on the
ring.
NOTE
SSM protection does not provide a complete solution to the timing loop. Do not configure the clock sources that
may form a loop. For example, you should not add the west and east clock sources to the clock source priority
list on NE11.
Figure 8-54 SSM protection

NE11
Radio link
Internal
NE13
E: GE
W: Radio
Internal
NE12
W: GE
E: Radio
Internal
E
W
NE22
W: GE
E: Radio
Internal
NE32
E: Radio
W: GE
Internal
E
E
Cable
Issue 02 (2012-12-30)
W
E
NE21
W: Radio
E: GE
Internal
BITS
Radio Network
Radio link
E
East
NE31
E: GE
W: Radio
Internal
NE NAME
Clock priority 1
Clock priority 2
Internal clock
West

330

Extended SSM Protection

Extended SSM protection uses clock source markers to perform SSM protection. Table 8-106
provides details on extended SSM protection.
Table 8-106 Extended SSM protection
Item
Description
Definition
Extended SSM protection refers to clock protection in compliance with

Huawei-defined extended SSM protocol that introduces clock IDs into the
SSM protocol. Clock IDs are transmitted with SSM messages and are used
in automatic clock switching.
The clock ID takes a value from 0 to 15. 0 being the default value indicates
an invalid clock ID. After the extended SSM protocol is enabled, the NE
does not select clock source 0 as the current clock source.
Channel
Extended SSM protection is always applied with SSM protection. The OptiX
RTN 310 supports extended SSM protection and SSM protection on Ethernet
and microwave links.
l On microwave links, SSM messages and extended SSM messages are
transmitted through specific overhead bytes.
l On GE ports, SSM messages and extended SSM messages are
transmitted through specific protocol control packets.
Function
Extended SSM messages prevent timing loops because clock devices can
determine whether clock references come from their own input.
Handling
process
After extended SSM protection is enabled on an NE, automatic clock

switching conforms to the following rules:
l According to the clock source priority list, the NE selects the clock source
of the best quality as its synchronization source.
l If the clock ID of a certain clock source indicates that the clock source
is from the NE itself, that source is not processed.
l If multiple clock sources are of equally high quality, the NE selects the
one of the highest priority as the synchronization source.
l The NE broadcasts the quality information and the clock ID of the
synchronization clock source to its downstream NE, and also notifies its
upstream NE that its own clock source cannot be used for
synchronization.
Issue 02 (2012-12-30)

331

Item
Description
Application
scenario
Extended SSM protocol applies to complex clock synchronization networks,

such as networks with multiple clock references, tangent rings, intersecting
rings, and mesh networks.
Clock IDs are allocated as follows:
l When extended SSM is used, the clock ID of an external clock source
cannot be automatically extracted and needs to be allocated.
l At all the nodes that access external clock sources, the internal clock
sources should have a clock ID.
l At any node intersecting a ring or chain with a ring, the internal clock
sources should have a clock ID.
l At any node intersecting a ring or chain with a ring, clock sources that
are accessed within the ring should have a clock ID.
l Clock sources other than the preceding types should always have their
clock ID set to the default value 0.
l Clock IDs are used for timing reference only. They do not indicate any
priority difference.
Figure 8-55 is a microwave ring with extended SSM protection enabled.

On the ring, the following clock sources require a clock ID:
l
P&E interface clock on NE11
P&E interface clock on NE42
Internal clock source on NE11
Internal clock source on NE42
Issue 02 (2012-12-30)

332

Figure 8-55 Extended SSM protection

Master BITS
NE12
W: GE
E: Radio
Internal
P&E
E
NE21
W: Radio
E: GE
Internal
NE11
P&E
W: Radio 1
E: GE
Internal
NE32
E: Radio
W: GE
Internal
E
E
W
E
NE22
W: GE
E: Radio
Internal
NE31
E: GE
W: Radio
Internal
E
E
W
NE41
W: Radio
E: GE
Internal
EW
P&E
NE42
W: GE
E: Radio
P&E
Internal
Slave BITS
Cabel/fiber
W
Radio link
E
East
west
NE NAME
Clock priority 1
Clock priority 2
Internal clock
NOTE
l The extended SSM protection provides a complete solution to the timing loop. Therefore, when you
configure clock sources, the clocks can form a loop.
l The extended SSM protection is advantageous in the complex networking of clock protection, for example,
the dual external clocks. Hence, the extended SSM protection is used in only a few cases.
8.8.1.3 Clock Synchronization Policy

Plan an appropriate clock synchronization policy based on the network topology.
Issue 02 (2012-12-30)

333

Clock Synchronization Policy for a Chain Network

For a chain network consisting of microwave links, plan the clock synchronization policy
according to the following principles:
l
If an Ethernet clock source is input into the master (source) node, configure this clock
source for this node.
For the other nodes, configure the clock sources from their upper-level microwave links.
If a node has multiple upper-level microwave links (for example, the upper-level
microwave links use the XPIC configuration), configure one radio clock source for each
microwave link and allocate priorities to these radio clock sources based on the microwave
link status.
Do not configure synchronization status message (SSM) or extended SSM protection.
Figure 8-56 shows the clock synchronization policy for a chain network.
l
An Ethernet clock source is input into the master node NE1. The clock source priorities for
NE1 in descending order are: GE1 (the Ethernet clock source) > internal clock source.
NE2 is the downstream NE of NE1. Therefore, the clock source priorities for NE2 in
descending order are: IF > internal clock source.
NE3 and NE2 are cascaded. Therefore, the clock source priorities for NE3 in descending
order are: GE2 > internal clock source.
NE4 is the downstream NE of NE3. Therefore, the clock source priorities for NE4 in
descending order are: IF > internal clock source.
Do not configure SSM or extended SSM protection.
Figure 8-56 Clock synchronization policy for a chain network
GE
NE4
BITS
NE1
GE1/
Internal
Clock
Issue 02 (2012-12-30)
NE2
IF/
Internal
Microwave link

NE3
GE2/
Internal
IF/
Internal
Ethernet link
334

NOTE
l For a microwave link not configured with 1+1 or PLA protection, Clock Control Mode is fixed to
Standalone at both ends of the link.
l For a microwave link configured with 1+1 protection, Clock Control Mode is fixed to Centralized
at both ends of the link. In this case, the standby NE traces the clock information received from the
main NE through the COMBO port.
l For a microwave link configured with PLA protection, it is recommended that you set Clock Control
Mode to Standalone and enable the SSM protocol to implement clock protection.
Clock Synchronization Policy for a Ring Network

For a ring network consisting of microwave links, plan the clock synchronization policy
according to the following principles:
Divide the ring into two chains and configure the clock synchronization policy separately on
each chain.
Figure 8-57 shows the clock synchronization policy for a ring network.
l
Enable the SSM function for all nodes on the ring.
An Ethernet clock source is input into the master node NE1. The clock source priorities for
NE1 in descending order are: GE1 (the Ethernet clock source) > internal clock source.
NE2 traces the clock of NE1. Therefore, the clock source priorities for NE2 in descending
order are: IF > GE2 > internal clock source.
order are: GE2 > IF > internal clock source.
order are: IF > GE2 > internal clock source.
Issue 02 (2012-12-30)

335

Figure 8-57 Clock synchronization policy for a ring network
BITS
GE1/
Internal
GE2/
IF/
Internal
GE
NE1
IF/
GE2/
Internal
NE6
NE2
NE5
NE3
NE4
GE2/
IF/
Internal
GE2/
IF/
Internal
Clock
IF/
GE2/
Internal
Microwave link
Ethernet link
Precautions of Planning a Clock Synchronization Policy

Take the following precautions when planning a clock synchronization policy.
The number of NEs on a long clock chain must not be more than 20. A number less than 10 is
recommended. If a large number of NEs exist on a long clock chain, add one more clock source
for signal compensation in the middle of the chain.
Clock Synchronization Policy for Base Stations

The clock synchronization policy is as follows when a microwave transmission network
transmits clock synchronization signals to a base station.
If the base station is connected to the network through Ethernet ports, timing reference signals
are transmitted to the base station through the Ethernet ports.
If the base station is connected to the network through Ethernet ports only and does not support
the synchronous Ethernet function, you can provide timing reference signals to the base station
through an external clock port. OptiX RTN 310 does not support external clock ports.
Issue 02 (2012-12-30)

336

8.8.2 Configuration Process (Configuring a Clock)

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

source.
Configuring the clock

control mode.
Configure SSM or
extended SSM protection.
Query the clock

synchronization status.
End

Table 8-107 Process of configuring the clock
Issue 02 (2012-12-30)
Step
Operation
Remarks
A.8.1.2 Configuring Clock

Sources

Set Clock Source according to clock source
planning information.

337

Step
Operation
Remarks
Configuring the Clock

Control Mode
Required when configuring a PLA group. Set

parameters as follows:
l The clock control mode is fixed to
Standalone when you are not configuring 1
+1 or PLA protection.
l The clock control mode is fixed to
Centralized when you are configuring 1+1
protection.
l The clock control mode can be set to either
Centralized or Standalone when you are
configuring PLA.
Configu
ring the
Synchro
nization
Status
Messag
e (SSM)
or
extende
d SSM
protecti
on
A.8.1.3
Configuring
Protection for
Clock Sources
Required when the SSM or extended SSM

protection is used. Set parameters as follows:
l Set Protection Status according to the used
protocol type.
l If the clock uses the extended SSM
protection, set Clock Source ID for the
following clock sources:
Internal clock source of the NE that
connects the intersecting ring and chain or
connects the intersecting rings
Line clock source that is accessed to the
ring through the NE that connects the
intersecting ring and chain or connects the
intersecting rings and is configured with
the line clock source on the ring
The values of Clock Source ID for these
clock sources should be different.
A.8.1.5
Enabling/
Disabling SSM
Transmission
Required when the SSM or extended SSM

protection is used.
A.8.1.6
Enabling/
Disabling the
Output of
Clock Source
IDs
Required when the extended SSM protection is

used.
A.8.1.4
Customizing
the Clock
Quality
Issue 02 (2012-12-30)
When a line port is connected to the NE on the

same clock subnet, set Control Status to
Enabled. In other cases, set Control Status to
Disabled.
When a line port is connected to the NE on the

same clock subnet, set Output Clock ID to
Enabled.
Optional.

338

Step
Operation
Remarks
A.8.1.8 Querying the

Clock Synchronization
Status
Optional.
8.8.3 Configuration Example (Clock on a Microwave Chain

Network)
This section provides an example of how to configure the clock on a microwave chain network

Network), configure clocks according to the following requirements. Figure 8-59 shows the
networking diagram.
l
The microwave chain network is directly synchronized with the clock of the radio network
controller (RNC).
Clock synchronization signals are transmitted to each NodeB through a GE port.
Issue 02 (2012-12-30)

339

Figure 8-59 Networking diagram (clocks on a microwave chain network)

NMS
LAN switch
NE11
P&E
NE13
V-polarization
P&E
GE
NodeB 1
NE99_2
GE
Local backhaul
network
COMBO
COMBO
COMBO
COMBO
GE
GE
P&E
NE12
H-polarization
GE
RNC
NE14
GE
GE
GE
NE99_1
NE24
NodeB 2
NE21
NE22
GE
NE23
NodeB 3
OptiX RTN 900
Microwave link
Ethernet link
XPIC cable

This section describes the parameters required for configuring clocks on a microwave chain
network.
Clock Source Information

Based on 8.8.1.3 Clock Synchronization Policy, you can obtain the clock source information
as shown in Figure 8-60.
Issue 02 (2012-12-30)

340

Figure 8-60 Networking diagram (clocks on a microwave chain network)

NMS
LAN switch
NE11
NE13
NE99_1
V-polarization
Local backhaul
network
GE
NE12
H-polarization
RNC
NE14
GE
GE
NE99_2
NE24
NE21
NE22
GE
NE23
Master clock
OptiX RTN 900
Microwave link
Ethernet link
XPIC cable
Clock Protection
Cross polarization interference cancellation (XPIC) links on a chain network require the
Synchronization Status Message (SSM) protocol to be enabled, whereas non-XPIC links require
only clock source priority protection.

In this example, the microwave transmission network is synchronized with the radio network
controller (RNC) through GE ports, and transmits timing reference signals to the base station
through the GE ports.

This section describes the procedure for configuring clocks.
Issue 02 (2012-12-30)

341

Procedure
Step 1 Configure clock sources. For details, see A.8.1.2 Configuring Clock Sources.
This table provides parameter values for configuring clock sources.
Table 8-108 XPIC links
Parameter
Clock Source
Value
NE11
NE12
NE13
NE14
1-SHXA2-1
1-SHXA2-3
1-SHXA2-2
1-SHXA2-3
1-SHXA2-3
1-SHXA2-1
1-SHXA2-3
1-SHXA2-2
Internal Clock
Source
Internal Clock
Source
Internal Clock
Source
Internal Clock
Source
NE21
NE22
NE23
NE24
1-SHXA2-1
1-SHXA2-3
1-SHXA2-1
1-SHXA2-2
Internal Clock
Source
Internal Clock
Source
Internal Clock
Source
Internal Clock
Source
Table 8-109 Non-XPIC links

Parameter
Clock Source
Value
Step 2 Configure protection for the clock sources. For details, see A.8.1.3 Configuring Protection for
Clock Sources.
Parameter
Value
Start Standard SSM Protocol
Selected
NOTE
The other parameters take their default values.
Step 3 Query the clock synchronization status. For details, see A.8.1.8 Querying the Clock
Synchronization Status.
NE Clock Mode must be Normal Mode for all NEs.
----End
8.8.4 Configuration Example (Clock on a Microwave Ring Network)

This section provides an example of how to configure the clock on a microwave ring network
Issue 02 (2012-12-30)

342


Based on 8.6.4 Configuration Example (Microwave Links on a Microwave Ring
Network), configure clocks according to the following requirements. Figure 8-61 shows the
networking diagram.
l
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 a GE port.
Figure 8-61 Networking diagram (clocks on a microwave ring network)
NMS
NodeB 1
GE
LAN switch
GE
NE31
NE36
GE
Local backhaul
network
RNC
NE35
NE32
GE
GE
GE
NodeB 2
NE33
Microwave link
NE34
Ethernet link

This section describes the parameters required for configuring clocks on a microwave ring
network.
Clock Source Information

Based on 8.8.1.3 Clock Synchronization Policy, you can obtain the clock source information
as shown in Figure 8-62.
Issue 02 (2012-12-30)

343

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

NMS
GE2/
IF/
Internal
IF/
GE2/
Internal
LAN switch
GE
NE31
NE36
GE
IF/
GE2/
Internal
Local backhaul
network
GE1/
Internal
NE32
RNC
NE35
GE
GE2/
IF/
Internal
GE
NE33
Master clock
NE34
GE2/
IF/
Internal
Microwave link
Ethernet link
Clock Protection
The standard Synchronization Status Message (SSM) protocol is enabled for all NEs on the ring
network.

In this example, the microwave transmission network is synchronized with the radio network
controller (RNC) through GE ports, and transmits timing reference signals to the base station
through the GE ports.

This section describes the procedure for configuring clocks.
Procedure
Step 1 Configure the clock sources. For details, see A.8.1.2 Configuring Clock Sources.
This table provides parameter values for configuring clock sources.
Issue 02 (2012-12-30)

344

Paramete
r
Value
NE31
NE32
NE33
NE34
NE35
NE36
Clock
Source
1SHXA2-3
1SHXA2-1
1SHXA2-3
1SHXA2-1
1SHXA2-2
1SHXA2-1
1SHXA2-1
1SHXA2-3
1SHXA2-1
1SHXA2-3
1SHXA2-3
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Step 2 Configure protection for the clock sources. For details, see A.8.1.3 Configuring Protection for
Clock Sources.
Parameter
Value
Start Standard SSM Protocol
Selected
NOTE
The other parameters take their default values.
Step 3 Query the clock synchronization status. For details, see A.8.1.8 Querying the Clock
Synchronization Status.
NE Clock Mode must be Normal Mode for all NEs.
----End
8.9 Adding and Modifying Configuration Data

During the equipment commissioning and operating phases, you need to add or modify certain
configuration data according to the actual requirements.
8.9.1 Common Task Collection (Network Topology)

Common tasks associated with the network topology include common configuration tasks
associated with NE attributes.
Issue 02 (2012-12-30)

345

Table 8-110 Common task collection (NE attributes)

Task
Application
Scenario
Configuration
Operation
Description
Creating NEs
When using the

network management
system (NMS) to
perform centralized
management of NEs,
create the icons of the
NEs to be managed at
corresponding
positions on Main
Topology.
A.3.1.2 Creating an NE
Manually or A.3.1.1
Creating an NE by
Using the Search
Method
l Generally, NEs
are created by
searching for the
NE on the NMS.
Changing an
NE ID
You must change an

NE ID, if it does not
meet the network
planning requirements
(for example, if the NE
ID is the same as
another NE ID).
A.3.1.4 Changing an
NE ID
Changing the
IP address of an
NE
You must change the

IP address of the
gateway NE if changes
occur in the external
data communication
network (DCN)
between the NMS
server and the gateway
NE.
A.3.6.1 Setting NE
Communication
Parameters
Synchronizing
the NE time
You can configure the

NE time to be
automatically and
periodically
synchronized. You can
also manually
synchronize the NE
time if the NE time is
lost due to NE faults.
A.3.1.6 Synchronizing
the NE Time
To ensure that the NE

time is synchronized
correctly, the time
and time domain of
the NMS server must
be set correctly.
l The manual NE
creation method
is applicable only
when several NEs
need to be created
on a large
microwave
transmission
network.
8.9.2 Common Task Collection (Microwave Links)

This section describes the common configuration tasks associated with microwave links.
Issue 02 (2012-12-30)

346

CAUTION
When you add or modify the configurations of a microwave link, you must first modify the
configurations of the NE that is located far from the network management system (NMS) server
and then modify the configurations of the NE that is located near to the NMS server.
NOTE
An MW_CFG_MISMATCH alarm is reported if the adaptive modulation (AM) status (enabled/disabled),

IEEE 1588 overheads, or parameters related to modulation schemes are set inconsistently at the two ends
of a microwave link. Clear the alarm as soon as possible because it may cause ineffective service
configurations or service interruptions.
Table 8-111 Common task collection (microwave links)
Issue 02 (2012-12-30)
Task
Application
Scenario
Configuration
Operation
Description
Configuring
the automatic
transmit power
control
(ATPC)
function
The ATPC function

must be enabled for the
microwave link or the
values of ATPC
parameters must be
changed.
A.5.1 Configuring a
Single Hop of
Microwave Link
To enable the ATPC

function, set ATPC
Enable Status to
Enabled and change
other ATPC
parameter values
according to the
planning
information.
Changing the
transmit power
You can change the

transmit power if the
fading margin is
insufficient but the
transmit power can still
be increased.

In RF, change TX
Power (dBm) or
parameter values
associated with
power.
347

Task
Application
Scenario
Changing the
modulation
scheme of a
microwave link
When the original

modulation scheme
does not meet the
service requirements,
you must use another
modulation scheme.
Configuration
Operation
Description
l Before using the
new modulation
scheme, contact
the network
planning
department to
confirm that the
Hybrid
microwave link
supports the new
Modulation
Mode of the
Guarantee AM
Capacity and
Modulation
Mode of the Full
AM Capacity.
l Ensure that the
parameter values
are the same at
both ends of the
Hybrid
microwave link.
8.9.3 Common Task Collection (Ethernet Services)

This section describes the common configuration tasks associated with Native Ethernet services.
Table 8-112 Common task collection (Ethernet services)
Issue 02 (2012-12-30)
Task
Application
Scenario
Configuration Operation
Remarks
Creating an
Ethernet
service
An Ethernet service
must be created
according to the service
plan.
A.7.3 Configuring Ethernet

Services
Setting or
modifying the
parameters of
Ethernet ports
If the service
requirements or
configurations at the
opposite end change,
the parameters of an
Ethernet port must be
changed.
A.6.1 Setting Parameters for

an Ethernet Port

348

Task
Application
Scenario
Remarks
Deleting an
Ethernet
service
Perform this operation

if you want to delete the
Ethernet services that
will no longer be used
to release the occupied
resources.
A.7.3.10 Deleting an E-Line

Service or A.7.3.11 Deleting
an E-LAN Service
Creating a
link
aggregation
group (LAG)
A.7.2.1 Creating a LAG

l Perform this
operation when the
available bandwidth
is insufficient and
you want to create a
LAG to increase the
bandwidth.
l Perform this
operation if you
want to improve
link reliability.
Changing
logical ports
mounted to an
Ethernet local
area network
(E-LAN)
Issue 02 (2012-12-30)

when the E-LAN
service requirements
change and the logical
ports connected to the
E-LAN must be
changed.
l When
creating a
LAG, set
the port that
already
carries
services to
be the main
port.
l This
operation
causes
transient
service
interruption
s.

Ports Mounted to a Bridge

You must add

or delete the
logical ports
connected to
the E-LAN, or
modify
attributes
associated with
the logical ports
connected to
the E-LAN
according to the
actual network
plan.
349

Task
Application
Scenario
Remarks
Managing the
MAC address
table
l Create MAC
address blacklist
entries when you
want to prevent
certain MAC
address hosts from
using E-LAN
services.
A.7.4 Managing MAC

Address Tables
A.7.6 Managing QoS
Change the
values of QoS
parameters to
adjust the QoS.
l Create static MAC

address entries
when you want to
prevent certain
MAC address
entries from being
aged.
l Set the aging
parameters of
corresponding
MAC addresses
when you want to
disable the aging
function or modify
the default aging
time (5 minutes).
Adjusting the
quality of
service (QoS)
Issue 02 (2012-12-30)

when the service
requirements change
and the QoS must be
adjusted.

350

A Task Collection
Task Collection
This document describes tasks related to OptiX RTN 310.

A.1 U2000 Quick Start
This chapter describes basic operations on the U2000 client.
A.2 Web LCT Quick Start
This chapter describes basic operations on the Web LCT client.
A.3 Network Management
Network management involves topology management, communication management, and
security management.
A.4 Security Management
Security management is an important part of network management.
A.5 Managing Microwave Links
Before you configure a microwave link between two microwave sites, configure information
about the microwave link.
A.6 Managing Ports
Setting port parameters correctly is the basis for configuring ports to carry services.
A.7 Managing Ethernet Services and Features
Configurations of Ethernet services and features on the packet plane include Ethernet port,
protection, service, protocol, and OAM configurations.
A.8 Managing Clocks
To ensure clock synchronization between transmission nodes on a transport network, you need
to manage the NE clocks.
A.9 Using RMON
Remote network monitoring (RMON) monitors the data traffic on a network segment or an entire
network. Currently, RMON is one of the most widely used network management standards.
A.10 Configuring a Native Ethernet Service (in End-to-End Mode)
The U2000 allows Native Ethernet services to be configured in an end-to-end mode.
A.11 Verifying Services and Features
This chapter describes how to verify service and feature configurations.
Issue 02 (2012-12-30)

351

A Task Collection
A.1 U2000 Quick Start

This chapter describes basic operations on the U2000 client.
A.1.1 Logging In to a U2000 Client

The U2000 uses the client/server architecture and allows multiple clients. You can log in to the
U2000 server from a U2000 client to manage OptiX RTN NEs.
Prerequisites
l
The U2000 system has been started on the U2000 server.
The IP address of the U2000 client is in the access control list (ACL) configured in the
U2000 system.
The U2000 client is communicating with the U2000 server properly.
Tools, Meter, and Materials

U2000
NOTE
Context
The following procedure helps you log in to the U2000 client.
Procedure
Step 1
----End
A.1.2 Shutting Down a U2000 Client

Shut down a U2000 client when it will not to be used.
Issue 02 (2012-12-30)

352

A Task Collection
Prerequisites

U2000
NOTE
Context
The following procedure shuts down a U2000 client.
Procedure
Step 1
----End
A.1.3 Using the Help

The Help provides help information about the U2000.
Prerequisites

U2000
NOTE
Context
The following procedure helps you use the iManager U2000 Help.
Issue 02 (2012-12-30)

353

A Task Collection
Procedure
Step 1
----End
A.1.4 Navigating to Common Views

This section describes how to navigate to the common views of the U2000 and the functions of
the views.
A.1.4.1 Navigating to Main Topology

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

U2000
NOTE
Context
The following procedure navigates to Main Topology.
Procedure
Step 1
Issue 02 (2012-12-30)

354

A Task Collection
----End
A.1.4.2 Navigating to NE Explorer

The U2000 provides the NE Explorer view for equipment management. The NE Explorer view
consists of the function tree pane, object tree pane, and configuration pane.
Prerequisites

U2000
NOTE
Context
The following procedure navigates to NE Explorer.
Procedure
Step 1
Issue 02 (2012-12-30)

355

A Task Collection
----End
A.1.4.3 Navigating to the NE Panel

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

U2000
NOTE
Context
The following procedure navigates to NE Panel.
Procedure
Step 1
Issue 02 (2012-12-30)

356

A Task Collection
----End
A.2 Web LCT Quick Start

This chapter describes basic operations on the Web LCT client.
A.2.1 Connecting the Web LCT to the Equipment

Prerequisites
NOTE
link.

Web LCT
Procedure
255.255.0.0).
Issue 02 (2012-12-30)

357

A Task Collection
configuration. For details, see Figure A-1.
CAUTION
Figure A-1 Ways for connecting the Web LCT to an OptiX RTN 310
1
P&E
MGMT
P&E
P&E
USB/RSSI/NMS
NMS/COM
P&E
4/P2
NMS
Fiber
To NodeB
MGMT
P&E
EG4P

(using the PI)

OptiX RTN 900s

OptiX RTN 310s
NOTE
the laptop.
Issue 02 (2012-12-30)

358

A Task Collection
l User Name: admin
----End
Follow-up Procedure
l
Issue 02 (2012-12-30)

359

A Task Collection
A.2.2 Using the Help

The Help provides help information about the Web LCT.
Prerequisites

Web LCT
NOTE
Context
The following procedure obtains help information related to the Web LCT.
Procedure
Step 1
Issue 02 (2012-12-30)

360

A Task Collection
----End
A.2.3 Navigating to NE Explorer

The U2000 provides the NE Explorer view for equipment management. The NE Explorer view
consists of the function tree pane, object tree pane, and configuration pane.
Prerequisites

Web LCT
NOTE
Context
The following procedure helps you navigates to NE Explorer by clicking NE Explorer.
Procedure
Step 1
Issue 02 (2012-12-30)

361

A Task Collection
----End
A.3 Network Management

Network management involves topology management, communication management, and
security management.
A.3.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the network management
system (NMS).
A.3.1.1 Creating an NE by Using the Search Method

The U2000 can find all NEs that communicate with a specific gateway NE by using the IP address
of the gateway NE, the network segment of the gateway NE IP address, or the NSAP addresses.
In addition, the U2000 can create the NEs that are found in batches. Compared with the method
of manually creating NEs, this search method creates NEs faster and more reliably.
Prerequisites
l
The network management system (NMS) is communicating with NEs properly.

U2000
NOTE
This task can also be performed on the Web LCT, but the steps are different from those on the U2000.
Context
l
Issue 02 (2012-12-30)
Creates an NE by using the search method.

362

A Task Collection
Creates an NE by using the NE Search method (only on the Web LCT) if the NE is the
gateway NE and belongs to the same network segment as the NMS server.
Procedure
Step 1 Create an NE by using the search method.
Step 2 Create an NE by using the NE Search method (only on Web LCT).
Issue 02 (2012-12-30)

363

A Task Collection
----End
Related References
B.1.1.1 Parameter Description: NE Searching
A.3.1.2 Creating an NE Manually

If you create NEs manually, you can create them one by one instead of in batches.
Prerequisites
l
The network management system (NMS) is properly communicating with the NE to be

created.
If the NE to be created is a non-gateway NE, the corresponding gateway NE has been

created.

U2000
NOTE
Context
The following procedure creates NE(9-16947) manually.
Procedure
Step 1
Issue 02 (2012-12-30)

364

A Task Collection
----End
Related References
B.1.1.2 Parameter Description: NE Creation
A.3.1.3 Logging In to an NE
After an NE is created, log in to the NE before you can manage it.
Prerequisites
l
The NE to be managed has been created in NE List.

Web LCT
NOTE
Context
The following procedure helps you log in to an NE.
Procedure
Step 1
Issue 02 (2012-12-30)

365

A Task Collection
----End
A.3.1.4 Changing an NE ID
Change the NE ID according to the engineering plan to ensure that each NE ID is unique. This
task does not interrupt services.
Prerequisites

U2000
NOTE
Context
The following procedure changes an NE ID to the planned value listed in the following table.
Parameter
Value
New ID
320
Procedure
Step 1
Issue 02 (2012-12-30)

366

A Task Collection
----End
A.3.1.5 Changing an NE Name

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

U2000
NOTE
Context
The following procedure changes an NE name to the planned value listed in the following table.
Parameter
Value
Name
Site2-1
Procedure
Step 1
Issue 02 (2012-12-30)

367

A Task Collection
----End
A.3.1.6 Synchronizing the NE Time

By configuring the NE time to be synchronous with the time on the network management system
(NMS) or standard Network Time Protocol (NTP) server, you can record the exact time when
an alarm and abnormal event occurs.
Prerequisites
l
The time zone and time have been set correctly on the PC or server running the NMS
software.
The time on the NTP server has been set correctly. The NTP protocol is running normally.

U2000
NOTE
Context
l
Synchronizes the NE time with the NMS time according to the planned parameter values
listed in the following table
Table A-1 Parameters for NE time synchronization
Issue 02 (2012-12-30)
Parameter
Value
Synchronous Mode
NM
Synchronizes the NE time with the NTP server time according to the planned parameter
values listed in the following tables.
368

A Task Collection
Table A-2 Parameters for NE time synchronization

Parameter
Value
Synchronous Mode
Standard NTP
Standard NTP Authentication
Disabled
Table A-3 Parameters for the standard NTP server

Parameter
Value
Standard NTP Server Flag
NE ID
Standard NTP Server
9-16
Standard NTP Server Key
Procedure
Step 1 Synchronize the NE time with the NMS time.
Step 2 Synchronize the NE time with the NTP server time.
Issue 02 (2012-12-30)

369

A Task Collection
----End
Related References
B.1.1.3 Parameter Description: NE Time Synchronization (U2000)
A.3.1.7 Localizing the NE Time

If daylight saving time (DST) is used in the area where an NE is located, localize the NE time
to synchronize it with the local time.
Prerequisites

U2000
NOTE
This task can also be performed on the Web LCT, but the steps are different from those on the U2000.
Context
The following procedure synchronizes the NE time with the local time according to the planned
Issue 02 (2012-12-30)
Parameter
Value
Time Zone (U2000)
(UTC+01:00)-Central European Time

(Europe/Berlin)
Time Zone (Web LCT)
(GMT+08:00)-China Standard Time(PRC)
DST
Selected
Start Rule
Week
End Rule
Week
370

A Task Collection
Procedure
Step 1 Localize the NE time (U2000).
Step 2 Localize the NE time (Web LCT).
----End
Related References
B.1.1.5 Parameter Description: Localization Management of the NE Time
A.3.1.8 Configuring a Standard NTP Key

Prerequisites
l
Synchronous Mode is set to Standard NTP, and Standard NTP Authentication is set
to Enabled.
Issue 02 (2012-12-30)

371

A Task Collection
The Network Time Protocol (NTP) is running properly. The NTP identity authentication
has been enabled on the NTP server.
Tools, Meter, and Materials

U2000
NOTE
Context
The following procedure configures a standard NTP key according to the planned parameter
Parameter
Value
Key ID
123
Password
test1234
Trusted
Yes
Procedure
Step 1
----End
Related References
B.1.1.4 Parameter Description: Standard NTP Key Management
A.3.2 Configuring NE Data

After an NE is created, configure NE data so that the network management system (NMS) can
manage this NE.
Issue 02 (2012-12-30)

372

A Task Collection
A.3.2.1 Uploading NE Data

Uploading NE data is commonly used for configuring NE data. By performing this task, you
can upload NE data, such as configuration, alarm, and performance data, to the network
management system (NMS).
Prerequisites
l
You have logged in to the NE.

U2000
NOTE
Context
l
Uploads NE data when the NE has not been configured.
Uploads NE data when the NE has been configured.
Procedure
Step 1 Upload NE data when the NE has not been configured.
Step 2 Upload NE data when the NE has been configured.
Issue 02 (2012-12-30)

373

A Task Collection
----End
A.3.2.2 Synchronizing NE Data

Synchronizing NE data is uploading the NE-side data that is different from the NMS-side data,
including conflicting data and absent data, to the network management system (NMS).
Prerequisites
l
An NE has been created.
The NE is in unsynchronized state.

NOTE
An NE in unsynchronized state is marked with

U2000
NOTE
Context
The following procedure synchronizes NE data.
Procedure
Step 1
Issue 02 (2012-12-30)

374

A Task Collection
----End
A.3.3 Setting the Performance Monitoring Status for an NE

By performing this task, you can manually enable or disable performance monitoring for NEs,
or set the performance monitoring period.
Prerequisites

U2000
NOTE
Context
The following procedure enables the 15-minute performance monitoring function and the 24hour performance monitoring function for an NE.
Procedure
Step 1
Issue 02 (2012-12-30)

375

A Task Collection
----End
A.3.4 Creating a Fiber/Cable

To implement end-to-end service management on the network management system (NMS), you
must create fibers or cables first.
A.3.4.1 Creating a Fiber/Cable by Using the Search Method

The network management system (NMS) can find the fibers connected to a specified microwave
port or Ethernet port by using the search method. This method is the most common method for
creating microwave links.
Prerequisites

U2000
NOTE
Context
The following procedure creates a microwave link or an Ethernet link on the RTN subnet using
the search method.
Procedure
Step 1 Create a microwave link on the RTN subnet using the search method.
Issue 02 (2012-12-30)

376

A Task Collection
Step 2 Create an Ethernet link on the RTN subnet using the search method.
----End
A.3.4.2 Creating a Fiber/Cable Manually

You can create a fiber by specifying the ports connected by the fiber. This method can be used
to create both microwave links and Ethernet links.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

377

A Task Collection
Context
The following procedure creates a fiber manually according to the planned parameter values
Parameter
Value
Fiber/Cable Type
Radio Link
Name
l-1
Source NE
NE16938
Source NE Subrack-Slot-Board Type-Port
1-SHXA2-1(IF)
Sink NE
NE(12916937)
Sink NE Subrack-Slot-Board Type-Port
1-SHXA2-1(IF)
Automatically Allocate IP Address
No
Procedure
Step 1
----End
A.3.4.3 Creating an Extended ECC Connection

Extended embedded control channel (ECC) connections indicate that inter-NE data
communication network (DCN) communication is implemented using cascaded network
management system (NMS) ports.
Prerequisites
Issue 02 (2012-12-30)

378

A Task Collection

U2000
NOTE
Context
The following procedure creates an extended ECC connection according to the planned
Parameter
Value
Name
Extended ECC-1
Source NE
NE16938
Sink NE
NE(12916937)
Procedure
Step 1
----End
A.3.4.4 Creating a Back-to-back Radio Connection

Back-to-back radio connections indicate the stacking of multiple OptiX RTN NEs at the same
site.
Prerequisites
Issue 02 (2012-12-30)

379

A Task Collection

U2000
NOTE
Context
The following procedure creates a back-to-back radio connection according to the planned
Parameter
Value
Name
b-1
Source NE
NE(916943)
Sink NE
NE16938
Procedure
Step 1
----End
A.3.5 Managing Subnets

To facilitate NE management, you can allocate the NEs that are in the same domain or that have
similar attributes to the same subnet.
A.3.5.1 Creating a Subnet

In Main Topology, you can create a subnet object and allocate an NE to this subnet.
Issue 02 (2012-12-30)

380

A Task Collection
Prerequisites

U2000
NOTE
Context
The following procedure creates a subnet named RTN.
Procedure
Step 1
----End
A.3.5.2 Copying a Topology Object

In the current topology, you can copy topology objects from one subnet to another subnet.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

381

A Task Collection
Context
The following procedure copies NE16938 to the RTN subnet.
Procedure
Step 1
----End
A.3.5.3 Moving a Topology Object

In the current topology, you can move topology objects from one subnet to another subnet.
Prerequisites

U2000
NOTE
Context
The following procedure moves NE16938 to the RTN subnet.
Procedure
Step 1
Issue 02 (2012-12-30)

382

A Task Collection
----End
A.3.6 Managing Communication

To manage NEs using the network management system (NMS), ensure that the data
communication network (DCN) communication between the NEs and NMS is normal.
A.3.6.1 Setting NE Communication Parameters

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

U2000
NOTE
Precautions
If multiple parameters need to be set, click Apply after setting each parameter.
Context
The following procedure sets the IP address and subnet mask of an NE to the planned values
Issue 02 (2012-12-30)
Parameter
Value
IP Address
129.9.0.1
Subnet Mask
255.255.0.0

383

A Task Collection
Procedure
Step 1
----End
Related References
B.1.2.1 Parameter Description: NE Communication Parameter Setting
A.3.6.2 Configuring DCCs

To meet the requirements for managing a complex network, you must set the channel type,
protocol type, and status of data communications channels (DCCs) according to the network
plan.
Prerequisites

U2000
NOTE
Context
The following procedure changes the DCC protocol to Huawei embedded control channel
(HWECC).
Issue 02 (2012-12-30)
Parameter
Value
Enabled/Disabled
Protocol Type
HWECC

384

A Task Collection
Procedure
Step 1
----End
Related References
B.1.2.6 Parameter Description: DCC Management_DCC Rate Configuration
A.3.6.3 Setting the VLAN ID and Bandwidth for an Inband DCN

The VLAN ID used by an inband data communication network (DCN) must be different from
the VLAN ID used by services. The bandwidth of an inband DCN must meet the requirements
of the transmission network for managing messages.
Prerequisites

U2000
NOTE
Context
The following procedure sets the VLAN ID and bandwidth to the planned values listed in the
following table for an inband DCN.
Issue 02 (2012-12-30)
Parameter
Value
VLAN ID
4092
Bandwidth(Kbit/s)
1000bit/s

385

A Task Collection
Procedure
Step 1
----End
Related References
B.1.2.15 Parameter Description: DCN Management_Bandwidth Management
A.3.6.4 Configuring the Priorities of Inband DCN Packets

By performing this task, you can set the VLAN priorities and differentiated services code point
(DSCP) values carried by inband data communication network (DCN) packets.
Prerequisites

U2000
NOTE
Context
The following procedure sets the VLAN priority and DSCP value carried by inband DCN packets
to the planned values listed in the following table.
Issue 02 (2012-12-30)
Packet Type
Priority
VLAN
EF
DSCP
BE (default value)

386

A Task Collection
Procedure
Step 1
----End
Related References
B.1.2.18 Parameter Description: DCN Management_Packet Control
A.3.6.5 Setting a Port for an Inband DCN

By performing this task, you can set the inband data communication network (DCN) status and
inband DCN protocol stack type for an inband DCN port.
Prerequisites

U2000
NOTE
Context
l
Issue 02 (2012-12-30)
Sets the inband DCN protocol stack to the Huawei embedded control channel (HWECC)
protocol stack for two Ethernet ports.
Parameter
GE1
GE2
Enabled Status
Protocol Type
HWECC
HWECC

387

A Task Collection
Disables the inband DCN function of a microwave port.

Parameter
IF
Enabled Status
Disabled
Procedure
Step 1 Change the inband DCN protocol stack for an Ethernet port.
Step 2 Change the inband DCN status for a microwave port.
----End
Related References
B.1.2.16 Parameter Description: DCN Management_Port Setting
Issue 02 (2012-12-30)

388

A Task Collection
A.3.6.6 Configuring Access Control

When an NE is connected to the network management system (NMS) using an Ethernet service
port, you must configure access control.
Prerequisites

U2000
NOTE
Context
The following procedure configures the access control function for the port GE1 according to
the planned parameter values listed in the following table.
Parameter
Value
Enabled Status
IP Address
129.9.0.1
Subnet Mask
255.255.0.0
Procedure
Step 1
----End
Related References
B.1.2.17 Parameter Description: DCN Management_Access Control
Issue 02 (2012-12-30)

389

A Task Collection
A.3.6.7 Configuring Extended ECCs

Two extended embedded control channel (ECC) modes are available: auto and manual.
Prerequisites
Tools, Instruments and Materials

U2000
NOTE
Precautions
The default extended ECC mode is Auto mode.
Context
l
Disables the extended ECC function in auto mode.
Enables the manual extended ECC function and configures an NE as the server, according
to the planned parameter values listed in the following table.
Parameter
Value
Port
1602
Enables the manual extended ECC function and configures an NE as the client, according
Parameter
Value
Opposite IP
129.9.0.1
Port
1602
Procedure
Step 1 Disable the extended ECC function in auto mode.
Issue 02 (2012-12-30)

390

A Task Collection
Step 2 Enable the manual extended ECC function and configure an NE as the server.
Step 3 Enable the manual extended ECC function and configure an NE as the client.
----End
Issue 02 (2012-12-30)

391

A Task Collection
Related References
B.1.2.2 Parameter Description: ECC Management_Ethernet Port Extended ECC
A.3.6.8 Creating a Static IP Route

When dynamic routes fail to meet planning requirements, you must create static IP routes
manually.
Prerequisites

U2000
NOTE
Context
The following procedure creates a static IP route according to the planned parameter values
Parameter
Value
Destination Address
129.9.0.7
Subnet Mask
255.255.255.255
Gateway
129.0.0.1
Procedure
Step 1
----End
Issue 02 (2012-12-30)

392

A Task Collection
Related References
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management
A.3.6.9 Setting OSPF Protocol Parameters

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

U2000
NOTE
Context
The following procedure configures OSPF parameters according to the planned parameter values
Parameter
Value
Area
0.0.0.1
OSPF Status
Enabled
Static route
Enabled
LAN Interface
Disabled
Procedure
Step 1
Issue 02 (2012-12-30)

393

A Task Collection
----End
Related References
B.1.2.11 Parameter Description: Management of Multiple OSPF Areas
A.3.6.10 Creating an OSPF Area

If an NE functions as an area border router (ABR), you must create the non-backbone area to
which the ABR belongs.
Prerequisites

U2000
NOTE
Context
The following procedure creates an Open Shortest Path First (OSPF) area according to the
planned parameter values listed in the following table.
Issue 02 (2012-12-30)
Parameter
Value
ID
0.0.0.1
IP Address
129.11.0.0
Subnet Mask
255.255.0.0
Authentication Type
none
Automatic Route Aggregation
Enabled

394

A Task Collection
Parameter
Value
Stub Type
NON-STUB
Procedure
Step 1
----End
Related References
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas
A.3.6.11 Configuring the Network Information of an ABR

By performing this task, you can add or modify the network information of an area border router
(ABR).
Prerequisites

U2000
NOTE
Context
l
Issue 02 (2012-12-30)
Modifies the network information about the backbone Open Shortest Path First (OSPF)
area according to the planned parameter values listed in the following table.
395

A Task Collection
Parameter
Value
IP Address
129.9.0.0
Subnet Mask
255.255.0.0
Adds the network information about a non-backbone OSPF area according to the planned
Parameter
Value
IP Address
129.10.0.0
Subnet Mask
255.255.0.0
Procedure
Step 1 Modify the network information about the backbone OSPF area.
Step 2 Add the network information about a non-backbone OSPF area.
----End
Issue 02 (2012-12-30)

396

A Task Collection
Related References
A.3.6.12 Creating a Manual Route Aggregation Group

An NE supports a maximum of eight manual route aggregation groups.
Prerequisites

U2000
NOTE
Context
The following procedure creates a manual route aggregation group according to the planned
Parameter
Value
IP Address
129.11.0.0
Subnet Mask
255.255.0.0
Procedure
Step 1
----End
Issue 02 (2012-12-30)

397

A Task Collection
Related References
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be
Manually Aggregated
A.3.6.13 Configuring Port IP Addresses for an ABR

If a port on an area border router (ABR) does not belong to the backbone area, you must configure
an IP address for this port.
Prerequisites

U2000
NOTE
Context
l
Sets a port IP address for the data communications channel (DCC) at a microwave port.
Parameter
Value
Enabled/Disabled
Protocol Type
IP (default value)
IP Address
129.9.0.10
Subnet Mask
255.255.255.255
Sets a port IP address for the inband data communication network (DCN) channel at the
Ethernet port GE1.
Parameter
Value
Enabled/Disabled
Protocol Type
IP (default value)
IP Address
129.9.0.11
Subnet Mask
255.255.255.255
Procedure
Step 1 Set a port IP address for the DCC channel at a microwave port.
Issue 02 (2012-12-30)

398

A Task Collection
Step 2 Set a port IP address for the inband DCN channel at the Ethernet port GE1.
----End
A.3.6.14 Configuring the OSPF Authentication Type

By performing this task, you can configure the authentication type for an OSPF area and also
configure authentication passwords for different port types when different authentication types
are used.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

399

A Task Collection
Context
l
Changes the authentication type for area 0.0.0.1.

Table A-4 Authentication Type
Parameter
Value
Authentication Type
MD5
Sets the passwords used for a data communication network (DCN) port when different
Open Shortest Path First (OSPF) authentication types are used.
Table A-5 Authentication Password
Port Type
Authentication
Type
Authentication
Password
MD5 Key
LAN
MD5
abc123
16
DCC
none (default value)
Procedure
Step 1 Change the authentication type for an area.
Step 2 Set the passwords used for a DCN port when different OSPF authentication types are used.
Issue 02 (2012-12-30)

400

A Task Collection
----End
Related References
B.1.2.9 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
A.3.6.15 Enabling the Proxy ARP

The proxy Address Resolution Protocol (ARP) enables NEs in the same network segment but
different domains to communicate with one another.
Prerequisites

U2000
NOTE
Context
The following procedure enables the proxy ARP function for NE1 (gateway NE) shown in the
following figure. By performing this operation, the network management system (NMS) gains
direct access to NE2.
Issue 02 (2012-12-30)

401

A Task Collection
ARP proxy enabled

NE 1
NE 2
Third-party NMS
129.9.0.100
129.9.0.1
129.9.0.2
Ethernet link
Radio link
Procedure
Step 1
----End
Related References
B.1.2.10 Parameter Description: IP Protocol Stack_Proxy ARP
A.3.6.16 Querying ECC Routes

By querying embedded control channel (ECC) routes, you can check whether the HWECC
solution is correctly configured and whether NEs properly communicate with one another.
Prerequisites

U2000
Issue 02 (2012-12-30)

402

A Task Collection
NOTE
Context
The following procedure checks whether the NE ECC routes and parameters are properly
planned.
Procedure
Step 1
----End
Related References
B.1.2.3 Parameter Description: NE ECC Link Management
A.3.6.17 Querying IP Routes

By querying IP routes, you can check whether the IP data communication network (DCN)
solution and inband DCN solution are configured correctly and whether NEs properly
communicate with one another.
Prerequisites

U2000
NOTE
Context
The following procedure checks whether the NE IP routes and parameters are properly planned.
Issue 02 (2012-12-30)

403

A Task Collection
Procedure
Step 1
----End
Related References
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management
A.3.6.18 Verifying Connectivity of an ECC Network

You can use the ping or traceroute function to verify the data communication network (DCN)
connectivity between two NEs on an embedded control channel (ECC) network.
Prerequisites

U2000
NOTE
Context
l
Checks the DCN connectivity between two NEs on an ECC network by using the ping
function.
Checks the DCN connectivity between two NEs on an ECC network by using the traceroute
function.
Procedure
Step 1 Check the DCN connectivity by using the ping function.
Issue 02 (2012-12-30)

404

A Task Collection
Step 2 Check the DCN connectivity by using the traceroute function.
----End
Related References
B.1.2.4 Parameter Description: ECC Link Management_Availability Test
A.3.6.19 Verifying Connectivity of an IP DCN Network

You can use the ping or traceroute function to verify the data communication network (DCN)
connectivity between two NEs on an IP DCN network.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

405

A Task Collection
Context
l
Checks the DCN connectivity between two NEs on an IP DCN network by using the ping
function.
Checks the DCN connectivity between two NEs on an IP DCN network by using the
traceroute function.
Procedure
Step 1 Check the DCN connectivity by using the ping function.
Step 2 Check the DCN connectivity by using the traceroute function.
----End
Related References
B.1.2.8 Parameter Description: IP Protocol Stack Management_Availability Test
Issue 02 (2012-12-30)

406

A Task Collection
A.3.6.20 Setting SNMP Communication Parameters

By performing this task, you can configure the Simple Network Management Protocol (SNMP)
parameters for an NE that functions as an SNMP agent. This SNMP agent uses these parameters
to communicate with the SNMP server.
Prerequisites

U2000
NOTE
Precautions
The SNMP version, read/write permissions, and community name planned for an OptiX RTN
310 must be the same as those for the SNMP server.
Context
The following procedure configures the SNMP server to directly query alarms and performance
events on all NEs.
NE 1
NE 2
NE 8
NE 7
IP DCN
NE 3
External DCN
NE 6 (GNE)
NE 4
SNMP server
IP address: 10.10.10.3
NE 5
Based on the SNMP server information, the SNMP parameters planned for all NEs are listed in
Table A-6 SNMP plan
Parameter
All NEs
IP address of the SNMP server
10.10.10.3
Read/Write permissions
Reading and writing
Read community name
Read_01
Write community name
Write_01
Issue 02 (2012-12-30)

407

A Task Collection
Parameter
All NEs
Trap version
SNMP V2C
Report MW performance Trap
Report
Report IP performance Trap
Report
Report Alarm Trap
Report
Port
162
Procedure
Step 1
----End
Related References
B.1.2.19 Parameter Description: SNMP Communications Parameters Setting
A.3.6.21 Configuring the Active and Standby Gateway NEs

By performing this task, you can configure the active and standby gateway NEs on a data
communication network (DCN) to improve network reliability.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

408

A Task Collection
Context
The following procedure configures the standby gateway NE for NE(129-16937) according to
the planned parameter value listed in the following table.
Parameter
Value
Standby gateway NE
NE16938
Procedure
Step 1
----End
A.3.7 Configuring the NMS Port on an NE

By default, an NE can connect to the network management system (NMS) or another NE through
its NMS port. The NMS port works in auto-negotiation mode.
Prerequisites

U2000
NOTE
Precautions
l
It is recommended that the Web LCT access an NE through an Ethernet port
If you need to initialize an NE or download software by using the LCT, the LCT must
access the NE through an Ethernet port.
Issue 02 (2012-12-30)

409

A Task Collection
Context
The following procedure sets the working mode for an Ethernet port according to the planned
Parameter
Value
Work Mode
100M Full-Duplex
Enable Ethernet Access
Enabled
Procedure
Step 1
----End
Related References
B.1.2.5 Parameter Description: Access Control
A.4 Security Management

Security management is an important part of network management.
A.4.1 Configuring an NE User

NE users refer to the users who log in to and operate NEs. Different types of NE users are
assigned different rights to log in to and manage NEs.
A.4.1.1 Creating an NE User

NE users are divided into five levels in ascending order of operation rights: monitor level,
operation level, maintenance level, system level, and debug level. Different levels of NE users
can be created as required.
Issue 02 (2012-12-30)

410

A Task Collection
Prerequisites
l
You must be an NM user with a higher level than the user to be created.

U2000
NOTE
Precautions
l
The default NE user is at the monitor level.
For security of NE data, it is recommended to assign operations rights to NE users based

on their responsibilities.
Context
The following procedure creates an NE user according to the planned parameter values listed in
Parameter
Value
NE User
user1
User Level
Monitor Level (default value)
Procedure
Step 1
----End
Issue 02 (2012-12-30)

411

A Task Collection
A.4.1.2 Changing the Password of an NE User

Periodically changing the password of an NE user ensures the NE security.
Prerequisites
l
An NE user has been created.
You must be an NM user with a higher level than the user whose password is to be changed.

U2000
NOTE
Precautions
Periodically change the password of an NE user to ensure NE security.
Context
The following steps change the password of user1.
Procedure
Step 1
----End
A.4.1.3 Setting the Warning Screen Parameters

By performing this task, you can enable the warning screen function. With this function enabled,
the network management system (NMS) displays some information to a user when the user logs
in to an NE. The displayed information can be defined by carriers.
Issue 02 (2012-12-30)

412

A Task Collection
Prerequisites

U2000
NOTE
Context
The following procedure enables the warning screen function. After you log in to an NE, the
NMS displays the message "The NE is online."
Procedure
Step 1
----End
A.4.1.4 Switching NE Users

By performing this task, you can switch an NE user to a higher-level NE user when the operations
on the network management system (NMS) are beyond the operation rights of the NE user.
Prerequisites
l
An NE user has been created.

U2000
NOTE
Issue 02 (2012-12-30)

413

A Task Collection
Precautions
An NE user cannot log in to and manage an NE from different servers at the same time. If an
NE user logs in to an NE from two servers at different time, the first logged-in user is forcibly
logged out.
Context
The following procedure switches an NE user according to the planned parameter value listed
Parameter
Value
NE user to be switched
user1
Procedure
Step 1
----End
A.4.2 Configuring Web LCT Access to an NE

When an NE is managed by the network management system (NMS), the Web LCT can access
this NE by default.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

414

A Task Collection
Precautions
l
If the Web LCT requests to log in to an NE to which the NMS has logged in, the NE
determines whether to permit the login of the Web LCT according to LCT Access Control
Switch.
If the Web LCT requests to log in to an NE to which the NMS has not logged in, the NE
permits the login of the Web LCT regardless of LCT Access Control Switch. After the
Web LCT logs in, the NMS can also log in to the NE. After the NMS user logs in to the
NE successfully, the logged-in Web LCT user is not affected even if LCT Access Control
Switch is set to Disable Access.
Context
The following procedure disables Web LCT access.
Procedure
Step 1
----End
A.4.3 Configuring an Access Control List for an NE

This chapter describes how to configure an access control list (ACL) for an NE to filter IP packets
attempting to access the NE.
A.4.3.1 Creating Basic ACL Rules

This section describes how to create basic access control list (ACL) rules for an NE. Based on
the basic ACL rules, IP packets attempting to access the NE can be filtered by source address.
Prerequisites

U2000
Issue 02 (2012-12-30)

415

A Task Collection
NOTE
Context
The following procedure sets a basic ACL rule which allows IP packets with the source IP
addresses in the network segment 129.9.0.0/16 to traverse the NE.
Procedure
Step 1
----End
A.4.3.2 Creating Advanced ACL Rules

This section describes how to create advanced access control list (ACL) rules for an NE. Based
on the advanced ACL rules, IP packets attempting to access the NE can be filtered by source/
sink address, source/sink port, and protocol type.
Prerequisites

U2000
NOTE
Context
The following procedure sets an ACL rule which forbids TCP packets with the sink port number
23 to traverse the NE.
Issue 02 (2012-12-30)

416

A Task Collection
Procedure
Step 1
----End
A.4.4 Querying NE Operation Logs

This section describes how to query operation logs of an NE.
Prerequisites

U2000
NOTE
Context
The followings steps allow you to browse the operation logs of user szhw.
Procedure
Step 1
Issue 02 (2012-12-30)

417

A Task Collection
----End
A.4.5 Querying Operation Logs Sent to Syslog Servers

This section describes how to query operation logs sent from an NE to its Syslog servers.
Prerequisites
You must be an NM user with NE monitor rights or higher.

U2000
NOTE
Procedure
Step 1
----End
Issue 02 (2012-12-30)

418

A Task Collection
A.4.6 Configuring Syslog

This chapter describes how to configure Syslog if Syslog servers are used to collect logs of all
NEs on a network.
A.4.6.1 Enabling the Syslog Service

This section describes how to enable the Syslog service if an NE is required to forward its logs
to Syslog servers.
Prerequisites

U2000
NOTE
Context
The following procedure enables Syslog services for an NE.
Procedure
Step 1
----End
A.4.6.2 Setting Types and Severities of Logs to Be Sent to Syslog Servers

This section describes how to set types and severities of logs to be sent to Syslog servers.
Issue 02 (2012-12-30)

419

A Task Collection
Prerequisites

U2000
NOTE
Context
The following procedure adds a type of logs to be transferred to the Syslog server. The following
table provides the log type and severity.
Parameters
Value
Log Type
security/authorization messages
Log Severity
Debug
NOTE
By default, the NE forwards security/authentication messages of all severities to the Syslog server.
Procedure
Step 1
----End
A.4.6.3 Configuring Syslog Servers

This section describes how to set Syslog server-related parameters on NEs that transmit logs to
Syslog servers.
Issue 02 (2012-12-30)

420

A Task Collection
Prerequisites

U2000
NOTE
Context
The following procedure configures a Syslog server. The following table provides information
about logs received by the server.
Parameters
Value
IP Address
129.9.100.200
Send Mode
UDP
Port
514
Procedure
Step 1
----End
A.4.6.4 Configuring Gateway NEs for Communication Between NEs and Syslog
Servers
If no IP routes are available between an NE and its Syslog servers, configure a gateway NE to
forward the NE's logs to the Syslog servers. Ensure that IP routes are available between the
gateway NE and the Syslog servers, and the data communication network (DCN) communication
between the NE and the gateway NE is normal.
Issue 02 (2012-12-30)

421

A Task Collection
Prerequisites

U2000
NOTE
Context
The following procedure sets NE(9-16938) as the gateway NE for forwarding logs to the Syslog
server.
Procedure
Step 1
----End
A.4.7 Configuring File Transfer Protocols

This section describes how to configure file transfer protocols that are used when the network
management system (NMS) loads software to NEs. The File Transfer Protocol (FTP) or Secure
File Transfer Protocol (SFTP) is used by default when the NMS loads software to NEs.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

422

A Task Collection
Context
The following procedure prevents the NMS from loading software to NE(9-16838) using the
FTP.
Procedure
Step 1
----End
A.4.8 Configuring SSL Protocol Communication

The security socket layer (SSL) protocol provides encrypted and reliable communication
between entities, improving the network management security.
A.4.8.1 Configuring SSL Protocol Communication Between a U2000 Server and Its
Clients
Secure Sockets Layer (SSL) protocol communication between a U2000 server and its clients is
supported only after corresponding configurations are performed on the U2000 server and
clients.
Prerequisites
The connection mode of the U2000 server is set to SSL.

U2000
NOTE
Issue 02 (2012-12-30)

423

A Task Collection
Precautions
l
Two connection modes are supported, which are Common and Security(SSL). You can
query the connection mode on the U2000 server by running a query command.
The default connection mode is Common.

NOTE
l When the U2000 server and its client are deployed on the same host and the U2000 server uses the
SSL connection mode, the client can log in to the server by using the common or SSL connection
mode. When the U2000 server and its client are deployed on the same host and the U2000 server uses
the common connection mode, the client can log in to the server only by using the common connection
mode.
l When the U2000 server and its client are deployed on different hosts, the client can log in to the U2000
server only by using the same connection mode as the U2000 server.
Context
The following procedure sets the connection mode to Security (SSL) for a client.
Procedure
Step 1
----End
A.4.8.2 Configuring the Connection Mode Between the U2000 and Its Gateway NE
Two connection modes are supported between the U2000 and its gateway NE: common
connection mode and Secure Sockets Layer (SSL) connection mode.
Prerequisites
l
SSL licenses have been deployed on the gateway NE and the U2000 according to the SSL
loading guide.

U2000
Issue 02 (2012-12-30)

424

A Task Collection
NOTE
Context
The following procedure configures NE(12916937), the gateway NE, to communicate with the
U2000 by using only the SSL protocol.
Procedure
Step 1 Configure the connection mode of the U2000.
Step 2 Configure the connection mode of the gateway NE.
----End
A.4.9 Configuring RADIUS Authentication

The Remote Authentication Dial In User Service (RADIUS) authentication function allows a
RADIUS server to implement centralized management over all users that log in to an NE.
Issue 02 (2012-12-30)

425

A Task Collection
A.4.9.1 Enabling/Disabling the RADIUS Authentication Function

An NE can use the Remote Authentication Dial In User Service (RADIUS) authentication
function only after the RADIUS client function is enabled on the NE. An NE can function as a
proxy server only after the proxy server function is enabled on the NE.
Prerequisites

U2000
NOTE
Context
The following procedure configures the local NE as the gateway NE, enables the RADIUS
authentication function, and configures the local NE as the proxy server.
Procedure
Step 1
----End
Related References
B.1.3.2 Parameter Description: Enabling/Disabling the RADIUS Function
A.4.9.2 Creating a RADIUS Server or a RADIUS Proxy Server

A Remote Authentication Dial In User Service (RADIUS) server needs to be configured if an
NE uses RADIUS authentication in network access server (NAS) mode or functions as a proxy
server. A RADIUS proxy server needs to be configured if an NE uses RADIUS authentication
in proxy NAS mode.
Issue 02 (2012-12-30)

426

A Task Collection
Prerequisites
l
The RADIUS authentication function has been enabled for an NE.

U2000
NOTE
Context
l
Configures the RADIUS server according to the planned parameter values listed in the
following table, when the NE performs security authentication in NAS mode or functions
as a proxy server.
Parameter
Value
Function
Authentication
Server Type
Radius Server
Server ID
IP Address: 10.10.10.1
Configures the proxy server according to the planned parameter values listed in the
following table, when the NE performs security authentication in proxy NAS mode.
Parameter
Value
Function
Authentication
Server Type
Proxy Server
Server ID
NE ID: NE(12916937)
Procedure
Step 1 Configure information about the RADIUS server.
Issue 02 (2012-12-30)

427

A Task Collection
Step 2 Configure information about the RADIUS proxy server.
----End
Related References
B.1.3.1 Parameter Description: RADIUS Configuration_Creation
A.4.9.3 Configuring RADIUS Server Parameters

This section describes how to configure Remote Authentication Dial In User Service (RADIUS)
server parameters.
Prerequisites
l
The RADIUS server or RADIUS proxy server has been configured for an NE.
The RADIUS authentication function has been enabled for the NE.

U2000
Issue 02 (2012-12-30)

428

A Task Collection
NOTE
Context
l
Configures RADIUS server parameters according to the planned parameter values listed
in the following table, when the NE performs security authentication in network access
server (NAS) mode.
Parameter
Value
Function
Authentication
Server Type
Radius Server
Server ID
IP Address: 10.10.10.1
Server Status
Active
Shared Key
Abcd1234
Interval of Packet Transmission
5 (default)
Packet Retransmission Attempts
3 (default)
Configures RADIUS server parameters according to the planned parameter values listed
in the following table, when the NE performs security authentication in proxy NAS mode.
Parameter
Value
Function
Authentication
Server Type
Proxy Server
Server ID
NE ID: NE(92327)
Server Status
Active
Interval of Packet Transmission
5 (default)
Packet Retransmission Attempts
3 (default)
Procedure
Step 1 Configure RADIUS server parameters when the NE performs security authentication in NAS
mode.
Issue 02 (2012-12-30)

429

A Task Collection
Step 2 Configure RADIUS server parameters when the NE performs security authentication in proxy
NAS mode.
----End
Related References
A.5 Managing Microwave Links

Before you configure a microwave link between two microwave sites, configure information
about the microwave link.
A.5.1 Configuring a Single Hop of Microwave Link

By performing this task, you can set the basic attributes for the local NE and the peer NE on a
single hop of microwave link.
Issue 02 (2012-12-30)

430

A Task Collection
Prerequisites
l
The sites at the two ends of a microwave link hop are communicating properly.

U2000
NOTE
Precautions
The following parameters of the NEs on a hop of microwave link are automatically synchronized:
Link ID, IF Channel Bandwidth, XPIC, AM, Modulation Mode of the Guaranteed AM
Capacity, Modulation Mode of the Full AM Capacity, Modulation Mode, T/R Spacing
(MHz), and ATPC. That is, if one of the preceding parameters is modified on an NE, the
modification is automatically duplicated on the peer NE.
Context
The following procedure configures basic information for the hop of microwave link shown in
the following figure by configuring NE1. The hop of microwave link is a member of a cross
polarization interference cancellation (XPIC) group.
NE1
NE3
V-polarization
GE
GE
COMBO
COMBO
COMBO
COMBO
H-polarization
GE
NE2
GE
NE4
The planned parameter values are listed in the following table.
Issue 02 (2012-12-30)
Parameter
Link 1
Link 2
NE ID
9-2327(Local Radio
Terminal)
9-2322(Local Radio
Terminal)
Terminal)
Terminal)
Link ID
TX frequency at the TX high

site (MHz)
14920 (NE1)
14920 (NE2)
TX frequency at the TX low

site (MHz)
14500 (NE3)
14500 (NE4)

431

A Task Collection
Parameter
Link 1
Link 2
RF configuration mode
XPIC
XPIC
Polarization direction
H (horizontal polarization)
Radio working mode
28 MHz
28 MHz
AM
Disabled
Disabled
Modulation Mode
16QAM
16QAM
T/R Spacing (MHz)
420
420
ATPC
Disabled
Disabled
TX power (dBm)
22
22
RX power (dBm)
-26
-26
Procedure
Step 1
----End
Related References
B.2.3 Parameters Description: Radio Link Configuration
A.5.2 Browsing the Performance of a Hop of Microwave Link

This section describes how to query performance information about a microwave link hop.
Prerequisites
Issue 02 (2012-12-30)

432

A Task Collection

Web LCT
NOTE
Context
The following procedure queries performance information about a microwave link hop.
Procedure
Step 1
----End
A.5.3 Creating a Microwave 1+1 Protection Group

If microwave links are configured with 1+1 hot standby (HSB), frequency diversity (FD), or
space diversity (SD) protection, you need to create a corresponding microwave 1+1 protection
group.
Prerequisites
l
An enhanced link aggregation group (E-LAG) has been configured.
1+1 protection cannot coexist with cross polarization interference cancellation (XPIC) or
physical link aggregation (PLA).
The Ethernet ports on the active and standby OptiX RTN 310s must both be P&E electrical
ports or GE optical ports, and work in Auto-negotiation mode. A static and non-load
sharing link aggregation group (LAG) has been created on each of the active and standby
OptiX RTN 310s. The LAG has only one member port, which is an Ethernet port.
Ethernet services are received/transmitted through either the GE optical port or the P&E
electrical port of an OptiX RTN 310. If Ethernet services are received/transmitted through
both ports, 1+1 protection cannot be successfully configured.
Issue 02 (2012-12-30)

433

A Task Collection
The COMBO ports on the active and standby OptiX RTN 310s are connected using an
optical fiber.
Logical Port Attribute has been set to Electrical Port if the Ethernet port in the 1+1
protection group is a P&E electrical port.

U2000
Context
The following procedure creates a microwave 1+1 protection group according to the planned
Parameter
Value
Working Mode
HSB
Reversion Mode
Revertive
WTR Time (s)
600 (default value)
Enable Reverse Switching
Enable
Working/Protection Unit Type
Working Unit
Service Port
1-SHXA2-2(GE1)
Procedure
Step 1
----End
Related References
B.2.1 Parameter Description: IF 1+1 Protection Group
Issue 02 (2012-12-30)

434

A Task Collection
A.5.4 Microwave 1+1 Protection Switching

You can perform external switching on the microwave 1+1 protection by performing microwave
1+1 protection switching.
Prerequisites
l
Microwave 1+1 protection has been configured.

U2000
NOTE
Context
The following procedure performs external switching on a microwave 1+1 protection group
according to the planned parameter values listed in the following table.
Parameter
Value
Working Mode
SD
Unit
Working Board
Switching Conditions
Force Switching to Protection Port
Procedure
Step 1
----End
Issue 02 (2012-12-30)

435

A Task Collection
A.5.5 Querying the Microwave 1+1 Protection Status

You can learn about the current information about the microwave 1+1 protection by querying
the microwave 1+1 protection status.
Prerequisites
l
Microwave 1+1 protection has been configured.

U2000
NOTE
The Web LCT also supports this task. The steps are similar to those on the U2000.
Context
The following procedure queries the status information about a 1+1 space diversity (SD)
protection group.
Procedure
Step 1
----End
Related References
A.5.6 Creating a PLA Group

When physical link aggregation (PLA) is required to improve Ethernet service bandwidth or
reliability on microwave links, you need to create a PLA group.
Issue 02 (2012-12-30)

436

A Task Collection
Prerequisites
l
No Ethernet service has been configured on the slave NE if a PLA group without NE-level
protection will be created.

U2000
Context
The following procedure creates a PLA group according to the planned parameter values listed
Parameter
Value
Protection Type
NE-level LAG protection
NE Role
Slave
IF Port
1-SHXA2-1 (IF)
Service Port
1-SHXA2-2 (GE1)
Cascade Port
1-SHXA2-3 (GE2)
Procedure
Step 1
----End
Related References
B.2.2 Parameter Description: PLA Group Creation
Issue 02 (2012-12-30)

437

A Task Collection
A.5.7 Querying the Status of a PLA Group

This section describes how to query the current information about a PLA group.
Prerequisites
l
A PLA group has been configured.

U2000
Context
The following procedure queries the current information of a PLA group.
Procedure
Step 1
----End
Related References
A.5.8 Configuring Ethernet Frame Header Compression and

Errored Frame Discarding Over Air Interfaces
You can configure the Ethernet header compression function and enable/disable the errored
frame discarding function by setting microwave port parameters.
Prerequisites
Issue 02 (2012-12-30)

438

A Task Collection

U2000
NOTE
Context
The following procedure configures a microwave port according to the planned parameter values
Parameter
Value
1SHXA21 (IF)
Speed Transmission at L2
Enabled
Speed Transmission at L3
Enabled
NOTE
If the Ethernet header compression function is enabled, set the preceding two parameters to Enabled to compress
Layer 2 headers and IP headers.
Procedure
Step 1
----End
A.5.9 Enabling the Notification of Radio Bandwidth

After the notification of radio bandwidth is enabled, the bandwidth information about a
microwave port can be transmitted to a connected ATN device through a GE port.
Issue 02 (2012-12-30)

439

A Task Collection
Prerequisites

U2000
Context
The following procedure enables the notification of radio bandwidth according to the planned
parameter value listed in the following table.
Parameter
Value
Microwave Capacity Report Port
1-SHXA2-2(GE1)
Procedure
Step 1
----End
A.5.10 Setting the Maximum Transmit Power and the Power

Thresholds
This section describes how to set the maximum transmit power and the power thresholds.
Prerequisites

U2000
Issue 02 (2012-12-30)

440

A Task Collection
Context
The following procedure sets the maximum transmit power to the planned value listed in the
following table for an NE.
NOTE
The method for setting power thresholds is the same as that for setting the maximum transmit power.
Parameter
Value
Maximum Transmit Power
17 dBm
Procedure
Step 1
----End
A.5.11 Querying the AM Status

This section describes how to query the adaptive modulation (AM) scheme changes and the
Ethernet bandwidth in the current modulation scheme.
Prerequisites

U2000
Context
The following procedure queries the AM scheme and the Ethernet bandwidth in the current
modulation scheme.
Issue 02 (2012-12-30)

441

A Task Collection
Procedure
Step 1
----End
A.5.12 Querying ATPC Adjustment Records

This section describes how to query automatic transmit power control (ATPC) adjustment
records.
Prerequisites

U2000
NOTE
Context
The following procedure queries ATPC adjustment records.
Procedure
Step 1
Issue 02 (2012-12-30)

442

A Task Collection
----End
A.5.13 Querying Historical Transmit Power and Receive Power

This section describes how to query the change trend of historical transmit power and receive
power, which serves as a reference for microwave link troubleshooting.
Prerequisites

U2000
NOTE
Context
The following procedure queries the change trend of historical transmit power and receive
power.
Procedure
Step 1
Issue 02 (2012-12-30)

443

A Task Collection
----End
A.5.14 Querying the SNR Value of a Microwave Link

This section describes how to query the change trend of the signal-to-noise ratio (SNR) value
of a microwave link, which serves as a reference for troubleshooting microwave link faults.
Prerequisites

U2000
NOTE
Context
The following procedure queries the change trend of the SNR value of a microwave link.
Procedure
Step 1
Issue 02 (2012-12-30)

444

A Task Collection
----End
A.6 Managing Ports

Setting port parameters correctly is the basis for configuring ports to carry services.
A.6.1 Setting Parameters for an Ethernet Port

Ethernet port parameters include basic attributes, traffic control, Layer 2 attributes, and advanced
attributes.
A.6.1.1 Setting the Basic Attributes for an Ethernet Port

The basic attributes of an Ethernet port define physical-layer information, such as the port mode,
encapsulation type, and maximum frame length.
Prerequisites

U2000
NOTE
The procedures performed on the Web LCT and U2000 are the same. In addition, the procedure performed on
the Web LCT can configure basic attributes for microwave ports.
Context
The following procedure configures the basic attributes for the port GE1 according to the planned
Issue 02 (2012-12-30)

445

Parameter
A Task Collection
Value
1SHXA22 (GE1)
Working Mode
1000M Full-Duplex
Logical Port Attribute
Optical Port
NOTE
For the port GE1, if Logical Port Attribute is set to Optical Port, the COMBO port is used for receiving
Ethernet services. If Logical Port Attribute is set to Electrical Port, the P&E port is used for receiving Ethernet
services.
Procedure
Step 1
----End
Related References
B.3.1.1 Parameter Description: Ethernet Interface_Basic Attributes
A.6.1.2 Configuring the Traffic Control Function for an Ethernet Port

After the traffic control function is enabled, an Ethernet port sends a pause frame to instruct the
peer end to stop sending Ethernet packets for a specific period of time if congestion occurs on
the link. Then the link congestion is eliminated.
Prerequisites

U2000
Issue 02 (2012-12-30)

446

A Task Collection
NOTE
Context
The following procedure configures the access control function for the port GE1 according to
Parameter
Value
1SHXA22 (GE1)
Auto-Negotiation Flow Control Mode
Enable Symmetric Flow Control
Non-Autonegotiation Flow Control Mode
Disabled
NOTE
Enable the flow control function for ports connected to external equipment only when the external equipment
uses the flow control function. Normally, the function is not required.
Procedure
Step 1
----End
Related References
B.3.1.2 Parameter Description: Ethernet Interface_Flow Control
A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port

Layer 2 attributes of Ethernet ports define tag attributes.
Issue 02 (2012-12-30)

447

A Task Collection
Prerequisites
l
Encapsulation Type is set to 802.1Q for an Ethernet port.

U2000
NOTE
the Web LCT can configure Layer 2 attributes for microwave ports.
Context
The following procedure configures the Layer 2 attributes for the port GE1 according to the
Parameter
Value
1SHXA22 (GE1)
Tag
Access
Default VLAN ID
100
VLAN Priority
NOTE
All tag attributes, except for the VLAN priority, can be configured during service configuration.
Procedure
Step 1
----End
Issue 02 (2012-12-30)

448

A Task Collection
Related References
B.3.1.3 Parameter Description: Ethernet Interface_Layer 2 Attributes
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port

You can configure MAC/PHY layer loopbacks, check the port rates, and configure loopback
detection and broadcast packet suppression functions by setting related Ethernet advanced
attributes.
Prerequisites

U2000
NOTE
the Web LCT can configure advanced attributes for microwave ports.
Context
The following procedure configures the advanced attributes for the port GE1 according to the
Parameter
Value
1SHXA22 (GE1)
Broadcast Packet Suppression
Enabled
Broadcast Packet Suppression Threshold
30%
NOTE
If the port is mounted with Ethernet local area network (E-LAN) services, enable the broadcast packet
suppression function for the port to suppress excessive packets in case of broadcast storms to E-LAN services.
It is recommended that you set the broadcast packet suppression threshold to the default value 30%.
Procedure
Step 1
Issue 02 (2012-12-30)

449

A Task Collection
----End
Related References
B.3.1.4 Parameter Description: Ethernet Interface_Advanced Attributes
A.6.1.5 Querying the Running Status of a Microwave Port

This section describes how to query the running status of a microwave port.
Prerequisites

U2000
Context
The following procedure queries the running status of a microwave port.
Procedure
Step 1
Issue 02 (2012-12-30)

450

A Task Collection
----End
A.6.2 Setting Parameters for a Microwave Port

The process of setting the basic attributes, Layer 2 attributes, and advanced attributes for a
microwave port is similar to that for an Ethernet port.
A.6.2.1 Setting Basic Attributes for a Microwave Port

The general attributes of microwave ports define the physical-layer information, such as the port
mode and encapsulation type.
Prerequisites

U2000
NOTE
A.6.1.1 Setting the Basic Attributes for an Ethernet Port shows how to set the basic attributes for a microwave
port on the Web LCT. The procedures in A.6.1.1 Setting the Basic Attributes for an Ethernet Port performed
on the Web LCT and U2000 are the same. In addition, the procedure performed on the Web LCT can configure
basic attributes for microwave ports.
Context
The following procedure configures the basic attributes for a microwave port according to the
Parameters
Value
1SHXA21(IF)
Encapsulation Type
Issue 02 (2012-12-30)
802.1Q

451

A Task Collection
Procedure
Step 1 Set the basic attributes for a microwave port.
----End
Related References
B.3.2.1 Parameter Description: Microwave Interface_Basic Attributes
A.6.2.2 Setting Layer 2 Attributes for a Microwave Port

The Layer 2 attributes of microwave ports define tag attributes.
Prerequisites
l
Encapsulation Type is set to 802.1Q for a microwave port.

U2000
NOTE
A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port shows how to set the Layer 2 attributes for a
microwave port on the Web LCT. The procedures in A.6.1.3 Setting the Layer 2 Attributes for an Ethernet
Port performed on the Web LCT and U2000 are the same. In addition, the procedure performed on the Web
LCT can configure Layer 2 attributes for microwave ports.
Context
The following procedure configures the Layer 2 attributes for a microwave port according to
Parameters
Value
1SHXA21(IF)
Tag
Issue 02 (2012-12-30)
Access
452

Parameters
A Task Collection
Value
1SHXA21(IF)
Default VLAN ID
100
VLAN Priority
NOTE
When services are configured on a per-NE basis, all tag attributes, except for the VLAN priorities, can be
configured during service configuration.
Procedure
Step 1
----End
Related References
B.3.2.2 Parameter Description: Microwave Interface_Layer 2 Attributes
A.6.2.3 Setting Advanced Attributes for a Microwave Port

The advanced attributes of microwave ports are for querying the port traffic rate, configuring
loop detection, and configuring broadcast packet suppression.
Prerequisites

U2000
Issue 02 (2012-12-30)

453

A Task Collection
NOTE
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port shows how to set the advanced attributes for
a microwave port on the Web LCT. The procedures in A.6.1.4 Setting the Advanced Attributes for an
Ethernet Port performed on the Web LCT and U2000 are the same. In addition, the procedure performed on
the Web LCT can configure advanced attributes for microwave ports.
Context
The following procedure configures the advanced attributes for a microwave port according to
Parameters
Value
1SHXA21(IF)
Broadcast Packet Suppression
Enabled
Broadcast Packet Suppression Threshold
30%
NOTE
If the port is mounted with Ethernet local area network (E-LAN) services, enable the broadcast packet
suppression function for the port to suppress excessive broadcast packets in an E-LAN service broadcast storm.
It is recommended that you set the broadcast packet suppression threshold to the default value 30%.
Procedure
Step 1
----End
Related References
B.3.2.3 Parameter Description: Microwave Interface_Advanced Attributes
A.6.2.4 Querying the Running Status of an Ethernet Port

This section describes how to query the running status of an Ethernet port.
Issue 02 (2012-12-30)

454

A Task Collection
Prerequisites

U2000
Context
The following procedure queries the running status of an Ethernet port.
Procedure
Step 1
----End
A.7 Managing Ethernet Services and Features

Configurations of Ethernet services and features on the packet plane include Ethernet port,
protection, service, protocol, and OAM configurations.
A.7.1 Managing ERPS

For an FE/GE ring network or a hybrid network, Ethernet ring protection switching (ERPS) can
be configured to protect Ethernet services.
A.7.1.1 Creating an ERP Instance

Ethernet ring protection switching (ERPS) is configured by creating ERP instances.
Prerequisites
Issue 02 (2012-12-30)

455

A Task Collection

U2000
NOTE
Context
The following procedure creates an ERP instance according to the planned parameter values
Parameter
Value
ERPS ID
East Port
1-SHXA2-1(IF)
West Port
1-SHXA2-2(GE1)
RPL Owner Ring Node Flag
Yes
RPL Port
1-SHXA2-1(IF)
Control VLAN
100
Procedure
Step 1
----End
Related References
B.4.2.1 Parameter Description: ERPS Management
Issue 02 (2012-12-30)

456

A Task Collection
A.7.1.2 Setting ERPS Protocol Parameters

The Ethernet ring protection switching (ERPS) protocol parameters to be set include the holdoff time, wait to restore (WTR) time, and guard time.
Prerequisites
l
An Ethernet ring protection (ERP) instance has been created.

U2000
NOTE
Context
The following procedure configures ERPS protocol parameters according to the planned
Parameter
Value
WTR Time (min)
10
Set the parameters according to the network plan. Default values are recommended.
Procedure
Step 1
----End
Related References
Issue 02 (2012-12-30)

457

A Task Collection
A.7.1.3 Querying the ERPS Status

By performing this task, you can query the Ethernet ring protection switching (ERPS) status.
Prerequisites

U2000
NOTE
Context
The following procedure queries the ERPS status.
Procedure
Step 1
----End
Related References
A.7.2 Managing LAGs

Link aggregation allows one or multiple links that are connected to the same equipment to be
aggregated to form a link aggregation group (LAG). For MAC users, a LAG works as a single
link. In this manner, the link bandwidth and availability are improved.

If the bandwidth or availability of the Ethernet link between two NEs needs to be improved,
create a link aggregation group (LAG).
Issue 02 (2012-12-30)

458

A Task Collection
Prerequisites

U2000
NOTE
Context
l
Issue 02 (2012-12-30)
Creates a non-load sharing LAG to protect the Ethernet link from a UNI-side equipment
to an NE, according to the planned parameter values listed in the following table.
Parameter
NE
LAG No.
LAG Name
LAG_01
LAG Type
Load Sharing
Non-Sharing
LAG Priority
Long period
Main Ports
1-SHXA2-3 (GE2)
Standby Ports
1-SHXA2-2 (GE1)
Creates a load-sharing LAG to increase the Ethernet bandwidth for a link between air
interfaces, according to the planned parameter values listed in the following table.
Parameter
NE
LAG No.
LAG Name
LAG_02
LAG Type
Load Sharing
Sharing
LAG Priority
Long period
Main Ports
1-SHXA2-1 (IF)

459

A Task Collection
Parameter
NE
Standby Ports
1-SHXA2-2 (GE1)
Switch LAG upon Air Interface SD
Enabled
Create a LAG for configuring 1+1 or PLA protection according to the planned parameter
Parameter
NE
LAG No.
Assign Automatically (default value).
LAG type
Load sharing type
Non-load sharing (default value)
LAG priority
Main port
1-SHXA2-2 (GE1)
Procedure
Step 1 Create a non-load sharing LAG.
Step 2 Create a load-sharing LAG.
Issue 02 (2012-12-30)

460

A Task Collection
Step 3 Create a LAG for configuring 1+1 or PLA protection with NE-level protection.
----End
Related References
B.4.2.2 Parameter Description: Ethernet Link Aggregation Management
A.7.2.2 Setting Parameters for a LAG

Link aggregation group (LAG) parameters include port priority and load-sharing algorithm.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

461

A Task Collection
Context
The following procedure sets LAG parameters according to the planned parameter values listed
Parameter
Value
Port Priority
System Load Sharing Hash Algorithm
Source and Destination MACs
Procedure
Step 1
----End
Related References
B.4.2.3 Parameter Description: Ethernet Link Aggregation_Link Aggregation
A.7.2.3 Querying the Protocol Information About a LAG

By performing this task, you can learn about the running information of the Link Aggregation
Control Protocol (LACP) used for a link aggregation group (LAG).
Prerequisites
l
A LAG has been created.

U2000
NOTE
Issue 02 (2012-12-30)

462

A Task Collection
Context
The following procedure queries the LACP information about a LAG.
Procedure
Step 1
----End
A.7.3 Configuring Ethernet Services

Ethernet services are classified into two types: Ethernet line (E-Line) service and Ethernet local
area network (E-LAN) service.
A.7.3.1 Creating a Point-to-Point Transparently Transmitted E-Line Service

By creating point-to-point transparently transmitted Ethernet line (E-Line) services, you can
transparently transmit all packets received at the source to the sink.
Prerequisites
l
The service to be created does not conflict with existing services.

U2000
NOTE
Precautions
In point-to-point transparently transmitted E-Line services, Layer 2 protocol packets are
transmitted as common services. Therefore, Layer 2 protocol packets cannot be transmitted first
in the case of link congestion.
Issue 02 (2012-12-30)

463

A Task Collection
Context
The following procedure creates the point-to-point transparently transmitted E-Line service
shown in the following figure.
GE1
(Auto-Negotiation)
E-Line
IF
GE2
Procedure
Step 1
----End
Related References
B.4.1.1 Parameter Description: E-Line Service
A.7.3.2 Creating a VLAN-based E-Line Service

By creating VLAN-based Ethernet line (E-Line) services, you can transmit service packets from
the source to a sink based on the VLAN IDs carried by the packets. Layer 2 protocol packets
cannot be transmitted as VLAN-based E-Line services.
Prerequisites
l

U2000
Issue 02 (2012-12-30)

464

A Task Collection
NOTE
Precautions
Layer 2 protocol packets cannot be transmitted as VLAN-based E-Line services. See A.7.3.3
Creating an E-Line Service for Transmitting Layer 2 Protocol Packets to perform necessary
operations if Layer 2 protocol packets need to be transparently transmitted.
Context
The following procedure creates the VLAN-based E-Line service shown in the following figure.
GE1
(Auto-Negotiation)
VLAN ID=100
E-Line
IF
VLAN ID=100
GE2
Procedure
Step 1
----End
Related References
A.7.3.3 Creating an E-Line Service for Transmitting Layer 2 Protocol Packets

An Ethernet line (E-Line) service can be created for transmitting Layer 2 protocol packets from
the source to the sink as packets with a per-hop behavior (PHB) of CS7.
Issue 02 (2012-12-30)

465

A Task Collection
Prerequisites
l

U2000
NOTE
Context
The following procedure creates the E-Line service shown in the following figure for
transmitting Link Aggregation Control Protocol (LACP) packets.
GE1
LACP packet
E-Line
IF
LACP packet
GE2
Procedure
Step 1
----End
Related References
Issue 02 (2012-12-30)

466

A Task Collection
A.7.3.4 Creating VLAN Forwarding Table Entries

VLAN forwarding table entries enable VLAN ID switching at the source or sink end of an
Ethernet line (E-Line) service.
Prerequisites
l
An E-Line service has been configured.

U2000
NOTE
Context
The following procedure configures a VLAN forwarding table to implement VLAN switching
for an E-Line service.
GE1
VLAN ID=100
E-Line
IF
VLAN ID=200
GE2
E-Line Service Information Table

Source
Interface
Source
VLAN ID
GE1
100
Sink
Sink
Interface VLAN ID
IF
200
VLAN Forwarding Table

Source
Interface
GE1
Source
VLAN ID
100
IF
200
Sink
Sink
Interface VLAN ID
IF
200
GE1
100
NOTE
A VLAN forwarding table entry implements only unidirectional VLAN switching. For bidirectional VLAN
switching, you must configure two VLAN forwarding table entries.
Procedure
Step 1
Issue 02 (2012-12-30)

467

A Task Collection
----End
Related References
A.7.3.5 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
l

U2000
NOTE
Precautions
l
In IEEE 802.1D bridge-based Ethernet local area network (E-LAN) services, Layer 2
protocol packets are transmitted as common services. Therefore, Layer 2 protocol packets
cannot be transmitted first in the case of link congestion.
By default, the NE carries an IEEE 802.1D bridge-based E-LAN service that is mounted
to all three ports of the NE.
Context
The following procedure creates the IEEE 802.1D bridge-based E-LAN service shown in the
following figure.
Issue 02 (2012-12-30)

468

A Task Collection
GE1
(Auto-Negotiation)
IF
GE2
(Auto-Negotiation)
Bridge
Procedure
Step 1
----End
Related References
B.4.1.2 Parameter Description: E-LAN Service
A.7.3.6 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
l

U2000
NOTE
Issue 02 (2012-12-30)

469

A Task Collection
Precautions
IEEE 802.1Q bridge-based Ethernet local area network (E-LAN) services can be configured to
transparently transmit Layer 2 protocol packets as packets with a per-hop behavior (PHB) of
CS7.
Context
The following procedure creates the IEEE 802.1Q bridge-based E-LAN service shown in the
following figure.
GE1
(Auto-Negotiation)
VLAN ID=100
IF
VLAN ID=100,200
GE2
(Auto-Negotiation)
VLAN ID=200
Bridge
Procedure
Step 1
----End
Related References
A.7.3.7 Creating an E-LAN Service for Transmitting Layer 2 Protocol Packets

An Ethernet local area network (E-LAN) service can be created for transmitting Layer 2 protocol
packets from the source to the sink as packets with a per-hop behavior (PHB) of CS7.
Issue 02 (2012-12-30)

470

A Task Collection
Prerequisites
l
An IEEE 802.1Q bridge-based E-LAN service has been created.

U2000
NOTE
Context
The following procedure creates an E-LAN service for transmitting Link Aggregation Control
Protocol (LACP) packets shown in the following figure.
GE1
LACP packet
E-LAN
IF
LACP packet
GE2
NOTE
The port used to transmit the E-LAN service carrying LACP packets must be the same as the port that is used
to transmit the IEEE 802.1Q bridge-based E-LAN service.
Procedure
Step 1
----End
Related References
Issue 02 (2012-12-30)

471

A Task Collection
A.7.3.8 Configuring a Split Horizon Group

Ports mounted to the same split horizon group cannot forward packets to one another.
Prerequisites
l
Ethernet local area network (E-LAN) services have been configured.

U2000
NOTE
Context
The following procedure creates a split horizon group for the E-LAN services shown in the
following figure, so that the ports GE1 and GE2 cannot forward packets to each other.
GE1
(Auto-Negotiation)
IF
GE2
(Auto-Negotiation)
Bridge
Split horizon group
Procedure
Step 1
----End
Issue 02 (2012-12-30)

472

A Task Collection
Related References
A.7.3.9 Changing Logical Ports Mounted to a Bridge

This section describes how to change the logical ports mounted to a bridge and how to modify
the attributes of the ports.
Prerequisites
l

U2000
NOTE
Context
The following procedure deletes the port GE2 to which the E-LAN services are mounted and
removes VLAN 200 from the VLAN list of the microwave port.
Procedure
Step 1
----End
A.7.3.10 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.
Issue 02 (2012-12-30)

473

A Task Collection
Prerequisites
l
An E-Line service has been configured.

U2000
NOTE
Context
The following procedure deletes the E-Line service whose ID is 1.
Procedure
Step 1
----End
A.7.3.11 Deleting an E-LAN Service

When an Ethernet local area network (E-LAN) service is not used, you need to delete the service
to release Ethernet resources.
Prerequisites
l
An E-LAN service has been configured.

U2000
NOTE
Issue 02 (2012-12-30)

474

A Task Collection
Context
The following procedure deletes the E-LAN service whose ID is 1.
Procedure
Step 1
----End
A.7.4 Managing MAC Address Tables

A MAC address table is the core of an Ethernet local area network (E-LAN) service. OptiX RTN
310 provides various functions for managing MAC address tables.
A.7.4.1 Creating a Static MAC Address Entry

By creating static MAC address entries, you can ensure that hosts with specific MAC addresses
are not affected after the MAC addresses are aged out. In addition, static MAC address entries
ensure that Ethernet local area network (E-LAN) services are applicable to hosts that receive
but not transmit packets.
Prerequisites
l
E-LAN services have been configured.

U2000
NOTE
Context
The following procedure adds the MAC address listed in the following table into the static MAC
address table for an E-LAN service.
Issue 02 (2012-12-30)

475

A Task Collection
Parameter
Value
VLAN ID
100
MAC Address
000909095801
Egress Interface
GE1
Procedure
Step 1
----End
Related References
A.7.4.2 Creating a Blacklist MAC Address Entry

This section describes how to prevent NEs with specific MAC addresses from receiving/
transmitting Ethernet local area network (E-LAN) services by creating blacklist MAC address
entries.
Prerequisites
l

U2000
NOTE
Issue 02 (2012-12-30)

476

A Task Collection
Context
The following procedure blacklists the MAC address listed in the following table for an E-LAN
service.
Parameter
Value
VLAN ID
100
MAC Address
000809095707
Procedure
Step 1
----End
Related References
A.7.4.3 Managing a Dynamic MAC Address Table

By performing this task, you can set aging parameters, or query or clear entries in a dynamic
MAC address table.
Prerequisites
l

U2000
NOTE
Issue 02 (2012-12-30)

477

A Task Collection
Context
The following procedure sets the aging time to 10 minutes for a dynamic MAC address entry.
Procedure
Step 1
----End
Related References
A.7.5 Setting the Mode for Processing an Unknown Frame of an ELAN Service
An unknown frame refers to either a unicast frame whose destination MAC address is not in the
MAC address table or a multicast frame whose MAC address is not in a multicast group. By
default, an NE broadcast an unknown frame. By performing this task, you can change the
processing mode to discarding.
Prerequisites
l

U2000
NOTE
Context
The following procedure changes the processing mode for unknown frames to Discarding.
Issue 02 (2012-12-30)

478

A Task Collection
NOTE
In practice, it is recommended that you do not change the processing mode for unknown frames.
Procedure
Step 1
----End
Related References
A.7.6 Managing QoS

By managing QoS, you can provide different service levels for different service types.
A.7.6.1 Modifying the Mapping for a DS Domain

This section describes how to modify the mapping between packet priorities and per-hop
behaviors (PHBs) in the ingress or egress direction of a Differentiated Services (DS) domain.
Prerequisites

U2000
NOTE
Context
The following procedure changes the mapping for a DS domain according to the planned
parameter values listed in the following tables.
The following table provides the values of the parameters on the Ingress tab page.
Issue 02 (2012-12-30)

479

A Task Collection
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7
The following table provides the values of the parameters on the Egress tab page.
Issue 02 (2012-12-30)
CVLAN
MPLS EXP
IP DSCP
PHB
Default value
Default value
BE
12
AF11
AF13
20
AF21
16
AF23
28
AF31
24
AF33
36
AF41
32
AF43
40
EF
48
CS6
56
CS7

480

A Task Collection
Procedure
Step 1
----End
Related References
B.4.4 Parameter Description: QoS Management
A.7.6.2 Changing the Packet Type Trusted by a Port

This section describes how to set the packet type trusted by a port.
Prerequisites

U2000
NOTE
Context
The following procedure changes the packet types trusted by the Ethernet ports and microwave
port to the planned value listed in the following table.
Parameter
Packet Type
GE1
ip-dscp
GE2
IF
Issue 02 (2012-12-30)

481

A Task Collection
Procedure
Step 1
----End
Related References
A.7.6.3 Configuring Port Shaping

This section describes how to configure traffic shaping for an egress port.
Prerequisites

U2000
NOTE
Context
The following procedure configures port shaping for the Ethernet port GE1 according to the
Issue 02 (2012-12-30)
Parameter
Value
Bandwidth Limit
Enabled
PIR (kbit/s)
512
PBS (kbit/s)
512

482

A Task Collection
Procedure
Step 1
----End
Related References
A.7.6.4 Setting Egress Queue Scheduling Policies

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

U2000
NOTE
Context
The following procedure configures queue scheduling policies for a microwave port according
Issue 02 (2012-12-30)
Parameter
Grooming Policy After Reloading
CS7
SP (default value)
CS6
SP (default value)
EF
SP (default value)
AF4
SP
483

A Task Collection
Parameter
Grooming Policy After Reloading
AF3
SP
AF2
SP
AF1
SP
BE
SP (default value)
Procedure
Step 1
----End
Related References
A.7.6.5 Setting Traffic Shaping for Egress Queues

This section describes how to set traffic shaping for an egress queue.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

484

A Task Collection
Context
The following procedure sets traffic shaping for an egress queue (AF4) at a microwave port
Parameter
Value
Bandwidth Limit
Enabled
PIR (kbit/s)
512
PBS (kbit/s)
512
Procedure
Step 1
----End
Related References
A.7.6.6 Setting the Congestion Management Mode for Egress Queues

This section describes how to set the congestion management mode for an egress queue.
Prerequisites

U2000
NOTE
Issue 02 (2012-12-30)

485

A Task Collection
Context
The following procedure sets the congestion management mode for an egress queue at a
microwave port according to the planned parameter values listed in the following table.
Paramete
r
Congesti
on
Manage
ment
Mode
WRED Configuration
ID
Name
Upper
Threshol
d (Bytes)
Lower
Threshol
d (Bytes)
Discard
Ratio (%)
CS7
Tail drop
(default)
WRED
Autoassign
WRED1
64 (green)
42 (green)
42 (red)
21 (red)
100
(default
value)
CS6
EF
AF4
AF2
AF1
BE
AF3
Procedure
Step 1
----End
Related References
Issue 02 (2012-12-30)

486

A Task Collection
A.7.7 Using Ethernet Service OAM

By using Ethernet service OAM, you can maintain Ethernet services in an end-to-end manner.
A.7.7.1 Creating an MD
A maintenance domain (MD) defines the Ethernet OAM range and level. MDs of different ranges
and levels can provide users with differentiated OAM services.
Prerequisites

U2000
NOTE
Context
The following procedure creates a maintenance domain according to the planned parameter
Parameter
Value
MD1
Maintenance Domain Level
Procedure
Step 1
----End
Issue 02 (2012-12-30)

487

A Task Collection
Related References
B.4.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain
Creation
A.7.7.2 Creating an MA
A maintenance domain (MD) can be divided into several independent maintenance associations
(MAs). By creating MAs, you can associate specific Ethernet services with MAs. This facilitates
Ethernet OAM operations.
Prerequisites
l
An MD has been created.
An Ethernet service has been created.

U2000
NOTE
Context
The following procedure creates an MA according to the planned parameter values listed in the
following table.
Parameter
Value
default
MA1
Relevant Service
auto_configuration
1s
Procedure
Step 1
Issue 02 (2012-12-30)

488

A Task Collection
----End
Related References
B.4.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association
Creation
A.7.7.3 Creating an MEP

Maintenance association end points (MEPs) initiate or terminate Ethernet OAM packets. After
creating MEPs, you can check the Ethernet link between MEPs in the same maintenance
association (MA) by performing OAM operations.
Prerequisites
l
An MA has been created.

U2000
NOTE
Context
The following procedure creates an MEP for the Ethernet port GE1 according to the planned
Issue 02 (2012-12-30)
Parameter
Value
default
MA1
Port
1-SHXA2-2(GE1)
489

A Task Collection
Parameter
Value
VLAN
100
MP ID
Direction
Ingress
CC Status
Active
Procedure
Step 1
----End
Related References
B.4.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation
A.7.7.4 Creating a Remote MEP in an MA

To ensure that a maintenance association end point (MEP) can respond to the OAM operations
initiated by the other MEPs in the same maintenance association (MA), you must configure the
other MEPs to be the remote MEPs of this MEP.
Prerequisites
l
An MA has been created.

U2000
NOTE
Issue 02 (2012-12-30)

490

A Task Collection
Context
The following procedure creates a remote MEP according to the planned parameter values listed
Parameter
Value
default
MA1
Remote Maintenance Point ID
Procedure
Step 1
----End
Related References
B.4.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation
A.7.7.5 Creating an MIP

Maintenance association intermediate points (MIPs) can respond to specific OAM packets. By
creating MIPs, you can divide the Ethernet link between two MEPs in the same maintenance
association (MA) into several segments, therefore facilitating the Ethernet link checking.
Prerequisites
l
A maintenance domain (MD) has been created.

U2000
Issue 02 (2012-12-30)

491

A Task Collection
NOTE
Context
The following procedure creates an MIP for the Ethernet port GE2 according to the planned
Parameter
Value
default
Port
1-SHXA2-3(GE2)
MP ID
Procedure
Step 1
----End
Related References
B.4.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation
A.7.7.6 Performing a CC Test

A continuity check (CC) test checks the status of a unidirectional link automatically and
periodically. If a CC test started at the source end finds that the link is faulty, the sink reports
the corresponding alarm.
Prerequisites
l
Issue 02 (2012-12-30)

492

A Task Collection
The source and sink maintenance association end points (MEPs) in the same maintenance
associations have been created.
The remote MEPs have been created.

U2000
NOTE
Precautions
l
Only an MEP can start a CC test and function as the receive or respond end in the test.
During a CC check, the source MEP constructs and transmits continuity check message
(CCM) packets periodically. After receiving the CCM packets from the source MEP, the
sink MEP directly enables the CC function. If the sink MEP fails to receive the CCM packets
from the source MEP within the specified period (3.5 times the transmission interval), it
reports an alarm automatically.
A CC test does not affect services.
Context
The following procedure enables a CC test.
Procedure
Step 1
----End
A.7.7.7 Performing an LB Test

A loopback (LB) test enables you to check the bidirectional connectivity between the source
and sink maintenance association end points (MEPs) in the same maintenance association (MA).
Issue 02 (2012-12-30)

493

A Task Collection
Prerequisites
l
The source and sink MEPs in the same maintenance associations have been created.
The continuity check (CC) function has been enabled.

U2000
NOTE
Precautions
l
Only an MEP can initiate an LB test and function as the receive end in the test.
During an LB test, the source MEP constructs and transmits loopback message (LBM)
frames and starts the timer. If the sink MEP receives the LBM frames, it sends loopback
reply (LBR) frames back to the source MEP. This indicates that the loopback is successful.
If the source MEP timer expires, the loopback has failed.
An LB test does not affect services.
Context
The following procedure enables an LB test according to the planned parameter values listed in
Parameter
Value
default
MA1
Source Maintenance ID
Destination Maintenance ID
Procedure
Step 1
Issue 02 (2012-12-30)

494

A Task Collection
----End
Related References
B.4.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling
A.7.7.8 Performing an LT Test

Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate
faults. A faulty network segment can be located based on maintenance association intermediate
points (MIPs) through only one test.
Prerequisites
l
association (MA) have been created.
The continuity check (CC) function has been enabled.

U2000
NOTE
Precautions
l
Only an MEP can initiate an LT test and work as the receive end in the test.
During an LT test, the source MEP constructs and transmits link trace message (LTM)
frames and starts the timer. All the MPs that receive the LTM frames respond with link
trace reply (LTR) frames. According to the LTR frames, you can determine all the MIPs
long the path from the source MEP to the sink MEP.
An LT test does not affect services.
Issue 02 (2012-12-30)

495

A Task Collection
Context
The following procedure enables an LT test according to the planned parameter values listed in
Parameter
Value
default
MA1
Source Maintenance ID
Destination Maintenance ID
Procedure
Step 1
----End
Related References
B.4.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling
A.7.7.9 Activating the AIS

After a fault is detected by a maintenance point (MP) on which the alarm indication signal (AIS)
function is activated, the MP sends an AIS packet to inform a higher-level MP of the fault
information.
Prerequisites
l
domain (MD) have been created.
Issue 02 (2012-12-30)

496

A Task Collection

U2000
NOTE
Context
The following procedure activates the AIS function.
Procedure
Step 1
----End
A.7.7.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet

Services
The ETH OAM function allows you to monitor packet loss ratio, delay, or delay variation of
Ethernet services without any impact on the Ethernet services.
Prerequisites
l
Native Ethernet line (E-Line) services that are transmitted based on ports and VLAN IDs
have been created.
The source and sink maintenance end points (MEPs) in the same maintenance domain (MD)
have been created.

U2000
NOTE
Issue 02 (2012-12-30)

497

A Task Collection
Precautions
OptiX RTN 310 uses the remote network monitoring (RMON) function to collect statistics about
packet loss ratio, delay, or delay variation of Ethernet services.
Context
l
Monitors the real-time performance statistics of Ethernet ports.
Monitors the 30-minute historical performance statistics of Ethernet ports.
Procedure
Step 1 Monitor the current packet loss ratio, delay, or delay variation.
Step 2 Monitor the historical packet loss ratio, delay, or delay variation.
----End
Issue 02 (2012-12-30)

498

A Task Collection
A.7.7.11 Performing E-LAN Service Loopback Detection

This section describes how to configure automatic detection of Ethernet local area network (ELAN) service loopbacks and automatic service disabling.
Prerequisites
l
E-LAN services have been created.

U2000
Context
l
Creation of MEPs is not a prerequisite for service loopback detection.
Service loopback detection and STP/RSTP are mutually exclusive (STP is short for
Spanning Tree Protocol, and RSTP for Rapid Spanning Tree Protocol).
NOTE
During an E-LAN service loopback test, if a node on the network to which the test port is connected reports a
loopback packet threshold-crossing event, there is an E-LAN service loop on this node.
The following procedure performs E-LAN service loopback detection and disables services
automatically in the case of an E-LAN service loopback.
Parameter
Value
VLAN/CVLAN
NULL
Packet Timeout Period(s)
Disable Service When Loopback Is Detected
Yes
Procedure
Step 1
Issue 02 (2012-12-30)

499

A Task Collection
----End
Related References
B.4.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback Detection
A.7.7.12 Reactivating an E-LAN Service

This section describes how to reactivate Ethernet local area network (E-LAN) services that are
deactivated during a service loopback detection process.
Prerequisites
l
An E-LAN service port has been disabled due to a service loopback.

U2000
Context
The following procedure reactivates an E-LAN service.
Procedure
Step 1
Issue 02 (2012-12-30)

500

A Task Collection
----End
A.7.8 Using Ethernet Port OAM

By using Ethernet port OAM, you can maintain point-to-point Ethernet links.
A.7.8.1 Enabling OAM Auto-discovery

IEEE 802.3ah OAM is implemented based on OAM auto-discovery. After the OAM autodiscovery operation is successful, the equipment automatically monitors the fault and
performance of the link.
Prerequisites

U2000
NOTE
Precautions
OAM auto-discovery is implemented based on the auto-negotiation between the local equipment
and the peer equipment. If the negotiation fails, the local equipment reports an alarm. After OAM
auto-discovery is successfully completed, the link performance is monitored according to the
errored frame threshold. You can set the errored frame threshold on the network management
system (NMS).
Context
The following procedure enables the OAM auto-discovery function according to the planned
Issue 02 (2012-12-30)

501

A Task Collection
Parameter
Value
Port
1-SHXA2-1(IF-1)
OAM Working Mode
Active (default value)
Enable OAM Protocol
Enabled
Procedure
Step 1
----End
Related References
B.4.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter
A.7.8.2 Enabling the Link Event Notification

After the link event notification is enabled on the local equipment, the peer equipment is
informed if OAM detects a link fault or a link performance event.
Prerequisites
l
The OAM auto-discovery operation has been performed successfully on the equipment at
both ends.

U2000
NOTE
Issue 02 (2012-12-30)

502

A Task Collection
Context
The following procedure enables the link event notification function for a microwave port.
Procedure
Step 1
----End
Related References
A.7.8.3 Changing the OAM Errored Frame Monitoring Threshold

Set the OAM errored frame monitoring threshold, so OAM checks link performance based on
this threshold. Generally, the default value is used. You can change the value based on link
conditions.
Prerequisites
l
The IEEE 802.3ah OAM function has been enabled on the peer equipment. The OAM autodiscovery operation has been performed successfully on the equipment at both ends.

U2000
NOTE
Precautions
After the OAM auto-discovery operation is successful, the remote link event notification
function is enabled and the monitoring time and errored frame threshold are set at the local end.
If the local equipment detects a link event in the receive direction, it informs the peer equipment
Issue 02 (2012-12-30)

503

A Task Collection
of the link event. If the remote alarm for the link event is also supported at the peer end, the peer
equipment can inform the local equipment of the link event it has detected. Then, the
corresponding alarm is reported at the local end.
Context
The following procedure modifies Error Frame Period Window of the port GE1 to the planned
value listed in the following table.
Parameter
Value
Error Frame Monitor Window(ms)
Error Frame Monitor Threshold(frames)
1 (default value)
Error Frame Period Window(frame)
8928000
Error Frame Period Threshold(frames)
1 (default value)
Error Frame Second Window(s)
60 (default value)
Error Frame Second Threshold(s)
1 (default value)
Procedure
Step 1
----End
Related References
B.4.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame
Monitoring
A.7.8.4 Performing a Remote Loopback

After the Ethernet port on the local equipment sends data to the port on the interconnected
equipment, the local end can request the peer end to return the data.
Issue 02 (2012-12-30)

504

A Task Collection
Prerequisites
l
The OAM auto-discovery operation has been performed successfully at both ends of the
link.
OAM Working Mode is set to Active on the equipment that has initiated the loopback.
The equipment that responds to the loopback supports the remote loopback.

U2000
NOTE
Precautions
l
If a port is capable of responding to loopbacks, it enters the loopback responding state and
reports a loopback responding alarm after receiving the command of enabling the remote
loopback function sent from the peer OAM port. The equipment that initiates the loopback
enters the loopback initiation state and reports a loopback initiation alarm.
Generally, after the remote loopback function is enabled, service packets, except for
OAMPDU packets and data communication network (DCN) packets, are looped back at
the peer end.
After using the remote loopback function to locate a fault and test link performance, you
must disable the remote loopback function at the end where the loopback is initiated, and
then restore services. The alarm is automatically cleared.
Context
The following procedure performs a remote loopback on a microwave port.
Procedure
Step 1
----End
Issue 02 (2012-12-30)

505

A Task Collection
Related References
A.7.8.5 Enabling Self-loop Detection

After enabling self-loop detection on an Ethernet port, you can check the loopback of the port
and the loopback between the port and other Ethernet ports.
Prerequisites
l
All the external physical ports have been enabled.

U2000
NOTE
Context
The following procedure enables the self-loop detection function for the Ethernet port GE1.
Procedure
Step 1
----End
Related References
Issue 02 (2012-12-30)

506

A Task Collection
A.7.9 Configuring LPT

After link-state pass through (LPT) is configured, Ethernet ports correlated with microwave
links can be disabled automatically in the case of a microwave link fault. OptiX RTN 310
supports simplified LPT.
Prerequisites

U2000
Context
The following procedure configures LPT according to the planned parameter values listed in the
following table.
Parameter
Value
Convergence Port
1-SHXA2-1 (IF)
Access Port
1-SHXA2-2 (GE1)
Procedure
Step 1
----End
Related References
B.4.2.4 Parameter Description: Simplified LPT Creation
Issue 02 (2012-12-30)

507

A Task Collection
A.8 Managing Clocks

To ensure clock synchronization between transmission nodes on a transport network, you need
to manage the NE clocks.
A.8.1 Managing Clocks at the Physical Layer

This section describes how to synchronize clock signals by transmitting reference clock signals
at the physical layer.
A.8.1.1 Changing the Clock Control Mode

You can change the clock control mode as desired when configuring a physical link aggregation
(PLA) group.
Prerequisites

U2000
Precautions
l
The clock control mode is fixed to Standalone when you are not configuring 1+1 protection
and PLA.
The clock control mode is fixed to Centralized when you are configuring 1+1 protection.
The clock control mode is default to Standalone when a PLA is being configured. You
can change it to Centralized.
Context
The following procedure changes the clock control mode according to the planned parameter
value listed in the following table.
Parameter
Value
Clock Control Mode
Centralized
NOTE
l In standalone mode, NEs trace and switch clock sources based on the clock configuration on each NE.
l In centralized mode, the current standby NE is fixed to trace the clock of the current main NE through
a cascade port.
l For PLA, the clock control mode needs to be changed only when the cascade ports are GE electrical
ports, in order to prevent impact on services during clock switching.
Issue 02 (2012-12-30)

508

A Task Collection
Procedure
Step 1
----End
A.8.1.2 Configuring Clock Sources

This section describes how to configure clock sources according to the planned clock
synchronization scheme so that all the NEs on the network trace the same clock.
Prerequisites

U2000
NOTE
Context
The following procedure configures a microwave port and the port GE1 as clock sources. The
priority of the clock source at the microwave port is higher than that at the port GE1.
Procedure
Step 1
Step 2
Issue 02 (2012-12-30)

509

A Task Collection
----End
Related References
B.6.1.2 Parameter Description: Clock Source Priority Table
A.8.1.3 Configuring Protection for Clock Sources

This section describes how to configure protection for clock sources. For a simple network (such
as a chain network), protection for the clock sources is not required or the clock sources are
protected according to the clock source priority table. For a complex network (such as a ring
network, a ring with chain network, or a network consisting of intersectant rings), clock sources
need to be protected by using the standard Synchronization Status Message (SSM) protocol or
the extended SSM protocol.
Prerequisites
l
Clock sources have been configured.

U2000
NOTE
Context
l
Enables the standard SSM protocol.
Enables the extended SSM protocol and sets the IDs of the clock source GE1 and the internal
clock source to 1 and 2 respectively.
Issue 02 (2012-12-30)

510

A Task Collection
NOTE
l It is recommended that you enable the standard SSM protocol for a simple ring network and enable the
extended SSM protocol for a complex network (for example, a network consisting of intersectant rings,
which may provide the network with multiple clock sources).
l If the extended SSM protocol is enabled, set IDs for the following clock sources:
l Reference clock sources for a ring network
l Local clock source of an NE that traces a clock source outside the ring network
Each clock source ID must be unique and is unrelated to priorities.
Procedure
Step 1 Enable the standard SSM protocol.
Step 2 Enable the extended SSM protocol.
----End
Related References
B.6.1.5 Parameter Description: Clock Subnet Setting_Clock Subnet
Issue 02 (2012-12-30)

511

A Task Collection
A.8.1.4 Customizing the Clock Quality

By default, an NE determines the quality of a clock based on the clock quality information
extracted from the clock source. If the clock quality is 0 (indicating that the synchronization
quality is unknown), the clock source is unavailable. If required, you can customize the clock
quality of all clock sources and the clock quality level of the clock source whose clock quality
is 0.
Prerequisites
l
Clock sources have been configured.

U2000
NOTE
Context
The following procedure sets the clock quality of the clock source at the port GE1 to G.811.
NOTE
If an NE cannot extract the clock quality of a clock source for a ring network (for example, if an NE provides
a synchronous Ethernet clock source for the ring network but cannot transmit the clock quality information
through SSMs), define the clock quality manually.
Procedure
Step 1
----End
Related References
B.6.1.6 Parameter Description: Clock Subnet Setting_Clock Quality
Issue 02 (2012-12-30)

512

A Task Collection
A.8.1.5 Enabling/Disabling SSM Transmission

After the standard Synchronization Status Message (SSM) protocol or the extended SSM
protocol is enabled for an NE, the NE sends SSMs to the other NEs in the same clock subnet
through all microwave links or Ethernet links. To prevent interference between two different
clock subnets, the NE must be disabled from sending SSMs to links connected to another clock
subnet.
Prerequisites

U2000
NOTE
Context
The following procedure disables the port GE1 from transmitting SSMs.
NOTE
For a port connected to another clock subnet on which the SSM protocol is enabled, disable the port from
transmitting SSMs.
Procedure
Step 1
----End
Related References
B.6.1.7 Parameter Description: Clock Subset Setting_SSM Output Control
Issue 02 (2012-12-30)

513

A Task Collection
A.8.1.6 Enabling/Disabling the Output of Clock Source IDs

After the extended Synchronization Status Message (SSM) protocol is enabled for an NE, the
NE sends clock source IDs to the other NEs through all microwave links or Ethernet links. To
avoid interference between two different clock subnets, the NE needs to be disabled from sending
clock source IDs to links connected to another clock subnet.
Prerequisites

U2000
NOTE
Context
The following procedure disables the port GE1 from transmitting clock source IDs.
NOTE
For a port connected to another clock subnet on which the extended SSM protocol is enabled, disable the port
from transmitting clock source IDs.
Procedure
Step 1
----End
Related References
B.6.1.8 Parameter Description: Clock Subset Setting_Clock ID Enabling Status
A.8.1.7 Modifying Clock Source Reversion Parameters

You can change the default values of certain clock source reversion parameters if required.
Issue 02 (2012-12-30)

514

A Task Collection
Prerequisites

U2000
NOTE
Context
The following procedure sets the clock reversion mode of a high-priority clock source to nonrevertive.
NOTE
Normally, all clock source reversion parameters take their default values. If strict concordance between the clock
trail and the service route is required, you can change the parameter values according to the reversion mode and
wait to restore (WTR) time configured for service protection.
Procedure
Step 1
----End
Related References
B.6.1.4 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
A.8.1.8 Querying the Clock Synchronization Status

By performing this task, you can query the clock synchronization status of an NE.
Prerequisites
Issue 02 (2012-12-30)

515

A Task Collection

U2000
NOTE
Procedure
Step 1
----End
Related References
B.6.1.1 Parameter Description: Clock Synchronization Status
A.8.2 Managing the IEEE 1588v2 Clock

On a transmission network, the IEEE 1588v2 protocol can be used to synchronize network-wide
high-precision time or transparently transmit high-precision time signals. As a result, the IEEE
1588v2 protocol can substitute for the GPS and other timing equipment to provide high-precision
timing signals for 3G base stations.
A.8.2.1 Enabling/Disabling the IEEE-1588 Timeslot for a Microwave Port

Enable the IEEE-1588 timeslot for a microwave port if the port is required to transmit IEEE
1588v2 packets.
Prerequisites

U2000
Issue 02 (2012-12-30)

516

A Task Collection
NOTE
Context
The following procedure enables the IEEE-1588 timeslot for a microwave port.
NOTE
The IEEE-1588 timeslot status must be the same at the two ends of a microwave link.
Procedure
Step 1
----End
A.8.2.2 Querying or Modifying the PTP System Time

If the IEEE 1588v2 protocol is used for time synchronization, identical Precision Time Protocol
(PTP) system time is displayed on all NEs. If the PTP system time of the primary time source
in the clock subnet is changed, the PTP system time of other NEs on the clock subnet changes
accordingly.
Prerequisites
l
The PTP time synchronization function has been enabled (this function is enabled by
default).

U2000
NOTE
Issue 02 (2012-12-30)

517

A Task Collection
Context
The following procedure changes the PTP system time to July 06, 2012.
NOTE
In practice, in an IEEE 1588v2 clock synchronization solution, the basic PTP system time of a network is
provided by the GPS and does not need to be changed manually. This task is mainly performed for commissioning
and verifying the IEEE 1588v2 time synchronization.
Procedure
Step 1
----End
A.8.2.3 Setting the PTP NE Attributes

Precision Time Protocol (PTP) NE attributes include the working mode, multicast packet
transmission mode, and time calibration function.
Prerequisites

U2000
NOTE
Context
The following procedure changes the NE clock type to BC.
Issue 02 (2012-12-30)

518

A Task Collection
NOTE
l If an OptiX RTN 310 needs to transparently transmit clock signals to interconnected user equipment, set the
NE clock type to TC+BC. In other cases, set the NE clock type to BC.
l Unless otherwise specified, it is recommended that you set the other PTP NE attributes to the default values.
Procedure
Step 1
----End
Related References
B.7.1 Parameter Description: Clock Synchronization Attribute
A.8.2.4 Creating a PTP Clock Port

A Precision Time Protocol (PTP) clock port transmits or receives PTP packets.
Prerequisites
l
NE Clock Type has been set.

U2000
NOTE
Context
The following procedure sets a microwave port and the port GE1 as PTP ports.
Issue 02 (2012-12-30)

519

A Task Collection
Procedure
Step 1
----End
A.8.2.5 Setting PTP Clock Port Attributes

Precision Time Protocol (PTP) clock port attributes include the VLAN ID and encapsulation
format carried in the PTP packets transmitted or received at a port and the reference clock source.
Prerequisites
l
A PTP port has been created.

U2000
NOTE
Context
l
Sets PTP port attributes for an NE whose clock type is boundary clock (BC), according to
Parameter
Value
1SHXA23 (GE2)
Issue 02 (2012-12-30)
Step Mode
Single step
PTP Packet VLAN
100

520

Parameter
A Task Collection
Value
1SHXA23 (GE2)
PTP Packet Encapsulation Format
PTP ETH
NOTE
If two PTP devices are directly connected to each other, the PTP packet VLAN does not need to be set.
If two PTP devices are connected through another device, set the PTP packet VLAN based on the way the
PTP packets traverse the device.
Sets PTP port attributes for an NE whose clock type is TC+BC, according to the planned
Parameter
Value
1SHXA22 (GE1)
Clock Type
TC
Step Mode
Single step
PTP Packet VLAN
100
PTP Packet Encapsulation Format
PTP ETH
NOTE
l If an Ethernet port is connected to a device in another clock domain, set Clock Type to TC. Otherwise,
set it to BC.
l If clock signals are transparently transmitted through a TC port with services, it is recommended that
you set PTP Packet VLAN to the VLAN ID of a service, so that PTP packets of another clock domain
are transmitted as service packets in this clock domain.
Procedure
Step 1 Set attributes for a PTP port on an NE whose clock type is BC.
Issue 02 (2012-12-30)

521

A Task Collection
Step 2 Set attributes for a PTP port on an NE whose clock type is TC+BC.
----End
Related References
A.8.2.6 Setting Parameters for IEEE 1588v2 Clock Packets

Parameters for IEEE 1588v2 clock packets include the P/E mode, packet transmission period,
and announce packet timeout coefficient.
Prerequisites
l
A Precision Time Protocol (PTP) port has been created.

U2000
Issue 02 (2012-12-30)

522

A Task Collection
NOTE
Context
The following procedure configures IEEE 1588v2 packet parameters for the port GE2 according
Parameter
Value
1SHXA23 (GE2)
P/E mode
E2E
SYNC packet frequency
8 packets/s
Delay_Req packet frequency
1 packet/s
Announce packet frequency
1 packet/s
ANNOUNCE packet timeout coefficient
NOTE
l If a microwave port is a PTP port, it is recommended that you set all IEEE 1588v2 clock packet parameters
to their default values.
l If an Ethernet port is a TC port, you do not need to set IEEE 1588v2 clock packet parameters.
l If the clock type of an Ethernet port is boundary clock (BC), set IEEE 1588v2 clock packet parameters
consistently for the Ethernet port and interconnected equipment. Pay attention to the following points:
l Ethernet ports on OptiX RTN 310 support only the E2E mode.
l The transmission frequency of Sync packets must be higher than or equal to two packets per second.
Procedure
Step 1
----End
Issue 02 (2012-12-30)

523

A Task Collection
Related References
A.8.2.7 Configuring the Delay Offset for Asymmetric Transmission Between NEs
This section describes how to compensate for the delay that results from asymmetric clock signal
transmission between NEs.
Prerequisites
l
A Precision Time Protocol (PTP) port has been created.

U2000
NOTE
Context
The following procedure compensates -5 ns for the port 1-SHXA2-3 (GE2).
Procedure
Step 1
----End
Related References
Issue 02 (2012-12-30)

524

A Task Collection
A.8.2.8 Configuring the Cascade Fiber Length for a 1+1 Protection Group
This operation is used to compensate the asymmetric transmission delay caused by cascade fibers
of non-standard length in a 1+1 protection group.
Prerequisites
l
A microwave 1+1 protection group has been created.

U2000
Context
The following procedure configures the cascade fiber length in a 1+1 protection group according
to the planned parameter value listed in the following table.
Parameter
Value
Fiber Length(m)
200
NOTE
l For 1+1 hot standby (HSB) or 1+1 frequency diversity (FD) protection, NEs make compensations
according to the default cascade fiber length 2 m.
l For 1+1 space diversity (SD) protection, NEs make compensations according to the default cascade
fiber length 20 m.
l This parameter needs to be changed only when a 1+1 protection group uses a fiber with special length.
Procedure
Step 1
----End
Issue 02 (2012-12-30)

525

A Task Collection
A.8.2.9 Configuring a PTP Clock Subnet

A Precision Time Protocol (PTP) subnet refers to a PTP clock domain. Each clock
synchronization device can belong to only one PTP clock domain and must trace a clock source
inside the domain.
Prerequisites

U2000
NOTE
Context
The following procedure sets the clock domain to which an NE belongs to 1.
NOTE
The clock domain that the NE belongs to and that the grandmaster clock belongs to are set consistently. In the
network-wide clock synchronization solution, the grandmaster clock often belongs to clock domain 0. This
parameter does not need to be changed. In the clock transparent transmission solution, this parameter must be
set to a value different from that set for the clock domain to which the transparently transmitted clock belongs.
Procedure
Step 1
----End
Related References
B.7.2 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet
Issue 02 (2012-12-30)

526

A Task Collection
A.8.2.10 Modifying the BMC Algorithm Parameters for an NE Clock

When the internal clock of an NE is used as a best master clock (BMC) source, you can modify
the BMC algorithm parameters for the internal clock of the NE.
Prerequisites

U2000
NOTE
Context
The following procedure changes PTP Clock Source Priority 1 to 129 for the BMC algorithm
of an NE clock.
NOTE
In practice, the internal clock of an OptiX RTN 310 NE will not be planned as the BMC reference clock source.
Therefore, the BMC algorithm parameters do not need to be modified. This task is mainly for commissioning
and verifying the BMC algorithm.
Procedure
Step 1
----End
Related References
B.7.3 Parameter Description: Setting of a PTP Clock Subnet_Port_BMC
Issue 02 (2012-12-30)

527

A Task Collection
A.9 Using RMON

Remote network monitoring (RMON) monitors the data traffic on a network segment or an entire
network. Currently, RMON is one of the most widely used network management standards.
A.9.1 Browsing Current Performance Events of Ethernet

After you configure a remote network monitoring (RMON) statistics group for a port, you can
browse the real-time statistical performance data of the port.
Prerequisites

U2000
NOTE
Context
The following procedure allows you to browse the real-time Unicast Packets Received
(packets/s) and Unicast Packets Transmitted(packets/s) of port GE1.
Procedure
Step 1
----End
Related References
B.5.1 Parameter Description: RMON Performance_Statistics Group
Issue 02 (2012-12-30)

528

A Task Collection
A.9.2 Setting the Ethernet Performance Threshold-Crossing

Parameter
After you configure a remote network monitoring (RMON) alarm group for a port, you can
monitor whether the performance value of the port crosses the configured thresholds in the long
term.
Prerequisites

U2000
NOTE
Context
The following procedure enables the threshold-crossing monitoring function for RXPKT64
Parameter
Value
30-Second
Enabled
30-Minute
Enabled
Custom Period 1
Enabled
Custom Period 2
Enabled
Procedure
Step 1
----End
Issue 02 (2012-12-30)

529

A Task Collection
Related References
B.5.3 Parameter Description: RMON Performance_RMON Setting
A.9.3 Configuring the Parameters for Ethernet Historical

Performance Monitoring
When configuring a historical control group for an Ethernet port, you can configure how the
historical performance data of the port is monitored. The Ethernet board monitors the historical
performance data of each port at the default sampling interval of 30 minutes. A maximum of 50
historical performance entries can be saved.
Prerequisites

U2000
NOTE
Context
The following procedure enables the monitoring of Custom Period 1 for undersized packets
Parameter
Value
Custom Period 1
Enabled
Period Length(s)
900
History Register Count
16
Procedure
Step 1
Issue 02 (2012-12-30)

530

A Task Collection
----End
Related References
A.9.4 Browsing Ethernet Historical Performance Data

After you configure a remote network monitoring (RMON) historical group for a port, you can
browse the historical performance data of the port.
Prerequisites
l
The task in A.9.3 Configuring the Parameters for Ethernet Historical Performance
Monitoring has been completed.

U2000
NOTE
Context
The following procedure allows you to browse the 30-second historical performance count
statistics at port GE1.
Procedure
Step 1
Issue 02 (2012-12-30)

531

A Task Collection
----End
Related References
B.5.2 Parameter Description: RMON Performance_History Group
A.10 Configuring a Native Ethernet Service (in End-to-End

Mode)
The U2000 allows Native Ethernet services to be configured in an end-to-end mode.
A.10.1 Searching for Native Ethernet Services

This section describes how to synchronize Native Ethernet services from the NE layer of the
network management system (NMS) to the network layer of the NMS.
Prerequisites
l
Native Ethernet service data has been correctly configured for the NE.
Data is synchronous between the NE and NMS.

U2000
NOTE
Precautions
This task synchronizes Native Ethernet services that have not yet been synchronized to the
network layer topology of the NMS. For Native Ethernet services that have been synchronized
to the network layer topology of the NMS, skip this task and manage the services by referring
to A.10.7 Managing Native Ethernet Services.
Issue 02 (2012-12-30)

532

A Task Collection
Context
The procedure described in this section synchronizes the Native Ethernet line (E-Line) and
Native Ethernet local area network (E-LAN) services of a specified search area to the network
layer of the NMS.
Procedure
Step 1
----End
A.10.2 Creating a Point-to-Point Transparently Transmitted E-Line

Service
This section describes how to create a point-to-point transparently transmitted Ethernet line (ELine) service in end-to-end mode.
Prerequisites
l
Port attributes have been configured for each board on an NE.
Fiber connections for Ethernet links between NEs have been created on Main Topology.
Data is synchronous between the NE and network management system (NMS).

U2000
NOTE
Context
The procedure described in this section creates a point-to-point transparently transmitted E-Line
service according to the planned parameter values listed in the following table.
Issue 02 (2012-12-30)

533

A Task Collection
Parameter
Value
Service Name
E-Line-001
BPDU Private Service
No
Customer
Customer1
Source NE
NE(922141)
Source port
1-SHXA2-2(GE1)
Sink NE
NE(922142)
Sink port
1-SHXA2-2(GE1)
Procedure
Step 1
----End
A.10.3 Creating a VLAN-based E-Line Service

This section describes how to create a VLAN-based Ethernet line (E-Line) service in end-toend mode.
Prerequisites
l
Port attributes have been configured for each board on an NE.

U2000
Issue 02 (2012-12-30)

534

A Task Collection
NOTE
Context
The procedure described in this section creates a VLAN-based E-Line service according to the
Parameter
Value
Service Name
E-Line-002
BPDU Private Service
No
Customer
Customer1
Source NE
NE(922141)
Source port
1-SHXA2-2(GE1)
C-VLAN of the source port
100
Sink NE
NE(922142)
Sink port
1-SHXA2-2(GE1)
C-VLAN of the sink port
100
Procedure
Step 1
----End
A.10.4 Creating an IEEE 802.1D Bridge-based E-LAN Service

This section describes how to create an IEEE 802.1D bridge-based Ethernet local area network
(E-LAN) service in end-to-end mode.
Issue 02 (2012-12-30)

535

A Task Collection
Prerequisites
l
Port attributes have been correctly configured for each board on an NE.

U2000
NOTE
Context
The procedure described in this section creates an IEEE 802.1D bridge-based E-LAN service
Table A-7 Basic parameters for an IEEE 802.1D bridge-based E-LAN service
Parameter
Value
Service Type
E-LAN
Service Name
E-LAN-00001
Customer
customer_01
Tag Type
Tag-Transparent
Table A-8 Information about ports mounted to network bridges

Para
meter
Issue 02 (2012-12-30)
Value
NE(9-22144)
NE(9-22142)
NE(9-22143)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
Enabl
e Port
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Worki
ng
Mode
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation
Loopb
ack
Check
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed

536

Para
meter
A Task Collection
Value
NE(9-22144)
NE(9-22142)
NE(9-22143)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
Broad
cast
Packet
Suppr
ession
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Broad
cast
Packet
Suppr
ession
Thres
hold
(%)
30
30
30
30
30
30
30
30
30
Procedure
Step 1
----End
A.10.5 Creating an IEEE 802.1Q Bridge-based E-LAN Service

This section describes how to create an IEEE 802.1Q bridge-based Ethernet local area network
(E-LAN) service in end-to-end mode.
Issue 02 (2012-12-30)

537

A Task Collection
Prerequisites
l
Port attributes have been correctly configured for each board on an NE.

U2000
NOTE
Context
The procedure described in this section creates an IEEE 802.1Q bridge-based E-LAN service
Table A-9 Basic parameters for an IEEE 802.1Q bridge-based E-LAN service
Parameter
Value
Service Type
E-LAN
Service Name
E-LAN-00001
Customer
customer_02
Tag Type
C-Aware
Table A-10 Information about ports mounted to network bridges

Para
meter
Issue 02 (2012-12-30)
Value
NE(9-22144)
NE(9-22142)
NE(9-22143)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
CVLA
N
100,
200
100
200
100
100
100
200
200
200
Enabl
e Port
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Worki
ng
Mode
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation
AutoNegoti
ation

538

Para
meter
A Task Collection
Value
NE(9-22144)
NE(9-22142)
NE(9-22143)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
1SHX
A2-1
(IF)
1SHX
A2-2
(GE1)
1SHX
A2-3
(GE2)
Loopb
ack
Check
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Broad
cast
Packet
Suppr
ession
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Enabl
ed
Broad
cast
Packet
Suppr
ession
Thres
hold
(%)
30
30
30
30
30
30
30
30
30
Procedure
Step 1
----End
A.10.6 Verifying a Native Ethernet Service

This section describes how to use ETH OAM to verify the connectivity of Native Ethernet
services.
Issue 02 (2012-12-30)

539

A Task Collection
Prerequisites
l
Native Ethernet services are configured in end-to-end mode and ETH OAM CC has been
enabled.

U2000
NOTE
Context
The procedure described in this section aims to:
1.
Verify Ethernet line (E-Line) services transmitted in Native Ethernet mode.
2.
Verify Ethernet local area network (E-LAN) services transmitted in Native Ethernet mode.
Procedure
Step 1 Verify Ethernet line (E-Line) services transmitted in Native Ethernet mode.
Step 2 Verify Ethernet local area network (E-LAN) services transmitted in Native Ethernet mode.
Issue 02 (2012-12-30)

540

A Task Collection
----End
A.10.7 Managing Native Ethernet Services

This section describes how to manage a Native Ethernet service, such as deploying and deleting
a Native Ethernet service and querying information about the service.
Prerequisites

U2000
NOTE
Context
The procedure described in this section enables you to manage a Native Ethernet service.
Procedure
Step 1
Issue 02 (2012-12-30)

541

A Task Collection
----End
A.10.8 Managing Discrete Native Ethernet Services

This section describes how to manage discrete Native Ethernet services. Such services cannot
become network-layer services and exist only on isolated NEs.
Prerequisites

U2000
NOTE
Context
The procedure described in this section enables you to manage discrete Native Ethernet services.
Procedure
Step 1
Issue 02 (2012-12-30)

542

A Task Collection
----End
A.10.9 Adjusting an E-LAN Service Network

This section describes how to adjust an Ethernet local area network (E-LAN) service network
after E-LAN services are configured in end-to-end mode.
Prerequisites
l

U2000
NOTE
Context
The procedure described in this section adjusts an E-LAN service network.
Procedure
Step 1
Issue 02 (2012-12-30)

543

A Task Collection
----End
A.11 Verifying Services and Features

This chapter describes how to verify service and feature configurations.
A.11.1 Testing Ethernet Services

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

To test Ethernet services configured on a per NE basis, you must create ETH OAM manually.
Prerequisites
NOTE

U2000

example, as shown in Figure A-2.
Issue 02 (2012-12-30)

544

A Task Collection
Figure A-2 Connection diagram for testing Ethernet services
NE 1

NE 2
GE 1
GE 1
NodeB
VLAN ID = 100
VLAN ID = 100
RNC
Procedure
Step 1 Test the Ethernet services between NE1 and NE2.
l If the value of LossRate in Result is 0, the test is successful.

l If the value of LossRate in Result is not 0, handle the problem based on the procedures in
Cause
Handling Procedure
Connecting to the peer end fails within the

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

than the transmission bandwidth.
Check the link for bit errors.
----End
Issue 02 (2012-12-30)

545

A Task Collection
A.11.1.2 Testing Ethernet Services Configured in End-to-End Mode

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

U2000
NOTE

example, as shown in Figure A-3.
Figure A-3 Connection diagram for testing Ethernet services
NE 1
GE 1
NE 2
GE 1
NodeB
VLAN ID = 100
VLAN ID = 100
RNC

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

546

A Task Collection
Step 2 Verify E-LAN services transmitted in Native Ethernet mode.
----End
A.11.2 Testing AM Shifting

Prerequisites
l
The adaptive modulation (AM) function has been enabled for the microwave link to be
tested.

Web LCT
NOTE
Issue 02 (2012-12-30)

547

A Task Collection
Context
The following procedure tests the AM shifting function on an NE.
Procedure
Step 1 Set the AM attributes.
Step 2 Test one-click AM shifting.
----End
A.11.3 Testing Protection Switching

A.11.3.1 Testing ERPS Switching

You can verify the Ethernet ring protection switching (ERPS) function by checking the port
status of the ERPS protection group before and after switching.
Issue 02 (2012-12-30)

548

A Task Collection
Prerequisites
l
ERPS has been configured for OptiX RTN 310s on a ring network.
Ethernet links on the ring network are connected correctly.

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

In Figure A-4, the Ethernet services between NE 1 and NE 6 are protected by ERPS, and NE 1
is the RPL owner node.
Figure A-4 Configuration for testing ERPS
NE 4
E: IF
W: GE (GE2)
NE 3
E: GE (GE2)
W: IF
NE 5
E: GE (GE2)
W: IF
NE 6
E: IF
W: GE (GE2)
NE 2
E: IF
W: GE (GE2)
NE 7
E: GE (GE2)
W: IF
NE 8
E: IF
W: GE (GE2)
NE 1
E: GE (GE2)
W: IF
RPL owner
Ethernet cable
Blocked port
Issue 02 (2012-12-30)

549

A Task Collection
Procedure
Step 1 Before switching, query the status of the ERPS protection group that is configured on NE 1.
Step 4 After switching, query the status of the ERPS protection group that is configured on NE 1.
Issue 02 (2012-12-30)

550

A Task Collection
----End
A.11.3.2 Testing 1+1 Protection Switching

You can verify the 1+1 protection functions by checking the changes of the main and standby
devices before and after switching.
Prerequisites
l
Ethernet services and 1+1 protection have been configured.
Static link aggregation groups (LAGs) have been configured for third-party devices.

U2000
Issue 02 (2012-12-30)

551

A Task Collection

Figure A-5 Test connection diagram
The basic configurations are as follows:
l
Main OptiX RTN 310s: NE 11 and NE 12
Standby OptiX RTN 310s: NE 21 and NE 22

LAG
NE 11
NE 12
LAG
LAG
LAG
COMBO
COMBO
Antenna
NE 21
Antenna
NE 22
LAG
LAG
E-LAG
E-LAG
OptiX RTN 900
Ethernet link
Microwave link
Optical fiber
The Ethernet services protected by 1+1 hot standby (HSB) between NE 11 and NE 12 shown in
Figure A-5 are tested.
Procedure
Step 1 Configure Reversion Mode for the 1+1 HSB protection group on NE 11.
1.
2.
In Protection Group, select the desired protection group and set Reversion Mode to NonRevertive.
3.
Click Apply.
4.
Click Close.
Step 2 Query the protection group status on NE 11 before switching.

1.
2.
3.
Step 3 Test availability of the tested Ethernet services before switching. For details, see A.11.1 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.
Issue 02 (2012-12-30)

552

A Task Collection
3.
Select the SHXA2 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.
2.
3.
Step 6 Test availability of the tested Ethernet services after switching. For details, see A.11.1 Testing
Ethernet Services. The value of LossRate in Test Result should be 0, indicating that the 1+1
protection switching is successful.
Step 7 Restore Reversion Mode to the original value.
----End
A.11.3.3 Testing PLA Protection Switching

You can verify the physical link aggregation (PLA) function by checking the changes of devices
and links in a PLA group before and after switching.
Prerequisites
l
PLA protection has been configured.
Enhanced link aggregation groups (E-LAGs) have been configured for OptiX RTN 310s,
and static LAGs have been configured for third-party devices.

U2000
Issue 02 (2012-12-30)

553

A Task Collection

Figure A-6 Test connection diagram
LAG
NE 11
NE 12
LAG
LAG
LAG
COMBO
COMBO
Antenna
NE 21
Antenna
NE 22
LAG
LAG
E-LAG
E-LAG
Microwave link
OptiX RTN 900

Ethernet link
Optical fiber
As shown in the preceding figure, the basic configurations are as follows:

l
The PLA configuration with E-LAG is used as an example.
Procedure
Step 1 Test the availability of the tested Ethernet services before switching. For details, see A.11.1
Testing Ethernet Services. The value of LossRate in Test Result should be 0.
1.
2.
In RF, set TX Status to mute.
3.
Click Apply.
Step 3 Test the availability of the tested Ethernet services after switching. For details, see A.11.1
Testing Ethernet Services. The value of LossRate in Test Result should be 0, indicating that
the PLA protection switching is successful.
1.
2.
In RF, set TX Status to unmute.
Issue 02 (2012-12-30)

554

3.
A Task Collection
Click Apply.
----End
Issue 02 (2012-12-30)

555

B Parameters Description
Parameters Description
This chapter describes the parameters used in this document.

B.1 Parameters for Network Management
This topic describes the parameters that are related to network management.
B.2 Radio Link Parameters
This topic describes the parameters that are related to radio links.
B.3 Parameters for Board Interfaces
This topic describes the parameters that are related to board interfaces.
B.4 Parameters for Ethernet Services and Ethernet Features
This section describes the parameters for the Ethernet services and Ethernet features, including
service parameters, protocol parameters, OAM parameters, and QoS parameters.
B.5 RMON Parameters
This topic describes the parameters that are related to RMON performances.
B.6 Clock Parameters
This topic describes the parameters that are related to clocks.
B.7 PTP Clock Parameters
This topic describes PTP clock parameters.
Issue 02 (2012-12-30)

556

B.1 Parameters for Network Management

This topic describes the parameters that are related to network management.
B.1.1 Parameters for NE Management

This topic describes the parameters that are used for managing network elements (NEs).
B.1.1.1 Parameter Description: NE Searching

This topic describes the parameters that are used for searching for NEs.
Parameters for the Search Field

Parameter
Value Range
Default Value
Description
Address Type
IP Address of GNE
IP Address Range of GNE
l To search for all the

NEs that communicate
with the gateway NE,
select IP Address
Range of GNE.
NSAP Address
IP Address Range of GNE
l To select the gateway

NE only, select IP
Address of GNE.
NOTE
If Address Type is set to IP
Address of GNE or IP
Address Range of GNE,
and if the U2000 (server)
and the gateway NE are
located in different network
segments, ensure that the
U2000 and relevant routers
are configured with the IP
routes for the network
segment in which the
U2000 and gateway NE are
located.
Search Address
l If Address Type is set

to IP Address of
GNE, enter the IP
address of the gateway
NE, such as 129.9.x.x.
l If Address Type is set
to IP Address Range
of GNE, enter the
number of the IP
network segment in
which the gateway NE
is located, such as
129.9.255.255.
Issue 02 (2012-12-30)

557

Parameter
Value Range
Default Value
Description
User Name
This parameter specifies

the user name of the
gateway NE.
Password

the password of the
gateway NE.
Parameter for Searching for NEs

Parameter
Value Range
Default Value
Description
Create NE after search
Selected
Deselected
l To create NEs in
batches, it is
recommended that you
select Create NE
after search. The NEs
are automatically
created after they are
found.
Deselected
l After Create NE after

search is selected,
enter NE User and
Password that are
used for creating an
NE.
NOTE
If only Create NE after
search is selected, Search
for NE is selected
automatically.
NE User
l This parameter
specifies the user name
to be entered when an
NE is created.
l This parameter is valid
only when Create NE
after search is
selected.
Password
l This parameter
specifies the password
NE is created.
only when Create NE
after search is
selected.
Issue 02 (2012-12-30)

558

Parameter
Value Range
Default Value
Description
Upload after being

created
Selected
Deselected
l This parameter
specifies whether to
automatically upload
the NE data after the
NE is found and
created.
Deselected
l If only Upload after

create is selected,
Search for NE and
Create NE after
search are selected
automatically.
Parameter for the Found NEs

Parameter
Value Range
Default Value
Description
NE ID
This parameter indicates

the ID of the found NE,
which consists of
extended ID and NE ID.
GNE Address

the address of the gateway
NE that is connected to the
found NE.
GNE ID

the ID of the gateway NE
that is connected to the
found NE.
Can Be Created As GNE
Yes
Yes
l This parameter
specifies the password
NE is created.
No

only when Create NE
after search is
selected.
Connection Mode
Common
Common
The communication
between the client and the
server is encrypted if this
parameter is set to
Security SSL.
1400

the communication port.
Security SSL
Port
Issue 02 (2012-12-30)

559

Parameter
Value Range
Default Value
Description
NE Status
Created

whether the found NE is
created.
Uncreated
Related Tasks
A.3.1.1 Creating an NE by Using the Search Method
B.1.1.2 Parameter Description: NE Creation

This topic describes the parameters that are related to NE creation.
Parameters on the Main Interface

Parameter
Value Range
Default Value
Description
Type

the type of the NE to be
created.
ID
1 to 49151
l The ID refers to the

basic ID. If the
extended ID is not
used, the basic ID of an
NE must be unique on
the networks that are
managed by the same
NMS.
l This parameter is set
according to the
l The NE ID consisting
of the basic ID and
extended ID identifies
an NE on the NMS.
Extended ID
Issue 02 (2012-12-30)
1 to 254

If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
Extended ID.
560

Parameter
Value Range
Default Value
Description
Name
l This parameter
specifies the name of
the NE.
l After you have
specified the name of
the NE, the name is
displayed under the
icon of the NE.
Remarks

the remarks of the NE.
Gateway Type
Non-Gateway
Non-Gateway
l This parameter is set to

Gateway if the new
NE is a gateway NE.
Gateway
l This parameter is set to

Non-Gateway if the
new NE is a nongateway NE.
according to the DCN
planning if the new NE
can function as a
gateway NE or a nongateway NE.
Gateway

the gateway NE of the new
NE when Gateway Type
is set to Non-Gateway.
Protocol
IP
IP
l This parameter needs

to be set when
Gateway Type is set
to Gateway.
OSI
l In other cases, this

parameter is set to IP.
IP Address

the IP address of the
gateway NE. This
parameter needs to be set
when Affiliated Gateway
Protocol is set to IP.
Connection Mode
Common
Common
The communication
between the client and the
server is encrypted if this
parameter is set to
Security SSL.
Security SSL
Issue 02 (2012-12-30)

561

Parameter
Value Range
Default Value
Description
Port

the communication port.
NE User

the user name to be
entered when an NE is
created.
Password

the password to be entered
when an NE is created.
Related Tasks
A.3.1.2 Creating an NE Manually
B.1.1.3 Parameter Description: NE Time Synchronization (U2000)

This topic describes the parameters that are used for synchronizing the time of NEs.
Parameters for NE Time Synchronization

Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
NE ID

the ID of the NE.
Synchronous Mode
Standard NTP
Null
l If this parameter is set

to NM, the NE
synchronizes the time
of the NMS server.
NM
Null
l If this parameter is set

to Standard NTP, the
NE synchronizes the
Network Time
Protocol (NTP) server
through the standard
NTP.
Standard NTP
Authentication
Issue 02 (2012-12-30)
Enabled
Disabled
Disabled

This parameter is valid

only when Synchronous
Mode is set to Standard
NTP.
562

Parameters for the Standard NTP Server

Parameter
Value Range
Default Value
Description
Standard NTP Server

Identifier
NE ID
NE ID
l If the NE functions as
the gateway NE, this
IP
a non-gateway NE and
communicates with
the gateway NE
through the HWECC
protocol, this
parameter is set to NE
ID.
a non-gateway NE and
communicates with
the gateway NE
through the IP
protocol, this
Standard NTP Server
the gateway NE, this
parameter is set to the
IP address of the
external NTP server.
a non-gateway NE,
this parameter is set to
the ID or IP address of
the gateway NE.
Issue 02 (2012-12-30)

563

Parameter
Value Range
Default Value
Description
Standard NTP Server

Key
0 to 1024
l If the NTP server does

not need to
authenticated, this
parameter is set to the
value "0".
l If the NTP server
needs to be
authenticated, the
authentication is
performed according
to the allocated key of
the NTP server. In this
case, the NE
authenticates the NTP
server based on the key
and the corresponding
password (specified in
the management of the
standard NTP key).
Parameters for Setting Automatic Synchronization

Parameter
Value Range
Default Value
Description
Start Time
l This parameter
specifies the start time
of the synchronization
period. After this
parameter is specified,
the NMS and the NE
synchronize the time
once at the intervals of
Synchronization
Period(days).
l It is recommended that
you use the default
value.
DST
Selected
Deselected
Deselected
l This parameter
indicates whether
Synchronization
Starting Time is the
daylight saving time.
situation.
Issue 02 (2012-12-30)

564

Parameter
Value Range
Default Value
Description
Period(days)
1 to 300
l This parameter
indicates the period of
synchronizing the time
of the NE with the time
of the NMS.
you use the default
value.
Related Tasks
A.3.1.6 Synchronizing the NE Time
B.1.1.4 Parameter Description: Standard NTP Key Management

This topic describes the parameters that are used for managing the standard NTP key.

Parameter
Value Range
Default Value
Description
Key ID
1 to 1024
l This parameter
indicates the key for
NTP authentication.
according to the
requirements of the
Password
l This parameter
indicates the password
that corresponds to
Key ID.
according to the
requirements of the
Issue 02 (2012-12-30)

565

Parameter
Value Range
Default Value
Description
Trusted
Yes
Yes
l When this parameter is

set to No, the key
verification is not
trusted. After
receiving the key, the
NE rejects the clock
synchronization
service.
No

set to Yes, the key
verification is trusted.
After receiving the
key, the NE provides
the clock
synchronization
service.
l After receiving an
unknown or incorrect
key, the NE rejects the
clock synchronization
service. Hence, it is
set a trusted key only.
Related Tasks
A.3.1.8 Configuring a Standard NTP Key
B.1.1.5 Parameter Description: Localization Management of the NE Time

This parameter describes the parameters that are used for localization management of the NE
time.
Parameters for Localization Management of the NE Time

Parameter
Value Range
Default Value
Description
NE
This parameter indicates the name of the

NE.
Time Zone
This parameter indicates the time zone.
DST
This parameter indicates whether DST is

enabled.
Issue 02 (2012-12-30)

566

Parameters for Time Zone

Parameter
Value Range
Default Value
Description
Time Zone
l After the time zone is changed, the

current time of the NE is changed
accordingly.
l This parameter is set according to the
place where the NE is located.
DST
Selected
Deselected
Deselected
l The parameters related to daylight

saving time can be valid only when this
parameter is selected.
situation whether daylight saving time is
used in the place where the NE is located.
1 to 120
Offset
This parameter specifies the offset value of

the daylight saving time.
WEEK
This parameter specifies the method of

adjusting the daylight saving time.
Unit: minute(s)
Start Rule
WEEK
DATE
DATE-WEEK
Start Time
This parameter specifies the start daylight

saving time.
End Rule
WEEK
WEEK
This parameter specifies the method of

adjusting the daylight saving time.
This parameter specifies the end daylight

saving time.
DATE
DATE-WEEK
End Time
Related Tasks
A.3.1.7 Localizing the NE Time
B.1.2 Parameters for Communications Management

This topic describes the parameters that are used for communications management.
B.1.2.1 Parameter Description: NE Communication Parameter Setting

This topic describes the parameters that are used for NE communication setting.
Issue 02 (2012-12-30)

567

Parameters for NE Communication Setting

Parameter
Value Range
Default Value
Description
IP Address
Before delivery, the

IP address of the NE
is set to 129.9.x.x.
The letter x indicates
the basic ID.
Gateway IP
Address
0.0.0.0
Subnet Mask
255.255.0.0
In the HWECC solution, an IP address is set

according to the following rules:
l The IP address, subnet mask, and default
gateway of the gateway NE should meet
the planning requirements of the
external DCN.
l If an NE uses the extended ECC, the IP
address must be in the same network
segment.
l The IP address of other NEs should be
set according to the NE ID. In this case,
the IP address of an NE should be set in
the format of 0x81000000+ID. That is,
if the ID is 0x090001, the IP address
should be set to 129.9.0.1.
Extended ID
1 to 254
l Do not change the extended ID when the

number of actual NEs does not exceed
the range permitted by the basic NE ID.
l It is recommended that this parameter
takes the default value.
NSAP Address
This parameter is valid only when the OSI

over DCC solution is applied. This
parameter is used to set only the area ID of
an NSAP address. The other parts of the
NSAP address are automatically generated
by the NE.
NOTE
OptiX RTN 310 does not support this parameter.
Issue 02 (2012-12-30)

568

Parameter
Value Range
Default Value
Description
Connection Mode
Common + Security
SSL
Common + Security
SSL
l Specifies the connection mode that the

gateway NE allows the NMS to use for
connecting to the gateway NE.
Common
l If the gateway NE has no special

security requirement for connection to
the NMS, Connection Mode can be set
to Common.
Security SSL
l If the gateway NE requests secure

connection to the NMS for preventing
information interception and cracking,
Connection Mode needs to be set to
Security SSL.
l If NE communication security level
needs to be the same as NMS
communication security level,
Connection Mode needs to be set to
Common + Security SSL.
l The default parameter value is
recommended unless the gateway NE
requires that the NMS use the SSL
connection mode.
l The parameter value takes effect only
when it is set for a gateway NE and the
gateway NE is connected to the NMS by
means of the IP protocol.
Related Tasks
A.3.6.1 Setting NE Communication Parameters
B.1.2.2 Parameter Description: ECC Management_Ethernet Port Extended ECC

This topic describes the parameters that are related to the extended ECCs of Ethernet ports.
Parameters for the ECC Extended Mode

Parameter
Value Range
Default Value
Description
ECC Extended
Mode
Auto mode
Auto mode
It is recommended that you use the default

value.
Issue 02 (2012-12-30)
Specified mode

569

Parameters for Setting the Server

Parameter
Value Range
Default Value
Description
IP
This parameter indicates or specifies the IP

address of the server.
Port
1601 to 1699
l This parameter is valid only when ECC

Extended Mode is set to Specified
mode.
l This parameter can be set only when the
NE functions as the server of the
extended ECC. In normal cases, the NE
that is close to the NMS functions as the
server.
l This parameter can be set to any value
from 1601 to 1699.
Parameters for Setting the Client

Parameter
Value Range
Default Value
Description
Opposite IP
0.0.0.0
Port
1601 to 1699
l This parameter is valid only when ECC

Extended Mode is set to Specified
mode.
l This parameter can be set only when the
NE functions as the client of the
extended ECC. Except for the NE that
functions as the server, all other NEs that
use the extended ECC can function as the
client.
l Opposite IP and Port are respectively
set to the IP address of the server NE and
the specified port number.
Related Tasks
A.3.6.7 Configuring Extended ECCs
B.1.2.3 Parameter Description: NE ECC Link Management

This topic describes the parameters that are used for NE ECC link management.
Parameter for NE ECC Link Management

Parameter
Value Range
Default Value
Description
Destination NE
This parameter specifies the sink NE of the

ECC connection.
Issue 02 (2012-12-30)

570

Parameter
Value Range
Default Value
Description
Transfer NE
This parameter specifies the next transfer

NE and the direction of the ECC route.
Distance
l This parameter specifies the number of

NEs (excluding the source NE and sink
NE) through which the ECC route
passes, namely, the number of ECC
packet forwarding attempts. The value
can be set to a value that is greater than
the number of actual ECC packet
forwarding attempts. If the value is set to
a value that is less than the number of
actual ECC packet forwarding attempts,
however, the destination NE fails to be
accessed.
l If the value is set to 0, it indicates that the
source NE is adjacent to the destination
NE.
Level
l This parameter indicates that multiple

ECC routes from the source NE to the
destination NE may be available. An
ECC route of a higher priority is selected
to transmit the packets to the destination
NE.
l If the ECC route is generated
automatically, the priority is 4.
l If the ECC route is added manually, the
priority is 5.
Mode
This parameter indicates the ECC routing

mode.
SCC No.
This parameter specifies the physical port

through which the ECC route passes. The
value of this parameter is automatically
assigned the NE.
Related Tasks
A.3.6.16 Querying ECC Routes
B.1.2.4 Parameter Description: ECC Link Management_Availability Test

This topic describes the parameters that are used to test ECC availability.
Issue 02 (2012-12-30)

571

Ping Test Parameters

Parameter
Value Range
Default Value
Description
Target NE
Specifies the NE for which a ping test will

be performed.
Packet Length
(Byte)
0-800
64
l Specifies the test packet length.
Packet Quantity
1-65535

take its default value.
3
l Specifies the number of test packets.

Sending Interval
(10ms)
0-65535
l Specifies the test packet transmission

interval.
Response Timeout
Time(10ms)
1-65535
1000
l Specifies the maximum time for test

packet to wait until being responded to.
Traceroute Parameters
Parameter
Value Range
Default Value
Description
Target NE
Specifies the NE for which a traceroute test

will be performed.
Response Timeout
Time(10ms)
0-65535
1000

Forwarding NEs
0-255
64
Specifies the number of NEs that test

packets will traverse during the forwarding
process.
Related Tasks
A.3.6.18 Verifying Connectivity of an ECC Network
B.1.2.5 Parameter Description: Access Control

This topic describes the parameters that are used for access control of the NMS.
Issue 02 (2012-12-30)

572

Parameters for Ethernet Access Control

Parameter
Value Range
Default Value
Description
Enable Ethernet
Access
Selected
After The First Network Port is set to

Enabled for Ethernet access, the NE can
access the NMS through the Ethernet port.
Port
This parameter displays the NMS port.
Work Mode
adapt
This parameter specifies the working modes

of the NMS.
This parameter displays the working modes

of the NMS port.
Deselected
10M Half_Duplex
10M Full_Duplex
100M Half_Duplex
100M Full_Duplex
Actual Work Mode
Enabled/Disabled
Enabled
Specifies whether the Ethernet network

management portis enabled.
Disabled
Parameters for Access Control over Serial Ports

Parameter
Value Range
Default Value
Description
Enable Serial Port

Access
Selected
Selected
After Enable Serial Port Access is

selected, the NE can access the NMS or
command lines through the serial port.
Access Command
Line
Selected
Deselected
If Access Command Line is selected, the

serial interface can be used to access the
command line terminal.
Access NM
Selected
Deselected
If Access NM is selected, the serial interface

can be used to access the NMS.
9600
l This parameter specifies the data

transmission rate in the communications
through serial ports.
Deselected
Deselected
Deselected
Baud Rate
1200
2400
4800

rate of the serial port at the opposite end,
and the rates at both ends must be the
same.
9600
19200
38400
57600
115200
Related Tasks
A.3.7 Configuring the NMS Port on an NE
Issue 02 (2012-12-30)

573

B.1.2.6 Parameter Description: DCC Management_DCC Rate Configuration

This topic describes the parameters that are used for configuring the DCC rate.
Parameters for DCC Rate Configuration

Parameter
Value Range
Default Value
Description
Port
This parameter indicates the port that is

connected to the DCC channel.
Enabled/Disabled
Enabled
Enabled

value, except for the following cases:
Disabled
l If the port is connected to the other ECC

subnet, Enabled/Disabled is set to
Disabled.
l If the port is connected to a third-party
network and does not exchange the
network management information with
other ports, Enabled/Disabled is set to
Disabled.
Channel
D1-D3
D1-D3
D4-D12

value.
D1-D12
OptiX RTN 310 supports only D1-D3.
D1-D1
DCC Resources
This parameter indicates the DCC

resources.
Communication
Status
This parameter indicates the

communication status.
Protocol Type
HWECC
TCP/IP
TCP/IP

value.
OSI
OptiX RTN 310 does not support OSI.
IP Address
l IP Address is available only if Protocol

Type is set to TCP/IP.
l When the IP DCN solution is used and
the NE functions as an ABR, this
parameter specifies the interface IP
address of the non-backbone area port on
the ABR.
Subnet Mask
l Subnet Mask is available only if

Protocol Type is set to TCP/IP.
parameter specifies the subnet mask of
the non-backbone area port on the ABR.
Issue 02 (2012-12-30)

574

Related Tasks
A.3.6.2 Configuring DCCs
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route

Management
This topic describes the parameters that are used for IP route management.
Parameters for IP Route Management

Parameter
Value Range
Default Value
Description
Destination
Address
This parameter indicates the destination

address of the packets. This parameter can
be set to a valid IP address of class A, B, or
C only, but cannot be set to the IP address
of the local host or the loopback address
with the 127 field.
Subnet Mask
This parameter indicates the subnet mask of

the destination address of the packets.
Gateway
This parameter indicates the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of the
next hop of the packets.
Protocol
l DIRECT: indicates the route between

the local NE and an adjacent NE.
l STATIC: indicates the route that is
created manually.
l OSPF: indicates the route between the
local NE and a non-adjacent NE.
l OSPF_ASE: indicates the route whose
Destination Address is beyond the
OSPF domain.
l A route can be deleted in the case of
STATIC only, but cannot be edited in
the other cases.
l Compared with a dynamic route, a static
route has a higher priority. If any conflict
occurs, the static route is preferred.
Issue 02 (2012-12-30)

575

Parameter
Value Range
Default Value
Description
Interface
This parameter indicates the interface that is

used on the route. Interface is a concept
specified in the TCP/IP protocol stack. In
the TCP/IP protocol stack, you can create
multiple types of interface, such as a
loopback interface (namely, the interface
whose IP address is 127.0.0.1), an Ethernet
interface, and PPP interface. Each interface
must have a unique interface name.
Metric
This parameter indicates the maximum

number of routers through which the
packets are transmitted. Metric is used to
indicate the overhead bytes that are
transmitted to the destination address. The
smaller the value, the less the overhead
bytes. If multiple routes can reach the same
destination address, a route whose overhead
is less is preferred to transmit the packets.
Related Tasks
A.3.6.8 Creating a Static IP Route
A.3.6.17 Querying IP Routes
B.1.2.8 Parameter Description: IP Protocol Stack Management_Availability Test

This topic describes the parameters that are used to test IP DCN availability.
Ping Test Parameters

Parameter
Value Range
Default Value
Description
Target NE IP
Specifies the NE for which a ping test will

be performed.
Packet Length
(Byte)
0-800
64
l Specifies the test packet length.
Packet Quantity
1-65535

3
l Specifies the number of test packets.

Sending Interval
(10ms)
0-65535
l Specifies the test packet transmission

interval.
Issue 02 (2012-12-30)

576

Parameter
Value Range
Default Value
Description
Response Timeout
Time(10ms)
1-65535
5000

Traceroute Parameters
Parameter
Value Range
Default Value
Description
Target NE IP
Specifies the NE for which a traceroute test

will be performed.
Max Hops
1-30
10
Specifies the number of hops which test

packets traverse during the packet
transmission process.
Related Tasks
A.3.6.19 Verifying Connectivity of an IP DCN Network
B.1.2.9 Parameter Description: IP Protocol Stack Management_OSPF Parameter

Settings
This topic describes the parameters that are used for OSPF settings.
OSPF Parameters
Parameter
Value Range
Default Value
Description
Area
0.0.0.0
l If only an OSPF area is configured on an

NE, set this parameter according to the
l If multiple OSPF areas are configured on
an NE, this parameter takes its default
value 0.0.0.0.
Issue 02 (2012-12-30)

577

Parameter
Value Range
Default Value
Description
DCC Hello Timer

(s)
1 to 255
10
l DCC Hello Timer(s) specifies the Hello

packet timer for the DCC channel or
inband DCN.
l The Hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l DCC Hello Timer(s) determines the
interval for the hello packet timer to
transmit the hello packets.
l In the case of two interconnected NEs,
DCC Hello Timer(s) must be set to the
same value.
l Unless otherwise specified, it is
recommended that this parameter take its
default value.
DCC Neighbor
Dead Time(s)
1 to 65535
40
l DCC Neighbor Dead Time(s) specifies

the dead time of a neighbor router for the
DCC channel or inband DCN.
l If the local router fails to receive the
hello packets from the connected
neighbor router within the time specified
in DCC Neighbor Dead Time(s), it
considers that the neighbor router is
unavailable.
l DCC Neighbor Dead Time(s) should
be set to a value that is a minimum of
twice the value of DCC Hello Timer
(s).
l In the case of adjacent NEs, DCC
Neighbor Dead Time(s) must be set to
the same value. Otherwise, the OSPF
protocol fails to operate normally.
default value.
Issue 02 (2012-12-30)

578

Parameter
Value Range
Default Value
Description
DCC
Retransmission
Timer(s)
1 to 65535
l DCC Retransmission Timer(s)

specifies the interval for transmitting a
request through the DCC channel or
inband DCN to retransmit the link state
advertisement (LSA) packets.
default value.
DCC Delay(s)
1 to 3600
l DCC Delay(s) specifies the delay time

to transmit the LSA packets through the
DCC channel or inband DCN.
l The LSA packets in the LSA database of
the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the age
of the LSA packets based on the value of
DCC Delay(s).
default value.
LAN Hello Timer

(s)
1 to 255
10
l DCC Hello Timer(s) specifies the hello

packet timer at the Ethernet network
management port.
l The hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l LAN Hello Timer(s) determines the
interval for the hello packet timer of the
NE to transmit the hello packets.
l In the case of two interconnected NEs,
LAN Hello Timer(s) must be set to the
same value.
default value.
Issue 02 (2012-12-30)

579

Parameter
Value Range
Default Value
Description
LAN Neighbor
Dead Time(s)
1 to 65535
40
l LAN Neighbor Dead Time(s) specifies

the dead time of a neighbor router at the
LAN interface.
l If the local router fails to receive the
hello packets from the connected
neighbor router within the time specified
in LAN Neighbor Dead Time(s), it
considers that the neighbor router is
unavailable.
l LAN Neighbor Dead Time(s) should be
set to a value that is a minimum of two
times the value of LAN Neighbor Dead
Time(s).
l In the case of adjacent NEs, DCC
Neighbor Dead Time(s) must be set to
the same value. Otherwise, the OSPF
protocol fails to operate normally.
default value.
LAN
Retransmission
Timer(s)
1 to 65535
l LAN Retransmission Timer(s)

specifies the time for transmitting a
request for retransmission of the LSA
packets through the Ethernet network
management port.
default value.
LAN Delay(s)
1 to 3600
l LAN Delay(s) specifies the delay time

to transmit the LSA packets through the
Ethernet network management port.
l The LSA packets in the LSA database of
the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the age
of the LSA packets based on the value of
LAN Delay(s).
default value.
OSPF Status
Enabled
Disabled
Issue 02 (2012-12-30)
Enabled
Specifies whether the OSPF protocol is

enabled. If an NE uses only static routes
with OSPF disabled, set this parameter to
Disabled.

580

Parameter
Value Range
Default Value
Description
STUB Area
Enabled
Disabled
l Specifies whether to enable the STUB

Area.
Disabled
l Set this parameter as required.

l A backbone area cannot be a STUB area.
NSSA Area
Enabled
Disabled
Disabled
l Specifies whether to enable the NSSA

Area.
l A backbone area cannot be an NSSA
area.
NOTE
OptiX RTN 310 does not support this parameter.
Direct route
Enabled
Disabled
Disabled
l Specifies whether the direct route

automatic flooding function is enabled.
l Direct route: the route detected by the
link layer protocol.
Static route
Enabled
Disabled
Disabled
l Specifies whether the static route

automatic flooding function is enabled.
l Static route: the route manually
configured by the network
administrator.
Default Route
Enabled
Disabled
Disabled
l Specifies whether the default route

automatic flooding function is enabled
for ASBRs.
l Default OSPF routes are routes whose
destination addresses and subnet masks
are 0s.
l Set this parameter according to the
Router ID
The Router IP address is always the NE IP

address.
Opaque LSA of
External Network
Port
Enabled
Enabled
l Specifies whether the Ethernet network

management port transmits Type-10
LSAs.
Disabled
l If this parameter is set to Disabled, the

Ethernet network management port
transmits network management
information.
Issue 02 (2012-12-30)

581

Parameter
Value Range
Default Value
Description
LAN Interface
Enabled
Disabled
l Specifies whether the OSPF protocol is

enabled for the Ethernet network
management port.
Disabled
l If this parameter is set to Enabled, the

OSPF protocol is communicated with
other equipment through the Ethernet
network management port.
OSPF authentication parameters

Parameter
Value Range
Default Value
Description
Interface Type
l Displays the DCN port types that allow

the OSPF authentication key to be
specified.
l LAN indicates the Ethernet network
management port.
l DCC indicates the DCC channels or
inband DCN port.
none
Authentication
Type
none
MD5
l Specifies the OSPF authentication mode

for which a key needs to be set.
l If Authentication Type is MD5, a key
needs to be set for the MD5
authentication mode.
simple
l If Authentication Type is simple, a key

needs to be set for the simple
authentication mode.
l If Authentication Type is none, all
preset keys for the related port type are
cleared.
Authentication
Password
Specifies the OSPF authentication password

for each port type.
MD5 Key
1-255
MD5 Key is available only when

Authentication Type is MD5.
Related Tasks
A.3.6.14 Configuring the OSPF Authentication Type
B.1.2.10 Parameter Description: IP Protocol Stack_Proxy ARP

This topic describes the parameters that are used for configuring the proxy ARP.
Issue 02 (2012-12-30)

582

Parameters for configuring the proxy ARP

Parameter
Value Range
Default Value
Description
Proxy ARP
Disabled
Disabled
l The proxy ARP enables the NEs in the

same network segment but different
domains to communicate with each
other.
Enabled
l To realize communication between such

NEs, the source NE sends the ARP
broadcast packet to address the route to
the destination NE. The NE with the
proxy ARP function enabled checks the
routing table after sensing the ARP
broadcast packet. If the routing table
contains the destination address that the
ARP broadcast packet looks for, the NE
returns an ARP spoofing packet, which
enables the NE that sends the ARP
broadcast packet to consider that the
MAC address of the NE that returns the
ARP spoofing packet is the MAC
address of the destination NE. In this
manner, the packet that is to be sent to
the destination NE is first sent to the NE
with the proxy ARP function enabled
and then forwarded to the destination
NE.
Related Tasks
A.3.6.15 Enabling the Proxy ARP

This topic describes the parameters that are related to management of multiple OSPF areas.
Parameters Required for Configuring Multiple OSPF Areas

Parameter
Value Range
Default Value
Description
ID
Displays the area ID.
Default Area
Displays whether an area is the default area.
Authentication
Type
none
none
MD5
l Specifies the OSPF authentication type

used by an area.
simple
l none indicates no authentication.
Issue 02 (2012-12-30)

583

Parameter
Value Range
Default Value
Description
Automatic Route
Aggregation
Enabled
Disabled
l Specifies whether automatic route

aggregation is enabled for an area.
Disabled
l The number of routes after automatic

route aggregation is the same as the
number of Networks.
Stub Type
Displays the STUB type of an area.
Network Parameters
Parameter
Value Range
Default Value
Description
IP Address
Displays the IP addresses of the Networks

in an area.
Subnet Mask
Displays the subnet masks of the Networks

in an area.
Parameters for Configuring Manual Route Aggregation

Parameter
Value Range
Default Value
Description
IP Address
Displays the IP address of the Network

where route aggregation is manually
enabled.
Subnet Mask
Displays the subnet mask of the Network

where route aggregation is manually
enabled.
Related Tasks
A.3.6.9 Setting OSPF Protocol Parameters
A.3.6.11 Configuring the Network Information of an ABR
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas_Adding

OSPF Areas
This topic describes the parameters that are used for adding OSFP areas.
Issue 02 (2012-12-30)

584

Parameters Required for Creating OSPF Areas

Parameter
Value Range
Default Value
Description
ID
l Set the area ID of a new OSPF area

according to the planning information.
l An NE can be configured with a
maximum of four OSPF areas.
IP Address
l Set the IP addresses of the Networks in

an area according to planning
information.
l An area supports a maximum of four
Networks.
Subnet Mask
Set the subnet masks of the Networks in an

area according to planning information. A
subnet mask can contain a maximum of 30
bits.
Authentication
Type
none
none
Specifies the OSPF authentication type used

by an area according to planning
information.
MD5
simple
l none indicates no authentication.

l MD5 indicates that authentication is
performed based on the preset password,
with the password encrypted in MD5
mode.
l simple: indicates that authentication is
performed based on the preset password,
with the password not encrypted.
Enabled
Automatic Route
Aggregation
Disabled
Disabled
l Specifies whether automatic route

aggregation is enabled for an area.
l The number of routes after automatic
route aggregation is the same as the
number of Networks.
Stub Type
NON-STUB
NON-STUB
STUB
Set the STUB type of an area according to

l For the backbone area, this parameter
must be set to NON-STUB.
NSSA
l For other areas, it is recommended that

you set this parameter to NON-STUB.
Related Tasks
A.3.6.10 Creating an OSPF Area
Issue 02 (2012-12-30)

585

B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding

Routes to Be Manually Aggregated
This topic describes the parameters for adding routes to be manually aggregated.
Parameters for Configuring Manual Route Aggregation

Parameter
Value Range
Default Value
Description
IP Address
Specifies the IP address of the Network

where routes need to be aggregated
manually.
Subnet Mask
Specifies the subnet mask of the Network

where routes need to be aggregated
manually.
Related Tasks
A.3.6.12 Creating a Manual Route Aggregation Group
B.1.2.14 Parameter Description: Port OSPF Setting

This section describes the parameters that are used for setting port OSPF parameters.
Port OSPF Parameters

Parameter
Value Range
Default Value
Description
Port
Displays the ports that allow OSPF

parameters to be set.
Path Type
Displays the current DCC channel type.
OSPF Status
Enabled
Enabled
l Specifies whether to enable the OSPF.

Disabled
Opaque LSA of
External Network
Port
Enabled
Disabled
Enabled
l Specifies whether DCCs support Type10

LSA.
B.1.2.15 Parameter Description: DCN Management_Bandwidth Management

This topic describes the parameters that are used for bandwidth management of the inband DCN.
Issue 02 (2012-12-30)

586

Parameters for Bandwidth Management

Parameter
Value Range
Default Value
Description
Ethernet Board
VLAN ID
2 to 4094
4094
Specifies the VLAN ID used by inband

DCN channels.
l The equipment on the traditional DCN
can be connected to the NMS through the
SCC board, but the OptiX RTN 310 can
also be connected to the NMS through an
Ethernet interface. If an Ethernet port is
used to carry the network management
information, the NE differentiates the
network management information and
Ethernet service information according
to the VLAN ID.
l If the default VLAN ID of the inband
DCN conflicts with the VLAN ID in the
service, the Ethernet Board VLAN ID
of the inband DCN can be changed
manually. The same VLAN ID must be,
however, is used on the network-wide
inband DCN.
Bandwidth(Kbit/s)
64 to 1000
512
Bandwidth(Kbit/s) specifies the bandwidth

for inband DCN messaging on the Ethernet
link.
E1 Port
Bandwidth(Kbit/s)
The OptiX RTN 310 does not support this

parameter.
Tunnel Bandwidth
(Kbit/s)
The OptiX RTN 310 does not support this

parameter.
IF Port Bandwidth
(Kbit/s)
64 to 1000
512
IF Port Bandwidth(Kbit/s) specifies the

bandwidth for inband DCN messaging on
the radio link.
Related Tasks
A.3.6.3 Setting the VLAN ID and Bandwidth for an Inband DCN
B.1.2.16 Parameter Description: DCN Management_Port Setting

This topic describes the parameters that are used for setting ports of the inband DCN.
Parameters for Setting Ports

Parameter
Value Range
Default Value
Description
Port Name
This parameter indicates the port name.
Issue 02 (2012-12-30)

587

Parameter
Value Range
Default Value
Description
Enabled Status
Enabled
l Enabled Status specifies the enabling

status of the port.
Disabled
l The network management information

can be transmitted over the inband DCN
when the DCN function is enabled for
the ports at both ends of a link.
IP
Protocol Type
IP
HWECC
l Specifies the DCN protocol used by the

inband DCN.
l If Protocol Type is set to different
values for two interconnected sets of
equipment, equipment interconnection
fails. Therefore, set Protocol Type to the
same value for both ends of a link.
L2DCN
l OptiX RTN 310 does not support

L2DCN.
-
IP Address
l This parameter is available only when

Protocol Type is set to IP.
parameter specifies the interface IP
address of the non-backbone area port on
the ABR.
Subnet Mask
l This parameter is available only when

Protocol Type is set to IP.
parameter specifies the subnet mask of
the non-backbone area port on the ABR.
Related Tasks
A.3.6.5 Setting a Port for an Inband DCN
B.1.2.17 Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Parameters
Parameter
Value Range
Default Value
Description
Port Name
Displays the Ethernet ports that support this

function.
Issue 02 (2012-12-30)

588

Parameter
Value Range
Default Value
Description
Enabled Status
Disabled
Disabled
l Specifies the enabling status of the port.
Enabled
l If the Enabled Status is set to

Enabled, this port can be used to support
access of the management information
from the NMS.
l If the Enabled Status is set to
Disabled, this port cannot be used to
support access of the management
information from the NMS.
IP Address
0.0.0.0
Specifies the IP address of the port. The port

IP address must be in a network segment
different from the NE IP address.
Subnet Mask
0.0.0.0
Specifies the submask of the port.
Related Tasks
A.3.6.6 Configuring Access Control
B.1.2.18 Parameter Description: DCN Management_Packet Control

This topic describes the parameters for controlling the priority of inband DCN packets.

Parameter
Value Range
Default Value
Description
Packet Type
Displays the packet type for which the

packet priority can be manually specified.
Supported
Application
This parameter cannot be specified

manually.
Packet Priority
CS6
EF (Packet Type is
VLAN)
Specifies the VLAN priorities of inband

DCN packets or the PHBs corresponding to
the DSCP values of the inband DCN
packets.
EF
AF4
AF3
BE (Packet Type is
DSCP)
AF2
AF1
BE
Related Tasks
A.3.6.4 Configuring the Priorities of Inband DCN Packets
Issue 02 (2012-12-30)

589

B.1.2.19 Parameter Description: SNMP Communications Parameters Setting

This topic describes parameters related to SNMP communication.

Parameters
Value Range
Default Value
Description
NMS IP Address
Set NMS IP Address to the IP address of

the SNMP server that uses these
communications parameters. If there are no
restrictions on the IP address of the SNMP
server that accesses the NE, set this
parameter to 0.0.0.0.
Read/Write
Permissions
Read Only
Read Only
Verify Read/Write Permissions of the

SNMP server based on the network plan.
Read/Write Permissions must take the
same values as the right parameters set on
the SNMP server.
Report MW
Performance Trap
Report
No Report
Report IP
Performance Trap
Report
Report Alarm
Trap
Report
Set Report MW Performance Trap,

Report IP Performance Trap, and Report
Alarm Trap to Report if an SNMP server
is required to automatically report trap
packets when the radio performance crosses
the threshold, the data performance crosses
the threshold, or an alarm is generated on an
OptiX RTN 310 NE.
Port
It is recommended that Port take the default

value.
Read Community
Name
Write Community
Nam
Verify Read Community Name, and

Write Community Nam of the SNMP
server based on the network plan. Read
Community Name, and Write
Community Nam must take the same
values as the right parameters set on the
SNMP server.
Traps Version
SNMPV1
Read/Write
No Report
No Report
No Report
No Report
No Report
SNMPV2C
Set Traps Version based on the actual

SNMP version.
Related Tasks
A.3.6.20 Setting SNMP Communication Parameters
B.1.3 Parameters for RADIUS

This topic describes the parameters that are used for Radius.
Issue 02 (2012-12-30)

590


This topic describes the parameters that are related to RADIUS configuration.
Parameters
Parameter
Value Range
Default Value
Description
Function
Server ID
Server Type
Specifies the desired RADIUS function, the

authentication server ID, and the server type.
l Function, Server ID, and Server Type are
associated with the servers that are
configured in A.4.9.2 Creating a RADIUS
Server or a RADIUS Proxy Server.
l Select the desired RADIUS server or proxy
server according to planning information.
Server Status
Active
Active
Standby
Specifies the active/standby status of the

RADIUS server or proxy server.
l If no standby server is required, set Server
Status to Active.
l The OptiX RTN 310 supports one active
server and one standby server. If both the
active and standby servers are configured,
set Server Status of the active server to
Active and Server Status of the standby
server to Standby.
Shared Key
Specifies the key for communication between

an NE and the RADIUS server.
l Set Shared Key to the same value on the
NE and on the RADIUS server.
l If Server Type is Proxy Server, Shared
Key is not available.
Interval of Packet
Transmission
3 to 10
Packet
Retransmission
Attempts
1 to 5
Specifies the number of packet retransmission

attempts and the interval between the attempts.
l If an NE does not receive the response from
the RADIUS server within a specific
period, the NE re-transmits the
authentication request for the configured
attempt times and at the configured
interval.
l It is recommended that Interval of Packet
Transmission and Packet
Retransmission Attempts take their
default values.
Related Tasks
A.4.9.2 Creating a RADIUS Server or a RADIUS Proxy Server
Issue 02 (2012-12-30)

591

A.4.9.3 Configuring RADIUS Server Parameters
B.1.3.2 Parameter Description: Enabling/Disabling the RADIUS Function

This topic describes the parameters that are required for enabling/disabling the RADIUS
function.
Parameters
Parameter
Value Range
Default Value
Description
NE
Displays the NE name.
RADIUS Client
Open
Close
Specifies whether an NE has the ability to be

a RADIUS client. The RADIUS function can
be enabled on an NE only if RADIUS Client
is set to Open for the NE.
Close
Specifies whether an NE has the ability to be

a proxy server.
Close
Proxy Server
Open
Close
l If an NE needs to function as a proxy

server, set Proxy Server to Open for the
NE.
l Proxy Server can be set to Open only if
RADIUS Client is set to Open.
l When an NE uses RADIUS authentication
in the proxy NAS mode, set Proxy
Server to Close.
Related Tasks
A.4.9.1 Enabling/Disabling the RADIUS Authentication Function
B.2 Radio Link Parameters

This topic describes the parameters that are related to radio links.

This section describes the parameters for an IF 1+1 protection group.
Parameters for an IF 1+1 Protection Group

Parameter
Value Range
Default Value
Description
Protection Group
ID
This parameter displays the ID of the IF 1+1

protection group.
Service Protection
Type
This parameter has a fixed value of LAG

Mode.
Issue 02 (2012-12-30)

592

Parameter
Value Range
Default Value
Description
Please confirm the

LAG is already
exist
An enhanced link aggregation group (ELAG) must be configured for OptiX RTN
310s.
Working Mode
HSB
HSB
l This parameter specifies the working

mode of the IF 1+1 protection group.
FD
l If this parameter is set to HSB, 1+1 hot

standby (HSB) is implemented to protect
the OptiX RTN 310s at the two ends of
a hop of radio link.
SD
l If this parameter is set to FD, two

channels with a frequency spacing in
between are used to receive and transmit
the same services, and the receive end
selects only the channel of service
signals with better quality. With 1+1 FD,
the impact of transmission fading is
reduced.
l If this parameter is set to SD, two
antennas at different heights are used to
receive and transmit the same services,
and the receive end selects only the
channel of service signals with better
quality. With 1+1 SD, the impact of
transmission fading is reduced.
l If this parameter is set to FD or SD, HSB
switching is also supported.
l Set this parameter according to the plan.
Revertive Mode
Revertive
Revertive
Non-Revertive
l This parameter specifies the revertive

mode of the IF 1+1 protection group.
l If this parameter is set to Revertive, the
NE releases switching and services are
switched back to the working channel
some time after the working channel is
restored to normal.
l If this parameter is set to NonRevertive, the NE remains in the
switching state even after the working
channel is restored to normal. The
protection channel continues to transmit
services unless another switchover
occurs.
l It is recommended that you set this
parameter to Revertive.
Issue 02 (2012-12-30)

593

Parameter
Value Range
Default Value
Description
Fiber Length (m)
1-300
l Generally, 2 m cascade optical fibers are

used for configuring 1+1 HSB or 1+1
FD, and 20 m cascade optical fibers are
used for configuring 1+1 SD.
l If a customer uses cascade optical fibers
of another length, set this parameter to
the actual length.
WTR Time (s)
300-720
600
l This parameter specifies the WTR time.

l When the working channel remains
normal for WTR Time (s) after being
restored, revertive switching occurs.
l The WTR Time (s) parameter is
available only when Revertive Mode is
set to Revertive.
parameter to the default value.
Enable Reverse
Switching
Enable
Enable
Disable
l This parameter enables or disables

reverse switching.
l If both the main and standby NEs at the
sink end generate service alarms, they
send the alarms to the source end by
using the MWRDI overheads in
microwave frames. If this parameter is
set to Enable at the source end and the
reverse switching conditions are met, an
IF 1+1 protection switchover occurs at
the source end.
l The Enable Reverse Switching
parameter is valid only when Working
Mode is set to HSB or SD.
parameter to the default value Enable.
Working/
Protection Unit
Type
Working Unit
IF Port
Issue 02 (2012-12-30)
Set Working/Protection Unit Type to

Working Unit on the main OptiX RTN
310 and to Protection Unit on the standby
OptiX RTN 310.
This parameter displays the IF port that

participates in IF 1+1 protection.
Protection Unit

594

Parameter
Value Range
Default Value
Description
Service Port
l Set Service port to the Ethernet port that

receives/transmits services. Set this
parameter to the same value as Master
Port that you set during LAG creation.
l The service ports for the main and
standby OptiX RTN 310s must both be
P&E electrical ports or GE optical ports.
NE Switching
Status
l This parameter displays the NE

switching status.
l If you do not query the status or if you
query the status but the status cannot be
found, the value of this parameter is
Unknown.
Channel Switching
Status
l This parameter displays the channel

switching status.
l If you do not query the status or if you
query the status but the status cannot be
found, the value of this parameter is
Unknown.
Device Active NE
This parameter displays the active OptiX

RTN 310 on the NE side.
Device Active Port
This parameter displays the active port on

the NE side.
Channel Active NE
This parameter displays the active OptiX

RTN 310 on the channel side.
Channel Active
Port
This parameter displays the active port on

the channel side.
Enable Switching
upon ETH_LOS
Alarm
When the Ethernet access link of the main

NE becomes faulty, an
ETN_LINK_DOWN or ETH_LOS alarm is
reported. Meanwhile, a 1+1 protection
switchover is triggered by default.
Slot Mapping Parameters

Parameter
Value Range
Default Value
Description
Board
This parameter displays the name of the

main or standby OptiX RTN 310.
IF Port
This parameter displays the name and port

ID of the main or standby OptiX RTN 310.
Issue 02 (2012-12-30)

595

Parameter
Value Range
Default Value
Description
Service Port
This parameter displays the service port ID

of the main or standby OptiX RTN 310.
NE Status
This parameter displays the NE status.
Channel Status
This parameter displays the channel status.
Related Tasks
A.5.3 Creating a Microwave 1+1 Protection Group
A.5.5 Querying the Microwave 1+1 Protection Status

This section describes the parameters for creating a physical link aggregation (PLA) group.
Parameters for Creating a PLA Group

Parameter
Value Range
Default Value
Description
PLA ID
This parameter displays the ID of the PLA

group.
Protection Type
No NE-Level
Protection
No NE-Level
Protection
This parameter specifies the protection type

of the PLA group.
l No NE-Level Protection
NE-Level LAG
Protection
Protects radio links, but not radio

equipment.
l NE-Level LAG Protection
Protects both radio links and radio
equipment.
Please confirm the

LAG is already
exist
Click this link to configure an enhanced link

aggregation group (E-LAG) if Protection
Type is set to No NE-Level Protection.
NE Role
Slave
Slave
l Slave: indicates that the current NE is the

slave NE in the PLA group.
Master
l Master: indicates that the current NE is

the master NE in the PLA group.
IF Port
Issue 02 (2012-12-30)
1-SHXA2-1
(RTNIF-1)
1-SHXA2-1
(RTNIF-1)
This parameter specifies the IF port that

transmits services.

596

Parameter
Value Range
Default Value
Description
Service Port
1-SHXA2-2
(PORT-2)
1-SHXA2-2
(PORT-2)
This parameter specifies the port that

receives/transmits Ethernet services.
l Set Working Mode to the default value
Auto-Negotiation for all service ports.
1-SHXA2-3
(PORT-3)
l If service ports are P&E ports, set

Logical Port Attribute to the default
value Electrical Port.
1-SHXA2-2
(PORT-2)
Cascade Port
1-SHXA2-3
(PORT-3)
1-SHXA2-3
(PORT-3)
Minimum Active
Links Threshold
This parameter specifies the cascade port

that connects the master and slave NEs in the
PLA group.
Before configuring the PLA group, delete
the existing Ethernet services at cascade
ports.
If this parameter is set to 2, LPT switching

can be triggered when one member link in
the PLA group fails.
Related Tasks
A.5.6 Creating a PLA Group
A.5.7 Querying the Status of a PLA Group
B.2.3 Parameters Description: Radio Link Configuration

This topic describes parameters related to radio link management.
Basic Parameters Description

Parameters
Value Range
Default Value
Description
XPIC
Selected
Deselected
This parameter specifies whether the XPIC

function is enabled.
Deselected
Polarization
Direction
This parameter specifies the polarization

direction. This parameter takes effect only
when Polarization Direction is Enabled.
Adjacent NE Link
ID
This parameter specifies the adjacent NE

ID.
Issue 02 (2012-12-30)

597

Parameters
Value Range
Default Value
Description
Link ID
l Link ID indicates or specifies the ID of

a radio link. As the identifier of a radio
link, this parameter is used to prevent
incorrect connections of radio links
between sites.
l If the value of Received Radio Link
ID does not match the preset value at the
local end, the local end inserts the AIS
signal to the downstream direction of the
service. At the same time, the local end
reports MW_LIM alarm to the NMS,
indicating that the link IDs do not match.
l Link ID is set according to the network
plan. Each radio link of an NE should
have a unique link ID, and the link IDs
at both ends of a radio link should be the
same.
Received Link ID
l This parameter indicates the received ID

of the radio link.
l If the value of Received Link ID does
not match the preset value of Link ID at
the local end, the local end inserts the
AIS signal to the downstream direction
of the service. At the same time, the local
end reports an alarm to the NMS,
indicating that the link IDs do not match.
l When the radio link becomes faulty, this
parameter is displayed as an invalid
value.
IF Parameters Description
Parameters
Value Range
Default Value
Description
IF Channel
Bandwidth
7M
7M
IF Channel Bandwidth indicates the

channel spacing of the corresponding radio
link. This parameter is set according to the
network plan.
14M
28M
56M
Issue 02 (2012-12-30)

598

Parameters
Value Range
Default Value
Description
AM
Selected
Deselected
l When DeselectedAM, the radio link

uses only the specified modulation
scheme. In this case, you need to select
Modulation Mode.
Deselected
l When SelectedAM, the radio link uses

the corresponding modulation scheme
according to the channel conditions.
l Hence, it can ensure the reliable
transmission of the services and provide
bandwidth adaptively for the Ethernet
services when the AM function is
enabled.
Modulation Mode
QPSK Strong
QPSK
16QAM Strong
l This parameter specifies the modulation

scheme that the radio link uses for signal
transmission.
l This parameter is valid only when AM
is set to Disabled.
16QAM
32QAM
NOTE
Some modulation modes are not supported in
certain scenarios. For details, see the heading
"Microwave Work Modes" in the Product
Description.
64QAM
128QAM
256QAM
512QAM
512QAM Light
1024QAM
1024QAM Light
2048QAM
Modulation Mode
of the Guaranteed
AM Capacity
QPSK Strong
QPSK
16QAM Strong
16QAM
32QAM
64QAM
128QAM
256QAM
512QAM
512QAM Light
1024QAM
1024QAM Light
2048QAM
Issue 02 (2012-12-30)

is set to Enabled.
l Modulation Mode of the Guaranteed
AM Capacity specifies the lowest-order
modulation scheme that the AM function
supports. This parameter is set according
to the network plan. Generally, the value
of this parameter is determined by the
service transmission bandwidth that the
radio must ensure and the availability of
the radio link that corresponds to this
modulation scheme.
NOTE
Description.

599

Parameters
Value Range
Default Value
Description
Modulation Mode
of the Full AM
Capacity
QPSK Strong

is set to Enabled.
QPSK
l Modulation Mode of the Full AM

Capacity specifies the highest-order
modulation scheme that the AM function
supports. This parameter is set according
to the network plan. Generally, the value
of this parameter is determined by the
bandwidth of the services that need to be
transmitted over the radio and the
availability of the radio link that
corresponds to this modulation scheme.
16QAM Strong
16QAM
32QAM
64QAM
128QAM
256QAM
512QAM
512QAM Light
NOTE
Modulation Mode of the Full AM
Capacity must be higher than Modulation
Mode of the Guaranteed AM Capacity.
1024QAM
1024QAM Light
2048QAM
NOTE
Description.
RF Parameters Description
Parameters
Value Range
Default Value
Description
Tx Frequency
(MHz)
l This parameter indicates or specifies the

transmit frequency of the OptiX RTN
310, namely, the channel central
frequency.
l The value of this parameter must not be
less than the sum of the lower TX
frequency limit supported by the OptiX
RTN 310 and a half of the channel
spacing, and must not be more than the
difference between the upper TX
frequency limit supported by the OptiX
RTN 310 and a half of the channel
spacing.
l The difference between the transmit
frequencies of both the ends of a radio
link should be one T/R spacing.
l This parameter needs to be set according
Rx Frequency
(MHz)
Issue 02 (2012-12-30)
This parameter indicates the actual receive

frequency.

600

Parameters
Value Range
Default Value
Description
T/R Spacing(MHz)
0 to 4294967.295
l This parameter specifies the spacing

between the transmit frequency and the
receive frequency to prevent
interference between them.
l If Station Type is TX high, the TX
frequency is one T/R spacing higher than
the receive frequency. If Station Type is
TX low, the TX frequency is one T/R
spacing lower than the receive
frequency.
l If the OptiX RTN 310 supports only one
T/R spacing, set this parameter to 0,
indicating that the T/R spacing
supported by the OptiX RTN 310 is used.
l A valid T/R spacing value is determined
by the OptiX RTN 310 itself, and the T/
R spacing should be set according to the
technical specifications of the OptiX
RTN 310.
l The T/R spacing of the OptiX RTN 310
should be set to the same value at both
the ends of a radio link.
ATPC
Selected
Deselected
Deselected
l This parameter specifies whether the

ATPC function is enabled.
l If this parameter is set to Enabled and if
the RSL at the receive end is 2 dB higher
or lower than the central value between
the ATPC upper threshold and the ATPC
lower threshold at the receive end, the
receiver notifies the transmitter to
decrease or increase the transmit power
until the RSL is within the range that is
2 dB higher or lower than the central
value between the ATPC upper
threshold and the ATPC lower threshold.
l The settings of the ATPC attributes must
be consistent at both ends of a radio link.
l In the case of areas where fast fading
severely affects the radio transmission, it
is recommended that you set this
parameter to Disabled.
l During the commissioning process, set
this parameter to Disabled to ensure that
the transmit power is not changed. After
the commissioning, re-set the ATPC
attributes.
Issue 02 (2012-12-30)

601

Parameters
Value Range
Default Value
Description
ATPC Upper
Threshold(dBm)
-85 to -20
ATPC Lower
Threshold(dBm)
-90 to -25
l Set the central value between the ATPC

upper threshold and the ATPC lower
threshold to a value for the expected
receive power.
l It is recommended that you set ATPC
Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
value between the ATPC upper
threshold and the ATPC lower threshold
and 10 dB.
TX Power(dBm)
-10 to 24

transmit power of the OptiX RTN 310.
This parameter cannot be set to a value
that exceeds the nominal power range of
the OptiX RTN 310.
l This parameter cannot take a value
greater than the preset value of
Maximum Transmit Power(dBm).
l It is recommended that you set the
transmit power of the OptiX RTN 310 to
the same value at both ends of a radio
link.
l Consider the receive power of the OptiX
RTN 310 at the opposite end when you
set this parameter. Ensure that the
receive power of the OptiX RTN 310 at
the opposite end can ensure stable radio
services.
l This parameter needs to be set according
Power to Be
Received(dBm)
-10, or -90 to -20
This parameter is set according to the

network plan.
RX Power(dBm)
This parameter indicates the actual receive

power of the the OptiX RTN 310.
TX Status
Unmute
Unmute
This parameter indicates the actual transmit

status of the OptiX RTN 310.
Mute
Issue 02 (2012-12-30)

602

Equip information Description

Parameters
Value Range
Default Value
Description
Frequency(GHz)
This parameter indicates the frequency band

where the OptiX RTN 310 operates.
Equip Type
This parameter indicates the equipment type

of the OptiX RTN 310.
Station Type
l This parameter indicates whether the

OptiX RTN 310 is a Tx high station or a
Tx low station.
l The transmit frequency of a Tx high
station is one T/R spacing higher than the
transmit frequency of a Tx low station.
Product SN
This parameter indicates the manufacturing

serial number and the manufacturer code of
the OptiX RTN 310.
RF Type
This parameter indicates the level of the

output power of the OptiX RTN 310.
Related Tasks
A.5.1 Configuring a Single Hop of Microwave Link
B.3 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces.
B.3.1 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports.
B.3.1.1 Parameter Description: Ethernet Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of an Ethernet interface.

Parameter
Value Range
Default Value
Description
Port
Displays the port name.
Name
Specifies the port name.
Issue 02 (2012-12-30)

603

Parameter
Value Range
Default Value
Description
Enable Port
Enabled
Enabled
l Specifies whether an
Ethernet port is
enabled. An Ethernet
port can receive,
process, and forward
Ethernet services only
if this parameter is set
to Enabled.
Disabled
l Set this parameter

according to the
Port Mode
Layer 2
Layer 2
The OptiX RTN 310

supports only Layer 2.
Encapsulation Type
Null
Null
l Encapsulation Type
specifies the method of
the port to process the
received packets.
802.1Q
QinQ
l If you set
Encapsulation Type
to Null, the port
transparently
transmits the received
packets.
l If you set
Encapsulation Type
to 802.1Q, the port
identifies the packets
that comply with the
IEEE 802.1q standard.
l If you set
Encapsulation Type
to QinQ, the port
identifies the packets
that comply with the
IEEE 802.1ad QinQ
standard. The OptiX
RTN 310 does not
support QinQ.
Issue 02 (2012-12-30)

604

Parameter
Value Range
Default Value
Description
Working Mode
Auto-Negotiation
Auto-Negotiation
l The Ethernet ports of

different types support
different Working
Mode.
10M Full-Duplex
100M Full-Duplex
1000M Full-Duplex
l When the equipment

on the opposite side
works in autonegotiation mode, set
the Working Mode of
the equipment on the
local side to AutoNegotiation.
works in full-duplex
mode, set the
Working Mode of the
equipment on the local
side to 10M FullDuplex, 100M FullDuplex, or 1000M
Full-Duplex
depending on the port
rate of the equipment
on the opposite side.
Max Frame Length

(byte)
1518 to 9600
9600
The value of Max Frame

Length(byte) should be
greater than the length of
any frame to be
transported.
Auto-Negotiation
Ability
10M Half-Duplex
1000M Full-Duplex
l Auto-Negotiation
Ability specifies the
auto-negotiation
capability of the
Ethernet port.
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
1000M Full-Duplex
1000M Half-Duplex
l For GE optical ports,

Auto-Negotiation
Ability can be set to
1000M Full-Duplex
only.
l Auto-Negotiation
Ability is valid only
when Working Mode
is set to AutoNegotiation.
Issue 02 (2012-12-30)

605

Parameter
Value Range
Default Value
Description
Logical Port Attribute
Optical Port

the attribute of the logical
port.
Electrical Port
Physical Port Attribute

the attribute of the
physical port.
Running Status

the running status of the
Ethernet link.
Traffic Policing Status
Enabled
Disabled

the enabled status of the
traffic monitoring
function over an Ethernet
port.
15

the traffic monitoring
period.
Disabled
Traffic Policing Period

(min)
1 to 30
Related Tasks
A.6.1.1 Setting the Basic Attributes for an Ethernet Port
B.3.1.2 Parameter Description: Ethernet Interface_Flow Control

This topic describes the parameters that are related to flow control.

Parameter
Value Range
Default Value
Description
Port

the port name.
Issue 02 (2012-12-30)

606

Parameter
Value Range
Default Value
Description
Non-Autonegotiation
Flow Control Mode
Disabled
Disabled
l Non-Autonegotiation
Flow Control Mode is
valid only when
Working Mode is not
set to AutoNegotiation.
Enable Symmetric Flow

Control
Send Only
Receive Only
l Non-Autonegotiation
Flow Control Mode
of the equipment on
the local side must be
consistent with the
non-autonegotiation
flow control mode of
opposite side
l The OptiX RTN 310
supports only two nonauto-negotiation flow
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
Auto-Negotiation Flow
Control Mode
Disabled
Disabled
Enable Symmetric Flow

Control
Enable Dissymmetric
Flow Control
Enable Symmetric/
Dissymmetric Flow
Control
l Auto-Negotiation
Flow Control Mode is
valid only when
Working Mode is set
to Auto-Negotiation.
l Auto-Negotiation
Flow Control Mode
of the equipment on
the local side must be
consistent with the
auto-negotiation flow
control mode of the
equipment on the
opposite side
l The OptiX RTN 310
supports only two
auto-negotiation flow
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
Issue 02 (2012-12-30)

607

Related Tasks
A.6.1.2 Configuring the Traffic Control Function for an Ethernet Port
B.3.1.3 Parameter Description: Ethernet Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes.

Parameter
Value Range
Default Value
Description
Port

the port name.
QinQ Type Domain
The OptiX RTN 310 does

not support this
parameter.
Tag
Tag Aware
Hybrid
l If all the accessed

services are frames
with the VLAN tag
(tagged frames), set
TAG to Tag Aware.
Access
Hybrid

services are frames
without the VLAN tag
(untagged frames), set
TAG to Access.
l If the accessed
services contain
tagged frames and
untagged frames, set
TAG to Hybrid.
NOTE
TAG specifies the TAG
flag of a port. For details
about the TAG flags and
associated frameprocessing methods, see
Table B-1.
Default VLAN ID
1 to 4094
l Default VLAN ID is
valid only when TAG
is set to Access or
Hybrid.
set according to the
actual situations.
NOTE
For details about the
functions of Default VLAN
ID, see Table B-1.
Issue 02 (2012-12-30)

608

Parameter
Value Range
Default Value
Description
VLAN Priority
0 to 7
l VLAN Priority is
valid only when TAG
is set to Access or
Hybrid.
l When the VLAN
priority is required to
divide streams or to be
used for other
purposes, VLAN
Priority is set
according to the
In normal cases, it is
use the default value.
NOTE
For details about the
functions of VLAN
Priority, see Table B-1.
Table B-1 Methods used by Ethernet interfaces to process data frames

Port
Ingress UNI
Issue 02 (2012-12-30)
Type of Data
Frame
Processing Method
Tag Aware
Access
Hybrid
Tagged frame
The port receives the

frame.
The port discards

the frame.
The port receives

the frame.
Untagged frame
The port discards the

frame.
The ports add the

VLAN tag, to which
Default VLAN ID
and VLAN
Priority
correspond, to the
frame and receive
the frame.
The ports add the

VLAN tag, to which
Default VLAN ID
and VLAN
Priority
correspond, to the
frame and receive
the frame.

609

Port
Egress UNI
Type of Data
Frame
Processing Method
Tag Aware
Access
Hybrid
Tagged frame
The port transmits

the frame.
The port strips the

VLAN tag from the
frame and then
transmits the frame.
l If the VLAN ID
in the frame is
Default VLAN
ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Related Tasks
A.6.1.3 Setting the Layer 2 Attributes for an Ethernet Port
B.3.1.4 Parameter Description: Ethernet Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes.

Parameter
Value Range
Default Value
Description
Port

the port name.
Port Physical
Parameters

the physical parameters of
the port.
Issue 02 (2012-12-30)

610

Parameter
Value Range
Default Value
Description
MAC Loopback
Non-Loopback
Non-Loopback
l This parameter
specifies the loopback
state at the MAC layer.
When this parameter is
set to Inloop, the
Ethernet signals
transmitted to the
opposite end are
looped back.
Inloop
Outloop
l In normal cases, it is
l OptiX RTN 310 does
not support Outloop.
PHY Loopback
Non-Loopback
Non-Loopback
Inloop
Outloop
l This parameter
specifies the loopback
state at the PHY layer.
When this parameter is
set to Inloop, the
Ethernet signals
transmitted to the
opposite end are
looped back.
l In normal cases, it is
l OptiX RTN 310 does
not support Outloop.
MAC Address

the MAC address of the
port.
Transmitting Rate(kbit/
s)

the rate at which the data
packets are transmitted.
Receiving Rate(kbit/s)

the rate at which the data
packets are received.
Loopback Check
Enabled
Disabled

whether to enable loop
detection, which is used to
check whether a loop
exists on the port.
Disabled

whether to enable the loop
port shutdown function.
Disabled
Loopback Port Block
Enabled
Disabled
Issue 02 (2012-12-30)

611

Parameter
Value Range
Default Value
Description
Egress PIR Bandwidth

(kbit/s)

the egress PIR bandwidth.
Broadcast Packet
Suppression
Disabled
Disabled
l This parameter
limit the traffic rate of
the broadcast packets
according to the
proportion of the
broadcast packets in
the total packets.
When the equipment at
the opposite end may
encounter a broadcast
storm, this parameter
is set to Enabled.
Enabled
l If Ethernet services are

E-LAN services, the
recommended value is
Enabled.
l This parameter takes
effect only for E-LAN
services in the ingress
direction.
Broadcast Packet
Suppression Threshold
0 to 100
30
When the proportion of

the broadcast packets in
the total packets exceeds
the value of this
parameter, the received
broadcast packets are
discarded. The value of
this parameter should be
more than the proportion
of the broadcast packets in
the total packets before
the broadcast storm
occurs. In normal cases,
this parameter is set to
default value.
Network Cable Mode
This parameter displays

the working mode of the
network cable connected
to an Ethernet port.
Optical Module Type

the optical module type.
POE
OptiX RTN 310 does not

support this parameter.
Issue 02 (2012-12-30)

612

Related Tasks
A.6.1.4 Setting the Advanced Attributes for an Ethernet Port
B.3.2 Microwave Interface Parameters

This topic describes the parameters that are related to Microwave interfaces.
B.3.2.1 Parameter Description: Microwave Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of microwave
interfaces.
Parameters
Parameter
Value Range
Default Value
Description
Port
This parameter indicates the corresponding

IF port.
Name
This parameter indicates or specifies the

customized port name.
Port Mode
Layer 2
Layer 2
The OptiX RTN 310 supports only Layer

2.
Encapsulation
Type
Null
802.1Q
l Encapsulation Type specifies the

method of the port to process the
received packets.
802.1Q
QinQ
l If Encapsulation Type is set to Null, the

port transparently transmits the received
packets.
l If Encapsulation Type is set to
802.1Q, the port identifies the packets
that comply with the IEEE 802.1Q
standard.
l If Encapsulation Type is set to QinQ,
the port identifies the packets that
comply with the IEEE 802.1ad QinQ
standard. The OptiX RTN 310 does not
support QinQ.
Traffic Policing
Status
Enabled
Traffic Policing
Period (min)
Running Status
Issue 02 (2012-12-30)
Disabled
This parameter indicates the enabled status

of the traffic monitoring function over an
Ethernet port.
1 to 30
15
This parameter indicates the traffic

monitoring period.
This parameter indicates the running status

of the radio link.
Disabled

613

Related Tasks
A.6.2.1 Setting Basic Attributes for a Microwave Port
B.3.2.2 Parameter Description: Microwave Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes of microwave
interfaces.
Parameters for Layer 2 Attributes

Parameter
Value Range
Default Value
Description
Port

IF port.
Tag
Tag Aware
Hybrid
l If all the accessed services are frames

that contain the VLAN tag (tagged
frames), set Tag to "Tag Aware".
Access
Hybrid
l If all the accessed services are frames

that do not contain the VLAN tag
(untagged frames), set Tag to "Access".
l If the accessed services contain tagged
"Hybrid".
NOTE
Tag specifies the TAG flag of a port. For details
about the TAG flags and associated frameprocessing methods, see Table B-2.
Default VLAN ID
1 to 4094
l Default VLAN ID is valid only when

TAG is set to Access or Hybrid.
l Default VLAN ID needs to be set
according to the actual situations.
NOTE
For details about the functions of Default VLAN
ID, see Table B-2.
VLAN Priority
0
1
2
3
4
5
6
7
Issue 02 (2012-12-30)
l VLAN Priority is valid only when

TAG is set to Access or Hybrid.
l When the VLAN priority is required to
divide streams or to be used for other
purposes, VLAN Priority needs to be set
according to the planning information. In
normal cases, it is recommended that you
NOTE
For details about the functions of VLAN
Priority, see Table B-2.

614

Table B-2 Data frame processing

Status
Ingress Port
Egress Port
Type of Data
Frame
Processing Method
Tag Aware
Access
Hybrid
Tagged frame
The port receives the

frame.
The port discards

the frame.
The port receives

the frame.
Untagged frame
The port discards the

frame.
The port receives

the frame after the
VLAN tag that
corresponds to
"Default VLAN ID"
and "VLAN
Priority" is added to
the frame.
The port receives

the frame after the
VLAN tag that
corresponds to
"Default VLAN ID"
and "VLAN
Priority" is added to
the frame.
Tagged frame
The port transmits

the frame.
The port strips the

VLAN tag from the
frame and then
transmits the frame.
l If the VLAN ID
in the frame is
"Default VLAN
ID", the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not "Default
VLAN ID", the
port directly
transmits the
frame.
Related Tasks
A.6.2.2 Setting Layer 2 Attributes for a Microwave Port
B.3.2.3 Parameter Description: Microwave Interface_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of microwave
interfaces.
Parameters for Advanced Attributes

Parameter
Value Range
Default Value
Description
Port

microwave port.
Issue 02 (2012-12-30)

615

Parameter
Value Range
Default Value
Description
MAC Address
This parameter indicates the MAC address

of the port.
Speed
Transmission at
L2
Disabled
Disabled
l If Speed Transmission at L2 is set to

Enabled, the Layer-2 Ethernet packets
transmitted at microwave ports will be
compressed to improve transmission
efficiency.
Enabled
l The settings of Speed Transmission at

L2 must be the same at both ends of a
radio link.
Speed
Transmission at
L3
Disabled
Disabled
Enabled
l If Speed Transmission at L3 is set to

Enabled, the IP packets transmitted at
microwave ports will be compressed to
improve transmission efficiency.
l The settings of Speed Transmission at
L3 must be the same at both ends of a
radio link.
Loopback Check
Disabled
Disabled
This parameter specifies whether to enable

loop detection, which is used to check
whether a loop exists on the port.
Disabled
This parameter indicates whether to enable

the automatic shut-down of looped ports.
Disabled
l This parameter specifies whether to limit

the traffic rate of the broadcast packets
according to the proportion of the
broadcast packets in the total packets.
When the equipment at the opposite end
may encounter a broadcast storm, this
parameter is set to Enabled.
Enabled
Loopback Port
Block
Disabled
Broadcast Packet
Suppression
Disabled
Enabled
Enabled
l If Ethernet services are E-LAN services,

the recommended value is Enabled.
l This parameter takes effect only for ELAN services in the ingress direction.
Broadcast Packet
Suppression
Threshold
Issue 02 (2012-12-30)
0 to 100
30
When the proportion of the broadcast

packets in the total packets exceeds the value
of this parameter, the received broadcast
packets are discarded. The value of this
parameter should be more than the
proportion of the broadcast packets in the
total packets before the broadcast storm
occurs. In normal cases, this parameter is set
to default value.

616

Related Tasks
A.6.2.3 Setting Advanced Attributes for a Microwave Port
B.4 Parameters for Ethernet Services and Ethernet Features

This section describes the parameters for the Ethernet services and Ethernet features, including
service parameters, protocol parameters, OAM parameters, and QoS parameters.
B.4.1 Parameters for Ethernet Services

This topic describes the parameters that are related to Ethernet services.

This topic describes the parameters that are related to E-Line services.
Basic Information
Parameter
Value Range
Default Value
Description
Service ID

the ID of the E-Line
service. The ID of each
service must be unique.
Service Name

or specifies the name of
the E-Line service.
Direction

the direction of the E-Line
service.
Issue 02 (2012-12-30)

617

Parameter
Value Range
Default Value
Description
L2 Protocol Control
Not Transparent
Not Transparent
l For point-to-point
transparently
transmitted services,
this parameter takes
the fixed value Not
Transparent.
BPDU Packet Transparent

LACP Packet Transparent
l For an E-Line service

transparently
transmitting LACP
packets from other
equipment, set this
parameter to LACP
Packet Transparent.
l For an E-Line service
transparently
transmitting BPDU
packets from other
equipment, set this
parameter to BPDU
Packet Transparent.
Source

the source node of the ELine service.
Sink

the sink node of the ELine service.
Parameters for the Port Attributes

Parameter
Value Range
Default Value
Description
Port
Displays the port

information.
Port Enable
Enabled
l This parameter
displays or specifies
whether the port is
enabled.
Disabled
l Ethernet services can

be received,
processed, and
forwarded normally
only if Port Enable is
set to Enabled.
Issue 02 (2012-12-30)

618

Parameter
Value Range
Default Value
Description
VLAN ID(e.g.1,3-5)

according to the
network plan.
l If this parameter has
different values at the
source and the sink, a
VLAN forwarding
table needs to be
configured.
Working Mode
Auto-Negotiation
10M Full-Duplex
100M Full-Duplex
1000M Full-Duplex

different working
modes.
the working mode of
mode, set the working
mode of the equipment
on the local side to
10M Full-Duplex,
100M Full-Duplex, or
1000M Full-Duplex
Issue 02 (2012-12-30)

619

Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
the method of the port
to process the received
packets.
802.1Q
QinQ
l If you set this

parameter to Null, the
port transparently
packets.
l If you set this
parameter to 802.1Q,
the port processes
received packets based
on its tag attribute.
l For a point-to-point
transparently
transmitted E-Line
service, this parameter
takes a fixed value
Null.
l For a VLAN-based ELine service, this
parameter takes a fixed
value 802.1Q.
l The OptiX RTN 310
does not support
QinQ.
Tag
Tag Aware
Access
Hybrid

services are frames
with the VLAN tag
TAG to Tag Aware.
services are frames
TAG to Access.
l If the accessed
services contain
tagged frames and
TAG to Hybrid.
effect only when
Encapsulation Type
is 802.1Q.
Issue 02 (2012-12-30)

620

Parameter
Value Range
Default Value
Description
Default VLAN ID
1 to 4094
valid only when TAG
is set to Access or
Hybrid.
actual situations.
OAM Parameters
Parameter
Value Range
Default Value
Description
AIS Active Status
Active
Inactive
l This parameter specifies the AIS active

status.
Inactive
l If several MDs exist on a link, to locate

a fault accurately, set AIS Active
Status to Active and Client Layer
Level that functions to suppress the AIS
information.
l After a fault is detected by an MP, if this
MP activates the AIS, it sends the AIS
packet to a higher level MP, informing
the higher level MP of the fault
information; if this MP does not activate
the AIS, it does not report the fault.
Client Layer Level
1 to 7
l Normally, if an MP is set to level n, it is

recommended that you set Client Layer
information to n+1.
l Client Layer Level is valid only if AIS
Active Status is Active.
Parameters for VLAN Forwarding Table Item

Parameter
Value Range
Default Value
Description
Source Interface
Type
V-UNI
V-UNI
This parameter specifies the network

attribute of the source interface.
Source Interface
This parameter specifies the source

interface.
Source VLAN ID
1 to 4094
This parameter specifies the VLAN ID of

the source service.
Issue 02 (2012-12-30)

621

Parameter
Value Range
Default Value
Description
Sink Interface
Type
V-UNI
V-UNI
This parameter specifies the network

attribute of the sink interface.
Sink Interface
This parameter specifies the sink interface.
Sink VLAN ID
1 to 4094
This parameter specifies the VLAN ID of

the sink service.
Related Tasks
A.7.3.1 Creating a Point-to-Point Transparently Transmitted E-Line Service
A.7.3.2 Creating a VLAN-based E-Line Service
A.7.3.3 Creating an E-Line Service for Transmitting Layer 2 Protocol Packets
A.7.3.4 Creating VLAN Forwarding Table Entries

This topic describes the parameters that are related to E-LAN services.
Basic Information
Parameter
Value Range
Default Value
Description
Service ID

the ID of the E-LAN
service.
Service Name

the name of the E-LAN
service.
Issue 02 (2012-12-30)

622

Parameter
Value Range
Default Value
Description
Tag Type
Tag-Transparent
Tag-Transparent
l C-Awared indicates
that the packets are
learnt according to CTag (the VLAN tag on
the client-side). To
create the 802.1q
bridge, set this
parameter to CAwared.
C-Awared
l Tag-Transparent
indicates that the
packets are
transparently
transmitted. To create
the 802.1d bridge, set
this parameter to TagTransparent.
according to the
L2 Protocol Control
Not Transparent
Not Transparent
BPDU Packet Transparent

LACP Packet Transparent
l For an IEEE 802.1d

bridge/802.1q bridgebased E-LAN service
transmitting service
signals, this parameter
takes a fixed value Not
Transparent.
l For an IEEE 802.1q
bridge-based E-LAN
service transparently
transmitting LACP
packets from other
equipment, this
value LACP Packet
Transparent.
l For an IEEE 802.1q
bridge-based E-LAN
service transparently
transmitting BPDU
packets from other
equipment, this
value BPDU Packet
Transparent.
Issue 02 (2012-12-30)

623

Parameter
Value Range
Default Value
Description
Self-Learning MAC
Address
Enabled
Enabled
l This parameter
indicates whether to
enable the MAC
address self-learning
function.
Disabled
l If the MAC selflearning function of an

Ethernet LAN is
enabled, the Ethernet
LAN learns an MAC
address according to
the original MAC
address in the packet
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC selflearning function of an
Ethernet LAN is
disabled, a static MAC
address forwarding
table is recommended
to be configured.
Mode

the mode used to learn an
MAC address.
Parameter
Value Range
Default Value
Description
Port
Displays the port

information.
Port Enable
Enabled
l This parameter
whether the port is
enabled.
Port Attributes
Disabled
l Ethernet services can

be received,
processed, and
forwarded normally
only if Port Enable is
set to Enabled.
Issue 02 (2012-12-30)

624

Parameter
Value Range
Default Value
Description
VLAN ID(e.g.1,3-5)

according to the
network plan.
l This parameter must
have the same value at
the source and sink
ends.
Working Mode
Auto-Negotiation
10M Full-Duplex
100M Full-Duplex
1000M Full-Duplex

different working
modes.
the working mode of
mode, set the working
mode of the equipment
on the local side to
10M Full-Duplex,
100M Full-Duplex, or
1000M Full-Duplex
Issue 02 (2012-12-30)

625

Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
the method of the port
to process the received
packets.
802.1Q
QinQ
l If you set this

parameter to Null, the
port transparently
packets.
l If you set this
parameter to 802.1Q,
the port processes
received packets based
on its tag attribute.
l For IEEE 802.1d
bridge-based E-LAN
services, this
parameter takes the
fixed value Null.
l For IEEE 802.1q
bridge-based E-LAN
services, this
parameter takes the
fixed value 802.1Q.
l The OptiX RTN 310
does not support
QinQ.
Tag
Tag Aware
Access
Hybrid

services are frames
with the VLAN tag
TAG to Tag Aware.
services are frames
TAG to Access.
l If the accessed
services contain
tagged frames and
TAG to Hybrid.
effect only when
Encapsulation Type
is 802.1Q.
Issue 02 (2012-12-30)

626

Parameter
Value Range
Default Value
Description
Default VLAN ID
1 to 4094
valid only when TAG
is set to Access or
Hybrid.
actual situations.
Parameters for the Split Horizon Group

Parameter
Value Range
Default Value
Description
Split Horizon Group ID
l This parameter
indicates the ID of the
split horizon group.
l The default split
horizon group ID is 1
and cannot be set
manually.
Split Horizon Group

Member
l A split horizon group

member indicates the
logical port member in
the split horizon
group.
l The ports that are
added to the same split
horizon group cannot
communicate with
each other.
l The supports only the
division of the split
horizon group
members according to
the Ethernet physical
port.
Issue 02 (2012-12-30)

627

OAM Parameters
Parameter
Value Range
Default Value
Description
AIS Active Status
Active
Inactive

status.
Inactive

information.
Client Layer Level
1 to 7

information to n+1.

Parameters for Static MAC Addresses

Parameter
Value Range
Default Value
Description
VLAN ID
l This parameter is
invalid if MAC
Address Learning
Mode is SVL. That is,
the preset static MAC
address entries are
valid for all VLANs.
l If MAC Address
Learning Mode is set
to IVL, the preset
static MAC address
entries are valid for
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the
Issue 02 (2012-12-30)

628

Parameter
Value Range
Default Value
Description
MAC Address
l This parameter
indicates or specifies
the static MAC
address.
l A static MAC address
is an address that is set
manually. It is not
aged automatically
and needs to be deleted
manually.
l Generally, a static
MAC address is used
for the port that
receives but does not
forward Ethernet
service packets or for
the port whose MAC
address does not need
to be aged
automatically.
Egress Interface
l This parameter
specifies the Ethernet
port that corresponds
to the MAC address.
according to the
Issue 02 (2012-12-30)

629

Parameters for Self-Learning MAC Address

Parameter
Value Range
Default Value
Description
VLAN ID
l This parameter is
invalid if MAC
Address Learning
Mode is SVL. That is,
the preset self-learning
MAC address entries
are valid for all
VLANs.
l If MAC Address
Learning Mode is set
to IVL, the preset selflearning MAC address
entries are valid for
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the
MAC Address
l This parameter
the self-learning MAC
address. A selflearning MAC address
is also called a
dynamic MAC
address.
l A self-learning MAC
address is an entry
obtained by a bridge in
SVL or IVL learning
mode. A self-learning
MAC address can be
aged.
Egress Interface
l This parameter
specifies the Ethernet
port that corresponds
to the MAC address.
according to the
Issue 02 (2012-12-30)

630

Parameters Associated with MAC Address Learning

Parameter
Value Range
Default Value
Description
Aging Ability
Enabled
Enabled
The OptiX RTN 310

supports enabling/
disabling of the aging
function and aging time
for the MAC address
table.
If one routing entry is not
updated in a certain
period, that is, if no new
packet from this MAC
address is received to
enable the re-learning of
this MAC address, this
routing entry is
automatically deleted.
This mechanism is called
aging, and this period is
called aging time. The
aging time of a MAC
address table is 5 minutes
by default.
Disabled
Aging Time(min)
1 to 640
Parameters for Disabled MAC Addresses

Parameter
Value Range
Default Value
Description
VLAN ID

or specifies the VLAN ID
of the service. A disabled
MAC address is valid for
the VLAN whose VLAN
ID is equal to the preset
VLAN ID.
Issue 02 (2012-12-30)

631

Parameter
Value Range
Default Value
Description
MAC Address
l This parameter
specifies or indicates
the disabled MAC
address. A disabled
MAC address is also
called a blacklisted
MAC address.
l This parameter is used
for discarding an
entry, also called a
black hole entry,
whose data frame that
contains a specific
MAC address. A
disabled MAC address
needs to be set
manually and cannot
be aged.
Parameters for Unknown Frame Processing

Parameter
Value Range
Default Value
Description
Frame Type
Unicast

the type of the received
unknown frame.
Broadcast
Selects the method of

processing the unknown
frame. If this parameter is
set to Discard, the
unknown frame is directly
discarded. If this
parameter is set to
Broadcast, the unknown
frame is broadcast at the
forwarding port.
Multicast
Handing Mode
Discard
Broadcast
Related Tasks
A.7.3.5 Creating an IEEE 802.1D Bridge-based E-LAN Service
A.7.3.6 Creating an IEEE 802.1Q Bridge-based E-LAN Service
A.7.3.7 Creating an E-LAN Service for Transmitting Layer 2 Protocol Packets
A.7.3.8 Configuring a Split Horizon Group
A.7.4.1 Creating a Static MAC Address Entry
A.7.4.2 Creating a Blacklist MAC Address Entry
Issue 02 (2012-12-30)

632

A.7.4.3 Managing a Dynamic MAC Address Table

A.7.5 Setting the Mode for Processing an Unknown Frame of an E-LAN Service
B.4.2 Parameters for Ethernet Protocols

This topic describes the parameters that are related to the Ethernet protocol.

This topic describes the parameters that are used for Ethernet ring protection switching (ERPS)
management.
Parameters
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 8
The IDs of ERPS

instances on an NE must
be different from each
other.
East Port

or specifies the east port of
the ERPS instance.
West Port

or specifies the west port
of the ERPS instance.
RPL Owner Ring Node

Flag
Yes
No
l This parameter
whether the node on
the ring is the ring
protection link (RPL)
owner.
No
l Only one node on the

ring can be set as the
RPL owner for each
Ethernet ring.
l An RPL owner needs
to balance the traffic
on each link of an
Ethernet ring.
Therefore, it is not
select a convergence
node as an RPL owner.
Instead, select the NE
that is farthest away
from the convergence
node as an RPL owner.
Issue 02 (2012-12-30)

633

Parameter
Value Range
Default Value
Description
RPL Port
l There is only one RPL

port and this RPL port
must be the east or
west port on the RPL
owner node.
you set the east port on
an RPL owner as an
RPL Port.
Control VLAN
1 to 4094
l This parameter
the VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring transmits
the R-APS packets on
the dedicated ring APS
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
isolating the dedicated
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
that are contained in
the service packets or
inband DCN packets.
l The Control VLAN
must be set to the same
value for all the NEs
on an ERPS ring.
Destination Node
01-19-A7-00-00-01
01-19-A7-00-00-01

the MAC address of the
destination node. The
default destination MAC
address in the R-APS
packets is always 01-19A7-00-00-01.
Current Node

the current node.
Issue 02 (2012-12-30)

634

Parameter
Value Range
Default Value
Description
Hold-Off Time(ms)
0 to 10000, in step of 100
l This parameter
the hold-off time of the
ERPS hold-off timer.
l The hold-off timer is
used for negotiating
the protection
switching sequence
when the ERPS
coexists with other
protection schemes so
that the fault can be
rectified in the case of
other protection
switching (such as
LAG protection)
before the ERPS
occurs. When a node
on the ring detects one
or more new faults, it
starts up the hold-off
timer if the preset
hold-off time is set to a
value that is not 0.
During the hold-off
time, the fault is not
reported to trigger an
ERPS. When the holdoff timer times out, the
node checks the link
status regardless
whether the fault that
triggers the startup of
the timer exists. If the
fault exists, the node
reports it to trigger an
ERPS. This fault can
be the same as or
different from the fault
that triggers the initial
startup of the hold-off
timer.
Issue 02 (2012-12-30)

635

Parameter
Value Range
Default Value
Description
Guard Time(ms)
10 to 2000, in step of 10
500
l This parameter
the guard time of the
ERPS guard timer.
l The nodes on the ring
continuously forward
the R-APS packets to
the Ethernet ring. As a
result, the outdated RAPS packets may exist
on the ring network.
After a node on the
ring receives the
outdated R-APS
packets, an incorrect
ERPS may occur. The
ERPS guard timer is an
R-APS timer used for
preventing a node on
the ring from receiving
outdated R-APS
packets. When a faulty
node on the ring
detects that the
switching condition is
cleared, the node starts
up the guard timer and
starts to forward the RAPS (NR) packets.
During this period, the
R-APS packets
received by the node
are discarded. The
received R-APS
packets are forwarded
only after the time of
the guard timer
expires.
Issue 02 (2012-12-30)

636

Parameter
Value Range
Default Value
Description
WTR Time(mm:ss)
5 to 12, in step of 1
l This parameter
the WTR time of the
WRT timer in the case
of ERPS protection.
l The WTR time refers
to the duration from
the time when the
working channel is
restored to the time
when the switching is
released. When the
working channel is
restored, the WTR
timer of the RPL
owner starts up. In
addition, a signal that
indicates the operation
of the WTR timer is
continuously output in
the timing process.
When the WTR timer
times out and no
switching request of a
higher priority is
received, the signal
indicating the
operation of the WTR
timer is not
transmitted. In
addition, the WTR
release signal is
continuously output.
l The WTR timer is used
to prevent frequent
switching caused by
the unstable working
channel.
Packet Transmit
Interval(s)
1 to 10
This parameter displays or

specifies the interval for
sending R-APS packets
periodically.
Entity Level
0 to 7

or specifies the level of the
maintenance entity.
Last Switching Request

the last switching request.
Issue 02 (2012-12-30)

637

Parameter
Value Range
Default Value
Description
RB Status

the RB (RPL Blocked)
status of the packets
received by the working
node.
l noRB: The RPL is not
blocked.
l RB: The RPL is
blocked.
DNF Status

the DNF status of the
packets received by the
working node.
l noDNF: The R-APS
packets do not contain
the DNF flag. In this
case, the packets are
forwarded by the node
that detects the fault on
a non-RPL link, and
the node that receives
the packets is
requested to clear the
forwarding address
table.
l DNF: The R-APS
packets contain the
DNF flags. In this
case, the packets are
forwarded by the node
that detects the fault on
an RPL link, and the
node that receives the
packets is informed
not to clear the
forwarding address
table.
Issue 02 (2012-12-30)

638

Parameter
Value Range
Default Value
Description
State Machine Status

the status of the state
machine at the working
node.
l Idle: The Ethernet ring
is in normal state. For
example, no node on
the Ethernet ring
detects any faults or
receives the R_APS
(NR, RB) packets.
l Protection: The
Ethernet ring is in
protected state. For
example, a fault on the
node triggers the
ERPS, or a node on the
ring is in the WTR
period after the fault is
rectified.
Node Carried with

Current Packet

the MAC address carried
in the R-APS packets
received by the current
node. The MAC address
refers to the MAC address
of the source node that
initiates the switching
request.
East Port Status
Displays the status of the

east port.
West Port Status
Displays the status of the

west port.
Related Tasks
A.7.1.1 Creating an ERP Instance
A.7.1.2 Setting ERPS Protocol Parameters
A.7.1.3 Querying the ERPS Status
B.4.2.2 Parameter Description: Ethernet Link Aggregation Management

This topic describes the parameters that are used for creating a link aggregation group (LAG).
Issue 02 (2012-12-30)

639


Parameter
Value Range
Default Value
Description
LAG No.
l This parameter
specifies the LAG
number to be set
manually.

only when
Automatically
Assign is not selected.
Selected
Selected
Deselected
l This parameter
indicates whether
LAG No. is allocated
automatically.
l When Automatically
Assign is selected,
LAG No. cannot be
set.
LAG Name
Issue 02 (2012-12-30)


the LAG name.
640

Parameter
Value Range
Default Value
Description
LAG Type
Static
Static
l Static: You can create

a LAG. When you add
or delete a member
port to or from the
LAG, the Link
Aggregation Control
Protocol (LACP)
protocol is required. In
a LAG, a port can be in
selected, standby, or
unselected state. The
aggregation
information is
exchanged among
different equipment
through the LACP
protocol to ensure that
the aggregation
information is the
same among all the
nodes.
Manual
l Manual: You can

create a LAG. When
you add or delete a
member port, the
LACP protocol is not
required. The port can
be in the up or down
state. The system
determines whether to
aggregate a port
according to its
physical state (UP or
DOWN), working
mode, and rate.
l For LAGs consisting
of microwave ports
and GE ports, set LAG
Type to Static.
Switch Protocol

not support this
parameter.
Switch Mode

not support this
parameter.
Link Trace Protocol

not support this
parameter.
Issue 02 (2012-12-30)

641

Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive
Revertive
l Revertive Mode can

be set only when Load
Sharing is set to NonSharing.
Non-Revertive
l When Revertive
Mode is set to
Revertive, the
services are switched
back to the former
working channel after
this channel is restored
to normal.
l When Revertive
Mode is set to NonRevertive, the status
of the LAG does not
change after the
former working
channel is restored to
normal. That is, the
services are still
transmitted on the
protection channel.
Issue 02 (2012-12-30)

642

Parameter
Value Range
Default Value
Description
Load Balancing
Sharing
Non-Sharing
l Set Load Balancing to

the same value as the
peer equipment. It is
set Load Balancing to
Non-Sharing at both
ends if the LAGs are
used for protection and
set Load Balancing to
Sharing at both ends if
the LAGs are used for
increasing
bandwidths.
Non-Sharing
l Sharing: Each member

link of a LAG
processes traffic at the
same time and shares
the traffic load. The
sharing mode can
increase a bandwidth
utilization for the link.
When the LAG
members change, or
certain links fail, the
system automatically
re-allocates the traffic.
l Non-Sharing: Only
one member link of a
LAG carries traffic,
and the other link is in
the standby state. In
this case, a hot backup
mechanism is
provided. When the
active link of a LAG is
faulty, the system
activates the standby
link, thus preventing
link failure.
Load Balancing Hash
Algorithm
Issue 02 (2012-12-30)

Set this parameter in the

Link Aggregation
Parameters tab page.
643

Parameter
Value Range
Default Value
Description
LAG Priority
0 to 65535
32768
l LAG Priority
indicates the priority
of a LAG. The smaller
the value of LAGm
Priority, the higher
the priority.
l When a local LAG
negotiates with an
opposite LAG through
LACP packets, both
LAGs can obtain the
system priorities of
each other. Then, the
LAG of the higher
system priority is
considered as the
comparison result of
both LAGs so that the
aggregation
information is
consistent at both
LAGs. If the priorities
of both LAGs are the
same, the system MAC
addresses are
compared. Then, the
comparison result
based on the LAG with
smaller system MAC
address is considered
as the result of both
LAGs and is used to
ensure that the
aggregation
information is
consistent at both
LAGs.
WTR Time(min)
1 to 30
10
l Specifies the WTR

time for the LAG.
l WTR Time(min)
takes effect only when
Revertive Mode is
Revertive Mode.
Issue 02 (2012-12-30)

644

Parameter
Value Range
Default Value
Description
Switch LAG upon Air

Interface SD
Disabled
Disabled
l This parameter
enable the switching
triggered by bit errors.
Enabled
l If Switch LAG upon

Air Interface SD is set
to Enabled, the
MW_BER_SD alarm
will trigger the LAG
switching at the air
interface.
Packet Receive Timeout
Period
Short period
Short period
Long period
l A LAG switching is
triggered if no LACP
packet is received after
Packet Receive
Timeout Period times
out.
l When LACP protocol
packets pass through
an intermediate
network, it is
recommended to set
Packet Receive
Timeout Period to
Short period. In other
scenarios, set it to
Long period to avoid
mistaken switching.
l This parameter is
supported only when
LAG Type is set to
Static.
LAG Min Active Link

Threshold
Issue 02 (2012-12-30)

To trigger LPT switching

upon failure of a member
link in a LAG when LAG
and LPT coexist, LAG
Min Active Link
Threshold must be set to
the total number of links in
the LAG.
645

Port Settings Parameters

Parameter
Value Range
Default Value
Description
Master Board

the main board in a LAG.
Master Port
l This parameter
specifies the main port
in a LAG.
l After a LAG is created,
you can add Ethernet
services to the main
port only. Services
cannot be added to a
slave port. When Load
Sharing is set to NonSharing, the link
connected to the main
port is used to transmit
the services, and the
link connected to the
slave port is used for
protection.
Board (Available Standby

Ports)

the slave board in a LAG.
Port (Available Standby

Ports)
l This parameter
specifies the salve port
in a LAG.
l The slave ports in a
LAG are fixed. Unless
they are manually
modified, the system
does not automatically
add them to or delete
them from the LAG.
Selected Standby Ports

the selected slave ports.
Related Tasks
B.4.2.3 Parameter Description: Ethernet Link Aggregation_Link Aggregation

This section describes the parameters for configuring the port priority and system load-sharing
hash algorithm.
Issue 02 (2012-12-30)

646


Parameter
Value Range
Default Value
Description
Port

the port whose priority can
be set.
Port Priority
0 to 65535
32768
l This parameter
indicates the priorities
of the ports in a LAG
as defined in the LACP
protocol. The smaller
the value, the higher
the priority.
l When ports are added
into a LAG, the port of
the highest priority is
preferred for service
transmission.
Automatic
System Load Sharing

Hash Algorithm
l System Load Sharing

Hash Algorithm is
valid only when Load
Sharing of a LAG is
set to Sharing.
Automatic
Source and Destination

MAC
Source and Destination IP
l After the configuration

data is deployed,
System Load Sharing
Hash Algorithm takes
effect for the entire
NE.
l Unless otherwise
specified, set this
parameter to
Automatic.
Related Tasks
A.7.2.2 Setting Parameters for a LAG
B.4.2.4 Parameter Description: Simplified LPT Creation

This section describes the parameters for creating simplified link-state pass through (LPT).
Parameters for a Convergence Node

Parameter
Value Range
Default Value
Description
Board
This parameter displays the board that

functions as a convergence node.
Issue 02 (2012-12-30)

647

Parameter
Value Range
Default Value
Description
Port
This parameter specifies the port on the

board that functions as a convergence node.
Set this parameter to a microwave port for
the OptiX RTN 310.
Parameters for an Access Node

Parameter
Value Range
Default Value
Description
Board
This parameter displays the board that

functions as an access node.
Port
This parameter specifies the port on the

board that functions as an access node. Set
this parameter to an Ethernet port that
receives/transmits services.
Related Tasks
A.7.9 Configuring LPT
B.4.3 Parameters for the Ethernet OAM

This topic describes the parameters that are related to the Ethernet operation, administration and
maintenance (OAM).
B.4.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance

Domain Creation
This topic describes the parameters that are used for creating maintenance domains.

Parameter
Value Range
Default Value
Description
Maintenance
Domain Name
default
l This parameter specifies the name of the

maintenance domain.
l The maintenance domain refers to the
network for the Ethernet OAM.
l This parameter can contain a maximum
of eight bytes.
Issue 02 (2012-12-30)

648

Parameter
Value Range
Default Value
Description
Maintenance
Domain Level
l Maintenance Domain Level specifies

the level of the maintenance domain.
l The values 0 to 7 indicates maintenance

domain levels in an ascending order.
2
3
l MEPs transparently transmit OAM

protocol packets if the packets have a
higher level than the parameter value.
4
5
6
l MEPs discard OAM protocol packets if

the packets have a lower level than the
parameter value.
l MEPs respond to or terminate OAM

protocol packets based on the packet type
if the packets have the same level as the
parameter value.
Related Tasks
A.7.7.1 Creating an MD
B.4.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance

Association Creation
This topic describes the parameters that are used for creating maintenance associations.

Parameter
Value Range
Default Value
Description
Maintenance
Domain Name
This parameter indicates the maintenance

domain of the created maintenance
association.
Maintenance
Association Name
l This parameter specifies the name of the

maintenance association, which is a
domain related to a service. Through
maintenance association division, the
connectivity check (CC) can be
performed on the network that transmits
a service instance.
l This parameter can contain a maximum
of eight bytes.
Relevant Service
Issue 02 (2012-12-30)
This parameter specifies the service

instance that is related to the maintenance
association.

649

Parameter
Value Range
Default Value
Description
CC Test Transmit
Period
3.3ms
1s
l This parameter specifies the interval for

transmitting packets in the CC.
10ms
l The CC is performed to check the

availability of the service.
100ms
1s
10s
1min
10min
Related Tasks
A.7.7.2 Creating an MA
B.4.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation

This topic describes the parameters that are used for creating a maintenance association end
point (MEP).

Parameter
Value Range
Default Value
Description
Maintenance
Domain Name

domain of the created MEP.
Maintenance
Association Name

association of the created MEP.
Board
This parameter specifies the board where

the MEP is located.
Port
This parameter specifies the port where the

MEP is located.
VLAN
This parameter indicates the VLAN ID of

the current service.
MEP ID
1 to 8191
l This parameter specifies the MEP ID.

l Each MEP needs to be configured with
an MEP ID, which is unique in the
maintenance association. The MEP ID
is required in the OAM operation.
Issue 02 (2012-12-30)

650

Parameter
Value Range
Default Value
Description
Direction
Ingress
Ingress
l Direction specifies the direction of the

MEP.
Egress
l Ingress indicates the direction in which

the packets are transmitted to the port,
and Egress indicates the direction in
which the packets are transmitted from
the port.
l When 1-SHXA2-2(GE1) or 1-SHXA2-3
(GE2) functions as an MEP, its
Direction cannot be set to Egress.
Active
CC Status
Active
Inactive
l This parameter specifies whether to

enable the CC function of the MEP.
l In the case of the tests based on the MP
IDs, CC Status must be set to Active.
AIS Active Status
Active
Inactive
Inactive

status.
information.
Client Layer Level
1 to 7

information to n+1.
Related Tasks
A.7.7.3 Creating an MEP
B.4.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP

Creation
This topic describes the parameters that are used for creating a remote MEP.
Issue 02 (2012-12-30)

651


Parameter
Value Range
Default Value
Description
Maintenance
Domain Name

domain of the MEP.
Maintenance
Association Name

association of the created MEP.
Remote
Maintenance Point
ID(e.g:1,3-6)
1 to 8191
l This parameter specifies the ID of the

remote MEP.
l If other MEPs will initiate OAM
operations to an MEP in the same MA,
set these MEPs as remote MEPs.
Related Tasks
A.7.7.4 Creating a Remote MEP in an MA
B.4.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation

This topic describes the parameters that are used for creating a maintenance association
intermediate point (MIP).

Parameter
Value Range
Default Value
Description
Maintenance
Domain Name

domain of the MIP.
Board
This parameter specifies the board where

the MIP is located.
Port
This parameter specifies the port where the

MIP is located.
MIP ID
1 to 8191
l This parameter specifies the MIP ID.

l Each MIP needs to be configured with an
MIP ID, which is unique in the
maintenance domain. The MIP ID is
required in the OAM operation.
NOTE
To create MEPs and MIPs in a service at a
port, ensure that only one MIP can be created
and the level of the MIP must be higher than
the level of the MEP.
Related Tasks
A.7.7.5 Creating an MIP
Issue 02 (2012-12-30)

652

B.4.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling

This topic describes the parameters that are used for enabling the LB.

Parameter
Value Range
Default Value
Description
Destination
Maintenance Point
ID
Selected
Deselected
l This parameter needs to be selected if the

LB test is performed on the basis of
Destination Maintenance Point IDs.
Deselected
l Only the MEP ID can be set to the

Destination Maintenance Point ID.
Destination
Maintenance Point
MAC Address
Selected
Selected
Deselected

LB test is performed on the basis of
MAC addresses.
l Only the MAC address of the MEP can
be set to the MAC address of the
Destination Maintenance Point MAC
Address.
Maintenance
Domain Name

maintenance domain for the LB test.
Maintenance
Association Name

maintenance association for the LB test.
Source
Maintenance Point
ID
l This parameter specifies the source

maintenance point in the LB test.
Transmitted
Packet Count
1 to 255
l Only the MEP can be set to the source

maintenance point.
3
l This parameter specifies the number of

packets transmitted each time in the LB
test.
l When the value is greater, the required
duration is longer.
Transmitted
Packet Length
64 to 1400
64
l This parameter specifies the length of a

transmitted LBM packet.
l If the packet length is different, the test
result may be different. In normal cases,
it is recommended that you use the
default value.
Transmitted
Packet Priority
0 to 7
l This parameter specifies the priority of

transmitting packets.
l 0 indicates the lowest priority, and 7
indicates the highest priority. In normal
cases, this parameter is set to the highest
priority.
Issue 02 (2012-12-30)

653

Parameter
Value Range
Default Value
Description
Detection Result
This parameter indicates the relevant

information and result of the LB test.
Related Tasks
A.7.7.7 Performing an LB Test
B.4.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

This topic describes the parameters that are used for enabling the LT.
Test Node Parameters

Parameter
Value Range
Default Value
Description
Destination
Maintenance Point
ID
Selected
Deselected

LT test is performed on the basis of MP
IDs.
Deselected
l Only the MEP ID can be set to the

Destination Maintenance Point ID.
Destination
Maintenance Point
MAC Address
Selected
Selected
Deselected

LT test is performed on the basis of MAC
addresses.
l Only the MAC address of the MEP can
be set to the MAC address of the
Destination Maintenance Point MAC
Address.
Maintenance
Domain Name

maintenance domain for the LT test.
Maintenance
Association Name

maintenance association for the LT test.
Source
Maintenance Point
ID
l This parameter specifies the source

maintenance point in the LT test.
l Only the MEP can be set to the source
maintenance point.
Parameters for the Detection Result

Parameter
Value Range
Default Value
Description
Source
Maintenance Point
ID
This parameter indicates the source

maintenance point in the LT test.
Issue 02 (2012-12-30)

654

Parameter
Value Range
Default Value
Description
Destination
Maintenance Point
ID/MAC

of the port where the destination
maintenance point is located in the LT test.
Response
Maintenance Point
ID/MAC

of the port where the responding
maintenance point is located in the LT test.
Hop Count
1 to 64
l This parameter indicates the number of

hops from the source maintenance point
to the responding maintenance point or
to the destination maintenance point in
the LT test.
l The number of hops indicates the
adjacent relation between the responding
maintenance point to the source
maintenance point. The number of hops
increases by one when a responding
point occurs on the link from the source
maintenance point to the destination
maintenance point.
Test Result
This parameter indicates the result of the LT

test.
Related Tasks
A.7.7.8 Performing an LT Test
B.4.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback

Detection
This section describes the parameters for enabling E-LAN service loopback detection.
Parameter
Value Range
Default Value
Description
Port

the port on which service
loopback detection can be
enabled.
Available CVLANs

the VLAN ID in the
packets passing the port on
which service loopback
detection can be enabled.
Issue 02 (2012-12-30)

655

Parameter
Value Range
Default Value
Description
Vlans/CVLAN
1-4094
1-4094

the VLAN ID of the
service for which
loopback detection is
enabled. Loopback
detection can be
performed for only one
service at a time.
Packet Timeout Period

(s)
3-10
Loopback detection ends

if no loopback detection
packets are received after
Available CVLANs
elapses.
Packet Length

the length of a loopback
detection packet.
VLAN Packet sending

Interval(s)

the interval for
transmitting loopback
detection packets.
Disable Service When

Loopback Is Detected
No
No
This parameters specifies

whether services are
automatically disabled
when loopback detection
packets are received.
Yes
Related Tasks
A.7.7.11 Performing E-LAN Service Loopback Detection

This topic describes the OAM parameters that are related to Ethernet ports.

Parameter
Value Range
Default Value
Description
Port

port.
Issue 02 (2012-12-30)

656

Parameter
Value Range
Default Value
Description
Enable OAM
Protocol
Enabled
Disabled
l This parameter indicates or specifies

whether to enable the OAM protocol.
Disabled
l After the OAM protocol is enabled, the

current Ethernet port starts to use the
preset mode to create the OAM
connection with the opposite end.
OAM Working
Mode
Active
Active
Passive

working mode of the OAM.
l The port whose OAM working mode is
set to Active can initiate the OAM
connection.
l The port whose OAM working mode is
set to Passive can only wait for the
opposite end to send the OAM
connection request.
l The OAM working mode of the
equipment at only one end can be
Passive.
Link Event
Notification
Enabled
Disabled
Enabled

whether the local link events can be
notified to the opposite end.
l If the alarms caused by link events can
be reported, that is, if the number of
performance events (for example, error
frame period, error frame, error frame
second, and error frame signal cycle) at
the local end exceeds the preset
threshold, these performance events are
notified to the port at the opposite end
through the link event notification
function.
Issue 02 (2012-12-30)

657

Parameter
Value Range
Default Value
Description
Remote Side
Loopback
Response
Disabled
Disabled

whether the port responds to the remote
loopback.
Enabled
l Remote loopback indicates that the local

OAM entity transmits packets to the
remote OAM entity for loopback. The
local OAM entity can locate the fault and
test the link performance through
loopback data analysis.
l If a port does not support remote
loopback response, this port does not
respond to the loopback request from the
remote port regardless of the OAM port
status.
Non-Loopback
Loopback Status
Initiate Loopback at
Local
This parameter indicates the loopback status

at the local end.
NOTE
When OAM is enabled, Loopback Status takes
effect only after you choose OAM > Enable
Remote Loopback.
Respond Loopback
of Remote
OAM Discovery
Status
This parameter indicates the OAM

discovery status at the local end.
Port Transmit
Status
This parameter indicates the status of

transmitting packets at the local end.
Port Receive Status
This parameter indicates the status of

receiving packets at the local end.
Related Tasks
A.7.8.1 Enabling OAM Auto-discovery
A.7.8.2 Enabling the Link Event Notification
A.7.8.4 Performing a Remote Loopback
A.7.8.5 Enabling Self-loop Detection
B.4.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error

Frame Monitoring
This topic describes the parameters that are used for monitoring the OAM error frames at the
Ethernet port.
Issue 02 (2012-12-30)

658


Parameter
Value Range
Default Value
Description
Port

port.
Error Frame
Monitor Window
(ms)
1000 to 60000, in
step of 100
1000
This parameter specifies the duration of

monitoring error frames.
Error Frame
Monitor Threshold
(frames)
1 to 4294967295, in
step of 1
l This parameter specifies the threshold of

monitoring error frames.
Error Frame
Period Window
(frames)
1488 to 892800000,
in step of 1
1488000
This parameter specifies the window of

monitoring the error frame period.
Error Frame
Period Threshold
(frames)
1 to 892800000, in
step of 1

monitoring the error frame period.
Error Frame
Second Window(s)
10 to 900, in step of
1
60
This parameter specifies the time window of

monitoring the error frame second.
Error Frame
Second Threshold
(s)
10 to 900, in step of
1

monitoring error frame seconds.
l Within the specified value of Error

Frame Monitor Window(ms), if the
number of error frames on the link
exceeds the preset value of Error
Frame Monitor Threshold(frame), an
alarm is reported.
l Within the specified value of Error

Frame Period Window(frame), if the
Frame Period Threshold(frame), an
alarm is reported.
l If any error frame occurs in one second,

this second is called an errored frame
second. Within the specified value of
Error Frame Second Window(s), if the
Frame Second Threshold(s), an alarm
is reported.
Related Tasks
A.7.8.3 Changing the OAM Errored Frame Monitoring Threshold
Issue 02 (2012-12-30)

659


This topic describes the parameters that are related to QoS.
Parameters Related to Mapping Between the Ingress and Egress

Parameter
Value Range
Default Value
Description
CVLAN
0 to 7
l This parameter
specifies the C-VLAN
priority in the ingress/
egress direction.
effect when Packet
Type is CVLAN.
After receiving
packets, an ingress
port schedules the
packets to their target
queue at the egress
port based on the PHB
class corresponding to
the parameter value.
Before sending out the
packets, the egress
port set the C-VLAN
priority based on the
PHB class.
according to the
service plan.
Issue 02 (2012-12-30)

660

Parameter
Value Range
Default Value
Description
MPLS EXP
l This parameter
specifies the MPLS
EXP value for packets
in the ingress/egress
direction.
effect when Packet
Type is MPLS EXP.
After receiving
packets, an ingress
port schedules the
queue at the egress
packets, the egress
port set the MPLS
EXP value based on
the PHB class.
l The MPLS EXP value
is not modifiable in the
egress direction.
this parameter take its
default value.
Issue 02 (2012-12-30)

661

Parameter
Value Range
Default Value
Description
IP DSCP
0 to 63
l This parameter
specifies the IP DSCP
priority in the ingress/
egress direction.
l The differentiated
services code point
(DSCP) refers to bits
0-5 of the
differentiated services
(DS) field in the packet
and indicates the
service class and
discarding priority of
the packet.
effect when Packet
Type is IP DSCP.
After receiving
packets, an ingress
port schedules the
queue at the egress
packets, the egress
port set the IP DSCP
value based on the
PHB class.
l Mappings in the egress
direction must be the
same as those in the
ingress direction.
Issue 02 (2012-12-30)

662

Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the PHB
service class of the DS
domain.
AF1 (AF11 and AF13)

AF2 (AF21 and AF23)
AF3 (AF31 and AF33)
l The PHB service class

refers to the
forwarding behavior
of the DS node on the
behavior aggregate
(BA) operation. The
forwarding behavior
can meet the specific
requirements.
AF4 (AF41 and AF43)

EF
CS6
CS7
l The PHB service

classes are BE, AF1,
AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, DSCP value
and MPLS EXP value)
contained in the
packets of the DS
domain and the eight
PHB service classes
meet the requirements
of the specified or
default mapping
relationship.
Port Policy Parameters

Parameter
Value Range
Default Value
Description
Port
Display the ports.
Packet Type
ip-dscp
cvlan
By default, the untrusted

packets are mapped to the
BE service class for besteffort forwarding.
Disabled
Enable Bandwidth
Restriction indicates or
specifies whether traffic
shaping is enabled for an
egress queue.
cvlan
mpls-exp
Enable Bandwidth
Restriction
Issue 02 (2012-12-30)
Disabled
Enabled

663

Parameter
Value Range
Default Value
Description
PIR (kbit/s)
l When the buffer queue

is empty, the packets
are processed as
follows: If the rate of a
packet is equal to or
lower than the PIR, it
is directly forwarded;
if the rate of a packet is
higher than the PIR, it
enters the buffer queue
and then is forwarded
at a rate equal to the
PIR.
is not empty, the
packets whose rate
passes the restriction
of the PIR directly
enter the buffer queue
and then are forwarded
PIR.
according to the
PBS (bytes)

is empty, certain burst
packets can be
forwarded if the rate of
the packets is equal to
or lower than the PIR
in a certain period. The
maximum traffic of the
burst packets is
determined by the
PBS.
according to the
QoS Parameters
Parameter
Value Range
Default Value
Description
PHB

the port queue names.
Issue 02 (2012-12-30)

664

Parameter
Value Range
Default Value
Description
Grooming Police After

Reloading
SP
l The strict priority (SP)

scheduling algorithm
is designed for the key
services. One
important
characteristic of the
key services is that
higher priorities are
required to minimize
the response delay in
the case of congestion
events.
WRR
l The weighted round

robin (WRR)
divides each port into
multiple output subqueues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each subqueue has a certain
period of service time.
l The OptiX RTN 310
supports the setting of
the SP+WRR
of the CoS queue
according to the
requirement, and
provides one or more
queues that comply
with the SP algorithm.
Except for the default
value, however, the
value of the WRR
and the value of the SP
cannot be interleaved.
That is, except for the
default value,
Grooming Police
After Reloading can
be changed from SP to
WRR according to the
queue priorities in a
descending order
(CS7-BE).
Issue 02 (2012-12-30)

665

Parameter
Value Range
Default Value
Description
according to the
Scheduling Weight
1 to 100
l The eight classes of

service (CoSs),
namely, BE, AF1,
AF2, AF3, AF4, EF,
CS6, and CS7
correspond to eight
queues.
l The Scheduling
Weight parameter
indicates the
percentage of the
bandwidth resources
gained by the WRR
queue.
l The scheduling weight
sum of WRR queues
must be 100%.
Congest
Tail Drop Threshold
Tail Drop Threshold
WRED
l A microwave port
supports Tail Drop
Threshold and
WRED. An Ethernet
port supports only Tail
Drop Threshold.
l To avoid congestion, it
is recommended that
weighted random
early detection
(WRED) should be
configured for
microwave ports on
the OptiX RTN 310 so
that the transmission
of high-priority
services can be
ensured.
Tail Drop Threshold

(256 bytes)
Issue 02 (2012-12-30)
0 to 480


the tail drop threshold.
This parameter takes
effect only when
Congest is Tail Drop
Threshold.
666

Parameter
Value Range
Default Value
Description
WRED

the port WRED policy.
This parameter takes
effect only when
Congest is WRED.
Enable Bandwidth
Restriction
Disabled
Disabled
Bandwidth Limit
whether traffic shaping is
enabled for an egress
queue corresponding to a
PHB service class.
PIR (kbit/s)

is empty, the packets
are processed as
follows: If the rate of a
packet is equal to or
lower than the PIR, it
is directly forwarded;
if the rate of a packet is
higher than the PIR, it
enters the buffer queue
and then is forwarded
PIR.
Enabled

is not empty, the
packets whose rate
passes the restriction
of the PIR directly
enter the buffer queue
and then are forwarded
PIR.
according to the
Issue 02 (2012-12-30)

667

Parameter
Value Range
Default Value
Description
PBS (bytes)

is empty, certain burst
packets can be
forwarded if the rate of
the packets is equal to
or lower than the PIR
in a certain period. The
maximum traffic of the
burst packets is
determined by the
PBS.
according to the
Related Tasks
A.7.6.1 Modifying the Mapping for a DS Domain
A.7.6.2 Changing the Packet Type Trusted by a Port
A.7.6.3 Configuring Port Shaping
A.7.6.4 Setting Egress Queue Scheduling Policies
A.7.6.5 Setting Traffic Shaping for Egress Queues
A.7.6.6 Setting the Congestion Management Mode for Egress Queues
B.5 RMON Parameters

This topic describes the parameters that are related to RMON performances.
B.5.1 Parameter Description: RMON Performance_Statistics Group

This topic describes the parameters that are related to RMON statistics groups.
Parameters
Parameter
Value Range
Default Value
Description
Object
This parameter specifies the object to be

monitored.
Sampling Period
5 to 150
This parameter specifies the duration of the

monitoring period.
Issue 02 (2012-12-30)

668

Parameter
Value Range
Default Value
Description
Display
Accumulated
Value
Selected
Unselected
l This parameter specifies the method of

displaying the performance events.
Unselected
l If this parameter is not selected, the

displayed value is an increment
compared to the value that is collected in
last sampling period and stored in the
register.
l If this parameter is selected, the
displayed value is an absolute value that
is currently stored in the register.
Graphics
Display Mode
List
List

l If this parameter is set to Graphics, the
number of performance events to be
monitored at each time cannot be more
than 10, and the unit should be the same.
Color
Legend
Description
l This parameter indicates the description

of different colors.
l This parameter is valid only when
Display Mode is set to Graphics.
Event
l This parameter indicates the queried

performance events.
Display Mode is set to List.
Related Tasks
A.9.1 Browsing Current Performance Events of Ethernet
B.5.2 Parameter Description: RMON Performance_History Group

This topic describes the parameters that are related to RMON history groups.
Parameters
Parameter
Value Range
Default Value
Description
Object
The parameter indicates the object to be

monitored.
Ended from/to
This parameter specifies the start time and

end time of the monitoring period.
Issue 02 (2012-12-30)

669

Parameter
Value Range
Default Value
Description
History Table
Type
30-Second
30-Second
This parameter specifies the monitoring

period.
List

30-Minute
Custom Period 1
Custom Period 2
Display Mode
Graphics
List
l If this parameter is set to Graphics, the

number of performance events to be
monitored at each time cannot be more
than 10, and the unit should be the same.
Color
Legend
Description
l This parameter indicates the description

of different colors.
Display Mode is set to Graphics.
Event
l This parameter indicates the queried

performance events.
Display Mode is set to List.
Statistical Item
This parameter indicates the performance

items to be monitored.
Statistical Value
This parameter indicates the statistical value

of the monitored performance items.
Time Flag
This parameter indicates the time point of

each performance event.
Related Tasks
A.9.4 Browsing Ethernet Historical Performance Data

This topic describes the parameters that are related to RMON setting.
Event Parameters
Parameter
Value Range
Default Value
Description
Event
This parameter indicates the performance

event to be monitored.
30-Second
Enabled
Disabled
This parameter indicates or specifies

whether to enable the monitoring function
based on 30-Second.
Disabled
Issue 02 (2012-12-30)

670

Parameter
Value Range
Default Value
Description
30-Minute
Enabled

whether to enable the 30-Minute
monitoring function.
Disabled

based on Custom Period 1Custom Period
1 Monitor.
Disabled

based on Custom Period 2Custom Period
2 Monitor.
Report All

threshold detection method.
Disabled
Custom Period 1
Enabled
Disabled
Custom Period 2
Enabled
Disabled
Threshold Detect
Report All
Do Not Detect
l If the number of detected events reaches

the preset threshold, the events are
reported to the NMS. Otherwise, the
events are not reported to the NMS.
Report Only the

Upper Threshold
Report Only the
Lower Threshold
l If an event does not support this

parameter, Not Supported is displayed.
Upper Threshold

upper threshold. If the number of
performance events exceeds the preset
upper threshold, the corresponding
performance events are reported.
Lower Threshold

lower threshold. If the number of
performance events is less than the preset
lower threshold, the corresponding
performance events are reported.
Threshold Unit
This parameter indicates the unit of each

threshold of the performance events.
Related Tasks
A.9.2 Setting the Ethernet Performance Threshold-Crossing Parameter
A.9.3 Configuring the Parameters for Ethernet Historical Performance Monitoring
B.6 Clock Parameters

This topic describes the parameters that are related to clocks.
B.6.1 Physical-Layer Clock Parameters

This topic describes physical-layer clock parameters.
Issue 02 (2012-12-30)

671

B.6.1.1 Parameter Description: Clock Synchronization Status

This topic describes the parameters that are related to the clock synchronization status.
Parameters
Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
NE Clock Mode

the working mode of the
NE clock.
S1 Byte Synchronization
Quality Info

the synchronization
quality information of the
S1 byte.
S1 Byte Clock
Synchronous Source

the current S1-byte clock
synchronization source.
Synchronous Source

the clock source that is
currently traced.
Issue 02 (2012-12-30)

672

Parameter
Value Range
Default Value
Description
Clock Control Mode
Centralized
Centralized
l This parameter is
available only for IF 1
+1 protection and
PLA.
Standalone
l If IF 1+1 protection is
configured, this
parameter has a fixed
value of Centralized.
l If PLA is configured,
the default value of
this parameter is
Standalone. It is
set this parameter to
the default value.
l The value
Centralized indicates
that the standby NE
traces the clock source
provided by the
cascade port of the
active NE and the
standby link does not
transmit clock
information.
l The value Standalone
indicates that each NE
determines the clock
source to be traced
based on the
configured clock
source priority or SSM
protocol.
Related Tasks
A.8.1.8 Querying the Clock Synchronization Status
B.6.1.2 Parameter Description: Clock Source Priority Table

This topic describes the parameters that are related to the priority table of a clock source.
Issue 02 (2012-12-30)

673

Parameters
Parameter
Value Range
Default Value
Description
Clock Source
l The internal clock

source is always at the
lowest priority and
indicates that the NE
works in the free-run
mode.
l The clock sources and
the corresponding
clock source priority
levels are determined
according to the clock
synchronization
schemes.
External Clock Source

Mode

not support this
parameter.
Synchronous Status Byte

not support this
parameter.
Clock Source Priority

Sequence (Highest: 1)
Displays the priority

sequence of clock sources.
1 indicates the highest
clock source priority.
Related Tasks
A.8.1.2 Configuring Clock Sources
B.6.1.3 Parameter Description: Clock Source Switching_Clock Source Switching

This topic describes the parameters that are related to the switching status of a clock source.
Parameters
Parameter
Value Range
Default Value
Description
Clock Source

the name of the clock
source.
Current Status
Valid

whether the clock source
is valid.
Invalid
Issue 02 (2012-12-30)

674

Parameter
Value Range
Default Value
Description
Lock Status
Lock
l This parameter
specifies the locking
status of the clock
source in the priority
table.
Unlock
l Lock: A clock source

in the priority table is
in the locked state. The
clock source in the
locked state cannot be
switched.
l Unlock: A clock
source in the priority
table is in the unlocked
state. The clock source
in the unlocked state
can be switched.
Switching Source

the clock source to be
traced by the NE after the
switching.
Switching Status
Normal

the switching status of the
current clock source.
Manual Switching
Forced Switching
B.6.1.4 Parameter Description: Clock Source Switching_Clock Source Restoration

Parameters
This topic describes the parameters that are related to clock source restoration.
Parameters
Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
Issue 02 (2012-12-30)

675

Parameter
Value Range
Default Value
Description
Higher Priority Clock

Source Reversion
Auto-Revertive
Auto-Revertive
l When the quality of a

higher-priority clock
source degrades, the
NE automatically
switches the clock
source to a lowerpriority clock source.
If this parameter is set
to Auto-Revertive,
the NE automatically
switches the clock
source to the higherpriority clock source
when this higherpriority clock source
restores. If this
parameter is set to
Non-Revertive, the
NE does not
automatically switch
the clock source to the
source when this
source restores.
Non-Revertive
l Correct setting of
Clock Source
Switching Condition
ensures the reliability
of the clock source
switching. To improve
the clock quality,
select AutoRevertive. Otherwise,
to prevent jitter of the
clock, generally, it is
set this parameter to
Non-Revertive.
Issue 02 (2012-12-30)

676

Parameter
Value Range
Default Value
Description
Clock Source WTR

Time(min.)
0 to 12
l This parameter
specifies the duration
from the time when the
clock source
restoration is detected
to the time when the
clock source switching
is triggered. This
parameter is used to
avoid frequent
switching of the clock
source due to
instability of the clock
source state within a
short time.
only when Higher
Priority Clock
Source Reversion is
set to AutoRevertive.
Related Tasks
A.8.1.7 Modifying Clock Source Reversion Parameters
B.6.1.5 Parameter Description: Clock Subnet Setting_Clock Subnet

This topic describes the parameters that are related to a clock subnet.
Parameters for Setting a Clock Subnet

Parameter
Value Range
Default Value
Description
Affiliated Subnet

not support this
parameter.
Issue 02 (2012-12-30)

677

Parameter
Value Range
Default Value
Description
Protection Status
Start Extended SSM

Protocol
Stop SSM Protocol
l The SSM protocol is a

scheme used for
synchronous
management on an
SDH network and
indicates that the SSM
is passed by the lower
four bits of the S1 byte
and can be exchanged
between the nodes.
The SSM protocol
ensures that the
equipment
automatically selects
the clock source of the
highest quality and
highest priority, thus
preventing mutual
clock tracing.
Start Standard SSM

Protocol
Stop SSM Protocol
l After the standard

SSM protocol is
started, the NE first
performs the
protection switching
on the clock source
quality level
information provided
by the S1 byte. If the
quality level of the
clock source is the
same, the NE then
performs the
priority table. That is,
the NE selects an
unlocked clock source
that is of the highest
quality and highest
priority from all the
current available clock
sources as the clock
source to be
synchronized and
traced by the local
station.
l If the SSM protocol is
stopped, it indicates
Issue 02 (2012-12-30)

678

Parameter
Value Range
Default Value
Description
that the S1 byte is not
used. The NE selects
and switches a clock
source only according
to the sequence
specified in the
priority table. The
clock source of the
highest priority is used
as the clock source to
be traced.
l After the SSM
protocol is stopped,
each NE performs the
on the clock according
to the preset priority
table of the clock
source only when the
clock source of a
higher priority is lost.
Clock Source
Issue 02 (2012-12-30)


the clock source that is
configured for an NE. In
Clock Source Priority,
you can set whether to add
or delete a clock source.
679

Parameter
Value Range
Default Value
Description
Clock Source ID
(None)
(None)

only when the
extended SSM
protocol is started.
1 to 15
l Clock source IDs are

allocated for the
following clock
sources only:
Internal clock
source of the node
that accesses the
external clock
sources.
At all the
intersecting nodes
of a ring/chain and
a ring, allocate
clock IDs to the
internal clock
sources.
At all the
intersecting nodes
of a ring/chain and
a ring, allocate
clock IDs to the
line clock sources
that are transmitted
to the ring.
Related Tasks
A.8.1.3 Configuring Protection for Clock Sources
B.6.1.6 Parameter Description: Clock Subnet Setting_Clock Quality

This topic describes the parameters that are related clock quality.
Issue 02 (2012-12-30)

680

Parameters for Clock Source Quality

Parameter
Value Range
Default Value
Description
Clock Source

the name of the
configured clock source.
In Clock Source
Priority, you can set
whether to add or delete a
clock source.
Configured Quality
Unknown
Synchronization Quality
Automatic Extraction

the quality level that is
configured for the clock
source. This function is
required only in a special
scenario or in a test.
Generally, this parameter
need not be set.

the clock source quality
signal received by the NE.
The NE extracts the clock
source quality signal from
the S1 byte of each clock
source.
G.811 Clock Signal

G.812 Transit Clock
Signal
G.812 Local Clock Signal
G.813 SDH Equipment
Timing Source (SETS)
Signal
Do Not Use For
Synchronization
Automatic Extraction
Received Quality
Parameters for Manual Setting of 0 Quality Level

Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
Issue 02 (2012-12-30)

681

Parameter
Value Range
Default Value
Description
Manual Setting of 0
Quality Level
Do Not Use For

Synchronization
Do Not Use For

Synchronization

the clock quality whose
level is manually set to
zero.
G.811 Reference Clock

Between G.811 Reference
Clock and G.812 Transit
Clock
G.812 Transit Clock
Between G.812 Transit
Clock and G.812 Local
Clock
G.812 Local Clock
Between G.812 Local
Clock and synchronous
equipment timing source
(SETS)
SETS Clock
Between synchronous
equipment timing source
(SETS) and quality
unavailable
l Do Not Use For

Synchronization: the
notification
information in the
reverse direction of the
selected
synchronization clock
source to avoid direct
mutual locking of
adjacent NEs.
l G.811 Reference
Clock: the clock signal
specified in ITU-T G.
811.
l Between G.811
Reference Clock and
G.812 Transit Clock:
lower than the quality
level of the clock
signal specified in
ITU-T G.811 but
higher than the quality
level of the transit
exchange clock signal
812.
l G.812 Transit Clock:
the transit exchange
clock signal specified
in ITU-T G.812.
l Between G.812
Transit Clock and G.
812 Local Clock:
level of the transit
exchange clock signal
812 but higher than the
quality level of the
local exchange clock
signal specified in
ITU-T G.812.
l G.812 Local Clock:
the local exchange
Issue 02 (2012-12-30)

682

Parameter
Value Range
Default Value
Description
in ITU-T G.812.
l Between G.812 Local
Clock and
synchronous
equipment timing
source (SETS): lower
than the quality level
of the local exchange
in ITU-T G.812 but
level of the clock
signal of the SETS.
l SETS Clock: the clock
signal of the SETS.
l Between synchronous
equipment timing
source (SETS) and
quality unavailable:
level of the clock
signal of the SETS but
level unavailable in the
synchronous timing
source.
Related Tasks
A.8.1.4 Customizing the Clock Quality
B.6.1.7 Parameter Description: Clock Subset Setting_SSM Output Control

This topic describes the parameters that are related to SSM output control.
Issue 02 (2012-12-30)

683

Parameters
Parameter
Value Range
Default Value
Description
Line Port
l This parameter
indicates the name of
the line clock port.
l Line Port: indicates
the SSM quality
information output
port of the current
available clock source
This output port can
transmit the quality
information of the
clock source by
outputting the S1 byte
to the downstream NE.
Output S1 Byte Info
Enabled
Enabled
Disabled
l Output S1 Byte Info

is valid only when the
SSM protocol or the
extended SSM
l Output S1 Byte Info
indicates whether the
SSM is output at the
line port.
l When the line port is
connected to an NE in
the same clock subnet,
set Output S1 Byte
Info to Enabled.
Otherwise, set this
parameter to
Disabled.
Related Tasks
A.8.1.5 Enabling/Disabling SSM Transmission
B.6.1.8 Parameter Description: Clock Subset Setting_Clock ID Enabling Status

This topic describes the parameters that are used for enabling the clock ID function.
Issue 02 (2012-12-30)

684

Parameters
Parameter
Value Range
Default Value
Description
Line Port
l This parameter
indicates the name of
the line clock port.
l Line Port: indicates
the SSM quality
information output
port of the current
available clock source.
This output port can
transmit the quality
information of the
clock source by
outputting the S1 byte
to the downstream NE.
Enabled
Output Clock ID
Enabled
Disabled
l Output Clock ID is
valid only when the
extended SSM
l Output Clock ID
indicates whether the
clock source ID is
output at the line port.
l If the line ports are
connected to the NEs
in the same clock
subnet and if the
extended SSM
protocol is started on
the opposite NE,
Output Clock ID is
set to Enabled.
Otherwise, this
parameter is set to
Disabled.
Related Tasks
A.8.1.6 Enabling/Disabling the Output of Clock Source IDs
B.7 PTP Clock Parameters

This topic describes PTP clock parameters.

This topic describes parameters that are used for creating a PTP clock port.
Issue 02 (2012-12-30)

685

Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Clock > PTP Clock > Clock Synchronization Attribute.

Parameter
Value Range
Default Value
Description
PTP System Time
l PTP System Time is

synchronized with the
current clock source
that the NE traces. If
the NE traces its local
time, PTP System
Time is the same as the
local time.
l This parameter can be
set when the NE traces
its local time.
NE Name
Displays the name of the

local NE.
NE Clock Type
OC
BC
l An NE in OC mode
supports only one PTP
port and is used at the
network edge.
BC
TC
TC+BC
l An NE in BC mode
supports multiple PTP
ports and is used as an
intermediate network
node.
l A TC provides
multiple PTP ports for
processing and
forwarding IEEE 1588
messages. However, it
does not recover a
clock from the
received IEEE 1588
messages.
l The TC+BC mode
supports both time
transparent
transmission and time
synchronization.
Static BMC
Disabled
Disabled
Enabled
Issue 02 (2012-12-30)

Specifies the state of the

BMC algorithm. This
parameter can be set
manually.
686

Parameter
Value Range
Default Value
Description
Slave_Only
SLAVE_ONLY
NON_SLAVE_ONLY

set only in OC mode.
NON_SLAVE_ONLY

set to
SLAVE_ONLY, the
NE can function only
as a slave clock node.
set to
NON_SLAVE_ONL
Y, the NE can function
as a master clock node.
PTP Time Adjustment
Enabled
Enabled
Disabled
l If the PTP system time

needs to be adjusted
(for example, during
network-wide time
synchronization), set
this parameter to
Enabled.
l If the PTP system time
(for example, 1588
ACR clock) does not
need to be adjusted, set
this parameter to
Disabled.
Packet Multicast Mode
Fully Multicasted
Fully Multicasted
Partially Multicasted
l If Packet Multicast
Mode is set to Fully
Multicasted, SYNC,
ANNOUNCE, and
DELAY packets are
multicast.
l If Packet Multicast
Mode is set to
Partially
Multicasted, SYNC
and ANNOUNCE
packets are multicast
but DELAY packets
are unicast.
l Generally, the value
Fully Multicasted is
recommended.
Issue 02 (2012-12-30)

687

Parameter
Value Range
Default Value
Description
Local Clock Source No
l Displays the ID of the

local PTP clock
source.
l The clock source ID is
comprised of the
enterprise code, NE
ID, and supplementary
code.
l For a PTP clock source
ID of Huawei
equipment, the
enterprise code is
always 0x001E10, the
NE ID is in IPv4
format, and the
supplementary code is
10.
Current Master Clock

No
l Displays the ID of the

current PTP clock that
the NE traces.
l If Current Master
Clock No is the same
as Local Clock
Source No, the NE
works in free-run
mode.
Ingress of Current
Master Clock
Displays the input port of

the current clock source
that the NE traces.
Port Status Parameters

Parameter
Value Range
Default Value
Description
Port
Displays the PTP ports.
Clock Type
l The working mode of a

PTP port can be
manually set to BC or
TC only when NE
Clock Type is set to
TC+BC and the PTP
port is an Ethernet port.
l Set the parameter
according to the
service plan.
Issue 02 (2012-12-30)

688

Parameter
Value Range
Default Value
Description
Step Mode
Single Step
Single Step
l Single Step represents

the one-step mode.
Single Step indicates
that SYNC packets (in
Delay mode) and
PDELAY_RESP
packets (in PDELAY
mode) carry the time
stamps of their
transmission
moments.
Double Step
l Double Step
represents the two-step
mode. Double Step
indicates that SYNC
packets (in Delay
mode) and
PDELAY_RESP
packets (in PDELAY
mode) do not carry the
time stamps of their
transmission
moments. The packets
only record their
transmission moments
and the time stamps of
their transmission
moments are carried
by follow-up packets
(namely,
FOLLOW_UP and
PDELAY_RESP_FO
LLOW_UP packets).
to be set to the same
value for the local and
opposite NEs.
Generally, the onestep mode is preferred.
Issue 02 (2012-12-30)

689

Parameter
Value Range
Default Value
Description
PTP Port Status
INITIALIZING
INITIALIZING
l This parameter is used

for specifying the port
status when the BMC
algorithm is not used
for source selection.
FAULTY
DISABLED
LISTENING
PRE_MASTER
l For microwave ports,

retain the default value
for this parameter.
MASTER
PASSIVE

its default value when
the BMC algorithm is
used for source
selection.
UNCALIBRATED
SLAVE
PTP Packet VLAN
1-4094
l Specifies or displays
the VLAN ID carried
by PTP packets that
travel through a PTP
port.
l If a Layer 2 network
exists between two
NEs interworking the
PTP protocol, you
need to set a VLAN ID
for PTP packets based
on the situation of the
Layer 2 network to
ensure that the Layer 2
network transparently
transmits the PTP
packets.
PTP Packet VLAN

Priority
0-7
Set this parameter

according to the service
plan.
PTP Packet
Encapsulation Format
PTP ETH
PTP ETH
l If Layer 2
encapsulation needs to
be performed for PTP
packets, set this
parameter to PTP
ETH.
PTP IP
l If IP encapsulation
needs to be performed
for PTP packets, set
this parameter to PTP
IP.
l This parameter does
not take effect for
microwave interfaces.
Issue 02 (2012-12-30)

690

Parameter
Value Range
Default Value
Description
Port Status
MASTER+SLAVE
MASTER+SLAVE
l Specifies or displays
the default status of a
PTP port.
MASTER
SLAVE
l MASTER: When a
clock port is in
MASTER state, it
provides the clock
source to the
downstream
equipment.
l SLAVE: When a port
is in SLAVE state, it
functions as the
downstream port to
receive the clock
information from its
upstream port.
l MASTER+SLAVE:
When a port is in
MASTER+SLAVE
state, it receives clock
information from its
upstream port and
functions as a clock
source for its
downstream port.
l The default value is
recommended.
Current Port Status
l Displays the actual

port status.
l This parameter value is
determined based on
the BMC algorithm.
Issue 02 (2012-12-30)

691

Parameter
Value Range
Default Value
Description
Reference Clock Source

No
1-0xFFFFFFFFFFFFFFF
FFFFF
FFFFFFFFFFFFFFFFFF
FF
l Specifies the reference

clock source for a PTP
port.
l The reference clock
source is in "clock ID
+port ID" format. A
PTP NE allocates its
PTP ports each a
unique port ID ranging
from 0.
l If this parameter is
specified manually,
the PTP port uses this
parameter value in the
BMC algorithm for
clock source selection.
l If the default
parameter value is
used, the PTP port uses
its first received clock
source in the BMC
algorithm for clock
source selection.
l If a PTP port can
receive more than one
clock sources, you
need to specify a
reference clock source
for the port. In other
cases, this parameter
takes its default value.
Enable IEEE-1588
Timeslot
Enabled
Disabled
l Enable IEEE-1588
Timeslot needs to be
set consistently
between two ends of a
link.
l If the OptiX RTN 310
needs to transmit IEEE
1588v2 packets, set
Enable IEEE-1588
Timeslot to Enabled.
If the OptiX RTN 310
does not need to
transmit IEEE 1588v2
packets, set Enable
IEEE-1588 Timeslot
to Disabled.
Issue 02 (2012-12-30)

692

Port Message Parameters

Parameter
Value Range
Default Value
Description
Port
Displays the PTP port

names.
P/E Mode
P2P
l Set this parameter to

the same value for both
ends ends of the PTP
link. For microwave
ports, set this
parameter to P2P. For
Ethernet ports, set this
parameter to E2E.
E2E
l If the opposite NE is an
E2E TC NE, set this
parameter to E2E.
l If the opposite NE is a
P2P TC NE, set this
parameter to P2P.
l If the opposite NE is an
OC/BC node, set this
parameter to E2E.
SYNC Packet Period (s)
l Specifies the intervals

for transmitting SYNC
packets.
be set to the same value
for the local and
opposite PTP NEs. The
default value is
recommended.
DELAY Packet Period

(s)

for transmitting
DELAY packets.
for the local and
default value is
recommended.
NOTE
This parameter can be set
only if P/E Mode is E2E.
Issue 02 (2012-12-30)

693

Parameter
Value Range
Default Value
Description
PDELAY Packet Period

(s)

for transmitting
PDELAY packets.
for the local and
default value is
recommended.
NOTE
This parameter can be set
only if P/E Mode is P2P.
ANNOUNCE Packet
Period (s)

for transmitting
ANNOUNCE packets.
for the local and
default value is
recommended.
2-10
ANNOUNCE Packet
Timeout Coefficient
l Specifies the packet

transmission interval
coefficient for
determining that
receiving of
ANNOUNCE packets
times out.
l If a port does not
receive ANNOUNCE
packets within the
parameter value, it
determines that the
link fails.
for the local and
default value is
recommended.
NOTE
When the OptiX RTN 310 interconnects with the OptiX RTN 900 through Ethernet ports, it is recommended
that you set SYNC Packet Period (s) to 256/1024 and set ANNOUNCE Packet Period (s), PDELAY Packet
Period (s), and DELAY Packet Period (s) to 1 for the Ethernet ports.
Issue 02 (2012-12-30)

694

Parameters for Cable Transmission Offset

Parameter
Value Range
Default Value
Description
Port
Displays the PTP port

names.
Warp Direction
Negative
Positive
l Specifies the
transmission direction
of PTP packets.
Positive
l Specifies whether
asymmetric delay
compensation is
performed in the
transmit direction or
receive direction.
Warp Mode
Length
Length
Time
l Specifies the
transmission delay
compensation mode.
l Length indicates that
compensation is
provided based on the
distance between the
receive end and the
transmit end.
l Time indicates that
compensation is
provided based on the
transmission delay
between the receive
end and the transmit
end.
l Generally, the value
Time is used.
Warp Length(m)
l Specifies the distance

to be compensated.
set when Warp Mode
is Length.
Wrap Time (ns)
l Specifies the time

delay to be
compensated.
l This parameter value
can be obtained by
means of GPS
calibration.
set when Warp Mode
is Time.
Issue 02 (2012-12-30)

695

Related Tasks
A.8.2.3 Setting the PTP NE Attributes
A.8.2.5 Setting PTP Clock Port Attributes
A.8.2.6 Setting Parameters for IEEE 1588v2 Clock Packets
A.8.2.7 Configuring the Delay Offset for Asymmetric Transmission Between NEs
B.7.2 Parameter Description: Setting of a PTP Clock Subnet_Clock

Subnet
This topic describes the parameters that are related to a PTP clock subnet.

Parameter
Value Range
Default Value
Description
NE Name
Displays the name of the

local NE.
Clock Subnet No.
0-255

to be set when a clock
subnet topology needs
to be created on the
NMS.
l NEs that trace the same
grandmaster clock
need to be allocated the
same clock subnet ID.
Related Tasks
A.8.2.9 Configuring a PTP Clock Subnet
B.7.3 Parameter Description: Setting of a PTP Clock

Subnet_Port_BMC
This topic describes the BMC parameters that are related to a PTP clock subnet.

Parameter
Value Range
Default Value
Description
NE Name
Displays the NE Name.
Issue 02 (2012-12-30)

696

Parameter
Value Range
Default Value
Description
Time Quality Level
0-255
187
l The smaller the

parameter value, the
higher the quality
level.
recommended.
Time Precision
0-255
254
l The smaller the

higher the time
accuracy.
recommended.
PTP Clock Source Type
ATOMIC_CLOCK
GPS
INTERNAL_OSCILLATOR
Specifies the source of an

external clock. For
example, if an external
clock is obtained by means
of GPS, set this parameter
to GPS.
128
l The smaller the

higher the priority.
TERRESTRIAL_RADIO
PTP
NTP
HAND_SET
OTHER
INTERNAL_OSCILLATOR
PTP Clock Source
Priority 1
0-255
l If the external clock

source functions as the
master clock, the value
1 is recommended.
Issue 02 (2012-12-30)

697

Parameter
Value Range
Default Value
Description
PTP Clock Source

Priority 2
0-255
128
l The smaller the

higher the clock
priority.
you set this parameter
to 1 for the external
clock source that
functions as the
grandmaster clock in a
clock subnet.
l If another external
clock source functions
as a standby
grandmaster clock in
the clock subnet, it is
set this parameter to 2
for the external clock
source.
NOTE
Select the optimal clock
source according to the
following preference
sequence: Clock source
priority 1 > Time precision
> Time quality level > Clock
source priority 2.
Related Tasks
A.8.2.10 Modifying the BMC Algorithm Parameters for an NE Clock
Issue 02 (2012-12-30)

698

C Glossary
Glossary
Numerics
3G
See 3rd Generation.
3rd Generation (3G)
The third generation of digital wireless technology, as defined by the International

Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to
19.2 kbit/s offered by second generation technology.
A
ABR
See area border router.
ACAP
See adjacent channel alternate polarization.
ACL
See access control list.
AF
See assured forwarding.
AIS
alarm indication signal
AM
See adaptive modulation.
ARP
See Address Resolution Protocol.
ASBR
See autonomous system boundary router.
ATM
asynchronous transfer mode
ATPC
See automatic transmit power control.
Address Resolution
Protocol (ARP)
An Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and
routers to determine the link layer addresses through ARP requests and ARP responses.
access control list

(ACL)
A list of entities, together with their access rights, which are authorized to have access
to a resource.
adaptive modulation
(AM)
A technology that is used to automatically adjust the modulation mode according to the
channel quality. When the channel quality is favorable, the equipment uses a highefficiency modulation mode to improve the transmission efficiency and the spectrum
utilization of the system. When the channel quality is degraded, the equipment uses the
low-efficiency modulation mode to improve the anti-interference capability of the link
that carries high-priority services.
Issue 02 (2012-12-30)

699

C Glossary
adjacent channel
alternate polarization
(ACAP)
A channel configuration method, which uses two adjacent channels (a horizontal

polarization wave and a vertical polarization wave) to transmit two signals.
air interface
The interface between the cellular phone set or wireless modem (usually portable or
mobile) and the active base station.
alarm suppression
An alarm management method. Alarms that are set to be suppressed are not reported
from NEs any more.
area border router

(ABR)
A router that can belong to more than two areas of which one area must be a backbone
area.
assured forwarding
(AF)
One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.
It is suitable for certain key data services that require assured bandwidth and short delay.
For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that
exceeds the bandwidth limit, AF degrades the service class and continues to forward the
traffic instead of discarding the packets.
automatic transmit
A method of adjusting the transmit power based on fading of the transmit signal detected
power control (ATPC) at the receiver
autonomous system
boundary router
(ASBR)
A router that exchanges routing information with other ASs.
B
BE
See best effort.
BIOS
See basic input/output system.
backup
A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth
A range of transmission frequencies that a transmission line or channel can carry in a

network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
baseband
A form of modulation in which the information is applied directly onto the physical
transmission medium.
basic input/output
system (BIOS)
A firmware stored in the computer mainboard. It contains basic input/output control

programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
best effort (BE)
A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of the
network and routers. The amount of resource that a diagram can use depends of the time
it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss
ratio, and high reliability.
blacklist
A method of filtering packets based on their source IP addresses. Compared with ACL,
the match condition for the black list is much simpler. Therefore, the black list can filter
packets at a higher speed and can effectively screen the packet sent from the specific IP
address.
Issue 02 (2012-12-30)

700

C Glossary
bridge
A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ from repeaters because bridges store
and forward complete packets, while repeaters forward all electrical signals. Bridges
differ from routers because bridges use physical addresses, while routers use IP
addresses.
broadcast
A means of delivering information to all members in a network. The broadcast range is

determined by the broadcast address.
burst
A process of forming data into a block of the proper size, uninterruptedly sending the
block in a fast operation, waiting for a long time, and preparing for the next fast sending.
C
CC
See continuity check.
CCDP
See co-channel dual polarization.
CSES
consecutive severely errored second
CSMA/CD
See carrier sense multiple access with collision detection.
carrier sense multiple

access with collision
detection (CSMA/CD)
Carrier sense multiple access with collision detection (CSMA/CD) is a computer

networking access method in which:
l
A carrier sensing scheme is used.
A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
chain network
One type of network that all network nodes are connected one after one to be in series.
channel spacing
The center-to-center difference in frequency or wavelength between adjacent channels

in a WDM device.
co-channel dual
polarization (CCDP)
A channel configuration method, which uses a horizontal polarization wave and a vertical
polarization wave to transmit two signals. The Co-Channel Dual Polarization has twice
the transmission capacity of the single polarization.
congestion
management
A flow control measure to solve the problem of network resource competition. When
the network congestion occurs, it places packets into the queue for buffer and determines
the packet forwarding order.
continuity check (CC)
Ethernet CFM can detect the connectivity between MEPs. The detection is achieved after
MEPs transmit Continuity Check Messages (CCMs) periodically.
cross polarization
interference
cancellation (XPIC)
A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate
the cross-connect interference between two polarization waves in the CCDP.
D
DCC
See data communications channel.
DCN
See data communication network.
DD
database description
DM
See delay measurement.
Issue 02 (2012-12-30)

701

C Glossary
DRDB
dynamic random database
DS
data service
DSCP
differentiated services code point
data communication
network (DCN)
A communication network used in a TMN or between TMNs to support the data

communication function.
data communications
channel (DCC)
The data channel that uses the D1D12 bytes in the overhead of an STM-N signal to
transmit information about operation, management, maintenance and provision
(OAM&P) between NEs. The DCC channels that are composed of bytes D1D3 are
referred to as the 192 kbit/s DCC-R channel. The other DCC channels that are composed
of bytes D4D12 are referred to as the 576 kbit/s DCC-M channel.
delay measurement
(DM)
The time elapsed since the start of transmission of the first bit of the frame by a source
node until the reception of the last bit of the loopbacked frame by the same source node,
when the loopback is performed at the frame's destination node.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves
orthogonally polarized.
E
E-LAN
See Ethernet local area network.
E-Line
See Ethernet line.
E1
An European standard for high-speed data transmission at 2.048 Mbit/s. It provides

thirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32
timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization, and
timeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use as speech
channels. Each timeslot sends or receives an 8-bit data per second. Each frame sends or
receives 256-bit data per second. 8000 frames will be sent or received per second.
Therefore the line data rate is 2.048 Mbit/s.
ECC
See embedded control channel.
EF
See expedited forwarding.
EMC
See electromagnetic compatibility.
ERPS
Ethernet ring protection switching
ES
errored second
ESD
electrostatic discharge
ETS
European Telecommunication Standards
ETSI
See European Telecommunications Standards Institute.
Ethernet line (E-Line)
A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual

connection).
Ethernet local area

network (E-LAN)
A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet

virtual connection).
European
Telecommunications
Standards Institute
(ETSI)
A standards-setting body in Europe. Also the standards body responsible for GSM.
Issue 02 (2012-12-30)

702

C Glossary
electromagnetic
compatibility (EMC)
A condition which prevails when telecommunications equipment is performing its

individually designed function in a common electromagnetic environment without
causing or suffering unacceptable degradation due to unintentional electromagnetic
interference to or from other equipment in the same environment.
embedded control
channel (ECC)
A logical channel that uses a data communications channel (DCC) as its physical layer,
to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
expedited forwarding
(EF)
The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF
traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP
value of EF PHB is "101110".
extended ID
The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The physical ID of an NE is comprised of the NE ID and extended
ID.
extended NE ID
The serial number of a subnetwork where an NE resides, which is usually used to

distinguish different network segments. An extended ID and an ID form the physical ID
of an NE.
F
FE
See fast Ethernet.
FEC
See forward error correction.
FIFO
See first in first out.
FPGA
See field programmable gate array.
FTP
File Transfer Protocol
fast Ethernet (FE)
Any network that supports transmission rate of 100 Mbit/s. The Fast Ethernet is 10 times
faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so
on. Fast Ethernet is extended based on the IEEE802.3 standard, and it uses the following
three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),
100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical
fibers).
field programmable
gate array (FPGA)
A type of semi-customized circuit used in the application specific integrated circuit

(ASIC) field. It is developed on the basis of the programmable components, such as the
PAL, GAL, and EPLD. It not only remedies the defects of customized circuits but also
overcomes the disadvantage of the original programmable components in terms of the
limited number of gate arrays.
first in first out (FIFO) A stack management mechanism. The first saved data is first read and invoked.
flooding
A type of incident, such as insertion of a large volume of data, that results in denial of
service.
forward error
correction (FEC)
A bit error correction technology that adds the correction information to the payload at
the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
G
GE
Issue 02 (2012-12-30)
See gigabit Ethernet.

703

C Glossary
GNE
See gateway network element.
gateway
A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
gateway network
element (GNE)
A network element that is used for communication between the NE application layer and
the NM application layer.
gigabit Ethernet (GE)
A collection of technologies for transmitting Ethernet frames at a rate of a gigabit per

second, as defined by the IEEE 802.3z standard. GE is compatible with 10 Mbit/s and
100 Mbit/s Ethernet. It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and
it does not support coaxial cables or other cables. It also supports the channels in the
bandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidth
system with a bridge (switch) or a router as the center, it gives full play to the performance
and the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links that
are private, causing the length of the links to be sufficient for backbone applications in
a building and campus.
H
HSDPA
See High Speed Downlink Packet Access.
HUAWEI Electronic
Document Explorer
(HedEx)
The software used to view, search for, and upgrade electronic documentation of Huawei
products. HedEx, pronounced as [hediks], has two editions, HedEx Lite and HedEx
Server.
HedEx
See HUAWEI Electronic Document Explorer.
High Speed Downlink

Packet Access
(HSDPA)
A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement

for asymmetric uplink and downlink transmission of data services. It enables the
maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
I
ICMP
See Internet Control Message Protocol.
IDU
See indoor unit.
IEEE
See Institute of Electrical and Electronics Engineers.
IETF
See Internet Engineering Task Force.
IP
Internet Protocol
IP address
A 32-bit (4-byte) binary digit that uniquely identifies a host (computer) connected to the
Internet for communication with other hosts in the Internet by transferring packets. An
IP address is expressed in dotted decimal notation, consisting of decimal values of its 4
bytes, separated by periods (,), for example, 127.0.0.1. The first three bytes of an IP
address identify the network to which the host is connected, and the last byte identifies
the host itself.
IPv4
See Internet Protocol version 4.
IPv6
See Internet Protocol version 6.
ISO
International Organization for Standardization
ITU
See International Telecommunication Union.
Issue 02 (2012-12-30)

704

C Glossary
ITU-T
See International Telecommunication Union-Telecommunication Standardization

Sector.
Institute of Electrical
and Electronics
Engineers (IEEE)
A society of engineering and electronics professionals based in the United States but
boasting membership from numerous other countries. The IEEE focuses on electrical,
electronics, computer engineering, and science-related matters.
International
Telecommunication
Union (ITU)
A United Nations agency, one of the most important and influential recommendation
bodies, responsible for recommending standards for telecommunication (ITU-T) and
radio networks (ITU-R).
International
Telecommunication
UnionTelecommunication
Standardization Sector
(ITU-T)
An international body that develops worldwide standards for telecommunications

technologies. These standards are grouped together in series which are prefixed with a
letter indicating the general subject and a number specifying the particular standard. For
example, X.25 comes from the "X" series which deals with data networks and open
system communications and number "25" deals with packet switched networks.
Internet Control
Message Protocol
(ICMP)
A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and
other information relevant to IP packet processing. For example, it can let the IP software
on one machine inform another machine about an unreachable destination. See also
communications protocol, IP, ISO/OSI reference model, packet (definition 1).
Internet Engineering
Task Force (IETF)
A worldwide organization of individuals interested in networking and the Internet.

Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with
studying technical problems facing the Internet and proposing solutions to the Internet
Architecture Board (IAB). The work of the IETF is carried out by various working groups
that concentrate on specific topics such as routing and security. The IETF is the publisher
of the specifications that led to the TCP/IP protocol standard.
Internet Protocol
version 4 (IPv4)
The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers together
are used for routing, and the host number is used to address an individual host within the
network or subnetwork.
Internet Protocol
version 6 (IPv6)
An update version of IPv4, which is designed by the Internet Engineering Task Force
(IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
indoor unit (IDU)
The indoor unit of the split-structured radio equipment. It implements accessing,

multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
J
jitter
Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
L
L2VPN
Layer 2 virtual private network
LACP
See Link Aggregation Control Protocol.
Issue 02 (2012-12-30)

705

C Glossary
LAG
See link aggregation group.
LAN
See local area network.
LB
See loopback.
LBM
See loopback message.
LBR
See loopback reply.
LCT
local craft terminal
LM
See loss measurement.
LOS
See loss of signal.
LSA
link-state advertisement
LSDB
link state database
LSR
See label switching router.
LT
linktrace
LTM
See linktrace message.
LTR
See linktrace reply.
Layer 2 switching
A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch

transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switching.
Link Aggregation
Control Protocol
(LACP)
A method of bundling a group of physical interfaces together as a logical interface to

increase bandwidth and reliability. For related protocols and standards, refer to IEEE
802.3ad.
label switching router

(LSR)
Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is
composed of two parts: control unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label forwarding table, creating and
removing the label switch path; the latter forwards the labels according to groups
received in the label forwarding table.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
(LAG)
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
linktrace message
(LTM)
The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP.
LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.
linktrace reply (LTR)
For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called LTR. LTR also includes the TTL that equals the result of the TTL of LTM minus
1.
local area network

(LAN)
A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
loopback (LB)
A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
Issue 02 (2012-12-30)

706

C Glossary
loopback message
(LBM)
The loopback packet sent by the node that supports 802.2ag MAC Ping to the destination
node. LBM message carries its own sending time.
loopback reply (LBR)
A response message involved in the 802.2ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the LBM.
The LBR carries the sending time of LBM, the receiving time of LBM and the sending
time of LBR.
loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frames
where the counters maintain a count of transmitted and received data frames between a
pair of MEPs.
loss of signal (LOS)
No transitions occurring in the received signal.
M
MA
maintenance association
MAC
See Media Access Control.
MAC address
A link layer address or physical address. It is six bytes long.
MD
See maintenance domain.
MDI
medium dependent interface
ME
maintenance entity
MEP
maintenance end point
MIB
See management information base.
MIP
maintenance intermediate point
MP
maintenance point
MPLS
See Multiprotocol Label Switching.
MSTP
See Multiple Spanning Tree Protocol.
MTBF
See mean time between failures.
MTTR
See mean time to repair.
MTU
See maximum transmission unit.
Media Access Control

(MAC)
A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
Multiple Spanning
Tree Protocol (MSTP)
A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
redundant paths so that the loop network can be trimmed as a tree network. In this case,
the proliferation and endless cycling of packets is avoided in the loop network. The
protocol that introduces the mapping between VLANs and multiple spanning trees. This
solves the problem that data cannot be normally forwarded in a VLAN because in STP/
RSTP, only one spanning tree corresponds to all the VLANs.
Issue 02 (2012-12-30)

707

C Glossary
Multiprotocol Label
Switching (MPLS)
A technology that uses short tags of fixed length to encapsulate packets in different link
layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
maintenance domain
(MD)
The network or the part of the network for which connectivity is managed by connectivity
fault management (CFM). The devices in a maintenance domain are managed by a single
Internet service provider (ISP).
management
A type of database used for managing the devices in a communications network. It
information base (MIB) comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies,
unit (MTU)
depending on the network576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
mean time between
failures (MTBF)
The average time between consecutive failures of a piece of equipment. It is a measure

of the reliability of the system.
mean time to repair

(MTTR)
The average time that a device will take to recover from a failure.
microwave
The portion of the electromagnetic spectrum with much longer wavelengths than infrared
radiation, typically above about 1 mm.
multicast
A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
N
NAS
network access server
NE
network element
NE Explorer
The main operation interface, of the network management system, which is used to
manage the telecommunication equipment. In the NE Explorer, the user can query,
manage and maintain the NE, boards, and ports on a per-NE basis.
NTP
Network Time Protocol
network segment
A part of an Ethernet or other network, on which all message traffic is common to all
nodes, that is, it is broadcast from one node on the segment and received by all others.
network storm
A phenomenon that occurs during data communication. To be specific, mass broadcast

packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by network
connection or configuration problems.
O
OAM
Issue 02 (2012-12-30)
See operation, administration and maintenance.

708

C Glossary
ODF
optical distribution frame
ODU
See outdoor unit.
OSI
See open systems interconnection.
OSPF
See Open Shortest Path First.
Open Shortest Path

First (OSPF)
A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed with the network topology which is identical on all
routers in the area.
open systems
interconnection (OSI)
A framework of ISO standards for communication between different systems made by

different vendors, in which the communications process is organized into seven different
categories that are placed in a layered sequence based on their relationship to the user.
Each layer uses the layer immediately below it and provides a service to the layer above.
Layers 7 through 4 deal with end-to-end communication between the message source
and destination, and layers 3 through 1 deal with network functions.
operation,
administration and
maintenance (OAM)
A group of network support functions that monitor and sustain segment operation,
support activities that are concerned with, but not limited to, failure detection,
notification, location, and repairs that are intended to eliminate faults and keep a segment
in an operational state, and support activities required to provide the services of a
subscriber access network to users/subscribers.
outdoor unit (ODU)
The outdoor unit of the split-structured radio equipment. It implements frequency

conversion and amplification for radio frequency (RF) signals.
P
P2P
See point-to-point service.
PBS
See peak burst size.
PDU
protocol data unit
PHB
See per-hop behavior.
PLL
See phase-locked loop.
PPP
Point-to-Point Protocol
PPPoE
Point-to-Point Protocol over Ethernet
PRBS
See pseudo random binary sequence.
PSN
See packet switched network.
PTP
Precision Time Protocol
PWE3
See pseudo wire emulation edge-to-edge.
packet loss
The discarding of data packets in a network when a device is overloaded and cannot
accept any incoming data at a given moment.
packet switched
network (PSN)
A telecommunications network that works in packet switching mode.
peak burst size (PBS)
A parameter that is used to define the capacity of token bucket P, that is, the maximum
burst IP packet size when the information is transferred at the peak information rate. This
parameter must be larger than 0. It is recommended that PBS should be not less than the
maximum length of the IP packet that might be forwarded. See also CIR, CBS, and PIR.
Issue 02 (2012-12-30)

709

C Glossary
per-hop behavior
(PHB)
IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop

behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).
phase-locked loop
(PLL)
A circuit that consists essentially of a phase detector which compares the frequency of
a voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator; the output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
physical layer
Layer 1 in the Open System Interconnection (OSI) architecture; the layer that provides
services to transmit bits or groups of bits over a transmission link between open systems
and which entails electrical, mechanical and handshaking.
point-to-point service
(P2P)
A service between two terminal users. In P2P services, senders and recipients are
terminal users.
polarization
A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
policy
A set of rules that are applied when the conditions for triggering an event are met.
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the
sequence (PRBS)
values of any of the other elements, similar to real random sequences.
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
edge-to-edge (PWE3) telecommunication service such as ATM, FR or Ethernet in a packet switched network
(PSN). PWE3 also emulates the essential attributes of low speed time division
multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
Q
QPSK
See quadrature phase shift keying.
QoS
See quality of service.
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying (QPSK)
the phase determination of the reference signals (carrier). It is also called the fourth period
or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are
evenly distributed on a circle. On these phases, each QPSK character can perform twobit coding and display the codes in Gray code on graph with the minimum BER.
quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
Issue 02 (2012-12-30)

710

C Glossary
RADIUS
See Remote Authentication Dial-In User Service.
RADIUS
authentication
An authentication mode in which the BRAS sends the user name and the password to
the RADIUS server by using the RADIUS protocol. The RADIUS server authenticates
the user, and then returns the result to the BRAS.
RDI
remote defect indication
RED
See random early detection.
RF
See radio frequency.
RFC
See Request For Comments.
RMON
remote network monitoring
RNC
See radio network controller.
RSL
See received signal level.
RSSI
See received signal strength indicator.
RTN
radio transmission node
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial-In User Service
access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
(RADIUS)
transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
Request For Comments A document in which a standard, a protocol, or other information pertaining to the
(RFC)
operation of the Internet is published. The RFC is actually issued, under the control of
the IAB, after discussion and serves as the standard. RFCs can be obtained from sources
such as InterNIC.
radio frequency (RF)
A type of electric current in the wireless network using AC antennas to create an

electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
radio network
controller (RNC)
A piece of equipment in the RNS which is in charge of controlling the use and the integrity
of the radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
(RED)
to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulting from traditional tail drop can be prevented.
received signal level
(RSL)
The signal level at a receiver input terminal.
received signal strength The received wide band power, including thermal noise and noise generated in the
indicator (RSSI)
receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
receiver sensitivity
The minimum acceptable value of average received power at point R to achieve a 1 x

10-12 BER (The FEC is open).
route
The path that network traffic takes from its source to its destination. In a TCP/IP network,
each IP packet is routed independently. Routes can change dynamically.
routing table
A mapping table that stores the relationship between the original address, destination
address, SMS protocol type, and account. The SMSC delivers an SMS message to the
designated account according to the information in the routing table.
Issue 02 (2012-12-30)

711

C Glossary
S
SD
See signal degrade.
SF
See signal fail.
SFP
small form-factor pluggable
SNMP
See Simple Network Management Protocol.
SNR
See signal-to-noise ratio.
SPF
shortest path first
SSL
See Secure Sockets Layer.
SSM
See Synchronization Status Message.
Secure Sockets Layer

(SSL)
A security protocol that works at a socket level. This layer exists between the TCP layer
and the application layer to encrypt/decode data and authenticate concerned entities.
Simple Network
Management Protocol
(SNMP)
A network management protocol of TCP/IP. It enables remote users to view and modify
the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Nodes on an SDH network and a synchronization network acquire upstream clock
Message (SSM)
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.
service flow
An MAC-layer-based unidirectional transmission service. It is used to transmit data

packets, and is characterized by a set of QoS parameters, such as latency, jitter, and
throughput.
shaping
A process of delaying packets within a traffic stream to cause it to conform to specific

defined traffic profile.
signal degrade (SD)
A signal indicating that associated data has degraded in the sense that a degraded defect
condition is active.
signal fail (SF)
A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio
(SNR)
The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB (Decibel).
single-polarized
antenna
An antenna intended to radiate or receive radio waves with only one specified
polarization.
subnet mask
The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router matches with the IP address.
T
Issue 02 (2012-12-30)

712

C Glossary
TCP/IP
Transmission Control Protocol/Internet Protocol
TD-SCDMA
See Time Division-Synchronous Code Division Multiple Access.
Time DivisionSynchronous Code

Division Multiple
Access (TD-SCDMA)
A 3G mobile communications standard found in UMTS mobile telecommunications

networks in China as an alternative to W-CDMA. TD-SCDMA integrates technologies
of CDMA, TDMA, and FDMA, and makes use of technologies including intelligent
antenna, joint detection, low chip rate (LCR), and adaptive power control. With the
flexibility of service processing, a TD-SCDMA network can connect to other networks
through the RNC.
tail drop
A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
tolerance
Permissible degree of variation from a pre-set standard.
traffic classification
A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the entire
network. In this way, different traffic packets can be treated differently.
traffic shaping
A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in the
scenario that the traffic matches network resources provided by the lower layer devices,
avoiding packet loss and congestion.
U
UAS
unavailable second
UAT
See unavailable time event.
UDP
See User Datagram Protocol.
UNI
See user-to-network interface.
User Datagram
Protocol (UDP)
A TCP/IP standard protocol that allows an application program on one device to send a
datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagram. UDP provides application programs with the unreliable
connectionless packet delivery service. There is a possibility that UDP messages will be
lost, duplicated, delayed, or delivered out of order. The destination device does not
confirm whether a data packet is received.
unavailable time event An event that is reported when the monitored object generates 10 consecutive severely
(UAT)
errored seconds (SES) and the SESs begin to be included in the unavailable time. The
event will end when the bit error ratio per second is better than 10-3 within 10 consecutive
seconds.
unicast
The process of sending data from a source to a single recipient.
user-to-network
interface (UNI)
The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
VB
virtual bridge
VLAN
virtual local area network
VM
virtual memory
Issue 02 (2012-12-30)

713

C Glossary
W
WAN
See wide area network.
WEEE
waste electrical and electronic equipment
WRED
See weighted random early detection.
WRR
weighted round robin
WTR
See wait to restore.
Web LCT
The local maintenance terminal of a transport network, which is located at the NE

management layer of the transport network.
wait to restore (WTR)
The number of minutes to wait before services are switched back to the working line.
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
detection (WRED)
synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
wide area network
(WAN)
A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
window
General method for speech preprocessing, like Haming window.
X
XPIC
Issue 02 (2012-12-30)
See cross polarization interference cancellation.

714

RTN 310 V100R001C01 Commissioning and Configuration Guide 02 PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RTN 310 V100R001C01 Commissioning and Configuration Guide 02 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX RTN 310 Radio Transmission System

Commissioning and Configuration

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

About This Document

About This Document

OptiX RTN 310

Installation and commissioning engineers

Data configuration engineers

System maintenance engineers

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

About This Document

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

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

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

8.7 Configuring Native Ethernet Services

Added end-to-end configuration examples.

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

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

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

4.4 Creating NEs Using the Search Method...........................................................................................................37

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

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

6.7.1 Testing the Latency, Throughput, and Packet Loss Ratio.....................................................................107

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

8 Configuring Networkwide Service Data..............................................................................116

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

8.6.3.1 Networking Diagram....................................................................................................................162

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

8.7.5.6 Per-NE Configuration Procedure (Ethernet Protection)...............................................................250

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

8.7.8.9 Per-NE Configuration Procedure (QoS).......................................................................................315

Huawei Proprietary and Confidential

OptiX RTN 310 Radio Transmission System

A.3.1.4 Changing an NE ID.....................................................................................................................366

Huawei Proprietary and Confidential